Database Info

[Q] Other possibility to flash my phone to stock ROM?? RUU doesn't work

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

[Q] HBoot and Radio Advice please

Hi,
I've been using custom roms for a couple months now but am still a bit bewildered by the link between HBoot and the Radio.
My current setup is HBoot 1.17.1111, radio 10.14.9035.01_M and virtuous ICS rom. Pretty sure that when it was stock I started with HBoot 1.18.
My question is, do roms include an HBoot flash, i can see a 'boot.img' file in the root directory of the rom zips?
What HBoot/radio combination is recommended?
Ta.

corumuk said:
Hi,
I've been using custom roms for a couple months now but am still a bit bewildered by the link between HBoot and the Radio.
My current setup is HBoot 1.17.1111, radio 10.14.9035.01_M and virtuous ICS rom. Pretty sure that when it was stock I started with HBoot 1.18.
My question is, do roms include an HBoot flash, i can see a 'boot.img' file in the root directory of the rom zips?
What HBoot/radio combination is recommended?
Ta.
Click to expand...
Click to collapse
ROM's do not inclide HBOOT or Radio. only RUU's do.
the best way to get latest hboot and radio is to flash the leaked ICS RUU from capychimp and robocik

Hi mrangry.
From what i understand if i flash the ICS RUU i will retain S-Off but the bootloader will be locked which cannot currently be undone by revolutionary.
When i first attempted unlocking it was following the official HTCDev guide (to the letter) which didn't work (even though it said it was successful), whereas revolutionary worked fine, so i'm a bit apprehensive about flashing the RUU.

ok i've tried applying the ruu, after ensuring supercid is set, but am getting a connection error.
the ruu states 'waiting for bootloader' for a couple of minutes then throws up 'Error 171, usb connection error' even though during the early part of the setup it detected the phone and rom version number. HTC Sync also doesn't seem to detect the phone when connected by USB.
any further tips would be appreciated.
edit: the ruu was run with the phone on as normal, the ruu then tries to reboot into the bootloader. i'm assuming i could try to run the ruu with the bootloader already loaded, but given the problems already wasn't sure whether this would be a good idea.

gave up on the ruu and installed the firmware zip posted in a separate thread. flashed ok, am now restoring a 4ext nandroid.
nothing is ever straightforward is seems!

just thought i'd update and say much improved battery life with the new firmware, just over 48 hours (fairly light use of apps).

[Q] Stuck with HBOOT 1.20

So tried to update when the HBOOT 1.20 firmware leak came out and the update failed. I panicked and did something stupid, while trying to revert to stock I managed to remove SuperCID and put S-ON back on. For awhile I was stuck in bootloader loop. Finally I used htcdev to unlock bootloader and now I have custom recovery and able to flash custom ROMs.
One problem, no WIFI with latest ROMS and I absolutely cannot flash anything that seems to touch HBOOT.
RUUs do not work (black HTC screen, show security failure, update failed after USB is disconnected). RUU log shows unknown failure.
P58IMG.zip (with older or newer HBOOT, or repackaged RUU, does not matter) simply return to the bootloader with no messages.
Fastboot flash attempts fail with error 99.
modelid: PG5810000
cid: T-MOB010
bootloader shows UNLOCKED HBOOT 1.20 S-ON
Please help ! I need either a solid idea how to downgrade so I can revolutionary or at the very least an idea on how to fix WIFI.

I did the same thing, semi-bricked in until I went to htcdev.....as far as your wifi goes, that may be fixed with a new radio...but your is the same as mine and my wifi is working fine, it takes a L O N G time to connect after finding a network though...no clue how to fix your wifi my friend. I have been and still am searching all day for a solution, I think if we can figure out how to get our HBOOT back to 1.18 or below we can use Revolutionary and start from scratch...but this seems to be a problem no one has come up with a fix for. If you find anything let me know and I will do the same.

Hello,
I think the problems that you are facing are due to "S-ON" and the Radio. Try flashing a new radio and try attaining S-Off from HERE

The problem is due to S-ON and mismatched kernel. I cannot however flash radio as 1.20 does not support partial flashes. I guess I am stuck waiting for either official ICS or revolutionary update.

silverion said:
RUUs do not work (black HTC screen, show security failure, update failed after USB is disconnected). RUU log shows unknown failure.
Click to expand...
Click to collapse
Can you try again using your original RUU, which part does it stop or says fail?

silverion said:
The problem is due to S-ON and mismatched kernel. I cannot however flash radio as 1.20 does not support partial flashes. I guess I am stuck waiting for either official ICS or revolutionary update.
Click to expand...
Click to collapse
Have you tried downgrading the RUU to 1.17?

Here is the snippet of the RUU log (TMOUS 1.27.531.2). On the HBOOT screen it says Security Fail! Update Fail!
<T100344><DEBUG><OUT>sending 'zip' (388341 KB)... OKAY</OUT>
</DEBUG></T100344>
<T100344><DEBUG><OUT>writing 'zip'... INFOadopting the signature contained in this image...</OUT>
</DEBUG></T100344>
<T100345><DEBUG><OUT>INFOzip header checking...</OUT>
</DEBUG></T100345>
<T100345><DEBUG><OUT>INFOzip info parsing...</OUT>
</DEBUG></T100345>
<T100345><DEBUG><OUT>FAILED (remote: 99 unknown fail)</OUT>

When attempting to downgrade to 1.17 via P58img.zip it simply returns to the menu after "parsing".

Wow. Have u tried the img from a diff source?
Sent From My steak using A1 steak sauce app (Sensation)

Try using the ruu.exe to downgrade all the way to 1.17. There will be at one time you will get stuck with some error(i forgot, but i do get that), so simply just follow what the the guide asked you to. Remember there will be one time where it will asked you to removed the battery, do remove and put in back but instead of turning on as per normal what you need to do is to enter your phone to fastboot and then bootloader and resume again by pressing next. I manage to get the ruu.exe to complete its full restoration.
Edit: i cant replicate that right now as im on sense 3.0, I have to get back to where my siggy in order to do so.

I am in the same boat.. Same situation and Same Results.. To the poster above doing the RUU 1.17 does not work even after you follow the trouble shooting. I have spent at least 20 hrs working on my phone and nope, I have started threads and nope, I have even tried to disect the RUU and tweak security files to allow it to by pass the fact that it finds a newer image than what i'm trying to put on there, It went further but still nothing.
I believe we must wait until a newer RUU comes out that is newer than the 1.72 image we have. Or until Revo updates to 1.20HBOOT support.

Remove the SD card and try again

Thats weird. I had couple of times switched from s-ons to s-offs and vice versas, from all firmwares and even back to the native firmware without issues. Sorry not much else I can help with.

I ran an RUU that was a higher image than what I have, and still no luck there, and no luck booting the phone up into fastboot and restarting the RUU either. If I could find a way to flash a new radio to match my ROM (revo hd 3.6.13) I would settle for s-on until somebody comes out with something to s-off 1.20 and up.

silverion said:
When attempting to downgrade to 1.17 via P58img.zip it simply returns to the menu after "parsing".
Click to expand...
Click to collapse
Minor point, assume you mean PG58IMG.zip ......

Saxman6699 said:
I ran an RUU that was a higher image than what I have, and still no luck there, and no luck booting the phone up into fastboot and restarting the RUU either. If I could find a way to flash a new radio to match my ROM (revo hd 3.6.13) I would settle for s-on until somebody comes out with something to s-off 1.20 and up.
Click to expand...
Click to collapse
Just because the RUU is a higher image doesn't mean it will work if you don't have SUPER CID, and you can't obtain SUPERCID in this state.
You have to have the RUU from your carrier/country and it must be newer than your image. So me, I am waiting for the official Tmobile RUU ICS
---------- Post added at 03:45 PM ---------- Previous post was at 03:44 PM ----------
johnerz said:
Remove the SD card and try again
Click to expand...
Click to collapse
Remove the SD card and try what again? Try the RUU again? Which one? Any of them? What would the SD card have to do with not passing the Security check put in place regarding the image file?

If you downgrade the hboot back to 1.17 doesn't that break functionality of ics roms? Just curious.
Sent from my HTC Sensation 4G with Beats Audio using XDA App

If you are able to downgrade to 1.17 yes it will break ICS. But who cares as it would allow me to S-OFF again and do everything properly.

Correct, our issue is we cannot even downgrade due to the S-On.

[Q] Rooting needs S-off, S-off-ing needs Root? WTH?

Ok, so I've been searching and browsing the forum for hours now...
I want to install a custom rom/kernel/recovery etc etc on my sensation.
It's currently unlocked with Hboot 1.27 and firmware version 3.32.162.52
Everywhere I look on the forum I find that Rooting needs S-off, and to S-off I need Root access!
Can someone please help me

wjdijkstra said:
Ok, so I've been searching and browsing the forum for hours now...
I want to install a custom rom/kernel/recovery etc etc on my sensation.
It's currently unlocked with Hboot 1.27 and firmware version 3.32.162.52
Everywhere I look on the forum I find that Rooting needs S-off, and to S-off I need Root access!
Can someone please help me
Click to expand...
Click to collapse
look here
http://forum.xda-developers.com/showthread.php?t=1631861

Thanks, but not exactly what I was looking for
I want to either ROOT or S-OFF my sensation... After that I'll install custom roms and whatnot.
Also, when loading a recovery (for example, twrp or 4ext), after that I can't start recovery, it hangs on the htc splash screen, or just reboots the phone
WAIT! just got a working version of 4EXT running, let's mess with this first

wjdijkstra said:
Thanks, but not exactly what I was looking for
Click to expand...
Click to collapse
It is actually.. It shows you how to flash ROMs with s-on, and they will give you root.. You can also just flash superuser from recovery and you will be rooted
So in short, you don't need s-off for root
Sent from my SGH-T999 using Tapatalk 4 Beta

got a rom working now, I'll save the S-offing for later.
Thanks for the help

Well, have to S-off anyway now, I've got the revolution rom loaded, but no wifi/radio.
and I need S-off to flash radio

wjdijkstra said:
Well, have to S-off anyway now, I've got the revolution rom loaded, but no wifi/radio.
and I need S-off to flash radio
Click to expand...
Click to collapse
no wifi!
flash the boot.img of the rom manually

You mean the boot.img that's in the kernel right?
cause I couldn't find one in the rom-zip?

Well, manually loaded the boot.img, no goose.
The guys DO say in the rom topic I have to load their radio img...

cleared cache + dalvik, still no wifi

and here comes the new problem:
s-off by Juopunutbear does not support windows 7 ?
So, any tips on getting S-off now ?
or does a kernel include a good radio rom?
If yes, should I just install Sultan Kernel?

installed sultan kernel, still no wifi
Guys, what am I missing!!!

device is now S-off, still can't install a radio.img
I need help here

Try updating to latest firmware and start fresh
Sent from my SGH-T999 using Tapatalk 4 Beta

or use wifix manager app
basically take a look here
http://forum.xda-developers.com/showthread.php?t=2085009
otherwise do as above user suggested

ooooh, thats a nice topic, thanks ! I'll have a look

unfortunately, that topic didn't REALLY help me.
I've run across a new problem, I can't fastboot flash boot.img because it says FAILED (remote: not allowed)
What does this mean? I had an unlocked bootloader, but after S-off it looks like it's locked again (says locked in purple on the top)?
Do I need to unlock my bootloader again to be able to fastboot flash? If yes, then how do I do this?
thanks in advance

wjdijkstra said:
unfortunately, that topic didn't REALLY help me.
I've run across a new problem, I can't fastboot flash boot.img because it says FAILED (remote: not allowed)
What does this mean? I had an unlocked bootloader, but after S-off it looks like it's locked again (says locked in purple on the top)?
Do I need to unlock my bootloader again to be able to fastboot flash? If yes, then how do I do this?
thanks in advance
Click to expand...
Click to collapse
after achieving S-OFF the bootloader returns to locked situation.(that's why you couldn't perform the fastboot command)
do this now.from this thread flash 3.33 universal
http://forum.xda-developers.com/showthread.php?t=1459767
it will give you also a patched hboot which is unlocked
but before flashing check md5 sums (important)

thank you VERY much!
I now have an unlocked bootloader, firware 3.33, can't wait to get home and flash that sucker

well, the good news is, I have full "control" over my phone now.
The bad news is, I still can't get wifi to work, I'm trying with 3 different roms and like 6 different kernels. I had it working with darksense and one of their included kernels, can't remember which one anymore though. I'm trying to recreate that same situation again, I'll keep you informed of my "accomplishements"
I do have a question though, what EXACTLY controls my wifi? Is it the Radio ? (radio.img) or maybe Boot? (boot.img)
GETril doesnt run properly on my device, so that's no help yet.

[q] 2.16 s-off tmous

This is more of a clarification request than a help question
As I understand it, mind you I am not that well versed in Android dev, you cannot obtain SuperCID/S-OFF either through Moonshine or Facepalm methods when you are on 2.16 HBOOT. Is that correct?
Given this is fact, the only way to have 2.16 + S-OFF is to be S-OFF before upgrading HBOOT to 2.16?
So let's say for my phone I have 2.15 HBOOT Moonshine'd S-OFF, if I upgrade to HBOOT 2.16 will i still maintain my S-OFF status?
And as a side question, what methods are available to upgrade my HBOOT from 2.15 to 2.16? Current phone is TMOUS CM10.1.3 with the latest *.17 firmware.

pyrocide said:
This is more of a clarification request than a help question
As I understand it, mind you I am not that well versed in Android dev, you cannot obtain SuperCID/S-OFF either through Moonshine or Facepalm methods when you are on 2.16 HBOOT. Is that correct?
Given this is fact, the only way to have 2.16 + S-OFF is to be S-OFF before upgrading HBOOT to 2.16?
So let's say for my phone I have 2.15 HBOOT Moonshine'd S-OFF, if I upgrade to HBOOT 2.16 will i still maintain my S-OFF status?
And as a side question, what methods are available to upgrade my HBOOT from 2.15 to 2.16? Current phone is TMOUS CM10.1.3 with the latest *.17 firmware.
Click to expand...
Click to collapse
Yes you stay s-off unless you give a certain command in fastboot. I'm not going to say the command because someone will type it and mess up their phone.
(FYI do not Go back to S-on unless your phone is completely back to stock)
Follow the original post in the Maximus HD thread, that flashes the new firmware that will update the HBoot, Radio, Repartition for new Android. Also the modified TWRP in that post is the only recovery that will work with the new firmware.
Oh, and yes, Moonshine and Facepalm do not work with 2.16. But there is a new way to S-off using rumrunner, that will even work with 2.16.
http://forum.xda-developers.com/showthread.php?t=2558334

tivofool said:
Yes you stay s-off unless you give a certain command in fastboot. I'm not going to say the command because someone will type it and mess up their phone.
(FYI do not Go back to S-on unless your phone is completely back to stock)
Follow the original post in the Maximus HD thread, that flashes the new firmware that will update the HBoot, Radio, Repartition for new Android. Also the modified TWRP in that post is the only recovery that will work with the new firmware.
Oh, and yes, Moonshine and Facepalm do not work with 2.16. But there is a new way to S-off using rumrunner, that will even work with 2.16.
http://forum.xda-developers.com/showthread.php?t=2558334
Click to expand...
Click to collapse
Do i have to be on stock to follow the Maximus install or can I be on a different rom with a different recovery than what is provided in the install package until I flash the provided recovery at the end of the install?

pyrocide said:
Do i have to be on stock to follow the Maximus install or can I be on a different rom with a different recovery than what is provided in the install package until I flash the provided recovery at the end of the install?
Click to expand...
Click to collapse
Ya, that is fine to be on a different ROM and Recovery.
Follow the directions exactly. (for example downloading and installing maximus before installing the new firmware and recovery and then reinstalling Maximus.
-------------------------------------------
Here is another post related to MagioRom. It has firmware update instructions and also a link to a tool if you don't want to manually enter commands.
http://forum.xda-developers.com/showpost.php?p=47403627&postcount=3

tivofool said:
Ya, that is fine to be on a different ROM and Recovery.
Follow the directions exactly. (for example downloading and installing maximus before installing the new firmware and recovery and then reinstalling Maximus.
-------------------------------------------
Here is another post related to MagioRom. It has firmware update instructions and also a link to a tool if you don't want to manually enter commands.
http://forum.xda-developers.com/showpost.php?p=47403627&postcount=3
Click to expand...
Click to collapse
Welp i got past the first install but after rebooting into fastboot and oemReboot trying to flash the recovery (after the firmware.zip was successful) I am stuck at the black screen w/ silver HTC logo and an incomplete green bar. Power down and try again? Or wait some more, been about 5 minutes so far.

pyrocide said:
Welp i got past the first install but after rebooting into fastboot and oemReboot trying to flash the recovery (after the firmware.zip was successful) I am stuck at the black screen w/ silver HTC logo and an incomplete green bar. Power down and try again? Or wait some more, been about 5 minutes so far.
Click to expand...
Click to collapse
I believe you are still in RUU mode, so since the firmware successfully flashed, reboot phone into bootloader and fastboot flash recovery recovery.img

tivofool said:
I believe you are still in RUU mode, so since the firmware successfully flashed, reboot phone into bootloader and fastboot flash recovery recovery.img
Click to expand...
Click to collapse
that is correct, following maximus to the letter it did not mention going back to bootloader after flashing the firmware.zip. What about the incomplete green bar should I be worried about that?

pyrocide said:
that is correct, following maximus to the letter it did not mention going back to bootloader after flashing the firmware.zip. What about the incomplete green bar should I be worried about that?
Click to expand...
Click to collapse
Nope, I'm almost positive you have done everything correctly. Just my memory is a little fuzzy, but I'm pretty sure that is exactly what has happened to me. (I've installed Maximus and firmware 3 different occasions)

tivofool said:
Nope, I'm almost positive you have done everything correctly. Just my memory is a little fuzzy, but I'm pretty sure that is exactly what has happened to me. (I've installed Maximus and firmware 3 different occasions)
Click to expand...
Click to collapse
Still not able to flash recovery after rebooting to bootloader fastboot USB mode.
Device now shows instead of Moonshine at the top
***Tampered***
***Locked***
S-OFF
CID T-MOB010
HBoot 2.16
Code:
C:\adb\Install Package>fastboot flash recovery recovery.img
sending 'recovery' (8900 KB)...
OKAY [ 1.077s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.114s
It shouldnt matter still being s-off, but I still have my unlock token to unlock the bootloader.

pyrocide said:
Still not able to flash recovery after rebooting to bootloader fastboot USB mode.
Device now shows instead of Moonshine at the top
***Tampered***
***Locked***
S-OFF
CID T-MOB010
HBoot 2.16
Code:
C:\adb\Install Package>fastboot flash recovery recovery.img
sending 'recovery' (8900 KB)...
OKAY [ 1.077s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.114s
It shouldnt matter still being s-off, but I still have my unlock token to unlock the bootloader.
Click to expand...
Click to collapse
Yep, that is why. Unlock that bootloader.

tivofool said:
Yep, that is why. Unlock that bootloader.
Click to expand...
Click to collapse
Forgive my ignorance but wasnt the entire point of being S-OFF was not having to jack with the bootloader being locked and unlocked/relocked etc?
Got it to boot, working on second maximus install now.

pyrocide said:
Forgive my ignorance but wasnt the entire point of being S-OFF was not having to jack with the bootloader being locked and unlocked/relocked etc?
Got it to boot, working on second maximus install now.
Click to expand...
Click to collapse
I know what you mean, but no, the bootloader needs to be unlocked to root and flash custom roms. But there is still some security that needs to be turned off to be able to change some things, like HBoot and other things.

tivofool said:
I know what you mean, but no, the bootloader needs to be unlocked to root and flash custom roms. But there is still some security that needs to be turned off to be able to change some things, like HBoot and other things.
Click to expand...
Click to collapse
Thanks for the help, got it booting and charging. Gonna test the battery with the extended battery from the One X+ and see how much better this battery is vs CM10.1.3 and bootloops/reboots etc.