Database Users

nothing work afrer update

i want update radio update but its locked at %10 then i restarted
and i want to enter bootloader but nothing come to screen. no power no bootloader!
how can i solve this problem...

albetratz said:
i want update radio update but its locked at %10 then i restarted
and i want to enter bootloader but nothing come to screen. no power no bootloader!
how can i solve this problem...
Click to expand...
Click to collapse
You should have read the instructions before trying the upgrade. ROM upgrade goes first, then the radio stack. I don't know if there's something you can do yourself to fix your device, or if you need to have it reflashed by your supplier. Anyone else?

bamse said:
albetratz said:
i want update radio update but its locked at %10 then i restarted
and i want to enter bootloader but nothing come to screen. no power no bootloader!
how can i solve this problem...
Click to expand...
Click to collapse
You should have read the instructions before trying the upgrade. ROM upgrade goes first, then the radio stack. I don't know if there's something you can do yourself to fix your device, or if you need to have it reflashed by your supplier. Anyone else?
Click to expand...
Click to collapse
Hi,
Seems like you are another of the many victims who got problems
after trying to upgrading new ROM & Raidio stack. Hope you still
got that warrant and get it replaced with a new one. Otherwise
you might have to try what some crazy guys do here trying to fix
it by doing all sort of bootloader etc.. Hope those who are trying
to get the upgrade ROM and Radio stack be very careful and make
sure your device are from the same supplier or distributor where
you got the new upgrade. Otherwise it will be screwed. Dont learn
your lesson the hard way.

same problem here.
i've got the O2 NL XDA
downloaded the 3.15 and radio updates from O2 NL website
installed updates as per instructions
1st update went without a hitch
2nd update totally screwed my xda.
now it takes a long time to start up, and when it does it just displays a white screen with a blue taskbar.
tried the bootloader way of flashing the rom, but still no luck
luckily I can send it back in to O2 to have it fixed.
I may try to do it by backup up another XDA, and reflashing mine.

Same prob with me..
I've got exactly the same problem. I downloaded the Rom update 3.15 and the new radio update. First I installed teh Rom update and after a hard reset I "installed" the radio update.
While updating the XDA hang and I waited for about ten minutes to see if the XDA was really hanging. I gave the XDA a hard reset but then the XDA didn't work anymore (white screen and blue bar on top).
I can still access the bootloader. I installed a Rom from a XDA which still works. Still no difference. When I tried to write the Radio rom to a sd-card I got that message that I have to connect one or another RS cable.
The XDA still doesn't work anymore. I have contacted O2 but they told me that they couldn't help me because they can't find my IMEI number in their system. I contacted the company where we ordered all the XDA's but I still don't have an answer.
Thank you O2 for being so nice with not helping me out with my one week old XDA without any scratch. I hope my XDA could be replaced as soon as possible since the XDA will not sold anymore when O2 changes to Telfort !

If you can make the ROM update work, you should be able to install the corresponding radio as well.
Try this:
1. Make sure you have the latest version of ActiveSync (=3.6)
2. Make sure the battery is fully loaded.
3. Extract the ROM update and Radio update to different folders.
3. Connect the cradle to AC-adapter and computer.
4. Put the device in the cradle and make sure it connects to ActiveSync.
5. Run the ROM installation application. Should take 5-6 minutes.
6. Run the radio installation. IMPORTANT: When you are prompted to remove power supply, pull the power plug from the cradle. If you do not disconnect power, the update will fail. I think this update took a little more time than the ROM update, and the device may seem "dead" for a while.
Good luck!

Hy Guys.
Are there any news about the problem flashing the XDA?
Tried last night to update my XDA to the last Qtek-Versions (ROM 3.16.52.....)
ROM Update works fine, but after the RSU Update the phone didn't work any more.
Have the same white screen with the blue taskbar and the little keyboardicaon down the right side.
Entering Bootloader mode there comes the Error Message "GSM Error"
Nice screen is the qtek "Booting Screen".
It shows
G <empty>
R <empty>
3.16.52
Hope there are any other hints to resolv this problem.
Have anyone got some experiences with sending it back to O2 with an "unoffical" Softwareversion?
Or is there any posibility to change the ROM Version to an old (original) O2-RomVErsion?
Thanks for any help....
Regards
Stefan

Hi Stefan,
I would suggest to try upgrade you device with any XDA ROM version by bootloader's CE to SD backup/restore and after try again to upgrade RUU by PC.
I know that upgrading/degrading by bootloader is the more safety way to do it.
Regards,
Riccardo

Riccardo said:
Hi Stefan,
I would suggest to try upgrade you device with any XDA ROM version by bootloader's CE to SD backup/restore and after try again to upgrade RUU by PC.
I know that upgrading/degrading by bootloader is the more safety way to do it.
Click to expand...
Click to collapse
SD-Card Writer just orderd
But I don´t know if it will work. Since the Bootloader says GSM Error, I think there will be no other posibility to restore it.
Let´s wait for some days, hope and we will see.....
Stefan

N00b Needs help please! RSU upgrade issues...

Hello All!
I just got an XDA that has the oldest version of all three components. I was browsing the rom cooker last night and also found a RSU for 4.21 that i thought i could install (activesync install exe)... Oh boy what a mistake!
So now, after the "programme B" update that was in dutch was completed, i got a continuous pop-up in dutch that came up and stayed on every boot. I managed to remove the items from startup and i dont have that problem any more, but my radio does not work at all, and i cannot connect to active-sync to go back or try another RSU!!! It just seems that the usb on the device is messed up, as the PC tries to connect when i cradle it.
I believe my problem is that i did not use programme A first? i only discovered that program after screwing up the wallaby...
I am on my way to buy an SD card now to aid in the disaster recovery. In the meantime, if anyone would be so kind as to reply with a suggestion for fixing it, and how to properly update the components, i would Greatly appreciate it!
Thanks in advance, and i love the forum! Look foward to spending lots of time here

OK, so i found the GSM error thread and followed the instructions, but when trying to upgrade the RSU, i get the error: "Upgrade Failed! hit ok to reset device"
Any suggestions?

All Fixed! From zero to hero in a day!

gazorp said:
All Fixed! From zero to hero in a day!
Click to expand...
Click to collapse
How have you fixed it?
Maybe we can update the instructions....
Stefan

I followed the instructions here: http://wiki.xda-developers.com/index.php?pagename=Wallaby_HT_GSMError
The only difference is that i did not copy to the startup folder and ran the update manually from the windows directory. Allowing the upgrade to run on startup always caused a problem like you described

Error (262) for diamond2 wm 6.5

Hi,
Help me please just me and that happens to me the mistakes my God.... I had the original ROM version coming with my diamond2, put the upgrading and went well until the moment he arrived at 9% and restart the pda, re-install I think is normal, however the installation continued until k stopped in 18% and after a long time gave a notice of error (262) made the recovery as recommended and continues to give error ....
I do help me please

This just happened to me too
My phone was hardspl´d
It stuck at 18%, but no error message so far. Did you unplug your phone?

Read this:
http://forum.xda-developers.com/showthread.php?t=425913

I'm not sure. Have you flashed other roms before? Perhaps you have a bad download. I know the servers are overloaded from all of us geeks sucking down the WM6.5 rom... perhaps its bad.
What I normally do is put the phone in bootloader mode first by holding VolDown, while resetting the phone. This will give windows time to install the proper drivers and get situated. Once done, try flashing again.
I think 262 is a connection error. Probably driver related since you said you ran your stock rom. But check your cable. Make sure its secure and reliable. Next try another USB slot. If nothing else try a different computer... sometimes PCs just will not cooperate.

Thank you very much fighter, will try that.

I had Official 6.1 Asia WWE installed, HARDSPLed. Tried to upgrade to 6.5 on my computer and my laptop, nothing worked. Both stops at 9%, disconnects, comes back and stucks at 18% again. Had to go back to 6.1, this time it worked to bring phone to life.
My phone was bought in Taiwan.
Guess I am out of luck

I think the best way to upgrade is as follows:
1. Run the RUU_Topaz_S_HTC_WWE_2.16.405.4_Radio_Sign_Topaz_61.44tc.25.32_4.49.25.17_Ship.exe on your PC/laptop to extract and get the RUU-signed.nbh.
2. Copy the RUU-signed.nbh to topaz SD card and rename to topaimg.nbh
3. Upgrade new ROM from SD card.

I had the same 262 error as well, screen went blank for a second at 9% and finally freezez at 18% with the error message. Heres what you need to do:
Update your HardSPL to 1.83
Flash 6.5 again
????
Profit!

Hello,
already did everything you say and nothing. I liked to tell me where I can get the former Rom wm6.1 because meeting.
help me please

duongla said:
I think the best way to upgrade is as follows:
1. Run the RUU_Topaz_S_HTC_WWE_2.16.405.4_Radio_Sign_Topaz_61.44tc.25.32_4.49.25.17_Ship.exe on your PC/laptop to extract and get the RUU-signed.nbh.
2. Copy the RUU-signed.nbh to topaz SD card and rename to topaimg.nbh
3. Upgrade new ROM from SD card.
Click to expand...
Click to collapse
Would you be so kind as to enlighten me/us on how to extract the nbh file from the executable file.
Thanks

player911 said:
I'm not sure. Have you flashed other roms before? Perhaps you have a bad download. I know the servers are overloaded from all of us geeks sucking down the WM6.5 rom... perhaps its bad.
What I normally do is put the phone in bootloader mode first by holding VolDown, while resetting the phone. This will give windows time to install the proper drivers and get situated. Once done, try flashing again.
I think 262 is a connection error. Probably driver related since you said you ran your stock rom. But check your cable. Make sure its secure and reliable. Next try another USB slot. If nothing else try a different computer... sometimes PCs just will not cooperate.
Click to expand...
Click to collapse
How can u exit bootloader screen? Only by removing the battery or...?
Thanks!

I do not have with me the adapter card to do this
There is also a problem is that the pda now I do not go the menu with the three colors blue, green and red, until I have done a hardreset and nothing ....
at least I no longer ask the solution with the ROM 6.5 we only have as I had before ... and wanted my pda to work help me please

Little history for my friends with same problem here:
1. Bought Diamond in Taiwan with Chinese;
2. HARDSPL 1.33;
3. Install Asia WWE 6.1 ROM;
4. Try update Official WWE 6.5 ROM, no luck, remove battery and put back;
5. Reinstall Asia WWE 6.1 ROM, everything back to normal;
6. Update HARDSPL 1.83; Ask brother to donate
7. Install Duttys ROM or Official ROM works too

Hello,
I already installed the previous ROM with the 6.1 and everything was normal.
I tried to install again the OFFICIAL ROM 6.5 and the problem remains back to the error at 9% and 18% for the progress bar giving an error (262).
not understand some things as:
6. Update HARDSPL 1.83; Ask brother to donate
7. Install Duttys ROM or Official ROM works too
is there any solution?
can help me

Sorry:
1. install Hard-SPL 1.83.OliNex (http://forum.xda-developers.com/showthread.php?t=520312)
2. install 6.5 ROM or Cooked Rom.
It resets 9% again in Official ROM, but reconnects and go to 100% (no stop 18% again).
Dutty ROM no stop at 9% or 18%.

problem solved
thanks for the great help amazing
thank you very much

hello
the memory card is not me out with the official wm 6.5 ROM
what can I do to boot the card?? I have a diamond2
ah no problem of card pk started the card with the adapter to the PC and read it perfectly.
pesquisar

AntonyWatson said:
Would you be so kind as to enlighten me/us on how to extract the nbh file from the executable file.
Thanks
Click to expand...
Click to collapse
When you run the RUU, the RUU-signed.nbh will be extract temporarily to a folder in driver C:
(For me: C:\Users\Duongla\AppData\Local\Temp\pft51D9.tmp)
Just do a search and you'll find it.
And remember to HSPL to 1.83.

i have the same problem too
hello
i have a diamond 2
ihave olinex 1.83 from here http://forum.xda-developers.com/showthread.php?t=520312 and i can not install ANY wm6.5 rom!!! on the other hand EVERY 6.1 rom i have trie (5 different greek and english) work perfect?!?!??
any suggestions?
thanks

i had the same issue
i was running 6.1 (stock rom) which was hard spl'd
i had the same error kept going to 262 and haviong to be recovered
so i re hard spl'd with the latest one, and it worked fine after that,

Cannont update HTC HD2 Error [260]

hi guys,
im attempting to update my hd2 but cannont. i sync it with active sync, start the update and it changes the phone to the tri color screen, but immediately disconnects on the computer, and a 1 minute later i get the error [260] connection screen.
can anyone assist me with updating? i also heard there is a way to update from the memory card...that might be the best way for me if someone can help me with that. THANKS

trexxcrap2 said:
hi guys,
im attempting to update my hd2 but cannont. i sync it with active sync, start the update and it changes the phone to the tri color screen, but immediately disconnects on the computer, and a 1 minute later i get the error [260] connection screen.
can anyone assist me with updating? i also heard there is a way to update from the memory card...that might be the best way for me if someone can help me with that. THANKS
Click to expand...
Click to collapse
What are you trying to update it to?

secano said:
What are you trying to update it to?
Click to expand...
Click to collapse
the new update that came out a few days ago....

trexxcrap2 said:
im attempting to update my hd2 but cannont. i sync it with active sync, start the update and it changes the phone to the tri color screen, but immediately disconnects on the computer, and a 1 minute later i get the error [260] connection screen.
Click to expand...
Click to collapse
Here is a link to the error codes. Your error means you need to go back to SSPL before you can flash that ROM.
trexxcrap2 said:
i also heard there is a way to update from the memory card...that might be the best way for me if someone can help me with that. THANKS
Click to expand...
Click to collapse
Here is a link to my tutorial on how to flash via SD card.

i am having the same issue each time i attempt to update my rom. error 260.

jenelson said:
i am having the same issue each time i attempt to update my rom. error 260.
Click to expand...
Click to collapse
You are still using the original SSPL (Soft Second Program Loader) which will only accept official update ROMs.
In order to flash the custom ROMs available here, you will need to flash in a HSPL (Hard Second Program Loader).
I don't know if you are totally new to flashing ROMs or not, since you didn't say and your post indicator said that was your first post here, but I would advise you to be very, very careful. In the early days (last month, actually) a TON of people were bricking their phones because they accidentally downloaded the European ROMs for the 512Leo. Ours is the 1024Leo and only ROMs designed for our phones will work.

The phone I am using is actually a replacement from TMO. I was having issues with the original device I purchased.
How do I use a HSPL or whatever... I am slightly confused but I can catch up quickly...
Thanks.

same thing happened to me, what i did was i restarted the update without disconnecting the phone from the computer, and it worked.

nyaznteen said:
same thing happened to me, what i did was i restarted the update without disconnecting the phone from the computer, and it worked.
Click to expand...
Click to collapse
I encountered the same problem and it appeared that my computer was slow in "re-recognizing" the phone. For some reason, it had to reinstall drivers before continuing with the update. After the device was again recognized, I restartde the update (without disconnecting the phone) and it continued without issue.
I had been worried that the phone had become a paperweight when I saw the tricolor screen, but everything has been fine and the upgrade appears to have worked correctly.

jenelson said:
The phone I am using is actually a replacement from TMO. I was having issues with the original device I purchased.
How do I use a HSPL or whatever... I am slightly confused but I can catch up quickly...
Thanks.
Click to expand...
Click to collapse
Think of HSPL as your BIOS (it isn't, but it may help you to think of it as such). You don't have any control over the options, but you need it to load or install your OS. Installing HSPL is simply a matter of following the directions in the link that I posted last time: http://forum.xda-developers.com/showthread.php?t=653614
Once you have HSPL installed, you should be able to "flash" any ROM. Of course, this also allows you to flash ROMs that are not meant for your phone, so that's the danger behind it.
When you visit a thread that offers a ROM, it should either have instructions or a link to instructions on how to install. If it does not, a google search for "xda how to install a custom rom" should give you a million helpful links. (This is actually beyond the scope of this post so I won't go into details)
Hope this helped some...

Same problem but i have hspl?
not sure what im doing wrong here I've installed hspl 1.42 which was enough trouble for what seemed like a pretty straight forward job. now whatever i try to install all i get is error 260? on top of this i don't seem to be able to send message tho i can receive and the camera on my phone no longer seems to work?
i am a newbie but Ive been reading and clicking and trying to install stuff for hours and hours and so far all Ive managed to do is install hspl and reduce my phones usability.
i got windows mobile device center 6.1 tried it with and without allow usb connections.
my antivirus and firewall is off.
.net framework 4 installed.
tried different usb ports
ive tried installing Duttys_Leo_Sense_2.5_5.23569.5.5.0_2.14_Holy_Grail_576MB_V4.3_WWE and a stock rom
my computer has vista 64 on it.
im hoping im just being a bit dense here please help me i just wanna join in on all this flashing fun!!

mumbles85 said:
not sure what im doing wrong here I've installed hspl 1.42 which was enough trouble for what seemed like a pretty straight forward job. now whatever i try to install all i get is error 260? on top of this i don't seem to be able to send message tho i can receive and the camera on my phone no longer seems to work?
i am a newbie but Ive been reading and clicking and trying to install stuff for hours and hours and so far all Ive managed to do is install hspl and reduce my phones usability.
i got windows mobile device center 6.1 tried it with and without allow usb connections.
my antivirus and firewall is off.
.net framework 4 installed.
tried different usb ports
ive tried installing Duttys_Leo_Sense_2.5_5.23569.5.5.0_2.14_Holy_Grail_576MB_V4.3_WWE and a stock rom
my computer has vista 64 on it.
im hoping im just being a bit dense here please help me i just wanna join in on all this flashing fun!!
Click to expand...
Click to collapse
just for kicks did you try a different ROM, find another ROM that is Compatible and try it, not saying there is anything wrong with Dutty's , but could just be the download , but not sure since you tried stock too ...
You may need to reinstall HSPL3, if you tried to flash a stock rom, and even if it failed it could have removed HSPL ...
Also try plugging the USB cable into the back of the machine

error 260 1024hd2
Hey guys,
I am having the same issue although I may know the answer but not sure how to fix it. Prior to flashing chuckyRom, I installed HSPL but I don't think I installed the correct version (still worked). So does anyone think this entire problem is attributed to initially installing the wrong hard SPL. If so, how can this be fixed? android is running great on chuckyRom but it would be nice to use a rom that is used for more than running android.
Please help, I have been in misery trying to solve this for over two weeks now.
Error 260, T-mobile HD2

Error 260 during ROM update
I had the same problem and tried everything (?)
Finally I got it work.
After I started the update the first time, I got the message, driver was not installed successfuly ...blabla
I ignored the message, tried and the connection disconnected every time again.
At the end I used another usb port and it asked me to download the CDMA driver. After download and installation, the update was in 5 min. done

Snarksneeze said:
You are still using the original SSPL (Soft Second Program Loader) which will only accept official update ROMs.
In order to flash the custom ROMs available here, you will need to flash in a HSPL (Hard Second Program Loader).
Click to expand...
Click to collapse
He was trying to install the OEM rom. I'm doing the same and have the same issues.

Error 260 on Htc Hd2 running windows mobile 7
I cannot get data on my hd2 when I installed win7 so I wanted to downgrade the os back to 6.5 but I get Error 260 when I connect to my phone to my cpu via usb. Is there a work around?

Dizzle88 said:
I cannot get data on my hd2 when I installed win7 so I wanted to downgrade the os back to 6.5 but I get Error 260 when I connect to my phone to my cpu via usb. Is there a work around?
Click to expand...
Click to collapse
Put the phone into BootLoader Mode then connect to the PC. Run the ROM.

Error 260 connection in HTC HD2
Dear all;
i have this problem in windows 7 each time i connect my phone with pc it gave me error 260 , so when i connect the usb cable i choose the first choice sync not the default one storage and it worked for me .
Ahmed Hosni

thanks for the note
fred_up said:
Put the phone into BootLoader Mode then connect to the PC. Run the ROM.
Click to expand...
Click to collapse
First time flashing the radio and kept getting error 260 from CustomRUU.
Read so many threads and all say sync the phone with your PC and run CustomRUU. Nobody said to run it under BootLoader Mode.
This simple note helped a lot for a newbie like me.... thanks

Error [260]
Hello
I want to try to update my HD2 from 2.2 to 2.3.x but I always geht thr Connection error.
I´ve flashed my HD2 from Windows Mobile 6 to Android.
I thank you for your help.

Vogue refuse to flash a new rom

Hi all i try to flash wm6.5 rom to Vogue every time i have (error 270).
I try with different rom but same problem even when i try to unlocked with Vogue_unlocker_MFG_2.31 i have ( error 260).
It was wm6 before then i change it to wm6.1.

so 77 said:
Hi all i try to flash wm6.5 rom to Vogue every time i have (error 270).
I try with different rom but same problem even when i try to unlocked with Vogue_unlocker_MFG_2.31 i have ( error 260).
It was wm6 before then i change it to wm6.1.
Click to expand...
Click to collapse
Follow my upgrading guide. And just to be sure, re-download the unlocker. Also, try to use a windows XP computer to do this.
Good luck.

Hello my friend thanks for your help i re-downloaded the unlock and i have same problem.
Just when it says ( disconnect and reconnect ) i think i do it in wrong way can you please Explain it to me how and where to do that, thank you again.

so 77 said:
Hello my friend thanks for your help i re-downloaded the unlock and i have same problem.
Just when it says ( disconnect and reconnect ) i think i do it in wrong way can you please Explain it to me how and where to do that, thank you again.
Click to expand...
Click to collapse
You literally need to unplug the phone and then plug it back in... there is nothing special about that step
I would suggest that you read the whole guide first and try to make some sense out of it before proceeding as you may end up bricking your device otherwise.