I have a note 3 and used towelroot when I was running 4.4.2, but got the notification that 4.4.4 was available. I went into supersu, ran unroot, rebooted and my phone status said I had a custom device status. I rerooted with towelroot, and the status went back to official, so I downloaded the OTA then ran the unroot on supersu and installed 4.4.4
Now that it's installed, I'm back to having my device status as custom and I have no root. Would it just be better to flash back to 4.4.2 and reroot?
Odin twrp and flash supersu in recovery.
Sent from my SM-N900P using Tapatalk
JoshRoss70 said:
I have a note 3 and used towelroot when I was running 4.4.2, but got the notification that 4.4.4 was available. I went into supersu, ran unroot, rebooted and my phone status said I had a custom device status. I rerooted with towelroot, and the status went back to official, so I downloaded the OTA then ran the unroot on supersu and installed 4.4.4
Now that it's installed, I'm back to having my device status as custom and I have no root. Would it just be better to flash back to 4.4.2 and reroot?
Click to expand...
Click to collapse
If you have not tripped your KNOX 0x0, then I would do a Factory Reset. This should uninstall the OTA update and allow you to reroot with Towel root at 4.4.2. If Knox is 0x1, then you can always flash a fresh copy of 4.4.2 through a recovery like twrp or cwm. As far as I know Towel Root and others have not been updated to root 4.4.4, and the 4.4.4 update is supposed to be a security update. So, I'm sure one of the updates functions is to close the latest ways to root.
JoshRoss70 said:
I have a note 3 and used towelroot when I was running 4.4.2, but got the notification that 4.4.4 was available. I went into supersu, ran unroot, rebooted and my phone status said I had a custom device status. I rerooted with towelroot, and the status went back to official, so I downloaded the OTA then ran the unroot on supersu and installed 4.4.4
Now that it's installed, I'm back to having my device status as custom and I have no root. Would it just be better to flash back to 4.4.2 and reroot?
Click to expand...
Click to collapse
I did just as bhurst suggested. Odined twrp rhan flashed supersu. When i ran super su it gave a warning about knox. I disabled/turned off everything i coukd find in application manager and reran supersu and when it asked to disable knox i said yes and it said knox disabled and im all rooted on 4.4.4..
Fyi i tried to let supersu disable knix on its own but it locked up.
Sent from my SM-N900P using Xparent Purple Tapatalk 2
jimzweb1 said:
If you have not tripped your KNOX 0x0, then I would do a Factory Reset. This should uninstall the OTA update and allow you to reroot with Towel root at 4.4.2. If Knox is 0x1, then you can always flash a fresh copy of 4.4.2 through a recovery like twrp or cwm. As far as I know Towel Root and others have not been updated to root 4.4.4, and the 4.4.4 update is supposed to be a security update. So, I'm sure one of the updates functions is to close the latest ways to root.
Click to expand...
Click to collapse
I've never opened the Knox apk, so how do I check the counter? I'm not really familiar with Knox, just know it's a security app, but didn't have it until I upgraded to the note, so I never even messed with it.
JoshRoss70 said:
I've never opened the Knox apk, so how do I check the counter? I'm not really familiar with Knox, just know it's a security app, but didn't have it until I upgraded to the note, so I never even messed with it.
Click to expand...
Click to collapse
Well unlesss you rooted via a non knox safe method or installed custom recovery thsn knox is not tripped. If you boot your phone into download or recovery mode i think it one of those shows.. if it says 01 its tripped 00 not tripped
Related
So I've been really confused about all this MJ4 updating and such lately. My Note 3 was running a stock rooted M15. But I wanted to get these new fixes for the call quality in MJ4.
So here is what I did......
I downloaded MJ4 tar and Kernel from the Samsung updates site. I installed via Odin 3.07. It apparently updated my phone to MJ4 according to the "About Device" screen on my phone. However I was still having bad audio issues. So I ran "Root Checker" back to back 3 times while I was at work this evening and of course it said I didn't have root. So i then tried to installed the MJ4 update again via the "Updates" menu on my phone and it said I couldn't because my phone was modified.
So when I got home, I reran that tar and kernel again, with same result. So then I stared hunting around the forum for answers. I ran across a thread that said there were two ways to restore root: 1.)Install TWRP via Odin, Use a nanadroid back up and restore the rom from the M15 backup but without reinstalling the modem or 2.)install TWRP via Odin, disconnect my phone reboot into TWRP and then Flash the ChainFire SU 1.65 zip.
Well I couldnt do method 1.) because I forgot to do a nandroid before performing the update (I know....Idiot). So I tried option 2.) after rerunning the tar and kernel again. Then I tried to install Freeza's [ROM|StockRooted] 11/6/13 Sprint TouchWiz Jelly Bean 4.3 (N900PVPUBMJ4) Odex/DeOdex which of course failed.
So I then rebooted to recovery again and wiped dalvik and cache. Then rebooted my device in order to be disappointed. So I ran "Root Checker" again and low and behold , it says my device is rooted. So confused,. I ran it again and it say's I'm rooted. So I open Titanium Backup to see if I get a error and I dont. It acts as if I'm rooted.
Now key things to remember in the process:
When I initially updated to M15 I used a rooted stock version of the M15 firmware.
I NEVER wiped anything (dalvik, cache, data or system) before flashing. Also none of my data, apps, internal or external storage were wiped in this process. So all of my apps are installed and running. To answer the first question, Yes...Knox is still saying I have 0x1 void warranty.
So am I really rooted or is my system just fooled into thinking I'm rooted and how do I find out?
ANY IDEAS?
Is superuser installed? If it is just try a new app that requires root, if it asks form permission and you can grant it then you are rooted. Personally I would reflash MJ4 tar from odin. Run cf auto root from Odin and you will be on stock rooted MJ4. If you want to flash a custom ROM then flash twrp from Odin and you can then flash a ROM through twrp. Bonsai ROM is working great, freeza's stock MJ4 ROM had a couple minor issues which are ironed out with Bonsai.
SGS4 Sent
ifly4vamerica said:
Is superuser installed? If it is just try a new app that requires root, if it asks form permission and you can grant it then you are rooted. Personally I would reflash MJ4 tar from odin. Run cf auto root from Odin and you will be on stock rooted MJ4. If you want to flash a custom ROM then flash twrp from Odin and you can then flash a ROM through twrp. Bonsai ROM is working great, freeza's stock MJ4 ROM had a couple minor issues which are ironed out with Bonsai.
SGS4 Sent
Click to expand...
Click to collapse
Thanks for the reply bro. Yeah I was thinking to try the whole thing over again. I heard people were not able to root MJ4 with CF Autoroot right now. I just flashed a couple of mods and they worked. I also gave Superusers permission to two apps and they are working.
shaun0207 said:
Thanks for the reply bro. Yeah I was thinking to try the whole thing over again. I heard people were not able to root MJ4 with CF Autoroot right now. I just flashed a couple of mods and they worked. I also gave Superusers permission to two apps and they are working.
Click to expand...
Click to collapse
You should be good to go then. As long as you are happy with the ROM you have etc I wouldn't mess with it. If you do go back to stock there is always kingoroot, people seems to have good luck with that.
Note 3 or Gear Sent
I just got done rooting my phone after doing a factory restore using Odin-CF-Auto-Root-d2att-d2uc-samsungsghi747.tar for my Samsung Galaxy S3 AT&T I747. after I rooted it everything seemed fine, SuperSU opened fine. But I got a system update, I looked and I was running on 4.0.4. So I let the phone install 4.1.2. After the install I go into SuperSU again and I get the Error Message this is no SU binary, This is a problem. Then force close.
The devise still reads as modified, And when putting it in download mode it says custom. So to get SuperSU working again do i need to uninstall the root and then reinstall it on the current 4.1.2? If so how do I got about uninstalling the root? installing it again is simple.
There is an update su binary floating around here somewhere. Search for it and flash it in recovery. All will be fixed.
It happened in mine flashing 4.3
Sent from my iPhone using Tapatalk
I just ended up fixing it. I guess updating the firmware screws with the superSU. rerooted the phone and superSU worked again but I had 2 trip counts so I used Triangle away and now Its reading as official.
Now I need to find some ROMS for the I747 AT&T.. I hard bricked my last s3 and AT&T replaced it. (not knowing it was hard bricked)
I have the same problem with CF-auto root. SU binary not found.
is there any other method to root s3, 4.3?
another question: why is important the binary counter? who cares how many times did you modified a stock device?
I was stock rooted with Kingo and marked official with Wanam Xposed so I unrooted with Kingo and ran Xposed Disabler. So far I have downloaded the official update three times, it goes through the motions of rebooting and installing, but at the end it says it failed.
How can I get this installed? Will Odin'ing Freeza's tar fix it? If not, do I need to install an official MJ4 tar first? Will either of these tars wipe my data? Any other suggestions? I'd like to end up stock rooted on KitKat without tripping Knox if possible.
JimSmith94 said:
I was stock rooted with Kingo and marked official with Wanam Xposed so I unrooted with Kingo and ran Xposed Disabler. So far I have downloaded the official update three times, it goes through the motions of rebooting and installing, but at the end it says it failed.
How can I get this installed? Will Odin'ing Freeza's tar fix it? If not, do I need to install an official MJ4 tar first? Will either of these tars wipe my data? Any other suggestions? I'd like to end up stock rooted on KitKat without tripping Knox if possible.
Click to expand...
Click to collapse
I was getting a fail at 27% I flashed the stock Tar for Kitkat from Freeza and it worked great all data in tacked. I was not rooted but I am guessing you will loose root.
I have Note 3 Sprint, 4.3 phone was rooted, wanted to update to kitkat, said cant because device modified, used wanam mod to fake status, was then allowed to update, when restarted note 3 was still on 4.3 but not rooted. I tried to root again, when restarted after attempt root with cf-auto phone says (RECOVERY IS NOT SEANDROID ENFORCING) (Set Warranty Bit: recovery) Please Help Thanx.....
Mecdemo said:
I have Note 3 Sprint, 4.3 phone was rooted, wanted to update to kitkat, said cant because device modified, used wanam mod to fake status, was then allowed to update, when restarted note 3 was still on 4.3 but not rooted. I tried to root again, when restarted after attempt root with cf-auto phone says (RECOVERY IS NOT SEANDROID ENFORCING) (Set Warranty Bit: recovery) Please Help Thanx.....
Click to expand...
Click to collapse
I would just flash one of the 4.4 tar files via odin as opposed to hassling with getting OTA. Freeza and other's have some in the Sprint Android Development forum, just follow the instruction in the OP. If you're hellbent on getting it via OTA. I'd suggest flashing the tar for stock MJ4 (4.3) then taking the OTA that way.
Gack69 said:
I would just flash one of the 4.4 tar files via odin as opposed to hassling with getting OTA. Freeza and other's have some in the Sprint Android Development forum, just follow the instruction in the OP. If you're hellbent on getting it via OTA. I'd suggest flashing the tar for stock MJ4 (4.3) then taking the OTA that way.
Click to expand...
Click to collapse
Hey Gack69, I appreciate that, will try your method. OTA method not important just didnt no which direction to take. Thanx again
You're welcome. There are already some custom 4.4 ROMs up too. Sacs is nice and mostly stock in appearance. .. Then there's JB's KitKatKiller (K3) which is themed and modded. Depends on what your personal preference are.
Sent from my SM-N900P using Tapatalk
Yeah Odin a 4.4 tar, you can't take a Ota while being rooted even with Wanam. It will always fail or can in some cases brick your device. Odin a kitkat then root with Cf and then add your recovery just be sure you download a Kitkat recovery. After you can use any rom you wish.
I successfully rooted my NK1 4.4.2 phone yesterday and was so happy!
I hadn't bought Titanium Bakcup yet though and didn't disable the process that keeps the update notifications from coming up. In the haze of sleep this morning I pressed update.... Luckily!(?), the update is in two parts, so I stopped after the first half.
I tried flashing the NC5 kernel and rooting. Towelroot hung for a bit then said it should have rooted. Phone crashed (unstability of NC5 kernel) before rootchecker could validate. Restarted ran root checker again and it said it didn't work...
Tried flashing NK1 then back to NC5 and tried again. Same stuff happened.... So now I've got this new MK4 crap but NOT 5.0 on my phone.
What method should I use to root? I intend only to modify stock 4.4.2.
Thanks!
blueman189 said:
I successfully rooted my NK1 4.4.2 phone yesterday and was so happy!
I hadn't bought Titanium Bakcup yet though and didn't disable the process that keeps the update notifications from coming up. In the haze of sleep this morning I pressed update.... Luckily!(?), the update is in two parts, so I stopped after the first half.
I tried flashing the NC5 kernel and rooting. Towelroot hung for a bit then said it should have rooted. Phone crashed (unstability of NC5 kernel) before rootchecker could validate. Restarted ran root checker again and it said it didn't work...
Tried flashing NK1 then back to NC5 and tried again. Same stuff happened.... So now I've got this new MK4 crap but NOT 5.0 on my phone.
What method should I use to root? I intend only to modify stock 4.4.2.
Thanks!
Click to expand...
Click to collapse
Unless root checker PURELY verifies through the installation of SuperSU, then I DO have root again. Yay!