Whenever I go to flash my phone I get all the way up to the point where the .NBH file is being loaded to my phone and maybe like 10% in I get an error saying that "The file was corrupted please check your update utility"....can you direct me to a link thats a good update utility? Or if you know the problem then by all means feel free to make me loo dumb lol!!
ALSO I am using ITsPapaWingRC5_3 as my .nbh file and my Flash program is Flash Center (Herald-uspl.exe)
Are you hardspl'd?
http://forum.xda-developers.com/showthread.php?t=358615
Never mind I got it to work..does anyone have the original rom that comes with the tmobile wing? Just incase I ever want to go back to the original factory settings?
Just look for Tmobile_Offical_RUU. It's all over the place in here. Or go to the tmobile web site and click upgrade your device and it will let you download it there.
Got it...I love my XDA Family!!
Related
Hello,
I was today handed a fried XDA 2.
My boss had attemted to flash it and it failed for whatever reason.
Now i will say from the outset that i have only ever flashed my XDA1 with a XDA-Developers ROM and it was a breeze.
The ROM file HE flashed with was called.
Xda_II_Upgrade_v16050.exe
Now when you switch the thing on.. all you get is a a small amount of txt saying
'Serial'
'v1.06'
and nothing else..
What have i done? Well i have sifted through the articles on here.. and found this rom
XDA-developers-SER-v12.exe
I have installed this on an SD card using xdatools.. WHOLESALE.. i.e. no moding of the files...
I have looked at 'http://wiki.xda-developers.com/wiki/HimalayaRomFlashing'
but as i can boot into the device.. i cant get the info it requires.
I am open to any and all help. And I'll even buy you a pint!
I am really at a lose.
Thanks in advance Guys and Girls.
It may not be as bad as you think.
It is in bootloader mode - currently in Serial mode and if you put it in a cradle connected to a PC (with ActiveSync installed) the bootloader should change to USB v 1.06. From this point you should be able to load a normal ROM from the manufacturer.
I have an i-mate, so am not sure what the current ROM version for the XDA II is, but I'm sure others will chime in with this information.
I upgraded to this version, not knowing I already had this loaded. You need to check the extROM version before upgrading as this appears to be way the official upgrades seem to change.
I had no problems and it was done through the Active Sync process
The file can be found here if you haven't already got it... http://www.my-xda.com/downloads.html
Try it again. It does take about 90 mins.
Regards
Nope... Nadda... Zip... Zilch.
Roit...
When i dock the pesky thing in the USB craddle.. it does display USB and v.1.06.
Activesync shows NO sign of knowing the XDA is there.
The ROM found at http://www.my-xda.com/downloads.html as suggested by flintanis fails with a ERROR 100: MODEL ID ERROR.
BRosenow what do you mean by 'load a normal ROM form the manufacturer' is that not what i have just tried?
Once again a pint for all contributors.. and my first born to the dude with the solution.
Cheers.
ActriveSync won't activate because it's in Boot loader mode but you can download the latest ROM Update from the manufacturer or cellphone service provider and load that to flash the ROM and complete the process.
If it's a UK XDAII, get the update at www.my-xda.com .
It appears the previous user tried to flash it with a ROM from another manufacturer (Q-Tek/MDA II/i-mate). You are now receiving a Model/Country ID error. I have not experienced this myself, but I have read posts in this forum on how to fix it. Do a search and I bet you will find it.
- OR - any user who has experienced this and successfully flashed his ROM could chime in here and give jonathh some advice . . .
After much ado about nothing..
i have returned to again fix this XDA2 (the joys of pesky FT employment; make your minds up guys.. you want this XDA2 fixed or not?)
Right i *think* with quite a high level of certainty that the XDA2 currently in my grubby mitts was purchased in Malaysia/Sinapore.
Now.. am i correct in that flashing it Xda_II_Upgrade_v16050.exe from http://www.my-xda.com/downloads.html
Would cuase the problem i have now.. or at the very least wont go on on the XDA2 now because it is a UK ROM and a Malaysia XDA2?
I have flicked thru the pages on here.. and i cant seen to see how to solve this!!
PPllleeasseee help
*sobs, and gently rocks back and fourth*
I think there is a bit of confusion going on in this post!
The first ROM you tried (XDA-developers-SER-v12.exe) is for XDA1 - NOT XDA2.
The best place to get the latest UK XDA2 ROM is http://www.sourceo2.com/O2_Developers/Devices/O2_Xda_II/XdaIIRom.htm
and i *believe* that the place to download the Malaysia ROM is
http://www.myxda.com/XdaII/serviceandsupport/template/XdaIISoftwareUpgrade.vm (note the absence of the '-' between my and xda...this is the Asian O2 website)
See if the ROM from either of those sites will install
Hope that helps!
How about scrambled?
Ok, thanks 'pope'
*none* of the roms suggest work..
Xda_II_Upgrade_v16050.exe reports unknown country code..
and the recently suggested
Xda_II_LaunchROM_v10311.exe just sticks on the 'checking for information' left it for over an hour! BUT doesn't report unknown country code like the other one.
I cant get the XDA2 rom from the Asia site, as after i registerd my XDA2 it reports i dont need the damn update... anyone got it already?
I have extracted the core files from both these exe's and tried to copy them to an SD card(the NBF fille) using XDAtools.. and xdatools report the files are invalid.
I am lost and clueless!
HHHEEELLLPPPPP
Well that didn't work...
I got my grimmy grits on another XDA2 and using XDAtools sucked the ROM off of that.. and then.. again using XDAtools squirtted it out onto an SD card..
But i am unsure what i have to do then? is this latest approach possible??
Comments welcome![/code]
Love to help… but
My UK O2 XDA II has exactly the same problem. I died whilst flashing the UK O2 1.60 ROM, and now I can't do anything with it. Identical symptoms. Identical complete lack of success (eight hours and counting).
How can I find out the country ID of my device when my XDAII is dead?
mark8barnes said:
Love to help… but
My UK O2 XDA II has exactly the same problem. I died whilst flashing the UK O2 1.60 ROM, and now I can't do anything with it. Identical symptoms. Identical complete lack of success (eight hours and counting).
How can I find out the country ID of my device when my XDAII is dead?
Click to expand...
Click to collapse
O2 will fix this for you if it happened as a result of flashing with their rom.
By they way, in case anyone was concerned when I said " I died whilst flashing the UK ROM", I did of course mean "it died..." ;-)
But I have solved my own problem! How come you can spend hours trying to find a solution, and as soon as you ask for help, you sort it out straight away??!!
I hope this works for you if you're still struggling.
1) Download the latest i_Mate ROM from http://www.clubimate.com/Support/RUU172126WWE_imate.exe
2) Download the XDAII Rom Editor from http://wiki.xda-developers.com/uploads/ER2003Edit_1_2_20.msi
3) Extract the files from the IMate ROM, and use the ROM Editor to change the Operator to 02. Get the instructions here and the password here
4) Flash the ROM as normal. It worked for me You could experiment with using the O2 extended ROM files rather than the T-Mobile ones, but I was just glad to get the thing working. Perhaps I'll feel braver later.
I did feel braver, and copied the O2 Cabs into the IMate Extended ROM file. Then I deleted the IMate cabs I didn't want, modified config.txt and prayed! Everything seems to have gone fine, and I'm now re-installing all the software. Already there seems to be a significant speed increase over 1.60.
I'd recommend taking this step before you flash the ROM, rather than doing it twice like I did.
mark8barnes is the man!
I didn't do the mods.. just as per your original post.. and it worked!! Yay
Thanks mate you da man!
Now i do have a query tho.. if i did suck the rom off using XDATools.. how would i get it bck on again?
Cheers all you guys..
Fried XDA
Hello Mark
Me too, I flashed my ROM with the UK version with the same result.
The link to the iMate ROM no longer exists, can you help me please. I'm a real novice at this.
Thank you
Ben (Aust)
mark8barnes said:
By they way, in case anyone was concerned when I said " I died whilst flashing the UK ROM", I did of course mean "it died..." ;-)
But I have solved my own problem! How come you can spend hours trying to find a solution, and as soon as you ask for help, you sort it out straight away??!!
I hope this works for you if you're still struggling.
1) Download the latest i_Mate ROM from http://www.clubimate.com/Support/RUU172126WWE_imate.exe
2) Download the XDAII Rom Editor from http://wiki.xda-developers.com/uploads/ER2003Edit_1_2_20.msi
3) Extract the files from the IMate ROM, and use the ROM Editor to change the Operator to 02. Get the instructions here and the password here
4) Flash the ROM as normal. It worked for me You could experiment with using the O2 extended ROM files rather than the T-Mobile ones, but I was just glad to get the thing working. Perhaps I'll feel braver later.
Click to expand...
Click to collapse
While trying to update my MDA Vario with the new AKU 2 ROM of T-Mobile the RUU puts the MDA in bootloader. Then Windows notifies me of a new unknown USB device and the update utility gives me an communication error with error code [260] - upgrade failed. :shock:
1) How to solve this problem as this would make me or
2) Is it possible for someone to make a complete backup on a mini SD card of his HTC Wizard? From what I have read on Internet this can be written to a file. When posted on the XDA ftp I can write this file back to a mini SD card and restore a original ROM (for this I need a short tutorial).
option 2 assumes that the problem is related to the ROM. I super CID and SIM unlocked using the well known tools. Maybe this has gone wrong at some point :?: ?.
I'm having the same problem moving up to a custom 2.26. Did you ever find a solution.
Thanks,
Jeff
dont qoute me on this.. but i believe its an issue with the update utility... hopefully someone else can confirm or deny this..
but you can try this one:
i dont know how much either of you know so i will try some directions with this...
take my rar file, extract them to a folder, lets use c:\rom for an example
if you rom you have is in an *.exe format then use winrar to extract the rom to a folder then take the nk.nbf file and copy it to c:\rom and then run the update utility
if your rom is already in a rar or zip file then just extract the nk.nbf file to the c:\rom folder and then run the update utility
hope that helps
shogunmark said:
dont qoute me on this.. but i believe its an issue with the update utility... hopefully someone else can confirm or deny this..
but you can try this one:
Click to expand...
Click to collapse
I really appreciate your help, but before I risk bricking my phone, could you tell you tell me how this differs from the ROMUpdateUtility_Wizard_NoID.exe and RUU*.* that are part of the custom ROM update package I already have?
Thanks,
Jeff
datawrhsdoc said:
shogunmark said:
dont qoute me on this.. but i believe its an issue with the update utility... hopefully someone else can confirm or deny this..
but you can try this one:
Click to expand...
Click to collapse
I really appreciate your help, but before I risk bricking my phone, could you tell you tell me how this differs from the ROMUpdateUtility_Wizard_NoID.exe and RUU*.* that are part of the custom ROM update package I already have?
Thanks,
Jeff
Click to expand...
Click to collapse
the custom rom that you have, does it have the NoID update utility already?
ANSWER
I spent a few hours fiddling with this, and it turns out that my problem was that I have a miniSD installed. Make sure you pop your miniSD out of the slot before you begin the update, and it should work.
Re: ANSWER
doomcomplex said:
I spent a few hours fiddling with this, and it turns out that my problem was that I have a miniSD installed. Make sure you pop your miniSD out of the slot before you begin the update, and it should work.
Click to expand...
Click to collapse
WTF that is WEIRD
i have flashed many roms and never had an issue with the sd card being in... but will definitely file that in the back of my brain in case i ever run into the same issue
shogunmark said:
the custom rom that you have, does it have the NoID update utility already?
Click to expand...
Click to collapse
Yes, it does. Oh, I also tried this without the MiniSD in the device (a known but really strange problem). Still getting the error.
Error 260 Finally Gone!!!
Well, just for the heck of it, I tried xelencin's 2.26 ROM update from another PC...and it succeeded.
Clearly, it is a new issue related to my laptop but it is probably going to quite a bit of trouble to track down.
Thanks everyone,
Jeff
Re: Answer
doomcomplex said:
I spent a few hours fiddling with this, and it turns out that my problem was that I have a miniSD installed. Make sure you pop your miniSD out of the slot before you begin the update, and it should work.
Click to expand...
Click to collapse
WTF!!! I had the exact same problem. Popped out the Mini-SD Card and voila! The Bootloader started!
Thanks man!!
Ty man ... MS card out and it is working .... yea
i cant get this to work PDA PHONE ROM UPDATER, send a black screen to s200 and then gives error 260
I tried to upgrade mine xda with ivan's rom but something went wrong so now i cand upgrade it at all.
Allways i get some country or model id error.
I tried to restore image(which i got from another XDA) but says when i enter bootloader & when i should be asked for rom dump it says:
SD Download
Sections=3
Not allow update
I checked ExtROM version but it says 0.0
Please if u have any solution i would be gratefull
stop complaining and start searching for solution.
hint: use MaUpgradeUt_noID.exe to bypass the country code error.
helmi_c has packed this kinda utility in this latest rom (in the folder PH20B1).
good luck.
also read the upgrading wiki. what does it say your meant to do before you upgrade? get ur device data. then what does it say to do with that data?
input it into the upgrade file. helmi's newest rom pretty much does this for u if u follow the wiki and the readme that comes with it.
always follow guides TO THE LETTER, or you're gonna screw up your device.
Hi All,
I want to upgrade my phone to 2.26. The old details of my phone are as follows:
Ipl 1.05
Spl 1.05
Gsm 01.09.10
Os 1.5.4.2
Is there any specific way to do this?
Cheers,
Dave.
If u want to use TMO's official rom, just go to their website and download their updated rom,2.26. If u want a custom rom, do a search and there are plenty of helpful post to guide u thru it. PM me if u need to. good luck
custom help
i have downloaded 2 custom roms, one for the radio 2.47.11 and one for the 3.2 both are RAR files. how do i load those onto my phone? double clicking doesn't work or do i go through boot loader somehow? do i load them onto my MDA drive and double click? tried everything to no avail. help
berzansky said:
i have downloaded 2 custom roms, one for the radio 2.47.11 and one for the 3.2 both are RAR files. how do i load those onto my phone? double clicking doesn't work or do i go through boot loader somehow? do i load them onto my MDA drive and double click? tried everything to no avail. help
Click to expand...
Click to collapse
Your gonna have to extract them using some kind of rar extractor .
I downloaded WinRar and used the trial version. Probably gonna need to purchase it myself, as it seems a lot of downloads are using this format. I thought I read somewhere in here that there is a free rar extractor out there. Anyone know about this?
DON'T DO ANYTHING until you've read enough of this site to know what you're doing with a rom. If you don't know how to extract it from a rar file, I'd bet a paycheck you're going to trash your expensive toy. Spend a couple of weeks reading about what to do and how to recover if flashing the phone goes bad. There are lots and lots of answers all over this site and it's up to YOU to know what you're doing. No one is going to hold your hand, push the buttons, take the blame or give you a new phone when your laptop crashes at 98% done and your phone doesn't even turn on afterwards.
markgamber said:
DON'T DO ANYTHING until you've read enough of this site to know what you're doing with a rom. If you don't know how to extract it from a rar file, I'd bet a paycheck you're going to trash your expensive toy. Spend a couple of weeks reading about what to do and how to recover if flashing the phone goes bad. There are lots and lots of answers all over this site and it's up to YOU to know what you're doing. No one is going to hold your hand, push the buttons, take the blame or give you a new phone when your laptop crashes at 98% done and your phone doesn't even turn on afterwards.
Click to expand...
Click to collapse
I agree! read, read, read, first before doing anything to your phone. I'm sure you don't want an expensive paperweight.
thanks for the info on winrar. i had been keeping up with these posts since the first day mad monkey boy sold the first imate kjam's way back when. been playing with my new daughter and have been out of the loop. winrar wasn't that hard to use. just didn't want to read through 10 hrs of posts to get the simple instructions of using winrar. thanks, marc
Dude I agree with everyone else I dont think you should do anything if you dont even know how to extract files from a rar. This stuff can really mess your phone up. Learn some PC stuff before you do anything.
My phone has been going haywire for the last month. Its extremely pissing me off. It'll restart all the time by itself and now it thinks the enter button is stuck so trying to do ANYTHING wont work because enter keeps opening whatevers selected..
so I got my replacement in the mail from tmobile today, and I wanted to flash the tmobile ruu back on my old wing before I sent it back in. I downloaded the new version off tmobiles site and it had an error during install. Doesnt seem like the ruu is going to load over the open touch I've got on there now.
Suggestions?
TylerC161 said:
My phone has been going haywire for the last month. Its extremely pissing me off. It'll restart all the time by itself and now it thinks the enter button is stuck so trying to do ANYTHING wont work because enter keeps opening whatevers selected..
so I got my replacement in the mail from tmobile today, and I wanted to flash the tmobile ruu back on my old wing before I sent it back in. I downloaded the new version off tmobiles site and it had an error during install. Doesnt seem like the ruu is going to load over the open touch I've got on there now.
Suggestions?
Click to expand...
Click to collapse
Did you try this thread? http://forum.xda-developers.com/showthread.php?t=364543
waynehathaway said:
Did you try this thread? http://forum.xda-developers.com/showthread.php?t=364543
Click to expand...
Click to collapse
I missed that thread. Thanks!
use flashcenter (uspl) with the tmobile rom)
my understanding...was that...to get rid of hardspl, you needed to use the uspl or flashcenter to flash the original tmobile rom...and it'll write over the hardspl.
Well I went through it, and everything was going as the installer said it should, but when the update utility started to run to flash back the old ruu it gave me a connection error and quit.. I suppose I'll give it another shot.
I actually extracted the files from the newest Tmobile ROM and just used the flashcenter to put it on my HARDSPL'd Wing. It seemed pretty quick to.
But you can try this here then flash the newest ROM
http://forum.xda-developers.com/showpost.php?p=2008521&postcount=308
damnitpud said:
I actually extracted the files from the newest Tmobile ROM and just used the flashcenter to put it on my HARDSPL'd Wing. It seemed pretty quick to.
But you can try this here then flash the newest ROM
http://forum.xda-developers.com/showpost.php?p=2008521&postcount=308
Click to expand...
Click to collapse
so you just updated your ipl & spl but then flashed a custom rom?
or did you flash the new tmobile rom then flash a custom?
I was getting the connection error as well, I restarted holding down the camera button to go to the bootloader, then run the t-mobile rom.
Hey sorry for the long time without replying. But i did a search for my posts and noticed i never answered back here.
What i was talking about is, if you use WinRaR you can extract the Tmobile exe file which gives you the flash center files, SPL.nbh and RUU_Signed.nbh. With the phone hardSPL'd you can just run the ROMUpdateUtility.exe and it will install the OEM WM6 from TMobile.
Nice and easy eh?
To extract an exe file with WinRaR, you have to right click the file and choose extract files.