Related
Hi, I want to flash a development RUU, but everytime I try, I get Error [155]. This RUU is supposed to have 1.13.0000 bootloader version, but I don't know how to update from 1.06.0000 and if it may cause the error.
Any suggestion about it? Thanks in advance.
You're talking about ONE S, right?
Right, HTC One S
Well first of all is the chosen RUU compatible with your CID ?? If it isnt it will fail so you need to download one that is compatible, Or change your CID to match the one inside the RUU..
Secondly, If you haver done this and still get the error, Try to run the RUU from fastboot.
Oh and also, RUU requires a LOCKED / RELOCKED bootloader and sometimes stock recovery too !
azzledazzle said:
Well first of all is the chosen RUU compatible with your CID ?? If it isnt it will fail so you need to download one that is compatible, Or change your CID to match the one inside the RUU..
Secondly, If you haver done this and still get the error, Try to run the RUU from fastboot.
Oh and also, RUU requires a LOCKED / RELOCKED bootloader and sometimes stock recovery too !
Click to expand...
Click to collapse
Yes, I have the same CID that is inside the RUU.
Could you tell me how to run it from fastboot?
I'm trying almost everything I can (locked, relocked, unlocked, stock recovery...), even I'm trying now to update to the latest OTA_Ville_U_HTC_Europe_1.78.401.2-1.53.401.2 (now I have 1.53.401.2 from Orange Spain) as it has a firmware update (maybe hboot 1.13.0000?) what I think that can be one of the reasons why I can't flash the rom I need.
Thanks in advance!
boot into bootloader and connect USB cable, Select fastboot and then run the RUU on your PC.
Make sure bootloader is locked BEFORE running the ruu
azzledazzle said:
boot into bootloader and connect USB cable, Select fastboot and then run the RUU on your PC.
Make sure bootloader is locked BEFORE running the ruu
Click to expand...
Click to collapse
Yes, it's something I've already tried. Another problem I'm trying to solve is when installing from stock recovery, cause it says sdcart can't be mounted...
What are you trying to install from Stock Recovery ?? you cant flash an RUU and all flashable zip files MUST be signed otherwise it will fail..
I also had the cant mount sd card error in stock recovery, But when i tried CWM i didnt.. Dont know much about how stock recovery works, I just know i dont like it lol
lol, me neither!!!
I'm trying to install a stock rom, so I am supposed to do it from stock recovery, that's the matter. But I can't do it because it can't mount sdcard. I'm getting crazy, but now it is something personal, between the phone and me!!! I'll try to be patient and find the solution.
Stock ROM ?? How have you obtained this ? has someone posted it in a flashable .zip file ? If so, You need to flash it via CWM Recovery THEN flash stock recovery through fastboot.
If the Stock ROM is a Nandroid you will also need to restore this using CWM Recovery. THEN flash stock recovery after.
If the Stock ROM is dissected from an RUU you will need to flash this via bootloader, BUT unless you have a S-OFF phone (which i doubt you do cause there is no S-OFF yet) It wont work.
azzledazzle said:
Stock ROM ?? How have you obtained this ? has someone posted it in a flashable .zip file ? If so, You need to flash it via CWM Recovery THEN flash stock recovery through fastboot.
If the Stock ROM is a Nandroid you will also need to restore this using CWM Recovery. THEN flash stock recovery after.
If the Stock ROM is dissected from an RUU you will need to flash this via bootloader, BUT unless you have a S-OFF phone (which i doubt you do cause there is no S-OFF yet) It wont work.
Click to expand...
Click to collapse
Ok, it is the third option, and evidently, I'm not S-OFF. I had read a thread where they dissected this zip and I thought it was useful. Now I have found the RUU, I will try to install it. I've changed the zip and relocked it but I'm still finding Error [155]
Its useful if you are S-OFF, You just extract the ROM.zip from the RUU, Rename it to the phones model number, So in our case it would be PG40100.img ( i think) and then flash it in bootloader. However ignore this option as it wont work with a S-ON device...
If you still get the Error 155 message and you're positive you've done everything correctly, Maybe download the same / another RUU, Chances are it could have been a bad / corrupted download It happens to us all !
Ok, finally I solved it. I found original RUUs for HTC_Europe 1.53 and 1.78
Firstly, I changed my CID to HTC__001, extracted recovery.img from 1.53 RUU, flashed it, relocked the bootloader and installed the 1.53 RUU... and it worked!!! After that, nothing special to say installing 1.78 (hboot and radio updated!)
rpachecoh said:
Ok, finally I solved it. I found original RUUs for HTC_Europe 1.53 and 1.78
Firstly, I changed my CID to HTC__001, extracted recovery.img from 1.53 RUU, flashed it, relocked the bootloader and installed the 1.53 RUU... and it worked!!! After that, nothing special to say installing 1.78 (hboot and radio updated!)
Click to expand...
Click to collapse
I have done exactly (!!) the same, but you know, I have Hboot in version 2.15. And I can run none of RUUs, because I think they are not compatible with this version of Hboot (And this is that Error 155 for me). Well, so what can I do for installing the Stock RUU to my One S ?
Hey guys
I've got a bit of a situation. A friend of mine gave me this sensation (carrier T-mobiel) wich was all but bricked. Since I have some experience rooting and flashing custom ROMs, he asked me to give it a try at reviving it.
The owner had been messing around a bit himself and he managed to install clockwordmod recovery. Don't know if he installed any ROM, the device gets stuck on splashscreen.
I did the following; full format, superwipe and install a ARHD ROM. result was te same; stuck on splash-screen.
Then I did another full format, wipe and installed Cyanogenmod, still the same result.
I wanted to try and install 4EXT touch recovery, but the device doesn't respond to any USB connection method so ADB won't work. there's no working ROM so installing through the app won't go either. basicly, I don't know if there's a way to uninstall and install a recovery through flashing.
I have another phone to use to store required files on a SDcard.
these are the things dat DO work:
Bootloader, fastboot and clockworkmod recovery v5.8.0.9
this is the device's bootloader information
UNLOCKED
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
RADIO-10.14.9035.01_M
Aug 2 2011, 22:35:52
my guess is that I'm trying to install ROM's that don't work with the current firmware. I don't know if the owner installed the OTA ICS before he got these problems. But I don't know what firmware is currently on this this device, and how to check it.
Lost for clues here and calling out for help
Onemanshow
onemanshow85 said:
Hey guys
I've got a bit of a situation. A friend of mine gave me this sensation (carrier T-mobiel) wich was all but bricked. Since I have some experience rooting and flashing custom ROMs, he asked me to give it a try at reviving it.
The owner had been messing around a bit himself and he managed to install clockwordmod recovery. Don't know if he installed any ROM, the device gets stuck on splashscreen.
I did the following; full format, superwipe and install a ARHD ROM. result was te same; stuck on splash-screen.
Then I did another full format, wipe and installed Cyanogenmod, still the same result.
I wanted to try and install 4EXT touch recovery, but the device doesn't respond to any USB connection method so ADB won't work. there's no working ROM so installing through the app won't go either. basicly, I don't know if there's a way to uninstall and install a recovery through flashing.
I have another phone to use to store required files on a SDcard.
these are the things dat DO work:
Bootloader, fastboot and clockworkmod recovery v5.8.0.9
this is the device's bootloader information
UNLOCKED
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
RADIO-10.14.9035.01_M
Aug 2 2011, 22:35:52
my guess is that I'm trying to install ROM's that don't work with the current firmware. I don't know if the owner installed the OTA ICS before he got these problems. But I don't know what firmware is currently on this this device, and how to check it.
Lost for clues here and calling out for help
Onemanshow
Click to expand...
Click to collapse
Hi,
2 things you can try.
1.Run a GingerBread RUU.
Look HERE
2.If that works,try s-off.
Look HERE
Then,you could change firmwares and do whatever you like.
Hi Malybru,
I understand what you suggested and I'm currently working on it. Only I can't find the right RUU for this phone.
Current CID is: T-MOB003
getting it superCID'd was no go since I can't get it S-OFF with the revolutionary utility. is there another way to S-OFF the phone besides revolutionary?
edit: I downloaded and executed a RUU that apearantly wasn't compatible with the phone. I'm guessing it removed whatever ROM was installed, but didn't install the ROM from the RUU.
I also followed step 3; RUU to restore stock up to the part of relocking the bootloader. I didn't come any further cause I can't find the right RUU.
the phone now only boots into bootloader with "security warning" displayed below "relocked".
I'm guessing, if I find the correct RUU with gingerbread, things will be okay again.
on a sidenote, does a RUU install also returns the recovery to stock?
onemanshow85 said:
Hi Malybru,
I understand what you suggested and I'm currently working on it. Only I can't find the right RUU for this phone.
Current CID is: T-MOB003
getting it superCID'd was no go since I can't get it S-OFF with the revolutionary utility. is there another way to S-OFF the phone besides revolutionary?
Click to expand...
Click to collapse
Hi,
RUU does not matter too much as long as it is Europe and GB.
If you can find a dutch tmo ,then even better.
No harm will come if it is the wrong one.
It will only throw up an error.
This will at least get a ROM on your phone,so that you can s-off .
Revolutionary is the easiest way to s-off.
so, to summarize:
the RUU has to be TMO for either UK or EU. Does the radio need to match the one that's currently displayed in the bootloader?
onemanshow85 said:
so, to summarize:
the RUU has to be TMO for either UK or EU. Does the radio need to match the one that's currently displayed in the bootloader?
Click to expand...
Click to collapse
Hi,
The closer the match,the more chance of success.
But close will do.
Yes,with the same radio.
finding a dutch RUU with this radio for TMO is pretty challenging. So I tried it with a german version (DE). Other then that it matches the radio, and the carrier.
the first method through the RUU.exe failed, it tells me to get the right RUU for my carrier/phone.
So I tried it through flashing with a SDcard. I changed the CID in the notepad file in the PG58IMG.zip to T-MOB003. In bootloader, it checks the file twice and after that nothing happens, the regular bootloader screen is prompted.
Then I tried to flash it through fastboot CMD command, pretty much my last option according to the guid you linked me. This also fails with the notification that it failed to verify 12 signatures.
now I found some universal firmware packages but they don't seem to contain any ROM and recovery, only firmware. are there any of these universal packages as complete RUU?
or is there a way to bypass the signature check with a fastboot command?
onemanshow85 said:
finding a dutch RUU with this radio for TMO is pretty challenging. So I tried it with a german version (DE). Other then that it matches the radio, and the carrier.
the first method through the RUU.exe failed, it tells me to get the right RUU for my carrier/phone.
So I tried it through flashing with a SDcard. I changed the CID in the notepad file in the PG58IMG.zip to T-MOB003. In bootloader, it checks the file twice and after that nothing happens, the regular bootloader screen is prompted.
Then I tried to flash it through fastboot CMD command, pretty much my last option according to the guid you linked me. This also fails with the notification that it failed to verify 12 signatures.
now I found some universal firmware packages but they don't seem to contain any ROM and recovery, only firmware. are there any of these universal packages as complete RUU?
or is there a way to bypass the signature check with a fastboot command?
Click to expand...
Click to collapse
Hi,
Try the European RUU with the 10.14 radio that matches yours.
Add your CID in the PG58IMG text file.
Make sure you have the phone in fastboot when you attach your USB cable(it should say "fastboot USB"),and start running the RUU from your PC.
http://db.tt/A7lS7PaD
Here is a link to 4ext touch recovery as a IMG. http://db.tt/KFKpcrhB and here is a pg58img.zip. put the zip file onto the sdcard and boot to boot loader. It will hopefully flash the recovery. If not fast boot flash the IMG. Once you have the recovery installed enable smart flash and then flash the roms. Hopefully that will work for you
Sent from my HTC Sensation using xda premium
tnx for the files.
I tried the suggestions you made but flash from sdcard doesn't work; it checks the file once and doesn't do anything after it.
when I try to flash either one of the files through fastboot I get signature verification fail.
my bootloader says RELOCKED, I got that after following step 3.1 in the RUU flash guide to return to stock. I don't know if this is blocking anything from being flashed with the nasty signature notifications?
also, most like because nothing is installed on my device, when I plug in the USB cable when it's turned off, it automatically swithces on displaying SECURITY WARNING below RELOCKED.
Damn, wasn't fast enough. I'm not sure what the best way to approach this is. Either attempt to full s-off the device with revolutionary/ jupuntobear, or re-unlock your boot loader with htcdev, then fastboot flash the recovery. Then install the rom. Then run jupuntobear to full s-off
Sent from my HTC Sensation using xda premium
heavy_metal_man said the right thing. First focus on unlocking it on hTCdev.com and afterwards, flash a 4Ext Recovery to make things easyer. Then put the device in bootmenu (not in the Graphic shell) and attach a USB, start any Official European RUU that is Gingerbread - with 1.50 in the numbers.
an update
I managed to get it unlocked again with htcdev.com. After that I flashed 4EXT recovery, succesfully.
only thing now I need to do is installing a ROM. I tried the following without succes so far:
with RUU
I can't find a dutch RUU for TMO with radio 10.14.9035 anywhere so I tried the closest match possible, a german one. through the .exe method I get incompatibility errors. So I extracted the ROM/.zip, added my CID and tried with SDcard flash and fastboot flash, both unsuccesfull. Hboot checks the file twice and does nothing afterwards, and fasboot prompts the message "FAILED (remote ** unknown fail)"
Universal firmware package to make sure I'm on 3.32, so I can install ARHD 6.7.2 or any other ICS rom
I took one from http://forum.xda-developers.com/showthread.php?p=21711154#post21711154.
I get the same errors as when I was trying to flash the ROM.zip from the RUU, both with sdcard flash and fastboot flash.
a random Gingerbread ROM
I found this GB ROM http://forum.xda-developers.com/showthread.php?t=1226564.
I installed it through EXT4. after a reboot it's stuck in a bootloop. No splash screen is shown however, it get's to the withe-field-green-HTC-screen and reboots after, showing the same.
I don't understand what's wrong. I got a good recovery now and the bootloader is unlocked. For some reason the ROM's I tried are incompatible with the current state of the device and I can't figure out why. are dutch T-mobile branded phones so tough to crack or what?
also, after a certain step wich I can't remember, my bootloader doesn't display a radio anymore.
Current bootloader:
UNLOCKED
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
eMMC-boot
Aug 2 2011,22:35:52
EDIT: I would be less restricted in my actions if the damn thing were to be S-OFF. is there any way to get get S-OFF through bootloader/fastboot? All the S-OFF methods and utillities I found so far need the device to have a ROM running.
SOLVED
with help of KGS1992, I managed to restore the device.
- installed a stock GB ROM since I was on hboot 1.18, and to get root acces
- aquired root through adb
- gained S-off with revolutionary
reason why I couldn't manage this before is because I didn't have a genuin stock ROM.
tnx all for the help
onemanshow85 said:
SOLVED
with help of KGS1992, I managed to restore the device.
- installed a stock GB ROM since I was on hboot 1.18, and to get root acces
- aquired root through adb
- gained S-off with revolutionary
reason why I couldn't manage this before is because I didn't have a genuin stock ROM.
tnx all for the help
Click to expand...
Click to collapse
Glad you got sorted pal and thanks for letting us know
Recently I tried out a custom rom on my T-mobile branded One S, but I want to revert back to stock in order to do a S-OFF.
Before flashing the custom rom I ran the latest official t-mobile firmware, non rooted, original recovery, h-boot 2.16 and radio 1.15, S-ON. I unlocked the phone with an HTC-dev unlock token, flashed TWRP recovery and flashed a custom rom but left the phone S-ON.
Now I want to revert back to stock so I can do a S-OFF (which is needed for certain roms). I picked a RUU corresponding my CID t-mob101, in this case the only one I could find was:
Code:
RUU_Ville_U_TMO_DE_1.77.111.5_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_259421_signed.exe
I wanted to try this one, but the download link is dead:
Code:
RUU_Ville_U_ICS_40_S_TMO_DE_2.38.111.10_Radio_1.09 es.50.02.07_2_10.09d.50.04L_ver2_release_287723_si gned.exe
I flashed back the original recovery, relocked the phone and tried to run the RUU. However when running the RUU I get an 155 error, which means the RUU isn't corresponding to my CID?
Does this mean i'm out of any options reverting to stock? I don't have a nandroid backup..
Thanks in advance!
Try Magio Rom and do S-off > then flash RUU. It works for me with hboot 2.16
First: S-off using facepalm follow this:
1) update your android sdk by clicking android sdk manager and then update from there.
2) after the update finished, shut down your computer and then turn it on again.
3) turn off your phone, just leave it off for like 5 minutes then go to recovery, wipe cache and dalvik cache, then fix permissions then reboot to system.
4) using ONLY the oem htc usb cable, plug in your phone to a usb 2.0 port.
5) just before doing anything else, first check if your phone is recognized by typing "adb devices", there you should see your devices' serial number if it's recognized correctly.
6) then proceed to the steps of facepalm.
Just remember to NOT do the fastboot flash firmware again after error 92. Then after finishing "fastboot oem boot", your computer should then recognize again your phone, then you could proceed to the last three commands.
This is how i managed to have s-off using facepalm. At first i was really frustrated of that error 99, but a little reading and searching won't hurt you.
Take note that the steps i just said may or may not be required to do so, and i don't know if all these steps are really necessary but i just want to share to you guys that have had the same problem as mine. Good luck guys. Hope this helps.
Click to expand...
Click to collapse
hongha_222 said:
Try Magio Rom and do S-off > then flash RUU. It works for me with hboot 2.16
Click to expand...
Click to collapse
Do I need superCID?
And what RUU is needed in step 5 of the facepalm S-OFF
mk13139 said:
Do I need superCID?
And what RUU is needed in step 5 of the facepalm S-OFF
Click to expand...
Click to collapse
not RUU / PJ4010000-OneS.zip
I think you don't need Supercid. Just try Magio first
hongha_222 said:
not RUU / PJ4010000-OneS.zip
I think you don't need Supercid. Just try Magio first
Click to expand...
Click to collapse
Ok thank you for your help, I will try it out soon!
However in the facepalm thread it says you do need supercid... And for supercid you do need to be S-OFF? That's strange..
When I have S-OFF, I can flash any ROM without boot.img and any RUU right?
mk13139 said:
Ok thank you for your help, I will try it out soon!
However in the facepalm thread it says you do need supercid... And for supercid you do need to be S-OFF? That's strange..
When I have S-OFF, I can flash any ROM without boot.img and any RUU right?
Click to expand...
Click to collapse
Magio rom don't need s-off. You might be stuck at supercid and s-off with hboot 2.16 !!! Try it first to do supercid and s-off
When you have s-off, you can flash any Rom with boot.img and RUU.
hongha_222 said:
Magio rom don't need s-off. You might be stuck at supercid and s-off with hboot 2.16 !!! Try it first to do supercid and s-off
When you have s-off, you can flash any Rom with boot.img and RUU.
Click to expand...
Click to collapse
Hey bro, I was in the same situation as you was. Flashing magio rom brought no luck. Instead of searching for RUU, which I simply cannot get I downloaded the nandroid backup 3.16.111.7 from that awesome guy over at this post http://forum.xda-developers.com/showthread.php?t=2192964&page=2
Copy that to your phone (the backup is big, but google drive is fast, I've downloaded it as fast as 12MB/s) and restore the backup. Note that you need to put the backup into /sdcard/TWRP/BACKUPS/ <your device serial> /
If you dont have <your device serial> folder in BACKUPS, just do a backup of something small, it will appear there.
So restore the backup, boot into the rom you just restored, enable android debugging and run moonshine (HTC One S TMO_DE for 3.16.111.10) - it works flawlessly on the backup of 3.16.111.7.
NOTE: After restoring the backup, you may need to flash original kernel boot.img. All I did was download Bulletproof kernel 1.1 and flash the boot.img in fastboot. If the bootloader is locked, just unlock it by the steps below.
So now you're s-off hopefully, and you can boot into fastboot to get SuperCID (command fastboot oem writecid 11111111), and the bootloader may actually get locked now (or it may not...)
If your bootloader is locked, head on to htcdev and unlock it (you will need new unlock_code.bin, the old one wouldn't work).
After unlocking, just flash your favorite recovery (I use TWRP 2.4.1.0) and voila, you can mount your sdcard or adb sideload the rom zip. You may need to format external sd and then mount your sdcard, then windows will ask to format it, which is good and then you can copy the rom zip.
Hope this helped you, because I was struggling for 3 days with a non-working phone.
m4te said:
Hey bro, I was in the same situation as you was. Flashing magio rom brought no luck. Instead of searching for RUU, which I simply cannot get I downloaded the nandroid backup 3.16.111.7 from that awesome guy over at this post http://forum.xda-developers.com/showthread.php?t=2192964&page=2
Copy that to your phone (the backup is big, but google drive is fast, I've downloaded it as fast as 12MB/s) and restore the backup. Note that you need to put the backup into /sdcard/TWRP/BACKUPS/ <your device serial> /
If you dont have <your device serial> folder in BACKUPS, just do a backup of something small, it will appear there.
So restore the backup, boot into the rom you just restored, enable android debugging and run moonshine (HTC One S TMO_DE for 3.16.111.10) - it works flawlessly on the backup of 3.16.111.7.
NOTE: After restoring the backup, you may need to flash original kernel boot.img. All I did was download Bulletproof kernel 1.1 and flash the boot.img in fastboot. If the bootloader is locked, just unlock it by the steps below.
So now you're s-off hopefully, and you can boot into fastboot to get SuperCID (command fastboot oem writecid 11111111), and the bootloader may actually get locked now (or it may not...)
If your bootloader is locked, head on to htcdev and unlock it (you will need new unlock_code.bin, the old one wouldn't work).
After unlocking, just flash your favorite recovery (I use TWRP 2.4.1.0) and voila, you can mount your sdcard or adb sideload the rom zip. You may need to format external sd and then mount your sdcard, then windows will ask to format it, which is good and then you can copy the rom zip.
Hope this helped you, because I was struggling for 3 days with a non-working phone.
Click to expand...
Click to collapse
Wait all of this would work on hboot 2.16? I have the same problem im s-on but super cid.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Edit: I have an htc one s by rogers so would it matter if i use the nandroid i dont have a tmo htc one s
cyberusman said:
Wait all of this would work on hboot 2.16? I have the same problem im s-on but super cid.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Edit: I have an htc one s by rogers so would it matter if i use the nandroid i dont have a tmo htc one s
Click to expand...
Click to collapse
I was on HBOOT 2.15 (from JB OTA). With that hboot, you can not get SuperCID only by altering it in mmcblk0p4, so I had to do s-off first. If you have SuperCID, why dont you try facepalm s-off method? http://forum.xda-developers.com/showthread.php?t=2155135
Please help. I'm confused. I have HBOOT 2.15
I'm S-ON.
I can't get supercid, because mmcblk0p4 is write protected or something. (I followed exactly the steps but it just doesn't stick)
And I can't S-OFF because for that I need Supercid. But you say you can S-OFF without having supercid?
Sent from my One S using xda app-developers app
rolo143 said:
Please help. I'm confused. I have HBOOT 2.15
I'm S-ON.
I can't get supercid, because mmcblk0p4 is write protected or something. (I followed exactly the steps but it just doesn't stick)
And I can't S-OFF because for that I need Supercid. But you say you can S-OFF without having supercid?
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Have you tried my instructions that are on this page? http://forum.xda-developers.com/showpost.php?p=46939498&postcount=7
I haven't. Can I use that method and install the backup doesn't matter which firmware version I have?
Sent from my One S using xda app-developers app
m4te said:
Hey bro, I was in the same situation as you was. Flashing magio rom brought no luck. Instead of searching for RUU, which I simply cannot get I downloaded the nandroid backup 3.16.111.7 from that awesome guy over at this post http://forum.xda-developers.com/showthread.php?t=2192964&page=2
Copy that to your phone (the backup is big, but google drive is fast, I've downloaded it as fast as 12MB/s) and restore the backup. Note that you need to put the backup into /sdcard/TWRP/BACKUPS/ <your device serial> /
If you dont have <your device serial> folder in BACKUPS, just do a backup of something small, it will appear there.
So restore the backup, boot into the rom you just restored, enable android debugging and run moonshine (HTC One S TMO_DE for 3.16.111.10) - it works flawlessly on the backup of 3.16.111.7.
NOTE: After restoring the backup, you may need to flash original kernel boot.img. All I did was download Bulletproof kernel 1.1 and flash the boot.img in fastboot. If the bootloader is locked, just unlock it by the steps below.
So now you're s-off hopefully, and you can boot into fastboot to get SuperCID (command fastboot oem writecid 11111111), and the bootloader may actually get locked now (or it may not...)
If your bootloader is locked, head on to htcdev and unlock it (you will need new unlock_code.bin, the old one wouldn't work).
After unlocking, just flash your favorite recovery (I use TWRP 2.4.1.0) and voila, you can mount your sdcard or adb sideload the rom zip. You may need to format external sd and then mount your sdcard, then windows will ask to format it, which is good and then you can copy the rom zip.
Hope this helped you, because I was struggling for 3 days with a non-working phone.
Click to expand...
Click to collapse
When you had this problem were you on hboot 2.16? I have super cid but when i try to flash the zip file for face palm s-off it gives me error 99 unkown fail
Running an RUU is only simple for those who haven't been messing with their devices, and that usually isn't us. Since I just did this, I want to write down the steps because I was not able to find easy answers.
This assumes your device is rooted with a different ROM installed. If that is not the case, then you can just download and run the RUU for your device, end of instructions.
Downloading the correct RUU
The most complete list of RUUs for Ville is found on androidruu.com
T-Mobile: http://www.androidruu.com/getdownlo..._10.30.50.08L_release_309489_signed_ICS_2.exe
HTC Europe: http://www.androidruu.com/getdownlo...28_10.27.50.08L_release_301814_signed_2_4.exe
There are RUU updates listed for other service providers, but I can't tell if they are JellyBean hboot 2.15 or not. If someone knows, I'll update this post.
Preparing your device
Make your device s-off if it isn't already. Why?
You will not have to relock the bootloader to perform the RUU update.
You will not have to flash the boot image separately.
If for some reason you can't or won't go s-off, you can still do this, but will have many more steps to follow.
Instructions to make your device s-off are here for firmwares below 3.14: Facepalm S-Off for HTC Devices One S, One XL, Droid DNA
Or you can use the HTC All-In-One Toolkit which helps you through the process.
Use the HTC All-In-One Toolkit (link above) to change the CID to match the RUU.
You needed Super CID to gain s-off, but it won't help you install RUUs. Even if you are Super CID (11111111), you must change your CID to match the RUU you are installing (mine is TMobile: T-MOB010). I know, kinda defeats the purpose of being Super CID, but the RUU won't succeed otherwise. If you are s-off, it is a one click operation using the All-In-One Toolkit.
Backup your device
Use Titanium backup to backup all your user apps so you can restore them afterwards. (No, don't restore system apps please!)
Also back up your ROM by booting into recovery mode and selecting Backup.
If you are only updating the hboot but keeping the same ROM, you can just restore the backup afterwards. Not sure why anyone would need to update the hboot without installing a new ROM, but then you also have a backup in case things go wrong.
Run the RUU
If you are s-on you will have to relock the bootloader by rebooting into the fastboot mode, connecting your device to the computer and running the command "fastboot oem lock". You will also have to follow the process again to unlock your bootloader after doing the update. Tutorials for that are found elsewhere.
1. Leave bootloader unlocked, and leave s-off as is. No need to go back to s-on or relock bootloader.
2. Run the RUU and wait while it updates the phone (Incidentally, it didn't even wipe my sd partition data!)
3. While you are still in bootloader mode (before booting up), use the All-In-One tool to install the TWRP S4 recovery. Or, if you don't want to use the tool, you'll have to download a recovery and use "fastboot flash recovery" followed by the name of the recovery img file.
4. Reboot bootloader and enter recovery mode
5. Restore from backup or Mount USB from TWRP and copy over the ROM and gapps package, flash, wipe cache, and you are up and running.
If you are s-on you will need to extract the boot.img from the zip you are flashing and flash that image separately with "fastboot flash boot boot.img"
Note that device still has the unlocked bootloader and is still s-off! :victory:
My device before: hboot 1.09, unlocked bootloader, Super CID, s-off (In layman's terms, this is a device with an unlocked bootloader so it can accept other ROMs, set to accept any service provider's RUU update via SuperCID, and has had write permission to the boot sector removed via s-off).
My device after: hboot 2.15, unlocked bootloader, T-MOB010 CID, s-off
If possible, I will answer your comments or questions by updating this post and I'll refer you back to here.
Have you changed your CID?
mag13 said:
Have you changed your CID?
Click to expand...
Click to collapse
Please read again.
I was Super CID (11111111) but easily changed it to match TMobile (T-MOB010) with this tool for the update.
Click to expand...
Click to collapse
yooouuri said:
Please read again.
Click to expand...
Click to collapse
I am on Super CID and it does not work
mag13 said:
I am on Super CID and it does not work
Click to expand...
Click to collapse
You have to change your CID back to the one for your RUU.
Can I use this tutorial to rollback to 2.15 or whatever works for ViperS rom with sense 4 after I flashed MaximusHD and firmware?
Now my phone is like this:
Hboot 2.16
Radio 1.20.50 (worst radio ever)
S-OFF
CID 11111111
The rom's with sense 5 (I tried just maximus because the others are not compatible with the new firmware, the sdcard mount point for multi user) are killing my battery more than twice faster compared with ViperS. 2h Display vs 5h on Viper.
Thank you!
Can we use this as rollback from h-boot 2.16 ?
mag13 said:
I am on Super CID and it does not work
Click to expand...
Click to collapse
I didn't think it would. Glad you didn't brick your phone and I'll update the OP based on your experiment.
flow27 said:
Can we use this as rollback from h-boot 2.16 ?
Click to expand...
Click to collapse
arazvan2002 said:
Can I use this tutorial to rollback to 2.15 or whatever works for ViperS rom with sense 4
Click to expand...
Click to collapse
Upgrading your hboot is a one way street, as far as I know. Can't you change the radio to something else?
I flashed Viper ROM. All the things are ok, gsm, wifi, etc just I can't see the internal memory like I should. I can browse to it file es file explorer but I need a method to default mount the new (4.2.2) location of it. Where is mounted by the internal memory in 4.1 JB? I discovered a file vold.fstab. Maybe I can change something like that somewhere to be able to use 4.1 ROM's again.
Sorry for OFF topic.
Somebody asked it but i want a clear awnser.
Can i use it to roll back to 2.15 from 2.16?
yooouuri said:
Somebody asked it but i want a clear awnser.
Can i use it to roll back to 2.15 from 2.16?
Click to expand...
Click to collapse
Yes you can if youre s-off.
Sent from HTC One S using android 4.2.2 sense 5
Im s-off and changen my RUU back to the origonal.
Using RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4
But i get the same error. Cant update because wrong "Update tool".
-------------------------------
Flashed orig_hboot_2.15.0000.zip
But im stuck on 1.20 Radio?
yooouuri said:
Im s-off and changen my RUU back to the origonal.
Using RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4
But i get the same error. Cant update because wrong "Update tool".
-------------------------------
Flashed orig_hboot_2.15.0000.zip
But im stuck on 1.20 Radio?
Click to expand...
Click to collapse
Did you run the RUU.exe when your phone was in bootloader (fastboot USB mode)?
tivofool said:
Did you run the RUU.exe when your phone was in bootloader (fastboot USB mode)?
Click to expand...
Click to collapse
That's the right thing to do, yes?
kilo94 said:
That's the right thing to do, yes?
Click to expand...
Click to collapse
Yes
I have the same problem. I can't go back to stock. I haven't changed my CID yet but I see that has not worked for you.
Did you try with HTC__001 ?
dhigby said:
Running an RUU is only simple for those who haven't been messing with their devices, and that usually isn't us. Since I just did this, I want to write down the steps because I was not able to find easy answers.
This assumes your device is rooted with a different ROM installed. If that is not the case, then you can just download and run the RUU for your device, end of instructions.
Downloading the correct RUU
The most complete list of RUUs for Ville is found on androidruu.com
T-Mobile: http://www.androidruu.com/getdownlo..._10.30.50.08L_release_309489_signed_ICS_2.exe
HTC Europe: http://www.androidruu.com/getdownlo...28_10.27.50.08L_release_301814_signed_2_4.exe
There are RUU updates listed for other service providers, but I can't tell if they are JellyBean hboot 2.15 or not. If someone knows, I'll update this post.
Preparing your device
Make your device s-off if it isn't already. Why?
You will not have to relock the bootloader to perform the RUU update.
You will not have to flash the boot image separately.
If for some reason you can't or won't go s-off, you can still do this, but will have many more steps to follow.
Instructions to make your device s-off are here for firmwares below 3.14: Facepalm S-Off for HTC Devices One S, One XL, Droid DNA
Or you can use the HTC All-In-One Toolkit which helps you through the process.
Use the HTC All-In-One Toolkit (link above) to change the CID to match the RUU.
You needed Super CID to gain s-off, but it won't help you install RUUs. Even if you are Super CID (11111111), you must change your CID to match the RUU you are installing (mine is TMobile: T-MOB010). I know, kinda defeats the purpose of being Super CID, but the RUU won't succeed otherwise. If you are s-off, it is a one click operation using the All-In-One Toolkit.
Backup your device
Use Titanium backup to backup all your user apps so you can restore them afterwards. (No, don't restore system apps please!)
Also back up your ROM by booting into recovery mode and selecting Backup.
If you are only updating the hboot but keeping the same ROM, you can just restore the backup afterwards. Not sure why anyone would need to update the hboot without installing a new ROM, but then you also have a backup in case things go wrong.
Run the RUU
If you are s-on you will have to relock the bootloader by rebooting into the fastboot mode, connecting your device to the computer and running the command "fastboot oem lock". You will also have to follow the process again to unlock your bootloader after doing the update. Tutorials for that are found elsewhere.
1. Leave bootloader unlocked, and leave s-off as is. No need to go back to s-on or relock bootloader.
2. Run the RUU and wait while it updates the phone (Incidentally, it didn't even wipe my sd partition data!)
3. While you are still in bootloader mode (before booting up), use the All-In-One tool to install the TWRP S4 recovery. Or, if you don't want to use the tool, you'll have to download a recovery and use "fastboot flash recovery" followed by the name of the recovery img file.
4. Reboot bootloader and enter recovery mode
5. Restore from backup or Mount USB from TWRP and copy over the ROM and gapps package, flash, wipe cache, and you are up and running.
If you are s-on you will need to extract the boot.img from the zip you are flashing and flash that image separately with "fastboot flash boot boot.img"
Note that device still has the unlocked bootloader and is still s-off! :victory:
My device before: hboot 1.09, unlocked bootloader, Super CID, s-off (In layman's terms, this is a device with an unlocked bootloader so it can accept other ROMs, set to accept any service provider's RUU update via SuperCID, and has had write permission to the boot sector removed via s-off).
My device after: hboot 2.15, unlocked bootloader, T-MOB010 CID, s-off
If possible, I will answer your comments or questions by updating this post and I'll refer you back to here.
Click to expand...
Click to collapse
Hey I used your instructions and everything was perfect thank you. I used to upgarde and downgrade hboot even to restore the HTC one S
I got the RUU "Error: 159" again with both RUU from first post and testet with each common cid, but at the end I only got success with super cid and the TMO_US Ruu.
Now I am back on Hboot 2.15 and can flash again the newest custom-recovery, thank you very much.
I've heard about a flashabe standalone zip for the hboot 2.15 and found this:
Only for S4!
Boot into bootloader and enable fastboot.
Code:
fastboot oem rebootRUU
Wait for the black screen with white HTC symbol. (Like when you flash a RUU)
then enter:
Code:
fastboot flash zip modded_hboot_YOUR_NEEDED_HBOOT.zip
then if you want
Code:
fastboot oem boot
(Boot into your current ROM)
modded_ = The red text is removed and "tampered" is gone in bootloader.
Download:
modded_hboot_1.06.0000.zip - (397.1 KB)
modded_hboot_1.09.0000.zip - (400.6 KB)
modded_hboot_1.13.0000.zip - (399.0 KB)
modded_hboot_1.14.0002.zip - (405.3 KB)
modded_hboot_1.14.0004.zip - (373.2 KB)
modded_hboot_1.14.0005.zip - (373.6 KB)
modded_hboot_2.15.0000.zip - (400.9 KB)
modded_hboot_2.16.0000.zip - (398.6 KB)
Thx goes to: touch of jobo XDA Post Source
DISCLAIMER:this is not my work. i have tested it on my own device,but use it at your own risk. if it melts your phone into a lil pile of goo,its not my fault.
Greetings by Idijt
Hello I have supercid, s-off and previously flashed MAXIMUSHD ROM and that's on hboot 2.16 so I got board and sick of sense 5 and I want to try out one of the kitkat ROMs but I need hboot 2.15 for that and yes I know that there are hboot 2.16 kitkat roms but they are unstable so can someone tell me step by step how to downgrade hboot 2.16 to 2.15 because I'm quite of a dumb person
the_ziom said:
Hello I have supercid, s-off and previously flashed MAXIMUSHD ROM and that's on hboot 2.16 so I got board and sick of sense 5 and I want to try out one of the kitkat ROMs but I need hboot 2.15 for that and yes I know that there are hboot 2.16 kitkat roms but they are unstable so can someone tell me step by step how to downgrade hboot 2.16 to 2.15 because I'm quite of a dumb person
Click to expand...
Click to collapse
This is how I proceed :
1) Downgrade to 2.15 hboot by flashing the old firmware (extract firmware.zip and flash as you did for MaximusHD)
2) Run the latest RUU to get everything clean (I flashed this one)
3) Flash custom recovery with fastboot (TWRP 2.3.X.X)
4) You're done !
benJX said:
This is how I proceed :
1) Downgrade to 2.15 hboot by flashing the old firmware (extract firmware.zip and flash as you did for MaximusHD)
2) Run the latest RUU to get everything clean (I flashed this one)
3) Flash custom recovery with fastboot (TWRP 2.3.X.X)
4) You're done !
Click to expand...
Click to collapse
thank you but i have super cid and from what i have read i have to install the ruu according to my cid
tell me if im right
the_ziom said:
thank you but i have super cid and from what i have read i have to install the ruu according to my cid
tell me if im right
Click to expand...
Click to collapse
In fact, the CID matters if you have one from an operator (have a look here, but not the last one, it's the superCID), in this case, you have to choose a RUU according to your operator.
But being superCID, you can run any RUU, so run the last generic one (see my link) and everything will be ok to start from official clean install. Of course you'll stay S-OFF after running the RUU.
The only thing requested is to be on 2.15 hboot, that's why you have to downgrade to older firmware in order to run this.
Hope it will help.
I have kind of a similar question. After moonshine S-OFF, I'm on modified moonshine HBOOT 2.15.4444. Now I want to go back to the stock HBOOT 2.15.0000. Do I just need to run the RUU to go back? I'm bootloader unlocked, CID T-MOB010, TWRP recovery, and I flashed radio 1.20. Do I need to flash radio back to match the RUU before I run it?
Thanks
dr3amsINdigital said:
I have kind of a similar question. After moonshine S-OFF, I'm on modified moonshine HBOOT 2.15.4444. Now I want to go back to the stock HBOOT 2.15.0000. Do I just need to run the RUU to go back? I'm bootloader unlocked, CID T-MOB010, TWRP recovery, and I flashed radio 1.20. Do I need to flash radio back to match the RUU before I run it?
Thanks
Click to expand...
Click to collapse
Running an RUU is the safest option, although its a bit hit and miss getting the RUU to run correctly. Flashalot recently made a guide (http://forum.xda-developers.com/showthread.php?t=2678700) if you run into any problems. I would try it without changing the radio, if it doesn't work then flash the matching one and go from there.
Now I cannot recommend this, as I have only tried it once myself and the consequences if it went wrong could mean a dead phone, but this post (http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274) details how you can manually flash a hboot version in RUU mode since you are S-OFF. It comes from this thread: http://forum.xda-developers.com/showthread.php?t=1777223. Use it at your own risk, there have been two incidents of bricks but it depends how lucky you are feeling!
rosswhite said:
Running an RUU is the safest option, although its a bit hit and miss getting the RUU to run correctly. Flashalot recently made a guide (http://forum.xda-developers.com/showthread.php?t=2678700) if you run into any problems. I would try it without changing the radio, if it doesn't work then flash the matching one and go from there.
Now I cannot recommend this, as I have only tried it once myself and the consequences if it went wrong could mean a dead phone, but this post (http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274) details how you can manually flash a hboot version in RUU mode since you are S-OFF. It comes from this thread: http://forum.xda-developers.com/showthread.php?t=1777223. Use it at your own risk, there have been two incidents of bricks but it depends how lucky you are feeling!
Click to expand...
Click to collapse
Yeah I heard about that method, but I thought it would be safer to just run the RUU even though it's more work. I think the bricks were from flashing the zips in recovery, not the new ones you flash in fastboot. Either way, I didn't feel like risking it.
Thanks! I'll try the RUU.
dr3amsINdigital said:
Yeah I heard about that method, but I thought it would be safer to just run the RUU even though it's more work. I think the bricks were from flashing the zips in recovery, not the new ones you flash in fastboot. Either way, I didn't feel like risking it.
Thanks! I'll try the RUU.
Click to expand...
Click to collapse
Wise choice, yeah you are right, the bricks were when they were flashing the zips in recovery. Its actually pretty safe in RUU mode but what's the point of risking it.
benJX said:
In fact, the CID matters if you have one from an operator (have a look here, but not the last one, it's the superCID), in this case, you have to choose a RUU according to your operator.
But being superCID, you can run any RUU, so run the last generic one (see my link) and everything will be ok to start from official clean install. Of course you'll stay S-OFF after running the RUU.
The only thing requested is to be on 2.15 hboot, that's why you have to downgrade to older firmware in order to run this.
Hope it will help.
Click to expand...
Click to collapse
dr3amsINdigital said:
I have kind of a similar question. After moonshine S-OFF, I'm on modified moonshine HBOOT 2.15.4444. Now I want to go back to the stock HBOOT 2.15.0000. Do I just need to run the RUU to go back? I'm bootloader unlocked, CID T-MOB010, TWRP recovery, and I flashed radio 1.20. Do I need to flash radio back to match the RUU before I run it?
Thanks
Click to expand...
Click to collapse
rosswhite said:
Running an RUU is the safest option, although its a bit hit and miss getting the RUU to run correctly. Flashalot recently made a guide (http://forum.xda-developers.com/showthread.php?t=2678700) if you run into any problems. I would try it without changing the radio, if it doesn't work then flash the matching one and go from there.
Now I cannot recommend this, as I have only tried it once myself and the consequences if it went wrong could mean a dead phone, but this post (http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274) details how you can manually flash a hboot version in RUU mode since you are S-OFF. It comes from this thread: http://forum.xda-developers.com/showthread.php?t=1777223. Use it at your own risk, there have been two incidents of bricks but it depends how lucky you are feeling!
Click to expand...
Click to collapse
HELP my device does not see any memory and i cant flash any rom hellpp
the_ziom said:
HELP my device does not see any memory and i cant flash any rom hellpp
Click to expand...
Click to collapse
What hboot are you on now? Did you run an RUU to downgrade?
rosswhite said:
What hboot are you on now? Did you run an RUU to downgrade?
Click to expand...
Click to collapse
Hboot 2.15 after running the |RUU.exe|
dont have the memory (does not see device when trying to side load , recovery cant mount sdcard)
help i need my phone
the_ziom said:
Hboot 2.15 after running the |RUU.exe|
dont have the memory (does not see device when trying to side load , recovery cant mount sdcard)
help i need my phone
Click to expand...
Click to collapse
Which recovery did you flash? Try TWRP 2.7.0.0.
the_ziom said:
Hboot 2.15 after running the |RUU.exe|
dont have the memory (does not see device when trying to side load , recovery cant mount sdcard)
help i need my phone
Click to expand...
Click to collapse
Can you boot on stock android rom installed by the ruu ?
rosswhite said:
Which recovery did you flash? Try TWRP 2.7.0.0.
Click to expand...
Click to collapse
i already have twrp 2.7 and i flashed phillz and still nothing
benJX said:
Can you boot on stock android rom installed by the ruu ?
Click to expand...
Click to collapse
yes but i formated my memory to instal a pac man rom
the_ziom said:
yes but i formated my memory to instal a pac man rom
Click to expand...
Click to collapse
So actually you can confirm you are on HBOOT 2.15, Pihllz recovery and no rom installed ?
If yes reboot to bootloader, select clear storage, flash this recovery. Your sdcard should be mountable and let you install your rom.
####
benJX said:
So actually you can confirm you are on HBOOT 2.15, Pihllz recovery and no rom installed ?
If yes reboot to bootloader, select clear storage, flash this recovery. Your sdcard should be mountable and let you install your rom.
Click to expand...
Click to collapse
Another Problem
when ever i try to flash any rom it fails! and i dont know what to do HElp
So many developers and only 2 can help me
Please I'm begging for help
the_ziom said:
Another Problem
when ever i try to flash any rom it fails! and i dont know what to do HElp
Click to expand...
Click to collapse
Flash stock recovery : http://loadbalancing.modaco.com/download.php?file=ville_recovery_signed.img
Then Clear Storage from bootloader and flash TWRP recovery