[S-Off] Convert to HTC USA Unlocked 1.12.617.6 - HTC One A9

this guide is probably not user friendly. im a long time htc user, and am just showing how i successfully converted my ATT A9 to the USA Unlocked A9 version 1.12.617.6
this should work for any A9 with the MID: 2PQ912000
if you have another MID like 2PQ910000, it may work but i cannot test -see step 2b (thanks @alray)
i also cannot test to see if this ACTUALLY unlocks the phone, because i dont have a nanosim from another carrier
finally, i am not responsible if you mess your device up and make it unusable, this worked for me.
i used SuperCID, 11111111, but this also may work with the cid of the unlocked phone, BS_US001.
Note: if youre using a different cid and/or mid you will not be able to install OTA updates. (thanks @htconeXX and @JochenP)
Extra Note: if you used superCID already, you can change it and try OTA again without reflashing, given you have not modified /system (tested by me)
prerequisites:
1.12.617.6 RUU: Here
drivers, bootloader unlocked from htcdev, s-off using sunshine YES PAY FOR IT IT WORKS AND THEYRE GREAT PEOPLE theroot.ninja
fastboot and ability to use command line
steps:
step 1: boot into DOWNLOAD MODE
this is the BLACK SCREEN that you can get to from the bootloader
from cmd, run
Code:
adb reboot bootloader
(or use the hardkey method)
which which will take you to the WHITE BOOTLOADER SCREEN
from there, navigate to "reboot to download mode" using the volume buttons and select with the power button
or
by turning off the phone, and holding the power + volume down buttons until you see the htc logo
step 2 change cid
once youre in the BLACK DOWNLOAD MODE screen, from your computer run
Code:
fastboot oem writecid BS_US001
from the command line (or fastboot oem writecid 11111111 for SuperCID)
(step 2b if your mid is something other than 2PQ912000 you can change it with the command
Code:
fastboot oem writemid 2PQ912000
which should allow you to flash the RUU (thanks @alray) )
then run
Code:
fastboot reboot-bootloader
step 3 go back into download mode, verify it says the cid youve chosen , and run the RUU you downloaded from above. follow the onscreen instructions to update your phone to 1.12.617.6
step4: re root, install recovery.
supersu BETA now supports /system-less root
you can find the TWRP flashible package here: http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
SYSTEMLESS SUPERSU is no longer beta, its WIP, and the post can be found HERE
the most recent supersu as of 12/31/15 is v2.65
(any supersu should suffice, but you know what they say, latest is greatest)
First flash twrp
Code:
fastboot flash recovery <recovery.img>
then boot into recovery and FORMAT YOUR DATA PARTITION
IGNORE PASSWORD PROMPT
GOTO WIPE>FORMAT DATA> and TYPE YES
reboot recovery
then sideload <supersu>.zip you downloaded earlier
go to advanced> adb sideload in TWRP
then from your computer run
Code:
adb sideload <supersu>.zip
which will patch your bootloader, and root your device

Ae3NerdGod said:
if you have another MID like 2PQ910000, it may work but i cannot test
Click to expand...
Click to collapse
Someone did it in the ruu thread.
Code:
fastboot oem writemid 2PQ912000
nice guide :good:

alray said:
Someone did it in the ruu thread.
Code:
fastboot oem writemid 2PQ912000
nice guide :good:
Click to expand...
Click to collapse
very useful. didnt know it was that easy on the a9. someone had to mess with hex to change the mid on the m8 i believe

Works with mobile Europe this method?,Thanks
Enviado desde mi HTC One A9 mediante Tapatalk

jureca said:
Works with mobile Europe this method?,Thanks
Enviado desde mi HTC One A9 mediante Tapatalk
Click to expand...
Click to collapse
Should work on any UHL variant

alray said:
Should work on any UHL variant
Click to expand...
Click to collapse
Ok Thanks.
Enviado desde mi HTC One A9 mediante Tapatalk

If it helps, I have an s-off, unlocked bootloader supercid and was able to flash this on a at&t branded a9

Hi Ae3NerdGod
you don't have to use adb reboot bootloader and - adb reboot download boots direct to download mode

htconeXX said:
If it helps, I have an s-off, unlocked bootloader supercid and was able to flash this on a at&t branded a9
Click to expand...
Click to collapse
yep, like said above, this should work on any UHL variant.

Can you remove my at&t branding too? Lol that'd be awesome. Nice guide. I'll be doing this when my at&t one arrives
Sent from my Nexus 5 using Tapatalk

alray said:
yep, like said above, this should work on any UHL variant.
Click to expand...
Click to collapse
Well with supercid s-off and stock unlocked rom, the 6.0.1 update will not take, downloads but wont install. I think I need to teh CID for a US unlocked phone.

cid AND mid
Gesendet von meinem HTC One A9 mit Tapatalk

SU 2.65 Beta is out. I would recommend you use 2.64 system less from here on out anybody to start with. There are issues with 2.63 (non-systemless) and trying to then go system less. More steps to ensure a proper installation.
2.65 Beta you can install right on top of 2.64 Beta in TWRP recovery. I tested this, no issues.
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3

htconeXX said:
Well with supercid s-off and stock unlocked rom, the 6.0.1 update will not take, downloads but wont install. I think I need to teh CID for a US unlocked phone.
Click to expand...
Click to collapse
JochenP said:
cid AND mid
Gesendet von meinem HTC One A9 mit Tapatalk
Click to expand...
Click to collapse
This is accurate, i will update OP with these notes.
techlogik said:
SU 2.65 Beta is out. I would recommend you use 2.64 system less from here on out anybody to start with. There are issues with 2.63 (non-systemless) and trying to then go system less. More steps to ensure a proper installation.
2.65 Beta you can install right on top of 2.64 Beta in TWRP recovery. I tested this, no issues.
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Click to expand...
Click to collapse
i personally dont like systemless, ive been removing it afterwards and manually rooting, but ill update the OP.

@Ae3NerdGod would you you. Know if i s-off a sprint Htc a9 and convert it with your method... Would that sim unlock the device?

Google~Android said:
@Ae3NerdGod would you you. Know if i s-off a sprint Htc a9 and convert it with your method... Would that sim unlock the device?
Click to expand...
Click to collapse
Do NOT try to convert a Sprint/CDMA device! It will break completely break mobile data because the radio firmware is incompatible.

Captain_Throwback said:
Do NOT try to convert a Sprint/CDMA device! It will break completely break mobile data because the radio firmware is incompatible.
Click to expand...
Click to collapse
But wudnt returning the stock sprint wit ruu fix it?? I want to at least give it a shot..

I successfully converted by AT&T to USA unlocked thank you for the post. Only issue an facing is I can't delete pictures from my gallery is telling me about permissions on my system but I have gone thru the app and made sure it was active.
Sent from my HTC One A9 using Tapatalk

Convert from China to US
Work great for me
Thank you

Followed the guide and successfully converted my AT&T to US unlocked using SuperCID thanks to @Ae3NerdGod ran 1.55.617.4 Dev Edition RUU from @Captain_Throwback and updated to 6.0.1, re-rooted and installed Xposed on the stock ROM. I can confirm that all are working fine:good:

Related

[Q] Installing RUU, which one to choose

Hi,
My battery has been acting up for almost half a year now and my usage time is half of what it was when i got it. I have been installing several different ROMs and kernels so I am at a lost on what's wrong. So I have decided to install a RUU to see if a total reset can fix my phone.
I found this page: http://www.androidfiles.org/ruu/?developer=Ville
Does anybody know which RUU from the link is the newest/best? Will I get updates from HTC when I do this?
Currently running trickdroid 10.3.2, bricked kernel, twrp 2.3.3, S-OFF and superCID - is there anything in particular I should know before doing this?
I have never installed a RUU before, hope somebody can help
anyone? Or perhaps just a part answer
teamet said:
anyone? Or perhaps just a part answer
Click to expand...
Click to collapse
Choose RUU according to your CID.
Must restore original CID to avaoid having problems with OTA updates.
If you receive OTA updates with superCID, a brick is going to welcome you.
Sent from my HTC One S using Tapatalk 4 Beta
khan.orak said:
Choose RUU according to your CID.
Must restore original CID to avaoid having problems with OTA updates.
If you receive OTA updates with superCID, a brick is going to welcome you.
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
Ok so i am in a similar fix.
I obtained S-Off/superCID the very next day i got my One S .. things were running smooth on stock. Looked out for some ROMS and finally installed one. Now I want to revert to my stock ROM while maintaining S-off/root. My problem is only that i don't find this ROM stable or the kernel .. just want to revert to stock.
Live in Pakistan, hence i doubt OTA is going to ever cause me any trouble. Could you please recommend which RRU should i install?
Would really appreciate some help from a fellow countryman
G.Rabbani said:
Ok so i am in a similar fix.
I obtained S-Off/superCID the very next day i got my One S .. things were running smooth on stock. Looked out for some ROMS and finally installed one. Now I want to revert to my stock ROM while maintaining S-off/root. My problem is only that i don't find this ROM stable or the kernel .. just want to revert to stock.
Live in Pakistan, hence i doubt OTA is going to ever cause me any trouble. Could you please recommend which RRU should i install?
Would really appreciate some help from a fellow countryman
Click to expand...
Click to collapse
Yes, you're right. Latest 4.2.2 Custom ROMs are having some bugs at the moment.
I need to know some details before I recommend anything.
1. S3/S4 version processor? (CPU-Z from play store will tell you that)
2. CID & MID (CID getter from play store will tell you that)
3. Last Stock firmware you had/installed?
4. HBOOT version?
Sent from my Nexus 7 using Tapatalk HD
khan.orak said:
Yes, you're right. Latest 4.2.2 Custom ROMs are having some bugs at the moment.
I need to know some details before I recommend anything.
1. S3/S4 version processor? (CPU-Z from play store will tell you that) -----> S4
2. CID & MID (CID getter from play store will tell you that) -----> 11111111
3. Last Stock firmware you had/installed? -----> JB 4.1.1
4. HBOOT version? -----> 2.15.0000
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Thanks for the response I've responded to your queries inline.
G.Rabbani said:
Thanks for the response I've responded to your queries inline.
Click to expand...
Click to collapse
Okay that's good but I need to know the original CID that the phone was shipped with.
Also, I'll need to know MID (Model ID). You can find it out via CID GETTER. When you open the app search for the line [ro.aa.modelid]: PJxxxxxxx that's the model ID
Sent from my Nexus 7 using Tapatalk HD
khan.orak said:
Okay that's good but I need to know the original CID that the phone was shipped with.
Also, I'll need to know MID (Model ID). You can find it out via CID GETTER. When you open the app search for the line [ro.aa.modelid]: PJxxxxxxx that's the model ID
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Thanks a lot for the hint. The CID on the top in CID getter was showing all ones. Ok so following is the information i made out from the verbosity, related to CID and Model ID and all of the rest that made sense to me.
ro.aa.cutomizationid: 452550
ro.aa.maincid: HTC__001
ro.aa.modelid: PJ4010000
ro.baseband: 1.11.50.05.28
ro.bootloader:2.15.0000
ro.aa.project: Ville_U_JB_45_S
ro.aa.rid: 386
G.Rabbani said:
Thanks a lot for the hint. The CID on the top in CID getter was showing all ones. Ok so following is the information i made out from the verbosity, related to CID and Model ID and all of the rest that made sense to me.
ro.aa.cutomizationid: 452550
ro.aa.maincid: HTC__001
ro.aa.modelid: PJ4010000
ro.baseband: 1.11.50.05.28
ro.bootloader:2.15.0000
ro.aa.project: Ville_U_JB_45_S
ro.aa.rid: 386
Click to expand...
Click to collapse
Ok. I deem this RUU to be the most suitable for you, which is Here.
Just run the RUU and it will do the job for you.
A word or two of caution here:
1. The RUU will erase everything.
2. After the RUU, you might want to change your CID back to HTC__001 because it has been rumored that HTC will release JellyBean 4.2.2 + Sense 5 for the One S. If you update the ONE S via OTA with SUPERCID, you will brick your device.
And anyway, SuperCID is not necessary at all for flashing Custom ROMs.
3. You will lose the Root for sure. But you can flash custom recovery + SuperSU again after going stock.
Edit: Oh! and match the MD5 hash of the downloaded file and the one on the server. MD5 checking utility is on XDA somewhere.
Edit 2: The CID in all cases comprises of 8 characters. i.e HTC__001 (8 chars), BM___001 (8 chars, my CID) etc. So when changing the CID, be sure to have an 8 character CID.
regards
khan.orak said:
Ok. I deem this RUU to be the most suitable for you, which is Here.
Just run the RUU and it will do the job for you.
A word or two of caution here:
1. The RUU will erase everything.
2. After the RUU, you might want to change your CID back to HTC__001 because it has been rumored that HTC will release JellyBean 4.2.2 + Sense 5 for the One S. If you update the ONE S via OTA with SUPERCID, you will brick your device.
And anyway, SuperCID is not necessary at all for flashing Custom ROMs.
3. You will lose the Root for sure. But you can flash custom recovery + SuperSU again after going stock.
Edit: Oh! and match the MD5 hash of the downloaded file and the one on the server. MD5 checking utility is on XDA somewhere.
regards
Click to expand...
Click to collapse
Thanks a lot brother!
Will follow your instructions. I was following a guide (All in one tool kit for ONE S) to achieve S-OFF for rooting and following that procedure the CID was reset as well. Not sure whether i can achieve S-OFF without meddling with the CID .... This being my first HTC after SGS and SGS2.
G.Rabbani said:
Thanks a lot brother!
Will follow your instructions. I was following a guide (All in one tool kit for ONE S) to achieve S-OFF for rooting and following that procedure the CID was reset as well. Not sure whether i can achieve S-OFF without meddling with the CID .... This being my first HTC after SGS and SGS2.
Click to expand...
Click to collapse
No problem at all.
Ok. Some interesting info for you again:
- S-OFF/SuperCID is not necessary for Rooting/Custom Recovery/Flashing Custom ROMs. You must have missed something.
- Just need to Unlock bootloader to Root/Flash custom recovery/custom ROM
khan.orak said:
No problem at all.
Ok. Some interesting info for you again:
- S-OFF/SuperCID is not necessary for Rooting/Custom Recovery/Flashing Custom ROMs. You must have missed something.
Click to expand...
Click to collapse
Hain ??
For all I have read, the reason for going after S-Off to begin with is essentially to gain capability to flash customer roms. I feel sorry for being a consistent bother, but could you please guide me towards a thread where I can learn rooting without messing with S-Off ...
G.Rabbani said:
Hain ??
For all I have read, the reason for going after S-Off to begin with is essentially to gain capability to flash customer roms. I feel sorry for being a consistent bother, but could you please guide me towards a thread where I can learn rooting without messing with S-Off ...
Click to expand...
Click to collapse
haha... Yes..
Well the All-in-One-Toolkit by Hasoon2000 is the one you have to follow. But no S-OFFing/SuperCID.
You just need the bootloader unlocked to get Rooted/Custom ROM/Recovery.
Since you have already unlocked the bootloader, I think it's not necessary to use the AIO toolkit again.
What we need is this:
- Run the RUU. (Run it first, and if it gives you errors, you might need to Relock your bootloader which is quite simple).
[For the latter part] - Then if you want to Root you stock ROM, we will have to flash custom Recovery, which again is quite simple and can be flashed from fastboot. I'll guide you on this part later when you are stock again. No biggy.
khan.orak said:
haha... Yes..
Well the All-in-One-Toolkit by Hasoon2000 is the one you have to follow. But no S-OFFing/SuperCID.
You just need the bootloader unlocked to get Rooted/Custom ROM/Recovery.
Since you have already unlocked the bootloader, I think it's not necessary to use the AIO toolkit again.
What we need is this:
- Run the RUU. (Run it first, and if it gives you errors, you might need to Relock your bootloader which is quite simple).
[For the latter part] - Then if you want to Root you stock ROM, we will have to flash custom Recovery, which again is quite simple and can be flashed from fastboot. I'll guide you on this part later when you are stock again. No biggy.
Click to expand...
Click to collapse
YOU ARE THE MAN! :good:
Take care bro. I'll catch up with you tomorrow after going through the RUU part :highfive:
G.Rabbani said:
YOU ARE THE MAN! :good:
Take care bro. I'll catch up with you tomorrow after going through the RUU part :highfive:
Click to expand...
Click to collapse
glad I could help
Sent from my HTC One S using Tapatalk 4 Beta
khan.orak said:
glad I could help
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
AOA Orak,
I installed the RUU and am back to stock now. Using the toolkit installed TWRP S4 recovery but when i try to go into recovery a red triangle with an exclamation mark appears; the phone stays with it for a while and then reboots to normal desktop. Tried it a number of times with the same result. Since i am unable to go into recovery, i cannot flash the supersu.zip and thus no root :/ Should I go for CWM?
G.Rabbani said:
AOA Orak,
I installed the RUU and am back to stock now. Using the toolkit installed TWRP S4 recovery but when i try to go into recovery a red triangle with an exclamation mark appears; the phone stays with it for a while and then reboots to normal desktop. Tried it a number of times with the same result. Since i am unable to go into recovery, i cannot flash the supersu.zip and thus no root :/ Should I go for CWM?
Click to expand...
Click to collapse
W/S
Okay first you boot into bootloader and tell me the details ..
To go into bootloader, turn off device, then hold power + vol down ... A white background with details..
Post them here.
Sent from my HTC One S using Tapatalk 4 Beta
khan.orak said:
W/S
Okay first you boot into bootloader and tell me the details ..
To go into bootloader, turn off device, then hold power + vol down ... A white background with details..
Post them here.
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
Ok so i figured it out in the meanwhile .. I had locked the bootloader before running the RUU. Unlocked it, installed recovery and flashed SU successfully.
So now I have two questions:
1- Do i need to re-lock the bootloader? If yes, will I still be able to flash custom roms?
2- How do i revert my original CID value? Will 'fastboot writecid HTC__001' do the trick? Are there any pre-requisites for it?
G.Rabbani said:
Ok so i figured it out in the meanwhile .. I had locked the bootloader before running the RUU. Unlocked it, installed recovery and flashed SU successfully.
So now I have two questions:
1- Do i need to re-lock the bootloader? If yes, will I still be able to flash custom roms?
2- How do i revert my original CID value? Will 'fastboot writecid HTC__001' do the trick? Are there any pre-requisites for it?
Click to expand...
Click to collapse
- Okay before anything, i would advise to flash TWRP 2.3.3.0 recovery and you will avoid many issues currently being faced with 2.5.0.0.
You can find 2.3.3.0 Here.
If you need help on flashing, ask away.
- now your questions:
1. No and No
2. You have to boot into bootloader and then go into FASTBOOT and write the command
fastboot oem writecid HTC__001
BTW, I assume you have adb+fastboot files on your PC?
Sent from my Nexus 7 using Tapatalk HD
khan.orak said:
fastboot oem writecid HTC__001
Click to expand...
Click to collapse
This only works if you are S-OFF
hTConeS | SoFF | ChaRmAnDrOiD | BuLLetprOOf
Inverted Sense 5 Theme Updates+Tweaks
Inverted Sense 4+

Problem during back to stock rom S4

Today I tried back from CyanogenMod 12 to stock rom in HTC ONE S.
One S 1.5, TWRP 2.8.5, HBoot 2.15, S-ON. Cid T-MOB101
During this procedure: https://translate.google.pl/translat...OMu&edit-text=
In this 6. point "6. Turn the phone back - no, it's not over yet, but the worst is behind us. We run suitable for our model and already RUU.exe normally carry out the procedure ROM Upgrade Utility - Using the instructions of the installer. ". I used RUU from this link https://drive.google.com/folderview?id=0B1IYElPvrGZrdGR6SXIwYjgxd1U&usp=sharing#list
Installer (RUU) show me error [140]: error bootloader version.
After I close installer phone was reboot and I see only bootloader - On the top I see TAMPERED RELOCKED Security Warning)
I can not run Android now
Could you help me? Please
Update> I unlock it using fastboot flash unlocktoken Unlock_code.bin, but what is next?
noiserobert said:
Today I tried back from CyanogenMod 12 to stock rom in HTC ONE S.
One S 1.5, TWRP 2.8.5, HBoot 2.15, S-ON. Cid T-MOB101
During this procedure: https://translate.google.pl/translat...OMu&edit-text=
In this 6. point "6. Turn the phone back - no, it's not over yet, but the worst is behind us. We run suitable for our model and already RUU.exe normally carry out the procedure ROM Upgrade Utility - Using the instructions of the installer. ". I used RUU from this link https://drive.google.com/folderview?id=0B1IYElPvrGZrdGR6SXIwYjgxd1U&usp=sharing#list
Installer (RUU) show me error [140]: error bootloader version.
After I close installer phone was reboot and I see only bootloader - On the top I see TAMPERED RELOCKED Security Warning)
I can not run Android now
Could you help me? Please
Update> I unlock it using fastboot flash unlocktoken Unlock_code.bin, but what is next?
Click to expand...
Click to collapse
to use a RUU your bootloader need be relocked
---------- Post added at 06:28 PM ---------- Previous post was at 06:26 PM ----------
You can try rumrunner to S-OFF and after that try with Ruu
JavierG123 said:
You can try rumrunner to S-OFF and after that try with Ruu
Click to expand...
Click to collapse
I tried it but it not work. I think because it work only with stock rom
How back t stock rom with s-on?
noiserobert said:
I tried it but it not work. I think because it work only with stock rom
How back t stock rom with s-on?
Click to expand...
Click to collapse
Flash the proper RUU for your CID, you don't need S-Off for that.
Sent from nowhere over the air...
@thanks Rapier
I describe as I did it in detaliled:
1. Run fastboot oem readcid and fastboot getvar version-main and receive inforamtion Cid T-MOB101 3.16.111.11
2. Downlaod proper (??) RUU RUU_Ville_U_ICS_40_S_TMO_DE_2.38.111.10_Radio_1.09es.50.02.07_2_10.09d.50.04L_ver2_release_287723_signed.exe . Is it proper for my device One S 1.5, TWRP 2.8.5, HBoot 2.15, S-ON. Cid T-MOB101?
3. Run fastboot oem lock
4. Run fastboot erase cache
5. Run RUU (from 1 point)
6. RUU inform me that will be install oddest (something like 2.38.111.xx - I dont remember all number) version then is on my ONE S (3.16.111.11), I accept it
7. RUU reboots my phone, and HTC starts and on blac background was logo htc
8. After few minutes RUU installer show me error [140]: error bootloader version.
9. I accept RUU and it close and my phone reboot to bootloader On the top I see TAMPERED RELOCKED Security Warning)
Where is wrong ?
Plese help me
I resolve it
1. Install a Viper 2.20
2. Use rumrunner.us to set your phone S-OFF
noiserobert said:
I resolve it
1. Install a Viper 2.20
2. Use rumrunner.us to set your phone S-OFF
Click to expand...
Click to collapse
And the RUU works?
I do not RUU because I did S-Off and it was fantastic
I go to Maximums HD (based on stock rom)
noiserobert said:
I do not RUU because I did S-Off and it was fantastic
I go to Maximums HD (based on stock rom)
Click to expand...
Click to collapse
but... for install Maximums HD you don't need S-OFF....
JavierG123 said:
but... for install Maximums HD you don't need S-OFF....
Click to expand...
Click to collapse
Of course you MUST have S-OFF to install Maxiums HD. Please read about it!
noiserobert said:
Of course you MUST have S-OFF to install Maxiums HD. Please read about it!
Click to expand...
Click to collapse
i'm sorry men. my bad
No problem
Only one problem is that not support beatsaudio
noiserobert said:
No problem
Only one problem is that not support beatsaudio
Click to expand...
Click to collapse
in android development or other section like that here in the forum... exist a flasheable zip to get on any device beats audio and other features...
I am wrong, this rom support BA! It is fantastic!

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.

HTC ONE Unlocked OTA 1.57.617.41 Download

Latest HTC One A9 Unlocked Edition OTA
OTA_HIA_AERO_UL_M60_SENSE7GP_ATT_MR_NA_Gen_Unlock_1.57.617.41-1.57.617.32_release_480058icet4xqcwsg0zr0g.zip
http://d-h.st/YwvS
techlogik said:
Latest HTC One A9 Unlocked Edition OTA
OTA_HIA_AERO_UL_M60_SENSE7GP_ATT_MR_NA_Gen_Unlock_1.57.617.41-1.57.617.32_release_480058icet4xqcwsg0zr0g.zip
http://d-h.st/YwvS
Click to expand...
Click to collapse
I have European version 1.56 , how can I install this?
Sent from my HTC One A9 using XDA-Developers mobile app
If you want to install this update you need to S-OFF your phone and change CID and MID using fastboot command from download mode:
fastboot oem writecid 11111111
fastboot oem writemid 2PQ912000
Then you will be able to flash US firmware.
Anybody have a valid TRWP system image for 1.57.617.32?
I took one but it still failed the verity check.
NuShrike said:
Anybody have a valid TRWP system image for 1.57.617.32?
I took one but it still failed the verity check.
Click to expand...
Click to collapse
Oh well, I flashed the .32 RUU and restored data from TWRP/FlashFire, flash this update, and I think I'm done.
NuShrike said:
Oh well, I flashed the .32 RUU and restored data from TWRP/FlashFire, flash this update, and I think I'm done.
Click to expand...
Click to collapse
Did you use FlashFire to only restore data? Just curious.
qooob said:
If you want to install this update you need to S-OFF your phone and change CID and MID using fastboot command from download mode:
fastboot oem writecid 11111111
fastboot oem writemid 2PQ912000
Then you will be able to flash US firmware.
Click to expand...
Click to collapse
This OTA will not flash if you're superCID. You must use the US unlocked or developer CID specifically to flash this OTA (BS_001 or BS_002).
The RUU will flash if you are superCID, but 1.57.617.41 RUU hasn't been officially (or unofficially that I'm aware of) released yet.
eelpout said:
Did you use FlashFire to only restore data? Just curious.
Click to expand...
Click to collapse
I used FlashFire generated backup in TWRP to restore data.
Of course internal-storage was still wiped, but I manually back that up these days (with SyncMe app), and don't put anything there, if possible.
qooob said:
If you want to install this update you need to S-OFF your phone and change CID and MID using fastboot command from download mode:
fastboot oem writecid 11111111
fastboot oem writemid 2PQ912000
Then you will be able to flash US firmware.
Click to expand...
Click to collapse
Will it really work? My phone will work properly? How to get S-OFF? Will S-On be back after I flash? Do I need to root?
It worked for me.
To get S-Off I used SunShine S-Off. You can disabled S-Off by running command `fastboot oem writesecureflag 3`. You need root to run SunShine.
After getting S-Off be careful not to mess HBOOT otherwise your phone will be hard-bricked and non-recovereable at home (you would need a programmer (device)).
qooob said:
If you want to install this update you need to S-OFF your phone and change CID and MID using fastboot command from download mode:
fastboot oem writecid 11111111
fastboot oem writemid 2PQ912000
Then you will be able to flash US firmware.
Click to expand...
Click to collapse
Will I get OTA?
MVince25 said:
Will I get OTA?
Click to expand...
Click to collapse
Yes, you should. You will need to relock the bootloader and s-on to make OTA work as far as I remember.
Convert UHL to UL
Hi, I have an European Unlocked A9, stock firmware 1.56.401.70. Also, I am S-off, SuperCid, and my device has 2GB of RAM. Can I use US Unlocked RUU to convert my HTC? I want to use 1.57.617.52 software. Is it ok to convert? The US unlocked version has 3GB RAM... Thanks !
qooob said:
Yes, you should. You will need to relock the bootloader and s-on to make OTA work as far as I remember.
Click to expand...
Click to collapse
bro OTA no need S-ON just relock bootloader

Feeling dumb with this phone

.
Hi ppl!
So, I had a working HTC One S (s4) with Bootloader Unlocked, Root, Stock rom and Custom Recovery all done many years ago. I picked it up because I want to give it to someone in my family and I decided to see how it runs Lineage OS. So I found a LOS Rom, copied it and tried to install it via the latest TWRP. I wiped all, changed Data partition to F2FS and tried to install. But it said I needed Hboot 2.16 and it only has 2.15.
So then I found out to update the Hboot I need S-Off. And apparently every method needs a working Rom which I dont have right now. So I tried to find an old CM rom that runs on Hboot 2.15 but I just cannot install it. I'm just too used to how easy is to modify the Moto X so I was overconfident with the One S. And I cannot remember any of the stuff I did with it to achieve a rooted Stock Rom.
Can someone lend me a hand please?
So I have no idea what's wrong with the phone, but I tried to install CM11 and CM12 which supposedly are hboot 2.15 compatible according to their OPs and yet when restarting I just get a blackscreen after the boot image and nothing happens. What I did wrong?
With S-ON you need to flash the boot.img via fastboot after flashing a rom via TWRP or the phone won't boot.
I got S-OFF with Viper 2.x and Facepalm. Alternatively, you can try CM11 and Rumrunner. Or you get back to stock via a RUU* and root the stock rom with TWRP and SuperSU (not sure which versions are compatible with the old android 4.1). After that you should be able to use Sunshine (costs 25 bucks).
* Check your firmware version with fastboot getvar all (either "version-main" or "main version") and find a RUU with the same version.
Flippy498 said:
With S-ON you need to flash the boot.img via fastboot after flashing a rom via TWRP or the phone won't boot.
I got S-OFF with Viper 2.x and Facepalm. Alternatively, you can try CM11 and Rumrunner. Or you get back to stock via a RUU* and root the stock rom with TWRP and SuperSU (not sure which versions are compatible with the old androud 4.1). After that you should be able to use Sunshine (costs 25 bucks).
* Check your firmware version with fastboot getvar all (either "version-main" or "main version") and find a RUU with the same version.
Click to expand...
Click to collapse
Wow, many thanks! Such an easy thing I didnt see posted in all the forums I scourged. Now the phone finally boots.
Btw, I got version-main 3.16.401.10, and I found a RUU for 3.16.401.8 I guess it's ok to use?
You'll need to try. If it was a One M9 then I'd say yes it'll work. However, the One S is so much older and it's been ages since mine was S-ON so I'm not completely sure.
Edit: There won't happen anything bad if it's not the correct RUU. It'll just abort the process before it really starts flashing.
Edit2: I found the needed RUU on AFH. I've been working together with Krocko, in the past. Therefore, I know that he's a reliable source. Boot the phone to fastboot USB mode and flash the file with
Code:
fastboot flash zip PJ40IMG_Ville_U_JB_45_S_HTC_Europe_3.16.401.10_Radio_1.11.50.05.28_10.27.50.08L_release_368741_signed.zip
Check the file's MD5 checksum before you flash so that you can rest assured that it didn't get damaged during the download. The desired value is mentioned on the download page.
Edit3: You'll need to use that command twice. The first try will probably end with error 90 or something like that.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
Edit3: You'll need to use that command twice. The first try will probably end with error 90 or something like that.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Darn, I can't thank you enough for all the support!
So indeed it failed, but not the Error 9X, rather "FAILED (remote: not allowed)" Google say such error results when the Bootloader is locked but mine is unlocked. And the MD5 is ok.
Code:
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
FAILED (remote: not allowed)
My bootloader says the following info:
**TAMPERED** (TWRP 3.1)
**UNLOCKED**
VLE PVT SHIP S-ON RL
HBOOT-2.15.000
OpenDSP-v31.1.0.45.0815
eMMC-bot
Dec 14 2012,17:10:57:-1
I'm on Windows 10 and the phone is recognized no problem.
So, I'm lost...
EDIT: And CID = HTC__001
Ah, now that you mention it: On the One S the bootloader needs to be locked or relocked for flashing RUUs if the phone is S-ON. My bad. Sorry.
Code:
fastboot oem lock
In addition, flashing RUUs via fastboot (that's what the *.exe versions do, as well) can be a bit tricky and since the One S has no micro SD card slot there's no alternative method...
I don't have a link with instructions at hand that are specific for the One S but I can link you some troubleshooting tips that I posted in the One M9 forum. They're universal and should theoretically be able to help you (if one of the mentioned problems actually is your issue).
Flippy498 said:
Ah, now that you mention it: On the One S the bootloader needs to be locked or relocked for flashing RUUs if the phone is S-ON. My bad. Sorry.
Code:
fastboot oem lock
In addition, flashing RUUs via fastboot (that's what the *.exe versions do, as well) can be a bit tricky and since the One S has no micro SD card slot there's no alternative method...
I don't have a link with instructions at hand that are specific for the One S but I can link you some troubleshooting tips that I posted in the One M9 forum. They're universal and should theoretically be able to help you (if one of the mentioned problems actually is your issue).
Click to expand...
Click to collapse
Ahhh that explains. Thanks!
One question before I do that though, to unlock it again, do I need the unlock bin file from HTC again?
Sent from my XT1095 using Tapatalk
Yeah, but you'll probably need a new one. At least I had to request a new one whenever I flashed a RUU on my One S.
Sent from my HTC One M9 using XDA Labs
Perfect, I'll do that then, a thousand thanks for all your help!
Sent from my XT1095 using Tapatalk

Categories

Resources