Database Develop

k-jam, another brick in the wall (dead after rom update)

Hello folks,
Today I flashed with the ROM in thread 'T-Mobile USA 2.17 ROM (Custom)'. After it came up, I ran through the screen align and wizard. When it was all done installing extended rom etc it restarted on its own. After booting back up, everthing was really slow and there was no cell signal. The battery icon had an ! mark on it and when clicked, it says unknown battery. At this point everything keeps freezing and genrally not working including no activesync connection possible. I restarted into the bootloader and tried to flash again. It completed, but now I just get the tmobile boot screen, and eventually it restarts again, never completing the boot. This is when I notice that it doesnt seem to have a radio rom (GSM) version listed, but rather a gap where it should be. I ended up pulling the battery out and trying to get back into the boot loader again, and now I cant get it to power on in any way.
I guess that is enough said. The only other thing to note is that everything was working fine prior to the attempted update, I was merely hoping to get a performance boost, as I was using the original rom.
Any thoughts?
Thanks!
B. Ramsey

Fixed!
No other ROM would install, but in reading back through threads, I found a link to RUU_Prodigy_1081002_108_10910_TMO_US.exe. After installing this, I had my GSM rom back. Then everything worked. I think the not powering on issue had to do with the fact that it sat in the bootloader screen for several hours at one point. Since there was no standby, the battery was wasted. I am attempting to reflash it now to 2.17, we'll see.

No dice
After installing the 2.17 ROM, no more GSM, and same problems. I reflashed back to the previous and it works again..

Re: Fixed!
pterodyne said:
No other ROM would install, but in reading back through threads, I found a link to RUU_Prodigy_1081002_108_10910_TMO_US.exe. After installing this, I had my GSM rom back. Then everything worked. I think the not powering on issue had to do with the fact that it sat in the bootloader screen for several hours at one point. Since there was no standby, the battery was wasted. I am attempting to reflash it now to 2.17, we'll see.
Click to expand...
Click to collapse
THANK YOU SO MUCH for posting this! I also had a brick because of the same setup - trying to use the custom TMOBILE ROM. I had the same symptoms you did - basically non-responsive and no radio stack and no USB connection. I was not getting anywhere with any other ROM. Now, at least I have a working device.
Still no AKU2 though
Let me know if you manage to get an AKU2 ROM on your device!

That's worrisome. Do you know if the CID unlock was successful? (I think it's scripted into that custom upgrader)
If you're feeling adventurous, you could try intalling the custom 2.17 Cingular upgrader I made (it's on the FTP server). If that's successful, then the problem is with the T-MO upgrader. Based on all the folks having success with that T-MO upgrader though, I imagine the only issue might be a corrupt download. If the Cingular upgrader results in the same behavior, then the problem is either with the CID lock or some odd hardware problem.
I'm truly perplexed by the issue you're having..sure wish I knew how to help ya.

Thanks for the replies. My phone was already unlocked as it was purchased that way. I actually did get custom 2.17 tmo Rom to work, I just hadnt posted here yet. After flashing to the older rom, I flashed to the 2.16 Rom on clubimate.com. Then I had a working 2.16 with GSM. I figured what the hey and went ahead and tried the custom 2.17 Rom again. All is great, and FAST. I wish I could remember what custom Rom I was using before I think it must be the culprit. I cant remember, but it did have the extended rom free and open, total commander, and an unlocker.
Thanks

pterodyne said:
Thanks for the replies. My phone was already unlocked as it was purchased that way. I actually did get custom 2.17 tmo Rom to work, I just hadnt posted here yet. After flashing to the older rom, I flashed to the 2.16 Rom on clubimate.com. Then I had a working 2.16 with GSM. I figured what the hey and went ahead and tried the custom 2.17 Rom again. All is great, and FAST. I wish I could remember what custom Rom I was using before I think it must be the culprit. I cant remember, but it did have the extended rom free and open, total commander, and an unlocker.
Thanks
Click to expand...
Click to collapse
My device is a QTEK 9100. I was upgrading from the ROM on my device when I got it:
ROM 1.1.7.5 9/22/2005
Radio: 01.01.10
Protocol: 4.0.13.16
ExtROM: 1.1.7.105
My carrier is TMobile, so I figured the TMobile custom rom that was built off of the latest QTEK would be a good bet for me - but instead I ended up with no Radio.
I have the IMATE ROM you refer to - maybe I'll try to go to that as an interim step to get to the QTEK ROM I really want, since you had success with that method.
What I don't understand is why the Vanilla QTEK 2.17 (which is what I tried after the TMO Custom 2.17) gave me problems. I don't recall the exact error message, but basically it said it couldn't use that ROM on my device.

pterodyne said:
Thanks for the replies. My phone was already unlocked as it was purchased that way. I actually did get custom 2.17 tmo Rom to work, I just hadnt posted here yet. After flashing to the older rom, I flashed to the 2.16 Rom on clubimate.com. Then I had a working 2.16 with GSM. I figured what the hey and went ahead and tried the custom 2.17 Rom again. All is great, and FAST. I wish I could remember what custom Rom I was using before I think it must be the culprit. I cant remember, but it did have the extended rom free and open, total commander, and an unlocker.
Thanks
Click to expand...
Click to collapse
When you say it was already unlocked, don't you mean SIM unlocked? It would be unusual to buy a phone that is already CID unlocked.

I bought the unbranded k-jam from Simoncells.com. All I did was put my tmobile sim card in it and it worked. I guess I dont know the difference between SIM and CID unlocking.

Well theb that's where you went wrong, sim unlock refers to ur phone being able to use any world sim card...cid unlock refers to country Identification...if ur fone is not cid unlocked then wen u install foreign roms it will bugg up ur fone...dats wat happened to u and that other fellow pterodyne...I sim and cid unlocked my fone. ran the tmo 2.17 custom rom without a problem....plz do ur research on upgrading roms b4 u bash them...most factory fones don't come cid unlocked so I'd b surprised if urs did (tho it prolly came sim unlocked)...

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

SPL only downgrade

Folks,
Is there a way to downgrade just the SPL?
I'm having problems with a died wizard (mda vario) and my only hope is to get
a SPL downgrade from 3.08 to 1.X, so I'll be able to install again the T-mobile 2.26 rom.
My phone is totally killed at this moment and any help would be greatly apreciated!

Is there a way to flash another wm5 rom that works with IPL 1.x and SPL 3.08?
So I would be able to put the phone to work again, instead trying to downgrade SPL from 3.08...

T-Mobiles 2.26 should already downgrade it for you. I have my IPL/SPL upgraded to 3.08 and every time I get ready to flash a new ROM I load 2.26 first and it always downgrades it back to the 2.26 IPL/SPL.

Xeno,
When I try T-mobile 2.26 rom I got
"ERROR [296]: UPGRADE ONLY. The NBF file cannot be used for your PDA Phone. Please get another NBF file."

Ok, try this. Extract the nk file from the t-mobile rom update and then put that file in this flashing tools folder and then run the rom update utility in the folder and see if it solves your problem.
If you have the t-mobile rom in it's original form (a single exe file) and you don't know how to extract the nk file, that's actually very easy. All you have to do is use winrar, right click on the exe file and choose extract here and all the files will be extracted for you and nk file will be right there where you extracted it to.
By the way, I'm assuming that you are CID unlocked since you upgraded your IPL/SPL to 3.08.

Xeno1, thanx by the help,
Using original T-mobile 2.26 rom, it gives me File Read Error [238]
Now I'm Trying with wizard love rom, and its trying to flash
let's see what happens...sometimes my battery ends before finishing the flashing procedure, and I have to recharge again...(don't have cradle)

Hopefully the wizard love rom will work for you. Did you get that error using the flashing tools that I uploaded and the nk file from the t-mobile rom?

Oh, I just read your post in the did I kill the wizard thread. I didn't know you had an IPL of 1.xx and an SPL of 3.08. No wonder the t-mobile rom was doing that. The wizard love rom shoulkd be able to fix that for you.

Yes,
I'm using your flashing kit. First time the battery went down, so I'm trying again.
I tried this afternoon the Xda_MiniS_LaunchROM_v154102 rom too, and nothing happened (it flashed 100%, no errors at all). Just my IPL turned to 1.05, and the system didn't boot up.
EDIT
I don't know if my battery is damaged too, or the flashing procedure needs a lot of energy, but I had no lucky flashing this yet. The phone very often go back to the rainbow screen (showing a lose of battery power)

There seems to be a few people with an IPL of 1.05 and an SPL of 3.08 on here and all of them seem to have the same problem you're having. I'm not sure that the flashing tools that I gave you are going to help, but you can try them and see. It's worth a try anyway. Flashing the wizard love rom is what most people have been suggesting to do to fix it though. Did you try flashing the 3.08 IPL/SPL update aagain and seeing if that fixed it?

Nice idea about update again to 3.08,
So, this is a know issue? (having 1.X IPL and 3.08 SPL?)
Is there any known recovery procedure?
I did not try to do a 3.08 update again.
At this moment I'm recharging the battery, so I'll try one more time the wizard love rom, and can try to upgrade to 3.08 again as you said...

Trying to flash again the 3.08 update I got this:
ERROR[300]
These update utility cannot be used for your PDA phone. Please get newer Update Utility
Now I'll try the love rom again...
Any other ideas?
EDIT
I don't know if it is a battery issue or a problem with the love rom, because I've tried 5 times and got the rainbow screen at 55%, 85%, 96%, 99%, 100%, for example...I'll recharge battery for about 3 hours and give another try.
Any other good idea?

You could try using those flashing tools with the nk file in the 3.08 IPL/SPL update also and see if that works. I have a few more ideas to work on yet if those don't work.

Trying the 3.X flashing tools with wizard love rom I got the
message 300 (invalid rom, get new one..)
I still wanna try a full wizard love flashing, so we can try to conclude anything.
I'll go to sleep now, and will charge battery all night.
Tomorrow I'll give you the feedbacks...thank you Xeno1 for your help
We're almost there...

It's probably a good idea to give it a full charge before you start trying again. Heres another thing I thought of, I extracted just the IPL and SPL from the 2.26 rom and made a IPL/SPL 2.26 update for you.

Xeno1, you're a genius!
It worked!
I could not flash the wizard love rom, it's always stopped before the 100%.
I flashed your 2.26 ipl/spl rom, without hope, and it suddently started the chime!!!
Now my IPL is 2.26 and SPL is 3.08.... (the SPL didn't change anyway, but I'm glad the phone is back!!!)
Do you have a Vario MDA G3 wizard? I never could see(or even install) a WM6 on it, do you know if is it really possible? (I messed the things up trying to do that...)

Yes, I have a G3. I'm glad that worked for you. You still probably need to get your IPL ans SPL to be the same number. Running the 3.08 IPL/SPL update should be able to take care of that now.
WM6 is definitely possible on a wizard, It's been on my phone for about 2 months now. Before you flash to WM6 though, make sure you flash the whole t-mobile 2.26 rom back on it so that it has a good clean base.
Anyway, let me know how things go.

lotsa people make mistakes when flashing their rom for the first time and all.
whenever you start...when you use buttoms or love rom...BOTH your IPL and SPL should be 1.XX...before you start flashing back up. If BOTH are not 1.XX, you have to reflash with buttons or love, until they both drop down to 1.XX.
a lot of people don't read that part of the step...and seem to just flash with button or love once...have one number as 1.XX the other as 2.XX and then try to upgrade...lotsa times this causes problems.
in most cases, if you flash back down to 1.XX with buttons or love, and keep doing so til they are the same and then flash back up, things tend to work...otherwise...you can be screwed...

is it possible to flash wm6 right after flashing love rom with both ipl/spl 1.X, or should I do some other flashing before wm6?

If the WM6 ROM includes IPL/SPL, you can flash it without problem.
However if the ROM is OS only, you will get stuck at bootloader as WM6 requires 2.xx or IPL and SPL to load.

IPL doesnt change anymore! (1.01)

I have a CID unlocked wizard which has seen many roms, without any problems.
Lately I upgraded to IPL/SPL 3.08 and tried the touchflo rom.
Since it didnt work as expected, i presumed i needed to go back to the button rom before burning yet another rom.
Guess that was a mistake. I am now stuck on IPL 1.01 ! Whatever I do, cant get it to go to anything higher. Tried 2.26 IPL/SPL only, the full t-mobile version, the 3.08 again (which gives me spl 3.08 only this time), the german rom etc.
All that changes is the SPL. Tried installing enablerapi again, no result.
I can always get back to 1.01 IPL/SPL but THAT's IT ! NO other ROM works anymore!
What to do, what have i done....

You mean you can flash and work with Button ROM?
If so why not try to go from there to Qtek WWE 1.06, then 2.17 or 2.26?

tried flashing to 1.06 .. and got at 96% that the NBF was no good for my device.
However it changed the spl to 1.01.0000 instead of 1.01.

you should flash the buttom or love rom over and over again til you get both spl and ipl to 1.xx. people in the the threads have commented that sometimes it could take up to 8 flashes or more to eventually get it to work...dunno what causes it, but afterwards, flashing to a carrier rom should be fine...
good luck

Please read my first post.
I can get both IPL and SPL the same without a problem.
Both are 1.01 at that point.
I have been burning ROMs for a year now, so I know about this stuff already.
It must have something to do with going back from 3.08.
I have been on 3.08 both IPL and SPL dont forget!
At 1.01/1.01 IPL/SPL I still can not burn any ROM without error.
It wasnt like this before, have been on high numbers already.

after trying yet another operator ROM, gone back to IPL/SPL 1.01/Button ROM.
(shouldnt it say 1.05 btw?)
Button doesnt fully install anymore.. it gets stuck at about 98% after discobuttons.cab on the extended rom installation.
maybe that is a hint?
should i reinstall enableRAPI and cert_spcs before upgrading? my phone is cid unlocked for sure, and the service tool also says it is.
UPDATE: * installing xda mini..
* it got me 1.01 / 1.05
* reinstalling mini
* install also stops on signed discobuttons.sa.cab

d-lite said:
after trying yet another operator ROM, gone back to IPL/SPL 1.01/Button ROM.
(shouldnt it say 1.05 btw?)
Button doesnt fully install anymore.. it gets stuck at about 98% after discobuttons.cab on the extended rom installation.
maybe that is a hint?
should i reinstall enableRAPI and cert_spcs before upgrading? my phone is cid unlocked for sure, and the service tool also says it is.
UPDATE: * installing xda mini..
* it got me 1.01 / 1.05
* reinstalling mini
* install also stops on signed discobuttons.sa.cab
Click to expand...
Click to collapse
It means you can take it as far as installing extended_rom? Why don't you soft-reset the phone when the message of the 3 seconds appear?
if you're just installing button rom as a step to higher roms why the extended_rom? Simply forget about it and install 2.xx

No roms worked anymore, so tried ipl/spl 2.26 together with the installer from button.. it gave me 2.26 on spl again. NO change still on IPL.
IPL seems pretty stuck on 1.01.

in case it helps, are you flashing on windows xp or windows vista?

Here, try this. It's IPL/SPL 1.05 only. I'm not sure if it will work but it's worth a try.

It gives me 1.01 / 1.05 ....
trying multiple times .. hold on
tried 10 times.. ipl 1.01 spl 1.05
giving it few more tries on button
oh windows xp professional 32bit ..

trying love, buttong all in a row again.. still on IPL 1.01 SPL 1.01.
I think i found a new way to brick a wizard, goto 3.08 and back to 1.01
However, I think the phone not fully installing the extended rom must be a hint, since it usually had no problems with this.
Now on love and button, it stops at discobuttons.

Hate to tell you this, but I'm out of ideas at the moment. If I think of something, I'll let you know though.
Just a quick thought though, did you try removing the battery for about a half hour or so and then trying it again?

will leave battery out all night and try again tomorrow.
apart from the 'not being able to fully install extended rom' another thing that is remarkable is that the wizard service tool says I don't have a Wizard, after that however the info is correct (wiza200, cid unlocked etc).
further most ROM installers now crash at about 95% with error 320 saying the NBF is not made for my device.
is there anyone that has succesfully been on ipl/spl 3.08, down to button and up to 3.08again?
something else, the bootscreen doesnt show a GSM ROM version anymore, is that normal on ipl 1.01, could it be that i need to downgrade to certain gsm version ?
^$%#$ i dont think i can get the t-mobile service department to fall for my bricked mda excuses for a second time.
was pretty proud i got them to fix it for free first time i bricked it.. but this is different hehe....
(in case you wonder: 24volts made them not discover the cid lock, just created a bigger problem for the phone so they gave me whole new pcb.. i said the powersuply caused it )

The person that I was helping on that other thread successfully got his from 3.08 down to 1.01 and then back again. It wasn't easy, but getting theirs back up was a walk in the park compared to yours. I seriously hope that leaving the battery out over night does the trick because I'm pretty much at a loss as to what else to do.
It not showing a gsm version shouldn't be a big deal. You said that your rom installers are shutting down at 95% so it just may not be installing the radio, but your wizard should still operate without it. You just wouldn't be able to do any phone related things like make calls etc. but everything else should still work.
Don't worry about the wizard service tool saying that it isn't a wizard, it says that when I run it on mine too.
Just a thought, and definitely not a suggestion since you mentioned the 24v thing, do you have insurance on it? Accidentally dropping it in the bathtub might help solve your problem, not that I would ever condone insurance fraud or anything like that. All you would be out would be whatever your deductible is, although if your deductible is like mine it still wouldn't be cheap. I'd still give a little more time before doing anything rash anyway.

xeno1 said:
Just a thought, and definitely not a suggestion since you mentioned the 24v thing, do you have insurance on it? Accidentally dropping it in the bathtub might help solve your problem
Click to expand...
Click to collapse
good idea, but on the limit for this kind of thing for this phone as you can understand from the 24v issue
now at work, phone doing without battery all night... told him it is final warning, maybe taking his juice away will make him realise it is time to get to life

LOL Good idea. Tell it that if it doesn't decide to straighten up and start working you're going to run it over with your car. That ought to make it decide to work again'

So did it fix it?

oh man it got really angry with me.
on the wizardlove rom i had no radio @ all. but no charging or power info either!
you guessed it, been playing with wires and a 1.5v-12v powersupply set on 4.5v. Since it was doing it's paperweight imitation on me.
Got power back on 39%, going for a uuh 41% walk of my labrador.
Keep you posted.
Btw, extended rom in wst is unknown... is that any hint?
could protocol version be a hint?
next thing i try is flash another radio first, turn around the sequence.

Hmm, with the things that are hapening right now, no radio and the extended rom being unknown, I'm starting to think maybe the rom you're flashing has somehow become corrupted. You don't really need to worry about the ROM or the radio too much anyway, that shouldn't really have any bearing on whether you can get your IPL up or not. Try just flashing the 1.05 IPL/SPL update or the 2.26 update again and see if leaving the battery out for a while finally lets you upgrade it.

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??