Database Develop

Forcing Bootloader Mode

Maybe some of you are already aware of this procedure, maybe not.
Anyway, it worked for me and I decided to share how to do it. Simple.
This procedure should only be used in case you really need enter into a bootloader mode and all other ways to do it has failed! Hold Camera button is one of these I am mentioning.
My Wizard was almost bricked at that time and after I speak with an I-mate technical guy, I got the following:
1. Make sure your i-mate™ K-JAM is not Connected to the PC and remove the dummy card or SD/MMC card
2. On your Desktop PC, open Microsoft ActiveSync, then go to File >Connection Settings >Remove the Selection from “Allow USB Connection with this desktop computer”
3. Reconnect your i-mate K-JAM to the Desktop PC using the USB Cradle and the Charger MUST be Connected to the Cradle (Don’t use the IrDA or Bluetooth for the Upgrade)
4. Run the Upgrade again and it will work fine without any problems.
While upgrading, the ActiveSync program will not go on, however the upgrade is running.
Hope it helps!

this realy worked for my (ex)bricked dutch tmobile mda vario !!!!
tip: REALY make shure that there is no wcescomm.exe running all the time and realy remove the sd card else is nogo
btw: my wizard is CID locked! and works like a charm

Thanks buddy!
I'm happy that worked for ya!
Take care!

I'm having a problem
The power went out as I was upgrading my Wizard (Cingular) so now it just turns on at the boatloader screen. I've tried running updates while it was in this screen (it did show the "USB" in the white bar) but most of the time it tells me there is a connection error. Even if I kill Activesync, I notice that when I run the update utility it still runs Activesync. I've tried disabling the USB connection but still get the connection error.
The only time I haven't gotten the connection error was twice it asked me to update but then told me I had the wrong file. This only happened when I tried "upgrading" to 1.05 as I was trying to start again. After it tells me that if I try running it again it gives me the connection error.
Any ideas?

Hi!
Have you already flashed your device once?
Which ipl/spl do you have?
I had problems over 1.05 ROM in the beggining.
If you stuck on bootloader mode, that's a good signal your device is not bricked.
I'd recommend you to disable activesync as you did and reflash it again! Check also if your device is CID unlocked! Search for a thread in the xda developers root.
Try to upgrade to ipl/spl 2.26 first and later to others you want.
Regarding the old file error...can be related to a missing file called enterbootloader.exe.
Hope it works for ya!
Take care
Ironman273 said:
I'm having a problem
The power went out as I was upgrading my Wizard (Cingular) so now it just turns on at the boatloader screen. I've tried running updates while it was in this screen (it did show the "USB" in the white bar) but most of the time it tells me there is a connection error. Even if I kill Activesync, I notice that when I run the update utility it still runs Activesync. I've tried disabling the USB connection but still get the connection error.
The only time I haven't gotten the connection error was twice it asked me to update but then told me I had the wrong file. This only happened when I tried "upgrading" to 1.05 as I was trying to start again. After it tells me that if I try running it again it gives me the connection error.
Any ideas?
Click to expand...
Click to collapse

My device is unlocked as I've been trying different ROMs as of late. I had gone back to the Cingular 2.25 ROM for a couple days to sort some things out and was going to flash Farias AKu 3.3 when my power problems happened. My Current IPL/SPL is 2.25
I've tried flashing the TMobile 2.26 but keep getting connection errors. In fact, I've tried flashing with every ROM I have pdviet 3 and 4, CIngular 2.25, TMobile 2.26 and Custom 1.05. Everything (except twice in the custom) gives me connection errors.
Any other trick I can try?
BTW, I used to live in Sao Paulo years ago...
Edit: OK, so I tried the 2.26 TMobile ROM after I typed this and it worked!! I'm back up but I was having trouble with that ROM beause of some incompatibilities with Cingular. I'll go back to Cingular's ROM and play it safe for now.
I believe part of my problem was I kept trying different updates one after the other. Now that I think back, the 2 times I got the update to almost work was after I turned off the device and turned it on again, which is what I did this time around also.

I had the same problems as mentioned by Ironman before. I followed the steps and with a few slight changes, I managed as well to "unbrick" my wiz. THANKS A LOT for the great step by step manual!!!
Still I wanted to know WHY i bricked my device:
I was trying to upgrade to the underground WM6 ROM. I got the same situation as ironman:
Quote:
The power went out as I was upgrading my Wizard (Cingular) so now it just turns on at the boatloader screen. I've tried running updates while it was in this screen (it did show the "USB" in the white bar) but most of the time it tells me there is a connection error. Even if I kill Activesync, I notice that when I run the update utility it still runs Activesync. I've tried disabling the USB connection but still get the connection error.
The only time I haven't gotten the connection error was twice it asked me to update but then told me I had the wrong file. This only happened when I tried "upgrading" to 1.05 as I was trying to start again. After it tells me that if I try running it again it gives me the connection error.
Unquote
I then followed the instructions by epimazzo as written above. I also tried the T-Mobile ROM 2.26 which was not working for me. PANIC!!!! Error messag was that I had the wrong Vendor ID. THerefore no upgrade to TMob 2.26 was possible. I tried it then my original qtek ROM in my language and see it worked!!! This IMHO means that I did not put the device in a proper IPL1.xx and SPL 1.xx status which is required for a clean system in irder to unlock it! So if it is bricked, try your native AKU2 ROM and make sure you unlocked it properly. Maybe you have to run the 1.05 ROM for a second time after the unlocking.
I hope this helps you guys.

Sounds great to hear that!
I had play around with pdaviet3, underground and another ROM just today without any problems at all. I don't think that this is the case. Now you get your device back to normal, try to reflash it again. Hope it works this time!
BTW,...São Paulo is a nice city. Thanks! Let me know if you decide to come here!
Take care
Ironman273 said:
My device is unlocked as I've been trying different ROMs as of late. I had gone back to the Cingular 2.25 ROM for a couple days to sort some things out and was going to flash Farias AKu 3.3 when my power problems happened. My Current IPL/SPL is 2.25
I've tried flashing the TMobile 2.26 but keep getting connection errors. In fact, I've tried flashing with every ROM I have pdviet 3 and 4, CIngular 2.25, TMobile 2.26 and Custom 1.05. Everything (except twice in the custom) gives me connection errors.
Any other trick I can try?
BTW, I used to live in Sao Paulo years ago...
Edit: OK, so I tried the 2.26 TMobile ROM after I typed this and it worked!! I'm back up but I was having trouble with that ROM beause of some incompatibilities with Cingular. I'll go back to Cingular's ROM and play it safe for now.
I believe part of my problem was I kept trying different updates one after the other. Now that I think back, the 2 times I got the update to almost work was after I turned off the device and turned it on again, which is what I did this time around also.
Click to expand...
Click to collapse

It seems you got the idea!
You did the right thing! Sometimes, use the official ROM can solve many issues out there!
Keep walking!
enlite_de said:
I had the same problems as mentioned by Ironman before. I followed the steps and with a few slight changes, I managed as well to "unbrick" my wiz. THANKS A LOT for the great step by step manual!!!
Still I wanted to know WHY i bricked my device:
I was trying to upgrade to the underground WM6 ROM. I got the same situation as ironman:
Quote:
The power went out as I was upgrading my Wizard (Cingular) so now it just turns on at the boatloader screen. I've tried running updates while it was in this screen (it did show the "USB" in the white bar) but most of the time it tells me there is a connection error. Even if I kill Activesync, I notice that when I run the update utility it still runs Activesync. I've tried disabling the USB connection but still get the connection error.
The only time I haven't gotten the connection error was twice it asked me to update but then told me I had the wrong file. This only happened when I tried "upgrading" to 1.05 as I was trying to start again. After it tells me that if I try running it again it gives me the connection error.
Unquote
I then followed the instructions by epimazzo as written above. I also tried the T-Mobile ROM 2.26 which was not working for me. PANIC!!!! Error messag was that I had the wrong Vendor ID. THerefore no upgrade to TMob 2.26 was possible. I tried it then my original qtek ROM in my language and see it worked!!! This IMHO means that I did not put the device in a proper IPL1.xx and SPL 1.xx status which is required for a clean system in irder to unlock it! So if it is bricked, try your native AKU2 ROM and make sure you unlocked it properly. Maybe you have to run the 1.05 ROM for a second time after the unlocking.
I hope this helps you guys.
Click to expand...
Click to collapse

Excellent post. I messed up with my own cooked ROM and could only get the bootloader screen. Tried the tips here - didn't work first time but I pulled the battery from the KJAM to reset it rather than using the reset button and it worked fine.

In my opinion this thread is so helpful to people who brick their device, it should go "sticky". Mods anything you can do about it?

Thanks buddy! I really appreciate!
We survive here over tips like that!
jt_armstrong said:
Excellent post. I messed up with my own cooked ROM and could only get the bootloader screen. Tried the tips here - didn't work first time but I pulled the battery from the KJAM to reset it rather than using the reset button and it worked fine.
Click to expand...
Click to collapse

Help me similar problem
I upgraded Super Rom, then my Wizard run very slow and no signal (no call out and in- no network at all). And Terible thing is PC could not dectect PPC thought Active Sync. I've soft and hard reset but no use.
So I donot know where to start to re install Rom again.
Please help me....

Hi there!
It seems that you just need to enter into the bootloader mode and reflash it again!
I had similar problems and more during my brick "false" stage!
So, just try to follow my steps here and you should be fine! Once you get into bootloader mode, just use any ROM out there to reflash.
Good [email protected]
thaiphong said:
I upgraded Super Rom, then my Wizard run very slow and no signal (no call out and in- no network at all). And Terible thing is PC could not dectect PPC thought Active Sync. I've soft and hard reset but no use.
So I donot know where to start to re install Rom again.
Please help me....
Click to expand...
Click to collapse

I was about to start a EMERGENCY HELP thread, but I *think* this is the right place instead.
The "touch" of my screen went dead today. It got progressively worse over a few hours, starting with difficulty in using the phone dialer, then random incorrect stuff getting triggered by screen taps.
So I hard reset, and got no response on the fifth alignment cross, meaning 1) "Tap on the screen...; 2) center; 3) top left; 4) bottom left; 5) bottom right. In that I could not proceed with alignment, I hard reset again, and now, at the first alignment screen, i.e. "Tap on the screen...", I have no screen response at all.
I called T-mo, and they are being great about sending a replacement ASAP (and getting me a loaner in the meantime).
BUT, I am running Faria+ AKU3.3 V2... so I clearly have to flash back to T-mo 2.26. I can;t figure out how to do it though, as no matter what I do I am stuck at the first alignment screen!!
HELP!! EMERGENCY!!!
(I have three or four days to get this done, so it's not THAT urgent)

Do a search for Broken Screen. Someone (either in Wizard Upgrading or in the Wizard forum) just had a similar issue with a cracked screen. They downloaded something that allowed them to get around the welcome page.

Actually, if you are just trying to flash a new ROM, don't even mess with it. Go straight to the Boot Loader screen (see the first post of this thread). No tapping necessary until the new rom is on (and that will be the Tmobile then so you would be good.

Thanks for the quick reply. Charging up to green now, and then will try to enter bootloader and flash T-mo 2.26. Will report back.

Worked great. Back to T-mo she goes!!!

BootLoader Mode
Excellent thread but you left out one thing.....exactly how to place your device in bootloader mode.
To clear up any misunderstanding because this is very important....this is how you do it:
Perform a soft reset, when the screen goes blank hold the camera button until a multi colored screen comes up .... That's it !!!!!!
When the unit is connected, USB is displayed at the bottom left.

Nervous about upgrading with error 'message' in place

There is a problem with my MDA: It continually flashes the volume/ringer control on the screen with the circle with the loudspeaker and mic turned off. This flashes every second or two and when it flashes, prevents pretty much anything else from working or command from executing.
I had a very old TMobile software version on it. I down loaded a much newer version from TMobile in an attempt to get rid of this problem before upgrading to XDA firmware: (The whole thing is very out of warranty)
The upgrade went successfully but the flashing volume / ringer control still flashes.
Does anyone know what this means or if upgrading to XDA will get rid of this problem (or exacerbate it!)

Has anyone noticed IF there is a problem with Puttenham's "Step 17"?
I got around my nerves about upgrading this G3 with a hardware problem in place and appear to be encountering a severe problem with Step 17 which is that it says it is "Your Choice" to go to a 3.08 SPL/IPL. Nowhere however does it say which later ROMs you can apply if you DO choose to go with the 3.08. I applied this to correct what I thought was the hardware issue (reinstalling the T-Mobile ROM at SPL 2.26 didn’t seem to cure it) and the 3.08 did install properly and cured the hardware problem.
I tried different ROMs because I cant seem to understand how to use VoIP or which ROM will let me use this 'feature' or which ROM has this feature built it as some say they have deliberately taken it out.
Suddenly I am getting error messages telling me that the unit needs a later ROM revision to install perfectly.
(WizardLove was the first to do this: It executes in Italian and as I mentioned, just tells me that it needs a later version to work)
So I reflashed with the Molski ROM which is the only one which seems to be around and the flash worked up until 94%. At that stage the progress bar turned to red and there was an error message telling me that I can recover and try again. I did this a few times and SEEM to have bricked my Wizard (When the Molski upgrade failed, attempts to chkdsk, reboot, delete all temp files etc failed). The unit will now only boot to the three-colour screen? Further attempts to flash seem to see and read the device and tell me either that there is no ROM on it and would I like to upgrade? Followed by this unexplained 'USE LATER ROM'. (There may be a problem with installing the T-Mobile ROM on an unlocked Wizard with a 3.08 IPL/SPL However it has to be said that Molski is, still, the only ROM which runs and it inevitably stops at the same position, the 94% mark when the MDA progress bar goes red, the unit shuts down, the upgrade process thinks about it for a while and ultimately reports ERROR [302] UPDATE ERROR)
Alternatively they (for example ROM Update Utility 2.00.1) tell me that there is no communication between the PC and the Wizard. Actually ActiveSync 4.5 does show no connection between the device and the PC, which I suppose I would expect if the Molski ROM failed to complete? Device Manager seems OK with the unit being in place though? And I cant believe this is important as there obviously IS connection between the computer and the PDA
Easymob said he would let users have a path to a ROM they could use but no where is it set out which ROMs you can use of the ones you actually CAN find?
I have also tried the Xelencin ROM which initially tells me that it cant see the PDA. Then it admits that it can and tries to unlock the CID (which surely must be already unlocked by now if I have upgraded to the later SPL??)
I am not sure I have a totally bricked unit, - The Xelencin T-Mobile ROM MUST be doing something because it does successfully run the RAPI unlock and after a few error messages telling me it can't access the MDA, reports DONE! But then it tries to run Machinagod's HTC Wizard Unlocker and gets stuck. It shouldnt get stuck at this step as I must already BE unlocked! It should pass this step.
I can hear hdd movement (not churning) but the program doesn’t progress past this step. Ultimately this carries on for hours and the Wizard shuts down I presume when the battery fails as the charge function doesn’t seem to work in ROM upgrade three colour screen mode. Plugging the charger in now doesnt seem to do anything
Again as the program was built for the 2.26 SPL, I still cant figure out whether these available ROMs should run on the 3.08 which I followed in the STEP 17.
MEANWHILE BACK AT THE RANCH: Is there a more obvious answer to why Molski always fails at precisely the same 94% position?

RUU Fails since i upgraded to a WM6 ROM?

Hi everyone,
First and foremost, let me introduce myself, I am known as wizzkidd (a name that often is used against me at times like these). Aged 27 from London, UK. I'm a typical mod-freak, modding anything and everything possible from PSP's to Wii's to Cable TV etc etc.
Anyway, I've got a SPV M700 (aka HTC P3600) branded on Orange UK running Windows Mobile 5, and everthing works fine. I found this wonderful site when I was researching into the amazing additions and power of Windows Mobile 6.
To my amazement, I soon realised it would be possible to upgrade to WM6, so off I went reading through the forum....
To start with I realised I needed to perform a CID Unlock (and whilst at it, I done the SIM Unlock too) before I could proceed. I done this perfectly fine.
I then found the first ROM that looked impressive as it was based on WM6 and had a bundle of goodies baked within it. (im learning the terminology too, hehe), it was a PDAViet ROM (latest to date)... I followed the instructions and hey presto, my phone was a fancy WM6 version with loads of impressive goodies installed.
After search for more stuff here, I found loads of interesting stuff. But firstly I decided to install the Hard-SPL into my phone for my own protection when doing future ROM flashes.
What caught my eye was the Touch Flo stuff, so I wanted it. Searching through the threads and the progress in development, I soon found a Wizard ROM that includes Touch Flo, and based on user suggestions and feedback, I decided to go for NBD v7.4.
My problem:
- (currently running PDAViet ROM: 02.07.06.PV and have Hard-SPL integrated)
- I double click on the "ROMUpdateUtility_Wizard_NoID.exe"
- I tick the "I understand...." and the "I Completed the steps..." boxes
- (the USB cable is connected and ActiveSync 4.5 detects the connection fine)
"Verifying the information on your PDS Phone..." displays for about 4 seconds...
The RUU displays the current information about my phones image, and has a "Update" button to click to update the current ROM version, so I click it...
The RUU displays some verify checks such as
FROM
model ID: ""
image version: "02.07.06.PV"
Language: ""
TO
model ID: "Wizard"
Image Version: ""
Language: "WWE"
I click next twice... the phone boots into the Hard bootloader (SPL-1.20.Olipro) and the USB connection disconects and then reconnects at this point (i can tell this by the audio sounds), the RUU displays the progress bar at 0% and nothing happens, the screen on the M700 stays on the bootloader screen, and the RUU stays on 0% - this lasts for about 15 seconds, then the RUU says "ERROR [264]: CONNECTION, and gives me the option of clicking the "Recovery" button, doing so, and following the instructions, leads to a final message saying: "Error recovery has been successful and the update process is ready to resume. Exit recovery and run the RUU again."... I try running the RUU again, and im back to sqyare one again!
I've even tried using the Soft-SSL (by Des), but the progess bar stays at 0% and the bootloader stays on the screen.
What could be wrong?
PS Thanks for reading and thanks for your patience if you've got this far. lol

Don't flash a wizard rom onto a trinity rom. Only flash trinity roms. That's like trying to flash moto razr firmware on it. Not meant to insult, just telling. I hope your device isn't bricked.

what you're doing wrong is flashing a Wizard Rom on your phone. There's a reason that the forum is divided in to different sections for different phones.
Think of it this way.. would you put a Wii mod on your PSP? you're lucky that the RUU has saved you from carrying around an expensive brick.. read a little more.. flash a little less..

Ohh I see, I didnt realise 'Wizard' was a different model name, I assumed it was a Wizard in the sense of an 'Easy Install For All...' type ROM, (ie If you was to use a wizard when creating a chart in an excel spreadsheet, catch my drift).
My bad for mis inturpreting what a 'Wizard ROM' was. Ooops. Well, my device still operates pefectly fine anyway.
Do you know anywhere I can get a stable version of Touch Flo for my device? Preferably cooked in a ROM, because I used a alpha version of the Touch Flo .cab file, and I had nothing but problems.
Thanks

there are no trinity ROM's to my knowledge with touch flo built in... should be coming soon now that official Dopod WM6 ROM is out... keep an eye on the trinity mobile 6 forum (and not on the Wizard forum haha)

lol. OK.
I noticed you're using the same ROM as me at the moment. Have you tried installing the Touch Flo (Alpha) cab file and managed to get it working by anychance? (eg. No black screen)

didn't work for me. I couldn't really be bothered to mess with it too much as people have such varied results. Someone will cook it in to a ROM before long. Look out for mun's Indigo ROM.. he said he'd put it in.

Trinity running 6.1 Elegance- totally bricked - please help me!!

Hi all,
I have been visiting these forums for 2 years now and have downloaded some great tools and ROMs to enhance my Trinity, however something all of a sudden has gone very wrong!
I upgraded to WM6.1 Elegance edition about 3/4 months ago, CID unlocked the phone about a month ago and everything has been working like a dream.
However just today, I attempted to turn the volume down on my phone during a meeting (I always forget to normally!) and there was no display. After few battery resets, again no display. It starts up, loads the the Elegance splash screens and then hangs on the screen before when the OS should appear.
My decision was to flash the ROM again. I cant flash using Activesync as it wont pick up on the hung screen, so I started the bootloader and got as far as 1% of the flash and it will restart. So I tried the SD Card method when resulted in a "loading" screen appearing for a few seconds and then it goes back to the standard bootloader and displayed a 00068002 error.
I am out of ideas, I hear mtty.exe is a good program for this kind of thing, but what I want to know is if this is fixable or if I should give up!
I have been working on this since 2pm today none stop!
Can any of you guys give me any suggestions please?!?!?
Kind regards,
Jonathan

Should be a cinch
Did you SPL the Phone before flashing roms?
If you put the phone into the bootloader mode The RGB screen and kill of activesync you should be able to run one of the flash update programs.
If I have flashing problems its usually Active sync so I kill it then run the flash program.
I've got a sneaky suspision your battery might be causing the problem.

Hi there, thanks for the reply. As I was new to upgrading I havent used SPL on the phone before flashing the ROMS. I did use an unlock tool recently as i wanted to try a different network SIM to see if it worked when I was in South America, so the phone is unlocked to all networks. Are you saying if I SPL now it should sort the problem out? If so how do I do this withour ActiveSync working - can you use SD?
Another thing I failed to mention was that when I start an upgrade and it follows all the steps, it doesnt say the current ROM on the screen where you press update ROM. It just gives the name of the new ROM and the current one is left blank.
I have disabled Active Sync before attempting the update. It seems to go through fine and then the phone restarts wafter 1% of the update.
What makes you think it is the battery? I am happy to spend under 20 pound on ebay if you think it will fix the issue!

try unbrick.bat.......my trinity was also stuck.......unbrick.bat save my day....

The same happened to me several time....I could not find a solution other than this one:
1. Flash the official HTC ROM.
2. Flash the required ROM then.
it works for my TrinTy.

8125 bootloader stuck

ok, im inbetween a newb and a full out destructive force to any type of moddable device and im having a little bit of trouble with my cingular 8125. ive had this phone for a few months and i am having the hardest time dealing with the rom on the phone now. ill give a quick breifing on it:
got it with original cingular rom, not sure what spl or ipl on it but the first thing i did was unlock it by myself, cid and sim unlocked, and then updated to a jaguar wm 6.1 rom which worked fine. decided i was going to unfortunately sell this phone so i decided to upgrade it one more time to see if i really wanted to sell it, i then bought the upgrade to go past my 2.21 ipl and spl. i got my unlocker and followed my instructions and got a brick. but not a full brick. its stuck in the bootloader screen. after reading countless threads, i learned that i should be able to just still update a rom to the phone with no problems which actually works, but as soon as a rom completes it goes right back to my bootloader screen so help me! please cuz now thats its a challenge again, i want the phone! plus all my info is on the phone still back up

Flash the official stock ROM first, then use Button's ROM to downgrade your IPL and SPL before unlocking CID.

post the present IPL/SPL it displays now.Which rom you are trying to flash now ?

ok when i try to put the most current 8125 rom on my phone (2.25.blah) it tells me that its not the same phone which is weird but thats preventing me from putting the original rom on the phone. however if i try and put the buton rom on the phone now, it will go through completely and say it put it on the phone, but when it restart, its right back to the bootload screen...
and im running IPL 2.21.0001 and SPL 2.21 with a previous installation of a jaguar rom, dont know exactly which one, but i know it was a jaguar rom. but right before i tried to upgrade the updater, i went back to my default WM5 rom so i guess it was te basic 2.21 rom on the phone with WM5

dimedash12 said:
ok when i try to put the most current 8125 rom on my phone (2.25.blah) it tells me that its not the same phone which is weird but thats preventing me from putting the original rom on the phone. however if i try and put the buton rom on the phone now, it will go through completely and say it put it on the phone, but when it restart, its right back to the bootload screen...
and im running IPL 2.21.0001 and SPL 2.21 with a previous installation of a jaguar rom, dont know exactly which one, but i know it was a jaguar rom. but right before i tried to upgrade the updater, i went back to my default WM5 rom so i guess it was te basic 2.21 rom on the phone with WM5
Click to expand...
Click to collapse
WEIRD !
You got mixed Bootloaders of G3 And G4,IPL 2.21.0001 is G4 and SPL 2.21 is G3,as you posted,well,can't say which was original,only you can tell,but some how its mixed Bootloaders,in this situation no Rom will flash,its a 'Brick'.

If as Zabardast says its bricked then you have three options:
1. Get a new Wizard
2. Get a new Wizard Motherboard
3. Get a Wizard with broken LCD from eBay and replace its LCD with your current one and Enjoy!!! (Cheapest)

lol this is tough! but no worries, ill be back with some other pda at some point and time and then ill try and take this phone apart! but the weird thing about my wizard is that this only happened when i tried to update the phone with the CID unlock program that you have to pay for!
lol it was perfectly fine until i tried to do it! oh well, back to my crappy p168!

May be that CID Unlock program was not meant to be for a G3 and you were updating a G3 so it mixed you IPL/SPL and caused a kinda BRICK. So please be careful before doing flashing things because if you dont be carefull then your PPC may become a heavy paper weight, and a costy one too. LOL. TC

kitty4uhig said:
Farming for eq2 plat isn't easy, but you can buy eq2 plat, guides, accounts & items on sale. We have revolutionized the exchange of money to eq2 plat. Purchase eq2 plat& power up your character ot the next level. Our world class customer service will make sure you are more than satisfied with every purchase. Feel free to contact our 24 hour live support with any questions you may have. Shop now and play as a VIP!
Click to expand...
Click to collapse
Stop this nonsense immediately,otherwise it'll be reported and you'll be banned.Its spam !!!

try this: http://forum.xda-developers.com/showthread.php?t=276963

Cingular 8125 problems
Ok guys i am really pissed i have been looking for three days and cant find it, first off my IPL is at 1.01 and the SPL is at 2.25 and i cant fix it i wanted to install the original 2.25 again and start from scratch but can not find the damn thing so if anyone has it can u just upload it fo me and give me a link that i can get it at please i am sick and tired of waitnin i really like this phone and i dont want to risk bricking it thanks.

Ok, grimgod, aggression is reaaaallly ugly and no freakin one will help with that sh!t attitude (pardon the language, mods). The senior members do everything they can to help the noobs. Have you tried reading the flashing guide, wiki, or tutorial? I'd bet even money you haven't. Have you CID unlocked? Did you flash the button rom twice ( as the guide suggested to get ipl/spl both 2.xx)? Did you flash the official tmo rom (found im the flashing guide)? Have you done anything other than sit on your hands and wait for it to be handed to you? READ AND SEARCH!!!!!!!!!!!!!!!!

http://forum.xda-developers.com/showthread.php?t=310831 <HERE!!!!!!!!!! Should I flash your device, too?

Similar issue... need some Wizard Expertise
I picked up a coworkers old Cingular 8125 that he'd had in a drawer for about a year. Battery was right dead so the phone wouldn't boot. I charged the battery on an external charger for a few minutes, put it back into the phone, and plugged it in to the charger until the LED went green indicating a full charge.
When I power up I see the T-Mobile splash screen (light gray background, some square dots, and the "T-Mobile" logo). And there it stays indefinitely.
Tried a hard reset (Comm Mgr + Voice Cmd + Soft Reset), and it said "Press Send to restore factory default". Pressed the green dialer key (I assume that's send), and it says Format FAT partition, FAT partition complete, and then returns to the same T-Mobile splash screen and hangs there.
So then I tried putting it into Boot Loader manually (Power On + Camera). No problem, shows IPL 2.26 and SPL 2.26. Plug it into the computer USB port (running XP Pro), and then the USB connection shows on the phone. Attempted to flash the Wizard Love ROM to get this thing back to square-one. Error 260. Attempted to flash the T-Mobile stock ROM. Error 260.
Between each flash attempt, I'm pulling the battery out and starting fresh. I think I've followed all the steps I'm finding in multiple threads. But for some reason I'm not able to get this thing to communicate via USB. All RUU's give an Error 260. Am I missing something?

Forgot to mention I'm following the steps outlined in this thread from Dr P. To the letter!
Also did a little reading up on using the MTTY method in this thread by Drug_Store. Thought maybe the existing ROM might be intact, and I might be able get it to a 256MB MiniSD, then write the backup ROM from SD in boot loader. Well, for some reason I don't even see the USB connection option when I use the MTTY - can't ever get to a point where I can issue commands. Again, I think I'm following the instruction. But still no juice.

Nudge, nudge. I'd donate for a solution that works... otherwise I have to keep letting my 10 year old play The Quest on my phone.