yashsingh1/xdaforums huggingface dataset:
[JASJAR, XDA Exec, MDA Pro Software Upgrading] Jorgee:
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.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] 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
[JASJAR, XDA Exec, MDA Pro Software Upgrading] angeln20:
i hope to make a little program for us that we stuck in the splash screen....... :D
[JASJAR, XDA Exec, MDA Pro Software Upgrading] buzz_lightyear:
once i'll know, why it is not booting further...

Anyone ready with the KITL log?

buzz
[JASJAR, XDA Exec, MDA Pro Software Upgrading] qtotter:
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
[JASJAR, XDA Exec, MDA Pro Software Upgrading] qtotter:
Re: MATTER OF FACT

first of all, i sympathize your broken heart from all of this stress and am not trying to be *****y, 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.)
[JASJAR, XDA Exec, MDA Pro Software Upgrading] 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.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] 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.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] 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...

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
[JASJAR, XDA Exec, MDA Pro Software Upgrading] Asukal:
Recovering with Platform Builder

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/...00-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/downl...90828a8112c2/Release Notes Windows CE 5.0.htm

---------------------------------------------------------------

Do someboday have any other idea from those links?
[JASJAR, XDA Exec, MDA Pro Software Upgrading] KT:
Re: Recovering with Platform Builder

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
[JASJAR, XDA Exec, MDA Pro Software Upgrading] 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:
[JASJAR, XDA Exec, MDA Pro Software Upgrading] qtotter:
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...
[JASJAR, XDA Exec, MDA Pro Software Upgrading] KT:
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
[JASJAR, XDA Exec, MDA Pro Software Upgrading] KT:
DIFFERENCE IN RUU Log File

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
[JASJAR, XDA Exec, MDA Pro Software Upgrading] buzz_lightyear:
hi morph,

are you able to successfully flash ExtendedROM only?

please try and post the log...

thanx

buzz
[JASJAR, XDA Exec, MDA Pro Software Upgrading] KT:
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
[JASJAR, XDA Exec, MDA Pro Software Upgrading] 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
[JASJAR, XDA Exec, MDA Pro Software Upgrading] olliesshop:
Latest Update on ROM upgrade warranty fix

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.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] sandrobber:
rom upgrade

this is true in my case also but they do hve six buisness days to repair or give you a refurb
[JASJAR, XDA Exec, MDA Pro Software Upgrading] apbristow:
Eternal thanks

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
[JASJAR, XDA Exec, MDA Pro Software Upgrading] zYxMa:
Warranty??

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:
[JASJAR, XDA Exec, MDA Pro Software Upgrading] Jorgee:
Enter BL again by pressing Backlight+Power+reset hole.

Then upgrade only radio....

This might work
[JASJAR, XDA Exec, MDA Pro Software Upgrading] apbristow:
Reason for getting stuck in Botloader?

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.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] 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 :(
[JASJAR, XDA Exec, MDA Pro Software Upgrading] ady:
hmmmm KITL doesn't work. after turning it on, it just get stuck at the KITL screen and doesn't go any further
[JASJAR, XDA Exec, MDA Pro Software Upgrading] zYxMa:
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! :)
[JASJAR, XDA Exec, MDA Pro Software Upgrading] 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.....
[JASJAR, XDA Exec, MDA Pro Software Upgrading] buzz_lightyear:
imagine, that you want to reinstall your PC, which is full of **** 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
[JASJAR, XDA Exec, MDA Pro Software Upgrading] buzz_lightyear:
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
[JASJAR, XDA Exec, MDA Pro Software Upgrading] 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 !
[JASJAR, XDA Exec, MDA Pro Software Upgrading] qtotter:
hi buzz,

if it is the only reason, you can hardreset later after you burn a rom and softrest. correct?
[JASJAR, XDA Exec, MDA Pro Software Upgrading] KT:
Hi Buzz...

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

Thanx

Regards,

mOrph
[JASJAR, XDA Exec, MDA Pro Software Upgrading] Waltzing Mathilda:
QTEK 9000 stuck in bootloader - a fix that might help.

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.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] ady:
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
[JASJAR, XDA Exec, MDA Pro Software Upgrading] 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.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] buzz_lightyear:
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
[JASJAR, XDA Exec, MDA Pro Software Upgrading] 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.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] Tamirs:
Blue Screen (or Orange)

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
[JASJAR, XDA Exec, MDA Pro Software Upgrading] ady:
try "task 28" through mtty. then update the rom if it succeeds
[JASJAR, XDA Exec, MDA Pro Software Upgrading] KT:
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
[JASJAR, XDA Exec, MDA Pro Software Upgrading] 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
[JASJAR, XDA Exec, MDA Pro Software Upgrading] Tamirs:
I Did "Task 28" No Luck With That...

any Idia?
[JASJAR, XDA Exec, MDA Pro Software Upgrading] ady:
what was the result of task 28?
[JASJAR, XDA Exec, MDA Pro Software Upgrading] KT:
Hi ady,

How do i issue d2s command?

Regards,

mOrph
[JASJAR, XDA Exec, MDA Pro Software Upgrading] Tamirs:
The Task 28 failed...
[JASJAR, XDA Exec, MDA Pro Software Upgrading] buzz_lightyear:
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
[JASJAR, XDA Exec, MDA Pro Software Upgrading] 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
[JASJAR, XDA Exec, MDA Pro Software Upgrading] ady:
post the C:\RUU.log here.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] ady:
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.