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.
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 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 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
Does anyone know if you can update to 5.1.1 from rooted 5.0.1 with knox not tripped using flashfire?
I have tried it with the s6 and it didn't work. Had to flash back to stock after trying.
Normally I just flash the stock file with Flashfire then flash again the same file with system removed and that got 5.0.1 up and running.
Do you think this is possible?
Right now samfirmware is not working for me to download the update. My internet connect here is too slow I think. Gets about halfway then breaks.
M9x3mos said:
Does anyone know if you can update to 5.1.1 from rooted 5.0.1 with knox not tripped using flashfire?
I have tried it with the s6 and it didn't work. Had to flash back to stock after trying.
Normally I just flash the stock file with Flashfire then flash again the same file with system removed and that got 5.0.1 up and running.
Do you think this is possible?
Right now samfirmware is not working for me to download the update. My internet connect here is too slow I think. Gets about halfway then breaks.
Click to expand...
Click to collapse
Yes, see here: http://forum.xda-developers.com/tmo...l/how-to-update-to-g900tof6-5-1-1-pc-t3141404
so since I am knox not tripped I flash the stock 100% rom without injection and the other partitions using odin, downgrade the kernel and use towelroot to root it again?
That is how to get around the bootloop issue?
Flashed GOF1 by mistake from sammmobile using Odin. Now can't find a root method that works. Tried to flash COF1 using Odin but get fail message. Anyone have any suggestions? I'm really just needing root to get backups restored from TiBu. Much appreciated if anyone has suggestions.
Same here. Looking for a way to root OF1. Tried to downgrade to OC1 using method here:
http://forum.xda-developers.com/gal...-to-update-to-i545of1-5-0-1-keeproot-t3182544
It starts to install, but then fails and soft-bricks the phone and I have to use Repair Assistant get reinstall OF1. Any help to root from OF1 appreciated. TIA
I was able to downgrade to oc1 baseband and build. I got the idea from how I use to jump from android to Tizen on my first generation watch. I ran the of1 md5 and intentionally pulled the cord from my phone about 3/4 of the way through the install. Rebooted and had the white monitors telling me to hook up to kies. Then I loaded the PIT file in Odin, and put I545_OC1_Bootloader.tar.md5 in pda, ticked Re-Partition, Auto Reboot, and Nand Erase All boxes in options, and flashed it. After my bootloader flashed sucessfullly, I ran a stock md5 of the OC1 rom. Once flashed I booted into recovery, wiped cache, wiped system data both two times just to be safe, rebooted and I was on stock OC1 baseband and build ready to root with kingroot.
So you tried to reflash of1 using kies? Would you posible have the files you used to go back?
Thanks, really good idea
HeeyMaan said:
I was able to downgrade to oc1 baseband and build. I got the idea from how I use to jump from android to Tizen on my first generation watch. I ran the of1 md5 and intentionally pulled the cord from my phone about 3/4 of the way through the install. Rebooted and had the white monitors telling me to hook up to kies. Then I loaded the PIT file in Odin, and put I545_OC1_Bootloader.tar.md5 in pda, ticked Re-Partition, Auto Reboot, and Nand Erase All boxes in options, and flashed it. After my bootloader flashed sucessfullly, I ran a stock md5 of the OC1 rom. Once flashed I booted into recovery, wiped cache, wiped system data both two times just to be safe, rebooted and I was on stock OC1 baseband and build ready to root with kingroot.
Click to expand...
Click to collapse
This is exactly what i need. I have just lost root by taking OTA to OF1, and i think what you mentioned might work to get me back to OC1 Rooted until someone comes up with something better. Sound feasible? Does this method only work when you pull the plug like that? still not sure what white monitors is, sorry.
I am on OF1 and was rooted, flashed the stock rooted ROM and it didn't take. I Odin flashed this - http://forum.xda-developers.com/galaxy-s4-verizon/development/odin-i545vrugof1-neutered-bl-t3203361 and it got me back to unrooted OF1. I then went and did the re-root process for OF1 and am back rooted again. I think this file is a stock OF1 image, just doesn't have the bootloader which if you're on OF1 already then you have the OF1 bootloader.
What options do we have if we have the OF1 bootloader.
Sent from my SCH-I545 using Tapatalk
shiz0id said:
What options do we have if we have the OF1 bootloader.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
As far as I know stang5litre has a OF1 compatible ROM and of course the stock deodex ROM/stock ROM. I'm not sure of any past those.