I have safestrap installed on my rooted droid Razr and to make long story short I was stupid and factory reset my unsafe or stock ROM without knowing I was unable to reinstall a zip file to the unsafe system. Now all I have is my safe customer ROM. I heard the only way to install a ROM on your unsafe system is to uninstall safestrap and use bootstrap, but if I do that, I won't be able to boot my phone up at all because all I have is my safe system running, right? So, my question is: how do I get a stock ROM running on my unsafe again without making my phone unusable? I have a zip file for the stock ROM already, I just need to know how to install it. Thank you in advance!
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root Rooted Razr with safestrap problem!
- Thread starter tkd_aj
- Start date
-
- Tags
- motorola droid razr
Okay, so I actually figured out how to get the stock ROM back on myself. I just booted up in unsafe mode and used the hard buttons to perform a hard factory reset, which worked, but now I am getting the force close for com.android.phone which is why I originally cleared my unsafe system... Does anyone know how to fix something like that? I happened because I uninstalled some root files. I actually uninstalled the default dialer because I use godialer/gocontacts, and I think that is what is causing the force close. I will push "force close" on the message and it will go away for about half a second and then come back instantly. I can still do things on the phone if I push wherever I have to in between the time I push force close and when the message comes back up, but since i factory reset my phone it comes up to the little android guy when I turn on the phone. Everytime I click on him it says "Please wait. This may take a few minutes." and it never goes away and just gets stuck there. If i can get passed that screen and into my phone I should be able to remove safestrap and install bootstrap and then install the stock ROM again and I think that would fix it.
Podivin
Android Expert
I had a similar problem on mine about a week ago, I messed up doing changes and put myself into the same kind of force close loop you're in. I don't recall the exact program that was failing, but I couldn't get past it.
I finally decided to completely reset the phone by to stock by using this method. It was fairly painless to do. Because the file in this thread takes you all the way back to the original operating system on the phone, you will actually receive 3 different OTA update notifications that will eventually have you the current Razr OS. (you'll receive one notification on each reboot of the phone, not all at the same time).
You could probably also use [url="http://www.droidrzr.com/index.php/topic/749-droid-razr-utility-windows]the Droid Razr Utility[/url]. I expect this works fine, but can't say for sure since I used the other method (this one would be slightly easier). I believe this one takes the phone to the most current OS, so no OTA updates using this method.
Both of these methods require that the phone is in fastboot mode. In case you don't know how to get there, the steps are:
1. Power off the device.
2. Power the device back on by pressing and holding the Volume Up and Volume Down and power buttons all at the same time until a menu appears. Volumne up/down to 'fastboot' option then press the power button to select.
As stated in at least one of the threads above, make sure your phone has a good charge on it, this will take some time and you don't want the battery to die in the middle.
I've not yet rerooted my phone, I'm thinking that since I'm back on the Moto upgrade path I might just wait for them to push ICS to us.
Unless of course some Dev comes out with a ROM that I just HAVE to try.
I finally decided to completely reset the phone by to stock by using this method. It was fairly painless to do. Because the file in this thread takes you all the way back to the original operating system on the phone, you will actually receive 3 different OTA update notifications that will eventually have you the current Razr OS. (you'll receive one notification on each reboot of the phone, not all at the same time).
You could probably also use [url="http://www.droidrzr.com/index.php/topic/749-droid-razr-utility-windows]the Droid Razr Utility[/url]. I expect this works fine, but can't say for sure since I used the other method (this one would be slightly easier). I believe this one takes the phone to the most current OS, so no OTA updates using this method.
Both of these methods require that the phone is in fastboot mode. In case you don't know how to get there, the steps are:
1. Power off the device.
2. Power the device back on by pressing and holding the Volume Up and Volume Down and power buttons all at the same time until a menu appears. Volumne up/down to 'fastboot' option then press the power button to select.
As stated in at least one of the threads above, make sure your phone has a good charge on it, this will take some time and you don't want the battery to die in the middle.
I've not yet rerooted my phone, I'm thinking that since I'm back on the Moto upgrade path I might just wait for them to push ICS to us.
Unless of course some Dev comes out with a ROM that I just HAVE to try.
Yea there just isn't anything out there ROM-wise that has enticed me to go through the hassle of putting a new ROM on yet. I've seen the ICS builds but none of them are whole yet. They can't do the camera or video or whatever so none of them is 'daily driver' ready yet and who knows if they ever will be. Still waiting for the "official" ICS. At this rate I'll have my new NON-Moto, opened bootloader phone by then....in 2014....
Kelmar
Done by choice
Yea there just isn't anything out there ROM-wise that has enticed me to go through the hassle of putting a new ROM on yet. I've seen the ICS builds but none of them are whole yet. They can't do the camera or video or whatever so none of them is 'daily driver' ready yet and who knows if they ever will be. Still waiting for the "official" ICS. At this rate I'll have my new NON-Moto, opened bootloader phone by then....in 2014....
Last I checked the Dev built ICS had working camera
Podivin
Android Expert
Last I checked the Dev built ICS had working camera
Yep, both front and back cameras are working now.
For ME, the thing that keeps them from being a daily driver is the way bluetooth works. If BT is on but not connected then your voice is 'muted' on a call.
I leave BT on all the time, so that when I get in my car it automatically connects. I'll either forget to turn it on, and then have to fumble for my phone if someone calls. Or I do remember to turn it on, but then forget to turn it off when I get out of the car - thus causing the mute problem on the next call.
Once this problem gets worked out, I'll probably be back to one of the ICS roms (unless of course Moto has pushed something out to us by then).