Database Info

*** Rom ? ***

I see the clean Rom requires you to be on 1.85 before you can flash it. Does anyone know if all new roms coming out will be 1.85 like this ???
Reason I ask is because I'm 1.73 & from my understanding I'd have to relock, reroot, ruu etc in order to flash this Rom & not really feeling all that lol assuming we had s-off this wouldn't be an issue. But for now is this the only method ? Thanks
Sent from my HTC One X using xda premium

doin-it said:
I see the clean Rom requires you to be on 1.85 before you can flash it. Does anyone know if all new roms coming out will be 1.85 like this ???
Reason I ask is because I'm 1.73 & from my understanding I'd have to relock, reroot, ruu etc in order to flash this Rom & not really feeling all that lol assuming we had s-off this wouldn't be an issue. But for now is this the only method ? Thanks
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I'm not an expert by any stretch of the imagination but I believe we will need a proper recovery and "S-Off" before things like this become more streamlined and user friendly. I'm just sitting back and waiting for the devs to do their magic and/or I might be picking up a second HOX to do testing on.

doin-it said:
I see the clean Rom requires you to be on 1.85 before you can flash it. Does anyone know if all new roms coming out will be 1.85 like this ???
Reason I ask is because I'm 1.73 & from my understanding I'd have to relock, reroot, ruu etc in order to flash this Rom & not really feeling all that lol assuming we had s-off this wouldn't be an issue. But for now is this the only method ? Thanks
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
It looks like the ROM builders are using 1.85 just to be up to date.
I'm feeling your hesitation. I think most of us should just be patient until the dev work is done. The phone hasn't been out a month, and some amazing progress has been made. Remember when news of the locked bootloader first came out, a lot of people were suggesting it would take months to crack if it was possible at all.

Re-locking your device, upgrading RUU, and unlocking again is really a rather simple process if you want the steps to do it.

freshleysnipes said:
Re-locking your device, upgrading RUU, and unlocking again is really a rather simple process if you want the steps to do it.
Click to expand...
Click to collapse
Do you mind posting the steps?
Thanks!

How to relock bootloader to upgrade to 1.85
If you're reading this I'm going to assume you are already on 1.82 with your bootloader unlocked. I will tell you how to relock it, upgrade, and unlock it again.
Just to make things simple, open the folder where you downloaded the tools to unlock your bootloader, and copy the adb.exe AdbWinApi.dll fastboot.exe and your Unlock_code.bin to C:\Android
First to Relock your device, you will want to boot into your bootloader and select fastboot. After you've selected fastboot plug your device into your pc and open a command prompt. You'll want to type 'cd C:\Android' and then 'fastboot oem lock' and your phone will restart with a locked bootloader. Now you can upgrade to the 1.85 RUU without any issues.
Once you've finished upgrading to 1.85 you will want to boot into your bootloader again, with your device unplugged, and select fastboot. THEN plug your device in and run your command prompt again on your PC. Again, cd to C:\Android and type in the following command to unlock your bootloader again: 'fastboot flash unlocktoken Unlock_code.bin' (I've heard reports of some people having to type this command two or three times for it to work but it went the first time for me)
Now once you've finished unlocking your bootloader again you can install CWM Recovery the same way you did before.
I hope this helps!

[SOLVED!!] Customer ID Error on RUU

So my ATT One X is soft bricked and when I run RUU_Evita_UL_Cingular_US-1.82.502 It gives me the customer ID error.
I rooted, unlocked bootloader, and flashed CMR, but it is now no longer rooted and the bootloader is relocked.
I did modify the CID to "11111111" to unlock the bootloader, but without me being rooted I am unable to put the original "mmcblk0p4" back on (idk if that even matters.) I have no backups and absolutely everything is erased.
I did flash the stock recovery img file, but I don't know if it was relevant to international One X or if there is one specifically for ATT One X.
I guess a fix would be making a goldcard, without an sd card somehow....
Thanks for the Help.

Never seen that error before. Have you tried running the 1.85 RUU? I have RUU'd multiple times while still having the SuperCID so I don't think that's the issue.
Sent from my HTC One X using xda premium

_MetalHead_ said:
Never seen that error before. Have you tried running the 1.85 RUU? I have RUU'd multiple times while still having the SuperCID so I don't think that's the issue.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I was actually using the 1.7 RUU
I'll try 1.82 then 1.85. Hopefully that will work.
Thanks for the quick reply! :good:

Have you tried to relocking the boot loader?
fastboot oem lock
Then run ruu.
The ruu will flash the stock recovery.
Sent from my HTC One X using xda premium

Still not going through and getting same error....
Any ideas?
Thanks.

Are in Canada? That would mean u need to use the rogers ruu, not the evita. Or, are u positive u changed your cid to 11111111 and not ROGER001. There were tutorials in the beginning doing this before supercid 11111111 was found. But customer I'd means either, rogers or evita typically. Evita ruu won't work on rogers and vice versa:thumbup:
Sent from my HTC One X using xda premium

18th.abn said:
Are in Canada? That would mean u need to use the rogers ruu, not the evita. Or, are u positive u changed your cid to 11111111 and not ROGER001. There were tutorials in the beginning doing this before supercid 11111111 was found. But customer I'd means either, rogers or evita typically. Evita ruu won't work on rogers and vice versa:thumbup:
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
No. I'm in US on ATT network. And yes I did change the CID to 11111111 because I used that method to unlock my bootloader.
I've tried several RUUs for my phone and still get same error. If I were to verify I had changed the CID I would have to be rooted.
Is it possible to root a soft-bricked device????

What's the error number?
Depending on what it is, there are different fixes.
if you can still do fastboot commands I'd unlock the bootloader again then push the twrp with USB support.
Once you do that you can flash the rom of your choice by copying it to your phone from TWRP.
---------- Post added at 08:51 PM ---------- Previous post was at 08:44 PM ----------
I was stuck with a soft brick when I interrupted the installation of a ROM that was a bad download.
I was able to do what I said in my previous post and it fixed me right up

gunnyman said:
What's the error number?
Depending on what it is, there are different fixes.
if you can still do fastboot commands I'd unlock the bootloader again then push the twrp with USB support.
Once you do that you can flash the rom of your choice by copying it to your phone from TWRP.
Click to expand...
Click to collapse
It's error #131.
Can I unlock bootloader without root? I have tried running the adb shell in cmd, but the device cannot be found.
I was able to check if I had the SuperCID, and unfortunately it has changed back to stock.

ArcriusOneX said:
It's error #131.
Can I unlock bootloader without root? I have tried running the adb shell in cmd, but the device cannot be found.
I was able to check if I had the SuperCID, and unfortunately it has changed back to stock.[/QUOTEhmm I've never switched my CID back so I am not sure if it will work, but try this
get to the bootloader (power volume down)
from bootloader select fastboot
once in fastboot mode
with phone plugged into usb type
fastboot flash unlocktoken Unlock_code.bin just like you did to unlock the bootloader in the first place just make sure that adb, fastboot, and the unlock.bin file are all in the same directory on your computer
once you are unlocked you should be able to do the rest
Error 131 is related to using the wrong RUU for your CID SuperCID will override this error. If you flashed your CID back to the AT&T one the only RUU you can flash (I think) is the 1.85 one
Click to expand...
Click to collapse

gunnyman said:
ArcriusOneX said:
It's error #131.
Can I unlock bootloader without root? I have tried running the adb shell in cmd, but the device cannot be found.
I was able to check if I had the SuperCID, and unfortunately it has changed back to stock.[/QUOTEhmm I've never switched my CID back so I am not sure if it will work, but try this
get to the bootloader (power volume down)
from bootloader select fastboot
once in fastboot mode
with phone plugged into usb type
fastboot flash unlocktoken Unlock_code.bin just like you did to unlock the bootloader in the first place just make sure that adb, fastboot, and the unlock.bin file are all in the same directory on your computer
once you are unlocked you should be able to do the rest
Error 131 is related to using the wrong RUU for your CID SuperCID will override this error. If you flashed your CID back to the AT&T one the only RUU you can flash (I think) is the 1.85 one
Click to expand...
Click to collapse
Yeah I actually was able to unlock the bootloader already. Sorry I spoke too soon!
How do I go about pushing the twrp?
Click to expand...
Click to collapse

ArcriusOneX said:
gunnyman said:
Yeah I actually was able to unlock the bootloader already. Sorry I spoke too soon!
How do I go about pushing the twrp?
Click to expand...
Click to collapse
download it from and follow the directions here http://forum.xda-developers.com/showthread.php?t=1703626
very simple and straightforward
Click to expand...
Click to collapse

gunnyman said:
ArcriusOneX said:
download it from and follow the directions here http://forum.xda-developers.com/showthread.php?t=1703626
very simple and straightforward
Click to expand...
Click to collapse
SUCCESS!!!! :laugh::laugh::laugh:
Thank you so much! You resurrected my phone!
I'm guessing this is similar to CMR?? Looks a lot nicer.
Click to expand...
Click to collapse

ArcriusOneX said:
gunnyman said:
SUCCESS!!!! :laugh::laugh::laugh:
Thank you so much! You resurrected my phone!
I'm guessing this is similar to CMR?? Looks a lot nicer.
Click to expand...
Click to collapse
yeah I like it better myself it's faster.
glad you're all fixed
Click to expand...
Click to collapse

[GUIDE] Upgrade to ATT 2.20 OTA Safely

Ok this is a simple guide more for newer users as older members here already will know this information probably.
As people may have heard there is a new OTA for ATT. I and gunnyman bit the bullet to see if the old way of doing things ( upgrading, etc as long as you already had unlock token ) still worked with this new base and OTA.
Im proud to say yes. thanks to gunnyman and zounduser for help and hopes that I made it though un harmed lol
Disclaimer As usual this works as I am proof. However I cant be held liable if you mess up your phone! This only works for those who are already unlocked rooted etc.
Here are the steps to getting the update safely.
Prerequisites:
1. You must already be unlocked with supercid and have your Unlock_code.bin file still on your pc. ( there is a thread for this )
2. you must be rooted
3. You must have an understanding of adb and how it works (threads all over xda)
4. Have an RUU available I used 1.85
5. copy of custom recovery twrp 2.1.8.1 is what i used
6. copy of superuser in a zip available in attachments at bottom.
7. Disable HTC SYNC from running!
Here we go:
1. Reboot your phone into fastboot
2. Open a command promp and point to your adb directory. Type the following command: fastboot oem lock
This will lock your bootloader allowing you to RUU
3. Open the 1.85 RUU file.
4. Go through the RUU process.
5. Once you have finished RUUing boot the phone up if it isint booted already
6. Do a minimal setup just skip through the initial set up screens.
7. Check for att software update.
8. A box will appear saying a security update is available. enable your wifi and download it.
9. Allow the update to install
10. After the update finishes ( takes roughly 8-10 mins) some faster some longer. Boot the phone if it isin't booted ( should be ) disable fastboot under system settings power. Enable USB debugging under system developer options.
11. Attach your phone to your pc if it isint already.
12. Open a command promp and point to your adb directory.
type: adb reboot bootloader. If you get an error from adb type adb reboot-bootloader
13. Locate your unlocktoken Unlock_code.bin and place it in the same folder as your adb, fastboot, etc if its not already there from the last time you unlocked.
14. Flash your unlock token. Open a command prompt and type:
fastboot flash unlocktoken Unlock_code.bin
15. Once the token flashes before selecting yes to unlock, unplug your phone from pc. After you unplug it go ahead and select yes.
16. Once phone boots up do a minimal set up as before. Plug your phone back in to pc. Open command prompt and type: to verify unlock
adb reboot bootloader if you get an error from adb type adb reboot-bootloader
you should now see UNLOCKED at the top. If not repeat number 14 until it sticks can take a few tries.
17. If your screen says unlocked, flash your custom recovery. Locate your recovery flash it by typing in command promp: fastboot flash recovery recoveryname.img ( twrp2.1.8.1.img is mine replace with whatever yours is)
18. Once you have the recovery flashed reboot the phone.
19. Plug the phone in and select disk drive. Copy the superuser zip over to your sd card.
20. After that select charge only, open a command prompt and type:
adb reboot recovery
21. Once in recovery locate the superuser zip and flash it.
22. Reboot enjoy you should now be on OTA 2.20 Unlocked, Rooted, etc
O one thing I forgot Please hit thanks if this helped you!
Issues:
1. If you update you will get a newer hboot, you may not be able to use other older ruu's such as 1.85, etc. Recommend immediately making a backup once rooted, unlocked, etc.
2. Updating results in boot.IMG from custom roms not being flashed again. Have to flash the boot.IMG of custom Rom in fastboot as before.
3. Radio.img will not flash on new hboot either must be done in fastboot same as boot.img.

Wanna dd a radio img for me?
Sent from my HTC One X using xda app-developers app

First.. lol thanks man, nice guide!!! Site this will help our nooblets
Sent from my HTC One XL using xda app-developers app

Yeah, we want radio. Good guide too.
Sent from my HTC One X using xda premium

Thought gunnyman switched to the dark side and got a galaxy lol
Sent from my HTC One X using xda app-developers app

InflatedTitan said:
Thought gunnyman switched to the dark side and got a galaxy lol
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
He came Back!

if you have a higher hboot. u cant RUU with a lower hboot correct?

daddioj said:
if you have a higher hboot. u cant RUU with a lower hboot correct?
Click to expand...
Click to collapse
Hmm dunno that one. I was on 1.85 CleanROM 4.5 asia2.23 base when I went to new OTA. I thought as long as one had super cid RUU would work either way up or down software.

thanks for the tutorial.

john9 said:
thanks for the tutorial.
Click to expand...
Click to collapse
Welcome

eraste said:
Hmm dunno that one. I was on 1.85 CleanROM 4.5 asia2.23 base when I went to new OTA. I thought as long as one had super cid RUU would work either way up or down software.
Click to expand...
Click to collapse
well yea if you a custom rom. base dont matter b/c hboot does not get updated. i went to offical asia RUU and hboot got updated i am pretty sure u cant go backwards without s-off i could be wrong though

Any idea if root exploit works after update? People are saying it won't work on 1.85 now bc of update on server.
Sent from my HTC One X using xda app-developers app

drummaniac83 said:
Any idea if root exploit works after update? People are saying it won't work on 1.85 now bc of update on server.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
its right in the OP. as long as YOU HAVE the unlock code file from htc dev already you can update then unlock and root with the file posted. but if you didnt unlock already DO NOT UPDATE i dont think anyone knows yet
or are u talking about the original 1.85 exploit?

daddioj said:
or are u talking about the original 1.85 exploit?
Click to expand...
Click to collapse
Orignal exploit. I'm on 1.85 non root. Was going to root this weekend since CR 4.5 was final. DOH!
Sent from my HTC One X using xda app-developers app

drummaniac83 said:
Any idea if root exploit works after update? People are saying it won't work on 1.85 now bc of update on server.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I do not know that one as it was designed for 1.85 I would say no. People are working on root for the ota as we speak

eraste said:
I do not know that one as it was designed for 1.85 I would say no. People are working on root for the ota as we speak
Click to expand...
Click to collapse
Good to know. I got my One x last month from att with 1.85 loaded. I think I'm fine without the update. I'll stick to custom ROMs lol. And your awesome boot animations :thumbup:
Sent from my HTC One X

Updating now.
I prefer to run sense roms based on ATT, just seem to work a bit better imo.
Besides, with what i know of the 4.0.4 (clean rom) it is much smoother and all around much better than the 4.0.3 we got originally, may not need to run a custom rom to get the results i require (though i probably still will haha).

so if im unlocked, i can update and worry about rooting and unlocking tomorrow since i already have the unlock.bin file ?
Sent from my HTC One X using xda app-developers app

Psst; the command to rebooting to bootloader is 'adb reboot-bootloader'
...that hyphen is pretty important.

JSLEnterprises said:
Psst; the command to rebooting to bootloader is 'adb reboot-bootloader'
...that hyphen is pretty important.
Click to expand...
Click to collapse
hmm adb setup on my pc doesnt require that particular hyphen. I never have to use " either thought that was a little wierd. It works tho. I do need that hypen when doing kill-server start-server tho. Those are the only two commands that seem to not work without it for me.
thanks ill update lines.

supercid says 11111111 on 2.20 but cant unlock bootloader

i updated to 2.20 ruu and thank god i already had supercid set to 11111111.but now when i try to unlock bootloader from htcdev,it doesn't stick.please help

saketh91 said:
i updated to 2.20 ruu and thank god i already had supercid set to 11111111.but now when i try to unlock bootloader from htcdev,it doesn't stick.please help
Click to expand...
Click to collapse
very simple to fix. The fact that you got to the "ready to unlock?" screen means the unlock token works.
go into settings on the phone go to power. Turn OFF fastboot.
Power off the phone completely.
Boot to bootloader
send the unlock.bin again
this time it will stick.

saketh91 said:
i updated to 2.20 ruu and thank god i already had supercid set to 11111111.but now when i try to unlock bootloader from htcdev,it doesn't stick.please help
Click to expand...
Click to collapse
Sometimes the phone can get confused about its locked state.
To fix:
-Force reboot the phone. Hold the power button for 10+ seconds until bottom lights flash and then stop.
-Boot in to bootloader
Now force the phone to lock even if you think it is locked already.
-fastboot oem lock
-fastboot flash unlocktoken Unlock_code.bin
Sending "fastboot oem lock" tends to get the phone back on the right track so it doesn't just keep rebooting in to a relocked state.

get into bootloader manually volume down + power.

Wow, so I've been under the impression that if I updated to 2.20 via the RUU that I couldn't do anything. I know my supercid is definitely 11111111. I can still unlock the bootloader if this is the situation? Root wouldn't happen though right?

Ethere said:
Wow, so I've been under the impression that if I updated to 2.20 via the RUU that I couldn't do anything. I know my supercid is definitely 11111111. I can still unlock the bootloader if this is the situation? Root wouldn't happen though right?
Click to expand...
Click to collapse
yes root will happen.
unlock bootloader. Install twrp recovery. Flash the root package found here http://forum.xda-developers.com/showthread.php?t=1673935

Thanks so much gunny. One quick question. I got the bootloader unlocked without a problem. Now, twrp recovery...can I just do that through GooManager, or should I do it another way?

Ethere said:
Thanks so much gunny. One quick question. I got the bootloader unlocked without a problem. Now, twrp recovery...can I just do that through GooManager, or should I do it another way?
Click to expand...
Click to collapse
I think you may have to use fastboot flash recovery recovery.img because of the new limitations of the new HBOOT. It might be only for boot.imgs though

That worked rohan32 Thanks so much to both of you. Now I have an unlocked bootloader and TWRP installed. Going for root now. Thank you thank you thank you! You guys have saved me from wanting another phone!
[EDIT]Rooted as well. Again, thank you both so much!

thanks everyone i solved my problem.dint except quick replies from you guys.

Ethere said:
Wow, so I've been under the impression that if I updated to 2.20 via the RUU that I couldn't do anything. I know my supercid is definitely 11111111. I can still unlock the bootloader if this is the situation? Root wouldn't happen though right?
Click to expand...
Click to collapse
If you stay away from the AT&T cid you will be fine.
In theory things could change but at the moment so long as you have super cid prior to RUU flashing you will be fine.

OK I just got my AT&T HOX today and from what I've read hear there is no way to root it? Since I have 2.20.502.7 710RD but if I use super cid I can flash roms?

Without root you can't get super Cid

Please update the title and add "Resolved"
Sent from my HTC One XL using xda premium

No longer needed

Edit- sunshine can temp root and s-off all versions now so this method is no longer needed
If you are currently on OS 4.17.605.9 you can downgrade to 4.17.605.5 while s-on by using a signed RUU.
Why might one need this? Perhaps a sunshine app update will support it? Dunno
This will NOT wipe your phone.
Option 1
For Lollipop
Download DOTTAT_VZWM8_S_ON_5.0.1_RUU.exe and doubleclick. Allow file to extract and install dependencies and then follow on screen prompts.
Option 2
Copy 0P6BIMG.zip to root of a physical SD formatted to fat32. No exfat! No internal storage! Must be external SD formated to fat32!
Reboot phone to bootloader and follow prompts once RUU is detected by phone.
Option 3
- (use this fastboot https://www.androidfilehost.com/?fid=95784891001612150 )
Fastboot RUU mode . This method assumes you have a working ADB/Fastboot directory on your PC. Download RUUish file and place in your working fastboot/adb directory. Boot your phone to fastboot mode and connect to PC. Issue the following commands.
fastboot oem rebootRUU
###while in this mode your phone will display an HTC logo on the screen
fastboot flash zip 0P6BIMG.zip
##while in this mode you will see an HTC logo on the screen and a green status bar across the bottom of the screen. When command output ##completes it may say reboot required to flush etc... if that's the case issue a "fastboot reboot-bootloader" command and restart option 1 again.
example
## assuming flash completes and no further flushing/reboots are requested from the cmd output you can now reboot IF you simply wish to reboot the system you can issue "fastboot reboot" which will reboot system.
## expect a good 5 minute plus first boot!
Downloads Do NOT mirror these elsewhere.
5.0.1 RUU EXE (single exe don't unzip)
- https://www.androidfilehost.com/?fid=95916177934540519
md5 e0ca625c221724d1e50d27330f97ba32
5.0.1 RUU zip
- https://www.androidfilehost.com/?fid=95916177934540511
md5 6a32ce5d3f86b886d38414e27cf5246e

FIRST!
J/K...
Thanks dottat, that's good information to have! A lot of people will be happy.

Zanzibar said:
FIRST!
Click to expand...
Click to collapse
Congrats...[emoji6]
Sent from my HTC6525LVW using Tapatalk

Will this allow HTCDEV.com to work?

razieltov said:
Will this allow HTCDEV.com to work?
Click to expand...
Click to collapse
No. This just downgrades you from 4.17.605.9 to 4.17.605.5. It does not change your CID to one allowed by HTCdev.com
Sent from my HTC6525LVW using Tapatalk

Quick question from a noob:
You say in the post that this will NOT delete data from the device. But the RUU tool ReadMe has a giant, bold red warning that says "Installing the ROM Update Utility (RUU) will delete ALL information and data on your Android phone."
So... which is it? Will the tool wipe the device or not?

nic0machus said:
Quick question from a noob:
You say in the post that this will NOT delete data from the device. But the RUU tool ReadMe has a giant, bold red warning that says "Installing the ROM Update Utility (RUU) will delete ALL information and data on your Android phone."
So... which is it? Will the tool wipe the device or not?
Click to expand...
Click to collapse
Well geesssh... who you gonna believe? So you are asking me if it's my word or some silly readme? That's a conflict of interest for me to answer of sorts
NO IT WILL NOT WIPE

dottat said:
Well geesssh... who you gonna believe? So you are asking me if it's my word or some silly readme? That's a conflict of interest for me to answer of sorts
NO IT WILL NOT WIPE
Click to expand...
Click to collapse
I don't believe you...[emoji6]
Sent from my unknown using Tapatalk

bschram said:
I don't believe you...[emoji6]
Sent from my unknown using Tapatalk
Click to expand...
Click to collapse
I wouldn't either.. I've got nothing to lose!

>NO IT WILL NOT WIPE
Well gee... if you say so... I guess I'll get a 4th opinion first.

nic0machus said:
>NO IT WILL NOT WIPE
Well gee... if you say so... I guess I'll get a 4th opinion first.
Click to expand...
Click to collapse
Asking whom?

dottat said:
Asking whom?
Click to expand...
Click to collapse
Just messing with you, man.
It just finished, worked perfectly. Thank you!

dottat said:
Asking whom?
Click to expand...
Click to collapse
nic0machus said:
Just messing with you, man.
It just finished, worked perfectly. Thank you!
Click to expand...
Click to collapse
Somehow when he ran the RUU on his device, it wiped my device. Thanks for nothing :/

Hello, after exhaustive novice efforts and following the link rabbit hole, I'm here. I have a Verizon HTC One M7 on lollipop 5.0.2. I'm bootloader locked, s-on and of course not rooted. I tried this thread to no success http://forum.xda-developers.com/ver...root-root-method-bl-unlock-5-0-x-ota-t3122099. That thread deals with kingroot and Sunshine. It looks like I need to get to temproot for Sunshine to work.
This thread looks like it's using downgrading to get to a point where one can attain temproot which will enable Sunshine to run? - that is if I'm understanding correctly.
Will this work for an M7? It looks like it's for an M8.
Is there any other hope for a locked, s-on, unrooted M7 at this point? THANK YOU for what you do.

NoFussGus said:
Hello, after exhaustive novice efforts and following the link rabbit hole, I'm here. I have a Verizon HTC One M7 on lollipop 5.0.2. I'm bootloader locked, s-on and of course not rooted. I tried this thread to no success http://forum.xda-developers.com/ver...root-root-method-bl-unlock-5-0-x-ota-t3122099. That thread deals with kingroot and Sunshine. It looks like I need to get to temproot for Sunshine to work.
This thread looks like it's using downgrading to get to a point where one can attain temproot which will enable Sunshine to run? - that is if I'm understanding correctly.
Will this work for an M7? It looks like it's for an M8.
Is there any other hope for a locked, s-on, unrooted M7 at this point? THANK YOU for what you do.
Click to expand...
Click to collapse
You can get S-OFF using Java card.
http://forum.xda-developers.com/verizon-one-m9/general/m9-java-card-t3063247

When i Try to use the RUU on my M8 to revert the firmware to the earlier version of 5.01 the program get stuck saying updating (0/7) sending and doesnt budge. any help?

revert
rayparlour said:
When i Try to use the RUU on my M8 to revert the firmware to the earlier version of 5.01 the program get stuck saying updating (0/7) sending and doesnt budge. any help?
Click to expand...
Click to collapse
You need to be S-0ff to downgrade to an earlier version.

michaelbsheldon said:
You need to be S-0ff to downgrade to an earlier version.
Click to expand...
Click to collapse
LOL... you missed the thread title?

rayparlour said:
When i Try to use the RUU on my M8 to revert the firmware to the earlier version of 5.01 the program get stuck saying updating (0/7) sending and doesnt budge. any help?
Click to expand...
Click to collapse
Boot phone into fastboot mode and restart the EXE.

Used Fastboot Method
I tried the exe method and it kept getting stuck. I switched over to the Fastboot method and the flash of the ZIP file failed. Tried this twice and it failed both times. I'm S-On with a Verizon M8 (5.0.1). I'm trying to downgrade to root and while I've seen several sites say it couldn't be done, your post gave me a small bit of hope.
Let me know if you have any ideas. Gracias.