Database Develop

Sliding won't work anymore

Hey guys,
I could need a bit of help! It's now the third time I'm having this problem, don't ask me why. I've got the feeling that I read the whole forum here, but didn't find anything similiar.
The 1st time I didn't change anything (ok, rooted it, but nothing else)
The 2nd time I overclocked it slightly (~850-900 MHz)
Now I'm using MIUI.
But back to the problem:
I'm unable to use the keyboard, every time I'm sliding open the keyboard (even when it's turned off), it "crashes". The screen stops working or it freezes, the only way to turn it off is taking out the battery.
However, the bigger problem comes now: I'm barely able to restart it. It tries booting, but is restarting all the time or the screen is just turning on (in some angles you see that it is turned on but it's black). After many retries, it starts working, sometimes the bootloop is running 15min or i have to manually restart it 10 times or more. The strange thing is that the keyboard works fine, nevertheless I have to choose between using it opened (taking it with me becomes difficult ) or closed...
...the main problem now is flashing a new Rom, I'm currently trying it through the android sdk and adb, but using the power-button + x is easier
I don't think that I can solve the problem, I sent the device two times back (warranty till may 2012), but maybe someone here knows a bit more. My guess is that one of the sensors is broken, or some parts of the display that should manage the sliding process...
Anyway, thanks for your attention!
Web

If you already have Rom Manager, just click Reboot into Recovery..

inches0 said:
If you already have Rom Manager, just click Reboot into Recovery..
Click to expand...
Click to collapse
Tried to use one a time ago, but it wasn't working right....
However, now I'm not even able to boot it, the screen just flashes and turns off itself before trying to restart a few moments later....guess I lost my Milestone

Sbf back to stock?

taptaptouch said:
Sbf back to stock?
Click to expand...
Click to collapse
the computer isn't finding it anymore...I'll back up the data and try use my warranty... I hope that they don't complain about MIUI...
But I'm still not getting the point, why my mobile had these issues three times, although they "repaired" it twice...and nobody else is having the same problem

[Q] Bootloop, software or hardware caused?

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.

[Q] Hard briked S3 mini out of nowhere

I have the feeling I'm going to get repetitive here guys, but I've been reading the troubleshooting threads for over an hour and couldn't find an answer to help me.
Last saturday I was to lazy to move from the couch, so I watched as my S3 Mini ran out of battery. I got the "phone is turning off" screen as usual. Later I went to bed, but as I needed my alarm to go off in the morning I tried turning it on again, and nothing* happened. Plugged it on the wall, nothing*. Replaced the battery, nothing*. Gave it a good half hour plugged, and as you can guess, nothing*.
* when I say nothing, I mean it won't light up, won't vibrate, won't wink for me, won't load any kind of error, it's actually just like if you were trying to turn on a phone without any battery connected, no grasp of life comes from its poor soul.
The only moment I could see some action on the device is when I tried connecting it on the PC a few hours ago, as it installed drivers to Windows. Right after installing the drivers however, it won't show in the file explorer. I've tried to detect it with a few development tools such as ORT and Odin and there was no sucess either. Download or Recover mode will not work as well.
One thing I think worth mentioning, is that ever since I rooted it a couple of years ago, whenever I tried to recharge it while it was off, the standard "green charging battery" would never appear. What would appear on the screen was a freezed loading icon (the one that keeps roling again and again, but frozen). This particular issue never came off, even reseting it or installing new ROMs.
I always used Maclaw's, some of the latest 4.x, because I tought the 5.x was to heavy for the s3 minis.
I've read some about USB JIGs and stuff, but what makes me very curious is what the heck?! The phone was working just fine, the battery runs out and I have a brick? Is this possible? Can anyone tell me any work around?
I apologize for possible grammar mistakes.

ScrewedImei said:
I have the feeling I'm going to get repetitive here guys, but I've been reading the troubleshooting threads for over an hour and couldn't find an answer to help me.
Last saturday I was to lazy to move from the couch, so I watched as my S3 Mini ran out of battery. I got the "phone is turning off" screen as usual. Later I went to bed, but as I needed my alarm to go off in the morning I tried turning it on again, and nothing* happened. Plugged it on the wall, nothing*. Replaced the battery, nothing*. Gave it a good half hour plugged, and as you can guess, nothing*.
* when I say nothing, I mean it won't light up, won't vibrate, won't wink for me, won't load any kind of error, it's actually just like if you were trying to turn on a phone without any battery connected, no grasp of life comes from its poor soul.
The only moment I could see some action on the device is when I tried connecting it on the PC a few hours ago, as it installed drivers to Windows. Right after installing the drivers however, it won't show in the file explorer. I've tried to detect it with a few development tools such as ORT and Odin and there was no sucess either. Download or Recover mode will not work as well.
One thing I think worth mentioning, is that ever since I rooted it a couple of years ago, whenever I tried to recharge it while it was off, the standard "green charging battery" would never appear. What would appear on the screen was a freezed loading icon (the one that keeps roling again and again, but frozen). This particular issue never came off, even reseting it or installing new ROMs.
I always used Maclaw's, some of the latest 4.x, because I tought the 5.x was to heavy for the s3 minis.
I've read some about USB JIGs and stuff, but what makes me very curious is what the heck?! The phone was working just fine, the battery runs out and I have a brick? Is this possible? Can anyone tell me any work around?
I apologize for possible grammar mistakes.
Click to expand...
Click to collapse
try to plug in the phone into charger & leave it there like 20 mins or more. battery loads then.
then try access samsung download mode, if you cant the phone is probably useless (brick for ever) because itslike mthe last standing thing.
& sorry i say that but thats typically samsung behaviuor. there allways this kind of threads in the samsung forums of xda... other manufacturer can mostly be restored or atleast you know what make it dead.

Exactly the same problems happening to me.
This is my thread:
http://forum.xda-developers.com/galaxy-s3-mini/help/sgs3-mini-dead-t3085031
Can you try to follow what appears on this link? (I can't by now because my PC is broken)
I think won't do nothing because you won't be able to access to the recovery mode on android, as me, but to try...
http://forum.xda-developers.com/showthread.php?t=1840030

bejunk said:
try to plug in the phone into charger & leave it there like 20 mins or more. battery loads then.
then try access samsung download mode, if you cant the phone is probably useless (brick for ever) because itslike mthe last standing thing.
& sorry i say that but thats typically samsung behaviuor. there allways this kind of threads in the samsung forums of xda... other manufacturer can mostly be restored or atleast you know what make it dead.
Click to expand...
Click to collapse
Hi there,
Thank you for your interest but I have passed this point already. Tried a brand new battery I had laying down in the drawer (which was fully charged with an universal charger) and there is no answer to any attempt of turning it on. Via recovery, download or normal boot.
CrashOverride93 said:
Exactly the same problems happening to me.
This is my thread:
http://forum.xda-developers.com/galaxy-s3-mini/help/sgs3-mini-dead-t3085031
Can you try to follow what appears on this link? (I can't by now because my PC is broken)
I think won't do nothing because you won't be able to access to the recovery mode on android, as me, but to try...
http://forum.xda-developers.com/showthread.php?t=1840030
Click to expand...
Click to collapse
Hello there,
I'm sorry to hear I'm not the only one affected by this bug (lets call it a bug). This shows there is a lack of concern from Samsung on dealing with this issues, and thus we see that old programmed obsolescence.
I will try that later on the weekend, and I come back here with an report.
Cheers

ScrewedImei said:
Hi there,
Thank you for your interest but I have passed this point already. Tried a brand new battery I had laying down in the drawer (which was fully charged with an universal charger) and there is no answer to any attempt of turning it on. Via recovery, download or normal boot.
Hello there,
I'm sorry to hear I'm not the only one affected by this bug (lets call it a bug). This shows there is a lack of concern from Samsung on dealing with this issues, and thus we see that old programmed obsolescence.
I will try that later on the weekend, and I come back here with an report.
Cheers
Click to expand...
Click to collapse
this guide useless for you. how u want flash things with odin if u cant enter download mode at all??
im really sorry for you that this phone is dead. just can give you 1 advice, dont buy samsung in future.

I have been repaired my phone successfully!!!
I just needed to change two capacitors on its motherboard, and that's it.
Here the video where I have found the info and how to do that. It's in Spanish but easy to understand for you I think. But if you need some help, send me a PM.

can you take a picture from the location of the 2 capasitors and the types of it

Hi everyone.
I have some news. It took me a while but I followed CrashOverride93's advice on that video. It actually solved one issue, as I now can turn it on, but now I have a second problem, I'm stuck on a boot loop, with acess to Download mode ONLY. No recovery.
Considering where my issue started, and where I am now, I have tried the following:
- Flashed via Odin stock ROM, kernel;
- flashed Wipe;
- flashed PARAM;
- three button combo.
So far I couldn't get it pass the boot loop. Any thoughts?

Urgent help needed: Phone reboots continuosly after setup

I am currently experiencing continuous reboot on my Single Sim Z3+ phone on .253 firmware. It used to be ok but about a week ago I started experiencing this problem as soon as I reboot the phone after setting it up from a fresh install with full wipe. It seems to work normal on earlier builds like 28.0.A.8.266 so only happens on 32.1.A.1.185; 32.2.A.0.224 - .253. I repeat, I have done fresh install with Full wipe several times but problem still exists. Urgent help needed.
Thanks

yawo76 said:
I am currently experiencing continuous reboot on my Single Sim Z3+ phone on .253 firmware. It used to be ok but about a week ago I started experiencing this problem as soon as I reboot the phone after setting it up from a fresh install with full wipe. It seems to work normal on earlier builds like 28.0.A.8.266 so only happens on 32.1.A.1.185; 32.2.A.0.224 - .253. I repeat, I have done fresh install with Full wipe several times but problem still exists. Urgent help needed.
Thanks
Click to expand...
Click to collapse
Hello yawo76,
I have the same device, and I had the same problem, what I did is the next:
With flashtool, download the stock firmware via xperia firm on the same tool (I have successful with E6553_32.2.A.0.253_1295-0156_R6C), after that, in the options, be sure that the MiscTA Exclude options are check, that's the clue. After that complete the setup menu, and try again.
Regards! and sorry for my horrible english.

I do have the same issue. I have Z3+ Dual. Random reboot and/or sleep of death.
What I saw from other posts about hardware issue (no other proof), is about the NFC antenna. But I tried and nothing changed.
I have my phone fresh ROM .253 MM installed and click all the way to home screen and let it sit. Well, nothing happened for many hours 5-6hr. Almost every other hardware functions off. However, once I turned on WIFI, something happened. Blank screen and 3 red LED blinks to reboot. A few moments later at home screen.
Soon, sleep of death (SOD). It is like, when the phone is standby (black screen sleep), when I pushed power button to wake the phone, it won't turn screen on. Like it's hang or something. No choice but to hard reset so that I could turn back on.
Then, I played with WIFI setting and saw a "Keep Wifi On during Sleep". I switched to "never" and tried let it sit again. I found out problem was gone for 10 hours (this is best record now, usually 2-3 hours, reboot happened).
I am still monitoring.
Wish you can try and confirm this.

I ran many tests about this issue. Found out it was the material of board or CPU or power which was not made strong enough. I tried tuning the CPU a little (just like PC of CPU tuning). So that it will not cause SOD, random reboot issue. It was also adjusted such that the battery saves much and prolong the usage of the phone.
With sitting of standby the phone is not running warm. Messages or phone calls will not delay in receiving. Plus, it draws about 2% of juice during standby of 6-8 hours.
Worth the try.

phone turns off by itself

Hi, this happend already to me few times so I decided to put it on here.
Sometimes when I pick up my phone and try to unlock it nothing happens, fingerprint and button all the same it looks like it completely Off. Then i have to press few times a button to actually start it and it's booting. There is huge battery loss after it boot up. See image.
I am in Stock 4.0.2 no root just few standard apps installed. Nothing fancy. This happend already few times to me. I left the phone locked and when I want to unlock its dead. Also it is behaving weirdly, when I turn it off manually I just need to press longer a button and it's turning on, but here I need to press it few times to work.
Does it happen to anyone else?

terragady said:
Hi, this happend already to me few times so I decided to put it on here.
Sometimes when I pick up my phone and try to unlock it nothing happens, fingerprint and button all the same it looks like it completely Off. Then i have to press few times a button to actually start it and it's booting. There is huge battery loss after it boot up. See image.
I am in Stock 4.0.2 no root just few standard apps installed. Nothing fancy. This happend already few times to me. I left the phone locked and when I want to unlock its dead. Also it is behaving weirdly, when I turn it off manually I just need to press longer a button and it's turning on, but here I need to press it few times to work.
Does it happen to anyone else?
Click to expand...
Click to collapse
Honestly, there's not enough information to understand exactly why it's happening. You need to get a logcat in the time before the reboot; unfortunately, logcats get erased during a reboot so it might be a little tricky getting it if the reboot is seemingly random. Someone had posted this as a possible way of getting the log:
"Retrieving the logs is tricky, since the log cache gets erased on reboot. If the phone reboots even while sitting on a charger, try running adb logcat continuously (you will need Android SDK and USB drivers installed and configured on your PC.) When the phone reboots, look at the last several pages in the command prompt window for any errors or abnormalities."
Click to expand...
Click to collapse
Otherwise, it's hard for anyone to help. I'm not much help in actually figuring out the issue, but I know if you can get the log, someone else probably can help.
For more information on logcats: Logcat Tutorial

Yeah I was trying to connect it to PC but nothing, so it is turned off. I will try next time to run command when turning on, maybe there will be something but I do not see it working before it gets erased. I was hoping that anyone else is having this problem so it might be rom related. It is completely random so you can;t guess when it happens.
I had it only few times so it's not super annoying but still it is not normal behavior. In addition it is weird that battery went from 55% to 33%, just phone reboot will not drain that much... I hope there is nothing wrong with the phone itself.

terragady said:
Yeah I was trying to connect it to PC but nothing, so it is turned off. I will try next time to run command when turning on, maybe there will be something but I do not see it working before it gets erased. I was hoping that anyone else is having this problem so it might be rom related. It is completely random so you can;t guess when it happens.
I had it only few times so it's not super annoying but still it is not normal behavior. In addition it is weird that battery went from 55% to 33%, just phone reboot will not drain that much... I hope there is nothing wrong with the phone itself.
Click to expand...
Click to collapse
Check in advanced to see if schedule off is on

Nope it's off

Happened to me to on 4.0.2. Rebooted twice a day.
Solution to me was Qualcomm flash back to stock 3.5.1 and uodate from internal to 3.5.4. OTA 4.0.2.
The theard "how to unbrick".
Not one reboot until now in days.

I think I found a culprit responsible for it. It is Hill Climb 2 game which doesn't close properly sometimes and I think it causes some kind of crash in the system. Is it possible?

terragady said:
I think I found a culprit responsible for it. It is Hill Climb 2 game which doesn't close properly sometimes and I think it causes some kind of crash in the system. Is it possible?
Click to expand...
Click to collapse
It's possible. Not necessarily the reason, but it might be. Either uninstall the app or freeze it using Titanium. Greenify might also work, but that allows the app to start itself up and potentially continue the issue. See if that stops the crashes for a couple of days.

The problem is that it doesn't happen often and only when I quit the game and lock the phone immediately after that. I am not sure if that's a reason though, just guessing because it happens after this last time. I will uninstall this game anyway, it's just time eater