Related
Is anyone working on rooting the actual NC5 update from Verizon?
Yes I know we can Odin back to mk2 and then flash back to NC5 root but my question is, is anyone actually working on finding a root exploit like saferoot on mj7
I asked the same thing the other day (maybe on another forum) and never got a clear answer. Anyway, I hope someone is!
Sent from my SCH-I545
nedfred5507 said:
Is anyone working on rooting the actual NC5 update from Verizon?
Yes I know we can Odin back to mk2 and then flash back to NC5 root but my question is, is anyone actually working on finding a root exploit like saferoot on mj7
Click to expand...
Click to collapse
Yes. However, let me clarify what "working on" means.
To gain root, you've got to find a means of bypassing the kernel's security, or find an installed application with root permissions that has some error that allows us to manipulate it to find root.
Right now, neither of those are known, so you can't get root. Hopefully someone will eventually find a way, but who knows when. Maybe never.
security holes are patched with each subsequent release of a firmware update. Thats why many of us aren't updating our phones becasue once you do, you may lock yourself out. Work has been done on trying to find a bootloader exploit since ME7 was released and none so far....same issue with root, there is no native root method for NC5 and there might never be as kmu1 stated
I have been searching all over to find any information on this new kitkat update for the Note 2. I haven't found much. I think the main thing I found was Knox 2.0 or whatever. Is it possible, or is anyone working on a way to at least get root back on here? I didn't do the update yet, but it's bugging me. I would like kitkat and I like this phone, but samsung/verizon locking this thing down is driving me nuts. To the point that I want to sell this phone. So yeah, is anyone aware of any information on the 4.4.2 update and the possibilities to root it at least. I don't even care to install ROMS.
S5 rooted
mkobella said:
I have been searching all over to find any information on this new kitkat update for the Note 2. I haven't found much. I think the main thing I found was Knox 2.0 or whatever. Is it possible, or is anyone working on a way to at least get root back on here? I didn't do the update yet, but it's bugging me. I would like kitkat and I like this phone, but samsung/verizon locking this thing down is driving me nuts. To the point that I want to sell this phone. So yeah, is anyone aware of any information on the 4.4.2 update and the possibilities to root it at least. I don't even care to install ROMS.
Click to expand...
Click to collapse
Galaxy S5 just rooted maybe this will work for Note2 after 4.4.2 update
http://forum.xda-developers.com/showpost.php?p=53406788&postcount=1
I think it's worth trying for everyone without root. Seems to be successful on several different phones.
Sent from my SCH-I605 using Tapatalk
Yeah I'm just not sure I want to let this update go through just to find out it fails and I'm stuck locked down. Is anyone willing to try? Or has tried? I guess I may have to be the first.
Mkobella I'm in the same boat as you... I've been lurking waiting to see if towel root will work for the 4.4.2 update... I'm on 4.3 and not going to lose my root... If you check it out please report back... It would be awesome if someone who took the kit Kat update could try it out
dpeck411 said:
Mkobella I'm in the same boat as you... I've been lurking waiting to see if towel root will work for the 4.4.2 update... I'm on 4.3 and not going to lose my root... If you check it out please report back... It would be awesome if someone who took the kit Kat update could try it out
Click to expand...
Click to collapse
Looks like it doesn't work currently maybe something will be available in the upcoming days
http://forum.xda-developers.com/showpost.php?p=53423728&postcount=548
Thats unfortunate, has anyone else given it a try?
Yeah this is unfortunate. I would try it if I could flash back to 4.3. Has anyone attempted that? I would gladly chip in and help with this, but I'm new and don't know much about rooting and what not. If there are people working on it I would like to find them.
So... I can confirm that this root does not work for the VZW Galaxy note II running the latest update 4.4.2 (ND7). I tried it several times. Not sure if I am doing anything wrong, but from what I gathered, its pretty straight forward. Just run the app. Also, I can tell you that once you download the OTA you WILL NOT be able to go back to a previous version. I tried to Odin back to MJ9 4.3 and that failed. So, essentially, once you do the kitkat update, you're screwed, and stuck. I can't root, can't go back now. Hopefully someone else can figure this out. Or chime in?
Please try these steps: http://forum.xda-developers.com/showthread.php?t=2784138
Rooted wife's S4. Ran towelroot. Tried the play store supersu but it couldn't install su binaries so I thought it wasn't rooted until I tried an app that needed root. It got root via supersu even tho it kept complaining about binaries. I then followed the steps in that post and the phone is now rooted with safestrap.
Also try app called root checker from play store.
Towel root does not work. The phone just reboots almost immediately after pressing make it ra1n. Once it boots back up I have checked with root checker. I am not root. Tried it several times. It appears that the exploit gets past the enforce SELinux but for some reason it doesn't on this phone. Or maybe it's Knox that is knocking it down and rebooting the phone.
Sent from my SCH-I605 using Tapatalk
mkobella said:
Towel root does not work. The phone just reboots almost immediately after pressing make it ra1n. Once it boots back up I have checked with root checker. I am not root. Tried it several times. It appears that the exploit gets past the enforce SELinux but for some reason it doesn't on this phone. Or maybe it's Knox that is knocking it down and rebooting the phone.
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
doesn't work with mine either
after reading the thread on towel with the drastic high usage is disappointing. Im seeing now where someone suggested puttting SuperSU on before the the towel exploit .. however it questionable. RIght now most talk seems to steam from shutting off knox which seems to be the issue.
Unfortunately putting supersu on before you use the towel exploit does nothing. Supersu needs root in order to run or do anything. And even so. I ran the exploit several times. First time with with supersu. Second time with out. Then I reinstalled the latest and ran it again. Still nothing. Phone just reboots and is unrooted. Also, you can't disable Knox with out root. Whether that be from supersu disabling it or freezing and/or uninstalling Knox files. You need root in order to do these things. I ended up emailing geohot a few days ago about it, but he never got back to me. Like I said I am willing to try things and help on a project. But, I am no programmer.
Sent from my SCH-I605 using Tapatalk
No root eiter
mkobella said:
Unfortunately putting supersu on before you use the towel exploit does nothing. Supersu needs root in order to run or do anything. And even so. I ran the exploit several times. First time with with supersu. Second time with out. Then I reinstalled the latest and ran it again. Still nothing. Phone just reboots and is unrooted. Also, you can't disable Knox with out root. Whether that be from supersu disabling it or freezing and/or uninstalling Knox files. You need root in order to do these things. I ended up emailing geohot a few days ago about it, but he never got back to me. Like I said I am willing to try things and help on a project. But, I am no programmer.
N2 VZW
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
I too am in this boat! have tried EVERY possible way too get towel too work on my N2 VZW but nada!. I also emaled him and G+ him but NO response?, So i think we are left out!!
I guess we are left out. I'm sick of Verizon and Samsung locking us down! Well I'm not giving up. I keep looking and trying. Hopefully someone else comes on here and helps out.
Sent from my SCH-I605 using Tapatalk
Hey everyone. I am in the same boat. I just want to root because I can't save anything to my SD card anymore. If anyone has a fix please let us know!!
Thanks!!
Sent from my SCH-I605 using XDA Free mobile app
Me too!
It has nothing to do with Verizon. It's all samsung
Sent from my LG-VS980 using XDA Free mobile app
Well, I managed to get a log of this Towelroot running via ADB. I emailed Geohot again, and pasted a portion of my log in the email. I'm hoping he responds this time. I will post a snippit of my log on here for anyone to see if they can make sense of it. Hoping Geohot or someone can respond and shed some light on this, as to why this doesn't work for us, and if it can. After the last line the phone just reboots, no root.
http://pastebin.com/P05AuknT
I don't mean to beat a dead horse, as I'm sure it's been brought up. But every search I've done just brings up how to update to OC1 without losing root. All the way back to the original Motorola Droid, I've always rooted and added a custom recovery and ROM to every phone I've had. I was running Hyperdrive RLS20 and loved it. I've been using Hyperdrive since my Galaxy S3. Then I saw Hyperdrive RLS21 came out and decided I wanted to give it a shot. And although I've flashed over a few hundred ROMs no problem, this time really screwed my phone. I could only get into DL mode. I tried about 25 different ways until I had Kies fix it, which put it on 5.0.1. Can I revert down with Odin? Or is there anything I can do to get root and SU back. Any help would be much, MUCH appreciated
Nope, by taking the latest OTA (or in this case Kies) you've locked yourself into the latest version, for which there is currently no Root
That sucks. No way to use Odin in order to downgrade or anything? This is the first time since I've ever owned an android phone that I've been stuck without root
52brandon said:
That sucks. No way to use Odin in order to downgrade or anything? This is the first time since I've ever owned an android phone that I've been stuck without root
Click to expand...
Click to collapse
Nope. Locked Bootloader sucks.
Every single time there is an update these individuals always end up in this situation! !! No matter how many times they're told to wait and just not update!!!
Charlie115 said:
Every single time there is an update these individuals always end up in this situation! !! No matter how many times they're told to wait and just not update!!!
Click to expand...
Click to collapse
Don't lump me In with that crowd. I had no intention on going to 5.0.1. If you read my original post, I was upgrading to Hyperdrive KK21 from KK20 (and yes, I followed every single instruction to the T. My only guess is that the USB connection got messed up and only flashed a portion causing the problems) and it **** the bed mid-update. I couldn't get into SS recovery or even stock recovery, only DL mode. I spent 2 days without a working phone trying to flash every single Odin file that retained root and they all failed. So I used Kies to try to repair it and ended up ****ed on 5.0.1. The one solution I didn't want. I've NEVER had an android since the D1 that wasn't rooted running a custom ROM. Which is why I'm so desperately trying to get back to rooted. While 5.0.1 is actually a very nice OS, not having all the root options is killing me. And since its now 2 generations old, my hopes that a root exploit will be found, or that people even care enough to try to find one are extremely low. But, I sure hope I'm wrong, and that an exploit for one of the newer generations Galaxies will work on this one too. I'm OCD about having root and this is killing me
52brandon said:
I couldn't get into SS recovery or even stock recovery, only DL mode. I spent 2 days without a working phone trying to flash every single Odin file that retained root and they all failed.
Click to expand...
Click to collapse
If you're ever in this situation again, give up on retaining your current root, flash back to true stock (with a re-partition .pit file as well), and re-root. If you had flashed the nc5 full-wipe with the .pit file and just restored root from a clean system, you would have been fine.
52brandon said:
Don't lump me In with that crowd. I had no intention on going to 5.0.1. If you read my original post, I was upgrading to Hyperdrive KK21 from KK20 (and yes, I followed every single instruction to the T. My only guess is that the USB connection got messed up and only flashed a portion causing the problems) and it **** the bed mid-update. I couldn't get into SS recovery or even stock recovery, only DL mode. I spent 2 days without a working phone trying to flash every single Odin file that retained root and they all failed. So I used Kies to try to repair it and ended up ****ed on 5.0.1. The one solution I didn't want. I've NEVER had an android since the D1 that wasn't rooted running a custom ROM. Which is why I'm so desperately trying to get back to rooted. While 5.0.1 is actually a very nice OS, not having all the root options is killing me. And since its now 2 generations old, my hopes that a root exploit will be found, or that people even care enough to try to find one are extremely low. But, I sure hope I'm wrong, and that an exploit for one of the newer generations Galaxies will work on this one too. I'm OCD about having root and this is killing me
Click to expand...
Click to collapse
Well, you should have known better than to use kies...
Sent from my SCH-I545 using XDA Free mobile app
Honestly I don't even think that devlopers will make much effort to even find out how to root this version as its says that this is one of two updates before getting lollypop.
Development Forums are for developers to share their work and post their Roms and Mods.
Questions belong in the Q&A section.
Thread has been moved to correct section, please pay attention to XDA rules.
Root
52brandon said:
I don't mean to beat a dead horse, as I'm sure it's been brought up. But every search I've done just brings up how to update to OC1 without losing root. All the way back to the original Motorola Droid, I've always rooted and added a custom recovery and ROM to every phone I've had. I was running Hyperdrive RLS20 and loved it. I've been using Hyperdrive since my Galaxy S3. Then I saw Hyperdrive RLS21 came out and decided I wanted to give it a shot. And although I've flashed over a few hundred ROMs no problem, this time really screwed my phone. I could only get into DL mode. I tried about 25 different ways until I had Kies fix it, which put it on 5.0.1. Can I revert down with Odin? Or is there anything I can do to get root and SU back. Any help would be much, MUCH appreciated
Click to expand...
Click to collapse
KingRoot 4.1 rooted my galaxy s4 on oc1....and try flashing an nc5 tar in flashfire
You cannot flash anything with flashfire. If you flash that tar, you WILL brick.
Question
Just wondering, i have rooted my OC1 with Kingroot 4.1, now, can someone make a guide showing how to downgrade from OC1?
PD:. Sorry for my horrible english.
Epiphany^ said:
Just wondering, i have rooted my OC1 with Kingroot 4.1, now, can someone make a guide showing how to downgrade from OC1?
PD:. Sorry for my horrible english.
Click to expand...
Click to collapse
You can't downgrade from OC1.
Downgrade isn't a root issue, it is a bootloader issue. Unless the bootloader gets unlocked, we're stuck on OC1
kingroot does work
I had done the dumb thing and was impatient and did the oc1 update to later find out you can not downgrade and im on Verizon Samsung galaxy s4 (sch-i545) which even on kit kat is very limited to rooting it.. but on a whim I seen a post about king root and it mentioned that and I did see this myself but it will say not supported like it did on mine. but I figured what the hell.. whats the worst that could happen... well im rooted now and only tried because I had seen others make that comment.. well kingroot works for s4 Verizon with locked bootloader.. no need to downgrade from oc1.. just get the app and click... took less than 10 mins if I rememner right.. and I have had no pronlems in 3 days.. it oddly even fixed some of the bugs I was having with oc1 like incoming calls not ringing
Munk3ybones said:
I had done the dumb thing and was impatient and did the oc1 update to later find out you can not downgrade and im on Verizon Samsung galaxy s4 (sch-i545) which even on kit kat is very limited to rooting it.. but on a whim I seen a post about king root and it mentioned that and I did see this myself but it will say not supported like it did on mine. but I figured what the hell.. whats the worst that could happen... well im rooted now and only tried because I had seen others make that comment.. well kingroot works for s4 Verizon with locked bootloader.. no need to downgrade from oc1.. just get the app and click... took less than 10 mins if I rememner right.. and I have had no pronlems in 3 days.. it oddly even fixed some of the bugs I was having with oc1 like incoming calls not ringing
Click to expand...
Click to collapse
You have root. But you have a much lower chance of getting an unlocked Bootloader than anyone on NC5/NK1/NK4. They have root, module loading, and a potential for kexec to run custom kernels.
Don't upgrade to OC1 via OTA if you haven't already everyone! Use Muniz_ri's keeproot upgrade method!
Sent from my Nexus 6 using Tapatalk
---------- Post added at 12:53 AM ---------- Previous post was at 12:53 AM ----------
bigg6987 said:
Downgrade isn't a root issue, it is a bootloader issue. Unless the bootloader gets unlocked, we're stuck on OC1
Click to expand...
Click to collapse
Even then you're stuck. Rollback has little to do with the BL. Rollback is set at a much lower level (physically).
Sent from my Nexus 6 using Tapatalk
Hi there. I just broke my s6 and so had to go back to my old s4, heh. I currently have a rooted OC1, and I was looking at the latest info on available root methods and see that the OF1 can be rooted using kingroot. My phone shows an OTA available but repeatedly fails when trying to update.
My question is, should I try to figure out what is causing the failure, update the "right" way, and then root with kingroot? Or should I just figure out another way to get the update, like I think the old way was to downgrade to OC1, root, then odin the OF1 update. Should I just do that?
This happens when you try to ota on a rom which has root or has been modified. Just dont update it doesnt add any features
I am going crazy trying to resolve my issue. I was tasked with getting CM13 onto a new S4 I545VRUFNK1. The only root that worked was Kingo Root despite several website claiming that towelroot or one click would work, they DID NOT. After installing TWRP and the 3.0.1 recovery, when i go into recover a Verizon message appears saying the software is not authorized so it won't work.
There are several version of this phone which is contributing to the problem. At this point I want to get a stock rom of 4.4.2 and flash it with odin and get it back to the way it was before I tried to do this.
samsmobile won't let me download, samsung-firmware.org only lets me get 3/4 of it and I can't resume it. Everyone wants money for this firmware and even that seems to not work and I probably have to cancel a credit card and dispute the charge
Can someone please either tell me how to bypass the verizon warning so I can get CM13 (i found a thread that talked about editing some system files, but looked very risky) or even better, help me with a download of the firmware, should be 1.5 GB in size so I can reflash with Odin
Please help before I or the phone break
Use samsung kies for the firmware. You will not get cm13 on nk1, stop trying or you will hard brick.
Sent from my SCH-I545 using XDA-Developers mobile app
http://forum.xda-developers.com/showthread.php?t=2735172
you are never going to get CM or ASOP or any rom that requires a custom bootloader/recovery/kernel to run on the S4
its not possible