Missing CID,IMEI,Radio Version - 8525, TyTN, MDA Vario II, JasJam Software Upgradin

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!!

Related

Determine Bootloader Version

Is there a way to determine my bootloader version? I see "info 1" on the bootloader FAQ, but it returns nothing.
I have a Softbank X01HT with the JASJAM_telstra_1.31.305.2_1.31.305.103_1.20.31.10_ship burned to it. I thought the CID was stored in the ROM flash so I upgraded from the previous JASJAM ROM. Now I cant downgrade apparently. I have a 1.06 Bootloader right?
Here is some additional info:
----
USB>info 2
HTCSSuperCIDHTCE
USB>checkimage
IPL CRC checksum = 0x4A75448F
SPL CRC checksum = 0x3BF03635
CE CRC checksum = 0x964CDB85
ExtROM CRC checksum = 0xC80B05D
Radio Image CRC checksum = 0xB1B0E47C
----
IPL-1.01
SPL-1.04
Thanks
jokinawa said:
Is there a way to determine my bootloader version? I see "info 1" on the bootloader FAQ, but it returns nothing.
Click to expand...
Click to collapse
info "0" and "1" do not seem to work in the Hermes, "info 7" will give you your answer:
Code:
HTC Integrated Re-Flash Utility, Common Base Version : 1.50a
Device Name: H, [b]Bootloader Version : 1.04[/b]
Built at: May 26 2006 20:17:35
Copyright (c) 1998-2006 High Tech Computer Corporation
[...]
jokinawa said:
Here is some additional info:
----
USB>info 2
HTCSSuperCIDHTCE
Click to expand...
Click to collapse
Your device is SuperCID, you should be able to flash ANY rom. Can you paste the output of "task 32"? It shows the security level.
Did you use v3 of imei-check unlocker?
pof said:
info "0" and "1" do not seem to work in the Hermes, "info 7" will give you your answer:
Code:
HTC Integrated Re-Flash Utility, Common Base Version : 1.50a
Device Name: H, [b]Bootloader Version : 1.04[/b]
Built at: May 26 2006 20:17:35
Copyright (c) 1998-2006 High Tech Computer Corporation
[...]
Your device is SuperCID, you should be able to flash ANY rom. Can you paste the output of "task 32"? It shows the security level.
Did you use v3 of imei-check unlocker?
Click to expand...
Click to collapse
Here is the info.
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
Upper CPLD version=0x4
Main Board version=0x6
USB>task 32
Level = 0
I used the only unlocker at the time for the X01HT.
Whats weird is it says I have Bootloader 1.04 but I cant change from:
JASJAM_telstra_1.31.305.2_1.31.305.103_1.20.31.10_ship (supposed to be BL 1.06)
down to
JASJAM_WWE_1.20.305.3_1.20.305.104_1.07.03.10_ship
I was trying to downgrade to the 1.20 JASJAM to install EXT_ROM from Softbank.
When I couldn't downgrade I ran the IMEI-Check unlocker again. Maybe that changed my bootloader back down?
I will try to burn the Dopod ROM. That one has worked before.
Thank you for the help.
Really weird because your device has Seclevel=0 and SuperCID, this is a developer device able to flash any ROM without restrictions.
Did you use v3 of imei-check unlocker?? Probably they changed this on v3...
V3 Unlocker
Yes,
I used this ZIP:
M3100v3Unlock.zip
which contained this file:
M3100v3cUnlock.exe
Any other commands before I disconnect and flash? I hope flashing a ROM wont mess up my CID and Sec lvl.
Flashing rom will not touch CID and Seclevel.
This is new from v3 unlocker, they didn't do this before. CID stayed the same and SecLevel=FF (unpriviledged).
jokinawa said:
Yes,
I used this ZIP:
M3100v3Unlock.zip
Click to expand...
Click to collapse
What a pity you didn't log the process as has been told here.
Chatty said:
What a pity you didn't log the process as has been told here.
Click to expand...
Click to collapse
Yep, Sorry I unlocked it as soon as I saw it avail because I cant read Japanese.
pof said:
Flashing rom will not touch CID and Seclevel.
This is new from v3 unlocker, they didn't do this before. CID stayed the same and SecLevel=FF (unpriviledged).
Click to expand...
Click to collapse
I can confirm this. I was using Bootloader 1.06 from the Cingular ROM. I did previosuly use IMEI-CHECK V2 unlocker before upgrading to the Cingular ROM. Couldn't downgrade to other ROMS.
Have now re-unlocked again using IMEI-CHECK V3 unlocker and now can downgrade as it has reverted me to 1.04 bootloader:
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
Upper CPLD version=0x4
Main Board version=0x5
USB>task 32
Level = 0
UPDATE: Radio from latest I-Mate ROM cannot be updated with bootloader 1.06 even if device us SUPERCID, have to use IMEI-CHECK to revert back to 1.04!
Thanks for posting confirmation.
Unlocking an x01ht
Hi, First post, new to the forum,
I just moved to Tokyo and am going out today to by the softbank x01ht (at ~170$us, the gadget freak in me wont let me get something else that is bilingual)
Anyway I'm willing and minimially capable of paying and completing the imei unlocking process. I've only ever done pc and laptop flashing before so I may need a bit of a walk through on how to get this dump file your looking for.
I just have one quetion - if I unlock to a cid of supercid and security level 0, I understand that I can change my ROM to a nice user friendly English speaking ROM but will my hermes still work on my network (softbank) even though I will be operating a rom from another network in a different country.
Also is there an original sim/operator free ROM uploaded anywhere or is there any ROM you would recommend for me an english speaker on a japanese (softbank) network.
Thanks for any help you can provide. I'll do my best not too mess up the imei unlocking process dump in return.
Cheers
rorycooney said:
Hi, First post, new to the forum,
I just moved to Tokyo and am going out today to by the softbank x01ht (at ~170$us, the gadget freak in me wont let me get something else that is bilingual)
Anyway I'm willing and minimially capable of paying and completing the imei unlocking process. I've only ever done pc and laptop flashing before so I may need a bit of a walk through on how to get this dump file your looking for.
I just have one quetion - if I unlock to a cid of supercid and security level 0, I understand that I can change my ROM to a nice user friendly English speaking ROM but will my hermes still work on my network (softbank) even though I will be operating a rom from another network in a different country.
Also is there an original sim/operator free ROM uploaded anywhere or is there any ROM you would recommend for me an english speaker on a japanese (softbank) network.
Thanks for any help you can provide. I'll do my best not too mess up the imei unlocking process dump in return.
Cheers
Click to expand...
Click to collapse
All of the ROMS will work for Softbank as I have tried pretty much all of them by now. All of the files you need should be on this forum/wiki or linked from here.
Here are the main ROM files.
http://wiki.xda-developers.com/index.php?pagename=Hermes_Upgrades
I have only done this for about a week so its not too difficult. Need help just make a thread after searching for the answer first.
Have Fun.
is there a bootloader guide sorry for being a bit stupid but when i press the buttons to get it into boot mode all that is displayed on the screen is some colored lines and herm200 ipl-1.00 herm200 spl-1.04 am i doing it wrong
That is bootloader mode. You have to connect via USB with MTTY to give it commands.
http://wiki.xda-developers.com/index.php?pagename=Hermes_BootLoader
jokinwa thank you ive been looking for that

Stuck on 5% - URGENT

Hello everybody - can anyone help me at this moment. I am right now sitting with my Hermes connected through USB. I was flashing the standard ROM with RUU_HERMES_HTC_WWE_1[1].35.255.2_1.35.255.102_1.08.00.10_SHIP. Unfortunately it stopped at 5% some half an hour ago. I prefer to ask you before disconnecting it. Please help!!!!!!!!!
OK, having no answer I decided to disconnect it and look for an answer. Now I know that I have a 1000 USD brick and no possibility to put it back to work.
I now suspect that the upgrade did not work properly because my device had a CID lock. That is quite strange however, because I bought it on the open market without any commitment to any GSM operator.
I am now stuck on the tricolor bootloader screen with SPL 1,09.
Basing on the post: http://forum.xda-developers.com/showthread.php?t=285157 - especially on the lines:
"1.09
You can't downgrade to bootloader 1.04 by flashing a Shipped ROM. However imei-check.co.uk is able to downgrade the bootloader.
There was a solution posted on this forum, but it was stolen from imei-check and was removed. If you are not willing to pay you have to wait until another solution is developed.
The RadioROM can't be upgraded. You have to downgrade to bootloader 1.04 to unlock your device.", despite seeing info on the website, I paid to imei-check the 20 pounds.
So far I only lost money, time and nerves trying to downgrade or "repair" my hermes. Nothing works. If anybody has any suggestions please share on the forum or PM me.
BTW I started the whole process with SPL 1,04.
Sounds to me like a flaky USB port which is why it stopped at 5%. Try another port in the rear of your PC and re-flash. Be sure to follow the mantra:
Windows XP, screensaver, powersave disabled
No other programs running.
i had a similar problem probably with the flaky usb port as Sleuth255 mentioned. trying with a different pc is another option if you have one and that was what i did with success.
im not sure about the hermes.. but i know on the wizard as long as you could get to the bootloader screen (the RGB screen) that your device isnt bricked yet.. i would follow the other suggestions about usb ports and using different pc's, i bet you can make your $1k work for you again
Try:
Go into bootloader by pressing down both the POWER button and SIDE OK together and using the stylus at the same time to press the RESET button at the bottom.
Make sure you have disabled the USB connection in ActiveSync, before trying to connect to the bootloader:
File --> Connection settings --> uncheck "allow USB connections"
Connect your USB-Cable
Download mtty.exe. Start it and connect to USB
When you see "USB>" Type "info 2". You should get: "HTCS" + CID + (4-byte checksum) + "HTCE". Remeber what CID you have.
Look for a Shipped ROM that matches your CID
Download and flash it using a different USB-Port or PC than the last time
Afterwards you will be able to use the file that you got from imei-check. The imei-check downgrader/unlocker only works if you've got a working operating system on your device.
After typing "info 2" in mtty.exe I get the following line
HTCSF kEŘ(HTCEUSB>
Which of those is the CID? I cannot find any matching one in the Wiki.
corrupted CID by wrong flash.
OK, I have now the confirmation of the diagnosis - as I was suspecting.
Can I now have some help in the solution?
Some people succeded with the method described as "problem 5" here:
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems
but some others don't succeed and have a brick. Try the steps on the wiki, if you are not able to fix it this way, send it to repair centre.
Following the steps from point 5 of the given website, I only get the following lines:
USB>password 0000000000000000
HTCSPass1.CMˆËHTCEUSB>
USB>set le 1
USB>erase a0040000 c80000
HTCST ÚČŇHTCEUSB>
USB>erase a0cc0000 c80000
HTCST ÚČŇHTCEUSB>
USB>erase a1940000 640000
HTCST ÚČŇHTCEUSB>
USB>set le 0
USB>
Unfortunatelly nothing changes.
I've the same problem. I was flashing the HTC 1.18.416.1 1.18.416.101 1.14.00.10 but the process has stopped to 89 % and now the phone is in bootloader mode spl- 1.06 and don't enter in windows mode !!! My cid is HTCSORANG001a#USB> I hope that i've not a brick !!!
mtadeuszak said:
Following the steps from point 5 of the given website, I only get the following lines:
[...]
Unfortunatelly nothing changes.
Click to expand...
Click to collapse
Your bootloader is 1.09 and you'll not be able to flash anything because the CID will not match. Send it to service centre.
deika95 said:
I've the same problem. I was flashing the HTC 1.18.416.1 1.18.416.101 1.14.00.10 but the process has stopped to 89 % and now the phone is in bootloader mode spl- 1.06 and don't enter in windows mode !!! My cid is HTCSORANG001a#USB> I hope that i've not a brick !!!
Click to expand...
Click to collapse
Your phone is not trashed, but there is no rom matching your CID yet. You should have cid unlocked it before flashing a rom with BL 1.06.
Try to boot OS again using "set 14 0" (see wiki, "problem 4"), if that doesn't fix it (chances are it will not), then wait until orange releases a rom upgrade with CID "ORANG001".
I've try the procedure "Problem 4" but after "write nand success" and sr it don't start. My cid is always ORANG001 with spl-1.06
pof said:
Your bootloader is 1.09 and you'll not be able to flash anything because the CID will not match. Send it to service centre.
Your phone is not trashed, but there is no rom matching your CID yet. You should have cid unlocked it before flashing a rom with BL 1.06.
Try to boot OS again using "set 14 0" (see wiki, "problem 4"), if that doesn't fix it (chances are it will not), then wait until orange releases a rom upgrade with CID "ORANG001".
Click to expand...
Click to collapse
Please Pof try to help me. Where can i find that rom ? Thanks
You can't find it at the moment. It's not released yet
sn00x said:
You can't find it at the moment. It's not released yet
Click to expand...
Click to collapse
But you think that it will be available ? Thanks
Yes it will surely be released I think. But nobody knows when. Perhaps tomorrow, perhaps next year.
It bet it will be listed here when it's available.

Downgrading to 1.04

Hi all,
I know this has been asked and answered lots of times, I have read all the wiki posts I could find, but still I'm not 100% sure that I understand correctly, hence this question.
I have a Dopod 838 Pro (Hermes) which I have SuperCID'ed and loaded with bootloader 1.09.
My ppc gets stuck on the windows mobile screen, and in addition I can see in the HTC subsplash screen the "NO GSM" indicator for a flick of a second.
I can go into bootloader and connect with mtty.
In another thread (and also in the wiki), it is suggested that the only way to get my machine back, is first to downgrade to SPL 1.04, and the only way to do this since I'm at 1.09 and no windows, is to purchase the IMEI-CHECK tool .
Am I correct in understanding this? or is there another way?
Thanks for any and all help.
Chris
No, I think you quit reading a bit soon.
With the new unlocker v3 and Des' SSPL flashing method, you no longer need to downgrade from 1.09 to flash anything. Simply find the newest version of the ROM and Radio you are trying to load and run the exe. Hard to believe, but it's really that easy.
Hi and thanks for the reply,
will the v3 unlocker work even if I cant boot my ppc and so I cant connect with activesync?
The only thing I can do, is boot into bootloader on the ppc and connect using the mtty tool.
Can I still use the method you suggest?
Thanks again,
Chris
T-mobile unlocker bootloader 1.09
chrisvor said:
Hi and thanks for the reply,
will the v3 unlocker work even if I cant boot my ppc and so I cant connect with activesync?
The only thing I can do, is boot into bootloader on the ppc and connect using the mtty tool.
Can I still use the method you suggest?
Thanks again,
Chris
Click to expand...
Click to collapse
Im having the same problem
Hi X01HT Rock....
can I ask u a favor? If you find a solution please PM me... I will do the same
thanks
Chris
you can't use the unlocker unless you can copy it to the device and run it from there.
from xda wiki
Problem 5: Device shows NO GSM when booting
* The radio stack is screwed, you don't get GSM signal and the phone says unknown SIM status
* Device won't start after trying to unlock it with HTC Universal Unlocker (HTC_Uni_SIM_Unlock_v1)
Here is how to fix it:
1. Disable activesync on your computer by right click on activesync icon -> connection settings -> uncheck "allow USB connections".
2. Put your Hermes in bootloader mode
3. Connect device to computer using USB cable.
4. Open mtty.exe and select USB port, then connect.
5. Hit enter twice, you will see the "USB>" prompt.
6.
Type the following commands (do not copy paste!!!)
USB> password 0000000000000000
USB> set 1e 1
USB> erase a0040000 c80000
USB> erase a0cc0000 c80000
USB> erase a1940000 640000
USB> set 1e 0
7. Reset your phone and put it back in bootloader mode
Click to expand...
Click to collapse
now copy unlock v3 to your phone, and run on the phone.
download radio 1.34 and run on your pc, while your device and pc is in activesync mode.
I believe all of this is in the wiki.
lpsi2000 said:
I believe all of this is in the wiki.
Click to expand...
Click to collapse
yeah, but the guy's device is locked with a 1.09 bootloader. we might need POF's help here.
please PLEASE guys, i need your help here (POF are you reading this?)
My machine was made SuperCID using v2a before all this sh*t happened and it was running smoothly.
It now seems that some of the mtty commands I read and tried to apply resulted in the SuperCID status to go away and now it's *scrambled* (info 2 results in "HTCSF kEØ(HTCE"). So now I cannot flash ANY rom into it even if I could.
I get to the bootloader (SPL 1.09) and also up to the windows mobile splash screen.
Also at the HTC subsplash I can see the "No GSM" msg for a fraction of a second.
Please help me unbrick this baby. I can't afford to buy another one
cant run the mtty that way
I have tried to run the password and every thing it I am having some problems with the communication
HTCST ÚÈÒHTCEUSB>
USB>password 0000000000000000
HTCSPass1.CMˆËHTCEUSB>set 1e 1
USB>erase a040000 c80000
HTCST ÚÈÒHTCEUSB>erase a0cc0000 c80000
HTCST ÚÈÒHTCEUSB>erase a01940000 640000
HTCST ÚÈÒHTCEUSB>set 1e 0
USB>
this is what happens then I try to rest the phone but it just goes back to whatit was doing.
I think that I have a language problem here.
chrisvor said:
My machine was made SuperCID using v2a before all this sh*t happened and it was running smoothly.
Click to expand...
Click to collapse
SuperCID unlocker v2a would not have worked on SPL 1.09. It might have said that unlocked successfully, but it wont have unlocked. Only unlocker 3 will unlock a SPL 1.09 phone. You'll have to keep hammering on the "bricked hermes" sticky. Someone will get round to helping you in a day or two.
I put this in the wrong place and cannot delete. Sorry for the misspost.
Hello,
I have seen on the Universal thread a way to completly format the device. After that lot of people who were stuck in windows mobile screen have recovered their device.
I dont know if it is working with hermes.
http://forum.xda-developers.com/showthread.php?t=289325
X01HT Rock said:
Im having the same problem
Click to expand...
Click to collapse
Me too....!!!! Can't solve this problem
.VIBE said:
you can't use the unlocker unless you can copy it to the device and run it from there.
from xda wiki
now copy unlock v3 to your phone, and run on the phone.
download radio 1.34 and run on your pc, while your device and pc is in activesync mode.
Click to expand...
Click to collapse
I did what you said before but can't solve the problem
.VIBE said:
SuperCID unlocker v2a would not have worked on SPL 1.09. It might have said that unlocked successfully, but it wont have unlocked. Only unlocker 3 will unlock a SPL 1.09 phone. You'll have to keep hammering on the "bricked hermes" sticky. Someone will get round to helping you in a day or two.
Click to expand...
Click to collapse
@.VIBE:
My original SPL at the time when I applied v2a unlocker was 1.01, and v2a unlocked it, I verified it with "info 2" in mtty just after, and also after all this mess started.
Something I did while trying to get out of this mess, changed my SuperCID status and corrupted it.
Is there a way to make it superCID again if the only thing I can connect with is mtty?
Thanks
Chris
You guys with bricked phones need to carefully read and understand ALL of the "dead hermes? corrupted radio? Post comments here" sticky!
Everything that POF currently knows on unbricking your device is in there also Superdave has some help for those who can get into KITL mode. Even then not every brick is recoverable at the moment, but you need to spend some time reading to find out!!
I've noticed that POF's not as quick as he used to be in replying to these kind of threads, I surmise he could be a little fed up with repeating the same thing over and over again, but I could be wrong.
Best of luck to you and my advice at the moment to anybody else coming across this is to SuperCID your phone and always try to keep your bootloader at SPL 1.04 (upgrade using mtty) as it makes recovering from bricked phones much easier.
Im having the same problem
There Is A Way Of Downgrading From 109.
Search Google For Downgrade_SPL Then Do This.
1. Go to Google, search for DownGrade_SPL.rar
2. Connect your tytn to PC and wait until activesync completed.
3. Run M3100v3cUnlock.exe. Once you see checking device.... in DOS box and whilte screen on your tytn, close the program (Dos box) immedaitely.
4. Run ROMUpgradeUt.exe and follow the japanese wizard to complete the boot loader downgrade.
5. Reboot your tytn and then put it into bootloader mode agian, you should see SPL-1.04. Great!
Cheers
@Mousey
You need to be able to fully boot into the OS to connect to activesync and the phones described here can't. The only other way I know of downgrading from 1.09 to 1.04 is from KITL mode which not all ROMS have. Full details are in the sticky I mentioned earlier.

PLEASE HELP ME TO UPGRADE MY K-JAM FROM WM5 to WM6

these are the details of my device:
I want to install Windows Mobile 6 Professional
I want to install Windows Mobile 6 Professional on my imate K-JAM. its details are mentioned as under:
Received Info Via:
Wizard Service Tool v4.2.1
Device Info:
CPU: Texas Instruments - OMAP850
MODEL: Wizard
=> Bootloaders:
IPL: 2.26.0001 (G4 device)
SPL: 2.26.0001 (G4 device)
Copyright (c) 2003 High Tech Computer Corporation
=> Firmware:
OS: 5.1.xxx (Build 14955.2.3.0)
ROM: 2.26
Registry AKU: .2.3.0
Radio: 02.25.11
Protocol: 4.1.13.12
=>Extended_ROM:
Version: 2.26.10.105
Name: Extended_ROM
Status: hidden
=> Drives and partitions:
|--Handle--|---Size---|
ce9df3ca - 5.00M (0x4fec00)
2ea9d13a - 48.23M (0x303c000)
4fb25f92 - 50.95M (0x32f4000)
6fb25f3e - 2.94M (0x2f0000)
cfb25fb6 - 3.06M (0x30fc00)
All Done.
I have tried a lot with different ROMs but ...i just wana weep .....i dono wat the hell is happening with all this....
some times wen the installation completes and everything looks fine as with Wizard_Love_2.26.10.2_WWE_Novii_CF2 it worked fine but when i checked the version of WM it says its same as before WM5. sometimes it completes the installation with e.g Xplore_1.1 but at the time of reboot it shoes bootloader screen (try color screen). then i re-install the original WM5 ROM and get my device back in action from that BRICKED HELL.
please help me out and tell me the right path to go on...
1- is it possible to upgrade this device to WM6?
2- if yes then what are the exact files and exact method to do all that?
3- I NEED IT URGENTLY.... I MEAN THE ANSWER.?
thnx and regards,
Yawar
oh one thing more i have checked the CID lock the answer is:
SPL version is 2.26.0001
DOC chip is write-protected!!
Downgrade SPL to no higher than 1.06 and
repeat procedure.
Now Tell Me Wat to do????
http://forum.xda-developers.com/showpost.php?p=1849388&postcount=3
Download the ROM from this page:
http://rapidshare.com/users/IW25NT
Install the ROM which is clean vanilla.. I have installed the same in my kjam and it works fine...
for more info mail me at [email protected]
y4yawar
To upgrade your phone read and do as instructed in stickies 'HardSPL' or 'SoftSPL' in this forum.
Cheers!
Resolved By Me
Well all, i have resolved this problem. the reason was CID Locked. I used one tool to UNLOCK CID. Now everything works fine.
Thanks For all of yours help
y4yawar said:
Well all, i have resolved this problem. the reason was CID Locked. I used one tool to UNLOCK CID. Now everything works fine.
Thanks For all of yours help
Click to expand...
Click to collapse
For free? that's not possible unless you're talking about HardSPL (which isn't a real CID unlocking...)
y4yawar said:
Well all, i have resolved this problem. the reason was CID Locked. I used one tool to UNLOCK CID. Now everything works fine.
Thanks For all of yours help
Click to expand...
Click to collapse
Which tool did you use? Because I used all the tools I know but couldn't unlock that G4 monster. I am going to the mental hospital if I don't find the solution in 24 hours,
sipraomer said:
Which tool did you use? Because I used all the tools I know but couldn't unlock that G4 monster. I am going to the mental hospital if I don't find the solution in 24 hours,
Click to expand...
Click to collapse
Hold your horses here! if its a G4,it cannot be CID unlocked,there's no free solution for this,the only other way to get it upgraded is through 'HardSPL' or 'SoftSPL', both the methods are posted as stickies in this G4 forum,read and do it correctly.
zabardast_1 said:
Hold your horses here! if its a G4,it cannot be CID unlocked,there's no free solution for this,the only other way to get it upgraded is through 'HardSPL' or 'SoftSPL', both the methods are posted as stickies in this G4 forum,read and do it correctly.
Click to expand...
Click to collapse
hahahh. Yeh I managed it. Illusion is a dangerous enemy. My saying.

dead hermes? corrupted radio? Post comments here

This is becoming a common issue and there are a lot of people with a bricked Hermes devices, usually because of a WinXP crash, bad USB port, USB hub or pulled USB cable while flashing.
This thread is in the aim of finding a solution to all these common problems: if you are the owner of a bricked hermes, please post your comments here instead of opening a new thread.
There seems to be 3 types of bricked (or dead) hermes devices:
Type 1 bricks: Corrupted radio area: No GSM, No CID, no IMEI
Usual reason for that is flashing whent wrong when RUU was flashing the radio stack (GSM.nb). Other reason can be that you flashed radio from another device (universal unlocker run on hermes, for example).
Within the type 1 bricks, there seem to be two variants:
Type 1a:devices which can boot windows mobile but can't use the phone functions.
Type 1b: devices which can't boot windows mobile and are stuck while booting, see also type 2 bricks below.
Type 2 bricks: Stuck in boot process
Usual reason for that is that flashing went wrong when the RUU was flashing any rom part different than IPL and SPL. Symptoms can vary depending on which is the ROM part affected. The most common is OS because it is the bigger part. Radio is the second most common.
Type 2a: When the phone boots, it goes directly to bootloader mode (tri-color screen)
Type 2b: When the phone boots, it stays in subslpash screen (htc or operator logo)
Type 2c: When the phone boots, it doesn't pass the windows mobile logo
Hybrid Bricks: combinations of both type 1 and type 2 bricks
These usually have a corrupted radio and are stuck in bootloader, unfortunately these are very common too, and the most dificult to repair.​
We made a wiki page long time ago whith the solutions that have worked for some people to fix bricks, unfotunately these solutions do not work for everyone, some devices are more bricked than others
First thing you have to do is visit this wiki page and follow the process explained: Common upgrade problems
If you can't repair your brick after following the process, please provide a USB monitor capture in ANSI text format (this is explained on the wiki page too) as this is the only thing that can give us a real idea on what your exact problem is. Please don't come crying and say "help me" because we can't help you if you don't provide useful information, you are in front of a big problem and you will have to loose some hours reading and experimenting before repairing your brick. If you are not willing to loose some hours reading, go and send the device to the service centre for a repair as it is the only valid solution most of the times.
Hopefully after research of everyone in this thread we can find new solutions for some of the bricks
EDIT: Please use axiom's comment below as a template for your comment and attach USB monitor capture: If your bootloader is 1.04 attach capture when trying to flash an extracted radio ROM and when trying to flash a shipped rom update. If your bootloader is 1.06 or 1.09 only attach the usb monitor capture of the shipped update.
EDIT (2007-03-22):
After more than 3 months since this thread started and more than 660 comments, we have now solutions for some bricks, so I compiled the most common on this unbricking guide:
How to unbrick your bricked hermes​
Please spend some time reading through the wiki and thread comments before posting desesperately, otherwise you'll get no answer.​
The following info may help in isolating the problem and keeping the clutter down.:
I'm including my info.
Model: O2 XDA Trion
ROM Before Flash: Dopod 1.23.707.4
Radio Before Flash: 1.16
Bootloader Before Flash: 1.04
Flash failed at: 6%
Flashing ROM: 1.35.255.2
Flashing Radio: 1.18.00.10
Bootloader After Failure: 1.09
CID Before Failure Super CID: Yes
CID Corrupt: Yes
Radio Corrupt: Yes
No GSM Error: Yes
Stuck In Bootloader: No
Stuck On Windows Mobile Splash: Yes
Can boot into OS: No
Tried mtty command set 14 0: Yes
Tried wiki problem number 5: Yes
mtty info 2 output: CID: Wait interpreter timeout HTCSF kEØ(HTCEUSB>
Current Device Status: unusable
Hi, I've managed to brick my Hermes as well.. First time on any of my HTC Devices....
Model: Vodafone v1605
ROM Before Flash: Voda Launch ROM
Radio Before Flash: Not sure
Bootloader Before Flash: 1.04
Flash failed at: 8%
Flashing ROM: 1.35.255.2
Flashing Radio: 1.18.00.10
Bootloader After Failure: 1.09
CID Before Failure Super CID: Yes
CID Corrupt: 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
Tried wiki problem number 5: Yes
mtty info 2 output: CID: Wait interpreter timeout HTCSF kEØ(HTCEUSB>
Current Device Status: unusable
You may already know this, as I posted it in all over the other threads of people with bricked hermes, but I'm posting again to make sure every piece of information is concentrated on this thread, and see if finally this can get us somewhere
HTC bootloader returns data encapsulated in a block between HTCS (start) and HTCE (end), before the HTCE there's always a 4-byte checksum of the data. You're getting a timeout when you query the bootloader for the device's CID, so the output you see is "F" which means failure (T means success) encapsulated in this HTCS/HTCE block, plus the checksum. The CID is read from the security area of the device, found on radio, but the wrong flash corrupted the radio area.
As the CID is not returned, the error you get when flashing the ROM is "CID Not allow (255)". The security level depends on CID, as the device has CID corrupted, the security level returned is FF (255), which means you can't bypass CID check in bootloader.
You both have bootloader 1.09 which does enforce CID checking (as opposite to bootloader 1.04 which has a known bug to circumvent this). This bootloader also only allows updates with bootloader version > 1.09 (and no such bootloader exists yet).
Bootloader 1.04 allows to flash unsigned code in radio with radio bootloader command 'rwdata', but radio bootloader is accessed through command 'rtask' and this command has been removed in following bootloader versions.
All the commands to flash code in bootloader 1.06 and above require the code to be signed (the commands are 'wdatah' and 'lnbs'), and bootloader checks the signature before the code is actually flashed on the device. So modifying a 1.04 bootloader to show itself as 1.10 is not possible because it will return a certificate error and will not be possible to flash.
Command 'lnbs' doesn't check CID, but it is only enabled if device has security level=0, and as your radio is corrupted and your seclevel=FF it will not be possible to use this command to fix it even if you had a signed bootloader, so 'wdatah' is the only command that would allow you flashing code, but 'wdatah' requires a NBH header to be sent, which contains the CID of the update and is checked against the missing CID on your device and will never match (even if you could modify the NBH header and have a valid signature after).
In conclusion, my recommendation to you is that you send the device to service centre to get it repaired and don't try to fix this by yourselves, as you will go nowhere.
Many thanks for explaining it so succinctly Pof, much appreciated. With this error I've learnt a heck of a lot more about the ROM flashing process... I guess it may be time to send the unit for repair!
This is the full report after I soft rest my phone while the USB is still connected. Would any one know what the rest of the data means? I did it in the morning then just left it for the day to see what would happen, I just got back from work.
onj: can you use axiom comment as a template to provide information?
radioerror.txt: I see you're using the Himalaya upgrade utility there... rbmc reads data from memory, but I don't know what is at 0x70010000. It would be better if you can provide a log of hermes RUU.
Model: x01ht
ROM Before Flash: i-mate
Radio Before Flash: 1.07.03.10
Bootloader Before Flash: 1.04
Flash failed at: 0%
Flashing ROM: JASJAR_WWE_19096_19505_11300_AKU_3_2_ship
Flashing Radio: 1.13.00
Bootloader After Failure: 1.04
CID Before Failure Super CID: success
CID Corrupt: don't know
Radio Corrupt: Yes
No GSM Error: Yes
Stuck In Bootloader: No
Stuck On Windows Mobile Splash: Yes
Can boot into OS: No
Tried mtty command set 14 0: Yes
Tried wiki problem number 5: Yes
mtty info 2 output: CID: stalls
Current Device Status: unusable
I will upload the usbmonitor with using
RUU_HERMES_HTC_WWE_1[1].35.255.2_1.35.255.102_1.08.00.10_SHIP
the upgrading dies after info 3
computer says ERROR [222] Device not responding
that's with all the RUU's that I use and even the full upgrade ROM
Hi, I have a herm 200 an i have a Type 2a bricks (it goes directly to bootloader mode tri-color screen).
But i upgrade with the rom (ME_DT_WWE_1182553_106_10303_Ship) and all run good. but 3 moths later i have the type 2a bricks.
I try with that solution (http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems) and others and NOthing.
In screnn say herm200 ILP-1.00 and Her200 SPL-1.04.
ps: sorry my english is very bad.
@onj: Oh ****! You where trying to flash an HTC Universal ROM in your HTC Hermes!! These are different devices, most probably that's what screwed it.
From your attached file I see bootloader does not answer to any command.
@landtd5: please use axiom comment as a template, and attach USB monitor capture when tryng to flash a shipped rom and a radio rom.
Yup, I upgraded with the wrong Rom. After going through the forum for the past 2 weeks I realized what I did. I guess it's time for me to send it to the shop
thanks for you help pof
jash431 Dead Tytn
I had tytn with this rom
"TYTN_me_dt_wwe_1182553_106_10303_ship" which has bootloader 1.04
And I upgraded with
"RUU_HERMES_HTC_WWE_1.35.255.2_1.35.255.102_1.08.00.10_SHIP"
during upgrade stopped and after that I cannot do anything with it
It never answer to any solutions .
Please help me .
USB monitore is attached here .
jash431 said:
USB monitore is attached here .
Click to expand...
Click to collapse
This is not useful: You saved LGS file, please follow instructions in wiki, you need to EXPORT as ANSI TEXT file. Also please use the 1st comment as a template to provide useful information.
Jash431
I exported in ansi text
@jash431: doesn't return anything... when you connect to bootloader on mtty, do you see the USB prompt? does it answer any commands?
Jash431
I'm sorry . this is complete one .
yes I can work with mtty.exe and my info 2 is "HTCSF kEØ(HTCEUSB>"
jash431: hybrid brick with corrupted radio and bootloader 1.09. Send it to repair centre.
jash431
is it theorically possible to fix my tytn . I mean maybe in future someone make a downgrade or SuperCID rom !! .
Because in my country doesn't exist repair center (Iran) . So what can I do ???
then keep it until something is found to fix this, creative solutions to the problem will come to your mind after looking everyday at a $500 brick.
Jash431
Thanks pof for your answer . I'll check my private message every day , for your solution and I remember you whenever I see a 500$ . ( Of course 500$ doesn't exist but you do ).

Categories

Resources