Database Users

[Q] Safe Build for Root on SM-N900V

I'm looking to root my Note 3, and I'm curious what the safe guidelines are, I can't seem to find a definitive answer on this.
There was the OTA yesterday (maybe it was on the 6th) that went out.
If that is installed, can you still root at this current point in time?
My current details are as follows:
Model: SM-N900V
Build: JSS15J.N900VVRUBMJ7
Am I SoL?
Thanks for the help.
NOTE: I tried searching , but it seems the search function is temporarily unavailable :crying:

crizznaig said:
There was the OTA yesterday (maybe it was on the 6th) that went out.
If that is installed, can you still root at this current point in time?
Click to expand...
Click to collapse
Yes, you can either use the Kingo root tool or wait until "Root de la Vega" gets a fix.
Personally, I would wait instead of using Kingo: there is some privacy concerns with using Kingo since we don't actually know how/what it does.
DroidModderX said:
The verdict is still out as to whether Kingo App is anything other than a malicious virus ridden software, or an innocent one click root method for many devices. If you do decide to use this app you should do so at your own risk. This root method is completely close sourced so we aren't sure of everything contained with in it. If this bothers you then steer clear. If you don't mind your data potentially being at risk this method is a one click method that works for a long list of devices. It has been confirmed via an XDA thread that this method will work with the Verizon Galaxy Note 3 after the latest OTA update.
Click to expand...
Click to collapse

Yeah I've read the recent situations with Kingo and Vroot as well. I'm cool with waiting, I'd prefer to not have my IMEI data mined for root
I've waited thus far.
So basically I should be following developments on the Root de la Vega stuff.
Appreciate the response

Yeah I've read the recent situations with Kingo and Vroot as well. I'm cool with waiting, I'd prefer to not have my IMEI data mined for root
I've waited thus far.
So basically I should be following developments on the Root de la Vega stuff.
Appreciate the response

Bricked
bummer, i didnt see this yesterday, and i am now bricked and looking to restore somehow back to factory via odin or whatever

crizznaig said:
I'm looking to root my Note 3, and I'm curious what the safe guidelines are, I can't seem to find a definitive answer on this.
There was the OTA yesterday (maybe it was on the 6th) that went out.
If that is installed, can you still root at this current point in time?
My current details are as follows:
Model: SM-N900V
Build: JSS15J.N900VVRUBMJ7
Am I SoL?
Thanks for the help.
NOTE: I tried searching , but it seems the search function is temporarily unavailable :crying:
Click to expand...
Click to collapse
Try this: http://forum.xda-developers.com/showthread.php?t=2498850

I also just received my Note3 with that build number. Any update yet on root?

lieutenantglorp said:
I also just received my Note3 with that build number. Any update yet on root?
Click to expand...
Click to collapse
I have MJ7 and used Kingo
http://forum.xda-developers.com/showthread.php?t=2521581

Kingo Can't Connect
I have just tested Kingo with a Note 3 Verizon (N900V Firmware MJ7) and can't connect.
Thing is, I can see it find in ADB and I can issue commands via ADB. Of course USB debugging is enabled and working fine through ADB.
I'm running the latest version of Kingo 1.1.2.1770, and it just reads "Connecting service" in the bottom-right and the big "Not Connected" in the middle.
I've also attempted to connect my G-III phone which I access via ADB with no problem, and Kingo doesn't see that either.
This is my first test with a one-click root solution. I haven't found any instructions for rooting the N900V any other way (eg directly via command line) .. Anyone have any idea what I could be doing wrong, or how to root the N900V running MJ7 without Kingo?
Thank you in advance
RKM

I would assume you can use odin with stock original firmware and pit file to downgrade your phone from MJ7, use de la vega, use supersu+ "preserve superuser" functionality, then OTA update. Using supersu+/preserve option/OTA/re-enable is how I updated and kept root.

I'd be willing to bet it's your anti-virus or firewall software and that you are doing this on either Win 7 or Win 8.
Sent from my SM-N900V using Tapatalk

Also, having just read up on the latest Kingo stuff, just use it. It's fine. The latest versions don't send your IMEI. I'd still use it if they did, personally. IMEI+serials are sent around all the time when you buy/sell phones online since you need to confirm clean IMEI before paying to be sure the phone hasn't been reported stolen. Nothing bad to worry about. It's your phone, if someone could possibly do anything weird, Verizon would swap you a new one.

bigillz said:
I would assume you can use odin with stock original firmware and pit file to downgrade your phone from MJ7, use de la vega, use supersu+ "preserve superuser" functionality, then OTA update. Using supersu+/preserve option/OTA/re-enable is how I updated and kept root.
Click to expand...
Click to collapse
Doing this will soft brick your device. You cannot go back to MI9 if you are already on MJ7. Do not try to flash back to stock MI9 if you are already on MJ7.
HAZA12D_HYPERDRIVE_NOTE3

haza12d said:
Doing this will soft brick your device. You cannot go back to MI9 if you are already on MJ7. Do not try to flash back to stock MI9 if you are already on MJ7.
HAZA12D_HYPERDRIVE_NOTE3
Click to expand...
Click to collapse
Even with the proper pit file? I was under the impression the people who were soft bricking were flashing just the rom in odin, no pit. I saw another thread where people where un-bricking by flashing the pit file in the process.

bigillz said:
Even with the proper pit file? I was under the impression the people who were soft bricking were flashing just the rom in odin, no pit. I saw another thread where people where un-bricking by flashing the pit file in the process.
Click to expand...
Click to collapse
Not positive, but I think they were having to use the pit file with MJ7 after they had tried MI9. Just flashing MJ7 wouldn't work. I've been wrong before though.

G8orDroid said:
Not positive, but I think they were having to use the pit file with MJ7 after they had tried MI9. Just flashing MJ7 wouldn't work. I've been wrong before though.
Click to expand...
Click to collapse
Yes, that's what I've read too.
I'd be willing to bet it's your anti-virus or firewall software and that you are doing this on either Win 7 or Win 8.
Click to expand...
Click to collapse
Unfortunately I don't run any AV software other than the intrinsic Win7, and I had already setup exceptions for the app, disabled, it -- and I've been running Kingo "As Administrator" explicitly in each case.
It just seems so weird that ADB works flawless, and Kingo does not. They're basically the same thing (I believe Kingo is just running everything through ADB, right?)
Ugh .. so I can't downgrade to root, and I can't get Kingo to connect despite it not being related to AV apps and ADB working fine. Leave it to tech to turn a thirty minute project into days!!
Thanks again for any ideas

bigillz said:
Even with the proper pit file? I was under the impression the people who were soft bricking were flashing just the rom in odin, no pit. I saw another thread where people where un-bricking by flashing the pit file in the process.
Click to expand...
Click to collapse
Yes, even with the pit. You cannot go back to MI9 once you update.
HAZA12D_HYPERDRIVE_NOTE3
---------- Post added at 01:50 PM ---------- Previous post was at 01:46 PM ----------
rkmFL said:
Yes, that's what I've read too.
Unfortunately I don't run any AV software other than the intrinsic Win7, and I had already setup exceptions for the app, disabled, it -- and I've been running Kingo "As Administrator" explicitly in each case.
It just seems so weird that ADB works flawless, and Kingo does not. They're basically the same thing (I believe Kingo is just running everything through ADB, right?)
Ugh .. so I can't downgrade to root, and I can't get Kingo to connect despite it not being related to AV apps and ADB working fine. Leave it to tech to turn a thirty minute project into days!!
Thanks again for any ideas
Click to expand...
Click to collapse
Do you have developer options enabled and have USB debugging enabled?
HAZA12D_HYPERDRIVE_NOTE3

haza12d said:
Do you have developer options enabled and have USB debugging enabled?
Click to expand...
Click to collapse
Absolutely, yes.
I mentioned back in the original thread, I have USB debugging enabled and successfully using ADB, which requires this along with the cert approval (required as of Android 4.2 or 4.3, can't remember now).
As a developer, I use ADB on a daily basis and have never had any issue connecting to the phones.
I've re-installed Kingo, etc -- nothing. I can even fire up a command prompt while Kingo is running and send an ADB devices to see my phone successfully connected with the (with the latest Samsung drivers, right from Kingo's site stating the requirement).
Thanks again for the ideas

rkmFL said:
Absolutely, yes.
I mentioned back in the original thread, I have USB debugging enabled and successfully using ADB, which requires this along with the cert approval (required as of Android 4.2 or 4.3, can't remember now).
As a developer, I use ADB on a daily basis and have never had any issue connecting to the phones.
I've re-installed Kingo, etc -- nothing. I can even fire up a command prompt while Kingo is running and send an ADB devices to see my phone successfully connected with the (with the latest Samsung drivers, right from Kingo's site stating the requirement).
Thanks again for the ideas
Click to expand...
Click to collapse
I agree, it doesn't make a lot of sense that Kingo wouldn't connect if you can connect manually thru ADB. I believe it does use ADB to communicate. The software will take a while to run especially on a slow connection, but I am assuming from what you've said that it never gives you a "Device Connected" status, correct?
I mentioned firewall and AV earlier because some of them will block either the app or the communication. I had Trend Micro running on one of the computers I used and it wouldn't connect until I uninstalled it.

[Q] Rooting w/Kingo App Question

Please forgive me if this has been discussed elsewhere. I could not locate it. Anyways, I have the Verizon Samsung Galaxy Note 3 with the latest software...Android 4.3, build MJE. My goal is to hopefully root the device and then install SS to add a ROM. Previously I have the Galaxy S3, which was running a custom ROM. I had no problems with my S3. Since the boot loader of the Note 3 is locked, it's not as easy to do. I keep reading about using Kingo but I'm not sure if it will actually will work with this phone. Has anybody out there successfully rooted their phone with Kingo? Please respond if you have. I have a free day and would love to spend it customizing my phone.
Thanks!

tss01 said:
Has anybody out there successfully rooted their phone with Kingo? Please respond if you have. I have a free day and would love to spend it customizing my phone.
Click to expand...
Click to collapse
Yes. It was really not difficult although it took me a few tries to successfully get SS working. Although Kingo kept saying I was rooted, SS said I was not rooted and it did not have SU access. I just removed SS and SU and un-rooted and tried again. The 3rd time it just worked. In hindsight I think I was having a problem with the cable, that came with the phone, maintaining a USB connection.

Rooting w/Kingo
Hi,
I went ahead to gave it a shot. First I made sure my anti-virus was disabled then I started Kingo and following the onscreen prompts. I automatically downloaded needed drivers. It then told me to re-connect my phone. I did and within a couple of minutes I get "ROOT Failed Not Support". I tried it two more times with the same result.
Any suggestions on my next step cuz I'm out of ideas.
Thanks!

I used it successfully last night, but on MJ7, not MJE.
I didn't read very carefully and had my phone in download/Odin mode.
Kingo recognizes that and attempted exploits against the bootloader - which failed.
So I booted the phone (with ADB / USB debugging on), and Kingo automatically recognized that and succeeded.
Just mentioning in case that's what is going on.

I've used it twice now, most recently about 12 hours ago. Haven't had a problem doing it. Worked first try both times. Normally booted with USB debugging enabled, connected and ran the program. Windows 8.1 laptop. Verizon GN3 fresh odin of MJE and am now rooted with SS installed and running Beans B6 on the stock slot.
Did you get this situated OP? We would love to help get you up and running so you can customize away.

Rooting w/Kingo
There must be some special trick to get Kingo to work properly. I did disable my anti-virus on my computer. I forgot that I have an anti-virus program on my phone as well. Should I disable that also? Is there some special way that I need to install my drivers? I'm really lost right now.
Thanks, for any help.

tss01 said:
There must be some special trick to get Kingo to work properly. I did disable my anti-virus on my computer. I forgot that I have an anti-virus program on my phone as well. Should I disable that also? Is there some special way that I need to install my drivers? I'm really lost right now.
Thanks, for any help.
Click to expand...
Click to collapse
Kingo should install the drivers for you. As far as the anti virus on your phone that could be a problem. I've never tried when I wasn't bare bones stock before I installed anything. Are you adverse to doing a factory reset and trying from scratch, I mean thats what you are doing after you root anyways right?, or are you wanting root to use titanium or whatever to backup everything before you use SafeStrap?
I would reboot everything, disable both Anti-Virus, make sure USB debugging is enabled and run Kingo again. You may have to run as administrator. Keep watching during the process and your phone will prompt you to allow USB debugging for your computer and then it will prompt you again to allow unknown source installs and then after the reboot the phone will prompt one more time for root right to finalize the process.

I was able to root with Kingo on the latest built MJE. It worked for me on the first try. Try another computer if you can.
Does anyone know if there is a way to remove the Custom text with the padlock from the splash screen?
Sent from my SM-N900V using Tapatalk

mexiking713 said:
I was able to root with Kingo on the latest built MJE. It worked for me on the first try. Try another computer if you can.
Does anyone know if there is a way to remove the Custom text with the padlock from the splash screen?
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Use Wanam and check "fake system status" reboot a couple times and it will be gone.

GrandMasterB said:
Use Wanam and check "fake system status" reboot a couple times and it will be gone.
Click to expand...
Click to collapse
I tried that but it didn't work. I rooted while on the official MJE with Kingo. I installed SafeStrap recovery and I'm running CleanRom. It's no big deal but it would be nice to be able to get rid of it.
Sent from my SM-N900V using Tapatalk

Just as a note for people using this method. I tried it it told me it failed but it actually worked. I don't understand the reasoning behind it but all I know is that it worked. Way easier than de LA Vega. Which used to be easy. Lol. I still prefer Odin and CF auto root. But kingo works
Sent from my SM-N900P using xda app-developers app

mexiking713 said:
I tried that but it didn't work. I rooted while on the official MJE with Kingo. I installed SafeStrap recovery and I'm running CleanRom. It's no big deal but it would be nice to be able to get rid of it.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
You made sure to install/activate Xposed framework, then reboot, then activate the Wanam Module and reboot again? Just asking because I've never had it not work for me and I've done it a dozen times or more between the AT&T Galaxy Note 3 and now the Verizon Galaxy Note 3.

GrandMasterB said:
You made sure to install/activate Xposed framework, then reboot, then activate the Wanam Module and reboot again? Just asking because I've never had it not work for me and I've done it a dozen times or more between the AT&T Galaxy Note 3 and now the Verizon Galaxy Note 3.
Click to expand...
Click to collapse
I have other mods running from Wanam right now but that particular one doesn't work. Bummer
Sent from my SM-N900V using Tapatalk

tss01 said:
Hi,
I went ahead to gave it a shot. First I made sure my anti-virus was disabled then I started Kingo and following the onscreen prompts. I automatically downloaded needed drivers. It then told me to re-connect my phone. I did and within a couple of minutes I get "ROOT Failed Not Support". I tried it two more times with the same result.
Any suggestions on my next step cuz I'm out of ideas.
Thanks!
Click to expand...
Click to collapse
If you're still having issues, check the link in my sig. Step by step instructions to get you up and running. Basically fool-proof

MJE TAR File - Question
Hello again:
I'm alittle confused about the need to Oden the MJE Tar file. I am already at MJE (from Verizon) and wonder why I would need to install this? I am Jelly Beans Build 6 installed and it appears to be working just fine. I also have HyperDrive installed and it appears to be working "ok" so far but time will tell. I did have a problem getting my phone to connect to my car via bluetooth but will try this again when I go out this morning.
Thanks!

tss01 said:
Hello again:
I'm alittle confused about the need to Oden the MJE Tar file. I am already at MJE (from Verizon) and wonder why I would need to install this? I am Jelly Beans Build 6 installed and it appears to be working just fine. I also have HyperDrive installed and it appears to be working "ok" so far but time will tell. I did have a problem getting my phone to connect to my car via bluetooth but will try this again when I go out this morning.
Thanks!
Click to expand...
Click to collapse
If you're already running MJE no need to reflash it in Odin. The Odin step isvfor those still on Mi9 or Mj7.
Notorious 3

Rooting Verizon Note3 Help

I've been reading the forum for few hours Friday night and yesterday and found lots of help but and videos but not on how to run this Universal De La Vega script which is where I think I'mscewing it up. I downloaded the N900VVRUBMJE_N900VVZWMJE_N900VVRUBMJE_HOME.tar.md5 from SamMobile. I ran the Universal De La Vega script using Cygwin. After a couple of attempts I figured out to move everything to the c:/ root to reduce typing errors. It produced a file with a Vega in the name as the instructions say, but I not sure I ran the script correctly. More on that in a second. I flashed the NOTE3 with the file using ODin and got a soft brick. I then flashed it with the HOME_tar.md5 I got from SamMobile and the phone rebooted and worked ok, but I'm back to stock and not yet rooted. Happy I downloaded the correct stock file and flashing it save my xss, but I still need to root.
Can I please get a little help on how the De La Vega script is executed.
These are the instructions:
Usage: ./URDLV.sh [full|csc] [stock firmware file path]
Example: ./URDLV.sh csc F:\N900PVPUBMI3_N900PSPTBMI3_SPR.tar.md5
Example: ./URDLV.sh full F:\OneClick_I537UCUBMI2.exe
full = AP and CSC (Creates a single file with both AP and CSC, no bootloaders, modems, etc.)
csc = CSC only
[stock firmware file path] - needs to be the full file path!
Drag and drop the file into the terminal window to get the full path.
I'm having trouble undertanding the second line entry. the ./URDLV.sh full ... where is the OneClick_I537?UCBM12.exe file? When I ran it I just ran the URDLV..sh csc and the URDLV.sh full both on the same N900VVRUBMJE_N900VVZWMJE_N900VVRUBMJE_HOME.tar.md5 from SamMobile. Do I only run one of the two lines on the script? And then set up Odin depending on one or two files?
I trust that this makes sense to someone, I am not Lenix command line savvy...
Thanks in advance!

I rooted my note 3 verizon via Kingo.
Was easy and quick.
Look in the Root via Kingo forum if you want to go a different route~

OneClick_I537?UCBM12.exe ="equal to" grab and drop your N900VVRUBMJE_N900VVZWMJE_N900VVRUBMJE_HOME.tar.md5
but i try it 10+ time not working for me neither....i have the OEM MJE not OTA

tigersfa8 said:
I rooted my note 3 verizon via Kingo.
Was easy and quick.
Look in the Root via Kingo forum if you want to go a different route~
Click to expand...
Click to collapse
Just looked at Kingo looks easy but I'd rather stay with sda if there's a solution. These guys are very trust worthy!

I think I figured it out. Am going to try running the script with [full] only and it generates a tar.md5 and I'll try it. But that's tomorrow, now it's SuperBowl. Thanks all.

Is Kingo chinese spyware?

I too need root help
I just got the Verizon Note 3 today and it came out of the box with build MJE on it. I tried Kingo's app to root it and it said unsupported after it tried to root it. I cannot find a method of rooting the device with this build number. I am hesitant about moving everything to the new phone just to have to wipe it again.

wizard62777 said:
I just got the Verizon Note 3 today and it came out of the box with build MJE on it. I tried Kingo's app to root it and it said unsupported after it tried to root it. I cannot find a method of rooting the device with this build number. I am hesitant about moving everything to the new phone just to have to wipe it again.
Click to expand...
Click to collapse
use "vroot"
remember disable all firewall and anti virus.
i was rooting my phone for 5 days now. finally got it rooted.

I follow all the instructions for vroot, but when I install SuperSU it tries to disable KNOX but it says failed, and root checker says I still don't have root access.

wizard62777 said:
I follow all the instructions for vroot, but when I install SuperSU it tries to disable KNOX but it says failed, and root checker says I still don't have root access.
Click to expand...
Click to collapse
try run vroot as administrator. i happened to me yesterday.

I finally got vroot to give me root access on my phone, but now I cant get SuperSU to install and update and get rid of the chinese root.

WOW
I posted the original post asking for help rooting using dela vega and still no help. Everyone says use kingo and that's apparently not working now either. So I'm going to go read up on vroot as many have suggested.
This is not the type of help that I got the last time I posted for help on my S2.
ADMIN you can close this thread it went no where.

ansel1 said:
I posted the original post asking for help rooting using dela vega and still no help. Everyone says use kingo and that's apparently not working now either. So I'm going to go read up on vroot as many have suggested.
This is not the type of help that I got the last time I posted for help on my S2.
ADMIN you can close this thread it went no where.
Click to expand...
Click to collapse
de la vega won't work with mje - there are a slew of posts stating such.
Sent from my SM-N900V using XDA Premium 4 mobile app

Reilly1812 said:
de la vega won't work with mje - there are a slew of posts stating such.
Click to expand...
Click to collapse
Correct. De la vega no longer works on the latest Verizon builds. Samsung patched the exploit up. Kingo has been having very slow website and server problems, so people have not been able to root using that either. The only one that's working correctly at the moment is vRoot.
Once you root with vRoot, do a search for chainfire's SU 1.00 apk and flash that in SafeStrap. That will get rid of the Chinese SU app. Then you can also uninstall the other Chinese app that gets installed.

-BoneZ- said:
Correct. De la vega no longer works on the latest Verizon builds. Samsung patched the exploit up. Kingo has been having very slow website and server problems, so people have not been able to root using that either. The only one that's working correctly at the moment is vRoot.
Once you root with vRoot, do a search for chainfire's SU 1.00 apk and flash that in SafeStrap. That will get rid of the Chinese SU app. Then you can also uninstall the other Chinese app that gets installed.
Click to expand...
Click to collapse
Just bought a VZW Note 3 (N 9000V UD) and I could swear it came with MJE but I still got an OTA and since I was reading that Kingo worked with MJE, I took it. Kingo didn't work before as far as I could tell, but I had only tried a few times. After, I can say definitively that Kingo is useless.
Tried De La Vega next and can also confirm that it's useless on OTA MJE. Got an error during ODIN upload and was soft-bricked at that point. ODIN'd back to OEM MJE, tried De la Vega again and got the same result; soft-brick.
As of 20140209, I cannot find a way to root a new VZW Note 3 but I'm still looking because as nice as this hardware is, I couldn't care less if I can't even restore my apps/data (backed up with TB).
I have looked at vroot, but since it's not in English, I'm not sure how far I'd get and I'm nervous as hell relying on something that's such a clear security risk.

rainabba said:
I have looked at vroot, but since it's not in English, I'm not sure how far I'd get and I'm nervous as hell relying on something that's such a clear security risk.
Click to expand...
Click to collapse
The vRoot software for your PC is in English. Only the SU app is in Chinese, but you need to overwrite that SU app with a secure one like chainefire's anyway.
The security risk is minimal if you have good security software on your PC and if you replace the Chinese SU with a more secure one. And the security risk is virtually eliminated if you install Safestrap and then use a different ROM.

-BoneZ- said:
The vRoot software for your PC is in English. Only the SU app is in Chinese, but you need to overwrite that SU app with a secure one like chainefire's anyway.
The security risk is minimal if you have good security software on your PC and if you replace the Chinese SU with a more secure one. And the security risk is virtually eliminated if you install Safestrap and then use a different ROM.
Click to expand...
Click to collapse
I did get rooted after some 3 hours of sifting through old posts and figuring out how to get through the Chinese interface of vroot but I saw some warnings while installing that I don't like (mtkcamera) and so far, I've had to re-root at least 6 times while trying to get SuperSU in place.
All the directions indicate that I need to launch SuperSU, grant it permissions, then continue but when I open it, I immediately get the "outdate binary" prompt and no superuser prompt so I can't move forward with this one. I'm going to try an older version of SuperSU in the hopes that it will be less agressive with the binary update and perhaps give me a shot at authorizing it.
UPDATE:
Thanks to cubarican84, I used the following SIMPLE solution to clean up the chinese superuser mess: http://www.w0lfdroid.com/2013/11/How-to-Remove-Replace-VRoot-Chinese-superuser-with-SuperSU.html?m=1

Reilly1812 said:
de la vega won't work with mje - there are a slew of posts stating such.
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I thought it worked but tripped knox.
Sent from my SM-N900V using Tapatalk 2

recDNA said:
I thought it worked but tripped knox.
Sent from my SM-N900V using Tapatalk 2
Click to expand...
Click to collapse
With MJE just soft bricks. Unless there's a trick like repartitioning or something. But nobody has chimed in on that thread despite numerous help requests.
Just got Kingo working again tonight. May have to try a few times. I succeeded using USB 3 cable in MTP USB 3.0 mode.
Sent from my SM-N900V using Tapatalk

Were you able to update supersu in the playstore?
Sent from my SM-N900V using Tapatalk 2

[Q] Verizon SM-N900V root woes

Some history:
I rooted my Verizon Note 3 running v4.4.2 using TowelRoot, SuperSU, and SafeStrap. All was well.
I tried installing a custom ROM and bricked the phone. Using ODIN, I flashed the latest stock firmware from SamMobile, which included Android v4.4.4.
Apparently TowelRoot doesn't support v4.4.4. I tried to use ODIN to go back to v4.4.2. When plugging in the phone, it says "Added!" but when I select the .tar.md5 file and click Start, it gives me a big ugly "FAILED" message.
I've been spending copious amounts of time on Google/the forums trying to find a root method for v4.4.4, but to no avail, so I have two questions:
Does anyone know how I can go back to v4.4.2?
Does anyone know how I can root my v4.4.4 device?
Thanks in advance for any help. All this bloatware is killing me.

rickwschneider said:
Some history:
I rooted my Verizon Note 3 running v4.4.2 using TowelRoot, SuperSU, and SafeStrap. All was well.
I tried installing a custom ROM and bricked the phone. Using ODIN, I flashed the latest stock firmware from SamMobile, which included Android v4.4.4.
Apparently TowelRoot doesn't support v4.4.4. I tried to use ODIN to go back to v4.4.2. When plugging in the phone, it says "Added!" but when I select the .tar.md5 file and click Start, it gives me a big ugly "FAILED" message.
I've been spending copious amounts of time on Google/the forums trying to find a root method for v4.4.4, but to no avail, so I have two questions:
Does anyone know how I can go back to v4.4.2?
Does anyone know how I can root my v4.4.4 device?
Thanks in advance for any help. All this bloatware is killing me.
Click to expand...
Click to collapse
There's no going back... at the moment. You're stuck til someone finds a way to root

yep no going back no root only a small ever dimming glimmer of hope... at least you might get 5.0 before the rest of us at the rate development on the note 3 is going... i wish the bootloader would break itself open

[Q] How to root T337A

hi all. I have searched and tried the only 2 different roots that said that worked.
I used towel root and didn't work. I also tried srsroot and it said it worked but nothing.
So, any way I can do this?
Picture: i.imgur.com/uctefka.jpg

If your kernel is past June of last year, you can't root the AT&T tab 4. I'm not responsible if something happens to your device, but you could try downloading the only ODIN file you'll find on sammobile.com and load up that. I'm not saying it will work, not even sure you can downgrade to that version. You may brick your tab. if it works, then you can root with towelroot and make sure to freeze any and all updater apps right away. Good luck

pre4speed said:
If your kernel is past June of last year, you can't root the AT&T tab 4. I'm not responsible if something happens to your device, but you could try downloading the only ODIN file you'll find on sammobile.com and load up that. I'm not saying it will work, not even sure you can downgrade to that version. You may brick your tab. if it works, then you can root with towelroot and make sure to freeze any and all updater apps right away. Good luck
Click to expand...
Click to collapse
Has anyone tried this?

Juan71287 said:
hi all. I have searched and tried the only 2 different roots that said that worked.
I used towel root and didn't work. I also tried srsroot and it said it worked but nothing.
So, any way I can do this?
Picture: i.imgur.com/uctefka.jpg
Click to expand...
Click to collapse
Have you tried this method ?