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.
Related
Hi! This is my first post.
I have a HTC Sensation 4G and I cannot update the firmware.
My CID PG5811000
and MID BM___001
I read the post http://forum.xda-developers.com/showthread.php?p=21481563 And I got the same problem like the user AlphaX
But when I reboot my HTC to try to install I got a wrong MID message.
Any ideas?
Send HTC a mail with your problem to get a update any time.
Mit freundlichen Grüßen
would HTC help people who unlock the phone by themself?
I have S-Off and installed Insert Coin 4.06 Android 4.0.1
I tried to get SuperCID and it doesn't change.
Any ideas?
BTW. I wrote to HTC giving my serial number, CID and MID.
When I turn on my phone into Fastboot mode I got the next information
*** LOCKED ***
PYRAMID PVT SHIP S-OO RL
HBOOT-1.23.0000
RADIO-10.12.9007.21_2M
eMMC-boot
So, the "LOCKED" at the beginning loks weird.
Each time I enter to fastboot, try to look for a PG58 file
I'm still looking at google (and falling on xda forums )
But any help will be welcomed
Hi,
You can add your CID to the Firmware.
Try this:
1. Check your CID using fastboot getvar cid and MID using fastboot getvar mid or fastboot getvar cid
2a. If your CID and MID are supported by default, navigate to point 3.
2b. If your CID or MID is not supported by default, do this: (you do it at your own risk)
2c. Open PG58IMG.zip (don't extract it)
2d. Open android-info.txt in text editor
2e. Add your cidnum: <your CID> or modelid: <your MID> to the list, save file and close archive
3. Place PG58IMG.zip on your SD card
4. Boot your device holding power button + vol down button
5. Follow instructions on the screen
I hope it works
"LOCKED" means:
You're locked out of some of the most advanced fastboot commands. But that's it.
You still have S-Off. ADB will still work. You can flash ROM's.
Dav375
I got SuperCID!!!!
using fastboot I did it
./fastboot-mac oem writecid 11111111
Then I download the firmware from http://db.tt/EjYujYj7 (http://forum.xda-developers.com/showthread.php?t=1412618&page=96) and rebooting my HTC Sensation the update was successful!!!!
Now I hope to install new ROMs with ICS.
I have a sensation thats giving me two CID numbers.
If i use fastboot commands i get 11111111.
If i use CID getter i get VODAP001.
Phone is s-off, rooted and unlocked.
How can i get these the same?
The phone is downloading an ICS update but not installing it.
I've seen the same thing, your correct CID is the one you got through adb. CID getter for some reason throws up CID information stored elsewhere so you generally end up getting the CID the phone came with.
Given that you are SuperCID, why won't ICS install? What error(s) are you seeing?
goatee84 said:
I've seen the same thing, your correct CID is the one you got through adb. CID getter for some reason throws up CID information stored elsewhere so you generally end up getting the CID the phone came with.
Given that you are SuperCID, why won't ICS install? What error(s) are you seeing?
Click to expand...
Click to collapse
More accurately... Your correct CID is the one you get through:
Code:
fastboot getvar cid
If I use adb shell command:
Code:
getprop ro.cid
Then I get my original CID "T-MOB010"...
To the OP:
Go to your directory where adb and fastboot are, and type the following:
Code:
adb reboot bootloader
wait for bootloader to boot
Code:
fastboot oem writecid VODAP001
wait for it to flash
Code:
fastboot reboot-bootloader
wait for bootloader to boot
Code:
fastboot getvar cid
verify that the output is "VODAP001"
Code:
fastboot reboot
wait for device to reboot and you should be able to install your update if you're on an unaltered stock ROM...
Thanks for the replies.
It is the rom that came on the phone but i have removed some of the app's that Vodaphone pre-install, will this affect the up date?
Part of the error message was a problem with flickr which i did remove.
I would like a T-mobile ICS stock rom that is rooted as that is my provider, any suggestions?
I tried updating to 3.32 firmware but was getting boot loops, so downgraded again.
If you apply SuperCID, your phone has 2 CIDs:
the actual CID, which is 11111111
and the backup CID, which is a backup of the
cid the phone was before(shipped).
The backup CID is stored in the misc partition,
and i havent tried yet, but there are following fastboot cmds:
fastboot oem erasebcid
fastboot oem readbcid
fastboot oem writebcid
I think theyre the appropriate cmds for handling the bcid.
After deleting the backup CID the only CID left is the (main) CID.
BTT: If you want to apply a ICS RUU, I think you have to change your CID back
to stock, because the RUU checks for a T-Mob phone, which your phone isnt if
you have SuperCID ;D
After the RUU, you can SuperCID again.
Edit:
Have not read the first time:
If you want to install a T-Mobile RUU on a Vodaphone Device,
you have to set one of the following CIDs, matching the RUU best:
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
Greetz
criestr
ann-dr01d said:
Thanks for the replies.
It is the rom that came on the phone but i have removed some of the app's that Vodaphone pre-install, will this affect the up date?
Part of the error message was a problem with flickr which i did remove.
I would like a T-mobile ICS stock rom that is rooted as that is my provider, any suggestions?
I tried updating to 3.32 firmware but was getting boot loops, so downgraded again.
Click to expand...
Click to collapse
Your stock ROM must be unaltered... Restore those apps if you still have them.
Ok, so I can't find a compatible boot.img to flash via cmd in bootloader to restore my 2.3.5 original nandroid backup.
All I want to do is return to stock rom after which I will attempt downgrade and s-off because I'm tired of the restrictions and I couldn't care a less about my warranty etc.. I'll use either zerg rush or taco root depending on my software version which atm I have no idea of obviously..so I know to downgrade it's a different story..
Currently S-ON, HBOOT 2.00.0002 HTC UNLOCKED, REAPER 3.0(CM7) ROM Installed. 4EXT Recovery.
I have downloaded a compatible RUU which in my case is
RUU_Saga_S_HTC_Thailand_2.15.1113.2_Radio_20.4801.30.0822U_3822.10.08.04_M_release_226808_signed.exe
Checked by running fastboot getvar main-version: C:\WINDOWS\system32>fastboot getvar version-main
version-main: 2.15.1113.2 (and) CID HTC__058
So that is equal to what I have now on the phone (I also have another older RUU with hboot 98.00.000 for use with S-OFF'ing later...)
So becaue the RUU version is the same as my original can I just run the INSTALLER and let it do it's thing? And do I need to relock my bootloader first?
I have been reading and searching guides for hours, but nothing is clear to me, my wife is at my throat as well saying I've married my PC *you've probably heard it*
Has anyone done this before?
To save you some unnecessary steps:
1) Change the misc_version (look it up, it's a step in downgrading guide) under your current ROM (I assume you're rooted).
2) Lock the bootloader.
3) Flash the older (0.98 bootloader) RUU.
The correct answer for Jack_R1.
[GUIDE] Official HBOOT 2.00.0002 Downgrade to OLD HBOOT thanks Skanob
Some extra optimizations on the guide that bring it to my short version:
1. If you're using the correct RUU for your region - you can skip GoldCard step.
3,4. You don't have to flash stock rooted ROM if you know that you can reboot to bootloader and run the RUU while in fastboot mode. Your phone might not load the OS after locking the bootloader on non-stock firmware, but it won't matter, since all you need is fastboot.
If you're not familiar enough with what things do - follow the guide exactly, don't take shortcuts.
Now I have:
-Revolutionary-
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3805.04.02.01_M
eMMC-boot
Mar 10 2011, 14:58:38
I still didn't understand how things worked and was up another 4 hours mucking around, in the end after succeeding, I can't believe how easy it was.
I never even knew what zergrush and tacoroot were for exactly or which misc version number i should use.
In the end I went back to stock rom, unlocked again using my original token, flashed recovery and then Superuser. After that I didn't need zergrush etc to gain temp root(obviously), just changed misc version, rebooted, revolutionary to s-off and 'Bob's your Uncle'. Now I guess I should learn about the things I can do with s-off...(apart from not needing to fastboot flash boot.img every rom change)
I will elaborate on the things that confused me for others later, but right now, I'm off to work.
Thanks again Jack,
Now you might discover that unless you made some steps you didn't list, S-OFF won't work for you, and you'll still have to flash boot.img manually. If you didn't relock the bootloader and flash the RUU, that is. But I assume you did, and just skipped it on the list of things.
Zergrush or tacoroot are means to get temporary root - which is no good, since it doesn't stick after reboot, but it allows you this one time to change misc_version to allow downgrade. And any misc_version would do, as long as it's below the one you're flashing for downgrade. On MT4G, we usually set it for 1.00.000, that way you can't go wrong.
Glad you made it.
Embarrassingly, I do have problems still. After relocking and flashing the older RUU(HBOOT 0.98.000) successfully, I used Revolutionary to S-OFF. During the process the software asked me if i wanted to install clockwork Recovery, to which I answered 'no'. After that I tried to manually flash 'ext recovery' which I had before, so then I can flash 'Superuser.zip', but get an error message, I'm not sure why?
So I don't have root.
I'm at work now, when I get home all I can try is flash clockwork and see if that works.
*EDIT* Successfully flashed recovery-clockwork-5.0.2.0-saga.img and then superuser, perhaps the version of 4EXT recovery wasn't compatible or something...!? I can't be sure.
Restored Nandroid of previous Reaper 3.0, all is well.
My device used to be S-OFF hboot 6.98.0002.
but now is S-OFF Hboot 7.00.1002.
look : [HBOOT] | 29-05-2012 | 7.00.1002 | Reengineered 2.00.002
kyeeliu said:
My device used to be S-OFF hboot 6.98.0002.
but now is S-OFF Hboot 7.00.1002.
look : [HBOOT] | 29-05-2012 | 7.00.1002 | Reengineered 2.00.002
Click to expand...
Click to collapse
Thanks for the lead kyeeliu, but I have little idea what that can provide, I heard upgrading HBOOT can S-ON your phone again as well. Although I'll have a read and try to garner what I can...
My phone upgraded, but the S-OFF.
Because our mobile phone software unlock.If you use the official RUU upgrade will become S-ON.
We use modified HBOOT, there is no problem.
I currently use, and indeed as vampire36 said, the flash ROM no problem.
My Experience with S-OFF
First of all I want to thank Jack_R1 for his input and wisdom, even though I didn't really understand some things he mentioned, it all made sense in the end) as well as kyeeliu for his comments.
At first I didn't really trust many guides enough to follow possibly bricking my phone. I see too many people[READ:Beginners] with opinions and problems because some guides are not explained from a beginner point of view often offering instructions but little in the way of explanations for steps...., but in all fairness, this is also due to inexperience, or the users own failure to to make sure they followed everything correctly. Such is life...All in all happy to HAVE Guides, we can't really complain, just feel lucky ppl take time to write. And writing in DEPTH is bloody tiring when you hate typing as I do...
I believe NOONE should be attempting, however, to mess with their phone's inner workings until they've tried their best to assimilate all the information they can[ie:SEARCH]. I know it's time consuming and frustrating sometimes, but that onus is on you when you chose to 'take the plunge' so to speak..
I read for so many hours, wading through a disorganised sea of excited opinions READ:misinformation, good advice and hidden gems, but I was unable to discern what was best simply because I only had opinions and a sense of logic to dissasemble everything. In the end I followed a guide HERE by Skanob, it worked A-OK!
So this this is my Story of how I S-OFFED my Phone. By NO means extraordinary, :laugh:
Desire S - S-ON - HBOOT 2.00.0002 - CM7 ROM[Reaper 3.0]
*Note: I nandroid restored my original rooted rom first*
First of all the RUU. Noobspeak: It's just a version of your phones operating system in installer format, just like Windows XP is different[read:updated] to Windows 7, so is 1 RUU from another. Some are branded (have the carrier's logo) some are not (unbranded) Mine in particular was unbranded.
First you need to find out YOUR phones RUU, so to do this reboot your phone into Bootloader - Fastboot and then open command prompt on your PC and navigate to where you have adb and fastboot files located (I have copies of these files in windows\system32\ folder. When there type C:\WINDOWS\system32>fastboot getvar all. In this list of information look for these:
INFOversion-main: '2.15.1113.2' (and) INFOcidnum: 'HTC__053'
version-main is your phones current operating system version CID is your particular phones region(eg: HTC__058 = Thailand)
So This was my phone's current RUU:
RUU_Saga_S_HTC_Thailand_2.15.1113.2_Radio_20.4801.30.0822U_3822.10.08.04_M_release_226808_signed.exe
My current version has HBOOT 2.00.0002. I will need to downgrade this number to 98.00.000. I can do this by installing an older RUU that has HBOOT (98.00.000) I didn't know WHICH RUU that was so I just looked for an older RUU done by checking my current version_main '2.15.1113.2' and looking for something lower. I found: [RUU_Saga_HTC_Thailand_1.35.1113.2_Radio_20.28d.30.0805U_3805.04.02.01_M_release_183327_signed.exe]
I wasn't sure which HBOOT was inside (silly me) so i ran the installer just letting the first screen open up (which extracts all the files from the RUU to temp) and going NO further.. After that I went to 'Run' and typed in %temp% and looked for a recent folder with a long name which had the contens of the installer extracted. Amongst these files I found 'rom.zip' I opened it and inside could see the HBOOT file version 98.00.000_'other numbers'. This was my ticket :highfive: lol...
Now because my stock ROM was already rooted and I had previously flashed recovery all I needed to do was the -Modify the version of your phone- step in Skanob's Guide: (obviously I downloaded the attached misc_version file and as instructed created a new folder on C: called 'downsaga' and dropped misc_version inside)
Code:
adb push C:\downsaga\misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell
su
cd /data/local/tmp
./misc_version -s 1.27.405.6
exit
exit
This part of the code
Code:
./misc_version -s [COLOR="Blue"]1.27.405.6[/COLOR]
sets your phone to accept any RUU with a higher version than that number. I had no idea which number to put there exactly so I used 1.27.405.6 as well, noting it was lower than the RUU version I was going to install[1.35.1113.2] So it would be accepted.
Later Jack_R1 advised me to put 1.00.000 instead, and as he stated, "you can't go wrong". :good:
After setting the new version, I Re-locked my phone via command again using fastboot oem lock. I do not need root privileges anymore as I have already changed my misc_version [lower version] And the RUU installation needs phone to be relocked again before proceeding.
After that it's simply connect your phone to the PC and run the installer:
[RUU_Saga_HTC_Thailand_1.35.1113.2_Radio_20.28d.30.0805U_3805.04.02.01_M_release_183327_signed.exe]
I now had HBOOT 98.00.000. After that, a trip to http://revolutionary.io/ to S-OFF, and flash recovery file. If you choose during the S-OFF process to not install recovery you can do it manually afterwards as I did(I used recovery-clockwork-5.0.2.0-saga.img, because for some reason I got an error trying to flash 4EXT_Recovery_v2.2.7_RC5 which I previously had) Then I simply dropped Superuser-3.0.7-efghi-signed.zip on my SDCARD and installed via recovery, all done. Nandroid restore of my CM7, and that was it...
I remember many weeks ago just trying to achieve root was bewildering, trying superoneclick and 1 or 2 others methods that also failed me. Only to find all i had to do was flash a recovery file in fastboot, then install superuser. ... all the time I wasted...lolz.. thx to n0elite for that http://forum.xda-developers.com/showthread.php?t=1525100
On a side note: Please think again before reporting an error, and retrace your footsteps first. I have seen people reporting errors in forum such as: can't re-unlock my phone(yes, with the same Unlock_code.bin) simply because they were unwittingly in HBOOT instead of FASTBOOT, etc....
Now I'm well aware I could have done 'this or done 'that' etc differently and saved time etc..blah blah, and opions are welcome. I did not ,however, write this as a step-by-step Guide. Only as my personal experience, and yes, to many seasoned members minds I may have over explained, but this is because your so 733T and obviously I'm a slow learner perhaps, but I was mind-boggled so tried to write this from my own perspective as a 'virgin' flasher.
Peace!
twIIce
ok, THAT I can understand. Thanks a million!!!
yeeeeeeee, I've made it!!!
it was soooo simple! thank you mate!!!
This Guide will help you revert back to S-ON if you S-OFF with XTC Clip.
Confirmed working with and without SuperCID, With and without sim unlocked and i can confirm this method will work on ALL HTC devices supported with the old MTD.
This Guide runs the risk of bricking your device, Therefor i take no responsibility for your actions
Change CID on second post. im just ironing out some things then ill update the guide. Thanks.
S-ON :
1. Download RUU from here = DOWNLOAD
2. Run the RUU and get back to stock Rom ( make sure to enable usb debugging ( settings/applications/development )
3. Download SuperOneClick from here = SuperOneClick
4. Run it and select ZergRush then click root
5. Once rooted open up a CMD and CD into your adb folder
6. Once you are in your adb folder type adb devices and press enter
7. Now type adb shell and press enter ( you should now get a # sign in the terminal continue to step 8 )
8. Now type echo -e '[email protected]=7,1\r' > /dev/smd0 Your CMD window should now be back at the #
9. Your device is now S-ON with root to confirm reboot into bootloader and see it states S-ON
10. ENJOY !!!
If you don't currently have any ADB folder there is 1 attached below.
ADB FOLDER ( WITH HTC DRIVERS )
If this Guide helped you please dont forget to hit the thanks button. This was tested on GSM HTC Desire ONLY. i had stock CID HTC__001. I will try with super cid 2morrow and post a video. Thanks
Change CID From super CID back to a CID of your Choice
Welcome to my CID Guide.
This is NOT for SLCD DEVICES !!!!!
This guide will help you change your Super CID ( 11111111 ) back to its original eg: HTC__001.
Please use this guide ONLY if you understand what your doing. I take no responsibility for broken devices.
ENG Hboot can be flashed over by ANY Hboot Nexus One or Bravo. All Hboots have been repartitioned and are exact same sizes as Alpharev Hboots. This is because everyone is already used to these sizes but if you wish for a custom size please PM me and ill re partition for you and email you the Hboot. These Hboots have extended fastboot commands for changing CID and Backup CID
Now lets get to is shall we
1. Download The ENG Hboot located at the attachments section ( bottom of this post )
2. Flash the ENG Hboot with fastboot flash hboot ENG_Hboot_7.01.1111_Desire.img
3. Reboot your HTC Desire into Bootloader mode fastboot reboot-bootloader
4. now whilst still in Fastboot open up a CMD ( windows only ) and CD to your fastboot folder and type fastboot devices.
5. If your device was located now type fastboot oem changeCid xxxxxx ( replace xxxxxx with whatever your CID is find a list below )
5a. Please make sure when running the fastboot oem changeCid command you let it Finish DO NOT UNPLUG UNTILL IT HAS FINISHED.
6. Now on your device reboot back into bootloader and type fastboot getvar all and look for your new CID number
7. Now that you have changed your CID you can either stay on this Hboot or flash back to Desire Hboot.
If you wish to change your backup CID ( Somtimes this can be empty ( if backup was not created )
Run this in fastboot fastboot oem writebcid HTC__001 ( or whatever you want it to be ) [ Replace HTC__001 with your CID ]
Stock CID Numbers below:
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__M27
cidnum: HTC__032
cidnum: HTC__016
cidnum: 11111111
These are the CID numbers i know. I know there is hundreds more and as i find out more and more ill add to the pile. Thanks
or you can use this XTC Clip firmware to gain super CID PB99diag.nbh can be downloaded below. Please get a EMPTY sdcard ( format it 1st ) place the PB99diag.nbh file on the root of the sdcard and reboot into bootloader and follow instructions to clean s58 data
Thanks for using my guide, All stuff used can be downloaded from the attachments below. including stock alpharev hboot.
Re: [S-ON after XTC Clip] ( Tutorial ) Only GSM
So this ia basically getting s-on with the 2.3 RUU.
DigginGraves said:
So this ia basically getting s-on with the 2.3 RUU.
Click to expand...
Click to collapse
yes. but you can use ANY RUU you want. but MAKE SURE you run the RUU before you do this guide.
I posted this S-On long time ago. So it still working for everyone then?
But you've made a nice guide out of it.
How ever it only works for Wildfire, the other HTC's use a totally different MTD.
Super CID guide is now up on 2nd Post thanks
Guide is now up on 2nd Post thanks for all your support in the other thread
No problem.
Hi! Making this thread is kind of my last resort as I'm stuck in a good ol' bootloop. I would like to downgrade from Android 4.2 to the official rom it shipped with. I'm not familliar enough with the technical side of things to know why the RUU's I'm trying to flash won't work but i believe it's because I still have HBOOT 2.00.002.
First I tried Android Flasher to flash engHBOOToverARX.img to it (which should set it to 0.98.0000) but when i flash the window just stays empty and it executes nothing.
Then I followed this guide multiple times but then this happens:
Code:
C:\NEW>adb push zergRush /data/local/tmp
adb server is out of date. killing...
* daemon started successfully *
1098 KB/s (23060 bytes in 0.020s)
C:\NEW>adb push misc_version /data/local/tmp
1754 KB/s (589450 bytes in 0.328s)
C:\NEW>adb shell chmod 777 /data/local/tmp/zergRush
chmod: /data/local/tmp/zergRush: Not a directory
C:\NEW>adb shell chmod 777 /data/local/tmp/misc_version
chmod: /data/local/tmp/misc_version: Not a directory
I tried my best to search for solutions but no luck yet.
I'm trying to use this version (with the correct region and radio ofcourse) but during the installation it returns an error.
RUU_Saga_S_HTC_Europe_2.10.401.9_Radio_20.4801.30.0822U_3822.10.08.04_M_release_234765_signed.exe
I've tried other ones as well and also extracting the rom.zip/PH98IMG.zip and manually flashing it through recovery. This is what recovery returns:
Code:
Installing '/sdcard/PH98IMG.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Verifying zip signature...
E:Zip signature verification failed: 1
Error flashing zip '/sdcard/PH98IMG.zip'
Updating partition details...
E:Unable to mount '/data'
Samething with SetMainVersionLOW.zip using this guide, with the correct mainver number in the android_info file.
Together with trying the goldcard method I believe those are most of the things I have tried so far. My current details are:
UNLOCKED
Saga PVT SHIP S-ON RL
HBOOT-2.00.0002
Radio-3822.10.08.04_M
eMMC-boot
TWRP Recovery
I hope someone will try to help me out so maybe others in my situation can learn from my mistakes
man i was tired when i misread your post, you have already said you tried everything i sugested so ive deleted what i wrote to save further embarasment lol
Pixilume said:
Hi! Making this thread is kind of my last resort as I'm stuck in a good ol' bootloop. I would like to downgrade from Android 4.2 to the official rom it shipped with. I'm not familliar enough with the technical side of things to know why the RUU's I'm trying to flash won't work but i believe it's because I still have HBOOT 2.00.002.
First I tried Android Flasher to flash engHBOOToverARX.img to it (which should set it to 0.98.0000) but when i flash the window just stays empty and it executes nothing.
Then I followed this guide multiple times but then this happens:
Code:
C:\NEW>adb push zergRush /data/local/tmp
adb server is out of date. killing...
* daemon started successfully *
1098 KB/s (23060 bytes in 0.020s)
C:\NEW>adb push misc_version /data/local/tmp
1754 KB/s (589450 bytes in 0.328s)
C:\NEW>adb shell chmod 777 /data/local/tmp/zergRush
chmod: /data/local/tmp/zergRush: Not a directory
C:\NEW>adb shell chmod 777 /data/local/tmp/misc_version
chmod: /data/local/tmp/misc_version: Not a directory
I tried my best to search for solutions but no luck yet.
I'm trying to use this version (with the correct region and radio ofcourse) but during the installation it returns an error.
RUU_Saga_S_HTC_Europe_2.10.401.9_Radio_20.4801.30.0822U_3822.10.08.04_M_release_234765_signed.exe
I've tried other ones as well and also extracting the rom.zip/PH98IMG.zip and manually flashing it through recovery. This is what recovery returns:
Code:
Installing '/sdcard/PH98IMG.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Verifying zip signature...
E:Zip signature verification failed: 1
Error flashing zip '/sdcard/PH98IMG.zip'
Updating partition details...
E:Unable to mount '/data'
Samething with SetMainVersionLOW.zip using this guide, with the correct mainver number in the android_info file.
Together with trying the goldcard method I believe those are most of the things I have tried so far. My current details are:
UNLOCKED
Saga PVT SHIP S-ON RL
HBOOT-2.00.0002
Radio-3822.10.08.04_M
eMMC-boot
TWRP Recovery
I hope someone will try to help me out so maybe others in my situation can learn from my mistakes
Click to expand...
Click to collapse
First its PG88IMG not PH98IMG
Second, u need to relock ur bootloader for ruu to work. Boot into fastboot, open command window and type
fastboot oem lock
Thank you both for replying! Steve_htc_wizard: I'll try your way if all else fails!
jmcclue said:
First its PG88IMG not PH98IMG
Second, u need to relock ur bootloader for ruu to work. Boot into fastboot, open command window and type
fastboot oem lock
Click to expand...
Click to collapse
The problem is that when i relock I can't access recovery anymore to execute any zips. Adb doesn't connect to my device either eventhough I updated/installed the google USB driver (Android ADB Interface) and added my model ID into the .inf file. The HTC drivers aren't any miracle workers either.
Pixilume said:
Thank you both for replying! Steve_htc_wizard: I'll try your way if all else fails!
The problem is that when i relock I can't access recovery anymore to execute any zips. Adb doesn't connect to my device either eventhough I updated/installed the google USB driver (Android ADB Interface) and added my model ID into the .inf file. The HTC drivers aren't any miracle workers either.
Click to expand...
Click to collapse
If ur running a ruu PG88IMG method then u do NOT flash it in recovery, put the PG88IMG.zip on the root of ur sdcard (not in a folder) then boot ur phone into bootloader (vol down + power) and bootloader will find PG88IMG and ask to update. Follow instructions on screen.
It'll load PG88IMG.zip and proceeds to a second load bar but after 100% it'll pop back to the bootloader screen.
Pixilume said:
It'll load PG88IMG.zip and proceeds to a second load bar but after 100% it'll pop back to the bootloader screen.
Click to expand...
Click to collapse
Did u relock ur bootloader?
jmcclue said:
Did u relock ur bootloader?
Click to expand...
Click to collapse
Yes I did (RELOCKED, SAGA PVT SHIP S-ON RL, hboot 2.00.002).
Pixilume said:
Yes I did (RELOCKED, SAGA PVT SHIP S-ON RL, hboot 2.00.002).
Click to expand...
Click to collapse
Strange that it dont work. Try redownload the exe file and extract rom.zip but dont edit anything this time, just rename it to PG88IMG.zip and try that or try getting ur phone to connect to pc. Or try different ruu. Thats the only options i can think of. Getting ur phone to connect to pc is prob ur best bet.
jmcclue said:
Strange that it dont work. Try redownload the exe file and extract rom.zip but dont edit anything this time, just rename it to PG88IMG.zip and try that or try getting ur phone to connect to pc. Or try different ruu. Thats the only options i can think of. Getting ur phone to connect to pc is prob ur best bet.
Click to expand...
Click to collapse
Then i get the "Main Version is older! Update Fail!" error. I did make my sd card a goldcard and never formatted it, if that's any help. By the way...thank you for your replies so far!
Pixilume said:
Then i get the "Main Version is older! Update Fail!" error. I did make my sd card a goldcard and never formatted it, if that's any help. By the way...thank you for your replies so far!
Click to expand...
Click to collapse
A goldcard bypasses the cid check so thats good that u have it, use a ruu with a higher main version than the one ur trying to run. So ur trying 2.10.401.9 so download higher version.
To check what is on ur phone, boot into fastboot, plug into pc and open command window and type
fastboot getvar all
And ul see what version_main u have then just use ruu with the same or higher main version. Post the results here n we can see whats what
Hey, i've looked for a higher number download but cant seem to find one. What would be the next step? Should i edit the main version number with this misctool?
Code:
[B]C:\>fastboot getvar all[/B]
INFOversion-bootloader: 2.00.0002
INFOversion-baseband: 3822.10.08.04_M
INFOversion-main: 13.10.401.8
INFOproduct: saga
Pixilume said:
Hey, i've looked for a higher number download but cant seem to find one. What would be the next step? Should i edit the main version number with this misctool?
Code:
[B]C:\>fastboot getvar all[/B]
INFOversion-bootloader: 2.00.0002
INFOversion-baseband: 3822.10.08.04_M
INFOversion-main: 13.10.401.8
INFOproduct: saga
Click to expand...
Click to collapse
13.10.401.8? Never even seen that befor nor can i find ruu with that number.
If it were me id just run the ICS ruu and get it booting then if u want to use GB u can unlock ur bootloader, root then flash misc version and use older ruu. Probably quicker too
jmcclue said:
13.10.401.8? Never even seen that befor nor can i find ruu with that number.
If it were me id just run the ICS ruu and get it booting then if u want to use GB u can unlock ur bootloader, root then flash misc version and use older ruu. Probably quicker too
Click to expand...
Click to collapse
That sure works! I think i'll settle for ICS just for a while atleast. Thank you and other contributors for your help. People helping people is a rare thing :good: