I'm trying to help a family member root their new phone. The most up to date guide I've found here is for the previous update (NI2) and I haven't seen anything for the Verizon NK2 version. Is it still possible to root this version? If so do you know where I can find out how?
worf65 said:
I'm trying to help a family member root their new phone. The most up to date guide I've found here is for the previous update (NI2) and I haven't seen anything for the Verizon NK2 version. Is it still possible to root this version? If so do you know where I can find out how?
Click to expand...
Click to collapse
It's the same thing, doesn't matter what the starting version is. You still have to downgrade to NGC
ldeveraux said:
It's the same thing, doesn't matter what the starting version is. You still have to downgrade to NGC
Click to expand...
Click to collapse
So just downgrade the kernal to NCG, root, then update the kernal using Odin? Skipping the step about flashing the OTA since its already updated?
worf65 said:
So just downgrade the kernal to NCG, root, then update the kernal using Odin? Skipping the step about flashing the OTA since its already updated?
Click to expand...
Click to collapse
No not at all. Just go read the thread it's sticked at the top, or at least it should be
worf65 said:
So just downgrade the kernal to NCG, root, then update the kernal using Odin? Skipping the step about flashing the OTA since its already updated?
Click to expand...
Click to collapse
I believe that flashing the kernel would work but you would have to work your way through a lot of FC's. I normally flash a full tar but you having a brand new phone, this probably isn't necessary but it is what I normally do ( below is the tar file I use. It is a complete internal wipe to a like new phone on NGC). Root with towelroot, download SuperSU from play store, update the binaries and reboot. I would suggest safestrap. You would need to download from play store then install busybox first. Then install safestrap and install its recovery.
https://www.androidfilehost.com/?fid=23610159112652178
Tulsadiver said:
I believe that flashing the kernel would work but you would have to work your way through a lot of FC's. I normally flash a full tar but you having a brand new phone, this probably isn't necessary but it is what I normally do ( below is the tar file I use. It is a complete internal wipe to a like new phone on NGC). Root with towelroot, download SuperSU from play store, update the binaries and reboot. I would suggest safestrap. You would need to download from play store then install busybox first. Then install safestrap and install its recovery.
https://www.androidfilehost.com/?fid=23610159112652178
Click to expand...
Click to collapse
I'm pretty familiar with how rooting the S5 works before updates as that is how I did mine (froze the updater and didn't have time to figure out how to safely update). What I am confused about is what I do when coming from a later software version, the guide is even called "Safely Upgrade and Root..." not how to downgrade and root, and the guide to update to lollipop seems to require already being rooted.
worf65 said:
I'm pretty familiar with how rooting the S5 works before updatesj as that is how I did mine (froze the updater and didn't have time to figure out how to safely update). What I am confused about is what I do when coming from a later software version, the guide is even called "Safely Upgrade and Root..." not how to downgrade and root, and the guide to update to lollipop seems to require already being rooted.
Click to expand...
Click to collapse
I told you how to root, downgrade, root, then upgrade. Plus, you need to read down a little further. See notes #4
http://forum.xda-developers.com/ver...w-to-update-to-g900voc4-5-0-keeproot-t3068546
Tulsadiver said:
I told you how to root, downgrade, root, then upgrade. Plus, you need to read down a little further. See notes #4
http://forum.xda-developers.com/ver...w-to-update-to-g900voc4-5-0-keeproot-t3068546
Click to expand...
Click to collapse
Ok, I had found that guide before getting this new phone for my phone but didn't look at it again since I remembered that it had to be rooted already and was assuming I had to root on an earlier version hence the confusion.
Its understandable why people without root don't read it or at least don't read on down.
Related
Is there any way to gain root for most recent att s4 update? Build number is KOT49H.I337UCUFNC1
I've been asking the same question every since the update as well. I was hoping to install a Custom ROM on my phone, but I am playing it safe until it's been confirmed workable with the latest update. As a back up, I've seen people mention it's possible to rollback this update to NB1. I've had no luck so far pulling up a thread about rolling back updates, though...
kot49h.i337ucufnc1
bluestar23 said:
Is there any way to gain root for most recent att s4 update? Build number is KOT49H.I337UCUFNC1
Click to expand...
Click to collapse
I tried the downgrade method for the NB1 and it failed with Odin3 V3.09 and got stuck with Odin3 V1.85
Root
Also looking for a way to root the i337ucufnc1
I337UCUFNC1 System Status
I was rooted yet my ATT phone still forced 2 ATT push updates. I lost root yet my phone is still showing as custom system status and unlocked custom icon on reboot.
Ditto
Jbjamin said:
I was rooted yet my ATT phone still forced 2 ATT push updates. I lost root yet my phone is still showing as custom system status and unlocked custom icon on reboot.
Click to expand...
Click to collapse
Are you able to access your external SD? I too have the same Build and have lost access to my SD, can't root, or unlock, even using the Network Unlock code from AT&T. I've lost apps, it has slowed waaaaaaaaaaaay down, and the battery is not lasting, even with Powersave. I just got this phone and the guy I bought it from factory reset it. There was an update that accepted, but it stopped and said I had to restart the update for some reason. I did, but it is still 4.4.2, but now has a different Security Software Version, MDF v1.0 Release 2. It won't accept USSD codes and gives me a 'connection error invalid mmi code' message.
Are you having the same issues? I sure wish I could find something on this. Every time I try to search, it changes the I337UCUFBNCI to "Did you mean: i337ucufnb1?" I can't find anything totally, just bits and pieces. UGHHHHHH
Success, I couldn't find a step by step tutorial to fix my issue but thanks to a full nb1 .tar and a couple other files all given by contributors I was able to odin download to reset the custom icon to official then I had to odin download the full nb1 .tar. after doing this I did the ota att nc1 update and my phone is good as factory. Until I decide to root again that is.
If you would like some help let me know
i337ucufnc1 root
Jbjamin said:
Success, I couldn't find a step by step tutorial to fix my issue but thanks to a full nb1 .tar and a couple other files all given by contributors I was able to odin download to reset the custom icon to official then I had to odin download the full nb1 .tar. after doing this I did the ota att nc1 update and my phone is good as factory. Until I decide to root again that is.
If you would like some help let me know
Click to expand...
Click to collapse
I would like some help! How were you able to root fnc1? ! And is safe strap the only custom recovery that will work I'm guessing?
thanks in advance.
adam
I did not root nc1, but it is possible thanks to some very smart contributors. I was previously rooted and wanted to unroot to factory. I became unrooted but my system was still unofficial and custom which I was having a problem getting rid of so I can trade in my phone in the future for credit. Just search nc1 root on xda and you should find the info. Its a bit of a process but you should be able to figure it out. You need to odin download back to nb1 first and go from there. If you would like some additional help I can try to give some advise but I'm no expert or developer just an enthusiast
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
bluestar23 said:
Is there any way to gain root for most recent att s4 update? Build number is KOT49H.I337UCUFNC1
Click to expand...
Click to collapse
It will help you maybe: HERE
Reboot your phone into download mode and use the NB1 full odin tar. http://forum.xda-developers.com/show...66&postcount=2
Use the MK2 downgrade method to obtain root. http://forum.xda-developers.com/show....php?t=2663545
Then use the NC1 keep root http://forum.xda-developers.com/show....php?t=2730144
This should help.
Jbjamin said:
Reboot your phone into download mode and use the NB1 full odin tar. http://forum.xda-developers.com/show...66&postcount=2
Use the MK2 downgrade method to obtain root. http://forum.xda-developers.com/show....php?t=2663545
Then use the NC1 keep root http://forum.xda-developers.com/show....php?t=2730144
This should help.
Click to expand...
Click to collapse
Can you repost those links please because none of them are valid...
Somehow when the post was made the links were messed up so the middle part is missing and just has ... instead. Thanks!
Trying to fix my mothers phone which she accidentally updated!
DornoDiosMio said:
Can you repost those links please because none of them are valid...
Somehow when the post was made the links were messed up so the middle part is missing and just has ... instead. Thanks!
Trying to fix my mothers phone which she accidentally updated!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=50667366
http://forum.xda-developers.com/showthread.php?t=2663545
http://forum.xda-developers.com/showthread.php?t=2730144
There you go
Rooting I337UCUFNC1
Hi. I have followed the threads for a while on rooting my I337. I purchased it used a month ago and really want to root it and install a custom rom. But by reading all the threads I am confused and somewhat worried I will brick it!
Can someone explain to me real clearly what software and files I should use to obtain root on AT&T I337UCUFNC1 and install a custom rom? I am ok with downgrading.
Thanks much.
Rooting the ATT SGH-I337 build I337UCUFNC1
I have this phone: build I337UCUFNC1, and was finally able to root it via the Towelroot method: Towelroot dot com.
fhuddles said:
I have this phone: build I337UCUFNC1, and was finally able to root it via the Towelroot method: Towelroot dot com.
Click to expand...
Click to collapse
i was able to root my I337UCUFNC1 using towelroot as well. however stuck trying to unlock my bootloader to install this custom rom: http://forum.xda-developers.com/showthread.php?t=2537495
any help is appreciated
It's just not clear when I look at all the about phone page.It does say 4.4.2.
pego99 said:
It's just not clear when I look at all the about phone page.It does say 4.4.2.
Click to expand...
Click to collapse
Look at the "Build number".
Cat McGowan said:
Look at the "Build number".
Click to expand...
Click to collapse
NCG so that's it.
Off-Topic Question
Cat McGowan said:
Look at the "Build number".
Click to expand...
Click to collapse
Hi Cat,
Sorry, this will be off topic, but I noticed you have an s5 running the latest Android build (KTU84P.G900VVRU1ANI2) and are still rooted. So I'm assuming that the new OTA for this won't break root? (I'm on a Rooted Verizon S5, running 4.4.2, Build #KOT49H.G900VVRU1ANCG, Hardware Version G900V.05, Kernel Version 3.4.0, Rooted via Towelroot)
Is that true, or did you have to root somehow after upgrading to 4.4.4 in the latest build?
Thanks for your answer.
akoziol90 said:
Hi Cat,
Sorry, this will be off topic, but I noticed you have an s5 running the latest Android build (KTU84P.G900VVRU1ANI2) and are still rooted. So I'm assuming that the new OTA for this won't break root? (I'm on a Rooted Verizon S5, running 4.4.2, Build #KOT49H.G900VVRU1ANCG, Hardware Version G900V.05, Kernel Version 3.4.0, Rooted via Towelroot)
Is that true, or did you have to root somehow after upgrading to 4.4.4 in the latest build?
Thanks for your answer.
Click to expand...
Click to collapse
Allowing the NI2 OTA update will cause you to lose root access. To regain root access after the OTA update, you need to (1) use ODIN to install the NCG kernel, (2) run TowelRoot to gain root access again, and (3) use ODIN to install the NI2 kernel. You can download the NCG and NI2 kernels using links in THIS POST. If you already had SuperSU installed before the OTA update, just run it and acknowledge the error message, and then reboot; SuperSU will fix itself. Otherwise, install SuperSU.
Question
Cat McGowan said:
Allowing the NI2 OTA update will cause you to lose root access. To regain root access after the OTA update, you need to (1) use ODIN to install the NCG kernel, (2) run TowelRoot to gain root access again, and (3) use ODIN to install the NI2 kernel. You can download the NCG and NI2 kernels using links in THIS POST. If you already had SuperSU installed before the OTA update, just run it and acknowledge the error message, and then reboot; SuperSU will fix itself. Otherwise, install SuperSU.
Click to expand...
Click to collapse
Hi I'm new to this and I have a few questions before doing this. I am have the KTU84P.G900VVRU1ANI2 Build number and I have never rooted my phone before. Will this method still work even though I never previously rooted? Also what are the chances of me bricking my device?
After doing this procedure should I then freeze the OTA update service?
Okay so I've been browsing through the forums and been reading up on this phone (even contacted Samsung about info on unlocking the bootloader, no go on that. Had to try though)
Basically I want to know what's the proper procedure for installing custom roms on an NC4 device 4.4.2
Things I know:
Bootloader is unlockable at the moment (hoping for some good news in the future)
Towelroot for rooting
Safestrap for recovery
(Both just download and install the apk)
Things I don't know:
Kernel?
Somebody said I had to flash the NC2 kernel via Odin?
Knox?
What is this? What trips it?
I did see the list of guides and I did read and watch all the necessary ones, but the date on those are from 2 years ago and I just need confirmation on if I'm going about this right.
Any help is appreciated. I thank you in advance for taking the time to read this.
Please excuse my lack of knowledge, this is my first Samsung device.
Also, what would happen if somebody were to flash the DE stock files via Odin to a Retail N3?
If you upgraded to NC4 or NK1, you're stuck until Samsung unlocks the bootloader or Verizon stops lying to their customers. There is no root available after upgrade at this moment in time.
Dravekx said:
If you upgraded to NC4 or NK1, you're stuck until Samsung unlocks the bootloader or Verizon stops lying to their customers. There is no root available after upgrade at this moment in time.
Click to expand...
Click to collapse
I didn't upgrade to NC4, it came like this.
rdar_93 said:
I didn't upgrade to NC4, it came like this.
Click to expand...
Click to collapse
That sucks. You can't do anything about it at the moment. I was forced to upgrade and lost root. Custom ROMs won't be available to you or me until someone finds a hole to unlock the bootloader. Welcome to our Verizon Note 3 rooting dilemma.
mirrin said:
You do not have a dev version so cm 11 or 12 is a far off dream you won't get. Your bootloader is locked there is no unlock.
You are in luck nc4 is root able using towel root then safe strap and the unified firmware. You will need odin and a pc for flashing a few things the NK1 modem towel root and the unified firmware. Pick a rom from the development thread i suggest jasmine 1.x or eclipse.
Click to expand...
Click to collapse
Copied from another post I had.
I don't know much about the device which is why I'm trying to find out.
Dravekx said:
That sucks. You can't do anything about it at the moment. I was forced to upgrade and lost root. Custom ROMs won't be available to you or me until someone finds a hole to unlock the bootloader. Welcome to our Verizon Note 3 rooting dilemma.
Click to expand...
Click to collapse
I actually just got root on my phone, I felt adventurous and installed towelroot and voila it rooted my phone.
I should state that I'm on 4.4.2, not 4.4.4.
Checked root status with Titanium Backup Pro, everything checked out a-okay.
rdar_93 said:
Okay so I've been browsing through the forums and been reading up on this phone (even contacted Samsung about info on unlocking the bootloader, no go on that. Had to try though)
Basically I want to know what's the proper procedure for installing custom roms on an NC4 device 4.4.2
Things I know:
Bootloader is unlockable at the moment (hoping for some good news in the future)
Towelroot for rooting
Safestrap for recovery
(Both just download and install the apk)
Things I don't know:
Kernel?
Somebody said I had to flash the NC2 kernel via Odin?
Knox?
What is this? What trips it?
I did see the list of guides and I did read and watch all the necessary ones, but the date on those are from 2 years ago and I just need confirmation on if I'm going about this right.
Any help is appreciated. I thank you in advance for taking the time to read this.
Please excuse my lack of knowledge, this is my first Samsung device.
Also, what would happen if somebody were to flash the DE stock files via Odin to a Retail N3?
Click to expand...
Click to collapse
Ahhhh... You're good to go then! Find a good custom ROM and follow the instructions. Whatever you do.. Don't upgrade!
rdar_93 said:
I actually just got root on my phone, I felt adventurous and installed towelroot and voila it rooted my phone.
I should state that I'm on 4.4.2, not 4.4.4.
Checked root status with Titanium Backup Pro, everything checked out a-okay.
Click to expand...
Click to collapse
Dravekx said:
Ahhhh... You're good to go then! Find a good custom ROM and follow the instructions. Whatever you do.. Don't upgrade!
Click to expand...
Click to collapse
Lol I still need clarification on the Kernel information that I don't know about.
What do I need to flash?
Do I flash it after I install a custom rom or before?
rdar_93 said:
Lol I still need clarification on the Kernel information that I don't know about.
What do I need to flash?
Do I flash it after I install a custom rom or before?
Click to expand...
Click to collapse
My opinion: If you're doing a custom kernel, make sure it works with whatever ROM you're flashing. I suggest sticking with the stock kernel* until you get the hang of things OR do a little research and learn a bit before you attempt anything. There's a lot of forums with details and help here. I've installed kernels before and after installing ROMs with little or zero problems, but I'm more of a dabbler than a professional.
I would suggest backing up your current setup in case you need to reflash. That's a definite.
Dravekx said:
My opinion: If you're doing a custom kernel, make sure it works with whatever ROM you're flashing. I suggest sticking with the stock kernel* until you get the hang of things OR do a little research and learn a bit before you attempt anything. There's a lot of forums with details and help here. I've installed kernels before and after installing ROMs with little or zero problems, but I'm more of a dabbler than a professional.
I would suggest backing up your current setup in case you need to reflash. That's a definite.
Click to expand...
Click to collapse
Lol that doesn't really answer the question. I hope somebody sees it and clears it up for me
rdar_93 said:
Lol that doesn't really answer the question. I hope somebody sees it and clears it up for me
Click to expand...
Click to collapse
The kernel can't be changed...although it can be "tuned" if you have root.
http://forum.xda-developers.com/showthread.php?p=58813428
Sent from my Note 3 via Tapatalk
Still hoping somebody helps me out and posts a short but precise guide to install a custom rom on 4.4.2 NC4
I don't want to end up bricking my device on the first try. I've been there already and it sucks lol
rdar_93 said:
Still hoping somebody helps me out and posts a short but precise guide to install a custom rom on 4.4.2 NC4
I don't want to end up bricking my device on the first try. I've been there already and it sucks lol
Click to expand...
Click to collapse
It really depends on the ROM, there is no set guide for all ROMs.
Did you install busybox? I like using busybox on rails. Just download the app and click install.
Download the safestrap apk (3.75 B04) and install that, open it and install recovery.
I'm currently running Clean ROM. I am on NC4. I downloaded the rom, and moved it to my SD card. I rebooted to safestrap, wiped data, cache and dalvik then installed the ROM to the stock slot. Then, following the instructions for Clean ROM, I rebooted to download mode from recovery and flashed the NC2 Kernel with odin.
The main thing is to read the installation instructions for the particular ROM you want to flash.
Don't forget to use Titanium backup to freeze SDM app (I think that's what its called) so your phone will stop trying to update.
---------- Post added at 05:29 PM ---------- Previous post was at 05:23 PM ----------
rdar_93 said:
Still hoping somebody helps me out and posts a short but precise guide to install a custom rom on 4.4.2 NC4
I don't want to end up bricking my device on the first try. I've been there already and it sucks lol
Click to expand...
Click to collapse
If you're at all proficient with Odin it is really REALLY hard to brick these phones.
BladeRunner said:
It really depends on the ROM, there is no set guide for all ROMs.
Did you install busybox? I like using busybox on rails. Just download the app and click install.
Download the safestrap apk (3.75 B04) and install that, open it and install recovery.
I'm currently running Clean ROM. I am on NC4. I downloaded the rom, and moved it to my SD card. I rebooted to safestrap, wiped data, cache and dalvik then installed the ROM to the stock slot. Then, following the instructions for Clean ROM, I rebooted to download mode from recovery and flashed the NC2 Kernel with odin.
The main thing is to read the installation instructions for the particular ROM you want to flash.
Don't forget to use Titanium backup to freeze SDM app (I think that's what its called) so your phone will stop trying to update.
---------- Post added at 05:29 PM ---------- Previous post was at 05:23 PM ----------
If you're at all proficient with Odin it is really REALLY hard to brick these phones.
Click to expand...
Click to collapse
Thanks man, I was supposed to update this thread saying that I got through with the proper procedure for installing Jasmine Rom
Although I was running Eclipse before, and I wanted to try going back to stock but it just got stuck on the Verizon splash screen
I'm thinking it's because I had the NC2 kernel active when I should have gone back to the NC4 kernel
I looked for a NC4 kernel to flash but I only saw the modems and tar files, so not knowing if those were the same as kernels I decided to just try Jasmine. So far, I like it.
I have crazy battery drain though. I think it's because I'm running it in Slot 1
just picked up a verizon note 3 android 4.4.2 NC4
one of the very first posts above says you cant do anything on NC4 and then another post says NC4 is ok but just not android 4.4.4
NC4 is the latest update as of this writing isnt it?
what can actually be done with this vzw note 3 on android 4.4.2 NC4?
non dev edition of course
what about knox?
if rooting can be done with this phone on this OS is there any safe way not to trip knox?
en11gma said:
just picked up a verizon note 3 android 4.4.2 NC4
one of the very first posts above says you cant do anything on NC4 and then another post says NC4 is ok but just not android 4.4.4
NC4 is the latest update as of this writing isnt it?
what can actually be done with this vzw note 3 on android 4.4.2 NC4?
non dev edition of course
what about knox?
if rooting can be done with this phone on this OS is there any safe way not to trip knox?
Click to expand...
Click to collapse
I'd be happy to answer your questions
If you have an NC4 device that's running 4.4.2, you are able to gain root access and install safestrap recovery on your device. However, if the android version is 4.4.4, you cannot root or install safestrap.
NC4 is just our last build number, but there are two versions I think, the 4.4.2 and the 4.4.4. In the 4.4.4, they blacklisted every single compatible kernel that could work on the device. They forgot to do it in the 4.4.2 version, that's why we're able to gain root.
On our NC4 4.4.2 Verizon Note 3, we can root, install safestrap recovery and install a very limited amount of roms from the non developer edition selection on the XDA forums.
Rooting via towelroot, to my knowledge, does not trip knox. However, installing safestrap recovery does. But if you're worried about your warranty being voided, I wouldn't panic too much because with our bootloader being locked, it is very easy to flash the original Stock Verizon files through Odin to go straight back to factory settings so it looks like if you just pulled it out the box. The knox code would be reset and you would have a device that looked like if it has never been rooted or modified.
rdar_93 said:
I'd be happy to answer your questions
If you have an NC4 device that's running 4.4.2, you are able to gain root access and install safestrap recovery on your device. However, if the android version is 4.4.4, you cannot root or install safestrap.
NC4 is just our last build number, but there are two versions I think, the 4.4.2 and the 4.4.4. In the 4.4.4, they blacklisted every single compatible kernel that could work on the device. They forgot to do it in the 4.4.2 version, that's why we're able to gain root.
On our NC4 4.4.2 Verizon Note 3, we can root, install safestrap recovery and install a very limited amount of roms from the non developer edition selection on the XDA forums.
Rooting via towelroot, to my knowledge, does not trip knox. However, installing safestrap recovery does. But if you're worried about your warranty being voided, I wouldn't panic too much because with our bootloader being locked, it is very easy to flash the original Stock Verizon files through Odin to go straight back to factory settings so it looks like if you just pulled it out the box. The knox code would be reset and you would have a device that looked like if it has never been rooted or modified.
Click to expand...
Click to collapse
Safestrap does not trip knox.
mjh68 said:
Safestrap does not trip knox.
Click to expand...
Click to collapse
Thanks. I must have tripped mine somehow cause my device says "custom" when booting.
I'm guessing it might be Xposed but I'm not too sure.
rdar_93 said:
Thanks. I must have tripped mine somehow cause my device says "custom" when booting.
I'm guessing it might be Xposed but I'm not too sure.
Click to expand...
Click to collapse
It will say custom, but that isn't tripping knox. Custom can be removed with the triangle away app. Custom just gets flagged like you were saying by changing the recovery , but it doesn't trip the knox counter.
mjh68 said:
It will say custom, but that isn't tripping knox. Custom can be removed with the triangle away app. Custom just gets flagged like you were saying by changing the recovery , but it doesn't trip the knox counter.
Click to expand...
Click to collapse
Then I must be confused about what knox really is.
What is "Knox" then?
So as i dont see the model # listed for CF root or towelroot, im guessing i need to odin custom recovery and flash SU or is there another way out there im not finding?:fingers-crossed:
Karl said:
So as i dont see the model # listed for CF root or towelroot, im guessing i need to odin custom recovery and flash SU or is there another way out there im not finding?:fingers-crossed:
Click to expand...
Click to collapse
I was able to use towelroot to get access on this device. I haven't been able to get TWRP onto it though, or get a Rom on either.
---------- Post added at 10:19 AM ---------- Previous post was at 10:07 AM ----------
Karl said:
So as i dont see the model # listed for CF root or towelroot, im guessing i need to odin custom recovery and flash SU or is there another way out there im not finding?:fingers-crossed:
Click to expand...
Click to collapse
I was able to use towelroot to get access on this device. I haven't been able to get TWRP onto it though, or get a Rom on either.
Hmm how did you get towel root to work
Sent From HTC One M9
Karl said:
Hmm how did you get towel root to work
Sent From HTC One M9
Click to expand...
Click to collapse
If this is like a lot of Samsung devices then what's going on is the early firmware (NE2) was rootable with towelroot, but the more recent one (NK1) is not. Check your settings > about tablet to see which build number you're on (I'm assuming it's NK1). The most immediate solution would be to just downgrade the firmware, root, and stay with that (disable update notifications/freeze the updater app).
However, if you know what you're doing, it's only the kernel that needs to be changed. So extract the kernel file (boot.img) from both firmware files and make a tar file for each boot.img. Flash the older kernel, root with towelroot, then flash the newer kernel, and voila you're rooted on the latest build. Your call
thisisapoorusernamechoice said:
If this is like a lot of Samsung devices then what's going on is the early firmware (NE2) was rootable with towelroot, but the more recent one (NK1) is not. Check your settings > about tablet to see which build number you're on (I'm assuming it's NK1). The most immediate solution would be to just downgrade the firmware, root, and stay with that (disable update notifications/freeze the updater app).
However, if you know what you're doing, it's only the kernel that needs to be changed. So extract the kernel file (boot.img) from both firmware files and make a tar file for each boot.img. Flash the older kernel, root with towelroot, then flash the newer kernel, and voila you're rooted on the latest build. Your call
Click to expand...
Click to collapse
do you have the NE2 firm ?
Karl said:
do you have the NE2 firm ?
Click to expand...
Click to collapse
I really wish I had a better link for you but it can be found: here
thisisapoorusernamechoice said:
I really wish I had a better link for you but it can be found: here
Click to expand...
Click to collapse
thanks,i saw it on sammobile but you gotta pay to DL
have you used this to make a tar? http://forum.xda-developers.com/showthread.php?t=2446269
Karl said:
have you used this to make a tar? url
Click to expand...
Click to collapse
I have not tried, sorry
I did this with the t337a, if you want I could take a shot at it. I have no way of making sure it works though. Let me know if you are interested or if anyone would be willing to test the kernel.
I own the Tab S. It was released after towelroot was patched. So recently when Kingroot update their root method and such, we now can root with kingroot on KitKat ANK1 firmwares and not trip Knox. Of course people who owned att devices said it worked and some with Verizon said it didn't work. I mean its worth a try if anyone wants to try kingroot.
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Rooted! SM-T537V
Kingroot worked
DUHAsianSKILLZ said:
I own the Tab S. It was released after towelroot was patched. So recently when Kingroot update their root method and such, we now can root with kingroot on KitKat ANK1 firmwares and not trip Knox. Of course people who owned att devices said it worked and some with Verizon said it didn't work. I mean its worth a try if anyone wants to try kingroot.
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Click to expand...
Click to collapse
Hi ive got kingroot goin and it says its rooted but when u restart it, its gone.
I have a Verizon Galaxy S5 (G900V) that I rooted a couple of years ago and never updated any further. It's currently running 4.4.4 / NK2 and I've been looking at upgrading to a Lollipop build. I have the Toshiba 11x eMMC so it doesn't sound like Marshmallow is an option if I want to keep root. I've spent significant time rooting through the forums and I can't seem to find a method to update my phone from KitKat to Lollipop (while keeping root) that is current, has the necessary files available to download, and works. Using FlashFire and G900V_OE1_Stock_Rooted_ROM.zip followed by Odin and an OD5 bootloader is failing on my phone for whatever reason. The other methods, including muniz_ri's, don't seem to have current files available for download.
I've fried my brain searching with no success. If anyone could point me to current directions/files to upgrade from KitKat to a solid Lollipop build while maintaining my root access, it would be GREATLY appreciated.
Thank you.
I would Odin this file https://www.androidfilehost.com/?fid=24438995911970571
That will take you to stock PB1 then follow this guide to get root https://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
Then I would use flash fire or LP safe strap to flash a ROM I recommended
https://forum.xda-developers.com/ve...ang5litre-edition-5-0-pb1-devnon-dev-t3381850 or https://forum.xda-developers.com/ve...enix-rom-9-0-ported-g900v-ported-rom-t3188443
OrneryTX said:
I have a Verizon Galaxy S5 (G900V) that I rooted a couple of years ago and never updated any further. It's currently running 4.4.4 / NK2 and I've been looking at upgrading to a Lollipop build. I have the Toshiba 11x eMMC so it doesn't sound like Marshmallow is an option if I want to keep root. I've spent significant time rooting through the forums and I can't seem to find a method to update my phone from KitKat to Lollipop (while keeping root) that is current, has the necessary files available to download, and works. Using FlashFire and G900V_OE1_Stock_Rooted_ROM.zip followed by Odin and an OD5 bootloader is failing on my phone for whatever reason. The other methods, including muniz_ri's, don't seem to have current files available for download.
I've fried my brain searching with no success. If anyone could point me to current directions/files to upgrade from KitKat to a solid Lollipop build while maintaining my root access, it would be GREATLY appreciated.
Thank you.
Click to expand...
Click to collapse
You have root so just skip the rooting part everything you need is here to https://forum.xda-developers.com/showpost.php?p=71202995&postcount=3
jrkruse said:
You have root so just skip the rooting part everything you need is here to https://forum.xda-developers.com/showpost.php?p=71202995&postcount=3
Click to expand...
Click to collapse
So if I'm reading that correctly, I can skip to step #9 of the "Directions For Users With CID 11' Toshiba eMMC" section and then use the EMMC_11_PB1_5_0_1_LL_Firmware_Bootloader.zip and VZW_BPB1_ODEX_DEODEX_V9.zip files. Is that correct?
OrneryTX said:
So if I'm reading that correctly, I can skip to step #9 of the "Directions For Users With CID 11' Toshiba eMMC" section and then use the EMMC_11_PB1_5_0_1_LL_Firmware_Bootloader.zip and VZW_BPB1_ODEX_DEODEX_V9.zip files. Is that correct?
Click to expand...
Click to collapse
Yes. You must have safestrap and use it to flash EMMC_11_PB1_5_0_1_LL_Firmware_Bootloader.zip and rom
jrkruse said:
Yes. You must have safestrap and use it to flash EMMC_11_PB1_5_0_1_LL_Firmware_Bootloader.zip and rom
Click to expand...
Click to collapse
Success! Now on 5.0 and PB1 with no significant issues during or after the upgrade.
Many thanks!
jrkruse said:
Yes. You must have safestrap and use it to flash EMMC_11_PB1_5_0_1_LL_Firmware_Bootloader.zip and rom
Click to expand...
Click to collapse
Let me add a caveat to that success story. I do notice that I don't have the Safestrap recovery option during the boot up process and it looks like this is expected behavior for Lollipop. The "Reboot to Recovery" option with the app is also not active or functional. What's the best way to get back the full Safestrap functionality? I found the below thread of yours but I'm not sure if the files and instructions are current. Thoughts?
https://forum.xda-developers.com/verizon-galaxy-s5/development/safestrap-5-0-lollipop-t3313800
jrkruse said:
Yes. You must have safestrap and use it to flash EMMC_11_PB1_5_0_1_LL_Firmware_Bootloader.zip and rom
Click to expand...
Click to collapse
OrneryTX said:
Let me add a caveat to that success story. I do notice that I don't have the Safestrap recovery option during the boot up process and it looks like this is expected behavior for Lollipop. The "Reboot to Recovery" option with the app is also not active or functional. What's the best way to get back the full Safestrap functionality? I found the below thread of yours but I'm not sure if the files and instructions are current. Thoughts?
https://forum.xda-developers.com/verizon-galaxy-s5/development/safestrap-5-0-lollipop-t3313800
Click to expand...
Click to collapse
I think I see where I went wrong with Safestrap but it's going to be a little while before I can investigate further. Don't want to brick my phone at work and not be able to phone home.
I'll update after I do some more troubleshooting.
Thanks again.