Database Info

Can't run RUU on Sensation - "Customer ID Error"

Hi all - yet more problems, so few answers..
I was on ARHD but it sucked for me. So I wanted to revert to stock. But the RUU wouldn't run, so on another member's advice, I flashed InsertCoin and have just tried to run the RUU again.
And it ran, but then stopped saying it couldn't update and I've got a "Customer ID Error". I've no idea what this means or what I can do.
Please? Anyone?
s

schnidex said:
Hi all - yet more problems, so few answers..
I was on ARHD but it sucked for me. So I wanted to revert to stock. But the RUU wouldn't run, so on another member's advice, I flashed InsertCoin and have just tried to run the RUU again.
And it ran, but then stopped saying it couldn't update and I've got a "Customer ID Error". I've no idea what this means or what I can do.
Please? Anyone?
s
Click to expand...
Click to collapse
Appreciate to post the picture when your phone at Hboot or Fastboot state (?) is phone s-off and what you are doing to phone before running RUU.

Is your unit Super CID? You need this to flash RUU

paulmor said:
Is your unit Super CID? You need this to flash RUU
Click to expand...
Click to collapse
I don't know - can you tell me how to find out? Honestly, I've really had enough of how complicated this has to get - I just want to restore root and sell the thing. Any help would be much, much appreciated.

Are you using the correct RUU for your device, eg. Asian RUU for Asian device etc?
I doubt that your device is on SuperCID as having that will negate the Customer ID errors

Blodia said:
Are you using the correct RUU for your device, eg. Asian RUU for Asian device etc?
I doubt that your device is on SuperCID as having that will negate the Customer ID errors
Click to expand...
Click to collapse
Reboot into the Bootloader and then select Fastboot-USB. Run the RUU again and it will work with no issues.

Blodia said:
Are you using the correct RUU for your device, eg. Asian RUU for Asian device etc?
I doubt that your device is on SuperCID as having that will negate the Customer ID errors
Click to expand...
Click to collapse
Definitely - but I will try the dr's solution and get back to you guys if I have any more problems.
Thanks for your help.

schnidex said:
I don't know - can you tell me how to find out? Honestly, I've really had enough of how complicated this has to get - I just want to restore root and sell the thing. Any help would be much, much appreciated.
Click to expand...
Click to collapse
It's not complicated, just that you need to do the things in order.
If you want to check the CID, look at: http://forum.xda-developers.com/showthread.php?t=1192300
Note though that you'll need ADB installed and working.
Step 4. is about the CID, there are steps to check it and write a different one.
9. enter the command "fastboot reboot-bootloader (Wait for it to reboot the bootloader)
10. enter the command "fastboot getvar cid" [it should confirm your CID is 11111111]

dr9722 said:
Reboot into the Bootloader and then select Fastboot-USB. Run the RUU again and it will work with no issues.
Click to expand...
Click to collapse
Thanks again for this, but it didn't work unfortunately..

However..
gol_n_dal said:
It's not complicated, just that you need to do the things in order.
If you want to check the CID, look at: http://forum.xda-developers.com/showthread.php?t=1192300
Note though that you'll need ADB installed and working.
Step 4. is about the CID, there are steps to check it and write a different one.
9. enter the command "fastboot reboot-bootloader (Wait for it to reboot the bootloader)
10. enter the command "fastboot getvar cid" [it should confirm your CID is 11111111]
Click to expand...
Click to collapse
..this did! Thank you for this - the RUU is installing now!

Possible to change "modelid" of HTC One S?

Hi guys! I have T-Mobile US version of One S and have changed to SuperCID and have the latest rom from Euro RUU 2.31. The model of my phone is different form european, so after checking I found the model to be PJ40110. I have first tried to make CID as HTC__001, but it wouldn't install RUU saying that model id doesn't match. Then I found txt file and saw that it needs a different model id, so this is when SuperCID came into play. Is there a way to change 'modelid' of the phone?
Thanks in advance!

In the build.prop
T-MobileUS HTC One S

fastboot write mid?
Sent from pixels to more pixels

usaff22 said:
fastboot write mid?
Sent from pixels to more pixels
Click to expand...
Click to collapse
I have tried the following command: fastboot oem writemid PJ4010000, the is the midel id I need to change to, but I get "Info[ERR] Command Error!!!" I know that this command is correct and looks like I would have to wait for S-OFF to make it work.

Charkatak said:
I have tried the following command: fastboot oem writemid PJ4010000, the is the midel id I need to change to, but I get "Info[ERR] Command Error!!!" I know that this command is correct and looks like I would have to wait for S-OFF to make it work.
Click to expand...
Click to collapse
Yes, I think it is only possible with the Engineering HBOOT, with S-OFF.
I don't think it is possible with HTCDev. You'll have to wait until we get S-OFF.
Sent from pixels to more pixels

usaff22 said:
Yes, I think it is only possible with the Engineering HBOOT, with S-OFF.
I don't think it is possible with HTCDev. You'll have to wait until we get S-OFF.
Sent from pixels to more pixels
Click to expand...
Click to collapse
- Now we have SOFF. What I did was I debranded the TMOUS HOS to WWE EU and flashed ICS rom.zip from RUU. All was fine till now and I have SOFF, relocked BL etc.
- Moreover, I do get notification for JB OTA and it also completes the download. However, it doesn't install as my MID is PJ4011000. EU RUU expects it to be PJ4010000.
- On searching, I found this thread. I tried issuing: sudo ./fastboot oem writemid PJ4010000 as well as sudo ./fastboot oem modelid PJ4010000. However, it still gives error:
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.012s]
finished. total time: 0.012s
- I have Ubuntu 12.04 on 64-bit 8 core machine (not sure if this is of any help but still thought of mentioning) which I am using for the playing with my HOS.
I guess now I need to find out how to change MID with SOFF.
Edit: I checked my build.prop and it has MID PJ4010000. So this MID is also stored somewhere apart from build.prop. Damn it !!

chota_shivaji said:
- Now we have SOFF. What I did was I debranded the TMOUS HOS to WWE EU and flashed ICS rom.zip from RUU. All was fine till now and I have SOFF, relocked BL etc.
- Moreover, I do get notification for JB OTA and it also completes the download. However, it doesn't install as my MID is PJ4011000. EU RUU expects it to be PJ4010000.
- On searching, I found this thread. I tried issuing: sudo ./fastboot oem writemid PJ4010000 as well as sudo ./fastboot oem modelid PJ4010000. However, it still gives error:
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.012s]
finished. total time: 0.012s
- I have Ubuntu 12.04 on 64-bit 8 core machine (not sure if this is of any help but still thought of mentioning) which I am using for the playing with my HOS.
I guess now I need to find out how to change MID with SOFF.
Click to expand...
Click to collapse
You need an Engineering HBOOT which supports those commands

usaff22 said:
You need an Engineering HBOOT which supports those commands
Click to expand...
Click to collapse
Thanks for the update.
I guess I am now *really* stuck on WWE ICS (for stock). Of course, I can flash any ROMs I want since I am SOFF, so not a big deal. I must say WWE ICS ROM is better than TMOUS with their bloat (which is anyway not useful to me at all since I am out of USA now).

chota_shivaji said:
Thanks for the update.
I guess I am now *really* stuck on WWE ICS (for stock). Of course, I can flash any ROMs I want since I am SOFF, so not a big deal. I must say WWE ICS ROM is better than TMOUS with their bloat (which is anyway not useful to me at all since I am out of USA now).
Click to expand...
Click to collapse
I'd bet money you could dd the correct partition from the phone change it with a hex editor and dd it back to the phone. I've done it with a handful of things and never had a problem.

I decrypted the zip and changed it to the US model. Run the RUU and before letting it install it to your phone, open up the temp directory and replace my zip with the 'rom.zip' in the temp folder. I will upload mine after I am home
Sent from my HTC One S using xda app-developers app

dc211 said:
I'd bet money you could dd the correct partition from the phone change it with a hex editor and dd it back to the phone. I've done it with a handful of things and never had a problem.
Click to expand...
Click to collapse
Hey thanks for the update. I agree with you on this point. Do you know what partition holds the MID in HOS?
Sent from my HTC One S using xda app-developers app
---------- Post added at 07:19 AM ---------- Previous post was at 07:16 AM ----------
leald said:
I decrypted the zip and changed it to the US model. Run the RUU and before letting it install it to your phone, open up the temp directory and replace my zip with the 'rom.zip' in the temp folder. I will upload mine after I am home
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Fantastic !! Would you mind sharing how to decrypt the zip? In any case awaiting for your rom.zip which has TMOUS MID in android_info.txt extracted EU JB RUU and decrypted .
Sent from my HTC One S using xda app-developers app

chota_shivaji said:
Hey thanks for the update. I agree with you on this point. Do you know what partition holds the MID in HOS?
Sent from my HTC One S using xda app-developers app
---------- Post added at 07:19 AM ---------- Previous post was at 07:16 AM ----------
Fantastic !! Would you mind sharing how to decrypt the zip? In any case awaiting for your rom.zip which has TMOUS MID in android_info.txt extracted EU JB RUU and decrypted .
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Ill try and upload it tonight but it might not be up until tomorrow morning because of its side. And actually you will have to "fastboot oem writecid HTC__001" asi already repackaged the zip before thinking I would have to add a tmobile cid, sorry
Sent from my HTC One S using xda app-developers app

leald said:
Ill try and upload it tonight but it might not be up until tomorrow morning because of its side. And actually you will have to "fastboot oem writecid HTC__001" asi already repackaged the zip before thinking I would have to add a tmobile cid, sorry
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
- I think you misunderstood me.
- My HOS is de-branded and has CID = HTC__001 from TMOUS & SOFF. I am on 2.31 EU stock ICS. The only hurdle now for me to use JB OTA/RUU/rom.zip is MID.
- So, what I am looking for is: rom.zip from JB EU RUU with android_info.txt changed for TMOUS MID and decrypted. Once I get that, I can use via RUU mode of fastboot.

chota_shivaji said:
- I think you misunderstood me.
- My HOS is de-branded and has CID = HTC__001 from TMOUS & SOFF. I am on 2.31 EU stock ICS. The only hurdle now for me to use JB OTA/RUU/rom.zip is MID.
- So, what I am looking for is: rom.zip from JB EU RUU with android_info.txt changed for EU MID and decrypted. Once I get that, I can use via RUU mode of fastboot.
Click to expand...
Click to collapse
- I found this thread http://forum.xda-developers.com/showthread.php?t=2084470 which has a tool to decrypt the JB RUU. It uses the libcrypt on Linux host machine to decrypt the rom.zip. It looks like for many phones JB RUU is encrypted.
- The tool mentions that it supports HTC One S (ville).
- I tried this tool to decrypt the rom.zip from JB EU RUU. It runs fine and I am able to get the decrypted rom.zip with MID = TMOUS in android_info.txt. However, I have not flashed it yet as I am not brave enough to face a brick (even though my signature mentions JB, I am still on ICS).
Can someone try this tool and flash as well? It needs Linux machine to compile and generate the binary to be useful.
Please note: I am not responsible if you brick your HOS due to this. You have been warned, do not attempt if you don't understand what you are doing.

Charkatak said:
Hi guys! I have T-Mobile US version of One S and have changed to SuperCID and have the latest rom from Euro RUU 2.31. The model of my phone is different form european, so after checking I found the model to be PJ40110. I have first tried to make CID as HTC__001, but it wouldn't install RUU saying that model id doesn't match. Then I found txt file and saw that it needs a different model id, so this is when SuperCID came into play. Is there a way to change 'modelid' of the phone?
Thanks in advance!
Click to expand...
Click to collapse
I think you should put the breaks on your project. Why exactly are you trying to change your MID anyways. If it's to get a RUU to run I'd suggest that you not go forward with your plan. There is no real reason to run an RUU if you have S-off other then to "start over" on a clean install of everything.
You can flash any: rom, firmware, radio, and hboot you choose so why change the model ID to run a RUU. Which is something I've NEVER seen anyone do in this forum to run a RUU. What's the full name of the RUU you want to run?
It looks like you're doing all this just to get to the official Jelly Bean release is that your goal? If so why not just flash it without using a RUU?

If so why not just flash it without using a RUU?[/QUOTE]
because the JB zip won't flash in a Tmous device because of different model id..

cyriantherockstar said:
because the JB zip won't flash in a Tmous device because of different model id..
Click to expand...
Click to collapse
Why not just install the rom that someone made compatible with TWRP then flash the firmware separately?

you can hex mod the mmcblk0p6 partition. it has a string pj0011000 in there somewhere as well as a spaced out string p j 0 0 1 1 0 0 0. if you edit those out, you should be fine to flash the ruu. first you need to supercid and s off though.

chota_shivaji said:
- I found this thread http://forum.xda-developers.com/showthread.php?t=2084470 which has a tool to decrypt the JB RUU. It uses the libcrypt on Linux host machine to decrypt the rom.zip. It looks like for many phones JB RUU is encrypted.
- The tool mentions that it supports HTC One S (ville).
- I tried this tool to decrypt the rom.zip from JB EU RUU. It runs fine and I am able to get the decrypted rom.zip with MID = TMOUS in android_info.txt. However, I have not flashed it yet as I am not brave enough to face a brick (even though my signature mentions JB, I am still on ICS).
Can someone try this tool and flash as well? It needs Linux machine to compile and generate the binary to be useful.
Please note: I am not responsible if you brick your HOS due to this. You have been warned, do not attempt if you don't understand what you are doing.
Click to expand...
Click to collapse
correct me if i am wrong here, but why dont you just take the rom.zip from the ruu, decrypt it and change the androidinfo.txt and change the model id to say the one you need. then rezip it with winrar or 7zip and feed it to the hboot... you are s-off so it shouldnt ask any questions regarding the signiture of the zip file, but i am not sure about the compression.

untrueparadox said:
you can hex mod the mmcblk0p6 partition. it has a string pj0011000 in there somewhere as well as a spaced out string p j 0 0 1 1 0 0 0. if you edit those out, you should be fine to flash the ruu. first you need to supercid and s off though.
Click to expand...
Click to collapse
Has anyone had success doing this?

[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

[Q] Where to Request for RUU's

I have to request for an RUU which is missing. Who can be approached in this regard?

Please, search before making questions. This has been asked thousands times.
link

nor-ric said:
Please, search before making questions. This has been asked thousands times.
link
Click to expand...
Click to collapse
Sorry for that but I think My question is incomplete.
The RUU is missing for JellyBean BM_001 (Bell Mobility). It has only got OTA and no RUU. I direly need it.

RUU VILLE o2_001 update problem
Current software (ICS 2.38.206.2) My problem is that after downloading the phone indicated JB (3.16.401.8) update software, I get the following error message:
Changing system version.
We determined that your phone is running a modified version. We can not update your phone so restore it to the original version for your protection.
Can you help me?
To my knowledge it was not modified by the device.
I'm waiting for their response.
Best regards.

eperjesi76 said:
Current software (ICS 2.38.206.2) My problem is that after downloading the phone indicated JB (3.16.401.8) update software, I get the following error message:
Changing system version.
We determined that your phone is running a modified version. We can not update your phone so restore it to the original version for your protection.
Can you help me?
To my knowledge it was not modified by the device.
I'm waiting for their response.
Best regards.
Click to expand...
Click to collapse
Well based on my reading here, I can say the following can be the reasons:
- Unlocked bootloader
- Phone Rooted
- Any of the bloatware removed/changed in the phone which came pre-installed.

khan.orak said:
Well based on my reading here, I can say the following can be the reasons:
- Unlocked bootloader
- Phone Rooted
- Any of the bloatware removed/changed in the phone which came pre-installed.
Click to expand...
Click to collapse
Bootloader mode, the display shows:
TAMPERED
LOCKED
VLE PVT SHIP S-ON RL
HBOOT-1.14.0002
50.02.16-RADIO-1.08es
OPEN DSP v29.1.0.45.0622
root nothing.
It find out something?
According to the CID number cidgetter HTC_032 but O2_001 is mentioned below.
The phone O2 and English, but independent.
Well?

eperjesi76 said:
Bootloader mode, the display shows:
TAMPERED
LOCKED
VLE PVT SHIP S-ON RL
HBOOT-1.14.0002
50.02.16-RADIO-1.08es
OPEN DSP v29.1.0.45.0622
It find out something?
According to the CID number cidgetter HTC_032 but O2_001 is mentioned below.
The phone O2 and English, but independent.
Well?
Click to expand...
Click to collapse
So it says tampered. That's why it isn't updating OTA.
It means either you have installed a custom recovery or you have rooted the phone.
The CID. well I'm not quite sure about that. I have little expertise in that area.
Where is O2_001 mentioned?

also depatib
khan.orak said:
So it says tampered. That's why it isn't updating OTA.
It means either you have installed a custom recovery or you have rooted the phone.
The CID. well I'm not quite sure about that. I have little expertise in that area.
Where is O2_001 mentioned?
Click to expand...
Click to collapse
top of cidgetter program writes htc_032
the following:
ro.aa.cidlist O2_001
ro.aa.maincid O2_001
ro.aa.project Ville_U_ICS_S
ro.build.fingerprint o2_uk/ville/ville/4.0.4
ro.carrier HTC EastEurope
ro.com HTC_032
ro.cwkey O2 001
etc. ..

eperjesi76 said:
top of cidgetter program writes htc_032
the following:
ro.aa.cidlist O2_001
ro.aa.maincid O2_001
ro.aa.project Ville_U_ICS_S
ro.build.fingerprint o2_uk/ville/ville/4.0.4
ro.carrier HTC EastEurope
ro.com HTC_032
ro.cwkey O2 001
etc. ..
Click to expand...
Click to collapse
No it's just the one at top marked RED. and it must be O2_001. So you have this CID. Get an RUU for this one.

khan.orak said:
No it's just the one at top marked RED. and it must be O2_001. So you have this CID. Get an RUU for this one.
Click to expand...
Click to collapse
Many RUU was tried, but each error (bootstrap error 140, 159 image error 155 unknown error ...) refers.
I tried EUREPO Cid_032 ruins but also not good.
The O2 ruins region code is not good.

eperjesi76 said:
Many RUU was tried, but each error (bootstrap error 140, 159 image error 155 unknown error ...) refers.
I tried EUREPO Cid_032 ruins but also not good.
The O2 ruins region code is not good.
Click to expand...
Click to collapse
well I am PMing you with a link. Try to follow that guide. and use the O2 RUU not any other.

khan.orak said:
well I am PMing you with a link. Try to follow that guide. and use the O2 RUU not any other.
Click to expand...
Click to collapse
I look forward
---------- Post added at 04:59 PM ---------- Previous post was at 04:26 PM ----------
eperjesi76 said:
I look forward
Click to expand...
Click to collapse
Unfortunately, I can not translate clearly.
The SDK is 500MB and windows command line I do not understand where you are

khan.orak said:
well I am PMing you with a link. Try to follow that guide. and use the O2 RUU not any other.
Click to expand...
Click to collapse
Sorry simply can not do anything.
The fastboot program does nothing, has no effect on the phone.

eperjesi76 said:
Sorry simply can not do anything.
The fastboot program does nothing, has no effect on the phone.
Click to expand...
Click to collapse
This is the method. You may want to find other guides on how to flash stock ROM. ADB and FastBoot are necessary and nothing is possible without it.
Sent from my Nexus 7 using Tapatalk HD

khan.orak said:
This is the method. You may want to find other guides on how to flash stock ROM. ADB and FastBoot are necessary and nothing is possible without it.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I do not get the phone to fastboot USB connection is ok.
with plug.
The machine is not doing anything with the phone.

eperjesi76 said:
I do not get the phone to fastboot USB connection is ok.
with plug.
The machine is not doing anything with the phone.
Click to expand...
Click to collapse
You can also fastboot by All in one tool of Hasoon.
Oprn the tool, connect the phone with USB DEBUGGING ON, Press boot to Bootloader in the tool and follow instructions.
Sent from my Nexus 7 using Tapatalk HD

khan.orak said:
You can also fastboot by All in one tool of Hasoon.
Oprn the tool, connect the phone with USB DEBUGGING ON, Press boot to Bootloader in the tool and follow instructions.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I used TWRP Recovery, I thought it would be easier. More rom.zip tried, but each one says the recovery that:
This operation may install Incompatible software and render your device unusable.
The Cid HTC_032 or O2_001 cause such a problem if you do not have the correct rom?

Watch it.
A cid is always 8 digits as far as i have seen.
Watch here also. http://forum.xda-developers.com/showthread.php?t=2139447
It probaly wont install because of custom recovery/ or incorrect cid
Check cid in fastboot to be sure.
Command: fastboot getvar all
If you unlock again. It might format the device again. (needed to install stock recovery)
Verstuurd van mijn HTC One S met Tapatalk

[Q] Bootloop and can't find the RUU file!!

Hi everyone
I have this htc sensation it is stack in bootllop and I don't know why!! anyway I tried to fix it with a RUU file but can't find the correct file to my phone.
I belive it is a T-Mobile phone from NL and here the info from my bootloader
**** LOCKED ****
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
eMMC-boot
jan 13 2012,17:33:34
Click to expand...
Click to collapse
also I got this by cheking my version and CID
fastboot getvar cid
cid: T-MOB003
finished. total time: 0.002s
Click to expand...
Click to collapse
fastboot getvar version-main
version-main: 3.33.114.51
finished. total time: 0.003s
Click to expand...
Click to collapse
If anyone can help me with the link to the correct RUU file it would be nice
thanks guys

if you still can't find your RUU...you can try another RUU (different CID) that have a same or higher version than yours...but ofcourse you must modified first android-info.txt in that rom.zip file..you can follow completed guide from here.. especially read at step 4. Flashing RUU manually
or alternative way..you must make a goldcard..
hope this help...

JJeamy said:
if you still can't find your RUU...you can try another RUU (different CID) that have a same or higher version than yours...but ofcourse you must modified first android-info.txt in that rom.zip file..you can follow completed guide from here.. especially read at step 4. Flashing RUU manually
or alternative way..you must make a goldcard..
hope this help...
Click to expand...
Click to collapse
thanks but how to modify the android-info.txt I add my CID like this :
modelid: PG5813000cidnum: T-MOB003mainver: 3.33.709.6hbootpreupdate:12DelCache:1
Click to expand...
Click to collapse
it does not flash

Topol-Ms said:
thanks but how to modify the android-info.txt I add my CID like this :
it does not flash
Click to expand...
Click to collapse
yap..that's correct...but..what's your MID anyway..?
how do you to change that...did you already extracted the rom.zip file then modified that android-info.txt file..?
because you don't need to extract that rom.zip (because if you extracting that file first that will broken a compiled that rom.zip)...just open it that archive then open it android-info.txt from there..then edited that file and save it
also try open it and edited that file with notepad++..
hope this help..

JJeamy said:
yap..that's correct...but..what's your MID anyway..?
how do you to change that...did you already extracted the rom.zip file then modified that android-info.txt file..?
because you don't need to extract that rom.zip (because if you extracting that file first that will broken a compiled that rom.zip)...just open it that archive then open it android-info.txt from there..then edited that file and save it
also try open it and edited that file with notepad++..
hope this help..
Click to expand...
Click to collapse
sry what what you mean with MID? and the winrare says the file is curopted I can't cahnge it

Topol-Ms said:
sry what what you mean with MID? and the winrare says the file is curopted I can't cahnge it
Click to expand...
Click to collapse
MID = model id ...to know that just using command "fastboot getvar mid" or "fastboot getvar all"
just try open it that archive with Windows Archive Manager (Windows built in ZIP program), then copied android-info.txt to outside (don't extracted) then edited with nopad++ then save it...then deleted original android-info.txt from that archive then drag and drop the new one to that archive..

JJeamy said:
MID = model id ...to know that just using command "fastboot getvar mid" or "fastboot getvar all"
just try open it that archive with Windows Archive Manager (Windows built in ZIP program), then copied android-info.txt to outside (don't extracted) then edited with nopad++ then save it...then deleted original android-info.txt from that archive then drag and drop the new one to that archive..
Click to expand...
Click to collapse
He's already posted it:
modelid: PG5813000cidnum: T-MOB003mainver: 3.33.709.6hbootpreupdate:12DelCache:1
Click to expand...
Click to collapse
FYI, you can't flash unsigned or missing-cid firmware without S-OFF.
Try these:
http://www.tsar3000.com/Joomla/inde...riginal-roms&catid=65:htc-downloads&Itemid=98
http://www.shipped-roms.com/index.php?category=android&model=Pyramid
Use this thread to look for an RUU. Nearly all RUUs are present on above two links. Your CID is included, so I guess an RUU should be available.

Far_SighT said:
He's already posted it:
FYI, you can't flash unsigned or missing-cid firmware without S-OFF.
Try these:
http://www.tsar3000.com/Joomla/inde...riginal-roms&catid=65:htc-downloads&Itemid=98
http://www.shipped-roms.com/index.php?category=android&model=Pyramid
Use this thread to look for an RUU. Nearly all RUUs are present on above two links. Your CID is included, so I guess an RUU should be available.
Click to expand...
Click to collapse
1. what he's already posted it is android-info.txt from ruu that he want changed it..not MID from the phone that he has..that's why i ask him to see his mid and changed it too to android-info.txt from that RUU..
thanks but how to modify the android-info.txt I add my CID like this :
modelid: PG5813000cidnum: T-MOB003mainver: 3.33.709.6hbootpreupdate:12DelCache:1
Click to expand...
Click to collapse
Click to expand...
Click to collapse
2. he can't find the right RUU for his phone...so that's why i suggest it to him to flashing another RUU and try change it cid and mid in android-info.txt from that other RUU to match with his phone..
3. you can see that i've already suggest it him to the same link thread about related RUU that you give it again to him too..
JJeamy said:
if you still can't find your RUU...you can try another RUU (different CID) that have a same or higher version than yours...but ofcourse you must modified first android-info.txt in that rom.zip file..you can follow completed guide from here.. especially read at step 4. Flashing RUU manually
hope this help...
Click to expand...
Click to collapse
4. so you're already guessing that the right RUU for his phone is available from the two link that you're give it to him above...so can you show me and posting it in here exactly the link for that RUU (i mean the correct RUU that have CID and MID that are suitable for his phone and have equal or higher version than he was had right now)..ofcourse this is for helped him..then make an more easy and a simple way to fix his sensation..
so for @Topol-Ms if that's RUU way fail..maybe you can try it a way to unlocking your bootloader first via htcdev.com.. then after that you can continued to flashing custom recovery..then flashing custom rom..
hope this help...and good luck..

JJeamy said:
1. what he's already posted it is android-info.txt from ruu that he want changed it..not MID from the phone that he has..that's why i ask him to see his mid and changed it too to android-info.txt from that RUU..
2. he can't find the right RUU for his phone...so that's why i suggest it to him to flashing another RUU and try change it cid and mid in android-info.txt from that other RUU to match with his phone..
3. you can see that i've already suggest it him to the same link thread about related RUU that you give it again to him too..
4. so you're already guessing that the right RUU for his phone is available from the two link that you're give it to him above...so can you show me and posting it in here exactly the link for that RUU (i mean the correct RUU that have CID and MID that are suitable for his phone and have equal or higher version than he was had right now)..ofcourse this is for helped him..then make an more easy and a simple way to fix his sensation..
so for @Topol-Ms if that's RUU way fail..maybe you can try it a way to unlocking your bootloader first via htcdev.com.. then after that you can continued to flashing custom recovery..then flashing custom rom..
hope this help...and good luck..
Click to expand...
Click to collapse
thanks man I tried to unlock my phone with htcdev.com everything go smooth untill I get the email with unlock_code.bin and when I try to flash it it says this :
C:\Users\Naoufel\Desktop\fastboot-win>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.151s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.157s
Click to expand...
Click to collapse
I hate this phone!!

Topol-Ms said:
thanks man I tried to unlock my phone with htcdev.com everything go smooth untill I get the email with unlock_code.bin and when I try to flash it it says this :
I hate this phone!!
Click to expand...
Click to collapse
what you choice while in the list of "select your device" to unlock in the first gate in htcdev.com..?
that you already choice "All Other Supported Models" ..?

JJeamy said:
what you choice while in the list of "select your device" to unlock in the first gate in htcdev.com..?
that you already choice "All Other Supported Models" ..?
Click to expand...
Click to collapse
I tried 3 kind of sensation phones in the list and also all other supported models but nothing everytime I get the same message

Topol-Ms said:
I tried 3 kind of sensation phones in the list and also all other supported models but nothing everytime I get the same message
Click to expand...
Click to collapse
did you already tried...i think maybe you can try it if don't..just try factory reset from bootloader first..let me know what happen..

JJeamy said:
did you already tried...i think maybe you can try it..just try factory reset from bootloader first..let me know what happen..
Click to expand...
Click to collapse
factory reset and then I unlock again?

Topol-Ms said:
factory reset and then I unlock again?
Click to expand...
Click to collapse
yap..but after factory reset...just try it to boot normal first..who knows that's will worked..
if not...just continued to flashing unlock token again..but this time just using Unlock_code.bin that you get it from selected "All Others Supported Models"

JJeamy said:
yap..but after factory reset...just try it to boot normal first..who knows that's will worked..
if not...just continued to flashing unlock token again..but this time just using Unlock_code.bin that you get it from selected "All Others Supported Models"
Click to expand...
Click to collapse
sorry dude done all nothing happen same error

Topol-Ms said:
sorry dude done all nothing happen same error
Click to expand...
Click to collapse
this is mean a factory reset way is worked and your phone is already back to normal again..?, or this mean the phone still bootlop and still can't flashing Unlock_code.bin too..?

JJeamy said:
this is mean a factory reset way is worked and your phone is already back to normal again..?
Click to expand...
Click to collapse
I don't think the factory reset was complete it doesn't take much time it was fast the phone is still in boot loop

Topol-Ms said:
I don't think the factory reset was complete it doesn't take much time it was fast the phone is still in boot loop
Click to expand...
Click to collapse
OMG...
so after that did you already tried to flashing Unlock_code.bin again..?

JJeamy said:
OMG...
so after that did you already tried to flashing Unlock_code.bin again..?
Click to expand...
Click to collapse
yes!!

Topol-Ms said:
yes!!
Click to expand...
Click to collapse
this is so weird...
because what i know...if sensation can't unlock bootloader almost all the reason is because that phone is ever get to the service center before for replacing some hardware..especially is the display hw because already broken..did you sure your sensation never replacing some hw broken before..?
sorry mate..i can't help you more than this..i think the only way is just brought your sensation to the service center..or 3rd party service center that had some kind of riff box or jtag tools that can flashing a emmc from the beginning again...