Database Develop

[Q] a quick bypass of pattern lock

Recently my BFF thinks that her boyfriend is starting to lose feeling for her and start finding other girls. She wants to break up but her boyfriend won't let her go unless she provides evidence that he is losing feeling/cheating on her. She asked me to help but I'm at a loss except for one idea.
It was recently reported in the newspapers that you could bypass all security by freezing an android phone for an hour, then quickly removing the battery and putting it back on and turning it on while it was still below -10 degrees celcius. Is this really possible?
Secondly, his phone is a Galaxy Mini with whatever is the newest firmware (I'm a galaxy Mini II user so I'm not too sure), stock kernel, stock ROM, non-rooted but bootloader i think by default it's unlocked in SG. (mine came unlocked). It's been in use for quite some time only.
If the freezing is not possible, could we do it by any other method? note: before i can get pass the damn password i can't turn adb, unknown sources or debugging on.
Yeah that's all. Also, we can't wipe the /data since that's what we're gunning for. The method must be accomplish-able within 2 hours.
I might sound like I'm asking for a lot and might be unreasonable but please help.
Thanks in advance.
P.S. Please don't talk about the "just break up" or "politely ask him". If that had worked I wouldn't be asking here. He refuses to break up and he refuses to give his phone to me, even to "play". so called ethical hacking through the human link doesn't work anymore. We plan to take his phone for a while, bypass the pattern lock, then sieve through information.

blazerphoenix said:
Recently my BFF thinks that her boyfriend is starting to lose feeling for her and start finding other girls. She wants to break up but her boyfriend won't let her go unless she provides evidence that he is losing feeling/cheating on her. She asked me to help but I'm at a loss except for one idea.
It was recently reported in the newspapers that you could bypass all security by freezing an android phone for an hour, then quickly removing the battery and putting it back on and turning it on while it was still below -10 degrees celcius. Is this really possible?
Secondly, his phone is a Galaxy Mini with whatever is the newest firmware (I'm a galaxy Mini II user so I'm not too sure), stock kernel, stock ROM, non-rooted but bootloader i think by default it's unlocked in SG. (mine came unlocked). It's been in use for quite some time only.
If the freezing is not possible, could we do it by any other method? note: before i can get pass the damn password i can't turn adb, unknown sources or debugging on.
Yeah that's all. Also, we can't wipe the /data since that's what we're gunning for. The method must be accomplish-able within 2 hours.
I might sound like I'm asking for a lot and might be unreasonable but please help.
Thanks in advance.
P.S. Please don't talk about the "just break up" or "politely ask him". If that had worked I wouldn't be asking here. He refuses to break up and he refuses to give his phone to me, even to "play". so called ethical hacking through the human link doesn't work anymore. We plan to take his phone for a while, bypass the pattern lock, then sieve through information.
Click to expand...
Click to collapse
ADB isn't on, well i think somehow exploit might work. Search around XDA there are some tutorials here.

F4uzan said:
ADB isn't on, well i think somehow exploit might work. Search around XDA there are some tutorials here.
Click to expand...
Click to collapse
Erm sorry i'm not sure what do you mean by exploits. I'm sorry I'm kinda new to all these stuff.

How do u know that the phone is not "Debugging On"
Most android users are turning on that feature.
Well if the Debugging is ON ... I got the way to unlock the pattern within 1 minute.

Fastest way to bypass: Wipe data. If you can't, there are only harder ways.

Factory reset
You can always do a factory reset to remove the lock but it will wipe /data. You can still do that tho. It's explained here : http://www.hard-reset.com/samsung-gt-s5570-galaxy-mini-hard-reset.html . Also the fastboot mode works with adb swell as download mode.

Generalil said:
You can always do a factory reset to remove the lock but it will wipe /data. You can still do that tho. It's explained here : http://www.hard-reset.com/samsung-gt-s5570-galaxy-mini-hard-reset.html . Also the fastboot mode works with adb swell as download mode.
Click to expand...
Click to collapse
Mini doesn't have fastboot. It only have Recovery, and Download Mode (don't tell me about normal boot).

My mistake ;P A habit from LG-GT540

ಠ_ಠ

Verizon Auto-Updating Turbos to .49?

Something really strange happened to my father's Turbo. He got it brand new from Verizon about a month ago and I sat down and updated up to .44. I told him that if another update comes in, do not touch it because I was going to unlock it with Sunshine and root it. I don't allow him to do updates on anything, I do it for him when I know the bugs won't screw anything up and flash it myself.
I was ready to unlock the phone and when I looked About Phone, I saw it was on .49. So I checked a little more and found the exact date and time it updated (July 23rd, 7:23PM). The date and time coincided with his being in the hospital and I had possession of the phone. The phone was sitting in my room (there's no one else around to mess with things), undisturbed for a week. I never saw the .49 update show up before I left it alone--and I checked it to make sure he didn't accidentally update it, just in case. I know on my Turbo, it was annoying as all get out and I dealt with the nag screens for a week or so until I could buy the Sunshine app.
Is it possible Verizon is now forcing the .49 update? I know there's no way possible that either, I or my father, allowed this update to happen.

pearlheartgtr said:
Is it possible Verizon is now forcing the .49 update? I know there's no way possible that either, I or my father, allowed this update to happen.
Click to expand...
Click to collapse
Others have claimed that with some people being very skeptical. I would not put it past Verizon. Is it possible if you totally ignored the nag screens Verizon takes that as a yes?

Thing is, the update and nags never showed up in the first place for it to be accepted or ignored. It just happened.

My phone auto-updated while I was sleeping one night. I was thinking of unlocking the bootloader. Oh well.

lastnight that's update come to my turbo,.luckily that's happen when the phone on my hand,so i'm disconeted a mobile data ..
but now i'm stuck on no mobile data or wifi cause i'm afraid when i'm turn it on,the updates get installed

mt021322 said:
lastnight that's update come to my turbo,.luckily that's happen when the phone on my hand,so i'm disconnected a mobile data ..
but now i'm stuck on no mobile data or wifi cause i'm afraid when i'm turn it on,the updates get installed
Click to expand...
Click to collapse
(Wow, that's quite a cracked screen!)
Can you boot into recovery and clear cache? Would that clear the downloaded update files from the phone?
Of course, first chance -- after you stop the SUTL-49 update -- you get go ahead and unlock the bootloader already! Then you don't have to worry about it anymore.

(Wow, that's quite a cracked screen!)
Can you boot into recovery and clear cache? Would that clear the downloaded update files from the phone?
Of course, first chance -- after you stop the SUTL-49 update -- you get go ahead and unlock the bootloader already! Then you don't have to worry about it anymore.[/QUOTE]
yups,,for a first time the progress still there,,but after I'm trying to root a phone using vroot (via pc) and kingroot,specially by vroot cause this process makes turbo reboot a couple time (with a failed result :silly,.now on the second time on wipe cache,the progress is gone ( it's a temporary right?it's will coming again on a mysterius time :silly i'm use Gsm/Edge for a connectivity to make a slow downloading update progress when is coming back
.
a money problems for this time to buy that license

I, too, would probably resist unlocking that particular device, since the screen is so cracked up... if you replace the phone, you'd have to get another Sunshine license for the new device.
Anyway, back to the original point, I recall on my old GalaxyS3, VZ was pushing an update that only allowed you to postpone it for some specific amount of time and/or it had a timer for the "we're going to start installing" popup, after which it would force-install. Based on that, I wouldn't be surprised to hear VZ is forcing updates, especially on an unattended phone...

There may be hope...
http://forum.xda-developers.com/droid-turbo/general/sunshine-bootloader-unlock-su4tl-49-t3445523

while collecting a money,i'm try freezing updater using adguard.apk (non root) and the result for a last two days,the update progress is gone (I don't know if that's a result from a adguard method)..

The old user of my phone said that. The .49 update was made automatically, with no Yes/No options, just updated.

I think it might be that if you don't interact with the prompt it will update your phone after a certain amount of time. When the update first rolled out I would always postpone it, telling it to remind me at 12AM cause that's when I usually go to bed. However one day, after setting it to remind me at 12, I fell asleep earlier and didn't see the prompt. The next morning, surprise, surprise, it was updated to .49.

Good news!
Sunshine will now unlock bootloader on Verizon SUTL-49 on the Droid Turbo XT1254:
http://forum.xda-developers.com/showpost.php?p=68384014&postcount=21
jcase said:
We just released it, 3.4.6 will unlock SunShine
Sometimes stars align and a bug becomes apparent, one that we can use.
Click to expand...
Click to collapse

ChazzMatt said:
Good news!
Sunshine will now unlock bootloader on Verizon SUTL-49 on the Droid Turbo XT1254:
http://forum.xda-developers.com/showpost.php?p=68384014&postcount=21
Click to expand...
Click to collapse
It is a great news for a lot of people.
Good work by Sunshine team.

In the future with any phone. If you see a update is about to happen, plug your phone to your computer, go to root of storage, and delete the download.. Hell I do this all the time... You can't miss it, it will be the only white looking item there..

Smart Lock Settings Disappeared?

I am running an XZ1 Compact US version stock and locked bootloader. I am on the 47.1.A.12.205 firmware and when I go to smart Lock in settings it is blank. Has anyone else had this issue?
Trying to upload screenshots but cannot currently.

Milly7 said:
I am running an XZ1 Compact US version stock and locked bootloader. I am on the 47.1.A.12.205 firmware and when I go to smart Lock in settings it is blank. Has anyone else had this issue?
Trying to upload screenshots but cannot currently.
Click to expand...
Click to collapse
Apparently the smartlock feature has been fixed in the latest firmware update.
But if you want to see the page before you update, open settings\lock screen & security, scroll to the bottom and disable smart lock (google) under trust agents, reboot the phone, go back to trust agents, enable smart lock (google), now go back to the smart lock settings and they will be visable.

Latest firmware has not fixed the issue, at least not for me. Smart lock settings still are blank after every reboot. I still have to use the trust agent trick and reboot again.

htc 10, 7.1.2 LOS ROM, same issue here.
after trying everything mentioned, nothing worked.
so I downloaded a newer google play services via apkmirror
it actually froze the device when trying to enter smart lock... thus I went to apps and uninstalled back to the previous version.
bingo bango we have smart lock settings.
worth a try, you lose no data, and is quicker than clearing cache

andybones said:
htc 10, 7.1.2 LOS ROM, same issue here.
after trying everything mentioned, nothing worked.
so I downloaded a newer google play services via apkmirror
it actually froze the device when trying to enter smart lock... thus I went to apps and uninstalled back to the previous version.
bingo bango we have smart lock settings.
worth a try, you lose no data, and is quicker than clearing cache
Click to expand...
Click to collapse
U should wait and see if it lasts...
We already know how to make it appear again. The problem is that after a few days, it goes back empty again.

Dany XP said:
U should wait and see if it lasts...
We already know how to make it appear again. The problem is that after a few days, it goes back empty again.
Click to expand...
Click to collapse
I've been checking it multiple times, I'll report in a few days. This was just something that worked for me and shared. :good:
. Also different phones, but where's the harm in trying to help?

andybones said:
I've been checking it multiple times, I'll report in a few days. This was just something that worked for me and shared. :good:
. Also different phones, but where's the harm in trying to help?
Click to expand...
Click to collapse
Updates?

Dany XP said:
Updates?
Click to expand...
Click to collapse
Smart lock is broken. It holds 'trusted devices' for a couple of days, sometimes only hours. It then resets itself and goes back to a blank page. Google don't seem to be interested in fixing it and although Sony keep up with the security updates, it's not covered by that. Don't hold your breath fir a fix anytime soon.

Didgesteve said:
Smart lock is broken. It holds 'trusted devices' for a couple of days, sometimes only hours. It then resets itself and goes back to a blank page. Google don't seem to be interested in fixing it and although Sony keep up with the security updates, it's not covered by that. Don't hold your breath fir a fix anytime soon.
Click to expand...
Click to collapse
I was asking to andybones, he was trying a new Google play services, as u can read above...

Dany XP said:
I was asking to andybones, he was trying a new Google play services, as u can read above...
Click to expand...
Click to collapse
As I said, I wouldn't hold your breath. The official Google forum still has no fix.

Dany XP said:
Updates?
Click to expand...
Click to collapse
Hey, sorry for not posting sooner, totally forgot.
I hadn't been checking it, but I only use the on body detection. Is the issue that it is blank AND the services stop working, or is it the blank page problem only?
Onbody detection has been working for me since last posting but as mentioned, forgot to keep checking for blank page. Right now I checked and it isn't blank, however, I do flash gapps relatively often to update the apps. I last did this 2 days ago and I'm thinking that is why it isn't blank right now, but I do feel this is a Google issue as it's on multiple devices and my "method" was just another temp. way around the issue.
I will keep checking daily and post again, (I'll try not to forget again) but I do feel it will be blank soon. I wish we could find a permanent solution, but seems that is on Google.
Didn't mean to stir anything up in the thread here, I was just posting what my phone behavior was.
I'll turn on trusted places and see if that continues to work like Onbody has.

I've been checking multiple times a day since my last posting.
So far it hasn't disappeared, but maybe it has something to do with rebooting?
Clearly I don't reboot often. :laugh:

Well... At least Android Pie fixed this issue... It was about time.

Tab a (2017) force oem unlock

I purchased my first Samsung tablet today after a long, loving relationship with Asus Transformers (wanting something smaller). To my surprise OEM Unlocking was not available in Dev Mode. Having not owned a Samsung device since my S5 I searched high and low on Google and nothing worked. Tons of suggestions for S8's/9's but nothing for my new little SM-T380. I tried variations of everything I found and when none of them worked, started back at the top of the list. I FINALLY GOT LUCKY.
TL;DR - Today's date is 12/1/2018, time was 9:32pm (central).
I toggled my date/time to manual.
I manually set my date to 11/1/17. (YES, ONE YEAR AND ONE MONTH EARLIER)
Before wifi had time to reconnect after the date change I manually checked for updates and it errored out.
Without pressing anything else, I held the power button and restarted.
After restart I checked to see if OEM Unlocking was there and it wasn't.
I then adjusted the date back farther to a random interval. (Ended up being 03/1/17)
Manually check for updates again.
Selected dev options on the left again and OEM Unlocking finally appeared!!!!!1
Notes:
SM-T380
7.1.1
ARB3 build

B1G7r33! said:
I purchased my first Samsung tablet today after a long, loving relationship with Asus Transformers (wanting something smaller). To my surprise OEM Unlocking was not available in Dev Mode. Having not owned a Samsung device since my S5 I searched high and low on Google and nothing worked. Tons of suggestions for S8's/9's but nothing for my new little SM-T380. I tried variations of everything I found and when none of them worked, started back at the top of the list. I FINALLY GOT LUCKY.
TL;DR - Today's date is 12/1/2018, time was 9:32pm (central).
I toggled my date/time to manual.
I manually set my date to 11/1/17. (YES, ONE YEAR AND ONE MONTH EARLIER)
Before wifi had time to reconnect after the date change I manually checked for updates and it errored out.
Without pressing anything else, I held the power button and restarted.
After restart I checked to see if OEM Unlocking was there and it wasn't.
I then adjusted the date back farther to a random interval. (Ended up being 03/1/17)
Manually check for updates again.
Selected dev options on the left again and OEM Unlocking finally appeared!!!!!1
Notes:
SM-T380
7.1.1
ARB3 build
Click to expand...
Click to collapse
What's the REAL difference between what you did today and what we did days ago.? Is the same thing we came up with 3 days ago.. Just your version of the same thing..

Three days ago?

This didn't work for me. Neither have any of the other similar date-spoofing methods people have suggested or linked to on this forum. I'd be happy to be wrong, but there doesn't seem to be a legitimate way to trick this tablet into letting you bypass the 7 day wait for OEM Unlock to appear.
@B1G7r33!, if your method actually works, can you replicate the process and prove it? Can you wipe your data, flash back to stock firmware, go to Settings>About tablet>Status, and take a screenshot that shows the "Up time" of the tablet, go through your suggested date-spoofing method, then if OEM Unlock appears, take another screenshot of your tablet's up time, and one screenshot of your developer options menu.
I'm not calling you a liar, it's just that this and similar methods haven't worked for me and haven't been confirmed as working by anyone else yet. If it actually works, then great, but it's not working for me, so I'd like to pinpoint the problem and solve it.

B1G7r33! said:
Three days ago?
Click to expand...
Click to collapse
actually starting on 14th November 2018, 07:17 PM and ending about 4 days ago.. with ptballers solution.
post 118 was the beginnings of it on the thread: https://forum.xda-developers.com/ga...10-02-2018-t3747564/post78159074#post78159074
but even THAT came from earlier works that weren't detailed enough and reconstructed.
the builds seem to be way different here in the solution, i had luck with what we came up with but have only done that once so far.
I am using build NMF26X.T380DXU1ARB3 myself, what about you?
we need to figure out what ptballer is using and everyone else too as we confirm stuff so we know what to do with tablets based upon builds.
seems there is no single solution yet, and that's what we really need too keep confusion cut down to a minimum.
---------- Post added at 06:16 PM ---------- Previous post was at 06:12 PM ----------
Evul1 said:
This didn't work for me. Neither have any of the other similar date-spoofing methods people have suggested or linked to on this forum. I'd be happy to be wrong, but there doesn't seem to be a legitimate way to trick this tablet into letting you bypass the 7 day wait for OEM Unlock to appear.
@B1G7r33!, if your method actually works, can you replicate the process and prove it? Can you wipe your data, flash back to stock firmware, go to Settings>About tablet>Status, and take a screenshot that shows the "Up time" of the tablet, go through your suggested date-spoofing method, then if OEM Unlock appears, take another screenshot of your tablet's up time, and one screenshot of your developer options menu.
I'm not calling you a liar, it's just that this and similar methods haven't worked for me and haven't been confirmed as working by anyone else yet. If it actually works, then great, but it's not working for me, so I'd like to pinpoint the problem and solve it.
Click to expand...
Click to collapse
did you clear out your storage cache after changing the date and then turn on developer options?
what build are you working with btw.

Trying this on round two after root yielded no results. I also tried the clear cache method from your post I found which has a MUCH more consistent process to follow and still got nothing.
Perhaps starting from the bottom would be beneficial here.
Flash stock with odin --> find method that works --> add to root process.
It adds two more steps but that seems like a small price for consistency.
This is f***ing infuriating.
7r33

capriorn1971ad said:
did you clear out your storage cache after changing the date and then turn on developer options?
what build are you working with btw.
Click to expand...
Click to collapse
Yes, I tried that as well and it didn't work. Are you suggesting that this has worked for you? If so, can you reset your tablet right now and try it again to confirm?
I'm using the same build you are using, NMF26X.T380DXU1ARB3

Evul1 said:
Yes, I tried that as well and it didn't work. Are you suggesting that this has worked for you? If so, can you reset your tablet right now and try it again to confirm?
I'm using the same build you are using, NMF26X.T380DXU1ARB3
Click to expand...
Click to collapse
thats quite a bit of work to do, but yes it worked for me.
I was planning on writing a guide on rooting this and what to do if and when it fails in laymans terms and utilizing this, but if it isn't working for everyone.. if it isn't the cache then what is causing it to show for some and not others?
to do the guide i was going to start from a failed installation so i could write part 2 first and finish with part 1 (the actual initial rooting), which would require me to reset the tablet but if this isn't working right.. then i need to hold off on that idea.
maybe i should just do it and spend my day tearing around on that, sounds fun and all but i have to go to Burbank tomorrow to sign up at Central Casting (they are actually looking for someone like me right now, i am going with inside information) and it will be an all day endeavor, tuesday would be much better for me in truth, that allows me to use that tablet while i wait, and i will have hours to wait, but of course with my luck they will call me wednesday and null and void that.

B1G7r33! said:
Trying this on round two after root yielded no results. I also tried the clear cache method from your post I found which has a MUCH more consistent process to follow and still got nothing.
Perhaps starting from the bottom would be beneficial here.
Flash stock with odin --> find method that works --> add to root process.
It adds two more steps but that seems like a small price for consistency.
This is f***ing infuriating.
7r33
Click to expand...
Click to collapse
when you flash stock, restart the device and set the date back 2 months, then do a factory reset AFTER that and it will work.
after rooting it DO NOT reboot it until the OEM unlock shows up again, you can't rely on a method to bypass the second 7 days that requires rebooting, it null and voids the rooting by doing such.
this tablet is awefully touchy, i lost root 2 1/2 weeks after rooting and being able to reboot having OEM unlock showing and all.. but i didn't set up magiskhide..
don't know how the tablet detected it and figured it out..
yes it is infuriating, least you have company to work on it with..

capriorn1971ad said:
thats quite a bit of work to do, but yes it worked for me.
I was planning on writing a guide on rooting this and what to do if and when it fails in laymans terms and utilizing this, but if it isn't working for everyone.. if it isn't the cache then what is causing it to show for some and not others?
to do the guide i was going to start from a failed installation so i could write part 2 first and finish with part 1 (the actual initial rooting), which would require me to reset the tablet but if this isn't working right.. then i need to hold off on that idea.
maybe i should just do it and spend my day tearing around on that, sounds fun and all but i have to go to Burbank tomorrow to sign up at Central Casting (they are actually looking for someone like me right now, i am going with inside information) and it will be an all day endeavor, tuesday would be much better for me in truth, that allows me to use that tablet while i wait, and i will have hours to wait, but of course with my luck they will call me wednesday and null and void that.
Click to expand...
Click to collapse
It shouldn't be that much work at all if your method to get OEM Unlock to display actually works, as your bootloader will then be unlocked and you can immediately re-root, re-flash TWRP, and restore a nandroid backup. Rooting this tablet [flashing TWRP and su and/or magisk and/or a nandroid image] is actually quite simple and can be done in 5 minutes once you have OEM Unlock displayed.
You certainly wouldn't need a whole day just to try this. But I understand. Samsung's security nonsense makes the initial root of this tablet rather fragile if you don't know all the potential roadblocks beforehand. And a comprehensive root guide that explains all of this would certainly help people looking to root this tablet, so I don't want to rush you.

capriorn1971ad said:
when you flash stock, restart the device and set the date back 2 months, then do a factory reset AFTER that and it will work.
after rooting it DO NOT reboot it until the OEM unlock shows up again, you can't rely on a method to bypass the second 7 days that requires rebooting, it null and voids the rooting by doing such.
this tablet is awefully touchy, i lost root 2 1/2 weeks after rooting and being able to reboot having OEM unlock showing and all.. but i didn't set up magiskhide..
don't know how the tablet detected it and figured it out..
yes it is infuriating, least you have company to work on it with..
Click to expand...
Click to collapse
I found out the reboot after root no-no the hard way, lol.
After playing with it all day today, I think you're on the right path with it being application based. If we could log which run before and after, the chances of finding it and being able to adb uninstall/disable would be significantly increased.
So what can be used to low-level log WITHOUT root?

B1G7r33! said:
I found out the reboot after root no-no the hard way, lol.
After playing with it all day today, I think you're on the right path with it being application based. If we could log which run before and after, the chances of finding it and being able to adb uninstall/disable would be significantly increased.
So what can be used to low-level log WITHOUT root?
Click to expand...
Click to collapse
don't think we can really.
trial and error..
thought i was on the right path earlier, but if it didn't work for you then it isn't the solution, cause the solution will work for everyone.
has to be some small thing were overlooking i would assume.
I worked for Metricom through Verso Technologies back in the late 90's, the first coast to coast wireless provider, had dealings with the big wigs and all, but they always opted for less security and more accessibility in most everything pertaining to networking, always afraid to give up backdoors.
i need to go back to what you said too and see what slight differences there are, did you have any luck this time around? was it repeatable?
sucks to know i am going to have to root to cause a failure to try to bypass and root again only to cause a second failure to verify, and to get it right it is going to take that really, the bypass has to be repeatable, i think setting the date back before the systems restore is key to it, but i could be wrong.
if you would lose root and be able to get it pass the first 7 days OEM unlock then your good, because even if you can't get the second, and something goes wrong to where you need it, your gonna have to wipe anyways, which means you just wipe, set date back and then do the factory reset, not being able to reboot afterwards until the OEM unlock appears and not being able to advance it through the last 7 days means little so long as the root is good and right, funny thing really, took me a while to realize that, there is no real need to rush the second 7 days, only the first 7, but it would be nice to be able to reboot it again afterwards, the same day, and not have to worry about it anymore, but like i said earlier, i got detected somehow and lost root still., wish i knew how.
that's alot of my problem though, i do things and try to document them afterwards rather than as, and i am not 20 years old anymore with a mind like a razor, it's just a serrated steak knife now at almost 50, wish i wasn't like that, because i lose bits and pieces as i go.

so if my tablet auto updates to Oreo 8.1 ... then i'm SOL huh?

Random reboots and bootloops

Once and and while my Pixel 5 reboots and gets stuck in a bootloop. It happens while I listen to music with YouTube Music on a bluetooth ear phones or search for updates on the Play Store or nothing at all. I have no idea what is causing this.
I suspect one app called ProCall Mobile but I can't really test for two reasons: 1st it happens to randomly, weeks without one, than two in a row, than nothing for a month, or for few days, 2nd I need the app for my job and can't just remove it for testing.
I'm really annoyed by this, I also can't reset the phone because of reasons. Any ideas how can I narrow it down?

Sounds like something is causing a kernel panic, and it's hard to say what. The best thing I could really recommend is a complete factory reflash, but that requires an unlocked bootloader. I believe there may be a way to use ADB and USB Debugging to get a log dump, but I have no idea how to do that or how to read it.

V0latyle said:
Sounds like something is causing a kernel panic, and it's hard to say what. The best thing I could really recommend is a complete factory reflash, but that requires an unlocked bootloader. I believe there may be a way to use ADB and USB Debugging to get a log dump, but I have no idea how to do that or how to read it.
Click to expand...
Click to collapse
I fear you are right. I think I should set aside a few hours on the weekend to do that.

tehabe said:
need the app for my job and can't just remove it for testing.
Click to expand...
Click to collapse
Nope. If it's your phone, you don't have to keep any app on it. I have never experienced bootlooping or forced reboot on P5. Ask them for a work phone or tablet. It's not like old phones are expensive.
tehabe said:
I'm really annoyed by this, I also can't reset the phone because of reasons. Any ideas how can I narrow it down?
Click to expand...
Click to collapse
Also nope. You can back the entire phone up on google, data reset and reinstall everything.
Try force stop and clear cache in app.
Uninstall reinstall app.
Remove all unused apps.
Check Battery Usage
Go to Dev Options and turn on System Tracing and other debuggin features. I highly doubt you will be able to figure it out from there, but it may help others.