Related
Managed to get my Droid 2 to a point where it will not go beyond the M screen on boot. I've tried pulling the battery over and over again and cannot get to the Clockwork bootstrap. I've also tried plugging it in and pulling the battery many, many times.
So I figure the next best step is to .sbf this mofo.
I've downloaded & installed rdslite, the USB drivers. Also have the Droid 2 .sbf files. Droid.Co_Downloader.exe pulled down RSD Lite v4.8 though rather than 4.7. And the link to 4.7 is now showing as invalid. Will 4.8 work for what I'm trying to do?
Also, when I plug in my phone RSD Lite never shows anything in the devices table. What are the steps to get my phone to show up? Plug in phone, power on, turn on RDS Lite? The tutorial seemed to be aimed at people who still have working phones in that it has you adjusting setting on the phone i.e. enable debug mode.
Sidenote, I know debug mode is disabled on my phone. Does that mean RSD Lite isn't going to work?
Help!
I think if you pull and replace the battery at the M it should reboot into recovery, and if it won't do that you can always try sliding out the keyboard and booting the phone while holding the X key to see if it will dump you into the stock recovery
Ok, some more reading uncovered hitting the physical keyboard's Up arrow and powering on will take the phone to the Bootloader and once in the bootloader my pc recognized it.
And then RSD Lite showed my device in the table but it didn't show up as the A955 it was Model "S Flash OMAP3630 MI".
Currently flashing DROID2_X6_2.2.20 .sbf, hopefully that pans out.
Thanks, I tried the battery pull thing A LOT of times. Never went into bootstrap. Not sure what's going on there.
I tried the stock recovery but got the Android-exclaimation mark icon which I presume means the stock recovery was F-ed up.
Really hope this sbf recovery works.
Ok, disaster averted.
Looks like rebooting into the bootloader was the secret. Hope that is helpful to someone else who's bricked their phone.
BTW, used RSD Lite version 4.8 and that worked with my Droid 2.
aplus01 said:
Thanks, I tried the battery pull thing A LOT of times. Never went into bootstrap. Not sure what's going on there.
I tried the stock recovery but got the Android-exclaimation mark icon which I presume means the stock recovery was F-ed up.
Really hope this sbf recovery works.
Click to expand...
Click to collapse
Glad you got it working! For future reference if you want the stock recovery, after you hold x and get to the exlamation point, press the search key on the keyboard. (The little magnifying glass) and it should take right Into it.
Sent from my DROID2 using XDA App
Me too!
Search key? Good to know. Man, that could have saved me quite a bit of time I think.
So now that I've restored everyting I'm going to risk it all and install the fission rom again.
It's less intimidating now that I know how to sbf restore. Hopefully I won't need to this go round.
Just follow the instructions as they are laid out and you shouldn't run into much trouble. Also, be sure to let the device sit for a bit after you reboot from clockwork, as it could take a good 15 minutes before it fully boots up the first time, and interrupting that could put you back at square one
Could you add [SOLVED] to your thread title please. Thanks
I'm on (or was) Gingerbread "ota" (second leak), and trying to sbf back to 2.340.
Using 2.340 SBF, on RSD lite 4.8, I get the error:
Failed flashing process. Phone[0000]: Error getting subscriber unit checksum. Device API Error: 0xE003003F. Command: RQRCS (0xE403203F); phone connected
Also, I cannot boot into the recovery.
Please help.
Other possibly relevant info:
Windows XP
RSD LIte 4.8
Not rooted (on GB)
Battery pull, only results in loading up the bootloader again (without pressing any buttons)
Bootloader says:
BOOTLOADER
30.04
Code Corrupt
re-download the SBF file (or check the checksum). Attempt to reflash again.
Will Re-Download SBF, however I've used this SBF before successfully.
I'm also now downloading RSD 4.9 rather than 4.8.
found this: Do a battery pull...then hold the home button and power at the same time to get into recovery. Press the search button, and use the volume button to select factory reset. Let it do it's thing, and select reboot system now...after that, it should boot.
snwagner said:
found this: Do a battery pull...then hold the home button and power at the same time to get into recovery. Press the search button, and use the volume button to select factory reset. Let it do it's thing, and select reboot system now...after that, it should boot.
Click to expand...
Click to collapse
I stated in my OP, that I cannot get into recovery. I know how to, but I cannot.
UPDATE:
Did all that was stated above, and was able to SBF.
However, once the SBF got to the rebooting process, it remained in a bootloop.
I am able to get into recovery now. And I did a factory wipe.
Still in bootloop.
SUggestions?
Pull battery...hold volume up and down then power....after about 3 seconds your phone will load up a black screen with white font and other stuff( debugging mode).... then plug usb to pc....load up rsd lite and flash sbf... if bootloops simply boot into recovery and wipe data... i had the same problem as you and this is how i fixed it....
Sent from my DROIDX using XDA Premium App
mr_villagomez said:
Pull battery...hold volume up and down then power....after about 3 seconds your phone will load up a black screen with white font and other stuff( debugging mode).... then plug usb to pc....load up rsd lite and flash sbf... if bootloops simply boot into recovery and wipe data... i had the same problem as you and this is how i fixed it....
Sent from my DROIDX using XDA Premium App
Click to expand...
Click to collapse
If you read my above post, I said that I did basically exactly what you just said. Im still in bootloops.
Oh sorry i thought that person mentioned holding the power button instead of the volume buttons... did you try rebooting your pc before using rsd again? If that doesnt work maybe try uninstalling drivers and rsd then reinstalling again.
Sent from my DROIDX using XDA Premium App
ITS ALIVE!
THE SOLUTION
I factory wiped like 3-4 times and then rebooted and it worked!
doronster195 said:
ITS ALIVE!
THE SOLUTION
I factory wiped like 3-4 times and then rebooted and it worked!
Click to expand...
Click to collapse
I joined the party late. Yea cwm sometimes wipes like a dirty person. I would always recommend doing it a few times when switching roms or in your case. It can't hurt the phone and sometimes the first wipe doesn't work.
im having the same problem!!!
except im STUCK on the
home+volume up+power screen
i used the same sbf i did the first time from the leaked gb and it worked fine
and well i downloaded nightlies to get liberty on my phone, and i wasnt a big fan of the text msg layout so i tried to clockwork mod (flash) into the deoxed gb but i still had a liberty boot and i thought nothing of it so i continued on and the phone worked fine itll it said gbkeyboard failed and i couldnt do anything!
so i turned it off and when i turned it back on flashwork was on!!! so i flashed the gb leak without root (the first one) and then i wanted root so i did the sbf but this time it said fail and my screen said it was still installing so i pulled the usb and the phone still said installing
so i battery pulled and my phone said code corrupted
so i tried the sbf back x3 still getting the same fail then i got to the part im at now,
code corrupted
battery low
cannot program
i left it on the charger for like an hour and its still "low"
am i soft bricked or hard?
[btw im stuck in the mode]
piax said:
im having the same problem!!!
except im STUCK on the
home+volume up+power screen
i used the same sbf i did the first time from the leaked gb and it worked fine
and well i downloaded nightlies to get liberty on my phone, and i wasnt a big fan of the text msg layout so i tried to clockwork mod (flash) into the deoxed gb but i still had a liberty boot and i thought nothing of it so i continued on and the phone worked fine itll it said gbkeyboard failed and i couldnt do anything!
so i turned it off and when i turned it back on flashwork was on!!! so i flashed the gb leak without root (the first one) and then i wanted root so i did the sbf but this time it said fail and my screen said it was still installing so i pulled the usb and the phone still said installing
so i battery pulled and my phone said code corrupted
so i tried the sbf back x3 still getting the same fail then i got to the part im at now,
code corrupted
battery low
cannot program
i left it on the charger for like an hour and its still "low"
am i soft bricked or hard?
[btw im stuck in the mode]
Click to expand...
Click to collapse
After the FULL sbf fails do the SYSTEM only and you should be good.
piax said:
im having the same problem!!!
except im STUCK on the
home+volume up+power screen
i used the same sbf i did the first time from the leaked gb and it worked fine
and well i downloaded nightlies to get liberty on my phone, and i wasnt a big fan of the text msg layout so i tried to clockwork mod (flash) into the deoxed gb but i still had a liberty boot and i thought nothing of it so i continued on and the phone worked fine itll it said gbkeyboard failed and i couldnt do anything!
so i turned it off and when i turned it back on flashwork was on!!! so i flashed the gb leak without root (the first one) and then i wanted root so i did the sbf but this time it said fail and my screen said it was still installing so i pulled the usb and the phone still said installing
so i battery pulled and my phone said code corrupted
so i tried the sbf back x3 still getting the same fail then i got to the part im at now,
code corrupted
battery low
cannot program
i left it on the charger for like an hour and its still "low"
am i soft bricked or hard?
[btw im stuck in the mode]
Click to expand...
Click to collapse
the low battery keeps it from being able to sbf (which is good because if it dies during an sbf, you are hard bricked. Since i am too lazy to type out full instructions, here is a quote from sysadmin x's guide
IF YOUR PHONE DIES DURING SBF
How to Fix
One thing that you may notice is that when you have this error, your phone will not charge the battery and you'll only be able to see the screen turn on if its plugged into the wall. Somewhere on the screen it will say "Your Battery is Low" and "Cannot Reprogram" or something like that. The easiest way to get through this is to find a friend with a charged battery or go to your local Verizon store and see if they have a demo phone they can use to charge your battery. If you're like me though you will not be lucky in any sense like this so you will have to find the MacGyver inside of you and get a little creative. What you need for this is an old USB cord. One end must be a standard USB cable head and the other can pretty much be anything. Once you have that, follow these steps:
NOTE: I TAKE NO RESPONSIBILITY FOR DAMAGE DONE TO ANY PHONE, BATTERY, ETC. FOLLOW THESE STEPS WITH CAUTION TO AVOID RISK OF DAMAGE.
1. Take your cable and cut off one of the ends, leaving a standard USB plug at the opposite end to plug into your computer.
2. Now you need to strip about and inch of the wire off until you get to the core where you should see 4 colored wires (red, black, white, and green). The colors don't really matter and they may vary, just as long as you can see a red wire and a black wire.
3. Strip off about a quarter inch of the rubber sleeving on the red and black cables, exposing the actual metal wire.
4. Twist the metal strands of each of the wires a couple of times so that all of the wires from the black cable are together and all of the wires from the red cable are together. This is just to make sure that you don't create a short circuit.
5. Here's where it gets a little tricky. You are going to use this cable to make the phone think the battery is fully charged, when in fact you will just be powering the phone using the power from the USB port. Pull out the battery on your phone and find the 4 exposed metal slots (the battery terminals).
6. Each of the far terminals should be labeled with a plus (+) or a minus (-). What you need to do is put exposed leads on the red wire up to the positive terminal and the leads of the black wire up to the negative terminal.
7. While still holding the leads on their respective terminals, slide the battery back into place in the phone. MAKE SURE THE WIRES ARE NOT TOUCHING WHEN YOU PUT THE BATTERY INTO THE PHONE! BAD THINGS COULD HAPPEN ONCE YOU PLUG THE CORD INTO THE COMPUTER!
Note: As tested by parm289, you can skip step 7 and just use the cable to charge the battery if you'd like. He recommends allowing it to charge for 6-7 minutes before placing it back into the phone. Thanks parm!
8. Once the battery is in place and the wires are on the correct terminals but not touching each other, plug the USB cord into the computer. If all has gone as it should, the screen on your phone should come on (may have to press the power button) and the phone should be telling you that the battery charge is okay and that it is okay to program. YAY! Your phone is almost back to normal!
9. Go back up to the previous section in this post that tells you how to reflash the .sbf and follow all of the instructions there. Once that has finished flashing the .sbf to your phone, your phone should be back to working order! You will most likely have to redo the entire setup on your phone but at least your phone is no longer a fancy paperweight
Click to expand...
Click to collapse
Borrow someone's droid x battery, or their phone to charge yours. that's gonna be alot easier than trying to strip the wires down. Also, check with p3droid (team black hat) they've been working on some fancy usb cables that will charge and flash.
thats exactly what the quote said, the numbers were there in case you cant get a charged battery. a last resort besides cutting the cable, you can go to verizon and ask to borrow a show floor battery, and give em yours so you can sbf. verizon is usually pretty nice
wow!!! thanks!
...but
now rsd says flashing failed
and the phone says its still installing
=/
I know the feeling! I have tried getiing into recovery from rooted GB usually just have to battery pull but have had to SBF for the 6th time. GB is great I benchmarked 2144 with Quadrant. Glad you fixed your phone.
And to think I went to Verizon and they wanted to send it to Motorola which they warned might charge me $300...
They also look at the battery to see if there's water damage... so this means you can just get a different battery and voila no water damage...
maybe if i use a different computer???
best part in all this i lost internet connection at home for a week
-.-
FFFMMMLLL
temp on blackberry storm ='[
i DOWNGRADED!!!!|
...ideas?
This is wife's phone. I was doing regular App Market updates for her installed apps. After they were complete got an error message, don't remember exactly what, but rebooted... Phone then went into a boot loop... It would boot all the way up to the lock screen then reboot again. I went in and wiped both cache's with no success. Went back into recovery and did a set factory defaults and now I am dead in the water...
I get to the Bootloader screen and it tells me Err:A5,69,35,00,27 and I have done everything but stand on my head to fix. I have re-SBF'd from multiple computers, using different SBF versions, driver versions, and RSD Lite versions including multiple bootable Linux CD's with embedded SBF. All resulted in getting the darn ERR:A5,69,35,00,27.
The only way I ever got anything different was to flash 1.13.604 and then I got an error message Err:A5,70,70,00,1F.
After that, if I SBF the newer version, I go right back to original error.
I tried a suggestion from another thread to download the system and full sbf files for 340. I flashed the full, got error... Then flashed system, still get error.
I am using RSD Lite 5.4 on Vista 32 with UAC disabled (full admin mode), latest Moto drivers as of this post. Again, I have tried all of the versions of bootable linux SBF's as well. All yield the same result.
Wife's phone, she is very unhappy with me, and if I don't get her back up and running, I guess I will be dropping $500 on a new phone, as she is still under contract. If Mama ain't happy, I sure ain't getting any! LOL!
It seems to me that you've tried everything possible.
Your best bet now would be to take it to Verizon, if it's still under warranty.
Sent from my DROIDX using XDA App
Out of warranty by 2 months.
I actually have two of these phones, and I was able to figure some information out here. I wanted to see if I could get my working Droid X into Stock Recovery, and low and behold it wouldn't go in either. I did some searching around and found that some ROM's were wiping out the stock recovery. I found this file dxgb_recovery_patch.zip and downloaded it and flashed it in Clockwork Recovery and that fixed the Stock Recovery on my working phone.
However, since my wife's Droid X is bootlooping, I can't access Stock Recovery or Clockwork Recovery. I feel like I am chasing my tail here. I need to wipe the data/factory reset, but I can't get there because I don't have Stock Recovery. I can reinstall Stock Recovery if I have Clockwork Recovery, but I don't have Stock Recovery to install Clockwork Recovery... Round and round I go...
There absolutely must be a way to get the Stock Recovery reinstalled from the state I am in.
what rom was the phone running when you had the original issue?
Apex 2.0 RC4
Good ROM, but it appears to torch stock recovery. I ended up having wife call and plead stupidity with Motorola. They are exchanging phone.
Still don't feel bad. Would have been able to fixed If they would unlock the damn billiard.
I have the same Problem with my Defy+ what can i do?
I have the exact same issue. Have tried all the sbf methods, still getting the error :A5,69,---, I was on MIUI prior to this. When I boot the phone back up I get the motorola M but then it brings me right back to bootloader and the error. I'm guessing stock recovery is gone.
Anybody find a fix to this yet. I am about to go back to Verizon, but wanted to fix it myself if at all possible, cause I have had my phone for a year and a half so I doubt they will help me out and don't have the money for a new phone right now.
Are you holding down Home and both volume buttons with power at boot to get to stock recovery?
*I have had several phones and don't remember exactly so you may have to hold Home and vol- only.
Jiggity Janx said:
Are you holding down Home and both volume buttons with power at boot to get to stock recovery?
*I have had several phones and don't remember exactly so you may have to hold Home and vol- only.
Click to expand...
Click to collapse
Yes, on the droid x its just home and the power button release the power button when you see the m and then you hit search once the droid pops up. Instead of seeing the droid it takes me to the bootloader screen with the above error message. The way to bootloader is volume button camera button and power. Which that still works and I have tried several sbf methods with none working. I didn't know if it was an issue that may have been mentioned above about the stock recovery being missing now since I was on MIUI 2.1 wizards verison. I didn't know if there was a way to get stock recovery back on the phone cause sbf doesn't seem to work. I really have no clue at this point. But full disclosure I have done quite a few sbf's and this is the first time I've ran into such an issue. Thanks again for any help.
Apologize ahead this is so long. I just wanted to update anyone just in case they ran into the same error that I did earlier. The Err:A5,69,35,00,27 on the bootloader 30.04 screen. I finally got an sbf to stick. About 30 sbf's later (no exaggeration) and 3 different nights of working on it. Honestly persistence just ended up paying off. Anyone else can chime in here if they know why it worked so its not so grueling for the next guy/gal and major props to 1kds who gave me a couple different suggestions and for making this awesome way to sbf. The linux disc didn't end up working for me in the end but it may have if I kept at it, because that is the way to go if you can (way easy to run), Also may have worked if I did the linux disc on a different computer. I started on MIUI 2.1 (Wizards vers) but previous to that the latest android vers I was on was 602, friday night my phone died and for some reason wouldn't charge in the morning or boot up. I had a spare battery with about 50% charge on it, so I used that to try and turn on the phone and I got the red M then the error message on the bootloader screen mentioned above. I ran the linux disc on my windows 7 (64bit) machine for all the currently downloadable files (froyo, 596, 602, 602root). Kept getting the err:a5,69...
Ran RSDLite on the Windows 7 machine (my current vers was 4.8, but then upgraded to 4.9) then 5.4.4 and also 5.6.4 (latest on the rsdlite motosbf site). I tried both froyo .340 and gingerbread 602 files on all these versions and even the .596 gingerbread which I had never been on. Nothing worked and I had gone through my second battery at this point. Then I figured I would try my Windows Vista 32 bit Laptop that never had rsd lite on it or the drivers. So Downloaded 5.4.4 (found this to be the one favorable for the 602 flash per the forums) and the motorola driver and sbf'd again both the froyo .340 and the gingerbread 602 file. Still getting the same error. Every third sbf or so I would even start getting a code corrupt error. The flashes actually failed every now and then and then sometimes they would show finished and the phone would still show the s/w update screen (I just did a battery pull and would sbf again at this point). After each sbf tried getting into stock recovery Volume down, home, and power button and each time I would get an error and/or go back to the bootloader screen. I also tried just home and the power button.
What worked!!! - Not sure why but my last sbf I did was the 602 still on the laptop running Windows Vista 32 bit since I thought that would work on the rsd lite 5.4.4 (credit here to droidmodderx and 1kds). It still showed the Err:A5,69,35,00,27 after the sbf finished and it tried to boot (i did get the red m, but then went to that error page again). Battery pull, turned back on and then error page on bootloader 30.04 again. I held the home, volume down, and power button for about 1-2 minutes = same result. Held Home and Power button = same result with error. Tried the home, volume down, and power one more time (still same result). Battery pull again, waited a few minutes and just tried to turn on and it got past the red m to the droid eye!!!! It did bootloop, but I battery pulled and tried to reboot since stock recovery hadn't been working. Same thing, bootloop, so I tried the stock recovery again (home, volume down, and the power button) and stock recovery came up. Hit the search button then did the factory reset. I couldn't believe it and like I said not sure why/how it worked (maybe the multiple attempts to get into stock recovery). All I know is 4 days later it works now and I thought all was lost!!! Of course again wouldn't have been able to do this without 1kds or these awesome forums! Thanks again and sorry so long, but hopefully this helps someone else!
Back on the X!
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!
I have a Defy Plus on GB T-mobile. Last wek, for some reason it suddenly showed the Android figure with a warning triangle behind it. I decided to do a restore but couldn't get the soft restore to work. I switched off and restarted, holding the power down button and entered the restore menue. I selected the wipe/factory restore. This is when my problems began.
My phone is stuck, it shows an android figure with a box behind it and an arrow coming out of the top, theres a hatcheted line below, which on occasion moves. This sits on screen for a while before going back to the motorola logo and then the android figure again. I've left the phone like this for over 12 hours, with the charger plugged in. No change.
I downloaded the Motorola software update and it tries to update the software but near the end, when it asks me to reboot. I end up back with the android and box figures.
I can't get back to the restore menue, to try wiping data or cache.
Any suggestions - motorola customer services just say send it to their repair centre.
Thanks
James Smalls said:
I have a Defy Plus on GB T-mobile. Last wek, for some reason it suddenly showed the Android figure with a warning triangle behind it. I decided to do a restore but couldn't get the soft restore to work. I switched off and restarted, holding the power down button and entered the restore menue. I selected the wipe/factory restore. This is when my problems began.
My phone is stuck, it shows an android figure with a box behind it and an arrow coming out of the top, theres a hatcheted line below, which on occasion moves. This sits on screen for a while before going back to the motorola logo and then the android figure again. I've left the phone like this for over 12 hours, with the charger plugged in. No change.
I downloaded the Motorola software update and it tries to update the software but near the end, when it asks me to reboot. I end up back with the android and box figures.
I can't get back to the restore menue, to try wiping data or cache.
Any suggestions - motorola customer services just say send it to their repair centre.
Thanks
Click to expand...
Click to collapse
Try to flash a stock ROM from the forum with RSDlite.
Thanks for the reply. I tried to flash the GB tmobile rom & a couple of others. It goes through setup, then asks me to manually resart. When I try, it goes back to the android figure with the box behind it.
The only way I can get rsd lite to reconnect and finish the setup is to re-enter bootloader.
Sent from my U8180 using xda app-developers app