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!
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
Hello! The reason why I am posting here is because I don't exactly know what my problem is caused by. Yesterday, I followed Surge's method of updating to 4.4.2 with root on my Verizon Galaxy S4. That was successful, and I soon after decided that I wanted to give HyperDrive RLS 16 a try on the 4.4.2 base. I installed HyperDrive, but when when I boot up the phone, I lost all root access, safestrap, and my WiFi will not turn on. I know how to fix the WiFi issue and its an easy fix with root, but the problem is that I totally lost root. When I open up SuperSu it says that the binaries are not installed, and I cannot install safestrap to even flash the Verizon modules to get wifi working. Any help would be much appreciated, and like I said, I do not know what the problem actually is so I asked it in general questions. Thanks in advance!
Same thing just happened to me.. used Surges NC5 stock root and everything was fine for the past few weeks.. today I decided to try Hyperdrive, first custom ROM on this phone for me and I'm having the same exact issue as the OP.. haven't tested wifi so not sure but I've lost root and of course Safestrap custom recovery. Guess I have to Odin back.. so frustrating.
Just flash the latest SuperSU zip through recovery and you should be rooted again in no time.
http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip?retrieve_file=1
Thanks..found the answer in the HD thread..I didn't realize I needed to flash superuser right after the ROM..lost root and SS recovery..ended up having to odin back to MK2.. Re-root and then to NC5.. it's been a long night.
I was having the same problem! No root, wireless or SafeStrap. Had to downgrade to MK2 and start over. Finally running the latest HyperDrive with root and SafeStrap but no wireless, even after flashing the NC5 modules
Ok, I was force updated to NG6, I downgraded to NC5 using a no wipe tar with ODIN. That put my phone into a loop. I did a hard reset to my phone which successfully got me back to NC5. I did a towelroot and installed SuperSU. I changed the files SDM.apk and FWUpgrade.apk to back ups which stopped the NG6 update.
Now I have a security update that keeps showing up in my notification panel. I just clear it and it goes away for a while but always comes back.
What else do I need to freeze to get this to stop.
Thanks.
Similar question. I went from rooted NC5 to stock NC5 using ODIN.
1. I still see Customer Recovery icon on boot
2. I get this same security update msg as well, but it will not install for some reason.
I actually want to go to complete OTA stock. How can I solve above 2 issues?
Okay here's my tale of woe..
I rooted my phone last year - but at some point - took an update and lost root.
Though the phone still displays the "custom" boot screen with the padlock.
I tried to take the Lollipop update through the OTA but it fails and I get the "laying on his back" failed Android dude...
The phone DID take the first update.
I have: wiped cache in recovery, wiped data and cache in download manager.
No luck.
I have tried loading the NC5 kernel back on (via Odin 3.09) - but that makes the phone 100% unstable...reboots every 3 minutes..no access to apps - they lock and reboot etc etc.
Loaded the NG6 kernel back on to re-stabilize the phone and tried to Kies the update.
Kies downloads the update then when it tries to apply it the phone boots into "download mode"
I have been advised to:
I had the same custom boot screen--even after unrooting. Tried using Triangle Away to reset the binary count, but the count was already at 0. So ultimately I had to re-flash the NC5 kernel via Odin to get things truly back to being recognized as stock.
Then updates started rolling in for NG6, then NK1. Finally the two-part update for Lollipop.
Click to expand...
Click to collapse
and - of course that doesn't work. NC5 won't let the phone run long enough to take an update..
It has been said:
Try to flash the OC1 with the pit file
Click to expand...
Click to collapse
But I haven't found the stock OC1 file anywhere to even try and begin to get it loaded.
Honestly - I'm not even really concerned about rooting right now. I'd really just like to get the phone back to a stock configuration and kernel and lollipop.
Developer mode is enabled. Obviously both Kies and Odin talk to the phone with no problems.
Any ideas ?
Thanks, Dan
Get your phone to 4.4.2, use the verizon software upgrade assistant program preloaded on your phone to update. I had this exact same problem and that's how I got to 5.0.1
You WILL lose root. And there's no method to root 5.0 right now, and people have been saying that there might never be. You also won't be able to downgrade, or at least there's no method to do so at the moment, so you will be stuck with lollipop for a while, maybe forever.
Yes.
Maybe I need to clarify.
I do not care about root at this point. I just want to get the phone back to a stock state and take the Lollipop update.
I'm curious as to why I will never be able to update beyond Lollipop.
Doesn't matter I guess - the phone will have been replaced by then - but still...why ?
Thanks, Dan
CyrusKhane said:
Get your phone to 4.4.2, use the verizon software upgrade assistant program preloaded on your phone to update. I had this exact same problem and that's how I got to 5.0.1
You WILL lose root. And there's no method to root 5.0 right now, and people have been saying that there might never be. You also won't be able to downgrade, or at least there's no method to do so at the moment, so you will be stuck with lollipop for a while, maybe forever.
Click to expand...
Click to collapse
I've downloaded (3) different 4.4.2 Firmwares.
FNK1
FNC5 (No Wipe)
FNG6 (No Wipe)
Any opinion on which one is best ?
Did you download these manually or OTA? When I re-flashed the NC5 kernel, I received NG6 then NK1 then the 2-part Lollipop updates all OTA back-to-back.
Sent from my SCH-I545 using XDA Free mobile app
I would use the ng6. That's what I was running.
Rip Syntaxx said:
Did you download these manually or OTA? When I re-flashed the NC5 kernel, I received NG6 then NK1 then the 2-part Lollipop updates all OTA back-to-back.
Sent from my SCH-I545 using XDA Free mobile app
Click to expand...
Click to collapse
Manually - from these (XDA) forums.
danielzink said:
Manually - from these (XDA) forums.
Click to expand...
Click to collapse
Hmm... I'm not sure if it makes a difference to download OTA instead of manually. I would think it's worth a shot flashing NC5 (if it will let you downgrade) and using the software update feature to update OTA the rest of the way.
Sent from my SCH-I545 using XDA Free mobile app
Got it finally !
started out by flashing (FNG6 (No Wipe)) in Odin 3.09
That got me to regular boots with no "custom" screen showing the lock symbol.
Then I had to take OTA updates to FNK1 then the OTA preliminary Lollipop update then (OTA) finally Lollipop itself.
No root - but that's OK.
It took about an hour and a couple shutdowns to get things running smoothly but it's all good now.
Thanks everyone for their help.
I'm new to the forum. I've been lurking here for the past couple of weeks trying to piece together a way to root my SCH i545 running 5.0.1 with the pl1 update so that I might get to the point of running a custom nougat rom. Yesterday I started trying to figure out how to get a custom rom loaded on it, but got nowhere. I've never done anything like this before.
So, today I came across this thread. https://forum.xda-developers.com/galaxy-s4-verizon/general/update-1545vrsgpl1-t3537781 which linked me to the stang5litre rom. I thought I'd see if I could get that running. I downloaded kingoroot and got it rooted, confirmed by root checker. Then I downloaded SuperSU and tried to load it. I used Titanium Backup to remove the superuser, but when I tried to install the SuperSU it said that KNOX was interfering with the install. After some reading, uninstalled the KNOX using Titanium Backup and tried installing the SuperSU again. This time I got an error that said I needed to reboot. On rebooting, the phone makes it as far as the red Verizon screen and sticks.
It will still boot into the Recovery and Download modes. Can someone please tell me how to proceed from here?
Your best option is to start over by re-flashing it with stock PL1.
Then be careful during the superuser replacement process, that's when things went wrong basically breaking the system bootup.
Try using something like Super SUme to replace King with SSU.