I have a PDA2k and it doesnt go on so i tried to update it with the upgrade utility but it hangs on getting the information from the device. Then it pops a error 201 that it cant connect to device.
I tried different ports,Restarting and taking out the battery.
IS there a way i can just have the utility write to the device without getting the device information?
Good if you can provide more information about your unit.
Look at the specific threat for flashing the ROM would be good. Most of the case, flashing technique used here doesn't require the knowledge of the unit being flashed. Which is good and bad. Good, it can write onto any unit, dead of alive. Bad, it might permanently damage it. Just make sure you have your unit matched against the flashing program that has been proven to work.
its the sx66 Simens its the same as the PDA2k without the camera
Related
I have downloaded the new Shipping ROM update from ClubImate.com (uni_cdl-me_11238_132_10301_ship.exe) and tried installing it onto my JasJar with a horrible result: it's now only good to use as a paper weight Initially everything looked fine; the ROM utility detected the device and correctly displayed the existing versions of CE image, Device Extended image and Device Radio image, along with the versions it was going to upgrade to. It reset the JasJar (what I'd think was erasing the current versions), but has since been unable to install the upgraded versions. Result: a (virtually) dead JasJar :evil:
I have done the following in order to try and get it up and running again:
1) Several soft and hard resets - the best effort is a screen (with no back light) saying 'Serial' at the top and 'v0.60' at the bottom.
2) Uninstalled ActiveSync and tried reinstalling both version 4.10 and 4.1
3) I have tried to complete the upgrade procedure on two different PCs; one running WinXP SP2 and Win2K SP4.
Despite these efforts, the ROM installation utility is unable to detect the device (ActiveSync's device detection has been dodgy from the word get-go, despite WinXP detecting it every single time - although saying it's unable to identify it) resulting in the following error message from the ROM Update Utility:
In the Dialog's title bar: "R:3030 D:21200 U:11000 P:857873 - CB1" and the message "Error 101: Connection Error".
Please, please, please (with sugar ontop); can anyone of all you clever people out there offer some help or hope?
Thank you very much :!:
sure you did hardresets?
You´re really stuck in bootloader? strange... if it happens to me, i just do the standard hardreset: keep the 2 softbuttons pressed, resest with the stylus, and the confirm with 0 (zero). did you do that?
Yup - really stuck
Yes, I'm afraid the normal hard reset (Soft keys+Stylus reset) followed by entering '0' to confirm the reset, only brings me back to the boot loader...
same here
Help?
I had the same problem once with my himalaya and it was due to a firewall and virusscanner.
I turned them off- Look in your taskmanager that there isn't still running a service in the background. then I reinstalled the update and tried i new hard reset.
This worked for me I hope it will help you too
Good luck
1. pres ctl alt sup
2. kill wcesMgr.exe and wcscomm.exe
3. Connect your jasjas
4. Now your bootloader must show USB in the screen
5. Run the upgrade.
It should works...
Good luck
here it is
http://forum.xda-developers.com/viewtopic.php?p=161210#161210
Dear oddball,
Did you find solution to your problem?
I have the same problem!
dherrero's solution did not work for me.
Hope to hear another solution.
Thanks
Sorted...
First of all, thanks a lot to everyone who tried to lend a helping hand (what an absolutely brilliant forum this is!!! ).
However, neither of the solutions suggested worked for me, as I after lots more trial and error, worked out that the problem had to be hardware related. And I'm pleased to say that fault wasn't in the JasJar; in fact it was down to an un-original sync cable :idea: ! I managed to lose the one that came with the device (along with the CD and everything else that was in the box ) and after consulting Club imate support, was (obviously wrongly) told that any standard min-USB cable would do the trick. Ordered a new cable from where I bought the JasJar, and hey presto, problem solved. ROM upgrade worked without a hitch on first attempt - I didn't even have to disable my anti-virus or fire-wall software.
It might not be the solution for everyone else who seems to be struggling, but it worked for me, so if you've run out of options, it's worth a go.
Again, thanks a lot - and good luck to those still seeking a solution.
I have the sam problem
CRAP cant work it out
Hi,
Had the same problem..
- flashing ROM said 100% successful, but after power+reset still got "serial v1.00"
- tried different ROMs, no luck
- tried power and hard reset, no luck
- then tried JasJar ROM again, no luck
- but then I tried the radio ROM flash and the power-reset brought it to life.
So I recommend trying
a) just the radio update first, if no luck
b) jasjar THEN radio
See how you go.
Michael
my mda pro is be gone (turn on)
thank for everyone!
my jj is in bootload three day!cannt turn on
today i just update firmware of xda exec,finished! i do soft reset !my jj is be come back!
now i try update to cht! good luck!!
now my jj is cht!
if you want to update lanuage :
1:download rom and rar a new folder
2:delet firmware file
3:use no_id.exe to update,
maybe 5min finished ,it is fast!
then kick -and- and reset (hard reset)
now become cht version!
good luck
Hi guys. I know I know, wrong place, but maybe some one here could help too! Just maybe.. You guys are very smart peps here. You've helped me with many XDA's I own. And I'm just hoping you wouldn't let me down this time too. Any way I’ve killed my eten (typhoon my guide m500 German) and hoping some one could help me to bring it back to life. Please understand that I have exhausted all my resources in order to find the solution my self but came up empty handed. I have read every single post in this forum as well as few others in order to find the solution. And now I am hoping that some one could help. I may have overlooked some little but important piece of info. Please except my apologies if this request may be annoying.
This is what happened and what I’ve done about it.
I’ve got Typhoon MyGuide m500 (E-Ten m500) Original rom was German.
The reason I say “was” is since I had german OS that I can’t read it I wanted to flash the device with WWE Rom. But the device would not accept any other rom and at the time of reflashing through RUU, I get message “the os image is not compatible with your device”. I understand a lot of people have this problem, but still, some succeed. I have tried all the possible roms that are available there. I’m sure you’ve heard that before too Finally I’ve succeeded in flashing CHT WM2003 rom that came with WM 5 Rom update for downgrade purposes. But, I can’t read chinese either so I tried to flash wwe at this time. Hoping that chinese rom would allow upgrades in different language. But the upgrade went bad I’ve ended up with formatted e-ten with no OS installed. It was only showing white screen when turned on or it would boot into boot loader when soft reset and power was pressed.
At that time, since the device would not boot and I couldn’t active sync it, I’ve tried SD flashing with RescueDLX.bin. As well USB download utility. It flashed the device, but I was stuck at the green m500 screen when tried booting. So that didn’t work either. I’ve tried SD flashing with temp.dat saved as .bin from all possible roms, including the first chineese that worked once for me. But again, I got “the os image is not compatible with your device”
Well, here is where I’ve screwed up big time. Since the rescueDLX.bin was actually flashing into my device, and I was not getting “the os image is not compatible with your device” message, I’ve opened the rescueDLX.bin with Hex Editor, copied first 400 bytes of the header, then using Hex Editor opened the temp.dat from WWE rom update that I wanted to use and pasted this 400 bytes from rescuedlx.bin over the first 400 bytes of temp.dat file and saved it as a bin. Then copied on SD card, put it in the device, entered into the boot loader and started flashing process. Amazingly, I didn’t get the “the os image is not compatible with your device” message! But worst thing happened The boot loader was going through all the check lists and everything was ok but device froze at the last one, “looking for FPTP” or something like that.. Apperantly I copied to much stuff or it just plain incompatible. Well, now my device would not even load into the boot loader! I think I’ve erased it too So no more updating for me, that is for a sure not through RUU, not through USB Update Utility that I found on etens forum, and not even through SD with devices internal boot loader. There isn’t one anymore
So here we go, I’ve got really nice looking paper weight Oh, and I can use it as a flash light too When turned on, the screen lights up with bright white light
So any way, can any body help?! Is there any way to revive this thing? Or the road is straight to manufacturer? I don’t think I even have a warranty on this device; it’s in brand new condition, but its second hand. So I have only one hope that some smart gurus of this forum would show mercy and would help! Like I said, I’ve researched all over the internet, all forums, even xda developers and spv developers forums, but this is different device. Deferent rules… But I know it’s doable, I’ve seen posts that others did it! So please, share how you guys did it!
Thank you in advance. And sorry for such a long post!
Hi All,
Hope you can help. Have played with multitued of roms, crossbow and aku3.x.. changed radios alot. Now I can't seem to change the rom anymore, using official files or maupgradeut tool. Get error 114. It says about to update.. the progress bar never moves and after half minute will time out with the error. Changing CE and ExtRom is fine.
Any ideas?
did you connect your device trough a usb hub or somekind maybe?
I had that problem.
try this:
- Put the device in BL
- start your AC on your pc and disable all connection options
- connect the device on a free usb port, directly on the pc
this should work
Also please use the original cable. This is particularly important for Radio upgrade. If all else please try upgrading from a different PC.
cheers for tips. I will try these.. I think I've poached a cable from a pc peripheral as I'm at work :-D
lx_t said:
Hi All,
Hope you can help. Have played with multitued of roms, crossbow and aku3.x.. changed radios alot. Now I can't seem to change the rom anymore, using official files or maupgradeut tool. Get error 114. It says about to update.. the progress bar never moves and after half minute will time out with the error. Changing CE and ExtRom is fine.
Any ideas?
Click to expand...
Click to collapse
i'm having the same problem and sadly i want to aware you .... there is no solution for this till now! i have spent a lot of time by now and my universal is still a brick.... just like somebody said... a 1000$ paper weight
tell me if you get through of this.... i know the solution is to get the mother board changed.......
farehmani
Did your IMEI get changed already once? (motherboard)
My Uni died on me after flashing I think it was a Imate rom and it went back for repairs, they changed the board (therefore the Imei).
Since then no problems anymore.
Could be that your device is still original, I think the early devices atleast had problems with a corrupt eeprom or something which could lockup after flashing.
Has anyone had any experience trying to upgrade software and end up with no OS at all? Only the USB and Serial prompts appear-somewhat like the phone was formatted but was left hanging without an OS.
Maybe some one can give some advice on how to set it back to at least its default state? thanks
that is a common problem, because most people don't know exactly what they are doing.
so, the first thing, you should think about is: is your device GSM or CDMA. if it is a CDMA device, there is no point trying to upgrade it with a blueangel rom, as it is a harrier then, and that just doesn't work. in that case you should visit xplode's shipped rom archive here:
http://firmware.atspace.com/
and download your shipped harrier (2nd device from the left) rom and flash that.
before doing that you should also think about what PC os you are running, because if it is vista or 7, upgrading is not as easy, as you might have thought before. in that case you should look at this:
http://wiki.xda-developers.com/index.php?pagename=HTC_Blueangel_WM6_WizzardUpgrade4_Vista
and this:
http://wiki.xda-developers.com/index.php?pagename=HTC_Blueangel_WM6_WizzardUpgrade4_Vista_Pic
because vista determines, that something changes about your device during the process of upgrading, and downloads a new driver, which cuts the connection to the phone, so flashing wouldn't finish, like the wizard tells you: "under no circumstances shall you cut the connection while upgrading, or your phone might be damaged". (btw, it's not damaged, relaxed )
if both those options are not the case, so you do have a blueangel and you use xp, something else went wrong, don't know what, but also that is fixable. just download mtty and flash the rom with that. it is the common thing to do, when you are "stuck in bootloader" (a nice phrase for googling by the way )
but if it was either number 1 or 2, you are not actually stuck in bootloader and can just go on flashing any rom. but just to make sure, this time you know what you are doing, please also visit this link, and make sure you go through all the steps and don't skip anything:
http://wiki.xda-developers.com/index.php?pagename=HTC_Blueangel_WM6_WizzardUpgrade1_WM2003SE0
this is a step by step wizard for upgrading, about at the step where you are. the only options i checked so far are, that you want to upgrade to wm6, coming from wm2003.
you have a lot to read and to work through now, so have fun and good luck.
Chef_Tony
Okay. I have in my possession an LG-v495 that I received, fully functioning, a few weeks ago. I attempted to, using the information I could find on various similar models, which was not a lot mind, unlock the device (Successfully), and flash stock android 4.4.2 on to the tablet using methods that I found on this form. The only information I could find at the time were for various other models like the v490, v498 or similar. These are functionally identical devices on a hardware level, the only differences being what carrier software was stapled on at the last minute.
After I attempted this Flash, by rooting the phone, then putting it in download mode, then loading the stock rom utilizing LG's developer tools, the devices boots into the LG welcome/setup-device screen, like it would had I turned on a new device, and then forcibly turns the screen off. It is important to note, my computer still recognizes the device as present and on, but at no point during the process can i interact with the screen in any way, or influence the device beyond forcibly resetting it. I can still get into download mode, but, as part of the process involved "factory resetting the device" after flashing the new firmware, the device no longer reads as Rooted.
This device is of vital importance to me, as I have been on the verge of homelessness for a while now, and do not possess a phone. I cannot get the device replaced, as it is 1 month out of warranty, and cannot afford to buy another one. Is there anything at all that I can to get this device working. I am a software engineer, and not above getting my hands dirty with ADB and the like, but there is a lot of conflicting information out there, and I get the impression that it was trusting the wrong information that got me into this mess in the first place. Any assistance that you can give me would be greatly appreciated.
I apologize for the wall of text, and appreciate you all taking the time to read this.
Was it by chance a US Cellular Gpad? My pad is listed as a v495 but it takes the firmware for a UK495. They are not the same machine.
Yes. This is the US Model, and I am familiar with the difference in hardware