Button ROM wont execute after load

[licensedtoquill]

I have just got this Wizard and am having difficulties getting past the first screen: I Have unlocked before and should know the answer to this question. But the annoying thing is that the ugraders do upgrade to 100% and go to FINISH.

The unit then boots to the initial beer mug screen, the red markings appear and the whole unit stops. It is showing an IPL of 1.01 (which I have never heard of before), an SPL of 2.26, a GSM of 01.12.10 and now an OS of 1.5.4.2. No amount of soft booting will get me past this screen and all I can do else is to upgrade to some different ROM and it loads fully and then wont get past THAT splash screen, when it wont of course activate ActiveSync because presumably the ROM OS isnt loading past the splash screen.

I can of course get to the three coloured screen and try again and this result repeats itself.

[licensedtoquill]

I should add that PDA Update Utility 2.00.1 gives an error message 300, 'get newer update utility' which seems to make no sense as this is 3.08

[zabardast_1]

I have just got this Wizard and am having difficulties getting past the first screen: I Have unlocked before and should know the answer to this question. But the annoying thing is that the ugraders do upgrade to 100% and go to FINISH.

The unit then boots to the initial beer mug screen, the red markings appear and the whole unit stops. It is showing an IPL of 1.01 (which I have never heard of before), an SPL of 2.26, a GSM of 01.12.10 and now an OS of 1.5.4.2. No amount of soft booting will get me past this screen and all I can do else is to upgrade to some different ROM and it loads fully and then wont get past THAT splash screen, when it wont of course activate ActiveSync because presumably the ROM OS isnt loading past the splash screen.

I can of course get to the three coloured screen and try again and this result repeats itself.

What was the ipl/spl...? before you flashed button's rom 1.05 ? and which carrier's Rom was loaded ?
you got ipl 1.01 due to flashing button's rom but your spl remained 2.26,try to flash button's rom a couple of times more,sometimes it takes a lot more than one flash to load up button's rom,or try a hard reset.
secondly,download official carrier's rom and as you say you can get into bootloaders,flash it.

Disconnect your phone from the usb cable,disable any Firewall and Anti virus and reboot your Pc.

1. Make sure your phone is not Connected to the PC and remove the dummy card or SD/MMC card

2. On your Desktop PC, open Microsoft ActiveSync, then go to File >Connection Settings >Remove the Selection from “Allow USB Connection with this desktop computer”

3. Reconnect your phone to the Desktop PC using the USB Cradle and the Charger MUST be Connected to the Cradle (Don’t Bluetooth for the Upgrade)

4. When you see usb appear at the bottom of bootloader screen

5. Run the Upgrade again and it will work fine without any problems.


While upgrading, the ActiveSync program will not go on, however the upgrade is running.

What do you mean by 'I should add that PDA Update Utility 2.00.1 gives an error message 300, 'get newer update utility' which seems to make no sense as this is 3.08',did you upgraded to ipl/spl 3.08 before flashing button's rom 1.05 ?
good luck

[licensedtoquill]

OK I will follow your instructions: Just a few points. Firstly I didnt realise that when it says Button's ROM has loaded properly, you might still have to try loading it again a few times.

Secondly I did try loading the manufacturer's ROM and it gave the same result: Loaded fully, went to FINISH. After 100%, wouldn't get past initial splash screen on reset.

Thirdly the reason I was doing the upgrade which failed with that error message was because I just didn't recognise the IPL of 1.anything. So as I had heard that the SPL/IPL was some type of bootloader, I thought that the reason it wouldnt in effect boot was because I was trying to load an advanced ROM with a dinosaur boot loader. So I was trying to load IPL/SPL 3.08 to try the ROM flash again. This seems to have been a red herring. I am reasonably sure that the IPL/SPLs were the same as they are at present before I loaded Button's ROM

Lastly I can do all of this with a vanilla computer I have lying around somewhere onto which I can load ActiveSync 4.5 so I will try that.

[licensedtoquill]

Here's where I am stuck now: Reloading button ROM numerous times did nothing. Same problem. Gets stuck at splash screen. Tried loading T-Mobile ROM. Went successfully to 100% then prompted to FINISH. Same problem. Gets stuck at splash screen. All soft reboots result in same. Holding down all three buttons while pressing the power button seems to result in a black screen with "Press SEND to restore factory defaults, Other keys to quit" Pressing SEND (I presume they mean CALL?) gives a very quick report something like 'Formating FAT32 partition Formatting failed' followed by t-mobile splash screen for a few seconds and then IPL 2.26 SPL 2.26 GSM 02.25.11 and OS 2.26.10.2, so that flash did take successfully and then the screen hangs!

Then I noticed that Vippie tells you that you have to re-run lokiwiz after flashing the Button ROM, which raises the question: how do you do that after Button hasnt actually run it's course after the successful flash? (besides this, which unlock do you run? There seem to be about four options. So presumably you have to assume it is the full CID unlock)

Then I ran the Button again and of course it completed (this time going red at a more normal 98% rather than the 85% as last time, flashing blue quickly and then going red again before going to 100% at red and then turning blue again) and of course it then gets stuck at splash screen as soon as the red info crops up. But as I had received a successful flash report, I re-booted, ran Lokiwiz again and tried to CID unlock again. Naturally lokiwiz gets stuck at the unlock DOS screen when trying to unlock with the Button splash screen stuck on the Wizard (which is a bit Vippie doesnt tell you on his instructions page).

So I Controlled-C to stop the non-running lokiwiz and tried Wizard_Love ROM from the tri-coloured screen, with the IPL of 1.01 and an SPL of 2.26 just to show me that the most recent flash had worked: Which returned the (italian) error 300 message, old utility and of course no activity on the Wizard.

With the tri-coloured screen, plugging the Wizard in again and seeing the USB appear on the Wizard to make sure the computer sees the device, I ran lokiwiz again and saw no activity on the device, just an inactive tri-coloured screen along with a (after about an hour of this) non-working CID unlock program.

Does anyone have any idea what could be causing any or all of this or are these symptoms a bit egregious/

[zabardast_1]

Here's where I am stuck now: Reloading button ROM numerous times did nothing. Same problem. Gets stuck at splash screen. Tried loading T-Mobile ROM. Went successfully to 100% then prompted to FINISH. Same problem. Gets stuck at splash screen. All soft reboots result in same. Holding down all three buttons while pressing the power button seems to result in a black screen with "Press SEND to restore factory defaults, Other keys to quit" Pressing SEND (I presume they mean CALL?) gives a very quick report something like 'Formating FAT32 partition Formatting failed' followed by t-mobile splash screen for a few seconds and then IPL 2.26 SPL 2.26 GSM 02.25.11 and OS 2.26.10.2, so that flash did take successfully and then the screen hangs!

Then I noticed that Vippie tells you that you have to re-run lokiwiz after flashing the Button ROM, which raises the question: how do you do that after Button hasnt actually run it's course after the successful flash? (besides this, which unlock do you run? There seem to be about four options. So presumably you have to assume it is the full CID unlock)

Then I ran the Button again and of course it completed (this time going red at a more normal 98% rather than the 85% as last time, flashing blue quickly and then going red again before going to 100% at red and then turning blue again) and of course it then gets stuck at splash screen as soon as the red info crops up. But as I had received a successful flash report, I re-booted, ran Lokiwiz again and tried to CID unlock again. Naturally lokiwiz gets stuck at the unlock DOS screen when trying to unlock with the Button splash screen stuck on the Wizard (which is a bit Vippie doesnt tell you on his instructions page).

So I Controlled-C to stop the non-running lokiwiz and tried Wizard_Love ROM from the tri-coloured screen, with the IPL of 1.01 and an SPL of 2.26 just to show me that the most recent flash had worked: Which returned the (italian) error 300 message, old utility and of course no activity on the Wizard.

With the tri-coloured screen, plugging the Wizard in again and seeing the USB appear on the Wizard to make sure the computer sees the device, I ran lokiwiz again and saw no activity on the device, just an inactive tri-coloured screen along with a (after about an hour of this) non-working CID unlock program.

Does anyone have any idea what could be causing any or all of this or are these symptoms a bit egregious/


First of all,let me advise you that lokiwiz02b tool never works in bootloader mode (tri color screen),to work it has to have a working OS on your phone,therefore using lokiwiz again and again will not work and is of no use,untill and unless your able to flash button's rom 1.05 successfully and it loads up correctly and the phone is in working condition,also downgrading to IPL/SPL 1.xx,lokiwiz will not operate.

Vippe said to rerun the lokiwiz in this sense that if you ever again downgrade to IPL/SPL 1.xx by flashing button's rom.as if you have upgraded to a wm6 Rom with ipl/spl 2.xx or 3.xx and you flash back again button's rom 1.05,than only to rerun the lokiwiz.but if you are able to flash button's rom 1.05 and load up sucessfully to OS and get the device unlocked,than there's no need to go back to ipl/spl 1.05 as your phone will be permanently unlocked.

regarding Error 'Formating FAT32 partition Formatting failed'
well to my understanding and knowledge,it does not pertain to any Rom flashing errors,it's mostly related to sdcard/mini-sd problems,Are you having any sdcard/mini-sd card in your phone,then remove it before flashing cuz it has been seen that sdcard/mini-sd card create problems while flashing.If the sdcard/mini-sd card requires format,it usually get splash screen stuck up or won't let bootloader mode stuck.

So, try to flash button's rom a couple of more times or as sometimes it gives problems then download and try xda_minis_Launch Rom :- http://rapidshare.com/files/43423464/Xda_MiniS_LaunchROM_v154102.exe

and the third option is of course try to flash the official carrier's rom,good luck

[licensedtoquill]

Many thanks for the note: To restate the problem, no ROM I flash can get me past the initial splash screen and I am not using any SD card at all.

Every ROM flashes successfully. It always then gives me it's SPL/IPL report on the initial splash screen but none of them get past that first splash screen. All they do is to load the splash screen (whether it is the beer mug or the T-Mobile one) and then tell me what versions I am running in red and then all stop.

Actually I thought that there wasnt much point in re-running the unlock program of whatever type if it was unlocked already but that was how I interpreted Vippie's advice if you had somehow got back to a 1.xx IPL. Now I see that was incorrect. I have tried so many times to reflash Button ROM and seen it complete fully and even close the utility that I am beginning to wonder whether it IS worthwhile trying numerous times again. So I will now try to flash the http://rapidshare.com/files/43423464/Xda_MiniS_LaunchROM_v154102.exe as you suggest.

By the way, I don't ever seem to be able to get the computer to see the device so as to flash it when any OS is loaded (obviously because none of them load after the soft resets after their flashes). it SEEMS to me that I can only get ROMs to re-flash from the three colour screen? But even trying to get a stable T-Mobile ROM onto the machine seems to work this way and as I say usually completes to 'FINISH' and then doesn't get me past the splash screen again. Curiously this device doesn't seem to mind being flashed in tri-colour mode!!

In first splash screen mode with the Button beer mug showing, and with the red text showing an IPL of 1.01,, an SPL of 2.26, GSM or 01.12.10 and an OS of 1.5.4.2 all I get now when I try to flash the T-Mobile ROM is an error 274 or error 260 telling me that although I can see the green light lit on the Wizard telling me that the device IS connected to the computer and the battery IS fully charged, there is no connection between the computer and the Wizard! Actually flashing Xda_MiniS_LaunchROM_v154102 now does the same thing: I should try rebooting and possibly [grasping at straws here] moving the flash directory from the desktop to the root of C:

[licensedtoquill]

Just to update this, I did flash the mini-ROM Xda_MiniS_LaunchROM_v154102 and it did complete successfully from the tricolour screen (going red at 85% and then at 98% as well) and then completing and closing the utility

And now stops yet again at the Button beer mug after reading the parameters (which are the same)

[licensedtoquill]

I have now flashed the manufacturers ROM and it took successfully from the tricolour screen and the unit now boots to the T-Mobile initial splash screen where it yet again stops completely after telling me that it is now at spl/ipl 2.26

[lou2ser]

I have just got this Wizard and am having difficulties getting past the first screen: I Have unlocked before and should know the answer to this question. But the annoying thing is that the ugraders do upgrade to 100% and go to FINISH.

The unit then boots to the initial beer mug screen, the red markings appear and the whole unit stops. It is showing an IPL of 1.01 (which I have never heard of before), an SPL of 2.26, a GSM of 01.12.10 and now an OS of 1.5.4.2. No amount of soft booting will get me past this screen and all I can do else is to upgrade to some different ROM and it loads fully and then wont get past THAT splash screen, when it wont of course activate ActiveSync because presumably the ROM OS isnt loading past the splash screen.

I can of course get to the three coloured screen and try again and this result repeats itself.


The issues began right after a ROM downgrade from IPL/SPL 2.25.001 using the button 1.05 ROM. After 100% complete the phone got stuck on the beer mug. I waited 5-10 minutes before doing a soft reboot. Now the phone won't turn on it all.

No LEDS when charging via USB, no activity on the PC. When I pull the battery I get an amber LED and a white screen for a fraction of a second. I think this is just the screen and LED discharging.

I thought it may be a battery issue even though the batter was at 90% before the firmware upgrade. I tried jumping the battery by wiring a 9 volt to the + and - ports on the HTC battery for between 1 and 5 seconds without any luck. I do not have a multimeter to verify, but I think the battery is good. I tried swapping my battery with a co-workers. His phone turned on, mine did not.

At this point I'm pretty sure I bricked it but want to confirm before I move on to my next toy.

Thanks!

[licensedtoquill]

I'm having similar issues. I got to the beer mug screen and waited 5-10 minutes before doing a soft reset. Now I can't even get the phone to power on. No LEDS when charging via USB, no activity on the PC. When I pull the battery I get an amber LED and a white screen for a fraction of a second.

Any ideas?

EDIT: I've done some reading and it looks like it may be a dead battery. I'll try jumping it tonight and will report back.

At the moment the Consumer Product Safety Commission is looking into the general question of battery malfunction on these Wizards: T-Mobile seem to know all about it as they have instructions to try to sell customers new units when problems with batteries or battery overheating are reported; if customers don't respond positively, they are instructed to read endless scripts to you and keep you on the phone for as long as possible and hope that sooner or later you will go away.

Did yours overheat before dying? Some element of reseting the device may be called for: I found that with a working unit I have, (not the one with the frozen screen problem) if you simply put another charged battery in it, the Wizard may spring to life. But don't expect T-Mobile to assist you with this, they are in denial about this problem. One suspects Cingular may react the same way, I have never had any experience with them.

Nevertheless this does appear to be a real problem here judging by the number of page views and the lack of suggestions by any moderators?

[zabardast_1]

I'm having similar issues. I got to the beer mug screen and waited 5-10 minutes before doing a soft reset. Now I can't even get the phone to power on. No LEDS when charging via USB, no activity on the PC. When I pull the battery I get an amber LED and a white screen for a fraction of a second.

Any ideas?

EDIT: I've done some reading and it looks like it may be a dead battery. I'll try jumping it tonight and will report back.

what is the data of your phone like IPL/SPL...?,is it a G3 or G4 device,if it's a G3 then it might be your battery problem,either you did not had a full charged battery when you flashed the Rom or may be it's a faulty battery,but did have any previous problems of this battery,before in normal working or before you flashed ?

secondly the most important,If you have G4 device and you flashed a G3 Rom with IPL/SPL 1.05,well....... man you got a Bricked Phone.

[licensedtoquill]

No, read the thread: But I may have a bricked device and not know it. No one has suggested this yet. The device cannot be seen by the computer. If I go to the bootloader screen and then connect the USB cable, I can flash the ROM successfully.

Nobody seems to know why this should be. This flashing changes the splash screen, ROM and the SPL/IPL.

But I can never get past the first splash screen. After the red data is displayed, the unit freezes. Although I always do this with a fully charged battery, lately the unit doesn't seem to want to charge itself.

Can you still flash your device?

[zabardast_1]

No, read the thread: But I may have a bricked device and not know it. No one has suggested this yet. The device cannot be seen by the computer. If I go to the bootloader screen and then connect the USB cable, I can flash the ROM successfully.

Nobody seems to know why this should be. This flashing changes the splash screen, ROM and the SPL/IPL.

But I can never get past the first splash screen. After the red data is displayed, the unit freezes. Although I always do this with a fully charged battery, lately the unit doesn't seem to want to charge itself.

Can you still flash your device?

As long as your phone gets into bootloaders(tri color screen),it's not 'Bricked',be rest assured of this,ok :)
Secondly until and unless you have working OS on your phone,it'll not be recognized by the computer,as it cannot establish connectivity through Activesync.Activesync will only detect your phone in a normal working status,so in present status,your phone doesn't bootup normally into working OS and it only goes into bootloaders,it will never be detected by the Activesync and thus your computer.
The only test to verify the connectivity of your phone with computer at present is that when you attach your phone with the USB cable to the PC and there appears small usb at the bottom of the bootloader screen,that means your phone has established connectivity with PC.
It's a 'catch 22' situation,where your bootloaders are not accepting any Rom flash and the only way is to get your phone start working normal and unlock it ,for that it's required to downgrade to ipl/spl 1.xx,or the other option is to flash the official rom to bring it back to it's default status and then try to downgrade to ipl/spl 1.xx and unlock it.
Well,as you say it's not charging that cud be a major hindrance in flashing,cuz it's recommended to have atleast 70% charged battery before starting any flash,if it does not retain charge during a flash and does not have enough juice left to complete the flash then the flash will not complete,it's a bad flash and phone usually stuck up at the bootloader screen,this cud also be the problem ,you are not getting a full proper flash.
Try to fully charge your battery and then try to flash,if it's not charging,than check your charger or the usb plug of the charger,it might not be having a good connection with the mini usb port of your phone,wiggle it a bit and see if it starts to charge,secondly,it cud also be the mini usb port of your phone which might be malfunctioning,anyway verify and rectify the problem.if it's the usb plug of the charger,get a new charger,but if it's the mini usb port,than I'm afraid you'll have to get it repaired or replaced,
good luck :)

[lou2ser]

what is the data of your phone like IPL/SPL...?,is it a G3 or G4 device,if it's a G3 then it might be your battery problem,either you did not had a full charged battery when you flashed the Rom or may be it's a faulty battery,but did have any previous problems of this battery,before in normal working or before you flashed ?

secondly the most important,If you have G4 device and you flashed a G3 Rom with IPL/SPL 1.05,well....... man you got a Bricked Phone.

Here's my updated post:

The issues began right after a ROM downgrade from IPL/SPL 2.25.001 using the button 1.05 ROM. After 100% complete the phone got stuck on the beer mug. I waited 5-10 minutes before doing a soft reboot. Now the phone won't turn on it all.

No LEDS when charging via USB, no activity on the PC. When I pull the battery I get an amber LED and a white screen for a fraction of a second. I think this is just the screen and LED discharging.

I thought it may be a battery issue even though the batter was at 90% before the firmware upgrade. I tried jumping the battery by wiring a 9 volt to the + and - ports on the HTC battery for between 1 and 5 seconds without any luck. I do not have a multimeter to verify, but I think the battery is good. I tried swapping my battery with a co-workers. His phone turned on, mine did not.

At this point I'm pretty sure I bricked it but want to confirm before I move on to my next toy.

Thanks!

[zabardast_1]

Here's my updated post:

The issues began right after a ROM downgrade from IPL/SPL 2.25.001 using the button 1.05 ROM. After 100% complete the phone got stuck on the beer mug. I waited 5-10 minutes before doing a soft reboot. Now the phone won't turn on it all.

No LEDS when charging via USB, no activity on the PC. When I pull the battery I get an amber LED and a white screen for a fraction of a second. I think this is just the screen and LED discharging.

I thought it may be a battery issue even though the batter was at 90% before the firmware upgrade. I tried jumping the battery by wiring a 9 volt to the + and - ports on the HTC battery for between 1 and 5 seconds without any luck. I do not have a multimeter to verify, but I think the battery is good. I tried swapping my battery with a co-workers. His phone turned on, mine did not.

At this point I'm pretty sure I bricked it but want to confirm before I move on to my next toy.

Thanks!

hmmm,are you sure it's IPL/SPL 2.25.001 (two '0') and not 2.25.0001(three'0') ?
well if it's 2.25.001,it'a G3 device and I find no reason that it cud brick like this,but if it has 2.25.0001,than it's a G4 device,than it's pretty well known that by flashing a G3 Rom will definitely Brick it.

secondly,First fully charge the battery,somehow,even you can do this by your friend's phone than try to force your phone into boot loader mode.Power off the phone completely,not stand-by but completely power off,and take out the battery for about one minute and insert it again.....Hold down the camera button and while keeping it holding down push down the power on button,as normally you power on the phone,The phone will start up,keep holding down the camera button till your phone gets into bootloader mode(multicolor screen),if it goes into bootloader mode,that means it's not "Bricked"

[lou2ser]

I'm pretty sure. I wrote it down before staring the update process.

Not sure if this matters:
GSM: 2.25.11.1
OS: 2.25.1.1

Am I describing what a bricked phone looks like? Any other ideas on how to revive it?

This was a replacement from ATT under warranty from an 8125 that had a bad touchscreen. It broke the 1st day and I'm sure I can get another replacement but I want to make sure they aren't going to find a way to power it up and see the hacked firmware.

[zabardast_1]

I'm pretty sure. I wrote it down before staring the update process.

Not sure if this matters:
GSM: 2.25.11.1
OS: 2.25.1.1

Am I describing what a bricked phone looks like? Any other ideas on how to revive it?

This was a replacement from ATT under warranty from an 8125 that had a bad touchscreen. It broke the 1st day and I'm sure I can get another replacement but I want to make sure they aren't going to find a way to power it up and see the hacked firmware.

GSM 2.25.11.1 and OS 2.25.1.1 are the Radio version and windows Rom version which were installed on your phone before.they are not IPL/SPL bootloaders,it can only be verified if a device is a G3 or G4 by bootloader IPL/SPL data.

well,usually when you flash a rom,it replaces the IPL/SPL of the phone,as your phone does not show even the bootloader mode,its difficult to say,if the ipl/spl has been repladed or not.
So if it still has the initial bootloaders IPL/SPL,which were uploaded by the vendors,than there's no problem for replacement,as you can always say that,it never started again,BUT !!!,if during the flashing of Button's Rom 1.05,it has replaced the IPL/SPL than I'm really sorry,it won't be easy to explain and get away that the device was not fiddled with and you won't get a warranty replacement :(

[lou2ser]

GSM 2.25.11.1 and OS 2.25.1.1 are the Radio version and windows Rom version which were installed on your phone before.they are not IPL/SPL bootloaders,it can only be verified if a device is a G3 or G4 by bootloader IPL/SPL data.

well,usually when you flash a rom,it replaces the IPL/SPL of the phone,as your phone does not show even the bootloader mode,its difficult to say,if the ipl/spl has been repladed or not.
So if it still has the initial bootloaders IPL/SPL,which were uploaded by the vendors,than there's no problem for replacement,as you can always say that,it never started again,BUT !!!,if during the flashing of Button's Rom 1.05,it has replaced the IPL/SPL than I'm really sorry,it won't be easy to explain and get away that the device was not fiddled with and you won't get a warranty replacement :(

The GMS and OS versions were recorded before any update was done. As of right now the phone does nothing whatsoever. I just want to make sure there's not a magic button the technician can push to see my tampering.

Again, thanks for your help.

[zabardast_1]

The GMS and OS versions were recorded before any update was done. As of right now the phone does nothing whatsoever. I just want to make sure there's not a magic button the technician can push to see my tampering.

Again, thanks for your help.

wee.this you know yourself that they are the manufacturers,technicians and have all the gadgets,knowledge and means to find out.lol

why don't you atleast try the 'Force bootloader' once,let's check it out.huh !
Try this.First fully charge the battery,somehow,even you can do this by your friend's phone than try to force your phone into boot loader mode.Power off the phone completely,not stand-by but completely power off,and take out the battery for about one minute and insert it again.....Hold down the camera button and while keeping it holding down push down the power on button,as normally you power on the phone,The phone will start up,keep holding down the camera button till your phone gets into bootloader mode(multicolor screen),if it goes into bootloader mode,that means it's not "Bricked"

[licensedtoquill]

As long as your phone gets into bootloaders(tri color screen),it's not 'Bricked',be rest assured of this,ok :)

I figured as much: In fact I was going to repost with the heading "Help. My phone isn't bricked, What can I do next?"

[/QUOTE]Secondly until and unless you have working OS on your phone,it'll not be recognized by the computer,as it cannot establish connectivity through Activesync.[/QUOTE]

Absolutely correct: The phone isnt seen by the computer. The only way I can transfer a ROM onto it is to get to bootloader screen by pressing the LASSOO (not the camera button) while powering on and then putting the USB cable in.

[/QUOTE]Activesync will only detect your phone in a normal working status,so in present status,your phone doesn't bootup normally into working OS and it only goes into bootloaders,it will never be detected by the Activesync and thus your computer.
The only test to verify the connectivity of your phone with computer at present is that when you attach your phone with the USB cable to the PC and there appears small usb at the bottom of the bootloader screen,that means your phone has established connectivity with PC. [/QUOTE]

Yes, it does. And I know I shouldnt be able to, but I CAN flash a ROM from there! Not only flash it but also change the SPL/IPL! (which then appears both on the tricolour screen as well as on the frozen screen)
[/QUOTE]
It's a 'catch 22' situation,where your bootloaders are not accepting any Rom flash and the only way is to get your phone start working normal and unlock it[/QUOTE]
Now I am confused all over again: When it is unlocked, if I downgrade the IPL from 2.26 to 1.01, do I need to CID Unlock it all over again? I have successfully flashed Button and it showed 1/.01 on the frozen screen and I then successfully flashed Manufacturer's ROM and now it shows 2.26 again on the bootloader AND the frozen T-Mobile screen.

[/QUOTE] ,for that it's required to downgrade to ipl/spl 1.xx,or the other option is to flash the official rom to bring it back to it's default status and then try to downgrade to ipl/spl 1.xx and unlock it.
Well,as you say it's not charging that cud be a major hindrance in flashing,cuz it's recommended to have atleast 70% charged battery before starting any flash,[/QUOTE]
in practice I always flash on a full charge
[/QUOTE]if it does not retain charge during a flash and does not have enough juice left to complete the flash then the flash will not complete,it's a bad flash and phone usually stuck up at the bootloader screen,this cud also be the problem ,you are not getting a full proper flash.[/QUOTE]
Almost all of my flashed end successfully. On the one occasion they didnt, I was trying ot be a wiseguy when no ROM woudl work and tried flashing from the manufacturer's to Molski!! That didnt complete successfully and gave me instructions on how to unbrick. But after that I have now successfully flashed to the T-Mobile one.
[/QUOTE]
Try to fully charge your battery and then try to flash,if it's not charging,than check your charger or the usb plug of the charger,it might not be having a good connection with the mini usb port of your phone,wiggle it a bit and see if it starts to charge,[/QUOTE]
You have correctly identified another problem here: It does sometimes need wiggling to get it to charge. But it never seems to need wiggling to get the USB letters to appear on the bootloader screen???
[/QUOTE]secondly,it cud also be the mini usb port of your phone which might be malfunctioning,anyway verify and rectify the problem.if it's the usb plug of the charger,get a new charger,but if it's the mini usb port,than I'm afraid you'll have to get it repaired or replaced,
good luck :)[/QUOTE]

Is it likely to need this repair if USB always comes up on the tricolour screen without problems as soon as I plug the cable in to the port?

[lou2ser]

wee.this you know yourself that they are the manufacturers,technicians and have all the gadgets,knowledge and means to find out.lol

why don't you atleast try the 'Force bootloader' once,let's check it out.huh !
Try this.First fully charge the battery,somehow,even you can do this by your friend's phone than try to force your phone into boot loader mode.Power off the phone completely,not stand-by but completely power off,and take out the battery for about one minute and insert it again.....Hold down the camera button and while keeping it holding down push down the power on button,as normally you power on the phone,The phone will start up,keep holding down the camera button till your phone gets into bootloader mode(multicolor screen),if it goes into bootloader mode,that means it's not "Bricked"

No change, still dead. I think I'm in the clear. :)

[zabardast_1]

licensedtoquill
how come you know that your phone is CID unlocked ?

as long as you are not able to load up the phone in working OS,it's not a successful flash,and untill and unless you have a working os you cannot verify if it's cid locked/unlocked.
therefore,it's essential you to have a working OS to check and upgrade to any wm6.secondly T-Mobile 2.26 is itself a official rom it will get flashed without getting the phone cid unlocked.so just by thinking that you have flashed Button's Rom and it confirmed by 100% 'congratulation and then stuck up at spash screen doesn't mean it was a successful flash and you applying lokiwiz tool in this status will certainly won't work or unlock the phone.
As I said earlier it only works in a working OS and only if it confirms afterwards,see the image below ,how lokiwiz confirms:-

[zabardast_1]

No change, still dead. I think I'm in the clear. :)


That's it !!!
sorry to say you got a "BRICK",infact you had a G4 device with IPL/SPL 2.25.0001 and you flashed a G3 Button's Rom 1.05,it bricked the phone.:eek:

[licensedtoquill]

licensedtoquill
how come you know that your phone is CID unlocked ?

as long as you are not able to load up the phone in working OS,it's not a successful flash,and untill and unless you have a working os you cannot verify if it's cid locked/unlocked.
therefore,it's essential you to have a working OS to check and upgrade to any wm6.secondly T-Mobile 2.26 is itself a official rom it will get flashed without getting the phone cid unlocked.so just by thinking that you have flashed Button's Rom and it confirmed by 100% 'congratulation and then stuck up at spash screen doesn't mean it was a successful flash and you applying lokiwiz tool in this status will certainly won't work or unlock the phone.
As I said earlier it only works in a working OS and only if it confirms afterwards,see the image below ,how lokiwiz confirms:-

OK I hadn't realised this: I was TOLD that the phone was unlocked (by a guy who may just have tried to flash a locked phone, not realised what he had done and then tried flashing the T-Mobile ROM, causing the frozen screen) and I thought that if a flash went to 100% and then reported completion and then I flashed with the Official one and IT reported success, this must mean that the phone is unlocked.

Most importantly, where can I get the utility you show? All I have is one which gives you a DOS screen with 4 options, do nothing (I think) sim unlock, cid unlock and exit. No buttons, no checks or anything like that. Can I load this utility by getting to the bootloader screen, connecting the USB cable and opening the utility? (That APPEARS to be all I can do at the moment.)

The Lokiwiz utility I have got also doesn't complete: It runs and doesnt do anything (haven't tried leaving it on all night but an hour or so should tell me that it isnt working, shouldn't it?)

When I first started all this with a different phone, I did try like a newbie to flash a locked phone and it went to 98% and then stopped before I realised that the phone simply wasn't unlocked. I then unlocked it.

[zabardast_1]

This Tool is called WST Tool by mestrini and you can download from the link below,bit then again it cannot also work in bootloader mode,it also require a normal workinh phone.
http://forum.xda-developers.com/showthread.php?t=329170

well,back to the same situation,you got to have a working phone to proceed further either way,so just concentrate how to get it back on the road ,otherwise nothing can be done in this state.:)

[licensedtoquill]

just concentrate how to get it back on the road ,otherwise nothing can be done in this state.:)


But there are no suggestions as to what one can do in this situation, when you havent got a bricked phone but you cant connect with it as someone has at some time screwed up the installation of the OS in some way. At the moment I have the T-Mobile official ROM 'on' it, stuck at the first screen. The only way I can get it to connect to the computer is by plugging in the USB cable when the 2.26 bootloader screen is displayed. what tricks are there to get a Wizard without an OS properly installed on it to communicate with the computer so that I can flash the ROM with anything at all???

[zabardast_1]

But there are no suggestions as to what one can do in this situation, when you havent got a bricked phone but you cant connect with it as someone has at some time screwed up the installation of the OS in some way. At the moment I have the T-Mobile official ROM 'on' it, stuck at the first screen. The only way I can get it to connect to the computer is by plugging in the USB cable when the 2.26 bootloader screen is displayed. what tricks are there to get a Wizard without an OS properly installed on it to communicate with the computer so that I can flash the ROM with anything at all???

Why don't you try flashing the stock T-mobile 2.26 with a replaced 'romupdateutility',it sometimes help,download the attached zipfile,extract it in a folder,you'll see four files in,just copy and paste these four files in the T-mobile Rom folder and replace the similar four files in the T-mobile 2.26 Rom and reboot your pc,reboot your phone,get into bootloaders,connect with usb cable,confirm usb appear at the bottom of bootloader screen and run the replaced 'romupdateutility'in the T-mobile Rom 2.26,hope it might do the trick,cheers

[licensedtoquill]

Why don't you try flashing the stock T-mobile 2.26 with a replaced 'romupdateutility',it sometimes help,download the attached zipfile,extract it in a folder,you'll see four files in,just copy and paste these four files in the T-mobile Rom folder and replace the similar four files in the T-mobile 2.26 Rom and reboot your pc,reboot your phone,get into bootloaders,connect with usb cable,confirm usb appear at the bottom of bootloader screen and run the replaced 'romupdateutility'in the T-mobile Rom 2.26,hope it might do the trick,cheers

Great idea if it will let me flash from the bootloader screen. Many thanks: Just one minor point. I flash the T-Mobile ROM with an exe file (called T-Mobile_RUU_Wizard_2261020_226_22511_ENG_US.exe).

Do you have any idea where it creates it's folder if it does so? I cant find it on my hard drive and think it deletes the folder as part of the cleaning up process after the flash? Or where can I find a t-mobile ROM which executes in the normal way and creates a folder?

[zabardast_1]

Great idea if it will let me flash from the bootloader screen. Many thanks: Just one minor point. I flash the T-Mobile ROM with an exe file (called T-Mobile_RUU_Wizard_2261020_226_22511_ENG_US.exe).

Do you have any idea where it creates it's folder if it does so? I cant find it on my hard drive and think it deletes the folder as part of the cleaning up process after the flash? Or where can I find a t-mobile ROM which executes in the normal way and creates a folder?

Create a new folder anywhere,lets say in 'My documents' and just name it anything,e,g 'T-mobile' and copy and paste the original official T-Mobile Rom(T-Mobile_RUU_Wizard_2261020_226_22511_ENG_US.exe) in it.
Use winRAR extraction utility...Then right click the exe file(T-Mobile_RUU_Wizard_2261020_226_22511_ENG_US.exe),ch oose & click 'extract it' from the drop box ,it'll open the options page wth all the drives and folders on your computer,with present derive and folder already pr-selected in the destination path,just click 'ok',it'll create a folder bu itself and extract the contents of the exe file of T-Mobile in it in the same folder which you created and placed the original T-Mobile Rom.You'll find all the contents of the official T-Mobile extracted in the new created folder by the winRAR.:)

[licensedtoquill]

Create a new folder anywhere,lets say in 'My documents' and just name it anything,e,g 'T-mobile' and copy and paste the original official T-Mobile Rom(T-Mobile_RUU_Wizard_2261020_226_22511_ENG_US.exe) in it.
Use winRAR extraction utility...Then right click the exe file(T-Mobile_RUU_Wizard_2261020_226_22511_ENG_US.exe),ch oose & click 'extract it' from the drop box ,it'll open the options page wth all the drives and folders on your computer,with present derive and folder already pr-selected in the destination path,just click 'ok',it'll create a folder bu itself and extract the contents of the exe file of T-Mobile in it in the same folder which you created and placed the original T-Mobile Rom.You'll find all the contents of the official T-Mobile extracted in the new created folder by the winRAR.:)

WOW! It's not that I am an idiot but I would have never thought of opening an exe file with any other program! I thought you could only double click them. Many thanks. Will do it ASAP

[licensedtoquill]

Create a new folder anywhere,lets say in 'My documents' and just name it anything,e,g 'T-mobile' and copy and paste the original official T-Mobile Rom(T-Mobile_RUU_Wizard_2261020_226_22511_ENG_US.exe) in it.
Use winRAR extraction utility...Then right click the exe file(T-Mobile_RUU_Wizard_2261020_226_22511_ENG_US.exe),ch oose & click 'extract it' from the drop box ,it'll open the options page wth all the drives and folders on your computer,with present derive and folder already pr-selected in the destination path,just click 'ok',it'll create a folder bu itself and extract the contents of the exe file of T-Mobile in it in the same folder which you created and placed the original T-Mobile Rom.You'll find all the contents of the official T-Mobile extracted in the new created folder by the winRAR.:)

Is there a problem with the T-Mobile ROM on the site? I tried to do what you said and used what was called the TMobile ROM. I opened it as you say and replaced the files as you say. It suddenly told me it was updating to Faria?? So I tried and it (up)dated successfully from ipl/spl 2.26 to Button with an ipl 1.01, along with the frozen beer mug screen. So I went to another computer and tried the same thing again with what might be a different version of the T-Mobile ROM, also an exe file called MDA_software_update_226102_22610105_022511.

STILL it tells me that I am updating to Faria AKU 3.3. And that this isnt the correct update tool to do this??

Will your suggestion of how to flash from the bootloader screen with an adapted utility work with the actual T-Mobile ROM and if so where can I get it please?

[zabardast_1]

Is there a problem with the T-Mobile ROM on the site? I tried to do what you said and used what was called the TMobile ROM. I opened it as you say and replaced the files as you say. It suddenly told me it was updating to Faria?? So I tried and it (up)dated successfully from ipl/spl 2.26 to Button with an ipl 1.01, along with the frozen beer mug screen. So I went to another computer and tried the same thing again with what might be a different version of the T-Mobile ROM, also an exe file called MDA_software_update_226102_22610105_022511.

STILL it tells me that I am updating to Faria AKU 3.3. And that this isnt the correct update tool to do this??

Will your suggestion of how to flash from the bootloader screen with an adapted utility work with the actual T-Mobile ROM and if so where can I get it please?

you can download official T-Mobile 2.26 Rom from this link,hope this'll work,good luck:-
http://www.lvlolvlo.net/wp-content/u...wwe_ship. zip

[licensedtoquill]

you can download official T-Mobile 2.26 Rom from this link,hope this'll work,good luck:-
http://www.lvlolvlo.net/wp-content/u...wwe_ship. zip

No, snot there any more: Any idea where another is please?

[licensedtoquill]

Why don't you try flashing the stock T-mobile 2.26 with a replaced 'romupdateutility',it sometimes help,download the attached zipfile,extract it in a folder,you'll see four files in,just copy and paste these four files in the T-mobile Rom folder and replace the similar four files in the T-mobile 2.26 Rom and reboot your pc,reboot your phone,get into bootloaders,connect with usb cable,confirm usb appear at the bottom of bootloader screen and run the replaced 'romupdateutility'in the T-mobile Rom 2.26,hope it might do the trick,cheers

There is a problem with your files: I managed to find a mysterious file on my Briefcase called MDA_software_update_226102_22610105_022511.exe which does execute as an installation of the T-Mobile ROM. It upgraded the Button which we arrived at when I installed your suggestions as I described. (which left me with an ipl of 1.01/spl 2.26)

It installed the TMobile ROM again successfully. Which now freezes at the red text screen on the TMobile background, But the red text does now show that I now do have ipl/spl 2.26. So I tried to replace the extracted files on this .exe file with those from your download as per your instructions. This gave me a Faria 3.3 screen again and when I tried to upgrade as you suggest, it gave me a 'wrong upgrade utility' tool screen. But at least it communicates with the device

I then as an experiment tried to install the 3/08 ipl/spl. That upgrade utility reported non-communication between the computer and the Wizard!

Are you sure you zipped up the correct files please?

[zabardast_1]

There is a problem with your files: I managed to find a mysterious file on my Briefcase called MDA_software_update_226102_22610105_022511.exe which does execute as an installation of the T-Mobile ROM. It upgraded the Button which we arrived at when I installed your suggestions as I described. (which left me with an ipl of 1.01/spl 2.26)

It installed the TMobile ROM again successfully. Which now freezes at the red text screen on the TMobile background, But the red text does now show that I now do have ipl/spl 2.26. So I tried to replace the extracted files on this .exe file with those from your download as per your instructions. This gave me a Faria 3.3 screen again and when I tried to upgrade as you suggest, it gave me a 'wrong upgrade utility' tool screen. But at least it communicates with the device

I then as an experiment tried to install the 3/08 ipl/spl. That upgrade utility reported non-communication between the computer and the Wizard!

Are you sure you zipped up the correct files please?

Download the latest official T-Mobile Rom of your device from here :-
http://www.tm-phonedownloads.com/index.html

cheers ::)

[snootch]

Licensedtoquill: Are you using XP or Vista on your computer? I ask because I am having the exact same problems as you, but I believe my issues are Vista related. Everyone seems to swear the T-mobile 2.26 rom WILL flash through bootloader even though the wizard may be CID-locked. I have tried it over and over and have the same symptoms as you. However I am using Vista, and am adding dual-boot XP partition right now; so I'll see how it works using XP. (and BTW, yes I did install the wbsh.inf driver for vista before, still didnt work)

[licensedtoquill]

Licensedtoquill: Are you using XP or Vista on your computer? I ask because I am having the exact same problems as you, but I believe my issues are Vista related. Everyone seems to swear the T-mobile 2.26 rom WILL flash through bootloader even though the wizard may be CID-locked. I have tried it over and over and have the same symptoms as you. However I am using Vista, and am adding dual-boot XP partition right now; so I'll see how it works using XP. (and BTW, yes I did install the wbsh.inf driver for vista before, still didnt work)

I have now as I say tried to download the T-Mobile software from the T-Mobile site to which you now direct me and install it. It installs properly and finishes and gives me the frozen t-mobile screen with IPL/SPL 2.26. I then add your files and it tells me it is flashing Faria 3.3 and then tells me that the update utility is incorrect.

[licensedtoquill]

Licensedtoquill: Are you using XP or Vista on your computer? I ask because I am having the exact same problems as you, but I believe my issues are Vista related. Everyone seems to swear the T-mobile 2.26 rom WILL flash through bootloader even though the wizard may be CID-locked. I have tried it over and over and have the same symptoms as you. However I am using Vista, and am adding dual-boot XP partition right now; so I'll see how it works using XP. (and BTW, yes I did install the wbsh.inf driver for vista before, still didnt work)


Sorry for the cross-posting. I am hoping that this isn't seen as a hardware problem because no one on this forum seems to like to respond to hardware problems. As soon as things start to look like hardware problems, threads dry up quickly

It is a bit suspicious that so many people have this problem (see numbers of page views) that it doesnt look like a hardware problem; and surely amongst all the authorities, SOMEONE must know what causes this and the procedures for loading ROMs properly when all you can get into is the bootloader? The unit itself certainly doesn't seem to dislike loading anything from the tricolour screen so I wonder why we cant do it?

[zabardast_1]

Sorry for the cross-posting. I am hoping that this isn't seen as a hardware problem because no one on this forum seems to like to respond to hardware problems. As soon as things start to look like hardware problems, threads dry up quickly

It is a bit suspicious that so many people have this problem (see numbers of page views) that it doesnt look like a hardware problem; and surely amongst all the authorities, SOMEONE must know what causes this and the procedures for loading ROMs properly when all you can get into is the bootloader? The unit itself certainly doesn't seem to dislike loading anything from the tricolour screen so I wonder why we cant do it?

Ok,let me try to clear a few things in your mind here,regarding not being able to flash and recover the device.
First of all it's not a Hardware problem here, if your phone gets into Bootloader mode and while in bootloaders you can see usb appear at the bottom of your phone,while getting it connected to the pc via usb cable.if it doesn't appear then you got a Hardware malfunction,either your cable is not establishing connectivity or mini usb port of the phone is faulty.

Secondly,as long as your phone gets into bootloaders then it's not 'Bricked' and working,the only problem is that it's not able to flash a working OS on the phone, cuz somehow the Bootloaders (IPL/SPL) have got corrupted.It usually happens when people don't do the procedure correctly as per guides provided and do something, which is not required to do or miss any step correctly.

Read through the whole forum,guys with similar devices like yourself have got it done easily and successfully, thousands have done,only a few have got stuck,unfortunately,that to only to their own mishandling and not following and understanding the procedure correctly as instructed in the guides,Although it happens,no one is perfect,mistakes do happen,but you shud not blame somebody for it.It's very clearly been warned in the forum "To Do At Your Own Risk",Still all the methods and guides have been very explicitly and elaborately posted and stickied for the public to 'READ AND READ" and fully understand the procedure and only then do the method.

Anyway, as for this problem of your's,as the bootloaders have got corrupt somehow,the only way out is to get them corrected by flashing the official carrier's to get your phone back to it's default status,and then downgrade to IPL/SPL 1.xx to CID unlock,or try to flash any IPL/SPL 1.xx Rom,it cud be Button's Rom 1.05 or any Official carrier's Rom 1.xx to downgrade and apply CID unlock.It's a catch 22 situation!!
Cheers

[licensedtoquill]

the bootloaders have got corrupt somehow,the only way out is to get them corrected by flashing the official carrier's to get your phone back to it's default status,and then downgrade to IPL/SPL 1.xx to CID unlock,or try to flash any IPL/SPL 1.xx Rom,it cud be Button's Rom 1.05 or any Official carrier's Rom 1.xx to downgrade and apply CID unlock.It's a catch 22 situation!!
Cheers

You may be right but just telling me that it is my fault doesn't actually assist me: When I got this phone the screen was frozen at t-mobile. Since then I have flashed successfully in my spare time a few dozen times but never got past that frozen screen. I have upgraded to SPL/2.26 and downgraded to IPL 1.01 (tried to CID unlock unsuccessfully) and upgraded again numerous times but I don't get past the first splash screen which freezes as soon as the red writing appears on it.

Please dont take this the wrong way but you are simply wrong when you say that all which is needed is to flash to the carrier's stable ROM and then do whatever. The last stage in that process isn't the SUCCESS message (or apparently even the installation of the new SPL/IPL), it is the successful restarting of the device.

The procedure doesn't look all that difficult and isn't susceptible to getting it wrong somewhere along the way (especially when users are told they have flashed successfully). When I have followed your instructions to the letter and still get frozen, doesn't it mean something to you?

You say there are posts out there. The search function of this forum isn't the best: Have you ever read any post which says that anyone has flashed to the carrier's ROM and a frozen screen resulted and .......... is the way out of this mess? Why do YOU think there are 612 page views of this thread? The catch 22 is that when you flash the carrier's ROM, you get a frozen screen. Thereafter, as far as I can see, you cant enter the CID unlock from the bootloader screen? You CAN downgrade to button but you still cant reset or unlock.

If you dont agree that the non-resetting is the problem, what reason do you have for the error message I am getting which tells me that when I replace the files in the T-Mobile ROM with the ones you sent after successfully flashing the carrier's ROM, I am told I am using the wrong utility. If we can understand this problem, we might get somewhere but would probably still have the non-resetting problem? With respect, if you continue to tell me to continue to follow the same steps which inevitably result in a frozen screen, we aren't going to get far.

Perhaps if you don't know the answer to this question, you could consider this question for the 612 people out there who seem to have this problem with frozen screens: You say simply "flashing the official carrier's to get your phone back to it's default status,and then downgrade to IPL/SPL 1.xx to CID unlock,or try to flash any IPL/SPL 1.xx Rom,it cud be Button's Rom 1.05 or any Official carrier's Rom 1.xx to downgrade and apply CID unlock." which tells me that the phone becomes CID locked when flashing down after flashing the carrier's ROM (which I didn't know). Should there be some change made to the unlock utility to cover the 612 people who have flashed to the carrier's ROM and the still got to the frozen screen and who can ONLY unlock from the bootloader screen? If so how does one address this problem if your suggested adaptation contained in the zip file you sent results in the WRONG UPGRADE UTILITY error message.

As far as I can see, - and I may be oversimplifying,- besides re-flashing the carrier's ROM 20-30 times before it gets it right and resets, THIS is the only conceivable place where one CAN go wrong in the instructions you gave?

Put another way, has anyone EVER flashed the carrier's ROM successfully to a frozen screen and managed to get out of it without the carrier's ROM starting successfully so that they can get to the steps you mention? Don't take this the wrong way, - I can see you are trying to help, - but to me it is blindingly obvious that the problem you yourself mention (the supposedly incorrectly followed step) is that the device doesn't reset on restart after flashing the carrier's ROM! IT FREEZES.

[zabardast_1]

Ok,
You started this thread on 20/10/2007,with the post that you have a device with frozen splash screen.
I know you have an experience in flashing, as evident from your 80+ posts.Till to date I have tried to help you out of this problem to the best of my knowledge,which I have gathered here and have very successfully unlocked and upgraded more than two dozen devices. I,too had a few problems with some devices,but always through trial & error and,of course, worth mentioning flashing the official carrier's Rom,always did the trick.I have read and gone through almost all the forums and threads,every guru and techy recommends to flash a stock rom to recover back to default.Even this has been very specifically recommended in many unlocking and upgrading guides by the gurus of this forum.Just for reference,read this excellent guide from Dr.P,from which thousands have benefitted and I quote "IF, by chance your device hangs and never completes the flash (always give it a LOT of time, with no programs running, hopefully after a fresh reboot of your computer) you'll be stuck in (hopefully) the bootloader screen. It's very scary (at least to me the 4 or 5 times my own custom ROM's have been bad) all is not lost. Each time (after trial and error) I was able to restore. If this happens reboot your PC and then rerun the Button 1.05. It will act like it doesn't see it at first but have faith! I've tried this by using various provider's shipped ROMs and it always tell me it can't communicate. But, if I reboot, the 1.05 has always worked.":-
http://forum.xda-developers.com/showthread.php?t=285435

I never compelled you to follow my instructions,if you had any reservations,then why did you adopted my instructions,well as you say I was wrong in my instructions and methods,just for your ease,read all my posts,hope you'll be satisfied of my instructions and the way I have tried to help out the guys,I don't say I'm a high tech expert in unlocking and upgrading but,Yes I can manage it quite fairly.

Secondly,mind you ,I never forwarded you with any such rom or program of my own,other than,which has not been already posted or referred in this forum,and people have used them and been successful in recovering their devices,
Lastly,since your posting,this thread has been viewed 668 times by the members,Gurus,Moderators,Administrators and many who are much,much more knowledgeable and experts, if I was giving you wrong instructions and misleading you,certainly someone must have corrected me,so I believe I did my best to help you out.
Bye

[snootch]

I got it to work! see post #13: http://forum.xda-developers.com/showthread.php?p=1619858#post1619858

[licensedtoquill]

Ok,
It's very scary (at least to me the 4 or 5 times my own custom ROM's have been bad) all is not lost. Each time (after trial and error) I was able to restore. If this happens reboot your PC and then rerun the Button 1.05. It will act like it doesn't see it at first but have faith! I've tried this by using various provider's shipped ROMs and it always tell me it can't communicate. But, if I reboot, the 1.05 has always worked.":-
http://forum.xda-developers.com/showthread.php?t=285435

Hey WHOA wait a minute: I am not blaming you for anything and am grateful to you for your suggestions!! This isn't your problem, it is mine [and a huge number of others']. And I am lucky to get anyone to respond to my posts. Nobody else does, - so let's try to work together on this as the moderators don't seem to care about those around-600 people who seem to have this problem.

I personally don't believe that you can flash anything when you haven't managed to get your device to reset itself after the last flash but I am willing to try again

I wonder why none of the real experts will chime in with any solution to the can-only-flash-from-bootloader problem? They all seem quite willing to tell any number of newbies their solutions to common problems which arise out of the newbies not reading the instruction properly or not reading threads before responding and asking already-answered problems!

Thanks again!

[giangnh]

I am a patient, also. ur Problem is my problem, too.
My situation:
1. IPL/SPL 2.26 (T-mobile original) -> any wm5, wm6: ok
2. IPL/SPL 2.26 -> downgrade -> Button 1.05 -> lokiwiz02b -> unlock CID -> IPL/SPL 3.08: ok
3. IPL/SPL 3.08 -> wm6 (any rom)
some fail process -> IPL 1.05 or 1.01 + SPL 3.08 + Formatting FAT partition Format is fail: Stuck
4. any up/downgrade process:
4.1. not greater than: IPL 1.01 or 1.05
4.2. SPL 3.08 was fixed (can not change to any version)
4.3. GSM, OS version can change with Button's Rom <-> T-mobile's rom original (2.26.xx)
4.4. Always: Formatting FAT partition Format is fail.
5. I try with Xda_MiniS_LaunchROM_v154102: Invalid vendor ID -> used: Wizard service tool to extract nk.nbf after that is nbfsplash-tool.exe to modify to Wizard and language is US -> downgrade with that -OS, GSM version changed but IPL/SPL no change. Stuck long time - hard reset -> Format is failed.
6. I try use mtty v1.11a or/and v1.42: I try:
--------------------------------------------
Cmd>info 2

GetDeviceInfo=0x00000002

+ SD Controller init

- SD Controller init

+StorageInit

***** user area size = 0x77A80000 Bytes

HTCSWIZTMU01 â-r€HTCE
Cmd>format BINFS
Not allow operation!

Cmd>l 1
clean up the image temp buffer at 0x8C100000 Length 0x03900000
BOOTLOAD_PAGE_TABLE_BASE_C_VIRTUAL= 0x8C080000
Clear image temp buffer done .
MTTYDownloadImageNot allow operation!
Error : DownloadImage return error (code = 0xFFFFFFFF)

Cmd>format BINFS
Not allow operation!

Cmd>set BINFS_TYPE

Cmd>format BINFS
Not allow operation!

Cmd>ResetDevice
----------------------
r2sd all
***** user area size = 0x77A80000 Bytes

R2SDBackup() - Download type = 5
usTotalBlock = 1 sizeof(SDCARD_SIGNATRUE_TABLE)=512

You didn't get the proper security level to download a specific image
-------------------------------------------------------------------
ruurun 0
Need password!


Cmd>
------------------------------
I try to prepare splash from SD card but received:"You didn't get the proper security level to download a specific image". It is mean: my wizard locked? "Need passwor!" what is going on? How I can get password and how to put in password and how to...continue?

How I can solved it?

Help me, please! 2 days over, no wizard, no happy..help me!

[snootch]

Looks like your phone wasn't actually CID-unlocked before you attempted to flash it. The same thing hapenned to me, ans apparently the thread-starter. I do not know how to fix the problem without spending some money. Apparently it is possible, but I really did not have the time to mess with it. See my post in this thread to a link to the solution. (post #43) I had to spent approximately $40. But my phone works again, and I installed a WM6 ROM with no problems. Hope you can get yours fixed as well. Good luck!

[giangnh]

11day pass over. no PPC, no dictationary, no map, no magicall, no thing
To day is a my happiness day. hehe..
I solved my problem without any fee from any check imei site.
I post my progress for everybody can reference. My English is very very terrible, so sorry.
1. Run doctest to downgrade SPL is the same IPL (1.05 or 1.01)
2. Run CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE.exe (in Bootloader)
3. Nothing change (format is failed, r2sd ..GetCID: error,)
4. Run RUU_Prophet_215738_2157127_023021_QTEK_FRE_Ship_No VendorID (ftp xda site) -> SPL,Splash, version... changed, but still "format is failed" (hard reset as Prophet's way)
5. once more run CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE.exe (in Bootloader)
6. Everything is ok (without simcard):
7. If within sim card notice that: "Data crashed":
- remove sim card, using WZS tool for write rom CID with CIDunlocked.bin (64k) (I was backup, when unlocked by lokiwi02b) ->soft reset.
- continue unlock sim only when finish CID unlocked (using WZS tool).
--------------------------------------------------------------------
Thanks to PDAviet.net: http://pdaviet.com/showthread.php?p=174500
I try to thanks this site but too many time this server was down.
In this thread they give another Prophet rom and I unsucessful with that.
-----------------------------------------------------------------------
I hope, my problem can help someone. My YM: engine3stage@yahoo.com
If something is not clearly, I can help anyone by YM.
------------------------------------------------------------------------
Thank so much to XDA development was help everybody