Related
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
Hi everybody
Yesterday i had a problem trying to upgrade my wallaby to radiostack 6.18 tu RSU 6.24.
When i was doing the upgrade with the rsu files and the upgrade was in 88% in the screen appears:
" Upgrade problem, please reset" (something like that :? )
When i did the reset i got the boot screen and in the corner only i get the ROM version. The radio stack dissapears and then im not able to have my wallaby works.
Then i get into the wallaby bootloader version 5.15 and i got the following message:
GSM-ERROR
I reset the device a lot of times and nothing. i think " god i lost mi phone"
and then reading posts and posts i solve the problem in this way:
1:- I cook a rom image in an sd card using Xtools and a card reader instaled in your pc.
2.- when you finish insert the sd card with the image, enter again bootloader by holding On/Off and doing a soft reset
3.- Bootloader should tell you something that OS is detected on your SD-Card
4.- Press Action Key to install the ROM
5.-After finishing do a hard reset
Now your ROM should be installed on your device.
6.- turn off your device, maybe you will have to press the power button several times.
7.- Remove your SIM card
8.- Turn on your device, wait about 15 minutes and you can see that the device goes out off that frezze screen and gets into the align screen setup.
9. When you get the TODAY screen connect your device in the cradle and make a new asociation for your device
10. get into the windows file with the explorer of activesync on your pc and copy the 4 radio stack files in the windows file of your deviceq and the .exe file in the \Windows\StartUp folder of your device.
11. Restart the device and the upgrade will begins automaticaly in the back ground
12. when it sucsesfully done, do a soft reset and you must have your radio stack upgrade done and your wallaby completly recovered.
13.- Insert your SIM card again and enjoy
I hope this guide will help you
Rememeber to copy the correct radio stack in your device, i used the RSU 6.24 because i have a PW10B1 wallaby. check your version in the label in the rear part off your device
[/b]
if this tip results succesfully to someone please let me know. thanks
Well done, not many people manage to repair corrupt/missing radio stack, thanks for the details also, it may help resurrect other dead Wallabys.
which RSU to use
hi,
mine is PW10A1 so which RSU to use
Re: which RSU to use
maddawood said:
hi,
mine is PW10A1 so which RSU to use
Click to expand...
Click to collapse
ftp://[email protected]/Wallaby/Radio_Stack/RSU_V4.16_PPC.zip
HTH
Stefan
which rom you used?
Re: which RSU to use
LumpiStefan said:
maddawood said:
hi,
mine is PW10A1 so which RSU to use
Click to expand...
Click to collapse
ftp://[email protected]/Wallaby/Radio_Stack/RSU_V4.16_PPC.zip
HTH
Stefan
Click to expand...
Click to collapse
That link isn't working at the moment - I could sure use it
Link should be:
ftp://xda:[email protected]/Wallaby/Radio_Stack/RSU_V4.16_PPC.zip
Stefan
Thanks Stefan - I saw elsewhere what the password was, and noticed it was missing from the URL. I got the RSU file and have finally managed to get it on to the XDA, but still fails every time it restarts... the old 1% problem... Do you know if it is easier to update the radio stack from an SD card? The XDA is running the special edition ROM, which has at least given me back some control of the device.
Thanks in anticipation
Phil
PhilHirons said:
Thanks Stefan - I saw elsewhere what the password was, and noticed it was missing from the URL. I got the RSU file and have finally managed to get it on to the XDA, but still fails every time it restarts... the old 1% problem... Do you know if it is easier to update the radio stack from an SD card? The XDA is running the special edition ROM, which has at least given me back some control of the device.
Thanks in anticipation
Phil
Click to expand...
Click to collapse
I have the same problem, every time my device restarts, and stop at 1%. So I am wondering if Stefan can help us to give us solution in this case.
Worth the risk?
After reading this ordeal, is it worth the risk to upgrade a working radio stack? Does the telephone work substantially better after the upgrade?
Try other RSU's
kinowong said:
PhilHirons said:
Thanks Stefan - I saw elsewhere what the password was, and noticed it was missing from the URL. I got the RSU file and have finally managed to get it on to the XDA, but still fails every time it restarts... the old 1% problem... Do you know if it is easier to update the radio stack from an SD card? The XDA is running the special edition ROM, which has at least given me back some control of the device.
Thanks in anticipation
Phil
Click to expand...
Click to collapse
I have the same problem, every time my device restarts, and stop at 1%. So I am wondering if Stefan can help us to give us solution in this case.
Click to expand...
Click to collapse
Hi, have you tried using other RSU versions? I had the same problem too (1% fail) using 4.16. After giving up on the 4.16, I tried RSU 4.21 (exe). One shot and I was able to re-flash my RSU. What I did differently was to remove the AC power while doing the RSU upgrade (the exe file prompted me). Hope you get your wallaby up and running again.
I try alot of times but it stop at 1% - full batery got the same result.
help.
Re: Try other RSU's
Thank you for your help. I have tried many vensions of RSU, such as 4.16, 4.21, 6.24, 6.25, etc. But all of them showed 1% mistake.
morph751 said:
kinowong said:
PhilHirons said:
Thanks Stefan - I saw elsewhere what the password was, and noticed it was missing from the URL. I got the RSU file and have finally managed to get it on to the XDA, but still fails every time it restarts... the old 1% problem... Do you know if it is easier to update the radio stack from an SD card? The XDA is running the special edition ROM, which has at least given me back some control of the device.
Thanks in anticipation
Phil
Click to expand...
Click to collapse
I have the same problem, every time my device restarts, and stop at 1%. So I am wondering if Stefan can help us to give us solution in this case.
Click to expand...
Click to collapse
Hi, have you tried using other RSU versions? I had the same problem too (1% fail) using 4.16. After giving up on the 4.16, I tried RSU 4.21 (exe). One shot and I was able to re-flash my RSU. What I did differently was to remove the AC power while doing the RSU upgrade (the exe file prompted me). Hope you get your wallaby up and running again.
Click to expand...
Click to collapse
Re: which RSU to use
LumpiStefan said:
maddawood said:
hi,
mine is PW10A1 so which RSU to use
Click to expand...
Click to collapse
ftp://[email protected]/Wallaby/Radio_Stack/RSU_V4.16_PPC.zip
HTH
Stefan
Click to expand...
Click to collapse
Hi guys i have a pw10a1 too, and my radio version is 4.21, i really think it sucks. so is it a good idea to downgrade to 4.16??? or will it only be made worse. or can i use the 6.25.02 version? or is that for another phone type.. PWIEW srry for all the questions .. if 1 is awnsered. i'm happy
I haven't done this before so I want to make it right for the first time.
My friends XDAIIi can not make calls (flight mode on all the time and can not be turned off) after WM6 rom upgrade (which I think was for Himalaya only) by some cell phone shop.
Now how do I upgrade the rom to a working one or at least put back the original rom?
What file/s do I need to download? I don't have a cradle just a USB for connecting to ActiveSync which I think serves the same thing as the cradle. Do I need to reflash it first? How do I do that? What files do I need?
Thanks in advance.
Help!
Anyone?
Okay after about an hour or so searching I found this rom -> http://www.maxishare.net/en/file/37...-1-04-bluetooth-patched-camera-fixed-rar.html but after completing the first stage (I guess because for a moment there a quick glimpse of Stage 2 dialog box) I will get this error
Error 113: Extended ROM Update Error
And I repeated the process aboput 10 times with no luck.
Anyone care to point me to another rom that I can try?
zxt said:
Okay after about an hour or so searching I found this rom -> http://www.maxishare.net/en/file/37...-1-04-bluetooth-patched-camera-fixed-rar.html but after completing the first stage (I guess because for a moment there a quick glimpse of Stage 2 dialog box) I will get this error
Error 113: Extended ROM Update Error
And I repeated the process aboput 10 times with no luck.
Anyone care to point me to another rom that I can try?
Click to expand...
Click to collapse
right i usualy flame ppl for this, but as it was not you or your m8s fault:
1- got here http://forum.xda-developers.com/showthread.php?t=306600 and download the firmware
2 - make sure the phone is Fully charged
3 - put the phone in its cradle on a PC that running xp home or pro ONLY it will not work on vista. helps if you have activesync (u can get it from M$) then follow the instructions with the firmware. the program u want is called maupgrade.
4 - it will almost definatly fail the first time you run the updater (if its inactive for more than 15 mins, nothing changing on the updater screen as it should say its updating somink or other), DO NOT PANIC!! close the updater and run it again it will say no firmware found or anything it will work perfectly this time.. total time for update is 30~ mins.
BANG u have a working phone again hopfully!
"1- got here http://forum.xda-developers.com/showthread.php?t=306600 and download the firmware" -> This has exactly the same firmware/file/rom as this right -> http://www.maxishare.net/en/file/37...-1-04-bluetooth-patched-camera-fixed-rar.html right?
Anyways I am still downloading it tho it has the same file name I downloaded 3 days ago. Just like what I've said I already tried it (maupgrade) and followed the instructions and I think I only finished the first stage then it gave me the Error 113: Extended Rom update error
How bout an original ROM? Maybe somebody can give me the link because most of the links I found for original rom's are dead already.
Thanks.
you ARE runing a pc that uses the windows XP operating system?
skeeve666 said:
you ARE runing a pc that uses the windows XP operating system?
Click to expand...
Click to collapse
Yes I am using XP. Anyones know where I can find original rom? Maybe I can try that.
BTW, just for the sake of seeing the whole process of rom flashing, I did upgrade my Himalaya (XDAII) last week to WM6 using rom for XDAII of course and it was successful. Now I only did that to see how it works but I'm sticking to WM6 for my XDAII but I still don't know what to do with my friends XDAIIi and revert it to working rom.
Hi, first post on the forum so please be gentle with me....
I have an XDA Orbit 2 which was until last Thursday working fine with the last official upgrade from O2 (Win 6.1, no idea about all the other stuff).
Whilst using the phone last week it suddenly died in the middle of a conversation. It wouldn't power on at all. I took out the battery, waited a couple of minutes, put the battery back in and switched it on. All that happened was the phone displayed the 4 colour screen with "POLA200 SPL-3.13.0000 CPLD-2" in the red section and "Serial" in the white. I repeated the battery removal exercise a few times, waiting for increasing lengths of time but nothing changed.
I had a fairly long search through the forum and have tried for a few hours now going through the various fixes suggested but I am getting nowhere.
It won't hard reset, all that happens is the message "No Image Found" appears for a very short time and I then get stuck on the 4 coloured screen with the message above.
The same thing happens if I try just putting the thing in bootloader mode.
I can't use any of the official O2 rom upgrades as the phone because all the PCs I've tried connecting to it won't recognise it over a USB link.
I've tried connecting to it using mtty, again on several PCs, but I just get a message "USB port can not open". Just in case I've uninstalled Activesync on one PC and got the same answer.
The "how to flash you polaris using the microSD card" originally looked useful but I have some problems with it.
The first is that I need HardSPL installing on the device, which I can't do because I can't get to it.
The second will be down to me not knowing where to look, but I can't find a ROM to download and copy to the microSD card as POLAIMG.nbh. I did manage to find a Win6.5 one (the HTC Polaris - PDaviet rom wm6.5 manilla 2d (core 23004) by tranminhman one) which I thought I'd try. I guess the idea was that if I could just get something working I could always reflash it again with a different ROM or maybe apply the o2 upgrade. Unfortunately the image was password protected and I couldn't find the password in the thread.
I'm kind of at a loss now so any help would be appreciated.
Cheers
Hey,
Sorry i can't help much you'll need to do a lot of reading and troubleshooting...usually it's the onyl way to solve it by trying all options.
I'm just posting this message to bump it up in this forum, but more importantly you should be posting in the Iolite section for help with that specific device especially if you're trying other ROMs.
Also if it died on you and you haven't begun to flash it, can't you send it to the service for them to fix it for you? That way you can rule out any hardware malfunction.
Best of luck!
Alan
Did you do soft reset
alanazar said:
Hey,
Sorry i can't help much you'll need to do a lot of reading and troubleshooting...usually it's the onyl way to solve it by trying all options.
I'm just posting this message to bump it up in this forum, but more importantly you should be posting in the Iolite section for help with that specific device especially if you're trying other ROMs.
Also if it died on you and you haven't begun to flash it, can't you send it to the service for them to fix it for you? That way you can rule out any hardware malfunction.
Best of luck!
Alan
Click to expand...
Click to collapse
Bit in bold er... cant quite understand why in iolite section as the xda orbit 2 is the rebrand htc touch cruise => htc touch find. Its in the right place.
On the side of what to do i the ony thing i can think of would be mtty and if that didnt work then try to reflash the official o2 6.1 release and see what happens when you try to do it.
You cant try to install any 3rd party roms they jsut wont flash as you dont have hard spl installed and cant do that until you have it running again.
Try the above and see what happens...
Hi Nik
I have tried just about every kind of reset, nothing has worked.
Hi Alan
If I can't get it sorted any other way I'll probably send it off somewhere but I'd like to have a go at fixing it myself. It will at least be a bit of fun!
I take then that I've posted this in the wrong forum. Oops, apologies.
Jon
You have not posted in the wrong forum look at my signature!
Hi jon,
Conclusion from post 1,
1) Uncompleted flash with new ROM or hardware problem (half way die)
2) Unsuccessful flash Hard SPL (cannot see Olinex 2.2 wording during bootloader)
3) Your PC & PDA fail to connect via USB (serial wording appear during bootloader)
Try this method,
1) Get shipped ROM from HTC web site, key in your country & serial behind battery
1a) Extract shipped ROM by WinRAR , take RUU Signed.nbh
2) Rename to POLAIMG.nbh put inside SD card, "flash using SD card"
3) Make sure your battery power more than 50% cause it take about 2 hours
Good luck, my friend
[Your request Password: TranMinhMan]
Nik Ahmad said:
Hi jon,
Conclusion from post 1,
1) Uncompleted flash with new ROM or hardware problem (half way die)
2) Unsuccessful flash Hard SPL (cannot see Olinex 2.2 wording during bootloader)
3) Your PC & PDA fail to connect via USB (serial wording appear during bootloader)
Try this method,
1) Get shipped ROM from HTC web site, key in your country & serial behind battery
2) Rename to POLAIMG.nbh put inside SD card, "flash using SD card"
3) Make sure your battery power more than 50% cause it take about 2 hours
Good luck, my friend
[Your request Password: TranMinhMan]
Click to expand...
Click to collapse
Thanks Nik
I've had a bit of a look round the HTC site and couldn't see a ROM to download so I've asked their technical support people if there's anywhere to download it.
Fingers crossed they'll help.
Jon
jonfsharp said:
Thanks Nik
I've had a bit of a look round the HTC site and couldn't see a ROM to download so I've asked their technical support people if there's anywhere to download it.
Fingers crossed they'll help.
Jon
Click to expand...
Click to collapse
Try to get official HTC ROM here, Select WWE (405) CID_001 for your country.
Good luck my friend
have u tried this?...
turn off, pull out the battery, then put it back, charge ur phone till the battery indicators shows green (which mean it's already fully charged) then... power on ur device.
it looks like a dumb suggestion , but... i have had a same situation
(HTC KAISER, not Polaris).
if it doesn't work, then try to upgrade with a POLAIMG.nbh (take it from official HTC ROM)
in a 2G FAT32 microSD root directory.
Nik Ahmad said:
Try to get official HTC ROM here, Select WWE (405) CID_001 for your country.
Good luck my friend
Click to expand...
Click to collapse
Thanks Nik
Much appreciated.
Downloaded the ROM as suggested, unzipped to the SD card, renamed the image to POLAIMG.nbh, stuck it in the phone and things got slightly more interesting.
In bootloader mode I now get a bit further. I get a grey screen which says "Loading ..." then "Checking...." then "00028002 Not allow". It then goes back to the four coloured screen as before.
However, does the fact that it is trying to read something mean that I have just got the wrong file?
I'll try a few more and see what happens.
Thanks once again, your help is greatly appreciated.
Jon
Hi oza
Yep tried all the battery pulling out stuff but got nowhere.
The ROM thing on the SD card gets further. I extracted the ROM from the official O2 upgrade, stuck it on the card and renamed it POLAIMG.nbh.
If I put the phone in Bootloader mode I now get even further than before. I get a grey screen with:-
POLAIMG.nbh -
RADIO_V2 -
BOOTLOADER -
SPLASH1 -
OS -
Press power button to start update image
Press action button to cancel update image
If I press the power button
I get an "Update In Progress" message and a progress bar.
After about 4 minutes I get a full progress bar and :-
POLAIMG.nbh - OK
RADIO_V2 - OK
BOOTLOADER - OK
SPLASH1 - OK
OS - OK
Update complete
UPDATE SUCCESS
And that's as far as I've got so far.
If I take the SD card out and try a hard reset I just get stuck on the 4 coloured screen I got before, but with no No Image Found message.
I get the same thing with bootloader mode and when I just remove the battery.
If I put the SD card back in I can go through the update process but I can't do anything
else.
So, have I actually made any progress? I'm not actually sure what I have updated and what state the phone is in at the moment. Is the fact that this didn't work an indication of a hardware failure and I should send it off somewhere.
Any advice on next steps would be good.
Jon
what is ur bootloader screen says now?
IPL...
SPL...
Before you can be helped you need to supply this information:
What rom were you using when it died?
What SPL are you using?
You used MITTY and fixes so I assume you're not a complete nunce and have hard spl on your phone, so on that assumption and ONLY if you have hard spl on your phone, try this:
If it isnt a hardware problem, then Its possible you have a dodgy radio flash issue - normally that would have been caused by a bad flash, but you indicated that this happened in use.
Provided it isnt a hardware, to fix this you need to either flash the radio (less reliable, but try it) rename the radio file to POLAIMG.nbh as directed before and stick on SD card.
The other thing to try is to flash a rom with a radio INCLUDED in it. Try and avoid fancy 6.5 beta roms and stick to 6.0 and 6.1 basic roms.
I believe Chavonbravo's VLIT roms come with the radio so try that. Its listed in the forum. I'm not providing links as I dont know what radio you were using and you really need to go for like to like or close. My preference is 1.59.44.02 radio rom if you find one.
Let us know how you do.
Lastly what radio and rom did you have?
Try this one M-AMINES if the radio you had was a 1.59.xx radio as it has the radio included.
if it was a 1.65.xx radio then try the VLIT naked rom.
oza_crazy said:
what is ur bootloader screen says now?
IPL...
SPL...
Click to expand...
Click to collapse
Hi Oza
Exactly the same as it did when it first broke. I get the 4 coloured screen with "POLA200 SPL-3.13.0000 CPLD-2" in the red section and "Serial" in the white.
No idea what the IPL is or was I'm afraid.
Jon
bally3 said:
Before you can be helped you need to supply this information:
What rom were you using when it died?
What SPL are you using?
You used MITTY and fixes so I assume you're not a complete nunce and have hard spl on your phone, so on that assumption and ONLY if you have hard spl on your phone, try this:
If it isnt a hardware problem, then Its possible you have a dodgy radio flash issue - normally that would have been caused by a bad flash, but you indicated that this happened in use.
Provided it isnt a hardware, to fix this you need to either flash the radio (less reliable, but try it) rename the radio file to POLAIMG.nbh as directed before and stick on SD card.
The other thing to try is to flash a rom with a radio INCLUDED in it. Try and avoid fancy 6.5 beta roms and stick to 6.0 and 6.1 basic roms.
I believe Chavonbravo's VLIT roms come with the radio so try that. Its listed in the forum. I'm not providing links as I dont know what radio you were using and you really need to go for like to like or close. My preference is 1.59.44.02 radio rom if you find one.
Let us know how you do.
Lastly what radio and rom did you have?
Click to expand...
Click to collapse
I've not been a big modifier in the past so it was just using the bog standard O2 software from the O2 website. The name of the file is "RUU_Polaris_O2_UK_3.13.206.0_radio_sign_25.85.30.07_1.59.42.15_Ship.exe" so I presume that there can be information gleaned about things like the SPL, ROM and radio versions?
Not a complete nunce, no, but so very far away from being comfortable with all this. This post was a result of a good few hours trawling through the forums looking for help. Anything I have done has been the result of a post on this site and I am very grateful that there are people willing to share their knowledge.
Anyway, as for hard spl, nope it isn't installed. I'd never needed anything like it before the phone died and now that it has died I can't get onto it to install anything.
Yes, this happened right in the middle of a conversation after a good year or so of normal day to day use. As I said, I haven't needed to make any changes to the phone so the only thing I've ever done is upgraded it with software from the O2 site.
I'm beginning to suspect that without Hard spl my options are very limited and pointing towards either sending it off for costly repairs or just binning the thing. I am probably wrong but I'm guessing that the fact that I don't have it installed is the reason why nothing is happening with the "Update in progress" stuff that is happening now.
Radio & ROM, as above. Whatever the O2 update provided. From the filename radio would be 1.59.42.15.
Many thanks
Jon
jonfsharp said:
I'm beginning to suspect that without Hard spl my options are very limited and pointing towards either sending it off for costly repairs or just binning the thing. I am probably wrong but I'm guessing that the fact that I don't have it installed is the reason why nothing is happening with the "Update in progress" stuff that is happening now.
Radio & ROM, as above. Whatever the O2 update provided. From the filename radio would be 1.59.42.15.
Many thanks
Jon
Click to expand...
Click to collapse
Well whatever you do dont bin it, we can always use it on the Android project if you decide to go that way.
Ok.. so lets see.. the phone is not picked up at all in windows?
If that is the case, if even a serial connection cant be made then theres issues. At this point, I would disregard all the other advice as it only applies to a hard spl device unfortunately. SD card flashing and all other radio rom flashing will only work with hard spl as far as I know - definitely safer for certain and you dont want to wreck a repairable device.
I take it, its not under warranty, for your mention of costly repair.
The important thing at this stage is a serial or usb connection from a Windows PC. I think I have heard of forcing this connection by opening the device but this would really be in the realms of profficient repairer or enthusiast.
I'll have a look but also do some searching yourself for making a connection to a Windows PC and forcing an SPL onto a phone.
I dont know whether anyone's ever managed to HardSPL a phone using a memory card? Just a thought...
Who would have known.. have a read of this and see if you can follow it up regarding the spl through sd card ..
http://forum.xda-developers.com/showpost.php?p=3273438&postcount=7
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.