Related
Probably been covered before, but I need help in returning my Desire S to stock asap and also in Laymans terms as I'm new to all this.
I managed to get S off and its running SAGA LBC Mod v0.5.3 Android 2.3.3, sense 2.1
I only have limited access to the internet today so any links would be appreciated as I need it done by tonight.
Thanks in advance.
If you have a 6.98.xxxx hboot
Change your hboot with this one
Download PG88IMG.zip, extract it and use Android Flasher to flash the exctracted hboot.img
The hboot version now should be 0.98.2000
Search in this thread for the proper RUU and install it.
If you have a custom ROM and no info about your original software version the solution is as follows:
Connect the device, enter the bootloader and type the following command in the cmd:
Code:
fastboot getvar version-main
This is the number of your original software.
If this number is higher than the one of your RUU and you cannot flash it, change the number with the version of your RUU (be careful - use the correct RUU for your brand/region!) with misc_version that can be found here - post #1, link from step 1.
Cheers for that. I'll be trying it soon when my daughter goes to bed. Only part that is confusing me is where is the CMD. Probably a total noob question, sorry.
megzilla said:
... where is the CMD. .
Click to expand...
Click to collapse
See the guide in my signature about adb and fastboot - then it will be clear. By the way you will have to follow it too (in order to use the fastboot getvar command)
Again a problem. I want to downgrade hboot from 2.00.0002 to 0.98.00000
so I used misc_version. In one of the step it said
--> now adb shell closes and restarts, instead of having a $ you have a # which means root
But it dont happened.I ignored and continue other step. I went to fastboot and run RUU. It said Image version is 1.27.405.6
I think it work but after a while it said Error [155] unknown error.
so why? and what should I do?
ayene said:
Again a problem. I want to downgrade hboot from 2.00.0002 to 0.98.00000
so I used misc_version. In one of the step it said
--> now adb shell closes and restarts, instead of having a $ you have a # which means root
But it dont happened.I ignored and continue other step. I went to fastboot and run RUU. It said Image version is 1.27.405.6
I think it work but after a while it said Error [155] unknown error.
so why? and what should I do?
Click to expand...
Click to collapse
I think you simply forgot to relock your phone before flashing the RUU.
Sent from my HTC Desire S
relock using "FASTBOOT OEM UNLOCK"
nageshmv said:
relock using "FASTBOOT OEM UNLOCK"
Click to expand...
Click to collapse
Do you realize you've actually typed the command for "unlocking" instead of locking?
Won't work...
Thank all of u
Solved
how did you solve it? i have the same problem i s-on ed because the gps was broken(i sent it to waranty). now i m stuck. s-on + unloked. hboot 2.00.0002. i just want to install the ruu (for the moment). so... how can i lock it?
-
htc desire s error [155]: unknown error
radusy said:
how did you solve it? i have the same problem i s-on ed because the gps was broken(i sent it to waranty). now i m stuck. s-on + unloked. hboot 2.00.0002. i just want to install the ruu (for the moment). so... how can i lock it?
-
htc desire s error [155]: unknown error
Click to expand...
Click to collapse
Boot into bootloader. Go to fastboot mode and issue the command
Fastboot oem lock
Look at the thread posted right below this one. The answer is there too
Sent from my HTC Desire S
thank you problem solved
if you cant relock idid fastboot oem lock but restart and go to android logo how can i relock it ? after i flash oem lock failed and check hboot still unlock how can you fix it ?
Thank you for the advice
This is what fixed my device, I was running circles in twrp trying to figure out how to restore... all i had to do was relock the bootloader... and run ruu. You saved me a ton of headache.
Hi Everyone..
I have HTC sensation xe
Software version: 4.0.3 ((3.32.405.... Europe))
I bought this phone just 3 days ago and i was trying to make S-off Just to upgrade to official Middle East Rom (3.32.415...) as i got the RUU from here.
I try many time to use JuopunutBear But always gives "device
not root"..
Last time i try then start make backup then reboot
i make the wire-trick at same place for the picture and video in article..
after that the mobile stop at JuopunutBear screen,, i try fastboot, factory reset, recovery from Hboot screen,, all is just come back to same JuopunutBear screen
and do nothing..
The phone is restarted every 5 min automaticly and give HTC green logo first then stuck on same screen in image
I use this thread
http://forum.xda-developers.com/showthread.php?t=1661631
I unlock by HTCdev.com
and do all steps one by one
I make backup for recovery by Clockworkmod before as i learn from other thread
Please help me what i can do and what's happen with me
Any Attention, response, answer or help will be really appreciated
MAESTRO_X said:
Hi Everyone..
I have HTC sensation xe
Software version: 4.0.3 ((3.32.405.... Europe))
I bought this phone just 3 days ago and i was trying to make S-off Just to upgrade to official Middle East Rom (3.32.415...) as i got the RUU from here.
I try many time to use JuopunutBear But always gives "device
not root"..
Last time i try then start make backup then reboot
i make the wire-trick at same place for the picture and video in article..
after that the mobile stop at JuopunutBear screen,, i try fastboot, factory reset, recovery from Hboot screen,, all is just come back to same JuopunutBear screen
and do nothing..
The phone is restarted every 5 min automaticly and give HTC green logo first then stuck on same screen in image
I use this thread
http://forum.xda-developers.com/showthread.php?t=1661631
I unlock by HTCdev.com
and do all steps one by one
I make backup for recovery by Clockworkmod before as i learn from other thread
Please help me what i can do and what's happen with me
Any Attention, response, answer or help will be really appreciated
Click to expand...
Click to collapse
connect the phone to PC and go to the folder with controlbear.exe
Hold down shift and right-click Select the option open command window here and type this command and press enter:
Code:
controlbear.exe -r
After that, if you don't wanna run the controlbear again, don't forget to remove temp_root
Thankssssss
It's really great
Thank you very much kgs1992
I thought my mobile is brick down
So.. what's the best way to upgrade my phone rom
Just i need the official ME (Arabic) RUU Rom to be installed?
and how to delete temp_root?
Thanks & Regards
MAESTRO_X said:
It's really great
Thank you very much kgs1992
I thought my mobile is brick down
So.. what's the best way to upgrade my phone rom
Just i need the official ME (Arabic) RUU Rom to be installed?
and how to delete temp_root?
Thanks & Regards
Click to expand...
Click to collapse
It's included in the guide that your viewing.
I'm not sure about language specific RUUs. You can try my RUU Guide, link in my signature.
I try to open your threads
[GUIDE]RUU related info (S-On with RUU, extracting rom.zip & manual flashing, etc)
but:
Error: Unable to find site's URL to redirect to.
Please check that the URL entered is correct. To learn more about TinyURL.com, please visit the homepage.
!!??
MAESTRO_X said:
I try to open your threads
[GUIDE]RUU related info (S-On with RUU, extracting rom.zip & manual flashing, etc)
but:
Error: Unable to find site's URL to redirect to.
Please check that the URL entered is correct. To learn more about TinyURL.com, please visit the homepage.
!!??
Click to expand...
Click to collapse
I'm sorry, I was editing my signature, something must have gone wrong.
It's fine now.
You did not need to unlock your bootloader.
Plus, if you're only interested in your stock RUU, you should be able to just change cid in android-info.txt. Might be wrong
how to use android-info.txt, or even make my mobile with supercid 11111111
I try many ways not work,,
I still s-on and i interest with official ruu for middle east and as i see the version is 3.415,, and my version is 3.405
so what's the best way to install this ruu without troubles as i tried many ways
Run your RUU. When it loads, check your temp folder for the zip file. Modify android-info.txt in the zip with your cid. Either modify the existing zip and continue with the RUU update, or rename the zip to PG58IMG.zip, place on root, and boot into bootloader.
renaming and put on sdcard i already tried but i will try editing cid and see if possible..
i will do factory reset first maybe better..
thanks alot
MAESTRO_X said:
renaming and put on sdcard i already tried but i will try editing cid and see if possible..
i will do factory reset first maybe better..
thanks alot
Click to expand...
Click to collapse
Man.. In my guide I already told you if you have htc dev unlocked bootloader please follow the guide by auggie2k.. Buy you still followed mine.. That's the issue soff didnt worked
Also you said you want to install middle east RUU.. That is easily possible in your case
First get the cid of middle east from those thread http://forum.xda-developers.com/showthread.php?t=1195475
It it HTC__J15 I think (Arabic one)
Then change the cid
Connect them phone in fastboot and then to pc.. Then open command prompt from there adb folder on pc
Then type this
fastboot oem writecid <your cid >
(you'll lose the supercid though)
Now just reboot to bootloader again
fastboot reboot-bootloader
Then from this fastboot mode itself
Relock the bootloader
fastboot oem lock
Then run the RUU.exe on pc
(phone should be in fastboot)
Ps: changing the cid in android-info.txt won't help you as you are SON
Sent from my pyramid.. Through blazing fast sonic waves
OK, so there is a signature check that prevents you from simply changing the cid in the android-info? Or does is the cid defined somewhere else?
Being supercid, you should be able to flash any ruu you want, assuming it's not a downgrade I thought. Or does that still only apply for s-off?
ganeshp said:
Man.. In my guide I already told you if you have htc dev unlocked bootloader please follow the guide by auggie2k.. Buy you still followed mine.. That's the issue soff didnt worked
Also you said you want to install middle east RUU.. That is easily possible in your case
First get the cid of middle east from those thread http://forum.xda-developers.com/showthread.php?t=1195475
It it HTC__J15 I think (Arabic one)
Then change the cid
Connect them phone in fastboot and then to pc.. Then open command prompt from there adb folder on pc
Then type this
fastboot oem writecid <your cid >
(you'll lose the supercid though)
Now just reboot to bootloader again
fastboot reboot-bootloader
Then from this fastboot mode itself
Relock the bootloader
fastboot oem lock
Then run the RUU.exe on pc
(phone should be in fastboot)
Ps: changing the cid in android-info.txt won't help you as you are SON
Sent from my pyramid.. Through blazing fast sonic waves
Click to expand...
Click to collapse
S On implies that you cannot fire fastboot oem commands as well, right? how will he writecid? :/
I meant if he changed the cid in android-info to his native cid, then he should be able to flash it while s-on?
ziddey said:
I meant if he changed the cid in android-info to his native cid, then he should be able to flash it while s-on?
Click to expand...
Click to collapse
Mate, if the android-info.txt is changed, the rom.zip will change. This implies signature check will fail due to modified file size. :/
ganeshp said:
Man.. In my guide I already told you if you have htc dev unlocked bootloader please follow the guide by auggie2k.. Buy you still followed mine.. That's the issue soff didnt worked
Also you said you want to install middle east RUU.. That is easily possible in your case
First get the cid of middle east from those thread http://forum.xda-developers.com/showthread.php?t=1195475
It it HTC__J15 I think (Arabic one)
Then change the cid
Connect them phone in fastboot and then to pc.. Then open command prompt from there adb folder on pc
Then type this
fastboot oem writecid <your cid >
(you'll lose the supercid though)
Now just reboot to bootloader again
fastboot reboot-bootloader
Then from this fastboot mode itself
Relock the bootloader
fastboot oem lock
Then run the RUU.exe on pc
(phone should be in fastboot)
Ps: changing the cid in android-info.txt won't help you as you are SON
Sent from my pyramid.. Through blazing fast sonic waves
Click to expand...
Click to collapse
I try this at all before from the guide but my cid not change at all
i have already HTC__J15 but also the RUU of arabic dosen't install with two ways
(1- copy in the sdcard and hboot)
(2- directly setup in windows with or without edit android-txt to my cid)
I think s-off is the best way but i try also many time with JB but no way
maybe there's other wrong but i still not discover it..
Is there any other tool for S-off as my version 1.29!?
Thank you friend ,, it's really appreciate that all people here is kindly helping
with quick response
MAESTRO_X said:
I try this at all before from the guide but my cid not change at all
i have already HTC__J15 but also the RUU of arabic dosen't install with two ways
(1- copy in the sdcard and hboot)
(2- directly setup in windows with or without edit android-txt to my cid)
I think s-off is the best way but i try also many time with JB but no way
maybe there's other wrong but i still not discover it..
Is there any other tool for S-off as my version 1.29!?
Thank you friend ,, it's really appreciate that all people here is kindly helping
with quick response
Click to expand...
Click to collapse
Yes, I too think S Off is best for you, but it's best if you wait for ganeshp to reply, as he is the most experienced of us..
kgs1992 said:
Yes, I too think S Off is best for you, but it's best if you wait for ganeshp to reply, as he is the most experienced of us..
Click to expand...
Click to collapse
Yes sure i will wait..
Thank you and everyone for help and share experience..
kgs1992 said:
S On implies that you cannot fire fastboot oem commands as well, right? how will he writecid? :/
Click to expand...
Click to collapse
Yes technically that should be the case.. But apparently there is a hole in HTC bootloader.. Which makes it change the cid.. (happens only on 1.2x hboots only though)
Edit: What cid change didnt worked?
We tried it on two guys one having unlocked bootloader and other having looked bootloader.. For both of them it worked fine.
Have you tried checking the cid after changing it?
First change cid using
fastboot oem writecid <your cid >
(it says failed but after rebooting the bootloader using "fastboot reboot-bootloader" if you check for cid again using "fastboot getvar cid" it should show you the new cid)
If the above was success then just Run the Arabic ruu...
Otherwise soff is not really required for you as you are htc dev unlocked
Just install the asanic custom rom by darkmantra if you just want support for Arabic language..
For installing custom roms while SON. Please follow the guide "flashing rom's with SON" by asskicker2 present in sensation general section
If you insist on getting that Arabic RUU.. Then soff is the only way for you..
Please follow the " guide to soff using Juopunutbear " by auggie2k which is also present in sensation general section
Sent from my pyramid.. Through blazing fast sonic waves
dude my phone is also stuck on the same screen n when did the above explnation it says waiting for device n dosent goes forward ne where tell me what to do my cell is bricked plzz help
htc sensation
hboot 1.27.0000
rooted
unlocked form htc dev
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
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.