Related
Hi to all, my problem is that I can't enter the bootloader. in other words I can enter it(power+navigation buttom and reset) but i only see the word Serial and v1.01, and when usb is connected I see USB v1.01 , i can't see d2s or any other information and options. I wanted to flash my rom to SD using Multi-Port/USB TTY . I did a search on this forum but no luck so if anybody can give me a hand I'll appriciate it. Ciaoz Mine is XDAII the german verwsion.
Please anybody can give me a step by step info on how to copy the original rom to SD card, I need to change language from german to english and I want to keep the original german rom just in case. Thx
Does it have to be on sd there are other way of doing it which I will be able to talk you through (I think) if you need a hand
Well I was thinking to flash it to the sd in case the phone goes dead and you're out of activesync so the only way of flahsing it will be through SD. But another way of flashing is more than appriciated so I'll be waiting for ur guide.. do u happen to know why I can't see the options in the bootloader? thanks really
1st ... I have no idea why you cant get into the bootloader. On my xda 2 after a cold reboot i just get the serial and then when in the cradle I get usb, from their I dont know what to do. I would class myself as a newbie as well but I can talk you through what I did.
Which rom is it that you want to flash?
The extended rom or the Os rom?
i'm willing to flash the OS rom and not the extended. My version is 1.03.00 Ger and I want to flash to the "Dangaard (Qtek) 1.60" or RUU16006WWE_T-mobile_NL version which is an english one although I heard some people had their phones dead while doing so. I must find a way to back my rom 1st.. Did u do the update urself??
Yes I did the update using a programme called
HimaUpgradeUt.exe
I was originally after flashing the extended rom only, but due to not fully understanding the instructions at
http://forum.xda-developers.com/viewtopic.php?t=6470&highlight=
I made a mistake and flash the Radio Stack - the OS and the extended rom as well. After this I worked out how to use HimUpgradeUt.exe to flash the extended rom only. I am guessing that if you follow the same procdure for flashing the rom and flash the OS you will get the same results.
However I haven't tried it yet. I am hoping to get the radio rom and the OS rom for O2 xda2 and try it but until them I cant confirm it. I am only guessing that it will work?
So its up to you I have successfully updated the extended rom 4 time but I just dont have the files to do it?
Where did you get you Os file from?
I already tried Multi-Port/USB TTY program , but in the instructions it says"
3. boot the machine into bootloader mode (hold the Power and directional pad , then push reset)
4. Run the rompdate utility, select the comport as "wceusb001" or something like that as the default comport." The problem is that After going into bootloader mode I launched the romupdate utility but in the com-ports I only see com1 and com2 ,there is no wceusb001!!. And where did u see the d2s that I hear about??
I've got the downloads from the forum this one http://forum.xda-developers.com/viewtopic.php?t=6214&sid=0dad85b97d280219dc51962a01a4997b and the other form here http://shop.store.yahoo.com/cellpoint/tmobilemdaii.html
It seems that we are taking cross purposes here.
Using HimaUpgradeUt.exe you can update the roms using .NBF files,
hence the way in which I updated all 3 of my roms in one go.
Radio.nbf
Ms.nbf
Exteneded Rom.nbf (can’t remember the actual name) it looks like you are using a different up loader or have different files to upload. I can only really help with advice on the process that I followed. I can provide you with the files that I had, if you want it will change your 02 format to I-Mate in English.
Does this help?
well I know we have differnet purposes but we should use the same tool I guess if we followed this link. http://forum.xda-developers.com/viewtopic.php?t=6470&highlight= and the tool is Multi-Port/USB TTY program to back up rom or extended rom. Please provide me the info to back up the rom no matter if to SD or HD. Thanks for ur time man.
I think that you can try using ositools I will find the link and then post it, but again I am still not sure how you reinstal it afterwards
whafni77 said:
Hi to all, my problem is that I can't enter the bootloader. in other words I can enter it(power+navigation buttom and reset) but i only see the word Serial and v1.01, and when usb is connected I see USB v1.01 , i can't see d2s or any other information and options. I wanted to flash my rom to SD using Multi-Port/USB TTY . I did a search on this forum but no luck so if anybody can give me a hand I'll appriciate it. Ciaoz Mine is XDAII the german verwsion.
Click to expand...
Click to collapse
I am in the same situation with you, have you solved yet?
Serial / USB V1.01
I had the same problem, and I found the cause to be a USB Hub. I found that when I plugged the cradle directly into my PC I managed to load the update without any further problems.
I hope this helps
you have to disable usb or com port in activesync, before trying to connect with mtty, or terminal program.
see http://wiki.xda-developers.com/wiki/HimalayaBootloader
lo all
i gots a prob with SpecialEditionROM v1.2
whenever i try to run this, i keep getting an error, it cant seem to connect to my MDA (Wallaby) thru usb any suggestion?
cheers
andy
Yep.
Do the upgrade via the SD card instead. If you extract the Special Rom, you will find inside it the actual rom inside names NK.NBF, Use OSImageTool to write it to your SD card. Reboot to the boot loader (Hold in the soft reset button and hit power) and it will start updating.
OS IMage tool is available on the FTP.
The problem is likely because you have a ROM installed based on the TMobile 2003SE version. That one breaks the ability to upgrade ROM via Activesync.
Yep.
Do the upgrade via the SD card instead. If you extract the Special Rom, you will find inside it the actual rom inside names NK.NBF, Use OSImageTool to write it to your SD card. Reboot to the boot loader (Hold in the soft reset button and hit power) and it will start updating.
OS IMage tool is available on the FTP.
The problem is likely because you have a ROM installed based on the TMobile 2003SE version. That one breaks the ability to upgrade ROM via Activesync.
well i managed to unlock it, paid £1 for a program off ebay, which was pretty good actually, real quick n easy
thanks for your time anyway
andy
Hello everyone!
Can someone please advice me with my problem. I stopped syncing using the sync cable for over 6 months now since it (the mini usb slot on my HTC tytn) stopped working.
My phone must've fallen the wrong way or something coz i've tried using different cables to sync with my laptop, and my laptop couldnt identify the "device" that was being attached. I originally was able to use the cable before my phone fell, so I was able to configure the bluetooth connection after things got messed up. ( I understand that initial syncing can only be done via cable?)
I was so excited to upgrade to WM6... THANK GOODNESS I decided to "VIEW README" before I install the RUU! It specifically said the upgrade should be done using the cable... please HELP!!
Is there a way to upgrade without the cable, and use the BT connection instead? If not, where can I have my phone mini USB slot fixed?
I wish I hadnt dropped my phone! I cant figure though how the USB slot could have been affected by any type of fall??
I can still charge the phone using the USB slot, so I guess its not TOTALLY damaged.
I'd really really appreciate anybopdy's help! Thank you in advance guys!!
There is no way to flash through BT, but it should be possible to have your device upgrade through the storage card.
Read the wiki for more information
It might not even be the USB port affected through the drop but the CPU itself. In that case you might not even be able to flash via SD!
CPU damage? and flashing from Storage card
I gues it could be possible that my phone CPU was damaged... but I guess the fact that I still get to sync via BT is a good sign it's still ok. But thank you so much for the idea. I actually ran across that thread about flashing from the storage card... but i think I missed the instruction on where to get the "WM6.nbh" file to rename it to " HERMIMG.nbh" .................... the only .nbh file I saw when I opened the "RUU_Hermes_DOPODASIA_WWE_3.54.707.3_6275_1.47.00.10_108_Ship.exe" with Winrar was "SPL.nmh"
When unraring the file you will find another executable called RUU_Inside.exe
Unrar that one too and you will find the image file (nbh)
Thanx Junner and every1!
WOW! I'll try that... OK... I officially love this site! I guess I'll just have to wait for my computer to finish copying the files from my phone's Storage Device... It's been copying for over 2 hours now. BT transfer seems much slower... BTW, I hope it wont matter if my phone's IPL is 1.01 | SPL: 1.04 ..........
SSPL question
regarding the SSPL instruction: according to the readme file: " *** Usage ***
For flashing ROM copy sspl-XXXX.exe (XXXX stands for short device platform name
i.e. TRIN for HTC Trinity) to your device and run it. Standart bootloader prompt should appear on screen, ..."
--- is sspl-HERM compatible with my HTC tytn?
"....check SPL version number: if it ends with ".ds" then
everything is fine...."
------ If my SPL is just 1.04, without the .ds , what should i do then?
(Re)attach usb cable and run firmware update utility.
".....In case if something goes wrong during flashing you should flash your device with ROM accepted by standard bootloader (and have another try if you wish)."
------ what does that last statement mean?
I installed an "updated" HTC Home Screen Plugin (obviously not for my phone model #) and now my phone is frozen. It will boot up but the home screen is frozen (i.e., non-responsive to any button presses). I attempted to re-flash the ROM using various ones I found for the NEON but all fail for the same reason.
Specifically, connection to ActiveSync is not possible (I connect via USB cable but ActiveSync doesn't recognize device). So what I do is put the phone in bootloader mode and then connect the USB cable. When I do this, the ROM upgrade program recognizes the phone and gets to the point where it shows the screen "Updating the ROM image on your PDA Phone.." and the phone shows a status bar at 0%. However, after a minute the computer screen says "ERROR [262]: UPDATE ERROR" and the phone is stile stuck at 0%.
My question is if there is any other way I can re-flash my NEON300? I've heard that it may be possible to but the nbh file on a FAT32 formatted card. I tried this by naming the nbh file to "TOUCHIMG.NBH" and "NEONIMG.NBH" but neither are recognized by the bootloader.
Thanks in advance for any assistance.
Try changing usb port or even re-installing activesync.
Alot pf people had the same problem on different devices but the cause should be the same.
for example, http://forum.xda-developers.com/showthread.php?t=298516
Let me know how you go.
Thanks for the advice Seth. I followed the link (install/re-install of ActiveSync didn't help) and I think I found my problem. Do I need to CID unlock the phone to install the ROM's? I ran the type 32 command from mtty and it shows a value of FF for the security lock.
Thanks
wangobyte said:
Thanks for the advice Seth. I followed the link (install/re-install of ActiveSync didn't help) and I think I found my problem. Do I need to CID unlock the phone to install the ROM's? I ran the type 32 command from mtty and it shows a value of FF for the security lock.
Thanks
Click to expand...
Click to collapse
You should have read the WIKI before flashing your device... http://wiki.xda-developers.com/index.php?pagename=Flashing Guide and here http://forum.xda-developers.com/showthread.php?t=355730
Hy!
I did a stupid thing, with the following. I copyed an LEOIMG.nbh file to my formatted sd card, so I get an SPL-1.42.0000, but I can't flash any HSPL to my device, because the HSPL setup writes out USB connection error. Neighter can I flash for example the official 1.66 rom, the installation stops after 1%, and writes INVALID VENDER ID. What can I do?
Very siple but you need lots of time for it. The rom you flashe has spl 3.03 on it and so it doesn't allow you to flash any other spl on it. What you can do is you have to search for old stock roms in the native language of your phone. As long as the phone keeps giving you error when trying to flash a stockrom with you sd card, it means you have not yet gotten the right stockrom for you phone so you have to try with different old stockroms till you get the right one.
After that. you'll be able to flash whatever you like. Hope it helps.
But remember, you need time and patience.
Abdul9. said:
Very siple but you need lots of time for it. The rom you flashe has spl 3.03 on it and so it doesn't allow you to flash any other spl on it. What you can do is you have to search for old stock roms in the native language of your phone. As long as the phone keeps giving you error when trying to flash a stockrom with you sd card, it means you have not yet gotten the right stockrom for you phone so you have to try with different old stockroms till you get the right one.
After that. you'll be able to flash whatever you like. Hope it helps.
But remember, you need time and patience.
Click to expand...
Click to collapse
Thanks, I will try it. This stockrom is 1.66?
zoldya said:
Hy!
I did a stupid thing, with the following. I copyed an LEOIMG.nbh file to my formatted sd card, so I get an SPL-1.42.0000, but I can't flash any HSPL to my device, because the HSPL setup writes out USB connection error. Neighter can I flash for example the official 1.66 rom, the installation stops after 1%, and writes INVALID VENDER ID. What can I do?
Click to expand...
Click to collapse
You can also download HSPL 4 and use it to downgrade your SPL. To do this manualy put your HD2 into bootloader by holding the volume down button and pressing the power(end) butom momentarily. Once in bootloader connect your HD2 to your computer via USB cable wait until you see USB in the white bar of thd bootloader and run the HSPL 4 on your computer. It will ask you which SPL or HSPL you wish go flash select the proper SPL version to flash to your HD2 and you should be good to go. Hint the SPL version will have zeros at the end of them and the HSPL version will not. Example SPL 2.08.0000 HSPL 2.08. Hope this helps.
T-Macgnolia said:
You can also download HSPL 4 and use it to downgrade your SPL. To do this manualy put your HD2 into bootloader by holding the volume down button and pressing the power(end) butom momentarily. Once in bootloader connect your HD2 to your computer via USB cable wait until you see USB in the white bar of thd bootloader and run the HSPL 4 on your computer. It will ask you which SPL or HSPL you wish go flash select the proper SPL version to flash to your HD2 and you should be good to go. Hint the SPL version will have zeros at the end of them and the HSPL version will not. Example SPL 2.08.0000 HSPL 2.08. Hope this helps.
Click to expand...
Click to collapse
I have tried that, but after a few minutes - when it tries connect to the device - the HSPL setup writes out an error message;
CRITICAL ERROR
Flow:00000001
Error code: 00000002
Description: USB Connect failed!
but i don't know why, because during the installationvI see USB in the white bar of the bootloader - the device manager on the notebook shows the connection too. :S
Abdul9. said:
Very siple but you need lots of time for it. The rom you flashe has spl 3.03 on it and so it doesn't allow you to flash any other spl on it. What you can do is you have to search for old stock roms in the native language of your phone. As long as the phone keeps giving you error when trying to flash a stockrom with you sd card, it means you have not yet gotten the right stockrom for you phone so you have to try with different old stockroms till you get the right one.
After that. you'll be able to flash whatever you like. Hope it helps.
But remember, you need time and patience.
Click to expand...
Click to collapse
I just finished with the 1.66 OSPL roms http://http://forum.xda-developers.com/showthread.php?t=623283 but the problem was the same with each one. Should I try the 3.14 rom-s too?
zoldya said:
I just finished with the 1.66 OSPL roms http://http://forum.xda-developers.com/showthread.php?t=623283 but the problem was the same with each one. Should I try the 3.14 rom-s too?
Click to expand...
Click to collapse
Have you tried to restart your PC and or change another USB port of your PC?
zoldya said:
I have tried that, but after a few minutes - when it tries connect to the device - the HSPL setup writes out an error message;
CRITICAL ERROR
Flow:00000001
Error code: 00000002
Description: USB Connect failed!
but i don't know why, because during the installationvI see USB in the white bar of the bootloader - the device manager on the notebook shows the connection too. :S
Click to expand...
Click to collapse
Try the above post by silverwind and try another USB port, another computer, and another cable if you have too. Something just does not sound right about this. I am looking at this.
CRITICAL ERROR
Flow:00000001
Error code: 00000002
Description: USB Connect failed!
Click to expand...
Click to collapse
Just keep trying man I think you might just have a simple problem here.
Heck reset your notbook if you think it might help.
I have tried that too, and didn't solve the problem... :'(
Do you think that GoldCard method would help?
Hi. I have the same pronblem. I have a UK HD2 that was originally on Tmobile. I flashed 2.08HSPL using HSPL4 & upgraded the ROM to the standard WWE_3.14. A long story short... after playing around with SD Android & a few other utilities I wanted to make a clean start, so my plan was to use HSPL4 to remove the HSPL before then re-installing it & reflashing the ROM. Unfortunately I now seem to be stuck in SPL2.08.0000. HSPL4 just gives the same error:
CRITICAL ERROR
Flow:00000001
Error code: 00000002
Description: USB Connect failed!
I have also tried flashing a stock ROM via SD (renamed leoimg.nbh), but I can't get passed the bootloader displaying 'serial'.
Any ideas?
Chameleon846 said:
Hi. I have the same pronblem. I have a UK HD2 that was originally on Tmobile. I flashed 2.08HSPL using HSPL4 & upgraded the ROM to the standard WWE_3.14. A long story short... after playing around with SD Android & a few other utilities I wanted to make a clean start, so my plan was to use HSPL4 to remove the HSPL before then re-installing it & reflashing the ROM. Unfortunately I now seem to be stuck in SPL2.08.0000. HSPL4 just gives the same error:
CRITICAL ERROR
Flow:00000001
Error code: 00000002
Description: USB Connect failed!
I have also tried flashing a stock ROM via SD (renamed leoimg.nbh), but I can't get passed the bootloader displaying 'serial'.
Any ideas?
Click to expand...
Click to collapse
Did you place the leoimg.nbh on the root of your SD card? Also was tbe dile you renamed originaly named RUU_signed.nbh?
T-Macgnolia said:
Did you place the leoimg.nbh on the root of your SD card? Also was tbe dile you renamed originaly named RUU_signed.nbh?
Click to expand...
Click to collapse
Yes on both counts... I've even tried a complete 'long' reformat of the SD card first using the Panasonic SD Formatter, before putting the leoimg.nbh at the root.
I'm guessing that my stupid mistake is downgrading to SPL2.08.0000 whilst having a generic version of the 3.14 ROM installed. I guess I should have downgraded the ROM to an original Tmobile one first...
Could i ask what operating system you guys are using cos this problem could have less to do with the phone than it has to do with the operating system on the pc. I was trying to flash some roms on some old devices using Windows 7 but this didn't seem to work but it magically worked when i used Windows xp. I hope this works.
About the wrong Vendor problem, this just means the rom flashed is not recognized by the phone as the official one, i also had that problem and after flashing a official rom in the language of my phone, the problem was solved. I used the 1.66 rom so that i could flash hspl or else it might be impossible to do so.
Or as someone suggested you might try the hspl4 (never knew that existed) but try using Windows xp and if the problem persists try reinstalling your operating system (on your pc). I know it a lot of work but its just to rule out that the problem is from the pc.
Another thing i want to make sure of is if the phone is working normally with the rom on it or is there no rom at all?
Abdul9. said:
Could i ask what operating system you guys are using cos this problem could have less to do with the phone than it has to do with the operating system on the pc. I was trying to flash some roms on some old devices using Windows 7 but this didn't seem to work but it magically worked when i used Windows xp. I hope this works.
About the wrong Vendor problem, this just means the rom flashed is not recognized by the phone as the official one, i also had that problem and after flashing a official rom in the language of my phone, the problem was solved. I used the 1.66 rom so that i could flash hspl or else it might be impossible to do so.
Or as someone suggested you might try the hspl4 (never knew that existed) but try using Windows xp and if the problem persists try reinstalling your operating system (on your pc). I know it a lot of work but its just to rule out that the problem is from the pc.
Another thing i want to make sure of is if the phone is working normally with the rom on it or is there no rom at all?
Click to expand...
Click to collapse
Hi. Thanks for the input. The problem is getting even more frustrating! I've tried buying a new 4GB micro SD card (both are class 4). I have tried both TMO_UK_1.72 & TMO_UK_1.43. Both ROMs were downloaded from HTC using the correct phone's serial, so they should be the correct ones.
With the original SD card I can't get passed the bootloader screen & it just stays in 'serial' mode. With the new SD card it moves on to 'loading...', but then just hangs. I haven't yet seen the word 'searching' as described in the [TUT] Flash your ROM / Radio via microSD.
To clarify, the phone boots fine with the installed 3.14 ROM, but I can't get away from SPL 2.08.0000 or flash any other ROM.
Chameleon846 said:
Hi. Thanks for the input. The problem is getting even more frustrating! I've tried buying a new 4GB micro SD card (both are class 4). I have tried both TMO_UK_1.72 & TMO_UK_1.43. Both ROMs were downloaded from HTC using the correct phone's serial, so they should be the correct ones.
With the original SD card I can't get passed the bootloader screen & it just stays in 'serial' mode. With the new SD card it moves on to 'loading...', but then just hangs. I haven't yet seen the word 'searching' as described in the [TUT] Flash your ROM / Radio via microSD.
To clarify, the phone boots fine with the installed 3.14 ROM, but I can't get away from SPL 2.08.0000 or flash any other ROM.
Click to expand...
Click to collapse
Ok here is a couple of options for you. One go to www.t-mobile.com if you have a T-Mobile HD2 and type HTC HD2 upgrade in the search box on the home screen of the website and you will find the official T-Mobile 3.14 ROM. You will have to enter your IMEI number under your battery to download it. Download this ROM and then follow the steps to flash it via SD card, hint you will have to rename the original .exe file to .zip to gain access to the .nbh file. Also you can download and run HSPL 4 on your HD2 and select SPL 3.03.0000 but the official ROM will change it to SPL 3.10.0000 if you flash via SD card
Its a common problem i think if you are trying to flash a rom via sd card with a sd card higher than class two. Many here have encountered such problems.
According to your description, it will seem that it is as i suspected, the pc doesn't seem to recognize the phone and this could mean you have a defect usb cable or the useport itself is not funtioning properly. Try holding the phone in your hand with the usb in and support the usb with your hand to make sure the usb is indeed in the phone and see what happens. My usb cable is a little bit loose so when i want to flash anything, i use my hand to support it or i place my phone on a smoot surface and make sure the usb cable is in it.
zoldya said:
Hy!
I did a stupid thing, with the following. I copyed an LEOIMG.nbh file to my formatted sd card, so I get an SPL-1.42.0000, but I can't flash any HSPL to my device, because the HSPL setup writes out USB connection error. Neighter can I flash for example the official 1.66 rom, the installation stops after 1%, and writes INVALID VENDER ID. What can I do?
Click to expand...
Click to collapse
Chameleon846 said:
Hi. I have the same pronblem. I have a UK HD2 that was originally on Tmobile. I flashed 2.08HSPL using HSPL4 & upgraded the ROM to the standard WWE_3.14. A long story short... after playing around with SD Android & a few other utilities I wanted to make a clean start, so my plan was to use HSPL4 to remove the HSPL before then re-installing it & reflashing the ROM. Unfortunately I now seem to be stuck in SPL2.08.0000. HSPL4 just gives the same error:
CRITICAL ERROR
Flow:00000001
Error code: 00000002
Description: USB Connect failed!
I have also tried flashing a stock ROM via SD (renamed leoimg.nbh), but I can't get passed the bootloader displaying 'serial'.
Any ideas?
Click to expand...
Click to collapse
Ok do to some recent personal experience and some other members problem of late. I suggest both of you do this go to www.windowsmobile.com/getstarted and download the most recent version of WMDC wich has updated drivers in it that seems to solve somd problems with flashing via USB especially if you are using a 64 bit system. Just so both of you know unless your HD2 shows up as "HTC USB Sync" in the device manager while connected via USB while in bootlaoder you do not have the correct drivers installed and any flash will fail.
T-Macgnolia & Abdul9: Thanks for that, however mine is a UK Tmobile HD2 & the .com site is only for US ones (it doesn't recognise UK IMEI's). If I go via the UK site it just links me to the HTC update site for the RUU_Leo_S_TMO_UK_3.14.110.1_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship (& also the 1.72 & 1.43 versions. I have tried all of these via both SD card & via USB. I have also tried HSPL4, HSPL3 & HSPL2. All options have failed. I have tried from Win XP Pro & Win 7 Ultimate (both 32bit) with two different USB leads. I have also tried a 3rd SD card (which ends up stalling at the 'loading' screen. The phone flashed fine prior to removing 2.08HSPL with HSPL4.
I think that the problem is not the SD card or the USB lead, but is the problem that I've now got a Tmobile (UK) phone with spl 2.08 & a WWE_3.14 ROM installed - this should obviously not normally be possible. I can't flash back to HSPL & I can't downgrade to any other ROM.
Does anyone have any idea how I can 'fool' the phone into letting me change the ROM?
I've been reading about Task29, but it says don't do this unless you have HSPL (which I can't get!). I don't want to brick the phone (because it still runs!), but I want HSPL back otherwise I can't reinstall Android on SD.
Furthermore, I don't think this is a USB driver issue, as it flashed fine before & it's occurring across different PC's & operating systems.
It's an incompatibility between a branded Tmobile with SPL & a WWE HTC ROM... I just need to get out of the loop I'm stuck in!
Hey Chameleon I know you don't think it is a problem with the drivers cause it was flashing fine before. But what I do not think you have taken into account is that you came from a older ROM and you had the right drivers to work with that ROM or the update for that ROM. But you now have a 3.14 ROM and this is a newer ROM that probably requires different drivers. I mean Microsoft did not create a new WMDC with updated drivers if it was not needed for the 3.14 ROMs as they are the most recent official ROM versions. Microsoft is the one that comes out with the new ROM versions too, the carriers just add their bloatware to them. Do you see my train of thought here? Also make sure you are usinv SD card that is 500MBPS to 8GB that is formated with Fat 32.
T-Macgnolia said:
Hey Chameleon I know you don't think it is a problem with the drivers cause it was flashing fine before. But what I do not think you have taken into account is that you came from a older ROM and you had the right drivers to work with that ROM or the update for that ROM. But you now have a 3.14 ROM and this is a newer ROM that probably requires different drivers. I mean Microsoft did not create a new WMDC with updated drivers if it was not needed for the 3.14 ROMs as they are the most recent official ROM versions. Microsoft is the one that comes out with the new ROM versions too, the carriers just add their bloatware to them. Do you see my train of thought here? Also make sure you are usinv SD card that is 500MBPS to 8GB that is formated with Fat 32.
Click to expand...
Click to collapse
WOW! I've got the problem sorted! This can't be a coincidence... I haven't done anything different to my PC, but I got an 'unlock' code through for my phone this morning (£5.99 on Ebay) & it worked fine. I though "why not" & tried HSPL4 again. With no other changes it worked absolutely fine this time & I now have 2.08HSPL installed.
Presumably by unlocking my my phone from Tmobile it has also removed the 'you're using the incorrect ROM' problem.
Thanks for everyones input on this. I maintain that XDA-Developers is one of the best Forums around (not just within the mobile phone arena).