Universal (JasJar) is now brick after radio update attempt

[atekant]

Ouch!!!!!

I tried the radio update, during which I got a communication error.
Now I have a brick!

The blue i-mate screen comes up. the rom info is displayed (radio still says 1.03.00) and there it is stuck.

Now what? Hard reset? (how do you hard reset from that point?)
Bootloader? How is that done?

Please help. I am off to go under my blanket to cry.

[akira]

Just retry the radio update again and again, put it in bootloader

[atekant]

How do I get bootloader? I tried the camera+power+reset combination but it still does the same thing, no bootloader menu.

Or do I have to have the bootloader files in the storage card first?
Can I also get help on how to extract the files. I don't know where the installer is putting the binaries, and at this point I would very much prefer not guessing what files to put where.

[dherrero]

try this
light + power + reset

[atekant]

try this
light + power + reset

That did something. Now I have a white screen (no light) that says "Serial" on top and "v 0. 60" at the bottom.

I have the following files in the sd:
EnterBL.exe
GetServiceData.exe
radio_.nbf
RUU.conf
RUU.dll
UI.dll


But it is not doing anything.

[dherrero]

yes, now it's in bootloader. Now connect the jasjar to your pc and execute the upgrade. If it doesnt work kill the activesync processes (WCESMgr.exe and wcescomm.exe) and repeat the upgrade

[atekant]

OK! That seemed to work, but it still gets stuck at the bootup screen (except now it shows the new radio version).

The update program asks for a hard reset, but others in another thread mentioned they did not need a hard reset after this update.

Is there something else I can try before trying a hard reset?
I just spent a week to set the damned thing to the way I like, and don't want to do all that again.

[dherrero]

I didnt hard reset. try resetting 2 or 3 times. If it doesnt work then hard reset

[atekant]

I took out the battery. Will wait a bit and try resetting a few times.
How long does it take for yours to show some activity after the rom versions are displayed?

It does take longer for this device to bootup, but I wonder if the new rom made a difference there.

[dherrero]

Usually the blue boot screen disappears in 30 seconds. But when i installed pocket plus many times it keeped freezed and a had to reset 3 o 4 times.
Is your case?

[atekant]

Usually the blue boot screen disappears in 30 seconds. But when i installed pocket plus many times it keeped freezed and a had to reset 3 o 4 times.


Hmm. I don't have pocket plus, but I have the spb gprs monitor (or whatever it is called) at the startup. Maybe that's causing a problem with the new radio.

I will reset 3 - 4 more times and then do a hard reset.
If it does not come back from hard reset, the bawling you hear all the way out there is me.

[dherrero]

he he . I ve spb gprs monitor too and it works fine.
good luck :wink:
When perform soft reset, wait 1 or 2 minutes before doing other soft reset

[atekant]

OK, now it is time to cry.
It is not coming back from hard reset either.
It is officially a brick. Any more ideas? Please?

[dherrero]

thy to make the update again. Perhaps this revives it

[akira]

if a radio update is available, maybe a rom update is around the corner.
Or just a recovery standard rom

[dherrero]

Does exits an official rom to reinstall jasjar rom?

[atekant]

I am doing the radio update again to see if that helps.

I will probably need to contact imate support for a recovery rom image I suppose. I suppose I should tell them what I was doing.
But this update was from imate, right, so I didn't do anything "wrong".

If someone has a rom, please let me know.

[atekant]

So, I am getting the runaround.
iMate says they don't have the rom to send me and I should send the device to the service center. The service center says they don't work on JasJars there.

So I am stuck with a paperweight?

[Dubi]

Just try to Hard reset .. most probably one of your already installed S/W causes the machine to hangup.... once you clear after Hard reset it should boot up.. worse while before sending it back to imate and being blamed for loading un-official and not released update... Unfortunatly there no "shipped rom" yet. you best choice to recover the paper weight is to hard reset and perhaps load S/W again. ... I have been trying to dump the rom for days with no success .. once one of us can do it we are releaseed.
Good luck

[atekant]

Just try to Hard reset .. Good luck

Already did the hard reset (many times) and nothing changed.
The problem started after the radio update, and the hard reset does not reset that update (I see the new version on startup).

Unless there is a harder reset I can do, I suppose I will have to wait for the rom.

makes a grown man cry...

[dherrero]

opppsss. Be patient. Be sure in a few days someone will leak a rom (imate, o2, tmobile, xda-developers)...and then your baby will come back to life.....Check this forum every day. I am looking for a rom too.....

[jrp]

I too seem to have a brick on performing this update.

"Updating radio: please wait ..." timed out at 0%, (Error 114: ROM Updating Error) and I now cannot get the JASJAR out of the USB/updating mode, even when I try to factory reset.

The WCESLog.log says:

09/26/2005 23:40:09.300 **************** Logging Started ****************
09/26/2005 23:40:09.300 Process C:\DOCUME~1\jrp\LOCALS~1\Temp\pft50.tmp\ROMUpgrade Ut.exe p(4768)
09/26/2005 23:40:47.301 p(2076) t(844) TraceToFile -> ERROR in CRAPISocket::WaitForDataToRecv : hr = 0x80072745 - rapisock.cpp(413)
09/26/2005 23:40:47.301 p(2076) t(844) TraceToFile -> ERROR in CRAPISocket::ReceiveBufferNoDecrypt : hr = 0x80072745 - rapisock.cpp(498)
09/26/2005 23:40:47.301 p(2076) t(844) TraceToFile -> ERROR in CRAPISocket::ReceiveBuffer : hr = 0x80072745 - rapisock.cpp(690)
09/26/2005 23:40:47.301 p(2076) t(844) TraceToFile -> ERROR in CRAPIPacket::ReadPacket : hr = 0x80072745 - rapiconnection.cpp(620)
09/26/2005 23:40:47.301 p(2076) t(844) TraceToFile -> ERROR in CRAPIDevicePrivate::HandlePackets : hr = 0x80072745 - RAPIDevicePriv.cpp(435)
09/26/2005 23:40:47.301 p(2076) t(844) TraceToFile -> ERROR in CRAPIDevicePrivate::DeviceThread : hr = 0x80072745 - RAPIDevicePriv.cpp(636)
09/26/2005 23:40:47.582 p(4192) t(6068) SyncEng -> Terminate Extension called - SyncEng will uninitialize - Service.cpp(1031)
09/26/2005 23:40:47.582 p(4192) t(6068) Notif -> CMapiSession::Unregister - entering - mbase.cpp(2089)
09/26/2005 23:40:47.582 p(4192) t(6068) Notif -> CMapiSession::Unregister(0x2244530) - m_ulSessionConnectionId = 1, m_ulStoreConnectionId = 0 - mbase.cpp(2108)
09/26/2005 23:40:47.582 p(4192) t(6068) Notif -> CMapiSession::Unregister - returning 0x0 - mbase.cpp(2150)
09/26/2005 23:40:48.144 p(4768) t(4872) TraceToFile -> ERROR in CRAPISession::CeRapiUninitInternal : hr = 0x8000ffff - rapisession.cpp(466)
09/26/2005 23:40:48.801 **************** Logging Stopped ****************
09/26/2005 23:40:49.301 p(2076) t(660) TraceToFile -> ERROR in CRAPIListener::AcceptConnection : hr = 0x8007274a - rapiconnection.cpp(268)
09/26/2005 23:40:49.301 p(2076) t(660) TraceToFile -> ERROR in CRAPIDesktopPrivate::ReceiveConnection : hr = 0x8007274a - RAPIDesktopPriv.cpp(372)
09/26/2005 23:40:49.301 p(2076) t(660) TraceToFile -> ERROR in ServerThread : hr = 0x8007274a - rapimgr.cpp(493)
09/26/2005 23:40:52.066 p(4192) t(4196) SyncEng -> Asked to Unload - Unloading - Service.cpp(223)
09/26/2005 23:40:52.066 **************** Logging Stopped ****************
09/26/2005 23:40:52.176 **************** Logging Stopped ****************
09/26/2005 23:40:52.191 **************** Logging Stopped ****************
09/26/2005 23:41:03.347 p(2076) t(792) TraceToFile -> ERROR in CRAPIListener::AcceptConnection : hr = 0x8007274a - rapiconnection.cpp(268)
09/26/2005 23:41:03.347 p(2076) t(792) TraceToFile -> ERROR in CRAPIDesktopPrivate::ReceiveConnection : hr = 0x8007274a - RAPIDesktopPriv.cpp(372)
09/26/2005 23:41:03.347 p(2076) t(792) TraceToFile -> ERROR in ServerThread : hr = 0x8007274a - rapimgr.cpp(493)
09/26/2005 23:44:58.915 **************** Logging Stopped ****************
09/26/2005 23:46:18.922 **************** Logging Started ****************
09/26/2005 23:46:18.922 Process C:\DOCUME~1\jrp\LOCALS~1\Temp\pft57.tmp\ROMUpgrade Ut.exe p(5516)
09/26/2005 23:46:23.032 p(2076) t(6096) TraceToFile -> ERROR in CRAPIListener::AcceptConnection : hr = 0x8007274a - rapiconnection.cpp(268)
09/26/2005 23:46:23.032 p(2076) t(6096) TraceToFile -> ERROR in CRAPIDesktopPrivate::ReceiveConnection : hr = 0x8007274a - RAPIDesktopPriv.cpp(372)
09/26/2005 23:46:23.032 p(2076) t(6096) TraceToFile -> ERROR in ServerThread : hr = 0x8007274a - rapimgr.cpp(493)
09/26/2005 23:51:10.374 **************** Logging Stopped ****************
09/27/2005 00:04:13.508 **************** Logging Started ****************
09/27/2005 00:04:13.508 Process C:\DOCUME~1\jrp\LOCALS~1\Temp\pft5A.tmp\ROMUpgrade Ut.exe p(1008)
09/27/2005 00:04:17.618 p(2076) t(2248) TraceToFile -> ERROR in CRAPIListener::AcceptConnection : hr = 0x8007274a - rapiconnection.cpp(268)
09/27/2005 00:04:17.618 p(2076) t(2248) TraceToFile -> ERROR in CRAPIDesktopPrivate::ReceiveConnection : hr = 0x8007274a - RAPIDesktopPriv.cpp(372)
09/27/2005 00:04:17.618 p(2076) t(2248) TraceToFile -> ERROR in ServerThread : hr = 0x8007274a - rapimgr.cpp(493)
09/27/2005 00:05:54.339 **************** Logging Stopped ****************
09/27/2005 00:06:40.840 **************** Logging Started ****************
09/27/2005 00:06:40.840 Process C:\DOCUME~1\jrp\LOCALS~1\Temp\pft5D.tmp\ROMUpgrade Ut.exe p(4992)
09/27/2005 00:06:44.950 p(2076) t(1320) TraceToFile -> ERROR in CRAPIListener::AcceptConnection : hr = 0x8007274a - rapiconnection.cpp(268)
09/27/2005 00:06:44.950 p(2076) t(1320) TraceToFile -> ERROR in CRAPIDesktopPrivate::ReceiveConnection : hr = 0x8007274a - RAPIDesktopPriv.cpp(372)
09/27/2005 00:06:44.950 p(2076) t(1320) TraceToFile -> ERROR in ServerThread : hr = 0x8007274a - rapimgr.cpp(493)
09/27/2005 00:14:58.431 **************** Logging Stopped ****************
09/27/2005 00:22:06.031 **************** Logging Started ****************
09/27/2005 00:22:06.031 Process C:\PROGRA~1\MI3AA1~1\rapimgr.exe p(1928)
09/27/2005 00:22:06.031 p(1928) t(3256) RAPIMgr -> Enabling RAPIMgr process for SessionID: 0, ProcessID: 1928 - rapimgr.cpp(1909)
09/27/2005 07:54:45.897 **************** Logging Started ****************
09/27/2005 07:54:45.897 Process C:\DOCUME~1\jrp\LOCALS~1\Temp\pft14.tmp\ROMUpgrade Ut.exe p(5324)
09/27/2005 07:54:50.162 p(1928) t(3600) TraceToFile -> ERROR in CRAPIListener::AcceptConnection : hr = 0x8007274a - rapiconnection.cpp(268)
09/27/2005 07:54:50.162 p(1928) t(3600) TraceToFile -> ERROR in CRAPIDesktopPrivate::ReceiveConnection : hr = 0x8007274a - RAPIDesktopPriv.cpp(372)
09/27/2005 07:54:50.162 p(1928) t(3600) TraceToFile -> ERROR in ServerThread : hr = 0x8007274a - rapimgr.cpp(493)
09/27/2005 07:59:41.152 **************** Logging Stopped ****************
09/27/2005 19:32:18.080 **************** Logging Started ****************
09/27/2005 19:32:18.080 Process C:\Program Files\Microsoft ActiveSync\WCESMgr.exe p(2472)
09/27/2005 19:32:22.690 **************** Logging Stopped ****************
09/27/2005 19:46:15.117 **************** Logging Started ****************
09/27/2005 19:46:15.117 Process C:\DOCUME~1\jrp\LOCALS~1\Temp\pft61.tmp\ROMUpgrade Ut.exe p(2092)
09/27/2005 19:46:19.508 p(1928) t(5828) TraceToFile -> ERROR in CRAPIListener::AcceptConnection : hr = 0x8007274a - rapiconnection.cpp(268)
09/27/2005 19:46:19.508 p(1928) t(5828) TraceToFile -> ERROR in CRAPIDesktopPrivate::ReceiveConnection : hr = 0x8007274a - RAPIDesktopPriv.cpp(372)
09/27/2005 19:46:19.508 p(1928) t(5828) TraceToFile -> ERROR in ServerThread : hr = 0x8007274a - rapimgr.cpp(493)


The error codes via google is said to mean:

WSAECONNABORTED (0x80072745)

Software caused connection abort.

An established connection was aborted by the software in your host machine, possibly due to a data transmission timeout or protocol error.


The above was the original error. The error that now seems to be:

WSAESHUTDOWN (0x8007274A)

Cannot send after socket shutdown.

A request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous shutdown call. By calling shutdown a partial close of a socket is requested, which is a signal that sending or receiving or both has been discontinued.

Another log says:

09/27/2005 19:52:23.902 - Windows CE Services (4.0.0) Communication Logging.
09/27/2005 19:52:23.902 - IrUtil: IrDA socket cannot be created, error code 10093.
09/27/2005 19:52:23.902 - Windows CE Services Communication started.
09/27/2005 19:52:23.965 - USB: CE USB Device already plugged in.
09/27/2005 19:52:23.965 - UsbComm: Open device <USB>.
09/27/2005 19:52:23.980 - Serial: Starting device detection at 115200.
09/27/2005 19:52:23.980 - UsbComm: Change DTR to 1.
09/27/2005 19:52:23.996 - Started desktop passthru TCP2UDP component
09/27/2005 19:52:23.996 - Connection: Prep for a new socket connection.
09/27/2005 19:52:23.996 - UsbComm: Change DTR to 1.
09/27/2005 19:58:31.753 - UsbComm: Change DTR to 0.
09/27/2005 19:58:31.753 - UsbComm: Closed device.
09/27/2005 19:58:31.753 - USB: Event 32772, name \\?\USB#Vid_045e&Pid_00ce#6&389b0f7&0&3#{25dbce51-6c8f-4a72-8a6d-b54c2b4fc835}
09/27/2005 19:58:31.769 - USB: Device Remove Complete notification

I tried installing on a machine without ActiveSync installed, but I get an error saying that Activesync 3.7 is required.

Could it be my anti-virus / firewall software (I am running XP SP2 and Norton)?

Suggestions? Is there a way of doing the update via the SD card, eg?

[jrp]

:D Well I have a live JasJar.

Here's what I did:

Uninstalled ActiveSync 4 and rebooted.

Installed ActiveSync 4.1 prerelease.

Connected to the USB port on the PC, rather than the docking station.

I had previously hard reset the device, so when it came up, I had to reset it from scratch.

[atekant]

Unfortunately AS 4.1 did not help me. I am still in the same situation.
I couldn't really use AS anyways because the machine never boots into the OS. The only thing that seems to work is the bootloader.

I really need a full rom image and/or a way to reset the device harder than the hard reset (with all this talk about WM5 not really clearing everything)

Anybody getting closer to dumping out the full rom out there?

[jrp]

I was in the same situation -- bootloader only. Sorry that it didn't work for you.

[atekant]

I was in the same situation -- bootloader only

What exactly did you do with AS 4.1 then?

When I am in bootloader and plug it in, I get the USB device notification from the PC, but AS does not kick in. I run the rom update exe and that does not seem to care about AS, as I had tried uninstalling AS and running the update without.

[jrp]

I did nothing with it. It may well be that plugging the JASJAR into a different USB port did the trick.

[Perttir]

I was also in in boot loader loop - nothing seemed to help. Uninstalling AS 4.1 and reinstalling it again helped to regocnise the device. So I'm up and running now !

[decebal]

how did you get out from bootloader ? can you please us step by step. i have an mda pro.

thanks

[Perttir]

I connected JASJAR (while in loader loop) to XP. => XP recognises the usb device (if not try by softresetting your PDA). Got Active sync = not connected. Uninstalled AS (in my case 4.1). Reinstalled AS and rerun the upgrade. That solved the problem (at least in my case) !