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
Related
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?!
I am not sure what I have done. I have a cingular 8125 G4. Downloaded the Risidioro g4 rom upgrade and my phone was not probably CID unlocked. Thought that did not matter cause I was able to install Mr Clean ROM couple of months back. I read some users in the forum who successfully upgraded from Mr Clean.
Everything went nice and smooth, the upgrade completed 100% and when it finished and rebooted it stopped at the blue, red screen and got stuck there. I did soft reset, hard reset but every time that blue, red screen comes up and gets stuck.
Has my phone become a "nice but dead piece of furniture" ? Oh! man..that would devastating!
Please help!
BigMonty
All right, no response yet but it is only a hour since I posted but for me it seems eternity already. I did something further reading and got some hope. My phone might not be dead yet. Somebody said, if I can get to the bootloader mode, I still have some hope.
I did some trick on hard resetting found here
http://forum.xda-developers.com/showthread.php?t=268836&highlight=dead
but to no avail.
Any other idea?? Cry!! Cry!! Cry!!!
Got another guy who successfully got out of the jail by having a SD image. Do you think it would work for me too? If it works where can I find it? I already e-mailed the guy, seems like a nice guy, let's see if he replies.
http://forum.xda-developers.com/showthread.php?t=274471&highlight=dead
Do you see a USB connection if you connect it to Active sync, normally it is showing in the lower left or right corner, I'm not sure.
If so, you should be able to re-flash again, best would be to do this with your previous installed ROM.
Btw,
Spl 2.25.0001
Ipl 2.25.0001
Can somebody suggest what would be most suitable ROM to go for once I am in the bootloader screen?
Vilem said:
Do you see a USB connection if you connect it to Active sync, normally it is showing in the lower left or right corner, I'm not sure.
If so, you should be able to re-flash again, best would be to do this with your previous installed ROM.
Click to expand...
Click to collapse
Thanks a lot Vilem for your reply. Yes I see a USB connection..but I guess we can't get to activesync because the OS did not load yet. I had the Mr Clean ROM installed and I tried to go for it but failed. What should I do now? Go for the original shipped Cingular ROM?Anybody knows which version it was and where can I find it?
bigmonty said:
I see a USB connection..
Click to expand...
Click to collapse
Means connected, try it. Mine crashed a couple of times like that and managed to get it going again.
You mean I should run the Mr Clean update utility which is the last successful ROM update or the orginial Cingular shipped ROM?
bigmonty said:
You mean I should run the Mr Clean update utility which is the last successful ROM update or the orginial Cingular shipped ROM?
Click to expand...
Click to collapse
try the last succesful.
bigmonty said:
All right, no response yet but it is only a hour since I posted but for me it seems eternity already. I did something further reading and got some hope. My phone might not be dead yet. Somebody said, if I can get to the bootloader mode, I still have some hope.
I did some trick on hard resetting found here
http://forum.xda-developers.com/showthread.php?t=268836&highlight=dead
but to no avail.
Any other idea?? Cry!! Cry!! Cry!!!
Click to expand...
Click to collapse
Bigmonty - after getting into allsorts of issues after trying to upgrade my G4 to various 3.2 based ROMS, i also got to the bootloader screen with the USB indicator in the righthand corner.
This worked for me - take the battery out for an hour or so, put back in and soft reset. make sure you have a good charge. reboot the PC and plug in the device.
Now the only ROM i can recover a working device from isto use the latest ROM from the phone supplier. in my case from the club i-mate site (my device is SIM unlocked).
hope it helps
Thanks AirWol. I was able to go back to Mr Clean successfully, which was a great relief. What I was doing wrong was, I was using the wrong update utility of Mr Clean. I should have used the one which was modified according to Risidioro guide for use in g4 chips. But I was using the original Mr Clean instead.
BTW, anybody knows whether it is possible to update g4 phones to the latest Risidioro or Cingular 2.26 ROMS? That is, can I modify according to Rididioro guide for use in g4? Anybody?
Probably I haven't learned enough lessons yet!
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'm not sure why, but my 8925 shuts down after the vibrate and the att screen comes up. It doesn't get to the 3G splash. I tried to enter bootloader, but to no avail. I guess the power isn't on long enough. Is there any other way to get into the bootloader mode so I can try loading a new rom or at least hard spl. I tried a battery from my other tilts and same response. I've tried the hard reset also, but nothing. This is my first post so hopefully its in the right section. I've flashed many roms, etc, but not on this machine (still running att rom) so I know just enough to be dangerous. But this one has me stumped. Its out of warranty, so this is my last hope. Thanks for any ideas you may have!!
please go read this thread and start from there...there are quite a few links that you help you in that thread..
http://forum.xda-developers.com/showthread.php?t=433835
when you go into that bootloader, make sure the camera button is ALL the way down, and also click that link up there ^
Hello there,
I messed up my just acquired used HTC Breeze. Isn't too bad, as it wasn't so expensive and it had SIM lock anyway. So hadn't I done anything, then I wouldn't have been able to used it as well.
My question: The info 2 - command returned "HTCSF kEØ(HTCE", so as far as I understand the bootloader has been bricked. But why can I still get to the three-color-screen? I always thought, this is only possible, if the bootloader is not bricked. I'm very sure I read about that regarding a HTC Canary.Or isn't that the case anymore with never devices?
In case anyone's interested, the whole story:
I tried the Hermes unlocker-method, but couldn't get it to work. The first problem was, that SSPL didn't work, because my phone was app-locked. Well removing the app-lock wasn't that hard.
I eventually managed to find out, how exactly this SSPL-stuff works. However, I still couldn't use the Hermes-unlocker. Flashing with SD-card wouldn't work - and using the RUU would only cause the phone to reboot, hence leaving the SPPL and being stuck with the normal bootloader, which wasn't unlocked (sorry if that sounded too untechnical - you probably know, what I mean).
So my last hope was the thread "Application UNLOCK/SSPL/HARDSPL" . First I upgraded to SPL 1.09 (might have been a bad choice, as I didn't think it through). Phone would still work then. Then I tried RUU_MTeoR_1.34.251.1_1.38.00.10_HTCEUR_SHIP , which is where I probably broke my bootloader, as it wouldn't start the OS after successfully flashing. (although it was IPL 1.00 and SPL 1.09, if I remember correctly).
Then I flashed RUU_BREE100_1.13.251.2_1.06.00.10_QtekEUR_Ship_R3 via SD-Card, cause it's said to have SPL 2.05. With that I wanted to do the final step in the said posting - flashing hardspl, so that I'd get SPL 7.77 anytime, without SSPL. I thought, the Hermes unlocker might work then. Only it was a dead end. After flashing to RUU_BREE100_1.13.251.2_1.06.00.10_QtekEUR_Ship_R3, I couldn't get anything to work anymore. And now I'm stuck with IPL 0.90 and SPL 1.09. End of the Story
If you can see three color screen (bootloader) that's mean it's ok Try flash with shipped ROM from the bootloader mode. I can upload it to you, but I have to know your device brand (CID lock)...