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
Related
Tuesday night I loaded CM7, and then the Market wouldn't update my apps so I decided I would restore BAMF 1.5. After doing so, the Market just gave me "Fails" trying to update, and I could not access recovery, as I was going to do a complete wipe and reflash. Most of Wednesday, an extremely helpful & knowledgable member, Mattgyver83, tried diligently to help me rectify the situation, but to no avail. We tried to Fastboot, tried flash_image, tried fix permissions...shoot, I practically wore out adb..anyway, I ended up reverting back to stock and unrooted. I used jcase's method to revert back to stock, and that was painless, and successful. I decided last night to try rooting again, thinking a fresh root would solve my issue of not being able to access recovery. Root was successful, but I still cannot access recovery, through rom manager, or through bootloader. When I attempt it my Tbolt goes to white HTC screen, and stays there. All functions of my phone now work, and all aspects of root work, except I cannot flash anything. Rom manager shows I have clockwork recovery, but I just can't get to it.
Sorry for the long ramble. If anyone has had this issue, or if anyone knows a fix, I would appreciate it. Otherwise, I wait for Gingerbread.
Thanks
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
travishamockery said:
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
Click to expand...
Click to collapse
Tried that, but thanks. Still just goes to white HTC screen, and stays there until I do battery pull.
jr4000watts said:
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
Click to expand...
Click to collapse
I can get to bootloader, just not able to get into recovery.
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
monolithic said:
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
Click to expand...
Click to collapse
Thanks, but that didn't work. I think something in my os got lost when I restored BAMF from CM7.
Yea I spent a good few hours yesterday trying to help Orio out and we attempted a ton of things to try and fix the recovery issue, this post should offer a bit more insight to the methods used, this is running off memory;
adb reboot recovery failed
Reinstall latest Rom Manager apk and Flash CWM
flash latest rom manager via fastboot (CWM only)
(fastboot flash recovery /sdcard/recovery-clockwork-3.0.2.5.img)
**did not do fastboot erase recovery first**
"return to stock safely and properly" XDAthread by jcase
return to stock image [RUU], reroot, try again
try to boot into recovery via hboot
manually installed fix_permissions.sh script and busybox on rooted stock, ran.. didnt fix
tried to see if flash_image method would work, didn't
All of the above have failed and we basically tried almost all combinations. Not once would this phone get back into recovery, even after flashing the appropriate RUUs which include either stock android or CWM recovery. The only thing we have not currently attempted which might be the last thing left is to do is manually install the nandroid.sh script and do an advanced restore of the recovery image only from a nandroid backup on SD. I would rather not go down this method as it could have an undesired result, I have done it to restore a G1 back in the day but not 100% if its gonna work on a tbolt. Thankfully his phone boots, and we can get into hboot, but yea.. pretend recovery just doesnt exist at all...
Curious if anyone has any knowledge above what we have already tried.
monolithic said:
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Click to expand...
Click to collapse
I recall the same thing and its a good thought however that was mostly a generic error due to a CWM update and CM6 (I think) but either way flashing an RUU should override this shortcoming and im pretty sure that issue was worked out in CWM as well.
Not to be rude, but I don't think this question belongs in the development section.
Orio56 said:
I can get to bootloader, just not able to get into recovery.
Click to expand...
Click to collapse
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
hogowner said:
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
Click to expand...
Click to collapse
Thanks, but no, I deleted that after loading it. I actually reverted back to stock/unrooted last night and rerooted and the problem still remains. It's quite strange.
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
shelooga said:
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
Click to expand...
Click to collapse
That is what I was going to suggest. In ROM Manager at the very bottom try and flash an older version.
Sent from my ADR6400L using XDA Premium App
SUCCESS !!!
I fixed it !
Apparently, when I loaded up cm7, files showed up about the same time on my sdcard in clockworkmod download file. I deleted those files, and reflashed clockworkmod in rom manager, (which this time took like 3 - 4 minutes), and rebooted into recovery and it worked...did it again, just in case it was a fluke and it worked.
All is well now...the planets are realigned !!!
Thanks everyone for your ideas and especially thanks to mattgyver83 who helped me for something like 4 hours yesterday. Exceptional kindness !!
mods...you can close this thread.
GREAT NEWS!!!! CONGRATULATIONS!!
THANKS FOR REPORTING BACK!
This may help out other members with the same problem!!
now go ahead and start playing with your T-BOLT again!
That's a very odd solution. My first two things to try would have been:
1) fastboot:
fastboot erase recovery
fastboot flash recovery C:\some\local\path\recovery.img
You can't, well, probably shouldn't, flash a recovery from the /sdcard. When in fastboot mode I don't think the sdcard is even mounted. Either way, I think fastboot needs the img file on the local file system.
2) Create a PG05IMG.zip file with the recovery.img file in it, and flash that through HBOOT. Although this should have been done in some form or fashion when you downgraded or re-rooted, so YMMV.
Alright, here's the deal. I had some problems with my Atrix so I ended up having to re-flash RomRacer's Recovery. Then I tried re-flashing Neutrino ROM, when it finally booted into it a windows entitled "Android System" popped up and then a message boxed popped up saying "Shutting Down". It does this for EVERY single rom I flash. I tried Neutrino 2.7 and 2.6, CM7 Ba2Tf, Jokersax's CM9, and Alien ROM. All do exactly the same thing. Can anyone help me?
EDIT: I just tried flashing MIUI and CM9 via Kitchen Sink ROM and both did the same thing. Boots to lock screen then vibrates and shuts down.
EDIT 2: If it helps, this isn't my first time flashing a ROM, I've flash all of these multiple times, so I don't really know what the issue is.
EDIT 3: I just did 3 different restores including one to the original ROM, it did the exact same thing. I also tried 2 different batteries, both of which are fully charged.
**BUMP**
Try a full wipe from fastboot, then try to flash a fruitcake.
fastboot erase boot
fastboot erase system
etc.
There are a couple of scripts in forums which work nicely if you're feeling lazy. Best thing to try with any problem like this is just start over from the beginning properly.
Sent from my MB860 using xda premium
I already tried multiple fastboot wipes, but I'm downloading this "Fruitcake" and I'll FB wipe then flash that and see if it works.
Alright. Did a full fastboot wipe. Flashed the 2.3.4 Fruitcake. Won't even boot into the lockscreen, just boot loops the boot animation.
May have to flash stock kernel also. Can do from fastboot.
Sent from my MB860 using xda premium
I don't mean to sound like a noob, but I searched and I can't seem to find the stock kernel. I found a couple links, but they were all the same multiupload link and did not work. Do you have a link?
Sorry, I don't have that kernel or a link to it.
I can't see what the problem would be if you are wiping fully via fastboot and flashing a ROM, whichever one you choose. If you flash CM7.2 for example on a clean phone, there shouldn't be a problem unless something else is going on, like hardware issues.
What problems did you originally have that resulted in you re-flashing recovery? Maybe that's where we should start in figuring this out.
I was running Alien ROM perfectly fine. For whatever reason I decided I wanted to flash Neutrino ROM V2.7 and I didn't realize how low my battery was when I flashed it. I think the battery may have died either during or just after flash. So i bought a new battery and a wall charger so I could charge the battery outside of the phone. When I put the new battery in, it would not boot into recovery, so I re-flashed recovery and that's where I'm at now.
Stock 2.3.6 OS, webtop, and kernel are here > http://forum.xda-developers.com/showpost.php?p=24472332&postcount=1
This version is rooted also.
Thank you very much for your help. I will flash everything back to complete stock, and hopefully that solves this. Thank you again!
Sounds like your system believes battery is low, you can try wiping data and installing CM, then power off your phone, plug it to wall charger and leave it charging for some time. If it still doesn't work, you can try pulling the battery while charging (will show a "?" battery icon) and then put it back in.
I just did a full fastboot wipe, then flash all 3 of the stock things, OS, kernel, and Webtop. It won't boot past red flashing Motorola Logo. I think I'll try what the above user says.
I'm having some issues getting the phone to "charge" If I put the battery in and then plug it into a wall charger, it turns on and starts the boot loop. If I plug it in with no battery, the battery with a "?" shows up, but then when I put in a battery nothing happens.
**BUMP**.....
BUMP 2. Any last ditch effort?
I have been runnig CM9 for about two weeks. Really liked it.
Thought I would flash the build.props mashup. After I did I started getting the following message:
process com.android.phone is not responding. Couldn't do anything but pull the battery.
Plugged into power strip.
Went into CM7 Patched Recovery recovery. Wipe Cache and Dalvik. No change.
Wipe Data. No change.
Also ran Fix Permissions. No change.
Don't ask me why but I ran Key Test.. BAD MOVE. Couldn't get out of Key Test.
Pulled battery again.
Still plugged into power strip. Now I am stcuk at the red Motto M and can't get past it.
If I unplugged and reboot CM9 will start but again I get process com.android.phone is not responding.
Any help would be greatly appreciated.
The reason it messed up is because the mash up is already built into CM9 and probably has different tweaks by dragonzkiller. If you can still get into the recovery, try flashing the CM9 ROM zip again. It should overwrite the problem.
EDIT: Actually if you already wiped data, you may not be able to get into BSR. So if you cant get into the system, you may have to SBF. Unless you can use ADB to push BSR to the phone which I dont know how to do or even if it will work. I've never used that but read people talking about stuff like that.
If you cant fix it, follow the instructions here to reset your phone:
http://forum.xda-developers.com/showthread.php?t=1317707
Thanks - nnow on the root!
SBF worked fine. Thanks.
Back on 2.3.4. On to root, except my employer has blocked to down site..
and then on to CM7 and CM9.
Thanks again JS
jsgraphicart said:
The reason it messed up is because the mash up is already built into CM9 and probably has different tweaks by dragonzkiller. If you can still get into the recovery, try flashing the CM9 ROM zip again. It should overwrite the problem.
EDIT: Actually if you already wiped data, you may not be able to get into BSR. So if you cant get into the system, you may have to SBF. Unless you can use ADB to push BSR to the phone which I dont know how to do or even if it will work. I've never used that but read people talking about stuff like that.
If you cant fix it, follow the instructions here to reset your phone:
http://forum.xda-developers.com/showthread.php?t=1317707
Click to expand...
Click to collapse
Glad you got it back to working condition. Next time you have a problem like that, flashing the ROM again should take care of it. If not, try to always have a ROM backup on hand.
And also, stay away from mashup when on CM9 as well as the Test Keys function in CM7 recovery.
If I hadn't foolishly done Test Keys my next step was to flash the ROM again.
Thanks again.
jsgraphicart said:
Glad you got it back to working condition. Next time you have a problem like that, flashing the ROM again should take care of it. If not, try to always have a ROM backup on hand.
Click to expand...
Click to collapse
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
So I got bored and decided to start messing with my old X2. It is rooted with Eclipse V2.3 ROM. All I did was change the theme a couple times. Worked perfect for the first two or three but then I found one that caught my eye.
This one here.
http://forum.xda-developers.com/showthread.php?t=1380719
It installed fine, liked the look, but had two problems right off the bat. First was that Eclipse Tools kept force closing so there was no way to get into bootstrap recovery. Second was when I pressed the power button, it would only reboot the phone, nothing else. So I decided to do a factory data reset on it to see if that would fix it...
It did the reset, but now it is stuck in the bootscreen. It gets past the red M, but that's it. Is it bricked or is there something I can do to get it back? I wouldn't mind doing a SBF and/or totally rerooting it again, but I need to find out how to do this while stuck in the boot screen with no way to get into recovery. Can anyone help me out?
if you are on eclipse 2.3, blue neon steel is for 1.3, not the version you are on. this is why youre having problems. 1.3 is based on 2.3.4, and 2.3 is based on 2.3.5 , so themes are not backwards compatable. or any compatable, it should be made specifically for your version of eclipse. ble neon is also my favorite theme, but an update for 2.3 seems unlikely, as i have tried to contact kevin about it before. everyone has moved on to other phones. a strong few still deal with this beast.
Well crap... Didn't even think about that. I have the other themes on my SD card, all I need to do is get into Bootstrap Recovery so that I can install the zip file. Is there a way to get into Bootstrap Recovery from a power off state?
ramthis9501 said:
Well crap... Didn't even think about that. I have the other themes on my SD card, all I need to do is get into Bootstrap Recovery so that I can install the zip file. Is there a way to get into Bootstrap Recovery from a power off state?
Click to expand...
Click to collapse
Try the Motorola system recovery by holding down volume down and power button. Wipe data and cache partition.
Did you ever install the bootstrap recovery? If so, try plugging in your charger with phone off to see if it will boot into bsr. Try this step first, then if that doesn't work try system recovery. If neither of these work you will more than likely need to sbf.
Sent from my Droid X2 using Tapatalk 2
Just plugged it in and it's stuck on the red M. I tried using stock recovery earlier and it didn't fix the problem either so hopefully SBF will be my rescue. Thanks for the help
give cm10 a try while youre on 2.3.4 :good: