Recently I decided to root my eris. It was running ota 2.1 with hboot 1.47. I followed the instructions to the letter and everything seems to have worked, but this is not the case.
Currently none of the root apps work, ie superuser permissions. I also cannot access the phone via adb as if it was not rooted.
did you root or install one of the leaks by mistake? check your hboot version to verify what you have. if it says 1.49.xx s-off you have root, if it says s-on you either have not rooted it or have installed one of the leak versions floating around.
I flashed the rom in the root how to post in the forums.
Eris_Official_0.8.1T2.zip
I see
PB00100 XC ENG S-OFF
HBOOT-1.49.2000 (PB0010000)
when I vol down + power to get to hboot
(note I still have PB00IMG.zip in my root of the sdcard)
I have now tried 6-7 roms from the dev forum with no success accessing a shell after I install the rom. When the image from PB0100.zip is the image in use, I have no issue accessing the device with adb. But after a root rom is installed, there is no luck.
Is USB debugging on?
lotus22 said:
Is USB debugging on?
Click to expand...
Click to collapse
Yes, I have made sure it is. I can mount it as a partition on my box but get the following errors when trying to access the device.
~/src/add/android-sdk-linux_86/tools$ adb shell
error: insufficient permissions for device
Related
Ok, did have my phone rooted but one of the ROM's on here managed to cause problems so installed one of the factory HTC ROM's to unroot it and put it back should I need to send it to HTC to fix.
So after putting the stock HTC ROM on when I enter recovery mode it is now teling me that the handset is locked (bootloader is presume) also the it is still showing S-OFF.
It is showing the following so if someone can explain to a noob how to re-root it that would be fantastic.
SHOOTER_U PUT SHIP S-OFF RL
HBOOT - 1.49.0018
RADIO-10.14.9020.06_M
eMMC-boot
Oct 3 2011,15:03:01
Any help is really appreciated as there is some really cool looking ROM's that I would like to try.
So, over 80 views and no-one has an answer for this?!
ratedr75 said:
Ok, did have my phone rooted but one of the ROM's on here managed to cause problems so installed one of the factory HTC ROM's to unroot it and put it back should I need to send it to HTC to fix.
So after putting the stock HTC ROM on when I enter recovery mode it is now teling me that the handset is locked (bootloader is presume) also the it is still showing S-OFF.
It is showing the following so if someone can explain to a noob how to re-root it that would be fantastic.
SHOOTER_U PUT SHIP S-OFF RL
HBOOT - 1.49.0018
RADIO-10.14.9020.06_M
eMMC-boot
Oct 3 2011,15:03:01
Any help is really appreciated as there is some really cool looking ROM's that I would like to try.
Click to expand...
Click to collapse
ratedr75 said:
So, over 80 views and no-one has an answer for this?!
Click to expand...
Click to collapse
Wow .. so originally you had an older hboot and used revolutionary to set s-off. Then you loaded a newer RUU which contained an hboot that was patched against revolutionary's s-off method.
Now you're on a newer hboot patched against revolutionary's s-off method, but you're still set s-off from previously using their method.
Don't see this situation very often. According to the theory, of how unrevoked set s-off and how I assume revolutionary is similar, you should still be s-off, as your bootloader shows, meaning your internal memory is NOT write protected.
In order to root your device, you should be able to fastboot flash a custom recovery. Boot into the custom recovery and load the normal superuser .zip or manually over adb push an su binary (I prefer aosp for developers) and chmod 4755 /system/bin/su . Both of those methods should give you root!
Hope that helps!
So if I install another ROM and try to goto recovery mode (which at the moment I am getting the triangle when I enter) I should be able to re-root this?
joeykrim said:
Wow .. so originally you had an older hboot and used revolutionary to set s-off. Then you loaded a newer RUU which contained an hboot that was patched against revolutionary's s-off method.
Now you're on a newer hboot patched against revolutionary's s-off method, but you're still set s-off from previously using their method.
Don't see this situation very often. According to the theory, of how unrevoked set s-off and how I assume revolutionary is similar, you should still be s-off, as your bootloader shows, meaning your internal memory is NOT write protected.
In order to root your device, you should be able to fastboot flash a custom recovery. Boot into the custom recovery and load the normal superuser .zip or manually over adb push an su binary (I prefer aosp for developers) and chmod 4755 /system/bin/su . Both of those methods should give you root!
Hope that helps!
Click to expand...
Click to collapse
ratedr75 said:
So if I install another ROM and try to goto recovery mode (which at the moment I am getting the triangle when I enter) I should be able to re-root this?
Click to expand...
Click to collapse
I've quoted my previous post to highlight the steps outlined. I never mentioned anything about another ROM.
If the theory holds, as it was true for unrevoked's method of s-off and some members of unrevoked are now part of AlphaRevX releasing the revolutionary tool, you only need to flash a custom recovery through fastboot or bootloader.
If you have adb setup, it would literally take you 10 seconds to issue the fastboot command and another 10 seconds to reboot into recovery to see if t worked.
Currently, when you boot into recovery and you see the triangle, that is the stock recovery. Sometimes on the stock recovery screen, if you want to activate the menu, pressing vol up + pwr *should* work in stock recovery but sometimes manf like HTC change this function in the version of recovery they distribute.
Once you use the command: fastboot flash recovery c:\android\cwm-recovery.img , you should be able to boot into recovery and see the custom recovery load.
If that method doesnt work, the other method to attempt is loading a PG86IMG.zip file on the root of the sdcard with the custom recovery inside the PG86IMG.zip. Upon booting into the bootloader, it should scan this file and ask to update. If you select yes to update, the bootloader should flash and you should have a custom recovery.
If neither of those two methods work, you'll likely have to use the HTC unlock method. But I think those methods should work as your device still shows S-OFF.
Good luck!
Have tried all your methods and various other ones.
None of them work at all, a lot of the people on here seem to think that eveyrone has their abilities.
I could get an ADB shell up, the CMD prompt didn't work either.
The phone is going in its box and i'd rather spend some money on a phone that is easier to work with a windows 7 laptop.
ratedr75 said:
Have tried all your methods and various other ones.
None of them work at all, a lot of the people on here seem to think that eveyrone has their abilities.
I could get an ADB shell up, the CMD prompt didn't work either.
The phone is going in its box and i'd rather spend some money on a phone that is easier to work with a windows 7 laptop.
Click to expand...
Click to collapse
The issues you're experiencing are due to HTC's complex locking method to deter root access. There are many Android devices which come stock with no locking protection or must less sophisticated locking protection.
If you're not able to properly setup adb, then the PG86IMG.zip method should be more convenient for you. All you need to do is put a PG86IMG.zip file onto the root (main dir) of your sdcard and holding vol down + pwr (boot into the bootloader). From here, it will scan the PG86IMG.zip and prompt if you want to load. Choose yes and this will flash the custom recovery.
Once the custom recovery is loaded, you should be able to flash a rooted ROM from, flash superuser .zip file or adb push su binary to restore root.
HTC intentionally makes this process difficult and it is relatively more difficult than other Android devices. All the resources are here at your disposal but HTC requires a bit more work/effort/learning to accomplish what is easier on some other Android devices. Although, even the Google Nexus S requires using fastboot to unlock t he device.
Nobody wants to see anybody give up and abandon. Hope that helps!
for whatever reason on the evo 3D, fastboot commands for things like flashing a recovery don't seem to work even with s-off. You need to put the custom recovery in a zip and name it PG86IMG then flash it from the bootloader and it will work.
fyi you should always be able to run a stock RUU (even new ones) because Revolutionary for the evo 3D gave you actual radio s-off and not just fake s-off with a patched hboot which is how Revolutionary worked on most phones. radio s-off pretty much means your phone will never go back to s-on even with a stock RUU. that is why you were able to upgrade the hboot and still keep s-off.
Thanks for the help guys. I'm going to give this one last try before I got and invest in an xperia arc s.
Does anyone have a decent download for the PG86IMG.zip file?
Ill try this at lunch, if not its away it goes.
patrick92260 said:
for whatever reason on the evo 3D, fastboot commands for things like flashing a recovery don't seem to work even with s-off.
Click to expand...
Click to collapse
fastboot commands don't work on the EVO 3D? even for recovery?
I haven't seen this complaint on the Q&A board. Majority of users seem to have plenty of success using fastboot to flash kernels and custom recoveries. Although, majority of people posting on the Q&A board recently have the latest hboot and can only use HTC's unlock method. Perhaps this is only an issue on revolutionary s-off devices?
ratedr75 said:
Thanks for the help guys. I'm going to give this one last try before I got and invest in an xperia arc s.
Does anyone have a decent download for the PG86IMG.zip file?
Ill try this at lunch, if not its away it goes.
Click to expand...
Click to collapse
I went to google.com and typed in the phrase, "twrp PG86IMG.zip" and the second link looks to be the quickest to obtaining the file:
http://teamw.in/project/twrp/67
I have heard pretty decent reports of Sony being fairly support of developers and allowing their devices to be unlocked and rooted.
Good Luck!
Thanks guys. Again. Now would anyone be interested in purchasing the EVO 3D GSM sim free from myself?
hi I am in the same position as the OP, just got my phone 2nd hand..want to flash LeeDroids Rom, my phone is GSM version, please advise how to get custom recovery..thanks
Hey guys,
So when I updated my superuser, I seemed to loose root access.. Im currently running Vicious MIUI 1.11.25, HBOOT version 1.04.2000. The Revolution tool only allows for 1.04.0000 and 1.05.0000 so therefore I was going to use the Radios, Recoveries, and HBOOTs thread over at AndroidForums, download the HBOOT 1.05.0000, rename it and flash it so that I can run Revolution tool.. I still have S-Off and such just wondering if anyone can give some guidance on this before I make my phone into a paper weight. Thanks for your help..
Dave
Revert back to the older version of Superuser.
Revolutionary does NOT root your phone, it just gives you S-OFF, which allows you to flash an alternate recovery (which allows you to flash Superuser).
Thanks Steven,
So what would be my next course of action?
Currently when in ADB, I get shell, then su so I still have root. However when I goto Titanium Backup it states I dont have root access and then in Wifi Tether it states it cant download binaries and to check root access.. Also Barnacle states it cannot make the binary writable so im at a loss.. I tried when in ADB with su to type mount and I get mount: permission denied..
make sure you have debugging on settings/applications/developement/check usb debugging to push the old superuser back to your phone through ADB
d.scardino said:
Thanks Steven,
So what would be my next course of action?
Currently when in ADB, I get shell, then su so I still have root. However when I goto Titanium Backup it states I dont have root access and then in Wifi Tether it states it cant download binaries and to check root access.. Also Barnacle states it cannot make the binary writable so im at a loss.. I tried when in ADB with su to type mount and I get mount: permission denied..
Click to expand...
Click to collapse
As mentioned above, I would obtain an older version of SU (ROM Manager has it) flash that and see if it gets fixed.
had the same issue a while back, SU update broke itself. Reinstalled the old zip file in recovery and worked just fine.
Since theirs no OTA, I relocked and installed the latest ICS leak
then used the htc all in one kit, unlocked the bootloader, installed Amon-Ra 3.15
and tried the perm root option (which for some reason didn't work last time either)
so I booted into Amon-Ra and installed SU which said it worked.
I still can't get root on ICS, I'd just install a rooted rom, but I'm trying to get S-OFF
I did not that it said tampered above unlocked in the bootloader.
Did I miss something?
movielover76 said:
Since theirs no OTA, I relocked and installed the latest ICS leak
then used the htc all in one kit, unlocked the bootloader, installed Amon-Ra 3.15
and tried the perm root option (which for some reason didn't work last time either)
so I booted into Amon-Ra and installed SU which said it worked.
I still can't get root on ICS, I'd just install a rooted rom, but I'm trying to get S-OFF
I did not that it said tampered above unlocked in the bootloader.
Did I miss something?
Click to expand...
Click to collapse
Tampered is a result of installing a custom recovery, has nothing to do with installing a rooted rom.
mjones73 said:
Tampered is a result of installing a custom recovery, has nothing to do with installing a rooted rom.
Click to expand...
Click to collapse
Ok, I was pretty sure tampered was ok, just trying to include all of the details I have., what am I missing in rooting ICS?, su is installed but it says permissions denied when I run it via terminal emulator?
I tried fixed permissions and that didn't work either.
Nevermind,
I just flashed the stock rooted rom and I'm all good and have achieved S-OFF, Yeah
movielover76 said:
Ok, I was pretty sure tampered was ok, just trying to include all of the details I have., what am I missing in rooting ICS?, su is installed but it says permissions denied when I run it via terminal emulator?
I tried fixed permissions and that didn't work either.
Nevermind,
I just flashed the stock rooted rom and I'm all good and have achieved S-OFF, Yeah
Click to expand...
Click to collapse
ok yeah, the problem i found with that rooting method is it puts the su bin in /xbin/ instead of /bin.
i could talk you through how to use the adb shell to put the su binary in /bin/ and ln-s it to /xbin.
if you need more help come to the IRC channel: http://forum.xda-developers.com/showthread.php?t=1345401
I've rooted my original Incredible and a Nook before with no problems. I didn't anticipate any problems here. From stock, I successfully flashed the latest ICS RUU (3.14) and unlocked the phone via Hasoon2000's kit. I confirmed in HBOOT that I was unlocked. When I tried to run the "Perm Root (GB/ICS)" command, it didn't work. There were a lot of "Device not found" errors in the terminal (yes, USB debugging was enabled at all times). My phone would try to reboot but then get stuck on the triangle/exclamation point screen.
After a few tries, I decided to manually root the phone. I rebooted normally (after taking the battery on and off) and used Hasoon2000's kit to install AmonRa. I then booted into recovery. I wiped cache and Dalvik cache and went into Developer Menu. I then chose "Install superuser and su." It seemed to do it correctly. I rebooted and made sure Superuser was installed and updated. At this point, I thought I had root access.
I installed Titanium Backup but it gave me an error that it couldn't acquire root privileges. I installed the Root Checker app and it also said I wasn't rooted properly. I don't know what I did wrong. Please help.
Install a custom rom from the Dev section. They are all pre-rooted
AshtonTS said:
Install a custom rom from the Dev section. They are all pre-rooted
Click to expand...
Click to collapse
Would this allow me to get S-Off?
luis1972 said:
Would this allow me to get S-Off?
Click to expand...
Click to collapse
Yes, you need to be rooted to get S-off, so installing any of the roms will do.
S-OFF is a whole another process, you definitely need to be rooted first though.
Sent from my ADR6425LVW
I also got errors when tring to do the one-click root method. So try flashing the Amon-Ra recovery after you unlocked the bootloader. Reboot into recovery and then go to develpoer's menu and select root and something else in that menu. From there you are rooted. After that, follow this website to get S-OFF. I did mine last night and it went smooth. It took me a few times to do the wire trick, but I finally got it.
S-OFF Instructions
First thank you for reading this thread.
I successfully unlocked the bootloader but I'm have trouble with the permanent root of my phone.
I connect my phone via usb, I disable htc sync and set the phone to charge only
usb debugging is active
I run "rEZoundRoot-v1.5-TheDr1ver" option 1, the device reboots to flashboot
and it looks like the root works from the messages in the program works
the device reboots. I run the batch again and choose option 2, to permanently
install amon ra and I then create a full backup then I reboot.
but when I check for root its not rooted!!????
help please
astbnboy001 said:
First thank you for reading this thread.
I successfully unlocked the bootloader but I'm have trouble with the permanent root of my phone.
I connect my phone via usb, I disable htc sync and set the phone to charge only
usb debugging is active
I run "rEZoundRoot-v1.5-TheDr1ver" option 1, the device reboots to flashboot
and it looks like the root works from the messages in the program works
the device reboots. I run the batch again and choose option 2, to permanently
install amon ra and I then create a full backup then I reboot.
but when I check for root its not rooted!!????
help please
Click to expand...
Click to collapse
easiest method especially if you s-on is fastboot flash amon ra and go to advanced options or developer options in it and flash its su and superuser and binaries thats built into the recovery...if you plan on staying on ics or lower roms amon ra and s-on is good for you...if you flash any rom higher i highly HIGHLY suggest gaining s-off and using a recovery like twrp or cwm as they have been updated here in the threads specifically for jellybean and kitkat where as amon ra hasnt....also updating to most recent stuff like radios and hboot and kitkat roms while s-on puts you in a much higher risk of a brick as you will not be able to downgrade to fix a soft brick just in case things get messed up on your end...its only possible to fix a soft brick while s-off
thanks for the answer
I don't know about or understand the s-on/s-off thing. how do I s-off??? As I read your reply again I can tell you that I did exactly that when I rebooted I ran "rEZoundRoot-v1.5-TheDr1ver" again in option 2, which gave me access into amon ra and I installed su and superuser at that time but still no root, can you tell me how to find out if I'm s-on or s-off. are you automatically s-on if you have done nothing to obtain s-off??
thank you for helping************** edit
I just booted my phone into fastboot and discovered I'm s-on
here is what I see
*** TAMPERED ***
*** UNLOCKED ***
VIGOR PVT SHIP S-ON RL
HBOOT-2.25.000
RADIO-1.22.10.042r/1.22.10.0424r
OpenDSP-v13.6.0.7611.00.0104
eMMC-boot
Apr 12 2012, 16:47:46
*****************3rd edit
I was able to boot into amon ra untethered and I tried to reinstall or fix su it appeared to go well
I then went into the fix permissions menu and ran that app after which I rebooted and checked for root su was again denied!!! I'm so frustrated.
astbnboy001 said:
I don't know about or understand the s-on/s-off thing. how do I s-off??? As I read your reply again I can tell you that I did exactly that when I rebooted I ran "rEZoundRoot-v1.5-TheDr1ver" again in option 2, which gave me access into amon ra and I installed su and superuser at that time but still no root, can you tell me how to find out if I'm s-on or s-off. are you automatically s-on if you have done nothing to obtain s-off??
thank you for helping************** edit
I just booted my phone into fastboot and discovered I'm s-on
here is what I see
*** TAMPERED ***
*** UNLOCKED ***
VIGOR PVT SHIP S-ON RL
HBOOT-2.25.000
RADIO-1.22.10.042r/1.22.10.0424r
OpenDSP-v13.6.0.7611.00.0104
eMMC-boot
Apr 12 2012, 16:47:46
*****************3rd edit
I was able to boot into amon ra untethered and I tried to reinstall or fix su it appeared to go well
I then went into the fix permissions menu and ran that app after which I rebooted and checked for root su was again denied!!! I'm so frustrated.
Click to expand...
Click to collapse
You appear to be running ICS firmware, did you read the notes and information on TheDr1ver.com about this method of rooting? I am assuming not, as this is for Gingerbread only, it will not work on ICS.
Proper rooting of the Rezound is actually VERY simple, no tool or all in one is needed, just proper drivers, adb, and an unlocked bootloader.
1. Install adb and fastboot (usually the ADB SDK from Google appropriate for your machine)
2. Install drivers (if not already installed, use HTC Sync, install then remove the application)
3. Go to HTCDev.com and follow through the unlock process
4. Boot and/or flash a recovery like Amon Ra/TWRP/CWM
5. Flash SuperSUxxx.zip in recovery
6. Reboot and go to the SuperSU app and update binaries if necessary
Done, permanent root. With ICS there is no real "one click" method of rooting, GB had some exploits that some scripts could temp root, then permanent root, but they don't work in ICS or are no longer supported.
Sorry, but you really should just to do it the manual way, there are tons of step-by-step tutorials on the various forums.
ok
acejavelin said:
You appear to be running ICS firmware, did you read the notes and information on TheDr1ver.com about this method of rooting? I am assuming not, as this is for Gingerbread only, it will not work on ICS.
Proper rooting of the Rezound is actually VERY simple, no tool or all in one is needed, just proper drivers, adb, and an unlocked bootloader.
1. Install adb and fastboot (usually the ADB SDK from Google appropriate for your machine)
2. Install drivers (if not already installed, use HTC Sync, install then remove the application)
3. Go to HTCDev.com and follow through the unlock process
4. Boot and/or flash a recovery like Amon Ra/TWRP/CWM
5. Flash SuperSUxxx.zip in recovery
6. Reboot and go to the SuperSU app and update binaries if necessary
Done, permanent root. With ICS there is no real "one click" method of rooting, GB had some exploits that some scripts could temp root, then permanent root, but they don't work in ICS or are no longer supported.
Sorry, but you really should just to do it the manual way, there are tons of step-by-step tutorials on the various forums.
Click to expand...
Click to collapse
Ok i'm already able to flash into Amon Ra and within the Amon Ra recovery I have made a full backup and, under the "developer options"
tab I installed su. So since I'm apparently part rooted because I can flash into amon ra but there is a problem when attempting to install su from Amon Ra so I'll read some more because I don't want to brick my phone.
astbnboy001 said:
Ok i'm already able to flash into Amon Ra and within the Amon Ra recovery I have made a full backup and, under the "developer options"
tab I installed su. So since I'm apparently part rooted because I can flash into amon ra but there is a problem when attempting to install su from Amon Ra so I'll read some more because I don't want to brick my phone.
Click to expand...
Click to collapse
OK, then do it manually...
1) Download UPDATE-SuperSU-vx.xx.zip from http://download.chainfire.eu/supersu, where x.xx is the current version (1.94 at the time of this posting) and place it in the root of your external storage (SD Card)
2) Reboot and start Amon Ra
3) Install/Flash UPDATE-SuperSU-v1.94.zip
4) Wipe cache and dalvik (do not wipe/format anything else)
5) Reboot (will take longer than normal, be patient)
6) Open SuperSU and update the binary (it will prompt you if it needs to)
7) Go to Settings tab and scroll down to SYSTEM section, and select "Install SuperSU into /system", if it is grayed out and you can't select it, then it is already there. Reboot immediately if prompted.
8) Open the Play Store and install BusyBox and Root Checker
9) Open BusyBox and grant it root permissions, after it goes through it's checks it should say something about "BusyBox xxxxx is installed. Busy Box is installed to /system/xbin", Select Busybox 1.22.1 will be installed to /system/xbin and click INSTALL at the bottom and allow it to finish, then close Busybox
10) Reboot
11) Open Root Checker and tab Verify Root, you should be good to go.
If this doesn't work, I would replace Amon Ra with TWRP or CWM and do it again.
I would really suggest twrp... ....when I first rooted and installed twrp the first thing it asked me when on stock before I rebooted was right before I rebooted, would you like to install su? I swiped to flash rebooted checked and su was working perfectly.... I would suggest that..... Okay I know I'm probably not the right person to do this, but I'm thinking about making a root guide for the Rezound..... Taking everything that could go wrong and also putting that in there with a answer on what to do.....
Sent from my Rezound using tapatalk. CyanogenMod 11. S-off.
pball52998 said:
I would really suggest twrp... ....when I first rooted and installed twrp the first thing it asked me when on stock before I rebooted was right before I rebooted, would you like to install su? I swiped to flash rebooted checked and su was working perfectly.... I would suggest that..... Okay I know I'm probably not the right person to do this, but I'm thinking about making a root guide for the Rezound..... Taking everything that could go wrong and also putting that in there with a answer on what to do.....
Sent from my Rezound using tapatalk. CyanogenMod 11. S-off.
Click to expand...
Click to collapse
I think that would be useful. I'm looking into finally rooting my current rezound and there's just so much info out there my brain can't process anymore. I used to know exactly how to do it but my brain has totally regressed and there are to many term/acronyms to hold onto in my brain. Also trying to figure out all of it will work on my mac booted into windows.
Morpheus991 said:
I think that would be useful. I'm looking into finally rooting my current rezound and there's just so much info out there my brain can't process anymore. I used to know exactly how to do it but my brain has totally regressed and there are to many term/acronyms to hold onto in my brain. Also trying to figure out all of it will work on my mac booted into windows.
Click to expand...
Click to collapse
PM me fellow mac user and rezound user...