Related
Right, had desire s from three, alpharevx'd it installed clockwork mod, flashed eng hboot. Tried to flash RUU 1.47 europe on it, and it started to work and go through process, updated radio fine, then came up with CID error. No option to do anything but exit. Now I have a desire s that will boot into Bootloader, which has now s-on'd itself and upgraded to 0.98.0002.
Only method of comms seems to be via fastboot.
Now i cant flash the h3g one cos its too low a bootloader version, and i cant upgrade to a newer version cos one don't exist. Can anyone come up with a solution please??
Cheers.
What does HBOOT screen say (in full)?
Are you still able to get into recovery? If yes, then have you tried loading a custom ROM onto the SD card and simply flashing that using the flash zip from sd card option of CWM (clock work mod)?
Unfortunately I am unable to get into recovery, only bootloader, nothing else works. Hboot is displaying a security error at the top highlighted in pink, followed by the version number as described
You should have stuck with the alpharev hboot, which does not allow itself to be overwritten by RUU installs.
Anyway, you need to:
- install hboot 0.980000 (so you can run alpharevx again and get S-OFF)
- run alpharevx and reinstall CWM at the end
- DO NOT install the eng hboot
- flash whatever rom whichever way you want. Your hboot is safe
Follow the instructions on:
http://forum.xda-developers.com/showthread.php?t=1187231
How can I run alpharevx when I can only boot into bootloader tho?
Try running it while in bootloader. Never tryed it that way, but I'm pretty sure it only needs the USB comms to be up, same as adb. Which they should be anyway in bootloader...
Have you tried to re-setup your phone by executing one of the RUU.exe?
k, as i expected, with no access to adb in bootloader mode, i am unable to do anything. Remember, i only have bootloader to work from. I don't eve3n have a recovery partition installed, it just comes back to bootloader whatever i choose, well, bootloader and fastboot anyway.
yup, tried running the ruu again but to no avail. Just get cid error. And i can't make a goldcard either cos i cant get the code. Might just send it back i think and act dumb :/
What about using the "normal" upadte procedure? Placing the PG88(whatever).zip on the root of the sdcard, and have the bootloader install it?
Of courtse with S-ON, it must be a signed version...
If all else fails s-off with xtc clip then flash custom rom
Sent from my HTC Desire S using XDA Premium App
Have you tried to use the original RUU for your phone/network? I'm not sure if it would take care of the CID error.
Any of these:
http://forum.xda-developers.com/showthread.php?t=1002506
Clivectmob said:
yup, tried running the ruu again but to no avail. Just get cid error. And i can't make a goldcard either cos i cant get the code. Might just send it back i think and act dumb :/
Click to expand...
Click to collapse
I do not expect this to work, but you said you are able to get into recovery, correct?
Well, I would try to enter fastboot mode and try to flash cwm via fastboot -> fastboot flash recovery XXXXXXXX.img
Correct (windows) drivers installed?
Edit:
lowveld said:
What about using the "normal" upadte procedure? Placing the PG88(whatever).zip on the root of the sdcard, and have the bootloader install it?
Of courtse with S-ON, it must be a signed version...
Click to expand...
Click to collapse
Good suggestion! Try this one first.
The problem with trying my original ruu for my network is that it contains the lower hboot version, when i flashed the generic ruu earlier, it actually started the update and flashed the radio part, then informed me the cid error, of course, by this time it had updated the hboot too. So now i have a desire s with an upgraded hboot so i can't flash a new one because of cid error and i can;t go back cos it reports a hboot version error. Where do i look on the system for the p88ing.zip now? can't remember now!
I haven't run a RUU in years, but I think that when you run it on a windows machine, it extracts a bunch of files to a directory. Cancel the process, find the directory, find th PG88... in the directory... You get the drift.
Clivectmob said:
The problem with trying my original ruu for my network is that it contains the lower hboot version, when i flashed the generic ruu earlier, it actually started the update and flashed the radio part, then informed me the cid error, of course, by this time it had updated the hboot too. So now i have a desire s with an upgraded hboot so i can't flash a new one because of cid error and i can;t go back cos it reports a hboot version error. Where do i look on the system for the p88ing.zip now? can't remember now!
Click to expand...
Click to collapse
It is not relevant which network you are using !!! Just try newest RUU to get control over your phone again in the first place!
Even if you don't get any network access after setup newest RUU you will definitely be abte to execute alpharevx again, flash cwm and flash any stuff you want to.
just tried flashing via fastboot, got a remote bootloader signature fail response (recovery)
Clivectmob said:
just tried flashing via fastboot, got a remote bootloader signature fail response (recovery)
Click to expand...
Click to collapse
I guess that means you tried flashing recovery via fastboot?
Then concentrate on our RUU-suggestions.
Yes, as i said, flashed via fastboot, and i already explained that i cant up/down grade via ruu method because of bootloader version. I can't think of a way out of this as it stands. The only thing that may work is doing it via the p88img method with my original 3uk rom, but i cant find it in my temp files, searched everywhere for it. I've seen it's location posted on here before now, and i've searched it to death and can't seem to find it now
I'm going to extract and upload your 3GUK-PG88*.img although I think you'll need an newer one. Just a few minutes of patience.
Hi, I think I may have completely screwed the phone up...
I've been on T-Mobile UK with this phone for quite a while now, 2.3.5 updates being available in Europe and on other UK providers for ages, and I know friends have recently received it on T-Mo UK too, but I couldn't get it for some reason. Investigating why with T-Mo customer service was futile so I decided to try and set about upgrading it myself.
I used superoneclick to get temporary root, flashed revolutionary recovery to get S-Off and got myself permanent root on 2.2 -- however something went wrong after this and I'm not quite sure what.
On trying the European RUU (2.10.401.8) it seemed as though it was successful, but going into HBoot, I could see it was no longer Revolutionary branded - instead it says:
Code:
*** LOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot
Aug 22 2011, 15:22:13
Trying to flash another recovery tool doesn't work, trying to flash an earlier version of HBOOT doesn't work. Re-flashing the European unbranded RUU doesn't work because its now picking up that the CID isn't right, and in this environment (Hboot) my gold card doesn't seem to be working. The latest Desire S T-Mobile RUU I can find is version 1.30.110.2, and as its older I get the "Main version is older" error.
I tried extracting the rom.zip from the RUU .exe file, renaming it to PG88IMG.zip - but same error there - and trying to fool it by changing the version number in the manifest inside the archive just makes the sig check fail...
I'm totally outta ideas here, anyone got any more for me to try, or am I going to have to send this off to someone to fix?
Cheers!
edit: Issue solved, see page 2.
Also, in case this information helps - I do have a goldcard.img but it doesn't appear to work. My CID is T-Mob005
this guy seems to have been in the same boat as me but he did everything correctly - http://forum.xda-developers.com/showthread.php?t=1378921
if he still has his goldcard.img is there a chance it would work in my phone? I've PM'd him asking if he still has it
FrakEarth said:
Hi, I think I may have completely screwed the phone up...
I've been on T-Mobile UK with this phone for quite a while now, 2.3.5 updates being available in Europe and on other UK providers for ages, and I know friends have recently received it on T-Mo UK too, but I couldn't get it for some reason. Investigating why with T-Mo customer service was futile so I decided to try and set about upgrading it myself.
I used superoneclick to get temporary root, flashed revolutionary recovery to get S-Off and got myself permanent root on 2.2 -- however something went wrong after this and I'm not quite sure what.
On trying the European RUU (2.10.401.8) it seemed as though it was successful, but going into HBoot, I could see it was no longer Revolutionary branded - instead it says:
Code:
*** LOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot
Aug 22 2011, 15:22:13
Trying to flash another recovery tool doesn't work, trying to flash an earlier version of HBOOT doesn't work. Re-flashing the European unbranded RUU doesn't work because its now picking up that the CID isn't right, and in this environment (Hboot) my gold card doesn't seem to be working. The latest Desire S T-Mobile RUU I can find is version 1.30.110.2, and as its older I get the "Main version is older" error.
I tried extracting the rom.zip from the RUU .exe file, renaming it to PG88IMG.zip - but same error there - and trying to fool it by changing the version number in the manifest inside the archive just makes the sig check fail...
I'm totally outta ideas here, anyone got any more for me to try, or am I going to have to send this off to someone to fix?
Cheers!
Click to expand...
Click to collapse
Relax, you have simply gotten the locked bootloader flashed to your phone. You can go to the HTCDEV.com site and unlock the bootloader and then you will be able to install a custom recovery and root the phone again.
tpbklake said:
Relax, you have simply gotten the locked bootloader flashed to your phone. You can go to the HTCDEV.com site and unlock the bootloader and then you will be able to install a custom recovery and root the phone again.
Click to expand...
Click to collapse
Thanks, that's one problem down!
At present I have this RUU Europe Rom that won't load, and the T-MO UK ones still won't install either. I've installed ClockwordMod Recovery 5.0.2.0, so that's good, but I take it I still need a goldcard if I'm going to install a ROM that doesn't match my phone's carrier ID?
Is the reason these older T-Mobile ROMS won't install because of S-ON and the higher radio version number?
edit: by the way, cyanogenmod and similar ROMs appear to install with no errors in clockworkmod recovery but I don't think they are. If I load one of the RUU exes it shows the same 2.10.4 version number with no changes evident whatsoever.
Don't do all so fast. READ FORUMS, READ COMMENTS. Revolutionary wont work with 2.00.0002 . It wont work
Sent from my HTC Desire S using xda premium
gefilus said:
Don't do all so fast. READ FORUMS, READ COMMENTS. Revolutionary wont work with 2.00.0002 . It wont work
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
I realise that now... I'm less concerned about rooting / getting full S-Off again and more concerned with just getting any working ROM at all onto the phone... as it seems the only ones that are probably going to work are T-Mobile ones, and the only available ROMs I can find are older - I may have to send this off to someone
So you cab get into fastboot?? If you can then use downgrading without HTC Dec unlocked bootloader, there is a post about this, try it should work and use misc_version to let phone thinks he is on older hboot and then use latest T-Mobile ruu. I hope and it should work.
Sent from my HTC Desire S using xda premium
i would do this:
unlock with htcdev.com
downgrade hboot to 0.98.0000
use revolutionary for s-off
change cid to supercid
relock bootloader again
and flash the ruu of youre dreams.
think this should do it
This worked for me in the same situation
http://forum.xda-developers.com/showthread.php?t=1443636
Is there a way to get adb terminal access when the phone won't actually load a ROM?
Because all the tutorials I can find for downgrading HBOOT or installing an older ROM (with misc_version etc) - seem to require adb access. I can *only* get into fastboot or a recovery tool like clockworkmod recovery.
Installs of ROMs just aren't working at all. I'm getting "Security Fail" on some of the official ROMs, and the custom roms just aren't working (I assume because of S-ON).
FrakEarth said:
Is there a way to get adb terminal access when the phone won't actually load a ROM?
Because all the tutorials I can find for downgrading HBOOT or installing an older ROM (with misc_version etc) - seem to require adb access. I can *only* get into fastboot or a recovery tool like clockworkmod recovery.
Installs of ROMs just aren't working at all. I'm getting "Security Fail" on some of the official ROMs, and the custom roms just aren't working (I assume because of S-ON).
Click to expand...
Click to collapse
Only if you left on USB dedebuging if it's off then sorry can't. Bet if its o n you can easy make him to boot into fastboot. Take a try, and you need to be installed sdk and adb tools on, PC. Try switch on phone put into USB and open terminal, write adb devices if it works there will show a list and HTXXXXXXXXXX something. If it so then adb reboot - bootloader or if you have custom recovery boot there. If don't anderstand look commands in Wikipedia about adb. Good luck
Sent from my HTC Desire S using xda premium
Okay guys, managed to get this sorted.
Firstly, I read that if you mounted /system from Clockwork mod that ADB commands work... well I didn't get to try that out, because something else worked.
One of the reason RUU updates were failing was because the bootloader was unlocked, when I relocked (fastboot oem lock) they started working again, but I was getting Carrier ID errors on the European RUUs and the T-Mobile ones were too old.
I decided to visit a friend who also has a Desire S and from his phone I was able to get the CID (card identification register) code from a smaller microSD card I have -- this was one I hadn't tried as a goldcard before, and I was unable to try without being able to get at the GoldCard Helper app on my phone... so after using his phone and writing down BOTH CIDs, I tried both and it worked -- I now have the phone updated fully using the European RUU.
I think my mistake the first time may have been copying the wrong CID from Goldcard Helper: if you press Menu > Copy Code it seems to copy the code from MMC1, whereas my SD card was clearly MMC2 -- so my goldcard.img was completely incorrect the first time I tried it. I don't know why the phone let me partially install the European RUU without a goldcard and almost brick the phone, but I suspect it was because I had the Revolutionary bootloader with S-OFF.
So in summary if you have this problem I would suggest borrowing an Android phone (any should work) to get the right goldcard CID needed and then try installing an RUU.
Many thanks to everyone who replied and tried to help me, you guys helped me exhaust every other possibility - and I appreciate it a lot! Thanks!
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
UPDATE 30/11/2013:
This thread describes my efforts in updating my unlocked One S to a hboot higher than 2.13. The phone had an H3G CID but non of the RUU's (see thread) worked. For me the solution was to Super CID and S-OFF the phone. Iḿ now on hboot 2.16.
END UPDATE
After more than two years of using Android (Legend, Desire S) phones and rooting them, I now have to register to be able to ask a question on this great forum.
Yesterday I obtained a One S. It is a UK model (not sim-locked to a carrier). I unlocked the bootloader almost immediatly with the intention of running a 4.3 or 4.4 based ROM (cyanogenmod or codename lungo). Here are some of the getvar details:
Code:
version: 0.5
version-bootloader: 2.13.0000
version-baseband: 1.11.50.05.28
version-misc: PVT SHIP S-ON
cidnum: H3G__001
boot-mode: FASTBOOT
Both cyanogen 4.4 and lungo ended in a bootloop and I figured it had to do with the hboot version. Self assured as I was I did not do a nandroid backup in twrp when flashing cyanogen and lungo and I ended up looking for a rom that would boot. I was succesful with MagioRom_ONE_S_RC6. From that I intended to use a RUU to update my hboot. I tried several (including both the H3G's) from this resource. All ended up in errors (131, 132, 155, 170 and probably some more). After reading some threads I relocked the bootloader and flashed stock recovery. All to no avail, no RUU will install. After reading a bit more I concluded that SuperCID was my best option of getting my brand new One S to a higher hboot version. I decided to go with this tutorial, but I ended up in another frustration: adb is not working for me in both windows (7) and linux (ubuntu). I reinstall the drivers (under windows) and tried some other things, but nothing works.
This is where I am now. I hope someone is willing to help. I tried to be as complete in describing the things I tried and the information I have, but I'd be happy to provide any additional info.
Getting custom roms on the legend and desire s was a lot easier.
First I do not own a UK version One S, I have the TMOUS but these are some tips that I used to help get my phone back from a non booting state.
Couple things,
Make absolutely sure this is a Ville not a VilleC2 (aka S3 One S)
Are you at all able to boot the phone to a recovery program (TWRP/CWM etc)?
Ensure that you have followed these instructions to get adb and fastboot to work. Use the Unlock section. Its best to make sure you can fastboot or at least adb before doing anything with the phone.
If you can get to fastboot (Power and Vol Down button), connect your phone and run the command "fastboot devices" post output - keep in mind command shell has to be at the adb directory most of the time C:\adb or something similar.
Make sure you have the latest driver installed and to remove (completely uninstall it) HTC Sync or Sync Manager. Not needed if you don't keep the stock ROM on your phone IMO. If you are unsure, remove all HTC software and just reinstall the driver.
Make sure you are running the right RUU for your specific device. What carrier was this phone for when it was purchased? Assuming it is H3G this is the latest RUU available for that particular OneS. You will have to run either the same version F/W or later RUU, you cannot go backwards.
Once we get the phone back to stock rom. Then start over by unlocking bootloader and getting S-OFF THEN start to flash roms.
In order to run CM11 Beta you need to have l a certain recovery installed + a few other things. I think it would be best if you can get back on CM10.1.3 Stable first then attempt to go to CM11.
TL;DR
Verify carrier and version of phone
Lock Bootloader if not already done
Download and run carrier specific RUU while in fastboot mode (power +vol down)
Unlock Bootloader
S-OFF
Flash rom
@pyrocide
Thanks for the reply. I've been working through your post. First I wanna point out that the phone is in a working state know running the MagioRom and I can boot into TWRP recovery.
Here is the output for fastboot devices:
Code:
SH24PW402945 fastboot
I'm sure it is an s4. It is says Z520e and 1.5 ghz on the box. I got the phone from ebay, so I'm not 100% which carrier it was on, but there was a T-Mobile sim still in the phone :silly:. The CID reads H3G though and the phone is not locked to a carrier/network since my giffgaff sim works fine.
I got adb to work. Thanks for that :good:.
I relocked the bootloader with fastboot oem lock (it know says 'relocked'). Running the suggested RUU ends in an error 155 during the veryfiying signature step.
And you ran the RUU while you were in fastboot usb mode?
based on Google
"ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again."
So the RUU is wrong, we need to find out specifically what version of OneS it is.
run this command while in fasboot usb mode
Code:
fastboot getvar all
post modelid: XXXXXXXXXX
The output of that:
Code:
modelid: PJ4010000
http://androidforums.appforerunner....ed-problem-restoring-ruu-error-131-151-a.html
Guy had the same problem and same modelid
Used this RUU and was able to go back to stock.
Hopefully this works.
Thanks for the help. Appreciate it.
That RUU ended in an 131 error, unfortunately.
H2Oxide said:
Thanks for the help. Appreciate it.
That RUU ended in an 131 error, unfortunately.
Click to expand...
Click to collapse
At this point i would suggest doing all Euro RUUs. That should have worked considering the modelid is the same for that guy and it worked. Sorry man but I don't know what else to suggest other than to do each RUU. If none of them work then something is definitely wrong.
pyrocide said:
At this point i would suggest doing all Euro RUUs. That should have worked considering the modelid is the same for that guy and it worked. Sorry man but I don't know what else to suggest other than to do each RUU. If none of them work then something is definitely wrong.
Click to expand...
Click to collapse
Would I need to reflash a/the stock recovery to make for a successful RUU flash?
The list of the RUU's I tried. Non worked... Really frustrating.
Code:
RUU_Ville_U_BM_1.70.666.1_R_Radio_0.16.31501S.06_3_10.20.31501S.09L_release_255222_signed.exe
RUU_Ville_U_BM_1.84.666.9_Radio_0.17.31501S.10_2_10.27.31501S.10L_release_265369_signed.exe
RUU_Ville_U_H3G_UK_1.53.771.4_Radio_0.15.31501S.19_2_10.13.31501S.06L_release_251870_signed.exe
RUU_Ville_U_H3G_UK_1.78.771.5_Radio_0.16.31501S.19_2_10.23.31501S.10L_release_258982_signed.exe
RUU_Ville_U_HTC_Europe_1.09.401.1_R_Radio_0.14.3059.14_2_release_243825_signed.exe
RUU_Ville_U_HTC_Europe_1.47.401.1_Radio_0.15.31501S.13_3_10.08.31501S.04L_release_250115_signed.exe
RUU_Ville_U_HTC_Europe_1.53.401.2_Radio_0.15.31501S.19_10.12.31501S.06L_release_251412_signed.exe
RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed.exe
RUU_Ville_U_ICS_40_S_BM_2.40.666.1_Radio_1.09ts.50.02.04_10.08g.50.04L_release_280275_signed.exe
RUU_Ville_U_ICS_40_S_HTC_Europe_2.21.401.10_Radio_1.06s.50.02.27_2_10.08.50.04L__release_271119_signed.exe
RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5.exe
RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed.exe
RUU_Ville_U_ICS_40_S_TMOUS_2.35.531.7_Radio_1.08ts.50.02.16_10.08e.50.04L_release_279577_signed.exe
RUU_Ville_U_ICS_40_S_Vodafone_UK_2.38.161.6_Radio_1.08es.50.02.21_10.09c.50.04L_release_280400_signed.exe
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.exe
RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.50.05.31_10.30.50.08L_release_309489_signed_ICS_2.exe
RUU_Ville_U_O2_UK_1.78.206.4_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258707_signed.exe
RUU_Ville_U_TMO_DE_1.77.111.5_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_259421_signed.exe
RUU_Ville_U_TMOUS_1.53.531.16_Radio_0.16.31501S.02_10.18.31501S.08L_release_262073_signed.exe
RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S.16_2_10.22.31501S.10L_release_263233_signed.exe
RUU_Ville_U_Vodafone_UK_1.53.161.3_Radio_0.15.31501S.19_2_10.13.31501S.06L_release_251482_signed.exe
RUU_Ville_U_Vodafone_UK_1.78.161.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258386_signed.exe
H2Oxide said:
Would I need to reflash a/the stock recovery to make for a successful RUU flash?
Click to expand...
Click to collapse
No, running the RUU erases custom recovery & flashes stock recovery.
Did all of the downloads MD5 checkout correctly?
Also, just to make sure we are ruling everything out. Did you run the RUU by double clicking or right clicking and Run as Administrator? If you just did it by double clicking rerun the one I posted that fixed the other guys issue by using Run as Administrator. Again be sure to be in fastboot usb mode and that "fastboot devices" command shows your device in the output. Make sure you use a usb 2.0 port in case of compatibility issues and the cable that came with the phone if possible.
pyrocide said:
No, running the RUU erases custom recovery & flashes stock recovery.
Did all of the downloads MD5 checkout correctly?
Also, just to make sure we are ruling everything out. Did you run the RUU by double clicking or right clicking and Run as Administrator? If you just did it by double clicking rerun the one I posted that fixed the other guys issue by using Run as Administrator. Again be sure to be in fastboot usb mode and that "fastboot devices" command shows your device in the output. Make sure you use a usb 2.0 port in case of compatibility issues and the cable that came with the phone if possible.
Click to expand...
Click to collapse
I used another laptop. Running the suggested RUU again resulted in the same 131 error. I ran as admin and did an md5 check. I'd say the other RUU's will also result in an error again...
H2Oxide said:
I used another laptop. Running the suggested RUU again resulted in the same 131 error. I ran as admin and did an md5 check. I'd say the other RUU's will also result in an error again...
Click to expand...
Click to collapse
Did some digging.
Error 155 - usually wrong recovery.img /wrong boot.img
Error 140 - wrong bootloader / bootloader unlocked
Error 131 - wrong RUU for your device
So, if one is giving you the 155 error then try with the stock recovery and do the RUU.
The phone does say relocked in bootloader right? Try doing fastboot oem lock again and run the RUU that gave you the 155 error.
Wow, that still didn't work.
So I flashed stock recovery and relocked the bootloader. Then I tried three RUU's, both the H3G RUU's and the HTC Europe RUU mentoined before. The H3G's ended up in a 155 error, the HTC Europe in a 131.
So, still no succes. This is getting annoying, right... ? Any other suggestions besides flushing the One S down the toilet?
Regards.
H2Oxide said:
Wow, that still didn't work.
So I flashed stock recovery and relocked the bootloader. Then I tried three RUU's, both the H3G RUU's and the HTC Europe RUU mentoined before. The H3G's ended up in a 155 error, the HTC Europe in a 131.
So, still no succes. This is getting annoying, right... ? Any other suggestions besides flushing the One S down the toilet?
Regards.
Click to expand...
Click to collapse
Im at a loss man. At this point I would email HTC with the getvar all info and see what they say and which RUU they give you to try. If nothing else itll help narrow down exactly what model phone it is.
pyrocide said:
Im at a loss man. At this point I would email HTC with the getvar all info and see what they say and which RUU they give you to try. If nothing else itll help narrow down exactly what model phone it is.
Click to expand...
Click to collapse
Just a thought. Since the 155 error could point to both a wrong recovery.img or a wrong boot.img, I could try flashing another (stock) boot.img. Maybe the custom rom's boot.img is in the way. So what boot.img would I need?
So I did that. I extracted the boot.img from de H3G RUU and flashed it. I also extracted the recovery and flashed that. I then tried different scenario's with the H3G, the HTC Europe and the O2 UK RUU's. Non worked. The H3G ended up in 155, the others in 131.
Anyone else any ideas on this besides emailing HTC?
H2Oxide said:
Just a thought. Since the 155 error could point to both a wrong recovery.img or a wrong boot.img, I could try flashing another (stock) boot.img. Maybe the custom rom's boot.img is in the way. So what boot.img would I need?
Click to expand...
Click to collapse
You could try to decompile the 155 error exe and fastboot flash boot boot.img but I am very nervous that might screw something up. I still suggest contacting HTC directly to have their input on what exactly RUU is needed and if you do have the right one, why it is not working.
Code:
<T133845><DEBUG><OUT>FAILED (remote: 44 hboot version check fail)</OUT>
Got the line above out the RUU log files. This is the 155 error RUU.
This raises two question:
Is it possible to get the expected hboot version number out the decompiled RUU (decompiled = the stuff placed in user/temp)?
Is it possible to down/upgrade hboot with any of the hboot versions posted here or would I run the risk of softbricking my One S then?
Don't flash any of that hboots. You will brick.
Just try to s-off, follow facepalm method in dev forum.
After that you can flash any ruu.
Sent from my HTC One S using Tapatalk
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.