I've been trying to upgrade my 8125 ROM from the original 1.8.11. I ran the 2.2 upgrade and everything except the ROM had new numbers. Next I tried 2.3 and the same results.
I then followed the instructions to downgrade, run Lokiwiz and then upgrade. Now I'm stuck with a 1.5 ROM while everything else says 2.25..
Any suggestions?
My bad!
Oops! My bad - I was entering U and not C on Lokiwiz so I wasn't doiing a CID unlock. Just finihsing the process and it looks like it's working.
Related
Can anyone confirm if you can or cannot CID unlock a Wizard G3 running the IPL/SPL of 2.26?
I've been trying to downgrade my XDA Mini S to a v1.x firmware to CID unlock, I've managed to get the Molinksi ROM running, but I want to try some other ones? All the v1.x ones haven't seemed to work, and left me with just a boot loader. Can anyone help me out?
Cheers!!!
soopahfly said:
Can anyone confirm if you can or cannot CID unlock a Wizard G3 running the IPL/SPL of 2.26?
I've been trying to downgrade my XDA Mini S to a v1.x firmware to CID unlock, I've managed to get the Molinksi ROM running, but I want to try some other ones? All the v1.x ones haven't seemed to work, and left me with just a boot loader. Can anyone help me out?
Cheers!!!
Click to expand...
Click to collapse
SOLUTION FOUND -CID/sim UNLOCKING FOR WIZARD WITH AKU2 ROMS
Disregard the "doesn't work with 2.21" disclaimer as I've used this method on around 10 "out of the box" Cingular 2.25's with no problem. Follow the directions exactly. If the device doesn't reboot when you CID unlock and SIM unlock then you didn't follow procedure. Sometimes one need to reflash the 1.05 a second time after this to get the 1.x IPL and SPL.
You DID say that you have a G3.... If you want a brick do this on a G4!
All hail Faria!
It seems to hang at 98%
As I stated in the other post, the 98-99% portions take much longer than the rest of the flashing process. This can take up to 5 minutes on USB 2.0. If you are using an older computer with USB 1.1, this could take a really really long time. Just leave the phone overnight and see if it completes. Also, try a different computer if you can
I ended up paying IMEI-Check.
Its not that it hung, It crashed out after about 45mins.
Didn't really want to risk a bricked phone. Its all sorted now though!
Is it worth upgrading to a 3.2 Rom?
Hi,
I have a dutch HTC wizard/qtek 9100, with the AKU 2 NLD ROM.
I tried CID unlocking but noticed that didn't work with AKU 2,
Is it possible my phone isn't cid-locked? Is there a quick way to check?
How can I downgrade to an older rom version and what file should I use,
I tried this one: "RUU_Prodigy_1030710_110_10410_Qtek_NLD_Ship.exe"
but after restarting my wizard and loading the bootloader the update program gave an error claiming that it can only UPgrade to newer versions...
I suppose I cant use the wwe version or can I?
well, thanx in advance,
Bonusbartus
As written before, u need AKU 1 to CID unlock your phone..the only way to be sure is to unlock again. Use buttons rom.. downgrade to that... unlock the phone.. install the rom again so the IPL and SPL are the same..then you can switch to whatever rom you want. How ever, you havent shown what type of Wizard you have whether its a G3 or a G4..the above method is what i used for my G3 Wizard
I have a g3 wizard,
so I can use that rom, I don't need a dutch version or something else?
Bonusbartus said:
Hi,
I have a dutch HTC wizard/qtek 9100, with the AKU 2 NLD ROM.
I tried CID unlocking but noticed that didn't work with AKU 2,
Is it possible my phone isn't cid-locked? Is there a quick way to check?
How can I downgrade to an older rom version and what file should I use,
I tried this one: "RUU_Prodigy_1030710_110_10410_Qtek_NLD_Ship.exe"
but after restarting my wizard and loading the bootloader the update program gave an error claiming that it can only UPgrade to newer versions...
I suppose I cant use the wwe version or can I?
well, thanx in advance,
Bonusbartus
Click to expand...
Click to collapse
1. Thank-you for posting in a new thread and not in a ROM release thread.
2. Do you have a G3 or G4 (what is your IPL/SPL?)
2a. If you have a G3 read the Sticky post The Definitive Guide to Unlocking & Rom Upgrading G3 Wizards.
2b. If you have a G4 log onto the IMEI pay site (links all over the place) and pay to get your phone unlocked.
3. IF you have a G3 rom you must downgrade to CID unlock. It isn't possible to CID unlock from AKU2 or higher (read the sticky, it tells you what you need to do)
4. The best thing to do if you are unsure is to just repeat the unlock procedure. It won't hurt a thing if you are already unlocked, but will unlock you if you are locked.
5. Don't do anything flash related until you know for sure, beyond a doubt which version of Wizard you have (G3 or G4) If you have a G4 and use G3 procedures you WILL most likely ruin your device.
6. You won't get this error if you follow the steps in the correct order from the upgrade guide.
7. Good Luck
Bonusbartus said:
I have a g3 wizard,
so I can use that rom, I don't need a dutch version or something else?
Click to expand...
Click to collapse
With your G3 just follow the steps, in order, from the sticky and you should be able to end with whatever ROM you choose. Some of the steps may not make sense but, they are necessary and prevent common issues if followed correctly.
Well, I do have a G3 so I can follow the tutorial,
ipl and spl are 2.18,
only question left, CAN I downgrade to the wwe rom in the tutorial? that's what I wanna know, because I now have a nld rom, can I flash to the wwe rom in the tutorial without CID-unlocking?
well I think I just try
thanx
oh btw, any recommendations on which rom to flash to after unlocking? and I saw something about radio only roms and page-pools what would u recommend there?
so i upgraded to t mobile 2.26 and it worked fine..then i tried to flash the underground wm6 and it stalled out at 96 percent and errored...now im stuck at the boot screen with IPL 2.25 and spl 2.25 ....when i try to run the RUU it give me error: 260 or 274 connection or update error...
i dont know what else to do...anybody have any suggestions? please help!
Please read through the Wiki before posting.
Direct link: http://wiki.xda-developers.com/index.php?pagename=HTC_Wizard#upgradings
There are several suggestions there on reviving a possibly bricked phone.
i did try that already to no avail...currently i am trying to use the shelltool to flash it..it picks up this info: version 2.26.10.2 device wizard lang. WWE brand HTC ...CID n/a ROM...N/a...says this should take more then 15 min..ill update on the progress....i really hope this works:-(
stolli said:
i did try that already to no avail...currently i am trying to use the shelltool to flash it..it picks up this info: version 2.26.10.2 device wizard lang. WWE brand HTC ...CID n/a ROM...N/a...says this should take more then 15 min..ill update on the progress....i really hope this works:-(
Click to expand...
Click to collapse
Follow this:
http://forum.xda-developers.com/showthread.php?t=298613
BTW:It really helps if you tell us what IPL, SPL, OS versions you are on (those numbers that show up when you reboot). Also what type of phone you have (G3 or G4).
im sorry...it says 2.25 for both...however on the shelltool it says 2.26 so i dont even know anymore..
i did follow that tut....the problem is..i cant seem to flash from the bootloader screen...the RUU wont flash to my phone..it gives me an error when its checking phone info...o and its a G3 phone..(to the best of my knowladge)..when i started my rom was 2.25.11.1
stolli said:
im sorry...it says 2.25 for both...however on the shelltool it says 2.26 so i dont even know anymore..
i did follow that tut....the problem is..i cant seem to flash from the bootloader screen...the RUU wont flash to my phone..it gives me an error when its checking phone info...o and its a G3 phone..(to the best of my knowladge)..when i started my rom was 2.25.11.1
Click to expand...
Click to collapse
Why are you doing shell tool with a G3 (I've seen where some G3's have been bricked with shell tool is used on them)? Did you try to flash the Wizard Love ROM? That seems to help in a lot of situations.
So again, more info helps. What is the exact error you are getting. And what rom are you trying to install? Is your phone CID Unlocked? May be worth trying to go back down to the Button Rom and doing the CID Unlock again.
PROBLEM SOLVED!
i dont know what was wrong..really..i just restarted my comp...and downgraded to a stock rom..and it worked fine!
man you have no idea how much i was freakin out..
thanks for all your help! i really appriate it!
time to try again
I have tried to update to wm6 but the update stoped now i am stucked at bootloader. My ipl 1.01 / spl is 2.26 what should i do next?
Same thing everybody else does. Same thing thats mentioned many times on this forum. Flash back to your carriers rom then you can try to flash again.
whatever i try to flash i get error 300
Did you correctly unlock your device? I mean, CID? It seems looking on your IPL/SPL that you still need to unlock to go on.
Look for the G3 thread "how to" by Dr. P on the top of Wizard upgrading and follow the instructions there. You should get away from that...
Good luck!
Artan said:
I have tried to update to wm6 but the update stoped now i am stucked at bootloader. My ipl 1.01 / spl is 2.26 what should i do next?
Click to expand...
Click to collapse
mis-matched IPL/SPL show that you skipped at least one and possibly more steps in unlocking your device. Try again and don't skip the step that says to flash the button rom again after CID unlocking to downgrade the SPL, then flash up to a 2.xx CARRIER rom prior to flashing anything else. You cannot flash a 2.xx or higher custom rom into 1.xx bootloaders.
I had the same problem so I flashed the button rom again and everytime after that when I tried to flash the official t-mobile rom it would change the IPL to 1.01.0000. So after flashing the button rom then the t-mobile rom back and forth and it kept doing that. So I installed the IPL/SPL 3.08 then the 2.19 Radio Rom and just flashed a WM6 os and all works great now
Button ROM issue
I get stuck on the Button ROM loader. At 98% on the phone it stops. Left it going till the battery died and now charging again. Last time I had to start the flash without act syn. Went right into the TMobile ROM and it works again. Any help in trying to get it, Buttom ROM, to work, as in flash completely?
... works now ...
Hi, Ive looked around the forum and cannot find a solution to my problem. Ok, step by step here is what I did: I used the button 1.05 custom ROM, this was installed successfully. Then I used the definitive guide to unlocking the G3 wizard using the lokiwiz tool and this was successful as far as I know. I then upgraded to the t - mobile 3.08 ROM as this was recommended before upgrading to a WM6 ROM. This is where the problems began. I tried to flash Faria's WM6 crossbow rom and partway through the flash it hung and got stuck in bootloader mode. I read around the forums and tried to downgrade back to button 1.05, the tmobile 3.08 rom, and also the cingular 2.25 rom. The furthest I got was about 49% on the progress when my phone returns to the bootloader screen. My phone always seems to do one of two things: I either get a communication error "with my pc" which starts the recovery process(which never actually works) or I get error 274 which says that I am no longer connected to my pc (even though it still says "usb" on the screen of my pocket pc. I know that my battery will soon run out and I will have to buy a new one to resume trying to get my phone to work again. I ve also uninstalled active sync, re- down loaded and installed it, rebooted my computer (as was suggested) and this didnt work. Some one please help me as I am pretty new at this and cannot find this exact issue on the forums. Any help will be greatly appreciated!!!
Try to flash on another PC.
Ok I've tried to flash it on 3 different PCs and I havent been able to make it work, any other suggestions?
You have misread and misunderstood the definitive guide.You are confusing T-mobile 2.26 and IPL/SPL 3.08,its T-mobile 2.26 and not T-mobile 3.08. T-mobile 2.26 is a Rom ,an OS (Operating System) and IPL/SPL 3.08 are the latest upgrades to Bootloaders and not a rom.
Now,after downgrading with Button's Rom 1.05,your phone's IPL/SPL must have been 1.05,then you applied lokiwiz02b to SIM/CID unlock the phone,but ipl/spl must have remained 1.05 as you had Button's Rom 1.05 installed on your phone.
In order to upgrade to wm6,its required to have IPL/SPL 2.xx,so you were supposed to flash T-mobile 2.26 to get your IPL/SPL 2.26,but,instead of flashing t-mobile 2.26,you flashed IPL/SPL 3.08,so you have now IPL/SPL 3.08,correct ?
IPL/SPL 3.08 is an option to upgrade your IPL/SPL (Bootloaders) but upgrading to T-mobile 2.26 is recommended,so that you get IPL/SPL 2.xx to upgrade to wm6.There's your mistake,got my point ?
So,now try to downgrade to ipl/spl 2.xx or 1.xx,to do so,download the official carrier's rom of your phone from it's website and flash to get back to its original default status.
After that reread the guide correctly and follow the method.
Good luck
Thanks for your help, I'll try that and let you know how it turns out.
OK i downloaded the official cingular ROM 2.25 and attempted to flash it. I got about 76% done and got a communication error. I've tried to do it several times since then with no luck. However, my ipl and spl did change to 2.25. What should I do now?
Anybody have any suggestions? I'm dying here guys I would really appreciate some help, thanks
ok,get into Bootloaders (tricolor screen)check usb appear at the bottom of bootloaders,,try to get down to ipl/spl 1.xx,first try with button's rom,if it works,fine,otherwise try xda_minis_launch rom or wizard_love rom,if any of them installs,download WST tool and check the status of your phone by hitting the 'CID Action' button.It'll verify if your phone is locked or unlocked,ok,if unlocked then flash t_mobile 2.26 and if locked,run the lokiwiz02b again to unlock.
while flashing,turn off any antivirus,firewall and don't surf the net,check email or play any games.Leave the phone and pc alone.Must have a fully charged battery.Delete partnership with activesync and uncheck 'Allow usb connection' in the activesync,it helps sometimes.Try with a different usb cable or plugin usb cable in other usb input slot of the pc.I do hope,it might do the trick and work out fine.
Good luck