Database Info

Radio S-OFF and SuperCID coming to a Desire HD near you

Just like the G2 (vision) we can now get radio s-off and superCID on our devices . there is also the chance of a sim unlock this way (i cant verify this working on the ace as mine is unlocked)
LOOK AT THE CID
#
INFOversion: 0.5
#
INFOversion-bootloader: 0.85.2007
#
INFOversion-baseband: 26.03.02.26_M
#
INFOversion-cpld: None
#
INFOversion-microp: 0438
#
INFOversion-main: 1.32.405.6
#
INFOserialno: HT0AXXXXXXXX
#
INFOimei: XXXXXXXXXXXX
#
INFOproduct: ace
#
INFOplatform: HBOOT-7230
#
INFOmodelid: PD9810000
#
INFOcidnum: 11111111
#
INFObattery-status: good
#
INFObattery-voltage: 3803mV
#
INFOpartition-layout: Generic
#
INFOsecurity: off
#
INFObuild-mode: ENG
#
INFOboot-mode: FASTBOOT
#
INFOcommitno-bootloader: 7eafc656
#
INFOhbootpreupdate: 11
#
INFOgencheckpt: 0
Click to expand...
Click to collapse
Although the steps are almost identical to the Visions method I would not recommend it yet. there are some simpler / safer tools on there way
[What Is Radio S-OFF ?]
Basically what we have at the moment is an ENG hboot that is ignoring the securflag value .... which means if you update an official RUU or just to a shipping hboot you will lose S-OFF. But with this you will always be s-off and therefore no matter what you wont have write protected eMMC even on a shipping hboot
[What Is SuperCID ?]
The CID (Carrier ID) is a string that the hboot looks at to see what RUU's you can flash i.e HTC__001 can flash WWE roms and VODA only Vodafone roms. With SuperCID (11111111) we can flash any rom from anyone
[Credits]
All the devs in #g2root that contributed I helped in no way to this hack it was all other devs im just relaying the info to the DesireHD users many many thanks .... although i was the first person to do the radio S-OFF on the DesireHD (ace)
[One More Warning]
Just to repeat i advise against trying to radio s-off with the g2 guide at this time as the method is messy and has a real chance of really messing things up .... if u try this now u are on your own ..... really
MODs ill replace this with a full guide when the method is safer

thanks apache the procedure is simliar to the "original" permroot/S-off process I see the only difference is probably the kernel, where I assume you used your own kernel mod/modified the vision CM kernel alongside a modified WPTHIS to match your kernel adaptation to make it work?!

As far as I understood it, this method patches radio to achieve S-OFF, SuperCID and unlock.
So, flashing a RUU or applying an OTA would revert this procedure?

Hi,
nevertheless could be the SuperCID independent from kernel,
as in older devices (HTC Hermes).
with friendly greet
starbase64

Closed for now so Dev can work his magic and we don't get 1000+ posts saying "thank you..this will be epic"
Apache...contact me when you are ready for me to re-open
Cheers,
M_T_M
Your friendly Mod

Update error

Hi guys I have problem in updating the new ruu 1.45.401.2 . Currently I am running 1.35.401.1. I am from Bahrain . I had my stock ROM 1.34.xx.xx . I had recently updated ruu Europe 1.35.401.1 downloaded from xda it didn't had any error it installed and working fine.and I am not rooted . but today I downloaded 1.45.401.2 from xda but it gives me error 131. Can any one help me to update to 1.45.401.2.
Sent from my HTC Sensation Z710e using XDA App

Probibly due to cid. Wait for the fota
Sent from my HTC Sensation Z710e using XDA App

But still I have a doubt.. if it is cid problem then ruu europe 1.35.401.1 should have also give the same error right. I again flashed 1.35.401.1 still no errors but why in new ruu 1.45.401.2 gives error 131.
Sent from my HTC Sensation Z710e using XDA App

RUU_Pyramid_HTC_Europe_1.45.401.2_Radio_10.56.9035 .00U_10.14.9035.01_M_release_208857_signed
can any body tel me wat is this M stands for ?
as i had observed in ruu europe 1.35.401.1 it is M3 but in ruu europe 1.45.401.2 it is Simply M.

Maybe I'm wrong in some part, as I couldn't find any tutorials pointing out those things. I just discovered this. If I'm wrong in anything I said, please anybody put me on the right track
So,
Open up CMD and write:
cd C:\adb {assuming that you have adb folder containing adb.exe and fastboot.exe}
Then write:
Code:
adb reboot-bootloader
Press enter, and wait until your phone gets into bootloader.
Then write:
Code:
fastboot getvar cid
Press enter.
Doing so, will retrieve the CID number of your device, note it down.
Mine for example, is: HTC__J15
- Open your RUU that you're not able to flash, wait untill you get to the "View Readme" page where there is the picture of an HTC device.
- Go to your temp folder (Generally on Win 7 it's in "C:\Users\USERNAME\AppData\Local\Temp")
- Look manually for folders that have lots of characters in that format: "{XXXXXX-XXXX-XXXX-XXXX-XXXXXXXX}".
- One of them should have another folder in it and 2 files, this folder should be in that same format "{XXXXXX-XXXX-XXXX-XXXX-XXXXXXXX} too.
- There should be in that folder something named "rom.zip", open it up and you should find a file named "android-info.txt".
- Open up "android-info.txt" with any text editor, it should say on the second line: "cidnum: XXXXXXX".
- This is supposed to be the same as the CID you got from your device, if not, to be able to install this RUU, you should change your CID to a super CID or to the CID that is written in "android-info.txt".
I do not recommend changing your CID and I take no responsibilities if you do so.
Do anything to your device at your own risk. I, personally didn't change my CID number.
P.S: Note down your old CID, before ever changing to SuperCID or to any other one.
Hope it helped
Good luck

thanks mate.. i have checked the cid numbers in the rom will post it here it ll be helpful for others also.
modelid: PG5813000
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__032
cidnum: HTC__102
cidnum: HTC__Y13
cidnum: HTC__203
cidnum: HTC__405
cidnum: HTC__N34
cidnum: HTC__304
cidnum: HTC__A07
cidnum: HTC__016
mainver: 1.45.401.2
hbootpreupdate:12
DelCache:1
this is wat i got in that file .
i think the phones having above cid numbers can update without problems.

raghavendrenk said:
thanks mate.. i have checked the cid numbers in the rom will post it here it ll be helpful for others also.
modelid: PG5813000
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__032
cidnum: HTC__102
cidnum: HTC__Y13
cidnum: HTC__203
cidnum: HTC__405
cidnum: HTC__N34
cidnum: HTC__304
cidnum: HTC__A07
cidnum: HTC__016
mainver: 1.45.401.2
hbootpreupdate:12
DelCache:1
this is wat i got in that file .
i think the phones having above cid numbers can update without problems.
Click to expand...
Click to collapse
Glad it helped
So, your device CID wasn't listed here, right?

i dont know man.. i am new to android i dont know how to check cid number and all .. can u suggest me any threads so that i can follow it step by step.

Keeping your CID
I copied what was wrote from this thread at step 4, just added some steps.
- Download adb tools here.
- On your pc click on your local disk C: Drive (or D: drive for some) (WINDOWS users: Start > My computer > Local Disk (C)
- Create a new folder called "adb" and extract the files from adb.zip into it. Make sure it doesn't create another folder in the adb folder when extracting.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Open command prompt (Press the start Logo on your keyboard + R, then write cmd and press enter) and type "cd C:\adb" {without quotes}
- Ensure your phone is switched on (regular home screen) and connect it by USB in charging mode (Ensure USB Debugging is On by going on your phone to Settings -> Applications -> Development and Check USB Debugging).
- Enter the command "adb devices". This is to confirm your phone is connected. (It should come back with list of devices attached and your serial number)
- Enter the command "adb reboot-bootloader".
- Waint until the bootloader opens up, and write in cmd "fastboot getvar cid".
It will say CID: XXXX this is your CID.
Take note of this number, you'll not need it now, maybe you'll never do, but just keep it in-case
********** Optional: Write SuperCID ************
- Enter the command "fastboot oem writecid 11111111"
- Enter the command "fastboot reboot-bootloader"
- Enter the command "fastboot getvar cid"
It should show CID: 11111111
You can now flash any RUU you want. You don't need this to flash a Custom ROM.
******************************************
- You can now write "fastboot reboot" in CMD to get back to your android.
I take no responsibilities of anything you're doing on your phone, do what you want at your own risk.

thanks man.. i ll give a try ..but i checked cid numbers in 1.34.415.1 it is only htc_j15. i think mine will also be same. as i had purchased this from dubai.

raghavendrenk said:
thanks man.. i ll give a try ..but i checked cid numbers in 1.34.415.1 it is only htc_j15. i think mine will also be same. as i had purchased this from dubai.
Click to expand...
Click to collapse
Mine is HTC__J15 too, bought it from Saudi Arabia xD
Good luck

mine too HTC__J15 . there is only one CID change when compared to 1.35.401.1 and 1.45.401.2 . HTC__J15 present in 1.35.401.1 missing in 1.45.401.2. thats why i think i am able to install 1.35.401.1.
thanks for the support mate.

OTA ARABIC 1.57.415.3 and WARANTY IS BACK

Dear ALL
Today I did Manage to re-lock the Chacha bootloader to win the waranty back here is what I did
1- My ChaCha is an Arabic version bought it from egypt it was coming with ROM (( RUU_Chacha_HTC_ARA_1.22.415.2_Radio_47.14.35.3030H_7.47.35.17_release_198595_signed.exe )) you can find it somewhere in ChaCha thread .
2- I did extract the above rom and i toke the file called rom.zip then i did extract it
3- i did flash boot.img , radio.img , recovery.img and system.img using fastboot.exe
CMD
fastboot.exe flash boot boot.img
then
fastboot.exe flash radio radio.img
then
fastboot.exe flash recovery recovery.img
then
fastboot.exe flash system system.img
then
Factory Rest
then
Restart
4- The ROM 1.22.415.2 installed on my Chacha and working super . I went to Settings > About Phone > Software Updates > Check now . the system asked me to download the new update then I did
5- For sure before i install the update I looked for the OTA update on my phone and i managed to find it on my SD under folder called download (( OTA_Chacha_HTC_ARA_1.57.415.3-1.22.415.2_release_228158ps5fo8iej85c5rzr.zip )) Here is a link of the OTA update
http://ifile.it/y5jwsx2/OTA_Chacha_HTC_ARA_1.57.415.3-1.22.415.2_release_228158ps5fo8iej85c5rzr.zip
6- I asked the Updater to install the OTA ROM
7- The rom installed i did uncheck fastboot from Settings > Power > Fastboot
8- I checked the Bootloader i found it as before i start to unlock it via HTCdev unlocker with the stock bootloader 1.07.0000 S-ON RL
Cheersssssssssssssssssssssss yahoooooooooooooooooooooo My waranty is back

I haven't checked on the Chacha, but on Motorola's there's a flash in fastboot that can tell you if warranty is void because of unlocking. Even relocking won't reset the flag.

adlx.xda lets look for it but i don`t think that HTC is that smart anyways if so no problem at less that it downgraded the Hboot from 1.10.0000 to 1.07.0000 and lock it
Sent from my HTC ChaCha A810e using XDA App

the variable I know from Motorola is: iswarrantyvoid
fastboot getvar iswarrantyvoid
Idk if it's valid for HTC though. Not tried yet.

adlx.xda said:
the variable I know from Motorola is: iswarrantyvoid
fastboot getvar iswarrantyvoid
Idk if it's valid for HTC though. Not tried yet.
Click to expand...
Click to collapse
I tried the above CMD but its not working
I did type
fastboot.exe getvar all
I got
INFOversion: 0.5
INFOversion-bootloader: 1.07.0000
INFOversion-baseband: 7.51.35.19
INFOversion-cpld: None
INFOversion-microp: 0557
INFOversion-main: 1.57.415.3
INFOserialno: "My Serial No"
INFOimei: "My IMEI"
INFOproduct: chacha
INFOplatform: HBOOT-7227
INFOmodelid: PH0611000
INFOcidnum: HTC__J15
INFObattery-status: good
INFObattery-voltage: 3738mV
INFOpartition-layout: HTC
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-8ecce785
INFOhbootpreupdate: 12
INFOgencheckpt: 0
all: Done!
finished. total time: 0.031s
Anthor CMD
c:\Andriod>fastboot oem boot
... INFOsetup_tag addr=0x60000100 cmdline add=0x9
07E42C
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x29001
INFOTAG:hero panel = 0x0
INFOTAG:engineerid = 0x0
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFOTAG:TP = 1
INFODevice CID is not super CID
INFOCID is HTC__J15
INFOsetting->cid::HTC__J15
INFOserial number: " MY SN"
INFOcommandline from head: no_console_suspend=1 console=null
INFOcommand line length =565
INFOactive commandline: board_chacha.disable_uart3=0 board_chach
INFOa.usb_h2w_sw=0 board_chacha.disable_sdcard=0 diag.enabled=0
INFOboard_chacha.debug_uart=0 smisize=0 userdata_sel=0 androidbo
INFOot.emmc=false androidboot.pagesize=4096 androidboot.baseban
INFOd=7.51.35.19 androidboot.cid=HTC__J15 androidboot.batt_power
INFOon=good_battery androidboot.carrier=HTC-GCC androidboot.mid=
INFOPH0611000 androidboot.keycaps=qwerty androidboot.qwerty_colo
INFOr=white androidboot.mode=normal androidboot.serialno=HT169V4
INFO03255 androidboot.bootloader=1.07.0000 zygote_oneshot=off km
INFOemleak=off no_console_suspend=1 console=null
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=cache
INFOaARM_Partion[5].name=userdata
INFOaARM_Partion[6].name=devlog
INFOpartition number=7
INFOValid partition num=7
INFODelay 99978(us) for dpram command before goto AMSS...
FAILED (status read failed (Too many links))
finished. total time: 1.716s
is that usefull ?

I wouldn't count on this actually working tbh... I downgraded my bootloader to 1.04.0000, updated to 1.07.0000, then 1.10.0000 (the one from HTCDev) just to see what would happen, and upon applying 1.10.0000, it still showed as *** UNLOCKED ***. Doing a fastboot oem lock won't work either, your bootloader will say *** RELOCKED ***.
In short: the unlock flag is stored in a secret partition and is still visible no matter what bootloader is running

Dear qzfive..
I think you did S-Off to your device using XTC clip ? OR you did the downgrade using gold card ? Right

I S-OFF'd via the Clip a good month before HTC-Dev unlock, however that's not relevant in this situation. S-OFF and the HTC-Dev unlock definitely appear to be two seperate flags, since some people haven't used the Clip and have an HTC-Dev unlocked bootloader are S-ON.
I think that the HTC-Dev unlock/relock flag is on the same partition as the @secuflag, which controls S-ON and S-OFF. HTC would know how to read this partition and read the flags to determine if your warranty is void or not. Also, remember when you started the HTC-Dev unlock, and you had to get a unique ID key from your device? Chances are they also save that key onto their systems as one that's had its bootloader unlocked.
One additional note: doing radio flashes won't reset the flags either, as when I applied the different HBOOTS, radios were flashed along with them as part of an RUU or OTA.
Either way, after we've used the HTC-Dev unlock, we can say goodbye to our warranties

Dear I agree with you but if there is no secueflag says its locked or unlocked only and about the saving the code in thier system easy i can complain about maybe some hacker did stolen my SN. or somthing and he did register with it in thier system
any ways Warranty on or off i dont care because HTC service they are useless at the end
I am going to search how to read the SecureFlag from the partattion
Thank you any ways

You can reupload the file please?

I will upload it again tomorrow
Sent from my GT-N7000 using XDA App

how did u extract the ruu.exe file?, what program did u use?
I tried winrar and 7zip but nothing worked!

for extracting ruu file....
run the ruu.exe
wait till view read me and chacha image page come....
then..in computer..go to c>user>username>appdata>local>temp..
there you can folder with numbers..
select that folder and check,there will be a file named rom.zip..
extract that file..then flash the images..
sorry for bad english.....

could you re-upload please ?

Where can i get the boot.img , radio.img , recovery.img and system.img

Want to switch roms, not sure what my possibilities are

Hello,
I'm on Avatar Rom now and I'm getting really sick of all the stuff that crashes and/or doesn't work at all. (Like recording video!)
But I'm not sure what my options are. I think I'm stuck on my HBOOT as well.
Some info about my phone, obviously a ONE X:
*** UNLOCKED ***
Endeavoru PVT SHIP S-ON RL
HBOOT-0.95.0000
CLPD-None
MICROP-none
RADIO-none
EMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM PATH: OFF
May 8 2012, 21:32:10
Fastboot variables:
Version: 0.5a
Bootloader (HBOOT): 0.95.0000
Baseband version: None
CPLD Version: None
Microp version: None
Main version: 1.29.161.13
Serial nr: 353043052926402
Product: Endeavoru
Platform: PJ4610000
CIDNUM: None
Security: On
Build-mode: Ship
hbootpreupdate: 2
fastboot getvar version: 0.5a
fastboot oem readcid: VODAP102
So, is there any way I can update my HBOOT.
Are there any power-saving ROMS?
Thanks in advance!
TimVN

You're in the wrong forum, you need the international one x forum.
Sent from my One X using xda premium

Ok thanks, will post it there

One Mini s-ON, trying to get s-OFF

Hey guys, I have a problem with this phone HTC one mini, in fact I'm trying to unlock it with Sieempi method, but for this I need the device to be s-off. I unlocked the bootloader, the device be rooted, and when I try to use Rumrunner i got this error message.
Code:
Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner] ----
(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this world
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (19/120)
Waiting
Test 2: Booting device
Waiting for ADB (55/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
Waiting for ADB (55/120)
must ferment longer...
chilling..................
it's a little stinky here, hmm....
bottles are packed, here we go, shhhhhh....
hmm, cap is on tighter than I expected........
hell, that damn cap is on REALLY tight.......
unfortunately this isn't going to work out with your configuration. you have 2 options:
1.) flash an unsecure kernel that's compatible with your ROM and retry rumrunner (preferred and most reliable method).
2.) flash a different rom.
NOTE: No amount of messing around with su binaries and apk's is going to fix this issue for you!!!.
Better luck next time!!!!bye
Press ENTER to exit
Then i find this theard
http://forum.xda-developers.com/showthread.php?t=2573479
And download this two files, but then I stuck.
I'm not sure how to do the rest, but I tried it this way and I have failed.
I unpacked JmzM4_Kernel-09-4-13.zip file, and copied the boot.img file in the SDK folder from where I started CMD. In the CMD I typed "fastboot flash boot boot.img" and I got the message OK.
Then I went into recovery and found JmzM4_Kernel-09-4-13.zip file on the internal memory of a cell phone and I tried to install it (so I read) a zip file, and then I got the error MD5 file check, something like that.
I then reboot to recovery again and tried to install "JmzM4StockRootedOdex-WWE 1.22.401.1" also a zip file, and again the same error MD5 file check.
Then the phone in fastboot mode remained and could not boot the system. So I had to do a restore of backup I in which they made before I got into flash kernel, and roma.
Here is also my fastboot getvar all the info.
Code:
C:\ADB>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 2.22.0000
INFOversion-baseband: 1.28.40e.00.24
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 4.14.401.1
INFOversion-misc: PVT SHIP S-ON
INFOserialno:
INFOimei:
INFOmeid:
INFOproduct: m4_ul
INFOplatform: HBOOT-8930
INFOmodelid: PO5820000
INFOcidnum: HTC__032
INFObattery-status: good
INFObattery-voltage: 4316mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-0e1af350
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.124s
C:\ADB>
Can someone tell me what is the solution for my problem, I just want my device S-off to try Sieempi method of unlocking, to see if it works. Thx!

Nothing? I try a couple thing more. I think its problem in the file I downloaded, and download a MD5 checker, and says thats ok. Then I save a md5 file from Md5 checker @ the same folder like zip file, and run again from recovery, and now got another error, you can see image.
IMG]http://tapatalk.imageshack.com/v2/14/10/08/624d91145625043f190be1d67997e6a2.jpg[/IMG]
Revone method doesnt work i got error -2. And boot intro the bootloader and stil s-on.

Please lock theard, phone was smashed. I lost nerves!

Hi Errornt
pardon if i only post today!
had your same situation and now i've solved! the solution? just flash a new kernel! i've used xXminiWHOOPERxX Kernel and now.... i'm s-off
so, unlock bootloader, install custom recovery and root, flash an insecure kernel with fastboot method and run rumrunner
that's all
i'm sorry for your smashed phone
br
ss