Totaly screwed now...

[ID64]

ok, now I am totaly screwed.... imate stuck in loading screen with version numbers etc... Not going further and bootloader not available.... Is there any way to communicate with unit while it's in this mode?

[Victor]

what you are saying is unclear. Does your device say "Serial" (or "USB") on top with "V 1.06" on the bottom?

If so, you ARE in bootloader mode. If not, then please specify what it actually says on the screen

[ID64]

no, it's not in bootlader mode. it's in Tmobile screen at the bottom it says R 1.12.00
G blah
D blah

it stuck there. and I can't enter bootloader mode. looks like it's totaly dead

[Victor]

What happens when you try to enter bootloader (Power - Action - stylus)?
What happens when you try to press (Camera - Record - Stylus)?

[Ivan_R]

F%@#&!?G FREAK ROM!! :evil:

[Victor]

Please calm down... in a day or two, this problem will be solved and everyone will probably be back to where they were

((and a lot smarter than they were too))

[ID64]

What happens when you try to enter bootloader (Power - Action - stylus)?
What happens when you try to press (Camera - Record - Stylus)?


It both cases it still sits in this screen :(

[Victor]

Try removing the battery and waiting for a period of time (20 Mins ??)

Then try the two things again (first without the battery -- for the heck of it -- and then replace the battery and try them)

...obviously, you need to remove it from the charger too :wink:

[Victor]

to be clear... nothing is expected to happen when you try to do these without the battery in, except perhaps (??) clear out any remaining charge held in capacitance, if any.

Kinda like removing the batteries in the remote control of a TV and then pushing a button on it (there is always enough charge in the capacitors for a single push/command to the TV

[Rudegar]

that once happent to me
and softreset dident help
so i did a hardreset and that fixed it
fixed my data too though :/

[ID64]

that once happent to me
and softreset dident help
so i did a hardreset and that fixed it
fixed my data too though :/

nothing happenes :( Sent email to imate tech support. I am not sure if they going to warranty unit with Tmobile betta screen stuck on IMATE. looks like i am short 700 USD........ :( :( :( :( :(

[ID64]

Is there any way to communicate with XDA2 when it stuck in this loading screen? Terminal via serial cable doesn't work. anyother low level programs are out there? please, help.

[Victor]

Have figured out that the problem is in the Bootloader. If there is a way to (and I know there is) revert to an older Bootloader version, then the problems will all be solved.

[cairo31male]

OK Guys. Problem Solved : Dead devices due to tmob 1.72 + Downgrade

http://forum.xda-developers.com/viewtopic.php?t=8606

[ID64]

That's great, but unfortunately my device is one step more screwed that others - no bootloader :( not even working Windows now.

Is there any way to boot directly from SD card?

[vwonges]

victor,
can you upgrade or downgrade the bootloader ? If you can, HOW? please post the way to upgrade or to downgrade the bootloader. :shock:

[ranger]

ID64,

I had an XDA I and wiped the bootloader by accident. As far as I know, you have only two options. The first one is JTAG [http://www.xda-developers.com/jtag/] but I don't think the boards have been documented yet for XDA II. The other option is to bring it back to where you bought it from. Tell them there's something wrong with it and play dumb. If you're lucky they might replace it for you, if they assume that you are still within warranty.

[Victor]

Yes, there is a way to upgrade/downgrade the Bootloader. I just don't know how.

The bootloader is locked, that is the problem you have (except for those who cannot access the bootloader).

If you know the right syntax and use the password to the bootloader (it is BOOTLOADER), you can load the proper ROM back using the "LNB" command. However, they have changed the syntax since ITSME's doc on the subject, or he mis-documented the syntax to the bootloader. Or at least his syntax was wrong with 1.06 version.

I got mine fixed, but I have means available that 99.9% of the people out there do not have. If I knew more, I would tell you about the percise syntax in the bootloader -- but alas, I am not a developer.

[ID64]

Yes, there is a way to upgrade/downgrade the Bootloader. I just don't know how.

The bootloader is locked, that is the problem you have (except for those who cannot access the bootloader).

If you know the right syntax and use the password to the bootloader (it is BOOTLOADER), you can load the proper ROM back using the "LNB" command. However, they have changed the syntax since ITSME's doc on the subject, or he mis-documented the syntax to the bootloader. Or at least his syntax was wrong with 1.06 version.

I got mine fixed, but I have means available that 99.9% of the people out there do not have. If I knew more, I would tell you about the percise syntax in the bootloader -- but alas, I am not a developer.

Thanks for the reply, Victor. When you talking about commands for bootloder what connection to PC you are talking about? Serial or jtag?

[Victor]

I am referring to the device in the cradle, in bootloader mode. The screen in this mode should read "USB" on top and "V.1.06" (or whatever version) on the bottom. Very hard to read, as there is no backlight.

Anyhow, just for fun.... why don't you try the following:

Uncheck the USB option in Active Sync Connection Settings
Cold boot your system (hard reset)
place the device in the cradle
run the communications software (found on this forum)

When asked which COM port to use, click on the down arrow and see if there is a USB port listed (should be top entry in list).

If so... click it. (if not, you are basically done)
After clicked, then hit return (enter) on the pc a few times.

Anything happen?

[ID64]

I am referring to the device in the cradle, in bootloader mode. The screen in this mode should read "USB" on top and "V.1.06" (or whatever version) on the bottom. Very hard to read, as there is no backlight.

Anyhow, just for fun.... why don't you try the following:

Uncheck the USB option in Active Sync Connection Settings
Cold boot your system (hard reset)
place the device in the cradle
run the communications software (found on this forum)

When asked which COM port to use, click on the down arrow and see if there is a USB port listed (should be top entry in list).


If so... click it. (if not, you are basically done)
After clicked, then hit return (enter) on the pc a few times.

Anything happen?

My bootlader is dead, so I can do the first thing.

To what communitcation software you are reffering to? My device wont even recognized by hyperterminal connected by a serial cable

[Victor]

I am referring to the mtty tool found here

http://wiki.xda-developers.com/wiki/HimalayaBootloader

Try to connect through the USB Port to the device using this tool and see what happens .. but do it with Active Sync USB disabled and after a Hard Reset (without waiting too long)

[ID64]

I am referring to the mtty tool found here

http://wiki.xda-developers.com/wiki/HimalayaBootloader

Try to connect through the USB Port to the device using this tool and see what happens .. but do it with Active Sync USB disabled and after a Hard Reset (without waiting too long)

Thanks, Victor. But nothing happenes, I even used serial cable and nada...

It's time to send my imate for service. But where? Carrier Devices tech support is abit mmm.... slow.

[ID64]

Well, my iMATE is on it's way to Dubai service centre. I have to tell you, that I am very happy with imate tech support. Response wast fast and I got RMA in one day. Wonder, how long it will take to get it back...

[fedup]

I had the same problem several time and the only way trying to solving it it is putting the battery out. It is really deceiving that a device like this simply goes stuck for unknown reason, you cannot rely on it. I've lost several times all data. See "unknonw sim status causes several serious crashes" under "Using it" section

[ID64]

Actually, I was very happy with the device in genreal before this unfortunate upgrade. It was very reliable and stable, as well as my first iMATE I've had 4 monhts ago.