Database Info

Signature verify fail

I need help. I am trying to revert back to stock but when I run RUU for my HTC One S T-Mobile USA it stops every time when trying to verify the signature. I locked my bootloader and tried unlocking it and the same thing happened when verifying my signature it said it failed. I don't know what to do please help me.

Did you flash a signed stock recovery before locking the bootloader?

reverting from a higher firmware version to lower is not possible until the s-off is achieved for htc s

touch of jobo said:
Did you flash a signed stock recovery before locking the bootloader?
Click to expand...
Click to collapse
im not quite sure I'm using a trickdroid rom. Is there anyway that i can still do that?

In order to run a RUU, your must have a signed stock recovery [ <-- Edit: That may not be true, according to post below this one. ] and a locked bootloader. However, in order to flash a recovery, you must have an unlocked bootloader.
So if you are locked but still have a custom recovery, you have to unlock again so that you can flash a stock recovery. Then lock and RUU.
Also, like mughalgxt said, you can not run a RUU with an oler hboot than you have now.

touch of jobo said:
In order to run a RUU, your must have a signed stock recovery and a locked bootloader. However, in order to flash a recovery, you must have an unlocked bootloader.
So if you are locked but still have a custom recovery, you have to unlock again so that you can flash a stock recovery. Then lock and RUU.
Also, like mughalgxt said, you can not run a RUU with an oler hboot than you have now.
Click to expand...
Click to collapse
Just relocking the bootloader is sufficient to enable an RUU install. The RUU will re-install the stock recovery (wether you want it or not)

bobsie41 said:
Just relocking the bootloader is sufficient to enable an RUU install. The RUU will re-install the stock recovery (wether you want it or not)
Click to expand...
Click to collapse
But I have tried to update with a re locked bootloader and every time it fails at the signature verification

touch of jobo said:
In order to run a RUU, your must have a signed stock recovery [ <-- Edit: That may not be true, according to post below this one. ] and a locked bootloader. However, in order to flash a recovery, you must have an unlocked bootloader.
So if you are locked but still have a custom recovery, you have to unlock again so that you can flash a stock recovery. Then lock and RUU.
Also, like mughalgxt said, you can not run a RUU with an oler hboot than you have now.
Click to expand...
Click to collapse
I've tried to unlock the bootloader again but it says something is wrong with signature I don't know what it is though

milkshakes said:
I've tried to unlock the bootloader again but it says something is wrong with signature I don't know what it is though
Click to expand...
Click to collapse
Having the same problem. Was able to RELOCK but still won't flash RUU. Would really appreciate any help. Almost as much as I now appreciate a removable SD card.

i have this same problem, orginal bootloader etc boot loader relock and still nothing always finish with error checksum failed
FAILED (remote: 12 signature verify fail)
Click to expand...
Click to collapse
Any other solution
CID to H3G__001
version-baseband 1.11.50.05.28
version bootloader 2.13.0000
Regards

Chances are you're using the wrong RUU. Google one specific to Three UK.
Sent from my HTC One S using xda premium

kylepont said:
Chances are you're using the wrong RUU. Google one specific to Three UK.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
now i have error 155 it look like wrong bootloader or recovery
i change couple times recovery and boot (taken from OTA update) and still nothing
this two firmware i try :
RUU_Ville_U_H3G_UK_1.78.771.5_Radio_0.16.31501S.19_2_10.23.31501S.10L_release_258982_signed
RUU_Ville_U_H3G_UK_1.53.771.4_Radio_0.15.31501S.19_2_10.13.31501S.06L_release_251870_signed
Regards

blackangel82 said:
version-baseband 1.11.50.05.28
version bootloader 2.13.0000
Click to expand...
Click to collapse
blackangel82 said:
this two firmware i try :
RUU_Ville_U_H3G_UK_1.78.771.5_Radio_0.16.31501S.19_2_10.23.31501S.10L_release_258982_signed
RUU_Ville_U_H3G_UK_1.53.771.4_Radio_0.15.31501S.19_2_10.13.31501S.06L_release_251870_signed
Click to expand...
Click to collapse
Those RUUs are too old for you. (You can't run a RUU with an older hboot than you have.) If I remember correctly, 1.53.xx comes with hboot-1.06 and the 1.78.xx RUU has hboot-1.13
and you have hboot-2.13. If you are S-Off, you can flash an older stock hboot.
-Jobo

Having same problem. I flashed my recovery back to stock ICS recovery and relocked the bootloader. In hboot however, I still have TAMPERED at the top. Every time I try to flash back to stock RUU it fails with the message "FAILED (remote: 12 signature verify fail)". I've got a Bell Mobility One S and I'm using the BM RUU.

stoked said:
Having same problem. I flashed my recovery back to stock ICS recovery and relocked the bootloader. In hboot however, I still have TAMPERED at the top. Every time I try to flash back to stock RUU it fails with the message "FAILED (remote: 12 signature verify fail)". I've got a Bell Mobility One S and I'm using the BM RUU.
Click to expand...
Click to collapse
Use the Link in my signature.

khan.orak said:
Use the Link in my signature.
Click to expand...
Click to collapse
Thanks. I actually got my phone upgraded by reflashing the stock recovery, locking the bootloader and then running the ota update. Still not sure why I still have a tampered message in the hboot though.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

[Q] No Way back - ERROR 155

cheers!
Status of my HTC:
Now it's RELOCKED
It has the original Recovery and Super CID (11111111)
BUT:
I can't flash any Stock rom! I always get the error 155! The bad thing is, I am not able to use a custom rom because, some of the Stock rom erased my flash!
but but but! the best thing is , I can't unlock the bootloader now! With the old unlock_boot.bin I will get an error and if I want to get a new Code from HTCDEV.com I also get an Error on the side, and they say, that the code is too long or not right (but I know how to copy and paste the text )
Why I want to go back to Stock?
First of all, I had an Wlan problem, which I solved but after that, i always got the Error (with Custom Roms) that the Android Keyboard (AOSP) will be closed, so I had no keyboard to work with
What can I do?
I only want to go back to my Custom Rom or the Stock ROM!!!!!

thesoldier16 said:
cheers!
Status of my HTC:
Now it's RELOCKED
It has the original Recovery and Super CID (11111111)
BUT:
I can't flash any Stock rom! I always get the error 155! The bad thing is, I am not able to use a custom rom because, some of the Stock rom erased my flash!
but but but! the best thing is , I can't unlock the bootloader now! With the old unlock_boot.bin I will get an error and if I want to get a new Code from HTCDEV.com I also get an Error on the side, and they say, that the code is too long or not right (but I know how to copy and paste the text )
Why I want to go back to Stock?
First of all, I had an Wlan problem, which I solved but after that, i always got the Error (with Custom Roms) that the Android Keyboard (AOSP) will be closed, so I had no keyboard to work with
What can I do?
I only want to go back to my Custom Rom or the Stock ROM!!!!!
Click to expand...
Click to collapse
Well, I imagine with the RUU you got back to a stock ROM... At any rate, you could try reflashing the RUU, or attempt to flash a different RUU (since you have SuperCID) and then see if your still having issues with getting a new unlock_boot.bin.
I imagine your 100% sure you know how to cut and paste? LOL I have to ask (even though you said it)... I was able to unlock my bootloader after flashing a newer RUU and didnt have this issue.
AKToronto

Well, I imagine with the RUU you got back to a stock ROM... At any rate, you could try reflashing the RUU, or attempt to flash a different RUU (since you have SuperCID) and then see if your still having issues with getting a new unlock_boot.bin.
Click to expand...
Click to collapse
Good aspect, but (now I love this word ) I tested nearly every Europe RUU and I always get the 155!
Some people said, that one of the latest RUU works with the CID :
RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed
At tis moment I found this rom, I will test it tomorrow!
I imagine your 100% sure you know how to cut and paste? LOL I have to ask (even though you said it)... I was able to unlock my bootloader after flashing a newer RUU and didnt have this issue.
Click to expand...
Click to collapse
Come on man! I unlocked the bootloader Soooo this is not the problem for me!
I read in some threads, that you can't generate a new .bin file with htcdev when you have on working Rom on your phone haha funny, yeah and I am not able to put a normal stock rom on the phone

This is a long shot, but if you still have a custom recovery, try loading it up and flashing this: http://www.mediafire.com/?l35x37414jhwual
That package will set your mainver to the lowest possible number, which combined with SuperCID will allow flashing of any RUU.
If that doesn't work, you'll have to keep trying the htcdev to get your unlock code. It's possible that the website could be having some temporary problems. If all else fails, shoot an e-mail to HTC Support with screenshots of the errors on the website, the fastboot errors, a picture of your phone's HBOOT, your old unlock_code.bin and your identifier token.
Edit: Oops, just read that you had the original recovery :/ Yeah, try the absolute latest RUU and if that doesn't work, you'll need a new unlock code to have any progress.

what is your hboot version?

thesoldier16 said:
I only want to go back to my Custom Rom or the Stock ROM!!!!!
Click to expand...
Click to collapse
The unlock_code.bin file you get from HTC is generated using fingerprints on your phone. When you changed your CID it's like changing a fingerprint. All you have to do is go through the unlocking process again and get a NEW unlock_code.bin from HTC Dev.
thesoldier16 said:
I always get the error 155! The bad thing is, I am not able to use a custom rom because, some of the Stock rom erased my flash!
Click to expand...
Click to collapse
Most likley you are trying to use a RUU that have a lower hboot then yours. You can only use an RUU that has the same version or a higher hboot.
thesoldier16 said:
It has the original Recovery and Super CID (11111111)
I can't flash any Stock rom!
Click to expand...
Click to collapse
If you have the original recovery you need to flash a custom recovery first. Find TWRP and flash that.

what is your hboot version?
Click to expand...
Click to collapse
It's the version 1.14.0002
Ok these roms don'tt work for me:
RUU_Ville_U_H3G_UK_1.53.771.4_Radio_0.15.31501S.19_2_10.13.31501S.06L_release_251870_signed.exe -> I tried this rom with my old CID , it was H3G__106
RUU_Ville_U_HTC_Europe_1.53.401.2_Radio_0.15.31501S.19_10.12.31501S.06L_release_251412_signed.exe
RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed.exe
EDIT EDIT EDIT:
I got a new code from htcdev!
my problem was, I paste the text with the "info" . ok it was my fault, but now i have to try, to get my custom Recovery back!
One question, if I replace the SUPER CID with the HTC__001 one, can I flash the HTC Europe ones? (the 1.53 or the 1.78?)
Click to expand...
Click to collapse

thesoldier16 said:
It's the version 1.14.0002
Ok these roms don'tt work for me:
RUU_Ville_U_H3G_UK_1.53.771.4_Radio_0.15.31501S.19_2_10.13.31501S.06L_release_251870_signed.exe -> I tried this rom with my old CID , it was H3G__106
RUU_Ville_U_HTC_Europe_1.53.401.2_Radio_0.15.31501S.19_10.12.31501S.06L_release_251412_signed.exe
RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed.exe
EDIT EDIT EDIT:
I got a new code from htcdev!
my problem was, I paste the text with the "info" . ok it was my fault, but now i have to try, to get my custom Recovery back!
One question, if I replace the SUPER CID with the HTC__001 one, can I flash the HTC Europe ones? (the 1.53 or the 1.78?)
Click to expand...
Click to collapse
The problem is that you trying to use RUU's with a lower Hboot then what you got it will never work without a downgrade. Its has to be the same or higher then what you got.

Bell/Virgin HTC Sensation Boot-loop

Hello, I know this may seem like a redundant post but I cannot for the life of me figure out how to un-brick this phone..
Currently the only menu I can get into is the Hboot menu, where it says
RELOCKED
HBoot-1.27.0000
RADIO-11.24.3504.10_M
eMMc-boot
This phone has never been rooted or modified in anyway and just started this bootloop, where I've tried unlocking the bootloader, flashing different recovery's and many RUU files and nothing has worked..
When trying to enter the recovery menu from the HBoot menu it the phone simply resets itself and back to the dreaded HTC bootloop..
The phone is currently on 3.32.666.13 I believe and there is no RUU that I can use to reflash it because the latest RUU for Bell Sensations is
1.45.666.5 and it errors out saying it's the incorrect version.
I've went through many tutorials and searched through many posts trying to get s-off but there is no method that will work because I cannot get into the recovery or the android os or perform a factory reset even..
If anybody has any ideas or can shine some light onto this problem I'd greatly appreciate it

Tom-5- said:
Hello, I know this may seem like a redundant post but I cannot for the life of me figure out how to un-brick this phone..
Currently the only menu I can get into is the Hboot menu, where it says
RELOCKED
HBoot-1.27.0000
RADIO-11.24.3504.10_M
eMMc-boot
This phone has never been rooted or modified in anyway and just started this bootloop, where I've tried unlocking the bootloader, flashing different recovery's and many RUU files and nothing has worked..
When trying to enter the recovery menu from the HBoot menu it the phone simply resets itself and back to the dreaded HTC bootloop..
The phone is currently on 3.32.666.13 I believe and there is no RUU that I can use to reflash it because the latest RUU for Bell Sensations is
1.45.666.5 and it errors out saying it's the incorrect version.
I've went through many tutorials and searched through many posts trying to get s-off but there is no method that will work because I cannot get into the recovery or the android os or perform a factory reset even..
If anybody has any ideas or can shine some light onto this problem I'd greatly appreciate it
Click to expand...
Click to collapse
Hi,
To get into stock recovery,hold volume up and down + power button.

malybru said:
Hi,
To get into stock recovery,hold volume up and down + power button.
Click to expand...
Click to collapse
Hi there, thanks for the suggestion but instead of loading the recovery it just boots to the white htc screen, goes black for about second and reboots.. no matter how long or which button combination I use, besides to get into the Hboot Menu, I haven't seen any recovery menu yet

Tom-5- said:
Hi there, thanks for the suggestion but instead of loading the recovery it just boots to the white htc screen, goes black for about second and reboots.. no matter how long or which button combination I use, besides to get into the Hboot Menu, I haven't seen any recovery menu yet
Click to expand...
Click to collapse
Can you check the cid?
If it's super CID then change it back to original one and then do a reboot and see
Sent from my HTC Sensation using xda premium

ganeshp said:
Can you check the cid?
If it's super CID then change it back to original one and then do a reboot and see
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
Hello, Unfortunately the CID hasn't been changed, it's currently BM___001
Is there any RUU's available for this model equal to 3.32.666.13 or higher?

Tom-5- said:
Hello, Unfortunately the CID hasn't been changed, it's currently BM___001
Is there any RUU's available for this model equal to 3.32.666.13 or higher?
Click to expand...
Click to collapse
Hi,
Look HERE or HERE

malybru said:
Hi,
Look HERE or HERE
Click to expand...
Click to collapse
Hello, thanks for the links.
I've tried both the BM RUU's and some of the HTC Europe ones as their firmware versions are higher, but they error out with
<T192024><DEBUG><OUT>FAILED (remote: 43 main version check fail)</OUT>
or
<T003702><DEBUG><OUT>FAILED (remote: 41 model id check fail)</OUT>
(From RUU Logs)
it was my understanding I need one with 3.32.666.13 or higher retaining the same '666' region type code and a higher or equal firmware to the one already installed, as far as I'm aware no such RUU exists
I've tried taking the rom from either RUU's and flashing the zip manually with fastboot with either a locked or unlocked bootloader using commands like "fastboot -s SH16LV603891 flash zip C:\rom.zip" and it either says something like "remote:signature fail" or "Remote:not allowed" (with unlocked bootloader)

Tom-5- said:
Hello, thanks for the links.
I've tried both the BM RUU's and some of the HTC Europe ones as their firmware versions are higher, but they error out with
<T192024><DEBUG><OUT>FAILED (remote: 43 main version check fail)</OUT>
or
<T003702><DEBUG><OUT>FAILED (remote: 41 model id check fail)</OUT>
(From RUU Logs)
it was my understanding I need one with 3.32.666.13 or higher retaining the same '666' region type code and a higher or equal firmware to the one already installed, as far as I'm aware no such RUU exists
I've tried taking the rom from either RUU's and flashing the zip manually with fastboot with either a locked or unlocked bootloader using commands like "fastboot -s SH16LV603891 flash zip C:\rom.zip" and it either says something like "remote:signature fail" or "Remote:not allowed" (with unlocked bootloader)
Click to expand...
Click to collapse
Hi,
Relock the bootloader
Code:
fastboot oem lock
Then,try the RUU again.

malybru said:
Hi,
Relock the bootloader
Code:
fastboot oem lock
Then,try the RUU again.
Click to expand...
Click to collapse
Unfortunately no matter which RUU I use or whether the bootloader is locked or unlocked it errors out before it can finish
I appreciate the help though
Is is possible to get supercid without booting into the android operating system or recovery menu? so I could at least flash a custom rom or not be limited with my fastboot commands

Tom-5- said:
Unfortunately no matter which RUU I use or whether the bootloader is locked or unlocked it errors out before it can finish
I appreciate the help though
Is is possible to get supercid without booting into the android operating system or recovery menu? so I could at least flash a custom rom or not be limited with my fastboot commands
Click to expand...
Click to collapse
Hi,
I do not think you can supercid with s-on.
But you can try to follow THIS GUIDE to install a custom ROM.

malybru said:
Hi,
I do not think you can supercid with s-on.
But you can try to follow THIS GUIDE to install a custom ROM.
Click to expand...
Click to collapse
I was able to flash the recovery, but when attempting to boot into the recovery it instantly brings up the white HTC logo on the screen, and stays there until the phone eventually reboots

Tom-5- said:
I was able to flash the recovery, but when attempting to boot into the recovery it instantly brings up the white HTC logo on the screen, and stays there until the phone eventually reboots
Click to expand...
Click to collapse
Hi,
I am running out of things to suggest.
The best thing would obviously be a RUU to reset everything.
Maybe try to re-install the recovery.

malybru said:
Hi,
I am running out of things to suggest.
The best thing would obviously be a RUU to reset everything.
Maybe try to re-install the recovery.
Click to expand...
Click to collapse
It's got me stumped too! I've tried multiple recoveries.. I wonder if it's possible that it could be a hardware-related problem? As I should be able to enter the recovery at this point I think, unless I'm missing something? Would any RUU that is over higher than the current firmware be suitable? for example it currently sits at 3.32.666.13, say I were to use "RUU-Pyramid-ICS-hTC-Europe-3.33.401.53-Radio-11.76A.3504.00U-11.24A.3504.31-M-release-280871-signed" The firmware is higher but the region code doesn't match up. If I were to use "RUU_Pyramid_BM_1.45.666.5_Radio_10.56.9035.00U_10.14.9035.01_M_release_220007_signed" the firmware version is too low, but the region matches up. I figured if I used just an unbranded stock rom.zip based off of 3.32 or 3.33 and flashed it via fastboot with an unlocked/locked bootloader I may have some luck but it was a no-dice situation..
The model of this sensation is a PG58110 with a manufacture date of 2011/06/17
Could these possibly be the wrong RUU's ? I tried ones for the Sensation 4G and regular Sensation
as I wasn't positive which one I have.. No luck either way

Tom-5- said:
It's got me stumped too! I've tried multiple recoveries.. I wonder if it's possible that it could be a hardware-related problem? As I should be able to enter the recovery at this point I think, unless I'm missing something? Would any RUU that is over higher than the current firmware be suitable? for example it currently sits at 3.32.666.13, say I were to use "RUU-Pyramid-ICS-hTC-Europe-3.33.401.53-Radio-11.76A.3504.00U-11.24A.3504.31-M-release-280871-signed" The firmware is higher but the region code doesn't match up. If I were to use "RUU_Pyramid_BM_1.45.666.5_Radio_10.56.9035.00U_10.14.9035.01_M_release_220007_signed" the firmware version is too low, but the region matches up. I figured if I used just an unbranded stock rom.zip based off of 3.32 or 3.33 and flashed it via fastboot with an unlocked/locked bootloader I may have some luck but it was a no-dice situation..
The model of this sensation is a PG58110 with a manufacture date of 2011/06/17
Could these possibly be the wrong RUU's ? I tried ones for the Sensation 4G and regular Sensation
as I wasn't positive which one I have.. No luck either way
Click to expand...
Click to collapse
Hi,
Did you fully read THIS LINK that I gave you?
It shows various alternatives to just running a RUU.
It helps you to determine which of the 3 types of Sensation you have.
Try running all the RUU's that are even reasonably close to your version.
It will only throw up an error if it is no good.
Remember that the phone should be locked or relocked.

[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] Cannot flash stock/any rom

I decided to update my Dev unlocked Sensation to ICS, but had forgotten it was probably still on a Gingerbread radio. Now I have no working rom, and for some reason I am unable to flash the original rom (RUU) via the SD card method (PG58IMG).
My CID is HTC__E11 and therefor european roms from RUU should work, but I get the following error message when trying the sd card flash: wrong zipped image. In other cases it wont go further than parsing.
When i try to flash the RUU in ruu mode on the phone I get the following error: 99 unknown fail.
Unfortunately I cannot go back to the rom I was on before, since I dont have it anymore.
So the only thing I have now is TWRP recovery 2.6.3 and unlocked HBOOT 1.27.
Furthermore I am unable to see what my current radio firmware is. I want to flash a jellybean rom.
Does anyone know what to do?

MAsterokki said:
I decided to update my Dev unlocked Sensation to ICS, but had forgotten it was probably still on a Gingerbread radio. Now I have no working rom, and for some reason I am unable to flash the original rom (RUU) via the SD card method (PG58IMG).
My CID is HTC__E11 and therefor european roms from RUU should work, but I get the following error message when trying the sd card flash: wrong zipped image. In other cases it wont go further than parsing.
When i try to flash the RUU in ruu mode on the phone I get the following error: 99 unknown fail.
Unfortunately I cannot go back to the rom I was on before, since I dont have it anymore.
So the only thing I have now is TWRP recovery 2.6.3 and unlocked HBOOT 1.27.
Furthermore I am unable to see what my current radio firmware is. I want to flash a jellybean rom.
Does anyone know what to do?
Click to expand...
Click to collapse
ok would i be correct in thinking that you are s-on? how exactly did you upgrade from gingerbread to ics and have you tried formatting all partitions from twrp?

heavy_metal_man said:
ok would i be correct in thinking that you are s-on? how exactly did you upgrade from gingerbread to ics and have you tried formatting all partitions from twrp?
Click to expand...
Click to collapse
Yes I am S-ON. I did try formatting all partitions from twrp, that didnt help. I also tried cwm, but that didnt help either.
My radio was finally displayed by HBOOT, it is: 11.29A.3504.18_M. I believe this is a ICS radio, so there should be no problem here. Unfortunately i cannot find the RUU that corresponds to that radio and trying to flash another ruu wont work.
To go to ICS I just installed the latest CM11 from Sultan, which works on my other sensation (which is S-OFF). I have also tried other roms, but they all wont boot for some weird reason. For every rom I do a full wipe.

MAsterokki said:
Yes I am S-ON. I did try formatting all partitions from twrp, that didnt help. I also tried cwm, but that didnt help either.
My radio was finally displayed by HBOOT, it is: 11.29A.3504.18_M. I believe this is a ICS radio, so there should be no problem here. Unfortunately i cannot find the RUU that corresponds to that radio and trying to flash another ruu wont work.
To go to ICS I just installed the latest CM11 from Sultan, which works on my other sensation (which is S-OFF). I have also tried other roms, but they all wont boot for some weird reason. For every rom I do a full wipe.
Click to expand...
Click to collapse
If your s-on you need to flash the boot.IMG of your rom from fastboot straight after flashing your rom from recovery pal. But I recommend installing 4ext recovery and enabling its "smart flash" feature and this will do it for you try this and check back pal.
Sent from my Nexus 7 using Tapatalk

heavy_metal_man said:
If your s-on you need to flash the boot.IMG of your rom from fastboot straight after flashing your rom from recovery pal. But I recommend installing 4ext recovery and enabling its "smart flash" feature and this will do it for you try this and check back pal.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Lol I have been doing this for so long with a S-OFF device that I totally forgot about that! Thank you so much, sorry for my stupidity haha. Still weird that I cannot flash RUU though...

MAsterokki said:
Lol I have been doing this for so long with a S-OFF device that I totally forgot about that! Thank you so much, sorry for my stupidity haha. Still weird that I cannot flash RUU though...
Click to expand...
Click to collapse
Its cool pal it is, but then again ruus won't flash unless your bootloader is relocked
Sent from my Nexus 7 using Tapatalk