ICS 232
Anyone have problems getting bionic bootstrapper to boot into cwm I am having problems getting it to work any help would be appreciated
Sent from my DROID BIONIC using xda premium
I'm having the same issue. I've installed Bootstrapper APK, run the install from the app, then rebooted from the app. It will reboot, get the red M, then sit at a black screen and require a battery pull.
I've tried two different Bootstrap APKs from online. Using 232. I'd also like to find a solution.
I keep getting a superuser has stopped working message every time I choose reboot recovery
Sent from my DROID BIONIC ( ICS 232)
i don't think the normal boostrapper works with ICS you will have to get a version for ICS.
No it works just fine I'm on 235 and I just rebooted into recovery through bootstrap,
sparkyman216 helped me on Twitter and told me to delete the junk out of the preinstall folder. I did that, reinstalled the bootstrapper, and it worked like a charm.
I'm having the same problem now. I installed BionicBootStrap in the .244 ICS system. Then reboot won't get into the system. It stays at the red eye boot animation forever. How to fix this? Thanks.
A couple days ago I decided to load the new Safestrap Hashcode linked to. Everything went very well, and I have been running Maverick 4.5 in slot 2 as my daily driver. I was able to get back into Safestrap using the menu button. I also loaded Gummybear ICS into Slot 3, but went back to Maverick.
Yesterday I was going to go back into Safestrap and switch to the Gummybear/slot 3 rom to check it out.
I can't get back into Safestrap at all. I am stuck in the Maverick 4.5 rom.
One thing I did notice and do not understand: When I use Titanium Backup or the Reboot Widget to "Reboot into Recovery", I get a Yellow Triangle with an Exclamation Mark and the Android guy.
mhelm23 said:
One thing I did notice and do not understand: When I use Titanium Backup or the Reboot Widget to "Reboot into Recovery", I get a Yellow Triangle with an Exclamation Mark and the Android guy.
Click to expand...
Click to collapse
That's the stock Droid 3 recovery. Using a reboot recovery will lead to that, and will not allow Safestrap's bootloader to intercept the boot and activate Safestrap recovery.
I haven't tried running Safestrap 3.05 myself, since it's still not official, but I do know that you cannot reboot recovery as you describe to to get into Safestrap for any version of Safestrap.
mhelm23 said:
A couple days ago I decided to load the new Safestrap Hashcode linked to. Everything went very well, and I have been running Maverick 4.5 in slot 2 as my daily driver. I was able to get back into Safestrap using the menu button. I also loaded Gummybear ICS into Slot 3, but went back to Maverick.
Yesterday I was going to go back into Safestrap and switch to the Gummybear/slot 3 rom to check it out.
I can't get back into Safestrap at all. I am stuck in the Maverick 4.5 rom.
One thing I did notice and do not understand: When I use Titanium Backup or the Reboot Widget to "Reboot into Recovery", I get a Yellow Triangle with an Exclamation Mark and the Android guy.
Click to expand...
Click to collapse
thats the stock recovery
now. do you still get the boot menu splash page where it asks you to input the menu key or continue?
if so hit the menu many times or hit on the screen the hit menu for recovery image section, as it shoulod also work.
maybe my next question is silly or already tried, but have you tried to try it with the charger disconnected?
some times when my droid 3 is connected, the touch screen gets un responsive o registers more than input
hope this helps
I now have the same problem. I see the splash screen and it vibrates and reacts when I press the menu button, however it does not boot into safestrap v3.05.
From the JB topic it seems more people have this problem!
DoubleYouPee said:
I now have the same problem. I see the splash screen and it vibrates and reacts when I press the menu button, however it does not boot into safestrap v3.05.
From the JB topic it seems more people have this problem!
Click to expand...
Click to collapse
For those with trouble entering recovery with SS 3.05
The EASIEST and most DEPENDABLE way I've found to boot into the new SS 3.05 is;
Shutdown the phone
Slide open keyboard
Hold M and press the power button to boot the phone (still holding M, release when it boots the next step)
Immediately a menu pops up
Press Volume DOWN to highlight "BP Tools" (tap several times, be quick, if you wait too long, it'll automatically select what is highlighted)
Press Volume UP to select it.
Phone will reboot showing the M logo, then proceed into SS Recovery.
Skreelink said:
For those with trouble entering recovery with SS 3.05
The EASIEST and most DEPENDABLE way I've found to boot into the new SS 3.05 is;
Shutdown the phone
Slide open keyboard
Hold M and press the power button to boot the phone (still holding M, release when it boots the next step)
Immediately a menu pops up
Press Volume DOWN to highlight "BP Tools" (tap several times, be quick, if you wait too long, it'll automatically select what is highlighted)
Press Volume UP to select it.
Phone will reboot showing the M logo, then proceed into SS Recovery.
Click to expand...
Click to collapse
This did not work for me. It just hangs on the Motorola splash screen after choosing BP Tools. Just tried a few moments ago.
Also I haven't had my phone plugged in or charging.
Sent from my DROID3 using xda premium
mhelm23 said:
This did not work for me. It just hangs on the Motorola splash screen after choosing BP Tools. Just tried a few moments ago.
Also I haven't had my phone plugged in or charging.
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
Strange, I have tried it several times... worked each time... maybe try reinstalling safestrap 3.05? Back up what you can of course, stock should not be touched.
Skreelink said:
Strange, I have tried it several times... worked each time... maybe try reinstalling safestrap 3.05? Back up what you can of course, stock should not be touched.
Click to expand...
Click to collapse
Yea - I tried that too. I am really at a loss.
Sent from my DROID3 using xda premium
I am sittin in the same spot. Can't boot into recovery...
Sent from my DROID3 using xda app-developers app
Skreelink said:
For those with trouble entering recovery with SS 3.05
The EASIEST and most DEPENDABLE way I've found to boot into the new SS 3.05 is;
Shutdown the phone
Slide open keyboard
Hold M and press the power button to boot the phone (still holding M, release when it boots the next step)
Immediately a menu pops up
Press Volume DOWN to highlight "BP Tools" (tap several times, be quick, if you wait too long, it'll automatically select what is highlighted)
Press Volume UP to select it.
Phone will reboot showing the M logo, then proceed into SS Recovery.
Click to expand...
Click to collapse
Had this problem today after creating a rom slot and flashing a new rom, this worked for me however I had to try it a few times. Once I got into recovery I wiped the rom and rom slot and ss3 is working properly now. Not sure if this was a rom issue or ss3.
Sent from my DROID3 using XDA
i had the same problem. and a bootloop top...
i have complete install my droid everything is lost...
another question. my "new" droid has the build 860 and withe safetrap i installed 2 other system.
can i update the stock to 906 without loosing safetrap and the 2 new systems?
dabayer said:
i had the same problem. and a bootloop top...
i have complete install my droid everything is lost...
another question. my "new" droid has the build 860 and withe safetrap i installed 2 other system.
can i update the stock to 906 without loosing safetrap and the 2 new systems?
Click to expand...
Click to collapse
When you run the OTA update to 906, it will remove the Safestrap bootstrap and will unroot as well. However, you can reroot with Motofail, then run the Safestrap app again to install recovery, and you slots *should* still be there. Perhaps making a backup of each slot before running the OTA would be smart.
doogald said:
When you run the OTA update to 906, it will remove the Safestrap bootstrap and will unroot as well. However, you can reroot with Motofail, then run the Safestrap app again to install recovery, and you slots *should* still be there. Perhaps making a backup of each slot before running the OTA would be smart.
Click to expand...
Click to collapse
i dont like the word "should"
ok i try to save the files in safetrap and try an OTA. yesterday the ota didn't run but i think i have to wait longer thar it starts the installation than the 10 minutes...
The slots are all stored on the internal storage (the mount point /sdcard) on the phone, so as long as you don't format internal storage, they should stay there.
I should note that I have never tried installing the OTA with safestrap 3.05 installed - I did it with 1.08. Actually, you may want to activate the stock slot, go into the safestrap app and uninstall recovery, and then try running the OTA. It's possible that the OTA will balk with a custom recovery installed - I don't remember, and, like I said, I never tried with Safestrap 3.05 installed.
You can also download the OTA, copy it to an external SD card, and manually run the update from stock recovery. See this thread: http://forum.xda-developers.com/showthread.php?t=1643521
[edit] Sorry - that link is for an update from 890 to 906. I forgot that you were not on 890. Sorry about that...
I had almost the same problem with my phone, the diference is that mine got stuck on non safe system (Stock ROM). Initializing the phone with th Android Recovery (Turning on with the key "m" pressed down) and choosing BP Tools doesn't worked.
- Phone: Milestone 3 XT860 (Brazilian Droid 3)
- Carrier: Vivo
- Current ROM: Stock 2.3.5 - 5.2.440
I have a recurring issue trying to install any roms on this device. Every time I perform an install, after I reboot I get the error that the android keyboard has stopped working (keyboard crashes). It happens over and over. I can't type anything and the home button doesn't work, either.
I wipe the system and cache before doing every install, do a factory reset after, wipe dalvik, let it sit before rebooting. It doesn't matter if I wait 5 minutes or an hour, I get the same error every time. I have tried every rom in this forum, same result, same error.
I end up having to restore back to factory rooted every time.
Is there something that I just keep forgetting to do? Something I'm missing? Any help would be appreciated.
Sent from my SGH-T879 using xda premium
Android Revolution said:
I have a recurring issue trying to install any roms on this device. Every time I perform an install, after I reboot I get the error that the android keyboard has stopped working (keyboard crashes). It happens over and over. I can't type anything and the home button doesn't work, either.
I wipe the system and cache before doing every install, do a factory reset after, wipe dalvik, let it sit before rebooting. It doesn't matter if I wait 5 minutes or an hour, I get the same error every time. I have tried every rom in this forum, same result, same error.
I end up having to restore back to factory rooted every time.
Is there something that I just keep forgetting to do? Something I'm missing? Any help would be appreciated.
Sent from my SGH-T879 using xda premium
Click to expand...
Click to collapse
Are you using TWRP or cwm?
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
I was using cwr originally with this phone and with all previous phones, but switched to twrp since most people say it's better.
Sent from my SGH-T879 using xda premium
Android Revolution said:
I was using cwr originally with this phone and with all previous phones, but switched to twrp since most people say it's better.
Sent from my SGH-T879 using xda premium
Click to expand...
Click to collapse
And it still happens with twrp?
These are the steps I take with twrp.
1. Wipe data
2. Wipe system
3. Wipe cache/dalvik
4. Install rom
5. Install gapps if flashing aosp based rom.
6. Wipe cache/dalvik
7. Fix permissions *optional
8. Reboot then leave alone and don't touch for ten minutes.
9. Reboot again and enjoy.
If that doesn't work then something is wrong with your phone.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
I have no idea if this will help because i've never had this problem, but as long as your phone hasn't frozen, maybe you could try installing a 3rd party keyboard from the Play store (do it from the Play store on your PC since you can't use the keyboard on your phone). Maybe that might fix what's broken, or at least give you the option to use another keyboard.
Another option would be to install Teamviewer QuickSupport from the Play store (again, use your PC). This free app allows you to actually control your Android phone from your computer (Your phone actually pops up in a window and you can control it with mouse clicks), so you might be able to troubleshoot a little bit easier using that, or install apps, etc.
Also, if you are installing Gapps, make sure you are using the right one for your specific ROM. There are separate ones for JB ROMS and ICS ROMS (if I remember correctly). Also, make sure the one you are using is the latest version for that ROM.
I hope one of these suggestions helps. If either one does, click the thanks button.
My phone forced the update on me and I was still rooted. Now I'm stuck in a bootloop. How do I delete the update or stop it from rebooting the phone? If I remember you can just delete the file or something right?
When the phone turns on, quickly go to settings and change the time to like 2 hours ahead. It won't reboot again. Then you can do whatever you need to unroot, flash stock recovery and update
Sent from my XT1056 using xda app-developers app
9kracing said:
My phone forced the update on me and I was still rooted. Now I'm stuck in a bootloop. How do I delete the update or stop it from rebooting the phone? If I remember you can just delete the file or something right?
Click to expand...
Click to collapse
Use titanium backup to freeze Motorola ota
MOTO X SLAPPED
You can go to your setting option and get off your updated option.. i think it's simple... Did it ?
As the title suggests, I uninstalled the Google app last night to try and install the newest version (new version wouldn't install, so i figured I needed to uninstall the previous version). When I tried to reboot the phone after uninstalling the Google app, it went into a boot loop. I have manualy flashed system images twice now and every time it gets stuck on the boot animation. How can uninstalling the Google app possibly cause boot loops?! Anyone have any suggestions? Thanks
comoc85 said:
As the title suggests, I uninstalled the Google app last night to try and install the newest version (new version wouldn't install, so i figured I needed to uninstall the previous version). When I tried to reboot the phone after uninstalling the Google app, it went into a boot loop. I have manualy flashed system images twice now and every time it gets stuck on the boot animation. How can uninstalling the Google app possibly cause boot loops?! Anyone have any suggestions? Thanks
Click to expand...
Click to collapse
i would do a full clean flash.
i dont know why its doing that, maybe google boobytrapped the rom so you cant remove their app without complications.