Related
My device: XDA O2, with wallaby boot loader 5.17
Tried to flash RSUv1.15(GPRS_421_ENG_O2) into it. Update froze at either 48% or 53%. Tried it 10 times over, while waiting infinitely but the device just auto-booted itself after each froze. Deleted the autorun files from the startup director on the XDA. After which it did not try the update at bootup anymore. Instead the device is now dead :
On boot it just gives a white screen and everything fails / nothing can be done. The device cannot be connected through USB, and nothing on either SD card of MM card will install.
I tried to flash wallaby-patch-tool.nb2 to fix the key problem with 5.17 bootloader but as GSM fails at the bootloader: it just ignores the disk. I tried the patch tool on a SD card and on two other MM cards it does not work on any of them: as the damn bootloader checks GSM first (and gives GSM ERROR)
Also since the device is trashed it does not apper to load its battery, I assume it must be quite dead soon. (is there any way to load a battery on a software-trashed XDA O2??)
I have another fully working XDA O2 at my disposal. That machine is running older version of CE, GSM and 5.15 Bootloader. I tried flashing the OS from that device to the SD card, succeeded in getting it there - but the broken device will not flash itself from the SD card since it has "wrong key", and the patch tool fails to work because the GSM fails before it even checks any cards in 5.17..
The GSM cannot be copied to the SD card from the working device, because copying the GSM requires connecting something called RS232 and running some program nobody has heard of..
Is there anything I can do? I even tried copying the 5.15 bootloader from the working device to SD, and flashing that to the 5.17 broken device: no success, since it fails the GSM at bootloader startup, and the card has "wrong key" anyways.
How can I recover from this?
When you do reply, please reply in full generously abundant and exquisite detail. I am unable to follow instructions such as "just do this and that" if you do give instructions please be very detailed: tell me where to load the files (paste the links) and preferably go step by step through the process.
I have noticed that some other people have this exact same problem. If you give good enough guidance maybe we can create a help file to address this same problem in the future as well.
Thank you in advance!
A further problem with the other XDA
A further problem emerged with the other XDA:
- now it only boots to bootloader, and refuses to power up properly
pressing the power button does nothing. Soft reseting does nothing. Hard reseting does nothing. The only thing that seems to work is pressing the powerbutton+softreseting at the same time == entering the bootloader mode. There the machine passes all tests and seems to be fully functional. however refuses to power up.
I tought maybe the SIM slot is improperly closed, tried closing it better, and manually pressing the switch inside - doesn't work either.
Also tired inserting, taking out, and reinserting the XDA to the cradle, with either the power button pressed at the same time or not (this seems to work sometimes when the XDA O2 in unresponsive) but that doesn't work either.
What to do? how can the device be powered up?
Still stuck with this same situation
Hi all,
I'm still stuck with this same situation. So far nobody has even tried offering any help to me. What can I do? Do you think I should just give up and toss the damn device to the nearest body of water I can see, or what?
look for "repair.zip" in the forum, for some people this helped.
XDA developer Itsme said:
look for "repair.zip" in the forum, for some people this helped.
Click to expand...
Click to collapse
Tried that. That doesn't work since that repair requires that the device works as far as the today screen - my device dies out well before that. As described above it dies right in the start: just frozes up and displays a white screen with a blue bar in top, and after that does nothing, runs nothing, reacts to nothing, etc..
Any other ideas?
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
I tried to install the faria wm6 update with the shelltool. everything was going as per the directions, about 3 or 5 mins in the install process(which says takes 15 mins) it stopped and it gave me an error on the phone saying something about the reprog.exe or someting... anyways, the computer said done and to reboot... so I did and now it goes as far as the white TMOBILE screen with the following 4 lines of code
IPL 2.26.0001
SPL 2.26.0001
GSM 02.25.11
OS 2.18.0.0
and it freezes there... it wont turn off either.
Tries removing the battery and reinserting it. Well the same thing happens upon powering on the device. Tried hitting the little hard reset button on the side with the stylus... the screen flashes off and then it attempts to reboot again and the phone freezes at the same spot. Please help. I did everything according to the directions. PLEASE TELL ME I DIDNT BRICK MY PHONE. :'(
This was answered over in the WM6 forum.
But read this:
http://forum.xda-developers.com/showthread.php?t=298613
thanks.. the reboot with the camera button worked.. then I flashed the original rom back... now time to try again. thanks
Hi!
I have a HTC P3300.
I bought a 4Gb SDHC card, and it won't work. I read at the forum that I would need a different rom, so I downloaded "Artemis_Touch_4.02_Full_with_no_cube", which would have sdhc-support.
Then I executed "STEP 1 - activesync then uspl cid unlocking.bat", that finished ok, and then "STEP 2 - activesync then flash artemis touch rom.bat", which stopped with an error 302.
After a restart all that came up was the boot loader. I then tried to flash the original rom (HTC WM6 Dutch) from the computer, but that ended also in an error.
I tried the SD upgrade (rename .nbh file to ARTEIMG.nbh, put it on a formatted sd-card and load it in my phone), and it finished without errors, saying I should press any key.
After pressing a key, the bootloader popped up again.... :S
Can anyone help me? I have been searching the forum and trying to get my phone to work since 21:00 and I haven't got any progress at all!
well sorry for that
did you tried to make hard reset?
and once i had a completely dead artemis.. no sign of life..but it fixed by the following..(and maybe this may help you cuz the flasheng goes not like usual)
while your mobile is off.. press the record botton and the camera and it should starts with usual sd card flashing.
for me this what happens.
the setup was in three phases as i saw... and it took about 30 mins .
maybe it will works for you
I also tried a hard reset, wouldn't work.
I pressed and hold the camerabutton, but nothing happend...
Maybe the battery is empty, so I pressed and hold the camera button while plugging in the usb-cable.
It started the SD-upgrade, and is still busy.
The update ended with a "press any key to continue".
But when I pressed a key, the boot loader popped up :S
When I tried to flash another rom (NLD-FINAL), an error occurred (I believe it was error 270, not sure).
But then the normal startup screen appeared!
I don't know how, but the problem seems to be fixed!
sorry i mentioned the wronge button before..
try to start flashing by pressing the RECORED button and the power.. while your mobile is off.
and be sure that you copied the original shipped ROM to your device (NOT elese)
As you can see in my previous post, I managed to flash the original rom.
I'm gonna try to upload an other rom some other time...
And with a patch I got the SDHC working too!
Thnx for your help!
y_bother said:
sorry i mentioned the wronge button before..
try to start flashing by pressing the RECORED button and the power.. while your mobile is off.
and be sure that you copied the original shipped ROM to your device (NOT elese)
Click to expand...
Click to collapse
Hey, thanks a lot, I tought, my HTC-Cruise is ready for sending to repair, but with your info, it works again. I could install the WM 6.1 again, after System hangs up while booting every time. He found USB connection on a colored sreen. Thank you very much.
Jupeli
Hello mates,
My i-mate Jasjar doesn't start any longer. Here's how I got here. I tried to flash my jasjar with Crossbow ROM using ROMUpgradeUt.exe but it didn't do anything. So I went into the Country_ID_Error folder on the computer and executed MaUpgradeUt_noID.exe. My jasjar froze after this and everytime I restarted it just hung on the bootscreen that says i-mate.
So I tried using mamaich method using mtty and now I can't even get to the i-mate bootscreen. So nothing just happens when I try to power up the phone (I'm sure the battery isn't dead).
All I can do is just enter the bootloader mode. That is the only thing that I can do that I know.
Please suggest something. I'm lifeless without the i-mate.
Thanks and regards,
Aditya More.
i had this same issue, i task28?'d my device, whatever command that resets the flash structure, then booted into bootloader, and flashed this file:
http://rs507.rapidshare.com/files/184081773/JASJAR_WWE_11353_137_10301.zip
that should fix you up real good, hopefully.
Well thanks a lot. But it doesn't help. It gives me a connection error when everything is fine. USB is connected, ActiveSync USB connection is disallowed.
I forgot to mention, that when I task 28'd my device, nothing showed on the device. It just showed USB at the top and v2.01 at the bottom for ever, which means the task 28 wasn't probably successful or I ain't sure what.
Yeah, I had to ask you how if the above given file will work if the phone is in bootloader mode.
To fill you on more details, my phone somehow strangely starts. I'll explain how.
When the phone is switched off, and when I press the reset button, nothing actually happens, no activities can be observed.
When the phone is switched off and I connect it to the computer via USB, it shows the charging light. Now when I press the reset button with the phone connected to the USB, the charging light goes off and the USB detection sound sounds on the computer and the computer shows "USB Device not recognized". This means the phone started.
But strangely in both the above cases, none of the two lights on the phone indicate anything and display of the phone shows absolutely nothing.
The only thing I can do with the phone now is enter bootloader.
Also, since I compromised so much, is it possible that I can still flash it with WM6? Because going back to WM5 will make me feel miserable.
Thanks.
@cheapusenet:
I tried flashing with that file. It flashed successfully, but the screen is all smudged. I soft reseted the phone too (using reset+two soft keys) but it keeps displaying that same smudged screen.
Good news is it did something.
Bad new is that it didn't make the mate work.
Please help. I'm dying without the phone.
Thanks and best regards,
Aditya More.
is it possible you can get a picture of what screen its showing? I THINK it happened on mine as well, did you let it sit for 10 or so minutes? if i recall the bootscreen was all corrupted but it started into WM5 just fine.
and regarding wm6, i'd attempt to get the device working before you try and get fancy. is the device cid unlocked? mine was and thats what was causing the issues.
Originally Posted by mamaich
if you can enter bootloader - use "task 28 55aa", this would restore DOC to its original layout.
If you cannot - contact service center.
if you didnt run that exact command, it's probably a good idea.
and you could try reflashing that stock imate rom?
This is all that happens.. I have waited for 5 minutes. I'll wait for 20 minutes now.
i waited for 30 minutes.. no go..
yap it did that EXACT same thing to mine.
reflash it, i think that fixed mine.
if that doesnt work, attempt flashing some custom roms.
is it CID unlocked?
i flashed it twice.. no go..
what's CID unlocked?
CID
Read the Wiki on my sig link
cid unlock allows flashing of roms that don't match your device branding.
i don't remember what brought me back from that, i may have flashed a custom rom with the imate cid settings in it? i don't remember.
i'll post a rom that i think may have helped in a few hours, I have slow upload speed. until then, just keep tinkering.
also, you should only be flashing nk.nbf. not the ms, or radio nbfs.
http://milfweed.info/UNI_AKU3_2_WWE_IVAN_beta_4_extrom_public.rar
try that rom.
hey man.. Flashed the rom with Ranju's ROM of WM6.1.. it worked.. But I can get the phone to be turned on. i mean device turns on but I can't make or receive calls or text. Let me check the thread of that rom. Thanks a ton for your support. Really appreciate it.