Related
I realize this may have been asked before and if so i want to apologize in advance. First off Im an android NOOB. Long time iphone user and jailbreaker. Anyhow, I rooted my ATT Samsung Galaxy note 2 with CWM6, I also made a backup after installing this from inside recovery. I believe that is what its called anyhow. I then tryed Jedi X and CleanRom 3.0.1. After giving these 2 a try I realized I prefer stock and set out to go back to that. I followed all the instruction that are listed on the pages within XDA. Ran triangle away and removed SU. After reboot Im still sitting in a modified status.
Now according to Triangle Away documentation this can happen. And I need to install a stock firmware. Im currently downloading that from a link on this site.
I re-rooted and installed triangle away.
My question is what order should everuthing be done? Im guessing, 1, flash stock recovery. 2, run triangle away, Uninstall SuperSU 4 flash factory firmware. Is this correct? Also, how do I flash factory firmware? Do I use factory recovery mode to do this?
Thanks so much for the help in advance.
By flashing factory firmware you are tripping the counter again. If you are already on stock firmware and just rooted look here.
1. Factory reset
2. Restore stock rooted backup
3. Click on thread below
4. Post in thread questions press thanks if it helped.
http://forum.xda-developers.com/showthread.php?t=2020607
Sent from my GT-N7105 using xda premium
Android The Greek said:
By flashing factory firmware you are tripping the counter again. If you are already on stock firmware and just rooted look here.
1. Factory reset
2. Restore stock rooted backup
3. Click on thread below
4. Post in thread questions press thanks if it helped.
http://forum.xda-developers.com/showthread.php?t=2020607
Sent from my GT-N7105 using xda premium
Click to expand...
Click to collapse
Flashing a stock rom through Odin does not trip the counter
Sent from my Bell Note II
If you do triangle away, then go into download mode, then flash stock rom you will trip the counter.... you should have stock rom on before triangle away. Then triangle away. Then unroot.
Sent from my GT-N7105 using xda premium
Android The Greek said:
If you do triangle away, then go into download mode, then flash stock rom you will trip the counter.... you should have stock rom on before triangle away. Then triangle away. Then unroot.
Sent from my GT-N7105 using xda premium
Click to expand...
Click to collapse
Ok I did this. Then went to odin mode here is what it says
Custom Binary Download : no
Current Binary: Samsung official
System Status: official.
Device status in settings still says modified. I have no root, no TA and stock recovery this stuff is driving me batty.
Edit. I just tried to go into stock recovery by volume up, home and power. It DOES not go to whatever menu is there. It just boots.
bigdaddyjosh said:
Ok I did this. Then went to odin mode here is what it says
Custom Binary Download : no
Current Binary: Samsung official
System Status: official.
Device status in settings still says modified. I have no root, no TA and stock recovery this stuff is driving me batty.
Edit. I just tried to go into stock recovery by volume up, home and power. It DOES not go to whatever menu is there. It just boots.
Click to expand...
Click to collapse
Stock recovery should work..... If not try cf root again. That restores stock
Anyways you need to factory reset to change modify to official.
I suggest you dont factory reset unless you need to return it, You may decide to root again as I did.
Android The Greek said:
Stock recovery should work..... If not try cf root again. That restores stock
Anyways you need to factory reset to change modify to official.
I suggest you dont factory reset unless you need to return it, You may decide to root again as I did.
Click to expand...
Click to collapse
Yea, I tried to factory reset, but i was missing the stock recovery so it went into a boot loop. I battery pulled and booted odin and reinstalled factory recovery, using cf-auto root. Here is my question. Everytime I factory reset it auto installs SuperSU. WTH is going on here
What is the downside of staying rooted? Can I still get updates? Maybe not OTA but some how?
Did you go into supersu do full unroot then factory reset?
Being rooted only affects renting and buying from play store and ota updates.
Upside of rooting... having newest firmware before everone else
Sent from my GT-N7105 using xda premium
Android The Greek said:
Did you go into supersu do full unroot then factory reset?
Being rooted only affects renting and buying from play store and ota updates.
Upside of rooting... having newest firmware before everone else
Sent from my GT-N7105 using xda premium
Click to expand...
Click to collapse
The very first time I rooted with cwm6 the tutoril said to make a backup of those settings. Is it possible that when I perform the reset with stock recovery that it is reflashing supersu? Because that is what im seeing on my end. Weird thing is that odin mode still shows 0 flashes but cant get rid of supersu it just comes back after reset.
bigdaddyjosh said:
Yea, I tried to factory reset, but i was missing the stock recovery so it went into a boot loop. I battery pulled and booted odin and reinstalled factory recovery, using cf-auto root. Here is my question. Everytime I factory reset it auto installs SuperSU. WTH is going on here
What is the downside of staying rooted? Can I still get updates? Maybe not OTA but some how?
Click to expand...
Click to collapse
if you're still stuck, consider the using the method i followed in post 51 in the cf root thread (steps 2-8). ignore step 1 if you don't have a custom recovery (e.g., CWM or TWRP). i've followed the steps listed in that post on 4 different devices and it's worked every time. good luck, hope you get this resolved.
Did you go into supersu and click full unroot thats the last step.
Then you can facrory reset in stock recovery.
Sent from my GT-N7105 using xda premium
Ive followed your direction. I have no custom recovery. Odin download mode still shows official with no counts of flashes.
After bootup I still have SuperSu.
I have done complete unroot with superSu so many times its not funny. Each time I do the unroot I go and do a factory reset. And after every reset it restores root. Under device status it says modified, but Odin says im good. Can I do OTA in this status?
I shouldnt say it restored root after factory reset but it does restore supersu.
After you do full unroot go to play store and unistall all supersu supersu pro super user etc. Then factory reset.
Also take a screenshot of your device app drawer after you factory reset.
Sent from my GT-N7105 using xda premium
So I was jacking with my phone at work today and I was looking at the internal memory. I had several entrues for titanium backup still sitting there. Wanting to get rid of all things root on my phone I went througj and deleted everything resembling root apps. Then rebooted. Check device settings and it says NORMAL!!! I dont know which app or what was causing it and I dont care. It is back to normal. Thanks for all your help last night.
No problem please don't make this a reason you dont root in the future. I learned the hard way like you did with help from the good people here. Im sure you will be alot more successful on the next go around.
Sent from my GT-N7105 using xda premium
Hi everyone,
I just bought the Allshare Cast hub and it wont stay connected for more 20 secs then says end connection...
I rooted my Tmobile GN2 to TWRP with Odin. I know that I have to use Triangle Away to reset the binary counter to 0 in order for Allshare Cast Hub to work. I already ran the Triangle Away app and reset the binary counter; However, the binary counter still says 1. I did run TA 2 times, but the results were still the same. Some people did get their binary counter to 0 after reseting it with TA.
Is there any reason why mine CANT be reset to 0?
Can someone point me to the right direction please?
I'm very noob on rooting stuff, please help,
Thank you very much for your and for your time.
mygalaxynote2 said:
Hi everyone,
I just bought the Allshare Cast hub and it wont stay connected for more 20 secs then says end connection...
I rooted my Tmobile GN2 to TWRP with Odin. I know that I have to use Triangle Away to reset the binary counter to 0 in order for Allshare Cast Hub to work. I already ran the Triangle Away app and reset the binary counter; However, the binary counter still says 1. I did run TA 2 times, but the results were still the same. Some people did get their binary counter to 0 after reseting it with TA.
Is there any reason why mine CANT be reset to 0?
Can someone point me to the right direction please?
I'm very noob on rooting stuff, please help,
Thank you very much for your and for your time.
Click to expand...
Click to collapse
are you on custom rom or kernel or recovery ?
if yes tht is the reason binary shows 1
aukhan said:
are you on custom rom or kernel or recovery ?
if yes tht is the reason binary shows 1
Click to expand...
Click to collapse
Honestly, I'm not even sure. I followed the youtube video and it has links to the odin files. it has a bunch of GN2 versions to select during the Odin rooting process. is there anyway I can find out if I have any of the above you mentioned? If mine has any of the above, is there a way to make my phone not on custom rom, kernel, or recovery?
Thanks alot
twrp could be the problem.
it's just really random.
2 more things you could try:
use the note 2 toolkit(I'm sure it's somewhere in the development sections here) to flash the stock recovery.
or use sysscope blaster (xposed module) to set the flash counter to 0(use it together with triangle away)
Boot you phone in recovery mode can googel it how to Press Volume Up +menu+power button release the buttons as soon as you N7100
or you got plenty of you tube Videos let mw what does it say on this CWM, TWRP,Philz
thedicemaster said:
twrp could be the problem.
it's just really random.
2 more things you could try:
use the note 2 toolkit(I'm sure it's somewhere in the development sections here) to flash the stock recovery.
or use sysscope blaster (xposed module) to set the flash counter to 0(use it together with triangle away)
Click to expand...
Click to collapse
GN2 Toolkit was the one I used to root my phone. How do I flash the stock recovery and any danger in doing it? Is my phone still rooted after flashing it to stock recovery?
Steps by steps would be greatly appreciated.
thanks alot
recovery is used to make full system backups and installing updates/roms as zip files.
it's ok to use the stock recovery if you don't install too many odd mods.
it won't affect root, and you should just follow the instructions in the toolbox screen.
aukhan said:
Boot you phone in recovery mode can googel it how to Press Volume Up +menu+power button release the buttons as soon as you N7100
or you got plenty of you tube Videos let mw what does it say on this CWM, TWRP,Philz
Click to expand...
Click to collapse
Mine is Tmobile TGH 889
Kernel version: 3.0.31-260018
Thanks
What do you see in recovery s ree
There is no harm in having custom or stock recovery
Benefit of
If your doin lot of flashing it's helpful for you to do a nand backup and restore.
Sent from my GT-N7100 using xda premium
thedicemaster said:
recovery is used to make full system backups and installing updates/roms as zip files.
it's ok to use the stock recovery if you don't install too many odd mods.
it won't affect root, and you should just follow the instructions in the toolbox screen.
Click to expand...
Click to collapse
Thank you very for replies.
I ran the GN2 Toolkit and it has a bunch of options.
one of them says "Reflashing Stock Recovery Via Odin"
Is this the right option that I need?
Also, do i need to unroot 1st before doing it?
I'm sorry for asking so many questions, but I love GN2 and I cant afford another one because of my noob mistakes.
thank you very much
there is no need to unroot, and yes that is the right option.
mygalaxynote2 said:
Hi everyone,
I just bought the Allshare Cast hub and it wont stay connected for more 20 secs then says end connection...
I rooted my Tmobile GN2 to TWRP with Odin. I know that I have to use Triangle Away to reset the binary counter to 0 in order for Allshare Cast Hub to work. I already ran the Triangle Away app and reset the binary counter; However, the binary counter still says 1. I did run TA 2 times, but the results were still the same. Some people did get their binary counter to 0 after reseting it with TA.
Is there any reason why mine CANT be reset to 0?
Can someone point me to the right direction please?
I'm very noob on rooting stuff, please help,
Thank you very much for your and for your time.
Click to expand...
Click to collapse
Thats because when u root by cf autoroot or whatever, it uses a "custom recovery" for few secs to root your device and after that it changes back to stock but samsung detects those few secs and it raises your binary counter to 1.. and now u want to reset your binary counter so u have downloaded + installed the app...
Ta uses also a "custom recovery" to reset your counter. After resetting it (0), your recovery changes back to your current recovery may it be stock samsung or cmw doesnt mather but when u reboot samsung detects that also and raises back to 1
Thats why when people want to unroot their phone and t use Triangle away..
They follow the following steps
While resetting the counter it asks u to reboot.. dont let the phone directly boot up (so samsung doesnt detects anything custom and counter stays 1)
And go directly to download ODIN mode.. now open odin and flash stock rom. This way you would perfectly unroot your phone..
Ps: counter 0 and root is possible by prerooted roms.. but counter 0 + custom recovery is impossible imo (maybe im wrong xd)
Sent from my GT-N7100 using xda premium
it's kinda possible.
while in download mode my flash counter is probably at 1, but while android is running it's at 0 thanks to sysscope blaster.
AskinSavascisi said:
Thats because when u root by cf autoroot or whatever, it uses a "custom recovery" for few secs to root your device and after that it changes back to stock but samsung detects those few secs and it raises your binary counter to 1.. and now u want to reset your binary counter so u have downloaded + installed the app...
Ta uses also a "custom recovery" to reset your counter. After resetting it (0), your recovery changes back to your current recovery may it be stock samsung or cmw doesnt mather but when u reboot samsung detects that also and raises back to 1
Thats why when people want to unroot their phone and t use Triangle away..
They follow the following steps
While resetting the counter it asks u to reboot.. dont let the phone directly boot up (so samsung doesnt detects anything custom and counter stays 1)
And go directly to download ODIN mode.. now open odin and flash stock rom. This way you would perfectly unroot your phone..
Ps: counter 0 and root is possible by prerooted roms.. but counter 0 + custom recovery is impossible imo (maybe im wrong xd)
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
I reflashed my phone to stock recovery with option 6. I also ran Triangle Away, but my binary counter is still 1.
Therefore, I decided to try your methods by running TA 1st to reset the binary counter and let it boot into Odin downloading mode. I ran the GN2 Toolkit and tried to reflash the stock with option 6, the GN2 Toolkit was just waiting for USB Debugging althought I had it turned on. Can you please help me pass this step?
I very appreciate for your help.
yeah sure..
so lets make ourselves first clear..
u want to unroot your phone fully??
can u boot into your rom/phone now??
do u have root?
AskinSavascisi said:
yeah sure..
so lets make ourselves first clear..
u want to unroot your phone fully??
can u boot into your rom/phone now??
do u have root?
Click to expand...
Click to collapse
No, I just want my phone to stay rooted with stock recovery and binary counter = 0.
After I reflashed the stock recovery with option 6 and reset binary counter with TA, but the binary counter is still 1.
My phone is till rooted and still boots up just like I had before. I can still go into Odin Downloading Mode.
I hope I provide you enough info.
Thank you
did you try allshare cast again?
it works for me even with the counter at 1.
thedicemaster said:
did you try allshare cast again?
it works for me even with the counter at 1.
Click to expand...
Click to collapse
hmmm, that's interesting. No, I have not tried to run allshare cast yet after I reflashed stock recovery.
Alot of people said that it wont work when the binary counter is 1 or greater. Thats the reason I didnt try the allshare cast.
I will run Allshare Cast when I get home from work.
What does your phone status say? Modified or Normal?
as i said in my first reply, allshare cast is very random.
initially it worked only if i used a stock recovery, while my counter was at 1.
somehow it started working later on using CWM.
then it stopped working, but running triangle-away fixed it(even though it changed nothing)
my counter should still be at 1, but because i use sysscope blaster android thinks it's at 0.
thedicemaster said:
as i said in my first reply, allshare cast is very random.
initially it worked only if i used a stock recovery, while my counter was at 1.
somehow it started working later on using CWM.
then it stopped working, but running triangle-away fixed it(even though it changed nothing)
my counter should still be at 1, but because i use sysscope blaster android thinks it's at 0.
Click to expand...
Click to collapse
I just ran the Allshare Cast again, same issue.
Furthermore, I was able to reset the binary counter with TA, then instead of letting it reboot, I went into Odin Downloading Mode, used Odin software to reflashed the stock recovery. Sadly, the problem is still exist: my phone status still says modified and wont work with Allshare Cast.... I'm afraid I'll have to unroot it unless someone can help me out. this allshare Cast crap starts to piss me off!
I think I deleted a few bloatwares before.
are all my settings, apps etc going to be deleted/reset after I unroot my phone?
Thanks alot
So, after years of flashing roms on my phones, this is the first time I got a bootloop issue.
First of all, I tried to install the new Dn3 5.5 rom, which didnt get installed properly and ended up having my Knox warranty bit triggered.
Now on the 'downloading' screen, it shows two more lines,
KNOX WARRANTY VOID: 1
SWREV: A2
I read the forums and am guessing that even after this I should be able to flash custom roms, but I cant.
I tried installing the stock firmwares through Odin, but everything failed giving me an 'Invalid magic string' error, except the new FNI1 firmware, which I am assuming, worked because its the latest one and I cant downgrade due to the Knox bit being set.
Now although my phone has booted up, I rooted it using CF Auto root and de-knoxed it using Dr.Ketan's Multitool, I cant seem to turn off the phone.
Everytime I perform a reboot or 'power off' or even perform a hard restart, it shows the grey battery icon, turns off and loops again.
I have to clear the cache, after which it boots normally.
So, summarizing,
Phone gets a bootloop on the charging screen, and cannot install custom roms.
I am assuming its a bootloader issue, but need some guidelines by someone who has an idea about why this is happening just so that I dont mess up my phone more.
I need to perform a downgrade, and if possible reset the Knox bit too if anyone knows how to by now.
I think Dr.Ketan might be able to help out.
Thanks a lot.
Tan9890 said:
So, after years of flashing roms on my phones, this is the first time I got a bootloop issue.
First of all, I tried to install the new Dn3 5.5 rom, which didnt get installed properly and ended up having my Knox warranty bit triggered.
Now on the 'downloading' screen, it shows two more lines,
KNOX WARRANTY VOID: 1
SWREV: A2
I read the forums and am guessing that even after this I should be able to flash custom roms, but I cant.
I tried installing the stock firmwares through Odin, but everything failed giving me an 'Invalid magic string' error, except the new FNI1 firmware, which I am assuming, worked because its the latest one and I cant downgrade due to the Knox bit being set.
Now although my phone has booted up, I rooted it using CF Auto root and de-knoxed it using Dr.Ketan's Multitool, I cant seem to turn off the phone.
Everytime I perform a reboot or 'power off' or even perform a hard restart, it shows the grey battery icon, turns off and loops again.
I have to clear the cache, after which it boots normally.
So, summarizing,
Phone gets a bootloop on the charging screen, and cannot install custom roms.
I am assuming its a bootloader issue, but need some guidelines by someone who has an idea about why this is happening just so that I dont mess up my phone more.
I need to perform a downgrade, and if possible reset the Knox bit too if anyone knows how to by now.
I think Dr.Ketan might be able to help out.
Thanks a lot.
Click to expand...
Click to collapse
Knox trigger can't be reversed.
Of course, it is a bootloader issue. Follow the procedure and it should work out well for you.
1. Use stock recovery to wipe cache and factory reset.
2. Don't use cf-auto root.
3. Download Philz recovery latest version and supersu zip file. (For Note 2 )
4. Flash Philz. Uncheck auto reboot option in ODIN. Once you get pass message, unplug. Don't start your phone yet. Boot directly into recovery.
5. Install supersu zip file
6. Reboot to check if you are rooted.
7. DN3 5.5 has given me a headache. But it must be something ---- looking at the number of people using it.
8. I prefer Dr. Ketan's V12 Touchwiz ROM.
With Aroma installer, it is almost impossible to go wrong. Support is amazing. Doc himself answers all queries as fast as he can. But choice is yours.
Press thumps up if you found this suggestion helpful.
Link to all the files: http://www.ibtimes.co.uk/root-galax...d-4-4-2-kitkat-install-philz-recovery-1447891
Sent from my GT-N7100 using Tapatalk
Hi...Thanks for the quick reply.
Your solution did help, although partially. I liked the idea of unchecking the auto-reboot option.
I installed the SuperSU as you said, but the problem still remains. I think the bootloader resets all the root access everytime it boots. I had to go with CF autoroot to get it booting again.
But the good news is, with the autoreboot turned off, I was able to install a custom rom.
Here's what happened.
I installed the rom successfully, rebooted the phone n got back to the same battery screen again. Tried hard resetting it but couldnt get too the boot screen. Then I flashed the CF autoroot after which it booted fine into the Aosb rom.
I think a patched bootloader which removes the root disabling would do the trick here. Also, the recovery also gets removed during the next boot.
So is there any way to flash a different bootloader from ODIN? I have this Patched MJ5 bootloader, but there's an error saying 'SWREV: CHECK FAIL, DEVICE:2, BINARY:1'
Tan9890 said:
Hi...Thanks for the quick reply.
Your solution did help, although partially. I liked the idea of unchecking the auto-reboot option.
I installed the SuperSU as you said, but the problem still remains. I think the bootloader resets all the root access everytime it boots. I had to go with CF autoroot to get it booting again.
But the good news is, with the autoreboot turned off, I was able to install a custom rom.
Here's what happened.
I installed the rom successfully, rebooted the phone n got back to the same battery screen again. Tried hard resetting it but couldnt get too the boot screen. Then I flashed the CF autoroot after which it booted fine into the Aosb rom.
I think a patched bootloader which removes the root disabling would do the trick here. Also, the recovery also gets removed during the next boot.
So is there any way to flash a different bootloader from ODIN? I have this Patched MJ5 bootloader, but there's an error saying 'SWREV: CHECK FAIL, DEVICE:2, BINARY:1'
Click to expand...
Click to collapse
Don't flash old bootloaders. Now you are on NI1. (Only a 4.4.2-based bootloader can rewrite the existing bootloader)
Also, losing recovery is common. On 4.4.2, it gets rewritten. Hence, after flashing recovery you should not reboot the phone immediately.
Instead, as I said you press the key combo to enter recovery (preferably Philz recovery) as soon as you flash it.
Clear cache and factory reset.
Then you start the phone
Also, most custom ROMs are prerooted. You don't even have to use cf-auto or supersu zip to root your device if you intend to flash a custom ROM.
I don't know which ROM you like, but, ideally, a ROM should be prerooted, zip aligned and deodexed. For instance, DN3 5.5 and Dr.Ketan's V12 are the leading ones in this category. In fact, you have Omni, Phantom, Ultra, Diamond, etc, etc. One is simply spoilt for choice.
Caution: Bootloaders are sensitive. If they get screwed up, your phone will end up in service centre.
Sent from my GT-N7100 using Tapatalk
ceomaverick said:
Don't flash old bootloaders. Now you are on NI1. (Only a 4.4.2-based bootloader can rewrite the existing bootloader)
Also, losing recovery is common. On 4.4.2, it gets rewritten. Hence, after flashing recovery you should not reboot the phone immediately.
Instead, as I said you press the key combo to enter recovery (preferably Philz recovery) as soon as you flash it.
Clear cache and factory reset.
Then you start the phone
Also, most custom ROMs are prerooted. You don't even have to use cf-auto or supersu zip to root your device if you intend to flash a custom ROM.
I don't know which ROM you like, but, ideally, a ROM should be prerooted, zip aligned and deodexed. For instance, DN3 5.5 and Dr.Ketan's V12 are the leading ones in this category. In fact, you have Omni, Phantom, Ultra, Diamond, etc, etc. One is simply spoilt for choice.
Caution: Bootloaders are sensitive. If they get screwed up, your phone will end up in service centre.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Yes, but I am losing the recovery everytime when I boot. Its like, Once the rom gets set up and running. I should not switch off or restart my phone at all. Else it again goes back to the battery charging screen and gets stuck.
In case I have to reboot, I must flash the CF autoroot so that it restarts the rom.
Sounds weird right?
Tan9890 said:
Yes, but I am losing the recovery everytime when I boot. Its like, Once the rom gets set up and running. I should not switch off or restart my phone at all. Else it again goes back to the battery charging screen and gets stuck.
In case I have to reboot, I must flash the CF autoroot so that it restarts the rom.
Sounds weird right?
Click to expand...
Click to collapse
Very weird. Never heard of such a thing. Btw, which recovery you are using? TWRP or CWM. Also, chk if the version is latest. The latest versions are fixed for these very issues.
Probably, flashing N7100XXUFNI1 out of the box should solve your problem.
Beyond that I don't have answers.
Sent from my GT-N7100 using Tapatalk
Snippet taken from: http://mark.candleshoreblog.com/2013/06/13/tip-steps-to-prevent-clockwork-or-any-custom-recovery-from-being-overwritten-by-factory-stock-roms-at-android-system-reboot/:
The reason your stock recovery system keeps getting overwritten at Android startup is because of a script that is being run. All you need to do is either rename this script or simply delete it.
Please keep in mind that if you restore your stock ROM, this script will be restored with it so you will have to rename or delete it again. Do the following:
1.
Make sure your device is powered on and running normally,
2.
Make sure you have rooted your device and that you have all of the necessary permissions in order to manipulate system files.
3.
In the root file system go to \system\etc
4.
Find the file named install-recovery.sh and either rename it or, as I did, delete it.
That’s all there is to it.
Hey guys,
Im not new to rooting and custom roms and all, but I never had something like this happen before. I'm on 4.4.2 on my i747 and I got the cwm from Clockworkmod.com and every time I flash the custom recovery with odin 3 my stock recovery overwrites cwm. Can I use the 4.0.4 version of cf autoroot to root my phone or will it brick?
Any help is appreciated, thanks again
Easiest way to root this phone is just flash supersu in custom recovery.
1) Download a recovery flashable supersu.zip to the phone storage.
2) Use Odin to flash custom recovery (consider using TWRP, CWM hasn't been developed in quite some time). Be sure to uncheck auto-reboot in Odin. Upon success do not reboot into system, unplug the USB cable and pull the battery.
3) Replace battery and boot straight into recovery. Hold vol up + home + power together and don't let go until you see "recovery booting" in little blue text in the upper left.
4) Make a backup in recovery, just in case things go wrong.
5) Flash the supersu.zip in custom recovery.
6) Reboot into system.
You might have to update the supersu binary and reboot a few times until it gets Knox properly disabled and everything settles. Once you're rooted the stock rom will stop overwriting your custom recovery every time you boot into it.
This phone is very brickable, but generally not when messing with recovery, rooting, or custom roms. The things that tend to result in hard bricks are messing with the bootloader and modem (keep them matched and don't ever downgrade), accidentally flashing a rom intended for i9300 (the other S3), or attempting to unlock the already not locked bootloader. Use caution in those areas and this is actually a pretty modder friendly phone (especially for a Samsung).
jason2678 said:
Easiest way to root this phone is just flash supersu in custom recovery.
1) Download a recovery flashable supersu.zip to the phone storage.
2) Use Odin to flash custom recovery (consider using TWRP, CWM hasn't been developed in quite some time). Be sure to uncheck auto-reboot in Odin. Upon success do not reboot into system, unplug the USB cable and pull the battery.
3) Replace battery and boot straight into recovery. Hold vol up + home + power together and don't let go until you see "recovery booting" in little blue text in the upper left.
4) Make a backup in recovery, just in case things go wrong.
5) Flash the supersu.zip in custom recovery.
6) Reboot into system.
You might have to update the supersu binary and reboot a few times until it gets Knox properly disabled and everything settles. Once you're rooted the stock rom will stop overwriting your custom recovery every time you boot into it.
This phone is very brickable, but generally not when messing with recovery, rooting, or custom roms. The things that tend to result in hard bricks are messing with the bootloader and modem (keep them matched and don't ever downgrade), accidentally flashing a rom intended for i9300 (the other S3), or attempting to unlock the already not locked bootloader. Use caution in those areas and this is actually a pretty modder friendly phone (especially for a Samsung).
Click to expand...
Click to collapse
Thanks. 2 more questions,
1) Do I use the .img.tar file [twrp-3.0.2-0-d2att.img.tar] or the .img file [twrp-3.0.2-0-d2att.img] here > https://dl.twrp.me/d2att/
2) I have the kot94h....NJ2 build number on my phone as I attempted root before, does this matter?
Ulti2x said:
Thanks. 2 more questions,
1) Do I use the .img.tar file [twrp-3.0.2-0-d2att.img.tar] or the .img file [twrp-3.0.2-0-d2att.img] here > https://dl.twrp.me/d2att/
2) I have the kot94h....NJ2 build number on my phone as I attempted root before, does this matter?
Click to expand...
Click to collapse
The twrp files that end in .tar are packaged to be flashed with Odin.
I never updated my i747 past NJ1, but I've not seen any discussion that NJ2 changed anything with respect to rooting on this phone. Just try the stable TWRP flashable supersu.zip.
My experience has been that even if rooting this way fails the worst thing that happens is your rom won't boot, so you pull the battery, boot back into recovery, restore a backup, and you're back up and running. I've never had rooting this way fail on the good old i747, only on newer phones with stock marshmallow.
jason2678 said:
The twrp files that end in .tar are packaged to be flashed with Odin.
I never updated my i747 past NJ1, but I've not seen any discussion that NJ2 changed anything with respect to rooting on this phone. Just try the stable TWRP flashable supersu.zip.
My experience has been that even if rooting this way fails the worst thing that happens is your rom won't boot, so you pull the battery, boot back into recovery, restore a backup, and you're back up and running. I've never had rooting this way fail on the good old i747, only on newer phones with stock marshmallow.
Click to expand...
Click to collapse
Thanks so much. I will do what you told me and report back. By the way, do all att s3's have unlocked bootloaders?, and how do you update the supersu binary?
Ulti2x said:
Thanks so much. I will do what you told me and report back. By the way, do all att s3's have unlocked bootloaders?, and how do you update the supersu binary?
Click to expand...
Click to collapse
The i747 and i747m were all unlocked by default. I'm pretty sure t999's are too.
Verizon's were locked. There was an unlock exploit for Verizon. Occasionally I read about someone trying it on an AT&T S3 and bricking it here.
I think supersu will pop up something on it's own if it is out of date, and retrieves what it needs from the Play store. It has been ages since I actually rooted stock on this phone. I vaguely remember Knox blocking root, supersu updating, rebooting a time or two then supersu eventually offering to disable Knox.
jason2678 said:
The i747 and i747m were all unlocked by default. I'm pretty sure t999's are too.
Verizon's were locked. There was an unlock exploit for Verizon. Occasionally I read about someone trying it on an AT&T S3 and bricking it here.
I think supersu will pop up something on it's own if it is out of date, and retrieves what it needs from the Play store. It has been ages since I actually rooted stock on this phone. I vaguely remember Knox blocking root, supersu updating, rebooting a time or two then supersu eventually offering to disable Knox.
Click to expand...
Click to collapse
I got backed up and successfully rooted. Thanks so much for the help. By the way, in logs and apps in supersu free it shows the loading circle forever, does that matter? I still have full root access to all apps.
EDIT: Turned out I needed a reboot to disable KNOX, you were right. Thanks for all your help jason!
I need help get past the Tmobile logo at boot.
SM-N900T
Android 4.4.2
N900TUVUENK3
Performed CF-Auto-Root 2.5 years ago. Ran like a champ until last week when phone got boot stuck on white T-mobile logo.
will not start in Safe Mode - press power till Galaxy Note 3 logo shows up, then vol down. does not start in safe mode
Put in Recovery (power, home, vol up), wiped cache, reboot . still boot stuck at T mobile logo
Put in download mode (power, home, vol down), Re-flashed with Odin3-v3.07.exe CF latest SM-N900T (T-Mobile US): CF-Auto-Root-hltetmo-hltetmo-smn900t.zip , extracted to .tar.md5, still boot stuck
Put in Recovery (power, home, vol up), wipe data/factory reset, then reboot. got past Tmobile white boot screen.
Must keep phone on and not reboot otherwise , I will need to wipe data/factory reset each time to boot and get past Tmobile logo
JJEgan said:
Dont know why you are blaming ROOT .
Suggest you ask in your models forum .
I would wipe phone install stock rom and use SuperSu zip as root after flashing custom recovery .
Click to expand...
Click to collapse
The Latest CF-AUTO-ROOT flashed with Odin installed latest SuperSu v2.82 and has stock recovery with stock rom.
Why is phone stuck at boot? Why install custom recovery, I did not need it before? And if so, Which one? Why would SuperSu zip be needed if latest version is already installed?
My TMo Note3 did the exact same thing last week. (I was still on v4.4.2.) After fiddling with it a little bit, I decided to try a factory-reset. That worked, and then after signing into google, all my apps started to re-download and install. Once that completed, I rebooted and again got stuck at the white TMo screen. Eventually I just bit the bullet and flash-updated it to v5. I disabled auto-installing my apps, and carefully installed just the apps I really wanted, rebooting after a few at a time just to see if I could catch whatever was causing it. But after getting all my apps installed, it's working fine now with no reboot issues.
My personal guess (no direct evidence) is that one of the apps was breaking the bootup somehow.
Looks like I am not the only one having this problem. I don't think this would have suddenly happen. I think there must of have been something with a Samsung update that caused the boot to stick at the Tmobile logo. I am thinking I am just going to have to update from 4.4.2 to 5 and trip my knox. Unless someone else has any other ideas.
Thanks for replying. So you upgraded from 4.4.2 to 5.0. How? What does it matter if you trip Knox if phone is already rooted?
I think cfautoroot will always trip the Knox indicator if the phone is running a 4.3 or newer bootloader.
Tried flashing supersu from twrp to get root?
2Code said:
Thanks for replying. So you upgraded from 4.4.2 to 5.0. How? What does it matter if you trip Knox if phone is already rooted?
Click to expand...
Click to collapse
any ideas here?
2Code said:
any ideas here?
Click to expand...
Click to collapse
I used Samsung's Smart Switch PC. One of the "features" is that it will detect the older Android OS on your phone and offer to install the latest - albeit at the cost of a total wipe and re-flash. (Hence why it recommends you use the app to first back up your phone.) I my case, I had nothing to lose since I couldn't get out of the boot-up screen, and I had already done a factory-reset.
I don't know how this will affect the Knox flag. I never tripped that flag, so I can't say if this will reset it or not.
software_samurai said:
I used Samsung's Smart Switch PC. One of the "features" is that it will detect the older Android OS on your phone and offer to install the latest - albeit at the cost of a total wipe and re-flash. (Hence why it recommends you use the app to first back up your phone.) I my case, I had nothing to lose since I couldn't get out of the boot-up screen, and I had already done a factory-reset.
I don't know how this will affect the Knox flag. I never tripped that flag, so I can't say if this will reset it or not.
Click to expand...
Click to collapse
Thanks software_samurai.
so download the pc version, connect phone, and it will wipe and install Android 5.0
Phone was rooted with CF-autoroot , will phone stay rooted after android upgrade from 4.4 2 to 5.0 ? Or will I need to redo CF-autoroot?
Earlier post indicated that autpupdate of apps may be interfering with boot and is cause of boot stuck at Tmobike logo. Post suggests to install apps one at a time and disable autoupdate of apps. Has one app been identified as suspect app? What other steps should I take to prevent recurrance?
TWRP recovery. Do I need to install it to prevent boot stuck issue? How does it help prevent recurrance of boot stuck issue?
2Code said:
so download the pc version, connect phone, and it will wipe and install Android 5.0
Click to expand...
Click to collapse
yes. it will offer the "upgrade" and if you accept, it will wipe and re-flash with the stock OS.
2Code said:
Phone was rooted with CF-autoroot , will phone stay rooted after android upgrade from 4.4 2 to 5.0 ? Or will I need to redo CF-autoroot?
Click to expand...
Click to collapse
this will wipe the phone and install the stock OS, so no, it will not stay rooted after this.
2Code said:
Earlier post indicated that autpupdate of apps may be interfering with boot and is cause of boot stuck at Tmobike logo. Post suggests to install apps one at a time and disable autoupdate of apps. Has one app been identified as suspect app? What other steps should I take to prevent recurrance?
Click to expand...
Click to collapse
that was my attempt at recovering from a factory reset on 4.4.2. my guess was that one of the apps caused the boot-problem, but I can't be sure.
2Code said:
TWRP recovery. Do I need to install it to prevent boot stuck issue?
Click to expand...
Click to collapse
wiping the phone and re-flashing to stock OS is what I did to avoid the boot-problem. I've got no idea about using TWRP since I've never used it.
2Code said:
How does it help prevent recurrance of boot stuck issue?
Click to expand...
Click to collapse
again, wiping and re-flashing to stock OS should totally clear out any software-related problem.
if your phone has some hardware issue, you're out of luck.
software_samurai said:
this will wipe the phone and install the stock OS, so no, it will not stay rooted after this.
Click to expand...
Click to collapse
Many Thanks for replying.
have you rooted with CF-autoroot after using samsung smarts witch pic to install Android 5.0 and stock rom ? How did it go?
2Code said:
have you rooted with CF-autoroot after using samsung smarts witch pic to install Android 5.0 and stock rom ? How did it go?
Click to expand...
Click to collapse
nope. so far I haven't needed root. Android 5.0 has a (rather clunky) way to handle giving specific apps write access to the sdcard, thus eliminating the only reason I would need root.
Curious, Is installing Android 5.0 using Samsung switch PC same as flashing sambile latest SM-900T firmware https://www.sammobile.com/firmwares/galaxy-note3/SM-N900T/TMB/download/N900TUVSFPL1/120222/ ?
2Code said:
Curious, Is installing Android 5.0 using Samsung switch PC same as flashing sambile latest SM-900T firmware https://www.sammobile.com/firmwares/galaxy-note3/SM-N900T/TMB/download/N900TUVSFPL1/120222/ ?
Click to expand...
Click to collapse
Downloaded latest SM-N900T Android 5.0.1 stock Ron & Kernel and flashed with Odin v3.12. Did not wipe out personal data but lost root.
This,took care of the boot stuck at T-Mobile logo
Re-flashed CF-AUTO root to restore root access.
Hope these steps help somebody.