So, I installed safestrap and rebooted. Everything was fine, I let it boot normally and then rebooted again to get into recovery. In the recovery menu I tried installing a zip, and it told me I had to enable the safe system, so I did so. Now when I reboot the phone, I get a pure black screen and the phone is completely non-responsive. Trying to power it on does nothing, what should I do?
edit: OK, if I hold down power & the volume key, the screen will flash. If I hold down power again I can get back into recovery. I'm trying to disable safe system now, hopefully that'll work.
edit 2: Yep, that worked
Just curious in the safe side, did you actually flash any custom ROM?
Sent from my DROID RAZR using xda app-developers app
Related
Hi. I looked throughout this cunk of the forum and couldn't find anything on the mater, so figured I'd ask.
I cannot get Recovery to work on my X2. Just got it yesterday (Love it so far, but I'd love to put the Atrix 4G on my phone.) I tried the boostrap method using the System Recovery app, and tried Clockwork Recovery. Reboot Into Recovery with System simply rebooted my phone, and the same with CWR. Manually pushing my phone into Recovery (power button and volume down at boot to select the option) Gives me an error. Any ideas?
Yes, I made sure my phone was rooted. lol
With the bootstrap you did hit install recovery first and then plugged into the wall Before hitting recovery mode, right?
Sent from my DROID X2 using Tapatalk
...Damnit, nope. It was plugged into my computer the entire time. I had it set to Charge Only, though.
Posted in wrong section...your issue seems to be resolved tho.
Recently i flashed the CM9 rom onto my Droid X2. Followed the instructions and everything installed correctly. Since it has been a couple of days and I have installed all my programs and got everything where i wanted it, i wanted to make a backup.
Soon i discovered that I didnt have System Recovery installed. SO i began looking into my SD card and i have two files,MOTODX2_Bootstrap_signed.apk. So i decided to install it, everything went fine but now my phone is stuck in a boot loop. It wont even boot into CM9.
Is there another BSR that i should be flashing instead of this one. Maybe the ReRecovery one? i know theres a [patched] BSR to install but i gave me the same problems.
Thanks EHB
Hi, for Cyanogenmod9 use the CM7 PATCHED BSR. It works just fine for me everyday. I'm kind of addicted to flashing ROMs for some reason and usually am on different ones multiple times a day. Always in BSR either restoring or backing up. The patched BSR for CM7 works just fine for me. For reference, in the app drawer it should say "CM7 System Recovery" not just System Recovery.
I'm not sure if it has been looked into by dev's yet or not, but the day CM9 was released I actually did flash the CM7 ReRecovery zip and I was able to boot to BSR from a powered off state just by plugging in. I wasn't sure if it was okay to use, so I installed a fresh CM9 without it. I don't know if this is 100% safe or if there would be any issues from using the ReRecovery zip. I would recommend just installing the patched CM7 apk and trying to use that.
Here's the link to the patched CM7 Recovery. Pulled straight from the CM7 thread
http://www.mediafire.com/?pzz4413k6wggcao
***^That BSR is an application. You download, install and run it on your phone. The ReRecovery is a flashable zip you can install once already inside of BSR allowing you to get into custom recovery say for example, if you're boot looping. ***
================================================
If you're still having bootloop issues, try this;
-Grab your ECOMOTO charger, plug into A/C power, pull battery, replace & plug into wall.
- Wait for the Motorola logo to disappear and the battery charging icon to appear (this can take several minutes)
-When you see the battery charging icon, unplug your phone and pull your battery.
-Reinstall the battery and hold the VOLUME DOWN key while powering on the device. Release the VOLUME DOWN button when it turns on.
You should now see "FASTBOOT" in white text above the Motorola logo.
-Press the volume down key several times until you see ANDROID RECOVERY.
-With ANDROID RECOVERY now showing where fasboot was, press the VOLUME UP button. It will tell you that it is starting android recovery mode.
This will take you to a screen that shows a picture of an android next to a triangle with an exclamation mark (!) inside of it.
-From that screen press both the VOLUME UP and VOLUME DOWN keys at the same time.
If you made it this far, you're now in the stock android recovery. Using the volume buttons, key down to Wipe Cache Partition then press the power button to select. You will be taken to a confirmation screen. Key down and select Yes. Wait for it to complete. After you wipe the cache try rebooting back into CM9. This will take slightly longer than usual as your cache has to rebuild itself. If you can boot back up successfully, click the link above. Download the patched CM7 Bootstrap Recovery and install it. If you don't know what to do from there, open the application "CM7 System Recovery" and click "Install Recovery" -- You will now be prompted to grant or deny it superuser permissions. Allow them. You will receive a message saying the install was a success! Click OK. Now plug your phone back into the wall outlet and hit "Recovery Mode" and your phone will boot into BSR! From there just go to backup and save it to your external SD card. You can find your backups later via the file explorer of your choice under /mnt/sdcard/clockworkmod/backup. Note: You can rename the file so you know which ROM is which, just don't add spaces to the file name or it will ruin your backup and you will not be able to restore it. NO SPACES!!!
FYI you will still see the Motorola logo immediately after it turns back on. It takes a minute or two to boot into custom recovery.
I've been through a lot of trial and error with the X2 and these steps have helped me plenty of times. Hopefully they do the same for you....Good luck.
Cyanogenmod all day
Thanks for the information.
I knew basically everything you said except for the "wipe cache partition". Why is this necessary? I know that it doesn't delete personal information but what does it wipe/delete?
Im going wait to do this tomorrow - my day off. Im just worried that its going do the same thing and ill have to reflash and start all over again.
Thanks again EHB
Wiping the cache partition clears any/all application data and common app components. It does not wipe apps themselves, rather the files that the app generates when used.
Wiping it is necessary because when core system components are changed, the resources used by the apps also (could) change. Having stale app data after a system change or tweak can cause problems, which is why it is best to clear it. It gets rebuilt as apps are used.
RoyJ said:
- Wait for the Motorola logo to disappear and the battery charging icon to appear (this can take several minutes)
Click to expand...
Click to collapse
I'm afraid I'm in the same boat and am going through these steps to hopefully get back on the right track. When you say the battery charging icon can take several minutes... are you suggesting 3-5 minutes, or up to 30 minutes? Because... I'm at about 35 minutes right now and am getting pretty nervous.
just skip to this part, if you can
remove charger and battery
-Reinstall the battery and hold the VOLUME DOWN key while powering on the device. Release the VOLUME DOWN button when it turns on.
You should now see "FASTBOOT" in white text above the Motorola logo.
-Press the volume down key several times until you see ANDROID RECOVERY.
-With ANDROID RECOVERY now showing where fasboot was, press the VOLUME UP button. It will tell you that it is starting android recovery mode.
Click to expand...
Click to collapse
Patched BSR, please help!!
RoyJ said:
Hi, for Cyanogenmod9 use the CM7 PATCHED BSR. It works just fine for me everyday. I'm kind of addicted to flashing ROMs for some reason and usually am on different ones multiple times a day. Always in BSR either restoring or backing up. The patched BSR for CM7 works just fine for me. For reference, in the app drawer it should say "CM7 System Recovery" not just System Recovery.
I'm not sure if it has been looked into by dev's yet or not, but the day CM9 was released I actually did flash the CM7 ReRecovery zip and I was able to boot to BSR from a powered off state just by plugging in. I wasn't sure if it was okay to use, so I installed a fresh CM9 without it. I don't know if this is 100% safe or if there would be any issues from using the ReRecovery zip. I would recommend just installing the patched CM7 apk and trying to use that.
***^That BSR is an application. You download, install and run it on your phone. The ReRecovery is a flashable zip you can install once already inside of BSR allowing you to get into custom recovery say for example, if you're boot looping. ***
================================================
If you're still having bootloop issues, try this;
-Grab your ECOMOTO charger, plug into A/C power, pull battery, replace & plug into wall.
- Wait for the Motorola logo to disappear and the battery charging icon to appear (this can take several minutes)
-When you see the battery charging icon, unplug your phone and pull your battery.
-Reinstall the battery and hold the VOLUME DOWN key while powering on the device. Release the VOLUME DOWN button when it turns on.
You should now see "FASTBOOT" in white text above the Motorola logo.
-Press the volume down key several times until you see ANDROID RECOVERY.
-With ANDROID RECOVERY now showing where fasboot was, press the VOLUME UP button. It will tell you that it is starting android recovery mode.
This will take you to a screen that shows a picture of an android next to a triangle with an exclamation mark (!) inside of it.
-From that screen press both the VOLUME UP and VOLUME DOWN keys at the same time.
If you made it this far, you're now in the stock android recovery. Using the volume buttons, key down to Wipe Cache Partition then press the power button to select. You will be taken to a confirmation screen. Key down and select Yes. Wait for it to complete. After you wipe the cache try rebooting back into CM9. This will take slightly longer than usual as your cache has to rebuild itself. If you can boot back up successfully, click the link above. Download the patched CM7 Bootstrap Recovery and install it. If you don't know what to do from there, open the application "CM7 System Recovery" and click "Install Recovery" -- You will now be prompted to grant or deny it superuser permissions. Allow them. You will receive a message saying the install was a success! Click OK. Now plug your phone back into the wall outlet and hit "Recovery Mode" and your phone will boot into BSR! From there just go to backup and save it to your external SD card. You can find your backups later via the file explorer of your choice under /mnt/sdcard/clockworkmod/backup. Note: You can rename the file so you know which ROM is which, just don't add spaces to the file name or it will ruin your backup and you will not be able to restore it. NO SPACES!!!
FYI you will still see the Motorola logo immediately after it turns back on. It takes a minute or two to boot into custom recovery.
I've been through a lot of trial and error with the X2 and these steps have helped me plenty of times. Hopefully they do the same for you....Good luck.
Cyanogenmod all day
Click to expand...
Click to collapse
I am having a similar but different problem with the patched BSR. I had it running fine while using CM9 on my Droid X2, but now I am running MIUI, and when I install and attempt to get into the custom recovery, it seems like it attempts to load it, but does not. What I get is a jumbled screen that has the colors of the custom recovery, so I can tell it is attempting to come up, but something is going wrong. It shows that jumbled screen for a few seconds, then goes black and eventually just shuts down. I have tried EVERYTHING I can think of to fix this. I have tried a fresh download of the patched BSR, and even did a fresh SBF and reinstall of MIUI, but nothing fixes it. Any advice you have would be greatly appreciated. Thanks!
I would re flash sbf
if you have been using ezSBF
use rsd lite, vise versa, or try a different sbf version like 2.3.3 and take ota update
or see if someone could upload a nandroid backup
Sent from my MB870 using xda premium
The odd thing is, if I restore to CM7 or CM9, then the patched BSR will work again. It seems it only goes bad with MIUI. Could the ROM somehow affect the BSR installation and/or function? I wouldn't think this is the case, as other are using the patched BSR with MIUI without trouble.
Sent from my MB870 using xda app-developers app
So, I unlocked and rooted my phone earlier and was looking for a rom to install. I downloaded one and installed it, but then it would get stuck on the boot screen of the rom. I realized after that, I had gotten it from an ATT forum for roms and I have a Verizon phone. I've tried to hold down power + volume up, power + volume down, power + volume up + volume down ... I've tried it on just the battery and with it plugged in, but it continues to just go to the boot screen and sitting there. Is there anything I can do?
This can be deleted ... Just found out it needed to be power + volume up + home key.
Ok .... Still having issues
I have tried multiple roms and I'm not making it past the boot screen on any
LiquidSmooth - The "Galaxy 2" initial screen would start jumping around everywhere and then just go black.
JellyBeans - Wouldn't even install.
Jedi - Just sits on the boot logo
Downloading MeanBean now.
j0hnq229 said:
Ok .... Still having issues
I have tried multiple roms and I'm not making it past the boot screen on any
LiquidSmooth - The "Galaxy 2" initial screen would start jumping around everywhere and then just go black.
JellyBeans - Wouldn't even install.
Jedi - Just sits on the boot logo
Downloading MeanBean now.
Click to expand...
Click to collapse
Are you doing s factory reset when flashing
Sent from my SGH-T889 using xda app-developers app
Make sure you're putting the zip on the internal memory not your SD card.
j0hnq229 said:
So, I unlocked and rooted my phone earlier and was looking for a rom to install. I downloaded one and installed it, but then it would get stuck on the boot screen of the rom. I realized after that, I had gotten it from an ATT forum for roms and I have a Verizon phone. I've tried to hold down power + volume up, power + volume down, power + volume up + volume down ... I've tried it on just the battery and with it plugged in, but it continues to just go to the boot screen and sitting there. Is there anything I can do?
Click to expand...
Click to collapse
Do you know which recovery and version you are using? You may want/need to upgrade...worth a shoot anyways
I'm sure you already have tried this but I am not going to assume that you have. Did you wipe EVERYTHING, excluding external sd card?
Or, a better option my be to download a stock verizon rom, flash it with Odin and then reunlock and reroot.
shadowdweller said:
I'm sure you already have tried this but I am not going to assume that you have. Did you wipe EVERYTHING, excluding external sd card?
Or, a better option my be to download a stock verizon rom, flash it with Odin and then reunlock and reroot.
Click to expand...
Click to collapse
Download the stock VZW Rom and PIT file and re-flash through ODIN.
Hey everyone, my S4 is running TWRP and it was fine until just now...it keeps freezing when I boot into recovery in which I have to do a battery pull...on top of that, when I pull the battery and put it back in, I'll power it on and it will automatically boot into recovery without me doing anything! Idk what to do, should I have used CWM instead? This is a never ending loop cycle now! Please help!
Iskateforfree said:
Hey everyone, my S4 is running TWRP and it was fine until just now...it keeps freezing when I boot into recovery in which I have to do a battery pull...on top of that, when I pull the battery and put it back in, I'll power it on and it will automatically boot into recovery without me doing anything! Idk what to do, should I have used CWM instead? This is a never ending loop cycle now! Please help!
Click to expand...
Click to collapse
You can end the cycle by booting into download mode. After you pull your battery and reinsert it, hold volume down + power button then just cancel when it asks if you want to boot into download mode.
Sent from my SCH-I545 using xda app-developers app
Surge1223 said:
You can end the cycle by booting into download mode. After you pull your battery and reinsert it, hold volume down + power button then just cancel when it asks if you want to boot into download mode.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
THANKS SO MUCH! I think something is messed up with TWRP cause it's been acting funny lately and now this happens.
Failing to boot
Surge1223 said:
You can end the cycle by booting into download mode. After you pull your battery and reinsert it, hold volume down + power button then just cancel when it asks if you want to boot into download mode.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
I installed Hyperdrive RLS10.2 on my Verizon GS4 and tried to reboot, but now it shows me the Samsung custom boot and simply recycles doing this. If I boot to download mode, and deselect download it goes into the same loop.. Any suggestions on how to fix this?
HELP! Recovery bootloop, no adb, no odin, no kies
wally44 said:
I installed Hyperdrive RLS10.2 on my Verizon GS4 and tried to reboot, but now it shows me the Samsung custom boot and simply recycles doing this. If I boot to download mode, and deselect download it goes into the same loop.. Any suggestions on how to fix this?
Click to expand...
Click to collapse
Same EXACT problem here. Tried to install the new TWRP 2.6.3.1 to prep for a 4.3 ROM install. TWRP suggest a goo install .The Goo install ran through, goo was back to it's main menu and i hit reboot recovery, but still had 2.6.0. So, I renamed the 2.6.3.1 img and put it in the BHP090808_I545_ALL_IN_ONE_TOOL all in one dir, then flashed it through that. Went fine, odined it in, then rebooted into recovery like usual..... Except, recovery never comes up. it just sits there with the Recovery Booting.... thing and Samsung custom screen FOREVER! I tried to use all in one tool to reflash 2.6.0 and it fails becasue odin doesn't see the phone, even thought it's sitting on the booting recovery screen. Tried button hold to get into download, same problems, I get the vol up prompt, hit vol up, get the d/l mode screen for 1-3 secs and then it just reboots itself - into recovery booting screen if i don't try d/l mode,.And odin doesn't see it while the d/l mode vol up msg or d/l active screen is up. Only way to stop bootloops temporarily is batt pull.
So to summarize, recovery bootloop but never gets to recovery, adb can't connect, odin doesn't see the phone at ANY time, during recovery booting, d/l mode confirm screen, or short time of d/l mode screen itself, and I have no tarball to odin a twrp recovery in even if i could get odin going b/c they only offer img files now. Oh, and Kies doesn't even see the phone due to mods. ANY help would be GREATLY appreciated!!
Also, after batt pull, phone sits with blank screen even when on charger/usb and i get a vibrate every 3 seconds continuously.
:crying:
Suggestions?
I545 loki'd, TWRP (read post), HyperDrive 9.1 MDK (which I'd like to keep at nearly any cost)
TIA, for all your conisderation and previous, current, and future help! :good:
same exact problem on tmo
I tried to flash a cm nightly, and then tried to restore it. then this problem occured. any help?
Use Flashify to install TWRP. Goo hasn't worked correctly for some time now.
FernBch said:
Use Flashify to install TWRP. Goo hasn't worked correctly for some time now.
Click to expand...
Click to collapse
This. Flashify is a really good app to use for flashing twrp and will even download for you.
But how are you supposed to use flashify if you're stuck in a boot loop.
twrp keeps booting into recovery mode, I can't get it to just load up my phone OS (CM12)
How do I get my phone to run.
Surge1223 said:
You can end the cycle by booting into download mode. After you pull your battery and reinsert it, hold volume down + power button then just cancel when it asks if you want to boot into download mode.
Click to expand...
Click to collapse
I know this is a ghost thread, but my wife still uses an S4 and somehow it got into the configuration where it would only boot into recovery mode. This trick worked, in fact, I didn't even get the question about booting into download mode; it just booted normally.
Guys,
I'm rooted, with MDK base, and THOUGHT I had a working version of CWM (maybe 6.0.2.3?)
I was in the process of getting ready to try out a new ROM; going through the usual motions, formatting system, data, cache, and for good measure, I finished with a Wipe Data/Factory Reset (which I believe just does the same things again).
The phone suddenly rebooted and froze at the samsung custom screen. When I try to get back to recovery, I can't (hold down up-vol and power; blue message appears and disappears quickly in upper left, and back to Samsung custom lock screen.
I'm stuck. In the past, I always got into recovery by rebooting with ROM Manager, so I haven't really had to use the power-on/ vol up method (thus it may never have worked).
I can get into download mode. So I'm thinking - assuming - that the first thing I should try is to Odin CWM. But I'm admittedly confused, because all of the posts that relate to installing CWM seem to be in the context of the rooting process, and assume you have the ability to place certain files in rooted directories (like loki), which I obviously can't b/c I can't boot.
1) Is re-flashing CWM the right approach ? If so, is there a .TAR file somewhere with just CWM? I can't find an Odin-flashable .tar. EDIT: I found one, but it's designated for i9505. Same thing?
2) If that's not the right approach (or I'm just an idiot and don't know how to get into a working recovery), please advise
Thanks!
Turn the phone off.
Hold volume up and press the power button until it vibrates.
When it vibrates let go of the power and stay holding volume up until you see the recovery splash.
I've found that sometimes continuing to hold the power button will cancel the call for recovery boot. Not sure why.
You can always Odin if that doesn't work.
And I don't know of an Odin package for vzw recovery.
sent from my GE gs4
Dubbsy said:
Turn the phone off.
Hold volume up and press the power button until it vibrates.
When it vibrates let go of the power and stay holding volume up until you see the recovery splash.
Click to expand...
Click to collapse
O - M - G !? Unbelievable. Thanks a BILLION! You just saved me a ton of time.
EDIT: Cr*p. Not out of the woods yet. Now, when choosing 'Install from SD Card' I'm getting 'E: Can't mount /sdcard/'
I'll post this issue in a separate Q.