yashsingh1/xdaforums huggingface dataset:
[JASJAR, XDA Exec, MDA Pro Software Upgrading] -Jonny-:
You must first unlock ROM before flashing

Try running MaUpgradeUt_noID.exe again.

In instructions it says wait patiently.

I know a full ROM+RADIO can take 20-40 minutes. I cannot remember how long this takes. So wait an hour before giving up. (anyone else know how long?)

Install Instructions

1. Backup your phone (not necessary, but advisable).

2. Remove your SD Card.

3. Enter bootloader mode on your Phone. To do this, simultaneously hold down the backlight key (“bulb” key, next to volume key), the power key and soft reset the phone. Your phone screen should clear, and you will see very faint writing saying “serial”. Let go of buttons etc.

4. Connect your phone to your computer using the USB lead.

5. Run the MaUpgradeUt_noID.exe program – this will reflash your phone with necessary software required to enable the unlocker.

6. Wait patiently.

7. Once the MaUpgradeUt_noID.exe upgrade completes, soft reset your phone by pressing the soft reset button on the back of the device [if the flash has been successfully applied, you should see that you now have Radio version 0.00.00]

8. Allow your phone to reboot. Once it has, connect to your PC using Activesync, and copy the UNI_Unlock_v1.exe program onto your phone. Alternatively, copy it to an SD card and insert into your phone.

9. Run UNI_Unlock_v1.exe on your phone. Wait patiently.

10. Once the process completes, soft reset your phone.

11. Process is (hopefully) complete!

References

wiki here

HTC_Uni_SIM_Unlock_v1.rar download here
[JASJAR, XDA Exec, MDA Pro Software Upgrading] da1deycallzean:
ok im making progress but when i go to run the MaUpgradeUt_noID.exe download im getting a error say compenant errot. Its says tool cannot bcuz the RUUI thingy is incorrect. It suggested renunstalling the tool. I keep gettin the same error message
[JASJAR, XDA Exec, MDA Pro Software Upgrading] da1deycallzean:
lol and ofcourse i have a G4 device so i couldnt use the excellent tutorial link as it was only for G3's. R there ne threads to unlocking a G4 device?
[JASJAR, XDA Exec, MDA Pro Software Upgrading] -Jonny-:
Unlocking G3 and G4 is same... I can't see where the tutorial says it's only for G3's? (You only have to watch what ROM you are flashing - although many are for both G3 and G4).
[JASJAR, XDA Exec, MDA Pro Software Upgrading] da1deycallzean:
FINALLY!!!!!

I have to first say thanks for all the help i received this is my first time in this type of forum setting. People here are very helpfull. I found that like many people have told me vista was my problem. Hooked my exec to a xp and the process was smooth im back in business.

thanks for ur help john an to all others who assisted me!!
[JASJAR, XDA Exec, MDA Pro Software Upgrading] Erikih:
HC Universal failed to flash the wm6.5 beta 9 test 1 from luca16thebig

Hi all,

After a hard night trying to get my universal back alive, ive tried the mtty method in page 38 i guess. I've flashed DarkForce wm6 dutch and it freezes at 99%, than ive decieded to reset my universal and guess what, it BOOTS! Well i wonder if someone got the same problem and i want to know if my universal is fixed, because i dont want to brick it again lol.:confused:
[JASJAR, XDA Exec, MDA Pro Software Upgrading] umair muddassir:
Cant boot with my i-mate jasjam herm100

please help me with this..

when i start my i-mate it stucks while loading windows mobile...

will some 1 tell me how to solve this problem with a easy way!!!!

thnxxx
[JASJAR, XDA Exec, MDA Pro Software Upgrading] orb3000:
Wrong section

Welcome to forums

You are in the wrong section...Universal does not means all devices!, in fact is a model:eek::eek:

Visit Hermes section

Good luck,
[JASJAR, XDA Exec, MDA Pro Software Upgrading] bahrom:
how do you do it when you have a vista with no active sync?
[JASJAR, XDA Exec, MDA Pro Software Upgrading] onesolution:
OMG

Thank you people of the xda world. The mtty work for me. Just go through the steps and make sure you hit enter and then soft reset. Then BAM back to normal. :D.

Oh yah dont use that vista crap. You need to run this on XP. For some reason it didnt give the option for usb in vista.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] orb3000:
Welcome to forums

Glad to see it worked for you

As you can see all is question of reading and searching

Now enjoy!
[JASJAR, XDA Exec, MDA Pro Software Upgrading] allen501:
where can I download the MTTY 1.4 and can it work on HTC touch dual niki100.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] orb3000:
Wrong section

wrong section!
[JASJAR, XDA Exec, MDA Pro Software Upgrading] yousaf2k:
JAS JAR Blue Boot Screen SPV M5000 Orange Boot Screen Stuck Soution

Dear users,

After trying variuos methods i am able to install and BOOT tomal wm6.4 v10.

The first problem after installing normally which i got was i was stuck at orange boot screen where rom and radio version were being shown.

I tried many different inc reflashing etc.

But the solution which worked for me is.

1. Install the USB drivers for MTTY

2. Disable USB Connection in Active Sync Connection Settings.

3. Run the MTTY v1.42.

4. Select the usb from menu and press ok.

5. enter task 28 55aa press enter

6. You will see some messages.

7. Now exit mtty.

8. Flash the rom.

9. Reset the device by pressing soft key 1 and soft key 2 + reset.

10. press 0 zero.

A black screen will come following the windows screen.

wow WM 6.5 is working...

It took a day to gather all this information from xda dev.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] XDA_LEON:
Stuck in Bootloader

problem solved
[JASJAR, XDA Exec, MDA Pro Software Upgrading] cr2:
And how are you going to boot when the bootloader

is reformatted ? :?
[JASJAR, XDA Exec, MDA Pro Software Upgrading] KT:
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
[JASJAR, XDA Exec, MDA Pro Software Upgrading] KT:
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
[JASJAR, XDA Exec, MDA Pro Software Upgrading] 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.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] 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??
[JASJAR, XDA Exec, MDA Pro Software Upgrading] hdubli:
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
[JASJAR, XDA Exec, MDA Pro Software Upgrading] KT:
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
[JASJAR, XDA Exec, MDA Pro Software Upgrading] buzz_lightyear:
Platform Builder is your debugger.

You have to build at least one platform and then make a connection to it..
[JASJAR, XDA Exec, MDA Pro Software Upgrading] Asukal:
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)
[JASJAR, XDA Exec, MDA Pro Software Upgrading] 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.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] olliesshop:
Could it have been a bad USB Cable that started this?

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.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] Rik Lijkendijk:
UnStuck from bootloadermode

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:
[JASJAR, XDA Exec, MDA Pro Software Upgrading] qtotter:
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.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] qtotter:
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.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] qtotter:
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...
[JASJAR, XDA Exec, MDA Pro Software Upgrading] buzz_lightyear:
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
[JASJAR, XDA Exec, MDA Pro Software Upgrading] qtotter:
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
[JASJAR, XDA Exec, MDA Pro Software Upgrading] KT:
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
[JASJAR, XDA Exec, MDA Pro Software Upgrading] KT:
Re: Could it have been a bad USB Cable that started this?

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
[JASJAR, XDA Exec, MDA Pro Software Upgrading] KT:
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
[JASJAR, XDA Exec, MDA Pro Software Upgrading] 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.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] qtotter:
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)
[JASJAR, XDA Exec, MDA Pro Software Upgrading] 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
[JASJAR, XDA Exec, MDA Pro Software Upgrading] 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
[JASJAR, XDA Exec, MDA Pro Software Upgrading] buzz_lightyear:
i'll build a tool, which will jump you out of the bootloader, tomorrow...

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

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

buzz
[JASJAR, XDA Exec, MDA Pro Software Upgrading] buzz_lightyear:
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
[JASJAR, XDA Exec, MDA Pro Software Upgrading] 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.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] 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
[JASJAR, XDA Exec, MDA Pro Software Upgrading] meer:
This solves only the Problem if stuck in Bootloader Modus, not the Splash screen Problem.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] KT:
MATTER OF FACT

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