Develop Bugs

BA - SX66 Variant won't load - stuck in Splash or Bootloader

Got a little problem, maybe big =(
Basically the phone one day decided not to work
i can get only two screens
either the start-up splash screen displaying CINGLAR and the firmware stuff on the bottom corner
or
if i enter bootloader mode, i get SERIAL 2.07 and nothing else
i have tried hard reset, take out the battery for ever, even flash
hard reset does nothing, soft does nothing
take out the battery does nothing
the phone won't charge through the cradle or charger, i can only charge the battery alone using the cradle
as for flashing it won't flash in the cingular splash screen or the bootloader screen, it doesn't change from SERIAL to USB when connected, thus the computer can't send anything to it
what can i do ?????

Do you have an SDIO card in the top slot? That can cause problems with the bootloader accepting the image from the PC.

nope only have the original DEMO SD plastic

any one what could be wrong ?

had same problem
dont know if you are doing the wm5.0 hard reset or teh old style hard reset that we used to on wm2003se. its teh notes button, camera, power and soft reset button. clear registry and the storage and then it should work. it did for me.

tried your reset steps boots the bootloader =(

Re: BA - SX66 Variant won't load - stuck in Splash or Bootlo
evilgabbie said:
if i enter bootloader mode, i get SERIAL 2.07 and nothing else
...
what can i do ?????
Click to expand...
Click to collapse
BigDamHero said:
If you got bootloader mode then you should be able to upgrade your rom to whatever you like.
Step by step insturctions are on WIKKI. The page for upgrading to the most recent ROM for the Blue Angel that IS NOT WM2005 is here:
http://wiki.xda-developers.com/index.php?pagename=BA_1.40.00_Upgrade
If your device is in bootloader mode just put it in the cradle (activsync won't start but don't worry about that) and start the upgrade!
Click to expand...
Click to collapse
When you get to the Bootloader screen, probably you are home free. Just use the abouve link to resolve you problem.

BootLoader Loop Issue - SX66 Siemens
I am having a similar issue , where i am unable to hard reset or soft reset ,If I place SX66 (SIEMENS) in cradle it appears to charge after charge is complete , it will go to bootloader menu.
==========================================================
I have downloaded the MTTY , and would to know the settings required for USB , is selected from dropdown what is the optimal choice to make.
Im not seeing the cmd line " CMD> " in using MTTY.
I was gonna use com ports but dont know the settings to set:
==========================================================
parity
data bits
stop bits
flow control
local echo

http://wiki.xda-developers.com/index.php?pagename=BlueAngel_WM5_For_Beginners
had exactly the same problem, follow these steps for hard reset
my phone came good after (running wm6)

ROM Upgrade problems - Device dead? HELP please.

I am a rookie at upgrading this stuff. I have a QTEK 9000. I got UNI_QTEK_13077_176_10900_WWE_Ship.exe from the ftp site.
1) Did a device reset.
2) Connected via active sync.
3) ran the program.
After a short period, The device shut off and active sync disconnected.
The screen is black. On button does not work.
I tried a hard boot and I get the boot menu and 0 or x does not seem to do anything.
Did I do something wrong? What now.

GaryK2 said:
I am a rookie at upgrading this stuff. I have a QTEK 9000. I got UNI_QTEK_13077_176_10900_WWE_Ship.exe from the ftp site.
1) Did a device reset.
2) Connected via active sync.
3) ran the program.
After a short period, The device shut off and active sync disconnected.
The screen is black. On button does not work.
I tried a hard boot and I get the boot menu and 0 or x does not seem to do anything.
Did I do something wrong? What now.
Click to expand...
Click to collapse
I think that program is supposed to be run after you've removed USB from the connection methods in activesync - i.e. you're not connecting via activesync, even though the device is physically connected.

OK, I tried the process again without activesync.
That seems to be the answer. ROM Is now installed. I just have to finish up.
Thanks alot,
That scared the hell out of me.

GaryK2 said:
OK, I tried the process again without activesync.
That seems to be the answer. ROM Is now installed. I just have to finish up.
Thanks alot,
That scared the hell out of me.
Click to expand...
Click to collapse
Hehee... when you get the new rom on, you'll love it...

GaryK2 said:
OK, I tried the process again without activesync.
That seems to be the answer. ROM Is now installed. I just have to finish up.
Thanks alot,
That scared the hell out of me.
Click to expand...
Click to collapse
Sorry for my silly question but how can you process it without activesync, mean you have removed activesync form your conputer?, because my activesync is automatic running when the computer start up
Thanks,
Orangevn

orangevn said:
Sorry for my silly question but how can you process it without activesync, mean you have removed activesync form your conputer?, because my activesync is automatic running when the computer start up
Click to expand...
Click to collapse
You're just telling AS to ignore the Exec when it's connected. The PC itself still sees it and adds a driver on connection. So you're not removing AS from the PC as such.

i have same problem but it doesn't work
please help me....this phone is dead now:-(

Re: i have same problem but it doesn't work
bmlsbr said:
please help me....this phone is dead now:-(
Click to expand...
Click to collapse
Did you try the AS thing above?

First off what do you on the screen of your device when you turn it on? Is it in boot loader screen, a black screen with text that says boot loader mode and serial?
If it is in boot loader screen and it says serial on the bottom, when you plug in the USB do you see the "serial" text change to "USB"?
I had this problem with mine. I upgraded my Qtek9000 with the new orange ROM and when the process finished I was still in the boot loader screen and could not get out of it. I had to re-flash it back to the Original Qtek ROM which revived the devices. I then started the ROM upgrade process all over again which resulted in a successful flash.
If you can answers some of the questions above I can try to help.

BTW, the upgrade process takes about 20-25 minutes. if it was any less then that you unplugged the device to early.
Plug device in.
• Start ROM upgrade process.
• The device will turn off and go into boot loader mode (the computer will lose connection to the device and unrecognized USB devices error will appear in your task bar).
• Wait until the device reconnects to the computer and the ROM upgrade starts.
• This process will take 20-25 minutes.
• Reset the device with option 0 (erase all data)
• The device will boot normally and go through the extended ROM application installs. It will ask you to reset again.
• After the second reset you are done.

xda exec upgrade (dead phone)
tHIS ALSO HAPPENED TO ME (IT WAS PRETTY SCARY) . i DISCOVERED THAT I COULD GET IT LIVE BY PRESSING THE LIGHT BUTTON THE POWER BUTTON AND THEN SOFT RESET (THIS IS THAT BOOT MODE) .
THEN I RE-CONNECTED TO MY PC AND RE COMMENCED THE UPGRADE...WORKED FINE. I HAD ACTIVESYNC RUNNING WHEN I DID THE INTIAL UPGARDE, PROPBABLY THE PROBLEM!! :wink:

none of this worked....may be I am not doing it right
when I try to add hard-reset all I get this is this:
"press 0 to restore factory default"
"press X to exit"
When I run the rom update, I get device connection problem error message and sometimes the country id error message.

none of this worked....may be I am not doing it right
when I try to add hard-reset all I get this is this:
"press 0 to restore factory default"
"press X to exit"
When I run the rom update, I get device connection problem error message and sometimes the country id error message.
my yahoo and msn id is bmlsbr...please someone chat with me and provide some help. I feel helpless after spending all the money and the phone dead after i day of use.
please...........

here is what I am getting
I can not turn my device on at all.

I'm unclear to what you are saying. First you tell us that the device does not turn on. Then you say you are getting the 0 X option. Which one is it? If you are getting the O/X option what do you see on the screen when you press 0. Do you see the device in boot loader mode? You might have to remove the battery and try the reset button after. my experience has been when the device is in boot loader mode I cannot turn it off. It always stayed on. So you might want to charge it just to make sure you have full power. I would also use the ROM loader without the country and device ID restrictions you can download it from the FTP site.

QTEK 9000 DEAD
I was always able to get the hardware reset menu..but nothing happened beyond that.
Now the phone is working after multiple tries to put the rom. But active sync won't work. Any clues????

What do you mean by works? Did you load the ROM?

Have you tried to follow these instructions:
http://forum.xda-developers.com/viewtopic.php?t=43592
Seems to work for a few people.

error [260] message every time

Firstly I would like to say thanks to this site and the trinityguides.info site for the great work people have being doing and making available to everybody, it is great being able to use my trinity with wm6, keep the good work going!
Now the issue I seem to be hitting the same "error [260] connection" every time I attempt to update anything on my Trinity. I have followed the advice on the trinityguides site regarding being stuck in bootloader mode to no avail, and I can't seem to find anything in the posts on the xda site which will rectify the issue.
Previously I have been able to update to AX3L v2.8.01 version without any problems, but I decided to update to sammy's ultra light, it initially kicks into des' crashproof sspl, but then it can't connect to the pc. even when I manually enter olipro's hard-spl it does the same. I have tried to re-install hard-spl, but can't. Disconnecting the usb option in the activesync settings doesn't do anything either. Does anybody have any suggestions for me please?
I am not even too sure if my trinity should have both Des' crashproof and hard-spl on it at the same time? Could someone advise me on whether this is alright please?
the tech details:
Trinity
AX3L_OS_v2.0.8.2
radio - 1.46.30 (even though it doesn't say this in the device info, or boot screen after soft reset)
Home PC - XP (just in case)

Did you also try flashing it again, the ROM I mean. I have this error also but as soon as I execute the ROM flash again it finds the device and starts flashing:
http://forum.xda-developers.com/showpost.php?p=1449597&postcount=2

I am assuming you mean flash with the new ROM, sammy's in my case?

yes, as described in the link I posted before. As soon as the error occurs, do not touch the phone, leave it, just start the ROM flash procedure again. (execute ROMUpdateUtility.exe)

No, I am in the same situation. The first attempt puts the device in 'ipl-sspl by des' bootloader mode then after about 10 seconds or so the error[260] is displayed on the pc. If I exit the ruu app and attempt again, nothing new happens on the trinity (i.e. it is still in Des bootloader) and the message is displayed again.

the thing is that when it first goes into des bootloader mode, the white strip doesn't have any text in it. If I pull the usb cable out then put it back in, 'serial' is then displayed in the white bar, but I am still in the same situation as before.

What operating system en activesync are you using?

On the PC I am using XP and Activesync 4.5

Check your connection settings to accept USB connections. Also, try using Hard-SPL 1.30 before flashing the ROM again.

deejacker said:
the thing is that when it first goes into des bootloader mode, the white strip doesn't have any text in it. If I pull the usb cable out then put it back in, 'serial' is then displayed in the white bar, but I am still in the same situation as before.
Click to expand...
Click to collapse
In your PC, try another USB connection.

BLOODY HELL!!! It is the simplest things which we often forget to try. Thanks Jotam for pointing out an obvious point, it must have needed a re-plug of the usb cable into another port for the pc to pick up the device again. I will remember that for future updates so I don't make a dumb ass of myself again. Thanks guys/gals.

Vista
Using Vista? if so which version?

Hi I asked this question yesterday, I am a noob :-[ but the only difference is I'm using Vista Ultimate.
Just for others who have the problem.
When you replug into another USB port (Luckly I've got two on my laptop..)
I used the Vista drivers from TrintyGuides and bingo !
now I try and flash a WM6.....English or Italian...maybe French.
Thanks for the help I keep you posted.
Richard

It works
Now to discover the joys of WM6 after only having WM5 for two weeks....

/i am getting the same only rom update 3.14.4.1 now sees the phone..
has the device name changed???
evene exploit no longer sees the phone

sorry, can you be a little more clear.. what ROM are you flashing, and what exactly is happening?
by the way... i thought error 246 was the connection error... am i mixed up? which is 260?

This seems to be on any rom bar the Dopod roms
and it says 260 connection error

Error 260 connection error - the phone is not going in to bootloader mode - and the RUU cannot seem to initiate communication with the phone.
I'm getting this a lot recently trying to flash.
However, Hold the power and camera buttons while resetting with the stylus (keep them buttons held down).
When you get to the bootloader - plug the phone in - wait till you see the USB at the bottom of the bootloader screen - then run the RUU again - it WILL work - every time.

I used to get this error message alot. sometimes the programs you install don't allow you to update even if you force the phone into bootloader mode so you have to hardreset the device and then upgrade.....hope this helps

htc diamond stuck
T-Rob said:
yes, as described in the link I posted before. As soon as the error occurs, do not touch the phone, leave it, just start the ROM flash procedure again. (execute ROMUpdateUtility.exe)
Click to expand...
Click to collapse
hi ,
my htc diamond stack, no respond on the screen i try to do hard reset with tree buttons but its not working, nothing happaned, screen stay home screen with the time and not responding touching the screen at all
please emergensy help

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!