Related
i want to boot and install new rom img withput pc connection..
10x
i've tried here: http://wiki.xda-developers.com/index.php?pagename=Hermes_SDCardFlashing
the device say: "not allow 00028002" and returns to bootloader mode
which rom version are you attempting to upgrade to?
what is your CID, which device are you using? do you have HardSPL on the device??
we need more info!
i'm working on Jasjam with WM5.
IPL-1.00
SPL-1.11
Can you not install via USB?
You really need HardSPL before you go ahead with any upgrades.
i can't... the device stuck on the windows welcome screen and therefore i can't connect via USB
sagivo said:
i can't... the device stuck on the windows welcome screen and therefore i can't connect via USB
Click to expand...
Click to collapse
can you put your device in the booloader? that should do the trick
i can. but now what?
10x again
Your best bet is to follow the instructions in the Unbricking Thread.
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. I wanted to install Android on my HD2 but for that I need radio versions 2.08 - 2.12. And currently my radio version is 2.06 so I wanted to flash it to 2.10 or one of them between 2.08-2.12. For this I used Custom RUU. Everything went well untill it said installing, and it went to 4% and then suddenly my phone reboots and then on my computer it says "Error 270. The image file is corrupted. Please check your Update Utility."
Well what have I done wrong?
Nilee said:
Hi. I wanted to install Android on my HD2 but for that I need radio versions 2.08 - 2.12. And currently my radio version is 2.06 so I wanted to flash it to 2.10 or one of them between 2.08-2.12. For this I used Custom RUU. Everything went well untill it said installing, and it went to 4% and then suddenly my phone reboots and then on my computer it says "Error 270. The image file is corrupted. Please check your Update Utility."
Well what have I done wrong?
Click to expand...
Click to collapse
Did you have install HSPL on your device?
Yes I have installed HSPL. But if you have installed HSPL, is it then supposed to show "HSPL" somehere on the bootloader screen? Because on mine it doesn't.
But then that's weird because I did install HSPL and it even said succesfull. But still I get the same error when I try to flash the radio.
Go into bootloader by holding the VOL- (down) button, while pressing the End Call button to boot up your phone from being all the way turned off.
Check on your bootloader (tri-color) screen for the letters HSPL and the name Cotulla.
If these things are not present, then for some reason you don't have HSPL installed.
If this is the case, stay in bootloader, and re-run HSPL, and then check again in your bootloader to make sure you have HSPL, and then re-flash the custom_ruu
Chances are it just didn't take because your phone didn't have HSPL for whatever reason. You might want to re-download the radio ROM just to be sure you didn't get a corrupted/incomplete download.
Good luck
oops ignore plz
but what a shame that my pc even doesnt play with custom ruu.nothitng happen when i click.i have everything installed.
huggs said:
Go into bootloader by holding the VOL- (down) button, while pressing the End Call button to boot up your phone from being all the way turned off.
Check on your bootloader (tri-color) screen for the letters HSPL and the name Cotulla.
If these things are not present, then for some reason you don't have HSPL installed.
If this is the case, stay in bootloader, and re-run HSPL, and then check again in your bootloader to make sure you have HSPL, and then re-flash the custom_ruu
Chances are it just didn't take because your phone didn't have HSPL for whatever reason. You might want to re-download the radio ROM just to be sure you didn't get a corrupted/incomplete download.
Good luck
Click to expand...
Click to collapse
Ok, then my HSPL isn't installed. But that's real' weird. Because when I install HSPL everything goes okay and it even says "Succesful" etc. I've tried to install HSPL for like 4 times and it always says installation completed, but however it doesn't show anything like HSPL or Cotulla on the bootloader screen. And I do have SPL 1.42.0000, which is required to install HSPL. And I also disabled my anti-virus so what have I done wrong?
By the way: When I go to bootloader mode it always goes to a grey screen first with blue words "Loading" and after a few seconds it says "Not allow" and after that it finally goes to bootloader mode. Is it supposed to be like that or what's wrong with this?
Nilee said:
But then that's weird because I did install HSPL and it even said succesfull. But still I get the same error when I try to flash the radio.
Click to expand...
Click to collapse
did you use hspl3 and not changing the dropdown from its default 2.08.0000 which is stock. run it again and make sure the dropdown ends .hspl
saurabh88 said:
but what a shame that my pc even doesnt play with custom ruu.nothitng happen when i click.i have everything installed.
Click to expand...
Click to collapse
anti virus program give you a hit when you first downloaded it?
many times the file gets disabled so you need to download it again, even if you turned off the av or told it to allow customruu.
also right click and "run as administrator" even if you are logged in as admin.
Nilee said:
By the way: When I go to bootloader mode it always goes to a grey screen first with blue words "Loading" and after a few seconds it says "Not allow" and after that it finally goes to bootloader mode. Is it supposed to be like that or what's wrong with this?
Click to expand...
Click to collapse
there's a leoimg on your sd card (or your phone thinks there is) but it isn't starting. remove the card.
Ok, well I used HSPL 2 and it installed correctly. HSPL 1 however didn't work for me. After I installed HSPL 2 it clearly said something like HSPL 2.08 on the bootloader screen. So I tried to flash to a new radio with CustomRUU. It all went well, untill it was installing and suddenly said: CONNECTION ERROR CRITICAL ERROR or something like that. It also said that the USB cradle or something was unconnected, however it was still connected and I didn't even touch it. After that my phone rebooted and went into bootloader mode again. The weird thing is that it doesn't say HSPL 2.08 anymore. Now t says SPL 1.42 again so the HSPL went away or something. I tried to reboot the phone (using the red button at the back of the phone) but it went into bootloader mode again. Well, all it does is go into bootloader mode. I can't even get to the normal thing again, only the bootloader mode. What the hell have I done wrong?
By the way: If I'm in bootloader mode all it says is this:
HX-BC
SPL-1.42.0000 XE <-- (before this it still had HSPL but now it went away)
MicroP-Wrong Platform (0x0)
MicroP(TOUCH) 0x30
Can anyone help me? Have I bricked my phone??
Just a question/suggestion,
Did you already thought to use/install the latest stock ROM 3.14 !?
the reason of this suggestion is this stock ROM have Radio 2.15.50 already integrated (no need of HSPL) and it's compatible with Android.
Well I didn't, I will try to do it. But I don't know how. Because my phone is still only able to get into bootloader mode. And it won't even charge it's battery..
So do I have to put the Stock ROM on my SD now, and flash it from the SD card?
I don't even know how much battery my phone still has..
Nilee said:
Well I didn't, I will try to do it. But I don't know how. Because my phone is still only able to get into bootloader mode. And it won't even charge it's battery..
So do I have to put the Custom ROM on my SD now, and flash it from the SD card?
I don't even know how much battery my phone still has..
Click to expand...
Click to collapse
You can flash stock ROM when you are in bootloader mode.
kurt-willems said:
You can flash stock ROM when you are in bootloader mode.
Click to expand...
Click to collapse
How?
By the way, my phone is in bootloader mode but it won't connect to the computer using a USB cable, it also won't charge it's battery.
Nilee said:
How?
By the way, my phone is in bootloader mode but it won't connect to the computer using a USB cable, it also won't charge it's battery.
Click to expand...
Click to collapse
Ok, then rest you the flashing over SD.
Make attention to use the right stock ROM; use your S/N to get access at your stock ROM on the HTC webpage.
deleted please ignore
Ok so I just extract the .exe and take the .nbh file of it and rename it to leoimg.nbh and put it on SD and start flashing?
Nilee said:
Ok so I just extract the .exe and take the .nbh file of it and rename it to leoimg.nbh and put it on SD and start flashing?
Click to expand...
Click to collapse
Yes; that"s it.
Hy!
I did a stupid thing, with the following. I copyed an LEOIMG.nbh file to my formatted sd card, so I get an SPL-1.42.0000, but I can't flash any HSPL to my device, because the HSPL setup writes out USB connection error. Neighter can I flash for example the official 1.66 rom, the installation stops after 1%, and writes INVALID VENDER ID. What can I do?
Very siple but you need lots of time for it. The rom you flashe has spl 3.03 on it and so it doesn't allow you to flash any other spl on it. What you can do is you have to search for old stock roms in the native language of your phone. As long as the phone keeps giving you error when trying to flash a stockrom with you sd card, it means you have not yet gotten the right stockrom for you phone so you have to try with different old stockroms till you get the right one.
After that. you'll be able to flash whatever you like. Hope it helps.
But remember, you need time and patience.
Abdul9. said:
Very siple but you need lots of time for it. The rom you flashe has spl 3.03 on it and so it doesn't allow you to flash any other spl on it. What you can do is you have to search for old stock roms in the native language of your phone. As long as the phone keeps giving you error when trying to flash a stockrom with you sd card, it means you have not yet gotten the right stockrom for you phone so you have to try with different old stockroms till you get the right one.
After that. you'll be able to flash whatever you like. Hope it helps.
But remember, you need time and patience.
Click to expand...
Click to collapse
Thanks, I will try it. This stockrom is 1.66?
zoldya said:
Hy!
I did a stupid thing, with the following. I copyed an LEOIMG.nbh file to my formatted sd card, so I get an SPL-1.42.0000, but I can't flash any HSPL to my device, because the HSPL setup writes out USB connection error. Neighter can I flash for example the official 1.66 rom, the installation stops after 1%, and writes INVALID VENDER ID. What can I do?
Click to expand...
Click to collapse
You can also download HSPL 4 and use it to downgrade your SPL. To do this manualy put your HD2 into bootloader by holding the volume down button and pressing the power(end) butom momentarily. Once in bootloader connect your HD2 to your computer via USB cable wait until you see USB in the white bar of thd bootloader and run the HSPL 4 on your computer. It will ask you which SPL or HSPL you wish go flash select the proper SPL version to flash to your HD2 and you should be good to go. Hint the SPL version will have zeros at the end of them and the HSPL version will not. Example SPL 2.08.0000 HSPL 2.08. Hope this helps.
T-Macgnolia said:
You can also download HSPL 4 and use it to downgrade your SPL. To do this manualy put your HD2 into bootloader by holding the volume down button and pressing the power(end) butom momentarily. Once in bootloader connect your HD2 to your computer via USB cable wait until you see USB in the white bar of thd bootloader and run the HSPL 4 on your computer. It will ask you which SPL or HSPL you wish go flash select the proper SPL version to flash to your HD2 and you should be good to go. Hint the SPL version will have zeros at the end of them and the HSPL version will not. Example SPL 2.08.0000 HSPL 2.08. Hope this helps.
Click to expand...
Click to collapse
I have tried that, but after a few minutes - when it tries connect to the device - the HSPL setup writes out an error message;
CRITICAL ERROR
Flow:00000001
Error code: 00000002
Description: USB Connect failed!
but i don't know why, because during the installationvI see USB in the white bar of the bootloader - the device manager on the notebook shows the connection too. :S
Abdul9. said:
Very siple but you need lots of time for it. The rom you flashe has spl 3.03 on it and so it doesn't allow you to flash any other spl on it. What you can do is you have to search for old stock roms in the native language of your phone. As long as the phone keeps giving you error when trying to flash a stockrom with you sd card, it means you have not yet gotten the right stockrom for you phone so you have to try with different old stockroms till you get the right one.
After that. you'll be able to flash whatever you like. Hope it helps.
But remember, you need time and patience.
Click to expand...
Click to collapse
I just finished with the 1.66 OSPL roms http://http://forum.xda-developers.com/showthread.php?t=623283 but the problem was the same with each one. Should I try the 3.14 rom-s too?
zoldya said:
I just finished with the 1.66 OSPL roms http://http://forum.xda-developers.com/showthread.php?t=623283 but the problem was the same with each one. Should I try the 3.14 rom-s too?
Click to expand...
Click to collapse
Have you tried to restart your PC and or change another USB port of your PC?
zoldya said:
I have tried that, but after a few minutes - when it tries connect to the device - the HSPL setup writes out an error message;
CRITICAL ERROR
Flow:00000001
Error code: 00000002
Description: USB Connect failed!
but i don't know why, because during the installationvI see USB in the white bar of the bootloader - the device manager on the notebook shows the connection too. :S
Click to expand...
Click to collapse
Try the above post by silverwind and try another USB port, another computer, and another cable if you have too. Something just does not sound right about this. I am looking at this.
CRITICAL ERROR
Flow:00000001
Error code: 00000002
Description: USB Connect failed!
Click to expand...
Click to collapse
Just keep trying man I think you might just have a simple problem here.
Heck reset your notbook if you think it might help.
I have tried that too, and didn't solve the problem... :'(
Do you think that GoldCard method would help?
Hi. I have the same pronblem. I have a UK HD2 that was originally on Tmobile. I flashed 2.08HSPL using HSPL4 & upgraded the ROM to the standard WWE_3.14. A long story short... after playing around with SD Android & a few other utilities I wanted to make a clean start, so my plan was to use HSPL4 to remove the HSPL before then re-installing it & reflashing the ROM. Unfortunately I now seem to be stuck in SPL2.08.0000. HSPL4 just gives the same error:
CRITICAL ERROR
Flow:00000001
Error code: 00000002
Description: USB Connect failed!
I have also tried flashing a stock ROM via SD (renamed leoimg.nbh), but I can't get passed the bootloader displaying 'serial'.
Any ideas?
Chameleon846 said:
Hi. I have the same pronblem. I have a UK HD2 that was originally on Tmobile. I flashed 2.08HSPL using HSPL4 & upgraded the ROM to the standard WWE_3.14. A long story short... after playing around with SD Android & a few other utilities I wanted to make a clean start, so my plan was to use HSPL4 to remove the HSPL before then re-installing it & reflashing the ROM. Unfortunately I now seem to be stuck in SPL2.08.0000. HSPL4 just gives the same error:
CRITICAL ERROR
Flow:00000001
Error code: 00000002
Description: USB Connect failed!
I have also tried flashing a stock ROM via SD (renamed leoimg.nbh), but I can't get passed the bootloader displaying 'serial'.
Any ideas?
Click to expand...
Click to collapse
Did you place the leoimg.nbh on the root of your SD card? Also was tbe dile you renamed originaly named RUU_signed.nbh?
T-Macgnolia said:
Did you place the leoimg.nbh on the root of your SD card? Also was tbe dile you renamed originaly named RUU_signed.nbh?
Click to expand...
Click to collapse
Yes on both counts... I've even tried a complete 'long' reformat of the SD card first using the Panasonic SD Formatter, before putting the leoimg.nbh at the root.
I'm guessing that my stupid mistake is downgrading to SPL2.08.0000 whilst having a generic version of the 3.14 ROM installed. I guess I should have downgraded the ROM to an original Tmobile one first...
Could i ask what operating system you guys are using cos this problem could have less to do with the phone than it has to do with the operating system on the pc. I was trying to flash some roms on some old devices using Windows 7 but this didn't seem to work but it magically worked when i used Windows xp. I hope this works.
About the wrong Vendor problem, this just means the rom flashed is not recognized by the phone as the official one, i also had that problem and after flashing a official rom in the language of my phone, the problem was solved. I used the 1.66 rom so that i could flash hspl or else it might be impossible to do so.
Or as someone suggested you might try the hspl4 (never knew that existed) but try using Windows xp and if the problem persists try reinstalling your operating system (on your pc). I know it a lot of work but its just to rule out that the problem is from the pc.
Another thing i want to make sure of is if the phone is working normally with the rom on it or is there no rom at all?
Abdul9. said:
Could i ask what operating system you guys are using cos this problem could have less to do with the phone than it has to do with the operating system on the pc. I was trying to flash some roms on some old devices using Windows 7 but this didn't seem to work but it magically worked when i used Windows xp. I hope this works.
About the wrong Vendor problem, this just means the rom flashed is not recognized by the phone as the official one, i also had that problem and after flashing a official rom in the language of my phone, the problem was solved. I used the 1.66 rom so that i could flash hspl or else it might be impossible to do so.
Or as someone suggested you might try the hspl4 (never knew that existed) but try using Windows xp and if the problem persists try reinstalling your operating system (on your pc). I know it a lot of work but its just to rule out that the problem is from the pc.
Another thing i want to make sure of is if the phone is working normally with the rom on it or is there no rom at all?
Click to expand...
Click to collapse
Hi. Thanks for the input. The problem is getting even more frustrating! I've tried buying a new 4GB micro SD card (both are class 4). I have tried both TMO_UK_1.72 & TMO_UK_1.43. Both ROMs were downloaded from HTC using the correct phone's serial, so they should be the correct ones.
With the original SD card I can't get passed the bootloader screen & it just stays in 'serial' mode. With the new SD card it moves on to 'loading...', but then just hangs. I haven't yet seen the word 'searching' as described in the [TUT] Flash your ROM / Radio via microSD.
To clarify, the phone boots fine with the installed 3.14 ROM, but I can't get away from SPL 2.08.0000 or flash any other ROM.
Chameleon846 said:
Hi. Thanks for the input. The problem is getting even more frustrating! I've tried buying a new 4GB micro SD card (both are class 4). I have tried both TMO_UK_1.72 & TMO_UK_1.43. Both ROMs were downloaded from HTC using the correct phone's serial, so they should be the correct ones.
With the original SD card I can't get passed the bootloader screen & it just stays in 'serial' mode. With the new SD card it moves on to 'loading...', but then just hangs. I haven't yet seen the word 'searching' as described in the [TUT] Flash your ROM / Radio via microSD.
To clarify, the phone boots fine with the installed 3.14 ROM, but I can't get away from SPL 2.08.0000 or flash any other ROM.
Click to expand...
Click to collapse
Ok here is a couple of options for you. One go to www.t-mobile.com if you have a T-Mobile HD2 and type HTC HD2 upgrade in the search box on the home screen of the website and you will find the official T-Mobile 3.14 ROM. You will have to enter your IMEI number under your battery to download it. Download this ROM and then follow the steps to flash it via SD card, hint you will have to rename the original .exe file to .zip to gain access to the .nbh file. Also you can download and run HSPL 4 on your HD2 and select SPL 3.03.0000 but the official ROM will change it to SPL 3.10.0000 if you flash via SD card
Its a common problem i think if you are trying to flash a rom via sd card with a sd card higher than class two. Many here have encountered such problems.
According to your description, it will seem that it is as i suspected, the pc doesn't seem to recognize the phone and this could mean you have a defect usb cable or the useport itself is not funtioning properly. Try holding the phone in your hand with the usb in and support the usb with your hand to make sure the usb is indeed in the phone and see what happens. My usb cable is a little bit loose so when i want to flash anything, i use my hand to support it or i place my phone on a smoot surface and make sure the usb cable is in it.
zoldya said:
Hy!
I did a stupid thing, with the following. I copyed an LEOIMG.nbh file to my formatted sd card, so I get an SPL-1.42.0000, but I can't flash any HSPL to my device, because the HSPL setup writes out USB connection error. Neighter can I flash for example the official 1.66 rom, the installation stops after 1%, and writes INVALID VENDER ID. What can I do?
Click to expand...
Click to collapse
Chameleon846 said:
Hi. I have the same pronblem. I have a UK HD2 that was originally on Tmobile. I flashed 2.08HSPL using HSPL4 & upgraded the ROM to the standard WWE_3.14. A long story short... after playing around with SD Android & a few other utilities I wanted to make a clean start, so my plan was to use HSPL4 to remove the HSPL before then re-installing it & reflashing the ROM. Unfortunately I now seem to be stuck in SPL2.08.0000. HSPL4 just gives the same error:
CRITICAL ERROR
Flow:00000001
Error code: 00000002
Description: USB Connect failed!
I have also tried flashing a stock ROM via SD (renamed leoimg.nbh), but I can't get passed the bootloader displaying 'serial'.
Any ideas?
Click to expand...
Click to collapse
Ok do to some recent personal experience and some other members problem of late. I suggest both of you do this go to www.windowsmobile.com/getstarted and download the most recent version of WMDC wich has updated drivers in it that seems to solve somd problems with flashing via USB especially if you are using a 64 bit system. Just so both of you know unless your HD2 shows up as "HTC USB Sync" in the device manager while connected via USB while in bootlaoder you do not have the correct drivers installed and any flash will fail.
T-Macgnolia & Abdul9: Thanks for that, however mine is a UK Tmobile HD2 & the .com site is only for US ones (it doesn't recognise UK IMEI's). If I go via the UK site it just links me to the HTC update site for the RUU_Leo_S_TMO_UK_3.14.110.1_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship (& also the 1.72 & 1.43 versions. I have tried all of these via both SD card & via USB. I have also tried HSPL4, HSPL3 & HSPL2. All options have failed. I have tried from Win XP Pro & Win 7 Ultimate (both 32bit) with two different USB leads. I have also tried a 3rd SD card (which ends up stalling at the 'loading' screen. The phone flashed fine prior to removing 2.08HSPL with HSPL4.
I think that the problem is not the SD card or the USB lead, but is the problem that I've now got a Tmobile (UK) phone with spl 2.08 & a WWE_3.14 ROM installed - this should obviously not normally be possible. I can't flash back to HSPL & I can't downgrade to any other ROM.
Does anyone have any idea how I can 'fool' the phone into letting me change the ROM?
I've been reading about Task29, but it says don't do this unless you have HSPL (which I can't get!). I don't want to brick the phone (because it still runs!), but I want HSPL back otherwise I can't reinstall Android on SD.
Furthermore, I don't think this is a USB driver issue, as it flashed fine before & it's occurring across different PC's & operating systems.
It's an incompatibility between a branded Tmobile with SPL & a WWE HTC ROM... I just need to get out of the loop I'm stuck in!
Hey Chameleon I know you don't think it is a problem with the drivers cause it was flashing fine before. But what I do not think you have taken into account is that you came from a older ROM and you had the right drivers to work with that ROM or the update for that ROM. But you now have a 3.14 ROM and this is a newer ROM that probably requires different drivers. I mean Microsoft did not create a new WMDC with updated drivers if it was not needed for the 3.14 ROMs as they are the most recent official ROM versions. Microsoft is the one that comes out with the new ROM versions too, the carriers just add their bloatware to them. Do you see my train of thought here? Also make sure you are usinv SD card that is 500MBPS to 8GB that is formated with Fat 32.
T-Macgnolia said:
Hey Chameleon I know you don't think it is a problem with the drivers cause it was flashing fine before. But what I do not think you have taken into account is that you came from a older ROM and you had the right drivers to work with that ROM or the update for that ROM. But you now have a 3.14 ROM and this is a newer ROM that probably requires different drivers. I mean Microsoft did not create a new WMDC with updated drivers if it was not needed for the 3.14 ROMs as they are the most recent official ROM versions. Microsoft is the one that comes out with the new ROM versions too, the carriers just add their bloatware to them. Do you see my train of thought here? Also make sure you are usinv SD card that is 500MBPS to 8GB that is formated with Fat 32.
Click to expand...
Click to collapse
WOW! I've got the problem sorted! This can't be a coincidence... I haven't done anything different to my PC, but I got an 'unlock' code through for my phone this morning (£5.99 on Ebay) & it worked fine. I though "why not" & tried HSPL4 again. With no other changes it worked absolutely fine this time & I now have 2.08HSPL installed.
Presumably by unlocking my my phone from Tmobile it has also removed the 'you're using the incorrect ROM' problem.
Thanks for everyones input on this. I maintain that XDA-Developers is one of the best Forums around (not just within the mobile phone arena).
Please help anyone. Now phone not works. back screen always! jus when i connect it to usb pc shows found new hardware Qualcomm CDMA Technologios MSM.
Sorry, pushed thanks button accidently
Well, are you able to enter bootloader? Push volume button down (when the phone switched off) and push switch on button (end call). See if you have hspl on three-colored screen, then connect phone to pc. If you see USB, then flash original Rom. Then you can flash any rom according to cooker instructions. But I would recommend to install HSPL.
This could happen if you flashed radio without having HSPL on.
Skyguar said:
Sorry, pushed thanks button accidently
Well, are you able to enter bootloader? Push volume button down (when the phone switched off) and push switch on button (end call). See if you have hspl on three-colored screen, then connect phone to pc. If you see USB, then flash original Rom. Then you can flash any rom according to cooker instructions. But I would recommend to install HSPL.
This could happen if you flashed radio without having HSPL on.
Click to expand...
Click to collapse
Now press who you want... NO three-colored screen. Only Qualcomm CDMA Technologies MSM in device manager. Yes i had HSPL.. Actually im in shock now my HD2 really no longer works can't believe it
try to remove the battery for 10 seconds and then put it back and try to enter bootloader.
Try many times if u do not get it first time.
Flash ur HD2 with the original ROM.
WBR
Siemens Lover
SiemensLover said:
try to remove the battery for 10 seconds and then put it back and try to enter bootloader.
Try many times if u do not get it first time.
Flash ur HD2 with the original ROM.
WBR
Siemens Lover
Click to expand...
Click to collapse
Try everything.. I thing jtag can help here ?
Is it a T-Mobile HD2? If yes, then you bricked it. .51 radios are strictly for non TMOUS HD2's
Have a look here maybe you can save it
http://forum.xda-developers.com/showthread.php?t=668347#6262090
stathis95194 said:
Have a look here maybe you can save it
http://forum.xda-developers.com/showthread.php?t=668347#6262090
Click to expand...
Click to collapse
relies on being able to get into bootloader, so cant help a radio brick.
@OP, you need JTAG or new mainboard or new phone.
stathis95194 said:
Is it a T-Mobile HD2? If yes, then you bricked it. .51 radios are strictly for non TMOUS HD2's
Have a look here maybe you can save it
http://forum.xda-developers.com/showthread.php?t=668347#6262090
Click to expand...
Click to collapse
Yes mine is HTC HD2 T-mobile from USA ..