So here's the story. Bought a used Droid X from a guy at work. Phone was fine. Never rooted or anything related to root. So I decided to root it. Used ZergRush method I believe. Installed Bootstrap Recovery. Wife used Rom Toolbox to change several notification icons, boot animation and boot logo. Everything was great for awhile, but she got tired of it always booting into recovery. So I was going to un-root and return to stock. Ran the same ZergRush Un-root app. Then removed Bootstrap and all other root apps. Then found out wife accepted an OTA before I un-rooted. Well, at this point the phone still worked, and was un-rooted, but still rebooted into recovery, still had custom boot animation and logo as well. So she then reset phone to factory defaults. After that is when we had problems. Basically it wouldn't load past the boot logo. I just pulled the phone out from its hiding spot after a month or so to try and tackle it again. But now I think the battery is shot because it won't turn on period, whether plugged in or not, and the battery looks like its swollen. Has a huge bulge in the middle.
My question is, do you think the phone is able to work again? Cuz if not, I'm not buying a new battery.
Yeah it sounds like a bad battery now but before would it would just boot to the red m? If so an sbf would probably do the trick
Sent from my ADR6425LVW using Tapatalk 2
Ya before it would boot to the M and stay there, until I pulled the battery. So hopefully new battery and sbf and it will work?
Well yeah an sbf should do you just fine
Just be sure once you do the sbf you boot into stock recovery (vol down+home+power then vol up+down together when you see the !) And do a factory reset or you'll just have another headache
Sent from my ADR6425LVW using Tapatalk 2
Alright cool. Looks like I'll be finding a battery and having a whirl at this. Thanks for the replies
So i sbf'd the shadow 2.3.4 using rsd and it said it was completed and to manually boot the phone. So i did and it still stays at red m logo. Only difference is its now the red m where as before the sbf it was the pink Android my wife installed. So some progress I guess.
Any ideas? Try a different sbf file maybe?
Sent from my R800x using XDA
EDIT: Nvm, tried a different sbf and it works fine now.
I know you say it would boot into the M but could you get it to boot into recovery?
Don't remember if i tried actually lol. Its plain now, no root or bootstrap, but it works
Sent from my R800x using XDA
Kasper DG said:
Its plain now, no root or bootstrap, but it works
Click to expand...
Click to collapse
Strange how DroidX phones eventually become stock and unrooted :^)
Sent from my unrooted DroidX using Tapatalk
Nate2 said:
Strange how DroidX phones eventually become stock and unrooted :^)
Sent from my unrooted DroidX using Tapatalk
Click to expand...
Click to collapse
Very strange indeed. Almost like I got the sbf to work or something
Sent from my R800x using XDA
Related
I think i bricked my Droid X. i was running Rubix Focused and tryed to flash GingerAle 3.0 and now it just sits at the moto "M" logo. i can get into the recovery by pulling the battery but even after a wipe and a recovery it still just sits. did i brick it, and if so how can i fix it? please help, reletivly new to flashing roms.
P.S. I'll love you forever if i can fix it =)
now i think i really did it. I tried running a recovery image from a few days ago and now i cant get back into the recovery menu...
Sounds Like SBF Time
Sounds like SBF is going to be your friend here, if you don't know how, head to
http://forum.xda-developers.com/showpost.php?p=11118819&postcount=2
and look for "SBF: What is it, and what does it do?!?"
OK, so i SBFed the phone, got all the way through it, got to the phone is rebooting and it just sits at the Moto "M" again. did i SBF wrong or what?
EDIT: I can get into the stock recovery... sort of. i can get to the ! with the droid next to it but nothing happens when i push the search button.
hmm, I know GB doesnt use the search button to pass that, try using vol UP+DOWN at the same time. perhaps the stock recovery isn't modified from SBF?
Woot that worked. got into recovery. wiped data and tryed a reboot, got stuck at logo again. should i try flashing back to the Rubix focused i had before?
Edit: it now boots into <3e> recovery and i get the e: signature verification failed instillation aborted when i try to install Rubix or Gingerale.
You can't install a custom roms from stock recovery
Sent from my DROIDX using XDA Premium App
try doing a full wipe data/cache a couple of times. that usually works for me
Sent from my DROIDX using the XDA mobile application powered by Tapatalk
YAY
Fixed it!!! yay!! I had to flash the full SBF file, not just the system one. thanks for the help guys
thats ur best bet. full sbf
Sent from my DROIDX using the XDA mobile application powered by Tapatalk
Hey guys I need some help here. I just rooted my droid x and installed the koush recovery as stated in the noobs guide to the droid x. i was able to boot into recovery and clear my data and cache and I installed Gingerale 3.0.
Well I cant get wifi tethering to work so I need to install a WUG's patch. Problem is, I cant seem to boot into koush's recovery anymore. I installed it again on the new rom and tapped bootstrap recovery and it said success. Then I tapped reboot recovery and my phone rebooted. The M came up then all I get is black screen with the backlight on. I have waited 15 minutes and same thing. I have to pull the battery and reboot. I can not for the life of me figure out why I cannot boot into clockwork.
I could use some help. Thanks.
Franteeko said:
Hey guys I need some help here. I just rooted my droid x and installed the koush recovery as stated in the noobs guide to the droid x. i was able to boot into recovery and clear my data and cache and I installed Gingerale 3.0.
Well I cant get wifi tethering to work so I need to install a WUG's patch. Problem is, I cant seem to boot into koush's recovery anymore. I installed it again on the new rom and tapped bootstrap recovery and it said success. Then I tapped reboot recovery and my phone rebooted. The M came up then all I get is black screen with the backlight on. I have waited 15 minutes and same thing. I have to pull the battery and reboot. I can not for the life of me figure out why I cannot boot into clockwork.
I could use some help. Thanks.
Click to expand...
Click to collapse
Try downloading ROM Manager from the Market. Once you open it up click Flash Recovery and select Droid X. Now try to boot into recovery from ROM Manager.
Thanks for the reply. I have done as you said and still no dice. The phone reboots, the M comes up then screen goes black with the backlight on and thats it. Any other ideas?
Franteeko said:
Thanks for the reply. I have done as you said and still no dice. The phone reboots, the M comes up then screen goes black with the backlight on and thats it. Any other ideas?
Click to expand...
Click to collapse
You might have to sbf.
I had the same problem. I installed the droid 2 recovery and got out back finally....
Sent from my DROIDX using XDA Premium App
I dont have a problem sbfing but I would hate to do that if its just going to happen again. A quick search on this forums brings up tons of results of people having the same issue and i have not been able to find a solution for it.
Any ideas?
Have you tried stock recovery? And you have d2 bootatrapper?
Sent from my DROIDX using XDA App
Now you need D2 bootstrap, DX doesn't work on GB
Sent from my DROIDX using XDA Premium App
Hey guys.
Sooooo sorry if i am missing something obvious.. Im trying to do a backup after a fresh rooted .605 from Tom Tools thread.
Rooted fine. (see superuser)
Downloaded Rom Manager
Clicked Flash Clockworkmod Recovery
Chose Droid X
Said it did
Reboot into recovery just boots back to the OS.
Is there something between here and there I need to do?
just downloaded bootstrapper for droidx....now it boots to a black screen.
mrhunters said:
just downloaded bootstrapper for droidx....now it boots to a black screen.
Click to expand...
Click to collapse
You must use Droid 2 Bootatrapper instead of the Droid X version.
Sent from my DROIDX using XDA App
ok thanks. got that , got into recovery... now the camera button doesnt (or any other button) select an option. i can just toggle up and down using vol keys
looks like my camera button is broken and I just called to find out my warranty expires in 6 days! I'm not usually a lucky person so that is pretty lucky for me
Will revisit this with the new phone
ok so this might have to be a new thread but.
I unrooted since it will be going back on Monday.
I need to get rid of SU and from what i read i have to sbf or use maderstcok - OTA 2.3.340 update.zip
Both guides NEED the camera button......
Is there another way?
mrhunters said:
ok so this might have to be a new thread but.
I unrooted since it will be going back on Monday.
I need to get rid of SU and from what i read i have to sbf or use maderstcok - OTA 2.3.340 update.zip
Both guides NEED the camera button......
Is there another way?
Click to expand...
Click to collapse
You shouldn't need the camera button to SBF.
Sent from my DROIDX using XDA App
you need it to get to stock boot loader....
at least thats what the guide says.?
mrhunters said:
you need it to get to stock boot loader....
at least thats what the guide says.?
Click to expand...
Click to collapse
If on Gingerbread, holding both volume keys and pressing the power button gets you into bootloader mode. I believe it's different if you're on Froyo.
Sent from my DROIDX using XDA App
that worked... sbf'ing as i type this.
I had encounter ICS, which was great, but isn't ready to be a daily rom, so I use koush's app to reboot into recovery.
then I got stuck at the boot animation, so I decided to open up the stock recovery, and wiped data/factory reset like an idiot. So now all i have is stuck at the M logo, or stock recovery.
Am I going to have to use an official update.zip to flash, then root my phone again?
You are going to have to sbf.
Sent from my DROID2 using xda premium
okay, so I sbf'd back to stock froyo (only GB sbf I can find around the net is a megaupload link, which is obviously not very helpful nowadays) and let it do an OTA update to GB.
I then root, just like i have before, using the motorola one click root program on my computer.
I get root, install koush's bootstrap, and reboot into recovery. I then try to install libertyv3 2.0, which seems to go well...
until i reboot. once i reboot my phone, I'm stuck back at the bootloader, and can't do anything except SBF all over again.
seriously, what's going on? maybe this liberty .zip is broken or something? (i had to find a mirror, because A team gummy's site seems to be down, and B the only other official mirror is megaupload)
I'm going to try another rom, probably encounter ICS because i already have it on my SD card.
this time, I actually read the instructions and tried to install Liberty with clockwork recovery instead of koush.
still. effing. happening.
I reboot after flashing the zip and I can't get past the bootloader screen.
Code:
Bootloader
D2.37
Err:A5,69,35,00,23
Battery OK
OK to Program
Connect USB
Data Cable
I'm seriously at wit's end here. I just got this phone but a couple days ago after I lost my original. it's an insurance replacement. I rooted with the moto one click root, and used koush to install encounter ICS. after not knowing about encounter's wonky way of activation the custom bootloader, I mistakenly wiped the phone with the stock bootloader. I SBf'd back to stock froyo, then OTA updated to gingerbread.
That is my entire history with this phone. what the hell could possibly be wrong with it?
Do you wipe data/cache/dalvic once before you flash and twice after? Liberty is dead use ICS.
Sent from my DROID2 ICS using xda premium
Albinoman said:
Do you wipe data/cache/dalvic once before you flash and twice after? Liberty is dead use ICS.
Sent from my DROID2 ICS using xda premium
Click to expand...
Click to collapse
I did certainly wipe before flashing, but have never not once heard of wiping twice after flashing. wouldn't that undo the flash? what's the point of that? And like I said, I would use encounter ICS, but it's nowhere near stable enough for daily use.
When you wipe after its just to make sure everything is stock. As long as you don't wipe /system the rom will still be there. Actually if you can live without a camera EncounterICS is an amazing daily driver. Also never use bootstrap unless you're on stock gb.
Sent from my DROID2 ICS using xda premium
I can live without a camera, but google music barely works, which is something I can't live without. I'm thinking about going back to Apex until encounter gets really good (had apex for months up until i lost my original phone)
Google music is working fine for me. Good idea apex is great.
Sent from my DROID2 using xda premium
if I'm posted in the wrong spot please move me
wife's phone started acting weird. it's been on 4.1.2 for a long time. it was rooted but no BL unlocked.
so after trying numerous ways to fix it I decided to try and move to KK. so I defrosted all my bloat and the updater then accepted the first OTA. all worked great. then accepted the second OTA and it installed and was halfway through installing when it rebooted and then went to a more dim version of the same screen. open chested droid with spinning item inside. when it finally finished it rebooted to the Red M and will not go any further.
I can get into fastboot and I have pushed a few commands to see if it works but I cannot get it to allow me to do much else. I have RSD but it seems the device but doesn't show any information. tried to flash something via RSD and it says PHONE RETURNED FAIL
is there a way to get this phone back to some workable form? BL is locked.
===================================================
lots of reading.
it appears that with locked bootloader only signed official MOTO system and boot.img can be loaded thus the fails. downloaded official files
running RSD now and it's gone through 15/17 steps, now loading system for last few minutes.
fingers crossed....
Let us know what happens
Sent from my DROID RAZR M using XDA Premium 4 mobile app
Got it working. Then had to redo it because I flashed 182 not 183. Then that meant I had to delete getvar, got it working and it's perfect EXCEPT WiFi sucks. It doesn't see or stay connected to access points that are best in house. Makes me want to Revert just for that.
Sent from my SCH-I535 using Tapatalk
dyskinesia said:
Got it working. Then had to redo it because I flashed 182 not 183. Then that meant I had to delete getvar, got it working and it's perfect EXCEPT WiFi sucks. It doesn't see or stay connected to access points that are best in house. Makes me want to Revert just for that.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
It's pretty easy to downgrade back to jb
Sent from my DROID RAZR M using XDA Premium 4 mobile app
Ultimately phone had h/w issues. So swapped for another just like it still on jb. Rooted and unlocked so golden.
Sent from my SM-G900V using Tapatalk