HELP ME! My Tilt Is Bricked. - Tilt, TyTN II, MDA Vario III General

Ok, so today I tried to flash my Rom with the official att 6.1 rom from HTC. I got it to finally start flashing after about ten tries but when it reached about 13% it gave me an error 276 I think. I tried the recovery method suggested by removing the battery for 3 seconds and reseting the device but now my device isn't recognized in windows and I can't run the upgrade file anymore.
It just goes to the bootloader screen with "KAIS1*0" on the top, then "SPL-3.02.000" below that, and "CPLD-8" below that. At the very bottom it shows USB but my computer doesn't recognize the device. I've tried hard reseting it and it just goes back to the bootloader screen.
Is there any way I can get my Kaiser back or am I screwed?? All this waiting for 6.1 and now my phone is dead. What a load of crap.

Just re start the ruu and let it sit for a minute when that happens, it will start again by itself. Almost shat myself when it happened to me.

First of all, relax. Your phone is not bricked. Do a little looking around the forums and you will resolve this.
I am too lazy to search for him but is the 3.02 SPL compatible with the 6.1 ROM?

I can't restart the Ruu because I can't get a usb connection to my phone. The bootloader goes into usb mode but my computer does not see the phone. The Ruu says it cannot detect the phone either.

Isn't there a way this guy can re-flash using a MicroSD card?

MineralGray02K said:
Isn't there a way this guy can re-flash using a MicroSD card?
Click to expand...
Click to collapse
I'm not sure if the OEM SPL has the ability to flash from card like the Hard SPLs.
To test put the Carrier ROM (Download from the Wiki) on to the root of the MicroSD Card and call it KAISIMG.NBH. Turn on the Phone with the Camera Button Held Down. It should try and flash the ROM then. If that doesn't work, I have a thread and wiki page all about getting stuck on the bootloader, check my Sig for more info.
Hope this helps.
Dave

rodavery said:
Ok, so today I tried to flash my Rom with the official att 6.1 rom from HTC. I got it to finally start flashing after about ten tries but when it reached about 13% it gave me an error 276 I think. I tried the recovery method suggested by removing the battery for 3 seconds and reseting the device but now my device isn't recognized in windows and I can't run the upgrade file anymore.
It just goes to the bootloader screen with "KAIS1*0" on the top, then "SPL-3.02.000" below that, and "CPLD-8" below that. At the very bottom it shows USB but my computer doesn't recognize the device. I've tried hard reseting it and it just goes back to the bootloader screen.
Is there any way I can get my Kaiser back or am I screwed?? All this waiting for 6.1 and now my phone is dead. What a load of crap.
Click to expand...
Click to collapse
run this while phone is hooked up to computer stuck in bootloader.

Sweet Jesus
Ok, I tried the tri-color fix from nufsaid. It didn't work b/c it couldn't open a usb port or didn't see the phone or something. Then I tried putting the rom on my microSD card.
And *SHAZAM* there it was. DaveShaw you are a god to me now. It said the update was successful but I'm still stuck in the bootloader. It used to work if I would plug it into the wasll charger and reset it but that isn't working now. My computer still doesn't recognize it so Mtty or anything still doesn't work.

Ok, I left my tilt on the tri-color screen all night long to run down the battery. When I woke up I tried to power it on and I got the familiar ATT flash screen but when I plugged it into the AC power it went straight into the bootloader.

I don't know what's worse, bootloader or red light of death, I just experienced the red light, called att and got a new phone sent out in 12 hours! What SPL does your phone show? they might exchange if it's not 'voided'

ok, I finally got it to load the windows. If the battery has a high charge or is charging resetting won't get out of the bootloader. If I let the battery run down to almost nothing, wait a little while with it out, then try it again it will turn on. my spl is now 3.56.0000.

Finally
I finally got it out of the bootloader. I'm never going to reset my phone again. It's gonna suck if it freezes. Thanks for all the help.

rodavery said:
I finally got it out of the bootloader. I'm never going to reset my phone again. It's gonna suck if it freezes. Thanks for all the help.
Click to expand...
Click to collapse
Glad your back up and running. There are two new hard SPL's be cmonex (they are mentioned in the link in my sig) that make it less likley for you to get stuck at the bootloader. You could try those?
Ta
Dave

Related

oh my...did i brick my phone?

I cant believe this....I had no issues all day upgrading the ROM...until my PC overheated and shut off at 57%...
now when my phone starts up I see the 3 bars and it sais USB in the bottom left...but active sync is not connecting!
help!
what 3 bars?
a Red Blue Green Bars color?..
If that so.. you are too lucky..
I read a little more on the wiki:
Type 2a: When the phone boots, it goes directly to bootloader mode (tri-color screen)
This is what I have right now...I can't seem to get active sync to connect...although at the bottom of the screen it has "USB"
I have tried using mtty and dont think its diong anything...
Just stay in the bootloader (tri-color screen) and make sure the "USB" is shown in your device screen..
The reflash.. even if its not sync/connected.. just reflash the ROM..
Everything will be fine..
wow....i think it may actually work....that was SCARY.
nice to know the good ole button flash works when all others fail
I just want to make a clarification..
You are just flashing your device and when the upgrade process is on 57% your computer suddenly shutoff? and the upgrade was cut..
What happened next? did you reset the device then went to tri-color screen? or you just force bootloader mode it?
Yeah pretty much exactly what you said. I literally got up for a second to get some water, came back and saw the telltale sign that my pc had just shut itself off (the screen was black except for the standard boot junk that shows up).
So I look at my device (8125) and it was locked at 57% and was not responsive. I figured that the flash util probably wouldn't continue after the computer started back up (and besides, the device wasn't alive anymore) so I rolled the dice and unplugged the USB and took out the battery. When I put the battery back in and hit the power button, it went straight to the bootloader (the tri color screen).
- By the way - ive got the button image on here now - workin like a champ...
tnx for the explanation..
have fun!!..
thanks for the quick reply - i thought i was completely stuck but the button flash seemed to take care of everything. Makes me almost think that bricking this thing is near impossible... >
Yup!.. that also my conclusion.. its impossible to brick.. thats why i ask for your clarification..
What is this "button flash"? I am stuck in RGB boot mode with no activesync connection. I have read til my eyes crossed, but can not fix my 8125 (G3)!
Please advise.
How about more information? On your bootloader (Rainbow screen) what does it show the IPL / SPL to be? What were you trying to do when you got into this situation? What happened when you were flashing? Is your device a G3 or G4?
Safest thing for you to do right now is to flash your carrier's rom onto the phone (an official shipped ROM). With your phone in the bootload, just run the ROM and it will install (DO NOT RUN A CUSTOM ROM AT THIS POINT SINCE YOU HAVEN"T TOLD US ANY OTHER INFORMATION).
G3 8125
ipl/spl 2.25
Was trying to use faria's latest rom...got stuck at 99% for almost one hour, so I rebooted computer and discon'd the wizard. Now it will boot to rainbow screen and will not connect via activesync (so I can't utilize any other roms to get back to square one).
ActiveSync will NOT connect when you are at the boot loader. As long as you see USB in the bottom left of your phone (above the left soft key) then you can flash your original Cingular ROM and be good to go again.
brick, brick, brick
It happend to me too with faria´s new crossbow rom:
the device freezed at 99% and I reseted it then....nothing happend- bootloader mode: red green blue + usb... but no chance to flash ANYTHING... always the same message:ERROR (260) update error, no connection to the device...???
I tried the O2-mini s update, and the faria rom, no chance just a brick
I need help....
Hunter6 said:
It happend to me too with faria´s new crossbow rom:
the device freezed at 99% and I reseted it then....nothing happend- bootloader mode: red green blue + usb... but no chance to flash ANYTHING... always the same message:ERROR (260) update error, no connection to the device...???
I tried the O2-mini s update, and the faria rom, no chance just a brick
Click to expand...
Click to collapse
Why did you reset it??? All roms freeze. The screen that is flashing the ROM even says it can take up to 10 mins. If you don't get an error onthe PC then DON'T stop the flashing process.
Go get a copy of your carrier's official ROM (not a custom one, but an official one from your carrier.). Then with the phone at the boot loader (Rainbow screen) and the USB cord plugged, in, run the official ROM. If that doesn't work, then get a copy of the Wizard Love rom and flash it (You'll need to find links around here for it, or pull it via PirateBay). You may also want to reboot the PC you are running on and remove your SD card (if you have one) just to remove variables that can play in to all of this.
Good luck
mfrazzz said:
Why did you reset it??? All roms freeze. The screen that is flashing the ROM even says it can take up to 10 mins. If you don't get an error onthe PC then DON'T stop the flashing process.
Click to expand...
Click to collapse
Ten minutes is understandable, but mine stalled for about an hour at the 99% mark. Even my PC would not respond. Is that normal for a rom upgrade?
-----
I was finally able to reset my 8125 to the Cingular ROM. Not sure why I couldn't do it on my PC, but after moving over to my wife's PC I did not have any problems.
Thanks!
brick, brick, brick
o.k. boys, now it is a nice little crossbow brick from faria.....and I can make telefon-calls with my brick.
thanks a lot for your help
entdiablo said:
Ten minutes is understandable, but mine stalled for about an hour at the 99% mark. Even my PC would not respond. Is that normal for a rom upgrade?
Click to expand...
Click to collapse
No, that sounds like your pc locked up or something (I'd blame windows on that one )
I was finally able to reset my 8125 to the Cingular ROM. Not sure why I couldn't do it on my PC, but after moving over to my wife's PC I did not have any problems.
Click to expand...
Click to collapse
Glad to hear you got it going. Good luck and be careful out there!
Hunter6 said:
o.k. boys, now it is a nice little crossbow brick from faria.....and I can make telefon-calls with my brick.
thanks a lot for your help
Click to expand...
Click to collapse
Sorry, I may be missing your humor or sarcasm... Are you saying its dead (if so, give more details about what it does or doesn't do, IPL/SPL it shows (if it turns on), etc... If its now working, then congrats!

Kaiser Issue - Bootloader only .. OS suddenly won't load.

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 !

Help!!!!! Urgent!!!!!

this morning, I restarted my x1 because it was awfully slow this morning. so after I restarted it, it stayed at the sony ericsson splash screen for long time and didn't do anything. I tried to reinstall the rom through SD and it didn't work. Then I hardspl-ed it and tried to reinstall one of my old kovsimg.nbh in it, then now....it won't even turn on!!!
Did I brick my x1??? HOW IN THE WORLD CAN I FIX IT?
my battery is fully charged btw. PLEASE HELP. THIS IS URGENT!!!!!!
I've checked on different forum guides on here and none of which seem to be having what I am looking for.
UPDATE: i just plugged in my phone to the computer and then it popped out a notice on my computer saying that the device is not recognized. "the device is malfunctioned and does not recognize it."
@[email protected]" so what am I to do? do I return it to the store and get them to fix it or is it better just to give it up?
Have you tried a hard reset?
I have, but still no reaction...
I am guessing the x1 is still safe in a sense since the red light is still on.
Can you put it in booloader mode? If so, what version of the spl do you have?
the Phone won't even turn on. no possible way to get into bootloader. when you say spl as in hardspl and also softspl. i'm not quite sure. i just found it on this forum in the latest forum updates.
asian_boi said:
the Phone won't even turn on. no possible way to get into bootloader. when you say spl as in hardspl and also softspl. i'm not quite sure. i just found it on this forum in the latest forum updates.
Click to expand...
Click to collapse
Have you tried taking the battery out for ten seconds, put the battery back in, then hold the power and volume down keys until you see the tri color screen. Does this work?
yes. I've done that.
the phone still can't be turned on.
need help too
i just tried to Hard SPL my phone, and now i'm on the bootloader screen
showing KOVS110
SPL-0.72.OliNex
Micro P1 -787
Micro P2 -707
and it says continue to upgrade ROM please wait. i've been waiting for for a long time. it stucked there. i take off the battery for few second and put it back it shows the same screen again. And i need to use MTTY to boot it to get into window mobile. i was trying to Hard SPL the NEW ORIGINAL X1 ROMS INCLUDING R3xxxxx update 1.10.2009. and i can't upgrade it. everytime i restart my phone it goes back to the bootloader screen and freezed there. then i need to use MTTY to boot it and bring it alive again. can anyone help me out with this? pls

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

HELP! Unable to connect after flashing

Hello, Im sure that there is a thread somewhere with the answer to this question but i have searched and searched and cannot find it anywhere. I was trying to flash the new version of EnergyROM on my Tilt 2. I ran Task29 and now im at the bootloader and it shows USB on the phone but my computer is not recognizing my phone. I accidently left my SIM card and MicroSD card in when i did this. Can someone please help me.
i went out and bought a card reader and got my ROM on the card and plugged it into the phone and turned it on and it didnt do anything and now im stuck at a black screen with the red light on. the phone wont turn on wont reset wont do anything i just bought this phone 2 weeks ago and i hope i didnt completely screw it up.
jeepin304 said:
Hello, Im sure that there is a thread somewhere with the answer to this question but i have searched and searched and cannot find it anywhere. I was trying to flash the new version of EnergyROM on my Tilt 2. I ran Task29 and now im at the bootloader and it shows USB on the phone but my computer is not recognizing my phone. I accidently left my SIM card and MicroSD card in when i did this. Can someone please help me.
Click to expand...
Click to collapse
first of all is your phone hard spl'ed ?
running task29 completely wipes the entire os of the phone which is why your phone won't boot all the way
all you have to do is put phone into bootloader mode by holding down volume button while pressing the power button at the bottom of your phone screen it should say serial
now plug phone into computer it now should say usb at the bottom of your phone screen
from here flash whatever rom you are trying to flash & you should be good to go
hope this helps
yes its hard SPLed. activesync doesnt recognize my phone as connected to the PC. I have since been able to somewhat get it off the black screen and back to bootloader and it starts the process of flashing the new rom but then goes back to a black screen.
jeepin304 said:
yes its hard SPLed. activesync doesnt recognize my phone as connected to the PC. I have since been able to somewhat get it off the black screen and back to bootloader and it starts the process of flashing the new rom but then goes back to a black screen.
Click to expand...
Click to collapse
since you task29'ed activesync is not going to recognize your phone until you flash a rom to it
1.task29
2.flash stock rom
3.task29 again
4.flash new rom
alright now im just stuck with a black screen everytime it starts to flash the new rom it will get about 20-25% and then go back to the black screen. im wondering if my battery isnt charged enough to flash the new rom on there but it doesnt seem to want to charge
well i was making progress until the phone wont stay on long enough to complete the install, it will load the bootloader screen and start to update the new ROM and then before it starts it will go right back to the black screen...any ideas on why?
alright sorry to keep blowing up this post but now i have the ROM flashed but when i turn on the phone, it gets to the ATT boot up screen where the RGB things are and then goes right back to the black screen now what is wrong?
Is the rom you downloaded and attempted to flash CDMA or GSM? If am not mistaken, AT&T is GSM and if you got the rom here chances are you got a GSM one. However, I would double check to see if that's the problem
i got the GSM version it was working until i tried to update from the Dec 27 version to the Jan 6 version of the ROM. im pretty sure ive bricked the phone it just keeps restarting itself itll boot up then get to the BRGD screen and act like it wants to start up but then just shuts back off
is there a GSM and CDMA version of Task29? i dont know what ive done wrong but i really truely hope i havent bricked my phone but im pretty sure i have.

Categories

Resources