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
Related
Thanks to Paul O'Brien @ Modaco, we now have permaroot via his VISIONary+ app, which for some reason was removed from the Market. See his changelog and download site below:
http://android.modaco.com/content/t...350/10-nov-r12-test-visionary-one-click-root/
It's so exciting watching this stuff come alive!
allen099 said:
Thanks to Paul O'Brien @ Modaco, we now have permaroot via his VISIONary+ app, which for some reason was removed from the Market. See his changelog and download site below:
http://android.modaco.com/content/t...350/10-nov-r12-test-visionary-one-click-root/
It's so exciting watching this stuff come alive!
Click to expand...
Click to collapse
Reading the thread it doesn't appear that permroot works for MT4G, or is it just inconsistent?
my permaroot works just fine i even battery pulled twice today just to test that it really did stick. no problems so far either
aznpr1de808 said:
my permaroot works just fine i even battery pulled twice today just to test that it really did stick. no problems so far either
Click to expand...
Click to collapse
Is that using visionary+ or my guide? BTW, What's up from a flying tiger!
It is unfortunate Google is shutting down non-malicious useful tools like this (they also remove a rooter I had used on my N! - easy root). Unless they are being threatened by legal action from HTC or others - they should stay out of the fray.
I did not delete VISIONary for this reason 9in case i had to do a factory reset and re-root). Now, the new version with perm root will make having to do it again much easier.
I hope the below is not really what it looks like (from the download link):
11/10/2010 2:43:25 PM Detected: Exploit.Linux.Lotoor.g Firefox http://pepsi.romraid.com/files/paul/com.modaco.visionaryplus.r12.apk/assets/ratc
Oh well - shut off my antivirus and downloaded file onto the SD card.
Installed it and tested it. I had gone the s=off route yesterday, so I un-rooted it (apps needing root would then not work), re-rooted it, temp and permanent. It rebootedagain, and apps that need root work OK again (it was not set to root on boot-up). App looks pretty good.
Can some more people comment on if r12 is working for MT4G permroot? And do we still have to do the other steps manually to turn S-off?
I was able to get it to work for me. I was temprooted and then applied permaroot. I haven't done S-Off yet, but I don't see a reason to do that yet anyhow.
grankin01 said:
Is that using visionary+ or my guide? BTW, What's up from a flying tiger!
Click to expand...
Click to collapse
I can confirm.. I uninstalled VISIONary after a temproot and then the permroot attempt and ran quickboot and I actually got su..
VISIONary r12 permroots the Touch.. Yes..
Now @gankin just needs to mod the latest kernel bits for this.. but otherwise.. just like that it works..
allen099 said:
I was able to get it to work for me. I was temprooted and then applied permaroot. I haven't done S-Off yet, but I don't see a reason to do that yet anyhow.
Click to expand...
Click to collapse
Do we need to uninstall the Visionary app from the Market before we install the v12?
I seem to be having problems after I temp root my phone I go and press the permaroot button and nothing happens
Sent from my HTC Glacier using XDA App
Anyone try permaroot with pre ota (2.2 not 2.2.1). I have no success by any means, need the damn ota...
I tried to permroot but failed...temproot worked just fine.
Sent from my HTC Glacier using XDA App
Ok I was able to permroot mine you must be quick when you click permroot to press allow superuser permision.
I have a few questions not about the other options in the new visionary r12:
To be able to load custom ROMS etc which options do we need in visionary+ I assume we need the rw option, but what is the other option to run visionary.sh after root?
Also do we need to turn S-off? Just trying to get everything ready waiting on the recovery app.
So in the same way that the manual way wouldn't perm root my phone, neither does visionary r12. It just doesn't stick, period.
RealityDesign said:
So in the same way that the manual way wouldn't perm root my phone, neither does visionary r12. It just doesn't stick, period.
Click to expand...
Click to collapse
When I did the manual way, I wasn't permrooted when I booted back up, I had to run visionary (the temporary one) one more time and rebooted and then I was permrooted.
itmustbejj said:
When I did the manual way, I wasn't permrooted when I booted back up, I had to run visionary (the temporary one) one more time and rebooted and then I was permrooted.
Click to expand...
Click to collapse
So it's the same app but different options (temp root/perm root) correct?
And the manual method is required to get S-OFF so that we can flash a custom recovery, yes?
Just recapping to make sure I understand.
Phateless said:
So it's the same app but different options (temp root/perm root) correct?
And the manual method is required to get S-OFF so that we can flash a custom recovery, yes?
Just recapping to make sure I understand.
Click to expand...
Click to collapse
Thats what I'm gathering..
From what I've read, even if we do achieve perm root with the app, we will still need to manually turn s-off to flash a custom recovery (and have it stick).
So my question is, does the permroot option (within visionary) even do anything for us MT4G guys? If we still need to go the manual ABD route to turn s-off, is the permroot option within Visionary just a short cut in the process to achieve s-off?
Everything seemed clear on what I was planning to do till the permaroot option lol
I tried this earlier and it is not a true root, s is still on after doing everything. If you still have to do other steps whats the point of visionary? Lol.
Has anyone actually gotten a true perm root with visionary with s=off? How did you do it?
Sent from my HTC Vision using XDA App
Arcadia310 said:
I tried this earlier and it is not a true root, s is still on after doing everything. If you still have to do other steps whats the point of visionary? Lol.
Has anyone actually gotten a true perm root with visionary with s=off? How did you do it?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
To get s=off you have to use the manual method.
My MyGlacier 4G MINE!!!
grankin01 said:
To get s=off you have to use the manual method.
My MyGlacier 4G MINE!!!
Click to expand...
Click to collapse
IMHO, if people have to use tools like Visionary because they don't understand how to do it manually - they shouldn't root their phones. Visionary is a shortcut, not a substitute for knowledge. ADB is a must-have as well. I can't wait to see all cries for help once people start soft-bricking their phones because they cant read directions, don't know how to access ADB or, in general, don't know a singel linux command.
G1 forums were fairly decent until 1-click root was introduced and made it accessible for idiots to mod without having a slightest clue. I have a feeling MT4G forums are heading that way too.
Let the fun begin...
I have a problem rooting a friend's phone using gfree.
When I rooted my phone, I used a different method since it was in the early days of rooting the desire z. I've followed the instructions found here: http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
Everything seems to work correctly until I execute ./gfree -f
At this point I get the error "Error reading input file" and the phone gets stuck (I have to remove battery to boot it up again).
Anyone has had this problem before? Possible fixes? Any help is appreciated.
Has he done the OTA update??
Edit: @Dan.. Oh yeah... my bad
MacaronyMax said:
Has he done the OTA update??
Click to expand...
Click to collapse
Look at the picture
The # is there.
Which means root.
WHich means rage / VISIONary worked.
He hasn't OTA'd
yea rage seems to have worked, i'm just getting that error at the end and can't proceed with the rooting.
If I'm not mistaking I believe he is rooted.already ( don't flame me if he's not I can't really see the pic on the xda app ....)
tsubus said:
yea rage seems to have worked, i'm just getting that error at the end and can't proceed with the rooting.
Click to expand...
Click to collapse
Sent from my HTC Vision using XDA App
unfortunately i am not rooted (i can't even sync after ./gfree -f, gives an i/o error)
tsubus said:
unfortunately i am not rooted (i can't even sync after ./gfree -f, gives an i/o error)
Click to expand...
Click to collapse
You're running as root though (# prompt), so you have at least got temp root even if it isn't permanent.
You're getting an error when it tries to disable the write protection though, so I am guessing it is indeed temp root and you lose it after a reboot.
What ROM/kernel are you running exactly ? Some don't work with gfree.
Am having the exact same problem as Tsubus.
Orginal rom, no updates applied.
details:
Vision PVT SHIP S-ON
HBOOT-0.85.0005
MIRCOP-0425
RADIO-26.03.02.26-M
Did try Visionary, rage and gfree03 without luck
stringbean82 said:
Am having the exact same problem as Tsubus.
Orginal rom, no updates applied.
details:
Vision PVT SHIP S-ON
HBOOT-0.85.0005
MIRCOP-0425
RADIO-26.03.02.26-M
Did try Visionary, rage and gfree03 without luck
Click to expand...
Click to collapse
Which original ROM exactly though ? There are loads.
steviewevie said:
Which original ROM exactly though ? There are loads.
Click to expand...
Click to collapse
Android version 2.2
Kernel 2.6.32.21
Software version 1.34.405.5
stringbean82 said:
Android version 2.2
Kernel 2.6.32.21
Software version 1.34.405.5
Click to expand...
Click to collapse
Hmm, gfree should work fine on that version
What happened with Visionary ? I wonder if Visionary messed things up somehow ?
How much of a pain would it be for you to re-flash the ROM and see if it's happier after that ? (e.g. how difficult to get your data/settings back ?)
Let's see if anyone can come up with another idea.
Am available for any test, been busy for the last 6 hours at work trying to get it to work.
stringbean82 said:
Am available for any test, been busy for the last 6 hours at work trying to get it to work.
Click to expand...
Click to collapse
Well, it should work perfectly with that ROM version. That's the same version that I'm using. If you don't mind re-flashing your ROM (with the same version) it could be worth a try. I am not saying that I think it will definitely fix it, this is a long shot, but I can't think what else to suggest right now.
Edit - have you also tried the older method using the "insmod" command, the one in the threads on rage ? That would be interesting to double-check that the insmod is coming up with the "wrong" error message, similarly showing that it failed to disable the NAND write protection.
doesn't work with this on my friend's phone:
android version 2.2
kernel 2.6.32.21
software number 1.34.166.5
haven't tried visionary, only gfree...might give visionary a try later on if you guys think it could work.
Tomorrow am going to load the same image as i have now on it and then try again.
What is the recommended method?
Sent from my HTC Vision using Tapatalk
tsubus said:
doesn't work with this on my friend's phone:
android version 2.2
kernel 2.6.32.21
software number 1.34.166.5
haven't tried visionary, only gfree...might give visionary a try later on if you guys think it could work.
Click to expand...
Click to collapse
Don't try to perm-root with Visionary it'll soft-brick... Just a warning
alright, thanks for the heads-up.
not sure what i should try now though, it kind of seems like there is no way to root it atm. i guess time will tell.
same problem for me =/
You probably need to push superuser to your phone in a different way. I had a similar problem using gfree. Hold on and I will send you a link to the nook method that I used. You do this after you run rage and are in the root shell on terminal emulator. (Pound symbol at the beginning of the command line). once you push superuser this way it locks in itself. then you can run the ./gfree command hopefully. I never had a problem with that command before I got the proper superuser but it might help you. Wait 1 and I will send the link.
Sent from my HTC Vision using XDA App
http://nookdevs.com/NookColor_Installing_su_and_the_Superuser_app
That should take you to the proper page. Don't run the first command that starts with unzip. Its easier to download the superuser zip to your desktop and then extract it to the root of Your android sdk tools folder. Aka put it in the tools folder and not inside any other folder that might be in your tools folder. Then run the next two commands on adb after you navigate to your androidsdk/tools folder to install. The next commands that you run in your root shell are run with terminal emulator. You should still be in a root shell if you used rage and haven't rebooted your phone. Pound sign will be present. Pm me if you have problems or if you are confused in any way.
Sent from my HTC Vision using XDA App
Hi all
For the last few weeks I have been trying to fix my HTC Desire back to some sort of working state. After awhile, I managed to get back to stock (from CM7), but soon realised I had the USB brick and SD Card issue. For info I used the stock HTC 2.3 Gingerbread RUU and used Alpharev PB99IMG_downgrade.zip for HBOOT (I was using Alpharev S-OFF with CM7).
So, I followed this guide, http://android.modaco.com/topic/309939-usb-brickrickrolledb0rked-fixed/ and managed to mount the SD Card. However, I could not get the update.zip file to apply because I was no longer rooted.
So I followed the guide linked in the USB brick article, http://android.modaco.com/topic/307...ide-now-with-hboot-080-and-os-to-121-support/ and soon realised that I did not have the HBOOT version required. Either 0.75 and below, or, 0.80 and below. I have 1.02.0001.
Not a problem, I thought. I will follow this guide to downgrade, http://forum.xda-developers.com/showthread.php?t=768256 as it specifically says that "...the downgrade does not depend on any version of HBOOT" which is what I need. However, first step is to get a working Goldcard. This is where I start to get into trouble and I'm already losing track of what I'm doing, but I soldier on...
How do I create a Goldcard? I followed this guide, http://android.modaco.com/topic/305672-creating-a-goldcard/ and got stuck at running the ADB command as because my USB is broken, Windows 7 (x64) refuses to see the Phone. Luckily, my father has the same phone, so I put my SD Card into his Desire and managed to create a Goldcard (he is running CM7 on his Desire too).
So Goldcard in hand, I go back to the downgrade guide and then spot my next issue. I can't get Windows to see the phone to use ADB commands and I also can't get Windows to see the phone when it is booted up (the charge light won't even come on now), meaning I can't run the downloaded application.
Not to be outdone I went back to the Rooting Guide and tried both of the downloads with the "step1-windows.bat" command just in case they did work, but both give an error, which on searching, is to do with the HBOOT version being incompatible.
I tried putting on the PB99IMG_downgrade.zip file from Alpharev again, then re-running the HTC 2.3 Gingerbread stock RRU and taking the ROM.zip folder and re-loading it on to the phone, but it hasn't changed the HBOOT version. So my cry for help is.... how can I downgrade HBOOT without using ADB commands or having to have Windows detect my phone? I'm basically stuck with Fastboot and my SD Card.
Even though my phone looks stock, I can't call people as it disconnects straight away, the USB is broken and the battery drains stupidly quickly.
Thanks for any help!
now this IS a sticky situation.. well done on what you've done so far by the way.
On my guide there's a section on how to temproot and flash recovery without USB connection, then flash a recovery that restores usb functionality, but it's only been tested on 2.2 and S-OFF... could be worth a try though
bortak said:
now this IS a sticky situation.. well done on what you've done so far by the way.
On my guide there's a section on how to temproot and flash recovery without USB connection, then flash a recovery that restores usb functionality, but it's only been tested on 2.2 and S-OFF... could be worth a try though
Click to expand...
Click to collapse
Hi bortak,
Thanks for the reply. It is a bit of a strange situation I agree. I've been putting off signing up and posting for help as I feel quite dumb for breaking my own phone, but I have to admit defeat on this one.
I saw your reply also in this similar topic, http://forum.xda-developers.com/showthread.php?t=1290391, so I will definitely try your suggestion and report back.
Appreciate you taking the time to post.
Thanks.
USB Brick on official GB 2.3.3 and HBoot 1.02
I still have the same problem and tried to get temp. root with the "rageagainstthecage" and terminal emulator method:
http://forum.xda-developers.com/showthread.php?t=691639&page=73
But I had no luck. There is no way to write the Misc patition... I´d like to downgrade (to Froyo), but without USB it seems to be impossible. Alpharev did not work. Revolutionary needs USB !USB brick with official Gingerbread, S-ON and HBoot 1.02 seems to be a dead end so far....
dexterm1 said:
I still have the same problem and tried to get temp. root with the "rageagainstthecage" and terminal emulator method:
http://forum.xda-developers.com/showthread.php?t=691639&page=73
But I had no luck. There is no way to write the Misc patition... I´d like to downgrade (to Froyo), but without USB it seems to be impossible. Alpharev did not work. Revolutionary needs USB !USB brick with official Gingerbread, S-ON and HBoot 1.02 seems to be a dead end so far....
Click to expand...
Click to collapse
well this sucks, it's also strange how there is so many people at once with exactly same problem as well!
you could call HTC and ask if they'd fix it for you, and say that this happened after you did the update.
bortak said:
well this sucks, it's also strange how there is so many people at once with exactly same problem as well!
you could call HTC and ask if they'd fix it for you, and say that this happened after you did the update.
Click to expand...
Click to collapse
I´ll have a try
just fixed my desire 1 hour ago and it works.
look at this http://forum.xda-developers.com/showthread.php?t=1296916
What I did:
I was able to connect my pc and phone through wi-fi and adb worked (adb connect phones-IP-address ) and then pushed, chmod'd 755 and executed zergrush. Gained root via cmd with adb shell in windows and after that I just pushed flash_image and mtd0.img to phone and ran it like you supposed to in the guides (chmod 755 and execute). Rebooted and voila! USB connection is working and now my phone signal isn't dropping anymore - phone fixed!
I fixed my unrootet Phone (official GB 2.3.3, HBoot 1.02, S-ON, USB Brick)!!!!
I wifi connected with adb and got temp root with zergRush!
Then from cmd in adb shell I flashed the misc with mtd0.img!
Rebooting and everything was fine ))
Many thanks to all of you!!!
dexterm1 said:
I fixed my unrootet Phone (official GB 2.3.3, HBoot 1.02, S-ON, USB Brick)!!!!
I wifi connected with adb and got temp root with zergRush!
Then from cmd in adb shell I flashed the misc with mtd0.img!
Rebooting and everything was fine ))
Many thanks to all of you!!!
Click to expand...
Click to collapse
Hi, pls. tell us how did you managed to connect your unrooted phone over wifi with adb? I get only "unable to connect to ... ip ..."
You may now want to install 4ext touch recovery now u have sorted it. This has a USB unbrick feature and will save a lot of time should this happen again
exocetdj said:
You may now want to install 4ext touch recovery now u have sorted it. This has a USB unbrick feature and will save a lot of time should this happen again
Click to expand...
Click to collapse
I can not install anything without root, and i can't root 2.3.3 software.
try this,
http://theunlockr.com/2010/09/20/how-to-root-the-htc-desire-unrevoked-method/
mine was 2.3.3 after the manual update but now rooted
exocetdj said:
try this,
http://theunlockr.com/2010/09/20/how-to-root-the-htc-desire-unrevoked-method/
mine was 2.3.3 after the manual update but now rooted
Click to expand...
Click to collapse
Ignore this, you can't root 2.3.3 with unrevoked
r5_alpine said:
I can not install anything without root, and i can't root 2.3.3 software.
Click to expand...
Click to collapse
Use revolutionary instead
http://theunlockr.com/2011/08/02/ho...android-phone-using-the-revolutionary-method/
Instructions are all there, read them several times
Sent from my HTC Desire using XDA
eddiehk6 said:
Ignore this, you can't root 2.3.3 with unrevoked
Use revolutionary instead
Instructions are all there, read them several times
Sent from my HTC Desire using XDA
Click to expand...
Click to collapse
I can't do both of this, because my phone is not recognized by PC in any way, i must root it without PC.
If you have 2.3 connect to same wifi as your pc and adb connect to your phone's IP. Then run zergrush and you will have temproot over adb from your pc. Then you can flash your mtd0.img and your brick will be resolved
Sent from my HTC Sensation Z710e using XDA
matus.karahuta said:
If you have 2.3 connect to same wifi as your pc and adb connect to your phone's IP. Then run zergrush and you will have temproot over adb from your pc. Then you can flash your mtd0.img and your brick will be resolved
Sent from my HTC Sensation Z710e using XDA
Click to expand...
Click to collapse
I have tried this too, but i get unable to connect error. And on phone i can't enable adb over wifi without root. I have tried almost everything what i found, and im still on the same step.
r5_alpine said:
I have tried this too, but i get unable to connect error. And on phone i can't enable adb over wifi without root. I have tried almost everything what i found, and im still on the same step.
Click to expand...
Click to collapse
Are you on 2.3 from htcdev? Because that version has adb over wifi enabled by default as it is a dev version. Are you S-on?
matus.karahuta said:
Are you on 2.3 from htcdev? Because that version has adb over wifi enabled by default as it is a dev version. Are you S-on?
Click to expand...
Click to collapse
Yes i have flashed it via bootloader from sd card, hoping to resolve the problem, but it become worse. With previous firmware there was no problem temp rooting, now it seems impossible. And yes i am S-ON.
r5_alpine said:
Yes i have flashed it via bootloader from sd card, hoping to resolve the problem, but it become worse. With previous firmware there was no problem temp rooting, now it seems impossible. And yes i am S-ON.
Click to expand...
Click to collapse
Have you tried running RUU while connected with fastboot? Have you tried flashing anything while in fastboot? I am just throwing suggestions at the wall, anything might work or brick...
matus.karahuta said:
Have you tried running RUU while connected with fastboot? Have you tried flashing anything while in fastboot? I am just throwing suggestions at the wall, anything might work or brick...
Click to expand...
Click to collapse
The phone is not seen by pc in any statement, not in bootloader, or fastboot, or recovery. I need to either downgrade to 2.29 rom version, or to root it in some way.
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 Everyone! I have a HTC One M7 with Verizon and am looking to unlock bootloader, S-OFF, as well as root mainly. I have tried Sunshine which tells me I have to root first. I have also tried, Kingroot, Moonshiner and most of all of the other programs.Upon looking up this I found I need to unlock my bootloader. To do this I need to S-OFF. I didn't catch HTCDEV in time to unlock the bootloader since Verizon blocked it so I would appreciate anyone who could help me root, unlock the bootloader and S-OFF. Thanks! I forgot to add, I am running HBOOT 1.6.1.
mnorris298 said:
Hi Everyone! I have a HTC One M7 with Verizon and am looking to unlock bootloader, S-OFF, as well as root mainly. I have tried Sunshine which tells me I have to root first. I have also tried, Kingroot, Moonshiner and most of all of the other programs.Upon looking up this I found I need to unlock my bootloader. To do this I need to S-OFF. I didn't catch HTCDEV in time to unlock the bootloader since Verizon blocked it so I would appreciate anyone who could help me root, unlock the bootloader and S-OFF. Thanks! I forgot to add, I am running HBOOT 1.6.1.
Click to expand...
Click to collapse
If you're on lollipop, pretty much only things I can think of that have worked are Kingroot (You have to try it MULTIPLE MULTIPLE TIMES) , N if that doesn't work on the latest version, try older versions (I remember old versions working for a few ppl, I believe it was like version 4.5 or 4.50.-something). The way kingroot works, u have to run it like sometimes 10-20-30 times of it saying failed, and eventually it works. I successfully did it on 2 of my friends m7's... (Not my own, I Sunshined back on 4.4.2)
Then, when/if u get kingroot to work, run sunshine...
Alright I'll keep trying kingroot
Sent from my HTC6500LVW using Tapatalk
Any other ideas? Kingroot just keeps rebooting my phone. If not rebooting it fails regardless. Ran at least 40 times
Sent from my HTC6500LVW using Tapatalk
mnorris298 said:
Any other ideas? Kingroot just keeps rebooting my phone. If not rebooting it fails regardless. Ran at least 40 times
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Only other way for a vZw m7 is to find somebody who has a Java card, and make arrangements to ship / drive your phone to them, and they'll b able to S-off, bootloader unlock, & root it within 5 mins. Java cards from what I understand r VERY expensive, but over in the vzw M9 thread, there's a whole thread that's just/only for the topic of arranging to get your phone unlocked with a Java card owner, as Sunshine still to this day has never worked for the VZW variant of the M9. I know there are some VERY reputable and well known devs over there who would be willing to hook u up and have been doing it for others on xda for over a year now, (for quite cheap I understand) -although I highly recommend tossing em a donation at least for their troubles.... Maybe @dottat can point u in the right direction
mnorris298 said:
Any other ideas? Kingroot just keeps rebooting my phone. If not rebooting it fails regardless. Ran at least 40 times
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Danngg.. I wonder if this is a result of Google's continuous security updates? When I ran Kingroot to temp root before running Sunshine, it rooted on like... the first or second try... this was also after I'd foolishly tried every single root exploit that were designed in the days of Android 1.x and Gingerbread, which might have weakened some security if it didn't break it completely.. The binaries are called psneuter and gingerbreak, if you wanna give it a shot. There's also Rumrush, Firewater, Towelroot... probably others that I can't think of. None of them are likely to give you root, but if you use all of them and then use Kingroot, maybe Kingroot will work. I would personally do that sooner than running Kingroot and having my phone reboot 300 times...
So, I guess all you can do is keep trying.
I have verizon htc one m7 and i want to root it i have tried
Kingoroot
Kinguser
Firewater
Rumrunner
Rootgenius
Etc
Android kitkat 4.4.3 htc6500lvw plz help
mnorris298 said:
Hi Everyone! I have a HTC One M7 with Verizon and am looking to unlock bootloader, S-OFF, as well as root mainly. I have tried Sunshine which tells me I have to root first. I have also tried, Kingroot, Moonshiner and most of all of the other programs.Upon looking up this I found I need to unlock my bootloader. To do this I need to S-OFF. I didn't catch HTCDEV in time to unlock the bootloader since Verizon blocked it so I would appreciate anyone who could help me root, unlock the bootloader and S-OFF. Thanks! I forgot to add, I am running HBOOT 1.6.1.
Click to expand...
Click to collapse
I can not help you with the s-off and unlocking bootloader but Ican tell you how to root your phone.
Install WeakSauce2.apk, and superuser in that order and you are done.
solve it?
Did you find a way to do s-off? because I can't do it, It rooted but I can do the s-off
sandraf said:
Did you find a way to do s-off? because I can't do it, It rooted but I can do the s-off
Click to expand...
Click to collapse
I did it as follows. I used KingRoot and obtained its form of root. Then I ran Sunshine, which requires that you first are rooted. Sunshine reboots mid-process, losing root. So I ran KingRoot again, obtaining root. Then I ran Sunshine and it took up where it had rebooted, and got s-off. Then I found a script to eliminate the KingRoot temporary root. It did not exactly fit my file system, so I by hand made all of the changes indicated in the script (some of the changes in the script were not really important, some referred to files I did not have, etc., but I was able to change the important ones.) When I rebooted, I got the SuperSu pop-up to update, which I did, and ended up with a Verizon M7 with unlocked bootloader, s-off, and rooted.
mozhno said:
I did it as follows. I used KingRoot and obtained its form of root. Then I ran Sunshine, which requires that you first are rooted. Sunshine reboots mid-process, losing root. So I ran KingRoot again, obtaining root. Then I ran Sunshine and it took up where it had rebooted, and got s-off. Then I found a script to eliminate the KingRoot temporary root. It did not exactly fit my file system, so I by hand made all of the changes indicated in the script (some of the changes in the script were not really important, some referred to files I did not have, etc., but I was able to change the important ones.) When I rebooted, I got the SuperSu pop-up to update, which I did, and ended up with a Verizon M7 with unlocked bootloader, s-off, and rooted.
Click to expand...
Click to collapse
What script did you find? Do you mind sharing it? So that I try your method... because I too have the same htc6500lvw and have tried all of the above methods using KingRoot and sunshine. :good: thanks I'm advance
Maonela said:
What script did you find? Do you mind sharing it? So that I try your method... because I too have the same htc6500lvw and have tried all of the above methods using KingRoot and sunshine. :good: thanks I'm advance
Click to expand...
Click to collapse
Here are two sites I had left in my bookmarks:
http://zidroid.com/how-to-get-ride-and-replace-kinguser-with-supersu-app/
https://androidmtk.com/replace-kinguser-with-supersu
You could probably find more.
The only way this worked for me was to read the script and figure out what the critical replacements are. You should note that the critical steps involve files that have the immutable bit set, and the scripts show a two step process of first changing the immutable bit, and then deleting the file. I did these by hand, since some of the files that needed replacing were not in the sub-folders indicated in the scripts.
HI, fellow m7vzw user here. Let me share my experience. Around mid 2015 last year HTC released an update for lollipop that patched kingroot to be used to root its device. But all hope is not lost as you can doengrade back to the version of lollipop that is vulnerable to Kingroot exploit. I discussed this method last year around October with some other htc one m7 vzw owners. One of them pointed out that as a failsafe in case something went wrong with htc's firmware, it can be downgraded back ONE version to avoid that faulty firmware. For example if they release a version in January, February and March (March firmware being faulty as example). You can downgtade back to the previous firmware using fastboot and the required firmware files. We never tried to downgtafe again from Febraury to January because when we were already rooted and s-off after one downgrade ???.All files on links for the files are located on the Verzion HTC one forum..... i'll try to find the post containing proof for you.
---------- Post added at 07:56 PM ---------- Previous post was at 07:49 PM ----------
Sorry for the long post btw. Here's the link to the thread that taught me how to downgrade. http://forum.xda-developers.com/ver...-3-s-users-t2919442/post64629850#post64629850 Today im happily S-off and running santod's GPE 5.1.1 cfw. Good luck! !