Database Users

critical problem in jamin for help please

My friend's jamin when he tried upgrading with smart1 wm6
after the flashing process finished it gives the 3 colors of boot loader
the screen flickers continously with the 3 colors
no way to hard reset the device
and activesync doesn't feel it
I searched all the forum for a problem like this but I didn't find any
any suggestion please, or any help?

Flash NVID Rom and try Smart again. Read WM6 upgrade Manuel and readme for the ROM.

NetrunnerAT said:
Flash NVID Rom and try Smart again. Read WM6 upgrade Manuel and readme for the ROM.
Click to expand...
Click to collapse
Please how can i flash with the activesync doesn't notice my device and where's NVID Rom
Ok. I'll search for it but please help how can I flash it to the device which doesn't recognized or felt by PC

If your device is in bootloader mode, activesync cannot recognize it but this is normal. Jamin is recognize only as a usb device and you can downgrade it to NVID rom easly.
Then you could upgrade your favorite rom, I suggest PDAVIET 4.0.0.1
Bye for now

divxmaniak said:
If your device is in bootloader mode, activesync cannot recognize it but this is normal. Jamin is recognize only as a usb device and you can downgrade it to NVID rom easly.
Then you could upgrade your favorite rom, I suggest PDAVIET 4.0.0.1
Bye for now
Click to expand...
Click to collapse
I think I didn't discuss the problem well
The Problem is when I start to flashing a rom a message tells that check if the usb is connected and if the device is connected .
This is happen with the device is connected to the cable and the tricolor screen is flicking . and the device doesn't open doesn't flashing.

must use NVID rom. maybe qtek nvid one from here? http://wiki.xda-developers.com/index.php?pagename=Prophet_ROMs

hasanemara said:
I think I didn't discuss the problem well
The Problem is when I start to flashing a rom a message tells that check if the usb is connected and if the device is connected .
This is happen with the device is connected to the cable and the tricolor screen is flicking . and the device doesn't open doesn't flashing.
Click to expand...
Click to collapse
If the problem still there, Try to release the battery for 1-3 hours and put it again to the device, go to the boot loader and pray. Hopefully it could work. Actually, this way worked on my Himalaya and Prophet.

Just run the "Step 1" component of the PDAViet ROM (http://rapidshare.com/files/32728615/Prophet_PDAViet_Step1.zip), which is just a plain AKU 2.20 NVID. This will find your device even if its in bootloader mode (it doesnt depend on activesync). Just flash it with that sucker and you should have a working phone on WM5, then you can safely upgrade it to WM6 (or leave it if you like).

ekto said:
Just run the "Step 1" component of the PDAViet ROM (http://rapidshare.com/files/32728615/Prophet_PDAViet_Step1.zip), which is just a plain AKU 2.20 NVID. This will find your device even if its in bootloader mode (it doesnt depend on activesync). Just flash it with that sucker and you should have a working phone on WM5, then you can safely upgrade it to WM6 (or leave it if you like).
Click to expand...
Click to collapse
I shall try and tell you the result

error 260 this is the result

i have a slight variation problem like this...
1. i was upgrading my O2 Neo to the latest WM05 & the phone went to bootloader mode & the upgrade started searching for the phone as normal..then some error & it stopped upgrading while the phone was in bootloader mode..
2. at that time,i got an urgent call & had to leave the phone in bootloader mode...
3. when i came back..the phone was dead & now it wont startup at all.. not even in the bootloader mode.
4. Maybe the batteries dead...so i charged it (Over night)..nothing happened in the morning..
5. kept the battery removed for about 5-6hours & still nothing happens..it simply does not startup.
6.I've tried holding the camera button & resetting, but it wont go into bootloader mode.
7. i;ve tried holding the connections button + camera button _ reset but it wont hard reset...
can anyone help me here...
what can i do???

hasanemara said:
error 260 this is the result
Click to expand...
Click to collapse
Error 260... If i remember correctly that's "cant find device" or something.
Few things to check:
Is the PC you are upgrading on running windows vista?
If so, use a different PC running windows XP.
Have you tried a different USB cable?
If not, do so, this tends to be the cause of problems like this.
Have you checked device manager?
Go to control panel, Administrative tools, computer management, device manager and see if you can find your device. If it has a yellow ! icon on it or is listed as "Unknown device" or anything like that then you may need to reinstall the drivers (int hsi case the easiest way to do that is to reinstall activesync). If everyhting is working properly it should show up as "HTC USB Sync", "PocketPC USB Sync" or something like that under the heading "Mobile Devices".
Have you just plain tried another computer, regardless of the OS?
I found that I could never get my phone to flash on my laptop, but it worked without a problem on my desktop. This is not to say laptop's cant do it, it simply means some computers just have problems like (in my case i believe) no USB 2.0, or too low-powered USB ports.

ekto said:
Error 260... If i remember correctly that's "cant find device" or something.
Few things to check:
Is the PC you are upgrading on running windows vista?
If so, use a different PC running windows XP.
Have you tried a different USB cable?
If not, do so, this tends to be the cause of problems like this.
Have you checked device manager?
Go to control panel, Administrative tools, computer management, device manager and see if you can find your device. If it has a yellow ! icon on it or is listed as "Unknown device" or anything like that then you may need to reinstall the drivers (int hsi case the easiest way to do that is to reinstall activesync). If everyhting is working properly it should show up as "HTC USB Sync", "PocketPC USB Sync" or something like that under the heading "Mobile Devices".
Have you just plain tried another computer, regardless of the OS?
I found that I could never get my phone to flash on my laptop, but it worked without a problem on my desktop. This is not to say laptop's cant do it, it simply means some computers just have problems like (in my case i believe) no USB 2.0, or too low-powered USB ports.
Click to expand...
Click to collapse
No I didn't change any and I can connect my o2 xda mini to the same cable
I want to ask few technical question
HOW CAN A SOFTWARE DAMAGE THE DEVICE?
CAN A SOFTWARE FOR EXAMPLE BURNS A PROCESSOR OR SOMETHING LIKE THIS?
If So there will be a big problem with those types of devices
a virus for example can destroy my device's board or processor!!
Yesterday My friend went to an I-mate customer service who tel him that
the board had been destroyed by the bad software !!!!!!!!!
Please Give me technical advice about this problem
and is there a web site for him to buy this board (i-mate jamin)?

I've tried everything... even tried it on my desktop... but my phone just wont turn on now. i've kept the battery removed for more than 8hrs now... i've even charged it for more than 8hrs non-stop..nothing happens..
maybe i should get hold of a charged battery & try it with that battery...?
Any clue how to get my phone started??

got it working !!! PHEW... i used my HP battery which was charged & put it into it..now i've got my bootloader & i'm installing the new OS as we speak... 15% done.... keeping my fingers crossed

done.. got my HP Ipaq battery , which was charged & my new started up in bootloader more.. PHEW !!!
66% done... keeping my fingers crossed

ok, installed...now, one more problem..my touch screen's not working...???
Any idea what to do?
i installed "Prophet_PDAViet_Step1"

Why ActiveSync always disconnects the BA while upgrading to the new ROM.

I have upgraded from WM2003SE to WM6 (the first released from XPlode version OS 5.2.1620 build 18125.0.4.2) without any problem. Now I want to upgrade from that version to the current release, but the ActiveSync (I am using 4.5) always disconnect after MaUpgradeUT_noID has detected the previous installed OS. So I got an error message like "cannot to the device" or so. It happens everytime even I just try to upgrade the Radio rom.
I have also tried to use ActiveSync to version 3.8 (I found this suggestion from this web site) but bad luck it can't detect my BA device at all. I have also tried to revert back to WM2003SE but still get the same problem. My system is WinXP SP2 & O2 IIs. So Please help I am in the dark right now.

Same problem here...

su2003 said:
I have upgraded from WM2003SE to WM6 (the first released from XPlode version OS 5.2.1620 build 18125.0.4.2) without any problem. Now I want to upgrade from that version to the current release, but the ActiveSync (I am using 4.5) always disconnect after MaUpgradeUT_noID has detected the previous installed OS. So I got an error message like "cannot to the device" or so. It happens everytime even I just try to upgrade the Radio rom.
Click to expand...
Click to collapse
get into boot loader mode,then try
(press record button + power button and reset at same time)

addan said:
get into boot loader mode,then try
(press record button + power button and reset at same time)
Click to expand...
Click to collapse
Have tried that already but still get the same error. I have even reformatted my PC and reinstalled WinXP and ActiveSync 4.5 just in case there are viruses or so but also get no luck.

Did you soft (or hard) reset your BA and reboot your PC after failure? (Try clean upgrade, and in bootloader).
Did you (succesfully) establish an ActiveSync partnership before upgrading?
Did you try unchecking Enable advance network functionality in USB to PC (under settings, connections)?

Did you soft (or hard) reset your BA and reboot your PC after failure? (Try clean upgrade, and in bootloader).
Yes, at this time you asked me. Nothing changed.
Did you (succesfully) establish an ActiveSync partnership before upgrading?
Yes.
Did you try unchecking Enable advance network functionality in USB to PC (under settings, connections)?
Yes. I did it.
More over, if I started BootLoader mode before execute MaUpgradeUt_noID.exe the program get struck while performs device information checking, I have to pull it out from Sync station the program then continue running but without any information (like the existing OS version etc.)

how long did you wait for the program to respond before you find that its stuck ?
Here it takes about 2 min to find the device
Proper upgrading procedure, as it was said 10000's of times
1.put your device in bootloader mode
2. place it to cradle
3. kill activesync (optional - if you dont do it the upgrade utility will do it for you, but sometimes activesync stays on and fail the upgrade process)
4. start upgrade utility and follow the onscreen instructions
5. perform hard reset (the three options thing)
thats all

Xplode's new cube cab
deleted... off topic

how long did you wait for the program to respond before you find that its stuck ?
It was about 5 min and the program still had no responses. I then have to pull it out and the program continue running but without any information (like I had mentioned it before).
Here it takes about 2 min to find the device
Unfortunately not with mine.
Proper upgrading procedure, as it was said 10000's of times
1.put your device in bootloader mode
Yes. I did it.
2. place it to cradle
Yes. I did it.
3. kill activesync (optional - if you dont do it the upgrade utility will do it for you, but sometimes activesync stays on and fail the upgrade process)
I have tried it both with and without killing the activesync.
4. start upgrade utility and follow the onscreen instructions
Yes, but once I started the upgrade I have noticed that the activesynce has disconnected my device.
5. perform hard reset (the three options thing)
I didn't have chance to go to this point.
thats all
I think the main problem is the activesync has disconnected my device suddenly when started the utility. I have also tried to take out anythings that using USB port like mouse, ext. DVD, printer, scanner just in case the upgrade utility may conflicts with those devices.
I think I shall try to change the PC to upgrade my device to make sure that it wasn't caused from hardware defection.

su2003 said:
4. start upgrade utility and follow the onscreen instructions
Yes, but once I started the upgrade I have noticed that the activesynce has disconnected my device.
5. perform hard reset (the three options thing)
I didn't have chance to go to this point.
thats all
I think the main problem is the activesync has disconnected my device suddenly when started the utility. I have also tried to take out anythings that using USB port like mouse, ext. DVD, printer, scanner just in case the upgrade utility may conflicts with those devices.
I think I shall try to change the PC to upgrade my device to make sure that it wasn't caused from hardware defection.
Click to expand...
Click to collapse
With regard to your last remark: you stated earlier you did a fresh reinstall of XP. Now, why would you install and connect all these peripherals if you only want to upgrade your BA rom??? All you need is a fresh WinXP and ActiveSync...
Did you really do a fresh install and follow the wiki and the tips mentioned again (and again)?
You are getting me (and probably all of us) confused.
Your answers to especially points 4 and 5 of xplode tips to me clearly indicate that you do not really take (enough) time to understand the procedures (or what you are doing) and want to have WM6 running asap with no effort at all...
Your remark "I think the main problem is the activesync has disconnected my device suddenly when started the utility" only confirms this as this is the whole point of boatloader and was furthermore indicated it would do exactly so by xplode earlier on.
Please do take time and hence show consideration to all of us that are trying to help you in preparing yourself properly before trying to attempt any further upgrade.
Good luck!

With regard to your last remark: you stated earlier you did a fresh reinstall of XP. Now, why would you install and connect all these peripherals if you only want to upgrade your BA rom??? All you need is a fresh WinXP and ActiveSync...
Did you really do a fresh install and follow the wiki and the tips mentioned again (and again)?
You are getting me (and probably all of us) confused.
First of all, Sorry if I make you and other confused. I have began to unsuccessfully upgrade my device since Friday. So I decided to help myself at first by try to do everything I can do by myself. I have formatted PC HDD and also reinstalled activesync because I thought the utility may conflict with other program on my PC or from Viruses. I have also tried many ways with hard reset and cold reset etc. to upgrade my device but have no luck. That was with very fresh new installed WinXP PC. Unfortunately, I have to use this computer for my job also. So that's why I have to install printer & scanner driver including MS Office, AutoCAD and other necessary program to serve my job . I have falled with upgrading but I do not want to have problem with my job. Hope you understand my essential.
Your answers to especially points 4 and 5 of xplode tips to me clearly indicate that you do not really take (enough) time to understand the procedures (or what you are doing) and want to have WM6 running asap with no effort at all...
Since I began to upgrading and everytime I have executed the utility I have always wait & wait but I just never look at the clock to see how long I have waited. Xplode has just warned me to take enough time so I started to upgrading but with clock at this time. I have already mentioned that I have successfully upgrade from WM2003SE to the WM6 (previous version) so as a user I have enough experience and know what I am doing.
Your remark "I think the main problem is the activesync has disconnected my device suddenly when started the utility" only confirms this as this is the whole point of boatloader and was furthermore indicated it would do exactly so by xplode earlier on.
This is just my opinion to let you guy see and understand the problem. That's it.
Please do take time and hence show consideration to all of us that are trying to help you in preparing yourself properly before trying to attempt any further upgrade.
I think I have already put a lot of effort about upgradind my device. I have reformatted and reinstalled all necessary programs. It took me out almost half a day to do this. And not only with my PC I have also reinstalled all programs on my device with an old OS version since I have lost them all from hard reset. Other than that I have also tried & tested upgrading the device during the time. The only word I can say that It was not funny to do all of this. It was not really a hard job but it took almost my weekend time.
Good luck!
Yes I do need it barely. Actually I have already felt a little lucky got from all of you that try help me solving the problem. Thanks.

su2003, nice answer.
His main problem is that he does not understand that activSync will work if the device is in a normal state but when device goes to bootlogger mode, its only USB connection that will help a PC to talk to Device and not activSync.

April 1 said:
su2003, nice answer.
His main problem is that he does not understand that activSync will work if the device is in a normal state but when device goes to bootlogger mode, its only USB connection that will help a PC to talk to Device and not activSync.
Click to expand...
Click to collapse
Thanks for your additional.
I have also tried using different PC to upgrade the OS but got the same result.

you have to be sure that your BA when cradled display USB (after getting into bootloader mode) instead of serial 2.06 than run the upgrade utility

I am quite sure that the screen has displayed USB but the number is 2.07 not 2.06. I am not sure about the meaning of the number, it could be the version.
I have also brought a new USB-XDA IIs cable yesterday, just in case the cardle was defected but it doesn't work also, I have got the same result.

khanem said:
you have to be sure that your BA when cradled display USB (after getting into bootloader mode) instead of serial 2.06 than run the upgrade utility
Click to expand...
Click to collapse
I am quite sure that the screen shown USB 2.07 (should be differ version than your).
I have also brought a new USB-XDA IIs sync cable but getting the same result.

Conclusion:
Bad Hardware(Flash ROM)?
Your Bootloader is toasted or had it's LAST flash of it's lifetime???
We can say that... but hopefully not for your sake.
Because as you have said you've done EVERYTHING that was posted.
and though our Senior's "inputs" didnt worked out the way it SHOULD work.
I cant say it's a waste of time to answer your questions.
But there are no more questions to ASK
and there are no more questions to ANSWER
They're all been said here.
All you have to do is PRAY HARD leave the BA rest for a day...
remove the battery...
think things out, clear your mind... sleep...
then execute Xplode's Walkthrough from Step 1 the next day.
but be sure to have the battery fully charged.

Your BA is not dead and your bootloader is not toast. The only problem you have is probably you are impatient. Go to the Wiki and follow the procedure exactly as it is written. It will work. By the way, if you kill Activesync (ie disable USB connection in activesync connection setting), put your device in bootloader mode and connect your usb cable (in that order), run the upgrade and it will work. Forget about activesync.

su2003 said:
I am quite sure that the screen shown USB 2.07 (should be differ version than your).
I have also brought a new USB-XDA IIs sync cable but getting the same result.
Click to expand...
Click to collapse
I use xda IIs and the bootloader mode shows ver 2.07, and i dont have any probs installing. I dont think the version 2.07 has got something to do with your problem.
You said that you tried other pc and it doesnt work, and it worked before when you upgraded previously. I think you know enuf about upgrading if you have done it before....
did you have problem with sync connection before? I was just thinking maybe there is something wrong with your BA....like actual hardware problem with the cable connection??
what about firewall? would it affect it - I doubt it cause its not in sync mode.... but at this stage, maybe just try all possibilities to try to get it working.
Good luck

Mhm. I'm not sure I've really followed all the intricacies of this case ... But whatever, here's my two cents for a safe upgrading procecedure:
1) use a cradle, not a USB cable, and make sure the cradle's
power supply is plugged into a wall outlet. It also helps to make
sure the cradle is plugged directly into the PC, not via any kind of
USB hub. No other devices should be connected to that same USB
channel. I suppose temporarily disconnecting other (unneeded) USB
devices from the computer can't hurt, either.
2) I guess "kill ActiveSync" can mean various things ...
however, here's the best way to do it I think: as sofene mentioned,
disable USB connections (what the hell - disable ALL connections) in
ActiveSync settings. Then reboot the PC. No need to look for ActiveSync
processes and kill them manually -- disabling the connections will take
care of that. Rebooting ensures that ActiveSync's driver code is really
unloaded.
3) remove SD card and, for good measure, SIM card from the BA.
4) perhaps soft (or even hard) reset your device
5) put device in Bootloader mode
6) insert device in cradle, start upgrade utility, off you go ...
By the way, ActiveSync has got nothing to do with the ROM upgrade utility, and it should therefore not have been necessary to re-install ActiveSync, etc. You just have to make sure it does not get in the way of the upgrade process. As far as I understand the process, the ROM upgrade should work equally well on a PC that does not even have ActiveSync installed.

Maybe activesync??

When trying to flash rom my activesync shuts down and i get a error 260, I have to reboot pc to try again,thought it might be pc problem but installed activesync 4.5 on another and tried that - same thing???
Any ideas?
Can't seem to get into bootloader either regardless of keypress sequences.

You're running Windows Vista aren't you?
Simplest solution is to get access to an XP machine and try with that. Problem Solved.

No, I'm not running vista - thankfully and neither was the other machine that I tried it on.

Factory reset my Hero

Hi,
I now have a custom ROM on my HTC Hero, but I have had a lot of trouble with it. And since the 2.1 update is hopefully is coming soon, I want to get my Hero back to what is was when I bought it. I want to remove the recovery image (this is the screen I see when I wipe it and install new ROMs from?) and my current ROM, and install the official HTC ROM.
I hope this is possible and somebody can help me. And sorry for my poor English and lack of knowledge.

Just download and install the official firmware from HTC support page.

But I can only find an upgrade there, not the whole ROM.

They are complete ROMs about 100MB each.
You can also look here:
http://forum.xda-developers.com/showthread.php?t=559622

Ok, thanks. I will download and try to install.
My main concern is that I get an error if I try to call (something with "com.android.phone" isn't working). I can't call out and nobody can call me. Hope this wil fix it.

Problem when I run the RUU
I want to do the same, but when I run HTC official RUU, after a while it stops and sends me the usb / connection error that is not connected, and the phone keep standing in the fastboot.
I have tried with all of HTC ruu, and i 2 different computer, and still have the same problem.

Try using windows XP not vista or 7...

Argghhh...
So you propose to change windows for make my phone virgin. No way.
How does it work with mac?

cant see why there would be a difference between XP / win7, but if it is.. just right click the file and run in compability mode with XP, shouldnt be any difference then.

I had exactly the same problem till i used win XP. Compatibility didn't work.

SherlockHolmz said:
cant see why there would be a difference between XP / win7, but if it is.. just right click the file and run in compability mode with XP, shouldnt be any difference then.
Click to expand...
Click to collapse
I will test this mode.

Hard Reset HTC Hero
1. Switch off the phone (either removing the battery or shutting down by holding the "end call" button for few seconds
2. While being switched off, hold the "home" (house) and "back" (the arrow in the lower right corner)
3. Hit briefly the "end call" button" while still holding the "home" and "back" buttons.
4. Release the "home" and "back" button, a white screen containing technical information should appear, with a red message asking for hitting the "menu" button.
5. Hit the "menu button", the Hero will now boot with factory settings.

blixsDot said:
I will test this mode.
Click to expand...
Click to collapse
Didn't work.

Find a friend or borrow a computer with windows XP. It's the only solution.
Edit: Or use VMWare box as stated here:http://forum.xda-developers.com/showthread.php?t=703445

Hi,
I'm using W7 and I had the same problem. I've wait that the USB connection is lost (and the RUU tell me that he cannot go forward) and let the phone in this pseudo "RUU waiting mode". and restart the RUU on the computer. Then it works... I don't know if it works with mac but with W7 it does ;-)
Cheers!

dodjob said:
Hi,
I'm using W7 and I had the same problem. I've wait that the USB connection is lost (and the RUU tell me that he cannot go forward) and let the phone in this pseudo "RUU waiting mode". and restart the RUU on the computer. Then it works... I don't know if it works with mac but with W7 it does ;-)
Cheers!
Click to expand...
Click to collapse
Now it will not connect at all with the RUU. Even with the hard reset.

definitively a driver problem :-/ Are you on mac or W7 ?

On W7.
But the htc sync works normally when i don't try to use the RUU.

Mate.. Just google "HTC Hero Win7 drivers". Install the correct drivers from Device Manager and voila.

yep or uninstall the drivers and install the last ones on the htc website. There is a tutorial I've followed which as worked 100% /execpt the little trick with starting the ruu again in wating mode:
this thread : http://forum.xda-developers.com/showthread.php?t=645253 and it works ;-) at least for me
for the drivers the phone should be reconized in recovery mode (it make the little noise for usb device plugged ;-)

Touch Diamond2 keeps disconnecting from Windows 7

My HTC Touch Diamond2 never stays connected to my Windows 7 PC for long.
Therefore its not syncing everything.
If I go into Sync Center the status of the device is Disconnected.
To fix this problem I have to go into Device manager, Uninstall the Microsoft Windows Mobile Remote Adapter, unplug the phone from USB, plug the phone back into USB and Windows recognises the phone and reinstalls the driver.
But later in the day it will disconnect and I have to go through the reinstall process again.
Its really annoying.
How can I permanately fix this?

Try a Hard-Reset. It worked for me to. Or try to reinstall Windows mobile device center.
if that does not work, try to update hard-spl to 2.51 (if your device is already rooted). that helped me out, maybe it will help you, too.

wavesshock said:
Try a Hard-Reset. It worked for me to. Or try to reinstall Windows mobile device center.
if that does not work, try to update hard-spl to 2.51 (if your device is already rooted). that helped me out, maybe it will help you, too.
Click to expand...
Click to collapse
Thanks for the reply.
I have not done a hard reset but I updated the ROM, last week, to the latest that HTC have published.
It did not fix the problem.
I also reinstalled the Mobile Device Center and it didn't fix it.
I have now created a script to reinstall the driver for me. So I just double-click it on my PC and its automatic. Still annoying but now less so!

had same problem but Hard-Reset helped me

you can try do that in another pc ?

I have the same problem.... and I can't try do that in another pc.... what have I to do?
Is it a firewall problem?