correct RUU 3.32.161.11 in post #11
Hi people.
The thing at the moment is stuck at JuopunutBear. But better to start from begining...
I decided to flash a different rom into it. So i unlocked a bootloader, installed "4EXT Recoveryy Touch" and tried to flash it straight away without having any backup... then the device use to get stuck on boot logo (as i rear later because of "s-on") and enabling "smart flash" on 4ext might help... but it didn't worked for me so i decided to install "JuopunutBear" and get "s-off" (on device which does not boot up any more)...
But my plan failed because whatever i did it ends up on "JuopunutBear" screen.
i though this was going to work but it did not:
C:\Users\user\Desktop\ControlBearRelease_pyramid_ICS_WIN>controlbear.exe -r
======== ControlBear 0.8 beta for JuopunutBear S-OFF ==========
Restoring to normal mode
Searching for device.....
Found device... Please wait...
Device should be in normal boot mode....
Press ENTER to exit.....
changed nothing.
this is all info i can see on hboot:
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
eMMC-boot
Jan 13 2012, 17:33:34
As far i can at first i need to get rid of "JuopunutBear" at first.. and then somehow to make the rom work... have no idea what to do next... is it possible to do fresh reinstall for all regardless what mess is there right now?
that is definitely the last time i play like this but now only thing i want is to get it working...
I would be glad for some advice. thank you!
An RUU will make your phone completely stock. As for the juopuonut s-off, it seems like you are using an old version of control bear.
Look here for ruu: http://forum.xda-developers.com/showthread.php?p=26541170
Sent from my HTC Sensation
AndroidSupporter318 said:
An RUU will make your phone completely stock. As for the juopuonut s-off, it seems like you are using an old version of control bear.
Look here for ruu: http://forum.xda-developers.com/showthread.php?p=26541170
Sent from my HTC Sensation
Click to expand...
Click to collapse
Well you opened my eyes but still...
C:\Users\user\Desktop\ControlBearRelease_pyramid_ICS_WIN>fastboot getvar cid
cid: VODAP001
finished. total time: 0.003s
C:\Users\user\Desktop\ControlBearRelease_pyramid_ICS_WIN>fastboot getvar version
-main
version-main: 3.32.161.52
finished. total time: 0.003s
C:\Users\user\Desktop\ControlBearRelease_pyramid_ICS_WIN>
tried all steps till 4.4.2 With a PC, via fastboot USB and at the end i got an error
C:\Users\user\Desktop>fastboot flash zip PG58IMG.zip
sending 'zip' (437337 KB)... OKAY [ 64.719s]
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 139.619s
i found the rom, extracted it from exe file (boot.zip) then i needed to modify "android-info.txt" because there are just rally old rom`s with a proper signature. But i could only view and extract archive (if i archive it back it won't work) but not change files inside of them... i tried a couple of them and got the same problem that i can't modify them with any archiver ("archive is corrupt") so i just carryed on with extracting and archiving even when i read that it won't work... windows default archiver does not work, 7-zip as well, winRAR either... am i using a wrong archiver or there is some other way of getting everything done properly? i am totally lost
gyrtaz said:
C:\Users\user\Desktop\ControlBearRelease_pyramid_ICS_WIN>fastboot getvar cid
cid: VODAP001
finished. total time: 0.003s
C:\Users\user\Desktop\ControlBearRelease_pyramid_ICS_WIN>fastboot getvar version
-main
version-main: 3.32.161.52
finished. total time: 0.003s
C:\Users\user\Desktop\ControlBearRelease_pyramid_ICS_WIN>
tried all steps till 4.4.2 With a PC, via fastboot USB and at the end i got an error
C:\Users\user\Desktop>fastboot flash zip PG58IMG.zip
sending 'zip' (437337 KB)... OKAY [ 64.719s]
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 139.619s
i found the rom, extracted it from exe file (boot.zip) then i needed to modify "android-info.txt" because there are just rally old rom`s with a proper signature. But i could only view and extract archive (if i archive it back it won't work) but not change files inside of them... i tried a couple of them and got the same problem that i can't modify them with any archiver ("archive is corrupt") so i just carryed on with extracting and archiving even when i read that it won't work... windows default archiver does not work, 7-zip as well, winRAR either... am i using a wrong archiver or there is some other way of getting everything done properly? i am totally lost
http://forum.xda-developers.com/showthread.php?p=26541170
Click to expand...
Click to collapse
you are SON
so you need the correct RUU based on your CID/MiD/Version-Main ..
downloading any RUU and just modifying the android-info.txt wont do any good (it only works when you are SOFF)
ganeshp said:
you are SON
so you need the correct RUU based on your CID/MiD/Version-Main ..
downloading any RUU and just modifying the android-info.txt wont do any good (it only works when you are SOFF)
Click to expand...
Click to collapse
my current non-working version is 3.32.161.52
and the best i could find is 1.24.161...
i can't downgrade and can't put anything custom because i it is SON... so it is dead end for me.
is it possible to put some fake ROM by force (like copying files somewhere or smth...) even if it would not work but which would be seen as an "1.24.161..." when i would try to install it properly?
Just brain storming sorry if i am not telling anything clever...
It should be this one: http://hotfile.com/dl/176652525/e42....23.3504.07_M2_release_256146_signed.exe.html
If this one is not it, then try looking at the two sites that were listed in the ruu thread I gave you.
Sent from my HTC Sensation
---------- Post added at 10:43 AM ---------- Previous post was at 10:36 AM ----------
Actually, the link above is for Australian vodaphone users.
This one is general, not branded. It is for European users: http://hotfile.com/dl/158597479/f24...1.22.3504.07_M_release_252064_signed.exe.html
Sent from my HTC Sensation
---------- Post added at 10:45 AM ---------- Previous post was at 10:43 AM ----------
Also, the version number 1.2x is the gingerbread RUU's. 3.32 is for ICS RUU's
Sent from my HTC Sensation
AndroidSupporter318 said:
It should be this one: hotfile.com/dl/176652525/e4290a8/RUU_PYRAMID_ICS_Voda-Hutch_AU_3.32.862.13_Radio_11.69A.3504.00U_11.23.3504.07_M2_release_256146_signed.exe.html
If this one is not it, then try looking at the two sites that were listed in the ruu thread I gave you.
Sent from my HTC Sensation
Click to expand...
Click to collapse
i have checked these links you gave before and there was just gingerbread if i try to find exactly by uk wodafone
will try these too... thanks
AndroidSupporter318 said:
It should be this one: http://hotfile.com/dl/176652525/e42....23.3504.07_M2_release_256146_signed.exe.html
If this one is not it, then try looking at the two sites that were listed in the ruu thread I gave you.
Sent from my HTC Sensation
---------- Post added at 10:43 AM ---------- Previous post was at 10:36 AM ----------
Actually, the link above is for Australian vodaphone users.
This one is general, not branded. It is for European users: http://hotfile.com/dl/158597479/f24...1.22.3504.07_M_release_252064_signed.exe.html
Sent from my HTC Sensation
---------- Post added at 10:45 AM ---------- Previous post was at 10:43 AM ----------
Also, the version number 1.2x is the gingerbread RUU's. 3.32 is for ICS RUU's
Sent from my HTC Sensation
Click to expand...
Click to collapse
Didn't worked out...
How do you think if i unlock the bootloader again is it possible to delete the partition containing OS trough recovery and maybe than having a blank device i would be able to install any version of RUU..? Need some sort of other solution in this situation...
Hmm... can you try to format all partitions from recovery and then try ruu again?
Sent from my HTC Sensation
gyrtaz said:
Hi people.
The thing at the moment is stuck at JuopunutBear. But better to start from begining...
I decided to flash a different rom into it. So i unlocked a bootloader, installed "4EXT Recoveryy Touch" and tried to flash it straight away without having any backup... then the device use to get stuck on boot logo (as i rear later because of "s-on") and enabling "smart flash" on 4ext might help... but it didn't worked for me so i decided to install "JuopunutBear" and get "s-off" (on device which does not boot up any more)...
But my plan failed because whatever i did it ends up on "JuopunutBear" screen.
i though this was going to work but it did not:
C:\Users\user\Desktop\ControlBearRelease_pyramid_ICS_WIN>controlbear.exe -r
======== ControlBear 0.8 beta for JuopunutBear S-OFF ==========
Restoring to normal mode
Searching for device.....
Found device... Please wait...
Device should be in normal boot mode....
Press ENTER to exit.....
changed nothing.
this is all info i can see on hboot:
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
eMMC-boot
Jan 13 2012, 17:33:34
As far i can at first i need to get rid of "JuopunutBear" at first.. and then somehow to make the rom work... have no idea what to do next... is it possible to do fresh reinstall for all regardless what mess is there right now?
that is definitely the last time i play like this but now only thing i want is to get it working...
I would be glad for some advice. thank you!
Click to expand...
Click to collapse
Hi! Are you still looking for the right RUU? If I got it right you need the Vodafone UK one. You can download it from HERE That will work with your phone. I have the same RUU and always used it when I had to. Boot your phone into Bootloader, then select Fastboot. Make sure on the screen it does say Fastboot USB, then run the RUU and let it finish. Ohh! And don't forget to relock your bootloader before running the RUU. "fastboot oem lock"
AndroidSupporter318 said:
Hmm... can you try to format all partitions from recovery and then try ruu again?
Sent from my HTC Sensation
Click to expand...
Click to collapse
i think i am able to wipe something if i unlock it again but i have no idea what and what effects it is going to make if i do and if i am not going to delete too much (like HBOOT itself) and stuff like that...
is that way possible at all in my condition? is there any tutorials about doing so?
I just unlocked it again. i have some options..:
wipe data/factory reset
wipe cache
wipe catce + dalvik
wipe dalvik cache
wipe battery stats
format system
format data
format boot
format all partitions (except sdcard)
format sdcard
is deleting something going to make me able of installing gingerbread ruu? (because in theory just this old rom is good to my device)
is there anything useful in this list?
If you do a full wipe that's not going to effect hboot but all your data and the installed rom itself. That means you will not have a usable rom flashed on your phone so it will automatically boot into bootloader. But try to download the ruu I linked and follow the steps. If it doesn't work then we can figure out something else.
Sent from your back garden! Don't look back!
matekaneve said:
Hi! Are you still looking for the right RUU? If I got it right you need the Vodafone UK one. You can download it from HERE That will work with your phone. I have the same RUU and always used it when I had to. Boot your phone into Bootloader, then select Fastboot. Make sure on the screen it does say Fastboot USB, then run the RUU and let it finish. Ohh! And don't forget to relock your bootloader before running the RUU. "fastboot oem lock"
Click to expand...
Click to collapse
[RED]OH WOW MATE!!! YOU ARE MY HERO SINCE NOW! EVERYTHING WORKED JUST AS IT SHOULD[/RED]
anyway it is still interesting to me what can you delete with these functions of "4eXT" in the list and if my theory about deleting something and installing gingerbread is right? if yes what should i wipe or format?
When you are flashing roms, in 4ext recovery, there is an option to format all partitions. By doing so you can achive a fresh and clean install of the chosen rom. It does not affect your hboot or your firmware. It only ereases the partitions roms are using. To install gingerbread roms or ruu, you must flash the appropriate gingerbread firmware first. To do so, you must achive s-off first. As you already have 3.32 firmware installed you are "only" able to flash all the currently available ice cream sandwich and jelly bean roms. Hope this helps.
Sent from your back garden... Don't look back!
matekaneve said:
When you are flashing roms, in 4ext recovery, there is an option to format all partitions. By doing so you can achive a fresh and clean install of the chosen rom. It does not affect your hboot or your firmware. It only ereases the partitions roms are using. To install gingerbread roms or ruu, you must flash the appropriate gingerbread firmware first. To do so, you must achive s-off first. As you already have 3.32 firmware installed you are "only" able to flash all the currently available ice cream sandwich and jelly bean roms. Hope this helps.
Sent from your back garden... Don't look back!
Click to expand...
Click to collapse
aha... so if i would not have got any version above 3.32.161 my phone would be pretty much doomed..?
just asking for basic knowledge if i would have any similar problems in the future.. should i seek some info for bricked phone recovery then?
gyrtaz said:
aha... so if i would not have got any version above 3.32.161 my phone would be pretty much doomed..?
just asking for basic knowledge if i would have any similar problems in the future.. should i seek some info for bricked phone recovery then?
Click to expand...
Click to collapse
Honestly, do not worry about bricking your device, just enjoy the freedom rooting gave you. If something goes wrong, you can always use that ruu. The latest voda UK version is 3.32.161.(52)? The main thing is the first 3 digits: 3.32-> ics firmware, ...161-> Vodafone UK code. The last numbers don't matter. Always make sure you flash the correct rom according to your firmware version and your device
Btw. You can install roms require 3.32 or 3.33 firmware! Enjoy flashing!
Sent from my HTC Sensation Z710e using xda app-developers app
matekaneve said:
Honestly, do not worry about bricking your device, just enjoy the freedom rooting gave you. If something goes wrong, you can always use that ruu. The latest voda UK version is 3.32.161.(52)? The main thing is the first 3 digits: 3.32-> ics firmware, ...161-> Vodafone UK code. The last numbers don't matter. Always make sure you flash the correct rom according to your firmware version and your device
Btw. You can install roms require 3.32 or 3.33 firmware! Enjoy flashing!
Sent from my HTC Sensation Z710e using xda app-developers app
Click to expand...
Click to collapse
Come on... I am about learning stuff and knowing. Maybe some day helping someone else. You can tell someone who doesn't really care to not worry instead of telling a short proper answer... sorry i am not trying to be offensive but it was one of the "try using google" sort of answers and that was how i feel about it...
THANKS FOR ALL THE HELP YOU ALL :highfive:
Related
just letting those who s.offed with xtc clip can flash PG88IMG.zip which is 53.922kb large . from w http://db.tt/JH7Mhb0 with out having to do the deadly dd commands in his guide. just flash the whole zip in bootloader mode as normal this gives you the new 2.00.2002 hboot 3817.07.00.19_m. radio plus libs and ramdisk you can also boot back into a 2.1 rom without problems and boot from there into recovery to flash a 3.0 rom if u wish. you can also flash a ruu rom which will put you back to stock hboot. iv tried all this today without a problem infact iv done it twice.
tready said:
just letting those who s.offed with xtc clip can flash PG88IMG.zip which is 53.922kb large . from http://forum.xda-developers.com/showthread.php?t=1236890 with out having to do the deadly dd commands in his guide. just flash the whole zip in bootloader mode as normal this gives you the new 2.00.2002 hboot 3817.07.00.19_m. radio plus libs and ramdisk you can also boot back into a 2.1 rom without problems and boot from there into recovery to flash a 3.0 rom if u wish. you can also flash a ruu rom which will put you back to stock hboot. iv tried all this today without a problem infact iv done it twice.
Click to expand...
Click to collapse
Just to confirm....(for the third time ) What you're saying is that a XTC'd S-OFF user like myself, can apply the above zip to get the latest upgraded HBOOT 2.xxxx.xxx and Radio?
Couple of questions:
[Q1] This new HBOOT will work on both older Sense 2.1 ROMS, current Sense 2.1+3.0 ROMS (like LBC) and the latest leaked Sense 3.0 ROMS?
[Q2] is this an ENG hboot? with access to flash radio & recovery with fastboot (over bootloader)? as I currently can do?
Answers appreciated
ben_pyett said:
Just to confirm....(for the third time ) What you're saying is that a XTC'd S-OFF user like myself, can apply the above zip to get the latest upgraded HBOOT 2.xxxx.xxx and Radio?
Couple of questions:
[Q1] This new HBOOT will work on both older Sense 2.1 ROMS, current Sense 2.1+3.0 ROMS (like LBC) and the latest leaked Sense 3.0 ROMS?
[Q2] is this an ENG hboot? with access to flash radio & recovery with fastboot (over bootloader)? as I currently can do?
Answers appreciated
Click to expand...
Click to collapse
Q1= yes it works on sense 2.1 rom i flashed the PG88IMG.zip new hboot radio libs ramdisk then booted back into my 2.1 stock rom with no problem then booted into recovery and flashed this http://forum.xda-developers.com/showthread.php?t=1240132 thats the stock 3.0 rom you can also use proxuser roms with new hboot.Q2 im not sure as iv not tried flashing recovery via fastboot with this hboot
I will wait for the confirmation than we will be access to flash and recovery with fastboot.
I am in the same case that @ ben_pyett
philos64 said:
I will wait for the confirmation than we will be access to flash and recovery with fastboot.
I am in the same case that @ ben_pyett
Click to expand...
Click to collapse
ill try it now and let u no
philos64 said:
I will wait for the confirmation than we will be access to flash and recovery with fastboot.
I am in the same case that @ ben_pyett
Click to expand...
Click to collapse
I imagine that we'll have to wait for a further leaked device release, however, this time one that with a new ENG hboot, so unfortunately I suspect that the chances of that happening are quite small.
Although, if we're able to revert to the stock hboot after being on the new hboot?
If the new ROMS are worth moving to and they do look to have serious potential , then it may well be worth the risk, only time will tell.
EDIT: just read your post above....looking forward to answer....Thanks again.
ben_pyett said:
I imagine that we'll have to wait for a further leaked device release, however, this time one that with a new ENG hboot, so unfortunately I suspect that the chances of that happening are quite small.
Although, if we're able to revert to the stock hboot after being on the new hboot?
If the new ROMS are worth moving to and they do look to have serious potential , then it may well be worth the risk, only time will tell.
EDIT: just read your post above....looking forward to answer....Thanks again.
Click to expand...
Click to collapse
good new fastboot works iv just flashed recovery.img via fastboot
C:\Users\sarah>cd/
C:\>cd AndroidSDK/tools/
C:\AndroidSDK\tools>adb devices
List of devices attached
************ device
C:\AndroidSDK\tools>fastboot flash recovery recovery.img
sending 'recovery' (5030 KB)... OKAY [ 0.892s]
writing 'recovery'... OKAY [ 0.925s]
finished. total time: 1.818s
C:\AndroidSDK\tools>
tready said:
good new fastboot works iv just flashed recovery.img via fastboot
C:\Users\sarah>cd/
C:\>cd AndroidSDK/tools/
C:\AndroidSDK\tools>adb devices
List of devices attached
************ device
C:\AndroidSDK\tools>fastboot flash recovery recovery.img
sending 'recovery' (5030 KB)... OKAY [ 0.892s]
writing 'recovery'... OKAY [ 0.925s]
finished. total time: 1.818s
C:\AndroidSDK\tools>
Click to expand...
Click to collapse
great, I don't suppose that you can attach a link to the PG88IMG.zip that is to be downloaded and flashed within post #1 above could you?
As that other thread is now quite littered and contains several file links.
ben_pyett said:
great, I don't suppose that you can attach a link to the PG88IMG.zip that is to be downloaded and flashed within post #1 above could you?
As that other thread is now quite littered and contains several file links.
Click to expand...
Click to collapse
If you follow my link its on the the first page of that thread a few lines down iv just checked the down load link takes you to a Chinese cite just use google translate the download is on the bottom left corner hit it and it should start downloading use Google crome
Sent from my HTC Desire S using xda premium
It works
Now I have hboot 2.00.2002, radio 3817.07.00.19_m; s-off & 4ext recovery remains.
Coredriod 1.3 works.
Could upload and make a link for this version of new Hboot.
Everybody don't use Google Chrome, and speak or read chinese, and I think it's much helpfull for all users
philos64 said:
Could upload and make a link for this version of new Hboot.
Everybody don't use Google Chrome, and speak or read chinese, and I think it's much helpfull for all users
Click to expand...
Click to collapse
http://db.tt/JH7Mhb0 here you go
Sent from my HTC Desire S using xda premium
Thk's a lot.
I'm gonna try when I'm Off on my work
Edit: It works well
Now I have hboot 2.00.2002, radio 3817.07.00.19_m (already flashed) ; s-off & 4ext recovery are here and functional.
Coredriod 1.3 works perfectly
Edit 2 : But I've got "locked" who's wrote on bootloader screen
philos64 said:
Thk's a lot.
I'm gonna try when I'm Off on my work
Edit: It works well
Now I have hboot 2.00.2002, radio 3817.07.00.19_m (already flashed) ; s-off & 4ext recovery are here and functional.
Coredriod 1.3 works perfectly
I'm on test with Coredroid 2.3.5
Edit 2 : But I've got "locked" who's wrote on bootloader screen
Click to expand...
Click to collapse
Yeah that's right it says locked its an enghboot but don't worry its not really locked as I said fastboot works and 2.1 /3.0 roms work with it and you can just flash ruu rom to remove it.
Sent from my HTC Desire S using xda premium
I'm not scared by it 'locked'. This is just to inform other users
Ok cool I would say this to people who have used revolotinary to s off DO NOT FLASH THE WHOLE ZIP use biglsd guide. Why I flashed the whole zip last week on my 3 day old desire s it worked fine but the problem was I needed to s on as the screen became lose I follwed the s on guide and my phone bricked totally dead. Lookely tmibile sent me a new one which I then s offed with xtc clip even though its a one way ticket. I'm not 100% sure the bricking happened because of the zip flash but its not worth the risk so be warned.
Sent from my HTC Desire S using xda premium
philos64 said:
I'm not scared by it 'locked'. This is just to inform other users
Click to expand...
Click to collapse
Especially if like most of us posting here in this thread you've been down the XTC Clip route and will therefore remain S-OFF UNLOCLKED forever!
I know it ... and I knew it when I used the XTC clip route.
Us XTC Clip folk are a minority in this forum now, we've been inundated!!!
All good though, brings more devs and stuff eh
For those people who's want install the new Hboot.
1 - Rename the "file.zip" who's contains "hboot - radio and lib" => PM88IMG.zip
2 - Install this file on your Sdcard - Make a Nand backup...just in case
2 - Boot into your recovery (Ext4 or CWM)
3 - reboot bootloader (Volume Down + POWER)
4 - fastboot and flash PM88IMG.zip
5 - fastboot reboot
6 - Or install your new rom
If I forgot something on the hboot flash, tell me
Hey
It seems OTA is of no use for Rooted Phone.
Where do i download and upgrade to 2.3.5 + HTC Sense 3.0 ? (manually)
xAutobot said:
Hey
It seems OTA is of no use for Rooted Phone.
Where do i download and upgrade to 2.3.5 + HTC Sense 3.0 ? (manually)
Click to expand...
Click to collapse
Just change your hboot to 0.98.2000 and the update will be fine.
The more safe way is to flash an older RUU to go back to stock and then update OTA
amidabuddha said:
Just change your hboot to 0.98.2000 and the update will be fine.
The more safe way is to flash an older RUU to go back to stock and then update OTA
Click to expand...
Click to collapse
I downgraded my HBOOT-0.98.2000 (PG8810000) using the sticky link. OTA still doesnt work. Stucks at a white screen with Droid near a Warning Triangle!
I had HTC Desire S 2.3.3 Sense 2.1. Rooted + SOFF using Revolutionary method. I've read almost all post on Unrooting / S-on . The main post itself has been removed and 100s of post following with people trying random stuff.
Any suggestions?
xAutobot said:
I downgraded my HBOOT-0.98.2000 (PG8810000) using the sticky link. OTA still doesnt work. Stucks at a white screen with Droid near a Warning Triangle!
I had HTC Desire S 2.3.3 Sense 2.1. Rooted + SOFF using Revolutionary method. I've read almost all post on Unrooting / S-on . The main post itself has been removed and 100s of post following with people trying random stuff.
Any suggestions?
Click to expand...
Click to collapse
I didn't know that you have already applied the OTA
Since you have the 0.98.2000 hboot download this RUU (which is for Asia-India and I suppose that is your version) and run it on your PC with USB connected phone. This should give you the previous version and complete Stock/S-ON. Then check for OTA update from the settings.
If the RUU says that your current version is higher and cannot proceed, you should have to flash a custom recovery (download and extract this zip file) flash extracted recovery.img from fastboot:
Code:
fastboot flash recovery {path to file}/recovery.img
, reboot to recovery, get root access through adb shell and use the misc_version from this thread (point 1) to change your version to 1.47.720.1. Then the RUU will work.
If you have troubles post back I will describe step by step what to do.
And remember - do not pull the battery in any case!
It worked!
The software version was already 1.47.720.1
Everything went perfect and smooth. You rock mate!
Applied OTA, and now i'm back on stock 2.3.5.
I realized HBOOT 2.00.0002 is not supported by Revolutionary for S-OFF and Rooting. Any other way? or if i want to have root I need to flash back to 2.3.3 stock revolutionary root and then install available pre-rooted stock rom?
Nice to know that you managed.
If you need root you can unlock your new 2.00.0002 hboot on htcdev.com I think there is a guide in the forum, search for it.
Sent from my HTC Desire S using Tapatalk
The guide you need is here, post #36
Sent from my HTC Desire S using Tapatalk
You rock bro! I need to sleep now. Will try the method tomorrow.
*fingers crossed*
i'm not getting over the air update for my desire hd!
daily i used to check for the update but my phone says the phone software is up to date!..is there sumthin that i can do to get the ota????
:-( :-(
pls help me!!!
i've been tryin to get from the moment i heard there is an update!
pls reply asap!!!
siddhuyzfr15 said:
daily i used to check for the update but my phone says the phone software is up to date!..is there sumthin that i can do to get the ota????
:-( :-(
pls help me!!!
i've been tryin to get from the moment i heard there is an update!
pls reply asap!!!
Click to expand...
Click to collapse
Hey please relax
HTC is pushing the update to a limited number of devices daily to avoid overloading of their server. Keep checking and you will receive it it the next couple of days.
The other possibility is that you version is older. Check it from your phone settings, if it is different that 1.47.720.1 you should use the RUU linked in post #4 and then you will receive the OTA. Keep in mind that the RUU will delete your data so make a Google backup.
Also if you phone is S-OFFed with Revolutionary you will have to change the hboot (see posts above).
Good luck
siddhuyzfr15 said:
daily i used to check for the update but my phone says the phone software is up to date!..is there sumthin that i can do to get the ota????
:-( :-(
pls help me!!!
i've been tryin to get from the moment i heard there is an update!
pls reply asap!!!
Click to expand...
Click to collapse
Can it be carrier based?
Just try inserting someones Airtel SIM and check for an OTA Update!. You never know, it may work
amidabuddha said:
The guide you need is here, post #36
Sent from my HTC Desire S using Tapatalk
Click to expand...
Click to collapse
Hey Un Lock via HTC Site worked. I can see Unlocked in Bootloader.
On trying to Flash using AndroidFlasher nothing happens!
I downloaded all those given in links. Started flashing utility. It gave the following message
< waiting for device >
security: on
finished. total time: -0.000s
sending 'recovery' (4336 KB)...
OKAY [ 0.822s]
writing 'recovery'...
OKAY [ 0.836s]
finished. total time: 1.658s
downloading 'boot.img'...
OKAY [ 0.746s]
booting...
OKAY [ 0.001s]
finished. total time: 0.747s
and phone got stuck at HTC White Screen with Green Logo for 20 minutes. Then i removed battery and restart Phone. Checked its still S-ON + Not Rooted. Phone is working as well.
Repeated second time. almost same message. Again stuck at white screen. still S-ON.
I have posted this on original thread as well. Hoping for a quick reply
Have you formatted the SD card before doing this?
Read the whole thread there were other users with the same problem and I think you will find the solution
Sent from my HTC Desire S using Tapatalk
amidabuddha said:
Have you formatted the SD card before doing this?
Read the whole thread there were other users with the same problem and I think you will find the solution
Sent from my HTC Desire S using Tapatalk
Click to expand...
Click to collapse
Hi
I did formatted my card. btw Method pops-up an error message on windows : "Device is S-ON" if i run from windows (ir reboots in bootloader).
It shows no error if i boot into bootloader before starting the flashing utility.
Nevertheless No result. Device is still S-ON. and When i try to go to recovery, Phone gets stuck at white screen. Does that mean it has flashed recovery and the recovery is not supported kinda (maybe old). Maybe thats why It was going to white screen after flash and going again if i manually choose recovery from bootloader.
xAutobot said:
Hi
I did formatted my card. btw Method pops-up an error message on windows : "Device is S-ON" if i run from windows (ir reboots in bootloader).
It shows no error if i boot into bootloader before starting the flashing utility.
Nevertheless No result. Device is still S-ON. and When i try to go to recovery, Phone gets stuck at white screen. Does that mean it has flashed recovery and the recovery is not supported kinda (maybe old). Maybe thats why It was going to white screen after flash and going again if i manually choose recovery from bootloader.
Click to expand...
Click to collapse
The device will remain S-ON. With HTC unlock you are able to flash recovery, kernel and even custom ROM. S-ON means that you cannot flash hboot and radio, but I do not think that you will need this in the near future (your hboot and radio are now the latest after the OTA)
Maybe you are on the right direction thinking that the recovery may be incompatible. So try this one - it is for Desire S. Extract the image and flash with Android Flasher
That did not work as well! Same getting stuck at white screen.
Then I gave a shot to CWM Recovery http://www.clockworkmod.com/rommanager Took the desire s one an VOILA!!! It worked in a second. Weird!
Anyways its S-ON + Rooted now.
1 quick (probably last), If i can do almost everything from Custom ROM etc, means I can now install TITANIUM Backup and get all my previous apps from backup right? No issues at all
I'd only need S-OFF to change HBOOT + Radio (I dont care). If i need to in future, I hope thats easy as well, right?
Your signature terrifies me about Sudden Death for Devices which were never S-OFFed! >.<
xAutobot said:
That did not work as well! Same getting stuck at white screen.
Then I gave a shot to CWM Recovery http://www.clockworkmod.com/rommanager Took the desire s one an VOILA!!! It worked in a second. Weird!
Anyways its S-ON + Rooted now.
1 quick (probably last), If i can do almost everything from Custom ROM etc, means I can now install TITANIUM Backup and get all my previous apps from backup right? No issues at all
I'd only need S-OFF to change HBOOT + Radio (I dont care). If i need to in future, I hope thats easy as well, right?
Your signature terrifies me about Sudden Death for Devices which were never S-OFFed! >.<
Click to expand...
Click to collapse
Now you can use everything that requires root without a problem. Just remember if you want to install a Custom ROM you should flash the kernel separately.
About changing HBOOT and RADIO there is a downgrade guide here that can give you S-OFF back when you need it in future.
And about my signature - the most Desire S are dying when pulling out the battery, so keep that in mind and you will be fine.
HTC desire s OTA update india
amidabuddha said:
Now you can use everything that requires root without a problem. Just remember if you want to install a Custom ROM you should flash the kernel separately.
About changing HBOOT and RADIO there is a downgrade guide here that can give you S-OFF back when you need it in future.
And about my signature - the most Desire S are dying when pulling out the battery, so keep that in mind and you will be fine.
Click to expand...
Click to collapse
I am using htc desire s in india. It is device from UK. I have not recd update of 2.3.5 yet. Contacted HTC india and htc UK but not got any satisfactory answer from them . Pls help for receiving the update. How can i do so? Is there any link for official RUU for android 2.3.5 with sense 3.0? Plssssssssssss...help
There are official RUU for both Asia / UK. Check the posts above. He included a link for RUU India. I can suggest to flash your device with that. All the Best!
Test
Sent from my HTC Desire S using XDA App
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?
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
Hi guys,
My sister sent me her HTC One SV aka K2-UL i offered her from expansys on june, it is stuck on Hboot
*** LOCKED***
K2_UL XA SHIP S-ON RL
HBOOT-2.00.0000
eMMC Boot
...
I can go to Fastboot USB ( or AC )
She 's worst than a noob so phone is stock, up to date but non-root non-unlock, still S-ON and so on.
just once phone reboot and stay stuck...
From here i can navigate but after reboot i'm still here.
I tried :
factory reset and recovery (with rom renamed PL80DIAG but would be too easy...)
RUU but RUU asked for bootloader so stuck on "waiting for bootloader"
go to htc dev to unlock bootloader but after flash unlock token ( unlock token check successfully) but : Nothing happens and still writtten ***Locked*** then if I "fastboot oem unlock" it says failed :<remote : loading custom splash failed>
fastboot flash boot.img but nothing works since still S-on and locked bootloader (superCID is out too)
flash custom recovey or even fresh stock recovery but nothing worked for the same reasons...
Do you guys have any idea of something i could do?
Thanks for your answer and forgive my English I'm French
As long as you are ***LOCKED*** you can quiet do nothing.
To use our available RUU you must also be unlocked & S-Off.
Somewhat the same situation
I am stuck here:
***Tampered***
***Unlocked***
K2_PLC_CL PVT Ship S-ON RL
HBOOT -1.01.0000
Radio - 1.12.00.0208
OpenDSP - v.7.2.0221.1123
eMMC - boot
Feb 8 2013, 16:29:40:-1
I can get into Fastboot as well as bootloader, I CANNOT GET INTO RECOVERY. I have tried to restore with the respective RUU files from the All things HTC ONE SV forum. I have also tried to flash the recovery boot and radio img files through fastboot usb. NONE of this has worked for me. I really enjoyed this phone before I went and made it all FUBR. If there is anyway to get it to boot to any recovery or rom, i will much appreciate it. Thanks for all your help from previous posts as well as any future help I get from information posted here.
Related to your hboot, you should be able to flash any recoveries, but i usually recommend this one.
What command do you use to flash recovery and do you get an output from "fastboot devices"?
Thedc24 said:
I am stuck here:
***Tampered***
***Unlocked***
K2_PLC_CL PVT Ship S-ON RL
HBOOT -1.01.0000
Radio - 1.12.00.0208
OpenDSP - v.7.2.0221.1123
eMMC - boot
Feb 8 2013, 16:29:40:-1
Click to expand...
Click to collapse
Oops you already are 4.2.2. I have a system.img and a boot.img that I can make into a rom.zip to flash via the OEM-RUU mode.
eduardog131 said:
Oops you already are 4.2.2. I have a system.img and a boot.img that I can make into a rom.zip to flash via the OEM-RUU mode.
Click to expand...
Click to collapse
HBOOT 1.01 is ICS (4.0.x).
Sent from my C525c using Tapatalk
Modding.MyMind said:
HBOOT 1.01 is ICS (4.0.x).
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Well then I was right then I was wrong. Sorry. HBOOT versions for the Sensation are stuck in my mind.
Sent from my HTC Sensation
Thanks a million for the replies. I was able to lead the recovery and get into it (the most progress i have had in a year with this phone). With that being done. When I go into recovery I am unable to mount the internal storage. I am not too sure of the procedures I need to go through to get this thing functional again. I have been tinkering with my S3 for the last few months, but with KNOX on now I am looking to Jump ship completely from both verizon and samsung. Enough rambling, Like I said thanks for the help, any assistance in getting this thing to boot to a ROM would be much appreciated.
BTW
I used the fastboot flash recovery recovery.img
I have tried this before with no success. This time it worked.
I also flased the Radio and Boot img for ICS.
Thanks.
Thedc24 said:
Thanks a million for the replies. I was able to lead the recovery and get into it (the most progress i have had in a year with this phone). With that being done. When I go into recovery I am unable to mount the internal storage. I am not too sure of the procedures I need to go through to get this thing functional again. I have been tinkering with my S3 for the last few months, but with KNOX on now I am looking to Jump ship completely from both verizon and samsung. Enough rambling, Like I said thanks for the help, any assistance in getting this thing to boot to a ROM would be much appreciated.
BTW
I used the fastboot flash recovery recovery.img
I have tried this before with no success. This time it worked.
I also flased the Radio and Boot img for ICS.
Thanks.
Click to expand...
Click to collapse
If you want I can just skip you to 4.2.2. You don't need to reflash recovery and stuff. I will make a package that will update HBOOT and radios. And system/boot.img.
Sent from my HTC Sensation
He first needs to be S-off, to flash radio & hboot. I have made a 4.1.2 rom for cricket, must be linked in my index thread. Wipe all, flash the rom, flash boot.imgwith fastboot and hope that little baby is booting.
If yes, use moonshine.io or rumrunner.us to get S-off.
Then we will do next steps.
old.splatterhand said:
He first needs to be S-off, to flash radio & hboot. I have made a 4.1.2 rom for cricket, must be linked in my index thread. Wipe all, flash the rom, flash boot.imgwith fastboot and hope that little baby is booting.
If yes, use moonshine.io or rumrunner.us to get S-off.
Then we will do next steps.
Click to expand...
Click to collapse
Wow! Awsome! This bad boy booted. I was able to flash the rom through recovery. This is much further than I expected to get with this device. Now when I try to go S-Off with either moonshine or rumrunner I get an error saying not able to make adb connection. When I use fastboot devices my device will show up...if i do adb devices nothing...Would love to have S-Off and SU installed. But like I said this is much further than I expected to get so anything further is icing on the cake. Thanks in Advance.
Is Usb-Debugging enabled?
Any output from adb devices? HTC Sync installed (for the drivers)?
old.splatterhand said:
Is Usb-Debugging enabled?
Any output from adb devices? HTC Sync installed (for the drivers)?
Click to expand...
Click to collapse
He can just use the Naked Driver for the adb driver. http://forum.xda-developers.com/showthread.php?t=2263822
Ok I DID have USB debugging enabled. After messing with the drivers and my Windows 8 computer, I have came to the conclusion that it is something with the drivers and their compatibility with Windows 8. Either way moonshine or rumnunner never worked for me in a windows 8 environment. I dual boot ubuntu 12.04 anyway, it saw my device just fine adb and fastboot. I ran moonshine and it went through all the testing stages, but was never able to completely run...so I still have no S-Off. Do I need to update Hboot or anything? Also am I able to load a custom rom on this device with S-ON? I have been looking but I do not see many out for this device at all, which is a shame because I feel as though it is very comparable to my GS3. It would be nice to see a nice AOSP ROM on this device. But all take any updates I can for the device, hopefully it will help with the issue I have will cell reception dropping all the time. Thanks
To answer some of your questions:
- you can't update hboot because you are not stock and not S-off
- there are indeed not much roms to flash, but you could do with S-on (and unlocked bootloader)
- if you would flash the Sense 5/Android 4.2.2 rom, you would have noizy sound, without the firmware files (which you need S-Off to flash)
Another way for getting S-off (which should work with your hboot), is facepalm.
But the part of changing CID to SuperCID is very risky, read carefully and only do, when you are sure you understand, what to do!!!
old.splatterhand said:
To answer some of your questions:
- you can't update hboot because you are not stock and not S-off
- there are indeed not much roms to flash, but you could do with S-on (and unlocked bootloader)
- if you would flash the Sense 5/Android 4.2.2 rom, you would have noizy sound, without the firmware files (which you need S-Off to flash)
Another way for getting S-off (which should work with your hboot), is facepalm.
But the part of changing CID to SuperCID is very risky, read carefully and only do, when you are sure you understand, what to do!!!
Click to expand...
Click to collapse
Thanks for all the help! I am now SuperCID with S-OFF, Facepalm worked like a charm. Would it be possible to put slimrom on this device? Anyway thanks for all the help, I am going to check out some ROMS..as far as flashing goes, I am assuming how I have my phone now I should be able to flash any rom that is compatible with the device.
---------- Post added at 05:46 PM ---------- Previous post was at 05:24 PM ----------
eduardog131 said:
If you want I can just skip you to 4.2.2. You don't need to reflash recovery and stuff. I will make a package that will update HBOOT and radios. And system/boot.img.
Sent from my HTC Sensation
Click to expand...
Click to collapse
Yea that would be cool. I am assuming I would just flash it through recovery?
Thedc24 said:
Thanks for all the help! I am now SuperCID with S-OFF, Facepalm worked like a charm. Would it be possible to put slimrom on this device? Anyway thanks for all the help, I am going to check out some ROMS..as far as flashing goes, I am assuming how I have my phone now I should be able to flash any rom that is compatible with the device.
---------- Post added at 05:46 PM ---------- Previous post was at 05:24 PM ----------
Yea that would be cool. I am assuming I would just flash it through recovery?
Click to expand...
Click to collapse
You're completely S-OFF? The radios and new HBOOT update need to be flashed in RUU mode. Let me get my bearings and you can flash everything. (adb reboot oem-42 or fastboot oem rebootRUU is a way to get to RUU mode.)
Sent from my HTC Sensation using Tapatalk
eduardog131 said:
You're completely S-OFF? The radios and new HBOOT update need to be flashed in RUU mode. Let me get my bearings and you can flash everything. (adb reboot oem-42 or fastboot oem rebootRUU is a way to get to RUU mode.)
Sent from my HTC Sensation using Tapatalk
Click to expand...
Click to collapse
Yes I am completely S-OFF with CID 111111 and SU. The phone has been working good, Cricket service is not all that great in my area. I see there is a software update 2.04.1050.5 (15.1 MB), I am assuming if i run this update it will most likely wipe everything I just did. Is this correct?
Thedc24 said:
Yes I am completely S-OFF with CID 111111 and SU. The phone has been working good, Cricket service is not all that great in my area. I see there is a software update 2.04.1050.5 (15.1 MB), I am assuming if i run this update it will most likely wipe everything I just did. Is this correct?
Click to expand...
Click to collapse
I think. Anyways, download this: http://www.mediafire.com/download/maa60jha4eod834/rom.zip
Contents of said rom.zip:
4.2.2 system.img with root.
4.2.2 stock boot.img.
4.2.2 stock recovery.
New HBOOT and radios and stuff.
If you get an error (flush again or something.), then just resend the command. (fastboot flash zip path/to/rom.zip)
eduardog131 said:
I think. Anyways, download this: http://www.mediafire.com/download/maa60jha4eod834/rom.zip
Contents of said rom.zip:
4.2.2 system.img with root.
4.2.2 stock boot.img.
4.2.2 stock recovery.
New HBOOT and radios and stuff.
If you get an error (flush again or something.), then just resend the command. (fastboot flash zip path/to/rom.zip)
Click to expand...
Click to collapse
Downloading now. I will let you know how it goes...thanks a million.
This is what I got when I tried to flash the rom:
sending 'zip' (691470 KB)...
OKAY [ 37.267s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 37.301s
I dont understand if I am S-Off and super CID.