Database Info

[RESOLVED] Did I kill my phone ? catch-22

Hi,
After running with revolutionary and my rooted stock rom 1.47.401.4, I got yesterday a new OTA with 2.10.401.4 (2.3.5 and sense 3).
When trying to install it, it failed (blue android with big "!" on my screen)
First I downgraded my hboot back to 0.98.0000, but than I did something stupid .
I flash my hboot to the one provided with the OTA 2.00.0002, incl radio and all other stuff from the firmware.zip.
Now I ended up with a *** LOCKED *** HBOOT 2.00.0002, but also a 1.47.401.4 rom with android.
I tried to use the RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085 AU_3805.06.02.03_M_release_199410_signed.exe from windows, but that fails as the hboot has the incorrect version.
THe other thing I could do is go back to a 0.98 HBOOT, but that doesn't work either. the rom is ***LOCKED***, I have no root and it's S-ON.
I also searched for an RUU_Sage_HTC_Europe_*2.10.401.4*.exe as that might work because the HBOOT has the right version, but I could not find anything like that
Does anyone have an idea how I can go forward or how to go back ??
My phone is alive again as used the recovery.img procedure below and installed Saga3D 3.0. After that, I tried also the RUU installation to fully go back to stock, but that doesn't work. It complains about a security failure in hboot screen. I locked it back with 'fastboot oem lock', but that doesn't make the RUU work either.

lessimp said:
THe other thing I could do is go back to a 0.98 HBOOT, but that doesn't work either. the rom is ***LOCKED***, I have no root and it's S-ON.
Click to expand...
Click to collapse
did u try that or u think that wont work?

Before I updated to 2.00.0002, I created a dd-backup on the sdcard for the 0.98.000
when I however use adb to connect, I don't see how I can restore that back without root. I also didn't see the sdcard mounted
I was also thinking ....
Would it maybe also be possible to create a PG88IMG.zip with all the right software for 1.47.401.4 ? and restore that via recovery ? would the current hboot allow a downgrade ?

Today I was able to get the **LOCKED*** off to UNLOCKED via htcdev.com
In the thread http://forum.xda-developers.com/showthread.php?t=1299438
I found this (identical to my problem)
If anyone has the same problem and has hboot-2.00.0002 & S-ON you have to unlock the bootloader via htcdev.com site following all the steps and flash the EXT4 Recovery via FASTBOOT and NOT ADB.!!
Then go to recovery and flash any custom rom.
I don't unserstand what I have to do next. ADB does not work anymore, and only fastboot is available. I downloaded an EXT4 recovery (4EXTRecovery_v2.1.0_saga.zip) which have me an recovery.img and a META-INF folder.
When I name the zip image update.zip, and run
C:\android>fastboot.exe update update.zip
it fails with ...
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
How to I proceed to get it working ?
BTW, HBOOT is UNLOCKED but still S-ON
Please help

you already update hboot right. try this
RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_219480_signed
from here.

budingyun said:
you already update hboot right. try this
RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_219480_signed
from here.
Click to expand...
Click to collapse
You can RUU with that correct version or follow my instructions to achieve custom recovery/rom since you are already "unlocked":
Skanob said:
You should be able to change your recovery without any problem if your s-off or unlocked 2.xx.xx hboot s-on.
1. Get 4ext recovery.img
2. connect phone on fastboot
3. In cmd use these command to push the recovery image:
fastboot flash recovery D:\recovery.img (<- should be directory of 4ext recovery image)
fastboot reboot-bootloader
Now you should have 4ext recovery.
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
From here on you can now flash custom ROMs that you would like that is compatible to Desire S.

[Q] S-OFF & Root on Pyramid whith HBOOT 1.19 is possible?

Hi to hall.
I bought an HTC Sensation with HBOOT 1.17. I've rooted it with the Official LEAK ROM, Sense 3.5 "2.08.401.1_stock_rooted_signed-v0.3.zip" ad S-OFF it.
Unfortunately I had to follow the procedure of S-ON to send back the phone in technical assistance.
Now I have my phone with display repaired, but the assistance have upgrated my HBOOT in new version 1.19.
These are bootloader informations:
*** UNLOCKED ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.19.0000
eMMC-boot
Sep 6 2011,19:13:20
If i try the S-OFF with the revolutionary.io site it tell me tath the 1.19 is not supported.
How can i have the permanent root and the S-OFF?
Thank's and merry christmas to everybody.

can't you run RUU to reflash hboot to early version you use it to flash the revolutionary.io hboot back to stock

I'm a newbie, have you a guide or an how-to url?
Tanks
Sent from my HTC Sensation Z710e using XDA App

UP!
Nobody knows a solution to my problem?

You could try to flash back to hboot 1.17, check http://forum.xda-developers.com/showpost.php?p=20681060&postcount=22.
Just place the file (it must be called PG58IMG.zip) on the root folder of your sd-card, triple check md5 and then boot into bootloader to flash it.
If that works use should be able to S-Off.
Edit: Here are the same instructions (it's about firmware flashing but it's the same method, my reference is also mentioned there)
Edit2: I think Madenssblade is talking about flashing back to an earlier STOCK rom, see here, you can try that if the above does not work

Thank's a lot!
A question, if i launch the downgrade, it will destroy all my data?

If you flash the new ROM, yes (but not the data on your sdcard).
If you succeed in flashing the new hboot, no.
Good luck, I don't know if this all works given your device is S-ON, but it's worth a try (your HBOOT says unlocked).

A small update.
Yesterday i installed the app 4EXT Recovery Control and i noticed with surprise that i still root; perhaps it was sleeping in the state.
I cannot yet find a guide to give the S-OFF at HBOOT 1.19 .

ziopippo said:
I'm a newbie, have you a guide or an how-to url?
Tanks
Sent from my HTC Sensation Z710e using XDA App
Click to expand...
Click to collapse
Hi, try to downgrade your firmware. I am not sure but it may work. Try the following.
A. Downgrading the firmware
Visit this thread. Download v1.17 firmware . Are u having superCID? If so then you can download any v1.17 firmware else choose that firmware file which includes your CID. If you are not sure about your CID follow that same thread to find it.
Flash the firmware by the following method.
1. place Firmware PG58IMG.zip (v1.17) on the root of your sdcard.
2. Remove the battery.
3. Wait a minute.
4. Put the battery.
5.Press power+ volume- key together.
6.Phone will boot into bootloader.
7.Follow the instruction on your phone screen.
If the firmware downgrade successfull then Perform Revolutionary method to make your device S-OFF. If this method does not work try flashing an RUU.
B. Flashing an older RUU (HBOOT 1.17 )
Find a suitable RUU from here.
If RUU Flashing fails, boot into bootloader. Then retry to flash the RUU.
Then try to follow Revolutionary method.

musarraf172 said:
Hi, try to downgrade your firmware. I am not sure but it may work. Try the following.
A. Downgrading the firmware
Visit this thread. Download v1.17 firmware . Are u having superCID? If so then you can download any v1.17 firmware else choose that firmware file which includes your CID. If you are not sure about your CID follow that same thread to find it.
Flash the firmware by the following method.
1. place Firmware PG58IMG.zip (v1.17) on the root of your sdcard.
2. Remove the battery.
3. Wait a minute.
4. Put the battery.
5.Press power+ volume- key together.
6.Phone will boot into bootloader.
7.Follow the instruction on your phone screen.
If the firmware downgrade successfull then Perform Revolutionary method to make your device S-OFF. If this method does not work try flashing an RUU.
B. Flashing an older RUU (HBOOT 1.17 )
Find a suitable RUU from here.
If RUU Flashing fails, boot into bootloader. Then retry to flash the RUU.
Then try to follow Revolutionary method.
Click to expand...
Click to collapse
I have tried this process several times but my HTC says "Parsing PG58IMG.zip"
could this be because i am S-ON? i am trying to downgrade from 1.23

slimldj said:
I have tried this process several times but my HTC says "Parsing PG58IMG.zip"
could this be because i am S-ON? i am trying to downgrade from 1.23
Click to expand...
Click to collapse
Did you try Flashing an RUU?
Sent from my HTC Sensation using Tapatalk

musarraf172 said:
Did you try Flashing an RUU?
Sent from my HTC Sensation using Tapatalk
Click to expand...
Click to collapse
yes. but when i try to, the phone enters the "black htc screen" and after a couple of minutes i get error 155 from the RUU saying i should get the corrent ROM Update utility.
i dont know whats wrong
Also i have tried to get the rom.zip from the temp folder of my computer sourced from the RUU. changed the name to P......zip so that bootloader can flash. it just ends up saying "parsing P........zip"

slimldj said:
yes. but when i try to, the phone enters the "black htc screen" and after a couple of minutes i get error 155 from the RUU saying i should get the corrent ROM Update utility.
i dont know whats wrong
Also i have tried to get the rom.zip from the temp folder of my computer sourced from the RUU. changed the name to P......zip so that bootloader can flash. it just ends up saying "parsing P........zip"
Click to expand...
Click to collapse
As I said earlier , be in bootloader mode first. Then flash RUU. Error 155 should go off.

musarraf172 said:
As I said earlier , be in bootloader mode first. Then flash RUU. Error 155 should go off.
Click to expand...
Click to collapse
tried that as well.. as soon as the RUU says sending, i see the error again... 155

slimldj said:
tried that as well.. as soon as the RUU says sending, i see the error again... 155
Click to expand...
Click to collapse
Hope surely the following posts will help you.
http://forum.xda-developers.com/showthread.php?t=1469296
http://forum.xda-developers.com/showthread.php?t=1478828

musarraf172 said:
Hope surely the following posts will help you.
http://forum.xda-developers.com/showthread.php?t=1469296
http://forum.xda-developers.com/showthread.php?t=1478828
Click to expand...
Click to collapse
hello excuse the disorder but having the same problem on and hboot 1.19 s-on can not flash a stock ruu wanted to ask if you found a way to put s-off.

[Q] S-OFF on HBOOT 1.20

Is there an S-OFF available for HBOOT 1.20? Saw "locked" after flashing 1.20 and S-ONed phone. Finally unlocked using htcdev but nothing I found could help me downgrade HBOOT and do S-OFF again. Do not have SuperCID atm.

there is a thread on this your still rooted even though it says s on

Yeah, I am still rooted and can get into recovery and flash ROMs. But I am having issues with signal and I cannot flash anything because 1.20 does not support fastboot commands. I would like to downgrade but cannot. I tried flashing the customized p85img.zip with my CID T-MOB010 and it would just return to menu w/o any messages.

Make sure it's p85img in the file name.
Don't INSERT .zip at the end. It should automatically be a .zip file.

The file is named correctly.

There is a thread here ima try and find it were you can revert back to hboot 1.17.0000
Sent from my HTC Sensation using xda premium

silverion said:
Is there an S-OFF available for HBOOT 1.20? Saw "locked" after flashing 1.20 and S-ONed phone. Finally unlocked using htcdev but nothing I found could help me downgrade HBOOT and do S-OFF again. Do not have SuperCID atm.
Click to expand...
Click to collapse
i m facinf d same problm wit my sensation with bootloader unlocked thro htc dev. i m unable 2 flash any radios. Even i m unable to flash any custom firmware also. I need ur help if u found any solution.

either downgrade your hboot to 1.17 or update to ics 3.24 which has hboot 1.27 (unlocked) and you will have advance fastboot commands

Same exact problem here, semi-bricked my phone before I went over to Htcdev.... attempting to flash a p85img for HBOOT 1.17 or any p85img does nothing but parse it. Searched all day today couldn't find a thing to help...Others have suggested just waiting until Revolution comes out with an Unlock for 1.20 but I'm determined to find a solution for us.

[Tutorial] Update to hboot 2.15 via RUU

Running an RUU is only simple for those who haven't been messing with their devices, and that usually isn't us. Since I just did this, I want to write down the steps because I was not able to find easy answers.
This assumes your device is rooted with a different ROM installed. If that is not the case, then you can just download and run the RUU for your device, end of instructions.
Downloading the correct RUU
The most complete list of RUUs for Ville is found on androidruu.com
T-Mobile: http://www.androidruu.com/getdownlo..._10.30.50.08L_release_309489_signed_ICS_2.exe
HTC Europe: http://www.androidruu.com/getdownlo...28_10.27.50.08L_release_301814_signed_2_4.exe
There are RUU updates listed for other service providers, but I can't tell if they are JellyBean hboot 2.15 or not. If someone knows, I'll update this post.
Preparing your device
Make your device s-off if it isn't already. Why?
You will not have to relock the bootloader to perform the RUU update.
You will not have to flash the boot image separately.
If for some reason you can't or won't go s-off, you can still do this, but will have many more steps to follow.
Instructions to make your device s-off are here for firmwares below 3.14: Facepalm S-Off for HTC Devices One S, One XL, Droid DNA
Or you can use the HTC All-In-One Toolkit which helps you through the process.
Use the HTC All-In-One Toolkit (link above) to change the CID to match the RUU.
You needed Super CID to gain s-off, but it won't help you install RUUs. Even if you are Super CID (11111111), you must change your CID to match the RUU you are installing (mine is TMobile: T-MOB010). I know, kinda defeats the purpose of being Super CID, but the RUU won't succeed otherwise. If you are s-off, it is a one click operation using the All-In-One Toolkit.
Backup your device
Use Titanium backup to backup all your user apps so you can restore them afterwards. (No, don't restore system apps please!)
Also back up your ROM by booting into recovery mode and selecting Backup.
If you are only updating the hboot but keeping the same ROM, you can just restore the backup afterwards. Not sure why anyone would need to update the hboot without installing a new ROM, but then you also have a backup in case things go wrong.
Run the RUU
If you are s-on you will have to relock the bootloader by rebooting into the fastboot mode, connecting your device to the computer and running the command "fastboot oem lock". You will also have to follow the process again to unlock your bootloader after doing the update. Tutorials for that are found elsewhere.
1. Leave bootloader unlocked, and leave s-off as is. No need to go back to s-on or relock bootloader.
2. Run the RUU and wait while it updates the phone (Incidentally, it didn't even wipe my sd partition data!)
3. While you are still in bootloader mode (before booting up), use the All-In-One tool to install the TWRP S4 recovery. Or, if you don't want to use the tool, you'll have to download a recovery and use "fastboot flash recovery" followed by the name of the recovery img file.
4. Reboot bootloader and enter recovery mode
5. Restore from backup or Mount USB from TWRP and copy over the ROM and gapps package, flash, wipe cache, and you are up and running.
If you are s-on you will need to extract the boot.img from the zip you are flashing and flash that image separately with "fastboot flash boot boot.img"
Note that device still has the unlocked bootloader and is still s-off! :victory:
My device before: hboot 1.09, unlocked bootloader, Super CID, s-off (In layman's terms, this is a device with an unlocked bootloader so it can accept other ROMs, set to accept any service provider's RUU update via SuperCID, and has had write permission to the boot sector removed via s-off).
My device after: hboot 2.15, unlocked bootloader, T-MOB010 CID, s-off
If possible, I will answer your comments or questions by updating this post and I'll refer you back to here.

Have you changed your CID?

mag13 said:
Have you changed your CID?
Click to expand...
Click to collapse
Please read again.
I was Super CID (11111111) but easily changed it to match TMobile (T-MOB010) with this tool for the update.
Click to expand...
Click to collapse

yooouuri said:
Please read again.
Click to expand...
Click to collapse
I am on Super CID and it does not work

mag13 said:
I am on Super CID and it does not work
Click to expand...
Click to collapse
You have to change your CID back to the one for your RUU.

Can I use this tutorial to rollback to 2.15 or whatever works for ViperS rom with sense 4 after I flashed MaximusHD and firmware?
Now my phone is like this:
Hboot 2.16
Radio 1.20.50 (worst radio ever)
S-OFF
CID 11111111
The rom's with sense 5 (I tried just maximus because the others are not compatible with the new firmware, the sdcard mount point for multi user) are killing my battery more than twice faster compared with ViperS. 2h Display vs 5h on Viper.
Thank you!

Can we use this as rollback from h-boot 2.16 ?

mag13 said:
I am on Super CID and it does not work
Click to expand...
Click to collapse
I didn't think it would. Glad you didn't brick your phone and I'll update the OP based on your experiment.

flow27 said:
Can we use this as rollback from h-boot 2.16 ?
Click to expand...
Click to collapse
arazvan2002 said:
Can I use this tutorial to rollback to 2.15 or whatever works for ViperS rom with sense 4
Click to expand...
Click to collapse
Upgrading your hboot is a one way street, as far as I know. Can't you change the radio to something else?

I flashed Viper ROM. All the things are ok, gsm, wifi, etc just I can't see the internal memory like I should. I can browse to it file es file explorer but I need a method to default mount the new (4.2.2) location of it. Where is mounted by the internal memory in 4.1 JB? I discovered a file vold.fstab. Maybe I can change something like that somewhere to be able to use 4.1 ROM's again.
Sorry for OFF topic.

Somebody asked it but i want a clear awnser.
Can i use it to roll back to 2.15 from 2.16?

yooouuri said:
Somebody asked it but i want a clear awnser.
Can i use it to roll back to 2.15 from 2.16?
Click to expand...
Click to collapse
Yes you can if youre s-off.
Sent from HTC One S using android 4.2.2 sense 5

Im s-off and changen my RUU back to the origonal.
Using RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4
But i get the same error. Cant update because wrong "Update tool".
-------------------------------
Flashed orig_hboot_2.15.0000.zip
But im stuck on 1.20 Radio?

yooouuri said:
Im s-off and changen my RUU back to the origonal.
Using RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4
But i get the same error. Cant update because wrong "Update tool".
-------------------------------
Flashed orig_hboot_2.15.0000.zip
But im stuck on 1.20 Radio?
Click to expand...
Click to collapse
Did you run the RUU.exe when your phone was in bootloader (fastboot USB mode)?

tivofool said:
Did you run the RUU.exe when your phone was in bootloader (fastboot USB mode)?
Click to expand...
Click to collapse
That's the right thing to do, yes?

kilo94 said:
That's the right thing to do, yes?
Click to expand...
Click to collapse
Yes

I have the same problem. I can't go back to stock. I haven't changed my CID yet but I see that has not worked for you.
Did you try with HTC__001 ?

dhigby said:
Running an RUU is only simple for those who haven't been messing with their devices, and that usually isn't us. Since I just did this, I want to write down the steps because I was not able to find easy answers.
This assumes your device is rooted with a different ROM installed. If that is not the case, then you can just download and run the RUU for your device, end of instructions.
Downloading the correct RUU
The most complete list of RUUs for Ville is found on androidruu.com
T-Mobile: http://www.androidruu.com/getdownlo..._10.30.50.08L_release_309489_signed_ICS_2.exe
HTC Europe: http://www.androidruu.com/getdownlo...28_10.27.50.08L_release_301814_signed_2_4.exe
There are RUU updates listed for other service providers, but I can't tell if they are JellyBean hboot 2.15 or not. If someone knows, I'll update this post.
Preparing your device
Make your device s-off if it isn't already. Why?
You will not have to relock the bootloader to perform the RUU update.
You will not have to flash the boot image separately.
If for some reason you can't or won't go s-off, you can still do this, but will have many more steps to follow.
Instructions to make your device s-off are here for firmwares below 3.14: Facepalm S-Off for HTC Devices One S, One XL, Droid DNA
Or you can use the HTC All-In-One Toolkit which helps you through the process.
Use the HTC All-In-One Toolkit (link above) to change the CID to match the RUU.
You needed Super CID to gain s-off, but it won't help you install RUUs. Even if you are Super CID (11111111), you must change your CID to match the RUU you are installing (mine is TMobile: T-MOB010). I know, kinda defeats the purpose of being Super CID, but the RUU won't succeed otherwise. If you are s-off, it is a one click operation using the All-In-One Toolkit.
Backup your device
Use Titanium backup to backup all your user apps so you can restore them afterwards. (No, don't restore system apps please!)
Also back up your ROM by booting into recovery mode and selecting Backup.
If you are only updating the hboot but keeping the same ROM, you can just restore the backup afterwards. Not sure why anyone would need to update the hboot without installing a new ROM, but then you also have a backup in case things go wrong.
Run the RUU
If you are s-on you will have to relock the bootloader by rebooting into the fastboot mode, connecting your device to the computer and running the command "fastboot oem lock". You will also have to follow the process again to unlock your bootloader after doing the update. Tutorials for that are found elsewhere.
1. Leave bootloader unlocked, and leave s-off as is. No need to go back to s-on or relock bootloader.
2. Run the RUU and wait while it updates the phone (Incidentally, it didn't even wipe my sd partition data!)
3. While you are still in bootloader mode (before booting up), use the All-In-One tool to install the TWRP S4 recovery. Or, if you don't want to use the tool, you'll have to download a recovery and use "fastboot flash recovery" followed by the name of the recovery img file.
4. Reboot bootloader and enter recovery mode
5. Restore from backup or Mount USB from TWRP and copy over the ROM and gapps package, flash, wipe cache, and you are up and running.
If you are s-on you will need to extract the boot.img from the zip you are flashing and flash that image separately with "fastboot flash boot boot.img"
Note that device still has the unlocked bootloader and is still s-off! :victory:
My device before: hboot 1.09, unlocked bootloader, Super CID, s-off (In layman's terms, this is a device with an unlocked bootloader so it can accept other ROMs, set to accept any service provider's RUU update via SuperCID, and has had write permission to the boot sector removed via s-off).
My device after: hboot 2.15, unlocked bootloader, T-MOB010 CID, s-off
If possible, I will answer your comments or questions by updating this post and I'll refer you back to here.
Click to expand...
Click to collapse
Hey I used your instructions and everything was perfect thank you. I used to upgarde and downgrade hboot even to restore the HTC one S

I got the RUU "Error: 159" again with both RUU from first post and testet with each common cid, but at the end I only got success with super cid and the TMO_US Ruu.
Now I am back on Hboot 2.15 and can flash again the newest custom-recovery, thank you very much.
I've heard about a flashabe standalone zip for the hboot 2.15 and found this:
Only for S4!
Boot into bootloader and enable fastboot.
Code:
fastboot oem rebootRUU
Wait for the black screen with white HTC symbol. (Like when you flash a RUU)
then enter:
Code:
fastboot flash zip modded_hboot_YOUR_NEEDED_HBOOT.zip
then if you want
Code:
fastboot oem boot
(Boot into your current ROM)
modded_ = The red text is removed and "tampered" is gone in bootloader.
Download:
modded_hboot_1.06.0000.zip - (397.1 KB)
modded_hboot_1.09.0000.zip - (400.6 KB)
modded_hboot_1.13.0000.zip - (399.0 KB)
modded_hboot_1.14.0002.zip - (405.3 KB)
modded_hboot_1.14.0004.zip - (373.2 KB)
modded_hboot_1.14.0005.zip - (373.6 KB)
modded_hboot_2.15.0000.zip - (400.9 KB)
modded_hboot_2.16.0000.zip - (398.6 KB)
Thx goes to: touch of jobo XDA Post Source
DISCLAIMER:this is not my work. i have tested it on my own device,but use it at your own risk. if it melts your phone into a lil pile of goo,its not my fault.
Greetings by Idijt

[Q] Any SAFE & easy way to upgrade to HBOOT 2.16? Currently S-OFF with HBOOT 2.15

Hi everyone,
I got S-OFF quite a while back (when the first method came out, can't remember the name) and at that time I also upgraded to HBOOT 2.15 using some RUU (can't remember the details). Also, my factory CID is HTC__001 (I got it SIM-free).
Could anyone recommed a tried and tested way to upgrade to HBOOT 2.16? Wouldn't really want to brick my phone...
Thanks

It's really depressing that no one has an answer for this...

Is there any advantage to 2.16?

Well, as for me, I see the situation like this:
- You have S-OFF. You can flash whatever you like to system partitions, and even to HBoot
- You don't have S-off. You can only flash HTC-signed images to system partitions, sich as hboot, tz, radio, etc
Hboot 2.16 is a stuff from HTC One m7 world and won't won't boot on HTC One S straight away as a dump from that phone. If you modify it, you break signature, so you will get working but not flashable via RUU hboot.
Am I missing something?

@Jem256: Advantages and disadvantages can be found here.
@ovimunt: Upgrading to 2.16 isn't that complicated or risky (AS LONG AS YOU FOLLOW THE INSTRUCTIONS [look at the first post]). If you want to use the mounting option in recovery mode you need to flash the recovery I linked in my signature afterwards.
@ojomio: Actually hboot 2.16 is a leaked firmware which HTC abandoned before it was finished completely but it got finished and released by llabtoofer.

Follow MaximusHD
All U have to do just flash MaximusHD Rom or Follow their instructions coz MaximusHD requires Hboot 2.16