Database Info

[Q] My phone doesn't boot after loading back a stock firmware

Hi,
Recently I flashed my phone to CyanogenMod 7.1. Later on I changed my mind and wanted to use the latest stock ROM. Specifically RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30.0822U_3822.10.08.04_M_release_219480_signed.exe.
I extracted the file and followed the instructions. After the flashing is done, I got stuck with the HTC logo on the white screen.
Before that I rooted my phone using Revolutionary and used ClockworkMod to install any image, but now this part is gone due to flashing to stock firmware... so I get the original Android system recovery with options like reboot, apply update from sd card, wipe data/factory reset and wipe cache partition.
So, as a result, I am still able to go to the boot menu as usual, but I can't install any image. When I try to open the CyanogenMod ROM file from the sdcard, I get this message:
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Click to expand...
Click to collapse
My boot menu shows this:
- Revolutionary -
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3822.10.08.04_M
eMMC-boot
Mar 10 2011, 14:58:38
Click to expand...
Click to collapse
I tried to connect the USB cable to my PC, but I could not get adb working. Actually, the only thing that recognized my phone was the exe file of the stock firmware (in FASTBOOT USB mode). I wish that I could use revolutionary again or at least to deactivate signature verification, so I would be able to flash using the extended recovery screen (and as a result I would be able to install any ROM that I want).
How do I get out of this messy situation?
Thanks a lot for your help.

The thing messed up because the phone was able to successfully update the ROM, but its your HBOOT now which has a problem. What you've tried to do will NEVER gonna work. You have managed to S-OFF your phone, you should have know already that its unchangeable (on a certain angle).
The latest official ROM uses system/lib on a separate partition but your HBOOT does not support that. That maybe one of the reason why ROM is not booting up.
Installing CM directly won't be successful as you are not in a custom recovery.
Method to get out of this messy situation:
1. Install custom recovery via fastboot
2. Install custom ROM again
3. If you really want to be on stock, you need to change your HBOOT first to either the old S-ON or S-OFF HBOOT, then RUU (GoldCard recommended). It's just easy considering you are still on revolutionary HBOOT.
All the step's guides has already been posted a LOT on the forum, use search.
Hint!
|
V

Thanks so much. That really helped. I thought that getting the original stock ROM back would be as easy as setting a new ROM, so I am back to CM7.1 and everything is fine now.

barman1 said:
Thanks so much. That really helped. I thought that getting the original stock ROM back would be as easy as setting a new ROM, so I am back to CM7.1 and everything is fine now.
Click to expand...
Click to collapse
Good to hear you got it working. Ask a mod to close the thread.

After HTCDEV unlock restore orginal recovery backup

HI , thanks a lot for the great forum , but i have a problem that i dont see in this forum.
Wat i make :
I have a TMO Desire Saga ugrade an Android 3.0 ,
Bootloader:
***LOCKED***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.05.04_M
eMMC-boot
Aug 22 2011, 15:22:13
Android-Version: 2.3.5 (Stock)
HTC Sense 3.0
Software-Nummer: 2.10.401.8
then i make a Root with HTCDEV and i copy over fastboot the cmrecovery.img
At the first boot i think , that i will make a recovery backup of my orginal rom . That i make.
NOw after a will on custom roms i will back to the orginal rom .
Then i think , ok i make a restore of my orginal recovery backup .
That i make with recovery restore , then i turn in the fastboot menu and i will flash the boot.img
then i go to fastboot and copy the boot.img ( i copy this bevor from the sdcard Nanabackup) and flash it with fastboot flash boot boot.img
after this i copy the recovery ( i copy this also from the sdcard of the recovery backup) with fastboot flash recovery recovery.img.
Then i type fastboot oem look and i will hopefull that the saga reboot with the old orginal rom .
but , it dosent work . its start with the tmo splashscreen, after this ist restarts at the bootloader nothing runs.
What i make wrong or do this work??
Sorry for my bad english
Thanks a lot bevor of tells

re
Hi , @ all .
a new question about my problem . Is it possibile to make a flasheble Rom.zip about my nanbackup ?

When you backed up the recovery, you didn't back up your original recovery. You backed up the recovery that was on the device - which was ClockworkMod. You can't back up something that was erased. So your backup is useless.
Also, boot.img taken by the recovery might differ from the original boot.img.
To return to stock, write "Desire S return to stock" in Google and follow one of the guides you'll find on this forum. Or just look in the INDEX thread.

lup0 said:
Then i type fastboot oem look and i will hopefull that the saga reboot with the old orginal rom .
but , it dosent work . its start with the tmo splashscreen, after this ist restarts at the bootloader nothing runs.
Click to expand...
Click to collapse
If you want it to boot again, i'm afraid you have to redo the HTCDev bootloader unlock again.. I did the same thing when trying to downgrade my Hboot to gain S-OFF, I unknowingly typed the fastboot OEM Lock and my DS can't boot up, it will only restart to the bootloader..
Just to check, is the bootloader says something like ***RE-LOCKED***?
If yes, then just unlock it again with HTCDev and you should be able to boot up to recovery, and flash the ROM from there.. But I'm afraid that you can't restore the original stock ROM.. One way to do it is to flash RUU, but you need to downgrade your HBoot first, I suggest you to follow this thread:
http://forum.xda-developers.com/showthread.php?t=1318919
downgrade it and then you can flash the RUU, but you will have it locked down again (if i remember correctly) and you won't have the user data restored (means you will have a clean , stock firmware)
but, since you already rooted and stuff, why not flashing pre-rooted stock ROMs?
http://forum.xda-developers.com/showthread.php?t=1480576
http://forum.xda-developers.com/showthread.php?t=1183684

No need to give bad advice. HBOOT downgrade is NOT needed to flash RUU, only the main_version downgrade (which is just a number stored on MISC partition). The guide for downgrading HBOOT isn't relevant, and there are plenty guides for returning to stock that you could have pointed to.

Can't revert to stock --> T-mob101 (DE), hboot 2.16, S-ON

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

[Q] Can't s-off!

Hi everyone
You must be pretty bored of threads like these!
Basically I can't s-off, so I was hoping for some advice. Here is my fastboot info:
TAMPERED, UNLOCKED
M4_UL PVT SHIP S-ON RL
HBOOT-2.21.0000
RADIO-1.23.40e.00.26
OpenDSP-v19.2.0268.0927
OS-
eMMC-boot 1024MB
I'm running TWRP 2.7.1.1 through which I installed JmzM4StockRootedOdex-WWE-1.22.401.1.zip and JmzM4_Kernel-09-4-13.zip. SuperSU is configured.
I have tried rumrunner, revone and firewater.
Rumrunner: Fails during Test 2. Tried two different PCs running Windows 7 and Ubuntu respectively. Last three entries are:
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
FATAL: Download updated package at rumrunner.us
Revone: ./revone -P gives error message 2 as it should, then after reboot I get error 1 with ./revone -s 0 -u
Firewater: Error: "Kernel contains anti-firewater patch".
So, does anyone have any ideas as to what I can try next? I have seen a couple of other people on the forum who can't s-off under similar circumstances. I don't usually have problems with this sort of thing, but this one has me stumped.
Any help would be appreciated. Thank you.

Any news? I'm in the same boat.
European unlocked regular HTC One Mini.
Have been running 4.3 and I think 4.4.2 ok for a while (don't even know).
I'm 'tampered', 'unlocked' but 's-on'. Hboot 2.21.
Can't supercid, can't flash firmware.
I can flash the twrp 2.7.1.1 though.
I'm now running the JmzM4StockRootedDeOdex-WWE-1.22.401.1.zip rom, with regular SuperSU flashed after it was installed.
Fast boot is off, usb-debugging is on.
Rumrunner gives 'fatal, download updated package at www.rumrunner.us'
Revone gives the 'error -2' when doing ./revone -P.
But after rebooting, 'revone -s 0 -u' just gives 'error -1' and fails, without an error message.

dipje said:
Any news? I'm in the same boat.
European unlocked regular HTC One Mini.
Click to expand...
Click to collapse
Interesting. Glad to hear I'm not alone! What is your CID, out of interest?

moomoomoo2 said:
Interesting. Glad to hear I'm not alone! What is your CID, out of interest?
Click to expand...
Click to collapse
INFOversion-bootloader: 2.21.0000
INFOversion-main: 2.12.401.1
INFOversion-misc: PVT SHIP S-ONINFOplatform: HBOOT-8930
INFOmodelid: PO5820000
INFOcidnum: HTC__E11
revone just keeps giving errors -1/-2.
firewater finally bails out saying I'm running a kernel that has the anti-firewater patch. But I'm running custom kernels that are in the howto's. I flashed boot.img manually through fastboot and made sure by 'uname -a' that I'm indeed running the intended kernel. Tried 'JmzM4_Kernel-09-4-13.zip' and the 'bubba kernel' from 01-nov-2013.
And as I said, rumrunner seems to run OK. (during 'hold please' where you see the **** that become --- slowly, the bar fills up. After that it says it's rebooting into bootloader again, and after that it bails by saying 'FATAL: Download updated package at www.rumrunner.us'.
Different firmware packages I tried to flash all bail with some 'android_info' error, even after making sure the CID and model-ID match. But the way I see it I need to be s-off before those packages work anyway.

Sounds like we've both tried the exact same things. Hopefully someone will be able to help.
I take it you are going through this pain to get sense 6?

Have you guys tried going to SuperSU and change the Default access to grant? And then run rumrunner?

Everest_ said:
Have you guys tried going to SuperSU and change the Default access to grant? And then run rumrunner?
Click to expand...
Click to collapse
Yup, that's how I have my SuperSU. Thank you for your reply.

I will check and try again, but I can't imagine it having an impact, since I'm running firewater and revone from a root-prompt already, and rumrunner runs happily but bails _in_ one of the later fastboot things.
I tried relocking and unlocking through the HTC dev thing again, just in case. Of course (I forgot) that has the effect of my entire /data (including 'sdcard') being wiped, so I now have to push a rom through ADB into recovery to flash and get the device running again.
From that I can turn usb-debugging on again, flash supersu and try setting it to always-grant and try again.
@moomoomoo2: Did you have your device sent to HTC for repairs by any chance?

dipje said:
@moomoomoo2: Did you have your device sent to HTC for repairs by any chance?
Click to expand...
Click to collapse
Not me personally, but I bought the phone second-hand in October 2013 so theoretically it could have been sent to HTC before then.

Hey guys. I am in the same situation. I have htc one mini Europe version with:
Android 4.4.2
Sense 5.5 stock
Hboot 2.21
Unlocked
Rooted
S-On and CID HTC_035
And I can't get S-Off. I tried rumrunner, firewaters, revoke. Same errors like you.
I really want the sense 6 ))
Sent from my HTC One mini using XDA Free mobile app

Seems there's a pattern emerging! For the record, my CID is ORANG001.

Can you guys (or girls) report if your device was ever sent to HTC or not? Just a sneaky suspicion. Mine is, the original posters 'could be'.. until we get a definitive 'no' I'm having a feeling that they did something at the HTC repair .
Right this moment I managed to get my device pretty much back to stock 4.4.2 / sense 5.5 (in detail, firmware 3.10.401.4). I'm 'relocked' (so still tampered) and on the firmware package (hboot, kernel, radio, recovery) that came in the european OTA update.
The thing is, that OTA update was ment to bring me to 3.10.401.6 (the last number is different). My software version now says .4.
If I do the 'search for software updates' it says there is nothing available?! It should report an upgrade to .6 or to the new Sense6 rom I guess. It's the regular european / international version.... my CID and model ID is in the sense6-OTA update's firmware... so I should be able to flash it...
Maybe I'll try that. Flash the untouched firmware that is in the sense6-OTA (it's an OTA file for my model anyway, no idea why it's not showing in the software-updates scan),

The same situation, device was sent to HTC repair.

Well, I'm no closer to the s-off business...
I locked my htcdev bootloader, flashed the firmware from the OTA Europe-3.10.401.6 (4.4.2, Sense 5.5). Then unlocked the bootloader again (Wiping /data, grr) and installed TWRP 2.7.1.1 again.
Then I managed to install Europe-2.12.401.1 from a odex'ed full rom dump here on XDA. Simple flash from TWRP.
Once it is loaded it detects an OTA update to Europe-3.10.401.6 (I already had the OTA files, exactly the same as posted on XDA here).
I kinda modified the update-script for it. Removing the cid checks from the start, and removing the md5-check and patch for '/system/bin/app_process', and then making sure the mount() and unmount() calls matched (no double mounts, etc...) the update-script ran fine from TWRP! I removed the firmware business from the update-script (was already running it) and added an 'app_process' to the system folder so it would be copied. I also removed the 'fota' business at the end of the script.
And it ran! So ignoring the single app_process file (which I took from a 3.10.401.4 dump here on XDA) I was running a pretty good stock 4.4.2-Sense5.5 rom, with official matching firmware. Once the rom loaded up, it detected the OTA update to Europe-4.09.401.3 (4.4.2-Sense6).
I first booted back to fastboot mode, and flashed the official recovery that was in the 3.10 OTA (so I got the proper stock recovery) but left the device unlocker. Booted the ROM back up, started the OTA download and just clicked 'install now' at the end.
It took some time, but the OTA update ran without any modification perfectly it seems. It even flashed the new firmware (I got a slightly new boot logo and I'm on hboot 2.22 all of a sudden) without me needed to relock and unlock the device, and the new 4.09 rom seems to run just fine. It boots, runs fast, camera works, I got signal and wifi works.. I think it's ok. It's late, the rest I gotta check out tomorrow.
Mental note for me: Now make backups of your system dump since it's nice clean and stock, and don't forget to make a backup of the /data/preload folder in case you wipe your /data again. I can still flash TWRP, so getting root should be easy.
I now wonder if just using the supplied firmware package in the Sense6-thread, and modifying it to match my CID and MID would've worked anyway. I tried it, didn't work.. but I didn't know you had to relock the bootloader before flashing firmware as s-on. Anyway, I got my device up to the latest official firmware as stock as it's going to be (hboot, recovery, kernel, system, preload, all stock at the moment. Only htcdev-unlocked and it shows 'tampered'. Feels as a nice base to root and just use it for now .
All this still doesn't answer why our devices will not get s-off working at all.. but the reason I wanted s-off is done now for me, so I'm afraid I don't care anymore

Hi dipje,
I am exactly in the same situation like you was.
But my htc was never send to service.
If your kind please could you write down the process you did step by step and attach some links where needed with the location of the firmware, roms etc that you used and the files that you modified to not check the cid and other.
I will be very thankful.
Thank you very much.
Ovidiu
Sent from my HTC One mini using XDA Free mobile app

Excellent work dipje. Some more info would be great, including the modified script if you still have it. Regarding Europe-2.12.401.1 - was this vrvr's straight dump, or tr1gg3r84's international odex?

This worked for me because I apparently had the right device (right CID). Since we can't change CID without s-off, I was lucky. Also, I was on the 4.4.2 3.10 firmware I believe from an official OTA, but to be honest, I have no clue. Since I'm s-on I could only have installed official firmware files from OTA packages, so I guess I was on hboot 2.21 from the start. Just FYI.
If your CID is not in the list of supposed devices for these OTA updates, you're **** out of luck. At least, as far as I know, I'm not all knowing and only got into flashing my mini not too long ago. My CID is HTC__E11 and that _is_ in the list of supported CIDs for these OTA packages (and the 2.12 international rom we start with). That might be something to check first if you start down this path.
Do yourself a favour, try installing the firmware from OTA 3.10 (it's in the instructions below, you need to relock your device first, try to flash it by reading the fastboot commands, then you can htcdev-unlock again).. If that 'takes' and works OK, you're in the right CID list .
REMEMBER, ALL OF YOUR /DATA (including internal storage) WILL BE GONE!!
(because htcdev-unlocking does that, and to install an official firmware package we have to relock and then unlock again afterwards... If I'm wrong about this, please let me know ).
Anyway, yes I've used "Stock2.12.401.1Odex(tr1gg3r84).zip" as a starting point (http://forum.xda-developers.com/showthread.php?t=2575766).
Then get the 3.10 OTA from http://forum.xda-developers.com/showthread.php?t=2722370. Or, once you have 2.12 booted up let it download the OTA package, but _do not_ execute it. Once downloaded it should be in 'Download' in your internal storage/sdcard. Transfer it to your PC.
Install TWRP 2.7.1.1, then use it to flash tr1gg3r84's 2.12 as is. Start it up, do as minimal setup as you can, make sure you disable fast-boot in the power options (to be sure) and I always enable USB debugging first. (google how to do it if you don't know, it's a sort-of hidden option these days).
Then, relock your bootloader. Go to the bootloader menu and choose fastboot if you have to (hold vol-down while restarting / booting up).
From your PC, use the command line 'fastboot oem lock'. In the command line it will do some stuff (and read error at the end, don't worry) and your device should reboot automatically. After it is booted up, go to the bootloader / fastboot _again_, and this time give the command 'fastboot oem rebootRUU'. Your device should restart quickly to a black screen with a small white HTC logo. Give the command 'fastboot flash zip firmware.zip'. That firmware.zip file is the file that is _inside_ the 3.10 OTA, so you need to extract that first.
If correct, it will start doing stuff and a green bar will slowly fill up. It will _NOT_ reach the end. In your command-line window it should say it completed OK.
Ok, so now we have a 2.12 rom installed with the 3.10 firmware installed. Unlock your device again through htcdev.com, and install TWRP again.
If all is OK, you should be able to flash my modified 3.10 patch (http://clients.maxx-traxx.eu:8080/tmp/xda/mine3.10.zip)
I hope the bandwidth will be OK for that server, if it will be too much I have to upload it somewhere else.
That's what I used in the end, and should be able to install it without problems.
How I created it: The only file from trigger84's 2.12 rom that fails to MD5 check is the modified '/system/bin/app_process'. So I took the file from another 3.10 full dump (the 3.10.401.4 one from trigger too) and placed it inside the /system folder of the extracted OTA update. It will be copied automatically. I removed the lines from the updater-script that try to verify and patch /system/bin/app_process, but left the 'setting permisions' alone. Then I removed all the CID-checking from the start of the script (TWRP can't do that apparently) and removed all the 'fota' stuff from the end ( no clue what it is). Also, remove the lines that try to transfer the firmware.zip package. And as I said, fixed some unmatched mounts/unmounts. With that I mean everytime /system is mounted, it should be unmounted first before trying to be mounted again. The script tries to mount /data multiple times and only unmounts it once or something, and that tends to fail on TWRP.
I've attached my updater-script if you want to check it out and try to do it yourself. Compare the differences between mine and the original in the OTA to see what I mean.
You can delete the fota*** files and the firmware.zip from the OTA package, rezip it (properly, take care of the folder structure, ahem ) and try to flash it.
In the end, it should update OK, and since you already were on the firmware from 3.10, it should boot up OK like normal, _IF_ we flash the correct kernel. So before booting up 3.10 (it will bootloop if you try, no big problem) go to bootloader-fastboot mode again, and give the command 'fastboot flash boot boot.img'. The boot.img is the file that is inside the 3.10 Firmware.zip. The 3.10 should now boot up OK.
So, now you're on 3.10 ROM with 3.10 firmware (notice, 3.10.401.6, not the .4 version). Now, we're gonna install the stock 3.10 recovery again.
Take the 3.10 OTA extracted firmware.zip, and take the recovery.img out of it. Go to bootloader-mode again, and use 'fastboot flash recovery recovery.img' to install it. You now have your stock 3.10 recovery installed, but are still htcdev-unlocked. Start the ROM again.
A software update should be available to 4.09.401.3. Let it download, and let it execute. It should work without any problems, and your phone should reboot a couple of times.
At the end, after Sense6 is up and running, you can go into bootloader-mode again, and flash TWRP again, and use TWRP to flash the SuperSU update package to get root. (Because we're still unlocked, we don't have to do the htcdev-unlock thing this time).
Remember, your /system/bin/app_process file is not stock for sure, and there might be other files. The 4.09 OTA update (Sense6) just doesn't touch those files so it runs without modification, but with a next OTA we might not be so lucky and might have to modify the OTA package again. Do yourself a favour and make a backup of your current /system layout (I guess TWRP can do it), and yourself another favour by also making a backup of the /data/preload folder as it is now. Those files can be hard to come by later on, and if you ever do the htcdev-unlock thing again, they are gone (/data is wiped). Use a root-file-explorer app or something to copy the /data/preload folder to your sdcard/internal storage. Then copy it your PC and zip it up, label it preload-eu-4.09.401.3.zip and keep it safe .
This is not the most noob-friendly guide, but then it isn't intended to be. People who've been fighting to get s-off should know most key-shortcuts, fastboot and adb commands by now

Great guide dipje. Will hopefully help those who have the more generic CIDs. Counts me out unfortunately, but hopefully someone will figure out how to s-off the damn thing!

Hi everybody,
Just for information, i am french (sorry for my poor English ) and i am in the same situation :
One mini rooted, TWRP 2.7.1.1, S-ON, hboot 2.21.0000, revone : fail, rumrunner : fail, firewater : fail...
And my HTC also was sent for repairs (cracked shell, speaker HS, software update).
i am desperate...

I'm getting the feeling that (EU?) hboot 2.21 is simply protected against s-off tricks.
Is downgrading hboot possible with s-on? Guess not.

How to restore to stock using signed OTA Zip

I got the HTC One S (S4) with Hboot 2.15 carrier is Virgin Mobile Canada (Bell Mobility, CID: BM_____1) with bootloader unlock via HTC Dev. I have been using CyanogenMod for quite some time and have no nandoird backup. My phone was updated to JellyBean via an OTA prior to unlocking and installing custom rom.
My reason from wanting to restore to stock is that I can't facepalm s-off but discovered that Moonshine s-off is compatible with my phone and stock OTA from carrier. I want s-off mainly to flash custom kernel. I've been just using fastboot to flash the boot.img thus far but seems that I can't do this with customer kernels.
I looked on the RUU thread in the development section and there is no RUU for my phone (ally RUU's for my carrier are older and don't work). The signed OTA for BM is available as a zip. There is no .exe here. Inside the OTA zip there is a firmware.zip which contains things like the radio, recovery, and boot.img. The zip for the OTA also includes a folder for /system. This is not a system.img but just a folder. There are some other small files also.
I tried locking the bootloader via fastboot and then flashing the OTA zip that doesn't work. If I extract the firmware.zip from the OTA's zip and after running "fastboot oem rebootRUU" I am able to flash the firmware.zip successfully. This however doesn't allow the phone to boot as nothing is flashed to /system.
I'm not sure how to get this to work. I read that what I need to do is rename the OTA's zip to update.zip and place is sdcard partition and then I can from the stock recovery flash this. I am able to get in the stock recovery but when there it displays and error saying that it can't mount sdcard (both CWM and TWRP can mount SD card). How do I flash this to restore to stock. How can I get the /system part of the OTA to flash?