Related
I think i must have the worst luck or else I'm doing something stupidily wrong...
I fried my device when trying to apply the bigstorage hack on ROM version 1.12WWE.
A week later my mate asked me to do the same on his JAM- same thing again- device just totally fried!
I had successfully applied the bigstorage hack on both the above devices with the original T-Mobile Rom (1.01 or something)- this went without a single hitch.
The method I used was using the 'Bigstorage software'
Do i need overwite the first 416 bytes even if im using my own rom and not a downloaded one?
What am I doing wrong?? This has really got me frustrated now.
Any insight as to what I could be doing wrong would be very much appreciated.
Thanks
Quite a few people have reported to get a totally "dead" magician using the "Make BigStorage" method. The good news is that when they return the machine to the service center, it can be fixed.
This is different from the "stuck at bootloader or splash screen" cases, which can be easily recovered by the user without the need to return it for repair.
It is much more safe to use the "edit two bytes at two locations" method to get BigStorage.
Talents- I was guessing that it would be you to reply- much appreciated for that . I was/am 99.9% confident that the service centre would get it working again. My frustrastion comes from figuring out what I am doing wrong. I am stumbled even with professional background (IT/PCs!).
So is it just my worst luck- or could I have done something wrong, unknowningly?
As much I want the latest ROM and bigstorage- i dont think i can run that risk again- even with the 'two bytes' method.
P.S. I was using a 128MB SD to perform hack- surely this is enough?
I recently did the bigrom hack, and had the same problem. after the device took the hacked rom, i soft reset, and it stayed on the boot screen for 25 mins.
I re-flashed the original non edited dumped rom to the device and it worked, copied the hacked rom to the card, and tried to flash again....and it worked.
My heart stopped when i just hung on the boot logo originaly.
Imp
Impossible,
From what I can gather the problem that you had is (was) not fatal... when I performed the bigstorage hack the device was TRUELY dead- nothing showing on the screen whatsoever... as Talents has also mentioned.
Anyway I had it sent off to the repair centre and have a brand new JAM back. Performed the 'two bytes' bigstorage method (thanks to Talents) and all is running well
Glad you didnt loose will in the upgrade.
Where abouts did you have to send your dead handset to, how long did it take to get a replacement.
Imp
In the end performing the upgrade was purely for the fact of doing it for the sake of it and frustration.
My original JAM was only about 2 and bit months old so it was still under warranty- returned to the place of purchase- T-mobile centre.
My one took 8 working days for me to get back but my mate's one took only 3 days.
Hello,
I experience same trouble as u all, still wasn't able to get the big storage to work. Let me tell u what I already tried:
Had a good working Dutch Orange M500 device with 1.06 original ROM. Udated it to 1.11 WWE I-mate ROM, no prob. Opend the storagespace with the mksBigStorage method, no problem,had 27MB free.
Updated to latest 1.12 original new Orange ROM via USB-cable method, no problem.
Now I want to open bigstorage on this original Orange 1.12 ROM, and no matter what I try, I cant get it to work.
-Tried yesterday all day, got a backup from CLEAN Orange 1.12 ROM, edited it with mksbigstorage program, no success at all. Got through all the steps, it goes to 100 %, checksum fale, upgrade fail message. Now it is stuck in bootloader mode.
-Edited original clean ROM with "edit two bytes at two locations" method, got through all the steps, it goes to 100 %, checksum fale, upgrade fail message. Again stuck in bootloader mode. Funny thing was that when I edited the rom, I only found 1 location in the ROM to edit, not 2. Went through it with the following query in the Bytes field: 02 00 00 80 00 20.
Maybe this is my mistake? Anyhow:
- got an external reader today, after trying all day yesterday with internal reader. Doesn't seem to make any difference, no matter what method, still no big storage. Did the whole process again, both metods. No luck until now. WHAT AM I DOING WRONG???
Yoho, I did it! It turns out that my 128 MB SD-card is giving me trouble, when I used the 512 card it finally worked!!
Hi all,
Have purchased a German MDA_C and flashed it to the latest dutch WWE rom (1.13). I use the NOID updater and get an error message at 99% of the update.
After this my MDA hangs at the splash screen (but showing updated rom and radio versions).
Doing a lot of soft and hard resets I managed to get by the splash screen 1 time...
Tried a lot of different rom versions but each time I get the same problem
I've read that the SPLASH screen problem is more or less common but I wasn't able to find a solution on the forum.
Now I made one stupid mistake... I did not backup the original rom...
Any suggestions how to get up and running?
Thanks in advance...
BuDDaH
The very first boot takes a long time, 15 mins for some! If you're not waiting for around 15 mins ....
Thanks for this valuable information kta.
This time I waited 1 hour after upgrading just to be sure.
same result. flashing stops at 99% of the CE Rom.
Hard reset shows splash screen with version numbers (radio 1.13 rom 1.13 wwe) and then just hangs.
From bad to worse
So I had a MDA_C that did not boot further than the splash screen.
Updated using the MaUpgradeUt_noID.exe. Thought I'd give the SD way a try since I already tried about 6 different roms all with the same result.
First I made a backup to SD card of what was in my MDA using romupdate.exe
extracted the file to my HD.
After extracting (and securing the device ID) I tried rebooting my MDA.
Now things got worse!!! instead of the splashscreen I now have the BLACK SCREEN......
Have tried resetting and hard resetting dozens of times (more like a thousand times) and only occasionaly the splash screen comes up. :roll:
But over the last couple of days I only managed to get the bootloader 1 time (and at that time there was no SD card inside) :shock:
this is behaviour I haven't read about on the forum.
Guess I will have to get it serviced.
Is there anyone on the board that has an address in the Netherlands that can flash or repair my mda? Not sure T-Mobile NL services German devices...
Thanks!
Not dead yet?
Here's some more info.
My 'almost dead' Magician is showing signs of life.
I had the BLACK SCREEN.... (first couple of lines of pixels were not black)
After thousands of hard and soft resets (soft resets seemed to have the best results) I managed to get into the bootloader!! Flashed with an older rom and at least I'm getting the splash screen again. (but still getting an error at 99% of update of the CE rom).
I'm updating using the exe in bootloader mode btw....
Since there's always an error at 99% when I use the exe method and the device is not booting I thought about giving the SD method a shot.
My device didn's show the SD option but fortunately tadzio explained about the MBR (didn't even know a SD card had one!!! :lol:
http://forum.xda-developers.com/viewtopic.php?t=32849
When I decode a nbf file using nbfdec.exe and flashing afterwards I get a message that my ROM is to small.
Size is same as nbf file.
How do I correctly decode a nbf file?
Thanks for the help.
BuDDaH
Don't use a nbf, get a dumped or bs rom from the ftp & follow instructions with copying bytes etc.
M
Ok OLTP I'll skip the nbf decoding route.
Think one of the problems is the way the newer roms are encoded.....
Saw you're using a 1.13 bigstorage rom?
That one is not on the ftp is it?
Modified your own rom image?
Hi BuDDaH,
I downloaded at the Dutch TMO site the shipped-rom, unzipped the exe file & decoded the nk.nbf nbfdec. In this nk.nb1 I altered the usual BS bit patterns and re-encoded the nk.nb1, again with nbfdec, to the nk.nbf. After that it was just running, the extracted, upgrade program & it worked like the usual shipped-rom upgrade. you might have to use the maupgrade_noid version, sometimes twice.
This method is better described in the thread about upgrading to radio 1.13 which you can add along the road as well.
So yes I made it myself, not so fond of using other people's rom unless I have to. Please don't let anyone be offended by this, cause a replaced bit can cause serious harm, like I encountered myself, with my own corrupted rom-dump.
Good luck, M
Just wanted to update you all on the latest status.
I managed to flash a german rom (as I've got a German device) although I always get an error message at 99%.....
Fist it just stuck on the splash screen but this somehow deteriorated. Now I get a black screen covering about 5/6th of the screen. the first 1/6th shows a part of the splash screen. No backlight and it hangs.
No more bootloader so I need to have it serviced (anybody knows what the techies do with such a device?)....
Now the question remains where.
T-Mobile NL refuses to service it since the IMEI is unknown to their system
T-mobile Germany doesn't have a service center but only takes repairs through a T-Punkt shop..
Any ideas?
Thanks,
BuDDaH
Latest update...
I sent it in for repair and it turns out that the ROM is damaged and the phone needs a mainboard replacement..... which costs about the same as a new unit...
Anyone got a spare one laying around for me?
So much for my Magician!
Cheers,
BuDDaH....
Sorry to hear...did you try another SD card?
Yep I did; but unfotunately the situation deteriorated and I'm completely unable to get into bootloader mode.....
Well.. :idea: maybe I must see this as a great opportunity to get wild with a set of scewdrivers
Hey BuddaH,
There enough people interested in the parts here at the forum, so there's a tiny brightside on your adventure :-(, man i do feel sorry for you.
Regards, M
Yup, i need some parts also
BuDDaH said:
Yep I did; but unfotunately the situation deteriorated and I'm completely unable to get into bootloader mode.....
Well.. :idea: maybe I must see this as a great opportunity to get wild with a set of scewdrivers
Click to expand...
Click to collapse
You probably ran the battery down. I don't think it charges unless the ROM is working. That is why it is highly recommended that you start with a full charge before commencing a ROM update.
Hi Stevedebbi,
Even in my situation the it still seemed possible to charge the battery (at least the red light went out and the battery got hot).
Sent my device to apexlaptops.co.uk cause they claimed they reflash...
Got the reply back that they couldn't get it too bootloader mode and were unable to repair. (guess they could not do some JTAG debugging).
I may be able to buy a working device that's damaged on the outside....
I didn't read the unlocking SIM procedure by jocky properly. I understood that I MUST get HardSPL installed, and so I go the JumpSPL1.56-KAIS.exe to the phone and then executed it. It got me the tri-color screen (Is this called bootloader?) and then I executed the KaiserCustomRUU.exe from the flash-HardSPL.zip thinking that this will put in the HardSPL into the ROM. The progress bar went upto 95% and then it exited with error and after that the "Recovery" option of the loader hasn't been able to revive the phone. Every time, I put the battery back in and power it up, I get the tri-color screen with the following message:
RUUNBH (on the top right hand side of the screen)
KAIS1*0
SPL-1.56.0000
CPLD-8
I think I now understand the mistake I made. I had a bunch of .nbh files in the directory from where I ran the KaiserCustomRUU after extracting and that is why it must have failed. Now every time I get the tri-color screen when I boot up.
Can someone please help me recover from this position? I have now got the actual simunlocker zip from the original thread and extracted it with folder names and so now I am ready to try again, only if I can recover from the mess I created. Please help!!!
mtty recovered, but I get back the bootloader every time I power up
I used mtty (set 14 0 and boot) to make the phone work (now data was lost and all my prgrams were still there). However, every time I power up my phone, the tri-color screen is back. How can I resolve this?
When I run mtty, I get the following messages on mtty:
set 14 0
HTCST ÚÈÒHTCE
Cmd>boot
InitDisplay: Display_Chip=1
No card inserted
OSSIReadBack ++
Read SI data from flash success
tail signature match
Checksum match
UserStorageSIPreload ++
FMD_ReadSector+, bad block no=0xFAC0, status:0x0
flash the original rom your device came with! only shot buddy!
Thanks for the advice. Where do I get the original ROM and how do I flash it? After the mess I created, I want to be doubly sure. I remember the versions of ROM that the phone used to show during bootup was R1.27.12.11 and D1.56.00.00 (I don't remember the G number). Appreciate if you could let me know. I have downloaded the Radio ROM numbered 1.27.12.11... is that the original ROM?
if it's a tilt, flashing the original rom will not work, you will get an invalid model error. Instead, use this one RUU_Kaiser_CINGULAR_WWE_1.61.502.2.exe. Trust me, been there done that. (twice)
Once you've done flashing to RUU_Kaiser_CINGULAR_WWE_1.61.502.2.exe and you want to unlock, HardSPL, then flash it back to RUU_Kaiser_CINGULAR_WWE_1.57.502.2, then start w/ step 1 from simunlock.
the_passenger said:
if it's a tilt, flashing the original rom will now work, you will get an invalid model error. Instead, use this one RUU_Kaiser_CINGULAR_WWE_1.61.502.2.exe. Trust me, been there done that. (twice)
Once you've done flashing to RUU_Kaiser_CINGULAR_WWE_1.61.502.2.exe and you want to unlock, HardSPL, then flash it back to RUU_Kaiser_CINGULAR_WWE_1.57.502.2, then start w/ step 1 from simunlock.
Click to expand...
Click to collapse
Did you mean to attach the ROM because it isn't there? I found this thread http://forum.xda-developers.com/showthread.php?t=335568 and it shows a ATT_SPL ROM. But, I ran out of free download limits from rapidshare for today (tonight). Is that the correct procedure? And when you say "flash" the ROM, please correct me if my understanding is wrong:
1. Get the bootloader running (tri-color screen). In my case, just power cycling does it.
2. Have the .nbh file for the ROM and the KaiserCustomRUU.exe in a folder with no other files in it in your PC.
3. Execute the .exe file which should take me thru the prompts on the PC to flash the ROM. I should see a progress bar on the PC as well as cellphone.
Is this procedure correct?
If I am able to get the device back to original state, I will need to find out how I can get the HardSPL loaded "definitively" as well.
sigh, I thought you know how to flash. Anyway, i'm being nice tonight.
http://wiki.xda-developers.com/index.php?pagename=Kaiser_ROMs
get the 1.61.502.2 from that link. put your phone into that tri-color screen, run the exe file you just download. That will bring your Tilt back, if you want to unlock the phone, then read my previous post again, and again and again if you still dont get it.
the_passenger said:
sigh, I thought you know how to flash. Anyway, i'm being nice tonight.
http://wiki.xda-developers.com/index.php?pagename=Kaiser_ROMs
get the 1.61.502.2 from that link. put your phone into that tri-color screen, run the exe file you just download. That will bring your Tilt back, if you want to unlock the phone, then read my previous post again, and again and again if you still dont get it.
Click to expand...
Click to collapse
I know why you feel that way. But, since I screwed up a simple process, my grey cells have really degenerated. My apologies for being dense. I did download that file from the original post of the thread, but now I have run out of free downloads from Rapidshare and I don't have a paypal account. I have to wait another 1hr before it allows me to download. I will try using the Cingular file to flash the device. Fingers crossed!!!
It'll work, dont worry. Just get a new ip and d/l from rapidshare.
Got error 294: Invalid vendor ID, just 1% into flashing. How can I make the phone not go into the boot loader every time I power it ON? Currently, I am using mtty to boot it out of the bootloader.
PS: I had earlier today downloaded the Cingular ROM, but its size as shown in Rapidshare is different from the one you pointed to. I will try that once Rapidshare allows me to.
Looks like the vendor id got screwed up when I had incorrectly flashed the device as I am not able to send emails (POP yahoo mail) or get Direct Push Mail (Outlook) working now. Before this attempt of mine to unlock the SIM, the yahoo and outlook was working fine. Now, during activesync, it says "waiting for network". I am able to browse the internet using PIE though.
I hope the AT&T ROM flashing works.
Downloaded the 1.61 ROM and was able to flash it successfully. It installed all the apps that came with ROM. However, I am not able to access my yahoo POP mail nor my Outlook. I am able to browse the internet though.
Is there a way to get the original AT&T ROM (v1.56) with the 1.27.12.11 radio? I know that that ROM worked fine with my data connections.
Edit: I am able to sync Outlook and Yahoo successfully now with the 1.61 ROM itself.
Thanks to all who helped me with this. I can't thank enough.
Try this first: http://forum.xda-developers.com/showpost.php?p=1894935&postcount=135
i screwed up TytnII
dear all...after flashing my tytnII with DCS V1.3 rom my tytnII is unable to boot up again. the only show on the screen is word "smart mobility" and 3 red lines below it. i have tried everything included hard reset, remove sim card and SD card but still wont help me. i also tried to flashed again but i cannot communicate with activesyn anymore. please if there still way to safe my baby...
Enter to bootloader,and then flash again
thank you for you advice.finally my tyntII is back on line...thanks again my man
jockyw2001 said:
Try this first: http://forum.xda-developers.com/showpost.php?p=1894935&postcount=135
Click to expand...
Click to collapse
Thanks jockyw2001.
Now that my phone is working nicely with the modified AT&T ROM, I want to attempt unlocking the SIM again. I screwed up when I tried to install HardSPL. I will write the procedure here from what I understood from your posts (and thank you very very much for your work). Appreciate if you can confirm that before I show my stupidity again.
Steps:
1. Go to the bootloader by executing JumpSPL1.56-KAIS.exe from the phone
2. Connect thru USB to my Win XP laptop (the loader should show USB)
3. Unzip the contents of flash-HardSPL.zip into an empty folder which will put KaiserCustomRUU.exe and kaiser_hardSPL_1.0.nbh files into the folder.
4. Run the .exe file from that folder which will bring up the ROM loader utility which will automatically load the .nbh file located in the same folder. This will result in the HardSPL being loaded into the phone and the SPL string as seen on the boot loader will change to SPL-1.0 OliPof. Is that a confirmation that HardSPL is loaded?
Can I get out of the boot loader mode after loading HardSPL and continue to use my phone and then attempt the SIM unlocking later?
My phone currently has the AT&T ROm v1.61.502.2 with the Radio ROM v1.27.14.09. Will jocky's unlock method work with this?
I have an unusual problem with my oem att tilt running SPL-1.56.0000 (according to the bootloader screen).
The ROM is somehow corrupted in that it will not boot past the giant ATT logo and coordinates (?) screen. I have been having some trouble with the device, but this is a new occurrence not related to anything I did. I have never reflashed the ROM, and because it is in a current hosed state I cannot run hardspl on the device.
I have tried reloading many of the "ATT OEM" ROMs I can find, but they all return "Invalid ID" error the ROM uploader I believe because the versions don't match.
Is there any way to reflash the ROM and bootloader on the device without having first run hardspl? Am I SOL?
Thanks
RK
Did you try going to tri-color first then flashing a stock tilt rom?
Dude, I have the same problem...
I bought the tilt 2 weeks when I was in a business travel in the US and came back to Argentina... I'm kind of screwed about the warranty 'cause I don't think I'll go again so soon to the US...
Is there anybody who can help us with this?
The very diference is that (At the ATT start up Logo screen) the bottom line says D 1.57.00.00 instead of D 1.56.00.00.
Tried everything... soft reset, hard reset... and so on...
The thing is that at some point I think I can get to the phone in some way since if I turn on the phone keeping pressed the camera button and enter in the rom loader screen I can get comm to the phone using mtty (As pof explained to do for "Un-brick" the phone (In the case you got a bad flashing) in this thread...
So, please If anybody have any idea it would be great!
I still have a little hope, because it's like there is some kind of communication between the phone and the computer...
Thanks in advance to any help.
A.
both of you...
Check my sticky thread for reverting back to the stock tilt ROM and SPL...
all you really need from there is the Stock ATT ROM... download it!
Put your phone in Bootloader (shouldn't be too difficult by the sounds of it)
Install the stock ATT ROM.
If this doesn't work try extracting the downloaded ROM (using WinRAR or similar) then just run the ROMUpdateUtility.exe
Then you might want to consider installing HardSPL... the default download should work for the 1.56 guy. The 1.57 guy will need to download jwocky2001's whitescreen fix (check the stickies).
Good Luck!
I am at the tricolor screen and I have tried the instructions on your thread (thanks very much for making it so easy). However, it says invalid vendor ID after loading 1%; the device automatically reboots and reverts back to the ATT screen until I place it back into the tricolor bootloader again. I thought this was because the version I'm running is 1.56 and I could only find two original OEM ATT ROMs, neither was 1.56 and both failed.
BTW I couldn't do the part about hardspl and running the kaiser program on the device for obvious reasons, but I could get the kaiserruu program to recognize the device, another ROM and attempt to upload it.
Any other thoughts? Do I really need the exact same ATT OEM ROM as what is on the device or is something else wrong?
Thanks again
RK
does anyone have the official TMo Dash 3g ROM upgrade (ver 1.17.531.6) that was on Tmo's site? It's been removed from their site, and I searched in the forums but can't seem to find it.
edit...never mind...found it.
It's still up on T-Mobile's site.
Try: www.t-mobileusa.com/wmupgrade
Was thee just now.....
Dash 3G Update
http://rapidshare.com/files/331920783/RUU_Captain_S_TMOUS_2.06.531.4_Radio_Signed_MAPLE_61.36t.25.29_3.47.25.48m_Ship.rar
brad1825 said:
http://rapidshare.com/files/331920783/RUU_Captain_S_TMOUS_2.06.531.4_Radio_Signed_MAPLE_61.36t.25.29_3.47.25.48m_Ship.rar
Click to expand...
Click to collapse
Any chance someone can mirror this on mediafire? DOWNLOAD SPEED ON RAPIDSHARE IS AT 38K RIGHT NOW!!!!
official tmo 6.5 locks up at 27%
anyone find a fix for this?
happens with hard spl 1.17 and 1.19
I would imagine if you "reset" the spl to 1.17 or 1.19 it will load.
I loaded it on a "virgin" Dash 3G new out of the box. During the upgrade process, it reset at 13%, and then paused for a FEW MINUTES at 27% (using XP).
Go back to this thread and reload the "Original SPL" on your Dash, and then try again. http://forum.xda-developers.com/showthread.php?t=550620
Works fine, EXCEPT for the notifications and reminders "VIB" functions as set up in my Profile settings. Looks like HTC is determined to "upgrade" the volume control at the expense of full profile functionality.........looks like the end of the road with WM (Sph) for me. I rely on the vibrate reminders in particular for meetings etc. Back to 6.1 for the moment.
Spl 1.26.0000
Good Day,
To load this without error...
First Download
Dash3G (Maple): SSPL, HardSPL and original SPL by Jock Dash3G then extract to a file and remove 1.19 hard spl.nbh and any other nbh files.
Then Extract the The new 3g rom to a file, copy the spl.nbh from there into the file you extracted Dash3G (Maple): SSPL, HardSPL and original SPL by JockyW
Run the auto exe and flash the new spl to your Maple.
after the phone is done customizing flash the new rom.
Work for me... Good luck
Spl 1.25.000
I folowed your instruction but I have an issue with with flashing the original SPL, it stop on 97%, after a while i gave up and after rebooting the phone the SPL reads 1.25.000 then flash the t-mobile 6.5ROM and it went through and my phone is happy. me too.
Still not able to flash the T-Mobile version
Tried the ideas on here but still cannot get this version flashed.
abofihmi said:
I folowed your instruction but I have an issue with with flashing the original SPL, it stop on 97%, after a while i gave up and after rebooting the phone the SPL reads 1.25.000 then flash the t-mobile 6.5ROM and it went through and my phone is happy. me too.
Click to expand...
Click to collapse
Upgrading to 6.5
Of course, T-Mobile tech support's solution is to send a new phone! I don't believe for an instant that this will have ANYTHING to do with solving the problem but, well, it is new and shiny!
When I downgraded to 6.1, that changed the spl to 1.17 from 1.19. Is
that what is being referred to? I tried the hard reset before as well.
Tried to upgrade from 6.1 to the t-mobile official version. I don't seem to have a problem going to the Windows Mobile 6.5 3VO version. I tried calling T-Mobile tech support but, surprise, their solution is to send me a new Dash! Okay, I don't mind the new phone but it really shouldn't be necessary. I guess having a new one will be easier to do the official upgrade.
Any instructions on what I should do to get the phone in a format so I
can do the upgrade would be appreciated. Is there a way to do the
upgrade from the memory stick?
abofihmi said:
I folowed your instruction but I have an issue with with flashing the original SPL, it stop on 97%, after a while i gave up and after rebooting the phone the SPL reads 1.25.000 then flash the t-mobile 6.5ROM and it went through and my phone is happy. me too.
Click to expand...
Click to collapse
I have confirmed this. You can not just run Jockys RomUpdateUtility.exe though, it will not work. You must run the auto.bat from within winmo. If you are stuck at the tri color then just reflash any spl (jocky) using the romupdateutility and it should boot. Then run the auto.bat. It will freeze at 97%, remove battery and USB, insert battery. You will see tri color with error code. Run T-mobile update and it should work.
EDIT:
Ok so to recap
1) Extract Jockeys HARD SPL and T-Mobile's 6.5 Rom into seperate folders.
2) Delete any .nbh files from Jockys directory
3) Copy the SPL.nbh from T-mobile directory into Jockeys
4) Run jockys auto.bat with your phone started up in windows mobile.
5) It will freeze at 97%, wait a minute and remove battery and usb.
6) Re-insert battery and power on. You will see tri color with error code.
7) Run the ROMUpdateUtility.exe from T-mobile 6.5 directory.
If you are stuck at tri color and cant boot into windows mobile to run auto.bat:
1) Follow steps 1 - 3 above.
2) run the ROMUpdateUtility.exe in Jockys directory. It will complete but will not change the SPL for some reason and boot into windows mobile.
3) Continue from step 4 above.
I downloaded the new ROM from t-mobile but it’s an executable. How do I extract the spl from this file?
Any help would be appreciated.
If you right click the ROM you can extract it. Just extract it to a folder. Then follow the instructions.
Finally got this to install!
I had to revert back to my original SPL by replacing the hard_SPL in the main folder and then running auto.bat (just running the RUU doesn't work).
The I ran the new T-Mobile ROM and it froze, but installed the new SPL.
Ran it again and it worked!
Hi aaronbaird1
Very thank you for the instructions to fix. 6.5 ROM update I was successful.
thanks a lot