I can not leave the fastboot - X 2014 Q&A, Help & Troubleshooting

hi all just now try to install the firmware with RETAILBR but at the end saying "failed to validate system image" and below said "fastboot reason: fall through from the normal boot mode" and good at last I took hours trying out the fastboot and can not .:llorando:

The flash failed, so you either now likely have a corrupt OS or a nonexistent OS. Flash it properly and it will boot correctly.
Sent from my XT1095 using Tapatalk

friend if you were right, I arrange, thanks

Related

[Q] Stuck in bootloader after foolish attempt at flashing ROM

So being the hot headed fool that I am, I pretty much just upped and tried to flash a non-stock ROM onto my L90 D415 10c without reading enough about the process. I rooted with towelroot and got into the bootloader, then I thought that simply with an erase command and an update command my phone would just reboot with the new ROM on it, alas this was not true. What I did was
fastboot erase system
fastboot erase boot
After entering "fastboot update cmod.zip" there was a message:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
My phone is now stuck in the bootloader, what do I do? Is there any way to restore it's previous settings/memory?
The two "guides" that I followed (pretty much exactly) were first this and then this.
Last thing that seems like it may help is when I type "fastboot continue", my phone ends up with a message saying:
ERROR: Invalid boot image header
If anybody can solve this for me I would be eternally grateful. I've already learned my lesson, and I've got a feeling I'll be coming back to xda. For better reasons I hope. Thanks in Advance
EDIT: I guess I should add that I tried to flash the ROM in fastboot, which now that I think of it, I'm not sure is even possible? I do have my entire terminal history if that helps.
karlsin said:
So being the hot headed fool that I am, I pretty much just upped and tried to flash a non-stock ROM onto my L90 D415 10c without reading enough about the process. I rooted with towelroot and got into the bootloader, then I thought that simply with an erase command and an update command my phone would just reboot with the new ROM on it, alas this was not true. What I did was
fastboot erase system
fastboot erase boot
After entering "fastboot update cmod.zip" there was a message:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
My phone is now stuck in the bootloader, what do I do? Is there any way to restore it's previous settings/memory?
The two "guides" that I followed (pretty much exactly) were first this and then this.
Last thing that seems like it may help is when I type "fastboot continue", my phone ends up with a message saying:
ERROR: Invalid boot image header
If anybody can solve this for me I would be eternally grateful. I've already learned my lesson, and I've got a feeling I'll be coming back to xda. For better reasons I hope. Thanks in Advance
EDIT: I guess I should add that I tried to flash the ROM in fastboot, which now that I think of it, I'm not sure is even possible? I do have my entire terminal history if that helps.
Click to expand...
Click to collapse
Just follow my KDZ flashing guide and reflash kdz
http://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479
gdjindal said:
Just follow my KDZ flashing guide and reflash kdz
http://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479
Click to expand...
Click to collapse
The LG Mobile Support Tool doesn't recognize my phone. I followed the directions exactly (plugging the phone in after the first error message), but the same message appears after pressing retry.
karlsin said:
The LG Mobile Support Tool doesn't recognize my phone. I followed the directions exactly (plugging the phone in after the first error message), but the same message appears after pressing retry.
Click to expand...
Click to collapse
Power off the phone, pret volume up and insert USB cable . Now follow the guide.
Sent from my LG-D405 using XDA Free mobile app

Stuck at start of boot after flash-all.bat flash from android M preview

This time I tried the flash-all.bat file. I did not notice big problems during the flashing process, (it mentioned missing .sig files). When flash-all.bat finished, I scrolled up to Recovery using the volume keys, hit the power key, and the screen changed to the first part of the boot sequence, the black screen with Google at the top and a small unlocked lock sign at the bottom... And there it has set for the past hour
It does not seem to connect to the usb port anymore, so I don't know where I go from here.
I have flashed factory images on my Nexus 6 several times, including each of the recent developer previews. I always used the fastboot commands. The bootloader is unlocked; the phone is not rooted, it was running preview 3.
Uh, what next?
OK, I got back to the bootloader.
Now when I try to flash the files one at a time, I get:
Motobootreflash validation for aboot
preflash validation failed
failed remote failure
I tried to upgrade from Android M preview 3 to 6.0 Marshmallow using the flash-all.bat.
There were error messages and the phone would not boot into recovery.
I went back to fastboot to flash files one at a time.
When I try to flash bootloader it fails with the "Preflash validation error" message.
Is this telling me that I can't flash the bootloader because it was already flashed during the (unsuccessful) flash-all.bat?
Can I flash the other files to get the phone back to working order?
I was on preview 3 and used flash-all.bat to go to the official 6.0 image. No issues on my end, the missing boot sig message is normal, phone took about 5 min but booted up clean. You might want to try downloading the factory image again, maybe it was partially corrupted? Should be recoverable since you can still get into the bootloader and access fastboot.
Update: I kept trying to reflash changing one thing at a time, until I finally tried my old, tired laptop with an old fastboot.exe on it.
With the old software on the old computer, Marshmallow flashed normally using the command line.

Help, Can't leave bootloader. Flashed M system image

Hi,
I was unlocked and rooted and I tried using the NRT to flash the M system image. It worked and I got the phone to boot once. It went through the Android is upgrading process and I used it for a few seconds and then it froze. I rebooted it by holding the power button. It now will not leave the bootloader. When I try to start it just flashes back into the bootloader. In the BL log it says "failed to validate boot image: ref=-1" So I tried re-flashing both manually and in the NRT. This is the error I get when flashing
(bootloader) failed to write primary GPT
(bootlaoder) failed to flash partition
FAILED (remote failure)
Any help would be appreciated.
Thanks
Try fastboot erase before fastboot flash
-----_--------_--------_----------_---_--------_------------
....read......read more........think.........think more.......read...........read more........
Stop using a toolkit and do it manually https://developers.google.com/android/nexus/images?hl=en
I said that I did it both manually and with the toolkit. Sorry you feel that since I didn't want to type all that in you are better than me. I figured it out though. I couldn't get into any recovery so I used the toolkit to boot into the temporary twrp. Formatted all the partitions and got it to flash successfully.
From what I can tell it tried encrypting and it ruined the partitions.
My nexus 6 received the update by ota and I have experienced the same thing.... Tech support was no help telling me to go to a sprint store. I'm not sure what caused the issues here... My phone did the normal Android is upgrading thing and and I left I to do its thing it booted up and I used to it. Make a phone call. After the call my phone froze when I tried to open all apps. I restarted the phone in the same way the first post did. How ever my phone booted up to the new Android boot screen , however the phone restarted again and this time into the bootloader. Can anyone help me with this?

moto g 2nd gen stuck in fastboot mode

i tried rooting my android phone using the king root app but mid-rooting the phone went into the fastboot mode and whenever i try booting up the phone it says " hab check failed for boot
Failed to verify hab image boot
Failed to validate boot image
Fast boot Reason: Fall-through from normal boot mode"
ive tried factory reseting the phone and wiping the cache multiple times but it keeps saying that...please help thank you.
You'll have to reflash your rom, because it's corrupted. You can't root like this!
Written with my XT1068 using Tapatalk on CM13

Think I broke my bootloader flashing TWRP, stuck with no phone, need help!

I've on an older version of Android. I've never had a problem using TWRP on other phones but due to the lack of having it on my Pixel 4XL, I've just never had it.
I haven't upgraded in ages, I see we have a working TWRP now. I tried to flash it via Magik and I think I flashed the wrong one.
My phones stuck in a boot loop mode and IF I can get to the screen that says "fastboot mode", I cant do anything with it.
"adb devices" returns nothing so I cant even attempt to flash the correct recovery.
Help!
kdoggy said:
I've on an older version of Android. I've never had a problem using TWRP on other phones but due to the lack of having it on my Pixel 4XL, I've just never had it.
I haven't upgraded in ages, I see we have a working TWRP now. I tried to flash it via Magik and I think I flashed the wrong one.
My phones stuck in a boot loop mode and IF I can get to the screen that says "fastboot mode", I cant do anything with it.
"adb devices" returns nothing so I cant even attempt to flash the correct recovery.
Help!
Click to expand...
Click to collapse
When you get to the screen that says "fastboot mode", do "fastboot devices", not "adb devices". If that works, flash the boot image with "fastboot flash boot boot.img". Make sure the boot.img matches what you had on the phone before breaking it. Either the stock boot.img or magisk patched boot image should work, but you'll loose root with the stock boot.img.
It is best to boot TWRP without installing it. "fastboot boot twrp.img".
Hey.
Yeah check "fastboot devices". If you get something on terminal, use Google flash tool to reflash the original firmware, this will repair any damaged/corrupted file.
If you don't get anything your phone is very likely bricked. You can still try the emergency mode but I believe it won't work. In this case there is still a way to recover your phone, and it's using the EDL mode(which is contain in every phone that has a Qualcomm Chipset). From there you can force flash firmware and boot image.
Tell me how it goes
OK I got TWRP working.
Phones updated to September 2021, turned out I was still on March 2021! Anyway, all updated, rooted etc!
Thanks very much folks!
Nice
dcarvil said:
When you get to the screen that says "fastboot mode", do "fastboot devices", not "adb devices". If that works, flash the boot image with "fastboot flash boot boot.img". Make sure the boot.img matches what you had on the phone before breaking it. Either the stock boot.img or magisk patched boot image should work, but you'll loose root with the stock boot.img.
It is best to boot TWRP without installing it. "fastboot boot twrp.img".
Click to expand...
Click to collapse
Glad to know that my habit of fastboot booting twrp images on 2XL will keep me safe here on 4XL too

Categories

Resources