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
Related
Have tried all sorts and still cannot boot after using the wrong sim unlock.
Have tried doing hard reset and then soft reset instead of spacebar, it still did not boot.
MTTY command set 14 0 and soft reset made no difference.
Tried the SD card method but it didn't work as Orange have not relesed an ugrade yet (Jan 2007 I've heard) CID is ORANG001.
Trying to reflash with any other ROM I either get connetion error or non compatability error. Using USB Monitor shows no results although MTTY commands do show up.
Is there any way I can reflash with original ROM? I have access to a locked SPV M3100, could this help in any way?
When phone tries to boot it shows:
M05
S04
B05
No GSM
D 1.23
I know the radio part is screwed and have tried to flash radio only, nothing happened and nothing showed in USB Monitor.
Even tried method used by Kimbay http://forum.xda-developers.com/showthread.php?t=280228 this also had no effect.
Hoping someone somewhere can help, I know quite a few people are in the same situation and if a solution can be found will help others if I can.
Thanks to pof who has already given me some advice, sadly none of it worked.
I have a similar problem as you, and i have tried everything, my last test will be when I get an original rom for my device that matches my CID.
There is no date for my original rom to be delivered so I have to wait.
rachelm700 said:
Trying to reflash with any other ROM I either get connetion error or non compatability error. Using USB Monitor shows no results although MTTY commands do show up.
Is there any way I can reflash with original ROM? I have access to a locked SPV M3100, could this help in any way?
...
I know the radio part is screwed and have tried to flash radio only, nothing happened and nothing showed in USB Monitor.
Click to expand...
Click to collapse
Had the same problems as you, This is how I repaired it:
http://forum.xda-developers.com/showthread.php?t=280425
Houz74 - Tried your method, never got past the white screen. Will keep trying.
I tried this, but as I don't have an original rom and being on bootloader 1.06.
Its not a big problem as I have 2 tytn, one to play and one for proper use.
rachelm700 said:
Houz74 - Tried your method, never got past the white screen. Will keep trying.
Click to expand...
Click to collapse
Didn't work for me in one time too, had to reset both my phone and my pc for it.
After which step do you get the white screen ?
You could try this ROM:
ftp://xda:[email protected]/Himalaya/ROM166/RUU166223WWE.exe
Use it til just after the erasing part of the upgrade.
You have bootloader 1.04 ? Otherwise this method doesn't work
Houz74 said:
Didn't work for me in one time too, had to reset both my phone and my pc for it.
After which step do you get the white screen ?
You could try this ROM:
ftp://xda:[email protected]/Himalaya/ROM166/RUU166223WWE.exe
Use it til just after the erasing part of the upgrade.
You have bootloader 1.04 ? Otherwise this method doesn't work
Click to expand...
Click to collapse
Bootloader version is 1.04
Tried above method, results below:
1. Welcome to the Pocket PC software upgrade utility.
2. Checking the information on your pocket PC... Please wait...
SCREEN GOES WHITE AT THIS STAGE
3. update screen:
CE image version 1.66.00
Extended image version 1.66.223
Radio image version 1.10.00
4. Checking
5. The current sofware is being erased from your Pocket PC.
Even if left for over an hour this stays at 0%
I got the same results with RUU120_172125_Qtek_WWE_R11400_Shipping but obviously the update screen shows different CE Image Version etc.
Sorry for the lengthy reply but wanted to show as much info as possible. Have tried both ROMs many times and hangs at the same stage every time.
rachelm700 said:
I got the same results with RUU120_172125_Qtek_WWE_R11400_Shipping but obviously the update screen shows different CE Image Version etc.
Sorry for the lengthy reply but wanted to show as much info as possible. Have tried both ROMs many times and hangs at the same stage every time.
Click to expand...
Click to collapse
Can you do a full USB monitor caputre of the process when trying to put the Himalaya ROM? I explained how to do it here:
http://forum.xda-developers.com/showpost.php?p=1036494&postcount=4
If we don't know 'what goes on through the USB cable' we will not be able to understand why the problem is fixed using this method, and what prevents the erase proces to end in your case.
There are two erase commands in Hermes bootloader 'erase' and 'rerase' (for radio) which take an address and a length as arguments. If you look at what the upgrade tries to do, you can do it manually after from the bootloader.
Hi pof
This is what was captured with USB Monitor, the first is RUU166223WWE
the second is from RUU120_172125_Qtek_WWE_R11400_Shipping
In both cases nothing seemed to show up after the screen which says: The current software is being erased from your Pocket PC - it just hangs at 0% no matter how long it is left.
Not sure which Himalaya ROM you meant so have posted the results from these two for now. Please advise which Himalaya ROM should be run.
rachelm700 said:
Not sure which Himalaya ROM you meant so have posted the results from these two for now. Please advise which Himalaya ROM should be run.
Click to expand...
Click to collapse
The Himalaya ROMs you used are OK, both files show the same output. These are the commands sent to bootloader and my explanation of the process:
Code:
USB> USBPortTest
Command error !!!
This should be Himalay specific, not working on the Hermes bootloader, so it says "command error".
Code:
USB> info 0
USB> info 1
On the Himalaya, "info 0" returns platfrom name (16 bytes) and "info 1" returns bootloader version (16 bytes). On the Hermes these commands return nothing (no output).
Code:
USB> password 0000000000000000
HTCSPass1..CM??HTCE
Himalaya RUU sends "password 0000000000000000", on the hermes this password is dynamic and the RUU should issue "info 3" command first to calculate the password, but as "info 3" has not been issued yet the Hermes bootloader returns Pass1 encapsulated in HTCS/HTCE block, which is the output when the password is valid!!!
Code:
USB> set 1 0
USB> set 6 ffff
USB> set 2 1
USB> set 5 F800
These commands are the same in the Himalaya and in the Hermes:
- "set 1 0" sets the operation mode to user which makes the other commands return more friendly values
- "set 6 ffff" changes the screen color to FFFF
- "set 2 1" change back color on
- "set 5 f800" changes background color to F800
Code:
USB> info 2
This should return the CID on the Hermes, but it does not ... I don't know what it does on Himalaya. As I see no output from your Hermes here, I guess the proces has already stopped, so the following commands sent by the RUU will not work.
Code:
USB> set 1e 1
This unlocks the read/write flag, should be always done before flashing. (when the flash process ends, it should be done the oposite: "set 1e 0").
Code:
USB> rbmc Temp.txt 70010000 28
This reads 28 bytes of memory starting from addres 0x70010000 and saves the read data to Temp.txt file.
I don't know what there is on this memory address (anyone?), but I guess it's himalaya's specific.
The "juicy" commands will come after this one, but your hermes doesn't seem to pass from here. Luckily I found on buzzdev.net the Himalaya upgrading process, which shows exactly the same process as I can see in your attached files, so the following that should come here if your Hermes was still alive is this:
Code:
USB> erase a0040000 c80000
USB> erase a0cc0000 c80000
USB> erase a1940000 640000
USB> set 1e 1
USB> wdata a0040000 20000
The last 'wdata' command will not work on the hermes (it uses 'wdatah' instead) so nothing is written on the rom, just erased.
CONCLUSION:
If you feel brave, and always at your own risk, what you should do to fix your bricked hermes with screwed radio is this:
1) Put your Hermes in bootloader mode
2) Disable USB connections in ActiveSync
3) Open mtty.exe and select USB port, then connect.
4) Hit enter twice, you will see the "USB>" prompt.
5) Type the following commands (do not copy paste!!!):
Code:
set 1e 1
erase a0040000 c80000
erase a0cc0000 c80000
erase a1940000 640000
set 1e 0
6) Reset your phone and put it back in bootloader mode
7) Flash the Hermes rom of your choice (if your bootloader is 1.06 it MUST match your CID, if it's 1.04 it isn't important)
Good luck and let us know how it goes!
I think you will need to authenticate to the bootloader before issuing the "erase" commands, otherwise the bootloader won't let you erase.
When you are on "step 5" of the process I described before, if you get an error when issuing the first "erase" command try these commands instead:
First try to use the "Himalaya" method, as it worked for some people:
- in step 5, use these commands:
Code:
password 0000000000000000
set 1e 1
erase a0040000 c80000
erase a0cc0000 c80000
erase a1940000 640000
set 1e 0
If it doesn't let you erase, then you'll have to authenticate to bootloader using the dynamic password.
The attached file will try to authenticate to the bootloader for you, so you don't need to go through all the process described in this PDF, which is a bit tedious. It should be run before you actually open mtty on step 3, when it authenticates sucessfully it should show the message "Entered advanced bootloader", when you see it you can open mtty and follow the next steps. Probably it doesn't work at first try and you have to run TryBootloader.exe several times before it acctually successfully authenticates to the bootloader, but it's better than the process in the pdf
Once you're actually authenticated correctly with TryBootloader.exe, just run the commands in mtty as in step 5, do not use the "password" command again.
Let me know if something is unclear or you need more help.
Yipee, It's back to life, please see new post
http://forum.xda-developers.com/showthread.php?t=280733
1) Put your Hermes in bootloader mode
2) Disable USB connections in ActiveSync
3) Open mtty.exe and select USB port, then connect.
4) Hit enter twice, you will see the "USB>" prompt.
5) Type the following commands (do not copy paste!!!):
Code:
set 1e 1
erase a0040000 c80000
erase a0cc0000 c80000
erase a1940000 640000
set 1e 0
6) Reset your phone and put it back in bootloader mode
7) Flash the Hermes rom of your choice (if your bootloader is 1.06 it MUST match your CID, if it's 1.04 it isn't important)
Dear Prof:
I'm totaly stuck trying to flash it with Qtek 2020 with 0%. Also, noID did not work as it show no radio or other CE version numbers and end with sucessfully completed operation. I would appreciate if you can advise me.
Hi, i want use the mtty but, when i select the usb, the promp file go to the cmd>
dont appear the usb>
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.
I have searched the forums and have found 1 post saying that the T-MOB005 cannot be CID unlocked ? is this still the case as the post was dated Nov2006 ?
I have tried the POF method twice (i.e. Herm CID Unlock v2a). and although it had updated the Radio to 1.16 when i enter the "info 2" command with mtty it brings back
HTCST-MOB005¼ôàŠHTCEUSB>
which means that it is not super cid unlocked.
SPL=1.04
IPL=1.01
I have also checked that the radio has been flashed correctly and it show in device id that the Radio Version is 1.16 so it certainly appears that all has worked apart from the SuperCid
When i put in a sim from another network i get a screen that " I have tried 10 times and to wait till timeout" both buttons are greyed out so i cannot input any numbers.
My T-Mobile sim still works fine.
mtty output
USB>
USB>info 2
HTCST-MOB005¼ôàŠHTCEUSB>
USB>
USB>rtask b
0
0
atvl
0
[email protected]?40
@SIMLOCK= 01
0
atel
0
USB>
USB>rtask b
0
0
[email protected]=0,1,22051978
4
[email protected]=0,2,22051978
4
[email protected]=0,4,22051978
4
[email protected]=0,8,22051978
4
[email protected]=0,16,22051978
4
[email protected]=0,32,22051978
4
Any info appreciated.
Thanks
Are you sure you didn't flash extracted radio 1.16 before and that's why it's showing 1.16 on radio version now?
If your SPL is 1.04 it should work. Try flashing the patched radio again, and capture the flashing process with USB monitor if nothing changes after flashing the radio. This should help to troubleshoot why it is not working on your device.
I will start from scratch again this evening and see if it still gives the same results. I had already flashed my other vario II and this worked with no problems.
Will post my results this evening.
Thanks for your help so far.
I have absolutely no idea how I got the 1.16 radio roms mixed up but when i re-downloaded the unlocker again and used this one, everything unlocked fine first time. info 2 shows supercid.
Lesson learnt i think, dont do anything when you have been working for the last 14 hours as you tend to miss the most obvious things.
Thanks for your help.
FRIENDS help , I think I have the brick of all bricks I followed the wiki step by step including creating and copying the nbh file. I got as far as 70% of image loading and it hung and dropped into recovery mode but could not get passed there. I have tried all forms of reset and do not get passed bootloader screen with Herm100 IPL-1.04 and SPL-2.03. This was a imate jasjam running windows mobile 5.0 to which I tried flashing to the new HTC WWE 6.0 upgrade. I have tried running usb monitor from the link but it just gives me a series of paramters in a notice window and then dops off. I have tried another verison but it is not capturing anything.
I have tried mtty and cant even get the usb> prompt after disabling the usb connect in activesync. Please help as this was a works new unit last month and I have some major explaining to do if I cant get it sorted!
Model: Imate Jasjam
ROM Before Flash: TMO_UK_3.60.110.1_6275_1.50.00.00_108_Test
Radio Before Flash: 1.50
Bootloader Before Flash: Not sure
Flash failed at: 70%
Flashing ROM: Image Vers 3.54.255.3
CID Corrupt: Assume Yes
Radio Corrupt: Assume Yes
No GSM Error: Not got that far
Stuck In Bootloader: Yes
Stuck On Windows Mobile Splash: Not got that far
Can boot into OS: No
Tried mtty command set 14 0: Yes but not getting usb>
Tried wiki problem number 4: Yes dont get passed point 3 as as soon as powers up goes to tri colour screen. Switched from serial to usb with connect of usb cable
mtty info 2 output: cannot run
Current Device Status: unusable
Tried re running install and get error 260 and 294(AFTER 1%)and - Not getting a response from PDA!
I TRIED PB + KITL method .BUT IT FAILED AS I COULD NOT ACTIVATE KITL MODE.I BELIEVE ITS NOT ACTIVATED IN MY PDA.
I SPOKE TO TO IMATE INDIA PEOPLE , THEY REPLIED THAT THE MOTHERBOARD IS TO BE CHANGED , WHICH COSTS 60% OF THE COST OF THE PDA.
CAN ANYONE HELP WITH A BOOTLOADER V2.03 ?
WAKE UP DEVELOPERS .DO SOMETHING.
tHANKS IN ADVANCE.
the output is for :
HTC_Hermes_SIM_CID_Unlock_v3a
And
RUU_Hermes_TMO_UK_3.60.110.1_6275_1.50.00.00_108_Test repectively.
So no HardSPL before you flashed?
You should still be able to get a USB monitor from it.. regardless if the thing has been thrown off the empire state building.
What USB monitor program are you using?
MTTY Set 14 0 I beleive is for a corrupt radio stack, all that does is restore your radio stack to factory form, sounds to me like you have a hybrid brick, which is corrupet or invalid CID coupled along with a corrupt radio stack..
Madcap180 said:
MTTY Set 14 0 I beleive is for a corrupt radio stack, all that does is restore your radio stack to factory form, sounds to me like you have a hybrid brick, which is corrupet or invalid CID coupled along with a corrupt radio stack..
Click to expand...
Click to collapse
set 14 0 tells the device to skip to OS boot rather than go to bootloader (opposite of set 14 1)
what we need to ascertain is exactly what bootloader version this guy is running, and then to find out what CID he has from the bootloader.
until we get these both, I think we'll have to "assume" it's ****ed.
oh and in future, don't PM me twice, it pisses me off. so consider yourself lucky I've bothered to comment.
Cmd>
Cmd>info 2
HTCSCDL__001ÄÊìHTCE
Cmd>info 7
HTC Integrated Re-Flash Utility, Common Base Version : 1.51d
Device Name: HERM100, Bootloader Version : 2.03
Built at: Jun 16 2007 01:57:22
Copyright (c) 1998-2006 High Tech Computer Corporation
CPU ID=0x41129200
Main CPLD version=0x5
Upper CPLD version=0x4
Main Board version=0x6
Cmd>info 6
HTCST ÚÈÒHTCE
Cmd>info 5
Cmd>info 4
HTCSCDL__001ÄÊìHTCE
Cmd>info 3
HTCSH
Cmd>set 14 1
Write Nand Success
HTCST ÚÈÒHTCE
Cmd>rtask 32
Command error !!!
Cmd>rtask 28
Command error !!!
Cmd>rtask 8
Command error !!!
lastly it's not KITL enable.
Hi gents,
I finally managed to put my hermes in unusable state and would appreciate any suggestions to get it working again.
Here is the situation: My phone is Hermes 200 with SuperCID and bootloader IPL-1.04, SPL-2.10.Olipro. Currently it sits stuck in tri-color bootloader mode and it doesn't matter what I do. Within last 24 hours I tried to change the boot flags "set 14 0" and "set 16 0" respectively at least 50 times without success. I flashed about 6 different versions of roms including original HTC distributions for WM5. Nothing happens.
As far as history is concerned, I flashed many roms since Black 1.0 onto my TyTN without any problems. two weeks ago, I tried one of Pay's roms trying to get something faster then Schap's 4.22 I was using. Got stuck in BL but could recover using the "set 14 0" and "set 16 0" commands. since then, I had couple of occasions where phone got stuck in BL after rebooting it. Removing and reinserting battery always helped. Last thursday, I donwgraded my radio from 1.54 to 1.43. You all know the reasons. No problems. Since then, phone worked like a charm and even power consumption was good. Yesterday, my battery ran out and in order to preserve it, I turned of the phone. Stuck in BL since then.I believe that the problem is that my SPL got somehow corrupted.
So my first question is, how do I reflash HardSPL from WITHIN BL with no access to OS? I can still talk to my phone BL through mtty and get all info etc.
Again, any help would be appreciated.
Roman
Please remember I'm new at this, but have you tried the sd card method of flashing? Hard Spl ver 7 has an .nbh file like a rom upgrade so this may be your best bet. Cheers.
Can't flash with SD card
ultramag69 said:
Please remember I'm new at this, but have you tried the sd card method of flashing? Hard Spl ver 7 has an .nbh file like a rom upgrade so this may be your best bet. Cheers.
Click to expand...
Click to collapse
Didn't try it first as my SD card contains programs/data which I would like to backup first before formatting it. Unfortunately, my laptop with XP refuses to recognize it as a formatted drive for some reason after insertion. I have 2GB KingMax with adapter.
From SPL 2.10 Olipro to dead phone. It's getting worse every minute.
Well, guess what. My phone just decided today, around noon to boot into OS! even though I tried to reboot it several times during morning without success. So I left it alone, without resetting it until I got home. Spent plenty of time reading wiki and upgrading posts etc. While doing that, I backed up my SD card via ActiveSync file access and erased everything on the card. I also copied HardSPL v7 RUU_signed.nbh on it and renamed it to hermimg.nbh.
Going through all the info, I decided to try DOWNGRADE SPL 2.10 to 1.10, following mrvanx's guide and links, as it is still HardSPL. Well, the update process went without a hitch. It loaded SSPL on TyTN and flashed it with 1.10. No errors. It reset the phone and stopped in BL. Again. This time, it says 1.10 Olipro as it should. Going ty mtty after USB connection, and running info commands, reveals some differences as info 2 NO LONGER reports SuperCID as it did before. It just prints the HTCS marker. The phone is still SuperCID I believe as task 32 reports level=0.
Remembering that removing and reinserting battery sometimes helped ( I forgot to try the set 14 0 and set 16 0 ) I removed the battery. About ten minutes later and more wiki reading, I realized I should try the set flag commands. So I reinserted the battery, reboot and NOTHING. And I mean nothing! The phone is as dead as it could be. NO LIGHTS , NO DISPLAY, NO RESPONSE WHATSOEVER. Did I just foo bared my IPL ?
Sorry to hear that, best bet would be to pm Olipro and see what he has to say. He is the Guru when it comes to SPL. He may have an idea but if you cant get into bootloader then phone is probably foo bared, Still, I'd see what he has to say, might pull a miracle out of his hat...
Resolved. My TyTN is alive again
See post http://forum.xda-developers.com/showthread.php?p=1867765#post1867765 for the end of the story.
open mtty and put this command.
Put hermes in bootloader and disable activsync,
open mtty.exe select usb and put this command:
set 32 (enter)
set 14 0 (enter)
set 16 0 (enter)
task 28 (enter)
task 8 (enter) After this command hermes will automicaly boot os if not then your os is demaged just flash full rom.
what you see when write this command in mtty :
checkimage (with this command you can see status of full rom)
gsmhackerns said:
Put hermes in bootloader and disable activsync,
open mtty.exe select usb and put this command:
set 32 (enter)
set 14 0 (enter)
set 16 0 (enter)
task 28 (enter)
task 8 (enter) After this command hermes will automicaly boot os if not then your os is demaged just flash full rom.
what you see when write this command in mtty :
checkimage (with this command you can see status of full rom)
Click to expand...
Click to collapse
I did the resetting of flags multiple times. No joy. I tried to do the NAND formatting as you suggested, nothing. Reflashing with shipped rom, nothing.
I ran checkimage so many times over last week, I lost count.
Stil BL only...
rronge said:
I did the resetting of flags multiple times. No joy. I tried to do the NAND formatting as you suggested, nothing. Reflashing with shipped rom, nothing.
I ran checkimage so many times over last week, I lost count.
Stil BL only...
Click to expand...
Click to collapse
my God !!! that's the worst brick i ever heard, Hybrid brick ???
From the 1st post, I saw all of the effort you use and that's the way should be, but no result.
I think you should re-consider to buy new gadget then. This is for your health too
ermenzegna said:
my God !!! that's the worst brick i ever heard, Hybrid brick ???
From the 1st post, I saw all of the effort you use and that's the way should be, but no result.
I think you should re-consider to buy new gadget then. This is for your health too
Click to expand...
Click to collapse
I still think it's fixable. When I turn the power button on, or plugin the charger, there is significant delay ( about 1.5 - 2 seconds ) before the BL starts. I think that the IPL is trying to boot the OS image but something goes wrong and it aborts and starts SPL. If the NAND is corrupted, it could be re-verified by a proper walkthrough and marking of bad blocks. I have done this at work while writing device driver for another Samsung NAND. I still have the code somewhere. Unfortunately, I don't know how to make it into signed nbs so it can be loaded and executed by SPL as a diagnostic utility.
rronge said:
I did the resetting of flags multiple times. No joy. I tried to do the NAND formatting as you suggested, nothing. Reflashing with shipped rom, nothing.
I ran checkimage so many times over last week, I lost count.
Stil BL only...
Click to expand...
Click to collapse
Many people try to unbrick spl 2.03 stack in boot no gsm and kitl mode and can not boot os just led light when power up...can go in bootloader bat this is all!!!.
I speak with imei-check abaout this and they told me that can repair this and it will cost 60pounds+ Here is message from imei-check.co.uk to me Hello,
You must send the device to us. The cost is 60 GBP + 15 gbp postage fee to return it back to you (or 7 GBP if we send it back to a UK address). In the day we receive it, we fix it, and next working day we send it back to you.
If you want to go ahead, please send the device + battery
(i think just need to open temporaly cid unlock in spl and this will help i mean from dos prompt,blank screen+ then flash??)and i must sent from Europe Union country .I live in Serbia and think that solution to unbrick hermes existed bat not want to tell many people......?? I will work in this now and i hope that solution will be for free when fix this.. I unbrick many hermes.artemis...etc..in Serbia bat this solution to unbrick hermes with spl 2.03 temporaly can not not have time to try?. I now will try many solution and will post here when fix this,you can trust me??....
If somebody else create solution before me please sent me message to know??
Do not post any solution from this site i try all and not work(SD card will not work when cid locked,hard spl-not work always 100% then message image corrupted,No kitl.....so please only original solution not from xda-developers..etc.
thanks for all.