Like the subject says, I'm fully rooted with SIM/bootloader unlocked, and SafetyNet is passing just fine thanks to Zygisk.
However, while fingerprints were still working after I got root, they disappeared at some point while backing up everything via Titanium Backup (Pro, if that matters). Now, while trying to re-enroll them, it just lights up but sits there doing nothing. No errors but also no additional vibration + light up.
Tried rebooting multiple times, going back to light theme/turning up brightness, and even using all of my fingers separately. Is there any kind of "temp cache" I can wipe to see if it might allow me to kick back off the enrollment process again?
Otherwise, should I aim for restoring my backup to see if that helps? I *should* be testing the recovery process that I rooted mostly to make available to me, after a fresh re-image (even though my current one is only two weeks old) but I'm worried it will mess up something else, lol
It's better to ask here.
Related
I've been having a weird issue for the past few weeks where my phone will lock up and the screen won't turn on anymore. Often, it happens with the phone in standby in my pocket. I'll feel a vibration (sometimes just 1 vibration, sometimes followed by the usual 3 fast vibrations of a force close) and then the phone is gone. I have to hold all 3 buttons to reset it and then it boots up fine like nothing is wrong. I've had this same issue on various roms I've used lately (Serendipity, Firefly, Cog4, etc.) and on my last flash I've even done the full flash to stock and master clear. Is anyone else having any issues like this?
I'm guessing this is 1 of 3 things:
1) I have a hardware problem with my phone and need a new one.
2) This is an issue with custom kernels with lagfix and I have to live with it or use a stock kernel. I know some custom kernels have had charging death issues (I've seen that happen to me also but idk if its from charging or the same thing as when its in my pocket)
3) Some app I installed is causing this. I have a hard time believing this can be the problem only because any app issues I've seen in the past just show up as a FC and don't take out the entire phone. If this is in fact an app issue, IDK how I'll ever figure out which one is causing it since it just dies and I don't get a chance to see a FC message or anything like that.
Any thoughts or suggestions are appreciated as I really don't know what to do at this point. My next step is probably going to run pure stock froyo for a few days to see if I still have the issue but I suspect I will since its been present on every rom config I've used. Whats even worse is, if it happens and I don't notice for a while, when I finally reboot it the battery is severely drained. Its like something gets in an infinite loop and kills the battery depending on how long I leave it like that (the phone also warms up when its been in this state for a while).
Thanks in advance for any help!
Sounds like a warranty replavement to me.
Caution swyping! Read at your own risk.
TheSopranos16 said:
I've been having a weird issue for the past few weeks where my phone will lock up and the screen won't turn on anymore. Often, it happens with the phone in standby in my pocket. I'll feel a vibration (sometimes just 1 vibration, sometimes followed by the usual 3 fast vibrations of a force close) and then the phone is gone. I have to hold all 3 buttons to reset it and then it boots up fine like nothing is wrong. I've had this same issue on various roms I've used lately (Serendipity, Firefly, Cog4, etc.) and on my last flash I've even done the full flash to stock and master clear. Is anyone else having any issues like this?
I'm guessing this is 1 of 3 things:
1) I have a hardware problem with my phone and need a new one.
2) This is an issue with custom kernels with lagfix and I have to live with it or use a stock kernel. I know some custom kernels have had charging death issues (I've seen that happen to me also but idk if its from charging or the same thing as when its in my pocket)
3) Some app I installed is causing this. I have a hard time believing this can be the problem only because any app issues I've seen in the past just show up as a FC and don't take out the entire phone. If this is in fact an app issue, IDK how I'll ever figure out which one is causing it since it just dies and I don't get a chance to see a FC message or anything like that.
Any thoughts or suggestions are appreciated as I really don't know what to do at this point. My next step is probably going to run pure stock froyo for a few days to see if I still have the issue but I suspect I will since its been present on every rom config I've used. Whats even worse is, if it happens and I don't notice for a while, when I finally reboot it the battery is severely drained. Its like something gets in an infinite loop and kills the battery depending on how long I leave it like that (the phone also warms up when its been in this state for a while).
Thanks in advance for any help!
Click to expand...
Click to collapse
What kernel are you running? And are you OC/UV?
If so, try a different kernel (like speedmod k13e) that doesn't have OC/UV option. Black screen is usually a UV setting problem.
If it's not the case, warranty?
EDIT: Have you flashed over different ROM with lagfix/ OC/UV enabled?
Right now I'm running lastest Cog 4 with the included kernel (which doesn't support UV). I was OC but once I had this issue I reset the clocks to stock but then it happened again. Before I installed Cog 4 I flashed stock and master cleared...
1. Did u restore any data using TiBu when u flashed the ROM? Did u happen to restore any system data?
2. Did u put on any kind of under volting?
Flash any ROM, say Firefly, and use it for a day or two without restoring any of ur apps, and see if the issue is coming up again.
If yes, try changing kernel, say to onix, and keep on for a day or two see if the issue is recurring.
Just to be sure, can u do this:
1. Revert to stock
2. Format internal SD (similar to master clear to clear out SD card; I never did a master clear so far, only this)
3. Copy the ROM u want to use to SD
4. Flash Firefly 3.0 (this formats all system partitions, so no need to master clear)
Firefly has hardcore's kernel by default, and this kernel does not apply lagfix by default. Same with onix kernel too, and this is the reason I am recommending this combination of ROM and kernels. I use onix cos I have some wifi issues on hardcore's kernel.
5. Do NOT restore of ur data or apps
I did restore data using TiBu but only app data. The only system stuff I restored was bluetooth pairings and wifi access points. Other than that only app data. I don't have any UV right now...
TheSopranos16 said:
I did restore data using TiBu but only app data. The only system stuff I restored was bluetooth pairings and wifi access points. Other than that only app data. I don't have any UV right now...
Click to expand...
Click to collapse
I would NOT recommend ANY system data, except for contacts storage. This is the only one system data I personally found not to cause any issues.
Its easier to connect BT and wifi again, than go through the pain restoring this data sometimes creates. I faced issues with my phone not being paired to my car when I tried to restore bluetooth settings. It shows my car, but doesn't pair. I had to restart phone, delete the connection, and then reconnect. I found it easier to add back, than restore and go through all this trouble.
This time, pls try to refrain from restoring any of ur data from TiBu and a day's run for the ROM and see how it goes. If it goes well, u can restore data. But, before u restore data, I would recommend taking a nandroid backup just in case restoring apps starts creating issues again. This could save some time by getting u back to current state with no apps, instead of flashing all over again.
Before doing any of those things, I would check out your IMEI number and compare it to the one in this link,
http://www.captivateforums.com/sams...random-shutdown-issues-on-att-captivate-1272/
I dont pay for any warranty through AT&T, but I brought my phone in to a device replacement center and they replaced mine with a brand new phone!
Its worth a shot if you ask me.
So, about 2 or 3 days ago I downgraded back to Froyo from the latest Gingerbread leak (too many bugs.) I did so with GTG's Ulimate unbrick, and then I flashed the pre-rooted/ pre-CWM stock ROM to it. I updated to the latest UCKH1 to be up to date, and then I restored a backup I made in ROM Manager a few weeks back. After that, I restored all my apps with Titanium backup. Now on to the issues. First time around my phone literally crapped out software-wise. It was literally force closing everything, texting wouldn't work, the Advanced power menu was gone except for Power Off. That only started after a full day of use with no issues whatsoever. It was completely random. Well late last night, I factory reset and put my apps back on again. Well I woke up this morning to find that my phone's suddenly being dumb again. Except this time the only issues that I know of are, the Advanced power menu's gone except for Power Off, and the home button will not function AT ALL. If anyone has any idea what's going on, or how I can resolve this, please lend a hand.
Kevinr678 said:
So, about 2 or 3 days ago I downgraded back to Froyo from the latest Gingerbread leak (too many bugs.) I did so with GTG's Ulimate unbrick, and then I flashed the pre-rooted/ pre-CWM stock ROM to it. I updated to the latest UCKH1 to be up to date, and then I restored a backup I made in ROM Manager a few weeks back. After that, I restored all my apps with Titanium backup. Now on to the issues. First time around my phone literally crapped out software-wise. It was literally force closing everything, texting wouldn't work, the Advanced power menu was gone except for Power Off. That only started after a full day of use with no issues whatsoever. It was completely random. Well late last night, I factory reset and put my apps back on again. Well I woke up this morning to find that my phone's suddenly being dumb again. Except this time the only issues that I know of are, the Advanced power menu's gone except for Power Off, and the home button will not function AT ALL. If anyone has any idea what's going on, or how I can resolve this, please lend a hand.
Click to expand...
Click to collapse
It sound like every time you encountered a problem it was after restoring your app with TiBu. Are you just restoring apps or apps&data? See how your phone runs without restoring apps. Try restoring apps(without data) and see what happens, or just manually download apps again. Could be a problem with data from the apps.
bigfau said:
It sound like every time you encountered a problem it was after restoring your app with TiBu. Are you just restoring apps or apps&data? See how your phone runs without restoring apps. Try restoring apps(without data) and see what happens, or just manually download apps again. Could be a problem with data from the apps.
Click to expand...
Click to collapse
I was wondering the same. I have indeed been restoring apps with data. Didn't want to lose my Cut the Rope progress But, they may end up being my problem. I've always gotten away without issues, so I guess it's about time for one to happen, haha. I'll try it out after work today and post how it goes.
Kevinr678 said:
I was wondering the same. I have indeed been restoring apps with data. Didn't want to lose my Cut the Rope progress But, they may end up being my problem. I've always gotten away without issues, so I guess it's about time for one to happen, haha. I'll try it out after work today and post how it goes.
Click to expand...
Click to collapse
Most likely the problem lies with the backups being from a GB rom and now you are trying to put them an a Froyo rom. Probably saves it differently or something.
They tell you "Not" to use the backups from Titanium as they can cause issues, I reinstalled back to Stock Froyo as well running the latest UCKH1, When you do the Update to UCKH1 my advice is to go to Settings: Privacy: and do a Factory reset to fix the clock problem The clock will appear screwed up and will correct itself even when it's on Automatic Mode. Otherwise all is fine downgrading from GB Rom. Install all normal apps as usual, Screw Titanium my advice is just save the .apk file for the app in a Folder on your External SD Card, that's my quick way of reinstalling all my apps back regardless of losing settings.
you can also use tibu to restore single apps with data, you can try the ones you want to save progress and see if it causes issues. just stay away from system apps
I've never ha a problem with TitBU, as long as I restored "missing apps & data" ONLY!
same here, regardless of android version or even restoring on a different device. the only time i have seen issues is when i accidentally hit restore all apps with data, including system apps. thats when i got the constant fc and crashing
bigfau said:
Most likely the problem lies with the backups being from a GB rom and now you are trying to put them an a Froyo rom. Probably saves it differently or something.
Click to expand...
Click to collapse
You know, now that I think about it I actually made a backup from UCKJ2. That's more than likely my problem. Funny how I'm looking for all these complicated things and it ends up being something easy. Haven't restored anything, so I'll wait a day or two and see if everything stays like it should, and then I'll restore only what's needed to ensure it stays that way. Sorry it took so long to respond, had work, haha. Thanks guys all the responses were much appreciated.
Kevinr678 said:
You know, now that I think about it I actually made a backup from UCKJ2. That's more than likely my problem. Funny how I'm looking for all these complicated things and it ends up being something easy. Haven't restored anything, so I'll wait a day or two and see if everything stays like it should, and then I'll restore only what's needed to ensure it stays that way. Sorry it took so long to respond, had work, haha. Thanks guys all the responses were much appreciated.
Click to expand...
Click to collapse
You should be alright as long as you don't restore data. I think. Lol
Sent from my SAMSUNG-SGH-I997 using Tapatalk
For the past few days, my phone has been acting up pretty badly. On the rare occasions that it finishes booting (usually gets to the CM boot animation and stays there), it will then only work for a short time before either I press the lock button to wake the device, but the screen stays black, or occasionally the screen will go black while I'm actually using the phone. The only way I have managed to get the phone working again is pulling the battery and restarting, and hoping it will boot this time.
It seems to do the black screen thing particularly frequently when text messages are received, but it's not ONLY when they are received.
It started when I flashed the latest kernel posted in the Evervolv thread [here: http://forum.xda-developers.com/showpost.php?p=41359720&postcount=183]. My current rom is CM10 build #6. Once this started happening, I restored a nandroid backup I had made a few weeks ago. At first I only restored the "boot" partition, and when that didn't help I restored the "system" and "boot" partitions. That still didn't work, so I flashed the Garuda kernel v5. That also did no good.
Is my only option re-flashing my ROM? I'm a little reluctant because that would mean losing all my apps etc. and having to restore them. I guess I could try a full nandroid restore first.
But before I go too drastic and potentially lose data, does anyone have any other suggestions as to what may be the cause?
I also have Mounts2SD installed (from Play Store) in case that's relevant.
EDIT: Could I flash the ROM without wiping and thus keep my installed apps and data?
A logcat would help.. In the meantime, install the" app2zip" app from the play store.. It allows you to make flashable zips of installed apps.. Also, try to find "zipme" by jrummy.. That app lets you make a flashables of apps, app data, system data, Bluetooth pairing info, Wi-Fi info, n much more.. And just to have covered all the bases, try reflashing the full rom...
ғг๏๓ ҭђє ғเรђ™
I'm cautious about speaking too soon, but last night I fixed permissions in recovery and it hasn't black screened or rebooted since so I'm hopeful it may be Ok now. Thanks so much for the suggestions though, I'll be sure to look into those options in case something else goes wrong or else if this problem isn't actually fixed.
Edit: oh and I had tried to get a logcat but once it black screened it wouldn't respond to adb
The Problem: As soon as I make a call or answer one I'm receiving, the screen goes completely black, although the call is connected and I can speak with them okay. I almost always must reboot the phone by holding power and volume button in order to use my phone again. Very rarely the screen has turned back on, I think after the call disconnects, but this is not reproducible.
I can't say when this started happening, but it may have been after I was fixing a "ERROR: LoadImageAndAuth Failed: Load Error" boot up issue I created when messing around, I think when I restored an old backup made with TWRP. I fixed the problem using this method (a modified Deuce script/.bat file that flashed in the 8.1 OTA to both A/B slots) but I'm not positive. I don't talk on my phone that much so it's hard to say what when.
I'm contemplating putting my phone as far back to storebought-stock-setup as I can before I modified it with Magisk and TWRP, but I wanted to check in here to see if anyone had suggestions on what to look at. My Hope is this will subside when I undo everything and then I can see where the problem was created as I walk the path again, checking as I go.
I tried wiping my data partition in TWRP and setting Android it up from scratch but it looks like the water is still black.
mentalfloss said:
The Problem: As soon as I make a call or answer one I'm receiving, the screen goes completely black, although the call is connected and I can speak with them okay. I almost always must reboot the phone by holding power and volume button in order to use my phone again. Very rarely the screen has turned back on, I think after the call disconnects, but this is not reproducible.
I can't say when this started happening, but it may have been after I was fixing a "ERROR: LoadImageAndAuth Failed: Load Error" boot up issue I created when messing around, I think when I restored an old backup made with TWRP. I fixed the problem using this method (a modified Deuce script/.bat file that flashed in the 8.1 OTA to both A/B slots) but I'm not positive. I don't talk on my phone that much so it's hard to say what when.
I'm contemplating putting my phone as far back to storebought-stock-setup as I can before I modified it with Magisk and TWRP, but I wanted to check in here to see if anyone had suggestions on what to look at. My Hope is this will subside when I undo everything and then I can see where the problem was created as I walk the path again, checking as I go.
I tried wiping my data partition in TWRP and setting Android it up from scratch but it looks like the water is still black.
Click to expand...
Click to collapse
I'm having the same issue but my pixel two is bone stock running 8.1.
Sent from my Pixel 2 using Tapatalk
Screen protectors that do not allow for the light sensor have this issue.
At least I'm not alone, if only for this problem, but my soul is still empty
steve0.adams said:
I'm having the same issue but my pixel two is bone stock running 8.1
Click to expand...
Click to collapse
That's good to know an unmodified version is also affected. Let us know what becomes your fix eventually, even if that means you had it swapped for another phone.
Turns out when the call disconnects I can access my screen again. A temporary fix I figured out is in Android's Accessibility settings you can set the power button to hang up a phone call, so that will let you get back into the system without forcing a reboot.
Doesn't apply to me
teakdamar said:
Screen protectors that do not allow for the light sensor have this issue.
Click to expand...
Click to collapse
I have a screen protector but the phone still functioned okay after it was applied. Just to double-check this I just peeled it back right now and the same behavior still happened. Good point, though.
Let me tell you a story (you can skip if you want to):
Once upon a time I ****ed up the back layer of the touch screen during repair and desperately tried to use my phone with my PC, found some tools online that let me simulate my phone's screen via ADB. Didn't got that working, ADB was unable to recognize my phone. Ok. Then i taped together the touchscreen (one of the absurdest things i ever did), reconnected it to the phone and guess what. It worked. I booted into recovery mode first and it worked flawlessly. No issues whatsoever. "Wonderful" i thought to myself, booting into system mode eagerly. The boot animation went by without any crashes, graphical issues or anything one could think off, and i even was able to enter my pin. When i did that i was full of enthuisasm. But that didn't last long. The SystemUI began to crash constantly, the lockscreen hasn't even finished building and it crashed again. I was absolutely unable to use the device and utterly devasted. Then i absolutely knew: i. ****ed. up.
But that didn't keep my from trying things out and eventually i was able to get past the lockscreen (without a SIM card so no PIN required) without any crashes and back up at least Whatsapp and a few other apps. But then i made the mistake of turning the screen off which set me back to square one: constant SystemUI crashes. I tried again and again and again and finally, after hours of work i got in a second time. This time, i thought to myself, i gonna make things differently. I backed up everything with Titanium, thought of myself to be safe. Which i technically was, i got backups of everything now. Then i decided to re-flash the rom without a factory reset which didn't do anything. Luckily there is an unofficial build of the ROM i'm using (Resurrection Remix) and i clean flashed it. It worked. Flawlessly. I was thrilled. The phone i was ready to toss into the trash finally worked again. I set everything up, thought myself to be safe but boy was i wrong. Google made regular (i think daily) backups of my apps and contacts and all so i wanted to restore that first. But it required a Pattern which i don't have because i always had a 5x5 pattern and it gave me a 3x3 pattern. I didn't know what to do with it!
I continued setting up my phone after failing to restore that backup and then instantly continued to restore the backup i made with Titanium, It installed all the missing apps, apparently restored the data. Nice. But there are a few apps that don't like that restored data so they just didn't use it and started from scratch again (like SwiftKey). Also, some of my contacts are missing and i'm lowkey too lazy to like the existing ones to Whatsapp again.
Tl;dr: ****ed up phone, got it working again, some apps didn't accept the Titanium backup and now i want to restore the Google backup which requires a 3x3 pattern which i don't have because i always used a 5x5 pattern.
Well, the question is simply: Is there a way to unlock the Google Drive backup without that pattern or do i need to try my luck again accessing the old Data (made a TWRP backup before flashing the new ROM)? If i do need to try again, how do i disable the lock on my backups? Do i only need to change my pattern to a 3x3 one?