Related
Hello everyone, I'm a returning (or more so new) user who's been here since the tytn2 days but gone rogue for awhile. Recently I've picked up an s4 through my contract renewal and stepped into a few hickups on rooting. beforehand, i've been on the iphone for a long time and only recently gotten somewhat recognized into the android platform with the note 10.1 before getting the s4 so i'm not completely new to it, but still a noob when it comes to fixing recurring problems when it comes to rooting. Anyways... For the past week i've tried the motochopper method to root my galaxy s4 with unsuccessful results as each time i've tried it the string: "[-] Failure." would occur every time i got it to run.
Methods of rooting:
- Particularly, motochopper was the only method of rooting that i've tried and it did install the superuser apk, however when i'm prompted to install the superuser binary update within the app the following error, "There was an error installing superuser. Please send a log of the error to the developer" always occurs. installing SuperSU and attempting to use it also didn't work as it will prompt me, "There is no binary installed, and SuperSU cannot install it. This is a problem!"
Notable things:
- I've updated my phone to the most recent firmware from att as of 4 days ago. I'm aware that this is most likely the cause of my difficulties and i was foolish to not read beforehand about the update blocking root :/.
- My phone is the galaxy s4 version sgh-i337 from AT&T US
- Baseband number is i337UCUAMF3. I'm also aware that this is the version that everyone's having trouble with for those trying to root.
- After the root attempt, i've read up on a few things regarding my issue as well as a couple of posts within the motochopper thread where some people had trouble rooting. After which i figured out that the update blocked root.
- I strongly do not want to factory reset my phone and have to back up everything but, if necessary, then i will.
- So far with the information I've read I couldn't find many clear answers which is why I ended up making this thread.
- Even with the experience that I had with the note 10.1 i'm still fairly new to android, so my apologies if all of this sounds ignorant or.. "newbish".
Problems I've come across:
- Using root checker pro i've compiled the detailed results on the bottom. It should also be noted that i was prompted, "root access not properly configured or was not granted." It will say that superuser was not installed but I can assure that it's on my app drawer.
Code:
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - is NOT installed.
SuperSU application - version 1.41 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: /system/xbin/su: No such file or directory
Analysis: File /system/xbin/su does not exist.
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
- For reference, i've also tried an app that required root (GMusicFS) but it tells me "Device is not rooted"
- I read up on the site how to use odin to remove the root but my current baseband doesn't match the baseband of the md5 files supplied as the end letters like MDL do not match with my own which are MF3. My fears are that i'll brick it, especially if it isn't necessary to do so given that my root went unsuccessful.
- Tried using the Updater to see if it tells me that my phone is up to date after attempting the root, but after being stuck on "contacting DM server" for a good 10 minutes and force closing it, it prompted me that the process was interrupted and that the phone was up to date. What worries me is that the updater may or may not be broken after the root attempt
General Questions:
- Is it necessary to unroot my phone given that there is no root present to begin with? or will there be any recurring problems if i don't do so?
- Is the updater to my phone broken because of the root attempt or is it something else?
- Will Odin brick my phone if i use it with the current files and should i wait until an mf3 file shows up if i need to unroot? (my common sense tells me that if i do it will brick it, but i want to get someone else's opinion on it if it's possible)
- Can i remove the superuser app manually and will it be safe if i do it?
- Did the root attempt on motochopper work to a certain point or did it not go through at all?
- When is it expected that we'll see a fix for the mf3 baseband and see a root program for it? I'm aware that it locks the bootloader too and some deeming it impossible at the moment but i'm just curious.
Any help to these questions is very much appreciated and if there's anything that i've missed to which you need more info on i'd be glad to respond.
You cant downgrade...once on mf3 your stuck, odin will instantly fail when trying ti flash if your on mf3. Lastly there is no current root methid for mf3...so you will just have to wait for a new exploit..
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
mg2195 said:
You cant downgrade...once on mf3 your stuck, odin will instantly fail when trying ti flash if your on mf3. Lastly there is no current root methid for mf3...so you will just have to wait for a new exploit..
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
Thank you for replying, i didn't know that about odin. So because of this it also means that nothing got changed except just adding the superuser apk on my phone then, right? Seeing that i can't even use odin and the root doesn't go through on mf3 anyway, i don't need to unroot for any reason or factory reset except if the root went through successfully and i wanted to remove it correct?
Is there still not a way to unroot when youre on mf3?
Zamdam1 said:
Is there still not a way to unroot when youre on mf3?
Click to expand...
Click to collapse
You should have super su on your phone. There is an unroot feature in it. Many have reported success unrooting with it.
http://forum.xda-developers.com/showthread.php?p=45301834
jd1639 said:
You should have super su on your phone. There is an unroot feature in it. Many have reported success unrooting with it.
Click to expand...
Click to collapse
Well, i removed supersu somehow.. i guess i should try this again and then try and use supersu to unroot it.
Why don'y you just read the information already available in this forum. Especially the "pinned" threads in 'General" and "Q & A" sections. Also read the threads with MF3 in the title. ALL of the questions you asked are answered in detail in those threads, plus you will learn a lot more about the phone while reading the threads. Good luck.
Read through this thread:
http://forum.xda-developers.com/showthread.php?t=2432876&page=2
scott14719 said:
Why don'y you just read the information already available in this forum. Especially the "pinned" threads in 'General" and "Q & A" sections. Also read the threads with MF3 in the title. ALL of the questions you asked are answered in detail in those threads, plus you will learn a lot more about the phone while reading the threads. Good luck.
Click to expand...
Click to collapse
I've read quite a lot actually, that's why i made this thread at the time mostly to clear some glaring concerns I had being new to this. Since then though the MF3 update was able to be rooted and most of my questions and concerns were answered. I appreciate the help.
skullstrider said:
I've read quite a lot actually, that's why i made this thread at the time mostly to clear some glaring concerns I had being new to this. Since then though the MF3 update was able to be rooted and most of my questions and concerns were answered. I appreciate the help.
Click to expand...
Click to collapse
Also notice SuperSU upgraded to 1.60. I noticed you posted an older version which may be incompatible with latest MF3 update. :S
In short motochopper rooting method DOES NOT work with MF3. I know a lot of people are tired of saying that but I'll be the one this time to remind you haha. But it looks like you figured that out and moved on to jortex's rooting method.
Just know there is no way to ODIN it back like on the old MDL update.
haremmon said:
Also notice SuperSU upgraded to 1.60. I noticed you posted an older version which may be incompatible with latest MF3 update. :S
In short motochopper rooting method DOES NOT work with MF3. I know a lot of people are tired of saying that but I'll be the one this time to remind you haha. But it looks like you figured that out and moved on to jortex's rooting method.
Just know there is no way to ODIN it back like on the old MDL update.
Click to expand...
Click to collapse
well.. for some reason the jortex method did reinstall supersu.. i used motochopper to install the superuser app. im guessing there is no unroot option in that app.. oh well. i will just keep it rooted until they release the fw for mf3..
Zamdam1 said:
well.. for some reason the jortex method did reinstall supersu.. i used motochopper to install the superuser app. im guessing there is no unroot option in that app.. oh well. i will just keep it rooted until they release the fw for mf3..
Click to expand...
Click to collapse
Are you trying to unroot? Try following this post I made on the other thread: http://forum.xda-developers.com/showpost.php?p=45340743&postcount=12
I wanted to root my phone so I can add more apps to the multiwindow feature. I downloaded samsung multi window manager, and I also downloaded superuser. Everything worked fine until I open superuser, asks me to update the superuser binary. I installed and it says "There was an error installing superuser. Please send a log of the error to the developer." Help please?
My phone is the AT&T S4, and pardon me if I don't know about much tech lingo, so please be very clear lol. It is my first time trying it. Thanks.
swimtech4me said:
I wanted to root my phone so I can add more apps to the multiwindow feature. I downloaded samsung multi window manager, and I also downloaded superuser. Everything worked fine until I open superuser, asks me to update the superuser binary. I installed and it says "There was an error installing superuser. Please send a log of the error to the developer." Help please?
My phone is the AT&T S4, and pardon me if I don't know about much tech lingo, so please be very clear lol. It is my first time trying it. Thanks.
Click to expand...
Click to collapse
You aren't rooted.
Just downloading and installing SuperUser does not root a phone.
See this -> http://forum.xda-developers.com/showthread.php?t=2419762
tech_head said:
You aren't rooted.
Just downloading and installing SuperUser does not root a phone.
See this -> http://forum.xda-developers.com/showthread.php?t=2419762
Click to expand...
Click to collapse
How do I know which of these models apply to me? I have the sgh i337
swimtech4me said:
How do I know which of these models apply to me? I have the sgh i337
Click to expand...
Click to collapse
Dude, your in the wrong forum. You don't have any of those devices you have an i337. Goto the att s4 forum
Edit. Read all of this http://forum.xda-developers.com/showthread.php?p=42320391
http://forum.xda-developers.com/showthread.php?t=2460626
This is a way easier method no SD card required.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
jd1639 said:
Dude, your in the wrong forum. You don't have any of those devices you have an i337. Goto the att s4 forum
Edit. Read all of this http://forum.xda-developers.com/showthread.php?p=42320391
Click to expand...
Click to collapse
On that same link it showed a video as an easy guide. The host downloaded the root checker while the one I downloaded was superuser. Is downloading the other one gonna interfere with the system?
swimtech4me said:
On that same link it showed a video as an easy guide. The host downloaded the root checker while the one I downloaded was superuser. Is downloading the other one gonna interfere with the system?
Click to expand...
Click to collapse
They're two different things. Root checker just checks if you have root. You need to root your device first. The kango root method seems to be the easiest. See the post and link just above yours by hovax
It worked!!
The Kingo Root proved to be much more beneficial and easier than going through all the steps! I'm so happy thanks to all of you for your help. :good::laugh:
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'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
Greetings,
My wife's S4 is on 4.2.2 (MF3) and it drives me nuts. I've been looking around the forums, but haven't found anything conclusive as to if there is a way to go from 4.2.2 to 4.4.2 and keep or reroot.
Normally I'd throw caution to the wind, close my eyes, and hit start... but, being that this is the wife's phone and that she is perfectly content with 4.2.2, the last thing I want to do is screw up her phone.
So I guess the question is: Does anyone know of a guide they can point me to that upgrades a rooted 4.2.2 to 4.4.2?
Thank you!
PS
I found this guide (http://forum.xda-developers.com/showthread.php?t=2728462), but it just seems strange that the thread was all but ignored, so there is no feedback from users/testers.
You can upgrade to 4.4.2, but you don't keep root. You'll have to re-root it. And you have to use Odin which means you'll wipe the phone. If it was my wife's phone I wouldn't want to put up with the complaining of having to setup everything again.
Sent from my Nexus 5 using XDA Free mobile app
tarikakleh said:
Greetings,
My wife's S4 is on 4.2.2 (MF3) and it drives me nuts. I've been looking around the forums, but haven't found anything conclusive as to if there is a way to go from 4.2.2 to 4.4.2 and keep or reroot.
Normally I'd throw caution to the wind, close my eyes, and hit start... but, being that this is the wife's phone and that she is perfectly content with 4.2.2, the last thing I want to do is screw up her phone.
So I guess the question is: Does anyone know of a guide they can point me to that upgrades a rooted 4.2.2 to 4.4.2?
Thank you!
PS
I found this guide (http://forum.xda-developers.com/showthread.php?t=2728462), but it just seems strange that the thread was all but ignored, so there is no feedback from users/testers.
Click to expand...
Click to collapse
You can first unroot then go to settings---->more----->about device----> software update and take the OTA to MK2. Once on MK2 take the OTA to NB1, then to NC1, then re-root using towelroot: http://forum.xda-developers.com/showthread.php?t=2783157
The above process will leave your current set-up intact and rooted.
muniz_ri said:
You can first unroot then go to settings---->more----->about device----> software update and take the OTA to MK2. Once on MK2 take the OTA to NB1, then to NC1, then re-root using towelroot: http://forum.xda-developers.com/showthread.php?t=2783157
The above process will leave your current set-up intact and rooted.
Click to expand...
Click to collapse
Would this method be the best way to unroot, starting with step 2 in my case since I still have root...or is there a different route I can take?
Originally Posted by ou812bkewl
So, here is what I did and what you must do:
1. Re-root again using the same method you did before for MF3, then:
--a) Reboot, update SuperSU app and it's binary
--b) Reboot again, verify device status is back to"Official"
--c) Reboot again, verifying that, this time, the boot screen is back to normal again
2. Download a file manager app in the Play Store called "Total Commander" and enable "Root functions everywhere" in its settings.
3. Navigate to a folder called "/system/xbin"
4. Delete ONLY files in that folder with the word "busybox" within its filename or symlink path. You should end up with three files left. I did. Two of them are SuperSU related. DO NOT DELETE ANY OF THEM!
5.Open SuperSU and, in its settings, select the "Full un-root" option. Once SuperSU closes, reboot.
When you reboot, wait a full minute and check on device status. It should still say "Official" and you will be fully un-rooted.
Why does it stay "Official" with Busybox present ONLY when SuperSU's most recently updated apk and binary are present? I have no clue... But I hope this helps you out.
Click to expand...
Click to collapse