Database Develop

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.

Xperia TX freezing & restarting after JB update

hi everyone....
my brother updated his xperia tx to jelly bean using flash tool before 3 hours... nothing showed in flashtool or the phone about any problem in flashing
in the last hour the phone started to restart & freeze
it's freezing suddenly & you cannot do anything but taking out the battery
can a factory data reset help?? also we have a backup on PC companion so is it recommended to return it on the phone??

Try repair option in PCC.
Tapatalked from my TX

i have problem using FXP212.
My TX goes in endless rebooting. Tried flashing again but same luck. I m downloading FXP210 to try now.

i did repair but its same thing i don't know what to do with it anymore, i would like help if anyone could give
should i downgrade to ICS and download again from PC companion?

smarda7a said:
i did repair but its same thing i don't know what to do with it anymore, i would like help if anyone could give
should i downgrade to ICS and download again from PC companion?
Click to expand...
Click to collapse
Did you do the repair or did you restore the backup?
Click on the update software option and then when it says you have the latest software click on repair my firmware

gregbradley said:
Did you do the repair or did you restore the backup?
Click on the update software option and then when it says you have the latest software click on repair my firmware
Click to expand...
Click to collapse
yea that what i did really twice already and i even reset the phone fully but im not sure whats wrong with it, it keep rebooting from time to time :/

smarda7a said:
yea that what i did really twice already and i even reset the phone fully but im not sure whats wrong with it, it keep rebooting from time to time :/
Click to expand...
Click to collapse
which one! I asked if you repaired or restored a backup.....
If you repair the phone it should be exactly like a factory shipped phone.
My only other thing to say will be have you got anything in your sd card (Both internal or external) that may be causing this? Any init.d scripts that reduce voltage etc...try deleting the contents of the sdcards and repairing again. (Obviously back anything up you want to keep)

gregbradley said:
which one! I asked if you repaired or restored a backup.....
If you repair the phone it should be exactly like a factory shipped phone.
My only other thing to say will be have you got anything in your sd card (Both internal or external) that may be causing this? Any init.d scripts that reduce voltage etc...try deleting the contents of the sdcards and repairing again. (Obviously back anything up you want to keep)
Click to expand...
Click to collapse
i did repaired twice from PC companion and did once i think from the phone itself, and i don't have Scards its only the phone internal storge..
when i did it first in flash tool it didn't give me any error and then i did repaired it twice from pc companion however whats strange in ICS i never had the reboot problem
and if i remember correctly it only delete the programs etc, but the photos/music etc it never left the phone with both options i did...
so you suggesting to also wipe internal storage and repair to see if it reboot or not? i already have back up for all stuff so it won't hurt to try
thanks alot really for helping and sorry for my bad english ^^;

If you have a backup then try it.
Have you got a bootloop or do you have some reboots? What i mean is, does the phone actually boot up and only reboot occasionally or is it just bootlooping?

gregbradley said:
If you have a backup then try it.
Have you got a bootloop or do you have some reboots? What i mean is, does the phone actually boot up and only reboot occasionally or is it just bootlooping?
Click to expand...
Click to collapse
nah it freeze and reboot when i use it after certain amount of time, sometimes when it reboot it doesn't even give me option to enter my password
the phone start up like there is no lock

I also have this problem with my LT30a. This started the very first time I flashed a Rom ( locked bootloader) that was meant for an LT30p. Sense then I have reverted back to my stock ROM, still have the issue but not so often.
Sent from my LT30a using xda premium

so now i did wipe to internal storage and did repair and such now im facing new problem the phone turn off and and when i try to switch it on...it wont work i have to remove battery and insert it again to make it work, any idea?

How this end up? Anyone has find a solution for this problem? I have xperia t with same problem. The phone mostly freezes and restarts on long listings like fb/twitter feeds, messages...

i have TX same on my device freeze and some times don't wakeup only when battery pulled out

[SOLVED] My Xperia t touchscreen suddenly doesn't work anymore

Yesterday I went to a party, nothing wrong with the xperia t. When I got home I let it recharge. I think it still worked at that moment. Pretty sure it did. Went to sleep. Woke up. My phone battery was empty lol. Still in the recharger. Did some stuff, let it recharge some more. Got it to boot up again. Now touch screen doesn't work anymore . Tried wiping cache, factory reset. Still not working.
I have cm-10.1.3-RC2-mint installed. I think I might have to update it. This could be the problem.
Any more tips for if it doesn't work? never had this problem before. I hope it is a software thingy.

I updated the firmware but still doesn't work. I think im gonna re-install the stock firmware, and flash a stock kernel which will unroot my mobile. Any tips? please? I can't use my phone at all atm. It just stays at the cyanogenmod install screen..

Reflash the touch firmware
read this
http://forum.xda-developers.com/showthread.php?t=2220290&highlight=touch+screen+not+working
especially post 11

gregbradley said:
Reflash the touch firmware
read this
http://forum.xda-developers.com/showthread.php?t=2220290&highlight=touch+screen+not+working
especially post 11
Click to expand...
Click to collapse
I would like to try that thing with adb, but as I have already reinstalled cyanogenmod, developer options/debugging is turned off. I can't use ADB. Unless you know another way.

So this is totally getting out of hand.. (and I don't know if that is also a english expression lol).
I tried reflashing a stock firmware. Worked, but touchscreen still doesn't work. Then I noticed, that I now don't have cwm anymore... how the f?
SO I probably forgot to exclude the kernel. So now I tried reflashing a kernel with cwm, but flashtool doesn't recognize the kernel files... I don't know what is going on..
Ah already found the problem. Got cwm back phewww..
So here is what needs to be done. I want to try gregbradleys adb shell fix but my usb debugging is off and this means that I can't use adb, as I don't have touchscreen.
So, is there any way, any way at all, to enable usb debugging without touching the screen? Maybe a kernel with that settings automaticly set?
Im getting a bit angry at my phone now.. I didn't even do anything to break it in the first place. Just tried recharging it, and that killed the touchscreen? lol. Help will be appreciated. Im out of ideas.

Get a usbotg cable and attach a usb mouse
Then use that to turn debugging on
When you flash a stock firmware you lose recovery.
Sent from my C6903 using xda premium

thanks, I'll get one tomorrow. I hope it will help. You've helped me before so im pretty confident that you fix my problem again haha. You are a boss.

A non responsive touch screen happened to me too after I flashed a wrong firmware. I flashed back the version that was on before, but it didn't help. Only after I flashed this (pretty old) version Xperia T - 7.0.A.1.303 Generic DE with Flashtool, the touch screen started to working again. I am not sure, maybe any ftf would work. But I know that I had success with this one.
You should try gregbradleys method first though. Funny, that your touch screen stopped working, without you modifying anything. Hopefully it's not a hardware problem.

gwodus said:
A non responsive touch screen happened to me too after I flashed a wrong firmware. I flashed back the version that was on before, but it didn't help. Only after I flashed this (pretty old) version Xperia T - 7.0.A.1.303 Generic DE with Flashtool, the touch screen started to working again. I am not sure, maybe any ftf would work. But I know that I had success with this one.
You should try gregbradleys method first though. Funny, that your touch screen stopped working, without you modifying anything. Hopefully it's not a hardware problem.
Click to expand...
Click to collapse
hmmm, I tried this and it worked. problem solved. I did however not have wrong firmware installed, but it was an rc2 version of cm. So it can be unstable and stuff, but this was kind of a big problem.

quinten96 said:
hmmm, I tried this and it worked. problem solved. I did however not have wrong firmware installed, but it was an rc2 version of cm. So it can be unstable and stuff, but this was kind of a big problem.
Click to expand...
Click to collapse
Hey, glad your phone is ok again. I remember when that happened to me. I just had the phone for a couple weeks. Shat my pants, thinking I wrecked it. It worked out at the end, though. Feels good to recover a bricked phone, doesn't it.

Sorry to bump
gwodus said:
Hey, glad your phone is ok again. I remember when that happened to me. I just had the phone for a couple weeks. Shat my pants, thinking I wrecked it. It worked out at the end, though. Feels good to recover a bricked phone, doesn't it.
Click to expand...
Click to collapse
I am having this exact problem! I'm sorry to awake this sleeping thread, but I have a locked bootloader and I tried a Sony PC Companion reset and it still has the problem. Is there anything else I can do?

jmm288 said:
I am having this exact problem! I'm sorry to awake this sleeping thread, but I have a locked bootloader and I tried a Sony PC Companion reset and it still has the problem. Is there anything else I can do?
Click to expand...
Click to collapse
I have the same problem... I changed touch panel, flex cable and update with pc-companion but it doesn't work

Red Triangle Stock Sense 6 update

Just received the stock update to Sense 6. I am in Canada, on Telus, fully stock.
When the phone boots into the recovery to flash the update, I am getting a red triangle and the error is unexpected contents in settings.apk
Any suggestions on how to get this update working other than hard resetting before the update?
Thanks.

Can you reboot normally? Just select the Reboot system option? Also, if it insists on going to update, hold power button to forcefully restart and keep pressing the volume down button to get into bootloader mode.
Try restart from there.
As you are FULLY stock (no root, should say LOCKED on that bootloader screen) you can either consider going through the warranty OR trying it yourself to fix by unlocking bootloader OR take it to someone locally.
Unfortunately all options will lead to data loss.

SaHiLzZ said:
Can you reboot normally? Just select the Reboot system option? Also, if it insists on going to update, hold power button to forcefully restart and keep pressing the volume down button to get into bootloader mode.
Try restart from there.
As you are FULLY stock (no root, should say LOCKED on that bootloader screen) you can either consider going through the warranty OR trying it yourself to fix by unlocking bootloader OR take it to someone locally.
Unfortunately all options will lead to data loss.
Click to expand...
Click to collapse
Yes it reboots and yes I have a locked bootloader. I would hard reset before sending it out for servicing.
Any other people having this issue?

mfpreach said:
Yes it reboots and yes I have a locked bootloader. I would hard reset before sending it out for servicing.
Any other people having this issue?
Click to expand...
Click to collapse
Not heard of a problem while updating. You are special.

What are your guys thoughts on flashing a stock ruu and then trying to ota to sense 6?

mfpreach said:
What are your guys thoughts on flashing a stock ruu and then trying to ota to sense 6?
Click to expand...
Click to collapse
Great idea!

mfpreach said:
What are your guys thoughts on flashing a stock ruu and then trying to ota to sense 6?
Click to expand...
Click to collapse
Did your problem solved?

Haha I haven't been able to try, on my 8.1 box I get an error 170 when trying to connect the phone in ruu. On my win7 box the ruu just auto closes....

mfpreach said:
Haha I haven't been able to try, on my 8.1 box I get an error 170 when trying to connect the phone in ruu. On my win7 box the ruu just auto closes....
Click to expand...
Click to collapse
well error 170 is either because your drivers aren't installed correctly or because you have a bad usb cable/port

alray said:
well error 170 is either because your drivers aren't installed correctly or because you have a bad usb cable/port
Click to expand...
Click to collapse
Thanks,I will look into it tomorrow.
Are there even good drivers for 8.1 yet bearing in mind I don't have a USB 3 port?

mfpreach said:
Thanks,I will look into it tomorrow.
Are there even good drivers for 8.1 yet bearing in mind I don't have a USB 3 port?
Click to expand...
Click to collapse
hi, we have similar issues although mine is the soundhound_freemium.apk instead of settings.apk, I hope that you will get your issue settled and also update me and the rest of us who are having the issues here. good luck and thanks! (do check out my thread which I've just posted like 5 minutes back!)

Do not install sense 6 upgrade
I would recommend NOT installing the stock Sense 6 upgrade. I installed it a couple days ago and currently my phone is bricked because of it.
I posted about my issue in another thread. In case people want to read what's been going on i'll repost it here.
Kg810 said:
So I performed the Sense 6 upgrade a couple days ago, update went through fine, yesterday morning my phone started acting all weird (sluggish, random reboots, bunch of apps reporting errors, etc) and battery was draining fast.
I probably rebooted my phone 10 times, 5 times normally by just the power button and the remaining times through the light trick, power button and volume button. Once my phone finally got back to normal, I was typing on whatsapp and then suddenly it froze.
It froze for a couple minutes and then it turned off. I believe the battery was at 39%. I plugged the phone into my work computer and it would make the USB connection sound, then after a few seconds it would display drivers failed to install followed by 3 subtle sounds similar to the connection sound. So right away I checked Device Manager and it displayed QHSUSB_DLOAD.
Currently my phone has been charging all night, currently it is being charged at work and there has been no sign of life.
I've tried putting it in the freezer, the light trick, the laptop connecting/disconnecting trick, and the go ole punching the phone trick. None of them have worked.
The phone is definitely not charging at this point as it is stone cold when I hold it or touch the wall charger.
Any ideas what I can do? I don't want to contact Rogers and have to send it in. I've got so many songs, videos and pictures I have yet to backup.
Any help and/or suggestions welcome.
Click to expand...
Click to collapse

Kg810 said:
I would recommend NOT installing the stock Sense 6 upgrade. I installed it a couple days ago and currently my phone is bricked because of it.
Click to expand...
Click to collapse
Well your issue have nothing to do with the sense 6 update. You even said that you have updated the phone a couple of days before your phone died. QHSUSB_DLOAD mode mean your phone motherboard is dead, either because of an hardware failure or because you have flashed something really wrong (probably not your case). So how an hardware failure could be caused by a sofware update and only occur days later....? unfortunately, you must send your phone for repair.
---------- Post added at 05:23 PM ---------- Previous post was at 05:22 PM ----------
mfpreach said:
Thanks,I will look into it tomorrow.
Are there even good drivers for 8.1 yet bearing in mind I don't have a USB 3 port?
Click to expand...
Click to collapse
if you have a win7 computer, then use that one.

alray said:
Well your issue have nothing to do with the sense 6 update. You even said that you have updated the phone a couple of days before your phone died. QHSUSB_DLOAD mode mean your phone motherboard is dead, either because of an hardware failure or because you have flashed something really wrong (probably not your case). So how an hardware failure could be caused by a sofware update and only occur days later....? unfortunately, you must send your phone for repair.
Click to expand...
Click to collapse
Maybe I wasn't clear.
Tuesday night before I went to bed I performed the upgrade.
Wednesday morning, is when the issues started occuring.
Today is May 29th, Tuesday was May 27th, which is 2 days ago, hence why I said I performed the upgrade a couple days ago.
From the time I performed the install Tuesday night to Wednesday morning when I got into work, there was nothing done to the phone. The only thing that was done was the Sense 6 upgrade.
So you're trying to tell me that the upgrade has nothing to do with it?

Kg810 said:
So you're trying to tell me that the upgrade has nothing to do with it?
Click to expand...
Click to collapse
If your phone was 100% stock, I highly doubt the ota could hard brick it.
like I said QHSUSB_DLOAD = defect motherboard
in most cases because:
1- hardware failure
or
2- Flashing something that screwed your phone (i.e flashing something not meant for your phone with S-OFF)
I'm not saying its impossible, but I think it's more a coincidence

alray said:
If your phone was 100% stock, I highly doubt the ota could hard brick it.
like I said QHSUSB_DLOAD = defect motherboard
in most cases because:
1- hardware failure
or
2- Flashing something that screwed your phone (i.e flashing something not meant for your phone with S-OFF)
I'm not saying its impossible, but I think it's more a coincidence
Click to expand...
Click to collapse
I've had the phone for a little over a year and it has been 100% stock. Never tinkered with it in any way shape or form.
I just can't see how it is a mere coincidence that right after the update, my phone starts acting up, and then becomes bricked.

Kg810 said:
I've had the phone for a little over a year and it has been 100% stock. Never tinkered with it in any way shape or form.
I just can't see how it is a mere coincidence that right after the update, my phone starts acting up, and then becomes bricked.
Click to expand...
Click to collapse
Anyway, your only way out of this qhsusb brick is to send your phone for repair.
Sorry

mfpreach said:
Yes it reboots and yes I have a locked bootloader. I would hard reset before sending it out for servicing.
Any other people having this issue?
Click to expand...
Click to collapse
facing same problem with you. my problem haven't fix. from malaysia

akasi91 said:
facing same problem with you. my problem haven't fix. from malaysia
Click to expand...
Click to collapse
From Malaysia as well, hey mind telling me how big is your sense 6 update download size?

kuzumitaiga said:
From Malaysia as well, hey mind telling me how big is your sense 6 update download size?
Click to expand...
Click to collapse
6xxmb.

[Q] Moto G (2014) Wifi not turning on

Hi all,
I am the new owner of a Moto G (2014) a few weeks now but since last weekend, I have been having major issues with my wi-fi. It refuses to turn on for me for some reason. The phone is not rooted and I have tried a factory reset from the settings menu so not sure what is causing the issue with the wi-fi. The phone is otherwise working fine bar the battery has been draining a lot quicker the last few days. Would appreciate any help with fixing this.

Do factory reset or flash stoc firmware.

scroochie said:
Hi all,
I am the new owner of a Moto G (2014) a few weeks now but since last weekend, I have been having major issues with my wi-fi. It refuses to turn on for me for some reason. The phone is not rooted and I have tried a factory reset from the settings menu so not sure what is causing the issue with the wi-fi. The phone is otherwise working fine bar the battery has been draining a lot quicker the last few days. Would appreciate any help with fixing this.
Click to expand...
Click to collapse
U should factory reset and wiped cache for better performance of lollipop..
Sent from my XT1068 using XDA Free mobile app

[email protected] said:
Do factory reset or flash stoc firmware.
Click to expand...
Click to collapse
Thanks for replying, tried doing a hard factory reset last night and it made no difference going to try flash stock firmware this evening. Fingers crossed it will work, havent done this before but will follow one of the guides on here.

scroochie said:
Thanks for replying, tried doing a hard factory reset last night and it made no difference going to try flash stock firmware this evening. Fingers crossed it will work, havent done this before but will follow one of the guides on here.
Click to expand...
Click to collapse
:good: