Related
I really don't understand this phone. I've been on a quest of 2 weeks to be rooted and on official status, finally i gave up everything because i was not able to have both. Finally i flashed factory rom through odin, formated a couple of time the phone, and i got back official status. I much rather gave up a few rooting benefits then OTAs, at least until they fix the phone's problems.
Well, this morning, i wake up, and that DAMN custom status is back....WHY????????? I'm not rooted, i'm 100% stock, i checked with rootchecker and my phone doesnt have root....then why does that damn status keep coming back??? There is obviously something else that triggers it......man i'm so deperate! Please help!
polish_pat said:
I really don't understand this phone. I've been on a quest of 2 weeks to be rooted and on official status, finally i gave up everything because i was not able to have both. Finally i flashed factory rom through odin, formated a couple of time the phone, and i got back official status. I much rather gave up a few rooting benefits then OTAs, at least until they fix the phone's problems.
Well, this morning, i wake up, and that DAMN custom status is back....WHY????????? I'm not rooted, i'm 100% stock, i checked with rootchecker and my phone doesnt have root....then why does that damn status keep coming back??? There is obviously something else that triggers it......man i'm so deperate! Please help!
Click to expand...
Click to collapse
It's really not as big of a deal as you are making it. The way I see it you have 2 choices.
1. Exchange the phone for another (that might do the same thing)
2. Ignore it.
Just like every other Galaxy phone out there (you remember the skyrockets, right?) not all of them react the same way. Some get custom, some do not. Others switch back and forth.
I've noticed you have made many posts about this same thing. If someone hasn't provided a concrete answer that has worked for you by now it just doesn't exist yet. No matter how frustrated you are over it, making new posts about it are not going to change anything.
Its up to you if you keep wanting to post about it (I'm not complaining about it), I just don't think it's going to get you any more information at this point than what already has been said. Maybe I am wrong and someone will tell you exactly what to do to make it "official", but I haven't seen anything yet.
Good luck and try not to let it get to you so much.
euhhh no, they are not about the same thing, one was about retaining officiel while rooted, and now that i've given up on that, i still have a custom status, the reson why i dont report there is becuase poeple have seen the thread and will not go back, so in order to attract new poster i create a new thread. And no, i dont want to ignore anything because i want OTAs. If you have a problem with that, dont answer
You need to re-root (motochopper method) and then using a file browser such as "root explorer" go to:
/System/Xbin
Once you have navigated to the above path, delete these two files:
"su" and " busybox"
Once you've deleted the two files, uninstall SuperSU and reboot your phone twice.
You'll notice that after the second reboot the "custom" will revert back to "official"
Sent from my SGH-I337M using Tapatalk 2
peoples_flip said:
You need to re-root (motochopper method) and then using a file browser such as "root explorer" go to:
/System/Xbin
Once you have navigated to the above path, delete these two files:
"su" and " busybox"
Once you've deleted the two files, uninstall SuperSU and reboot your phone twice.
You'll notice that after the second reboot the "custom" will revert back to "official"
Sent from my SGH-I337M using Tapatalk 2
Click to expand...
Click to collapse
correct me if i'm wrong but these 2 files, should not even exist if you install a firmware thru odin and format the phone a few times...
I went through what you have, I completed a full stock restore via Odin and these two files I mentioned were still there. Use a file explorer and go to the path I suggested and you'll see them there
Sent from my SGH-I337M using Tapatalk 2
polish_pat said:
correct me if i'm wrong but these 2 files, should not even exist if you install a firmware thru odin and format the phone a few times...
Click to expand...
Click to collapse
I don't believe the current Odin contains a pit...or whatever it is that formats the phone...
So all Odin is going to do is reinstall everything...so replace missing or corrupted files - it will not delete your new files
Formating from the phone itself won't delete everything...its just going to delete your apps, app data, and cache
Therefore doing multiple factory resets and odins likely will not remove all traces of root...someone correct me if I'm wrong but that's what I believe is the case...
Sent from my HTC PH39100 using Tapatalk 2
Is there a reason why it showing custom is a bad thing?
Sent from my SAMSUNG-SGH-I337 using xda premium
XGhozt said:
Is there a reason why it showing custom is a bad thing?
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
AT&T software update push or download will not work for your phone if it is showing custom. People like to be getting these stock updates as soon as they are published by the provider, not when some good heart packages a new ROM using them.
polish_pat said:
correct me if i'm wrong but these 2 files, should not even exist if you install a firmware thru odin and format the phone a few times...
Click to expand...
Click to collapse
Good info here, I did this procedure as you described, and yes, official is showing, but you can NOT delete su, it will unroot. I just renamed the 2 files, and root was gone. renamed su back, re-installed su superuser, and reboot, root is back with official status.
Thanks.
TheAxman said:
Good info here, I did this procedure as you described, and yes, official is showing, but you can NOT delete su, it will unroot. I just renamed the 2 files, and root was gone. renamed su back, re-installed su superuser, and reboot, root is back with official status.
Click to expand...
Click to collapse
I tried this procedure and still have custom after 2 reboots. I renamed su and busybox then verified root was gone. Then renamed su back. I guess the part I was confused at was reinstall super user. Do I uninstall then re-install from play store?
Thank you.
EDIT: Followed my thought of uninstalling and re-installing through play store and still get custom.
CAG-man said:
I tried this procedure and still have custom after 2 reboots. I renamed su and busybox then verified root was gone. Then renamed su back. I guess the part I was confused at was reinstall super user. Do I uninstall then re-install from play store?
Thank you.
EDIT: Followed my thought of uninstalling and re-installing through play store and still get custom.
Click to expand...
Click to collapse
Same here
CAG-man said:
I tried this procedure and still have custom after 2 reboots. I renamed su and busybox then verified root was gone. Then renamed su back. I guess the part I was confused at was reinstall super user. Do I uninstall then re-install from play store?
Thank you.
EDIT: Followed my thought of uninstalling and re-installing through play store and still get custom.
Click to expand...
Click to collapse
Correct. the one from the playstore updates the binaries. then uninstall.
---------- Post added at 07:11 PM ---------- Previous post was at 07:10 PM ----------
XGhozt said:
Is there a reason why it showing custom is a bad thing?
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
Good answer, why does it matter if it says custom? whats the big deal here. If you are wanting the update, why not just wait until a dev does what they need to do to it, and flash it later. I updated 1 time in a year on my GS3, and never did it again. When a new rom is developed, it usually is a base from the update...so....
Had a posting. Could not delete
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Did some digging in the forums and I am rooted with OFFICIAL.
This is how to do it. Taken from this thread.
http://forum.xda-developers.com/showthread.php?t=2252248&page=42
Mr. Q said:
Well, you do not have to install the ZIP, but instead, do the following:
- Install SuperSU from the market
- Grant SuperSU root access
- When asked to update su-binary, please do
- Remove SuperUser from your device
- Reboot (I read two reboots are needed to make the icon disappear again.)
Click to expand...
Click to collapse
My process completely.
Remove Busybox from system/xbin (or your busybox backup)
Install SuperSU by Chainfire from playstore.
Open SuperSU and Grant SU root
Update the binary
Say yes to try to remove other root apps. This will remove superuser.
reboot
reboot
On second reboot you will notice the Galaxy S4 logo returns and Official Status has returned.
If it has not returned then some other issue is causing the custom status.
CAG-man said:
Did some digging in the forums and I am rooted with OFFICIAL.
This is how to do it. Taken from this thread.
http://forum.xda-developers.com/showthread.php?t=2252248&page=42
My process completely.
Remove Busybox from system/xbin (or your busybox backup)
Install SuperSU by Chainfire from playstore.
Open SuperSU and Grant SU root
Update the binary
Say yes to try to remove other root apps. This will remove superuser.
reboot
reboot
On second reboot you will notice the Galaxy S4 logo returns and Official Status has returned.
If it has not returned then some other issue is causing the custom status.
Click to expand...
Click to collapse
I was able to get official and root, the problem is it comes back after 2-3 days, please report back on sturday and tell me if its still official, also this logo you are talking about, i never see it because im in canada and my bootloader is unlocked already
EDIT: Ok, so once i was rooted and installed SuperSU and got superuser out, i deleted busybox, i then rebooted ONCE and got official just like that. I also took out SD card because i know this screwed me up last time. I'm happy because i'm rooted and official, but i'm not convinced this will last very long because it has never lasted more than 2 days. I will report back in a few days. Thanks Cagman, you've been very helpful and what you told me to do did the best results for me, i just hope they last
so far so good!!!:fingers-crossed:
polish_pat said:
so far so good!!!:fingers-crossed:
Click to expand...
Click to collapse
Try rebooting a few more times.
For about a week i was getting the custom status every 2nd or 3rd reboot, and then eventually it just went away...
joeybear23 said:
Try rebooting a few more times.
For about a week i was getting the custom status every 2nd or 3rd reboot, and then eventually it just went away...
Click to expand...
Click to collapse
Hahaha, i did it!! earlier this afternoon i sort of challenged my phone by rebooting it constantly, ive rebboted probbaly 20-30 times and its still official, i guess deleting busybox sealed the deal!!
Polish_pat I am glad I was able to help. You are welcome. Congratulations.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Ok so my SGH-I337 S4 is rooted using Motochopper and is still stock ROM, just rooted. I did it so I could make Google Wallet work on AT&T, which was successful. Now AT&T has an OTA update that I want. So I will have to unroot. I already have the stock ROM download that I can flash via Odin to unroot. But what will happen to the apps I have installed that require root, like Titanium Backup, ROM manager, etc. Will they automatically be removed or just stop working? Also, has anyone had any experience with the Universal Unroot app? That would sure be easier. But my main question remains: what does Unrooting do to apps that are installed that require root privileges?
Sent from my SGH-I337 using Tapatalk 4
When you user Odin you'll have to do a factory reset or you'll get into a boot loop. So by by apps. Your tibu backup file will still be there, but just in case copy it to your pc before hand. The apps that require root will not work until you re-root.
Hi highly recommend you don't get the ota. Even though it's root able it's very dangerous to do so.
What I will say, if you want the update is to go here http://forum.xda-developers.com/showthread.php?p=43963746 and you will have the benefit of the OTA and not lose the root and custom recovery, and all the app will work! You will not upgrade the bootloader. Once you updated the bootloader is not coming back!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
I don't understand why you get a boot loop. I once soft bricked a phone and used Odin to flash a md5.tar of a stock ROM. The phone rebooted and I saw my wallpaper and all my apps and data intact. I have seen threads on Unrooting that describe using Odin that way. They all said that doing a factory reset afterword is if you want to delete all your apps and data like if you sell your phone or just want it as it was out of the box
Sent from my SGH-I337 using Tapatalk 4
feetr2c said:
I don't understand why you get a boot loop. I once soft bricked a phone and used Odin to flash a md5.tar of a stock ROM. The phone rebooted and I saw my wallpaper and all my apps and data intact. I have seen threads on Unrooting that describe using Odin that way. They all said that doing a factory reset afterword is if you want to delete all your apps and data like if you sell your phone or just want it as it was out of the box
Sent from my SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
what device were you using?
That was my S3
Sent from my SGH-I337 using Tapatalk 4
feetr2c said:
That was my S3
Sent from my SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
thats interesting. were you on stock when you soft bricked it?
many, many...many users commonly have to wipe data/factory reset after flashing stock via odin. sometimes they can get away with just a cache wipe. not often, though.
I had used (can't remember his name) Galaxy S3 Toolkit to root the phone. Interestingly, Root Checker said I was rooted, but Titanium Backup wouldn't install... It said I needed root access... Hmmm.... Later when I went to unroot using the same S3 Toolkit, I did something wrong. The phone would boot but stick at tiny little letters in the upper left of the screen that I *think* said recover. I messaged the developer of the Toolkit and he sent me a link to download the original AT&T stock ROM. He told me how to use Odin and check the PDA box. I did it and it fixed my phone.
Sent from my SGH-I337 using Tapatalk 4
I had rooted my S3 using the Galaxy S3 Toolkit by (can't remember his name). Interestingly enough, Root Checker said I was rooted but yet Titanium Backup wouldn't install... Said it needed root access... Hmmm.... When I tried to unroot using the Toolkit, I did something wrong and the phone rebooted with little Teeny letters in the upper left corner of the screen that I *think* said recover. I messaged the developer of the Toolkit and he sent me a link to the AT&T stock ROM. He told me how to use Odin and check the PDA box. I did and it fixed my phone
Sent from my SGH-I337 using Tapatalk 4
thats why i asked if you were still on stock when you used odin. most users are not, which is ultimately what requires them to factory reset in recovery.
I wonder if universal unroot is trustworthy
Sent from my SGH-I337 using Tapatalk 4
All that would happen to your rooted apps is they wouldn't have root privileges anymore, which means they ultimately won't work as expected. I would recommend uninstalling them before you update. You may also be able to do a full unroot via SuperSU or one of the other superuser apps.
NOTE: Your phone may not update even after unrooting. You may have to do a factory reset first. I don't know why, I'm not a developer. I'm just speaking out of my own experience from the past.
Has anyone tried this method? SuperSU has a full unroot option in its settings. I have read many posts saying it is impossible to unroot at this time.
I did a little searching around and didn't find much. Just suggestions to try it and no one ever reported back if it works or doesn't.
I personally don't have the OTA and have a custom ROM, but i would like to know any confirmation of it working or not working by anyone that has tried it.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
I did the ota to mf3 and successfully rooted it I then realized that I had like 6gbs missing so in an effort to restore I went into the SU settings and chose the remove root option and it seemed to work I checked with root checker and I no longer had root access I still was unable to restore it just bumps me into Odin mode and I have to boot power+home+volume- then cancel to reboot my phone into working order
But as far as I can tell I have no root
Since I can't restore and try and clear up my missing storage I wanted to take it in and try and get a new one under warranty but I'm afraid to use triangle away so I'm just gonna wait it out until we get a mf3 restore firmware for Odin since my phone works fine for now
Sent from my SAMSUNG-SGH-I337 using xda premium
So that is 1 confirmation for an unroot. Basically hit unroot, it sends the phone to bootloop. Remove battery, put it back, then boot to download mode with power+volume down, then hit volume down again to cancel and reboot to a fully functional phone with no root. If that doesn't work, use power+home+volume down. Anyone else?
Btw,
Don't use triangle away. It flashes a temporary recovery to reset the binary. It will brick you or just fail.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
graydiggy said:
Has anyone tried this method? SuperSU has a full unroot option in its settings.
Click to expand...
Click to collapse
I fully un-rooted using the method in my post here - http://forum.xda-developers.com/showthread.php?p=44495559 . For me, it just threw the custom-lock icon boot up screen and showed "Custom" status in the "About Phone" menu when using the SuperSU's un-root method.
The problem was busy box. The MF3 root scripts install Busybox files into the /xbin directory, but SuperSU's "full unroot" doesn't touch Busybox's files. Not even any Busybox apps can remove those files.
So delete the busybox files first, then unroot. That is 2 confirmed unroots.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
ou812bkewl said:
I fully un-rooted using the method in my post here - http://forum.xda-developers.com/showthread.php?p=44495559 . For me, it just threw the custom-lock icon boot up screen and showed "Custom" status in the "About Phone" menu when using the SuperSU's un-root method.
The problem was busy box. The MF3 root scripts install Busybox files into the /xbin directory, but SuperSU's "full unroot" doesn't touch Busybox's files. Not even any Busybox apps can remove those files.
Click to expand...
Click to collapse
graydiggy said:
So delete the busybox files first, then unroot. That is 2 confirmed unroots.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This method also worked for me as well. Had no problems following the steps.
3 confirmed
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
graydiggy said:
3 confirmed
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Good info to know. Thanks graydiggy
I am going to change this to a how to thread later today. Anyone else try it?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
this may be a stupid question, but if you went through the trouble of rooting after the mf3 update.. why would you want to unroot?
Warranty replacement in case of a hardware issue, testing purposes, also, some people only want a temp root to remove bloat. After that, they don't want root anymore.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
So to summarize the steps from what I've read on rooting & unrooting MF3:
Root:
Use this guide by jortex: http://forum.xda-developers.com/showthread.php?t=2387577&highlight=mf3
Unroot: http://forum.xda-developers.com/showpost.php?p=44495559&postcount=39
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.
Click to expand...
Click to collapse
Follow step 1 if not rooted or messed up somewhere during unrooting process.
Just double checking step 2: We can use es file explorer with root explorer option as well correct?
Also I noticed superSU got updated today:
http://forum.xda-developers.com/showthread.php?t=1538053
05.09.2013 - v1.60
- Added SELinux+Enforcing compatibility (for new SGS4 ROMs)
- Fixed (newest) CWM versions asking you question that break root if answered wrongly
- Fixed issue with the TWRP/CWM binary installer
- Fixed 4.3 OTA survival looping
Click to expand...
Click to collapse
Does the new update have something to do with our mf3 baseband like SELinux?
haremmon said:
So to summarize the steps from what I've read on rooting & unrooting MF3:
Root:
Use this guide by jortex: http://forum.xda-developers.com/showthread.php?t=2387577&highlight=mf3
Unroot: http://forum.xda-developers.com/showpost.php?p=44495559&postcount=39
Follow step 1 if not rooted or messed up somewhere during unrooting process.
Just double checking step 2: We can use es file explorer with root explorer option as well correct?
Also I noticed superSU got updated today:
http://forum.xda-developers.com/showthread.php?t=1538053
Does the new update have something to do with our mf3 baseband like SELinux?
Click to expand...
Click to collapse
This worked for me! But I skipped all the steps in the beginning. They sounded useless to me. Rerouting to unroot? Hah
I deleted all busybox files and was left with 3 files then went to SuperSU and did the full unroot and restart.
I check with root checker and installed SuperSU as well. Root checker said I have no root and SuperSU fails. Status is official.
Going to restart a few times to be sure.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
WezzleD said:
This worked for me! But I skipped all the steps in the beginning. They sounded useless to me. Rerouting to unroot? Hah
I deleted all busybox files and was left with 3 files then went to SuperSU and did the full unroot and restart.
I check with root checker and installed SuperSU as well. Root checker said I have no root and SuperSU fails. Status is official.
Going to restart a few times to be sure.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Nice! Thank you. Looks like 4 confirmed. Also, was SuperSU on v1.60?
haremmon said:
Nice! Thank you. Looks like 4 confirmed. Also, was SuperSU on v1.60?
Click to expand...
Click to collapse
I'm actually not sure. Didn't look at version numbers.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
4 confirmed. Let's get 5 and I will post a how to.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
ou812bkewl said:
I fully un-rooted using the method in my post here - http://forum.xda-developers.com/showthread.php?p=44495559 . For me, it just threw the custom-lock icon boot up screen and showed "Custom" status in the "About Phone" menu when using the SuperSU's un-root method.
The problem was busy box. The MF3 root scripts install Busybox files into the /xbin directory, but SuperSU's "full unroot" doesn't touch Busybox's files. Not even any Busybox apps can remove those files.
Click to expand...
Click to collapse
That method worked for me also. I'm so glad it was discovered. Successfully unrooted.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
5!
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
graydiggy said:
5!
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I was able to unlock as well. However my phone stopped showing the custom unlocked symbol at bootup a few days ago (before doing this) and I am at a loss as to why. So I am not sure I can count as a real confirmation.
I did your unroot process, root checker confirms I no longer have root and the unlock symbol has not come back.
Stay tuned guys. Getting everything ready to quickly make a more organized how to.
Being horribly sick is not helping
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
For those who have taken the MJ7 update and realized that you can't regain root. Kingo is working on a solution. Verizon likes to lock their loaders so it takes a little time to break them. I had to take my note to a Best Buy store about an hour from where I live to have them reset my phone from what is being labeled a Softbrick. If anyone knows a way to root the SM-900V with MJ7 please let me know.
Thanks,
GoNavyMike
I took the update a week ago and just rooted with kingo yesterday..all I did was follow instructions withing the app and was rooted minutes later . ... Installed safe strap with beans on slot 2..all is well except I can't get the custom logo to go away from the boot up screen but I don't really care
Sent from my SM-N900V using Tapatalk
I have no idea why people claim kingo doesn't work. It works fine, I and many others have used it on newest update without issue. Also, this isn't development.
Sent from my SM-N900V using xda app-developers app
custom logo
gcforreal said:
I took the update a week ago and just rooted with kingo yesterday..all I did was follow instructions withing the app and was rooted minutes later . ... Installed safe strap with beans on slot 2..all is well except I can't get the custom logo to go away from the boot up screen but I don't really care
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
If you run Triangle Away app, from App Store, it will get rid of custom lock logo on boot up screen
GoNavyMike said:
For those who have taken the MJ7 update and realized that you can't regain root. Kingo is working on a solution. Verizon likes to lock their loaders so it takes a little time to break them. I had to take my note to a Best Buy store about an hour from where I live to have them reset my phone from what is being labeled a Softbrick. If anyone knows a way to root the SM-900V with MJ7 please let me know.
Thanks,
GoNavyMike
Click to expand...
Click to collapse
The Kingo does work for the Verizon Note 3. I literally just did it. At first, it kept saying not supported, but I tried it again with my screen timeout off and I saw that when my phone was connected to Kingo, something popped up warning me something was trying to exploit my phone, click on the box and hit install. Then not long after that your phone will reboot and grant permission stuff will come up. You can either do it this way, or under security uncheck verify apps located under unknown sources.
So on the kingo screen,when selecting the OS mine only goes up to 4.2.2. I am obviously running 4.3 on the note 3. Do I pull the trigger? Or am I missing an update?
Sent from my SM-N900V using Tapatalk
mtnbst said:
So on the kingo screen,when selecting the OS mine only goes up to 4.2.2. I am obviously running 4.3 on the note 3. Do I pull the trigger? Or am I missing an update?
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Worked for me and mine said the same thing. "4.2.2" Took me a couple minutes or so and all is good!
I have been hung up on "waiting for device" (after fetching scripts) for about 10 minutes now. Wondering when I should pull the plug. ...
It's a no go... Maybe because it's VZ?
Sent from my SM-N900V using Tapatalk
Kingo works for mj7, if you get hung up on waiting for device, close the kingo app restart computer, open kingo, plug phone into a different usb port.
Sent from my SM-N900V using Xparent Green Tapatalk 2
YES guys, you can root your phone VIA Kingo even if you updated to the newer firmware. My scenario, got my N3 bone stock, rooted it on MJ9 via kingo and worked. Applied OTA update to version to MJ7 and lost root. Used kingo again and gained root. Works totally fine and SS works fine as well.
Still nothing. .I am running win 8 through VM firmware. I wonder if that's my prob. I get all the way to the last step and it hangs. I rooted my Galaxy nexus with this virtual win machine. I might have to borrow a windows laptop
Sent from my SM-N900V using Tapatalk
Kingo
Does anyone have a link to Kingo. I can't get mine to go in Odin, I click to import the file, hit start, and it doesn't do anything. Does the De la Vega file have to be renamed? I'm usually pretty good at getting these things rooted, this seems to be dealing me fits. I NEED ROOT lol
Other issue is that 7zip will not extract the de la Vega file, says it can't open as a archive
Why is this thread so long? Kingo works with MJ7. Nuff said. If the OP would of read the Verizon Note 3 threads for 10-15 minutes he/she would of found this out.
It works for most. I am not most
Sent from my SM-N900V using Tapatalk
mtnbst said:
Still nothing. .I am running win 8 through VM firmware. I wonder if that's my prob. I get all the way to the last step and it hangs. I rooted my Galaxy nexus with this virtual win machine. I might have to borrow a windows laptop
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
VM could definitely be part of your problem, especially if you do not have Internet access through it. USB connections can sometimes be flaky as well.
musicman625 said:
Does anyone have a link to Kingo. I can't get mine to go in Odin, I click to import the file, hit start, and it doesn't do anything. Does the De la Vega file have to be renamed? I'm usually pretty good at getting these things rooted, this seems to be dealing me fits. I NEED ROOT lol
Other issue is that 7zip will not extract the de la Vega file, says it can't open as a archive
Click to expand...
Click to collapse
RDLV does not work on MJ7, unless they have released an update.
http://lmgtfy.com/?q=kingo+root
Sent from my SM-N900V using Tapatalk
I have Internet through it. .. But the USB connection is extremely flakey. I wonder if I try 100 times. .. It's bound to take
Edit: Using the original USB cable for my galaxy nexus gets me 95% through the process vs 50% through the process with the Note 3 cable.
Siiiiiigh,
perhaps my nexus 7 cable will be the ticket...
This will be my first android device that does not have root privileges. $#%@
Sent from my SM-N900V using Tapatalk
The kingo app will do it, make take a few tries and you'll probably have to do it from an actual Windows PC, but it should work. I'd probably try to use a USB 2.0 port rather than a 3.0, if possible.
Sent from my SM-N900V using Tapatalk
Thanks, I won't have access to a PC for a few weeks. I will patiently wait
Sent from my SM-N900V using Tapatalk
Kingo does work. I tried literally 40 times no luck on new ota. Battery pull took out sd card rebooted. First try rooted.
Sent from my SM-N900V using Tapatalk
Ahhh, so there is hope! As soon as I get home I'm trying. Fingers crossed
Nope, tried all that. .. Nothing
Edit: I think Im on at least my 85th attempt...battery pulls, SD pulls computer reboots, different usb cables (note 3 cable is the least effective) Im even alternating USB inputs. anything I'm leaving out?
Sent from my SM-N900V using Tapatalk
I'm interested in the new ROMs that are out but before I start playing I want to have my odin and root steps up to date. I notice that there have been several folks have had kingo fail and have had to use vroot. Is this the standard to use now? Just want to be sure I'm doing this correctly.
I'm on the current baseband and kernel, if that helps.
Thanks in advance.
Oh_wow said:
I'm interested in the new ROMs that are out but before I start playing I want to have my odin and root steps up to date. I notice that there have been several folks have had kingo fail and have had to use vroot. Is this the standard to use now? Just want to be sure I'm doing this correctly.
I'm on the current baseband and kernel, if that helps.
Thanks in advance.
Click to expand...
Click to collapse
I am one of the folks who had to use Vroot. I would try Kingo first and if that does not work then switch to Vroot.
oconnell84 said:
I am one of the folks who had to use Vroot. I would try Kingo first and if that does not work then switch to Vroot.
Click to expand...
Click to collapse
Great! Thanks for the quick reply!
I tried everything under the sun to get kingo to work and it never did. I went to vroot and it worked first try
Sent from my SM-N900V using Tapatalk
I used vroot about a week ago. Super easy, took maybe 30 seconds, and my knox WAS NOT tripped. I couldn't be happier.
Kevins89notch said:
I used vroot about a week ago. Super easy, took maybe 30 seconds, and my knox WAS NOT tripped. I couldn't be happier.
Click to expand...
Click to collapse
Are you using the chinese super user app?
Sent from my SM-N900V using Tapatalk 2
I used Vroot the other day to re root my phone after a reset and replaced the Chinese superuser with Chainfires supersu. You can install it either via Playstore or flash it in safestrap witch I prefer. Also be sure to uninstall whatever other Chinese app gets installed. I have no idea what it is because I can't read it. As a added precaution I also removed my sim card during root. As for Kingo It didn't work for me but there is activity on their twitter account.
recDNA said:
Are you using the chinese super user app?
Sent from my SM-N900V using Tapatalk 2
Click to expand...
Click to collapse
No, right away I installed the proper english version, and then deleted the chinese one.
Just tried Kingo and it's working again.
Misterxtc said:
I used Vroot the other day to re root my phone after a reset and replaced the Chinese superuser with Chainfires supersu. You can install it either via Playstore or flash it in safestrap witch I prefer. Also be sure to uninstall whatever other Chinese app gets installed. I have no idea what it is because I can't read it. As a added precaution I also removed my sim card during root. As for Kingo It didn't work for me but there is activity on their twitter account.
Click to expand...
Click to collapse
Removing the simm card during root sounds like a great idea.
Sent from my SM-N900V using Tapatalk 2
---------- Post added at 09:40 AM ---------- Previous post was at 09:38 AM ----------
Misterxtc said:
I used Vroot the other day to re root my phone after a reset and replaced the Chinese superuser with Chainfires supersu. You can install it either via Playstore or flash it in safestrap witch I prefer. Also be sure to uninstall whatever other Chinese app gets installed. I have no idea what it is because I can't read it. As a added precaution I also removed my sim card during root. As for Kingo It didn't work for me but there is activity on their twitter account.
Click to expand...
Click to collapse
I miss the good old days when there would be a separate thread for each rooting process with suggestions and questions. Now it's search here, search there, search everywhere!
Sent from my SM-N900V using Tapatalk 2
Turmin said:
Thank you.
Click to expand...
Click to collapse
Your welcome. It did take a few tries but it went. Be sure to update supersu when you finish, Kingo is out of date a couple of versions.
I tried 1000000 times last night and it did not work. I used Vroot and it worked great. But remember to do I factory reset to get rid of all the bad crap it loads.
Sent from my SM-N900P using Tapatalk
NissanNick said:
I tried 1000000 times last night and it did not work. I used Vroot and it worked great. But remember to do I factory reset to get rid of all the bad crap it loads.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
They must have just got Kingo working because I used it twice today. The second time worked on the first try. I tried it a second time after a full Oden reset just to make sure. Had some extra time today to play around.
Misterxtc said:
They must have just got Kingo working because I used it twice today. The second time worked on the first try. I tried it a second time after a full Oden reset just to make sure. Had some extra time today to play around.
Click to expand...
Click to collapse
What firmware are you on? MJE?
Sent from my SM-N900V using Tapatalk
Yes, MJE.
Misterxtc said:
Yes, MJE.
Click to expand...
Click to collapse
Worked for me too with MJE. Used USB 3.0 cable in USB 3.0 mode MTP. Prior to that failed in ODIN mode and in MTP mode without USB 3.0. But may be just random luck. Now have Supersu app.
Questions:
1. Should I use that Supersu or change. Looks like same old Supersu, but the version with yellow superman shield and red # sign.
2. Also, it asks if I want to disable Knox. Should I do that? Does that risk tripping know counter?
Sent from my SM-N900V using Tapatalk
yearn2burn said:
Worked for me too with MJE. Used USB 3.0 cable in USB 3.0 mode MTP. Prior to that failed in ODIN mode and in MTP mode without USB 3.0. But may be just random luck. Now have Supersu app.
Questions:
1. Should I use that Supersu or change. Looks like same old Supersu, but the version with yellow superman shield and red # sign.
2. Also, it asks if I want to disable Knox. Should I do that? Does that risk tripping know counter?
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Keep supersu but update it to the current v1.93 either by Play Store or flashing in safestrap and yes disable Knox it will not trip the counter. Enjoy.
Yes K works even though it says it fails. I posted my experience back on Feb 3 in another similar thread or look via my profile. In short it will say that it failed but su app shows up and use a root checker to verify. Removal of sd card and pulling and replacing the sim card before root might help. Also watch you phone for a security permission to add an app. I sat an extra five minutes before realizing it.
danthepunman said:
Yes K works even though it says it fails. I posted my experience back on Feb 3 in another similar thread In short it will say that it failed but su app shows up and use a root checker to verify.
Click to expand...
Click to collapse
For me it realized it succeeded.
Sent from my SM-N900V using Tapatalk