Database Info

HTC ONE S revert to stock

It's a stupid guide for noob as me...
I've spent much time reading these pages to find what i need to revert and use OTA update.
To revert stock rom, following this simple step:
1) download the ruu of your htc
http://forum.xda-developers.com/showthread.php?p=24886181#post24886181
2) run the ruu and waiting it finish
note:
if you previously don't change anything on system partition (for example you don't cancel any application in system\data whit root privileges) you can run the execute the .exe file and wait it finish.
Otherwise you must flash from recovery a stock nand backup ((for example, if you have the 153.x.x... you can download from this http://forum.xda-developers.com/showpost.php?p=24886181&postcount=18the cmw stock backup) to comeback to the originary size partition and run RUU
I'm sorry for my poor english but I hope it is clear and hope this post has not violated terms of section...

Moved To General​
Thanks for the post, but this is best off in the general section, as its not really development.​

I downloaded the 1.53 RUU and it just wouldnt work for me. I also flashed the image you provided. Coming from Virtuous. Really odd.....

The Jones said:
I downloaded the 1.53 RUU and it just wouldnt work for me. I also flashed the image you provided. Coming from Virtuous. Really odd.....
Click to expand...
Click to collapse
at the end i had got a old nand backup of untouched rom stock and after this restore and reflashed original recovery (but i think it isn't really necessary), the execution of ruu finished without problems.
I think it gets error if we have supersu too, because it modifies the file system space..

I tried that as well and the ruu refused to work. I am re downloading the ruu to aee what happens.
Sent from my HTC One S using XDA

The ruu you had downloaded is correct to me.. try to verify if your CID is present in android.txt (you must enter in temporary directory where ruu put his files, open rom.zip and verify is your CID is present..). Try this, in case you can add it.
i'm sorry for my poor english... i hope it's clear ;-)

nascio said:
The ruu you had downloaded is correct to me.. try to verify if your CID is present in android.txt (you must enter in temporary directory where ruu put his files, open rom.zip and verify is your CID is present..). Try this, in case you can add it.
i'm sorry for my poor english... i hope it's clear ;-)
Click to expand...
Click to collapse
Thanks. I did look for this and it is in there. I got the CID out of some fastboot command that I cant remember now.

The Jones said:
Thanks. I did look for this and it is in there. I got the CID out of some fastboot command that I cant remember now.
Click to expand...
Click to collapse
fastboot command is this: fastboot getvar cid

i need serious help!
i try evertything...i try to flash stock cmw flashable rom,flash the original recovery and try ruu....nothing....the best i can get it's after sending the update say sometingh like "invalid id client"....
i search CID and is VODAP102...someone can help me to restore to stock????? PLEASE!!!
and many thanks

You try to flash wrong version of RUU. I don't know if it's the case here, I do not own the device (yet )but I had a similar problem with my old incredible s. As it turned out RUU didn't match my MODEL-ID. Every htc-device has its model-id, but for some reason there is always released a batch with different model-id (So it was with Incredible S provided by Bell Canada. While almost the whole world enjoyed PG3213000, phones from Bell had model ID- PG3212000, and they needed their own special RUU.)
I'm from Europe but used XTC-clip to unlock bootloader and during this procedure I accidentally changed model-id from PG3213000 too PG3212000. That's why I was unable to flash any WWE RUU ( error [130] model ID error). Once I re-changed model-id (with the same xtc clip) my all problems were gone.

Everything that I need now is RUU 1.78.401.2.

gimmyxx said:
i need serious help!
i try evertything...i try to flash stock cmw flashable rom,flash the original recovery and try ruu....nothing....the best i can get it's after sending the update say sometingh like "invalid id client"....
i search CID and is VODAP102...someone can help me to restore to stock????? PLEASE!!!
and many thanks
Click to expand...
Click to collapse
I need that too.... thanks to who ever made it

chrisrudolf said:
I need that too.... thanks to who ever made it
Click to expand...
Click to collapse
you can try to add manually your CID in android.txt file inside rom.zip (in ruu temporary directory)

In ruu it didn't work, i tried it.
i hear voices in my head

[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] how to change mid from PJ4011000 to PJ4010000

Plz some one help us to change the model id .we have now s-off .some kind of fastboot command .....plz help us

aman0406 said:
Plz some one help us to change the model id .we have now s-off .some kind of fastboot command .....plz help us
Click to expand...
Click to collapse
as far as i know you can edit the mid in the build.prop

You don't need to change the MID. I already S-Off'd my phone without changing it.
Sent from my HTC VLE_U using Tapatalk 2

hasoon2000 said:
You don't need to change the MID. I already S-Off'd my phone without changing it.
Sent from my HTC VLE_U using Tapatalk 2
Click to expand...
Click to collapse
thx for reply.
. i am s-off .changed my cid to HTC__001 try to install ota of jellybean update but its says modify system cant update.getting error while installing ruu of jellybean error no 159............when is use fastboot (FASTBOOT GETVAR ALL) my mid is PJ4011000.......

aman0406 said:
thx for reply.
. i am s-off .changed my cid to HTC__001 try to install ota of jellybean update but its says modify system cant update.getting error while installing ruu of jellybean error no 159............when is use fastboot (FASTBOOT GETVAR ALL) my mid is PJ4011000.......
Click to expand...
Click to collapse
As far as I know, you need eng hboot to change mid. Checkout the thread about this as I don't have its link handy.
Do the following:
- download jb eu ruu
- extract Rom.zip from it
- decrypt it using tool called ruuveal
- edit android_info.txt inside it to replace the mid with pj4011000.
- flash the decrypted Rom.zip via oem ruu mode
This has worked on my hos which was tmobile us branded.
Note: if you don't understand any of the step above, please do not attempt any of them. I cannot be held responsible if you brick your phone due to these steps.
Sent from my HTC One S using xda app-developers app

No need in changing the Model ID
aman0406 said:
Plz some one help us to change the model id .we have now s-off .some kind of fastboot command .....plz help us
Click to expand...
Click to collapse
just download and replace the PJ4010000 with this one and do everything else like it says.
http://d-h.st/qVx
i know this because when i ordered my new htc one s it already had the update so i figured i would just switch the .zip that is on the forum with this one seeing how they are close to same size in mb i figured they was the same files needed...
worked just fine for me

????
williamx87 said:
just download and replace the PJ4010000 with this one and do everything else like it says.
http://d-h.st/qVx
i know this because when i ordered my new htc one s it already had the update so i figured i would just switch the .zip that is on the forum with this one seeing how they are close to same size in mb i figured they was the same files needed...
worked just fine for me
Click to expand...
Click to collapse
What to do with this zip. I
am using t mobile one s ?

aman0406 said:
What to do with this zip. I
am using t mobile one s ?
Click to expand...
Click to collapse
When you goto the forum to do the s-off u have to download the pj1000.zip. instead of downloading it use the zip I provided

williamx87 said:
When you goto the forum to do the s-off u have to download the pj1000.zip. instead of downloading it use the zip I provided
Click to expand...
Click to collapse
I am already s-off .but mid is PJ4011000.can not install jellybean ruu. 3.16.401.8 error 159

williamx87 said:
just download and replace the PJ4010000 with this one and do everything else like it says.
http://d-h.st/qVx
i know this because when i ordered my new htc one s it already had the update so i figured i would just switch the .zip that is on the forum with this one seeing how they are close to same size in mb i figured they was the same files needed...
worked just fine for me
Click to expand...
Click to collapse
I just tried to use that zip and it failed. and aborted. so i still have the same mid.

aman0406 said:
I am already s-off .but mid is PJ4011000.can not install jellybean ruu. 3.16.401.8 error 159
Click to expand...
Click to collapse
Yeah mate, please do a search for 'error 159' in this forum. You'll probably know then why it doesn't work (for your device).

How i can see what is my model ID ? There is not a such info in my build.prop.

boc11 said:
How i can see what is my model ID ? There is not a such info in my build.prop.
Click to expand...
Click to collapse
see post 4

Ok, i go to here
C:\Android\android-sdk\platform-tools>adb shell su -c "/data/local/tmp/soffbin3"
Permission denied
Click to expand...
Click to collapse
What is the problem?

I didnt want to open a new theme, so I will write here.
My HOS is S-OFF, cid 11111111, but when I type "getvar all" command I get result which shows me that my "model id" is PJ4011000.
Whan I type "adb shell getprop ro.aa.modelid" I get that my model id is PJ4010000.
So, if someone knows, can you please explain me why is this happen and is there some tutorial or something to change model id to PJ4010000.
I tried to do this with Root Manager, but it didnt help me, because when I type "getvar all" I get same like I said already.
One of the reason because I want to get back on PJ4010000 is that I think my phone stuck on edge after doing Facepalm s-off.
Sorry on my grammer, and thank you on your time. :good:

I don't get it...why do you need to change the model ID? The CID and MID are usually checked and you get errors about them (error 41 or 42), when trying to flash a firmware zip by "fastboot flash zip firmware_name.zip" command (after issuing "fastboot oem rebootRUU" command).
It is more easier to change the MID & CIF in the android-info.txt file inside the firmware zip, than to change the CID or MID

Rapier said:
I don't get it...why do you need to change the model ID? The CID and MID are usually checked and you get errors about them (error 41 or 42), when trying to flash a firmware zip by "fastboot flash zip firmware_name.zip" command (after issuing "fastboot oem rebootRUU" command).
It is more easier to change the MID & CIF in the android-info.txt file inside the firmware zip, than to change the CID or MID
Click to expand...
Click to collapse
Changing modelid is a necessary step for facepalm
s-off.
coma_white said:
I didnt want to open a new theme, so I will write here.
My HOS is S-OFF, cid 11111111, but when I type "getvar all" command I get result which shows me that my "model id" is PJ4011000.
Whan I type "adb shell getprop ro.aa.modelid" I get that my model id is PJ4010000.
So, if someone knows, can you please explain me why is this happen and is there some tutorial or something to change model id to PJ4010000.
I tried to do this with Root Manager, but it didnt help me, because when I type "getvar all" I get same like I said already.
One of the reason because I want to get back on PJ4010000 is that I think my phone stuck on edge after doing Facepalm s-off.
Sorry on my grammer, and thank you on your time. :good:
Click to expand...
Click to collapse
"adb shell getprop ro.aa.modelid" reads your build.porp AFAIK. Try changing your mid to pj4011000 from your build.prop and see if it helps your "stuck on edge" problem
Sent from my One S

ka_55 said:
Changing modelid is a necessary step for facepalm
s-off.
"adb shell getprop ro.aa.modelid" reads your build.porp AFAIK. Try changing your mid to pj4011000 from your build.prop and see if it helps your "stuck on edge" problem
Sent from my One S
Click to expand...
Click to collapse
tnx mate
it didnt really help me with my real problem about edge, but at least I learned something more about model id.

[Q] Relocked bootloader & it show Fastboot menu

hi Guyzz
im new to Android phone
i've Unlock Bootloader from HTC Dev, roorted my HTC Explorer,
i've relocked bootloader of my HTC Explorer through this command "fastboot oem lock" but facing some issues like
after relocking bootloader my phone does not starts it show fastboot menu again n again, i tried many time by removing battery but same issue occurs
After applying all those solutions that found on google notthing happens
help me guyzzzz

If you relock your bootloader, you should flash stock ROM (with stock kernel) and stock recovery. Otherwise the phone will be stuck at the HBOOT screen with a "Security Warning" message

relock bootloader
Sachin Thomas said:
If you relock your bootloader, you should flash stock ROM (with stock kernel) and stock recovery. Otherwise the phone will be stuck at the HBOOT screen with a "Security Warning" message
Click to expand...
Click to collapse
Oh thats great but how can i do this sir....?
Plz describe in detail

ammarraza94 said:
Oh thats great but how can i do this sir....?
Plz describe in detail
Click to expand...
Click to collapse
Why are you trying to do this? You have lost your warranty by unlocking the bootloader. Re-locking will not make any difference.
If you are trying to return to stock ROM, unlock your bootloader and flash this:
http://forum.xda-developers.com/showthread.php?t=2225776
Or if you really want to re-lock it find an RUU appropriate for your radio version and run it after re-locking

Sachin Thomas said:
Why are you trying to do this? You have lost your warranty by unlocking the bootloader. Re-locking will not make any difference.
If you are trying to return to stock ROM, unlock your bootloader and flash this:
http://forum.xda-developers.com/showthread.php?t=2225776
Or if you really want to re-lock it find an RUU appropriate for your radio version and run it after re-locking
Click to expand...
Click to collapse
Hello,
Yes Sir i don't have Warranty...& how can i flash stock ROM (with stock kernel) and stock recovery

ammarraza94 said:
Hello,
Yes Sir i don't have Warranty...& how can i flash stock ROM (with stock kernel) and stock recovery
Click to expand...
Click to collapse
Download RUU and run it after relocking

Sachin Thomas said:
Download RUU and run it after relocking
Click to expand...
Click to collapse
hi Dear this is my Radio Version & HBoot Version
HBOOT-1.01.0000
RADIO-1.10.80.13M2
Can i Apply this RUU on my Phone
"RUU_Pico_HTC_Europe_1.28.401.1_Radio_10.35d.80.09H_1.11.82.17_release_230964_signed"

ammarraza94 said:
hi Dear this is my Radio Version & HBoot Version
HBOOT-1.01.0000
RADIO-1.10.80.13M2
Can i Apply this RUU on my Phone
"RUU_Pico_HTC_Europe_1.28.401.1_Radio_10.35d.80.09H_1.11.82.17_release_230964_signed"
Click to expand...
Click to collapse
What's your device's CID? Type "fastboot getvar cid" in fastboot mode to find out

Sachin Thomas said:
What's your device's CID? Type "fastboot getvar cid" in fastboot mode to find out
Click to expand...
Click to collapse
CID: HTC__Y13
finished. total time: 0.000s

ammarraza94 said:
CID: HTC__Y13
finished. total time: 0.000s
Click to expand...
Click to collapse
According to this page HTC__Y13 corresponds to HTC_Europe
http://mobility.forumsee.com/a/m/s/p12-9502-061490--operator-name-and-cid-classification-for-mozart-roms-ansar.html
So I think you'll be able to use the European RUU. The installation will not continue if it's incompatible, it'll show Error [131]

Sachin Thomas said:
According to this page HTC__Y13 corresponds to HTC_Europe
http://mobility.forumsee.com/a/m/s/p12-9502-061490--operator-name-and-cid-classification-for-mozart-roms-ansar.html
So I think you'll be able to use the European RUU. The installation will not continue if it's incompatible, it'll show Error [131]
Click to expand...
Click to collapse
Hello
Sir which RUU Can i Use. What do u Prefer..?
"RUU_Pico_HTC_Europe_1.17.401.2 Radio_10.30.80.09 H_1.10.80.13M2 release_221180_signed"
"RUU_Pico_HTC_Europe_1.28.401.1 Radio_10.35d.80.09 H_1.11.82.17 release_230964_signed"
These Is My Phone Details
"HBOOT-1.01.0000"
"RADIO-1.10.80.13M2"
"CID: HTC__Y13 .finished. total time: 0.000s"

You can use any RUU that contains a radio that's newer than your current radio version

Sachin Thomas said:
You can use any RUU that contains a radio that's newer than your current radio version
Click to expand...
Click to collapse
pls i need a little help.
my phone cvid is : VODAP304
i've noticed that theres not this on that site you gave ->http://mobility.forumsee.com/a/m/s/...cid-classification-for-mozart-roms-ansar.html
maybe thats why i keep gettint the "error131" whenever i try to install a RUU...
i'm from portugal, so i'm using a europe ruu everytime i try to install, but i keep getting that error131 and saying that i should install a version compatible with my phone... idk what to do... can you help me?

[Q] Trying to upgrade HTC Desire S to HTC Android 4.0 (without Windows)

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.)