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
Related
i have go to S-On whit this tutorial
http://forum.xda-developers.com/showthread.php?t=1187231
after i reboot i can only in the bootloader an its say Security warning.
I can not flash a RUU .
The VF Ruu say bootloader version error, and the HTC Ruu say User ID Wrong.
wat can i do?? My device is a VF devices..
or iss the device absolutly Bricket?!
Bootloader Shows:
****Security Warning****
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0000
Radio-3805.06.02.03_M
eMMC-boot
Mar 10 2011,14:58:38
edit: i think i need a RUU_Saga_Vodafone_UK_1.47. ROM
****....
Try again and again with that RUU.
It didn't worked first time for me either.
Or try other RUU.
I used
RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.080 5U_38.03.02.11_M_release
You should go to fastboot and try RUU
thanks for your answers.
i try it again and again (in fastboot)
it say update from 1.47.161.2
to 1.32.161.1 than it stop into 104 Bootloader Version Error.
I use the VF UK 1.32.161.1
all HTC Europe RUU`s says USER ID Error
before i would go to stock i have installed de Virtuos unity 1.31.
and befor this the VF German 1.47...
Try other RUU's...It has to work, anyway the phone is not bricked....maybe you should try revolutionary to get it S-off again. Don't know if it works if you are in fastboot, but you can try.
I try all the RUU`s and all give me (Device ID ERROR, USER ID ERROR) the Vodafone RUU alone give me the Bootloader Version ERROR...
I Try this again and again and ever it give me this errors.
Can not understand that is not worked...
i think i must really wait for a Vodafone RUU Leak that have the version 1.47.
Revolutionary say ever "waiting for Device" i think it will not work into the Fastboot Mode
I am very happy wen any can help me to make the system run.
i found the debug files of the RUUs and cane see wat he do..
i check and can make Fastboot commands over cmd
like this : fastboot devices
than it give an output like:
SH16KTJ01149 fastboot
wen i use any adb commands it never found the device....
can we any make over the Fastboot commands for fixing my problem?!
Or can we any moddifing the RUUs that this accept my device?!
i have copy two debug messages of the Vodafone RUU and a other:
Code:
<T011153><DEBUG><CMD>fastboot -s SH16KTJ01149 flash zip C:\Users\Dee\AppData\Local\Temp\{95567211-FFFE-46A1-B012-975D1FD8FE2D}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip</CMD>
</DEBUG></T011153>
<T011237><DEBUG><OUT>sending 'zip' (268758 KB)... OKAY</OUT>
</DEBUG></T011237>
<T011237><DEBUG><OUT>writing 'zip'... INFOadopting the signature contained in this image...</OUT>
</DEBUG></T011237>
<T011237><DEBUG><OUT>INFOsignature checking...</OUT>
</DEBUG></T011237>
<T011318><DEBUG><OUT>INFOzip header checking...</OUT>
</DEBUG></T011318>
<T011318><DEBUG><OUT>INFOzip info parsing...</OUT>
</DEBUG></T011318>
<T011318><DEBUG><OUT>INFOchecking model ID...</OUT>
</DEBUG></T011318>
<T011318><DEBUG><OUT>INFOchecking custom ID...</OUT>
</DEBUG></T011318>
<T011318><DEBUG><OUT>INFOchecking main version...</OUT>
</DEBUG></T011318>
<T011318><DEBUG><OUT>FAILED (remote: 43 main version check fail)</OUT>
</DEBUG></T011318>
or debug messages like this:
Code:
<T230252><DEBUG><CMD>fastboot -s SH16KTJ01149 flash zip C:\Users\Dee\AppData\Local\Temp\{FB1AC174-A654-4612-B610-902E97243E0E}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip</CMD>
</DEBUG></T230252>
<T230335><DEBUG><OUT>sending 'zip' (254595 KB)... OKAY</OUT>
</DEBUG></T230335>
<T230335><DEBUG><OUT>writing 'zip'... INFOadopting the signature contained in this image...</OUT>
</DEBUG></T230335>
<T230335><DEBUG><OUT>INFOsignature checking...</OUT>
</DEBUG></T230335>
<T230414><DEBUG><OUT>INFOzip header checking...</OUT>
</DEBUG></T230414>
<T230414><DEBUG><OUT>INFOzip info parsing...</OUT>
</DEBUG></T230414>
<T230414><DEBUG><OUT>INFOchecking model ID...</OUT>
</DEBUG></T230414>
<T230414><DEBUG><OUT>FAILED (remote: 41 model id check fail)</OUT>
</DEBUG></T230414>
HTML:
<T011638><DEBUG><OUT>sending 'zip' (254865 KB)... OKAY</OUT>
</DEBUG></T011638>
<T011638><DEBUG><OUT>writing 'zip'... INFOadopting the signature contained in this image...</OUT>
</DEBUG></T011638>
<T011638><DEBUG><OUT>INFOsignature checking...</OUT>
</DEBUG></T011638>
<T011717><DEBUG><OUT>INFOzip header checking...</OUT>
</DEBUG></T011717>
<T011717><DEBUG><OUT>INFOzip info parsing...</OUT>
</DEBUG></T011717>
<T011717><DEBUG><OUT>INFOchecking model ID...</OUT>
</DEBUG></T011717>
<T011717><DEBUG><OUT>INFOchecking custom ID...</OUT>
</DEBUG></T011717>
<T011717><DEBUG><OUT>FAILED (remote: 42 custom id check fail)</OUT>
</DEBUG></T011717>
Stuck in bootloader after use the S-off to S-on tutorial
no one can help???
edit: i see that is the exact same problem in this treath : http://forum.xda-developers.com/showthread.php?t=1190050
should i extract the boot.img and recovery.img from the rom.zip (VF Ruu) and install it over Fastboot commands??
i see a topic about this, but it was another htc phone
http://forum.xda-developers.com/showthread.php?t=1168081
can this work ?!
or should iflash CWM over fastboot ?? can i acces than CWM on s-on hboot??
i have backups from my stock rom.
should i go to buy a xtc-clip for s-off again?!
i think nobody have a solution for my problem.
Silverbullet09 said:
should i go to buy a xtc-clip for s-off again?!
i think nobody have a solution for my problem.
Click to expand...
Click to collapse
I'm afraid that I don't really know what is the best step for you to do next, so aren't going to offer any advice in case it's incorrect.
Don't buy an xtc either look into the pay as you go xtc option or find someone who owns one near where you live, and pay to use it, should be about a tenth the cost.
See a very old thread that I created regarding the xtc clip http://forum.xda-developers.com/showthread.php?t=1076937
Swyped from HTC Desire S using XDA Premium
Try to use steps 1 - 10 from this guide : http://forum.xda-developers.com/showthread.php?t=1190992
If anyone is interested his phone is fixed now.
The S-OFF to S-ON is not correct is a couple of places, and people who have taken the 1.47.XXX.X OTA or RUUs could find themselves in difficulty if they are not super cid particularly on branded phones.
It as a bit of a PITA, but if anyone else finds themself in this situation shoot me a PM, I'll post the solution when I get time but until then I'll help people who get stuck.
globatron said:
If anyone is interested his phone is fixed now.
The S-OFF to S-ON is not correct is a couple of places, and people who have taken the 1.47.XXX.X OTA or RUUs could find themselves in difficulty if they are not super cid particularly on branded phones.
It as a bit of a PITA, but if anyone else finds themself in this situation shoot me a PM, I'll post the solution when I get time but until then I'll help people who get stuck.
Click to expand...
Click to collapse
plz provide us with more information..
I s-offed my device using fre3vo & Revolutionary, as i had installed the update from HTC.
are you saying that if I try to use the procedure from 1st post to S-on, i might brick my phone?
what is super CID? my phone is not branded
@ all
my phone is Fixed!!!
Special Thanks on the Alpharev/Revolutionary Team!
@Bubaaak
in this situation you can not take any adb commands.
Only Fastboot commands are work.
Silverbullet09 said:
@ all
my phone is Fixed!!!
Special Thanks on the Alpharev/Revolutionary Team!
@Bubaaak
in this situation you can not take any adb commands.
Only Fastboot commands are work.
Click to expand...
Click to collapse
Very glad to hear it
Swyped from HTC Desire S using XDA Premium
Nomader0 said:
plz provide us with more information..
I s-offed my device using fre3vo & Revolutionary, as i had installed the update from HTC.
are you saying that if I try to use the procedure from 1st post to S-on, i might brick my phone?
what is super CID? my phone is not branded
Click to expand...
Click to collapse
do not use this procedure to s-on your Phone wen it iss branded, and you never have a 1.47 RUU from your Provider.
Your Phone is not Bricked but it will Stock on the bootloader,
i think wen you make a GoldCard before you S-on with this methode you are able to install a 1.47 RUU wen this is avaibled for you.
(I am not Sure, i think this only)
The know way to fixed this Problem wen you will not have a GoldCard will tell you another. Thats not my Fame
I think the best iss all have to wait off a SAFE S-ON methode.
We have not the Vodafone UK RUU can install than its not leaked with Version 1.47.
We have install the HTC Europe RUU with this Versions number on my Phone.
A Super CID let you install all RUU Updates with Version 1.47.Never need a GoldCard for this, wen you have Super CID.
I Know the workaround for this but i will tested this before i post this thing her.
@ben_pyett
so if my phone is not branded=i am super CID?
and it is safe to s-on with this method?
no you must enter the super cid wen you are s-off ...
i think you can go with the tutorial but all HTC RUU Europe for unbranded Phones avaibled.
Silverbullet09 said:
@ all
my phone is Fixed!!!
Special Thanks on the Alpharev/Revolutionary Team!
@Bubaaak
in this situation you can not take any adb commands.
Only Fastboot commands are work.
Click to expand...
Click to collapse
How to you fixed it ?
my DS work only fastboot cmd
help me, plzz...
poppy8x:
In order to bypass CID errors while flashing a RUU you can try one of two methods:
- If you're still S-OFF, you can change your CID to a SuperCID using fastboot (many guides are available at the HTC Sensation forums). Remember to write down your original CID.
- If you're S-ON already, you can create a goldcard using this guide: http://theunlockr.com/2010/03/10/how-to-create-a-goldcard/ You can get the SD's CID from another Android phone, doesn't have to be yours. Insert the goldcard before flashing the RUU (and keep it in until the process ends), and you should be good to go.
Hi Everyone..
I have HTC sensation xe
Software version: 4.0.3 ((3.32.405.... Europe))
I bought this phone just 3 days ago and i was trying to make S-off Just to upgrade to official Middle East Rom (3.32.415...) as i got the RUU from here.
I try many time to use JuopunutBear But always gives "device
not root"..
Last time i try then start make backup then reboot
i make the wire-trick at same place for the picture and video in article..
after that the mobile stop at JuopunutBear screen,, i try fastboot, factory reset, recovery from Hboot screen,, all is just come back to same JuopunutBear screen
and do nothing..
The phone is restarted every 5 min automaticly and give HTC green logo first then stuck on same screen in image
I use this thread
http://forum.xda-developers.com/showthread.php?t=1661631
I unlock by HTCdev.com
and do all steps one by one
I make backup for recovery by Clockworkmod before as i learn from other thread
Please help me what i can do and what's happen with me
Any Attention, response, answer or help will be really appreciated
MAESTRO_X said:
Hi Everyone..
I have HTC sensation xe
Software version: 4.0.3 ((3.32.405.... Europe))
I bought this phone just 3 days ago and i was trying to make S-off Just to upgrade to official Middle East Rom (3.32.415...) as i got the RUU from here.
I try many time to use JuopunutBear But always gives "device
not root"..
Last time i try then start make backup then reboot
i make the wire-trick at same place for the picture and video in article..
after that the mobile stop at JuopunutBear screen,, i try fastboot, factory reset, recovery from Hboot screen,, all is just come back to same JuopunutBear screen
and do nothing..
The phone is restarted every 5 min automaticly and give HTC green logo first then stuck on same screen in image
I use this thread
http://forum.xda-developers.com/showthread.php?t=1661631
I unlock by HTCdev.com
and do all steps one by one
I make backup for recovery by Clockworkmod before as i learn from other thread
Please help me what i can do and what's happen with me
Any Attention, response, answer or help will be really appreciated
Click to expand...
Click to collapse
connect the phone to PC and go to the folder with controlbear.exe
Hold down shift and right-click Select the option open command window here and type this command and press enter:
Code:
controlbear.exe -r
After that, if you don't wanna run the controlbear again, don't forget to remove temp_root
Thankssssss
It's really great
Thank you very much kgs1992
I thought my mobile is brick down
So.. what's the best way to upgrade my phone rom
Just i need the official ME (Arabic) RUU Rom to be installed?
and how to delete temp_root?
Thanks & Regards
MAESTRO_X said:
It's really great
Thank you very much kgs1992
I thought my mobile is brick down
So.. what's the best way to upgrade my phone rom
Just i need the official ME (Arabic) RUU Rom to be installed?
and how to delete temp_root?
Thanks & Regards
Click to expand...
Click to collapse
It's included in the guide that your viewing.
I'm not sure about language specific RUUs. You can try my RUU Guide, link in my signature.
I try to open your threads
[GUIDE]RUU related info (S-On with RUU, extracting rom.zip & manual flashing, etc)
but:
Error: Unable to find site's URL to redirect to.
Please check that the URL entered is correct. To learn more about TinyURL.com, please visit the homepage.
!!??
MAESTRO_X said:
I try to open your threads
[GUIDE]RUU related info (S-On with RUU, extracting rom.zip & manual flashing, etc)
but:
Error: Unable to find site's URL to redirect to.
Please check that the URL entered is correct. To learn more about TinyURL.com, please visit the homepage.
!!??
Click to expand...
Click to collapse
I'm sorry, I was editing my signature, something must have gone wrong.
It's fine now.
You did not need to unlock your bootloader.
Plus, if you're only interested in your stock RUU, you should be able to just change cid in android-info.txt. Might be wrong
how to use android-info.txt, or even make my mobile with supercid 11111111
I try many ways not work,,
I still s-on and i interest with official ruu for middle east and as i see the version is 3.415,, and my version is 3.405
so what's the best way to install this ruu without troubles as i tried many ways
Run your RUU. When it loads, check your temp folder for the zip file. Modify android-info.txt in the zip with your cid. Either modify the existing zip and continue with the RUU update, or rename the zip to PG58IMG.zip, place on root, and boot into bootloader.
renaming and put on sdcard i already tried but i will try editing cid and see if possible..
i will do factory reset first maybe better..
thanks alot
MAESTRO_X said:
renaming and put on sdcard i already tried but i will try editing cid and see if possible..
i will do factory reset first maybe better..
thanks alot
Click to expand...
Click to collapse
Man.. In my guide I already told you if you have htc dev unlocked bootloader please follow the guide by auggie2k.. Buy you still followed mine.. That's the issue soff didnt worked
Also you said you want to install middle east RUU.. That is easily possible in your case
First get the cid of middle east from those thread http://forum.xda-developers.com/showthread.php?t=1195475
It it HTC__J15 I think (Arabic one)
Then change the cid
Connect them phone in fastboot and then to pc.. Then open command prompt from there adb folder on pc
Then type this
fastboot oem writecid <your cid >
(you'll lose the supercid though)
Now just reboot to bootloader again
fastboot reboot-bootloader
Then from this fastboot mode itself
Relock the bootloader
fastboot oem lock
Then run the RUU.exe on pc
(phone should be in fastboot)
Ps: changing the cid in android-info.txt won't help you as you are SON
Sent from my pyramid.. Through blazing fast sonic waves
OK, so there is a signature check that prevents you from simply changing the cid in the android-info? Or does is the cid defined somewhere else?
Being supercid, you should be able to flash any ruu you want, assuming it's not a downgrade I thought. Or does that still only apply for s-off?
ganeshp said:
Man.. In my guide I already told you if you have htc dev unlocked bootloader please follow the guide by auggie2k.. Buy you still followed mine.. That's the issue soff didnt worked
Also you said you want to install middle east RUU.. That is easily possible in your case
First get the cid of middle east from those thread http://forum.xda-developers.com/showthread.php?t=1195475
It it HTC__J15 I think (Arabic one)
Then change the cid
Connect them phone in fastboot and then to pc.. Then open command prompt from there adb folder on pc
Then type this
fastboot oem writecid <your cid >
(you'll lose the supercid though)
Now just reboot to bootloader again
fastboot reboot-bootloader
Then from this fastboot mode itself
Relock the bootloader
fastboot oem lock
Then run the RUU.exe on pc
(phone should be in fastboot)
Ps: changing the cid in android-info.txt won't help you as you are SON
Sent from my pyramid.. Through blazing fast sonic waves
Click to expand...
Click to collapse
S On implies that you cannot fire fastboot oem commands as well, right? how will he writecid? :/
I meant if he changed the cid in android-info to his native cid, then he should be able to flash it while s-on?
ziddey said:
I meant if he changed the cid in android-info to his native cid, then he should be able to flash it while s-on?
Click to expand...
Click to collapse
Mate, if the android-info.txt is changed, the rom.zip will change. This implies signature check will fail due to modified file size. :/
ganeshp said:
Man.. In my guide I already told you if you have htc dev unlocked bootloader please follow the guide by auggie2k.. Buy you still followed mine.. That's the issue soff didnt worked
Also you said you want to install middle east RUU.. That is easily possible in your case
First get the cid of middle east from those thread http://forum.xda-developers.com/showthread.php?t=1195475
It it HTC__J15 I think (Arabic one)
Then change the cid
Connect them phone in fastboot and then to pc.. Then open command prompt from there adb folder on pc
Then type this
fastboot oem writecid <your cid >
(you'll lose the supercid though)
Now just reboot to bootloader again
fastboot reboot-bootloader
Then from this fastboot mode itself
Relock the bootloader
fastboot oem lock
Then run the RUU.exe on pc
(phone should be in fastboot)
Ps: changing the cid in android-info.txt won't help you as you are SON
Sent from my pyramid.. Through blazing fast sonic waves
Click to expand...
Click to collapse
I try this at all before from the guide but my cid not change at all
i have already HTC__J15 but also the RUU of arabic dosen't install with two ways
(1- copy in the sdcard and hboot)
(2- directly setup in windows with or without edit android-txt to my cid)
I think s-off is the best way but i try also many time with JB but no way
maybe there's other wrong but i still not discover it..
Is there any other tool for S-off as my version 1.29!?
Thank you friend ,, it's really appreciate that all people here is kindly helping
with quick response
MAESTRO_X said:
I try this at all before from the guide but my cid not change at all
i have already HTC__J15 but also the RUU of arabic dosen't install with two ways
(1- copy in the sdcard and hboot)
(2- directly setup in windows with or without edit android-txt to my cid)
I think s-off is the best way but i try also many time with JB but no way
maybe there's other wrong but i still not discover it..
Is there any other tool for S-off as my version 1.29!?
Thank you friend ,, it's really appreciate that all people here is kindly helping
with quick response
Click to expand...
Click to collapse
Yes, I too think S Off is best for you, but it's best if you wait for ganeshp to reply, as he is the most experienced of us..
kgs1992 said:
Yes, I too think S Off is best for you, but it's best if you wait for ganeshp to reply, as he is the most experienced of us..
Click to expand...
Click to collapse
Yes sure i will wait..
Thank you and everyone for help and share experience..
kgs1992 said:
S On implies that you cannot fire fastboot oem commands as well, right? how will he writecid? :/
Click to expand...
Click to collapse
Yes technically that should be the case.. But apparently there is a hole in HTC bootloader.. Which makes it change the cid.. (happens only on 1.2x hboots only though)
Edit: What cid change didnt worked?
We tried it on two guys one having unlocked bootloader and other having looked bootloader.. For both of them it worked fine.
Have you tried checking the cid after changing it?
First change cid using
fastboot oem writecid <your cid >
(it says failed but after rebooting the bootloader using "fastboot reboot-bootloader" if you check for cid again using "fastboot getvar cid" it should show you the new cid)
If the above was success then just Run the Arabic ruu...
Otherwise soff is not really required for you as you are htc dev unlocked
Just install the asanic custom rom by darkmantra if you just want support for Arabic language..
For installing custom roms while SON. Please follow the guide "flashing rom's with SON" by asskicker2 present in sensation general section
If you insist on getting that Arabic RUU.. Then soff is the only way for you..
Please follow the " guide to soff using Juopunutbear " by auggie2k which is also present in sensation general section
Sent from my pyramid.. Through blazing fast sonic waves
dude my phone is also stuck on the same screen n when did the above explnation it says waiting for device n dosent goes forward ne where tell me what to do my cell is bricked plzz help
htc sensation
hboot 1.27.0000
rooted
unlocked form htc dev
Hello Everyone,
I need to send my Sensation in for dust removal. I was running CM9, changed my CID back to BM___01 or something for bell mobility, where the phone came from. I then did the
Code:
fastboot oem writesecureflag 3
and got a brick. I unbricked successfully with the unbricking project. Kudos to the devs of that.
I now have a problem. My CID is for bell, so can't flash anything else, error in the ruu.
My hboot is 1.27 and my radio 11.22.3504.07_M, so I can't flash any of the bell ruu because of error 140 wrong bootloader. The only RUUs for bell are gingerbread with really old hboot.
I think I need to s-off and change CID to get a newer ICS RUU on here.
3 questions:
1. can I s-off without any firmware (no recovery, no rom) on the device, so no adb
2. Is there any other way to get a booting rom on here?
3. can I revert back to the gingerbread RUU using some sort of hboot downgrade, once I have something installed? (rom)
Thanks for your help.
jcarrz1
jcarrz1 said:
Hello Everyone,
I need to send my Sensation in for dust removal. I was running CM9, changed my CID back to BM___01 or something for bell mobility, where the phone came from. I then did the
Code:
fastboot oem writesecureflag 3
and got a brick. I unbricked successfully with the unbricking project. Kudos to the devs of that.
I now have a problem. My CID is for bell, so can't flash anything else, error in the ruu.
My hboot is 1.27 and my radio 11.22.3504.07_M, so I can't flash any of the bell ruu because of error 140 wrong bootloader. The only RUUs for bell are gingerbread with really old hboot.
I think I need to s-off and change CID to get a newer ICS RUU on here.
3 questions:
1. can I s-off without any firmware (no recovery, no rom) on the device, so no adb
2. Is there any other way to get a booting rom on here?
3. can I revert back to the gingerbread RUU using some sort of hboot downgrade, once I have something installed? (rom)
Thanks for your help.
jcarrz1
Click to expand...
Click to collapse
Hmm that's a rough situation you are in.. If you can't find the ruu that would be a problem..
First try contacting football.. For ics ruu of bell.. (football provides most of the ruu's.. He is the OP of pyramid shipped rom collections thread present in sensation development section)
Try changing Cid to a well know one
Like this.. What you do is
First reboot to bootloader
fastboot oem writecid HTC__001 (supercid won't work.. So stick with this for now)
Then remove battery..
Then reinsert it. Power on to bootloader
And check Cid
fastboot getvar cid
If this worked.. Great. Find a Europe ruu and flash it
Last .. Try htc-dev unlock.. If luckily you..got unlocked bootloader..
Flash custom rom..Then SOFF..Then change back Cid..Then flash the old ruu of your Cid..Then SON
To get a working rom
Sent from my pyramid.. Through blazing fast sonic waves
For future reference; S-ON is the last thing you do when sending the phone back. RUU needs to happen before that.
The situation you're in, you're going to have to HTC Dev unlock your bootloader, and fastboot flash system and boot, possibly install a firmware PG58IMG as well... hopefully that will be enough to get the phone booting. Then you'll want to S-OFF and flash the RUU (this will also set you back to ***LOCKED***), then you can S-ON.
You guys are so helpful. I will try this.
My utmost thanks,
jcarrz1
Is HTC dev unlock reversible, and does it void my warranty even if I reverse it? does it leave any trace/can they tell?
Getting S-OFF removes all trace of it.
Rusty! said:
Getting S-OFF removes all trace of it.
Click to expand...
Click to collapse
And then getting S-ON again will be like stock configuration?
No, going S-OFF changes ***UNLOCKED*** back to ***LOCKED***
jcarrz1 said:
And then getting S-ON again will be like stock configuration?
Click to expand...
Click to collapse
yep...
if you use juopunutbear soff after HTC-dev unlock ..you will get locked/juopunutbear bootloader (instead of relocked )
then RUU (to make everything stock..and to prevent wrong SON brick) and SON again ..will be complete stock
Again, I am amazed by your helpfulness.
Thanks guys! you run the general section
jcarrz1
I can't flash firmware because it says "parsing package" and then does nothing
I can't push a system.img because it says "too large"
I've tried ARHD, CM9, and stock zippified roms, and none of them boot. Probably firmware issue, but see first problem...
any tips?
jcarrz1 said:
I can't flash firmware because it says "parsing package" and then does nothing
I can't push a system.img because it says "too large"
I've tried ARHD, CM9, and stock zippified roms, and none of them boot. Probably firmware issue, but see first problem...
any tips?
Click to expand...
Click to collapse
ohk for firmware flash you can use this
copy the firmware zip (PG58IMG.zip) to the adb/fastboot folder
open command prompt from adb/fastboot
then these commands one by one
fastboot erase cache
fastboot oem rebootRUU (black screen with silver HTC)
fastboot flash zip PG58IMG.zip (if failed while flashing in the middle ..be careful)
fastboot reboot-bootloader
that would flash the firmware
UPDATE 30/11/2013:
This thread describes my efforts in updating my unlocked One S to a hboot higher than 2.13. The phone had an H3G CID but non of the RUU's (see thread) worked. For me the solution was to Super CID and S-OFF the phone. Iḿ now on hboot 2.16.
END UPDATE
After more than two years of using Android (Legend, Desire S) phones and rooting them, I now have to register to be able to ask a question on this great forum.
Yesterday I obtained a One S. It is a UK model (not sim-locked to a carrier). I unlocked the bootloader almost immediatly with the intention of running a 4.3 or 4.4 based ROM (cyanogenmod or codename lungo). Here are some of the getvar details:
Code:
version: 0.5
version-bootloader: 2.13.0000
version-baseband: 1.11.50.05.28
version-misc: PVT SHIP S-ON
cidnum: H3G__001
boot-mode: FASTBOOT
Both cyanogen 4.4 and lungo ended in a bootloop and I figured it had to do with the hboot version. Self assured as I was I did not do a nandroid backup in twrp when flashing cyanogen and lungo and I ended up looking for a rom that would boot. I was succesful with MagioRom_ONE_S_RC6. From that I intended to use a RUU to update my hboot. I tried several (including both the H3G's) from this resource. All ended up in errors (131, 132, 155, 170 and probably some more). After reading some threads I relocked the bootloader and flashed stock recovery. All to no avail, no RUU will install. After reading a bit more I concluded that SuperCID was my best option of getting my brand new One S to a higher hboot version. I decided to go with this tutorial, but I ended up in another frustration: adb is not working for me in both windows (7) and linux (ubuntu). I reinstall the drivers (under windows) and tried some other things, but nothing works.
This is where I am now. I hope someone is willing to help. I tried to be as complete in describing the things I tried and the information I have, but I'd be happy to provide any additional info.
Getting custom roms on the legend and desire s was a lot easier.
First I do not own a UK version One S, I have the TMOUS but these are some tips that I used to help get my phone back from a non booting state.
Couple things,
Make absolutely sure this is a Ville not a VilleC2 (aka S3 One S)
Are you at all able to boot the phone to a recovery program (TWRP/CWM etc)?
Ensure that you have followed these instructions to get adb and fastboot to work. Use the Unlock section. Its best to make sure you can fastboot or at least adb before doing anything with the phone.
If you can get to fastboot (Power and Vol Down button), connect your phone and run the command "fastboot devices" post output - keep in mind command shell has to be at the adb directory most of the time C:\adb or something similar.
Make sure you have the latest driver installed and to remove (completely uninstall it) HTC Sync or Sync Manager. Not needed if you don't keep the stock ROM on your phone IMO. If you are unsure, remove all HTC software and just reinstall the driver.
Make sure you are running the right RUU for your specific device. What carrier was this phone for when it was purchased? Assuming it is H3G this is the latest RUU available for that particular OneS. You will have to run either the same version F/W or later RUU, you cannot go backwards.
Once we get the phone back to stock rom. Then start over by unlocking bootloader and getting S-OFF THEN start to flash roms.
In order to run CM11 Beta you need to have l a certain recovery installed + a few other things. I think it would be best if you can get back on CM10.1.3 Stable first then attempt to go to CM11.
TL;DR
Verify carrier and version of phone
Lock Bootloader if not already done
Download and run carrier specific RUU while in fastboot mode (power +vol down)
Unlock Bootloader
S-OFF
Flash rom
@pyrocide
Thanks for the reply. I've been working through your post. First I wanna point out that the phone is in a working state know running the MagioRom and I can boot into TWRP recovery.
Here is the output for fastboot devices:
Code:
SH24PW402945 fastboot
I'm sure it is an s4. It is says Z520e and 1.5 ghz on the box. I got the phone from ebay, so I'm not 100% which carrier it was on, but there was a T-Mobile sim still in the phone :silly:. The CID reads H3G though and the phone is not locked to a carrier/network since my giffgaff sim works fine.
I got adb to work. Thanks for that :good:.
I relocked the bootloader with fastboot oem lock (it know says 'relocked'). Running the suggested RUU ends in an error 155 during the veryfiying signature step.
And you ran the RUU while you were in fastboot usb mode?
based on Google
"ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again."
So the RUU is wrong, we need to find out specifically what version of OneS it is.
run this command while in fasboot usb mode
Code:
fastboot getvar all
post modelid: XXXXXXXXXX
The output of that:
Code:
modelid: PJ4010000
http://androidforums.appforerunner....ed-problem-restoring-ruu-error-131-151-a.html
Guy had the same problem and same modelid
Used this RUU and was able to go back to stock.
Hopefully this works.
Thanks for the help. Appreciate it.
That RUU ended in an 131 error, unfortunately.
H2Oxide said:
Thanks for the help. Appreciate it.
That RUU ended in an 131 error, unfortunately.
Click to expand...
Click to collapse
At this point i would suggest doing all Euro RUUs. That should have worked considering the modelid is the same for that guy and it worked. Sorry man but I don't know what else to suggest other than to do each RUU. If none of them work then something is definitely wrong.
pyrocide said:
At this point i would suggest doing all Euro RUUs. That should have worked considering the modelid is the same for that guy and it worked. Sorry man but I don't know what else to suggest other than to do each RUU. If none of them work then something is definitely wrong.
Click to expand...
Click to collapse
Would I need to reflash a/the stock recovery to make for a successful RUU flash?
The list of the RUU's I tried. Non worked... Really frustrating.
Code:
RUU_Ville_U_BM_1.70.666.1_R_Radio_0.16.31501S.06_3_10.20.31501S.09L_release_255222_signed.exe
RUU_Ville_U_BM_1.84.666.9_Radio_0.17.31501S.10_2_10.27.31501S.10L_release_265369_signed.exe
RUU_Ville_U_H3G_UK_1.53.771.4_Radio_0.15.31501S.19_2_10.13.31501S.06L_release_251870_signed.exe
RUU_Ville_U_H3G_UK_1.78.771.5_Radio_0.16.31501S.19_2_10.23.31501S.10L_release_258982_signed.exe
RUU_Ville_U_HTC_Europe_1.09.401.1_R_Radio_0.14.3059.14_2_release_243825_signed.exe
RUU_Ville_U_HTC_Europe_1.47.401.1_Radio_0.15.31501S.13_3_10.08.31501S.04L_release_250115_signed.exe
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
RUU_Ville_U_ICS_40_S_BM_2.40.666.1_Radio_1.09ts.50.02.04_10.08g.50.04L_release_280275_signed.exe
RUU_Ville_U_ICS_40_S_HTC_Europe_2.21.401.10_Radio_1.06s.50.02.27_2_10.08.50.04L__release_271119_signed.exe
RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5.exe
RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed.exe
RUU_Ville_U_ICS_40_S_TMOUS_2.35.531.7_Radio_1.08ts.50.02.16_10.08e.50.04L_release_279577_signed.exe
RUU_Ville_U_ICS_40_S_Vodafone_UK_2.38.161.6_Radio_1.08es.50.02.21_10.09c.50.04L_release_280400_signed.exe
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
RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.50.05.31_10.30.50.08L_release_309489_signed_ICS_2.exe
RUU_Ville_U_O2_UK_1.78.206.4_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258707_signed.exe
RUU_Ville_U_TMO_DE_1.77.111.5_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_259421_signed.exe
RUU_Ville_U_TMOUS_1.53.531.16_Radio_0.16.31501S.02_10.18.31501S.08L_release_262073_signed.exe
RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S.16_2_10.22.31501S.10L_release_263233_signed.exe
RUU_Ville_U_Vodafone_UK_1.53.161.3_Radio_0.15.31501S.19_2_10.13.31501S.06L_release_251482_signed.exe
RUU_Ville_U_Vodafone_UK_1.78.161.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258386_signed.exe
H2Oxide said:
Would I need to reflash a/the stock recovery to make for a successful RUU flash?
Click to expand...
Click to collapse
No, running the RUU erases custom recovery & flashes stock recovery.
Did all of the downloads MD5 checkout correctly?
Also, just to make sure we are ruling everything out. Did you run the RUU by double clicking or right clicking and Run as Administrator? If you just did it by double clicking rerun the one I posted that fixed the other guys issue by using Run as Administrator. Again be sure to be in fastboot usb mode and that "fastboot devices" command shows your device in the output. Make sure you use a usb 2.0 port in case of compatibility issues and the cable that came with the phone if possible.
pyrocide said:
No, running the RUU erases custom recovery & flashes stock recovery.
Did all of the downloads MD5 checkout correctly?
Also, just to make sure we are ruling everything out. Did you run the RUU by double clicking or right clicking and Run as Administrator? If you just did it by double clicking rerun the one I posted that fixed the other guys issue by using Run as Administrator. Again be sure to be in fastboot usb mode and that "fastboot devices" command shows your device in the output. Make sure you use a usb 2.0 port in case of compatibility issues and the cable that came with the phone if possible.
Click to expand...
Click to collapse
I used another laptop. Running the suggested RUU again resulted in the same 131 error. I ran as admin and did an md5 check. I'd say the other RUU's will also result in an error again...
H2Oxide said:
I used another laptop. Running the suggested RUU again resulted in the same 131 error. I ran as admin and did an md5 check. I'd say the other RUU's will also result in an error again...
Click to expand...
Click to collapse
Did some digging.
Error 155 - usually wrong recovery.img /wrong boot.img
Error 140 - wrong bootloader / bootloader unlocked
Error 131 - wrong RUU for your device
So, if one is giving you the 155 error then try with the stock recovery and do the RUU.
The phone does say relocked in bootloader right? Try doing fastboot oem lock again and run the RUU that gave you the 155 error.
Wow, that still didn't work.
So I flashed stock recovery and relocked the bootloader. Then I tried three RUU's, both the H3G RUU's and the HTC Europe RUU mentoined before. The H3G's ended up in a 155 error, the HTC Europe in a 131.
So, still no succes. This is getting annoying, right... ? Any other suggestions besides flushing the One S down the toilet?
Regards.
H2Oxide said:
Wow, that still didn't work.
So I flashed stock recovery and relocked the bootloader. Then I tried three RUU's, both the H3G RUU's and the HTC Europe RUU mentoined before. The H3G's ended up in a 155 error, the HTC Europe in a 131.
So, still no succes. This is getting annoying, right... ? Any other suggestions besides flushing the One S down the toilet?
Regards.
Click to expand...
Click to collapse
Im at a loss man. At this point I would email HTC with the getvar all info and see what they say and which RUU they give you to try. If nothing else itll help narrow down exactly what model phone it is.
pyrocide said:
Im at a loss man. At this point I would email HTC with the getvar all info and see what they say and which RUU they give you to try. If nothing else itll help narrow down exactly what model phone it is.
Click to expand...
Click to collapse
Just a thought. Since the 155 error could point to both a wrong recovery.img or a wrong boot.img, I could try flashing another (stock) boot.img. Maybe the custom rom's boot.img is in the way. So what boot.img would I need?
So I did that. I extracted the boot.img from de H3G RUU and flashed it. I also extracted the recovery and flashed that. I then tried different scenario's with the H3G, the HTC Europe and the O2 UK RUU's. Non worked. The H3G ended up in 155, the others in 131.
Anyone else any ideas on this besides emailing HTC?
H2Oxide said:
Just a thought. Since the 155 error could point to both a wrong recovery.img or a wrong boot.img, I could try flashing another (stock) boot.img. Maybe the custom rom's boot.img is in the way. So what boot.img would I need?
Click to expand...
Click to collapse
You could try to decompile the 155 error exe and fastboot flash boot boot.img but I am very nervous that might screw something up. I still suggest contacting HTC directly to have their input on what exactly RUU is needed and if you do have the right one, why it is not working.
Code:
<T133845><DEBUG><OUT>FAILED (remote: 44 hboot version check fail)</OUT>
Got the line above out the RUU log files. This is the 155 error RUU.
This raises two question:
Is it possible to get the expected hboot version number out the decompiled RUU (decompiled = the stuff placed in user/temp)?
Is it possible to down/upgrade hboot with any of the hboot versions posted here or would I run the risk of softbricking my One S then?
Don't flash any of that hboots. You will brick.
Just try to s-off, follow facepalm method in dev forum.
After that you can flash any ruu.
Sent from my HTC One S using Tapatalk
Thought I would try to upgrade Android from 2.3.5 to 4.0. HTC said it would work...
I've now got it stuck, though and can't move on. I do not own a Windows computer (I'm on Ubuntu).
What I did
I unlocked the phone using HTC's website tools. It uses adb, and you have to send some key to them and they generate an unlock code for you which you then do: fastboot flash unlocktoken Unlock_code.bin
I downloaded the RUU (RUU_SAGA_ICS_35_S_HTC_EU_14.01.401.2_20.76.30.0835_3831.19.00.110_275068) from HTC.
Try 1: OpenRUU
I extracted the rom.zip file by using Wine, then searching on rom.zip. I moved it to ~/rom.zip
I then tried running the OpenRUU scripts which failed on attempting to flash (and failed on the automatic reflash attemtp, too):
sending 'zip' (410735 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOzip header checking...
INFOzip info parsing...
FAILED (remote: 99 unknown fail)
Try2: using hboot
I then tried with the hboot script. This is not for the "desire S" and has the wrong code in for the renamed rom.zip file. I then tried manually putting rom.zip, renamed as PG88IMG.zip into the root of the SD card as clearly summarised at (1)
I booted up into fastboot and the phone opened the zip file but then said "Wrong zipped image!".
Try3: using WinXP in VirtualBox
I then tried to run the RUU exe file in an XP VirtualBox VM. To do this I enabled USB devices for the phone (i.e. added filters for it both in fastboot and android modes), installed the stuff (HTC Sync) and tried running the RUU file.
It keeps saying "error 170 usb connection error". I've tried with the phone turned on (normally) and plugged in via USB, in charge only, Disk Drive and in USB debugging modes. I've also tried with the phone in fastboot mode. I always get this error.
...disable VirtualBox's USB2.0 support
Then it's able to connect to the phone. It ran all the way through the update process except that (a) there was never a progress indicator on the phone itself, (b) at the end it gave an 155 "image error". The recovery process then didn't really relate to anything I could see on the phone. The phone is again back in a2.3.5, so at least not bricked.
Trying to re-lock bootloader...
Then I thought that maybe the bootloader should be locked again (step 11 at (2)) - I had skipped this step before because I thought "I've just UNlocked it, why would I now want to RElock it?". But this won't work either! In fastboot mode, from a terminal, I type
Code:
$ fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (Protocol error))
then the phone reboots itself, and it still shows unlocked. My fastboot screen (in case it's useful) says:
Code:
*** UNLOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot
Aug 22 20111, 15:22:13
HBOOT
Can anybody help?!
Links: (1), (2) : see pastebin dot com slash 1wKTF8Am (I am not allowed to post links here)
Rename rom.zip to PG88IMG.zip (not .jpg) then put on the root of ur sdcard (not in any folder) then boot into bootloader, it should find it
jmcclue said:
Rename rom.zip to PG88IMG.zip (not .jpg)
Click to expand...
Click to collapse
Doh! my bad - I had of course named it .zip not .jpg. (I have edited the post since). It WAS found by the phone, but error-ed after opening it, as described.
I flashed my RUU on Linux simply by doing:
Code:
fastboot oem lock
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip YOURRUUZIP.zip
fastboot flash zip YOURRUUZIP.zip
fastboot reboot
(yes, you flash it twice - it asks you 'please flush[sic] image again immediately' because it's upgrading your hboot)
obviously, replace YOURRUUZIP.zip with the zip file you extracted (e.g. PG88IMG.zip)
From the looks of your errors, though, it looks like your zip is simply corrupt...?
shinyblue said:
Doh! my bad - I had of course named it .zip not .jpg. (I have edited the post since). It WAS found by the phone, but error-ed after opening it, as described.
Click to expand...
Click to collapse
What error exactly? What does it say?
Aquous said:
I flashed my RUU on Linux simply by doing:
Code:
fastboot oem lock
Click to expand...
Click to collapse
As you'll see above - I can't do this, it errors about protocols and reboots the phone immediately!
Aquous said:
From the looks of your errors, though, it looks like your zip is simply corrupt...?
Click to expand...
Click to collapse
Could be but I don't think so. I've extracted it twice, once under Windows and once under Wine and the md5s are the same. I have no way of testing the integrity of the file I downloaded since htc don't apparently provide any hashes, but I would think that the .exe file probably checks its own integrity before running.
Thanks anyway! it looks like I need to re-lock it as a first step, maybe.
jmcclue said:
What error exactly? What does it say?
Click to expand...
Click to collapse
As posted: "Wrong zipped image!". Here's an (awful!) screenshot: (new members aren't allowed images...) i.imgur.com JqsG71r.png
shinyblue said:
As posted: "Wrong zipped image!". Here's an (awful!) screenshot: (new members aren't allowed images...) i.imgur.com JqsG71r.png
Click to expand...
Click to collapse
and is the PG88IMG.zip on the root of ur sdcard? im guessing not coz that green writing comes up every time u enter bootloader. make sure the PG88IMG.zip is NOT inside a folder
EDIT: heres a wee guide my mate wrote, its for the htc desire but its the exact same method.
PG88IMG Method
jmcclue said:
and is the PG88IMG.zip on the root of ur sdcard?
Click to expand...
Click to collapse
Yep. And the phone reads it all (takes it about 3 minutes to open, with the little vertical progress bar), then gives that error. The error goes away fast, so I had to make a video and freeze frame to get that picture.
shinyblue said:
Yep. And the phone reads it all (takes it about 3 minutes to open, with the little vertical progress bar), then gives that error. The error goes away fast, so I had to make a video and freeze frame to get that picture.
Click to expand...
Click to collapse
Oh rite. Must be corrupt download id say, coz it should work. When u downloaded the ruu, was there a md5 next to the download? If so, check it, make sure it matched, if not then try re download the ruu and try again.
Good suggestion. Just done that and the md5s are the same. It's
RUU_SAGA_ICS_35_S_HTC_EU_14.01.401.2_20.76.30.0835_3831.19.00.110_275068.zip
from htcdev site.
shinyblue said:
Good suggestion. Just done that and the md5s are the same. It's
RUU_SAGA_ICS_35_S_HTC_EU_14.01.401.2_20.76.30.0835_3831.19.00.110_275068.zip
from htcdev site.
Click to expand...
Click to collapse
Hmm strange one. I have that ruu on my laptop so il upload the PG88IMG tonight, i know it works coz i already used it. Only thing i can think why its not working is maybe something to do with taking the rom.zip from the ruu using ubuntu, i got no idea why tho.
jmcclue said:
Hmm strange one. I have that ruu on my laptop so il upload the PG88IMG tonight, i know it works coz i already used it. Only thing i can think why its not working is maybe something to do with taking the rom.zip from the ruu using ubuntu, i got no idea why tho.
Click to expand...
Click to collapse
u can't use auto install from sdcard with s-on, u can flash ruu by using fastboot commands
turekk said:
u can't use auto install from sdcard with s-on, u can flash ruu by using fastboot commands
Click to expand...
Click to collapse
Haha what a tit i am.
I know that u need to be s-off, cant believe i forgot, what a noob. I even made 16 hboots for the desire and 4ext recovery this way. Hope thats the last noobie moment for the year :sly:
shinyblue said:
As you'll see above - I can't do this, it errors about protocols and reboots the phone immediately!
Click to expand...
Click to collapse
That's probably because you're trying to run this through VirtualBox - does this also happen if you use adb from within Ubuntu rather than putting VirtualBox between your OS and your phone for no reason?
Aquous said:
That's probably because you're trying to run this through VirtualBox - does this also happen if you use adb from within Ubuntu rather than putting VirtualBox between your OS and your phone for no reason?
Click to expand...
Click to collapse
Maybe, but I think VirtualBox was working fine (e.g. HTC Sync worked).
As for "for no reason", I have read that the executable does quite a bit of stuff in terms of resetting various low level bits, and of course, being an HTC, there are hundreds of flash options, not just the usual handful.
I have been in touch with HTC directly (they told me initially the 4.0 upgrade was available), but they now say that this won't work with my phone.
I believe that the update is not accepted during the normal means because it is the WWE not the UK edition, and therefore the CID/MID do not match and are getting rejected because of S-ON.
Thing is, I don't want to risk bricking the phone by trying to get S-OFF and forcing the update because handsets are expensive! I've given up on this project for now...
Thanks to all for the help and advice.
shinyblue said:
As for "for no reason", I have read that the executable does quite a bit of stuff in terms of resetting various low level bits, and of course, being an HTC, there are hundreds of flash options, not just the usual handful.
Click to expand...
Click to collapse
Nope, all it does is this:
Code:
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip YOURRUUZIP.zip
fastboot flash zip YOURRUUZIP.zip
fastboot reboot
This is what I did with my phone (I never ran the RUU) and it updated to ICS just fine.
I believe that the update is not accepted during the normal means because it is the WWE not the UK edition, and therefore the CID/MID do not match and are getting rejected because of S-ON.
Click to expand...
Click to collapse
My phone wasn't WWE either and that was no problem for me.
Aquous said:
This is what I did with my phone (I never ran the RUU) and it updated to ICS just fine.
My phone wasn't WWE either and that was no problem for me.
Click to expand...
Click to collapse
Was yours a Desire S? I was going on this article: http://android-revolution-hd.blogspot.co.uk/2013/06/do-we-really-need-s-off.html
shinyblue said:
Was yours a Desire S? I was going on this article: http://android-revolution-hd.blogspot.co.uk/2013/06/do-we-really-need-s-off.html
Click to expand...
Click to collapse
Yeah it was a DS. The article you link to even mentions that flashing a WWE RUU should always be possible: 'Everyone can de-brand his device easily by flashing a stock system image' (although, that sentence continues, that will make you unable to receive carrier OTAs, but that doesn't matter for our device)
Can I confirm that
Aquous said:
Code:
fastboot flash zip YOURRUUZIP.zip
Click to expand...
Click to collapse
means the whole RUU.zip as downloaded from HTC, or the rom.zip as extracted from running the .exe file within the downloaded RUU?
And also, http://www.htc1guru.com/2013/09/new-ruu-zips-posted/ says "You still need to have the proper CID for the RUU. You can run the RUU.zip with super CID, but you will have to lock your bootloader first."
AFAICS the RUU I have downloaded has a different CID so won't work. Also my bootloader is unlocked (and the oem lock command fails, as mentioned above). (And I'm S-ON.)