Related
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
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!!
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 ).
well...
that didnt work :|
running vista ultimate sp1, following all the guides, trying to update to RUU Nike Radio 1.58.21.23,
had the RUU Nike Radio 1.58.16.27 installed...
everything went fine untill it came to 99%... it stalled and the install program told me to follow some
recovery steps, i did, but vista cant recognize the usb device... henche, i cant connect to the phone...
is there a place for drivers or so...??
please help out a noob...
anyone...??
when i start my phone i only get the different color screen, and it says:
Niki100
SPL-1.6.0000
CPLD-4
in the top right corner it says: RUUNBH
Ah easy ... Download MTTY disable Activsync USB Connection and start MTTY -> set Connection to USB -> if you see CMD> use the commando "boot"
Have you a Windows XP PC? Vista make some troubles!
Your device boot now! if your device make troubles ... flash a full rom with SPL, Radio and OS! Have you CID Unlock your device? HardSPL, USPL or SSPL? I want know to cross check!
Your SPL is very low ... i havent this version to test it with all radio roms.
will try this asap...
i used sspl, dont know if it is CID unlocked, think so...
ok...
did what you said, but what is suposed to happen...??
i get this in the log window of mtty:
boot
Fill RSVD information for block 288 to 309
Storage start sector=0x8940, total sector=0x12980
Storage start block=570, total block=1190
Total Bad Block in CE: 0
Erase physical block from 860 to 2032
si backup: Erase physical block from 2032 to 2048
No card inserted
OEMGetUpdateMode
OEMTranslateBaseAddress 23 80000000 80000000
IPLMSG:0x8:INFO: Loading image ...
IPLMSG:0x9:INFO: Jumping to image...
OEMLaunchImage 80000000
Jump to Physical Address 10300000
you say my spl is low, any way to update this...?
uhm ... realy bad!
what nike device is yours? can you say me your country and original os your device are?
i got it working again...
tried the mtty thing again and i booted, i flash with the hardspl thingy, and updating the rom now to the: RUU_Nike_HTCASIA_AUS_1.31.710.12_Radio_Nike_1.58.21.23_signed_Ship_PA
i bought mine in norway, december 2007
its alive
thank you for your help, you serously saved my day
^_^
try to flash radio again and tell me if you get the same problem again or not! its for debuging! i think ... some flash problems come from vista.
i used a wxp laptop, and flashed with the RUU_Nike_HTCASIA_AUS_1.31.710.12_Radio_Nike_1.58.2 1.23_signed_Ship_PA rom and radio, and it all works just fine
will try again with the updated radio as soon as i get home...