Back to stock via RSD or something? - Motorola Droid 4

So I got a Droid 4 and seem to be having problems with Safestrap enabling the safe side, is there a way I can RSD back to complete stock so I can go back and do everything myself? I know when I had a Razr I had the same issue but when I RSD backed to stock I was able to root and go back to everything myself and didn't have any problems after that.
I've looked and couldn't find anything to do it...anyone?
**I had it disabled running the stock rom, installed Safestrap went into recovery and was going to switch to the safe side and it gave me a error. So I went to reboot my phone and now everything is wiped and I lost everything

collins521 said:
So I got a Droid 4 and seem to be having problems with Safestrap enabling the safe side, is there a way I can RSD back to complete stock so I can go back and do everything myself? I know when I had a Razr I had the same issue but when I RSD backed to stock I was able to root and go back to everything myself and didn't have any problems after that.
I've looked and couldn't find anything to do it...anyone?
**I had it disabled running the stock rom, installed Safestrap went into recovery and was going to switch to the safe side and it gave me a error. So I went to reboot my phone and now everything is wiped and I lost everything
Click to expand...
Click to collapse
You are not the first one to have this problem. I had this happen to me a few weeks ago and have seen a few others posting of similar issues since. Not sure what is happening that is causing this. Did you make a backup of you non-safe system? If you did you can try restoring it although that did not work for me. Kept getting stuck restoring system.orig. Reboot just brings you back to a completely wiped stock ROM. Really strange. What I did to fix safestrap was uninstall safestrap recovery, delete the safestrap folder on /sdcard, then re-install safestrap recovery. I think somehow something is getting corrupted when switching between the safe and non-safe system.
I haven't seen a good guide on XDA for using the fastboot files to restore your phone to stock but here is a good guide from DroidForums courtesy of SGMD1.
http://www.droidforums.net/forum/dr...otorola-droid-4-xt894-stock-windows-only.html
I would also highly recommend using Titanium Backup or something similar to backup all you apps and data. That way, if something like this happens again, you can restore all you stuff.

Thanks that's what I was looking for, as far as having a back up...no I don't have one since it came with Safestrap and running eclipse I don't have a backup of the stock that's why I was wanting to start from scratch and get my ducks in a row with everything

There's a Droid 4 SBF out there. I've been able to get it to work with RSD Lite 5.7

Related

[Q] Does ROM Manager back up the ENTIRE phone?

Silly noob-like question, but I wanted to make sure before I continued messing with my phone.
Does ROM Manager back up EVERYTHING on the phone? For example, I backup my rom. Move the backup file onto my pc. Then I screw around with roms, lag fixes, etc. and totally screw it up. If I "restore" the backup made by ROM Manager, will all my apps, settings, desktop, data files, etc be exactly as they were before I started screwing around?
Or, would I need to use Odin to load the same ROM as that which was backed up and then run Rom Manager Restore?
Thanks!
Yes it does
Sent from my SAMSUNG-SGH-I897 using XDA App
Here's another question regarding this thread:
I have the lagfix mod which uses the internal sdcard. When I create a backup will it and restore exactly how it was including the lagfix partition? If yes, is it the same procedures or do I have to do it a different way with the extra partition?
Thanks in advance.
Deca4 said:
Here's another question regarding this thread:
I have the lagfix mod which uses the internal sdcard. When I create a backup will it and restore exactly how it was including the lagfix partition? If yes, is it the same procedures or do I have to do it a different way with the extra partition?
Thanks in advance.
Click to expand...
Click to collapse
Actually I am trying to figure out the same thing. I made a backup before I started messing around with lag fixes, different roms and so forth. Then the other day I tried to restore a rom it didn't work. Eventually I soft bricked the phone and had to make the USB Jig to get it working again. Needless to say I am very intrigued with what exactly Rom Manager does backup and its limitations but I can't seem to find it anywhere. I am thinking the reason my backup was screwed up was because of a lag fix, only problem is I can't remember what lag fix I had on it when I did the initial recovery.
Something from my experience to add here:
Scenario 1:
-----------
I backed up the original 2.1 JH7 on my phone.
Installed 2.2 custom ROM, and played around with it.
Backed up 2.2 ROM.
Messed up with my 2.2 custom ROM.
Went to ROM manager recovery, and recovered the backed up 2.1 JH7, and ended up messing up. My phone didn't even boot up.
Then I went back to recovery, and tried restoring the backed up version of 2.2.
Phone booted up into 2.2, but, started giving a lot of FCs.
Scenario 2:
-----------
Installed 2.2 custom ROM 1.
Backed it up.
Messed it.
Restored it - worked fine.
Installed 2.2 custom ROM 2.
Backed it up.
Restored the 2.2 custom ROM 1.
Everything working fine.
Looks like as long as the core OS is of the same version, it seems to work.
Maybe there is something in the boot sequence that's probably not being restored (???)
---------------
Edit: I do not have CWM app installed. I use the CWM update.zip recovery manager since its the least intrusive way.
diablo009 said:
Something from my experience to add here:
Scenario 1:
-----------
I backed up the original 2.1 JH7 on my phone.
Installed 2.2 custom ROM, and played around with it.
Backed up 2.2 ROM.
Messed up with my 2.2 custom ROM.
Went to ROM manager recovery, and recovered the backed up 2.1 JH7, and ended up messing up. My phone didn't even boot up.
Then I went back to recovery, and tried restoring the backed up version of 2.2.
Phone booted up into 2.2, but, started giving a lot of FCs.
Scenario 2:
-----------
Installed 2.2 custom ROM 1.
Backed it up.
Messed it.
Restored it - worked fine.
Installed 2.2 custom ROM 2.
Backed it up.
Restored the 2.2 custom ROM 1.
Everything working fine.
Looks like as long as the core OS is of the same version, it seems to work.
Maybe there is something in the boot sequence that's probably not being restored (???)
---------------
Edit: I do not have CWM app installed. I use the CWM update.zip recovery manager since its the least intrusive way.
Click to expand...
Click to collapse
Interesting, it would makes sense in what you are saying. My error that I go was when I went from my original JH7 backup, installed a rom based on JH6 and then tried to install my original backup. I might have to try JH6 roms and see if I can restore to them easily or not. I will have to wait for Micro USB cables to come in as I don't have a spare since I used my only cable to make the JIG.
The kernel and modem aren't backed up, so if your backups use different ones and you try to restore them you'll have issues.
I herd a rumor that rom manager doesn't work with froyo on the captivate. But I could be totally wrong.
Sent from my SAMSUNG-SGH-I897 using XDA App
peachpuff said:
The kernel and modem aren't backed up, so if your backups use different ones and you try to restore them you'll have issues.
Click to expand...
Click to collapse
This is what I have read about it as well
Voodoo
There is also a different version of CWM Recovery (what Rom Manager uses to back things up) for the voodoo lag fix.
tnerb123 said:
I herd a rumor that rom manager doesn't work with froyo on the captivate. But I could be totally wrong.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
It works. I backed up and restored a few variants of Froyo ROMs.
peachpuff said:
The kernel and modem aren't backed up, so if your backups use different ones and you try to restore them you'll have issues.
Click to expand...
Click to collapse
How do I backup these? Is there any way?
If Ron Manager does backup the kernel and modem why would so many people have problems restoring back to different Roms? This is why I am so puzzled with this software.
Sent from my SAMSUNG-SGH-I897 using XDA App
Rom Manager can backup EFS folder ??
i lost my imei and the only backup that i have its from Ron Manager
Absolutely it does there!
Maybe I'm old fashioned, but best bet is backup from recovery. Saves everything down to browser login data. Can't go wrong with a full backup! I make one every time I flash just about anything.
Sent from my SGH-I897 using xda app-developers app
Rom Manager vs CWM Recovery
yes Rom Manager can do backup of phone..but why not just do
a Nandroid Backup from CWM Recovery..
never had problem with Nandroid Backup from CWM Recovery :victory:
dobi3 said:
yes Rom Manager can do backup of phone..but why not just do
a Nandroid Backup from CWM Recovery..
never had problem with Nandroid Backup from CWM Recovery :victory:
Click to expand...
Click to collapse
Agreed!
Sent from my SGH-I897 using xda app-developers app

[Q] CWM Recovery Restore Problem

I have an ATT Captivate running the stock ATT Froyo upgrade. The phone has been rooted and SU and Busybox installed using Titanium Backup. The modified recovery file has been installed to allow 3e recovery to load unsigned files. CWM Rocovery 2.5.1.2 is installed and seems to be working.
I have several games and apps installed but nothing that would require root access except ROM Manager, Ti Backup and File Expert. The phone is running Launcher Pro. It is pretty much stock except for the changes listed above.
I performed two backups of the phone about a week apart and copied them to my computer and left them on the internal SD card as well. I made a couple of changes to the icons on my home screen so I could verify if a restore ran succesfully.
I ran the restore from the most recent backup. I expected the restore to fail right away, brick my phone or run successfully. The restore ran, indicating that files where being restored and at some point the phone rebooted.
When it came back up TwLauncher was running with the Blue Sea wallpaper as the background which I believe is the default. Most of my apps weren't on the home screens or in the app drawer. These included both the standard ATT and 3rd party apps.
I tried using my first backup with the same results. I was able to do a factory reset on the phone to get it back to its original state. I was then able to use Ti Backup to reinstall everything.
Is there something I am missing in the backup or restore process? It seems pretty fool proof. I checked threads and once people get past the 3e recovery issue it seems like it is pretty much problem free for people.
Could someone at least let me know if I need to do something other than Backup and Restore to get this to work? From the posts it seems like there are a lot of people using this successfully.
it has always worked fine for me as long as i was not going back and forth from 2.1-2.2
i dont really know what your issue could be

[Q] OTA Update and Safestrap Clarification

Hello all,
I've been running Eclipse 2.2 on 902 for some time and I've stubbornly refused to switch away from using bootstrap for all my backup needs, however, after reading enough about it I decided to give safestrap a try. I've had a little trouble with the process however and was looking for a little clarity...
My understanding with safestrap was that in addition to giving me a safe (technically unsafe) 2nd partition/access to recovery in case I messed something up, that it would also pretty easily transfer data, apps, etc from one partition to the next, making flashing roms (and I thought updating) much easier and quicker without needing to backup individual portions of my system, Is this correct or am I mistaken?
Onward to what I did (my goal is to update to 905 and install eclipse 3.0) - Installed safestrap, backed up safe and unsafe side. I then went to unsafe and used bootstrap to restore to IMMEDIATELY after I applied the 902 update (had backed it up previously). This backup was literally a stock Bionic which I had updated from 886 all the way to 902, rooted, then installed bootstrap to backup. I then updated this to 905 with no issue, and of course backed it up... From here, my understanding was that I could simply swap over to safe side, then install the eclipse 3.0 through finding a zip in recovery - Recovery would not do this for me. It gave me an error similar to "cannot apply eclipse3.0.zip (bad)"
I tried to push the ROM both without making any changes (just switching from unsafe to safe and immediately trying to apply the zip) and when that didn't work I wiped data, formatted system, and wiped cache/dalvik and got the same error. (the net result through all of this was making my safe side non-responsive, and me ending up restoring safe side system to the initial backup I had made about 30 minutes prior).
Is this working as intended? Should I look at safestrap as purely an extra failsafe to keep me from bricking my phone and not an easier method to flash/update? If I have to expect that I need to go to safe, follow the same path to apply the update as I did on unsafe, then flash 3.0 and restore with titaniumbackup, sms/call log backup, etc, I will, but I just wanted to make sure I'm not misunderstanding something with safestrap that may allow me to make this whole process easier - I'd be much more interested in trying out a variety of ROMs if the restoring of my data wasn't such a hassle when I did it.
Sorry for the long post - I'm long winded and also wanted to get all of the information out there for anyone who may answer.
Thanks in advance!
-Jamie
Guess I was too wordy and nobody wants to read it (or posted in the wrong spot maybe) -
tldr:
Is there a way to use safestrap as having a way to easily transfer data etc from one rom/update to the next? or should I be using it solely to have an extra backup to prevent me from bricking my phone, and just do the longer more arduous methods of restoring data and settings after a rom swap/update?
I'm no expert but I have successfully used Safestrap, installed eclipse 3.0 as well as tried other roms and themes, and have other Android experience as well. Sounded like you may have used bootstrap and Safestrap at the same time. Am I wrong? If not, from my understanding that is a no no. Uninstall bootstrap completely and use Safestrap only. I also upgraded my "unsafe" system to .905 via OTA before attempting 3.0. My first experience with Safestrap, however, was not entirely positive either. I think my download was corrupt because it stopped working correctly. I downloaded again and haven't had any problems since. I followed this guide http://forum.xda-developers.com/showthread.php?t=1455888 and it worked. He's not really all that clear at times. It's also not necessary to factory reset after flashing a new rom. Always do it, but it can be done before too. I always do it before and have no problems. Also if you decide to apply a theme make sure you boot up the new ROM before flashing the theme. This guide was not entirely clear on that and it got stuck in a wicked boot loop that ended with me on stock and Safestrap gone. Keep trying. Hope some of this helped. I'm wordy too
Sent from my Galaxy Nexus using xda app-developers app
Btw, to answer your first question, the best way I've found to transfer user apps from ROM to ROM is with titanium backup. Other data will still be on your sd cards and accessible to the new ROM. I never use titanium to restore system settings and most system apps though. Things tend to get messed up if you try to do this from one rom to another. System apps can be converted to user apps with titanium which is cool then backed up and restored to new ROM. And never restore Google play app with titanium. Some go so far as to say don't restore apps with data but I haven't had any trouble except with core google apps like play, gmail, voice. Usually flash gapps if I have to and restore other core Google apps directly from play store. Sometimes titanium "hangs" on some apps. Not to much trouble with it lately maybe it's fixed used to be a PIA though.Sorry there's still plenty of setup involved any time you want to "dial in" a new ROM.
Sent from my Galaxy Nexus using xda app-developers app
Thanks G-diddy,
To clarify, I knew bootstrap and safestrap didn't play well together. That being said, I did NOT use safestrap to try and restore to a bootstrap backup. I installed safestrap, then swapped to my UNSAFE side, then restored to a previous bootstrap backup (using bootstrap), then OTAd to .905. I then backed up this fresh near stock but rooted .905 with safestrap (thus should never have to use bootstrap ever again). I then tried to swap over to safe and push eclipse 3.0 but had no success... At present my phone has near stock but rooted .905 on my unsafe side, and the same .902 with 2.2 eclipse on my safe side that I've been running for months...
I guess I have no choice but to restore my present safe side to the old bootstrap backup, then manually ota, then install the rom, I just thought that Safestrap would make all of this process easier - in as much as since my unsafe side is successfully updated, I was hoping my safe side would be too, making the process somewhat simpler. Sounds like I'm wrong in this assumption though, unless someone else can say otherwise?
Thanks for the tip on Titanium Backup too, although I've been using the premium version of that for months now, ever since I decided I was going to turn my phone into a toy

[Q] Problems upgrading from CM9 to 10.1

Maybe I havn't done my homework properly but I need to ask.
I have been running an OLD version of the CM9 (2012-07-25) on my xt862, and I finally decided to upgrade.
To my delight, I even found out there was an CM10.1 for my beloved Droid3.
I upgraded safestrap to 2.01 and started installing the lastest 10.1 image.
But when the upgrade is done, and I reboot, it seems to boot into stock rom for some odd reason.
After some reading I found that if charger is in while booting, it will boot into stock rom because of some bug.
So I tried to boot without charger - Same result.
Then I though, well, I had the charger plugged when upgrading.. maybe that's the issue.
Pulled the charger, rebooted, reinstalled, rebooted - same result.
I am now back on my backup with the old ICS image.
Am I doing something wrong? Or do I need perhaps to use the Saftestrap3?
I chose not to install the safestrap3 due to the incompatibility with the safestrap 1/2 backups.
Is there someone who can advice me on how to upgrade properly, and preferably without risking to loose my backups, or atleast a good way to convert/make new backups.
By the way, can I safely install saftestrap3 (if needed) from safe system? Or do I need to go back to stock for that?
(I went back to stock when upgrading from safestrap 1.08 to 2.01 though).
Also, one more question, I rad a lot about the camera not working.
I remember reading about the camera not working properly when I upgraded to CM9, but that was only video recording I think.
Is it the same problems in CM10.1 or is it the entire camera not working?
Edit: Maybe I should add, I am talking about Hashcodes rom's, nothing else.
Hmm.. anyone?
noratx said:
By the way, can I safely install saftestrap3 (if needed) from safe system? Or do I need to go back to stock for that?
(I went back to stock when upgrading from safestrap 1.08 to 2.01 though).
Click to expand...
Click to collapse
You need to upgrade from non-safe. Switch back to non-safe, start Safestrap, uninstall recovery. Restart to make sure that Safestrap is no longer running. Uninstall the current Safestrap app, and then install Safestrap 3.05. Start it, and tap the install recovery.
That should do it.
I haven't installed CM10.1, so can't answer any questions about that. I do know that it must be installed in the first ROM slot.
Yes, you definitely need to upgrade your Safestrap. Hash's latest Safestrap for D3 is v3.05.

Is there a twrp flashable zip of an unrooted stock version of c432b378 anywhere?

Hi,
Title pretty much says it all. Trying to go back to stock after ****ing something up using titanium backup. Phone still works, just a little buggy, tried undoing what I did using Titanium but it locks up. So I just want to essentially do a factory reset on the phone so I can try again. I have backups but they were from MM and as I understand it I can't go from Nougat to MM without potentially destroying my phone so i'd only use those as a last resort. Can't do a factory reset from within the phone because the file that got deleted was probably a system file and that won't be coming back unless I can find a way to restore it using Titanium which as I mentioned earlier won't work properly.
Alternatively a guide to resetting everything back to stock including recovery. As I would prefer to start completely over with the updated files.
Thanks

Categories

Resources