EDIT: Apologies, I've just noticed I've posted this in the wrong section - though not sure how to move it!?!
Hi all, I’m in need of some help!
I recently rooted my N7100, using CF Auto root – great instructions, easy to follow, and it rooted perfectly
All was good, except that it would not of course, run SkyGo. After downloading voodoo and superuser, I managed to get the phone to temporarily disable root, but Sky Go still wouldn’t work. So, I un rooted, and Sky Go worked - and then re-rooted, with the aim of trying to temporarily disable root again.
Noooooow, my binary su counter has gone to 3, root checker says it’s not properly rooted, Sky Go won’t work because it says it IS rooted, Titanium Backup and Triangle Away won’t work because they say it’s not rooted – and I’m stuck!
Tried re-rooting yet again, via the same method, and it seems to work, but again, root checker says it’s not rooted ‘properly’, and no apps requiring root will work. Also, in spite of supersuer and superSU not being installed (as far as I can see anyway), superSU doesn’t get installed during the root process, as it did the first time I did it.
I seem to be stuck on some sort of root limbo – does anyone have any ideas?
Thanks for reading.
You might want to try the megawipe option from zoot's wipe script you will need to flash clockworkmod though. Hope I helped you out! Good luck
Sent from my GT-N7100 using xda app-developers app
Flash a rooted recovery using Odin. then flash a rooted rom. good set of instructions can be found here along with a video
http://galaxynote2root.com/galaxy-note-2-root/how-to-root-galaxy-note-2-easiest-method/
Related
I just performed the manual root on the HTC Thunderbolt. I was able to get all the way to Step 9 without any problems. Downloaded Superuser and ROM Manager and successfully flashed ClockworkMod Recovery (CWM).
How can I confirm whether or not the root was successful?
Now I am trying to use Titanium Backup and it says that it cannot obtain root access?
I remember one hiccup in the rooting process. When I was on step 6, I typed adb reboot bootloader. As it was flashing the ROM PG05IMG.zip, it had that list of 9 parameters. I don't remember what all of the were called. However, I got OK on all of them except for the 7th or 8th parameter (I think it was tp). Instead of OK, it got BYPASS.
Is that a problem?
With assistance from #andirc, I figured this out.
I had root access the entire time.
Using Titanium Backup, it asked for BusyBox. That was the problem. I simply went to the Market, downloaded and installed busybox. Then Titaniumbackup worked.
Checking root access is done simply by going to the market and downloading root checker.
I answer my own questions in threads just in case anyone else runs along this problem in the future and needs help! Otherwise, this thread can be deleted.
Hey All,
I posted a question the other day that nobody got to... no worries.
I have obtained a full root. I have SU and have root apps running like TiBu, SetCPU and others and they work fine. I have root, I just can't get CWM.
I used this link at first to get both root and CWM. Like I said... root worked fine, CWM not so much. I have tried several times following those same steps to flash the cwm again and again but I only end up with an Android with an exclamation point.
I also tried a second computer running the same steps -- same results.
What I'm wondering now -- Can I use this other guide and instead of following the full guide, I skip to the CWM part. I should not have any problems with that, correct? The first part is getting temp root and the last part is full root. I already have full root, so can I skip to the CWM?
Or does anyone else have ideas?
Thank you!
I'm not that knowledgable about all of this stuff, I tried that method last night to try to root my phone and like others get stuck at the point where its dl the volds. I think this method was built for hc 3.0 and 3.01.
It won't hurt to give it a try though.
I just wish i could get root. To me this thing is a nightmare to hack. I managed to get my atrix rooted with cwm, unlocked with a custom rom, and this tab is tougher for me to crack.
Best of luck to you.
Sent from my Transformer TF101 using XDA Premium App
Apologize in advance if this is intuitively obvious to other but after searching and reading a better part of the day, I can't figure it out...
In any case...I rooted my 4.1.2 phone a while back with the casual root. Didn't unlock the bootloader or install a custom recovery, just rooted. So that puts busybox and supersu on my phone. Later on, I installed a custom sound thing to get some decent volume out of this thing.
Now I tried taking the OTA and it failed. I thought it would just wipe out the root stuff and be on it's merry way (like other devices I've had in the past). So, I used the one touch unroot in SuperSu and tried again. Still failed. And it still showed me busybox in the app drawer.
So, here's my question...
Do I need to remove my custom volume thing as well as do the unroot?
And do I need to uninstall busybox before doing the unroot via supersu? Or do i just go to the apps and install it there after the SuperSu unroot?
And, if none of those work right, do I fall back to flashing 4.1.2 directly - or maybe better to flash 4.3 directly? I plan on using saferoot once I'm up to 4.3.
If anyone can help me sort this out, I'd greatly appreciate it. I'm rerooted for the moment.
Thanks!
doncaruana said:
Apologize in advance if this is intuitively obvious to other but after searching and reading a better part of the day, I can't figure it out...
In any case...I rooted my 4.1.2 phone a while back with the casual root. Didn't unlock the bootloader or install a custom recovery, just rooted. So that puts busybox and supersu on my phone. Later on, I installed a custom sound thing to get some decent volume out of this thing.
Now I tried taking the OTA and it failed. I thought it would just wipe out the root stuff and be on it's merry way (like other devices I've had in the past). So, I used the one touch unroot in SuperSu and tried again. Still failed. And it still showed me busybox in the app drawer.
So, here's my question...
Do I need to remove my custom volume thing as well as do the unroot?
And do I need to uninstall busybox before doing the unroot via supersu? Or do i just go to the apps and install it there after the SuperSu unroot?
And, if none of those work right, do I fall back to flashing 4.1.2 directly - or maybe better to flash 4.3 directly? I plan on using saferoot once I'm up to 4.3.
If anyone can help me sort this out, I'd greatly appreciate it. I'm rerooted for the moment.
Thanks!
Click to expand...
Click to collapse
OTA will look for any rooted app and fail so you best bet is just Odin the full 4.3 then root with saferoot. This is you also have a nice clean install.
buhohitr said:
OTA will look for any rooted app and fail so you best bet is just Odin the full 4.3 then root with saferoot. This is you also have a nice clean install.
Click to expand...
Click to collapse
Thanks!
Been a looong time since I messed with Odin...this will just be firmware - no data or store apps will be touched, right?
doncaruana said:
Thanks!
Been a looong time since I messed with Odin...this will just be firmware - no data or store apps will be touched, right?
Click to expand...
Click to collapse
Sorry but flashing the full firmware will wipe everything bring it back to factory stock phone, so you need to backup all your stuff.
Well, just to share with everyone, I did not flash back to stock. For a number of reasons, that wasn't really an option.
My first step was removing viper4android. That actually got rid of the "custom" screen with the open lock on boot.
Then I uninstalled busybox from within itself. Unfortunately, as noted elsewhere, that leaves several hundred symlinks in xbin, so I removed all of those (I was only left with dexdump and su there). After that, I actually uninstalled busybox via the app manager.
Then I used the unroot option in supersu to clean up the rest and remove it.
At this point, I should be completely unrooted, but still got the 402 error when failing to upgrade with the OTA.
So...I plugged the phone in and ran the software upgrade assistant that shows up on the "CD" that presents itself from the phone when you plug it in to USB to the computer. And, actually, that successfully completed the upgrade to 4.3!
Haven't embarked on re-rooting yet (using saferoot) but that's the plan at least.
I found a solution for rooting my D801 running Android 5.0.2. I used KingRoot to gain root access and then Super-Sume Pro to remove KingRoot and install SuperSU. I have not installed TWRP because I am going to stay on stock. It was difficult to find a one-click solution so I hope this helps someone else.
Kingroot has worked for me, too. Nothing else worked, no matter what I did. But Kingroot works great! Thanks for posting.
I have tried Purple Drake, ioroot, StumpRoot, and LGOneClickRoot. None of these worked. I'm particularly chagrined over the ioroot failure because ioroot is listed in the Cyanomodgen installation instructions.
I have not tried Kingroot and am hopeful it's the answer to my prayers.
Could you please confirm your T-Mobile Lollipop software info with mine to make sure we're on the same page? Many thanks.
Android version: 5.0.2
Build number: LRX22G
Software version: D80130c
Woohoo, Kingroot does indeed root the phone. That's the good news.
Now for the bad news. Super-Sume Pro does NOT remove KingRoot v4.8.0 (latest version). I like having a rooted phone, but I don't like having Spyware running on it that chews up bandwidth. How do I get rid of this thing? Brute force delete of binaries?
UPDATE: I got rid of KingRoot via method 2 at https://www.droidmen.com/remove-replace-kingroot-kinguser-with-supersu/. Unfortunately although RootChecker claims the phone is rooted none of the apps that need root can find the su binary because the SuperSU installation failed. Effectively the phone is un-rooted since apps requiring root are inoperable. So back to square 1. It's a big steaming pile of you-know-what.
UPDATE: I retraced my steps and re-ran the shell script of method 2 above. This time it worked. Kingroot is gone, SuperSU 2.49 is installed, and the phone is rooted according to root checker. The phone seemed strangely unstable for a while, but seems to have settled into normal behavior. Don't know if that was a consequence of this procedure or is possibly a hardware problem (battery?). Will keep a close eye on it, but for now all the apps that need root have it. Contemplating the installation of TWRP via GooManager, but that's not a high priority right now.
If anyone reading this is a bloatware removal expert (especially with regard to LG & T-Mobile) I'd like to hear from you. Tools that I've seen mentioned in this regard are Titanium Backup, System App Remover, and Clean Master.
Guys, just followed nbi1's method and finally got this working! Thanks!
Bageland2000 said:
Guys, just followed nbi1's method and finally got this working! Thanks!
Click to expand...
Click to collapse
Did you by any chance install TWRP? If so, how did you unlock the bootloader? I'm looking for a pain free unlock. Held out hope for FreeGee, but despite claims to the contrary this app doesn't support many G2 variants such as mine, the D801 30c (T-Mobile).
nbi1 said:
Did you by any chance install TWRP? If so, how did you unlock the bootloader? I'm looking for a pain free unlock. Held out hope for FreeGee, but despite claims to the contrary this app doesn't support many G2 variants such as mine, the D801 30c (T-Mobile).
Click to expand...
Click to collapse
Never installed TWRP, sorry...
Bageland2000 said:
Never installed TWRP, sorry...
Click to expand...
Click to collapse
Don't try it with Flashify. It'll destroy your recovery. Before trying any custom recovery make sure you have the stock kdz on hand so you can flash the stock recovery if need be.
UPDATE: I was able to flash the stock recovery.img. Of course that doesn't help as far as TWRP is concerned, but at least you wouldn't have a totally munged recovery on the phone.
UPDATE: Was able to successfully install TWRP using Autorec after figuring out that the SuperSU "Mount Namespace Separation" setting needs to be cleared/unchecked.
nbi1 said:
I have tried Purple Drake, ioroot, StumpRoot, and LGOneClickRoot. None of these worked. I'm particularly chagrined over the ioroot failure because ioroot is listed in the Cyanomodgen installation instructions.
I have not tried Kingroot and am hopeful it's the answer to my prayers.
Could you please confirm your T-Mobile Lollipop software info with mine to make sure we're on the same page? Many thanks.
Android version: 5.0.2
Build number: LRX22G
Software version: D80130c
Woohoo, Kingroot does indeed root the phone. That's the good news.
Now for the bad news. Super-Sume Pro does NOT remove KingRoot v4.8.0 (latest version). I like having a rooted phone, but I don't like having Spyware running on it that chews up bandwidth. How do I get rid of this thing? Brute force delete of binaries?
UPDATE: I got rid of KingRoot via method 2 at https://www.droidmen.com/remove-replace-kingroot-kinguser-with-supersu/. Unfortunately although RootChecker claims the phone is rooted none of the apps that need root can find the su binary because the SuperSU installation failed. Effectively the phone is un-rooted since apps requiring root are inoperable. So back to square 1. It's a big steaming pile of you-know-what.
UPDATE: I retraced my steps and re-ran the shell script of method 2 above. This time it worked. Kingroot is gone, SuperSU 2.49 is installed, and the phone is rooted according to root checker. The phone seemed strangely unstable for a while, but seems to have settled into normal behavior. Don't know if that was a consequence of this procedure or is possibly a hardware problem (battery?). Will keep a close eye on it, but for now all the apps that need root have it. Contemplating the installation of TWRP via GooManager, but that's not a high priority right now.
If anyone reading this is a bloatware removal expert (especially with regard to LG & T-Mobile) I'd like to hear from you. Tools that I've seen mentioned in this regard are Titanium Backup, System App Remover, and Clean Master.
Click to expand...
Click to collapse
Thanks for the info. Did method 1 not work for you though?
So I finally tried to root my phone. Tried the LG One Click Root first and as posted here it did not work right. I have now SuperSU on the phone but I can't grant root to anything. Rootchecker shows no root. Now I tried Kingoroot and SuperSU asks to grant access but I can't confirm it. Looks like I have to first get rid of SuperSU? Stuck here not sure what I need to do the get rid of the butchered SuperSU install. Any tips?
Can someone point me to where I can get the AutoRec version that works on D801 Lollipop?
dant3ch said:
I found a solution for rooting my D801 running Android 5.0.2. I used KingRoot to gain root access and then Super-Sume Pro to remove KingRoot and install SuperSU.
Click to expand...
Click to collapse
I was able to do the same using KingRoot-4.1.0.249-release-nolog-201505211812_105241.apk and Super-Sume-v9.1.9.apk
If KingRoot tells you "Unable to get root strategy" or "Failed to acquire cloud issued Root strategy", try to reboot once or twice before trying anything else!
Hi all,
I am having problems with my phone and its starting to drive me crazy. I have a ZTE N817 (Obama phone) which I rooted and flashed TWRP to about 8 months ago. The rom is stock because I've never been able to find any custom roms. I used the kingoroot PC application to root the device (the app I've found that was able to root it), and replaced kinguser with supersu. Everything worked great, or at least as good as one can expect from a device with such lown spec hardware.
About a week ago I opened my busybox installer (Busybox Pro (Stericson) and I noticed the app said either I didn't have root or I needed to update the supersu binary. I had the most recent supersu binary but I reinstalled it and updated the binary anyway. The binary updated fine. Busybox still said I didnt have root. I then down loaded a root checker app from the store, it said I had root and my busybox installation was fine. I opened a few more apps that require root (titanium backup, root explorer, etc) all said the device was not rooted. I installed a couple more root checkers, both said the device was not rooted but one said busybox was installed and the other said it wasnt. The first root checker app still said the phone was rooted and busybox installed.
Whenever I run an app that requires root, I get the popup from supersu asking me to grant root access. I grant it but then the apps just tell me that they are unable to get root access and my device is not rooted. I reinstalled kingoroot on my PC and ran it to root the phone again. It said it ran successfully, supersu installed fine and updated the binary. Still no change in anything. I tried to use kingoroot to unroot the device (just so I could root it again) but kingoroot was unsuccessful, but it says it has no problems rooting it.
At this point I have no idea what is going on or how I can get root access back. Any help or ideas anyone may have will be greatly appreciated.:highfive: Like I said, its seriously starting to drive me nuts. :crying::crying:
Happy Memorial Day to everyone!
jritt said:
Hi all,
I am having problems with my phone and its starting to drive me crazy. I have a ZTE N817 (Obama phone) which I rooted and flashed TWRP to about 8 months ago. The rom is stock because I've never been able to find any custom roms. I used the kingoroot PC application to root the device (the app I've found that was able to root it), and replaced kinguser with supersu. Everything worked great, or at least as good as one can expect from a device with such lown spec hardware.
About a week ago I opened my busybox installer (Busybox Pro (Stericson) and I noticed the app said either I didn't have root or I needed to update the supersu binary. I had the most recent supersu binary but I reinstalled it and updated the binary anyway. The binary updated fine. Busybox still said I didnt have root. I then down loaded a root checker app from the store, it said I had root and my busybox installation was fine. I opened a few more apps that require root (titanium backup, root explorer, etc) all said the device was not rooted. I installed a couple more root checkers, both said the device was not rooted but one said busybox was installed and the other said it wasnt. The first root checker app still said the phone was rooted and busybox installed.
Whenever I run an app that requires root, I get the popup from supersu asking me to grant root access. I grant it but then the apps just tell me that they are unable to get root access and my device is not rooted. I reinstalled kingoroot on my PC and ran it to root the phone again. It said it ran successfully, supersu installed fine and updated the binary. Still no change in anything. I tried to use kingoroot to unroot the device (just so I could root it again) but kingoroot was unsuccessful, but it says it has no problems rooting it.
At this point I have no idea what is going on or how I can get root access back. Any help or ideas anyone may have will be greatly appreciated.:highfive: Like I said, its seriously starting to drive me nuts. :crying::crying:
Happy Memorial Day to everyone!
Click to expand...
Click to collapse
you have twrp still?
install latest supersu.zip
Sent from my XT1096 using Tapatalk
sd_shadow said:
you have twrp still?
install latest supersu.zip
Sent from my XT1096 using Tapatalk
Click to expand...
Click to collapse
Yes, I still have TWRP. If I install supersu from the play store without the binary installed the app will tell me immediately after opening that my device is not rooted and it won't work. If I flash the binary through TWRP first, then supersu installs from the play store no different than if the device was still rooted, but I still don't have root. I get the toast notifications whenever an app requests access, but of course it is unable to grant it. I am still on the exact same version of Android as when I got the phone, nothing other than apps themselves have been updated. I have zero idea how I lost root, and even more confusing to me is why I cannot reacquire it. Again just last night, I tried Kingoroot (what I originally rooted the device with), Dr Fone, iRoot, eRoot and Framaroot. Every one failed.:crying: It's a real pain in the rear because the phone's hardware is so lacking that root access is needed just to make the device somewhat usable. I have not ever been able to find a custom rom despite searching all over many times. But last night I was thinking, since I stil have TWRP if I can find someone else with the same handset with root....could I flash a backup of their stock rom? Would that work?:fingers-crossed: I'm becoming extremely frustrated
jritt said:
Yes, I still have TWRP. If I install supersu from the play store without the binary installed the app will tell me immediately after opening that my device is not rooted and it won't work. If I flash the binary through TWRP first, then supersu installs from the play store no different than if the device was still rooted, but I still don't have root. I get the toast notifications whenever an app requests access, but of course it is unable to grant it. I am still on the exact same version of Android as when I got the phone, nothing other than apps themselves have been updated. I have zero idea how I lost root, and even more confusing to me is why I cannot reacquire it. Again just last night, I tried Kingoroot (what I originally rooted the device with), Dr Fone, iRoot, eRoot and Framaroot. Every one failed.:crying: It's a real pain in the rear because the phone's hardware is so lacking that root access is needed just to make the device somewhat usable. I have not ever been able to find a custom rom despite searching all over many times. But last night I was thinking, since I stil have TWRP if I can find someone else with the same handset with root....could I flash a backup of their stock rom? Would that work?:fingers-crossed: I'm becoming extremely frustrated
Click to expand...
Click to collapse
which Supersu.zip zip are you using?
Sent from my XT1254 using Tapatalk
sd_shadow said:
which Supersu.zip zip are you using?
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
The one I used last night was SR3-SuperSU-v2.79-SR3-20170114223742.zip.
jritt said:
The one I used last night was SR3-SuperSU-v2.79-SR3-20170114223742.zip.
Click to expand...
Click to collapse
Here are some things to check.
Maybe you need to make sure you have root access in developer options set to "apps and adb".
Make sure you have a root explorer and that it is enabled.
Check SELinux to see if it's set to "enforcing" or "permissive", set it to permissive if you can.
You might need to use SuperSU in "systemless mode"
Yes, in theory, a rooted backup from someone else should work.
Sent from my SM-S903VL using Tapatalk