I'm hoping someone can offer me some advice as I'm new to this... I thought I'd done plenty of reading and knew what I was doing, but I appear to have fallen at the first hurdle...
I've downloaded pof's artemis_USPL, and followed the instructions to the letter, however everytime I run it, I get the DOS screen which appears to finish successfully (while my phone's screen goes black with the linux penguin on it, and 'WELCOME TO HARET' written below it). The rom update utility then launches, and I click through the wizard, but at this point my computer loses connection to the phone (while the modeless dialog saying something like 'inspecting moblie device's configuration' is displayed on the computer). ActiveSync also terminates itself when this happens. The Rom update wizard then reports Error [260]. I've looked this up on the RUU_Errors page on the wiki, and it says I should use softSPL. Do I need a specific version of this for the Artemis? And am I likely to have any more success?
Any suggestions would be greatly appreciated!
Thanks guys.
be a bit specific about your PC......what OS u r using?
I was plagued with error 260 for months. Resolved it by reinstalling activesync. This may not be your issue, but have a go.
See post no.14 here
Assuming that you have a error which is similar to what I had, this is what i did ...hard reset.. holding the two keys between the call and end button Press the reset ..keep holding the two soft keys and then when the screen comes on asking for a input release the two softkeys and press the call button, the do the entire process again starting with uspl
Related
Hi,
I am in the process of upgrading my rom using the rom upgrade from the o2 www site.
Its been stuck on the
'checking the information on your device....Please wait.....Please do not disconnect your device from the PC or power supply until the upgrade is complete'
window for some time now. I dont know if its hung / crashed or in the middle of upgrading.
I dont want to chance it by removing the unit from the sync cradle but at the same time i dont wanna just leave it there for hours if its not doing anything.
Can anyone help ?
Steve
ps - the window I am speaking about came after the big window stating what your current rom / radio stack was and what they would be updated to giving you the option to click 'update' or 'cancel' I chose 'update' and got the message which I described earlier
Try this on a different PC...I'm assuming the phone itself is still functioning.
I had this a while back with the XDA2 and found that by attempting the upgrade on a laptop I had, it worked great without the hang.
I would then remove ASync completely (including registry items) and then reinstall it.
Cheers
Ant
I had this happen, I just shut down and restarted the installer program
I guys, I've tried upgrading my JasJar with Xda_Exec_Upgrade_v1.30.162, using MaUpgradeUt_noID and when update was complete I cannot load my JasJar anymore. I am using hard reset, but when choosing "0" off the boot screen - noting happens and screeen remains black.
Can someone please help me with this issue?
Thanks a lot in advance,
Best regards,
Stazik
Try reflashing it again. If it does not work, try reflashing back to the i-Mate ROM.
Whats the version of your bootloader (the screen with serial at the top changing to usb when plugged into usb)? If it is 0.56 or something else below 0.6 thats an already known problem.
I had similar problems with my O2 upgrade.
Try:
- Turn off USB in ActiveSync
- Hold Power/Light and press reset button
- Run the upgrade again
Thank you very much for help and support, guys!
When I try flashing my JasJar with Bootloader update or JASJAR_WWE_13076_164_10900_wwe_ship I get the same error message: Error 101 Connection Error. And also when I disable ActiveSync USB and plug my Jasjar into USB - I get a message from windows saying the device was not recognized...
The only I can get from JasJar is a black screen, except when I press two soft buttons and reset - that gives me a screen with 0 and x to choose. Neither of choices helps thou.
Any help is appreciated. Thanks a lot.
you didnt answer the question re the boot loader number.
when your screen is grey or starting to reset, there are numbers on the screen. what are they.
if it is less that 0.6 your in trouble and assistance is different to if your boot loader is 1.0 or similar.
My screen doesn't change from gray except when I do hard reset. And then I hit two buttons and reset, then press 0 the message Clearing now appears and then everything returns to gray again.
How can I tell the version of bootloader in this case?
Thank you in advance!
they are hard to see, if the screen is grey, the numbers are black.
f the screen is blue/coloured, the nmbers are probably red.
Thanks for help guys,
I brought my JasJar for service today, somehow they were able to put older ROM in there. Now I've upgraded bootloader, hopefully newest ROM from i-mate going to fit without problems )
Well I've killed my Jasjar upgrading I was installing the bootloader update. It sat there saying "Checking information on your device" for about 30 minutes after the update started (notes said it would take 10 so I figured something was amiss - disconnected & rebooted my PC.
Now when I turn the Jasjar on I get the USB/Serial screen referred to above and (good news I figure) it has v1.00 at the bottom. How do I fix this?
TIA
Sheesh. I did a search (I know I should have done that first) and found the answer here
Took a while to find a copy of mtty to download, but found that at http://buzzdev.net
Once I'd done the Set 14 0 and tried the boot loader update again it took seconds so something definitely went wrong the first time.
Firstly I would like to say thanks to this site and the trinityguides.info site for the great work people have being doing and making available to everybody, it is great being able to use my trinity with wm6, keep the good work going!
Now the issue I seem to be hitting the same "error [260] connection" every time I attempt to update anything on my Trinity. I have followed the advice on the trinityguides site regarding being stuck in bootloader mode to no avail, and I can't seem to find anything in the posts on the xda site which will rectify the issue.
Previously I have been able to update to AX3L v2.8.01 version without any problems, but I decided to update to sammy's ultra light, it initially kicks into des' crashproof sspl, but then it can't connect to the pc. even when I manually enter olipro's hard-spl it does the same. I have tried to re-install hard-spl, but can't. Disconnecting the usb option in the activesync settings doesn't do anything either. Does anybody have any suggestions for me please?
I am not even too sure if my trinity should have both Des' crashproof and hard-spl on it at the same time? Could someone advise me on whether this is alright please?
the tech details:
Trinity
AX3L_OS_v2.0.8.2
radio - 1.46.30 (even though it doesn't say this in the device info, or boot screen after soft reset)
Home PC - XP (just in case)
Did you also try flashing it again, the ROM I mean. I have this error also but as soon as I execute the ROM flash again it finds the device and starts flashing:
http://forum.xda-developers.com/showpost.php?p=1449597&postcount=2
I am assuming you mean flash with the new ROM, sammy's in my case?
yes, as described in the link I posted before. As soon as the error occurs, do not touch the phone, leave it, just start the ROM flash procedure again. (execute ROMUpdateUtility.exe)
No, I am in the same situation. The first attempt puts the device in 'ipl-sspl by des' bootloader mode then after about 10 seconds or so the error[260] is displayed on the pc. If I exit the ruu app and attempt again, nothing new happens on the trinity (i.e. it is still in Des bootloader) and the message is displayed again.
the thing is that when it first goes into des bootloader mode, the white strip doesn't have any text in it. If I pull the usb cable out then put it back in, 'serial' is then displayed in the white bar, but I am still in the same situation as before.
What operating system en activesync are you using?
On the PC I am using XP and Activesync 4.5
Check your connection settings to accept USB connections. Also, try using Hard-SPL 1.30 before flashing the ROM again.
deejacker said:
the thing is that when it first goes into des bootloader mode, the white strip doesn't have any text in it. If I pull the usb cable out then put it back in, 'serial' is then displayed in the white bar, but I am still in the same situation as before.
Click to expand...
Click to collapse
In your PC, try another USB connection.
BLOODY HELL!!! It is the simplest things which we often forget to try. Thanks Jotam for pointing out an obvious point, it must have needed a re-plug of the usb cable into another port for the pc to pick up the device again. I will remember that for future updates so I don't make a dumb ass of myself again. Thanks guys/gals.
Vista
Using Vista? if so which version?
Hi I asked this question yesterday, I am a noob :-[ but the only difference is I'm using Vista Ultimate.
Just for others who have the problem.
When you replug into another USB port (Luckly I've got two on my laptop..)
I used the Vista drivers from TrintyGuides and bingo !
now I try and flash a WM6.....English or Italian...maybe French.
Thanks for the help I keep you posted.
Richard
It works
Now to discover the joys of WM6 after only having WM5 for two weeks....
/i am getting the same only rom update 3.14.4.1 now sees the phone..
has the device name changed???
evene exploit no longer sees the phone
sorry, can you be a little more clear.. what ROM are you flashing, and what exactly is happening?
by the way... i thought error 246 was the connection error... am i mixed up? which is 260?
This seems to be on any rom bar the Dopod roms
and it says 260 connection error
Error 260 connection error - the phone is not going in to bootloader mode - and the RUU cannot seem to initiate communication with the phone.
I'm getting this a lot recently trying to flash.
However, Hold the power and camera buttons while resetting with the stylus (keep them buttons held down).
When you get to the bootloader - plug the phone in - wait till you see the USB at the bottom of the bootloader screen - then run the RUU again - it WILL work - every time.
I used to get this error message alot. sometimes the programs you install don't allow you to update even if you force the phone into bootloader mode so you have to hardreset the device and then upgrade.....hope this helps
htc diamond stuck
T-Rob said:
yes, as described in the link I posted before. As soon as the error occurs, do not touch the phone, leave it, just start the ROM flash procedure again. (execute ROMUpdateUtility.exe)
Click to expand...
Click to collapse
hi ,
my htc diamond stack, no respond on the screen i try to do hard reset with tree buttons but its not working, nothing happaned, screen stay home screen with the time and not responding touching the screen at all
please emergensy help
I own a new blue angel...called by O2 II's
So, after i read ,again,and again...I have successed enter boot loader.
With white screen it's shown the version 2.07 and the line at the top "Serial"
(uhm, i use WM2003SE as the original pda when i purchase)
Ok, the problem now is, i can't flash anyrom (in Wiki and any rom i found)
After the line appear "Don't plug cable or craddle of ...." it's seem to verifie it's self... and then the line appear again "this tool is not support for this device".....and some error like that.
I was totally confused, how i made the thing go wrong? or just i missed something???
i make a soft reset, then hard reset and then 3 button together to get the white screen with no light, still see words such as: serial, version 2.0.7...
When i plug the usb cable , then the serial change into USB as usual.
As my experience,( Dopod810 and Qtek S200) everything is normal...
One problem too, i can't connect to PC with activsync (i tried any versions as possible)but itself avaiable on Boot loader...
All you understand what happen with me???
Please help me out of this. I want my Blue Angel is not the worst i got ...(i think it's possible go up to wm6???)
Finally, thanks you all for listening( reading this topic)
Yep, Happened to me too. Heres the fix.
The regular WM6 exe will give you an error everytime with the O2 IIs. Finally I printed out the WM6 directions, and also the Blue Angel for beginners and some other threads and found the answer.
You are in the right place (stuck in bootloader that is). Now you should be ready to load the OS. In the Upgrade folder you will find:
"MaUpgradeUt_noID.exe"
Run it and you will see the progress bars on the Windows screen and the dark XDA screen. Don't bother it - allow it to complete.
After it completed, I was unable to restart, soft reset, hard reboot. I think I actually had to take the battery off. When I powered it again I saw the Color Bars and knew it was good.
Good luck, Be careful. Try to be calm. I know when I was stuck in between Roms I was close to being a nervous wreck.
erh, one more message when i fkash rom...
This MaUpgradeUT novid erh something like this but this
" This tool is not support for my device" or somehow ...
I think i really stuck...
when itself verifie version of rom , i can't see both version appear on windows.
ie : version rom which is in PDA and version of rom which is in the OS i next to flash(want to flash).
So Confused . Anyway, thank for helping !!!
You are close!
Yea,
I Kept getting that too. Couldn't see both versions. Got a couple of different error messages. you are right where I was. you've got to find the upgrade exe. in one of the folders. My IIs was stuck in bootloader and I started that upgrade and it skips checking the IIs first and just begins to xfer the data.
Hi there!
I am in serious need of help with my iPAQ hx2490. Yesterday, I tried to do the
official HP ROM Update. Everything went well, up to about a point when the RUU told me that there is a connection problem with my device.
The update went to just about half way through, and I didn't touch anything, I just left the device in it's cradle.
Anyway, my problem now is, that the device won't start the OS, I can't get past the HP welcome screen. The loading bar fires up, and completes it's way to the right, but after that: NOTHING!
I have tried soft, hard and clean reset, without any help. When I do a clean reset, the display shows "Formattin PS", and the loading bar reaches the right. But after that: NOTHING again!
I tried flashing everything again, from WM 2005 first and second edition, even WM 2003. The result is always the same.
I can get it into Pre-Bootloader, normal E-Bootloader. I do get a "USB Connected" message, and I do get the following "USB" message on the screen.
Now here's the odd thing (and I do hope that all you experts are dying to solve this mystery!): when I do the update again, at either 84,1% or sometimes 85,1%, the iPAQ shuts down, and starts again. But this doesn't stop the RUU from continuing!!
I've tried everything I can, I read all the infos in the forums concerning iPAQ problems, but they're mostly concerning entering bootloader, which is NOT my problem.
Money ahead: I'll donate 10€ to the person who is able to solve this riddle!!
The money can go to either this website or the person's own PayPal account.
oh I forgot: I did try ChrisMRulz bootloader method, but I wouldn't work for me. I managed as far as the MTTY program firing up, and I do get a WCEUSB prompt, but can't enter any commands, and the nbf file doesn't get uploaded!
PROBLEM SOLVED!! Sorry.....
Can you tell us how?
Maybe it will be helpful for others that have similar problems in future.
Sure, I can do that:
I managed to flash the official International English ROM Update to my german hx2490 iPAQ. I just used the trick that you have to start the correct HPRUU.exe for your country-specific device, but just before you hit the last "Update" button, you change the .nbf file with the one you want to flash.
But you have to rename it to according filename the HPRUU.exe originally loaded,
if you don't rename it, the update utility will crash.
By doing so, I was able to flash the above mentioned ROM to my device, and after that I just flashed my country-specific ROM.
Now I'm back and running WM5.
If further explanation is needed, I'll gladly help out someone with the same problem.