Related
Anyone know how to go about this on my GSII?
Planning on flashing to Stock and would prefer a fresh start, would just flashing the firmware be sufficient?
I do remember seeing a reset option when pressing power+home+vol down on start. Would ideally like everything to go back to factory and all data deleted, basically factory fresh.
Thanks Guys.
Chronicles404 said:
Anyone know how to go about this on my GSII?
Planning on flashing to Stock and would prefer a fresh start, would just flashing the firmware be sufficient?
I do remember seeing a reset option when pressing power+home+vol down on start. Would ideally like everything to go back to factory and all data deleted, basically factory fresh.
Thanks Guys.
Click to expand...
Click to collapse
Have you rooted and flashed anything or changed anything on /system?
If not, the reset option in recovery would be fine.
If you have, you would need to reflash.
pulser_g2 said:
Have you rooted and flashed anything or changed anything on /system?
If not, the reset option in recovery would be fine.
If you have, you would need to reflash.
Click to expand...
Click to collapse
Thanks for the prompt reply.
Rooted yes, though not sure if anything is changed on/system as a result (I personally haven't).
I've an O2 Handest so would like to unbrand, hence I would be flashing to the actual stock Rom so I'm assuming I would need to Root again anyhow?
Just wondering If I would need to reset then flash, or would flash be sufficient and get rid of everything in the process?
A flash should be enough to clear out anything left behind.
You would obviously flash the O2 UK firmware, and you would want to reset the download mode counter (see the dev section) before you presented it as an "untouched" phone
Can someone who knows explain the specifics about what happens to the phone during a flash, hard reset, etc.?
Specifically, what I'm asking is this: I know that flashing replaces your ROM, obviously, but what I'm asking is related to what happens on a lower level.
When, for example, one flashes a ROM that has mods, etc. all those mods (as part of the flashed ROM) are written from where to where on a hard reset or factory reset?
I don't really understand where the ROM software is stored on the partitions and I'd like to have a better understanding of that.
Restoring from a NAND backup rewrites what data?
Anyone?
can't really help you with partitions.. I did read it somewhere but can't recall of the top of my head..try a search on the original dev forum.
but if u open where the nadroid backup is located, most likely inside the clockworkmod folder, u'll have some of ur questions answered...
btw, when u do a data wipe in cwm recovery, it tells you which folders/partitions gets formatted..
I have a Samsung Transform Ultra (rooted), I am using the stock ROM that came with the phone, recently I have corrupted something and need to attempt a factory reset, however some people have said that doing a factory reset on a rooted phone could brick it, so this brings a couple of questions:
1.- How would I un-root my phone, or, if un-rooting is not necessary, what steps should I take to factory reset it safely? My data is safely backed up already.
2.- Has anyone done a factory reset on a rooted Transform Ultra?
Any help would be most appreciated.
The4thDoctor said:
I have a Samsung Transform Ultra (rooted), I am using the stock ROM that came with the phone, recently I have corrupted something and need to attempt a factory reset, however some people have said that doing a factory reset on a rooted phone could brick it, so this brings a couple of questions:
1.- How would I un-root my phone, or, if un-rooting is not necessary, what steps should I take to factory reset it safely? My data is safely backed up already.
2.- Has anyone done a factory reset on a rooted Transform Ultra?
Any help would be most appreciated.
Click to expand...
Click to collapse
Don't you have a custom Recovery installed? I don't know about this device specifically, but there should be a factory reset option you can utilize within your Recovery image. You'll need a ROM to flash afterwards also, otherwise you'll have no OS on your device. Or simply flash a NANDroid backup.
Sent from my HTC Vision using XDA App
Since my (rooted) phone has the stock factory ROM only, and I never changed it, do I still need a ROM? My original ROM was never removed or changed.
The4thDoctor said:
Since my (rooted) phone has the stock factory ROM only, and I never changed it, do I still need a ROM? My original ROM was never removed or changed.
Click to expand...
Click to collapse
Well that's the thing, when you factory reset a rooted phone it wipes everything, including the OS. So after a factory reset there will be no ROM to boot into. Even though you've never changed it and you're running stock, you'd still need a copy of that stock ROM (if you wanted to continue running stock). But if you've made a nandroid backup (complete snapshot of your entire system) at some point before you noticed the current problem you're having, it might be easier to simply restore that particular backup via Recovery.
I never flashed any roms or recovery, just rooted.
Unfortunately, I never made a nandroid backup before I had this problem, however, my daughter has an identical phone, could I make such a backup from hers, and use it on my phone, then just delete her settings etc?
I had no idea that just rooting would kill the stock ROM image, making the phone un-recoverable, I thought that rooting only gave me superuser permissions.
The4thDoctor said:
I never flashed any roms or recovery, just rooted.
Unfortunately, I never made a nandroid backup before I had this problem, however, my daughter has an identical phone, could I make such a backup from hers, and use it on my phone, then just delete her settings etc?
I had no idea that just rooting would kill the stock ROM image, making the phone un-recoverable, I thought that rooting only gave me superuser permissions.
Click to expand...
Click to collapse
Looks like Clockworkmod doesn't support your device.... not sure what custom Recoveries are available for your phone... but rooting doesn't mess up the stock ROM, we (the users) mess up our ROMs. You're right when you said that rooting gives you superuser privileges, and with those privileges come the unfortunate ability to screws stuff up. In my case I have tons of backups and a custom Recovery whereby I can wipe the phone and restore if need be. I also have ADB installed and can use Fastboot commands if things go sideways. Basically if you're gonna root have a backup plan.
Can you perhaps follow an unrooting method? Then you could safely factory reset without losing the OS... you know...the more I think about this, the more I wonder if you could just use the factory reset option from within the phone's settings... on a custom ROM you'd never do it, but in your situation (no custom recovery or ROM) who knows, maybe it would work with a problem.... I'll ask a friend of mine and post back.
Edit: Never heard back, but in your case on the stock ROM without a custom Recovery you *should* be able to factory reset through the Privacy setting section of your settings. If you do lose root, simply re root and you're good to go.
Thanks, Well I am going to give it a try and see what happens, worst case, I will have to buy another phone.
EDIT: I had no problems with factory reset, thank you!
Hi all,
I have a Droid incredible 4g (stock, unrooted/unlocked, w/ the recent OTA update). I saw the Bootloader Unlock exploit in the developer's forum so I gave it a go, and it worked fine. Then I installed the Viper 1.0 ROM, but I haven't been able to get it to do anything after successfully booting except run through a loop of errors such as "Unfortunately, the process android.process.acore has stopped working." After I click "OK" on about 10 critical errors, it self-reboots and does the whole thing again.
Unfortunately, I didn't do a backup this time, so I have nothing to restore (first time I haven't done a backup, but also the first time I've ever had any kind of an issue w/ a ROM). I tried using the HTC Android ROM Update Utility 1.0.5.2011 that I found in the dev forum, but that didn't work either. Finally, I installed 2.17.605.2 Verizon Global Sense4.1 Android 4.0.4. It's a lot more stable than Viper was and the phone is basically usable, but I still get lots of critical errors. So this morning I went back to the forum and saw that I needed to downgrade to the old 1.43.605.3 kernel. I tried that and then reinstalled Viper 1.0, but it seemed to have no effect--still stuck in a critical error/reboot loop.
I realize that's the risk of playing with ROMs and I should have done a backup, but anyone have any ideas on how I can get my phone back and running?
Thanks!
Even though it explicitly stated you didn't need to do a backup, I did one anyway, to prevent something like this from happening. Always do a backup.
Did you verify the MD5Sum of ViperLTE?
Did you go to Recovery and Wipe -> Factory Reset and Wipe -> System both twice before trying to install the ROM?
Did you change anything in the ROM before attempting to load it?
There are lots of questions we could ask to ascertain the root of the problem, but these three are among the most important.
Wi-Fi won't work without the old boot.img, and from what I can tell, that's the only thing. It doesn't give critical errors.
I'm thinking since you are new to root you were un-aware the need to wipe before installing a rom.
im thinking that is the issue.
Thanks for the reply!
I didn't check the MD5 last night but I did just now and it matches.
I did a cache wipe the first time but not a system wipe. Then I started getting more desperate and tried reinstalling w/ system wipes and factory resets, but it didn't change anything.
No, I didn't change the ROM. Doing the Bootloader unlock exploit was about the absolute maximum of my technical abilities! The only thing I know I did wrong was that I didn't downgrade to the old boot version the first time (mainly because the wifi thing sounded inconsequential and I didn't want to learn the procedure if I didn't have to).
Anyway, I just tried Ultimate KangBang and it seems to work--no error messages so far. I don't know what I did wrong, but hopefully this keeps working!
IceDragon59 said:
Even though it explicitly stated you didn't need to do a backup, I did one anyway, to prevent something like this from happening. Always do a backup.
Did you verify the MD5Sum of ViperLTE?
Did you go to Recovery and Wipe -> Factory Reset and Wipe -> System both twice before trying to install the ROM?
Did you change anything in the ROM before attempting to load it?
There are lots of questions we could ask to ascertain the root of the problem, but these three are among the most important.
Wi-Fi won't work without the old boot.img, and from what I can tell, that's the only thing. It doesn't give critical errors.
Click to expand...
Click to collapse
andybones said:
I'm thinking since you are new to root you were un-aware the need to wipe before installing a rom.
im thinking that is the issue.
Click to expand...
Click to collapse
Yes, I took a short-cut that didn't quite work out. I didn't want to wipe the system because I wasn't sure if my pictures would be wiped too, but then when everything died I tried wiping everything and reinstalling and it didn't seem to improve anything. I did end up losing my pictures too. Oh well. Maybe it's just a combination of stuff I did to try to get things working (there was some trial and error in unlocking the bootloader but I did get that to work finally, and then more trial and error with the ROMs).
I guess the best thing to do is leave the phone the heck alone as long as it's working, for now. I just don't know why nothing seemed to work--I thought factory reset/fresh ROM would do it.
franklin411 said:
Yes, I took a short-cut that didn't quite work out. I didn't want to wipe the system because I wasn't sure if my pictures would be wiped too, but then when everything died I tried wiping everything and reinstalling and it didn't seem to improve anything. I did end up losing my pictures too. Oh well. Maybe it's just a combination of stuff I did to try to get things working (there was some trial and error in unlocking the bootloader but I did get that to work finally, and then more trial and error with the ROMs).
I guess the best thing to do is leave the phone the heck alone as long as it's working, for now. I just don't know why nothing seemed to work--I thought factory reset/fresh ROM would do it.
Click to expand...
Click to collapse
If UKB ROM works then Viper ROM will too, installing the boot.img is very simple it's one command
I can help you with that if you'd like
in recovery before installing ROM, do a wipe of, (I go in this order, but it doesn't matter.)
1) Factory Reset
2) System
3) Cache
4) Dalvik Cache
then install the ROM
just DO NOT do External storage (unless of coarse u WANT to wipe your SD-Card.)
as long as you don't wipe External Storage you won't lose anything that's on your SD-Card.
in the future it is always good practice to backup(nandroid) your current ROM. I have been burned too many times, always do a nandroid before you do anything in recovery.
your photos are normally saved to the SD, flashing ROMs or wiping the system will not delete them
andybones said:
If UKB ROM works then Viper ROM will too, installing the boot.img is very simple it's one command
I can help you with that if you'd like
in recovery before installing ROM, do a wipe of, (I go in this order, but it doesn't matter.)
1) Factory Reset
2) System
3) Cache
4) Dalvik Cache
then install the ROM
just DO NOT do External storage (unless of coarse u WANT to wipe your SD-Card.)
as long as you don't wipe External Storage you won't lose anything that's on your SD-Card.
Click to expand...
Click to collapse
It worked this time! Maybe the difference was that the boot.img file I downloaded was called "boot_signed.img" or something. I had no idea what it was supposed to look like, so I installed it that way and it didn't work. Then I tried renaming it to "boot.img" this morning and installing viper, but that didn't work. And then I restarted and installed UKB, and it worked. Just now I wiped and tried again with Viper and it's working fine. Maybe I did something this morning that caused it not to take properly when I tried with Viper, and then I reset and it worked.
Thanks for the help!
franklin411 said:
It worked this time! Maybe the difference was that the boot.img file I downloaded was called "boot_signed.img" or something. I had no idea what it was supposed to look like, so I installed it that way and it didn't work. Then I tried renaming it to "boot.img" this morning and installing viper, but that didn't work. And then I restarted and installed UKB, and it worked. Just now I wiped and tried again with Viper and it's working fine. Maybe I did something this morning that caused it not to take properly when I tried with Viper, and then I reset and it worked.
Thanks for the help!
Click to expand...
Click to collapse
na the name has nothing to do with it. it can be named whatever.
im guessing the wipe worked.
franklin411 said:
Hi all,
I have a Droid incredible 4g (stock, unrooted/unlocked, w/ the recent OTA update). I saw the Bootloader Unlock exploit in the developer's forum so I gave it a go, and it worked fine. Then I installed the Viper 1.0 ROM, but I haven't been able to get it to do anything after successfully booting except run through a loop of errors such as "Unfortunately, the process android.process.acore has stopped working." After I click "OK" on about 10 critical errors, it self-reboots and does the whole thing again.
Unfortunately, I didn't do a backup this time, so I have nothing to restore (first time I haven't done a backup, but also the first time I've ever had any kind of an issue w/ a ROM). I tried using the HTC Android ROM Update Utility 1.0.5.2011 that I found in the dev forum, but that didn't work either. Finally, I installed 2.17.605.2 Verizon Global Sense4.1 Android 4.0.4. It's a lot more stable than Viper was and the phone is basically usable, but I still get lots of critical errors. So this morning I went back to the forum and saw that I needed to downgrade to the old 1.43.605.3 kernel. I tried that and then reinstalled Viper 1.0, but it seemed to have no effect--still stuck in a critical error/reboot loop.
I realize that's the risk of playing with ROMs and I should have done a backup, but anyone have any ideas on how I can get my phone back and running?
Thanks!
Click to expand...
Click to collapse
weird, i was having the same problem with the same processes stopped working. i wiped cache dalvik and system but not factory reset. once i factory reset, it worked fine. i figured a system wipe would have been enough....
Forgive my novice status with both my first Android phone and this site. Galaxy S6 which I rooted using Odin and I believe a kernel it was, from here.
If I run the os upgrade from Smartswitch, what effect will that have one the phone as far as being rooted and all the stuff I've done since being rooted. Thank you very much.
If you update, you will lose root. I would not update via Smart Switch, being that you are rooted with a custom kernel. Your best bet would be to update via Odin. Check the subforum here @ xda for your variant of the S6 for further info. You should find what you need in the General forum of that subforum.
es0tericcha0s said:
If you update, you will lose root. I would not update via Smart Switch, being that you are rooted with a custom kernel. Your best bet would be to update via Odin. Check the subforum here @ xda for your variant of the S6 for further info. You should find what you need in the General forum of that subforum.
Click to expand...
Click to collapse
Thank you sir. Is it simply a matter rerooting the device? Or will every other change I made from root be gone too?
It will wipe your phone, so you will have to redo any mods or settings.
es0tericcha0s said:
It will wipe your phone, so you will have to redo any mods or settings.
Click to expand...
Click to collapse
It wipes the phone every time you do an operating system update? Why would anybody ever do it unless something wasn't working? Unless it's only when rooted? I have good pc skills and some understanding of Linux even, but man I have a lot to learn about these phones.. What about Smart Switch backups? It wipes the phone, how close to before the update will that get somebody? I don't have time to research all this. I may just leave it. This update I'm talking about is a gigabyte btw. That seems pretty huge for a phone.
It wipes the phone when you update via Odin (unless modded by a dev to not wipe for some versions). The reason that this needs to be done is that when you are rooted and have changed system files, OTA updates usually cause issues like bootloops / soft brick. Typically when you have a Samsung with a modded kernel and system, the regular Samsung tools like Kies and Smart Switch fail. Your results may vary, but I would have the firmware downloaded to reload via Odin in case that does not work. I am not familar with Smart Switch as it just came out for the S6 and newer stuff and I have never had use for Samsung's tools like that because I prefer to use Google and Titanium Backup to backup and restore my apps, contacts, texts, call logs, etc. As far as the updates go, 1 GB is actually kind of small for newer versions. It's probably bigger once unzipped. Some newer phones have systems that are well over 2 GBs. Most people here usually update via custom rom as it's easy to do on the phone once you have a working custom recovery and doing a factory reset there will not wipe the internal storage @ /data/media. If you prefer to be stock rooted, there most likely is a version already posted in the subforum for your phone. If you are updating whole Android versions and not minor updates, it might be required to install additional firmware files with Odin or Chainfire's Flashfire tool. If so, the developer will mention that in the OP of the thread.
es0tericcha0s said:
It wipes the phone when you update via Odin (unless modded by a dev to not wipe for some versions). The reason that this needs to be done is that when you are rooted and have changed system files, OTA updates usually cause issues like bootloops / soft brick. Typically when you have a Samsung with a modded kernel and system, the regular Samsung tools like Kies and Smart Switch fail. Your results may vary, but I would have the firmware downloaded to reload via Odin in case that does not work. I am not familar with Smart Switch as it just came out for the S6 and newer stuff and I have never had use for Samsung's tools like that because I prefer to use Google and Titanium Backup to backup and restore my apps, contacts, texts, call logs, etc. As far as the updates go, 1 GB is actually kind of small for newer versions. It's probably bigger once unzipped. Some newer phones have systems that are well over 2 GBs. Most people here usually update via custom rom as it's easy to do on the phone once you have a working custom recovery and doing a factory reset there will not wipe the internal storage @ /data/media. If you prefer to be stock rooted, there most likely is a version already posted in the subforum for your phone. If you are updating whole Android versions and not minor updates, it might be required to install additional firmware files with Odin or Chainfire's Flashfire tool. If so, the developer will mention that in the OP of the thread.
Click to expand...
Click to collapse
It just occurred to me. Firmware IS the Android OS on these phones. That's not the same as a kernel though? With the regular Linux os it isn't. Forgive my ignorance. Like I say this is my first one.
Unfortunalely, firmware is one of those terms that can mean a few different things depending on the situation (like flashing). Firmware in this instance refers to the bootloader and modem files as well for Samsungs. If you don't have the bootloader and modem files (which roms do not install) correctly matched to the OS then you might have issues like not being able to boot or cell service issues.
es0tericcha0s said:
It wipes the phone when you update via Odin (unless modded by a dev to not wipe for some versions). The reason that this needs to be done is that when you are rooted and have changed system files, OTA updates usually cause issues like bootloops / soft brick. Typically when you have a Samsung with a modded kernel and system, the regular Samsung tools like Kies and Smart Switch fail. Your results may vary, but I would have the firmware downloaded to reload via Odin in case that does not work. I am not familar with Smart Switch as it just came out for the S6 and newer stuff and I have never had use for Samsung's tools like that because I prefer to use Google and Titanium Backup to backup and restore my apps, contacts, texts, call logs, etc. As far as the updates go, 1 GB is actually kind of small for newer versions. It's probably bigger once unzipped. Some newer phones have systems that are well over 2 GBs. Most people here usually update via custom rom as it's easy to do on the phone once you have a working custom recovery and doing a factory reset there will not wipe the internal storage @ /data/media. If you prefer to be stock rooted, there most likely is a version already posted in the subforum for your phone. If you are updating whole Android versions and not minor updates, it might be required to install additional firmware files with Odin or Chainfire's Flashfire tool. If so, the developer will mention that in the OP of the thread.
Click to expand...
Click to collapse
What I'm wondering is if there's any to have this galaxy s6 just like it is now after many hours of tweaking after one of these updates. I couldn't make heads or tails out of Titanium update.
You are being very helpful sir. Thank you.
Depends on what tweaks you've done and which update that it is. If it is a minor security update, then usually someone will post a flashable via custom recovery version and often you can get away with installing that over your current system while just wiping cache and dalvik cache. If it is a major update, like when Marshmallow comes out, it would benefit you to do a factory reset before updating. Yea, it sucks having to set up your phone again, though with all the tools available, it's really not that bad, but better to start fresh instead of wondering if the phone is slow or buggy because you didn't.
es0tericcha0s said:
Depends on what tweaks you've done and which update that it is. If it is a minor security update, then usually someone will post a flashable via custom recovery version and often you can get away with installing that over your current system while just wiping cache and dalvik cache. If it is a major update, like when Marshmallow comes out, it would benefit you to do a factory reset before updating. Yea, it sucks having to set up your phone again, though with all the tools available, it's really not that bad, but better to start fresh instead of wondering if the phone is slow or buggy because you didn't.
Click to expand...
Click to collapse
You're making sense. I totally get it. (about starting from scratch) Can I then re-root it with the same UniKernel-v5-920P-072715.tar as before or will I need a new one of those too.? Thanks again.
This is the update SmartSwitch is telling me is available. I don't even know which of this stuff we've been discussing this is. Firmware, ROM or OS update.
Current version: PDA:0H1 / CSC:0H1/ PHONE:0H1 (SPR)
Latest version: PDA:011 / CSC:011 / PHONE:011 (SPR)
Size: 1612 MB
That's just a minor security update. I would not use that kernel to reroot. I believe the only option available for the update you are on and the update that is available is via TWRP + SuperSU zip.
es0tericcha0s said:
That's just a minor security update. I would not use that kernel to reroot. I believe the only option available for the update you are on and the update that is available is via TWRP + SuperSU zip.
Click to expand...
Click to collapse
Whatsa TWRP + SuperSU zip Is that a tool and file for getting this update?
Sorry man. I've had this phone for less than 2 months and it's my very first one.
I do appreciate your patience. I've been a PC support guy for 16 years. I know what it's like.
TWRP = Team Win Recovery Project. It replaces the stock recovery that the phone uses to perform factory resets and updates signed by Samsung. This allows you multiple benefits such as complete system/data/kernel backups, being able to wipe any combo of system/data/caches/internal storage, factory data reset without wiping internal storage, terminal commands, and installing custom files, roms, mods, etc not signed by Samsung to name a few. SuperSU is the popular root binary and root permissions app made by the developer Chainfire. If you needs links, I can provide, but assuming you're familiar with Googling things being a support guy. ☺
es0tericcha0s said:
TWRP = Team Win Recovery Project. It replaces the stock recovery that the phone uses to perform factory resets and updates signed by Samsung. This allows you multiple benefits such as complete system/data/kernel backups, being able to wipe any combo of system/data/caches/internal storage, factory data reset without wiping internal storage, terminal commands, and installing custom files, roms, mods, etc not signed by Samsung to name a few. SuperSU is the popular root binary and root permissions app made by the developer Chainfire. If you needs links, I can provide, but assuming you're familiar with Googling things being a support guy.
Click to expand...
Click to collapse
I have SuperSU already.
These are some truly terrible directions unless you already know enough to not need them.
https://twrp.me/devices/samsunggalaxys6sprint.html
Will installing TWRP effect the root method I've already used?
Will installing recovery effect any of the multitude of configurations I've already done?
Does this then allow manual installs of OTA updates without losing root or any of your configuration customizations?
Is it JUST the recovery partition were dealing which stands alone from the os?
Does Nandroid backup then encompass the recovery and os and rom etc? Meaning are they all backed up and custom recovery via TWRP was what made that possible? Or do you have to make your current config the recovery itself in order to do a ghost style backup and restore if you jack yourself up later? OR is not even this a ghost style restore?
Maybe it's just me, but the terminology is very confusing and I can't make heads or tails of what I'm even talking about with all this.
Tried to make backup with TWRP...
I guess whatever I flashed it with last time won't let it boot into recovery or the bootloader or whatever it's called. If I tell TWRP manager to reboot and do backup it just goes to the menu for rebooting and wiping cache etc. If I specifically go to "reboot to bootloader" it just reboots into android. I went to install a custom recovery and it said that if the location for the recovery is wrong it could brick the phone. I have no idea if it's right or wrong or if the root method I've already used is effecting this or not.
Installing a custom recovery will not affect your OS or any settings (as long as the recovery version is compatible with your phone and update). It is installed in a different partition than where the OS resides. It will not let you install official OTA zips. It is only for installing files not directly signed with Samsung's special key. When you do a nandroid backup, it will give you options on which parts of the phone you would like to backup. The important ones are boot, system, data, and EFS (though this is not typically needed when you restore, just as a precaution because it holds important data and settings of your IMEI and such - only restore if needed). Boot is the kernel, which controls many drivers for stuff like wifi, BT, CPU and GPU processes as well as others. System contains preloaded software, as in if you just restored boot and system, it would be like you factory reset the device and would need to setup your accounts and settings. Data is the apps, data, settings you have changed or added. A factory reset in the stock recovery would also wipe your /data/media storage which your phone sees as your internal storage. TWRP allows a factory reset that skips this so you will not lose the stuff you have accumulated on the phone such as pictures, music, downloads, etc.
The reason that when you are using TWRP Manager to install the recovery and reboot to it and it is still stock is probably due to the system has a script built in that notices if you change the recovery and will rewrite the stock recovery back to it upon rebooting. You can avoid this by renaming the script with a root enabled file browser. You will find this script in /system/etc/install-recovery.sh (or something similar). Just rename it to something like install-recovery.sh.bak.
es0tericcha0s said:
Installing a custom recovery will not affect your OS or any settings (as long as the recovery version is compatible with your phone and update). It is installed in a different partition than where the OS resides. It will not let you install official OTA zips. It is only for installing files not directly signed with Samsung's special key. When you do a nandroid backup, it will give you options on which parts of the phone you would like to backup. The important ones are boot, system, data, and EFS (though this is not typically needed when you restore, just as a precaution because it holds important data and settings of your IMEI and such - only restore if needed). Boot is the kernel, which controls many drivers for stuff like wifi, BT, CPU and GPU processes as well as others. System contains preloaded software, as in if you just restored boot and system, it would be like you factory reset the device and would need to setup your accounts and settings. Data is the apps, data, settings you have changed or added. A factory reset in the stock recovery would also wipe your /data/media storage which your phone sees as your internal storage. TWRP allows a factory reset that skips this so you will not lose the stuff you have accumulated on the phone such as pictures, music, downloads, etc.
The reason that when you are using TWRP Manager to install the recovery and reboot to it and it is still stock is probably due to the system has a script built in that notices if you change the recovery and will rewrite the stock recovery back to it upon rebooting. You can avoid this by renaming the script with a root enabled file browser. You will find this script in /system/etc/install-recovery.sh (or something similar). Just rename it to something like install-recovery.sh.bak.
Click to expand...
Click to collapse
You sir, are one patient and helpful man I very much appreciate your suffering through my whining. Interestingly, the boot loop just stopped in it's own and now I have the TWRP interface in place of the stock menu where the option was to wipe the cache partition.
Does this THIS mean I have a custom recovery now? Meaning, a different restore image than the one that came with the phone? Or does this now let me install that?
About this....
You were saying up HERE that if I run this update with smart switch I would lose root, but if I use TWRP to do it, I won't? Is that right? Thanks again.
Tiribulus said:
You sir, are one patient and helpful man I very much appreciate your suffering through my whining. Interestingly, the boot loop just stopped in it's own and now I have the TWRP interface in place of the stock menu where the option was to wipe the cache partition.
Does this THIS mean I have a custom recovery now? Meaning, a different restore image than the one that came with the phone? Or does this now let me install that?
Click to expand...
Click to collapse
This should mean that the recovery is installed. You can verify by using the app to boot to recovery or via powering the phone on by holding the Power, Volume Up, and Home buttons together as you restart. You should notice a recovery booting message in the top left and then you can let go of the buttons. Once there, you should perform a backup of the boot, system, and data partitions. If you have an EFS option, I would back that up too for safe keeping. It's rare that it would get corrupted, but best to have a backup just in cause.
If you update via Smart Switch, you will definitely lose root, as well as TWRP. Most likely, a developer has posted a rooted version of the update that you can use TWRP to install.
So I was looking into this a little closer for you and realized that the preferred method of updating and rooting the update you are trying to get involves using Odin to install the full update package, then reflashing TWRP, and using a newer version of the kernel to root. However, from some of the user comments about it, it seems like it might be better to wait till Samsung has released the source code of the kernel for the OI1 update. The kernels based on the slightly older 5.1.1 builds will work, but some people were experiencing random issues such as reboots or other oddities. I don't think OI1 has anything in it that would be worth losing root over or possibly having things run oddly. The alternative would be to update via a rom like this http://forum.xda-developers.com/spr...ment/ram9200-ofe-rom-thread-v3-5-1-1-t3173417