[Q] Stuck in AP Fastboot - Droid RAZR M Q&A, Help & Troubleshooting

My phone is seriously screwed as of right now. The other day I learned there was finally a way to root the XT907 version 98.30.1 and so that's immediately did exactly that. Successfully rooted my phone and decided why not go further and flash a custom ROM to it. Attempted to unlock the bootloader was under the belief that it had done so successfully and attempted to flash a recovery twrp to be exact. Now my phone is stuck in AP Fastboot and i cant do anything with it. I can't turn it off, I can't change the menu to reset it, nothing. I'm fairly new to this so i'm probably missing something but I have taken apart the phone and disconnected the battery cable and left it over night, nothing happened still stuck on the same page. I have tried RSDLite, didn't work. I don't know what else to do. This is all my phone says
AP Fastboot Flash Mode (S)
10.9B(*) 9sha-1e9f557, 2013-09-26 13:20:55)
eMMC Info: Size 8GB
Device is LOCKED. Status Code: 0
Battery Low
Transfer Mode:
USB Connected
Fastboot Reason: Flash Fail
then its just usb connection and disconnection. The only thing i know that i can do is replace the mother board and im tempted to do just that but im hoping someone on here can help.

Rsdlite will fix you right up. If it didn't work the first time you probably did something wrong
Sent from my XT907 using Tapatalk

Yep
thewraith420 said:
Rsdlite will fix you right up. If it didn't work the first time you probably did something wrong
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
Your probably right at first it didnt do anything but i had just left it plugged into the comp for awhile and came back and it was fixed thankfully. more than likely it was the rsd so thank you

hold volume up and power as soon as it turns of press volume up and down and power and then scoll down to reboot and there you go quick fix after just reinstall the stock file and it will fix the loop
good luck

Related

brick boot loader to black screen: no simple solution, simple prevention

Hi
So last night when I flashed my new created ROM with CWM, it seems like I ruined my boot loader, and from that I can't find the way to recover
SYMPTOMS:
- black screen
- power button doesn't do anything
- no button combination boots to download mode
- no charghing indication when connected to charger or USB
- no detection in the computer when connected to the USB
Is this the real black screen of death?
How did I get there?
I flashed a ROM through CWM, when it finished I selected reboot from CWM, and since then, all I see is black screen, no indication whatsoever to powering up.
I didn't try a USB JIG yet, but I will at Thursday (meet with a friend that has one)
as far as I understand the only way to recover from this is using a RIFF Box JTAG which requires, taking apart the phone, and soldering small wires to the board, and then reload the boot loader
Where do we go from here?
If it happened to you Please write down:
how did it happened to you?
what did you do to try to recover?
did you mange to recover?
if you did, how did you?
Why is this post so important to everyone?
Because if it didn't happen to you yet it might happen in your next CWM flashing.
So its very important to find a solution or at least the way to prevent it.
- update 31/12/2010 -
Cause
corrupted boot loader , bad sbl.bin flashing
Prevention:
do not flash roms/addons/fixes with sbl.bin
if you must flash sbl.bin, do it while you are sure that your USB configuration is perfect, and do it as less as possible.
Solution (for those who already bricked to black)
you're not gonna like it
find riffbox jtag....
marcelo.waisman said:
Hi
So last night when I flashed my new created ROM with CWM, it seems like I ruined my boot loader, and from that I can't find the way to recover
SYMPTOMS:
- black screen
- power button doesn't do anything
- no button combination boots to download mode
- no charghing indication when connected to charger or USB
- no detection in the computer when connected to the USB
Is this the real black screen of death?
How did I get there?
I flashed a ROM through CWM, when it finished I selected reboot from CWM, and since then, all I see is black screen, no indication whatsoever to powering up.
I didn't try a USB JIG yet, but I will at Thursday (meet with a friend that has one)
as far as I understand the only way to recover from this is using a RIFF Box JTAG which requires, taking apart the phone, and soldering small wires to the board, and then reload the boot loader
Where do we go from here?
If it happened to you Please write down:
how did it happened to you?
what did you do to try to recover?
did you mange to recover?
if you did, how did you?
Why is this post so important to everyone?
Because if it didn't happen to you yet it might happen in your next CWM flashing.
So its very important to find a solution or at least the way to prevent it.
BTW I think its a developers post, because we need developers creative way of thinking to find a solution
Click to expand...
Click to collapse
Happened to me too. I was tinkering with the Armani source to hopefully find something of use for Axura, and I bricked it. Same things happened to me. I called att and got a new one.
marcelo.waisman said:
Hi
So last night when I flashed my new created ROM with CWM, it seems like I ruined my boot loader, and from that I can't find the way to recover
SYMPTOMS:
- black screen
- power button doesn't do anything
- no button combination boots to download mode
- no charghing indication when connected to charger or USB
- no detection in the computer when connected to the USB
Is this the real black screen of death?
How did I get there?
I flashed a ROM through CWM, when it finished I selected reboot from CWM, and since then, all I see is black screen, no indication whatsoever to powering up.
I didn't try a USB JIG yet, but I will at Thursday (meet with a friend that has one)
as far as I understand the only way to recover from this is using a RIFF Box JTAG which requires, taking apart the phone, and soldering small wires to the board, and then reload the boot loader
Where do we go from here?
If it happened to you Please write down:
how did it happened to you?
what did you do to try to recover?
did you mange to recover?
if you did, how did you?
Why is this post so important to everyone?
Because if it didn't happen to you yet it might happen in your next CWM flashing.
So its very important to find a solution or at least the way to prevent it.
BTW I think its a developers post, because we need developers creative way of thinking to find a solution
Click to expand...
Click to collapse
Did you try removing battery and putting it back and then opening ODIN, holding the volume up/down and inserting the usb to bring it on the download mode. I guess I might have experience almost similar issue with one of the rom. I almost freaked out. Phone wont show if its charging. It wont mount on the pc. But tried all the possible method available several times including adb shell command. And finally I did hear the magical sound from window when the usb is connected and finally it did work.
Also try the adb method if it doesn't go into download mode using volume button combo.
Sent from my SAMSUNG-SGH-I897 using XDA App
Did u remove sbl.bin
Sent from my SAMSUNG-SGH-I897 using XDA App
Happened to me the first time I ran the OTA update from ATT. Paused the update, and when I resumed it - the phone though I finished downloading the JH7 update and tried to apply it.
It failed to apply and when it went to restart, it never powered on. No download mode, recovery, USB power, Odin, nothing. It was completely dead.
I got it replaced at the AT&T store.
If sbl.bin was removed or corrupted you should call the warranty center. Tell them ota update bricked your phone. Lol good luck
sent from my cappy running di11igaf's rom v2.5 at 1280mhz!!
I think it is just bad luck. I was once being careless and had the battery fall out of my phone while flashing, it interrupted the flash and I was still able to get in download mode to Odin it. Needless to say, I'll never flash again without the back cover on
bulletproof1013 said:
Did u remove sbl.bin
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Yes i'ts probably a bad sbl.bin, but I didn't remove it I flashed a new one, most of the rom's do the same
yeah sounds like it...sry for your luck.but seems like its toast then. keep us posted
But if you had a batch 1008 captivate and you messed up during and Odin flash to stock then your screwed bcuz Odin one click swaps the sbl.bins to make your button combinations impossible. ADB would work but you obviously can't access that. I too have a 1008 and it sucks, that is why I bought a jig.
silverslotcar said:
But if you had a batch 1008 captivate and you messed up during and Odin flash to stock then your screwed bcuz Odin one click swaps the sbl.bins to make your button combinations impossible. ADB would work but you obviously can't access that. I too have a 1008 and it sucks, that is why I bought a jig.
Click to expand...
Click to collapse
There is a a way. Whenever you need to flash to stock you must use following stock. http://forum.xda-developers.com/showthread.php?t=818439
This is same as normal stock posted by DG except that it includes sbl.bin that we (1008) need. I use it everytime and 3 button combos for Download, Recovery work great.
silverslotcar said:
But if you had a batch 1008 captivate and you messed up during and Odin flash to stock then your screwed bcuz Odin one click swaps the sbl.bins to make your button combinations impossible. ADB would work but you obviously can't access that. I too have a 1008 and it sucks, that is why I bought a jig.
Click to expand...
Click to collapse
it seems like this is not my case
I'm still looking for other people who had my case, and recovered (even with the JTAG riff box) or at least find someone who know's what we shouldn't do, so we don't break our phones.
so whats batch 1008?
This happened to me last night. I was trying to flash the Darky port via CWM and during the flash it became unresponsive. I had to pull the battery. This caused 2 different things. Sometimes it would be a never ending loop of boot screens and then others it would just go into recovery where it wouldn't let me do anything.
From here luckily I was able to access download mode by using the "adb reboot download" command. So I then got into dl mode and tried to flash stock (not the 3 button fixed one) and it froze on FACTORYFS (or whatever it is). I had no choice but to pull the battery. Now it won't boot at all. So my assumption is it wiped the bootloader. I'm not 100% sure but I feel that the reason it stopped where it did was because I didn't run odin as admin on my Win7 pc. I read in another thread that someone had the same problem when they didn't do that either.
If you are in a pitch black room and you press power you can see your screen illuminate, it's just very dim.
I have batch 1008 if it makes any difference to anyone.
Either way I'm heading to the device support center in a half hour or so to try to get a replacement. I originally was going to make or order a jig but people are saying it only works if the bootloader is intact. I originally had hopes because one person claimed that they recovered a completely dead phone with it, but upon further reading all others could not. It seems like his phone may not have been completely bricked.
Update:
Just got back from the at&t device support center. They gave me a new phone without any hassle. They asked what was wrong with my phone and I told them that I was trying to update it and now it won't turn on. The guy tried a few combinations of button presses and tried hooking it up to a jig-like device. Nothing worked so he just gave me a refurbished phones. No questions asked. As I was walking out he said a few people have had the same issue so it's not a big deal.
Either way I thought this would help to realize that there is likely no way to get the phone to boot unless you have a jtag handy.
I don't feel safe to flash rom via CWM.
If you really want to do that, delete the bootloader inside the .zip
So i think i killed mine too
so i get black screen, two button combo gives me SEC S5PC110 Test B/d
I opened odin but nothing Is this toast?
I had this exact problem over thanksgiving weekend. My phone was was was hard bricked I was getting the "phone + computer" it took some effort to get it into download but I got it there and when I was recovering with odin the connection got lost the screen went blue and then nothing. It was dead totally unresponsive no charging or boot screen nothing but once I got a black screen with redlines. After a lot of attempts to revive it I gave up called ATT warranty for a replacement. Luckily I opted for the slow mail service and kept reading. Yesterday I saw the above post and now I can say "yes even now your phone is not bricked even though it does NOTHING"
step 1) first thing I did was charge the battery with my replacement phone as the bricked phone was no longer able to charge the battery
step 2) open odin1 click and hooked up the usb to the phone and computer no battery
step 3) inserted the battery holding only volume up+down
step 4) "BOOM" download mode and a happy dance
I posted this in the"read before flashing" thread there are other people who have recovered from this and now I think that the extra trick to this is getting a 100% battery you need this to flash, and state the phone is in now wont charge a battery.
hope this sound encouraging
silverslotcar said:
But if you had a batch 1008 captivate and you messed up during and Odin flash to stock then your screwed bcuz Odin one click swaps the sbl.bins to make your button combinations impossible. ADB would work but you obviously can't access that. I too have a 1008 and it sucks, that is why I bought a jig.
Click to expand...
Click to collapse
It's odd because I keep seeing people saying things like this. I, too, have a 1008 Captivate. My button combos have worked from day one and Odin one click has never messed that up. Maybe I'm just lucky?
Sent from my SAMSUNG-SGH-I897 using XDA App
RKight said:
It's odd because I keep seeing people saying things like this. I, too, have a 1008 Captivate. My button combos have worked from day one and Odin one click has never messed that up. Maybe I'm just lucky?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I believe there's a "fixed" 1008 batch. Not all 1008s are going to have the problem.
norcal einstein said:
I believe there's a "fixed" 1008 batch. Not all 1008s are going to have the problem.
Click to expand...
Click to collapse
Yeah it's either that or just a misconception spread by the community. Both my old captivate and replacement were 1008. I have been able to get into recovery via the power+volume combination. I was also able to get into dl mode using the vol+insert usb combination.
It's possible I just got lucky on both but who knows.
I, and many others have a 1008 that don't go into download or recovery via the button combos without fixing sbl.bin.
Sent from my SAMSUNG-SGH-I897 using XDA App

Stuck on "Warning Bootloader Unlocked" Screen after OTA

I bought my first phone from Swappa a couple days ago, and figured I would go ahead and by a rooted/unlocked RAZR M and start messing with ROMS.
When I booted the phone, and got connected to my WiFi network it said I had an OTA, so I went ahead and installed it, (now I know that one should avoid OTAs on rooted phones), but now its stuck on the Warning Bootloader Unlocked screen. I do a hard reset (power + volume up/down), it boots, its done, I unlock the screen, it shuts down, repeat. I can't get it unstuck.
This is my first experience with any sort of unlocked or rooted phone, so I have no idea what I'm doing.
Please help
http://www.droidrzr.com/index.php/topic/16812-droid-razr-m-utility-120-windowsmaclinux/ as long as your BOOTLOADER IS UNLOCKED run this
Which option am I supposed to choose (1-6)? I can't boot into it normally, its stuck on the Warning Bootloader Unlocked screen.
Kruger2147 said:
Which option am I supposed to choose (1-6)? I can't boot into it normally, its stuck on the Warning Bootloader Unlocked screen.
Click to expand...
Click to collapse
When your phone turns off hold all three buttons then go into ap fastboot and use option one
Sent from my XT907 using Tapatalk 2
Kruger2147 said:
Which option am I supposed to choose (1-6)? I can't boot into it normally, its stuck on the Warning Bootloader Unlocked screen.
Click to expand...
Click to collapse
You need to be in fastboot, before connecting the phone to the computer and starting the utility. Brandon gave you the key combo to do it.
I got it fixed, and it upgraded to 4.1.2, then went to install Eclipse ROM, the install failed so I hit ++++ back+++++ and then rebooted from the recovery menu, and now it's stuck in the Warning Bootloader Unlocked screen again. Hard reset doesn't work, it reboots back into the Warning screen, and the utility that was posted earlier isn't connecting to recover the device.
What now?
Sent from my SCH-I535 using Tapatalk 2
Kruger2147 said:
I got it fixed, and it upgraded to 4.1.2, then went to install Eclipse ROM, the install failed so I hit ++++ back+++++ and then rebooted from the recovery menu, and now it's stuck in the Warning Bootloader Unlocked screen again. Hard reset doesn't work, it reboots back into the Warning screen, and the utility that was posted earlier isn't connecting to recover the device.
What now?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Boot back into fastboot and use the utility again. The utility won't work unless you're in fastboot, and for heaven's sake, make a backup of your stock ROM, before flashing anything new. If you had a saved ROM, this would be easy. After Eclipse failed to install (it has been well documented that a straight install of Eclipse through TWRP or CWM usually won't install), you could have easily gone to the main menu in recovery and clicked "restore" and restored with zero issues.
Kruger2147 said:
I got it fixed, and it upgraded to 4.1.2, then went to install Eclipse ROM, the install failed so I hit ++++ back+++++ and then rebooted from the recovery menu, and now it's stuck in the Warning Bootloader Unlocked screen again. Hard reset doesn't work, it reboots back into the Warning screen, and the utility that was posted earlier isn't connecting to recover the device.
What now?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
always make a backup man, safe yourself some time.
I can get it to boot into Fastboot no problem, but when I go to run the script its not recognizing that the phone is connected. The phone says "Connect USB
Data Cable" even when its connected. I'm not sure which side is failing to see the connection, the phone or computer.
Kruger2147 said:
I can get it to boot into Fastboot no problem, but when I go to run the script its not recognizing that the phone is connected. The phone says "Connect USB
Data Cable" even when its connected. I'm not sure which side is failing to see the connection, the phone or computer.
Click to expand...
Click to collapse
Make sure your driver's are up to date
Sent from my XT907 using Tapatalk 2
I'm running Fuduntu Linux, the script worked the first time, but not the second. I'll trying running it on my girlfriends computer with Windows when I get home tonight.
EDIT: Never mind my girlfriend fixed it while as was at work, looks like my computer was being stupid. Thanks for all your help guys.
Sent from my SCH-I535 using Tapatalk 2
how did you get out the stuck mode..
Kruger2147 said:
I'm running Fuduntu Linux, the script worked the first time, but not the second. I'll trying running it on my girlfriends computer with Windows when I get home tonight.
EDIT: Never mind my girlfriend fixed it while as was at work, looks like my computer was being stupid. Thanks for all your help guys.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
hi, can you tell me how did you get out from the stuck mode, i am in the stuck mode now..

[HELP] SGH-I337M Boots first into D/L Mode

I have a phone I am fixing for a friend, so I don't have a complete accurate history of what happened, so please bare with me.
Basically, you put the battery in and it boots right to download mode (Factory Mode), no power button required. I can then reboot it using the power, hold down the Vol-Down button and then I am prompted if I want to enter D/L mode, in which you can use Vol-Down to cancel and it boots like normal.
I have tried the following, nothing fixes it!
Factory Wipe
Root using CF-Auto Root
Every Key Combination Possible on Boot
Odin Stock Install
Kies Upgrade (just stalls on that)
It was not rooted when I got it, and now it is. I haven't installed any recovery yet, but am willing too. It has possible water damage, so it ain't going back to the store anytime soon. I can't even get USB Debugging to appear that it is connected, nor will ADB recognize it. But the USB is working and read/writing.
This isn't my first time working with this sort of stuff, I am just at my wits end, plus I'm a Sony/HTC/LG person, so if there is something I am missing with this wonderful(ly crappy) bootloader, let me know.
Thanks in advance!
shroomun said:
I have a phone I am fixing for a friend, so I don't have a complete accurate history of what happened, so please bare with me.
Basically, you put the battery in and it boots right to download mode (Factory Mode), no power button required. I can then reboot it using the power, hold down the Vol-Down button and then I am prompted if I want to enter D/L mode, in which you can use Vol-Down to cancel and it boots like normal.
I have tried the following, nothing fixes it!
Factory Wipe
Root using CF-Auto Root
Every Key Combination Possible on Boot
Odin Stock Install
Kies Upgrade (just stalls on that)
It was not rooted when I got it, and now it is. I haven't installed any recovery yet, but am willing too. It has possible water damage, so it ain't going back to the store anytime soon. I can't even get USB Debugging to appear that it is connected, nor will ADB recognize it. But the USB is working and read/writing.
This isn't my first time working with this sort of stuff, I am just at my wits end, plus I'm a Sony/HTC/LG person, so if there is something I am missing with this wonderful(ly crappy) bootloader, let me know.
Thanks in advance!
Click to expand...
Click to collapse
If you can hold the vol-down and home button when you boot it up and get into Odin mode you should be about to flash the stock MD5 for your phone. Stock Canadian Odin files here:
http://forum.xda-developers.com/showthread.php?t=2269304
Also make sure to use the lastest version of Odin, 3.07 I believe. After you are done flashing with Odin you will have to boot into Recovery (vol-up when booting) and do a factory reset. This has always fixed any boot problems with my phone.
Jdiesel87 said:
If you can hold the vol-down and home button when you boot it up and get into Odin mode you should be about to flash the stock MD5 for your phone. Stock Canadian Odin files here:
http://forum.xda-developers.com/showthread.php?t=2269304
Also make sure to use the lastest version of Odin, 3.07 I believe. After you are done flashing with Odin you will have to boot into Recovery (vol-up when booting) and do a factory reset. This has always fixed any boot problems with my phone.
Click to expand...
Click to collapse
So did you go into settings, more, developer mode to check usb/debug?
USB debugging isn't required to flash the Odin MD5. One thing I did notice is that you should boot into Odin download mode before connecting your USB cable. I was having issues with Odin not detecting my phone and waiting to connect the USB cable solved that.
Sent from my Nexus 7 using xda app-developers app
sloanster said:
So did you go into settings, more, developer mode to check usb/debug?
Click to expand...
Click to collapse
Duh...
I was referring going to adb fastboot
see the thing is that flashing did work fine, it just didn't fix the problem. I guess in Samsung terms I am stuck in Odin download mode when turning the phone on. This is why I wanted to see of I could push some standard reboot command via adb to see of it would "jig" it into place, but no matter what I try it always boots into download mode first.
and yes, I did turn on usb debugging
shroomun said:
see the thing is that flashing did work fine, it just didn't fix the problem. I guess in Samsung terms I am stuck in Odin download mode when turning the phone on. This is why I wanted to see of I could push some standard reboot command via adb to see of it would "jig" it into place, but no matter what I try it always boots into download mode first.
and yes, I did turn on usb debugging
Click to expand...
Click to collapse
Could you have bent pins maybe where you plug it in? Its doing exactly what a jig would do..
TheAxman said:
Could you have bent pins maybe where you plug it in? Its doing exactly what a jig would do..
Click to expand...
Click to collapse
Nothing is wrong with the pins, USB is working fine and can be used in any other mode. I got ADB finally, I guess it was just not playing nice with me before. However, still anything I try the bloody thing still insists on booting first into download mode.
Just an update, it is still booting into download mode, tried a couple different stocks and still no good result. Anyone suggest any of the options in Odin might help work? Like F Reset Time or Phone EFS Clear?
shroomun said:
Just an update, it is still booting into download mode, tried a couple different stocks and still no good result. Anyone suggest any of the options in Odin might help work? Like F Reset Time or Phone EFS Clear?
Click to expand...
Click to collapse
I have seen this elsewhere, one guy suggested, using Keis, and it took him 2-3 times to get the stock to stick.
As far as checking those items in odin, could brick the phone. he also said, he got nowhere using odin in this situation.
Have you tried maybe flashing a recovery via odin? could be the recovery is corrupt.
what does this mean: in which you can use Vol-Down to cancel and it boots like normal. <<< Can you boot to the OS?
I can imagine your frustration here...good luck.
I did try Kies and it would keep getting stuck at 10% (I let it sit overnight) so I had no luck with that...
Have you tried maybe flashing a recovery via odin? could be the recovery is corrupt.
what does this mean: in which you can use Vol-Down to cancel and it boots like normal. <<< Can you boot to the OS?
Click to expand...
Click to collapse
Yes, I have gone from stock recovery to CMW and back to Stock and still nothing. As for you other question, yes, I can boot into Android. The downside is I can't turn the phone off unless the battery is pulled out. This is why I bought an HTC One and not an S4 lol .. thank god this isn't my phone, but it is frustrating because of all the things I've tried to do to fix it.

lg mobile support tool stuck at 49%

i tried going back to stock firmware using the method in general section but i always seem to get an error at 49%. can someone explain how to get passed this.
i using the t-mobile d801.
also my recovery seemed to have gotten erased because i cant boot into twrp anymore.
LG G2 Stuck @ 49%
El Killer said:
i tried going back to stock firmware using the method in general section but i always seem to get an error at 49%. can someone explain how to get passed this.
i using the t-mobile d801.
also my recovery seemed to have gotten erased because i cant boot into twrp anymore.
Click to expand...
Click to collapse
HEY! I'm on the d801 as well and I've been where you're at a number of times, unfortunately. But I've always gotten out. Here's the conclusion I've reached. Trying to flash directly back to stock without wiping all the partitions first is what makes the RDTool get stuck. It's like the phone runs out of memory and can't host a full Gig+ of data since your last ROM is in the way. Sorry if I'm wrong but I'm only assuming you didn't wipe everything except the Internal storage. The good thing every time this has happened to me is that your recovery partition should be intact. Mine always is, and we're on the same variant. Another thing, booting back into recovery is not impossible. It's all in the timing it takes from the first time you see the LG logo while holding volume - and the power button, but don't let go. What worked for me was to let the phone cycle between off and boot power states twice until the phone is completely off again. You may even notice the LED indicator flash red. Release your keys if the phone stays off and immediately hold the combo down again until the phone tries to boot again just don't let go of the buttons. Once it powers down again, leave the phone alone for a few minutes. Come back and this time get ready to boot into recovery. The combo button press will initiate boot but don't let go until the next time you see the LG logo flash, then quickly release and depress the vol down power up combo and hold. May take a minute longer than usual but the reset menu should pop up thereafter. Tap power 2 more times and you should back into recovery. It's worked every time for me. Let me know if you're good and whether this helped!
Good Luck,
tinydynamite00
try with x86
El Killer said:
i tried going back to stock firmware using the method in general section but i always seem to get an error at 49%. can someone explain how to get passed this.
i using the t-mobile d801.
also my recovery seemed to have gotten erased because i cant boot into twrp anymore.
Click to expand...
Click to collapse
i had exact same issue that progress stucked on 49%. if you are using 64bit OS, try to flash it with 32bit(x86) OS
good luck
tinydynamite00 said:
HEY! I'm on the d801 as well and I've been where you're at a number of times, unfortunately. But I've always gotten out. Here's the conclusion I've reached. Trying to flash directly back to stock without wiping all the partitions first is what makes the RDTool get stuck. It's like the phone runs out of memory and can't host a full Gig+ of data since your last ROM is in the way. Sorry if I'm wrong but I'm only assuming you didn't wipe everything except the Internal storage. The good thing every time this has happened to me is that your recovery partition should be intact. Mine always is, and we're on the same variant. Another thing, booting back into recovery is not impossible. It's all in the timing it takes from the first time you see the LG logo while holding volume - and the power button, but don't let go. What worked for me was to let the phone cycle between off and boot power states twice until the phone is completely off again. You may even notice the LED indicator flash red. Release your keys if the phone stays off and immediately hold the combo down again until the phone tries to boot again just don't let go of the buttons. Once it powers down again, leave the phone alone for a few minutes. Come back and this time get ready to boot into recovery. The combo button press will initiate boot but don't let go until the next time you see the LG logo flash, then quickly release and depress the vol down power up combo and hold. May take a minute longer than usual but the reset menu should pop up thereafter. Tap power 2 more times and you should back into recovery. It's worked every time for me. Let me know if you're good and whether this helped!
Good Luck,
tinydynamite00
Click to expand...
Click to collapse
still no luck
El Killer said:
still no luck
Click to expand...
Click to collapse
OK. So tell me, what ROM were you on, which recovery version and name are you using, why were you flashing back to stock, i.e. were you having problems, what kind. Explain as much as you can in detail. Need to retrace your exact steps to best get you fixed up!
tinydynamite00
tinydynamite00 said:
OK. So tell me, what ROM were you on, which recovery version and name are you using, why were you flashing back to stock, i.e. were you having problems, what kind. Explain as much as you can in detail. Need to retrace your exact steps to best get you fixed up!
tinydynamite00
Click to expand...
Click to collapse
i was using pa4.0 and wanted to go back to stock because i preffered the lg ui. i had twrp 2.6.3.5 i restored my back up of stock but when i rebooted i got into fastboot mode.
twrp wasnt working after i had restored my back up go straight to fastboot was stuck in fastboot until i found a thread explaining how to get out of fastboot and restore download mode.
managed to get download mode working and tried to flash stock with mobile support tool and got the 49 percent error,
my phone never really displayed any progress just says download mode with a white box and blue dots
El Killer said:
i was using pa4.0 and wanted to go back to stock because i preffered the lg ui. i had twrp 2.6.3.5 i restored my back up of stock but when i rebooted i got into fastboot mode.
twrp wasnt working after i had restored my back up go straight to fastboot was stuck in fastboot until i found a thread explaining how to get out of fastboot and restore download mode.
managed to get download mode working and tried to flash stock with mobile support tool and got the 49 percent error,
my phone never really displayed any progress just says download mode with a white box and blue dots
Click to expand...
Click to collapse
K, now if you're only seeing the blue dots when you attach by USB your phone to PC, then you're not fully in DL mode to process the kdz. You should see a white wheel in the center of the screen when you connect and a viewing mirror near the base of your phone with ROOTED in red directly below that. And you're sure your PC is detecting your phone? You've the drivers installed? Because when RDT tells you to run the tool, you'll see some binary code in the viewing window I spoke of, the white wheel will turn and below it will be shown the COM port to which you're connected and a solid thin red bar will begin to fill a space in the viewer showing you the progress.
Also, be sure when attempting the first steps I gave you to boot into recovery that you are not USB connected. It won't work.
And, try to remember if your phone was well enough charged, should have been at least 80% full. It happened to me once that I couldn't boot recovery and my phone would go to fastboot like yours until I left it alone to charge and then I repeated the stepsvi laid out to get back into recovery. This part is paramount!
Please READ CAREFULLY
I used to be in your same situation. I thought I had bricked my phone for good. I finally figured it out. Here is my solution from my Thread.
Esteef said:
Okay, after 12+ hours of trying every method possible on XDA I finally resolved my issue. I will update the first post just incase any others care or fall into the same dilemma I was in.
The LG Mobile Support tool would not download the firmware and it would NOT ask me for my IMEI to download it either.
So my solution....
***
Installed LG Mobile Support Tool then Installed the LG Drivers. (FROM HERE http://forum.xda-developers.com/showthread.php?t=2471370
BEFORE I connected the phone to the computer. I opened the LG Mobile support tool clicked (Options on the top right).
When the dropped down opened, I clicked the (Upgrade Recovery) option. THEN, is when the prompt opened to ask me what my IMEI is.
Before I entered my IMEI, I connected my phone to the computer in download mode, then proceeded to enter my IMEI and hit OK.
This is when the LG Mobile Support tool SUCCESSFULLY downloaded the latest official LG firmware and installed it.
*** BE AWARE, with the phone connected to the PC, the prompt NEVER appeared to enter my IMEI.
*** But with the phone disconnected, the prompt came up every time. This might be the trick for some people.
*** with the IMEI prompt opened, I then connected the phone , entered the IMEI, then hit OK. BOOM HERPES....
Well I'll polish this up more later. I hope this works for every LG G2 Variant and not just the T-Mobile one (D801)
-Esteef
Click to expand...
Click to collapse
THIS WILL WIPE YOUR PHONE COMPLETELY...
tinydynamite00 said:
K, now if you're only seeing the blue dots when you attach by USB your phone to PC, then you're not fully in DL mode to process the kdz. You should see a white wheel in the center of the screen when you connect and a viewing mirror near the base of your phone with ROOTED in red directly below that. And you're sure your PC is detecting your phone? You've the drivers installed? Because when RDT tells you to run the tool, you'll see some binary code in the viewing window I spoke of, the white wheel will turn and below it will be shown the COM port to which you're connected and a solid thin red bar will begin to fill a space in the viewer showing you the progress.
Also, be sure when attempting the first steps I gave you to boot into recovery that you are not USB connected. It won't work.
And, try to remember if your phone was well enough charged, should have been at least 80% full. It happened to me once that I couldn't boot recovery and my phone would go to fastboot like yours until I left it alone to charge and then I repeated the stepsvi laid out to get back into recovery. This part is paramount!
Click to expand...
Click to collapse
yeah my computer does recognize my phone. but i cant run adb or fastboot anymore. all drivers are installed also.
i never got the while wheel or any progress indicator. so i guees im not really in download mode.
i let my phone charge for a few hours and try your method again and let you know what happens
El Killer said:
yeah my computer does recognize my phone. but i cant run adb or fastboot anymore. all drivers are installed also.
i never got the while wheel or any progress indicator. so i guees im not really in download mode.
i let my phone charge for a few hours and try your method again and let you know what happens
Click to expand...
Click to collapse
Sounds good. A full charge can make all the difference. I learnt the hard way! One or more of us will be along should you need further help.
I do hope you get this sorted! I've come back from the brink too many times to not believe you won't.
tinydynamite00
Do as esteef recommended..
Sent from my LG-D802 using XDA Premium 4 mobile app
Falaco147 said:
Do as esteef recommended..
Sent from my LG-D802 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
im trying but i get a battery to low error. i guess i need to charge it longer
i owe you all a million thanks for helping me unbrick my phone. i really thought i was left with a paper weight and then i tried esteefs method again i really owe you guys thank you for the support
El Killer said:
i owe you all a million thanks for helping me unbrick my phone. i really thought i was left with a paper weight and then i tried esteefs method again i really owe you guys thank you for the support
Click to expand...
Click to collapse
You are welcome... The first time I did it too my battery was at 28% and I panicked since I got the low battery error.
I could of sworn that my phone officially became a paper weight. My heart dropped.
I'm glad you are up and running with the rest of us!
-Esteef
1732359994
hey !
I have the same problem, but... I can't acces to the recovery :/ i tried to install CWM (with Freegee) over Team win recovery and... boot loop :
The rom 4.2.2 flex was gone, no boot animation
-When i pres volum down + power, i have the reset menu, but after that, there is a black screen and it's written at the top left "started usb_start Fastboot Mode ()"
Please, i need your help, i'm so afraid !!
Thx !
Esteef said:
I used to be in your same situation. I thought I had bricked my phone for good. I finally figured it out. Here is my solution from my Thread.
THIS WILL WIPE YOUR PHONE COMPLETELY...
Click to expand...
Click to collapse
I know this thread is a bit old, but it saved my butt. Your method worked perfectly. Thank you for this post.
My LG F460 was bricked (error 570), only download mode was working. Esteef method works fine even my pictures and programs was saved. Thanks!

been working 2 days many hours to resolve PLEASE HELP!

"Power On This Pops Up As A Black Screen"
ap fastboot Flash Mode (s)
10.9B(*) (sha-61146a2, 2014-07-29 2:30:05)
eMMC Info: Size 8GB
Device is LOCKED, Status Code:0
Battery OK
Connect USB
Data Cable
Fastboot Reason: Sticky bit factory_fastboot
------------------------------------------------------------------------------------------------------------------
The Version Is 4.4.2 of the operating system
when i press the power button this happens, i can however hold the power button and both volume buttons to get into the operating system, by loading normally, I need to fix this issue so i can take another swing at trying to mod this razr-m xt907
the previous issue, before i made it to this issue was
Fastboot Reason: fastboot failure this happens if you mess up and try to towel root from your phone as in download the file onto your phone and then run the file from your phone, so any user out there trying to root their phone, that is not the way to go. Also I Am Dubbing This The Screen of Black Death!
As per Rooting the Phone, I tried Using "motofail2go" I press enter the App communicates with the phone then the dameon Starts, after that nothing at all happens i let it sit for 15-20 minutes and nothing happens
please help me figure this out, my goal is to put cmod on my phone, it is locked and unrooted at the moment, it has full charge and something has went wrong taking the above information walk me through it please, im on my knees begging. Ill even donate some money on the first of the month if we can get it working.
just_guy said:
"Power On This Pops Up As A Black Screen"
ap fastboot Flash Mode (s)
10.9B(*) (sha-61146a2, 2014-07-29 2:30:05)
eMMC Info: Size 8GB
Device is LOCKED, Status Code:0
Battery OK
Connect USB
Data Cable
Fastboot Reason: Sticky bit factory_fastboot
------------------------------------------------------------------------------------------------------------------
The Version Is 4.4.2 of the operating system
when i press the power button this happens, i can however hold the power button and both volume buttons to get into the operating system, by loading normally, I need to fix this issue so i can take another swing at trying to mod this razr-m xt907
the previous issue, before i made it to this issue was
Fastboot Reason: fastboot failure this happens if you mess up and try to towel root from your phone as in download the file onto your phone and then run the file from your phone, so any user out there trying to root their phone, that is not the way to go. Also I Am Dubbing This The Screen of Black Death!
As per Rooting the Phone, I tried Using "motofail2go" I press enter the App communicates with the phone then the dameon Starts, after that nothing at all happens i let it sit for 15-20 minutes and nothing happens
please help me figure this out, my goal is to put cmod on my phone, it is locked and unrooted at the moment, it has full charge and something has went wrong taking the above information walk me through it please, im on my knees begging. Ill even donate some money on the first of the month if we can get it working.
Click to expand...
Click to collapse
You can fix the sticky bit issue pretty easily through another fastboot command. The command is: fastboot oem fb_mode_clear - Check out this thread for all the details. http://forum.xda-developers.com/showpost.php?p=41706009&postcount=2
Alternatively, a full reflash of the firmware generally fixes the issue.
Sent from my Moto X 2014 Pure Edition using Tapatalk
xKroniK13x said:
You can fix the sticky bit issue pretty easily through another fastboot command. The command is: fastboot oem fb_mode_clear - Check out this thread for all the details. http://forum.xda-developers.com/showpost.php?p=41706009&postcount=2
Alternatively, a full reflash of the firmware generally fixes the issue.
Sent from my Moto X 2014 Pure Edition using Tapatalk
Click to expand...
Click to collapse
I know its been a long time but um here is a belated thank you! I did in fact solve the issue thanks to xda and you, so truly thank you

Categories

Resources