Related
Ok, I've been trying to update my 8525 for hours...here is my problem. First, I tried to HardSPL-v7 but I kept getting an "Error [240] File open". I think this is preventing me from doing any ROM update. When I try to run the Cingular ROM update activesync shuts down and I get a connection error, I think it is "error [260]". I have wiped or cleaned out my 8525 so that I am back to day one. I have tried both ROM updates on 2 separate computers and I get same error messages on both computers. I have searched the Wiki's but have found nothing, so please help. As you can tell, I am a virgin to ROM updates so please go gently.
I should add, my present ver. ROM AKU 2.3 (1.34.502.7018.01H) SPL 1.06 IPL 1.01. Radio is 1.16.
have you taken a look at my Safe WM5 Upgrade Guide??
If you follow this guide EXACTLY, you should be fine.
mrvanx said:
have you taken a look at my Safe WM5 Upgrade Guide??
If you follow this guide EXACTLY, you should be fine.
Click to expand...
Click to collapse
I have, I have even tried the mtty "fix" but I had problems with that as well. I get a modem connection screen but there is nothing about a USB connection.
Bit more info would be nice, which ROM are downloading, and where from??
Also what procedure are you doing to update?? EXACT info please.
mrvanx said:
have you taken a look at my Safe WM5 Upgrade Guide??
If you follow this guide EXACTLY, you should be fine.
Click to expand...
Click to collapse
Ok, I just tried it 2 more times, Hard-SPL. It flashes to the 8525 and goes into bootloader and shows the following "HERM100 IPL-SSPL by Des HERM100 SPL-1.09.ds" at this point activesync 4.5 shuts down the 8525 is stuck in bootloader (it never reboots) and after a few minutes I get "Error [260] Upated Error". Hard SPL shuts down and the 8525 is stuck in bootloader mode. At this point I have been disconnecting the USB cable and doing a soft reset, once the phone is on, I go into bootloader and the old info shows up SPL 1.06 and IPL 1.01.
Let me have a think, firstly do you have the latest versions of the .net framework installed?
I was able to finally run HardSPLv7, I had to do it on another computer. Now, I would like to update to RUU_Hermes_CINGULAR_WWE_2.15.502.3_6275_1.40.30.00_108_Ship.exe. I assume I should use the same computer that I used to successfully run HardSPL. Do I need to rebuild the rom file with RUUWrapper.exe (CustomRUU by olipro) & Dutty's Good NBH Tool, before running the RUU_Hermes_CINGULAR_WWE_2.15.502.3_6275_1.40.30.00_108_Ship.exe update?
mrvanx said:
Let me have a think, firstly do you have the latest versions of the .net framework installed?
Click to expand...
Click to collapse
I have .Net 1 thru 3.5 (pre-release) installed on the computer that I can not get to run any ROM updates.
9
compudds said:
I was able to finally run HardSPLv7, I had to do it on another computer. Now, I would like to update to RUU_Hermes_CINGULAR_WWE_2.15.502.3_6275_1.40.30.00_108_Ship.exe. I assume I should use the same computer that I used to successfully run HardSPL. Do I need to rebuild the rom file with RUUWrapper.exe (CustomRUU by olipro) & Dutty's Good NBH Tool, before running the RUU_Hermes_CINGULAR_WWE_2.15.502.3_6275_1.40.30.00_108_Ship.exe update?
Click to expand...
Click to collapse
Yes if you carry on the guide past flashing hardspl you will get the radio updated aswell.
Can i ask, what is different on the computer you used???
mrvanx said:
Yes if you carry on the guide past flashing hardspl you will get the radio updated aswell.
Can i ask, what is different on the computer you used???
Click to expand...
Click to collapse
Off hand, the major difference would be Intel (worked) vs. AMD (failed) but I doubt that is the problem, you would be flooded with questions due to so many computers that have AMD chips. The USB cable was the same as well. I'll have to think about that...
Definatly check your "failed" computer is up to date with .net and everything else, most likely a software problem.
I have this problem as well..
AT&T 8525 windows moble 6 trying to install the hardspl v7.
v3.5 and 3.0 .net framework.
the RUUwrapper program gets to the 'verifiying info' screen then give me an erroe 240 message. 'the update utility can not open the requested file.'
any help would be great. Looking to add the touch it interface.
thanks,
Mike
Read the post Hard SPL at the top of this forum and go to page 116 ( I believe its post #1160) and use the sd card method. You don't need to use the pc at all. I generally flasah ALL os's using the sd card method as it seems to be safer then using the usb method. No "sync errors" to deal with.
Cheers...
I have the exact same problem..
When it goes to tri-color screen, the USB connection goes off and windows will pop up the search for driver dialogue box.. then afterward another dialogue box will appear saying Error [260].
I tried restarting my pc and device (even removing the battery) but still failure
Any help would be highly appreciated. Thanks.
blackphnx said:
I have the exact same problem..
When it goes to tri-color screen, the USB connection goes off and windows will pop up the search for driver dialogue box.. then afterward another dialogue box will appear saying Error [260].
I tried restarting my pc and device (even removing the battery) but still failure
Any help would be highly appreciated. Thanks.
Click to expand...
Click to collapse
I loaded it thru the sd card just as the post above suggested. It loaded the hardspl just fine. My PPC seems to run faster as well.
Thanks for the help! it is much appreciated.
blackphnx said:
I have the exact same problem..
When it goes to tri-color screen, the USB connection goes off and windows will pop up the search for driver dialogue box.. then afterward another dialogue box will appear saying Error [260].
I tried restarting my pc and device (even removing the battery) but still failure
Any help would be highly appreciated. Thanks.
Click to expand...
Click to collapse
One thing that i have learned from flashing my 8525 is to remove any USB device except the 8525. This has worked for me.
swimmy said:
One thing that i have learned from flashing my 8525 is to remove any USB device except the 8525. This has worked for me.
Click to expand...
Click to collapse
But my mouse is on USB. I might try on different computer and post back the results.
UPDATE
I tried using my friend's laptop and it installed without a problem. I think the issue is with the .NET framework. I installed the latest one before flashing and it worked fine. Hmmm.. Im not sure about this tho.
Hello.... Try the sd card method. You don't need the computer...
Sorry if I sound condescending, but, I seem to find a lot of people saying that they have sync problems. Solution, Take the pc out of the equation (except to load files onto sd card). It is SOOO much safer then using the pc, no "sync" problems, no chance of usb being disconnected, reset button being hit or , worst case scenario, power failure...
You have to either have little or no battery power or MANUALLY hit the reset button with the stylus to stop the flash...
And thats my 2 cents....
Refer to post #13 to find out how to use sd card method to flash hard spl...
Cheers...
sd card method???
how?
Hi All,
I'm new to the PDA-world and the Hermes. I'm trying to Hard SPL my Hermes, but it fails everytime.
When I run 2.10 - Hard-SPL-V7, it kills activesync and my connection is lost and I get always the message "error 260, Update error".
I have the latest framework edition and tried it on 3 pc's (1 Vista, 2 XP)...
What am I doing wrong?
Hope somebody can help me....
Kind Regards,
Micha
1). dont connect to active sync. open active sync and untick "allow usb connections".
2). put hermes into bootloader and connect to usb.
3). run ruu_wrapper.exe
should update to hard spl....
dont forget to tick "allow usb connections" again or you wnot be able to sync..
error 260 is an open port error.
if you wish to flash new os would advise to use sd card method. its safer than using the computer. just make sure you have greater than 50% battery power. happy flashing
Thnx, will give it a try.
First I have to flash HardSPL before I can flash a new OS, don't I?
yep, sorry, should have said run the ruu_wrapper for hard spl. My bad...
im having the same problem. I also tried the way ultramag recommended but i also received the same ending. After time i try i get the Error 260 Update error. Im running SPL 2.04 and the HTC WM6 rom from the HTC website. Does any one know what the problem is?
ultramag69 said:
2). put hermes into bootloader and connect to usb.
Click to expand...
Click to collapse
NOOOOO, that won't work, you need the SSPL to deploy to the phone, if you're running stock HTC bootloader this won't work at all, otherwise we'd have no need for Hard-SPL
hey olipro, then how would i fix this. Im running the stock rom from the HTC website with no hacks. Im trying to load PDA Corners V9 rom. Any ideas on how to fix? thanks!
Take a peek at the guide i wrote about updating the hardspl. Theres some explanation about why we need to use SSPL and the procedures.
http://www.mrvanx.org/hermes_guide/hardspl
thats the guide i used. it still gives me the error. I even unchecked "allow connections" cause i read somewhere that that would help.
i did this two days ago on my phone, im running windows vista on my home laptop and got any number of errors and problems trying to do it via sync with the phone (even after reading the vista troubleshooter, with the drivers etc)
What i ended up using was the memory card upgrade, dump the file onto the memory card and go into bootloader with the card installed.
worked fine doing that way, maybe less risky as there is no chance of the usb cable coming out.
just make sure you have a good battery charge on the phone.
Help Help Help w bricked 8525
I got into this position trying to upgrade WM5 to WM6 from HTC site.
Process got to 20% and just stayed there.
I reconnected usb cable and got a vendor id error
Then I get the Error [260]: CONNECTION
I have read a lot of posts and have tried the sd method (although i am not 100% clear) and all i get is the screen with four colors, red, green blue and white.
I believe this is the bootloader? I have downloaded RUU_signed.nbh, renamed it to hermimg.nbh, installed on root of my SD card and held OK, soft reset and power button:
My display reads:
HERM100
IPL-1.04
HERM100
SPL-2.03
This is where my journey ends.
All post indicate that the device can be reflashed and have the OS reinstalled. I can't get there from here.
Can anyone please help?
blackdog9692 said:
I have read a lot of posts and have tried the sd method (although i am not 100% clear) and all i get is the screen with four colors, red, green blue and white.
Click to expand...
Click to collapse
How big is your SD card? Flashing only works with cards <2GB. Also, sometimes certain cards just don't work for flashing, and just swapping to a different card fixes the problem.
I assume you searched the wiki, and found the relevant pages on the Hermes (including SD Card Flashing and other things about flashing/upgrading) there?
Still Lost
My SD is 2GB and I have tried many times but i just keep getting the 4 color screen. rt now when i boot from the SD my screen goes white and displays "Loading..." and then returns to bootloader screen. When i attempt to flash the rom via PC to WM5 or WM6 i get the Error 260, i also get a vendor ID error sometimes.
How can i find the key 8525 thread that i am told has the answer to my delima? I keep picking up bits and pieces but am missing some key steps and tips.
blackdog9692 said:
My SD is 2GB and I have tried many times but i just keep getting the 4 color screen. rt now when i boot from the SD my screen goes white and displays "Loading..." and then returns to bootloader screen.
Click to expand...
Click to collapse
That sounds like the SD card is formatted incorrectly. Make sure it's formatted using fat32, nothing else will work.
Still not there from here
Thanks for your help. Before I formatted the SD FAT32, nothing would happen doing the bootloader reset. OK/ON/reset button.
After format and only the hermimg.nbh file renamed as indicated, I then get what looks like the loading process but back to the bootloader screen.
Q1: This is an AT&T 8525, it was perfectly fine before failure from WM5 to WM6 (process froze at 20%), what is the RUU file that I need to put on SD??
Q2: After "Loading ..." I try the WM5 PC upgrade of ROM via USB cable, I get the load process to appear to work but it gets to 1% and the phone reboots and the PC reports error [294]: Invalid vendor ID. If I do this again I will get the Error [260]. Ive repeated the process several times.
Is this the normal course to take or should the "SD Method" (with the WM5 or WM6 RUU.. file) complete the process to a working OS?
Q3: Is my situation hopeless? ATT will take my out of warrantee 8525 and reflash for $129. Reading the threads it seems that like me this can be done by me, this is my desire.
Q4: I still am confused by some basic terms and assumed steps. I dont understand "Hard SPL" or OLI's IPLs/SPLs and when and when to use them.
The newbe guide has been off line. I will look again. Is there a single place to read about "radio PDAs and the 8525 and understand the software build and custom options?
Sy for the long post. But still want to fix if possible or I will be force to mail in for ATT repair.
Thank you all.
blackdog9692 said:
Q4: I still am confused by some basic terms and assumed steps. I dont understand "Hard SPL" or OLI's IPLs/SPLs and when and when to use them.
Click to expand...
Click to collapse
Oh boy, you haven't installed HardSPL? You are walking a bit of a line there mate...
HardSPL is a custom boot loader that makes bricking your phone when flashing much harder to do, and helps large amounts in the recovery process if you phone does brick.
Does the phone boot at this point? If so, do not try flashing the phone again. Go get a copy of HardSPL and install it, then try flashing from the SD.
I still wonder why people didn't read before bricking...
Anyway, you should start reading now and wiki is your friend. Your SPL is 2.03, so look at the bottom of the page (there is only one solution till now, so good luck with that):
Code:
1. Boot OS using KITL+PB
2. Do no disconnect your HERMES till the end of the step 6
3. Download SSPL on HERMES by wifi from ie explorer
4. Launch SSPL then flash Hard-SPL from your computer
5. Put your hermes in bootloader mode
6. Flash any radio in NBH format from your computer
Still researching and working this bricked 8525
Thanks for coming to my aide. I believe that I have Hard SPL'd my device. I downloaded Olipro's Hard SPL v7. extracted the RUU_ file and renamed to hermimg.nbh.
I then put it on an SD card and held the keys and reset. The device displayed a white screen and "Loading..." appeared. Afterward the 8525 returned to the stipped boat loader screen and that is where I am now.
Some of the help i receive and read on wiki threads has me confused with what to do next and how "exactly" to do it.
It does seem that I am not alone and people have fixed their phones and the process to do this is on the forum. I'm just still missing something.
Help me further if u can.
Thank you.
blackdog9692 said:
Thanks for coming to my aide. I believe that I have Hard SPL'd my device. I downloaded Olipro's Hard SPL v7. extracted the RUU_ file and renamed to hermimg.nbh.
Click to expand...
Click to collapse
FYI: bad form to PM someone and post the same thing here. Keep it in the thread so others can be helped as well.
As I replied in the PM, if I'm understanding your post correctly, the phone boots to the tri-colour screen?
What text is showing on the screen? This will tell if HardSPL is on the phone or not.
jdc said:
What text is showing on the screen? This will tell if HardSPL is on the phone or not.
Click to expand...
Click to collapse
We already know that the phone is without HardSPL, according:
My display reads:
HERM100
IPL-1.04
HERM100
SPL-2.03
This is where my journey ends.
Click to expand...
Click to collapse
There is small chance (read my previous post) to unbrick device with SPL2.03 so better try to get this back from where you take it.
And please, change topic, because this brick isn't HardSPL fault at all.
Edit: oh dear, it's even not your topic ...good game, I'm off
Hi All,
I had on my Athena the previous Michy Rom (2.04 with SPL 1.20) and when I saw the new version (4.00 with SPL 3.5):
http://forum.xda-developers.com/showthread.php?t=411371
I decided to install it. Like an idiot, I did not pay attention to the fact the SPL was different... I started the flash process and when I realized my error, it was too late.
The upgrade did not completed (as expected :-()) and now I am stuck with a corrupted bootloader screen, so I can't proceed (the device does not boot so I can't access ActiveSync).
Any way forward? Thanks for any hints!
Anubis
Update - I just tried this:
http://forum.xda-developers.com/showthread.php?t=326953
but without success. I get an Error [260] and the entire process stops.
Anubis1965 said:
Hi All,
I had on my Athena the previous Michy Rom (2.04 with SPL 1.20) and when I saw the new version (4.00 with SPL 3.5):
http://forum.xda-developers.com/showthread.php?t=411371
I decided to install it. Like an idiot, I did not pay attention to the fact the SPL was different... I started the flash process and when I realized my error, it was too late.
The upgrade did not completed (as expected :-()) and now I am stuck with a corrupted bootloader screen, so I can't proceed (the device does not boot so I can't access ActiveSync).
Any way forward? Thanks for any hints!
Anubis
Click to expand...
Click to collapse
look here
http://forum.xda-developers.com/showthread.php?t=405814
lakeman said:
look here
http://forum.xda-developers.com/showthread.php?t=405814
Click to expand...
Click to collapse
I have seen that thread. But the problem is different. I have also tried to reload a vanilla WM6 ROM but I cannot go past the corrupted bootloader part...
Anubis
Anubis1965 said:
I have seen that thread. But the problem is different. I have also tried to reload a vanilla WM6 ROM but I cannot go past the corrupted bootloader part...
Anubis
Click to expand...
Click to collapse
When you are in bootloader(three coloured screen) what do you see?
remove sim and sd card , hold camera button all the way in and press the reset button(on the back close to the battery cover)
If you see in bootloader mode ID showing somenting different than ATHE100 the solution is HERE http://forum.xda-developers.com/showthread.php?t=405814
I had the same problem! whell restart your pc and then connect the device to it. now start flashin an spl 1.20 rom. i did it and it worked! I hope i works for you too.
Cheers, Hirad
lakeman said:
When you are in bootloader(three coloured screen) what do you see?
remove sim and sd card , hold camera button all the way in and press the reset button(on the back close to the battery cover)
Click to expand...
Click to collapse
Thanks - already tried!
When I reset/hard-reset the phone (tried many ways) I see a garbled boot image (with random pixels here and there)... It is definitively not the usual bootloader with the information about the various ROM components and the "USB" text at the bottom.
Anubis
Solution!
I managed to do the same thing - had an old AP ROM with SPL 1.2 already installed then earlier today I tried to upgrade to the new Mitchy R4 SPL 3.5. I thought my Ameo was bricked, but after some pain it is now working again.
Here is what I did:
1) Enter bootloader mode using the very tricky Camera+Volume+Reset method.
2)
Follow exactly the steps in post 33 here:
http://forum.xda-developers.com/showthread.php?t=387454&highlight=mtty&page=4
Note, I'm running Vista so to get the USB option to show in MTTY, I had to first open "Windows Mobile Device Center" in Control Panel then disable the USB.
Also, note you should find your MAC under the battery flap.
3) Now all you need to do is reset, enter the bootloader mode again, and re-try the ROM (PS, make sure you use the correct SPL version!
Hope this helps.
spoonter said:
I managed to do the same thing - had an old AP ROM with SPL 1.2 already installed then earlier today I tried to upgrade to the new Mitchy R4 SPL 3.5. I thought my Ameo was bricked, but after some pain it is now working again.
Here is what I did:
1) Enter bootloader mode using the very tricky Camera+Volume+Reset method.
2)
Follow exactly the steps in post 33 here:
http://forum.xda-developers.com/showthread.php?t=387454&highlight=mtty&page=4
Note, I'm running Vista so to get the USB option to show in MTTY, I had to first open "Windows Mobile Device Center" in Control Panel then disable the USB.
Also, note you should find your MAC under the battery flap.
3) Now all you need to do is reset, enter the bootloader mode again, and re-try the ROM (PS, make sure you use the correct SPL version!
Hope this helps.
Click to expand...
Click to collapse
You are right and this is what sergiopi and I were referring to , specifically this post
http://forum.xda-developers.com/showpost.php?p=2154726&postcount=33
We were refering to the whole thread so you could learn the background.
However you are incorrect in your advice about how to enter bootloader
All you need to do is hold in the camera button and reset
spoonter said:
I managed to do the same thing - had an old AP ROM with SPL 1.2 already installed then earlier today I tried to upgrade to the new Mitchy R4 SPL 3.5. I thought my Ameo was bricked, but after some pain it is now working again.
Here is what I did:
1) Enter bootloader mode using the very tricky Camera+Volume+Reset method.
2)
Follow exactly the steps in post 33 here:
http://forum.xda-developers.com/showthread.php?t=387454&highlight=mtty&page=4
Note, I'm running Vista so to get the USB option to show in MTTY, I had to first open "Windows Mobile Device Center" in Control Panel then disable the USB.
Also, note you should find your MAC under the battery flap.
3) Now all you need to do is reset, enter the bootloader mode again, and re-try the ROM (PS, make sure you use the correct SPL version!
Hope this helps.
Click to expand...
Click to collapse
Thanks - you are giving me some hope! I am on a business trip now and my Athena is at home, but I will try that as soon as I am back
Anubis
Purchased the Raphael in Hong Kong, it does not have SIM lock.
It was HARDSPL by myself, done.
Then I flashed other rom - just OS, and the phone worked well. Yesterday, I saw the screen stayed on TRI colors, I made soft reset for couple time, the device is able to load Windows. Thus, I thought the ROM - OS is not good, so I flashed other ROM (OS) bt micro SD card, and it said the job was done and succeed.
But the phone cannot enter Windows anymore, just stayed on the TRICOLORS screen.
What can I do?
Thanks!!
Did you try a hard reset?
did you used the right hardspl?
because there are olso different for wm 6.5
greetz
n3m3s1s said:
did you used the right hardspl?
because there are olso different for wm 6.5
greetz
Click to expand...
Click to collapse
What? HardSPL is HardSPL. It's device specific, not OS specific. As long as his device has been HardSPL'd he's good to go. shgman, when you're at the tricolor screen, connect the phone to your computer. You can't use activesync so don't try. At the bottom of your screen, does it say USB? If so, try to flash again. Sometimes I get incomplete flashes from my SD card.
silentP said:
What? HardSPL is HardSPL. It's device specific, not OS specific. As long as his device has been HardSPL'd he's good to go. shgman, when you're at the tricolor screen, connect the phone to your computer. You can't use activesync so don't try. At the bottom of your screen, does it say USB? If so, try to flash again. Sometimes I get incomplete flashes from my SD card.
Click to expand...
Click to collapse
SlientP, I agree with you. HardSPL is hardSPL, then OS is OS. Yes, the device is able to Laptop while the USB cable is plugged in, the bottom of screen - white area say USB.
I had downloaded official ROM from HTC Hong Kong, and tried to flash the device back to factory default, the package is including Radio, done again. But......... the screen is still stayed at TRICLOLOR screen.
Thanks, shgman
I appreciate somebody who can help me?
I remember having a corrupted ROM install and had to manual enter into the bootloader. From there I was able to flash from my computer just fine... Wanna try that?
Try flashing stock rom then flash custom rom. It the custom rom fails again then its a bad rom or hardspl is not working right.
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).