FOR ALL THOSE WHO STUCK IN THE BOOT SCREEN OF UNIVERSAL

[hdubli]

This is based on my experience with two UNis..one Exec and other JASJAR..both had same problem...this is how I solved :

-Put yr device in bootloader Mode
-Disable USB in Active Sync
-Now connect woth USB cable and open mtty utility
-Select the "WESUSB... " port
-You shall see a blank white screen..press Enter to get "USB>"
-Then type ( as BUzz has informed) set 14 0
(here I wud like to inform that after doing the above I did not get success so I typed set 14 10,then set 14 9 for two three times)
-Then I ran the ROM Upgrade directly(After enbabling the USB)
-I then followed the procedure as informed on the COngratulations Screen that is hold the two "-" buttons and soft reset and then pressed 0
-I got them back to normal..


I hope this helps to all my friends...Pls feel free..pls do not trouble our Buzz..he might be busy in inventing something more to our devices

[simon_darley]

could you please clarify this statement

(here I wud like to inform that after doing the above I did not get success so I typed set 14 10,then set 14 9 for two three times)

in particular the bit "for two three times"

ta

[hdubli]

I meant that after typing set 14 0 did not help so in frsutration I thoight of typing something more like set 14 10, set 14 9 set 14 20 also...then I did the flashing again...I got the success...

my msn : h_dubli@hotmail.com pls add me...I am normally on line 07.30 to 09.30 IST and 22.00 onwards IST(Indian Std Time).I can help u out

[jmcl]

great info. I suggest the following as well:

- If after upgrading and reset, still see Serial 1.0, UpGRADE THE RADIO, and reset again (for mor info search for "MDA PRO is alive"). It will work.
- And, as Dherrero said to me, Dont' worry! there is almost always a solution for your problem (99%).
;)

[mcackay]

Hi -

My Jasjar is now sitting endlessly at the blue imate boot screen, showing the new ROM version numbers. Help!

I've tried "hdubli"s suggestions, but to no avail (although i still have no idea what "set 14 0" was meant to do, or what i was meant to see on screen afterwards!) I also tried "set 14 10", "set 14 9", "set 14 20"...

I've tried reflashing down to the older ROM version, then back to the latest ROM(several times now).

I've tried the following update: http://forum.xda-developers.com/viewtopic.php?t=42992&highlight=bootloader

I'm re-applying the imate official rom now, as i don't know what the above version one is.

But it's still hanging at the blue startup screen...

- It seems to be ROM version independent
- what else is there that i can flash? could the bootloader be corrupt or something?

- iMate online support walked me through reapplying from bootloader, and removing the battery, but that was all they could offer. THen referred me to a 'local service agent'.... but that could take days...

Can anyone help?

/Mark

[KT]

Hi -

My Jasjar is now sitting endlessly at the blue imate boot screen, showing the new ROM version numbers. Help!

I've tried "hdubli"s suggestions, but to no avail (although i still have no idea what "set 14 0" was meant to do, or what i was meant to see on screen afterwards!) I also tried "set 14 10", "set 14 9", "set 14 20"...

I've tried reflashing down to the older ROM version, then back to the latest ROM(several times now).

I've tried the following update: http://forum.xda-developers.com/viewtopic.php?t=42992&highlight=bootloader

I'm re-applying the imate official rom now, as i don't know what the above version one is.

But it's still hanging at the blue startup screen...

- It seems to be ROM version independent
- what else is there that i can flash? could the bootloader be corrupt or something?

- iMate online support walked me through reapplying from bootloader, and removing the battery, but that was all they could offer. THen referred me to a 'local service agent'.... but that could take days...

Can anyone help?

/Mark

Hi all,

I have been following almost every thread of this forum for the past week or so, && this is the first time i have come across another person who is suffering from the same problem... Hi Mcackay... I have the EXACT same problem... I have been given some suggestions which i shall try soon... If anything atall works i shall let you know bro... && please inform me if you find any solution...

mOrph

[hdubli]

If one has tried to update Atom/Wizard ROm...will certainly notice that the upgrade process doesn't start unless the battery is >50%..so this is the biggest clue.

Those who want to upgrade make sure that their battery is more than 50%..no one will face the problem.

So those huys who are already in problems...shd try to get their friend's battery which is fully charged and then do the ROM Update..

This will certainly solve their problems.

[hollytree]

I installed the new ROM but every time it just said 'congratulations all done etc.....' and I could not get out of bootloader mode.
I did a hard reset to get the white screen and then had the choice of X or 0, but both put me back at the grey screen (where it is just possible to read USB and serial 1.0).
After doing this 5 or 6 times, I found the old radio 1.06 upgrade and ran that, and on completion it allowed the universal to start up AND the ROM files that I had sucessfully installed (see above) were there.
Only problem is I now have 1.06 radio and not 1.09, but i can do an upgrade for just that later.
steve

[angeln20]

i cannot make it start i have tried to write in mtty set 14 0 , set 14 9, set 14 20 but nothing.also i ave triedto install almost all rom but everytime stucks in the blue i mate image,any ideas please???

[KT]

i cannot make it start i have tried to write in mtty set 14 0 , set 14 9, set 14 20 but nothing.also i ave triedto install almost all rom but everytime stucks in the blue i mate image,any ideas please???
Hi buddy... Am facing the same problem for the past 15 days... My JASJAR has been stuck on the blue imate splashscreen mode... I too have tried flashing the device with all possible ROMS but to no use... One thing that we can conclude is that the problem is ROM independent... Lets work on this together.. There are other 2-3 people on this forum who are facing this same problem... Lets put our heads together && work out a solution... If there is any success at my end, i will update you asap.. PLEASE do the same...

Regards,
mOrph

[azhar63]

Almost the same problem I have with MDA Compact II Now the device is dead the screen blinks. somebody told me that there is a software that works on dos mode and reset all to bring it boot loader & and so there is a bottun inside the device to to clear every thing. But I don't know how???

[olliesshop]

This all started when I used the official imate Jasjar ROM upgrade from the clubimate site (since I have an imate Jasjar). I've come a long way in understanding how to manually upgrade the ROM and have tried numerous ROMs, radios, etc. and still won't go past the splash screen. I'm hoping I we can figure it out today.

[angeln20]

no luck yet.i cannot to something and i am afraid that the battery will empty.....

[olliesshop]

I keep on getting disonnected from their support, but so far they said "its just and error but i will help you to fix it so please me the IMEI number" so I gave him my IMEI number and he's supposed to email me the fix. We'll see ..... I'm keeping my fingers crossed.

[Asukal]

i cannot make it start i have tried to write in mtty set 14 0 , set 14 9, set 14 20 but nothing.also i ave triedto install almost all rom but everytime stucks in the blue i mate image,any ideas please???
Hi buddy... Am facing the same problem for the past 15 days... My JASJAR has been stuck on the blue imate splashscreen mode... I too have tried flashing the device with all possible ROMS but to no use... One thing that we can conclude is that the problem is ROM independent... Lets work on this together.. There are other 2-3 people on this forum who are facing this same problem... Lets put our heads together && work out a solution... If there is any success at my end, i will update you asap.. PLEASE do the same...

Regards,
mOrph

i agree this, i also got problem with my exec,
some of thread told us use mtty set 14 0, or just falsh single rom such llike radio rom or nk.nbf, tied many time, tried may ways of reset, boot options, other version and kinds of roms, still no work for me,

[hdubli]

I did solve the problem with 3 Unis by what I hv explained above...I think it is Flash Chip related issue...after upgrade it is just not getting a kind of trigger to load the OS..This time I am really struggling with morphosin's JASJAR...it is lying at my place for past 2 days...but no luck so far.

I hv also tried following mtty commands and the results are as explained

task 28
DOC_format failed

task 0
task 7 0/1
made the Uni hang...it did not lock/unlock the ROM

rtask 0/1/3/4
In all these cases it did reset the radio...also had the Radio ROM run but still no effect on booting

May be buzz can help now as increasing number of people are getting this
problem..

I also think of some kind of Super CID in new ROMs which need to be unlocked before doing the upgrade..

:cry:

[Asukal]

@hdubli
thanks but many of my friends are helped by your post,too.

Also one of my friend, receovered by useing command with PlatformBuilder from PC, he reported me like that.

[KT]

@hdubli
thanks but many of my friends are helped by your post,too.

Also one of my friend, receovered by useing command with PlatformBuilder from PC, he reported me like that.

Hi Asukal...

Can you please elaborate the "platform builder recovery method"... I think thats the only thing left to do now...

Thanks...

[olliesshop]

I've made some progress with imate technical support, but still no solution. So far it's the standard bootloader - USB - Load the ROM response. I'm hoping they'll email me back today with a real answer. I'll keep you all posted.

[Pegasus626]

This is based on my experience with two UNis..one Exec and other JASJAR..both had same problem...this is how I solved :

-Put yr device in bootloader Mode
-Disable USB in Active Sync
-Now connect woth USB cable and open mtty utility
-Select the "WESUSB... " port
-You shall see a blank white screen..press Enter to get "USB>"
-Then type ( as BUzz has informed) set 14 0
(here I wud like to inform that after doing the above I did not get success so I typed set 14 10,then set 14 9 for two three times)
-Then I ran the ROM Upgrade directly(After enbabling the USB)
-I then followed the procedure as informed on the COngratulations Screen that is hold the two "-" buttons and soft reset and then pressed 0
-I got them back to normal..


I hope this helps to all my friends...Pls feel free..pls do not trouble our Buzz..he might be busy in inventing something more to our devices

I also have been stuck in bootloader mode for days, but by following the above it sorts it every time.

I am using mtty v1.42 and simply select USB get the USB> prompt then type SET 14 0 then return. I then see HTCUSB> and close the program

I then cold boot and I am back in business. This is 100% repaeatable

Hope this helps

Stu

[cr2]

task 28
DOC_format failed


This is the best way to make your Universal unbootable
forever!

[hdubli]

Don't know..but clear reg hive and format storage options, too did not have any effect...and this was before applying the task 28 command

Some kind of Bad sector in boot area of the flash ROM(Just guesing)

[Asukal]

@hdubli
thanks but many of my friends are helped by your post,too.

Also one of my friend, receovered by useing command with PlatformBuilder from PC, he reported me like that.

Hi Asukal...

Can you please elaborate the "platform builder recovery method"... I think thats the only thing left to do now...

Thanks...

just back from work, and i am waiting the instruction from friend,

upon i reciept from him, i try and report here.

PLS wait.

[olliesshop]

This is based on my experience with two UNis..one Exec and other JASJAR..both had same problem...this is how I solved :

-Put yr device in bootloader Mode
-Disable USB in Active Sync
-Now connect woth USB cable and open mtty utility
-Select the "WESUSB... " port
-You shall see a blank white screen..press Enter to get "USB>"
-Then type ( as BUzz has informed) set 14 0
(here I wud like to inform that after doing the above I did not get success so I typed set 14 10,then set 14 9 for two three times)
-Then I ran the ROM Upgrade directly(After enbabling the USB)
-I then followed the procedure as informed on the COngratulations Screen that is hold the two "-" buttons and soft reset and then pressed 0
-I got them back to normal..


I hope this helps to all my friends...Pls feel free..pls do not trouble our Buzz..he might be busy in inventing something more to our devices

I also have been stuck in bootloader mode for days, but by following the above it sorts it every time.

I am using mtty v1.42 and simply select USB get the USB> prompt then type SET 14 0 then return. I then see HTCUSB> and close the program

I then cold boot and I am back in business. This is 100% repaeatable

Hope this helps

Stu


When I try set 14 0 I get

USB>set 14 0
HTCST ÚÈÒHTCEUSB>

Is that ok? Since I've tried it after doing this and still get stuck on the blue splash screen.

Is the blue splash screen also called the bootloader screen? I thought the bootloader screen was the non-lit screen with Serial at the top and v06.0 at the bottom.

I'm going to try it again to make sure. Also, FYI, nothing back from imate techsupport yet ... big suprise !!!

[olliesshop]

Just letting you know I tried the set 14 0 again with mtty and it will not connect to the Jasjar (Error 101 Connection Error) . If I just connect without the set 14 0 it does the connection just fine through the congratulation screen. I also tried just leaving the mtty screen as USB> and it also gives Error 101.

Sorry for being confused, but it seems that the mtty set 14 0 will not solve anything with folks with the blue splash screen, since it's allready flashing the ROM through the Congratulations screen without mtty.

[angeln20]

@hdubli
thanks but many of my friends are helped by your post,too.

Also one of my friend, receovered by useing command with PlatformBuilder from PC, he reported me like that.

Hi Asukal...

Can you please elaborate the "platform builder recovery method"... I think thats the only thing left to do now...

Thanks...

just back from work, and i am waiting the instruction from friend,

upon i reciept from him, i try and report here.

PLS wait.

any info my friend????

[buzz_lightyear]

hi all,
set 14 0
.. is to tell bootloader to boot the OS after reset.

set 14 1
is to tell the bootloader to stay at Serial/USB screen after reset.

task 0
is to reboot

so you would do:
set 14 0
task 0
if you are stuck at Serial/USB screen.

that works on Universal only (afaik).

for the Morph's device..
it looks like you really have unreadable block at the beginning of DOC. task 28 should have reformat it (i tested it on mine device first). if it is saying 'failed', it can't be done for some reason...
i'd really send it to service center...

buzz

[angeln20]

if i stuck to the logo screen what can i do?
the set 14 0 and task 0 doesn't help my universal to continue working.....

[buzz_lightyear]

if i stuck to the logo screen what can i do?
the set 14 0 and task 0 doesn't help my universal to continue working.....
no, it will not help you.
i'd hook it up witk PlatformBuilder and look at the KITL output...
you should see what's going wrong..

buzz

[angeln20]

what is PlatformBuilder???

[AntiProxy]

http://forum.xda-developers.com/viewtopic.php?p=252135

[buzz_lightyear]

what is PlatformBuilder???
PB is a set of tools + IDE to build WCE/WM ROMs...

here's an example KITL output of booting the Universal:
http://forum.xda-developers.com/viewtopic.php?p=251705

buzz

[KT]

PB is a set of tools + IDE to build WCE/WM ROMs...

Hi Buzz...

Please tell us where can we find the Platform Builder(the tools + IDE) for download. Can you please provide the url.. I searched on M$ site but found only updates to Platform Builder for CE 5.0

I couldnt find the PB itself. Only updates (quarterly, monthly, yearly)

Please help...

Regards,
mOrph

[buzz_lightyear]

here:
http://www.microsoft.com/windows/embedded/eval/default.mspx

[KT]

here:
http://www.microsoft.com/windows/embedded/eval/default.mspx

Hi Buzz... The link above just keeps going round and round between the download page & a form that we have to fill out... The download actually never starts.. I tried it about 20-25 times... All the fields that were compulsory in the form were filled appropriately and i was logged in to my passport account. Still nothing happened... Is it possible to upload the trial version on FTP ( thats if it is legal?)

Regards,
mOrph

[KT]

Hi Buzz...

i am giving link to a url which i found out... It has multiple download files ( for ARM,MIPS...etc...) Is this the platform builder aswell??

For arm processors, the file is about 120 Mb... Please comfirm if this is of any use atall


http://www.microsoft.com/downloads/details.aspx?familyid=6C69461E-89FA-40B0-8953-B4CC1ADBC8D8&displaylang=en#filelist


Regards,
mOrph

[buzz_lightyear]

Windows Embedded 120-day Trial
Register to get a 120-day trial version of Windows Embedded.

Don't have a Microsoft® Passport?


Use one e-mail address and password to sign in to any site on the Microsoft Passport Network.

Do you have a Hotmail or MSN e-mail address? It's already a Microsoft Passport. Use it to sign in!

you have to register here:
https://login.passport.net/ppsecure/uisecure.srf?lc=1033&id=42814

that's the next page, after you click the download button.

buzz

[magpie2000k]

I can confirm it works.

The mtty method descibed by buzz.

One noticable thing, My battery was very low when I tried first time ie 10%. I tried another three times having done the mtty method.

I then plugged my Exec into a mains adapter supplied with a Motorola razor.

when I reflashed again, AND THIS TIME IT WORKED, stangely enough the batter level when started up was 51%.

i CAN ONLY CONCLUDE THAT UNLESS THE BATTERY LEVEL IS ADEQUATE THIS DONT WORK.


STAY HAPPY
(I AM NOW!!!)

[hdubli]

I tried to see the RUU.txt after upgrade in case of Morphosin's JASJAR.
END UpdateRadio !

08:54:58:156 [msg] : START BackCEMode !

08:54:58:156 [err] : BL Set BackCE Flag Error.

08:54:58:156 [msg] : START UnInitialization !

08:54:58:156 [msg] : END UnInitialization !


Buzz can throw more light on the 2nd line
Also in case of Exec, before the Start and End Uninitialisation, there is "StartFormatExtend" and StopFormatExtend"

This is not there in any of the ROMs Flashed to JASJAR.
Buzz can throw some light on this too

[buzz_lightyear]

hmm...
lets hope, that morph didn't try to run DOC_Tool on it...

hook it up on KITL and post the log

buzz

[cr2]

task 28 should have reformat it (i tested it on mine device first).


And how are you going to boot when the bootloader
is reformatted ? :?

[KT]

hmm...
lets hope, that morph didn't try to run DOC_Tool on it...

hook it up on KITL and post the log

buzz

Hey Buzz... Just wanted to ask what is the DOC Tool? Am not too sure & wanted to know prior to doing something stupid.. "hdubli" is way tooo busy and has given more than his share of time to my device. Out of shear shame i have brought it back to my place for a few days to see if something happens.. Am very sure i'll be taking it back to him && wanted to make sure its not worse than how he handed it over...

btw... all u guys...i'd like to mention here that am way too overwhelmed with the kind of support that "HDUBLI","BUZZ","SIMON" and all you guys have shown... Immaterial of whether my device ever breathes again, am really happy to see the spirits of this palce... May God bless all the UNIVERSALS that are stuck in SPLASHSCREEN

Regards,
mOrph

[KT]

task 28 should have reformat it (i tested it on mine device first).


And how are you going to boot when the bootloader
is reformatted ? :?

WHOA!!!

Who said anything about bootloader being reformatted... Is that what task 28 does???

Respected Mr. CR2,

I am a novice so cant really challenge your word but i have being told that task 28 formats the DOC.. Hence by 1 & 2 you wanna say that the bootloader is also on the DOC???

Also, we all would really appreciate if you could explain your one-liners :D ...

Am very sure that alot many people over here are interested in knowing anything that they dont know about the JASJAR... Guys, am i right...

Anyways... All that i am trying to say is that please dont scare us with those kind of one-liners... We would appreciate if you could back it up with reasoning or explanation as most of us are dummies (Except BUZZ,HDUBLI,MWANG,ASUKAL,SIMON... etc...)

thanking in advance & hoping for a more detailed post from you...

Kind Regards,
mOrph

[qtotter]

hi guys,

i would like to know what _caused_ this problem as well as how we can fix it. fortunately, i succeeded updating my uni with one of the new roms this time, but i would hasitate to do it again until we find the cause...

was there a wrong step in the way those who got their unis frozen at the splash screen updated their unis? (morphosin is the only one who explained what he did step by step...)

low battery level, anti-virus software intervention, interferring pc while updating rom, etc?

is this a new problem or this risk has been always there from the beginning?

sorry for putting only questions here while many are looking for some solutions to the problem.

[angeln20]

which rom did u install??at the end of the installation which buttons u press for reset?? the two -,on/off and reset with stylus??

[hdubli]

hmm...
lets hope, that morph didn't try to run DOC_Tool on it...

hook it up on KITL and post the log

buzz

I choose Enable KITL and active conection on USB,,,I get found new harware...your hardware is installed properly....In Active Sync, I disable USB and select DMA port..

Now how do I move ahaead..I do not have debugger...pls advice

[KT]

hi guys,

i would like to know what _caused_ this problem as well as how we can fix it. fortunately, i succeeded updating my uni with one of the new roms this time, but i would hasitate to do it again until we find the cause...

was there a wrong step in the way those who got their unis frozen at the splash screen updated their unis? (morphosin is the only one who explained what he did step by step...)

low battery level, anti-virus software intervention, interferring pc while updating rom, etc?

is this a new problem or this risk has been always there from the beginning?

sorry for putting only questions here while many are looking for some solutions to the problem.

Hi Qtotter...

I can confirm that the antivirus software intervention is certainly not the reason as i have tried the same procedure over and over on a machine (PC) which doesnt have any antivirus installed on it...

Battery level might not have been above 50 % the first time i performed the upgrade but certainly following that, i have tried installing on a fully charged battery.. It didn't help me atleast...

Regarding the interferring with PC during ROM Upgrade can be ruled out... The only interferring that i was doing was constantly staring at the screen...

I hope these observations help...

Thanks...

Regards,
mOrph

[buzz_lightyear]

hmm...
lets hope, that morph didn't try to run DOC_Tool on it...

hook it up on KITL and post the log

buzz

I choose Enable KITL and active conection on USB,,,I get found new harware...your hardware is installed properly....In Active Sync, I disable USB and select DMA port..

Now how do I move ahaead..I do not have debugger...pls advice
Platform Builder is your debugger.
You have to build at least one platform and then make a connection to it..

[Asukal]

@hdubli
thanks but many of my friends are helped by your post,too.

Also one of my friend, receovered by useing command with PlatformBuilder from PC, he reported me like that.

Hi Asukal...

Can you please elaborate the "platform builder recovery method"... I think thats the only thing left to do now...

Thanks...

just back from work, and i am waiting the instruction from friend,

upon i reciept from him, i try and report here.

PLS wait.

any info my friend????

he didnt replay me yet! he seems to be on holidays and out
he will replay tonight...........i hope...........

i tried many way with Platrorm builder, but couldnt.
i am very want to know how he did,too :cry:
(but it will be possiblity same as Mtty.exe, some guy effect, some guys not)

[Wail]

What we really need is for someone, or some many, who have performed the upgrade SUCCESSFULLY!

Giving us step-by-step of what they did, what configurations they have on their PCs and so forth.

I have not yet done the upgrade, as I am very reluctant to do so; but I would suggest the following: -

On the PC

1. Make sure that the screen saver is turned off.
2. Make sure that there is no power-saver features turned on.
3. Make sure that Activesync is installed in the root (default) directory.

On the PPC

1. Make sure that the unit is 100% charged.
2. Make sure that there is none of the auto-off are ticked.
3. Make sure that you do, at least, a soft reset – preferably do a hard reset.
4. Connect the PC and PPC and let it take its’ course.

Of course, make sure that you synchronise all your data before doing anything.

Now, I give these hits in lieu of my experience with ROM updates for various iPaqs. I had always been reluctant about ROM updates but have always followed the above rules and seemed to have fared well with each of the updates that I ran.

Again, I would love to hear from anyone who has SUCCESSFULLY done the update and the details of the steps they followed.

[olliesshop]

Mid-way through my diagnosis I realized my USB cable was not working correctly and would not allow it to connect with bootloader. Although, it did allow the ROM update to work the first time. I'm wondering if this could be a common thread with the devices that are stuck on the splash screen, since I used the USB cable that came with the Jasjar to do the original ROM upgrade. Could it have only sent part of the upgrade to the device and somehow screwed up the upgrade? If some of the USB cables were bad from the factory that might explain why it only affected some of the Universals. Just a thought to ponder.

[Rik Lijkendijk]

My sad history and my salvation.

Two weeks ago i received my Qtek 9000 and was very happy. But not happy enough since there were newer ROMS out there.

So after a week i downloaded and successfully installed the JASJAR ROM 1.30.68 (marked test),(using the NoID install tool)

Last week the final version of the ROM was released (1.30.76) and I really really really wanted that one.

I used the same method for the update and sh.....tttt I became stuck in bootloadermode.

After trying a million restarts I decided to try and get my original ROM back, but my device was not recognized on the USB bus.

The way i got my USB connection recognized was as follows.

Connect the device to your PC and wait for the message that the USB device is unknown. Then still connected push both softbuttons and perform a reset.

On the white screen asking for 0 or x press 0. The device returns to bootloadermode, but the USB connection to your PC will be OK. (At least is was for me)

I was then able to successfully reflash my original ROM and got my device working again.

I again finished the setup and after that was able to reflash with the latest JASJAR ROM, using the NoID tool.

I am now the proud owner of a Qtek 9000 with a i-mate ROM version 1.30.76.

This is my story. There is no way to tell if it will work for someone else, But if your device is stuck every option is worth lookin at.

:idea: :idea:

[qtotter]

which rom did u install??at the end of the installation which buttons u press for reset?? the two -,on/off and reset with stylus??

if this is a question addressed to me;

i used "JASJAR WWE 1.30.76 164 1.09.00 WWE ship ROM" and modifed the rom with some fonts and files so that i can read/write japanese.

after burning the modifed rom into my uni, i took off the usb cable and rebooted the machine by [power]+[reset]. not [-]+[-]+[reset].

i guess the last one is the only difference in updating between me and morph.

[qtotter]

Hi Qtotter...

I can confirm that the antivirus software intervention is certainly not the reason as i have tried the same procedure over and over on a machine (PC) which doesnt have any antivirus installed on it...


hi morph,

if i may ask, what is the cpu of your win machine? how about ram? my pc has p4-3ghz with 1gb ram.

[qtotter]

On the PC

1. Make sure that the screen saver is turned off.
2. Make sure that there is no power-saver features turned on.
3. Make sure that Activesync is installed in the root (default) directory.

On the PPC

1. Make sure that the unit is 100% charged.
2. Make sure that there is none of the auto-off are ticked.
3. Make sure that you do, at least, a soft reset – preferably do a hard reset.
4. Connect the PC and PPC and let it take its’ course.
.

pc
1 i don't use screen saver on my home pcs.
2 my power saver setting is just "turn off monitor" after 2 hrs.
3 i installed activesync as default.
4 i turned off all the other programs unnecessary for rom-burning as well as norton anti-virus.
5 many suggest you disable usb connection in activesync, but i did not because it seems to turn off automatically anyway when you burn a rom.
6 i did not even touch the mouse while burning the rom.

ppc
1 i did not check how the battery level of my uni was before i updated the rom. i just took out sim & sd.
2 i do not use the auto-off function, therefore it was unchecked in the power setting.
3 i rebooted the machine by [power]+[reset], not [-]+[-]+[reset], right after rom-burning completed.
4 i did not understand your 4th item...

[buzz_lightyear]

3 i rebooted the machine by [power]+[reset], not [-]+[-]+[reset], right after rom-burning completed.
you didnt hardreset after update.

you must hardreset after OS update.
so either press - - and reset and then confirm with 0 (zero) or press reset and hold down Light Button until Boot Options menu appears.
THere you have to select:
Enable KITL -> NO
Format Storage -> YES
Clean Reg Hive -> YES

You use the Dpad UP DOWN, to move across the menu and change the values. Use center button of Dpad to confirm (enter).

buzz

[qtotter]

3 i rebooted the machine by [power]+[reset], not [-]+[-]+[reset], right after rom-burning completed.
you didnt hardreset after update.

you must hardreset after OS update.
hi buzz,

no, i did not hardrest "right after" rom-burning although everything including the ocntents of extended rom and the splash screen were updated normally.

i, of course, had to hardrest a couple of times afterwards since i wanted to test and check a few things with the new rom.

why do we have to perform hard reset even though softrest works?

qt

[KT]

What we really need is for someone, or some many, who have performed the upgrade SUCCESSFULLY!

Giving us step-by-step of what they did, what configurations they have on their PCs and so forth.

I have not yet done the upgrade, as I am very reluctant to do so; but I would suggest the following: -

On the PC

1. Make sure that the screen saver is turned off.
2. Make sure that there is no power-saver features turned on.
3. Make sure that Activesync is installed in the root (default) directory.

On the PPC

1. Make sure that the unit is 100% charged.
2. Make sure that there is none of the auto-off are ticked.
3. Make sure that you do, at least, a soft reset – preferably do a hard reset.
4. Connect the PC and PPC and let it take its’ course.

Of course, make sure that you synchronise all your data before doing anything.

Now, I give these hits in lieu of my experience with ROM updates for various iPaqs. I had always been reluctant about ROM updates but have always followed the above rules and seemed to have fared well with each of the updates that I ran.

Again, I would love to hear from anyone who has SUCCESSFULLY done the update and the details of the steps they followed.

Hi dude...

All the precautionary measures are valid but kind of insignificant as we have already incorporated them in our ROM flashings...

TAKE MY ADVICE... UNTIL THE PROBLEM DOESNT GET SOLVED DO NOT PERFORM THE UPGRADE...

Regards,

mOrph

[KT]

Mid-way through my diagnosis I realized my USB cable was not working correctly and would not allow it to connect with bootloader. Although, it did allow the ROM update to work the first time. I'm wondering if this could be a common thread with the devices that are stuck on the splash screen, since I used the USB cable that came with the Jasjar to do the original ROM upgrade. Could it have only sent part of the upgrade to the device and somehow screwed up the upgrade? If some of the USB cables were bad from the factory that might explain why it only affected some of the Universals. Just a thought to ponder.


Hi olliesshop...

I cant be certain as what urr saying is a possibility as i tried more than one data cables. Though its not like anybody had got success using any of these cables, but i thought to myself that what are the odds that two cables can be bad...

Thought i'd let you know...

Regards,

mOrph

[KT]

hi morph,

if i may ask, what is the cpu of your win machine? how about ram? my pc has p4-3ghz with 1gb ram.

Hi qtotter...

The following are the details of my PC:

CPU : Intel(R) Pentium(R) M Processor 2.13 GHz
RAM : 797Mhz, 1.00 Gb of RAM

If you need any other details, please do let me know...

Regards,
mOrph

[meer]

I have the same Problem on my new MDA Pro.
- first I flashed the Imate Rom but after the HR nothing happens
- then I flashed it from the Bootloader Modus agian and now it stucks in th Splash screen after HR.

[qtotter]

Hi qtotter...

The following are the details of my PC:

CPU : Intel(R) Pentium(R) M Processor 2.13 GHz
RAM : 797Mhz, 1.00 Gb of RAM

If you need any other details, please do let me know...

Regards,
mOrph

hi morph,

well, i think your machine is powerful enough since i could burn a rom using a notebook pc with less cpu power than yours...

i wonder what the cause is.... (burning radio rom now since i did not notice it was 1.08.00)

[qtotter]

i just updated the radio rom to 1.09.00 using maupgradeut_noid.exe (thanks!!) and performed "softrest."

the splash screen says it is 1.09.00 and the device info in settings also says it 1.09.00...

is it not really updated to 1.09.00? i still wonder why we need to perform hardrest after rom-burning...

qt

[bigjimd366]

I am beyond lost.

I started upgrade thru activesync as the instuctions stated. During the upgrade JASJAR/Universal turned off for no apparent reason. Naturally the upgrade setup failed.

Now the unit will not turn back on. after preforming a "hard reset" all i can see is a screen with no backlight. At the top it says "Serial" and the bottom "v1.00"

Somone please tell me what to be with some detail I am to fustrated to figure things out on my own. Thankyou

[buzz_lightyear]

I am beyond lost.

I started upgrade thru activesync as the instuctions stated. During the upgrade JASJAR/Universal turned off for no apparent reason. Naturally the upgrade setup failed.

Now the unit will not turn back on. after preforming a "hard reset" all i can see is a screen with no backlight. At the top it says "Serial" and the bottom "v1.00"

Somone please tell me what to be with some detail I am to fustrated to figure things out on my own. Thankyou
i'll build a tool, which will jump you out of the bootloader, tomorrow...

buzz

[meer]

I tried to dump the Rom out of the Bootloader Modus without any success.

Nothing is written to the SD Card.

Maybe it helps somebody. :cry:

[qtotter]

I am beyond lost.

I started upgrade thru activesync as the instuctions stated. During the upgrade JASJAR/Universal turned off for no apparent reason. Naturally the upgrade setup failed.

Now the unit will not turn back on. after preforming a "hard reset" all i can see is a screen with no backlight. At the top it says "Serial" and the bottom "v1.00"

Somone please tell me what to be with some detail I am to fustrated to figure things out on my own. Thankyou
hi big,

i think buzz has already written how to fix this without reflashing the radio rom somewhere here, but the quickest way to fix your problem is to reflash ONLY the radio rom. your case is curable. you will find how to do it in many threads if you search in the forum, which i did when i had the exact same problem. hope you will find a way out.

qt

[bigjimd366]

hi big,

i think buzz has already written how to fix this without reflashing the radio rom somewhere here, but the quickest way to fix your problem is to reflash ONLY the radio rom. your case is curable. you will find how to do it in many threads if you search in the forum, which i did when i had the exact same problem. hope you will find a way out.

qt

I read these same forums about upgradeing with the radio only rom. First, I am not sure where to get this rom. Second, I do not see how I can preform a upgrade again when my PC cannot recognize a device that does not turn on.

[hdubli]

Dear Buzz,
Looking at all these posts, it is clear that there is something hidden which we common people do not know.Since you hv been testing Beta ROMs and making them also, can u figure out as why these are happening in case of Universal.

One of my Logical guess is that each variant of ROM must be having a differrent Checksum..so upgrading(burning the ROM) might not be proper or with a bit of damage to boot sector of ROM, which is causing this.

Ones who hv got past in those cases there might hv been a proper formatting of FLash so buring of the Flash was perfect.

You can throw more light on this

[buzz_lightyear]

I do not see how I can preform a upgrade again when my PC cannot recognize a device that does not turn on.

hi,
just run the upgrade again. it will find the device. you don't need ActiveSync connection to flash.

buzz

[buzz_lightyear]

Dear Buzz,
Looking at all these posts, it is clear that there is something hidden which we common people do not know.Since you hv been testing Beta ROMs and making them also, can u figure out as why these are happening in case of Universal.

One of my Logical guess is that each variant of ROM must be having a differrent Checksum..so upgrading(burning the ROM) might not be proper or with a bit of damage to boot sector of ROM, which is causing this.

Ones who hv got past in those cases there might hv been a proper formatting of FLash so buring of the Flash was perfect.

You can throw more light on this
hi hdubli,
all what I know is, that if you are stuck at bootloader, it is easy to recover.
but if it passes bootloader and then stuck at splash screen... hmm..
it might be, that you have bad/unreadable blocks on DOC.
if it is possible, for such device, to use d2s command, then would be interesting to get ROM dump, to see, if it is complete or not. most of the universals have d2s disabled (lower level CID), so they cannot be d2s dumped.

did you already logged booting with KITL?

buzz

[bigjimd366]

I got mine fixed just now. I had been working at it for many hours. I gave up sent an email to I-Mate and left for the night. After a long night of drinking and playing air-hockey with my hands(no paddles) I came home and got it fixed up

Did hard reset to get to the bootloader screen that is very dificult to see. At the screen I plugged in the USB cable and for the first time ever the word "Serial" at the top changed to "USB". At this point I felt confident I was good to go. While waiting for the update to complete I got an email reply from I-Mate provideing me with intrustions that verified I was doing the right thing.

The following are the steps provided to me by I-Mate support:

1. Make sure your i-mate(tm) PPC is not Connected to the PC and remove the dummy card or SD/MMC card

2. On your Desktop PC, open Microsoft ActiveSync, then go to File >Connection Settings >Remove the Selection from "Allow USB Connection with this desktop computer"

3. Make sure your Device is on Boot loader Screen*

4. Reconnect your i-mate PPC to the Desktop PC using the USB cable or creadle (Don't use the IrDA or Bluetooth for the Upgrade)

5. Run the Upgrade again.



*Boot loader mode - For the boot loader mode to appear, you need to press and hold at the backlight + Power buttons then perform soft reset.

One thing I would like to add to this is, after upgrade is said to be complete successfully, preform a soft reset useing the reset button on the back.

I am fully operational. Thanks to all that replied to me. I was being a NOOB, sorry.

[qtotter]

congrats, big.

fyi,

the rom .exe file you used is actually an executable archived file which contains three roms and updating software. if you open the .exe file using compatible uncompressing software, you will get the radio rom out of it.

also, you can download maupgradeut_noid.exe from buzz's site with which you can burn whichever rom you like as long as it is meant to be created for universal.

qt

[meer]

The following are the steps provided to me by I-Mate support:

1. Make sure your i-mate(tm) PPC is not Connected to the PC and remove the dummy card or SD/MMC card

2. On your Desktop PC, open Microsoft ActiveSync, then go to File >Connection Settings >Remove the Selection from "Allow USB Connection with this desktop computer"

3. Make sure your Device is on Boot loader Screen*

4. Reconnect your i-mate PPC to the Desktop PC using the USB cable or creadle (Don't use the IrDA or Bluetooth for the Upgrade)

5. Run the Upgrade again.



*Boot loader mode - For the boot loader mode to appear, you need to press and hold at the backlight + Power buttons then perform soft reset.

One thing I would like to add to this is, after upgrade is said to be complete successfully, preform a soft reset useing the reset button on the back.

I am fully operational. Thanks to all that replied to me. I was being a NOOB, sorry.

This solves only the Problem if stuck in Bootloader Modus, not the Splash screen Problem.

[KT]

I hate to admit that for all these years I kept on bumming around with our devices (Hima, BA, etc...). We kept flashing them almost every week, trying stunts of all sorts and nothing went wrong beyond repair.

&& now that I followed the protocols & upgraded my JASJAR with an authentic ROM provided by them, the device is gone dead.

What a pity... I wish someone could make Imate realise what they've done to their customers && consequently what the repurcussions will be for their Marketing...

I Morphosin hereby take an oath that leave apart buying an iMate device ever again, i will go out of my way to make sure nobody i know buys an iMate aswell..


A very heartbroken,
mOrph

[Wail]

Buzz,

Why would you need to do a hard reset after doing any of the ROM updates?

I have updated with WWE European version, ran smoothly and I just did a reset. It functioned well. Then did an update with WWE Middle East version, ran smoothly and I just did a reset. It, too, functioned well. Then I did an update with the Arabic ROM, ran smoothly until I did the hard reset and everything got messed up. After hours of tweaking I figured that my device would not boot up with the SIM installed, so I removed SIM and SD and re-ran the ROM update but this time I did NOT do a hard reset – just a soft reset – and it is working fine so far.

So, would you please let me know why do I need to do a hard reset after the ROM update? And, do you have any idea as to what may have been going wrong with my initial Arabic ROM update?

Thanks, in advance, for your feedback.

[Jorgee]

Buzz,

Why would you need to do a hard reset after doing any of the ROM updates?

I have updated with WWE European version, ran smoothly and I just did a reset. It functioned well. Then did an update with WWE Middle East version, ran smoothly and I just did a reset. It, too, functioned well. Then I did an update with the Arabic ROM, ran smoothly until I did the hard reset and everything got messed up. After hours of tweaking I figured that my device would not boot up with the SIM installed, so I removed SIM and SD and re-ran the ROM update but this time I did NOT do a hard reset – just a soft reset – and it is working fine so far.

So, would you please let me know why do I need to do a hard reset after the ROM update? And, do you have any idea as to what may have been going wrong with my initial Arabic ROM update?

Thanks, in advance, for your feedback.

Sorry im not buzz but just to clarify something. Doing a hard reset will install the extended ROM so if you dont want to change extended ROM, then soft resetting will not re-install extended rom.

Im not sure if O2 extended rom will work on Imate OS... hmm, because im sure that the OS upgrade changes the registry and this might affect pre-installed applications.

Just to put some substance to my claim (from my experience) i backed-up using SPB Backup's full backup, Flashed to a newer (same brand) ROM and restored the backup. Didn't work. The device kept on rebooting.

I may be wrong but this made me conclude that just changing the ROM and leaving everything else as it was (ie not hard resetting and installing everything) doesn't work. But maybe it's because i use a qtek. Don't know.

If this didn't help, please ignore my message.

[buzz_lightyear]

All right,
as promised, here's a little PC tool, which will jump you out of the bootloader.

To be clear:
It works only for "stuck at serial/usb" screen.
It will NOT work, if you are stuck at splash screen.
You ALWAYS HAVE TO TRY REFLASH prior running this tool, it will help most of the times. If flashing didnt help, run the tool.
It works on UNIVERSAL device type (maybe some others as well).

The tool does opposite of what EnterBL.exe does.
Once you ran EnterBL.exe on your Universal, it will prevent the system to boot into OS.

In such case, or after unsuccessful update, you can recover using this UNI_ExitBootloader.exe tool.

How to:
- disconnect USB cable from your device
- disable USB connection in ActiveSync
- reconnect USB cable
- wait some 30 seconds
- run the tool

If successful, device will boot itself.

:o)
buzz

[angeln20]

i hope to make a little program for us that we stuck in the splash screen....... :D

[buzz_lightyear]

i hope to make a little program for us that we stuck in the splash screen....... :D
once i'll know, why it is not booting further...

Anyone ready with the KITL log?

buzz

[qtotter]

Doing a hard reset will install the extended ROM so if you dont want to change extended ROM, then soft resetting will not re-install extended rom.
hi jorgee,

i don't think that is exactly true. your comment applies to the second reset or later, but not to the first rest right after rom-burning. in fact, i just burnt a rom with a jpn/chn font and some modification to reg, and performed soft-rest. however, the setup process tried to run apps in extended rom.

i still do not understand why people say you need to perform hard-rest right after rom-burning although soft-rest works as well. none of those who suggest hard-rest have answered this question...

i have another question to those who have their universals frozen at the splash screen. has anyone of you performed soft-rest ([power]+[reset]) right after rom-burning to end up with this problem??

cheers,

qt

[qtotter]

I Morphosin hereby take an oath that leave apart buying an iMate device ever again, i will go out of my way to make sure nobody i know buys an iMate aswell..
A very heartbroken,
mOrph
first of all, i sympathize your broken heart from all of this stress and am not trying to be bitchy, but...

i have reinstalled windows 3.1/95/98/2000/xp much more than i burnt ppc roms or hardrest my ppcs... also, i have made a couple of my old pcs just pieces of junk of metal on my own risk.

i suppose i-mate simply makes apps in extended rom, and the other roms are packaged by htc and ms... plus, i-mate did not force you to update the rom, and i am sure they offer their customers to drop by at their shops or customer servies centers to update their products in a safer way under warrenty if customers want...

(i have nothing to do with i-mate.)

[Wail]

Can someone please confirm for sure why we need to do a hard reset after installing the new ROM. From the looks of it, my JazJar seems to be working 100% fine after a ROM update without doing a hard reset at the end of the process.

[Wail]

Jorgee,

Sorry, I didn’t see your reply to my post / question. Thank you for the reply.


Buzz,

Thank you, too, for your clear instructions.


Just so that others know what I finally did, here is a brief of what I went through …


I removed my SIM and SD and proceeded with the hard reset as you had suggested, using the reset + Light Button .. I chose the options you’ve told of (NO, YES, YES) and what I got was the same process as I did with the soft-reset after the complete installation.

Still, I thought I would follow your instructions since you do seem to know “a lot” about this issue.

In the end, my system went into the reset operation and seemed to working fine, I re-installed my SD & SIM switched on my PDA and everything was fine, then did a soft-reset (which is where I used to have problems with the system turning in to a brick) but to my surprise the PDA came back alive and worked fine. I then proceeded to delete my old partnership from M$ Activesync, did a new partnership and watched it all run fine, then just to put my mind to rest, I did another soft-reset and it was all fine and dandy ….

So, my thoughts are that there is an issue with doing the hard-reset with the (-) + (-) + (reset) .. since doing it with the (Light Button) + (reset) didn’t make my machine die.

To all those who made suggestions patiently, and for all the positive feedbacks, thank you.

[KT]

Doing a hard reset will install the extended ROM so if you dont want to change extended ROM, then soft resetting will not re-install extended rom.
hi jorgee,

i don't think that is exactly true. your comment applies to the second reset or later, but not to the first rest right after rom-burning. in fact, i just burnt a rom with a jpn/chn font and some modification to reg, and performed soft-rest. however, the setup process tried to run apps in extended rom.

i still do not understand why people say you need to perform hard-rest right after rom-burning although soft-rest works as well. none of those who suggest hard-rest have answered this question...

i have another question to those who have their universals frozen at the splash screen. has anyone of you performed soft-rest ([power]+[reset]) right after rom-burning to end up with this problem??

cheers,

qt

Hi dude...

Yes, immediately after ROM flashing, i have tried all kinds of resets..

1) [-] [-] + Reset

2) Power + Reset

3) Only Reset

They all result in the same scenario... A perpetual Splashscreen...


Also, i respectfully disagree... iMate might just only make the extended ROM.. Infact, for all i care, they might not even make that... But the fact remains that "iMate" is what is written on my device & not HTC... So, if somebody is supposed to give me a service its none other than iMate... & honestly speaking, replying to multiple mails that i sent to "support@imate.com" after 5-6 days giving vauge information does not qualify for support OR service.


Well... anyways... Lets hope things change as far as our devices are concerned...


Regards,
mOrph

[Asukal]

my friend send me a instruction of recovering with Platfrom Builder(too late?).
But his problem was Bootloader, not Stucked in Splash.

so i am afraid this work or not for the problem Stuck on Splash/
My challenge this way is still in progress....

He Initialiaze Bootloader with "Board Support Package(BSP)" for XScale(pxa27x)
*ref;
http://msdn.microsoft.com/library/en-us/dnce50/html/ce50prev.asp?frame=true&_r=1

Download the MSIIIOBCE.msi

http://www.microsoft.com/downloads/details.aspx?FamilyID=BDF43D00-55B6-4E51-82A5-F0A8395D4903&displaylang=en

----------------------------------------------------------------
The package containing Windows CE 5.0 Mainstone BSP Update will be placed in the following two directories during installation:

%winceroot%/public/csp_pxa27x
%winceroot%/platform/mainstoneiii

thus means
Create 2 folder Mainstone III and csp_pca27x as following location.

C:\WINCE500\PLATFORM\Mainstone III

C:\WINCE500\PUBLIC\csp_pxa27x

ref
http://download.microsoft.com/download/b/9/5/b950c64a-00eb-4897-b037-90828a8112c2/Release%20Notes%20Windows%20CE%205.0.htm
---------------------------------------------------------------

Do someboday have any other idea from those links?

[KT]

my friend send me a instruction of recovering with Platfrom Builder(too late?).
But his problem was Bootloader, not Stucked in Splash.

so i am afraid this work or not for the problem Stuck on Splash/
My challenge this way is still in progress....

He Initialiaze Bootloader with "Board Support Package(BSP)" for XScale(pxa27x)
*ref;
http://msdn.microsoft.com/library/en-us/dnce50/html/ce50prev.asp?frame=true&_r=1

Download the MSIIIOBCE.msi

http://www.microsoft.com/downloads/details.aspx?FamilyID=BDF43D00-55B6-4E51-82A5-F0A8395D4903&displaylang=en

----------------------------------------------------------------
The package containing Windows CE 5.0 Mainstone BSP Update will be placed in the following two directories during installation:

%winceroot%/public/csp_pxa27x
%winceroot%/platform/mainstoneiii

thus means
Create 2 folder Mainstone III and csp_pca27x as following location.

C:\WINCE500\PLATFORM\Mainstone III

C:\WINCE500\PUBLIC\csp_pxa27x

ref
http://download.microsoft.com/download/b/9/5/b950c64a-00eb-4897-b037-90828a8112c2/Release%20Notes%20Windows%20CE%205.0.htm
---------------------------------------------------------------

Do someboday have any other idea from those links?

Hi Asukal...

I downloaded the MSIIIOBCE.msi but it would not install on my machine. It was giving me an error that i have pasted below. Please tell me how to overcome this problem.

Regards,
mOrph

[Asukal]

Frankly,,,, i am also stopping there at installation now! :roll: :oops:

Now i am finding solution,,, PLS wait,
But i can not say this will be solve our problem on Universal,
i wish just try it even have 0.1% possiblity. :cry:

preffere challenge than just wait, pls watch me witout expect :wink:

[qtotter]

Hi dude...

Yes, immediately after ROM flashing, i have tried all kinds of resets..

1) [-] [-] + Reset

2) Power + Reset

3) Only Reset

They all result in the same scenario... A perpetual Splashscreen...

hi morph,

i think you misundersood me. i am not saying reflashing rom and performing soft-rest might fix your problem. i simply would like to find what causes the problem.

i think you have tried all different kinds of resets "after" you got your universal frozen at the splash screen. (you said, you reflashed rom, performed hardreset and got your universal dead, didn't you?) i think no matter which reset you do the result would be the same at that stage.

i know your interest is how to fix your devide, and i am sorry about your situation. but i am sure many poeple are also interested in how to avoid such a tragedy. so far, i cannot find any difference between my success and your case other than the ways we performed reset just after rom-burning.

cheers,

qt

p.s.
i just realized the ratio of the number of the posts in this thread to the number of the times this thread has been viewed is not as high as the other threads. i wonder if the possibilty of this problem is not as high as i was worried...

[KT]

Hi dude...

Yes, immediately after ROM flashing, i have tried all kinds of resets..

1) [-] [-] + Reset

2) Power + Reset

3) Only Reset

They all result in the same scenario... A perpetual Splashscreen...

hi morph,

i think you misundersood me. i am not saying reflashing rom and performing soft-rest might fix your problem. i simply would like to find what causes the problem.

i think you have tried all different kinds of resets "after" you got your universal frozen at the splash screen. (you said, you reflashed rom, performed hardreset and got your universal dead, didn't you?) i think no matter which reset you do the result would be the same at that stage.

i know your interest is how to fix your devide, and i am sorry about your situation. but i am sure many poeple are also interested in how to avoid such a tragedy. so far, i cannot find any difference between my success and your case other than the ways we performed reset just after rom-burning.

cheers,

qt

p.s.
i just realized the ratio of the number of the posts in this thread to the number of the times this thread has been viewed is not as high as the other threads. i wonder if the possibilty of this problem is not as high as i was worried...

Hi dude...

No no i didnt misunderstand you... i mean no hard feelings atall bro... i wasnt being witty or sarcastic... i did get what u were saying bout the origin of the problem. I just generally happened to mention for the records that all types of resets have been tested by us...

Sorry if there has been any miscommunication... Do accept my apologies...

LOOKING FORWARD TO SOME SOLUTION TO THIS PROBLEM... LETS HOPE FOR THE BEST....

chao...

Regards,
mOrph

[KT]

Hi all...

Am sure that this has been discussed before by hdubli, but now that i myself had the log files of two different RUU, i thought i'd post the difference here.. Maybe Buzz or one of our other geniuses could figure out something... Well, as we all know that RUU Log file that is created has hundreds of lines. Amongst these lines only the end differs when i used a complete i-Mate ROM Package in the first case && Radio ROM ver 1.08 along with i-Mate CE ROM & Ext ROM in the second case.

Case 1 :- Pure i-Mate ROM Extracted & installed

02:00:02:593 [msg] : END UpdateCE !

02:00:04:593 [msg] : START FormatExtended !

02:00:05:546 [msg] : END FormatExtended !

02:00:05:546 [msg] : START BackCEMode !

02:00:06:328 [msg] : END BackCEMode !

02:00:06:328 [msg] : START UnInitialization !

02:00:06:328 [msg] : END UnInitialization !



Case 2 :- Radio 1.08 + i-Mate CE ROM & Ext ROM



00:12:39:000 [msg] : END UpdateCE !

00:12:43:031 [msg] : START UnInitialization !

00:12:43:046 [msg] : END UnInitialization !



Hope this helps us...


Regards,

mOrph

[buzz_lightyear]

hi morph,
are you able to successfully flash ExtendedROM only?

please try and post the log...

thanx
buzz

[KT]

hi morph,
are you able to successfully flash ExtendedROM only?

please try and post the log...

thanx
buzz

Hi Buzz...

I did try flashing the Ext ROM only once before & it did happen successfully. Though the result was the same, ie, a device stuck in the SplashScreen. But i dont have the logs. I'll redo it & post the log in a while...

Chao

Regards,
mOrph

[KT]

Hi Buzz...

Here is the full log of Ext ROM Upgrade... This is the log for Only ExtROM as you had asked...


12:38:56:468 [msg] : Version : [2.11].

12:38:56:484 [msg] : Config Info : [857873],[1],[0],[0],[1],[0],[0],[1].

12:38:56:500 [msg] : RadioFile Not Exist !

12:38:57:078 [msg] : CEFile Not Exist !

12:39:00:140 [msg] : Current Not in CE Mode or in CE Mode but ActiveSync Not Connected.

12:39:04:312 [msg] : Disconnect ActiveSync .... [2]

12:39:04:312 [msg] : Start Get Connect Port.

12:39:04:453 [msg] : Current in BL Mode. Open Port : [\\.\WCEUSBSH001] OK.

12:39:09:750 [msg] : Device BL VER : [0.60 ] [].

12:39:09:750 [msg] : Update Image. CE : [0], MSystem : [2], Radio : [0]

12:39:11:968 [msg] : Check Ac in BL mode. AC : [1]
12:39:13:468 [msg] : IsBL. BL : [1]

12:39:18:515 [msg] : =============================================

12:39:18:515 [msg] : START UpdateExtended !

12:39:19:640 [msg] : Upgrade 2 : 0 Start.

12:39:30:265 [msg] : Upgrade 2 : 0 End.

12:39:30:265 [msg] : Upgrade 2 : 1 Start.

12:39:40:781 [msg] : Upgrade 2 : 1 End.

12:39:40:781 [msg] : Upgrade 3 : 2 Start.

12:39:46:203 [msg] : Upgrade 3 : 2 End.

12:39:50:578 [msg] : END UpdateExtended !

12:40:00:578 [msg] : START BackCEMode !

12:40:01:375 [msg] : END BackCEMode !

12:40:01:375 [msg] : START UnInitialization !

12:40:01:390 [msg] : END UnInitialization !



Hope this helps...

Regards,
mOrph

[olliesshop]

FYI ... my Jasjar has been at Topp Solutions in Miami since Friday. I talked to them yesterday and they're waiting to hear back from "the factory" on a fix. Evidently the technician could not get the ROM to upgrade either. So no word yet on what the fix is. It actually may end up being a hardware problem, we'll see.

[sandrobber]

this is true in my case also but they do hve six buisness days to repair or give you a refurb

[apbristow]

Buzz,

Many many thanks for your little app to break out of Bootloader cycle during ROM Upgrade. You've saved my Exec and marriage!! Strange because I've done upgrades several times before but this once it just locked up in bootloader. Worrying times but I can now reassure others who think all is lost just to take their time and follow the superb advice in the forums.

Small donation in gratitude on its way via Buzzdev.net.

Andy

[zYxMa]

I run EnterBL.exe on my universal for some reason :? and all I could see was USB/SERIAL grey screen and then I upgrade radio to 1.06.00 (I thought it would help) and now I see only QTEK screen with R/G/D versions...

Is that possible if I'll take my universal to local t-mobile warranty if I upgraded t-mobile ROM to QTEK ROM before? Will they accept it?

If yes - will they give me substitute phone? :?

That is what I see now:

http://img97.imageshack.us/img97/8107/dsc040655ox.th.jpg (http://img97.imageshack.us/my.php?image=dsc040655ox.jpg)

[Jorgee]

Enter BL again by pressing Backlight+Power+reset hole.

Then upgrade only radio....

This might work

[apbristow]

FWIW the only thing I did not do before the upgrade that led to me getting stuck in Bootloader cycle was take out the SD card. I don't know enough about these things to suggest that is the reason for it failing but when I took it out, re-flashed and used Buzz's little app posted above it started again perfectly. I don't want to try it again to do a scientific study of whether it works again but if it helps............

So....... Many thanks to Buzz and I'd advise double double checking removal of SD cards prior to updating ROM.

Sympathies to those stuck in splash screen.

[zYxMa]

Unfortunetly did't work :(
I mean EnterBL worked and I did downgrade to previous Radio (1.4.02) and agains I see only splash screen :(

[ady]

hmmmm KITL doesn't work. after turning it on, it just get stuck at the KITL screen and doesn't go any further

[zYxMa]

Enter BL again by pressing Backlight+Power+reset hole.

Then upgrade only radio....

This might work

Thank you so much :D

All done, but when I upgraded radio only didn't work, so then I upgraded to newest t-mobile ROM and now is OK.

Thanks! :)

[chris_khho]

Hi all,

Please help.....

Now my O2 Exec stuck at the splash screen with the radio and rom version....

I am using the 1.30.76 Imate ROM......

Now it stuck....the previous thing that I have done to my machine just before it stucked....was ADDING THE REGISTRY OF "HKCU\Software\Microsoft\Shell\NeverDorkMemory"(THIS IS NOT IMPORTANT)
AND adding some cab files to the extended rom... (THIS IS IMPORTANT!!!)

And a softreset

Pls help....I dont know what's happening....

I gone through the post here but couldnt find a solution....

Thanks...and help....
^-----------------------------------------
POST EDIT>>>>>
OH!!! I just got it back by pressing the "-" "-" and reset pin......

The problem is actually the new cab file that I got from DOPOD...

AudioDrvPatch.cab (This is actually for 818Pro.....)

After installing this, the device hang....I tried couple times and that's it!!!!!

Thank god.....

[buzz_lightyear]

Buzz,

Why would you need to do a hard reset after doing any of the ROM updates?
imagine, that you want to reinstall your PC, which is full of shit now (at least my PC is).
So instead of just installing over the old stuff, you'd like to format your disks to remove all leftovers from previous system and install a clean system from the scratch.

The same you do after upgrade. I know, that flashing replaces the ROM itself, but you want also to clear all other stuff saved in DOC.

So you just hardreset it.

buzz

[buzz_lightyear]

12:39:09:750 [msg] : Device BL VER : [0.60] [].


This is interesting...
You have an old bootloader in it!

Can anyone else, who's stuck at splash, post this info from RUU.log??

buzz

[ady]

i don't have ruu.log @the moment but i checked through info 6 in mtty and mine is 1.4 built on oct 2005.

also it got stuck when i did hard reset and not rom update unlike others

correction: BL version is 1.00


here is the log:


23:21:25:421 [msg] : Version : [2.11].

23:21:25:453 [msg] : Config Info : [857873],[1],[0],[0],[1],[0],[0],[1].

23:21:25:468 [msg] : RadioFile Not Exist !

23:21:25:625 [msg] : CEFile Not Exist !

23:21:28:671 [msg] : Current Not in CE Mode or in CE Mode but ActiveSync Not Connected.

23:21:32:750 [msg] : Disconnect ActiveSync .... [2]

23:21:32:750 [msg] : Start Get Connect Port.

23:21:32:890 [msg] : Current in BL Mode. Open Port : [\\.\WCEUSBSH001] OK.

23:21:33:843 [msg] : Device BL VER : [1.00 ] [].

23:21:33:843 [msg] : Update Image. CE : [0], MSystem : [2], Radio : [0]

23:21:35:906 [msg] : Check Ac in BL mode. AC : [1]
23:21:35:906 [msg] : IsBL. BL : [1]

23:21:38:000 [msg] : =============================================

23:21:38:000 [msg] : START UpdateExtended !

23:21:39:062 [msg] : Upgrade 2 : 0 Start.

23:21:49:343 [msg] : Upgrade 2 : 0 End.

23:21:49:343 [msg] : Upgrade 2 : 1 Start.

23:21:59:453 [msg] : Upgrade 2 : 1 End.

23:21:59:453 [msg] : Upgrade 3 : 2 Start.

23:22:04:656 [msg] : Upgrade 3 : 2 End.

23:22:09:109 [msg] : END UpdateExtended !

23:22:11:125 [msg] : START FormatExtended !

23:22:12:171 [msg] : END FormatExtended !

23:22:12:171 [msg] : START BackCEMode !

23:22:13:046 [msg] : END BackCEMode !

23:22:13:046 [msg] : START UnInitialization !

23:22:13:062 [msg] : END UnInitialization !

[qtotter]

Buzz,

Why would you need to do a hard reset after doing any of the ROM updates?
imagine, that you want to reinstall your PC, which is full of shit now (at least my PC is).
So instead of just installing over the old stuff, you'd like to format your disks to remove all leftovers from previous system and install a clean system from the scratch.

The same you do after upgrade. I know, that flashing replaces the ROM itself, but you want also to clear all other stuff saved in DOC.

So you just hardreset it.

buzz
hi buzz,

if it is the only reason, you can hardreset later after you burn a rom and softrest. correct?

[KT]

12:39:09:750 [msg] : Device BL VER : [0.60] [].


This is interesting...
You have an old bootloader in it!

Can anyone else, who's stuck at splash, post this info from RUU.log??

buzz

Hi Buzz...

I understand my bootloader is old version.. Do you recommend upgrading it? Is there a way to upgrade it?

Thanx

Regards,
mOrph

[Waltzing Mathilda]

I am a newbie to this thread & I clearly had the problem many of you experienced. I had the country ID error so used the maupgradeut_noID utility which flashed the ROM (I guess) but then I was stuck in bootloader.
I then read through this thread and tried the mtty utility - set 14 0 which didn’t work for me.

I then ran task 28 with the mtty utility, then upgraded the ROM using maupgradeut_noID which when complete I followed with a soft reset – and it worked.

I didn’t try Buzz’s UNI_ExitBootloader but I guess that may have fixed it too.

Many thanks to all you guys for the help you give those of us who are less savvy.

[ady]

12:39:09:750 [msg] : Device BL VER : [0.60] [].


This is interesting...
You have an old bootloader in it!

Can anyone else, who's stuck at splash, post this info from RUU.log??

buzz

Hi Buzz...

I understand my bootloader is old version.. Do you recommend upgrading it? Is there a way to upgrade it?

Thanx

Regards,
mOrph

can you check through mtty if d2s command works? I'm curious since you have an older bootloader so it may be allowed in it

[ady]

some more info:

"task 28" is always issued after updating CEROM and EXTROM by RomUpgradeUt

On the device which I have, it fails with the error:

----------
USB>task 28
flFormatPhysicalDrive:status=23
DOC_format failed!
----------

I realized it while sniffing USB packets. I think this is the culprit here. Somehow the DOC is not writeable or eraseable anymore.

[buzz_lightyear]

some more info:

"task 28" is always issued after updating CEROM and EXTROM by RomUpgradeUt

On the device which I have, it fails with the error:

----------
USB>task 28
flFormatPhysicalDrive:status=23
DOC_format failed!
----------

I realized it while sniffing USB packets. I think this is the culprit here. Somehow the DOC is not writeable or eraseable anymore.
hi,
I said that before to morph, that he should try task 28 to reformat, but he's got the same error... so I said that time, that DOC is probably damaged/bad block or such...
I mean hardware failure... possibly, there might be some issue with that specific DOC production batch as well.

morph, please try d2s command, if you can dump the ROM.

buzz

[ady]

it hurts to say but think that is the case

let me describe how the problem occured. I was copying some files to the device and suddenly it refused to copy the files. i restarted but it didn't work so i did a hard reset after which it refused to boot. I think the DOC is now security locked making it totally unaccessible. I wonder if it is replacable because it sounds very sad to scrap an expensive piece of hardware.

[Tamirs]

I Have The SPV M5000
& I Updatet It With The Latest "Imate Rom"...
Everythng Was Gr8 But Then I Update With The New Orange ROM
Now I Have The Orange Splash Screen With # On It & Thats That...
I've Tryed To Do "Set 14 0" & To Flash It With Other Rom But Nothing.

I Dont Have AnyThing To Do But To Buy A New One...
Please Help Me.

Thanks

[ady]

try "task 28" through mtty. then update the rom if it succeeds

[KT]

morph, please try d2s command, if you can dump the ROM.

buzz

Hi Buzz...

Sure i'll try anything... Just tell me how... I have tried all the set 140 0, set 14 10, set 14 19, etc, commands...

Honestly u'll have to tell me what d2s commands are & how do i run them on my device... The only way of dumping ROM ( on a SD Card) that i knew was by using that tool which you gave me once. But i guess i'll need to go in the OS of the PPC for that as it wasn't a Win32 Command.


Bottomline : Just provide me with a stepwise algorithm of what to do & how to do it & i'll post back all the observations ...

Chao Buzz...

Regards,
mOrph

[ady]

morph, in general d2s command is not allowed and returns not allowed operation on a 1.00BL however you have an older version so we just want to see if it works or not.

connect through mtty and issue the d2s command. post the results here

[Tamirs]

I Did "Task 28" No Luck With That...
any Idia?

[ady]

what was the result of task 28?

[KT]

morph, in general d2s command is not allowed and returns not allowed operation on a 1.00BL however you have an older version so we just want to see if it works or not.

connect through mtty and issue the d2s command. post the results here

Hi ady,

How do i issue d2s command?

Regards,
mOrph

[Tamirs]

The Task 28 failed...

[buzz_lightyear]

Hi ady,

How do i issue d2s command?

Regards,
mOrph

Hi Morph,
you can issue that command while the device is in bootloader mode and you've made a connection to it with mtty terminal.

buzz

[Tamagochi]

My problem is more strange: I can do all bootloader commands with no problem: set 14 0, task 28, rtask 0... I can also upgrade all kinds of ROM, Radio with success. But after showing the boot splash screen, the screen became blue (whole screen is blue without any image) and stucks there forever. I tried to upgrade many times but it still couldnot pass this blue screen, some times the screen became grey but not blue.
Any idea, please
Thanks

[ady]

post the C:\RUU.log here.

[ady]

The Task 28 failed...

I'm afraid you are failing a similar problem where DOC become inaccessible.
If the device has warranty then send it in. Otherwise you have to wait till a solution is found.

[Tamagochi]

post the C:\RUU.log here.
Sorry, I did not find the RUU.log file anywhere. I used MAupgrade_noID to upgrade. May be it is because of the RUU.conf? Please look at my RUU.conf and check if there is any thing wrong

[PLATFORM]=857873
[RADIO_TYPE]=2
[SECURITY_FLAG]=1
[DECODER_KEY]=1
[RADIO_FLAG]=2
[GETADDR_TYPE]=1
[JUMPCODE_TYPE]=1
[FORMAT_TYPE]=2
[SCREEN_TYPE]=2

Regards!

[ady]

The RUU.conf is alright.

RUU.log must be there on your root drive. On my computer it is on C drive.

[Tamagochi]

The RUU.conf is alright.

RUU.log must be there on your root drive. On my computer it is on C drive.
Yes, you are right. I thought RUU.log should be in the current directory where i ran upgrade but it actually in the root directory of drive C:
Here is my RUU.log, but i did not see anything abnormal there

[ady]

now connect through mtty and do "task 28". Copy and paste the results here

[Tamagochi]

now connect through mtty and do "task 28". Copy and paste the results here
OK, here is the result
==============
USB>task 28
DOCInfoTableinitHW+
Binary0 Size: 0x100000
FAT0 Size: 0x4000000
FAT1 Size: 0xA00000
FAT2 Size: 0x2C70000
All Size: 0x7770000
FAT0_ADDR=0x100000,FAT1_ADDR=0x4100000,FAT2_ADDR=0 x4B00000
USB>

[ady]

Your DOC seems fine. hmmmm...
Try removing the sim and SD card and plug the USB cable directly into your PC. Then run the upgrade again.

[buzz_lightyear]

now connect through mtty and do "task 28". Copy and paste the results here
OK, here is the result
==============
USB>task 28
DOCInfoTableinitHW+
Binary0 Size: 0x100000
FAT0 Size: 0x4000000
FAT1 Size: 0xA00000
FAT2 Size: 0x2C70000
All Size: 0x7770000
FAT0_ADDR=0x100000,FAT1_ADDR=0x4100000,FAT2_ADDR=0 x4B00000
USB>

yes, it looks good....
try to go to Boot Options screen, by holding "Light button" after reseting it.
Then select:
Format Storage -> YES
Clean Reg Hive -> YES

buzz

[Tamagochi]

I then tried
USB>task 32
it returned the result:
Level = FF
Then tried
USB>task ?
The device itself exits from bootloader mode and start boot flash screen but again stucked at a grey screen.
Any action with the mtty did return the following result:
<CE-196609>
and I dont know what does it stand for!

[Tamagochi]

yes, it looks good....
try to go to Boot Options screen, by holding "Light button" after reseting it.
Then select:
Format Storage -> YES
Clean Reg Hive -> YES

buzz
Hi Buzz,
I did as you recommended but now i have white screen instead of blue or grey as before. Do i need another upgrade?
Regards!

[ady]

Your device looks fine. Weird that it doesn't work.

Does any of the LEDs blink when the splash screen is loading?

[Tamagochi]

Your device looks fine. Weird that it doesn't work.

Does any of the LEDs blink when the splash screen is loading?
None of the LEDs blinked when the splash image is loading. But when it came to the grey screen i got the charging LED, Call and Drop Call LEDs light permanently.
I also noted that, with Qtek Radio 1.06 and Exec Radio 1.09 i got a blue screen and with Dopod Radio 1.04 i got grey screen
Regards!

[buzz_lightyear]

yes, it looks good....
try to go to Boot Options screen, by holding "Light button" after reseting it.
Then select:
Format Storage -> YES
Clean Reg Hive -> YES

buzz
Hi Buzz,
I did as you recommended but now i have white screen instead of blue or grey as before. Do i need another upgrade?
Regards!
remove SD and SIM
start it in bootloader and reflash a complete ROM

buzz

[Tamagochi]

remove SD and SIM
start it in bootloader and reflash a complete ROM

buzz
Yes, i did it many times, without SD, without SIM card and with full ROM package etc. ROM, Radio and Extended ROM. Just have done once more and got the same result: a boot flash image and then a whole blue screen. Format Storage and Clean Reg Hive did not seem to work also.
Regards!

[buzz_lightyear]

Yes, i did it many times, without SD, without SIM card and with full ROM package etc. ROM, Radio and Extended ROM. Just have done once more and got the same result: a boot flash image and then a whole blue screen. Format Storage and Clean Reg Hive did not seem to work also.
Regards!

hmm, that's very strange...

[Tamirs]

This Is My File...

[ady]

in your case, there is a device CID error.

[dahuzi]

Hello all

I have a new problem never mentioned by others before. Mine toy is an O2 Exec. I have flashed many times of different ROM once I got it, never have the problem. Last night I flashed again the most updated Jasjar ROM with A2DP_MSFP version. It still works without any problem. Then I hack the Extended ROM by Buzz's tool ( I did few times before, everytime after flashing the ROM, no problem). Then I started to install the software. In summary, everything seems OK until this morning I found the RAM is a bit low then did a soft reset by psShutXP. The screen didn't react, just like power-off mode (no power supplied to LCD). Power button doesn't work anymore, the system died completely.

Now the sympton is as below:

1: Can't power on.
2: Can't charge the battery.
3: Can go into Bootloader mode, system can react with USB cable plug-in/out. (text swapping between Serial and USB).
4: Can do hard reset with two soft button + Reset button.
5: Can complete the Radio ROM flashing.
6: Can't complete the CE ROM flashing. Exit at around 7% if using English ROM or 16% if using Chinese ROM with error message code 112.
7: Can be connected with MTTY and can react with Set 14 0 and task 28.

Since I bought it through the 2nd hand market, so it's no way to have the repairing in China. I just paste the MTTY message and RUU.log for reference, please help me to recover it.

Message after run task28:

USB>task 28
Read data error in tag
DOCInfoTableinitHW+
Binary0 Size: 0x100000
MountVolume:status=23.
FAT0 Size: 0x0
FAT1 Size: 0xA00000
FAT2 Size: 0x2C40000
All Size: 0x3740000
FAT0_ADDR=0x100000,FAT1_ADDR=0x100000,FAT2_ADDR=0x B00000

RUU.log contents:

20:26:48:008 [msg] : Version : [2.11].

20:26:48:058 [msg] : Config Info : [857873],[1],[0],[0],[1],[0],[0],[1].

20:26:48:058 [msg] : RadioFile Not Exist !

20:26:48:058 [msg] : MSystemFile Not Exist !

20:26:52:324 [msg] : Current Not in CE Mode or in CE Mode but ActiveSync Not Connected.

20:26:56:670 [msg] : Disconnect ActiveSync .... [2]

20:26:56:670 [msg] : Start Get Connect Port.

20:26:56:870 [msg] : Current in BL Mode. Open Port : [\\.\WCEUSBSH003] OK.

20:27:01:447 [msg] : Device BL VER : [1.00 ] [].

20:27:01:487 [err] : Device CID Error.

20:27:01:487 [msg] : Update Image. CE : [4], MSystem : [0], Radio : [0]

20:27:11:371 [msg] : Check Ac in BL mode. AC : [1]
20:27:12:873 [msg] : IsBL. BL : [1]

20:27:17:911 [msg] : =============================================

20:27:17:911 [msg] : START UpdateCE !

20:27:19:012 [msg] : Upgrade 2 : 0 Start.

20:27:30:909 [msg] : Upgrade 2 : 0 End.

20:27:30:929 [msg] : Upgrade 2 : 1 Start.

20:27:42:506 [msg] : Upgrade 2 : 1 End.

20:27:42:506 [msg] : Upgrade 2 : 2 Start.

20:27:48:835 [err] :
BUF->{flAbsWrite is fail.:i=4000,ebstart=91000000
DOC_WriteFAT1 fail: Start=800000,Len=400000
HTCSF kE?HTCEUSB>}

20:27:48:845 [err] : Receive Data Error : 609 .

20:27:49:055 [msg] : Retry Write data Start.

20:28:07:782 [err] : Write Data Error.

20:28:07:782 [err] : BL UpdateCE Error.

20:28:07:802 [msg] : START UnInitialization !

20:28:07:842 [msg] : END UnInitialization !

20:28:07:842 [msg] : IsBL. BL : [1]

[buzz_lightyear]

20:27:01:487 [err] : Device CID Error.
CID error again...
hmm, what that might be... ??
buzz

[buzz_lightyear]

USB>task 28
Read data error in tag
DOCInfoTableinitHW+
Binary0 Size: 0x100000
MountVolume:status=23.
FAT0 Size: 0x0
FAT1 Size: 0xA00000
FAT2 Size: 0x2C40000
All Size: 0x3740000
FAT0_ADDR=0x100000,FAT1_ADDR=0x100000,FAT2_ADDR=0x B00000

USB>task 28
DOCInfoTableinitHW+
Binary0 Size: 0x100000
FAT0 Size: 0x4000000
FAT1 Size: 0xA00000
FAT2 Size: 0x2C70000
All Size: 0x7770000
FAT0_ADDR=0x100000,FAT1_ADDR=0x4100000,FAT2_ADDR=0 x4B00000
do you see the difference??
Dahuzi is missing the whole FAT0 partition!!!

Tamagochi's values are OK.

Whole OS is stored in FAT0. No wonder, that it doesn't boot :o(

i just did task 28 as well, on my yet still working device and here are the correct values:
USB>task 28
DOCInfoTableinitHW+
Binary0 Size: 0x100000
FAT0 Size: 0x4000000
FAT1 Size: 0xA00000
FAT2 Size: 0x2C70000
All Size: 0x7770000
FAT0_ADDR=0x100000,FAT1_ADDR=0x4100000,FAT2_ADDR=0 x4B00000


buzz

[Tamirs]

So If It's a device CID error...
What Can I Do?

[v4victory]

So If It's a device CID error...
What Can I Do?

Why dont you change the harddrive :wink:

[dahuzi]

I recall that I was touching the Extended ROM before resetting. I try to change the email storage setting from Storage Card back to main memory, just after the resetting, the devide died.

So I suppose the root cause if the FAT table or something else messed up and can't be recognized by the bootloader. Maybe a "low level format" can solve the problem, or it still can be saved from software site. Buzz, is my understanding correct?

BTW: I have sent my device to the seller and ask him try to repair. Properly he will replace the Flash ROM chip, I am not su sure.

Any clue is still welcome.

Thanks

Wilson

[ady]

I'm not sure if the DiskOnChip is available as a spare part.

[dahuzi]

What's the possibility to damage the chip physically? If it's not physical damaged, I think it can be recovered by software. But I don't know the details.

Or the last solution is send it back to HTC for repairing. Is it practical even the brand is O2?

[ady]

for one, it's definitelly not a dry solder. I resolder it and the error is still the same.

[MBosch]

I thing i have the same problem as ady.
I have a Vodafone V1640 and yesterday i upgraded it to the lastest version of Jasjar. Everything Ok till the hard reset. After it my Jasjar hangs on the Imate boot image. I've readen almost everything and i've tried also everything with these results:
1. Reflash the device. I've done that with lots of roms. No exit.
2. Set 14 0. Also no exit. Sometimes MaUpgradeUt_noID.exe doesn't find the devive (properly connected), sometimes it prompts a screen indicating that MaUpgradeUt_noID.exe is not te proper utility to upgrade my device.
3. Task 28. These results:
task 28
flFormatPhysicalDrive:status=23
DOC_format failed!
USB>

I've attached my ruu file.

Can anyone help me? If it is possible?

Lots of thanks.

[Tamirs]

Another One?
I Hope There Will Be A Way To Fix This Problem Or I Will Have To Buy Another Unit...
:( :( :(

[MBosch]

Me too.

[Tamagochi]

3. Task 28. These results:
task 28
flFormatPhysicalDrive:status=23
DOC_format failed!
USB>
.

Your DOC could be defected i guess. Usually, task 28 will be done with no error!

[MBosch]

So what do you suggest? Send it back to Vodafone and wait for a new one? I ve bought it three months ago.

[ady]

yeah... send it back if the warranty is valid.

[MBosch]

Ok. I will do that. Bur first i should replace Imate rom for Vodafone ones. And... I don't have Vodafones originals rooms. One problem more... Upps...

[Tamirs]

Seince the last rom update/
more and more seem to have this problem...

i dont think this is an hardware problem.

the only thing differnet for me was that i've opened the ext rom for the first time b4 i've update the rom.

so i guess there is a connection..?

[ady]

I'm not 100% sure if it is though I agree that it could be.

since universal is a recently released device so most of the people can get a warranty.

However if enough people have this problem and no warranty than someone can try taking ripping the boatloader somehow to analyze what is actually wrong.

[MBosch]

Can anyone provide me a backup ot the original Vodafone V1640 Rom. Mine is corrupted so i cannot upgrade back my device to its original rom in orden to send it to Vodafone.

Thanks...

[olliesshop]

I just heard from TOPP Solutions that "I-mate authorized the main board to be replaced. The ETD is two weeks. I wish there really was a better solution for this case. But they have found that by changing the main board it will be resolved."

They've been communicating with imate tech support over the last two weeks or so and have been unable to resolve the problem. I hope others can resolve it without replacing the board.

Total downtime, will be about 5 weeks, assuming I get it back in two weeks.

[buzz_lightyear]

Can anyone provide me a backup ot the original Vodafone V1640 Rom. Mine is corrupted so i cannot upgrade back my device to its original rom in orden to send it to Vodafone.

Thanks...
I wouldn't worry too much about flashing original rom to it...
they will not be able to read the doc, same as you are not.

I flashed alpine rom to my himalaya once, which rendered it dead and they fixed it under warranty

buzz

[MBosch]

Thanks.
Yesterday i sent my Universal to Vodafone...
Let's see what happens...

[Viper®]

Hmm, mine seems to be stuck in bootscreen as well

Never had problems, flashed from Tmobile -> qtek -> imate ->qtek

and now it stopped working. Try flashing it again. Then I'm trying the mtty and the rewrite rom solutions. If those don't work, I'll send it back to Tmobile.

[Tamirs]

I've Sent mine to orange...

[AlCapone]

Same here: (QTEK9000) - stuck at the blue splasscreen with version numbers..
-----------------
task 28
flFormatPhysicalDrive:status=23
DOC_format failed!
USB>
-----------------

[buzz_lightyear]

now, after reading all of the above, i'm really worried about my next ROM flashing...
i'll better think twice, before i'll do...

buzz

[buzz_lightyear]

btw, can we say, that the problem is related to anything? same brand? some operation?
i'm not gonna go through all those previous posts, but if there is someone, who has more time, maybe can summarize this problem...?

thanx
buzz

[PReDiToR]

I just put the latest WWE ROM into my m5000, and bricked it.

I put the .100 ESN in by mistake, thought about living with Spanish and decided to put the .90 WWE in.

Flashed it, did the hard reset, got the 0/X screen, hit 0.

It said Clearing Now, Clear OK ... Then nothing. Blank screen.

I'm having trouble now because I can't get the USB connection to work at all.
I can do a hard reset, put it into BL mode (without USB plugged in it says serial, putting the USB in changes it to USB mode), and when connecting it to the PC I get the device attached beep, but not the device installed and working sound that I get when I plug in my network card for instance.

When I try to reflash it gives me an error and cannot get the information from the unit for the flash compare screen.

My USB is fine, I have my BT dongle in the same port, that still works.

Whatever I have done to the m5000 has killed it's ability to connect via USB. I don't have USB in mtty, Buzz's BL fix says it can't find a USB connection.

I think I might have to send it back to Orange. PITA. I was hoping to be able to sort this one out myself seeing as all my other flashes have gone smoothly and this one is the one that challenges me.

Anyone have an idea?

[sandrobber]

topp sucks just contact imate via email and they will sen topp the part

[buzz_lightyear]

Flashed it, did the hard reset, got the 0/X screen, hit 0.

It said Clearing Now, Clear OK ... Then nothing. Blank screen.

can anyone else, with stucked device, please post here, how they did the hard reset?
Was it by holding down two "-" keys and then confirming by "0"?

I'm always doing hardreset bootloader way.
I mean to hold down "light" button after reset, till Boot Options screen comes and then i select "Format Storage - YES".

I don't know, but it might be, that the 0/X procedure is not doing the right job or behaves the wrong way..

THANX
buzz

[qtotter]

I don't know, but it might be, that the 0/X procedure is not doing the right job or behaves the wrong way..


i guess so, too. that's why i would like to know how all the guys who got their unis stuck at the splash screen reset their unis right after rom burning. was it [-]+[-]+[reset]?

qt

[telemix]

I have made it!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
I had the same problem (stuck in the boot screen, logo Qtek with rom informations). Today I have reinstalled Disk on Chip (DOC) from another Qtek 9000 and all has earned!!!!!!!!!!!!!!!!!!!
The decision is found!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Really a problem in bad blocks or damage of Disk on Chip. :D

[buzz_lightyear]

I have made it!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
I had the same problem (stuck in the boot screen, logo Qtek with rom informations). Today I have reinstalled Disk on Chip (DOC) from another Qtek 9000 and all has earned!!!!!!!!!!!!!!!!!!!
The decision is found!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Really a problem in bad blocks or damage of Disk on Chip. :D
do you mean, you've replaced the chip with another one?

we knew before, that it has bad blocks. main question is, how that happens?

buzz

[PReDiToR]

Flashed it, did the hard reset, got the 0/X screen, hit 0.

It said Clearing Now, Clear OK ... Then nothing. Blank screen.

can anyone else, with stucked device, please post here, how they did the hard reset?
Was it by holding down two "-" keys and then confirming by "0"?

I'm always doing hardreset bootloader way.
I mean to hold down "light" button after reset, till Boot Options screen comes and then i select "Format Storage - YES".

I don't know, but it might be, that the 0/X procedure is not doing the right job or behaves the wrong way..

THANX
buzz

I'll tell you tomorrow if your way works, new unit within 24 hours - one more reason to go Orange!

NB I didn't tell them I was flashing ... or that it was a Qtek ROM.

[telemix]

Yes, I replaced the chip with another one. Most likely it is factory defect. But I do not know, it is a mistake itself DOC or it has taken place in DOC at work accompanying IC or a mistake at a upgrade ROM. :?:

[ady]

so the point remains, from where to get the DOC G3 1Gb chip?

[PReDiToR]

Flashed it, did the hard reset, got the 0/X screen, hit 0.

It said Clearing Now, Clear OK ... Then nothing. Blank screen.

can anyone else, with stucked device, please post here, how they did the hard reset?
Was it by holding down two "-" keys and then confirming by "0"?

I'm always doing hardreset bootloader way.
I mean to hold down "light" button after reset, till Boot Options screen comes and then i select "Format Storage - YES".

I don't know, but it might be, that the 0/X procedure is not doing the right job or behaves the wrong way..

THANX
buzz

I'll tell you tomorrow if your way works, new unit within 24 hours - one more reason to go Orange!

NB I didn't tell them I was flashing ... or that it was a Qtek ROM.

I Flashed shipped ORUK 1.30.90 with the 1.09.00 radio in.

Used MaUpgradeUT, Left ActiveSync on but disabled USB. Turned Modem and Firewall off. Took SIM and SD out.
Reset, put Uni into bootloader (serial, v1.00), connected USB no hub.
BL changed to USB.
Ran upgrade, it didn't display currently installed versions, all three were blank.
Upgraded (how long??? =/ ), unplugged Uni, hit reset button only.
Rebooted, all worked well.

[paulojocelyn]

Please my friends, help me to fix this.
I bought a QTEK 9000 in France and i've problem to change my ROM to protuguese. Allways have a COUNTRY ERROR and i don't know how to fix it. I've changed all ready to 1.30.68 WWE Radio 1.09.00 and ExtROM 1.30.153 but it is a JASJAR. My memory looks weaker and i don't install anything yet. Can anyone help me???
Paulo.

[qtotter]

Used MaUpgradeUT, Left ActiveSync on but disabled USB. Turned Modem and Firewall off. Took SIM and SD out.
Reset, put Uni into bootloader (serial, v1.00), connected USB no hub.
BL changed to USB.
Ran upgrade, it didn't display currently installed versions, all three were blank.
Upgraded (how long??? =/ ), unplugged Uni, hit reset button only.
Rebooted, all worked well.

yeah, soft reset works.

i do not understand why people here still recommend unnecessary hard reset which i suspect causes the splash stuck.

[PReDiToR]

Might have something to do with following instructions - The last screen of the upgrade utility tells you to do a hard reset and shows you how (assuming you're using the right .EXE for your model).

[ady]

doesn't matter... task 28 which I suspect is equal to a hard reset is always ran after an update...

at this point I am forced to think that this is a manufacturing fault... probably caused due to static electricity

[qtotter]

at this point I am forced to think that this is a manufacturing fault... probably caused due to static electricity

If so, then, why has this problem not occurred with older ROMs before?

Well, it looks like guys who got their universals frozen do not really care about helping others to prevent them from the same problem...

[Viper®]

at this point I am forced to think that this is a manufacturing fault... probably caused due to static electricity

If so, then, why has this problem not occurred with older ROMs before?

Well, it looks like guys who got their universals frozen do not really care about helping others to prevent them from the same problem...

I find that remark a bit offensive. I mean all the info here and support is based on ppl's own experiences and time and no payed expertise.
Instead of looking at what's missing, look at what we offer here.

I say we but I'm not part of the xda-dev team or moderators. I'm just a
visitor like you.

nofi

[PReDiToR]

Signal to noise is getting low in this thread, and the lesson seems to be to hit the reset hole without the soft keys.

Add that to the first post of the upgrade threads, and add a FAQ and we have helped those who can/will read.

[qtotter]

Well, it looks like guys who got their universals frozen do not really care about helping others to prevent them from the same problem...

I find that remark a bit offensive. I mean all the info here and support is based on ppl's own experiences and time and no payed expertise.
Instead of looking at what's missing, look at what we offer here.

I say we but I'm not part of the xda-dev team or moderators. I'm just a
visitor like you.

nofi
i simply replied to ady's "doesn't matter."

anyway, have i simply been asking how they actually reset by their own experiences? did i ask for more in my comments?

does not really matter.

i agree with PReDiToR. i saw someone say "must hardreset" after rom burning in this forum, but it is not true.

[starche_old]

Hey, guys, finally, do we have a way, what shall we do if Uni got stuck? Of course, except "go to the service centre".

What does the guys who got stuck finally did?

I what to decide for myself should I risk to upgrade ROM or not in terms can I in future fix the problem IF it will appear or not.

Thx

[sandrobber]

If you flash the device and it sticks the hardware is bad anyways

[ady]

here is the status:

At the moment some people are able to get out of splash hangup by flashing again... some aren't...

Also task 28, which is ran each time at the end of a rom upgrade, fails on the devices which are permanently stuck at the splash screen

replacing the DOC G3 1Gb chip might be the solution however I am unable to locate any retail seller

there isn't any software solution available at the moment and it's hard to verify the problem due to locked up boot loader on universals

It is worth noting that not all of the devices got stuck due to ROM upgrade, some of the people simply did a hard reset... mine simply gave out an error of OUT OF SPACE although I had space available at that time (might be due to the fact that flash chip stopped working and OS was unable to commit changes to disk). I did a hard reset thinking that it is some software glitch and booom... it got stuck

p.s it seems more likely that the problem is due to increasing bad block on the chip than any other

[Viper®]

^^

There you have it.

SOme more info:

My bootscreen got stuck. What did't work:

-Flash again with same rom
-Flash again with rom changing supplierID
-Flash with original rom

Haven't tried
-mtty tool
-task 28


Reading through posts and info it seems there are devices completely stuck and won't get out. Seems maybe it's a hardware problem or software but it's occuring more and more, not before. Maybe due to the A2DP feature or updated roms.

There is NO solution yet for the problem. Many have taken it to service or send it for warranty. Until there is more info I haven't got a clue what you can do about it.

Flash is at your own risk. But I must say it happens a lot and if it is a hardware problem, it should be warranty. They can't sell me off with saying I flashed it with the TMOB uk rom instead of the NL one and therefor I lost warranty.
It's a mobile device, those are suppose to be updated and flashed multiple times. If you think you're gonna bring a device to the market and have people running the initial software for 3 years or having to bring it in to update it, get real.

[buzz_lightyear]

doesn't matter... task 28 which I suspect is equal to a hard reset is always ran after an update...

at this point I am forced to think that this is a manufacturing fault... probably caused due to static electricity
that's a big difference, I think, coz task 28 is a bootloader routine, but the instructions says you have to press two hw keys after reset. this is completely different routine and might be causing the problem.
but I still think, that it is a hw fault and would definitely go for warranty repair.

buzz

[buzz_lightyear]

...it would be nice, to have a tool, which will check DOC health on Universals (those still running ones) and will warn you, when things gets close to something bad.

buzz

[magicofavalon]

I have a SPV M5000 from Orange, unable to receive true push email I found an Orange upgrade (linked from microsoft) called "M5000 email.exe", followed the instructions and the PPC crashed. There was no USB driver for the PPC and I was left with a basic screen saying "Serial v1.00". After phoning Orange they sent me a new phone.....
Determined (as I am) I did it again and lo and behold got the same BSOD.

The Fix came from www.whitehorse-consultants.com

Install AppSuite Installer WWE 2.0.0.4.exe

rerun "M5000 email.exe" and Hey Presto, Bob's yer Uncle, Fanny's yer Aunt

[ady]

doesn't matter... task 28 which I suspect is equal to a hard reset is always ran after an update...

at this point I am forced to think that this is a manufacturing fault... probably caused due to static electricity
that's a big difference, I think, coz task 28 is a bootloader routine, but the instructions says you have to press two hw keys after reset. this is completely different routine and might be causing the problem.
but I still think, that it is a hw fault and would definitely go for warranty repair.

buzz

buzz buddy, from a programmer perspective, two different methods to do hard reset sounds unlikely... Are you sugesting that the two key press method do something other than a hard reset or that task 28 doesn't do hard reset?

Also as I've already said, my problem occured while the unit was running. I didn't do any hard reset neither any ROM upgrades at that particular time...

[buzz_lightyear]

buzz buddy, from a programmer perspective, two different methods to do hard reset sounds unlikely... Are you sugesting that the two key press method do something other than a hard reset or that task 28 doesn't do hard reset?

Also as I've already said, my problem occured while the unit was running. I didn't do any hard reset neither any ROM upgrades at that particular time...
eh... :o) there are many ways to hard resert WM5 device..
for example:
delete your FAT0 partition...
or you run CleanStorage.exe...
or you call a kernel IOCTL...
or do it with a bootloader...

How do you know, what exactly is programmed behind 0/X method?
Can you be abslolutely sure, that it is exactly the same as task 28?

Read this:
http://blogs.msdn.com/ce_base/archive/2006/02/09/How_OEMs_implement_Clean_Boot_on_WM5.aspx#535936

What if it's additionally doing something else? It may send a special signal to extraterrestrians, just before it really hardresets... or??

:o))
buzz

[nedge2k]

nm...problem fixed

http://www.msmobilenews.com/page/1223/

users with v0.56 bootloader, read that ^^

[starche_old]

nm...problem fixed

http://www.msmobilenews.com/page/1223/

users with v0.56 bootloader, read that ^^

It look the problem really-really fixed? SO simple - just version of bootloader?

Now I'm in doubts - should I try to upgrade or not. But it looks lots of guys, who got stuck had fixed their problems.

One question: how (or where I an read) about upgrading the version of bootloader?

Thx

[qtotter]

But it looks lots of guys, who got stuck had fixed their problems.

You mean a lot of people sent their machines to their phone service providers?

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

[Asukal]

how about this thread?

http://forum.xda-developers.com/viewtopic.php?p=276086#276086

try to replace Boot loader with this.

if this problem came from damaging of Boot Loader,
Are there possiblitity of recover by replacing bootloader?

unfortunatry, i am on trip and Damaged Exec is not with me,
so can not test it by myself..............

need brave guy!

this thread is correct one....
http://forum.xda-developers.com/viewtopic.php?t=48590 :?

[angeln20]

i cannot install bootloader it says to me country id error please help.....the MaUpgradeUt_noID.exe doesn\t work

[MBosch]

My precious V1640 is still at Vodafone. Three weeks waiting.
Ahhhhhhhhhhhhh
:evil: :evil: :evil: :evil:

[buzz_lightyear]

hi stuck guys ;o)))
can all of you, who's stuck at splash screen, please post your bootloader versions?

thanx
buzz

[buzz_lightyear]

nm...problem fixed

http://www.msmobilenews.com/page/1223/

users with v0.56 bootloader, read that ^^
dear nedge2k,
if you would review this thread again, from the beginning, same as I just did, you'd find out, that there are devices stuck at splash screen WITH BOOTLOADER v1.00 as well.

so I pretty much doubt, that the link you've posted above is any help here.
oh well, it wasn't any help anyway, am I right?

;o)))
buzz

[shaytaan]

My Jasjar was good but one day it stucked at splash screen.. Why? God take me too :,( "I updated the the rom to the newest version a week ago"
my boatloader is 0.6 (And I cant upgrade to boatloader v1 becouse of country error)

Please help...this is my secound device dying :twisted:

[Asukal]

hi stuck guys ;o)))
can all of you, who's stuck at splash screen, please post your bootloader versions?

thanx
buzz

hi!
My Exec stucked one has Ver1.0,
Another Jajsar has Ver 0.6 and neverstucked.

[MBosch]

Bootloader Version
1.00
:D

[shaytaan]

Someone please solve this! :cry: What should we do? :cry:

[ady]

hmmm there is a new bootloader 1.01 for jasjar on imate's ftp... works with no id update... but doesn't solve anything

[Tamirs]

Just Got An Email From HTC
They Told Me That My Main Board needs To Be Replaced...

[buzz_lightyear]

hmmm there is a new bootloader 1.01 for jasjar on imate's ftp... works with no id update... but doesn't solve anything
can you please download it and post it here?

thanx
buzz

[ady]

buzz, it has already been posted here:
http://forum.xda-developers.com/download.php?id=11271

the link to imate ftp:

ftp://ftp.clubimate.com/JASJAR_BL1.01_RUU_V1.2.zip

The bootloader version display changed to 1.01 after upgrading however rest of the characteristic of the stuck exec are the same i.e. doc formating failed. Also the file size is 512kb which is good for a bootloader however 95% of the bytes are repeating which means that it is only a small part of the actual bootloader.

In general it doesn't seem helpful for the devices which are stuck.

[hdubli]

To All and Buzz
I reapair lot of PPCs and PPC phones.Also got these types of cases and except the morphosin's I hv resolved all of them.

I repeat...while flashing these UNIs, I hv always checked for the battery level >50%...always put them in the Bootloader mode first and then flashed them..never got a stuck screen irrespective of the Boot Loader Version.

My experience tells that in case of exec or Bootloader v 1.0 if immediately Radio is flashed, the device boots up properly.

In case of JASJAR(never get Qteks and other brands) changing the battery and flashing with Radio works...else the method posted works.

I hv been thinking a lot from all points and my expereince as I was working with Electronic Manufacturing Services company wherein they hv to deals with lots of PCB designing,populating troubleshooting..In these the biggest bottle neck used to be the Static Current from human body.We used to get the Micons damaged/dead when the stores manager touched them for counting them and they were dead..

I am applying same logic here...but from where the hell this static current reaches to Flash...I think it is via USB charging port.Just think about all other PPCs, they hv got the charging from below, but UNI's case it is from side and the user might be touching the port 100 times while taking or making a call.

So in case of ady and morphosin..I think the static current seems to be issue as it has damaged the Flash.

This is just my summing up from whatever knowledge I hv got..others can well asses this and confirm

[sandrobber]

I didn't knowinly touch the usb port and have made probably 50 calls. I still think this may be a bad batch

[nicolito]

same problem on M5000 blocked on splashscreen and task 28 doesn't work.

upgrade on BL 1.0 don't solve pb. i'm sad for my universal.
anything to do ??

Br's

[zoroskynet]

My Jasjar do not boot. It stuck on boot screen with serial numbers. Bootloader version was 0.6. Upgraded to 1.01 bootloader but no change. I will try to send it back to Dubai for repair.

Local expert tald me that the board should be replaced.

Regards,

[buzz_lightyear]

My Jasjar do not boot. It stuck on boot screen with serial numbers. Bootloader version was 0.6. Upgraded to 1.01 bootloader but no change. I will try to send it back to Dubai for repair.

Local expert tald me that the board should be replaced.

Regards,
use the "ExitBL.exe" utility. it is attached somewhere in this thread...

buzz

[BigKuri]

Hi All,

After lurking on the site for some time (years?) and owning a himalaya, blue angel, alpine, and now a universal I’m finally posting! First off – thanks. Thanks to all who contribute and make such a great resource.

My Universal too was stuck in the boot screen, in my case showing the O2 logo plus build info, and that’s where it would stop. Like many – it happened when upgrading to the latest O2 release.

I’ve read what feels like thousands of pages in researching my problem, and tried absolutely everything that has been suggested. The straw that broke the camels back was simply the task 28 in mtty - failed....

Yesterday I finally gave up, and returned the unit to O2. They took me through some simple tests over phone support (basically hard resetting the device) and then simply said "send it in, and we will replace it with a brand new unit". They also let slip that many such returns have been happening. I luckily was able to do this through the technical support team at work – and the guy dealing with it used to work with such devices & for what it is worth he thought that it was a simple dodgy manufacturing error or fault in early hardware to blame (not static electricity or other things that have been surmised).

For those stuck on the boot screen, trying every suggestion of different reset combinations, set 14’s, old ROMs, new radios, etc. – my advice is to run mtty with task 28 and if it fails - forget it and return under warranty. I hope that this is seen as helpful – as there seems no decent conclusion that was drawn in this (and other) posts.

The good news is that with a bit of pushing, O2 are sending out a new unit tomorrow, so I should get it within 3-4 days of reporting the error; not painful at all. The bad news is that while being universal’less over last day I’ve dusted off the old XDA2i, and it is surprisingly good…..

Cheers all,
BigKuri

[dolbe]

my Qtek 9000 froze on the splash screen about 5 weeks ago now, if i would of seen this post then i would of attempted to fix it myself. but since i didnt ive sent it back under the warrenty to be fixed, it was barely 2 weeks old. im still waiting to see whats happened, apparently it had to go to germany to be fixed :roll:

[MBosch]

Last friday Vodafone sent me back my V1640 (a new one). Inmediatly I flashed it with the new Qtek rom (using bootloader method) and... everything Ok.
I can't understand why the last time I tried to do exactly the same (same ROM, same method), the machine get stucked at Qtek boot screen.
:cry:

[BigKuri]

Likewise - just got the new one this morning. Charged it, flashed it, and everything is fine. Can only conclude it is dodgy & flaky hardware. :shock:
BigKuri

[jamesmcuk]

I know this won't help anyone but I thought I would share what happened to me.
I flashed the new Dopod rom and it went on perfect. It ran perfect and I installed all my apps and settings.

The next morning I cradled it for GPS nav via bluetooth which I had already set up easily.

I started the car with TomTom running and the parrot 3100 turned on and tried to pair with it. I OK'ed it and entered the passcode. TomTom came back on and was very jerky. It then hung. Screen turned slowly to bright turquiose.

Reset it hung at splash

Took battery off it booted to windows, ran tomtom and hung

Reset it hung at splash screen permenantley

I tried all the suggestions in this thread and none made any differenace however task28 worked correctly and I could alternate between being stuck in bootloader and splash screen using the set command in mtty.

I reflashed it after doing a task 28 and a hard reset for good measure and it is booting fine again now. Very weird

Since this rom battery seems quick to drain.

[BUMP THAT]

Hi Buzz. I had to stop by and say thank you. WHen I was trying to upgrade my Exec ROM, I got stuck in bootloader. Your ExitBL app help greatly. Thank You!

[buzz_lightyear]

oh... ;o)))
I saw a last post by BUMP THAT and I did think to myself...
yeah, cool nick for those "bump" posts ;o)))

buzz

[BUMP THAT]

oh... ;o)))
I saw a last post by BUMP THAT and I did think to myself...
yeah, cool nick for those "bump" posts ;o)))

buzz

:lol: LOL

[siemens man]

hi guys.
i have same problem with my MDA PRO need solution help me
thanks a lot

[BigKuri]

Hi,
Solution is pretty simple -
1. Use mtty "task 28".
2. If it works then you can re-flash
2. If is "fails" then hand your exec back and get a new one = its toast.

Detailed instructions on how to get & use mtty in this most (back a few pages).

Cheers
BigKuri

[shaytaan]

I used mtty and get this messege and the phone is the same :(

task 28
flFormatPhysicalDrive:status=23
DOC_format failed!
USB>


Then I tried set 14 0
And I get this messege but the phone is the same :(

USB>set 14 0
HTCST ÚÈÒHTCEUSB>

HELP

[siemens man]

hi guys
i have same problem with MDA Pro. stay only in boot loader mode show only: serial v1.00. i'm try with many rom files. no result. my phone no reboot normaly. help me
please tell me how inter to task mode. i'm push light+power+ reset. i can't enter.
help me pleaseeeeeeeeee here is my log
thanks a lot
now connect through mtty and do "task 28". Copy and paste the results here
OK, here is the result
==============
USB>task 28
DOCInfoTableinitHW+
Binary0 Size: 0x100000
FAT0 Size: 0x4000000
FAT1 Size: 0xA00000
FAT2 Size: 0x2C70000
All Size: 0x7770000
FAT0_ADDR=0x100000,FAT1_ADDR=0x4100000,FAT2_ADDR=0 x4B00000
USB>

yes, it looks good....
try to go to Boot Options screen, by holding "Light button" after reseting it.
Then select:
Format Storage -> YES
Clean Reg Hive -> YES

buzz

[qtotter]

hi guys
i have same problem with MDA Pro. stay only in boot loader mode show only: serial v1.00.

your problem is not the same. refer to here.
http://forum.xda-developers.com/viewtopic.php?t=33191

just reflash only a radio rom or use the tool buzz developed to exit the bootloader loop.

qt

[buzz_lightyear]

@ siemens man

search for ExitBL.exe

buzz

[siemens man]

hi guys
thank you for reply mail. i'm update my phone boot to ver 1.02, and my phone turn on. all problem solved. now good working
thanks to Buzz

[cool_case]

When trying to upgrade my ROM back in early March, ran into the stuck in bootloader problem. I-mate authorized sending my JJ to TOPP Solutions for a MB replacement. They received it on March 23rd and just got it back to me on May 10th. Whew ...

Until checking back in with xda-dev today, had no idea the problem was so widespread. Thought my loading the new ROM a week before release might have been a factor, but that wouldn't have made sense because doing so had never caused a problem on several other HTC devices.

The new ROM is faster and the memory leak from apps not fully closing is quite a bit less.

[cedricbrossard]

Hi everyone,

I applied the docs I found (killing wcsecomm & wcsemgr) but when I plug the qtek 9000 with the USB cable, I only obtain the following :

PPC locked in bootloader mode : "Serial v1.00"

and

"USB device not recognized" on windows XP.
ActiveSync was working perfectly before.

Then of course no upgrade or flash is possible.
mtty using \\WCEUSUSBSH001 give me "port cannot open"
trying to flash only the radio or all 3 things give me error 150 or 101.

I tried many hard & soft reset - + - + reset 0/X etc. while connected/disconnected, same result. I of course remove the SD & the SIM.

It's a French Universal black.

I'm surely missing something....but what ?

Thanks by advance for any advice or lecture.

Before trying rom update, my version where :
ROM : 1.13.72 FRE
Date : 10/13/05
version radio : 1.03.00
protocole : 42.36.P8
extrom 1.13.166 FRE

[qtotter]

I applied the docs I found (killing wcsecomm & wcsemgr) but when I plug the qtek 9000 with the USB cable, I only obtain the following :

PPC locked in bootloader mode : "Serial v1.00"

and

"USB device not recognized" on windows XP.
ActiveSync was working perfectly before.

This sometimes happens to me. Try another USB port.

When this happens, I usually turn ON USB in ActiveSync and connect my Universal and turn OFF USB in ActiveSync again, and put my Uni into the bootloader. If I keep doing it, the PC recognizes the Uni all of a sudden.

Is there a smart way to make the PC to recognize the uni?

qt

[cedricbrossard]

Hi guys,

here is an update

My problem was a bad USB cable.
Changed to another one and voila, immediately & correctly detected.

Step 1 : Radio 1.03 --> 1.09 OK
Step 2 : 1.09 --> 1.11 OK
Step 3 : ROM 1.13 --> 1.30.97.186 FRE (without) OK

And now it works like a charm :^)

See ya
Cedric.

[hh686]

hi guys
thank you for reply mail. i'm update my phone boot to ver 1.02, and my phone turn on. all problem solved. now good working
thanks to Buzz

Hi! Semens men
where are you download Bootloader 1.02?

My bootloader is 1.01, tell me to try. thank you!

[qtotter]

My problem was a bad USB cable.
Changed to another one and voila, immediately & correctly detected.


maybe, i should change my cable, then...

[nedge2k]

nm...problem fixed

http://www.msmobilenews.com/page/1223/

users with v0.56 bootloader, read that ^^
dear nedge2k,
if you would review this thread again, from the beginning, same as I just did, you'd find out, that there are devices stuck at splash screen WITH BOOTLOADER v1.00 as well.

so I pretty much doubt, that the link you've posted above is any help here.
oh well, it wasn't any help anyway, am I right?

;o)))
buzz

erm...it says v0.56 so it only helps people with v0.56. Pre 0.60 bootloaders are not compatible with AKU2 roms and THAT is the problem I was addressing here as some people will have come to this thread after having that problem to find answers. Thats what I did and there werent any so i figured it out for myself and posted a warning to others. If my help is not welcome then maybe i should just stop posting here...

[buzz_lightyear]

nm...problem fixed

http://www.msmobilenews.com/page/1223/

users with v0.56 bootloader, read that ^^
dear nedge2k,
if you would review this thread again, from the beginning, same as I just did, you'd find out, that there are devices stuck at splash screen WITH BOOTLOADER v1.00 as well.

so I pretty much doubt, that the link you've posted above is any help here.
oh well, it wasn't any help anyway, am I right?

;o)))
buzz

erm...it says v0.56 so it only helps people with v0.56. Pre 0.60 bootloaders are not compatible with AKU2 roms and THAT is the problem I was addressing here as some people will have come to this thread after having that problem to find answers. Thats what I did and there werent any so i figured it out for myself and posted a warning to others. If my help is not welcome then maybe i should just stop posting here...
hi nedge2k,
your HELP is of course welcome...
but at the time, you posted, that it is needed to upgrade bootloader, there was no BL upgrade package available (now it is), and you were saying that you did upgrade yours.
I asked you how, and you replied, that you won't tell (very short written. It was few PMs).
That's why i wrote, that your help was not a help actually...

take care
buzz

[ARZLEB]

Hey guys,

well i browsed trough all the pages and a friend's JasJar was stuck on the blue Splash screen. I tried everything mentioned here but didnt work... then yesterday i downloaded the new ROM for the Imate JasJar and upgraded it using the Bootloader and now the device is working fine with no problems so far.

so i think there is hope and a way after all.

[buzz_lightyear]

Hey guys,

well i browsed trough all the pages and a friend's JasJar was stuck on the blue Splash screen. I tried everything mentioned here but didnt work... then yesterday i downloaded the new ROM for the Imate JasJar and upgraded it using the Bootloader and now the device is working fine with no problems so far.

so i think there is hope and a way after all.
Hi ARZLEB,
could you please post the link to that ROM?

THANX
buzz

[ARZLEB]

Hey guys,

well i browsed trough all the pages and a friend's JasJar was stuck on the blue Splash screen. I tried everything mentioned here but didnt work... then yesterday i downloaded the new ROM for the Imate JasJar and upgraded it using the Bootloader and now the device is working fine with no problems so far.

so i think there is hope and a way after all.
Hi ARZLEB,
could you please post the link to that ROM?

THANX
buzz

yes for sure:

http://www.imate.com/support/JASJAR/ROM/JASJAR_ME_13082_171_10900_wwe_ship.zip

[indra9110]

Hey guys,

well i browsed trough all the pages and a friend's JasJar was stuck on the blue Splash screen. I tried everything mentioned here but didnt work... then yesterday i downloaded the new ROM for the Imate JasJar and upgraded it using the Bootloader and now the device is working fine with no problems so far.

so i think there is hope and a way after all.
Hi ARZLEB,
could you please post the link to that ROM?

THANX
buzz


actualy what is the best and the fastest ROM for Universal for NOW ???

THANKS in Advanced

[ARZLEB]

Hey guys,

well i browsed trough all the pages and a friend's JasJar was stuck on the blue Splash screen. I tried everything mentioned here but didnt work... then yesterday i downloaded the new ROM for the Imate JasJar and upgraded it using the Bootloader and now the device is working fine with no problems so far.

so i think there is hope and a way after all.
Hi ARZLEB,
could you please post the link to that ROM?

THANX
buzz


actualy what is the best and the fastest ROM for Universal for NOW ???

THANKS in Advanced

The Imate's latest realease for JasJar is very stable and fast. After the successful recovery of the JasJar i did 2 days ago the device is fast and not lag... at least for now even when using WiFi is better and faster then before.

at least i will give 2 more days before my last judgement.

[tuanvic]

hi guys
thank you for reply mail. i'm update my phone boot to ver 1.02, and my phone turn on. all problem solved. now good working
thanks to Buzz

hi buddy, can u plz tell me where can i download boot ver 1.02 for my exec? or can u upload it and share with every one in here? :D

puch of thanks!!!

[florino69]

i have a problem finding the USB port on the mtty application, after i open the aplication and i have to select the wsc... port i can't find it, i only have com 1 and com 2. What can i do?

[bitshaker]

Hi all,

I also got the problem of getting stuck in splash screen on a MDA Pro. This happened after I applied the latest T-Mobile ROM upgrade. As I saw, it updated the bootloader to version v1.01 prior to upgrading CE, Radio and Extended Rom. Since this update I can't boot any more, everytime it stucks in Splashscreen (tried many of the suggestions mentioned here).

I know that I had bootloader v0.6 installed before, which was running fine and did not cause any problems. So is there a way to get my old v0.6 version back (I also have another device running v0.6 available, perhaps there is a way to extract it from there?)

Many Thx

[shing]

Hi all,

I also got the problem of getting stuck in splash screen on a MDA Pro. This happened after I applied the latest T-Mobile ROM upgrade. As I saw, it updated the bootloader to version v1.01 prior to upgrading CE, Radio and Extended Rom. Since this update I can't boot any more, everytime it stucks in Splashscreen (tried many of the suggestions mentioned here).

I know that I had bootloader v0.6 installed before, which was running fine and did not cause any problems. So is there a way to get my old v0.6 version back (I also have another device running v0.6 available, perhaps there is a way to extract it from there?)

Many Thx

i dont think its the bootloader, becoz my mda pro was working fine when i used the Qtek WWE rom with bootloader v1.00. and when i updated it with the dutch T-mobile rom it upgraded the bl to v1.01. and i also got stuck in the splashscreen. so i downgraded the bl to v1.00 and flashed the old Qtek WWE rom and it was still stuck in the splashscreen.

[sandrobber]

it is the bootloader. Its noted on the imate website