Database Users

Stuck in AP Fastboot It says Load kernel (boot) failed Fastboot Reason: Boot Failure

Hi all
Well I bricked my phone and I'm stuck in AP Fastboot. When I try to start the phone (boot it up from off) It gets as far as the M logo then enters AP fastboot or it might even go directly to fastboot.
What I was doing: I was trying to use Matt's Droid RAZR M utility 1.20 option 1 to go back to stock 4.1.2. That's when my problems started. I had nearly 70% battery when i started (now it says "low battery").
Phone set up: Droid RAZR M 4.1.2; Rooted; Locked bootloader; Safestrap 3.12 and backed up; stock slot was still stock and ROM slot 1 was running Eclipse Custom ROM. To be honest I cant remember if i was back in stock ROM slot or ROM slot 1 when I attempted to use Matt's Utility. And I didn't uninstall Safestrap nether prior to using the utility. Don't know how much those factors played into causing my problem.
What I have tried: I have tried RSD Lite 6.1.4 with xml.zip files from the Droid-Developers SBF web site. But i keep getting this fail message, "Failed flashing process. 1/19 flash partition "gpt_main0.bin" -> Phone returned Fail."
I have tried manually pushing the recovery.img, boot.img and system.img file onto the phone via cmd.exe and it fails with this message for all three attempts, "Battery Low!!" "FAILED (remote failure)".
I have tried Matt's Utility option 1 I get multiple fail messages, "Failed to erase partition", "FAILED (remote failure)", "Failed to flash partition boot", "Failed to write mmc".
I even purchased one of Team Black Hats Factory Programing Adapters (little red adapter) That acts like a factory programing cable (they said they don't sell the cable any more cause the red adapter does the same thing for cheaper).
With the adapter connected I still get the same fail messages in RSD Lite, Matt's Utility, and cmd.exe prompt. I was under the impression that the factory programing cable (adapter) would solve my low battery issue.
Any help would be great. Thank you in advance.
PS: Also, I did not take the last OTA update from a few weeks ago. I was planning to unlock my bootloader. And my computer is a Windows XP (sp3). Thanks Again.

SARM1084 said:
Hi all
Well I bricked my phone and I'm stuck in AP Fastboot. When I try to start the phone (boot it up from off) It gets as far as the M logo then enters AP fastboot or it might even go directly to fastboot.
What I was doing: I was trying to use Matt's Droid RAZR M utility 1.20 option 1 to go back to stock 4.1.2. That's when my problems started. I had nearly 70% battery when i started (now it says "low battery").
Phone set up: Droid RAZR M 4.1.2; Rooted; Locked bootloader; Safestrap 3.12 and backed up; stock slot was still stock and ROM slot 1 was running Eclipse Custom ROM. To be honest I cant remember if i was back in stock ROM slot or ROM slot 1 when I attempted to use Matt's Utility. And I didn't uninstall Safestrap nether prior to using the utility. Don't know how much those factors played into causing my problem.
What I have tried: I have tried RSD Lite 6.1.4 with xml.zip files from the Droid-Developers SBF web site. But i keep getting this fail message, "Failed flashing process. 1/19 flash partition "gpt_main0.bin" -> Phone returned Fail."
I have tried manually pushing the recovery.img, boot.img and system.img file onto the phone via cmd.exe and it fails with this message for all three attempts, "Battery Low!!" "FAILED (remote failure)".
I have tried Matt's Utility option 1 I get multiple fail messages, "Failed to erase partition", "FAILED (remote failure)", "Failed to flash partition boot", "Failed to write mmc".
I even purchased one of Team Black Hats Factory Programing Adapters (little red adapter) That acts like a factory programing cable (they said they don't sell the cable any more cause the red adapter does the same thing for cheaper).
With the adapter connected I still get the same fail messages in RSD Lite, Matt's Utility, and cmd.exe prompt. I was under the impression that the factory programing cable (adapter) would solve my low battery issue.
Any help would be great. Thank you in advance.
PS: Also, I did not take the last OTA update from a few weeks ago. I was planning to unlock my bootloader. And my computer is a Windows XP (sp3). Thanks Again.
Click to expand...
Click to collapse
http://www.droidrzr.com/index.php/t...not-going-into-recovery-no-os-on-phone/page-2
Found by
https://www.google.com/search?num=1...j1.6.0....0...1c.1.26.serp..6.0.0.Dd8aoiu_UJI

Thank you for offering help. Will try your suggestions.
Sent from my XT907 using Tapatalk 2

[SOLVED] I was able to get some more help on another forum. My problem was a corrupted utility. I was instructed to perform a md5 check sum on my version if Matts utility. I compared my results to the original file on batakang Web site. That's when I realized my file was no good. So I deleted it an downloaded a clean uninterrupted copy of Matts utility 1.20 and it worked perfectly. I hope this will help other people too. Thanks for your help my friend.
Sent from my XT907 using Tapatalk 2

[Q] nexus 7 bricked, cant restore

So I was running cynogenmod on my nexus 7 2012, and now that lollipop is out, I wanted to do a complete restore of my device and install stock. I first tried a few one click methods, but none of those worked, so I tried using the android sdk to install it through the command prompt. After a long struggle, I gave up and tried to turn my device back on, but it says "booting failed" in the upper right corner, and it doesnt get past the google screen. I can get to fastboot no problem, but I cant get into my recovery(which I am guessing got wiped). When I tried to reinstall stock again, every method i tried got stuck on trying to flash the bootloader. Is my device permanently bricked? If its not how can I fix it? thanks

See this. The Lollipop LRX21P factory image also has a borked bootloader file.
Replace the file "bootloader-grouper-4.23.img" with a valid version from the JWR66V, KRT16O, or KRT16S factory images and try again.
(actually, if you already have the 4.23 bootloader there is no need to flash the bootloader; you could edit the "flash-all.bat" file and remove the bootloader flash and reboot-bootloader lines).
Consider yourself lucky you still can get to fastboot.

bftb0 said:
See this. The Lollipop LRX21P factory image also has a borked bootloader file.
Replace the file "bootloader-grouper-4.23.img" with a valid version from the JWR66V, KRT16O, or KRT16S factory images and try again.
(actually, if you already have the 4.23 bootloader there is no need to flash the bootloader; you could edit the "flash-all.bat" file and remove the bootloader flash and reboot-bootloader lines).
Consider yourself lucky you still can get to fastboot.
Click to expand...
Click to collapse
Yea in fastboot it says that the bootloader version is 4.23. Ill try flashing it without the bootloader and see if that works

ok so I tried running the flash-all.bat, and it says archive does not contain boot.sig, and archive.sig. Then, it continues flashing, but after it gets to sending boot, I get an error that says FAILED(data transfer failure (unknown error)). then When I try to do something on the nexus it is frozen, and I have to hold power and volume down to get back into fastboot. Am I missing the boot and archive files?

ok so I reinstalled the android sdk and then flashed the image and it worked. There must have been some files missing or something. Thanks for your help!

No Recovery

I think i made i grave mistake. I want to upgrade my p9 lite to nougat so I decided to unroot my phone. The unrooting is successful with the device still booting. So next thing i want is to flash back my stock recovery so I can update my phone through OTA (this is where I made a mistake.) I tried doing it by flashing a full MM Rom that i got directly from huawei through dload method. The flashing went smoothly or so I thought. My phone got stuck in a boot loop and I cant seem to access recovery. eRecovery is also inaccessible so I tried reflashing the full MM Rom through dload method but I can't get it to work anymore. I tried it several times with no luck. I also tried reflashing meticulus' twrp through fastboot method but I always get an error saying "remote command not allowed". The bootloader is still unlock btw.
Someone help me. I don't know what to do anymore... :crying:

NikkoVicedo said:
I think i made i grave mistake. I want to upgrade my p9 lite to nougat so I decided to unroot my phone. The unrooting is successful with the device still booting. So next thing i want is to flash back my stock recovery so I can update my phone through OTA (this is where I made a mistake.) I tried doing it by flashing a full MM Rom that i got directly from huawei through dload method. The flashing went smoothly or so I thought. My phone got stuck in a boot loop and I cant seem to access recovery. eRecovery is also inaccessible so I tried reflashing the full MM Rom through dload method but I can't get it to work anymore. I tried it several times with no luck. I also tried reflashing meticulus' twrp through fastboot method but I always get an error saying "remote command not allowed". The bootloader is still unlock btw.
Someone help me. I don't know what to do anymore... :crying:
Click to expand...
Click to collapse
The bootloader appears unlocked, and says so, but it's not...I encountered the same situation with my colleagues device, you need to unlock it either way(careful this will wipe all your data if on nougat, but if on MM after unlocking keep phone connected to PC as it reboots and quickly press vol down+ power to get back to bootloader In order to flash TWRP, this will preserve your data partition and system), and try again, you need format that data partition by using changing format to f2fs then ext4...after this reboot, if it can't, reinstall the file In dload folder and go to stock recovery(disconnect phone from PC to do this if it fails) and do a factory reset.
.... if this fails, debrand And install MM or NOUGAT for your newly debranded system.
If this fails, which is highly unlikely,PM for un orthodox methods.
_New World Order (NWO)_

daner[email protected] said:
The bootloader appears unlocked, and says so, but it's not...I encountered the same situation with my colleagues device, you need to unlock it either way(careful this will wipe all your data if on nougat, but if on MM after unlocking keep phone connected to PC as it reboots and quickly press vol down+ power to get back to bootloader In order to flash TWRP, this will preserve your data partition and system), and try again, you need format that data partition by using changing format to f2fs then ext4...after this reboot, if it can't, reinstall the file In dload folder and go to stock recovery(disconnect phone from PC to do this if it fails) and do a factory reset.
.... if this fails, debrand And install MM or NOUGAT for your newly debranded system.
If this fails, which is highly unlikely,PM for un orthodox methods.
_New World Order (NWO)_
Click to expand...
Click to collapse
The problem is I cannot access recovery anymore. After trying to flash back full rom from huawei, i cannot access recovery anymore no matter how hard i try. eRecovery is also not accessible so i cannot turn off my phone. I tried flashing twrp trough fastboot i keep getting an error saying "remote command not allowed". Dload method is not working anymore. If only I can find a way to flash twrp, then I can restore the dump i made using meticulus' twrp.

NikkoVicedo said:
The problem is I cannot access recovery anymore. After trying to flash back full rom from huawei, i cannot access recovery anymore no matter how hard i try. eRecovery is also not accessible so i cannot turn off my phone. I tried flashing twrp trough fastboot i keep getting an error saying "remote command not allowed". Dload method is not working anymore. If only I can find a way to flash twrp, then I can restore the dump i made using meticulus' twrp.
Click to expand...
Click to collapse
Assuming that you have the unlock code, what happens if you try unlock bootloader again irrespective what status it is now?
_New World Order (NWO)_

[email protected] said:
Assuming that you have the unlock code, what happens if you try unlock bootloader again irrespective what status it is now?
_New World Order (NWO)_
Click to expand...
Click to collapse
It shows in fastboot that the phone is unlocked with frp locked. Unlocking it again through fastboot is not possible since I always get an error saying remote command not allowed.

NikkoVicedo said:
It shows in fastboot that the phone is unlocked with frp locked. Unlocking it again through fastboot is not possible since I always get an error saying remote command not allowed.
Click to expand...
Click to collapse
Hi guys, i Got the SAAAAAME Problem, this is all about what i PMd to you danerrickcuba FRP lock and bootloader unlocked. can't go to recovery, but has access to fastboot and wasn't able to do anything to fastboot.

Already fixed my phone. Had to pay 15 euros for DC Phoenix (this software saved me from bringing my phone to huawei service center to have it fix. Thank god!) so I can fix my phone. Recovery, eRecovery, Dload method working, and relocked bootloader. Currently updating my phone through OTA. Tnx danerrickcuba for suggesting methods to fix my phone....

NikkoVicedo said:
It shows in fastboot that the phone is unlocked with frp locked. Unlocking it again through fastboot is not possible since I always get an error saying remote command not allowed.
Click to expand...
Click to collapse
i have the same problem
bootloader unlock and frp lock ,bootlooping,rec&e-rec destoryed
if you do not log out google /shut down "find my phone"/check oem-unlock in developer mode before downgrading or flashing ,you will get "frp lock" warning
bootlooping may come from wrong update.app. eg. i use dload method to flash rollback(5.0-B300) pkg in EMUI4.1 , my rec and e-rec are destoryed
however, i think fastboot command could do nothing to "bootloader unlock ,frp lock,rec and e-rec destoryed ". i do not know how DC-phoenix fix this and i pay a new motherboard for my mistake

try https://forum.xda-developers.com/showpost.php?p=71338813&postcount=29

Can anyone help me fix my Axon 7.

I tried to unlock my phone (A2017G) and flash lineage OS today following Controllerboys guide, but must have done something wrong, I managed to unlock it and flash the bootstack, but I hit an error when trying to flash LOS and so decided to reboot the system and try again, however when rebooting the system I got the error "Your device software can't be checked for corruption, Please lock the bootloader". And I cant seem to access TWRP anymore just the stock recovery.
Is there a way that I can just flash stock OS and be able to use my phone?

King Norman said:
I tried to unlock my phone (A2017G) and flash lineage OS today following Controllerboys guide, but must have done something wrong, I managed to unlock it and flash the bootstack, but I hit an error when trying to flash LOS and so decided to reboot the system and try again, however when rebooting the system I got the error "Your device software can't be checked for corruption, Please lock the bootloader". And I cant seem to access TWRP anymore just the stock recovery.
Is there a way that I can just flash stock OS and be able to use my phone?
Click to expand...
Click to collapse
That's not an error message, it's the unlocked bootlaoder screen. get used to it, you're gonna see it every time you reboot
You probably didn't flash the Universal Bootloader. You didn't even read. You should install TWRP again with axon7tool, then get there and flash the Universal Bootloader, then the A2017G modem, the the ROM. If that doesn't work just download MiFlash and the latest G package and flash it

I ****ed up while using fastboot. I need help.

I'm afraid I ****ed something up.
My phone bootloops and the only way to reboot correctly is to do "fastboot boot boot.img" with the STOCK boot.img (which can be found here : https://drive.google.com/drive/u/0/folders/0B7F3ZXr565GkUU5iYjJtLXE2STQ)
Also I am not able to flash anything on the phone.
TWRP says "Error executing updater binary in zip...", and when I attempt to flash something through ADB Sideload, i get "Cannot read zip".
How can I fix everything? I guess I flashed something wrong trough fastboot but I'm not even sure what.

Also I found out that my bootloader was still locked.
But I can't unlock it since I am on Lollipop and the ASUS Unlock Tool is for Android M (I get error when i install the apk).
So I would flash Android M to unlock bootloader but hey, I can't flash anything....

I kinda fixed it, atleast I can now boot normally.
I followed this tutorial by @MiauLightouch : https://forum.xda-developers.com/showpost.php?p=66364620&postcount=8
And now I can boot without using fastboot.
Still unable to flash stuff using TWRP though.