I had 2 choices with my SPV M3100, throw it in the bin or find a ROM image with a Bluetooth stack that actually works (and stays working); so, I downloaded a Dopod and an I-Mate rom image.
Went through the motions with the Dopod image and at the end it said there had been communications errors, it needed to reset to rectify the problem.
After it reset I have a screen which is just a mass of random pixels; curiously with a very small set of digits in the bottom left corner in red. The screen is obviously looking at RAM as I can see the pixels change as the data changes.
After about 10 seconds I get the Windows Mobile flash screen and that's where it stops. I can get the bootloader screen to appear but nothing else documented on here has any effect. I've tried the SD Card image but the bootloader doesn't seem to care/know that it's there.
mtty can see the device and I can get "some" commands to react (info 2 hangs the system; I get HTC and then some garbage text if I enter "set 14 0" but then nothing).
Is there any way to get this <extremely> unstable product back to a usable state or should I just accidentally step on it.
From what you say I see you have done pretty much all the possibilities we know for recovering a bricked unit, and we don't have any shipped update with "ORANG001" CID yet, so the sd-card flash will not work with other NBHs.
Other that it seems that the CID is corrupted (you get no output from "info 2" in mtty!), try using USB Monitor as described in comment #11 in this post and see what it looks like on the exported .txt output file:
http://forum.xda-developers.com/showthread.php?t=278025
Sorry to say that if ROM upgrade utility is not able to talk to the bootloader anymore I guess you should send your phone to HTC's repair centre or wait for a Orange rom update matching your CID and try sd-card flashing with HERMIMG.nbh again to see if you're lucky with the right CID.
If it's insured you could "accidentally" drive yoyr car over it....
I discovered why the bootloader didn't like my SD card; it was formatted FAT and not FAT32. After I corrected that, whatever HERMIMG.nph image I use, the bootloader simply hangs at "checking..."; (I left it overnight to see if it was a sloooooow timing issue).
In all honesty I have been very disappointed with the device, the Bluetooth stack is more of a hindrance than a tool. If I run any peripherals via Bluetooth, and I do, extensively, I have to reset the device at random and unpredictable intervals (reminds me of the original 36xx iPAQs; guess HTC have gone back to their original stack )
I can feel a "faulty unit" scenario coming.
Thanks for the input anyway.
Hi all,
I have just bricked my hermes (twice) and I need some help. It's a SoftBank version, flashed with a Dopod ROM (the earliest version I think), with sim and CID unlocked. This is what happened:
0) Unhid and unlocked extended ROM using POF's cab. Restarted, can read/write to the ROM on the device, and via activesync + explorer. Installed programs there, played with it for a couple days. No problems.
1) Played an mp3 file with japanese ID3 tags, in TCPMP. Characters displayed as weird symbols (expected on enlighs rom), so I tried installing LetsJapanNo5.zip to have the characters display correctly. LetsJapanNo5.zip is mentioned here: http://forum.xda-developers.com/archive/index.php/t-281617.html
2) On restart after installing the cab, device freezes on Windows Mobile splash screen. Followed instructions here to fix, and only hard reset works:
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems#problem2
NOTE: if I just leave the device frozen on WM5 splash screen, LCD powers off after around 2 minutes (my own config before brickign it, IIRC), and device powers off after another several minutes (my own power-saving config again).
NOTE 2: I have a feeling LetsJapanNo5.zip is the one causing problems. And I probably shouldn't have tried installing it on an English rom.
3) After hardreset, I tried to unhide and unlock the extended ROM again, using fit4cat 2.1b. Unhiding worked no problems, but unlocking doesn't work: the unlock option in fit4cat always stays unticked after saving and restarting the device, and attempts to create a new folder in the extended ROM gives write permission errors. info 2 command in bootloader says the device is still CID unlocked:
HTCS00000000jR*¥HTCE
And the bootloader itself says:
HERM200
IPL-1.01
HERM200
SPL-1.04
4) Unable to unlock extended ROm with fit4cat 2.1b, I reverted back to pof's unlocking cab, which installs OK, but on restart, WM5 freezes at its blue splash screen again.
At this stage, I am able to hard reset again, but the device will always freeze again after I install the extended ROM unlocking cab (not using fit4cat because it still doesn't work).
Any suggestions on what I should do, to unlock the extended ROM, as well as clean up the mess made by installing LetsJapanNo5.zip?
And if a full reflash is the best course, any suggestions on what english ROM to use?
cheers.
I have just tried flashing WM6 on to a Friends QTEK 8500, it went wrong Doh!!!.
I had already last Friday put on it the version with non wroking GPRS and this went without issue. I then reflashed my own one with a GRPS working version (went without a problem) and then tried his. I can get it into the boot loader screen but nothing else. I have tried SD card flashing (3 cards) 1x 512MB Card and 2 x 2GB card all formatted as FAT32 with file on the root the phone searches for it but doesnt find it.
Please any advise.
vallancen said:
I have just tried flashing WM6 on to a Friends QTEK 8500, it went wrong Doh!!!.
I had already last Friday put on it the version with non wroking GPRS and this went without issue. I then reflashed my own one with a GRPS working version (went without a problem) and then tried his. I can get it into the boot loader screen but nothing else. I have tried SD card flashing (3 cards) 1x 512MB Card and 2 x 2GB card all formatted as FAT32 with file on the root the phone searches for it but doesnt find it.
Please any advise.
Click to expand...
Click to collapse
First of all, REMEMBER, your phone is NOT bricked until it goes to BOOTLOADER mode.
Have you made SuperCID before flashing? What firmware are you trying to flash via bootloader mode?
Erofich said:
First of all, REMEMBER, your phone is NOT bricked until it goes to BOOTLOADER mode.
Have you made SuperCID before flashing? What firmware are you trying to flash via bootloader mode?
Click to expand...
Click to collapse
When you say booloader mode what does that look like. At the moment if I reboot the phone I get the HTC Mobility windows by Erofich screen.
When you hold down camera and record button and then power on the device I get brifely the white scrren looking for SD card it then goes to the tri-colour screen and does nothing.
I beleive I have CID it as I did the same on this as I did on mine i.e. ran the unlock according to the sticky.
I than put on this
Windows Mobile 6 AKU 0.5.0 (5.2.1711 Build 18165.0.5.0) WWE v5c
Yours i beleive (excellent work by the way)
and it all worked fine bar GPRS I relay needed GPRS so I used
http://forum.xda-developers.com/showthread.php?t=368715
using the clean one which updated fine on my phone but when i tried it on my friends it fell over at about 83% I followed the recovery intructions but this did not work.
When you get into bootloader screen by pressing RECORD and CAMERA buttons, then you MUST flash back to the STOCK ROM first. You can't flash any custom WM6 at this point. Only AFTER you have the stock ROM flashed, you can use SDA_ApplicationUnlock.exe to app unlock the phone, and copy the SoftSPL into the phone. Then run SPL.lnk.
To summarize: The built-in bootloader CANNOT flash WM6 and can ONLY flash a stock ROM. Once you go back to stock, you can then try to flash WM6 again. Anytime a flash fails, you must go back to stock first, then try again.
GnatGoSplat said:
When you get into bootloader screen by pressing RECORD and CAMERA buttons, then you MUST flash back to the STOCK ROM first. You can't flash any custom WM6 at this point. Only AFTER you have the stock ROM flashed, you can use SDA_ApplicationUnlock.exe to app unlock the phone, and copy the SoftSPL into the phone. Then run SPL.lnk.
To summarize: The built-in bootloader CANNOT flash WM6 and can ONLY flash a stock ROM. Once you go back to stock, you can then try to flash WM6 again. Anytime a flash fails, you must go back to stock first, then try again.
Click to expand...
Click to collapse
I am trying RUU_STAR100_3.6.251.0_02.67.30_QtekEUR_Ship I believe this is an original version 5 rom?
GnatGoSplat said:
you can use SDA_ApplicationUnlock.exe to app unlock the phone
Click to expand...
Click to collapse
This method works on Cingular ROM only, not Qtek.
vallancen
Hold CAMERA and RECORD button and press power button. When it goes to Bootloader tricolor mode connect your device to PC and run official Qtek 8500 RUU. Then make a reg (app) unlock:
Download regeditSTG2 which is digitally signed: http://4pda.ru/forum/attach/387522/regeditSTG2.zip
Then install it and change some registry values:
HKEY_LOCAL_MACHINE\Security\Policies\Policies\00001001 = 2
-> change to 1
HKEY_LOCAL_MACHINE\Security\Policies\Policies\00001005 = 16
-> change to 40
HKEY_LOCAL_MACHINE\Security\Policies\Policies\00001017 = 128
-> change to 144
HKEY_LOCAL_MACHINE \Security\Policies\Policies
-> create new key "0000101a": Dword = 1
HKEY_LOCAL_MACHINE \Security\Policies\Policies
-> create new key "0000101b": Dword = 1"
Click to expand...
Click to collapse
copy SoftSPL to the root of your device and run SPL.lnk
Then run WM6 RUU
Erofich said:
This method works on Cingular ROM only, not Qtek.
vallancen
Hold CAMERA and RECORD button and press power button. When it goes to Bootloader tricolor mode connect your device to PC and run official Qtek 8500 RUU. Then make a reg (app) unlock:
copy SoftSPL to the root of your device and run SPL.lnk
Then run WM6 RUU
Click to expand...
Click to collapse
When I plug into PC (XP SP2) and run the Qtek 8500 RUU it just times out and says it cant find device.
vallancen said:
When I plug into PC (XP SP2) and run the Qtek 8500 RUU it just times out and says it cant find device.
Click to expand...
Click to collapse
I have two phones one did work and one did not the one that worked shows version 1.02 on the tri colour screen the one I am having problems with shows 3.06 not sure if this is relevant.
Try removing the battery for about 30-seconds (or just removing the battery cover) and then put it back on. With the phone OFF, hold RECORD and CAMERA and plug in the USB while holding those buttons. It should go to the Bootloader. Run the QTEK RUU immediately after doing that.
If you sit at bootloader very long (more than a minute or so), for some reason it times out and the RUU won't work. It could be that's what's happening.
GnatGoSplat said:
Try removing the battery for about 30-seconds (or just removing the battery cover) and then put it back on. With the phone OFF, hold RECORD and CAMERA and plug in the USB while holding those buttons. It should go to the Bootloader. Run the QTEK RUU immediately after doing that.
If you sit at bootloader very long (more than a minute or so), for some reason it times out and the RUU won't work. It could be that's what's happening.
Click to expand...
Click to collapse
Tried that a couple of times just to make sure I was doing it correctly it goes into the tri colour screen I pressed the reflash option on the PC 1 second later this then sits there for a minute or so and times out "ERROR [260]" the phone did come on and has a USB in the bottom left corner so I presume the connection to the PC is OK.
I have just re-done mine again using the NEO rom (very nice) to make sure I am not going mad and that I did it correctly and this all went without a hitch.
Is there anyway I can get the phone to boot of a SPL on an SD Card I think if I could do this then I could get it back to 5 and start again.
No, it will only boot off the built-in SPL in ROM.
Did you try using the OEM .nbh file, naming it STARIMG.nbh and putting it on the SD card?
GnatGoSplat said:
No, it will only boot off the built-in SPL in ROM.
Did you try using the OEM .nbh file, naming it STARIMG.nbh and putting it on the SD card?
Click to expand...
Click to collapse
Yes tried that made sure formatted FAT32 etc. I know the SD card is ok because if I take my working phone and run the SPL link with the card in my good phone it finds the file and asks me if i want to reflash it. The non working phone with SPL3.06 does not do this.
You are not alone.
The bad news - the person in the post ended up having to exchange the phone.
It could be there's a bug in 3.06 SPL? Seems to be the case because I've flashed bad ROMs many dozens of times on my Cingular 3125 StarTrek and not once did I have any trouble flashing OEM ROM back on it.
Can I write the flash at a lower level with any tools i.e. pdocwrite or seomthing like that?
I don't believe so. Those programs require an Activesync connection (copies files to the phone). You could try the MTTY method, but I don't know if that works on StarTrek. I think it's some kind of terminal access into the bootloader, but what I've said so far is the extent of my knowledge about it.
vallancen said:
I have two phones one did work and one did not the one that worked shows version 1.02 on the tri colour screen the one I am having problems with shows 3.06 not sure if this is relevant.
Click to expand...
Click to collapse
I have a similar problem on a 3125 and the phone reports V4.01. I acquired the phone in this condition, so don't know how that came to be. When I try to update via USB, it tells me I need a newer update tool (to match the 4.01, I assume). What error message are you getting when you try to update via USB?
I have been struggling to flash (again) the great pro V2 rom, but I always used my VMWare based XP windows version on my Vista laptop. Today I could use a genuine XP Laptop and I could make a connection and start the upgrade!
Sounds good? That's what I thought too, until the upgrade stopped at 70% (and I didn't touch anything), because of a connection error. I followed the text on my PC screen and I finally it started flashing again for a few seconds and then my startrek suddenly restarted, but it stops at the first splash screen! I tried to get my device back to bootloader mode (push 2 soft buttons and start), but no bootloader mode, only the 1st splash.
I solved the problem.
Thank you for this thread
I tried flashing a new ROM to my i-mate smartflip and thought I had killed it, but going back to the wm5 OEM as suggested on this thread worked and I still have my phone. Now, am I brave enough to try upgrading it to wm6.1 (or even 6.5) again... Once again, many thanks!
somebody can me give the oem rom because i am same problem too on the secreen 3.06 i cant flashing anytihing rom somebody must me help
Hello,
Yet again my infamous Mda Vario was playing up with the radio stack again, so I decided to flash a different radio to replace the current one, after looking at this thread as I was on bootloader 1.09 I decided to super CID it as this was the first step.
And revenge of the pda happened again, I ran the automatic script, it got to flashing HardSPL via SSPL when I noticed the PDA went into a bootloader coloured screen yet with no backlight and no text on it. Nothing will pick up the fact it is plugged into the machine like it is not turned on
The phone will not charge either (orange light not present) yet the red led is present when I remove the battery, I do have a spare lying round with an hours charge in it giving me a total play time of 6 hours.
I had previously flashed hard SPL before so when I went into the bootloader it always came up with
IPL-SPL by (cant remember the name)
SPL: 1.09 by des
Any ideas? I don't really want to use JTAG pins as I'm not confident with cracking the thing open and making the adapter to connect it to.
Use sd card method to flash a new rom onto your Hermes... If you then get to today screen, flash Hard SPL V7, you won't need to supercid it then as Hard SPL V7 bypasses the need...
Cheers...
Nope dead, I turned on the device and it did nothing except go into the tri coloured screen.
This is without text though and without any light so its barely visible, I cant reset it into bootloader (even though it is in it :S) as the ok button is bust from, ironically, overuse.
Any ideas?
Hi all,
I have a big problem with my HD2. When I power on the phone, the white screen with green HTC appears, that's all! No version of Radio or OS appear in bottom of the screen.
I don't remember how it's arrive, since, I have flashed a lots of OS and Radio.
I have tried with HSPL2.08 HSPL1.42 (with HSPL2 and 3) Official HTC Rom (1.66) Radio 2.10 2.11 2.14 2.15 Original Orange Rom (HD2 branded Orange FR) with different USB cable and different computers, with and within SIM or SD card....
All flash complete with successful, I try with MAGLDR and a WP7 rom, after the flash, the phone doesn't restart automatically. If I remove battery, or push reset bouton, the phone restart but a red text "FAILED" appears.
If I try to flash by SD card, the flash stops at the Radio flash (if radio is in the NBH) with an triangle with exclamation point (like that but for WinMo http://bcorse.files.wordpress.com/2010/07/nexus21.jpg I have not find a picture of WinMo).
Sorry for my very bad english, I hope you understand what I write !!
Thanks for your help, have a nice day
edit >> arf I have try to flash the latest Orange Rom (3.14) and now my HSPL is in 3.XX (I flash by USB cable)...
My english is too bad to have an answer or nobody knows what is the problem ?!
There are so many similar threads with almost identical questions...
And, apparently, as you write yourself, you tried everything.
All what one can say is that you definitely have a bootloader issue - what exactly does it look like when you start into the multicolor screen? All readable?
Plus, SPL is not overwritten via USB, that happens only via SD card, or, as you wrote, with HSPL2/3.exe.
Therefore, it is really strange that you´ve got SPL 3.03 on your device if you flashed via USB. Maybe it happened before, flashing another ROM via SD card?
Flashing via SD card can be a headache if you use cards bigger than 8GB, I usually recommend the 2GB card which was originally shipped with the device. Please try it with a freshly formatted (FAT32) card.
Starting from scratch, I would check the SD card thingy, put an older stock ROM which was made for your device on it (in order to get SPL below 3.03).
Also, it can be helpful to indeed take the battery out for a minute or two, and then re-insert it before pushing the buttons in order to get into the bootloader and then to flash the stock ROM.
Hi tictac0566, and thanks for the answer. That you say, I have tried everything it's possible.
I had contact the Orange France SAV, they returned me a "reconditionned" mobile!