Related
Can someone advise on the ota update.. I don't quite understand entirely boot loaders and such.. My note 2 is stock rooted. I don't think I will ever Change roms, but I want to stay rooted.
What is the verdict for someone like me? I do not want to block ota then miss other important updates, but I do not want to lose root either.
Please advise.
Again, sorry for such a basic question. I am still transistioning from iPhone world
Sent from my iPad using Tapatalk HD
crash613 said:
Can someone advise on the ota update.. I don't quite understand entirely boot loaders and such.. My note 2 is stock rooted. I don't think I will ever Change roms, but I want to stay rooted.
What is the verdict for someone like me? I do not want to block ota then miss other important updates, but I do not want to lose root either.
Please advise.
Again, sorry for such a basic question. I am still transistioning from iPhone world
Sent from my iPad using Tapatalk HD
Click to expand...
Click to collapse
Just block it. Sure devs will find a way to root and unlock again soon. At that point, you can restore the SDM 1.0 and get later updates if you need them.
You're sure to lose root within 5 days if you don't.
Ok, based on what you say you don't want to rom but you want root. That is where I am. There is an app called voodoo ota rootkeeper in the play store. It is free. Install it and use it to backup root. Take the update and use voodoo to restore root.
That will get you root and a locked bootloader. Which is where I read you want to be. But remember you may be stuck with a locked bootloader forever.
That said consider this. Pass on the update for now. You can always update to it later to get the next update. By waiting you keep your options open and miss nothing.
TonikJDK said:
Ok, based on what you say you don't want to rom but you want root. That is where I am. There is an app called voodoo ota rootkeeper in the play store. It is free. Install it and use it to backup root. Take the update and use voodoo to restore root.
That will get you root and a locked bootloader. Which is where I read you want to be. But remember you may be stuck with a locked bootloader forever.
That said consider this. Pass on the update for now. You can always update to it later to get the next update. By waiting you keep your options open and miss nothing.
Click to expand...
Click to collapse
Good advice. This is my plan as well.
Sent from my SCH-I605 using xda app-developers app
Thank you both for the quick replies. I think that is what I am going to do. Block it for now, using titanium. Then wait and see.
I am going to look in to that other program though. Right now I feel I will always want to reman stock-rooted, but who knows... No point in closing that door forever.
Just so I have this straight..... Using titanium I backed up the sdm 1.0 file, then in the same screen I click on it and choose delete? That's it? Thanks for being patient with me.
crash613 said:
Thank you both for the quick replies. I think that is what I am going to do. Block it for now, using titanium. Then wait and see.
I am going to look in to that other program though. Right now I feel I will always want to reman stock-rooted, but who knows... No point in closing that door forever.
Just so I have this straight..... Using titanium I backed up the sdm 1.0 file, then in the same screen I click on it and choose delete? That's it? Thanks for being patient with me.
Click to expand...
Click to collapse
Yes, although I believe it's "Un-install", not delete. You could freeze it as well, if you have the paid for version.
Sent from my SCH-I605 using xda app-developers app
I have a Note 2 that was rooted using a root-injected stock OS. Unfortunately, the OTA got me this morning and I have lost root. At the following link several folks have replied that they were able to get their Note 2's rooted after the OTA. What do you guys think? I don't want to brick my phone but I sure need Root-Explorer and Titanium Backup.
http://galaxynote2root.com/galaxy-note-2-root/how-to-root-verizon-galaxy-note-2-sch-i605/
Guitar4Him said:
I have a Note 2 that was rooted using a root-injected stock OS. Unfortunately, the OTA got me this morning and I have lost root. At the following link several folks have replied that they were able to get their Note 2's rooted after the OTA. What do you guys think? I don't want to brick my phone but I sure need Root-Explorer and Titanium Backup.
http://galaxynote2root.com/galaxy-note-2-root/how-to-root-verizon-galaxy-note-2-sch-i605/
Click to expand...
Click to collapse
I can now confirm that, if you have a rooted, stock Note II and lose root through the OTA, you can go the Odin route with a rooted stock image and successfully root the device. Additionally, if you install Voodoo OTA Rootkeeper after rooting the device, you can then, do the OTA and restore root using the Voodoo app. Instructions and files are available at:
http://forum.xda-developers.com/showthread.php?t=2024207
Please post Questions in Q&A'
Thread moved
Friendly Neighborhood Moderator
http://forum.xda-developers.com/showpost.php?p=37066564&postcount=1167
I can confirm that a handy dandy combination of:
1. Deferring the update
2. Rooting via ExynosAbuse
3. Backing up root via Voodoo OTA Rootkeeper
4. Updating
will maintain root with the latest Verizon Galaxy Note 2 update.
I am now I605VRALL4and my Device Status says "Normal" since I haven't flashed anything.
y8s said:
I am now I605VRALL4and my Device Status says "Normal" since I haven't flashed anything.
Click to expand...
Click to collapse
I did what you did and I am modified. I did the light sabre mod. But I don't think that would do it.
Edit......reboot and mine is back to normal.
Simple question and hopefully different from all the other "It's here!", "Where are our ROM" threads..
I upgraded (if you can call it that) to the Galaxy Nexus literally like a week ago and deactivated my TB but it remains rooted.
Anyone know if there are dangers trying to activate it rooted with the intent to unroot, wait for the OTA, just in the hopes it will sell for more.
Or would you recommend unrooting then activating and then waiting for the OTA?
Hopefully you understand the question. I had the impression from a friend that if I tried to re-activate with root, it would red flag me for modified software. Thanks in advance.
DNak206 said:
Simple question and hopefully different from all the other "It's here!", "Where are our ROM" threads..
I upgraded (if you can call it that) to the Galaxy Nexus literally like a week ago and deactivated my TB but it remains rooted.
Anyone know if there are dangers trying to activate it rooted with the intent to unroot, wait for the OTA, just in the hopes it will sell for more.
Or would you recommend unrooting then activating and then waiting for the OTA?
Hopefully you understand the question. I had the impression from a friend that if I tried to re-activate with root, it would red flag me for modified software. Thanks in advance.
Click to expand...
Click to collapse
The stock rooted roms are posted on the Infected forums if you just want to flash the stock rooted ICS.
OR, you could unroot and flash the OTA, but doing so I believe will upgrade your hboot, so you'll have to wait a bit until get the s-off on the new hboot.
Either way, I'm sure it'll be all squared away in the next couple of weeks.
Personally, if it were me, I would unroot and go OTA. Fly around completely stock for a while on your phone. I did that when 605.19 came out and I was actually surprised how well it performed being completely stock (battery life aside). But that didn't last long for me--I rooted it pretty shortly after.
Also, I'm not sure if you'd be red-flagged for trying to update OTA from root. I mean the worst that could happen is the update won't go through, and more likely, the update will go through, but will completely remove root and s-off.
Don't take the OTA expecting to reroot!
wazup7 said:
The stock rooted roms are posted on the Infected forums if you just want to flash the stock rooted ICS.
OR, you could unroot and flash the OTA, but doing so I believe will upgrade your hboot, so you'll have to wait a bit until get the s-off on the new hboot.
Either way, I'm sure it'll be all squared away in the next couple of weeks.
Personally, if it were me, I would unroot and go OTA. Fly around completely stock for a while on your phone. I did that when 605.19 came out and I was actually surprised how well it performed being completely stock (battery life aside). But that didn't last long for me--I rooted it pretty shortly after.
Also, I'm not sure if you'd be red-flagged for trying to update OTA from root. I mean the worst that could happen is the update won't go through, and more likely, the update will go through, but will completely remove root and s-off.
Click to expand...
Click to collapse
There may not be a "re-root" after you take the new hboot!!!!
YOU HAVE BEEN WARNED!!!
I've been saying this and not enough people are listening and stuck not being able to root again.
I know one person even trying to work on the hboot right now and his device will no longer boot, so think again before taking the OTA.
It's up to you and doesn't effect me either way, just a few words of advice if you will.
Maybe this will change and another miracle as big as this release will happen and an exploit will be found on a 2 year old device with less then a handful of devs even looking at it.
This could change, but right now I would not count on it.
I took the update unrooted but still had revolutionary's hboot. I can confirm that the hboot was not overwritten by the new one.
Edit
Didn't realize there was a thread about this already lol. My bad.
Sent from my HTC6435LVW using xda app-developers app
Seems there is a LOT of revert to stock and unroot threads, is there a consolidated place or simple means of doing this? I think I'm going to undo everything I did and just her activate it stock. If she *****es down the road about not having root (unlikely), I'll worry about it then.
Thanks guys.
I didnt realize at that time, that the update he was doing would block root. If I factory reset, will it put me back to pre-update so that when i boot up the phone I can root it first thing? Thanks for any help.
hondaboi20002 said:
I didnt realize at that time, that the update he was doing would block root. If I factory reset, will it put me back to pre-update so that when i boot up the phone I can root it first thing? Thanks for any help.
Click to expand...
Click to collapse
From what I have read the answer is NO. I think you are SOL until a new root method is found.
So basically all I can do is take it back, pay 35 buck restock fee, get another phone and root as soon as I get it setup and not install that update?
hondaboi20002 said:
So basically all I can do is take it back, pay 35 buck restock fee, get another phone and root as soon as I get it setup and not install that update?
Click to expand...
Click to collapse
I believe that is your only option, yes. To my knowledge, there is no way to revert back and you're stuck. Unless you'd like to just keep your current phone and wait until someone roots the new update, but your only other option would be to exchange it.
In your opinion, do you think the devs will find a way to crack this update and obtain root?
hondaboi20002 said:
So basically all I can do is take it back, pay 35 buck restock fee, get another phone and root as soon as I get it setup and not install that update?
Click to expand...
Click to collapse
Correct. That is *IF* the new phone doesn't already have the update installed, or the sales rep doesn't install the update while activating it and getting it ready for you.
Rumor has it that they already have root, but aren't releasing how until they can find a way to also unlock/patch the boot loader. They are said to be afraid of having Samsung/Verizon block this root method before they can use it to unlock the boot loader. Will they ever get it? Will they ever release the root method? That is anyone's guess.
So for now, it looks like the 16gig DEV edition direct from Samsung, without warranty, is the only option if you definitely want to root and flash custom roms now and "forever". But is it still available? or did they sell out yet?
Spoke with my rep and he told me bring it back, exchange it and all he will do is activate it and hand it right over to me and will not install the update. Now once I do get the new phone without the update and obtain root, can or will that verizon update still try and come thru and ask me to install it?
You can block the OTA updater with titanium backup. I'm not on a stock ROM, so I don't remember the updater app name.
Sent from my SCH-I545 using Tapatalk 4 Beta
SDM
That sucks. You gotta keep your eye on those reps :cyclops:
i never let any sales person set up, activate or even power up any phone i buy. if they chose to do so i cancel the order and buy on line where it comes sealed. i always tell them i'm in a rush and i'll take care of activating it afterwards. only one has ever refused and i told him to cancel the sale since he decided to open a product i purchase without my consent. he did get me a new one after that.
hondaboi20002 said:
So basically all I can do is take it back, pay 35 buck restock fee, get another phone and root as soon as I get it setup and not install that update?
Click to expand...
Click to collapse
That is assuming the new phone you get isn't updated b4 u turn it on...
Sent from my SCH-I545 using xda app-developers app
Ok, got a new S4 and this worked !!
Ok, everyone I got a new S4 and activated at Verizon which it immediately started download pretty much as soon as it was turned on. I immediately disabled mobile data, turned it off and then took out the sim card. Once I got home, I hooked this baby up to my PC and rooted...success, finally! I used the I545 all-in-one-root tool which includes OUDS clockwork. http://www.droid-life.com/2013/05/30/all-in-one-root-tool-released-for-verizon-galaxy-s4/
My questions is I have installed ROM Manager so that I could do a backup, but when I first open ROM manager, it says I need to install a custom recovery even though I have OUDS clockwork built in. Do I need to install clockwork from within the ROM manager app? I can reboot into recovery, but its the OUDS "generic" recovery, for lack of a better word. Is that recovery good to go for backing up, flashing another ROM or do I need to use the ROM manager to install CWM from with the app itself? Hope this makes sense. Thanks everyone!!
I'm a VZW rep and every time I activate a new S4, the update automatically starts downloading and there's NO way to tell it to "differ" to a different time.
Trust me, its not OUR fault. It just happens sadly :-\
I too hope devs get a way to root past this OTA because I have friends that would like me to root for them, but the OTA just muscles its way through.
I haven't upgraded anyone to an S4 today, but will report back with more info when I do. I'm pretty sure that after we activate the phone, the download starts and the notification just sits there until you click it (then it updates) or if you restart the device, it may force the update. I'll test on my next customer and let y'all know the real answer
Sent from my SCH-I545 using xda premium
dopediculous said:
I'm a VZW rep and every time I activate a new S4, the update automatically starts downloading and there's NO way to tell it to "differ" to a different time.
Trust me, its not OUR fault. It just happens sadly :-\
I too hope devs get a way to root past this OTA because I have friends that would like me to root for them, but the OTA just muscles its way through.
I haven't upgraded anyone to an S4 today, but will report back with more info when I do. I'm pretty sure that after we activate the phone, the download starts and the notification just sits there until you click it (then it updates) or if you restart the device, it may force the update. I'll test on my next customer and let y'all know the real answer
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
My experience with the update is that it will tell you the download is ready and at that point you can postpone it to a later time. It even gives you a little wheel to select when to install the update. The phone is still completely rootable during that time. When the notification comes back you can again postpone until a later time.
brw9100 said:
My experience with the update is that it will tell you the download is ready and at that point you can postpone it to a later time. It even gives you a little wheel to select when to install the update. The phone is still completely rootable during that time. When the notification comes back you can again postpone until a later time.
Click to expand...
Click to collapse
That's what happened to me. During the initial setup it was downloading the OTA update. As soon as I could, I enabled "Airplane mode" to kill the update, but no, it had already downloaded and asked if it was OK to install.
I deferred it until 1:00 AM and immediately started the rooting process. Got root, installed SuperSU Pro and enabled Survival mode. I also installed Voodoo OTA RootKeeper, but that wasn't necessary.
So I'm now running stock with superuser available and protected. Unfortunately, no custom recovery.
Since I have been doing smartphones, I have NEVER updated, I wait until someone has tried it. and even then, I wait for a dev to cook it up. And everyone better hope you do not have to do any replacements thru the carrier, you WILL get a bootloader locked device with the newest release, NO bootloader fix.
Need to find alternatives.
k1mu said:
That's what happened to me. During the initial setup it was downloading the OTA update. As soon as I could, I enabled "Airplane mode" to kill the update, but no, it had already downloaded and asked if it was OK to install.
I deferred it until 1:00 AM and immediately started the rooting process. Got root, installed SuperSU Pro and enabled Survival mode. I also installed Voodoo OTA RootKeeper, but that wasn't necessary.
So I'm now running stock with superuser available and protected. Unfortunately, no custom recovery.
Click to expand...
Click to collapse
That's great news to hear! Unfortunately my location was dead yesterday and I didn't sell any S4's. Just stupid idonts to bubblegum chewing pop tarts and grandparents. Ugh *face palm
Sent from my SCH-I545 using xda premium
brw9100 said:
My experience with the update is that it will tell you the download is ready and at that point you can postpone it to a later time. It even gives you a little wheel to select when to install the update. The phone is still completely rootable during that time. When the notification comes back you can again postpone until a later time.
Click to expand...
Click to collapse
Yeah, I ordered my S4 online, and it let me defer the update. It downloaded, then said ready to install would you like to install now or later? I set the timer to 12 hours, rooted, installed recovery, flashed AOKP, and bam, no worrying about OTA updates.
Sent from my SCH-I545 using Tapatalk 4 Beta
hondaboi20002 said:
Spoke with my rep and he told me bring it back, exchange it and all he will do is activate it and hand it right over to me and will not install the update. Now once I do get the new phone without the update and obtain root, can or will that verizon update still try and come thru and ask me to install it?
Click to expand...
Click to collapse
What I suggest is what I did.
Do not place the sim into the phone.
My phone came from Wirefly.com without the sim card installed.
Power up without sim card, boot directly to download mode, connect to pc usb port, run Odin, follow rooting procedure.
Only after you freeze SDM using titanium backup, should you consider inserting the sim card.
Also while on wifi samsung will ask to install update, say no.
P. S. I installed samsung drivers, and Odin. I did not install kies which I have read also tries to install the update.
I rooted my phone to prevent KitKat from installing, because I didn't want to lose access to FoxFi. I forze the SDM file so it wouldnt look for updates. Today FoxFi has fixed the problem, so I no longer fell the need to be rooted, and I would very much like a taste of that KitKat. If I understand correctly I should not unfreeze the the SDM file and take the OTA update, because it could "brick my phone". Is that the case?
Do I need to unroot first, and is there a thread without a hundred pages that explains how to unroot. I am on Build VRUEMK2.
Thoughts?
Under the settings in the Superuser app is an option to "Full Unroot" Will this really work for unrooting the device, or do i need to do the odin thing i keep reading about? Why would odin even be necessary if this is an option. It seems to easy.
You will need to return your phone to stock, root will prevent the OTA. You can try to unfreeze SDM and take the update, it won't brick your phone, it will just fail to install because root will cause it to fail.
There are threads about using Odin and no-wipe MK2 or MJ7 files to return your phone to stock without losing data. That is the best way to roll your phone back to take the update. Alternatively, you could just do a factory reset from the stock recovery, but you'll lose all your data on the phone. Otherwise, you can just update using the Odin tars that are available now, but since it seems like you don't want to do the research on how to do that, you'd probably better not try.
Paramemetic said:
There are threads about using Odin and no-wipe MK2 or MJ7 files to return your phone to stock without losing data. That is the best way to roll your phone back to take the update. Alternatively, you could just do a factory reset from the stock recovery, but you'll lose all your data on the phone. Otherwise, you can just update using the Odin tars that are available now, but since it seems like you don't want to do the research on how to do that, you'd probably better not try.
Click to expand...
Click to collapse
Thanks,
So you do not recommend or know about the "Full Unroot" option in the Superuser settings.
I do not mid a factory reset, as this is phone is only a month old. If it is that easy, I will probably go that route.
I am currently downloading a file called VRUAMDK_NoWipe.tar.zip which I understand to be a stock image of my android before i rooted that is supposed to take me back to pre-root. But if factory resetting will accomplish the same goal, then that seems like an easier way to go.
I do like the openness of being rooted, but My concern about updating with the root, is that some functions may not work like they are supposed to. I haven't been involved in rooting since the days of playing with my HTC Eris, and Droid X. Maybe things a re different today, but most roms I played with were found to have issues with thinks not functioning correctly. Do the 4.4 "tars" that you are referring to have all the functions?
I'd sit tight and see what comes from the latest tar files of NC5. Maybe nothing, but can't hurt to wait.
Sent from my SCH-I545 using XDA Free mobile app
Rageboardr said:
Thanks,
So you do not recommend or know about the "Full Unroot" option in the Superuser settings.
I do not mid a factory reset, as this is phone is only a month old. If it is that easy, I will probably go that route.
I am currently downloading a file called VRUAMDK_NoWipe.tar.zip which I understand to be a stock image of my android before i rooted that is supposed to take me back to pre-root. But if factory resetting will accomplish the same goal, then that seems like an easier way to go.
I do like the openness of being rooted, but My concern about updating with the root, is that some functions may not work like they are supposed to. I haven't been involved in rooting since the days of playing with my HTC Eris, and Droid X. Maybe things a re different today, but most roms I played with were found to have issues with thinks not functioning correctly. Do the 4.4 "tars" that you are referring to have all the functions?
Click to expand...
Click to collapse
The no wipe image you are downloading is probably not the correct version for your phone unless you are still on the MDK firmware.
Sent from my SCH-I545 using Tapatalk
jmgib said:
The no wipe image you are downloading is probably not the correct version for your phone unless you are still on the MDK firmware.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Bummer, I was wondering about that after i started looking at different image names. I started seeing the common theme, and no I am not on MDK, I am on MK2. Bummer because that file took along time to download here at work.
kude87 said:
I'd sit tight and see what comes from the latest tar files of NC5. Maybe nothing, but can't hurt to wait.
Sent from my SCH-I545 using XDA Free mobile app
Click to expand...
Click to collapse
What is the difference between a tar file, and ROMing. Are TAR files more reliable?
I am in no real hurry, but as this is my daily phone, I need everything to work correctly, and no reason to wait if its like ROMs, and there seem to always be things that are quirky in a ROM.
Rageboardr said:
What is the difference between a tar file, and ROMing. Are TAR files more reliable?
I am in no real hurry, but as this is my daily phone, I need everything to work correctly, and no reason to wait if its like ROMs, and there seem to always be things that are quirky in a ROM.
Click to expand...
Click to collapse
If it is your daily and you aren't in any hurry, I strongly suggest waiting it out. Read some forums and get a better feel about rooting and romming.
A tar file is flashed through Odin, and depending which one you download, could lock your bootloader (I forget which firmware you're on). I'd personally wait for/if NC5 is rooted and proceed then.
"Romming" is a broad term used to define flashing custom roms. Predominantly, this means you have an unlocked bootloader and are flashing zip files through a custom recovery.
Sent from my SCH-I545 using XDA Free mobile app
Rageboardr said:
I rooted my phone to prevent KitKat from installing, because I didn't want to lose access to FoxFi. I forze the SDM file so it wouldnt look for updates. Today FoxFi has fixed the problem, so I no longer fell the need to be rooted, and I would very much like a taste of that KitKat. If I understand correctly I should not unfreeze the the SDM file and take the OTA update, because it could "brick my phone". Is that the case?
Do I need to unroot first, and is there a thread without a hundred pages that explains how to unroot. I am on Build VRUEMK2.
Thoughts?
Click to expand...
Click to collapse
Hi I had the same issue. mk2, rooted, wanted to take the ota update and didn't mind losing root.
You won't brick trying to take the update it will just fail with error 402. I wrote out my steps below to guide you thru the process I used and were successful for me.
1. Unroot using SuperSU.
2. Use Kies to update/restore firmware on your PC.
3. Once rebooted search for system update.
4. Download and install the update. I did the whole process using only data no WiFi (not sure if it makes a difference but that's what I did).
5. Once your phone reboots you will be greeted by a lovely red Verizon splash screen.
Hope this helps you and others!
Sent from my Hp Touchpad Android 4.4.2 using Tapatalk Pro
Hey everyone, I have a question...so I rooted my phone a couple of months ago and never got around to installing a custom rom. So as of right now I have the stock 4.3 (sch-i545), I never done anything besides rooting it. I just received an update for the stock rom and my question is, could I just update it while my phone is rooted without voiding the warranty and or bricking it? Much obliged for your time
http://forum.xda-developers.com/showthread.php?t=2726868
Sent from my SCH-I545 using XDA Premium 4 mobile app
If all you did was rooted, and didn't delete any apps, make any changes to files, etc., it should work. It won't brick your phone if it doesn't work, it will just reboot and tell you it failed.
Sir_Eagle said:
If all you did was rooted, and didn't delete any apps, make any changes to files, etc., it should work. It won't brick your phone if it doesn't work, it will just reboot and tell you it failed.
Click to expand...
Click to collapse
My understanding was that you need to be absolute stock to take an OTA. Have you seen anyone say they've been able to OTA a rooted phone?
Sent from my SCH-I545 using XDA Premium 4 mobile app
joshm.1219 said:
My understanding was that you need to be absolute stock to take an OTA. Have you seen anyone say they've been able to OTA a rooted phone?
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Can't say for sure if I have. Never heard of anyone that rooted and didn't make any kind of change either.
Sir_Eagle said:
Can't say for sure if I have. Never heard of anyone that rooted and didn't make any kind of change either.
Click to expand...
Click to collapse
If all you did was root the phone, you will be able to OTA... BUT,
This OTA update will install NC5 on your phone and add the lovely Knox warranty void as well.
As far as I can tell, at this time, therd is NO way of rooting the Verizon S4 after updating to NC5.
If you look under "About Phone, Status.. Device Status, if it says OFFICIAL, you'll be good to go for OTA.
But remember... no Rooting under the new OTA with verizon, until one of the XDA Genius finds a solution for us zombies.
Pow35 said:
If all you did was root the phone, you will be able to OTA... BUT,
This OTA update will install NC5 on your phone and add the lovely Knox warranty void as well.
As far as I can tell, at this time, therd is NO way of rooting the Verizon S4 after updating to NC5.
If you look under "About Phone, Status.. Device Status, if it says OFFICIAL, you'll be good to go for OTA.
But remember... no Rooting under the new OTA with verizon, until one of the XDA Genius finds a solution for us zombies.
Click to expand...
Click to collapse
I tried to OTA on rooted phone and it failed.
Don't like to do a factory reset, so I basically only want an OTA update. Cant stick anymore as my phone is driving me nuts, my phone screen keeps on going black and locking every few seconds when I wake the screen from sleep
ch.ch1 said:
I tried to OTA on rooted phone and it failed.
Don't like to do a factory reset, so I basically only want an OTA update. Cant stick anymore as my phone is driving me nuts, my phone screen keeps on going black and locking every few seconds when I wake the screen from sleep
Click to expand...
Click to collapse
Go here:
http://forum.xda-developers.com/showthread.php?t=2578209
You can go to MK2; the latest version of Jellybean.
You can then either root and stay there.
You can root, install safestrap then go to a rooted KitKat (NC5) and keep the MK2 bootloader.
You can ignore all rooting and mods and take the OTA and go to a crippled NC5 with no root.
Hope that helps.
yupp
joshm.1219 said:
My understanding was that you need to be absolute stock to take an OTA. Have you seen anyone say they've been able to OTA a rooted phone?
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah I used the OTA update and my phone was rooted. Also every time I turn(ed) on my phone it says samsung custom with an unlock this is on 4.4.2 and on 4.3 before. I checked to see if I have root, but I don't. Also superuser is still installed, says I don't have root (obviously). Except the weird thing is, that it says samsung custom still, and on the isis mobile wallet it says I cant use it because my device is rooted. I also used root checker to see if I was to double check and it says I'm not. I'm really confused... but hey at least the OTA update worked, i just cant wait to get root again because I will miss all my rooted apps. I didn't check to make sure they developed root either. which sucks but whatever.