Related
I have only had my XdaII for a month, but last week it locked up and upon a soft reset it took 5 minutes to get past the O2 screen, then there was no responce to any screen taps, i decided to do a full reset, once rebooted still no response to screen taps, so i couldnt calibrate the screen or go any further, i connected the xda to activesync this still worked fine and was responding normally. I then decided to reload the rom from myxda.com, biggest mistake as it crashed halfway through now it just says Serial v1.06 or USB v1.06 if its in the cradle, now before i get bashed for just asking this question the same as a lot of other people have, i have spent the last 4 days go over this site trying anything that relates to getting any image back onto my xda, nothing has worked i have tried any nbf or nb1 image i can find on here with orginal or modified himaupgradeut.exe same response every time error 100: incorrect device type, i have tried any image i get can get onto an SD card, they either dont boot or wont allow upload, so my question is i have seen several people on here ask about bring v1.06 back from the dead but so far noone has had any instructions on how to this when a normal boot isnt possible.
I don't know if this is any help,but I had something similar.
I concluded that the rom on xda2 was newer than one being upgraded? with,so it says it won't work.I sent mine back to o2,but think that rom 172 or something, might be accepted.People say that you leave it 30 mins before it starts to upgrade.
There is a problem with bootloader v1.06 in that it will not allow 'downgrades'. It seems to have appeared on devices around the same time that ROM versions 1.72 appeared. I have read that it will allow installation of version 1.66 but nothing less than that (and that may apply only to T-Mobile). However, you should be able to install a version 1.72 ROM without to much problem.
My help
You can make the unit work again by downloading the rom version:
1. Ensure that the main battery has enough charge to make the unit in bootloading mode.
2. Execute the bootloading mode and connect the unit to the docking station(cradle), you will see the "Serial" in the upper portion of the screen will switch to "USB" this is an indication that there's a connection established between the pocket pc and your pc.
3. Then download the latest Rom version(1.72 is a better choice).
Thanks dcs and Juni
The 1.72 rom did get it going again .... but i still have no response on the screen so im guessing ill have to return it.
Does anyone know where i can get the 1.66WWE rom from as im assuming returning it with 1.72 rom on it may be frowned upon, and a voided warrany.
Thanks agian guys for your help
Does anyone know where i can get the 1.66WWE rom from as im assuming returning it with 1.72 rom on it may be frowned upon, and a voided warrany.[/quote]
talk to this person in here: :lol:
http://forum.xda-developers.com/viewtopic.php?t=12044
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.
I managed to upgrade my phone to aku 3.3 using pof's method(bootloader 1.01 MFG) . Then, out of no where, I tried to use MTTY to upgrade my radio rom
It started as usual with the status bar moving. Suddenly some error messages came up.
Now, the phone is dead completely. I can''t even enter bootloader mode.
Is there a possible way that I can still save it??
Help!!!!
Have I bricked my device? Help plz
I managed to upgrade my phone to aku 3.3 using pof's method(bootloader 1.01 MFG) . Then, out of no where, I tried to use MTTY to upgrade my radio rom
It started as usual with the status bar moving. Suddenly some error messages came up. Can't remember exactly, but like some address can't find error.
Now, the phone is dead completely. I can''t even enter bootloader mode. Only when I take out the battery and plug in the charger cable the red light comes on. I looked the upgrade problem page, my symptom doesn't match any.
Is there a possible way that I can still save it??
Help!!!!
I had something similiar happen a little while back. What I did was pull the battery out and leave it out for a while, maybe a few minutes. I then put the battery back in and held the two side buttons and hit the reset button to put me into bootloader mode. I then cabled it to my computer and flashed a new OS via mutty. That got my phone back and operational.
@float. Nuh, it didn't work on my brick. Prob i will have to take it back to Tmobile if they kind enough to repair the no warranty phone i bought on ebay.
Sorry to have opened a new thread, I was so desperate.
Plz delelte it.
how exactly did you try to update the radio using mtty?
I download the 1.27 shipped radio rom. P.S. It seemed to be a german version, not sure whether that caused the disaster.
Using NBHextract to get the single GSM.NB file, then in MTTY, typed
USB> task 32
USB> lnb GSM.NB
Before flashing, just had it upgraded to the HTC AKU3.3 OS rom only. The old version radio rom version before flashing was 1.18.
Maybe the order i flash is wrong. I flashed OS first then the radio rom.
just guessing
ok, you loaded the radio rom code where os.nb should go. That may have caused mega bad blocks in flash. Can you even get bootloader mode if you reset using Wiki directions to obtain Tri-color bootloader?
Yes. I have tried many ways wiki suggests. Such as removing the battery leaving it more than half an hour and plugging it to the usb cable without battery. still can't get to the tri-color bootloader mode. Basically, I just can't turn on the phone.
If you connect it to the computer, can it communicate w/the PC? If you hear the windows tones try opening up mtty and see if you can communicate.
i'm stuck in the same place
for me it happened during extrom flash
Try removing the battery for a bit (a few minutes, maybe half an hour). Then, put the battery back in but don't plug the usb cable in. After that, hold the two side buttons as if you're trying to get it to go into the bootloader. Hit the reset button a few times with your stylus and see if that gets you to the bootloader. That's what worked for me.
tried that
tried removing battery and connecting usb
nothing helps
is there a place that fixes tytn in belgium ?
is there a way to flash a new rom via mutty ?
cause i still have the boot loader, but the phone still in the splash screen
when i type info 2 in the mutty command prompt i get this answer
Cmd>info 2
HTCSQTEK_203”µ·êHTCE
i think it's not realy normal
diffda said:
is there a way to flash a new rom via mutty ?
cause i still have the boot loader, but the phone still in the splash screen
when i type info 2 in the mutty command prompt i get this answer
Cmd>info 2
HTCSQTEK_203”µ·êHTCE
i think it's not realy normal
Click to expand...
Click to collapse
well your not supercid... your still locked to qtek
Look here and unlock your phone before doing any flashing!
http://forum.xda-developers.com/showthread.php?t=295751
to late i ve done that tow day's ago , now the only way to make my phone back to life, PB + KITL method i think
god bless KITL
I was instaling NBD_v8.3_8MB trough shelltool on my MDA Vario then something happened and my PC restarted I whink it is because of the electicity .... so now when I restardet my phone it is stuck on the T-mobile screen Where it is writen.....
IPL 2.21.001
SPL 2.21.Olip
GSM 02.19.11
OS 6.6.6.666
Thanks in advance
First of all, its not bricked. Bricked = doesn't turn on, nothing, blank screen.
I've looked to your info, you already have HardSPL, so you can flash directly using any RUU, don't use shelltools!
Enter bootloader (hold camera+reset), open up the RUU of the ROM you want (make sure it doesn't have any IPL/SPL) and flash away
well I looked all day what to do and I can not find solution
I just can not understand how to flash the phone
I found one solution via some kind of Wizard_love, but again I do not know what to do
Please help i am haveing the same thing just did it today i have the Cingular 8125....i have held camera+reset and got into these Red,Green,Blue,white screen and it says IPL 2.25 and SPL 2.25 now when i run the ROMUpdateUtility_Wizard_NoID it does not work i have my usb pluged in and my phone says USB please help
Thank you
PS.
I am running Vista
IPL 2.25
SPL 2.25
GSM 02.25.11
OS.6.6.6.666
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Ok i have try everything. I have tried the RUU from the HTC site and even everything else when it is searching for the PDA and crashes idk why. I turn on my phone holding the camera and i get to the Red,Green,Blue,White...Plug the USB in and the phone says USB but not my computer??? so i don't know what i need to do please HELP i just got the phone and read you can do all this stuff
1. Please use a PC with Windows XP
2. Download your original carrier ROM (i.e. Cinglular stock ROM) and flash back to original WM5
3. Install HardSPL or use SSPL
4. Flash to WM6
starkwong said:
1. Please use a PC with Windows XP
2. Download your original carrier ROM (i.e. Cinglular stock ROM) and flash back to original WM5
3. Install HardSPL or use SSPL
4. Flash to WM6
Click to expand...
Click to collapse
Were can i get HardSPL,SSPLand the flash back up?
all i have is the original rom
You guys wanna see bricked? I have a BRICKED! phone... My MDA was the unfortunate victim of a car accident. When my car went carreening off the road, my MDA went flying through the air and ended up on the floor of the car but not before hitting virtually every surface on the inside of the car.
Now my charge port is completely snapped off and my battery shorted out when I was trying to hold the charge port in place to charge it and fried the main board. DEAD. NO MORE.
THAT MY FRIENDS, IS BRICKED....
No worries though, I already ordered a TyTN II
Cool can you help?
Oh and i had the same problem with my mda and i got it replaced from tmobile. - the easiest way to reapair an MDA is getting it replaced ^^
offtopic
@dharvey4651
Why didn't you buckle up your phone?
Well i got mine up and running agian just used XP and install the RUU from HTC YES.......Now when i go to install WM6 when i press update were it should show me the Ver. of the one i am installing on my phone it does not say why please help and what do i need to install WM6 on my phone?
Just a quick question did you read the other threads there are already. They basicly explain everything clear and good
i have just still stuck on some stuff
dferreira said:
First of all, its not bricked. Bricked = doesn't turn on, nothing, blank screen.
I've looked to your info, you already have HardSPL, so you can flash directly using any RUU, don't use shelltools!
Enter bootloader (hold camera+reset), open up the RUU of the ROM you want (make sure it doesn't have any IPL/SPL) and flash away
Click to expand...
Click to collapse
jukata
first of all,as dferreira has assured u that ur device is not bricked,secondly ,you already have HardSPL,that means your device is unlocked,just follow his instructions,download any wm6 Rom and flash,it'll good to go,but if u still want to be sure,download WST Tool from the below given thread read carefully and apply the tool to verify the status of ur device,
http://forum.xda-developers.com/showthread.php?t=329170
u can flash NBD rom which u have or any other wm6 rom,goodluck
NVM i am on the Other Page! Thanks
Ok, i have read everywhere and can't help myself, so if someone would be kind enough to help it would be much appreciated
Ok, Used SoftSPL and tried flashing the ROM. It manages to get to 99% and then just goes RED. I have tried 3 different ROMS and same story it goes RED at 99%.
When i remove the battery, it goes to the RUU Red, Green and Blue screen. SPL version is 2.16.0001. Not Oli's new one.
What do i do from now?
kastro said:
Ok, i have read everywhere and can't help myself, so if someone would be kind enough to help it would be much appreciated
Ok, Used SoftSPL and tried flashing the ROM. It manages to get to 99% and then just goes RED. I have tried 3 different ROMS and same story it goes RED at 99%.
When i remove the battery, it goes to the RUU Red, Green and Blue screen. SPL version is 2.16.0001. Not Oli's new one.
What do i do from now?
Click to expand...
Click to collapse
Soft SPL only allows you ONE update, so phone is CID unlocked only when Soft SPL is loaded.
It's normal for the RUU to stick on 99 % for a couple of minutes, The whole update will take aprox 10 minutes.
You can try the hard SPL from there you are semi-permanently CID unlocked.
Good luck,
EquinoXe
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