Database Info

Thunderbolt - How to confirm root?

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.

Droid 2 Global Can't connect to any wifi HELPP

I am a complete noob with this stuff. So i wanted to root but i read that i had to downgrade my firmware to do it. So i do some sbf-ing with rsdlite 5.7 and it says that it PASSed but on my phone it had an error and wouldnt let me leave bootloader. so i did a ton of research to fix it and i end up getting it to work.. im not sure of it downgraded but im just happy that the phonee turned on. I rooted it with superoneclick and it was a success. after i rooted it i realized that my wifi wasnt working so i wiped all my data and everything and unrooted it and it still wouldnt work. I have verizon fios and it is secured with WEP. i tried other wifi networks and i wasnt able to connect to any of them. it would just say obtaining ip address and then it wud disconnect and scan for other wifi networks and that would keep repeating. I have no idea what is going on and did research for over 24 hours and still cant find the solution. My phone is not activated so i cant call or text or use 3g data. My system version is 4.5.608.A956.Verizon.en.US and my android version is 2.3.3. PLEASE HELP I CANT FIGURE THIS OUT! Thanks in advance

SOMEONE PLEASE REPLY I REALLY NEED TO FIX IT
:crying:

Your problem is that you are still on Android 2.3.3
You have to take the OTA update in order to get WIFI working again.
If you already have root, you can install Voodoo OTA rootkeeper (look for it in the play store, there is an alternate download link there). After installing rootkeeper, you can open it and protect root, then temp unroot.
After that, you need to get the OTA update, and put the zip file on your SD card, and install it from recovery.
Then, restore root with Rootkeeper.
All those files should be available at
http://forum.xda-developers.com/showthread.php?t=1660713
Or, an alternate option is to flash back to Android 2.3.4, and use the direct root method now available.
A combined SBF and Root CD is at
http://forum.xda-developers.com/showthread.php?t=1701862
Or there is a Root only CD there, for if you are on 2.3.4

Thanks SOOO much.. Im going to try it out right now with the first option you gave me and post the results later tonight

the ota rootkeeper app doesnt say temp unroot.. do i use the superoneclick to unroot it.. im not sure if temp unrooting is the same as unrooting? im sorry im just new to android

Rootkeeper doesn't root, just saves a copy of the files.
So, you need to root with super1click, then protect root with rootkeeper.
Then temp unroot, and update in recovery
Sent from my DROID3 using Tapatalk 2

nvm i figured it out. I just unrooted with superoneclick, rerooted again, and then temp unroot showed up.

SWEET after i rebooted (from installing 629 OTA) i restored root and checked if the wifi worked and it did! THANKS SO MUCH! i literally tried for a couple of days to do this. never going to miss with this phone again.. ahaha thanks a ton!

You are welcome, glad you got it back up and working.

Hi;
Had the same problem, with the same specs.
Did as you advised' and have WiFi working!
Thanks loads for your kind input!!
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
bhigham said:
Your problem is that you are still on Android 2.3.3
You have to take the OTA update in order to get WIFI working again.
If you already have root, you can install Voodoo OTA rootkeeper (look for it in the play store, there is an alternate download link there). After installing rootkeeper, you can open it and protect root, then temp unroot.
After that, you need to get the OTA update, and put the zip file on your SD card, and install it from recovery.
Then, restore root with Rootkeeper.
All those files should be available at
http://forum.xda-developers.com/showthread.php?t=1660713
Or, an alternate option is to flash back to Android 2.3.4, and use the direct root method now available.
A combined SBF and Root CD is at
http://forum.xda-developers.com/showthread.php?t=1701862
Or there is a Root only CD there, for if you are on 2.3.4
Click to expand...
Click to collapse

2.3.4/4.5.629 is directly rootable now
Magic MD5 Root 2.3.4 for D2, R2D2, D2G, DX and 2.3.5 for DX2

[Q] limited/crippled Root on 9.30

Ok I searched the forums trying to see if anybody else as seen this issue.
I have unlocked bootloader, rooted, stock system.
When I take the OTA 9.30/9.18. I temp unrooted with Voodoo OTA Rootkeeper > install OTA> then re-root the phone, no problems restoring root and able to run root apps that where already in Superuser app "Allow" list. Problem is if I try to run any new apps that request root they report back that my device is not rooted?
Su is in system/bin. I have come up with the same results twice on 2 different phones. If I take the phone back to 9.20 with root I can add new apps to Superuser "allow" list then take the OTA up to 9.30 and the newly added apps will work.
Edit: it seems to happen only after I update the SU Binaries, tried it on Superuser and SuperSU same results
Any one else seeing this? or is it just me.

SaddleTramp said:
Ok I searched the forums trying to see if anybody else as seen this issue.
I have unlocked bootloader, rooted, stock system.
When I take the OTA 9.30/9.18. I temp unrooted with Voodoo OTA Rootkeeper > install OTA> then re-root the phone, no problems restoring root and able to run root apps that where already in Superuser app "Allow" list. Problem is if I try to run any new apps that request root they report back that my device is not rooted?
Su is in system/bin. I have come up with the same results twice on 2 different phones. If I take the phone back to 9.20 with root I can add new apps to Superuser "allow" list then take the OTA up to 9.30 and the newly added apps will work.
Edit: it seems to happen only after I update the SU Binaries, tried it on Superuser and SuperSU same results
Any one else seeing this? or is it just me.
Click to expand...
Click to collapse
I updated my phone same as you and kept root but can't test your issue until I get home later where the phone is.
What you could try is re-rooting with the unlocked boot loader method explained on the razr forum (link to the post is in one of the recent help/root threads here).
I know I kept root, but am interested to see if I have the same issue as you. This is the first I have seen it reported.
Tappin G2 Style

SaddleTramp said:
Ok I searched the forums trying to see if anybody else as seen this issue.
I have unlocked bootloader, rooted, stock system.
When I take the OTA 9.30/9.18. I temp unrooted with Voodoo OTA Rootkeeper > install OTA> then re-root the phone, no problems restoring root and able to run root apps that where already in Superuser app "Allow" list. Problem is if I try to run any new apps that request root they report back that my device is not rooted?
Su is in system/bin. I have come up with the same results twice on 2 different phones. If I take the phone back to 9.20 with root I can add new apps to Superuser "allow" list then take the OTA up to 9.30 and the newly added apps will work.
Edit: it seems to happen only after I update the SU Binaries, tried it on Superuser and SuperSU same results
Any one else seeing this? or is it just me.
Click to expand...
Click to collapse
as it turns out, i am in the same boat as you, no root for new apps. odd situation.

[Q] Rooting Problem (s)

I have the ZTE Warp Sequent N861 that I want to root for memory swapping. I tried using DoomLoRD's ICS root, and SRS root for android. Some of the root checker apps on google play say my phone is rooted, some say that it isn't. Any of the programs that need SU permission are not working, saying that there is either no root, or no superuser permissions. I'm not sure exactly what the problem. I reset my phone back to factory restore but the su program is still there and now I don't know what to do. Any help at all would be appreciated, I can't seem to figure this out. Thanks!

Help! Lost Root??

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