Develop Bugs

Qtek 9090 Dead - Update not 100%, no reaction, no bootloader

Hey guys,
I've searched the forum for like 5 hours or so
to find a thread that could help me solve this solution...
I've tried everything that had something to do with "dead"
in the BlueAngel and Blueangel Update etc. section
What it does:
- The screen stays black
- If I try to charge, the Red 'Charging' LED doesn't become red
unless I take the battery out of the Qtek and charge..
Then it gets red (WEIRD)
- No connection with activesync or rom update utilities
What happened:
- Rom update stopped after a few percentages...
If i try to get a new rom in it with or without cradle
with the following rom update utilities:
- BaUpgradeUt.exe:
then I get a Connection Error (101) when I try to update
- MaUpgradeUt_noID.exe:
ERROR 150: ROM UPGRADE UTILITY ERROR
(Rom Utility not designed for this device)
or "Finished" immediately (but it's not finished)
(Depends on the rom I use, and I used like 10 different roms)
Soft reset / Hard reset doesn't work,
I even tried to Hard Reset by holding the
Voice Record button + Power button + Reset button for 2 minutes
(I tried Camera + Power + Reset too) with the battery,
and I tried these without the battery...
No reaction...
If someone can help me, please do...
Thnx in advance

Maybe you can try thingds from this
http://forum.xda-developers.com/viewtopic.php?p=291989#291989

sep said:
Maybe you can try thingds from this
http://forum.xda-developers.com/viewtopic.php?p=291989#291989
Click to expand...
Click to collapse
Nope,
I've tried that too, but I don't get the USB or WCEUSB in mtty...
The COM ports don't react.
I know how to use it, because I used it like 10 times or somethin'
But I think the problem is, that I can't get in the bootloader mode
(or any other mode)... So there's no response from my Angel..
Thanks anyway..

have you tryed to remove battery, leave it without battery fo an hour or two then put the battery back and power on the device ?
this method may boot your device. If it worked go imediately in bot loader mode and reflash your favorite rom
If it does not helps maybe it is hardware problem ... and you should leave your device in service center

Tried this too
Isn't there any solution except for service center?
I want to know how I can solve this problem,
'cause it could happen again when I update the rom later.
And I know I'm not the only one with this problem.
It would help me and a lot of other BlueAngel owners..

Is it possible to make a serial connection with the bottom I/O port and issue the necessary commands with mtty? could be that there is some logic powered on the board but not enough to make the "USB" section powered up.. similar to serial a console cable on network gear etc. OR.. is there any known secrets such as a hardware debug mode initiated with certain pin(s) on the I/O connector.. such as grounding one or two.. any HTC tech documents floating around for troubleshooting?

You are not one with this problem. The same happens with me too.
Let searching for solution together.
If you want you can contact with me by icq: 190812766

i'm gonna kill myself..3 my friends Jasjar plus 1 qtek dead

Please guys..could anybody help me??error 150 rom upgrade utility error
this rom upgrade utility does not design for your device...
I tried everything but i can't make it works...the window is always the same ... :shock: error 150 rom upgrade utility error
this rom upgrade utility does not design for your device...
MaUpgradeUt_noID doesn't work...
PLEASE PLEASE PLEASE...thanks
mik111

Did you tried hard reset it?

First, don't get panic! Well.When I tried to unlock my device and make it Super CID that message appeared in my screen too.I tried anything I was told in this fantastic forum and nothing worked.Finally I was told to reinstalled windows on my PC and...it worked!! I think it's a problem of drivers. If you are desperated try it.
Good luck and be the force with you...

may the force be with you! :lol:
but like alberbrando said, don't panic. panic would only make things worse. try re-installing your windows. Hopefully, that should resolve your problem.

???
gtm55 said:
Did you tried hard reset it?
Click to expand...
Click to collapse
hi guys..i tried to hard reset it but nothing happend..i'm very depressed...how can it be possible??i've already done this operation with this pc..and it worked..is that possible ?drivers?reinstall windows??****..is one of the of the worst boring operations i've ever done..
any other ideas?

http://forum.xda-developers.com/viewtopic.php?t=61002

frz said:
http://forum.xda-developers.com/viewtopic.php?t=61002
Click to expand...
Click to collapse
thanks frz..i've hard resetted...nothing happend...

So do the other thing they told you and reset windows.
Which is worse? a few hours boredom of backups and reinstalls, or spending what. . . 1300. . £2600 on new PDA's for you and your friends?
I know which one I'D pick.

Try
Try with this upgrade Tools
-put nk.nbf file on this folder
-put your device to bootloader mode
-deactive active sync on your computer
-connect to USB
-Run upgrade tools
cheers
indra9110

Right, don't panic, not being able to flash isn't such a big deal.
First, get an official update package for your QTek, and for your friends an I-Mate update package.
Next, hold the power button and the light-button (next to the volume slider), and stick the stylus in the little reset hole in the back. Hold the keys for a little longer, untill you vaguely see "Serial" or "USB" on the bottom part of the screen (put a little light on the screen, as the backlight will not be lit).
At this point make sure it's connected to your PC through the USB cable.
Right-click the MS ActiveSync icon (on your PC) and choose connection settings, make sure "Allow USB Connections" is unticked.
Next run the update utility, and everything should be fine again
If this doesn't help, ask again and state clearly that you've tried this already.

TheBlasphemer said:
Right, don't panic, not being able to flash isn't such a big deal.
First, get an official update package for your QTek, and for your friends an I-Mate update package.
Next, hold the power button and the light-button (next to the volume slider), and stick the stylus in the little reset hole in the back. Hold the keys for a little longer, untill you vaguely see "Serial" or "USB" on the bottom part of the screen (put a little light on the screen, as the backlight will not be lit).
At this point make sure it's connected to your PC through the USB cable.
Right-click the MS ActiveSync icon (on your PC) and choose connection settings, make sure "Allow USB Connections" is unticked.
Next run the update utility, and everything should be fine again
If this doesn't help, ask again and state clearly that you've tried this already.
Click to expand...
Click to collapse
Thanks Blasphemer but i've done that 2000 times with no success at all...i think that entirely rebuild the pc is my last chance... I don't wanna think at what will happen when the same old window will came out...I' m preparing my gun... :shock:

b4 attempting to flash
b4 attempting to flash,
chk if the 3 steps with mtty work,
if u don't get any error,
plz get ur battrey charged fully from a friend.
then attempt a flash by downloading a different rom from the one u r presently using
disable ur pc firewall
also disable ur anti virus [dont know if this is really required...but i read it in quite a few forums & it worked for me...]
flash only the rom
no extended rom or radio
use the MaUpgradeUt_noID
hopefully this should sort out ur problem....
i know coz i had the same problem....
frz

Another suggestion....
before making any other test, if it's possible, try on another PC, using a fresh rom (not the same used...) .... can be a PC problem, so test the procedure on another host ....

... sorry, again...
have you checked the bootloader version on the devices ? ... verify it before any other tentative ....

crashed/frozen. wont boot (FInixNOver) - cant reflash!

Hi guys.
I was using the installed the FInixNOver 3.0.1 ROM onto my SPV M700 and it was great. I've had it for about 2 weeks without any problems.
Last night I looked at my phone, only to realise that it was completley dead. This didnt shock me to much because the battery was running low, and i decided to let it die completley before recharging it again.
I charged my phone overnight and switched it on this morning, but the phone would freeze at the 'FInixNOver' splash screen (the numbers at the bottom of the screen would appear overlaying the splash, but the phone wouldnt go pass this point).
The only way to turn off the phone from this state is to eject the battery. I have tried removing the sim card, turning it back on in as many ways as possible but to no avail. I am able to get to the TriColor test screen (im running IPL-0.50 / SPL-1.30.Olipro) but with all the custom roms available, they all use the ROMUpdateUtility which requires the phone to have established an activesync connection initially (but this would mean my phone would have to be 'on completley' - so this is catch 22.)
For the record, my phone/battery died while my wired handsfree was attached (dunno if thats of any interest to anyone or the rom baker).
But it looks like the only way i'll be able to flash my phone is by finding a way to install the .nbh file without using the RUU method. Because I can put my phone into test mode manually.... any help or guidence would be very much appriciated.
Thanks.

Ok can you get it into bootloader? power/camera buttons and reset?
sorry didnt read fully.
right get your device into bootloader first,
then open active sync (are you using xp)
then open connection settings and disable usb connection,
put your device into bootloader mode, then run any rom upgrade, i prefer the WM6.1 pdaviets from HERE (Username: PDAVIET / Password: pdaviet)

Your pda does not need active sync with ruu's, so no catch 22. if you turn off usb connection in active sync, you can still run ruu and it will be recognised, unless you are using vista, where you need to change your HTC SYNC drivers.

Thanks for your quick response...
Yes I can get into boot loader using the power and camera buttons (or holding the power and camera buttons when resetting the phone)...
When the phone is in boot loader mode, active sync doesnt even detect the phone anyway, but nevertheless, I have followed your instructions and disabled the USB Connection. (BTW, yes i am using XP)
The phone is still in boot loader mode, so now i try and execute the ROMUpdateUtility.exe and go through the steps, at the 1st step i tick the tickbox and click next, and the 2nd step i tick the tickbox and click next. (this step says DO NOT enter the bootloader manually? - but i have havent i?) anyway, when i click next, it says... "Verifying the information on your Trinity... Please Wait..." for about 10 seconds, and then i get a message "ERROR [260] : CONNECTION"
What am i doing wrong?

Huumm.. why dont you flash your phone throw the sd card??
Read this link:
http://wiki.xda-developers.com/index.php?pagename=Trinity_SDCardFlashing

try to flash your phone with some official rom and after that flash it with any other you want!

manos_23 said:
try to flash your phone with some official rom and after that flash it with any other you want!
Click to expand...
Click to collapse
I would recommend this option above, to be safe, i usually get them error messages when the battery is below 50% or sometimes i try it again and it works. it does state do not manually enter bootloader but i always do it this way.

also make sure active sync is not still running in taskmanager under the alais: wcescomm.exe and WCESMGR.exe, end them both.

I've just tried using an official ROM, but the problem still occurs with the 'connecting'. It doesnt seem that the computer picks up a connection to the phone whatsoever.
Should i be concerned that at the bottom of the bootloader screen it says "serial", is this correct?
Im starting to get annoyed now.

Bye,
the bottom of the sreen mast say "usb" not serial.

it seems there is a problem, if it states serial. as it should say usb. try THIS

Seems like the problem was that my USB lead was loose and made a bad connection, hence why the bootloader showed 'serial' and not 'usb'... as soon as i wiggled it and heard the 'connection noise' in windows, i knew i was good to go, and so using the RUU worked fine to reupdate my phones ROM.
Thanks for your help.
My only question is that why did it happen in the first plave?

WIZZKID - I just saw your post here now. I have to tell you that I also saw "SERIAL" at the bottom of the bootloader screen and not "USB". As I said I returned it to get another phone but maybe I will try something else for now instead of a P3600i. I will monitor your thread to see how it turns out for your phone, because it seems that we have the same problem.

if you see "serial" instead "usb" your problem is in the usb cable, usb port from your computer or in the usb connector from your trinity!!!!!
I was having the same problem that you have!! my problem was from my usb from mine trinity!! see if the conector is at good conditions !!!

Well as some of you may know, I got my Trinity replaced for sticking at the WM splash screen after a few days. This second one - I have had it ONE night - and the same thing has happened with incomplete booting. This time I have been trying all night to flash the phone to an official ROM, but I cannot do it (apparently) because I can't establish a connection via ActiveSync. When I stick the data cable in while in bootloader I see SERIAL replaced by USB and when I try the flash I get a "270" error (cannot connect to phone) and the phone re-boots to the sticking plash screen. What should I do now?

ladies and gentlemen...
we've got a lot of mixed messages in this thread.. please make sure you're posting the right thing. no need to disable USB when manually going in to bootloader to flash (at least in xp).. Also, you can ignore the part of the RUU that says 'do not manually enter bootloader' (you should really read the guide on my site)
foxuniform- can you please give some details..
1) are you running xp or vista
2) have you flashed hard-spl? if so what version?
in the mean time, try a couple of things.. first, flash hard-spl (even if you already have it, but from the sound of it i think you don't have it on your device).. if that works, try to flash an official ROM. Can also try to use splxploit, then flash hard-spl, and then flash official ROM (there's a guide on my site if you're unsure)
please post your results
*edit*
here are the steps for SD card upgrade, but i HIGHLY recommend flashing Hard-spl first..
try to do it from SD card. how?
Extract the .NBH file from your prefered ROM upgrade: In windows use winrar (right click) to extract the contents of the exe file. In Linux / MacOS use cabextract (http://www.cabextract.org.uk/) .
Rename the .NBH file to TRINIMG.nbh and copy it to the root folder of your miniSD card.
With miniSD card inserted on the phone, start the bootloader (hold Power button on right side and Camera button at same time and stick with stylus in RESET on bottom).
You should see the screen pictured on the left, confirm flashing on screen by pressing the power button.
Flashing might hang after some time but this is normal. Just wait. Complete flash takes about 30 minutes, so check your battery or connect to charger before the flashing process starts.
When flashing completes soft-reset your device.
Make sure your SD has FAT32 and has no label. There have been reports that if SD has a label the bootloader can not access the TRINIMG.nbh

racerx_ I have carefully read your response and suggestions, and thanks for your expertise input on the matter. I am fairly new to this stuff so read below carefully as you may find errors in the way I tried to go about doing what I was hoping to accomplish.
First let me answer your questions. I am running Windows XP. The phone is in it's completely natural state in that I have not flashed it in any way. The ROM I was TRYING to flash to the phone while it was not starting properly (this is where I manually entered bootloader) is an official ROM from the HTC website (please note everyone that when I registered my P3600i on the HTC website it came up as the Dopod 810). Anyway, that never worked. ActiveSync never detected the phone (and I guess that's the reason I could not do anything as far as flashing goes). I HARD-RESET my P3600i and it booted normally. I re-installed all the stuff I had on it, from memory card to various .cab files, and the phone is working beautifully thus far. I will report if anything funny happens again.
I have to ask you racerx_, if I CAN flash hard-SPL on the P3600i according to the lovely guide on www.trinityguides.info. I have been of the opinion that things don't work for the P3600i as they did for the P3600, and that has been echoed by many P3600i users on this forum who are ready and waiting to try out some cooked ROMs (myself included).
For the sake of record, my phone is running rom version 3.00.707.17 and radio version 1.46.00.11. I patiently await your response.

woaaahhh..
i didn't notice the 'i' in your previous post... yeah, as far as i know, these ROMs are not flashable on your p3600i.. sorry..
**correct me if i'm wrong somebody**

Yeah I kinda thought that would be your response. By the way - do you think that this phenomenon of sticking at the Windows Mobile splash screen (both the P3600 and P3600i models apparently) has anything to do with something users do with the devices, or you figure it's an inherent software glitch of some sort? I am wondering if I should try a different model or hold on to my P3600i? Hope it's not something that'll happen again - I fly for a living and it's not gonna be good to have the thing screw up on me away from base - I really count on it for everything from casual keeping in touch on Messenger to viewing my work schedule. I love the Trinity though - it's one of my all-time favourite HTC phones.

hmm... i don't think its inherent in the Trinity.. (not a hardware issue.. in my opinion)
its been a while since i followed the posts on it, but always seems to be software related.. sometimes ROM-specific problem. Personally, i've probably flashed as many ROMs as anyone and the only time i ever encountered problems was with the official HTC WM6 ha.. go figure.. I think ppl did find that hard resets before and after flashing are helpful as well..
i love my trinity, and there's not much else on the market to make me want to trade it in (is it just me, or have pda's kind of stopped getting cooler).. i'd stick with it..

Pocket Loox N560 stuck on boot screen. Won't start up

Does anybody know if there is a way to boot N560 using SD card? I think I killed my FS with some "rom killer" and all I get now is FS boot screen, no other activities.
Any way to start it from SD card and flash it from there?
Perhaps any other way to bring it back to life?

i have the same problem
is there anybody for help???
SOS please

Eenigmaa said:
Does anybody know if there is a way to boot N560 using SD card? I think I killed my FS with some "rom killer" and all I get now is FS boot screen, no other activities.
Any way to start it from SD card and flash it from there?
Perhaps any other way to bring it back to life?
Click to expand...
Click to collapse
You cannot burn the ROM from an SD card.
If the device has had the anti-theft password set at some stage then you cannot reburn the ROM! This might be the problem?
A hard reset on the N560 followed by running the Loox burn program on a PC with ActiveSync connection to the N560 cradle is the only answer i.e. a normal ROM burn.

fingerstoo said:
You cannot burn the ROM from an SD card.
If the device has had the anti-theft password set at some stage then you cannot reburn the ROM! This might be the problem?
A hard reset on the N560 followed by running the Loox burn program on a PC with ActiveSync connection to the N560 cradle is the only answer i.e. a normal ROM burn.
Click to expand...
Click to collapse
Theft protection is not a problem here. It was wrong ROM and now it is stuck on boot screen, active sync does not see it at all, maybe there is a trick to somehow anable burn, flash, service mode on it? So far nothing helps....

Eenigmaa said:
Theft protection is not a problem here. It was wrong ROM and now it is stuck on boot screen, active sync does not see it at all, maybe there is a trick to somehow anable burn, flash, service mode on it? So far nothing helps....
Click to expand...
Click to collapse
read, and pay attention here:
[email protected]@p://a.mod-site.net/gb/u/newplow-1.html
POST 203.
Edit/Delete Message

vladtapes said:
read, and pay attention here:
[email protected]@p://a.mod-site.net/gb/u/newplow-1.html
POST 203.
Edit/Delete Message
Click to expand...
Click to collapse
GREAT!!!!
Thanks ever so much! You are real HELP!!!!
You should close process "wcescomm.exe" on PC in task manager. Then hold button record, power and puch reset after that you will come in boot loader. Run the program mtty.1.42 and select usb connect. If You will see the any error just start again mtty. Put command l c:\os_213u.nbf (You should put correct flash file in c:\ or use correct path to os_213u.nbf, l - like L but small). When it will done You should start PocketLOOX5xxFlashTool.exe and flash you PDA.
Click to expand...
Click to collapse

Eenigmaa said:
GREAT!!!!
Thanks ever so much! You are real HELP!!!!
Click to expand...
Click to collapse
do you confirm the method is fully functional?
I made a backup of my german original rom, if i have problems i want to restore it...
have you got a backup of your old wm5?
thanks

Yes it is working! Even if error comes at the end, shut the appie and use FS update tool to finish it up! All perfect!
Google for WM5, it is somwhere out there!

Eenigmaa said:
Yes it is working! Even if error comes at the end, shut the appie and use FS update tool to finish it up! All perfect!
Google for WM5, it is somwhere out there!
Click to expand...
Click to collapse
could you please p.m. to me the link of wm5 other language?
If you refer 4pda...it can't be downloaded, i don't know russian, i registered, but always cannot download...
if you have other link...pls send me...

vladtapes said:
could you please p.m. to me the link of wm5 other language?
If you refer 4pda...it can't be downloaded, i don't know russian, i registered, but always cannot download...
if you have other link...pls send me...
Click to expand...
Click to collapse
You can if you use an translator like www.windowslivetranslator.com or translate.google.com
then it is pretty easy.

I've resolved...
Fully functional WM6.0 newplowe in English...
now I'm searching for editing it in Italian/French but I need to edit the rom part of the XIP (just that).
For doing that, I need to open decrypt the file .nbh file (don't really know howto, and newplow doesn't answer about that... ).

Hi everybody, I need your help. I spent 2 hours to read several posts about N560 brick recover, and I still can't figure how to do it.
I flashed the N560 with the WM 6.1 and then I tried to flash the backup Rom Image ... which failed. Now is stucked in the climbing image ... and is not reacting to nothing. I didn't try the mitty sol because I don't have a clear ideea about using it, I am still a newbie ...
Please, I am begging for help if you can , thanks

rcretu said:
Hi everybody, I need your help. I spent 2 hours to read several posts about N560 brick recover, and I still can't figure how to do it.
I flashed the N560 with the WM 6.1 and then I tried to flash the backup Rom Image ... which failed. Now is stucked in the climbing image ... and is not reacting to nothing. I didn't try the mitty sol because I don't have a clear ideea about using it, I am still a newbie ...
Please, I am begging for help if you can , thanks
Click to expand...
Click to collapse
Try this?
Take the N560 off the cradle. Remove the battery for at least 30 seconds. Reinsert battery and back cover. Do not worry if the screen shows the dolphins again. Do a full hard reset to get back to factory setting i.e Simultaneously press and hold the Suspend/Resume button (1) and the Calendar application button (2). Briefly press the stylus tip into the soft reset opening (3). Continue to hold down the Suspend/Resume button and the Calendar application button for a few seconds. The reset can take a few minutes. At the end an acoustic signal sounds. Please follow the further instructions on the display.
A hard reset should put the device back to the existing (last burned ROM) and you can try the burn again.
You probably do not know why the burn originally failed. The most common reason is some interrupt of the processor (internet access, switch of all internet access) but more likely something is polling the USB port, which might be shared in the PC. My external USB TV tuner constantly polls the USB port and interrupts any transfers on other ports! I suggest that you disconnect all other USB devices and make sure that your N560 cradle is connected to a USB port directly on the motherboard of the PC (not a USB hub or expansion card with multiple USB ports).
Hope this helps.

N560 - still stucked in the climbers bagground after WM 6.1 flash
fingerstoo said:
Try this?
Take the N560 off the cradle. Remove the battery for at least 30 seconds. Reinsert battery and back cover. Do not worry if the screen shows the dolphins again. Do a full hard reset to get back to factory setting i.e Simultaneously press and hold the Suspend/Resume button (1) and the Calendar application button (2). Briefly press the stylus tip into the soft reset opening (3). Continue to hold down the Suspend/Resume button and the Calendar application button for a few seconds. The reset can take a few minutes. At the end an acoustic signal sounds. Please follow the further instructions on the display.
A hard reset should put the device back to the existing (last burned ROM) and you can try the burn again again.
You probably do not know why the burn originally failed. The most common reason is some interrupt of the processor (internet access, switch of all internet access) but more likely something is polling the USB port, which might be shared in the PC. My external USB TV tuner constantly polls the USB port and interrupts any transfers on other ports! I suggest that you disconnect all other USB devices and make sure that your N560 cradle is connected to a USB port directly on the motherboard of the PC (not a USB hub or expansion card with multiple USB ports).
Hope this helps.
Click to expand...
Click to collapse
Hi and thanks a lot for your post ... I tried several times this procedure ... I see no change for the hard reset .. No dolphins image at all ... I would say whatever I do it doesn't affect it. No sound, no other signs ... same climbing image.... Please keep remember other solution, It should be one ... thank you again ...

rcretu said:
Hi and thanks a lot for your post ... I tried several times this procedure ... I see no change for the hard reset .. No dolphins image at all ... I would say whatever I do it doesn't affect it. No sound, no other signs ... same climbing image.... Please keep remember other solution, It should be one ... thank you again ...
Click to expand...
Click to collapse
THANKS FOR HELP, I didn't made correctly the the procedure ... now all it's Fine ... really appreciate your help ... saved my precious loox ...

rcretu said:
THANKS FOR HELP, I didn't made correctly the the procedure ... now all it's Fine ... really appreciate your help ... saved my precious loox ...
Click to expand...
Click to collapse
PHEW! Thank goodness. I suspect you did not do the hard reset correctly at first. But I agree about the Loox being precious! I look after mine very carefully! Glad I could help you. My pleasure....

My fs560 is brikked!!!!
It remains to climbing people...
I can enter to bootloader (dolphins) but i cannot update to Windows mobile 6.1 Classic ver. 063.07
I need your HELP!!
I tried to use mtty and i can arrive to:
Image Download Finish
OEMFlashWrite(A0000000h,8C200000h,0236002Ah)
Download Fails !!!
OEMFlashWrite error(12)
Error : DownloadImage return error (code = 0xFFFFFFFF)
but then I cannot initialize normal update, it remains to dolphins with the blue bar fullfilled by precedent mtty...
the PocketLOOXN560FlashTool.exe can't find the device...
Can someone explain me the CORRECT method after mtty?
PLEASEE!!!

vladtapes said:
My fs560 is brikked!!!!
It remains to climbing people...
I can enter to bootloader (dolphins) but i cannot update to Windows mobile 6.1 Classic ver. 063.07
I need your HELP!!
I tried to use mtty and i can arrive to:
Image Download Finish
OEMFlashWrite(A0000000h,8C200000h,0236002Ah)
Download Fails !!!
OEMFlashWrite error(12)
Error : DownloadImage return error (code = 0xFFFFFFFF)
but then I cannot initialize normal update, it remains to dolphins with the blue bar fullfilled by precedent mtty...
the PocketLOOXN560FlashTool.exe can't find the device...
Can someone explain me the CORRECT method after mtty?
PLEASEE!!!
Click to expand...
Click to collapse
I think you have received a reply from Newplow on his guestbook....

Hi
I tried to upgrade to 128mb but after restart I see only climbing. I tried everything here but on dolphins afterr line is blue it is finished. that I am unpluging device. starting looxflastool for 560 and first is trying to connect by active sync and that when no connection made I see dolphins on left screen of flash tool window. than I am pluging again and after couple secs I see that: Error"The language in this Flash Image update (ENGLISH) differs from that on your device. I tried to change rom on every language but not working as well. PLEASE HELP!!
if that helps than i will add than on top when delfins i see on 560 is two lines. first is typed 2.14.G4 on second directly below is 2.15.
and when mtty 1.42 finishing flashing i see following:
Image Download Finish
OEMFlashWrite(A0000000h,8C200000h,0224002Ah)
Download Fails !!!
OEMFlashWrite error(12)
Error : DownloadImage return error (code = 0xFFFFFFFF)
I've done already procedure You've mentioned here with taking of the battery for at least 30 secs with hard reset afterwards but it is still climibing screen. Can U manage this as well???
THX

The most common error with the procedure is NOT making a proper or true hard reset, or back to factory settings reset. If you do it wrong, you will only achieve a soft reset, the same as you get if you just put the stylus in the reset hole in the base of the N560.
The correct procedure is to hold Power/Resume/Suspend button (on/off button) and the Calendar button simultaneously. Keep holding them and with the other hand press in the reset hole with the stylus. The screen should blank out. KEEP holding the other two buttons all this time, and release the stylus. KEEP holding those two buttons until the screen display returns, only then release them.
This should allow another burn.
I hope this is the problem. It has happened to me and others, so I think I am right. But if this fails, you may need another approach.

Need desperate help with possibly bricked Diamond

Hi all,
Just received my Vodafone-branded Diamond, and I'm afraid I already managed to brick it!
It was equipped with version "1.37.172.3 NLD" so I decided to upgrade it to the latest version.
The installation of OliNex Hard-SPL 1.93 went flawless, but the installation of ROM "RUU_Diamond_HTC_WWE-ME_1.93.456.2_Radio_Signed_Diamond_52.29.25.12_1.00.25.05_Ship.exe" stopped at about 25% with error code 302. The recovery method that came with the package didn't help, every time the upgrade stopped at the same moment.
Since the device is stuck in the bootloader, and I'm left with a non-chargeable battery, I tried the official Vodafone-branded "RUU_Diamond_Vodafone_NL_1.97.172.4_Radio_Signed_Diamond_52.44.25.24_1.08.25.08_Ship.exe" ROM. Unfortunately, this upgrade stops at 48% and throws the same 302 error.
Anyone who can tell me what I'm doing wrong, and what I can do to solve all this?
I hope I don't have a brand new, but bricked device on Christmas!
TIA and have a nice day.

Try a hard reset first. If this doesn't help google or search at XDA for MTTY.
This tool can fix your device

http://wiki.xda-developers.com/index.php?pagename=Kaiser_Stuck_at_bootloader
Try this, maybe will work

Try a Vodafone branded stock rom before mtty.
Regards,
Carty..

He already tried a stock rom....

Potential Solution
Have you looked at the thread titled,
[UPG][TRBL]How-to fix: Update/Flash doesnt work, stops at 0% or 5% (invalid model ID)
It may just be a model ID glitch that can me fixed.
Take a look. It's in this forum in a sticky by cptsunshine.

Thanks all for the help, I'll have a look at your suggestions.
The problem isn't that it stops at 0% or 5%, it stops at random percentages (depending on the ROM I use).
I also see the bootloader (red / green / blue), so it's not dead. I guess it's just that it doesn't pick up a ROM.
Besides, the bootloaders says upgrade ROM code error please try again.
Edit:
A hard reset doesn't seem to work. In the bootloader, when I press "volume down" and "enter" together, and press the "reset button" the screen goes black, but then goes back to the bootloader screen after a sec or 2.
Edit 2:
MTTY doesn't do much either, after executing "boot" the phone is showing me the Vodafone logo and that's it.
For the rest, MTTY shows me the following:
Cmd>boot
InitDisplay: Display_Chip=1
dwDirectNum: 0, dwMatrixNum: 0, dwMicroPNum: 0
Fixed new dwPSImageSize = 0x53E0000

Install Rom via Internal Memory Method
Steps from Suiller:
1. open from your PC the rar or zip archive and extract only the BIG .nbh file
2. rename as DIAMIMG.NBH
3. copy the renamed file into the root dir of your "Storage Card" or "Internal Storage" (the one of 4Gb... NOT to the internal phone memory!)
4. reset your device and within 3 seconds push together the Vol_Down + Back button (the one on the right above the hangup button) and keep pressed until the boot loader appears (the one with the color stripes)
5. soon as you see the bootloader stop to press those poor buttons
6. a very simple gray menu will appear asking you what to do, simple press the power button to perform the ROM/Radio upgrade
7. while the upgrade runs be patient and don't press again the power button, reset the device or play with it until it finishes, when finished a message "UPDATE SUCCESS" will appear, now you can safely reset your device
8. who prefer can perform a hard reset after the fresh cook (soon after reset simply press Vol_Down + Circle button, then when you see another simple gray menu choose Vol_Up to confirm format), even if this has no-sense because internal memory is pre-formatted during flash, but... there is always a but... for some unknown "scientific" reason sometimes an hard-reset can save time & headache
Let me know how it goes.
Make sure you have Net framework 3.5 installed on devices.

Nakkie27 said:
Thanks all for the help, I'll have a look at your suggestions.
The problem isn't that it stops at 0% or 5%, it stops at random percentages (depending on the ROM I use).
I also see the bootloader (red / green / blue), so it's not dead. I guess it's just that it doesn't pick up a ROM.
Edit:
A hard reset doesn't seem to work. In the bootloader, when I press "volume down" and "enter" together, and press the "reset button" the screen goes black, but then goes back to the bootloader screen after a sec or 2.
Edit 2:
MTTY doesn't do much either, after executing "boot" the phone is showing me the Vodafone logo and that's it.
For the rest, MTTY shows me the following:
Cmd>boot
InitDisplay: Display_Chip=1
dwDirectNum: 0, dwMatrixNum: 0, dwMicroPNum: 0
Fixed new dwPSImageSize = 0x53E0000
Click to expand...
Click to collapse
u can do one thing then press woluem down and reset bottom at the same time then u go to rescue mode then u wait and put in the usb stick and there stand seriel when u put in the cable it will change to usb thenu can load the firmware again

band27 said:
Steps from Suiller:
3. copy the renamed file into the root dir of your "Storage Card" or "Internal Storage" (the one of 4Gb... NOT to the internal phone memory!
Click to expand...
Click to collapse
I wish I could mate, but I cannot put files on it anymore, since ActiveSync doesn't recognize my device when it's in the bootloader.
janielsen said:
u can do one thing then press woluem down and reset bottom at the same time then u go to rescue mode then u wait and put in the usb stick and there stand seriel when u put in the cable it will change to usb thenu can load the firmware again
Click to expand...
Click to collapse
Can you please be more specific? Are you telling me how to do a hard reset? I tried as to do a hard reset, but it goes back to the bootloader instead of resetting. USB stick?
Thanks all, much appreciated. A pain this can happen, looking at the fact that I did everything exactly as described in all these flashing manuals.

Nakkie27 said:
I wish I could mate, but I cannot put files on it anymore, since ActiveSync doesn't recognize my device when it's in the bootloader.
Can you please be more specific? Are you telling me how to do a hard reset? I tried as to do a hard reset, but it goes back to the bootloader instead of resetting. USB stick?
Thanks all, much appreciated. A pain this can happen, looking at the fact that I did everything exactly as described in all these flashing manuals.
Click to expand...
Click to collapse
first push the volum down buttom at the same time press the reset buttom then the 3 color display will appear and in the buttom will stand seriel then u putt in the usb cable to ur phone whit u have attact to ur pc then it will say usb now u can load new firmware

janielsen said:
first push the volum down buttom at the same time press the reset buttom then the 3 color display will appear and in the buttom will stand seriel then u putt in the usb cable to ur phone whit u have attact to ur pc then it will say usb now u can load new firmware
Click to expand...
Click to collapse
No mate, I never had problems getting into the 3 color screen. The problem was updating afterwards, which never completed without error code 302.
Anyway, I guess I just fully bricked my device after putting SPL-1.40.OliNex (according to the guide at http://forum.xda-developers.com/showthread.php?t=416211) on it. The SPL install was succesful, but when booting I'm now not even getting to see the 3 color bootloader. All I see is the Vodafone logo with some version numbers at the bottom, but that's it. It doesn't boot further on, and I can't get a USB-connection.
Edit:
Volume down + reset brought me in the bootloader again, although it's saying SPL-1.93.OliNex.

Nakkie27 said:
No mate, I never had problems getting into the 3 color screen. The problem was updating afterwards, which never completed without error code 302.
Anyway, I guess I just fully bricked my device after putting SPL-1.40.OliNex (according to the guide at http://forum.xda-developers.com/showthread.php?t=416211) on it. The SPL install was succesful, but when booting I'm now not even getting to see the 3 color bootloader. All I see is the Vodafone logo with some version numbers at the bottom, but that's it. It doesn't boot further on.
Click to expand...
Click to collapse
that i know but as i say in the post that when u do it that way i say u can load new firmware whitout it needs to boot try my friend i have done it 3 times because wrong loading of firmware

u have to only push thoose 2 buttom then it will work because u go to rescue mode

But what will that give me extra? I can access the Hard-SPL 1.93 bootloader (3 color screen), and I can get into USB mode. It's just that the upgrade of both firmwares stop at a certain percentage.
I'm constantly trying to hard reset the device, but after pushing the reset button (with both volumn down + enter pressed down), the device just reboots back into the bootloader and doesn't give me the hard reset warning.

Nakkie27 said:
But what will that give me extra? I can access the Hard-SPL 1.93 bootloader (3 color screen), and I can get into USB mode. It's just that the upgrade of both firmwares stop at a certain percentage.
I'm constantly trying to hard reset the device, but after pushing the reset button (with both volumn down + enter pressed down), the device just reboots back into the bootloader and doesn't give me the hard reset warning.
Click to expand...
Click to collapse
u need to hold them down until it leave the 3 color display an turns into grey

Ok, finally managed to do a hard reset. Afterwards I tried upgrading to the official Vodafone NL 1.97 ROM once more, but it failed at 48% again.
Any ideas what to do? I know have Diamond with Hard-SPL 1.93 (which says upgrade ROM code error) with no working OS.

Ok all, got it finally working again!
Don't ask me why, but flashing the newest Dutty ROM (and the included radio) did work.
Thanks for all your help, and a wonderful evening!

Hi all,
I have a quit similar problem. I've read a lot, but couldn't find an answer to my problem - may bye someone can help me.
I updated my Dimond (OliNex Hard-SPL 1.93, radio 1.09.25.23 and rom dutty V4). When I start my phone most of the time (95% plus) I end up in the color screen - however some time it's starts perfect (without changing anything).
When I get stock in the color screen, I can start the phone with mtty and the command "boot".
What can I do to make my phone always start in the normal way?
Thanks!

Nakkie27 said:
Ok all, got it finally working again!
Don't ask me why, but flashing the newest Dutty ROM (and the included radio) did work.
Thanks for all your help, and a wonderful evening!
Click to expand...
Click to collapse
i smell a radio issue - last time i was trying to upgrade my radio - ended up with something similar, managed it out like you did - but now you're up - so that's good!!
try some other rom (this time without radio) - i don't think you should have any issues going forward... good luck and have fun!