29.03.2017 13:02 - bearbeitet 29.03.2017 13:03
I have the known problem where a tablet boots into efi shell. So I try to use EFI Boot Fix .
Flash drive is formated as fat32, EFI Bott Fix files are placed on the flash drive. I connect the FlashDrive via OTG to tablet and powerOn the tablet.
The result is, that tablet doesn't start Android OS and again do the same problem. I captured a screenshot from the tablet durring the fixing process.
Thanks for any hints
30.03.2017 17:50 - bearbeitet 30.03.2017 18:00
I am not sure if I understand You correctly (german language I translate via translator), but Yes I use OTG reduction with three different USB sticks(512MB, 6GB, 8GB) all formated as FAT
do You think will be good to try use USB HUB?
tablet->OTG->USB HUB->USB Stick
30.03.2017 19:13 - bearbeitet 30.03.2017 19:24
Here in your flash failure-protocol it says "error":
error: cannot load '/efilinux-.efi': No such file or directory
I think the error text should be:
error: cannot load '/efilinux-user.efi': No such file or directory
That is maybe the reason für your bootorder-error; the efilinux-user.efi file was never found nor flashed, because the flash.sh looks instead for the "/efilinux-user .efi" for the "/efilinux- .efi" ?
The flash.sh says:
"./fastboot flash osloader $OUT/efilinux-$TARGET_BUILD_VARIANT.efi"
Did you mess around with the " $OUT/efilinux-$TARGET_BUILD_VARIANT.efi" line, and gave this the possible wrong error-text? Or is the efilinux-path wrongly written??
(Although later on the esp.zip is flashed, which also contains the identical files in Boot/ bootx64.efi and in /Intel/efilinux.efi; but do not know if bin the same position.
May be @TheDoctor could check this
30.03.2017 19:55 - bearbeitet 30.03.2017 20:20
Off course I read. Otherwise I couldn't have noticed the missing "user" in error-text:
"error: cannot load '/efilinux-.efi': No such file or directory"
The $TARGET_BUILD_VARIANT isn't replaced by "user" in error. Should it be?
Like I said in the beginning, I do not know much about Linux or Android.
May be by replacing standard $OUT with your long path-name (too long?) you made an error or typo?
And yes, reflashing the recovery-package in Windows you should try; but for safety reason make a new download before.
am 30.03.2017 20:00
when I replace the $OUT everywhere where the variable is , with my absolute path /home/zajdan/Downloads/medion-p7332/
the mentioned files are loaded without error
am 31.03.2017 08:34
I tried recovery package also from windows, but during process stage 2 each step ends with status FAILED