Develop Bugs

Root Phone T-Mo update questions

If I root my phone and Tmo sends an OTA update, will my phone still be rooted?

I don't believe you have to reset the flash count for this. But you do need to flash unrooted stock ROM first. Then get the OTA update. After that root again.

Thank you for the response.
I had another phone I rooted and when Tmo tried to push the update, Recovery mode caught it. I could never get the phone out of recovery mode after that. I got rid of the phone.
I don't want that to happen again obviously and why I asked the question. Seems to me, returning to stock, the rerooting might be more trouble than it's worth unless I had some compelling reason to do so.

JosephL said:
Thank you for the response.
I had another phone I rooted and when Tmo tried to push the update, Recovery mode caught it. I could never get the phone out of recovery mode after that. I got rid of the phone.
I don't want that to happen again obviously and why I asked the question. Seems to me, returning to stock, the rerooting might be more trouble than it's worth unless I had some compelling reason to do so.
Click to expand...
Click to collapse
Here is the easiest method of managing root with this device: http://forum.xda-developers.com/showthread.php?t=1957720
I like managing the background auto start processes to make my devices run much more smoothly. Which is why I like to root. Back up is another reason.
At this point I believe staying stock while rooted right now would help in the process of unrooting for updates.
There is going to be at least two or more updates. First update to get our multi-window, Swift Key Flow keyboard and other stuff that should of been in our Note 2 devices. Another update that will be enabling our LTE radio (when T-Mobile rolls out LTE). Jelly Bean 4.2 Android OS update should be updated somewhere in between these other updates (possibly at the same time as the enabling LTE update). So you are correct in thinking first before rooting.

JaguarXT said:
So you are correct in thinking first before rooting.
Click to expand...
Click to collapse
Uh huh. I see a stock ROM in my future.
Thanks.

JaguarXT said:
At this point I believe staying stock while rooted. right now would help in the process of unrooting for updates.
Click to expand...
Click to collapse
So you are saying, root but leave stock. Will the updates require me to unroot to receive them if I leave it stock?

Correct
Root and leave stock just my idea. Makes things easier when unrooting. But that is just my idea.
Always make a backup stock rom to unroot with. Or you can use the stock rom from this thread here. http://forum.xda-developers.com/sho...FIRMWARE] SGH-T889 Factory Image (Unmodified) This is gold here.
After each OTA update you should make a backup of your stock rom as your latest stock rom. We should have a latest version of stock rom posted in our forum. But always best to use your latest backup image for stock rom. Again: This is gold here.
Read the thread that I gave you above.
But yes, unrooting before you can take OTA update. Take OTA update. Then root again.
Sent from my SGH-T889 using xda premium

JaguarXT said:
But yes, unrooting before you can take OTA update. Take OTA update. Then root again.
Click to expand...
Click to collapse
According to this guy all I need to do is flash the stock recovery, then I can take the update, then just flash Clockwork recovery once the update is taken and by what I think he's saying I don't have to unroot.
http://www.youtube.com/watch?v=2VVyQRdsnaA&feature=channel&list=UL
Does this sound right?

Flashing stock rom will unroot your Galaxy Note 2. Basically put your Galaxy Note 2 back in to the same unmodified state that you bought it. Then OTA update. Then root.
Yes, I would take the OTA updates for now. They are important.
Also remember to backup your stock rom after OTA update. This will be the new stock rom for you to flash when you need to.
Sorry that I didn't explain what the process of unrooting was with GN2. Didn't have time, while with family. That is why I gave you the links.

JaguarXT said:
Flashing stock rom will unroot your Galaxy Note 2. Basically put your Galaxy Note 2 back in to the same unmodified state that you bought it. Then OTA update. Then root.
Yes, I would take the OTA updates for now. They are important.
Also remember to backup your stock rom after OTA update. This will be the new stock rom for you to flash when you need to.
Sorry that I didn't explain what the process of unrooting was with GN2. Didn't have time, while with family. That is why I gave you the links.
Click to expand...
Click to collapse
would voodoo rootkeeper work for unrooting a stock rom, taking the ota update, then using voodoo again to regain root?
the only thing ive done to my phone is root, but i still want the ota updates for multi-window, etc later on.

JosephL said:
Thank you for the response.
I had another phone I rooted and when Tmo tried to push the update, Recovery mode caught it. I could never get the phone out of recovery mode after that. I got rid of the phone.
I don't want that to happen again obviously and why I asked the question. Seems to me, returning to stock, the rerooting might be more trouble than it's worth unless I had some compelling reason to do so.
Click to expand...
Click to collapse
I dont have this phone yet but I know in most android you can disable updates in the settings so you dont run into those kinda problems
---------- Post added at 02:14 AM ---------- Previous post was at 02:11 AM ----------
JaguarXT said:
Flashing stock rom will unroot your Galaxy Note 2. Basically put your Galaxy Note 2 back in to the same unmodified state that you bought it. Then OTA update. Then root.
Yes, I would take the OTA updates for now. They are important.
Also remember to backup your stock rom after OTA update. This will be the new stock rom for you to flash when you need to.
Sorry that I didn't explain what the process of unrooting was with GN2. Didn't have time, while with family. That is why I gave you the links.
Click to expand...
Click to collapse
when you install custom roms doesnt that make ota s moot? or does the device still retain updated functionality when using custom rooted rom ?

It all depends on what is going with the OTA. Some OTA updates might enable hardware that was otherwise dormant. LTE sure would be nice...
Hastily spouted for your befuddlement

heiNey said:
would voodoo rootkeeper work for unrooting a stock rom, taking the ota update, then using voodoo again to regain root?
the only thing ive done to my phone is root, but i still want the ota updates for multi-window, etc later on.
Click to expand...
Click to collapse
No, Voodoo rootkeeper would not work here. Not needed either.
When you root Galaxy Note 2 it sets a "Modified" status to your Galaxy Note 2. As long as your Galaxy Note 2 status is set to "Modified" then you can't get OTA updates. This is why you have to flash Stock ROM back into your GN2. I am hoping and believing that you don't have to reset the flash count for this. At least that was not the case with Sprint OTA update version. The OTA updater just checks if you are unmodified or modified. If you are modified then the updater will tell you that you can't update because you are "Modified". Again this is the reason for flashing the Stock unrooted ROM. Once you flash Stock ROM then you will have "Unmodified" status. That is when you will be able to get OTA updates.
Please get the Stock recovering ROM and be ready to flash it when OTA update is ready.
---------- Post added at 07:09 PM ---------- Previous post was at 07:02 PM ----------
Some_dude36 said:
I dont have this phone yet but I know in most android you can disable updates in the settings so you dont run into those kinda problems
---------- Post added at 02:14 AM ---------- Previous post was at 02:11 AM ----------
when you install custom roms doesnt that make ota s moot? or does the device still retain updated functionality when using custom rooted rom ?
Click to expand...
Click to collapse
Yes, root disables the updates through the status of "Modified". In fact when you try to update it says that you can't update because your GN2 is "Modified". But there are reasons that people want OTA updates: If you want your Multi-window feature, Swift Key Flow keyboard w/ S pen write to text, etc then you want the OTA update. If you want the LTE enable when T-Mobile rolls out LTE, then you want OTA update at that time And I can go on....
That is why people are asking these very good questions.

And in either case, within 24 hrs of any updates being released we'll have that rom in a .zip here on xda pre-rooted and ready to flash. I don't mess with counters, rooting/unrooting, etc... It'll be here!

farfromovin said:
And in either case, within 24 hrs of any updates being released we'll have that rom in a .zip here on xda pre-rooted and ready to flash. I don't mess with counters, rooting/unrooting, etc... It'll be here!
Click to expand...
Click to collapse
Firstly messing with counters is mostly likely not needed. So that should not be a worry. Just to be noted.
Secondly, I hope that you are correct on that. But I been there thinking that community would do so but didn't. And least not for a while. And when they did found ways around to root again, it was not the way we wanted it. So I learned to not to put all my eggs in one basket.
Flashing Stock recovery ROM, taking the OTA updates, then root again is one of the baskets that all should have. If you don't need then no harm done. But if need and don't have it then harm done. A solution to the problem until another solution comes by.

heiNey said:
would voodoo rootkeeper work for unrooting a stock rom, taking the ota update, then using voodoo again to regain root?
the only thing ive done to my phone is root, but i still want the ota updates for multi-window, etc later on.
Click to expand...
Click to collapse
I was wondering this as well. In the past I have had success with getting updates and using apps that required root by simply using the Voodoo OTA Rootkeeper app, but I don't know if it will work on this particular phone or not.
I suppose it's worth a shot to at least try when an update rolls around because if it works it's a lot easier than flashing back to stock and re-rooting again.
*Edit: Ah never mind, saw JaguarXT's reply saying it won't work. In that case I think I will hold off rooting the Note II for the time being.

JaguarXT said:
No, Voodoo rootkeeper would not work here. Not needed either.
When you root Galaxy Note 2 it sets a "Modified" status to your Galaxy Note 2. As long as your Galaxy Note 2 status is set to "Modified" then you can't get OTA updates. This is why you have to flash Stock ROM back into your GN2. I am hoping and believing that you don't have to reset the flash count for this. At least that was not the case with Sprint OTA update version. The OTA updater just checks if you are unmodified or modified. If you are modified then the updater will tell you that you can't update because you are "Modified". Again this is the reason for flashing the Stock unrooted ROM. Once you flash Stock ROM then you will have "Unmodified" status. That is when you will be able to get OTA updates.
Click to expand...
Click to collapse
I am currently rooted and do not show the "Modified" status. I am also able to check for OTA updates. I believe it is bad information like this which is allowing people to feel it's OK to run amok with their phones. I feel this promotes the "need" for ROMs when most users could simply sit down with a launcher and customize it exactly the way they want it without a custom ROM. Now if I was getting some amazing battery life, or additional functionality that I can't live without, I might look at a ROM or two, but this isn't a Nexus, and stock\rooted\personalized works for me.
For those wanting to ROOT only, and that would be my recommendation, follow these instructions and STOP where he says STOP HERE.
http://forum.xda-developers.com/showthread.php?t=1975560

Here is a couple of screen shots of what I was talking about. After stock recovery ROM no more "Modified" and can accept updates. Only after rooting get "Modified". Right I am rooted for backup and for AutoStarts app. But I did tried methods and know what works.
This is the method I know and tried of going back to stock and ready for OTA.
Sent from my SGH-T889 using xda premium

double post

mdt73 said:
Now if I was getting some amazing battery life, or additional functionality that I can't live without, I might look at a ROM or two, but this isn't a Nexus, and stock\rooted\personalized works for me.
Click to expand...
Click to collapse
That's exactly where I am in all this. I plan NO custom roms because I'm sick of my phone not working.
I just want to do a few things that require root on the stock rom and for the things I want, I don't need a custom recovery.

samsung galaxy s3 sgh-t999v mobilicity shows up as Modified

Hi, I recently got a galaxy s3 (canadian version) 2 weeks ago from Mobilicity and just recently rooted following this method : http://forum.xda-developers.com/showthread.php?t=1771687. Before doing the rooting I was on the JB 4.1.1 update they released recently. Also used this method: http://forum.xda-developers.com/showpost.php?p=34661189&postcount=1 to unlock the phone
I would check daily but today I just noticed my device's status was Modified and I am unable to check for updates. I'm not sure what caused the modified status. I checked in download mode and my count is still 0/No. I also checked Triangle Away and it was the same. My device was normal when I first installed and used the root, I can only remember I just updated a few apps yesterday. I tried flashing with odin the rooted system image and it's the same.
I would like to be able to use the stock rom with root and updates, and set my device to normal status (I'd rather not update through Odin every time there is an update, and I am very satisfied with the stock rom). I've already backed up my data using Titaniumbackup, all my contact info and music (the stuff I only care about). Help appreciated.
EDIT: I also have installed Openrecovery script using goomanager, could that be the issue?

Use TriangleAway from the Play Store to get rid of the modified status

adslee said:
Use TriangleAway from the Play Store to get rid of the modified status
Click to expand...
Click to collapse
The counter is 0, should I still try to reset it?
Edit: just used TriangleAway, device status still modified, I can access the software update now though, but it gets stuck while checking

bump

You will not be able update via your carrier OAT if you rooted your device. The only thing you can do is to unroot the device, do the update, and re-root the device again. Visit www.galaxys3root.com on how to root and re-root.

Ganbara_Knight said:
You will not be able update via your carrier OAT if you rooted your device. The only thing you can do is to unroot the device, do the update, and re-root the device again.
Click to expand...
Click to collapse
yeah I was starting think that, I'll just get the updates using odin

deadmanrevolver said:
I would like to be able to use the stock rom with root and updates, and set my device to normal status (I'd rather not update through Odin every time there is an update, and I am very satisfied with the stock rom). I've already backed up my data using Titaniumbackup, all my contact info and music (the stuff I only care about). Help appreciated.
EDIT: I also have installed Openrecovery script using goomanager, could that be the issue?
Click to expand...
Click to collapse
If that is all you wanted just flashing the root66 rom from mrRobinson's threat in you original post could have accomplished it.
This would not trip the flash counter if it was still 0, what did it was installing a custom recovery like open recovery.
Follow this steps to get to a 4.1.1 "unmodified" or normal stock system with only root injected to it. You will be able to check and receive OTA updates, but if you ever update your rom OTA you will loose root.
1-download root66 jellybean rom for mobilicity from mrRobinson's thread, there are instructions there how to flash it with desktop Odin. (this will keep everything in your rom and will give you the stock recovery back, so the counter does not trip again)
2-download, install and run triangle away from chainfire's thread this will reset the counter to 0. Search for it.
Now your counter is 0 again, nothing is tripping it, room is rooted but it will still say "modified" and OTA updates may still not work, to fix it you need a clean start. Do a system factory reset, start over fresh and life will be beautiful.
Sent from my SGH-T999 using xda premium

[Q] Stupid question, because I am bone head!

I recently re-flashed my phone because I was unable to get it back to stock un-rooted so I could get the latest 4.4 update. Someone suggested using Triangle Away to reset my flash counter in order to show my phone was 'not modified'. I purchased Triangle Away installed etc, but it had a stern warning that resetting my flash counter could "hard brick" my phone.
I attempted to use the temporary disable of SU for OTA within Triangle Away to unroot my phone and apply the update, unfortunately the update didn't work and now I can not undo put back SU as enabled. My phone is unrooted without the ability to undo that feature in Triangle Away.
Question, is there a way to fix this with Triangle Away? Am I missing something or do I have to reflash my phone again?
Why would an app like Triangle Away have a feature within it's app that could cause this to happen and not a way to back out of it.
I hope someone can help me with this.:crying:

bigmtnskier said:
I recently re-flashed my phone because I was unable to get it back to stock un-rooted so I could get the latest 4.4 update. Someone suggested using Triangle Away to reset my flash counter in order to show my phone was 'not modified'. I purchased Triangle Away installed etc, but it had a stern warning that resetting my flash counter could "hard brick" my phone.
I attempted to use the temporary disable of SU for OTA within Triangle Away to unroot my phone and apply the update, unfortunately the update didn't work and now I can not undo put back SU as enabled. My phone is unrooted without the ability to undo that feature in Triangle Away.
Question, is there a way to fix this with Triangle Away? Am I missing something or do I have to reflash my phone again?
Why would an app like Triangle Away have a feature within it's app that could cause this to happen and not a way to back out of it.
I hope someone can help me with this.:crying:
Click to expand...
Click to collapse
Maybe I should ask the question more simply:
How do I re-ROOT my phone without flashing? Is that possible?

bigmtnskier said:
Maybe I should ask the question more simply:
How do I re-ROOT my phone without flashing? Is that possible?
Click to expand...
Click to collapse
Do u still have a custom recovery? If so, maybe flash the team epic root from recovery zip?

DMF1977 said:
Do u still have a custom recovery? If so, maybe flash the team epic root from recovery zip?
Click to expand...
Click to collapse
I do have a custom recovery, TWRP. I think I have it running again and rooted, what I did was re-install Busybox and rebooted into recovery, then rebooted back into the System and then it seemed to work fine. Not sure if I will brave Triangle Away again, but thank you for responding and offering a good suggestion.:good:

bigmtnskier said:
I purchased Triangle Away installed etc, but it had a stern warning that resetting my flash counter could "hard brick" my phone.
Click to expand...
Click to collapse
Did you reset your flash counter? As far as I know this was put in place by the developer to warn people...Of knowing what they are doing before hand. This warning is mainly in place to try and make people read to see if their phone model is supported.
To the best of my knowledge, no one has hard bricked their phone on any of the I747(m) models using this app. This feature does work as I have used it multiple times.
And what update our ROM are you installing? You said 4.4... I used ODIN to restore back to complete stock 4.1.1 (not rooted, stock recovery included) and the OTA update to stock 4.1.2 went without a hitch. I used CF Auto Root (via ODIN) to root and then installed a custom recovery.
Sent from my SAMSUNG-SGH-I747

aybarrap1 said:
Did you reset your flash counter? As far as I know this was put in place by the developer to warn people...Of knowing what they are doing before hand. This warning is mainly in place to try and make people read to see if their phone model is supported.
To the best of my knowledge, no one has hard bricked their phone on any of the I747(m) models using this app. This feature does work as I have used it multiple times.
And what update our ROM are you installing? You said 4.4... I used ODIN to restore back to complete stock 4.1.1 (not rooted, stock recovery included) and the OTA update to stock 4.1.2 went without a hitch. I used CF Auto Root (via ODIN) to root and then installed a custom recovery.
Sent from my SAMSUNG-SGH-I747
Click to expand...
Click to collapse
I was attempting to do the OTA to go from 4.0.4 ICS to 4.1.x Jellybean. BTW, I was able to re-set my count to 0! Thank you for the reassurance!

bigmtnskier said:
I was attempting to do the OTA to go from 4.0.4 ICS to 4.1.x Jellybean. BTW, I was able to re-set my count to 0! Thank you for the reassurance!
Click to expand...
Click to collapse
I would highly recommend flashing the pure stock 4.1.1 rom (including stock recovery) and then do the OTA. The 4.1.2 stock rom might be available through KIES or through other sites by now, but I can't say for certain. Since you are already using ODIN, then CF auto root will be a breeze for you to root 4.1.2.
No worries. I was a little nervous too about Triangle Away at first but searching did not net anything saying that reseting the flash counter had hard bricked someone's phone. That is what pushed me to use it.

aybarrap1 said:
I would highly recommend flashing the pure stock 4.1.1 rom (including stock recovery) and then do the OTA. The 4.1.2 stock rom might be available through KIES or through other sites by now, but I can't say for certain. Since you are already using ODIN, then CF auto root will be a breeze for you to root 4.1.2.
No worries. I was a little nervous too about Triangle Away at first but searching did not net anything saying that reseting the flash counter had hard bricked someone's phone. That is what pushed me to use it.
Click to expand...
Click to collapse
I blew out Kies on my main machine because it doesn't work well, I had to re-set all my USB ports and re-install the Samsung USB drivers so no Kies for me. But where do I find a stock 4.1.1 rom from? My stock version is 4.0.4 (the original ROM when the S3 was released), I wonder if I can just use a custom 4.1.1 ROM instead or do you think it would work if I unroot/stock to 4.0.4 then OTA to 4.1.2?

bigmtnskier said:
I blew out Kies on my main machine because it doesn't work well, I had to re-set all my USB ports and re-install the Samsung USB drivers so no Kies for me. But where do I find a stock 4.1.1 rom from? My stock version is 4.0.4 (the original ROM when the S3 was released), I wonder if I can just use a custom 4.1.1 ROM instead or do you think it would work if I unroot/stock to 4.0.4 then OTA to 4.1.2?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1968625
Flash in Odin..

bigmtnskier said:
I blew out Kies on my main machine because it doesn't work well, I had to re-set all my USB ports and re-install the Samsung USB drivers so no Kies for me. But where do I find a stock 4.1.1 rom from? My stock version is 4.0.4 (the original ROM when the S3 was released), I wonder if I can just use a custom 4.1.1 ROM instead or do you think it would work if I unroot/stock to 4.0.4 then OTA to 4.1.2?
Click to expand...
Click to collapse
To ensure best results use ODIN to flash the stock ROM to 4.1.1. You should return the phone stock as if you just purchased from the store new. Then do the OTA. You can use ODIN after that to root with CF Auto root.
Sent from my SAMSUNG-SGH-I747

Updating(OTA) to 4.3 with root?

I have looked around and can't seem to get a straight answer about this. I have a stock rooted gn2, if i update over the air will it brick it? At the moment i have the att updater frozen with titanium backup. Any insight would be greatly appreciated, happy holiday!

where have you been searching? This has been covered dozens of times...

sorry
could you possibly provide a link sir?

generally speaking you can NOT take/install any OTA update when you are rooted...most OTA updates wont install if a custom recovery is detected.
99% of the time it wont work, .09% of the time it might install but you will have all sorts of issues, and .01% of the time it will work..
I think that pretty much covers it; you should probably just be patient and wait until the dev's incorporate it into a custom rom, and then you wont have to unroot to "enjoy" what ever the wonderful features are that ATT was so kind to include in their update..

And the install checks for stock system

You can install if you have stock rom. Root doesn't matter. My phone was rooted with stock room and twrp recovery. I just flashed stock recovery back. I had my superuser integrated in system partition. After Ota, i upgraded superuser apk. It then disabled Knox and download latest su binary.
So successful update with root preserved. Pm me of you need help
Sent from my SAMSUNG-SGH-I317 using Tapatalk

WARNING :
If you take the official OTA to 4.3 while root is present...you WILL trip the KNOX counter in your boot loader.
And if you root after an official 4.3 update you WILL trip KNOX anyway..
My .02....DO NOT UPDATE....
Stay rooted on the old bootloader and flash a custom 4.3 rom.....g

Wife is getting a new AT&T note 2 on the 24th (it already shipped). I would assume it doesn't have the OTA on it yet. Can you just reject the OTA when it arrives? Or will it try to install automatically on the new phone. Any way to prevent that until I can get my hands on it (have time tio mess with it).

Anyone try flashing a rom After ota update?
Did you thank your Developer today?

Same boat
I too have a stock rooted 4.1.2. OTA fails as root present, got that. All I need is a stock 4.3 root. I have read several posts and still unclear as to what to do. I have either missed it or just not found the answer.
Do I need to unroot via SuperSU? then OTA? Odin flash a stock ROM?
Please don't bash as I am only seeking an answer. And any help is greatly appreciated!

cordless89 said:
I too have a stock rooted 4.1.2. OTA fails as root present, got that. All I need is a stock 4.3 root. I have read several posts and still unclear as to what to do. I have either missed it or just not found the answer.
Do I need to unroot via SuperSU? then OTA? Odin flash a stock ROM?
Please don't bash as I am only seeking an answer. And any help is greatly appreciated!
Click to expand...
Click to collapse
I had stock rooted 4.1.2 with cwm as my recovery. I did the ota update. After the update, cwm wanted to fix root but couldn't. Essentially I lost root. Next, I re-rooted with CF-Auto-Root. I then installed SuperSU from play store which disabled Knox. Using GooManager I flashed TWRP. The last issue was wifi wasn't working. I used Odin to flash this file: http://d-h.st/OYC (unzip and use the tar in Odin). Wifi restored. Overall I like this update. It's faster and smoother.
Having said all this, I do not recommend anyone use this method. It's much cleaner to unroot then update. Or better yet, as suggested before, use one of the custom 4.3 roms.

flymacs said:
I had stock rooted 4.1.2 with cwm as my recovery. I did the ota update. After the update, cwm wanted to fix root but couldn't. Essentially I lost root. Next, I re-rooted with CF-Auto-Root. I then installed SuperSU from play store which disabled Knox. Using GooManager I flashed TWRP. The last issue was wifi wasn't working. I used Odin to flash this file: link removed (unzip and use the tar in Odin). Wifi restored. Overall I like this update. It's faster and smoother.
Having said all this, I do not recommend anyone use this method. It's much cleaner to unroot then update. Or better yet, as suggested before, use one of the custom 4.3 roms.
Click to expand...
Click to collapse
I noticed the OTA did not work on my nine as I got the "unable to update" after the OTA downloaded. I initially rooted via the CF-Auto flash.
Just curious as to next step.

flymacs said:
I had stock rooted 4.1.2 with cwm as my recovery. I did the ota update. After the update, cwm wanted to fix root but couldn't. Essentially I lost root. Next, I re-rooted with CF-Auto-Root. I then installed SuperSU from play store which disabled Knox. Using GooManager I flashed TWRP. The last issue was wifi wasn't working. I used Odin to flash this file: http://d-h.st/OYC (unzip and use the tar in Odin). Wifi restored. Overall I like this update. It's faster and smoother.
Having said all this, I do not recommend anyone use this method. It's much cleaner to unroot then update. Or better yet, as suggested before, use one of the custom 4.3 roms.
Click to expand...
Click to collapse
So you had no trouble flashing TWRP? I went back to 4.1.1 from Skynote, OTA'd 4.1.2 and was going to flash another ROM but my wife got my phone the next morning to play slots and she accepted the 4.3 official update before I woke up. I did root with CF Auto and disabled Knox, but was wondering if Goomanager would work.
The next question is can we flash some ROMS with the rooted OTA 4.3?
Geeve

Is there a pre-rooted stock 4.3 for the i317 AT&T available?

geeve420 said:
So you had no trouble flashing TWRP? I went back to 4.1.1 from Skynote, OTA'd 4.1.2 and was going to flash another ROM but my wife got my phone the next morning to play slots and she accepted the 4.3 official update before I woke up. I did root with CF Auto and disabled Knox, but was wondering if Goomanager would work.
The next question is can we flash some ROMS with the rooted OTA 4.3?
Geeve
Click to expand...
Click to collapse
Goomanager worked fine. No problems with twrp either.
As far as flashing on from ota 4.3, I'm not brave enough yet.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
---------- Post added at 01:24 PM ---------- Previous post was at 01:17 PM ----------
cordless89 said:
I noticed the OTA did not work on my nine as I got the "unable to update" after the OTA downloaded. I initially rooted via the CF-Auto flash.
Just curious as to next step.
Click to expand...
Click to collapse
Did you debloat or remove any apps from the stock 4.1.2?

flymacs said:
Goomanager worked fine. No problems with twrp either.
As far as flashing on from ota 4.3, I'm not brave enough yet.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
---------- Post added at 01:24 PM ---------- Previous post was at 01:17 PM ----------
Did you debloat or remove any apps from the stock 4.1.2?
Click to expand...
Click to collapse
Nope, pretty much as stock as you can get plus root. OTA failed but I assume reason being the root... but I'm a newbie on this stuff.

cordless89 said:
Nope, pretty much as stock as you can get plus root. OTA failed but I assume reason being the root... but I'm a newbie on this stuff.
Click to expand...
Click to collapse
Then the next question I have is if you are using the stock recovery? I was using cwm on stock rooted 4.1.2. When I did the ota, the phone rebooted into cwm. Cwm asked if I wanted to do the update. I selected yes. When it completed, the Samsung installer gave a failed to install message, but cwm showed that it completed and wanted to fix root. It couldn't fix since I was unrooted at this point. I rebooted into 4.3 non-rooted. Re-rooted...etc.
I want to say again that I don't recommend anyone follow this procedure. I'm just trying to describe how I solved my own mess and hopefully answer any questions.

[Q] Plz Help 4.3 down to 4.1.2. rooted tried a few

So I'm by no means super knowledgable with this stuff but I've rooted a few phones, played around with CM on my old evo but for the most part I enjoy rooted stock.
I have Galaxy S3 Sprint 4.3 updated OTA from a rooted (4.1.2). When I took the OTA I lost root, no big deal I used Odin and flashed the CF auto root, it said it removed knox and I had root back. Cool!
In short 4.3 sucked, wanted to downgrade back so things like TrevE mod would work again and it wouldn't be so buggy. I tried to use odin to flash "KIES_HOME_L710VPBMD4_L710SPRBMD4_1130792_REV03_user_low_ship.tar.md5" but it gave me the "Use Kies Recovery and error occured" message.
So I then used odin and flashed TWRP and my phone booted.
I'm back on 4.3 rooted.
I've tried picking through the forums and interwebz for answers but I get mixed messages and info on international versions and what not.
I'm tired of trying to figure it out and really could use some help downgrading back to 4.1.2
Thanks,
Brandon

mentorkyrom said:
So I'm by no means super knowledgable with this stuff but I've rooted a few phones, played around with CM on my old evo but for the most part I enjoy rooted stock.
I have Galaxy S3 Sprint 4.3 updated OTA from a rooted (4.1.2). When I took the OTA I lost root, no big deal I used Odin and flashed the CF auto root, it said it removed knox and I had root back. Cool!
In short 4.3 sucked, wanted to downgrade back so things like TrevE mod would work again and it wouldn't be so buggy. I tried to use odin to flash "KIES_HOME_L710VPBMD4_L710SPRBMD4_1130792_REV03_user_low_ship.tar.md5" but it gave me the "Use Kies Recovery and error occured" message.
So I then used odin and flashed TWRP and my phone booted.
I'm back on 4.3 rooted.
I've tried picking through the forums and interwebz for answers but I get mixed messages and info on international versions and what not.
I'm tired of trying to figure it out and really could use some help downgrading back to 4.1.2
Thanks,
Brandon
Click to expand...
Click to collapse
The 4.3 OTA installed a locked bootloader, which will prevent you from ODIN'ing back to a previous version. you can flash any ROM you would like from recovery, you CANNOT downgrade the bootloader. As of right now, if you have knox, you are stuck with it.
You are extremely lucky that you didn't brick your phone by using odin to flash a non-4.3 tar. I wouldnt try again.
My advice is, remain rooted with a custom recovery, and find a ROM to your liking, and flash that.
I have also heard that we cannot flash custom kernels on the knox (MK3) bootloader as well, but I havent verified that.

eletendre84 said:
The 4.3 OTA installed a locked bootloader, which will prevent you from ODIN'ing back to a previous version. you can flash any ROM you would like from recovery, you CANNOT downgrade the bootloader. As of right now, if you have knox, you are stuck with it.
You are extremely lucky that you didn't brick your phone by using odin to flash a non-4.3 tar. I wouldnt try again.
My advice is, remain rooted with a custom recovery, and find a ROM to your liking, and flash that.
I have also heard that we cannot flash custom kernels on the knox (MK3) bootloader as well, but I havent verified that.
Click to expand...
Click to collapse
Thank you for the response. Is CyanogenMod an option then? If I go to CM could I flash back a stock 4.3 rom in the future?
As an added bonus question does CM allow wifi tethering?
Again thank you for the response.

mentorkyrom said:
Thank you for the response. Is CyanogenMod an option then? If I go to CM could I flash back a stock 4.3 rom in the future?
As an added bonus question does CM allow wifi tethering?
Again thank you for the response.
Click to expand...
Click to collapse
CM is certainly an option. In fact, its what i am running now. CM11 12-24. Runs great. You can always odin the stock mk3 tar and go back to stock unrooted, at any time.
in order to flash cm11 you MUST be on TWRP 2.6.3.1 or CWM 6.0.4.5 or newer or the assert check will fail.
not sure on the tethering, but im pretty sure it definitely works on cm10.2 and i think it does on 11 as well, but dont quote me on that.

eletendre84 said:
CM is certainly an option. In fact, its what i am running now. CM11 12-24. Runs great. You can always odin the stock mk3 tar and go back to stock unrooted, at any time.
in order to flash cm11 you MUST be on TWRP 2.6.3.1 or CWM 6.0.4.5 or newer or the assert check will fail.
not sure on the tethering, but im pretty sure it definitely works on cm10.2 and i think it does on 11 as well, but dont quote me on that.
Click to expand...
Click to collapse
Tethering is available on CM11 just like it was on 10.2; would strongly recommend latest Philz Touch Recovery over either TWRP or CWM though. Although it is based on CWM, it has proven to be pretty much the superior recovery option for flashing any Android build number, plus it is highly customizable.
Philz Touch Recovery

this is how to downgrade
mentorkyrom said:
So I'm by no means super knowledgable with this stuff but I've rooted a few phones, played around with CM on my old evo but for the most part I enjoy rooted stock.
I have Galaxy S3 Sprint 4.3 updated OTA from a rooted (4.1.2). When I took the OTA I lost root, no big deal I used Odin and flashed the CF auto root, it said it removed knox and I had root back. Cool!
In short 4.3 sucked, wanted to downgrade back so things like TrevE mod would work again and it wouldn't be so buggy. I tried to use odin to flash "KIES_HOME_L710VPBMD4_L710SPRBMD4_1130792_REV03_user_low_ship.tar.md5" but it gave me the "Use Kies Recovery and error occured" message.
So I then used odin and flashed TWRP and my phone booted.
I'm back on 4.3 rooted.
I've tried picking through the forums and interwebz for answers but I get mixed messages and info on international versions and what not.
I'm tired of trying to figure it out and really could use some help downgrading back to 4.1.2
Thanks,
Brandon
Click to expand...
Click to collapse
do a factory data reset then use odin auto root from computer ok...... after boot u will get a security message supersu will be unfortunately stopping this is ok..... then u will need to download the supersu.app to root of sd then manually install this will update it and now u can turn off knox and have root... then go to market and download odin mobile then flash your .tar file u want and you will be good to go 4.1.2 doesn't have knox and has a unlocked bootloader so have fun bro this method may work for other phones

smuther22 said:
do a factory data reset then use odin auto root from computer ok...... after boot u will get a security message supersu will be unfortunately stopping this is ok..... then u will need to download the supersu.app to root of sd then manually install this will update it and now u can turn off knox and have root... then go to market and download odin mobile then flash your .tar file u want and you will be good to go 4.1.2 doesn't have knox and has a unlocked bootloader so have fun bro this method may work for other phones
Click to expand...
Click to collapse
Do you realize that this thread hasn't been used in a couple of months? I would assume the author has no more need of advice based on the inactivity. Also, once Knox is installed, it is on the phone to stay. PERIOD. NO DOWNGRADING POSSIBLE VIA ODIN. Custom ROMs of any build are fine via custom recovery, but any attempt to change the bootloader will trigger Knox and brick the phone. Dangerous info to be posting here, especially since someone else who doesn't know better might try this.