Started Upgrade Rom now get Error 101 Cant Connect to Device - JAM, MDA Compact, S100 Software Upgrading

HELP!
ok connected my Imate to the PC, downloaded the Rom upgrade from Imate, ran upgrade, all was going ok found device started upgrade then came up with Error 101, trouble connecting to device
Now i get a grey screen cant enter bootloader mode or do anything and PC cant recognise phone to complete upgrade
On screens it says Serial (or USB when cable plugged in ) at the top of the grey screen (no backlight) and V1.00 at the bottom
So how do i fix this???.......

ok Crisis over!....
took battery out (for the 100th time) tried the bootloader mode (for the 200th time) and NOW it recognises.....
Persistance ... thats the key!!

Related

Help needed phone doesn´t not boot anymore

Hi,
I have tryed to upgrade my rom to a new version (Prophet WM5 AKU3.2 v3231). Followed the stept correctly, however my phone does not boot anymore. It gets stuck in the qtek logo (when it displays the AKU version i´ve got) and the sceen gets all shacky.
An addictional problem is because it is stuck at that point it does not connect to my computer....
What can I do to fix this, any good suggestions
Thank,
Sebastiaan
You should be able to enter bootloader mode by pressing and holding the camera button while you power on your phone. On the bottom left, you should then see "USB" - connect it to the PC and flash it again.
Had to do this yesterday after flashing failed.
Mike
thanks it worked
Sebastiaan
Error [296] Upgrade Only
Hello
I have same Trouble & I Make Bootloder from USB but Always I get This Error
ERROR [296] UPGRADE ONLY
This NBF file connects used for your PDA Phone. Please get newer NBF file.
Note: I try to Upgrade to 2006-11-12_Prophet_WM5AKU2.3_lvsw_edition but my Phone Stack So I reset as say after 30 m
Now I trying to back to Old Software from I-mate
Also I try to upgrade to 2006-11-12_Prophet_WM5AKU2.3_lvsw_edition but no Connection....
Please help me I with out Live (Phone)
I know it sounds strange but i used a different USB port and then it did connect. Now that everything is back to normal i can use the old one again.
maybe it works for you as well
I tried doing that, but for some reason my computer doen't recognize the device...pls help!

Prophet stuck in bootloader HELP!

1st off I DID use the search button.... 2nd HELPPP ME!!!
Waaah :'( I have a most intriguing problem I was running pdaviet 4.0.0.6 Touch for almost 2 weeks now without a single glitch.. the phone fell on my carpet and went to bootloader screen and eversince then it has never recovered I tried a hard reset it didn't work when I was pressing the send button it did nothing I did some forum searches and tried putting back the nvid RUU and it said that the update was succesfull and the progress bar on the phone moved accordingly but it went back to the bootloader screen ... then I tried pdaviet temp rom that was in the package still no go I can tell it works somehow because the USB lights up in the bottom left when I plug the usb cable and the progress bar that moves, but I'm getting desperate IPL and SPL info is in my sig...
same same... but i dropped mine before flashing the new PDAVIET touch rom.. still went fine..
now, it still flashes... RUU says its successful.. but PDA just reboots back to bootloader..
i can charge my phone fine in bootloader.. i can see the USB come on when i connect it to my computer.. other than that, can't do anything...
i've tried everything the past 2 days.. looks like i'll have to send it back to dopod.. will let u guys know what happens... probably something got damaged..
struck at bootloader
I tried WM6 (4.0.0.6 touch) from WM5 AKU 2.2 but it failed in between with some write message,which was bit strange as I didn't touch any key on laptop during that time and no program was being run at that time. (I am using VISTA Home premium). I got my phone into bootloader but it does not connect to my laptop...so cant upgrade back to AKU 2.2. In Windows Mobile Device Center, I cant see my device connected. So is it particular to Vista or my phone got bricked?
I am yet to try on Windows XP, which I have to arrange.
Please advise.
i had the sam problem.i installed this : try to install the 2.20 nvid rom
just go into bootloader mode-you dont need active sync connection and start the upgrade-search for 2.20 nvid rom download it and recover your device
charliess said:
i had the sam problem.i installed this : try to install the 2.20 nvid rom
just go into bootloader mode-you dont need active sync connection and start the upgrade-search for 2.20 nvid rom download it and recover your device
Click to expand...
Click to collapse
I tried the same but when I run ROMUpdateUtility_No_VenderID, I get a message 'Update Error, 260' which tells further that PDA is not connected to laptop., although it is very much connected. However LED on PDA does not blink as well.
When I plug in this phone to Wall adaptor, LED does show up.
'USB' appears at Bottom Left corner of PDA when connected to laptop and certainly its getting recognised by Vista as it starts installing Driver as soon as this is connected to laptop.
Please suggest.
I am stuck in the same situation, although I have a G3, running 2.20 on IPL & SPL
Working now
I tried on XP (I was trying on vista before)..I had to install Active Sync as it was not installed on that PC, then run RUU update for AKU 2.2 and update was successfull. Now will try Touch 4.0.0.6 again but this time on XP.
Hope this time I wont have any problems.

Cant Flash my Vox! Plz Help

Hi All,
Out of the blue my HTC Vox stopped booting. I mean, it would load to the windows mobile screen and then stay there till eternity. Removing my memory card and SIM also did not help! I then tried the hard reset option.
Even after hard reset it sometimes boots(1 out of 15 times) and when it does...it hangs after 10 to 12 minutes. Still have not put my sim n memory card into the phone.
I tries flashing the ROM using the ARA 1.27 ROM. After it rebooted to the bootloader, the flash utility gave a connection error! It did not connect to ActiveSync and stayed at the bootloader screen.
I still do not know how to flash it successfully.
If anybody can help me out, I'll be extremely grateful!
Thanks
Prateek
take the battery out, put it back.
connect your Vox (USB).
Hold the camera button and turn on your Vox.
you should see a red, blue and green screen (if my memory works as it should) and the computer should recognize the device, though you won't be able to explore it with activesync.
Run the SDA_ApplicationUnlock thingy (if you need to)
now try flashing the device.
If it flashes but after 3% restart, you need to do a CID unlock right before flashing.
hope that helps.
Invalid Vendor ID
Hi MoRkusReX,
Its giving me Invalid Vendor ID. How do I CID unlock it?
Thanks,
Prateek
http://forum.xda-developers.com/showthread.php?t=330909
first post , download the last file:
Vox USPL- CID BYPASS.zip
There a Readme file in there, you should read it.
post back where you're done.
No Luck!
Hi MoRkusReX,
Since my phone is not booting into the OS thus I cannot use the UPSL_CID provided in the link.
Only once I have been able to boot into my OS and followed the instructions given in the link. The phone comes to the Linux black screen and then switchers off. Then the ROM Update Utility with which i'm trying to update the ROM gives an error that "cannot connect to the phone".
So, now I need to flash my ROM from the bootloader itself. Have managed to get mtty and connect to the phone. But even trying ResetDevice command, the phone does not boot.
Can you tell me the exact steps to flash a new ROM from the bootloader itself including CID unlocking? Can it be done??
Thanks,
Prateek
prateekswarup said:
Hi MoRkusReX,
Since my phone is not booting into the OS thus I cannot use the UPSL_CID provided in the link.
...
including CID unlocking? Can it be done??
Thanks,
Prateek
Click to expand...
Click to collapse
yes it can be done.
you don't need to boot to OS, I couldn't either. after the steps from my first post here, run the uspl_116_jockyw.bat file. follow instructions.
that will unlock the CID.
Now the VOXs' screen should be white or so... then you run the ROM update thingy.
Hi..
I connected with the usb and got the bootloader screen.
tried running the SDA unlock program...the button to unlock the phone is grayed out. Cant click on it.
Next tried running uspl_116_jockyw.bat file
..cannot connect to phone and hence copy of haret.exe did not occur and neither did pmemtest run successfully...
What am I doing wrong??
ok..
first steps again..
battery out, back in.
connect USB
CAMERA button + Turn on.
now.. does windows do that USB sound? you know.. "tu du" ?
No sound....using win 2k Nt server edition...
but has detected my phone once on that USB and then allows me to talk to the phone using mtty....as in commands like ResetDevice work on the phone using mtty..
also, cannot get into bootlaoder mode with USB plugged in...
Steps and their results:
Disabled USB connections in activesync
Booted to the bootloader (red and green and Blue screen)
Connected the USB
"USB" displays on the left hand side corner
Now tried unlocking using Apllication unlock...grayed out button...
Tried running USPL bat but stops and says phone not connected when copying haret.exe
Using windows NT server 2003
if the SDA Application unlock button is grayed, of course the USPL won't work.
why "Disabled USB connections in activesync"?
And.. I doubt this is the problem but you should check on an winXP pc, I did it on XP.
No Luck!
Tried the same with USB enabled...same result
basically the thing we need to figure out is why your computer doesn't recognize the device.
the rest is obvious.
when I go to bootloader on my device windows pops up with a message says windows found device "and it's ready to use". like when you cannot every other USB item.
have you tried doing that on an XP system?
Going to do that now....lets hope it works....
Does ur activesync turn green when u connect at bootloader?
Also, I have removed my sim and memory card...thats okay right?
yeah, I removed both of them.
and no, activesync didn't turn green, but Windows recognized the device when I turned it on. turn on the speakers and wait for that winxp "USB connected" sound.
Still No Luck!
Tried doing the same on win xp...
no luck...
it connects to win xp ans says new device found...and ur USB device is now
ready to use...
after that i try application unlock it still gives me grayed out button....
ne suggestions???
Finally....
Finally got it done...
Thanks for all the help....
I managed to cold boot into the system for one time ans then SDA unlocked it and then ran UPSL .... it ran and then balnked out...
then i disconnected the usb before the ROM update utility and unchecked the USB option in active sync...
then i flashed it with the ARA rom...
Seems to be working okay now..will test for a day and see...
thanks a lot
prateek
prateekswarup said:
Finally got it done...
then i disconnected the usb before the ROM update utility and unchecked the USB option in active sync...
prateek
Click to expand...
Click to collapse
I'm not sure this step was necessary but as long as it worked.. good times.
btw, how did you boot into the system?
kept trying hard reset and repeated booting...( it was booting 1 in 15 times type...)..and one lucky time it didnt hang..so used that window to slip in the SDA unlock and USPL..
thanks ...
you're welcome.

I-Mate Jam Bootloader & Connection error!

Hello XDA Nice Team !
By mistaken i wrote some file to my bootloader in my I-Mate Jam ..
That was after using the bad ROM : 2.03
it's the worst cooked version i saw !
Now my bootloader mode is working .. but no way to connect to PC with USB port ..
My computer does not recognize my Magican when plugged in bootloader mode anymore!
Bootloader Ver: 1.0
is there any way to fix or upgrade or restore original bootloader
Now i cant upgrade or downgrade my magican by any method
Noway to use successful connection with any roomupdate utility
Please help me to fix or restore my bootloader!
Thanks to any one read or replay or try to help or help me to resolve my problem
XDA lover
i'm sorry that happened mate...
i've had success with flash-from-bootloader attempts before, both on my Magician, when i accidentally flashed off of Vista and it'd enter the bootloader every week or on a reset using the reset hole, and also on my Wizard when i ignored warnings from WM5torage and it'd only enter the bootloader
what precisely happens when you connect to the PC, allow USB connections in AS/MDC, and let the phone enter bootloader however it does? i can just flash a rom from there, but i won't (iirc) get any reports of as recognising the device...
My experience:
1- when i plug my sd card into my jam .. usb not recognized in bootloader mood !!
2- when i use puty or roomupdate it reaches to USB> then when i type any command it does not respond !
3- i could do something .. i let my phone bootup and this i-mate logon screen stays 4ever .. i connected my ppc to pc and i could explre my imate by activesync ...
i could reach something .. when i explore my phone and remove everything from startup folder .. my phone boots .. and i can see start botton .. no touch alignment comes .. and everything works .. but.. screen is virtually reversed .. i can see the OK botton but i must click on the facing area and it be clicked ..
i think i executed some wrong hard SPL to my phone ant that happened >
is there any way to resolve this problem?
is there any way to erase flash on my I-Mate Jam????
is there any way flash my phone?
i also have prepaid JAFWM with pkey and USB cable .. no BOX ..
Help please!
that's messed up... howsabout flashing it at the point when the phone boots up? if there's an AS connection there, then it may work... i'd flash to an official rom though
Same problem , PLS Help !!!
Thx for help
You should check USB connection I think...
Try plug your battery out of device and wait a moment (e.g.10 minutes) and try again,sometimes it will be fine when you did this.
If your magician isn't detected at ALL by your PC when plugging the USB cable into it (i mean, no new hardware; no unrecognized hardware; nothing is detected in your PC when you plug the USB cable), and unless you had previously made a SD backup of your entire Flash with this procedure ( http://wiki.xda-developers.com/index.php?pagename=MagicianSDflash ), then your only option will be to build a JTAG diag cable:
Here are some general directions / ideias:
Magician JTAG pinout: http://wiki.xda-developers.com/index.php?pagename=MagicianJTAG
How to build/run the JTAG: http://wiki.xda-developers.com/index.php?pagename=DeadBoot
Photos : http://www.cf-box.com/htm_data/55/0912/1679.html
Some interesting stuff for debugging problems: http://pda2u.ru/ptopic205.html
For sure cotulla has one built so to test his ROMs + bootloader - maybe he will be willing to give you some directions if you run into problems, and above all, give you a prepared .nb0 (with the bootloader file) for your magician, which i do not know if there's one out there, extracted from an original ROM.
Anyway, you can always try and do it for yourself using itsme utilities. Follow this link: http://forum.xda-developers.com/showthread.php?t=218643
Regards
Keeper,you're awesome! I'm searching for JTAG,too
xiaojin1985 said:
You should check USB connection I think...
Try plug your battery out of device and wait a moment (e.g.10 minutes) and try again,sometimes it will be fine when you did this.
Click to expand...
Click to collapse
Dear xiaojin1985 ,
Thx for your help, But unfortunately i tried your solution but it dosnt work !
Dear Keeper,
Thanks too for your help,
and i think the solution for my problem is one of the solutions you says ( How to build/run the JTAG: ) ,
but the pictures is not available anymore , so pls can you get the pictures ?
All the pictures are in here:
http://s218.photobucket.com/albums/cc23/alex_beda/ and in attachment there's a .mth file with all the pics built-in.
Don't take it wrong what i'm about to say, but in all honesty if you can't figure this out yourself (digging up the internet for the missing pics), i would suggest that you shouldn't try this, since this ain't easy at ALL...
Just to give you some ideias, it will require you to adapt your magician test point signals (TDO;TDI; nRESET; etc,)seen on the magician pinout pic to what is said; solder very thin wires (best done with a small hot air tip); fixate the small dip switch (micro switch) to be always on; keep the USB connected...idk... plus alot of other small details which ain't easy to accomplish.
Personally i haven't tried this yet but for sure it would work
If you decide to go ahead, please post some results!
Connection error solution
this is my problem
hi all. A friend of mine gave me an S100, and after i played for a few days with it, i decided to update it's rom. A "country error" problem appeared,cause i have the greek version, so i ran MaUpgradeUt_noID.exe which completed (as showed 100% process). My (new) problem is that i cannot update anymore. Every time i enter boot menu, i ran the upgrade
(HTCMAG_ROM_WWE_O2.rar) following all the steps normally. When the device resets (so the upgrade is going to start), it's re-reseting again and showing ERROR 101 connection error. Any ideas?
Qtek Greek version
R 1.12.00
G 1337.42
D 1.12.00 WWE
P.S. apart the problem everything is function properly
and the solution
hard reset
plug usb (uncheck allow usb connection in activesynch )
run MaUpgradeUt.exe radio_1.11_greek but idont reset the qtek in first screen
and upgrate downgrate start all ok
reset
welcome screen
hard reset
plug usb (uncheck allow usb connection in activesynch )
run MaUpgradeUt.exe MagicianRadio_1.12.10. uk but idont reset the qteki n first screen
upgrate from radio 1.11 to 1.12.10
reset
welcome screen
hard reset
plug usb (uncheck allow usb connection in activesynch )
run HTCMAG_ROM_WWE_O5_251209
everything is ok my magisian run the new Rom
here..........................

[Q] Connection Error

dear all,
first at all: I´m completely new here, so hello.
I finished reading the Wiki twice, also the guide from 'mskip' (Flashing your First GSM Raphael Rom (For Noobs)). very good and sounds very easy.
now I downloaded this file: RaphaelHardSPL-Unsigned_190_1_3
when I´m trying to flash, it results in a "error 202: connection". could the windows mobile device manager be a reason, because here is just an explanation with activesync. as I use win7 64bit, activesync will not run.
I also checked lots of posts here, but did not get a right answer which could lead to a solution.
btw I have the "MDA Vario IV"-version.
greetings, tris
EDIT:
Update: Now I downloaded "TAEL ROM v6.28244 RC2".
Connected mobile to PC, waited until it is connected via 'windows mobile device manager'.
Proceeded with the update (my image is 1.69.111.6) until the screen turned black and a progress bar is shown (0%). now error 262 appeared. have to unplug USB cable, reinstall battery and restart. old system is still working. what am I doing wrong? btw, same error on my laptop with win7 32bit with fresh installed 'windows mobile device manager'.
EDIT2: okay, and same on my other laptop with winXP and activesync.
You need to flash hard spl before doing anything else. Try putting the phone into bootloader (hold volume down, then soft reset), then connect it to your PC once it's in the tricolor screen and run the hard spl exe.
After that, just flash roms off your sd card. Make sure it's FAT 32 format, rename the ruu_signed.nbh to RAPHIMG.nbh, put it on the sd card root, and then go into bootloader and follow the instructions.
volume down and reset done. phone switched to tricolor screen. then I started 'RaphaelHardSPL-Unsigned_190_1_3', phone switched to gey screen with progress bar. 30 seconds later after 0% progress: error 262 appeared
EDIT: also when trying to update via bootloader, my image (1.69.111.6) will be left blank, I can´t see the version number which is currently installed.
I just hope you have a GSM TP/RAPH...
RAPH300 -> "T-Mobile MDA Vario IV"
but why do you ask? do I have the wrong software?
Just hear of those bad incidents with CDMA phones and GSM ROMs is all...
What does it display on the bottom of the screen when you boot into the tricolor screen/bootloader before you connect it to your PC and then after?
first serial, later USB
oh my god! *facepalm* okay for all the noobs out there: look at your phone. if you use HardSPL for the first time, you have a short timeframe to confirm "unsigned access to bootloader" via touchscreen. if you don´t do so, you will result in connection error 202 / 262.
thank you all, it works

Categories

Resources