Database Info

[Q] Phone lags so much, so that I can't answer incoming calls

I've been using a rooted X10 since Wolf's V6 release (for 8 months I guess). I've unlocked my phone's bootloader.
I' ve tried Fera's 4 releases.
I have been using doom's v6 kernel.
About two months ago, phone started to lag MOSTLY WHEN data connection is on, or trying to make phone calls from phone book, or trying to answer incoming calls so that there have been times on which I couldn't answer them at all. BUT rom continued to run normal and smoothly on other conditions (when data connection is off for example) When I try playing any games, they run way too much laggy, even the games I know I played very smoothly before.
I decided to try another rom so I gave Dxperia a shot. The problem kept remaining. I changed kernel to Thkernel. Level of problem decreased but didn't vanish. Whenever I install a new rom, phone runs perfect but after a couple of days the problem rises again. I don't use too much apps. The most extreme condition for my phone is an incoming call when I listen to music with it and have a scrobbler app running in background. :/ pff. that's really depressing.
I don't know whether are they related to each other or not but, I noticed that this problem started after I unlocked my phone's bootloader. I always flash roms after I make a factory wipe.
I have been searching forums for other Roms and kernels but don't believe anything will change, because I already use most stable and popular ones.
Does this problem means that I have to turn to stock rom with PC Companion?
If I have to do so, after PC Companion turns my phone to factory image, will my phone will be in warranty conditions again (locked bootloader and unrooted) ?
What can be causing this problem?
I found another user in forums(an Italian guy if I'm correct) having this problem but after Fera gave him an advice about flashing Thkernel, he stopped informing about the problem. Any other users having the same problem?
Any help?

Its not due to unlocked boot loader...I think its problem with kernal..or limited ram and phone memory..
if you want to go back to the stock rom you can do it easily with pc companinion doesn't matter is rooted or boot loader unlocked.connect your phone in flash mode and reinstall your stock rom with sony update software...
Or you can try once this
Do a full wipe
Wipe data
wipe data cache
Goto advanced> wipe dalvic cache
Wipe battery status
And instal your rom and kernal once again....
Install cpu tuner or set cpu
Goto settings overclock during phone call..there is a option for that....all the best
Hit thanks if it helps....
Hackdroid...

Xoom does not charger! Please help

Hi All,
My Xoom had worked normally but since few days ago, it could not hold charging anymore.
Xoom will be on as long as it's connected to power charger (battery indicator always showed 82% but not increase or decrease) and will switch off immediately if i unplug the charger. By the way the Xoom date and time was also changed back to 1970s.
I have tried to delete the batterystats.bin and refreshed it. Also try to use "Battery calibration" software but not thing change.
Please help.
Thanks in advance.

A bit more information would be nice...
That's unfortunate.
It might be worth putting up some more information about your device, it might help other people help you...
It might be worth mentioning if your xoom is rooted. if it's bootloader is unlocked or not, the rom/kernel you are running, and of course, the model of your xoom.
Have you tried factory resetting the tablet? Back up your data if you do that..
If your device is rooted with an unlocked bootloader, you could also try flashing or re-flashing a rom. Perhaps something went wrong and a fresh start might be required. Switching to a different rom though might require a full data wipe. Luckily, if you were using TitaniumBackup, that wouldn't be too much of an issue.
I am not responsible for what happens because of my advice..
EDIT: If all else fails you could also go to http://developer.motorola.com/products/software/ and download the images for your xoom, and flash them through fastboot, if your xoom's bootloader is unlocked. I have never tried it with a locked bootloader, so I cant guarantee it working in that case. Anyways, following all the steps should completely return your xoom back to factory condition.

As mentioned. Root it. Get custom rom, EOS nightlies recommended.
Factory reset.
Thru recovery, Wipe cache. Wipe dalvik. Wipe battery stats. Flash rom, and gapps. Then reboot. Set date and time and google account and then try.
Sent from my MZ601 using Tapatalk 2

[Q] Doing a factory reset to a rooted Xperia L

I have an Xperia L phone which I rooted a few months back. I haven't unlocked the bootloader AFAIR. Just rooted it.
Now I have been getting weird memory space issues. I already tried the album galleries fix, the SD-Maid, rooted and deleted junk files but it still doesn't let me install apps. So I'm planning to do a factory reset.
1) Does anyone know what exactly happens in a factory reset in XPeria L? Does it have a built-in image that gets restored? Or does it only wipe the data and cache completely?
2) Any idea whether root will still be maintained or not?
3) Is there anything that I should watch out for?

mugenishere said:
I have an Xperia L phone which I rooted a few months back. I haven't unlocked the bootloader AFAIR. Just rooted it.
Now I have been getting weird memory space issues. I already tried the album galleries fix, the SD-Maid, rooted and deleted junk files but it still doesn't let me install apps. So I'm planning to do a factory reset.
1) Does anyone know what exactly happens in a factory reset in XPeria L? Does it have a built-in image that gets restored? Or does it only wipe the data and cache completely?
2) Any idea whether root will still be maintained or not?
3) Is there anything that I should watch out for?
Click to expand...
Click to collapse
As far as I know, it wipes your data completely. And doesn't restore any factory image. And therefore you shouldn't lose root.
However, I can't guarantee it. There's nothing you should watch for and you can always root your device.
Hit thanks ¡*

mugenishere said:
I have an Xperia L phone which I rooted a few months back. I haven't unlocked the bootloader AFAIR. Just rooted it.
Now I have been getting weird memory space issues. I already tried the album galleries fix, the SD-Maid, rooted and deleted junk files but it still doesn't let me install apps. So I'm planning to do a factory reset.
1) Does anyone know what exactly happens in a factory reset in XPeria L? Does it have a built-in image that gets restored? Or does it only wipe the data and cache completely?
2) Any idea whether root will still be maintained or not?
3) Is there anything that I should watch out for?
Click to expand...
Click to collapse
after factory reset everything will be reset to factory image..
you will loose root access for sure.

SU binary and the Superuser apk are installed on the system partition and thus not touchable by the factory reset.
Send from my A0001 using Tapatalk

Joery360 said:
SU binary and the Superuser apk are installed on the system partition and thus not touchable by the factory reset.
Send from my A0001 using Tapatalk
Click to expand...
Click to collapse
Which means that...the root access should still be there?

[Q] bootloop on 5.X, works o 4.4.4

Hello,
I would be grateful for any kind of help. My Nexus 5 (5.0.1, stock ROM, not rooted, has never been modified) started to lag. After reboot it seems to be in a bootloop (those flying dots are on the screen constantly).
I'm not so defenseless - I have some experience with rom flashing etc. so I tried everything I've managed to find on web. All kind of 'bootloop' fixes. I've tried multiple combinations of rom flashing and wiping after/before that.
I've tried TWRP/sideload instruction. I've tried Nexus Root Toolkit v2.0.5 app. And nothing works. Every time after flashing (successful!) it is still in bootloop. All information from flashing programs, adb console are always positive (success, etc.).
I've tried 4.4.4 KitKat upload via NRT 2.0.5 and wow! it worked. But every other attempt to flash it with 5.X version ends with bootloop - via NRT, via ADB and via OTA.
What it wrong? Why KitKat is working but Lollipop doesn't?
BTW - is there any option to check logs? What is causing nexus to stop?
UPDATE - doesn't work on 4.4.4 well, G Play, Camera, Gallery constantly crash. It is basically only phone (and text) now.

Are you sure L is bootlooping after successful factory image flash? I've seen L take some good 15min to boot.

@kkrulik
ADB has nothing to do with flashing factory images. You need a fastboot for that purpose. http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701

kkrulik said:
Hello,
I would be grateful for any kind of help. My Nexus 5 (5.0.1, stock ROM, not rooted, has never been modified) started to lag. After reboot it seems to be in a bootloop (those flying dots are on the screen constantly).
I'm not so defenseless - I have some experience with rom flashing etc. so I tried everything I've managed to find on web. All kind of 'bootloop' fixes. I've tried multiple combinations of rom flashing and wiping after/before that.
I've tried TWRP/sideload instruction. I've tried Nexus Root Toolkit v2.0.5 app. And nothing works. Every time after flashing (successful!) it is still in bootloop. All information from flashing programs, adb console are always positive (success, etc.).
I've tried 4.4.4 KitKat upload via NRT 2.0.5 and wow! it worked. But every other attempt to flash it with 5.X version ends with bootloop - via NRT, via ADB and via OTA.
What it wrong? Why KitKat is working but Lollipop doesn't?
BTW - is there any option to check logs? What is causing nexus to stop?
UPDATE - doesn't work on 4.4.4 well, G Play, Camera, Gallery constantly crash. It is basically only phone (and text) now.
Click to expand...
Click to collapse
I wish I knew how to enable USB debugging on boot from custom recovery, so we could see why it stops booting on 5.0+
Have you tried wiping or fixing /persist partition, but just for safety reasones do a backup of it first.

Thx for the tips.
Yes - i've been waiting quite long time after flashing to boot my phone. 20 minutes, one hour and even the whole night.
Yes - I've tried fastboot.
Persist partition is new for me - I'll try it tomorrow.

bitdomo said:
I wish I knew how to enable USB debugging on boot from custom recovery, so we could see why it stops booting on 5.0+
Have you tried wiping or fixing /persist partition, but just for safety reasones do a backup of it first.
Click to expand...
Click to collapse
WOW! Your manual has helped! Thanks a lot! So it was something wrong with /persist partition...
Can someone explain that little bit? What caused that and if it is possible to avoid such issues in the future?

kkrulik said:
WOW! Your manual has helped! Thanks a lot! So it was something wrong with /persist partition...
Can someone explain that little bit? What caused that and if it is possible to avoid such issues in the future?
Click to expand...
Click to collapse
I really dont know why it happens or what cause it on a never rooted, never bootloader unlocked and always been on 100% stock roms, but it happens and it is always the persist partition. Maybe one of system apps or services which have read-write privilages to the /persist partition cause it. But to detect it we need a constant loging and a high amount of luck to get /persist corrupted again.
Do you remember what were you doing with the phone when it happend?

bitdomo said:
I really dont know why it happens or what cause it on a never rooted, never bootloader unlocked and always been on 100% stock roms, but it happens and it is always the persist partition. Maybe one of system apps or services which have read-write privilages to the /persist partition cause it. But to detect it we need a constant loging and a high amount of luck to get /persist corrupted again.
Do you remember what were you doing with the phone when it happend?
Click to expand...
Click to collapse
Well, I'm lucky then
I was just watching some photos when phone started to lag. I turned it off and it never boot again.

Device dead

So my Z3...
I had it since start of the year it was AWESOME, but not enough.
I rooted it. First got Cyanogen, after battery drain went to eXistenz Y Rom, awesome. SOmehow model changed from D6653 to D6603 ( I'm aware of differences), data still working, Lte, all fine.
Then I flashed a GOogle Play Rom for Z3, it worked beautifully with the normal GPE stuff. But data didnt work. Then suddenly after a day it did!
Okay I was envious of M launcher, installed APK, force close... OK. I'll just flash again (Didnt make backup of that particular rom)
Data didnt work again... Then try change rom to eXistenZ Y, still not working, it isn't even detecting the sim card now, and is overheating even when idle...
Flashtool had some problems (Device needs drivers, blablabla when my PC Companion works perfectly with drivers all installed)
I think I'll go to Sony and act dumb? (I still hv warranty)

For flashtool you need to install drivers seperately. Just read a tutorial.

yuzhengwen said:
So my Z3...
I had it since start of the year it was AWESOME, but not enough.
I rooted it. First got Cyanogen, after battery drain went to eXistenz Y Rom, awesome. SOmehow model changed from D6653 to D6603 ( I'm aware of differences), data still working, Lte, all fine.
Then I flashed a GOogle Play Rom for Z3, it worked beautifully with the normal GPE stuff. But data didnt work. Then suddenly after a day it did!
Okay I was envious of M launcher, installed APK, force close... OK. I'll just flash again (Didnt make backup of that particular rom)
Data didnt work again... Then try change rom to eXistenZ Y, still not working, it isn't even detecting the sim card now, and is overheating even when idle...
Flashtool had some problems (Device needs drivers, blablabla when my PC Companion works perfectly with drivers all installed)
I think I'll go to Sony and act dumb? (I still hv warranty)
Click to expand...
Click to collapse
maybe it's good if you use the 0.9.18.6 version of flashtool (if you did an an upgrade to a newer one already) (the new flashtool caused problems at me)
and flash a KK stock, tick wipe: appslog, cache, data.
boot it up, then switch to lp stock, tick wipe: appslog, cache, data, boot it up, then go back to anything.
i would be curious if this works.
good luck *fingers crossed*

Aronuser said:
maybe it's good if you use the 0.9.18.6 version of flashtool (if you did an an upgrade to a newer one already) (the new flashtool caused problems at me)
and flash a KK stock, tick wipe: appslog, cache, data.
boot it up, then switch to lp stock, tick wipe: appslog, cache, data, boot it up, then go back to anything.
i would be curious if this works.
good luck *fingers crossed*
Click to expand...
Click to collapse
Yea says the same thing... device drivers not installed, can be found in drivers folder (There was no 'drivers' folder)
Just wiping internal storage... Not working as well
EDIT: I used stock cable and is working BUT flashtool just says connected in flashmode... ready to flash ... and doesnt flash. Then my device boots somehow
EDIT: I realized I didnt wait for it to ask me to connect device and had no patience. Oopsie! Thanks for the help. XDA FOR THE WIN (wat does xda stand for?)