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.

I installed update and Kingo wont Root my device...Help!

Is there another root method I could use to root my device. Kingo goes through the whole process then fails.
Thanks!

stu5797 said:
Is there another root method I could use to root my device. Kingo goes through the whole process then fails.
Thanks!
Click to expand...
Click to collapse
Suggestions:
Make sure you have USB debugging enabled. Shut down and do a battery pull and re-try.
I haven't tried Kingo with the new update, but the battery pull seemed to help on MJ7 and I have seen where others successfully used Kingo after the update.

I did have USB debug enabled. Kingo goes through the whole process then says root failed

It worked. Forgot to turn off anti virus on computer

stu5797 said:
Is there another root method I could use to root my device. Kingo goes through the whole process then fails.
Thanks!
Click to expand...
Click to collapse
already answered

az_biker said:
already answered
Click to expand...
Click to collapse
so is kingo safe???

jrocc24 said:
so is kingo safe???
Click to expand...
Click to collapse
If you are ALREADY on MJE, root with Kingo, then install safestrap
If you are still on MI9 or MJ7, boot into odin and install MJ7 tar, accept MJE OTA, root with Kingo, install SS, profit.
With the exception of the above info, check out my SIG and see the detailed step by step!

but i mean with that whole stealing IMEI and all that... just a worry and not a reality?

jrocc24 said:
but i mean with that whole stealing IMEI and all that... just a worry and not a reality?
Click to expand...
Click to collapse
After gaining root with Kingo, there are steps in my SIG instructions how to install Chainfire's SuperSU which overwrites Kingo's superuser. Also, once rooted, I would uninstall Kingo app from pc, run quick anti-virus scan... I know dozens of users who have done this with ZERO issues, including myself.
As with ANYTHING when rooting your phone, it is YOUR call and your responsibility to change, add or remove anything related to your phone. But I can tell you, I have not heard of ONE verifiable incident of erroneous data collection or anything similar related to the use of Kingo.
Follow my steps, and enjoy! Don't forget to hit THANKS if this helped you and pass the word to others who would benefit from the step by step...

thanks man!! i hit thanks twice ill keep it in mind when i need it for tethering once they totally block it... once again thank you

Kingo is SAFE.
You also need to set your screen timeout to be 10 minutes and swipe to unlock your device to get to your home screen and leave it there while it installs.
You don't need to remove any PIN's or passwords you have, just get into the phone because Kingo will ask you to install a few programs on your device to get it to root.

RypeDub said:
Kingo is SAFE.
.
Click to expand...
Click to collapse
I don't think ANYBODY can state that 100% although it does seem relatively low risk at this point.

jmorton10 said:
I don't think ANYBODY can state that 100% although it does seem relatively low risk at this point.
Click to expand...
Click to collapse
Technically nobody can say ANY program that uses an exploit is 100% safe. Uninstall kingo from pc immediately (anti virus scan) install Chainfire's superSU immediately after root (overwrites kingo superuser)...
Notorious 3

got my new Note 3 today, i let it install the newest MJE update right away. Followed the directions with latest Kingo 1.1.5, it just sits there and says it can't connect over and over and does this little flashing between the orange and red icon on the Kingo client. Running on Windows XP, going to try again on a different pc with Windows 7 this evening. Yes USB debugging enabled and screen timeout set to max (10 minutes). Tried two different cables too. Tried different USB ports, tried rebooting phone and pc.

neyenlives said:
got my new Note 3 today, i let it install the newest MJE update right away. Followed the directions with latest Kingo 1.1.5, it just sits there and says it can't connect over and over and does this little flashing between the orange and red icon on the Kingo client. Running on Windows XP, going to try again on a different pc with Windows 7 this evening. Yes USB debugging enabled and screen timeout set to max (10 minutes). Tried two different cables too. Tried different USB ports, tried rebooting phone and pc.
Click to expand...
Click to collapse
Turn off you anti virus

Can't, I'm on a work pc right now. Will try later on my laptop at home.
Sent from my SM-N900V using Tapatalk

neyenlives said:
Can't, I'm on a work pc right now. Will try later on my laptop at home.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Make sure display timeout
is over 10 min, disable pc anti-virus. Retry even if kingo fails..took me 3 attempts
Check link in my sig for step by step
Notorious 3

It was the anti-virus I guess, worked fine first time at home on my laptop after disabling MSE real time protection.
Sent from my SM-N900V using Tapatalk

Glad you're up and running
Notorious 3

Just to confirm a few things:
Was running MJ7 rooted w/ Beans build 4
installed stock MJ7 tar through Odin
rebooted
Took MJE OTA
rebooted
rooted via Kingo
installed Chainfire's SuperSU
Installed Safestrap
restored MJ7 rom (Beans Build 4)
NOT a single issue after re-rooting with Kingo
MJE running MJ7 Rom
VERIFIED KNOX 0x0 and 0x0

Can't Root Note 3 (on MJE) with Kingo Root- HELP!

I just recently did a manual update of my Note 3 with Odin and am now on MJE. Every time I plug the Note in and run Kingo Root it never recognizes the phone but the computer does!
I have tried using a different USB port, re-installed Kingo, I'm sure my drivers are correct because again, I can connect to the PC with no problem.
Anyone have any idea how to get Kingo going? I am familiar with it since I used it to root my Note 3 when on MJ7 previously.
PLEASE HELP! I have a lot of apps that depend on root access that now I can't run any more.
Thanks.
P.S. - Sorry if this has already been covered somewhere here on the forum. I did several searches but came up with nothing.

What worked for me was turning on automatic updates in windows. I always have it disabled so I can control the windows update process.
Sent from my SM-N900V using XDA Premium 4 mobile app

Reilly1812 said:
What worked for me was turning on automatic updates in windows. I always have it disabled so I can control the windows update process.
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the info. I'm currently at work, and it appears that Windows automatic updates are already on and set to update once every week. However, all of these settings are actually greyed out so I assume that only my administrator can make any changes to these settings.
When I used Kingo before I was at home, so maybe I'll have more luck when I get there but surely welcome yours and anyone else's ideas on this.

See if vroot will do the job for you.

I'm having a Similar issue, I have the MJE update, however no matter what I do, I'm getting a "Not Support" error when trying to root, and I've tried multiple cables, ports, and two PCs now, getting the exact same error. I googled around but wasn't able to see ANYONE with this error, and all Kingo says to do is keep trying when the root fails.
Edit: i've even tried wiping my phone and resetting to defaults, but still, i get this error, my PC at home was windows 8 enterprise, and the PC i tried at work was XP, i'm going to try a win7 PC next, but this is really frustrating.

In the same boat, for the most part.
Got the phone three days ago. Shipped with MI9. Odined to MJE.
Tried every combination of Kingo 1.1.6, 1.1.7 and 1.1.8, along with several cords, all available USB2 and USB3 ports, along with setting the phone up as MTP, PTP and Media device USB3 mode. USB debugging is ON, every PC given authority on the phone popups. Unknown sources CHECKED. Antivirus off on PC. Display on phone set to 10 minutes. Rebooted phone and PC between installations of Kingo, between attempts at rooting, between driver installations and uninstallations. Let Kingo install drivers, pre-installed through XDA links to drivers on Sam's site. You name it, I've tried it. In all, I've spent about 4 hours trying over 100 permutations of variables I could think of. Goose eggs.

ZachPA said:
In the same boat, for the most part.
Got the phone three days ago. Shipped with MI9. Odined to MJE.
Tried every combination of Kingo 1.1.6, 1.1.7 and 1.1.8, along with several cords, all available USB2 and USB3 ports, along with setting the phone up as MTP, PTP and Media device USB3 mode. USB debugging is ON, every PC given authority on the phone popups. Unknown sources CHECKED. Antivirus off on PC. Display on phone set to 10 minutes. Rebooted phone and PC between installations of Kingo, between attempts at rooting, between driver installations and uninstallations. Let Kingo install drivers, pre-installed through XDA links to drivers on Sam's site. You name it, I've tried it. In all, I've spent about 4 hours trying over 100 permutations of variables I could think of. Goose eggs.
Click to expand...
Click to collapse
I'm wondering if where it pulls files it needs is having issues or something and isn't pulling the dependencies we need to properly root?

So it's not just me. Bummer

int3gr4l said:
I'm wondering if where it pulls files it needs is having issues or something and isn't pulling the dependencies we need to properly root?
Click to expand...
Click to collapse
And yet, there are plenty of reports here and elsewhere of folks with Verizon Note 3's on MJE having no troubles at all rooting using Kingo. FMITGA.

ZachPA said:
And yet, there are plenty of reports here and elsewhere of folks with Verizon Note 3's on MJE having no troubles at all rooting using Kingo. FMITGA.
Click to expand...
Click to collapse
That's why I'm curious if their site is having issues with us downloading the files using the root. It fails for me with the not support error immediately after saying downloading the dependencies.

Just some added confusion... I did the same method... Odin to MJE... Root with kingo... Get same fail message... Try again but this time noticed that it actually rebooted the phone... Same fail message again... Check with root checker and I'm rooted... Install safestrap and update superSU... Good to go... Kingo says fail but I'm rooted and all root access apps working and rom slots flashed.

Lucky SOB.
Sent from my SM-N900V using xda app-developers app

having the same issue here. just got my note yesterday and been trying but no luck. getting NotSupport right after the 2nd "downloading requisite dependency files". would love some insight on this.

privy said:
having the same issue here. just got my note yesterday and been trying but no luck. getting NotSupport right after the 2nd "downloading requisite dependency files". would love some insight on this.
Click to expand...
Click to collapse
I really am wondering if it's the Kingo site. Whenever I try to navigate to the site it's taking quite a long time to load, as if they're having some issues with hosting, and when it goes to download the second set of files, it's unable to get through to the site to pull them.

Same here Privy
Sent from my SM-N900V using xda app-developers app

I had this issue when using a USB 3.0 port. Once I switched to USB 2.0, my device was recognized by the software.
Sent from my SM-N900V using Tapatalk

Same issue here, was having some issues with play store so back to stock with odin. Tried everything just like everyone else here. It has to be an issue with the kingo site. Redownloaded kingo and it tool an hour. Thats way too long and i bet root is timing out. Has to be it, at least i hope so.

Just an FYI I was on the stock OTA MJE with my note 3 and I rooted with Kingo and it literally worked the very first time I did it. Click, click boom rooted. Couldn't of been easier.
Point being it's doable on the rom, and easily. So keep it up
Sent from my SM-N900V using Tapatalk

The first time I rooted with no problem but after I went back to stock with odin I can no longer root with Kingo.

Just got my Note 3 yesterday, and have spent easily an hour installing and reinstalling drivers trying to get Kingo to work, but no luck.
As privy said: "having the same issue here. just got my note yesterday and been trying but no luck. getting NotSupport right after the 2nd "downloading requisite dependency files". would love some insight on this."
That's exactly the issue I'm having too.

Towelroot work??

I know outside of Att note 3 it hasn't been confirmed to work but wondering if anyone tried it on other note devices? Thanks.
Sent from my iPhone using Tapatalk

Used it installed safestrap and when it reboots get the unlock symbol on the boot screen
Sent from my SM-N900V using XDA Premium 4 mobile app

Works fine on my device. For the unlock symbol, download latest SU and updated binaries. That will go away.
Sent from my SM-N900V using Tapatalk

Definitely works for getting root. Rooted, installed SuperSU, Xposed, SafeStrap all successfully. Now struggling to get a rom to work (tried Eclipse & Hyperdrive). Both say they install successfully via SafeStrap and then hangs on boot up. I've seen one other post on the Eclipse thread for the same problem, so it might be something to keep an eye on.

i can verify that this method works. i just installed superuser and it works flawlessly. the only thing is make sure to download the superuser app from here so you have the updated binaries: http://download.chainfire.eu/447/SuperSU/UPDATE-SuperSU-v1.99r4.zip

re
i have root access verified w/root checker
downloaded v1.99r4.zip and installed it
when i open it it asks for me to update binary and it fails installation
any ideas or workarounds??

lazygregg said:
i have root access verified w/root checker
downloaded v1.99r4.zip and installed it
when i open it it asks for me to update binary and it fails installation
any ideas or workarounds??
Click to expand...
Click to collapse
Rerun towelroot

re
drewcam888 said:
Rerun towelroot
Click to expand...
Click to collapse
i've done that multiple times...
reran towelroot, it reboots phone..open supersu the version that i downloaded earlier from the website and try to download supersu binary and it fails

lazygregg said:
i've done that multiple times...
reran towelroot, it reboots phone..open supersu the version that i downloaded earlier from the website and try to download supersu binary and it fails
Click to expand...
Click to collapse
I seem to be in the same boat as well. Things I have tried and it still does not work:
Installed Play Store Edition
Installed 1.99r4
Installed 1.99r5
All of them are saying I need to update binaries. While I am technically rooted and can grant permissions to apps, I need to get into SuperSU so I can modify some settings.
There are several others have issues on Reddit as well, so its not a couple of people.

exaltedgod said:
I seem to be in the same boat as well. Things I have tried and it still does not work:
Installed Play Store Edition
Installed 1.99r4
Installed 1.99r5
All of them are saying I need to update binaries. While I am technically rooted and can grant permissions to apps, I need to get into SuperSU so I can modify some settings.
There are several others have issues on Reddit as well, so its not a couple of people.
Click to expand...
Click to collapse
Try this. Install safestrap 3.7x. Open it, give su permission, install recovery, hit the home button. Open supersu, update binary thru cwm/twrp. Don't click to reboot phone into recovery from supersu. Hold down home and bring safestrap back up. Reboot to recovery from there and it should update the binary. Hope this helps.
Sent from my SM-N900V using XDA Premium HD app

Dc4479 said:
Try this. Install safestrap 3.7x. Open it, give su permission, install recovery, hit the home button. Open supersu, update binary thru cwm/twrp. Don't click to reboot phone into recovery from supersu. Hold down home and bring safestrap back up. Reboot to recovery from there and it should update the binary. Hope this helps.
Click to expand...
Click to collapse
This is being very peculiar. After I installed Safe Strap, SuperSU went fine, able to get in and do what I needed to get done. I reboot into recovery. Made a backup, and rebooted system. Went right to SuperSU again. And the same issue occurs, constantly asking for updated binaries. I am trying everyone once more to make it all work. If not, then I will just stick with what I have and hopefully it doesn't cause any other issues.
Thank you for the help thus far. :good:

exaltedgod said:
This is being very peculiar. After I installed Safe Strap, SuperSU went fine, able to get in and do what I needed to get done. I reboot into recovery. Made a backup, and rebooted system. Went right to SuperSU again. And the same issue occurs, constantly asking for updated binaries. I am trying everyone once more to make it all work. If not, then I will just stick with what I have and hopefully it doesn't cause any other issues.
Thank you for the help thus far. :good:
Click to expand...
Click to collapse
Yeah I just did all this last night...I installed SafeStrap and installed Recovery, then went into SuperSU and clicked Normal when asking for updating Binaries and it hasnt asked again thankfully. All of this of course was after installing BusyBox from the Play Store.
Note though: Safestrap isnt working for flashing roms just yet, just like someone else said here, and someone else said this in the Jasmine Rom forum. I just tried it myself and everything looks fine when installing, but then when you boot up, screen goes black and unresponsive after the SS splash screen on a reboot. Hopefully we have an update to SS soon. Fair warning - make sure you create a backup of your System/Data, etc in SS before messing around...it makes it so much easier to restore in case something screws up.

pmt223 said:
Yeah I just did all this last night...I installed SafeStrap and installed Recovery, then went into SuperSU and clicked Normal when asking for updating Binaries and it hasnt asked again thankfully. All of this of course was after installing BusyBox from the Play Store.
Note though: Safestrap isnt working for flashing roms just yet, just like someone else said here, and someone else said this in the Jasmine Rom forum. I just tried it myself and everything looks fine when installing, but then when you boot up, screen goes black and unresponsive after the SS splash screen on a reboot. Hopefully we have an update to SS soon. Fair warning - make sure you create a backup of your System/Data, etc in SS before messing around...it makes it so much easier to restore in case something screws up.
Click to expand...
Click to collapse
So, can someone enlighten me on what this "root" does? I've been running SafeStrap 3.72 with HyperROM 8 and just yesterday, successfully installed Towelroot on my Verizon Note 3. I downloaded the new SU to my SDcard before running Towelroot and was able to run it immediately after root and all looks good. But... what did I actually gain? Can I now install Cyanogen or others? I am a bit fuzzy on the difference, if any, on a rooted phone vs. an unlocked bootloader. Those of us on the Verizon retail Note 3 still don't have unlocked bootloaders do we? I miss the ease of playing with my old S3! LOL. Thanks!

emtownsend said:
So, can someone enlighten me on what this "root" does? I've been running SafeStrap 3.72 with HyperROM 8 and just yesterday, successfully installed Towelroot on my Verizon Note 3. I downloaded the new SU to my SDcard before running Towelroot and was able to run it immediately after root and all looks good. But... what did I actually gain? Can I now install Cyanogen or others? I am a bit fuzzy on the difference, if any, on a rooted phone vs. an unlocked bootloader. Those of us on the Verizon retail Note 3 still don't have unlocked bootloaders do we? I miss the ease of playing with my old S3! LOL. Thanks!
Click to expand...
Click to collapse
No, you dont gain an unlocked bootlader. At this point, only the Almighty will make that happen lol. For us with Verizon Notes (and some others), this helps the folks who either a) dont want to use Kingo or the other web methods, and b) folks who were on stock 4.4.2 NC4, like from an OTA (like me). This now gave me root, where when the OTA came out people were fearing there would never be a root for it (thanks to everyone else who put monies towards a bounty). Many people as well as myself cannot use SafeStrap successfully to fully flash a rom yet (you'll see this remarked in a lot of places), so Im sure there is an update forthcoming. In the meantime, I can use TB and freeze/uninstall a lot of the bloatware crap, and use Xposed for whatever else, which is fine by me. But no, we are still a no-go on full rooting and unlocked bootladers like on some other phones, which means no CyanogenMod, etc.

pmt223 said:
No, you dont gain an unlocked bootlader. At this point, only the Almighty will make that happen lol. For us with Verizon Notes (and some others), this helps the folks who either a) dont want to use Kingo or the other web methods, and b) folks who were on stock 4.4.2 NC4, like from an OTA (like me). This now gave me root, where when the OTA came out people were fearing there would never be a root for it (thanks to everyone else who put monies towards a bounty). Many people as well as myself cannot use SafeStrap successfully to fully flash a rom yet (you'll see this remarked in a lot of places), so Im sure there is an update forthcoming. In the meantime, I can use TB and freeze/uninstall a lot of the bloatware crap, and use Xposed for whatever else, which is fine by me. But no, we are still a no-go on full rooting and unlocked bootladers like on some other phones, which means no CyanogenMod, etc.
Click to expand...
Click to collapse
Ah. Got it. Thanks!
* I successfully used SafeStrap to install HyperROM 8 on slot 1 only, so I had to lose my stock ROM, but I'm OK with that.

cnotes2019 said:
I know outside of Att note 3 it hasn't been confirmed to work but wondering if anyone tried it on other note devices? Thanks.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
i rooted today with towelroot. i have a verizon note 3 on 4.4.2

[Q] no wifi rooted at&t S4 4.4.2 NB1

greetings!
I've been searching for hours and bashing my brains trying to get wifi working. It originally broke after an OTA update
tried all the tips and still nothing works permanently. The things I have tried are too numerous to remember or list.
It's not a hardware issue as wifi can work for periods of time but it always breaks - I assume because of an update that downloads and breaks it.
i see talk of reflashing "modules" with safestrap but safestrap has never worked properly and now does not work at all ("unfortunately safestrap has stopped") Can modules be flashed from Odin?
TIA !

Sorry to hear about your troubles man. Been there, done that...
IMHO, if you don't have hardware issues, this what you should do:
ODIN to stock http://forum.xda-developers.com/show....php?t=2616221 (post 1, the Returning to Stock / ODIN section)
After that root
Root with towel root (https://towelroot.com/)
Install SuperSU (PlayStore) and let it disable Knox.
Install BusyBox (PlayStore) and let it cook
Install SELinux Mode Changer (PlayStore). Run and set it to Permissive.
Install Safestrap (http://forum.xda-developers.com/show...php?p=45693712)
Now it's time to flash you favorite rom (Safestrap has the list). Copy the following to your SD card:
Your favority ROM
SuperSU.zip file. (http://download.chainfire.eu/451/Sup...erSU-v2.01.zip)
Your modem zip file (http://forum.xda-developers.com/show...96&postcount=1).
I337 Build.prop/APN (http://forum.xda-developers.com/show...81&postcount=9)

Same boat as well I believe, need help please.
I have a Samsung Galaxy S4 AT&T I337 ucufnbn1 MDF. And I've tried to get into the UMTS menu with every possible number and trick I can find on Google, here, YouTube. And nothing works. I just want to be able to sim unlock it and also be able to put cwm recovery on it so I can put ROMs on it. I do have it rooted with Towel and have busy box installed as well as SU. Cyanogen's website picks it up by its other name jfelte or whatever and has a lot of ROMs. If someone could please help me finish getting the rest of the way, that would be greatly appreciated.

Few screens to help out
Here are a few screen shots that I hope help someone out. Please let me know what I can do if anything.

ONLY DRAGONMIKE said:
I have a Samsung Galaxy S4 AT&T I337 ucufnbn1 MDF. And I've tried to get into the UMTS menu with every possible number and trick I can find on Google, here, YouTube. And nothing works. I just want to be able to sim unlock it and also be able to put cwm recovery on it so I can put ROMs on it. I do have it rooted with Towel and have busy box installed as well as SU. Cyanogen's website picks it up by its other name jfelte or whatever and has a lot of ROMs. If someone could please help me finish getting the rest of the way, that would be greatly appreciated.
Click to expand...
Click to collapse
You won't be able to put cwm on it or cm. See index, all things at&t......in the general forum
Sent from my Nexus 5 using XDA Free mobile app

Ummmm a tiny bit more help please lol
I looked at the stuff in that link and like eating ice cream to fast , I got a brain freeze or headache........ Lol. I'm getting that I need to downgrade to mk this and flash that. Could someone be kind enough to give me a quick but correct step by step run through. Again it'd be very appreciated.

ONLY DRAGONMIKE said:
I looked at the stuff in that link and like eating ice cream to fast , I got a brain freeze or headache........ Lol. I'm getting that I need to downgrade to mk this and flash that. Could someone be kind enough to give me a quick but correct step by step run through. Again it'd be very appreciated.
Click to expand...
Click to collapse
Just click on the spoiler for nb1 need users. The step by step is there. It's in the first post
Sent from my Nexus 5 using XDA Free mobile app

So this one
So are you talking about this one and if so, why would I do that when that's what I'm already on. I'm on nb1 4.4.2 rooted with towel. So I'm lost in what your trying to explain.

ONLY DRAGONMIKE said:
So are you talking about this one and if so, why would I do that when that's what I'm already on. I'm on nb1 4.4.2 rooted with towel. So I'm lost in what your trying to explain.
Click to expand...
Click to collapse
You're on nb1 and rooted. The next step is to install safestrap 3.72
Sent from my Nexus 5 using XDA Free mobile app

So Safestrap 3 it is
So I need to install Safestrap. I heard with my s4 being MDF , it would damage it. I could be wrong and if so cool. Just let me know no probs.

ONLY DRAGONMIKE said:
So I need to install Safestrap. I heard with my s4 being MDF , it would damage it. I could be wrong and if so cool. Just let me know no probs.
Click to expand...
Click to collapse
What's mdf?
Sent from my Nexus 5 using XDA Free mobile app

MDF Reply
Security software Version
MDF v1.0 Release 2

MDF Reply
Here is a screenshot of where I'm talking about. Oh and Safe strap 3.72 is installed perfectly thank you so very much for that. Your awesome. And a lot of people are saying when you reboot and it shows the "Safestrap is disabled" screen you can't get back into it. I did just fine.

ONLY DRAGONMIKE said:
Here is a screenshot of where I'm talking about.
Click to expand...
Click to collapse
You're on nb1 firmware, safestrap is ok
Sent from my Nexus 5 using XDA Free mobile app

NB1 discussion
Ok , well I honestly appreciate your help with this. With this setup can I install any ROMs at all? Am I limited to certain ones or can I install any compatible ones for my model? I know sometimes when your on a certain stock ROM your stuck with only like certain types. Like Paranoid or whatever it is, and a few others.

ONLY DRAGONMIKE said:
Ok , well I honestly appreciate your help with this. With this setup can I install any ROMs at all? Am I limited to certain ones or can I install any compatible ones for my model? I know sometimes when your on a certain stock ROM your stuck with only like certain types. Like Paranoid or whatever it is, and a few others.
Click to expand...
Click to collapse
You can not install any roms. The i337 on any firmware higher than mdl can only flash touch wiz based roms. See the index, all things at&t.... for roms that are compatible.
Sent from my Nexus 5 using XDA Free mobile app

This mini-guide should work!
The problem is, in order to get WiFi working, you need to install the NB1 modules, but to do that, you need to install Safestrap. However, you can not install Safestrap because the app keeps closing on you. There is a simple fix to this, which I will explain later. For now, just read this WHOLE post BEFORE you do anything, and keep in mind that I am NOT held liable if you mess up your phone. Use this at your own risk.
1.) Root your phone
If you're already rooted with something like SuperSU or Superuser, skip this. If not, read ahead. Download and install the Towelroot APK file attached to this post, open it, and click 'make it ra1n'. If your phone didn't reboot, now you have root (they need to trademark that). Now, down below, I also included the APK for SuperSU. Download and install it. Now open it. When you open it, let it install the 'Normal' way, not via the 'TWRP/CWM' way. Also, when it asks you to disable KNOX, say yes, wait a couple of minutes (it will still be loading) and reboot your phone. Open up SuperSU again, click 'Yes' to disable KNOX again, and now you have a good base to start from.
2.) Install Safestrap AFTER fixing the error
The error your are getting is easily fixed. Go to the Play Store and install 'SELinux Mode Changer'. Open it, grant it root access, and change the mode to 'Permissive'. Now, open up Safestrap again (you mentioned you already installed it), and it shouldn't force close. Click 'Install', and if the 'Reboot to Recovery' option below is not grayed out after that then it worked.
3.) Download and install the NB1 modules
On your phone, download the included NB1 modules ZIP file I attached for you, and once that is done you need to reboot. After the Galaxy S4 logo, you'll see a screen that says 'SAFESTRAP: DISABLED' and there will be a little robot. TIP: To enter Safestrap, press the menu button (physical, hardware key) under 'Recovery' at that screen. To continue to Android, press the back key (again, physical) under the 'System' tab. For now, press the menu button under 'Recovery'. Now, click 'Install' which should be in red, click 'Add zips', and navigate to your Downloads folder. Now click on the NB1 modules ZIP you just downloaded. Swipe to install, and reboot. This time, hit the back key under 'System'.
All done!
Now, Android should (and will) boot up, and you'll have working WiFi! If, for some odd reason, you don't have WiFi- do NOT panic! Just search around for the MF3 modules and flash those! All is good, all is good. A lot of this guide was taken from my post about my personal method of SIM unlocking the AT&T Galaxy S4 without the dialer codes or an AT&T SIM. It was just modified a little to work for you.
Remember, hit thanks! :good: