Hello!
I'm trying to fix a LG G4 that goes straight into fastboot mode when it's powered up.
I've tried several things:
1. Holding power + volume down. It goes into recovery mode but when I click yes to restoring everything, it automatically takes me back to the same fastboot screen.
2. I've installed Android-SDK and updated drivers when I plugged in the phone. When I put in 'adb devices', there is nothing. When I put in 'fastboot devices', the serial number shows up. The bootloader is locked and when I put in 'adb reboot bootloader', it says 'error: no devices/emulators found'. Then I tried both 'fastboot oem unlock' and 'fastboot flashing unlock', it gives me: 'FAILED <command write failed <Unknown error>>.
3. I've downloaded TWRP but it obviously does not do anything right now with my errors.
I unplugged the phone from the computer and now it says 0% battery, it does not charge.
I'm really confused and lost at what to do. Any help would be appreciated.
Thank you in advance!
JennV123 said:
Hello!
I'm trying to fix a LG G4 that goes straight into fastboot mode when it's powered up.
I've tried several things:
1. Holding power + volume down. It goes into recovery mode but when I click yes to restoring everything, it automatically takes me back to the same fastboot screen.
2. I've installed Android-SDK and updated drivers when I plugged in the phone. When I put in 'adb devices', there is nothing. When I put in 'fastboot devices', the serial number shows up. The bootloader is locked and when I put in 'adb reboot bootloader', it says 'error: no devices/emulators found'. Then I tried both 'fastboot oem unlock' and 'fastboot flashing unlock', it gives me: 'FAILED <command write failed <Unknown error>>.
3. I've downloaded TWRP but it obviously does not do anything right now with my errors.
I unplugged the phone from the computer and now it says 0% battery, it does not charge.
I'm really confused and lost at what to do. Any help would be appreciated.
Thank you in advance!
Click to expand...
Click to collapse
i dont know what fast boot means or is. but couldnt you just enter download mode and flash KDZ?
raptorddd said:
i dont know what fast boot means or is. but couldnt you just enter download mode and flash KDZ?
Click to expand...
Click to collapse
Hi! I did try to follow the guide to KDZ on here but I can't get into download mode. I'm literally stuck; the phone simply starts up right into fastboot mode.
I need to know the history. What model. What were you doing to get stuck in fastboot.
TheMadScientist420 said:
I need to know the history. What model. What were you doing to get stuck in fastboot.
Click to expand...
Click to collapse
Hi! It's the H810 model. My dad was watching YouTube videos when his phone suddenly turned black and went into fastboot. The phone was originally from Wind Mobile but my brother unlocked it through the web. My dad uses ChatR. In order to start up the phone now, I have to plug it to a wall outlet before it starts up into fastboot. When I plug it into my computer directly, it says 0% battery but it does not charge up.
I know a fastboot usb cable force charges. But it sounds like a more sisnister problem if its like u say. Id sent it to lg for waranty on bootloop issue
LG-H810 Qualcomm 9008
TheMadScientist said:
I know a fastboot usb cable force charges. But it sounds like a more sisnister problem if its like u say. Id sent it to lg for waranty on bootloop issue
Click to expand...
Click to collapse
Sir i ended up flashing wrong kdz to H810 and after flashing it become dead state (Qualcomm9008) mode i successfully recovered it by following this guide https://forum.xda-developers.com/att-g4/general/unbrick-9008-mode-h810-100-method-t3555231/page10
but now it won't go To DOWNLOAD MODE it goes To fastboot mode instead i've tried deffirent LAF.imges but no success !
here is what is on the phone screen when i connect it to pc!
(Product name-msm8992_spr_us
Variant msm8992_p1_spr_usToshiba 32GB
bootloader version -
basevand version -
serial number- LGLS991b77257e1
signing production
secureboot disabled
lock state-locked
can u help?
please (thanx)
And another one who converted his device by using qfil..
Sent from my LG-H815 using XDA Labs
JennV123 said:
Hello!
I'm trying to fix a LG G4 that goes straight into fastboot mode when it's powered up.
I've tried several things:
1. Holding power + volume down. It goes into recovery mode but when I click yes to restoring everything, it automatically takes me back to the same fastboot screen.
2. I've installed Android-SDK and updated drivers when I plugged in the phone. When I put in 'adb devices', there is nothing. When I put in 'fastboot devices', the serial number shows up. The bootloader is locked and when I put in 'adb reboot bootloader', it says 'error: no devices/emulators found'. Then I tried both 'fastboot oem unlock' and 'fastboot flashing unlock', it gives me: 'FAILED <command write failed <Unknown error>>.
3. I've downloaded TWRP but it obviously does not do anything right now with my errors.
I unplugged the phone from the computer and now it says 0% battery, it does not charge.
I'm really confused and lost at what to do. Any help would be appreciated.
Thank you in advance!
Click to expand...
Click to collapse
Try to type into the terminal: 'fastboot continue'. This should make the system start up.
JennV123 said:
Hello!
I'm trying to fix a LG G4 that goes straight into fastboot mode when it's powered up.
I've tried several things:
1. Holding power + volume down. It goes into recovery mode but when I click yes to restoring everything, it automatically takes me back to the same fastboot screen.
2. I've installed Android-SDK and updated drivers when I plugged in the phone. When I put in 'adb devices', there is nothing. When I put in 'fastboot devices', the serial number shows up. The bootloader is locked and when I put in 'adb reboot bootloader', it says 'error: no devices/emulators found'. Then I tried both 'fastboot oem unlock' and 'fastboot flashing unlock', it gives me: 'FAILED <command write failed <Unknown error>>.
3. I've downloaded TWRP but it obviously does not do anything right now with my errors.
I unplugged the phone from the computer and now it says 0% battery, it does not charge.
I'm really confused and lost at what to do. Any help would be appreciated.
Thank you in advance!
Click to expand...
Click to collapse
Just type "fasboot reboot" ..it should boot normally or just press power button for 10 seconds and release
Related
##PLEASE NOTE##
These files are from Motorola's Development site and I take no liability with anything that happens with your device if something goes wrong.
DO NOT ATTEMPT TO FLASH THIS FILE ON ANYTHING BUT THE VERIZON WIRELESS MOTOROLA XOOM Z600 (3G MODEL) OR YOU WILL HAVE A SHINEY PAPER WEIGHT!!!!
Click to expand...
Click to collapse
You're going to need to have the Android SDK installed. You can download it here:
ANDROID SDK - DOWNLOAD
XOOM Firmware Downloads:
[3G|MZ600-HRI66]
[4G|MZ602-HLK75D]
Unzip the files in MZ600_HRI66.zip and move or copy them to the /platform-tools folder in your SDK folder.
Connect your Xoom to your computer. Type:
Code:
adb reboot bootloader
Wait for it to reboot into the bootloader.
Type the following commands, waiting for each to finish before continuing:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
You've now successfully flashed your Xoom back to stock. Now it's time to relock the device. Type
Code:
fastboot oem lock
wait for the menu
then press the volume-down button.
Then press the volume up button.
It'll take a minute or so, then reboot. You're now completely back to stock and ready for the update.
So if you are on Three . One you can use this to revert back to out of the box freshness?
Brenardo said:
So if you are on Three . One you can use this to revert back to out of the box freshness?
Click to expand...
Click to collapse
Yes. That is correct. This will return your XOOM to 100% stock.
word!
I have already been thru the LNX 0x0004 debacle and it was absolutely no fun whatsoever.
well I got a stuck at moto logo for 10 minutes
I am going to try to fastboot oem unlock, reflash images again and fastboot lock to see if I get out of moto logo
second install fix it
jlouang said:
second install fix it
Click to expand...
Click to collapse
So that means that you got it working, correct?
>.>
So the HRI66 is the latest version on the Motorola site? I really need to get a grasp of their version numbers.
EDIT:
Never mind looks like HRI66 is the latest version Thanks anyway.
i was thinking that with the change to the bootloader in the 3.1 update we couldn't use previous versions img's. But I am glad we can return to stock and get this 4G update!
I'm following all those steps directly. Once I type in adb reboot bootloader, it says starting Fastboot protocol support. Once I try to type any other command it says not recognized in adb. Any ideas?
Dead link...
dchurch85 said:
I'm following all those steps directly. Once I type in adb reboot bootloader, it says starting Fastboot protocol support. Once I try to type any other command it says not recognized in adb. Any ideas?
Click to expand...
Click to collapse
Did you extract all of the files in the ZIP into the 'tools' folder? The same one that adb is in.
Could someone help me,
After the rebooting device I got this massage :
Failed to boot LNX 0x0004
Starting RSD mode 2
Then stuck on Motorola logo. I can't enter the recovery mode.
What should I do ?
My Xoom is H.6.1-38-9 International version
CakraMas said:
Could someone help me,
After the rebooting device I got this massage :
Failed to boot LNX 0x0004
Starting RSD mode 2
Then stuck on Motorola logo. I can't enter the recovery mode.
What should I do ?
My Xoom is H.6.1-38-9 International version
Click to expand...
Click to collapse
This is what I was afraid of..... try searching the error you are getting. Not many options on how to fix.
i am curious about the LNX 0x0004 error. I know it comes from trying to relock with non-factory img's but what exactly does that mean? I am curious what actually causes the device to soft brick.
Finally I made it, .
I can enter to bootloader by fastboot method, flash the stock image, then relock my device.
Kinda having the same issue as dchurch... "adb reboot bootloader" reboots Xoom to the "M" logo with "Starting Fastboot protocol support," but I can't continue with nay further commands. My computer no longer recognizes the presence of my Xoom and my Xoom doesn't progress past this screen. I can boot it normally with no problem. I've extracted all of the necessary files into my platform tools folder with adb.. any input?
gatorhater73 said:
Kinda having the same issue as dchurch... "adb reboot bootloader" reboots Xoom to the "M" logo with "Starting Fastboot protocol support," but I can't continue with nay further commands. My computer no longer recognizes the presence of my Xoom and my Xoom doesn't progress past this screen. I can boot it normally with no problem. I've extracted all of the necessary files into my platform tools folder with adb.. any input?
Click to expand...
Click to collapse
You can try manually going into fastboot as well... there are two ways to do this:
No matter what, power off the Xoom. Then, 1) Power on the Xoom and as soon as you see it turn on (within a second or two of the power on), press the Volume Down button, which kicks it into Fastboot. 2) If you miss the 1st couple of seconds and press Volume Down after 3-5 seconds, it will say "Android Recovery." You can then press Volume Down until you get to Fastboot, then press Volume Up.
My guess is that you have a different issue, something to do with your Fastboot image. Not sure if booting the Xoom into the OS and connecting with USB Debugging on will work or not to flash the files, perhaps maybe just the boot.img?
I also believe that when the Xoom says "Starting Fastboot protocol support", it is in fastboot mode and you can send the fastboot commands to the Xoom. If your PC does not show the Xoom as a device in your PC's Device manager, then you will probably need to load new/correct drivers onto your PC.
Did you make sure that adb recognized your device? Adb devices in the camaned prompt
Sent from my Xoom using Tapatalk
I think I bricked my G3 :/
I tried usual methods but couldn't get into recovery or download mode, then a few days ago I realized I could get it into this fastboot mode by holding volume up and plugging into USB as you would normally do to get into download mode but you have to hold up for a minute or so (it shows the download mode icon for a few seconds and then goes to fastboot) when in fastboot it connects to the computer and shows in device manager as "android device" and the phone says "processing commands" So I tried to follow this guide http://forum.xda-developers.com/showthread.php?t=2785089 to return it to stock, but I couldn't get it to show up in the LG software.
I read some forum posts about fastboot mode and found that by using the command "fastboot boot twrp.img" (the recovery image I downloaded) in command prompt it would send it to the phone and the phone would display some info and then reboot into TWRP, from here I tried to install a correct rom but the installation starts and there are some errors and then it hangs. I also tried the command "fastboot flash recovery twrp.img" but it fails. This is as far as I have got with it.
It came to me in this condition but the previous owner said he was running Cyanogen and it was working fine until he tried to update it with a nightly build. I suspect he might've tried to install the wrong rom for the phone or the rom was corrupt.
ou could try to revive the phone doing a testpoint and then use boarddiag tools (look in xda thread).
Here is how to make a testpoint: http://forum.xda-developers.com/showpost.php?p=65002893&postcount=17
my device came with unlocked bootloader, so I tried to flash twrp but every time i type "fastboot flash recovery C:\adb\twrp-3.2.1-3-whyred.img" and hit enter, the device seems to disconnect from pc and there is "press any key to reboot" in fastboot on my phone.
How can I solve this issue?`
Phone gets detected by adb/fastboot tool so its not a driver problem. I tried different cables and usb ports aswell.
Firmware is latest global stable.
Nazukii said:
my device came with unlocked bootloader, so I tried to flash twrp but every time i type "fastboot flash recovery C:\adb\twrp-3.2.1-3-whyred.img" and hit enter, the device seems to disconnect from pc and there is "press any key to reboot" in fastboot on my phone.
How can I solve this issue?`
Phone gets detected by adb/fastboot tool so its not a driver problem. I tried different cables and usb ports aswell.
Firmware is latest global stable.
Click to expand...
Click to collapse
try upgrade your android sdk on your pc
Nazukii said:
my device came with unlocked bootloader, so I tried to flash twrp but every time i type "fastboot flash recovery C:\adb\twrp-3.2.1-3-whyred.img" and hit enter, the device seems to disconnect from pc and there is "press any key to reboot" in fastboot on my phone.
How can I solve this issue?`
Phone gets detected by adb/fastboot tool so its not a driver problem. I tried different cables and usb ports aswell.
Firmware is latest global stable.
Click to expand...
Click to collapse
Well if you already had adb in your pc, rename the twrp file to recovery, you don't have to move the twrp from download folder, open download folder press shift and right click then select open cmd here, on cmd type "adb device" to see if your device connected, then after that type this "fastboot flash recovery recovery.img" press enter than after that type "fastboot boot recovery.img" TEAMWIN logo should appear on your device and then you can unplug your device. Hope this useful
i am trying to flash twrp there is no folder called adb i have installed the 15 second adb and all so i have got this minimal adb flashboot and i tried with that and got this ---- FAILED (remote: Flashing is not allowed in Lock State). i have granted all usb and oem unlocking. please help with this
Phone shows unlocked during the boot?
I had the same Problem,after a Factory Reset works for me.
I am on Miglobe-Rom Miui10 8.6.28.
Minimal ADB is enough.
Or use this from Attachment.
Unpack with Win.zip and copy Twrp in this Folder.
Conect the Phone with your Pc ,boot into Bootloader and click "cmd-here.exe"
Use this Command
fastboot flash recovery twrp-3.2.1-3-whyred.img
@Nazukii - Quick question - any chance you could try running GameBench on your device, and see if our background service dies when the device is disconnected from the PC? I don't have a Note 5 Pro to test, and I've got some user complaints. Any assistance would be awesome!
J
gamebenchjake said:
@Nazukii - Quick question - any chance you could try running GameBench on your device, and see if our background service dies when the device is disconnected from the PC? I don't have a Note 5 Pro to test, and I've got some user complaints. Any assistance would be awesome!
J
Click to expand...
Click to collapse
Have you fixed your app to run on Magisk-SU ?
otonieru said:
Have you fixed your app to run on Magisk-SU ?
Click to expand...
Click to collapse
Hey Otonieru,
Not yet, but I've got one of the engineers working on it - hopefully it'll be up in the next 30 days or so
Same problem here after updating my gcam was not working was enabling hall again but it is not booting into twrp
Redmi Note 5 pro
So my Bootloader is locked,
My phone stuck in MI recovery idk how.
I cant install MIUI via fastboot. Im stuck ..
Can anyone please help me here not sure how to proceed further.
If you have made sure that you have all the drivers installed and still have not solved, you need to use an Intel-based PC / notebook and use a usb 2.0.
”Well if you already had adb in your pc, rename the twrp file to recovery, you don't have to move the twrp from download folder, open download folder press shift and right click then select open cmd here, on cmd type "adb device" to see if your device connected, then after that type this "fastboot flash recovery recovery.img" press enter than after that type "fastboot boot recovery.img" TEAMWIN logo should appear on your device and then you can unplug your device. Hope this useful”
i did that but it is showing failed(too many links)and "press any key to reboot" showing on my phone's fastboot screen
Fastboot boot recovery.img flashing problem on Redmi note 5 pro
My bootloader is unlocked and my oem as well as usb deb is on. After i connect my phone in fastboot mode to my pc. The cmd shows fastboot devices but when it comes to fastboot boot recovery.img flashing device get disconnected. Plzzzzzz let me know a solution for this. A solution for this will be highly appreciateable.
Hello,
My H815 phone is stuck in fastboot mode.
Whenever i press the power key the phone goes directly into fastboot mode.
I wanted to reset the phone using the phone's menu but straight after that the phone booted directly in fastboot mode and it's now stucked.
I believe that the bottery should be dead as well.
The host has it's bootloader uncloked, however i cannot install TWRP as i receive a message command: unknow in ADB when i try to install the recoevery.
I tried different USB cables and different ports of the same |laptop, currently runnin windows 7 with all the drivers.
Looking for are feedback on how to install the recovery and get rid of the command:unknown error
gogobaba said:
Hello,
My H815 phone is stuck in fastboot mode.
Whenever i press the power key the phone goes directly into fastboot mode.
I wanted to reset the phone using the phone's menu but straight after that the phone booted directly in fastboot mode and it's now stucked.
I believe that the bottery should be dead as well.
The host has it's bootloader uncloked, however i cannot install TWRP as i receive a message command: unknow in ADB when i try to install the recoevery.
I tried different USB cables and different ports of the same |laptop, currently runnin windows 7 with all the drivers.
Looking for are feedback on how to install the recovery and get rid of the command:unknown error
Click to expand...
Click to collapse
Search for FWUL from Steadfasterx.
download-> flash->connect-> open Comannd-> type "fastboot flash recovery recovery.img" or "fastboot reboot system"
Which command are you using for installing TWRP in ADB?
Hi people,
I unlocked, rooted, and flashed Liquid on my XL tonight. Everything seemed to be going fine when I rebooted again and got a bootloop. TWRP is not loading, what I am getting is the Android on it's back menu and here's where I'm lost. I'm getting the error in the screenshots when I try to sideload the factory image from ADB. My cords are good, drivers are updated, and I have ADB and Fastboot set to Large Address Aware. I don't want to admit that I have a paperweight now. Any ideas? Thanks in Advance
elektrosoundwave said:
Hi people,
I unlocked, rooted, and flashed Liquid on my XL tonight. Everything seemed to be going fine when I rebooted again and got a bootloop. TWRP is not loading, what I am getting is the Android on it's back menu and here's where I'm lost. I'm getting the error in the screenshots when I try to sideload the factory image from ADB. My cords are good, drivers are updated, and I have ADB and Fastboot set to Large Address Aware. I don't want to admit that I have a paperweight now. Any ideas? Thanks in Advance
Click to expand...
Click to collapse
Can you reboot to download mode (fastboot)? Hold the power button and vol down buttons together.
If you can get into the bootloader, use fastboot to flash the factory image instead of using adb. Or try issuing 'adb reboot-bootloader' command to reboot to bootloader
koivth said:
Can you reboot to download mode (fastboot)? Hold the power button and vol down buttons together.
If you can get into the bootloader, use fastboot to flash the factory image instead of using adb. Or try issuing 'adb reboot-bootloader' command to reboot to bootloader
Click to expand...
Click to collapse
Both volume buttons? I've only done the power and down volume. I will try both of these when I get home tonight, or when I wake up. I stayed up until 6am working on this and did not get much sleep. I'm also going to uninstall and reinstall the Pixel driver. I don't remember off the top of my head if I installed it before or after I upgraded my laptop to Windows 10.
elektrosoundwave said:
Both volume buttons? I've only done the power and down volume. I will try both of these when I get home tonight, or when I wake up. I stayed up until 6am working on this and did not get much sleep. I'm also going to uninstall and reinstall the Pixel driver. I don't remember off the top of my head if I installed it before or after I upgraded my laptop to Windows 10.
Click to expand...
Click to collapse
Sorry for being unclear. To get into the bootloader (where you can use the fastboot command to re-flash the factory image), you hold the Power Button and Volume Down buttons together (not volume up button). This is what your screen should look like if you successfully get to the bootloader: https://www.xda-developers.com/files/2016/10/CvqcEDHUsAA_EY4.jpg
If you see that screen, you're sitting good. Download the latest factory image (https://developers.google.com/android/images#marlin) and run the flash-all.bat (for windows) script to reflash your phone. You will have to have fastboot drivers installed on your computer for that to work.
If your device is recognized by adb (if you type 'adb devices' and it shows your device as the output) but you are having trouble getting to the bootloader, you can type in 'adb reboot-bootloader' to reboot your device into fastboot mode where you can flash the factory image. Hopefully that helps push you in the right direction. Your phone isn't bricked/lost forever if adb or fastboot recognizes your device and you can save it!
koivth said:
Sorry for being unclear. To get into the bootloader (where you can use the fastboot command to re-flash the factory image), you hold the Power Button and Volume Down buttons together (not volume up button). This is what your screen should look like if you successfully get to the bootloader: https://www.xda-developers.com/files/2016/10/CvqcEDHUsAA_EY4.jpg
If you see that screen, you're sitting good. Download the latest factory image (https://developers.google.com/android/images#marlin) and run the flash-all.bat (for windows) script to reflash your phone. You will have to have fastboot drivers installed on your computer for that to work.
If your device is recognized by adb (if you type 'adb devices' and it shows your device as the output) but you are having trouble getting to the bootloader, you can type in 'adb reboot-bootloader' to reboot your device into fastboot mode where you can flash the factory image. Hopefully that helps push you in the right direction. Your phone isn't bricked/lost forever if adb or fastboot recognizes your device and you can save it!
Click to expand...
Click to collapse
That's where that first screenshot came from. I will try the reboot bootloader tonight. They sort of recognize my phone, but I can't get them to flash anything. This isn't my first rodeo with borked phones, but I don't think I've had this much trouble since I placed the wrong boot animation on my Droid 4 many years ago.
:victory: :highfive: It's flashing right now. You don't know how much I appreciate it.
Hi, thought I would jump in on this thread. I have the same issue, and I can get to the fastboot screen and device is recognised by adb with "fastboot devices". When I try to flash-all I get the message that the device must be unlocked. Any idea why mine in different? I just have stock recovery, maybe that is it. The device also will not boot into recovery, it just bootloops
obsidianlycanthrope said:
Hi, thought I would jump in on this thread. I have the same issue, and I can get to the fastboot screen and device is recognised by adb with "fastboot devices". When I try to flash-all I get the message that the device must be unlocked. Any idea why mine in different? I just have stock recovery, maybe that is it. The device also will not boot into recovery, it just bootloops
Click to expand...
Click to collapse
Is your bootloader unlocked?
obsidianlycanthrope said:
Hi, thought I would jump in on this thread. I have the same issue, and I can get to the fastboot screen and device is recognised by adb with "fastboot devices". When I try to flash-all I get the message that the device must be unlocked. Any idea why mine in different? I just have stock recovery, maybe that is it. The device also will not boot into recovery, it just bootloops
Click to expand...
Click to collapse
Before you can flash the factory image, you have to unlock the bootloader by issuing this command first: 'fastboot flashing unlock'