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.
Which Dopod device is based on HTC TyTN/Hermes?
Edit: OK these ones - Dopod CHT 9000 / Dopod 838 Pro/
Stupid question but did you try to flash the ROM for a different device?
I used the Hermes ROM images.
Even if I had used the wrong image, the issue is how do I get it to build only utilising the bootloader?
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 timing issue).
"..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 timing issue)..."
that is so because you trying to flash DOPOD ROM to Orange branded device. You need matching Orange branded ROM to flash with SD card. Your device has CID that is defferent to the CID the DOPOD is made for.
As far as I am concerned, Orange has not made available ROM image for your device as of yet.
ok so i just recieved my Cingular 8525 today after having my 8125 stolen.
i am trying to successfully install iiwpo but i have encountered a lot of problems so far:
1. i am trying to CID unlock so i can write IIWPO to the extended ROM. on the startup screen i cannot see anywhere that states if i have a 1.04 or 1.06 bootloader so i haven't even attempted to unlock it for fear of damaging something.
2. i can't find a working version of iiwpo. the file that i have downloaded seems to be corrupt and it won't unpack...
i don't want to lose this phone like i did the 8125- please help!!!
p.s. oh and i am also looking for the name of that program that is packaged in with the molski ROM for the universal that places the little red dot in the 'close program' X and asks if you REALLY want to close the program or not. can anyone provide a name for this particular program??
thanks in advance for any help!!!
The hermes doesn't display ipl/spl info at startup like the Wizard did. You have to go into bootloader mode to see it. However, it's already known that your 8525 will be running the 1.34 Cingular ROM which has BL 1.06. To unlock, you have to flash to the v1.30 ROM here which has BL 1.04. Then you can unlock/SuperCID and go back up to whatever ROM you like. SuperCID will give you R/W rights on the ExtRom once it's unhidden using the tools here.
Flashing is much more dangerous on the hermes than it was on the wizard due to the timeframes involved (flash takes 20-30 minutes). Be absolutely sure you have a solid USB connection. Read up on flashing best practices here too before you start. You've got an hour or so of flashing time in front of you:
- downgrade to v1.30
- unlock & superCID
- upgrade to v1.34 again
Hi,
I had successfully used ShellTool to load Crossbow Reloaded v1.5 on my Xda Mini S (G4 CID-Locked)
But then I became inquisitive and I tried loading the WM6 Business Edition.
http://forum.xda-developers.com/showthread.php?t=302934
The process interrupted abruptly as the activesync connection broke (Don't know why that happened.) However I restart the device and now it is stuck on the initial blue O2 screen displaying IPL, SPL, GSM and OS information.
Now it is mentioned here
http://forum.xda-developers.com/showthread.php?t=293480
That if the device does not boot I should restart it in the bootloader (which I did), connect the usb and run RUU. But the download (Wizard_Love_2.26.10.2_WWE_Novii+CF2.rar) contains newromupdateutility_wizard_noid.exe and on running that I get the CONNECTION ERROR. I think this is happening because in bootloader, actyivesync cannot connect.
Sorry I am a novice in this... please help.
Regards.
Activesync will not connect from the bootloader. This is not a problem. Activesync is not needed to flash your phone. You just need the USB connection in the bootloader. As long as you see the letters USB in the corner you can flash.
Did you use the shelltool in the attempt to load the other WM6 rom? And if ActiveSync is required to use the shelltool then you may have to flash an official carrier rom in your current state (one that matches your CID so it will flash) and once your device boots again you should be able to use the shelltool and load the other rom that you want.
Personally this sounds like a big hassle to me and if it were me I would just pay the 25 bucks or whatever it is to get the unlocking software from the unlocker website and CID unlock my device so I could pretty much flash at will (G4 safe roms of course)
Downloaded the original rom from my-xda.com and it worked. Got the original system back.
Just updated to faria's wm6 using the same shelltool and all works fine. Looking at voip now.
thanks for the suggestion.
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
Hi all,
I have a Hermes here (MDA version from Tmobile UK)
We know the customer has quite literally "fingered" the unit in all ways possible
At the time, he "claimed" to be a windows mobile developer who invented WM5 - dare I say more?
OK so the Hermes is doing the following:
Stuck on Bootloader screen
Herm300
IPL-1.04
Herm300
SPL-2.03
When I do a hard reset via the two soft keys and reset button, the phone boots up with the t-mobile splash with Test Only Not For Sale
Carries on booting, goes through the whole setting up procedure
Then on the reboot, it goes back to bootloader
Now Once I managed to reset and it simply booted in with me using the phone perfectly
The second time I reset, the phone went into a white screen but you could tell it was booting up.
I'm now back in bootloader which refuses to go any further.
Tried running Hard-SPL on it but it can't seem to detect the unit despite it going from Serial to USB
Appreciate any help
On PC (if u use XP), untick "Allow USB Connections" in activesync settings. Put Hermes into bootloader and connect to pc.
Install Hard SPL. Hermes WILL be detected by the Installation program.
Then try installing a new OS, now you should have Hard SPL I'd use the sd card method.
1. Format 2Gb or less sd card FAT32.
2. Copy .nbh file of the rom you want to it and rename to hermimg.nbh.
3 Insert into Hermes and reset to bootloader, follow the instructions....
Should install a new OS and get rid of that "testing only" message.
Cheers...
I follow to your guy , so my device flash :
IPL - Ok
Bootloader - ok
GSM -
It hand on there.
Can you held me now.
My device 's Softbank X01HT, I reflash original ROM (Japanese language)