T-Mo Wing RUU for USA!! - Wing, P4350 General

Here it is guys.
http://www.mediafire.com/?2nq9iu0a2nt
To enter the wing into boot loader, turn the phone off. Turn the phone back on while holding the camera button AND the voice button.

xavier6303 said:
Here it is guys.
http://www.mediafire.com/?21rtyxwyuyj
To enter the wing into boot loader, turn the phone off. Turn the phone back on while holding the camera button AND the voice button.
Click to expand...
Click to collapse
thanks mate... but unable to extract the file...

NNagendran said:
thanks mate... but unable to extract the file...
Click to expand...
Click to collapse
Try redownloading. It extracted fine for me.
xavier6303 said:
Here it is guys.
http://www.mediafire.com/?21rtyxwyuyj
To enter the wing into boot loader, turn the phone off. Turn the phone back on while holding the camera button AND the voice button.
Click to expand...
Click to collapse
What's the OS version on this? Anybody know?

tried redownloading a couple of times and still got an "unexpected end of archive" error when using WinRAR.
Can you repost the file somewhere else, please?

worked on my phone should work on yours

lucabraz23 said:
worked on my phone should work on yours
Click to expand...
Click to collapse
Do you have a wing, or an unbranded 4350? Also, can you do me a favor and check settings>about and give the version number on the OS?

delete delete

doesnt work for me i have an unbranded herald
i get error224 invalid model number

imawinnerbaby said:
doesnt work for me i have an unbranded herald
i get error224 invalid model number
Click to expand...
Click to collapse
The main benefit of this ATM is now wing users have the ability to flash from the bootloader.

will this rom get rid of the crazy memory leak?

Tried updating the ROM twice then checked under the device info:
ROM version still says: "4.10.531.2 WWE"
ROM date: 03/15/07
Radio Version: 02.83.90
Protocol version: 4.1.13.37
The ROM update utility says that the image is Version: "4.10.531.3" anyone know why this one was not loaded?

Guys, I know there are alot of questions pertaining to this RUU but it is the T-Mobile OEM Rom that comes on every T-Mobile Wing. This just helps if you brick it; you will be able to recover from a brick in most cases. I had a problem with my usb connection on my device after I reflashed it. For some reason I was getting "usb not found" errors. I cleared storage and it works fine now.

(post deleted)
(Apparently Mediafire doesn't like Firefox for some reason, but got the file downloading in IE.)

i'll try it
I've been after this file since about mid July and noone seems to have it. As a matter of fact, it seems like people have been waiting for this to release to show up. I've looked all over for this file. I'll give it a try tonight on my bricked Wing. I just don't know how you have this file and everyone else is scrambling for it.

transportguy said:
Tried updating the ROM twice then checked under the device info:
ROM version still says: "4.10.531.2 WWE"
ROM date: 03/15/07
Radio Version: 02.83.90
Protocol version: 4.1.13.37
The ROM update utility says that the image is Version: "4.10.531.3" anyone know why this one was not loaded?
Click to expand...
Click to collapse
transportguy,
My stock T-Mobile Wing reports it's ROM version as 4.10.531.3 WWE.

Okay, so apparently the Wing is supposed to reboot itself at around 1% and 30% in the update process. I thought the reboot was the RUU failing, so I disconnected my Wing and got a connection error message. Whoops. In other words, keep your Wing plugged in during the update process even if it reboots.
Just figured I'd post that in case anyone else runs into the same "problem" I did.

I have 2 Wings.
My bricked wing is 4.10.531.3 WWE
My unmodified, pristine Wing is 4.10.531.2 WWE
I've been waiting for this so that I can unbrick my 1st Wing and I can use that one as a testbed for ROMS, etc. I'm not sure if it'll work on my newer (x.2) Wing, but since there's no reason to try, I doubt I'm going to
Thank you for making this available to us!
EDIT:
Ok, so I decided to try, and it looks like the update is going to happen. This allowed me to upgrade 4.10.531.2 WWE to 4.10.531.3 WWE.

Is there a Dutch wing official ROM available?

applecarriage said:
transportguy,
My stock T-Mobile Wing reports it's ROM version as 4.10.531.3 WWE.
Click to expand...
Click to collapse
Thanks Applecarriage, after the second time I flashed the ROM it showed 3. I guess the first flash didnt take.

Has anyone noticed any difference from 4.10.531.2 WWE to 4.10.531.3 WWE ? I am wondering if its worth upgrading too.

Related

nothing work afrer update

i want update radio update but its locked at %10 then i restarted
and i want to enter bootloader but nothing come to screen. no power no bootloader!
how can i solve this problem...
albetratz said:
i want update radio update but its locked at %10 then i restarted
and i want to enter bootloader but nothing come to screen. no power no bootloader!
how can i solve this problem...
Click to expand...
Click to collapse
You should have read the instructions before trying the upgrade. ROM upgrade goes first, then the radio stack. I don't know if there's something you can do yourself to fix your device, or if you need to have it reflashed by your supplier. Anyone else?
bamse said:
albetratz said:
i want update radio update but its locked at %10 then i restarted
and i want to enter bootloader but nothing come to screen. no power no bootloader!
how can i solve this problem...
Click to expand...
Click to collapse
You should have read the instructions before trying the upgrade. ROM upgrade goes first, then the radio stack. I don't know if there's something you can do yourself to fix your device, or if you need to have it reflashed by your supplier. Anyone else?
Click to expand...
Click to collapse
Hi,
Seems like you are another of the many victims who got problems
after trying to upgrading new ROM & Raidio stack. Hope you still
got that warrant and get it replaced with a new one. Otherwise
you might have to try what some crazy guys do here trying to fix
it by doing all sort of bootloader etc.. Hope those who are trying
to get the upgrade ROM and Radio stack be very careful and make
sure your device are from the same supplier or distributor where
you got the new upgrade. Otherwise it will be screwed. Dont learn
your lesson the hard way.
same problem here.
i've got the O2 NL XDA
downloaded the 3.15 and radio updates from O2 NL website
installed updates as per instructions
1st update went without a hitch
2nd update totally screwed my xda.
now it takes a long time to start up, and when it does it just displays a white screen with a blue taskbar.
tried the bootloader way of flashing the rom, but still no luck
luckily I can send it back in to O2 to have it fixed.
I may try to do it by backup up another XDA, and reflashing mine.
Same prob with me..
I've got exactly the same problem. I downloaded the Rom update 3.15 and the new radio update. First I installed teh Rom update and after a hard reset I "installed" the radio update.
While updating the XDA hang and I waited for about ten minutes to see if the XDA was really hanging. I gave the XDA a hard reset but then the XDA didn't work anymore (white screen and blue bar on top).
I can still access the bootloader. I installed a Rom from a XDA which still works. Still no difference. When I tried to write the Radio rom to a sd-card I got that message that I have to connect one or another RS cable.
The XDA still doesn't work anymore. I have contacted O2 but they told me that they couldn't help me because they can't find my IMEI number in their system. I contacted the company where we ordered all the XDA's but I still don't have an answer.
Thank you O2 for being so nice with not helping me out with my one week old XDA without any scratch. I hope my XDA could be replaced as soon as possible since the XDA will not sold anymore when O2 changes to Telfort !
If you can make the ROM update work, you should be able to install the corresponding radio as well.
Try this:
1. Make sure you have the latest version of ActiveSync (=3.6)
2. Make sure the battery is fully loaded.
3. Extract the ROM update and Radio update to different folders.
3. Connect the cradle to AC-adapter and computer.
4. Put the device in the cradle and make sure it connects to ActiveSync.
5. Run the ROM installation application. Should take 5-6 minutes.
6. Run the radio installation. IMPORTANT: When you are prompted to remove power supply, pull the power plug from the cradle. If you do not disconnect power, the update will fail. I think this update took a little more time than the ROM update, and the device may seem "dead" for a while.
Good luck!
Hy Guys.
Are there any news about the problem flashing the XDA?
Tried last night to update my XDA to the last Qtek-Versions (ROM 3.16.52.....)
ROM Update works fine, but after the RSU Update the phone didn't work any more.
Have the same white screen with the blue taskbar and the little keyboardicaon down the right side.
Entering Bootloader mode there comes the Error Message "GSM Error"
Nice screen is the qtek "Booting Screen".
It shows
G <empty>
R <empty>
3.16.52
Hope there are any other hints to resolv this problem.
Have anyone got some experiences with sending it back to O2 with an "unoffical" Softwareversion?
Or is there any posibility to change the ROM Version to an old (original) O2-RomVErsion?
Thanks for any help....
Regards
Stefan
Hi Stefan,
I would suggest to try upgrade you device with any XDA ROM version by bootloader's CE to SD backup/restore and after try again to upgrade RUU by PC.
I know that upgrading/degrading by bootloader is the more safety way to do it.
Regards,
Riccardo
Riccardo said:
Hi Stefan,
I would suggest to try upgrade you device with any XDA ROM version by bootloader's CE to SD backup/restore and after try again to upgrade RUU by PC.
I know that upgrading/degrading by bootloader is the more safety way to do it.
Click to expand...
Click to collapse
SD-Card Writer just orderd
But I don´t know if it will work. Since the Bootloader says GSM Error, I think there will be no other posibility to restore it.
Let´s wait for some days, hope and we will see.....
Stefan

Help with charmer

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?

Help with my Bricked 8125

I think my 8125 is bricked. I've never had a problem flashing roms until yesterday I tried Farias Kitchen ROM. I flashing went through ok like normal, but when it restarted, it gets a little bit after the second splash screen. The green windows mobile with farias names at the bottom loads, then the topbar of windows mobile loads with the start button, but then nothing else.
I've tried reflashing it in forced bootload mode as well as doing a hard reset. no luck. The update utility keeps telling me that it is an invalid update tool, please get a newer update utility. I've tried taking the battery out for a while and from there doing forced bootloader. Still no luck
Any suggestions?
daddy_yankee1980 said:
I think my 8125 is bricked. I've never had a problem flashing roms until yesterday I tried Farias Kitchen ROM. I flashing went through ok like normal, but when it restarted, it gets a little bit after the second splash screen. The green windows mobile with farias names at the bottom loads, then the topbar of windows mobile loads with the start button, but then nothing else.
I've tried reflashing it in forced bootload mode as well as doing a hard reset. no luck. The update utility keeps telling me that it is an invalid update tool, please get a newer update utility. I've tried taking the battery out for a while and from there doing forced bootloader. Still no luck
Any suggestions?
Click to expand...
Click to collapse
What are you trying to re-flash it with in the BL?
You should be able to flash the loverom without a problem.
TaurusBullba said:
What are you trying to re-flash it with in the BL?
You should be able to flash the loverom without a problem.
Click to expand...
Click to collapse
Thanks, I'm gonna download it right now and try it. What is different about this ROM than any of the cooked roms I have already as well as and official one. All of them in past have worked for me without a problem until now.
daddy_yankee1980 said:
Thanks, I'm gonna download it right now and try it. What is different about this ROM than any of the cooked roms I have already as well as and official one. All of them in past have worked for me without a problem until now.
Click to expand...
Click to collapse
Well, it sounds like it may have just been a bad casserole you cooked.
But, you could probably even re-flash using your carrier ROM. This one is just a fool-proof way to get you back on your feet. This ROM is just G3/G4 independent and doesn't include a radio, ipl/spl, or extrom.
TaurusBullba said:
Well, it sounds like it may have just been a bad casserole you cooked.
But, you could probably even re-flash using your carrier ROM. This one is just a fool-proof way to get you back on your feet. This ROM is just G3/G4 independent and doesn't include a radio, ipl/spl, or extrom.
Click to expand...
Click to collapse
Nope, just tried flashing that ROM mentioned above, and still the same answer. It keeps telling me that I need to get a new update utility. That is so weird because I never had that problem. I have already tried flashing the official as well with no luck.
daddy_yankee1980 said:
Nope, just tried flashing that ROM mentioned above, and still the same answer. It keeps telling me that I need to get a new update utility. That is so weird because I never had that problem. I have already tried flashing the official as well with no luck.
Click to expand...
Click to collapse
So, how exactly are you updating it in the bootloader? (just curious)
TaurusBullba said:
So, how exactly are you updating it in the bootloader? (just curious)
Click to expand...
Click to collapse
I put the phone in bootload mode by pressing and holding the camera button, then resetting by pushing the reset hole which then loads it to a colorful screen which I assume is the bootloader screen. Then I just connect it and try to flash it using one of the ROMS i have. Thats how I did it the past couple of times.
What upgrade utility are you using? You might wanna try the one attached! It is the 'NO_ID' version and up to now it flashed everything! Simply extract the zip file to a folder on your desktop, then copy your nbf file in to it too and run the "ROMUpdateUtility_Wizard_NoID.exe"
hello
im having the same problem, i just tried it, didnt work for me
Did you CID unlock your phone before trying to flash it? Did you also try to flash it with your shipped ROM again?
My phone also appears to be bricked. It locked at 99%, and after trying the steps indicated in the core2.0 installer, it closed, and I'm having difficulty figuring out the next step. As is, I get ERROR [264] CONNECTION. Is there a way to get the phone functional enough to load an OS? I've been searching these forums for about 30 minutes and haven't found what I'm looking for. There should be a recovery wiki.
I have the same problem...
Junner2003 said:
Did you CID unlock your phone before trying to flash it? Did you also try to flash it with your shipped ROM again?
Click to expand...
Click to collapse
Hi Junner, i have the same problem too...i did a unlock CID before i try to put the core 2...but after the boot its freeze on splash screen and nothing happend...what can i do? help me please...tks a lot.
alissonguedes said:
Hi Junner, i have the same problem too...i did a unlock CID before i try to put the core 2...but after the boot its freeze on splash screen and nothing happend...what can i do? help me please...tks a lot.
Click to expand...
Click to collapse
First thing you could try is to flash it with your shipped ROM again (the one you had on there originally). If that does not work you might want to search the forum for the LOVE ROM ??? I never tried that one but people say it should worke on any device (G3 /G4).
I thing more
alissonguedes said:
Hi Junner, i have the same problem too...i did a unlock CID before i try to put the core 2...but after the boot its freeze on splash screen and nothing happend...what can i do? help me please...tks a lot.
Click to expand...
Click to collapse
Every rom that i put in the phone is the same...always freeze on the splash screen...
Junner2003 said:
First thing you could try is to flash it with your shipped ROM again (the one you had on there originally). If that does not work you might want to search the forum for the LOVE ROM ??? I never tried that one but people say it should worke on any device (G3 /G4).
Click to expand...
Click to collapse
I try LOVE too and nothing...the phone is G3 with ipl/spl 1.01
alissonguedes said:
I try LOVE too and nothing...the phone is G3 with ipl/spl 1.01
Click to expand...
Click to collapse
Did you try already to flash your shipped ROM?
I dont have one
Junner2003 said:
Did you try already to flash your shipped ROM?
Click to expand...
Click to collapse
I dont have one...
You can download the Official ROM directly from HTC's site.
alissonguedes said:
I dont have one...
Click to expand...
Click to collapse
Yeah, download that one if Cingular was the original one! If not: let me know what was on there originally!
Junner2003 said:
Yeah, download that one if Cingular was the original one! If not: let me know what was on there originally!
Click to expand...
Click to collapse
A mda vario tmobile from germany...

Upgrade Wont Work

Alright so I had a working Mobile 6 ROM on my HTC 8125 it was the Touch ROM, so I tried doing a hard reset one day by pressing the send key to format and it says formatting then FAT Format Failed or what not.
So I reflashed it with a different ROM as the Touch one wouldn't work anymore saying I needed a newer Touch ROM to flash it to my phone. It's running IPL 3.08 and 3.08 SPL not sure if that means I have to downgrade back to 2.x IPL/SPL. However so I got a new ROM flashed to it and it just sits at the booting screen for that ROM even though it successfully flashed. So once again I try the format and it says failed again.
What exactly are you asking for?
I've flashed my tmobile MDA a few times, but i'm no expert.. From what i've read, I believe the SPL/IPL version has to be specific for each ROM. The older one's have to start from scratch at 1.0x SPL/IPL, while the WM6 ROMs seem to be using the 2.0x version IPL/SPL.
What I'm trying to figure out is why it wont flash it's a unlocked phone and it says it flashes just fine goes to 100% reboots and gets stuck at the IPL/SPL OS Screen then if I do the voice dial / other button where it says press send to reset it says FAT Format Failed so I assume the WM6 isn't working right ive tried a few different ones too.
what I suggest is reflashing to your original wm5 rom, and moving on from there
Do you have a Link it's the Cingular 8125 HTC
Anyone? I've tried searching for the original ROM but cant find it.
So am I to understand no one has any clue where to get the original ROM? I've seen it on here before but the search feature is quite useless.
How about going to the source??
newbie2 said:
How about going to the source??
Click to expand...
Click to collapse
Hmm well that was too convinent didn't think of that. Now to hopefully see if that works. If not anyone have sugestions on what would cause this? The device is completely unlocked. Pretty much what happens is no matter what ROM it is, it gets stuck at the IPL / SPL / OS Screen and doesn't go any further. But I'm still waiting on the origional ROM download which is going slow as hell. So hopefully that will do it.
---------------
Origional ROMS now on it
IPL 2.25
SPL 2.25
GSM 02.25.11
OS 2.25.11.1
Cingular Screen still sits there and doesn't load, freaking crappy ass Windows product just another reason why I got a different phone.
I faced similar problem ("Format is failed") this morning:
http://forum.xda-developers.com/showthread.php?t=305453&page=3
After searching with the key words on the forum I found this very helpful to me:
http://forum.xda-developers.com/showthread.php?t=276963&highlight=format+is+failed
Cheers!
Just my luck I left my SD card for the phone at work (which I won't be back at for 3 weeks) bah.

I think I bricked my phone...

So I installed the updated ROM and Radio to see if I could get the GPS working...
Everything went fine, I had to call Verizon to get the AKEY, but everything worked after that. Then I decided to downgrade because I thought it was running a little slow, and I didn't like all the added programs.
That was where I messed up. I did everything like I thought I was supposed to. I used the RELOCKER, and flashed the older version of the VZW rom... well atleast I attempted to. My phone is stuck at 0% flashed.
Any ideas?
ajshah said:
So I installed the updated ROM and Radio to see if I could get the GPS working...
Everything went fine, I had to call Verizon to get the AKEY, but everything worked after that. Then I decided to downgrade because I thought it was running a little slow, and I didn't like all the added programs.
That was where I messed up. I did everything like I thought I was supposed to. I used the RELOCKER, and flashed the older version of the VZW rom... well atleast I attempted to. My phone is stuck at 0% flashed.
Any ideas?
Click to expand...
Click to collapse
It is really tough to brick a phone.
Just pull the battery and wait 3s. Then replace. It should boot back up to the last ROM installed.
The only problem with that is that it doesn't... its stuck on the bootloader screen...
ajshah said:
The only problem with that is that it doesn't... its stuck on the bootloader screen...
Click to expand...
Click to collapse
1) To get the Tricolor Bootloader Screen to come up (actually this may be where you are already - if so, skip to #2). You must simultaneously: (a) hold down the power button; (b) hold down the camera button; and (c) use your stylus to press the little reset button in the hole at the bottom of your 6800. This should pop up the Tricolor Bootloader screen if you'd installed this first, as instructed.
(2) Then plug it into the computer's USB port. Make sure that USB is NOT enabled in "Windows Mobile Device Center" (should be in your start->programs menu). Click on connection settings and turn off the checkbox for USB connection.
(3) Then run the 3.17 Rom loader. This will get you back up and running.
(4) Then start again and run the 2.09 or 2.17 Rom loader. It should load without a hitch.
(5) Then you will have to re-setup your your MSID and MDN. You will need your EPT.
3.17 Rom Loader? which one is that?
I know I am asking a lot, but I have been searching all day, and I am a relative n00b...
so Thank you soo much for helping me out...
I have the same problem as you. Relocked the phone and now I can't do anything. Tried flashing to different radios, different roms and nothing. I did get 1 rom to go to 1% complete but it told me I had the wrong vender(sic) or something
ajshah said:
3.17 Rom Loader? which one is that?
I know I am asking a lot, but I have been searching all day, and I am a relative n00b...
so Thank you soo much for helping me out...
Click to expand...
Click to collapse
Hmm -- well maybe I need more info.
Which ROM did you 'upgrade' to?
I upgraded to the new one with GPS... I did everything in the steps, the way it said to do it...
Then I wanted to downgrade, and I saw how some1 else did it with relocking it and downgrading it, so now my bootloader reads:
TITA100
SPL-1.06.0000
CPLD-9
and it still says RUUNBH in the right corner...
Oh, and the SD card TITAIMG.nbh thing doesn't work either, unless I am doing it wrong...
The error I get is a 262 error, if that helps...
ajshah said:
I upgraded to the new one with GPS... I did everything in the steps, the way it said to do it...
Then I wanted to downgrade, and I saw how some1 else did it with relocking it and downgrading it, so now my bootloader reads:
TITA100
SPL-1.06.0000
CPLD-9
and it still says RUUNBH in the right corner...
Click to expand...
Click to collapse
Oh -- then just run the Official Released version of 2.17. You should be golden.
quantumforce1 said:
Oh -- then just run the Official Released version of 2.17. You should be golden.
Click to expand...
Click to collapse
Where can I find the official version?
do i need to go through all of this if i want to go back from the gps rom to the dcd kitchen/rom 2.0 or can i just flash back and you only have to relock if you want to go back to the stock rom?
friguy33 said:
do i need to go through all of this if i want to go back from the gps rom to the dcd kitchen/rom 2.0 or can i just flash back and you only have to relock if you want to go back to the stock rom?
Click to expand...
Click to collapse
I reflashed back to the 2.0 rom and I got stuck at the vzw logo screen so I tried to get the radio flashed back. I ended up trying to lock the spl and thats where i got screwed
quantumforce1 said:
Oh -- then just run the Official Released version of 2.17. You should be golden.
Click to expand...
Click to collapse
Tried that... Didn't work... I tried re-installing radio 1.40 first and then 2.17 and nothing, then i tried the other way... I still am stuck at 0% and then I get the 262 error...
friguy33 said:
do i need to go through all of this if i want to go back from the gps rom to the dcd kitchen/rom 2.0 or can i just flash back and you only have to relock if you want to go back to the stock rom?
Click to expand...
Click to collapse
Think of it this way ...
There are 'basically' three parts to the software that runs your phone.
1. There is the SPL / bootloader.
2. There is the Radio ROM.
3. There is the System ROM.
2 and 3 above will not load or work correctly if #1 above is bad or the wrong version.
Therefore, if you want to go back to 2.17 then the easiest way to do this is to:
1a. Get the ReLocker (which is SPL v1.06)
1b. *Don't worry that it stays in the boot loader mode.
2. Run your offical carriers released ROM, Sprint 2.17 (which will include both the System and Radio ROMs).
3. Reload your custom apps.
4. Sync.
5. *Remember from the previous article above, you will still need your EPST, MDN and MSID codes.
That's it.
If I reset, right before I get the tri color screen, it flashed a grey screen that says "no image file" for a second.
dagnasty said:
If I reset, right before I get the tri color screen, it flashed a grey screen that says "no image file" for a second.
Click to expand...
Click to collapse
Do you have the tri-color screen up? If so - what version?
Screen says:
TITA100
SPL-1.06.0000
CPLD-9
dagnasty said:
Screen says:
TITA100
SPL-1.06.0000
CPLD-9
Click to expand...
Click to collapse
Mine says the same ****....
Does yours flash "no image file" right before you get the tricolor screen?

Categories

Resources