Hello,
I've been researching the Hermes BootLoader, the ROM Upgrade Utility issues a "info 3" command and gets some data and a checksum. This data is then used by the RUU to generate a dynamic password, then the RUU issues the command "password XXXX" and starts the upgrade process.
As this password is dynamic, you can't access the BootLoader in "privileged?" mode, but I don't know which bootloader commands are privileged.
I researched this because without password you cannot use command "d2s" or "s2d" to make ROM backups to SD, but after discovering how to access the bootloader with the correct password it is also not possible to issue these commands
BTW, in the attached file is described the method I used to access the bootloader with correct password. If someone could provide more information on the Hermes Bootloader, please reply to this topic or write a wiki article!
Enjoy!
I've written a page on the wiki with information on the Hermes Bootloader, if you find anything incorrect or missing feel free to edit
http://wiki.xda-developers.com/index.php?pagename=Hermes_BootLoader
Algoritm hax0r3d
http://forum.xda-developers.com/viewtopic.php?p=351363#351363
LOL! Thanks, will try that with the Hermes when I'm back home
pof said:
LOL! Thanks, will try that with the Hermes when I'm back home
Click to expand...
Click to collapse
I tried it with the data on the wiki, and it produced the same password, so it's likely to work
If you want me to send the program I used for debugging, send me a PM with your email/IM address and I'll contact you
After booting my TYTN in Bootloader
okay I think i am going to have to send my tytn back. After loading my TYTN in bootloader I did and info 8 and got the current print out. I think that it is tell me that my extended ROM is shot. Does any one know what this means? and can you tell me how to re-format my extended ROM?
I was going to post the results but made the post to long. the results are in the attached text file and help greatly appreciated
[/code]
Tried the algorithms on the Hermes and the bootloader password and radio-password were deciphered correctly Thanks TheBlasphemer!!
Full usb log here (zipped text file).
@LuckyBos: this thread is for discussing bootloader password, if you want to ask other questions about the bootloader not related to passwords please post a new topic. Btw, try to flash a new rom and see if info 8 still shows the errors, if it does post a new topic about it
where is the posix password generator?
This method will not work on bricked hermes caused by telstra wm6 because non of the WM5 shipped roms would work on these bricked hermese. considering this issue that ROMUpgradeUT.exe only appears to be inside of the WM5 Roms and not in the wm6 shipped roms and ROMUpgrade.exe cannot connect to these bricked hermese that was caused by wm6 ROMs.
does it mean that we can flash a rom to our bricked phone under wm5?
Related
Hi,
I recently had a power cut (yes, a lights off power cut!) that killed my PC half wat through installing the Cingular English CWS__001 1.34.502.1 09/21/06 ?? 1.16.00.00 32.53.7018.01H 14955.2.3.0 ROM onto my SPV 3100.
Now SPV 3100 will boot to the ROM I was running prior to the upgrade but I can't use the telephone. I'm also not able to rerun the upgrade as it got far enough through the process to upgrade my bootloader to 1.06 - therefor rendering me unable to load another ROM.
Before the crash I was using the Imate ROM as below and M3100 was sim unlocked and running on o2 3G
i-mate English CDL__001 1.20.305.3 07/21/06 1.20.305.104 1.07.03.10 32.41.7010.02H 14955.2.3.0 1.04
Please help.
Thanks
If your device is still working ok as a PDA then hopefully it just screwed up the radio update of your device.
Try reflashing the Radio only
Look Here
http://wiki.xda-developers.com/index.php?pagename=Hermes_ExtractedRadioRoms
Post back with results
Regards
S.K
EDIT: Sorry only works on 1.04 bootloader only. Afraid your gonna have to wait for Pof to come up with a 1.06-1.04 workaround
Hi S.K,
Thanks for the info. I have now tried installing the HERM_1.20.31.10_type2_radio_fixed upgrade but unfortunately the radio upgarde crashes also. It all seams to go well, (after using MaUpgradeUt_noID.exe twice) the phone says "Upgrade Radio Stack Please wait" and the progress bar appears on the PC but then after 10 mins I get an ERROR 114: RADIO ROM UPDATE ERROR.
Do you think this might be becuase the last upgarde partly installed bootloader 1.06?
Any other suggestions - I'm desperate to get the hpone on M3100 working again.
Thanks
Read here:
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems
Please post USB monitor capture, otherwise can't help u.
Hi Pof,
Thanks for the offer, I will sort out the usb software on Monday. Are there specific actions that I should try, obvioosly I will usb monior everthing I do but I want to keep it to the point and not waist yr time trailing through huge log files.
Cheers
BTW - I have tried all options of recovery, such as attempting to install the latest radio and trying to install the new rom from an sd card, trying several roms and using imei unlocker - all without any joy.
I think the problem is that I have partially installed radio and bootloader 1.06 so I can't fix the problem.
Thanks again.
@wotthefok:
For me is faster to look at the usb log file, then I exactly know why the upgrade fails, otherwise I have to decode it from your feedback and I can't be really sure. Check the "upgrading problems" page on the wiki, if none of the steps there seems to fix your problem, post USB monitor log please.
Log Files as requested
Hi,
I have captured information using usb monitor and attached the zipped log files for your attention.
The first is called USB_monitor_log_Herm_120Radio_twice. This log details attempting to install the HERM_1.20.31.10_type2_radio_fixed upgrade, and running it twice - just in case.
The USB_monitor_log_runing_Cingular_1.34.502_11_uprgrade_twice.zip details attempting to install the RUU_HER_Cingular_1.34.502.1_1.16.00.00_wwe_cws_ship upgrade, simply using the standard ROMUpgradeUt.exe method. This generates the expected Vendor ID error.
My primary focus is to install the radio upgare or download my bootloader to 1.04. The PDA part of my m3100 does now freeze occasionally but at least functions whereas the phone is completely dead.
Thanks in advance.
Please attach capture in *ANSI TEXT FORMAT*, the .lgs file you zipped is totally unuseful
Edit -> Export and Save as type "ANSI Text files".
Also make sure you export in "COMPLETE" view, see the wiki for more details.
OK, Spot the novice.... I have now created a txt log file that captures activity of me running the 120 Radio upgarde - but only once this time. I still had to zip the file due to it's size. Hope this is OK.
I'll send the other logs within the next couple of hours. Please let me know if the output I have sent so far is acceptable?
Thanks
wotthefok said:
Please let me know if the output I have sent so far is acceptable?
Click to expand...
Click to collapse
No, it's a "basic" capture, you have to export a "complete" capture:
Start USBMonitor.
File -> New session -> USB Monitor -> Select USB device where your phone is connected -> Check "request view" -> Finish
In the upper part there are two tabs: basic and complete. Click on "Complete".
Right, Try again (duh!) OK, I've tried to keep the log files names as self-explanitory as possible... USB_monitor_log_Herm_120Radio_run1.zip is the r20 radio upgrade, 1st run and USB_monitor_log_Herm_120Radio_run2.zip the second run - without disconneting or resetting the device.
USB_monitor_log_runing_Cingular_1.34.502_11_uprgrade_ran_twice.zip is the Cingular upgrade run via the ROMUpgradeUt.exe, again run twice without disconneting the device.
Hope I got it right this time.....Please let me know if there is anything else I can do.
Thanks.
This time you got the captures right
- You're on bootloader 1.06: You don't have 'rtask' command, you won't be able to do any radio upgrade only.
- Your device is not CID unlocked (Security level=FF, unprivileged)
- The bad flash caused the CID area to corrupt (CID: Wait interpreter timeout)
- When flashing a full ROM you get a CID not allow (255) this is because your corrupted CID doesn't match the CID on the ROM.
The radio part is screwed, you could have fixed this if you where in bootloader 1.04 by flashing a full ROM, but as you are in 1.06 you can't because of CID checking. But you're lucky because the OS ROM is intact and you can boot the OS, you should be able to downgrade to bootloader 1.04 from OS and flash a full ROM after, which will hopefully fix your radio.
Just wait until a solution to downgrade bootloader is available (I'm working on it).
Hi,
As I suspected.... Suppose it's not all bad news though - just means that I have to be patient and use my communicator once more. Do you know if the guys at IMEI-CHECK have a downgrade solution? Even if it's a pay for option??
I have already got a IMEI-CHECK sim unlock from where I originally got the M3100 unlocked from Orange to work on o2. That said, I have run either unlocker 2 or 3 with the .unl that I know worked I now get
HTC HERMES v3c unlock
Starting communication.........
Checking device..............ERROR
The device you try to unlock is not supported.
Please contact your supplier site.
Device is rebooting
Press any key to quit this application.
I'm currently chatting to the guys at IMEI-CHECK re this problem.
Anything else I can do to assist you in anyway??
Cheers
wotthefok said:
Do you know if the guys at IMEI-CHECK have a downgrade solution? Even if it's a pay for option??
Click to expand...
Click to collapse
They have it (M3100v3cUnlock.exe), but it will not work on your device because your IMEI is corrupted and their unlocker will not be able to read it and to check/compare with the .unl key file.
Hi,
Just a quick update. The guys at MIGsofT LTD have VERY VERY generously said they'll have a look at the problem for me so my phone will be winging it's way to them today.
Thanks for your assistance and helping me be certain of the problem and to better understand the root cause.
Hope this information will prove useful to others.
Another quick update...
The guys at IMEI-CHECK (MIGsofT LTD) have rectified problems with my handset and managing to reinstall bootloader 1.04 in the process!!
They also turned my phone around in under three days and only charged me the cost of postage! I had previously been a customer of theirs but it was still a very generous and helpful offer and I would certainly pay for the service than have a duff handset - after all £250 + for a paperweight is rather excessive....
If you're experiencing a problem like mine why not get in touch with them and offer them money to have a look at your handset? No Guarantees but it seemed like my last chance, for a while anyway.
Praise to IMEI-CHECK for a brilliant service - they are King of the day !!
here is what I've done and what happened:
my ROM was HTC 1.18.255.3 07/22/06 with bootloader 1.04 then I ran "HERM_Unlock_v2a.exe" on the device but I didn't use "HTC_Hermes_Radio_for_SIMunlock_v1.16.00.69" to save time and i wanted a CID unlock only.
after "SUCCESS!" message from "HERM_Unlock_v2a.exe", I connected my device via USB to PC and started to upgrade to Cingular 1.31.502.1 08/30/06 with aku 2.6 and bootloader 1.06 but when I get the "ID ERROR",without disconnecting the USB, I switched back to ugrading to previous ROM HTC 1.18.255.3 and the Processe started with no problem untill 98%, then suddenly upgading interrupted a message came saying connection error or somting like that!
since then my device is stuck on windows mobile screen and I've tested solutions in the "Hermes_Upgrade Problems" page and tried using the "Hermes SD Card flashing" method, But It seems impossible to flash my phone agian.
Help me PLEASE,HELP
someone help me please!
POF can't you help me please
I think Pof is away until 3rd december, I have the similiar problems with my second hermes, if you have then use mtty to see if you have an corrupted cid using info 2.
Do you have the original rom to go back on if so that will fix your problem.
I've used mtty to send some commands to my device and it answers to some of them but It just stop responding when I type "info 2" or "info 3".
and i tried this in mtty:
"
USB>checkimage
IPL CRC checksum = 0x9FCC6BEB
SPL CRC checksum = 0x3BF03635
CE CRC checksum = 0xC0E1751A
ExtROM CRC checksum = Total Block= 1024
dwBlockIndex= 1024
Address Error1!!!
Get checksum ERROR!!!
0x0
Radio Image CRC checksum =
"
again It stop responding
also tried upgrading, no matter which ROM I try, it just can't connect to device.
and thanx for your relpy.
hi, since there is NO htc service center available around me I have to do something about it myself but my phone is still dead and I'm using a nokia 1101. PLEASE someone help me, pof are you back? can you help me?
I've tried all in this page:
"http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems"
and this one too:
"http://forum.xda-developers.com/showthread.php?t=280733"
and tested qtek 2020 rom but no use.
from what I've found out my device hang up and stop responding when it gets the "INFO 2" or "INFO 3" or "TASK 32" or perhaps any thing involving CID so no upgrading utility is able to connect to it, the only thing is to connect to it using "mtty.exe" which I've tried any command found here, but no use again.
and my SPL is 1.04
can anyone help me?
mht220 said:
I ran "HERM_Unlock_v2a.exe" on the device but I didn't use "HTC_Hermes_Radio_for_SIMunlock_v1.16.00.69" to save time and i wanted a CID unlock only.
Click to expand...
Click to collapse
Wrong, you also need a patched radio to CID unlock. Running only the exe file without the patched radio has no effect on the unit.
mht220 said:
from what I've found out my device hang up and stop responding when it gets the "INFO 2" or "INFO 3" or "TASK 32" or perhaps any thing involving CID so no upgrading utility is able to connect to it, the only thing is to connect to it using "mtty.exe" which I've tried any command found here, but no use again.
and my SPL is 1.04
Click to expand...
Click to collapse
Please attach usb monitor capture when trying to flash a ROM and a radio ROM. Otherwise can't help you.
here is exported files from usb-monitor:
and tanx for your reply
uuh... there must be something really wrong with it, no response to bootloader commands. If no sd card flashing is possible, I would suggest you to send it to service centre too.
pof said:
...I would suggest you to send it to service centre too.
Click to expand...
Click to collapse
It's a difficult option for me, as I should send it to a foreign country to service center,so are you sure there is no way like erasing somewhere using mtty?
pof said:
... no response to bootloader commands...
Click to expand...
Click to collapse
but it respond to some of them in mtty.exe e.g. "erase", "set" and some other.
pof said:
...If no sd card flashing is possible...
Click to expand...
Click to collapse
no it would stuck in "checking..." forever
tanx
HI,
I have same exactly problem on my spv m3100: since sept06 I've tried every kind of Unlock software,upgrade ROM and method found in xda..In mtty bootloader (spl 1.04) respond at every command but not "info 2","info 3" and "task 32".Sd card method works but if you try to upgrade other ROM,in your screen "loading..." and then "checking..." hangs on because the ROM upgrade must to match CID (I suppose..).I'll wait the next ROM Upgrade and ORANGE won't release it until gen07..
warrio said:
I'll wait the next ROM Upgrade and ORANGE won't release it until gen07.
Click to expand...
Click to collapse
it seems your problem is like mine if so, I don't think ANY normal upgrade can solve your prolem 'cause it can't connect to it.
so don't wait and send your device to service center, if you can.
I'm in your same conditions:there's no repair center here so I have to wait Orange who release a upgrade Rom (I hope asap..).
Hello all,
I got a friend of mine who came to me with a device-password locked Hermes, which password he cannot recall (actually his girlfriend...). I said I would be willing to give him a hand to unbrick the device. The problem is that I cannot install any ROM on the device, coz I got an error connection right after the screen goes white and the percentage count should normally start.
So I put the Herm in Bootloader (spl-1.06) and try to flash the OliPro Bootloader. The procedure goes correctly until the step where the upgrade itself should begin, counting from 0%... here, I got:
ERROR [262]: Update error: communication error.
I also tried to flash a ROM directly, but since my Bootloader is 1.06, I didn't find a CID match ROM, so it also failed. The Herm is now not bricked, but it stays at the password input screen, so cannot enter windows properly.
Any help on this?
Thanks,
Ionutz
Interesting since you are trying to go around something HTC probably did not want for people to go around due to security....
agovinoveritas said:
Interesting since you are trying to go around something HTC probably did not want for people to go around due to security....
Click to expand...
Click to collapse
yes, i grih you,and normally i wouldnt even try to do such thing, if it hadnt been for a friend of mine which i know.
besides i would like to learn more stuff about my Herm and this is one thing I havent seen discussed here, although i keep reading xda forums for such info.
just found the solution: i flashed another ROM with same CID since my BL was 1.06, but with BL 1.04. After that, I managed to flash any other ROM and automatically upgrade the SPL to 1.10 or 2.10 Oli accordingly.
If any of you interested and dont get the short explanation, PM me.
cheers,
Io, owner of 2 kicking TyTn's
BL 1.06 didnt allow devices with a different CID to be flashed,
eg: my TyTN had the CID: QTEK001 so i couldnt flash a ROM destined for a device with CID: VODAP001
But BL 1.04 had a bug where you COULD flash any ROM to the device regardless of the CID, the first attempt shows a vendor ID error, then try again and it will flash no problem.
The simplest way I would have got past the device security problem would have been a hard reset.
mrvanx said:
BL 1.06 didnt allow devices with a different CID to be flashed,
eg: my TyTN had the CID: QTEK001 so i couldnt flash a ROM destined for a device with CID: VODAP001
But BL 1.04 had a bug where you COULD flash any ROM to the device regardless of the CID, the first attempt shows a vendor ID error, then try again and it will flash no problem.
The simplest way I would have got past the device security problem would have been a hard reset.
Click to expand...
Click to collapse
I know the details about BL 1.04 vs 1.06, thats why I flashed a BL 1.04 ROM, but with the same CID QTEK_001, or smth.
I have to admit though that I never ever thought about doing a simple hard-reset. I guess it would have been to easy, I jumped to more complicate scenarios. Thanks for the help anyway, i gotta learn that.
Thanks mrvanx, glad I read down the whole thread to the part about a simple hard reset working. I lent my 8525 to a friend, thinking he might be interested in buying it, then he didn't have the money, and after I listed it on ebay today, I charged it up to flash to ATT stock, found it password locked, called my friend a few times just getting his voicemail, so tried flashing, and it said the Hermes wasn't connected to the PC...
I figured there would be a solution here at XDA..and POOF, like magic here it is!
So yes, all I had to do was a hard reset, tested and it works, and it was simple, so thanks again mrvanx, although this thread is very old, glad I found it LOL!
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 ).
Hi,
I have a Tilt, the ROM version is: 1.57.502.2, Radio version: 1.27.12.11. I am trying to downgrade the phone to WM5 or to one of the cooked roms published on this site. I have spent hours reading the WIKI section and many posts. I have tried to install the HARD-SPL however in the begining I had the white screen problem. After using the JUMPSPL, I think that I have managed to install the Hard-SPL (The version that the bootloader shows is: SPL-1.0.Olipof.
I have also unlocked the phone and the CID using tools available on this website. I have no way to check if the unlock works since I do not have another SIM with me right now.
The problem that I am having is that every time I try to install a ROM, I start the upgrade wizard, and get to the point where the phone shows a promt that asks me if I want to approve the execution of a file. I confirm it and then the phone reboots, shows the AT&T logo right away and reloads everything. I do not see the bootloader and after around 60 seconds I get the 260 error on my computer telling me that there is an update error and that the update utility could not access my PDA phone.
I have also tried to get into the bootloader manually, then connect the USB while ActiveSync is open and load an ATT rom (It's an older one with WM5 provided by Cingular) however I get the same results...
Can anyone give me some guidance? Any advice will be greatly appreciated!!!
Thanks,
Joe
P.S. The computer's OS is windows XP, I have turned of the Anti-Virus Scanner (AVG)
FYI this section is for the Hermes/8525, you need to check out the Kaiser/8925/tilt section of this site.
Sorry
Sorry, my mistake. I can't delete my first message however I will change the subject so the moderator will erase it.
Thanks,
Joe