I recently installed the Cyanogenmod 10 ROM to my Droid x2. It was done correctly, and was working fine for about a week. But, it is currently stuck on the boot screen whenever I try starting it up. This is what I think happened: After a while, I realized that I had never installed Bootstrap recovery, over CM10. I checked on the Official ROM page, and saw that the bootstrap recovery for CM7 worked on CM10. I had to leave, and didn't have time to install it.
Later that day though, While looking through my SD card contents, I realized I had a Bootstrap apk on it. Without thinking, I went ahead and installed it (I believe the problem is that it was Bootstrap for 2.3.4, the one I first used to install CM7, on the way to CM10) I brought up the app, and installed recovery. I did not automatically restart my phone after, and carried on. Later on, while texting, the phone crashed without warning, and tried to restart. It failed to start up, leaving me where I am currently.
I've tried rebooting with the phone unplugged, with the phone plugged into a wall charger, and with the phone connected to the computer.
Also, Standard Android recovery fails to start. It gets stuck on "Starting RSD protocol support".
My question is... Does anyone know how I could regain access to my phone? I did NANDroid backup, but, I have no way of accessing and installing the backups, while locked out of my phone.
If you can't access stock recovery then you'll need to SBF... once back on 2.3.4 you can root, isntall BSR and then restore the backup you created.
Yes, I agree. You can sbf, root, install normal bootstrap, and restore nandroid. Then you can install the cm7 bootstrap. I've used it with cm10 a2 and can confirm it does work with it. I didn't like cm10 so I went into the cm7 bootstrap and restored my cm7 nandroid backup. Shouldn't be too hard for you to restore your phone. Good luck.
Sent from my MB870 using xda app-developers app
Related
I have an odd problem. My Dell Streak will boot but once it gets into the OS none of the buttons are responsive. It is not frozen however. I've recalibrated the touchscreen but that does nothing.
However, the controls work when I am booted into recovery and the screen before fastboot.
The person I bought it from had tried to install StreakDroid but I'm not sure how he went about it. I followed the guides, flashing the correct amss and dsp. But I have the same issue.
I'm wondering what the problem could be. Should I try and flash the original Dell rom back on first and see if that works? It is just odd that everything works except when it has booted into Android.
I'm going to assume you have a custom recovery on there. If so, make a nandroid backup, flash a stock recovery, update via the matching pkg file, flash StreakMod recovery, then restore your nandroid backup. That will ensure all the firmwares "match", which could be causing your problem. It sounds like you aren't sure of the history of the roms and such on this phone. This will start you out at square one without losing your custom rom and settings. Certainly couldn't hurt.
I've tried to install the stock pkgs (I tried 360 and 319) but both stop working at the end of the install. How long is the install meant to take? Because I've left them for half an hour at the end but it hasn't completed
Hello. I am new to posting on XDA so I hope I am posting in the right place. I have a DX2, rooted, current runnning the MIUI ICS rom. I have used both the regular BSR and patched BSR on stock and various roms without any trouble, and the patched version worked fine with MIUI initally. Now however, when I attempt to enter recovery mode, it reboots as it should, then it shows a jumbled screen that resembles the colors of the custom recovery, but then goes black and will not do anything further without a battery pull. I have tried all the methods of entering that I have had success with in the past, like following the exact patched BSR directions, the regular BSR directions, installing the recovery then powering down manually and plugging up, etc., but it always does the same. I even tried the regular BSR, which did allow me to enter the recovery, but left me stuck on the "M" screen after leaving it, and I was forced to SBF to get going again. Does anyone have any ideas on how I can resolve this? Is there another recovery option for the DX2 running ICS roms that I am not aware of? I would greatly appreciate any and all advice and assistance. Thank you for reading, and a BIG thanks to all the devs here, the help you have provided me since I first got an android phone has been enormous. Keep up the great work!!
Maybe try downloading the CM7 patched recovery again and placing the new download on your external card... Uninstall the one on there currently and install the new one.. Press install recovery and then see what happens.
sounds like a v6 supercharger conflict
you have to uninstall v6 (if you installed it) before using bsr on ics roms
sbf should fix
sd_shadow said:
sounds like a v6 supercharger conflict
you have to uninstall v6 (if you installed it) before using bsr on ics roms
sbf should fix
Click to expand...
Click to collapse
I have tried removing and reinstalling the BSR several times, both from my backup copy of the APK and from a fresh download, but no luck.
I have not installed V6 supercharger on my phone since I was on CM9, and I have SBF'd twice since then.
Thanks anyway for replying guys. Keep 'em coming.
Removing or disabling patched BSR
I have CM10a3 running on my Dx2. I have made my back up so I don't need BSR running. When I connect to a charger from OFF, BSR hijacks the Battery screen and launches into recovery. This is exactly what it is suppose to do but I would like to disable this until I need another backup.
I uninstalled the CM7 Recovery app but this did not stop CWM from starting when connecting to the charger. Modifying Hijack-root.zip seems to drastic. Is there a way to suspend CWM?
CCC0180 said:
I have CM10a3 running on my Dx2. I have made my back up so I don't need BSR running. When I connect to a charger from OFF, BSR hijacks the Battery screen and launches into recovery. This is exactly what it is suppose to do but I would like to disable this until I need another backup.
I uninstalled the CM7 Recovery app but this did not stop CWM from starting when connecting to the charger. Modifying Hijack-root.zip seems to drastic. Is there a way to suspend CWM?
Click to expand...
Click to collapse
just select the 3 option in the bsr app, charge mode.
Sent from my XT894 using Tapatalk
Before doing my flash, I did my research, and it seemed that in order to update from CM7 to CM10, I had to flash a different version of CWM. So I booted into recovery, flashed the version 6.xxx CWM, and then rebooted (I assumed that in order to flash CM10, I had to be in a CM10-compliant recovery). After getting back to my regular desktop, I rebooted into recovery as normal... only it didn't go into recovery. Instead, it paused for a moment like it would go into recovery, then booted to my normal desktop.
I've tried about a billion ways to boot into recovery, to include SD based recoveries, but it either goes to a larger sized N screen, then hangs up on a black screen, or it boots me to my normal CM7. I "can" continue to operate on CM7, but until I can boot into recovery, I can neither update to CM10 nor address any problems I come across in my current build.
Suggestions?
nashdude said:
Before doing my flash, I did my research, and it seemed that in order to update from CM7 to CM10, I had to flash a different version of CWM. So I booted into recovery, flashed the version 6.xxx CWM, and then rebooted (I assumed that in order to flash CM10, I had to be in a CM10-compliant recovery). After getting back to my regular desktop, I rebooted into recovery as normal... only it didn't go into recovery. Instead, it paused for a moment like it would go into recovery, then booted to my normal desktop.
I've tried about a billion ways to boot into recovery, to include SD based recoveries, but it either goes to a larger sized N screen, then hangs up on a black screen, or it boots me to my normal CM7. I "can" continue to operate on CM7, but until I can boot into recovery, I can neither update to CM10 nor address any problems I come across in my current build.
Suggestions?
Click to expand...
Click to collapse
Have you tried holding on the power button and the "n" button as you boot? I recall running into a similar issue as yours and that was the only way I could get to recovery. If you're able to get into recovery that way I would consider maybe getting a different version fo CWM. I had trouble with the 6.0.1.5 version. You might try the 6.0.1.2 version here: http://forum.xda-developers.com/showthread.php?t=1640958&page=5
I ran into something similar when I tried installing CWM 6.x.x. I chickened out and decided to run CM10 from SD instead, and I'm so happy on the performance now that I do!
I did the "unbrick" thing with "repart.img" to get the Tablet back to "out of the box" state and sighed of relief when it worked!
Yeah, I was afraid of that. I really didn't wanna go through the process of unbricking, but I guess there's no help for it.
troy9829 said:
Have you tried holding on the power button and the "n" button as you boot? I recall running into a similar issue as yours and that was the only way I could get to recovery. If you're able to get into recovery that way I would consider maybe getting a different version fo CWM. I had trouble with the 6.0.1.5 version. You might try the 6.0.1.2 version here: http://forum.xda-developers.com/showthread.php?t=1640958&page=5
Click to expand...
Click to collapse
Power + 'n' doesn't work on my NT either, I have to turn the device off, insert the SD with CWM, then plug in the (still turned-off) NT to a wall charger and allow it to boot up that way - then (and only then) do I boot into recovery, and without touching any buttons. Hopefully that helps
Dang, whoever thought this would be such a booger of a deal?!?
Okay, first off, let me apologize for coming off like a noob, but it seems there's so much information out there that everything's kinda bleeding together, so let me tell you where I'm at.
I've unbricked and restored the NT to stock 1.4.2
I tried rooting, but the only root I can find that is flashable from SD is the 5.5 CWM which is older than the CWM 6.xxx that every CM10 version calls for. So I went ahead and did the root, so now I have a stock NT with root access. This is where I'm getting stuck...
I'm at this point...
http://forum.xda-developers.com/showthread.php?t=1640958&highlight=cwm+1+4+2
...and it apparently requires you to reboot into CWM in order to install CWM?!?
I've found the CWM 6+ files I think I need, but when I try to follow the instructions, my NT won't kick over into recovery---it keeps booting straight to the rooted 1.4.2 stock rom. I've found guides that take you from stock 1.4.3 to CM10, some that take you from 1.4.2 to root, and I even found Indirect's CM7 (without the instructions on how to get CWM on there in the first place!). I even downloaded Rom Manager and tried to boot into recovery that way, but it said there was my device wasn't supported.
I've been staring at this dang screen for three hours, trying to find a step by step, and I'm coming up empty. Maybe I'm just too frustrated at this point and need a breather.
What I need to know is how to install CWM 6+ on a NT that's either rooted or stock 1.4.2 (I still have the unbrick SD card) so that I can boot into CWM. From there, I can make my way through installing CM10. Help. Please. Am about to chew the lining out of my cheek.
I don't know if this might be helpful? http://forum.xda-developers.com/showthread.php?t=2037368
Sent from my NookColor using Tapatalk 2
Not yet. I was expecting OTA to kick in, updating my current 1.4.2 to 1.4.3, but it hasn't. Honestly starting to think my NT doesn't want to be rehacked LOL
Okay, so here's what I'm doing at the moment...
I'm at rooted stock. I moved CWM 6.0.1.2, CM10, and gapps over to internal SD.
I booted into recovery with an older version CWM SD card (SD card image with Win32 > turned off NT > insert SD > plug in USB to autoboot)
While in recovery (from SD), I flashed CWM 6.0.1.2 , CM10 (meghd00t), and gapps-jb-20121011.
I reboot...
WE HAVE JOY!
Now to check to see if the thing's gonna run right (got a whole lotta "XYZ has stopped" error messages upon boot up)
Dangit, keep getting those error messages about Gapps stopping and Google Play, and other stuff. Not allowing me to do hardly anything I need to. I can't even boot into recovery from the home page---it still loads straight to the Rom. In order to get into recovery, I need to use the SD that I made to get into recovery in the first place. Going to wipe dalvik and the other caches to see if that helps...
After wiping the caches, I boot into CM10 with no error messages. I DL'd a game from my Gmail account, and it appears to be working properly. Thanks for the suggestions and for letting me vent
I just went thru this similar ordeal too. It took me over 3 weeks to finally find a recovery & cm10 combo. What I found is that I couldn't get ANY version of twrp to act right. Indirect's flashing tool was invaluable. I finally used it to flash a cwm 6.x from Laverne's thread. It seems that not all versions of cwm 6.x are compatible with certain cm10 roms too & by chance I hit a combo that finally worked! I'm staying with what I got for a while!
Sent from my Nexus 7 using Tapatalk 2
Hello,
History:
Recently my Droid x2 was acting somewhat slow and randomly rebooting, so I decided to backup some data using titanium backup.
After which, I performed a factory data wipe thing from the android recovery menu.
This went well and I started to restore my old apps and data, afterwards I noticed the same things happening again. So I decided to do the factory data wipe again to fix this.
This led me to think that there was something wrong with one of the system apps, so I slowly went through apps and only installed what I thought I needed.
I ended up repeating this a few times, and at some point used titanium backup to remove some of the stock apps like slacker and youtube.
And now my phone wont get past the motorola logo, although sometimes it does and gets into a boot loop or just gets to the first time set up screen.
History summary:
Basically I backed up the data I wanted to keep, and did some stuff now my phone doesn't function right.
What I am after from any expert is whether or not I can't simply put an update onto my sd card and use the android recovery menu to fix my phone back to the normal stock rom.
If this kind of thing is possible could someone send me a link to the file.
I have tried to use Moonshadows guide (http://forum.xda-developers.com/showthread.php?t=1317707) for SBFing, no luck, can't get it to work.
Also, I am basing this question off of Moonshadow's other guide (http://forum.xda-developers.com/showthread.php?t=1318083) for backup/restoring.
This is a:
Droid X2
Rooted
Running 2.3.5
Moto Updates only work to update, and phone must be complete stock, nothing removed.
to flash sbf phone needs to be in STARTING RSD PROTOCOL SUPPORT
Try ezSBF for dx2
Sent from my XT862 using Tapatalk
just an update
Just in case anyone is curious, ezSBF worked.
I used it, then updated my phone to 2.3.5, and rooted it.
Thanks shadow.
Your welcome, glad it worked
Sent from my XT862 using Tapatalk
Hello all. Long time lurker, first time poster here with a rooting question/situation. I rooted a Verizon Galaxy Nexus, running Android 4.2.2 today. After rooting, I thought to give Cyanogenmod a try and see how I liked it. It worked great, other than that I couldn't get on my Verizon mobile data, despite setting the APN's correctly (or so I thought...) After messing with that for a while, I decided to go back to Android Jelly Bean. I didn't backup the previous Android, because the phone was freshly wiped and had a factory reset done. After downloading a stock Android ROM.zip, I installed it and went back to Android flawlessly. The version didn't come with SuperSU or Busybox, or Titanium Backup (programs I am customary to using with root access, like many others) I went into Titanium Backup like an idiot and started slashing programs, including another Superuser that had been included in the Android ROM flash that I wasn't aware of. After this, I went into SuperSU and it said I would have to boot the phone in recovery mode to get it to work, so I did. I have CWM custom recovery on this phone. After doing that, the phone started booting normally instead of recovery mode, then showed the CWM custom recovery icon, and continued this process for a while. "bootloop". I went to start the phone normally, and the exact same thing happened. Tried custom recovery again, and same thing. Google icon starts, then the CWD logo comes up and continues in this pattern. I can access the boot loader, but can't start the phone or access recovery. To top it off, I never turned USB Debugging on the phone. Any Ideas?