Database Users

[Q] CM10.1 (3/02 nightly) + Franco #95. Reboot and touchscreen is unresponsive.

I don't know what the hell happened, but today I went to switch my sim card from another phone to my N4 (I have multiple and like to use different phones every now and then). So I turned the N4 off and put the sim card in it and rebooted it. When it rebooted and got to the lock screen, I could do nothing that didn't involve the power key or the volume rocker. So I rebooted and it happened again! Okay. Reboot one more time. Same thing. So this time I booted into recovery and cleared cache/dalvik cache and rebooted. After a few seconds the touch screen started working again (might be related to clearing cache/dalvik, might not).
No idea what went wrong, but is this more likely to be a kernel issue or a ROM issue? Or something else? I've been running this rom/kernel since 3/02 and it's been flawless until now. Has anyone else had this happen?

blackplague1347 said:
I don't know what the hell happened, but today I went to switch my sim card from another phone to my N4 (I have multiple and like to use different phones every now and then). So I turned the N4 off and put the sim card in it and rebooted it. When it rebooted and got to the lock screen, I could do nothing that didn't involve the power key or the volume rocker. So I rebooted and it happened again! Okay. Reboot one more time. Same thing. So this time I booted into recovery and cleared cache/dalvik cache and rebooted. After a few seconds the touch screen started working again (might be related to clearing cache/dalvik, might not).
No idea what went wrong, but is this more likely to be a kernel issue or a ROM issue? Or something else? I've been running this rom/kernel since 3/02 and it's been flawless until now. Has anyone else had this happen?
Click to expand...
Click to collapse
It has happened to me before. I would definitely update both as there might have been a bug fix on that specific ROM/kernel type. I would probably think it would be a ROM issue, but I guess there's a chance for the kernel. I would wipe and update and see what happens.

OEM STOCK S4 suddenly showing CUSTOM at boot! WTF?

My phone is bone stock, never rooted, flashed modded. Last night I put the phone on charger and woke up to phone being locked up. I removed/reinstalled battery and booted up.
TO my surprise on boot below the samsung logo, it says "CUSTOM" with an unlocked picture of a lock.
Anyone else have this issue? I've never modified the rom/recovery nor have I rooted.
I do have Nova launcher and Foxfi......could those be a culprit?
Update: I tried going into stock recovery. WHen I boot with buttons pressed it says "Recovery Booting" but nothing happens and phone reboots itself.

n19htmare said:
My phone is bone stock, never rooted, flashed modded. Last night I put the phone on charger and woke up to phone being locked up. I removed/reinstalled battery and booted up.
TO my surprise on boot below the samsung logo, it says "CUSTOM" with an unlocked picture of a lock.
Anyone else have this issue? I've never modified the rom/recovery nor have I rooted.
I do have Nova launcher and Foxfi......could those be a culprit?
Update: I tried going into stock recovery. WHen I boot with buttons pressed it says "Recovery Booting" but nothing happens and phone reboots itself.
Click to expand...
Click to collapse
What's funny is, I am running the Task650 AOKP rom and Goldeneye rom and my custom padlock icon went away on its own. Many others have reported the icon randomly showing up too. I'm betting it will go away. Try rebooting your device a couple of times and if it really bothers you do a factory reset.
It's really not that big of a deal. Your're still running the samsung recovery.

Interestingly, my phone did this for the first time last night as well. I've been rooted since the beginning. Since you mentioned it I'm also using Nova launcher but can't imagine that matters.

Well my concern is when it happens at the wrong time, say during a warranty repair/replacement. A message like that is show and bam, no warranty.
I went to the AT&T Device Support Center for my Note II and they booted the phone, and then into download mode to see if it was modified or not (obviously I had returned to stock). So they do check

Nova launcher in not the culprit, because I am on TW and it does the same, in and out that message appears, haven't seen it in a week or 2, but it will pop up occasionally. I think anytime you approach the bootloader with a modification, that will show, and then disappear. I could be wrong, but there has been no certain pattern confirmed by anyone.

do any of you guys have a 64gb Sandisk microsd?

polish_pat said:
do any of you guys have a 64gb Sandisk microsd?
Click to expand...
Click to collapse
no. I have a 32GB Samsung micro-sd.

n19htmare said:
no. I have a 32GB Samsung micro-sd.
Click to expand...
Click to collapse
then try this: http://forum.xda-developers.com/showthread.php?t=2296014

polish_pat said:
then try this: http://forum.xda-developers.com/showthread.php?t=2296014
Click to expand...
Click to collapse
He can't do that if he's not rooted.

CZ Eddie said:
He can't do that if he's not rooted.
Click to expand...
Click to collapse
he can root and then unroot. Or he can do the following: take our SD card, reboot twice and check if your system status is still custom

polish_pat said:
he can root and then unroot. Or he can do the following: take our SD card, reboot twice and check if your system status is still custom
Click to expand...
Click to collapse
Just an update. rebooted a few times and CUSTOM message was still there. then I turned the phone off and left it off for a few minutes rebooted and it was gone.
WEIRD!
I did a bit of research and seems like this issue (If you wanna call it that) has been lingering around on GS3 too. Wonder what the cause is.
If someone knows or figures it out, please update this thread. THanks.

n19htmare said:
My phone is bone stock, never rooted, flashed modded. Last night I put the phone on charger and woke up to phone being locked up. I removed/reinstalled battery and booted up.
TO my surprise on boot below the samsung logo, it says "CUSTOM" with an unlocked picture of a lock.
Anyone else have this issue? I've never modified the rom/recovery nor have I rooted.
I do have Nova launcher and Foxfi......could those be a culprit?
Update: I tried going into stock recovery. WHen I boot with buttons pressed it says "Recovery Booting" but nothing happens and phone reboots itself.
Click to expand...
Click to collapse
Same thing happen with me by replacing the battery. Just now. Nova launcher was acting up earlier. Galaxy S4 AT&T I was trying to keep this virgin I guess I now have to root and unroot.. But is this an option actually because they have protected the firmware so far to say that you cannot make yours virgin anymore without the original virgin firmware??

i have a sgh i337 at&t.. my phone suddenly freezed and went to bootloop
It suddenly freezed and after some minutes, it automatically went to bootloop.. All I see is the at&t logo for hours.. After that, I wiped data n cache from recovery and the phone started to work well, but after 30 minutes or more , same things are repeated.. Freezes and Wents to bootloop.. And the option I only have is to do a hard reset which works only for 30 minute.. And when I use the phone for 5 minutes after reset and then I restart it, it freezes on lock screen and goes to bootloop.. Please help.. Will flashing a custom ROM will work?.. I want to change the carrier and remove at&t.. Please help..

I had this same exact problem, with stock S5. One thing I noticed with mine that no one else mentioned was if I went into settings and then storage it would say SD Card - READING I believe and I couldn't access my pictures. Nor could I format it or erase it when i was doing a factory reset through the settings options. My phone would also freeze, and then there was times the screen would go black and on the very top of the screen would only display the time and battery life the time would change as well as the battery percentage but I was unable to leave that screen except if I would hold the power button down it would show me all the normal reset, power off options and I was able to select any one the options available. What ended up working for me was, removing the SD Card and replacing it. Then I did a factory reset through the settings options menu. Once it finished I instantly ( did not proceed with setup) I turned the phone off and then held the power button the volume up and home button and reset it that way as well. Once it rebooted I noticed the problem was gone and everything was back to normal.

Massive softbrick (haven't found a solution yet)

Hello everyone,
So here's my story: I got a 6P short after release and it's been amazing. After switching from a S6 I couldn't be happier until 3 days ago.
I was playing around with my phone (checking for updates on the play store if I recall correctly) and I was going to switch from 4g to wifi. I went ahead and pulled down my notification shade and went to press WiFi but misclicked and hit Hotspot which was below it. My phone suddenly froze big time and this is for the first time ever since purchase.
At first I thought I'd wait it out since the device was completely unresponsive, home button didn't work and neither did anything on screen. Buttons didn't make a difference either. 10 minutes went by and I ended up force restarting by holding down power + volume up. First part of my bootup went fine but when it got to the android boot animation after I put in my pin to allow the device to start it dropped from the smooth usual framerate down to 1 frame every 10-15 seconds and it slowed down further until it came to a complete halt around the time the android letters appear.
My first thought was corrupt rom so I went ahead and wiped data from the stock recovery. I was running completely stock with no modifications whatsoever. That didn't do anything. Phone still froze in the same boot phase. Desperate I unlocked bootloader to flash a clean fresh image to try to fix it and to my surprise that didn't change a thing.
As I was getting pretty desperate already I had one more idea and that was to flash up to the Dev preview. To my huge surprise it booted and I jumped from excitement. So I started setting up my phone again. I got past the prompt to insert sim card and I was now at the screen to choose a wifi network. As soon as I clicked into that the phone froze up again and at that point I lost all hope.
I wiped data in stock recovery and shut the phone down for the night. On day 3, today I woke up and tried starting the phone and it worked as if nothing had happened. I went through the setup and set up my phone on the N preview. At a certain point I was planning to go back to the latest official build but for now I was happy my phone was back from the dead. Later today I tried to restart my phone to clear all running apps etc and it froze up on boot.
I'm losing all hope that I'll be resolving this myself so I'm reaching out to the community to see if anyone's had this happen to them before and hopefuly for a solution. It's still under warranty so I can eventually send it back to the retailer but I'd rather not have a phone for 3 weeks.
Any and all help is appreciated.
Thank you for reading through my long and probably pretty boring story!

Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?

To the OP, is there any reason you did not flash to release version 6 instead of Dev preview ?
Also, any reason you can not simply do the "unenroll" from https://www.google.com/android/beta ?
It will require you to setup certain settings again as you will be back to a "factory reset".

DJBhardwaj said:
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
Click to expand...
Click to collapse
DJBhardwaj, i haven't specifically erased those partitions. I was under the impression wipe userdata along with reflashing did that. I will try that tonight when I get home!
Xdafly, I only updated up to N as a last resort because at first I had a locked BL. I was planning to unenrol but that would've been too late as it self bricked after a restart.

DJBhardwaj said:
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
Click to expand...
Click to collapse
Well I just did the erase thingy and my phone booted but wifi won't turn on. Enabling hotspot doesn't brick anymore but I now suspect WiFi might've been the issue. Any tips on how to find out what it could be and possibly fix it?
Edit: 2 restarts and a factory reset later I'm back to bricked same way as before.

try safe mode

mr.dj26 said:
try safe mode
Click to expand...
Click to collapse
That was my first thought, that was the restart that bricked it again. Safe mode shouldn't have made a difference since I hadn't even logged into Google account for apps.

After reading the very first post; sounds like bad WiFi hardware.
All the hanging has been related to WiFi or Hotspot.

I think you should get a replacement
Sent from my Purified NexusixP
If Someone Helped You Then Dont Just say Thanks...Hit The Thanks Button!

Is your phone rooted and did you install Xposed?
Over the weekend I shutdown my 6p (stock rooted with April security patch, Xposed v80) and charged it. When it turned it back up I kept getting "Unfortunately, nfc service has stopped". Long story short: I ended up factory reset my phone and reinstalled EVERYTHING and I still got into bootloop. Then I came across
https://github.com/rovo89/Xposed/issues/113
https://github.com/rovo89/android_art/issues/28
At the end of the second post rovo89 (developer of Xposed) fixed the bug in V83. I wiped my 6p once more and installed everything with v83. Problem solved.
Good luck!

V20 laggy after rooting

I rooted my v20 simply for viper4android and to enable the google assistant. Nothing else was done.
Ever since rooting, before even installing v4a, the notifications pull down was lagging when trying to swipe things away (it would leave a blank white space). Now, tons of things lag:
When trying to setup Google Voice
When opening Poweramp
When trying to pause or skip tracks in Spotify
When closing Chrome
The phone will hang; if I pressed a soft menu button, it will stay lit until the phone recovers.
I have factory reset, installed busybox and supersu only and still received the lag.
Is there something I can check or something I missed?

Faustous said:
I rooted my v20 simply for viper4android and to enable the google assistant. Nothing else was done.
Ever since rooting, before even installing v4a, the notifications pull down was lagging when trying to swipe things away (it would leave a blank white space). Now, tons of things lag:
When trying to setup Google Voice
When opening Poweramp
When trying to pause or skip tracks in Spotify
When closing Chrome
The phone will hang; if I pressed a soft menu button, it will stay lit until the phone recovers.
I have factory reset, installed busybox and supersu only and still received the lag.
Is there something I can check or something I missed?
Click to expand...
Click to collapse
Sorry for reviving a year and a half old thread, but did you find any solution? I am facing the exact same problem. I have one unrooted G5 and rooted V20 and another rooted G5, and the rooted ones lag horribly. Im in the exact same situation as yours, but I have magisk instead of SuperSU installed.

Hadi99 said:
Sorry for reviving a year and a half old thread, but did you find any solution? I am facing the exact same problem. I have one unrooted G5 and rooted V20 and another rooted G5, and the rooted ones lag horribly. Im in the exact same situation as yours, but I have magisk instead of SuperSU installed.
Click to expand...
Click to collapse
are you still running the ROM that was on the phone, after rooting? if i remember correctly (this was a year n a half ago... memory is **** nowadays.) some folks had problems when not flashing a new ROM after rooting.
maybe try a new ROM flash? .... I'm a nuke-n-pave kinda guy, so this is what i tend to resort to when in doubt.

Hadi99 said:
Sorry for reviving a year and a half old thread, but did you find any solution? I am facing the exact same problem. I have one unrooted G5 and rooted V20 and another rooted G5, and the rooted ones lag horribly. Im in the exact same situation as yours, but I have magisk instead of SuperSU installed.
Click to expand...
Click to collapse
Have you removed rctd? It may help...worth a shot.
https://labs.xda-developers.com/store/app/com.zacharee1.rctdremoverforlg

pistacios said:
Have you removed rctd? It may help...worth a shot.
https://labs.xda-developers.com/store/app/com.zacharee1.rctdremoverforlg
Click to expand...
Click to collapse
Thanks for the suggestions. Actually removing CCMD from RCDT tool did help a bit. It went from completely unusable to barely usable. Previously, it occasionally used to pause for about 20 seconds or so. But I still wonder what did LG implement to make the phone this laggy over time. Sure I have an enormous amount of apps installed, but they work just fine on the unrooted G5.

What variant do you have?
Have you tried flashing stock image with an updated kernel? Then update with kdz writer.

Guys after i did something stupid like factory reseting through settings (kept entering into twrp after that) i lguped to stock. Umm hello, is this my V20? I feel like i have a new phone! Previously i struggled with AKT performance profiles and diffenrent kernels but i wasn't happy, it always felt sluggish in some tasks. That is why i tried to f. reset in the first place, to see if it would feel fresh again. Currently i'm fully stock and the phone is flying! Only thing i'm missing is the mod that unlocks the high impedance hi-fi mode. For the time being i'll manage without it, i prefer having a phone that flies! I doubt it was the rctd because all custom kernels afaik include the removal script. Anyway thought i should chime in on this, as this happend a few days ago.

Lg doesn't wants us to have root access, simple as that, after rooting I got issues of lag, heating of phone and green hang screen. I too got a brand new fast flying v20 after flashing it with stock kdz via lgup with no root. So I guess, if factory reset wipe, cache, dalvik doesn't help you with lag issues you better flash it with stock rom for best performance

Fingerprint reader suddenly stopped- was working this morning!

My phone rebooted on me today while using the flashlight (something that occasionally happens from time to time), and now my fingerprint reader doesn't seem to work.
It says Fingerprint Hardware Not Available when I try to use it from the lock screen. The actual hardware itself is working, as I can still go into settings and try to set up a new fingerprint, it will vibrate and show that I touched the sensor as I move my finger, but then it fails at the end saying "enrollment not completed".
I also can't delete any of my saved fingerprints. It seems to get stuck trying to delete when I click one to remove. I'm thinking some sort of security thing got messed up when it rebooted, and I don't know how to fix it. I am rooted, so I already tried wiping cache and dalvik from TWRP. Not sure how to remove fingerprint data and start over... is there a way to do that?
I'm running the latest PE rom (flashed last week), and no, I didn't flash from Nougat in case anyone thinks this is that common issue some people have. I would try the fix for that, but since it isn't the cause of my problem I'm afraid it might mess things up more. Would really rather not hard reset again, took too long to get my phone set up with everything and paired again.

Dishe said:
My phone rebooted on me today while using the flashlight (something that occasionally happens from time to time), and now my fingerprint reader doesn't seem to work.
It says Fingerprint Hardware Not Available when I try to use it from the lock screen. The actual hardware itself is working, as I can still go into settings and try to set up a new fingerprint, it will vibrate and show that I touched the sensor as I move my finger, but then it fails at the end saying "enrollment not completed".
I also can't delete any of my saved fingerprints. It seems to get stuck trying to delete when I click one to remove. I'm thinking some sort of security thing got messed up when it rebooted, and I don't know how to fix it. I am rooted, so I already tried wiping cache and dalvik from TWRP. Not sure how to remove fingerprint data and start over... is there a way to do that?
I'm running the latest PE rom (flashed last week), and no, I didn't flash from Nougat in case anyone thinks this is that common issue some people have. I would try the fix for that, but since it isn't the cause of my problem I'm afraid it might mess things up more. Would really rather not hard reset again, took too long to get my phone set up with everything and paired again.
Click to expand...
Click to collapse
Reflash PE. If that doesn't work do a clean flash.

Boot into TWRP
Go to advanced>filemanager to acces the files in your phone.
Enter the folder /data/system/user/0
Delete following files: ./fpdata/user.db, settings_fingerprint.xml
Reboot to system and set up new fingerprints with the fingerprint wizard
Everything should work normal