Hello forum,
I have a problem with some kind of internal protection of Windows Mobile when I try to upgrade my SPL.
Following happened:
I started ROMUpdateUtility.exe, but when it tried to install a new SPL version, the Active Sync connection was aborted with error 246.
How can I fix this? Maybe manually starting in bootloader mode before Hard SPL upgrade? However, ROMUpdateUtility doesn't recommend that and my PC crashes in this case.
PS:
I have already read this thread: http://forum.xda-developers.com/showthread.php?t=351395
Related
Hello everybody
I recently bought a second hand QTEK 9100. It has following soft:
IPL 1.03
SPL 1.03.0000
GSM 1.410.0
OS 1.37.10
I want to flash it with any latest ROM upgrade but I always have following happening:
The utility starts propose the soft to flash and when doing the device shut down, the activesync on PC switch of and after a while the program gives error 260. I tried to reset device, restart PC change various ROM versions (1.** and 2.**) but nothing helps
What I'm doing wrong and can somebody give me a hand?
sailors_be said:
Hello everybody
I recently bought a second hand QTEK 9100. It has following soft:
IPL 1.03
SPL 1.03.0000
GSM 1.410.0
OS 1.37.10
I want to flash it with any latest ROM upgrade but I always have following happening:
The utility starts propose the soft to flash and when doing the device shut down, the activesync on PC switch of and after a while the program gives error 260. I tried to reset device, restart PC change various ROM versions (1.** and 2.**) but nothing helps
What I'm doing wrong and can somebody give me a hand?
Click to expand...
Click to collapse
You need to read quite a bit before you jump in with both feet.
To get you started have a look at these threads:
http://wiki.xda-developers.com/index.php?pagename=HTC_Wizard
http://forum.xda-developers.com/showthread.php?t=263116
http://forum.xda-developers.com/showthread.php?t=282498
http://forum.xda-developers.com/showthread.php?t=284292[/QUOTE]
I have G4 Wizard and i followed these steps http://forum.xda-developers.com/showthread.php?t=310831 only instead of soft SPL i done hard SPL. Iwanted to install XDA Mobile 6 ROM but when i want to install it my device restarts to bootloader mode and my update utility then cant find the device. Please help me.
[FIXED]
I think I've been a total idiot and messed up my HD. I hope there's a way to salvage the situation!
I was attempting to flash a 1.56 ROM so tried to downgrade to SPL 1.54; this was going along nicely until it encountered an error and tried to re-start the flash. Now the device is stuck on "Loading..." before begining the flashing process.
If I soft-reset the device, the SPL has changed to 1.54.0000 according to the Bootloader screen but it says "Upgrade ROM code error Please try again".
I've googled that error message and found a few hits but none of them presented a solution; just people asking this question.
Since that, I've tried to Hard-Reset but it brings me back to the same Bootloader error.
I've tried to flash a ROM but the device can't connect to Activesync to use the RUU_Wrapper and flashing via the BLACIMG.nbh on my SD card won't work either; it just goes back to the same Bootloader error screen and gets stuck on the "Loading..." again.
I've also tried to flash the new HSPL which is 1.56 capable but that suffers the same problem.
Anyone have any suggestions? Please? Never encountered anything like this in years of flashing my Blueangel and Tytn.
Full details from my bootloader screen:
RUUNBH
BLAC100 32M
SPL-1.54.0000
MicroP-Blackstone (LED) v6
Upgrade ROM code error
Please try again
Serial
Please use "Search" function before you posting a new thread.
http://forum.xda-developers.com/showthread.php?t=502167
That doesn't seem to be the same problem as the one I'm encountering. I found that thread via Google as I said I had searched in my post and flashing the stock HTC ROM that came with my device did nothing to solve the problem; 3 machines here, one running XP, one running Vista and one running 7 all fail to connect to the device to allow for any sort of flashing and flashing via an SD card does not provoke a response either.
--Edit--
Sorry - realised that my reply sounded a little stroppy! Blame it on the stress of having a possible brick on my hands! Thanks for the attempt to help but, like it says above, that solution hasn't worked for me
dom_mitchell1 said:
That doesn't seem to be the same problem as the one I'm encountering. I found that thread via Google as I said I had searched in my post and flashing the stock HTC ROM that came with my device did nothing to solve the problem; 3 machines here, one running XP, one running Vista and one running 7 all fail to connect to the device to allow for any sort of flashing and flashing via an SD card does not provoke a response either.
--Edit--
Sorry - realised that my reply sounded a little stroppy! Blame it on the stress of having a possible brick on my hands! Thanks for the attempt to help but, like it says above, that solution hasn't worked for me
Click to expand...
Click to collapse
Have you tried reading cRaCKwHoRe's guide for flashing 1.56 roms. Can be found in my signature. If you follow his steps, you should have no problems
dom_mitchell1 said:
That doesn't seem to be the same problem as the one I'm encountering. I found that thread via Google as I said I had searched in my post and flashing the stock HTC ROM that came with my device did nothing to solve the problem; 3 machines here, one running XP, one running Vista and one running 7 all fail to connect to the device to allow for any sort of flashing and flashing via an SD card does not provoke a response either.
--Edit--
Sorry - realised that my reply sounded a little stroppy! Blame it on the stress of having a possible brick on my hands! Thanks for the attempt to help but, like it says above, that solution hasn't worked for me
Click to expand...
Click to collapse
Hi, dom_mitchell1...did you manager to fix you HD ? I have encountered the "exact" same problem...I went from 1.56 to 1.54...and now I am stuck on the bootloader at "Loading...." If you have a fix...can you please let me know...and save my HD as well....thx
If you use USPL you will be able to flash everything you want.
Fallen Spartan said:
Have you tried reading cRaCKwHoRe's guide for flashing 1.56 roms. Can be found in my signature. If you follow his steps, you should have no problems
Click to expand...
Click to collapse
That's what I was following when things went wrong. Don't know what I did but during the downgrade process the flash "encountered an error" and had to restart....only it never did and just left me stuck in the bootloader with an error message.
It's fixed up now though and I'm running Dutty's shipped version quite happily. To fix it I tried different .msi packages from HTC and eventually one of them managed a successful flash. From there I was able to continue with cRaCKwHoRe's guide.
i had a similar problem i was upgrading to 1.56 so i to my thinking reverted to a stock rom them loaded 1.14 stock spl where my phone started showing the error screen i investigated and found that the stock rom id downlosded from the stock rom section must have been tampered with as the signarure was incommplete. so now the spl was reading 114000... as it was stuck in tri screen the data had loaded to my device it justxwasnt signed so wouldnt work i dowladed the appropriat 1.56 rom from htc which includdes the new 1.54spl started it and there i whent stock 1.56 rom with stock 1.54 spl. i than loaded olinexs new hspl im running vista so had to use the manual tool but othere than that installed ok.
i hope that helped in short as long as ur screen is reading a stock spl u can install an apropriat 1.56 rom from htc i belive the issue is caused by impropper signage of some stuff marked as stock here.
Hi Guys,
I have a Telstra branded Diamond, that Im trying to unlock.
I keep on getting the RUU 260 Error - device not connected.
I have followed some of the tuts and threads on what to do, but im a bit stuck. As nothing seems to help.
So, what I have done is - downloaded the newest ROM from HTC for the telstra phone and flashed it with that. It looks like it uses the same RUU as the HardSPL I downloaded, and it has the same error too.
I am using XP sp3, ActiveSync 4.5.
Cheers
Leaflet.
You try using this Hard - SPL from olipro?
http://forum.xda-developers.com/attachment.php?attachmentid=93362&d=1213719705
They are the Hard SPL's ive tried, the error occurs when I try to run the ROM Update utility. It stays on 0%, the screen on the diamond fades to black(!) and then it gives me the 260 : Connection Error.
I'd gotten all the way thru unlocking the CID, downgrading to IPL 1.? and loaded the TMobile ROM ... all good.. and then I tried to upgrade to WM6.?. Thats when my computer crashed at about 25%. All I've got now is is the RUU screen IPL 2.26 SPL ???
Whats a good place to start? Can I do a SD card ROM update?
Here's hoping...
If there is no normal spl version number shown, I think the spl is corrupt. I don't know if a sane spl is necessary for flashing firmware, but I'd try booting the device in the bootloader and then flash an original rom and see if it works.
If that doesn't work, it's probably bricked in a way that it can only be revived by connecting a JTAG cable; I don't know if anyone has ever done that with a wizard...
Hi...
What do you mean with "SPL ???" ?
Don't you remember the version when writing or the system doesn't recognize the version number?
Bytheway, probably you can start again with flashing simply killing the wcescomm.exe process.
Try and report what happens....
I hope you luck (I recently got a bricked wizard due to a problem in upgrading and a flat battery... but solved )
Pino