Hi. I committed a cardinal sin when installing TWRP by 'fastboot -i 0x0b05 flash recovery' but using the wrong file on my ME301T. This has led to to a dead android icon when trying to launch recovery. Trying to correct this by flashing the correct file brings up an error, "writing 'recovery' FAILED (remote: (InvalidState))." The machine otherwise boots up into 4.2 fine, and has been unlocked.
Is there any hope or any suggestions for fixing the recovery img and installing TWRP? Thanks much in advance.
Steve
Problem solved
Duffyxy said:
Hi. I committed a cardinal sin when installing TWRP by 'fastboot -i 0x0b05 flash recovery' but using the wrong file on my ME301T. This has led to to a dead android icon when trying to launch recovery. Trying to correct this by flashing the correct file brings up an error, "writing 'recovery' FAILED (remote: (InvalidState))." The machine otherwise boots up into 4.2 fine, and has been unlocked.
Is there any hope or any suggestions for fixing the recovery img and installing TWRP? Thanks much in advance.
Steve
Click to expand...
Click to collapse
Solution was right here:
http://forum.xda-developers.com/showthread.php?t=2179759&page=2
Hello,
I think my XT1541 (16GB/2GB Retail GB) with locked bootloader might be hard-bricked.
I was running the stock 5.11 firmware when I did the 6.0 update and since then my phone is stuck in a bootloop.
Motorola won't repair it because I had to replace the screen and the phone is out of warranty.
I can access the bootloader but if I select recovery mode the phone just keeps bootlooping and I can't get into recovery.
I followed the instructions here to flash a stock firmware using fastboot. All the steps complete successfully but after rebooting, the phone is still stuck in a bootloop and I can't get into recovery.
I wanted to install a custom recovery but I'm unable to unlock my bootloader because of this error:
Code:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Obviously I can't check that option as the phone won't boot.
So, is it hard bricked? Is there anything I can do to get my phone to work again?
Thanks a lot for your help!
How many system images do you need to flash? Sometimes there can be more than 6, sometimes there can be fewer.
sticktornado said:
How many system images do you need to flash? Sometimes there can be more than 6, sometimes there can be fewer.
Click to expand...
Click to collapse
I know, I flashed the correct number of system images that were in the zip file.
Thanks,
rent0n said:
Hello,
I think my XT1541 (16GB/2GB Retail GB) with locked bootloader might be hard-bricked.
I was running the stock 5.11 firmware when I did the 6.0 update and since then my phone is stuck in a bootloop.
Motorola won't repair it because I had to replace the screen and the phone is out of warranty.
I can access the bootloader but if I select recovery mode the phone just keeps bootlooping and I can't get into recovery.
I followed the instructions here to flash a stock firmware using fastboot. All the steps complete successfully but after rebooting, the phone is still stuck in a bootloop and I can't get into recovery.
I wanted to install a custom recovery but I'm unable to unlock my bootloader because of this error:
Code:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Obviously I can't check that option as the phone won't boot.
So, is it hard bricked? Is there anything I can do to get my phone to work again?
Thanks a lot for your help!
Click to expand...
Click to collapse
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
prasi.ram10 said:
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
Click to expand...
Click to collapse
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?
prasi.ram10 said:
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
Click to expand...
Click to collapse
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?
rent0n said:
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?
Click to expand...
Click to collapse
I tried that and it didn't work. When I try to go into recovery mode the phone keeps bootlooping.
One thing I noticed is that when I try to format cache or userdata I get this error:
Code:
$ fastboot format cache
formatting 'cache' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.013s
I think there might be something wrong with the file system in my partitions. How can I manually format my partitions?
Thanks,
man , if you really need recovery, type fastboot boot recovery.img . It will temporaily boot you into stock recovery. Wipe cache and data there
therealduff1 said:
man , if you really need recovery, type fastboot boot recovery.img . It will temporaily boot you into stock recovery. Wipe cache and data there
Click to expand...
Click to collapse
Thanks, but this is what I get when I try do do that:
Code:
$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.736s]
booting...
FAILED (remote failure)
finished. total time: 0.746s
There must be a way to restore this phone to a working state! I can't believe it's so messed up after an official update...
rent0n said:
Thanks, but this is what I get when I try do do that:
Code:
$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.736s]
booting...
FAILED (remote failure)
finished. total time: 0.746s
There must be a way to restore this phone to a working state! I can't believe it's so messed up after an official update...
Click to expand...
Click to collapse
What os were you running when the phone screwed up ?
therealduff1 said:
What os were you running when the phone screwed up ?
Click to expand...
Click to collapse
I was running 5.1.1 when I got the notification for the 6.0 update.
I've noticed that trying to flash 5.1.1 firmware with fastboot gives me errors (preflash validation failed) while the 6.0 work "fine" (i.e.: I get OKAY after every step but then the phone is always stuck in a bootloop).
Thanks!
DO NOT ATTEMPT TO DOWNGRADE BOOTLOADER.IMG OR GPT.IMG !!!!!!! DONT FLASH LOLLIPOP VERSION OF THOSE FILES ON A DEVICE RUNNING 6.0
plz tell me u didnt flash those files..
therealduff1 said:
DO NOT ATTEMPT TO DOWNGRADE BOOTLOADER.IMG OR GPT.IMG !!!!!!! DONT FLASH LOLLIPOP VERSION OF THOSE FILES ON A DEVICE RUNNING 6.0
plz tell me u didnt flash those files..
Click to expand...
Click to collapse
Well I wasn't sure what version I was running to be honest so I think I tried to flash the gpt.img from 5.1.1 at some point but it failed with the preflash validation failure. I've always only flashed the 6.0 firmware files.
rent0n said:
Well I wasn't sure what version I was running to be honest so I think I tried to flash the gpt.img from 5.1.1 at some point but it failed with the preflash validation failure. I've always only flashed the 6.0 firmware files.
Click to expand...
Click to collapse
Have you gave this a try?
heavy_metal_man said:
Have you gave this a try?
Click to expand...
Click to collapse
Yes, no luck unfortunately.
I think I might have flashed the 5.1.1 bootloader after all - is there any way to recover from there?
Thanks,
Bump!
Does anyone have any other suggestion please?
Thanks,
Last bump
I'm going to sell this on eBay as non-working then unless someone comes up with a clever solution?
Thanks for your help!
Try flashing once more starting with the gpt.bin (that should hopefully take care of raw partition error) and skipping the bootloader altogether. Also, may be worthwhile to try mfastboot.exe instead of fastboot.exe.
I have this same issue, but I haven't flash 5.1.1 Files, I Only tried with 6.0 Brazil Retail.
I also tried to flash gpt to get rid of the "raw" partition, everything goes ok but still displaying that error. Anyone can help?
I got the same problem with my Moto E 2015... If I find a solution I will reply it in this topic..
Hello,
I was facing a lot of issues with my YUPHORIA. So, I tried to flash it using the official instructions on official forum using Fastboot.
The flashing got stuck when it was trying to flash the "system" partition. I disconnected the cable and tried the flashing process again.
Now, I am able to flash everything else except "system"
It is giving an error -
"FAILED (remote: flash write failure)"
ADB is not detecting my phone.
QFIL is also showing "No Ports Found"
However, Fastboot is working fine.
I donot have TWRP on my phone as of now.
Please help !
I am having exact same problem. Were you able to find solution for it?
Same issue here
Did you get the final solution?
I cant not flash system.img to my softbricked Yu Yuphoria 5110 even with the latest version of adb and fastboot and even with the -S option! Nothing works! Can't flash only system.img, other images are getting flashed. Pl help!
hi
yesterday i tried to flash the latest LineageOS rom on my Mi pad 1
i booted into fastboot, erased everything and tried a command "Fastboot flash rom xxxx.zip"
and there i got the error FAILED (remote: Invalid Partition Name.)
anyone know what to do? it's two years since i worked in adb/fastboot and i cant remember :crying: :crying:
i have also tried to boot into CWM and 2 versions of TWRP - witch only the latest TWRP started and "froze" on boot(?) the totch did not work and the tablet rebooted after a while
ttps://forum.xda-developers.com/oneplus-6/themes/magisk-aod-lockscreen-weather-mods-oos-t3847008
OPENBETA3 I installed this module magiskden to my oneplus 6 device installed in rom. I installed the system backup from twrp (bluspark v9.85) before installing.
When I set up the module and restart it, the screen was opened and closed, it was not possible to enter magisk manager.
Twrpye and I said 'restore system'. When the Restore process was completed, I said reboot system and went into fastboot mode.
I can't boot to the phone and write twrp. Fastboot is entering mode every time I restart.
I need to save my data. I don't want to flash fastboot rum.
I think there is no way without msmtool. I had the same problem when I tried to restore backup.
Kollachi said:
I think there is no way without msmtool. I had the same problem when I tried to restore backup.
Click to expand...
Click to collapse
fastboot boot twrp-3.2.1-0-enchilada.img
downloading 'boot.img'...
OKAY [ 0.579s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.609s
have you received such an error?
This isn't related to the module and seems to happen whenever I try to restore /boot or /system using TWRP. This is easily fixable by flashing the original boot.img
Is there any other solution than flashing the factory rum? At least if I twrp, I would back up internal storage.
DevrimSeven60 said:
fastboot boot twrp-3.2.1-0-enchilada.img
downloading 'boot.img'...
OKAY [ 0.579s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.609s
have you received such an error?
Click to expand...
Click to collapse
Yes I had the same error
Kollachi said:
Yes I had the same error
Click to expand...
Click to collapse
what is the solution? Bluspark twrp flash I do not get error, but twrpye can not enter, although it is completed.
DevrimSeven60 said:
Is there any other solution than flashing the factory rum? At least if I twrp, I would back up internal storage.
Click to expand...
Click to collapse
You can try flash the boot.img like paphonb said. I didn't knew that and used msmtool. But I saved my data before restoring in twrp so I didn't lose anything just a lil bit time
paphonb said:
This isn't related to the module and seems to happen whenever I try to restore /boot or /system using TWRP. This is easily fixable by flashing the original boot.img
Click to expand...
Click to collapse
open beta 3 i have downloaded full rom zip. Is there an img I can use in zip?