Database Users

Why are my Clockworkmod backups unusable?

So, I just rooted my Mytouch 4G a few days ago using the 'Ultimate' guide on this forum. I had root access and I disabled and deleted some stock apps from my phone. I was using LauncherPro instead of the HTC Sense launcher. I made a backup in Clockworkmod recovery immediately after installing Clockworkmod, before I'd made any major changes.
So, I spent the past few days removing and tweaking things. I had my phone working extremely well. But then I realized that I actually wanted an .apk file (the stock visual voicemail app) that I'd already deleted from the phone. It should be in my original backup file, right? So I figured that I'd make a new backup, restore my old backup containing the .apk file, copy the .apk file off of the phone, then restore my recent backup. Well...this didn't work.
When I restored either the original backup or the more recent backup, the phone would boot up and I'd get a message that the System UIDs are inconsistent. The phone would let me make phone calls, but 95% of my apps were missing from the loader. Most of the icons on my home screens were grayed out and would tell me the applications were missing when I tried to click on them.
I tried Fix Permissions in Clockworkmod recovery, but it didn't help. My Android Market app and all of my file manager apps didn't work, so I couldn't reinstall any apps. When I'd wipe all the data on my phone, but only restore the System backup, the Android Market would work and the phone basically returns to stock. But as soon as I restore my Data backup, everything breaks.
At this point, I've already wiped the phone and started over from scratch, but I'm afraid to rely on Clockworkmod/Rom Manager for backups again. Any ideas what went wrong?

did you flash a different kernel? this may be the issue, as I know that for other devices CWM does not restore the kernel.

this happens when your backups/card gets corrupted... it could of been a number of things... changing the name of something to how much you scan the card... hard to say exactly what caused it... If your really worried about it I would suggest making a backup of your backup on your computer just to be safe...

Hmm. Mine does.
mr.tenuki said:
did you flash a different kernel? this may be the issue, as I know that for other devices CWM does not restore the kernel.
Click to expand...
Click to collapse
Sent from my stickie key HTC Glacier using XDA App

I did make a backup of my backup, but it's not like these backups sat on the memory card for months before they got used. I ran the restore within minutes of when I made the last backup. Besides, aren't the backups hashed with md5 and then retested before restoring? So, if the files did get corrupted, I would think Clockworkmod would have notified me, no?
I just wish that after making a backup, there was some way to test it out without taking the chance of trashing my phone.
Regarding using a different kernel, I did not. I did not flash any experimental/downloaded images, these were simple backups and restores of my existing phone data.

mr.tenuki said:
did you flash a different kernel? this may be the issue, as I know that for other devices CWM does not restore the kernel.
Click to expand...
Click to collapse
This is for phones that dont support Nand like the vibrant. HTC phones is a full backup including kernel.

sundayhustler said:
I did make a backup of my backup, but it's not like these backups sat on the memory card for months before they got used. I ran the restore within minutes of when I made the last backup. Besides, aren't the backups hashed with md5 and then retested before restoring? So, if the files did get corrupted, I would think Clockworkmod would have notified me, no?
I just wish that after making a backup, there was some way to test it out without taking the chance of trashing my phone.
Regarding using a different kernel, I did not. I did not flash any experimental/downloaded images, these were simple backups and restores of my existing phone data.
Click to expand...
Click to collapse
Your right, CWM does do a md5 check when restoring. I'm sorry, I don't know what could be wrong. I currently have like 5 backups of 4 ROMS and have to restored to just to play around. Did you do apps2sd? This can cause major issues when switching ROM's.

I am also having a problem restoring to my stock rom. how big does my backup file have to be?

I have had this problem before. I think in my case my issue was caused by and incompatible version of CWM. I found that to be safe, I usually make two back ups, one with recovery in 2.5.12 and one with 3.0.0.6.

It was the file. It was only 60mb, apparently I ran out of memory thanks though my other backups work fine and I found the stock rom on a thread.
Sent from my HTC Glacier using XDA App

oh haha i was about to post.

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] Smooth Rom 4.4

Hi
As you've prob guessed I'm a noob, hence the help.
Ive just recently rooted and unlocked my nexus 7 with wugfresh 1.6.2 and am now looking at putting a custom rom on it.
Ive followed the advice and put titanium backup on and backed up my apps and system data.
Having read the instructions for installing Smooth Rom 4.4, it states 'Please do not restore a 'system' data backup as it would overwritte some important files'
does this mean I cannot restore my apps from titanium backup as I cant restore system data as they where backed up together or is there some other way for me to do it ?
does titanium backup get wiped as well ?
All Help appreciated, this is my first rom install and I dont wanna **** it up.

Robbie_UK said:
All Help appreciated, this is my first rom install and I dont wanna **** it up.
Click to expand...
Click to collapse
The most important thing to do is to make a FULL nandroid backup before you begin.
The 2nd most important thing to do is to get that backup copied someplace else besides the tablet. (PC, USB key, etc) Screw-ups involving accidental erasure of the psuedo- SD card area on the tablet are commonplace with folks that are new to this. It won't do you any good to make a backup if you immediately erase it while fooling around with a custom recovery (or toolkit) that is new to you.
I suggest you learn to make backups using the custom recovery rather than relying on a toolkit.
If you are happy with the tablet in it's current configuration, then a back-up allows you to survive any ****-ups that inevitably follow as you can return back to a known state and proceed again having learned from your mistakes.
FULL NANDROID BACKUPS. COPIED SOMEPLACE SAFE (OFF THE TABLET)
As for TiB, the only thing that is 100% safe is to only restore apps & their data that are NOT pre-installed in whatever ROM you are installing. Note this means not restoring any of the Google gapps as well, as you may have had a different versions of those apps running on your current ROM than on the to-be-installed ROM, whether pre-installed or updated later.
Yeah it's a bit of work restoring apps one by one and re-configuring things. There probably are System apps that can have their data safely restored to the wrong version of the app - but there are absolutely no guarantees that correct operation of the app will follow that.
cheers and good luck

Clockworkmod Recovery for Backups

I use Diablo67's recovery and nothing beats that. For those who don't know it is based on smelkus 4.3 but it has Diablo67's artistic flair. It's the best recovery for sure. However, there are some ROM's and zip's that require CWM recovery to flash effectively. For this reason, I have the ROM Manager and I keep both recovery zips on my sd card. When I need either of them, I go to my sd card and change the name to PC36IMG then flash with FlashImageGUI. When I'm all done, I change the name so the bootloader doesn't harass me for an update every time I reboot or power off. I can say without a doubt that nothing beats Clockworkmod for backing up and restoring your complete ROM. It misses nothing, and I have never encountered a problem like I have many times with the smelkus backup and restore. The smelkus requires you to keep it really simple. You backup the Boot, Cache, and System. Maybe sometimes add in the .androidsecure. Anything else added and it's not going to restore. My set up gives me the best of both worlds, and it's easy to use and saves a lot of time. Plus, I have no worries. I know my zips are gonna flash, and I know my backups are gonna restore. Maybe you would like to give this a try.

Sleepycloud said:
I use Diablo67's recovery and nothing beats that. For those who don't know it is based on smelkus 4.3 but it has Diablo67's artistic flair. It's the best recovery for sure. However, there are some ROM's and zip's that require CWM recovery to flash effectively. For this reason, I have the ROM Manager and I keep both recovery zips on my sd card. When I need either of them, I go to my sd card and change the name to PC36IMG then flash with FlashImageGUI. When I'm all done, I change the name so the bootloader doesn't harass me for an update every time I reboot or power off. I can say without a doubt that nothing beats Clockworkmod for backing up and restoring your complete ROM. It misses nothing, and I have never encountered a problem like I have many times with the smelkus backup and restore. The smelkus requires you to keep it really simple. You backup the Boot, Cache, and System. Maybe sometimes add in the .androidsecure. Anything else added and it's not going to restore. My set up gives me the best of both worlds, and it's easy to use and saves a lot of time. Plus, I have no worries. I know my zips are gonna flash, and I know my backups are gonna restore. Maybe you would like to give this a try.
Click to expand...
Click to collapse
Are you writing commercials now?
I have never had any issue with smelkus recovery. Unlike with CWM that doesn't always properly format partitions when you are getting ready to install a new rom. But Smelkus has no problems backing up everything. Not only that, but it can actually restor some backups that were made in CWM.
Don't mind you promoting CWM, but don't put down smelkus, when it does everything properly with no issues. If you had an issue with smelkus, you probably forgot to mark the box when you made the backup.
Oh, and there are absolutely NO rom's or zips that require CWM. I don't know where you got that idea.

souleman said:
Are you writing commercials now?
I have never had any issue with smelkus recovery. Unlike with CWM that doesn't always properly format partitions when you are getting ready to install a new rom. But Smelkus has no problems backing up everything. Not only that, but it can actually restor some backups that were made in CWM.
Don't mind you promoting CWM, but don't put down smelkus, when it does everything properly with no issues. If you had an issue with smelkus, you probably forgot to mark the box when you made the backup.
Oh, and there are absolutely NO rom's or zips that require CWM. I don't know where you got that idea.
Click to expand...
Click to collapse
I love smelkus. There is nothing better for a recovery. The ONLY thing I use CMW for is to backup my entire ROM. Outside of that, it is never installed on my device. I use it for an easy back up, and then I put smelkus back on. As far as the zips... Man, I've seen tons of ROM's where it is clearly posted that you MUST be using CWM or the ROM won't flash. This wasn't meant for advertising or dissing anybody. I just got an Odexer zip from somebody, they said use CWM... I called B.S. and flashed the zip with Smelkus. My phone never rebooted. I started over and flashed it with CWM and my phone is now odexed. You don't know what you are talking about. It has something to do with they type of permissions each differs in. Go read idiot. Who is putting Smelkus down? You obviously can't read or you're stupid and can't comprehend sentences properly. MY first three sentences clearly state that Smelkus is the BEST.

Please stay on topic and with respect, thanks all for your cooperation.

Sleepycloud said:
I love smelkus. There is nothing better for a recovery. The ONLY thing I use CMW for is to backup my entire ROM. Outside of that, it is never installed on my device. I use it for an easy back up, and then I put smelkus back on. As far as the zips... Man, I've seen tons of ROM's where it is clearly posted that you MUST be using CWM or the ROM won't flash. This wasn't meant for advertising or dissing anybody. I just got an Odexer zip from somebody, they said use CWM... I called B.S. and flashed the zip with Smelkus. My phone never rebooted. I started over and flashed it with CWM and my phone is now odexed. You don't know what you are talking about. It has something to do with they type of permissions each differs in. Go read idiot. Who is putting Smelkus down? You obviously can't read or you're stupid and can't comprehend sentences properly. MY first three sentences clearly state that Smelkus is the BEST.
Click to expand...
Click to collapse
This one? http://forum.xda-developers.com/showthread.php?t=2278586
Running Jellybread right now, so decided to test the CM7.2 version. I'll admit it, I had to clear cache and davlic-cache after flashing the zip in Smelkus. Then everything worked as expected and my phone is odexed. But since it's recommended to always clear cache and DC every time you flash a new zip anyway....
I actually expected it to cause problems, because I didn't check BOOTCLASSPATH before flashing it, just ran it.

[Q] Simplified Root Instructions?

This is the first time I've ever rooted an Android device. The process has been fraught with uncertainty and misinformation from around the internet. I'd like to describe what I have come to understand is the current preferred method, and ask a few questions to hopefully get my S5 where I want it to be.
I don't want to do anything to crazy (yet, anyway). I just want to remove some bloat and get the notification panel as close to vanilla Android as possible.
So far, I have ran towelroot, which was incredibly simple.
I installed SuperSU from the Play Store. During installation, it got stuck at "Disabling KNOX...". I have since learned that this is common and a reboot usually fixes it. However, I have also learned that I probably don't want to disable KNOX yet anyway, since I am not going to flash a custom ROM until there is one that is known to be stable and is able to create the vanilla Android experience that I want. Some people said that I should have installed SuperSU from chainfire's page instead of the Play Store, but I think that was old information.
Edit: I'm editing these steps as I go along:
1. Install busybox and the Safestrap APK
2. Use Safestrap to set up a new ROM slot and use that slot from now on (consider the italics a strikethrough)
^Even though the instruction video on the Safestrap page said this, apparently that's not what most people do. They use Safestrap to make a nandroid backup, and then use only one slot, the stock ROM slot, to experiment or flash a new ROM.
3. Install Titanium Backup
Edit: I also had to install SD KitKat Fixer and then reboot afterward to allow TB to write to the SD card...
4. Use Titanium Backup to backup all apps and data to SD card
5. Use Titanium to freeze processes that I carefully choose
Edit: I froze everything from the list here.
6. Install Xposed framework
7. Find the modules to customize Android how I want
Does that sound right? Any tips/advice?

ergalthema said:
So far, I have ran towelroot, which was incredibly simple.
Click to expand...
Click to collapse
By doing this, you are rooted.
Even if you are not going to flash a custom rom, you can and probably should disable KNOX. Doing so will not trip the counter.
Install busybox and the Safestrap APK - This is indeed necessary if you want to install another ROM to customize. The whole point of safestrap is to flash ROMs and is not related to rooting itself. The other use of Safestrap is to create a complete backup of your current system so that if you mess something up, you can restore to a known, working state.
Use Safestrap to set up a new ROM slot and use that slot from now on - This is fine if you want to switch between ROMs. I know some people like to do this, but I am not one of them.
Install Titanium Backup - absolutely
Use Titanium to freeze processes that I carefully choose - correct and there are threads with lists of APKs to freeze. You will also want to make sure you freeze SDM so that it doesn't prompt for security updates.
Use Titanium as a backup? (not sure about this) - this is to backup your apps, texts, things like that but NOT your ROM
Install Xposed framework
Find the modules to customize Android how I want

jcollier said:
Install busybox and the Safestrap APK - This is indeed necessary if you want to install another ROM to customize. The whole point of safestrap is to flash ROMs and is not related to rooting itself. The other use of Safestrap is to create a complete backup of your current system so that if you mess something up, you can restore to a known, working state.
Use Safestrap to set up a new ROM slot and use that slot from now on - This is fine if you want to switch between ROMs. I know some people like to do this, but I am not one of them.
Click to expand...
Click to collapse
The first step in installing Xposed in this thread is to do a nandroid backup. I'm not totally sure what that is, but someone in another thread said implied that Safestrap essentially does the same thing. That is why I was planning to use Safestrap.

ergalthema said:
The first step in installing Xposed in this thread is to do a nandroid backup. I'm not totally sure what that is, but someone in another thread said implied that Safestrap essentially does the same thing. That is why I was planning to use Safestrap.
Click to expand...
Click to collapse
That is what I meant by this: "The other use of Safestrap is to create a complete backup of your current system so that if you mess something up, you can restore to a known, working state."
A nandroid is a backup image of your system so that you can restore it if you screw something up. Safestrap isn't "essentially" doing the same thing, it is doing exactly that thing. Safestrap is a way to make a custom recovery work on our phone without an unlocked bootloader.

Good advice up to here, but you might want to hold off on using Exposed. As I understand it, Exposed lets you tinker with the existing stock ROM. I don't think I would want to do that, and I have rooted and ROM flashed several Android devices over the years. But its up to you.
With your being new to rooting, I'll offer this advice:
Titanium Backup (a.k.a. "TIBU") is a good way to back up all your apps. Here are some suggestions in using it:
--Buy the PRO version. It has more features, is not very expensive, and helps support a really cool app that is very handy.
--Set the Preferences/Backup folder to your REAL external SD Card. It will default to internal storage (also called "sd card"....don't get me started lol) which is IMO totally useless. If you lose internal storage due to corruption or whatever, you would lose all your backups. Having them on the REAL SD card you can also archive them to your PC.
--Set your Max Backup History to some number larger than the default "1". I use 7. Why? Well, have you ever seen the developer of one of your favorite apps suddenly screw it completely up in some update? Or, worse yet, sell out to some other vendor who now made it a PAY SUBSCRIPTION app?? I have. By keeping multiple backups you can roll back in time to previous versions that you know WORKED when those things happen. I have several apps I will never update, especially on the Store, for various reasons. (TIBU used to be able to disconnect the link to the Store so apps didn't try to update, but Google broke their ability to do that).
--When you do make TIBU backups, select "app and system data" which is IMO incorrectly worded and causes confusion. It should read "app and APP data". Because that is what it really does. Backs up the data IN your system that is associated ONLY with the APP. NOT any "system files". When you restore a backup, restore "app and system data" and you not only get the app installed, you get all your data it created, as well as all your customized settings restored! It is a real time saver. And you can "usually" even do this with a new device, using the TIBU backup folder on an SD card you had in some previous Android device. I've done it many times.
Safestrap installs a custom version of TWRP recovery. From that you can make the aforementioned "nandroid" backups of your complete system. (You won't see the word "nandroid" in TWRP while you are doing this. It just calls them backups). Couple of caveats with TWRP (and the Safestrap version):
--The date/time stamp used in both TWRP and its alternative, Clockworkmod Recovery (CW) will always be wrong. I've read (in short) there is no way for them to fix it. BUT........you most certainly CAN edit the backup file name to be whatever you like while setting it up to make the backup. So I recommend deleting the portion of the name that is the screwed up date it will generate, and putting in a date you can read, like my preferred format of 2014-07-10-1727 which is today at 5:27 PM, or whatever format you like.
--By default, TWRP recovery uses (in the Advanced settings) an inane "power saving" feature of the display, which will maddeningly keep turning it off and making you think the phone died while it is in the middle of making your backup. A - ALWAYS keep your phone on the charger when working in Recovery!! Don't even start unless it has at least 40% charge. B- Turn OFF the inane "power saving feature" and get some peace of mind. The screen will stay lit forever, until you reboot system when you are done.
--By default, TWRP will be set to use INTERNAL STORAGE as the place to keep your nandroids. Again, I consider that a very bad idea. Use a REAL External SD card and keep them there. And make regular backups to your PC of the SD card. I've seen a great many SD cards suddenly fail without warning. Your device will pop up and tell you the SD card is corrupt, and you need to format it. Usually, there is no way to recover the lost data on the card when that happens.
--On my Galaxy S5, making a nandroid of the stock OS via Safestrap took up over 4GB! That is almost 4 x what I normally see making a nandroid of a custom ROM on some previous device. So make sure you have plenty of room on whatever SD card you choose to use.

jcollier said:
Even if you are not going to flash a custom rom, you can and probably should disable KNOX. Doing so will not trip the counter.
Click to expand...
Click to collapse
I didn't know it wouldn't trip the counter. I'm curious why I should disable it though.

I followed the video exactly and when I get to the point of the first Restore (around 9:00), it says "Restore Complete - Failed". There is a button to Reboot System. When I tap that, the phone won't turn on. I have to pull the batter to get it back on. I guess I'll be uninstalling Safestrap. If I "Uninstall Recovery" from the stock ROM slot, will the space be freed up again and the phone be returned to the same state as before I tried using Safestrap?

ergalthema said:
I followed the video exactly and when I get to the point of the first Restore (around 9:00), it says "Restore Complete - Failed". There is a button to Reboot System. When I tap that, the phone won't turn on. I have to pull the batter to get it back on. I guess I'll be uninstalling Safestrap. If I "Uninstall Recovery" from the stock ROM slot, will the space be freed up again and the phone be returned to the same state as before I tried using Safestrap?
Click to expand...
Click to collapse
May I ask what it is that you are restoring? Have you already made a (nandroid) backup? That's what the restore function is made to restore. If you tried to use Restore on some other kind of file, then it would try to overwrite your ROM (OS) with it, and make the phone unusable. If that happens, I think your only fix would be to Odin back to stock and start over from scratch. I believe there is a link to do that in the thread telling how to root the S5.

Zoandroid said:
May I ask what it is that you are restoring? Have you already made a (nandroid) backup?
Click to expand...
Click to collapse
The video at 9:00 explains it. I think it is basically flashing the backup I made of the stock ROM to the newly created ROM slot in order to begin running from the new ROM slot.

ergalthema said:
The video at 9:00 explains it. I think it is basically flashing the backup I made of the stock ROM to the newly created ROM slot in order to begin running from the new ROM slot.
Click to expand...
Click to collapse
Oh, OK. Since there aren't any ROMs available yet, I did not pursue that aspect of Safestrap. So you have stepped outside my range of experience with it. Hopefully someone else can help you.
If you get to a point in your endeavors where you find a solution to apply ad-blocking to the S5, please let me know in a PM. I've had no luck so far. It appears this will be yet another issue that will only be solved with some creative developer work. Google has done something in KitKat to block not only apps like Ad-Aware and Adblock Plus from working, they also seem to have some kind of snooper utility that, if you try to search online with the S5 for ad blocking, will pop up a browser page saying Google "cannot access" the page! Pages which my PCs can see easily. Crafty little PITAs for sure! I thought it might just be Chrome doing this, so when I tried to get Firefox from the Store, I was stuck in an endless downloading loop. I had to kill that and restore a copy from TIBU. They are doing everything they can think of to lock down a smartphone and spoon feed us only what THEY want us to see. Including copious advertisements.
There was a time when Android meant "freedom". I guess that time has passed. Now it is time for someone else with very deep pockets to re-kindle a hassle-free smartphone OS. It is a shame. Android has so much potential.

ergalthema said:
The video at 9:00 explains it. I think it is basically flashing the backup I made of the stock ROM to the newly created ROM slot in order to begin running from the new ROM slot.
Click to expand...
Click to collapse
Why flash the stock ROM in a newly created ROM slot? You should only create a ROM slot if you decide to run a custom ROM. If not, you can use safestrap to create the backup (nandroid) and save it to your SD card so you always have a "safe" restore point essentially. I run a custom ROM in my stock slot. And for the record... There are several ROMs in the development section which are quite stable. Also, you can check out the Safestrap thread there as well. If you read through the thread you'll have a better understanding of how it works and what bugs there are right now.
The thing that I find great about XDA is that folks will always try to help each other out. Good luck!
Sent from my SM-G900V using XDA Premium 4 mobile app

Do we have a thread where folks are reporting having tried various versions of the available ROMs for the Verizon S5, and can make a simple statement about what works and what doesn't? I think that would be a really good idea. Without something like that, the only way to really know which ones are trouble free is to slog through and read each and every post on every ROM thread, most of which will usually be outdated information anyway.
Maybe it could be done as a Poll so it doesn't grow into something just as long to read as the above.

Zoandroid said:
Do we have a thread where folks are reporting having tried various versions of the available ROMs for the Verizon S5, and can make a simple statement about what works and what doesn't? I think that would be a really good idea. Without something like that, the only way to really know which ones are trouble free is to slog through and read each and every post on every ROM thread, most of which will usually be outdated information anyway.
Maybe it could be done as a Poll so it doesn't grow into something just as long to read as the above.
Click to expand...
Click to collapse
That would be great - especially for the people who aren't on this site all day and don't know what is good and current.
shoresteve626 said:
Why flash the stock ROM in a newly created ROM slot? You should only create a ROM slot if you decide to run a custom ROM. If not, you can use safestrap to create the backup (nandroid) and save it to your SD card so you always have a "safe" restore point essentially. I run a custom ROM in my stock slot. And for the record... There are several ROMs in the development section which are quite stable.
Click to expand...
Click to collapse
I'm realizing that's probably what most people do. In the instructional video posted on the main Safestrap OP, it instructed to keep the original stock slot intact, and use a new slot for experimenting with another ROM. I would love to know a stable ROM that gives the most vanilla Android.