Started a rom upgrade, power failure :x I am NOT a developer so need simple step by step advice on what I may be able to do to recover situaton. Device says Serial 1.06, if I plug into cradle machine beeps to confirm connection and XDA II says USB 1.06.
All I have is the original Rom file and the upgrade (these are both exe's designed to run on PC to upgrade through activesync.
I do have SD card but no raw image.
What are my chances (other than sending in for repair?)
JeremyC said:
Started a rom upgrade, power failure :x I am NOT a developer so need simple step by step advice on what I may be able to do to recover situaton. Device says Serial 1.06, if I plug into cradle machine beeps to confirm connection and XDA II says USB 1.06.
All I have is the original Rom file and the upgrade (these are both exe's designed to run on PC to upgrade through activesync.
I do have SD card but no raw image.
What are my chances (other than sending in for repair?)
Click to expand...
Click to collapse
Don't panic...
Put the device into cradle (with power supply plugged) and run that update again...
HTH
Beecher, thanks for your reply. Sadly I had already tried that!
With the upgrade rom the app ran and found the XDA but reported that the update was the wrong version (I can only guess because it could not find an existing rom to update (I know the update had got as far as erasing the old one)
I did also try and run the original factory release rom prog but that did not seem to do anything at all.
what's your device type (qtek2020, i-mate, MDA II, O2 XDA II) ? ... and what was the original ROM version ?
JeremyC said:
Beecher, thanks for your reply. Sadly I had already tried that!
With the upgrade rom the app ran and found the XDA but reported that the update was the wrong version (I can only guess because it could not find an existing rom to update (I know the update had got as far as erasing the old one)
I did also try and run the original factory release rom prog but that did not seem to do anything at all.
Click to expand...
Click to collapse
Ouch, it looks like I missed basic information you have a XDA1/MDA1 device! I thought you have XDA2/MDA2 device.
In this case, try to find on this forum LumpiStefan ROM kitchen for XDA1/MDA1, cook you own ROM and download only ROM image. Then upload this ROM to your card and get to bootloader. It should somehow update your ROM in device.
HTH
beecher said:
JeremyC said:
Beecher, thanks for your reply. Sadly I had already tried that!
With the upgrade rom the app ran and found the XDA but reported that the update was the wrong version (I can only guess because it could not find an existing rom to update (I know the update had got as far as erasing the old one)
I did also try and run the original factory release rom prog but that did not seem to do anything at all.
Click to expand...
Click to collapse
Ouch, it looks like I missed basic information you have a XDA1/MDA1 device! I thought you have XDA2/MDA2 device.
In this case, try to find on this forum LumpiStefan ROM kitchen for XDA1/MDA1, cook you own ROM and download only ROM image. Then upload this ROM to your card and get to bootloader. It should somehow update your ROM in device.
HTH
Click to expand...
Click to collapse
:?: :?: :?: :?: :?:
Related
OK Guys. Problem Solved : Dead devices due to tmob 1.72 + Downgrade
Problem: New version changes Device ID, as well as ID format.
If you upgrade to tmob 1.72, you cannot downgrade back, as you cannot supply valid NBF files for the new device ID. If you try to play around, you end up with a very dull bootloader screen "Serial V.1.06", and nothing more can be done. SD card images cannot be flashed due to the same reason.
Untill our developers come up with a simple tool, the following 2 solutions can be used to get out of the disaster:
Solution 1:
(tested and 100% working for both dead devices stuck in bootloader and devices working but stuck with the tmob 1.72 version.)
You will need a working device (with old ROM before 1.72), besides your dead one.
1. Prepare your DEAD device in Bootloader mode. Don't connect it yet. (If it is still working but you want to downgrade, press Power+Action+Stylus, if it is already stuck in bootloader, just reset with stylus).
2. Connect your WORKING device, with OLD version via activesync.
3. Start the rom installation of your choice normally, with a version compatible with this WORKING device (Official or Modified NBF files via HymaUpgradeUT). If you don't know what I am talking about, just use your official file downloaded from your WORKING devices' provider).
4. Press NEXT, untill you are presented with the Current version and the one that will be installed. DO NOT click "UPGRADE" yet. (If you got an error so far, you are not using the correct version for your working device.)
5. When you get the dialog with the versions, disconnect the WORKING device from the craddle and connect your DEAD device, in bootloader mode.
6. Click "UPGRADE" and go get yourself a drink.
Et Voila.
Thanks to Victor for inspiring this solution.
Solution 2:
If you don't have another working device, and only have a dead one stuck in BootLoader, you can flash the attached image, through SD card. It will bring back your device to life with the BETA tmob 1.72 CE ROM.
Write the image to the card using "NTRW". Info on SD images and NTRW can be found in this forum.
Unfortunately, i don't have device even with working bootloader And it stuck in TMObile screen
I am sorry I have no solution for screwed Bootloaders, but if your device loads into the tmob screen, there must be something there still working. The only thing I can advise is to try to hard reset and not go into the extended ROM setup files (Soft Reset right after the Hard Reset and welcome procedure), but I guess you don't reach that far ....
What is about for XDA 1?
HI !
I have a Dead XDA. The bootloader is OK. How can I do with it ?
I need some advice for doing it, please !
Best reguard,
Carlo & Victor... You are GREAT!!
Okey.... I will try FIRST!!
please, where is the officiale t mobil rom ? we all have the beta (and thee pb you solve) but not the official one...
thanks
When i posted the T-mobile 172 rom i did not know how much greif it would cause people, sorry to everyone for this
As to the second solution using the SD card is it possible to use this method on a working XDA2.
Basically i have a UK XDA2 and of corse i getthe ID error if i run the upgrade, i dont understand very well how to change the ID part so could i just make the SD card with the rom on it and follow your instructions to recover a dead XDA2
Thanks
John
What should I do when I want to upgrade/downgrade...
I have the T-Mobile 1.72WWE rom installed.
Everything works ok for now, no problems.
But do I need to do when I want to upgrade/downgrade?
I don't have a second device so thats not an option
Please advise.
Thanks
To cairo31male!!
NOP!! Can't HELP!! Maybe the BOOTLOADER got the diffrent version? Mine is 1.03. Can u tell me how to upgrade the bootloader to 1.06?
And you mentioned about OLD version, what do you mean by that?
@hcnsoft:
The 2 solutions described above are for XDA 2's which have been screwed up by installing / uninstalling the latest beta version tmob 1.72. If this is your situation, and you have a working bootloader, both solutions should work for you.
@SEB152030:
The beta we have is 1.72, which caused all these problems. If you have another working device, as described in solution 1, you can revert back to the latest working official ROM (1.66), just follow the steps decribed above and use the official 1.66 upgrade program.
@applecom:
If your XDA 2 is dead, there is no harm in trying. But basically, this SD file will only work on devices that have already been upgraded to 1.72 and then died. If it is dead because of any other reason, I suggest you stick with older stable versions and don't try to mess up with 1.72 for now, until the developers come up with a simple tool to go back and forth between different roms. You can flash SD images that were made from other working devices that have your same model/language. You wouldn't get any errors that way.
@Panja:
Since your device is working, I suggest you wait a couple of days, before trying anything. The developers might come up with a simpler solution. If you absolutely have to downgrade, you can follow the solution 1 described above, but you will need another working device for a few minutes. Use the other working device which has the old ROM installed and start the OLD ROM installation software, then plug in your device with the 1.72 ROM AFTER you get the different versions dialog with the button "UPGRADE".
@Ivan-R: which method are you tying? Solution 1 or 2? FOr the first solution, I guess it should work. For the SD flashing, I beleive you should have Bootloader 1.06. How to get that one, I don't know, but I strongly advise against it, untill all this matter is clear, as each new version of the bootloader implements stricter security, which will make it harder to customize in the future.
OLD version means any version before 1.72
cairo31male said:
@hcnsoft:
@Ivan-R: which method are you tying? Solution 1 or 2? FOr the first solution, I guess it should work. For the SD flashing, I beleive you should have Bootloader 1.06. How to get that one, I don't know, but I strongly advise against it, untill all this matter is clear, as each new version of the bootloader implements stricter security, which will make it harder to customize in the future.
OLD version means any version before 1.72
Click to expand...
Click to collapse
I already try BOTH solution!! Solution 1, i try with ROM 1.03.11, which is thats the basic ROM. Solution 2, the RESULT is Not Allowed UpDate!!
So i guess this is the matter of BOOTLOADER!! Yours is 1.06 and me 1.03. THATS THE PROBLEMO NOW!! Now... How about upgrade the BOOTLOADER??
[email protected]#$!%G FREAK ROM!! :evil:
Mas Ivan,
Sebaiknya anda jangan menggunakan sd image yang di upload karena masih beta untuk menghindari kesalahan pada rom 1.72
thanks cairo for the info, my xda is working with the standard rom, Our only problem is me and the guy that got the rom in the first place would like to use it but we cant
anyway thanks for youe info
John
Solution 1
Solution 1 don't work for me because (I think) 2 version of bootloader 1.03 and 1.06.....
I found a solution : Here
Radio Stack Downgrade
I loaded the 1.72 Beta and would like to keep it, but the Radio Stack is horrible for me. I need to go back to the O2 launch version of the radio stack. I noticed in the O2launch Rom that the contents of the exe file included Radio.nb while the 1.72 exe contained Radio.nbf.
Is it safe for me to try and downgrade only the radio stack and if so should i use the launch version of himalaya upgrade or the 1.72 version of himalaya upgrade to install the launch radio.nb file?
Can anyone give me some advice here? My radio is barely functional. can't find networks where i know there is coverage. Thanks for any advice.
Re: Radio Stack Downgrade
watchdogsdg said:
I loaded the 1.72 Beta and would like to keep it, but the Radio Stack is horrible for me. I need to go back to the O2 launch version of the radio stack. I noticed in the O2launch Rom that the contents of the exe file included Radio.nb while the 1.72 exe contained Radio.nbf.
Is it safe for me to try and downgrade only the radio stack and if so should i use the launch version of himalaya upgrade or the 1.72 version of himalaya upgrade to install the launch radio.nb file?
Can anyone give me some advice here? My radio is barely functional. can't find networks where i know there is coverage. Thanks for any advice.
Click to expand...
Click to collapse
Go go go... Just downgrade it!! 8) Then you will join me in HERE!! Huahahahaha... You are STUCK for the REST OF YOUR LIFE!!
Didn't have any trouble downgrading
I just upgraded to 1.72 last week...hated it...gprs was WAY too slow. Today I downgraded and crossed my fingers back to Xda_II_Upgrade_v16050.exe (filename..not sure where i got it).
IT WORKS!! everything went fine and is fine.
I think my bootloader said it was something like version 1.01 (very hard to read that screen without the backlight) So I'm guessing this downgrade problem may be specific to bootloader versions.
No expert, just letting you know what i did.
This site is amazing. Thanks for everything.
Re: Didn't have any trouble downgrading
mkriemersma said:
So I'm guessing this downgrade problem may be specific to bootloader versions.
No expert, just letting you know what i did.
Click to expand...
Click to collapse
I AGREE WITH YOU!! BOOTLOADER thang'!! I am not EXPERT too, but I REALLY NEED SOME HELP HERE!!
Hi,
Thanks for all help!
I have a dead unit due to 1.72 ROm.
Itried to fool the himalya upgrade program with a soft reset as suggested in another thread, it works It gets trough the device id but stops when erasing rom, any suggestion?
Is there anyone out ther that can disassamble the himalyprogram and
make a small program without error checking?
I also have bootloader 1.06 and tried also "ntrw write ROM.nb1 H:"
It works writing the image but my bootloader don´t loads any rom.
Tried with 2 differnet SD cards, and soft reset, hardreset, and only pushing camera button, without succes, what is the right command?
Any more suggestions?
@nilron:
Press ARROW KEY (any direction on joystick) + POWER Button + SOFT RESET, all together, then wait a little. You should get instructions to press POWER to start flashing.
y saw at www.pocketpartner there is a romupdate 1.72 for the qtec 2020
link:http://www.pocketpc-club.nl/content.php?id=3331.
hein
Thanks!!!
Has anyone tried to upgrade using this ROM? Any problems?
I've posted the last rom french & English one on the following link.
Read what the people says (The roms that I post are original from dangard)
http://forum.xda-developers.com/vie...tart=200&sid=f82d07fe82b956d754c6f2e9845c419f
Kind regards
Problem with the ROM 1.72.03
Hi,
I've install the ROM 1.72.02FRA (ExtROM 1.72.603)
And the MMS composer don't work...
When I launch it, they close immediatly
Can you help me ?
Didier
hein said:
y saw at www.pocketpartner there is a romupdate 1.72 for the qtec 2020
link:http://www.pocketpc-club.nl/content.php?id=3331.
hein
Click to expand...
Click to collapse
I have installed the rom update 1.72.00WWE on a Qtek 2020. It works fine. However I do have a view remarks. I dont see any changes. I thought windows 2003 second edition was installed. The external rom version is 172.125. If I start TomTom3 when the wired GPS is not connected, I get the message "Can not open COM1. Port does not exist". Fortunaly it works well when I connect it. Does anyone know why I do not see any changes in 1.72
Re: Problem with the ROM 1.72.03
Figmentbe said:
Hi,
I've install the ROM 1.72.02FRA (ExtROM 1.72.603)
And the MMS composer don't work...
When I launch it, they close immediatly
Can you help me ?
Didier
Click to expand...
Click to collapse
Hi,
I think that you have make a backup before to install the update & that you have tryed to reinstall your backup after the update.
You have to remain that if you make a backup, you are not able to restore your backup after.
If you do this, you will overwrite some programs (mms,...)
If not give me more details.
Kind regards,
Update from pocetpc-club works fine.
I updated my QTEK with the file as mentioned. It worked fine. Restoring an old backup is not a problem, but doesn't give a full backup, because you restore the old files. So you really have to install everything new.
As far as I can see, there are no problems with the update.
Regards, Luc
Does this ROM update the bootloader?
Hi,
Has any of you who have upgraded to this ROM checked if it also does upgrade your bootloader to 1.06?
Regards,
Mark
Hello,
Mine has upgraded the bootloader to v1.10.
Cheers
BootLoader
Raphael said:
Hello,
Mine has upgraded the bootloader to v1.10.
Cheers
Click to expand...
Click to collapse
Upped and running on i-mate + qtek 1.72 ROMs but still 1.01 here.
Sorry, my mistake , my bootloade is V1.14 with the Dangaard 1.72 ROM.
cheers
@Raphael
Are you sure you'are looking at the right place? Haven't heard yet of booloader newer than 1.06 yet. But that doesn't ofcourse mean that it doesn't exist.
Mark
hmm, it seems that someone is mixing up radio stack and bootloader. have never heard of bootloader newer than 1.06 but radio stack 1.10 1.14 and even 1.17 (in some german replacement devices with 1.72.01GER) is out so far.
greetings from black forrest
peter
Sorry, You're right, had a mix up:V.1.02
No w I start to be ashamed of this mix up.
Cheers
:lol:
Just did a soft reset on mine with ROM 1.72 and I can insure you that
Radio is 1.14
I don't know how to find the "bootloader version" ?
so long
there are two ways of finding bootloader version:
1. you hold power-, 4-way rocker switch and soft-reset and your device goes into bootloader mode (and by the way all of your data is lost, so backup your device before doing that)
2. browse around xda-developers forum and find a tool that is called safebootloader.exe or something like that. this file must be copied to your device. start it and it writes a file where informations about the bootloader is in. open that file with a hex-editor e.g. and you can see the version.
regards
peter
My friend just got the hermes running the crossbow os, would someone tell me how to dump the rom out? Need urgen reply cause he will leave hong kong tomorrow.
First try Buzz's rom dumper. It's available here
There are reports that it won't work which may be related to the Hermes microSD slot. I'd try the miniSD version of Buzz's pgm first.
There are various ways to dump the ROM from a live device, I don't know which one will be the most reliable or will be more helpful to reconstruct the ROM after the dump, so if possible dump the rom in all methods explained here:
1) itsutils pdocread, as explained in the WIKI:
http://wiki.xda-developers.com/index.php?pagename=Hermes_HowtoDumpRom
This is IMHO the most reliable method, first use 'pdocread -l' to list all partitions, then dump ALL them in "raw" files. Feel free to ask if you need help or are unsure in any of the steps.
2) As Sleuth255 suggested, you can also try grab_it! tool from buzz, but I don't know if it will work or not.
3) There is also mamaich's TestWM5.exe, which dumps files and modules to SD card, but I think the dump will not be useful for creating a valid imgfs after, anyway try this method too.
4) It will be also useful if you dump the bootloader on this device: Run gnuharet.exe on the device, then telnet to port 9999 and issue this command: 'pwf splfile 0x30000000 0x40000' in gnuharet.exe
This will dump the running SPL in a file called "splfile" in the folder where you run gnuharet from. It will probably be corrupted by wince usb host buffers, but anyway will be useful too.
Good luck and feel free to ask if you have problems
Suspense is killing me... did we get a dump?
Also please, put the Hermes in bootloader mode (side ok + power button + softreset with stylus) and tell us exactly the IPL and SPL version you see in the tri-color screen. Probably we can investigate how to dump rom parts from bootloader using 'rbmc' command in mtty.
tsuishui said:
My friend just got the hermes running the crossbow os, would someone tell me how to dump the rom out? Need urgen reply cause he will leave hong kong tomorrow.
Click to expand...
Click to collapse
Any progress? Im all tingles here, my wife thinks im crazy...lol cannot wait to get my hands on this one...(and i dont mean my wife)
This should be interesting if he actually gets it
It is as follows
HERM100
IPL-1.00
HERM100 MFG
SPL-1.02
Ok, i will wait a while and I will provide you the commands to dump the ROM from bootloader. Meanwhile download HHD Usb Monitor trial version, and install it.
pof said:
Ok, i will wait a while and I will provide you the commands to dump the ROM from bootloader. Meanwhile download HHD Usb Monitor trial version, and install it.
Click to expand...
Click to collapse
Any idea what the chances are to create a working rom out of this?
I am out of computer right now so i will try to dump the rom later today and my friend tells me that this device is come from microsoft. Also it is the rom from t-mobile.
great news today!
Now I really can't wait for this
http://msmobiles.com/news.php/5846.html
darkjedi said:
Now I really can't wait for this
http://msmobiles.com/news.php/5846.html
Click to expand...
Click to collapse
nice tease...guess i put it up for discussion in our Hermes meeting tomorrow..
Well lookey here! M$ also released a version that runs on the HTC Wizard. The Wizard was their preferred device at MEDC 2006.
I'm really wondering why they called it WM6.0 instead of SE or 5.5...
POF and other more intelligent people than me - if we do get this ROM I am more than happy to act as a guinea pig for this!! I have 2 days off work and a brand new Hermes to mess around with!
LOL I'm sure everyone will want to be a guinea pigs for this
darkjedi said:
I'm really wondering why they called it WM6.0 instead of SE or 5.5...
Click to expand...
Click to collapse
possibly marketing...
Getting the ROM dump is only the first (most important) part. Next the talented folks here at xda developers will need to convert it to a flashable image. The Hermes architecture presents unique challenges here. I'm sure having this dump on the FTP site will add even more incentive to this effort which will also result in our ability to cook our own ROMs....
Hey guys/girls
i was messing with my mogul and now its stuck on the tri color screen.
Software
TITA100
SPL-1.20.Olipro
please if any one can help i would appreicate it.
Plug into usb and install your carriers current rom
wont let me. i get a connection error. it stops on 11% when trying to update the rom.
flash by microsd method. This will eliminate all usb problems
drewcam888 said:
flash by microsd method. This will eliminate all usb problems
Click to expand...
Click to collapse
is their any way to send me a link to the right update? because i tried the one from HTC via microcard and it wont load anything.
That would be hard in that I know nothing about your carrier. But I only have Verizon stuff. Maybe add your info to every post.
drewcam888 said:
That would be hard in that I know nothing about your carrier. But I only have Verizon stuff. Maybe add your info to every post.
Click to expand...
Click to collapse
i have sprint.
also i had 6.1 loaded inside
but now its stuck on the loader screen so prob dont have any software.
tank319 said:
wont let me. i get a connection error. it stops on 11% when trying to update the rom.
Click to expand...
Click to collapse
are you using VMWARE Fusion or Parallels Desktop?
If so, update to the lastest version and/or change the settings to "GUEST ONLY" for USB......
I has that issue a while back on a treo, several during the update process it "disconnects" the USB momentarily....
If you had it set to "ask me" then, it would attempt to "ask you.", causing the updater no not see it. (No fusion or parallels, because there is no valid firmware on the device.)
If that was your issue, let me know, please.
Just download the lastest rom and extract the .nbh from the .exe with winrar. Rename it properly and flash away.
Also, you may way to look into either olipro 2.40 or nueSPL 2.47 for your bootloader. It could be that you are trying to load an incompatible ROM. Check the wikis and stickies for a compatibility list of bootloader/radio/ROM.
i got it to turn on and stay on but i cant update it to 6.1 because of the SPL 1.20 bootloader i think how can i update it. i have dcd_2[1].0.0_beta_sprint.exe but it will not load on my phone even if i change the name. any idea's? also i tried to RUU_TITAN_SPRINT_WWE_3.56.651.0_RS_TITAN_3.42.02_SPCS2.04_PPST_0718_Ship.exe flash that on and still gives an error.
BTW thanks alot for helping me out
Look at Step II - 1 in the wiki. http://wiki.xda-developers.com/index.php?pagename=TitanRecentHome
You are also using a pretty old ROM made by DCD. He made a bunch more that worked very well before he stopped posting.
Hi!
I've a big problem with my german O2 XDA Star. The touchscreen doesn't work anymore. I tried a hardreset, but now I can't get through the configuration at the beginning, because the screen ist still not working. Now I think the last chance is to flash a new ROM, but it's not possible to flash any ROM because I can't do the Hard-Spl.
So I need a ROM, which doesn't need a unlock before installing it.
I hope someone can help!
Thanks!
Get the package here
Read the ReadMe.txt on how to flash the whole ROM before flashing! Good luck and let me know your succeeding!
Thank you for the link, but this Rom needs a Hardspl, too.
I can't do anything on the phone.
Any other idea how to solve the problem with the touchscreen?
Thanks!
Yes, you need at first a HardSPL on your phone to flash the OS and Radio only! After that, start SoftSPL on your phone and flash the original SPL!
So, what's your problem with that?
How can I do the HardSpl when the Touchscreen doesn't work? For the HardSpl I've to copy a file to the phone and run it, or am I wrong?
Awww, that's a problem, indeed!
Try the following:
- remove the Storage Card
- connect your XDA to your PC
- install Pocket Controller Pro (or similar tool) both on PC and XDA
- put SSPL into main storage
- start it by using the Controller program
- you might be able to flash USPL for flashing all things you need
If you didn't succeeded with it, I can have a look at it! Just contact me by PM for further infos!
where to get the original o2 spl for the star? im still searchin it..
edit: ah its in your package linked in your first post.... thank you...