ROM flash crashes - incorrect version? - MDA, XDA, 1010 Software Upgrading

Following my post of a crashed flash with 5.17 Wallaby, I have managed 5 hours sleep in 48, downloaded every possible image and tool.
The problem IS NOT IN THE FLASH IMAGE nor is it in the device.
Even with a crashed bootloader "Will take about 5 mins"
the device WILL still talk via USB cradle and ActiveSync, just hit cancel and continue.
But here you say, it complains the image file is of incorrect version with device.
WRONG - THIS IS A WINDOWS REGISTRY PROBLEM
The registry [using XP, not sure of other but assume the same] writes the version of the last flash into the key;
[HKEY_CURRENT_USER\Software\WFlashUtility]
"Flash"=dword:00000001
"Language"="English"
"ModelID"="PW10A1"
"Lang"="ENG"
"Version"="4.00"
"USB"=dword:00000001
"FlashFile"="C:\\Program Files\\XDAtools\\binaries\\English\\\\NK.nbf"
"ExtID"="001"
One only needs to modify the values of "Version" and "ExtID" to match what the image file purports to be, and away you go again.
Apparently my device requires cradling again after hard reset to switch on, another 5.17 funny perhaps?
Anyway it works.
Happy to help anyone struggling with same.

Related

Radio Stack upgrade disaster

If I have overlooked the thread that covered this situation, please just point me to it as I have made several searches and read several threads but no luck.
I was happily running a custom 2003 ROM with the original AT&T stack. As I was quite happy with the way my 2003 OS was configured and operating, I decided to just try the NEW AT&T radio stack as I wanted to see if it helped with some reception issues I have expereinced. I copied the four radio stack files to the Windows directory on the PPC. I had the PPC in its cradle for power. I then executed the RSUupgrade and at 10% it locked down completely. No hard key had any effect and in fact, not even the soft boot buttom worked. I then attempted a cold reboot and that resulted in a hung machine again.
So, I decided to take the safe route and do an SD flash burn back to the original AT&T ROM (which I had copied way back when). Using XDA Tools I burned it to my SD card. Did the soft/on button routine, and proceeded to flash the memory. If indicated that the checksum matched and was finished. After the cold reboot, I got the old splash screen, but it took forever for the today screen to appear and the START button as well as ALL the indicators at the TOP are missing. I am unable to get to file manager.
I then decided to see if I could connect via ActiveSync. I uninstalled AS3.7. and reinstalled the original 3.5. When I attempt to connect, AS does see that the PPC has been docked, but it is never able to connect.
So, I am unable to reinstall a radio stack of any kind. I am unable to get the OS to function normally.
BTW, Just for grins I also tried an SD card install of the newest AT&T ROM as well as my custom ROM and the results are all the same. I suspect the now corrupted radio stack, but HOW do I purge it and start over when I can't get the OS to boot sufficiently to reinstall the stack
ANY IDEA? HELP!!!
Come on, someone has to have an idea
I will start off with an update. After reading another thread, someone mentioned that initial boot was taking about 15 minutes when there was NO radio stack. I decided to see if that might be occurring to me and sure enough, after about 15 minutes, the PPC beeped and the OS came up. If was still a bit sluggish, but operational. I was able to successfully attach to my PC via ActiveSync.
Now for the downside. Still NO success with installing the radio stack. I have tried reflashing the OS back to the original AT&T PPC2002 OS but that made no difference. I have tried both the original radio stack and the new one, no difference. I have tried to install the stack with the SIM card (SIM not SD) in and out, no difference. It always sticks at 1%, tells me the upgrade failed and to press ok to reboot. I did read the thread that gave LOTS of help regarding this issue, but nothing seems to help. I can remove the lnk in the startup folder, delete the files, reboot, recopy via ActiveSync, start the upgrade (RSUpgrade.exe) and everytime it immediately goes to 1%, sets there a minute or so, the pops up the failure message.
Surely, someone has an idea. Could a corrupt SIM cause this? Is there a alternate way of installing the radio stack?
BTW, just for grins, I thought I would try doing a "normal" exe upgrade since AT&T posted such. I know that it is full of risk, but at this point, I had little to loose. I made sure that I was running ActiveSync 3.7.1 and was connected. I then launched the upgrade. It came up with a splash screen with some warnings and the typical stuff. I then selected the "next" button and nothing happened except that cursor (when pointing in the window) went into the "working" state where it remained until I finally killed it about 30 minutes later. There was NEVER any sign that progress was being made.
HELP!!!
david
I have the same exact problem.
The Start menu is missing. No Icons on the top bar.
What's funny is that the screen seems to be inverted.
When I tap close to the bottom of the screen, the clock setting screen appears.
Anybody have a solution?
I suspect there is an alignment problem
When I first boot up after ROM upgrade, I can get to the today screen with the volume button, but I can't get to the file explorer because the start menu is missing.
When I tap on the lower part of the screen, the upper part responds.
Could this be due to the alignment steps being bypassed?
What order do you have to tap the alignment crosshairs during startup?
This sounds like a different problem
As I mentioned, on my first reflash of the OS after the radio stack upgrade failure, I got the today screen without the start bar at the top (ie it was totally blank and tapping in that area did nothing). Everything else on the today page worked. On subsequent reflashes of the OS, the today page was totally normal, start button, everything in place and working. On those subsequent reflashes, I also got the normal initial screen alignment pages on the first boot after the reflash.
I will also post, that I finally gave up on getting the radio stack to install. I have sent my unit to the guys at PPCTechs. In talking to them, they have 2 other SX-56 units in for upgrades with the same radio stack issue. They feel that they will be able to force the reflash via alternate means using a serial cable. As I mentioned on the other thread where I have been posting, I will post back once I hear if they were successful.
David
in general people should not mess with radiostacks unless they have issues and the radiostack is recommended by the phonecompany one use

Magician hacking?

I tried to reflash my Magician. No success .
I think smth was fatal on reflashing of extended ROM part. Or device id data was erased.
1. I can switch on the phone only after battery removing (hard reset performing). Everything is working.
2. BUT - I can't do soft reset. I get dark sreen with "serial..." sign If I want to switch phone back again I have to do #1
3. There is no Ext ROM (even if I try to run loadvdisk.exe program) at all!
4. When I try to reflash from working phone (I want to get back to my previous ROM), at first everything is OK (fist checking of device is passed). Program detects current ROM versions and suggest to upgrade to another). But when I press "upgrade" button it begin to check device information again and freeze for several minutes. Then it report connection error 101 or get device data error.
5. If I try to reflash from dark screen with "serial" sign - I get error 201: get device data error. Even not first checking passed
6. I tried also SD card to reflash. I use English T-mobile ROM and ntrw.exe. SD card looked like unformatted after the procedure. I press camera and power button and reset - but nothing happenned .
7. BUT! I downloaded modified upgrade file Himaupgrade.exe from here -http://forum.xda-developers.com/viewtopic.php?t=9047&highlight=himaupgradeut+modified And when I run it in "dark screen" stage it is triing to do something. No device data error, program even begin to erase old ROM. But then doesn't work because it is different device and ROM from Himalaya is not suitable for Magician. But as I understood modified file skip device ID checking.
I think if somebody can modify Maupgrade.exe file (for Magician ROM upgrading) - it will helps.
Or any other suggestions? I tried bootloaderfix program, but doesn't work.
It is strange - phone is working, but I can't do soft reset and can't reflash

M6 upgrade failed (remained in RUU). How to fix it?

I have Cingular 8125 unit with Mobile 5.
Tried to upgrade to version 6 and apparently I screwed.
- First I created a backup with a SpriteBackup and got a file "PocketPC_Backup_2007-08-29.pbf"
- Than I run "MDA_software_update_226102_22610105_022511.exe". It failed, but after the reset I was able to get back to the OS.
- Than I tried "ROMUpdateUtility.exe". It went to 99% and than crashed. After the reset I am getting three color screen with the following:
RUU
IPL 2.25
SPL 2.25
USB
I tried to recover, but it is asking me for ActiveSync. The ActiveSync is not running because the phone is in the RUU mode.
Now, how to restore the operating system from the RUU mode?
How to read CID block of my device from RUU mode?
I already read the following threads:
http://forum.xda-developers.com/showthread.php?t=315178
http://forum.xda-developers.com/showthread.php?t=298613
http://forum.xda-developers.com/showthread.php?t=285435
but all references are referring to a "live" unit with ActiveSync. Nothing about loading from RUU.
I appreciate any advice.
i have the same problem...any solutions
It was fixed.
I went to:
http://www.america.htc.com/support/8125/software-downloads.html
and downloaded the following software: RUU_Wizard_225111_22511102_022511_CWS_WWE_Ship_1.exe
Please note:
The download speed is 7-8 kbps. It took few hours to download 53Mb.
The procedure:
- Press and hold the Photo and Power key buttons to enter into the RUU mode
- connect a USB cable
- double click on "RUU_Wizard_225111_22511102_022511_CWS_WWE_Ship_1.exe"
- Follow the menus and wait 10 min
It will stop on 85% and you may think that it failed, but just wait.
i ran that and it said my nbf file or something is outdated....

Why ActiveSync always disconnects the BA while upgrading to the new ROM.

I have upgraded from WM2003SE to WM6 (the first released from XPlode version OS 5.2.1620 build 18125.0.4.2) without any problem. Now I want to upgrade from that version to the current release, but the ActiveSync (I am using 4.5) always disconnect after MaUpgradeUT_noID has detected the previous installed OS. So I got an error message like "cannot to the device" or so. It happens everytime even I just try to upgrade the Radio rom.
I have also tried to use ActiveSync to version 3.8 (I found this suggestion from this web site) but bad luck it can't detect my BA device at all. I have also tried to revert back to WM2003SE but still get the same problem. My system is WinXP SP2 & O2 IIs. So Please help I am in the dark right now.
Same problem here...
su2003 said:
I have upgraded from WM2003SE to WM6 (the first released from XPlode version OS 5.2.1620 build 18125.0.4.2) without any problem. Now I want to upgrade from that version to the current release, but the ActiveSync (I am using 4.5) always disconnect after MaUpgradeUT_noID has detected the previous installed OS. So I got an error message like "cannot to the device" or so. It happens everytime even I just try to upgrade the Radio rom.
Click to expand...
Click to collapse
get into boot loader mode,then try
(press record button + power button and reset at same time)
addan said:
get into boot loader mode,then try
(press record button + power button and reset at same time)
Click to expand...
Click to collapse
Have tried that already but still get the same error. I have even reformatted my PC and reinstalled WinXP and ActiveSync 4.5 just in case there are viruses or so but also get no luck.
Did you soft (or hard) reset your BA and reboot your PC after failure? (Try clean upgrade, and in bootloader).
Did you (succesfully) establish an ActiveSync partnership before upgrading?
Did you try unchecking Enable advance network functionality in USB to PC (under settings, connections)?
Did you soft (or hard) reset your BA and reboot your PC after failure? (Try clean upgrade, and in bootloader).
Yes, at this time you asked me. Nothing changed.
Did you (succesfully) establish an ActiveSync partnership before upgrading?
Yes.
Did you try unchecking Enable advance network functionality in USB to PC (under settings, connections)?
Yes. I did it.
More over, if I started BootLoader mode before execute MaUpgradeUt_noID.exe the program get struck while performs device information checking, I have to pull it out from Sync station the program then continue running but without any information (like the existing OS version etc.)
how long did you wait for the program to respond before you find that its stuck ?
Here it takes about 2 min to find the device
Proper upgrading procedure, as it was said 10000's of times
1.put your device in bootloader mode
2. place it to cradle
3. kill activesync (optional - if you dont do it the upgrade utility will do it for you, but sometimes activesync stays on and fail the upgrade process)
4. start upgrade utility and follow the onscreen instructions
5. perform hard reset (the three options thing)
thats all
Xplode's new cube cab
deleted... off topic
how long did you wait for the program to respond before you find that its stuck ?
It was about 5 min and the program still had no responses. I then have to pull it out and the program continue running but without any information (like I had mentioned it before).
Here it takes about 2 min to find the device
Unfortunately not with mine.
Proper upgrading procedure, as it was said 10000's of times
1.put your device in bootloader mode
Yes. I did it.
2. place it to cradle
Yes. I did it.
3. kill activesync (optional - if you dont do it the upgrade utility will do it for you, but sometimes activesync stays on and fail the upgrade process)
I have tried it both with and without killing the activesync.
4. start upgrade utility and follow the onscreen instructions
Yes, but once I started the upgrade I have noticed that the activesynce has disconnected my device.
5. perform hard reset (the three options thing)
I didn't have chance to go to this point.
thats all
I think the main problem is the activesync has disconnected my device suddenly when started the utility. I have also tried to take out anythings that using USB port like mouse, ext. DVD, printer, scanner just in case the upgrade utility may conflicts with those devices.
I think I shall try to change the PC to upgrade my device to make sure that it wasn't caused from hardware defection.
su2003 said:
4. start upgrade utility and follow the onscreen instructions
Yes, but once I started the upgrade I have noticed that the activesynce has disconnected my device.
5. perform hard reset (the three options thing)
I didn't have chance to go to this point.
thats all
I think the main problem is the activesync has disconnected my device suddenly when started the utility. I have also tried to take out anythings that using USB port like mouse, ext. DVD, printer, scanner just in case the upgrade utility may conflicts with those devices.
I think I shall try to change the PC to upgrade my device to make sure that it wasn't caused from hardware defection.
Click to expand...
Click to collapse
With regard to your last remark: you stated earlier you did a fresh reinstall of XP. Now, why would you install and connect all these peripherals if you only want to upgrade your BA rom??? All you need is a fresh WinXP and ActiveSync...
Did you really do a fresh install and follow the wiki and the tips mentioned again (and again)?
You are getting me (and probably all of us) confused.
Your answers to especially points 4 and 5 of xplode tips to me clearly indicate that you do not really take (enough) time to understand the procedures (or what you are doing) and want to have WM6 running asap with no effort at all...
Your remark "I think the main problem is the activesync has disconnected my device suddenly when started the utility" only confirms this as this is the whole point of boatloader and was furthermore indicated it would do exactly so by xplode earlier on.
Please do take time and hence show consideration to all of us that are trying to help you in preparing yourself properly before trying to attempt any further upgrade.
Good luck!
With regard to your last remark: you stated earlier you did a fresh reinstall of XP. Now, why would you install and connect all these peripherals if you only want to upgrade your BA rom??? All you need is a fresh WinXP and ActiveSync...
Did you really do a fresh install and follow the wiki and the tips mentioned again (and again)?
You are getting me (and probably all of us) confused.
First of all, Sorry if I make you and other confused. I have began to unsuccessfully upgrade my device since Friday. So I decided to help myself at first by try to do everything I can do by myself. I have formatted PC HDD and also reinstalled activesync because I thought the utility may conflict with other program on my PC or from Viruses. I have also tried many ways with hard reset and cold reset etc. to upgrade my device but have no luck. That was with very fresh new installed WinXP PC. Unfortunately, I have to use this computer for my job also. So that's why I have to install printer & scanner driver including MS Office, AutoCAD and other necessary program to serve my job . I have falled with upgrading but I do not want to have problem with my job. Hope you understand my essential.
Your answers to especially points 4 and 5 of xplode tips to me clearly indicate that you do not really take (enough) time to understand the procedures (or what you are doing) and want to have WM6 running asap with no effort at all...
Since I began to upgrading and everytime I have executed the utility I have always wait & wait but I just never look at the clock to see how long I have waited. Xplode has just warned me to take enough time so I started to upgrading but with clock at this time. I have already mentioned that I have successfully upgrade from WM2003SE to the WM6 (previous version) so as a user I have enough experience and know what I am doing.
Your remark "I think the main problem is the activesync has disconnected my device suddenly when started the utility" only confirms this as this is the whole point of boatloader and was furthermore indicated it would do exactly so by xplode earlier on.
This is just my opinion to let you guy see and understand the problem. That's it.
Please do take time and hence show consideration to all of us that are trying to help you in preparing yourself properly before trying to attempt any further upgrade.
I think I have already put a lot of effort about upgradind my device. I have reformatted and reinstalled all necessary programs. It took me out almost half a day to do this. And not only with my PC I have also reinstalled all programs on my device with an old OS version since I have lost them all from hard reset. Other than that I have also tried & tested upgrading the device during the time. The only word I can say that It was not funny to do all of this. It was not really a hard job but it took almost my weekend time.
Good luck!
Yes I do need it barely. Actually I have already felt a little lucky got from all of you that try help me solving the problem. Thanks.
su2003, nice answer.
His main problem is that he does not understand that activSync will work if the device is in a normal state but when device goes to bootlogger mode, its only USB connection that will help a PC to talk to Device and not activSync.
April 1 said:
su2003, nice answer.
His main problem is that he does not understand that activSync will work if the device is in a normal state but when device goes to bootlogger mode, its only USB connection that will help a PC to talk to Device and not activSync.
Click to expand...
Click to collapse
Thanks for your additional.
I have also tried using different PC to upgrade the OS but got the same result.
you have to be sure that your BA when cradled display USB (after getting into bootloader mode) instead of serial 2.06 than run the upgrade utility
I am quite sure that the screen has displayed USB but the number is 2.07 not 2.06. I am not sure about the meaning of the number, it could be the version.
I have also brought a new USB-XDA IIs cable yesterday, just in case the cardle was defected but it doesn't work also, I have got the same result.
khanem said:
you have to be sure that your BA when cradled display USB (after getting into bootloader mode) instead of serial 2.06 than run the upgrade utility
Click to expand...
Click to collapse
I am quite sure that the screen shown USB 2.07 (should be differ version than your).
I have also brought a new USB-XDA IIs sync cable but getting the same result.
Conclusion:
Bad Hardware(Flash ROM)?
Your Bootloader is toasted or had it's LAST flash of it's lifetime???
We can say that... but hopefully not for your sake.
Because as you have said you've done EVERYTHING that was posted.
and though our Senior's "inputs" didnt worked out the way it SHOULD work.
I cant say it's a waste of time to answer your questions.
But there are no more questions to ASK
and there are no more questions to ANSWER
They're all been said here.
All you have to do is PRAY HARD leave the BA rest for a day...
remove the battery...
think things out, clear your mind... sleep...
then execute Xplode's Walkthrough from Step 1 the next day.
but be sure to have the battery fully charged.
Your BA is not dead and your bootloader is not toast. The only problem you have is probably you are impatient. Go to the Wiki and follow the procedure exactly as it is written. It will work. By the way, if you kill Activesync (ie disable USB connection in activesync connection setting), put your device in bootloader mode and connect your usb cable (in that order), run the upgrade and it will work. Forget about activesync.
su2003 said:
I am quite sure that the screen shown USB 2.07 (should be differ version than your).
I have also brought a new USB-XDA IIs sync cable but getting the same result.
Click to expand...
Click to collapse
I use xda IIs and the bootloader mode shows ver 2.07, and i dont have any probs installing. I dont think the version 2.07 has got something to do with your problem.
You said that you tried other pc and it doesnt work, and it worked before when you upgraded previously. I think you know enuf about upgrading if you have done it before....
did you have problem with sync connection before? I was just thinking maybe there is something wrong with your BA....like actual hardware problem with the cable connection??
what about firewall? would it affect it - I doubt it cause its not in sync mode.... but at this stage, maybe just try all possibilities to try to get it working.
Good luck
Mhm. I'm not sure I've really followed all the intricacies of this case ... But whatever, here's my two cents for a safe upgrading procecedure:
1) use a cradle, not a USB cable, and make sure the cradle's
power supply is plugged into a wall outlet. It also helps to make
sure the cradle is plugged directly into the PC, not via any kind of
USB hub. No other devices should be connected to that same USB
channel. I suppose temporarily disconnecting other (unneeded) USB
devices from the computer can't hurt, either.
2) I guess "kill ActiveSync" can mean various things ...
however, here's the best way to do it I think: as sofene mentioned,
disable USB connections (what the hell - disable ALL connections) in
ActiveSync settings. Then reboot the PC. No need to look for ActiveSync
processes and kill them manually -- disabling the connections will take
care of that. Rebooting ensures that ActiveSync's driver code is really
unloaded.
3) remove SD card and, for good measure, SIM card from the BA.
4) perhaps soft (or even hard) reset your device
5) put device in Bootloader mode
6) insert device in cradle, start upgrade utility, off you go ...
By the way, ActiveSync has got nothing to do with the ROM upgrade utility, and it should therefore not have been necessary to re-install ActiveSync, etc. You just have to make sure it does not get in the way of the upgrade process. As far as I understand the process, the ROM upgrade should work equally well on a PC that does not even have ActiveSync installed.

[HELP] HTC HD2 cant boot after hard reset or hard reset failed

hi guys..
please help me .. i flash my HTC HD2 with a MAGDLR111 and after it doesnt continue to boot and only stock in boot image. i try to use Hard Reset (holding down the up and down botton and tapping the power button), it response very quick but it says the "restore completed and press up botton to reboot" and so i did but still, it still stock up in boot image forever.. please help me, what should i do..thanks
Possibly a radio problem. Boot pressing volume down button to get into bootloader and flash a radio WITHOUT .51. in its name....
Sent from my Nexus One using XDA App
thanks, already did... and it works.. )))
hey i have that same problem now can you help me get a radio so i can download it or can even help me through the steps to get back my phone to normal plzzz.? thank you
Any new user most definitely has a lot of questions...
Here is a thread you should carefully check - it explains some basic stuff, and it offers links to many other specific threads, incl. Radio ROM.
To return to "normal" ROM, please just check the standard flashing process. You can flash via USB or SD card, whatever ROM you like, stock or custom.
Hey man thanks for all that but i really don't want just any rom, i wanna know if anyone can get me the rom that comes with the phone for windows mobile 6.5, you know with the orange load screen etc, i really dummy in this thing and i should not of even played fast to go try flashing my HTC HD2 with a MAGDLR111.
so i've tried various roms and everyone of them was going great unitl step 2 in the upgrade process, it kept saying error filr open, check update rom utility. where do i go from here?
It is quite difficult to help if there is so little basic information available.
The error you mention can have a simple reason. Usually, the ROM image file name is simply not correct.
To flash via USB:
There are 2 options:
First, you can take an original RUU of your network operator (in case you have a branded phone) or HTC, put the phone into boot loader mode (see below), start the RUU.exe on your PC.
Second, you can extract the original RUU.exe with WinRar or a similar program, take the .nbh file and rename it to leoimg.nbh.
Once you take an image of the ROM, you have to put it into the very same folder where your ROM update software is (LeoCustomRUU, SSPL, whatever). One more time, please check the suffix, it should be .nbh, as in "leoimg.nbh".
Keep in mind: Do start the RUU software as "Admin" - whichever you choose.
Instead of the original ROM, you can flash custom ROMs, too - since your device must have HSPL installed when you used WP7 or Android before.
If you´ve got issues (because of Win 7 on your PC or such), please try to put your device into bootloader mode before connectint it to the PC (turn off the device, push vol. down and power at the same time, the multi color bootscreen should appear, only now connect it to the PC).
To flash via SD card:
Re-format your SD card FAT32. Don´t put anything else on it. Copy the ROM image file with the exact naming as above on the SD card.
To start the flash process, do the same as above, go into bootloader mode, the flash process will start - just follow the on-screen instructions.
i have this same problem only it happened without me flashing anything or something like that. i dont have custom rom or hspl. everything is stock. what should i do?
bump ^^
The message you have entered is too short. Please lengthen your message to at least 10 characters.

Categories

Resources