Related
Hi; I tried to unlock my G3 wizard and now I think I am very stupid.
First, I get CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE.exe and upgrade wizard, on wizard was IPL 1.xx SPL 2.xx, GSM also anything, but OS nothing. Blank line. Then that booted to bootloader.
So I tried RUU_Molski.Biz_226102_22610105_022511_WWE.exe, it wrote IPL 2.26, SPL 2.26 and OS nothing. Then i tried t-mobile rom, but it didn't work, because "only upgrade".
I tried through CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE.exe, so now I have IPL 1.01, SPL 2.26, GSM something, OS nothing (blank line) and I think I'm stupid.
Any ideas? Thank you...
Michalek said:
Hi; I tried to unlock my G3 wizard and now I think I am very stupid.
First, I get CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE.exe and upgrade wizard, on wizard was IPL 1.xx SPL 2.xx, GSM also anything, but OS nothing. Blank line. Then that booted to bootloader.
So I tried RUU_Molski.Biz_226102_22610105_022511_WWE.exe, it wrote IPL 2.26, SPL 2.26 and OS nothing. Then i tried t-mobile rom, but it didn't work, because "only upgrade".
I tried through CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE.exe, so now I have IPL 1.01, SPL 2.26, GSM something, OS nothing (blank line) and I think I'm stupid.
Any ideas? Thank you...
Click to expand...
Click to collapse
Make sure that you have unlocked the device correctly. Read Dr. P's sticky:A Definitive Guide to Unlocking G3 Wizards and also the wiki.
I know that i haven't unlocked my wizard The problem was before that I started unlock... OS disappeared after first flash.
Michalek said:
I know that i haven't unlocked my wizard The problem was before that I started unlock... OS disappeared after first flash.
Click to expand...
Click to collapse
Reflash with the Button 1.05 Rom, if the IPL & SPL don't match after the first flash then flash a second time with the same Rom, that should fix IPL/SPL problems.
Now Unlock your device BEFORE flashng a 2.x Rom.
Dr P's Sticky Thread covers this, please read it throughly..
kyphur said:
Reflash with the Button 1.05 Rom, if the IPL & SPL don't match after the first flash then flash a second time with the same Rom, that should fix IPL/SPL problems.
Click to expand...
Click to collapse
I reflashed Button ROM for three times, I still have IPL 1.01 and SPL 2.26.
kyphur said:
Now Unlock your device BEFORE flashng a 2.x Rom.
Click to expand...
Click to collapse
I can't unlock my device, because I haven't OS...
kyphur said:
Dr P's Sticky Thread covers this, please read it throughly..
Click to expand...
Click to collapse
Hm, in point 7 - Connect your device and cancel the partnership. (You're a guest )
I can not connect my device, because I haven't OS on Wizard, he boots only to bootloader (with IPL 1.01 and SPL 2.26). I can flash from PC, but then I never have OS od MDA.
I read the "A Definitive Guide to Unlocking G3 Wizards" many times, but I dont's see any solution...
Maybe I have strange wizard
When all else fails, flash an official Rom from your Service Provider. That should get you back to working order then proceed with the unlocking from there.
Michalek said:
I reflashed Button ROM for three times, I still have IPL 1.01 and SPL 2.26.
I can't unlock my device, because I haven't OS...
Hm, in point 7 - Connect your device and cancel the partnership. (You're a guest )
I can not connect my device, because I haven't OS on Wizard, he boots only to bootloader (with IPL 1.01 and SPL 2.26). I can flash from PC, but then I never have OS od MDA.
I read the "A Definitive Guide to Unlocking G3 Wizards" many times, but I dont's see any solution...
Maybe I have strange wizard
Click to expand...
Click to collapse
When I say "Connect your device" I mean to connect it to the USB cable. Two paragraphs after item 17 I address this issue. You don't need an OS, just be in the bootloader screen. I've personally had this exact same thing happen where all I had was the IPL and SPL with nothing else. Remove battery from PDA and then put it back in. Make sure you reboot your PC.
Good luck.
When all else fails, flash an official Rom from your Service Provider.
Click to expand...
Click to collapse
good idea, but it doesn't work; because "upgrade only" - My originally T-Mobile ROM is only 2.21, so I can't flash it
17. My suggestion, take for what it's worth, is to download and install the T-Mobile 2.26 ROM This will give you a strong 2.26 IPL and SPL to work with.
Click to expand...
Click to collapse
Invalid Vender ID.
But I can flash MOLSKI ROM with 2.26 IPL/SPL. Should I?
==
For everyone: Thanks for your time, really. But I'm confused, I read all, nothing helped.
Let's say: "Michalek is very stupid, we'll write him "what to do" step by step" ) something like "You asshol, connect your mda in bootloader to pc via usb, then download this, run it, then ...".
Because manual doesn't work for me, probably.
New year, new way I tried to flash today - and - i see OS, I'm in OS, I'm going to unlock wizard based on Unlocking Tutorial ;-)
I don't know, why it was successful. I tried reboot yesterday for four times, but it not helped. Only today.
I'm the happiest man on the planet And, "I've seen PROBABLY every situation with a G3 device here." - it is TRUE
Thank you for your time.
Michalek said:
New year, new way I tried to flash today - and - i see OS, I'm in OS, I'm going to unlock wizard based on Unlocking Tutorial ;-)
I don't know, why it was successful. I tried reboot yesterday for four times, but it not helped. Only today.
I'm the happiest man on the planet And, "I've seen PROBABLY every situation with a G3 device here." - it is TRUE
Thank you for your time.
Click to expand...
Click to collapse
Good to hear you are making progress, let us know how things turn out!
--M
-Michalek- Well that's wha we like to hear! The 1.05 works great as a disaster recovery tool. Most times when it doesn't work I tend to lean on the PC as the culprit. CHKDSK, temp files, spyware and virus's, etc.
Happy New Year, no?
Don't feel stupid
I'm glad it's working for you! Don't feel stupid though. My first attempt at loading a new rom went very similar. The CID unlock process told me it was successful (I thought) but it wasn't. I freaked out and thought all was lost. But I finally worked through it by going back to the Button ROM (LOVE THAT BEER SPLASH SCREEN) and starting over. The same problem even happened again about three weeks ago. After freaking out, I reloaded the Button ROM and was back on my way to normalcy
MDA is running on Superrom 1.1 and it works!
I don't know, what exactly was the problem with OS, but it helped me, when I left MDA cca three hours without battery. When I flashed the ROM before, OS wasn't.
At the last time, THANK ALL OF YOU VERY MUCH. And special thanks for Dr Puttingham and his unlocking tutorial. Thanks.
He I have a Qtek 9100 and I flashed it to Consam_Prophet_WM6_Crossbow_msyh_chs_beta2 Gives
IPL 2.26
SPL 2.26
GSM 02.47.11
OS 10.1.0.811
But now the thing doesn't want to boot any more please help
try this
Firware an old rom back on the device prefrebly the one you ohone came with and make sure you phone is cid unlocked. Also have you tried a hard reset
Force bootloader mode!
Check this out!
http://forum.xda-developers.com/showthread.php?t=294107
That worked for me and others!
Good luck!
ghailoo said:
He I have a Qtek 9100 and I flashed it to Consam_Prophet_WM6_Crossbow_msyh_chs_beta2 Gives
IPL 2.26
SPL 2.26
GSM 02.47.11
OS 10.1.0.811
But now the thing doesn't want to boot any more please help
Click to expand...
Click to collapse
A couple of things to start with. First of all get you device back working. As mentioned by epimazzo above, force your device into bootloader and flash a stock ROM not a cooked one. Read the thread.
Once you have got your device working start reading before making any more rash decisions about upgrading to WM6 (especially when the file name hints that it is for a Prophet and not a Wizard). There is only one leaked Crossbow ROM for a Wizard. This has been cooked a few times (Orwell, PDAViet, Underground). There are many threads on the merrits of each ROM but you need to read read read before you end up with a brick.
Fixed Boot crash problem
Thank you Guys for all the help; I got it back running.
formatted : Push the network button and the voice button and reset then release the rest and you get the balck screen that has the press send button and that formats Wizard and then
Push the Power + Voice + Camera and I get the Red Green and White screen. quickly Update the ROM to the origunal one I have T-Mobile. It worked. You guys are the best. I found 5._Underground_edition_Crossbow_ROM But I was not able to flash it. I need to unlock the CID but I read that I would have to down grade the Wizard and then Unlock the CID. I am still looking for the old ROM.i think I found it. If anybody has a better way to Unlock the CID please tell me.
Thank you a Million tiles for all the Help guys.
Hello all,
I am somewhat of a newby here, but I have successfully unlocked my Cingular 8125 and installed a couple of WM6 ROMs. I followed the procedure of downgrading to Button 1.05 ROM, then running Lociwiz, then installing T-Mobile 2.26, then WM6 ROM. Worked great...until now.
I was going to try another ROM, and I followed above procedures (didn't know if I needed to after initial unlocking, but I did anyway). At the "install T-Mobile 2.26" step, after 1 %, I got an error 326?, nb file not for this device. I can still install cooked WM6 ROMs, and the SPL changes, but IPL always remains at 1.01. If I try to install IPL/SPL 3.08 CAB, SPL changes to 3.08, IPL stays at 1.01. I have re-installed Button Rom 1.05 and run Lociwiz a dozen times to no effect. Even the Cingular WM5 OS meant for this device gives me the same error code as the T-Mobile.
I'm hoping this is a simple newby error. Anybody have any suggestions.
Thanks for any help.
By the way, after loading Button ROM, my Wizard hangs during the customization routine at Signed_DiscoButton8.sa. I must soft reset.
I got exactly the same problem.
I am now on IPL 1.01 , SPL 3.08, radio 2.69, using rom NBD 8.3
doesnt seem a problem however...
d-lite said:
I got exactly the same problem.
I am now on IPL 1.01 , SPL 3.08, radio 2.69, using rom NBD 8.3
doesnt seem a problem however...
Click to expand...
Click to collapse
Hey m8,
have you forgotten this thread (http://forum.xda-developers.com/showthread.php?t=319582) ? (see last post)
mestrini said:
hahaha nice to see good spirit after all this
Here goes:
Make backup of the CID block (VERY VERY important!!!)
Make backup of the GSM calibration block (VERY VERY important!!!)
Kill wcescomm.exe process
Start mtty, enter bootloader mode in Wizard and connect
type doctest (this will write test patterns in DOC chip and clear all data!)
Flash button ROM (1.01_IPL/1.01_SPL/1.05_OS)
Flash CID block backup (don't miss this)
Flash GSM calibration backup (important)
If all ok then remember to upgrade to 2.xx before installing WM6!!
Post results
EDIT:
Use WST for steps 1, 7 & 8
Click to expand...
Click to collapse
are you willing to prove me wrong?
mestrini said:
are you willing to prove me wrong?
Click to expand...
Click to collapse
yes.. missed your last post to be honest, sorry..
(btw phone is happy till now .. but we go for solving it, killing seems impossible)
step 2, gsm callibration block.. how do i copy?
D-Lite
use the "Read ROM" button and select the appropriate section from the list.
status:
Code:
DOC ImgFS partition read/write test PASS
Ext ROM partition read/write test, offset=0x0, length=0xA00000
Test pattern =0xAA
Flash Ext ROM failed.
DOC Ext ROM partition read/write test FAILED
--Flashing button rom @ 100%
--DATA CRASHES PLEASE CONTACT SERVICE CENTRE
--WST Says I am still on SPL 3.08 and rom is write protected.. screen of wizard says SPL 1.01 ...
--Installing Button ROM, ... SIM Lock SUDDENLY
--Screen goes funny flashing between simlock and customise
--Few soft-resets, WST now convinced on SPL 1.01 and flashed CID block
--Soft-reset
--Imei gone, flashed back GSM callib. data, softreset
--doesnt boot passed the pint of beer... going for RUU of T-Mobile 2.x
--bootloader, flashing RUU_Prodigy_2210205_22102108_021911_TMO_NL_DUT_Ship.exe
--The NBF can not be used for your phone @95%, followed by congratiolations (stupid software)
--trying UK version...
--all give error 326
--another button flash
--*PLING IDEA* on 3.08 i couldnt doctest properly... so doing it again
-- bad idea.. same result...
damn... i thought it would work
anyway, there was point where the phone had same values for IPL/SPL (not too bad ). What is strange is why phone didn't boot anymore after flashing the GSM calibration and saying the flashes weren't suited for the phone.
What state is it on now? Wanna go again? This time, instead of flashing the 'GSM calibration data' do a simple IMEI writing and try to unlock CID before upgrading to official ROMs
sorry for this...
IPL locked on 2.26
I am having the same issue. I have tried numberous times to load my original rom and get the 326 error @ 1%. My ipl remains locked on 2.26. Is there any way to fix this? Please help.
it is now on 1.01, got my own imei back, spl 3.08, nbd 8.x rom...
everything fine again.. pretty sure it has something to do with ext.rom and/or write protection of it.. will give it another shot but not this month.. getting busy
@acmickey, not sure if you got same issue... is your IPL 1.01? else you might just have a locked phone..
Hey d-lite,
I followed your example and loaded BSD8.3 ROM and IPL/SPL 3.08 and radio 2.69. Everything seems to be fine. No missed calls. All programs work (touchflo is pretty cool). IPL is still locked on 1.01, even though SPL is 3.08.
I tend to agree with you that something is suspicious concerning the extended ROM. The first symptom I had that something was wrong was after loading Button's ROM, during the customization routine, Signed_DiscoButton8 would not install. Phone locked up and had to soft reset.
Oh, well, at least the phone works. The downside, of course, is that you can't load an original ROM, even though you can load a cooked one. Weird, huh?
Hopefully someone a lot more knowledgeable than I will figure this one out soon. Will keep checking the boards. At least we don't have bricks.
I am having the exact same problem as the 1st post but my ipl is stuck on 2.26. I am using an unlocked device and I have no problem downgrading/upgrading the spl. I also get the 326 error when I try to flash back to the original rom. (I used to be able to do this without a problem - I can't figure out what happened.)
It's really weird and I have search and searched and can't seem to figure out a solution.
which SPL you have now?
sorry.... my spl is 1.01
Right. Assuming your device is working 'normally' are you willing to try something new? If so contact me PM
what have you cooked up this time mestrini? lol
my wiz (at 1.01 still..) is doing a-ok, but always willing to go for something new so we can fix this for the communities sake...
d-lite said:
what have you cooked up this time mestrini? lol
my wiz (at 1.01 still..) is doing a-ok, but always willing to go for something new so we can fix this for the communities sake...
Click to expand...
Click to collapse
sorry to mislead you buddy but acmickey got it all wrong and, instead of IPL stuck at 2.26 and SPL 1.01, he has same as you IPL 'locked' at 1.01
So my theory could not be verified.
cheers
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!
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??