Related
Maybe some of you are already aware of this procedure, maybe not.
Anyway, it worked for me and I decided to share how to do it. Simple.
This procedure should only be used in case you really need enter into a bootloader mode and all other ways to do it has failed! Hold Camera button is one of these I am mentioning.
My Wizard was almost bricked at that time and after I speak with an I-mate technical guy, I got the following:
1. Make sure your i-mate™ K-JAM 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 i-mate K-JAM to the Desktop PC using the USB Cradle and the Charger MUST be Connected to the Cradle (Don’t use the IrDA or Bluetooth for the Upgrade)
4. 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.
Hope it helps!
this realy worked for my (ex)bricked dutch tmobile mda vario !!!!
tip: REALY make shure that there is no wcescomm.exe running all the time and realy remove the sd card else is nogo
btw: my wizard is CID locked! and works like a charm
Thanks buddy!
I'm happy that worked for ya!
Take care!
I'm having a problem
The power went out as I was upgrading my Wizard (Cingular) so now it just turns on at the boatloader screen. I've tried running updates while it was in this screen (it did show the "USB" in the white bar) but most of the time it tells me there is a connection error. Even if I kill Activesync, I notice that when I run the update utility it still runs Activesync. I've tried disabling the USB connection but still get the connection error.
The only time I haven't gotten the connection error was twice it asked me to update but then told me I had the wrong file. This only happened when I tried "upgrading" to 1.05 as I was trying to start again. After it tells me that if I try running it again it gives me the connection error.
Any ideas?
Hi!
Have you already flashed your device once?
Which ipl/spl do you have?
I had problems over 1.05 ROM in the beggining.
If you stuck on bootloader mode, that's a good signal your device is not bricked.
I'd recommend you to disable activesync as you did and reflash it again! Check also if your device is CID unlocked! Search for a thread in the xda developers root.
Try to upgrade to ipl/spl 2.26 first and later to others you want.
Regarding the old file error...can be related to a missing file called enterbootloader.exe.
Hope it works for ya!
Take care
Ironman273 said:
I'm having a problem
The power went out as I was upgrading my Wizard (Cingular) so now it just turns on at the boatloader screen. I've tried running updates while it was in this screen (it did show the "USB" in the white bar) but most of the time it tells me there is a connection error. Even if I kill Activesync, I notice that when I run the update utility it still runs Activesync. I've tried disabling the USB connection but still get the connection error.
The only time I haven't gotten the connection error was twice it asked me to update but then told me I had the wrong file. This only happened when I tried "upgrading" to 1.05 as I was trying to start again. After it tells me that if I try running it again it gives me the connection error.
Any ideas?
Click to expand...
Click to collapse
My device is unlocked as I've been trying different ROMs as of late. I had gone back to the Cingular 2.25 ROM for a couple days to sort some things out and was going to flash Farias AKu 3.3 when my power problems happened. My Current IPL/SPL is 2.25
I've tried flashing the TMobile 2.26 but keep getting connection errors. In fact, I've tried flashing with every ROM I have pdviet 3 and 4, CIngular 2.25, TMobile 2.26 and Custom 1.05. Everything (except twice in the custom) gives me connection errors.
Any other trick I can try?
BTW, I used to live in Sao Paulo years ago...
Edit: OK, so I tried the 2.26 TMobile ROM after I typed this and it worked!! I'm back up but I was having trouble with that ROM beause of some incompatibilities with Cingular. I'll go back to Cingular's ROM and play it safe for now.
I believe part of my problem was I kept trying different updates one after the other. Now that I think back, the 2 times I got the update to almost work was after I turned off the device and turned it on again, which is what I did this time around also.
I had the same problems as mentioned by Ironman before. I followed the steps and with a few slight changes, I managed as well to "unbrick" my wiz. THANKS A LOT for the great step by step manual!!!
Still I wanted to know WHY i bricked my device:
I was trying to upgrade to the underground WM6 ROM. I got the same situation as ironman:
Quote:
The power went out as I was upgrading my Wizard (Cingular) so now it just turns on at the boatloader screen. I've tried running updates while it was in this screen (it did show the "USB" in the white bar) but most of the time it tells me there is a connection error. Even if I kill Activesync, I notice that when I run the update utility it still runs Activesync. I've tried disabling the USB connection but still get the connection error.
The only time I haven't gotten the connection error was twice it asked me to update but then told me I had the wrong file. This only happened when I tried "upgrading" to 1.05 as I was trying to start again. After it tells me that if I try running it again it gives me the connection error.
Unquote
I then followed the instructions by epimazzo as written above. I also tried the T-Mobile ROM 2.26 which was not working for me. PANIC!!!! Error messag was that I had the wrong Vendor ID. THerefore no upgrade to TMob 2.26 was possible. I tried it then my original qtek ROM in my language and see it worked!!! This IMHO means that I did not put the device in a proper IPL1.xx and SPL 1.xx status which is required for a clean system in irder to unlock it! So if it is bricked, try your native AKU2 ROM and make sure you unlocked it properly. Maybe you have to run the 1.05 ROM for a second time after the unlocking.
I hope this helps you guys.
Sounds great to hear that!
I had play around with pdaviet3, underground and another ROM just today without any problems at all. I don't think that this is the case. Now you get your device back to normal, try to reflash it again. Hope it works this time!
BTW,...São Paulo is a nice city. Thanks! Let me know if you decide to come here!
Take care
Ironman273 said:
My device is unlocked as I've been trying different ROMs as of late. I had gone back to the Cingular 2.25 ROM for a couple days to sort some things out and was going to flash Farias AKu 3.3 when my power problems happened. My Current IPL/SPL is 2.25
I've tried flashing the TMobile 2.26 but keep getting connection errors. In fact, I've tried flashing with every ROM I have pdviet 3 and 4, CIngular 2.25, TMobile 2.26 and Custom 1.05. Everything (except twice in the custom) gives me connection errors.
Any other trick I can try?
BTW, I used to live in Sao Paulo years ago...
Edit: OK, so I tried the 2.26 TMobile ROM after I typed this and it worked!! I'm back up but I was having trouble with that ROM beause of some incompatibilities with Cingular. I'll go back to Cingular's ROM and play it safe for now.
I believe part of my problem was I kept trying different updates one after the other. Now that I think back, the 2 times I got the update to almost work was after I turned off the device and turned it on again, which is what I did this time around also.
Click to expand...
Click to collapse
It seems you got the idea!
You did the right thing! Sometimes, use the official ROM can solve many issues out there!
Keep walking!
enlite_de said:
I had the same problems as mentioned by Ironman before. I followed the steps and with a few slight changes, I managed as well to "unbrick" my wiz. THANKS A LOT for the great step by step manual!!!
Still I wanted to know WHY i bricked my device:
I was trying to upgrade to the underground WM6 ROM. I got the same situation as ironman:
Quote:
The power went out as I was upgrading my Wizard (Cingular) so now it just turns on at the boatloader screen. I've tried running updates while it was in this screen (it did show the "USB" in the white bar) but most of the time it tells me there is a connection error. Even if I kill Activesync, I notice that when I run the update utility it still runs Activesync. I've tried disabling the USB connection but still get the connection error.
The only time I haven't gotten the connection error was twice it asked me to update but then told me I had the wrong file. This only happened when I tried "upgrading" to 1.05 as I was trying to start again. After it tells me that if I try running it again it gives me the connection error.
Unquote
I then followed the instructions by epimazzo as written above. I also tried the T-Mobile ROM 2.26 which was not working for me. PANIC!!!! Error messag was that I had the wrong Vendor ID. THerefore no upgrade to TMob 2.26 was possible. I tried it then my original qtek ROM in my language and see it worked!!! This IMHO means that I did not put the device in a proper IPL1.xx and SPL 1.xx status which is required for a clean system in irder to unlock it! So if it is bricked, try your native AKU2 ROM and make sure you unlocked it properly. Maybe you have to run the 1.05 ROM for a second time after the unlocking.
I hope this helps you guys.
Click to expand...
Click to collapse
Excellent post. I messed up with my own cooked ROM and could only get the bootloader screen. Tried the tips here - didn't work first time but I pulled the battery from the KJAM to reset it rather than using the reset button and it worked fine.
In my opinion this thread is so helpful to people who brick their device, it should go "sticky". Mods anything you can do about it?
Thanks buddy! I really appreciate!
We survive here over tips like that!
jt_armstrong said:
Excellent post. I messed up with my own cooked ROM and could only get the bootloader screen. Tried the tips here - didn't work first time but I pulled the battery from the KJAM to reset it rather than using the reset button and it worked fine.
Click to expand...
Click to collapse
Help me similar problem
I upgraded Super Rom, then my Wizard run very slow and no signal (no call out and in- no network at all). And Terible thing is PC could not dectect PPC thought Active Sync. I've soft and hard reset but no use.
So I donot know where to start to re install Rom again.
Please help me....
Hi there!
It seems that you just need to enter into the bootloader mode and reflash it again!
I had similar problems and more during my brick "false" stage!
So, just try to follow my steps here and you should be fine! Once you get into bootloader mode, just use any ROM out there to reflash.
Good [email protected]
thaiphong said:
I upgraded Super Rom, then my Wizard run very slow and no signal (no call out and in- no network at all). And Terible thing is PC could not dectect PPC thought Active Sync. I've soft and hard reset but no use.
So I donot know where to start to re install Rom again.
Please help me....
Click to expand...
Click to collapse
I was about to start a EMERGENCY HELP thread, but I *think* this is the right place instead.
The "touch" of my screen went dead today. It got progressively worse over a few hours, starting with difficulty in using the phone dialer, then random incorrect stuff getting triggered by screen taps.
So I hard reset, and got no response on the fifth alignment cross, meaning 1) "Tap on the screen...; 2) center; 3) top left; 4) bottom left; 5) bottom right. In that I could not proceed with alignment, I hard reset again, and now, at the first alignment screen, i.e. "Tap on the screen...", I have no screen response at all.
I called T-mo, and they are being great about sending a replacement ASAP (and getting me a loaner in the meantime).
BUT, I am running Faria+ AKU3.3 V2... so I clearly have to flash back to T-mo 2.26. I can;t figure out how to do it though, as no matter what I do I am stuck at the first alignment screen!!
HELP!! EMERGENCY!!!
(I have three or four days to get this done, so it's not THAT urgent)
Do a search for Broken Screen. Someone (either in Wizard Upgrading or in the Wizard forum) just had a similar issue with a cracked screen. They downloaded something that allowed them to get around the welcome page.
Actually, if you are just trying to flash a new ROM, don't even mess with it. Go straight to the Boot Loader screen (see the first post of this thread). No tapping necessary until the new rom is on (and that will be the Tmobile then so you would be good.
Thanks for the quick reply. Charging up to green now, and then will try to enter bootloader and flash T-mo 2.26. Will report back.
Worked great. Back to T-mo she goes!!!
BootLoader Mode
Excellent thread but you left out one thing.....exactly how to place your device in bootloader mode.
To clear up any misunderstanding because this is very important....this is how you do it:
Perform a soft reset, when the screen goes blank hold the camera button until a multi colored screen comes up .... That's it !!!!!!
When the unit is connected, USB is displayed at the bottom left.
[SOLVED! See page 4]
I have a Cingular 8125, which I hadn't used for a while (got a Trinity
I am trying to set it up for my wife, so I attempted to unlock it and upgrade to WM6. It is a G3 (it had 2.26). I had upgraded it several times before. but was never able to bring it down to 1.xx in order to unlock it.
So, I started trying to downgrade it, but basically, every time it entered bootloader, it seemed to lose connection and it just timed out on the PC, without ever going to the update bar on the bootloader screen.
I ran IPL_SPL_3.08, and it upgraded fine. But still no go on downgrading.
Finally, I ran Shelltool (bug fixed) and managed to flash to OS 1.5.4.2. But, after the hard reset, it just stays on the blue Cingular screen (showing IPL 3.08; SPL 3.08; GSM 02.47.11; OS 1.5.4.2.)
I have tried flashing again with an original Cingular WWE ROM (RUU_Wizard_225111_22511102_022511_CWS_WWE_Ship_1.exe), with the 1.5.4.2 ROM, even with a WM6 ROM (again, through Shelltool.) I have placed it in a powered cradle, have tried both Shelltool and RUU flashes, both while in the blue Cingular screen, and while in Bootloader mode. I have disconnected and reconnected each time, and rebooted many times (both the Wizard and the PC.) I have hard-reset. I have also tried both with USB selected and unselected in Activesync.
The Shelltool seems to freeze. The official RUU gives "ERROR [296]: UPGRADE ONLY. The NBF file cannot be used for your PDA Phone. Please get another NBF file." Or, alternately, it gives "ERROR [264]: CONNECTION."
Any ideas if this is repairable?
(Or should I cry (or take a hammer to the Wizard:-((
Mine is a 2.25 and it's a G4.. Isnt 2.26 a G4?
I think it was 2.26 (it may have been something like 2.27....), but it definitely didn't have the .000 at the end. I thought that the Wizards without the .000 were G3. Did I screw up?
Madcap180 said:
Mine is a 2.25 and it's a G4.. Isnt 2.26 a G4?
Click to expand...
Click to collapse
2.25.0001 or 2.26.0001 would be a G4
2.25 or 2.26 would be a G3
MacGuy2006 said:
I have a Cingular 8125, which I hadn't used for a while (got a Trinity
I am trying to set it up for my wife, so I attempted to unlock it and upgrade to WM6. It is a G3 (it had 2.26). I had upgraded it several times before. but was never able to bring it down to 1.xx in order to unlock it.
So, I started trying to downgrade it, but basically, every time it entered bootloader, it seemed to lose connection and it just timed out on the PC, without ever going to the update bar on the bootloader screen.
I ran IPL_SPL_3.08, and it upgraded fine. But still no go on downgrading.
Finally, I ran Shelltool (bug fixed) and managed to flash to OS 1.5.4.2. But, after the hard reset, it just stays on the blue Cingular screen (showing IPL 3.08; SPL 3.08; GSM 02.47.11; OS 1.5.4.2.)
I have tried flashing again with an original Cingular WWE ROM (RUU_Wizard_225111_22511102_022511_CWS_WWE_Ship_1.exe), with the 1.5.4.2 ROM, even with a WM6 ROM (again, through Shelltool.) I have placed it in a powered cradle, have tried both Shelltool and RUU flashes, both while in the blue Cingular screen, and while in Bootloader mode. I have disconnected and reconnected each time, and rebooted many times (both the Wizard and the PC.) I have hard-reset. I have also tried both with USB selected and unselected in Activesync.
The Shelltool seems to freeze. The official RUU gives "ERROR [296]: UPGRADE ONLY. The NBF file cannot be used for your PDA Phone. Please get another NBF file." Or, alternately, it gives "ERROR [264]: CONNECTION."
Any ideas if this is repairable?
(Or should I cry (or take a hammer to the Wizard:-((
Click to expand...
Click to collapse
I thought I read somewhere that IPL/SPL 3.08 was a bad convert from a Charmer? If this is true and the Charmer bootloaders are different than the Wizard bootloaders then you may have put yourself in a bind.
The fact that you can still get past bootloader is promising even though the phone doesn't finish booting.
Try flashing from the bootloader (tricolor IPL/SPL screen with USB in the corner)
Thanks. I've been trying to flash in both bootloader or "blue" screen, but no go so far. I just tried the official Cingular .nbf through shelltool: it spent about 30 minutes (in bootloader,) then it stopped responding. It's been doing this forever now.
Any other options left?
MacGuy2006 said:
Thanks. I've been trying to flash in both bootloader or "blue" screen, but no go so far. I just tried the official Cingular .nbf through shelltool: it spent about 30 minutes (in bootloader,) then it stopped responding. It's been doing this forever now.
Any other options left?
Click to expand...
Click to collapse
You CAN'T use shelltool in boot loader mode! it needs the OS and the TRUFFS to read and write to the phone.
Any phone that doesn't go past the boot loader must be fixed with mtty, RUU or SD card...
Thanks for the info. I've been reading about mmty and just downloaded it. But I only have a 4GB card handy (from my Trinity.) I might be able to find my old 2GB one at home.
Edit: Well, this is what I just found: http://forum.xda-developers.com/showthread.php?t=308772&highlight=mtty+wizard
It seems that the IPL_SPL 3.08 might be a real problem. I'll try the card flash, but based on the above thread, I am not holding my breath.
If anyone has a suggestion or a solution, please let me know.
Thanks!
BTW, if the problem is indeed with the IPL_SPL 3.08, then perhaps the suggestion that we upgrade to it (in red) here http://forum.xda-developers.com/showthread.php?t=285435 should be removed, so that we don't get more expensive bricks.
Just to clear up the question about 3.08 IPL/SPL, it isn't an issue at all. It's been tested thoroughly to work well, better than 2.26.
TaurusBullba said:
Just to clear up the question about 3.08 IPL/SPL, it isn't an issue at all. It's been tested thoroughly to work well, better than 2.26.
Click to expand...
Click to collapse
After I unlocked my wizard and before I try any new ROM, I always burn the latest German wizard ROM with 3.08 IPL/SPL "ruu_vario_aku3.3_3822_382120_026911_tmo_de_ger_ship". Then I downgrade the Radio ROM to Cingular 2.25.11. Then I burn my ROM of choice. I've found it works best for me. I've never had a problem with 3.08.
TaurusBullba said:
Just to clear up the question about 3.08 IPL/SPL, it isn't an issue at all. It's been tested thoroughly to work well, better than 2.26.
Click to expand...
Click to collapse
What are the grounds for such a comparison? How to tell that an SPL works better than another? As far as i know the SPL is there to initialise the hardware and to apply security restrictions.
What i'd like to know is if anyone has been successful in downgrading IPL/SPL from 3.xx to 2.xx as itsme once said that there was a security in newer SPL's preventing downgrading (i must look for it...)
cheers
O.K., so maybe it's not 3.08, but something has sure gone bad.
I am trying to use mtty 1.1.42.538, but see only Port 1, Port 2 and USB. When I type in \\.\WSCUSBSH001 I get a message that it cannot open the \\.\WSCUSBSH001 port.
I tried resetting as described in message #7 here http://forum.xda-developers.com/showthread.php?t=264652&highlight=mtty1.42, but nothing happened.
I also tried choosing USB, then typed in r2sd all and again, nothing happened - I just get CMD> again....
So, can anyone think of anything else I can do, or should I just drop it from the 4th floor?
What IPL/SPL values you have at this moment?
mestrini said:
What IPL/SPL values you have at this moment?
Click to expand...
Click to collapse
Both ar 3.08, and I have the feeling that this is why I cannot flash the official Cingular ROM over what I have now. Which makes me wonder: is there an official Wizard ROM file combined with the IPL/SPL 3.08? This may at leas allow me to flash.
MacGuy2006 said:
Both ar 3.08, and I have the feeling that this is why I cannot flash the official Cingular ROM over what I have now. Which makes me wonder: is there an official Wizard ROM file combined with the IPL/SPL 3.08? This may at leas allow me to flash.
Click to expand...
Click to collapse
I had also upgraded my IPL/SPL to 3.08 -- up from the 2.25 on the newest Cingular ROM.
Anytime I've flashed to a WM6 ROM, I've been able to downgrade to the T-Mobile 2.26 ROM -- which changes the IPL/SPL to 2.26 -- with no problems before upgrading to a WM6 ROM. After flashing the WM6, I then go back in and upgrade the IPL/SPL once again to 3.08. It's not failed me yet.
O.K., I've spent the weekend screwing around with this:
If I run any of the original 2.xx ROMs, I get "you need an updated utility" message and then the utility goes to the "Exit" screen. (I am assuming this is because of the 3.08 IPL/SPL.)
mtty tells me I don't have permissions when I tried to load the ROM on a SD card (remember, the 8125 is not SuperCD-ed.). It also does nothing when I type "set 14 0" or "task 28."
But, I found that I can run the XDA Mobile 6 ROM (http://forum.xda-developers.com/showthread.php?t=310954) and it actually starts updating, but when it gets to 99%, the bar on the 8125 turns red and after a while the Update Utility tells me that the Wizard is not connected anymore.
Got very excited when I tried mattk_r's InGeNeTiCs' ROM(http://forum.xda-developers.com/showthread.php?t=311144): it started updating, went all the way to 100%, at which point the bar on the 8125 did turn red, however after a period of time the utility gave me the "Congratulations" message and told me I've successfully upgraded. But then, the 8125 reboots, and unfortunately, it still hangs on the boot screen, and it still gives the OS as 1.5.4.2. Have tried a number of times, always the same:-(
Oh, I tried upgrading the Radio only, and it worked: I was able to upgrade to 02.61.11.
So, does it seem like there is hope, and can anyone think of what else I can do?
MacGuy2006 said:
O.K., I've spent the weekend screwing around with this:
If I run any of the original 2.xx ROMs, I get "you need an updated utility" message and then the utility goes to the "Exit" screen. (I am assuming this is because of the 3.08 IPL/SPL.)
mtty tells me I don't have permissions when I tried to load the ROM on a SD card (remember, the 8125 is not SuperCD-ed.). It also does nothing when I type "set 14 0" or "task 28."
But, I found that I can run the XDA Mobile 6 ROM (http://forum.xda-developers.com/showthread.php?t=310954) and it actually starts updating, but when it gets to 99%, the bar on the 8125 turns red and after a while the Update Utility tells me that the Wizard is not connected anymore.
Got very excited when I tried mattk_r's InGeNeTiCs' ROM(http://forum.xda-developers.com/showthread.php?t=311144): it started updating, went all the way to 100%, at which point the bar on the 8125 did turn red, however after a period of time the utility gave me the "Congratulations" message and told me I've successfully upgraded. But then, the 8125 reboots, and unfortunately, it still hangs on the boot screen, and it still gives the OS as 1.5.4.2. Have tried a number of times, always the same:-(
Oh, I tried upgrading the Radio only, and it worked: I was able to upgrade to 02.61.11.
So, does it seem like there is hope, and can anyone think of what else I can do?
Click to expand...
Click to collapse
If I were you I might be talking to IMEI unlockers. Their process works from bootloader and might be able to get you CID unlocked and fix your corrupted CID area, which seems to be your major problem atm. In any case I would contact them and explain your situation and see if they think their software will unlock your phone. If so then you should be good to go once you CID is "uncorrupted" and unlocked.
one question: can You HARD RESET your device?
Do you have "format failed" message?
if so, you have 50/50 per cent for resurrection.
3.08 is not direct problem here anyway..., version is not exactly matter of problem...
(imei? now? lol)...
Thanks!
Yes, I can hard-reset fine and it claims to reformat fine.
Tx for the suggestion - I will contact IMEI (they unlocked my Trinity before the free unlockers were available
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.
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
licensedtoquill said:
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.
Click to expand...
Click to collapse
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
I've tried some of that: Now I'll do it properly
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.
I hope this is of some use to users who have this problem
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/
licensedtoquill said:
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/
Click to expand...
Click to collapse
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
Not sure I have simplified enough
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:
update
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)
Sorry to repost yet again
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
licensedtoquill said:
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.
Click to expand...
Click to collapse
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!
Pity no one seems to know the answer to this judging by the number of page views!
lou2ser said:
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.
Click to expand...
Click to collapse
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?
lou2ser said:
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.
Click to expand...
Click to collapse
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.
There may be another problem, - People dont like answering hardware problems here?
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?
licensedtoquill said:
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?
Click to expand...
Click to collapse
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
zabardast_1 said:
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.
Click to expand...
Click to collapse
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!
lou2ser said:
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!
Click to expand...
Click to collapse
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"
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.
lou2ser said:
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.
Click to expand...
Click to collapse
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
zabardast_1 said:
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
Click to expand...
Click to collapse
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.
lou2ser said:
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.
Click to expand...
Click to collapse
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"
First off, anyone on this forum who has contributed anything, I am have the deepest respect for, and my favorites will get donations as soon as I have money. Ok enough a$$ kissing.
So here is my problem:
I flashed it's right's TNT 6.1 19919 after hardspling. After many problems, like pseudo-hard resetting (turning off, losing all but 6% battery, and changing the date back to what it was originally i.e. 1/27/06) while in a phone call and doing the same while using the wifi, i hard reset and still the same problems occurred. so I undid the hardspl, so now i am back to 2.25.001 in the bootloader but when i connect it to the computer (winxp) to flash the original rom (cingular 2.25) it freezes at 91%. If anyone has had this problem occur or knows the solution as to get ANY rom back on it, IT would be greatly appreciated.
Also after doing some reading I tried to flash wizard love 2.26 to it and that freezes at about 50-60%. so I am stuck and it is really annoying.
Full 8 hour charge, restart computer, different usb port. Same happens: Error 302 Update Error
Hum... maybe when you reCID locked it, you put a CID that's not for that official ROM you're trying to flash. The misbehavior of the phone is due to the ROM you had, not the CID Unlock. If I'm not mistaken, you can hardSPL it again, from bootloader. Then you can try and flash any other ROM you wish. Give my ROM (WM5SE rev5 - if your phone can handle 240MHz - or rev4) a go, after you have CID Unlocked your phone.
My phone can take up to 273 but, all the roms i flashed were g4 safe.... because the ipl spl never changed and i checked them in shell tool . it gives me a update error 302 which wizard love documentation says that the "phone needs a new rom code" which implies that it needs to be taken to cingular, and i dont think i can lie that well. how would one "accidentally" put their phone into bootloader?
theblackhandx said:
First off, anyone on this forum who has contributed anything, I am have the deepest respect for, and my favorites will get donations as soon as I have money. Ok enough a$$ kissing.
So here is my problem:
I flashed it's right's TNT 6.1 19919 after hardspling. After many problems, like pseudo-hard resetting (turning off, losing all but 6% battery, and changing the date back to what it was originally i.e. 1/27/06) while in a phone call and doing the same while using the wifi, i hard reset and still the same problems occurred. so I undid the hardspl, so now i am back to 2.25.001 in the bootloader but when i connect it to the computer (winxp) to flash the original rom (cingular 2.25) it freezes at 91%. If anyone has had this problem occur or knows the solution as to get ANY rom back on it, IT would be greatly appreciated.
Also after doing some reading I tried to flash wizard love 2.26 to it and that freezes at about 50-60%. so I am stuck and it is really annoying.
Full 8 hour charge, restart computer, different usb port. Same happens: Error 302 Update Error
Click to expand...
Click to collapse
You have posted present IPL/SPL 2.25.001,is it 2.25.001 or .0001 ?
As you removed 'HardSPL',did you reflash the appropriate IPL/SPL regarding your phones official bootloader IPL/SPL...?
You shud do the 'HardSPL' again and either do the removal of HardSPL again correctly as instructed in the sticky ' How to remove HardSPL' or Flash any other Rom to recover.
Cheers!
no it was 2.25.001 just a typo. i think i will try these suggestions when i get home and i will post my findings.
Hi all,
I have been visiting these forums for 2 years now and have downloaded some great tools and ROMs to enhance my Trinity, however something all of a sudden has gone very wrong!
I upgraded to WM6.1 Elegance edition about 3/4 months ago, CID unlocked the phone about a month ago and everything has been working like a dream.
However just today, I attempted to turn the volume down on my phone during a meeting (I always forget to normally!) and there was no display. After few battery resets, again no display. It starts up, loads the the Elegance splash screens and then hangs on the screen before when the OS should appear.
My decision was to flash the ROM again. I cant flash using Activesync as it wont pick up on the hung screen, so I started the bootloader and got as far as 1% of the flash and it will restart. So I tried the SD Card method when resulted in a "loading" screen appearing for a few seconds and then it goes back to the standard bootloader and displayed a 00068002 error.
I am out of ideas, I hear mtty.exe is a good program for this kind of thing, but what I want to know is if this is fixable or if I should give up!
I have been working on this since 2pm today none stop!
Can any of you guys give me any suggestions please?!?!?
Kind regards,
Jonathan
Should be a cinch
Did you SPL the Phone before flashing roms?
If you put the phone into the bootloader mode The RGB screen and kill of activesync you should be able to run one of the flash update programs.
If I have flashing problems its usually Active sync so I kill it then run the flash program.
I've got a sneaky suspision your battery might be causing the problem.
Hi there, thanks for the reply. As I was new to upgrading I havent used SPL on the phone before flashing the ROMS. I did use an unlock tool recently as i wanted to try a different network SIM to see if it worked when I was in South America, so the phone is unlocked to all networks. Are you saying if I SPL now it should sort the problem out? If so how do I do this withour ActiveSync working - can you use SD?
Another thing I failed to mention was that when I start an upgrade and it follows all the steps, it doesnt say the current ROM on the screen where you press update ROM. It just gives the name of the new ROM and the current one is left blank.
I have disabled Active Sync before attempting the update. It seems to go through fine and then the phone restarts wafter 1% of the update.
What makes you think it is the battery? I am happy to spend under 20 pound on ebay if you think it will fix the issue!
try unbrick.bat.......my trinity was also stuck.......unbrick.bat save my day....
The same happened to me several time....I could not find a solution other than this one:
1. Flash the official HTC ROM.
2. Flash the required ROM then.
it works for my TrinTy.