I got trouble - I tell you....
Yesterday, I wanted to update my T-mobile MDA from winmobile 2002 to 2003. I was using "Lumpistefans" -Romkitchen (xda.weblink.net). I choose the rom to be coocked as an "installer exe".
When I performed the update, everything worked fine - for about 30 secs....then brakedown
This message accoured "Can not open COM/USB port...."
from this time on, my mda seems to be toasted!! I can't switch it on , softreset won't work - and after an hardreset the display only shows some black stripes and two blank squares at the top half.
I don't need to mention, that Activesync isn't recognising the mda anymore - saying "uknown usb device - can't connect"
I don't think the Bootloader is working still either - by pressing the on/off button, the bootloader should be activated ..or??!? I never tried that before.
I read the thread "rom flashing is dangerous" but didn't get any helpfull info on my case.
I need Help...getting quiet despered!!
THANKS for alls Help , Hints and comments!!!!!
ciao
mark
here is how you enter the bootloader
http://xda-developers.com/bootloader/
ok thanks - the bootloader is still working ... can i now just flash it with a rom using my sd card?
yes just plug in the sdcard of min 64MB into your sdcard writer/reader and use xdatools to flash the nbf or nb1 file to the card
and put in the sdcard and go back into the bootloader
I have a problem with my Jam
During the upgrade ( I messed sth up :/ ) the software quitted and the mdac went off. Restarting leads to nothing. After Cold reset,
the device is stuck in bootloader and doesnt do anything at all
only way to kind of restart it is to connect it via usb, remove the powerpack, ( red light glooming ), reinserting the power pack -> Device is Restarting last rom.
After the autoconfig ( T-Mobile ) device restarts ( as usual ) but again stucks in the BL
From time to time it communicates via USB in BL(after several restarts), but not enough to do a d2s.
How to handle it?!
When in BL disable usb connection in AS, connect it to PC and try to reflash.
we already did so,
but the problem is that there is no rom for our mdac outside....
(usb is deactivated in as)
I guess you'll have to use another rom (imate, qtek).
we tried this way, we used this rom: JAM_WWE_106_110_10500
with this patched application: MaUpgradeUt_noID...
Our bootloader is not able to reinstall its own backup from
a sd card...
I don't know what to suggest...
Sorry, mate...
I just got my Mini S and it is a BRICK! All it does is go straight to bootloader upon booting... So i can't use the updater that's available.
Even if i do a hard reset, it goes straight back to bootloader. Somebody help, please!
where did you get it from?
was it a brick when you got it? if so compain and send it back
or have you done something to make it a brick?
I received it as such, but would prefer to fix it myself- its just different than other smartphones in that you can't load a rom image on it when it is in bootloader.
anyone have suggestions?
somehow get a Rom on to a Mini SD card and restore it thou the boot loader
if you know someone with a Vario then could put a mini SD card in it and back up the rom
Hello timothyadam,
yesterday my "mini s" was also dead (no booting os!), but:
when you are in the screen with the three colors (press Voice and camera Button and then reset) and you have connect the mini s via usb cable (in the left down corner you must see USB) then you can click the exe (imate or qtek prodigy file) and this work.
Regards
I've tried that, but since the K-Jam rom update only works when the device isn't in bootloader, i can't get it to recognize the device...
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"
hey guys, over the past few days ive had battery problems with my iMate JAMin, i got a new battery, insert it, and power on my device, now, rather than loading up the iMate image, it goes to the tri-color boot screen, i've tried a Soft and Hard reset, no luck , any one willing to try and help solve this problem, please email or PM: [email protected]
Will installing a new rom fix this problem?
Aidenkidd.
From the wiki:
wiki said:
If during an upgrade your Prophet fails to start properly or can only enter bootloader follow this:
Recovery
Download and install the latest version of ActiveSync (Google for it)
Download and unzip an AKU2.2 (No Vendor) ROM for the Prophet-any AKU 2.2 will do-from
here (any part one) or
here
Within ActiveSync DISABLE connect through USB (Tools->Connection Settings->Uncheck Allow Connect through USB)
Put the Prophet into bootloader mode (hold the camera button and insert the stylus into the larger hole next to the power socket)
Plug the Prophet in via USB
Run the RUU specific to your device (G3 or G4) from the AKU2.2 folder
Disconnect the Prophet, and then re-enable the connect through USB.
Your Prophet should now work!
Click to expand...
Click to collapse
I wrote it any way, but since no one reads it I may as well post it here.