• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Virgin Mobile] Quick question re: future OTA updates & root

KOAM

KOAM

Well-Known Member
Apologies because I have a feeling this has been asked before, but I couldn't find anything through a search.. probably because the search terms are so basic.

I just rooted my S3 (4.3 stock) and am going to keep it on the stock rom, but I want to know if/when the official KitKat OTA update comes, is it safe to update as usual? It's fine if it unroots as I'm sure there will be a way to root it again, but I want to be sure it's not something to avoid right away.

Thanks very much.
 
Root will not remain so you would have to reroot it. The issue I believe is if you have flashed a custom recovery (TWRP, CWM) the OTA update, if and when it comes, may not work. I believe you must be on a stock recovery to install it.
 
MopedRyder is 100% correct. Once the OTA drops, simply flash the 4.3 Odin tar to get back to 100% stock unrooted(this process will wipe your internal memory so back up your files on your PC), then get the OTA, and root and flash or whatever you want. If you don't care about your warranty and Knox, KitKat update is already available through Sprint and works fine on our phones.
 
jdsingle76 said:
MopedRyder is 100% correct. Once the OTA drops, simply flash the 4.3 Odin tar to get back to 100% stock unrooted(this process will wipe your internal memory so back up your files on your PC), then get the OTA, and root and flash or whatever you want. If you don't care about your warranty and Knox, KitKat update is already available through Sprint and works fine on our phones.
Click to expand...

Or you could just flash the stock recovery(don't know if it has to be specific to mk5 or if it can be from earlier 'just ask JD single, but after that you should be able to take the ota, I had to use this method when accepting ota's for the nvidia shield
 
jdsingle76 said:
MopedRyder is 100% correct. Once the OTA drops, simply flash the 4.3 Odin tar to get back to 100% stock unrooted(this process will wipe your internal memory so back up your files on your PC), then get the OTA, and root and flash or whatever you want. If you don't care about your warranty and Knox, KitKat update is already available through Sprint and works fine on our phones.
Click to expand...
JDsingle76: I'm on stock mk5 and have yet to flash any roms. I want to receive the kitkat ota when it finally comes. I have philz 6 latest version 6.41.6 custom recovery. Is there just way to flash the stock recovery, so kitkat ota will work correctly. Flashing your mk5 4.3 do this for me?? Of course will continue to read the postings, just wanted to ask an expert on this posting.

thx, Steve
 
tigerstv44 said:
JDsingle76: I'm on stock mk5 and have yet to flash any roms. I want to receive the kitkat ota when it finally comes. I have philz 6 latest version 6.41.6 custom recovery. Is there just way to flash the stock recovery, so kitkat ota will work correctly. Flashing your mk5 4.3 do this for me?? Of course will continue to read the postings, just wanted to ask an expert on this posting.

thx, Steve
Click to expand...

Thanks for the remarks but I assure you I'm no expert. You have to be on stock recovery to take the KK ota and the only way to get that is to flash the stock mk5 tar. Here's the link.
http://forum.xda-developers.com/showthread.php?t=2746294
 
So I've flashed the mk5 stock tar and am back to stock. Before i went back to stock, I copied the KK update i received to my SD card, is there a way to install this through stock recovery? So far it fails when I try when it is checking the current system, something about a .ko file not having the expected contents and an error 7.
I have not rerooted yet.
 
sanjuro77 said:
So I've flashed the mk5 stock tar and am back to stock. Before i went back to stock, I copied the KK update i received to my SD card, is there a way to install this through stock recovery? So far it fails when I try when it is checking the current system, something about a .ko file not having the expected contents and an error 7.
I have not rerooted yet.
Click to expand...

If you can upload the zip file, we may be able to make a version that is flashable via custom recovery.
 
sanjuro77 said:
Right on, thanks. It's uploading now. I'll edit this with the link when it's up.

I guess that would help others that don't want to wait for the update to show up again!


Here's the update file, mk5 to nd8 ~

http://d-h.st/XnO
Click to expand...

Can you find out exactly what the error message says? I'm starting to think that once Knox is tripped it won't flash.
 
jdsingle76 said:
Can you find out exactly what the error message says? I'm starting to think that once Knox is tripped it won't flash.
Click to expand...


Well that would suck, considering the only reason I allowed Knox on my phone to begin with was to upgrade to KK.

I think the message said lib.modules.dhd.ko didn't have the expected contents while checking the current system. It only lasts on the screen for about a second.
 
sanjuro77 said:
I'll have to give this a shot today. It doesn't matter that I don't have a Nexus¿
Click to expand...

No. That was written when nexus first got the kk ota. I've read of others getting it to work that way after getting an error from getting it ota.

My S3 already has the Sprint KK ND8 boot loader so unfortunately I can't test this myself or I would. Good luck to anyone who gives it a go.
 
Should the stock MK5 tar I flashed with Odin have the Knox app in it, cause it doesn't. Could that be the issue? Perhaps I got the wrong tar?
 
Meaning there isn't an actual Knox app present in the drawer. The Knox boot loader is there for sure, since it's showing a flag in download mode. Just no app. My gf's s4 has a Knox app so I assumed I should too.
I was running the Knox-free mk5 beforehand.

Right now I'm connected to Kies seeing if it'll get me there. It failed once but now seems to be working (fingers crossed).

On a side note, why is Kies so unpredictable? Had to plug in 5 times before it decided it needed to reinstall its drivers.
 
You must log in or register to reply here.
Back
Top Bottom