Database Develop

[SOLVED] HELP! Xperia T does not boot after JB update

I updated my Sony Xperia T to 4.1.2 a few hours ago via PC Companion 2.1. Everything was good until I restarted my phone and it got stuck in the screen with white triangle and blue bar (after the Sony logo). I waited but nothing happens.
I've tried to force restart using power button + volume up (switching off using the power button alone doesn't respond) several times but it still get stuck in the same screen. I was able to repair it using PC companion and SEUS (both were successful) but when I turned on the phone the problem still persists. Restarted several times but to no avail. I cannot use my phone right now.
What seems to be the problem?
My phone is less than a week old, unlocked, stock and not rooted. I will try to flash 4.0.4 back using flashtool coz it was working fine before the JB update.

gabzki said:
I updated my Sony Xperia T to 4.1.2 a few hours ago via PC Companion 2.1. Everything was good until I restarted my phone and it got stuck in the screen with white triangle and blue bar (after the Sony logo). I waited but nothing happens.
I've tried to force restart using power button + volume up (switching off using the power button alone doesn't respond) several times but it still get stuck in the same screen. I was able to repair it using PC companion and SEUS (both were successful) but when I turned on the phone the problem still persists. Restarted several times but to no avail. I cannot use my phone right now.
What seems to be the problem?
My phone is less than a week old, unlocked, stock and not rooted. I will try to flash 4.0.4 back using flashtool coz it was working fine before the JB update.
Click to expand...
Click to collapse
Update: I flashed .233 using flashtool but still the same. Is my phone bricked?

gabzki said:
Update: I flashed .233 using flashtool but still the same. Is my phone bricked?
Click to expand...
Click to collapse
I have read that this process can take some time, flash a rom and give it at least upto 45 minutes, if it is still not working maybe you have a more serious problem.

Re: [Q] HELP! Xperia T does not boot after JB update
Flash a 303 firmware in flashtool instead of pc companion it never gets stuck for me weird some people have these problems
Sent from my LT30p using xda premium

Any news on that? i have exactly the same problem after flashing with PCCompanion.

Re: [Q] HELP! Xperia T does not boot after JB update
segataj said:
Any news on that? i have exactly the same problem after flashing with PCCompanion.
Click to expand...
Click to collapse
Just leave it be, plugged to the charger. I've heard of cases were it too about 3 hours to compete
Did I help? Please press the thanks button
Sent from my Xperia T (LT30P) using XDA premium

Re: [Q] HELP! Xperia T does not boot after JB update
I had this before, when going from 303 to 195.
Flash back the exact last full firmware you had prior to jb, if it was custom use the ftf the Rom is based on, it should boot, reset, then do the update again.
It took 35 mins to complete, I thought it was dead, once you get that screen, do not interrupt it or it can't complete and you need to start again.
Sent from my LT30p using xda app-developers app

OK, I was able to fix it and replicate it once but there's no certainty that it will not happen again once I restart the phone.
Here's what I did...
Since .233 did not work, I tried flashing the older firmware which is .303 - It worked!
I tried flashing .233 again to test if it has something to do with the firmware but it flashed without any problems!
I checked with PC companion to update to 4.1.2 but no update is available (since I used the UK firmware) so I flashed using the ftf file (.489) found here - it successfully flashed to 4.1.2!
HOWEVER, when the phone restarted (after inserting the sim card) and that's when the problem happened again! It stuck on the same screen. That's how I first encountered the problem earlier - the first reboot after updating caused for the phone to get stuck to that screen with white triangle and blue bar.
So I repeated the same process again (flashed .303 but skipped .233) then flashed .489 successfully but I DECIDED NOT TO RESTART THE PHONE this time. I'm not an expert so I don't know what's the cause of this??
My phone is working fine right now. Probably I will try to reboot the phone after 3 days to see if the issue comes back again.

segataj said:
Any news on that? i have exactly the same problem after flashing with PCCompanion.
Click to expand...
Click to collapse
Did the problem occur right after you updated? Or when you rebooted the phone for the first time after the update?
Mine was ok whether I updated via PC Companion or flashtool - the problem only happened when I restarted the phone for the first time after the update. So I tried not to reboot the phone on my third attempt. It's working fine now on 4.1.2. (as long as i don't restart it probably).
You can try the process I explained above and let us know!

gabzki said:
Did the problem occur right after you updated? Or when you rebooted the phone for the first time after the update?
Mine was ok whether I updated via PC Companion or flashtool - the problem only happened when I restarted the phone for the first time after the update. So I tried not to reboot the phone on my third attempt. It's working fine now on 4.1.2. (as long as i don't restart it probably).
You can try the process I explained above and let us know!
Click to expand...
Click to collapse
I've the same problem: https://www.dropbox.com/s/inagohwprijvc31/2013-02-02 10.27.02.jpg
I don't want void warranty... what can I do?

The solution for white triangle is, like DooMLoRD said, formating internal storage

dkownacki said:
The solution for white triangle is, like DooMLoRD said, formating internal storage
Click to expand...
Click to collapse
When more accurate to format the internal card?
Give me step by step if you think you know the cause of the problem.
Thank you in advance.

Fix to get JB Running
I had the exact same problem, a white triangle after flashing the JB update.
Here's how I solved it:
1. Flash a .303 stock firmware
2. Turn on your phone without Sim card and without MicroSD
3. Complete the Setup Guide (just pass the 7 steps).
4. Get Ready to flash the JB update (.489 I think)
5. EXCLUDE BASEBAND BEFORE FLASHING IT
6. It should work now (is working perfectly on my Xperia T since yesterday)
If this helps you, hit the thanks button, I'm trying to build a reputation here

Samper27 said:
I had the exact same problem, a white triangle after flashing the JB update.
Here's how I solved it:
1. Flash a .303 stock firmware
2. Turn on your phone without Sim card and without MicroSD
3. Complete the Setup Guide (just pass the 7 steps).
4. Get Ready to flash the JB update (.489 I think)
5. EXCLUDE BASEBAND BEFORE FLASHING IT
6. It should work now (is working perfectly on my Xperia T since yesterday)
If this helps you, hit the thanks button, I'm trying to build a reputation here
Click to expand...
Click to collapse
I mentioned in my process above that I will wait for 3 days before restarting the phone but I did it anyway to test your process. It didn't work for me.
I followed ALL the steps but after the phone restarted (when sim card was inserted) it got stuck on the same screen again. Have you tried rebooting your phone?
Looks like I'm gonna stay with .233 for now until this gets resolved.

dkownacki said:
The solution for white triangle is, like DooMLoRD said, formating internal storage
Click to expand...
Click to collapse
How do we do that in JB?
I noticed that after I flashed the .303 firmware the phone asks that internal storage be formatted (there's a notification in the notification bar). So I did that. But after updating to 4.1.2 the problem repeats again after the first reboot (stuck in the screen with white triangle).

Sounds like my problem has been solved. :good:
I repeated the process by Samper27 (except that I didn't remove the sim card; I don't have an sd card).
After updating to 4.1.2 I cleared the internal storage via the settings and performed a factory data reset - my phone restarted without any problems. I could switch it on and off now without getting stuck in that screen.

Great!
gabzki said:
Sounds like my problem has been solved. :good:
I repeated the process by Samper27 (except that I didn't remove the sim card; I don't have an sd card).
After updating to 4.1.2 I cleared the internal storage via the settings and performed a factory data reset - my phone restarted with any problems. I could switch it on and off now without getting stuck in that screen.
Click to expand...
Click to collapse
Glad to hear that! I don't know the change with the SIM Card, for my it worked like that and I have turned off and on several times. After doing that I lost my APN configuration but a quick google search and BAM, everything working smooth and battery life is a little better than before.
You should update the post to let everyone know that the problem is solved
If this helps you, hit the thanks button, I'm trying to build a reputation here

Samper27 said:
Glad to hear that! I don't know the change with the SIM Card, for my it worked like that and I have turned off and on several times. After doing that I lost my APN configuration but a quick google search and BAM, everything working smooth and battery life is a little better than before.
You should update the post to let everyone know that the problem is solved
If this helps you, hit the thanks button, I'm trying to build a reputation here
Click to expand...
Click to collapse
Yup, I just updated the thread title.

gabzki said:
Sounds like my problem has been solved. :good:
I repeated the process by Samper27 (except that I didn't remove the sim card; I don't have an sd card).
After updating to 4.1.2 I cleared the internal storage via the settings and performed a factory data reset - my phone restarted without any problems. I could switch it on and off now without getting stuck in that screen.
Click to expand...
Click to collapse
I have the same problem with this white triangle. The only firmware where the phone starts is .303. All other firmware doesn' start anymore.
I tried the process by Samper27, but it doesn't work for me. Could you please tell me which firmware of .303 and JB 4.1.2 you used? And what do you mean with factory data reset (Hold down the power button and volume up for 10 sec?)
Thanks

Even I gotta same problem. But my phone's screen is now blank, no LED no warning Triangles

[Q] No ROM to run

Hello...
I'm new to all of this rooting, installing and so( used to do this years ago on my LG KP500 Cookie ), so I'm not sure what to look/search for when I'm in this "bad" spot.
I used my sony xperia SP, but I did not like the current version of android it was, as it was lagging, hanging and other weird stuff, so I've decided to try and install the "lollipop" version. Since the guide I followed was detailed, I got it all working perfectly fine, until I tried to install gapps. After installing them, my phone started crashing / hanging on booting, which kept kicking it back to "SONY" screen, and from there it's just an endless loop.
so I tried to wipe and use backup that I had saved, so I could try and reinstall the ROM. It ended up at where I can't do anything anymore. I start my phone - "SONY" screen and nothing else. Can't access the CWM recovery, it doesn't progress anywhere, just sits there.
I'm lost. I don't know what to do Please help ;~;

Digital Noodle said:
Hello...
I'm new to all of this rooting, installing and so( used to do this years ago on my LG KP500 Cookie ), so I'm not sure what to look/search for when I'm in this "bad" spot.
I used my sony xperia SP, but I did not like the current version of android it was, as it was lagging, hanging and other weird stuff, so I've decided to try and install the "lollipop" version. Since the guide I followed was detailed, I got it all working perfectly fine, until I tried to install gapps. After installing them, my phone started crashing / hanging on booting, which kept kicking it back to "SONY" screen, and from there it's just an endless loop.
so I tried to wipe and use backup that I had saved, so I could try and reinstall the ROM. It ended up at where I can't do anything anymore. I start my phone - "SONY" screen and nothing else. Can't access the CWM recovery, it doesn't progress anywhere, just sits there.
I'm lost. I don't know what to do Please help ;~;
Click to expand...
Click to collapse
it's ok...please try to flash t-kernel v2.2 twrp via fastboot mode ...thread link
need further help? ...quote this post and i'll replay ....but always do some searching then ask
good luck :good:

XZ in continious bootloop, no matter what i flash/do

Hi guys,
Device info:
Model C6603, Unlocked bootloader
So i have the following problem, my device is in a bootloop and i can't figure out what the exact issue is. I'm out of options at least.
First a little background on how it came to be: (scroll down for short overview)
Before official lolipop came out I've been on CM12.1 for a few months, cm-12-20141221-INFECTED-yuga to be exact. When official lolipop came out I installed C6603_10.6.A.0.454_Customized_HK-Rooted+Xposed Modules for LB following the instructions, although i see the thread has been modified (name, updated etc.) the instructions are the same. I did not install Xposed yet, because i wanted to try stock+root first.
After a few weeks of normal use, i used google maps navigation. This worked fine but when i arrived at my destination and picked up my phone closed google maps app but then my phone crashed. It rebooted to the point where i had to enter my pincode, but every time i was entering my pin it crashed and after a few tries it dind't even got to the lock screen but only showed the sony logo and rebooted(bootloop). I noticed my device was getting hot and left it alone for a few minutes, after that i started my phone again and was able to use my phone again. Until I started google maps again for the way back and enabled gps it crashed again, the same thing happened the phone would reboot when entering my pin, the phone wasn't hot this time. I left the phone alone till i got home, put it on the charger and the next day my phone worked fine again.
A few days later i was outside in the sun whatsapping, when the same happened my phone crashed and rebooted when entering the pin or slightly after. The phone was feeling hot, also because it was exposed to the sun for a while, in TWRP recovery it showed temperatures around 70 degrees celsius (i don't know if this is too hot?). After i had left the device alone for a while and try to boot it up it got stuck in a bootloop (sony logo), after a night of charging it got to the point of entering the pin code again but crashed and got stuck in a bootloop again (sony logo). And since then i'm not able to get rid of this bootloop. However i could still get into recovery (TWRP).
First i tried to reinstall the rom, factory reset and flash via recovery: C6603_10.6.A.0.454_Customized_HK-Rooted+Xposed Modules for LB
This worked, and the device booted up but after a while it crashed and got stuck in a bootloop again (sony logo).
So all summed up:
cm-12-20141221-INFECTED-yuga
>> C6603_10.6.A.0.454_Customized_HK-Rooted+Xposed Modules for LB
>> Google maps navigation >> overheated >> bootloop (sony logo) >> charging night >> working >> whatsapping in bright sun >> overheating >> continuous bootloop (sony logo)
What i have tried:
- Tried booting without sim card, withoud sd but doesn't work
- Flash same rom via recovery C6603_10.6.A.0.454_Customized_HK-Rooted+Xposed Modules for LB : Worked once, but then crashed and went back in bootloop, now when i flash this only Bootloop (sony logo)
- Flash updated version of http://forum.xda-developers.com/xperia-z/help/lollipop-5-0-2-10-6-0-454-pre-rooted-t3116205 via recovery : Bootloop (sony logo)
- Flash kernel via fastboot http://forum.xda-developers.com/xperia-z/development/kernel-unlocked-bootloaders-t3114234 : Only recovery works
- Flash stock kernel via fastboot: boot (sony logo) one time then turns off
- Flash stock lolipop (with and without bootloader unlocked) via latest Flashtool : Bootloop (sony logo)
- Flash stock lolipop via xperifirm (C6603_10.6.A.0.454_KPN Mobile NL) xperia (with and without bootloader unlocked) via latest Flashtool : Bootloop (sony logo)
- Flash stock kitkat (with and without bootloader unlocked) via Flashtool: Bootloop (sony logo)
- Relock bootloader and Sony PC companion restore latest firmware : Bootloop (sony logo)
- Restoring serveral backups from TRWP and Phillz touch but they all result in the same bootloop, while at the time the backups were made there were no problems.
I'm pretty much out of options and begin to thinking something was damaged when the device overheated or a bad partion of a kernel is still stuck in the devices kernel.
Does anyone had the same issue, if so how to fix it? Or another option i could try, maybe someone spotted anything i did wrong?
Current state:
Locked bootloader, stock lolipop 10.6.A.0.454 flashed via Sony PC Companion recovery
Boots into setup, after a few reboots I completed the setup. But still randomly reboots when trying to use some apps or in general leaving it in standby for a while (might be due instability).
Thanks in advantage,
Jonathan

So the only things that you do that do not result in a bootloop are flashing a kernel. Try flashing a Stock kernel with Flashtool --> open flashtool >choose the flash button at the top left > flashmode > choose the firmware > check cache and data above and below check Only Kernel. Post result here...
Good luck

Try flashing a Stock kernel with Flashtool --> open flashtool >choose the flash button at the top left > flashmode > choose the firmware > check cache and data above and below check Only Kernel.
Click to expand...
Click to collapse
Don't do this. It will wipe your data and flash everything but the kernel, therefore losing root etc.
If you want to flash a stock kernel, you must leave everything in the "Wipe" section unchecked, and check everything but "Kernel" in the "Exclude" section.
I don't think this will help anyway, being that you're already on a stock firmware flashed via Flashtool.

aaronkatrini said:
So the only things that you do that do not result in a bootloop are flashing a kernel. Try flashing a Stock kernel with Flashtool --> open flashtool >choose the flash button at the top left > flashmode > choose the firmware > check cache and data above and below check Only Kernel. Post result here...
Good luck
Click to expand...
Click to collapse
Thanks for your fast reply, I think you meant: check everything but leave kernel unchecked (as kingvortex replied at the time of writing)? Since it is an 'Exclude' list. I flashed stock kernel, it shows the Sony logo and then shuts down. I used stock lolipop kernel from 'C6603_10.6.A.0.454_KPN' Mobile NL, and i also tried 'C6603_10.6.A.0.454_Customized CE1'. both have the same result.
I've got the most "life" after i restored my phone with pc companion to 10.6.A.0.454. Then, after being charged via the wall charger for a while, it boots up normally and goes into setup, since it is a complete restore. But crashed around the setup screen for wifi. The other options i tried do not come any further than showing the Sony logo, this stock one shows Sony logo >> android logo >> boot animation + sound.

I'm thinking it might be a case of a dead battery or battery controller of some sort. Because the phone only boots up normally, with stock android .454, when the phone is connected to the wall charger. Whenever i pull out the cable the phone crashes and reboots, also when not connected to the charger it gets stuck in a bootloop. However when the phone is connected to a charger and working for a while it still randomly crashes when using the device, sometimes these moments are suspicious because it sometimes reboots when enabling gps, wifi, mobile data or when starting an app, phone call or synchronizing accounts for instance. On a side note sometimes the battery percentage drops about 6-9 percent when rebooted one time or when crashed, also when i connect my phone to the charger the status led is red but when done showing the sony logo and when charging it turns green (or yellow, depends on battery percentage). This is why i think something internal is not working properly whether it is the battery or the battery controller, i don't know.
I still find it weird that the phone was in perfect condition before flashing .454 stock lolipop, it might be due to overheating that some components where damaged. At least i'm guessing this is the case because i know no other reason why it would show such behavior. Is there someone who has experienced something like this or another solution i might try?

In the mean time i bought a Z3, my XZ is definitely dead now after the battery has discharged and i can't charge it because it's constantly rebooting. However flashmode and fastboot are still working. Thanks for the replies. I might repair my XZ if i can get my hands on a cheap (broken) second hand and replace the internals, but i'll see.

Hi, i have the same problem... i cant charge and the constantly rebooting... and in my case also... when i try to flash any ROM, flashtool and Fastboot are stuck for 1 hour when try to flash system.sin (system.img)
i stop flashing after 1 hour... not sure if could finish after 2 hours :/
Cant use PC Companion because dont have charge in the phone (locked bootloader)
Any suggestion?

Z1 stuck in boot loop after fumbling my way around a Chinese recovery

So I recently tried updating MIUI v5 to MIUI v6. However, I stupidly opted for the FOTA update, rather than updating using recovery.
After running the update, my phone rebooted and it worked fine, MIUI v6 running great. However, because I'd updated using the in-built updater, my data and apps were still there from before. This was causing no-end of 'process stopped running' alerts, which drove me crazy after around 10 minutes.
Therefore, I decided to try and wipe my data. I went to the recovery menu and found that MIUI had installed its own Chinese recovery, my previous TeamWin one was gone. So I fumbled around and managed to find the 'Wipe data' etc. option, and chose it. I was presented with a couple more options which I didn't understand, and (stupidly) accepted both. This left me with a phone that would no longer boot past the 'Sony' logo. I was also unable to access the Chinese recovery menu.
Feeling a little worried at this point, I started to Google around for guides on how to flash a recovery back onto a phone stuck in a boot loop. After hours of searching, I decided it wasn't possible and instead follow a guide for fixing 'boot loops' through flashing an original Sony 'ftf' firmware using flashtool.
Now, the guide I was following was quite old, and provided a link to 'C6903_14.2.A.0.290_Global LTE' - so this is what I used to flash (which I'm now regretting). Before flashing, I was presented with some options, for which the guide I was following recommended I deselect the 'kernel' option. So I did this too.
After around 10-15 minutes and what seemed like a successful flash, I tried turning the phone on. This time, the Sony logo appears, then disappears to a black screen, and then the backlight turns off, followed by the Sony logo, then a black screen, then backlight turning off, etc. So slightly different behaviour to before, but still boot looping.
I think what may have happened is that MIUI includes an updated kernel, and through flashing the 14.2.A.0.290 firmware without a kernel, I've introduced some sort of incompatibility.
The problem I'm having now is getting another firmware onto the phone in order to resolve this. For some reason, despite flashtool recognising the phone being plugged in with flash mode, it refuses to load the firmware - I'm instead presented with the message:
"You must have the according fsc script to flash this device."
Does anyone know how I might be able to get around this? I admit to being a bit of a noob when it comes to flashing so have probably dug my own hole here, and seem to have left myself completely unable to work out what I need to do in order to get back out! Any help would be hugely appreciated.

Please see the attached screenshot of what I see when I try flashing with flashtool. The whole flash takes around 2 seconds, so it appears as though nothing's actually happening. However, it did flash successfully before, only without the kernel (which I think is what's causing my problems).
Please help!

langauld said:
Please see the attached screenshot of what I see when I try flashing with flashtool. The whole flash takes around 2 seconds, so it appears as though nothing's actually happening. However, it did flash successfully before, only without the kernel (which I think is what's causing my problems).
Please help!
Click to expand...
Click to collapse
This version of Flashtool you're using is known to require some files for your device to be able to work.
Try using the version before it.
Oh and NEVER:
- Wipe /system and /data using recovery with unlocked bootloader (it will remove everything and the phone will not be able to boot).
- Flash an ftf of a older android version (like flashing kitkat on top of lollipop) without including kernel because that will cause a bootloop. (not sure about flashing lollipop on top of kitkat but I think it's the same)

Just2Cause said:
This version of Flashtool you're using is known to require some files for your device to be able to work.
Try using the version before it.
Oh and NEVER:
- Wipe /system and /data using recovery with unlocked bootloader (it will remove everything and the phone will not be able to boot).
- Flash an ftf of a older android version (like flashing kitkat on top of lollipop) without including kernel because that will cause a bootloop. (not sure about flashing lollipop on top of kitkat but I think it's the same)
Click to expand...
Click to collapse
You sir, are a god amongst men. I'd never have thought to try the previous version of FlashTool. From reading around, I knew some devices had issues with it, but because it lists the Z1 as being 'supported', I didn't think that would apply to me.
I flashed again without deselecting the kernel and it booted first time. Thank you again.

langauld said:
You sir, are a god amongst men. I'd never have thought to try the previous version of FlashTool. From reading around, I knew some devices had issues with it, but because it lists the Z1 as being 'supported', I didn't think that would apply to me.
I flashed again without deselecting the kernel and it booted first time. Thank you again.
Click to expand...
Click to collapse
Glad I could help.

HELP! My Xperia Z CAN'T be unbricked

Hello all,
I already thank each and everyone of you willing to help/answer because I am truly desperate right now.
Id like to note that my phone (C6603) is rooted and the bootloader unlocked (i'm not sure though), and the internal storage was 75% full...
Here is the problem :
- I was using my phone as usual yesterday, then suddenly the phone power off, shows the hazard logo (the triangle with tools in it), as if it were installing an update. It lasted for like 5 seconds, then the phone rebooted.
- After the reboot, the phone was laggy as hell. And as it lagged, it shutted down and rebooted.
- During the reboot the phone was doing the "optimizing x/264app" thing. That optimization lasted for about 30minuts. Then the phone booted, but was laggy. I tried to go to settings but couldn't open anything in it, I couldn't even scroll. Then the phone rebooted again.
- After numerous reboots and lags, the phone couldn't get past the Optimization step anymore.
- I tried to repair with Sony Companion, but it said that it couldn't find any software for my device (even though I waited for 2 hours for the download - slow internet here).
- I tried to reflash the stock rom I had in the phone: C6603_10.7.A.0.222_UA.ftf (I checked "wipe userdata" because I wanted to clean the phone anyway)
- The flashing went fine. I turned on the phone, but on screen where you usually choose the language, it freezed and rebooted.
And there we are. Stuck in infinite reboot and "optimizing" again.
I tried to reflash the ftf file but Flashtool wasn't able to do it anymore, it said "Processing of loader.sin finished with errors."
Please tell me there is a solution other than trash this phone. Please.
Thank you.