Hi all, tried to upload my Wizard (8125) G4 to WM6 blackDiamont but it got stuck for more than 50 minutes with shellTool....
Now the phone is stuck on the screen that shows IPL/SPL, GSM and OS. From there i can force it to a hard reset but nothing happens..
Is there a way to get it working again or it just died?
marcelo1251 said:
Hi all, tried to upload my Wizard (8125) G4 to WM6 blackDiamont but it got stuck for more than 50 minutes with shellTool....
Now the phone is stuck on the screen that shows IPL/SPL, GSM and OS. From there i can force it to a hard reset but nothing happens..
Is there a way to get it working again or it just died?
Click to expand...
Click to collapse
Turn the device on and Flash the original ROM or Wizard Love Rom.
Wizard Love can be found here http://rapidshare.com/files/17792050/Wizard_Love_2.26.10.2_WWE_Novii_CF2.rar
Yeah, thanks man!
well, now trying to load Cingular's 2.25.11.1 WWE the update process got stuck in 95% and shows
error [326]: Invalid Command
This NBF file cannot be used for your PDA phone....
Is there possible that perhaps using Wizard love rom i'd have luck ?
marcelo1251 said:
Yeah, thanks man!
well, now trying to load Cingular's 2.25.11.1 WWE the update process got stuck in 95% and shows
error [326]: Invalid Command
This NBF file cannot be used for your PDA phone....
Is there possible that perhaps using Wizard love rom i'd have luck ?
Click to expand...
Click to collapse
You should be successful with Wizard Love. Good Luck!
Related
Hello,
Just flashed the Cingular 8125 to the new upgrade rom from the HTC site. All went okay but the 8125 hangs on teh startup screen the one that says
IPL 2.25
SPL 2.25
GSM 01.25.11
OS 2.25.11.1
won't go any furhter....... I did a hard rest but it says Format is Failed
I did another hard reset and it says Format is failed.
What is going on with this phone....
I even went into the bootlader by pressing the camera key.. It let me in so I flashed it again and it made it to 100% but the phone will not boot.
I tried to hard rest again and still the same result.
Is this phone dead?????????????????
As was explained to you in a prior thread, yes, the phone needs service. Asking the same question again does not change the answer. You either need to exchange it at the place of purchase or send it in for repair.
Prior thread: http://forum.xda-developers.com/viewtopic.php?t=53871
You have a hardware problem..
alynch75 said:
Hello,
Just flashed the Cingular 8125 to the new upgrade rom from the HTC site. All went okay but the 8125 hangs on teh startup screen the one that says
IPL 2.25
SPL 2.25
GSM 01.25.11
OS 2.25.11.1
won't go any furhter....... I did a hard rest but it says Format is Failed
I did another hard reset and it says Format is failed.
What is going on with this phone....
I even went into the bootlader by pressing the camera key.. It let me in so I flashed it again and it made it to 100% but the phone will not boot.
I tried to hard rest again and still the same result.
Is this phone dead?????????????????
Click to expand...
Click to collapse
Out of curiosity, have you tried the "Mr Clean" ROM? it's got a nearly empty extended ROM.
The error you're getting is in the attempted format of the fat filesystem which holds the extended ROM on the disk-on-chip. I wouldn't give up just yet.. =) But that's just me..
Mate thats exactly the problem I had with my wizard. I had to find another wizard (luckily at work lots of people had them) and create a backup of thier rom on to sd card. After that I reflashed mine with that image and my wizard started getting past the initial screen. I then reflashed with Mr Clean and promised never to touch it again (until another rom comes out of course :twisted: )Check my thread!
http://forum.xda-developers.com/viewtopic.php?p=304206
Good Luck!
does anyone know why this happens?
has anyone found a workaround?
i think this rom work well... i using about one week
most modern roms take 10-15 mins to pass from 98% to 100%...so wait...and wait...and wait...
Ditto
You gots to wait!
i should still wait 15 minutes after the computer says 100%
it has been 15 minutes and still at 99% how much longer
the update utility says congratulation! wtf
20 minutes and i am almost ready to flashback?
whats the problem? what roms haved you tried updating from i,ve tried
2.26 2.3 and 3.2 rc1?
both in the computer and the wizard it stay at the same number, if the computer finished be4 then there is a problem...
Whats your IPL/SPL version number?
had the same problem,
and wasn't patient :$
now i get stuck in the boatloader :s
another upgrade isn't a go since i itz not connected
to active sync?
is there a way out :s
haha, you don't have to be connected to activesync.
Just boot it in boot loader mode and plug it in. You can flash like that.
That's actually how I do all my flashes.
I am just on bootloader ...
itz stuck there :s
any reponse
i would like to try flashing again any ideas because it didn't work the first five times.
Me too
I have a G3 T-Mobile wizard (no .001), and it stuck at 99% with the PC version saying finished. I waited 25 minutes, gave up (there is a battery issue!) and reflashed with Molski's 2.26.
how can u flash it again?
I am in bootloader and stuck there no updates work nothing :s
prestonmcafee said:
I have a G3 T-Mobile wizard (no .001), and it stuck at 99% with the PC version saying finished. I waited 25 minutes, gave up (there is a battery issue!) and reflashed with Molski's 2.26.
Click to expand...
Click to collapse
If you have .0001 then you have a G4 Wizard and NOT a G3 Wizard.
Molski
no no
molski said:
If you have .0001 then you have a G4 Wizard and NOT a G3 Wizard.
Molski
Click to expand...
Click to collapse
Yes, but I have "no .001", which should have been "no .0001".
Is your rom the same as T-Mobile 2.26 if I don't install the extended rom? (I install my own extended rom manually.)
Kartboy: As goldrush98 said, you don't have to be connected to activesync. If you see "usb" on the tri-color bootloader screen, just start the rom flash program and it will flash the new ROM. Worked for me.
please stick to topic
the topic is ell AKU 3.2 rom 99% crash not ell AKU 3.2 rom ipl/spl
i do not think the crash has to do with ipl b/c i know i have a G3
where is the developers response
Same issue here.
I have the same problem here. Mine gets to 99% on the phone and the computer says it's done. I've waited over an hour for the phone to finish.
Hello, I've tried to upgrade my Qtek 9100 G3, the flashing finishing with success, but when I start the phone it doesn't load windows, I can see the splash screen, and then the screen become completely white.
I follow the faria instruction, and tried to install the wizard love ROM from bootloader screen, but I have error 300, "Strumento di aggiornamento non valido" that in english mean Update device not good..
Please, help me!!
finger roll said:
Hello, I've tried to upgrade my Qtek 9100 G3, the flashing finishing with success, but when I start the phone it doesn't load windows, I can see the splash screen, and then the screen become completely white.
I follow the faria instruction, and tried to install the wizard love ROM from bootloader screen, but I have error 300, "Strumento di aggiornamento non valido" that in english mean Update device not good..
Please, help me!!
Click to expand...
Click to collapse
1.- I don´t think you have a G3 because de IPL/SPL you posted, but is very strange that Wizard Love RUU reported such error in a G4
2.- What kind of upgrade you wanted to do?
3.- Reflash your original ROM if you have it available.
Mod edit: Please refer him to the wiki before posting such information.
Yes, I have a G4 phone, you can see on my sign, but my friend with the phone broken have a G3, and now he can install any kind of rom, the important it's that it works.
So.... problem solved?
finger roll said:
Yes, I have a G4 phone, you can see on my sign, but my friend with the phone broken have a G3, and now he can install any kind of rom, the important it's that it works.
Click to expand...
Click to collapse
Good for him! And how did he recover his phone? What did your friend do?
No he don't solved the problem, with any kind of ROM he's tring to install he get the same problem "error 300": invalid upgrade Tool!!
Please, do you have any idea?
Madcap180 said:
he has a G3 .. 2.17 I beleive is G3... Anything above 2.21 is G4 I beleive.
Click to expand...
Click to collapse
This is WRONG... PLEASE Don't post information like this unless you are positive of what you are saying as this could cause people to brick their phones.
Its explained in numerous places how to determine this, but this post is one of the best for overall information on determining your phone type and how to flash and recover from flash issues:
http://forum.xda-developers.com/showthread.php?t=298613
Madcap180 said:
he has a G3 .. 2.17 I beleive is G3... Anything above 2.21 is G4 I beleive.
Click to expand...
Click to collapse
Mine is a G4 (2.25.001) The trailing 0001 is what so far has identified a G4
when I was first trying to flash my phone I read anything 2.21 and above was a G4... so perhaps I READ the wrong information.
I got lost buddy
finger roll said:
No he don't solved the problem, with any kind of ROM he's tring to install he get the same problem "error 300": invalid upgrade Tool!!
Please, do you have any idea?
Click to expand...
Click to collapse
Could you provide the specifics of your friend´s phone?
* IPL / SPL (Current and original)
* Original ROM
* What ROM he was flashing when he got for the first time the white screen?
mfrazzz said:
This is WRONG... PLEASE Don't post information like this unless you are positive of what you are saying as this could cause people to brick their phones.
Its explained in numerous places how to determine this, but this post is one of the best for overall information on determining your phone type and how to flash and recover from flash issues:
http://forum.xda-developers.com/showthread.php?t=298613
Click to expand...
Click to collapse
The brick phone is a G3 with 2.26 IPL and SPL, from the T-mobile ROM. He brick the phone installing the prekitchen ROM from Faria.
Now Following the faria instruction, he would like to flash with wizard love rom, but he get the wrong update tool error. Did you know if there are some other possible solution?
In booloader mode, when I connect to the usb, in the phone screen appear USB, so I think that the phone it's not completely gone.
finger roll said:
The brick phone is a G3 with 2.26 IPL and SPL, from the T-mobile ROM. He brick the phone installing the prekitchen ROM from Faria.
Now Following the faria instruction, he would like to flash with wizard love rom, but he get the wrong update tool error. Did you know if there are some other possible solution?
In booloader mode, when I connect to the usb, in the phone screen appear USB, so I think that the phone it's not completely gone.
Click to expand...
Click to collapse
You´re right, if you have the tricolor screen and USB connection you´re safe, no worries!!! We can save it!
Have you tried the original T-Mobile? This one should do it, if you don´t succeed with the original ROM you may try Wizard Love but you have to use the right RUU, in this case pull de nk.nbf file from the Wizard Love and put it into the folder were the original T-Mobile RUU is (this would replace the original T-Mobile nk.nbf with the one from Wizard Love), then execute the original T-Mobile RUU with the new nk.nbf of course your Wizard connected to the PC, remove miniSD card (if any) and make sure you dissable the activesync connection
If my explanation sounds confussing for you, check this:
http://forum.xda-developers.com/showthread.php?t=294107
Good luck!
Thanks, I downloaded the T-mobile ROM, insert the love ROM nk.nbf and tried to upgrade...I get this error message:
Error 238: File Read
So, I extract the T-mobile, and launch the RUU directly, using the t-mobile nk.nbf, and not the wizard love one.
Now I'm flashing!!!!
Good for you!
finger roll said:
Thanks, I downloaded the T-mobile ROM, insert the love ROM nk.nbf and tried to upgrade...I get this error message:
Error 238: File Read
So, I extract the T-mobile, and launch the RUU directly, using the t-mobile nk.nbf, and not the wizard love one.
Now I'm flashing!!!!
Click to expand...
Click to collapse
Excelent!! I´m glad you had fix the problem!
I was upgrading my t-mobile 8150(?) the k-jam with the new windows mobile 6 and in the middle of it my comp crashed!! now i am stuck at the bootloader mode (3 colored screen) and when i try to redo it i get to 99% and get a 302 error message. i follow the instructions given but keeps going in circles. its a G3 so is my phone bricked or is there a way to save it? i've been looking at this site all day but am now just more confused. lol thanks for your help!
No your phone isn't bricked. As long as you can get into the bootloader screen you should be ok. What you need to do is flash an official carrier rom either tmobile 2.26 or wizard love rom after you that than you can reflash to wm6. look at the stickies in the wizard forums that is where you can find these roms.
Thanks for the info but seems my techno curse continues. I tried the wizard love rom but it was in a different language and whem i tried the tmobile 2.26 i got "error 274 connection." Any more suggestions? Again thanks soo much for an issue I'm sure has been posted here a thouand times.
This happens to me all the time. I always use the Cingular 2.25 rom, it works perfectly and I have an I-mate K-JAM. Then, do the WM6 upgrade, but ensure all of your Norton and Antivirus and background running apps are shut down. Good luck.
yes also take out your mini sd card if you have one. even though its in another language it will work. "AVANTI means next. so just keep hitting that and you will be fine.
hmm been trying to d/l the Cingular 2.25 rom but the link seems to have stoped working...
It;s aaaaaaaaaaaaaaalllllllllliiiiiiiiiiivvvvvvvvvvvvvvvvveeeeeeeeeeeeeeeee!!! for now lol Lets see what happens after i install wm6 I couldn't get the cingular rom but i had already dowbloaded the button rom i found here earlier and it worked like a dream!! quick and easy!! thank you all soooooo much!
hi all. one more little thing. after adding the new rom to get it back to life, now the numbers don't match so i can't upgrade to wm6. i have ipl 1.01 spl 2.26. advice?
flash to the tmo 2.26 or cingular 2.25...that will give you an IPL/SPL of 2.xx
then, you can flash to WM6
i want to delete this message. can't find a way to do it.
there's any other way to flash without usb cable?? sorry to bug in this thread but i lost my usb connection somehow and did a hard reset and still doesn't work. my phone charges. and no is not my computer cuz my wifes phone same as mine does sync i have a tmobile mda also known as the cingular 8125.
fallon75 said:
hi all. one more little thing. after adding the new rom to get it back to life, now the numbers don't match so i can't upgrade to wm6. i have ipl 1.01 spl 2.26. advice?
Click to expand...
Click to collapse
keep reflashing buttons rom until both ipl/spl are the same number. if they are different, then the flash didn't complete correctly. (it happens often, so it's kinda normal). just keep reflashing. after both ipl/spl are the same, then CID unlock and then update to an official carrier...then flash a wm6.
can anyone help me??
Check if "USB" displayed when in bootloader mode (Camera+reset) with Wizard connected to PC.
If so, you may try to flash another ROM through bootloader.
starkwong said:
Check if "USB" displayed when in bootloader mode (Camera+reset) with Wizard connected to PC.
If so, you may try to flash another ROM through bootloader.
Click to expand...
Click to collapse
it does shows but how can i flash?? it still won't connect o my pc. my pc doesn't recognize it. but it does recognize my wifes phone.
Try to run RUU straight with Wizard connected and running in bootloader mode
i have a cingular 8125
Ipl 2.26
spl 2.26
i was upgrading my rom and it stopped at 36% and now it is stuck in bootloader mode. i have tried to load other roms however it will not. it sounds like its connected but when i run a rom it says its not connected. i have tried many times and i do not know what to do! please someone help me!!
NVM i got it to work!! the problem was a soft reset that i did not do before hand!! i cant believe it was such a simple mistake!