Flashing TWRP over CWM delete old back ups? - Verizon Samsung Galaxy S III

So I'm thinking of flashing TWRP over CWM. I've discovered that the backups made in CWM can't be restored in TWRP from other threads. My question is, does flashing TWRP automatically delete the old backups? Any info would be appreciated.

Eggsnbacon said:
So I'm thinking of flashing TWRP over CWM. I've discovered that the backups made in CWM can't be restored in TWRP from other threads. My question is, does flashing TWRP automatically delete the old backups? Any info would be appreciated.
Click to expand...
Click to collapse
not too educated on the subject but maybe they handle backups differently and cannot be restored through each other.

It won't delete the old backups just won't read them.

It shouldn't delete them, but yeah, they won't be read by TWRP. If you go to your clockworkmod folder, they should still be there and fully functional if you choose to go back to CWM.
Sent from my Galaxy S3

Awesome, thanks for the info guys!

Related

[Q] (Clockwork Mod) What is Nandroid Backup and How Does it Work?

This is a noob question, but I have a bit of experience under my belt just so you don't have to worry too much about using "confusing" terminology.
I have rooted/ROMed many devices in the past and have heard guides talking about doing a Nandroid backup. My question is how exactly does it work? Say for example: I am on the stock ROM (rooted of course) and I do a Nandroid backup while on stock. If go to say Cyanogen and I don't like it can I just restore from my nandroid backup like I would flash any other ROM to go back to stock. And if that will get me back to stock does it also preserve all of the user data that was in that ROM when it was backed up?
Any other information about about nandroid backups would be appreciated. Thanks in advance!
From my understanding, the backup backs up all the stuff on your phone EXCEPT for what's on the SD card.
The idea is that you do a back up. Then install a new rom that you want to try out. BUt you don't like it, so you just restore the backup and woolah! your old phone is back along with all your settings, data, etc.
I'm not sure why it's called a nandroid backup, but from what I gather, you can do it with clockworkmod, just boot into recovery. And use the backup and restore option.
That was my understanding as well. I just wasn't sure on the situation with the user data (or the backup in general really). So all it takes is a nandrid backup to revert back to (rooted) stock?
A Android backup takes all the files on your device and saves them as a data.img,system.I mg,cache.I mg,user data,and recovery.img. It is also restorable through fastboot. It can also get you out of a tough spot. Say you are messing with a new theme and it causes your device not to boot up or causes unwanted problems. You can restore a backup to a time when your device was working correctly.
saintmagician said:
From my understanding, the backup backs up all the stuff on your phone EXCEPT for what's on the SD card.
Click to expand...
Click to collapse
this is true unless you do a nandroid+android_secure backup. this also backs up your external app data
dunngh said:
This is a noob question, but I have a bit of experience under my belt just so you don't have to worry too much about using "confusing" terminology.
I have rooted/ROMed many devices in the past and have heard guides talking about doing a Nandroid backup. My question is how exactly does it work? Say for example: I am on the stock ROM (rooted of course) and I do a Nandroid backup while on stock. If go to say Cyanogen and I don't like it can I just restore from my nandroid backup like I would flash any other ROM to go back to stock. And if that will get me back to stock does it also preserve all of the user data that was in that ROM when it was backed up?
Any other information about about nandroid backups would be appreciated. Thanks in advance!
Click to expand...
Click to collapse
Yes you're correct. You can restore but just remember some app might have ext data in sdcard. If you don't delete it, when you restore you'll get the same as before
Sent from my HTC Desire Z using XDA App
rootfan said:
A Android backup takes all the files on your device and saves them as a data.img,system.I mg,cache.I mg,user data,and recovery.img. It is also restorable through fastboot. It can also get you out of a tough spot. Say you are messing with a new theme and it causes your device not to boot up or causes unwanted problems. You can restore a backup to a time when your device was working correctly.
Click to expand...
Click to collapse
So if you want to restore say just your data can you just delete the images you do not wish to restore from the backup folder and it will just keep the ones you have? Or won't it work at all if you start deleting images?
rfp101 said:
So if you want to restore say just your data can you just delete the images you do not wish to restore from the backup folder and it will just keep the ones you have? Or won't it work at all if you start deleting images?
Click to expand...
Click to collapse
i wouldnt tamper with a nandroid backup, but if you have clockwordmod recovery, that is possible. clockwordmod recovery gives you the option to restore one of those images (but only one at a time).
does a nandroid backup include your kernel?
Pender1 said:
does a nandroid backup include your kernel?
Click to expand...
Click to collapse
It does! It's a compelete "snapshot" of your phone with all apps/settings etc.
Does it also backup the stuff which has been stored on the external ext2-Partition, which is mounted to enlarge the space for apps?
Same with restore of this nandroid-backup. Will it also place the backup again to the same space?
As I know there's a (symbolic) link put into /data which might get problems.
dunngh said:
This is a noob question, but I have a bit of experience under my belt just so you don't have to worry too much about using "confusing" terminology.
I have rooted/ROMed many devices in the past and have heard guides talking about doing a Nandroid backup. My question is how exactly does it work? Say for example: I am on the stock ROM (rooted of course) and I do a Nandroid backup while on stock. If go to say Cyanogen and I don't like it can I just restore from my nandroid backup like I would flash any other ROM to go back to stock. And if that will get me back to stock does it also preserve all of the user data that was in that ROM when it was backed up?
Any other information about about nandroid backups would be appreciated. Thanks in advance!
Click to expand...
Click to collapse
its back up all yore staff and programs so if u will back to the backup it eill be exactly the same as beafore
If you install another ROM with different kernel and then you want to go back to nandroid backup, does it work ?
Nandroid backups
I was wondering if the framework is saved as well. I recently updated to the ICS firmware and am wondering if I restore with a backup from the old GB firmware will that be restored as well or will it still stay on the ICS? From my understanding ICS firmware will run previous versions
will nandroid backup (made from cwm) un-brick your phone if say, you installed a custom rom via cwm and it bricked it?
dunngh said:
This is a noob question, but I have a bit of experience under my belt just so you don't have to worry too much about using "confusing" terminology.
I have rooted/ROMed many devices in the past and have heard guides talking about doing a Nandroid backup. My question is how exactly does it work? Say for example: I am on the stock ROM (rooted of course) and I do a Nandroid backup while on stock. If go to say Cyanogen and I don't like it can I just restore from my nandroid backup like I would flash any other ROM to go back to stock. And if that will get me back to stock does it also preserve all of the user data that was in that ROM when it was backed up?
Any other information about about nandroid backups would be appreciated. Thanks in advance!
Click to expand...
Click to collapse
Yes,It restores all data and apps nandroid backup is a mirror copy of your phone.after restoring you will get your previous stock ROM.
cheebs42 said:
I was wondering if the framework is saved as well. I recently updated to the ICS firmware and am wondering if I restore with a backup from the old GB firmware will that be restored as well or will it still stay on the ICS? From my understanding ICS firmware will run previous versions
Click to expand...
Click to collapse
Interesting question. Anyone?
Snake X said:
will nandroid backup (made from cwm) un-brick your phone if say, you installed a custom rom via cwm and it bricked it?
Click to expand...
Click to collapse
im not sure, i think nandroid backup will unbrick your phone as long as you can boot to recovery. atleast when i installed a roms pach it didnt fully boot, got stuck at bootanimation, no loop, just froze, then i got it back with nandroid backup
I have the latest CWM 5.xxx, but there is no Nandroid backup option.
but only those below';
- backup and restore and under it
- backup
- restore
- advanced restore
- backup to internal sd card
- advanced restore from internal sdcard
Where is NANDROID Backup?
sas_sas said:
I have the latest CWM 5.xxx, but there is no Nandroid backup option.
but only those below';
- backup and restore and under it
- backup
- restore
- advanced restore
- backup to internal sd card
- advanced restore from internal sdcard
Where is NANDROID Backup?
Click to expand...
Click to collapse
all the options with the word backup are.
Sent from my GT-I9100 using xda premium

Some Back up Questions

Hi,
i am using CWM.
currently, i am under Cyanogen.
i want to try AOKP.
my question is
i have followed the steps below
a backup
Wipe data
Wipe system
Install AOKp
Till now am i right?
and after to come back to my backup
step 1
Should i Wipe Data?
step 2
Should i wipe system ?
Restore CWM of Cyanogen
are the steps 1 and 2 necessary?
is it a bad practice?
do it let gremlim?
moreover can i restore a back up made under TWRP from CWM?
Can i restore a back up made under CWM from TWRP?
how do you restore the back up?
am i missing steps? Fix permissions?
do i need to recalibrate my battery each time?
Thanks
Heniki
You can only restore CWM backups with CWM and TWRP backups with TWRP. As of now CWM 6's backup function is broken but it is being worked on. So make sure your Backups are from either TWRP or CMW 5 if you want them to work.
To restore a backup I wipe data/factory reset and wipe system. Then choose the backup I want to restore. No need to fix permissions unless things start to act funny after the restore. As far as battery calibration goes it's a myth.
hechoen said:
You can only restore CWM backups with CWM and TWRP backups with TWRP. As of now CWM 6's backup function is broken but it is being worked on. So make sure your Backups are from either TWRP or CMW 5 if you want them to work.
To restore a backup I wipe data/factory reset and wipe system. Then choose the backup I want to restore. No need to fix permissions unless things start to act funny after the restore. As far as battery calibration goes it's a myth.
Click to expand...
Click to collapse
With R6, Bryan said he fixed the backup and restore issues with CWM6. Idk about the rest of the features
When you say "Cyanogen" I think many assume you mean CM9 (ICS).
If you are running CM7 (GB), be very careful how you restore. Most system data (and perhaps some user data) from GB is not compatible with ICS.
jeffsf said:
When you say "Cyanogen" I think many assume you mean CM9 (ICS).
If you are running CM7 (GB), be very careful how you restore. Most system data (and perhaps some user data) from GB is not compatible with ICS.
Click to expand...
Click to collapse
Right, i am under CM9
Thanks guys
How i Can move from TWRP To CWM?
i found this one to move from CWM to TWRP http://forum.xda-developers.com/showthread.php?t=1721489.
i want really to understand what are the bad practices which will create gremlims
heniki said:
Thanks guys
How i Can move from TWRP To CWM?
i found this one to move from CWM to TWRP http://forum.xda-developers.com/showthread.php?t=1721489.
i want really to understand what are the bad practices which will create gremlims
Click to expand...
Click to collapse
As Fb said in the post you linked you flash the boot.img that came with your rom or reflash the rom.
The more times you flash roms the more issues you could have with "gremlins". Read more about it in the link.
http://forum.xda-developers.com/showthread.php?t=1500427
Sent from my SGH-T959V using xda premium

Corrupt internal SD Card

Hi Folks.
Ok here is my situation, I have a rooted and unlocked TF700.
I flashed Zeus 4 and all worked well, then flashed (after full wipe) PARANOIDANDROID 2.15 and again everything was great,
Yesterday I flashed Baked Bean 4 (again after a full wipe) and apart from some SD issues all seemed ok,
I then decided to restore my TWRP backup of Zeus as I needed to use my 64gig msd card.
After a full wipe and restore Zeus started up but the dpi was messed up (160) I think (way small)
I was seeing loads of FC's and file manager showed my internal SD as being empty. Rebooted to recovery and tried the "Format Data" option
It failed right away with this message "E: Unable to format data."
I have tried flashing the stock .26 rom via TWRP and I have the same issue, dpi set to 160 and internal sd not mounted.
It seems my Internal sd is corrupt
What is the procedure to reformat it via ADB or fastboot? (I have searched but the results I found relate to other devices and I dont want to simply follow instructions that might cause further harm to my TF700)
I have followed the NVflash brick proof procedure and have all relevant files backed up (I did this before flashing the last 2 roms)
Please can some one point me in the right direction
Thanks a lot
Jules
I always wipe cache, system, internal, davic and then do a factory reset.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
When you said that you tried to flash the stock .26 you meant installing not restoring a backup, right? What rom you have on your device right now?
Pretoriano80 said:
When you said that you tried to flash the stock .26 you meant installing not restoring a backup, right. What rom you have on your device right now?
Click to expand...
Click to collapse
Yip extracted the zip from the zip file and copied it to my ext sd and flashed it via TWRP
I have an unusable Zeus4,
Im about to try a full wipe again and then flash .26 again
EDIT
After flashing .26 and selecting reboot I get the "No OS installed! Are you sure you wish to reboot?" message
Looks like the system partition is corrupted, but i'm not sure. I think you should come here on IRC and maybe someone with more experience will help you - - http://webchat.freenode.net/?channels=asus-transformer
Thanks so much Pretoriano80!
With his help on IRC I was able to solve the problem,
In the end I had to return to complete stock, It seems CM10 caused some problems,
You are a a legend dude Thanks!!
:good:
ZaJules said:
Thanks so much Pretoriano80!
With his help on IRC I was able to solve the problem,
In the end I had to return to complete stock, It seems CM10 caused some problems,
You are a a legend dude Thanks!!
:good:
Click to expand...
Click to collapse
This same thing happened to me with my Prime when I was getting ready to send it off for RMA because of a broken HDMI port. Since I was unlocked I was advised to restore to stock before sending it in. However, before I got the chance to do that I started getting the "E: Unable to format data." error that you were. I ended up erasing all partitions from fastboot and putting a note in the box that it wouldn't boot after an OTA. I managed to get away with it and wasn't charged for fixing it
For future reference it would be really helpful to know how you fixed this. Did you do something like what is in this thread: http://forum.xda-developers.com/showthread.php?t=1803343.
Did you ever figure out how CM10 messed up your Infinity? I was running CM9 on my Prime when I got this error. Thanks!
It's hard to say if it was CM10 (or any other custom rom) or TWRP to mess the things up but we managed to get back to stock by replacing the twrp with CWM recovery and installing a modified .30 update package. Was a tricky one but we didn't had to mess with the partitions and that's good.
Pretoriano80 said:
It's hard to say if it was CM10 (or any other custom rom) or TWRP to mess the things up but we managed to get back to stock by replacing the twrp with CWM recovery and installing a modified .30 update package. Was a tricky one but we didn't had to mess with the partitions and that's good.
Click to expand...
Click to collapse
Why did you switch to CWM? Do you have any thoughts on the advantages and disadvantages of TWRP vs CWM?
paddycr said:
Why did you switch to CWM? Do you have any thoughts on the advantages and disadvantages of TWRP vs CWM?
Click to expand...
Click to collapse
Switched to CWM just to make sure it wasn't twrp recovery that somehow was failing to flash the partitions correctly. Tbh so far both do their job and both share the same limitation so far, meaning both fail to restore the boot partition (kernel) so in order to restore successfully (from a nandroid backup) you need to flash the right kernel after restoring is done. Otherwise i like TWRP better and never had issues with it, but i miss the advanced option from CWM, the one that let you format each partition individually.
Pretoriano80 said:
Switched to CWM just to make sure it wasn't twrp recovery that somehow was failing to flash the partitions correctly. Tbh so far both do their job and both share the same limitation so far, meaning both fail to restore the boot partition (kernel) so in order to restore successfully (from a nandroid backup) you need to flash the right kernel after restoring is done. Otherwise i like TWRP better and never had issues with it, but i miss the advanced option from CWM, the one that let you format each partition individually.
Click to expand...
Click to collapse
I'm not certain what you're referring to here. I've restored many times from different TWRP backups (for each custom rom that successfully boots and is half-decent, I make and keep a backup in case I want to jump around and try new things) and I've never had any issues. I am still on the .26 firmware update because I plan to do the nvflash thing. Are you saying that between Zeus v4 (ICS) and various Jelly Bean roms I've been on the same kernel? I gues I just haven't checked.
Anyway, I really love the TWRP recovery and use it with Xoom and Nexus 7 as well. It's so easy to use and always has been reliable.
okantomi said:
I'm not certain what you're referring to here. I've restored many times from different TWRP backups (for each custom rom that successfully boots and is half-decent, I make and keep a backup in case I want to jump around and try new things) and I've never had any issues. I am still on the .26 firmware update because I plan to do the nvflash thing. Are you saying that between Zeus v4 (ICS) and various Jelly Bean roms I've been on the same kernel? I gues I just haven't checked.
Anyway, I really love the TWRP recovery and use it with Xoom and Nexus 7 as well. It's so easy to use and always has been reliable.
Click to expand...
Click to collapse
For me moving between various roms by just restoring a backup never worked like it should. Let's say i'm on CM10 and i want to restore from a stock rom backup, the restore process is done, after reboot the device gets stuck to the first Asus screen and will stay there. Now if i get back to recovery and flash an update. zip containing the stock kernel the device will boot just fine, so definitely the boot image doesn't get restored in my case (with . 26 bootloader ).
Edit: @okantomi: You are using the internal storage or a MicroSD for backup / restoring? I'm really curious how this could work for some and not work for others, i mean same device, same recovery, same bootloader version...
Pretoriano80 said:
For me moving between various roms by just restoring a backup never worked like it should. Let's say i'm on CM10 and i want to restore from a stock rom backup, the restore process is done, after reboot the device gets stuck to the first Asus screen and will stay there. Now if i get back to recovery and flash an update. zip containing the stock kernel the device will boot just fine, so definitely the boot image doesn't get restored in my case (with . 26 bootloader ).
Edit: @okantomi: You are using the internal storage or a MicroSD for backup / restoring? I'm really curious how this could work for some and not work for others, i mean same device, same recovery, same bootloader version...
Click to expand...
Click to collapse
Ok, I only flash a new zip from the internal storage...made myself a "Flashworthy" folder which I keep stocked with newest versions of roms/gapps. I save my TWRP backups to my external microsdcard, as well as my TiBu backups. I have never had a problem restoring from TWRP this way, honestly.
okantomi said:
Ok, I only flash a new zip from the internal storage...made myself a "Flashworthy" folder which I keep stocked with newest versions of roms/gapps. I save my TWRP backups to my external microsdcard, as well as my TiBu backups. I have never had a problem restoring from TWRP this way, honestly.
Click to expand...
Click to collapse
Well, in this case i really have no clue why restoring works for some users but not for all.Dees_Troy, the dev behind Twrp recovery told me that .26 bootloader is to blame for the recovery failing to restore the boot partition, but looks like you have that bootloader version and restoring works good for you... interesting.
Pretoriano80 said:
Well, in this case i really have no clue why restoring works for some users but not for all.Dees_Troy, the dev behind Twrp recovery told me that .26 bootloader is to blame for the recovery failing to restore the boot partition, but looks like you have that bootloader version and restoring works good for you... interesting.
Click to expand...
Click to collapse
It is a mystery. Is there any other info that might be relevant to see why the difference in results? I ask because I would like to understand this device better, as well as potentially help others.
okantomi said:
It is a mystery. Is there any other info that might be relevant to see why the difference in results? I ask because I would like to understand this device better, as well as potentially help others.
Click to expand...
Click to collapse
I don't know, maybe the twrp version and the backup options, like if you are using compression or not, which partitions do you backup (boot, system, data, recovery, cache)...
Pretoriano80 said:
I don't know, maybe the twrp version and the backup options, like if you are using compression or not, which partitions do you backup (boot, system, data, recovery, cache)...
Click to expand...
Click to collapse
I'm using TWRP 2.2.2.1, I back up boot, system and data only, and I don't use compression.

[Q] CWM Blobs?

I am about to flash my 1st ROM on my S3 and I had made a nandroid of my phone a cpl months ago when it was running great, I was copying that nandroid to my PC prior to flashing the new ROM and notice it is quite small, about 21MB. Is that the complete nandroid or is it in the "blobs"? I have 3300 folders in my blobs directory consisting of 7000 files and it is 3.27GB.
Do I need to backup that blobs folder and carry it everywhere the "nandroid" backup goes?
Lastly, if I flash TWRP will it overwrite CWM and does TWRP make reliable nandroids?
Thanks
the blobs folder is indeed specific to the nandroid backup you created...if you try to restore your backup with a different blobs folder, you will be greeted with a system error. i prefer cwm 6.0.1, it works with everything for this device. oh and yea you can flash back and fourth between recoveries, one just overwrites the other.
droidstyle said:
the blobs folder is indeed specific to the nandroid backup you created...if you try to restore your backup with a different blobs folder, you will be greeted with a system error. i prefer cwm 6.0.1, it works with everything for this device. oh and yea you can flash back and fourth between recoveries, one just overwrites the other.
Click to expand...
Click to collapse
Thanks, I have 6.0.1.2, does the 6.0.1 you reference NOT have blobs?
TWRP makes perfectly fine nandroids. The blobs crap is what prevents you from moving/deleting individual nandroid backups. This is the reason I ditched CWM and only use TWRP now. When you frequently make backups, you need the ability to delete individual ones. What I did was load my stock nandroid that I wanted to keep, then flashed TWRP and made a new nandroid in that, and then flashed CWM again so i could go back to my current rom. Flashed TWRP once more and made another nandroid.
droidstyle said:
the blobs folder is indeed specific to the nandroid backup you created...if you try to restore your backup with a different blobs folder, you will be greeted with a system error. i prefer cwm 6.0.1, it works with everything for this device. oh and yea you can flash back and fourth between recoveries, one just overwrites the other.
Click to expand...
Click to collapse
apacseven said:
TWRP makes perfectly fine nandroids. The blobs crap is what prevents you from moving/deleting individual nandroid backups. This is the reason I ditched CWM and only use TWRP now. When you frequently make backups, you need the ability to delete individual ones. What I did was load my stock nandroid that I wanted to keep, then flashed TWRP and made a new nandroid in that, and then flashed CWM again so i could go back to my current rom. Flashed TWRP once more and made another nandroid.
Click to expand...
Click to collapse
Sounds like a perfect plan, I'll give it a go.
You guys realize you can stop making blob backups and go back to normal tar right? Under back up go to advanced settings or whatever its called and choose the other option. Now you won't make back ups in blobs,but now you do them the old way. One folder for the whole back up, about 1-2 GB in size. Blobs are just nice as the backup takes under 5 min. Doing it the old way takes a bit longer.
Sent from a GlaDos Baked Potato
No I did not realize that. When I was frustrated with CWM and was looking for a way to get rid of blobs, I couldnt find any info about this. Too late I'm afraid, no turning back from TWRP for me.
Legato Bluesummers said:
You guys realize you can stop making blob backups and go back to normal tar right? Under back up go to advanced settings or whatever its called and choose the other option. Now you won't make back ups in blobs,but now you do them the old way. One folder for the whole back up, about 1-2 GB in size. Blobs are just nice as the backup takes under 5 min. Doing it the old way takes a bit longer.
Sent from a GlaDos Baked Potato
Click to expand...
Click to collapse
yes i know, but i like the blobs folder because backing up/ restoring is so much faster...its nice for bouncing back and forth between roms.
What the Blob files do is they keep copies individually of everything the nandroid backs up.... and when you go to do another backup it will read both blobs and current setup to see what, if anything is the same. Then it will only back up the differences and make reference to all the data that is the same.
And I dunno yet if I like the blob system better than the old way or not yet. Usually I only keep nandroids of the latest version of different ROMs.
Which is best for Samsung Galaxy Nexus (toro)
apacseven said:
TWRP makes perfectly fine nandroids. The blobs crap is what prevents you from moving/deleting individual nandroid backups. This is the reason I ditched CWM and only use TWRP now. When you frequently make backups, you need the ability to delete individual ones. What I did was load my stock nandroid that I wanted to keep, then flashed TWRP and made a new nandroid in that, and then flashed CWM again so i could go back to my current rom. Flashed TWRP once more and made another nandroid.
Click to expand...
Click to collapse
Use Safestrap on Droid Razr for 2+ years ,and loved it! the ability to immediately revert to Stock saved me many times while learning the ropes about roms, rooting, and flashing. I just got my hands on an old but new Samsung Galaxy Nexus (Toro). Owner installed KitKat Shiny Rom for GNex, via CWM Touch, but is now redeployed and difficult to reach UGH! So I have no way of knowing "what's next?" Rom works well, but I must say that Cm10.2 and CM10.3 were more inclusive than this AOSP version of pure Kitkat. But, is slim and sleek, and I want to get used to it, but I want to blow it up forst and start from scratch.
With my Raxr, I performed every step so I am familiar with installing TWRP and Safestrap for Razr, but have not tried it on a GNex? Can u advise if u have? Should I go from newest CMW to TWEP. The main reason I like TWRp is the ability too boot to stock if issues with Rom appear, ability to create "nandroid" backup, the ability to install several Roms on one system.
So, do ya think it's safe? Worthwhile? Thanks!

[Completed] Restore OS After Wiping System Partition - Galaxy S5

Due to problems with Google Services on my rooted Galaxy S5 (SM-G900F) I opted for a reset from TWRP and it returned to a condition where after some initial screens it was just stuck at "Checking for Updates" so I went back into TWRP and told it to wipe the other partitions. Whoops - now I have no OS (I was sort of assuming that the factory reset OS was somewhere else)
Which is the stock ROM for my Region - UK, unbranded - where do I get it from and how do I load it using Odin and/or TWRP?
TIA
Hello,
Did you make a nandroid backup of your stock ROM or a nandroid backup of a custom ROM if you installed one? If you have a nandroid backup of either of those then you can restore them in TWRP by choosing the restore option and then your nandroid then swipe the slider at the bottom of the screen. If you installed a custom ROM at any time before this and you still have the ROM file then you can reflash the ROM and Gapps.
If you don't have a custom ROM stored anywhere but can still get to recovery, then you can download any of the custom ROMs compatible with your device and a Gapps package that matches it and put them on your extsdcard then boot to recovery and flash the ROM and gapps, do the normal wipes in recovery after flashing, the normal wipes(wipe data/factory reset, wipe cache and wipe dalvik cache), DO NOT CHOOSE THE ADVANCED OPTIONS THAT LET YOU WIPE PARTITIONS.
Check this thread to see if it is your stock firmware, it SHOULD be but double check first, it also has instructions for rooting again and installing recovery.
http://forum.xda-developers.com/galaxy-s5/development/stock-rom-root-recovery-sm-g900f-t2967725
If that doesn't work then go to Sammobile.com and search for your stock firmware by using your device model number.
The firmwares can sometimes be found at samsung-updates.com also.
Find the right firmware for your exact model number and flash through Odin.
For further assistance, post your question in the forum linked below.
http://forum.xda-developers.com/galaxy-s5/help
Good luck.
Droidriven said:
Did you make a nandroid backup of your stock ROM or a nandroid backup of a custom ROM if you installed one?
Click to expand...
Click to collapse
Sadly not - wasn't expecting to need it, thought it would revert to factory default - I have Titanium backup of apps and data.
I am hopefully a few minutes away from downloading the stock ROM and hopefully can reflash that using ODIN.
KD
colehill said:
Sadly not - wasn't expecting to need it, thought it would revert to factory default - I have Titanium backup of apps and data.
I am hopefully a few minutes away from downloading the stock ROM and hopefully can reflash that using ODIN.
KD
Click to expand...
Click to collapse
Making nandroid backups in recovery is the most important and valuable function of custom recovery, flashing ROMs is its' secondary purpose Android is not like PC with a recovery partition that restores a factory IMG, on PC that factory IMG is stored in a recovery partition. The factory reset feature in stock android does not restore an IMG, it deletes all data from the user partition and leaves everything in system partition the way it is, if you delete a system app and then do a factory reset then you will still not have the system app that you deleted. Anything you modify in system remains the way you modified it if you use the factory reset option. You should only use the factory reset in recovery, not the factory reset in system settings when you have a rooted device with custom recovery.
I'm sure that when you found the recovery, the directions had to have mentioned making a nandroid backup of your stock ROM before flashing anything, your present situation is why you do that, so that if anything goes wrong then you can easily restore to the one ROM that you know for sure works with no issues.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
I'm sure that when you found the recovery, the directions had to have mentioned making a nandroid backup of your stock ROM before flashing anything, your present situation is why you do that, so that if anything goes wrong then you can easily restore to the one ROM that you know for sure works with no issues.
Click to expand...
Click to collapse
I installed the TWERP recovery as part of the rooting operation and I didn't pay any attention to the backup option - I thought that's what Titanium did.
I am learning and will make sure that I take a Nandroid backup once I have it back up and running. Life would be so much simpler if only Samsunng didn't stuff their 'phones with bloatware that can't be deleted in stock mode.
KD
colehill said:
I installed the TWERP recovery as part of the rooting operation and I didn't pay any attention to the backup option - I thought that's what Titanium did.
I am learning and will make sure that I take a Nandroid backup once I have it back up and running. Life would be so much simpler if only Samsunng didn't stuff their 'phones with bloatware that can't be deleted in stock mode.
KD
Click to expand...
Click to collapse
Titanium backup can only backup data that you installed or downloaded, it does not backup anything that comes on the phone itself, that is what custom recovery is for.
When following guides to mod your device, read and understand ALL instructions before you even make the first move to touch your device. Get used to being thorough about reading and understanding first or you'll end up in a mess, possibly even hard brick your device, all it takes is one wrong move. Not all mistakes are fixable with android devices.
Sent from my SCH-I535 using Tapatalk

Categories

Resources