Related
Guys,
I just tried to upgrade to a new ROM on my Cingular 8125. I have upgraded from the original rom to a Mr. Clean AKU 2.3 Rom a while back. This time I tried to load Ell's AKU 3.2 Rom.
Anyway, my computer locked and restarted during the flashing process (99%)
My phone turns on and shows the colored bar screen (is this called the bootloader?). This is all it does. I'm not sure how to try and fix this. I'd like to try and reflash a rom; however, if I try to do that I get Error 260. This error says it can't find the phone which is easy to understand since Activesync can't connect since the phone won't boot.
HELP!
SuperDodge said:
Guys,
I just tried to upgrade to a new ROM on my Cingular 8125. I have upgraded from the original rom to a Mr. Clean AKU 2.3 Rom a while back. This time I tried to load Ell's AKU 3.2 Rom.
Anyway, my computer locked and restarted during the flashing process (99%)
My phone turns on and shows the colored bar screen (is this called the bootloader?). This is all it does. I'm not sure how to try and fix this. I'd like to try and reflash a rom; however, if I try to do that I get Error 260. This error says it can't find the phone which is easy to understand since Activesync can't connect since the phone won't boot.
HELP!
Click to expand...
Click to collapse
i had this very proglem... TURN OFF THE PHONE ASAP.. as the bootloader screen will drain your battery very quickly.... reset computer and phone... plus in the USB cord.. and in the booth loader screen in the lower left corner.. you should see USB!!! just flash workin room.. and you should be set to go.. i believe>.
When I plug the phone in it does show USB in the lower left corner; however, The rom update utility can't see the phone.
Am I doing something wrong or should I be trying to install the rom in another manner?
SuperDodge said:
When I plug the phone in it does show USB in the lower left corner; however, The rom update utility can't see the phone.
Am I doing something wrong or should I be trying to install the rom in another manner?
Click to expand...
Click to collapse
hmmm i dont know... try restarting both devices.. other then that i cant hlep ya.. im still new to this...
USB means it is connected.
Again, keep the battery out when you aren't doing the flash. Reboot the PC in case the link is down.
Try flashing a stable ROM, like the Mr. Clean one you used before. Activesync doesn't need to operate, the ROM will see the wizard if the wizard says USB.
Zonealarm actually interferes with my ROM flashes, although it prompts me to see if it is ok; you might turn off your firewall prior to doing the ROM flash. If you do so, disconnect from the web.
I have also the same problem with my XDA 2 mini or the other called this the HTC Magician. I try to UPgrade my Radio 1.03 to 1.12. and when im applying the upgrade procedure the Upgrading stops and error. What happen now is my XDA 2 mini or HTC magician doesnt open now. only the word "SERIAL" and when i plug the USB, the word "USB" show on the screen................... Is there some one can help me pleasssse with my problem....
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.
Hello,
I`m trying to get latest lvsw wm6 to the device.
I own the phone since today.
I made the following steps:
Execute ROMUpdateUltility (Hard-SPL)
->Next->Next->Update
From: Image Version 1.16.407.2
to: Image Version 1.20
->Next -> Next
On the phone:
Enterbotloader.exe
"blabla"
YES
On the computer:
ERROR[246]: Device not responding
On the phone:
IPL-SSPL by Des
SPL-1.07.ds
ok,
trying to run ROMUPdateUltility again...
next next next... he shows me the progress bar --> finished! YES!
Rebooting the phone --> same software version as before the update?
trying to update for 2 hours... just to use gps as advertised
please help, i tried the official Update from HTC -> successfull but effects! programs, contacts etc still there, same version number!
messiah said:
please help, i tried the official Update from HTC -> successfull but effects! programs, contacts etc still there, same version number!
Click to expand...
Click to collapse
I've the same problem [246] upgrading unofficial roms like
GSM_1.41.00.11
and
ROM_ING_WM6_2.27
The only upgrade I make successfully is original
htcp3600-RUU_Trinity_HTC_ITA_1-23-408-2_103_6275_1-38-00-11_108
what's wrong ?
P.S.
I test it using activeSync 4.2 & 4.5
Messiah..... Have you read the very first post in the LVSW ROM thread?
I am NOT having ago, just checking, seems you may have miss-understood.
Grab ALL 3 downloads listed there.
Apply first one, and yes there IS NO real visible change to the phone apart from it has been hard SPL'd
Now apply Second one, will go through the same process BUT the Radio ROM is changed and updated
Now Apply the Third and WM6 is installed
The failure you describe is the computer dropping Activ Sync and then "seeing" the phone in Bootloader mode, which is why it take 2 bites of the first cherry, after that all "should " be ok.
I managed to get mine on the first attempt so it is "Me Proof"[TM] and "Just Works" (c)..... however report back if this hasnt helped
yeah, the process you described tells me that you've loaded hard-spl on your phone.. that's all. No WM6 yet...
I have the same problem.
I have Hard-SPL'ed my Orange M700
Then reboot and reestablish Active Sync
Then I have updated the Radio Rom
Then reboot and reestablish Active Sync
and now it's 1.41.00.11 in settings/system/device information
but when i apply
20070527_Trinity_WM6_v2.0.1.1 it uploads then i power on my device and it's still WM5 ?
What am I doing wrong??
Any help appreciated.
This may be a stupid question but have you SuperCID your device before running the updates?
If you go:
Start -> Settings
System
Device Information
What does it say under Radio version? (Just checks the second step has been completed successfully).
Also when you enter the bootloader what does it say on the screen?
akirainblack said:
This may be a stupid question but have you SuperCID your device before running the updates?
If you go:
Start -> Settings
System
Device Information
What does it say under Radio version? (Just checks the second step has been completed successfully).
Also when you enter the bootloader what does it say on the screen?
Click to expand...
Click to collapse
I thought you didn't need to SuperCID the device (http://forum.xda-developers.com/showpost.php?p=1245390&postcount=70)
My radio Rom shows 1.41.00.11
TBH I don't know. But it can't hurt to try it, I SuperCID mine and it flashes perfectly each and every time.
I'm merely trying to make suggestions that may get a result.
Oh, you didn't tell me what the bootscreen said and what version of Activesync do you have on your PC?
While doing the SuperCID upgrade i was wondering: After flashing any of the ROMs do I reboot or power On manually or wait for the device to reboot itself as the message in the SupoerCID tool suggests:
If radio upgrade went fine, wait until your phone reboots and make sure
ActiveSync is enabled again (you should see green icon in system tray)
Click to expand...
Click to collapse
Stupid Q: How can i make the boot screen stay long enough so i can write it down?
My ActiveSync is 4.5 on WinXP
Rummage around in Start--> Setting --> device ID, and version and stuff...... they are there and you get the same info as on the boot screen... and it stay on longer ;-)
Sorry if a little vague but away from phone at the moment......... erkkkkkkkk
/me runs off to find it so this may get edited
akirainblack said:
TBH I don't know. But it can't hurt to try it, I SuperCID mine and it flashes perfectly each and every time.
I'm merely trying to make suggestions that may get a result.
Oh, you didn't tell me what the bootscreen said and what version of Activesync do you have on your PC?
Click to expand...
Click to collapse
I didnt Super CID just followed the instructions in LVSW 's first thread, applied each DL in order and "it just works" (c)
Thanks. That's where i got the infroramtion from b4. I just thought it might be different in the boot screen.
I now did the SuperCID unlocking and did the 3 upgrades again. after the 3rd upgrade i still have:
- WM5.1.342 Build 15096.3.0.0
- ROM 1.23.61.5
- Radio 1.41.00.11
Q again: Do I need to wait after the flashing or do i immidiately press power
(that's what i do when it says finish) or do i soft reset? Or what else?
Thanks for your help.
Hmmmmm just got me phone....... dont ask
Right CE OS 5.2.1413 build 17745.0.2.3
ROM 2.0.1.1
Radio 1.41.00.11
Sooooo.......
a) are you using LVSW (just to be sure)
b) have you grabbed the latest version posted on page 1 of the upgrading thread?
c) I let it restart it self after it finished flashing, it then reclibrates the screen etc etc
Also looks like you havent upgraded anything just yet ... follow the instructions to the letter and it "should" be fine
a) yes
b) yes
c) there might be the problem i waited 2 mins ans as it wasn't rebooting i just used the power button. How long should i wait aftr the WM6 install?
I soft reset mine directly after the screen goes black. So that should be fine.
Maybe it has to do with my boot loader:
When i go to bootloader i see:
IPL-0.50
SPL-1.07.0000
then it starts fading quickly. is this normal? I have the same fading effect when i install ste 2 the radio ROM. but i still have the new radio rom on as it displays as 1.41.00.11
I again tried to use the 2.0.1.1 it uploads very quickly (maybe 2min) and then it's still the "orange" screen and WM5 on reboot and i still have all my data.
What a I doing wrong?
No. Mine stays there right up until the upload to the phone starts.
Then I get a grey background with a blue progress bar.
What happens if you run Enterbootloader on the phone. Then connect it to the PC.
Then run the install program on the PC.
The first process didn't work.
You should have:
TRIN100
IPL-SSPL by Des
TRIN100
SPL-1.07.ds
Hmmmmm if all else fails try a hard reset on your phone and see what versions of what you have after that.
Did you use ANY form of unlocking prior to using LVSW rom?
/me suspects this might be casuing issues
The radio rom zoooooomed up to my phone and likewise the WM6
I cannt remember reseting the phone after flashing.... IIRC it just worked as in it finished then re-started and way hey off it went.
Also FWIW I just used the DL's in the thread without bothering with anyother boot loaders etc... ie extract flies in first DL into 1 folders, run them, ditto DL's 2 and 3.
At 56%, the desktop went to a blue screen and said an error had occurred and the system must be restarted. The screen asked if I had installed any new programs, check with the adminstrator, etc. The only program recently installed is the program for this ROM revision. When it crashed, the phone had a completion bar in the top 1/3rd, showing 56% completion. The rest of the screen was white. I restarted the desktop and was unable to establish a sync connection. I then preformed a hard reset on the phone. When it restarted, it showed 4 color bars, red on top, green, blue and white at the bottom. Since I cannot restablish a sync connection, how do I finish the modification. I am now concerned that I have "bricked" the phone. I am reluctant to try this mod on another phone until I can determine what went wrong.
Adding additional info
My phone is a G3, CID and SIM are unlocked, desktop is using Windows XP, SP2 and ActiveSync is Ver. 4.5.0
phone isnt bricked, your getting into bootloader fine. you need to turn it on, get it into bootloader i mean. if needbe press camera and soft reset (power button) then plug it in USB. You then need to flash your phone with the operator ROM, or the ROM you want to flash it with. Your phone is by far bricked, G3 ones are really difficult to ruin. I learnt that first hand
http://forum.xda-developers.com/showthread.php?p=1560272#post1560272
Think I may have done just that...bricked my phone. G3 wiza200, IPL/SPL 2.26
Cannot get it to read a usb connection at all. Help please?? Thanks in advance
jphuffs said:
At 56%, the desktop went to a blue screen and said an error had occurred and the system must be restarted. The screen asked if I had installed any new programs, check with the adminstrator, etc. The only program recently installed is the program for this ROM revision. When it crashed, the phone had a completion bar in the top 1/3rd, showing 56% completion. The rest of the screen was white. I restarted the desktop and was unable to establish a sync connection. I then preformed a hard reset on the phone. When it restarted, it showed 4 color bars, red on top, green, blue and white at the bottom. Since I cannot restablish a sync connection, how do I finish the modification. I am now concerned that I have "bricked" the phone. I am reluctant to try this mod on another phone until I can determine what went wrong.
Click to expand...
Click to collapse
hi
ur phone is certainly not bricked,cuz ur desktop crashed therefore the phone upgrade cudn't be completed,nothing to worry as long u can get to bootloader mode(Tricolor Screen)
Ok,listen, u do not require active sync connection,to flash a rom,do as I say and it'll be working fine,follow these steps to complete ur upgrade:-
1.Switch on,go to bootloader mode (Tri colored screen).
2.Connect usb cable to the phone and PC
3. After connecting usb cable,u will notice small 'usb' showing on the corner at the bottom of the bootloader screen of ur phone,if it shows,ur r ready to flash and upgrade
4.start the upgrade RUU_ rom u want the to upgrade with
5. complete the flash,let it reboot
let me tell u,u dont need active sync connection to upgrade
cheers
akashastrega said:
http://forum.xda-developers.com/showthread.php?p=1560272#post1560272
Think I may have done just that...bricked my phone. G3 wiza200, IPL/SPL 2.26
Cannot get it to read a usb connection at all. Help please?? Thanks in advance
Click to expand...
Click to collapse
hi
i have read ur situation at thread u have mentioned here,well i can assure u it's not bricked,cuz as sometimes it's able to go to bootloader mode.
The only problem to me seems the usb connectivety problem.
does it charge ?,if not then clearly it' a usb connectivity,if u can manage to get another usb cable and check out,hope it wud clear this doubt
zabardast_1 said:
hi
ur phone is certainly not bricked,cuz ur desktop crashed therefore the phone upgrade cudn't be completed,nothing to worry as long u can get to bootloader mode(Tricolor Screen)
Ok,listen, u do not require active sync connection,to flash a rom,do as I say and it'll be working fine,follow these steps to complete ur upgrade:-
1.Switch on,go to bootloader mode (Tri colored screen).
2.Connect usb cable to the phone and PC
3. After connecting usb cable,u will notice small 'usb' showing on the corner at the bottom of the bootloader screen of ur phone,if it shows,ur r ready to flash and upgrade
4.start the upgrade RUU_ rom u want the to upgrade with
5. complete the flash,let it reboot
let me tell u,u dont need active sync connection to upgrade
cheers
Click to expand...
Click to collapse
I just had this happen to me as well, I got stuck a 29%
Now when I get to bootloader it shows the IPL 2.26 and SPL 2.26 and also a RUU in the top right hand corner. Plug in USB and I get USB at the bottom left but then when I try to launch the RUU with the rom I want to flash I Invalid update tool, download new tool... It wont "Verify information on the device"
**EDIT
Nevermind, I just got Titanium to take... I may be ok... I think the RUU in the vanilla download I got is messed up or something...
Currently ripping through the rom update now. Damn I just got this phone yesterday I was gonna be pissed if I killed it.
Okay, I have the tricolor screen with IPL 2.25 on the left top of the red bar, SPL 2.25 on the left bottom of the red bar, RUU on the right top of the red bar and USB on the bottom left of the screen.
I push the camers button, do a soft reset and launch the ROM update. First window says "Verifying information on your PDA phone. Please wait." After a few moments I get a window that says "ERROR (300) This update utility cannot be used for your phone. Please get newer update utility."
If I try again, I get a window with "ERROR (264) CONNECTION" And an additional message about the USB connection not working. I am using a USB charge/sync cable and not a cradle.
What now?
jphuffs said:
Okay, I have the tricolor screen with IPL 2.25 on the left top of the red bar, SPL 2.25 on the left bottom of the red bar, RUU on the right top of the red bar and USB on the bottom left of the screen.
I push the camers button, do a soft reset and launch the ROM update. First window says "Verifying information on your PDA phone. Please wait." After a few moments I get a window that says "ERROR (300) This update utility cannot be used for your phone. Please get newer update utility."
If I try again, I get a window with "ERROR (264) CONNECTION" And an additional message about the USB connection not working. I am using a USB charge/sync cable and not a cradle.
What now?
Click to expand...
Click to collapse
ok when u swith on the phone what happens ?
does it go to bootloader mood ? or u force it to go bootloader by keeping camera button pressed and doing soft reset ?
well,after geting to bootloader mode,don't reset again just establish usb connectivity and when it show usb in the lower part of the bootloader screen launch ruu and start the flash.if it still stops with an error,post that error,then it means u had a bad flash or no flash at all.are you pretty sure you got it CID unlocked ?
tell you what you do,go to this link download WST tool and apply it,than post the data info it gives here,this will give the present status of your phone,ok
http://forum.xda-developers.com/showthread.php?t=329170
read this sticky:http://forum.xda-developers.com/showthread.php?t=298613
jphuffs said:
Okay, I have the tricolor screen with IPL 2.25 on the left top of the red bar, SPL 2.25 on the left bottom of the red bar, RUU on the right top of the red bar and USB on the bottom left of the screen.
I push the camers button, do a soft reset and launch the ROM update. First window says "Verifying information on your PDA phone. Please wait." After a few moments I get a window that says "ERROR (300) This update utility cannot be used for your phone. Please get newer update utility."
If I try again, I get a window with "ERROR (264) CONNECTION" And an additional message about the USB connection not working. I am using a USB charge/sync cable and not a cradle.
What now?
Click to expand...
Click to collapse
download the wizar-love rom
flash it using the ruu provided..
ftp://xda:[email protected]_Novii+CF2.rar
it should work.....
read this sticky
http://forum.xda-developers.com/showthread.php?t=298613
G4.1 Does you're device start normally (yes) or is it stuck on the three-colored bootloader screen (no)? YES... go to step G4.4, NO go to step G4.2
G4.2 Turn off you're device totaly. Remove the SD card and disconnect the USB cable from you're device. Turn on the device while holding the camera button. You will get into bootloader mode (3 colored screen). Connect the USB cable to the computer and you will see USB at the bottom of your screen above the left softkey (Activesync will not connect in bootloader mode, but you can flash from this screen!). go to G4.3
G4.3 Download wizard_love rom and flash it to your device. Your device should startup again after doing this. Go to G4.4.
G4.4 Is your device CID-unlocked (note: it's not the same as SIM-unlocked!)? YES... go to step G4.7, NO OR DON'T KNOW go to step G4.5. (note: CID-unlocking a G4 is only possible by paying for it at imei-check!)
G4.5 Download enable-rapi.zip. Transfer Cert_SPCS.cab and EnableRapi.cab to your phone. Run Cert_SPCS.cab FIRST and EnableRapi.cab SECOND. Turn your device off and on or wait 5 minutes before soft resetting. Done? Go to G4.6.
G4.6 Follow this great thread by the-equinoxe: [solution] G4 SoftSPL Flash any ROM to CID locked G4 [UPDATED] and load the softSPL on your device using his method. Make sure you take a G4 safe rom (see the thread for details). After the steps you'll have the rom of your choise on your device!
G4.7 You're reade to flash the AKU2, AKU3, WM6 rom of you're choise IF the rom DOESN'T contain IPL/SPL. AKU3 and WM6 roms normally don't contain IPL/SPL. If you want to flash an AKU2 rom, make sure you take the G4 version. If you get an error 300 (invalid update tool) while trying to flash your device look at this thread!
NOTE: If you tried to flash a G3 rom with IPL/SPL in the rom on a G4 you probably will have a bricked device! DON'T flash the new 3.08 and 3.09 IPL/SPL to your G4!
NOTE2: If you got problems flashing with softSPL: Follow this great thread by mun_rus: Solutuion found: how to flash any rom to CIDLOCKED DEVICE. If your device won't start after flashing you can use step G4.2 and G4.3 and try again. Also look at this thread by eddieitman: Faria G4 Step by step installer with instructions to make sure you did all the necessary steps!
Crashed during flash
It has been suggested that I download Wizard Service Tool. OK, I did that. The Wizard Service Tool says to connect to ActiveSync. Can't do that. Phone is locked in Bootloader. It boots up into Bootloader. Any action requiring ActiveSync won't work as long as the phone is locked in Bootloader. Any suggestions as to procedures at this point. Remember, that trying to flash the ROM at this point, I get a message 300 that says I need to get a newer update utility.
Crashed during update
It has been suggested that I flash with wizar-love rom. Did that. Got a message 300, my phone need a newer update utility.
jphuffs said:
It has been suggested that I flash with wizar-love rom. Did that. Got a message 300, my phone need a newer update utility.
Click to expand...
Click to collapse
go to the G4 section and look for the HardSPL thread. Once there get the MUNRUU file from first post and use it with the ROM you wish to flash as it might do the trick of the ERROR 300
crashed during flash
It was suggested that I go to G4, first thread, HardSpl and down load file, munruu. Didn't find any such file. Went to second thread, by mun_rus, but was unable to download file.
My 8125 is locked in bootloader and I don' know what to do.
I still need help!!
jphuffs said:
It was suggested that I go to G4, first thread, HardSpl and down load file, munruu. Didn't find any such file. Went to second thread, by mun_rus, but was unable to download file.
My 8125 is locked in bootloader and I don' know what to do.
I still need help!!
Click to expand...
Click to collapse
this is the thread. and the link is there......
http://forum.xda-developers.com/showthread.php?t=332320
or another thread with link...
http://forum.xda-developers.com/showthread.php?t=334796
jphuffs said:
It was suggested that I go to G4, first thread, HardSpl and down load file, munruu. Didn't find any such file. Went to second thread, by mun_rus, but was unable to download file.
My 8125 is locked in bootloader and I don' know what to do.
I still need help!!
Click to expand...
Click to collapse
download latest Official Rom from carrier official site, establish usb connection while in bootloader flash,it will start working,after that follow the procedure of unlocking and upgrade
or if you have put in Sdcard,remove it and then switch on the device,it might get ok.It's seen in many cases that some Sdcards create problem while upgrade and bootloader screen gets stuck,by removing it,it starts to work fine
good luck
(mestrini;1565518]this is the thread. and the link is there......
http://forum.xda-developers.com/showthread.php?t=332320
or another thread with link...
http://forum.xda-developers.com/showthread.php?t=334796)
My phone is a G3. These links are pretty adamant about being for G4 only
jphuffs said:
My phone is a G3. These links are pretty adamant about being for G4 only
Click to expand...
Click to collapse
I'm talking about the, so called, 'MUN RUU' which are the files used to upload the nk.nbf. You just have to replace those for the ones you're using now; NOT THE nk.nbf, just the others...
zabardast_1 said:
download latest Official Rom from carrier official site, establish usb connection while in bootloader flash,it will start working,after that follow the procedure of unlocking and upgrade
or if you have put in Sdcard,remove it and then switch on the device,it might get ok.It's seen in many cases that some Sdcards create problem while upgrade and bootloader screen gets stuck,by removing it,it starts to work fine
good luck
Click to expand...
Click to collapse
What is "Official Rom from carrier official site"?
The SIM card was removed.
Hope this helps
jphuffs said:
What is "Official Rom from carrier official site"?
The SIM card was removed.
Click to expand...
Click to collapse
For instance, if you are (like me) with TmobileUS, go to the Tmo site and go to the page that gives you the download to rom 2.26. I have that rom, if you are with Tmo, but won't be able to upload it until later...
http://tmobile.infospace.com/tmweb/...wnloadCenter/DeviceDownloads.aspx?deviceID=24
THAT^^^ is for TMOUSA...it is the official Tmo rom. If you are with cingular/att, you need to access their website and download their official rom, etc.
I was attempting to flash my ROM to wm6 crossbow, I used Lokiwiz 02b to CID unlock my G3 wizard. Then, I attemped to flash the rom using the RUU. The Shelltool .exe never finished flashing the rom (even after 1.5 hours), so I disconnected the USB and tried to re-sync Windows Mobile Device Center (using Vista 32) as per the directions, but it would not detect the phone. I then entered bootloader mode and tried to run the RUU that way, but vista crashed the program if no sync connection is found. So, I downloaded the latest t-mobile ROM, and flashed the phone through bootloader (curiously the flash seemed to work using t-mo's RUU) and it installed to 100%. However, the phone will not get past the white splash screen. This is what it displays:
IPL 2.26
SPL 2.26
GSM 02.25.11
OS 2.26.10.2
I tried to un-rar the tmobile exe to a new folder and replaced the nk.nbf file with the file from the crossbow ROM. The t-mo RUU wouldnt read it properly and it crashed. Now the phone is sitting on my counter with it's battery pulled out for fear it mat discharge completely. Since i can get into bootloader mode with the "USB" display at the bottom, I know the device isn't bricked, but what can I do to get it up and running and hopefully flashed to wm6 crossbow? Thanks for any help!
snootch said:
I was attempting to flash my ROM to wm6 crossbow, I used Lokiwiz 02b to CID unlock my G3 wizard. Then, I attemped to flash the rom using the RUU. The Shelltool .exe never finished flashing the rom (even after 1.5 hours), so I disconnected the USB and tried to re-sync Windows Mobile Device Center (using Vista 32) as per the directions, but it would not detect the phone. I then entered bootloader mode and tried to run the RUU that way, but vista crashed the program if no sync connection is found. So, I downloaded the latest t-mobile ROM, and flashed the phone through bootloader (curiously the flash seemed to work using t-mo's RUU) and it installed to 100%. However, the phone will not get past the white splash screen. This is what it displays:
IPL 2.26
SPL 2.26
GSM 02.25.11
OS 2.26.10.2
I tried to un-rar the tmobile exe to a new folder and replaced the nk.nbf file with the file from the crossbow ROM. The t-mo RUU wouldnt read it properly and it crashed. Now the phone is sitting on my counter with it's battery pulled out for fear it mat discharge completely. Since i can get into bootloader mode with the "USB" display at the bottom, I know the device isn't bricked, but what can I do to get it up and running and hopefully flashed to wm6 crossbow? Thanks for any help!
Click to expand...
Click to collapse
Well Friend I hate to say it but Using Vista is your problem... The drivers in WMDC are different from those of activesync and thus Vista cannot talk to your phone in bootloader.
Follow this thread here:
Updated!!(10/20/2007) UPGRADE YOUR PHONE WITH WINDOWS VISTA!!! PROVEN METHOD!
Once you complete the steps in that thread, flash the Official T-Mobile Rom. I will be online for the rest of the night so I will walk you through everything if you would like me to. My AIM, Yahoo, and MSN messenger addresses are all at the top of every one of my posts.
First off, let me thank you for your help, as well as the time you have put in the community helping people like me. I had updated the driver before, but I guess several attempted flashed had overwritten the driver. Just now, I followed the link you gave me, updated the drivers, and flashed the T-mobile 2.26 ROM. The problem still remains. The RUU goes to 100%, shows me the finish/exit screen, mu wizard restarts, but hangs at the white boot screen and does not go any further.
Anyone? Need to get this phone up quick, as I am starting a new job soon and need the capabilities. BTW, i'm going to put XP on this laptop in dual-boot and see if I can get the t-mobile ROM to load fully using XP.
snootch said:
Anyone? Need to get this phone up quick, as I am starting a new job soon and need the capabilities. BTW, i'm going to put XP on this laptop in dual-boot and see if I can get the t-mobile ROM to load fully using XP.
Click to expand...
Click to collapse
If you can manage that, you will be set. All you have to do is create a hard drive partition and install xp to that partition.(from what I know anyway)
OK, i'm gonna try that (my internet is dropping every 5-10 secs, so it'll take a little time) I do have one question though- Last time I used Loki's unlocker, I unlocked the SIM, then the CID unlocker. After the CID unlocker, it locked me out of the phone. The OS wouldnt load unless I provided an unlock code. Then i reflashed it, then the problems started. I think i didn't have it CID unlocked properly. Plus having my miniSD in the slot probably didnt help things either. I've read the directions several times, and I dont see what i'm doing wrong. Could you maybe shed some light on what i'm doing wrong? Thanks!
EDIT: Also, I forgot to mention that I tried to do a hard-reset (hold wireless manager + voive command buttons + soft reset) and when you press the send button, it tells me unable to format FAT volume or something like that. Upon reading around, it seems like i'm having the exact same problem as this poster: http://forum.xda-developers.com/showthread.php?t=338315
snootch said:
OK, i'm gonna try that (my internet is dropping every 5-10 secs, so it'll take a little time) I do have one question though- Last time I used Loki's unlocker, I unlocked the SIM, then the CID unlocker. After the CID unlocker, it locked me out of the phone. The OS wouldnt load unless I provided an unlock code. Then i reflashed it, then the problems started. I think i didn't have it CID unlocked properly. Plus having my miniSD in the slot probably didnt help things either. I've read the directions several times, and I dont see what i'm doing wrong. Could you maybe shed some light on what i'm doing wrong? Thanks!
EDIT: Also, I forgot to mention that I tried to do a hard-reset (hold wireless manager + voive command buttons + soft reset) and when you press the send button, it tells me unable to format FAT volume or something like that. Upon reading around, it seems like i'm having the exact same problem as this poster: http://forum.xda-developers.com/showthread.php?t=338315
Click to expand...
Click to collapse
Although,many have successfully flashed using vista,but I'll suggest in your condition flash through WinXP. Download the official carrier's Rom from it's website.
1. Disconnect your phone from the usb cable,shut down any firewall,disable any Anti virus,Reboot your PC.
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. On your PC Open windows Task Manager...>Tab Processes...>wescomm.exe...>End process
4. Power off the phone completely (Not stand-by,shut off completely),or you may take the battery out for few seconds
5. Make sure your phone is not Connected to the PC via USB cable and remove the dummy Sdcard or mini-Sd card
6. Get your phone into Bootloader mode (Multicolor screen) by pressing camera button + Power on button
7. Reconnect your phone to the Desktop PC using the USB Cradle and the Charger MUST be Connected to the Cradle (Be sure that your battery is charged over 70%)
8. "USB"will appear on the bottom of the screen of the Bootloader (Multicolor screen)
9. Run the Upgrade again and it will work fine without any problems.
10.Never use Bluetooth sync for the Upgrade
While upgrading, the ActiveSync program will not go on, however the upgrade is running.Please be patient when you're flashing your device, even if 98%. It can wait a little bit, 5 ~ 7 minutes.
Don't cancell the flash or get the phone off the usb cable till it confirms "Congratulations" or stops with an Error!!!
Hope it'll recover back to it's default status,good luck
I'm going to assume I don't have to CID unlock it until I want to switch from the T-mobile 2.26 ROM? I am about to install XP dual-boot shortly. I'll post my results when it's done. Thank you.
snootch said:
I'm going to assume I don't have to CID unlock it until I want to switch from the T-mobile 2.26 ROM? I am about to install XP dual-boot shortly. I'll post my results when it's done. Thank you.
Click to expand...
Click to collapse
As long as you are going to keep T-Mobile 2.26 on your device or are restoring T-Mobile 2.26, you do not have to CID unlock but should you decide to change to another Rom, you will need to CID unlock.
Good luck on the dual boot. There is a detailed tutorial in my Signature if you would like to take a look at it. After I can restore my crashed laptop, I am going to take care of the dual boot also.(I have to do it again... )
I really want to put WM6 on my wizard, and customize it the way I want it. Do you have any favorite WM6 ROM? All day yesterday I spent trying to add a WinXP partition to my Vista laptop. Not fun. First, I shrank the only partition on the drive (where Vista is installed) using Disk management, the Diskpart.exe to create a new 2.5Gb partition to install XP on. I rebooted the labtop with a XP disk, and installed XP on the partition. After the laptop restarted the first time, it did not come back up (black screen, no CD activity), So I changed the boot options in BIOS to HDD, and the Vista partition responded with "Error loading operating system" on a black screen. So now, i've got a laptop with a corrupted Vista install, A partition with partially installed XP on it, a XP disk that just quits working, and my wizard is shot. Normally something I can deal with if I had my desktop, but unfortunately my entire house is packed up in storage, i'm living in a hotel, and the laptop and phone are all i've got. SO, against my better judgement, I went to the store and bought a Vista home basic upgrade DVD to fix my vista partition, and now i'm back on the net- and going to try anothe XP disk. Whew- what a pain in the ass.
snootch said:
I really want to put WM6 on my wizard, and customize it the way I want it. Do you have any favorite WM6 ROM? All day yesterday I spent trying to add a WinXP partition to my Vista laptop. Not fun. First, I shrank the only partition on the drive (where Vista is installed) using Disk management, the Diskpart.exe to create a new 2.5Gb partition to install XP on. I rebooted the labtop with a XP disk, and installed XP on the partition. After the laptop restarted the first time, it did not come back up (black screen, no CD activity), So I changed the boot options in BIOS to HDD, and the Vista partition responded with "Error loading operating system" on a black screen. So now, i've got a laptop with a corrupted Vista install, A partition with partially installed XP on it, a XP disk that just quits working, and my wizard is shot. Normally something I can deal with if I had my desktop, but unfortunately my entire house is packed up in storage, i'm living in a hotel, and the laptop and phone are all i've got. SO, against my better judgement, I went to the store and bought a Vista home basic upgrade DVD to fix my vista partition, and now i'm back on the net- and going to try anothe XP disk. Whew- what a pain in the ass.
Click to expand...
Click to collapse
It's better if you use 'PartitionMagic' software to create partition and install WinXp,as it has much advanced features as compared to built-in Disk Management.It also has the option to create a partition in the same one partition to install new OS.
I tried that first, too bad it doesnt work in Vista.
Woo Hoo!!! Success!!
Alright! I got it fixed! What I did:
1- Spent $42 on a CID unlocker from: http://www.imei-check.co.uk/m3000unlock.php
After i recieved the files from the via email (about 10 minutes) I ran their unlocker program with the file they emailed me. This CID unlocked the wizard.
2- I flashed button's ROM: http://rapidshare.com/files/18212239/CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE.exe.html
I had to flash it twice until it showed a IPL/SPL of 1.01
3- Followed this post: http://forum.xda-developers.com/showthread.php?t=276963&highlight=splash+screen+freezing
(make sure you use a blank SD card, as it will require you to format the card to make it useable again after your'e done)
4- Remove battery, and restart phone, BOOM! Button's ROM works fine!
5- Now upgrade to any ROM you like (WM6 etc.)
snootch said:
Alright! I got it fixed! What I did:
1- Spent $42 on a CID unlocker from: http://www.imei-check.co.uk/m3000unlock.php
After i recieved the files from the via email (about 10 minutes) I ran their unlocker program with the file they emailed me. This CID unlocked the wizard.
2- I flashed button's ROM: http://rapidshare.com/files/18212239/CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE.exe.html
I had to flash it twice until it showed a IPL/SPL of 1.05
3- Followed this post: http://forum.xda-developers.com/showthread.php?t=276963&highlight=splash+screen+freezing
(make sure you use a blank SD card, as it will require you to format the card to make it useable again after your'e done)
4- Remove battery, and restart phone, BOOM! Button's ROM works fine!
5- Now upgrade to any ROM you like (WM6 etc.)
Click to expand...
Click to collapse
Congrats ! that's the easy way.....
Yeah, I got tired of screwing with it, and I did it all in Vista!