Related
hi all,
i'm experiencing a weird problem. i've been flashing lots of roms (cm10.x, omni, stock-based ones), and suddenly my phone's camera started not working. however, if i turn the device off completely, start charging it, and turn it back on, the camera is fine until a reboot (even after unplugging from the charger). removing the sim card and rebooting also helps sometimes.
i've tried:
- factory reset
- flashing different roms
- revering to stock
- some forum post on the 'net about deleting the 'dcim' folder on both sd cards (wtf lol)
- disassembling the phone (my warranty is void anyways) and checking the main, battery and the camera's ribbon cable connection (they're fine)
i'm pretty sure it's not a hardware problem, but i can't be certain, of course.
anyone had this issue before? any suggestions? something else i forgot and should try?
thanks,
bamdad
update: somehow, after installing the new 4.3 firmware, it was alright for a while, then it started happening again. since my back cover was in quite a rough shape, i ordered a new one; after putting it on, the camera started working normally.
now i really don't get this, because i've taken the device apart dozens of times. it might have something to do with those little copper contacts being corroded on the old back cover, someone correct me if i'm wrong. the strange thing is that the camera seemed to work fine with the back cover off.
well, it's fixed now, but for how long? :/
this is just insane. yesterday i tried omnirom again, played around with it, then restored my backup of the official .199 firmware, and some time later tried to take a photo - boom, camera and flash hasn't worked since. now that i think of it, i distinctly remember trying a previous build of omnirom before the last time my phone went bonkers.
now i'm not hinting at that it's omnirom's fault directly, since apparently lots of people are using it without similar issues, and at the end of the day custom roms aren't responsible for damaging a device, but it's strange.
if someone has any pointers as to what should i do, i'd be really appreciative. i'm going to try flashing from an original ftf file, maybe this has to do with some firmware stuff that's reeeally over my head. fingers crossed..
the funny thing is that it works great after restoring my backup of omni. bloody hell. : ) i mean what am i missing here? : )
okay, so i managed to (maybe) fix it. the trick was to *not* use omnirom's cwm recovery to restore the stock rom, rather flash the stock kernel with philz touch, *then* restore the backup. man.. hope this lasts.
started again this morning on dark lord's blackxt (stock .199-based), torch went too. rebooting and the other tricks didn't do diddly-squat. however, a trip to recovery and back fixed it. i did install doomkernel, but it's probably not the one that helped, because i've been using that last time the problem started.
btw, i know i'm spamming this topic all alone, but maybe someday this will prove useful to, or someone who knows what's going on will laugh and tell me to idk reformat the whole device or flash some obscure firmware file or something.
Hello, Its been a long time since I don't ask anything on the forum, but in this occasion I haven't found any solution to what's happening to my Xperia Z, I'm gonna do my best to present the issue.
A couple of days ago I updated my Xperia (unlocked bootloader) from Existenz 1.5.5 to the latest 3.0 and the phone was completely fine for 2 days until it started shutting down by itself constantly and with no apparent reason, so I started to get worried, the first thing I did was try and reinstall the ROM thinking that I had some something incorrectly, I has no luck with that, on the contrary the phone died on the middle of the installation and it got bricked. My next step was to try do do everything from scratch, flashing the stock rom 10.5.1.A.0.283 to root it, install recovery and try flashing the Existenz after. I managed to do everything with lots of unwanted shuts downs in the middle but I managed. Unfortunately the phone kept on having the same problem so my last option was to try and use the Sony bridge on my mac to try and make a factory reset but it didn't let me because it detected the unlocked bootloader so I relocked it with flashtool, after that I tried again and it worked, it installed the official stock rom .101 and guess what..... same issue again, when I try to turn the phone on it shows the sony logo and turns off, if I try to turn it on connected to the AC it turns on but if I start playing with the menus and options it disconnects again, ofcourse if I turn it on connected and once it's on I disconnect it it shuts down almost instantly, At first I though the problem could be software, then hardware so I tried to check the battery status in the service app and it said good battery health so now I'm completely lost.., I've found this: http://forum.xda-developers.com/xperia-z/help/hardware-fix-xperia-z-charging-booting-t2760911 but I don't know if thats my case. I was gonna go to a sony store and ask them what could be the problem, but now I'm living in Brazil and it'd take lots of time and money to get ir fixed here.
I really need help here, sorry if I posted on an incorrect place.
I just found a video of someone with the exact same problem, in case in helps: https://www.youtube.com/watch?v=zkvLchJ_0oU
UPDATE: I rooted it, install recovery and once im in recovery it doesn't turn off by itself what tells me that may not be a hardware problem, at least not battery related, all this just makes me feel more confused!!
UPDATE 2: I rebooted the phone to load the recovery again and the battery indication went from 89% 2 minutes ago to 11% this second time, maybe it's hardware after all..
Battery.....
TapaTalked from my Xperia™ Z (C660²) running Ultimate PureXZ Ultra!
I seriously don't think is the battery, I think it's something related to the energy but I'm not sure what. As I said before the battery went from 89% to 11% quite fast but when it was at 1% it stayed there for hours, if it was the battery wouldn't it had turned off? after it finally turned off I left it charging for about 12 hr and today morning I try to turn it on without it being connected and no luck, it kept shutting down after the Sony logo. Sometimes when I turn it on with the cable connected it loads the OS and I unlock the lockscreen, diconnect the cable and extraneously it stays on just with the battery power, I manage to put the ScreenOff timeout to 30 mins and it stays on all the time, as long as I don't do certain things like opening the camera, phone or sometimes it just randomly turns off from anywhere. I know it's not the rom because I've tried 4 different ones including the official installed by Sony Bridge....
If the issue is software related what could it be?? the bootloader? the bios power management? battery stats? maybe restoring TA backup(because I just relocked the bootloader using the option o flashtool, not flashing the TA backup)?
I'm concerned about buying a battery, installing it and seeing no change as I've read happened to some guys with the same problem.
I really like my phone but after this I'm not so sure i'll buy another Xperia because this has happened to so many people and apparently there's no solution, my phone is out of warranty and I life in a foreign country (Brazil) so you guys are all I have...
Same Problem Here ... Impossible to flash either from fastboot or from CWM or TWRP
Hi, I am having exactly the same problem. I was trying to revert to stock kernel from CM10.2 and was following one of the many guides here on XDA. The phone was not passing the «SONY» Logo, and immediately after such logo it simply went completely black and the phone is off. After two days of trying several things, including Fastboot of Stock ROM, fastboot of different boot.img files including Doomlord, using Sony Bridge for Mac, all of which did not solve the issue, the problem now is that when I try to flash any ROM, the flashing operation begins and then after approx 15 seconds the phone goes black and switches off. The battery is at 82%, so I am quite sure it is not a battery problem.
I am more and more convinced that the internal filesystem (or simply RAM) needs to be formatted at low level from scratch.
The only problem is that I do not know how to do it: how to do LOW LEVEL Formatting of RAM? Any instructions out there?
Any other suggestion?
Thanks
gcecchini said:
Hi, I am having exactly the same problem. I was trying to revert to stock kernel from CM10.2 and was following one of the many guides here on XDA. The phone was not passing the «SONY» Logo, and immediately after such logo it simply went completely black and the phone is off. After two days of trying several things, including Fastboot of Stock ROM, fastboot of different boot.img files including Doomlord, using Sony Bridge for Mac, all of which did not solve the issue, the problem now is that when I try to flash any ROM, the flashing operation begins and then after approx 15 seconds the phone goes black and switches off. The battery is at 82%, so I am quite sure it is not a battery problem.
I am more and more convinced that the internal filesystem (or simply RAM) needs to be formatted at low level from scratch.
The only problem is that I do not know how to do it: how to do LOW LEVEL Formatting of RAM? Any instructions out there?
Any other suggestion?
Thanks
Click to expand...
Click to collapse
It seems like there's no solution and I don't think my battery is broken so I won't try the Hardware Fix since I don't wanna break my phone more than it already is, tomorrow I'll try to go the a Sony service store and see what they think the problem is, since I unlocked my bootloader and relocked after I think they will be able to see this, I think it ain't gonna be a problem because my warranty was void long time ago, and it's 1 year anyhow.... I hope they recognize it's a sony's fault issue and they decide to fix it with no cost, very unlikely but hoping is free gcecchini, i'll keep you updated, also if you find a solution let me know.
Hi Ringox!!! I'm having exact problem as your's.. This all started when I upgraded to 4.4.4 . First it was giving some weird problem like when opening camera , the phone shuts down. Then a time came the device was not charging.. The device boots up when connected to wall charger. But as soon as charger is removed the phone shut's down. Without connecting the charger when I tried to power on, it shows sony logo for 1 second the shut's down. I tried installing every stock rom , custom rom, kernel etc and it didn't solve the problem. I also bought new battery but same problem. I don't think it's software or hardware or battery problem but may be bootloader is corrupted. May be when we flash bootloader ( as in samsung) we may solve this problem. But I cannot find any tutorial an instruction to flash bootloader.
Also from quickstyler thread I can confirm that I have same problem as him, the sony mobile battey test app shows same error battery temperature -30 C . But his hardware fix didn't work either.
By searching for the problem on youtube, xda, google and other sources I can confirm 1000s of people is getting this problem ..
Please developer and member , help us provide solutions and tips what we can do next...
I have news, after one month waiting for Sony to repair my phone they've finally said it can't be fixed and they said the problem is the motherboard which is approximately 130 dollars plus installation, so I decided to park my Xperia and buy a SGS4. Something interesting that happened is that now the phone starts and sounds, just with a black screen all the time with the backlight ON, maybe they fixed something and broke something else, I don't know. If anyone knows a solution to this rather than changing the motherboard I'd appreciate the answer. I wanna fix it to give it to my mother, but I won't be buying any other Sony smartphone ever again, their service is a disgrace and I couldn't be more unsatisfied with them.
I EDITED the whole post to better explain the issue.
Okey, first of all I already try to use the search function with no luck (I found a similar case but he flashed with adb to solve it and that would void my warranty).
Today I received a moto x (it should be new) and I updated it to 4.4.4
The phone freeze itself whenever he wants and the only way to keep using it is to lock and unlock it.
By freez I mean I can't control it, I will try to explain:
I loose control over the touch, if I'm in a game that use the sensors (like riptide GP) I sitll can play it moving the phone with no glitch in the game, but I can't use the turbo or breaks, since I need to touch the screen. When this happens, sometimes the phone goes crazy and start touching everything, it makes the notification bar go down, make his way to desktop, go to settings and change everything (all of this with the phone factory reseted 30 mins ago, just installed es file explorer and installed one game, didn't updated anything).
This also hapened in stock 4.2, I suposed that an update would solve the problem, I have the 5.1 OTA available but I'm afraid to make the update and still have the issue.
I already made a full wipe.
Update:
It seems that this happens mostly when the phone is under heavy use of some app, mostly when it heats a little.
I found no problem in safe mode, but there is no heavy use app comming with the phone, so I can't test much further.
Thanks for your answers!
I would try a factory reset, you don't need an unlocked bootloader to do that. If that does not fix the issue, then your Moto X has a hardware problem.
I already did a factory reset, and wiped cache also, but the problem is the same, and it happens much frecuently when in games =S
I'm very sad that this may got no solution.
I may be the lucky one whose screen didn't start to peel off yet,but f*ck me this phone is starting to really piss me off.
Everything worked well after I have gone to SLiMM 1.4(way before) and as I was upgrading SLiMM versions it was slower and slower to the point where the phone is unusable!
So I thought,let's try to do a good old phone reset,reflash the ROM and go from the beginning.
I restored the apps,rebooted the phone and it was STILL painfully slow,so I resetted it again but this time restoring half the apps and half the Xposed modules I have used before.
It improved a tiny bit but nothing significant.
So I thought it is finally time to unlock the bootloader and see if there is any good AOSP ROMs,as the first one I tried was AOSP 7.1.1.
Fastest ROM I have used by far,the biggest problem,my device gets very hot from loading Messenger and jumping back to Snapchat and in AOSP 7.1.1 it would stop charging the phone because of the high temperature and this was quite a big issue.
So after using it for 2 weeks,I couldn't handle the charging thing anymore,so next best thing was Sony Concept ROM.
I install the ftf,goes well,install the recovery,install DRM fix,SuperSU and Xposed.
After rebooting I notice that Xposed didn't install properly so I jump back and flash it again,and the problem now was it would get like VERY VERY hot(you couldn't touch it) when it came to the "Android is starting" screen and of course the device started rebooting itself because it was way too hot.
So what I did was put the phone on a bag of f*cking ice to keep it cool,and it FINALLY passed that screen,only to find out a second later it returned to the bootanimation and gone into a bootloop.
Now I reflashed the ftf,but before even booting the ROM for the first time I flashed recovery,Xposed,SuperSU and the DRM fix.
It booted up fine,so I started to restore my apps and everything went well until I rebooted my device to find out it doesn't want to log in to Snapchat,the app I use very often.
So I flashed Magisk,systemless Xposed just that I can hide the root from it and disable Xposed just to log in to my account.
Even that didn't work so fine I'll try it next day.
So I decide to reboot the phone quickly and it has gone into the "Android is starting" screen and shut off in the half of the process. F*cking pissed.
I cool the phone down,boot it up,wait for it to finish and when it was close to finishing it has gone into a bootloop,and wiping cache doesn't solve it.
It is currently in a bootloop as we speak.
I really do like the phone but why is it behaving so badly? I do not know if someone had a similar experience as I did.
If anyone could give me a suggestion to make my phone stable and functional,please write a post since I need my phone to work.
Flash original android rom/kernel to the device to make device fully stock. Once it is back to stock, if problems still continue i recomend sell device and buy new one.. On my xperia, display stopped working out of blue, replaced it and my camera became blurry and vibration motor stopped working... Opened it again, fixed vibration motor, now it waits another opening to replace battery and camera lens... Disaster, but hey, device is great in hw department..
Strmy said:
Flash original android rom/kernel to the device to make device fully stock. Once it is back to stock, if problems still continue i recomend sell device and buy new one.. On my xperia, display stopped working out of blue, replaced it and my camera became blurry and vibration motor stopped working... Opened it again, fixed vibration motor, now it waits another opening to replace battery and camera lens... Disaster, but hey, device is great in hw department..
Click to expand...
Click to collapse
I forgot to mention,every time I said reset the phone I actually did flash the stock ftf and set it up all on my own,but whatever.
I guess it is just bad luck.
Dinkec27 said:
I forgot to mention,every time I said reset the phone I actually did flash the stock ftf and set it up all on my own,but whatever.
I guess it is just bad luck.
Click to expand...
Click to collapse
Jebiga mi Hrvati imamo lose srece sa mobitelima hahah
More luck next time
Dinkec27 said:
I forgot to mention,every time I said reset the phone I actually did flash the stock ftf and set it up all on my own,but whatever.
I guess it is just bad luck.
Click to expand...
Click to collapse
internal memory is failing.
bookworth said:
internal memory is failing.
Click to expand...
Click to collapse
Awesome
bookworth said:
internal memory is failing.
Click to expand...
Click to collapse
Dinkec27 said:
Awesome
Click to expand...
Click to collapse
Exactly, I suggest the same issue. I had exactly the same problem on my Xperia T, it became slower, slower, incredibly slow after three years so I couldn't even flash anything using flashtool - it was showing many errors. Even after factory resetting the phone, it was booting and setting up for like... two hours or more, becoming VERY hot but it finally booted, still was very slow.
Two solutions - warranty or selling it.
romcio47 said:
Exactly, I suggest the same issue. I had exactly the same problem on my Xperia T, it became slower, slower, incredibly slow after three years so I couldn't even flash anything using flashtool - it was showing many errors. Even after factory resetting the phone, it was booting and setting up for like... two hours or more, becoming VERY hot but it finally booted, still was very slow.
Two solutions - warranty or selling it.
Click to expand...
Click to collapse
It just doesn't make sense to me that the internal memory could be failing just under a year...
I cannot go for warranty since I voided it with unlocking the bootloader,and selling it is not an option because I am on a contract currently and I can only sell it once it expires and then get a new phone to renew my contract.
If it is internal memory,it is a second tine in a row,before I had the Galaxy S3 and it had the same symptoms,it looks like I'm prone to internal memory failures lol
Is there a way I can test the internal memory?
Hi.
Today appeared some problems with my A2. When I woke up and unlocked phone it turned off. Yesterday everything worked perfectly fine. I tried like 20 times, everytime the same scenario- turns on, but when I type PIN, home screen is loading, and phone goes down. It may look like bootloop, but its not typical, cuz it goes farther than just booting screen. So I tried to fix, wiped phone, set lang. to Polish, and it dumps again, but I've read somewhere, that it might be language issue, so I wiped it once more and set English. It seemed to be working, but then I unplugged it from my PC (charging only) and it turned off immediately. Worth mentioning is fact, that battery is 92%. What may cause this? Is this some soft problem? Or more like battery issue?
Update: Phone works unplugged, but only on lock screen. Turns down when I unlock.
Ashu14 said:
Hi.
Today appeared some problems with my A2. When I woke up and unlocked phone it turned off. Yesterday everything worked perfectly fine. I tried like 20 times, everytime the same scenario- turns on, but when I type PIN, home screen is loading, and phone goes down. It may look like bootloop, but its not typical, cuz it goes farther than just booting screen. So I tried to fix, wiped phone, set lang. to Polish, and it dumps again, but I've read somewhere, that it might be language issue, so I wiped it once more and set English. It seemed to be working, but then I unplugged it from my PC (charging only) and it turned off immediately. Worth mentioning is fact, that battery is 92%. What may cause this? Is this some soft problem? Or more like battery issue?
Update: Phone works unplugged, but only on lock screen. Turns down when I unlock.
hi i have the same problem with my mi a2. i can turn it on when is on charger but when i want to unlock the screen and to move something on screen is turning off. when i unplug the charger turning off too. do you found solution on your problem ?
Click to expand...
Click to collapse
Hello, I have the same problem. I now have to carry an external battery with me, because plugging it in is the only thing that wakes up my phone. If I don't have a charger, then I have to hold power for 30; seconds to force reset. It's really annoying, causing me to miss calls and alarms. Anyone know of any fixes? Thanks
Hey,
I am facing the exact same problem. Though I had an additional problem. My phone didn't charge when I plugged it in until I restarted it. Factory resedidn't help either.
In both your cases the problem is your wifi even if you dont understand it ...
if you can unlock your phone quickly and toggle off wifi the phone wont reboot or loop
your persist partition is damaged from changing between pie and android 10 ..
look around for a flashable zip to repair your persist ( it does it exist )
or take the long root and use miflash to flash persist by modifying certain files in stock fastboot rom folder
but next time explain your problem better
--- what did you do -- change version ( update or downgrade ) -- did you root -- do you have twrp -- what version of android-- did you return to stock from custom or vice versa --- etc etc etc
KevMetal said:
In both your cases the problem is your wifi even if you dont understand it ...
if you can unlock your phone quickly and toggle off wifi the phone wont reboot or loop
your persist partition is damaged from changing between pie and android 10 ..
look around for a flashable zip to repair your persist ( it does it exist )
or take the long root and use miflash to flash persist by modifying certain files in stock fastboot rom folder
but next time explain your problem better
--- what did you do -- change version ( update or downgrade ) -- did you root -- do you have twrp -- what version of android-- did you return to stock from custom or vice versa --- etc etc etc
Click to expand...
Click to collapse
tried with wifi toggle off but didn't work.
didn't tried persist partition
tried update software but still didn't work.
if there any hardware issue please let me know.