Hello,
I rooted my ATT SG2 some time ago and i tried a few of the popular ROMs. After trying them i went back to the original ATT ROM as it is a very good ROM.
Some time last week i got a message saying there is a new update for me to install, my question is, if i do the update will i lose root?, will i need to redo everything i did to root my phone without affecting the flash counter? or just the root part??
Thanks
PToN22 said:
Hello,
I rooted my ATT SG2 some time ago and i tried a few of the popular ROMs. After trying them i went back to the original ATT ROM as it is a very good ROM.
Some time last week i got a message saying there is a new update for me to install, my question is, if i do the update will i lose root?, will i need to redo everything i did to root my phone without affecting the flash counter? or just the root part??
Thanks
Click to expand...
Click to collapse
I believe the OTA update will remove root, but doing the update won't increase flash counter. But in order to get root back, you must follow the same steps you did to ensure you don't trip the counter.
You're the first person I've heard who likes the stock ATT Rom w/ Root (not touched at all).
My assumption is yes, you will lose root. Can anyone confirm this?
Skyrocketing with QuickWiz via XDA Premium
I was unable to apply the update with a rooted device.
I installed the image from this thread
http://forum.xda-developers.com/showthread.php?t=1381497
having trouble getting root with superoneclick (must be forgetting something)
Related
Got my Note the day that the local ATT store had it in stock. Rooted it the next day with Odin with no problems. I updated to the official ICS this morning but now its no longer rooted. I am sure there is a simple fix, and mabye I have become delerious in my frantic search for a solution, but everything I have tried thus far has not worked. Obviously I was probably supposed to return to stock before updating. Any lamens termed help would be appreciated. This is the third phone I have rooted, but I dont keep up with this stuff after I get them rooted.
Thanks in advance!
Root it the same way you did before. First you need to install clockwork through odin. Then install SU through CWM.
Unless I missed a step, Odin gave me the "Fail" indicator.
You are not mixing up the CWM tar and the Superuser zip are you?
Hi guys,
I am experiencing a problem I dont find any answer to but which may happen to others, too.
I got my new S3 one week ago and for beginners, i didnt want to flash a whole rom. As i was coming from HD2, I wanted to give TouchWiz a chance. I used the SGS3 Toolkit though to root/busybox/cwm all, as nothing is more terrible than an unrooted phone =D.
My problem today is, that my phone just told me there is a Samsung update available to install (~91MB downloaded) and if I wanna do it now -> YES. Phone reboots to CWM and asks me if I really want to install the update, which didnt work then. My guess is, that my "original" Samsung ROM intended to use my (not available) "original samsung recovery" and cwm couldnt handle this request.
Can I create a update.zip to falsh it with cwm or is there any other possibility to flash the update WITHOUT getting a custom Rom?
Thanks allready!
Cmoe
:EDIT: I found the possibility using KIES but it tells me there might be problems with rooted phones. As I hat 4 build to chose from when rooting the phone with toolbox, is it better to first unroot it with toolbox, then appliing the update and then reroot again?
As per thousands of same posts remove root first .
jje
Hi, appreciate this is my first post and thus my question will be regarded with a certain amount of skepticism.. am only posting cos I think my issue is unusual and have not been able to find a similar question/answer through my searches on this forum
Basically, the issue is I rooted my Galaxy S3 (GT-I9300) a month or so ago, installed clockwork mod and superuser etc,. however I held off flashing a ROM because I figured my OTA jellybean update was imminent and wanted to see what the touchwiz jellybean looked like before installing Cyanogen or another ROM. wasn't sure if the OTA would come thru once I shed the stock ROM
So I waited for weeks for the OTA (am on Orange, now Everything Everywhere, in the UK) and have not received it.. last week I went onto Kies and saw there was a new firmware update, so I updated thru Kies thinking that might be what was needed to receive the OTA JB update. updated the firmware but still no JB update - however, now when I check my root status on Root Checker, or try to use any app that requires root, I'm told that I don't have "proper" root access.
My question is updating the firmware over Kies, did that mess up my root access.. am I now unrooted? (this doesn't seem correct) It seems to me I am in a limbo of sorts - not properly rooted anymore, but not fully unrooted either. I want to root the thing again so I can install cyanogen or supernexus, and I would appreciate advice on what to do - should I do a factory reset and then root again as before, or will this cause issues.. was just gon soldier ahead and do it but aware that this may cause problems if my phone already has files from the previous attempt on there.. for example the SGS3 toolkit V.6.0.0 I'm using says not to proceed with its root operations on a phone "that's already rooted" so am hesitant to proceed. Any advice would be appreciated. cheers
You've lost root with the update, just root again and it's all good.
Hi everyone. Im real good with tech but i cant find anyone having asked...
I want to go buy the S4 and I will definitely root it (following the posted instructions on here) but before i do, will i be able to instal OTA updates after and if not, is there another way id be able to install updates? I used Voodoo rootkeeper on my tablet after rooting and the 1st ota went fine and kept root, the 2nd ota killed the root even while using Voodoo...
Please, any any all responses asap appreciated. I want to get the phone asap as i am tired of my rooted Bionic.
Thank all.
bobstone said:
Hi everyone. Im real good with tech but i cant find anyone having asked...
I want to go buy the S4 and I will definitely root it (following the posted instructions on here) but before i do, will i be able to instal OTA updates after and if not, is there another way id be able to install updates? I used Voodoo rootkeeper on my tablet after rooting and the 1st ota went fine and kept root, the 2nd ota killed the root even while using Voodoo...
Please, any any all responses asap appreciated. I want to get the phone asap as i am tired of my rooted Bionic.
Thank all.
Click to expand...
Click to collapse
Just wait for a rooted stock ROM based on the OTA to be made by a dev. You never NEED to take an OTA.
Thanks but im not sure what you mean. I have no interest in loading custom roms nor over-screwing around with the phone. Do you mean wait for another root process or wait for a download for an ota update?
Thanks again
Im guessing you mean a rom will be released again after the ota is out with the ota integrated in it... That process makes me kind of nervous as i need my phone for work as well as personal and cant risk screwing up the phone or erasing data eta...
There is pretty much always someone that releases the stock ROM flashable in a custom recovery so you can have a rooted stock ROM. Look at the dev beanstownm106 ROM in the development section. It is basically the stock ROM rooted with some very minor tweaks, but flashable with a custom recovery like TWRP.
BUT...there is almost never anything you can't do with basically any ROM that you can do with the stock ROM. So you really don't need the stock ROM...some people just prefer it. For my old Thunderbolt, it was pretty well known that for a long time there was a custom ROM, very similar to the stock ROM, that was more stable than stock (SkyRaider Zeus).
Another BUT: if you need Good for work, prepare for a constant fight with root detection. And you will want to back up your data often. I have a BB for work that I leave untouched (its not mine).
One more thing...the Loki workaround has its advantages...the bootloader is still locked and untouched, so it would be pretty hard to brick the device because you can get back into download mode and use odin to flash back to factory.
Whats the loki workaround? Also, im dont want to be doing any kind of flashing... I just simply want to root the s4 (which i now have) and be able to run ota updates or if not, download the ota and install the update manually. And if i get an ota, if it will kill root, even if i run voodoo.
Please, if someone could, let us all know if ota wont run or will kill root on say the s3 or s4 and if downloadable updates are another option... without flashing anything or going to crazy.
Thanks again in advance.
Running latest Pixel Experience w/ root right now and was wondering about OTAs.
When updating, is there anything I need to do with root or can I just run the OTA normally and update?
Last time I ran an OTA update w/ root, my phone would restart randomly sometimes during usage and I couldn't figure out why so I reflashed everything and it hasn't happened since.
Leads me to asking whether updating while still rooted messed with the phone in some way. So yeah, do I need to unroot before running the OTA or do I unroot and then OTA and then reroot?
(Also, if I need to unroot, how do I do that? Have only ever rooted phones, never had to unroot one.)
thevietmonk said:
Running latest Pixel Experience w/ root right now and was wondering about OTAs.
When updating, is there anything I need to do with root or can I just run the OTA normally and update?
Last time I ran an OTA update w/ root, my phone would restart randomly sometimes during usage and I couldn't figure out why so I reflashed everything and it hasn't happened since.
Leads me to asking whether updating while still rooted messed with the phone in some way. So yeah, do I need to unroot before running the OTA or do I unroot and then OTA and then reroot?
(Also, if I need to unroot, how do I do that? Have only ever rooted phones, never had to unroot one.)
Click to expand...
Click to collapse
disable magisk modules, reboot then try.
better to just n download the rom and dirty flash imho