Hi, Thanks to all who provide support and answer questions on this forum.
I need some help. I'm on a droid Razr MAXX, rooted, SafeStrap 3.11, Android ICS 4.0.4, System Version .211.XT912.
I've successfully flashed a few ROMS, ALL ICS ROMS (Flick, Eclipse,..). However when I tried installing any AOSP,AOKP,CM9+ mods The wireless would constantly say my router was "Not In Range" or would be completely non functional as in not even toggling on. So I've given up troubleshooting it and want to start from scratch. I need to know how to completely remove SafeStrap (properly) and Completely wipe all Data on my phone. Everything. Even the folders from old apps that are no longer installed and contain misc. files that are not being used and just taking up space.
I tried Factory Reset from within SafeStrap, and that still left the misc. folders i was talking about on my phone. If I just do a factory data reset from within the phone itself SETTINGS>Privacy>Factory Data reset, will that do what im wanting. Will it get rid of safestrap, or do i need to remove that and unroot first?
I've read places that suggest flashing an SBF file, and I've heard that thats required for using some of the newer JB roms (have to flash a JB SBF Kernel, am i understanding that right?), but I cant find the most recent version of RSD Lite, havent used it before, and honestly dont want to go that far yet until I can get these roms i've been messing with working first.
Thanks in advance for any help. Sorry for the long post
Try downloading the SafeStrap app and then from there choose "Uninstall Recovery"
go into stock android recovery and do a full wipe.
Related
What do I backup when I sbf? Can I back up everything I need with TiBu pro? When I reboot my phone after sbfing, is it like getting it out of the box, but with a newer version? How do I restore everything? Will it save app data?
Sorry for all the questions, but I need to know.
Edit: Also, if it is like getting it out of the box, what happens to my verizon plan?
Arbybear said:
What do I backup when I sbf? Can I back up everything I need with TiBu pro? When I reboot my phone after sbfing, is it like getting it out of the box, but with a newer version? How do I restore everything? Will it save app data?
Sorry for all the questions, but I need to know.
Edit: Also, if it is like getting it out of the box, what happens to my verizon plan?
Click to expand...
Click to collapse
You can back up your apps and data with TiBu. After sbf your phone will be like new, out of box, and you will need to activate your phone. It does not effect your plan. You can restore your apps and data from TiBu after the sbf.
maggard5 said:
You can back up your apps and data with TiBu. After sbf your phone will be like new, out of box, and you will need to activate your phone. It does not effect your plan. You can restore your apps and data from TiBu after the sbf.
Click to expand...
Click to collapse
Thank you. Is the only bug in 2.3.4 the battery percentage?
Arbybear said:
Thank you. Is the only bug in 2.3.4 the battery percentage?
Click to expand...
Click to collapse
I am using cm7 so not sure what issues you might encounter with stock 2.3.4.
Sent from my MB870 using XDA App
If u aren't on a rom or have any tweaks
just sbf
sbf doesn't wipe ur user data AT ALL it just upgrade ur system
BUT if u have a rom running or scripts or tweaks like that then u may bootloop after the sbf and will need to data wipe from stock recovery to remedy the bootloop
If u r dong sbf just to upgrade u wont lose ur apps data ...
ashclepdia said:
If u aren't on a rom or have any tweaks
just sbf
sbf doesn't wipe ur user data AT ALL it just upgrade ur system
BUT if u have a rom running or scripts or tweaks like that then u may bootloop after the sbf and will need to data wipe from stock recovery to remedy the bootloop
If u r dong sbf just to upgrade u wont lose ur apps data ...
Click to expand...
Click to collapse
so do you HAVE to wipe after sbf? I thought I had read on here that people had successfully sbf's without a wipe? as your post would seem to suggest?
I sbf'd for the first time in forever tonight, but didn't wipe just yet cause I didn't feel like setting everything up from scratch again.
But I still have superuser listed in my app drawer, but I seem to no longer be rooted, and had to reactivate the phone.
If the "crashed" rom is the same as the sbf no wipe needed but it's a crapshoot if "crashed" is custom rom then sbf will need wiping!
skwoodwiva said:
If the "crashed" rom is the same as the sbf no wipe needed but it's a crapshoot if "crashed" is custom rom then sbf will need wiping!
Click to expand...
Click to collapse
not necessarily
im not exactly sure why sometimes you need a wipe, and sometimes you dont.
i havent sbfd enough times to figure that out cuz i can usually just nandroid restore back to where i need to be.
but i have definitly sbfd from a rom like eclipse and NOT needed a data wipe
and i have also sbf'd when just stock rooted with some tweaks and NEEDED data wipe to stop the bootloop.
three west said:
so do you HAVE to wipe after sbf? I thought I had read on here that people had successfully sbf's without a wipe? as your post would seem to suggest?
I sbf'd for the first time in forever tonight, but didn't wipe just yet cause I didn't feel like setting everything up from scratch again.
But I still have superuser listed in my app drawer, but I seem to no longer be rooted, and had to reactivate the phone.
Click to expand...
Click to collapse
if you did a sbf you no longer have root access
i am not sure if the superuser app will be wiped away at this point if you do a data wipe either, superuser is usually a /system/app am i correct?
BUT if it is a user app(found in /data/app) then you can just uninstall the superuser via manage applications
if it is system/app you NEED root access to be able to remove the apk
if you wanna check if you are rooted or not just try to use an app that requires root access, if you are not rooted it wont work.
so yes, you inferred correctly, a data wipe is not NECESSARY after EVERY sbf flash, BUT it IS needed if you get caught up in a bootoop, data wipe from android recovery is the only way to get out of a bootloop resulting from sbf flash.
it is aso recommnded to data wipe after a sbf flash just due to issues that may arise later and u might have to data wipe then to get rid of those issues, you might end up never needing to data wipe, but if you do run into issues, that will be the solution
sorry, im not tryng to ramble here, just trying to be clear as much as i can based on my experience and based on the many results of others and their feedback.(if i have caused confusion i apologize, just ask and i will try to clear it up, i just watched hitchhikers guide to the galaxy, if u have ever read the book or seen the movie you know where my mind is right now LMAO)
well I was just going back to stock for, ya know, reasons
I had been just rooted stock at the time. I really don't want to wipe and set everything up from scratch again.
Root is gone, BSR is not functional, but they both still show in the app drawer.
Pulldown toggles are gone.
I think I'm going to give it a shot like this and see what comes
I think you will WANT to SBF>Factory Reset if you wanna do the "reasons"...
But only bug noted(that I can remember anyway) is the battery jump.
TiBu will not restore your apps or data unless you are rooted. My suggestion... do a Nandroid Backup and then do provided instructions... at least this way you can go back to what you had before hand.
SBF will bring your phone to an Out-of-Box state... Exactly how you got it at Verizon.
Questions Asked:
What do I backup when I sbf?
Whatever you want. Nandroid will be for if you want to go back to what you were using. TiBu is for if you are going to apply:
-SBF to a different Android Version.
-Apply a New Rom.
Can I back up everything I need with TiBu pro?
Depends on what you are doing. TiBu is intended for apps and app data, also keep in mind to watch what you restore because you DO NOT want to restore the Settings and other system apps when you are going to a different android version(if you know the exceptions then you know the exceptions... Dragons lie ahead if you don't know what you are doing... just trust this advice).
This WILL NOT cover user configuration in the internal settings.
When I reboot my phone after sbfing, is it like getting it out of the box, but with a newer version?
Did you upgrade or downgrade? SBF is used to go back if you brick your device or need to be on a specific android version/kernel for applying a ROM. Yes it will be out of box state with a specific android version.(i.e. If you apply 2.2 SBF you go back to 2.2 android out-of-box. If you apply 2.3.3 SBF you go back to 2.3.3 android out-of-box. etc...)
How do I restore everything? Will it save app data?
Did you Nandroid or TiBu?
Nandroid:
Apply SBF to specific android version/kernel version you were previously on(you want to be on the kernel you had with said Nandroid backup). Boot into BSR/CWM then go to restore>Internal/External Memory>Restore>Wait for application of backup>Reboot.
TiBu
Once you are on a satisfied android version/kernel open TiBu and restore whatever apps you want. You get the option to restore App(s) Only, App(s) Data Only, or App(s) and Data.
Also, if it is like getting it out of the box, what happens to my verizon plan?
Nothing!! Your Verizon Plan is saved server side and is paired with your device MEID. After a SBF is applied, you can follow the initial boot and activate your phone or dial *228 at any time to activate your device.
I hope I answered everything for you sir. Good luck with SBFing...If you have ANY bootloops or crashes after SBFing do this please:
Boot into STOCK android recovery:
1. Turn device off or Battery Pull.
2. Hold Volume Down until step 4.
3. Turn on device.
4. You should see the Moto Red Logo with white text "Fastboot" at the top of your screen. Press volume down until white text reads Android Recovery.
5. Press Volume Up to select Android Recovery.
6. You should see a Blue Android with Yellow Exclamation point.
7. Press Volume Up + Volume Down at the same time.
8. Using Volume Keys, highlight "Factory/Data Reset" then press Power Button.
9. Select Yes.
10. Reboot once complete.
Side Note:
lol I'm really bored at work right now.
Hello folks,
new here, but no new to Android, although I am not expert, thus please be patient
I have a 2-yr old Aria, which I rooted as soon as the warranty expired and it also has ClockworkMod Recovery on it, version 2.5.0.1. It is still running the stock 2.1 Eclair ROM, the really old one, with no OTA option.
Few days ago I became a victim of the infamous "download unsuccessful" issue with Market (running on 2.1 my Aria does not have Google Market). It just happened out of the blue, I had not installed any new application or done anything weird as root. After having tried all imaginable fixes, referring to the many Google search hit on the subject, but with no effect, I contacted Google support. Their suggestion: do a FDR....
Now, if I have to wipe my phone and rebuild the system, I'd rather take the plunge and upgrade to Froyo.I am getting a new phone soon, which will have ICS, therefore I am not interested at this time in any alternate ROM, the stock 2.2 from AT&T will do. I downloaded it a while ago but never upgraded.
My questions is: what is the correct procedure to upgrade to stock 2.2 Froyo with no danger of bricking the phone, since I have ClockworkMod on it? Do I just run the upgrade following the instructions on HTC web site because it will wipe CWM anyway or should I use the "apply sdcard:update.zip" or "install zip from sdcard" options in CWM Recovery main menu?
Also, should I decide to just do a FDR and go back to the original 2.1 ROM as Google suggested, the right way of doing it is through the "wipe data/factory reset" option in ClockworkMod Recovery, NOT through the "Factory Data Reset" option under "Settings -> Privacy", correct?
For many of you the answers will be obvious, but as much as I have searched over the internet, I have not found a straight answer, especially to my first question (how to upgrade to stock Froyo if you have ClockworkMod installed)
Thanks in advance for any guidance you may provide.
Batman66 said:
run the upgrade following the instructions on HTC web site because it will wipe CWM anyway
Click to expand...
Click to collapse
This
And factory reset in Android or recovery - doesn't really matter. Might be faster through recovery
WinSuk,
thanks for the speedy reply!! I suppose you mean doing a Factory Data Reset AFTER I run the HTC upgrade to 2.2, right?
And one more question, if I may: I believe I will lose root once I upgrade to stock Froyo, correct? At this time I do not mind, as Froyo should add a couple of missing features in Eclair that made me root in the first place, namely moving apps to SD and clearing the apps Data.
Thanks again! :good:
Batman66 said:
WinSuk,
thanks for the speedy reply!! I suppose you mean doing a Factory Data Reset AFTER I run the HTC upgrade to 2.2, right?
And one more question, if I may: I believe I will lose root once I upgrade to stock Froyo, correct? At this time I do not mind, as Froyo should add a couple of missing features in Eclair that made me root in the first place, namely moving apps to SD and clearing the apps Data.
Thanks again! :good:
Click to expand...
Click to collapse
I meant about your second question..
It will wipe data automatically when updating. And yes, no more root
Oh, I get it now. I misinterpreted the "And" at the beginning of your second sentence. Reading on other forums about people who had upgraded their phones from Ginger Bread to Ice Scream Sandwich, I noticed that many of them had to do a FDR after upgrading to get everything working right. I thought you were referring to something similar, although in this case I see how it wouldn't make much sense, since everything that has to do with Eclair 2.1 will be completely wiped off the phone by the 2.2 install.
Hi all,
I have a Droid incredible 4g (stock, unrooted/unlocked, w/ the recent OTA update). I saw the Bootloader Unlock exploit in the developer's forum so I gave it a go, and it worked fine. Then I installed the Viper 1.0 ROM, but I haven't been able to get it to do anything after successfully booting except run through a loop of errors such as "Unfortunately, the process android.process.acore has stopped working." After I click "OK" on about 10 critical errors, it self-reboots and does the whole thing again.
Unfortunately, I didn't do a backup this time, so I have nothing to restore (first time I haven't done a backup, but also the first time I've ever had any kind of an issue w/ a ROM). I tried using the HTC Android ROM Update Utility 1.0.5.2011 that I found in the dev forum, but that didn't work either. Finally, I installed 2.17.605.2 Verizon Global Sense4.1 Android 4.0.4. It's a lot more stable than Viper was and the phone is basically usable, but I still get lots of critical errors. So this morning I went back to the forum and saw that I needed to downgrade to the old 1.43.605.3 kernel. I tried that and then reinstalled Viper 1.0, but it seemed to have no effect--still stuck in a critical error/reboot loop.
I realize that's the risk of playing with ROMs and I should have done a backup, but anyone have any ideas on how I can get my phone back and running?
Thanks!
Even though it explicitly stated you didn't need to do a backup, I did one anyway, to prevent something like this from happening. Always do a backup.
Did you verify the MD5Sum of ViperLTE?
Did you go to Recovery and Wipe -> Factory Reset and Wipe -> System both twice before trying to install the ROM?
Did you change anything in the ROM before attempting to load it?
There are lots of questions we could ask to ascertain the root of the problem, but these three are among the most important.
Wi-Fi won't work without the old boot.img, and from what I can tell, that's the only thing. It doesn't give critical errors.
I'm thinking since you are new to root you were un-aware the need to wipe before installing a rom.
im thinking that is the issue.
Thanks for the reply!
I didn't check the MD5 last night but I did just now and it matches.
I did a cache wipe the first time but not a system wipe. Then I started getting more desperate and tried reinstalling w/ system wipes and factory resets, but it didn't change anything.
No, I didn't change the ROM. Doing the Bootloader unlock exploit was about the absolute maximum of my technical abilities! The only thing I know I did wrong was that I didn't downgrade to the old boot version the first time (mainly because the wifi thing sounded inconsequential and I didn't want to learn the procedure if I didn't have to).
Anyway, I just tried Ultimate KangBang and it seems to work--no error messages so far. I don't know what I did wrong, but hopefully this keeps working!
IceDragon59 said:
Even though it explicitly stated you didn't need to do a backup, I did one anyway, to prevent something like this from happening. Always do a backup.
Did you verify the MD5Sum of ViperLTE?
Did you go to Recovery and Wipe -> Factory Reset and Wipe -> System both twice before trying to install the ROM?
Did you change anything in the ROM before attempting to load it?
There are lots of questions we could ask to ascertain the root of the problem, but these three are among the most important.
Wi-Fi won't work without the old boot.img, and from what I can tell, that's the only thing. It doesn't give critical errors.
Click to expand...
Click to collapse
andybones said:
I'm thinking since you are new to root you were un-aware the need to wipe before installing a rom.
im thinking that is the issue.
Click to expand...
Click to collapse
Yes, I took a short-cut that didn't quite work out. I didn't want to wipe the system because I wasn't sure if my pictures would be wiped too, but then when everything died I tried wiping everything and reinstalling and it didn't seem to improve anything. I did end up losing my pictures too. Oh well. Maybe it's just a combination of stuff I did to try to get things working (there was some trial and error in unlocking the bootloader but I did get that to work finally, and then more trial and error with the ROMs).
I guess the best thing to do is leave the phone the heck alone as long as it's working, for now. I just don't know why nothing seemed to work--I thought factory reset/fresh ROM would do it.
franklin411 said:
Yes, I took a short-cut that didn't quite work out. I didn't want to wipe the system because I wasn't sure if my pictures would be wiped too, but then when everything died I tried wiping everything and reinstalling and it didn't seem to improve anything. I did end up losing my pictures too. Oh well. Maybe it's just a combination of stuff I did to try to get things working (there was some trial and error in unlocking the bootloader but I did get that to work finally, and then more trial and error with the ROMs).
I guess the best thing to do is leave the phone the heck alone as long as it's working, for now. I just don't know why nothing seemed to work--I thought factory reset/fresh ROM would do it.
Click to expand...
Click to collapse
If UKB ROM works then Viper ROM will too, installing the boot.img is very simple it's one command
I can help you with that if you'd like
in recovery before installing ROM, do a wipe of, (I go in this order, but it doesn't matter.)
1) Factory Reset
2) System
3) Cache
4) Dalvik Cache
then install the ROM
just DO NOT do External storage (unless of coarse u WANT to wipe your SD-Card.)
as long as you don't wipe External Storage you won't lose anything that's on your SD-Card.
in the future it is always good practice to backup(nandroid) your current ROM. I have been burned too many times, always do a nandroid before you do anything in recovery.
your photos are normally saved to the SD, flashing ROMs or wiping the system will not delete them
andybones said:
If UKB ROM works then Viper ROM will too, installing the boot.img is very simple it's one command
I can help you with that if you'd like
in recovery before installing ROM, do a wipe of, (I go in this order, but it doesn't matter.)
1) Factory Reset
2) System
3) Cache
4) Dalvik Cache
then install the ROM
just DO NOT do External storage (unless of coarse u WANT to wipe your SD-Card.)
as long as you don't wipe External Storage you won't lose anything that's on your SD-Card.
Click to expand...
Click to collapse
It worked this time! Maybe the difference was that the boot.img file I downloaded was called "boot_signed.img" or something. I had no idea what it was supposed to look like, so I installed it that way and it didn't work. Then I tried renaming it to "boot.img" this morning and installing viper, but that didn't work. And then I restarted and installed UKB, and it worked. Just now I wiped and tried again with Viper and it's working fine. Maybe I did something this morning that caused it not to take properly when I tried with Viper, and then I reset and it worked.
Thanks for the help!
franklin411 said:
It worked this time! Maybe the difference was that the boot.img file I downloaded was called "boot_signed.img" or something. I had no idea what it was supposed to look like, so I installed it that way and it didn't work. Then I tried renaming it to "boot.img" this morning and installing viper, but that didn't work. And then I restarted and installed UKB, and it worked. Just now I wiped and tried again with Viper and it's working fine. Maybe I did something this morning that caused it not to take properly when I tried with Viper, and then I reset and it worked.
Thanks for the help!
Click to expand...
Click to collapse
na the name has nothing to do with it. it can be named whatever.
im guessing the wipe worked.
franklin411 said:
Hi all,
I have a Droid incredible 4g (stock, unrooted/unlocked, w/ the recent OTA update). I saw the Bootloader Unlock exploit in the developer's forum so I gave it a go, and it worked fine. Then I installed the Viper 1.0 ROM, but I haven't been able to get it to do anything after successfully booting except run through a loop of errors such as "Unfortunately, the process android.process.acore has stopped working." After I click "OK" on about 10 critical errors, it self-reboots and does the whole thing again.
Unfortunately, I didn't do a backup this time, so I have nothing to restore (first time I haven't done a backup, but also the first time I've ever had any kind of an issue w/ a ROM). I tried using the HTC Android ROM Update Utility 1.0.5.2011 that I found in the dev forum, but that didn't work either. Finally, I installed 2.17.605.2 Verizon Global Sense4.1 Android 4.0.4. It's a lot more stable than Viper was and the phone is basically usable, but I still get lots of critical errors. So this morning I went back to the forum and saw that I needed to downgrade to the old 1.43.605.3 kernel. I tried that and then reinstalled Viper 1.0, but it seemed to have no effect--still stuck in a critical error/reboot loop.
I realize that's the risk of playing with ROMs and I should have done a backup, but anyone have any ideas on how I can get my phone back and running?
Thanks!
Click to expand...
Click to collapse
weird, i was having the same problem with the same processes stopped working. i wiped cache dalvik and system but not factory reset. once i factory reset, it worked fine. i figured a system wipe would have been enough....
I have a Droid Razr Maxx. I recently attempted to install 4.2.2 using Safestrap and it failed. It would just go in cycles of going to safestrap and restarting. I am now trying to restore my phone so that i can use it again. I cleared the cache/dalivk/and wiped, thinking that it would remove the recently installed file. When I go to reboot in safestrap it says there is "No OS installed". I think I bit off more than I can chew and really don't understand the advanced issues of installing roms from safestrap apparently. I definitely will not be trying this again. Would someone please be able to help me. Should there be a file I could use on the system to re install the stock rom? can I even transfer a file from the computer to my sd card, if all I can do is turn it on to safe strap..Desperate as I work in a hospital and this is necessary for communicating about patient care. Obviously I know I shouldn't have done this. Thanks you so much for any help.
Alright, here's the problem,when the official jb 4.1.2 update came out a few days ago I decided to re-root and try a custom rom (tried on ICS but never was successful, also never bricked). I rooted fine and updated to safestrap 3.11, found a cm 10.1 rom online, went through all the steps but never wiped the stock system so every time I tried to boot it would try to dual boot and not work. I finally realized that i was wiping the rom system and not the stock which was why it would never work. So, wiped both caches, factory reset, and system wiped as per instructed and after that I installed the cm 10.1 in rom slot 1. Rom booted great worked fairly well but was a bit buggy for the first day, installed gapps no problem. After messing with it for a day I decided to switch back to stock system because i had all my contacts on backup assistant which wasnt available on the cm rom. when i tried to restore stock, I realize that somehow my backup got erased or something because all it is is an empty folder and took no time at all to restore, also wont boot. Any suggestions?
Phone specs (idk if it matters): XT912 CDMA Droid RAZR 4.1.2 (or was anyway)
PS. sorry for the super long post, i was kinda venting
http://www.droidrzr.com/index.php/topic/12777-droid-razr-utility-xt912-jellybean-windows-mac-linux-all-in-one/page__pid__227369#entry227369You can try to use this utility to take you back to stock JB:
Wouldn't that just root me and not take me back to OTA JB? I used the same program to re-root after the update from ICS to JB a few days ago.
Matt's Utility also has a "flash back to stock" option.
Alright, I got my phone back on track without needing a factory cable which was the route everything was going until I found a post about a work around by outfieldslayer on droid forums, anyone else who has this problem, just search "HELP battery died during flash!". Thanks to shobon and Gus194 for pointing me in the right direction and special thanks to mattlgroff for his work on the Razr utility!