Develop Bugs

Would a Nandroid help me here?

Recently, my Play has been having some touchscreen issues. It will work perfectly for almost a day and then proceed to lock up. Screen still turns on with the power button and sliding the gamepad out unlocks the phone but the touchscreen becomes unusable.
Also I've noticed that some kernels are not booting either. Kernels that have worked for me in the past. Even some of the ftf firmware files wont work. The only one I can get working is 2.3.2 and UK generic 2.3.4 (4.0.2.A.42). The UK one then prompts me to upgrade to 4.0.2.A.42, which its already running :S
PC Companion says theres a problem updating my phone regardless of what firmware Im running as well and SEUS just closes on me after I click the Xperia Play.
Originally, I thought that this was a damaged digitiser. Now, seeing as Im having all these issues, Im starting to doubt that.
Would a Nandroid of another ROM (one that uses stock kernel i.e 2.3.2 or 2.3.4 from the ftf files I have) be able to correct the dodgy system issues Im having?
Or is my Play dead now?
Any help would be great

Anyone?

I think it would do the trick. As full restore givs ur phone the exact state of ur phone before it was faulty. Same as a pc recovery. Hope that help.

sdojoin said:
I think it would do the trick. As full restore givs ur phone the exact state of ur phone before it was faulty. Same as a pc recovery. Hope that help.
Click to expand...
Click to collapse
Just need to find a Nandroid now to try it out

CTU_Loscombe said:
Just need to find a Nandroid now to try it out
Click to expand...
Click to collapse
I also had this issue, but mine got progressively worse and the screen stopped responding altogether, and had to take it in and get a new one from Verizon due to hardware failure.
I would suggest doing a full backup (if you haven't already) and flashing your firmware and doing a factory reset...if your still having screen issues then its the phone.

ricenlives said:
I also had this issue, but mine got progressively worse and the screen stopped responding altogether, and had to take it in and get a new one from Verizon due to hardware failure.
I would suggest doing a full backup (if you haven't already) and flashing your firmware and doing a factory reset...if your still having screen issues then its the phone.
Click to expand...
Click to collapse
Yeah its the phone. Sold it for parts. Moving to HTC
Long story short, Ive had nothing but issues with SE devices. My brothers Play came with a dodgy power button and volume down rocker. My X10Mini touchscreen and system failed 2 months after getting it. Now my Play has died
Sticking around the Play forums to help people though

Constant Reboots!! PLEASE HELP!!!!

Hi guys,
I am using a Sony Ericsson Xperia Arc and am having a lot of trouble with the device constantly crashing and rebooting.
when this first happened these are the steps i took.
i completely wiped the device (factory reset, wipe dalvik cache, wipe cache partition, format system)
i then flashed Baseband 77 using flashtool
i then flashed fxp149 using flashtool
i then flashed Baseband 77 libs using CWM
i then flashed AOKP JB M1-R1 ROM using CWM
i then flashed gapps using CWM
i the reloaded all apps from the market and not applied any backups and yet it still rebooted all the time.
Since then i have tried using
Fusion 3.8
Fusion 3.9
Fusion 4.0
FXP 148
FXP 150
Stock Kernel inside ROM .zip file.
I have also tried putting it back to Baseband 72 but it made no difference.
None of these make any difference to my issue and yet before i had the issue, I had used all of these kernels except FXP 150 and they all worked fine with no issues at all.
I then decided to go all the way back to stock firmware as it is out of the box.
so I used flashtool and flashed LT18i_4.1.B.0.587_(1254-2716).ftf
I reloaded my applications and monitored the device only to see that by the next day, the problem had returned.
I am now at the end of my tether and do not know what else i can possibly do to figure out the issue.
the device has not been dropped or damaged in any way so there is no reason for a hardware fault.
i desperately NEED this device to be working as i use it on a daily basis for my business and cannot live with out it.
IF THERE IS ANYONE OUT THERE THAT COULD PLEASE PLEASE PLEASE HELP I WOULD BE FOREVER IN YOUR DEBT!!!!!!!

i also have a logcat that i was running in the background when one of the reboots happened
not sure if that can tell anyone anything but i have it if it does

First flash stock kernel (587), after flash the rom compatible with kernel. Remember full wipe before

have you tried not to restore your apps? Maybe one of them causes the problem. I'd try to stick with the clean (stock) rom an check if it still reboots. If it does I guess your device is ready for ebay

Could be a loose battery, try a bit of paper between the battery and the cover and see if that helps.

XperienceD said:
Could be a loose battery, try a bit of paper between the battery and the cover and see if that helps.
Click to expand...
Click to collapse
thanks for the suggestion but my battery is not loose and i have tried your method but with the same results.
weaselmetal said:
have you tried not to restore your apps? Maybe one of them causes the problem. I'd try to stick with the clean (stock) rom an check if it still reboots. If it does I guess your device is ready for ebay
Click to expand...
Click to collapse
hmmm i thought if that were the case there would be others experiencing it too.
i will take your idea and post results.
thank you very much
rod555 said:
First flash stock kernel (587), after flash the rom compatible with kernel. Remember full wipe before
Click to expand...
Click to collapse
i tried this, unfortunately i had the same issues occurring.
thank you for your suggestion

Needs a trip to the Service Centre then by the sounds of it.

XperienceD said:
Needs a trip to the Service Centre then by the sounds of it.
Click to expand...
Click to collapse
yes i am starting to think that may be my next move
will i have an issue with getting it repaired since i have unlocked my bootloader, flashed different kernels and roms and rooted the device?
if so, is there any way i can get it back to official "out of the box" state?

Flash a stock ftf and get the bootloader relocked. Having it rooted is fine
Sent from my lt18 using xda premium

tangosierra_ said:
Flash a stock ftf and get the bootloader relocked. Having it rooted is fine
Sent from my lt18 using xda premium
Click to expand...
Click to collapse
any chance you could explain a little about how to do that or possibly provide links to downloads or pages of instructions?

plastic_prophet said:
any chance you could explain a little about how to do that or possibly provide links to downloads or pages of instructions?
Click to expand...
Click to collapse
Here:- http://forum.xda-developers.com/showthread.php?t=1324703
Sent from my LT15i using xda premium

i have come across something quite interesting.
i had someone look at the logcat i had running live when i had a reboot and it showed that the last thing to function before the reboot was wifi scanning. they suggested i try turning off wifi and running the live logcat again to see if any reboots occured.
it has now been just over 48 hours and i have not had a reboot at all. i know is because my terminal session is still running the live logcat.
is there anyone that could suggest why this may be happening?
i mean, i know its wifi that is causing the problem, but would that be a hardware issue that could be fixed under warranty? or something else?
any suggestions are appreciated as always

plastic_prophet said:
i have come across something quite interesting.
i had someone look at the logcat i had running live when i had a reboot and it showed that the last thing to function before the reboot was wifi scanning. they suggested i try turning off wifi and running the live logcat again to see if any reboots occured.
it has now been just over 48 hours and i have not had a reboot at all. i know is because my terminal session is still running the live logcat.
is there anyone that could suggest why this may be happening?
i mean, i know its wifi that is causing the problem, but would that be a hardware issue that could be fixed under warranty? or something else?
any suggestions are appreciated as always
Click to expand...
Click to collapse
i don't think i can help, i just wanna say that i had (have) the same problem. I said had/have because probably I still have the issue, but i don't notice it that often. Before, I had my phone set to ask for pin code, but now I have removed it to avoid being unreachable if a restart occurs. I have raised the issue long time ago, but really didn't find any answer. Other ppl had same problem with their phone (look at the thread i started about this issue http://forum.xda-developers.com/showthread.php?t=1765537)
I also have HTC desire in daily use with CM7.2, that also reboots quite often. So I don't think the phones are broken. More likely it's kenel or rom or app issue, or some combination of those.
If you can tell me how to monitor things, I can do it on both phones, maybe we will figure out what's going on.

lalek said:
i don't think i can help, i just wanna say that i had (have) the same problem. I said had/have because probably I still have the issue, but i don't notice it that often. Before, I had my phone set to ask for pin code, but now I have removed it to avoid being unreachable if a restart occurs. I have raised the issue long time ago, but really didn't find any answer. Other ppl had same problem with their phone (look at the thread i started about this issue http://forum.xda-developers.com/showthread.php?t=1765537)
I also have HTC desire in daily use with CM7.2, that also reboots quite often. So I don't think the phones are broken. More likely it's kenel or rom or app issue, or some combination of those.
If you can tell me how to monitor things, I can do it on both phones, maybe we will figure out what's going on.
Click to expand...
Click to collapse
if you open a terminal session and type:
su
cd sdcard
logcat >> logcat.txt
it will create a .txt file and put the live logcat info into it.
you need to leave the terminal running in the background to make sure it continues to update
then when you see a reboot just get the logcat.txt file from the sd card and open it in wordpad or something. (notepad doesnt display properly)
have a look at the last thing that happened before the reboot and see what it tells you
mine had info about wifi scanning and showed that it had seen ssids
next step was to turn wifi off to see if the problem stayed or resolved.
good luck!! id love to hear how it goes

[Q] Xperia arc s screen issue,please help

please help
I am weak with English, but I hope you will understand me.
This is a problem with our XPERIA Arc, bootloader is unlocked and installed a custom rom Xperia ™ HD Ultimate 2.0.2, but the problem occurs on the other ROM.
Sometimes it happens that when I pressed the power button, the phone's screen does not turn on the lock screen but remain black but can be seen in the background light illumination.
Mobile phone can receive calls then everything works but nothing is visible on the screen, the screen is touch-sensitive.
Once it was repaired by itself or by pressing the power button several times and sometimes nothing without removing the battery.
I noticed that this is a common cell phone stays on while the charger.
Please help, what should I do?

"but the problem occurs on the other ROM."
What other ROM?
Try format your SD-card and a fresh install of HD 2.0.2.
Btw.. HD 2.0.3 might come today

Tesla said:
"but the problem occurs on the other ROM."
What other ROM?
Try format your SD-card and a fresh install of HD 2.0.2.
Btw.. HD 2.0.3 might come today
Click to expand...
Click to collapse
occurs with this
http://forum.xda-developers.com/showthread.php?t=1836993
with factory Rom was not the problem.

JELLY SANDWICH 8.5??
But you said Xperia ™ HD Ultimate 2.0.2

Tesla said:
JELLY SANDWICH 8.5??
But you said Xperia ™ HD Ultimate 2.0.2
Click to expand...
Click to collapse
its, I want to say that I tried the two differently roms only, and both are happening, now is the Ultimate HD on XPERIA.

gogYCH said:
its, I want to say that I tried the two differently roms only, and both are happening, now is the Ultimate HD on XPERIA.
Click to expand...
Click to collapse
now it happens on every rom I've tried.
I went back to the stock rom and the same error occurs, sometimes 5-6 times I pressed the power button to turn on the screen.
Is there a process that the cell phone back to its original factory condition, remain some files modified by installing custom ROMs, no matter if I install a stock rom?

your phone might be overheating? does it get extremely hot when charging?

jman2131 said:
your phone might be overheating? does it get extremely hot when charging?
Click to expand...
Click to collapse
no, it's normal.

here's my video of the problem
http://youtu.be/D5dk_IBCl40

Did you install device-specific patch?
Tried installing stock ROM?

was crtoeko
Someguyfromhell said:
Did you install device-specific patch?
Tried installing stock ROM?
Click to expand...
Click to collapse
I installed everything according to the instructions for the specific rom. repeatedly tried the same rom.
Many times I have returned to the stock rom.
But the same is happening to everyone.
I looked in the root file and I see that some have even date from 2008. year, is it normal?
Does installing new rom deleted all files from previous rom that was installed?

gogYCH said:
here's my video of the problem
http://youtu.be/D5dk_IBCl40
Click to expand...
Click to collapse
hmm, i think it's a hardware problem. The screen may not be properly connected. that kind of thing happened to my lappy once . Take it to the service peeps

jman2131 said:
hmm, i think it's a hardware problem. The screen may not be properly connected. that kind of thing happened to my lappy once . Take it to the service peeps
Click to expand...
Click to collapse
if the problem why hardwerski happens when a mob in cw recovery mode, and once he manages to turn the screen still works well until you are back off or go to sleep?

The problem is solved
I really tried all sorts of ways, but the problem was the micro sd card needed to be formatted and just repeat the process again and now all is well.
Thanks to everyone who tried to help!
Merry Christmas everyone!
edit:
Unfortunately, no.
Repeated.

C6502 failed OTA

Hello everyone.
I had tried to update my ZL just now.
Well, I have to say that it didn't go well.
Here's my spec:
C6502, .101 Stock
Towelroot rooted, locked(Never tried to unlock), SuperSU(OTA survival on)
NUT dual recovery
Xposed framework--uninstalled legally through installer
Here's my sits:
100% battery, .230 OTA downloaded.
Then I OTAed it.
After reboot, things looked so ordinary.
SONY logo appeared with red LED lit(Well, in fact I do not know what does it stand but I guess it's because of NUT recovery)(Thanks NUT BTW).
Then, the cute lil' Android with a rotating polygon stuff in it's belly.(I guess its a pretty normal update screen)
Suddenly, after a minute or so, my screen goes black, and refuse to respond to any hard keys.
After an hour, I force-shut down it, desperately.
I tried reboot it ten mins later, and it booted normally, nothing bad happed, except a prompt says that it failed to update.
Well, I guess that's it. I gonna try to flash it days later.
But, I know there's a lot of great people here and you all may give me some sort of information so I can realize what was really going on.
Anyway anything provided is much appreciated.
Thanks for watching this thread. Hope you all have a great day!
(F the summer vacation home works)
(F the curse word filtering)
Sent from my C6502 using XDA Free mobile app

psycho-punk said:
So now youre booting into .101?
Click to expand...
Click to collapse
Yes, I am using .101 now. It seemed that the attempt to update had failed but has left no bad effects.
Sent from my C6502 using XDA Free mobile app

OTA doesn't work if you changed some system app or recovery. For me it only worked with 100% stock.
Didn't test it with a non-modified rooted stock though.

tom282f3 said:
Hello everyone.
I had tried to update my ZL just now.
Well, I have to say that it didn't go well.
Here's my spec:
C6502, .101 Stock
Towelroot rooted, locked(Never tried to unlock), SuperSU(OTA survival on)
NUT dual recovery
Xposed framework--uninstalled legally through installer
Here's my sits:
100% battery, .230 OTA downloaded.
Then I OTAed it.
After reboot, things looked so ordinary.
SONY logo appeared with red LED lit(Well, in fact I do not know what does it stand but I guess it's because of NUT recovery)(Thanks NUT BTW).
Then, the cute lil' Android with a rotating polygon stuff in it's belly.(I guess its a pretty normal update screen)
Suddenly, after a minute or so, my screen goes black, and refuse to respond to any hard keys.
After an hour, I force-shut down it, desperately.
I tried reboot it ten mins later, and it booted normally, nothing bad happed, except a prompt says that it failed to update.
Well, I guess that's it. I gonna try to flash it days later.
But, I know there's a lot of great people here and you all may give me some sort of information so I can realize what was really going on.
Anyway anything provided is much appreciated.
Thanks for watching this thread. Hope you all have a great day!
(F the summer vacation home works)
(F the curse word filtering)
Sent from my C6502 using XDA Free mobile app
Click to expand...
Click to collapse
Force shutting down the device while you got this 'cute' Android thing then black screen can result a hard brick
BE VERY CAREFUL NEXT TIME
BTW flash STOCK ROM FTF file with flashtool might help you
Tapatalk'd from my Xperia™Z (C6602) running Dirty Unicorns ROM!

Screen issue after .90 update

Hello,
i have the same issue as described in the thread below and shown in this video ==> https://vid.me/NGc5
== > http://www.asus.com/zentalk/forum.php?mod=viewthread&tid=41205&extra=page=1&page=1
i have been suffering from same issue since the .90 update, i tried flashing the 1.1GB file using adb which didn't solve the issue along with the yesterday update
anyone having the same problem?
i want to flash the older .63 version, but using adb it says that it can't flash older version than the current version , anyone can help with that ?

@Asus_USA
any info please

I downgraded the rom to a version from July, yet the same issue persist
Seems like a member mentioned somewhere else that the. 90 update might have broken some hardware using code that is not reversible
Waiting for any feedback from Asus
Sent from my GT-N7000 using Tapatalk

That's actually a screen or onboard video issue.... I see this on laptops all the time

Frankenberrie said:
That's actually a screen or onboard video issue.... I see this on laptops all the time
Click to expand...
Click to collapse
the weird thing that it only happened after the .90 update and several users are reporting it

And some software works fine, like whatsapp where the screen is normal while inside it
Sent from my GT-N7000 using Tapatalk

more users are reporting the same issue on the zentalk forum, good luck all avoiding this

no one else here on the forum suffering from the same issue ? any ideas for troubleshooting or solving ?

@ASUS_Khang
can you please confirm that this is a software issue that will be solved through an update and not a hardware failure ?

AhmadOkda said:
no one else here on the forum suffering from the same issue ? any ideas for troubleshooting or solving ?
Click to expand...
Click to collapse
I am also having this SAME issue ! I have unlocked my bootloader, root access, and flashed the 2.40.97 update again, I tried downgrading, it won't let me install and lower update over an higher one. and I can't get twrp recrovery to stay after the flash, it always goes back to the stock recovery. Also I know whats causing the problem. it's the Auss / powered by intel animated screen , First you have the Asus splash screen, Then the Animated Asus / Intel animation Then the boot animation screen. after unocking my bootloader, and changing the boot animation. I can tell you for sure, the Asus / Intel animation that is causing the issue !. I don't know where this animation is stored on the phone, if anyone knows. maybe we can restore of get rid of it. Anyway my phone is pretty much useless right now, can't use the keypad on the call screen, and can't even see the bottom half of the phone, IT's NOT a hardware problem. like some people have said. it's that dam Asus / Intel animation at starup.

I tried downgrading (using fastboot and abd) to every available firmware and nothing solved this problem
IMHO I think that the 90 upgrade triggered a bug while flashing boot partition
Sent from my GT-N7000 using Tapatalk

UPDATE.. I was able to install cm-12.1-20151011-UNOFFICIAL-Z00A.zip 2015-10-11 01:29 Using Windroid UIniversal Android toolkit. and it worked. and TWRP also the recovery.
Unlocked bootloader, rooted phone, installwd TWRP. Flashed boot, droidboot, with WW. 2.12.40.09 Z00A Then installed cm-12.1-20151011-UNOFFICIAL-Z00A.zip 2015-10-11 01:29 . The screen problem IS still there ! \ Anyone else have any ideas ? ~ Travis

My phone (ZE551ML) developed the same issue. When flashing back to stock didn't work, I sent it in for an warranty RMA. A part was replaced and the phone sent immediately back. Not a word to me about the unlocked bootloader. Just make sure if you send it in, that you state you did flash attempt flashing to stock, and make sure the phone is as close to stock as you can get. Factory reset the phone and go.

I tried last week 3 times I got an RMA & then an advanced RMA and i'm getting the run around from them. they even had the hold of 344.00 on my checkings account to the advanced RMA and then THEY canceled the RMA and everytime I talked to them 3 different customer support people then said " sorry we're updating our systems call back tomorrow. " I got told that 3 times and I've called 4 times. the phone is pretty much useless at the moment.

If they send the phone back to you, the part that was replaced on mine is "90AZ00A1-M02610". Dunno if you can get that part yourself and have it repaired by a third party, but other than that I wouldn't know what to do in your situation.

ArmchairWizard said:
If they send the phone back to you, the part that was replaced on mine is "90AZ00A1-M02610". Dunno if you can get that part yourself and have it repaired by a third party, but other than that I wouldn't know what to do in your situation.
Click to expand...
Click to collapse
...This is the Hardware model# of the whole device, not just a part inside , buy a new phone and you have this yourself !
At least for those in Canada, here a short review for my "advanced replacement" experience:
I used the Chat on their website to get a RMA#, then got a confirmation email with a sort of howto. They mentioned to use Fedex or UPS to send the defective device in and noted not to long to wait to do this otherwise the hold on my creditcard... you know! So i sent the package 3 days later with UPS, cost me a bit over CA$60 with insurance and tracking.
Just the other day i got email from Purolator (a Canada only parcel service) to print a return sticker. No one from ASUS mentioned this to me - $60 wasted
The replacement phone came also with Purolator, ASUS emailed me a tracking# but NOT wich carrier they used. Cost me a few hours and a couple phone calls to find out and re-route the package to my workplace.
ASUS did not use a original case, just a folded carton as they stated the replacement would be a new device. In case i decide to sell the phone i don't have original carton
Start to install all my usual App's etc. found that the phone does not receive any GPS signals, so it seems i changed a not usable screen into a not working GPS
For me, this was my last ASUS for a very long time!

Finally got my Advanced RMA going. can't wait to get a working phone, as soon as I do. Going root & unlock bootloader and install CM 12.1 I'm DONE with ASUS's bloatware ! ~ T

I am having the same problem. I have gotten my screen to work, but it still glitches. Is the only solution to send it in?

jeisenhart34 said:
I am having the same problem. I have gotten my screen to work, but it still glitches. Is the only solution to send it in?
Click to expand...
Click to collapse
I think so, I tried to fix it, flash with 2.20.40.97 Four times now, the problem is still there, rooted, unlocked bootloader, and installed CM 12.1 thinking it would get rid of the problem, it didn't. I think the problem is in the boot partition now. I also flashed the splash screen, and the boot animation. the problem is still there, EVEN after returning this phone back to stock to RMA it. the problem is still there.

Rattraps123 said:
I think so, I tried to fix it, flash with 2.20.40.97 Four times now, the problem is still there, rooted, unlocked bootloader, and installed CM 12.1 thinking it would get rid of the problem, it didn't. I think the problem is in the boot partition now. I also flashed the splash screen, and the boot animation. the problem is still there, EVEN after returning this phone back to stock to RMA it. the problem is still there.
Click to expand...
Click to collapse
I contacted Asus and I have to send my phone in. If you haven't dropped your phone, Asus will overnight you a new one for $25. I dropped my phone so they will repair it free of charge if the damage from the drop isn't what caused the issue. Otherwise I'm going to have to pay.