Will the method described here [HOWTO] [ROOT] No Tripping Flash Counter - Updated [ATT / Bell / Telus / Rogers]Share Thread:
work with a phone that is already rooted under 4.0.3 or must the phone first be un-rooted? Thanks.
Its an Odin flash, so it rewrites everything. You can use it, but if your already rooted, why would you want to reroot?
I rooted under the original UCLEM 4.0.3 so if I can re-root directly it saves the effort to un-root to stock before re-rooting to stock with root. Does that make sense?
Not to me, but that's not abnormal for me.
Since I don't have enough posts to post in the Dev. forums I would like to thank mr Robinson here for the excellent tutorial and necessary files to root my S3 stock. Thanks man you are exceptioal.
FYI: I rooted over a previous CWM root with no issues. Used an old charge/data cable from my previous Palm Pre+ which worked fine. The firmware is now listed as Official not Custom and the flash counter has gone from 3 to 2.
Fwiw, Triangle Away will reset your flash counter, should you ever need to return for warranty.
Thanks again for the information re: Triangle Away.
Related
Hey guys, I know there are a few stock images floating around that can bring you back to stock, but I wanted to put down the steps I used to get back to stock with 0 flash counter.
Just in case you need to return it for warranty work and you've flashed or rooted. This is kind of a beginner's guide to going back to stock untouched.
--Doing this is your own responsibility and I offer nothing but what is in this post.
1. Use Odin to flash the stock rom. Found here -teshxx
2. Now use Chainfire's root without different recovery. Found here -Chainfire
3. Now install triangle away via the play store or apk found at Chainfire's thread and use it. Here -Chainfire
4. Finally Odin again with the stock rom found at step 1.
The idea is that booting with a non stock recovery will trip the flash counter. Also, running a rooted rom will register "Modified" with tmobile touchwiz.
This way you can reset the flash counter and it won't be tripped by a non-stock recovery. Then remove the "Modified" device flag by going back to stock.
I know the faster way to do this would be to catch the reboot after triangle away, but if you can do that, I assume you already are pretty proficient at going back for warranty work.
Also, if and when a stock root injected odin rom becomes available, this tutorial will be pointless.
In my days with the s3, even after using odin to go back to fully stock like in step 4, sometimes it woukd still show modified until I ran a factory reset.
I am super sorry if this has been covered, but I have indeed searched, several sites, and I haven't found anything on my specific problem. I had my Galaxy S3 rooted for a time then decided to unroot it. The unroot worked and the phone status now says "normal," but I still cannot receive any OTA updates and my flash counter does not say "0." I suppose my first question is would resetting the flash counter solve the problem with getting the updates? And if so, How can I go about doing that with an already unrooted phone? I searched through the thread here:
http://forum.xda-developers.com/showthread.php?t=1904099
- but was not allowed to post in it since I'm a noob. Thanks for any help.
Use triangle away to reset the flash counter, however you will need to reroot to run triangle away and then unroot again once your finished.
Could always PM the OP of the thread. Sure he wouldnt mind :laugh: That being said, flash the jb version of that rom. Youll be up to date w/ no root and a counter at 0.
Thanks. I'll reroot then follow that thread's guide and use the rom files linked. I know enough about rooting to root, but if I ever run into an issue, I have no idea what I'm doing. We all appreciate your guys' help!
Stupid question, but I want to be sure. I can easily root, then use the triangle away app. But, when I go to unroot, am I just using the JB.zip file from the above mentioned thread and that itself will unroot? Or do I unroot completely first then flash that zip?
Sorry, maybe is offtopic but I need this information badly...
I rooted my GS3 and installed some Incredible HD rom...now, I wanted to get back to stock rom! So, I restored to my Stock rom which I previously backed up in clockwork recovery...Now I have a stock rom but UNABLE to update my phone via KIES or OTA????? It sais > your device curred fw isnt supported ....
What should I do? Should I reset my flash counter or unroot it first before update or what???
THANKSSSS
I'm running a rooted stock I317M with nothing modified except for root. I used mrRobinson's thread h t t p :/ / forum.xda-developers.com/showthread.php?t=2004650 as a guide which worked perfectly to keep everything stock (and thus avoid tripping the flash counter) but gave me root. This morning the Canadian carriers began rolling out the 4.1.2 update OTA which failed a few times on my device so I used (GASP!) Kies to do the update. Not sure if it would have mattered OTA or Kies but I have now lost root. Has anyone managed to inject root into a stock image for the I317m yet? It looks like I could go with a custom AT&T I317 build or ADB in and manually install a custom recovery, root etc. but if possible I'm hoping to keep normal device status and not trip the flash counter.
Are you planning on turning your phone in for warranty anytime soon or do you just like the look of "Official" instead of "Modified" on your About Phone settings?
Exact same thing happened for mine, stock rooted Canadian OTA to 4.1.2 failed repeatedly, Had to use Kies as well and lost root. The main reason I wanted root was to switch off fast dormancy since my Canadian carrier doesn't support it and was killing battery. Good news is it stayed switched off.
[email protected] said:
Are you planning on turning your phone in for warranty anytime soon or do you just like the look of "Official" instead of "Modified" on your About Phone settings?
Click to expand...
Click to collapse
Not really. Originally it was just to make sure I'd get the update without issue when it was released. My understanding is that I can always reflash with the stock firmware I have from Sammobile and it will reset the flash counter + set the status back to normal if the need arose but also thought it easier to just unroot, reboot and uninstall SU if possible.
chris19000 said:
Not really. Originally it was just to make sure I'd get the update without issue when it was released. My understanding is that I can always reflash with the stock firmware I have from Sammobile and it will reset the flash counter + set the status back to normal if the need arose but also thought it easier to just unroot, reboot and uninstall SU if possible.
Click to expand...
Click to collapse
Cool.... Honestly, I never worry about tripping the counter unless I need to turn in for replacement/warranty repair. Apparently, this seems to work just fine: http://forum.xda-developers.com/showthread.php?t=2073141&highlight=lost+root
m4runner said:
Exact same thing happened for mine, stock rooted Canadian OTA to 4.1.2 failed repeatedly, Had to use Kies as well and lost root. The main reason I wanted root was to switch off fast dormancy since my Canadian carrier doesn't support it and was killing battery. Good news is it stayed switched off.
Click to expand...
Click to collapse
First time I've actually heard of fast dormancy. My battery life has actually been pretty good and that with fairly varied, heavy use. Have to look more into it. I rooted primarily for backing up (TB), remote file sharing and just plain messing around.
[email protected] said:
Cool.... Honestly, I never worry about tripping the counter unless I need to turn in for replacement/warranty repair. Apparently, this seems to work just fine: http://forum.xda-developers.com/showthread.php?t=2073141&highlight=lost+root
Click to expand...
Click to collapse
Thanks R1K, I looked at that earlier and still might try it after a little more in depth reading if nothing else presents itself. I use the camera fairly extensively and although it looks like the camera is only affected when patching the exploit I have to be a little cautious since I use it for work. Plus the easy unroot/stock return part :good:
m4runner said:
Exact same thing happened for mine, stock rooted Canadian OTA to 4.1.2 failed repeatedly, Had to use Kies as well and lost root. The main reason I wanted root was to switch off fast dormancy since my Canadian carrier doesn't support it and was killing battery. Good news is it stayed switched off.
Click to expand...
Click to collapse
One option which is what I did, was to download the 4.1.2 update from sammobile.
I then used mobile odin to flash it which has the ability to protect root.
So now I am stock rooted on latest firmware device status is normal
---------- Post added at 04:54 PM ---------- Previous post was at 04:42 PM ----------
[email protected] said:
Cool.... Honestly, I never worry about tripping the counter unless I need to turn in for replacement/warranty repair. Apparently, this seems to work just fine: http://forum.xda-developers.com/showthread.php?t=2073141&highlight=lost+root
Click to expand...
Click to collapse
Doubt this will work.
The whole way this gained root was via the exynos exploit.
This firmware I am pretty sure has patched it.
Exynos abuse says no but voodoo app says yes.
I can confirm the exploit is patched in this new firmware so I suspect this will close any holes used by exynos abuse app to root phone.
Canadoc said:
One option which is what I did, was to download the 4.1.2 update from sammobile.
I then used mobile odin to flash it which has the ability to protect root.
So now I am stock rooted on latest firmware device status is normal
---------- Post added at 04:54 PM ---------- Previous post was at 04:42 PM ----------
Doubt this will work.
The whole way this gained root was via the exynos exploit.
This firmware I am pretty sure has patched it.
Exynos abuse says no but voodoo app says yes.
I can confirm the exploit is patched in this new firmware so I suspect this will close any holes used by exynos abuse app to root phone.
Click to expand...
Click to collapse
Thank you Canadoc. Might be the best bet for me too. I did a TB backup just prior to the update so maybe I'll flash back to 4.1.1 with the root injected ROM in odin and then flash the 4.1.2 update from sammobile from mobile odin. Otherwise looks like it might be a custom i317 build for me. CWM sure sounds nice right now
For those trying to get multiveiw update and are rooted.... it is much much easier ti go get the firmware from sammobile.com then flash it with mobile odin with the ever root option.. all done :thumbup:
Sent from my SGH-I317 using xda premium
twanskys204 said:
For those trying to get multiveiw update and are rooted.... it is much much easier ti go get the firmware from sammobile.com then flash it with mobile odin with the ever root option.. all done :thumbup:
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
That's for sure. I'm going to go back to root injected stock 4.1.1 and start from scratch.
chris19000 said:
That's for sure. I'm going to go back to root injected stock 4.1.1 and start from scratch.
Click to expand...
Click to collapse
Worked as planned... more or less. Had to do a factory reset and flash twice to get 4.1.1 to boot but from there installed mobile odin, extracted and flashed from 4.1.2 (from sammobile and copied to external SD) and good to go. Now, if you want to go stock with root and for whatever reason don't want to/can't use mobile odin, head over to this thread http://forum.xda-developers.com/showthread.php?t=2004650&page=26 mrRobinson is working on injecting root into the stock builds.
Cheers.
Which is the better way ?
chris19000 said:
Worked as planned... more or less. Had to do a factory reset and flash twice to get 4.1.1 to boot but from there installed mobile odin, extracted and flashed from 4.1.2 (from sammobile and copied to external SD) and good to go. Now, if you want to go stock with root and for whatever reason don't want to/can't use mobile odin, head over to this thread http://forum.xda-developers.com/showthread.php?t=2004650&page=26 mrRobinson is working on injecting root into the stock builds.
Cheers.
Click to expand...
Click to collapse
I use the Mr. Robinsons thread to stock my device to 4.1.1 but when i did . it always stuck on the Samsung logo after rebooting.
so i have to put my phone in recovery mode and factory restore.
this wasy right now i have root on 4.1.1 .
but i wanna know the best way to update my phone to 4.1.2
becasue i know .. with OTA i will loose my root.
please help.
prashant19p said:
I use the Mr. Robinsons thread to stock my device to 4.1.1 but when i did . it always stuck on the Samsung logo after rebooting.
so i have to put my phone in recovery mode and factory restore.
this wasy right now i have root on 4.1.1 .
but i wanna know the best way to update my phone to 4.1.2
becasue i know .. with OTA i will loose my root.
please help.
Click to expand...
Click to collapse
Hi prashant there are a number of ways you can update OTA without losing root but of the easy ones I can only speak personally about one of them - Mobile Odin - which is what I used. It's a paid app but it gives you the option for EverRoot which maintains root across roms and automatically installs itself and SU in the new rom. Hate to ask, but are you sure you flashed the right rom? He has it listed as the new! Bell rom under January. If you flash that with his directions it should work - that being said though I did have to flash it twice myself to get it to work. One flash with odin, stuck on logo, back to regular recovery, wipe cache, download mode and reflash with odin, worked that time around. By that time I had mobile odin and flashed the regular update without root that way but mobile odin kept my root.
If you're looking to retain or regain root after ota, this is the easiest way imo. Just answered it in this thread.
http://forum.xda-developers.com/showthread.php?t=2156741
Froid said:
If you're looking to retain or regain root after ota, this is the easiest way imo. Just answered it in this thread.
http://forum.xda-developers.com/showthread.php?t=2156741
Click to expand...
Click to collapse
Thanks Froid. SuperSU seemed to work for some folks too if they dropped the dime for the PRO version. I did see some instances where neither worked too though, but not enough details to say why.
all you need to do is just reflash with odin rooted 4.1.1 stock rom then once that is done goto play store and get voodoo ota rootkeeper make backup then temp unroot then get the ota 4.1.2 update when finished goto to ota rootkeeper and restore root works just fine and u keep root.
Ok,
So I recently updated to the stock 4.1.2 image, and I wanted to root because I have always read it was best to have the latest base before rooting. I was able to root using the guides on here, but everything kept force closing and i was unable to do anything with the phone, so i went back to stock because of the problems. What i think was happening was that the rooted image I was using was 4.1.1, and i need 4.1.2.
Could anyone point me to where the 4.1.2 image is that i need to root is so that i can root correctly?
Well, I don't know which method you used before or how you plan on rooting now, but on 4.1.2,
Cf auto root still works.
Casual root still works.
Flashing recovery through Odin then supersu through recovery still works,
I've done them all.
What doesn't work is the No Tripping the flash counter (by flashing the root injected image) root, rooting with motochopper, or the root your phone with your phone root.
You probably know that you need Odin (3.07 preferably) no matter what you do, except I think for Casual;
and also yes you probably flashed a 4.1.1 image over your 4.1.2 data, but a factory reset should have fixed that.
They also have a rooted stock Rom somewhere in the development section if you want it, once you have a custom recovery.
Sent from my SAMSUNG-SGH-I747 using xda premium
I rooted my friends S3 ATT with the s3 toolkit v7.0 he now wants me to unroot it so he can take the 4.3 update it have run the unroot and remove zip multiple times ( I even re rooted it and tried removing it again) and it will not remove clockwork mod recovery even though it says it will, it has successfully unrooted it the phone and removed super user and busy box . he does not want to loose all the data on his phone is there another way to remove clock work mod and get him back to the stock recovery so he can take the 4.3 update with out using triangle away ?
thanks
You would need to flash the stock recovery to replace CWM.
audit13 said:
You would need to flash the stock recovery to replace CWM.
Click to expand...
Click to collapse
where do I acquire a stock recovery and is it flashed through oden or through clockwork ?
thanks
I'm not sure where to find the stock recovery as I have never seen one that is flashable via Odin, CWM, or TWRP.
By updating to stock 4.3, the phone will have a bootloader that cannot be downgraded and Knox will be installed.
I personally avoided the 4.3 update because the 4.3 bootloader makes it tough to go back to stock and tripping the knox counter will void the warranty. Also, knox can interfere with root access.
audit13 said:
I'm not sure where to find the stock recovery as I have never seen one that is flashable via Odin, CWM, or TWRP.
By updating to stock 4.3, the phone will have a bootloader that cannot be downgraded and Knox will be installed.
I personally avoided the 4.3 update because the 4.3 bootloader makes it tough to go back to stock and tripping the knox counter will void the warranty. Also, knox can interfere with root access.
Click to expand...
Click to collapse
actually I'm a blind idiot it is an option right in the tool kit i have just reflashed it and all is good
THANK YOU VERY MUCH I could not have fixed this with out your help
(he never used any custom roms and does not mind that his unit will be locked )
iiipm said:
actually I'm a blind idiot it is an option right in the tool kit i have just reflashed it and all is good
THANK YOU VERY MUCH I could not have fixed this with out your help
(he never used any custom roms and does not mind that his unit will be locked )
Click to expand...
Click to collapse
Hey, thanks for the post. I learned something too:good: