I have searched the forums and have found 1 post saying that the T-MOB005 cannot be CID unlocked ? is this still the case as the post was dated Nov2006 ?
I have tried the POF method twice (i.e. Herm CID Unlock v2a). and although it had updated the Radio to 1.16 when i enter the "info 2" command with mtty it brings back
HTCST-MOB005¼ôàŠHTCEUSB>
which means that it is not super cid unlocked.
SPL=1.04
IPL=1.01
I have also checked that the radio has been flashed correctly and it show in device id that the Radio Version is 1.16 so it certainly appears that all has worked apart from the SuperCid
When i put in a sim from another network i get a screen that " I have tried 10 times and to wait till timeout" both buttons are greyed out so i cannot input any numbers.
My T-Mobile sim still works fine.
mtty output
USB>
USB>info 2
HTCST-MOB005¼ôàŠHTCEUSB>
USB>
USB>rtask b
0
0
atvl
0
[email protected]?40
@SIMLOCK= 01
0
atel
0
USB>
USB>rtask b
0
0
[email protected]=0,1,22051978
4
[email protected]=0,2,22051978
4
[email protected]=0,4,22051978
4
[email protected]=0,8,22051978
4
[email protected]=0,16,22051978
4
[email protected]=0,32,22051978
4
Any info appreciated.
Thanks
Are you sure you didn't flash extracted radio 1.16 before and that's why it's showing 1.16 on radio version now?
If your SPL is 1.04 it should work. Try flashing the patched radio again, and capture the flashing process with USB monitor if nothing changes after flashing the radio. This should help to troubleshoot why it is not working on your device.
I will start from scratch again this evening and see if it still gives the same results. I had already flashed my other vario II and this worked with no problems.
Will post my results this evening.
Thanks for your help so far.
I have absolutely no idea how I got the 1.16 radio roms mixed up but when i re-downloaded the unlocker again and used this one, everything unlocked fine first time. info 2 shows supercid.
Lesson learnt i think, dont do anything when you have been working for the last 14 hours as you tend to miss the most obvious things.
Thanks for your help.
Related
Hi,
I see my CID by issuing bootloader command "info 2"
USB>info 2
CID: Wait interpreter timeout
HTCSF kEØ(HTCEUSB>
My radio part is screwed and have tried to flash radio only, nothing happened and nothing showed in USB Monitor.
This is the current configuration of my device with GetdeviceData:
HERM100 1 0 0 å $ p 1.20
Help me,please.
What Device do you have?
Have you checked everything on the wiki. I think there is something about bringing your radio part back. With links to some threads.
Not sure though, never had problems with my VarioII.
Good luck.
I have an SPV M3100 Orange Unlocked..(unlock V3)
After unlocked I have flash it with the newest rom JASJAM_telstra_1.31.305.2_1.31.305.103_1.20.31.10_ship.zip
The rom update crash and now i have NO GSM - NO IMEI -NO CID..and so I cannot flash with any rom!!
(Sorry for my english...)
I am having the same error - flashing froze partway through a radio-only install, and now I have no radio, and apparently no CID.
Radio flash attempts now pause at 0%
Device boots fine, no problems with WiFi, Bluetooth etc.
Read "problem 5" here:
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems
Tried to update as per point 5 on the wiki - 4 consecutive times the ugrade froze at 0%
Do you need to enter the set of 'erase' commands each time you attempt flashing or do they remain in the device?
redgsr said:
Do you need to enter the set of 'erase' commands each time you attempt flashing or do they remain in the device?
Click to expand...
Click to collapse
They remind on the device
Try to do a full rom upgrade, and capture the output using USB monitor. Attach it here and we'll see where it fails.
I last night I did a full ROM upgrade, with USB Monitor going, and looking at the logs, its froze at 14% when it had just finished updating the ExtROM and couldn't open the radio stack. Unfortunately I didn't save the log.
I just went out for a few hours, and left the battery out of my hermes. When I put it back in I immediately booted into Bootloader and it returned a DOPOD01 CID from 'info 2' in MTTY so I went to upgrade the radio, which curiosly also failed at 14%. This time I forgot to run USB Mon! Idiot!
When I rebooted just then and went back into MTTY it returned the CID: Wait interpreter timeout for 'info 2'
I am leaving the battery out again for a while, and will do a full upgrade if MTTY returns a valid CID, with USB Mon going, and upload the log.
Cheers!
Ok. Not good.
Left battery out of device until info 2 would return a CID.
1. Tried full Dopod ROM upgrade, failed at 15%
2. Had a couple of attempts at recovery within ROM upgrade program
3. Radio upgrade failed
Is now only booting to Bootloader, 'set 14 0' is not working
Am currently uploading my logfiles to my webspace, will post the link when they arrive.
Look for hermesfailure.zip in /Upload/Temp on the ftp.
Uploading now, so leave 10 mins or so.
EDIT: moved here ftp://xda:[email protected]/Hermes/Technical/hermesfailure.zip
Had a look at the files you uploaded:
1) in "hermes flash fail.txt" upgrade ends with "Restore GSM Fail"
2) in "recovery.txt" upgrade ends with "Check Cert Error!"
3) in "radio upgrade fail.txt" the radio bootloader returns no output.
Are you sure you run the "erase" commands successfully as shown in the wiki?
The result should be "HTCS+(T or F)+(4byteCRC)+HTCE". T means success, F means failure.
Make sure you see the "T" after you run the erase commands.
T returned after every erase command.
Transcript as follows:
Code:
USB>
USB>
USB>password 0000000000000000
HTCSPass1.CMˆËHTCEUSB>
USB>set 1e 1
USB>erase a0040000 c80000
HTCST ÚÈÒHTCEUSB>
USB>erase a0cc0000 c80000
HTCST ÚÈÒHTCEUSB>
USB>erase a1940000 640000
HTCST ÚÈÒHTCEUSB>
USB>set 1e 0
USB>
Full ROM upgrade error again at 14% - radio ROM upgrade freeze at 0%
Is it possible that there's something wrong with the device itself, as the NO GSM error came before I did any upgrading etc? The other thing that makes me think this is that only after a long period with the battery out will it show a CID and accept a Radio ROM upgrade.
I had the same problem, and now my device is at the support company to try and fix.
Right now I'd like to get back to the situation where it boots, without radio. That way I stand a chance of a warranty if the person in the store isn't too knowledgeable.
I tried to get back to the orginal, but could not, so I have to get it reapired outside warranty, i was told i will cost eur 90, which is better than paying eur 700 for a new one.
OK - Have tried various things and it comes down to 2 problems
1. No CID
2. Radio Bootloader freezes
I've had USBMon going permanently as I tinker, and every time you see "Enter Radio Bootloader...." that is where the process freezes, even when I enter rtask b manually via MTTY
I also tried the HImalaya fix as posted by others, this did nothing.
All other commands (info 2,3,7,8, checkimage, task 32 etc) work fine except the ones that should return a CID.
Any suggestions.
This afternoon I think I will take it back to the shop and play dumb
redgsr said:
I've had USBMon going permanently as I tinker, and every time you see "Enter Radio Bootloader...." that is where the process freezes, even when I enter rtask b manually via MTTY
Click to expand...
Click to collapse
'rtask b' is for GSM at command, radio bootloader is 'rtask a'. When you type commands in radio bootloader or GSM AT cmd interface you don't see the output (echo) of the commands you type, this doesn't mean it is hung. You can go back to "normal" bootloader USB> prompt by typing 'retuoR' (case sensitive!).
Anyway, I took it into the store today and because it was less than 2 weeks old they can swap it in-store, without referring to someone who even knows what a rom is... They are out of stock for a couple of days so I might keep playing with it until then, but will leave the replacement alone!
Thanks for the advice pof, really appreciate your help.
Brought it back to life!!!!
Your thread with the SIM unlocking inspired me to have one more try - since my carrier offered to replace my phone I put it in the drawer and didn't think about it.
I performed the erase commands (for the 100th time!!!) from the Wiki, then installed your hacked Radio ROM. Instead of stalling at 0% like normal, it flashed properly, giving the error message at 99%
When I soft reset it still went straight to Bootloader, even after a set 14 0 command.
I then reflashed it with a full Dopod ROM and it seems to be working!!!
As my NO GSM errors were present when the phone was new, I am still going to exchange it, but at least I have a working model to use for the next few days until they find one to exchange!
So thanks again for all your help
Please help me!
I screwed my german T- Mobile MDA Vario II. I used HTC universal sim unlocker and I haven’t got radio. I know I was a craze.
No GSM, no cid and no imei. The pda is working good.
I vas very happy when I find this site :
http://wiki.xda-developers.com/index...pgradeProblems.
The radio doesn’t work , no GSM, no cid and no imei. The pda is working good.
Please help me
At least your device is on bootloader 1.04
have you tried all the steps in "problem 5" on the wiki?
What the "MDA Vario II" is equipped with that one of "bootloader" 1.04 and I have done everything under "problem 5" unfortunately without steht. is carried out.
USB>info 2
CID: Wait interpreter timeout
HTCSF kEØ(HTCEUSB>
USB>
USB>info 3
CID: Wait interpreter timeout
HTCSHUSB>
USB>info 7
HTC Integrated Re-Flash Utility, Common Base Version : 1.50a
Device Name: H, Bootloader Version : 1.04
Built at: May 26 2006 20:17:35
Copyright (c) 1998-2006 High Tech Computer Corporation
CPU ID=0x41129200
Main CPLD version=0x5
USB>password 0000000000000000
HTCSInvalid password.R¿ËPHTCEUSB>set 1e1
USB>erase a0040000 c80000
HTCST ÚÈÒHTCEUSB>erase a0cc0000 c80000
HTCST ÚÈÒHTCEUSB>erase a1940000 640000
HTCST ÚÈÒHTCEUSB>set 1e 0
USB>
USB>
Upper CPLD version=0x4
Main Board version=0x6
Please help me
Try to flash a radio rom, and send me the USB Monitor capture exported in ANSI text format of all the radio rom flashing process.
Instructions for how to use USB Monitor are on the wiki "upgradin problems" page too:
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems
HElp me
Hello has a little lasted with me longer.
I hope you can help me at mine nevertheless problem!
Here is the ANSI file
The upgrade stops because radio bootloader doesn't answer to 'rerase' command after 3 retries. Repeat the steps on wiki "problem 5", do it several times. If you can't get it to work send it to repair centre.
hmm
would it use what if I make Rome one new completely, then?
gives it no questions possibility on the CID to circulate?
I don't understand what you mean.
Mummromeo, I also can't understand what you try to say. Send me a PM in german if you want to.
Another variation for this problem..
I am trying to recover my Smrtphone. I have a XDA First Trio. First I instaled a HTC ROM with bootloader 1.06. After I unlocked the SIM and CID. When I tried to install the ROM from Cirgular with Bootloader 1.04 the process stoped at 14% and now I have a mixed ROM with Bootloader 1.06... and I cannot unlock and install another ROM.... what I can do??? I am not an expert.. I dont know how to install DUmped Roms... I tried to follow the wiki but my device is locked and I dont know how to change the Key Entries.... HELP ME!!!! PLEASE
@rfgirardi: take any of the O2 XDA trion german ROMs found here:
http://wiki.xda-developers.com/index.php?pagename=Hermes_Upgrades
Try to flash it while the device is in bootloader mode, if you're not successful flashing then try to flash from SD card as described here:
http://wiki.xda-developers.com/index.php?pagename=Hermes_SDCardFlashing
Hi pof,
Thanks for your help, but the procedures doesnt function... I runnede the Devicedata.exe and the file created doesnt have the information about the device... In the bootloader i have HEM100 IPL-1.01 and SPL-1.06. In the devicedata.txt cretaed I have just this
HERM100 1 0 0 å p 1.18
If i look in the System»Settings»Device Information I have:
ROM Version: 1.18.416.1
RADIO Version: Nothing...
Protocol Version: Nothing...
IMEI: Nothing..
Do you think I can try another procedure or just send the device to the workshop?
Rodrigo
rfgirardi said:
Do you think I can try another procedure or just send the device to the workshop?
Click to expand...
Click to collapse
As you can boot OS it could be downgraded to bootloader 1.04, but with a corrupted radio.
This is what I got for updating by doing this:
"Bring your bricked TyTN back to live"
http://forum.xda-developers.com/showthread.php?t=280425
With doing this, this is the only solution that will get me far enough for the boot screen to actually go white. The rest of the Rom's or Radio's don't got anywhere past this.
I hope someone can help me, no solution anywhere? Not even the Softbank chip can help.
I answered you on this thread:
http://forum.xda-developers.com/showthread.php?p=1078913#post1078913
Please do not double-post.
pof, I think it's time for a Sticky on this matter, cause it's becoming a common issue.
axiom said:
pof, I think it's time for a Sticky on this matter, cause it's becoming a common issue.
Click to expand...
Click to collapse
Yes, great idea... will make one now and let's see if we can keep all the bricked devices in one whole sticky thread. Hopefully we find a solution by joining all our efforts
Hi Pof,
I have the Unlocker that I payed to do the first unlock. After the problem when the Upgrade Rom process stoped at 14%, the feature doesnt recognize my device as a valid one. With this feature I cannot downgrade to 1.04. I dont know more what I can do.... but anyway, thanks for your efforts!!
Alright, so im trying to superCID my Dopod 838 Pro. I've read the wiki and all the threads that i can find, and everything seems to go according to plan. Except i cannot verify SuperCID status.
I downloaded pofs http://pof.eslack.org/hermes-unlocker/
I flashed the radio, and received the "Upgrade Error 114" as expected.
I then ran HERM_Unlock_v2a.exe on the device, and after a minute i get a "Your device was SUCCESSFULLY unlocked and changed to SuperCID." message.
From mtty (after booting the device into the bootloader) i get the following results from the suggested commands.
USB>task 32
Level = FF
USB>info 2
HTCSDOPOD001Û<wHTCEUSB>
From what i understand, my device is still CIDlocked.
I want to make sure that superCID is enabled before i go flashing the ROM.
I've gone back and reread the instructions and repeated this procedure three times now.
Any suggestions as to what i might be doing wrong?
In the bootloader i see the following:
HERM100
IPL-1.01
SPL-1.04
thanks/Richard.
What radio version do you have currently installed? When you run the downgrade to radio 1.16 (attached to the unlock v2a) and get a error 114 you have to rerun it till the red progress bar appears and the radio is flashed to 1.16. Only then can you run superCID.
I have radio version: 1.06.00.10 installed.
Other versions are:
ROM Version: 1.23.707.4
ROM date : 07/21/06
Protocol version: 32.37.7010.01H
I see. Is the red bar to appear on the computer or the device? I received error 114 every time.
edit: when updating i see "Upgrade. Radio Stack. Please wait..." on the device. This message doesnt go away, even after error 114 , until i soft reset the device.
I've rerun it now an additional 5 times. I get no red bar.
Also, it wouldn't be a downgrade of the radio, as im trying to go from 1.06 to 1.16, but im not sure thats relevant.
does nobody have any insight to share?
littlenarf said:
does nobody have any insight to share?
Click to expand...
Click to collapse
I see you tried the unlocker v2a, have you tried the new version 3...just a thought.
Hey Gang,
Got a Cingular 8525 with the following symptoms:
1) Was SuperCID + SIM Unlocked
2) Was on Cingular 1.35 + Radio 1.27; attempted upgrade to Cingular 2.06 (.exe, full rom). Upgrade failed at the 25% point.
3) Boot loader got updated to 1.09
4) On power-up, phone displays AT&T splash screen with "No GSM", then hangs at Windows Mobile splash screen.
5) When I attempt to try a new ROM .exe (or re-run the Cingular one), or downgrade the Boot Loader, or anything from the tri-colored screen, the (win32) software returns an "INVALID VENDER" error,
which makes me wonder if the SuperCID status somehow got corrupted.
6) 'info 8' from the MTTY USB serial console shows that all blocks are present and in good condition.
As this is my sole phone, this really leaves me in a bad spot. I'd like to see if there's anything I can do to salvage it before waiting potentially a couple of days for
Cingular to ship me a replacement -- and that's assuming they will.
Any advice would be greatly appreciated.
fyi: USB>info 2
CID: Wait interpreter timeout
HTCSF kEØ(HTCEUSB>
USB>info 2
HTCSF kEØ(HTCEUSB>
USB>
USB>info 2
CID: Wait interpreter timeout
HTCSF kEØ(HTCEUSB>
USB>info 2
HTCSF kEØ(HTCEUSB>
USB>
USB>info 1
USB>info 2
HTCSF kEØ(HTCEUSB>info 3
HTCSH
Is this phone salvageable or not?
Anybody out there? pof? sleuth225?
dolemite said:
fyi: USB>info 2
CID: Wait interpreter timeout
HTCSF kEØ(HTCEUSB>
USB>info 2
HTCSF kEØ(HTCEUSB>
USB>
USB>info 2
CID: Wait interpreter timeout
HTCSF kEØ(HTCEUSB>
USB>info 2
HTCSF kEØ(HTCEUSB>
USB>
USB>info 1
USB>info 2
HTCSF kEØ(HTCEUSB>info 3
HTCSH
Is this phone salvageable or not?
Click to expand...
Click to collapse
ME TOO...
who can help us?
If you bothered to read the Wiki, you would have seen this:
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems#problem5
If you can't bother to read the wiki, don't play with roms!
LegolasTheElf said:
If you bothered to read the Wiki, you would have seen this:
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems#problem5
If you can't bother to read the wiki, don't play with roms!
Click to expand...
Click to collapse
Actually, I did read that, and a couple of problems:
1) Boot Loader is 1.09
2) OS won't load, so can't use any of the ActiveSync-based methods for downgrading to an older version, such as 1.04.
3) CID appears to be corrupted, as per the earlier output pasted.
Any brilliant ideas, or is my phone effectively bricked beyond repair?
Thanks...
the wiki that LegolasTheElf told you to review does in fact say what to do if you have bootloader 1.09 and can't boot into the OS to run SSPL...
8. If your bootloader version is different than 1.04 then Flash Bootloader version 1.04
on that page, you are told the following:
If no such rom is available for your device or your bootloader version is 1.09, you can buy the Imei-check unlocker to have bootloader 1.04. The HTC Hermes unlocker from imei-check is able to flash the 1.04 bootloader. It transfers the required files to the Hermes via ActiveSync before actually the unlocking key file with your IMEI is requested. The bootloader is flashed on the device after you enter the valid key file (you have to pay for that).
[edit: fixed incorrect bold formatting tags]
[edit 2: well, apparently i can't read. the text i linked definitely says it needs to transfer files via activesync, and of course you can't do that. sorry...been a long day. is it 5pm yet?]
Pretty much. No working OS, hence no ActiveSync. And the CID appears corrupt, so it's not like I can just downgrade to 1.01/1.04 from the boot loader.
Anybody want to drop some science on me? Cause it sounds as though I might be screwed...
yes, u are screwed! just like me! just get another one on ebay!
people keep saying DOWNGRADE to bootloader 1.04! but it' not possible if u have bootloader 1.09 and u stuck at the boot-up screen!
Sam case with me.
FRIENDS help , I think I have the brick of all bricks I followed the wiki step by step including creating and copying the nbh file. I got as far as 70% of image loading and it hung and dropped into recovery mode but could not get passed there. I have tried all forms of reset and do not get passed bootloader screen with Herm100 IPL-1.04 and SPL-2.03. This was a imate jasjam running windows mobile 5.0 to which I tried flashing to the new HTC WWE 6.0 upgrade. I have tried running usb monitor from the link but it just gives me a series of paramters in a notice window and then dops off. I have tried another verison but it is not capturing anything.
I have tried mtty and cant even get the usb> prompt after disabling the usb connect in activesync. Please help as this was a works new unit last month and I have some major explaining to do if I cant get it sorted!
Model: Imate Jasjam
ROM Before Flash: TMO_UK_3.60.110.1_6275_1.50.00.00_108_Test
Radio Before Flash: 1.50
Bootloader Before Flash: Not sure
Flash failed at: 70%
Flashing ROM: Image Vers 3.54.255.3
CID Corrupt: Assume Yes
Radio Corrupt: Assume Yes
No GSM Error: Not got that far
Stuck In Bootloader: Yes
Stuck On Windows Mobile Splash: Not got that far
Can boot into OS: No
Tried mtty command set 14 0: Yes but not getting usb>
Tried wiki problem number 4: Yes dont get passed point 3 as as soon as powers up goes to tri colour screen. Switched from serial to usb with connect of usb cable
mtty info 2 output: cannot run
Current Device Status: unusable
Tried re running install and get error 260 and 294(AFTER 1%)and - Not getting a response from PDA!
I TRIED PB + KITL method .BUT IT FAILED AS I COULD NOT ACTIVATE KITL MODE.I BELIEVE ITS NOT ACTIVATED IN MY PDA.
I SPOKE TO TO IMATE INDIA PEOPLE , THEY REPLIED THAT THE MOTHERBOARD IS TO BE CHANGED , WHICH COSTS 60% OF THE COST OF THE PDA.
CAN ANYONE HELP WITH A BOOTLOADER V2.03 ?
WAKE UP DEVELOPERS .DO SOMETHING.
tHANKS IN ADVANCE.
the output is for :
HTC_Hermes_SIM_CID_Unlock_v3a
And
RUU_Hermes_TMO_UK_3.60.110.1_6275_1.50.00.00_108_Test repectively.
So no HardSPL before you flashed?
You should still be able to get a USB monitor from it.. regardless if the thing has been thrown off the empire state building.
What USB monitor program are you using?
MTTY Set 14 0 I beleive is for a corrupt radio stack, all that does is restore your radio stack to factory form, sounds to me like you have a hybrid brick, which is corrupet or invalid CID coupled along with a corrupt radio stack..
Madcap180 said:
MTTY Set 14 0 I beleive is for a corrupt radio stack, all that does is restore your radio stack to factory form, sounds to me like you have a hybrid brick, which is corrupet or invalid CID coupled along with a corrupt radio stack..
Click to expand...
Click to collapse
set 14 0 tells the device to skip to OS boot rather than go to bootloader (opposite of set 14 1)
what we need to ascertain is exactly what bootloader version this guy is running, and then to find out what CID he has from the bootloader.
until we get these both, I think we'll have to "assume" it's ****ed.
oh and in future, don't PM me twice, it pisses me off. so consider yourself lucky I've bothered to comment.
Cmd>
Cmd>info 2
HTCSCDL__001ÄÊìHTCE
Cmd>info 7
HTC Integrated Re-Flash Utility, Common Base Version : 1.51d
Device Name: HERM100, Bootloader Version : 2.03
Built at: Jun 16 2007 01:57:22
Copyright (c) 1998-2006 High Tech Computer Corporation
CPU ID=0x41129200
Main CPLD version=0x5
Upper CPLD version=0x4
Main Board version=0x6
Cmd>info 6
HTCST ÚÈÒHTCE
Cmd>info 5
Cmd>info 4
HTCSCDL__001ÄÊìHTCE
Cmd>info 3
HTCSH
Cmd>set 14 1
Write Nand Success
HTCST ÚÈÒHTCE
Cmd>rtask 32
Command error !!!
Cmd>rtask 28
Command error !!!
Cmd>rtask 8
Command error !!!
lastly it's not KITL enable.