Concise guide to upgrading to WM6.1?/michyrom - Advantage X7500, MDA Ameo ROM Development

Hi there,
I'm looking to upgrade my stock (and unlocked) x7501 to WM6.1. First up i'd like to say that I *have* read the forums, and I *have* read lots of threads about upgrading. Unfortunately it seems I still don't understand what the entire process is.
Firstly, what is SPL? I could not discover what this acronym means. Thus, how do I determine my SPL version, and does this have anything to do with the fact that my phone is factory unlocked or not? Apparently the first step is to run something like Hard-SPL unlocker but my phone is unlocked - I don't want to do something unnecessary or brick the phone.
It seems unfortunate that other users asking similar questions to me got flamed for not reading or 'not reading enough' but i can say that unless i missed a crucial reading thread (i have read all the stickys) then it certainly isnt very clear what the process is.
Any help much appreciated.

hi
a little help on the acronyms from the wiki page:
CID lock (aka vendor lock): puts on your device by the manufacturer to prevent installation of a ROM not released by them.
HardSPL: This modified bootloader allows a much safer flashing process to take place since it reduces the chance of permenently bricking your device. It also removes the need to CID Unlock the device since it ALWAYS reports SuperCID when flashing. See the official thread for more info.
Hard Reset: Similar to a soft reset, by performing a hard reset you completely wipe your device and restore it to the position it was in when you first turned the device on after it was purchased or after a new ROM is flashed.
Radio: The radio stack is responsible for the phone functionality of the device. This includes GPRS, GSM, UMTS, and GPS operations as well as camera functionality. The version you use depends on who your carrier is as users have reported versions working better on one carrier than the other. The wiki pages contain the latest versions available to download and install.
ROM: The ROM holds the Operating system and other components such as the bluetooth and wifi stacks. The ROM is accompanied by the Radio, Ext_ROM, SPL and IPL. Carriers such as T-mobile or Vodaphone taylor the ROM to their specifications and version numbers do not carry the same meaning across different carriers. IF the carrier you use supports the device well they will usually release regular ROM updates.
RUU - ROM Upgrade Utility: It’s the s/w used on your PC to do a ROM upgrade for your PPC;
IPL - Initial Program Loader: It’s the bootloader for PPC. It boots up SPL;
SPL - Secondary Program Loader: Loads the actual OS;
WWE: World Wide English Edition;
SSPL: SSPL is a modified bootloader which is loaded into RAM when run, this allows us to overwrite any aspect of the ROM, Radio or Bootloader far easier than using mtty.

I agree
I have noticed a lot of members with only a few posts asking questions and making fundamental mistakes and I usually say "read the wiki and do a search " but I did just that and there are a confusing array of answers.
I wil try to do an idiots guide later and post it here unless someone with more time does it first

Thanks robson/lakeman, that actually helps a lot.
So... We want to put a new SPL on the system, so that the IPL loads the new SPL (HardSPL), which gets around CID locking to allow you to flash the ROM via an RUU?

Also, would like to add that there are two types of rom's.
Rom's for SPL1.2 and rom's for SPL3.5
If it is the first time I would suggest you first, to load SPL1.2 rom's
This way you can go back to original rom's very easy.
Rom's made to SPL3.5 gives more freedom to rom cookers, but once you are on SPL3.5 you cannot go back to original rom's unless you first revert to SPL1.2 first.
The process to revert from SPL1.2 to SPL3.5 and viceversa can be very tricky and can give you a lot of headackes.
You will need to read a lot and be aware of posible problems ( and resolutions ).
Welcome to this wonderfull world

re: spl and upgrading roms
putting aside my previous post, that's probably as far as i can go in terms of the techie stuff =)
my story: i was actually content with my original, untouched u1000 rom. then something happened with my bluetooth (all sounds kept on being streaming even without the bt activated)...that forced me to upgrade to ap3...probably the first rom upgrade that was made available for the u1000. i sorta felt that i had nothing to lose...if the rom upgrade couldn't fix the bt issue...then i'd get a replacement unit...
once i upgraded to ap3...and it was successful...i then tried out the rom upgrade by irus. it was fantastic...most notable was the auto-rotate feature....but apparently i was having some vga issues as i couldn't get 96dpi to work. that's when i installed michy's rom and i've been having a blast since then.
my point: i really can't answer the spl part in your original post...i kinda remember how to find the spl version....but i don't want to end up bricking or damaging your unit. there are others in the athena forum who are best qualified to answer that.....but once you get beyond this, let me know and i'd be happy to help you out in upgrading to michy's rom.
cheers

Robson, cool, your input is much appreciated. I think the first step is to find out my SPL version. I'll hunt around the forums/wiki for that, but if anyone knows off the top of their head, feel free to post.

Press all the way in the camera button and at the same time soft-reset.
Keep until it displays the famous tri-color screen. Loose buttons.
You will see something like this ( in my case ):
ATHE100
IPL-v1.00
ATHE100
SPL-v1.20.Olipro ( because I have already unlocked )
If your unit is virgin you will be SPL-v1.00 if I remember well.
regards,

Related

Need answer to understand few basic questions

I have read a lot on these forum but still can't understand few basic things.
I have upgraded my cingular 8525 with black dymond 3.5
Currently I have IPL 1.04 / SPL 2.10 Olipro / Radio Version 1.40.30.00
I followed the guide and installed SPL 2.10 Olipro before ugrading to prevent it from getting brick device...SPL 2.10 bypasses CID... corrupt sectors in ROM will not cause problem as it bypasses CID.. Can somebody explain these things in little detail please.
What exacltly SPL 2.10 does?
If some thing goes wrong while flashing - will I be able to install original cingular - att ROM?
Is SPL 2.10 permenantly install on device or it will be removed by ATT rom?
What is CID and What is super CID?
What other precautions I need to take besides this to prevent my phone from becoming brick device?
Again - I have no plan to go back to ATT rom, this is only if something terribly goes wrong.
GG
You've definitely done your reading and more or less have it right.
CID is an area of the radio bootloader that primarily "locks" your phone to a particular carrier. If you bollocks a radio flash and it becomes corrupt, you've "bricked" your device and it can be rather difficult to recover.
Hard-SPL is a brilliantly patched version of the SPL by Mr. Olipro that makes your device appear as SuperCID without having actually updated the "real" CID (which one used to have to do). SuperCID will allow you to flash any ROM to your device (not just the ones for your carrier) and enables some otherwise blocked commands, thereby giving you room to maneuver if you happen to "brick".
Hard-SPL also has a patched 'task 2a' command that will recover bad blocks (provided they aren't physical bad blocks from the factory) that can develop on your device as a result of flashing.
By design Hard-SPL prevents itself from being overwritten, but it can be done if you need to send your phone in for warranty, etc. There's a guide for that and several threads, too.
You've done about as much as you can to protect your Hermes. Good job!
Thanks vp3G for your explanation. Much appriciated.
GG

Upgrading, HardSPL, SuperCID.. confused, a little... help??

Sorry chaps, bit of a newb with the phone flashing, although experienced in general PC/I.T hardware etc... so usually get to grips with things techy...
Read the posts on HardSPL, but doesnt really explain what it is, what it does, or how it stops your phone getting bricked..the only thing I do understand that it is a MUST if you want to flash your rom. Which incidently I have successfully done twice now!! ALthough I know the enclosed quote mentions some of its features, I dont even know what SPL is..!! doh!!!
So its on my phone (Orange's M3100 flavour)...!! Now I assume this will let me quite happily swap roms to my hearts content...? Would this also include the hopefully forthcomming official Tytn/Hermes WM6 rom??
Now with regards to unlocking the phone for any network provider, this is where the SuperCID comes in?? Have I not read that having having HardSPL-2.10 enables SuperCID...??
CURRENT FEATURES
-SuperCID ????
-no file signing required
-no password required to authenticate with bootloader
-bad NAND can be recovered with "task 2a"
-bad NAND can be recovered by flashing an OS
-SPL protected from all HTC retail SPLs being flashed by accident (to bypass, use SSPL)
-IPL protected from all flashes; protection against bogus NBH's
-bad NAND can again be checked for with "info 8"
-version displays 2.10.Olipro
-no longer tries to read bad NAND - should fix whitescreen issue
ChangeLog
Hard-SPL-2.10
-based on a newer SPL base; bugfixes.
-IPL flashing disabled to prevent bogus NBHs bricking your device.
Click to expand...
Click to collapse
When flashing roms, am I supposed to check the "Is it hard-SPL" and the "SPL-2.02/2.10 New Bootloader" in all instances???
ANy guidance would be great, jus tso I understand what Im doing, rahter than just doing it, albeit with success up to now!!
Thanks!!
DocSoton said:
Sorry chaps, bit of a newb with the phone flashing, although experienced in general PC/I.T hardware etc... so usually get to grips with things techy...
Read the posts on HardSPL, but doesnt really explain what it is, what it does, or how it stops your phone getting bricked..the only thing I do understand that it is a MUST if you want to flash your rom. Which incidently I have successfully done twice now!! ALthough I know the enclosed quote mentions some of its features, I dont even know what SPL is..!! doh!!!
So its on my phone (Orange's M3100 flavour)...!! Now I assume this will let me quite happily swap roms to my hearts content...? Would this also include the hopefully forthcomming official Tytn/Hermes WM6 rom??
Now with regards to unlocking the phone for any network provider, this is where the SuperCID comes in?? Have I not read that having having HardSPL-2.10 enables SuperCID...??
When flashing roms, am I supposed to check the "Is it hard-SPL" and the "SPL-2.02/2.10 New Bootloader" in all instances???
ANy guidance would be great, jus tso I understand what Im doing, rahter than just doing it, albeit with success up to now!!
Thanks!!
Click to expand...
Click to collapse
Read HERE
Upgrading & cooking:
Upgrading for beginners: first time flashing a ROM?
Upgrading FAQs: read this before asking questions!
Available Original Shipped ROM Versions
Available Extracted Radio Upgrade Only
Available Extended ROM Versions
How to Unlock and Unhide Extended ROM
Available Cooked WM5 and WM6 ROM versions
Hermes Upgrading Guide
MrVanx Hermes upgrade guides
ROM cooking and Bootloader 1.01 MFG
Hermes HardSPL project
Custom RUU Updater
Hermes ROM kitchen
What I did was Flash HardSPLv7 for hermes.. then I flash pof's Free CID/SIM unlocker for hermes... and my phone is superCID and can't be bricked unless I'm an absolute moron.
Thanks Binyo.. Id not stumbled across many of them pages... great help!!!

Why Hard SPL is needed?

Hello friends,
I have some question, My Rom was TNT4 because of more hanging my device I installed TNT 5, but this Rom is hanged my device more than TNT4.
I want to use Maxniper Roms. so i have some question:
1- Can I install new WM6 or WM6.1 or WM7 Roms to my PPC witouht Hard SPL?
2- WHat is Hard SPl? is it needed for new ROMs or for all WM6 roms such as TNT4 or TNT5 or Aserg AKU3.13(WM5) ?
3- Can i come back to past SPL?
my device is I-mate Jamin
Thanks
For easy explanation about hardSPL, check THIS thread.
For further info, check THIS thread.
duato said:
For easy explanation about hardSPL, check THIS thread.
For further info, check THIS thread.
Click to expand...
Click to collapse
Dear Friend,
I read all posts about HardSPL
But the question is:
What's the differ between Old Method and New Method(Hard SPL)?
If I install PDIViet_Temp rom first and Install new WM6 or WM6.1 or 7 after it hanging in boot screen and freezing is apperar and IF i use HardSPL method the problems not occur?
Thanks
WHy is needed ?
* More STORAGE area ! the smaller the os.nb the larger your storage!
I encourage all of you who haven't tried this method yet, to try this method. Specially if your favorite rom is relatively a clean rom and consequently has small os.nb. If you want to know how much extra storage you will get by using this method subtract the size of the os.nb (in kb) from 58,368. the difference will be the amount of storage you will gain when you try this new method.
* Faster and safer Rom Upgrade.. If you do install PDAVIET first and overwrite its Data later. It takes more time.
Without HARDSPL. Big Storage mode can't be use.
hma4 has wrote it. Why no one read it??
http://forum.xda-developers.com/showthread.php?t=350033
You can always revert your spl by flashing an operator ROM such as teh Orange WM5 ROM available on the FTP server.
Or O2 ROM Germany.
Info on O2 Germany Website HERE
Download XDA neo original ROM.Version 215447 2154140 021921 (ca. 50 MB)
HERE
or XDA neo RACE Edition.Version 215448 2154141 021921 (ca. 51 MB)
HERE
Different between them?
Nothings different, just first and second SPLASH Screen. And Price Different for XDA Neo Race Edition.
Race Edition is more expensive.
What's the differ between Old Method and New Method(Hard SPL)?
Click to expand...
Click to collapse
Old method needs to downgrade before you can upgrade. It needs batch files as well as ROM files etc.
If I install PDIViet_Temp rom first and Install new WM6 or WM6.1 or 7 after it hanging in boot screen and freezing is apperar and IF i use HardSPL method the problems not occur?
Click to expand...
Click to collapse
This is because HardSPL prevents certain checks being performed, so that the ROM can boot without being an official ROM. Without it, the SPL part of the loading mechanism refuses to boot the OS and instead reverts to bootloader.
The official way to upgrade your Prophet is to use the Rom Update Utility (RUU) provided by your vendor. The RUU is very convinient; it has all the OS files packed together in one archive, so nothing can be misplaced and it is executed just by connecting your device to your PC, no preparation needed. This RUU has the nasty habit the check your Prophet by using the SPL. If your device isn't the same brand (like Q-tek, Dopod, O2, XDA, etc, etc,) it just refuses to work. Because of this it was practical unpossible to post a universal upgrade overhere.
Some genius people developped a way to replace the OS through the "backdoor". With the help of this set of hacking tools it became possible to upgrade your Prophet with a universal, homemade ROM. However, because of the complexity of this method (now refered to as the "Old Method") it was very funurable to errors an needed a lot of preparation. Also the OS-file cannot be combined in one single archive as with the RUU. The cange of loosing or misplacing one is there.
So the challenge became to find a way to use the RUU without the check. So other genius people find out a way to manipulate the SPL so the RUU will bypass its check and will work as if it was released by an offical vendor.
This SPL manipulation can be done for one time use only use SoftSPL (JumpSPL), the original SPL will stay resident but is bypassed prior to running the RUU. If you flash a lot this method is time consuming, but the advantage is that it won't interfere with your device (except upgrading the OS ofcourse...)
An other way is to use HardSPL. This will replace your SPL with a manipulated version wich will stay resident until you install another SPL. This way the first flash-cycle will be a bit complicated but the following atempt will be as easy as connecting your device to a non-Vista PC and run the provided RUU.
The downsite of this successtory is that it installing the HardSPL seems to be a tricky procedure where a lot of people obvious are making a lot of mistakes.

guidence please

Greetings,,this is my first post on this board I was on the verge of binning my KJAM did a search on WM6 and now Im here
Firstly thanks to those who have contibuted to the available infomation here,,big props to you
I have learnt some lingo and read and read and am feeling a bit overloaded and looking for clarity please, I am on my 4th KJAM within my contract (many problems) my current one seems to work great apart from terrible reception in fact I dont even use it as a phone anymore but am now under the impresion that its all about software
my phone works with any sim on any network but I will run the unlock anyways my numbers are:
ipl 2.16.0001
spl2.16.0001
gsm02.37.11
os2.16.9.1
I realise there is old and new info on this site so please point me as I understand this is the procedue I will rather upgrade from my xp desktop than my vista laptop
1.hard spl I see there are current versions but not sure for kjam?
2. wm6.1 Is there a current short list for the spl?
3. radio: I will try a few that comply with the ROM but would like to know is this a separate install ?an upgrade here could have improved my last two years dramaticly
my warranty is long gone so I may as well have some fun
thanks for any advice or info should I need to learn anything more before I go in.
Tks
1.hard spl I see there are current versions but not sure for kjam?
Click to expand...
Click to collapse
HardSPL is safe for your KJam.
2. wm6.1 Is there a current short list for the spl?
Click to expand...
Click to collapse
? I don't think this is something you want to tangle with. Look at your IPL/SPL...they both end in .0001, which means you have a G4 unit. Flash an IPL or SPL other than the service provider's ROM, and you'll be on KJam #5 in no time flat.
3. radio: I will try a few that comply with the ROM but would like to know is this a separate install ?
Click to expand...
Click to collapse
You can flash a radio ROM separately. Just make sure you CID Unlock your phone first (HardSPL), or, again...brick.
Read the Wizard Wiki.
Read the HardSPL thread.
Learn to back up your personal info with Dotfred's PIM Backup program (a MUST have!).
All ROMs have their problems, just read the entire thread and decide if the problems of the ROM are things you can deal with, or things people have found fixes for.
Flashing a Radio Rom doesn't need a device to be CID unlocked or HardSPL applied,its void of any IPL/SPL in it,it has its own protocols (GSM) only and don't flash any IPL/SPL to effect the device Bootloaders.
I may as well do the rom and radio upgrade all together can I use shelltool and go for the tnt rom?
Shelltool is an old method and creats problem,now there's more stable and confirmed method 'HardSPL',go for this.

Newbie needs help with updating T-Mobile MDA Touch plus (aka HTC Touch Dual)

Hi @ all,
after reading many and many threads here in this forum (and even others) I thought I gathered enough information for starting with update my T-Mobile MDA. The original image shows the following versions:
ROM-Version: 1.35.111.13
ROM-Date: 03/14/08
Radio-Version: 1.58.21.24
Protocol-Version: 25.65.30.04H
I saw that HTC offers an official WM6.1 build for this device and since I'm running WM6.0 with many obvious bugs (and slowlyness) I decided it can't get worst.
Fortunately I found the download-link here in this forum for the official WM6.1 Professional build in german, because HTC denies access telling me that this build can't be installed on a foreign (OEM) device. After downloading the image from the link I've found here I started the updater. But even this updater refused attempts telling me that the VendorID is wrong.
As stated before I read and read and read before trying the update - but it went wrong finally. By using uSSPL 1.16 I started the update process with the original HTC updater. Everything went fine until 15% then the updater again quotes that my device has a wrong VendorID. From that moment on I saw only the rainbowscreen telling me the following:
(Top right corner: RUUNBH)
NIKI200
SPL-1.18.0000
CPLD-4
I assume that the SPL on my device is guilty of deciding which firmware to install. Luckily I found a way of still booting my device using MTTY 1.42 and sending "boot" as command. Then it booted - but I have to do that right now every time I boot up the device - it doesn't bootup by itself :-(
Here's my first question: How can I achieve that the device boots up completely and automatically again without sending a "boot" command?
I certainly still want to upgrade to ANY better OS than the current one - it just sucks! So, here're my further questions and I know there are many, many threads here and I think that read all of them according to this, but I'm still confused:
Q: What do I need as prequisites for updating this T-Mobile branded device with the official HTC Image? I'm sure SPL 1.15 and 1.16 are "too old"(??) for dealing with this brand new release firmware, right? Maybe that was the cause why the update failed.
Q: Is it necessary to install a hardSPL before starting the update? I would prefer NOT to modify the hardSPL because if I brick the device totally, I lose warranty - I just want to prevent that! If anyone tells me here, that there's really no risk of flashing hardSPL and that this certainly will work (due to his/her own experience) then I sure would proceed. BTW: I'm a newbie to this forum here and by dealing with consumer PDAs and flashing them in general, but I'm working for a company who's manufacturing such devices for the industry in rugged environments as technical supporter/consultant therefore the basics an beyonds are clear to me - only this specific field is new.
Final question: According to my questions above, a structured list (Step-By-Step) of what is necessary to do to "convince" this T-Mobile device of loading foreign Firmware is highly appreciated!
Thanks in advance for your support!
Reingucker
If you can actually get in with the boot command from mtty you're in luck.
If you're getting the vendor ID error then you'll need to unlock the device (see http://forum.xda-developers.com/showthread.php?t=395945)
You don't need to install a hard spl, once you're unlocked and booted copy over the sspl file from the spl thread to your device (the device itself and not the SD) then take out your SD and run the sspl
This will then reboot the phone to bootloader and allow the rom to be flashed without a hard spl. As the new rom comes with spl 1.22 this will be installed.
WOW - thanks very much for this fast response!!
I've read the article of the link you quoted. There it is said, that I have to flash hardSPL 1.15 before proceeding. So I guess, there's no way around of modifying the device in such a manor that it would be noticed in cases of warranty repair, right?
Cheers,
Frank
hardSPL is an advisable safeguard while flashing but you can always revert to a stock SPL afterwards if you need to.
If you went to SPL 1.22 you'd need to do that anyway if you needed to return the device as T-mobile don't have a rom with that spl yet.
Dear randomelements,
THANKS VERY MUCH for your fast response and help!
FINALLY I DID IT!!!
BUT :-D one question left:
Now I've flashed the official HTC Image with WM6.1.
Is there any way of getting the T-Mobile splash screen back onto
the device? I've found the splash-screen flasher, but do you know
where to get the T-Mobile splash-image?
Thanks again very much,
Reingucker
There are some t-mob roms around for download (links are somewhere in the forum)
Using the nbh tools the splash screens can be extracted from that and repackaged.
I'll have a look when I get home tonight.
OK, great - thanks!
In the meanwhile I'm searching around for this as well. If I'm faster I'll let you know.
Since my device is "still" on hardSPL 1.15, would you recommend to upgrade to 1.22 or is that not necessary - or, better to say, what would be the advantage resp. the disadvantage?
Cheers,
Frank
Reingucker said:
OK, great - thanks!
In the meanwhile I'm searching around for this as well. If I'm faster I'll let you know.
Since my device is "still" on hardSPL 1.15, would you recommend to upgrade to 1.22 or is that not necessary - or, better to say, what would be the advantage resp. the disadvantage?
Cheers,
Frank
Click to expand...
Click to collapse
I have 1.22 for two days now an it is so fast. I think there are no disadvantages
Reingucker said:
OK, great - thanks!
In the meanwhile I'm searching around for this as well. If I'm faster I'll let you know.
Since my device is "still" on hardSPL 1.15, would you recommend to upgrade to 1.22 or is that not necessary - or, better to say, what would be the advantage resp. the disadvantage?
Cheers,
Frank
Click to expand...
Click to collapse
It's usually better to have a later SPL and everyone is saying that 1.22 makes the device run smoother.
Liquid Silver has created a 1.22 HardSPL so you might like to give that a try - I've been using it without issues:
http://forum.xda-developers.com/showpost.php?p=2778832&postcount=429
*** Request Completed ***
OK guys, especially randomelements,
I'm through! I did everything I wanted to do... Time to setup the device aknew.
Thank you very, very much!!
Hope the device works more stable now.
Have a great day!
Reingucker
Grrrrr.....
Okay, one more thing....
I tried to replace the "animated.gif" in the /windows directory.
But the file is a system file and I always get an error message
that this operation isn't allowed.
How can I replace this?
Thanks in advance,
Reingucker
You can replace it with Resco Explorer or Total Commander, because these File Explorers can overwrite system files!
*** Request Now Really Completed ***
OK, thanks for the hint....
I achieved it by changing the registry entry that links to the file...
However... learning that these two apps can do that helps certainly...
Thanks again and....
GOOD BYE for today!!
Cheers,
Reingucker
hardspl 1.6 or 1.22 is good?
hello mate
can you post a reply how excactly did you solve the above isue?
As i am havving the sane problem and cannot fix it.
Please help if you do remember how you solved this
rob
Reingucker said:
Hi @ all,
after reading many and many threads here in this forum (and even others) I thought I gathered enough information for starting with update my T-Mobile MDA. The original image shows the following versions:
ROM-Version: 1.35.111.13
ROM-Date: 03/14/08
Radio-Version: 1.58.21.24
Protocol-Version: 25.65.30.04H
I saw that HTC offers an official WM6.1 build for this device and since I'm running WM6.0 with many obvious bugs (and slowlyness) I decided it can't get worst.
Fortunately I found the download-link here in this forum for the official WM6.1 Professional build in german, because HTC denies access telling me that this build can't be installed on a foreign (OEM) device. After downloading the image from the link I've found here I started the updater. But even this updater refused attempts telling me that the VendorID is wrong.
As stated before I read and read and read before trying the update - but it went wrong finally. By using uSSPL 1.16 I started the update process with the original HTC updater. Everything went fine until 15% then the updater again quotes that my device has a wrong VendorID. From that moment on I saw only the rainbowscreen telling me the following:
(Top right corner: RUUNBH)
NIKI200
SPL-1.18.0000
CPLD-4
I assume that the SPL on my device is guilty of deciding which firmware to install. Luckily I found a way of still booting my device using MTTY 1.42 and sending "boot" as command. Then it booted - but I have to do that right now every time I boot up the device - it doesn't bootup by itself :-(
Here's my first question: How can I achieve that the device boots up completely and automatically again without sending a "boot" command?
I certainly still want to upgrade to ANY better OS than the current one - it just sucks! So, here're my further questions and I know there are many, many threads here and I think that read all of them according to this, but I'm still confused:
Q: What do I need as prequisites for updating this T-Mobile branded device with the official HTC Image? I'm sure SPL 1.15 and 1.16 are "too old"(??) for dealing with this brand new release firmware, right? Maybe that was the cause why the update failed.
Q: Is it necessary to install a hardSPL before starting the update? I would prefer NOT to modify the hardSPL because if I brick the device totally, I lose warranty - I just want to prevent that! If anyone tells me here, that there's really no risk of flashing hardSPL and that this certainly will work (due to his/her own experience) then I sure would proceed. BTW: I'm a newbie to this forum here and by dealing with consumer PDAs and flashing them in general, but I'm working for a company who's manufacturing such devices for the industry in rugged environments as technical supporter/consultant therefore the basics an beyonds are clear to me - only this specific field is new.
Final question: According to my questions above, a structured list (Step-By-Step) of what is necessary to do to "convince" this T-Mobile device of loading foreign Firmware is highly appreciated!
Thanks in advance for your support!
Reingucker
Click to expand...
Click to collapse
hello mate
can you post a reply how excactly did you solve the above isue?
As i am havving the sane problem and cannot fix it.
Please help if you do remember how you solved this
rob
You wrote you need an update from WM6.0 to WM6.1,
i think you are a german user, so if you want a original WM6.1 from T-Mobile try this <<link>>
Its the T-Mobile Update to WM6.1 including the start splash screen

Categories

Resources