Develop Bugs

JasJar ROM update - Another brick hits the wall

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

PLEASE HELP to revive dead e-ten. HAVE MERCY!

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!

Very Strange Brick Problem

Hi guys, I've read and used the forum for years and upgraded my Cingular 8525 a ton without troubles (followed Vanx's method for vista and for upgrading), but this is the first time I'm really stuck without a clue.
I had Schaps latest OS on my phone working fine for about three days. It was charging with the USB hook up to my Computer. I pulled the USB out and the phone entered bootloader. I couldn't get it out. I tried using mtty to no avail, hard reset ect., but finally used the SD loading method to put TNT's latest on it (don't know why this worked). Here's the thing though, the phone will load fine on first load after I flash, but if I soft reset or turn the phone off and on it goes right into bootloader mode. The only way I can get it to load up again is to connect it to the computer's USB, take out the battery and then put it back in. the OS then boots up without fail.
I have read a ton and searched on the forum, and if any of you can help me understand what the hell I can do to fix my phone I would really appreciate it. I will post anymore info you guys would like, I really need your help on this one.
Thank you so much!

Hi,
I posted exactly the same problem today ! here:
http://forum.xda-developers.com/showthread.php?t=381284
It's really strange !
Dave

I've been reading everything and it appears that Schaps's new version seems to have this problem sometimes....I have the exact same problem as everyone else (mtty gives me the same results), and flashing a new rom doesn't get rid of it....I hope there is some way to fix this!
maybe I'll try flashing a new radio and see if that helps things....

I did notice that flashing Schaps 4.31 seems to include radio 1.50 and I had changed my anyway to 1.43 as I thought that was better for my area.
Not sure a radio will help. Maybe a different ROM version will ? Maybe 3.54 ?

I have flashed TNT's rom as well and it still has the problem now....I'm flashing a new radio as I type, I'm going to have to reflash the OS too, it just got stuck again as it was restarting.

Just a quick thing, I think I have solved my problem (not sure if it is permanent) by powering the phone off and on. Not resetting, just a simple power off. I spoke to a colleague who said the way it shuts down is different to soft reset (makes sense) and I haven't powered my phone off properly for a long time.
I have tried soft reset a couple of times since doing this and it hasn't gone to the bootloader screen once.
Maybe this is the simple fix.
I will keep you posted.

try to flash OFFICIAL ROM first , maybe there are few bug / missing file when error appear while flashing other ROM.
I hope it will help you both.
rgds,
ermen

Use mtty to see if yo have any bad blocks... I've had a few problems the same as yours and found I had 1 or 2 extra bad blocks, after the 2 "factory standard" bad blocks I got on my jasjam of course. hope this helps...

My fix didn't work.
Not sure what I am suppossed to see when I run "task 2a".
Has anyone had any luck fixing this ?

Universal Imate JasJar broke after error code 120 - Message USB Device not recognized

Help Help, please, I need your help please,
I am really new to this forum. I have been reading a long time the forum, and see evolution of cooked rom. I love the Tomal version 8.2 19960 that was on my Jasjar Imate. When I try to put the Vanillla version 8.2 I think that I mismatch myself, and unfortunately I should get back when I saw the error code 120. What I did, I say yes, and now have a blank screen. Nothing happens. Badly again,again, I have seen before this message USB on top and 2.01 on the bottom, but after I pull out the battery and change for another, I cannot connect anymore the device to the computer. It gives me this message <USB device not recognized> or < Windows cannot recognize a device attaching to you computer>. I kept trying all times, and now that this message, I have on my computer.
I think I did break my device myself, or I have all my stuffs in it, my passwords, my agendas, my contacts and so on.
Howw can anybody help me get out of this mess and recover my device. Please, I need help. Your help please.
Gerard

Universal Imate JasJar broke after error code 120 - Message USB Device not recognize
Thanks to post already done in this forum. I searched and brwosed all <USB not recognized> installed many utilities but without success. Finally, I discover the post < Instructions for those stuck on Boot Screen (UNI_exitbootloader> in wiki.xda-developers.com and I get results, my device has been come to life again, it was RESURRECTED.
I follow exactly, that the solutions, I tried before, but in panic and in a hurry you could miss to steps and to pay attention to the instructions, but I retry again and again and finally it did work. And I put the Tomal 8.2 19960 again on my Imate jasJar and bingo, it works.
For sure, I have not seen the blue screen <clubimate> again, but a black screen, and at the bottom te version 1.15 radio, 8.2 TML and so on, but it doesn't matter, I am so glad to see all the functions come again to life, and put my sbp backup and bingo, I do have all my data and software back, as I take precautions allways to make a backup two days ago with sbp.
MANY THANKS TO XDA-DEVELOPERS; TO XDA DEVOPERS WIKI, AND TO THE PERSONS OR THE TEAM THAT FOCUS ON ANSWERS TO HELP PEOPLE LIKE ME AND OTHERS get out freely and sincerely to theirs problems.
I hope this post will help others to keep visiting and searching xda-developers for solutions of their device needs.
All the best

Cannot HARD Reset ???!!!!!

Hi Experts,
Would like to check whether anyone out there have ever encounter such problem?
I receive a rude shock this morning when I power on my 1 week old HTC HD which reads below:
"This concludes the beta test of this software release. Thank you very much for your time and effort in helping make this a great product for our customers.
To obtain a newer release or further information, please revisit the web site that you used to obtain your current beta release."
I've flashed it with Dutty's Rom v1.8 and many other software which I use to have on my previous PDA. I son't think its coming from the ROM but maybe the software i installed. I remember the last few ones was Resco Explorer, Resco Pro viewer, FTP CLient...etc.
I tried many ways but just cannot seem to get rid of this screen as it appears right after any reset. So I decided to hard reset the phone but after going thru the procedure of holding the Vol up/down and power button, it just reboot like after a soft reset...and YES, it went back to the same screen!
Another thing, I couldn't get the phone to sync with my PC too.
What when wrong and what other method can I try? Any kind soul's advice will be greatly appreciated.
Cheers and thanks in advance.

put your phone on bootloader mode(tricolour screen),then connect your usb cable,on your tricolour screen it should show you USB,when you see it on the screen(on your phone)then you can flashing rom.
Hope this help

chg1282002 said:
put your phone on bootloader mode(tricolour screen),then connect your usb cable,on your tricolour screen it should show you USB,when you see it on the screen(on your phone)then you can flashing rom.
Hope this help
Click to expand...
Click to collapse
Thanks for the advice, you are right. Its the Time Bomb for Dutty's ROM v1.8.
Just manage to get the new ROM and flash it. Have to re-install the bunch of softwares i did earlier as i didn't read carefully that there's a time bomb.
Thanks again for the advice.
Cheers

yes it's a problem with the OS version used unknown by the cooker. It has been corrected. It is mentioned the Dutty 1.8 thread. Since Dutty 1.9 is out seems good time for an upgrade.

you have to put the CAB file on your memory card,when you flashing the new rom,you have to install all software back your phone

Can you be a bit more specific
Hi
Can you please do a little step by step thing. I am having this problem. What do i do once i am in tricolour screen after USB is displayed at bottom of screen.
Thanks in advance