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?!
Related
Well, it seems that my BA finally broke (WM5 anyway). It happened when i was flashing back from a test rom to ivans latest version, i flashed, booted up and got to the wight screen, and stayed there... for 30 minutes. undettered i then tried every WM5 rom i could lay my hands on, but to no avail. in final desperation i downgraded to wm2003se and lo and behold it worked!
Anyone got any idea how to get wm5 working again on my ba?
just reflash back to WM5
thi is a rare bug, which occures, and the fix is downgrade to 2003 and then upgrade to WM5
done that, twice
have u tried to format your extended rom ?
there is topic out there, but show how to do it.
u could give that a try.
reflash everything including radio and ext rom, use radio 1.13, after flashing WM2003 try to flash WM5, please post the result. If this does not work i think it is a bootloader issue, if you can get the same version of boot loader and flash it maybe all will work.I am too scared to mess with bootloader yet.
http://forum.xda-developers.com/viewtopic.php?t=46867
Does anyone have command reference for BA bootloader trough mtty
[curse]
**** **** **** **** **** **** ****
[/curse]
right, i ran the mtty thingy, and reformatted the flash, i then went back to 2003se and storage and extrom were working , but then when i tried to go back to wm5 i kept getting a model id error even though i used xda3nbftool.exe to set the same one as in deveicedata.txt but to no avail, when i gave up to go back to wm2003se i found i couldnt exit bootloader! so i tried connecting again via mtty, it all went fine, ran the commands again etc but still stuck in bootloader. out of desperation i took out the battery, but now to my horror the phone wont even turn back one (yes, i've put the battery back in ). has anyone got a clue how to fix this?
Many thanks in advance....
edit - I just tried a bit of percussive maintanace on it and lo and behold... it began to boot
The only problem now is that the boot screen is f*cked up and i get a model id error whenever i try to upgrade roms (even the official orange shipped extract with no modifications wont run )
http://forum.xda-developers.com/viewtopic.php?t=49611&highlight=model+id+error
@Midget_1990
edit - I just tried a bit of percussive maintanace on it and lo and behold... it began to boot
Click to expand...
Click to collapse
"Percussive Maintenance" rarely fails. Nice term though - I'm sure I'll quote it.
Do post a link to the mtty command reference when you get it.
Cheers
- it just sounds better the 'i threw it at a wall'
I've got a weird one. Yesterday, my phone was running fine (I've had Dutty's rom on it for about 4months), I lost sound and needed a reboot. I rebooted and immediately got the RGBW bootloader screen. Successive reboots gave me this. I removed my flash card and tried again - was able to get in the O.S. but I still had no sound, so I rebooted again. Now I can't seem to get past the bootloader.
I'm probably going to try a reflash of the ROM, but I'm curious if there is another option since I'd rather not lose my data.
Any thoughts?
--Edit--
Bootloader screen says:
"KAIS1*0 MFG
SPL-1.0.OliPof
CPLD-8"
Bottom says: "Serial"
dude i am sorry to inform you but without an os back up is impossible
*just a thought - try removing SC Card and Sim Card and Remove Battery for some time then put everything back and try.. but most likely.. dont put lots of hope on this..
KyleK29 said:
I've got a weird one. Yesterday, my phone was running fine (I've had Dutty's rom on it for about 4months), I lost sound and needed a reboot. I rebooted and immediately got the RGBW bootloader screen. Successive reboots gave me this. I removed my flash card and tried again - was able to get in the O.S. but I still had no sound, so I rebooted again. Now I can't seem to get past the bootloader.
I'm probably going to try a reflash of the ROM, but I'm curious if there is another option since I'd rather not lose my data.
Any thoughts?
--Edit--
Bootloader screen says:
"KAIS1*0 MFG
SPL-1.0.OliPof
CPLD-8"
Bottom says: "Serial"
Click to expand...
Click to collapse
jahrami said:
dude i am sorry to inform you but without an os back up is impossible
*just a thought - try removing SC Card and Sim Card and Remove Battery for some time then put everything back and try.. but most likely.. dont put lots of hope on this..
Click to expand...
Click to collapse
Well, it's not a total loss. I have a backup of my settings from about 3 months ago and all my PIM data from 2 nights ago. I was just hoping to be able to recover most of it.
Thanks for the idea though, no luck. Here's hoping the new flash will work!
So I added the newest version of Dutty's - phone took it fine. I installed some apps, rebooted multiple times, worked for like 30minutes. Rebooted after installing one of the apps asked me to, and BLAM .. bootloader.
Would it be reasonable to assume that the ROM in this thing might be hosed?
Interesting I had the EXACT same issue yesterday with a the Default ATT ROM.. I was going to try Duttys since Its already wiped
Ransom342 said:
Interesting I had the EXACT same issue yesterday with a the Default ATT ROM.. I was going to try Duttys since Its already wiped
Click to expand...
Click to collapse
Yeah, mine seems to be fubar'd. I tried flashing Dutty's ROM again, it took the flash, rebooted, and immediately gave me the bootloader again with a blank image.
*edit*
Tried again with a different ROM. It got to the loading screen for the OS, as soon as I rebooted it went back to the bootloader with a blank OS.
Looks like my ROM is fubared. I think my warranty is up, or coming up very soon. Does HardSPL void it? Because I'd assume that is the only thing they can tell was done.
of course hard spl will void ur warranty but if u can revert to orgininal spl
http://forum.xda-developers.com/showthread.php?t=335568
KyleK29 said:
Does HardSPL void it? Because I'd assume that is the only thing they can tell was done.
Click to expand...
Click to collapse
Same issue - Semi Fix
Hi Kyle,
I started having the same exact problem three weeks ago (it is now Sep.18.2008). I've got no sound coming from my phone, and when I reboot I get the bootloader screen.
my FIX: Plug the phone into it's usb cable, and have it plugged into a source (computer, power jack, etc).
When I reset my phone with it plugged into the usb cable, it finds the rom and loads up perfectly. But when I reset without it, I get the bootloader. I still have not figured out why it is doing this. CAVEAT: this only works with my usb cable plugged into the power outlet of MY CAR. I know...it's weird...but that's what's working for me. When plugged into the computer I still only get the bootloader - it works in the car only. But I suggest you try your car, computer, and a wall outlet if you have one for usb and see what works for you. I find that I rarely reset my phone anyway, but it's just annoying when I do.
I hope this message hasn't found you too late :S Cheers
May anyone can help me ?
Kaiser 100 (TILT 8925) during Flashing, the battery was discharged. Now it does not join, the green light diode only burns at power ON attempt.
The computer defines it on USB as Flash device, but the driver from ActiveSynch do not approach.
How to restore it ?
What buttons for input in Flash mode (tricolor) ?
BR !
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,?
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
Ok hello again,
Its been 5 days without WoW trying to figure out what went wrong. Even if i cant get this thing working i'd like to know/learn 'why' it is bricked. But anyway. I recieved a kaiser [tilt] this past monday, my GF called me at work to let me know it came in the mail. After I got home I was ready to start flashing. Long story short, I was trying to upgrade to a HardSPL like i had done a couple times on my TP2. Something went terrible wrong somewhere between jumpSPL and somewhere else. The phone is now stuck in the bootloader. It did have RUUNBH in the top right corner but i got that to go away by flashing a shipped At&t rom back on the phone. But now it still wont leave the bootloader after completeing a couple different shipped rom updates. now the bootloader reads
KAIS1*0
SPL-3.56.0000
CPLD-8
I have usb support in bootloader but cant seem to get it to allow me to flash a new radio. So, i guess what my next question is what is the order I should try to try and recover this thing. Radio, SPL, Rom or some other combination. and thats it.
Thanks in advance,
Lord CraiguS
update
So i found, \RUU_Kaiser_CINGULAR_WWE_1.62.502.0_radio_sign_22.45.88.07_1.27.14.09R2_Ship.exe and it downgraded the spl to spl-1.93.0000 will see what i come up with after this.
ok after trying more shipped roms I DID get a hard reset to work, first time outta 100 tries. Altho it told me it reset the phone back to factory settings, I got the splash screen only to load up telling me the SIM cradle was unlocked and to lock it before continuing. Needless to say I didnt get it shut in time and it reset back to bootloader. In the wiki's ive seen that alot of bootloader looping errors occur with this device but none of the fixes seem to work for me. please help if you have any insight.
Lord CraiguS