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
C6603 Stuck in bootloop! [Last update: 24/1/14]
UPDATE 24/01/14
This issue has been SOLVED.
I replaced the battery with one from eBay and the phone is working flawlessly, all the ROM flashing I went through was not the problem at all. Remember that if you are going to try to replace the battery you may as well buy a new rear glass piece as it is almost guaranteed that the glass will break in the removal process. You will also require new a adhesive piece. The entire procedure cost me $51AUD (battery, glass, adhesive).
All the content below is irrelevant, if your phone randomly shuts off (instantaneously) on boot or soon after, try to replace your battery!
Thanks for your help.
I've got quite a story to tell and if you have the patience to read it, I will greatly appreciate your assistance. TL;DR BELOW
In the beginning I was running 4.2.2, on a stock Australian 10.3.A.0.423 Unbranded ftf. It had been working flawlessly for a month or so until quite recently. It had developed a problem where it would only remain switched on whilst being plugged into the wall socket. As soon as (or thereafter) I removed the plug out of the phone, with one touch, one action, BAM! The display was off and I had to restart the phone again. I spent a few hours browsing for solutions to this problem, most of them said to hold the power and vol+ buttons until the handset vibrated 3 times. That turned it off alright, but I'm looking to go in the other direction.
After a stressful while scrounging old forum posts, I came to the conclusion that the fault is in my ROM, after all, I had flashed from 4.1.2 (I think) to 4.2.2 just a month prior (I flashed a ROM instead of waiting until the snail-like carriers here in Australia decided to dribble out the release). So now being convinced that I ROM is at fault I browse XDA for a newer stock one. Hey! Look! 4.3 it being rolled out in Aust, I check whether it's available to me yet, and obviously, no, it is not. I stumble upon this thread in my travels. I spend a while working to meet it's requirements. Get flashtool, get unlocked bootloader, get root, install cwm, and attempt to install XzDualRecovery 2.6. I've placed the XDR.zip on the sdcard in the XZ, I run the zip using CWM, it seems successful, I then go to reboot and check whether my 4.3 works, after I select reboot I'm asked whether I wish to root the phone. Why yes! that seems easy enough, and just as I select 'ok' the screen goes blank. The bloody phone has switched off in the middle of my work! I try to boot and it hangs on the Sony logo then reboots, creating a cycle. I decide to plug it back in to the wall socket (as this is the only way to get it to boot and remain on), huzzah, it runs. But the root had failed. The rest of my rant is insignificant until now (around 7 hours of failed attempts later)
So in an attempt to keep this wall of text down, I try my best to summarize, If I am not clear enough, just say.
I tried reflashing my old 4.2.2 ROM back, this makes the whole thing worse, now the phone won't even get past the Sony logo (even when plugged to a socket), I flash a different 4.3 ftf, nothing, I restore with PCC, I restore with SUS, I create a ftf from the SUS files and attempt to flash that. Nothing, nothing works. So where am I at now?
The phone still has battery, although, I'm not sure how much, I can no longer get it to charge as it hangs on the Sony logo. The phone should be flashed with 10.3.A.0.423, but when I check the baseband version in Fastboot cmd prompt, it still says 10.4.B.0.569, I feel as though flashtool isn't flashing properly, but I've read that this is usually a non-issue. I can boot into flashmode and fastboot mode. I can unlock and lock the bootloader. I can use ADB and Fastboot CMD (Minimal version) to read values and run commands. Actually, I managed to use the phone in fastboot mode, in conjunction with ADB and Fastboot CMD, I ran the command "fastboot continue" and the phone went on to charge off the usb power, It didn't seem to charge very fast, or at all, and I haven't been able to get it to do it again. So a TL;DR:
-C6603 stuck in bootloop.
-Possibly has a 4.2.2 ROM installed (10.3.A.0.423 Unbranded AU)
-Cannot Charge
-Can run flashmode and fastboot mode
-Can use ADB and Fastboot
-Can use SUS, PCC, and Flashtool to flash stock roms
-Can't figure this out for the life of me!
UPDATE 01/01/14
Currently I have a kernel installed that allows me to use cwm twrp (doomkernel v19, maybe), I have flashed a 'flashable' stock 4.3 rom using cwm and the phone didn't manage to get past the kernel logo. HOWEVER, using fastboot mode, I run the command "fastboot continue", and if I allow the phone to go past the kernel logo it vibrates, the LED turns green as opposed to showing a purple one, and it will begin charging (The LED isn't green as a result of the battery level). EDIT [1/1/14 3:01AM]: I tried to launch the phone whilst it was charging, the charging symbol went away and the phone remained on a black screen (lcd is on, but nothing is displayed) for a few seconds before shutting off automatically.
I must mention, I cannot get into recovery unless I boot the phone into fastboot mode, run the command in fastboot: "fastboot continue". If I don't do this, it simply crashes (shuts off) when showing the kernel logo.
If you need to know more I will provide as much information as I can, as succinct as I can, as fast as I can. I am in this for the long run. Thank you for your time,
UPDATE 08/01/14
I've come to the conclusion that my issue is battery related. After repeated from flashes and fastboot attempts, I managed to get the phone charging a few times, I witnessed the level was sporadic upon infrequent viewings. I have come across a few other very similar threads and feel that it is necessary to try replacing the battery, I try and post a youtube clip that details what happens currently.
Keringkien
keringkien said:
C6603 Stuck in bootloop!
I've got quite a story to tell and if you have the patience to read it, I will greatly appreciate your assistance. TL;DR BELOW
In the beginning I was running 4.2.2, on a stock Australian 10.3.A.0.423 Unbranded ftf. It had been working flawlessly for a month or so until quite recently. It had developed a problem where it would only remain switched on whilst being plugged into the wall socket. As soon as (or thereafter) I removed the plug out of the phone, with one touch, one action, BAM! The display was off and I had to restart the phone again. I spent a few hours browsing for solutions to this problem, most of them said to hold the power and vol+ buttons until the handset vibrated 3 times. That turned it off alright, but I'm looking to go in the other direction.
After a stressful while scrounging old forum posts, I came to the conclusion that the fault is in my ROM, after all, I had flashed from 4.1.2 (I think) to 4.2.2 just a month prior (I flashed a ROM instead of waiting until the snail-like carriers here in Australia decided to dribble out the release). So now being convinced that I ROM is at fault I browse XDA for a newer stock one. Hey! Look! 4.3 it being rolled out in Aust, I check whether it's available to me yet, and obviously, no, it is not. I stumble upon this thread in my travels. I spend a while working to meet it's requirements. Get flashtool, get unlocked bootloader, get root, install cwm, and attempt to install XzDualRecovery 2.6. I've placed the XDR.zip on the sdcard in the XZ, I run the zip using CWM, it seems successful, I then go to reboot and check whether my 4.3 works, after I select reboot I'm asked whether I wish to root the phone. Why yes! that seems easy enough, and just as I select 'ok' the screen goes blank. The bloody phone has switched off in the middle of my work! I try to boot and it hangs on the Sony logo then reboots, creating a cycle. I decide to plug it back in to the wall socket (as this is the only way to get it to boot and remain on), huzzah, it runs. But the root had failed. The rest of my rant is insignificant until now (around 7 hours of failed attempts later)
So in an attempt to keep this wall of text down, I try my best to summarize, If I am not clear enough, just say.
I tried reflashing my old 4.2.2 ROM back, this makes the whole thing worse, now the phone won't even get past the Sony logo (even when plugged to a socket), I flash a different 4.3 ftf, nothing, I restore with PCC, I restore with SUS, I create a ftf from the SUS files and attempt to flash that. Nothing, nothing works. So where am I at now?
The phone still has battery, although, I'm not sure how much, I can no longer get it to charge as it hangs on the Sony logo. The phone should be flashed with 10.3.A.0.423, but when I check the baseband version in Fastboot cmd prompt, it still says 10.4.B.0.569, I feel as though flashtool isn't flashing properly, but I've read that this is usually a non-issue. I can boot into flashmode and fastboot mode. I can unlock and lock the bootloader. I can use ADB and Fastboot CMD (Minimal version) to read values and run commands. Actually, I managed to use the phone in fastboot mode, in conjunction with ADB and Fastboot CMD, I ran the command "fastboot continue" and the phone went on to charge off the usb power, It didn't seem to charge very fast, or at all, and I haven't been able to get it to do it again. So a TL;DR:
-C6603 stuck in bootloop.
-Possibly has a 4.2.2 ROM installed (10.3.A.0.423 Unbranded AU)
-Cannot Charge
-Can run flashmode and fastboot mode
-Can use ADB and Fastboot
-Can use SUS, PCC, and Flashtool to flash stock roms
-Can't figure this out for the life of me!
If you need to know more I will provide as much information as I can, as succinct as I can, as fast as I can. I am in this for the long run. Thank you for your time,
Keringkien
Click to expand...
Click to collapse
download any FTF , 4.2.2 or 4.3 , connect your device to flash tool as flashmode , and select to flash the ftf , when you are selecting the ftf in the flash tool , at the right side check all at the wipe section , and uncheck all at the exclude section
but your internal storage might get also wiped , but i assume it already happened when you unlocked your boot loader
elias234 said:
download any FTF , 4.2.2 or 4.3 , connect your device to flash tool as flashmode , and select to flash the ftf , when you are selecting the ftf in the flash tool , at the right side check all at the wipe section , and uncheck all at the exclude section
but your internal storage might get also wiped , but i assume it already happened when you unlocked your boot loader
Click to expand...
Click to collapse
Alrighty then, I'll give that a go later. I have just found a 4.3 for Australia, perhaps it will be different. Thanks for the quick reply.
keringkien said:
Alrighty then, I'll give that a go later. I have just found a 4.3 for Australia, perhaps it will be different. Thanks for the quick reply.
Click to expand...
Click to collapse
this thread could be helpful : http://forum.xda-developers.com/showthread.php?t=2229250
i'm not sure if that problem could be solve, but it was, like you said, different. never saw anything like that either.
Anyway:
Can it boot into custom recovery in its state now?( for mounting storage for something else in case you have cwm or twrp installed)
Jambu95 said:
this thread could be helpful : http://forum.xda-developers.com/showthread.php?t=2229250
i'm not sure if that problem could be solve, but it was, like you said, different. never saw anything like that either.
Anyway:
Can it boot into custom recovery in its state now?( for mounting storage for something else in case you have cwm or twrp installed)
Click to expand...
Click to collapse
Thanks so much for the reply. The thread has something I can try, if this new rom fails (I expect it will). What is custom recovery? I cannot access the storage, only fastboot and flashmode. no cwm and xdr was never completed.
ROM just failed, trying SUS now.
keringkien said:
Thanks so much for the reply. The thread has something I can try, if this new rom fails (I expect it will). What is custom recovery? I cannot access the storage, only fastboot and flashmode. no cwm and xdr was never completed.
ROM just failed, trying SUS now.
Click to expand...
Click to collapse
oh dear, custom recovery is cwm (clockworkmod recovery) or twrp (team win recovery project), it means, it allows you to do something important just before it boot into system, which is bootstall or bootloop as you call it. you cannot boot into system, then try to boot into recovery ( which is before it boot the system), that might help.
both recoveries will allow you to mount storage to copy things to sd cards from pc.
you can try unlock bootloader and flash custom kernel with recoveries, maybe you "could" boot into one of those recoveries.
I also got the same problem, but mine is a C6602. I was trying to setup a mail exchange, then it asked for some permission. I push enter, then after an hour, it start the bootloop.
The phone boot till the main screen, i could swipe and play around for 10 second, then it reboot.
I have tried everything from hard reset, to FlashTool to SUS, relock, unlock, flash stock, from old stock to new stock, it just won't work :|
Jambu95 said:
oh dear, custom recovery is cwm (clockworkmod recovery) or twrp (team win recovery project), it means, it allows you to do something important just before it boot into system, which is bootstall or bootloop as you call it. you cannot boot into system, then try to boot into recovery ( which is before it boot the system), that might help.
both recoveries will allow you to mount storage to copy things to sd cards from pc.
you can try unlock bootloader and flash custom kernel with recoveries, maybe you "could" boot into one of those recoveries.
Click to expand...
Click to collapse
I'm well aware what cwm is, I just assumed that because you said 'custom' that it might possibly be different, as recovery is always custom anyway, sorry for the misunderstanding.
I am able to flash a 'boot.img' that enables me to use cwm and twrp, HOWEVER, the only way I can access it (as in cause the phone to remain on long enough for it to parse the boot.img) is to connect the phone to my computer in fastboot mode, then using the Fastboot command: "fastboot continue", it will run the 'img' and allow me to enter twrp or cwm. It still won't begin charging or even show the Xperia logo if I allow it to continue without accessing the recovery options.
Thanks for your help.
keringkien said:
I'm well aware what cwm is, I just assumed that because you said 'custom' that it might possibly be different, as recovery is always custom anyway, sorry for the misunderstanding.
I am able to flash a 'boot.img' that enables me to use cwm and twrp, HOWEVER, the only way I can access it (as in cause the phone to remain on long enough for it to parse the boot.img) is to connect the phone to my computer in fastboot mode, then using the Fastboot command: "fastboot continue", it will run the 'img' and allow me to enter twrp or cwm. It still won't begin charging or even show the Xperia logo if I allow it to continue without accessing the recovery options.
Thanks for your help.
Click to expand...
Click to collapse
if you can mount the storage, you could copy the flashable stock rom (4.3) and copy it into your sd card, and maybe you can flash through there by following instructions from that thread.
---------- Post added at 11:21 PM ---------- Previous post was at 11:20 PM ----------
billhainh said:
I also got the same problem, but mine is a C6602. I was trying to setup a mail exchange, then it asked for some permission. I push enter, then after an hour, it start the bootloop.
The phone boot till the main screen, i could swipe and play around for 10 second, then it reboot.
I have tried everything from hard reset, to FlashTool to SUS, relock, unlock, flash stock, from old stock to new stock, it just won't work :|
Click to expand...
Click to collapse
look for the disaster recovery thread i posted above
Jambu95 said:
if you can mount the storage, you could copy the flashable stock rom (4.3) and copy it into your sd card, and maybe you can flash through there by following instructions from that thread.
---------- Post added at 11:21 PM ---------- Previous post was at 11:20 PM ----------
Click to expand...
Click to collapse
I tried to mount the storage, my pc wouldn't detect the phones storage, I managed to push the stock rom zip to the sd card using ADB. I still had cwm recovery and could flash the zip using it. Still, however, the phone shuts down before it gets past the kernel logo. Again, I used the phone in Fastboot mode and forced it to continue using "fastboot continue", I left it go past the kernel logo and it is charging at the moment. I may try to start the phone now, yet expect it to crash again.
EDIT: I tried to launch the phone whilst it was charging, the charging symbol went away and the phone remained on a black screen (lcd is on, but nothing is displayed) for a few seconds before shutting off automatically.
EDIT: Happy New Year!
Thank you.
keringkien said:
I tried to mount the storage, my pc wouldn't detect the phones storage, I managed to push the stock rom zip to the sd card using ADB. I still had cwm recovery and could flash the zip using it. Still, however, the phone shuts down before it gets past the kernel logo. Again, I used the phone in Fastboot mode and forced it to continue using "fastboot continue", I left it go past the kernel logo and it is charging at the moment. I may try to start the phone now, yet expect it to crash again.
EDIT: I tried to launch the phone whilst it was charging, the charging symbol went away and the phone remained on a black screen (lcd is on, but nothing is displayed) for a few seconds before shutting off automatically.
EDIT: Happy New Year!
Thank you.
Click to expand...
Click to collapse
this problem occurs with every kernel you've used (including stock and custom kernels)?
Jambu95 said:
this problem occurs with every kernel you've used (including stock and custom kernels)?
Click to expand...
Click to collapse
Yes that is correct, it's current issue (turning off sponanteously) occurred when I was running stock 4.2.2 (no root, no bootloader unlock).
keringkien said:
Yes that is correct, it's current issue (turning off sponanteously) occurred when I was running stock 4.2.2 (no root, no bootloader unlock).
Click to expand...
Click to collapse
lol, you should unlock the bootloader before you flash a custom boot.img. the primary solution now is to flash any rom to see if it boots up normally , then you can still find a way to revert back to stock.
Jambu95 said:
lol, you should unlock the bootloader before you flash a custom boot.img. the primary solution now is to flash any rom to see if it boots up normally , then you can still find a way to revert back to stock.
Click to expand...
Click to collapse
I never said that I flashed a custom boot.img whilst on a locked bootloader. The reason I tried all the things that I have is because the phone was spontaneously shutting down (on stock, unedited). Perhaps once I made the mistake of flashing a boot.img before unlocking, but I have since unlocked and flashed many roms and kernels. Thanks for your reply.
keringkien said:
I never said that I flashed a custom boot.img whilst on a locked bootloader. The reason I tried all the things that I have is because the phone was spontaneously shutting down (on stock, unedited). Perhaps once I made the mistake of flashing a boot.img before unlocking, but I have since unlocked and flashed many roms and kernels. Thanks for your reply.
Click to expand...
Click to collapse
the device can't get pass the sony logo?
edNHour consum
Jambu95 said:
the device can't get pass the sony logo?
Click to expand...
Click to collapse
That is correct, it doesn't hang but suddenly turns off, the only way I can use recovery tools in the kernel is if I plug the phone into my pc in Fastboot mode, then issue the command "fastboot continue" from cmd.
keringkien said:
That is correct, it doesn't hang but suddenly turns off, the only way I can use recovery tools in the kernel is if I plug the phone into my pc in Fastboot mode, then issue the command "fastboot continue" from cmd.
Click to expand...
Click to collapse
i think there is something wrong with your motherboard or the battery connection, i'm not sure, because my pc got that problem before, it just boot up to starting windows... and then reboot, in the end i found out the capacitor got swelled in the power supply.
Jambu95 said:
i think there is something wrong with your motherboard or the battery connection, i'm not sure, because my pc got that problem before, it just boot up to starting windows... and then reboot, in the end i found out the capacitor got swelled in the power supply.
Click to expand...
Click to collapse
That is certainly possible, I have had to replace the back glass and during that operation it is possible that the battery got too hot and is now lower in voltage or something. Thanks for the suggestion, I would appreciate a second opinion with this...
Thank you.
keringkien said:
That is certainly possible, I have had to replace the back glass and during that operation it is possible that the battery got too hot and is now lower in voltage or something. Thanks for the suggestion, I would appreciate a second opinion with this...
Thank you.
Click to expand...
Click to collapse
if you still have your warranty, you can go to the center and request for a replacement, the best solution now is to revert to as stock as possible, if can get the bootloader locked again then it's good,
Jambu95 said:
if you still have your warranty, you can go to the center and request for a replacement, the best solution now is to revert to as stock as possible, if can get the bootloader locked again then it's good,
Click to expand...
Click to collapse
I imagine it is still under warranty, however I have read that unlocking the bootloader permanently voids warranty. And I have replaced the back of my white phone with a black glass, perhaps if I get a new white rear glass it will be ok, but then I might as well just replace the battery $40AUD isn't too expensive IMO.