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.

BRICK - QMobile, Orange, hard spl'd ???

....before anyone moderates my ass i wasnt sure whch forum was the appropriate one for a bricking!
****
My phone seems to have given up the ghost. A few days after having put on the excellent Q-Mobile system. My phone has refused to boot properly. Heres what happens:
In start up from Soft reset, or Power off, i get the tricolour screen saying:
KAIS130 MFG
SPL-1.0 OliPof
CPLD-8
a few2 lines benath that is written 'Serial'
it then flashed onto a white screen saying 'loading......no image file' - this all takes about a second.
And then it rests on the screen mentioned above.
I haven't dropped it or done anything other than flash- correctly.
AAAARGH! it does randomly decide to boot up properly after its been left of for a whil if that helps.
Also - active synch wont recognise it , in the tr-colour state.
HELP!!!

Phone now stable
wondering what the best thing to do is to get it back on track...

i had same issue read the link to my post
http://forum.xda-developers.com/showthread.php?t=352859
mtty worked for me then i reflashed its worth a try i guess

kishorvalji said:
i had same issue read the link to my post
http://forum.xda-developers.com/showthread.php?t=352859
mtty worked for me then i reflashed its worth a try i guess
Click to expand...
Click to collapse
mtty is the way to do...you are not bricked...just take a few breaths and search the forums. When it happened to me, I had to use the BOOT command with MTTY. After it boots back up, run HARDSPL once again otherwise anytime you soft reset it will return to the bootloader screen.

thanks, but what is MTTY - i checked the posts and couldn't find it anywhere

Kaiser entering three-colour screen by itself

My Kaiser has entered the three-colour boot screen by itself twice. It happened the first time after I did a soft reset, and I didn't know what to do to solve it, but on attempting a ROM flash, it reset itself back to normal with all my information intact.
Now, it has gone into the bootloader again, without me having done anything at all - I just pulled it out of my pocket to use it, and there was the coloured screen again. This time I've made multiple attempts to clear it, using both the method above (no joy at all, just endless error messages) and MTTY, which won't connect properly at all.
I'm really anxious about this - I can't get the thing to come out of it however hard I try, and I really don't know what to do. I'm worried it's become a brick.
Lee

PrimitivePerson said:
My Kaiser has entered the three-colour boot screen by itself twice. It happened the first time after I did a soft reset, and I didn't know what to do to solve it, but on attempting a ROM flash, it reset itself back to normal with all my information intact.
Now, it has gone into the bootloader again, without me having done anything at all - I just pulled it out of my pocket to use it, and there was the coloured screen again. This time I've made multiple attempts to clear it, using both the method above (no joy at all, just endless error messages) and MTTY, which won't connect properly at all.
I'm really anxious about this - I can't get the thing to come out of it however hard I try, and I really don't know what to do. I'm worried it's become a brick.
Lee
Click to expand...
Click to collapse
See my guide here: http://forum.xda-developers.com/showthread.php?t=423486
Please post any more info in that thread.
ta
Dave

Please Follow Dave's Advice.
Thread Closed

My bricked P3600 is a Walking Zombie. Try this if you're desperate!

I don't know if I can help you but will try since this forum has helped me.
My P3600 is basically screwed. It's a walking zombie brick phone.
Why zombie? Because I bring it back from the dead everytime!
I dropped my phone quite badly twice in a day a few days back,
Next day I woke up... my pocket alarm had hung and I had to hard reset because a soft reset brought about the Tri-colored bootloader screen.
After that, everything was GONE... so I decided I might as well load a new up-to-date ROM. Was using Akeo's rom happily before that.
Did the usual SPL routine, new radio, new OS rom.
Installed new stuff...
But then phone would continually enter bootloader screen most of the time when I did a soft-reset. Except that it would have a terrible error message that only gave me the option of trying to restart without changes or basically reset everything to original settings (or something like that which meant everything is gone again). With the error message in place... nothing would work.
Could not reset into normal bootloader. (without the error message)
Windows mtty.exe method could not connect. (it would under normal bootloader)
Activesync was obviously disabledsync.
Flashed radio, spl and OS roms repeatedly using Des' SSPL and Olio's HardSPL 1.20 and 1.30 to no effect. It would always come back with that error on a random reset.
Then I read about the method of flashing with SD card. But this didn't solve my problem... it would come back still after a reset.
Mtty.exe from Windows XP to format nand and mark bad blocks etc.
Nothing found.
Finally, I almost gave up.
Then out of desperate measure.
I decided to leave a copy of a TRINIMG.nbh in the SDcard for GOOD!
It's basically an SPL image. Done with the NBHutil.
Used it to split out the HardSPL 1.30 spl.nb and merged it with the splash.nb and sub-splash.nb from my current OS rom.
Everytime I reset... there's still a chance it will enter bootloader mode with that horrible error message. But in such a situation... I now simply choose not to reset settings to default and instead simply pull out the battery.
Then plug it back in and power it on again. 80% of the time... it boots back into Windows mobile like normal on the first try! No loss of settings... nothing nasty. Back to normal! The other 20% of the time? I just pull out the battery and power it on more times! Till it works! Hasn't failed me yet in 5 days. Mind you, I was bricking it twice a day before this. That's progress!
I simply use SPL backup to make a full backup anyway whenever I install any new software etc, contacts etc.
Give it a shot.
I don't know why it worked for me...
Maybe I have bad sectors or something where the SPL is.
Whatever it is... the SDcard's TRINIMG.nbh works as my SPL now.
Think of it as a case of a bad bootup sequence on an old dos system needing a backup msdos bootdisk to do the trick!
Good luck!

Complete and utter noob in help.

Right. I bought this phone (second hand, flashed with shifu 4.2 ROM {I have no clue what this means}) and it worked perfectly. It didn't come with a sim, so I went out and bought two. An O2 and an Orange one. The O2 one had problem's activating, so I placed in the Orange one. The phone somehow screwed up, saying iLockV2.exe is corrupt/could not be found. So, I contacted the seller, he told me to do a hard reset, which I done. The phone worked fine from there.
This afternoon, the phone froze, so I took out the battery and put it back in. The same problem occurred with the iLockV2.exe thing above; so I tried to do another hard reset, it didn't work. After that, I was stuck at the HTC screen where it says:
Code:
R 1.71.09.01
G 25.75.40.02.
D 3.34.shifu
.
I then took out the battery again, and the same thing happened. So I took out the battery once more, and when I pushed the power button it wouldn't turn on. So, I took the battery out and left it for about 4 hours, and put it back in, but now, I'm still stuck at the HTC boot screen (same code as above).
What do I do to make my phone work again?

koglaa said:
Right. I bought this phone (second hand, flashed with shifu 4.2 ROM {I have no clue what this means}) and it worked perfectly. It didn't come with a sim, so I went out and bought two. An O2 and an Orange one. The O2 one had problem's activating, so I placed in the Orange one. The phone somehow screwed up, saying iLockV2.exe is corrupt/could not be found. So, I contacted the seller, he told me to do a hard reset, which I done. The phone worked fine from there.
This afternoon, the phone froze, so I took out the battery and put it back in. The same problem occurred with the iLockV2.exe thing above; so I tried to do another hard reset, it didn't work. After that, I was stuck at the HTC screen where it says:
Code:
R 1.71.09.01
G 25.75.40.02.
D 3.34.shifu
.
I then took out the battery again, and the same thing happened. So I took out the battery once more, and when I pushed the power button it wouldn't turn on. So, I took the battery out and left it for about 4 hours, and put it back in, but now, I'm still stuck at the HTC boot screen (same code as above).
What do I do to make my phone work again?
Click to expand...
Click to collapse
First of all, stop taking out the battery when the phone is on because that really screws up the files. You are doing more harm than good there.
Try a series of soft resets to try and fix it. If that doesn't work, try a series of hard resets to solve the problem.
If no luck there, go into bootloader ( tri color screen ), hold in power and camera button at same time while doing a soft reset. The try flashing a stock Orange rom ( found in the wiki ) Then re-flash with shifu rom.

Not letting me hard reset, so I'm just going to reflash (Y). I hope I do this right :\
EDIT:
My computer can't read my phone when connected via usb D:

koglaa said:
Not letting me hard reset, so I'm just going to reflash (Y). I hope I do this right :\
EDIT:
My computer can't read my phone when connected via usb D:
Click to expand...
Click to collapse
What does the phone do when you try to hard reset ?
When you put your phone into bootloader what does the screen say . When in bootloader, does the bottom of the screen change from serial to usb when you plug it in to your pc ?

denco7 said:
What does the phone do when you try to hard reset ?
When you put your phone into bootloader what does the screen say . When in bootloader, does the bottom of the screen change from serial to usb when you plug it in to your pc ?
Click to expand...
Click to collapse
The phone just soft reset's when I try to hard reset.
And yes, it does change from serial to usb when I plug it into my computer

Seem's like I was doing the hard reset wrong. Same thing is still happeneing, not getting past the part where it says:
Code:
R 1.71.09.01
G 25.75.40.02.
D 3.34.shifu
EDIT:
After 20 or so hard resets, I've moved onto the boot-loader, then it took about 5 minute's to load to the main OS. I think everything is sorted out now. Thanks

omg, this is getting really annoying now. The phone keeps on crashing at random interval's and can only be recovered by hard resetting :\

Well if it keeps happening try a different ROM just make sure you follow F.A.Q for ROM your flashing.
The thing that it's saying is corrupted is S2U2 and to me sounds like it just can't find the .lnk in Windows StartUp.

Flash OEM Rom before the new one and if you have 2GB or smaller SD Card flash using the SD Card method.

stylez said:
Well if it keeps happening try a different ROM just make sure you follow F.A.Q for ROM your flashing.
The thing that it's saying is corrupted is S2U2 and to me sounds like it just can't find the .lnk in Windows StartUp.
Click to expand...
Click to collapse
It happen's when the phone freeze's and I soft reset it :\

koglaa said:
It happen's when the phone freeze's and I soft reset it :\
Click to expand...
Click to collapse
I'd go with what Philux-X says "to which is why i said F.A.Q" try and flash a stock ROM prior to flashing custom so as to clear nand.
The corruption due to stalling sounds pretty normal as the phone does not get to shut down via the usual method.

stylez said:
I'd go with what Philux-X says "to which is why i said F.A.Q" try and flash a stock ROM prior to flashing custom so as to clear nand.
The corruption due to stalling sounds pretty normal as the phone does not get to shut down via the usual method.
Click to expand...
Click to collapse
I'll do that next time it crashes .
Thanks for all your help guys