Related
Firstly, let me thank everyone for their help in advance.
Tonight I tried upgrading my ROM to the newest Cingular ROM. I'm on Cingular in NYC and have been having radio problems so I hoped Cingular's optimizations would help. Anyway, I was running the i-mate ROM previously. I have done this many times. During the ROM upgrade, it gave me the usual Device ID error so I restarted the upgrade utility and evertything was good. Well, at 19% progress it stalled, eventually crapping out citing a communications error. The device won't reboot now.
I got the device in tri-color mode and began the process again. The upgrade stops with Device ID error, but now the restart trick no longer works! I also tried updating it with both the original TyTN ROM and the i-mate ROM I was previously using. They all crap out with a Device ID error! Now I have a paper weight because it also won't boot with what was loaded previously, hanging on the Windows Mobile splash screen.
Does anybody have any advice or solution???
Thanks...I'm desperate here!
See this page:
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems
Connect to your device bootloader using mtty.exe and issue the commands "set 14 0" and "task 8". This will (hopefully) boot the existing imate rom.
If this does not work run the commands "checkimage" and "info 8" and paste the output here. For more info read the wiki:
http://wiki.xda-developers.com/index.php?pagename=Hermes_BootLoader
Alternatively, you can try to flash it using HERMIMG.nbh on SD card:
http://wiki.xda-developers.com/index.php?pagename=Hermes_SDCardFlashing
Thank you...I'm going to try this in just a few minutes. Needless to say...I'm sweating!
OK guys, this is what I got running "checkimage" and "info 8". What do you think?
USB>checkimage
IPL CRC checksum = 0x24C42773
SPL CRC checksum = 0x9382C208
CE CRC checksum = 0x5D6A925D
ExtROM CRC checksum = 0xFFF79D19
Radio Image CRC checksum = Checksum: Wait interpreter timeout
0x0
USB>info 8
Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block
Block 0x3FB(1019) is Reversed block
Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1700
Partition[2], type=0x25, start=0x3000, total=0x19C00
Partition[3], type=0x4, start=0x1CC00, total=0x1DC00
CE Total Length(with sector info) = 0x3A66000
CE CheckSum Length(without sector info) = 0x3980000
USB>
Any clue on what this data means?
Thanks
CJNYC said:
Radio Image CRC checksum = Checksum: Wait interpreter timeout
0x0
Click to expand...
Click to collapse
Your radio is screwed. Format your microSD card and copy the NBH file contained in a rom upgrade (if possible use one that matches your CID). Rename the NBH file to 'HERMIMG.nbh' and put the microSD card on the phone. Power on the phone in bootloader mode and you should see the flash confirmation, press the power button to confirm and wait 30 min. This process is described in more detail here:
http://wiki.xda-developers.com/index.php?pagename=Hermes_SDCardFlashing
Good luck
Thanks POF...this will be the first thing I do tonight. I'm keeping my fingers crossed and will report back as soon as I'm done.
Thanks!
OK, that didn't work either. When the bootloader went to load the ROM from the Micro SD card I got the following message...
0028002
Not Allow
Any other suggestions??? Thanks
CJNYC said:
0028002
Not Allow
Click to expand...
Click to collapse
The NBH file you used doesn't match your CID. Use a NBH file that matches your CID.
You can see your CID by issuing bootloader command "info 2".
If you have an HTC branded Hermes (HTC TyTN) your CID will be QTEK_001, then you need an NBH file with this CID, for example "hermimg_QtekNOR_1.18.255.3_Ship.nbh" contained on HTC TyTN WWE rom.
pof...
That's the exact ROM I used and I do have an HTC branded TyTN. When I issue the "info 2" command all I get back is an "HTCSUSB>" prompt. Am I missing something?
Thanks
Probably mtty.exe doesn't parse the output of "info 2" correctly and that's why you can't see the CID, but if it is an HTC TyTN then your CID must be QTEK_001 and there should be no problems with the NBH you used... it is very weird that you get this error.
Did you try the "set 14 0" command to start OS after reset? If you can boot WM5 again you can run GetDeviceData.exe from your device to see your CID, otherwise you can use USB Monitor and look for the output of "info 2" there.
Another thing you can do is to start the TyTN 1.18 ROM upgrade using the normal procedure (RomUpgradeUt.exe), but capture the output of all the upgrade process using USB Monitor, and then export it to text file and attach it here. We will be able to see the error from bootloader and where exactly it stops the flashing process:
1) Disable activesync on your computer by right click on activesync icon -> connection settings -> uncheck "allow USB connections".
2) Put your device in BootLoader mode
3) Connect device to computer using USB cable.
4) Start USBMonitor.
5) File -> New session -> USB Monitor -> Select USB device where your phone is connected -> Check "request view" -> Finish
6) In the upper part there are two tabs: basic and complete. Click on "Complete".
7) click on RomUpgradeUt.exe and start the Rom Update Process, if everything went fine you should see all the USB traffic output on USB monitor window.
8 ) when rom upgrade fails, click on Edit -> Export and Save as type "ANSI Text files".
9) Save the file and zip it.
10) Upload the zipped file here or put it on xda-dev FTP if it is too big.
OK, I used USB Monitor and recorded the results of the upgrade attempt, which of course failed. Please see the attached file.
What do you think? Any hope?
Thanks...
-Craig
When the flash utility tries to get the CID from your device it gets this error:
CID: Wait interpreter timeout..
Click to expand...
Click to collapse
Info 2 should return:
Code:
"HTCS" + 8-byte CID + 4-byte checksum + "HTCE"
In your case the output of "info 2" shows this:
Code:
48 54 43 53 00 01 09 8C 5C 30 08 8C 66 17 09 7C HTCS...?\0.?f..|
48 54 43 45 HTCE
Your CID: 0x0001098C5C30088C (...?\0.?)
Output of "info 2" for HTC TyTN should show this:
Code:
48 54 43 53 51 54 45 4B 5F 30 30 31 D6 00 3D 07 HTCSQTEK_001.=.
48 54 43 45 HTCE
Normal CID for HTC TyTN: 0x5154454B5F303031 (QTEK_001)
I don't know what caused the CID to change, and it is not possible to change the CID on a NBH because signature will not be the same and you'll get a signature error. We don't know how to change the CID on the Hermes yet, probably someone will come out with a solution but now I don't know what to do....
Are you able to send back your device under warranty?
I'm going to try to ship it to the HTC repair center in Germany and see what they can do for me. Who knows how long this will take. I might pick up a Cingular 8525 when they are supposedly released on Friday and see how that goes. I'm not happy. I really like this device and simply wanted the Cingular network optimizations.
pof...I really appreciate the help and effort. In another thread, people are complaining that this same Cingular ROM is changing the CID's and locking phones. Oh well, back to the drawing board.
Thanks again!
CJNYC said:
In another thread, people are complaining that this same Cingular ROM is changing the CID's and locking phones.
Click to expand...
Click to collapse
Are you refering to user fun_key, not being able to downgrade after flashing cingular's 1.31 rom? He has checked and his CID remains the same, and I haven't heard of anyone having his phone locked for upgrading a ROM.
I've investigated into it, see my post here:
http://forum.xda-developers.com/viewtopic.php?t=63355&start=25
I guess your problem is that the rom upgrade flashed your bootloader and you cannot use the HERMIMG.nbh from the TyTN rom because it contains a lower bootloader version (1.04) while you have an higher bootloader version (1.06).
You can check your bootloader version by issuing the command "info 7".
Now you have tree options:
- wait for a rom upgrade with bootloader >= 1.06
- send your device to repair center
- wait until some xda-developer finds out how to downgrade the bootloader
I definitely understand this issue with the newer bootloader. Would it not stand to reason that I'd be able to re-run the Cingular ROM that failed or is this simply an issue now with the CID needing to match the original TyTN ROM?
Thanks again!
The TyTN has "flash from microSD" option much like the Wizard. On my 8125, IIRC, an SD based reflash ignored everything and put the base image + bootloader + ROMs back on; completely restoring the device to original factory specs.
I'm not sure if this is the same on the TyTN or not but it may be worth a try. The Wiki on this says that using the HERMIMG.NBH method to restore from SD may or may not ignore CID. At very least you could update the Wiki if it doesn't work
@CJNYC: I'm not really sure if your problem is related to bootloader version, CID or both.
@Sleuth255: He already tried sd-card flashing, if you follow the whole thread.
oops, now I see it. My bad...
What is this file ???
Is it aku 3.3 in english or russian????
-----------------------
MODERATOR EDIT:
Changed the subject, use this as the main thread to discuss HTC 2.05 WWE AKU 3.3 ROM issues.
Download and ROM details in the wiki:
http://wiki.xda-developers.com/index.php?pagename=Hermes_Upgrades
BE SURE TO READ THE WIKI BEFORE ASKING QUESTIONS PLEASE
English.
If you need Russian one look for it in Upload/Temp directory
It is in English, I just flashed it using 1.10mfg method
An still no MUI I presume ?
What Where Who Its New The Wwe Version?
Plz Give The Link And Why Dont You Say Anything?
bubu23 said:
What Where Who Its New The Wwe Version?
Plz Give The Link And Why Dont You Say Anything?
Click to expand...
Click to collapse
ftp://ftp.xda-developers.com/Uploads/Hermes/
Here you have.
BuT WhY TyPinG LikE ThAt ! Are YoU PaRkInsOn ?
Is it from HTC or cingular? I've heard both are about to release an AKU 3.3 rom
loll no im not parkinston maybe my keboard is
but why the file finish with test?
its not good its just test???
plz tell me im horny on that fileee(rom)
English confirmed.
Just flushed OS and Ext rom.
ROM Version:2.05.255.1
ROM Date: 01/17/07
ExtROM Version: 2.05.255.101
OS 5.1.461 (build 15671.3.3.0)
I can't get to FTP :/ what user and password ?
reg
Sar
Username = xda
Password = xda
You get to the ftp by this link no pass needed...
ftp://xda:[email protected]/Hermes/
Cheers
Seems very fast...
cant see where it says TEST though. My of been a test for the carriers, so likely the RTM for the carriers to then implement.
So far, so good... at least this one is english, unlike the Swedish update i did yesterday
in the ftp thers only the swedish rom i cant find the wwe rom??
RUU_Hermes_2.05.263.1_6275_1.34.00.10_108_SVE_HTCEUR.exe is now up... Guessing it is an official release from htc?
Cheers
Well i flashed it also.
the Test is included in the splash.bmp. =)
really... But imho the swedish one is a bit faster, but that is just subjectiv i didnt tried to test it with a benchmark program.
btw. any update from cingular?
Somethings fishy about this.
This is supposed to be AKU 3.3, but theres no WPA2 support???
not sure this is a complete ROM?
Does this mean MS Voice Command over bluetooth is fixed without the hacks?
I have detect problems with this rom! Is better wait for another!
Problems detect:
- No wpa2
- Phone connection always breaking down
- Can't go to my contacts!
- ActiveSync always says pocket is out of memory (yes I reset several times)
Flash Using Lnb
This is my first time flashing using lnb and i followed the wiki about using mtty..i just wanted an experimented persons to examine the output of mtty and tell me if the update was perfectly done and if there was no problems in nand please...
Thanks
Iverson....
USB>
USB>task 32
Level = 0
USB>task 28
Storage format start
Write Nand Success
dwBlockToWrite = 13
Storage start block: 461
Storage Total block: 475
Total Bad Block in CE: 0
NeedToEraseBlockStart: 474
Storage format success
USB>lnb 06_OS.nb
:F=06_OS.nb
:A=501A0000
:O=00000000
:L=FFFFFFFF
start NB image downloadSH
Load ADDR: 501A0000 Length: 3C0C800
*********************************************
*********************************************
*********************************************
*********************************************
*********************************************
*********LAST BLOCK, dwBytesCollected=0x13800
Code entry point at 0x53DA0000
Write Nand Success
USB>task 28
Storage format start
Write Nand Success
dwBlockToWrite = 13
Storage start block: 473
Storage Total block: 463
Total Bad Block in CE: 0
NeedToEraseBlockStart: 486
Storage format success
USB>
Hello,
i try to flash bootloader 1.01 mfg according to http://wiki.xda-developers.com/index.php?pagename=Hermes_BootloaderMFG
It hangs after
USB> lnbs SPL-1.01.nbs 50020000
...
start NB image download
According to other threads this behavior exists if mtty can not find the file. But the file is in the same directory as mtty.
Does anybody has an idea what is wrong?
Thanks
Andreas
did you do the "Task 32" first? and if you did did you get "Level = 00"
yes, but i only one 0
USB>task 32
Level = 0
USB> lnbs SPL-1.01.nbs 50020000
i got some output at this point, but i cannot remember exactly
???
? 50020000
? 00000000
????
The last line was: start NB image download
My device is SuperCID. SPL 1.09
there's your problem then; you need SPL-1.04.
I suggest you load Hard-SPL and try again...
also, might I heartily recommend that instead you download my MFG pack and use SSPL with 1.01 rather than flash it to your device... or at least use my patched 1.01 (create an NBH)
I get that message whenever I do not type the name of the file correctly, like for example, sp1-1.01.nbs instead of spL-1.01.nbs (the latter being the correct spelling). Just my two cents..
I had 1.09 before, coz I updated with full RUU versions of roms (like 2.06.502.3 cingy or 2.05.255.1 HTC), and I had no problem to downgrade to 1.01 MFG and now to 1.01 oli... I also used mtty, device was supercid, used commands was
USB>task 32
Level = 0
USB> lnbs SPL-1.01.nbs 50020000
USB> task 8
If I remember correctly, task 8 automatically SW reset herm... maybe I am lucky one?
take a look at your mtty icon. Does it say MFC or does it look like a serial connector. If it says MFC then you have the wrong version of mtty.
my guess: it says "MFC"
Thanks for all your answers. At the moment a'm at work and cannot try your suggestions.
But i have some further questions:
>olipro: there's your problem then; you need SPL-1.04.
According to the wiki:
"This is a very special bootloader which can be flashed in any bootloader version BUT to flash it your Hermes must be SuperCID first..."
...can be flashed in any bootloader... what does this mean? i thougt i can flash it from 1.09. sinmae was able to do it. (or did i miss something)
>crazyut: wrong file name
i checked this several times. i typed the right name, but i do not now whats the working directory of mtty. i put the nb-file in the same directory as mtty and startet mtty from a dos-prompt. so this should be ok.
>Sleuth255: wrong version of mtty
i tried to investigate this yesterday. somebody said he has version 1.11a. i have version 0.01. it says MFS. so this should be the problem. but this is the version from the wiki:
http://wiki.xda-developers.com/index.php?pagename=Hermes_BootLoader
http://wiki.xda-developers.com/uploads/mtty.exe
where can i get the right version? (at google i found mttty (3 t))
Thank
Andreas
Use the mtty.exe included in this pack, mtty and nbs file in the same dir.
I can't flash SPL 1.04 over mtty.
Code:
USB>
USB>task 32
Level = 0
USB>lnb SPL-1.04.nb 50020000
Command error !!!
USB>
What is the problem?
igord said:
I can't flash SPL 1.04 over mtty.
Code:
USB>
USB>task 32
Level = 0
USB>lnb SPL-1.04.nb 50020000
Command error !!!
USB>
What is the problem?
Click to expand...
Click to collapse
PLEASE tell me why you are trying to do this outdated DANGEROUS operation??
Download duttys nbh tool, pack the .nb file into an RUU and do it using safe SSPL........messing with mtty can be a risky business.
Hi.
my phone mtty conection is not working...
When the mtty is open the only thing i see is: CLIENTCLIENTCLIENT
So, untill i get this thing working i can't try any more updates to bring alive my RADIO!!!
can anyone help me to configure the phone, or the MTTY?
THANXS!
cauboi25 said:
Hi.
my phone mtty conection is not working...
When the mtty is open the only thing i see is: CLIENTCLIENTCLIENT
So, untill i get this thing working i can't try any more updates to bring alive my RADIO!!!
can anyone help me to configure the phone, or the MTTY?
THANXS!
Click to expand...
Click to collapse
Did you disable Active Sync USB?
Yes, many times i check and unchek the "Allow USB..."
Which SPL do you have?
hi, my phone is:
At&t 8525
IPL 1.04
SPL 2.30
Radio (unknown, i don't remember but i gues it will be the orginal 1.54)
ROM 2.15.502.3 (04/09/07)
Thank you for reading!
You can't use MTTY with SPL 2.30, you need SPL 1.04, SPL 1.06 (no rtask command), but the best SPL to use with MTTY is 1.04.
igord said:
I can't flash SPL 1.04 over mtty.
Code:
USB>
USB>task 32
Level = 0
USB>lnb SPL-1.04.nb 50020000
Command error !!!
USB>
What is the problem?
Click to expand...
Click to collapse
you should flash SPL With RUU;MTTY command work with SPl. so the MTTY commands different form different SPL
Version.
Ok guys,
i think i'm in a sort of big trouble. I got SPL1.2, i was installing this Miky ROM and then at 91% Windows Mobile Device Center crashed on my pc. Now what i have is a 7500 booting with strange lines on the screen and then fading to white. I tried to pull out the battery and then to recover but nothing is working. I broke my 7500??? Why God is never here when i need him???
See if you can get into bootloader (tri color screen) if you can flash a factory rom. Have a look here, you should find what you need or a link to the needed resources http://forum.xda-developers.com/showthread.php?t=429013
Cheers
BR
***Why You Try This !!!___carefully step by step !!!!!!!!
cmonex
Senior Member Join Date: Jul 2006
Location: Budapest
Posts: 2,314
--------------------------------------------------------------------------------
here's an experimental program I made to make the process more automatic so users can fix their own wifi without our help.
this is good for both corrupt modelid and corrupt wifi, and fixes both at the same time.
STEP BY STEP:
1. download attachment at the end of the post for mac1.exe (requires .net 2.0 installed on the PC)
2. you will also need to download the other attachment in this post for the mtty program.
3. enter bootloader (tricolour screen) manually by pressing and holding camera button all the way in (yes I mean that, press it in as hard as you can!!), while doing a reset, then keep the camera button held until you see the tricolour screen.
4. disable USB in activesync (wmdc if you have vista - in this case, do not kill wmdc, just disable usb in it!!!)
5. run mtty and select USB option from the dropdown box!
6. then press enter in main window that comes up, see if that gives you Cmd>
7. now you should have Cmd>, if not, re-check if you did the above steps right until you get Cmd>
8. now run the mac1.exe, type in your MAC address you want to use for the Athena, if you have SPL 3.xx reported on the tricolour screen, then use the button for SPL 3.xx, otherwise if you have SPL 1.xx reported, use button for 1.xx.
9. this should have generated a .bin file for you, copy that bin file in the folder of mtty.
10. now, in mtty, type (do not copypaste!) this command: task 32
11. this should return Level = 0
12. now, you must only do one of the two following commands:
- if you have SPL 3.xx, then type (do not copypaste!!) this command: lnb filename.bin 76508000
(there filename is the name of the .bin file you generated - don't forget to put .bin after filename, as the full name is needed).
- OR, if you have SPL 1.xx, then the command is different (do not copypaste!!): lnbs filename.bin 75108000
(there filename is the name of the .bin file you generated - don't forget to put .bin after filename, as the full name is needed).
NOTE, the command starts with a lowercase "L", not "I"!
WARNING: PLEASE DO NOT MIX UP THESE TWO DIFFERENT COMMANDS!!!
if this info helps: most people will have SPL 3.xx, and if you have AP4 (not vanilla) already running then you're definitely 3.xx
13. mtty will popup a window asking "OK", you press OK!
if you get "Fail to synchronize with the host (1)", then make sure you did follow step by step. if still same error, try placing mtty and the bin file under C:\.
14. now the file downloads, if mtty reports it flashed the file, and at the end "code entrypoint unknown", then that's it, now boot back to WM and see if wifi works.
edit: see raskell's mtty tutorial too, #36. post in this thread
if you *really* can't manage to get it working, you can still feel free to PM me.
let me know if this program and step by step description helped any.
Attached Files mac1.zip (6.3 KB, 1585 views)
mtty_0513_Test.zip (553.9 KB, 1883 views)
__________________
Here is direct link__on floor #33 ===>
http://forum.xda-developers.com/showthread.php?t=387454&highlight=mtty&page=4
Good Luck!!!