HI
I was flashing the GPe image on my XT1033 and while flashing the boot.img and logo.bin i got an error - out of memory , but rest of the parts like system.img etc flashed properly and now my phone won't boot giving me the error "failed to validate boot image'.
I am stuck at the bootloader screen and now neither can i flash some other image since my phone isn't being recognized anymore with cmd showing the message 'waiting for device'
Can someone please provide a solution?
Hello.
I faced the same problems when installing the 4.4.4 br firmware and trying to revert to my original firmware.
This happens because you have a locked bootloader and/or maybe you flashed a wrong boot.bin and you can't reflash boot.img because the bootloader is locked!
What I did is unlock the bootloader and all my problems vanished.. -_- reflash all the files using mfastboot, if it gives you errors on gpt.bin and motoboot.img dont worry and go on with the rest.
Oh, and one strange thing that I luckily figured out, is that to get the device recognized by the PC in the fastboot mode you got to enter fastboot MANUALLY. THat is, press volume down 3 seconds and then power on.
It's gotta say: Fastboot reason: Volume-down key pressed.
If you try to boot and it enters fast boot and gives you the error, for some reason doesn't recognize.
Related
Hey Guys,
I rooted my device a while ago and everyday had to dismiss the OTA update for the last few months. The other night I accidentally accepted the OTA and know my phone is stuck in a bootloop when connected to power. I'm occasionally able to get into Fastboot mode for RSD to see the phone, ADB will not see the phone. When I attempt to select Recovery or Factory the phone bootloops. I have also tried House of Moto and that didn't work.I have tried flashing all the files located at sbf with no luck. In Fastboot the Device is listed as UNLOCKED with a Status Code: 1.
Any help will be greatly appreciated.
When I flash using House of Moto I get an error for the following:
gpt.bin
motoboot.img
logo.bin
boot.img
recovery.img
system.img
NON-HLOS.bin
uniqueflips said:
Hey Guys,
I rooted my device a while ago and everyday had to dismiss the OTA update for the last few months. The other night I accidentally accepted the OTA and know my phone is stuck in a bootloop when connected to power. I'm occasionally able to get into Fastboot mode for RSD to see the phone, ADB will not see the phone. When I attempt to select Recovery or Factory the phone bootloops. I have also tried House of Moto and that didn't work.I have tried flashing all the files located at sbf with no luck. In Fastboot the Device is listed as UNLOCKED with a Status Code: 1.
Any help will be greatly appreciated.
When I flash using House of Moto I get an error for the following:
gpt.bin
motoboot.img
logo.bin
boot.img
recovery.img
system.img
NON-HLOS.bin
Click to expand...
Click to collapse
Does it ever actually boot up and then just restarts? Or are you never getting to the homescreen?
no home screen
Hi,
It won't even boot loop unless it's connected to power. When it is it just boot loops, tried everything but can't get past the boot loop. Spent countless hours trying to make any progress.
try flashing TWRP from fastboot
Code:
fastboot erase recovery
fastboot flash recovery name.img
if you get into recovery try restoring a nandroid
if that doesnt work, make sure you are flashing the appropriate SBF from the update you were in teh process of taking. My bet is somehow your device got partially updated (bootloader) so you are now unable to flash the SBF you were prevously on. ie. you were on 4.2.2, and took the 4.4 update, you need to flash the SBF for 4.4, not 4.2.2
Once you get back up and running, make sure you disable the Moto OTA app using titanium or the like. That should prevent the phone from trying to take an update again.
Still no luck
Thanks everyone for the suggestions, I'm not sure which firmware it was trying to install so I installed all the firmwares available via House of Moto and still no luck. Tried performing a Full and Keep Data and still the phone will continue to boot loop. One thing I did notice during the install using House of Moto I see the following error multiple times:
(bootloader) Variable not supported!
I got this error on all 5 firmwares.
Any ideas...
uniqueflips said:
Thanks everyone for the suggestions, I'm not sure which firmware it was trying to install so I installed all the firmwares available via House of Moto and still no luck. Tried performing a Full and Keep Data and still the phone will continue to boot loop. One thing I did notice during the install using House of Moto I see the following error multiple times:
(bootloader) Variable not supported!
I got this error on all 5 firmwares.
Any ideas...
Click to expand...
Click to collapse
what version of android were you on prior to this happening. What version was the OTA attempting to update you to?
I think I was on Android 4.4 Blur_Version.19.5.3.obake_verizon.Verizon.en.US, not 100% sure what it was trying to install 4.4.4 or 4.4 19.6.3.
Tried House of Moto again and on the 4.2.2 12.15.15 and 4.4.4 I don't get the (bootloader) Variable not supported! error. The phone still boot loops.
uniqueflips said:
I think I was on Android 4.4 Blur_Version.19.5.3.obake_verizon.Verizon.en.US, not 100% sure what it was trying to install 4.4.4 or 4.4 19.6.3.
Tried House of Moto again and on the 4.2.2 12.15.15 and 4.4.4 I don't get the (bootloader) Variable not supported! error. The phone still boot loops.
Click to expand...
Click to collapse
have you tried with the latest version of RSD lite?
If so make sure you edit the XML file to remove the part about erasing userdata
lets try this too... go to sbf.droid-developers.org and download this file for the maxx "Android 4.4.4
Blur_Version.21.11.21.obake_verizon.Verizon.en.US"
Install the latest moto device manager and RSD lite, then try flashing (might erase userdata)
If that does not work, you can manually flash each file in fastboot, lmk if any of that works
last Q, do you have a motorola factory cable?
Tried with and without removing the getvar file and no luck, still stuck in an endless boot loop when connected to power. ADB still doesn't see the device even in Fastboot mode. Never flashed each file in fastboot individual doesn't that require ADB?
uniqueflips said:
Tried with and without removing the getvar file and no luck, still stuck in an endless boot loop when connected to power. ADB still doesn't see the device even in Fastboot mode. Never flashed each file in fastboot individual doesn't that require ADB?
Click to expand...
Click to collapse
no you dont use adb from fastboot, you use "fastboot"
Lets see if we can get you booted to a recovery. Download this file, save it as recovery.img in your ADB directory.
boot to fastboot and run this command to determine fastboot sees the device
Code:
fastboot devices
If you see your device, then run the next command
Code:
fastboot flash recovery recovery.img
then try to boot to recovery. post result (make sure when you highlight "recovery" in fastboot you use volume up to select it. I just made the mistake of using power and my phone wouldnt boot to recovery)
Hi to XDA comunity
... and happy festive season
I tried to install a new ROM. So, I followed tutorials and I have a huge problem
I passed to unlock the tablet
But, when I tried to install the new Recovery, the installation failed and now, the tablet doesn't want to boot
When I boot normaly, in recovery mode or Fastboot mode, I get this message :
Code:
Bootloader Version JB-653b3d3 (Unlock Mode)
Entering boot menu mode
Booting failed
Bootloader VJB-653b3d3(UnlockMode): Starting Fastboot USB download protocol
When I send "Fastboot device", the device is shown
When I send "Fastboot flash recovery twrp-2.6.3.0_a700.img"
Code:
sending 'recovert' <5736 KB>...
But still indefinitely
So I stop and retry and I obtain
downloading 'boot.img'...
FAILED <commande write failed <Unknow error>>
finished. total time: 0.???s
i tried to erase recovery and retry.
Tried with several USB cables.
I don't know what to do...
I guess it's a fastboot problem ? How can I found a fastboot file ?
Thanks for any help !
grimnnir said:
Hi to XDA comunity
... and happy festive season
I tried to install a new ROM. So, I followed tutorials and I have a huge problem
I passed to unlock the tablet
But, when I tried to install the new Recovery, the installation failed and now, the tablet doesn't want to boot
When I boot normaly, in recovery mode or Fastboot mode, I get this message :
Code:
Bootloader Version JB-653b3d3 (Unlock Mode)
Entering boot menu mode
Booting failed
Bootloader VJB-653b3d3(UnlockMode): Starting Fastboot USB download protocol
When I send "Fastboot device", the device is shown
When I send "Fastboot flash recovery twrp-2.6.3.0_a700.img"
Code:
sending 'recovert' <5736 KB>...
But still indefinitely
So I stop and retry and I obtain
downloading 'boot.img'...
FAILED <commande write failed <Unknow error>>
finished. total time: 0.???s
i tried to erase recovery and retry.
Tried with several USB cables.
I don't know what to do...
I guess it's a fastboot problem ? How can I found a fastboot file ?
Thanks for any help !
Click to expand...
Click to collapse
make sure you have the a700 and not the a701 or a510 etc etc....
also, you could try booting directly into fastboot:
1. power off
2. hold power and volume down, while you're doing that, constantly change the rotation switch from lock unlock lock unlock.... keep doing it for about 5 seconds
try flashing from here... it might give you the same result but worth a try.
other possible problems:
1. the recovery you downloaded is corrupt
2. the recovery you downloaded was not a working version
3. you might not have the right usb drivers installed
4. you might have used the wrong recovery commands
5. command (sometimes) needs to be Run as Administrator on Windows (right click)
6. you might have waited too long to reboot to recovery, or used the wrong method to do it
it might make it easier for you if you just rename recovery on computer to recovery.img (so you can just type fastboot flash recovery recovery.img)
also, I have uploaded a copy of the recovery I'm using (it's newer)
you can also try (while in fastboot)
Code:
fastboot boot twrp.img
(or any custom recovery)
It should boot without flashing, and from there you're will be able to flash firmware, ROM, etc...
Shreps said:
you can also try (while in fastboot)
Code:
fastboot boot twrp.img
(or any custom recovery)
It should boot without flashing, and from there you're will be able to flash firmware, ROM, etc...
Click to expand...
Click to collapse
it might be fine but personally I would not try that... recovery and boot are not to be confused and bootloaders are not to be messed with
I would like to tell you my problem, I have a Mate 9 MHA-L09C432B368.
After several attempts and letting the battery drain I could enter Fastboot mode, I have the FRP unlocked and I could unlock the bootloader again, the problem is that I can not enter either the TWRP, or to recovery mode, try flashing again the same TWRP I had installed it well but still when I want to enter after passing the Huawei logo it remains on the white screen of ERROR MODE, Func NO: 11 (recovery image) Error NO: (image Failed!) Reading other forums and looking I have been told a lot by Internet that it is necessary to make the Dload method try it but it did not work, I understand that it does not work in this model but I still try it.
I also did a flash with all the files as I found in XDA
"When you have system extracted, flash it in fastboot using fastboot flash system system.img.
Do the same with KERNEL, extract and flash to fastboot flash kernel KERNEL.IMG
(BOOT is now split into RAMDISK and KERNEL)
Recovery was split to recovery_ramdisk, recovery_vendor and recovery_vbmeta
Boot was split into ramdisk and kernel
Recovery2 (erecovery) was split into erecovery_ramdisk, erecovery_kernel, erecovery_vendor and erecovery_vbmeta
fastboot flash ramdisk ramdisk.img. Kernel flashed as fastboot flash kernel kernel.img.
Recovery ramdisk as fastboot flash recovery_ramdisk recovery_ramdisk.img "
I'm still stuck on the same screen with error 11 and 2 I made the flash of the recovery that I used when I put version 368 are two MHA_RECOVERY_NoCheck.img and MHA_RECOVERY2_NoCheck.img both give Failed using the command Fastboot flash recovery_ramdisk RECOVERY_XXXX with both the same without using the _ramdisk command is equal I'm still stuck in the same state.
Does anyone have an idea that another method I can try?
I will thank you very much.
You can flash all * .img through ADB and in this case there is a specific order to do it, check several threads but I did not get an answer and search but I could not find anything, it is worth noting that when I flash files I mentioned before all OKAY but on power up it goes back to error 11 and 2 I have been told that it is a partition problem but I could not find something to recover them, there is some method that is missing or maybe an error in the steps I am doing ? I still can not access the TWRP but I can access without problems by ADB.
Help
Hello how are you. I had the same problem, I could not access to erecovery or recovery and worse to the system. only ERROR MODE appeared on the screen, Func NO: 11 (recovery image) Error NO: (image Failed!) .. could enter fastboot mode. with PHONE Unlocked and FRP Unlock but I took it to the official technical service of my country and they told me that it had no solution. at the time of testing on my computer I was left with PHONE Relocked and FRP lock in the fastboot. I have the code of my Bootloader and the FRP even though I can not unlock it to install files to my phone. help
hybrid09 said:
I would like to tell you my problem, I have a Mate 9 MHA-L09C432B368.
After several attempts and letting the battery drain I could enter Fastboot mode, I have the FRP unlocked and I could unlock the bootloader again, the problem is that I can not enter either the TWRP, or to recovery mode, try flashing again the same TWRP I had installed it well but still when I want to enter after passing the Huawei logo it remains on the white screen of ERROR MODE, Func NO: 11 (recovery image) Error NO: (image Failed!) Reading other forums and looking I have been told a lot by Internet that it is necessary to make the Dload method try it but it did not work, I understand that it does not work in this model but I still try it.
I also did a flash with all the files as I found in XDA
"When you have system extracted, flash it in fastboot using fastboot flash system system.img.
Do the same with KERNEL, extract and flash to fastboot flash kernel KERNEL.IMG
(BOOT is now split into RAMDISK and KERNEL)
Recovery was split to recovery_ramdisk, recovery_vendor and recovery_vbmeta
Boot was split into ramdisk and kernel
Recovery2 (erecovery) was split into erecovery_ramdisk, erecovery_kernel, erecovery_vendor and erecovery_vbmeta
fastboot flash ramdisk ramdisk.img. Kernel flashed as fastboot flash kernel kernel.img.
Recovery ramdisk as fastboot flash recovery_ramdisk recovery_ramdisk.img "
I'm still stuck on the same screen with error 11 and 2 I made the flash of the recovery that I used when I put version 368 are two MHA_RECOVERY_NoCheck.img and MHA_RECOVERY2_NoCheck.img both give Failed using the command Fastboot flash recovery_ramdisk RECOVERY_XXXX with both the same without using the _ramdisk command is equal I'm still stuck in the same state.
Does anyone have an idea that another method I can try?
I will thank you very much.
You can flash all * .img through ADB and in this case there is a specific order to do it, check several threads but I did not get an answer and search but I could not find anything, it is worth noting that when I flash files I mentioned before all OKAY but on power up it goes back to error 11 and 2 I have been told that it is a partition problem but I could not find something to recover them, there is some method that is missing or maybe an error in the steps I am doing ? I still can not access the TWRP but I can access without problems by ADB.
Click to expand...
Click to collapse
I think I can help the same happened to me. Is FRP still unlocked?
Re: I stuck with my Mate 9 Error mode numbers 11 and 2
Newrooter22 said:
I think I can help the same happened to me. Is FRP still unlocked?
Click to expand...
Click to collapse
Hi my phone have bootloader and FRP unlocked you can fix your phone for this error mode 11 and 2 ?
I wanted to ask please if this Thread can be closed since I could solve the problem, I share the solution which I obtained through a partner of the website HTC Mania @rodrigocarlosqm to which I am immensely grateful. Thanks to your generosity I was able to recover my phone and I do not want as a paperweight, the arrangement was simple buy credits in dc phoenix, in my case download the official version oreo 368, extract the update.app file and place it in the flashing program, restart the cell phone, in case it does not do so automatic do not panic turn it off and let it turn on normally, enter the recovery stock, make a wipe, then restart and return to the recovery in this case make a wipe hard reset, restart and terminate once that happens the phone it will restart again and once this is done, the operating system will start without any inconvenience. Thank you very much to everyone who helped with the help and ideas. I could find the result and I would like to thank @rodrigocarlosqm again, he was the one who helped me recover the brick he had. For all those who are in the same situation please I hope you can solve it before any query is at your disposal. Thank you all.
Hi all -
I have committed a stupid typo that has locked up my device: I just unlocked my bootloader and everything was working fine. I wanted to change the boot image so I don't get the "Bad Key" message at the bottom of the initial boot screen.
Unfortunately, in fastboot mode I typed:
Code:
fastboot flash boot logo.bin
instead of
Code:
fastboot flash logo_a logo.bin
Now a normal system boot fails and the device goes into fastboot with the message "Invalid boot image size! failed to validate boot image"
I am able to boot to TWRP by issuing the command
Code:
fastboot boot twrp-3.5.0_9-0-river.img
but I have no idea what to do after that.
How do I fix this?
After finding this thread:
Back to Stock & ReLock Boot Loader (Google Fi)
I wound up getting the $150 deal from google for the G7, had massive issues with the phone, so back to google with it. If you are curious the issues I had included: Speaker would randomly stop working, seriously I'd reboot, it would work, the...
forum.xda-developers.com
I have a possible path forward.
I am downloading the XT1962-1_RIVER_RETUS_9.0_PPO29.114-16_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip file (it's huge).
Then I will then extract the boot.img file and do a
Code:
fastboot flash boot boot.img
and see what happens.
Edit: I will wait a while first and see if any gurus have some better advice
I ended up just doing a factory reset from fastboot.
I was trying to upgrade my OP6 from the latest OOS 11 beta to a custom ROM.
I made sure the bootloader was unlocked, USB debugging enabled, backed everything up and rebooted into fastboot mode.
I flashed TWRP using "fastboot flash boot TWRP.img" and rebooted. I now see the above message when I try to boot. I've tried the MSM tool, but that hangs on "param preload" and shows no progress bar. I also tried flashing the fastboot ROM using flash-all.bat (which has helped me in the past), and extracting and flashing the boot.img file using payload dumper. I also trieda droidwin guide for restoring it to stock using fastboot commands one by one, but I can't flash critical partitions even after re-locking and unlocking using unlock critical. fastboot says secure boot is enabled.
I've been researching and trying everything all day, I haven't found anything successful, so I'm feeling pretty defeated. I can boot into fastboot and execute commands, and flashing boot.img and rebooting into recovery gives me "wiping, please wait" and hangs at 99%, and ADB devices shows it as "unauthorized."
edit: Now flashing boot.img and rebooting into recovery gives me a black screen.
edit 2: I fixed it by following this (https://www.droidwin.com/restore-oneplus-6-stock-via-fastboot-commands/) tutorial and just ignored the critical partitions errors. I think flashing the vendor is what fixed it, but I'm not sure.