Develop Bugs

Atom Exec dead after upgrade

I have an Atom Exec with ROM 20060721B1WWE, Radio RS00011. In the seeO2 website I saw an upgrade (Xda Atom Exec ROM Upgrade (ENG) 20060721B1WWE_RS00013) which is the same ROM but different Radio, supposed to improve quality of calls.
Anyway I went to upgrade it, followed the steps until it said it was uploading it and it would take up to 30 minutes. I went to do something else and when came back the pc screen was saying that the process finished successfully, saying that I had to do a hard reset of the Atom, wait for 30 seconds and then soft restart. I did all of that and all I got it's the O2 screen and doesn't go any further.
Following indication on this forum I launched the bootloader (camera button+reset), conected the usb cable, killed activesync and run again the updater.
The DSUU can see the Atom, says 'Device CE image version:0, Device Radio Image version: (blank) to CE Image version: 7210621, Radio Image version: R060822N_MN2ARC_RS00013.
When I click on Upgrade I get an Error message: Connection error, also on the Atom says '!!! Please use DSUU in OS mode and sync with Pc first !!! USB transfer Fail'
The only backup I did prior to this was using SPB Backup, nothing for the ROM. Is there any other way to upload the ROM?
From the Windows/Temp folder I got the files used by the DSUU:
Device Software Update Utility.exe
diskimage_Ver.nb0
EBOOT.nb0
ExtenderRom.img
nova_pda_033105.mot
vl1d_pda_Ver.mot
I've seen in other forums people recovering iPaqs or Axims using these files and software like romupdate, but I'm afraid it could get worse uploading the diskimage_Ver.nb0 as it is.
Anybody knows a workaround for this?

I ended copying diskimage_Ver.nb0 and eboot.nb0 to an miniSD card. Inserted it in the Atom and lauch the bootloader. It recognized the card and Rom file, started downloading it. After that I got few messages saying some files were missing.
Screen went blank and that's it. Now is completly dead, it won't restart or anything.
I'll have to send it to Hong Kong I guess.

hw6515a pnewbootloader hangs

I have two hw6515a phones. One mostly works, but resets randomly. The other is seemingly brand new. The 'new' phone does not function as a phone. The 'details' tab does not show any information regarding the GSM radio stack software. I've saved the ROM contents from the 'working' phone to an SD card.
Inserting that SD card into the 'new/non-functioning' phone, and doing a 'hard' reset (power and pin-hole reset) with that SD card in doesn't do anything. On the screen is USB at the top, the HP logo in the middle, and V0.21 at the bottom. I tried running the pnewbootloader DOS bat file in XDA tools, but it just seemingly hangs. Pressing power/pin-hole reset does a reset, and now, unplugged from the USB cradle it says "Serial' at the top. It would seem I need a new bootloader to be able to reflash my 'working' phone's flash image. The HP tools to reflash the radio stack software all hang.
I'm able to save the ROM image both phones using the XDA OS Image Tool.
HELP!
I apologize if the answer is somewhere in the forums. I've tried to follow the instructions.

bomp
anyone? I have exactly same issue .. looked all over the world can't find anything that'll work.. everything hangs..

got stuck at 15% then I rebooted the pda

Hi
I have a HTC Cruise(Polaris), I tried a view roms from the Polaris section, but I prefered goig back to my old rom. So when I tried to flash the Dutch Dumped Rom I got stuck at 15% I rebooted the pda. So now all I see are tree colors.
When I try to upgrade the phone to the WWE release version I get: "error 294 invalid vender ID". After it hits 1%.
- How can I CID unlock this phone?
- Joe

With Polaris_WWE_B_20273_1_3_3_V09_Lt_Swtos I get a ERROR [262] : UPDATE ERROR. Even when I retry. Also with the RUU_Polaris_HTC_NLD_SEA_1.28.404.2_radio_sign_25.69.30.05H_1.58.25.14_Ship

anyone can help me out?

Extract the RUU_Signed.nbh file from the downloaded ROM and try flashing from a microSD card. Directions can be found on the boards.

Extract the RUU_Signed.nbh file from the downloaded ROM and try flashing from a microSD card. Directions can be found on the boards.
Click to expand...
Click to collapse
i renamed the RUU_Signed.nbh and pushed down the camera button and rebooted, but doesn't work. Could you shed some light on this?

I have a completely different suggestion. Have you tried a hard reset BEFORE you attempt the burn?
I do not know or have experience of your hardware. I have burned new ROMs on two other makes of PDA and experienced the same problem. A hard reset or return to factory state works.
I have concluded that a burn often fails because the new image does not have enough memory space on the PDA to load the new ROM image and the small program that executes the burn. If you don't go back to the "factory state" by removing all your own installed programs and data first, then there may be insufficient memory to complete the burn. Precisely where it fails in the burn depends upon how much spare memory is available, so in other cases it will fail at a different percentage of the burn.
Worth a try?

solved it with mtty

My FSC-n560 is bricked. Help please!

Hi!
I was using Newplow's WM6 038 ROM with my N560.
Yesterday I tried to write another ROM(WM6 038 with 8MB pagepool) but during update got an error.. It said it just failed.
Now my N560 is stuck on booting screen(people climbing mountain..)
I tried Warm, Cold, Hard reset but with no luck.
Even the power button doesn't work so I had to remove battery. When I insert battery it powers on by itself.
I can enter bootloader screen by pushing power+record button so I tried to copy rom image file to SD card but it doesn't work.
I tried two ROMs(OS_213U.nbf from Original WM5 ROM and Newplow's) and 3 SD Cards(2GB SD, 1GB MicroSD with Adopter, 16GB SDHC)
Is there any recovery tutorial in bootloader mode?
Help me please!
Sorry for my English.

Have you tried flashing a ROM through the computer rather than the memory card? Try going into bootloader and flashing that way rather than the card.

The pagepool ROM is meant for N560s that have been upgraded to 128Mb RAM... have you upgraded the internal RAM to 128Mb? If you have not, then this may have caused your problem.
I had this problem when flashing to 038 normal RAM (from 035). A hard reset reset to the normal start screen, but nothing worked. However, trying a new burn with the Loox flash tool restarted the process and it worked. I found the cure was to make sure you hard reset the N560 before doing a burn. It appears to be that you have to do this to release enough RAM for the burn program to reside and for "working" storage. You may not have done this.
I suggest you try simply re-running the flashtool with SD/SDHC cards removed, battery in place, on the cradle via your PC, even though it appears stuck. The signals coming from the USB link may wake up the bootloader routine in the N560?

Solved the problem! Thanks for your comments!
I asked same question in Newplow's guestbook and the person who made pagepool rom answered. I used MTTY to revive my pda.
What I did is in below post. need translation
http://4pda.ru/forum/index.php?showtopic=55274

Hi all,
I have the same problem. N560 is stick on the himalaya picture. I tried to falsh from WM5 to new rom for Wm6 and after installation the pda stuked. So I did a warm reset and now only the start picture is apperaing. Problem is that battery is down now.
Can someone give more info on the process followed to revive the PDA ? I just cannont read russian (may be Jinsu77 ?)
Many thanks for support in advance

same problem here please please please someone help us
the only thing i can do is the l c:\os_213u.nbf on mtty program and nothing else happend to the machine
sorry for my english

read, and pay attention here:
[email protected]@p://a.mod-site.net/gb/u/newplow-1.html
POST 203.

It was me asking on Newplow's guestbook.
In case you're using Vista, you need some trick to be able to rom update. Read below.
http://www.modaco.com/content/windo...u-on-vista-it-can-be-done-the-ultimate-guide/
And then you need to download MTTY (I used version 1.42, got it by googling) and follow below steps.
(used google translation from 4pda.ru)
------------------------------------------------------------
For rom update without ActiveSync.
1) take this set of extract, copy it to the folder with the firmware.
2) copy the file os_213u.nbf example in C: \
3) You press the button Recorder + food and poke in the hole reset (Recorder button and hold until you eat dolphins)
4) plug the device to a PC, the Task Manager, shooting process - wcescomm.exe
5) Run mtty, choose Port: USB, connect.
6) If mtty caused an error and shut down, simply restart mtty, if not typed commands, then repeat the procedure with paragraph 3.
7) in mtty command, enter: (first letter in kommande - a little l l от слова from the word L L oad)
> l l c:\os_213u.nbf c: \ os_213u.nbf
Since the end of the process will be an inscription about the error, remove the device from the PC.
9) Run rom update, zhmete "next", until you see dolphins.
10), plug the device to a PC and program.
---------------------------------------------------------------
Hope this helps you all

in advance sorry for my english
I am doing all the instructions carefully and the mtty show this
Image Download Finish
OEMFlashWrite(A0000000h,8C200000h,1A0F023Ah)
Download Fails !!!
OEMFlashWrite error(12)
Error : DownloadImage return error (code = 0xFFFFFFFF)
the pda shos the dolphins and the full blue bar
after without change anything i run the PocketLOOX5xxFlashTool that i have in the same folder with the :
EnterBootLoader.exe
OS_213U.nbf (originally rom)
RUUServer.dll
RUU.dll
and the only thing i can see is that the PocketLOOX5xxFlashTool is trying to find the pda without any luck
also the pda is stucked in the same screen with the dolphins and the blue bar
do you see any mistake in this procedure

Helppp!!! please

tuluba said:
Helppp!!! please
Click to expand...
Click to collapse
have you closed EVERY process of activesync before proceding with mtty?

I close the wcescomm.exe and the rapimgr.exe is there anything else?

The pocket LOOX 5xx FlashTool cant connect with the N560 and at the and says that Error"The language in this Flash Image update (ENGLISH) differs from that on your device()!" and i have always english rom exept maybe from the last rom "the killer" with the 128MB rom that i dont know if it is an english or something else because the device never opens to see

After flashing in MTTY(don't care about error messages), you need to unplug your n560 from PC. And then proceed romupdate until you see the dolphin picture. Now you plug n560 to PC and cilck next and wait for a while.. Hope it works!

I change the language of the rom and it works
thank very much all of you

At all they have Probs with flash from SD Card: only use a Card with 512MB! I think a Card greater then can't read by the Bootloader....

hey.
i am compeletly new here. I have the same with my n560. 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)

Need help!!! Please!!!
I bricked my N560. I tried to downgrade from WM6 to WM5 and now I see only delfins and in the first line "2.14.G4" and in the second line "2.15"
What can I do?? How can I flash WM6 or WM5 ROM when there is no connection to the PDA????

ChrisDo said:
Need help!!! Please!!!
I bricked my N560. I tried to downgrade from WM6 to WM5 and now I see only delfins and in the first line "2.14.G4" and in the second line "2.15"
What can I do?? How can I flash WM6 or WM5 ROM when there is no connection to the PDA????
Click to expand...
Click to collapse
You can usually get back to the boot loader if you do a hard reset. I am sure you know how, if not you will find it in the FSC CDROM manual that came with the device. Let us know if this works? I have got stuck at this point too, so I know it works..... hopefully!

Sprint Vogue troubles AGAIN flashing at 29% then stopping???

I am using the 2.31 unlocker and I am attempting to flash the sprint update 6.1 rom from the sprintpcs web site.... and my phone keeps stopping at 29% and freezes there....
The ROM on my lap top has a recover procedure ... which I have followed several times .... with no luck
OH! and thanx to TMZ, for saving my phone last time around!
thanx
Kevie
So, I just flashed from the boot screen, this ROM "Sprint Vogue ROM. exe and what happened is .... runs up to 29% then gives me a ' 262 ' error message.
When I run the un-locker it seems to run that rom correctly also, I can load
23506_v4 ROM
this rom seems to load fine, then when it runs it continually will RESTART the Phone... ???
There have been times when this ROM ran for a while and I thought it was because of battery issues...??? because when I would take it off either the SYNC or the Charger... the RESTARTing would begin.... again I have NO IDEA... what is going on here....
Seems to me that I have not WIPED the Phone clean enough for these roms
I have also tried...
updater_htc_touch
via the sprint web site to the HTC website
same thing it stops at 29%
I thank anyONE in ADVANCE

Have you only tried flashing USB?
What happens when you try to flash the roms via the micro-sd card?
These phones usually came with a little 512MB card.
Format that card Fat-32, 1024 bytes/sector.
If you open up the Sprint.exe rom upgrader (with 7-zip), you'll see a folder.
Inside there are 2 .nbh files. 1.nbh I believe updates the system and phone.
The 2.nbh is the main rom file that flashes all the software.
Copy the 2.nbh file to the 512MB micro-sd and name it voguimg.nbh
Soft-reset until you see the 2.31 coke loader, and it should auto-detect
the voguimg.nbh file and say 'press power' to start flashing.
Best suggestion I can offer - micro-sd flashing is MUCH faster and
has much much less chance of connection errors over the usb cable.

OK I will try that... I had done that already... meaning I have the file on my MICRO SD already but the post I think I learned it from was all about capital letters in the name ... I have renamed it and here we go....???

Doesn't matter the lower-case or upper case for the file name.
it just has to be called: voguimg.nbh or VOGUIMG.NBH
Most important is the name.
Could also try a hard reset first:
Send, End, and push in the reset button, then follow the screen directions.
Once the hard reset is completed, pull out the battery for a minute,
then put the battery back in, and when you power on the phone, immediately
do the soft-reset to get to the tri-color coke screen and then try and
re-flash one of those images.
--------------------
http://forum.xda-developers.com/showthread.php?t=605590
Might also try the NFSFan 1.12 Sprint image in that post.
That one is based off the original 6.1 Sprint download.

seems like you may have the wrong sprint rom..
Even if your phone was locked you should be able to load the sprint update with no problem..
but the fact that you can load a custom rom tells me your phone is most likely unlocked, the resetting is most likely due to the fact that you have a non-gps radio from not having the sprint update.
go to the htc website, then to support, touch (sprint), downloads then finally click the download link on the rev a 6.1 update
After you flash that update rom you should be able to load any custom 6.1 or 6.5 rom
hope that helps

I've had the same problem in the past. Flash a Sprint WinMo6 ROM and unlock it to 2.31. Then you'll be able to flash a Sprint 6.1 ROM. Hope this helps

I had the same exact problem once and it was because I had a bad battery. Changing the battery should resolve your issue.