Rooting Verizon Note3 Help - Verizon Galaxy Note 3 Q&A, Help & Troubleshooting

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

Related

[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.

STOCK and ROOTED SGH-I257M

Thanks to @spyke555 for his backup copy of the Rogers version of the SGH-I257M firmware. I managed to root it with vroot, so there is a chinese version of SU on there but it works. I also stuck busy box on it and tried to get rid of most of Rogers apps.
Now to use this, you must stick it into your backup folder (i.e: clockworkmod/backup) it is NOT a flashable rom, it is a backup. If anyone wants to turn it into a flash rom, or create custom roms out of it, please do. Need to see some I257M roms popping up.
Dropbox
Box.com
G Drive
We also have @dsavard copy of the stock firmware from Koodo, which you can flash with Odin
Dropbox
Mirror 1
And here we have all of the STOCK and UNROOTED firmware for the Canadian I257M over at Sammobile
All vroot does is give root access without changing the rom. It uses the chinese program Superuser 1.0.4. You can get rid of this by following these steps:
Go to play store and install SuperSU.
Start SuperSU and you will be asked for permission by Superuser 1.0.4, choose 允许(means allow). (Should be the right side option.)
SuperSU will prompt to install SU binary, go ahead with OK and it will display successful.
Now, freeze Superuser 1.0.4 in titanium backup, just in case you need it again.
Note: If you uninstall straight away from app manager, you need to make sure SuperSU updated the binary.
Re-run SuperSU to make sure everything is alright. You will be prompt again to install SU binary, just do what it asked.
After that, you are rooted with SuperSU and Superuser 1.0.4 will not be there anymore.
Once you do that, SuperSU will be the default and will be in english.
Good to see this here. I just picked up my S4 Mini today. I'm from Canada so I'm assuming it's a slightly different version than the other models? Cause mine in an SGH-1257M. Is it a different process to root it?
I'm not too familiar with vroot. My last phone was an HTC Evo 3D.
Skyty said:
Good to see this here. I just picked up my S4 Mini today. I'm from Canada so I'm assuming it's a slightly different version than the other models? Cause mine in an SGH-1257M. Is it a different process to root it?
I'm not too familiar with vroot. My last phone was an HTC Evo 3D.
Click to expand...
Click to collapse
vroot is like SRS or any other one touch root program, but it's in chinese. Easy to use and has a high success rate for most phones. the I257M is slightly different from what we can tell from the other models; different features. As far as I can tell there isn't a different way to root this but I'm not to sure how the others were rooted. I also don't know if there is anything different between the Bell, Rogers, Fido, etc. versions besides their own bloatware. I hope I can get all the different versions uploaded.
Omega2513 said:
vroot is like SRS or any other one touch root program, but it's in chinese. Easy to use and has a high success rate for most phones. the I257M is slightly different from what we can tell from the other models; different features. As far as I can tell there isn't a different way to root this but I'm not to sure how the others were rooted. I also don't know if there is anything different between the Bell, Rogers, Fido, etc. versions besides their own bloatware. I hope I can get all the different versions uploaded.
Click to expand...
Click to collapse
Yeah, I have a Rogers phone. Just got it yesterday.
Is there a guide on here how to root with vroot? I'm not too good at rooting and whatnot. I've only done it once on my Evo 3D and that was more than a year a go haha!
Just google it. The vroot forum has step by step with pictures
Sent from my SGH-I257M disguised as a GT-I9195
hey can someone help me?
i have a telus version and i would like to back mine up and post an image for you guys. we can then update the first post with the different carrier versions if we ever need to go back to stock for warranty purposes. i'd also like to see if there are different files from the carriers.
Omega2513 said:
Just google it. The vroot forum has step by step with pictures
Sent from my SGH-I257M disguised as a GT-I9195
Click to expand...
Click to collapse
Will do!
Edit: So I found this post:
http://forum.xda-developers.com/showthread.php?t=2455822
It mentions select the drivers for your phone? Is the S4 Mini supported?
infamouskid said:
hey can someone help me?
i have a telus version and i would like to back mine up and post an image for you guys. we can then update the first post with the different carrier versions if we ever need to go back to stock for warranty purposes. i'd also like to see if there are different files from the carriers.
Click to expand...
Click to collapse
There are forums here on how to temporarily give root and install CMW to make a backup.
Well, I just rooted my phone using VROOT. It is still recognized as an SGH-I257M. However, when any of my apps update it's all in Mandarin (I think?). Would I simply use the backup you posted? Would that solve that issue?
Will the I9195 roms work with phone even though I didn't root it as a I9195?
Skyty said:
Well, I just rooted my phone using VROOT. It is still recognized as an SGH-I257M. However, when any of my apps update it's all in Mandarin (I think?). Would I simply use the backup you posted? Would that solve that issue?
Will the I9195 roms work with phone even though I didn't root it as a I9195?
Click to expand...
Click to collapse
All vroot does is give root access without changing the rom. It uses the chinese program Superuser 1.0.4. You can get rid of this by following these steps:
Go to play store and install SuperSU.
Start SuperSU and you will be asked for permission by Superuser 1.0.4, choose 允许(means allow). (Should be the right side option.)
SuperSU will prompt to install SU binary, go ahead with OK and it will display successful.
Now, freeze Superuser 1.0.4 in titanium backup, just in case you need it again.
Note: If you uninstall straight away from app manager, you need to make sure SuperSU updated the binary.
Re-run SuperSU to make sure everything is alright. You will be prompt again to install SU binary, just do what it asked.
After that, you are rooted with SuperSU and Superuser 1.0.4 will not be there anymore.
Once you do that, SuperSU will be the default and will be in english.
You can use the backup that I posted but it would be the same as your stock rom. The backup is just for those who don't want to root their own rom, doesn't trust the program, etc. The I9195 roms will still work, but when you flash them, your phone will recognize itself as a GT-I9195 instead of SGH-I257M
Sorry for bumping this, but I wanted to ask, did you have any trouble installing CWM after you rooted with VROOT?
It keeps telling me that SGH-I257M is unsupported.
What I did was use the I9195 rooting method to get CWM installed then switch back with I257M backup. It turns your phone back to I257M but CWM stays installed. You could also try installing twrp
Sent from my SGH-I257M disguised as a GT-I9195
Omega2513 said:
What I did was use the I9195 rooting method to get CWM installed then switch back with I257M backup. It turns your phone back to I257M but CWM stays installed. You could also try installing twrp
Sent from my SGH-I257M disguised as a GT-I9195
Click to expand...
Click to collapse
Ah... that's why I'm having issues. I'll look into TWRP.
Edit: Just tried TWRP. No luck.
It wouldn't backup my ROM. Just booted me into recovery with no option of backing up.
Edit #2:
Slowly figuring this out. I unrooted my phone and re-rooted with the I9195 method. I now have CWM.
What I think it is, the I9195 method unlocks the bootloader where just rooting the I257M doesn't do that
Sent from my SGH-I257M disguised as a GT-I9195
Be warned, VRoot and Kingo rooting methods have been temporarily banned from XDA forums. All links to the software have been removed from the posts.
During the rooting process, they collects sensitive data like IMEI and send it to remote servers. XDA moderators are currently investigating the issue to determine if it was done with bad intention or not.
For more information, check this thread : http://forum.xda-developers.com/showthread.php?t=2516942
dsavard said:
Be warned, VRoot and Kingo rooting methods have been temporarily banned from XDA forums. All links to the software have been removed from the posts.
During the rooting process, they collects sensitive data like IMEI and send it to remote servers. XDA moderators are currently investigating the issue to determine if it was done with bad intention or not.
For more information, check this thread : http://forum.xda-developers.com/showthread.php?t=2516942
Click to expand...
Click to collapse
Hmm... good to know... thanks!
I unrooted my phone and re-rooted via the I9195 so I could get CWM. Hopefully it removed anything that VROOT left.
dsavard said:
Be warned, VRoot and Kingo rooting methods have been temporarily banned from XDA forums. All links to the software have been removed from the posts.
During the rooting process, they collects sensitive data like IMEI and send it to remote servers. XDA moderators are currently investigating the issue to determine if it was done with bad intention or not.
For more information, check this thread : http://forum.xda-developers.com/showthread.php?t=2516942
Click to expand...
Click to collapse
Thanks for the info. I didn't realize that was possible
@Omega2513 As a safer alternative, why not install the S4Mini_RootKit_v1.zip from arco68 (http://forum.xda-developers.com/showthread.php?t=2364980) from CWM Recovery ? It is the same for all s4 mini (I9190, I9192 and I9195), so I suppose it will work for the SGH-I257M too.
It's possible it could work. Never tried it, but since it does the other models, I don't see why not.
Sent from my SGH-I257M disguised as a GT-I9195
I've got a backup of the latest Koodo SGH-I257M stock firmware [MK5 (KDO)]) by following this recipe:
​http://forum.xda-developers.com/showthread.php?p=23188887
I've uploaded it online for anyone who could need it :
​[EDIT: Download not available anymore. Anyway the firmware is now available on Sammobile.]
It seems to be in the same format than firmwares found on the sammobile web site. So, it could be useful for those who wish to revert to stock with Odin... and know how to do it.

Root SM-N900V MJE

Hi everyone, I'm having some issues trying to root my Note 3 SM-N900V on MJE. Here are the methods I have tried thus far:
-Installed/Ran Kingo
*Result: Device not supported (Multiple attempts, tried USB 2.0/3.0, uninstall/reinstall drivers and applications, flashed stock MJE rom then ran - same result)
-URDLV
*Result: Odin FAILED (used MJE from provided link to create .tar in terminal window, made second .tar in terminal using MJE from sammobile - same result, had to flash stock rom with Odin to get phone working again)
Is there a way to root this phone?
Same problem.....can't root this phone
I have tried everything.... anyone have a solution????
jimmayg said:
Hi everyone, I'm having some issues trying to root my Note 3 SM-N900V on MJE. Here are the methods I have tried thus far:
-Installed/Ran Kingo
*Result: Device not supported (Multiple attempts, tried USB 2.0/3.0, uninstall/reinstall drivers and applications, flashed stock MJE rom then ran - same result)
-URDLV
*Result: Odin FAILED (used MJE from provided link to create .tar in terminal window, made second .tar in terminal using MJE from sammobile - same result, had to flash stock rom with Odin to get phone working again)
Is there a way to root this phone?
Click to expand...
Click to collapse
Use vroot. It will and it will not trip Knox. I soft bricked mine this morning after screwing around. I used Odin to get back to stock MJE then I rooted with vroot. It a simple one click root but you have to search for the method of removing the Chinese superuser
sent from tapatalk....probably while pooping.
For this device you need Kingo 1.1.8. (Found on there Facebook page) If you downloaded Kingo from there site, it is the newest version witch may not work properly. Uninstall the version you have, reboot your PC and install 1.1.8. You may need to run Kingo more than one time before it takes. I had to run it 3 time before it took.
Good luck
phillymade said:
For this device you need Kingo 1.1.8. (Found on there Facebook page) If you downloaded Kingo from there site, it is the newest version witch may not work properly. Uninstall the version you have, reboot your PC and install 1.1.8. You may need to run Kingo more than one time before it takes. I had to run it 3 time before it took.
Good luck
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2630466&page=12 post #115
chriscw81 said:
Use vroot. It will and it will not trip Knox. I soft bricked mine this morning after screwing around. I used Odin to get back to stock MJE then I rooted with vroot. It a simple one click root but you have to search for the method of removing the Chinese superuser
Click to expand...
Click to collapse
Thank you for the reply, this is what I ended up using and it worked flawlessly. Installed app, clicked root, and I was rooted.
For those who don't know: Only drawback to Vroot is that it installs Chinese SU. For fix, type 'Replace Chinese Superuser' into google and follow first, or second link (first is video). (can't provide link because I haven't posted 10 times :/ ) The fix is easy and works instantaneously.
phillymade said:
For this device you need Kingo 1.1.8. (Found on there Facebook page) If you downloaded Kingo from there site, it is the newest version witch may not work properly. Uninstall the version you have, reboot your PC and install 1.1.8. You may need to run Kingo more than one time before it takes. I had to run it 3 time before it took.
Good luck
Click to expand...
Click to collapse
As far as Kingo 1.1.8 goes I was never able to find it... I read that people had success with that version but every time I followed links to obtain it I just got the same ole 1.2.0. (went to FB page and installed version was 1.2)
Thanks again for all the help everyone, Vroot did it for me
Cool, glad it worked out for ya.
sent from tapatalk....probably while pooping.

[Q] Note 3 Manual Re-Root - no SU binary installed

I rooted my device with Kingo Android root. I am currently running android OS 4.3.
Everything was going just fine until just today when opened SuperSU and it told me that there is no SU binary installed. SuperSU cannot install it.
Pretty much I need to manually re-root my device.
I am not aware of any recovery files that I may have. To clarify, I have never backed up my device in any way. I have only had it for a month, and there is hardly anything on it. I figured, why bother? Well now I know.
I have done quite a few google searches about this, and I can not find any help.
What is my best course of action?
Thank you very much.
Try reflash and re-root with cf-auto root through Odin. A a small question: u still have root right to install some app such root explorer and titanium backup?
Sent from my SM-N9005 using XDA Premium 4 mobile app
hhai2pth said:
Try reflash and re-root with cf-auto root through Odin. A a small question: u still have root right to install some app such root explorer and titanium backup?
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Unfortunatly, I no longer have root. None of my root apps can get root permissions because the SU binary is missing.
I tried flashing my firmware, but now my phone is stuck in an unusable state. The official firmware leaves me unable to boot with a "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
When I flash a different ROM on top of that one, all my spen stuff is messed up.
This is way different from jailbreaking. There are so many rom files I have a hard time finding the one I need.
SM-900A in case anyone wants my number.
DrShenanigan said:
Unfortunatly, I no longer have root. None of my root apps can get root permissions because the SU binary is missing.
I tried flashing my firmware, but now my phone is stuck in an unusable state. The official firmware leaves me unable to boot with a "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
When I flash a different ROM on top of that one, all my spen stuff is messed up.
This is way different from jailbreaking. There are so many rom files I have a hard time finding the one I need.
SM-900A in case anyone wants my number.
Click to expand...
Click to collapse
You need to go on sammobile and download your stock firmware (you probably want to stay on 4.3 unless your particular phone and carrier have root capabilities on 4.4.2 which verizon and att do not yet have) then flash it through odin... just search your model # through sammobile and it will show all the available stock firmwares. That will at least get you running again then u will have to root it again from there
Posted from my beast of a VZW Note 3!!
I downloaded the firmware from that site and have tried to flash it.
I get an Error Meassage:
SW REV CHECK FAIL : [sb1]Fused 2 > Binary 1
DrShenanigan said:
I rooted my device with Kingo Android root. I am currently running android OS 4.3.
Everything was going just fine until just today when opened SuperSU and it told me that there is no SU binary installed. SuperSU cannot install it.
Pretty much I need to manually re-root my device.
I am not aware of any recovery files that I may have. To clarify, I have never backed up my device in any way. I have only had it for a month, and there is hardly anything on it. I figured, why bother? Well now I know.
I have done quite a few google searches about this, and I can not find any help.
What is my best course of action?
Thank you very much.
Click to expand...
Click to collapse
1st : I dunno ur device which version of note 3.
2nd : kingo sometimes for some device not working well. Try avoid to use this method. Try cf-autoroot instead. Easy nd simple, but knox will trip.
3rd : have u tried update to latest supersu?
3rd :
Sent from somewhere under the sky, at the vorner of this rounded earth.
antique_sonic said:
1st : I dunno ur device which version of note 3.
2nd : kingo sometimes for some device not working well. Try avoid to use this method. Try cf-autoroot instead. Easy nd simple, but knox will trip.
3rd : have u tried update to latest supersu?
3rd :
Sent from somewhere under the sky, at the vorner of this rounded earth.
Click to expand...
Click to collapse
Updating SuperSU is what cause this mess, I believe. It's too late for that now anyhow, because my phone does not boot.
I have the SM-900A. There is no cf-autoroot for it. Not that I canfind at least.
DrShenanigan said:
Updating SuperSU is what cause this mess, I believe. It's too late for that now anyhow, because my phone does not boot.
I have the SM-900A. There is no cf-autoroot for it. Not that I canfind at least.
Click to expand...
Click to collapse
Try this, mate
http://forum.xda-developers.com/showthread.php?t=2466423

[Q] NC-4 can't get it rooted?....Help please

Ok I did take that darn update and so am on: NC-4
I used the " towelroot " when it was first introduced.
I have the " Unlocked padlock " with the word "custom" under it when I reboot.
I have used " Root checker basic " by Joeykrim. " this device does not have proper root access".
I have been reading loads of thread's but can't find anyone else who is having the same issue.
I then tried towelroot 2 and 3 when they came out, but I still can't get my phone rooted.
I don't know what to try now.
Did You update the su binaries? As per op
Sent from my SM-N900V using XDA Premium 4 mobile app
Have you just tried a different root checker?
I did and have
Sorry for my slow response, RL got crazy for a few days there.
I did update the SU, via the link to chain fire
I have tried multiple root checkers.
I am about to go through the steps again.
j_axxy said:
Sorry for my slow response, RL got crazy for a few days there.
I did update the SU, via the link to chain fire
I have tried multiple root checkers.
I am about to go through the steps again.
Click to expand...
Click to collapse
If it doesn't work again try reflashing the NC4 stock tar via odin and trying the towelroot process again. The SU binaries not being up to date should have no effect on whether you are actually rooted or not.
FIXED
kinstre11 said:
Try reflashing the NC4 stock tar via odin and trying the towelroot process again.
Click to expand...
Click to collapse
That got it done, thank you kindly kinstre11.
My pleasure.

Categories

Resources