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.
Related
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.
Hello Everyone!
Recently i had bought and LG G3 that had been preloaded with lollipop. So i decided to root it and install customer recovery thank to the new BUMP'D method that had just been released. Little did i know that google was going to be the death of me. I had accidentally used an entirely different installer (one for the D855) along with deleting my recovery, boot, aboot, laf, etc. in order to try and fix the problem. I ended up with endless errors including the fastboot_mode_started error as well as the endless bootloop with error message: LG Security error. Not finding a well organized post for people to see i have taken it upon myself to induce black magic in order to bring your devices back from the dead.
All of this is thanks to @autoprimes thread in which some people like me try to cut corners and brick our phones.
Follow his thread carefully: http://forum.xda-developers.com/showpost.php?p=59331618&postcount=1720
What you want to do is obtain the appropriate images from @autoprime.
The ones that i needed were the aboot, laf, recovery, as well as the patched boot from method 1.
****IF you are stuck in continuous bootloop. you must remove battery then hold down and power at the same time, insert battery, when lg screen appears release and quickly press again. this will take time, it took me 5-10 times to get it running. this will break the boot cycle and may boot you into recovery if you havent already erased it (in my case). if you have you will boot into fastboot_mode_started. You must then proceed to place all of the files (aboot,laf,modded boot, recovery) in the same folder as adb and fastboot program folder.. use the cmd prompt and replace the original cmd lines with fastboot code, for instance:
To flash aboot i would type this:
adb shell
su
fastboot erase aboot
fastboot flash aboot aboot.img <----------This will be what ever the name of the file is
fastboot erase recovery
fastboot flash recovery recovery.img<----------This will be what ever the name of the file is
fastboot erase laf
fastboot flash laf laf.img<----------This will be what ever the name of the file is
fastboot erase boot
fastboot flash modded-boot.img<----------This will be what ever the name of the file is
fastboot reboot recovery
from there you can restart from recovery and boot system up.
Remember download appropriate drivers for the ATT LG G3 in order for this all to work. also google some info on quickly getting adb running as you will need it.
After this i was up and running with everything functioning as it should. TWRP and root were also functioning .
Ran "fastboot flash boot twrp.img" instead of "fastboot boot twrp.img"
When trying install TWRP for the first time on a new (to me) Pixel 3, after unlocking the bootloader I ran "fastboot flash boot twrp.img" instead of "fastboot boot twrp.img". Can still enter the bootloader, but anything else gives a black screen.
What is the best method to recover from this? I still have access while in the bootloader through fastboot. Should I reflash stock google images or is something else better to recover? If I should reflash the stock google images what is the best method to do so?
Yes after reading more I realize this was the wrong thing to do. "fastboot boot twrp.img" was not working so I figured to try flashing instead, but afterwards realized that was obviously wrong.
Thanks for any help.
OK, It looks that I am soft bricked and a factory image reset is the only way to recover.
The steps I've seen mostly commonly referenced are to run the following
Code:
fastboot erase system_a
fastboot erase system_b
fastboot erase boot_a
fastboot erase boot_b
fastboot reboot-bootloader
flash-all.bat (using the factory images)
The issue seems to be that Android 10 which was on the phone doesn't work with fastboot erase. Is it necessary to run this or is it OK to go straight to flash-all.bat? (BTW I finally figured out that my issue above was TRWP doesn't support android 10 yet, but the guides I saw were older and didn't mention that. )
twfry said:
When trying install TWRP for the first time on a new (to me) Pixel 3, after unlocking the bootloader I ran "fastboot flash boot twrp.img" instead of "fastboot boot twrp.img". Can still enter the bootloader, but anything else gives a black screen.
What is the best method to recover from this? I still have access while in the bootloader through fastboot. Should I reflash stock google images or is something else better to recover? If I should reflash the stock google images what is the best method to do so?
Yes after reading more I realize this was the wrong thing to do. "fastboot boot twrp.img" was not working so I figured to try flashing instead, but afterwards realized that was obviously wrong.
Thanks for any help.
Click to expand...
Click to collapse
First things first. TWRP does not work at all on a Pixel with Android 10. Flash-all should be all you need to do to recover from your issue.
sliding_billy said:
First things first. TWRP does not work at all on a Pixel with Android 10. Flash-all should be all you need to do to recover from your issue.
Click to expand...
Click to collapse
The 3 top guides from google all had steps for android 9 apparently and so I didn't catch that 10 is different..... flash-all.sh worked and we're back. Thanks!
I've got a BIG problem with my new Pixel 5. I've successfully rooted it and had it operating for a day.
I then decided to boot into recovery mode just to see what the new stock recovery looks like (I used to use TWRP.).
BIG MISTAKE!
All I got was the error icon that I've seen in the past meaning that no recovery image is available. OK, so I try to just try to do a simple reboot. I'm taken back to the same place.
Now I try to reload Android. No luck! I'm stuck on:
"Device product is 'unknown'"
Update requires 'bramble'.
HELP!!!!
In the file android-info.txt, what would happen if I patched the line
require board=bramble
to
require board=unknown
Did you figure this out? I'm facing the same issue with my Pixel 5.
Edit: I figured it out. If you are having an issue with the 'flash-all.bat' command like we were, you just need to manually push the individual files and it should boot you back up into stock.
Run these commands:
1. fastboot flash bootloader <bootloader image file>
2. fastboot reboot-bootloader
3. fastboot flash radio <radio image file>.img
4. fastboot reboot-bootloader
5. fastboot update <image zip file>.zip
6. fastboot reboot
All of the reboot-bootloader commands may be redundant but it worked for me. It booted me into stock, verified I was unrooted with Root Checker, then proceeded to reboot back into the bootloader and 'fastboot flashing lock' to re-lock my bootloader and wipe the device.
Merry Christmas guys,
I have a really unusual situation.
First time that I have tried all tricks I know and I can't get myself out of this difficult situation.
I was trying to update Magisk with a patched boot file and after a reboot I was not being able anymore to access the system but only this black screen with the Crashdump Mode is appearing.
I can access the Fastboot screen, but no way to reboot to the TWRP recovery or to flash another boot.img, even through some pc flashing utilities.
Is there anything to try through another slot or something else?
I also tried:
fastboot flash boot_a boot.img
and I get this error:
FAILED (remote: Flashing is not allowed for Critical Partitions)
But my bootloader is unlocked and other commands like fastboot reboot works normally.
After I flashed through fastboot the images of boot, abl, dtbo, fw I can only access the TWRP recovery where everything is decrypted.
Any other ideas?
Try booting temporary into TWRP by using this command
fastboot boot twrp.img
If you can't use MSMDownloadTool