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
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 bought my Sensation few days ago. Updated it to 1.45.401.2, got bored with stock Rom. So I decided to unlock bootloader to use CustomeRoms
I removed SIMCard from Sensation (I needed it in my old phone) and used official bootloader unlocker tool from this site http://www.htcdev.com/bootloader and everything went ok. After unlocking I rebooted my phone to bootloader and saw this:
*** UNLOCKED ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
eMMC-boot
Aug 2 2011,22:35:52
Good so far.
Installed Recovery 5.0.2.0 (official tool doesn't include this) - no problem.
Downloaded ROM SlimSense, made full wipe (cache, data system, dalvik etc) installed it per Recovery (succesfully), rebooted and.... the problems started.
After rebooting bootloop started. Full wipe, reinstalation (succesful again), reboot and the same - bootloop.I thought that instalation .zip file maybe was broken - let's try different. Downloaded virtuous_sensation-s-pyramid-v3.0.0-beta ROM, full wiped, installed (succesfully), reboot and... the same - bootloop.
I started suspecting something is wrong so decided to cure my phone by flashing stockROM. Downloaded RUU_Pyramid_HTC_Europe_1.45.401.2_Radio_10.56.9035 .00U_10.14.9035.01_M_release_208857_signed from XDA, full wiped with recovery, and tried to flash it -RUU founds my phone, reboot it to start instalation (black screen with white htc- missing percentage info) and try to send files to phone for 15-20 sec - then RUU show message that it cannot update my phone. When I unplug phone from usb, phone goes back to bootloader and show:
*** UNLOCKED ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
eMMC-boot
Aug 2 2011,22:35:52
RUU
Security fail!
Update fail!
After this "try" i still have fully working Recovery. I tried also 1.35 and 1.73 stock ROMs - the same fail
I tried to unlock super cid 11111111 but it didn'twork - some SMART_IO.CRD file is missing.
Then i tried to use revolutionary way of unlocking, but without system on the phone it doesn't recognize it. And i can't have system cause RUU doesn't work.
Then I remembered that my SIM card is out of phone.
So I put it back but it didn't change anything: full wipe, instalation of SlimSense, reboot and... bootloop again, the same with virtuos.
The same fail with RUU! , the same supercid and revolutionary failure.
So here comes my question:
Is there any other posibility to flash stock ROM? PG58img somehow?
Pls - DON'T TELL me that i should use revolutionary first - i know it now.
Tell me how to solve this problem.
Tachion81 said:
Hi.
I bought my Sensation few days ago. Updated it to 1.45.401.2, got bored with stock Rom. So I decided to unlock bootloader to use CustomeRoms
I removed SIMCard from Sensation (I needed it in my old phone) and used official bootloader unlocker tool from this site http://www.htcdev.com/bootloader and everything went ok. After unlocking I rebooted my phone to bootloader and saw this:
*** UNLOCKED ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
eMMC-boot
Aug 2 2011,22:35:52
Good so far.
Installed Recovery 5.0.2.0 (official tool doesn't include this) - no problem.
Downloaded ROM SlimSense, made full wipe (cache, data system, dalvik etc) installed it per Recovery (succesfully), rebooted and.... the problems started.
After rebooting bootloop started. Full wipe, reinstalation (succesful again), reboot and the same - bootloop.I thought that instalation .zip file maybe was broken - let's try different. Downloaded virtuous_sensation-s-pyramid-v3.0.0-beta ROM, full wiped, installed (succesfully), reboot and... the same - bootloop.
I started suspecting something is wrong so decided to cure my phone by flashing stockROM. Downloaded RUU_Pyramid_HTC_Europe_1.45.401.2_Radio_10.56.9035 .00U_10.14.9035.01_M_release_208857_signed from XDA, full wiped with recovery, and tried to flash it -RUU founds my phone, reboot it to start instalation (black screen with white htc- missing percentage info) and try to send files to phone for 15-20 sec - then RUU show message that it cannot update my phone. When I unplug phone from usb, phone goes back to bootloader and show:
*** UNLOCKED ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
eMMC-boot
Aug 2 2011,22:35:52
RUU
Security fail!
Update fail!
After this "try" i still have fully working Recovery. I tried also 1.35 and 1.73 stock ROMs - the same fail
I tried to unlock super cid 11111111 but it didn'twork - some SMART_IO.CRD file is missing.
Then i tried to use revolutionary way of unlocking, but without system on the phone it doesn't recognize it. And i can't have system cause RUU doesn't work.
Then I remembered that my SIM card is out of phone.
So I put it back but it didn't change anything: full wipe, instalation of SlimSense, reboot and... bootloop again, the same with virtuos.
The same fail with RUU! , the same supercid and revolutionary failure.
So here comes my question:
Is there any other posibility to flash stock ROM? PG58img somehow?
Pls - DON'T TELL me that i should use revolutionary first - i know it now.
Tell me how to solve this problem.
Click to expand...
Click to collapse
PG58img ??? yes, you can try this : http://goo-inside.me/ruu/pyramid/fu...00U_10.14.9035.01_M_release_208857_signed.zip
after download, rename to PG58IMG.zip and move to root of your sd-card, enter to bootloader -> flash this...
i could be wrong (not an expert) but maybe its failing because your phone still says its S-ON
vegi71 said:
i could be wrong (not an expert) but maybe its failing because your phone still says its S-ON
Click to expand...
Click to collapse
As far as I know Official bootloader unlocker gives only "UNLOCKED" and it's enough to flash custom ROMs.
@ ranggazay
I extracted rom.zip from StockROM 1.45 renamed it to PG58IMG.zip and tried to flash but still nothing. Also tried the same earliers StockRoms (1.35, 1.27 etc).
Unfortunately I can't use your file cause i gave my phone to service.
Any solution?
Hello,
did you find a solution to the problem? I experienced this today and thinking about a repair unless I find something here. Did you get any solution? Thank you.
Try flashing the RUU again whist the phone is on FASTBOOT-USB
Same problem here - I'm interested in any solution
Tachion81 said:
As far as I know Official bootloader unlocker gives only "UNLOCKED" and it's enough to flash custom ROMs.
@ ranggazay
I extracted rom.zip from StockROM 1.45 renamed it to PG58IMG.zip and tried to flash but still nothing. Also tried the same earliers StockRoms (1.35, 1.27 etc).
Unfortunately I can't use your file cause i gave my phone to service.
Click to expand...
Click to collapse
S on will not allow you to flash radios. Unlocked bootloader through HTC does not give you s off which is a requirement to flash custom ROMS.
Sent from my HTC Sensation 4G XE with Beats Audio using xda premium
Htc dev method unlock only few parts of the bootloader.
It doesn't unlock the radio area, it doesn't give you advanced fastboot write command access (that's why you can't change your cid) and I think that the boot.img partition (where there is the kernel) is not flashable from recovery.
You unlocked your bootloader on a 2.3.4 rom (with a 2.3.4 kernel, sense 3.0) and you tried to flash two 2.3.5 roms.
Without the possibility to flash a new kernel your phone was trying to boot with a 2.3.4 stock kernel + a rom that was meant for 2.3.5. This could be the cause of your bootloops.
I would try to install a 2.3.4 rom, like android revolution HD 3.x.x, you could have problems with wifi but it should boot at least.
First of all get S-off then supercid ur phone. You need to have s off to install any custom Rom properly. Ones you do that hopefully solve problem. Try not to messing around u might brick ur phone. You already void ur warranty by unlocking bootloader.
Sent from my HTC Sensation Z710e using xda premium
su27 said:
Same problem here - I'm interested in any solution
Click to expand...
Click to collapse
Grandelama said:
Htc dev method unlock only few parts of the bootloader.
It doesn't unlock the radio area, it doesn't give you advanced fastboot write command access (that's why you can't change your cid) and I think that the boot.img partition (where there is the kernel) is not flashable from recovery.
You unlocked your bootloader on a 2.3.4 rom (with a 2.3.4 kernel, sense 3.0) and you tried to flash two 2.3.5 roms.
Without the possibility to flash a new kernel your phone was trying to boot with a 2.3.4 stock kernel + a rom that was meant for 2.3.5. This could be the cause of your bootloops.
I would try to install a 2.3.4 rom, like android revolution HD 3.x.x, you could have problems with wifi but it should boot at least.
Click to expand...
Click to collapse
Same problem but with different unit--- I have a HTC ChaCha.
Any solutions please? I would love to get S-OFF on my ChaCha but I know that is only possible via an XTC Clip.
Why would he have problems with WiFi? I think my stock ROM got broken or one of the stock ROM's kernels got messed up when I installed BusyBox because for some odd reason when I restored to factory settings with stock ROM the WiFi had problems connecting. It couldn't connect to anything at all.
I had same problem and this is how I solved it
Ok here is answer to solve you
Flash any 2.3.5 Rom and open that zip in computer and extract the boot.IMF file and place it to the web folder in c drive and and flash it immediately after installing Rom
Go to bootloader and make sure fastboot USB connected and then flash the boot.IMG file from cmd prompt
Sent from my HTC Sensation Z710e using XDA
With s-on and **unlocked** via htc.dev, you can't flash radio.img or boot.img, nor can you write using fastboot (eg. superCID). RUU will not run with s-on.
You will need to revert and downgrade via this guide, you can then either continue with custom flashing or run the ruu correct for your original software/baseband/carrier/location.
http://forum.xda-developers.com/showthread.php?p=23222794
Sent from my Pyramid-T
solution
ok here is solution
just after u unlocked your bootloader u have to keep stock rom.....means official 2.3.4 and then u need to flash android revolution rom "3.6.x"
then after that rom boots...........just open the revolutionary.exe and try to root it and i am sure u will get s-off
this is what i did to get out of this problem.......after this super cid your phone and u will be able to flash any ruu.....
if u think this helped press thanks button
ptlsajan said:
ok here is solution
just after u unlocked your bootloader u have to keep stock rom.....means official 2.3.4 and then u need to flash android revolution rom "3.6.x"
then after that rom boots...........just open the revolutionary.exe and try to root it and i am sure u will get s-off
this is what i did to get out of this problem.......after this super cid your phone and u will be able to flash any ruu.....
if u think this helped press thanks button
Click to expand...
Click to collapse
Flashing a custom ROM does not give you s off. Which part of you can't flash radios and kernels with s on do you not get?. You cannot flash Android Revolution ROM with s on. Read the OP of the thread, requires s off.
from my HTC Sensation 4G with Beats Audio using xda premium
Rhiannon224 said:
Flashing a custom ROM does not give you s off. Which part of you can't flash radios and kernels with s on do you not get?. You cannot flash Android Revolution ROM with s on. Read the OP of the thread, requires s off.
from my HTC Sensation 4G with Beats Audio using xda premium
Click to expand...
Click to collapse
You're wrong. You can flash ARHD with s-on. The only requisite is to flash the kernel (boot.img) by "fastboot flash boot boot.img" and voila. You need to have the unlocked bootloader with htcdev too.
My Sensation came with HBOOT 1.21, so no revolutionary at all. I unlocked by htcdev, installed 4ext recovery and ARHD 4.1.3 this way.
nangu said:
You're wrong. You can flash ARHD with s-on. The only requisite is to flash the kernel (boot.img) by "fastboot flash boot boot.img" and voila. You need to have the unlocked bootloader with htcdev too.
My Sensation came with HBOOT 1.21, so no revolutionary at all. I unlocked by htcdev, installed 4ext recovery and ARHD 4.1.3 this way.
Click to expand...
Click to collapse
i read that HBOOT 1.21 can be S-OFFed " reported done by a member " in [S-OFF] Juopunutbear S-OFF or [Finally Here!] HTC Unbricking Project threads , i don't remember if the device on GB or ICS
i think it is Juopunutbear S-OFF search inside it [S-OFF] Juopunutbear S-OFF , it is done using the wire trick , link http://unlimited.io/
the only comment i have , is to verify the S-OFF type , is it like hardware S-OFF " i.e can't be S-ON again for warranty reasons ? " or it Software S-OFF
ruu security fail update fail
hi
i am using htc explorer. somedays before i unlocked my phone through htc developer site. After that i made a partition in my sd card to increase internal memory of phone via using link2sd apps.
i found that my old application like ndtv which were already installed in my phone are not working .i reset my mobile by going into its setting menu.
Now phone stucks htc word screen.
To get out of the problem i tried to installed ruu.
But at the last of its installation part
i get an error 155
and get an message
ruu
security fail
update fail
after rebooting my phone it stucks to htc
show me the way to get out of it.
nirajkpatle said:
hi
i am using htc explorer. somedays before i unlocked my phone through htc developer site. After that i made a partition in my sd card to increase internal memory of phone via using link2sd apps.
i found that my old application like ndtv which were already installed in my phone are not working .i reset my mobile by going into its setting menu.
Now phone stucks htc word screen.
To get out of the problem i tried to installed ruu.
But at the last of its installation part
i get an error 155
and get an message
ruu
security fail
update fail
after rebooting my phone it stucks to htc
show me the way to get out of it.
Click to expand...
Click to collapse
if i remember well error 155 means connection issues
but i can't tell you more because you came in a sensation/xe/4g forum
search for your device's forum and ask there
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!
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
Hi all,
I installed MaximusHD ROM and messed up my partitions so now I have only 2 GB available. I want to fix it by going back to stock ROM.
Currently my phone is superCID, s-off, hboot 2.16, radio 1.20.
From what I've read I should be able to install any RUU but I have not been able to. I tried to do it in fastboot mode and in normal mode when Android is on but without success. Setup starts but some unknown error appears, I think it is error 105... or 150.
I've followed some guides here but the setup won't work because of the unknown error Do I have to look for a specific RUU ?
The only thing that I have not done is to lock my bootloader prior to installing the RUU. However the guides state that I do not have to lock it if my phone is S-OFF.
If I do fastboot getvar all next to "version main" I see nothing, it is empty.
Please help!
I changed my CID to HTC__001 but this did not help Please help me to get back to stock !
mkoev said:
I changed my CID to HTC__001 but this did not help Please help me to get back to stock !
Click to expand...
Click to collapse
I had similar issue what I ended up doing was pulling the recovery image out of the install package and flashing it via fastboot and it restored my sd storage I had to use the modified recovery supplied I would try that- I believe you could change your cid to whatever RUU your trying to flash and it should work also,its seems some have downgraded to hboot 2.1.5 to flash RUU (read,read,read)best of luck
Somehow I fixed my problem yesterday. I was not able to install RUU however I was able to change my hboot back to 1.04 ... afterwards I installed the latest version of TWRP and suddenly I was able to see stuff on my internal memory. Prior to that TWRP 2.3.x.x was not able to detect my whole internal memory. Anyway... my advice to people is not to install MaximusHD via CWM although it says that it works. It does work, but it is easier with TWRP