Database Users

Unresponsive Device

So, I had been using my A500 for the last few days with no problems. Well, yesterday, I got home from work and powered it on. The lockscreen came up, but the screen was unresponsive. I turned it off and then back on, but screen still didn't work. Then I did a hard reset, which still didn't fix the problem. I put it into recovery, then did a wipe that still didn't fix the issue. I flashed the ROM again. Then a different ROM. All it does is is boot up and go to the lock screen, but the screen does not respond.
If I can avoid it, I don't really want to go through the hassle of returning it since I got it online. Hopefully it can be fixed without having to take it back. Thanks in advance for everyone's help.

Boot back into recovery.
Wipe your 3 things,
User Data
Cache
Dalvik
Then go to Mounts
Format the same 3 (user data, cache partition and Dalvak.
And Flexrom
Then flash your rom. Try and flash a basic rooted rom. No kernels, no gapps.zip
See what happens.
If you have a file called update.zip, on your sd, I would delete it. And anything else there except for the rom.

sounds like hardware failure. Has the tablet been dropped or banged around. The connector on the digitizer could have came loose.That would mean void warranty and take it apart ..
Send it back is likely your. Best option

Thanks for the quick responses! I'm gonna try these things, hopefully I don't have to take it back.

Guess it is a massive hardware failure. I formatted everything and reset everything I could. All ROM's will flash and boot, but I since the screen does not work, I cannot get past the first screen.
I'm going to have to return it, dammit. So, with no touchscreen, does anyone know how I can remove Clockworkmod Recovery and get the tablet back to stock? I don't want to get any problems during the return. Thanks everyone.

sikkboy626 said:
Guess it is a massive software failure. I formatted everything and reset everything I could. All ROM's will flash and boot, but I since the screen does not work, I cannot get past the first screen.
I'm going to have to return it, dammit. So, with no touchscreen, does anyone know how I can remove Clockworkmod Recovery and get the tablet back to stock? I don't want to get any problems during the return. Thanks everyone.
Click to expand...
Click to collapse
Well, with no touchscreen that makes the easy way out of the question.
Vache has a page with stock roms and updates;
http://forum.xda-developers.com/showthread.php?t=1113878
Now, some people, extracted the update.zip from the update rom, copied it to sd, and booted holding vol+ and PWR. This automatically starts the update flashing.
Others have actually flashed them through CWM and were successful. You can read through the thread and see how they fared.
On a normal basis, we would install AcerRecovery and flash them through there, as that is the preferred method for the full rooms. But this is out of the question for you, as you only have CWM.
With the update.zip, it might work, might not. The update might look for a preinstalled stock rom matching the ComGen numbers. Really don't know.
(I would try the above if the following doesn't work)
Another method, is to use ADB and push a stock image to your device. I've never done this personally, but I know it can be done. Best bet, is to repost the question "how to push a stock image with adb", then explain briefly why. And post it in the Q&A forum. This should hopefully get some folks who use adb to help you out. I rarely use it.

Moscow Desire said:
Well, with no touchscreen that makes the easy way out of the question.
Vache has a page with stock roms and updates;
http://forum.xda-developers.com/showthread.php?t=1113878
Now, some people, extracted the update.zip from the update rom, copied it to sd, and booted holding vol+ and PWR. This automatically starts the update flashing.
Others have actually flashed them through CWM and were successful. You can read through the thread and see how they fared.
On a normal basis, we would install AcerRecovery and flash them through there, as that is the preferred method for the full rooms. But this is out of the question for you, as you only have CWM.
With the update.zip, it might work, might not. The update might look for a preinstalled stock rom matching the ComGen numbers. Really don't know.
(I would try the above if the following doesn't work)
Another method, is to use ADB and push a stock image to your device. I've never done this personally, but I know it can be done. Best bet, is to repost the question "how to push a stock image with adb", then explain briefly why. And post it in the Q&A forum. This should hopefully get some folks who use adb to help you out. I rarely use it.
Click to expand...
Click to collapse
Thanks for all your help. I was able to get it back to stock. The return should go fine. You're awesome and I did not forget to use the thank you button.

have you tried a USB keyboard or mouse to flash it.thou I still think its hardware.
Failure

You can use normal usb mouse with this tablet, you will get mouse pointer on the screen when you connect mouse...

erica_renee said:
have you tried a USB keyboard or mouse to flash it.thou I still think its hardware.
Failure
Click to expand...
Click to collapse
I was able to flash using the physical buttons. I got it all back to factory specs so I can return it. you were correct I believe, it does seem to be a screen hardware failure. Everything else works but the touch response.

Im very sorry for your luck.. But i do believe this is a very well built device. Someone has to get a bad one sometimes.. Boohooooooooo

erica_renee said:
Im very sorry for your luck.. But i do believe this is a very well built device. Someone has to get a bad one sometimes.. Boohooooooooo
Click to expand...
Click to collapse
Guess I had to take one for the team

[Q] Kindle Stuck in TWRP Recovery

Okay,I've read everything on this topic. I've tried almost everything (except using the factory cable). If you can help me fix this I will paypal you (or the charity of your choice) the $25 dollars I would've spent on a factory cable.
I just want to know if I'm missing anything before I try and make or buy a cable.
My Problem:
I rooted my Kindle fire 6.3 using KFU, everything went flawlessly
(This is when I should've stopped, enjoyed my new root, and be problem free...but I didn't)
I saw a thread for the CM9 Reloaded Rom and thought "Hey I should push my luck and install this rom immediately!"
so with KFU I installed TWRP and then from there all hell broke loose
and by all hell I mean that I got stuck in TWRP recovery and couldn't boot my device normally
blah blah blah, I tried everything and somewhere along the way wiped everything from my kindle, I dont know why or how but it happened
The only thing I can do now is boot into twrp recovery. I've tried literally everything but if there's anyways you can fix this I will paypal you the $25 I would've spent on the factory cable.
I will be on this forum all day seeing as it's sunday and I am ready and willing to answer any and all questions about my predicament to further clarify the issue.
THANKS!!
p.s.
This isn't a knock against ReloadedRom or TWRP, I understand people have worked hard on them and I really appreciate all the devs do around here. this is simply an IBM (Idiot Behind Machine) problem!

gdr425 said:
Okay,I've read everything on this topic. I've tried almost everything (except using the factory cable). If you can help me fix this I will paypal you (or the charity of your choice) the $25 dollars I would've spent on a factory cable.
I just want to know if I'm missing anything before I try and make or buy a cable.
My Problem:
I rooted my Kindle fire 6.3 using KFU, everything went flawlessly
(This is when I should've stopped, enjoyed my new root, and be problem free...but I didn't)
I saw a thread for the CM9 Reloaded Rom and thought "Hey I should push my luck and install this rom immediately!"
so with KFU I installed TWRP and then from there all hell broke loose
and by all hell I mean that I got stuck in TWRP recovery and couldn't boot my device normally
blah blah blah, I tried everything and somewhere along the way wiped everything from my kindle, I dont know why or how but it happened
The only thing I can do now is boot into twrp recovery. I've tried literally everything but if there's anyways you can fix this I will paypal you the $25 I would've spent on the factory cable.
I will be on this forum all day seeing as it's sunday and I am ready and willing to answer any and all questions about my predicament to further clarify the issue.
THANKS!!
p.s.
This isn't a knock against ReloadedRom or TWRP, I understand people have worked hard on them and I really appreciate all the devs do around here. this is simply an IBM (Idiot Behind Machine) problem!
Click to expand...
Click to collapse
If you know how to use fast boot try this command:
fastboot -i 0x1949 oem idme bootmode 4000
That should get you out of the twrp loop.
Sent from my Amazon Kindle Fire using XDA

gdr425 said:
Okay,I've read everything on this topic. I've tried almost everything (except using the factory cable). If you can help me fix this I will paypal you (or the charity of your choice) the $25 dollars I would've spent on a factory cable.
I just want to know if I'm missing anything before I try and make or buy a cable.
My Problem:
I rooted my Kindle fire 6.3 using KFU, everything went flawlessly
(This is when I should've stopped, enjoyed my new root, and be problem free...but I didn't)
I saw a thread for the CM9 Reloaded Rom and thought "Hey I should push my luck and install this rom immediately!"
so with KFU I installed TWRP and then from there all hell broke loose
and by all hell I mean that I got stuck in TWRP recovery and couldn't boot my device normally
blah blah blah, I tried everything and somewhere along the way wiped everything from my kindle, I dont know why or how but it happened
The only thing I can do now is boot into twrp recovery. I've tried literally everything but if there's anyways you can fix this I will paypal you the $25 I would've spent on the factory cable.
I will be on this forum all day seeing as it's sunday and I am ready and willing to answer any and all questions about my predicament to further clarify the issue.
THANKS!!
p.s.
This isn't a knock against ReloadedRom or TWRP, I understand people have worked hard on them and I really appreciate all the devs do around here. this is simply an IBM (Idiot Behind Machine) problem!
Click to expand...
Click to collapse
I'll help you if you'll spend the money on a factory cable anyway so you can get out of your next situation.
Read this post and make sure your drivers are in order.
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
You'll have to get that done first before anything else. If you are completely lost, reading the first post in that thread wouldn't be a bad idea either.
Basically, you have to set the bootmode back to normal using either adb or fastboot... but like I mentioned before, you have to make sure your drivers are working and recognizing your KF.

kinfauns said:
I'll help you if you'll spend the money on a factory cable anyway so you can get out of your next situation.
Read this post and make sure your drivers are in order.
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
You'll have to get that done first before anything else. If you are completely lost, reading the first post in that thread wouldn't be a bad idea either.
Basically, you have to set the bootmode back to normal using either adb or fastboot... but like I mentioned before, you have to make sure your drivers are working and recognizing your KF.
Click to expand...
Click to collapse
I'm sorry for asking noob like questions
I swear i've had an android phone rooted and all that for over 2 years...anyways
what do you mean "recognizing your KF"
It shows up in my list of devices when I plug it in

gdr425 said:
I'm sorry for asking noob like questions
I swear i've had an android phone rooted and all that for over 2 years...anyways
what do you mean "recognizing your KF"
It shows up in my list of devices when I plug it in
Click to expand...
Click to collapse
Just having it show up isn't good enough. With TWRP open... you need to have it show up exactly as "Android Phone -> Android Composite ADB Interface" and "Composite" must be in there.
If it does that... Go to your Kindle Fire Utility folder, open the tools folder inside there. Once you have that open, shift-right-click inside the folder and select "Open command window here" to get to the command line. Then inside that enter these two commands... one after the other....
Code:
adb shell idme bootmode 4000
adb reboot
Your KF should restart back into a normal boot and get you to your system.
EDIT: I guess I should mention that the "shift-right-click" inside a folder works in Windows 7, but I'm not sure that it does in previous versions.

When I did that, it reboots, shows the yellow triangle telling me to press the power button to enter recovery, if i press i get to twrp if i don't it just shuts off with the amber power button on
I think i may have to manually install the drivers?

gdr425 said:
When I did that, it reboots, shows the yellow triangle telling me to press the power button to enter recovery, if i press i get to twrp if i don't it just shuts off with the amber power button on
I think i may have to manually install the drivers?
Click to expand...
Click to collapse
If it's able to reboot with the "adb reboot" command, I'm guessing your drivers are working fine, but just to verify... What device is shown in the device manager when you have it booted into TWRP?
It's possible that you have a broken ROM flashed onto your device right now and it can't complete a normal boot. You might want to try flashing a new ROM...

If it's rebooting after issuing the commands, then you shouldn't have to press the power button once the yellow triangle comes up. Just give it a few seconds to get past that part and to the KF screen.
I was having the same issues yesterday after flashing, but resolved once I realized I could issue the commands.

if I dont press the power button it just shuts down, I actually figured out a fix for this brick that worked for me I'll post it in a thread today because i've seen a lot of people having the same problem without much success, THANKS to EVERYONE who helped me with this!

http://forum.xda-developers.com/showthread.php?t=1576675
should take care of your problem

Kindle Fire bricked. Need major help

Hello, so this is my first time trying to root an android device, and I think I messed up. I watched a tutorial on youtube on how to do it and successfully installed superuser and twrp from a batch file ( I had to install adb drivers first ). I wasn't really sure I did it in the correct steps, so I wanted to revert back to the stock os. I booted into twrp and wiped the data ( cache, system, etc) from twrp. I then mounted it and transfered the kindle fire update 6.3.1 to my KF. I used the option on twrp to revert back to stock using the newly transferred zip. It ran for awhile then prompted me to click reboot. So I did. And this is where it gets tricky
After the reboot, all I see is the boot screen displaying "kindle fire." It never booted and lasted like this for hours. I tried to boot into twrp but I think it got deleted. I googled the problem and found it was in some sort of fastboot loop. I tried many fixes, using adb and other fastboot commands. Every time I tried anything, all I got was "waiting for device." Also, I couldn't use adb shell because it said system/bin/sh was not found. I went to my computer and found that the kindle fire no longer showed up as a removable device, but it showed up in device manager as adb composite interface under android phone. I thought that somehow all of my system files got deleted and thats why it says system/bin/sh not found. I tried to use the adb push command to manually send the update.zip to the KF but it is no longer a mounted drive, so there is nowhere to send it to. I'm at a loss here, Ive tried numerous utilities such as KFU, firekit, unbrick utility. I just need to figure out a way to remount the KF and copy over the folder "system" in the update.zip. If anyone could help me that would be great, as I have been trying to fix this for three days now.:fingers-crossed:

Read the How To in the attached link and it should help you figure out what the problem is and get you unbricked, http://forum.xda-developers.com/showthread.php?t=1552547.

tazmanhawaii said:
Read the How To in the attached link and it should help you figure out what the problem is and get you unbricked, http://forum.xda-developers.com/showthread.php?t=1552547.
Click to expand...
Click to collapse
That doesn't really help me at all, as I have tried the solutions that what you just posted provides, and none of them have worked. I have tried flashing firefirefire and twrp to the kindle fire using fastboot, but to no avail. I think I need a bit more help than a beginner's guide can provide, but thanks for the link.

Marblesnake said:
That doesn't really help me at all, as I have tried the solutions that what you just posted provides, and none of them have worked. I have tried flashing firefirefire and twrp to the kindle fire using fastboot, but to no avail. I think I need a bit more help than a beginner's guide can provide, but thanks for the link.
Click to expand...
Click to collapse
First of all, when you try to revert to stock without wiping the necessary partitions, bad things will happen. What usually happens is you end up with some sort of frankenROM with no working shell and no custom bootloader or recovery.
Based on your description, it seems like you aren't in fastboot at all. You can confirm this by paying attention to the boot screen at the device starts up. If you see a bright Kindle Fire logo that stays bright, you're in fastboot. If you see a bright Kindle Fire logo that dims a little after a few seconds, you're no longer in fastboot and the device is trying to boot normally. What usually happens in situations like yours is, not only does the system have no way of booting, but there is also no working shell to send the necessary commands to change the bootmode, and you will receive the typical "system/bin/sh not found" error.
The problem is without a working shell, you cannot get into fastboot to install custom recovery and you cannot install recovery while booted "normally" without a working shell.
You have two options:
* Acquire a factory cable. A Motorola style factory programming cable to be exact. You can purchase one, or make one yourself. There is a thread in the KF General forum with information regarding both. The factory cable will put the device in fastboot so you will be able to install custom recovery and repair your system.
or
* Use Firekit. But in order for Firekit to work properly in your situation, you need to put the device in USBboot to install a "new" bootloader and recovery. This consists of opening the device and using the "shorting trick" as described in the Firekit thread. I would suggest creating a liveUSB with "persistence" and install the SoupKit. SoupKit comes with Firekit along with a number of other tools you may find useful.
Either way, you need to get custom recovery installed so you can wipe your system and data (factory reset) partitions and flash a new ROM. If it's the stock ROM you want, MoDaCo is your best bet. Once you install a custom ROM, there is no need to "root" as all custom ROMs come pre-rooted.
Hope that helps.

soupmagnet said:
First of all, when you try to revert to stock without wiping the necessary partitions, bad things will happen. What usually happens is you end up with some sort of frankenROM with no working shell and no custom bootloader or recovery.
Based on your description, it seems like you aren't in fastboot at all. You can confirm this by paying attention to the boot screen at the device starts up. If you see a bright Kindle Fire logo that stays bright, you're in fastboot. If you see a bright Kindle Fire logo that dims a little after a few seconds, you're no longer in fastboot and the device is trying to boot normally. What usually happens in situations like yours is, not only does the system have no way of booting, but there is also no working shell to send the necessary commands to change the bootmode, and you will receive the typical "system/bin/sh not found" error.
The problem is without a working shell, you cannot get into fastboot to install custom recovery and you cannot install recovery while booted "normally" without a working shell.
You have two options:
* Acquire a factory cable. A Motorola style factory programming cable to be exact. You can purchase one, or make one yourself. There is a thread in the KF General forum with information regarding both. The factory cable will put the device in fastboot so you will be able to install custom recovery and repair your system.
or
* Use Firekit. But in order for Firekit to work properly in your situation, you need to put the device in USBboot to install a "new" bootloader and recovery. This consists of opening the device and using the "shorting trick" as described in the Firekit thread. I would suggest creating a liveUSB with "persistence" and install the SoupKit. SoupKit comes with Firekit along with a number of other tools you may find useful.
Either way, you need to get custom recovery installed so you can wipe your system and data (factory reset) partitions and flash a new ROM. If it's the stock ROM you want, MoDaCo is your best bet. Once you install a custom ROM, there is no need to "root" as all custom ROMs come pre-rooted.
Hope that helps.
Click to expand...
Click to collapse
Thanks for the help. Yeah, I tried the firekit method but didn't use the shorting trick. I have scoured the internet for information and tricks and it seems like these are my last two options before I throw this thing out the window. I have seen your posts in other threads and you have been a great help throughout this ordeal.

factory cable
thank you for this information. I am in the same predicament. I am purchasing a factory cable from Amazon $1.27.
It is sold by Earlybirdsavings and is a 3ft micro USB factory cable for kindle fire and Motorola Xoom.
thank you for all the helpful information!

[Q] Fastboot Reason: Sticky bit factory_fastboot?

I flashed the Eclipse ROM via safestrap and then restored the Eclipse ROM onto the stock ROM slot. For some stupid reason, instead of restoring the stock ROM slot before resetting the phone back to stock, I opted to use RSD Lite 6.1.4 and tried to flash the JB firmware (yes, I got into fastboot). When I tried to do this, the phone reboots past the Motorola M insignia, to the droid startup screen (with the flashing red light/circle), but does not get past the startup screen (yes, I gave it 30+ minutes to no avail). I also tried to reflash the JB firmware, but no matter what, I ended up stuck at the bootup screen.
For this reason, I tried to flash the ICS firmware instead (per instructions on XDA and other websites, I removed the lines in the XML file that had the word var, getvar, and oem). This did work! However, after RSD flashed the firmware, rather than restarting into the OS, the phone reboots into a black screen w/ the phrase "Fastboot Reason: Sticky bit factory_fastboot" at the very bottom. Anytime I try to restart the phone, it automatically boots into this screen. If I hold the volume up and down buttons, together w/ the power button, I am able to get back to the option to start normally.
When I tried to do the OTA JB update, the phone downloads the necessary files, but when the phone tries to reboot to install the OS update, it goes back into that black screen and does not install the update. Also, when I finally do get back into the OS, the phone then constantly reboots as if it were trying to install the OTA JB update.
Does anyone know what "Fastboot Reason: Sticky bit factory_fastboot" means? Also, if anyone knows how to "fix" this issue, I'd greatly appreciate it. If the fix requires command line work (like in this thread), I'd greatly appreciate if someone could walk me through it step-by-step, as I am not familiar w/ the command line process.
Thanks!
Edit 1: The next step I will try is to get root back on my phone, install Safestrap, and see whether I can flash a backup that I previously had.
Edit 2: In some threads for other Moto phones, there is some discussion regarding using ADB to fastboot/flash the stock ROM. Anyone know how this is different from using RSD? Also, can anyone walk me through HOW to ADB? I have zero knowledge in this regard.

Have you tried holding the buttons down to enter fast boot again and reflash? Worth a shot if you haven't. You could also attempt a factory reset from the boot menu. Maybe the corrupt file would correct itself.
You should definitely take the time to learn some ADB; at least a working understanding. It helps down the road.
Here's a good tutorial on ADB commands. http://mobile.tutsplus.com/tutorials/android/android-adb-quick-guide/
And to install ADB without Android SDK (app production software) http://mobilecon.info/install-adb-in-windows.html
Sent from my Nexus 7 using xda app-developers app

skippid said:
Have you tried holding the buttons down to enter fast boot again and reflash? Worth a shot if you haven't. You could also attempt a factory reset from the boot menu. Maybe the corrupt file would correct itself.
You should definitely take the time to learn some ADB; at least a working understanding. It helps down the road.
Here's a good tutorial on ADB commands. http://mobile.tutsplus.com/tutorials/android/android-adb-quick-guide/
And to install ADB without Android SDK (app production software) http://mobilecon.info/install-adb-in-windows.html
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes, I attempted to reflash on multiple occasions, both using the stock ICS and the stock JB roms. I must have reflashed close to 10x at this point. In any case, no matter how often I have reflahsed (including after doing a factory reset from within the OS as well as from within recovery), I still get the error. The good news is that I was successfully able to flash the JB ROM and have the phone OS actually start up, whereas, a few days ago, it would be stuck at the red circle/eye thing.
Furthermore, I attempted the command fastboot flash system [system.img], and I got the error:
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
error: cannot load '[system.img]': no error
I saved the system.img in both c:\android, as well as the internal SD card of the phone.
The other good news is that I am still able to use the phone if I get into the boot menu and ask the phone to boot normally. However, I am now unable to get root, and anytime I need to restart the phone, it gives me that error message.
I have also tried the command fastboot reboot bootloader but continue to get the same error message.

OK. Find a JB leak zip or current stock JB zip, access the screen where it asks for AP Fast boot and recovery, choose recovery, then volume up I believe when the phone shows the android with the red exclamation point.. Then choose update with zip. Search your SD card and install. It's worth a try in this manner in case you haven't already.
That's odd that your phone didn't respond well with RSD.
Sent from my XT907 using xda app-developers app

You need to use an updated fastboot binary for the new larger images in these devices.
http://db.tt/AveMC40y

skippid said:
OK. Find a JB leak zip or current stock JB zip, access the screen where it asks for AP Fast boot and recovery, choose recovery, then volume up I believe when the phone shows the android with the red exclamation point.. Then choose update with zip. Search your SD card and install. It's worth a try in this manner in case you haven't already.
That's odd that your phone didn't respond well with RSD.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Skippid, thanks for the suggestions. I tried your method as well. Went into recovery, selected to update from external SD (or something to that effect), selected the JB zip file, and let it flash that way. Unfortunately, I still received the same error message regarding the sticky bit factory_fastboot.

cellzealot said:
You need to use an updated fastboot binary for the new larger images in these devices.
http://db.tt/AveMC40y
Click to expand...
Click to collapse
cellzealot, thank you for the link. I've downloaded the file that you linked to. Could you be so kind as to now give me a step-by-step on how to re-attempt the flashing process?

Quick update - I was able to get root back, installed safestrap, and flashed the nandroid that I had made back when I first flashed Eclipse. However, I am still having the same issue:
Whenever I restart the phone, I get the sticky bit factory_fastboot error. If I use the command fastboot continue, the phone boots up as normal; however, it would be great to not have to do this each and every time I reboot the phone. Any help would be greatly appreciated. Thanks!

More updates (still not fixed):
After getting root, I reflashed my nandroid, factory reset (both within the OS and in recovery), and then tried flashing both the ICS and JB stock ROMs. I tried flashing both using mfastboot, as well RSD Lite. The files flash successfully; however, whenever I restart the phone, I continue to get the stick bit factory_fastboot error.
Also, when I get into recovery, I try to flash via "update from external SD". When I do so, recovery simply restarts without flashing the stock ROM.

Here's my last update as to this issue:
After trying all of the methods that I could think of (RSD Lite, flashing via fastboot and mfastboot, flashing from external), the problem did not correct itself.
I brought my phone into a Verizon store, where they told me that they had never seen that problem before. They agreed to replace my phone pursuant to the one-year warranty (I received my phone in December), which I received today. I've again rooted my phone, but have opted to not screw around w/ safestrap and custom ROMs this time around, as I find the stock JB experience to actually be quite good.

Found the soultion!!!!!!
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful

Thank you!
cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Thank you! This was the answer I needed after searching and searching trying all the different things for over 3 hours, this 2 second fix worked!

Namanati said:
Thank you! This was the answer I needed after searching and searching trying all the different things for over 3 hours, this 2 second fix worked!
Click to expand...
Click to collapse
#8 > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432

ATTACK said:
#8 > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432
Click to expand...
Click to collapse
Thanks, but that didn't come up when I googled AP Fastboot: flash failed, and since I didn't get it from rooting or unlocking my phone I didn't think to look for that.

cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Oh my god dude thank you so much. That fixed my bootloader issue that was plaguing me for weeks
Thanks again!!!

cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Thanks Man You really saved my razr.:good:

Edit : Sorry I asked stupid question!

Pierro29 said:
Edit : Sorry I asked stupid question!
Click to expand...
Click to collapse
there are no stupid questions if you question its because you dont know something and would like to fulfill the empty space where a reasonable answer could go. and s thanks for the solution to this error.

Okay, I have a "stupid"/newbie question. I flashed an image and I am getting the sticky boot thing. How to a get to a window to type the lines in?
Thanks!

cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Hey dude ! You save my life
Awesome trick

LG G2 Fastboot

Everything I found on this says volume + and power, which kicks me into download mode, not fastboot.
I've gone into adb and typed adb reboot bootloader, but that just restarts the phone and turns in on like normal.
I google the how to enter fastboot mode on LG G2 and can find plenty of post about being stuck in fastboot, but nothing on how to get into fastboot in the first place.
Found a tutorial here about setting up and using fastboot and thought I was set until I got to the part about "and using fastback", where it just says:
Make sure you have android debugging turned on in your phone (not really needed for fastboot but you do need for ADB), plug it into your computer and boot into fastboot mode...
I felt like watching "Much ado about nothing" when Denzel says; "The learned constable is too cunning to be understood"
Any direction is appreciated.

Hmm, I may have written that guide... Just checked and yeah should have been more clear I'll change that up. It should have read the USB debugging was needed for adb (not for fastboot) so when you can issue
adb reboot bootloader
But after that I did mention to check device specific forum for answers on how to get into fastboot/bootloader and being I've never held an lg g2 I took a quick look around.
Unfortunately the only way that I found that people said works every time is to wipe recovery to get into bootloader mode as the recovery you guys currently have disables something due to a patch getting custom recoveries to work
So yeah, I would advice to speak with someone knowledgeable about your specific device before you just wipe recovery
Out of curiosity, is there something specific you need to do with fastboot or are you just curious about your phone?
Sent from my Nexus 7 using XDA Premium 4 mobile app

demkantor said:
Out of curiosity, is there something specific you need to do with fastboot or are you just curious about your phone?
Click to expand...
Click to collapse
the current thing I've been trying to straighten out is that despite being rooted and installing TWRP, I can't install ROMS. I tried CM 11 and Hellfire so that I could put kitkat on, but gave the following:
Error executing updater binary zip.
One of the answers I found said that I had to go back to TWRP 2.3 (I'm using 2.6) and I believe that's where the whole bootloader thing came into play, because it was the way to 'downgrade' -
So then I found Philz touch 6 (as I understand it a mode of CM 11), but here he talked about fastboot and lokifying items. Here's the link:
http://forum.xda-developers.com/showthread.php?t=2554053
In the end it still comes back to the "can't load ROMs" issue. Just want a completely stripped down Kitkat that I can add the stuff I want without the bloatware.
Thanks in advance.(and the thanks button was hit on your reply)

For KitKat you should need a newer recovery with SELinux support which I believe is 2.6.x and newer for twrp, 2.3 I doubt would work if there even is one for your phone
But yes fastboot is often the best way to change recoveries but not the only way.
If there is a flashable.zip you could install new recovery from old
If your current ROM supports the flash image binary you can use a terminal emulator
You can use adb to install
Or even apps from the market
I would look for the latest recovery for your device, twrp, cwm, shouldn't matter so long as its new and then find what way works best changing for your phone.
The update-binary issue is often a sign that you need to change recoveries
Unfortunately without having your device I don't know if I can give you the best answers but feel free to ask
Best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
Unfortunately without having your device I don't know if I can give you the best answers but feel free to ask
Best of luck!
Click to expand...
Click to collapse
Thanks again. I have adb and the script for loading TWRP 2.6.xx. I unrooted and rerooted the phone, because I wasn't sure how to replace the recovery... Now I think I realize that I could just find another recovery image and place it in the same file as the loki flash and that will flash it (At least that's what I understand at present).
If that's the case, then downloading the Philz touch 6 would work... but not wanting to brick it, I'm still asking and reading.

Hello Guys.
I am having a similar issue. I have a new ROM that will not run because of a faulty lg set up wizard that always force closes and I can not get passed it and a nandroid that for some reason is corrupted. So. This fastboot seems to be a dead end it looks like a quick learning curve of ADB is the only viable answer. I have installed all SDK Manager with ADB Tools and also the required Jarva JDK and LG drivers. The phone is turned on (at the beginning of the faulty setup wizard) In CMD my device is found when typing in 'adb devices' So. I am already to push a new ROM over to the phone.
Do either of you guys know the adb command?
Help would be appreciated.
Thanks

You can't actually flash a new ROM with adb, but you can either push it phone with adb and then flash in recovery. Or if your recovery has an option for adb sideload then use this.
Also setup wizard crashing is usually the fault of wrong gapps or not wiping before flashing a rom
Sent from my Nexus 4 using XDA Premium 4 mobile app

I found that the best way was to load flashify, that did the trick so I could start trying out ROMs... so no on to the next step - finding a 4.4.2 stripped down stock and the LG stuff I actually like.... thanks again.

demkantor said:
You can't actually flash a new ROM with adb, but you can either push it phone with adb and then flash in recovery. Or if your recovery has an option for adb sideload then use this.
Also setup wizard crashing is usually the fault of wrong gapps or not wiping before flashing a rom
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the reply!
I know it's not possible to flash a ROM via ADB. I have everything set up, ADB etc, etc. My phone is turned on and adb is seeing it but I can not work out the command to push. Every time I try to push I just get a long list of ADB instructions (I think they are) but nothing gets pushed. I have read lots of instructions on how to make the command but I still must be doing something wrong.
Here are my parameters;-
adb push/C:\Users\dene\Desktop/cm-11-20140210-SNAPSHOT-M3-d802.zip/sdcard
Am I missing some spaces I am not aware of? Are all my slashes the right way round and in the right places? Is my 'sdcard' destination designation correct seeing as there is only internal storage on the G2?
Another problem I am having is that ADB has no problem seeing my sevice EXCEPT when I boot in to recovery (TWRP). When in recovery I lose coms between my device and pc. Hence I can no do TWRP ADB side load (I have tried). I have all the correct LG drivers loaded. Except MTP keeps failing to install? Any ideas?
Not to be mardy about it or hassle you but I am fairly house bound and live out in the country and really require my mobile phone. I have spent many hours trying to figure this out. Any help with the above would be much appreciated?
PS. I did a very thorough wipe, I always do. The gapps are built in to this ROM!
Thanks

dodge3003 said:
Thanks for the reply!
I know it's not possible to flash a ROM via ADB. I have everything set up, ADB etc, etc. My phone is turned on and adb is seeing it but I can not work out the command to push. Every time I try to push I just get a long list of ADB instructions (I think they are) but nothing gets pushed. I have read lots of instructions on how to make the command but I still must be doing something wrong.
Here are my parameters;-
adb push/C:\Users\dene\Desktop/cm-11-20140210-SNAPSHOT-M3-d802.zip/sdcard
Am I missing some spaces I am not aware of? Are all my slashes the right way round and in the right places? Is my 'sdcard' destination designation correct seeing as there is only internal storage on the G2?
Another problem I am having is that ADB has no problem seeing my sevice EXCEPT when I boot in to recovery (TWRP). When in recovery I lose coms between my device and pc. Hence I can no do TWRP ADB side load (I have tried). I have all the correct LG drivers loaded. Except MTP keeps failing to install? Any ideas?
Not to be mardy about it or hassle you but I am fairly house bound and live out in the country and really require my mobile phone. I have spent many hours trying to figure this out. Any help with the above would be much appreciated?
PS. I did a very thorough wipe, I always do. The gapps are built in to this ROM!
Thanks
Click to expand...
Click to collapse
I HAVE SOLVED THE ISSUE! Thanks for your assistance mate but in the end I just went back to stock using this amazing thread:-
http://forum.xda-developers.com/showthread.php?t=2432476
in conjunction with this amazing video;-
http://www.youtube.com/watch?v=IixQjo_hyz8
So! I am now un rooted and back to stock. Time to start the rooting ana ROMing all over again.lol
Thanks

Glad to here!
You need a space after push
But it usually easier not to enter the location of a file while pushing so cd to the directory first like
cd C:\Users.....
Then once there adb push /nameoffile /locationonphone
But if you don't want to cd, I see you have widows, depending on version you can just right click in the folder your file is located and choose open cmd here
Sent from my Nexus 7 using XDA Premium 4 mobile app

Need Help
As I thought I bought LG G2 D-802, but it was D-800 and I accidentally install the lollipop of D802 and now it's in bootlap.... I can only get into fastboot and whenever I try to flash .img of D-800 or D-802 it just stuck at "writing .img"
What to do to unbrick the phone and bring it back to live. I tired the adb and fastboot cmd method on windows 10 and windows 7 but no success. It's just stuck at writing .img file.