Stuck in all ways I think - Droid X General

Okay I followed these instructions
http://www.talkandroid.com/55906-on...d-3-droid-x2-cliq-and-cliq-2-from-the-forums/
I had it rooted, I used the droid x bootstrap to install the recovery and then used it to go into recovery. I made a backup, but I forgot to wipe before I installed a new rom (newest MIUI). I tried using the bootstrap to install the recovery again and go into it, but when I try to go into the recovery it just reboots the phone basically. It stays on the Motorola logo for a long time but eventually boots. I tried the Droid 2 bootstrap now and still the same results. The wifi on it is broken and the data does not work. Every time the phone reboots, its completely starting from scratch. I have to resign in with gmail and everything, and the bootstrap is no longer installed.
I tried using the recovery by holding the home button while powering it on, but wiping data and cache does nothing, and it errors out when I try to install the rom from the install from update option.
I'm stumped. How can I get back into the recovery so I can wipe+install the rom again?

I fixed it. Please delete the thread. Not sure why we don't have the ability to do so if it's our own thread.

Only because I'm curious, related to my DX presenting similar symptoms: If you have a few minutes, would you be willing to post up your solution/fix? I might find your insight and information useful in my present situation. Thanks in advance,
~:sDs:~

Related

Boot Into Recovery From power off

Am stuck on The Rubix Logo. I was on Rubix 1.89 then I was messing around w/phone a lil bit so I decided to load the stock rom back. It loaded up fine. I attempted to load Rubix 1.93 and decided not to wipe (Stupid mistake) and now am stuck on Rubix boot loop. Can someone assist me in loading into Recovery when DX is powered off please. I hope no one mentions SBF. I have no clue how to even begin that process
Been in a similar situation. I assume we're talking about getting into clockwork recovery?
If that's the case, your only solution is an sbf if it isn't kicking you into clockwork already.
Getting into stock recovery is achieved by holding down the home and power buttons from power off.
SBFing is done from the bootloader. that is entered from power off by holding down power, volume down, and the camera button.
You will need the 2.2 sbf file and RSD lite 4.8 on your windows machine in order to perform sbf.
Yes You assumed right about CW, I knew it wouldn't be long before I Fd this up. I already have RSd lite 4.8(I think...have to double check). Where can I get this SBF 2.2 file from? I've looked all over but most links are dead This really Sucks..
Couldn't I just load the Leaked 2.3.320 file instead of the 2.3.15, since I wanted to do the upgrade anyway? or is it just not that Easy?
The 2.3.320 is just a system sbf. I think there were kernel changes that went with that you'll have to have. Standby for PM.
im in need of that 2.3.320 too i have a sitting brick that will not do recovery but can flash with a sbf
Not sure what your situation is but I posted some help over at DF as well and my issue has been resolved by Seph and these instructions I followed. Hope it works for you as well and fyi here's link(http://www.droidforums.net/forum/drod2169-x/99143-rubix-focused-1-8-9-1-9-3-a-34.html#post1021218)
First thing to try, is to wipe data and cache from the android recovery (NOT clockwork recovery.. as.. most liklely you can't get to clockwork recovery.
Easiest way:
--Battery Pull
--When you put the battery back in, hold down the home button the phone.
--As it powers up, let go of the home button when you see the M logo.
--It should go into android recovery. When you see the little droid with the ! in a triangle, hit the search button.
--From the menu, wipe data and cache, then reboot.. it should take you into Focused...
When you get back in.. the FIRST thing I suggest, is to reload 1.8.9.. as it sounds like you do not have the TBH leak (If you don't have it, you probably don't want it)...
PLEASE read the first post, that talks about the differences between 1.8.9, and 1.9.3...
Since you will have already wiped data and cache, you shouldn't need to when loading 1.8.9.. if you have troubles with loading it, just wipe data/cache again...
I wish I had come here first!!!! Been trying to get ROM Manager to work and finally got all excited because it seemed as though it had finally taken, well, now I am stuck in a the Rubix boot loop as well. I've wiped my cache as mentioned about but not data yet. My only option for that is to wipe data is to wipe data/ factory reset. Is it safe to do that since I am rooted? I was running OTA 2.2 rooted.
I am in sbf with rsd lite and can not get it to do anything after loading the file for sbf on my X. It recognizes it but the radio button for the start will not do anything.
rcnaimee826 said:
I wish I had come here first!!!! Been trying to get ROM Manager to work and finally got all excited because it seemed as though it had finally taken, well, now I am stuck in a the Rubix boot loop as well. I've wiped my cache as mentioned about but not data yet. My only option for that is to wipe data is to wipe data/ factory reset. Is it safe to do that since I am rooted? I was running OTA 2.2 rooted.
Click to expand...
Click to collapse
Someone please PM me and tell me what I am doing wrong!!!!

[Q] Need Help With Recovery

So this is what happened...
I was helping my buddy install a Rom on his Droid X, and after wiping everything and installing the rom, i rebooted the phone and it got stuck on the "M" screen.
So i figured i would go into recovery and either restore a back-uped session or just wipe everything and reboot again.
But in recovery, he doesnt have an option to restore sessions or anything. and when i try to wipe data and clear cache partitions, he still gets stuck at the "M" screen when i reboot.
Also, in recovery, it gives me a message that says,
"E:cant open /cache/recovery/command"
and after googling this and looking for solutions, none have helped. It says try pulling battery for 5 minutes, or deleting the "update.zip" file (which i cant because i cant boot the phone up), and even pulling the SD card (which doesnt make sense, but nonetheless didnt work anyway).
Any help would be appreciated. I feel real bad for putting his phone on a soft brick haha so please help a brotha out.
Thanks in advance
ejeetguy said:
So this is what happened...
I was helping my buddy install a Rom on his Droid X, and after wiping everything and installing the rom, i rebooted the phone and it got stuck on the "M" screen.
So i figured i would go into recovery and either restore a back-uped session or just wipe everything and reboot again.
But in recovery, he doesnt have an option to restore sessions or anything. and when i try to wipe data and clear cache partitions, he still gets stuck at the "M" screen when i reboot.
Also, in recovery, it gives me a message that says,
"E:cant open /cache/recovery/command"
and after googling this and looking for solutions, none have helped. It says try pulling battery for 5 minutes, or deleting the "update.zip" file (which i cant because i cant boot the phone up), and even pulling the SD card (which doesnt make sense, but nonetheless didnt work anyway).
Any help would be appreciated. I feel real bad for putting his phone on a soft brick haha so please help a brotha out.
Thanks in advance
Click to expand...
Click to collapse
What ROM? What was the Android version before hand? At this point it's not going to matter, you're going to need to SBF (factory restore). Check google for guides, or look @ the site in my signature.
Yeah, seems from you described you got your hands on a bad file; maybe the file didn't get downloaded completely. In any case, your best bet is to sbf your phone (restoring to stock using software). There is a ton of info on that, do you shouldn't have a problem on how to do that. If you need help or direction, please let us know.
Sent from my DROIDX using XDA Premium App
you have encountered my one gripe about my X. You can't get to recovery if you get stuck in a boot loop.
Your only option is to sbf back to stock and go again. I just had this happen today while I was at work. I decided I want to run Apex 2.0 alpha 3 and messed up. I was stuck at work all day without my toy.
im having the exact same problem and i tried to sdf back to stock using rsd lite as explained in another section and it goes thru the whole process reboots itself, says 100% done and tells me to "power up this phone" only i cant because when it rebooted it got stuck on the M screen ands stays there and i cant power it up.....Any suggestions appreciated THANX
Get into stock recovery and wipe
Sent from my DROIDX using Tapatalk

Update gone wrong! NEED HELP!!!

So I've been running MIUI 1.8.whatever for a few weeks and finally realized there hadn't been an update in a while. After discovering MIUI move into the 1.9.Xs I downloaded 1.9.16 and proceeded to update via CWM. While updating it told me 1.9.16 runs off the Gingerbread kernel. At that point I got worried since I had been running the Froyo kernel since I rooted my DX.
After the update I told it to reboot and now it gets stuck at the white M logo. I can boot into regular recovery but I CANNOT get my phone to boot into CWM recovery so I can run the backup!
I've tried every button combination with no luck. i've booted into regular recovery and selected reboot having read that it will boot back into CWM recovery. Needless to say that didn't work either. And lastly I tried running RSDLite to SBF the phone to .602 but since the phone can't fully boot up RSDLite doesn't see the phone.
That is where I am at and I seek the help and guidance of you much smarter folks to help me get my phone at minimum to CWM recovery.
PLEASE HELP!!!
Boot the phone into bootloader mode, then SBF.
Sent from my DROIDX using XDA App
I got it into bootloader mode now, but my computer isn't finding the OMAP drivers and the installation keeps failing. How can I get these drivers onto my computer? RSD isn't seeing the phone even in bootloader so these drivers seem to be the key.
You can find the drivers in this thread:
http://forum.xda-developers.com/showthread.php?t=1258599
Sent from my DROIDX using XDA App
I got RSDLite to see the phone. Now when I try to flash it, it makes it all the way to checking the checksums (which all pass) then tries to switch the phone to BP passthrough. It keeps failing to switch the phone to BP passthrough and now my phone will only boot to the Bootloader screen and says Code Corrupt. It'll let me run the flash again but RSDLite keeps failing at that BP passthrough switch.
Thats where i'm at now.
Try a different SBF file. I had problems like this when i tried to SBF once, but once I found the SBF file that works for me, its always worked since. (I've had to SBF like 6 times now haha)
will find an older sbf file and try that. Wil let you know.
Alright we've made progress! I was able to finally get the phone SBF'd to .602. Then I rocked the Pete's Droid Rooting program and all seemed to have gone smoothly... Except I cannot boot into CWM recovery at all! I've ensured ROM Manager has the correct flash for CWM installed, but when I click Reboot into CWM Recovery, it'll reboot normally. So I turned the phone off and held the Home + Power button to boot into regular recovery. I get the ! logo with the green android, but when I hit hte Search button nothing happens.
So now I'm rooted, but can't get to CWM Recovery to install ROMS.
What do you guys think?
Yeah, Reboot into Recovery from ROM Manager doesn't work for me usually either...in fact, I had to go into the Bootstrapper app, install the recovery again, and then hit Reboot Recovery. This is on Apex though, but can't hurt to try it.
Yea I finally got it figured out. Its been so long since I originally rooted my phone I forgot all about D2Bootstrapper. And I didn't read the how-to guide for updating to MIUI 1.9.16 so that was all on me.

In a mess of trouble. Help please I'v searched with no luck.

So I think I've royally F'd my DX. I was going to try rooting and flashing a new rom. I'm not a total noob (rooted gtab, nook color, Le Pan) but this is ****ing me up.
It was running 2.3.3 605 originally. I started out with just root, that seemed fine. I got superuser and busybox installed without a problem. I install clockwockmod and dx bootstrap. I was even able to get CWM 5.0.2 or whatever installed without any trouble like I had read.
I tried reading and following threads but I couldn't fallow on if I was missing steps. I have zero experience with rooting via scripts and I have no intention to learn and would rather go back to stock.
I immediately got problems with rebooting. It would not reboot via the power button. It would go to the Red M then just black screen. But it would boot just fine if I pulled out the battery and tried that way.
I did a factory reset thinking that would help, it didn't. I was still rooted but the problems got worse. Now I boot directly into CWM recovery and have to reboot from in there to get to the OS.
I read some more, thought I had figured more out. Installed Rom manger, installed Liberty3. I'm still booting straight into recovery but when I reboot from there I'm stuck at the spinning Liberty logo.
I need help, I've read and searched, if you want to be a **** have run. But I need my phone fixed. Hold my hand like I'm Hellen Keller and help please.
I would recommend reading the Droid X wiki at the Cyanogenmod website. I had some of the same issues until I followed the downgrade + root method and then installed ROM Manager and CM7 manually through recovery. Good luck!
Sent from my DROIDX using XDA App
Schwazilla said:
So I think I've royally F'd my DX. I was going to try rooting and flashing a new rom. I'm not a total noob (rooted gtab, nook color, Le Pan) but this is ****ing me up.
It was running 2.3.3 605 originally. I started out with just root, that seemed fine. I got superuser and busybox installed without a problem. I install clockwockmod and dx bootstrap. I was even able to get CWM 5.0.2 or whatever installed without any trouble like I had read.
I tried reading and following threads but I couldn't fallow on if I was missing steps. I have zero experience with rooting via scripts and I have no intention to learn and would rather go back to stock.
I immediately got problems with rebooting. It would not reboot via the power button. It would go to the Red M then just black screen. But it would boot just fine if I pulled out the battery and tried that way.
I did a factory reset thinking that would help, it didn't. I was still rooted but the problems got worse. Now I boot directly into CWM recovery and have to reboot from in there to get to the OS.
I read some more, thought I had figured more out. Installed Rom manger, installed Liberty3. I'm still booting straight into recovery but when I reboot from there I'm stuck at the spinning Liberty logo.
I need help, I've read and searched, if you want to be a **** have run. But I need my phone fixed. Hold my hand like I'm Hellen Keller and help please.
Click to expand...
Click to collapse
Don't use ROM manager and don't use dxbootstrap (unless you have usb debugging unchecked). I use d2 bootstrap always. And you will have the occasion of it going in to cwm when you boot phone back up. I dealt with it for while. And cwm should be 2502 or something like that when you're just rooted 605. Did you make a nandroid of your rooted 605 before you tried to flash liberty
? Hopefully you did. Go back to that. Then use d2 bootstrap to get in to recovery, wipe data, cache and dalvik, then select install ip from sd card, then choose zip, then scroll via volume down to the liberty file, select that and flash.
I used directions posted over at Androidforums.com under the All Things Root forum for the Dx. I had a couple of hiccups, but it was user error. I now have Liberty 3 running smoothly on my Dx. Check it out, including the guide and ROM lists.
HTH
chaz_
Schwazilla said:
So I think I've royally F'd my DX. I was going to try rooting and flashing a new rom. I'm not a total noob (rooted gtab, nook color, Le Pan) but this is ****ing me up.
It was running 2.3.3 605 originally. I started out with just root, that seemed fine. I got superuser and busybox installed without a problem. I install clockwockmod and dx bootstrap. I was even able to get CWM 5.0.2 or whatever installed without any trouble like I had read.
I tried reading and following threads but I couldn't fallow on if I was missing steps. I have zero experience with rooting via scripts and I have no intention to learn and would rather go back to stock.
I immediately got problems with rebooting. It would not reboot via the power button. It would go to the Red M then just black screen. But it would boot just fine if I pulled out the battery and tried that way.
I did a factory reset thinking that would help, it didn't. I was still rooted but the problems got worse. Now I boot directly into CWM recovery and have to reboot from in there to get to the OS.
I read some more, thought I had figured more out. Installed Rom manger, installed Liberty3. I'm still booting straight into recovery but when I reboot from there I'm stuck at the spinning Liberty logo.
I need help, I've read and searched, if you want to be a **** have run. But I need my phone fixed. Hold my hand like I'm Hellen Keller and help please.
Click to expand...
Click to collapse
Just re-flash ur phone dude. do you know how to do that? It's a pain in the butt. but it is always failsafe.

[Q] My Motorola Bravo doesn't power on after rom update

Let me see if somebody else have had this issue.
I flashed my Motorola Bravo, configured Motoblur and everything, then I rooted it, after that I installed Bravo Recovery and rebooted in recovery mode.
wipe data and cache.
Installed the CM9 and the gapps (correctly)
Ok, here comes the problem, I rebooted but I still was seeing the AT&T logo, it wasn't supposed to, but it's ok. After a while the phone was stock there so I take the battery off to restart in recovery mode again (volume up+power) and install the old rom that I had working on my phome (CM7). But after that the phone is dead, not power, so I'm not able to flash again or do anything else.
Any ideas?
Thanks in advance.
joserado said:
Let me see if somebody else have had this issue.
I flashed my Motorola Bravo, configured Motoblur and everything, then I rooted it, after that I installed Bravo Recovery and rebooted in recovery mode.
wipe data and cache.
Installed the CM9 and the gapps (correctly)
Ok, here comes the problem, I rebooted but I still was seeing the AT&T logo, it wasn't supposed to, but it's ok. After a while the phone was stock there so I take the battery off to restart in recovery mode again (volume up+power) and install the old rom that I had working on my phome (CM7). But after that the phone is dead, not power, so I'm not able to flash again or do anything else.
Any ideas?
Thanks in advance.
Click to expand...
Click to collapse
First of all, if you do get this to work, I would recommend NOT using the BandroidX Bravo Recovery app from the Android Market. It is very outdated. josuearisty came up with a one-click root and recovery (root doesn't work on it, root the Bravo then just use for recovery) which has a much newer version of CWM.
As for your no-power issue, sounds to me like your phone is hard bricked. Check out this thread to see if it answers your question:
http://forum.xda-developers.com/showthread.php?t=1702600

Categories

Resources