[Q] Regain root - One (M9) Q&A, Help & Troubleshooting

Hello Geeks,
I flashed the twrp and installed SU(att htc m9), initially i got Super SU, but after a pushing the new camera RUU update, i am unable to get the root on the device.
It gives me an error saying "No SU binaries present, SuperSU cannot install them..
What is the way that i can regain root on the device? NO S-OFF made on the device

Related

[Q] Can't update SuperUser?

Alright, I better put the whole backstory in first:
I had rooted my DHD (1.32.405.6 stock) with VISIONary+ r14 and all was fine. Then I unrooted, because I wanted to re-root with /system set as r/w. But after unrooting (also with VISIONary+ r14), I could only temproot for some reason.
I then proceeded to root it using the first two steps of this guide.
This caused all kinds of havoc on my phone, errors about UID's being inconsistent etc., so ended up doing a factory reset.
After that, I was able to permroot, again using VISIONary+ r14. All was/is well.
But I noticed that I'm now stuck with the old "SuperUser Permissions" app, and I can't update it to the release by ChainsDD (I had the one from ChainsDD when I originally rooted).
A search on the phone, reveals that I have a superuser.apk in /data/app, in /system/app and one in /data/data/com.modaco.visionaryplus.
Am I simply stuck with the old version? Or is there a way to update it, without breaking everything (again!)? It's not crucial, just liked the version by ChainsDD a lot more than the old one
I don't have eng hboot or radio s-off or anything like that, yet. Just permroot, without /system r/w, I can however mount /system as r/w with "Mount /system (rw/ro) from Market.
Thanks in advance (and sorry for the long post).
did you ever fix this, i have the same problem here upgrade by ChainsDD installation failed with not correct signed error. also send support question to ChainsDD but no answer yet
forget question, fixed it thx

[q] [b]dhd problem with super user & busybox ota 1.72[/b]

From the start i want to mention i have downgraded fro OTA 1.72 to 1.32 and i am ROOTed , ENG S-OF, RADIO S-OF
i tried to ugrade to OTA 1.72 without loosing root as in
http://forum.xda-developers.com/showthread.php?t=885996
and everthing went fine...but after i unistall te old SU and instal the old one...when i reboot....i download busy box installer from the maket but this fail to install the busy box. it keep tells me i am rooted but it can't install it...
i allerady read the threads about this problem but not at DESIRE HD
i even tried to install the PATCHED SU...but this one keeps crashing

[Q] Unrevoked 3 on Debranded HTC Desire not really rooting - SOLVED

Hi all,
I tried to search on this and didn't uncover my exact scenario. My issue is that after I successfully unrevoke my HTC Desire, I can't install BusyBox. I also get errors when I try to run Alpharev and by running adb su on the phone it says I don't have permissions, so clearly it's done something (I have Clockwork recovery now and also the Superuser app) but the root seems to be incomplete. Let me list everything out...
On my Stock Softbank Froyo 2.2 (HBOOT 0.93-0001, S-ON):
- Ran Unrevoked 3. This reported success.
- Rebooted.
- Attempted to install BusyBox via the installer app from market. I went to install to xbin and it says 'The application failed, either because your device is not nand unlocked or we were unable to remount'. Obviously I am not NAND unlocked at the moment.
- Ran Titanium backup. It says 'phone NOT rooted'.
- Ran Root Checker. It reports that the phone is rooted.
- So I tried Alpharev to S-OFF and it reports that the device is found, but then errors out with at: 'can't open `/tmp/cmdline' errors during model detection. According to Alpharev's instructions, this indicates that the phone isn't rooted.
- So, I tried unrevoked again and it says it can't root (system version too new? it says).
Ok, so I decide to debrand by creating a GoldCard and using the latest WWE RUU. This works perfectly without a hitch. So I rerun the above procedure *without doing anything else* and it fails in exactly the same way. Really there couldn't be fewer steps. From a freshly installed firmware, I have USB debugging on and it *won't really root*
Any suggestions? I think some people report success with Unrevoked 3.21 but I can't find a trustable source of this to try (don't want to try to use a version from a file sharing site for this reason).
Thanks!
Bah, nevermind SOLVED. I was trying to install BusyBox from the market, but I needed to run Titanium Backup, click 'Problems?', then install BusyBox from there. Now all works.

[Q] Root Not Working after bootloader unlocker?

Hello, I have ran into a problem, I have just unlocked my bootloader on my Desire HD. It says it is unlocked when i go into the H-boot (power and volume down). But the main problem is that i cannot root my phone. I have used various programs(HTC super tool, Oneclickroot and one other) and it says its rooted but when i reboot there is no super user installed, and cannot use titanium backup and busy box beacuse it cant find root, even with superuser from the market. When it was trying to root, it came across a few errors like "failed beacuse system is read only or somthing along those lines, when trying to Root the phone. When i was using HTC Super Tools v3 there were various "adb server is out of date restaring" but the main thing is that it says "cannot find directory su" or somthing like that when i am perm rooting it. I dont understand why this is happening beacuse, and i havnt seen this happen to any one else...
Any Ideas?
Thanks
EDIT
For those who may also have the same problem, this is my solution, that isn't rooting:
Originally Posted by silvake
CWM recovery 5.0.1.0 is already available in ROM Manager.
Or you can download it from the ClockworkMod website.
Using the Img file you have proivded i have got my desire hd in the recovery using the htcdev bootloader unlocker with S-ON. Thankyou. For the instructions in how i did it here is the website link: http://www.addictivetips.com/mobile/...-phone-device/
From there i can now put a custom rom! I havnent got a rom working yet so i reckomend a backup of the current rom before doing.
Warning i am not repsonsible if anything happens to your phone but if you have a problem please post below.

[Q] OTA 4.3 lost root

I was running 4.2.2 rooted using rumrunners script. I had supersu installed and voodoo rootkeeper and decided to accept the ota after seeing in rumrunner's thread that people were reporting that it didnt affect root. Well, mine did! I lost root and voodoo doesnt restore it. I tried downloading and rerunning the latest version of the rumrunner script and I get
Code:
Please wait....
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (5/120)
Waiting
Test 2: Booting device
Waiting for ADB (17/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[************************************************************]
Rebooting into bootloader (again)
Waiting for fastboot (5/120)
Waiting for ADB (16/120)
must ferment longer...
chilling..................
bottles are packed, here we go, shhhhhh....
Waiting for device
rom or root issue? unexpected behaviour detected - flash different rom and try again.
ERROR: run rumrunner again.....
The strange thing is that recovery still shows s-off and unlocked. I just can't seem to regain root.
Questions:
1) any ideas on getting the root binary installed?
2) since the phone is still s-off and unlocked, I assume that I could just install maybe the bonestock rom and be done with Verizon - thoughts?
3) worst case - I guess just wait for an updated script from rumrunner?
Thanks in advance!
gauchomark said:
I was running 4.2.2 rooted using rumrunners script. I had supersu installed and voodoo rootkeeper and decided to accept the ota after seeing in rumrunner's thread that people were reporting that it didnt affect root. Well, mine did! I lost root and voodoo doesnt restore it. I tried downloading and rerunning the latest version of the rumrunner script and I get
Code:
Please wait....
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (5/120)
Waiting
Test 2: Booting device
Waiting for ADB (17/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[************************************************************]
Rebooting into bootloader (again)
Waiting for fastboot (5/120)
Waiting for ADB (16/120)
must ferment longer...
chilling..................
bottles are packed, here we go, shhhhhh....
Waiting for device
rom or root issue? unexpected behaviour detected - flash different rom and try again.
ERROR: run rumrunner again.....
The strange thing is that recovery still shows s-off and unlocked. I just can't seem to regain root.
Questions:
1) any ideas on getting the root binary installed?
2) since the phone is still s-off and unlocked, I assume that I could just install maybe the bonestock rom and be done with Verizon - thoughts?
3) worst case - I guess just wait for an updated script from rumrunner?
Thanks in advance!
Click to expand...
Click to collapse
Rumrunner is mainly for gaining S-off.
S-off is not the same thing as root.
Rumrunner does have a nice added perk, in that it also installs superuser and the su binaries for you.(adds root)
But it is not required for rooting an already s-off device.
Either flash the stock rooted rom, or just flash SuperSu and you will be rooted again.
santod040 said:
Rumrunner is mainly for gaining S-off.
S-off is not the same thing as root.
Rumrunner does have a nice added perk, in that it also installs superuser and the su binaries for you.(adds root)
But it is not required for rooting an already s-off device.
Either flash the stock rooted rom, or just flash SuperSu and you will be rooted again.
Click to expand...
Click to collapse
Thanks. I reflashed the recovery (lost that for some reason) and reflashed the supersu zip. Now I have root back, but I have lost some connectivity. I have web access through the browser and a few programs but not play store, facebook, gmail etc. No idea what happened or how to fix it. btw, it doesnt seem to matter if I use wifi or data, the same programs dont work - almost like a firewall block or something.

Categories

Resources