Database Users

[Q] Deleted Settings .apk Now phone constantly restarts

I was cleaning up my phone with Root Explorer and was trying to get rid of the clutter that was in the App section. Now my phone is stuck in a constant loop of restarts. The only way to power it off is pull the battery. Any ideas on how to fix this? Please let me know what information you need.

you need to boot into Download mode, open up ODIN and flash back to stock. you made a big mistake deleting that

How do I boot into download mode? Is that like Android system recovery?

Adb reboot download
Sent from my SGH-T959 using XDA App

No its diffrent, have your phone off, connect it to your computer, pressdown volume down and power, as soon as you see a black screen let go of the power button not the volume down. Or when your phone restarts if you can see the t-mobile screen showing its powering down do this,connect the usb as soon as you the tmobile logo then after the battery charing screen shows up press volume up and down and power. Once you see the black screen let go. It may take a few tries but it works.
Sent from my SGH-T959 using XDA App

I would search this forum for a how to on using Odin and download necessary files to flash your phone.
Good luck.
Sent from my SGH-T959 using XDA App

I'm running Odin right now following the proper link. It's just sitting at file analysis. Any idea how long it takes to work?

apathy311 said:
I'm running Odin right now following the proper link. It's just sitting at file analysis. Any idea how long it takes to work?
Click to expand...
Click to collapse
If you are stuck there then its not working. What operating system are you using? And is it 32bit or 64Bit

I am running Windows 7 64-bit.

apathy311 said:
I am running Windows 7 64-bit.
Click to expand...
Click to collapse
People have reported problems with 64bit systems. Apparently, Odin is a POS. I use an old 32bit XP laptop for this stuff, works as good as Odin ever does.

Well now my phone is stuck at the "Phone + ! + PC" screen. I've pulled the battery, held every button combination possible, plugged and unplugged my phone while doing so and nothing works. I'm thinking I'm going to have to bring it to a T-Mobile store and exchange it.

Yet another person that borks their phone and has someone else pay for it .... sigh
Sent from Samsung Vibrant

apathy311 said:
Well now my phone is stuck at the "Phone + ! + PC" screen. I've pulled the battery, held every button combination possible, plugged and unplugged my phone while doing so and nothing works. I'm thinking I'm going to have to bring it to a T-Mobile store and exchange it.
Click to expand...
Click to collapse
They will probably tell you your warranty is now void, especially if you mention you deleted the settings.apk. Even if you don't, someone at the store will likely know you did something you shouldn't of and will want to send it out.
You should be able to get into downloader/bootloader mode and reflash the stock rom using the instructions on the last page still though. I find it weird that you can't, but I'm not going to try that out on my phone just to test it.
LESSON TO ALL: If you do not know what you are doing, do not go around deleting system .apk files. Deleting the settings.apk file is like deleted the windows folder on a windows machine.

You shouldn't take it back to the store. You should really just get on a 32bit system and flash a stock ROM in Odin.
Have you verified that you're getting into download mode correctly?

apathy311 said:
Well now my phone is stuck at the "Phone + ! + PC" screen. I've pulled the battery, held every button combination possible, plugged and unplugged my phone while doing so and nothing works. I'm thinking I'm going to have to bring it to a T-Mobile store and exchange it.
Click to expand...
Click to collapse
that is very easy to fix, just unplug the usb and re plug and hold the two volume buttons and then power and when it turns black leet go of power. This SHOULD work because i had that message too and this fixed it.,
i have heard that you must disable something on your computer first by restarting it and pressing f8 to disable some driver setting and it should get odin to work

or try puching settings apk with adb? but im guessint this guy cant use adb

Help or Free Defy, just pay shipping

Hey All,
I'm sick and tired of flashing SBFs to my Defy. I made a mistake and didn't flash the CM7 kernel after flashing CM10 and Gapps and now it's doing the 'blank screen unless you flash a SBF in RSDlite' nonsense. I've flashed a million SBFs, none of them work. I cannot get anywhere except the bootloader mode with the blank screen. The battery is charged, etc.
If someone has a step or two I can try, I'm game; but if no one can help, Imma shoot it (or ship it to someone if they want it).
Thanks dudes.
I hate motorola.

Use this chinese, it will work no matter what.
http://www.mediafire.com/?vbcv0lhopulntx8
---------- Post added at 08:05 PM ---------- Previous post was at 08:01 PM ----------
Unless you really want to ship it to me, then I'm game. I need a new defy cause mine is kinda busted. The earpiece doesnt work and the lighted buttons at the bottom dont work too well, I had to install CM10 for on screen navigation. I can provide the shipping address for you and stuff.

It really doesn't boot to the bootlogo or bootanimation? Have you tried entering stock recovery and wiping data and cache? That's a must for a stock ROM to work after using a custom one... Get your battery out; hold volume down + power button and insert the battery while holding; keep holding and it should enter stock recovery after a couple of seconds at the red M splash screen. Then press both volume keys at the same time for the menu to show up!

Darin_Ram said:
Use this chinese, it will work no matter what.
http://www.mediafire.com/?vbcv0lhopulntx8
Click to expand...
Click to collapse
He's right.
I don't know how many times that Chinese SBF got me unbricked. Always did the trick for me.
The only thing is: you'll be stucked with BL7 forever.
But that doesn't prevent you from using other Custom ROMs, just from using the usual SBF files provided by other carriers.
If you'r willing to try, here's a step-by-step guide:
http://forum.xda-developers.com/showthread.php?t=1542956

First of all,
Thanks so much for your help so far guys, I really appreciate it.
Lorenard said:
He's right.
I don't know how many times that Chinese SBF got me unbricked. Always did the trick for me.
The only thing is: you'll be stucked with BL7 forever.
But that doesn't prevent you from using other Custom ROMs, just from using the usual SBF files provided by other carriers.
If you'r willing to try, here's a step-by-step guide:
http://forum.xda-developers.com/showthread.php?t=1542956
Click to expand...
Click to collapse
Alright, so I flashed the file, but I have the same issue. The phone does not do anything with any type of button combination, however if I plug it into a computer, I can flash a file to it and the screen shows the progress. That's all I can get to show on the screen at all. I have 2 batteries of good condition and an external battery charger.
Any ideas?

andjohn said:
I can flash a file to it and the screen shows the progress. That's all I can get to show on the screen at all. I have 2 batteries of good condition and an external battery charger.
Click to expand...
Click to collapse
Flash the chinese SBF in RSD lite, the progress bar (on your PC) should count to 100% twice. It will then reboot your phone for you.
Do not unplug your phone before RSD lite says finished.. And yes, wiping in stock recovery is a must.
Don't lose hope on your defy, it is almost impossible to brick

viki1296 said:
Flash the chinese SBF in RSD lite, the progress bar (on your PC) should count to 100% twice. It will then reboot your phone for you.
Do not unplug your phone before RSD lite says finished.. And yes, wiping in stock recovery is a must.
Don't lose hope on your defy, it is almost impossible to brick
Click to expand...
Click to collapse
Thanks for your replies guys. Ya, I did this and it says PASS but when it says that it's rebooting the phone, it never does. I can't get into the stock recovery to wipe anything Any more ideas? Perhaps I'm holding the wrong buttons?

andjohn said:
Thanks for your replies guys. Ya, I did this and it says PASS but when it says that it's rebooting the phone, it never does. I can't get into the stock recovery to wipe anything Any more ideas? Perhaps I'm holding the wrong buttons?
Click to expand...
Click to collapse
Try doing this:
- once the SBF is flashed, wait for RSD Lite to finish its work
- if it says "Restart the phone manually" remove the battery and unplug the phone
- put the battery back in
- press and hold power and vol- buttons for a few seconds
- release the power button, but keep vol- button pressed
- if it shows a sign with Android guy and a ! in a triangle, release vol- button and press both vol+ and vol- buttons at the same time
- if nothing changes, press the screen at the bottom right corner (just above the magnifying glass, i.e. regular search button)
This should bring up stock recovery from which you should be able to wipe data/cache. This screen should be available by default, but sometimes it's hidden. After wiping the stuff, simply reboot the phone from the recovery.
I hope this helps.

Welp, I'm having some issues with my own Defy as well. So, yesterday I flashed that Chinese SBF. And now I can say that the steps from my previous reply won't work.

My wrong. This method does work http://forum.xda-developers.com/showthread.php?t=1542956
Even though I didn't have an access to stock recovery and didn't wipe everything, the SBF loaded just fine, as well as the second (rooted one). Try that method, andjohn.
However, this didn't solve my problem with the camera, unfortunately, so I'm off to my thread.

andjohn said:
Thanks for your replies guys. Ya, I did this and it says PASS but when it says that it's rebooting the phone, it never does. I can't get into the stock recovery to wipe anything Any more ideas? Perhaps I'm holding the wrong buttons?
Click to expand...
Click to collapse
Probably you are trying to flash an earlier BL version than what is already flashed.
So you probably need to try a BL7 SBF.
If you give up on your Defy give me a price to ship it to Australia. I might take it off your hands.

_ossie_ said:
Probably you are trying to flash an earlier BL version than what is already flashed.
So you probably need to try a BL7 SBF.
If you give up on your Defy give me a price to ship it to Australia. I might take it off your hands.
Click to expand...
Click to collapse
Alright, why don't you PM me your address. I have 2 good batteries, a battery charger, and the phone.

Is this phone still available?? Where you from??? I'll pay the shipping My digitalizer broke

Darin_Ram said:
Is this phone still available?? Where you from??? I'll pay the shipping My digitalizer broke
Click to expand...
Click to collapse
Yeah where's the free phone ?:laugh:

Hey! I called dibs! >_<

Hey even i need tht
Darin_Ram said:
Hey! I called dibs! >_<
Click to expand...
Click to collapse
I need battery cover and proximity sensor and can even pay a bit for tht... pls let me know if it is still available..

Possibly Bricked Defy??? Please Help

HEEEEELP!!! I'm in great need of assistance! I'm new to modified roms and I'm at a lose with my Motorola defy (MB525). it seems to be bricked and won't detect in my computer
Here is what i did:
1. I had rooted it with SOC
2. unlocked boot loader
3. I had installed clockwork mod and flashed CM10.1 Android 4.2.2. Everything was working but some of my google play services and data
4. The problem showed up when I tried to upgrade and install CM 10.2 Android 4.3
5. It flashed successfully but very time it would power on, it would forget all the settings. It also wouldn't boot into clockwork recovery mode and would reboot when installing Rom Manager.
6. I tried wiping cache but now it won't even boot up, just black screen.
7. I tried putting the clockwork mod back on but it goes to the andorid boot menu and can't find a custom recovery
8. Now it boots staight to android boot menu, It will not detect in my Mac or friend's PC
9. Downloaded motorola drivers, RSD Lite for pc and tried entering bootloader mode but battery is too low to put in USB transferring mode
10. Tried charging for hours but it is still not charged enough to do bootloader mode, doesn't seem to be charging.
11. When connected to a computer, it detects by displaying a white light but will not boot up to android boot menu.and is not detected by the computer
Not sure what else I can do, any suggestions? Please and thanks!

Similar issue
AlphaXray said:
HEEEEELP!!! I'm in great need of assistance! I'm new to modified roms and I'm at a lose with my Motorola defy (MB525). it seems to be bricked and won't detect in my computer
Here is what i did:
1. I had rooted it with SOC
2. unlocked boot loader
3. I had installed clockwork mod and flashed CM10.1 Android 4.2.2. Everything was working but some of my google play services and data
4. The problem showed up when I tried to upgrade and install CM 10.2 Android 4.3
5. It flashed successfully but very time it would power on, it would forget all the settings. It also wouldn't boot into clockwork recovery mode and would reboot when installing Rom Manager.
6. I tried wiping cache but now it won't even boot up, just black screen.
7. I tried putting the clockwork mod back on but it goes to the andorid boot menu and can't find a custom recovery
8. Now it boots staight to android boot menu, It will not detect in my Mac or friend's PC
9. Downloaded motorola drivers, RSD Lite for pc and tried entering bootloader mode but battery is too low to put in USB transferring mode
10. Tried charging for hours but it is still not charged enough to do bootloader mode, doesn't seem to be charging.
11. When connected to a computer, it detects by displaying a white light but will not boot up to android boot menu.and is not detected by the computer
Not sure what else I can do, any suggestions? Please and thanks!
Click to expand...
Click to collapse
I have a similar problem. My unmodified (not rooted) Defy (running 2.2.1) started to boot loop, so I eventually did a factory reset. That worked for a while, and then suddenly the defy froze on the Moto logo (not even cycling to the Blur screen) and I could no longer get to the reset screen. However I could still get to the bootloader, so I tried to use RDS lite. I got one sbf to say it passed, but the phone did not reboot. Now RDS will detect whether the phone is on or off (and if on I'll get a white LED) and I can flash the sbf still, but otherwise the phone is completely bricked - can't get to reset OR bootloader screen.
Any help would be appreciated greatly!

AlphaXray said:
HEEEEELP!!! I'm in great need of assistance! I'm new to modified roms and I'm at a lose with my Motorola defy (MB525). it seems to be bricked and won't detect in my computer
9. Downloaded motorola drivers, RSD Lite for pc and tried entering bootloader mode but battery is too low to put in USB transferring mode
Click to expand...
Click to collapse
First of all, you need to get the battery charged somehow. Here's some possibilities:
borrow from someone a "defy's battery compatible phone" and charge your battery inside that phone. A Defy or a Defy+ or a DroidX would work.
try to get an external battery charger
WARNING it's potentially dangerous: method B from this post (MacGyver way): http://forum.xda-developers.com/showthread.php?t=892026 :
Then you can go download mode and restore sbf.
---------- Post added at 12:35 PM ---------- Previous post was at 12:31 PM ----------
DefyVictim said:
I have a similar problem. My unmodified (not rooted) Defy (running 2.2.1) started to boot loop, so I eventually did a factory reset. That worked for a while, and then suddenly the defy froze on the Moto logo (not even cycling to the Blur screen) and I could no longer get to the reset screen. However I could still get to the bootloader, so I tried to use RDS lite. I got one sbf to say it passed, but the phone did not reboot. Now RDS will detect whether the phone is on or off (and if on I'll get a white LED) and I can flash the sbf still, but otherwise the phone is completely bricked - can't get to reset OR bootloader screen.
Click to expand...
Click to collapse
Which one sbf have you tried?
Are you sure is the right one? If yes, have you checked if it's corrupted or have your tried to redownload it?

DefyVictim said:
I have a similar problem. My unmodified (not rooted) Defy (running 2.2.1) started to boot loop, so I eventually did a factory reset. That worked for a while, and then suddenly the defy froze on the Moto logo (not even cycling to the Blur screen) and I could no longer get to the reset screen. However I could still get to the bootloader, so I tried to use RDS lite. I got one sbf to say it passed, but the phone did not reboot. Now RDS will detect whether the phone is on or off (and if on I'll get a white LED) and I can flash the sbf still, but otherwise the phone is completely bricked - can't get to reset OR bootloader screen.
Any help would be appreciated greatly!
Click to expand...
Click to collapse
How did RSD recognise your phone if you can't go to the bootloader?

Defy Wiki pages
There is Wiki page here at XDA with a lot of relevant information for Defy/Defy+: http://forum.xda-developers.com/wiki/Motorola_Defy
You may find this informations scattered there, but Wiki is always good starting point.
---------- Post added at 09:09 PM ---------- Previous post was at 08:52 PM ----------
hotdog125 said:
How did RSD recognise your phone if you can't go to the bootloader?
Click to expand...
Click to collapse
There is the answer: http://forum.xda-developers.com/wik...D_lite_to_recognise_a_phone_that_won.27t_boot

DeMonHell82 said:
First of all, you need to get the battery charged somehow. Here's some possibilities:
borrow from someone a "defy's battery compatible phone" and charge your battery inside that phone. A Defy or a Defy+ or a DroidX would work.
try to get an external battery charger
WARNING it's potentially dangerous: method B from this post (MacGyver way): http://forum.xda-developers.com/showthread.php?t=892026 :
Then you can go download mode and restore sbf.
---------- Post added at 12:35 PM ---------- Previous post was at 12:31 PM ----------
Which one sbf have you tried?
Are you sure is the right one? If yes, have you checked if it's corrupted or have your tried to redownload it?
Click to expand...
Click to collapse
_____
When I plug the phone into the USB the white LED comes on, but I can't raise ANYTHING on the screen (reset screen or bootloader screen, holding down the volume up or down w/ the power button). However pressing the power button alone does cause the computer to recognize hardware is plugged in, or alternately disconnected. RSD tells me a device is connected, but the only info given is the bootloader version and AP ID info (whatever that is). However, when I load the SBF, the phone lights up and says SW update in progress...
RSD tells me the phone is being rebooted and has passed, but screen goes dark and all I see i the white LED again.
I have no way of knowing how much juice is left in the battery (I have two, but I think one is dry) or if it is taking a charge..
I tried these two SBFs:
T-Mobile_MB525_6.19.0_1FF.sbf
JORDN_U3_6_36_0_SIGNED_USAJRDNTMOB1B4B5DE1028_0R_JORDANTMO_P022_HWp3_Service1FF.sbf
Only the 1st one works.

DefyVictim said:
When I plug the phone into the USB the white LED comes on
Click to expand...
Click to collapse
just to be sure you know it: when your battery is totally discharged, computer's usb doesn't give enough power to completely boot. (at least for me).

Milan Kerslager said:
There is Wiki page here at XDA with a lot of relevant information for Defy/Defy+: http://forum.xda-developers.com/wiki/Motorola_Defy
You may find this informations scattered there, but Wiki is always good starting point.
---------- Post added at 09:09 PM ---------- Previous post was at 08:52 PM ----------
There is the answer: http://forum.xda-developers.com/wik...D_lite_to_recognise_a_phone_that_won.27t_boot
Click to expand...
Click to collapse
To get RSDLIte to recognize your phone you have to enter boot loader mode. this means press VOL-UP + POWER If nothing helps, try pushing VOL UP before!' you put the battery in (RSDLIte should be running and awaiting a new connection at that time) If you are using Windows 7, try seting RSDLite to "compatibility mode: Windows XP SP3".
@DefyVictim said he could not get into bootloader and yet RSD recognised it.

Pleasa help
Hi.
I wanted to go back to stock ROM from Quarx's CM10 (sep 17) and flashed the next file with RSD, but ended up in bootloop at motorola logo.
DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf
Any ideas which sbf to flash beforemy battery goes down?
Defy plus.
Thanks!!

arvair said:
Hi.
I wanted to go back to stock ROM from Quarx's CM10 (sep 17) and flashed the next file with RSD, but ended up in bootloop at motorola logo.
DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf
Any ideas which sbf to flash beforemy battery goes down?
Defy plus.
Thanks!!
Click to expand...
Click to collapse
Try the Retail Taiwanese SBF.
Sent from my MB526 using Tapatalk

hotdog125 said:
Try the Retail Taiwanese SBF.
Sent from my MB526 using Tapatalk
Click to expand...
Click to collapse
No, it doesn't work, now it doesn't even start to boot...
when i connect the cable it recognizeses, but the screen is black. any ideas?
thanks

arvair said:
No, it doesn't work, now it doesn't even start to boot...
when i connect the cable it recognizeses, but the screen is black. any ideas?
thanks
Click to expand...
Click to collapse
Some SBF should work. Try wiping cache in stock recovery
Sent from my MB526 using Tapatalk

Still stuck
DeMonHell82 said:
just to be sure you know it: when your battery is totally discharged, computer's usb doesn't give enough power to completely boot. (at least for me).
Click to expand...
Click to collapse
So are you saying that my issue might still be a dead battery, despite the fact that my computer and RSD notice when I turn on and off the phone, and even though the phone has enough power to tell me "SW update in progress" when I flash the SBF, and RSD says the flash is a "PASS" and that the phone is being rebooted? I'm really asking, not being sarcastic. Thanks!

DefyVictim said:
So are you saying that my issue might still be a dead battery, despite the fact that my computer and RSD notice when I turn on and off the phone, and even though the phone has enough power to tell me "SW update in progress" when I flash the SBF, and RSD says the flash is a "PASS" and that the phone is being rebooted? I'm really asking, not being sarcastic. Thanks!
Click to expand...
Click to collapse
can't be sure, i'm just guessing.
I just know that the download mode doesn't use as much power as the full android booting up. In fact trying to boot a dead (0%) battery with pc's usb, lead to boot loop in my case or no boot at all.
But of course you need to be sure to have a 70-80% charged battery. Try mcgyver on one of yours.
if this fails you need to check as well with other SBFs

Which SBF
DeMonHell82 said:
can't be sure, i'm just guessing.
I just know that the download mode doesn't use as much power as the full android booting up. In fact trying to boot a dead (0%) battery with pc's usb, lead to boot loop in my case or no boot at all.
But of course you need to be sure to have a 70-80% charged battery. Try mcgyver on one of yours.
if this fails you need to check as well with other SBFs
Click to expand...
Click to collapse
Exactly which SBF should I be using?? (I'm on T Mobile in the US, although I bought the phone unlocked). I had been running Android 2.2.1. The phone was NOT rooted.

DefyVictim said:
Exactly which SBF should I be using?? (I'm on T Mobile in the US, although I bought the phone unlocked). I had been running Android 2.2.1. The phone was NOT rooted.
Click to expand...
Click to collapse
i really don't know which one is the right one for you. i use the one for MB525, Tim italy.
You should carefully check between the lists in this post for your model/carrier :
http://forum.xda-developers.com/showthread.php?t=1216982 (section Official SBFs)
Be careful because MB525 (defy) and MB526 (defy+) have differents SBFs.

DeMonHell82 said:
First of all, you need to get the battery charged somehow. Here's some possibilities:
borrow from someone a "defy's battery compatible phone" and charge your battery inside that phone. A Defy or a Defy+ or a DroidX would work.
try to get an external battery charger
WARNING it's potentially dangerous: method B from this post (MacGyver way): http://forum.xda-developers.com/showthread.php?t=892026 :
Then you can go download mode and restore sbf.
---------- Post added at 12:35 PM ---------- Previous post was at 12:31 PM ----------
Which one sbf have you tried?
Are you sure is the right one? If yes, have you checked if it's corrupted or have your tried to redownload it?
Click to expand...
Click to collapse
I'm not sure it's the right one. It was the T-Mobile for USA one. However it said it passed, so I don't think corruption is the issue.

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!

Nexus 4 Will not boot up

Hi,
My brother is having trouble with his Nexus 4 and I was hoping I could get some help here.
The phone won't go past the boot animation, with the 4 floating balls.
It keeps showing that forever (left it for 20 minutes with charger, phone got really hot but did not get past the animation)
- Never rooted or changed firmware. Only updates from Google. (It was on 5.1.1/5.1/5.0.1)
- Sent to a shop, which claimed it can't be fixed (I do not know the reason they gave him).
My brother thinks it is because a weight was accidently dropped on the phone, but the problem only started 3 days after the incident.
No outer damage can be seen on the device, other then a small brake in the back glass.
Thanks in advance to anyone who will try to help

possibly?
Did you just update and it got stuck at the booting up????

opeller said:
Hi,
My brother is having trouble with his Nexus 4 and I was hoping I could get some help here.
The phone won't go past the boot animation, with the 4 floating balls.
It keeps showing that forever (left it for 20 minutes with charger, phone got really hot but did not get past the animation)
- Never rooted or changed firmware. Only updates from Google. (It was on 5.1.1/5.1/5.0.1)
- Sent to a shop, which claimed it can't be fixed (I do not know the reason they gave him).
My brother thinks it is because a weight was accidently dropped on the phone, but the problem only started 3 days after the incident.
No outer damage can be seen on the device, other then a small brake in the back glass.
Thanks in advance to anyone who will try to help
Click to expand...
Click to collapse
Do you have data on it that you want to keep? If you don't you can try booting into the bootloader and unlock it. Then try flashing a factory image. This will wipe all the data on the phone though so that should probably be a last resort.

ChainFires Son said:
Did you just update and it got stuck at the booting up????
Click to expand...
Click to collapse
No, it did not occur after an update.

theminikiller said:
Do you have data on it that you want to keep? If you don't you can try booting into the bootloader and unlock it. Then try flashing a factory image. This will wipe all the data on the phone though so that should probably be a last resort.
Click to expand...
Click to collapse
I have no important data on it.
Which is the safest way to do this? I'd appreciate it if you would be detailed or refer me to a guide, as I want to be careful.
Where should I download the factory image from?
As the name of it states, I wish to get the one from Google, without any changes or addons from users.

Follow this guide http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
You can download factory images from here https://developers.google.com/android/nexus/images

opeller said:
I have no important data on it.
Which is the safest way to do this? I'd appreciate it if you would be detailed or refer me to a guide, as I want to be careful.
Where should I download the factory image from?
As the name of it states, I wish to get the one from Google, without any changes or addons from users.
Click to expand...
Click to collapse
First we should check if you can boot into the bootloader at all. First turn the device off. Then hold down both the volume buttons and then press and hold the power key. Keep holding all the buttons until you see some different colored text. If that happens we should be able to install a factory image, if it still gets stuck on the Google logo I unfortunately don't have any more ideas.

Tried pressing both volume keys and power button. Google logo show for a second, then black for 2 second, thank flashing red notification light every 1/2 second until I let go of the buttons.
When I release the buttons, the phone goes back to charging battery screen.
I see people suggesting that the red light flashing means a battery problem, but the device keeps trying to boot up while it is not plugged to the charger, unlike what happened to them
Any Ideas why this is happening or what the red light means in this case?

You need to press volume down+power button to get into bootloader. Unplug the charger before doing this.

harishmenace said:
You need to press volume down+power button to get into bootloader. Unplug the charger before doing this.
Click to expand...
Click to collapse
Oh it was just volume down, not both. Heh, sorry.

Use the Nexus Root Toolkit (NRT), it's the easiest way to unlock, root, flash and manage your SuperUser needs!
http://www.wugfresh.com/nrt/

Not sure, but maybe?
You can try using the nexus root kit & unlock your bootloader and see if a factory reset can work. If it does you can always relock it again ☺..Flashing a factory image can work too also ...

Tried volume down+ power button while unpluged from charger.
Google logo show up with vibration, then goes away after 2 seconds, like before, but then the screen goes blank. But red led not flashing.
What should I do now? Even just to use the Nexus Root Toolkit I have to allow Developer mode, which I can't as the phone will not boot up.

opeller said:
Tried volume down+ power button while unpluged from charger.
Google logo show up with vibration, then goes away after 2 seconds, like before, but then the screen goes blank. But red led not flashing.
What should I do now? Even just to use the Nexus Root Toolkit I have to allow Developer mode, which I can't as the phone will not boot up.
Click to expand...
Click to collapse
I'm you can't get into the bootloader then I am unfortunately not aware of any way to help you. If you can't even get into the bootloader I think it is a high probability that it is a hardware problem.

I understand. Thank you for your attempt to help me so far, I apriciate it
Anyone else has any Idea what I can try?

opeller said:
I understand. Thank you for your attempt to help me so far, I apriciate it
Anyone else has any Idea what I can try?
Click to expand...
Click to collapse
First you have to ensure "The Situation" of your phone, diagnostic is very important to decide the kind of medicine or treat. Your N4 booting, stuck on google-logo with red blink, then black screen.
To check : Connect your N4 to PC on linux check on terminal command $ lsusb if output
Bus 001 Device 005: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode),
Click to expand...
Click to collapse
on windows (XP/Vista/7)
Qualcomm something QDL Mode or something like this on "device manager"
Click to expand...
Click to collapse
there is a big hope to revive but very long journey. You are lucky since N4 is very popular device.You can obtain required file like MPRG8064.hex and friends

x1123 said:
First you have to ensure "The Situation" of your phone, diagnostic is very important to decide the kind of medicine or treat. Your N4 booting, stuck on google-logo with red blink, then black screen.
To check : Connect your N4 to PC on linux check on terminal command $ lsusb if output
on windows (XP/Vista/7) there is a big hope to revive but very long journey. You are lucky since N4 is very popular device.You can obtain required file like MPRG8064.hex and friends
Click to expand...
Click to collapse
Hi, thank you for your will to help.
When I turn on the Nexus 4 and connect it to my pc, it show the device as Nexus 4 in device manager.
What do you want me to do?

opeller said:
Hi, thank you for your will to help.
When I turn on the Nexus 4 and connect it to my pc, it show the device as Nexus 4 in device manager.
What do you want me to do?
Click to expand...
Click to collapse
detected as Nexus 4 mean your device well alive. any respons from the phone if you check with adb command ? if the phone give respond to adb you can ask phone to turn to recovery $ adb reboot recovery ...

opeller said:
Tried volume down+ power button while unpluged from charger.
Google logo show up with vibration, then goes away after 2 seconds, like before, but then the screen goes blank. But red led not flashing.
What should I do now? Even just to use the Nexus Root Toolkit I have to allow Developer mode, which I can't as the phone will not boot up.
Click to expand...
Click to collapse
That sounds like the battery is completely empty. Put the device on charger over a night and try then to boot into the bootloader.
Once I had these symptoms (red light flashing) on my N4, it was enough to charge the battery for one hour. Then it booted properly. It's worth trying.

x1123 said:
detected as Nexus 4 mean your device well alive. any respons from the phone if you check with adb command ? if the phone give respond to adb you can ask phone to turn to recovery $ adb reboot recovery ...
Click to expand...
Click to collapse
How do I do that?