Related
Hello All
Today I tried to upgrade my XDA. I used an usb-hub, wich caused the upgrade to hang . After this my XDA was dead.
I have read that it is possible to flash my device by using my SD card.
What I need is a bootloader (*.nb0) and a windows CE (*.nb1) file. My provider is O2-NL. Eng. europe version
Can anyone help me plz :?:
Eric
You do not need the bootloader file, the bootloader should still be there. Try holding the power button pressed while performing a soft reset (large hole), and see if the bootloader comes up.
The OS you already have, it is the large .nbf file that came with the "Programme A" upgrade software (in the 'English' directory). Just download XDA Rom Image Tool and write that nbf file to an SD card and away you go.
(Life gets a little bit more complicated if you have version 5.17 of the bootloader, but it's all documented on this site.)
Good luck...
XDA Died
After a botched upgrade, I too was left with a dead XDA, but I went down to the store where I bought it (Oxford street London by the Bond St Tube station), and there I befriended one of the guys, asked if they had a charged XDA in store, explained my situation to him, and then downloaded the flash from one of the store phones. It took about five minutes, but subsequently, my phone is back in business!
Much better than mailing it in...
Jim
i still have my xda not work, dunno how to flash it again coz dont have usb card reader. i just have 2 xda with 5.17 bootloader and 1 sd card 256m,need help soon
The situation, that you have 2 xda, make the situation much easier.
(Thinking, one of them is working....)
Make a backup of the CD-Card and insert it into the working xda. Enter the bootloader and make a rom Image to the sd card.
(may take a while)
Then insert the sd card in the malfunction xda ant enter the bootloader mode. It shows you a screen, that a rom-Image is found on sd, and asks you if you want to install it. Just do it.
This take also a while.
Questions about the bootloader will be answered at this webpage here.
Attention: Data on SD will be lost in this process, so be sure, to make a copy of the data...
Regards
Stefan
thx LumpiStefan for the answer,
but there is a problem coz 2 of them are using the same bootloader 5.17 that have some security feature so i cant make a backup from the working xda,
anything else i can do??
love u all,thz
(Was: Help me... Help me... Help me... Anyone help me !!!)
Hi all!
I stuck in WM2003PE v. 4.00.10. Since I have been updated to it, my XDA cannot use phone function. Cannot receive calls and while I make a call... appear a popup menu from signal: "The operation failed". I so sad, I don't know what to do now :x . Anyone help me ???
My XDA is:
Wallaby Bootloader: 5.17
ROM version: 4.00.10 (I feel a vindictive hatred for it :x :x :x )
Radio Stack: 4.21
I'm from ASIA
As you known I can not downgrade from this ROM version by exe file.
I can not downgrade from this ROM version by SD card because my Bootloader is 5.17
XDAtools is a new tool. Can I use it to downgrade my XDA? Tell me method by detail, please (sorry, I don't want to sad again).
Thank for all
You CAN downgrade to say, 3.17 (Thats my TMobile version) if you have the nk.nbf file and use the XDA Tools.
You have to do it via the Wallaby Boot loader method... by placing the ROM on an SD card (via XDA Tools). To do this, I think that you need an SD card reader, as XDA Tools does not seem to do it via the phone...
There are instructions on how to do this as well as
A BIG WARNING about 5.17 boot loader.
I did it on my TMobile phone, with Bootloader 5.15.
So, do NOT follow the instructions I have stated here, read on this site and in the forum about how to flash your rom via the SD CARD Method.
That should do it for you..
BTW, when you write the ROM to the SD CArd, it WILL erase the SDCard data, so save off your stuff before you do this.
J
Thank jta
But, How do I have to downgrade my Bootloader from 5.17 to 5.15?
I tried XDAtools but no success
Anyone idea?
Hi VHS,
My XDA had bootloader 5.17 like yours, and I was stuck with T-Mo 4.00.10 also. I was able to correct the situation though, by doing the following:
I changed the bootloader with XDAtools from Jeff (it has 5.15 included), by running the “Fix broken bootloader” part of the program.
Then, I used SDcard/bootloader method to go back to 4.00.05, and successful. I knew I could use XDAtools also for doing this, but I preferred the SDcard/bootloader’s way then. Mind you that, using SDcard/bootloader’s way was very easy after you downgrade from 5.17 to 5.15. Since then, I could flash whichever rom I want, but not 4.00.10.
If you want to do the same, please read as much for the detail from the various forum here and carefully.
I hope this helps.
Hi beeheij!
Can you tell me the way in order to downgrade my bootloader from 5.17 to 5.15 by detail? I tried a lot of time but no success. I don't know why. And you tell me go back v.4.00.05 by SD Card.
I'm grateful to you very much
Has it occured to you that
"Help me... Help me... Help me... Anyone help me !!!"
is a really, really, really bad subject line ? I changed it to something which may get many more people to take a look and possibly help you...
If you can still use ActiveSync, you could try to use Jeff's version of the XDAtools to downdgrade the bootloader to 5.15, and work your way out from there...
Can somebody please help me.
As I posted in this post, I scr3wed up my buddy's AT&T SX56.
I have got the thing past being dead, by putting a custom ROM on it.
However, I really need to get this thing back into AT&T mode, with either 2002 or 2003 on it. I will then upgrade to 2003.
Does anyone know where I can get a virgin AT&T ROM so that I can re-flash his system.
Thanks.
-=Nick=-
nickpoore said:
Can somebody please help me.
As I posted in this post, I scr3wed up my buddy's AT&T SX56.
I have got the thing past being dead, by putting a custom ROM on it.
However, I really need to get this thing back into AT&T mode, with either 2002 or 2003 on it. I will then upgrade to 2003.
Does anyone know where I can get a virgin AT&T ROM so that I can re-flash his system.
Thanks.
-=Nick=-
Click to expand...
Click to collapse
Check out Yorch.net
Okay, I'm making SOME progress.
Firstly thanks for the youch referral from kwlandry.
I had found the rom kitchens this afternoon while looking for solutions...
I'm busy flashing the ROM from SD for the umpteenth time.
It seems that whenever I flash the SX56 with an AT&T 30.09 ROM, then I get a hang on reboot.
I am currently trying the 4.00.05 ENG ppc2003 from yourch as it seemed to be non-specific (and a non-TMobile) one.
I seem to have the latest Radio stack (RA.33.02), and have been able to get a couple of ROM's to work.
Does anyone have ANY idea why the AT&T 30.09 ROM would fail in the same place every time? This is definately an AT&T unit, at is has the logo on the front. The phone was originally locked, but has been unlocked during the process.
I'm busy reading/searching the forum, but haven't seem to find this problem anywhere.
Thanks for ANY help.
-=Nick=-
I fixed many XDAs with your problem!
you could send the XDA to Siemens to repair/exchange.
Try flashing back to the original ROM via sd method then upgrading to wm2003.
You can get a copy of the 2002PPC ROM at siemens website. Cut & Paste the following link.
http://www.my-siemens.com/MySiemens...%2FMC%2FMC%2FSX56POCKETPCPHONE%2Fdesc,00.html
Extract the file to a directory, then use the XDA OSimage tool to write to SD card then use bootloader to write to ROM.
After a successful flash follow the same to upgrade to wm2003
You can also try this kitchen http://lumpistefan.dyndns.org/
BTW - the phone has to be fully charged. That might be the cause of your hanging issue.
I have posted this in answer to your other post, try using a diferent memory card for upgrade to wm2003, I had this problem when using an mmc memory card to upgrade to WM2003, it hung every time even though it seemed to complete correctly, I changed to a different memory card and had instant success.
Yes! I agree also. But, though "mmc" and "sd" cards are similar, in this case the process calls for an sd card. The size doesn't seem to matter, I use a 512mb, however some people have had issues with device detection. So, a 64mb card is recommended. Make sure it is formated before use. And again a fully charged phone is unlikely to have problems so save your battery till all requirements are in place. Also DO NOT DO A HARD RESET! untill you have a successful install. You could lose you GSM ROM.
Thanks for all the replies.
I have successfully flashed back to the original rom; I downloaded it from yorc.
Having got the device back up and running, I tried the upgrade to 2003 again; using the Siemens software in the cradle solution. Didn't work.
The battery was definately fully charged (90% or higher) at all times.
I will look to try another SD card, and see if that makes a difference, it just seems strange that the card works to restore WM2002, and either card or USB approaches to upgrading to WM2003 fail.
The card I've been using is a very generic 128MB MMC card.
Again, thanks to everyone for their suggestions.
Hi,
I seem to have made my MDA compact II a brick. I was having problems hard reseting it (Format FAT failed) so I tried upgrading to a different firmware.
I now have the RUU_Prophet_2151327_21513121_021921_DOP_ASIA_WWE_Ship-NoVendorID
firmware on it. This is not good as it is for the Prophet, although it says in the Wiki that this should work. Anyway I can now hard reset the phone, so all I need to do is flash the TmobileUK firmware back on it. The only problem is that it doesn;t let me do it. It says error:296 upgrade only.
Anyone any ideas?
cheers.
extract the contents of the t mobile package using win rar
download
ftp://xda:[email protected]/Prophet/Tools/ROMUpdateUtility-NoVendorID.zip
and put in the same directory and run.
It gets to 1% then says invalid command, not for this phone.
Latest T-Mobile ROM is at http://www.tm-phonedownloads.com/download_manager_mda_com2.html
very stable, much better than the original shipped ROM
Finally got it back.
If you have a T-mobile MDA II (Charmer), then Flash it with a Prophet ROM, the only way I could get it back was to use the following:
RUU_Charmer_100_100_049_CHS_Ship.rar
typho5 -x nk.nbf
Then created a new nk.nbf with the output using nb2nbf.
I then Flashed this with Wizard_RomUpgradeUtility_noID
And miracle it started. I quickly CID unlocked it and am now flashing with latest T-mobile.
My problem was that the Rom Update programs wouldn;t read version 2.xx ROMS.
Anyway it has just finished and looks fine. Thanks for everyones help, now I just have to get my SD wifi card working.
How do you do it
Hi I just got a MDA compact II from T Mobile UK I would like to upgade the ROM but its all very new to me since you know what you are doing can you post an idiots guide to the process.
Hope you can help
Hi, it depends what Rom you want to upgrade it to, the latest one from T-mobile is pretty good. There is an unbranded one (no T-mobile logos or suchlike) or there are Roms in different languages. It depends why you want to change the firmware and what to.
I suppose I don't really know the problem is as I just got the thing did some searching and came across this site read your post and thought i want to do this maybe you have some suggestion. Also I tried the RUU mentioned in an earlier post but it I can't update when I get to the from/to screen it tells me I will go from 2.6.2.110 to 2.6.2.110 I was expecting to move up.
daveh1171 said:
I suppose I don't really know the problem is as I just got the thing did some searching and came across this site read your post and thought i want to do this maybe you have some suggestion. Also I tried the RUU mentioned in an earlier post but it I can't update when I get to the from/to screen it tells me I will go from 2.6.2.110 to 2.6.2.110 I was expecting to move up.
Click to expand...
Click to collapse
Sounds like you are running the latest version. Is there a problem with the phone? If the phone works fine, I would just unlock it using lokiwiz02b (So you can use any network card) and then EnableRapi (So you can run unsigned code) then CID unlock it using awizard (so you can use any Brand/Language of ROM).
If you have no problem with the firmware I would leave it alone.
Hi,
Yep, I'm in the same situation, why does the prophet firmware load onto the charmer without erroring? !!!
Anyway, I have a copy of RUU.rar but I'm having problems working out what I need to do to it between unpacking and flashing the phone (i.e. the typho5 bit and then the nb2nbf).
Can someone please help me out?
P.S. The phone just sits at a black screen that says 'Dopod' across the front at the moment
Can anyone tell me how to 'force' a downgrade of firmware? I've got what appears to be the right firmware from FTP but it won't over write the incorrect version 2 installation as the uploader software thinks it's later therefore better.
There has got to be a better option from the command line surely?
HELP phone is dead
Chirpy said:
Can anyone tell me how to 'force' a downgrade of firmware? I've got what appears to be the right firmware from FTP but it won't over write the incorrect version 2 installation as the uploader software thinks it's later therefore better.
There has got to be a better option from the command line surely?
HELP phone is dead
Click to expand...
Click to collapse
Progress, but now it works only from the charger so the shipped ROM upgrade won't work as it reports the battery as being at less than 50%.
Anyone know how to force a ROM upgrade or where I can find the right ROM files to use awizard to do this?
Dear all,
First of all, many congratulations for the great forum and thanks for all the support given here.
Now, I recognise that problems similar to mine have been discussed elsewhere, so I apologise for opening a new post, however with all the material that I could find, I got a little bit lost, so here is the story.
Some 5 days ago, the screen on my HTC Elf stopped responding to any sort of touch. The green, red and action buttons were working but no touch screen.
I have read several posts, and concluded that one possible problem was a corrupted ROM, so I downloaded latest Onyx ROM and installed it. Phone was upgraded successfully and screen started to work again.
However, the first time I switched it off and then turned it on again, it did not boot up. It gets to the point where it displays Smart Mobility and then switches itself off. The orange light then comes on for about 6-7 seconds, then off for 1-2 seconds, and then on again......
Now it does not seem to be able to charge, but if I switch it on with the camera button on I am able to get to the ROM screen (the 'rainbow screen'), so I have hope that it is not dead.
What can I do to attempt to revive the phone please? Is there a sort of 'format' that can be given so that one can start flashing ROM, etc. from scratch?
Many thanks.
PS: Except for the above, I consider myself as a total beginner in this area.
Hearing that the touchscreen started working again after flashing the ROM, I would conclude it's a software-issue.
In the rainbow-screen, what SPL does your phone run? If it ends with 'cmon', you've installed HardSPL. That means you can flash your phone from the rainbow-screen. Given that your phone won't boot, you should try to flash a new ROM from the rainbow-screen. But first, you have to confirm that you've installed HardSPL.
Good luck!
@mrqips - many thanks for your reply.
The screen says that:
IPL 2.20.0002
SPL 1.11.0000
xumiking said:
@mrqips - many thanks for your reply.
The screen says that:
IPL 2.20.0002
SPL 1.11.0000
Click to expand...
Click to collapse
Sorry Buddy.. It seems that you didn't use HardSPL, unfortunately you won't be able to flash any other ROMs..
Yet.. You might be able to use the Gold Card Method.. Give it a try and see what would happen..
Another point is.. I'm very interested to know how did you flash Onyx ROM.. without using HardSPL nor USPL (as obvious from your IPL), I would say that you used the "White Screen Method" which is by the way.. the least safest way..
Hope That Helped...
Thanks for your feedback.
Actually, I happened to be reading the post by @sbettencourt in this thread:
http://forum.xda-developers.com/showthread.php?t=595856&highlight=smart+mobility
Here, a step-by-step approach is given to recover the phone:
"1º [PRJ] Unbricker ROM discovered (wildcard CID and Model ID)
2º Pick any shipped ROM from this thread:
If you have one P3450 -> here
If you have one P3452 -> here
After this, with luck and good work you recover the phone...
3º Then you must do CID_Unlock... You can search how to do it on Wiki or if you want i got one steps how to do it right here and you can see one video with cid_unlock on my signature..." (pasted from the thread)
I did Step 1, and updated it with the unbricker ROM using romupdateutility, and the phone was recovered! It could load, get to Windows Mobile, etc.
Then, unfortunately, when I did Step 2 (mine is a P3450) so I downloaded a ROM from the page indicated, I tried to update the shipped ROM using romupdateutility, but as soon as it got to 2% it failed saying that the vender ID is invalid.
Now, I don't seem to be able to update it with anything - not even the unbrick ROM. What a shame I almost go there.....
xumiking said:
I tried to update the shipped ROM using romupdateutility, but as soon as it got to 2% it failed saying that the vender ID is invalid.
Click to expand...
Click to collapse
You put the shipped ROM in the same folder with RUU??? Why??? You don't need to do that...
You only need to double click on shipped ROM and the installation process begins...
@sbettencourt,
actually yes what I did was to click on the update directly.
I downloaded the file RUU_Elfin_DOPODASIA_WWE_2.20.707.1R_4.1.13.51_03.07.90_RED_Ship_Reduced.exe and executed that directly.
However, now, even this one is stopping at 2%.
Is there any hope, or have I destroyed the phone?
Thanks.
If you can't flash the Shipped ROM, you have now to try the Gold Card... Follow the steps in that Gold Card thread...
Hello everyone,
I finally managed to revive the device, by flashing it with a 'correct' shipped ROM, which did not give any errors on updating. Big thanks for all your support - you are the best!
As this starts to get addictive, and because I am now running a ROM version which dates to 12/11/2007 (2.27.468.1B WWE), what are the suggestions for upgrading the ROM please? My device is an ELF0100.
Thanks again.
Coool Now try to keep him alive
Very true
I managed to flash it with Onyx Ultimate 4.8 (10/07/2009) and it seems to be performing splendidly.
Thanks for all your help.
Good Job