Bootloop problem since Android 9.0 update - Sony Xperia XZ1 Compact Questions & Answers

I have a weird problem since Android 9 update. Every now and then when i restart the phone, it either gets stuck on "restarting" or restarts until "Sony" appears on the screen and keeps restarting. The only way to fix this would be to use the Xperia Companion.
I had bought the Phone on Amazon Germany in July 2018. I sent the phone back to them and they returned it claiming they have "Repaired it" but the problem is back again. Is there anyway it could be fixed or am i stuck with this gorgeous little brick forever?

I have had this issue direct after upgrade: Solution was a factory reset (Hold power and Volume up(or down?) several seconds till the phone vibrates some times...
Gesendet von meinem viennalte mit Tapatalk

yekollu said:
Is there anyway it could be fixed or am i stuck with this gorgeous little brick forever?
Click to expand...
Click to collapse
If it's still within warranty, send it back, again.
You should be familliar with the proccess by now.
Some technicians are lazy and because they can't see what the probelem is when they turn it on they just send it back 'fixed'
You might end up with a new phone :good:
Edit: It's worth plugging it in to Xperia Companion and effecting a repair before you send it back, it might be a dodgy build.

Didgesteve said:
If it's still within warranty, send it back, again.
You should be familliar with the proccess by now.
Some technicians are lazy and because they can't see what the probelem is when they turn it on they just send it back 'fixed'
You might end up with a new phone :good:
Edit: It's worth plugging it in to Xperia Companion and effecting a repair before you send it back, it might be a dodgy build.
Click to expand...
Click to collapse
Thanks for the reply. I have to use the Xperia Companion every time to "Fix" the phone and use it again (while going through the whole process of setting up/Restoring)....
Guess i will have to file a complaint again

Didgesteve said:
If it's still within warranty, send it back, again.
You should be familliar with the proccess by now.
Some technicians are lazy and because they can't see what the probelem is when they turn it on they just send it back 'fixed'
You might end up with a new phone :good:
Edit: It's worth plugging it in to Xperia Companion and effecting a repair before you send it back, it might be a dodgy build.
Click to expand...
Click to collapse
I just noticed that my phone has new IMEI number

Just wondering which update caused bootloop
yekollu said:
I have a weird problem since Android 9 update. Every now and then when i restart the phone, it either gets stuck on "restarting" or restarts until "Sony" appears on the screen and keeps restarting. The only way to fix this would be to use the Xperia Companion.
I had bought the Phone on Amazon Germany in July 2018. I sent the phone back to them and they returned it claiming they have "Repaired it" but the problem is back again. Is there anyway it could be fixed or am i stuck with this gorgeous little brick forever?
Click to expand...
Click to collapse
Hi, was just wondering was it firmware update 47.2.A.4.45 that caused bootloop problem? And did you install via Xperia companion or OTA or ..? tia

strate aero said:
Hi, was just wondering was it firmware update 47.2.A.4.45 that caused bootloop problem? And did you install via Xperia companion or OTA or ..? tia
Click to expand...
Click to collapse
Yes and OTA

Related

Xperia Z; Dead problem After update to .434

Hi
any report about death problem of Xperia Z after updating new firmware (.434)?
Thanks
:good:
That title of yours is a bit off, you make it sound like you have a dead phone after updating
Hehe
No, i just wanna know if this happened or not.
If problem solved completely so we can use it more and etc
However i used it alot before update
Sent via my Sony Xperia Z | C6602
As far as I know, Sony hasn't received any reports of death phones due to the software issue of 350fw with the new 434fw
Sent from my C6603 using xda app-developers app
That is good news.
Can not wait for 4.2.x to release, did download krab his 434 NL FTF file just incase I get software problems.
Kind regards, Stefan.
But since the update after my nightmare began, First, ROOT many times without success (this is my problem), to complete the ROOT, try to go and get LINK2SD, but every time you create a EXT2 restartafter will not be able to enter, just kept restart, need to be removed the SDCARD, Anyway, if sdcard including not turn on, and subsequently I leave a message in the official website, and they told me to try a factory reset and clear memoryeverything, I have tried, but resolves containing the sdcard normal boot, but often a memory file something will restart to now, I have not yet been solved, I am thinking how to completely cleanpainted on the software, who can teach me how to clean, I also tried FLASHTOOL, but I try many time, it just is hold on at flash strat point, then over 30mins , is still....... i very bad lucky
pls Report here if u got this problem...
yes....
http://forum.xda-developers.com/showthread.php?t=2176978&page=5
Noobie UK said:
yes....
http://forum.xda-developers.com/showthread.php?t=2176978&page=5
Click to expand...
Click to collapse
yes like your phone died with the 434 update ?
there seem to be quite some reports of a damaged kernel version with this update that uses a lot of cpu in standby and damages it through heat.
Updated the phone a few days ago, powered it off today and it did not boot. Now its in repair
ltkort said:
Updated the phone a few days ago, powered it off today and it did not boot. Now its in repair
Click to expand...
Click to collapse
so explain about ur phone state
root, unlock bootloader and ....
sorry ment refer to link...reports of failure after 434 update.
digitalray said:
yes like your phone died with the 434 update ?
there seem to be quite some reports of a damaged kernel version with this update that uses a lot of cpu in standby and damages it through heat.
Click to expand...
Click to collapse
Sleep of death is still present in .434 Phone was fine for a week after updating, but the problem has happened once a day for the past 3 days. Wake up in the morning to a dead phone. Able to perform a reset with power + volume up.
Not happy, where's this fix we were promised! Sony never said .434 was to fix SOD, it was all stupid rumors.
kazaoc said:
Sleep of death is still present in .434 Phone was fine for a week after updating, but the problem has happened once a day for the past 3 days. Wake up in the morning to a dead phone. Able to perform a reset with power + volume up.
Not happy, where's this fix we were promised! Sony never said .434 was to fix SOD, it was all stupid rumors.
Click to expand...
Click to collapse
please explain about ur phone condition
root / unlock bootloader / stock rom ?
kazaoc said:
Sleep of death is still present in .434 Phone was fine for a week after updating, but the problem has happened once a day for the past 3 days. Wake up in the morning to a dead phone. Able to perform a reset with power + volume up.
Not happy, where's this fix we were promised! Sony never said .434 was to fix SOD, it was all stupid rumors.
Click to expand...
Click to collapse
i had the exact same probleme with my asus transformer pad for 5 months and asus delivered several updates promising to fix the probem, but it did not work, this happened with android ics 4.0.3.
after half a year they managed to fix it.
so until it's not completely dead, just wait for a working update.

[SOLVED] Xperia Z restarts after unplugging charger

Hi,
I bought Xperia Z a week ago and there was update available, I tried to update it, but the phone stuck in boot loop, I solved this via Sony Update Service. So there is new and actual software. It works fine, until the first charge, the charging was ok, but after unplugging I tried to resolve lock gesture, but it stuck and restarts, the restart repeat several times. And after every charging, there are frome three to five restarts and then the phone is available to using.
Unfortunately, the Backup and restore app is not working, it stuck at 8% and then the phone restarts. So I decided to use SUS again, but it doesn't helped. The restarts are still there, no matter if original or non-original charger, so there is no connection to used/downloaded apps.
Is there any help to this issue?
I don't rooted the phone, but the phone is bought as used from credible store.
Thanx for answers
FW: 10.1.1.A.1.253
I'd suggest to restore the phone to factory default and return it to the store. It could be a hardware issue, that the phone receives a to high voltage when removing it from the charger.
Sent from my C6603 using xda app-developers app
Dsteppa said:
I'd suggest to restore the phone to factory default and return it to the store. It could be a hardware issue, that the phone receives a to high voltage when removing it from the charger.
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
for several times after restart?
bump
when I charge the phone to 80%, not full, and then unplug, the phone doesn't restart
Something defiantly seems off. It should not restart. Loke other suggestion it try a factory reset, if that doesn't work u might need to contact Sony for exchange or repair.
Sent from my C6603 using xda app-developers app
try option 2 if option 1 fails
option 1: Repair through Sony Update Service followed by a Factory Reset under settings > backup & resets. (Internal Wipe)
option 2: Flash another FTF file
but then again, it seems like a hardware issue. Suggest you get an exchange if its still under warranty or whatever.
LitoNi said:
try option 2 if option 1 fails
option 1: Repair through Sony Update Service followed by a Factory Reset under settings > backup & resets. (Internal Wipe)
option 2: Flash another FTF file
but then again, it seems like a hardware issue. Suggest you get an exchange if its still under warranty or whatever.
Click to expand...
Click to collapse
1 - how to repare through SUS? when I connect phone to SUS it show me only the option to re-update phone and it delete all files, so after that is wipe necessary too?
2 - where to get FTF file?
zemko said:
Hi,
I bought Xperia Z a week ago and there was update available, I tried to update it, but the phone stuck in boot loop, I solved this via Sony Update Service. So there is new and actual software. It works fine, until the first charge, the charging was ok, but after unplugging I tried to resolve lock gesture, but it stuck and restarts, the restart repeat several times. And after every charging, there are frome three to five restarts and then the phone is available to using.
Unfortunately, the Backup and restore app is not working, it stuck at 8% and then the phone restarts. So I decided to use SUS again, but it doesn't helped. The restarts are still there, no matter if original or non-original charger, so there is no connection to used/downloaded apps.
Is there any help to this issue?
I don't rooted the phone, but the phone is bought as used from credible store.
Thanx for answers
FW: 10.1.1.A.1.253
Click to expand...
Click to collapse
if you bought the phone just a week ago, then why dont you ask your phone-company to resolve the issue. Phone-company is your retailer and from where you purchased the phone.
Why to take risks at your side....
zemko said:
1 - how to repare through SUS? when I connect phone to SUS it show me only the option to re-update phone and it delete all files, so after that is wipe necessary too?
2 - where to get FTF file?
Click to expand...
Click to collapse
op 1- when it says that your phone is up to date there should but a blue line of words saying something repair your phone if you are having issues, just click on that.
op 2- android development section and some in the general section too.
like i said if you seriously dont want to go through all that hassle just take it back to the shop and ask for a new one and show them that youre pissed off and demand for an exchange or something. Show them how it restarts lol.
LitoNi said:
op 1- when it says that your phone is up to date there should but a blue line of words saying something repair your phone if you are having issues, just click on that.
op 2- android development section and some in the general section too.
like i said if you seriously dont want to go through all that hassle just take it back to the shop and ask for a new one and show them that youre pissed off and demand for an exchange or something. Show them how it restarts lol.
Click to expand...
Click to collapse
1 - oh, you mean PC Companion...I don't think, there should be solution with this, because I tried to re-update the FW via SUS and it didn't work
2 - maybe I have no balls for this...
so, I will claim my warranty for this
thanx for answers guys
LitoNi - so the op1 helped, the problem was in micro SD card, after repair the SD card is dead, but the phone is working well, no restart since the repair (three days), even the connection between phone and linux (MTP) is ok and I can move with files...thanx

[Q] XV is almost bricked

I have an unlocked/rooted Xperia V. A few days ago it suddenly shuts down and bootloop. It's not like the previous SOD issue. I tried to flash official FTF and it still happens - suddenly shuts down, even damage the system partition to bootloop. Nanodroid and Flashtool don't help at all. I assume that maybe it got physical damage on system partition memory? The SONY service say no repair due to the unlock status.
What could I do to save this XV?
phhuang said:
I have an unlocked/rooted Xperia V. A few days ago it suddenly shuts down and bootloop. It's not like the previous SOD issue. I tried to flash official FTF and it still happens - suddenly shuts down, even damage the system partition to bootloop. Nanodroid and Flashtool don't help at all. I assume that maybe it got physical damage on system partition memory? The SONY service say no repair due to the unlock status.
What could I do to save this XV?
Click to expand...
Click to collapse
Relock your bootloader, and then REPAIR via PC Companion
it will help for sure, and if it still has the problem ,then it maybe is a physical problem (which is WAY WAY out of imaginations if you haven't dropped your phone from 6th floor of your apartment )
ebi4321 said:
Relock your bootloader, and then REPAIR via PC Companion
it will help for sure, and if it still has the problem ,then it maybe is a physical problem (which is WAY WAY out of imaginations if you haven't dropped your phone from 6th floor of your apartment )
Click to expand...
Click to collapse
Yes, I just relock it and repair via PC Companion. Then I unlock->fully restore from CWM->same issue happens again! I'm trying not adjust anything related to the kernel. Hope it works!
phhuang said:
Yes, I just relock it and repair via PC Companion. Then I unlock->fully restore from CWM->same issue happens again! I'm trying not adjust anything related to the kernel. Hope it works!
Click to expand...
Click to collapse
the very moment of FULLY restore via recovery, actually you are restoring THE ISSUE as well!
there is no need to be afraid of manipulating kernel, you just have to know what you are doing
hope it helped

Constant Reboot

Hi received a Z1 today. I updated to 257 straight away but the phone keeps rebooting itself. It's really frequent. If I'm using the phone I can pretty much guarantee it will reboot with less than 5 mins of use.
It freezes for a few seconds and then reboots.
Anyone heard anything of this?
Also, it keeps warning me of open flaps and waterproofing? is this standard?
Think I'll have to send it back but just wanted to check there wasnt a easy fix. I've resetted the phone and it still happens with no apps installed or anything which rules out any conflicted applications.
Thanks
leecasey said:
Hi received a Z1 today. I updated to 257 straight away but the phone keeps rebooting itself. It's really frequent. If I'm using the phone I can pretty much guarantee it will reboot with less than 5 mins of use.
It freezes for a few seconds and then reboots.
Anyone heard anything of this?
Also, it keeps warning me of open flaps and waterproofing? is this standard?
Think I'll have to send it back but just wanted to check there wasnt a easy fix. I've resetted the phone and it still happens with no apps installed or anything which rules out any conflicted applications.
Thanks
Click to expand...
Click to collapse
You can try to flash 257 firmware again via flashtool but if you don't have any apps and device is new it's better to return it and take another one or send it on repair.
It's not usual behavior and it shouldn't restart.
Warning for opened flaps should be visible only after upgrade or first boot.
Sent from my Z1
funky0308 said:
You can try to flash 257 firmware again via flashtool but if you don't have any apps and device is new it's better to return it and take another one or send it on repair.
It's not usual behavior and it shouldn't restart.
Warning for opened flaps should be visible only after upgrade or first boot.
Sent from my Z1
Click to expand...
Click to collapse
I keep getting the warning, im wondering if this is a clue that something is up software wise.
Will I void warranty and cause problem returning the phone if I use flashtool?
I also get the warning about waterproof, and to close external covers every time I turn my phone back on and off. Perplexes me too because I always carefully close the flaps after charging. Kinda makes me uneasy. Maybe I should return also. Should be noted phone is completely stock and on latest firmware.
i also got the same problem with my Z1 afterinstalling prerooted .257. already full-wiped -> no result
i dont have any apps that are cleaning/tuning/etc
now formating my 64gb ultra-sdhc from sandisk, hope this will help
will report if there is some change... or not
Caffeineshock said:
i also got the same problem with my Z1 afterinstalling prerooted .257. already full-wiped -> no result
i dont have any apps that are cleaning/tuning/etc
now formating my 64gb ultra-sdhc from sandisk, hope this will help
will report if there is some change... or not
Click to expand...
Click to collapse
I got some diagnostics off the phone. You can follow my progress here with it:
https://plus.google.com/u/0/+LeeCasey/posts/ZBn6opcMBm2
Posted on Plus. Seems a WiFi issue. Try disable WiFi.
After full wipe and firmating my sd Theresa are still 2 reboots per day...
Gesendet von meinem C6903 mit Tapatalk
Hi all. I had the exact same issue but I found a post in another forum on how to fix.
In the display menu ensure that "Optimize Backlight" is enabled. It's a glitch introduced with the latest patch.
As soon as I enabled that setting, my phone stopped rebooting.
Cheers,
brianmjames said:
Hi all. I had the exact same issue but I found a post in another forum on how to fix.
In the display menu ensure that "Optimize Backlight" is enabled. It's a glitch introduced with the latest patch.
As soon as I enabled that setting, my phone stopped rebooting.
Cheers,
Click to expand...
Click to collapse
That option is available only in 534 and lower.
It's not available in 257.
It's strictly software issue because flaps do not have sensors and that warning you are constantly getting shouldn't appear every time you boot device...
It should appear only for the first time to warn you and, if I remember correctly, yoy can tick checkbox "don't show it next time".
If some of you have this problems don't flash nothing - you could lose warranty.
Just take your phone and return it or send for repair.
Sent from my Z1
Noone will loose his waranty because of flashing
Its the BL you need to open to loose it ^^
Its something wrong with the wifi, i know it... Never got a reboot with disabled WLAN
Gesendet von meinem C6903 mit Tapatalk
Caffeineshock said:
Noone will loose his waranty because of flashing
Its the BL you need to open to loose it ^^
Its something wrong with the wifi, i know it... Never got a reboot with disabled WLAN
Gesendet von meinem C6903 mit Tapatalk
Click to expand...
Click to collapse
Don't be so sure.
If you flashed other version, the one that isn't meant to be on your phone (if you bought phone from your carrier) and try to send it for a warranty - you could pay for repair.
Been there - tried that.
Maybe it's not right but it could happen so - I would recommend - first contact seller.
Some of sellers won't take your phone (waranty) if you peeled screen protector (original) - mine carrier is O.K with that.
So, it's obviously that all sellers have their own rules - I'm not saying that's good - I'm saying - ask first because it could be very expensive try.
Sent from my Z1
I got a talk with Sony. There is no problem when a original fw based rom was flashed
Gesendet von meinem C6903 mit Tapatalk
I had the reboot problem after updating from (Rooted) 534 to (non root) 257 through PC Companion.
Downgraded to 534 with flashtool, rooted again and updated to 257 through OTA to keep root. reboot issue seems to have gone now (fingers crossed).
ota.... yes it could solve this problem^^
please report after day or 2 of usage about the problem. i also hope that there will be no reboots^^
now after flashing back to .514 to get the ota update (generic de) im not able to install the ota update!?!?!?
after the reboot there is a message with "you device was not updated. try it again" or something like that (translated from german)
does anyone know why this happens and how to solve the problem?
edit---------------------------------
the reason for that was the installed recovery
ill reaport if it helped

[Q] Xperia X8 brick?

Hello everyone!
I'm trying to fix my phone for 2 days still no success.
My problem is:
When i turn on the phone it does nothing,only the screen lights up for like 2-3 seconds after that it turns off.
It keeps doing it again and again until I take out the battery.
It cant even show the sony ericcson logo.
Battery works i tried it with another phone!
PHONE WASNT ROOTED OR FLASHED OR ANYTHING LIKE THAT
Solutions i tried :
Sony ericcson update service - no use
Flashing original firmware with flashtool - no use (btw flash mode works as long the flashing process works like charm)
Hope someone can help me out because there is no more warranty for the phone
Thanks in advance
Erik
erikserif said:
PHONE WASNT ROOTED OR FLASHED OR ANYTHING LIKE THAT
Click to expand...
Click to collapse
Probably a hardware issue, I guess it is time for a new phone.
stamatis said:
Probably a hardware issue, I guess it is time for a new phone.
Click to expand...
Click to collapse
Thanks for the answer!

Categories

Resources