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.
Related
I installed Visionary and everything was working perfect... But I made the stupid mistake to press Permroot and my G2 shut down and never bootup to Andrid OS..
I only see the HTC green logo .. I tried everything on recovery mode.. but I only get the HTC logo and the phone dont go anywere..
I tried to install the original G2 stock ROM but then the update fail saying Im trying to flash a older update. The room in the phone is newer than the update Im trying to install..,
Someone knows were I can find a Custom room that works in my Tmobile G2 USA...?
I need to install the room in recovery mode...ONLY .. because my phone do not boot-up.... So the ADB is disabled and the phone do not work... I only have access to recovery mode...
PLUS the phone is NOT rooted...
And Please dont tell me to do factory Reset.. because I did all that..If Im here is because I have tried everything and I dont get this phone to work.
Is there a room or a custom room somewhere that can be installed in my G2 by Recovery mode..?
If there is ,, can someone give me the link...?
My HBOOT screens says the following
VISION PVT SHIP S-ON
HBOOT- 0.82.0000
MICROP-0425
RADIO-26.03.02.26_M
eMMc-boot
Sep 2 2010, 17:59:38
boyfrom75 said:
I installed Visionary and everything was working perfect... But I made the stupid mistake to press Permroot and my G2 shut down and never bootup to Andrid OS..
I only see the HTC green logo .. I tried everything on recovery mode.. but I only get the HTC logo and the phone dont go anywere..
I tried to install the original G2 stock ROM but then the update fail saying Im trying to flash a older update. The room in the phone is newer than the update Im trying to install..,
Someone knows were I can find a Custom room that works in my Tmobile G2 USA...?
I need to install the room in recovery mode...ONLY .. because my phone do not boot-up.... So the ADB is disabled and the phone do not work... I only have access to recovery mode...
PLUS the phone is NOT rooted...
And Please dont tell me to do factory Reset.. because I did all that..If Im here is because I have tried everything and I dont get this phone to work.
Is there a room or a custom room somewhere that can be installed in my G2 by Recovery mode..?
If there is ,, can someone give me the link...?
My HBOOT screens says the following
VISION PVT SHIP S-ON
HBOOT- 0.82.0000
MICROP-0425
RADIO-26.03.02.26_M
eMMc-boot
Sep 2 2010, 17:59:38
Click to expand...
Click to collapse
Try the following link:
http://forum.xda-developers.com/showthread.php?t=842495
I already did try the link. But I dont understand what option to take..
The one of the options I think will work needs to have the phone ADB running ..
But my ADB is disabled because I can't get to the Android OS and the phone is not rooted..
I was reading that you can connect the phone to the Computer to fix it..
How do I do that ? What program do I need to run it ? But I dont like that option,,,, is to complicated..
Is there a way to fix the phone using the SD card on Recovery mode ?
boyfrom75 said:
I already did try the link. But I dont understand what option to take..
The one of the options I think will work needs to have the phone ADB running ..
But my ADB is disabled because I can't get to the Android OS and the phone is not rooted..
I was reading that you can connect the phone to the Computer to fix it..
How do I do that ? What program do I need to run it ? But I dont like that option,,,, is to complicated..
Is there a way to fix the phone using the SD card on Recovery mode ?
Click to expand...
Click to collapse
1) Just to clarify: VISIONary is a complete fail. Root using the rage method, then you can actually control what's happening to your device.
2) Did you ever flash clockwordmod recovery?
If you can boot into clockwork recovery you just need to flash another ROM.
Try posting this in the Q n A section. I know, posting a question in the QnA forum probably sounded like a CRAZY idea, but guess what, that is where this belongs.
tehseano said:
Try posting this in the Q n A section. I know, posting a question in the QnA forum probably sounded like a CRAZY idea, but guess what, that is where this belongs.
Click to expand...
Click to collapse
this guy is obviously new cut him some slack.....
just follow the instruction on the link carefully
idk why people are having trouble with VISONary i used it to root my phone n it worked....
im new on the forums but i know a thing or two about rooting
That's why I'm using Rom manager.. because its easier for my self.. as soon as you flash clock work recovery.. I believe that you can't go wrong.. I also did something similar and my phone also staid at the HTC screen.. but went back into recovery mode and clicked on restore and went in on my old Rom
sent from g2 using DHD Rom
boyfrom75 said:
I already did try the link. But I dont understand what option to take..
The one of the options I think will work needs to have the phone ADB running ..
But my ADB is disabled because I can't get to the Android OS and the phone is not rooted..
I was reading that you can connect the phone to the Computer to fix it..
How do I do that ? What program do I need to run it ? But I dont like that option,,,, is to complicated..
Is there a way to fix the phone using the SD card on Recovery mode ?
Click to expand...
Click to collapse
Ok, this is a snip from the link in the second post, it sounds like your are stuck in a boot loop with s-on, if so then this part is the part you need to try:
"*if you have stock or eng-recovery installed.
will the phone attempt to boot android at all? where is it stuck at?
a good min after it starts to try to boot, type these commands:
adb remount
adb shell
if you can get in shell then theres still hope. back out shell for a second and start here:
put the cwm recovery.img and wpthis.ko in your sdk folder
adb remount
adb push wpthis.ko /data/local/wpthis.ko (specific for your kernel)
adb push recovery.img /data/local/recovery.img
adb shell
# insmod /data/local/wpthis.ko (should get same function not implemented error as when u rooted first time)
# dd if=/data/local/recovery.img of=/dev/block/mmcblk0p21 (now wait a min or 2 to give it time to finish)
#sync (give it another min or to just to be safe)
#reboot recovery
at this point you should be in cwm recovery. follow instructions above for flashing with s-on."
So now you are gonna have to install Andriod SDK to your computer and the drivers for the G2, there is gonna be a lot of reading and some downloading on your part to do this. Next your gonna have to download cwm recovery.img and wpthis.ko in your sdk folder and then follow the instructions above to recover your phone. Unfortunatly there is no one click fix. Its gonna take a lot of reading and understanding to do this on your part. Gonna have to learn to use ADB there a guide for that and run some basic command promts. Im no Dev or anything but I taught myself by doing a lot of reading, watching videos and a lot of searching. Hope you find the will to do it and recover you phone. Plus we are here to help walk you through some of it but your also gonna have to do some leg work to. GOOD LUCK.
I don't think the OP knows what adb is... you gotta do some more reading get over your fear of using your computer to fix your phone. Its really nothing to be afraid of and its not at all complicated.
Sent from my HTC Vision using XDA App
I'm gonna assume he knows what ADB is and if that's the case, your only option is using one of the full updates...from tmobile. It would have to be a new version of course, for your recovery to allow it. Trying reading through thr RUU threads, perhaps something or someone there can help.
Goodluck, and sry.
Sent from my HTC Vision using XDA App
android602 said:
That's why I'm using Rom manager.. because its easier for my self.. as soon as you flash clock work recovery.. I believe that you can't go wrong.. I also did something similar and my phone also staid at the HTC screen.. but went back into recovery mode and clicked on restore and went in on my old Rom
sent from g2 using DHD Rom
Click to expand...
Click to collapse
Brah its not even rooted yet
Sent from my T-Mobile G2 using XDA App
Not only does he not know what adb is... he didn't even have usb debugging enabled... Not sure that affect's whether or not he can use adb in the recovery or not... but just saying
omarsalmin said:
Not only does he not know what adb is... he didn't even have usb debugging enabled... Not sure that affect's whether or not he can use adb in the recovery or not... but just saying
Click to expand...
Click to collapse
USB debugging does need to be enabled. I know this because I always forget that step when I'm trying to use ADB on a new Android device.
If OP wants a working phone again, he'd better take his pretty-looking paperweight back to get it replaced (just drop it in your toilet first).
blackknightavalon said:
USB debugging does need to be enabled. I know this because I always forget that step when I'm trying to use ADB on a new Android device.
If OP wants a working phone again, he'd better take his pretty-looking paperweight back to get it replaced (just drop it in your toilet first).
Click to expand...
Click to collapse
WATER DAMAGE! Haha I don't think warranty covers that
I just read somewhere that in order for VISIONary to perm root you need to have S-OFF. OP made a boo boo by attempting to perm root with S-OFF.
omarsalmin said:
WATER DAMAGE! Haha I don't think warranty covers that
I just read somewhere that in order for VISIONary to perm root you need to have S-OFF. OP made a boo boo by attempting to perm root with S-OFF.
Click to expand...
Click to collapse
actually all the older guides (including the one I used to root my phone) said you ran perma root first then do s-off.
the perma root method in visionary was made before we even had s-off (only like a day before, but still before).
It sounds to me like your having the same problem that some people have been having with the rage method, only because you have s-on still your stuffed.
Basically for some reason newer phones seem to be getting a corrupt rom when perma rooting by any method. If you had s-off you could manually flash a recovery then a new rom.
Lennyuk said:
It sounds to me like your having the same problem that some people have been having with the rage method, only because you have s-on still your stuffed.
Basically for some reason newer phones seem to be getting a corrupt rom when perma rooting by any method. If you had s-off you could manually flash a recovery then a new rom.
Click to expand...
Click to collapse
The OP here used Visionary, not rage. Not sure which problem with rage you're referring to, because I've never seen anyone stuck in a boot loop just because they did rage.
His phone also seems to have been messed with before he got it, e.g. it's a G2 but running the DZ radio (which is fine, but implies someone has been doing things to it).
steviewevie said:
The OP here used Visionary, not rage. Not sure which problem with rage you're referring to, because I've never seen anyone stuck in a boot loop just because they did rage.
His phone also seems to have been messed with before he got it, e.g. it's a G2 but running the DZ radio (which is fine, but implies someone has been doing things to it).
Click to expand...
Click to collapse
2 people last week on the same day got partial bricks by using rage, I had to talk both of them through flashing a recovery manually in order to install a non corrupt rom.
I have a feeling the perma root process is corrupting roms on newer devices, not sure on the why though.
Lennyuk said:
2 people last week on the same day got partial bricks by using rage, I had to talk both of them through flashing a recovery manually in order to install a non corrupt rom.
Click to expand...
Click to collapse
You said this the other day, but I asked you for links and I don't think you replied (but maybe I missed that).
Are you sure they didn't use Visionary first ? That's usually what corrupts the ROM. Because rage is very very simple, it's not like Visionary which does complicated stuff. I really don't see how rage on its own can corrupt a ROM.
If you have any links to threads where people have not used Visionary, only rage, and have corrupted the ROM, then I'd be very interested.
steviewevie said:
You said this the other day, but I asked you for links and I don't think you replied (but maybe I missed that).
Are you sure they didn't use Visionary first ? That's usually what corrupts the ROM. Because rage is very very simple, it's not like Visionary which does complicated stuff. I really don't see how rage on its own can corrupt a ROM.
If you have any links to threads where people have not used Visionary, only rage, and have corrupted the ROM, then I'd be very interested.
Click to expand...
Click to collapse
Come on man, I shouldn't have to prove myself...
but here you go
http://forum.xda-developers.com/showthread.php?t=871288
and
http://forum.xda-developers.com/showthread.php?t=871552
both using RAGE and not VISIONARY.
Lennyuk said:
Come on man, I shouldn't have to prove myself...
but here you go
http://forum.xda-developers.com/showthread.php?t=871288
and
http://forum.xda-developers.com/showthread.php?t=871552
both using RAGE and not VISIONARY.
Click to expand...
Click to collapse
Sorry you took it that I was asking you to prove yourself. I wasn't, I was just asking for information, because I'm interested in the subject.
I'd seen those threads but do you know for certain they didn't try Visionary first, find it didn't work properly, then try rage ?
I could of course be wrong, but I don't see how rage can cause corruption because it doesn't do a lot, it just fires up a bunch of processes to exploit a way to get root. It's so much simpler than Visionary, which does a whole load of RAM disk stuff and other things that could be more risky if it goes wrong.
I suspect in those two cases that something else had already messed with their phones to cause the boot problem.
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.
Guys,
I just got a replacement phone from Verizon and need your help to get it S-OFF. I tried both the firewater method and the Rumrunner method. Neither of them worked.
I installed Weaksauce to gain root and tried firewater (method 1) first. after trying all day and night to get it to work. I decided to try Rumrunner with the same result...
Android Version : 4.3
Sence Version: 5.0
Software number: 2.10.605.1
Base 1.12.40.1112-2
Hboot: 1.55.0000
Anything else you guys need from to help me figure out why I can S-OFF?
Thanks!
robramirez007 said:
Guys,
I just got a replacement phone from Verizon and need your help to get it S-OFF. I tried both the firewater method and the Rumrunner method. Neither of them worked.
I installed Weaksauce to gain root and tried firewater (method 1) first. after trying all day and night to get it to work. I decided to try Rumrunner with the same result...
Android Version : 4.3
Sence Version: 5.0
Software number: 2.10.605.1
Base 1.12.40.1112-2
Hboot: 1.55.0000
Anything else you guys need from to help me figure out why I can S-OFF?
Thanks!
Click to expand...
Click to collapse
I don't know much about weaksauce since I haven't had to use it, but for 4.3 the temp root method of firewater is what you use.
Sent from my HTC6500LVW using Tapatalk
After trying different computers and USB cords I was able to use the Weaksauce,Firewater method to S-OFF my phone. Im back in business!
robramirez007 said:
After trying different computers and USB cords I was able to use the Weaksauce,Firewater method to S-OFF my phone. Im back in business!
Click to expand...
Click to collapse
ive tried both ways on my computer.. do you think if i used someone elses computer it would work?
What Operating system are you on? I had win 7 64bit.
uninstall everything phone related HTC Sync, drivers, everything..... install this : http://forum.xda-developers.com/showthread.php?t=2376761 (worked for me)
grab ADB and fastboot from here : http://forum.xda-developers.com/showthread.php?t=2317790
Use weaksauce to gain root and make sure you look at your phone to grant it Superuser access...
and honestly just keep trying. I tried for maybe 50 times before it worked. Switched USB port every time until it worked.
robramirez007 said:
What Operating system are you on? I had win 7 64bit.
uninstall everything phone related HTC Sync, drivers, everything..... install this : http://forum.xda-developers.com/showthread.php?t=2376761 (worked for me)
grab ADB and fastboot from here : http://forum.xda-developers.com/showthread.php?t=2317790
Use weaksauce to gain root and make sure you look at your phone to grant it Superuser access...
and honestly just keep trying. I tried for maybe 50 times before it worked. Switched USB port every time until it worked.
Click to expand...
Click to collapse
Okay I'll try that
Sent from my HTC6500LVW using xda app-developers app
so i reinstalled all drivers and out of the 3 times i tried i got to the second bottle and i switched usb ports each time so at least im getting somewhere haha
[SOLVED]
Here are my thoughts after got it S-off on the second night.
I was having problems with adb disconnecting my device or was it my computer, not sure.
I got to "adb shell", then go into phone and tap the Weaksauce app and tap on "agree", then open SU app and changed the setting to "grant".
The dialog window in SU will still pops up and you hit allow for Superuser. I think this is the reason why it never chugged before here
You have to input the "su" command in the adb window
After "grant" it is able to S-Off, you know it when the promtp windows says " Your device is now S-Off..."
ps. For some reasons Weaksauce is not stable on my phone it does take way too long to root the device and sometimes not even does it.
This may sounds broken to some ppl lol, but this is my first post and first root.
So Cheeers
Congrats. Weaksauce is just a temp root, now that your s-off, you can remove weaksauce, flash a recovery, and then flash superuser thru recovery for full permanent root.
ok
nope still not working.. im thinking that it has to be a problem with disconnecting and then it loses the root cause whenever i restart the phone i have to enable root with weaksauce again.
prichable said:
nope still not working.. im thinking that it has to be a problem with disconnecting and then it loses the root cause whenever i restart the phone i have to enable root with weaksauce again.
Click to expand...
Click to collapse
It should automatically give you root access after you installed weaksauce and SuperSU. It takes maybe 30-60 seconds after it completely boots up.
Okay good to know. it's still not finishing the first bottle though
Sent from my HTC6500LVW using xda app-developers app
prichable said:
Okay good to know. it's still not finishing the first bottle though
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
I have been at this for over a week. I've gotten as far as the 8th bottle but still haven't been able to get S-OFF.
When I first started trying firewater was version 5, now it's up to version 8.
At this point I try it once a day every night(making sure to download the latest firewater each time). I just imagine that sometime it will work.
You can try to talk to beaups in the #firewater IRC channel. He tried helping me before saying "okay Ill try to fix it in the next few days." That was over a week ago but considering he's only getting donations for this I don't hold it against him for it not working instantly for me. Head to the IRC and see if he can help out. Otherwise, I'd say keep trying.
prichable said:
Okay good to know. it's still not finishing the first bottle though
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
Did you try manually turn on weaksauce in the phone ?
Yeah I've opened it every time I do an adb reboot
Sent from my HTC6500LVW using xda app-developers app
I have an HTC One M8 from T-Mobile
S-ON and UNLOCKED
I was just wondering how to get to a point where my phone wont brick on me, soft brick or hard brick.
I have the Insertcoin mod, 3.0.6 and it keeps prompting for an update on 3.0.7. When I click download and install it, it says "installation aborted" and then it exits me out.
I tried Googling the issue, but someone said that they did it manually and it actually soft bricked their phone and they got stuck in a bootloop.
I don't want that to happen to me because I've been dealing with my friend's HTC One M7 for the last few weeks where he was doing a normal HTC Update to 4.4 and his phone got soft bricked, stuck in bootloop. Tried factory reset, flashing RUU, wiping dalvic cache, and normal cache. Put it in fastboot and tried flashing it, nothing worked.
I'm thinking the reason is because it's S-ON and LOCKED. It got to a point where I just don't know what to do with it, so I kind of gave up.
But what's a good way of getting out of soft brick if you do get stuck in it?
I figured it should be easier than this, but this is really difficult.
-Thanks
Those 2 cases are completely different from each other (OTA install on a stock M7 versus updating a custom ROM on a M8); so I would not lump the 2 together.
IMO, best way to get out of a brick is to practice some good sense preparation:
1) Achieve S-off before you try to flash the new ROM. This will give you a lot more recovery options if things go south.
2) Make sure adb and fastboot is working properly with your device
3) Make sure TWRP is up to date, and check if the latest version has any known issues of bugs
4) Make a nandroid, and keep it on the internal memory. Copy it to your computer to be safe. This is really important; and one of the easiest and most reliable way to get back up and running if you run into trouble (or simply don't like the new ROM and want to revert). Yet, a lot of folks flash ROM without making a nandroid backup. I have no idea why.
5) Have a known good ROM handy (such as InsertCoin 3.0.7 which you say has been working "perfect" for you) on your PC or possibly even on the phone's internal memory
"How to get out of a bootloop" depends on what is causing it, what errors your are getting, etc.. There isn't a silver bullet solution. I would normally say RUU is that silver bullet; but you have found that is not the case. In general, you were on the right track with your friends M7 (which I won't comment on, since I never owned that phone). But a few guidelines are given below. Its listed sequentially for the most part, meaning if a particular solution fails, proceed to the next one.
1) A "dirty flash" (wipe only Dalvik and cache, keep user data) is often possible when updating within a particular custom ROM. But check the InsertCoin thread to see what the dev recommends, or how this went for other user on 3.0.8. If a bootloop occurs, or any other random bugs, do a factory reset in TWRP (wipe user data, Dalvik and cache) and flash again.
2) Try to download the ROM again, if you're bootlooping maybe the download was corrupt. Check the MD5, if available
3) Boot into TWRP and restore your nandroid
4) Try to flash a known good ROM, or another ROM.
5) Use fastboot to wipe cache and flash recovery again. Try again to flash a known good ROM or nandroid
6) All else fails, run the RUU (requires you to relock bootloader if S-on)
7) Whatever you do, do not do a factory reset in bootloader (only within the OS Settings itself, or TWRP). There is a known bug where factory reset in bootloader on a modded phone will corrupt the phone's internal memory (including loss of nandroid and ROM zips on the memory).
Thanks!
I'll take a look at all of it.
And a nandroid backup is when you use your custom recovery to make a backup right? If so I already did that for my M8
I have S-ON for my M8, how do I get it off? And is it worth getting it off? I haven't had any problems with access or ROMS yet with it being on.
Thanks
Sent from my HTC One_M8 using XDA Free mobile app
technocrat7 said:
And a nandroid backup is when you use your custom recovery to make a backup right? If so I already did that for my M8
Click to expand...
Click to collapse
Yes, nandroid is just a generic term for TWRP or CWM backup. You'd be amazed at home many folks flash mods to their phones without making one. You're already a cut above those folks!
technocrat7 said:
I have S-ON for my M8, how do I get it off? And is it worth getting it off? I haven't had any problems with access or ROMS yet with it being on.
Click to expand...
Click to collapse
Firewater S-off: http://forum.xda-developers.com/showthread.php?t=2708464
I already told you why S-off is important in my previous response; so I don't know why you are asking "is it worth getting?"
S-off can be important for recovery as it lets you run previous ("downgrade") RUUs (perhaps not as relevant this early, as most M8 versions only have one RUU version, or none at all) and RUUs for other carrier versions (may need to change CID also).
S-off also eliminates the requirement to relock the bootloader to run RUUs. So this saves you the extra steps of relocking to run the RUU, then unlocking again. Plus, you save yourself from the position of being relocked and in a bootloop (if RUU fails), which is a bit complicated and scary situation.
Further (aside from recovery options), S-off also permits you to flash different radios, mod hboot, update firmware packages, and other things not normally permitted with S-on.
The only downside to S-off, is that it bypasses all security and safety checks. For the most part while modding, this is a good thing. But you just have to be extra careful you only flash mods meant for the M8. Since device check is bypassed with S-off, its possible to flash a mod meant for another device and damage your M8 (such as different partitioning, damage partition table, etc.). But as long as you only flash things in the M8 forum, you will be safe.
So S-off has lots of upsides, very few downsides. Of course, its up to you whether to do it or not. But to me, the choice is pretty clear.
Thanks! I'll work on getting S-OFF on my device.
Also if you do screw it up and damage your M8, can you run the nandroid backup and get to where you were or no?
Sent from my HTC One_M8 using XDA Free mobile app
technocrat7 said:
Thanks! I'll work on getting S-OFF on my device.
Also if you do screw it up and damage your M8, can you run the nandroid backup and get to where you were or no?
Click to expand...
Click to collapse
Are you talking specifically about the firewater s-off process? If so, then no, a nandroid will not reverse this. But there isn't much to "screw up". Its a very easy process, and I wouldn't worry too much about it.
Alright thanks! I'll do that and then report back later!
Sent from my HTC One_M8
I ran firewater, it says:
Whelp, this sucks, firewater cannot work on your device. No amount of refreshing, retrying, or ruuing will fix this...
Sorry it didn't work out
Okay so I found out the real issue, and for those who saw my other post, the reason it said it could not be completed is because after I launch "adb shell"
I type "su"
And nothing happens. It's supposed to prompt me for my SuperSU permission but it doesn't.
SuperSU is not listed as a device manager under my security too. And in the shell it shows a # and I've granted other applications permission before so I know I'm rooted. Any help?
I'm running InsertCoin if it matters.
Have u tried the new other s-off methods? They do cost around 20 bucks I thinm
Sent from my HTC One_M8
technocrat7 said:
Okay so I found out the real issue, and for those who saw my other post, the reason it said it could not be completed is because after I launch "adb shell"
I type "su"
And nothing happens. It's supposed to prompt me for my SuperSU permission but it doesn't.
SuperSU is not listed as a device manager under my security too. And in the shell it shows a # and I've granted other applications permission before so I know I'm rooted. Any help?
I'm running InsertCoin if it matters.
Click to expand...
Click to collapse
If it doesn't prompt you for su access and doesn't seem to do anything when running firewater it's probably because the rom is not "stock" enough. Running Maximus or other near stock roms is more likely to succeed. But anyway if you previously got the whelp message in firewater I suppose you're like many of us out of luck using that since it seems HTC has closed the exploit that firewater used on some phones.
So as MotoTurbo said, you'll probably need to use Sunshine (http://theroot.ninja) rather than Firewater. It's made by the same devs, but works on all M8's (even the ones that got whelped in Firewater). It does cost $25 but it was really simple to use and worked perfect on my phone. The newest version even seem to root your phone if it's not rooted already and then s-off's your phone after it has made sure it will work on your phone and paying using Paypal or creditcard from within the app...
The close to stock requirement also seem valid for Sunshine, but you can always try from your current rom since it won't allow you to pay until it's sure it can s-off your phone.
Ah I see.
Thank you. It sucks I'm out of luck but I think it's worth the $20. I am pretty sure I plan on keeping the phone around long enough.
One more question. The newest update for InsertCoin, or even some xposed modules are falling to work. It says "installation aborted" after not being able to extract to some directory or find it or something.
But I was installing updates fine a week ago. It's just the newest one giving me trouble. Someone said I have to go to the website manually and just put it in my SD card and zip install it through recovery.
I don't want to screw things up because I heard someone got stuck in a bootloop by doing this.
technocrat7 said:
I ran firewater, it says:
Whelp, this sucks, firewater cannot work on your device. No amount of refreshing, retrying, or ruuing will fix this...
Sorry it didn't work out
Click to expand...
Click to collapse
Later hboots don't work with firewater. What hboot version is your device on?
---------- Post added at 09:37 AM ---------- Previous post was at 09:30 AM ----------
technocrat7 said:
But I was installing updates fine a week ago. It's just the newest one giving me trouble. Someone said I have to go to the website manually and just put it in my SD card and zip install it through recovery.
I don't want to screw things up because I heard someone got stuck in a bootloop by doing this.
Click to expand...
Click to collapse
There is no reason to believe the new InsertCoin has any higher change to cause a bootloop than any other update or mod. I just manually flashed InsertCoin 3.0.8 and things went just fine. Side note: its funny I haven't been keeping up with the InsertCoin versions, and this thread made me realized how out of date I was . . . I was still on 3.0.4!
I'd relax on the "fear of a bootloop" thing. Bootloops happen, its just a fact of flashing mods. But the solution to recover is often an easy one; its just a matter of knowing or figuring out the exact trick to recover (different based on various causes). S-off is nice to have, but honestly its not an absolute necessity, as long as you've followed the other suggestions I gave previously, you are well equipped to recover from a bootloop, even in the unlikely event that one happens. S-off isn't necessary to flash ROMs, many folks do so S-on. S-off just gives you more options if you run into problems.
Ah I see.
And well, downloading 3.0.7 is aborting the installation so I guess I'll just do it manually or something haha
Also I forgot to mention..
Why doesn't SuperSU show up as a device administrator under security?
How can I fix this? Or is it not supposed to?
When doing firewater, I do "su" and there is no authentication, nothing. It's like SU doesn't exist
-----
EDIT:
also, whenever I download something from the marketplace or something it says "installation aborted" is there a reason for this?