Related
I have rooted, installed Amon Ra flash recovery, and currently using CM6.
I forgot to do the backup flash when I had my stock rom, so I went ahead and backed up the CM6. Is that okay?
SHicks18 said:
I have rooted, installed Amon Ra flash recovery, and currently using CM6.
I forgot to do the backup flash when I had my stock rom, so I went ahead and backed up the CM6. Is that okay?
Click to expand...
Click to collapse
uhhh well, if you didn't need you're old stock rom or ever wanted to flash back to it you needed to back that up aswell, im guessing you atleast backedup your data and apps using mybackuppro or titanum?
From my research so far...and I have yet to actually commit to first root...you could just load the rooted 1.47...set it up...and back up that.
But...if I have the terminology right (please experts chime in as it will help me too)...titanium or whatever only backs up stuff...not the rom.
Nandroid back up is everything....
Which did you do? If you back up all the apps and whatever settings with titanium or my backup...then you should be ok regardless of rom.
If you are talking nandroid backup....then CM6 is now your fall back for everything.
So...my plan is to do my first nandroid with rooted 1.47. (Well it is at this moment in time.)
ps...is it nand or nandroid...oh well.
I could always download the stock rom, flash it as my backup, and go from there... correct?
SHicks18 said:
I could always download the stock rom, flash it as my backup, and go from there... correct?
Click to expand...
Click to collapse
yes, that's an possible option.
youngdhillon said:
yes, that's an possible option.
Click to expand...
Click to collapse
But...remember difference between stock Rom and rooted stock Rom...at least that is what I am reading. If you want to keep root...use a rooted version of that stock Rom.
(I have seen one thread saying could be issues.)
ps...again more experienced please chime in.
if you want to be safe dl rooted stock rom, flash radio then wimax then rom, once thats done do a nandroid backup of that then a nandriod restore of cm6 presto all warm and fuzzy with backups.
sablesurfer said:
..you could just load the rooted 1.47...set it up...and back up that.
But...if I have the terminology right (please experts chime in as it will help me too)...titanium or whatever only backs up stuff...not the rom.
Click to expand...
Click to collapse
This is correct you can always just re flash a rooted stock rom to get back to the ... rooted stock rom. since CM6 nightly is still a bit touch and go and probably not ready to be most peoples daily driver i would suggest doing this sooner rather then later so you have a fall back.
sablesurfer said:
Nandroid back up is everything....
Click to expand...
Click to collapse
This isnt exactly true. It does not back up radios, hboot, recovery. This usually isnt a big deal unless you are switching between roms using 1.47 and the older radios.
What i personally do is keep a fall back nandroid (or nand both same) of the stock rom as well as one for each rom i tend to play with (right now i have a cm6, dc3.5, and dc 3.2.3) this way i can easily restore to the roms i am playing with (cm6 dc 3.5) or back to my daily driver (dc 3,2,3) with out having to much of an issue.
Currently stock 2.2 (3.29x), odexed ROM, rooted.
Questions:
1) Would this allow me to manually deodex my phone:
http://www.droidxforums.com/forum/droid-x-themes/4620-how-manually-deodex-your-phone.html
2) If I made full backups using Titanium from my odexed, stock ROM, can I restore those apps and data back onto a deodexed ROM?
3) When I flash a new ROM, I gather most of them will wipe all the apps and files from my phone. Is that correct? Under what condition will a new ROM flash NOT wipe the data? RUUs? I'm asking because I know 3.30x is coming.
4) When someone takes the release OTA 3.3x, root it, and deodex it, can I flash it over my stock odexed ROM and not lose any apps/data, as well as have everything work?
Thank you!
Bump--will someone please provide some guidance?
Another question: If I restore apps and data from one phone to another, with both phones operating (using the same gmail account), will it cause a problem?
I was wondering if Android apps install with unique IDs that would cause confusion/conflict between devices.
Thanks.
Trying again in hopes that I get some answers, in particular, #1. If I can manually deodex my phone with the stock ROM, I won't have to rebuild everything.
Later, I presume, I can just update using a deodexed/rooted RUU without losing anything?
snovvman said:
Currently stock 2.2 (3.29x), odexed ROM, rooted.
Questions:
1) Would this allow me to manually deodex my phone:
http://www.droidxforums.com/forum/droid-x-themes/4620-how-manually-deodex-your-phone.html
2) If I made full backups using Titanium from my odexed, stock ROM, can I restore those apps and data back onto a deodexed ROM?
3) When I flash a new ROM, I gather most of them will wipe all the apps and files from my phone. Is that correct? Under what condition will a new ROM flash NOT wipe the data? RUUs? I'm asking because I know 3.30x is coming.
4) When someone takes the release OTA 3.3x, root it, and deodex it, can I flash it over my stock odexed ROM and not lose any apps/data, as well as have everything work?
Thank you!
Click to expand...
Click to collapse
1.) No, that was made for a different phone and if you try you will get bootloops.
http://forum.xda-developers.com/showthread.php?t=795104
2.) Yes. I've done it going from Stock 3.29 to Myn's rom.
3.) You can flash any rom over any other rom and retain your data.
It does however cause major compatibly problems as most roms are designed differently.
You can just flash over an updated version of the same rom though.
i.e. Going from version 1 to version 2 of the same rom.
Ruu's will wipe everything back to stock. (and un-root I think.)
and 3.30 won't be an OTA it is only being shipped on new phones because they have a different hardware that requires the changes in 3.30.
If everything is stock you should be able to flash it over your 3.29 rom.
4.) I am not sure on this. Just make a Nandroid backup and try it.
If it bootloops or doesn't work, just boot to recovery and restore you Nand.
Nandroid Backup before you attempt ANYTHING.
xNotta said:
1.) No, that was made for a different phone and if you try you will get bootloops.
http://forum.xda-developers.com/showthread.php?t=795104
2.) Yes. I've done it going from Stock 3.29 to Myn's rom.
3.) You can flash any rom over any other rom and retain your data.
It does however cause major compatibly problems as most roms are designed differently.
You can just flash over an updated version of the same rom though.
i.e. Going from version 1 to version 2 of the same rom.
Ruu's will wipe everything back to stock. (and un-root I think.)
and 3.30 won't be an OTA it is only being shipped on new phones because they have a different hardware that requires the changes in 3.30.
If everything is stock you should be able to flash it over your 3.29 rom.
4.) I am not sure on this. Just make a Nandroid backup and try it.
If it bootloops or doesn't work, just boot to recovery and restore you Nand.
Nandroid Backup before you attempt ANYTHING.
Click to expand...
Click to collapse
Thanks so much for your reply. I read your thread on #1, subscribed, in hoping that there may be a solution. I'm confused by your response #3, and how it relates to post #3 on the thread you cited. I thought I read that you wanted to manually deodex because you don't want to re-set thing up? If a ROM flash (not RUU) will simply overlay, why would you need to re-set thing up?
A couple of follow ups--If I make a full backup using Ti-Backup from an odexed/OE ROM, doesn't the odex files get backed up with it? So when I restore onto a deodexed ROM, wouldn't that cause a problem?
I'm in the same boat as you. I want to flash to the new 3.30 dodexed ROM so I can remove some taskbar icons (and get the newer ROM), but I don't want to re-setup everything I have done with my OE Evo ROM.
But, if I understand you, I CAN flash the 3.30/deodexed/rooted ROM over my OE 3.29 odexed ROM and everything will remain?
Thanks again! (and for the Nandroid reminder too)
Edit:
I see why this won't work--it's an RUU, therefore it will wipe?
[Supersonic RUU 3.30.651.2 | Kernel-Build149] - Flashable Zips - Odex and Deodex Ver.
snovvman said:
I thought I read that you wanted to manually deodex because you don't want to re-set thing up? If a ROM flash (not RUU) will simply overlay, why would you need to re-set thing up?
Click to expand...
Click to collapse
In theory flashing over a similar rom should not cause a problem since all the files are the same.
So if that's right, you wouldn't loose any of your settings since it would kind of be like an upgrade.
But that's a good point. I didn't even think to just flash a DeOdex'd version of the same rom over my Odex'd rom.
The thing that stopped me from successfully de-odexing my rom was the framework-res.apk, any modification of the .xml's in that file would prevent the phone from booting. So I don't know if that will cause a problem if you flash the De-Odex'd rom on top.
Titanium Backup(TiBu) actually restores everything like home screen layouts, ringtones and settings and the donate version has hypershell that makes it so you dont have to click install on every app.
snovvman said:
If I make a full backup using Ti-Backup from an odexed/OE ROM, doesn't the odex files get backed up with it? So when I restore onto a deodexed ROM, wouldn't that cause a problem?
Click to expand...
Click to collapse
I can't be completely sure, but I wouldn't try restoring system apps.
When I switched to a DeOdexed rom I went though every backup and didn't restore any of the system apps that would have still been Odex'd.
But I imagine TiBu would just replace those system files with the original Odex'd ones which kind of defeats the idea of DeOdex-ing, lol.
snovvman said:
But, if I understand you, I CAN flash the 3.30/deodexed/rooted ROM over my OE 3.29 odexed ROM and everything will remain?
Click to expand...
Click to collapse
I think if you do that you would end up with DeOdex'd system apps but you would have to go though and delete the .odex files from /system/apps/.
It might not even work flashing a DeOdex'd rom over an Odex'd rom.
If it does work, your data should still be there.
snovvman said:
I see why this won't work--it's an RUU, therefore it will wipe?
[Supersonic RUU 3.30.651.2 | Kernel-Build149] - Flashable Zips - Odex and Deodex Ver.
Click to expand...
Click to collapse
That is actually the rom extracted from the RUU.
So a wipe is probably recomended, but I don't think rom's touch the part of the phone where our settings are stored so it shouldn't wipe. (if it works)
http://shipped-roms.com/shipped/Supersonic/<-- that's the official RUU files, but they will reset your recovery back to stock and probably remove root.
That's going to be a really long post, haha. xD
Anyways, I would say do a Nandroid Backup or two (just in case) and wipe data, cache, and dalvik and flash the 3.30 rom .zip that was in the link you posted.
Then use TiBu to restore everything with the exception of the apps with red names, as those are system apps.
You need to restart you phone after TiBu finishes restoring.
You can always go back to your original nand backup if it doesn't work out.
I was reluctant to leave stock but once you try a better rom you wonder why you didn't switch earlier.
Hopefully someone with more experience can add to what I missed.
Thank you again for taking the time to reply.
Is it true that only system apps are odexed? What about market applications? I understand the concept of not restoring (via TiBu) system apps, but is it possible that there are other applications use the odex file?
I'm curious whether the state of odex/deodex is a system-wide property, where, if the system (phone) is deodexed, new installed are laid down as deodexed, and that would be the oppsite to be true for odexed phones?
When TiBu backs up an app that is odexed, does it backup both files and later try to restore both, even onto a deodexed system?
I presume it would be okay to restore "data only" on the system apps (going from odex to deodex)?
Lastly, not that I'd want to, I presume running deodexed precludes any possibility of OTA updates? Also, what about system app updates, like the recent Visual Voicemail update? Will it get installed as odexed because it is OE?
I feel totally comfortable flashing away on my evo knowing a backup will restore most anything. But I have zero comfort with my wife's epic.
If she hates a custom froyo rom with ext4, can clockwork restore back to her dl18 without issues? Im not sure what parts of memory are changed with these updates and if clockwork backs these up or not. Screwing up my phone is one thing, but I tread lightly with hers....married guys will understand
Yeah you'll be straight. In the Viperrom thread you will see the step by step for installing clock work mod 3 and flashing the rom. Of course you don't have to flash that particular rom. But when you're in cwm3 and about to convert to ext4 format (this is done before flashing the rom of choice assuming that rom runs on ext4) will be prompted to backup your data so you can restore if something goes wrong. Its really convenient because it backs up onto cwm so you can always just go into recovery mode if you need to restore
hdad2 said:
I feel totally comfortable flashing away on my evo knowing a backup will restore most anything. But I have zero comfort with my wife's epic.
If she hates a custom froyo rom with ext4, can clockwork restore back to her dl18 without issues? Im not sure what parts of memory are changed with these updates and if clockwork backs these up or not. Screwing up my phone is one thing, but I tread lightly with hers....married guys will understand
Click to expand...
Click to collapse
I'm not sure if Clockwork will revert back to RFS and DI18 but if anything you can just odin back to di18, 1click root/cwm , and then restore data.
JOLTnPEST said:
I'm not sure if Clockwork will revert back to RFS and DI18 but if anything you can just odin back to di18, 1click root/cwm , and then restore data.
Click to expand...
Click to collapse
Well it isn't CWM exactly. It's nandroid within CWM. It's no explicitly called nandroid when you're in CWM. It just says backup and restore. But if he follows the steps, and makes that backup before formatting to ext4, the name of the backed up file is called 'before ext4 formatting' or something like that so he knows exactly what that backup is.
Clockwork will not revert you back to RFS, and the stock ROM is not RFS-compatible. You will need to use Odin to revert back to stock. From there, you can restore your backup via CWM.
running_the_dream said:
Well it isn't CWM exactly. It's nandroid within CWM. It's no explicitly called nandroid when you're in CWM. It just says backup and restore. But if he follows the steps, and makes that backup before formatting to ext4, the name of the backed up file is called 'before ext4 formatting' or something like that so he knows exactly what that backup is.
Click to expand...
Click to collapse
Do NOT remove the original folder name. This will cause a md5 sum mismatch. You need the original folder name to prevent md5 mismatch
Tortel1210 said:
Do NOT remove the original folder name. This will cause a md5 sum mismatch. You need the original folder name to prevent md5 mismatch
Click to expand...
Click to collapse
What? I didn't say that he should change any names. The backup is given a name automatically when it's backed up. The name isn't just the date of the backup like most backups are. It's actually named 'before ext4 formatting' or something similar to that so that it's obvious and stands out.
running_the_dream said:
What? I didn't say that he should change any names. The backup is given a name automatically when it's backed up. The name isn't just the date of the backup like most backups are. It's actually named 'before ext4 formatting' or something similar to that so that it's obvious and stands out.
Click to expand...
Click to collapse
I didn't know we had cwm4. Did I miss something?
Sent From Da Hood.
You misread. I wrote ext4, not cwm4
mysteryemotionz said:
I didn't know we had cwm4. Did I miss something?
Sent From Da Hood.
Click to expand...
Click to collapse
I don't think you can make a backup on di18 and then update to froyo and if she doesn't like it just restore back to di18. Cwm does not restore kernels. I don't think that is possible.
You are correct
Sent From Da Hood.
What you want o do is get the nandroid backup on di18. If she doesn't like froyo with ext4 then odin back to di18, install root and cwm, and then do an advanced restore->restore data to restore her apps an settings.
Odin isn't as scary as it sounds. If you're computer runs the one click root and recovery, it should odin just fine.
Sent from my Epic Bonsai using XDA App
Thank you everyone. So it is like I feared. Nandroid will not restore with the file system change. I just have no comfort with this odin thing. I'll figure it out I guess. Enough instructions around here.
And none of the roms seem very solid. Not even sure which to flash. She just needs super stable. Her stock epic tends to hang on the lockscreen and phone app. Viper seems the most popular, but the first time she can't hear someone on the other end of the call, it'll be my fault . Any recommendations for super stability and decent battery?
Word on the street is Bonsai4All for stability. It's stock more or less with a couple baked in addons. I'm a Viper guy and haven't had any sort of phone issues like other users have reported.
hdad2 said:
Thank you everyone. So it is like I feared. Nandroid will not restore with the file system change. I just have no comfort with this odin thing. I'll figure it out I guess. Enough instructions around here.
And none of the roms seem very solid. Not even sure which to flash. She just needs super stable. Her stock epic tends to hang on the lockscreen and phone app. Viper seems the most popular, but the first time she can't hear someone on the other end of the call, it'll be my fault . Any recommendations for super stability and decent battery?
Click to expand...
Click to collapse
I'm on bonsai right now and it's very stable. A new release is getting ready to come out which is version 2 and I'm running it now and it's super stable. About the issue where she wouldn't be able to hear anything that is a dk28 thing. Not a rom thing. I personally have only had it happen to me a couple of tines but just toggle speakerphone on/off and it fixes it. Good luck.
So any current froyo rom will have this phone bug? Sucky. Here's hoping sprint let's froyo loose this week so the talented devs have a better base to work with!
Are we sure it is a dk28 thing and not a sprint thing? My centro used to drop audio too. Usually just hanging up and redialing fixes it.
Sent from my SPH-D700 using XDA App
Tortel1210 said:
Do NOT remove the original folder name. This will cause a md5 sum mismatch. You need the original folder name to prevent md5 mismatch
Click to expand...
Click to collapse
OMG- so this is why my backups usually give me a mismatch, and I end up re-doing everything manually! I've been renaming the folders to something meaningful, like "4-1-11 SFR110Vision11"
Holy crap.
crap crap crap.
All this time I've just been screwing myself!
Is there a way I can determine what the original folder name was??? to change it back?
[I'm going to post this as a new Q&A thread]
Never had a problem with not hearing a phone call, must be phone specific bug. I put Bonsai on my gf's Epic and she LOVES it! I learned through much trials and tribulation on how to restore my phone so I could do hers without getting any grief. Also CWM3 does save a backup to return to rfs before it converts to EXT4. I would root with CWM 2.5.1 and get Titanium and back everything up then Odin the EB13 prerooted with CWM3 found here:
http://forum.xda-developers.com/showthread.php?t=853209
And then Flash Bonsai 3.0.1 or 4.0.0 on it.
Agreed ^
My process is usually restore from CWM then restore apps from Titanium.
If Odin is necessary...then do that then restore from Titanium.
I had an idea, and wanted to run it by all the fine people here on XDA before proceeding.
As everyone knows, there was a press release yesterday informing us that the Telus Samsung Galaxy S 2 (T989D) model will be getting the ICS update right away, probably within the next couple weeks.
Currently, I am on the Stock Telus Gingerbread ROM that came with my phone, however, it is rooted and I have installed CWM recovery as well.
From my understanding, when ICS becomes available to download via Telus, I won't be able to upgrade since I am rooted.
In order to download the update I would have to remove root and also flash the stock Telus recovery through ODIN. Only problem with that is, there doesn't seem to be a flashable stock Telus recovery available, just a T-Mobile recovery.
This is what I was thinking of doing.
1. Make a nandroid, backup all my apps and data through Titanium Backup and also backup all my SMS/MMS and Call Logs with SMS Backup +.
2. Put my phone into download mode and go into ODIN and flash the following stock Telus ROM through the PDA option. http://forum.xda-developers.com/showthread.php?t=1350357 If everything goes well, I should have complete stock, no root and stock recovery.
3. Then I was going to use the ZergRush Exploit to re-root my phone http://forum.xda-developers.com/showthread.php?t=1321582 this should just give me root access but I would still have the stock recovery.
4. Go to the Market and download Titanium Backup and restore all my apps with data. Also, restore all my SMS and call logs through SMS Backup +
5. Then I would want to remove Root so I can proceed with the update to ICS. I could either go into Root Explorer or ES File Explorer and navigate to the following:
/system/bin/ then delete SU.
/system/xbin and delete SU
finally go into /system/app/ and delete Superuser.apk.
An alternative method would be to use the ZergRush unrooting script found here http://forum.xda-developers.com/showthread.php?p=18879974#post18879974 since I used ZergRush to Root originally.
If everything goes as planned I should now have my phone completely stock, no root, stock recovery and have all my apps back with data. Now, I know this seems like a long and tedious procedure, but would this technically work if I was to proceed?
I may just hold off on doing the update altogether and wait for one of the amazing Dev's to release their version of ICS. Although, I would like to experience the Stock ICS that Telus provides, since I really enjoy Telus Stock Gingerbread ROM (which is what I am currently running).
Thoughts, comments, they are all welcome. Thanks for listening.
99% of the time, there is a dev that provides the STOCK, rooted rom as a .zip. I could be wrong, but having gone through an HTC mt4g, sensation & still using the t989 & nexus, this is what goes on. However, you can just Odin back to stock & wait for the update as well...
Sent from my Galaxy Nexus using xda premium
cbutt said:
99% of the time, there is a dev that provides the STOCK, rooted rom as a .zip. I could be wrong, but having gone through an HTC mt4g, sensation & still using the t989 & nexus, this is what goes on. However, you can just Odin back to stock & wait for the update as well...
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Ya, that's what I was thinking as well. Hopefully our dev's can provide a complete stock but rooted ROM. The only stock rooted Telus ROM (for Gingerbread) that was available was slightly tweaked. Hopefully there will be one available that has no tweaks. Thank you for your response, much appreciated.
Chochiwpg said:
Ya, that's what I was thinking as well. Hopefully our dev's can provide a complete stock but rooted ROM. The only stock rooted Telus ROM (for Gingerbread) that was available was slightly tweaked. Hopefully there will be one available that has no tweaks. Thank you for your response, much appreciated.
Click to expand...
Click to collapse
You could easily flash back to stock and take the update, then root it yourself. It only takes a few minutes.
xcrazydx said:
You could easily flash back to stock and take the update, then root it yourself. It only takes a few minutes.
Click to expand...
Click to collapse
I was thinking about doing that, my concern is if I flash back to complete stock do I lose all my apps and data? I know I can re-download my apps again from the play store, but I would like to keep the data within those apps as well.
Or, when I flash back to complete stock are all my apps still in check because I wouldn't do a factory reset?
Chochiwpg said:
I was thinking about doing that, my concern is if I flash back to complete stock do I lose all my apps and data? I know I can re-download my apps again from the play store, but I would like to keep the data within those apps as well.
Or, when I flash back to complete stock are all my apps still in check because I wouldn't do a factory reset?
Click to expand...
Click to collapse
It will wipe all your apps and data. You can back that up via various apps like titanium and and a messaging backup, like backup to gmail or whatever you use.
xcrazydx said:
It will wipe all your apps and data. You can back that up via various apps like titanium and and a messaging backup, like backup to gmail or whatever you use.
Click to expand...
Click to collapse
Thank you. Yes, I know I can make the backups, and I would do that as well. But when you flash and go back to complete stock you lose root so I can't use titanium unless I re-route again.
that's why I was thinking about backing up first, flashing stock, then re-route with ZergRush (which won't touch the recovery). Reinstall all my apps with data and then remove root and wait for the update.
Logically to me this makes sense. I just don't know if technically it would work is all.
Chochiwpg said:
Thank you. Yes, I know I can make the backups, and I would do that as well. But when you flash and go back to complete stock you lose root so I can't use titanium unless I re-route again.
that's why I was thinking about backing up first, flashing stock, then re-route with ZergRush (which won't touch the recovery). Reinstall all my apps with data and then remove root and wait for the update.
Logically to me this makes sense. I just don't know if technically it would work is all.
Click to expand...
Click to collapse
What I'm saying is keep running whatever rom your on. Then back everything up when the official ics drops. Flash back to stock, Take the update, then root it. But migrating data from different OS's is generally not gonna be a good route to take. So, I would just start over anyway.
xcrazydx said:
What I'm saying is keep running whatever rom your on. Then back everything up when the official ics drops. Flash back to stock, Take the update, then root it. But migrating data from different OS's is generally not gonna be a good route to take. So, I would just start over anyway.
Click to expand...
Click to collapse
Ok, got ya. That makes sense and is probably what I am going to do. The data that I have saved in games isn't an issue, I don't really care about that. The info that I don't want to lose is in an Expense Manager application. that's the main one I don't want to lose the data. The text messages and call logs I can get back without issue and I can backup my pics and videos of my kids either to my computer manually or use Samsung Kies. So that's not an issue either.
Another question, just out of curiosity. Lets say someone didn't root their phone and received the OTA update. How would updating to ICS affect the apps already installed on their phone?
Chochiwpg said:
Ok, got ya. That makes sense and is probably what I am going to do. The data that I have saved in games isn't an issue, I don't really care about that. The info that I don't want to lose is in an Expense Manager application. that's the main one I don't want to lose the data. The text messages and call logs I can get back without issue and I can backup my pics and videos of my kids either to my computer manually or use Samsung Kies. So that's not an issue either.
Another question, just out of curiosity. Lets say someone didn't root their phone and received the OTA update. How would updating to ICS affect the apps already installed on their phone?
Click to expand...
Click to collapse
I believe it will wipe everything
You could backup your apps with an app that doesn't require root, such as my backup pro. That way you won't have an issue restoring after flashing back to stock.
Edit: never mind, still need root if you want to restore data.
Sent from my SGH-T989 using xda premium
Towle said:
You could backup your apps with an app that doesn't require root, such as my backup pro. That way you won't have an issue restoring after flashing back to stock.
Edit: never mind, still need root if you want to restore data.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
No problem. I think the only way is to backup, then flash stock, re root and install apps, then remove root. Or wait for a dev to release a stock rooted ICS ROM.
Chochiwpg said:
5. Then I would want to remove Root so I can proceed with the update to ICS. I could either go into Root Explorer or ES File Explorer and navigate to the following:
/system/bin/ then delete SU.
/system/xbin and delete SU
finally go into /system/app/ and delete Superuser.apk.
Click to expand...
Click to collapse
I've never really felt the need to unroot, but similar to Chochiwpg, I'm interested in receiving the stock Jelly Bean as soon as it's available, but don't want to have to flash stock ICS (and lose my apps and data) in the meantime. Will this unroot method do the trick? After that I can flash the stock recovery and be good to go with Kies for the update?
Thanks in advance for any advice.
I know a lot of people are coming from the EVO 3D...
Anyway i have a few question becuase im reading stuff about flashing issues...
I was about to flash a ICS ROM(Paranoid or CM9) and i read that i have to be carefull beacuse if i want to go back Nandroids will not work?
Well how do i make a Nandroid that works? I read that the only way to go back is flashing Stock via Odin(Im i wrong?)
I just finish the rooting process and im ready to install ICS ROM.
In the evo way, only thing i need it to do was nandroid, wipe, install from zip, DONE.
Thanks guys!
rockypr said:
I know a lot of people are coming from the EVO 3D...
Anyway i have a few question becuase im reading stuff about flashing issues...
I was about to flash a ICS ROM(Paranoid or CM9) and i read that i have to be carefull beacuse if i want to go back Nandroids will not work?
Well how do i make a Nandroid that works? I read that the only way to go back is flashing Stock via Odin(Im i wrong?)
I just finish the rooting process and im ready to install ICS ROM.
In the evo way, only thing i need it to do was nandroid, wipe, install from zip, DONE.
Thanks guys!
Click to expand...
Click to collapse
Basically make a nandroid with GB recovery the flash ics. If you want to restore Odin GB rom then nandroid restore.
Every rom should have instructions and as long as they are followed you should be safe.
Look up sfhub (I think) and agats custom recovery threads for more info.
Happy independence day!
Sent from my SPH-D710 using Tapatalk 2
rockypr said:
I know a lot of people are coming from the EVO 3D...
Anyway i have a few question becuase im reading stuff about flashing issues...
I was about to flash a ICS ROM(Paranoid or CM9) and i read that i have to be carefull beacuse if i want to go back Nandroids will not work?
Well how do i make a Nandroid that works? I read that the only way to go back is flashing Stock via Odin(Im i wrong?)
I just finish the rooting process and im ready to install ICS ROM.
In the evo way, only thing i need it to do was nandroid, wipe, install from zip, DONE.
Thanks guys!
Click to expand...
Click to collapse
Nandroids are perfectly safe, the only time when they're not safe, is when you make/restore from one on ICS.
The problem with all these ICS leaks, is a bug plaguing the emmc, which I believe that some methods of using ICS recoveries makes it wipe or something. Point is, it causes a brick. Here is the method that I use when flashing ICS, which works for most ICS ROMs, as most ICS ROMs need an EL26/EL29 framework. Pretty sure Paranoidandroid recommends this method, too.
Download these drivers
Download this: OC ODIN File for EL26 and this: E4GT Root Utility
Using Titanium Backup, make a backup of all your stuff, or use your preferred back-upper, just not nandroid. I recommend buying the Pro version, because it will save you so many times, and the dev is great. It's a little expensive though for an app.
OC Odin back to EL26. The good thing about this is, the process is straight forward, and doesn't add to your flash counter, and does not yellow triangle either.
Open up e4gtauto-sfx.exe, option C, then I. This gives you CWM, And just in case, I do not recommend using other than standard CWM to flash ICS roms. but that's me.
When your phone reboots, it should have CWM, and be rooted, just load up the flashing files onto your sd card, load up CWM, do 1 system data wipe, and flash the files in the order they have to be flashed.
Also, really important, DO NOT DIRECTLY RESTORE FROM A NANDROID You will most likely cause a brick if you do.
If you want to go back to GB, you have to Odin back to GB, and THEN you can perform the Nandroid Restore.
F3L1XZS said:
Nandroids are perfectly safe, the only time when they're not safe, is when you make/restore from one on ICS.
The problem with all these ICS leaks, is a bug plaguing the emmc, which I believe that some methods of using ICS recoveries makes it wipe or something. Point is, it causes a brick. Here is the method that I use when flashing ICS, which works for most ICS ROMs, as most ICS ROMs need an EL26/EL29 framework. Pretty sure Paranoidandroid recommends this method, too.
Download these drivers
Download this: OC ODIN File for EL26 and this: E4GT Root Utility
Using Titanium Backup, make a backup of all your stuff, or use your preferred back-upper, just not nandroid. I recommend buying the Pro version, because it will save you so many times, and the dev is great. It's a little expensive though for an app.
OC Odin back to EL26. The good thing about this is, the process is straight forward, and doesn't add to your flash counter, and does not yellow triangle either.
Open up e4gtauto-sfx.exe, option C, then I. This gives you CWM, And just in case, I do not recommend using other than standard CWM to flash ICS roms. but that's me.
When your phone reboots, it should have CWM, and be rooted, just load up the flashing files onto your sd card, load up CWM, do 1 system data wipe, and flash the files in the order they have to be flashed.
Also, really important, DO NOT DIRECTLY RESTORE FROM A NANDROID You will most likely cause a brick if you do.
If you want to go back to GB, you have to Odin back to GB, and THEN you can perform the Nandroid Restore.
Click to expand...
Click to collapse
Great info THANKS!!!!...
Also there is no problem to flash that EL26 file? when my stock is el29?
rockypr said:
Great info THANKS!!!!...
Also there is no problem to flash that EL26 file? when my stock is el29?
Click to expand...
Click to collapse
For OC ODIN, you don't have to worry about flashing, just plug your phone into the computer once you have the program running, an the drivers, and you'll be fine.
And yeah, you can go back using ODIN.
You just shouldn't use CWM to flash an older version of something if you're on the newer version.
So if install ICS and I want to return to GB the safe thing to do is run Odin back to stock rooted then Nandroid Restore?
Sent from my iPad using Tapatalk HD
rockypr said:
So if install ICS and I want to return to GB the safe thing to do is run Odin back to stock rooted then Nandroid Restore?
Sent from my iPad using Tapatalk HD
Click to expand...
Click to collapse
That is correct.
Sent from my Thuggin Azz 4G Touch