Ostensibly, srsroot supports rooting SM-T337V build KTU84P.T337VVRU2ANK1 Android version 4.4.4. It actually doesn't, and it doesn't appear that any other exploit exists. My business needs this. I'm not sure if this is right place to post, but we can definitely offer a bounty if this exploit does not yet exist.
Meditato said:
Ostensibly, srsroot supports rooting SM-T337V build KTU84P.T337VVRU2ANK1 Android version 4.4.4. It actually doesn't, and it doesn't appear that any other exploit exists. My business needs this. I'm not sure if this is right place to post, but we can definitely offer a bounty if this exploit does not yet exist.
Click to expand...
Click to collapse
Sorry just to eliminate the obvious, have you tried towelroot, and if that doesn't work, have you tried the newer method of flashing a kernel from an older build, rooting with towelroot, and flashing the latest kernel?
I've tried Towelroot- it does not support this update.
ODINing an old image over a new one is generally a bad idea- on Samsung devices, it has a nasty tendency of disabling the network devices.
Sent from my Nexus 5 using XDA Free mobile app
Meditato said:
I've tried Towelroot- it does not support this update.
ODINing an old image over a new one is generally a bad idea- on Samsung devices, it has a nasty tendency of disabling the network devices.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Not an entire firmware image, just a .tar of an older kernel, that's how I rooted my Galaxy S4 Active and my Tab 4 SM-T530NU
thisisapoorusernamechoice said:
Not an entire firmware image, just a .tar of an older kernel, that's how I rooted my Galaxy S4 Active and my Tab 4 SM-T530NU
Click to expand...
Click to collapse
Do you know of any links of this for the SM-T337V? Also, are you sure that the exploits in towelroot, srsroot, cfroot, etc are just kernel exploits and not dependent on other utilities or parts of the userspace? We just tried to flash the 4.4.2 kernel back over the 4.4.4 update and ended up almost bricking a test tablet.
To be clear, our tablets are already the latest update, so we have to find some way of rooting them that doesn't involve just rooting the previous version and then just never updating it.
Meditato said:
Do you know of any links of this for the SM-T337V? Also, are you sure that the exploits in towelroot, srsroot, cfroot, etc are just kernel exploits and not dependent on other utilities or parts of the userspace? We just tried to flash the 4.4.2 kernel back over the 4.4.4 update and ended up almost bricking a test tablet.
To be clear, our tablets are already the latest update, so we have to find some way of rooting them that doesn't involve just rooting the previous version and then just never updating it.
Click to expand...
Click to collapse
OK I don't think you see what I'm getting at. I understand you don't want to do a wholesale downgrade to a previous version, I get that. But the exploit in towelroot works on the older version's kernel. So, correct me if I'm wrong, but the kernel file is simply boot.img inside the tar.md5 file, which you can open as an archive in winrar or 7zip. So what I'm suggesting, and someone correct me if I'm wrong, but I'm pretty sure this is what they're doing to root the Tab 4 10.1, Galaxy S4, and Galaxy S5. So while on the latest SM-T337V firmware, extract the boot.img from the older firmware, create a tar just for the boot.img (may or may not need linux or at least cygwin to do that, honestly don't know for sure), flash that older kernel tar in Odin, quickly root your tablet with towelroot, then flash the current kernel. Sorry but I'm not sure if you want to install SuperSU before or after that last step.
But that's how the latest Samsung builds are being rooted
deleted
thisisapoorusernamechoice said:
OK I don't think you see what I'm getting at. I understand you don't want to do a wholesale downgrade to a previous version, I get that. But the exploit in towelroot works on the older version's kernel. So, correct me if I'm wrong, but the kernel file is simply boot.img inside the tar.md5 file, which you can open as an archive in winrar or 7zip. So what I'm suggesting, and someone correct me if I'm wrong, but I'm pretty sure this is what they're doing to root the Tab 4 10.1, Galaxy S4, and Galaxy S5. So while on the latest SM-T337V firmware, extract the boot.img from the older firmware, create a tar just for the boot.img (may or may not need linux or at least cygwin to do that, honestly don't know for sure), flash that older kernel tar in Odin, quickly root your tablet with towelroot, then flash the current kernel. Sorry but I'm not sure if you want to install SuperSU before or after that last step.
But that's how the latest Samsung builds are being rooted
Click to expand...
Click to collapse
We've tried this. As stated in the other thread about this OTA update, this doesn't appear to work. In our case, ODIN failed with _xmitdata error. Not even flashing the new kernel works.
Whelp, with the bootloader locked, downgrading not working, and Verizon/Samsung unwilling to help, it looks like we're SOL.
How to t337 rom install on t332?
Meditato said:
Whelp, with the bootloader locked, downgrading not working, and Verizon/Samsung unwilling to help, it looks like we're SOL.
Click to expand...
Click to collapse
I'm in the same boat as you but with the TM-537V. Also tried the downgrade kernel, towelroot, upgrade method and it failed. Are you still looking or have you given up on this?
any news?
any update on this? anyone figure out how to root the sm-t337v 4.4.4???
Meditato said:
Whelp, with the bootloader locked, downgrading not working, and Verizon/Samsung unwilling to help, it looks like we're SOL.
Click to expand...
Click to collapse
M,
are you still looking into this ? do you have or can you post/link the current bootimg in question ?
if so do you posess a tab that can be used as a guinea-pig?
I am trying to sort out an approach to a recovery for the sm-t337a and maybe tinkering with this might get
some answers to both problems at the same time.
thanks.
m
what i am thinking, ketut's degas bootimg tools seem to work unpacking and repacking a signed stock bootimg for the sm-t23xx without modification, from what i can get the signatures relates to sizes of portions of the bootimg. I have a thought that some combination of modifying the
img in question and changing compression, or just managing to change that i byte that makes secure=1 secure=0 might be a start
but need someone who can and is willing to experiment.
recovery.img too if you could.
also run in terminal [no need for root] the following
ls /proc/config.gz
i just want to see if it's there
my last thought is, if you have a device to "throw away" is to try flat out over-writing the locked bootloader with one that isn't?
evrkusd said:
I'm in the same boat as you but with the TM-537V. Also tried the downgrade kernel, towelroot, upgrade method and it failed. Are you still looking or have you given up on this?
Click to expand...
Click to collapse
Hi , now @sub77 upload new TWRP 2860 for all models , including T537V too . You may try to install it and in the success case , you may try to install superSU from recovery . Goodluck
repey6 said:
Hi , now @sub77 upload new TWRP 2860 for all models , including T537V too . You may try to install it and in the success case , you may try to install superSU from recovery . Goodluck
Click to expand...
Click to collapse
Thanks. I'm not sure if it's tested for 537V though! Did you see anyone saying that they used it for 537V or that the new version supports 537V?
evrkusd said:
Thanks. I'm not sure if it's tested for 537V though! Did you see anyone saying that they used it for 537V or that the new version supports 537V?
Click to expand...
Click to collapse
No , of course . It's new .
repey6 said:
No , of course . It's new .
Click to expand...
Click to collapse
I just tried flashing TWRP 2.8.6.0 to my SM-T537V with Odin and it failed
uroboch said:
I just tried flashing TWRP 2.8.6.0 to my SM-T537V with Odin and it failed
Click to expand...
Click to collapse
Did you try using the flashify app to install the TWRP img file? That's how I've been installing TWRP to my Tab 4
thisisapoorusernamechoice said:
Did you try using the flashify app to install the TWRP img file? That's how I've been installing TWRP to my Tab 4
Click to expand...
Click to collapse
I did not. I will give it a shot and let you know the outcome. I wont be able to use it as it requires root.
thisisapoorusernamechoice said:
Did you try using the flashify app to install the TWRP img file? That's how I've been installing TWRP to my Tab 4
Click to expand...
Click to collapse
Were you able to do this on an LTE Tab 4? or which one?
Related
I have an SM-G900A with a build date of July 22, 2014. Geohot's Towelroot won't work on it. I keep looking for information on rooting this phone, but they all go back to Towelroot or CF-Auto-Root. Chainfire's Auto-Root page doesn't list a file for the SM-G900A. What can I do to get this phone rooted? Is there someone at the AT&T store who can help?
You can downgrade your kernel temporarily, root via towelroot and upgrade your kernel again -> rooted S5. See here.
aregvadfbg said:
You can downgrade your kernel temporarily, root via towelroot and upgrade your kernel again -> rooted S5. See here.
Click to expand...
Click to collapse
Which is the correct firmware to use? This one? http://www.sammobile.com/firmwares/1/?model=SM-G900A&pcode=0#firmware
dgriffi said:
Which is the correct firmware to use? This one? http://www.sammobile.com/firmwares/1/?model=SM-G900A&pcode=0#firmware
Click to expand...
Click to collapse
I can't say for sure for this model, but here someone says the G900AUCU1ANCE 4.4.2 stock firmware can be towelrooted.
He suggests that you downgrade the comlete firmware, not only the kernel. This may be easier because a .tar.md5-file with only the kernel might be hard to find, i only found those for the g900f. After rooting with towelroot you might be able to update to the current firmware via Mobile Odin PRO and keep root, if you can find a version of your current firmware that can be flashed with MOP. I'm not sure about that though, you have to find out yourself, i have only downgraded and re-upgraded the kernel.
aregvadfbg said:
I can't say for sure for this model, but here someone says the G900AUCU1ANCE 4.4.2 stock firmware can be towelrooted.
He suggests that you downgrade the comlete firmware, not only the kernel. This may be easier because a .tar.md5-file with only the kernel might be hard to find, i only found those for the g900f. After rooting with towelroot you might be able to update to the current firmware via Mobile Odin PRO and keep root, if you can find a version of your current firmware that can be flashed with MOP. I'm not sure about that though, you have to find out yourself, i have only downgraded and re-upgraded the kernel.
Click to expand...
Click to collapse
I fiddled with Jodin and failed. Then I dug out an old laptop, put Windows 7 on it, and tried out regular Odin for a bit. For some reason, feeding it the regular .tar.md5 file I get from sammobile.com or samsung-updates.com wouldn't work. I kept getting complaints of "W Rev Check Fail [aboot] fused 2 >Binary 1". The solution was to feed Odin the files individually. Ultimately I followed this: http://forum.xda-developers.com/showthread.php?t=2785363. My SM-G900A is now rooted.
dgriffi said:
I fiddled with Jodin and failed. Then I dug out an old laptop, put Windows 7 on it, and tried out regular Odin for a bit. For some reason, feeding it the regular .tar.md5 file I get from sammobile.com or samsung-updates.com wouldn't work. I kept getting complaints of "W Rev Check Fail [aboot] fused 2 >Binary 1". The solution was to feed Odin the files individually. Ultimately I followed this: http://forum.xda-developers.com/showthread.php?t=2785363. My SM-G900A is now rooted.
Click to expand...
Click to collapse
Nice, thanks for sharing your solution! Which rooting method did work for you?
aregvadfbg said:
Nice, thanks for sharing your solution! Which rooting method did work for you?
Click to expand...
Click to collapse
I followed the referenced directions exactly and then used Towelroot. In retrospect, that was too much. I wound up erasing everything I did with the phone. I should have followed this instead: http://forum.xda-developers.com/att-galaxy-s5/general/g900and3tong3keeprootota-zip-t2862299. I picked up on that one with item 6 to close the hole that Towelroot exploited. I hope that will prevent an OTA from being pushed at me. Another good thing about the latter method, I think it's easily doable with Heimdall.
Nice link!
dgriffi said:
I followed the referenced directions exactly and then used Towelroot. In retrospect, that was too much. I wound up erasing everything I did with the phone. I should have followed this instead: http://forum.xda-developers.com/att-galaxy-s5/general/g900and3tong3keeprootota-zip-t2862299. I picked up on that one with item 6 to close the hole that Towelroot exploited. I hope that will prevent an OTA from being pushed at me. Another good thing about the latter method, I think it's easily doable with Heimdall.
Click to expand...
Click to collapse
At least one problem has cropped up: Wifi passwords are not saved. I flashed it with the ND3 stock kernel and now it's saving passwords again. I don't know what the problem is.
Diagnosis: brainfart
With my phone flashed with the ND3 stock kernel, I allowed the phone to take the OTA update. This put my phone back into the state it was when I walked out of the AT&T store with it. THEN I followed http://forum.xda-developers.com/att-galaxy-s5/general/g900and3tong3keeprootota-zip-t2862299 from beginning to end. Now I have a rooted phone, Towelroot hole patched, and Wifi passwords retained.
Lol
"Is there someone at the ATT store that can help"
Laughing my ass off right now.
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.
On Vodafone UK got the following OTA about 131MB (G925FXXU1AODG), checked Sammobile also posted there, but also branded Vodafone.
Not noticed any difference.
According to gsmarena there ia a noticeable improvement to the phone's performance (at least for S6)
www.gsmarena.com/samsung_galaxy_s6_is_receiving_a_new_502_ota_in_europe-news-12195.php
night clock fix by any chance?
So far cannot discern any changes - will play around more and see.
Can someone make sure the kernel build date is before 3th May?
Otherwise I'd not install this update if you want to root without tripping knox.
According to the S6 Forum the new root method only works for sure with kernels before 3th May.
whitepaw said:
Can someone make sure the kernel build date is before 3th May?
Otherwise I'd not install this update if you want to root without tripping knox.
According to the S6 Forum the new root method only works for sure with kernels before 3th May.
Click to expand...
Click to collapse
According to this http://www.android-hilfe.de/origina...ock-rom-22-04-15-g925fxxu1aodg-5-0-2-vd2.html build date is Apr 22
whitepaw said:
Can someone make sure the kernel build date is before 3th May?
Otherwise I'd not install this update if you want to root without tripping knox.
According to the S6 Forum the new root method only works for sure with kernels before 3th May.
Click to expand...
Click to collapse
...so you want ever use old software..?
freaksamael said:
According to this http://www.android-hilfe.de/origina...ock-rom-22-04-15-g925fxxu1aodg-5-0-2-vd2.html build date is Apr 22
Click to expand...
Click to collapse
Thank you. Then it should be save to install.
Alex-V said:
...so you want ever use old software..?
Click to expand...
Click to collapse
No. Once you got root you can flash custom Roms and then you can even update the Kernel (maybe...might not be needed so). Only for rooting the unsafe kernel is needed.
There might be the possibility to downgrade without tripping knox via Odin but I'm not quiet sure.
whitepaw said:
Thank you. Then it should be save to install.
No. Once you got root you can flash custom Roms and then you can even update the Kernel (maybe...might not be needed so). Only for rooting the unsafe kernel is needed.
There might be the possibility to downgrade without tripping knox via Odin but I'm not quiet sure.
Click to expand...
Click to collapse
OK..for the not tripping Knox..you have some info..? thanks
Alex-V said:
OK..for the not tripping Knox..you have some info..? thanks
Click to expand...
Click to collapse
You mean rooting without tripping knox?
http://forum.xda-developers.com/galaxy-s6/general/root-pingpongroot-s6-root-tool-t3103016
They are working on a s6e version and in the thread he says it should work with all kernel before may 3. You won't be able to flash a recovery but on the s5 it was possible with mobile odin to flash custom Roms without tripping knox. I assume it's the same for the s6.
Downgrade without tripping knox should be possible with official firmwares via odin. It worked for me on the s5. Not sure about the s6. That's why I wanted to make sure the kernel is still exploitable.
whitepaw said:
You mean rooting without tripping knox?
http://forum.xda-developers.com/galaxy-s6/general/root-pingpongroot-s6-root-tool-t3103016
They are working on a s6e version and in the thread he says it should work with all kernel before may 3. You won't be able to flash a recovery but on the s5 it was possible with mobile odin to flash custom Roms without tripping knox. I assume it's the same for the s6.
Downgrade without tripping knox should be possible with official firmwares via odin. It worked for me on the s5. Not sure about the s6. That's why I wanted to make sure the kernel is still exploitable.
Click to expand...
Click to collapse
thanks man ? sounds promising
Heads up for anyone attempting to flash it on another version.
Attempted to flash the Vodafone 925F(ODG) version on my W8. System only. No boot/radio/csc. The version boots fine even on older kernels, no fc's even without a data wipe. Sadly no in-call audio on W8 and it will be the same for TMO people as well.
For others with any 925F, you should be able to download the full image from SamMobile and then extract the system.img and boot.img. Convert them to ODIN flashable packages and then flash the tar files individually with AP mode in ODIN to upgrade. If you're using TWRP, you can then boot in and flash SuperSU and gain root back. Unsure when kernel sources would be released for the update.
The Vodafone image had 0 bloat on first boot so it should be the same for others.
Edit*
Please make a backup still to be safe. Also have a full flashable image ready incase flashing goes bad.
evonc said:
Heads up for anyone attempting to flash it on another version.
Attempted to flash the Vodafone 925F(ODG) version on my W8. System only. No boot/radio/csc. The version boots fine even on older kernels, no fc's even without a data wipe. Sadly no in-call audio on W8 and it will be the same for TMO people as well.
For others with any 925F, you should be able to download the full image from SamMobile and then extract the system.img and boot.img. Convert them to ODIN flashable packages and then flash the tar files individually with AP mode in ODIN to upgrade. If you're using TWRP, you can then boot in and flash SuperSU and gain root back. Unsure when kernel sources would be released for the update.
The Vodafone image had 0 bloat on first boot so it should be the same for others.
Edit*
Please make a backup still to be safe. Also have a full flashable image ready incase flashing goes bad.
Click to expand...
Click to collapse
I will try that..thanks my friend..
I still have my normal firmware download so I'm save.. lol..
evonc said:
Heads up for anyone attempting to flash it on another version.
Attempted to flash the Vodafone 925F(ODG) version on my W8. System only. No boot/radio/csc. The version boots fine even on older kernels, no fc's even without a data wipe. Sadly no in-call audio on W8 and it will be the same for TMO people as well.
For others with any 925F, you should be able to download the full image from SamMobile and then extract the system.img and boot.img. Convert them to ODIN flashable packages and then flash the tar files individually with AP mode in ODIN to upgrade. If you're using TWRP, you can then boot in and flash SuperSU and gain root back. Unsure when kernel sources would be released for the update.
The Vodafone image had 0 bloat on first boot so it should be the same for others.
Edit*
Please make a backup still to be safe. Also have a full flashable image ready incase flashing goes bad.
Click to expand...
Click to collapse
Please what do you mean by individual?
Also after flashing, will it trigger knox?
Do i need to be rooted to flash?
I have already combine both file and used tar package to make it flashable with odin
okolobaccess said:
Please what do you mean by individual?
I have already combine both file and used tar package to make it flashable with odin
Click to expand...
Click to collapse
I'm still download the firmware..lol..and works..?
okolobaccess said:
Please what do you mean by individual?
Also after flashing, will it trigger knox?
Do i need to be rooted to flash?
I have already combine both file and used tar package to make it flashable with odin
Click to expand...
Click to collapse
Take the ODG zip and create an Odin flashable tar package of only System.img and boot.img.
Once an image comes out for your carrier, you can update bootloader/radio if you choose.
Not sure if it will trigger KNOX. If you're worried about that, stick to OTA update from your carrier. You do not need to be rooted to flash an ODIN tar.
Alex-V said:
I'm still download the firmware..lol..and works..?
Click to expand...
Click to collapse
Yes it works.
---------- Post added at 09:53 PM ---------- Previous post was at 09:48 PM ----------
evonc said:
Take the ODG zip and create an Odin flashable tar package of only System.img and boot.img.
Once an image comes out for your carrier, you can update bootloader/radio if you choose.
Not sure if it will trigger KNOX. If you're worried about that, stick to OTA update from your carrier. You do not need to be rooted to flash an ODIN tar.
Click to expand...
Click to collapse
Thanks,
Knox didnt trigger
okolobaccess said:
Yes it works.
---------- Post added at 09:53 PM ---------- Previous post was at 09:48 PM ----------
Thanks,
Knox didnt trigger
Click to expand...
Click to collapse
yes..also on it now..works fine.
Alex-V said:
yes..also on it now..works fine.
Click to expand...
Click to collapse
have observed any changes yet
okolobaccess said:
have observed any changes yet
Click to expand...
Click to collapse
its much more stable..and noticeable faster..but still i have the night clock problem....
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've spent hours searching and I know this is an old phone. Is ther anyway to root the Lollipop and download Jelly Bean (custom or stock) to it? I'm not worried about Warranties. I'm not exactly a newb and I don't like Lollipop at all. I don't mind KitKat, but what I hate is the front facing camera can't be flipped. Dumbest thing ever.
http://forum.xda-developers.com/galaxy-s4-sprint
Search for CF-Autoroot.
Strephon Alkhalikoi said:
http://forum.xda-developers.com/galaxy-s4-sprint
Search for CF-Autoroot.
Click to expand...
Click to collapse
I'm supposedly rooted. I used KingRoot and then switched over yo SuperSU. But I can't seem to get the Rom's to install. This is where I'm probably going wrong. I'm assuming it has to do with the Bootloader.
BikerSk8rKid said:
I'm supposedly rooted. I used KingRoot and then switched over yo SuperSU. But I can't seem to get the Rom's to install. This is where I'm probably going wrong. I'm assuming it has to do with the Bootloader.
Click to expand...
Click to collapse
Ask the right questions if you want the right answer.
You said you're not a newb. So what exactly was the procedure used to to install those ROMs?
Well, you should be using CF-Autoroot, as it's the recommended method to root these devices. That said, unless you have a frankenphone, only AT&T and Verizon models have locked bootloaders. Enter download mode and verify your device's model number please?
GDReaper said:
Ask the right questions if you want the right answer.
You said you're not a newb. So what exactly was the procedure used to to install those ROMs?
Click to expand...
Click to collapse
I was half asleep and stressed out when I posted this. It's been a couple weeks or longer since I messed with the phone. Damn forums weren't resetting my password. When I mean I'm not a newb I mean I'm not like brand new to this and I know how to research. I guess you could say I'm not THAT stupid. haha
I'mma have to try this again and figure out what path's I kept trying. I'm so spaced out I can't remember hard any of it. Just that I tried to flash a stock and rooted rom with old odin and new odin. Spent 2 days straight messing with it and trying to get around it. But I kept getting blocked. I didn't come across CF-Autoroot. So I'll try that.
Strephon Alkhalikoi said:
Well, you should be using CF-Autoroot, as it's the recommended method to root these devices. That said, unless you have a frankenphone, only AT&T and Verizon models have locked bootloaders. Enter download mode and verify your device's model number please?
Click to expand...
Click to collapse
Of all the researching I've done (I couldn't login) that one never showed up in my searchs. haha I'll have to give that one a try. It's been a couple weeks or longer. SPH-L720. I had a few Tri-Bands, but it seemed those were limited compared to the standard model.
Update: I went the CF-AutoRoot route and then tried to use Odin to flash stock mk2 rom. Now that I remember it kept failing everytime and then it would corrupt the current rom. I also tried using TWRP and couldn't get it to work properly.
That's a Sprint device, so your bootloader is unlocked.
Here's something you should note: If you want to flash a ROM, of any kind, you don't necessarily have to be rooted.
Stock ROMs require Odin and custom ROMs require a custom recovery. None of them require root.
Your flash to an older version fails most probably due to the fact that you're trying to downgrade the bootloader (Any stock ROM flash also modifies the bootloader and modem partitions).
But your windows, cable, USB port and windows can also be at fault here.
GDReaper said:
That's a Sprint device, so your bootloader is unlocked.
Here's something you should note: If you want to flash a ROM, of any kind, you don't necessarily have to be rooted.
Stock ROMs require Odin and custom ROMs require a custom recovery. None of them require root.
Your flash to an older version fails most probably due to the fact that you're trying to downgrade the bootloader (Any stock ROM flash also modifies the bootloader and modem partitions).
But your windows, cable, USB port and windows can also be at fault here.
Click to expand...
Click to collapse
For some reason I kept reading that it was locked or thinking it was locked because of not being able to downgrade.
So that's what I thought and I guess that's what I was trying to get at in my first post. Trying to go from Lollipop 5 to Jelly Bean 4.3 or so. Is it possible to do that whether it's custom or not?
I just hate the Lollipop and the KitKat. My Galaxy S2 had the JB and Power Button took a crap. So I ended up getting a S3 and now been sitting on an S4.
I know it's not the cable or at least it shouldn't be because it works to flash the stock current rom everytime I corrupt it. The computer is like brand new and running Windows 8.1
BikerSk8rKid said:
For some reason I kept reading that it was locked or thinking it was locked because of not being able to downgrade.
So that's what I thought and I guess that's what I was trying to get at in my first post. Trying to go from Lollipop 5 to Jelly Bean 4.3 or so. Is it possible to do that whether it's custom or not?
I just hate the Lollipop and the KitKat. My Galaxy S2 had the JB and Power Button took a crap. So I ended up getting a S3 and now been sitting on an S4.
I know it's not the cable or at least it shouldn't be because it works to flash the stock current rom everytime I corrupt it. The computer is like brand new and running Windows 8.1
Click to expand...
Click to collapse
Downgrading sometimes succeeds. There are also guides on how to downgrade, though there aren't any special procedures. Maybe the bootloader version of the firmware-to-be-flashed matters.
With custom ROMs it's definitely possible, as they do not change the bootloader.
GDReaper said:
Downgrading sometimes succeeds. There are also guides on how to downgrade, though there aren't any special procedures. Maybe the bootloader version of the firmware-to-be-flashed matters.
With custom ROMs it's definitely possible, as they do not change the bootloader.
Click to expand...
Click to collapse
I guess I'm more of a newb with this than I expected. :/ It's been years since I've been on the forums or even tinkered with phones. HTC Touch Pro 2 was the last one I believe. haha
So... With that being said. Custom Roms are typically to the current stock rom, correct? or is it possible to get a Custom Jelly Bean and flash/overwrite it to the Lollipop/current? Since I just tripped wit the Knox Warranty with the CF-AutoRoot. LoL
BikerSk8rKid said:
I guess I'm more of a newb with this than I expected. :/ It's been years since I've been on the forums or even tinkered with phones. HTC Touch Pro 2 was the last one I believe. haha
So... With that being said. Custom Roms are typically to the current stock rom, correct? or is it possible to get a Custom Jelly Bean and flash/overwrite it to the Lollipop/current? Since I just tripped wit the Knox Warranty with the CF-AutoRoot. LoL
Click to expand...
Click to collapse
If you can find some viable download links, then yes, you should be able to flash custom jelly bean ROMs. But you need a custom recovery in order to do that.
The recovery can be flashed with Odin. Or, since you're rooted, you can also flash a recovery by using an app called Flashify.
Odin requires a .tar file and Flashify requires a .img file.
Oh, and you also need the gapps package for the Google Apps. You need a package for that specific android version, so it should be jelly bean gapps.
GDReaper said:
If you can find some viable download links, then yes, you should be able to flash custom jelly bean ROMs. But you need a custom recovery in order to do that.
The recovery can be flashed with Odin. Or, since you're rooted, you can also flash a recovery by using an app called Flashify.
Odin requires a .tar file and Flashify requires a .img file.
Oh, and you also need the gapps package for the Google Apps. You need a package for that specific android version, so it should be jelly bean gapps.
Click to expand...
Click to collapse
I'll look into that and give it a shot. Thank you! I knew it wasn't THAT easy. LOL