Database Develop

Stuck in bootloader

Hopefully, someone can help me fix my f*ckup...
I attempted to flash the qtek "test" rom to my I-mate K-jam branded wizard. The flash worked, and the customisation from the extnded rom completed.
then the fun began...
the device booted, and hung at the splash screen. I soft reset, and it hung at the same point. I then tried a hard reset, and it still hung...
At this point, I thought "oh well" and tried to flash back the old os.. which wouldn't work, as I couldn't get an activesync connection. so I put the device in bootloader, and flashed the rom. but.. it's now stuck in bootloader. no combination of soft or hard reset will allow it to boot, but I can flash roms.
anyone got any ideas?
thanks!
<edit>
Just a quick update.. flashing button's custom rom image got me out of bootloader, and booting as far as the splash screen again, but showin the old i-mate, not his pint..
I'll keep tinkering, and hoping that someone has a clue what i've screwed up.
</edit>

2 others with same problem
You're not alone...
http://forum.xda-developers.com/viewtopic.php?t=40871

Yeah, I saw
Sadly mine came from ebay, so returning it's going to be hard!
Hopefully, it's fixable.

It looks bad!! I'm afraid
I've given up and hopefully will get a replacement from T-mobile?? Somebody suggested I try running the battery down. I did this and now it won't start at all or even charge - so it's now well and truly dead!!!
I think whatever we have all down is terminal - as you say you can't even run activesync. Hope you didn't pay too much for your ebay wizard?!

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.

'No GSM' after numerous radio version flashes

I tripped over my usb cable while flashing an official orange rom + radio version a few months ago, and bricked my trinity. Left it on a shelf for ages & decided to try to revive it a few days ago.
The problem was that the thing kept hanging after the splash screen, all the backlights would go on and it would hang. I managed to splxploit it to get hardspl back on there (olipro 1.3) & successfully flashed a few OS roms from here but it still hung on the (now different) splash screen. Realised that the 'No GSM' thing was a killer, so tried reflashing a few radio versions, and that worked fine as far as the flash was concerned through USB / HSPL.
However, it still says 'No GSM' and hangs at boot. Any ideas? I've run all the tasks from mtty with spl-1.30lipro, the CID shows the HTC SuperCID(hex) etc successfuly, and it formats the OS portion successfuly. Task 2a, like with others, just returns a new prompt after a second or so.
I've got radio 1.56.70.11 on there apparently. It still says 'No GSM', although this goes away a lot quicker now, whereas before it would hang with that on the screen...
Help?? Should I throw it in the bin?
Thanks a lot, any help is much appreciated...
Nik

you've killed the radio BL in that case, bad timing on your part, sadly it's unrecoverable.
the only fix is desoldering the radio chip and soldering a new one in.

Have you tried whith the version 1.20? The version 1.30 gives some trouble flashing the radio

same problem...no way for me in this moment!
do you solve?

flash with hard-spl 1.20 ou crash'n'proof... then try again... it works with me

serbington said:
I tripped over my usb cable while flashing an official orange rom + radio version a few months ago, and bricked my trinity. Left it on a shelf for ages & decided to try to revive it a few days ago.
The problem was that the thing kept hanging after the splash screen, all the backlights would go on and it would hang. I managed to splxploit it to get hardspl back on there (olipro 1.3) & successfully flashed a few OS roms from here but it still hung on the (now different) splash screen. Realised that the 'No GSM' thing was a killer, so tried reflashing a few radio versions, and that worked fine as far as the flash was concerned through USB / HSPL.
However, it still says 'No GSM' and hangs at boot. Any ideas? I've run all the tasks from mtty with spl-1.30lipro, the CID shows the HTC SuperCID(hex) etc successfuly, and it formats the OS portion successfuly. Task 2a, like with others, just returns a new prompt after a second or so.
I've got radio 1.56.70.11 on there apparently. It still says 'No GSM', although this goes away a lot quicker now, whereas before it would hang with that on the screen...
Help?? Should I throw it in the bin?
Thanks a lot, any help is much appreciated...
Nik
Click to expand...
Click to collapse
Definately, don't throw it away. It's still worth $$$. A lot of people can use it for parts if you don't get it working. Offer it up for sale on here if that's the case.

Olipro said:
you've killed the radio BL in that case, bad timing on your part, sadly it's unrecoverable.
the only fix is desoldering the radio chip and soldering a new one in.
Click to expand...
Click to collapse
hi you know radio bl? any schematic to know.. im curios whats does it look like,?

Help! Problems flashing X1

Hey everyone. I'm tearing my hair out trying to get this sorted but I just don't know what to do!
So, when I got my X1 as everyone on here should do, was flash my X1 with the HardSPL and some custom roms, this was a few months back. Then, shock! Horror! My case went and broke, (cracked near the volume button build W44) so I sent it back to SE for repair. I sent it back reset back to defaults but left the hardspl on there.
SE sent me a brand new phone (I think... This one says under the battery build w50, but the battery says w32..) I received it today. I thought it would be my old one repaired but SE had other ideas. Booted up and have Image Version: 1.03.931.10 and HardSPL 72.000 I think I said that correctly...
Now since sending it for repair and receiving it back, their seems to be quite a few wm6.5 roms floating about, and obviously I can't use the stock software as that wouldn't be right!
Now I have tried flashing the hardspl to the phone through my Vista PC and all it keeps giving me is connection errors. I thought maybe it was already flashed so I tried flashing just a rom, and that just made the phone get stuck on loading (flash by memory card). I thought it might be Vista, so I tried doing it on my other PC (XP) and I get the same issue. This bloody thing won't flash!
I have had "Connection Problems" - "Update Errors" with different numbers. The current one being Error [260] CONNECTION.
Now I have been searching around through the hardspl thread and other places trying to find out what I need to do or how I can fix it, but everything I try doesn't make a difference. I did read some other people with recently repaired phones having the same problem and perhaps SE have put a new spl thingy-ma-jiggy on there. (Please forgive the technical jargon, I have no idea what im on about.) I have also tried the ticking/unticking advanced network functionality, but that hasn't made a difference either.
So by the end of typing this, I have little hair left. Let's hope you can all help, before I have none left!
I would appreciate ANY help! Really.
Just wanted to add, I was at first getting the phone to a loading bar when flashing, but it would stay at 0% then flag up an error on the PC. Now after the tri-colour bars, the phone just sticks on Loading...

Well just to update. I have been trying to sort this since posting. I flashed the rom to an old UK generic one, as I read in another topic people had to do that before HardSPL. Done that, and tried flashing the hardspl. Same thing, just getting connection errors.
I tried going into bootloader and running the hardspl from there. It works and the phone gets to 10% and then gives an UPDATE ERROR. The phone is now bricked, and I have to reflash the original wm rom to get it back.
Though the Tricolour screen now shows 0.52.Olinex
Any ideas?

Shameless bump for help.

very stupid situation.
i have the same situation in puncto of flashing.
i get my phone three month ago.
after hardspl i .... sorry, no hardspl ... the phone says at 0% bla bla bla
i solve the problem by consulting one night absolutly stressing again and again and again .... google ... xda ... google
than 3 thinks at one time was the solution:
0. need activesync - connect !!!!
1. SDA_ApplicationUnlock.exe for desktop pc
2. enterbootloader.exe for pocketpc (please, the right version, it exist for eten too, but we need the xpediaversion ..)
3. changing registry-entries
how to:
activesync-connect, than copy "enterbootloader.exe" to pocketpc. it must be root, not sd-card. use a pocketpc-registry-program to change these values :
HKEY_LOCAL_MACHINE\Security\Policies\Policies\00001001 = 1
HKEY_LOCAL_MACHINE\Security\Policies\Policies\00001005 = 40
HKEY_LOCAL_MACHINE\Security\Policies\Policies\00001017 = 144
HKEY_LOCAL_MACHINE \Security\Policies\Policies\0000101b = 1
if not exist than add the key.
now, start desktop-program, follow instruction EXCEPT reboot.
start "enterbootloader.exe" on pocketpc. now, you can install hardspl and the device is flashable for ever.
thats works on me, hope it could help you too.

Thanks for the reply. Not had time to try it till this morning. Ok so, after spending about an hour trying to find the correct enterbootloader.exe I finally realized, that the hardspl package includes it. *Duh!* So that was time wasted.
I changes the registry values as you said with Resco registry editor, and follower the unlock then enterbootloader.exe Start HardSPL package. Starts to install. Gets to 10% then I get
ERROR [262] : UPDATE ERROR
The rom update utility has encountered communication errors during the update process.
So im open to suggestions if anyone has any. I just can't understand why it's not working. It's not a problem with my computer or cables. I flashed the phone before I sent it for repair and I have tried doing it on two computers one with XP 32bit and one with Vista 64bit.

hmm. would u like to install a custom rom, or a stock rom?
msg me, and i hope, i can halp u.

I want to have the hardspl on there so I can flash custom roms.

If it's a case of the software/firmware/hardspl whatever you call it, has been updated by SE. How would one go about getting it flashed? Would we have to wait for an update HardSPL to be released?

U read this thread?
My first hardspl was from this thread. New X1 will come tomorrow back from SE (vibration was defect +++ some more problems with case), and i will try it again with this thread.
hope, this will help u mate.

Yeah, I have been through that thread with a fine toothcombe trying everything suggested to see if I can make it work.
When you get yours back, if you have to do anything out of the ordinary to get it to flash or can't do it. Please come and let me know in this thread. If they have updated yours like mine, and yours won't flash, at least I won't be the only one!

k, i will msg u tomorrow around 2pm.

Cheers.
In the meantime. Does anyone have any other suggestions I could try?

Bump, for some help.

now i know, what is exatcly your problem.... <--- SAME Problem
i hope, i will find a solution and msg u then. if u´ll got a solution for this prob, msg me too plz.

Solution found in this Thread!
Download this and unzip it to your device. ++ run it. It will start your X1 in Bootloader menu and say "0.52.OliNex".
Then start hardspl while X1 is in Bootloadermenu....
FINISH =)

Thanks for the reply matey. Glad you got yours sorted. Just tried what you said and I get 0% then it switches to ERROR [262] : UPDATE ERROR.

vwrmic said:
Thanks for the reply matey. Glad you got yours sorted. Just tried what you said and I get 0% then it switches to ERROR [262] : UPDATE ERROR.
Click to expand...
Click to collapse
hmmm... it works fine on my new x1. are u sure, that u start the ssplmanual on your x1 and not on your computer?

Yea, im not sure what the problem was with it. Thankfully I have it done and dusted today! Because I flashed it earlier to an older official version, and you said you got it working. I presumed you had - had yours flashed to the newest version due to it being off for repair. So I reflashed the official update and fully updated it. Then tried hardspl which didn't work. Tried with the advanced USB thing off, tried again with how you said you did it above, and Viola!
Hip hip hoorah! Thanks for the help. Can finally use me bleedin phone now!

no problem mate hf with your x1

hello,
i see smilies and yea's ...
for me to understanding (for next time or other users):
1. complete official update (if exists)
2. flashing (hardspl) without "advanced usb"
thats all?
cool.

Restore from Bootloader?

I tried to upgrade my 8125 using Shelltool earlier this week. I used the tool successfully before and so I was assuming that things would just go well.
Unfortunately, I ended up being stuck on the bootscreen. I can also still go into Bootloader mode and so I figured all I need to do is to download the Wizard Love ROM, go into Bootloader mode and apply the ROM to restore an older version. Well, for some reason the RUU utility keeps telling me about a communication issue even though I already disabled USB in Active Sync and I also killed the program using Task Manager...
What am I missing here? I am hoping that someone can enlighten me...
Thanks,
Jens

For some reason I was finally able to flash my 8125 with the Wizard Love ROM this morning. Flash completed and I was back to an old working ROM.
Unfortunately, when I flashed it with the latest CR86 it flashed fine, but then I am stuck on the Bootloader screen. Already tried it twice and just running it a third time, but I am puzzled...
Any help?
Thanks,
Jens

jstraten said:
For some reason I was finally able to flash my 8125 with the Wizard Love ROM this morning. Flash completed and I was back to an old working ROM.
Unfortunately, when I flashed it with the latest CR86 it flashed fine, but then I am stuck on the Bootloader screen. Already tried it twice and just running it a third time, but I am puzzled...
Any help?
Thanks,
Jens
Click to expand...
Click to collapse
its on its last flashes my friend(or maybe just tire of custom roms)
but just before mine died, it would do that, until i was stuck on the bootloader and the screen would just die, i would have to leave it off then turn on but the same, after that i just left it alone
i could not flash anything on it and i could not see it suffer anymore
i still have it but dont have time to bring it back to life, at least it blinks at me

That's what I was worried about...
Strange thing is I probably only flashed it about 10 times... Very frustrating!
Thanks for your reply!

Hmmm, I just tried the old Wizard Love ROM again and it worked right away.
What am I missing here? I am trying to get to the new CR85 6.5 ROM, but I always end up being stuck on the bootscreen loader. I mean it shows me the HTC screen, but then it goes straight to the bootscreen...
Any suggestions?

I am back in business!
It turned out that flashing back to an older ROM disabled my HardSPL. I guess a case of user error on my end...
Anyhow, I also experienced the fading display mentioned above and I think that's just a sign of a weakening battery. It seems that the phone doesn't charge fast enough over USB in Bootloader mode.
So, if you run into the same problems like me:
- Charge your phone using the charger when you are stuck in Bootloader mode for extended amount of times!!!
- Flash an old provider ROM or Wizard Love ROM
- Re-apply HardSPL if needed
- Upgrade to a newer ROM
Cheers,
Jens