Database Info

error 112 -- please help

can somebody help me update my t-Mobile XDA? i messed up my phone once already and know i keep getting error 112 during first step in update. CE Erase fails according to the log. Something is clearly locked, but I don't know what i am doing wrong or forgetting. I don't think t-mobile will restore my phone a second time. please help. I have tried diamondv1.2, wm2005, wm2003se, nothing seems to work.
UPDATE: sorry wrong categorie

not sure if that last big is a signature or a real confusement if so then
you cant use rom from one device on another so i would make pretty damm sure which device i had before trying to flash in worst case you can ruin the device 100%

i checked the requirements, so that should be ok. i just keep getting that same error 112, like something is locked. i haven't been able to find out what the error means. any tips?
and the update software i used checks if the device is right...
perhaps some more details:
if i connect it to my charger it will say serial, unless i pull the plug out a bit, then it will say usb.
if i connect to my pc via usb it will say usb v1.00, but after a while this will disappear and the RED light will go on
I have tried flashing it, but since activesync does not see it as a pocketpc anymore, i can't flash.
i have read a 100 posts by now, but i have not found any solutions.

Universal Dead

Hi
My Uni is dead, dont enter in bootloader mode, dont upgrade, dont do nothing.
Please help me, i dont know what happen.

You have to give us more clue. What were you doing with the Universal before this happened? Were you in the process of upgrading, downloading, etc...?

cktlcmd said:
You have to give us more clue. What were you doing with the Universal before this happened? Were you in the process of upgrading, downloading, etc...?
Click to expand...
Click to collapse
I upgrade with Vista. Dont work nothing.

Solution..
Hey i had the same problem... the Screen will say Serial no. and at the bottom it will say V. 1.01
Just do one thing.... connect yr fone to a desktop with Xp and then try running the upgrader... make sure u have the Sync software with u.....
I know this because the same thing happened with me.. my fone was dead.. till i did this..
try it

danidabest said:
Hey i had the same problem... the Screen will say Serial no. and at the bottom it will say V. 1.01
Just do one thing.... connect yr fone to a desktop with Xp and then try running the upgrader... make sure u have the Sync software with u.....
I know this because the same thing happened with me.. my fone was dead.. till i did this..
try it
Click to expand...
Click to collapse
My problem is the screen dont have nothing, any letters ou numbers.
having constantly the 150 connection error message

hellonasty said:
My problem is the screen dont have nothing, any letters ou numbers.
having constantly the 150 connection error message
Click to expand...
Click to collapse
Have you tried the suggestion at least?
Look for the original ROM of your device and find a WINDOWS XP computer and try to reflash with those 2 as suggested from above.

i want Try Mamaich Method but dont recognize the usb port.
Do you know?
Thanks

hellonasty said:
i want Try Mamaich Method but dont recognize the usb port.
Do you know?
Thanks
Click to expand...
Click to collapse
I don't think it would work. The Mamaich method is for a different problem. Yours clearly is due to Windows Vista incompatibility. I had read a couple of this type of thread in the past and the only solution was already given to you.

do you know where is the original rom?

hellonasty said:
do you know where is the original rom?
Click to expand...
Click to collapse
What type of Universal do you have? TMobile, O2, IMate...etc?

Sorry
I have a qtek9000

Before I tried my 1st upgrade I download the official ROM just in case.
I thought I had it but I can't find it. I have one copy on the PC at work, but I will only return there next Wednesday, so no big help.
I remember see a post were a member informed that he had an ftp with all the ROMS. Maybe some one remember the address. If I get, it i will post it.
Cheers.

Here: http://forum.xda-developers.com/showthread.php?t=296651&highlight=official+qtek+rom
Take a look into this thread at POST #7 by nvatvani
---

cktlcmd said:
Here: ftp://ftp.xda-developers.com/Universal/Uni_AKU2_WWE/QTEK_9000/
---
Click to expand...
Click to collapse
Am I wrong or those are the files that have been deleted because M$ "request"?

ultravox said:
Am I wrong or those are the files that have been deleted because M$ "request"?
Click to expand...
Click to collapse
OOOOPPPPs. that was the wrong dead link. But I corrected it already.

dead xda
i was trying to upgrade rom downloaded from o2 for my xda 2i i have same problem as previous guy i have tried to load from windows xp machine but get connection error 101 my screen is blank apart from usb and v1.01 can anyone help?

sounds to me like it might be as simple as a dead battery.
1. what happens when you try to charge it with the wall charger?
2. have you tried switching batteries?
3. you still haven't said what you were doing with the device before this happend
4. this is totally unrelated to WM6 Forum, you shouldn't have posted this here

when you put your universal on usb with a pc on xp there is a detection? or not and are you sur that there isn t any write on the screen .
because i have the same pb in 2006 an ithink that my universal is dead an aftrer 2 day i put the universal on the light and i see v101 if you don t see to the light you don t see it because the backlight don t work.
in this case the led for the charging don t work to.
if you have this there is a solution with a free operator rom i think it s on my pc.if you need tell me

sudf said:
when you put your universal on usb with a pc on xp there is a detection? or not and are you sur that there isn t any write on the screen .
because i have the same pb in 2006 an ithink that my universal is dead an aftrer 2 day i put the universal on the light and i see v101 if you don t see to the light you don t see it because the backlight don t work.
in this case the led for the charging don t work to.
if you have this there is a solution with a free operator rom i think it s on my pc.if you need tell me
Click to expand...
Click to collapse
Thanks
It do not enter boot loader with light + power + reset and show no signs of life.
The light is off.when i push reset button flash the red light.
When connected to USB, PC reports "USB device not recognised"
I want a original rom for qtek9000 for test.
Anybody have this rom?

When I bricked my XDA Exec by means of hung program during the upgrade, I had: no reaction to normal Reset, no entry to Bootloader - basically a brick.
I did LeftSoftKey + RightSoftKey + Reset to do a *hard* reset (everything was lost anyway), and after that I could see "Serial... v1.01" Bootloader notification. When you connected that to a computer, it changed to "USB... v1.01" prompt.
So I just took JWright's image, and re-flashed it.
Guess what? It detected I had no image/extRom/RadioRom whatsoever then offered to re-flash them. I knew I'm OK when Radio upgrade progress indicator started to move.
It took me to get to another machine first, however. My Vista machine totally screwed up things, whereas my home XP managed to do the job.
Sitting on JWright's 2.02.02 now - very thoroughly made ROM, love Voice Command integrated with it instead of crappy Cyberon's software.

Help! bricked Kaiser

Hi. There is something wrong with my phone. When i tried make phone call. It stopped responding. After reset it goes to four color screen with serial word on the bottom. I never flashed this mobile. Now when I try connect to vista it shows massage Usb device Not recognized, same on xp, but serial changes to usb. Please Help

first of all, i'm not an expert
but there are some threads in this forum about it. the only thing i can explain is:
that you're stuck in the bootloader,
the usb vs serial thingie, is that vista makes any usb device like a serial one..
try checking the spl threads and 'stuck' keywords
sorry can't be of more assitance...
anduh, keep calm and relax.. there's a lot of knowledge here.
so keep breathing and don't go paranoid..
gl
you might want to provide us with some more info,
rom version?, if it sais anything more in the RGB screen
and 1 more thing.. tried removing the battery for at least 1 minute.. / removing sd / simcard

on boot screen i have:
KAIS130
SPL-1.81.0000
CPLD-8
r
emoved sim and memory card
removed battery for 30 minutes.
no change.

podhal said:
on boot screen i have:
KAIS130
SPL-1.81.0000
CPLD-8
r
emoved sim and memory card
removed battery for 30 minutes.
no change.
Click to expand...
Click to collapse
hi podhal,
1) go to settings of activesync and uncheck 'allow USB connections'
2) or just to make sure, go to task manager and kill the process 'rapimgr.exe' and 'wcescomm.exe'
3) download mtty from here: http://forum.xda-developers.com/attachment.php?attachmentid=71806&d=1203597568
4) connect your cable to your kaiser-- it should say 'USB' and not 'Serial' at the bottom
5) choose 'USB' in the drop down list of ports and click 'OK'
6) on the mtty screen press enter key and you should get a cmd>
7) type in 'boot' (without the quotes) and press enter. If it doesn't boot up, paste the output here. DO NOT EXPERIMENT WITH MTTY AND TYPE ANY OTHER THING AS THIS CAN MAKE YOUR PROBLEMS WORSE.
EDIT: do this on you xp machine and not on vista!

HA! Problem solved! something had to be stuck in Usb connector. I just cleaned it with a bit of alcohol. Its a bit odd it went to boot loader just because of usb problem. But thanks for help.

podhal said:
HA! Problem solved! something had to be stuck in Usb connector. I just cleaned it with a bit of alcohol. Its a bit odd it went to boot loader just because of usb problem. But thanks for help.
Click to expand...
Click to collapse
good for you now read and go inside the wonderful world of flashing ROMs, heheh

What you are saying is really interesting. I´m one of the various kaiser users expriencing such problem.
I already did everything you can think of, nothing solved the problem so far. The only thing I didn´t try yet was to completely wipe the kaiser and use frankenkaiser.
Are you sure the problem is solved for you ?!?

StealthNet said:
What you are saying is really interesting. I´m one of the various kaiser users expriencing such problem.
I already did everything you can think of, nothing solved the problem so far. The only thing I didn´t try yet was to completely wipe the kaiser and use frankenkaiser.
Are you sure the problem is solved for you ?!?
Click to expand...
Click to collapse
Try the frankenkaiser then It's pretty *safe* if you know what you're doing-- did it 3-4 times because I was trying to wipe out bad blocks. Make sure you have the right radio though and an old hardspl before you use it jocky patched the new spls to ignore task 2a command.

pfcsabre,
Did you mean that by wiping the kaiser out with the pre-frankenkaiser commands (task 2a or rtask a) the phone is formatted and the bad blocks are mapped out ?
I really think that my problem is exactly that: a bad block within bootloader area...

StealthNet said:
pfcsabre,
Did you mean that by wiping the kaiser out with the pre-frankenkaiser commands (task 2a or rtask a) the phone is formatted and the bad blocks are mapped out ?
I really think that my problem is exactly that: a bad block within bootloader area...
Click to expand...
Click to collapse
well I had 3 bad blocks before, but the problem that I had is my ROM area is writing to that blocks and what's unlucky is the critical parts of the ROM is written there (bad blocks are common, but of all the places.. sheesh) that makes my kaiser just reboot indefinitely. So-- what I did was task 2a and it removed only one, but it was enough to get me flashing flawlessly to any ROM

Nice to know!
Well, since I haven´t frankenkaised my kaiser before, I have a last question:
According to the documented procedure in this thread, there is no task 2a command, instead, in step 2, it is said to issue an rtask a.
Am I right to assume that, if I task 2a my kaiser, I´ll have to pick up from step 3 and on ?
tia!

StealthNet said:
Nice to know!
Well, since I haven´t frankenkaised my kaiser before, I have a last question:
According to the documented procedure in this thread, there is no task 2a command, instead, in step 2, it is said to issue an rtask a.
Am I right to assume that, if I task 2a my kaiser, I´ll have to pick up from step 3 and on ?
tia!
Click to expand...
Click to collapse
there is in step 3 task 2a which completely *bricks* the phone. But as it said, you would go through oemsbl which is the radio bootloader and not the spl (os bootloader) anymore since it's wiped out already. Read the whole thread before doing it, it's not for the faint-hearted

StealthNet said:
Nice to know!
Am I right to assume that, if I task 2a my kaiser, I´ll have to pick up from step 3 and on ?
tia!
Click to expand...
Click to collapse
spot on but you need to make sure the drivers are there. After task 2a it would detect your kaiser as new hardware etc., so you need to still install the qualcomm drivers from that thread.

Thanks for the help! I have a XP machine set up just to do that
Ok, let´s do it.

pfcsabre, maybe you can help me.
I'm stuck at step 6. I successfully ran frankenkaiser. It asks me to replug the USB cable, and that's when things go wrong. In fact, when I remove the USB cable, the drivers are gone and phone is not recognized anymore when I plug it back (windows says the device is not recognized).
What am I doing wrong ??

StealthNet said:
pfcsabre, maybe you can help me.
I'm stuck at step 6. I successfully ran frankenkaiser. It asks me to replug the USB cable, and that's when things go wrong. In fact, when I remove the USB cable, the drivers are gone and phone is not recognized anymore when I plug it back (windows says the device is not recognized).
What am I doing wrong ??
Click to expand...
Click to collapse
sorry mate, just saw your reply.
Maybe you're replugging it too fast, I had that problem also. It kinda takes time before you get it but you're right on track if you ran step 6 with the output
EDIT: I think I know what you did wrong.. I remember that problem before. Are you running the frankenkaiser unbricker radio from hell? if you don't have the radio 1.65.17.10 that won't work. You should ask jocky for the right frankenkaiser unbricker for your radio.

check you later StealthNet, it's 2am and I got to go work in 6 hours. Ta!

StealthNet said:
pfcsabre, maybe you can help me.
I'm stuck at step 6. I successfully ran frankenkaiser. It asks me to replug the USB cable, and that's when things go wrong. In fact, when I remove the USB cable, the drivers are gone and phone is not recognized anymore when I plug it back (windows says the device is not recognized).
What am I doing wrong ??
Click to expand...
Click to collapse
if it's not recognized, try installing active sync again "to load usb drivers", and try again

You incorrectly installed the drivers most likely.
But before you use Franken, you need to be sure you are using one compatible with your OEMSBL & Vboot version.
What was your last radio & rom version?

GSLEON,
I PMed Jocky and, unfortunately, I did it wrong. When I read the procedure to use Frankenkaiser, I mistakenly assumed that, since task 2a wipes out the phone, the radio version wouldn't matter.
In fact, Jocky explained to me that it really does, and that Frankenkaiser is tailored to be used with radio from hell only.
My last ROM and Radio version were the ones based on the latest Dutty's (radio 1.65.16.25).
My attempt to "task 2a" my phone was my last attempt trying to solve my colored brick (booting into bootloader everytime I turn on the phone). I think this is being caused by bad blocks into bootloader or radio area.
Hopefully, I'll be able to get out of the hard brick (task 2a) and it will solve my colored brick problem
In fact, if it does work, I think it will be usefull for lots of kaiser users (last time I accounted at least 4 ppl with the same problem).
Thanks for the help!

Kaiser Stuck at Bootloader (aka Tri Color or Red, Green, Blue Screen)? Solutions Here

Before someone comes and flames me for creating a new thread (*hide from DaveShaw*) let me explain:
I have created a Wiki page for users who are stuck at the SPL (a.k.a Bootloader, Tri-Colour screen etc.):
Kaiser_stuck_at_bootloader ​
This has helped out a number of users who have become stuck at the SPL but every day I see more and more users getting stuck and creating new thread, or going off topic in other threads.
What to do if you get stuck:
Read the Wiki Page and follow the advice: Kaiser_stuck_at_bootloader
If you have tried all the steps in the wiki and still have a problem, read the feedback from other users in this thread and any advice I give out in this thread.
If you are still having problems please post all the details you can about what you have done and what version ROM / Radio / SPL you are running in this thread.
Credits:
Everyone I credited in the Wiki page.
mrdo who followed my advice and donated.
P1Tater for stickying this thread.
cmonex who seems to teach me something each day.
Thanks
Dave

Nice thread. Worth a sticky since it seems to be happening quite frequently lately

P1Tater said:
Nice thread. Worth a sticky since it seems to be happening quite frequently lately
Click to expand...
Click to collapse
Thanks to much I have learned from Master Jocky_W, I am currently working on hacking o a couple of Jockey's new HardSPL's into MFG variations. This will allow for the checking, formatting & fixing of OS flash memory blocks.
I am just about done I think, & then off to Jock it will go for his comments & keen eye.

GSLEON3 said:
Thanks to much I have learned from Master Jocky_W, I am currently working on hacking o a couple of Jockey's new HardSPL's into MFG variations. This will allow for the checking, formatting & fixing of OS flash memory blocks.
I am just about done I think, & then off to Jock it will go for his comments & keen eye.
Click to expand...
Click to collapse
Nice one, I was thinking MFG 3.* HardSPL would be good, but I assumed there was a good reason for them not to exist. Little did I know that's where you were hiding
Great work.
Dave

Good idea with this thread, congratulations.
Just to add something useful for the thread, here is my tip: (for n00bs, or a "newbie-n00bs" since I consider myself a n00b too )
No matter what, DON'T PANIC.
If your phone boots at least partially (the bootloader starts and shows R/G/D versions) maybe its not that bad
I've flashed few times "bad ROMs" and my phone stucked on bootloader. Luckily none of them was that bad that I couldn't recover from it.
What I do first:
disconnect the phone from anything you had it connected to,
and go into bootloader mode (camera button + reset with stylus).
It will show the tricolor+white screen, SPL version on the top and "Serial" at the bottom.
Plug in your USB cable.
If the "Serial" will change into "USB" at the bottom, you are most likely ready to fix the problem
- so flash your phone with new clean ROM now (I would go with clean stock ROM including radio as well)
oh, and don't worry about the ActiveSync info that may be displayed by the RUU app, because you are already in bootloader mode (RUU or KaiserCustomRUU etc, at first disconnects AS in order to set your phone in bootloader mode, thats why the warnings about AS being "green" etc)
HTH

this one isn't covered!
I go right to bootlader and see RUUNBH upper right!
my SPL is 3.56.hard
CPLD-8
I would flash my stock rom BUT i cant get a usb connection to work at all!
mtty doen't work at all!
hmm?!?!?!??
HELP, please!

OrrinS1189 said:
I go right to bootlader and see RUUNBH upper right!
my SPL is 3.56.hard
CPLD-8
I would flash my stock rom BUT i cant get a usb connection to work at all!
mtty doen't work at all!
hmm?!?!?!??
HELP, please!
Click to expand...
Click to collapse
Does "USB" show in the bootloader when you connect the USB plug or not?
Dave

yep
yes, those words DO change. But nothing can be done on my PC.

OrrinS1189 said:
yes, those words DO change. But nothing can be done on my PC.
Click to expand...
Click to collapse
Have you done the following to get MTTY to work?
* Download mtty.exe
* Disable activesync (connection settings -> uncheck "allow usb connections")
* Connect your Kaiser to PC using USB cable.
* Open mtty, select USB port and click OK.
* Hit ENTER twice, you should see the "Cmd>" prompt.
* Type the command "boot".
Are you using Vista or XP?
Dave

yes again!
i have disabled usb connections through active synch and killed ALL the mobile processes through task mngr. Still, usb port cannot be opened through mtty!
it's crazy! =[
also, when i plug in my tilt, i get a beep beep beep from my PC saying failure to cconnect to hardware. =[
VISTA!!!

OrrinS1189 said:
i have disabled usb connections through active synch and killed ALL the mobile processes through task mngr. Still, usb port cannot be opened through mtty!
it's crazy! =[
also, when i plug in my tilt, i get a beep beep beep from my PC saying failure to cconnect to hardware. =[
VISTA!!!
Click to expand...
Click to collapse
I'm leaving work now, but can you trying flashing your carrier ROM from the SD card, that might do it.
Also, try the attached MTTY.
If that don't work, can you find a Windows XP Machince and try the normal MTTY method.
Dave

No Luck
Since I can't establish a usb connection I have no way of getting ANYTHING to my tilt.
I can't access my SD card.
MTTY says command error when I say boot.
I don't think MTTY is connecting.
Does my SPL need to be changed?
If so, how do I change it if I can't get a connection to my tilt at all?

I GOT IT!
i TOOK your advice to flash from my SD my naming a rom KAISIMG.nbh and using my PC to put on card. then i just entered bootlader. I flashed a random new rom (not at&t) and it worked in restoring my phone.
I didn't use a stock rom cause my spl didn't match. thanks for all your help man.

OrrinS1189 said:
i TOOK your advice to flash from my SD my naming a rom KAISIMG.nbh and using my PC to put on card. then i just entered bootlader. I flashed a random new rom (not at&t) and it worked in restoring my phone.
I didn't use a stock rom cause my spl didn't match. thanks for all your help man.
Click to expand...
Click to collapse
Glad you got it working.
Dave

good thread
BTW, if you do not have the RUUNBH on the screen, but can't get OS to boot and you didn't flash my patched SPL's for prevention, I now have a solution for those too in my thread (also sticky, so easy to find).

cmonex said:
good thread
BTW, if you do not have the RUUNBH on the screen, but can't get OS to boot and you didn't flash my patched SPL's for prevention, I now have a solution for those too in my thread (also sticky, so easy to find).
Click to expand...
Click to collapse
Thanks for this.
I have added this to the Wiki Page. Which I may re-write later to be a little more clear.
Dave

I have re-written most of the Wiki Page to be more than a collection of random Links. It took over an hour, to get right, so please read it.
Now there's really no reason to get stuck.
Thanks
Dave

DaveShaw said:
I have re-written most of the Wiki Page to be more than a collection of random Links. It took over an hour, to get right, so please read it.
Now there's really no reason to get stuck.
Thanks
Dave
Click to expand...
Click to collapse
nice update! really useful to all kaiser owners.
btw, you wrote:
"This method will not work if RUUNBH is showing and cannot get the OS to boot even once"
I removed second part if you don't mind, the method doesn't need that as a requirement. (and it will actually unset RUUNBH flag too if the loading of the special SSPL and the flash is successful, but for RUUNBH issue this solution is overkill, because for that "set 16 0" is fine.)

cmonex said:
nice update! really useful to all kaiser owners.
btw, you wrote:
"This method will not work if RUUNBH is showing and cannot get the OS to boot even once"
I removed second part if you don't mind, the method doesn't need that as a requirement. (and it will actually unset RUUNBH flag too if the loading of the special SSPL and the flash is successful, but for RUUNBH issue this solution is overkill, because for that "set 16 0" is fine.)
Click to expand...
Click to collapse
Thanks cmonex, I don't even know what that senence means, I wrote it after midnight last night, and I really can't recall what I was thinking.
Cheers
Dave

First, I’m using the ROM L26KDV12. I used the tweaking program that comes with the ROM and I hit done, the phone said to restart the device to get effective or cancel to restart later but I choose to restart the device. So, the Phone restarted and I stuck in bootloader mode.
I tried to re-flash my ROM L26KDV12 and I got the 100% result in the screen but when I restarted the device it was stuck again in bootloader mode. I tried to update the Radio but got no luck also.
So I decided to update the ROM via MicroSD(Dutty’s Diamond V1.9) and I got 100%(complete result on the screen again) but when I did the last instruction of updating the ROM via MicroSD(to restart the device), my phone goes off and I can’t open anymore..
Please I need help..

O2 XDA Exec Won't Power On after Unccessfull ROM Upgrade

Hi...
I was trying to Upgrade my O2 XDA Exec Rom with Windows Mobile 6.5 by explode. The process went successfully till 99% and after that it ended up with Error. Then I unplugged my pda from the pc and tried to restart the device. I was surprised that the device did not respond to any of the following
Soft Reset
Hard Rest
Boot Loader mode Start (Bulb + Power + Reset)
It is totally blank screen whatever you do.
When I connected the device to the pc with usb cable, a Red Light is shown for 2 seconds and then goes off and a message comes up on the pc that "USB DEVICE NOT RECOGNIZED".
Then I tried to Remove battery from the device for a whole night and the next day morning i did all the above procedures again to get no results.
Kindly Help me out
Thanks
Dinesh Kumaar

I think you have been bricked your device...

dineshkumaar said:
Hi...
I was trying to Upgrade my O2 XDA Exec Rom with Windows Mobile 6.5 by explode. The process went successfully till 99% and after that it ended up with Error. Then I unplugged my pda from the pc and tried to restart the device. I was surprised that the device did not respond to any of the following
Soft Reset
Hard Rest
Boot Loader mode Start (Bulb + Power + Reset)
It is totally blank screen whatever you do.
When I connected the device to the pc with usb cable, a Red Light is shown for 2 seconds and then goes off and a message comes up on the pc that "USB DEVICE NOT RECOGNIZED".
Then I tried to Remove battery from the device for a whole night and the next day morning i did all the above procedures again to get no results.
Kindly Help me out
Thanks
Dinesh Kumaar
Click to expand...
Click to collapse
if it's not recognized, remove the SIM card, the SD card, and on the PC open activesync and disable usb connections. for more info open this link
http://wiki.xda-developers.com/index.php?pagename=Uni_Stuck_Bootloader_Serial

what if the device is bricked
Thanks for your quick reply
Kindly let me know what could be done with the bricked device. Can it be repaired again.
Thanks again
Dinesh Kumaar

dineshkumaar said:
Thanks for your quick reply
Kindly let me know what could be done with the bricked device. Can it be repaired again.
Thanks again
Dinesh Kumaar
Click to expand...
Click to collapse
you have to find another rom and try to flash it to your PDA.
ARE YOU RUNNING windows XP on your PC?

Yes ! I have Windows XP SP2 and Active Sync Version 4.5.0 (Build 5096)
Thanks

dineshkumaar said:
Yes ! I have Windows XP SP2 and Active Sync Version 4.5.0 (Build 5096)
Thanks
Click to expand...
Click to collapse
have you tried to upgrade another ROM, and if you did, is your PDA now working?

I cannot update my rom as my pc cannot recognize my device. is there any other way to update rom?

dineshkumaar said:
I cannot update my rom as my pc cannot recognize my device. is there any other way to update rom?
Click to expand...
Click to collapse
Have you read here?
http://wiki.xda-developers.com/index.php?pagename=Uni_Stuck_Bootloader_Serial
Try to reflash with another ROM
Hope it helped
And don´t forget to vote!

I had already done those steps to get no results.
its my badluck.

If you cannot get into bootloader and you have done the steps above, then you cannot flash to another rom.......it would seem you now have a paperweight im afraid

I am still not able to revive my device. I know that it is just due to corrupt bootloader but don't know how to repair it.
If anybody ever has solution for this... kindly let me know.
Regards

Have you tested mtty?
I would recommend to PM a chef on Universal forum
Good luck,

Mtty is not detecting my device
it says can't open usb port

One More thing I have noted is that when I keep the device connected with the pc, at a certain interval of about 10-15 mintues my device's Led shows RED Light for few seconds and then turns off followed by the the "USB device not recognized" on my pc.
I hope this can be used as a hint towards reviving my device.
Regards

have you followed orbs advise above and pm a chef on that section, they maybe able to help. From my knowledge (limited on that device) i ddont think there is any recovery proceedure that you have not tried. Have u downloaded offical wm5 rom and tried it. I know and appreciate that it will probably not work due to corrupt bootloader, but what else is there to do??
To understand more, what did you do PRIOR to trying to flash to 6.5.
Did you hardspl correctly? Had you already flashed to another rom and just felt like flashing to another new rom?? Give us more detail.

Thanks for your reply
I dont know how to PM Chef.
I had used 3 other Rom versions of WM6.1 on my device. They ran very much fine on my device. But When i found WM6.5 xplode, I wished to try that too. But the rom update procedure went successfully till 99% and after that it showed an error that upgrade was not successfull. I pulled out the device and tried to restart if by all methods but I wasnt able to power on at all.
Thanks
Regards

ok, goto the thread that you got the rom off, click the chefs name and you will get a menu there to send pm, do it, he might have seen a similar problem or know how to correct bootloader.
good luck

noup really no...
Is bricked
my bro has bricked an Universal and the same led turns red no power off no bootloar no power it means the flash chip is dead!
Sorry to heard that.
He waits too long for the upgrade it tooks at least 40 minutes
then ERROR... but you know... the batt was died in middle process ( th batt was ****ed up, it say full charged but no! it was on 60 or 50%) then the stupid thing is make a hardreset.. i told him dont hR your device... justa simple reste and reinit the process... and huh! its bricked.
if you are interested on sell your parts
maybe my bro want some parts.

my advice(similar to other people):
1. Charge your batery somehow (in other device or anything else)
2. put your devce in bootloader mode and connect it to pc - it wll be detected like microsoft usb sync
3. use mtty try difrend versions becuse sometimes 1.42 does not detect it properly - read here for what to do with mtty
IMO this may be battery problem or nand chip problem - in both cases it is hardware fail