ell AKU 3.2 rom 99% crash - 8125, K-JAM, P4300, MDA Vario Software Upgrading

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.

Related

Did I kill the Wizard? :-(

[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

ROM flash gone wronge! help!

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

did I brick my phone? :(

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!

Downgraded NBD to Button, then tried to upgrade to Cingular ROM, but getting errors

Have a G3 unlocked Wizard (Cingular 8125).
Have been running different ROMS to see which one I like.
Recently stayed with NBD 8.0 for a while.
Last week battery went to heck, apparantly during a reflashing.
Probably due to the battery, I could never reflash and would always get
stuck in bootscreen @ 98%, no matter how long I charged the battery
(using stock charger and battery in-phone.)
I purchased a cradle battery charger and a new battery from ebay (which works great BTW).
Now I can flash... I think.
I managed to flash in "Xda_MiniS_LaunchROM_v154102" and my phone works.
I even got caught up on my voicemails. But every time I try to
upgrade to stock Cingular or T-Mobile, the RUU says incorrect ?nk.nbf? file.
(The actual ROM file).........What gives?
This is what comes up upon bootup.
ipl-1.01
spl-1.01
gsm-1.12.10.0
os-1.5.4.2
I'm using an XP machine with ActiveSync 4.5. Never had a problem
re-flashing before. I tried looking through the threads without success.
Any help would be appreciated.
i was going to say try that xda mini rom. thats what fixed my problem , then i was able to flash a tmobile rom. then tne wm6.
http://forum.xda-developers.com/showthread.php?t=298613 I used this thread. try the tmobile rom on g3.7
joihan777 said:
Have a G3 unlocked Wizard (Cingular 8125).
Have been running different ROMS to see which one I like.
Recently stayed with NBD 8.0 for a while.
Last week battery went to heck, apparantly during a reflashing.
Probably due to the battery, I could never reflash and would always get
stuck in bootscreen @ 98%, no matter how long I charged the battery
(using stock charger and battery in-phone.)
I purchased a cradle battery charger and a new battery from ebay (which works great BTW).
Now I can flash... I think.
I managed to flash in "Xda_MiniS_LaunchROM_v154102" and my phone works.
I even got caught up on my voicemails. But every time I try to
upgrade to stock Cingular or T-Mobile, the RUU says incorrect ?nk.nbf? file.
(The actual ROM file).........What gives?
This is what comes up upon bootup.
ipl-1.01
spl-1.01
gsm-1.12.10.0
os-1.5.4.2
I'm using an XP machine with ActiveSync 4.5. Never had a problem
re-flashing before. I tried looking through the threads without success.
Any help would be appreciated.
Click to expand...
Click to collapse
It may be the RUU you are using. Try flashing the Cingular rom using one of the RUUs I attached below. I personally have never had this problem before so this is my best suggestion.
Is it possible that somehow it got re-locked????
Also, evrytime I try to upgrade out of 1.05 ROM the RUU process stops at 85% and then says nk.nbf not for this PDA.
No, except you didn't have a successful CID-unlock (e.g. Unlock when IPL and SPL is 2.xx, and flashed to WM6 using ShellTool, then you think that you have been unlocked, which is actually not)
Update: Even though I haven't been able to load the official Cingular ROM or
the T-Mobile 2.26 ROM, I HAVE been successful in loading NBD 8.0.
I DON'T GET IT!!!!! Why would NBD load but official carrier ROMs get stuck at 85%?
Although my G3 is is currently working again, I'll still do some more experimenting.
I don't know what an extended ROM is, but I wonder if mine was corrupted
during the power failure when attempting to downgrade last week from NBD to Cingular?
I'll post my results hoping this will help others.
Edit: An hour later- I tried another official WM5 ROM form HTC, no dice. Froze @ 85%
just like the other WM5 Official ROMs. On a hunch, I tried to install the newest NBD 9.2.
IT WORKED! WHY can I install NBD ROMS but not Official WM5 ROMs?
Now the first splash screen is the *dated* green stepped graduated green from 1.05. The current info:
IPL- 2.25
SPL- 2.25
GSM- 02.25.11
OS- 6.0.0.0
Itai! This is tough!
EDIT: OK, it's now 4am and I'm seeing double....
Tried Wizard Service Tool, a very efficient program by mestrini.
Apparantly, my extended ROM was hidden. So the WST unhid it. Now we'll see what this does.
According to WST, there was no pagepool found in WM6 or WM5 location.
Could this be why WM5 updates didn't work?
4:22am, even cat gave up on me...
Sorry if I missed something here, but if you have a CID Unlocked phone and you downgrade back to a 1.xx IPL/SPL, then you will be CID Locked again when you upgrade. Anytime you downgrade to 1.xx you have to redo the CID Unlock process while you are down there before going back to IPL/SPL 2.xx or higher.
So redo going back to the Button rom, do the lokiwiz unlock, make sure both IPL/SPL are 1.xx (so you may have to flash button a couple of times) then upgrade to Cingular, T-Mo or whatever official 2.xx rom.
joihan777 said:
According to WST, there was no pagepool found in WM6 or WM5 location.
Could this be why WM5 updates didn't work?
4:22am, even cat gave up on me...
Click to expand...
Click to collapse
Page Pool is set in ROM image, not hard-coded in hardware.
mfrazzz said:
Sorry if I missed something here, but if you have a CID Unlocked phone and you downgrade back to a 1.xx IPL/SPL, then you will be CID Locked again when you upgrade. Anytime you downgrade to 1.xx you have to redo the CID Unlock process while you are down there before going back to IPL/SPL 2.xx or higher.
So redo going back to the Button rom, do the lokiwiz unlock, make sure both IPL/SPL are 1.xx (so you may have to flash button a couple of times) then upgrade to Cingular, T-Mo or whatever official 2.xx rom.
Click to expand...
Click to collapse
Didn't work. I'm certain I'm unlocked, both by lokiwiz program saying so and
Wizard Service Tool saying so. After the unlock I was successfully able to
load NBD 8.0 & NBD 9.2 ROMs, but not the official T-Mo/Cingular WM5 ROMs.
WST found the pagepool completely missing in both WM5 & WM6 sectors.
The extended ROM was also hidden. Both of those items have been corrected
so later today I'll redo the entire process just to make sure all is well.
starkwong said:
Page Pool is set in ROM image, not hard-coded in hardware.
Click to expand...
Click to collapse
Thanks. More clues to this puzzle!
Try flashing the empty extented rom. Most new roms don't have extended roms, so if your extended rom is corrupt it may be keeping wm5 to load. Which explains why NBD roms work.
goofeyass said:
Try flashing the empty extented rom. Most new roms don't have extended roms, so if your extended rom is corrupt it may be keeping wm5 to load. Which explains why NBD roms work.
Click to expand...
Click to collapse
Thanks, I just now tried this approach. I used mestrini's Wizard Service Tool to 'format' the extended rom. As of this moment I've just downgraded to Button 1.05 ROM and going to use lokiwiz's unlocker.
There is a rom out that will flash an empty extended rom without changing anything else.
http://forum.xda-developers.com/attachment.php?attachmentid=42076&d=1182515673
I have formatted the extended rom.
Then I tried to redo the Button-->Unlock-->T-Mo 2.26.
Still process stops at 85% when installing T-Mo ROM!!!
Also, the splash screen doesn't seem to be working?
goofeyass said:
There is a rom out that will flash an empty extended rom without changing anything else.
http://forum.xda-developers.com/attachment.php?attachmentid=42076&d=1182515673
Click to expand...
Click to collapse
How long are you waiting when its at 85%. I've had them stay at 85 % for over 5 minutes before.
I would recommend flashing ---->http://forum.xda-developers.com/attachment.php?attachmentid=42076&d=1182515673
???
in my opinion it is a waste of time to downgrade to flash a new/original rom...i've flashed about 100 or so roms since late 2005, multiple devices, jumping from carrier rom to latest wm5/6 builds..never had an error.
Do what you like of course, im just saying save 10 mins and flash straight to whatever you're wanting to try. goodluck and happy flashing
BTW like I said before... for those of you with dual/quad core procs, try putting the romupdateutility.exe on real-time priority and check it, I flash in roms in less than 3 mins, everytime, no errors
goofeyass said:
How long are you waiting when its at 85%. I've had them stay at 85 % for over 5 minutes before.
I would recommend flashing ---->http://forum.xda-developers.com/attachment.php?attachmentid=42076&d=1182515673
Click to expand...
Click to collapse
Is there a correct method for using those files? I installed them to the Wizard's Windows/ Startup directory & rebooted. They sorta ran, but when I checked the extended ROM with WST, it reported the extended ROM was empty =)
Now I'll go around again Button 1.04-->Lokiwiz Unlock-->T-Mo 2.26
goofeyass said:
How long are you waiting when its at 85%. I've had them stay at 85 % for over 5 minutes before.
Click to expand...
Click to collapse
Good point... HOW long are you waiting. If you are doing an RUU, you should just let it run. Official roms will "Hang" at 85%, and I've had them hang for over 5mins before also, but they always finish.
As someone used to post, you should start the RUu, then head to the kitchen, go get coffee, a snack, whatever. Just ignore the flashing process until its done...
mfrazzz said:
As someone used to post, you should start the RUu, then head to the kitchen, go get coffee, a snack, whatever. Just ignore the flashing process until its done...
Click to expand...
Click to collapse
Very well said. Lol. It's true though. If you just ignore it, it will seem to go faster. I noticed the same thing too. If you are flashing an official rom, it will almost always stop at 85%, sometimes for a long time... Just let it go and it should eventually finish.

Wizard stuck on three-colour screen IPL/SPL after attempt to unlock

I have a wizard (wiza110) running wm5 and i wanted to upgrade it. It was the first time i was trying such thing. I was following these instructions http://wiki.xda-developers.com/index.php?pagename=Wizard%20Windows%20Mobile%206%20for%20newbies. My device is g3. My first attempt was with Button Rom, everything was fine until 99%... i think it was error 302 or something. I took off the battery and plugged it again several times but nothing came out. I had the three-colour screen.
Then I tried The Xda_MiniS_LaunchROM_v154102.exe, still nothing, lokiwiz also...
Last attempt was with wizard Love. USB appears but the ruu can't see the device and stops the process
Any ideas?
i think the device was sim-unlocked...
Flash back to the original rom, charge the battery to 100%. Make a guest connection to windows and start reading this thread from the beginning
do you have a link for the original rom? the thing is that ipl is 1.05 and spl is 2.25
aposperitis said:
do you have a link for the original rom? the thing is that ipl is 1.05 and spl is 2.25
Click to expand...
Click to collapse
Based on my experience and what I've read here, I'm guessing that your original rom had ipl and spl both 2.25. When you installed the button rom, it updated the ipl but nothing else. Just a guess, but that's what happened to me the first time on my G3. I just re-flashed button rom and continued from there. You should try to find the original rom for whatever kind of phone you have (I mean, the rom from the service provider like Orange, AT&T, etc). Their latest rom might not be 2.25. For example, my phone originally came from T-Mobile. I have the T-Mobile rom that is I think 2.26. I keep it handy, but have only reflashed back to that rom once when my extended rom got messed up.
Read the link suggested above. Good stuff. It is possible to flash a phone that is stuck on the tri-color screen, but it might not work the first try.
Same thing here, just youre getting further
I have ipl and spl on 2.26 received it this way. It's G3. I've been a week looking through the forums. Trying to avoid posting here. But damn it. I can't seem to get anything right. I previously had the G1 and Juno, Flashing was a breeze. But here i feel lost.
Basically my problem is i can't get it to downgrade. upgrade. CID unlock, With neither Lokiwiz or WST. A pain. And really NO RUU runs past the 0% it reboots my phone to boot loader image and USB shows but it reads that it can't find my phone anymore. It's been charged to 100%. Deleted TEMP folder. Was guest under activesync. Changed my USB cables 10 times. It's frustrating. Please. Any suggestions??

Categories

Resources