Well, I'll start from the beginning.
Yesterday I installed wmwifirouter 1.20 trial on my Uni, it worked great, when I finished using it I shut it down normally and all was perfectly fine. I'm not blaming wmwifirouter here, but I feel I must point it out as it was the last piece of software I installed.
I packed up my Uni, put it back in its slip case and started driving home. When I got home, I opened up the lid and it was dead. Fine I thought, battery was flat. So I charged it overnight (I have to use an external charger as my Uni's USB port broke off) and put the battery in this morning, Uni asks for initial Windows Mobile setup, WTF?
I panic, and I press the RESET button hoping that it will clear this problem and my Uni will work fine. Now it is stuck on the boot image, O2 logo with red text that says the following:
Code:
PU10 64Mb RAM
ROM image built:
Dec 31 2006
19:42:34
R 1.04.02
G 42.37.P8
D 2.01.06 WWE
I tried a hard reset (holding down both soft keys and pressing RESET, and then pressing zero key to initiate wipe), but it still doesn't get past the boot image..
Now, considering that my USB port is broken, is there any way to fix my Uni?
I have a 2GB SD card, and a 1GB MicroSD card with SD adapter, if this can help somehow?
try push light+power+reset and Yours uni should run i boot mode
read wiki - U'll find all solutions
FabianD said:
try push light+power+reset and Yours uni should run i boot mode
read wiki - U'll find all solutions
Click to expand...
Click to collapse
If I do that, I get the ROM flashing option, but that doesn't help me because I don't have a working USB port on my Uni
*BUMP* I need help with this please, I've not had a working Uni for days
Related
I've had my Qtek 9000 for a week. I've spent most of that week installing software, and getting it setup (using a lot of useful info from this site).
This afternoon it locked up, and wouldn't respond to any button presses (including the on/off button)
Soft resets result in it powering backon, but stopping at the boot screen, after displaying the ROM versions in red text.
Eventually, I tried a hard-reset. Same thing happens - process goes ok until it displays the ROM version, when it just sits there. I've tried removing the SD card and SIM card and hard-resetting. No Joy.
I had just installed OzVGA, and was testing it when this occurred, but that is probably just a coincidence (surely a hardreset should fix anything bad that happened there?)
I hadn't at any point played with the ROM.
What should I try next?
And, does anyone know if I'm going to be able to get support for this in the US from Qtek? (I bought it in the UK), new
Thanks in advance.
-Steve
RE
Have you try taking out the battery, leave it for a while, put back the battery and do a hard reset?
It may work
Re: RE
FOSA said:
Have you try taking out the battery, leave it for a while, put back the battery and do a hard reset?
It may work
Click to expand...
Click to collapse
Unfortunately, no such luck
I'd tried that before, but the battery was only out for a short time. This time it was been out for at least 15 minutes.
Does anyone know if there's any kind of hardware or diagnostic test mode it can be booted into?
-Steve
How about updating/upgrading thr ROM?
This might work. you'll have to reinstall everything again, though
Jorgee said:
How about updating/upgrading thr ROM?
This might work. you'll have to reinstall everything again, though
Click to expand...
Click to collapse
Thanks - I may try that tomorrow. However, I'm a little concerned that updating it with a new ROM might invalidate the warranty (especially if it's not a QTEK ROM)
I was hoping that there was some kind of hidden 'diagnostic mode' I could try first, before taking that step. I've also been looking everywhere on the web, and I can't find anyone else that this has happened to. This makes me think it may be a hardware problem, though the way it just 'happened' seems more like s/ware.
Anyway, I'm out today so this will have to wait until tomorrow. My biggest concern at the moment is how I'm going to get any warranty support in the US. All I have at the moment is a very expensive brick!
-Steve
Have you tried entering bootloader mode?
BACKLIGHT BUTTON + POWER BUTTON + RESET HOLE
Then the screen will go blank then show the words SERIAL but you have to look real good because the backlight will be off when the serial is displayed. If it does go there, try hard resetting from there:
__ + __ + RESET HOLE
Hope this helps. WHat's your ROM verison/language anyway?
Jorgee said:
Have you tried entering bootloader mode?
BACKLIGHT BUTTON + POWER BUTTON + RESET HOLE
Then the screen will go blank then show the words SERIAL but you have to look real good because the backlight will be off when the serial is displayed. If it does go there, try hard resetting from there:
__ + __ + RESET HOLE
Hope this helps. WHat's your ROM verison/language anyway?
Click to expand...
Click to collapse
Thanks - but no improvement. I do get the 'serial' screen (with v1.00 displayed at the bottom), but when I do _+_+reset from there, it just goes back to the 'normal' Qtek boot screen and sits there.
Unfortunately, not having access to the OS, I don't know exactly the ROM versions etc. However, the info displayed in red text on the Qtek boot screen (where it hangs) is as follows. How do you interpret this?
R 1.03.00
G 42.36.P8
D 1.13.64 WWE
Thanks for your help - I'm hoping I can get this resolved without having to find out how to get support from Qtek!
-Steve
thefixer said:
Jorgee said:
Have you tried entering bootloader mode?
BACKLIGHT BUTTON + POWER BUTTON + RESET HOLE
Then the screen will go blank then show the words SERIAL but you have to look real good because the backlight will be off when the serial is displayed. If it does go there, try hard resetting from there:
__ + __ + RESET HOLE
Hope this helps. WHat's your ROM verison/language anyway?
Click to expand...
Click to collapse
Thanks - but no improvement. I do get the 'serial' screen (with v1.00 displayed at the bottom), but when I do _+_+reset from there, it just goes back to the 'normal' Qtek boot screen and sits there.
Unfortunately, not having access to the OS, I don't know exactly the ROM versions etc. However, the info displayed in red text on the Qtek boot screen (where it hangs) is as follows. How do you interpret this?
R 1.03.00
G 42.36.P8
D 1.13.64 WWE
Thanks for your help - I'm hoping I can get this resolved without having to find out how to get support from Qtek!
-Steve
Click to expand...
Click to collapse
You have a WWE (English QTEK ROM) but since you cannot enter bootloader mode, I don't think you will be able to update. You might have to return your device to where you bought it
Jorgee said:
You have a WWE (English QTEK ROM) but since you cannot enter bootloader mode, I don't think you will be able to update. You might have to return your device to where you bought it
Click to expand...
Click to collapse
Jorgee,
I notice (in the HTC 'confidential' manual I just downloaded) that there is a diagnostic program. Apparently, I put it on an SD card, and do Power+Backlight+reset to invoke it.
Do you know if that diagnostic tool is available anywhere on here, or elsewhere on the web?
Also - I wqas trying to find exactly how to enter 'bootloader' mode (after I have the 'serial' screen). Should it boot differently from here when doing a hware reset (_+_+reset)?
Regards
Steve
Actually, when you see SERIAL, that means you are already in bootloader mode. One question, what ROM do you wanna update to? QTEK, IMATE, MDA, O2?
Do the following once you get the SERIAL ON THE SCREEN:
1. Open active SYNC, then choose FILE>CONNECTION SETTINGS, then remove the check on the USB option.
2. Connect the phone to the computer with the sync cable. This should change the SERIAL on the device to say USB.
3. Run the ROM Upgrade (whichever it is you chose).
This shoulod update your device. If you are able to enter bootloader mode (SERIAL) this means that probably your ROM (OS) is damaged. Just update it even to the same verison then it should work.
If you get Country ID error while trying to update or any other error, just inform me, i'll walk you through the process.
Jorgee said:
Actually, when you see SERIAL, that means you are already in bootloader mode. One question, what ROM do you wanna update to? QTEK, IMATE, MDA, O2?
Do the following once you get the SERIAL ON THE SCREEN:
1. Open active SYNC, then choose FILE>CONNECTION SETTINGS, then remove the check on the USB option.
2. Connect the phone to the computer with the sync cable. This should change the SERIAL on the device to say USB.
3. Run the ROM Upgrade (whichever it is you chose).
This shoulod update your device. If you are able to enter bootloader mode (SERIAL) this means that probably your ROM (OS) is damaged. Just update it even to the same verison then it should work.
If you get Country ID error while trying to update or any other error, just inform me, i'll walk you through the process.
Click to expand...
Click to collapse
Hi Jorgee,
I'd prefer to go for the QTEK Rom (I'm assuming, from the info I posted above that I currently have 1.13.64 WWE). I'd like to go for the same or later version of this, but looking on the ftp site here I can't see ay QTEK ROM upgraders.
I have checked that when I plug in the USB I get 'USB' appearing on the screen, so I'm hoping that a ROM upgrade will at least work, even if it doesn't fix my problem.
One other thing that concerns me. When I plug into USB (with either a PC or the AC charger) the LEDs aren't lighting to indicate it's charging. Obviously, when during the flash upgrade I should make sure I have a reasonably charged battery. However, I don't know if I do (or even if it's currently charging).
-Steve
I guess leave it charged using the AC adapter for an hours, then here's the QTEK ROM.
ftp://xdaupload:[email protected]/Universal
Under Shipped ROM's you should see the QTEK.
If you cannot find it, tell me, ill send it to you. Trying to avoid this because it is almost 60MB in size
Jorgee said:
I guess leave it charged using the AC adapter for an hours, then here's the QTEK ROM.
ftp://xdaupload:[email protected]/Universal
Under Shipped ROM's you should see the QTEK.
If you cannot find it, tell me, ill send it to you. Trying to avoid this because it is almost 60MB in size
Click to expand...
Click to collapse
Thanks - I'd already found it on the devbuzz site, and am currently giving the unit an hour or two's charge before trying this. Wish me luck!!
-Steve
OK, here's what happened when I tried to update with the same Qtek firmware:
Initial dialog (that shows old and new (to be installed) firmware versions had blanks for all three firmware versions currently installed.
Started the upgrade, and left it running (couldn't bear the tension of watching!). Came back, and found the following error message displayed:
"Error 113: Extended ROM Update Error"
The update tool indicated that I should 'try again'. I'm currently re-charging the unit, and hoping (against hope) that this error was caused by insufficent battery charge.
-Steve
Okay, but maybe it just didn't update the extended ROM but the OS rom has been updated properly. After this error, try the __ + __ + reset button and see if it does boot fine.
Jorgee said:
Okay, but maybe it just didn't update the extended ROM but the OS rom has been updated properly. After this error, try the __ + __ + reset button and see if it does boot fine.
Click to expand...
Click to collapse
No luck.
I've also tried re-flashing a second time, but this time I watched it to see what happens
As the radio firmware is flashing, a message to that effect is shown on the Qtek screen. Once that is finished, the upgrade tool starts the extended ROM flash. At that time the Qtek's screen goes completely blank. The, after a minute or two, the upgrade tool reports that the extended ROM failed to upgrade.
I am assuming that normally, while flashing the extended ROM, there's a message on the phone's screen to say what's going on?
I'm also wondering whether to have a go at flashing the ROM in one of the other ways?
-Steve
I heard sometimes just flashing the Radio only might work.... Then after that you can flash the rest. Just extract the contents of the ROM to a directory. Take note of the ff:
Radio : radio_.nbf
OS : nk_.nbf
Ext : ms_.nbf
I just rename/move/delete the MS and NK files then run the update
Jorgee said:
I heard sometimes just flashing the Radio only might work.... Then after that you can flash the rest. Just extract the contents of the ROM to a directory. Take note of the ff:
Radio : radio_.nbf
OS : nk_.nbf
Ext : ms_.nbf
I just rename/move/delete the MS and NK files then run the update
Click to expand...
Click to collapse
Thanks Jorgee. Still no real success, but I think I might be getting closer.
I've tried the above (using both the original romupdate_ut.exe and MaUpgradeUt_noID.exe - same results with both).
I've tried each of the three files individually (using the ones from the shipped ROM, as downloaded above)
radio_.nbf always seems to flash ok
ms_.nbf always fails right at the start, and nothing appears on the phone's screen
nk.nbf almost worked. It started, and got up to 87% (tried this 3 times), with the update showing on both the phone screen and PC. Then it failed with error 112, leaving the '87% complete' message on the phone's screen.
Soft or hard reboots still result in us just ending up 'hung' at the boot screen.
Once again, thanks for your help so far. However, I am beginning to give up hope!
-Steve
I have the same problem with my Dopod 900 at post http://forum.xda-developers.com/viewtopic.php?p=207524#207524
But mine is no problem with EXTRom Upgrade
Waiting for your advise!
Thanks
truongia said:
I have the same problem with my Dopod 900 at post http://forum.xda-developers.com/viewtopic.php?p=207524#207524
But mine is no problem with EXTRom Upgrade
Waiting for your advise!
Thanks
Click to expand...
Click to collapse
I wish I had a solution!!! I've spent about 20 hours trying to get this thing to boot!
One question though - how did you get the 'boot option' menu up (allowing you to clear the registry etc). I might try that on mine (I had assumed that a hard reset ALWAYS cleared the registry.
Given that I was playing around with ozvga before this happened, there's a small chance that might help (though I think not; as I can't see how that would also stop the flash update working)
-Steve
Hi All,
I had this device for few months now after selling off my Eten X500.
The Universal was a big device but I truly loved the XGA big screen. And yesterday disaster struck. Normally sometimes the device would go haywire but a few soft resets or hardreset would set it back on course. But yesterday it refused to move on from the bootloader mode and when I used Buzz utility prgram, it did move away from the bootloader but didn't swith on anyway. And yes, I have flashed the ROM's quite a few times and I managed to flash it with T-Mobile's latest WM5 ROM today morning. The flash was successful but it just wont work normally.
I have 2 batteries but bith yieled the same result. I could only get it to switch on if I hardreset it on a table with 2 fingers firmly pusing the soft keys down. It would sometimes would boot but would hand after it fully loaded. I have removed the SD card as well as the SIM card. Not sure if the devie motherboard is having any issues or some connection problem. One thing for sure if I hold both edges of the device and press it hard and try a soft reset, it would boot sometimes. I even have the external battery charger and I can charger the batteries full.
Any idea how much would it cost (I'm in Singapore) for a repair or anyone who could help me with this.
The worst thing is, this is my only phone and I really need it to work asap.
Hope someone could shed some light on this.
Thank you all in advance.
Techx
Have a look at the wiki...
I had the same problem after I put it on charge with no battery in - very smart I know . It explains about using MTTY and how you format the DOC which should solve your problem - hopefully...
Hi all,
I tried the MTTY utility but I can format the DOC files. everytime I try to format it, I get an error like this :-
USB>set 14 0
HTCSF kEØ(HTCEUSB>task 28 55aa
Wait..
flFormatPhysicalDrive:status=20
Read data error in tag
DOC_format failed!
USB>
So anyone can help in this issue plssssssssssssssss
Thank you all.
Techx
anyone????
Anyone? pls help!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Do h3lp!!!!!!!!!!!!!!!!!!!!!!!
Anyway of getting the unit fixed? Anyone from Singapore can recommend a shop or anything?
Hi,
I tried to USPL my P4350 (SPL & IPL 4.xx.xxxx) in order to update to WM6.1, using Herald-USPL-Beta3. Everything went OK until ROMUpdateUtility kicked in, and gave me an error: FILE IN USE.
So I started the ROMUpdateUtility again, with the screen still blank, and suddenly the P4350 turned off. I'm 100% sure the battery was at least 90% full during USPL'ing, so why it turned off; I have no idea.
Problem is: I can't power up the device anymore. No LED's, even when attaching it to the power adapter.
Any tips on how to fix this, or is it fair to say my device is now really DEAD?
Thanks!
Some suggestions of a Junior Member.
1st. Try a soft reset. Didn't work? Go to Step 2
2nd. Try a hard reset. Didn't work? Go to Step 3
3rd. Pull the battery off. Put it again. Try to turn it on. Didn't work? Go to Step 4
4rd. Wait replies from advanced user. End.
Thank you for replying
However none of the options you mentioned worked out.
I'm stuck waiting for some expert guidance here
Hi, it's been a while, but today I finally made -sure hope so- some progress..
I purchased a HTC Touch HD two weeks ago, from which I plugged in the power adaptor to see what my P4350 would do. (specs are the same btw as the P4350 power adaptor; output 5V, 1A) On this attempt however, the left LED on the front of the device turned RED for about 5 seconds before turning off again. I plugged in the adaptor again, and it lit up RED again. However, the device did not respond to an attempt to power it up.
What does this mean? Is it not dead after all?
Any tips on what to do?
Thanks again.
Wow man, I'm getting somewhere now!
I got the device powered on holding the RESET+POWER+CAMERA and it now hangs on the IPL + SPL screen.
What is very strange is the following:
IPL 1.08.0001
SPL 1.08.0001
as to where these were above 4.xx.xxxx before I did the USPL'ing. I am a 100% sure.. (not so sure anymore now to be honest.. )
The screen displays USB in the left bottom corner, because it is connected to the USB power supply.
I'm afraid to turn it off because it might not turn on again...
Where do I go from here?
Well, I finally got my P4350 to work again
I noticed I was able to start into bootloader mode using CAMERA+RESET, unlike previous attempts to do so. I don't know what caused the device to boot after 6 weeks, but I guess attaching the Touch HD power adapter did the trick.
At first I followed the instructions at topic "Goldcard for Herald", but somehow I wasn't able to make the MicroSD card bootable using my HTC Touch HD for the formatting.
Instead I went to page 5 of the topic and discovered this comment by leptir79, who stated the creation of the Goldcard could easily be done from a DOS-prompt in Windows, with the MicroSD card in the SD-cardreader on a PC or notebook. And this is what did the trick for me:
- I put the SD-card in my notebook cardreader (drive W: ), opened a DOS-prompt, and ran the following command to format the SD-card with the correct priviliges: FORMAT w: /FS:FAT32 /A:4096
- After that I copied heradiag.nbh to the blank MicroSD card to see if my P4350 would boot from the MicroSD card. And it did. From this tool I ran some diagnostics tools to see whether my device was fully functioning, and I got no errors. I noticed that among the diagnostics tools there was a tool to Flash the device with a new ROM
- So I downloaded HTC_P4350_WWE_4.17.405.2_4.1.13.44_02.94.90_Ship.exe, extracted RUU_signed.nbh to the root of my MicroSD card (along with heradiag.nbh), and renamed RUU_signed.nbh to heraimg.nbh.
- I started the P4350 into bootloader mode, booting from the MicroSD card. Heradiag.nbh booted up, and I chose to use the Flash ROM utility that came with heradiag. The device automatically found heraimg.nbh, and started the flashing procedure for my device. After confirming, the flashing started.
After a few minutes my P4350 rebooted, and my device is now running Windows Mobile 6.0. Everything seems to work just fine now.
So, if you don't have a second (working) WM device, but do have an cardreader on your PC or notebook, this really is the best option to create the Goldcard imho.. (even if you do have another WM-phone, really, try this procedure first before installing ActivePerl and all the perl-scripts)
Thanks everyone for all the procedures and help. You all did a great job, but most credits in this case go out to leptir79 who gave me the breakthrough in getting my -left for dead- device to work again.
This is a gold trick thats what i'm waiting for...
I have my heralds bricked since 2 months ago... Yup....really bricked...means cant do bootloader mode or hard reseting on device...
And already sent it to the HTC care center, and they ask for mainboard replacing...which is too expensive for me...400US...later cancelling it...
Searching out this forum, and didn't find a solution to reprogramming OMAP via JTAG...then my research suspended...
Untill I found this...
All I need...just to enter to the bootloader...powering up the brick
Can't wait to try this method @home...ASAP...
For now...just looking for 5V, 1A Charger first....
TIA frummel...
hera100
hie i have a hera100 does not detect on active sync when i try to update rom stops at 2% try diffrernt roms some stop at 7% my IPL 4.14.0002 SPL 4.10.000 i tried formating my 2gig and put heraimg on it nothing happens. pliz help how do i do it now phone shows three colors i cant hard spl coz of active sync. ithanx in advance
Attach phone to a computer with a mini-USB cable and install a RUU ROM.
alright.. i made a similar post to this before and i came across the wiki...
well i can't view what my SPL or my IPL because as soon as i turn the device on, all that shows is the boot loader screen and displays serial on the top with 0.16-0.90 in red characters on the bottom (I'm not sure what those are)...
here are the only details that i know about my phone:
I DON'T have hard SPL
My Original ROM i was using before was an htc windows mobile 5 rom
The reason that my phone is bricked right now is because the usb cable disconnected in the middle of the flash
I'm using Windows Vista for flashing
Computer won't recognize the phone when on usb
My phone (qtek 9600) can't load the operating system
*EDIT*
THE PHONE IS STUCK ON BOOTLOADER WHEN I TURN IT ON, NOTHING ELSE, BUT THE BOOTLOADER SCRREN DOESN'T SHOW MY SPL AT ALL.
ALSO, MY COMPUTER DOESN'T RECOGNIZE THE PHONE....... MY PHONE HAS A TYPE 2A BRICK
Helping me will be greatly appreciated
come on.. I'm without a phone
Do you have a 2GB or smaller SD card? Copy a rom image to it and rename it HERMIMG.NBH
Turn it on and you might get lucky!
Just make sure its stock rom that was supplied, or the updated WM06 version as the CID should check out then...
vwkess forgot to mention, reset into bootloader, hold power, ok button and reset with stylus. Hold all buttons in until you get to the tri-colour screen. If it works, follow the prompts....
Cheers...
hi,
i think i can hlep.
i had recently bricked my phone with a custom wm6 image, it worked fine for two days and then i reboot, and all i see was the welcome image, nothing else.
so what i did is -
i pressed the hard reset buttons - power + OK + SOFT RESET (Stylus), kept it pressed for 3-4 seconds, the fone rebooted, the screen was full with some colored bricks i connected my fone in USB and on screen i saw USB.
I then again flashed my fone with the working update, it worked perfectly for me, try may be you can get some luck
ps - before doing all these, i turned my fone off by removing the battery, i removed sim card and mmc card as well.
regards
That may work too, but again, try to flash with a stock rom, untick "connect with USB" in activesync and then try.
Make sure you go to boootloader screen, instruction in rajivlodha's post, before you connect to the pc.
Goodluck...
I need some help as well.
I think I may have bricked my phone. It's a rooted htc hero cdma. I'm running cyogenmod on it and it was working fine, until using metamorph to apply some changes to the theme.
I went to reboot, and it now it won't load past the htc screen. Even when i try the key combination to put it into recover mode. I didn't install a nandroid backup, and i'd be fine with just completely wiping my phone. help is appreciated.
hello,
since yesterday I cannot boot my X1 anymore.
Rebooting starts, then I get the screen where I have to enter a security code (thanks to my company`s security policies...) and I cannot enter values there. After a few seconds it stops booting. So I cannot proceed
Only option I see is to reinstall ROM/firmware.
My laptop cannot see the X1 via USB because it is not up and running, so I cannot move data/new ROM to the microSD.
Is there a Software/firmware/ROM-updates available (prefered: WM6.5 German, or at least WM6.1) which can be started/run from my laptop?
I couldnt find a download link to VodafoneGerman WM6.1 here
http://wiki.xda-developers.com/index.php?pagename=HTC_Kovsky_Shipped_Roms
thank you
Raggi
If you have soft SPL, you should be able to get into boot logger screen and update it thru the SE site/program.
Other option.. is there a card reader/adapter that fits the micro SD card for you to copy the ROM?
Edit: Does hard reset work at all?
hard reset doesnt work unfortunately.
Dont have soft SPL installed
my cardreader doesnt support microSD, so I guess I first have to buy a new one
is this the latest official Vodafone Germany WM61 ROM?
GENERIC deutsch DE (1.03.938.9) R2AA006
http://forum.xda-developers.com/showthread.php?t=477801
Now I called Vodafone Business SUpport and they dont have a link for me....
Try the following:
Enter bootloader (press the silver buttons and on/off button when phone is off)
Use SonyEricsson's update program.
IMHO it should update as the phone connects to usb with different mode than normally.
great, a few hours later and got it working.
I went into town and but a new cardreader. in the meantime my X1 woke up
and I could use the SE update installer.
So now I have got a newer WM6.1 (ROM 1.03.162.10, radio 1.10.25.18) running which is so much faster than my old system
now time to enjoy the sun....
Strange, almost the same thing happened to me on that very day... Phone stopped booting after the SE logo (Animation didn't show up). Had to Hardreset after several attempts to solve the problem...