I updated my Z3C to Concept Marshmallow. But now i cannot revert to Lollipop. Flashing goes well, but phone is not usable, it turns on, and it comes to startup screen where you can connect to wifi but it crashes after 1-2min and then it goes into bootloop.
Related
I recently bought an Xperia Z and in my notification bar it said there was a new firmware available. I downloaded & installed the firmware but when my device was meant to boot up, it just crashed. I tried to turn it on again but it just kept crashing.
It comes up with the 'Sony' logo then the phone crashes. Sometimes it says 'Xperia' then crashes. Then lastly it has the purple wave and then crashes...
I flashed different firmwares. 4.3 JB, 4.4.2 KK, 4.4.4 KK. It still happened. Repairing with PCC didn't work either.
When I try to charge it from a wall adapter it turns on then switches to the charging screen. I hold the power button and the phone boots up normally. I can use the phone. I unplug it and it is fine for a few minutes. When I click an app or exit an app, sometimes the phone just shuts down and then the crashing happens again, unless I connect it to the charger.
Anyone had a similar problem and fixed it? I'm honestly stumped right now.
How do you stop this? Every time I turn my screen off and back on wifi comes on. I have disabled scanning and everything. Annoying!
Ok, this one is driving me a bit nuts trying to diagnose. My Touchpad has started to not turn on the screen occasionally. If I press power or home, the LED in the home button will light but the screen won't come on. If I wait and try again, perhaps in a minute or 10, it will sometimes turn back on. If it does turn back on, everything is still obviously running, and I am receiving notification sound or vibrations when appropriate. If I do a forced reset (Power/VolDown/Home) it'll reboot and the screen comes on. I'm not sure if this is a software issue or hardware, but I hadn't loaded a new ROM in quite some time (I'm running JCSullins 4.4.4). I had been running one from last year and as part of trying to diagnose this updated to his latest 1/13/15 version http://forum.xda-developers.com/showthread.php?t=2712680 but unfortunately that didn't seem to fix it.
Is it possible the backlight is failing? If so, is there a guide on how to repair it? The unit still does most of what I use a tablet for albeit a bit slow (and battery life is starting to suck). For everything else I use my phone.
thegof said:
Ok, this one is driving me a bit nuts trying to diagnose. My Touchpad has started to not turn on the screen occasionally. If I press power or home, the LED in the home button will light but the screen won't come on. If I wait and try again, perhaps in a minute or 10, it will sometimes turn back on. If it does turn back on, everything is still obviously running, and I am receiving notification sound or vibrations when appropriate. If I do a forced reset (Power/VolDown/Home) it'll reboot and the screen comes on. I'm not sure if this is a software issue or hardware, but I hadn't loaded a new ROM in quite some time (I'm running JCSullins 4.4.4). I had been running one from last year and as part of trying to diagnose this updated to his latest 1/13/15 version http://forum.xda-developers.com/showthread.php?t=2712680 but unfortunately that didn't seem to fix it.
Is it possible the backlight is failing? If so, is there a guide on how to repair it? The unit still does most of what I use a tablet for albeit a bit slow (and battery life is starting to suck). For everything else I use my phone.
Click to expand...
Click to collapse
Try completely deleting everything and go to lollipop and try that out.
Hello,
I'm having issues with my N6 every time i take a picture with the flash ON it shuts my phone off completely and I cannot turn the phone back unless i connect the phone back to any charger. I've tried a different picture app and I still have the same issue with the phone shutting off.
the phone currently has Marshmallow 6.0 .1
baseband version: MDM9625 104662.22.05.32R
Kernel Version: 3.10.40-G9a3e9ef
build number MMB29V
I've tried a factory reset on the phone and cannot fix this issue Please Help! any feedback is appreciated.
Seems like some type of short-circuit kinda thing. If you're in the US, send it to Moto. If not, then R.I.P flash.
Also, what happens when you drag down the status bar and turn the torch on? Does it power off then too?
A similar thing happened with my Xperia Z2. Whenever I'd play audio through the speakers, a crackle sound would come, the screen would turn off, red LED would turn on and phone would just die. It took about 10 minutes to get it powered on after that, it had to be connected to a charger to boot it up again, holding the power button wouldn't do anything.
Yeah, definitely sounds hardware related to me. I've never had anything like that happen.
Just created a pre-rooted rom using nordic combined 23.5.A.0.570_R11D and flashed (locked bootloader method). But I have a couple of issues. One is that a few seconds after the phone boots up the screen goes blank and the only way to get a display again is to press the power button for a few seconds which makes the power menu and the home button appear. I'm then able to press the home button. Only seems to happen after reboot. Anyone else seen this? I didn't for one of the UK based roms as I was worried about bloatware / customisations by Vodafone or Virgin Mobile.
The other issue is with the alarm clock - when the alarm goes off the screen comes on but only shows the background wallpaper. Only way to stop the alarm is to hold power button to get power menu and reboot. I've managed to get around this by removing the 20.1.A.0.12 clock app that came with the rom and installing a 20.0.A.0.28 version from KK.
Hmm after another reboot after repairing the alarm clock with the KitKat version the blank screen's not appearing anymore so perhaps related.
Its hardware problem your screen needs to be replaced same happened on my Z3 D6603 and hopefully the warranty saved me
I flashed 4.4.4 then 5.0.2 but same problem so its not a software issue.
I'm facing the same problem the screen goes blank .Nothing work to fix it .I've flashed the phone with lolipop it goes back normal but after few hours it goes blank again.Any idea guys ?
XMoDuLeSx said:
Its hardware problem your screen needs to be replaced same happened on my Z3 D6603 and hopefully the warranty saved me
I flashed 4.4.4 then 5.0.2 but same problem so its not a software issue.
Click to expand...
Click to collapse
That's what I thought originally as it had just come back from repair after having the screen fixed but I've not had a problem since removing the clock apk.
Hi all,
I'm having this same issue. I've just updated my D5803 to Marshmallow 6.0.1, build 23.5.A.0.570. Ever since the update, whenever I reboot the phone, it shows a black screen, and I have to press and hold the power button to get the home screen icon to show. And when my alarm goes off, just the wallpaper shows. If I press and hold the power button, I can get back to the home screen, but there is no way to turn the alarm off, I have to reboot the phone - not so fun when I just want to hit snooze!
I find it hard to believe no one else has had this issue before this build was officially released? I'm considering going back to the previous version
Edit: Well, this is interesting. If I take the phone out of its case the alarm works fine, put it back in the case, doesn't work. Take it out, it works. Put it in, doesn't work.
Edit 2: So, I reverted to Lollipop 5.1.1 and the alarm and phone worked perfectly. Updated again to Marshmallow - same problems, black screen and alarm not working while in the case, but alarm works when not in the case. Seems pretty definitive to me that it's a Marshmallow problem!
Bug is still present on .575 update. The strange ting is, on my phone when I disable the smart cover(Settings -> Sound & notification -> Notification access) it stays off, and then the phone is working fine. On my colleagues phone's it's switches itself back on after a call. I have no idea why this is not happening on my phone. Can't find any relevant setting differences.
YoMarK said:
Bug is still present on .575 update.
Click to expand...
Click to collapse
Wonderful