[ota] 2.10.605.1 - new link - Verizon HTC One (M7)

Here is the link to the newest OTA 2.10.605.1
http://goo.gl/Qx4bVi
Had to change the link cuz those WANGS at dropbox said too much traffic.
MD5: BD94910A324B24D8690D689A0E0760F8
SHA-1: 4141C52B95E20E9CD394D89097D1F679A17F7D06
SHA3-256: 1A18E45BD7AC35145CE08F1769F8682CC6986E5913816207AC11B75ED1F632BD

carm01 said:
Here is the link to the newest OTA 2.10.605.1
https://www.dropbox.com/s/v10h6b5rrcygldc/OTAPkg.zip
Click to expand...
Click to collapse
Many thanks for mirroring the OTA. I've posted this to the XDA Portal.

Has rumrunner or anything been patched in this update?

fatmando2 said:
Has rumrunner or anything been patched in this update?
Click to expand...
Click to collapse
don't think so. Those that have successfully updated report still being s-offed/ unlocked.

nrfitchett4 said:
don't think so. Those that have successfully updated report still being s-offed/ unlocked.
Click to expand...
Click to collapse
S-off will survive ota's. The question is whether or not the exploit used to achieve s-off still works after the OTA for those not unlocked yet.

blackhand1001 said:
S-off will survive ota's. The question is whether or not the exploit used to achieve s-off still works after the OTA for those not unlocked yet.
Click to expand...
Click to collapse
No new Hboot in this build so it should still work.

synisterwolf said:
No new Hboot in this build so it should still work.
Click to expand...
Click to collapse
Actually that's not true.
We had 1.54.0000 in all previous versions.
This one is now 1.55.0000.
Until someone who is not yet S-Off takes the OTA and then tries to run rumrunner, we won't know if it works as is.
I tend to doubt it will and will likely be patched fairly easily for the new version by Beaups, once someone who is s-on works with him to get that done on the new hboot.
But I would not just assume that Rumrunner will work on the new hboot as is, since it has been made for specific hboots already, even ones that had the same hboot version, but came from different OTA's.

santod040 said:
Actually that's not true.
We had 1.54.0000 in all previous versions.
This one is now 1.55.0000.
Until someone who is not yet S-Off takes the OTA and then tries to run rumrunner, we won't know if it works as is.
I tend to doubt it will and will likely be patched fairly easily for the new version by Beaups, once someone who is s-on works with him to get that done on the new hboot.
But I would not just assume that Rumrunner will work on the new hboot as is, since it has been made for specific hboots already, even ones that had the same hboot version, but came from different OTA's.
Click to expand...
Click to collapse
do you have a link to the new hboot? im willing to try it and or patch it if it doesnt work. i just havent seen anyone talk about hboot 1.55
extracting it from firmware zip.

santod040 said:
Actually that's not true.
We had 1.54.0000 in all previous versions.
This one is now 1.55.0000.
Until someone who is not yet S-Off takes the OTA and then tries to run rumrunner, we won't know if it works as is.
I tend to doubt it will and will likely be patched fairly easily for the new version by Beaups, once someone who is s-on works with him to get that done on the new hboot.
But I would not just assume that Rumrunner will work on the new hboot as is, since it has been made for specific hboots already, even ones that had the same hboot version, but came from different OTA's.
Click to expand...
Click to collapse
I recently got the HTC One via Verizon and have had the OTA update to 4.3 without s-off. I attempted to use the universal rumrunner which failed pretty much immediately after going through the disclaimer and beginning the process. I'm not sure if it's because I did it wrong or if it's actually due to rumrunner not working with the the new OTA, but I'm fairly sure that I have everything set up correctly and had followed the directions very closely. I didn't think it was going to work, but I thought I'd try anyway. Thought I'd share my experience with you guys.

Somites said:
I recently got the HTC One via Verizon and have had the OTA update to 4.3 without s-off. I attempted to use the universal rumrunner which failed pretty much immediately after going through the disclaimer and beginning the process. I'm not sure if it's because I did it wrong or if it's actually due to rumrunner not working with the the new OTA, but I'm fairly sure that I have everything set up correctly and had followed the directions very closely. I didn't think it was going to work, but I thought I'd try anyway. Thought I'd share my experience with you guys.
Click to expand...
Click to collapse
No it isn't bc you ran it wrong. beaups hasn't posted a rumrunner update yet. If you aren't using rumrunner for the exact version of your current ROM it fails every time. I'm sure he'll update rumrunner when he has time but he's a busy dude like all of our devs are.

BreakingVZW said:
No it isn't bc you ran it wrong. beaups hasn't posted a rumrunner update yet. If you aren't using rumrunner for the exact version of your current ROM it fails every time. I'm sure he'll update rumrunner when he has time but he's a busy dude like all of our devs are.
Click to expand...
Click to collapse
Yes, that's what I was confirming with you guys. santod040 had suggested that it likely would not work due to the new Hboot version. I attempted to run both the universal rumrunner and the most recent one for the 1.10.605.2 ROM version, neither of which worked. I just posted here to confirm that his suspicions were true and that we will need to wait for if/when beaups has time to create a new version of rumrunner. I imagine that most of the devs and experienced users here already knew that this would happen but I just wanted to post actual experimental evidence of this being the case.

Lol I find it funny that as soon as I get a LG G2 Verizon is finally like "Oh... he doesn't have his One as his primary device anymore? Release the Kraken! (Kraken being the 4.3 update. For some reason.) Jerks. Still have my One but don't use it much anymore.
---------- Post added at 02:10 PM ---------- Previous post was at 02:07 PM ----------
Somites said:
Yes, that's what I was confirming with you guys. santod040 had suggested that it likely would not work due to the new Hboot version. I attempted to run both the universal rumrunner and the most recent one for the 1.10.605.2 ROM version, neither of which worked. I just posted here to confirm that his suspicions were true and that we will need to wait for if/when beaups has time to create a new version of rumrunner. I imagine that most of the devs and experienced users here already knew that this would happen but I just wanted to post actual experimental evidence of this being the case.
Click to expand...
Click to collapse
Oh I know. I wasn't trying to talk down to you or anything. Just stating what I know from my own past experiences when I was stupid and attempted rumrunner on the wrong version and then felt stupid when I realized what I did wrong. beaups is a beast. He'll get you guys a new version soon.

I made the mistake of updating to 4.3 O.T.A., and of course I need not wonder why Rumrunner isn't working for me. I do hope that they patch this soon. I tried different versions in 64- and 32-bit Linux, and 64-bit Windows, all with no success.
This isn't my first time modifying a P.D.A./Smartphone, either; I used to use Football's X51v ROMS, and then I rooted my Nexus One and Galaxy Nexus and put custom R.O.M.s on those, too. I just never noticed an official update taking away the ability to unlock/root a P.D.A., but then, I probably modified then sooner after getting them.

keet said:
I made the mistake of updating to 4.3 O.T.A., and of course I need not wonder why Rumrunner isn't working for me. I do hope that they patch this soon. I tried different versions in 64- and 32-bit Linux, and 64-bit Windows, all with no success.
This isn't my first time modifying a P.D.A./Smartphone, either; I used to use Football's X51v ROMS, and then I rooted my Nexus One and Galaxy Nexus and put custom R.O.M.s on those, too. I just never noticed an official update taking away the ability to unlock/root a P.D.A., but then, I probably modified then sooner after getting them.
Click to expand...
Click to collapse
Nexus devices don't have locked bootloaders that require hacks to crack.

My htc one came with the box saying software 1.6 but I tapped away in the settings to find out the previous owner updated it to 2.10.605.1 with hboot 1.55. If anyone needs any files from it let me know. This phone was never rooted before either. Currently it's sitting in the corner.
Sent from my HTC6435LVW using Tapatalk 2

keet said:
I made the mistake of updating to 4.3 O.T.A., and of course I need not wonder why Rumrunner isn't working for me. I do hope that they patch this soon. I tried different versions in 64- and 32-bit Linux, and 64-bit Windows, all with no success.
This isn't my first time modifying a P.D.A./Smartphone, either; I used to use Football's X51v ROMS, and then I rooted my Nexus One and Galaxy Nexus and put custom R.O.M.s on those, too. I just never noticed an official update taking away the ability to unlock/root a P.D.A., but then, I probably modified then sooner after getting them.
Click to expand...
Click to collapse
I came from a Galaxy S4 and I can tell you from experience never EVER take an OTA (unless it's a Nexus device I guess) because you can never be sure what they are doing. Only the first firmware on the S4 had an exploit, and anyone unlucky enough to get the next firmwares found their bootloader unable to be cracked. This is still true for them. It's been about 6 months and no one has cracked the new versions to allow an unlocked bootloader. I spent 3 months with the S4 only being able to root (hoping for an exploit) and it was miserable. I'm so much happier on the One.

Crawshayi said:
I came from a Galaxy S4 and I can tell you from experience never EVER take an OTA (unless it's a Nexus device I guess) because you can never be sure what they are doing. Only the first firmware on the S4 had an exploit, and anyone unlucky enough to get the next firmwares found their bootloader unable to be cracked. This is still true for them. It's been about 6 months and no one has cracked the new versions to allow an unlocked bootloader. I spent 3 months with the S4 only being able to root (hoping for an exploit) and it was miserable. I'm so much happier on the One.
Click to expand...
Click to collapse
Yeah I know what you mean. That's why I always ask what firmware the Phone has before I buy. I just wasn't expecting the guy to update it for me. I guess most people aren't interested in rooting/unlocking. That's why all my friends that have android complain that their devices get slow.
Out of all the android phones I had, rooted with a custom Rom or kernel and they never got slow.
Sent from my HTC6435LVW using Tapatalk 2

Related

[Q] Can I roll back from s-off and radio update

Currently have my phone rooted and running Cynogenmod 6 test 8 with the stock radio. This is an issue because I can't get my camcorder to work. I have been scared to update my radio in the past because 1, I didn't want to mess it up and 2, because I wanted to be able to go back to 100% stock at any time for warranty claims and what not.
With the unrevokedforever tool it looks like it is not easier to update radios on in any direction you want. So here are my questions.
1. Is there a way for me to backup my current radio prior to loading the latest radio?
2. Is there a place to download various radio versions to troubleshoot problems 1 radio might have with a rom?
3. Is there any way to roll back after applying the unrevokedforever fix? (can I change it back to s-on?)
I really want to try out skyraider but my understanding is I need a newer radio to do so.
There are many threads on rolling back your Radio.
As for "forever" the answer is no. While I hope/believe unrEVOked may be working on "S-ON" they have not done so yet. Since so many of these phones ultimately go bad (including blown speaker), people who have run "forever" are at risk with Verizon if they check since unrEVOked did not yet release S-ON.
If you do return your phone with S-OFF, please reply back if Verizon refuses to accept it or charges you for a new phone. There is considerable debate (in line with the requests for S-ON to be released) if VZW will refuse to replace obviously bad hardware, because S-OFF is showing.
Thanks!
Are you recommending that I update my radio the old fasion way until they come out with the s-on tool?
jdmba said:
There are many threads on rolling back your Radio.
Click to expand...
Click to collapse
I'm aware that there are tons of threads out there on this topic but thats kind of the problem. It seems everyone has a different method for doing this and they are all slightly confusing. With something as dangerous as updating the radio I don't want to be guessing anywhere along the way.
Can you recommend a good complete easy to follow tutorial on how to upgrade the radio to 2.x as well as a guide for downgrading back to stock if need be? It would be nice to find a guide that talked about both but I haven't found one yet.
Any ROM based off the 8/1 leak with Sense has a working camcorder. You can simply install that ROM and have a working camera/camcorder.
I thought those ROMs required the 2.x radio update. Do you have a list of ROMs based off the 8/1 leak? I thought the 8/1 leak was unstable.
trevoryour said:
I thought those ROMs required the 2.x radio update. Do you have a list of ROMs based off the 8/1 leak? I thought the 8/1 leak was unstable.
Click to expand...
Click to collapse
List of roms:
Sky raider
Aiccucs
jdfroyo
yasr
The actual 8/1 leak
That's all I know of....
sent from jdfroyo v2.0 EVO-lution
Sky Raider is the one I wanted to use but I read somewhere that it requires the 2.x radio.
All of the ones I listed are required to have the
2.x radio.....I cooked one of them, so I would know
sent from jdfroyo v2.0 EVO-lution
jdmba said:
There are many threads on rolling back your Radio.
As for "forever" the answer is no. While I hope/believe unrEVOked may be working on "S-ON" they have not done so yet. Since so many of these phones ultimately go bad (including blown speaker), people who have run "forever" are at risk with Verizon if they check since unrEVOked did not yet release S-ON.
If you do return your phone with S-OFF, please reply back if Verizon refuses to accept it or charges you for a new phone. There is considerable debate (in line with the requests for S-ON to be released) if VZW will refuse to replace obviously bad hardware, because S-OFF is showing.
Thanks!
Click to expand...
Click to collapse
I'll post my results sometime in the immediate future as well. I jut had to order a fru today. My phone started with random reboots and boot loops this past weekend. It's a double whammy or wonderment for me... am I going to get (justifiably) charged for the replacement and am I about to enter refurb hell? We shall see.
Just as jdmba said there's currently no way to revert back to s-on.
If you look through this users videos you should find how to upgrade and downgrade your phone (for those warrenty issues).
Link: youtube.com/user/mejdam
(Sorry for no link, not enough posts)
Sent from my ADR6300 using XDA App
Thanks
najaboy said:
I'll post my results sometime in the immediate future as well. I jut had to order a fru today. My phone started with random reboots and boot loops this past weekend. It's a double whammy or wonderment for me... am I going to get (justifiably) charged for the replacement and am I about to enter refurb hell? We shall see.
Click to expand...
Click to collapse
Wish you luck ... please remember it can take up to a month to see if VZW will refuse the warranty (which will likely take the form of a charge on your monthly bill). Let us know ... and fingers crossed that unrEVOked releases S-ON soon

install OTA update?

Hi all,
I am new here after retiring my broke dinc 1 and getting a replacement dinc2 from Asurion. I am still completely stock except for a hack on the phone to allow me to tether (no download was required).
My phone currently has software # 5.10605.9 and I was not able to run the s-off tool. I read there is an ICS OTA due soon so I thought I would just wait for that before going s-off or rooting. My only immediate need for root is so I can have Nandroid and Titanium backups. The sooner the better for that but I can wait for stock ICS before considering any custom ROMs.
I have an OTA update now that I have rejected. It says :
ADR6350_6.01.605.05-5.10.605.9
I assume this would upgrade me to 6.01.605.05 So should I let it install?
Thanks!
If you want to root/s-off dont apply that update!! You loose the ability to until you downgrade the software again which is a pain in the ass. As for not being able to currently get s-off you're gonna have to wait for some other people here to help, they can help you troubleshoot the problem.
Sent from my Incredible 2 using xda app-developers app
Thanks Triscuit,
That is what I suspected from looking around the forum. What confuses me is that I already could not run the Revolution s-off. If i don't have that latest firmware why can't I s-off now? Is it more a root issue?
You have to downgrade to 2.3.3 and hboot 97 first.
bberryhill0 said:
You have to downgrade to 2.3.3 and hboot 97 first.
Click to expand...
Click to collapse
If I wait for the ICS update with this issue go away or is the downgrade going to remain a necessity to root and s-off?
Each OTA is making s-off much more difficult. Honestly, I would downgrade your. 98hboot & s-off now. We have a very stable ICS sense 4 ROM.
Sent from my Incredible 2 using xda app-developers app
sjpritch25 said:
Each OTA is making s-off much more difficult. Honestly, I would downgrade your. 98hboot & s-off now. We have a very stable ICS sense 4 ROM.
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
Thanks, I will take your advice. Just to be certain, the warnings about not downgrading due to bootloops is for those who have the 6.01.605.05 installed so I should be fine?
That's not an issue anymore. It was in the beginning. But it was a problem that occurred after downgrading and s-off. So how knows if the ICS ota will be worse or even down-gradable.
Great, question resolved. I will happily be going s-off and rooting soon. As always the XDA community comes through for me. Thanks guys!
Actually being on the newest firmware is still an issue. Once you have been on the most recent OTA you have to run the most recent radio to run any Sense rom. The 0312 radio really sucks and does not have near as good of reception as previous ones. Do as these guys have said S Off and root now. This way you dont have to worry about it and by all means dont take the ICS OTA when or if it ever comes. Im sure once its out it wont take long before we have a flashable version.
zackspeed said:
Actually being on the newest firmware is still an issue. Once you have been on the most recent OTA you have to run the most recent radio to run any Sense rom. The 0312 radio really sucks and does not have near as good of reception as previous ones. Do as these guys have said S Off and root now. This way you dont have to worry about it and by all means dont take the ICS OTA when or if it ever comes. Im sure once its out it wont take long before we have a flashable version.
Click to expand...
Click to collapse
Thanks Zack, that is what I will do. Haven't checked since I got the phone a month or 2 ago but what is the latest/recommended tool. I was planning on using Revolution for s-off based on what I saw before. There are usually multiple tools available for rooting.
BTW- love your neck of the woods. I lived in Blowing Rock for a short time.
You have to downgrade first. I like this thread:
http://androidforums.com/showthread.php?t=444428
bberryhill0 said:
You have to downgrade first. I like this thread:
http://androidforums.com/showthread.php?t=444428
Click to expand...
Click to collapse
That is a well written set of instructions. Now I am ready to rock n roll. Thanks!

ReRoot after Sense 6.0 OTA

Anybody having any luck re-rooting after the Sense 6 OTA today?
brent372 said:
Anybody having any luck re-rooting after the Sense 6 OTA today?
Click to expand...
Click to collapse
im guessing they patched the exploit and will have to wait for a new one if you went back to locked, or s-on status.
synisterwolf said:
im guessing they patched the exploit and will have to wait for a new one if you went back to locked, or s-on status.
Click to expand...
Click to collapse
Never S-OFF'd or unlocked it.
Never perm-rooted it. Didn't even have custom recovery.
It was 100%, just rooted. It is a work-only phone so I am not overly concerned with it. But it would still be nice to be able to.
brent372 said:
Never S-OFF'd or unlocked it.
Never perm-rooted it. Didn't even have custom recovery.
It was 100%, just rooted. It is a work-only phone so I am not overly concerned with it. But it would still be nice to be able to.
Click to expand...
Click to collapse
Ah, im sure someone will find a way. they always do.
synisterwolf said:
Ah, im sure someone will find a way. they always do.
Click to expand...
Click to collapse
Tell that to the folks in the VZW s5 forums. lol
eman7131 said:
Tell that to the folks in the VZW s5 forums. lol
Click to expand...
Click to collapse
ZING
i guess i should say that HTC phones seem to be easier to root, well from the outside looking in that is. i have no clue how hard it really is to find an exploit.
newest RUU today
FLASH: Just now, I can confirm that after taking the 5-28-2014 update (4.10.605.3) Weaksauce 1.01 can't any longer attain root.
michaelbsheldon said:
FLASH: Just now, I can confirm that after taking the 5-28-2014 update (4.10.605.3) Weaksauce 1.01 can't any longer attain root.
Click to expand...
Click to collapse
And this is why I always tell people that if they want to stay rooted or unlock in the future that they shouldn't take any OTAs.
Wasnt a deal breaker for me on this phone
Sent from my HTC6525LVW using Tapatalk
not a tragedy
GrayTheWolf said:
And this is why I always tell people that if they want to stay rooted or unlock in the future that they shouldn't take any OTAs.
Click to expand...
Click to collapse
Nah, just a learning exercise!!
Was locked and S-0ff and took the 0TA to check it out. Including Weaksauce.
Easily flashed an unencrypted older RUU, then unlocked the bootloader with Scotty's recipe posted earlier.
Made firmware newest with SantoD's no-boot firmware and we're back at the races!
michaelbsheldon said:
Nah, just a learning exercise!!
Was locked and S-0ff and took the 0TA to check it out. Including Weaksauce.
Easily flashed an unencrypted older RUU, then unlocked the bootloader with Scotty's recipe posted earlier.
Made firmware newest with SantoD's no-boot firmware and we're back at the races!
Click to expand...
Click to collapse
If s-off there's no need to lock to get an OTA.
Also, keep this so you don't need to flash back to an older RUU.
http://forum.xda-developers.com/showthread.php?t=2765784

Sent One in for repair and now S-on and bootloader locked... What can I do?

I was s-off and bootloader unlocked before sending it in but they must have replaced something major to change that... Do we have anything to get s-off and unlock the bootloader on the latest update or am I stuck with stock? Thanks!
stuck with stock until an new exploit is release. i am in the same boat
d0m_ said:
stuck with stock until an new exploit is release. i am in the same boat
Click to expand...
Click to collapse
Me too. Currently the best hope appears to be the sunfire exploit. seems like jcase and beaups are currently working on an exploit and have published a lot of them previously. but nothing at the moment. I believe that you may be able to get temp root from a version of towelroot but the kernel exploits that were previously used, rumrunner, etc. are not compatible with the new kernel in 4.4.2 aka Sense 6.0.
At least that's what I have been able to determine from skimming over these forums. :good:
by sunfire do you mean sunshine? i'd gladly pay for it if it works with the m7 with 4.4.2 and sense 6. i miss AOSP
d0m_ said:
by sunfire do you mean sunshine? i'd gladly pay for it if it works with the m7 with 4.4.2 and sense 6. i miss AOSP
Click to expand...
Click to collapse
That's my main thing too, I really grew to like aosp on the one...

Root, Bootloader Unlock, S-OFF M7 Help?

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! !

Categories

Resources