FOR ALL THOSE WHO STUCK IN THE BOOT SCREEN OF UNIVERSAL

[shing]

Is there a solution for this problem? i flashed it with different roms (dopod t-mobile qtek) but they all stuck on the splash screen, i also tried the task 28 mtty thing. but nothing works =( i have no warranty on my mda so i cant bring it back. if anyone knows a solution please post. thanks :roll:

[vtnguyen]

I recently bought a new Dopod, already provided with ROM 111 AKU2. Last Friday after a sync with office laptop, before going home, I reset and ...Bang!! my Dopod stuck at the Boot Screen. I spent the whole week end to read this thread and tested everything, as follows:
- first i put Bootloader Mode (Version 2.01 !!!) and set MTTY with 14 0
- I flash with ROM Universal 1.30.68 from Imate (taken from XDA FTP), then hard reset. After a while it worked (IMate splash)
- I sync again with my home computer and introduced all key data (owner, regional settings, time, date etc...) and installed few basic SW applications such as Resco Explorer, Check Notifications...
- Then to be back to Dopod, I downloaded the original Dopod 1.30.111 WWE from DopodAsia, and reflashed via Bootloader and MTTY
- This time, it stucks, and so far I could not get out of this.

I try to reflash with Imate 1.30.68, no success. Same with reflash Dopod AKU2 or older version :-(
I checked Task 28 in MTTY. Everything is fine, the DOC was read and yielded values.

When I tried the method Soft Reset/Light button, and Yes/Yes to erase Storage and Registry, the Dopod stuck with blank white screen.

I plan to send back to service center for repair/replacement



P.S. I also ensured that the battery is sufficiently charged, via AC charger overnight , and via USB in BL (hours long). I also took the battery out of the Dopod for hours...






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

[StallionM5]

Same problem ,I Had an MDA Pro here and Sim Unlocked it and it worked then I upgraded the Flash from German to Newest english Version without Paying attention for my Bootloader version
Then did every thing to make it back from the dead

A friend of mine He is a tech guy who took my mobile and after about 30 min my mobile was alive again

When I asked what on earth did he do he said he Flashed it again with the original Bootloader Which was i think 0.56 then flashed the orginial rom

Then he upgraded the Bootloader later and then the new flash

Fresh as new


GUYS can you please Post an original Bootloader version I mean 0.56 or all old ones ?

We tried the same problem with a Jasjar and worked back with the same proceedure

Te problem is that the Tech was having all those bootloaders on his Flash Memrory Stick which I tried deadly to take and make a copy but he couldnt give it to me I dont know why

Anyway If you can please post original Copies of the boot loaders or if there is someone out there who have the origianl bootloader on his mobile and make us a bootloader and ROM back up it will Work

Regards
[/b]

[vtnguyen]

Update: sent the unit to Service Center. After diagnostic, they replace the Mother Board, sent back. Works very OK since then. Vtnguyen




I recently bought a new Dopod, already provided with ROM 111 AKU2. Last Friday after a sync with office laptop, before going home, I reset and ...Bang!! my Dopod stuck at the Boot Screen. I spent the whole week end to read this thread and tested everything, as follows:
- first i put Bootloader Mode (Version 2.01 !!!) and set MTTY with 14 0
- I flash with ROM Universal 1.30.68 from Imate (taken from XDA FTP), then hard reset. After a while it worked (IMate splash)
- I sync again with my home computer and introduced all key data (owner, regional settings, time, date etc...) and installed few basic SW applications such as Resco Explorer, Check Notifications...
- Then to be back to Dopod, I downloaded the original Dopod 1.30.111 WWE from DopodAsia, and reflashed via Bootloader and MTTY
- This time, it stucks, and so far I could not get out of this.

I try to reflash with Imate 1.30.68, no success. Same with reflash Dopod AKU2 or older version :-(
I checked Task 28 in MTTY. Everything is fine, the DOC was read and yielded values.

When I tried the method Soft Reset/Light button, and Yes/Yes to erase Storage and Registry, the Dopod stuck with blank white screen.

I plan to send back to service center for repair/replacement



P.S. I also ensured that the battery is sufficiently charged, via AC charger overnight , and via USB in BL (hours long). I also took the battery out of the Dopod for hours...






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

[itwasntme187]

Attempted to upgrade my MDA Pro to the latest rom on the website and now all i get is the white T-Mobile boot screen showing me the updated rom and radio versions. it just sits there. I have tried the mtty thing but no luck, and when trying the task 28 it just says failed as some of the other guys have said in this topic.

So im on my way today to the T-mobile store after speaking to the tech dept at cust services who has told me to give in the phone, wait 3-5 working days and they will either send me my fixed MDA Pro or a new one!!

For all you guys that have warranty on your phones......you might want to try sending it back

Il let you guys know what happens when i get it back in a few days.

[smb5823]

Hi Everyone.
I had a similar problem to everyone else and eventually organised a repair under warranty. Got the device back from Germany today with the repair report saying "replace ROM image".
What happens when I switch the darned thing on....yep u guessed it... sticks at splash screen.
I did wonder whether the battery might be at fault, as whilst I sent them the battery with the device, it would seem that they didn't open the envelope with the battery in it. Therefore is it just possible that the battery charge is too low to 'boot' the device fully? But this is NOT the case as I purchased a new battery and charged this with a second device and this didn't work either. So I'm stumped completely. I think it's return to dealer time.

[itwasntme187]

Ok guys so just to let you know what happened......

Well as i had last said i gave in my handset back to T-mobile and after two long weeks without my MDA Pro i called them up and was told that it was in store and ready to collect. The best part about it is that i have now a Brand new MDA Pro as the last one was unfixable and it also has the new rom and radio on it!

So it looks like everything is good!!

If you have a problem with your MDA after flashing it and you are still within your warranty period then take it back and get a new one!! :D

[fallenczar]

hey ppl....
thanks for the advice!!!!!!
my o2 xda exec got stuck in the bootloader screen when i updated its rom....

followed the advice on the forum.....

i want to share my experience here


first as recomended i disabled usb from activesync

then downloaded mtty 1.42

connected the usb and started mtty

chose usb

white screen.....

typed set 14 0...

some gibrish on the screen....

ran the rom update....but it informed me that the rom is not for my device...

typed task 0 in mtty (not sure bout the command but its on page 2 of the forum)

ran the update....nothing same error....

now i saw that my universals screen was blank....

removed the battery....and then restarted my universal....

voila!!!!

it came back to life.....

[mrf]

Hi ppl,

Same issues, i have tried everything contained within these 11 pages, nothing works, if it helps....

O2 XDA Exec
Was running 1.13.82 Boot Log 1.0
Ran sim unlocking tool from Buzz's pages (worked fine)
Ran rom flash upgrade from 02's pages up to 1.30.162 (dead as a dodo)

I have run mtty and tried the task 28 format.....errors.....

As my unit is 2nd user i dont have the facility of taking it back to supplier so im now the proud owner of a brick (had the unit 2 days) ce la vie...I should have took my £200 and gone pissed it up the wall down my local boozer :)

I will watch these pages with anticipation of Buzz performing a small miracle :)

[frz]

hi all,
i'm stukc on the splash screen too...
just an observation, i had the extended rom unlocked when i flashed my exec..
i also realised after i flashed the rom that my battrey wan't fully charged.
i can acces the bootloader & flash the rom again but still stuck on the bootsplash screen...
frz

[frz]

after running mtty 1.42
this is what i get on the screen of pc
set 14 0
HTCST ÚÈÒHTCEUSB>
tried updating the rom by ticking usb on active sync
got error 101
HTCST ÚÈÒHTCEUSB>task 28
DOCInfoTableinitHW+
Binary0 Size: 0x100000
FAT0 Size: 0x4000000
FAT1 Size: 0xA00000
FAT2 Size: 0x2840000
All Size: 0x7340000
FAT0_ADDR=0x100000,FAT1_ADDR=0x4100000,FAT2_ADDR=0 x4B00000
USB>tried updating the rom by ticking usb on active sync
got error 101
USB>task 0

after soft reset
still stuck
tried hard reset
still stuck
frz

[frz]

yes i've just managed to sort it out..
i think the O2 rom on the ftp is currupted
i downloaded the t-mobile rom & charged the battrey on someone elses exec...
made sure it is 100% charged
then i used manupgrade.exe & updated only the rom
no extended rom
no radia
after that reset
& thats it
it started working...
all the best

[hendrickwu]

dear friend
I see a lot of messages about solving the stuck screen at o2. but none of them can help me to solve. could you write me to hendrickwu@hotmail.com . how to solve it

Thank you in advance


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

[zedino]

My friend s Uni locked in bootloader mode : "Serial v1.00"

and

"USB device not recognized" on windows XP.
ActiveSync was working perfectly with my Uni

Then of course no upgrade or flash is possible.
trying to flash again give me error 150 or 101. constantly

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

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

USB port is good for my universal
friends Uni has BL v. 1.00
he upgraded yesterday with ivans AKU3.2 Beta8
Serial to USB sign is not changing while USB is pluged, just "Serial" stays
could be this total dead of his Uni???


thanx for any solution

[buzz_lightyear]

My friend s Uni locked in bootloader mode : "Serial v1.00"

and

"USB device not recognized" on windows XP.
ActiveSync was working perfectly with my Uni

Then of course no upgrade or flash is possible.
trying to flash again give me error 150 or 101. constantly

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

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

USB port is good for my universal
friends Uni has BL v. 1.00
he upgraded yesterday with ivans AKU3.2 Beta8
Serial to USB sign is not changing while USB is pluged, just "Serial" stays
could be this total dead of his Uni???


thanx for any solution
hi,
first you have to check, what's wrong with the PC, where you trying to flash.
It is a problem with drivers on your desktop PC.

buzz

[zedino]

there is nothing wrong with PC and its drivers, on the same USB port my Uni is recognized without error, the problem is that sign "serial" on bootloader screen do not change to "USB" when my friend's Uni is connected to PC

[beginner]

there is nothing wrong with PC and its drivers, on the same USB port my Uni is recognized without error, the problem is that sign "serial" on bootloader screen do not change to "USB" when my friend's Uni is connected to PC

I have some trouble. And many times, when I connect the universal, the computer stop to work...

[Cheshirrrrre]

When i've tryed to flash it with JASJAR_ME_13082_171_10900_wwe_ship, i got a message that flasher encountered some problems and i must to reset device and try to flash once more. And i get this message everytime i try to flash device.

But. When i renamed radio-rom, i've flashed nk and ms without problems. But all i've got - black'n'white splash and black'n'white welcome screen and a LCD, that doesn't interact with stilus.

Device doesn't charge and restart each time i take AC-adapter's cable out of it.

When it restarts - i see

"No GSM

D 1.30.82 WWE"

UPD:

now uni works fine - except "No GSM". Start - Settings - Device info - radio rom line is empty. Imei line is empty. When device is not connected to AC-adapter - message abbout insufficient power appears. Then i connect AC-adapter and 255% of remaining power appears! %)

task 28:

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>

RUU.log after trying to flash radio:

09:55:16:870 [msg] : Version : [2.11].
09:55:16:870 [msg] : Config Info : [857873],[1],[0],[0],[1],[0],[0],[1].
09:55:17:300 [msg] : MSystemFile Not Exist !
09:55:17:300 [msg] : CEFile Not Exist !
09:55:20:495 [msg] : Current Not in CE Mode or in CE Mode but ActiveSync Not Connected.
09:55:24:821 [msg] : Disconnect ActiveSync .... [2]
09:55:24:841 [msg] : Start Get Connect Port.
09:55:25:082 [msg] : Current in BL Mode. Open Port : [\\.\WCEUSBSH001] OK.
09:55:46:863 [msg] : Get Device Backup ID.
09:55:46:863 [msg] : Device BL VER : [1.00 ] [].
09:55:46:863 [msg] : Device ID Is Incompatible.
09:55:46:863 [msg] : Update Image. CE : [0], MSystem : [0], Radio : [1]
09:55:50:668 [msg] : Check Ac in BL mode. AC : [1]
09:55:52:171 [msg] : IsBL. BL : [1]
09:55:52:271 [msg] : =============================================
09:55:52:271 [msg] : START UpdateRadio !
09:56:00:012 [msg] : Check Radio Level 0 [704].
09:56:01:183 [msg] : RUpgrade 0 : 0 Start.
09:59:42:452 [err] : RWipe Data Error.
09:59:42:792 [err] : BL UpdateRadio Error.
09:59:42:792 [msg] : START UnInitialization !
09:59:42:792 [msg] : END UnInitialization !
09:59:42:822 [msg] : IsBL. BL : [1]

[buzz_lightyear]

Device ID Is Incompatible

you should either use "noid" flashing utility or make sure, your radio and OS images are both having same ID.

buzz

[Cheshirrrrre]

Device ID Is Incompatible

you should either use "noid" flashing utility or make sure, your radio and OS images are both having same ID.

buzz

they're same. I can flash nk and ms easily, but when i try to flash all 3 files - error appears.

All radio roms, even 0.00.00, that used for unlocking purposes - can't be flashed. Everytime i try - i get an error message.

[maester_squall]

What i did was hard reset the phone and i was able to get it working again. But i was able to duplicate getting stuck at the boot screen by installing programs i had previously used on my magician. Everytime i installed one of those apps it would hang at the boot screen. Most notably, my old version of pocket plus would do it the most. I dont know anything technical, just giving out some of my experiences. As of now, i havent been stuck in the boot screen.

[Rockafello]

Yae!! just got phoned by T-mobile service. they have repaired my mda pro under waranty! Two weeks ago i tried to update to O2 aku 3.2 Beta 8 firmware, but get stucked in bootscreen. i have "downgraded" my device to t-mobile rom again and they have repaired it at T-mobile service.

this is for dutch people.

Dus als task 28 een failed message geeft, gewoon garantiebewijs opzoeken en opsturen. na 2 weken heb je weer een werkende telefoon terug!

[jacquiegardner]

Where can I find the mtty utility?

[buddy28s]

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


I worked the problem out check this site out
http://wiki.xda-developers.com/index.php?pagename=Instructions%20for%20those%20st uck%20on%20Boot%20Screen

[barc]

thanks for this thread. my very first time upgrading of ROM using files from here. For a minute, I thought I just bricked my Universal

[whippet2k]

mtty can be found at:

http://forum.xda-developers.com/download.php?id=9864

[whippet2k]

Where can I find the mtty utility?

The link is http://forum.xda-developers.com/download.php?id=9864

Strange how ppl can be so self absorbed as not to reply

[orangdayak]

No more post?? Has anyone managed to get out of the splash screen? Pls guide me.. Buzz.. anyone??

[gopi159]

Thanks for those who created mtty 1.42 file and the steps.....after one full day my xda can alive from bootlooder stuck..

it all happnd when i upgraded my rom to the new one -AKU3.2 Rom for Universal - Lt.Cmdr.Ivan (am not blaming this rom,nothing wrong with the rom)....

what i did..

1. charged the phone whole night using charger,although no battery charging light indication was on.

2. with the mtty 1.42 software (follow the steps given under - those who got stuck in bootloader) tried entering the value set 14 0.

3. Intially didnt work, so went for set 14 0 & task 0

4. now, serial v 1.00 gone and the screen was blank.

5. In panic removed the battery immediately. then put it back and pushed the power button on...

6. happy when i saw bright white screen then started to boot normally...

Thanks for all who created those file and steps..
Guys

[gopi159]

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

Thanks Buzz...the steps u mentioned did worked for me instantly...
seems it will work only for universal

[orangdayak]

Hi,
I was just wondering whether any of u have solved the splash screen problem. Mine having the same problem yesterday and i couldnt get it started anymore.

If any of u have fixed it, pls tell me how.

~Cry!

[Wiz]

Hi,
I was just wondering whether any of u have solved the splash screen problem. Mine having the same problem yesterday and i couldnt get it started anymore.

If any of u have fixed it, pls tell me how.

~Cry!

Sorry mate, The format failed message indicates that you have a corrupt internal flash disk. Only option is return to the vendor/manufacturer and have it repaired under warranty

[Words_vs_Pain]

Device doesn't:

1 - Power UP
2 - Enter to OS
3 - Show Splash Screen

I tried:

1 - Reflashing it
2 - Use mtty utility
3 - Task 28


I can enter in bootloader but i'm not stucked there. When I press the button to power up the device... nothing happens!

Help me please




LOGS:
01:37:37:959 [msg] : Version : [2.11].
01:37:37:959 [msg] : Config Info : [857873],[1],[0],[0],[1],[0],[0],[1].
01:37:43:193 [msg] : Current Not in CE Mode or in CE Mode but ActiveSync Not Connected.
01:37:47:724 [msg] : Disconnect ActiveSync .... [2]
01:37:47:724 [msg] : Start Get Connect Port.
01:37:47:865 [msg] : Current in BL Mode. Open Port : [\\.\WCEUSBSH001] OK.
01:37:53:099 [msg] : Device BL VER : [1.01 ] [].
01:37:53:099 [msg] : Update Image. CE : [4], MSystem : [2], Radio : [1]
01:37:56:099 [msg] : Check Ac in BL mode. AC : [1]
01:37:57:599 [msg] : IsBL. BL : [1]
01:37:57:599 [msg] : =============================================
01:37:57:599 [msg] : START UpdateRadio !
01:54:42:655 [msg] : END UpdateExtended !
01:54:47:655 [msg] : =============================================
01:54:47:655 [msg] : START UpdateCE !
01:58:16:435 [msg] : END UpdateCE !
01:58:19:170 [msg] : START UnInitialization !
01:58:19:170 [msg] : END UnInitialization !



************

MTTY

USB>task 28
DOCInfoTableinitHW+
Binary0 Size: 0x100000
FAT0 Size: 0x4000000
FAT1 Size: 0xA00000
FAT2 Size: 0x2C40000
All Size: 0x7740000
FAT0_ADDR=0x100000,FAT1_ADDR=0x4100000,FAT2_ADDR=0 x4B00000

[hungdu]

For me, i hadnt notice this thread until today. 2 days ago, while receiving call there was call waiting. I finished the current to answer the 2nd but screen and phone buttons stuck! I reset my EXEC, it's stuck in welcome screen and black then. Thinking of low battery I plugged to charge. Soft reset and EXEC came alive. My battery level said >56%!!!!????

It's seem very strange to me of what i faced and read thru this thread!

[xtaurus]

me too, o2 exec has stopped at splask screen.I have tried lots of roms,no one can work.
my BL:v 1.00

[hungdu]

Today I meet the problem again and make a test with it. My battery level is <60%, EXEC hang and stuck everytime i make phone call. I plug the AC charge into EXEC and reset. It comes alive! I unplug and use again (for 6 times), it happended the same way.

To my EXEC: the error occurred when battery level is lower than some number (my test is 60%). Sound very strange to me!!! Is it the bug?

[orangdayak]

Hi guys,
There is a tip from Dubli for those who stuck on splash screen:
1. Get mtty
2. Connect to USB, press enter
3. Type task 32, enter
4. Type 28, enter
5. Flash CE Rom only
6. Hard Reset

Make sure to type task 32 first before task 28 coz task 28 alone wont work.
Pls try this and tell me the outcome. I cant try this coz i just sent my uni to UK just now.

[orangdayak]

Has anyone tried the above method? Pls post your results.

[liay]

Hi guys,
There is a tip from Dubli for those who stuck on splash screen:
1. Get mtty
2. Connect to USB, press enter
3. Type task 32, enter
4. Type 28, enter
5. Flash CE Rom only
6. Hard Reset

Make sure to type task 32 first before task 28 coz task 28 alone wont work.
Pls try this and tell me the outcome. I cant try this coz i just sent my uni to UK just now.

FYI failure again!

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

Should I must get a "Level = 0" after task 32 to fix it? but HOW?

[orangdayak]

FYI failure again!

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

Should I must get a "Level = 0" after task 32 to fix it? but HOW?

If thats the case, should should send it back to the manufacturer for the warranty. Im afraid there is no other solution for this, at least not now.
Hopping for the geniuses here can sort this thing.. sigh..

[agisofttm]

And a report ANOTHER CASE of failing format with task 28 :mad: going to get new Universal, because here in Bulgaria our warnities are from 6 months to 1 year :mad:

Well after I get new one I can test with my old one - with resoldering DOC and change with new one.

[corleno]

my universal just got stuck in this screen
press 0 to clear memory

so i cleared memory
and universal does not start up

so i went back to bootloader
disabled USB connection (active sync)
I start mitty
after that
I do not have "WESUSB... " port ???
I only have Com1 and Com2 :(

So i press Com1
I get white screen

I dont get USB>

so i directly enter set 14 0

it says ready

but nothing happens

someone plz help

[moh1978sen]

i have upgraded my rom accidentaly with incorect rom "hermes rom" it got 37 percent completed then showed comunication error i then flashed jasjar _bl1.01_ruu_v1.2.exe which was succesful and then tried to re flash my Right working rom "helmi universal" which was successful i then did a hard reset and now nothing workes completely nothing "baterry in battery out usb in usb out ....the screen shows nothing no serial usb or anything also xp doesn't recognise usb. I just got red light and when i press soft rest button will flash. please help i would be very greatful
if you can not help me I have to report police so i killed my baby!!!!!!

usb monitor error code ..000001: Bulk or Interrupt Transfer (UP), 28.12.2006 03:36:03.1562500 +0.3750000
Pipe Handle: 0x854e776c (Endpoint Address: 0x81)
Get 0x4 bytes from the device
000002: Bulk or Interrupt Transfer (UP), 28.12.2006 03:36:03.1718750 +0.0156250
Pipe Handle: 0x854e776c (Endpoint Address: 0x81
many thanks:mad: :mad: :mad: :mad:

[henk-jan]

upgrading for the 4e time, now to Helmi's 3.5 caused a problem (stuck in the boot mode) before mentioned by many others. Thanks to this great forum I could solve it easily. I like this forum so much :-) :-) :-)

[DuLanTus]

My ROM is O2 v1.13.139 (Launch ROM)
The only problem is ActiveSync didn't detect my Uni (possible USB port defect?)
So flashing directly from PC is impossible.

Then i try BootLoader mode.
My Uni is using BootLoader v1.00 and for this time can detect USB ("Serial" change into "USB" when connecting to PC)
I've try both mtty (1.16 & 1.42) but no use (only COM port are visible in mtty's)
Uni_Exit BootLoader also no use (can't open USB port)
MaUpgradeUt_noID also fail (not compatible device)

Of course i have removed both SD and SIM card from my Uni.

So now i have two thing to do, smack my Uni really hard and kick ém out my window OR there is a way to repair my Uni?

Everybody, please help me solve my precious Uni........ Thank you so much for helping me.

[corleno]

My ROM is O2 v1.13.139 (Launch ROM)
The only problem is ActiveSync didn't detect my Uni (possible USB port defect?)
So flashing directly from PC is impossible.

Then i try BootLoader mode.
My Uni is using BootLoader v1.00 and for this time can detect USB ("Serial" change into "USB" when connecting to PC)
I've try both mtty (1.16 & 1.42) but no use (only COM port are visible in mtty's)
Uni_Exit BootLoader also no use (can't open USB port)
MaUpgradeUt_noID also fail (not compatible device)

Of course i have removed both SD and SIM card from my Uni.

So now i have two thing to do, smack my Uni really hard and kick ém out my window OR there is a way to repair my Uni?

Everybody, please help me solve my precious Uni........ Thank you so much for helping me.

once you are into boot loader(light+power+reset)
connect the PPC (using another usb port)
ur device will get recognized

after which all you have to do is,run an official upgrade from O2 website

this worked for me

[DuLanTus]

once you are into boot loader(light+power+reset)
connect the PPC (using another usb port)
ur device will get recognized

after which all you have to do is,run an official upgrade from O2 website

this worked for me

Thank you corleno for helping me, but using another USB port is the same. Even all my USB port cannot recognise my ppc. They all say "Unknown Device". And if i force upgrading official rom from O2, all i've got is error.

Is it possible if my PPC USB port defects? If yes, then why in BootLoader mode my PPC USB port can recognise it?

Please, anyone could help me normalizing my Uni back?????

[corleno]

Thank you corleno for helping me, but using another USB port is the same. Even all my USB port cannot recognise my ppc. They all say "Unknown Device". And if i force upgrading official rom from O2, all i've got is error.

Is it possible if my PPC USB port defects? If yes, then why in BootLoader mode my PPC USB port can recognise it?

Please, anyone could help me normalizing my Uni back?????

this is what happened 2 me
1. my system was plugged in (device unrecognizable)
2.I changed the port (after restarting comp once and disabling USB connections in active sync)
3.It said installing drivers Pocket PC hub (I have boot loader 1)

after this step its quite obvious
hope it helps

[DuLanTus]

this is what happened 2 me
1. my system was plugged in (device unrecognizable)
2.I changed the port (after restarting comp once and disabling USB connections in active sync)
3.It said installing drivers Pocket PC hub (I have boot loader 1)

after this step its quite obvious
hope it helps

which activesync version do u use, corleno? I used activesync 4.1 and 4.5 beta. It's all same, "Unknown device" is rise again.

Now the problem is, how to fix the "Unknown device" condition? Do i need a ppc usb driver? if yes, then where i can find it?

Thank you corleno for replying me..

[pbocsak]

I'm stuck at the Booloader screen. I tried MaUpgradeUt.exe, nothing happens (error 101). I also tried the MTTY.exe thing but, just like for some of you guys, my desktop doesn't recognise my Uni and so it doesn't list the "WEUSB" (only COM1 and COM2)
What should I do?!? plz help me! I need this device back in shape ASAP!
thkx guys, you're doing a great job helping eachother out! :)

[pbocsak]

All right! I'm all set now!!!! I finally got this damn 1.30 ROM to work!!!
This is my story...
My JasJar turned off @ 85% of battery remaining, sometimes @ 94% (heavy use : MP3 + camera starting)
I thought "it maybe has something to do with the firmware... let's see if there's a new one out there..." so I DL the firmware... first it didn't work... 2nd try was unsucessful... Then I tryed with the MaUpgradeUt_noID.exe and it worked. As I rebooted the device (soft reset + [-] + [-]), I got into the BootLoader mode. I tried to update it with MaUpgradeUt_noID.exe, MaUpgradeUt.exe and even the original setup but sucessless... I noticed that whenever I wanted to boot, a red light blinked once (either if I was going to BootLoader mode, the "restore factory defaults" mode or juste trying to boot "normaly"). Sometimes the MaUpgradeUt.exe could connect to my device, but was saying sth like:
updating from
ROM version :
radio version :
xxxx version:

To

ROM version :
radio version:
xxxx version:
yes! nothing was written at all! Then - of course - the setup failed

I thought hmm... maybe there isn't enough power left in it ( I thought the battery was broken or sth and order a new one for arround USD 30.- on expansis, I think). So I plugged it into the wall socket for + 16hrs. Still no turn on, and still a single red blink of the right LED (right when you open it normaly, with the keyboard facing you).
As I came home from work, I surfed arround the forum for a while, getting tips from here and there... I noticed sth strange, though... when I went to BootLoader Mode, it was written "serial" if it wasn't plugged in, or "USB" if it was plugged in, but as soon as I changed it's status (plug it in or out), the status didn't change on the screen... I even tried to connect with the "MTTY" utility, but nothing worked... I don't know, how, or why I just thought... "hmm.. what if I remove the SD card (SIM was already removed and inserted into an "emergy-use" phone). I removed it, rebooted into BootLoader and plugged it into the computer... Now, the status changed from "serial" to "USB" on the screen, but the computer wouldn't recognise it ("uknown device, please update drivers blah blah...."). I tried switching USB ports... same result... damn... I just though "Oh hell! Let's go though all the 3x pages of this topic"... as I read morphosin's post

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...

I thought "hmmm why not switch cables?" even though this same cable was the one I used for ages either for my JasJar or my Digital Camera... So I picked a random (I have tons of them) USB A<-> mini-USB A cable, plugged it into the "new" USB socket and guesse what? Windows told me "PocketPC Smarte phone detected".... "installing those DAMN drivers you wanted me to install for so long"!!!! It was a dream come true! Then I did the "set 14 0" command through "MTTY" (it DID recognise USB this time!!). Then ran the "normal" set up of "JASJAR_WWE_13076_164_10900_wwe_ship.exe" I got from the FTP, disabled my screensaver, went to eat somthing and when I got back, my computer was telling me to reset my device (soft reset + [-] + [-]) what I did, and then, my JasJar told me
"i-mate JasJar!
Would you please calibrate my screen?"

Right now, I'm uploading it to I-can't-remember-who's JASJAR_WWE_19094_19503_11100_AKU_3_2_ship!!! Can't wait for it to be done!

I thank all you guys for any kind of tips you give during these procedures! In a word "you're the greatest!!!" (ok, make that 4)

If any one need help, MSN-me :
peter [dot] bocsak [ at ] bocsakcomputers [dot] com
(yes; this IS my MSN address!)

edit:
I don't think you need a fully charged battery for this opperation, since my JasJar was down @ arround 86% when I started and I had it @ 100% when I first went back to Windows Mobile... Even though I left it in the charger for +16hrs, I left it upluged at times, with BootLoader running...

[agisofttm]

Actually you fix YOUR problem - not that problem linked with failed TASK 28 command :-)

cheers

[crooner999]

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

I went into the KITL thingy and said yes as i didnt' know what it was...now i'm stuck in the BL mode...could you help me get out of it plz....

[crooner999]

I went into the KITL thingy and said yes as i didnt' know what it was...now i'm stuck in the BL mode...could you help me get out of it plz....

Got it Resurrected
Quote:
Originally Posted by crooner999
I know there's a lot of forums for this topic! i have tried following the procedure given at most of the forums but to no help. The upgrades just don't happen as the connection error 101 keeps popping up after executing the rom upgrade exe. I don't know how to use the mtty.exe and host.exe to fix the problem. I'm using vista ultimate on my desktop and wm6 rom (jwright 2.02.00) on the jasjar. before i got stuck in the bootloader mode, i remember getting the KITL option on the blue imate boot screen and enabling it. I'm stuck in the bootloader since then. I appreciate this forum and the people here...need your help. Thanks in advance.
Hi people...here's an update on how I came out of my crisis..(for a moment i thought there's some defect caused on the mainboard!) anyways, i went to a lot of threads pertaining to the 'stuck in bootloader topic' and mixed and matched the solutions. here's what i did.

unsuccessful efforts :
used the combination keys with reset to come out of the bootloader in vain.
tried hard-reseting the device in vain.
tried weird key combos in vain.
tried to upgrade rom (on vista ultimate) got connection error 101.
tried to reflash radio rom but got the error even though device was listed in the device manager
------------------------------------------------------------------------
Successful Effort:
Just when i thought that i'd have to bring my baby to the service center...i said a prayer to Jesus asking Him to fix it for me. Really got desperate and prayed...I got a check from Him to try using another computer with XP which i did but the Rom wouldn't flash. Still stuck on the bootscreen, I tried the radio upgrade on the computer running XP SP2 with the maupgrade noid stuff and there it was, upgrading the radio rom! I thanked the Lord for helping me for XDA Developers forum and I'm a happy Jasjar user once again. I hope you will get some help from my testimonial which is why I'm posting this!

[crooner999]

Got it Resurrected
Quote:
Originally Posted by crooner999
I know there's a lot of forums for this topic! i have tried following the procedure given at most of the forums but to no help. The upgrades just don't happen as the connection error 101 keeps popping up after executing the rom upgrade exe. I don't know how to use the mtty.exe and host.exe to fix the problem. I'm using vista ultimate on my desktop and wm6 rom (jwright 2.02.00) on the jasjar. before i got stuck in the bootloader mode, i remember getting the KITL option on the blue imate boot screen and enabling it. I'm stuck in the bootloader since then. I appreciate this forum and the people here...need your help. Thanks in advance.
Hi people...here's an update on how I came out of my crisis..(for a moment i thought there's some defect caused on the mainboard!) anyways, i went to a lot of threads pertaining to the 'stuck in bootloader topic' and mixed and matched the solutions. here's what i did.

unsuccessful efforts :
used the combination keys with reset to come out of the bootloader in vain.
tried hard-reseting the device in vain.
tried weird key combos in vain.
tried to upgrade rom (on vista ultimate) got connection error 101.
tried to reflash radio rom but got the error even though device was listed in the device manager
------------------------------------------------------------------------
Successful Effort:
Just when i thought that i'd have to bring my baby to the service center...i said a prayer to Jesus asking Him to fix it for me. Really got desperate and prayed...I got a check from Him to try using another computer with XP which i did but the Rom wouldn't flash. Still stuck on the bootscreen, I tried the radio upgrade on the computer running XP SP2 with the maupgrade noid stuff and there it was, upgrading the radio rom! I thanked the Lord for helping me for XDA Developers forum and I'm a happy Jasjar user once again. I hope you will get some help from my testimonial which is why I'm posting this!


Hey ppl...I'm sad to inform you that my JASJAR froze while trying to upgrade to wm6. everything seemed to be working fine except when i disconnected from the data cable after the upgrade was 100%, it never came on! I don't know what the problem is...it's stuck again. wouldn't even show me the bootloader screen and when i attach it to any computer, it shows the popup message about 'usb device not recognized'.
Has anyone of you faced a similar problem? what could be the problem? How could it be fixed? please help me...thanks in advance.

[SpiriTwin]

Go to
http://forum.xda-developers.com/showpost.php?p=1255206&postcount=52


and please there's many threads about the same issue, i hope we merge it to make it easy for all.

best regards,

[syed_mail]

my uni has stuck on blank screen not going further and i cant enter bootloader as my light button key is not working from long back
is there any other way to fix it

it would be a great help

[syed_mail]

Can any one say me is it necessary that universal should be bootloader mode to get detected by pc
When ever I connect my universal to pc it say unrecognized device
Even mtty 1.14 doesn’t show USB it only has options of com1 to com9 (I have uninstalled Active Sync) but still no use

Anyone’s help would be a great help

[Bat-Dan]

I had exactly the same problem after upgrading my SFR v1640 to qTek firmware. I solved the problem by simply upgrading the bootloader too.

[chrisky]

Ok, i found this solution from google and its a china website (http://bbs.pdafans.com/thread-332549-1-5.html). And it actually reference back to the xda-developers wiki
http://wiki.xda-developers.com/index.php?pagename=Universal_Technical

THIS WORKS ON when you run task 28 in MTTY and return the DOC_format failed result


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


NOW RUN THIS MAGIC COMMAND
task 28 55aa [MORE INFO IN THE WIKI (http://wiki.xda-developers.com/index.php?pagename=Universal_Technical)]
This commmand suppose to "Restores DOC to its original layout"

AFTER YOU RAN THE COMMAND, YOU WILL SEE "WAIT" and wait until you see the command line again

NOW if you run task 28 again,

------------------------------------
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>

You can INSTALL YOUR ROM AGAIN and it should work, at least it work for me

[fishboy420]

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


I used the Enterbootloader.exe and my deviuce is dead, no bootloader screen or nothing.

I tried this but I kept getting an error saying that I needed to disable USB (which I have already Done, and also it said or try to make sure usb is plugged in correctly) All of this was done correctly.
But nothing, -please help me if you can

fishboy420

[Lesane]

I've got the same problem as many other ppl here.

When putting my Universal in boot loader, it is not recognized on my PC. Not in Vista and not in XP. It keeps saying device not recognized. (unknown device).
I've plugged it many times in different USB ports and even gave my device a hard reset. I tried an other PC, doesn't work. Same error.

The boot loader screen keeps saying Serial (I've got v1.01).
Upgrading the boot loader doesn't work and upgrading my device is not working either.

I hope SOMEONE can give a solution, so i can go on with my life ;).

I've currently got a WM6 ROM .

[bullietje]

hello,

im a happy user of an i-mate jasjar i have the uni 1week or something, now i managed to update the i-mate jasjar to the latest release: JASJAR_WWE_13076_164_10900_wwe_ship, now i want to know what files i need to go WM6 or how to get JASJAR_WWE_19094_19503_11100_AKU_3_2_ship OR better? And if its possible for setting the links or download page.
And how that i have to do it

Sorry for my english but im from belgium.

With the best regards Bullietje

my I-Mate settings are:
ROM version: 1.30.76 WWE
ROM date: 02/20/06
RADIO version: 1.09.00
ExtROM version: 130.164 WWE

[vjj]

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

that works on Universal only (afaik).

buzz

After a lot of ROM flashes, I'm for the first time stucked in bootloader's USB screen that can't be solved by repeated flashing.
RomUpgradeUt, UNI_ExitBootloader and mtty1.42, none of them can see the USB port, despite the fact the "Serial" changes to "USB" after the cabel is connected.
Windows Hardware management shows "Microsoft USB Sync" device (working O.K.)
USB port in ActiveSync is disabled.
HELP, please.

[cktlcmd]

After a lot of ROM flashes, I'm for the first time stucked in bootloader's USB screen that can't be solved by repeated flashing.
RomUpgradeUt, UNI_ExitBootloader and mtty1.42, none of them can see the USB port, despite the fact the "Serial" changes to "USB" after the cabel is connected.
Windows Hardware management shows "Microsoft USB Sync" device (working O.K.)
USB port in ActiveSync is disabled.
HELP, please.

Are you VJ's little brother? Just kidding.

I believe you have to kill these 3 files first: wcescomm, wcesmgr, and rapimgr .exe files.

---

[vjj]

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.

Yes, I really do support your suspicion. I've tracked down my problems with downloader to the USB cabel (first event) and JasJar's USB connector, too.

[vjj]

I believe you have to kill these 3 files first: wcescomm, wcesmgr, and rapimgr .exe files.

---

Unfortunately, I've tried your suggestion and it didn't help.
Nevertheless, thanks.

I've tried two USB cabels
- the first case: PDA bootloader screen shows Serial, on PC device is not recognized
- the second case: PDA bootloader screen shows USB, on PC device is for a moment recognized as PocketPC, immediately changed to Microsoft USB Sync

RUU.log is the same in both cases
03:01:12:630 [msg] : Version : [2.11].
03:01:12:778 [msg] : Config Info : [857873],[1],[0],[0],[1],[0],[0],[1].
03:01:17:975 [msg] : Current Not in CE Mode or in CE Mode but ActiveSync Not Connected.
03:01:22:035 [msg] : Disconnect ActiveSync .... [0]
03:01:22:045 [msg] : Start Get Connect Port.
03:01:22:046 [msg] : Cann't Find Any USB Port.
03:01:22:054 [msg] : Open USB and COM Port Error. [2]
03:01:36:100 [msg] : Disconnect ActiveSync .... [0]
03:01:36:120 [msg] : Start Get Connect Port.
03:01:36:129 [msg] : Cann't Find Any USB Port.
03:01:36:141 [msg] : Open USB and COM Port Error. [2]
03:01:50:193 [msg] : Disconnect ActiveSync .... [0]
03:01:50:194 [msg] : Start Get Connect Port.
03:01:50:195 [msg] : Cann't Find Any USB Port.
03:01:50:197 [msg] : Open USB and COM Port Error. [2]
03:02:04:268 [msg] : Disconnect ActiveSync .... [0]
03:02:04:282 [msg] : Start Get Connect Port.
03:02:04:291 [msg] : Cann't Find Any USB Port.
03:02:04:292 [msg] : Open USB and COM Port Error. [2]
03:02:18:320 [msg] : Disconnect ActiveSync .... [0]
03:02:18:321 [msg] : Start Get Connect Port.
03:02:18:323 [msg] : Cann't Find Any USB Port.
03:02:18:324 [msg] : Open USB and COM Port Error. [2]
03:02:32:372 [msg] : Disconnect ActiveSync .... [0]
03:02:32:373 [msg] : Start Get Connect Port.
03:02:32:375 [msg] : Cann't Find Any COM Port
03:02:32:376 [msg] : Open USB and COM Port Error. [2]
03:02:46:402 [msg] : Disconnect ActiveSync .... [0]
03:02:46:420 [msg] : Start Get Connect Port.
03:02:46:430 [msg] : Cann't Find Any COM Port
03:02:46:432 [msg] : Open USB and COM Port Error. [2]
03:02:46:433 [msg] : Update Image. CE : [4], MSystem : [2], Radio : [1]

[sofene]

My unlocked O2 XDA is stuck on the splash screen. I had synced with my office pc successfully. When I got home and turned on the device, the screen did not come on although the green radio light was blinking. A soft reset did not work so I finally did a hard reset and got stuck on the splash screen. I have re-flashed with different roms including complete and partial re-flashing. The result is always the same. The flashing completes successfully but I'm still stuck at the splash screen each time. I have tried the set 14 0 command and reflashed many times with the same result. Here is the result of task 28:

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>

Here is the RUU log:

20:05:29:703 [msg] : Version : [2.11].

20:05:29:718 [msg] : Config Info : [857873],[1],[0],[0],[1],[0],[0],[1].

20:05:29:718 [msg] : RadioFile Not Exist !

20:05:29:718 [msg] : MSystemFile Not Exist !

20:05:33:562 [msg] : Current Not in CE Mode or in CE Mode but ActiveSync Not Connected.

20:05:37:687 [msg] : Disconnect ActiveSync .... [2]

20:05:37:687 [msg] : Start Get Connect Port.

20:05:37:828 [msg] : Current in BL Mode. Open Port : [\\.\WCEUSBSH001] OK.

20:05:38:812 [msg] : Device BL VER : [1.01 ] [].

20:05:38:812 [err] : Device CID Error.

20:05:38:812 [msg] : Update Image. CE : [4], MSystem : [0], Radio : [0]

20:05:44:937 [msg] : Check Ac in BL mode. AC : [1]
20:05:44:937 [msg] : IsBL. BL : [1]

20:05:46:953 [msg] : =============================================

20:05:46:953 [msg] : START UpdateCE !

20:05:48:078 [msg] : Upgrade 2 : 0 Start.

20:05:58:562 [msg] : Upgrade 2 : 0 End.

20:05:58:562 [msg] : Upgrade 2 : 1 Start.

20:06:08:968 [msg] : Upgrade 2 : 1 End.

20:06:08:968 [msg] : Upgrade 2 : 2 Start.

20:06:19:359 [msg] : Upgrade 2 : 2 End.

20:06:19:359 [msg] : Upgrade 2 : 3 Start.

20:06:29:765 [msg] : Upgrade 2 : 3 End.

20:06:29:765 [msg] : Upgrade 2 : 4 Start.

20:06:40:156 [msg] : Upgrade 2 : 4 End.

20:06:40:156 [msg] : Upgrade 2 : 5 Start.

20:06:50:546 [msg] : Upgrade 2 : 5 End.

20:06:50:546 [msg] : Upgrade 2 : 6 Start.

20:07:00:937 [msg] : Upgrade 2 : 6 End.

20:07:00:937 [msg] : Upgrade 2 : 7 Start.

20:07:11:312 [msg] : Upgrade 2 : 7 End.

20:07:11:312 [msg] : Upgrade 2 : 8 Start.

20:07:21:687 [msg] : Upgrade 2 : 8 End.

20:07:21:687 [msg] : Upgrade 2 : 9 Start.

20:07:32:093 [msg] : Upgrade 2 : 9 End.

20:07:32:093 [msg] : Upgrade 2 : 10 Start.

20:07:42:500 [msg] : Upgrade 2 : 10 End.

20:07:42:500 [msg] : Upgrade 2 : 11 Start.

20:07:52:921 [msg] : Upgrade 2 : 11 End.

20:07:52:921 [msg] : Upgrade 2 : 12 Start.

20:08:03:312 [msg] : Upgrade 2 : 12 End.

20:08:03:312 [msg] : Upgrade 2 : 13 Start.

20:08:13:718 [msg] : Upgrade 2 : 13 End.

20:08:13:718 [msg] : Upgrade 2 : 14 Start.

20:08:24:109 [msg] : Upgrade 2 : 14 End.

20:08:24:109 [msg] : Upgrade 3 : 15 Start.

20:08:32:140 [msg] : Upgrade 3 : 15 End.

20:09:04:296 [msg] : END UpdateCE !

20:09:06:296 [msg] : START FormatExtended !

20:09:08:578 [msg] : END FormatExtended !

20:09:08:578 [msg] : START BackCEMode !

20:09:09:468 [msg] : END BackCEMode !

20:09:09:468 [msg] : START UnInitialization !

20:09:09:468 [msg] : END UnInitialization !


Any ideas anyone on what I should do? Thanks in advance.

[gaguzman]

For folks stuck at the splash screen, and can't seem to get out, you might check the Wizard forum for stuck at splash screen, http://forum.xda-developers.com/showthread.php?t=276963 It does work for the Wizard, and if "you have nothing else to try", it might work. Hopefully some of the gurus can look at it and see if it might help.

Tony G.
Tmob. MDA, Qtek 9100 ROM,radio etc. are early releases, no hacks.

[ronaldphl]

Ok, i found this solution from google and its a china website (http://bbs.pdafans.com/thread-332549-1-5.html). And it actually reference back to the xda-developers wiki
http://wiki.xda-developers.com/index.php?pagename=Universal_Technical

THIS WORKS ON when you run task 28 in MTTY and return the DOC_format failed result


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


NOW RUN THIS MAGIC COMMAND
task 28 55aa [MORE INFO IN THE WIKI (http://wiki.xda-developers.com/index.php?pagename=Universal_Technical)]
This commmand suppose to "Restores DOC to its original layout"

AFTER YOU RAN THE COMMAND, YOU WILL SEE "WAIT" and wait until you see the command line again

NOW if you run task 28 again,

------------------------------------
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>

You can INSTALL YOUR ROM AGAIN and it should work, at least it work for me

For what I can say, this trick REALLY WORKS! and resurrented my paparweight!!!!!!!

May everybody just take sometime to read this if u got struck in the splashscreen!!!

[sofene]

For what I can say, this trick REALLY WORKS! and resurrented my paparweight!!!!!!!

May everybody just take sometime to read this if u got struck in the splashscreen!!!I have done this several times and I'm still stuck at the splash screen.

[ronaldphl]

I have done this several times and I'm still stuck at the splash screen.

Just for your information, my Uni shows DocFailed after the initial task 28 check

Then I try that magic command, "task 28 55aa"
it showed "Wait..." and then rewrite my whole Doc layout.
then my Uni is back to life again.

BEst wishes for you pal. We both love our uni I know.

[nomadjim]

Ok, this is a seriously long thread and while I've read most of it (as well as many others on this site for the last two hours) I'm still unable to figure out a resolution to this problem.

I can't seem to get out of the "serial v2.08" screen. Holding down reset/power/record doesn't do anything but slightly dim the "serial v2.08" font briefly. What am I missing?

Btw, I have the Qtek 9090 and I got to this spot by (mistakenly) running EnterBL.exe

[tansoftware]

Ok, this is a seriously long thread and while I've read most of it (as well as many others on this site for the last two hours) I'm still unable to figure out a resolution to this problem.

I can't seem to get out of the "serial v2.08" screen. Holding down reset/power/record doesn't do anything but slightly dim the "serial v2.08" font briefly. What am I missing?

Btw, I have the Qtek 9090 and I got to this spot by (mistakenly) running EnterBL.exe

It seems u have a communication problem with your USB interface. It is advisable to check your USB driver and USB port on your PC. Try uninstalling activesync and re-installing it again using the latest version available on the net. Second thing you check is your USB port on your universal... Does your PC recognize your phone when connected ? If not, and after checking your PC and required drivers, send your phone to have its USB port checked.

Normally your PC should recognize your phone after which your phone switches to USB in bootloader mode.

Good luck.

[nomadjim]

And suddenly it finally communicates with my computer :)

I was focusing too much on the soft reset thing. Once it finally connected and I ran through the mtty instructions it all worked. Thanks so much, everyone!

[mahermp3]

heyyyyyyyy i have just finished my jasjar and it realy worked it was dead for 14 days her is wt i did i was searching for an answar for splash screen i tried mtty and her is the way
first disconect ur active synic and put ur jasjar at bootloder screen then open mtty( if set 14 0 didn't work and task 28 didnt work 2 try this task 2855aa then ) it will work then your screen will be total black and no hard rest or even soft rest will work don't panic just take the battry of the jas and let it out for 15 min then put it back 2 the device then charge it for 10 min or more as u like then try boot loder way (light+power+rest) it will be back at boot lod screen put any rom you wish and it will be back again best luck all

[mahermp3]

hey any luck with any body

[nahidul]

Hi

With my jasjar its not stuck on the bootloader screen but its stuck on a screen that just says serial on the top and v0.60 on the bottom of the screen. And the screen isn't lit up. I don't if the methods told here would work or not. And im kind of a noob here, what am suppose to do with mtty.

[mahermp3]

he
just try it iswear my jasjar was dead and this way he camwe 2 live againe just type in ur mtty that when you open it
1/ choose the usb
2/click ok
3/type in the white screen that will apear 2 you enter
4/you will see this (usb>) type task 2855aa
5/ press enter
6/it will be format
7/ if your jas give you ablank black scren just take out you battary for 15 min then charge it for another 15
8/ then try the usual bootloder mode and instal your rom it will solve the prob
9/ just note you have 2 but an original rom first then upgrade 2 any one you like

[nahidul]

A couple more questions, where do i get this orignal rom and when i open mtty ders a bunch of these settings, like for com1 or com2, do i just connect to my jasjar and select usb. and in the blank screen do u mean da computer screen or pocket pc. And thanks alot.

[mahermp3]

look when you try 2 connect your jas 2 the pc you must put it first into boot loder mod and you will have 2 dissconeect your active synicyou will do this
1/ open active synic then go to file connection seting disable usb then ok and close it
2/ put your divice into bootloader then conect it to your pc
3/ you continue the rest of the way
you can find the original rom in this site some where her if you couldn't find i have one ill upload it for you best luck

[nahidul]

Well i wasn't able to find the original rom, since i'm not a user, so if its possible to upload, that would be great.

[mahermp3]

her you are http://download.yousendit.com/9A13FEBE550A2247

[Fenix]

For what I can say, this trick REALLY WORKS! and resurrented my paparweight!!!!!!!

May everybody just take sometime to read this if u got struck in the splashscreen!!!

It worked for me as well :) Many many thanks!

[nahidul]

now im having a problem that my usb is not detecting the device, it only detects it as unknown.

And when i open the mtty tool there is no option showing USB only com1 and com2

[mahermp3]

now im having a problem that my usb is not detecting the device, it only detects it as unknown.

And when i open the mtty tool there is no option showing USB only com1 and com2

you must disconnect your active sync first then you put ur phone on bootlader screen befor connecting it into ur pc if the pro still try 2 charge ur phone and change ur usb cabl

[nahidul]

I tried everything, charging batteries, changing batteries, unistalling activesync, changing to a activesync 4.1 from 4.5, killed of the wcescomm.exe, tried uni_Exitbootloader, changed usb cables, changed usb ports. I DON'T EVEN KNOW WHAT TO DO ANYMORE, all i did is taped a file on my universal then it just got stuck on bootloader, all it says serial on the top and v0.60 in the bottom. Is it bricked or something.

[famsanr]

Ok, i found this solution from google and its a china website (http://bbs.pdafans.com/thread-332549-1-5.html). And it actually reference back to the xda-developers wiki
http://wiki.xda-developers.com/index.php?pagename=Universal_Technical

THIS WORKS ON when you run task 28 in MTTY and return the DOC_format failed result


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


NOW RUN THIS MAGIC COMMAND
task 28 55aa [MORE INFO IN THE WIKI (http://wiki.xda-developers.com/index.php?pagename=Universal_Technical)]
This commmand suppose to "Restores DOC to its original layout"

AFTER YOU RAN THE COMMAND, YOU WILL SEE "WAIT" and wait until you see the command line again

NOW if you run task 28 again,

------------------------------------
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>

You can INSTALL YOUR ROM AGAIN and it should work, at least it work for me

I'm so grateful with you for helping me to back to life my universal. I've tried many ways and I must recognice your big work for my dear Uni. Thank you.

[sofene]

I'm so grateful with you for helping me to back to life my universal. I've tried many ways and I must recognice your big work for my dear Uni. Thank you.Why does it not work for me? Why am I permanently stuck on splash screen no matter what I do and I have tried every suggested trick. I can enter bootloader and do all the mitty tricks and reflash to any rom but without any errors and still get stuck on splash screen. Why, why, why??????? What else do I have to? I want my Uni back from this lonnnnng sleep. Somebody please help!!

[romabbs]

My first message just to share this message and say THANK YOU!!!
I've tried many ways too and spent a lot of time to find a solution without success. Finally, I ran the MAGIC command task 28 55aa and then task 28. I've installed again the original ROM and..... I'm back to use my QTEK 9000!!:D Thank you again!


I'm so grateful with you for helping me to back to life my universal. I've tried many ways and I must recognice your big work for my dear Uni. Thank you.

[dzinfo]

Why does it not work for me? Why am I permanently stuck on splash screen no matter what I do and I have tried every suggested trick. I can enter bootloader and do all the mitty tricks and reflash to any rom but without any errors and still get stuck on splash screen. Why, why, why??????? What else do I have to? I want my Uni back from this lonnnnng sleep. Somebody please help!!


:confused: :confused:

exactly the same issue with you, mine is 6515
any one knows how to deal with this? task 32, 28 doesn't supported by 6515, no respones at all

[Nomadturk]

Hmm, mine stuck at the splash screen as well.
This sucks, i don't know why but it does stuck when i install some ROM's.

Till now, it stuck when i tried flashing

Ranju_v1_1908_18508_0_7_0
and
BSTYL26_WM6PRO_Bussiness_VC update_1

But this time, i simply didn't wanted to install another ROM, and trying to find a solution.

Below are what i tried and that didn't work...

1- set 14 0
2- hard reset
3- soft reset
4- enter BL options and select YES for "clean storage" and the other one.
5- Re-install only the ROM


Now, i'm trying flashing only Radio and Extended ROM, hoping this will help.
If not, i have to go back to another ROM, but i really want to try these ROM's.

Right now, BSTYL26_WM6PRO_Bussiness_VC update_1 is installed on my SPV m5000 and radio upgrade is finished. I'll try resetting the device without doing a hard-reset. As i always do...

Radio is updated to 1.18 from 1.17 with success but...
I'm still waiting at this screen. Oh, let me mention that i already have removed SIM and SD Cards.

Now, i've opened mtty, and this is what i got for a task 28

DOCInfoTableinitHW+
Binary0 Size: 0x100000
FAT0 Size: 0x4000000
FAT1 Size: 0xA00000
FAT2 Size: 0x2900000
All Size: 0x7400000
FAT0_ADDR=0x100000,FAT1_ADDR=0x4100000,FAT2_ADDR=0 x4B00000

As fas as i can understand, it doesn't have a problem with storage or DOC.
My bootloader version is 2.01, does it have something to do with it?


Anyway, these steps didn't help, so now, if you excuse me i have to install yet another rom to avoid this screen.

task 28 55aa
Wait..
DOCInfoTableinitHW+
Binary0 Size: 0x100000
FAT0 Size: 0x4000000
FAT1 Size: 0xA00000
FAT2 Size: 0x2900000
All Size: 0x7400000
FAT0_ADDR=0x100000,FAT1_ADDR=0x4100000,FAT2_ADDR=0 x4B00000
USB>task 0

[akshaybs]

Hmm, mine stuck at the splash screen as well.
This sucks, i don't know why but it does stuck when i install some ROM's.

Till now, it stuck when i tried flashing

Ranju_v1_1908_18508_0_7_0
and
BSTYL26_WM6PRO_Bussiness_VC update_1

But this time, i simply didn't wanted to install another ROM, and trying to find a solution.

Below are what i tried and that didn't work...

1- set 14 0
2- hard reset
3- soft reset
4- enter BL options and select YES for "clean storage" and the other one.
5- Re-install only the ROM


Now, i'm trying flashing only Radio and Extended ROM, hoping this will help.
If not, i have to go back to another ROM, but i really want to try these ROM's.

Right now, BSTYL26_WM6PRO_Bussiness_VC update_1 is installed on my SPV m5000 and radio upgrade is finished. I'll try resetting the device without doing a hard-reset. As i always do...

Radio is updated to 1.18 from 1.17 with success but...
I'm still waiting at this screen. Oh, let me mention that i already have removed SIM and SD Cards.

Now, i've opened mtty, and this is what i got for a task 28


As fas as i can understand, it doesn't have a problem with storage or DOC.
My bootloader version is 2.01, does it have something to do with it?


Anyway, these steps didn't help, so now, if you excuse me i have to install yet another rom to avoid this screen.

I have the exact same problem!! The phone works well with the official Imate ROM but am stuck at the blue Imate splash screen when I install BSTYL26_WM6PRO_Bussiness_VC update_1. Havent tried other roms though. But looks like everything has been "updated" though. Any hardware issues that anyone knows about? Are the developers listening??

-Akshay

[homa]

Hi all!
I read all the 350 posts on this topic.
In my case the cause of this stuff was the flashing of the Videocall WM6 ROM Kitchen (further at the guessing part). Or maybe it occured when I couldn't finish flashing a Radio ROM (I killed the app and disconnected the Uni rather brutally). Or this just worsened the situation.

Sollution for me
Tried the task 28 in mtty, couldn't format. Than task 28 55aa, and it did the trick. So - that easy - I could bring my Uni back to life. Note: I charged to 100% before doing this (however, I only knew it was 100% after it came to life).

Guessing
Why this occurs? AFAIC nobody knows what exactly causes the bad blocks in the DOC. Because the problem is with the DOC for sure, if you stuck at the bootscreen. First I guessed it was because of the kitchen I used, even with standard packages it built a ROM with negative number of free sectors. At Blue Angel this definetly concluded into a faulty ROM.
After I read all the posts, I started to think, the problem was with the Radio stuck instead, because many ppl stucked after flashing an official ROM _and_ sometimes reflashing the RadioROM helps. So my hardest guess is that the Radio ROM is responsible for all this madness.

Hope this long brainstorming helps! And be caucious at flashing! I will...

[akshaybs]

Hi all!
I read all the 350 posts on this topic.
In my case the cause of this stuff was the flashing of the Videocall WM6 ROM Kitchen (further at the guessing part). Or maybe it occured when I couldn't finish flashing a Radio ROM (I killed the app and disconnected the Uni rather brutally). Or this just worsened the situation.

Sollution for me
Tried the task 28 in mtty, couldn't format. Than task 28 55aa, and it did the trick. So - that easy - I could bring my Uni back to life. Note: I charged to 100% before doing this (however, I only knew it was 100% after it came to life).

Guessing
Why this occurs? AFAIC nobody knows what exactly causes the bad blocks in the DOC. Because the problem is with the DOC for sure, if you stuck at the bootscreen. First I guessed it was because of the kitchen I used, even with standard packages it built a ROM with negative number of free sectors. At Blue Angel this definetly concluded into a faulty ROM.
After I read all the posts, I started to think, the problem was with the Radio stuck instead, because many ppl stucked after flashing an official ROM _and_ sometimes reflashing the RadioROM helps. So my hardest guess is that the Radio ROM is responsible for all this madness.

Hope this long brainstorming helps! And be caucious at flashing! I will...


Well, this is what happened to my phone

1. Flashed new rom (cooked rom)
2. stuck at blue screen
3. used the task 28 55aa magic
4. started working again (only on an official rom)
5. flashed with cooked rom again
6. stuck on blue screen
7. used task 28 55aa again and revived my uni
8. flashed officila rom and stfu

does this info help?

-Akshay

[homa]

Ummm... I'm not pretty sure if everybody knows what I'm thinking of.
When you build a ROM from a kitchen, you run the batch file (BuildROM or somethink like that) and after it built all the files and modules it writes a checksum: sectors/free sectors. If free sectors is a long hexa number, starting with an F, I'm quite sure it's negative and bad news.
But at least prebuilt ROMs work (for me) and task 28 55aa is already known.

[ynagy]

Ok, i found this solution from google and its a china website (http://bbs.pdafans.com/thread-332549-1-5.html). And it actually reference back to the xda-developers wiki
http://wiki.xda-developers.com/index.php?pagename=Universal_Technical

THIS WORKS ON when you run task 28 in MTTY and return the DOC_format failed result


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


NOW RUN THIS MAGIC COMMAND
task 28 55aa [MORE INFO IN THE WIKI (http://wiki.xda-developers.com/index.php?pagename=Universal_Technical)]
This commmand suppose to "Restores DOC to its original layout"

AFTER YOU RAN THE COMMAND, YOU WILL SEE "WAIT" and wait until you see the command line again

NOW if you run task 28 again,

------------------------------------
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>

You can INSTALL YOUR ROM AGAIN and it should work, at least it work for me

thank for your guide
here's the full solution step-by-step to share with you guys

First download mtty utility (see the attached file)
1. Take out the SD and SIM cards
2. Opened ActiveSync and go to file, connection setting and Un-check "Allow USB Connections". Then press Ok and close ActiveSync
3. Put in bootloader mode (Power + Light + reset) which brings up the "un-backlit" screen with "Serial" at the top and v0.XX at the bottom
4. Plug in USB cable DIRECTLY from PC to Jasjar (MAKE SURE NOT TO USE A USB HUB). You MIGHT then see a warning window complaining that an "Unsigned" device driver is being attempted to be installed. You will be prompted to either "STOP INSTALLATION" or "CONTINUE ANYWAY" - this warning can be safely ignored and so just click on "CONTINUE ANYWAY".
5. Open mtty utility / software
6. Select USB from the "Port" drop-down on the upper left corner of the dialog box and hit OK
7. Then another screen will come up. Hit enter and that will show "USB>"
8. Type "set 14 0" and hit enter. You will see some jibberish on the mtty utility which will again be suffixed by "USB>".
9. Type "task 28 55aa" This commmand suppose to "Restores DOC to its original layout". AFTER YOU RAN THE COMMAND, YOU WILL SEE "WAIT" and wait until you see the command line again.
10. You can INSTALL YOUR ROM AGAIN and it should work, at least it work for me

[xanadu]

Well, this is what happened to my phone

1. Flashed new rom (cooked rom)
2. stuck at blue screen
3. used the task 28 55aa magic
4. started working again (only on an official rom)
5. flashed with cooked rom again
6. stuck on blue screen
7. used task 28 55aa again and revived my uni
8. flashed officila rom and stfu

does this info help?

-Akshay
Thank you it was very helpfull. My friend's uni works again: only with officielle rom (Tmob UK last one) with cooked rom freeze allways. One usefull tip: entering MTTY only possible with original HTC usb-cable: As I'v tried before with two noname usb-cable they can't find usb-port any way.

[sofene]

Thank you it was very helpfull. My friend's uni works again: only with officielle rom (Tmob UK last one) with cooked rom freeze allways. One usefull tip: entering MTTY only possible with original HTC usb-cable: As I'v tried before with two noname usb-cable they can't find usb-port any way.

Where can I find the O2 XDA official rom?

[neoone]

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

That seriously WORKING !!
thx hdubli

[ThaDizzle01]

Ok have everything up to the part where you go to the bootload. screen and install the rom. I have vista but when i try to on a computer with XP it gives me a error when i try to load the rom saying rapi.dll mising or not found....should i just download the dll file and place it in the /system/ folder on the comp then retry?

[wsubrata]

I have vista but when i try to on a computer with XP it gives me a error when i try to load the rom saying rapi.dll mising or not found....should i just download the dll file and place it in the /system/ folder on the comp then retry?

missing rapi.dll ---> you are not install activesync on XP
i'm just finished upgrade B&L rom with xp servicepack1 :)
If you can not flash the universal then you must use the original usb-cable!

[geovass]

Hello all,

i am trying to follow the guide but i dont have a USB option on the drop down box onthe mtty..


EDIT: Fixed it.

[pradipa]

Dear, Buzz,

My O2 presently stuck on splas screen,
already try by using mtty, but on O2 appear "USB transfer fail",
any solution?

regards

[nahidul]

ya my htc universal is still stuck at serial v0.60 and i tried all the methods, mtty tool does not allow me the option of picking usb from the drop down menu. And I have closed the connection active sync. Tried different usb cords, different batteries, and once in a while if i replug the cord it stays on usb then switches back to serial. Please Help I've tried everything so far.

[Ai Mania]

I have do upgrade and flashing all new cooked uni ROM, Radio, and Ext Rom for many time without any problem. But suddently I got it a couple days ago. I have MDA PRO using Ranju's WM6.1 V7.6 for few days and I add some cab file until I feel the device become slow and I want to refresh the ROM by reflashing ROM.
Than I got stuck on 10% upgrade CE ROM progress. I waiting for at least 2 hours and everything still do nothing. I still got grey screen.
I tried reflash all rom, used mtty, do all info from the thread but always I got 10% upgrade CE ROM stuck with box message said "CE ROM UPDATE PROBLEM"
One thing that I cannot understand I still can flashing radio image, but it didn't work for CE ROM and ext rom.
Please anybody help me ...????

[Ai Mania]

I have do upgrade and flashing all new cooked uni ROM, Radio, and Ext Rom for many time without any problem. But suddently I got it a couple days ago. I have MDA PRO using Ranju's WM6.1 V7.6 for few days and I add some cab file until I feel the device become slow and I want to refresh the ROM by reflashing ROM.
Than I got stuck on 10% upgrade CE ROM progress. I waiting for at least 2 hours and everything still do nothing. I still got grey screen.
I tried reflash all rom, used mtty, do all info from the thread but always I got 10% upgrade CE ROM stuck with box message said "CE ROM UPDATE PROBLEM"
One thing that I cannot understand I still can flashing radio image, but it didn't work for CE ROM and ext rom.
Please anybody help me ...????


Alhamdulillah ... It's solved using mtty and task 28 55aa than flash use official ROM
Thanks guys ... I love this forum :D

[sturdza]

Hi there,

Mine looks bad :

I did everything I read, however, my Universal will not change to USB in the display when I plug in ther USB Cable. I have tried other calbles too.

What can I do ?

Please help

[terroar]

Hey can somebody help me, my O2 xda exec is stuck in the bootloader v2.01 ... how can i get out of this damn bootload screen and update my O2 xda exec and update it to WM6???

If you have to Private message me, thats even better ill even send in 50 bucks through paypal (ONLY WHEN WE FIX THIS AND GET WINDOWS 6 WORKING ON MY 02 EXEC) .... cause im like retarded when it comes to hacking phone Roms lol!!!!

thank you in advance,

RoaR

[orangdayak]

Hey can somebody help me, my O2 xda exec is stuck in the bootloader v2.01 ... how can i get out of this damn bootload screen and update my O2 xda exec and update it to WM6???

If you have to Private message me, thats even better ill even send in 50 bucks through paypal (ONLY WHEN WE FIX THIS AND GET WINDOWS 6 WORKING ON MY 02 EXEC) .... cause im like retarded when it comes to hacking phone Roms lol!!!!

thank you in advance,

RoaR

Dude, read the wiki and u will the the answer to fix it. Im tempted to have your 50 bucks, but nah nvm.. Enjoy

[arag0n]

THANKS!!!! THANKS!!!! THANKS!!!! THANKS!!!! THANKS!!!! THANKS!!!! My T-Mobile MDA Pro was dead, and it's solved using mtty and task 28 55aa. Now my PDA is alive again (and with WM 6.1)!!!

I love all of us, i love this forum!!!!

PD: My english is very bad, i'm sorry, but i'm very very very very happy!!!!

[ccarlsson]

Hallo aragün,

would you please be so kind and tell me the correct way that works.
I tryed many times but no way works on my MDA.
Do you speak (write) german?
Regards
ccarlsson

[ynagy]

I had it before with other ROMs to fix it try http://forum.xda-developers.com/showthread.php?p=1650610#post1650610

[arag0n]

Hallo aragün,

would you please be so kind and tell me the correct way that works.
I tryed many times but no way works on my MDA.
Do you speak (write) german?
Regards
ccarlsson

Hey ccarlsson, I did what was stated in the message:

"Originally Posted by chrisky
Ok, i found this solution from google and its a china website. And it actually reference back to the xda-developers wiki
http://wiki.xda-developers.com/index...rsal_Technical

THIS WORKS ON when you run task 28 in MTTY and return the DOC_format failed result


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


NOW RUN THIS MAGIC COMMAND
task 28 55aa [MORE INFO IN THE WIKI]
This commmand suppose to "Restores DOC to its original layout"

AFTER YOU RAN THE COMMAND, YOU WILL SEE "WAIT" and wait until you see the command line again

NOW if you run task 28 again,

------------------------------------
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>

You can INSTALL YOUR ROM AGAIN and it should work, at least it work for me"

[bym007]

Hey ccarlsson, I did what was stated in the message:

"Originally Posted by chrisky
Ok, i found this solution from google and its a china website. And it actually reference back to the xda-developers wiki
http://wiki.xda-developers.com/index...rsal_Technical

THIS WORKS ON when you run task 28 in MTTY and return the DOC_format failed result


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


NOW RUN THIS MAGIC COMMAND
task 28 55aa [MORE INFO IN THE WIKI]
This commmand suppose to "Restores DOC to its original layout"

AFTER YOU RAN THE COMMAND, YOU WILL SEE "WAIT" and wait until you see the command line again

NOW if you run task 28 again,

------------------------------------
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>

You can INSTALL YOUR ROM AGAIN and it should work, at least it work for me"

Here's my thing;
I have got an Exec, which was working until this morning with Tomal ver 8.x but a bit of hanging issues. So I decided to upgrade to the latest Tomal 8.2 available.

Now my screen is stuck on bootloader (says SERIAL and v2.01, and SERIAL changes to USB when I connect to my PC). I have Vista Ultimate on my PC. When I connect Exec to PC, the phone is not charging, I have unchecked the option of USB connectivity in "Windows Mobile Center" (new ActiveSync). Now when I try to use mtty, I can select USB or WESUSB (as suggested by someone else) but it never connects to my phone.

Trying to flash the ROMs (Tomal's latest + O2's latest official +Sivan310), it fails with error 112 "CE ROM UPDATE ERROR"...

Just to clarify once again, there is no SD or SIM cards in the phone. I am using Windows Vista, the phone does not charge from PC.

Any ideas guys ? Many thanks for reading about my misery ...

[bym007]

all guys, just worked out, the upgrade does not work from Vista (atleast when corrupted). I used windows xp from within vmware 6, and mTTY started connecting via USB, plus ROM upgrade worked like a charm ...

now Vista $uck$ ...

[sergimenez]

Thanks Thanks Thanks Ok Thanks Thanks Thanks.

[danielehk]

Hi, I have a xda exec the have "No gsm" problem.
I have tried to do task 28 55aa and task 28 from mtty, and....

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>


But when tried to reflash the radio....stop at 0 %.
Do you have some idea?
Thanks

Daniele

[danielehk]

I have also tried to upgrade from sd, usin ntrw ecc ecc but doesn't load os from sd, annd remain only in bl mode.
Daniele

[baaas07]

Please help

When i type task 28 55aa in MTTY it says:
USB>task 28 55aa
DOC_format_HW+
DOC_format failed!
USB>

Any sugestions?

[mahermp3]

Please help

When i type task 28 55aa in MTTY it says:
USB>task 28 55aa
DOC_format_HW+
DOC_format failed!
USB>

Any sugestions?

you can try to take of the battry for 10 minuites then try the mtty 28 55aa again if still try to use the mtty 28 and see what it say's waitting 4 you

[Curehead]

Hi there,

Mine looks bad :

I did everything I read, however, my Universal will not change to USB in the display when I plug in ther USB Cable. I have tried other calbles too.

What can I do ?

Please help


Hi there, I am having the same problem, does anyone has an idea? The funny thing alss is that when putting the usb connection halfway in the phone i get the "usb" instead of serial ...
I hope someone has an idea ...
Cureheade

[david_dessouza]

Dear All

My jasjar is stuck on the Boot screen , on top its showing USB and
Bottom V1.00, i try to hard reset , soft reset but nothing happend,

I try Mtty allso but no result still screen show the USB on top and Bottom
V1.00 .

can some one tell me how can i get back on normal .


Regards

David

[capati971]

hello same probleme: stay on the Boot screen...

i try different radio..and rom...nothing...
help,

thanks

[Curehead]

Hi to all,

having tried about anything, i was feeling VERY frustrated. I read about a thousand posts with all (more or less) interesting ideas.
Since my new universal is a replacement (my lovely 4year old daughter smashed it, and my phone connections were breaking up), I had still a functioning one (except the phone part that is!). So i started testing from scratch with my old universal and .... ALSO stuck in serial without changing to usb !!!!!
I read somewhere a post about changing cables, so I rounded up al mu usb-miniusb cables and what the F***: ALtough it did not work with my original cable, it DID work with another cable (don't know if it's A or B) which came with some old stuff.
and then it DID change to usb.
SECOND THING: ALtough I followed all the stuff concerning vista (wmdc, drivers, processes, it DID NOT WORK.
So I retook possession of my old laptop (OS=XP) and .... there it is able to flash ..
Now I am able to flash a certain rom (tomal) and a certain bl (v1.01). I am now trying out different roms.

Only thing annoying remaining is: when upgrading/flashing the install program never finds the already installed rom, radio, ....

well; I hope this helps some one, i mean I really tried about anything only to discover that another cable and another OS-laptop was the answer instead of thousands software try-outs

Success to all!

Curehead

[Curehead]

Hi all,
just dropped in to mention some final details. :) Since my phone was all messed up and had to flash new os. I took the time to flash like a dozen different roms, to test them out. And during this process bit by bit I saw my (previous installed roms) coming on the startup updater utility.:eek:

So keep up trying everybody!

[Icemanukle]

Hi, I too had a problem after 12 months of the bricked XDA Exec (Universal) just sitting on the self I finally took on the challange.
My issue was caused when i tried to update my Rom using a Vista PC.
It didnt matter what I did it just wouldnt work.
I got round it by partioning my Hdd on my PC loading a dual boot loader and installing XP.
When I ran the upgrade it loaded, no problems and now my O2 Exec is working perfectly.

There seems to be a real issue updating Roms with a Vista based PC.

Hope this works for you.
Kind regards Ice.

[Curehead]

Hi Icemanukle and others,

EXACTLY !!! Vista sucks AGAIN! So everybody: before going mtty or jtag, try XP (Why the hell did I had to have Vista on my newest laptop, stupid stupid me!)

Curehead

[justinwateridge]

I'm rubbish, I can't even get mtty1.42 to allow me to connect via USB. I'm using vista which has the bizarre activesync build in which allows me to disable the connection via usb but it still won't show it in the list in mtty or allow me to type it in. My exec is stuck on the dark screen with USB at the top and v2.01 at the bottom and won't let me do anything.

Any help would be gratefully recieved

regards

J

[Curehead]

Justin,
just try an xp! Vista just keeps on messing up (mtty won't make a difference; drivers aren't a garantuee 4 anything). Trust me, I tried everything for days on days with disappointing results. Dude, partition your harddisk and use XP as OS.

Need proof of life? Keep your eyes close on your boot screen "Serial" and when very slowly retracting usb-cable from your universal you WILL see it change for a very short moment (meaning hardware and connection-possibility is OK!)

Greetz,
Cureheaded

[kwmbrother]

hi please can u explain this for me
-Now connect woth USB cable and open mtty utility
-Select the "WESUSB... " port

[isaiah.blacknall]

Hi im so lost when i use the NTTY Ver, 1.42 Only a box opens up and shows com port and a few other things that all i see.:confused::confused::confused: Plz My T-Mobile MDA is stuck in bootloader. thats as far as i got

[rapboy23]

mtty nothing only com 1 and com 2 .bootloader nope power- backlight-reset nothing. always blank screen :( what must ı do?help me plsss

[mahermp3]

make sure you turned of the active sync and if it stell so try to changE the usb if not may bE its about your DEsktop winDoWs may be not stablled and you need afresh one installed and try to take of the battry of your phone untill you repair the windows on your pc may be it came back again and it will be in God well

[Heince]

hei guys, i have the same problem
anyone can help?

i try any posibilities but it still stuck.
help me please, i so confused

[Cielistha]

can anyone help me????

I got the universal stuck in bootloader. the only things i have just a dopod logo.
i tried:using mtty utilitty then write set 14 0,for usb connection, it works,and I tried to upgrade my universal, at the screen wrtitten:100% success,then I do a hard reset, but I just got the same as before....
at the screen only dopod logo has apperared.


can anyone help me,please.....

may my mainboard got a trouble ???

[samadkhi]

I upgrade my Universal with ROMs for HTC Universal, by Cotulla
this rom is one of the best i've ever use
in this rom there is no BootSplash to save memory
.........
so as i'am plaining to install my Universal in my car, i'll be needing
a bootsplash with my car brand logo .....

there for i need to have original rom .... but when i follow the
uninstallation procedure i've got error as by mistake i've upgrade
another rom with out uninstallation by bootsplash become's fussy...
then i charge 100% my universal

AND

I've followed the instructions in this forum .....

http://forum.xda-developers.com/showthread.php?t=259003

Problem Resolved

Here what I have done...

First I followed the uninstallation instruction

USB>task 32
Level = FF
USB>info 2
DOC_ReadFAT1 fail: Start=15A0000,Len=200
HTCSCDL__001 œˆóHTCE
USB>task 32
Level = FF
USB>task 28 55aa
Wait..
DOC_ReadFAT1 fail: Start=15A0000,Len=200
Read data error in tag
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

then...


USB>set 14 0
USB>set 14 10
USB>set 14 9
USB>set 14 9
USB>set 14 9
USB>set 14 20

after this close MTTY

and update

ms_.nbf nk.nbf radio_.nbf

by using

MaUpgradeUt_noID.exe

it takes me about 30 minutes with full Battery

[Yordan_Radev]

Hi guys.
I have very very big problem.
I tryed to upgrade my Qtek 9000 to WM6 cause it had some shity version of WM6 and cause my Active sync does not detect it i tried some SD card version.And the resault was stuck on bootscreen.After that i read 10000 things in this forum and tryed some exe from my pc to fix the bootscreen issue and the phone turned off and now it is not turning on and does not even want to charge.Please help me bring my phone to life again cause it is my favourite one and i do not want to throu it away.

Thnak you a lot in advance
Cheers

[-Jonny-]

Hi Yordan, I assume you've tried a soft and hard reset?

Otherwise, take yourself along to the Wiki and try the suggestions there
Instructions for those stuck on Boot Screen (http://forum.xda-developers.com/index.php?pagename=Uni_Stuck_Bootloader) (But the PC recognizes the PDA)
Instructions for those stuck on Boot Screen and the PDA is not Recognised (http://forum.xda-developers.com/index.php?pagename=Uni_Stuck_Bootloader_Serial)

Please let us know if you are still having problems.

[Yordan_Radev]

Yes man i think i hard reset it after it turned off.........is it dead or there is way to turn it on.I read all about it but when i was stuck on the screen showing USB it says that everything is ok but no version of WM was updating.They all failed and it continued to stay on bootscreen so i tryed this "tool" to take it out of boot loader mode and i turned off and never tunr on.So this is why i am asking what to do,cause it is very hard to find Universal in Bulgaria,and it my favourite one........other way i will buy the new Touch Pro 2 and put the Universal on my wall of shame :)))))
Cheers


Thank you again

[tusipali]

Dear Colleges!

I have the problem with my HTC Universal.
After not finished ROM upgrade, my Universal not booting up.
I have the blank screen and when i try to connect to my pc with USB connection, the PC don't recognize the Unuversal. With USB connection tha charging led not light. When i try to reset universal, the charging led blink for a moment with red light and switch off.

Im measure the voltage of accumulator and out from the phone is 3.65V.

Can help me somebody?
I dont't have more tips to wakeup my pda.

Regards, Pal

[orb3000]

Dear Colleges!

I have the problem with my HTC Universal.
After not finished ROM upgrade, my Universal not booting up.
I have the blank screen and when i try to connect to my pc with USB connection, the PC don't recognize the Unuversal. With USB connection tha charging led not light. When i try to reset universal, the charging led blink for a moment with red light and switch off.

Im measure the voltage of accumulator and out from the phone is 3.65V.

Can help me somebody?
I dont't have more tips to wakeup my pda.

Regards, Pal

Welcome to the forum

Have you read the Wiki here?
http://wiki.xda-developers.com/index.php?pagename=Uni_Stuck_Bootloader_Serial

Good luck,

[tusipali]

Orbs!

Thanks for tip, but on my universal display i don't see anithing, don't going to bootloader mode sorry.
The MTTY don't connect to USB port, don't see my phone.

Any more tips?

Thanks!

[-Jonny-]

Did you flash on charged battery (ie, is it still charged now).
Have you tried to go into bootloader?

[tomal]

Orbs!

Thanks for tip, but on my universal display i don't see anithing, don't going to bootloader mode sorry.
The MTTY don't connect to USB port, don't see my phone.

Any more tips?

Thanks!
If it doesn't go to BL then I'm pretty sure that your key combination is not right. Do it as follow -

1st - press light button and hold it
2nd - press power button and hold it (now you'll see kilt info)
3rd - press reset button and hold for a second
4th - release the reset button (now you'll see serial on top)
5th - release light and power button

regards

[Leviata]

Hi to all!,

Firstly this is my first post on the forum so I want to send a big kiss to everybody!

Now say that I have the same problem.

I used "task 28 55aa", it worked and my DOC was formated so I need to install a new ROM now but I can't.

I tryed with the O2 ship rom and Orange M5000 ship rom and nothing appears to happen. Program returns "Connection Problem, etc, etc" but update never begins.

My device is a Qtek 9000 (my father doesn't use it), so wich ROM i need to install to recover the device?.

Thank you very much to all,

A big kiss,
Mary

[orb3000]

Hi to all!,

Firstly this is my first post on the forum so I want to send a big kiss to everybody!

Now say that I have the same problem.

I used "task 28 55aa", it worked and my DOC was formated so I need to install a new ROM now but I can't.

I tryed with the O2 ship rom and Orange M5000 ship rom and nothing appears to happen. Program returns "Connection Problem, etc, etc" but update never begins.

My device is a Qtek 9000 (my father doesn't use it), so wich ROM i need to install to recover the device?.

Thank you very much to all,

A big kiss,
Mary

Welcome to the forum

Please have a look into the Wiki
http://wiki.xda-developers.com/index.php?pagename=HTC_Universal

Regarding what ROM to flash I can recommend Tomal 8.5 or 8.9ROm´s

Good luck,

[Leviata]

Welcome to the forum

Please have a look into the Wiki
http://wiki.xda-developers.com/index.php?pagename=HTC_Universal

Regarding what ROM to flash I can recommend Tomal 8.5 or 8.9ROm´s

Good luck,

Hi,

I have read the entire WIKI trying to recover my device but I can't. I tryed with Exit_Bootloader, mtty in bootloader with USB (tryed commands like 14 0, 16 0, etc).

As i said, task 28 55aa worked for me but now i need to flash a ROM to make my device usable.

As i know, I can't install a Tomal WM6.1 o WM6.5 because my device is locked. In fact, I broke my device trying to flash Tormal 8.9 directly from WM5.0.

When I try to flash a ROM it returns:

"Error 201: Get Device Data Error"

"Can not get device data."

"Please make sure device are connect to device and execute this update utility again"

So I'm stuck on BootLoader v1.00 screen with no ROM,no ExtRom and no Radio on my Uni...

Any idea?

[orb3000]

I presume you already unlock your device and made MTTY and/or Doc format right?

[Leviata]

I presume you already unlock your device and made MTTY and/or Doc format right?

-------------------------------------------------------------------------------------------
IN SPANISH

Veo que eres de México así que te hablo en Español si no te molesta, ¿vale?.

Bueno, te explico, la PDA la tenía mi padre en un cajón y no la usaba, tenía la ROM que venía de fábrica es decir, una con WM5.

Yo no la desbloquee (unlock), aunque si te sirve de algo es una Qtek 9000 libre de fábrica (no es de ningún operador) así que no se si hacía falta hacerle algún tipo de unlock. Si había que hacerlo yo no lo hice y a lo mejor ahí está el fallo.

Pues bueno desde WM5 intenté instalarle la Tomal 8.9. Me sincronizó el ActiveSync, se reinició la PDA se puso en Bootloader y salió la barra del %, pero no llegó ni a ponerse a 1%, dio error de comunicación y a partir de ahí solo sale la pantalla del Bootloader.

He probado con "set 14 0" para que arranque el OS, pero como no tiene pues no hace nada, ya que le hice un "task 28 55aa" para reiniciar la DOC.

Ahora estoy intentando flashearle algun ROM pero es imposible, no pilla ninguna.

Estoy en BootLoader y pone "Serial" y abajo "v1.00". Le conecto el cable USB, el ordenador lo detecta y en la PDA cambia "Serial" por "USB". Entonces ejecuto la actualización, aparece la primera ventana, le doy a Next, se queda un rato chequeando y aparece la pantalla que te dice la ROM,RAdio,Ext que tienes y las que vas a flashear, pero a mi me salen todos los campos vacios (mira la primera imagen de abajo). Igualmente le doy a siguiente y se queda para siempre en la pantalla que dice "Checking the information on your device..." y no avanza al proceso de actualización. No queda otra que quitar el USB y entonces aparece un Error 150: ROM UPGRADE UTILITY ERROR. Aun con el USB quitado en la pantalla de la Universe sigue apareciendo "USB" en vez de "Serial", es decir, que el Universe se ha colgado y solo vuelve en si con un softreset. A lo mejor no puedo flashear porque el aparato se cuelga y por eso no continua con el proceso.

Abajo te adjunto el RUU.txt para ver si te dice algo

He probado con multitud de ROMs y nada, con todas pasa lo mismo.

Abajo te adjunto unas capturas de pantalla para que veas lo que me pasa exactamente.

Estoy completamente desesperada y necesito ayuda porque estoy segura de que esto se puede arreglar, tengo fe!!.

Muchísimas gracias por tu ayuda guapo!.

Un beso!,
Mary

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

IN ENGLISH

I didn't unlock the phone, coz is a brand-unlocked Qtek 9000, so I don't know if a unlock is needed (for a SuperCID por example). If an unlock before flash was needed perhaps that was the problem.

Here is what I did. From WM5 I tryed to install Tomal 8.9. ActiveSync detected my phone then I executed the ROM. PDA reboots to BootLoader and the % percent bar appears but on 0% program returns a Connection Error and till then the PDA is in BootLoader.

I tried with Mtty and "set 14 0" (to load OS after reset) but nothing happens because I use "task 28 55aa" to initialize DOC so not OS is installed.

I'm trying to install a ROM to recover the device but is impossible to make it work.

I will explain what I do to try to flash a new ROM:

In BootLoader mode (appears "Serial" on top and "v1.00" on bottom) I plug the USB to the computer (Windows XP SP3). "Serial" changes to "USB" then I run MaUpgradeUt_noID.exe (ROMUpgradeUt.exe doesn't work either). I click Next to begin update and after several seconds appears an empty summary window with no ROM, Radio and ExtROM (look first attached screenshot). Wherever, I click on Next but the program hangs on "Checking the information on your device..." forever, no matter how many minutes I wait (see the second screenshot). Then I need to remove the USB to cut the process giving error 150: ROM UPGRADE UTILITY ERROR. Without USB the device keeps saying "USB" (doesn't change to "Serial" when I remove the wire) then a softreset is needed. Perhaps the device hang while updating so I cannot flash?.

I tryed with lot of ROMs and none worked.

Below I paste the RUU.txt. Perhaps it helps...

I'm so sad trying to repair the Universal but I'll never surrender.

Thank you very much for read.

A big kiss,
Mary

Screenshot 1:
http://i39.tinypic.com/m7ui54.jpg

Screenshot 2:
http://i41.tinypic.com/70gq6d.jpg

08:33:36:968 [msg] : Version : [2.11].

08:33:36:968 [msg] : Config Info : [857873],[1],[0],[0],[1],[0],[0],[1].

08:33:40:703 [msg] : Current Not in CE Mode or in CE Mode but ActiveSync Not Connected.

08:33:44:734 [msg] : Disconnect ActiveSync .... [2]

08:33:44:734 [msg] : Start Get Connect Port.

08:33:44:875 [msg] : Current in BL Mode. Open Port : [\\.\WCEUSBSH001] OK.

08:35:30:359 [err] : BL Get Device Data Error.

08:35:30:359 [msg] : Update Image. CE : [4], MSystem : [2], Radio : [1]

08:43:56:156 [msg] : Check Ac in BL mode. AC : [2]
08:43:57:656 [msg] : IsBL. BL : [1]

08:43:57:656 [msg] : =============================================

08:43:57:656 [msg] : START UpdateRadio !

08:43:57:671 [err] : Check SecurityPassword Error.

08:43:57:671 [msg] : START UnInitialization !

08:43:57:671 [msg] : END UnInitialization !

08:43:57:671 [msg] : IsBL. BL : [1]

08:43:57:687 [msg] : START BackCEMode !

08:43:57:687 [err] : BL Set BackCE Flag Error.

[Leviata]

Duplicated

[orb3000]

-------------------------------------------------------------------------------------------
IN SPANISH

Veo que eres de México así que te hablo en Español si no te molesta, ¿vale?.

Bueno, te explico, la PDA la tenía mi padre en un cajón y no la usaba, tenía la ROM que venía de fábrica es decir, una con WM5.

Yo no la desbloquee (unlock), aunque si te sirve de algo es una Qtek 9000 libre de fábrica (no es de ningún operador) así que no se si hacía falta hacerle algún tipo de unlock. Si había que hacerlo yo no lo hice y a lo mejor ahí está el fallo.

Pues bueno desde WM5 intenté instalarle la Tomal 8.9. Me sincronizó el ActiveSync, se reinició la PDA se puso en Bootloader y salió la barra del %, pero no llegó ni a ponerse a 1%, dio error de comunicación y a partir de ahí solo sale la pantalla del Bootloader.

He probado con "set 14 0" para que arranque el OS, pero como no tiene pues no hace nada, ya que le hice un "task 28 55aa" para reiniciar la DOC.

Ahora estoy intentando flashearle algun ROM pero es imposible, no pilla ninguna.

Estoy en BootLoader y pone "Serial" y abajo "v1.00". Le conecto el cable USB, el ordenador lo detecta y en la PDA cambia "Serial" por "USB". Entonces ejecuto la actualización, aparece la primera ventana, le doy a Next, se queda un rato chequeando y aparece la pantalla que te dice la ROM,RAdio,Ext que tienes y las que vas a flashear, pero a mi me salen todos los campos vacios (mira la primera imagen de abajo). Igualmente le doy a siguiente y se queda para siempre en la pantalla que dice "Checking the information on your device..." y no avanza al proceso de actualización. No queda otra que quitar el USB y entonces aparece un Error 150: ROM UPGRADE UTILITY ERROR. Aun con el USB quitado en la pantalla de la Universe sigue apareciendo "USB" en vez de "Serial", es decir, que el Universe se ha colgado y solo vuelve en si con un softreset. A lo mejor no puedo flashear porque el aparato se cuelga y por eso no continua con el proceso.

Abajo te adjunto el RUU.txt para ver si te dice algo

He probado con multitud de ROMs y nada, con todas pasa lo mismo.

Abajo te adjunto unas capturas de pantalla para que veas lo que me pasa exactamente.

Estoy completamente desesperada y necesito ayuda porque estoy segura de que esto se puede arreglar, tengo fe!!.

Muchísimas gracias por tu ayuda guapo!.

Un beso!,
Mary

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

IN ENGLISH

I didn't unlock the phone, coz is a brand-unlocked Qtek 9000, so I don't know if a unlock is needed (for a SuperCID por example). If an unlock before flash was needed perhaps that was the problem.

Here is what I did. From WM5 I tryed to install Tomal 8.9. ActiveSync detected my phone then I executed the ROM. PDA reboots to BootLoader and the % percent bar appears but on 0% program returns a Connection Error and till then the PDA is in BootLoader.

I tried with Mtty and "set 14 0" (to load OS after reset) but nothing happens because I use "task 28 55aa" to initialize DOC so not OS is installed.

I'm trying to install a ROM to recover the device but is impossible to make it work.

I will explain what I do to try to flash a new ROM:

In BootLoader mode (appears "Serial" on top and "v1.00" on bottom) I plug the USB to the computer (Windows XP SP3). "Serial" changes to "USB" then I run MaUpgradeUt_noID.exe (ROMUpgradeUt.exe doesn't work either). I click Next to begin update and after several seconds appears an empty summary window with no ROM, Radio and ExtROM (look first attached screenshot). Wherever, I click on Next but the program hangs on "Checking the information on your device..." forever, no matter how many minutes I wait (see the second screenshot). Then I need to remove the USB to cut the process giving error 150: ROM UPGRADE UTILITY ERROR. Without USB the device keeps saying "USB" (doesn't change to "Serial" when I remove the wire) then a softreset is needed. Perhaps the device hang while updating so I cannot flash?.

I tryed with lot of ROMs and none worked.

Below I paste the RUU.txt. Perhaps it helps...

I'm so sad trying to repair the Universal but I'll never surrender.

Thank you very much for read.

A big kiss,
Mary

Screenshot 1:
http://i39.tinypic.com/m7ui54.jpg

Screenshot 2:
http://i41.tinypic.com/70gq6d.jpg


Hola

Claro me parece bien en español!
Pues de todo lo que reportas, veo lo siguiente:

1. Me parece muy extraño que en la imagen del rom update no te aparezca una imagen de la Universal, al contrario te sale la imagen de otro tipo de device, podría ser que no tengas el rom adecuado?. A mi siempre me aparece la imagen del Universal cuando cambio de rom.
2. Ahi en la Wiki se habla de un método para hacer unlock, tal vez sea bueno que lo hagas
3. Tambien se habla de un método MTTY el cual a mi me ha salvado varias veces cuando me atoro
4. También hace el Doc format que viene en la wiki ayuda, ya que en algunos rom es completamente necesario hacerlo antes de poder hacer upgrade.
5. Trata con el rom de Tomal 8.5, en el no es necesario realizar el Doc format

Espero ayuden mis comentarios, si no seguramente alguien más te podra dar más ayuda.

Besos,
--------------------------------------------------

Hello
From what you report, I see the following:
1. It seems to me very strange that in the image of the ROM update does not appear an image of the Universal, on the contrary leaves the image of another type of device, could be that you do not have the suitable ROM. always it appears to me the image of the Universal when change of ROM.
2. in the Wiki it is spoken of a method to do unlock, is good to do it
3. Also it is spoken of a method MTTY which has saved me several times when I had problems
4. Also you can do the Doc format that comes in wiki, since in some ROM it is completely necessary to do it before being able to do upgrade.
5. try to flash the ROM of Tomal 8,5, in it is not necessary to realise the Doc format
Hope this helps, if not surely somebody else can give more aid more
. Kisses,

[Leviata]

Hola

Claro me parece bien en español!
Pues de todo lo que reportas, veo lo siguiente:

1. Me parece muy extraño que en la imagen del rom update no te aparezca una imagen de la Universal, al contrario te sale la imagen de otro tipo de device, podría ser que no tengas el rom adecuado?. A mi siempre me aparece la imagen del Universal cuando cambio de rom.
2. Ahi en la Wiki se habla de un método para hacer unlock, tal vez sea bueno que lo hagas
3. Tambien se habla de un método MTTY el cual a mi me ha salvado varias veces cuando me atoro
4. También hace el Doc format que viene en la wiki ayuda, ya que en algunos rom es completamente necesario hacerlo antes de poder hacer upgrade.
5. Trata con el rom de Tomal 8.5, en el no es necesario realizar el Doc format

Espero ayuden mis comentarios, si no seguramente alguien más te podra dar más ayuda.

Besos,
--------------------------------------------------

Hello
From what you report, I see the following:
1. It seems to me very strange that in the image of the ROM update does not appear an image of the Universal, on the contrary leaves the image of another type of device, could be that you do not have the suitable ROM. always it appears to me the image of the Universal when change of ROM.
2. in the Wiki it is spoken of a method to do unlock, is good to do it
3. Also it is spoken of a method MTTY which has saved me several times when I had problems
4. Also you can do the Doc format that comes in wiki, since in some ROM it is completely necessary to do it before being able to do upgrade.
5. try to flash the ROM of Tomal 8,5, in it is not necessary to realise the Doc format
Hope this helps, if not surely somebody else can give more aid more
. Kisses,

Thank u very much for asnwer me but I tryed all and nothing seems to work.

I assume my Universal is bricked. I will try to send it to HTC Tech Service, perhaps they can solve the problem for a cheap price (I hope).

Kisses,
Mary

[orb3000]

Thank u very much for asnwer me but I tryed all and nothing seems to work.

I assume my Universal is bricked. I will try to send it to HTC Tech Service, perhaps they can solve the problem for a cheap price (I hope).

Kisses,
Mary

Try to wait a few days, perhaps another member can help you before taking it to HTC tech serv.

Good luck Mary,

[Leviata]

Try to wait a few days, perhaps another member can help you before taking it to HTC tech serv.

Good luck Mary,

This forum (HTC Universal) seems to be desert of people because this device is too old, so I don't think that somebody will come here to help me. Anyway, I'll wait a few days more!.

Thank you very much for your help dear.

Un beso guapo!,
Mary

[orb3000]

This forum (HTC Universal) seems to be desert of people because this device is too old, so I don't think that somebody will come here to help me. Anyway, I'll wait a few days more!.

Thank you very much for your help dear.

Un beso guapo!,
Mary

There are plenty of active users!
you´ll see! :)

Besos,

[Leviata]

There are plenty of active users!
you´ll see! :)

Besos,

Ok Orb!!, if u say it then I believe you!.

Thanks for your support my friend!

[Yordan_Radev]

I have the same problem.After stucking on boot loader it turned off and now does not turn on.no mutty is helping..no nothing.....the phones does not want to charge even.....this is the real problem if we are able to turn it to some mode like bootloader or something we can fix it but when everything is offf what to do?????

Cheers

[da1deycallzean]

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 attempted to upgrade my exec it failed and now im stuck with the serial/usb screen. i have been told to use the uni exitbootloader download. when i try it my pc doesn't recognize the device. i have un checked the usb connection in my antivsync. i only had my phone for 2 days now i hear a lot of ways to get it back and running but im stuck.

[-Jonny-]

If your pc is complaining 'device unecogised', then have you tried rebooting your PC? This usually works for me.

[da1deycallzean]

I restarted my cpu still getting the same message my device has malfunctioned and pc cant recognize it. i need a step by step for dummies solution im not tech savy but have a general idea. what does device look like once its in bootloader mode? how do i even get it to that mode without my pc recognizing my device. Any help wld b a positive step.

thanks in advance

[da1deycallzean]

Rebooting my pc didnt work either. im very frustrated been searching for sum time now for a clear answer. i dwnloaded the mitty thingy but dnt get the option to select usb. i seen somewhere where u have to go into task manager and stop sum programs to get the usb option i tried to stop them and it wld not let me. Is my problem the fact my pc is running on vista? :confused:

[tomal]

Rebooting my pc didnt work either. im very frustrated been searching for sum time now for a clear answer. i dwnloaded the mitty thingy but dnt get the option to select usb. i seen somewhere where u have to go into task manager and stop sum programs to get the usb option i tried to stop them and it wld not let me. Is my problem the fact my pc is running on vista? :confused:
vista is not suggested for a newbie user!
try an xp computer

[da1deycallzean]

so there is no way i can use vista to get my phone back online? i read the wiki an it says i can flash it running vista will that get it restarted?

[da1deycallzean]

how do i get my phone out of smartphone mode and into bootloader mode on a vista? i believe thts where my issues lies????

any ideas are appreciated

[-Jonny-]

I restarted my cpu still getting the same message my device has malfunctioned and pc cant recognize it. i need a step by step for dummies solution im not tech savy but have a general idea. what does device look like once its in bootloader mode? how do i even get it to that mode without my pc recognizing my device. Any help wld b a positive step.

thanks in advance
step 13 in wiki here (http://wiki.xda-developers.com/index.php?pagename=Uni_ROM_Upgrade)

[-Jonny-]

As i know, I can't install a Tomal WM6.1 o WM6.5 because my device is locked. In fact, I broke my device trying to flash Tormal 8.9 directly from WM5.0.

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 (http://wiki.xda-developers.com/index.php?pagename=Uni_ROM_Upgrade)
HTC_Uni_SIM_Unlock_v1.rar download here (ftp://xda:xda@ftp.xda-developers.com/Universal/Tools_and_Programs/HTC_Uni_SIM_Unlock_v1.rar)

[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

[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?

[-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).

[da1deycallzean]

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!!

[Erikih]

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:

[umair muddassir]

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

[orb3000]

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,

[bahrom]

how do you do it when you have a vista with no active sync?

[onesolution]

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.

[orb3000]

Welcome to forums

Glad to see it worked for you
As you can see all is question of reading and searching

Now enjoy!

[allen501]

where can I download the MTTY 1.4 and can it work on HTC touch dual niki100.

[orb3000]

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

Visit touch section

Good luck,

where can I download the MTTY 1.4 and can it work on HTC touch dual niki100.

wrong section!

[yousaf2k]

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.

[XDA_LEON]

problem solved