Related
After doing with the PERM ROOT, i did reboot my G2 with volume down+power, "s-off" shows on the screen, but something just happened.
after rebooting, i just uninstall VISIONary, then i rebooted my G2 again, to make sure, i did volume down+power again. Good, s-off is still there. When i came into the home screen, i pressed the Root Explorer, oooooops, i got no root access to open this software....
To check this, i re-install VISIONary, --root now---"your device is already rooted".
All in all, i have the "s-off", but i have no root access.
Help!!!
A big thanks here and looking for some one would like to answer me.
Install Superuser (from ChainDD) and make sure it allows access for your root explorer. Also, try the steps again to get S-Off. After you do the 'sync' command, do a reboot back to your home screen (not bootloader) to see if the changes stick.
And don't start a new thread. Post in the old one.
Make sure Visionary is not set to "Root on Boot".
Reboot the phone and run Visionary again.
Make sure you have the newest version of visionary. Run it to root, open terminal emulator type in "SU" then type "sync" wait two minutes. reboot the phone.
You don't need visionary after you get pern root. I don't have it anymore. If you followed the guide then you should be golden.
Sent from my T-Mobile G2 using XDA App
superuser is useful, but when i redid this step"# /data/local/tmp/root",it was told that # /data/local/tmp/root not found. after sync, i still can not obtain the root access...
fox_lee said:
superuser is useful, but when i redid this step"# /data/local/tmp/root",it was told that # /data/local/tmp/root not found. after sync, i still can not obtain the root access...
Click to expand...
Click to collapse
Did you just try running su?
-RotorDemon- said:
Make sure you have the newest version of visionary. Run it to root, open terminal emulator type in "SU" then type "sync" wait two minutes. reboot the phone.
Click to expand...
Click to collapse
This is what did it for me, I had S-OFF and no SU/Root last night.. took 3 seconds..
Yes, if i uninstall superuser, "su" won't pass the premit. If i keep superuser in my G2, "su" will pass but i need confirm it with superuser...
I have this problem and I deleted visionary because I thought I didn't need it and when trying to get it back its not in the market so I can't try using it again to get the perm root eventhough I have soff
Sent from my T-Mobile G2 using XDA App
-RotorDemon- said:
Make sure you have the newest version of visionary. Run it to root, open terminal emulator type in "SU" then type "sync" wait two minutes. reboot the phone.
Click to expand...
Click to collapse
latest version? u mean R12 or R11?
v6tc said:
This is what did it for me, I had S-OFF and no SU/Root last night.. took 3 seconds..
Click to expand...
Click to collapse
What version of VISIONary did u use? r11 or r12(tested), and did u just work it out?
kicknik said:
I have this problem and I deleted visionary because I thought I didn't need it and when trying to get it back its not in the market so I can't try using it again to get the perm root eventhough I have soff
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Then you'll need to visit the VISIONary thread and download it from there. It was suspended from the Android Market.
Try to do the stock PC10.img to start all over and just go thru the steps.
Sent from my T-Mobile G2 using XDA App
Well I had the r12 version. Tried the temproot (checked for su and it was there.) and then permroot (the phone forced a reset) when it came back on, there was no root. So I decided to go manually. Followed all instructions here http://forum.xda-developers.com/showthread.php?t=833965. Did Everything exactly besides step 6. Well I did it but it said that I already had root. So i proceeded with step 7 and waited five minutes (just to be sure) and then restarted. Checked and confirmed that s-off. Powered on the phone and still no root access. I figured that step 6 may have thrown me off so i tried step 6 and 7 again to no avail. Stuck with s-off but no root.
I had perma-root yesterday. Working and tested... mui happy.
Got OTA update late last night (Southeast US / Tampabay FL). Accepted it like a dumbass.
Currently:
Phone works... I didn't get "teh brix".
VISIONARY tells me "your device is already rooted"
SuperUser has my Root-apps listed with green radio buttons.
su from terminal results in permission denied
screenshot will no-longer run (This program requires root access)
Recovery Boot = S-OFF
Confused = Yes, very
Can't re-root as visionary won't really run properly. Uninstalled Visionary and installed Visionary+. Still says "Your device is already rooted".
S-off no boot fix?
So to reply to my own thread once I've gone through all of the steps repeatedly, I wound up with s-off and no root. even after running visionary+ temp root and then entering (in terminal emulator on the phone) su (granted superuser) and then typing sync and then reboot. Did this over and over again with the same result but to get it to work(for me anyways) i had to run temproot, and then run permroot and then reboot. Mind you, I have already done this step before but it didnt seem to work until afterwards. Hopes that this helps SOMEONE.
For people facing a similar issue, use the RATC method instead of VISIONary, you should get perm root then.
I had the same issue I followed unforgiven's instructions
forum.xda-developers.com/showthread.php?t=833965
after step 7 and you reboot run visionary again and you should gain perm root, hope this helps.
Sent from my T-Mobile G2 using XDA App
Sorry, what is the RATC method of rooting?
Alright, I'll try not to make this an incomprehensible mess. I have an evo with s-off that I reset to stock after playing around with some ROMs. I used the unrevoked method to achieve s-off back then. Anyway, after the reset, I don't have superuser permissions. I do still have s-off, but I have no recovery flashed and as far as I can tell I need to get superuser permission first thing anyway.
The superuser app in the store doesn't do anything. As far as I've been able to find out, I need to flash superuser from the sd card. However, since I don't have a recovery installed, I can't do that. And since I don't have superuser, I can't flash a recovery.. see the problem?
So since my bootloader is locked I figured I'd try the HTCDev method for unlocking it, but when I get to the steps with the command prompt commands, I just get a "waiting for device" message. I tried installing the modified unrevoked drivers, which worked, but I still get the "waiting for device".
Basically I'm unsure what I'm supposed to do. Rooting the phone from stock is so goddamn easy, I don't know why it's being so difficult when I already have s-off. Any help would be appreciated. I couldn't find anything relevant by searching here or elsewhere.
AnHero said:
Alright, I'll try not to make this an incomprehensible mess. I have an evo with s-off that I reset to stock after playing around with some ROMs. I used the unrevoked method to achieve s-off back then. Anyway, after the reset, I don't have superuser permissions. I do still have s-off, but I have no recovery flashed and as far as I can tell I need to get superuser permission first thing anyway.
The superuser app in the store doesn't do anything. As far as I've been able to find out, I need to flash superuser from the sd card. However, since I don't have a recovery installed, I can't do that. And since I don't have superuser, I can't flash a recovery.. see the problem?
So since my bootloader is locked I figured I'd try the HTCDev method for unlocking it, but when I get to the steps with the command prompt commands, I just get a "waiting for device" message. I tried installing the modified unrevoked drivers, which worked, but I still get the "waiting for device".
Basically I'm unsure what I'm supposed to do. Rooting the phone from stock is so goddamn easy, I don't know why it's being so difficult when I already have s-off. Any help would be appreciated. I couldn't find anything relevant by searching here or elsewhere.
Click to expand...
Click to collapse
OH my god, it's so easy.
Download the attached files and place them on the root of your SD card. Run the PC36IMG file through your bootloader, and accept the update. Power off the phone (not going to explain that), then boot back into the bootloader. That will give you the Recovery that you need to flash the superuser app. Just go to RECOVERY after these steps and you will see.
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.
Hey all,
I just wanted to pose a few questions. I've spent about 20 hours going through forums and articles to root my Verizon HTC One, and a heck of a lot of the information out there is very dated, and often contradictory. I've tried condensing it into a single procedure, but am having problems.
Here's the procedure for a brand new phone straight from a verizon store yesterday, running Android 4.3, with hboot 2.55, as I understand it; the information that I believe is now out of date, wrong, or not for 4.3/ 2.55; and the problem(s) I'm running into:
Procedure:
1) Unlock the bootloader and get s-off -- Firewater should be able to do this using the temproot method
2) Flash recovery mod, I was going to use CWM since it worked so nicely on my Incredible for 4 years -- this requires an unlocked bootloader and s-off, done the standard way via fastboot
3) Use CWM to flash superuser in recovery -- push the zip to sd, flash it from recovery
4) Happy times with my old set up back
Misinformation:
1) HTCdev -- no longer allowed for HTC One by Verizon, can't unlock bootloader this way. Renders a lot of the threads irrelevant now that this is not a valid route
2) rumrunner -- works for Android 2.2.4, not 2.3, and up to hboot 2.54
3) firewater "standard method" -- useless to anyone attempting to root a new device for the first time
4) "flash ARHD, then run firewater" -- again, not useful if you're trying to get CWM and SU on your phone for the first time
Problems:
1) The big one. Running temproot/ firewater, I acquire root access after running temproot, but when I run firewater after I get
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, hold power for 60 seconds !!
preparing, one moment
The first bottle is open
chugging..........
C:\adb>
Click to expand...
Click to collapse
with the adb shell crashing out, and my phone will freeze, requiring a hard reboot.
2) I got a few suggestions to use rumrunner (before I decided rumrunner was 2.2.4, from the sources I could find). The process would be going fairly smoothily, until it would crash with the error "looks like device is not rooted AND lacks an unsecure kernel. su or FU!!" I also once got an error about "unexpected process or ROM" but haven't been able to replicate it.
3) Found some advice for "flashing CWM without s-off"...that obviously didn't work, but I thought I might as well try
4) Not so much a problem as a concern...I'm a bit worried about my drivers. I think they are good and up to date, I got them from HTCsync, and have full adb and fastboot control to my device, but still...
The Jury
So, what's your take? Am I missing something obvious?
Update
atewsleybooth said:
So, what's your take? Am I missing something obvious?
Click to expand...
Click to collapse
Update
I tried going through the firewater procedure on OSX instead of Windows, with the exact same results (crashing out of adb shell). This leads me to believe that the problem is with the device, and not the computer. Does that sound right?
I switched cables, got one instance where I actually received "somebody pissed in the firewater reboot and try again." However, 2 reboots since with the same cable and port have both gone back to crashing out of the shell.
Rumrunnwr is only for 4.2.2. Firewater is for 4.3. You need to be complete stock and follow temproot method. Firewater was written for multiple devices so the whole HTC dev unlock and other methods won't work for the m7vzw. If you are on 4.4.2 then you are sol for now.
Gizmoe said:
Rumrunnwr is only for 4.2.2. Firewater is for 4.3. You need to be complete stock and follow temproot method. Firewater was written for multiple devices so the whole HTC dev unlock and other methods won't work for the m7vzw. If you are on 4.4.2 then you are sol for now.
Click to expand...
Click to collapse
I'm on full stock 4.3 device, running firewater using the temproot. I've made sure not to got to 4.4.2.
atewsleybooth said:
I'm on full stock 4.3 device, running firewater using the temproot. I've made sure not to got to 4.4.2.
Click to expand...
Click to collapse
Have u tried to factory reset the device?
Try redownloading the firewater file, mabey it was a bad download, or got corrupted somewhere along the way. If thays not the issue try below.
You shouldnt have to do this but its worth a shot. Once you aquire temp root, try pushing the su binary to /system/xbin, and the superuser.apk to /system/app. Then reboot the phone. This should technically give you root. Then try running firewater again to unlock and get s-off.
cmlusco said:
Try redownloading the firewater file, mabey it was a bad download, or got corrupted somewhere along the way. If thays not the issue try below.
You shouldnt have to do this but its worth a shot. Once you aquire temp root, try pushing the su binary to /system/xbin, and the superuser.apk to /system/app. Then reboot the phone. This should technically give you root. Then try running firewater again to unlock and get s-off.
Click to expand...
Click to collapse
I got it working. What I wound up doing was saying "No" to the first prompt from firewater, then restarting firewater, and saying "Yes." Twice this gave me "somebody pissed in the firewater," but on the third try, it went through. Not initiating firewater twice and canceling out of the first run would always crash my shell.
Go figure.
atewsleybooth said:
I got it working. What I wound up doing was saying "No" to the first prompt from firewater, then restarting firewater, and saying "Yes." Twice this gave me "somebody pissed in the firewater," but on the third try, it went through. Not initiating firewater twice and canceling out of the first run would always crash my shell.
Go figure.
Click to expand...
Click to collapse
Weird. Glad you got it to work though.
Hi Guys,
I am S-OFF and Unlocked with Stock recovery. I need to send my phone back so I want to go back to Locked and S-ON.
Here is my current setup.
4.4.2
Sense 6
I tried Weaksauce and it says root failure. I am trying BMT626 method and it is saying permission denied so I am assuming I need root. I am trying to avoid the RUU method since I am on stock recover and stock rom.
Can anyone help?
Thank you.
Towelroot did the trick
I figured it out.
I used Towelroot and was able to get root and reset secure flag and relock.