For some reason my phone boots straight into CWM and i have to reboot from there to have a normal boot. Not a big problem but weird and sometimes it slips my mind. I'm running the spearmint gummy ROM, my favorite ICS so far, and this started only after flashing this. Before that I was on stock 902 rooted for a month or so, just felt like being on stock for a while until ICS kinks were getting worked out i was having issues with most GB ROMs. Anyone know what's going on here?
Sent from my Transformer TF101 using Tapatalk 2
Have you tried reimaging the phone?
Sent from my DROID BIONIC using Tapatalk
The ICS ROMS were built for safestrap not bootstrap (CWM).
It does that because it was flashed using CWM.
Flash it using safestrap and you won't have that reboot issue.
This behavior is intentional, and meant to prevent you from bricking your phone.
Gotcha. Had safestrap prior to returning to stock but was experiencing issues this time around and I'm pretty sure I fixed my problem so I guess I'll install safestrap now, I still have it in titanium. Just won't restore data
Sent from my XT875 using Tapatalk 2
Related
I got rom manager and im trying to do a nan droid back up and when i select back up current rom my phone just restarts? Anyone got any ideas?
Sent from my DROID BIONIC using Tapatalk
don't think no our phone supports from manager technically its supposed to take you to cwm and you navqgate to backup/restore so I think you have to do that in safe strap or what ever its called
Sent from my DROID BIONIC using XDA App
Oh, i wish i can back up my current state of my phone. Is there a way i can get more onfo on this?
Sent from my DROID BIONIC using Tapatalk
you are rooted with boot strap installed correct??
Sent from my DROID BIONIC using XDA App
rooted no bootstrap
You have to install either Bootstrap or Safestrap to make nandroid backups with this phone.
which is better safestrap or bootstrap is there a difference?
Bootstrap is simpler but has less features. Personally it's the one I use, as it seems to do the job fine when running stock as I do. If you plan to install a lot of different ROMs, such as the ICS alpha, then you might be better off using Safestrap. It basically creates two system images, one stock and the other a custom ROM. The idea is that if you go into a bootloop with one system, you can switch to the other one instead of being stuck. There are some drawbacks -- I have heard it uses some RAM and slightly degrades performance. Also, Webtop works on one system but not the other.
I have always used bootstrap and never had any issues.
---------- Post added at 05:27 AM ---------- Previous post was at 05:23 AM ----------
unbesorgt said:
Bootstrap is simpler but has less features. Personally it's the one I use, as it seems to do the job fine when running stock as I do. If you plan to install a lot of different ROMs, such as the ICS alpha, then you might be better off using Safestrap. It basically creates two system images, one stock and the other a custom ROM. The idea is that if you go into a bootloop with one system, you can switch to the other one instead of being stuck. There are some drawbacks -- I have heard it uses some RAM and slightly degrades performance. Also, Webtop works on one system but not the other.
Click to expand...
Click to collapse
I have never used safestrap I am sure it works great. But since I am new to bionic if you bootloop can't you pull battery boot up in android recovery and wipe data and cache? Works everytime on droidx2.
If you want to play with other roms while having a main rom that you use daily, go with safe strap. If your going to stick to one rom, either one will work. You can flash and backup with each one.
Sent from my DROID BIONIC using XDA App
People have been asking in the dev forum alot about how to have two roms on the same device. So i thought I would make a how to.
You do this at your own risk.
Things Needed:
external SD
Get CWM for droid3
SafeStrap for droid3
stable rom to use as nonsafe [put on external SD]
rom to use as safe [put on external SD]
TiBu
1. (make sure you are in nonsafe, if you don't know what this means then dont worry). Do a backup of everything you will want to keep with TiBu.
2. Put the backup on external SD or on dropbox.
3. Uninstall any existing recoveries.
4. Reboot device.
5. Install cwm.
6. Reboot into CWM Recovery and install stable rom.
7. Reboot device.
8. Uninstall CWM and Then install safestrap.
9. Reboot into safestrap recovery.
10. Use volume rockers to go to safe boot menu.
11. Toggle safesystem.
12. select install a zip
13. choose safe rom
14. DONE "]
The nonsafe system will now contain your stable rom. and the safe system will contain your 'experimental' or second rom. I recommend not putting any new or buggy roms as your nonsafe. And this is already considered a dangerous thing to do. And give a huge thanks to hashcode for providing us with safestrap and koush for cwm :]
I currently use MavRom as a nonsafe. Its extremely stable and has not caused any issues at all.
Also if you want to transfer the safe to the nonsafe, use tibu to entirely back up the rom, system and user apps, you can then restore it after flashing it to nonsafe. Make a new backup folder to put it in so you don't mix it up with other backups from different roms
Sent from my XT860 using xda premium
I can't seem to get this to work with Cm7 as Safe rom and Cm9 as my experimental. I got Steel Droid to boot up and stock but I'm starting to think any rom that isn't blur based (which is really only cyanogen) isn't able to be dual booted. I just get a black screen after the splash screen I've been trying for a week now. If anybody is willing to give it a shot just to see if its me then please let me know of your findings but Mavrom Liberty SD all of those I can boot its cm7.1 or Cm9 that won't...
Sent from my DROID3 using Tapatalk
Thwe blur based thing may be right. Im unsure, but cm7 to me personally shuld not be used as stable
Sent from my XT862 using Tapatalk
can somebody unite thiese 2 topics?
http://forum.xda-developers.com/showthread.php?t=1436380
Dri94 said:
Thwe blur based thing may be right. Im unsure, but cm7 to me personally shuld not be used as stable
Sent from my XT862 using Tapatalk
Click to expand...
Click to collapse
Damnit man I would rather not have to run cm7 as my stable rom seeing how I have no front facing camera support but the other features that the blur based roms lack just make it impossible to use as a daily driver. I need control over which buttons are in the notification widget and a few of the other features cm provides and none of the blurless roms give me that unfortunately... I'm determined to get this to work if its the last thing I do lol
Sent from my DROID3 using Tapatalk
Whats not working about it ?
Sent from my XT862 using Tapatalk
Dri94 said:
Whats not working about it ?
Sent from my XT862 using Tapatalk
Click to expand...
Click to collapse
I can't get cm7 to boot up past the safestrap splash screen.... I start out with bootstrap boot cm7 up and then remove bootstrap and install safestrap thus making cm7 my non safe or main rom but upon rebooting the phone I just get the black screen after the splash screen... I can get into safestrap and switch to safe mode and run whatever rom I last had there or flash any nandroids I had in non safe mode but whatever rom I had on prior to installing safestrap (cm7 or cm9) they won't actually reboot. I thought cm9 would work which would really be a hastle keeping that as my non safe rom and cm7 as my main one on the safe side thus leaving me to redo the entire process everytime a new cm9 is released but cm9 wouldn't boot up past the initializing apps screen that first pops up... It counts up to all the apps I have then just stays stuck on starting applications or whatever it says, cm7 doesn't even boot up beyond the splash screen...
Edit: And I know that I'm doing it right because I have got Steel Droid to dual boot before I just can't understand y blurfree roms can't boot in non safe mode
Sent from my DROID3 using Tapatalk
ill test it when i get home.
Sent from my XT862 using Tapatalk
Dri94 said:
ill test it when i get home.
Sent from my XT862 using Tapatalk
Click to expand...
Click to collapse
Appreciate it *fingers crossed*
Sent from my DROID3 using Tapatalk
Im sorry. I got behind on some work, when i catch up ill get back to you.
Sent from my XT862 using Tapatalk
Dri94 said:
Im sorry. I got behind on some work, when i catch up ill get back to you.
Sent from my XT862 using Tapatalk
Click to expand...
Click to collapse
No pressure man I do appreciate the response tho lol
Sent from my DROID3 using Tapatalk
Ill do it tonight when i install the new ics :]
Sent from my XT862 using Tapatalk
Dri94 said:
Ill do it tonight when i install the new ics :]
Sent from my XT862 using Tapatalk
Click to expand...
Click to collapse
I was gonna do the same lol hilarious
Sent from my DROID3 using Tapatalk
Lol cool :] lets see if we can both get it
Sent from my XT862 using Tapatalk
Ok im gonna give this another shot tonight..... haven't had the time or patience especially since I think its gonna fail again but ill update with my progress.... gonna try cm7 as the non safe and aokp as the safe one...
Sent from my DROID3 using Tapatalk
Ok, time to feel like a total noob.
So, my idea was to use safestrap to install aokp on the safe partition and leave my stock (+root) rom on the unsafe one.
I had bootstrap installed, just to back up my stuff and whatnot, so, I uninstalled it, installed safestrap, put all the stuff needed for AOKP ( rom, gsm patch and gapps ) and rebooted the phone. I enabled the safe system, and flashed rom, patch and gapps. then I rebooted, and I got into a loop where I would see the motorola logo ( the still one, which says "dual core technology" or something like that), then I got the safestrap splashscreen and if I pressed search, or left the phone idle so it would boot on it's own, it would get me to the motorola logo again, and repeat the loop.
I had to go back to the unsafe system and luckily it's all still there, but, since that point I tried every combination that I could think off, with wipes and I've flashed even just the rom, between wipes, and still, nothing.
I'm thinking that safestrap is not being able to write on the partition, or something like that, but I don't know how to solve it.
Any Ideas?
EDIT: I checked with a root explorer on /preinstall ( which I understand is the /system folder for the safe system ) and all the data seems to be there, but it's just not booting. Which makes me even more confused
Hey there XDA buddies,
Anyone tried the Google Now hack to load onto our Droid4 devices?
I'm definitely curious about Google Now and was wondering about people's experience with it.
The instructions are elsewhere here at XDA and I'll try and add a link on my lunch break to it.
Any feedback is appreciated.
Thanks
Sent from my DROID4 using Tapatalk
I have done it the apk way and the zip way in safeboot. Both seem to work just fine.
Sent from my DROID4 using Tapatalk 2
Eclipse 1.2 for the droid 4 has it pre-loaded, i use it on a daily basis with voice and all
I just loaded the APK and it works, kind of anyway... a little buggy I've noticed but decent enough so far.
Sent from my DROID4 using Tapatalk
Do you guys have a link to download? I'm thinking about trying it.
Thanks,
From what I understand of the Google Now app, you need to be on a custom ROM to use it. It won't work on stock (I tried to install via zip through stock and safetrap recovery on stock ROM and with apk). It sees the stock ROM as an uninstallable system. You must be on either aosp/aokp/eclipse or the like to install this.
If I am wrong and someone has it running on stock them I apologize, but this is what I found and read through the threads as well about it.
I tried a few versions right after i updated to ics and follows the renaming instructions and all...it didn't work..i am stock ics rooted
Sent from my DROID4 using Tapatalk 2
I flashed the deoxed stock rom last night into the safe system without wiping data. Rebooted perfect and then went back to recovery and flashed the google now zip and it works like a charm on stock in the safe mode.
Sent from my DROID4 using Tapatalk 2
I tried manually adding the ZIP contents to the /system (since the new Safestrap restricts flashing ZIPs onto the non-safe stock side.)
I'm flashing deodexed version to my safe side (and I'm not going to be wiping, like the poster above) right now. I'll let you know how it goes.
-Nolam
EDIT:
Flashed it on the safe-side, didn't wipe anything (The deodexed .zip I found will wipe caches for you), and it booted up as if nothing had changed. Then, went back and flashed M7 Google Now. Works great! It's sometimes slow and I do definitely notice a battery drain, but hopefully that can be sorted out.
I downloaded the official ICS OTA the other day but when I try to run the install it starts but then flashes a yellow exclamation point in a triangle and then just reboots like normal. Any clues?
Droid Bionic (rooted)
Wifi Hotspot hack
5.9.905.XT875
2.3.4
CDMA_N_04.07.02R LTEDC_U_07.1F.00
BUILD 5.5.1_84_DBN-74
Any suggestions?
thanks
If you removed any pre-installed apps, then that's your problem. You'll probably need to reflash the official 905 again then reapply the update.
Sent from my XT875 using xda premium
dshel61 said:
I downloaded the official ICS OTA the other day but when I try to run the install it starts but then flashes a yellow exclamation point in a triangle and then just reboots like normal. Any clues?
Droid Bionic (rooted)
Wifi Hotspot hack
5.9.905.XT875
2.3.4
CDMA_N_04.07.02R LTEDC_U_07.1F.00
BUILD 5.5.1_84_DBN-74
Any suggestions?
thanks
Click to expand...
Click to collapse
You need to unroot your bionic. If it is not 100% stock. The OTA will not install.
From my EVOLVED bionic
Obsidian_soul said:
You need to unroot your bionic. If it is not 100% stock. The OTA will not install.
From my EVOLVED bionic
Click to expand...
Click to collapse
and if you have safestrap, remove that, too. And recovery
I could not unroot my phone to succesfully install the update either. Try House of Bionic. It worked for me with a caveat. In the final step, my phone would not complete the install in reboot recovery and would not boot. I had the ota update file on my sd card from a manual install attempt. In reboot recovery mode I was able to install the ota update from the sd card and everything seems to be fine. Rerooted with motofail ics. I should mention that I did not do 905 fxz to stock rom as I was trying to keep my data.
Sent from my Transformer Prime TF201 using xda premium
Things that will make the OTA fail when installing
1. Bootstrap or safestrap is installed
2. Have some bloatware froze or uninstalled
3. Have a mod installed
4. Your still rooted. OTA Rootkeeper will allow you to quickly and easily unroot and reroot. It can be found on Google Play.
These seem to be the most common reasons people have trouble installing an update. I'm sure there are other reasons also, but these seem to be the most common problems.
Sent from my DROID BIONIC using Tapatalk 2
Ok soooo ive uninstalled safestrap and back on stock recovery and stock ics rooted. What else do i need to do to recieve ota when its pushed out?
Sent from my DROID4 using xda app-developers app
rruleford said:
Ok soooo ive uninstalled safestrap and back on stock recovery and stock ics rooted. What else do i need to do to recieve ota when its pushed out?
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
If it's like the last OTA to ICS, you're probably going to have to flash the ICS fastboot files before the new OTA will take. The problem before was safestrap changed something, somewhere (logwrapper maybe?), that did not get changed back after uninstalling the safestrap recovery and app. MAYBE this has been changed/fixed in the new versions of safestrap? Pretty sure we were on version 2.x at the time. You can always try without fastbooting and see what happens. Won't hurt anything. If you do need to fastboot, use jsnweitzel's utility. It has an option to fastboot without wiping data. That's what I'm planning on doing. It should still fix whatever safestrap changed.
Sent from my Droid 4 - LiquidSmooth
kwyrt said:
If it's like the last OTA to ICS, you're probably going to have to flash the ICS fastboot files before the new OTA will take. The problem before was safestrap changed something, somewhere (logwrapper maybe?), that did not get changed back after uninstalling the safestrap recovery and app. MAYBE this has been changed/fixed in the new versions of safestrap? Pretty sure we were on version 2.x at the time. You can always try without fastbooting and see what happens. Won't hurt anything. If you do need to fastboot, use jsnweitzel's utility. It has an option to fastboot without wiping data. That's what I'm planning on doing. It should still fix whatever safestrap changed.
Sent from my Droid 4 - LiquidSmooth
Click to expand...
Click to collapse
In doing that it froze on step 3 of 17 mbmloader. Over night. When disconnected and tried again the battery was to dead. Plugged into wall charger now. Should i try again when its fully charged??
Sent from my DROID4 using xda app-developers app
rruleford said:
In doing that it froze on step 3 of 17 mbmloader. Over night. When disconnected and tried again the battery was to dead. Plugged into wall charger now. Should i try again when its fully charged??
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
Yes. Never try to flash a fastboot or sbf file without making sure you have PLENTY of charge. Same goes for backing up and ROM flashing. You never want your phone to die in the middle of a flash.
Sent from my Droid 4 - LiquidSmooth
I think the most important thing to do is grab the update file and post it on Mediafire or similar so that the rest of us can have it