Database Users

[Q] alternative way to factory reset?

so heres my dilemma, my gfs droid 2 screen stop responding (cant get it off lock screen). I need to erase everything before I send it back to where I got it, but i cant get into thephone to do a reset and when i boot into recovery, the magnifying glass doesnt seem to work so i cant get past the exclamation point. Is there any other way that I could wipe this phone?

When you see triangle, ! , and android andy
Press both volume buttons, that changed with gb
Sent from my DROID3 using xda premium

what to do when it still won't reboot?
sd_shadow said:
When you see triangle, ! , and android andy
Press both volume buttons, that changed with gb
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
I got this far with my d2. Thanks. After choosing the wipe and reboot option it still boots only to the moto splash screen. it dims a bit after a few seconds and that is all she wrote. I've left it there for an hour.
Any moves to make now? I'd like to get it working. I am willing to learn whatever it takes.
Thanks.

flash sbf
try ezsbf in my list
sd_shadow's list of links for Droid FAQs, SBF, Rooting, ROMs.... https://docs.google.com/document/d/1Goawxdx_UBF4Y8lqzHYWf8Ha3yUcRK4faq0UWIlXLWA/edit
don't leave phone on, if it doesn't boot in 5mins it is not going to boot
and battery will not charge like that
Sent from my XT894 using xda premium

How to Enter Bootloader: (used to flash .sbf recovery images)
Power down the phone.
Slide the keyboard out.
Press and hold the up arrow (↑) key.
Press the lock/power button.
Once the SBF loader screen pops up, release the up arrow key.
is it bootloader D0.11 or D2.37?

help unbrick droid 2
sd_shadow said:
How to Enter Bootloader: (used to flash .sbf recovery images)
Power down the phone.
Slide the keyboard out.
Press and hold the up arrow (↑) key.
Press the lock/power button.
Once the SBF loader screen pops up, release the up arrow key.
is it bootloader D0.11 or D2.37?
Click to expand...
Click to collapse
This is a bootloader screen I get, and it gives me no choices to arrow down.
Bootloader
D2.37
Code Corrupt
Battery Low -- flash
Cannot Program -- flash
This happened after an OTA update, and now I am new to this forum, and trying to get this phone back working, Any help would be greatly appreciated.
I have adb loaded, and have used it to root, su with clockworkmod a CDMA Sprint phone to put into the Page Plus service network, so I have some experience - mostly willing to try just about anything.
The battery should be charged up.
I got this once, after leaving the phone sit for about two days, battery out.
Bootloader
D2.37
Code Corrupt
Battery OK
OK to Program
Connect USB
Data Cable
I mainly use this phone for VoIP service, but was eventually going to try to put Cyanogenmod 7 on it, and then this happened.
Any advice / help / pointers to somewhere, or something would be greatly appreciated.

s1x8 said:
This is a bootloader screen I get, and it gives me no choices to arrow down.
Bootloader
D2.37
Code Corrupt
Battery Low -- flash
Cannot Program -- flash
This happened after an OTA update, and now I am new to this forum, and trying to get this phone back working, Any help would be greatly appreciated.
Click to expand...
Click to collapse
update failed
I have adb loaded, and have used it to root, su with clockworkmod
Click to expand...
Click to collapse
phone needs to be complete stock or update will fail
a CDMA Sprint phone to put into the Page Plus service network, so I have some experience - mostly willing to try just about anything.
The battery should be charged up.
Click to expand...
Click to collapse
usually battery will not charge, when the code is corrupted
I got this once, after leaving the phone sit for about two days, battery out.
Bootloader
D2.37
Code Corrupt
Battery OK
OK to Program
Connect USB
Data Cable
Click to expand...
Click to collapse
you can try flashing 1FF-p2a_droid2_cdma_droid2-user-2.3.3-4.5.1_57_DR2-31-110719-release-keys-signed-Verizon-US.sbf.zip with rsd lite hopefiully the battery is charged enough,
if flash fails because of low battery you will need on of the following
Spare Battery Charger for Motorola Droid 2
a charged spare battery
TBH Factory Adaptor
I mainly use this phone for VoIP service, but was eventually going to try to put Cyanogenmod 7 on it, and then this happened.
Any advice / help / pointers to somewhere, or something would be greatly appreciated.
Click to expand...
Click to collapse

Thank you, and another question for the droid 2
I can't seem to get the drivers to work, I've tried about everything but booting into XP mode - not sure how to do that, as I am on a Windows Vista machine. Any advice, or process for that? I've tried it as Admin, and also a User, but no progress. The drivers are loaded through executing the msi file, but when I plug the phone in the computer doesn't detect phone, and the drivers don't show up in device manager, either.

win 7 64bit?
try Motorola Drivers Installing and Troubleshooting
---------- Post added at 12:41 PM ---------- Previous post was at 12:40 PM ----------
right vista, try the link

s1x8 said:
I can't seem to get the drivers to work, I've tried about everything but booting into XP mode - not sure how to do that, as I am on a Windows Vista machine. Any advice, or process for that? I've tried it as Admin, and also a User, but no progress. The drivers are loaded through executing the msi file, but when I plug the phone in the computer doesn't detect phone, and the drivers don't show up in device manager, either.
Click to expand...
Click to collapse
Spare battery charger on the way!
Also, I ordered a new battery, the old one, was, well, old, and could not hold a charge long enough to get through the flashing step. Once I figured this out, I was able to flash the phone, and then perform a factory reset, and it is back to the original. It wouldn't take the flash for CM but the phone is rooted now.
Thank you for your help!

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..

[Q] HELP! Stuck in Boot Loop, Locked/unrooted

Was on 4.1.2 OTA (yeah I know dumb of me, but it did it overnight), rooted with TWRP all was fine untill I decided to power cycle and got stuck in a boot loop...
Booted to twrp...tried to recover from a back up, still boot loop....Cleared dalvik and all other caches, Still bootloop....factory reset, still no change...
Last resort was to flash using RSDlite v6.1.5 to VRZ_XT907_9.8.1Q-78-1_1FF.xml ...and i'm still bootlooping!!:crying: Now I've lost root, NO Custom recovery with a locked bootloader. I can't push anything through adb cuz bootlloop interrupts windows recognizing the phone and the drivers don't properly install while in Stock Recovery (I do have the latest drivers BTW)...and only sees it as 'MOT SINGLE ADB INTERFACE' while in fastboot.
Question is, what could still be causing it to bootloop?? Anyone know?.. and is there any way to get this fixed and/or get back root and a custom recovery??
At the end of my rope here! Need some guidance....

Alright Guys and Gals I solved the issue (even though I'm not sure how! LOL)
What I did (with simplified instructions)
1. Let it bootloop till the battery ran down...
2. recharged it up to 100%
3. opened it up while still off
4. disconnected battery cable for 5 secs
5. reconnected battery cable
6. started into boot menu (hold POWER and VOL UP & VOL DOWN together) and chose recovery (VOL DOWN to highlight recovery and VOL UP to select it)
7. While in recovery Hold VOL DOWN and tap VOL UP to get the Recovery Menu
8. Chose wipe cache ( VOL buttons to highlight, Power Button to select)
9. then chose wipe data/factory reset
10. rebooted into boot menu again
11. chose Factory option
*12. Held my breath :fingers-crossed:*
AND IT BOOTED!!!:laugh:
Now just to be clear I am not even sure if it was one of these steps or the combination of all of them that got me off the Boot Loop, but I just thought I'd outline them just in case someone stumbles on the same problem I had. Also please note that all this was after I fastboot flashed the 4.1.2 (.78) firmware using RSDLite v6.1.5
Being stuck on on 4.1.2 (.78) Stock is alot better than being stuck in a Boot Loop at least, so I'm happy!
P.S: F.Y.I... I was getting stuck halfway through the boot animation (just about where the droid eye kinda thing closes up) so I could still recharge my Battery from a powered off state (why I had to let it run down to zero, as it was either that or open it up and manually disconnect the battery cable and I was feeling lazy.
Now I have another Logic Board which doesn't boot past the initial Motorola "M" Logo, and thus can't get into recovery or even charge from a powered down state (can only get into fastboot) even though I've successfully flash 4.1.1 to it TWICE!!

meaty0025 said:
Now I have another Logic Board which doesn't boot past the initial Motorola "M" Logo, and thus can't get into recovery or even charge from a powered down state (can only get into fastboot) even though I've successfully flash 4.1.1 to it TWICE!!
Click to expand...
Click to collapse
Do you know what build that logic board is... if its an older version use Matt's utility on it simply swap with your current one and have the joy of an unlocked device... first time I flashed (well almost every time I flash) 4.3 I get stuck on the boot logo and have to use Matt's utility to bring it to life again....
Sent from my XT907 using xda app-developers app

ezknives said:
Do you know what build that logic board is... if its an older version use Matt's utility on it simply swap with your current one and have the joy of an unlocked device... first time I flashed (well almost every time I flash) 4.3 I get stuck on the boot logo and have to use Matt's utility to bring it to life again....
Click to expand...
Click to collapse
That was my initial thought but, Where on the board can I find that info? and doesn't matt's utility in essence perform a fastboot flash, same as RSDlite?? Would love to have an unlocked device or at the very least a working back up board in case of unforeseen accidents, but this one has me stumped...

It won't say it on the board you'll have to install it to the housing n digitizer n get it to boot... I think you can tell by the fast boot menu but I'm not sure what to look for.... n to be honest I have never used rsd I've always used one of Matt's utilities for all my moto devices he has saved several of my phones...
Sent from my XT907 using xda app-developers app

ezknives said:
It won't say it on the board you'll have to install it to the housing n digitizer n get it to boot... I think you can tell by the fast boot menu but I'm not sure what to look for.... n to be honest I have never used rsd I've always used one of Matt's utilities for all my moto devices he has saved several of my phones...
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Utility doesnt seem to work for me for some reason, it just closes when i "hit any key to continue" even flashed it with rsd using the xml from matt's ultilty... Still no go.
It should be an older board though, i bought off ebay with a broken screen just mainly so i could get the pristine back housing off of it (lol) ... and that was in february.
The guy did say he'd dropped a wrench on it breaking the screen while workin on his car, guess it was a bigger wrench than i thought and it damaged the board too :laugh:

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.

Bricked Recovery

Hello All,
I'm not sure how I bricked my recovery, but I did. When i try to boot into recovery via quickboot or power off -> Vol DN + Power. I get the little dead Android guy.
If I leave it connected to my computer and boot into the recovery I get like 15 or 20 little 'new drive' windows that pop up (like putting in a flash drive) except these say they need to be 'Formatted'. Of course I just closed those. There is one drive that you can browse though and it looks like the image files for the phones OS. But I'm not sure what they are...
Anyway, I have tried to do the Full reset (see link)
http://www.droidviews.com/how-to-res...tock-firmware/
and thought that might take care of it... but I still get the little android on his back when I try to boot into the recovery SW.
Oddly enough, you can still hold down the power button to hard shutdown the phone and reboot into the ROM (flashed back to 10b) using the .TOT file and the process in the link above.
Any help would be greatly appreciated!

kaluna00 said:
Hello All,
I'm not sure how I bricked my recovery, but I did. When i try to boot into recovery via quickboot or power off -> Vol DN + Power. I get the little dead Android guy.
If I leave it connected to my computer and boot into the recovery I get like 15 or 20 little 'new drive' windows that pop up (like putting in a flash drive) except these say they need to be 'Formatted'. Of course I just closed those. There is one drive that you can browse though and it looks like the image files for the phones OS. But I'm not sure what they are...
Anyway, I have tried to do the Full reset (see link)
http://www.droidviews.com/how-to-res...tock-firmware/
and thought that might take care of it... but I still get the little android on his back when I try to boot into the recovery SW.
Oddly enough, you can still hold down the power button to hard shutdown the phone and reboot into the ROM (flashed back to 10b) using the .TOT file and the process in the link above.
Any help would be greatly appreciated!
Click to expand...
Click to collapse
Try this:
- unplug your device
- make sure device is completely off (hold and press power button until it turns off completely *when it cycles into the LG logo, continue to hold it and it'll turn off)
- give it a few seconds, then hold "power" + "vol down"
- AS SOON AS LG LOGO APPEARS, let everything go, then ONLY push "power" and hold it
- should take you to a white screen asking if you want to erase data or something, just push "power" once
- should take you into recovery
If this doesnt work, let me know and i'll give you directions on how to unbrick back into stock factory

kaluna00 said:
Hello All,
I'm not sure how I bricked my recovery, but I did. When i try to boot into recovery via quickboot or power off -> Vol DN + Power. I get the little dead Android guy.
If I leave it connected to my computer and boot into the recovery I get like 15 or 20 little 'new drive' windows that pop up (like putting in a flash drive) except these say they need to be 'Formatted'. Of course I just closed those. There is one drive that you can browse though and it looks like the image files for the phones OS. But I'm not sure what they are...
Anyway, I have tried to do the Full reset (see link)
http://www.droidviews.com/how-to-res...tock-firmware/
and thought that might take care of it... but I still get the little android on his back when I try to boot into the recovery SW.
Oddly enough, you can still hold down the power button to hard shutdown the phone and reboot into the ROM (flashed back to 10b) using the .TOT file and the process in the link above.
Any help would be greatly appreciated!
Click to expand...
Click to collapse
took the 11A OTA and it still has the dead android guy on his back when booting into the Recovery (or trying to...)

kaluna00 said:
took the 11A OTA and it still has the dead android guy on his back when booting into the Recovery (or trying to...)
Click to expand...
Click to collapse
Try this thread. It'll help you get back to factory stock.
http://forum.xda-developers.com/showthread.php?t=2432476

monkee012 said:
Try this:
- unplug your device
- make sure device is completely off (hold and press power button until it turns off completely *when it cycles into the LG logo, continue to hold it and it'll turn off)
- give it a few seconds, then hold "power" + "vol down"
- AS SOON AS LG LOGO APPEARS, let everything go, then ONLY push "power" and hold it
- should take you to a white screen asking if you want to erase data or something, just push "power" once
- should take you into recovery
If this doesnt work, let me know and i'll give you directions on how to unbrick back into stock factory
Click to expand...
Click to collapse
In the process of trying this out... I'll let you know how it turns out.

kaluna00 said:
In the process of trying this out... I'll let you know how it turns out.
Click to expand...
Click to collapse
Thanks for the try... but I still get the dead android guy.
Its my wifes phone and she is kinda getting tired of me trying to get a custom rom on it for her...
I did to the TOT flash with the LGFlashTool and it worked to change the ROM, and did something to the recovery.. I was getting a blank screen before the TOT flash, but after when trying to boot into recovery it showed the dead android on his back. Thanks for the thought though.

Moved out of the Development Sections, as this does not belong there.....Thanks.

Ok it returned the recovery back to stock. So this good, just reroot and use freegee to flash recovery
Sent from my VS980 4G using Tapatalk

greatnesstx said:
Ok it returned the recovery back to stock. So this good, just reroot and use freegee to flash recoveryA
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
Freegee says "Your devices specific software version of VS98011A is not currently supported"
do I need the paid version?

Ok You totally can revert back to version VS9810
Sent from my VS980 4G using Tapatalk
---------- Post added at 04:23 AM ---------- Previous post was at 04:22 AM ----------
I just recently bought an Lg f2f and it was version 12, I just used lg flash tool and reverted it back to 10 then I rooted, use freegee and BAM back in business
Sent from my VS980 4G using Tapatalk

greatnesstx said:
Ok You totally can revert back to version VS9810
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
I need to revert back to VS98010a or b for Freegee to work? Id I am on 11a the I would have to do the ADB push?

There are plenty of Roms out there that have rooted stock 12b if you want to be on the latest ota
Sent from my VS980 4G using Tapatalk
---------- Post added at 04:29 AM ---------- Previous post was at 04:25 AM ----------
To be honest once I get a phone I never take an ota, but I know for a fact you can root and use freegee on either or 10a or 10b
Sent from my VS980 4G using Tapatalk

greatnesstx said:
There are plenty of Roms out there that have rooted stock 12b if you want to be on the latest ota
Sent from my VS980 4G using Tapatalk
---------- Post added at 04:29 AM ---------- Previous post was at 04:25 AM ----------
To be honest once I get a phone I never take an ota, but I know for a fact you can root and use freegee on either or 10a or 10b
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
I would love to get to MicroMod's stock 12b rom for her... but I can't get a custom recovery on this darn thing... I normally avoid OTA's as well. but I was hoping that would fix my recovery problem...
It sounds like the TOT flash fixed it though (i just didn't realize it at that point). I thought the little android on his back was a bad thing... but if that is just what happens with the stock recovery, then I was OK and didn't know it. I appreciate your help and input! :highfive:
I'll see if she is happy the way it is or not... right now it is just stock Rom; rooted. maybe that is good enough for her. It just bugs me I couldn't get it to install the way I wanted.

kaluna00 said:
I would love to get to MicroMod's stock 12b rom for her... but I can't get a custom recovery on this darn thing... I normally avoid OTA's as well. but I was hoping that would fix my recovery problem...
It sounds like the TOT flash fixed it though (i just didn't realize it at that point). I thought the little android on his back was a bad thing... but if that is just what happens with the stock recovery, then I was OK and didn't know it. I appreciate your help and input! :highfive:
I'll see if she is happy the way it is or not... right now it is just stock Rom; rooted. maybe that is good enough for her. It just bugs me I couldn't get it to install the way I wanted.
Click to expand...
Click to collapse
Original stock is the 10A; that's what mine was when i first got it. there were a couple of OTA's after that, i think that's the 11-12 variants. So, i'd try with the 10 stock rom first; then reroot, add twrp/CM recovery.