Related
Hi please could somebody help me, I have a Desire S which I got on contract from 02 with a 02 branded rom on there originally and hboot 0.98.0002.
I had S-off, 4ext recovery, upgraded to hboot 2.00.0002 and a custom rom installed.
I have flashed a offical RUU RUU_Saga_O2_UK_1.31.206.1_Radio_20.28b.30.0805U_38.03.02.14_M_release_178935_signed.exe
and now I am stuck in hboot and it says **security warning** hboot version 0.98.000
I tried to flash the above o2 RUU again but it says bootloader version error, So I tried RUU 1.28, 1.47 and 2.10 with a gold card in the phone but the same error all the time.
I have also extracted the rom.zip from each of these and put it onto the goldcard renamed to PG88IMG.zip but then this says MAIN VERSION OLDER and will not flash.
Now I am really stuck on what I need to do, do I need to flash a 0.98.0002 hboot? as at the momment I have 0.98.000, if so how can I do this?
I have lost 4ext recovery, and back to S-On.
If anyone has any ideas I would be really grateful.
Thank you in advance
Cheers
edit: I think the bootloader I currently have on the phone 0.98.000 is incorrect ? , it should be 0.98.0000 or 0.98.0002? . As the hboot is S-ON is there anyway I can flash a hboot through using adb, or does it have to be S-OFF, if so is there anyway I can S-OFF in bootloader or fastboot alone, as I can't do anything else.
I think that the O2 RUU that you have used has an older hboot version (0.98.0000) than the version that was on your phone when you s-offed.
But with the Goldcard you should be able to flash it. So try another SDcard to create a goldcard, as far as I know not each one is suitable.
Do not try RUU for other brands/regions you may end up with a bricked device.
amidabuddha said:
I think that the O2 RUU that you have used has an older hboot version (0.98.0000) than the version that was on your phone when you s-offed.
But with the Goldcard you should be able to flash it. So try another SDcard to create a goldcard, as far as I know not each one is suitable.
Do not try RUU for other brands/regions you may end up with a bricked device.
Click to expand...
Click to collapse
Hi thanks for your reply, I currently have 0.98.000 hboot on the phone now which is S-ON. My gold card seems to be working as it doesn't say any CID errors.
How can I tell if my device is bricked?
I can only get into hboot, and fastboot/stock recovery. The phone won't do anything else and I can't flash any rom as it says about the bootloader version, but on the bootloader it says **security warning** at the top. Is there anyway I can flash a newer hboot? or won't it let me as it is S-ON, if its S-ON will I be able to flash a hboot or even 4ext recovery to flash a rom?
If so how can I s-off just using bootloader and fastboot?
I thought goldcard is only to bypass the CID checks so you can flash a debranded RUU.
It is not exactly clear: have you tried to extract the rom.zip from the O2 RUU, rename to PG88IMG.zip and flash in hboot?
Also you have to be completely sure that your version is the O2 one.
Follow the guide in my signature to make fastboot working on your PC.
Then connect your device to the PC while in the hboot. There should be 'FASTBOOT USB' written on the phone screen.
Then open a command prompt on your PC and type:
Code:
fastboot devices {your serial number should appear}
fastboot getvar all
Post here the output that is printed in the cmd.
amidabuddha said:
It is not exactly clear: have you tried to extract the rom.zip from the O2 RUU, rename to PG88IMG.zip and flash in hboot?
Also you have to be completely sure that your version is the O2 one.
Follow the guide in my signature to make fastboot working on your PC.
Then connect your device to the PC while in the hboot. There should be 'FASTBOOT USB' written on the phone screen.
Then open a command prompt on your PC and type:
Code:
fastboot devices {your serial number should appear}
fastboot getvar all
Post here the output that is printed in the cmd.
Click to expand...
Click to collapse
Hi, I have done the fastboot commands you said and below are the numbers I got:
fastboot devices - serial number which came up is: HT15NTJ00403
fastboot getvar version-main: 11.10.401.4
Can you help me?
Do you think my phone is bricked?
Thank you for your help with this
Try to put last rom.zip on sdcard with PG88IMG.zip name from version 2.10.401.8 RUU and maybe you will have new hboot 2.00.2002 and then have to unlock hboot from http://htcdev.com/.
first_damned said:
fastboot getvar version-main: 11.10.401.4
Can you help me?
Do you think my phone is bricked?
Click to expand...
Click to collapse
Cannot tell that it's bricked but now your software version is 2.10.401.4.
So you have to use a European RUU with the same version or higher. Probably you have debranded your device without an intention to do so.
Try with the RUU. If this is not working maybe you can try to flash hboot through the fastboot.
amidabuddha said:
Cannot tell that it's bricked but now your software version is 2.10.401.4.
So you have to use a European RUU with the same version or higher. Probably you have debranded your device without an intention to do so.
Try with the RUU. If this is not working maybe you can try to flash hboot through the fastboot.
Click to expand...
Click to collapse
Hi, I have tried RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_225161_signed.exe using the RUU on the laptop and tried extracting the rom.zip, renaming as PG88IMG.zip and flashing off sd card (goldcard), but the RUU said bootloader version error and flashing the PG88IMG.zip says main version older error.
There isn't a 2.10.401.4 version, but there is a
RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_219480_signed.exe
I would of thought the 2.10.401.8 should of worked?
also would I be able to flash a hboot being S-ON do you think?
I'm not sure how low my battery is also, If I plug it into the charger will it charge the phone on the bootloader do you know?
Thanks
All version info
INFOversion: 0.5
INFOversion-bootloader: 0.98.0000
INFOversion-baseband: 38.03.02.14_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 11.10.401.4
INFOserialno: HT15NTJ00403
INFOimei: 356708041449842
INFOproduct: saga
INFOplatform: HBOOT-7230
INFOmodelid: PG8810000
INFOcidnum: O2___001
INFObattery-status: good
INFObattery-voltage: 3851mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 361a7ba6
INFOhbootpreupdate: 12
INFOgencheckpt: 0
all: Done!
Ok so we have a nice mess here.
Your hboot and radio are still from the O2 RUU, but the main version changed to the European one. The cid is still O2 one (but with the goldcard it should not matter).
The security warning gives a chance that you are still able to have root.
So if you can enter the recovery you may be able to use adb as root.
Do the procedure, described here
If you can get the misc.img, after opening with Hex editor change the numbers to 1.31.206.1. Save the file, copy it to you SDcard and from adb flash it back:
Code:
dd if=/sdcard/misc.img of=/dev/block/mmcblk0p17
Then try the O2 RUU again.
Do not make attempts to change the hboot yet. Try the above and post back
The phone should be charging when you connect it to your PC.
amidabuddha said:
Ok so we have a nice mess here.
Your hboot and radio are still from the O2 RUU, but the main version changed to the European one. The cid is still O2 one (but with the goldcard it should not matter).
The security warning gives a chance that you are still able to have root.
So if you can enter the recovery you may be able to use adb as root.
Do the procedure, described here
If you can get the misc.img, after opening with Hex editor change the numbers to 1.31.206.1. Save the file, copy it to you SDcard and from adb flash it back:
Code:
dd if=/sdcard/misc.img of=/dev/block/mmcblk0p17
Then try the O2 RUU again.
Do not make attempts to change the hboot yet. Try the above and post back
The phone should be charging when you connect it to your PC.
Click to expand...
Click to collapse
Hi there, I have tried adb devices but it doesn't come up with my device which is strange. Maybe because my device is S-ON?
Do you think if I took it to a mobile repair shop and had it jtagged to restore original software would do the trick?
thanks
Both adb and fastboot commands are working on S-ON devices.
To use adb your device should be in Recovery mode (you can enter there from the hboot menu).
Of course you can bring it to a repair shop if you do not want to mess it yourself.
amidabuddha said:
Both adb and fastboot commands are working on S-ON devices.
To use adb your device should be in Recovery mode (you can enter there from the hboot menu).
Of course you can bring it to a repair shop if you do not want to mess it yourself.
Click to expand...
Click to collapse
Hi, I have entered recovery mode but thats where it says **security warning** at the top of the screen in pink. I have tried adb devices in cmd prompt but it says list of devices but nothing is listed. any idea why this is?
first_damned said:
Hi, I have entered recovery mode but thats where it says **security warning** at the top of the screen in pink. I have tried adb devices in cmd prompt but it says list of devices but nothing is listed. any idea why this is?
Click to expand...
Click to collapse
Obviously adb is not working in Recovery on S-ON devices. Sorry for misleading. I have just tried on my device, the adb works while booted to OS but not in Recovery.
I am afraid that doing anything further can brick the phone completely and the repair shop is your best option.
amidabuddha said:
Obviously adb is not working in Recovery on S-ON devices. Sorry for misleading. I have just tried on my device, the adb works while booted to OS but not in Recovery.
I am afraid that doing anything further can brick the phone completely and the repair shop is your best option.
Click to expand...
Click to collapse
I can't get adb to see the device, fastboot will do though but won't flash hboot, it says remote signature fail.
Looks like im going to have to send the phone off to be J Tagged. I have found a shop that does this for £24.99 and they know there stuff.
But if anyone has anymore ideas please let me know.
Thank you amidabuddha for your help, I will keep you updated on any progress.
Simon
You can repair it in HTC services or S-OFF again by Xtc-clip (as my HTC before).
Sent from my Desire S using xda premium
poppy8x said:
You can repair it in HTC services or S-OFF again by Xtc-clip (as my HTC before).
Sent from my Desire S using xda premium
Click to expand...
Click to collapse
Did the problem I have happen to you in the past also with the **security warning** ?
If so what did you do after s-off?
first_damned said:
Did the problem I have happen to you in the past also with the **security warning** ?
If so what did you do after s-off?
Click to expand...
Click to collapse
Yup, u can S-OFF your DS again by xtc-clip and then "security warning" is gone. But affter s-off by xtc-clip, u can't S-ON it. U can use custom rom only.
Sent from my HTC Desire S using xda premium
poppy8x said:
Yup, u can S-OFF your DS again by xtc-clip and then "security warning" is gone. But affter s-off by xtc-clip, u can't S-ON it. U can use custom rom only.
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
Sounds promising )
So did you s-off with xtc clip, then flash hboot to newer version, flash recovery (4ext or clockworkmod) and then flash a custom rom and all worked?
first_damned said:
Sounds promising )
So did you s-off with xtc clip, then flash hboot to newer version, flash recovery (4ext or clockworkmod) and then flash a custom rom and all worked?
Click to expand...
Click to collapse
Yeah. All worked. Look at my sig.
A month ago, i had "sercurity warning" too (i run RUU 1.48). Gold card coudn't do anything. And then i s-off by xtc-clip (in 5 mins)
Sry for my english bad.
Sent from my HTC Desire S using xda premium
Ok im not sure where to start but anyway
i have the vodafone ireland htc sense and few months back i rooted the phone but didnt change the stock mod.
every so often updates came out and i didnt update cuz it wouldnt allow me it would give me that error with the android fella and i would have to do something to fix it i forget what.
anyway
so last night i wanted to install THIS ROM (black forest)
http://forum.xda-developers.com/showthread.php?t=1423684
it said i needed to update the firmware and then thats when it went into a bootlooping
i fixed the eventual bootlooping but formatting just about everything but i backed everything up when i mounted
but now it doesnt load past the white HTC screen
in the recovery screen it says all this
*****LOCKED****
pyramid PVT SHIP s-off RL
HDBOOT-1.27.0000
Radio-10.14.9035.01_m
eMMC-boot
jane 13 2012,17:33:34
also when i load it it automatically looks for an image which i dont have any more
pg58diag.zip
edit:
i read and did this
You need to re-flash the ICS firmware from here --> http://forum.xda-developers.com/showthread.php?t=1412618
If it's an ICS ROM, flash the second one. If it's a Gingerbread ROM, flash the first one. Put the PG58IMG.zip on your SD card along with your ROM. Hold VOL-DOWN while you boot, and I think it asks you if you'd like to update (you do). You then need to remove the PG58IMG.zip from your SD card.
Boot into recovery after that and flash your ROM. If it still boot loops, that means you didn't flash the PG58IMG file correctly.
it says
cid incorrect update failed
stonedparadox said:
Ok im not sure where to start but anyway
i have the vodafone ireland htc sense and few months back i rooted the phone but didnt change the stock mod.
every so often updates came out and i didnt update cuz it wouldnt allow me it would give me that error with the android fella and i would have to do something to fix it i forget what.
anyway
so last night i wanted to install THIS ROM (black forest)
http://forum.xda-developers.com/showthread.php?t=1423684
it said i needed to update the firmware and then thats when it went into a bootlooping
i fixed the eventual bootlooping but formatting just about everything but i backed everything up when i mounted
but now it doesnt load past the white HTC screen
in the recovery screen it says all this
*****LOCKED****
pyramid PVT SHIP s-off RL
HDBOOT-1.27.0000
Radio-10.14.9035.01_m
eMMC-boot
jane 13 2012,17:33:34
also when i load it it automatically looks for an image which i dont have any more
pg58diag.zip
edit:
i read and did this
You need to re-flash the ICS firmware from here --> http://forum.xda-developers.com/showthread.php?t=1412618
If it's an ICS ROM, flash the second one. If it's a Gingerbread ROM, flash the first one. Put the PG58IMG.zip on your SD card along with your ROM. Hold VOL-DOWN while you boot, and I think it asks you if you'd like to update (you do). You then need to remove the PG58IMG.zip from your SD card.
Boot into recovery after that and flash your ROM. If it still boot loops, that means you didn't flash the PG58IMG file correctly.
it says
cid incorrect update failed
Click to expand...
Click to collapse
Hi,
You need to go HERE
Read the thread carefully,and it will guide you to which PG58IMG.zip you need for your phone.
Once you have flashed the appropriate firmware (PG58IMG.zip) it is important to delete the PG58IMG.zip from your sd card.
Then ,you can super wipe and flash your ROM.
right ill try this
but at the moment
when i get into recovery it loads the some file and it says wrong cid and it asks to reboot but it didnt
i dont have a card reader so im going to to a cafe of something
cheers for this
1. fastboot load into the bootloader and do:
fastboot getvar cid
fastboot getvar mid
If you don't have fastboot I have provided a download of it at the bottom of this post. Read the Read-Me file inside of it.
2. For those without fastboot you can use an app called CID Getter. CID is displayed at the top. MID is at the line ro.mid
This will not tell if you are SuperCID or not it just tells your original CID.
3. If you want to do it by terminal, open a terminal on the phone and do:
su
getprop ro.cid
getprop ro.mid
Click to expand...
Click to collapse
how to type IN fastboot?
stonedparadox said:
how to type IN fastboot?
Click to expand...
Click to collapse
Hi,
Fastboot is done on the pc,once you plugged your phone in with a USB.
If you cannot do this,then use method 2 or 3 .
i cant do 2 or 3
the link for the cidgetter is down
i got fastboot on my machine its just not recognizing my phone at the moment
edit:as far as i understand it here
http://androidforums.com/optimus-m-all-things-root/382525-guide-get-out-fastboot-mode.html
im supposed to get the phone drivers to see eachother but there not :/
stonedparadox said:
i cant do 2 or 3
the link for the cidgetter is down
i got fastboot on my machine its just not recognizing my phone at the moment
edit:as far as i understand it here
http://androidforums.com/optimus-m-all-things-root/382525-guide-get-out-fastboot-mode.html
im supposed to get the phone drivers to see eachother but there not :/
Click to expand...
Click to collapse
Hi,
You must have ADB installed on your PC in order to s-off
Use the same terminal on your PC to fastboot getvar cid
i do have adb installed but it looks like i dont have the right htc driver installed
when i type in fastboot getvar cid it says waiting for device
stonedparadox said:
i do have adb installed but it looks like i dont have the right htc driver installed
when i type in fastboot getvar cid it says waiting for device
Click to expand...
Click to collapse
Hi,
In order to make sure that you have the correct drivers,install the latest version of HTC Sync.
If it does not work the first time,close it all,then try again.
ok
cool
cid is vodaP001
mid is pg5813000
ok so i got it that working
its stuck on the HTC screen .. i assume i gotta put the mod i want in now right?
edit: i now need to super swipe and then add the mod and remove the update
stonedparadox said:
ok
cool
cid is vodaP001
mid is pg5813000
ok so i got it that working
its stuck on the HTC screen .. i assume i gotta put the mod i want in now right?
Click to expand...
Click to collapse
Hi,
Now You need to go HERE .Post # 2
Look for VODAPHONE Part 1:
DOWNLOAD 3.24 Unlocked: http://goo.gl/HWJJh
It has the PG58IMG.zip that contains:
cid is vodaP001
mid is pg5813000
Don't forget to thank Kohr-Ah for his efforts.
And flash that.Make sure it flashes fully(Including a reboot in the middle)
Then,delete the PG58IMG.zip,flash super wipe,then the new ROM.
ok ok
i got the dark forest os installed its just sim locked and in spanish
god damn
its in english just sim locked
is there a reason why my htc sensation wont see or read/see the nbh file in zip format on the sdcard while in hboot?
stonedparadox said:
is there a reason why my htc sensation wont see or read/see the nbh file in zip format on the sdcard while in hboot?
Click to expand...
Click to collapse
Hi,
It needs to be in the PG58IMG.zip format.
ok it reads it but i had to put it in a zip already used by something else in the phone and take out the stuff inside it
it gets as far as parses but then it stops
stonedparadox said:
its still not seeing the zip file
Click to expand...
Click to collapse
Hi,
It must be exactly PG58IMG.zip
Make sure there is no (1) in there
ok
so i did as you say
it gets as far as parsing and then stops ( that happens as soon as i enter the hboot screen )
if i go to install a zip it says
installing /sdcard/PG58IMG.ZIP
finding updating package
opening update package
installing update..
installation aborted
stonedparadox said:
ok
so i did as you say
it gets as far as parsing and then stops ( that happens as soon as i enter the hboot screen )
if i go to install a zip it says
installing /sdcard/PG58IMG.ZIP
finding updating package
opening update package
installing update..
installation aborted
Click to expand...
Click to collapse
Hi,
can i ask which PG58IMG.zip you are installing,and what you are trying to do?
ok
im trying to unlock my sim
Method 1 and method 2 dont work
http://forum.xda-developers.com/showthread.php?t=1192300
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
I see so many guides, but lots of information spread all over the place and much of it unclear. Hence, this guide. I hope everything is clear enough for someone completely new to understand, but also contains the information and resources to be useful to experienced members of these forums. If this is your first time attempting to flash your phone from stock (as you bought it), by the time you've read this post you should have the understanding of what steps to take and why you are doing them.
Prerequisites
First things first, things you will almost definitely need are
ADB and Fastboot as part of Google's platform-tools (16.0.2 windows, linux, macosx)
HTC's Drivers for Windows computers (here)
Android version number (Settings > System > About Phone)
HBoot version number (See hboot section)
USB debugging enabled (Settings > Applications > Development > USB debugging)
Fastboot disabled (Settings > Power > Fast Boot)
Your USB cable
You may also need
Your CID (Carrier ID, see hboot section)
Matching RUU for your carrier/region (Get here here, how to choose here and below)
A GoldCard (made from your SD Card, only needed if RUU for your carrier isn't available, see goldcard section)
Binary to get temproot (zergRush or tacoroot)
Binary to make your phone think it is a lower version number (misc_version_universal)
Revolutionary
Your phone's serial number (see hboot section)
Things you may want
A custom recovery (e.g. 4ext, zip)
An ENG hboot (0.98.2000, 2.00.2002, partition tables change so nandroid before, restore after)
signapk.jar to create a signed update.zip
To make life easy, I am going to assume that you have saved and extracted all files in the same directory as adb/fastboot.
You may decide to create a folder in the root directory of your computer's hard drive to put all these things in, e.g. C:\desires\
You will probably need an open command prompt or terminal on your computer at this location.
HTC Sync should not be installed on your computer as it can interfere with USB commands.
HBoot
To access your phone's hboot, disconnect any USB and power down your phone. Next, hold down the volume down button, then hold power down until the screen lights up. Release power before releasing volume.
Hboot is useful for flashing, getting information about your phone and running commands that you simply can't do from within Android.
Upon entering hboot, you should be confronted with a screen similar to one of these (left is hboot's bootloader, right is hboot's fastboot)
Code:
[COLOR="Magenta"]*** LOCKED *** *** LOCKED ***[/COLOR][COLOR="Green"]
SAGA PVT SHIP S-ON RL SAGA PVT SHIP S-ON RL
HBOOT-x.xx.xxxx HBOOT-x.xx.xxxx (PG8810000)
eMMC-boot RADIO-yyyy.yy.yy.yy_M
Jan 1 1970, 00:00:00 eMMC-boot
Jan 1 1970, 00:00:00[/COLOR]
[COLOR="Blue"]HBOOT[/COLOR]
[COLOR="Red"]FASTBOOT[/COLOR][COLOR="Orange"]
<VOL UP> to previous item
<VOL DOWN> to next item <VOL UP> to previous item
<POWER> to select item <VOL DOWN> to next item
<POWER> to select item[/COLOR]
[COLOR="Blue"]FASTBOOT[/COLOR]
[COLOR="Green"]RECOVERY[/COLOR] [COLOR="Blue"]BOOTLOADER[/COLOR]
[COLOR="Red"]FACTORY RESET[/COLOR] [COLOR="SandyBrown"]REBOOT[/COLOR]
[COLOR="Blue"]SIMLOCK[/COLOR] [COLOR="Purple"]REBOOT BOOTLOADER[/COLOR]
[COLOR="Black"]IMAGE CRC[/COLOR] [COLOR="Red"]POWER DOWN[/COLOR]
What information should you record here?
The HBOOT-x.xx.xxxx (this is your hboot's version)
Whether it says S-ON or S-OFF
Whether it says SHIP or ENG
If it says S-OFF,
You should already be able to flash a custom recovery via a PG88IMG.zip so you can skip ahead.
If it says SHIP, you may want to flash an ENG hboot.
If it says ENG, you may want to keep a backup of your hboot.
If it says S-ON,
If your android version was 4.0.4, you have to unlock the bootloader via htcdev.
If your hboot version is 0.98.0002 or lower, you can use revolutionary right away.
If your hboot is higher, you will need to downgrade by RUU before you can use revolutionary.
If you will be using revolutionary, you will need a few more bits of information.
If your screen looks like the one on the left, navigate to FASTBOOT and select it, and it will change to the one on the right.
Next, plug in your USB then in your command prompt enter the following commands;
Get your phone's serial number
Code:
fastboot devices
Get your phone's Carrier ID (for use with choosing RUU)
Code:
fastboot getvar cid
You have everything you need from here (for now) so power down or reboot your phone so it starts normally.
Temproot Requires Android 2.3.5 or lower.
This is useful if you have to downgrade your RUU. You will need your USB connected for this. You don't need to do this if you already have root, as the aim of temproot is to give you root until you next power down your device.
First, choose your weapon, zergRush or tacoroot. If one isn't working for you, use the other. Don't use both at the same time.
Using zergRush
Code:
adb push zergRush /data/local/tmp/zergRush
adb shell
chmod 755 /data/local/tmp/zergRush
/data/local/tmp/zergRush
shell will exit
Using tacoroot is a bit more complicated but works on more phones, you need to have gone into recovery at least once (tacoroot has command for this)
Code:
adb push tacoroot.bin /data/local/tmp/tacoroot
adb shell
chmod 777 /data/local/tmp/tacoroot
/data/local/tmp/tacoroot --recovery
Phone reboots to recovery, once it is there, reboot manually
Code:
adb shell /data/local/tmp/tacoroot --setup
Phone reboots again, if it stops at bootloader, choose reboot. It is now ready to be rooted
Code:
adb shell /data/local/tmp/tacoroot --root
You should now be rooted, to check this go back to shell
Code:
adb shell
exit
and look to see that there is now a # where there was a $.
If you have successfully got temproot, next is using misc_version. However, this is also a good time to install Titanium Backup, should you want to save any of your data. Busybox and superuser may also be required for Titanium to work, I didn't do it myself.
misc_version Requires root or temproot.
misc_version is used to trick your phone into thinking it is running an older version. Setting this number lower than the RUU you want makes the phone think the RUU is newer, and so lets it run.
Code:
adb push misc_version /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/misc_version -s 1.27.405.6
You should now be ready to downgrade by RUU.
RUU Requires misc set to lower version number. Will wipe your phone. Bootloader must be locked.
Choosing a RUU is quite simple, take the CID you found in the hboot section and compare it to this list of carriers
prank1 said:
vendor CID
SuperCID 11111111
AirTel-India ????????
Asia-HK-CHT HTC__622
ATT CWS__001
BM BM___001
Bouygues-Telecom BOUYG201
Brightstar-PTB BSTAR502
Brightstar-SPA BSTAR301
Chunghwa-Taiwan CHT__601
CT HTCCN702
CU HTCCN703
DCM DOCOM801
DOPOD DOPOD701
Era T-MOB009
Fastweb-IT FASTW401
GOOGLE GOOGL001
H3G-DAN H3G__F05
H3G-Italy H3G__402
H3G-ROI H3G__003
H3G-SWE H3G__G04
H3G-UK H3G__001
HTC-Asia-SEA HTC__037
HTC-Asia-SEA-WWE HTC__044
HTC-Australia HTC__023
HTC-BE HTC__E41
HTC-Czech HTC__C24
HTC-Denmark HTC__F08
HTC-Dutch HTC__E11
HTC-EastEurope HTC__032
HTC-ELL HTC__N34
HTC-FRA HTC__203
HTC-FRA-Bouygues HTC__247
HTC-GCC HTC__J15
HTC-GER HTC__102
HTC-India HTC__038
HTC-ITA HTC__405
HTC-Nor HTC__Y13
HTC-Norway HTC__H10
HTC-Poland HTC__B25
HTC-PTG HTC__506
HTC-Russia HTC__A07
HTC-Singapore ????????
HTC-SPA HTC__304
HTC-Sweden HTC__G09
HTC-Turkey HTC__M27
[*]HTC-WWE HTC__001
Hutch-Australia HUTCH001
O2-DE O2___102
O2-UK O2___001
Open-Channel HTCCN701
Optus-Australia OPTUS001
ORANGE-AT ORANG113
ORANGE-BE ORANG012
ORANGE-CH-FRA ORANG203
ORANGE-CH-GER ORANG104
ORANGE-ES ORANG309
ORANGE-French ORANG202
ORANGE-PL ORANGB10
ORANGE-PO ORANG008
ORANGE-SK ORANG006
ORANGE-UK ORANG001
Rogers ROGER001
SMC-Voda-HK SMCVD001
StarHub-Singapore ????????
TELEF-Spain TELEF301
Telstra TELST001
TELUS TELUS001
TIM-Italy TIM__401
TMA T-MOB102
TMCZ T-MOB004
TMD T-MOB101
TMH T-MOB007
TMHR T-MOB006
TMMK T-MOBL11
TMNL T-MOB003
TMSK T-MOB008
TMUK T-MOB005
TMUS T-MOB010
TWM-TW HTC__621
VIRGIN-UK VIRGI001
VODA-Africa-South HTC__016
VODA-Australia VODAP021
VODA-Germany VODAP102
VODA-Greece VODAP006
VODA-Ireland VODAP019
VODA-Italy VODAP405
VODA-Mobilkom VODAP120
VODA-Netherland VODAPE17
VODA-New-Zealand VODAP022
VODA-Portugal VODAPD18
VODA-Proximus VODAP024
VODA-SA VODAP026
VODA-SFR VODAP203
VODA-Spain VODAP304
VODA-Swisscom-DE VODAP110
VODA-Swisscom-FR VODAP212
VODA-Swisscom-IT VODAP416
VODA-Swisscom-WWE VODAP015
VODA-TR VODAPM27
VODA-UK VODAP001
Click to expand...
Click to collapse
Now go over to a repository of RUUs and select the oldest one for your carrier. If there isn't one, then try the generic one for your region (e.g. Europe/Asia/WWE).
The purpose of downgrading is to get an older hboot, so you will be looking for a RUU with version number 1.4x.xxx.x or lower.
There are a lot of SAGA RUUs hosted on androidruu.com androidfiles.org
If the install fails, you may need a goldcard (see GoldCard section) then come back here.
If the install works, go on to Revolutionary.
GoldCard
A GoldCard is used to make your phone ignore it's Carrier ID (CID) and branding when updating with a RUU. It, in effect, grants you "Super CID" whilst it is connected to your phone.
There are many ways to make a GoldCard, but not all SD cards work.
My preferred method uses the goldcard binary and is done with your phone connected by USB.
Code:
adb push goldcard /data/local/tmp/
adb shell chmod 777 /data/local/tmp/goldcard
adb shell cat /sys/class/mmc_host/mmc2/mmc2:*/cid > tcid
set/p cid= < tcid
del tcid
adb shell /data/local/tmp/goldcard -c %cid% -o /data/local/tmp/goldcard.img
adb shell dd if=/data/local/tmp/goldcard.img of=/dev/block/mmcblk1
Your SD card should now be a goldcard. Reboot and try running the RUU again.
Unlocking Bootloader Will wipe your phone. Don't do this if you're S-OFF.
This lets you flash a custom recovery and custom ROMs using a S-ON device. If you're able to use revolutionary or are already S-OFF, I advise against unlocking your bootloader. After this, when on a custom ROM that has been rooted, if you want to get S-OFF you can use misc_version, re-lock your bootloader and downgrade by RUU.
To unlock your bootloader, head over to htcdev.com/bootloader, choose "All Other Supported Models" and follow the steps it gives you. You can use the same adb and fastboot as linked in this guide.
You may want to backup /dev/block/mmcblk0p16 and /dev/block/mmcblk0p3 to your SD card (via dd) before unlocking, so you can see what is changed and in the future, if go on to S-OFF your device, attempt to lock as if it was never unlocked.
To re-lock your bootloader with fastboot, issue the following command (note that the device will remember that it was unlocked).
Code:
fastboot oem lock
Flashing Requires S-OFF or unlocked bootloader.
There are many ways to flash your phone; through recovery, using fastboot flash, fastboot flash zip, PG88IMG.zip and using dd. It is useful to know several methods as you may encounter a situation where one may not work but another will. A S-ON but unlocked device will still prevent some parts of the phone from being overwritten (e.g. hboot).
If you have reached here and just want to put a custom ROM onto your device, put the ROM's zip onto your SD card then the next step is to flash a custom recovery (usually via fastboot). After that, boot into the recovery and: 1. Backup your phone (savepoint), 2. Wipe the phone (clean start), 3. "Install from .zip" (flash ROM).
In all examples, I will demonstrate flashing "my_recovery.img" to the recovery partition.
By fastboot flash
Reboot to bootloader, select fastboot, connect USB, then
Code:
fastboot flash recovery [COLOR="Blue"][B]my_recovery.img[/B][/COLOR]
Wait for it to complete, reboot your device and it is done.By fastboot flash zip
This is the most similar to the method used by a RUU installer. It requires you to create a zip file as in the PG88IMG.zip for it to work, with the exception that you have the file on the computer and not on the SD card.
Reboot to bootloader, select fastboot, connect USB, then
Code:
fastboot oem rebootRUU
fastboot flash zip [COLOR="Red"][B]PG88IMG.zip[/B][/COLOR]
Wait for it to complete, reboot your device and it is done.By PG88IMG.zip
You create a zip file where the ".img" files are named the same as the partition you want to overwrite, and include an "android-info.txt" file to say "this is an important update".
File structure:
Code:
PG88IMG.zip
├android-info.txt
└[COLOR="Blue"][B]recovery.img[/B][/COLOR]
Example "android-info.txt"
Code:
modelid: PG8810000
cidnum:VODAP***
cidnum:VIRGI***
cidnum:T-MOB***
cidnum:TIM__***
cidnum:TELST***
cidnum:TELEF***
cidnum:eek:RANG***
cidnum:eek:2___***
cidnum:BOUYG***
cidnum:H3G__***
cidnum: HTC__***
mainver: 14.01.401.2
hbootpreupdate:13
DelCache:1
DelDevlog:1
Place the PG88IMG.zip file in the root of your SD card and reboot to bootloader. It will be automatically detected, preventing you from doing other actions whilst it is there. After it has flashed, remove or rename the file so that the bootloader won't detect it again next time.
Wait for it to complete, reboot your device and it is done.By dd
This is the only one done by adb (root environment, S-OFF) and the only one that lets you modify un-named partitions and skip version checks. It can also be done from recovery, but remember to mount /sdcard/ if you plan to use it.
Typing a wrong number when doing this can easily brick your phone, so some consider it the most dangerous method.
First, look up which block you want
Code:
mmcblk0p7 rcdata (still protected on revolutionary S-OFF)
mmcblk0p17 misc
mmcblk0p18 hboot
mmcblk0p19 splash1
mmcblk0p21 recovery
mmcblk0p22 boot
mmcblk0p25 system
mmcblk0p27 cache
mmcblk0p26 data
mmcblk0p28 devlog
mmcblk0p29 pdata
Then run the command
Code:
adb push [COLOR="Blue"][B]my_recovery.img[/B][/COLOR] /sdcard/
adb shell dd if=/sdcard/[COLOR="Blue"][B]my_recovery.img[/B][/COLOR] of=/dev/block/[COLOR="Red"][B]mmcblk0p21[/B][/COLOR]
(if you need to use su to get root, seperate "adb shell" from "dd" and "su" between them)
Wait for it to complete, reboot your device and it is done.
Backups Restores require S-OFF
Other than using your recovery's backup, you can also backup partitions through dd. This does not require S-OFF and is similar to flashing with dd but with the input and output paths the other way around.
For example, to backup your hboot as "my_hboot.img", find the block it is on (listed above) and run the command
Code:
adb shell dd if=/dev/block/[COLOR="Red"][B]mmcblk0p18[/B][/COLOR] of=/sdcard/my_hboot.img
If you are not going to be changing special partitions, normal backups made through your custom recovery are easier and store all your data.
update.zip Requires S-OFF or unlocked bootloader
An update.zip lets you interact with the filesystem as root without fully loading up Android via fastboot, stock recovery or custom recovery. It works in a similar way to PG88IMG.zip but with scripting, and the .zip needs to be signed.
The following is an example of how you might create an update.zip to root your device, grey entries are generated upon signing. Remember to include update-binary.
Code:
update.zip
├META-INF
│├com
││└google
││ └android
││ ├update-binary
││ └updater-script
│├[COLOR="Grey"]CERT.RSA[/COLOR]
│├[COLOR="Grey"]CERT.SF[/COLOR]
│└[COLOR="Grey"]MANIFEST.MF[/COLOR]
└system
└xbin
├busybox
└su
The updater-script contents for this example could be as follows below.
It is important to leave a blank line at the end of this file so that it works as expected.
Code:
mount("MTD", "system", "/system");
delete("/system/bin/busybox", "/system/xbin/busybox");
delete("/system/bin/su", "/system/xbin/su");
package_extract_dir("system", "/system");
set_perm(0, 0, 06755, "/system/xbin/busybox");
set_perm(0, 0, 06755, "/system/xbin/su");
unmount("/system");
To sign the zip, use signapk.jar with a pem certificate file and pk8 key file. You can generate your own or use the ones in the zip attached below.
Code:
java -jar signapk.jar certificate.pem key.pk8 update.zip update-signed.zip
Once signed, you have two choices of how to apply it
By recovery; place the update-signed.zip on the root of your SD card and rename it to update.zip. Now reboot into bootloader, choose recovery. If you're on stock recovery, you may be prompted by an exclamation mark here, hold volume up and volume down, press power and then release the buttons to proceed to the next screen. Now choose to apply update.zip.
By fastboot; boot into your bootloader, go to fastboot, and run
Code:
fastboot update update-signed.zip
The different commands you have available to you in updater-script are below
Code:
abort()
apply_patch(<source_file>, <targt_file>, <target_sha1>, <target_size>, <patch1_sha1>, <patch1>[, ..., <patchN_sha1>, <patchN>])
apply_patch_check(<file>, sha1_1[, ..., sha1_N])
apply_patch_space(<number_of_bytes>)
assert(<condition>)
delete(file1[, file2, ..., fileN])
delete_recursive(dir1[, dir2,...,dirN])
file_getprop(<property_file>, <key>)
format(<filesystem_type>, <partition_type>, <partition_or_device>)
[COLOR="Grey"]e.g. filesystem_type; "yaffs2", "ext4"
partition_type; "MTD", "EMMC"[/COLOR]
getprop(<key>)
ifelse(<condition>, <script_if_true>, <script_if_false>)
is_mounted(<mount_point>)
mount([<filesystem_type>, ]<partition_type>, <partition_or_device>, <mount_point>)
[COLOR="Grey"]e.g. filesystem_type; "yaffs2", "ext4"
partition_type; "MTD", "EMMC"[/COLOR]
package_extract_dir(<package_path>, <destination_path>)
package_extract_file(<package_path>[, <destination_path>])
read_file(<file>)
run_program(<program>, <arg1>[, .., <argN>])
set_perm(<user_id>, <group_id>, <mode>, <file1>[, <file2>, ..., <fileN>])
set_perm_recursive(<user_id>, <group_id>, <dir_mode>, <file_mode>, <dir1>[, ..., <dirN>])
set_progress(<fraction>)
sha1_check(<data>[, <sha1_1>, ..., <sha1_N>])
show_progress(<fraction>, <seconds>)
symlink(<target_path>, <link1>[, ..., <linkN>])
ui_print(<text1>[, ..., <textN>])
unmount(<mount_point>)
write_raw_image(<image_file>, <partition>)
Credits
xp314a, drivers
prank1, CID vendor list
Revolutionary, S-OFFing and zergRush
jcase, tacoroot
zryvffn, misc_version_universal
Google, adb and android
htcdev, bootloader unlocking
Many others
Thanks for reading, hope this clarifies a lot.
Please message me if you see any errors.
This
Is
Epic
:beer::beer:
Very nicely done :thumbup::beer:
how comes you've managed to accumulate all this knowledge? great formatted posting! where were you before XDA?
paul_robo?
Impressive work :thumbup:
Sent from my HTC Desire S using xda premium
ben_pyett said:
how comes you've managed to accumulate all this knowledge? great formatted posting! where were you before XDA?
Click to expand...
Click to collapse
I was not a member here before I joined.
All the knowledge is out there, much on xda, some across wikis and other forums, I accumulated it because rather than just blindly following a guide to S-OFF and flash my phone, I wanted to actually learn and understand what I was doing at each step.
Knowledge begets knowledge.
As for posting it, I was a little surprised to see nobody had compiled all the information I was looking for together, it was either guides based on more guides, or odd posts spread across the internet. I saw a gap so filled it!
How to Root.
Frndz here is my htc Desire HD Information,plz tell me the right way to root it?:crying:
shahzaib8711 said:
Frndz here is my htc Desire HD Information,plz tell me the right way to root it?:crying:
Click to expand...
Click to collapse
Try looking in your device forum this is for the desire s (saga).
"You learn something new every day if you're not careful" - Wilf Lunn
Very very helpful for a newbie like me, thanks for this.
shahzaib8711 said:
Frndz here is my htc Desire HD Information,plz tell me the right way to root it?:crying:
Click to expand...
Click to collapse
you need to unlock bootloader, then flash custom recovery (for example CWM or 4EXT) via fastboot, then flash superuser flashable zip via recovery
EXCELLENT! Just installed a new ROM and a Desire S for the first time, and this was a lifesaver
(One minor correction: think you need to chmod misc_version before you run it, at least I did.)
dbdkmezz said:
EXCELLENT! Just installed a new ROM and a Desire S for the first time, and this was a lifesaver
(One minor correction: think you need to chmod misc_version before you run it, at least I did.)
Click to expand...
Click to collapse
Thank you for pointing this out! I've updated that section to include a chmod, along with some other minor changes throughout. Please keep letting me know if you spot other things that are not clear / wrong. I want this to be the highest quality possible for people who aren't just looking for a 1-click solution.
Hmm I have just purchased an HTC Desire S, and it comes Locked and S-off. I think I only need to flash a custom recovery to start playing, but after entering the command, it says "not allowed"
Should I try to unlock my bootloader?
blackhawk_LA said:
Hmm I have just purchased an HTC Desire S, and it comes Locked and S-off. I think I only need to flash a custom recovery to start playing, but after entering the command, it says "not allowed"
Should I try to unlock my bootloader?
Click to expand...
Click to collapse
Yh u must still unlock bootloader
Hi everyone,
Not sure it this is the right topic or not...
I have been searching flashable zip of stock rom (ICS) of our beloved desire s. i found GB ones but not ICS. If anyone has it or knows the link, please share it. I want to return to stock!!...I am on hboot 2.02...Thanks in advance.
jmcclue said:
Yh u must still unlock bootloader
Click to expand...
Click to collapse
Unlocking the bootloader should not be necessary if the device is S-OFF, it's likely something else was going on if there was a "not allowed" error. Remember, S-OFF opens up the device more than unlocking it does.
suresh86 said:
Hi everyone,
Not sure it this is the right topic or not...
I have been searching flashable zip of stock rom (ICS) of our beloved desire s. i found GB ones but not ICS. If anyone has it or knows the link, please share it. I want to return to stock!!...I am on hboot 2.02...Thanks in advance.
Click to expand...
Click to collapse
The stock ICS was never properly completed and released unfinished. If you want ICS or newer, it's a much better choice to go for a custom ROM.
The HTC UI is called "Sense". If the reason you're looking for stock is the feel, then any custom Sense ROM will be similar.
Great guide ty for making one.
Please add info about revolutionary bc when you got beta key it can contain upper case and lower case.Problem is when you got l (lower L) and I (upper i) in same beta key.I got that problem and after a while I copied key to notepad (or word), select it and changed font to see difference then I got my phone S-OFF via revolutionary.
paulie-uk said:
Unlocking the bootloader should not be necessary if the device is S-OFF, it's likely something else was going on if there was a "not allowed" error. Remember, S-OFF opens up the device more than unlocking it does.
Click to expand...
Click to collapse
Yes i know exactly what s-off is. Basically, i know from experience that when ur phone is s-off and then lets say u go to sell the phone and u put it back to stock (ruu) ur bootloader will become locked again but still s-off, and to flash lets say recovery in fastboot, it will say something like remote error not allowed bla bla bla, so then u unlock bootloader via htcdev and then ul be back to full s-off and u can flash away mad. I know this because i had to do it with my sensation (twice) and desire. Soo im guessing that the person who he baught the phone off, flashed a ruu to sell the phone, hence the locked & s-off.
Hey guys,
I have a serious problem with my at&t htc one x, first time when i wanted to install a custom rom, i didn't backup ( i know my fault)
i had some problems with installation that drives me to change my cid to HTC_621 ( i don't know why i changed the 1st time, im noob)
now i can only install custom roms like viperXL and also,but it drains my battery,so i want to go back to stock room, or CM10.2 but i can't, when i try RUU it always give me an error, and when i downloaded the CM10.2.zip and tried to flash it via twrp it says Installation Failed. im totally confused and need real help.
my HBOOT infos:
Tampered
Unlocked
EVITA PVT SHIP S ON RL
HBOOT 1.14.0002
RADIO 0.19as.32.09.11_2
OpenDSP-v29.1.0.45.622
eMMC-boot
Jun 11 201. 14:36
What's your Cid? It should be 1111 etc.. Make sure ur super cid, then s- off.. After following those steps then try running the RUU
Sent from my Nexus 4 using XDA Premium 4 mobile app
zinter95 said:
Hey guys,
I have a serious problem with my at&t htc one x, first time when i wanted to install a custom rom, i didn't backup ( i know my fault)
i had some problems with installation that drives me to change my cid to HTC_621 ( i don't know why i changed the 1st time, im noob)
now i can only install custom roms like viperXL and also,but it drains my battery,so i want to go back to stock room, or CM10.2 but i can't, when i try RUU it always give me an error, and when i downloaded the CM10.2.zip and tried to flash it via twrp it says Installation Failed. im totally confused and need real help.
my HBOOT infos:
Tampered
Unlocked
EVITA PVT SHIP S ON RL
HBOOT 1.14.0002
RADIO 0.19as.32.09.11_2
OpenDSP-v29.1.0.45.622
eMMC-boot
Jun 11 201. 14:36
Click to expand...
Click to collapse
Why did you change the CID to HTC__621? That doesn't even look like it's for our device. That's the reason the RUU is failing.
The reason cm10.2 won't boot is because you need to RUU to 3.18 with the 2.14 hboot to flash that ROM, it does state that clearly in the install instructions for that ROM.
You're gonna need to get SuperCID first, then you can get s-off, then you can RUU to 3.18, then you can flash the cm10.2 ROM.
Sent from my Evita
I tried to SuperCID but i couldnt, i tried the hex editor way, but it gives me always errors, i guess thats why i can s-off.
Any solutions?
Ok, but why did you change it HTC__621? I don't think that's a CID for our device, were you trying to install software or something? The only problem is that without s-off you can only manually change the CID once, and you've used that one chance up by changing it to HTC__621. As far as a solution goes I'm not sure, there are a few different methods to change your CID, I'd suggest you try them all.
Sent from my Evita
zinter95 said:
I tried to SuperCID but i couldnt, i tried the hex editor way, but it gives me always errors, i guess thats why i can s-off.
Click to expand...
Click to collapse
SuperCID is mandatory for the s-off method. So yes, that is why you can't s-off.
i changed my cid to 11111111 now, but i still cannot change it to s-off i followed the instructions but i always failed.
You need to give more info. Where in the process did it fail?
Sent from my Evita
At the first time i failed when i type that code;
Code:
adb push soffbin3 /data/local/tmp/
adb shell chmod 744 /data/local/tmp/soffbin3
adb shell su -c "/data/local/tmp/soffbin3"
and when i wanted to try another time it keeps failing in the step before that one.
You're not being very specific, just saying it fails doesn't help diagnosing the problem.
Have you extracted the soffbin zip into the fastboot folder as per the instructions? Do you have usb debugging enabled in developer options? If applicable (on aosp ROM) have you granted adb root access in developer options?
When you say the step before that one, you mean the fastboot flash zip command right? And my guess is that you're getting error 99 instead of error 92? If you get error 99, force a reboot into the bootloader (by holding volume down and power) and start again from the beginning.
Sent from my Evita
timmaaa said:
You're not being very specific, just saying it fails doesn't help diagnosing the problem.
Have you extracted the soffbin zip into the fastboot folder as per the instructions? Do you have usb debugging enabled in developer options? If applicable (on aosp ROM) have you granted adb root access in developer options?
When you say the step before that one, you mean the fastboot flash zip command right? And my guess is that you're getting error 99 instead of error 92? If you get error 99, force a reboot into the bootloader (by holding volume down and power) and start again from the beginning.
Sent from my Evita
Click to expand...
Click to collapse
heey, im in this step right now
adb push soffbin3 /data/local/tmp/
adb shell chmod 744 /data/local/tmp/soffbin3
adb shell su -c "/data/local/tmp/soffbin3"
any time i run that command it says Device offline or device not found, but i have the latest updates of htc synmanager ..
im running RageXl 1.03 ROM.
How can i solve it please?
Uninstall HTC Sync Manager but leave the drivers installed. Make sure you have usb debugging enabled in developer options. When you try again you might get error 99 instead of error 92 after flashing the zip st the beginning. If this happens, force a reboot back to bootloader by holding volume down and power and start again from the beginning of the process.
Sent from my Evita
timmaaa said:
Uninstall HTC Sync Manager but leave the drivers installed. Make sure you have usb debugging enabled in developer options. When you try again you might get error 99 instead of error 92 after flashing the zip st the beginning. If this happens, force a reboot back to bootloader by holding volume down and power and start again from the beginning of the process.
Sent from my Evita
Click to expand...
Click to collapse
i uninstalled htc syn manager but it still telling me device offline!!!!!!!!!!!!!!!!!
Wow, that's a lot of exclamation marks. Maybe you need to try on a different ROM. Check your drivers, check adb, make sure usb debugging is enabled. It's almost impossible for me to diagnose what's going on without being there, you need to troubleshoot it.
Sent from my Evita
timmaaa said:
You're not being very specific, just saying it fails doesn't help diagnosing the problem.
Have you extracted the soffbin zip into the fastboot folder as per the instructions? Do you have usb debugging enabled in developer options? If applicable (on aosp ROM) have you granted adb root access in developer options?
When you say the step before that one, you mean the fastboot flash zip command right? And my guess is that you're getting error 99 instead of error 92? If you get error 99, force a reboot into the bootloader (by holding volume down and power) and start again from the beginning.
Sent from my Evita
Click to expand...
Click to collapse
Heey,
I installed an aosp rom, and everything was going alrgiht until the last step , the last command;
C:\Android>adb shell su -c "/data/local/tmp/soffbin3.zip"
/data/local/tmp/soffbin3.zip[2]: ┴¹Í♣î¶: not found
/data/local/tmp/soffbin3.zip[4]: syntax error: '³' unexpected
/data/local/tmp/soffbin3.zip[2]: ©╚ÇÎ⌂idþº╬R░4↔´NØU÷Å┘)È¿jØ&j+ò╩U¿PñF╩‗ÇTAäBÑJÇJ
ôç
►╝D<B}░wYQéäèÈ─ï¨╬▄;╗wªnEÃ>{¯╣þþ×{¯╣?þ╣╣┼yMË╚*ö: not found
/data/local/tmp/soffbin3.zip[2]: ┘ªnc↕♂mè◄←ßîÃÚ: not found
/data/local/tmp/soffbin3.zip[2]: can't create │╗▒Î÷: Read-only file system
/data/local/tmp/soffbin3.zip[2]: ô♦ý☻─Q└: not found
/data/local/tmp/soffbin3.zip[2]: ª↕Wê2└Ù}▄G╗2öó^*▲ñ¹®ç♦/│.×: not found
C:\Android>
i dont know whats the problem, may you help me?
What language and locale is your Windows and phone set to?
To me it looks like an application that does not correctly handle non-English locales.
Or something is corrupt.
twistedddx said:
What language and locale is your Windows and phone set to?
To me it looks like an application that does not correctly handle non-English locales.
Or something is corrupt.
Click to expand...
Click to collapse
my phone is set to english and my computer to french!but i dont think thats the problem.
anyone can help me guys??
You've entered the command incorrectly. There should be no ".zip" at the end of the command. Because of this I'm also assuming you haven't extracted (unzipped) the soffbin zip file into your adb/fastboot folder? Read the instructions on the s-off thread again, you must follow them absolutely precisely with no deviations.
Sent from my Evita
timmaaa said:
You've entered the command incorrectly. There should be no ".zip" at the end of the command. Because of this I'm also assuming you haven't extracted (unzipped) the soffbin zip file into your adb/fastboot folder? Read the instructions on the s-off thread again, you must follow them absolutely precisely with no deviations.
Click to expand...
Click to collapse
Yeah, when modding your phone, don't improvise or add things, unless you are positive of what you are doing. Folks have bricked their phones by not following instructions exactly.