Develop Bugs

Updating JASJAR

Hi all,
I have been trying to check out the forum here, to try and solve my problem, I literally bought my JASJAR today, and it was giving some wierd behaviour. In an attempt to reload the software (I prefere to reload the entire ROM), something went wrong, now all thats on my screen is "USB" and a lil lower down "v1.01".
ActiveSync obviously not connecting now bcos the OS is not on the JASJAR no more, in my device manager is a "Microsoft USB Sync" under my mobile devices.
I downloaded what I am guessing is WM6, 'JASJAR_WWE_20106_20301_11300_wwe_ship' from another thread in this forum, tried to load that but cant communicate with device cos no activesync.
I have tried the different reset options, like the 2 function keys and the reset on the back, I push 0 to clear, and then it jus goes back to the USB v1.01 thing.
I am running windows vista home basic, with the Windows Mobile Device Center, it synced perfectly with this software, communicated properly with the update tool, until my device reset and activsync lost connection, then i was stuffed.
Any help will be appreciated.
Thanks in advance.

Sounds like it is your first time with the upgrade. What you are seeing on the screen is the bootloader, which is what we use for flashing new ROMs.
ActiveSync or Windows Mobile Device Center (how come you have both on Vista?) will therefore not respond. This is fine, because we use a different program to load the new ROMs.
If you look at the folder you downloaded, chances are that there should be a program called "ROMUpgradeUt" or something similar. Provided that you have not changed anything in the folder, you should be able to flash the new ROM by simply following the instructions in the program.
You can also read this link for more information: http://wiki.xda-developers.com/index.php?pagename=HTC_Universal

Here is an instruction guide on ROM upgrading: http://forum.xda-developers.com/showthread.php?t=269118

how come you have both on Vista?
Sorry, I don't mean to sound like I have both, I recently moved to Vista, and am used to calling it activesync and not WMDC.
Thanks, will have a look

Ok, well I have got it up and running again, only problem now is activsync keeps freezing when I try and sync the device...any ideas?
I landed up using my work computer, which has XP on it, and then used MTTY and that connected fine, on Vista it simply didnt wanna work.
I ran the utility for those 'stuck on serial/usb', and that fixed it. Now I would like to load up WM6, but it keeps getting communication failures.

Thanks for the help guys....I got it working...running on WM6 now...whoo!!

error [260] message every 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

T-Mobile MDA Compact III issues...

Any help would be great....
I have a MDA Compact III issue when trying to upgrade to the ARTEMIS TOUCH 2.1 or 2.0 software
Unfortunatly, my pda was at 49% charge when i first tried, so stage one got to the end, then told me to charge my fone more and ended.
Thus i charge the fone to 75% and re-started. However, upon reconnecting the fone to commence the restart, the USB device was not recognised.
After removing the Active Sync and indeed the USB Driver from the PC and re-installing it, the conenction was re-established, however, it now often drops the connection. Plugging away, i tried the install Step 1 once more, and upon getting to 100% in the cmd part, and then progressing through the wizard, whereby the PDA displayed the progress bar reachinbg 100% (of the unlock stage) the PDA then reboots, and the connection is lost...and doesnt re-establish itself....and then the wizard reports Error [270] : Update Error The image file is corrupted. Please check your update Utility
Now, i have tried various sources for the software, and indeed tried both 2.0 and 2.1.....
Now i have a PDA that intermittantly drops its USB connection (and needs the USB removed and re-added on the PC) and is now slower than it was, plus never got to step 2 to get the software on iot.....
Can anyone help? Else i have a broken phone so to speak.....
Thanks alot in advance
Paul

paulcharles1 said:
Any help would be great....
I have a MDA Compact III issue when trying to upgrade to the ARTEMIS TOUCH 2.1 or 2.0 software
Unfortunatly, my pda was at 49% charge when i first tried, so stage one got to the end, then told me to charge my fone more and ended.
Thus i charge the fone to 75% and re-started. However, upon reconnecting the fone to commence the restart, the USB device was not recognised.
After removing the Active Sync and indeed the USB Driver from the PC and re-installing it, the conenction was re-established, however, it now often drops the connection. Plugging away, i tried the install Step 1 once more, and upon getting to 100% in the cmd part, and then progressing through the wizard, whereby the PDA displayed the progress bar reachinbg 100% (of the unlock stage) the PDA then reboots, and the connection is lost...and doesnt re-establish itself....and then the wizard reports Error [270] : Update Error The image file is corrupted. Please check your update Utility
Now, i have tried various sources for the software, and indeed tried both 2.0 and 2.1.....
Now i have a PDA that intermittantly drops its USB connection (and needs the USB removed and re-added on the PC) and is now slower than it was, plus never got to step 2 to get the software on iot.....
Can anyone help? Else i have a broken phone so to speak.....
Thanks alot in advance
Paul
Click to expand...
Click to collapse
well, I'll just try to give you some suggestions as I don't know much about MDA Compact III ,it does not fall in the category of wizard,it's a Magician device and I'm a wizard k-jam user. anyhow as a general of upgrading is to have your battery fully charged or atleast must have more than 70% charge.cuz during flashing in RUU upgrade mode,it does not charge,so if while during flash something goes wrong or it takes more time to flash,it shud have enough power to go through the whole process.if it does not have enough power to complete the process,it fails to flash properely and thus have a bad flash creating problems.so same has happened with u, you have a bad flash
well in wizards we have certain methods to revive the device or recharge the battery,i have no idea about your device,but can only suggest get the battery charge,secondly your usb connectivity problem is also due to the bad flash,cuz as there is no OS info on the device,it wont be able to establish the connection,which windows are you using,try to upgrade with winxp sp2 and active synchronize ver 4.5
as i have no idea about Magician upgrading method so wont comment further,but advise you to look in the below thread,it might be helpful,cuz its about Magician MDA Compact III
As your posting in the wring forum you might not get much help here,ok
http://forum.xda-developers.com/forumdisplay.php?f=276
good luck

thanks
thanks for the reply. Got it working - used 2.0 to unlock it, and 2.1 for the actual rom upgrade...

Activesync problem

I had to soft reset my orbit the otherday and since then have been unable to sync with my pc.
I have tried re installing activesync and soft resetting the orbit with no joy. when I select activesync on the orbit I get the message displayed in the attached jpeg.
I would rather not do a hard reset as some of the programs I use (particularly DrugDoses) use a device key for registration which is changed whenever the device is hard reset.
Any help and advice would be appreciated.
Forgot to add, I am using XP pro and my other WM6 device has no problems so the problem must be on the orbit.
ROM: 3.4.206.2 WWE
ROM Date: 8/31/07
Radio: 02.98.90
Protocol: 4.1.13.47

Same problem
I have the same problem since installing B&B 4.3 GER on my device. I should mention that I am using Vista.
Ideas, anybody?

I had the same problem when i was running B&B 4.3 whilst using xp. At first i thought it was a bad connection from the phone to the mini usb cable (as i manange to get connected whilst bending the wire). I managed to get a connection after 2 days of trying. I then reflashed the phone with a different ROM & all was well again. For some reason some people are affected by this whilst others arent. No idea why, but there is a conflict somewhere which was resolved once i changed to a different ROM. Hope this helps. But dont dispair cos you will eventually get a connection & then you can reflash.

On PPC, You could try looking at connections, USB connection and make sure advanced usb is disabled. May help.

[Question] 260 error when updating ROM

Okay, I've searched alot to get this thing solved. When I try to update my rom, the update starts normally, but then my telephone screen turns black, my gets disconnected, windows tells me it has found new hardware. The update failes and returns error 260 (connection lost). When I soft-reset the telephone afterwards, it returns to it's old shape.
Info about my telephone.
Rom: 1.93.404.1 NLD
Radio: 1.0025.05
PC: Windows XP SP 3, Active Sync 4.5
I tried to update with this rom: RUU_Diamond_HTC_NLD_2.03.404.3_Radio_Signed_Diamond_52.51.25.26_1.09.25.23_Ship.exe
I also tried to update to Hard-SPL but that gave me the same error.
PLease guys does anyone of you know how to fix this? (personally I think it's windows xp which is screwing up).
Thanks in advance, I appreciate all help.
Yours, Martijn.

Even the tiniest tip may help (A)

I had the same trouble with that rom, I tried from internal memory and it worked. Search the wiki I am sure the info is there.

"ERROR [260] : UPDATE ERROR
This error occurs when there is an "open port error" before upgrading the CE ROM image. Solution: You can reset the device and run RUU again. If you still encounter an "OPEN PORT ERROR" again, reset your computer and try again."
This is what the WIKI tells me. But I have tried that. How did you manage to perform the update on the internal storage? Because I tried that with hard-spl but it wouldn't work.
Besides I only have .exe files for the Hard-Spl and the official rom from HTC.
Thanks for your reply though.
EDIT PART, just read this on another thread in the wiki:
ERROR 260 (Update Error):
"Your phone is not connected to ActiveSync. Check your connection or restart the phone. Also make sure in ActiveSync that "Allow USB connections" is checked (under File->Connection Settings). If this still doesn't help, then remove the memory card and SIM card before flashing."
I'm going to try this now, if it worked, I'll let you know
Just found out I have a CDMA version or something, I'll try google for the problem now.

Get the rom image from your temp directory and look here, found in the wiki
http://wiki.xda-developers.com/index.php?pagename=Diamond_FlashfIS

Does the hardware install incorrectly? My laptop did this on XP.
XP would find the new hardware, my bootloader would say USB. Then it'd tell me new hardware could not be installed properly and from there my phone suffered those symptoms - Back to where I was. Funnily enough it eventually fixed itself.

dickenz said:
Does the hardware install incorrectly? My laptop did this on XP.
XP would find the new hardware, my bootloader would say USB. Then it'd tell me new hardware could not be installed properly and from there my phone suffered those symptoms - Back to where I was. Funnily enough it eventually fixed itself.
Click to expand...
Click to collapse
It looks alot like your problem yes. But last time the hardware installed correctly, then the patch I found for CDMA models on ppcgeeks failed, and my telephone got bricked. So I'll need to get that fixed first. After that I'll sure think twice before I try another rom update :/
Thanks for all the help though, and I have to advice everyone to not use the hard-spl for cmda users from ppcgeeks unless you're 100% sure it fits your model!