SBF vs. Nandroid of Clean Stock - Droid X General

Quick question for the gurus.
If you wipe everything, factory reset, SBF, and then immediately make a nandroid, what is left over when restoring to that point?
I've done SBF's before, without wiping everything manually, and there was still stuff saved. I've also done restores, where it would appear that some things remained.
Is it possible to have a perfectly (or extremely close) stock restore point? What exactly remains when doing a restore, and what should be done prior to the restore to ensure that it's complete?
Essentially, I would like to swap between Fission and Rubix blurry, as needed, without somehow contaminating the other ROM.
The last time I did a bit too much ROM testing, and was swapping between 5 or more builds, and in the end I found that I was starting to get a lot of force crashes, which of course led me to doing an SBF again.
Thank you,
--bb

bladebarrier said:
Quick question for the gurus.
If you wipe everything, factory reset, SBF, and then immediately make a nandroid, what is left over when restoring to that point?
I've done SBF's before, without wiping everything manually, and there was still stuff saved. I've also done restores, where it would appear that some things remained.
Is it possible to have a perfectly (or extremely close) stock restore point? What exactly remains when doing a restore, and what should be done prior to the restore to ensure that it's complete?
Essentially, I would like to swap between Fission and Rubix blurry, as needed, without somehow contaminating the other ROM.
The last time I did a bit too much ROM testing, and was swapping between 5 or more builds, and in the end I found that I was starting to get a lot of force crashes, which of course led me to doing an SBF again.
Thank you,
--bb
Click to expand...
Click to collapse
Good question. I've had different experiences with SBF, as have others. Sometimes, it does a clean wipe. Other times you need to factory reset to get to 2.3.15 OTA.
In order to do a backup, you MUST be rooted, so your backup is, by definition, not clean. In short, say you had to return your phone to stock so you could get it covered or exchanged, SBF + plus factory reset is your friend.
There is another way on the 928droid site. It's a link to the Stock OTA 2.3.15: http://928droid.com/DroidX.htm
Second link from the bottom. Bon apetit!

Related

[Q] One Click vs Unlocked Bootloader

Simple question, one i didn't find a quick simple answer too.
I know the main differences between one-click root and unlocking the bootloader, and the biggest for me was the warranty. I used one-click root so just in case, I could revert back. Now my warranty is just about up, and I figure why not? My biggest question is, will it provide any benefits?
For some reason I have never been able to install themes (either update.zip files or through metamorph), I just go into an infinite boot loop. I was hoping this was the only issue. But I don't know enough to know the answer
Benefits are safer radio flashing, and if you ever **** the phone up so bad you can't boot into anything other than the bootloader, you can fastboot flash everything required to get going again.
Rusty! said:
Benefits are safer radio flashing, and if you ever **** the phone up so bad you can't boot into anything other than the bootloader, you can fastboot flash everything required to get going again.
Click to expand...
Click to collapse
One more little question; Should i reflash CM7 (im running the nightlies currently) when its done? I read that it will wipe all data (already got everything backed up ready to go) but I was just wondering if I would need to reflash anything right now, like CM7 or the recovery?
Take NANDroid, unlock, restore NANDroid, continue as if nothing happened.
Rusty! said:
Take NANDroid, unlock, restore NANDroid, continue as if nothing happened.
Click to expand...
Click to collapse
Tons of awesomesauce I guess thats what I will go ahead and do! Thank you so very much for the quick help!
EDIT: Done, restoring the NANDroid backup now I hesitated a little bit when hitting that button though, a year of me holding back doing it because of the warranty was still making my trigger finger nervous
... And back in my rom, everything normal once again And again thanks for the quick help.
Well not so normal; I have lost my setup accounts, and everytime I try restoring a NANDroid the accounts are still gone, and there isn't an option to add in a google account and none of the google apps work. No force closes just closes the second you try to open it.
I have tried reflashing both the rom and gapps, still no good.
Am i going to need to wipe?
Certainly shouldn't do, I unlocked my bootloader in the same way and everything continued as normal.
Bit odd that you can't add your account back though, the option should be there under accounts & sync.
It sounds like what happens when you try and use CM without adding GApps
That's what I thought too. So I tried flashing gapps, nothing.
Went ahead and did a full wipe. Quite amazed so far what all android is restoring for me. Nearly all back
Sent from my Nexus One using XDA App

Thinking about starting over

I think I might RUU back to stock tonight, re-root, reformat my SD Card and just start fresh.
I've done so much to this phone, and I'm starting to see some glitches that I think I can solve by restoring to stock and going form there.
Now, if I can just remember how to run UnrEVOked in Ubuntu....
It does fix a lotta problems
A drop of Chuck Norris's semen was placed on Android OS. We now have CyanogenMod.
Sometimes when my phone used to act a little slow, I'd just wipe cache and dalvik cache and it would go back to normal. Now that I create NAND's every few days and delete the previous one (in case I have to restore my phone, this way my NAND will be as current as possible), I just wipe both caches during the NAND process and I haven't noticed my phone slow down one bit.
dont need to un-root. Just run the format-all.zip twice, flash a rom and reload apps.
One of the glitches is that none of my Nandroids will restore, which is part of why I want to start fresh, so I can have a fresh stock/rooted nandroid, and several of my apps aren't restoring data with Titanium Backup, for some reason.
Now for some reason, and this MAY be ROM related, my Swype stops Swyping, even though I just updated it via the Swype Installer, uhh, several timeas.
One other thing, I originally rooted with the one step root method, which kept freezing up, then UnrEVOked failed in Windows, which is why I did it on my Ubuntu, so right from the start things were a little messed up.
Besides, I can't remember what stock was even like anymore... lol
HipKat said:
Besides, I can't remember what stock was even like anymore... lol
Click to expand...
Click to collapse
I predict you won't like "stock" ... and even if it's tolerable, the urge to slip into that old dark rain coat will be lurking!
lol... 5 mins after Stock, I'll be reaching for a new ROM, I can see it already....
See that's the difference. On the Moment, you almost HAD to restore to stock before flashing a new ROM.
Just seemed like a lot less problems that way.

Gingerbread Backups - Unreliable?

Okay, I'm about to SBF my phone, which is a major PITA. So I thought I should caution other members. I was on the Rooted/DeOdex'd Gingerbread release with the ALPHA1 theme and wanted to try out RubixBlurryBread. Rubix install went fine, and booted no problem. It didn't seem like an improvement over the original leak, and actually ran slower on my phone. I thought "No biggie, I made a backup before flashing Rubix"...... wrong. I restored my backup and everything went as it always does with a backup, until the bootup. It's a backup, a 1-to-1 match of how my phone was just 30 minutes earlier, this can't be happening, but I'm stuck in a boot loop. So, even though I hate the idea, I formatted the Data and Cache. Still boot looping. Grrr... Did factory reset from standard recovery, no help. Wiped Data/Cache and reinstalled the original DeOdex'd zip from TBH.. nothing is working, everything results in a boot loop.
Anyone have any insight on this? I really don't want to have to set everything up again. I'm going to SBF, but not going to set everything up again, until I know for sure that my backup is useless, for whatever reason.
raziel36 said:
Okay, I'm about to SBF my phone, which is a major PITA. So I thought I should caution other members. I was on the Rooted/DeOdex'd Gingerbread release with the ALPHA1 theme and wanted to try out RubixBlurryBread. Rubix install went fine, and booted no problem. It didn't seem like an improvement over the original leak, and actually ran slower on my phone. I thought "No biggie, I made a backup before flashing Rubix"...... wrong. I restored my backup and everything went as it always does with a backup, until the bootup. It's a backup, a 1-to-1 match of how my phone was just 30 minutes earlier, this can't be happening, but I'm stuck in a boot loop. So, even though I hate the idea, I formatted the Data and Cache. Still boot looping. Grrr... Did factory reset from standard recovery, no help. Wiped Data/Cache and reinstalled the original DeOdex'd zip from TBH.. nothing is working, everything results in a boot loop.
Anyone have any insight on this? I really don't want to have to set everything up again. I'm going to SBF, but not going to set everything up again, until I know for sure that my backup is useless, for whatever reason.
Click to expand...
Click to collapse
just SBF, reroot, and reflash the GB leak
boot into the GB leaked than boot into recovery again
than advance restore data only
if this doesnt work than your back to square 1 with your data
raziel36 said:
Okay, I'm about to SBF my phone, which is a major PITA. So I thought I should caution other members. I was on the Rooted/DeOdex'd Gingerbread release with the ALPHA1 theme and wanted to try out RubixBlurryBread. Rubix install went fine, and booted no problem. It didn't seem like an improvement over the original leak, and actually ran slower on my phone. I thought "No biggie, I made a backup before flashing Rubix"...... wrong. I restored my backup and everything went as it always does with a backup, until the bootup. It's a backup, a 1-to-1 match of how my phone was just 30 minutes earlier, this can't be happening, but I'm stuck in a boot loop. So, even though I hate the idea, I formatted the Data and Cache. Still boot looping. Grrr... Did factory reset from standard recovery, no help. Wiped Data/Cache and reinstalled the original DeOdex'd zip from TBH.. nothing is working, everything results in a boot loop.
Anyone have any insight on this? I really don't want to have to set everything up again. I'm going to SBF, but not going to set everything up again, until I know for sure that my backup is useless, for whatever reason.
Click to expand...
Click to collapse
You have to install the rooted version first then install the deodexed zip because I believe the deodexed zip only changes some system files, I did the same thing by mistake. So unfortunately you will have to SBF but when you get back up and running just remember to flash the root only zip first then boot into recovery and you can then flash the deodexed zip, hope this helps
luigi90210 said:
just SBF, reroot, and reflash the GB leak
boot into the GB leaked than boot into recovery again
than advance restore data only
if this doesnt work than your back to square 1 with your data
Click to expand...
Click to collapse
This is what I did last night, just before going to sleep. Thankfully, it worked, so only thing I had to really do was re-apply the theme and 180 LCD Density. Cool that we had the same idea but I'm still concerned about the backup not working, because I definitely don't want to make a habit of SBF'ing any time I don't like a new ROM, though I'm probably going to wait for LibertyGB before I flash another, and I'm fairly certain I will like that one
Thanks for taking the time to read and comment, really appreciate it.
I tried to go back to my stock bg backup also. It went ok and started up but I got force close on all my blur apps. I couldn't get the fc's to stop so I also had to sbf and reload everything.

Newbie needs help/info

I have a T-Mo G2 and want to keep my Froyo image to reinstall later if I cannot get theGingerbread to work right. I want to make an image file that will restore the phone to exactly how it is now. I have tried all kinds of stuff, but am not able to make the "img" file so that I ca do a restore when booting...
Can someone point me to what I need to install to do this, and if possible some directions on what/how to create the "img" or restore file ?
I would be most appreciative, as I had to reverse everything from the OTA of Gingerbread, since too many apps didn't work, ESPECIALLY the GPS!
My current Froyo is a temp-root system.
Thank you all!
Aloha. .
I would do full root via the wiki, and then install 4EXT (the full one that's like $2) - it will keep your old stuff straight
Ditto on previous reply
Root your G2
Backup all your apps with using Titanium backup
Get Clockwork mod ROM manger or 4ext ( I prefer 4ext) and backup your stock rom. You can download new ROM CM7 for first ROM.
If you don't like the ROM you can restore your stock ROM with CWM or 4ext at anytime.
I have a theory that Ti Backup or any backing up of apps is a bad plan. I know you can do it no problem, and that it is a great time saver, but I have a strong feeling that this ultimately results in an unstable phone with mysterious force closes etc.
Even though it's a real pain, I think you are always better off reinstalling your apps from scratch after changing to a new ROM and wiping caches.
WTF? said:
I have a theory that Ti Backup or any backing up of apps is a bad plan. I know you can do it no problem, and that it is a great time saver, but I have a strong feeling that this ultimately results in an unstable phone with mysterious force closes etc.
Even though it's a real pain, I think you are always better off reinstalling your apps from scratch after changing to a new ROM and wiping caches.
Click to expand...
Click to collapse
1. I have had zero problems with TB personally.
2. Without it your app data is gone.
3. Triple wipe, takes a few extra minutes and makes a world of a difference.
4. Do not restore system data!
5. Check md5 sums BEFORE doing anything!!!!
6. Make sure you have a recent nandroid backup and you'll be fine either way.
7. triple wipe before flashing anything including nandroids. Preferably with different wipes aka factory reset, superwipe+ ext4, then recovery wipe!
Just my 2 cents, it's saved my a$$ more then a few times...

[Q] Different backups, superusers, and flashing kernels

Hi all,
I have learned a lot about Android customization in the last week since my Nexus 4 finally arrived at my door, and I have become reasonably comfortable with the processes of flashing ROMs/kernels, and backing up my phone to make sure I have something stable to return to if something happens to go wrong. However, I am still dealing with a few points of confusion that I was hoping someone could clarify for me:
1. I have CWM installed on my phone and I can use it to backup/restore images of my phone for safety. However, I have heard about other methods like Nandroid, Carbon/Helium, and Titanium Backup while browsing the forums, and have tried them only to become confused as to how they are different from using CWM backup. Could someone please explain this to me and clarify which is the best for keeping a backup of my phone stored on my computer?
2. I have noticed that when I "wipe date/factory reset" in CWM, not everything on my phone is wiped. There are still plenty of files left over from previous ROM installs when I browse my phone with Android File Transfer, and obviously the .zip files you need to flash new ROM's/kernels are left too. What exactly is deleted when do a CWM factory reset?
3. Is it necessary to wipe everything when installing a custom kernel? I have CyanogenMod 10.2 installed because it is quick and relatively bloat-free, but allows for enough customization that I can make the my phone feel the way I want it to. I want to give Matr1x/Hells-core a try, but I am tired of factory reseting everything when install a new kernel. Can I get away with just wiping Cache/Dalvik and flashing the new kernels? If not, what is the best way to avoid losing app data between ROM and kernel flashes?
4. What is the difference between the default Android superuser, CWM superuser, and SuperSU? They all seem like the same thing and it makes me nervous installing different ones.
Any information you guys can offer would be great. Thank you so much for your time !
Downloaded7 said:
Hi all,
I have learned a lot about Android customization in the last week since my Nexus 4 finally arrived at my door, and I have become reasonably comfortable with the processes of flashing ROMs/kernels, and backing up my phone to make sure I have something stable to return to if something happens to go wrong. However, I am still dealing with a few points of confusion that I was hoping someone could clarify for me:
1. I have CWM installed on my phone and I can use it to backup/restore images of my phone for safety. However, I have heard about other methods like Nandroid, Carbon/Helium, and Titanium Backup while browsing the forums, and have tried them only to become confused as to how they are different from using CWM backup. Could someone please explain this to me and clarify which is the best for keeping a backup of my phone stored on my computer?
A backup in CWM is the same as a nandroid backup. It basically take a "snapshot" of your ROM and restore it exactly as it was when backing up.
Titanium Backup is an app that backup your apps and app's data. It's recommend you only restore user's apps and data. Let Google restore any system app's data.
2. I have noticed that when I "wipe date/factory reset" in CWM, not everything on my phone is wiped. There are still plenty of files left over from previous ROM installs when I browse my phone with Android File Transfer, and obviously the .zip files you need to flash new ROM's/kernels are left too. What exactly is deleted when do a CWM factory reset?
Wiping data/factory reset only wipe the data. Wiping system will wipe your ROM (system partition) Of course you don't want to wipe all the files such as the ROM you're going to flash.
There's an option to format internal sd, that will wipe EVERYTHING so unless you know how to ADB push files or sideload a ROM, DO NOT touch that.
3. Is it necessary to wipe everything when installing a custom kernel? I have CyanogenMod 10.2 installed because it is quick and relatively bloat-free, but allows for enough customization that I can make the my phone feel the way I want it to. I want to give Matr1x/Hells-core a try, but I am tired of factory reseting everything when install a new kernel. Can I get away with just wiping Cache/Dalvik and flashing the new kernels? If not, what is the best way to avoid losing app data between ROM and kernel flashes?
No, just flash kernel. Some recommend wipe cache and dalvik cache after kernel flash before reboot.
4. What is the difference between the default Android superuser, CWM superuser, and SuperSU? They all seem like the same thing and it makes me nervous installing different ones.
Different app that does the same thing. Usually go with what is recommend by the ROM's dev. I ususally just leave what's included with the ROM.
Any information you guys can offer would be great. Thank you so much for your time !
Click to expand...
Click to collapse
Hope that answer some of your questions. I'm sure I left out some stuffs so hopefully someone else can add to it.:good:

Categories

Resources