Background:
I was having issues with my front/rear cameras failing to initialize sometimes, so I decided to do a factory reset of my phone. I was on 9.18, both rooted and unlocked (I unlocked prior to going to 9.18). I was able to use the RAZR Utility to downgrade to 4.1.2 and then root again. However, when I did the OTA update for my phone, the update failed and now my phone is stuck in "AP Fastboot Flash Mode (S)".
On the Fastboot screen it reads:
downgraded security version
update gpt_main version failed
failed to hab check for gpt_backup: 0x35
failed to load GPT
CID Read Failure
Invalid CID status 0x69
No SP partition found
Fastboot Reason: Invalid GPT
I have tried using RSD Lite to go to 9.30, but it keeps failing (I may be doing something wrong...). If anyone could provide any help, it would be greatly appreciated!
** Solved **
Used bweN diorD's modded utility to reformat the GPT partitions, all is well.
http://forum.xda-developers.com/showpost.php?p=49376894&postcount=6
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..
Hey guys. Today I tried to update my Moto G XT1039 EU version from CM12.1 to CM13. Firstly I tried to update my recovery... after some time i made it with problems. To open recovery i had to use command "fastboot boot recovery.img" and then it opened (I occured Boot up failed problem). Once I made it i went straing to erase any necessary data and I tried to install newest ROM which is CM13 and new gapps file. CM13 installed properly but gapps didnt. But i tried to turn on phone and see if it works anyway. Well... since then now i cant turn on phone becasue the only thing works is fastboot flash mode. I cant install any recovery file becasue i have Boot up fail problem, yet i cant open it via command prompt because Failed (Remote Failure). When i type "fastboot devices" my PC sees it. My bootloader version is 41.1A.
Is there any chance i can have that CM13 installed properly or at least to have it working at all?
Dear community. I screwed up.
I purchased my new OP7P and in all my excitement, logically, the first thing I went to do was to unlock the bootloader, install TWRP and root it, which I did successfully because I am pretty familiar with this on multiple phones. Long story short, here's what I did, and where my problem lies:
1. Went to install the Havoc Custom ROM by following their installation instructions, went ahead and booted to TWRP recovery
2. As instructed, wiped dalvik and /data
3. Flashed Havoc ROM and here is the part where I was supposed to flash TWRP installer
4. Forgot to reflash TWRP installer and rebooted to the now nonexisting recovery. - getting the dead android icon with the message "NO COMMAND"
5. After holding VOLUP + POWER managed to turn it off and then turn it on again with just POWER to be greeted with a message warning me that I am in a bootloop
and that I have two options; to try again or to "reset to factory settings", which I did, which booted me into the HavocOS.
The main problem here is that for some reason whenever I try to repeat the TWRP installation process using fastboot, by entering "fastboot boot twrp.img", it gives me the following error:
downloading 'boot.img'...
OKAY [ 1.340s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.343s
I have tried this on both Linux & Windows, same deal. The TWRP website has mentioned that if this happens I need root, but how do I root my phone without TWRP or "fastboot boot", and how do I install TWRP on the OP7P without livebooting TWRP?
Any help at all is truly appreciated. Thanks guys.
Download the MSM tool here and restore your phone. I've never used it but it gets everyone out of a brick.
I've used this tool a few times and it has gotten me out of a jam, just be sure to download the correct version for your phone. AFA your fastboot error, I got that until I let the OTA update to 9.5.11, then it worked again. https://forum.xda-developers.com/oneplus-7-pro/development/tool-tool-one-driversunlocktwrpfactory-t3930862
x3lade said:
The main problem here is that for some reason whenever I try to repeat the TWRP installation process using fastboot, by entering "fastboot boot twrp.img", it gives me the following error:
downloading 'boot.img'...
OKAY [ 1.340s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.343s
Click to expand...
Click to collapse
Try to fastboot boot the TWRP build -70 from here: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
It fixes the problem with "fastboot boot" not working on the official Android Q update. Not sure why that would apply to your case (custom ROM after already successfully installing TWRP). But it's very easy to try, and certainly can't hurt. And the error message you are getting is exactly the same as the official Android Q problem.
Hi,
I backed up my kernel using TWRP by fastbooting into the Pixel 3 blueline TWRP image. When I then tried to reboot the phone I get following error:
"Android Recovery
google/blueline/blueline
9/PI/gucheng0719045
userdebug/dev-keys
...
Can't load Android system."
I tried both options "try again" and "factory data reset" but both brought me back to this screen. I also tried booting into recovery mode and doing "Wipe data factory reset"; this also brought me back to the above error.
Finally, I tried installing OTA using sideload but the signature verification failed since I have an unlocked bootloader and had custom ROM running on the device.
How can I get the device into a usable state again? I don't care about keeping the data. Also note that I still have the TWRP kernel backup saved.
gardeimasei said:
Hi,
I backed up my kernel using TWRP by fastbooting into the Pixel 3 blueline TWRP image. When I then tried to reboot the phone I get following error:
"Android Recovery
google/blueline/blueline
9/PI/gucheng0719045
userdebug/dev-keys
...
Can't load Android system."
I tried both options "try again" and "factory data reset" but both brought me back to this screen. I also tried booting into recovery mode and doing "Wipe data factory reset"; this also brought me back to the above error.
Finally, I tried installing OTA using sideload but the signature verification failed since I have an unlocked bootloader and had custom ROM running on the device.
How can I get the device into a usable state again? I don't care about keeping the data. Also note that I still have the TWRP kernel backup saved.
Click to expand...
Click to collapse
Flash factory image with fastboot.
wangdaning said:
Flash factory image with fastboot.
Click to expand...
Click to collapse
Where can I get the factory image? And how do I use fastboot to flash the device? Like so?:
Code:
fastboot boot <image name>.img
I am able to fastboot boot into the blueline TWRP image. Selecting the "Fix bootloop" didn't work however
So I tried doing:
Code:
fastboot flash boot bootloader-blueline-b1c1-0.1-5578427.img
I got following error though:
Sending 'boot_a' (8493 KB) OKAY [ 0.130s]
Writing 'boot_a' (bootloader) Flashing Pack version b1c1-0.1-5578427
FAILED (remote: '(boot_a) No such partition')
fastboot: error: Command failed
Any suggestions on how to proceed?
gardeimasei said:
So I tried doing:
Code:
fastboot flash boot bootloader-blueline-b1c1-0.1-5578427.img
I got following error though:
Sending 'boot_a' (8493 KB) OKAY [ 0.130s]
Writing 'boot_a' (bootloader) Flashing Pack version b1c1-0.1-5578427
FAILED (remote: '(boot_a) No such partition')
fastboot: error: Command failed
Any suggestions on how to proceed?
Click to expand...
Click to collapse
That command flashes only the boot loader, not the factory image. The factory image and instructions for flashing are at https://developers.google.com/android/images
What android version were you on when you started? TWRP does not run on a Pixel 3 with Android 10.
Also, the boot partition is not the bootloader partition. Just run the flash-all script that google provides with the factory image download.
dcarvil said:
That command flashes only the boot loader, not the factory image. The factory image and instructions for flashing are at https://developers.google.com/android/images
What android version were you on when you started? TWRP does not run on a Pixel 3 with Android 10.
Click to expand...
Click to collapse
I was using Android 9. I tried running the flash-all script (i.e., follow the official instructions) but the fastboot commands would hang. Maybe I just didn't wait for long enough.
I wiped system,data,cache using TWRP following some online guide and now I can't boot into recovery mode. I can get into the bootloader menu though. When I try to boot into TWRP using:
Code:
fastboot boot twrp-3.3.0-0-blueline.img
I get the following error on the PC: Booting FAILED (remote: 'Error calling AvbLoadAndVerifyBootImages Load Error')
When I try to enter recovery mode the screen turns black indefinitely.
I still have the TWRP .win files from my backup on my PC. Is there a way out of this?
EDIT:
Weirdly, after trying the flash-all.sh script again it worked basically instantly. Possibly it took so long the first time i ran it because it was wiping data (which i then did manually).
Was able to get the factory image on there. Thanks a lot!