Database Info

[Q] Phone won't boot up normally and cannot flash RUU

Hi,
First of all, sorry if this has already been answered somewhere else but I literally spent the last 3 days gathering information on xda reading threads more of less related to my specific problem. I would appreciate any new piece of information that I could have missed.
I had a custom ROM (ARHD 7.1). I wanted to go back to stock ROM for my provider (Bell Mobility). I successfully went back to GB 2.3.4 by flashing my provider's RUU. My phone would not take OTA update to ICS (4.0.3). I changed my SuperCID back to carrier-specific and phone took OTA update. However, it didn't reboot properly. I thought that this was because I was S-OFF and unlocked. I changed to S-ON but that bricked the phone (not even powering on). I found a tool to unbrick the phone that flashes a proper HBOOT (1.17 in my case). That fixed the brick problem and I could get back to bootloader. Since then, I'm stucked with a phone that doesn't boot into the ROM and cannot get into recovery. I can get into bootloader but given that I am S-ON, I'm very limited to what I can do.
I have tried re-flashing my 1.45.666.1 RUU but it looks like some time ago (don't ask me why...), I changed my MID to PG5810000 and the RUU is expecting PG5811000 so it is not possible to use RUU. I even tried modifying the android-info.txt with my MID but then RUU failed for another reason (bad signature I think).
So, this is very confusing but if I could summarize, I would say
*Cannot boot into stock ROM (it should be GB 2.3.4 from Bell Mobility)
*Can boot in bootloader
*S-ON
*MID=PG581000 (should be PG5811000 according to my provider Bell Mobility)
*CID=BM____001 (it is the correct one for Bell Mobility)
Bootloader information
PYRAMID PVT SHIP S-ON RLo
HBOOT-1.17.0008
RADIO-10.14.9035.01_M
eMMC-boot
May 13 2011.21:04:57
Is there any thing I can do to recover? Getting S-OFF would help of course but I cannot use Revolutionary tool normally as it requires you to boot in your ROM. Maybe there are some backdoor commands that Revolutionary uses that I can call with fastboot?
My last resort is to contact HTC or Bell but I'd like to avoid this as I am out of the warranty period, which my messing around would have voided anyway. Thanks for your help.
Fred

fdavidson said:
Hi,
First of all, sorry if this has already been answered somewhere else but I literally spent the last 3 days gathering information on xda reading threads more of less related to my specific problem. I would appreciate any new piece of information that I could have missed.
I had a custom ROM (ARHD 7.1). I wanted to go back to stock ROM for my provider (Bell Mobility). I successfully went back to GB 2.3.4 by flashing my provider's RUU. My phone would not take OTA update to ICS (4.0.3). I changed my SuperCID back to carrier-specific and phone took OTA update. However, it didn't reboot properly. I thought that this was because I was S-OFF and unlocked. I changed to S-ON but that bricked the phone (not even powering on). I found a tool to unbrick the phone that flashes a proper HBOOT (1.17 in my case). That fixed the brick problem and I could get back to bootloader. Since then, I'm stucked with a phone that doesn't boot into the ROM and cannot get into recovery. I can get into bootloader but given that I am S-ON, I'm very limited to what I can do.
I have tried re-flashing my 1.45.666.1 RUU but it looks like some time ago (don't ask me why...), I changed my MID to PG5810000 and the RUU is expecting PG5811000 so it is not possible to use RUU. I even tried modifying the android-info.txt with my MID but then RUU failed for another reason (bad signature I think).
So, this is very confusing but if I could summarize, I would say
*Cannot boot into stock ROM (it should be GB 2.3.4 from Bell Mobility)
*Can boot in bootloader
*S-ON
*MID=PG581000 (should be PG5811000 according to my provider Bell Mobility)
*CID=BM____001 (it is the correct one for Bell Mobility)
Bootloader information
PYRAMID PVT SHIP S-ON RLo
HBOOT-1.17.0008
RADIO-10.14.9035.01_M
eMMC-boot
May 13 2011.21:04:57
Is there any thing I can do to recover? Getting S-OFF would help of course but I cannot use Revolutionary tool normally as it requires you to boot in your ROM. Maybe there are some backdoor commands that Revolutionary uses that I can call with fastboot?
My last resort is to contact HTC or Bell but I'd like to avoid this as I am out of the warranty period, which my messing around would have voided anyway. Thanks for your help.
Fred
Click to expand...
Click to collapse
you sure the RUU you are using is correct ?
if so then best solution is to try revolutionary
try the tool with phone connected in fastboot ...it might work (i remember one guy doing that )

ganeshp said:
you sure the RUU you are using is correct ?
if so then best solution is to try revolutionary
try the tool with phone connected in fastboot ...it might work (i remember one guy doing that )
Click to expand...
Click to collapse
Thanks ganeshp for the quick answer. I am pretty confident about the RUU as it is the same one I originally ran to move from custom ICS ROM to stock 2.3.4 ROM.
For Revolutionary, even in fastboot, it is stuck in "Waiting for devices..." I think it is because it issues "adb devices" command and expects some answer before carrying on to the bootloader. I would need it to skip this step. Are there any argument to revolutionary to do that?
Fred

A little more update on RUU failure. If I change the modelid in android-info.txt, this means that I have to re-package the files back into ROM.zip. I am doing this with WinZip. Even without editing any file, just extracting the files from original ROM.zip from RUU back to another version of ROM.zip (no change), I noticed that file size is not the same. Maybe that explain with the signature check fails when flashing RUU. Now, I don't know what to use to re-package files into a ROM.zip archive to use RUU.
Fred

fdavidson said:
A little more update on RUU failure. If I change the modelid in android-info.txt, this means that I have to re-package the files back into ROM.zip. I am doing this with WinZip. Even without editing any file, just extracting the files from original ROM.zip from RUU back to another version of ROM.zip (no change), I noticed that file size is not the same. Maybe that explain with the signature check fails when flashing RUU. Now, I don't know what to use to re-package files into a ROM.zip archive to use RUU.
Fred
Click to expand...
Click to collapse
Short answer - you cannot touch or do anything to ROM.zip if you want to use RUU, changing anything changes MD5 sum hence the signature error.
What you should do is run an ICS RUU compatible with your MID

Jonny said:
Short answer - you cannot touch or do anything to ROM.zip if you want to use RUU, changing anything changes MD5 sum hence the signature error.
What you should do is run an ICS RUU compatible with your MID
Click to expand...
Click to collapse
Thanks Jonny, that is good information. My problem with this is that I have a provider-specific CID (BM_0001) and not superCID. If I can find an ICS RUU for my MID (the one wrongly change for my device, i.e. PG5810000), would the CID affect anything?
Fred

fdavidson said:
Thanks Jonny, that is good information. My problem with this is that I have a provider-specific CID (BM_0001) and not superCID. If I can find an ICS RUU for my MID (the one wrongly chance for my device, i.e. PG5810000), would the CID affect anything?
Fred
Click to expand...
Click to collapse
Mate MID/CID are checked prior to flashing rom, so if the MID/CID are not "correct" installation will not take place

dublinz said:
Mate MID/CID are checked prior to flashing rom, so if the MID/CID are not "correct" installation will not take place
Click to expand...
Click to collapse
Thanks everyone for taking some of your time to help me. From the information that I've received, it looks that I will not be able to recover my phone, That's bad because I thought I was just a few steps away, maybe by being able to flash an unlocked S-OFF H-Boot 1.17 and by some way tweak RUU so that it would work. I'll wait one or two days in case someone suggests something different and then see if HTC can help. It will be interesting (or embarassing) to hear what they have to say.
Cheers,
Fred

fdavidson said:
Thanks everyone for taking some of your time to help me. From the information that I've received, it looks that I will not be able to recover my phone, That's bad because I thought I was just a few steps away, maybe by being able to flash an unlocked S-OFF H-Boot 1.17 and by some way tweak RUU so that it would work. I'll wait one or two days in case someone suggests something different and then see if HTC can help. It will be interesting (or embarassing) to hear what they have to say.
Cheers,
Fred
Click to expand...
Click to collapse
Change back the android-info.txt and run the ruu again.. From phone connected in fastboot.. And let me know what error it showed
Edit: or simply run the ruu you have.. With phone connected to pc in bootloader/fastboot
Sent from my HTC Sensation 4G using xda premium

ganeshp said:
Change back the android-info.txt and run the ruu again.. From phone connected in fastboot.. And let me know what error it showed
Edit: or simply run the ruu you have.. With phone connected to pc in bootloader/fastboot
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
ganeshp,
Without modifying android-info.txt (just running the RUU_Pyramid_BM_1.45.666.5_Radio_10.56.9035.00U_10.14.9035.01_M_release_220007_signed.exe), I am getting "ERROR [130]: MODEL ID ERROR. This is expected as my MID (modelID is incorrect. My phone is at PG5810000 when RUU expects PG5811000).
When I modify the android-info.txt in ROM.zip to have my correct MID, it goes a little bit further down the process. However, I am getting "ERROR [132]: SIGNATURE ERROR". Below is the related content of ruu_log.txt:
<T084503><DEBUG><CMD>fastboot -s SH16KV601188 flash zip "C:\Documents and Settings\fred\Local Settings\Temp\{A20F8D10-D7EB-4B01-91D2-68167E319F81}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip"</CMD>
</DEBUG></T084503>
<T084609><DEBUG><OUT>sending 'zip' (416943 KB)... OKAY</OUT>
</DEBUG></T084609>
<T084609><DEBUG><OUT>writing 'zip'... INFOsignature checking...</OUT>
</DEBUG></T084609>
<T084722><DEBUG><OUT>FAILED (remote: 12 signature verify fail)</OUT>
</DEBUG></T084722>
This is also expected as someone already pointed out earlier in this thread that ROM.zip cannot be modified because of different MD5 checksum. On this point, I am wondering if there would be some tool to re-generate a correct MD5 checksum.
Fred

fdavidson said:
ganeshp,
Without modifying android-info.txt (just running the RUU_Pyramid_BM_1.45.666.5_Radio_10.56.9035.00U_10.14.9035.01_M_release_220007_signed.exe), I am getting "ERROR [130]: MODEL ID ERROR. This is expected as my MID (modelID is incorrect. My phone is at PG5810000 when RUU expects PG5811000).
When I modify the android-info.txt in ROM.zip to have my correct MID, it goes a little bit further down the process. However, I am getting "ERROR [132]: SIGNATURE ERROR". Below is the related content of ruu_log.txt:
<T084503><DEBUG><CMD>fastboot -s SH16KV601188 flash zip "C:\Documents and Settings\fred\Local Settings\Temp\{A20F8D10-D7EB-4B01-91D2-68167E319F81}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip"</CMD>
</DEBUG></T084503>
<T084609><DEBUG><OUT>sending 'zip' (416943 KB)... OKAY</OUT>
</DEBUG></T084609>
<T084609><DEBUG><OUT>writing 'zip'... INFOsignature checking...</OUT>
</DEBUG></T084609>
<T084722><DEBUG><OUT>FAILED (remote: 12 signature verify fail)</OUT>
</DEBUG></T084722>
This is also expected as someone already pointed out earlier in this thread that ROM.zip cannot be modified because of different MD5 checksum. On this point, I am wondering if there would be some tool to re-generate a correct MD5 checksum.
Fred
Click to expand...
Click to collapse
ok RUU way is closed for you then
now if you can unlock your bootloader ..things can be better for you
try HTC-DEV unlock ...once done ..you need to flash a custom GB rom from recovery

ganeshp said:
ok RUU way is closed for you then
now if you can unlock your bootloader ..things can be better for you
try HTC-DEV unlock ...once done ..you need to flash a custom GB rom from recovery
Click to expand...
Click to collapse
I'm getting stuck at step 8 of HTC-Dev unlock. When I issue the command "fastboot oem get_identifier_token", I get back "INFO[ERR] Command error !!!". Maybe this oem command doesn't work with my bootloader (1.17.0008).
Fred

fdavidson said:
I'm getting stuck at step 8 of HTC-Dev unlock. When I issue the command "fastboot oem get_identifier_token", I get back "INFO[ERR] Command error !!!". Maybe this oem command doesn't work with my bootloader (1.17.0008).
Fred
Click to expand...
Click to collapse
no man with that hboot version you don't need htc dev unlock.use this site to S-OFF your device
http://revolutionary.io/
edit: i just read your first post
so you can not use revolutionary

fdavidson said:
I'm getting stuck at step 8 of HTC-Dev unlock. When I issue the command "fastboot oem get_identifier_token", I get back "INFO[ERR] Command error !!!". Maybe this oem command doesn't work with my bootloader (1.17.0008).
Fred
Click to expand...
Click to collapse
ahh even that got stuck huh ...try revolutionary again ..with phone boot-looping or when stuck at splash screen ..if revolutionary finds the device all good ..otherwise all doors closed
rzr86 said:
no man with that hboot version you don't need htc dev unlock.use this site to S-OFF your device
http://revolutionary.io/
Click to expand...
Click to collapse
he tried revolutionary already ..and he currently didnt have a booting rom ..so it might not work

rzr86 said:
no man with that hboot version you don't need htc dev unlock.use this site to S-OFF your device
http://revolutionary.io/
Click to expand...
Click to collapse
That was my original attempt but it looks like revolutionary expects the phone to be fully booted so it can set it himself in bootloader/fastboot through adb command. Since I can get into fastboot myself, If I could skip that part from revolutionary and have it do the next steps, I think I'd get a successful S-OFF. Any idea on how to do that?
Fred

wait if revolutionary wants a working adb then we will give it an adb
do this
get the recovery.img from this link (extract it)
copy it to fastboot
and try this command
fastboot boot recovery.img
if it booted ..then run revolutionary

ganeshp said:
wait if revolutionary wants a working adb then we will give it an adb
do this
get the recovery.img from this link (extract it)
copy it to fastboot
and try this command
fastboot boot recovery.img
if it booted ..then run revolutionary
Click to expand...
Click to collapse
I am getting:
downloading 'boot.img'... OKAY [ 1.706s]
booting... FAILED (remote: not allowed)
Is it because I am S-ON? I seem to remember that S-ON will not allow me to write to some partitions. I hope I'm wrong.

fdavidson said:
I am getting:
downloading 'boot.img'... OKAY [ 1.706s]
booting... FAILED (remote: not allowed)
Is it because I am S-ON? I seem to remember that S-ON will not allow me to write to some partitions. I hope I'm wrong.
Click to expand...
Click to collapse
we are not writing but we are trying to read ..
but is the command you typed is
fastboot boot recovery.img ? (coz in the output its saying downloading boot.img )

ganeshp said:
we are not writing but we are trying to read ..
but is the command you typed is
fastboot boot recovery.img ? (coz in the output its saying downloading boot.img )
Click to expand...
Click to collapse
Yes, my mistake. I sent the same command (fastboot boot recovery.img), so the problem is with reading as you said.

fdavidson said:
Yes, my mistake. I sent the same command (fastboot boot recovery.img), so the problem is with reading as you said.
Click to expand...
Click to collapse
then im out of ideas
one last try
try changing cid
fastboot oem writecid HTC__001
then
fastboot reboot-bootloader
then verify it
fastboot getvar cid
EDIT: if this worked then ..immediately flash the european unbranded 3.33 rom

[Guide] [UPDATED07.04.2013] unbranding HTC ONE S S4

UNBRAND HTC ONE S THE RIGHT WAY​
I am not responsible for anything that goes wrong which messes up your device !
Things needed
1. HTC ONE S S4 variant
2. Common Sense and patience
Steps :-
1.Relock your bootloader using "fastboot oem lock"
2. RUU your device , for RUU files use this http://www.androidfiles.org/ruu/?dir=Ville
3. Unlock your bootloader via htcdev.com
4. Flash TWRP recovery by "fastboot flash recovery TWRPS4.img "
5. Flash any custom rom you want like viperones or trickdroid or cm anyone your preference
S-off your device using facepalm s-off http://forum.xda-developers.com/showthread.php?t=2155135
Once you have s-off issue this command to change your cid WWE EUROPE
"fastboot oem writecid HTC__001"
issue "fastboot reboot-bootloader"
then use "fastboot getvar all" to check if your and cid have changed to HTC__001
Download this Jellybean RUU and flash it , its already edited , so no mid problem
To flash it
Fastboot oem rebootRUU
Fastboot flash zip JB316_WWE_ville_decrypt_rom.zip
http://dl.dropbox.com/u/55211431/JB316_WWE_ville_decrypt_rom.zip (credits jamus28) go hit his thanks button
Feel free to ask any question here:good:

What is the point of locking the phone and then unlocking it again to S-Off? Why not just S-Off then lock the bootloader and then run the JB RUU.

Re: [Guide] unbranding HTC ONE S S4
To let the phone be fully stable on stock firmware
Sent from my HTC One S using xda app-developers app

aditya. said:
To let the phone be fully stable on stock firmware
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Waste of time as long as the rom is working you only need to S-Off and then flash the RUU. I know it been updated but at the time I had to use a RUU to get my phone working again and went to S-Off and couldn't in till I flashed Viper2.

Re: [Guide] unbranding HTC ONE S S4
I had a bad time soffing my device 3 days ! Brick jtag repair etc but now I can deal with s off ing any one s
Sent from my HTC One S using xda app-developers app

i was able to change cid but i keep getting error when changing model id, please help!

cyriantherockstar said:
i was able to change cid but i keep getting error when changing model id, please help!
Click to expand...
Click to collapse
try flashing Jellybean RUU directly without changing MID ! it will work ! Sorry that command is Invalid you can proceed anyway dont worry mybad

Re: [Guide] unbranding HTC ONE S S4
Any recommendations to get rid of the silver metallic "T-Mobile" branding above the screen?
Regards,
Opentang

Re: [Guide] unbranding HTC ONE S S4
Opentang said:
Any recommendations to get rid of the silver metallic "T-Mobile" branding above the screen?
Regards,
Opentang
Click to expand...
Click to collapse
Change your LCD screen ! It will cost around 120$ ! Or look for a dead HTC one s on eBay take off Its LCD ...
Sent from my HTC One S using xda app-developers app

aditya. said:
UNBRAND HTC ONE S THE RIGHT WAY​
I am not responsible for anything that goes wrong which messes up your device !
Things needed
1. HTC ONE S S4 variant
2. Common Sense and patience
Steps :-
1.Relock your bootloader using "fastboot oem lock"
2. RUU your device , for RUU files use this http://www.androidfiles.org/ruu/?dir=Ville
3. Unlock your bootloader via htcdev.com
4. Flash TWRP recovery by "fastboot flash recovery TWRPS4.img "
5. Flash Superuser to root your device !
S-off your device using facepalm s-off http://forum.xda-developers.com/showthread.php?t=2155135
Once you have s-off these two commands to change your cid and mid to WWE EUROPE
"fastboot oem writecid HTC__001"
issue "fastboot reboot-bootloader"
then use "fastboot getvar all" to check if your and cid have changed to HTC__001
Then flash JELLYBEAN RUU - http://www.shipped-roms.com/download.php?category=android&model=Ville&file=RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe
You are unbranded !
Feel free to ask any question here:good:
Click to expand...
Click to collapse
hmmm....i didnt know that the htc one s got s-off (been busy with work lately).....i tried debranding before , using a method that doesnt involve s-off, i was able to change the CID but i could never install the RUU cause of the different MID.....is the different MID not a problem anymore ? also will you be able to get OTA updates after you debrand and flash stock Jelly Bean ROM

tried installing the JB RUU over my stock 2.31 ICS, but i get an unknown error ..im s-off already and changed cid to HTC__001, and i get the system notification for the JB OTA..is it safe to just install the OTA? coz i've read in another thread that some devices got bricked by installing the OTA (although they are using supercid when they upgraded..

anand_s said:
hmmm....i didnt know that the htc one s got s-off (been busy with work lately).....i tried debranding before , using a method that doesnt involve s-off, i was able to change the CID but i could never install the RUU cause of the different MID.....is the different MID not a problem anymore ? also will you be able to get OTA updates after you debrand and flash stock Jelly Bean ROM
Click to expand...
Click to collapse
After s-off the CID changing is easy and S-off disables signature checking so you can extract the rom.zip(ruu) and edit the android-info and change the mid in that text file save it and then add it to some.zip and flash it as RUU , it will work ! But remember you will need s-off, and you will get OTAs , Donot relock the bootloader ! the bootloader should be saying S-off and unlocked .

cyriantherockstar said:
tried installing the JB RUU over my stock 2.31 ICS, but i get an unknown error ..im s-off already and changed cid to HTC__001, and i get the system notification for the JB OTA..is it safe to just install the OTA? coz i've read in another thread that some devices got bricked by installing the OTA (although they are using supercid when they upgraded..
Click to expand...
Click to collapse
I recommend installing the RUU over the OTA , I have not tried the ota as my device was bricked by it earlier , the day i got it back from JTAG Repair I s-offed it and changed CID to htc__001 and flashed JB RUU it went smooth !
what error do you get ?

i get the image error

Re: [Guide] unbranding HTC ONE S S4
cyriantherockstar said:
i get the image error
Click to expand...
Click to collapse
Flash the Rom.zip from the ruu via fastboot flash zip Rom.zip after rebooting into ruu mode by fastboot oem rebootRUU , then post the exact error ! Try the 2.31 ruu if it works then just after the 2.31 ruu run the jb ruu
Sent from my HTC One S using xda app-developers app

i also tried to extract the rom.zip from the jb ruu, but i cant open it, winrar is saying it's corrupt so i cant edit the android-info

cyriantherockstar said:
i also tried to extract the rom.zip from the jb ruu, but i cant open it, winrar is saying it's corrupt so i cant edit the android-info
Click to expand...
Click to collapse
Its encrypted !

aditya. said:
UNBRAND HTC ONE S THE RIGHT WAY​
Then Download this JELLYBEAN RUU -
Extract it and then edit the android-info (edit the model id to PJ401100) then flash it !
Click to expand...
Click to collapse
Extract the .exe file on my pc? I don't see android-info in the files inside it, what should I be looking for and what should I edit it with?
Or do you mean install it onto the phone and then change something?

Re: [Guide] unbranding HTC ONE S S4
Hey can I ask if it is working for one s s3 variants? Because I really need to s-off
Sent from my HTC One S using xda app-developers app

Re: [Guide] unbranding HTC ONE S S4
dieseldane86 said:
Extract the .exe file on my pc? I don't see android-info in the files inside it, what should I be looking for and what should I edit it with?
Or do you mean install it onto the phone and then change something?
Click to expand...
Click to collapse
When you run the .exe file in the temporary folder you will see a file Rom.zip that's it copy and paste that to some location and inside that there is the android-info
Sent from my HTC One S using xda app-developers app

[HOWTO] [HTC One SV] Unbrand your phone to get the OTA updates

Bonjour everyone, here's a little guide on how to unbrand your phone in order to get the OTA updates notifications directly and be able to install them.
If you want to get S-OFF one day on your One SV, read this first. You need to change CID to SuperCID to do so, and it's not possible (for the moment) if you upgrade to JB
Basically this works as long as your phone model is sold unbranded somewhere in the world and that the people having such a phone got an OTA update.
For now, ther's no way to change CID if you're running JB and are S-ON. That means that this only work for One SV's running ICS who want to get the OTA updates.
As far as I know, it works on K2_U and K2_UL, since they both got an OTA update to JB.
The trick is simple, I didn't invent it and haven't been able to find its original founder, but thanks a lot to her or him !
I'm basically just a messenger here since I only tried out some stuff that worked with other phones, so thanks a lot to bkcokota, old.splatterhand and jmztaylor
Don't try it if you're worried, bricks happen, you'd be the only one responsible !
Here we go :
1. First you need to root your phone, here's how.
2. Change you CID using the same method than for the One S.
Personnaly, I changed it to "HTC__203", which is the CID unbranded HTC phones have in France (HTC-FRA).
For example, "HTC__001" is HTC-WWE, which stands for World Wide English.
You can change it to whatever CID you like : choose it well. I can only recommend to use HTC__203 since it's the only one I tried and that it worked, but do as you please !
3. Flash stock recovery back. You'll find it here or here. Flash it like you flashed CWM recovery (into fastboot, using fastboot flash recovery xxxxxx.img).
4. Relock your bootloader. It's possible that it's not necessary, but it can't hurt ("fastboot oem lock", when in fastboot usb)
5. Run a RUU that matches you unbranded CID to get an "unbranded" rom.
You'll find them here, for example. The "RUU_K2_UL_ICS_40_HTC_Europe_1.17.401.5_R....exe" one will work with HTC__203 and HTC__001 CIDs.
6. Go ask your phone if he can find any updates
WARNING : for the moment there's no way to change CID if you upgrade to JB since the newer HBOOT (v2.00) don't let you do it. That means that for now you won't be able to S-OFF if you upgrate to JB using this method. For now...

Nice one!
Only thing i would add for people to know:
if somebody want to get S-Off, they should change the CID to SuperCID 11111111 (or if you want 22222222,...).

old.splatterhand said:
Nice one!
Only thing i would add for people to know:
if somebody want to get S-Off, they should change the CID to SuperCID 11111111 (or if you want 22222222,...).
Click to expand...
Click to collapse
Done, sir.
It was only said at the bottom of the message at first, but now I put it at the beginning as well.
There's one thing that I'm trying to get though : according to a lot of people and forums, you don't get OTA when you have SuperCID... but some poeple say they do.
It probably changes depending on the type of HTC phone, but also depending on the OTA (some got the first ones, but not the latest...).

I got the ota notification with SuperCID, i think it depends on more things.
But there i'm not far enough into it.

I have had no success at all. My story:
Updated a branded phone to JB, rooted. Then I did a moonshine S-off and changed CID to HTC__001 (even tried 11111111).
I have downloaded a ICS RUU (couldn't find stock K2_UL so I thought that I would download ICS first and then do OTA to JB) but I am getting error 158. I have checked md5 sum and it matches (http://androidfiles.org/ruu/getdown...0.14_2_10.49.40.11L_release_301902_signed.exe). Any ideas?

If you're on jb and hboot 2.00, that's normal... and written in the first post.

There is information that it is impossible to change CID while on JB and with 2.0 hboot, but I guess that I have had success in changing to superCID (at least this is what I can read in bootloader and using fastboot oem readcid command.
So, as far as I understand newer hboot won't let me use older RUU as well, right?

Is there any chance to make this for the k2cl ( boost mobile ) version?

idr666 said:
Is there any chance to make this for the k2cl ( boost mobile ) version?
Click to expand...
Click to collapse
Can you be more specific, what you mean with "this".

old.splatterhand said:
Can you be more specific, what you mean with "this".
Click to expand...
Click to collapse
Sorry, I was wondering if there is a way to update this phone ( the k2cl ) to JB

idr666 said:
Sorry, I was wondering if there is a way to update this phone ( the k2cl ) to JB
Click to expand...
Click to collapse
Boost has no official jb, but i know that there is work for an custom jb rom for boost.

Oh, thank you for the info. Is there any link about this work in progress?

idr666 said:
Oh, thank you for the info. Is there any link about this work in progress?
Click to expand...
Click to collapse
Look here

szympro said:
There is information that it is impossible to change CID while on JB and with 2.0 hboot, but I guess that I have had success in changing to superCID (at least this is what I can read in bootloader and using fastboot oem readcid command.
So, as far as I understand newer hboot won't let me use older RUU as well, right?
Click to expand...
Click to collapse
old.splatterhand, you seem to know this and that about One SV. No chance for older RUU, right? I can't seem to find a clean WWE JB OTA update. I just want a clean, stock, not modified ROM from HTC and I thought RUU is the only way to go :crying: Any advices?

szympro said:
There is information that it is impossible to change CID while on JB and with 2.0 hboot,...
Click to expand...
Click to collapse
This was before moonshine was available. With S-Off i think it should be possible.
So, as far as I understand newer hboot won't let me use older RUU as well, right?
Click to expand...
Click to collapse
I think so.
szympro said:
old.splatterhand, you seem to know this and that about One SV. No chance for older RUU, right? I can't seem to find a clean WWE JB OTA update. I just want a clean, stock, not modified ROM from HTC and I thought RUU is the only way to go :crying: Any advices?
Click to expand...
Click to collapse
To get it a bit clearer.
At this point i'm not very up to date, thats why i didn't answer til now.
I think (but i'm not sure) you can flash the ruu, if you are on hboot 1.0.
And as you are S-Off you should be able to downgrade hboot. But this is a very risky point, you can easily brick your device. Here is, how you have to do:
rollon76 said:
To change hboot you will need a PL80IMG.zip on sdcard with android-info.txt and hboot.img inside it.
reboot to bootloader and flash.
Click to expand...
Click to collapse
The thing what makes it difficult, is to get the hboot.img (its inside ics ruu), cause the htc ruu's encrypted and i only have heard about tools for linux which can decrypt it.

Thanks to your reply I did some research and I have managed to do what I wanted. I have downgraded hboot first (by extracting and encrypting ICS RUU using linux), then I could run RUU and now I am stock ICS with S-off and superCID
Should I post some files from RUU? 1.0 hboot or stock recovery? You guys need something?
Thanks for your helping hand old.splatterhand!

szympro said:
Thanks to your reply I did some research and I have managed to do what I wanted. I have downgraded hboot first (by extracting and encrypting ICS RUU using linux), then I could run RUU and now I am stock ICS with S-off and superCID
Should I post some files from RUU? 1.0 hboot or stock recovery? You guys need something?
Thanks for your helping hand old.splatterhand!
Click to expand...
Click to collapse
Glad, it worked for you.
Yes, of course, everything is appreciated! You can use this thread, please post ruu name too. You can look at my posts there. Hboot, boot.img, recovery, radio, would be fine.

HERE have other ruu
https://www.dropbox.com/sh/1t2zswod7tc97az/5hbzEgTv80

szympro said:
I have downgraded hboot first (by extracting and encrypting ICS RUU using linux)
Click to expand...
Click to collapse
Wow, that's cool !
Did you use rollon's method and flashed PL80IMG.zip in bootloader mode ?
If yes, which android-info.txt did you use ?
If not, how did you do it ?
szympro said:
then I could run RUU and now I am stock ICS with S-off and superCID
Click to expand...
Click to collapse
Even cooler for you.
Did you get the ota update notification for JB then ?
Did you manage to apply it ?
Thanks and congratulations !

Hi everyone.
Just a quick message to confirm that rollon's method works.
To downgrade you need to be S-OFF, extract and decrypt (with ruuveal, using linux or a linux virtualbox runned in windows) hboot and androidinfo from ICS RUU, put them in a zip named PL80IMG.zip, put it on your sd card and boot into bootloader. Then you can run the ICS RUU normally and you'll be back to stock ICS, with a "*** LOCKED ***" bootloader (not relocked !), will be able to go back to S-ON using "fastboot oem writesecureflag 3" (thanks to JMZ)...
You'll then have a locked S-ON out of box phone running 100% stock ICS with original boot, recovery and all that... who'll get the 2 JB OTA's...
In case anyone's interested

Please Help Me Not Brick My One S

Basically I deleted everything off my One S (System OS,Backups,My Data) So I need to run a RUU to get my phone back to stock
------------------------------
**** TAMPERED ****
**** UNLOCKED ****
VLE PVT SHIP S-ON RL
Hboot-2.13.0000
Radio-1.11.50.05.28
Open DSP-v31.1.0.45.0815
eMMC-boot
Nov 20 2012 , 15:44:03,-1
------------------------------
There is not compatible RUU for my one s so heres the steps I'm going to do ....
1) SuperCID My Phone Using This Tutorial
http://androidforums.com/one-s-all-things-root/690970-guide-supercid.html
2) Then Proceed With S-OFF using this tutorial
http://m.youtube.com/watch?v=fTp5uwURKdg
3) Relock Bootloader Using Hasoon2000's All in one toolkit and flash stock recovery (I Need Stock Recovery Image For Htc one s S4 Processor) I Will use this tutorial for steps 3/4
http://m.youtube.com/watch?v=SZuAjz4PIjU
4) Run The RUU (will I be unbranded if I SuperCID and S OFF my phone so I can run. A unbranded RUU ?)
I Also Need A RUU Which Is On JellyBean Not ICS
5)Unlock Bootloader and Root
Please can ou Anwser These Questions Please <3
ill I be unbranded if I SuperCID and S OFF my phone so I can run. A unbranded RUU ? I am currently branded to three uk
And can someone link me to stock recovery Image for htc one s S4 Processor
Is There Any JellyBean RUU if So Please Link me to them and tell me if I can use them after I have done SuperCID and s off
And let me know if there any problems in my method I am going to use
Thanks One S Community

Do the steps 1 & 2 just as you mentioned.
Then, once you're s-off, you don't need to relock your bootloader. But you need to flash stock recovery before you flash any RUU. You can download it here, and flash it in fastboot mode ('fastboot flash recovery ville_recovery_signed.img').
Being s-off you can easily change to any CID by typing 'fastboot oem writecid xxxxxxxx'. You'll find CIDs in this thread, also keep in mind that using SCID might brick your phone in case of an OTA coming in. But it's easy to change...
Then choose any RUU which is closest to what you need and run it from your desktop/laptop or click me for latest EU RUU.
As you're already rooted, there is no need for step 5. You'll still be s-off and unlocked afterwards.
You should be good to go then.

rootrider said:
Do the steps 1 & 2 just as you mentioned.
Then, once you're s-off, you don't need to relock your bootloader. But you need to flash stock recovery before you flash any RUU. You can download it here, and flash it in fastboot mode ('fastboot flash recovery ville_recovery_signed.img').
Being s-off you can easily change to any CID by typing 'fastboot oem writecid xxxxxxxx'. You'll find CIDs in this thread, also keep in mind that using SCID might brick your phone in case of an OTA coming in. But it's easy to change...
Then choose any RUU which is closest to what you need and run it from your desktop/laptop or click me for latest EU RUU.
As you're already rooted, there is no need for step 5. You'll still be s-off and unlocked afterwards.
You should be good to go then.
Click to expand...
Click to collapse
What should I change my CID to and will I be unbranded ? And can I use the ruu you provided the latest one .and I don't understand what you mean with the OTA Updates. I'm branded to three UK and for 8. Change T-MOB010 to 11111111 and save the file as mmcblk0p4MOD. Would I just find H3G and change it to 11111111

You don't need stock recovery to run an ruu, all you need is a locked bootloader
Sent from my HTC One S using xda app-developers app

Ok then. Just to make shure, you're on an S4 device?
Three UK means you're just around the corner... United Kingdom.
So everything 'EU' will be good for you and you should choose HTC__001 then (HTC Europe). If this works, you'll be unbranded.
If you're s-off you basically can flash any RUU you want, even the most exotic one (if there is any :laugh. And to get the point 'any' means older ones as well, e.g. ICS based ones. Being on HTC__001 or 11111111 with ICS on the other hand means that your device will find an Over The Air update to JB. If you choose to install it, it will install JB without problems on HTC__001 but a possible lot of trouble being on 11111111. As a result you might brick your phone, according to some posts here on XDA. So you should choose HTC__001 (8 digits).
At this point keep in mind, never ever use the latest TMO US JB RUU, as this may install write protection to mmcblk0p4 on one s phones!!! (Maybe not if you're already s-off, idk at this point...)
And yes, you can use the one RUU I linked to in my previous post. It worked here, why should it not work on other phones?
---------- Post added at 11:06 AM ---------- Previous post was at 11:05 AM ----------
k1llacanon said:
You don't need stock recovery to run an ruu, all you need is a locked bootloader
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Crap - it's way easier to flash stock recovery than changing cid and unlocking/relocking bootloader. And it works.

I'm going to run the ruu you provided me with will I have any problems with that and what should I change my CID To? Also I'm going to flash stock recovery and lock bootloader so there no probs

rootrider said:
Ok then. Just to make shure, you're on an S4 device?
Three UK means you're just around the corner... United Kingdom.
So everything 'EU' will be good for you and you should choose HTC__001 then (HTC Europe). If this works, you'll be unbranded.
If you're s-off you basically can flash any RUU you want, even the most exotic one (if there is any :laugh. And to get the point 'any' means older ones as well, e.g. ICS based ones. Being on HTC__001 or 11111111 with ICS on the other hand means that your device will find an Over The Air update to JB. If you choose to install it, it will install JB without problems on HTC__001 but a possible lot of trouble being on 11111111. As a result you might brick your phone, according to some posts here on XDA. So you should choose HTC__001 (8 digits).
At this point keep in mind, never ever use the latest TMO US JB RUU, as this may install write protection to mmcblk0p4 on one s phones!!! (Maybe not if you're already s-off, idk at this point...)
And yes, you can use the one RUU I linked to in my previous post. It worked here, why should it not work on other phones?
---------- Post added at 11:06 AM ---------- Previous post was at 11:05 AM ----------
Crap - it's way easier to flash stock recovery than changing cid and unlocking/relocking bootloader. And it works.
Click to expand...
Click to collapse
Sorry for being a pain it's just I don't want to brick my phone and could you explain this as I don't understand it
view plaincopy to clipboardprint?
adb pull /sdcard/mmcblk0p4
and hit enter.
NOTE THE SIZE OF THE FILE BEFORE THE NEXT STEP!
6. Open the file (mmcblk0p4) with your hex editor.
7. Look for offset 00000210 or 00000214 and you should see "T-MOB010" with your IMEI number after it.
NOTE: "T-MOB010" is the T-Mobile US version, depending on your carrier this will change, but it will still precede your IMEI. See the link at the end of this post for a list of other CID's.
MAKE SURE AT THIS POINT THAT THE FILE IS THE EXACT SIZE IT WAS BEFORE YOU HEX EDITED IT!
9. Now go back to your command prompt and type
view plaincopy to clipboardprint?
adb push mmcblk0p4MOD /sdcard/mmcblk0p4MOD
Shall I note the file size so if it. Example.txt(4642kb). I would note the file size and I would just change my CID to HTC__001 ?
And don't I need to get the fast boot files and softbin3 and stuff but the site doesn't provide me with anything could you link me to them ? I have literally no clue
And in HxD. editor will mine look like this http://dl.xda-developers.com/attach...3a77c716b8/51864687/1/0/8/2/7/9/0/hexedit.jpg
Wouldn't I change my CID To H3G__001 but I want to be unbranded

For s off, you need super cid 11111111
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | Bulletproof_1.3

ryanshew said:
For s off, you need super cid 11111111
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | Bulletproof_1.3
Click to expand...
Click to collapse
should i do
SUPERCID :111111
CHANGE CID :HTC__001
I want to make sure the possiblity of me bricking my phone is extremely low rootrider said change it to HTC__001
btw im a noob at this stuff so i kin off need it simple

Zaman-The-Man said:
should i do
SUPERCID :111111
CHANGE CID :HTC__001
I want to make sure the possiblity of me bricking my phone is extremely low rootrider said change it to HTC__001
btw im a noob at this stuff so i kin off need it simple
Click to expand...
Click to collapse
Hi,
In the order listed, these are the following steps you must do: (this guide assumes you have the HTC drivers installed and a working folder with adb and fastboot files. if you need them, ask)
1. SuperCID. (using the previous link you mentioned, or this link)
2. S-OFF (using the previous link you mentioned, or this link)
3. Get a stock recovery. I have provided one from the Jelly Bean RUU, download it here. MD5 Sum: ed56807cb765ada1d49e7e6e246aea63
Place it in your working folder (the place where adb and fastboot etc. files are).
4. Flash the stock recovery using the command:
Code:
fastboot flash recovery recovery.img
5. Change your cid to HTC__001, using the command:
Code:
fastboot oem writecid HTC__001
You have to be in FASTBOOT USB mode in the bootloader for the command to work.
5. Run a Jelly Bean 3.16 RUU from here:
http://androidfiles.org/ruu/securek...28_10.27.50.08L_release_301814_signed_2_4.exe
6. Done!
Hope it helps

usaff22 said:
Hi,
In the order listed, these are the following steps you must do: (this guide assumes you have the HTC drivers installed and a working folder with adb and fastboot files. if you need them, ask)
1. SuperCID. (using the previous link you mentioned, or this link)
2. S-OFF (using the previous link you mentioned, or
3. Get a stock recovery. I have provided one from the Jelly Bean RUU, download it here. MD5 Sum: ed56807cb765ada1d49e7e6e246aea63
Place it in your working folder (the place where adb and fastboot etc. files are).
4. Flash the stock recovery using the command:
Code:
fastboot flash recovery recovery.img
5. Change your cid to HTC__001, using the command:
Code:
fastboot oem writecid HTC__001
You have to be in FASTBOOT USB mode in the bootloader for the command to work.
5. Run a Jelly Bean 3.16 RUU from here:
http://androidfiles.org/ruu/securek...28_10.27.50.08L_release_301814_signed_2_4.exe
6. Done!
Hope it helps
Click to expand...
Click to collapse
First of all THANKS SO MUCH
and should i be in fastboot mode when doing supercid ? and what should i do for the md5 file ?
THANKS

Zaman-The-Man said:
First of all THANKS SO MUCH
and should i be in fastboot mode when doing supercid ? and what should i do for the md5 file ?
THANKS
Click to expand...
Click to collapse
Hi,
I forgot to link the instructions for S-OFF, my apologies. I have corrected that now.
You should not be in fastboot mode when doing supercid, I didn't realize this. You should be booted into Android. I understand the catch-22 you are having here, so you may want to flash a custom ROM like CM10 for the time being, and then do SuperCID with USB Debugging enabled in Settings.
The md5 file is used to check for corrupt downloads, you download the file and use a tool to check the file's MD5 sum on the PC. Then you match it to the one I gave you and see if it matches. The purpose of this is so that you don't accidentally flash a corrupt file.
Also, the CID you need to find is not T-MOB010, but H3G__001 (two underscores there, to make it 8 digits). Change that to 11111111 (8 digits, again)

usaff22 said:
Hi,
I forgot to link the instructions for S-OFF, my apologies. I have corrected that now.
You should not be in fastboot mode when doing supercid, I didn't realize this. You should be booted into Android. I understand the catch-22 you are having here, so you may want to flash a custom ROM like CM10 for the time being, and then do SuperCID with USB Debugging enabled in Settings.
The md5 file is used to check for corrupt downloads, you download the file and use a tool to check the file's MD5 sum on the PC. Then you match it to the one I gave you and see if it matches. The purpose of this is so that you don't accidentally flash a corrupt file.
Also, the CID you need to find is not T-MOB010, but H3G__001 (two underscores there, to make it 8 digits). Change that to 11111111 (8 digits, again)
Click to expand...
Click to collapse
do i need to relock bootloader wen running the ruu or just the flash stock recovery ?

Zaman-The-Man said:
do i need to relock bootloader wen running the ruu or just the flash stock recovery ?
Click to expand...
Click to collapse
you shouldn't need to

usaff22 said:
you shouldn't need to
Click to expand...
Click to collapse
cant i s off using hasoon2000 toolkit ? wouldnt that be easier ?
thanks

Zaman-The-Man said:
cant i s off using hasoon2000 toolkit ? wouldnt that be easier ?
thanks
Click to expand...
Click to collapse
No, you can't. The developer(s) of the S-OFF exploit don't want their work getting repackaged
Sent from my HTC One S using Tapatalk 2

usaff22 said:
No, you can't. The developer(s) of the S-OFF exploit don't want their work getting repackaged
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
Alright so
1) Do SuperCID : 11111111
2) S - OFF
3 Do ' fastboot oem writecid HTC__001 '
4) Flash Stock Recovery
5) Run RUU
looks like I'm sorted
But can I ask what shall If my device doesn't match this PJ4010000.zip ?

You can forget step 4. It's not needed with S-off.
Verstuurd van mijn HTC One S met Tapatalk

Zaman-The-Man said:
Basically I deleted everything off my One S (System OS,Backups,My Data) So I need to run a RUU to get my phone back to stock
------------------------------
**** TAMPERED ****
**** UNLOCKED ****
VLE PVT SHIP S-ON RL
Hboot-2.13.0000
Radio-1.11.50.05.28
Open DSP-v31.1.0.45.0815
eMMC-boot
Nov 20 2012 , 15:44:03,-1
------------------------------
Click to expand...
Click to collapse
Hi, I basically did the same thing as the OP. Deleted my backups by accident by choosing Factory Reset instead of Recovery. I think I am in an even worse position as I thought I had the right RUU as one point and needed to relock the bootloader. My bootloader screen looks like this at the moment.
------------------------------
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
VLE PVT SHIP S-ON RL
Hboot-2.13.0000
Radio-1.11.50.05.28
Open DSP-v31.1.0.45.0815
eMMC-boot
Nov 20 2012 , 15:44:03,-1
------------------------------
Can anyone tell me if this is a lost cause? Thanks.
This is the RUU I used -
OTA_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_1.11.50.05.28_10.27.50.08L_release_301852xf01hejl416oev96.zip.
Does anyone know if this is definitely the wrong one?

To all: Guys, no need to use S-Off for RUU. I DON'T KNOW WHO THE F*** CREATED THE PROCESS OF S-OFFING FOR RUUs AS WHEN I RESTORE STOCK LAST YEAR, IT WAS A SIMPLE BOOTLOADER RELOCK, AND RUU WE GO. IF WE S-OFFED, WE S-ON USING ONE-TOUCH STUFF.
To folaxstar: Well, you got as far as him. However, you got the COMPLETELY WRONG RUU. Technically, IT'S NOT AN RUU AT ALL. It is a Android 4.1 Sense 4.5/+ update for European unlocked HTC One S.
Do a "fastboot getvar cid" without the quotes (of course). You should get a CID that looks like the following: T-MOB010(T-Mobile US, as an example, it might not match what you got). Someone could determine the correct RUU.

[Q] HTC SENSATION got completely stuck on boot (complicated)

correct RUU 3.32.161.11 in post #11
Hi people.
The thing at the moment is stuck at JuopunutBear. But better to start from begining...
I decided to flash a different rom into it. So i unlocked a bootloader, installed "4EXT Recoveryy Touch" and tried to flash it straight away without having any backup... then the device use to get stuck on boot logo (as i rear later because of "s-on") and enabling "smart flash" on 4ext might help... but it didn't worked for me so i decided to install "JuopunutBear" and get "s-off" (on device which does not boot up any more)...
But my plan failed because whatever i did it ends up on "JuopunutBear" screen.
i though this was going to work but it did not:
C:\Users\user\Desktop\ControlBearRelease_pyramid_ICS_WIN>controlbear.exe -r
======== ControlBear 0.8 beta for JuopunutBear S-OFF ==========
Restoring to normal mode
Searching for device.....
Found device... Please wait...
Device should be in normal boot mode....
Press ENTER to exit.....
changed nothing.
this is all info i can see on hboot:
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
eMMC-boot
Jan 13 2012, 17:33:34
As far i can at first i need to get rid of "JuopunutBear" at first.. and then somehow to make the rom work... have no idea what to do next... is it possible to do fresh reinstall for all regardless what mess is there right now?
that is definitely the last time i play like this but now only thing i want is to get it working...
I would be glad for some advice. thank you!

An RUU will make your phone completely stock. As for the juopuonut s-off, it seems like you are using an old version of control bear.
Look here for ruu: http://forum.xda-developers.com/showthread.php?p=26541170
Sent from my HTC Sensation

AndroidSupporter318 said:
An RUU will make your phone completely stock. As for the juopuonut s-off, it seems like you are using an old version of control bear.
Look here for ruu: http://forum.xda-developers.com/showthread.php?p=26541170
Sent from my HTC Sensation
Click to expand...
Click to collapse
Well you opened my eyes but still...

C:\Users\user\Desktop\ControlBearRelease_pyramid_ICS_WIN>fastboot getvar cid
cid: VODAP001
finished. total time: 0.003s
C:\Users\user\Desktop\ControlBearRelease_pyramid_ICS_WIN>fastboot getvar version
-main
version-main: 3.32.161.52
finished. total time: 0.003s
C:\Users\user\Desktop\ControlBearRelease_pyramid_ICS_WIN>
tried all steps till 4.4.2 With a PC, via fastboot USB and at the end i got an error
C:\Users\user\Desktop>fastboot flash zip PG58IMG.zip
sending 'zip' (437337 KB)... OKAY [ 64.719s]
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 139.619s
i found the rom, extracted it from exe file (boot.zip) then i needed to modify "android-info.txt" because there are just rally old rom`s with a proper signature. But i could only view and extract archive (if i archive it back it won't work) but not change files inside of them... i tried a couple of them and got the same problem that i can't modify them with any archiver ("archive is corrupt") so i just carryed on with extracting and archiving even when i read that it won't work... windows default archiver does not work, 7-zip as well, winRAR either... am i using a wrong archiver or there is some other way of getting everything done properly? i am totally lost

gyrtaz said:
C:\Users\user\Desktop\ControlBearRelease_pyramid_ICS_WIN>fastboot getvar cid
cid: VODAP001
finished. total time: 0.003s
C:\Users\user\Desktop\ControlBearRelease_pyramid_ICS_WIN>fastboot getvar version
-main
version-main: 3.32.161.52
finished. total time: 0.003s
C:\Users\user\Desktop\ControlBearRelease_pyramid_ICS_WIN>
tried all steps till 4.4.2 With a PC, via fastboot USB and at the end i got an error
C:\Users\user\Desktop>fastboot flash zip PG58IMG.zip
sending 'zip' (437337 KB)... OKAY [ 64.719s]
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 139.619s
i found the rom, extracted it from exe file (boot.zip) then i needed to modify "android-info.txt" because there are just rally old rom`s with a proper signature. But i could only view and extract archive (if i archive it back it won't work) but not change files inside of them... i tried a couple of them and got the same problem that i can't modify them with any archiver ("archive is corrupt") so i just carryed on with extracting and archiving even when i read that it won't work... windows default archiver does not work, 7-zip as well, winRAR either... am i using a wrong archiver or there is some other way of getting everything done properly? i am totally lost
http://forum.xda-developers.com/showthread.php?p=26541170
Click to expand...
Click to collapse
you are SON
so you need the correct RUU based on your CID/MiD/Version-Main ..
downloading any RUU and just modifying the android-info.txt wont do any good (it only works when you are SOFF)

ganeshp said:
you are SON
so you need the correct RUU based on your CID/MiD/Version-Main ..
downloading any RUU and just modifying the android-info.txt wont do any good (it only works when you are SOFF)
Click to expand...
Click to collapse
my current non-working version is 3.32.161.52
and the best i could find is 1.24.161...
i can't downgrade and can't put anything custom because i it is SON... so it is dead end for me.
is it possible to put some fake ROM by force (like copying files somewhere or smth...) even if it would not work but which would be seen as an "1.24.161..." when i would try to install it properly?
Just brain storming sorry if i am not telling anything clever...

It should be this one: http://hotfile.com/dl/176652525/e42....23.3504.07_M2_release_256146_signed.exe.html
If this one is not it, then try looking at the two sites that were listed in the ruu thread I gave you.
Sent from my HTC Sensation
---------- Post added at 10:43 AM ---------- Previous post was at 10:36 AM ----------
Actually, the link above is for Australian vodaphone users.
This one is general, not branded. It is for European users: http://hotfile.com/dl/158597479/f24...1.22.3504.07_M_release_252064_signed.exe.html
Sent from my HTC Sensation
---------- Post added at 10:45 AM ---------- Previous post was at 10:43 AM ----------
Also, the version number 1.2x is the gingerbread RUU's. 3.32 is for ICS RUU's
Sent from my HTC Sensation

AndroidSupporter318 said:
It should be this one: hotfile.com/dl/176652525/e4290a8/RUU_PYRAMID_ICS_Voda-Hutch_AU_3.32.862.13_Radio_11.69A.3504.00U_11.23.3504.07_M2_release_256146_signed.exe.html
If this one is not it, then try looking at the two sites that were listed in the ruu thread I gave you.
Sent from my HTC Sensation
Click to expand...
Click to collapse
i have checked these links you gave before and there was just gingerbread if i try to find exactly by uk wodafone
will try these too... thanks

AndroidSupporter318 said:
It should be this one: http://hotfile.com/dl/176652525/e42....23.3504.07_M2_release_256146_signed.exe.html
If this one is not it, then try looking at the two sites that were listed in the ruu thread I gave you.
Sent from my HTC Sensation
---------- Post added at 10:43 AM ---------- Previous post was at 10:36 AM ----------
Actually, the link above is for Australian vodaphone users.
This one is general, not branded. It is for European users: http://hotfile.com/dl/158597479/f24...1.22.3504.07_M_release_252064_signed.exe.html
Sent from my HTC Sensation
---------- Post added at 10:45 AM ---------- Previous post was at 10:43 AM ----------
Also, the version number 1.2x is the gingerbread RUU's. 3.32 is for ICS RUU's
Sent from my HTC Sensation
Click to expand...
Click to collapse
Didn't worked out...
How do you think if i unlock the bootloader again is it possible to delete the partition containing OS trough recovery and maybe than having a blank device i would be able to install any version of RUU..? Need some sort of other solution in this situation...

Hmm... can you try to format all partitions from recovery and then try ruu again?
Sent from my HTC Sensation

gyrtaz said:
Hi people.
The thing at the moment is stuck at JuopunutBear. But better to start from begining...
I decided to flash a different rom into it. So i unlocked a bootloader, installed "4EXT Recoveryy Touch" and tried to flash it straight away without having any backup... then the device use to get stuck on boot logo (as i rear later because of "s-on") and enabling "smart flash" on 4ext might help... but it didn't worked for me so i decided to install "JuopunutBear" and get "s-off" (on device which does not boot up any more)...
But my plan failed because whatever i did it ends up on "JuopunutBear" screen.
i though this was going to work but it did not:
C:\Users\user\Desktop\ControlBearRelease_pyramid_ICS_WIN>controlbear.exe -r
======== ControlBear 0.8 beta for JuopunutBear S-OFF ==========
Restoring to normal mode
Searching for device.....
Found device... Please wait...
Device should be in normal boot mode....
Press ENTER to exit.....
changed nothing.
this is all info i can see on hboot:
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
eMMC-boot
Jan 13 2012, 17:33:34
As far i can at first i need to get rid of "JuopunutBear" at first.. and then somehow to make the rom work... have no idea what to do next... is it possible to do fresh reinstall for all regardless what mess is there right now?
that is definitely the last time i play like this but now only thing i want is to get it working...
I would be glad for some advice. thank you!
Click to expand...
Click to collapse
Hi! Are you still looking for the right RUU? If I got it right you need the Vodafone UK one. You can download it from HERE That will work with your phone. I have the same RUU and always used it when I had to. Boot your phone into Bootloader, then select Fastboot. Make sure on the screen it does say Fastboot USB, then run the RUU and let it finish. Ohh! And don't forget to relock your bootloader before running the RUU. "fastboot oem lock"

AndroidSupporter318 said:
Hmm... can you try to format all partitions from recovery and then try ruu again?
Sent from my HTC Sensation
Click to expand...
Click to collapse
i think i am able to wipe something if i unlock it again but i have no idea what and what effects it is going to make if i do and if i am not going to delete too much (like HBOOT itself) and stuff like that...
is that way possible at all in my condition? is there any tutorials about doing so?
I just unlocked it again. i have some options..:
wipe data/factory reset
wipe cache
wipe catce + dalvik
wipe dalvik cache
wipe battery stats
format system
format data
format boot
format all partitions (except sdcard)
format sdcard
is deleting something going to make me able of installing gingerbread ruu? (because in theory just this old rom is good to my device)
is there anything useful in this list?

If you do a full wipe that's not going to effect hboot but all your data and the installed rom itself. That means you will not have a usable rom flashed on your phone so it will automatically boot into bootloader. But try to download the ruu I linked and follow the steps. If it doesn't work then we can figure out something else.
Sent from your back garden! Don't look back!

matekaneve said:
Hi! Are you still looking for the right RUU? If I got it right you need the Vodafone UK one. You can download it from HERE That will work with your phone. I have the same RUU and always used it when I had to. Boot your phone into Bootloader, then select Fastboot. Make sure on the screen it does say Fastboot USB, then run the RUU and let it finish. Ohh! And don't forget to relock your bootloader before running the RUU. "fastboot oem lock"
Click to expand...
Click to collapse
[RED]OH WOW MATE!!! YOU ARE MY HERO SINCE NOW! EVERYTHING WORKED JUST AS IT SHOULD[/RED]
anyway it is still interesting to me what can you delete with these functions of "4eXT" in the list and if my theory about deleting something and installing gingerbread is right? if yes what should i wipe or format?

When you are flashing roms, in 4ext recovery, there is an option to format all partitions. By doing so you can achive a fresh and clean install of the chosen rom. It does not affect your hboot or your firmware. It only ereases the partitions roms are using. To install gingerbread roms or ruu, you must flash the appropriate gingerbread firmware first. To do so, you must achive s-off first. As you already have 3.32 firmware installed you are "only" able to flash all the currently available ice cream sandwich and jelly bean roms. Hope this helps.
Sent from your back garden... Don't look back!

matekaneve said:
When you are flashing roms, in 4ext recovery, there is an option to format all partitions. By doing so you can achive a fresh and clean install of the chosen rom. It does not affect your hboot or your firmware. It only ereases the partitions roms are using. To install gingerbread roms or ruu, you must flash the appropriate gingerbread firmware first. To do so, you must achive s-off first. As you already have 3.32 firmware installed you are "only" able to flash all the currently available ice cream sandwich and jelly bean roms. Hope this helps.
Sent from your back garden... Don't look back!
Click to expand...
Click to collapse
aha... so if i would not have got any version above 3.32.161 my phone would be pretty much doomed..?
just asking for basic knowledge if i would have any similar problems in the future.. should i seek some info for bricked phone recovery then?

gyrtaz said:
aha... so if i would not have got any version above 3.32.161 my phone would be pretty much doomed..?
just asking for basic knowledge if i would have any similar problems in the future.. should i seek some info for bricked phone recovery then?
Click to expand...
Click to collapse
Honestly, do not worry about bricking your device, just enjoy the freedom rooting gave you. If something goes wrong, you can always use that ruu. The latest voda UK version is 3.32.161.(52)? The main thing is the first 3 digits: 3.32-> ics firmware, ...161-> Vodafone UK code. The last numbers don't matter. Always make sure you flash the correct rom according to your firmware version and your device
Btw. You can install roms require 3.32 or 3.33 firmware! Enjoy flashing!
Sent from my HTC Sensation Z710e using xda app-developers app

matekaneve said:
Honestly, do not worry about bricking your device, just enjoy the freedom rooting gave you. If something goes wrong, you can always use that ruu. The latest voda UK version is 3.32.161.(52)? The main thing is the first 3 digits: 3.32-> ics firmware, ...161-> Vodafone UK code. The last numbers don't matter. Always make sure you flash the correct rom according to your firmware version and your device
Btw. You can install roms require 3.32 or 3.33 firmware! Enjoy flashing!
Sent from my HTC Sensation Z710e using xda app-developers app
Click to expand...
Click to collapse
Come on... I am about learning stuff and knowing. Maybe some day helping someone else. You can tell someone who doesn't really care to not worry instead of telling a short proper answer... sorry i am not trying to be offensive but it was one of the "try using google" sort of answers and that was how i feel about it...
THANKS FOR ALL THE HELP YOU ALL :highfive: