Auto start apps on reboot before unlocked? - Google Pixel 2 XL Questions & Answers

This may be just an Oreo thing or maybe pixel specific but despite a ton of searching I can't find anything helpful.
When the phone is rebooted, something I do daily, it won't launch any user apps until it's unlocked.
So if I reboot and don't stay by the phone to unlock it things like slack, phoneweaver, nine, and a handful of other important apps won't start. In turn if it was close to a scheduled profile change in phoneweaver it won't work. Or if a slack message comes in it won't to the phone. Nova doesn't fill in widgets. Etc.
This is a minor headache but still annoying. Hoping someone may know why? My gut is that despite not having multiple users set on the phone Oreo doesn't load apps until you officially "login" by unlocking.
Something it would be nice to work around without compromising security ...
Appreciate anything you all may have.
_tsp

I just noticed this on my Google Pixel 2! What the hell Google? No apps auto-start until after the first unlock. Is this an Oreo or Pixel specific thing?

Did either of you two find a solution to this?

Darke5tShad0w said:
Did either of you two find a solution to this?
Click to expand...
Click to collapse
No, I think it has to do with the data partition needing to be decrypted by unlocking before anything actually starts up.

It also does it on my Xiami MI 9.
I have not activated data encryption. In my opinion it is wrong that no service starts.
For example, the "Find my phone" would be good if it always started regardless of everything.
tspnews said:
This may be just an Oreo thing or maybe pixel specific but despite a ton of searching I can't find anything helpful.
When the phone is rebooted, something I do daily, it won't launch any user apps until it's unlocked.
So if I reboot and don't stay by the phone to unlock it things like slack, phoneweaver, nine, and a handful of other important apps won't start. In turn if it was close to a scheduled profile change in phoneweaver it won't work. Or if a slack message comes in it won't to the phone. Nova doesn't fill in widgets. Etc.
This is a minor headache but still annoying. Hoping someone may know why? My gut is that despite not having multiple users set on the phone Oreo doesn't load apps until you officially "login" by unlocking.
Something it would be nice to work around without compromising security ...
Appreciate anything you all may have.
_tsp
Click to expand...
Click to collapse

Related

Can't unlock phone on boot

Hi all,
bit of an emergency here. I am running rooted Chroma rom, just went into twrp to backup my EPS, and upon reboot it is saying I need to enter my password. I have done this several times. Now, it keeps saying the password is incorrect, and after the 5th time, there is no option to reset it! Help please!! Don't feel like wiping my phone again...
greves1 said:
Hi all,
bit of an emergency here. I am running rooted Chroma rom, just went into twrp to backup my EPS, and upon reboot it is saying I need to enter my password. I have done this several times. Now, it keeps saying the password is incorrect, and after the 5th time, there is no option to reset it! Help please!! Don't feel like wiping my phone again...
Click to expand...
Click to collapse
You can search that but might as wipe in the meantime. Get yourself a working phone.
bobby janow said:
You can search that but might as wipe in the meantime. Get yourself a working phone.
Click to expand...
Click to collapse
Thanks for the reply. Going through the post-wipe setup now. Grrrr. It's just that I entered the password a bunch of times, and it always worked. Just on reboot from recovery it didnt. Now I'm afraid to go back into twrp...
Anyone know if this could be caused by some android security feature that doesnt like systemless root, xposed, etc.
greves1 said:
Hi all,
bit of an emergency here. I am running rooted Chroma rom, just went into twrp to backup my EPS, and upon reboot it is saying I need to enter my password. I have done this several times. Now, it keeps saying the password is incorrect, and after the 5th time, there is no option to reset it! Help please!! Don't feel like wiping my phone again...
Click to expand...
Click to collapse
I assume this is the same problem as the Nexus 6P. You need to disable the security before making a TWRP backup. The fix is:
After restoring the nandroid, boot into twrp and then delete /data/sytem/locksettings.db. If that doesn't fix it, delete the locksettings.db-shm and locksettings.db-wal in the same location. If that doesn't fix it either, delete gatekeeper.password.key and gatekeeper.pattern.key in the same location.
Click to expand...
Click to collapse
KennyG123 said:
I assume this is the same problem as the Nexus 6P. You need to disable the security before making a TWRP backup. The fix is:
Click to expand...
Click to collapse
Thanks for this fix. I'll keep it in mind next time. My broader question is now about security in general, since there seems to be a way to remove security from our roms?? For example, if someone got ahold of your phone, couldnt they just follow these steps to get in? Is this just a side-effect of unlocking the phone that is unavoidable? If I'm missing something about how to maintain security in the unlocked/rooted environment, please let me know. I've looked around but I haven't found any great guides for best practices regarding nandroids/security, etc. Thanks all!
greves1 said:
Thanks for this fix. I'll keep it in mind next time. My broader question is now about security in general, since there seems to be a way to remove security from our roms?? For example, if someone got ahold of your phone, couldnt they just follow these steps to get in? Is this just a side-effect of unlocking the phone that is unavoidable? If I'm missing something about how to maintain security in the unlocked/rooted environment, please let me know. I've looked around but I haven't found any great guides for best practices regarding nandroids/security, etc. Thanks all!
Click to expand...
Click to collapse
Rooting is in itself the biggest security risk. This is why carriers are working with manufacturers to make many phones fully locked and unrootable. Our main security expert Jcase does not use a rooted phone. He recommends if you need to root, go ahead, make the changes you want, then quickly unroot. So sure, if someone stole your phone they could follow that procedure to get into it. They could also just force a fresh stock version on it to wipe everything. Security and locks are meant to keep out honest people and slow down the dishonest.
KennyG123 said:
Rooting is in itself the biggest security risk. This is why carriers are working with manufacturers to make many phones fully locked and unrootable. Our main security expert Jcase does not use a rooted phone. He recommends if you need to root, go ahead, make the changes you want, then quickly unroot. So sure, if someone stole your phone they could follow that procedure to get into it. They could also just force a fresh stock version on it to wipe everything. Security and locks are meant to keep out honest people and slow down the dishonest.
Click to expand...
Click to collapse
Just so I'm clear, the only thing keeping a stock phone safe is that when its locked, it can't be unlocked/rooted because the option to allow oem unlocking/adb connections are not (or should not be) checked in the developer options, is that correct? From what you're saying, as long as those two boxes are checked, there is essentially nothing stopping someone from wiping out your password and getting into your device. I'd love to run unrooted, but would adaway still have an effect? I'm thinking that the definitions are already applied, so maybe it would work unrooted. But cf.lumen, which I love and can't find the same functionality anywhere else, seems to always "enable interactive shell" on boot. Would this work unrooted? But again, as long so you're doing all this stuff, you can't lock your bootloader again, can you? Or can you lock it on a stock rom with the kind of modifications I'm talking about. I read that locking bootloader while having a custom rom loaded can cause a brick, although I'm not quite sure why. Couldn't you just always get into fastboot to unlock it again?
greves1 said:
Just so I'm clear, the only thing keeping a stock phone safe is that when its locked, it can't be unlocked/rooted because the option to allow oem unlocking/adb connections are not (or should not be) checked in the developer options, is that correct? From what you're saying, as long as those two boxes are checked, there is essentially nothing stopping someone from wiping out your password and getting into your device. I'd love to run unrooted, but would adaway still have an effect? I'm thinking that the definitions are already applied, so maybe it would work unrooted. But cf.lumen, which I love and can't find the same functionality anywhere else, seems to always "enable interactive shell" on boot. Would this work unrooted? But again, as long so you're doing all this stuff, you can't lock your bootloader again, can you? Or can you lock it on a stock rom with the kind of modifications I'm talking about. I read that locking bootloader while having a custom rom loaded can cause a brick, although I'm not quite sure why. Couldn't you just always get into fastboot to unlock it again?
Click to expand...
Click to collapse
Pfew...so many questions...there are always vulnerabilities out there that hackers can find..like Stagefright...but a rooted phone is the most vulnerable. So having a phone with a locked bootloader and unrooted is the best security...still not guaranteed against every possible thing. But it is the best...now what are you trying to protect? Your data...or someone being able to wipe and use the phone as their own? All you can do really is try to protect from a phone being hacked remotely...and a rooted phone is like leaving the safe door open. But if someone steals your phone, there are always nefarious ways to make it usable.
KennyG123 said:
Pfew...so many questions...there are always vulnerabilities out there that hackers can find..like Stagefright...but a rooted phone is the most vulnerable. So having a phone with a locked bootloader and unrooted is the best security...still not guaranteed against every possible thing. But it is the best...now what are you trying to protect? Your data...or someone being able to wipe and use the phone as their own? All you can do really is try to protect from a phone being hacked remotely...and a rooted phone is like leaving the safe door open. But if someone steals your phone, there are always nefarious ways to make it usable.
Click to expand...
Click to collapse
Yeah, sorry for the wall of questions. I am just trying to wrap my head around some of these issues. At the end of the day, I don't really keep sensitive data on the phone, although it would not be good if a bad actor got into my gmail, for instance. I suppose I should migrate the last of my sensitive accounts to a secondary email, so no password resets could be initiated from a stolen phone. It's always a tradeoff between convenience and security I know. It's also a little worrysome that simply unlocking the phone activates it for androidpay. An unlocked phone stolen out of someone's hand is essentially the same as stealing all the credit cards in their wallet. It would be nice if android pay allowed an additional fingreprint/pin/password to make the transaction. Anyway, I'm now taking my own thread way off topic. Thanks for the insights though.
greves1 said:
Yeah, sorry for the wall of questions. I am just trying to wrap my head around some of these issues. At the end of the day, I don't really keep sensitive data on the phone, although it would not be good if a bad actor got into my gmail, for instance. I suppose I should migrate the last of my sensitive accounts to a secondary email, so no password resets could be initiated from a stolen phone. It's always a tradeoff between convenience and security I know. It's also a little worrysome that simply unlocking the phone activates it for androidpay. An unlocked phone stolen out of someone's hand is essentially the same as stealing all the credit cards in their wallet. It would be nice if android pay allowed an additional fingreprint/pin/password to make the transaction. Anyway, I'm now taking my own thread way off topic. Thanks for the insights though.
Click to expand...
Click to collapse
For most phones that have fingerprint security Android Pay can be set up that way. I won't use it anyway because it would be crazy to hand a waiter your unlocked phone, or to have to follow him to the register. It would only be useful to me in the supermarket but I am carrying a credit card anyway. But that is one thing people forget, rooting a phone means removing the main security.
KennyG123 said:
For most phones that have fingerprint security Android Pay can be set up that way. I won't use it anyway because it would be crazy to hand a waiter your unlocked phone, or to have to follow him to the register. It would only be useful to me in the supermarket but I am carrying a credit card anyway. But that is one thing people forget, rooting a phone means removing the main security.
Click to expand...
Click to collapse
N5X and android pay seems to tell me to just "unlock your phone" and hold it close to the reader. No need for an additional fingerprint. And no option to require this in settings...
greves1 said:
N5X and android pay seems to tell me to just "unlock your phone" and hold it close to the reader. No need for an additional fingerprint. And no option to require this in settings...
Click to expand...
Click to collapse
Yes, that should get you to the authorization screen and then if you have fingerprint set up should ask you for the fingerprint to authorize. Android Pay also now works on phones without fingerprint sensors so that is why they provide those simple instructions. Final authorization instructions will appear on your screen.
KennyG123 said:
Yes, that should get you to the authorization screen and then if you have fingerprint set up should ask you for the fingerprint to authorize. Android Pay also now works on phones without fingerprint sensors so that is why they provide those simple instructions. Final authorization instructions will appear on your screen.
Click to expand...
Click to collapse
Ah, great to know. Thanks.
greves1 said:
Ah, great to know. Thanks.
Click to expand...
Click to collapse
Unfortunately I can't test that theory since I am on a custom ROM and also Xposed. But everything I read says it should utilize the fingerprint if available.
KennyG123 said:
Unfortunately I can't test that theory since I am on a custom ROM and also Xposed. But everything I read says it should utilize the fingerprint if available.
Click to expand...
Click to collapse
Real word use shows that android pay does not ask for an additional fingerprint at the time of use. It's just as the instructions say, as long as your phone is unlocked at the time it is held up to the scanner, androidpay will work. I kind of wish they allowed for the additional security of an at-scan fingerprint read, but oh well. I have yet to test if the password/pin can be removed by the methods discussed in this thread, and androidpay working after defeating this security. If it does, then this is obviously a major security vulnerability of having an unlocked phone and using androidpay at the same time. Probably not more dangerous in terms of protecting against CC thieves, since they can just swipe a card stolen from your wallet at a terminal, but you probably wouldn't want to keep too many cards on your phone. Again, I haven't tested this out, if a fingerprint is still required to get in after a password database defeat, but someone should do this test.
If you have your phone lost or stolen just cancel your cards as if it happened to your wallet. Simple no?

Strange "RootPA" app on my HTC 10. Is it a potential security issue?

Im using a HTC 10 (EU variant). Today i was scrolling through "Netguard" (if you dont know it, its an app to prevent other apps from internet access), since i configured it to show system apps it displays way more apps than the normal app overview in the settings. In there i found an app called "RootPA" and one called "root", which seems strange since i didnt unlock the bootloader or root on my own. The details in the RootPA entry say "com.gd.mobicore.pa", no idea if thats helpfull to determine the origin of this mysterious app.
Can you help me with this?
Did you Google it?
I did, but the results were not realy usefull. I found someone with a modded Galaxy S3 who deleted a RootPA on accident and broke stuff, but that ssems unrelated. Are there any things i could do to find out more about the app installed on my phone without root?
I cant say its something I've ever seen. If this person in the past removed it, and it broke stuff, that would suggest that it may have been a system app and he was rooted. From what I managed to find on google, it is part of a security suite (mobicore) used by networks to monitor what the state of the phone is, presumably incase something happens, and it was the user fault, and they know for a fact because they have logs of what the phone has done.
[ACCESS_NETWORK_STATE] Allows applications to access information about networks
[INTERNET] Allows applications to open network sockets. (i.e send information)
[READ_EXTERNAL_STORAGE] Allows an application to read from external storage.
[READ_PHONE_STATE] Allows read only access to phone state.
A friend of mine got his HTC 10 2 days ago, ill ask him to look for this app. Its unlikely we would have the same virus/whatever installed.
Edit: He just reseted his 10 (due to missing language options, but thats another topic), but still found "root" and "rootPA" on his phone, so its preinstalled (although i still dont understand whats its purpose).
RootPA is provides service for provisioning secure applications that run on ARM trustzone and t-base OS (formerly mobicore). It is preinstalled in some vendors Android devices (search for this string on the internet: htc-devices-to-incorporate-trustonic-t-base-tee), but mostly unused as far as I know. The source code of some versions is available on the Internet (e.g. on github /Faryaab/android_hardware_samsung_slsi_exynos5410/tree/master/mobicore/rootpa).
It has nothing to to with rooting or unrooting the device.
PA route is very dangerous I had some I have somebody who has hacked into my phone through this particular program so to speak I have a lot of issues right now with my phone trying to get them off of my phone and this seems to be the root cause or the start of it have anybody knows how I can clear my phone and my Ram from the Vicious hacker I appreciate it I'm tired of being watched and recorded everything I do
Illfidusoon12 said:
PA route is very dangerous I had some I have somebody who has hacked into my phone through this particular program so to speak I have a lot of issues right now with my phone trying to get them off of my phone and this seems to be the root cause or the start of it have anybody knows how I can clear my phone and my Ram from the Vicious hacker I appreciate it I'm tired of being watched and recorded everything I do
Click to expand...
Click to collapse
PA route..... .rootPA ......2 different things. Hacked ? Unlikely, I think some OCD is kicking in. Want to be clean? RUU the device and do not restore anything

Any one else notice our interesting tag along in our note 10+?

So, since I've got this over monster I've had a shocking number of issues. From sudden influx of crap followers online, people sending photos of some of those little people some people keep as pets.
But, it was probably a month in kept getting restarts that left my wall paper different, noticed key guard was in the running processes and Samsung wasn't able to give me much info at all.
Frequently my antivirus Would randomly flag some huge archive that would appear in Google vending folder and for some reason my weather app for my gear fit updated EVERYDAY
Today a series of unfortunate events and my phone did a factory reset shortly after a drop. I actually find that interesting because I don't know the drop or one of my...well call them gremlins. (Let's face it most of things i have attributed are probably just me going into PTSD blah blah blah... )
But today Turn process I did streamline to get Nic cards logging up and go and build to set up a good firewall get ad blockers going but I wanted to see what happened. And I go my weather app eventually.
And for some reason over in reddit they tend to think permissions like this are normal (I know Samsung's calculator is more than a calculator but mine once had almost every permission with about 800MB storage taken up.
So, This weather app seemed a little abnormal look up the IP address, looked up the company and, I looked furlough their partners for Samsung and Knox (didnt Find the one)
Just a quick assumption;
This module has the Hotspot 2.0 and REALLY likes its certificates. I noticed the option to share Your Wi-Fi with someone is always default toggle on.
If you scroll through the websites what we do you see that they are very proud that they have the edge one of the largest threat assessments for everybody when hop away from 1 of their servers , how many of them there are etc. And I Have this feeling that my device is actually just a nice little go between allowing others access to the internet while gathering their data points.
I can't actually post links but if you do their site plus this thing takes you right to the talk about their platform. Gove the data that goes through phones, that is good for anything from Cambridge analytica code level stealing countries to just figuring out how stable and great 5G is
/us/en/
what-we-do/intelligent-platform
I've seen the Address actually go by in my primary bp and add blocker but that 1 doesn't give me per app metrics so not sure what else goes to them.
Also, suddenly I think I know at least partially why they don't want flashed ROMS(?), at least yet.
I'd actually really like to know if anyone else, specifically related to 5G sees these also. Given the timing of that release device and anal FMRi weather app there. And for some reason even though I use a little cheaper company gives me unlimited data they have swapped my network several times between bigger company the smaller company. Its same towers and stuff usually so no big deal but, doesn't normally do that. (Have noticed that actually from the Galaxy store I see that quite often, but the "same" download from play store different version number less permissions)
(By the way hello this is the 1st device actually looking to rooting, prior the risk of that access to someone else was too much. Thanks for letting me join the community, I do hope I catch on quick ans don't drive any one too crazy)
(I tried to add in pictures of the weather app permissions and everything but can't post pictures either)
A drop shouldn't cause a factory reset... if it was caused by software you have an apk(s) that are trashware.
A 3rd party launcher put mine in a boot loop... twice.
If you did a recent firmware update it may have corrupted that load, reload as you did.
A virus or trojan are suspect as well. Run Malwarebytes and Trojan scanner. Some malware may not always be detected.
If you suspect a virus after a reload be careful what you load and bring into the system including the on SD card and any backups. Start with the base load and add only apps from Playstore at first. Go from there if it runs ok. Be wary of updates, one at a time, look for issues as you progress.
Same with backup data... if it's there you'll need to isolate it or dump all the data.
Use a package disabler like PD MDM to block bloatware from running and to troubleshoot.
blackhawk said:
A 3rd party launcher put mine in a boot loop... twice.
If you did a recent firmware update it may have corrupted that load, reload as you did.
Click to expand...
Click to collapse
I was worried so, as I'd never seen it i just know these things actually include that hardware backed encryption. I had worries that I had knocked that loose and might have issues with it later. (Accelerometer is off bit it seems now)
I can say likely:
1. Third party lock screen with data wipe. Not highly reviewed but was but trashy. May have accidently in the tussle woke the screen with motion and performed a wipe.
2. Package disabled. I play with what I can get away with disabling. Some Knox stuff is bit touchy.
3. I'd managed to start process of adding a second secure folder on a secondary profile. It hadn't like it but stayed working.
Or combo 2 & 3 but lock screen most likely I'd say
HungryRobotics said:
I was worried so, as I'd never seen it i just know these things actually include that hardware backed encryption. I had worries that I had knocked that loose and might have issues with it later. (Accelerometer is off bit it seems now)
I can say likely:
1. Third party lock screen with data wipe. Not highly reviewed but was but trashy. May have accidently in the tussle woke the screen with motion and performed a wipe.
2. Package disabled. I play with what I can get away with disabling. Some Knox stuff is bit touchy.
3. I'd managed to start process of adding a second secure folder on a secondary profile. It hadn't like it but stayed working.
Or combo 2 & 3 but lock screen most likely I'd say
Click to expand...
Click to collapse
Get a good case like the Bolt. High G impacts can cause internal damage but usually not especially if in a case.
I don't use secure folder, encryption or any screen lock especially 3rd party. Any apk you give administrator rights to lock the phone can effectively trash your OS load in a heartbeat.
Have had passwords get corrupted (rare) before and gotten totally locked out on a laptop bios.
That machine is now useless.
On Androids you can reload to recover if all else fails but a reload takes a lot of work...

Question Help Desperately Needed - Random Reboots

So I posted about this previously but here's more info and a clearer summary
The Issue:
Phone randomly reboots about an average of once per day. Screen freezes, goes black, comes back on for 3 seconds still frozen, then proceeds to reboot. I've kept track and 100% of of the time this seems to happen when I'm typing. Initially I thought it was Textra, but it has happened in Snapchat, and Twitch whenever the google keyboard is up. Google sent a replacement phone and the issues persists, and I find it hard to believe that both phone would have the exact same hardware issue. Furthermore it very much seems like a software issue considering it ONLY happens when the google keyboard is up.
My hope is that someone might have encountered this and has a simple solution although I doubt it. Unfortunately since I don't have another phone, I have to wait to obtain one before I do a safe mode test. And even if I do it's not realistic for me to test it that way because I'd have to spend hours typing away just to try to get the issue to occur (since it's not frequent like every 5 minutes).
I'm suspecting some data or a setting is getting transferred over from my previous backup that's affecting google keyboard or something of the sort. My next step will be a factory reset, and then reinstalling everything bit by bit manually. Of course I have to link my google account, but I won't have it automatically restore the backup. If that doesn't help then I'm at a loss. At that point I'd probably pick up a cheap Pixel 2XL as my daily, and use my P6Pro in safe mode as much as I can to try to trigger the issue I guess?
The Phone:
Pixel 6 Pro
Not Rooted
November 5 Update
Set up done using my google account to restore all apps and settings, not cable
Remind me since I don't recall if it was brought up in your other thread about the issue, did you try Official Google Android Flash Tool yet?
Agree with edor, Android flash tool, flash both slots, start all over
roirraW edor ehT said:
Remind me since I don't recall if it was brought up in your other thread about the issue, did you try Official Google Android Flash Tool yet?
Click to expand...
Click to collapse
I have not tried this. What would this be used for?
ne0ns4l4m4nder said:
Agree with edor, Android flash tool, flash both slots, start all over
Click to expand...
Click to collapse
Not sure what that means sorry, can you elaborate?
MarkAnthony121 said:
I have not tried this. What would this be used for?
Click to expand...
Click to collapse
To wipe the phone and start back fresh.
MarkAnthony121 said:
Not sure what that means sorry, can you elaborate?
Click to expand...
Click to collapse
Just that. To start back fully fresh. Then if you do that take my advice from the other thread, don't restore backups from Google or anywhere, and initially only install your most critical apps. Once you determine you're not having the problem, install some more. Verify, repeat.
ne0ns4l4m4nder said:
Agree with edor, Android flash tool, flash both slots, start all over
Click to expand...
Click to collapse
Not sure what that means sorry, can you elaborate?
roirraW edor ehT said:
To wipe the phone and start back fresh.
Just that. To start back fully fresh. Then if you do that take my advice from the other thread, don't restore backups from Google or anywhere, and initially only install your most critical apps. Once you determine you're not having the problem, install some more. Verify, repeat.
Click to expand...
Click to collapse
Yes but I don't understand what "flash both slots" means. And wouldn't I get the same result by simply doing a factory reset and then proceeding with the method of installing everything manually and not from a backup? Why use the google flash tool vs factory reset?
MarkAnthony121 said:
Not sure what that means sorry, can you elaborate?
Yes but I don't understand what "flash both slots" means. And wouldn't I get the same result by simply doing a factory reset and then proceeding with the method of installing everything manually and not from a backup? Why use the google flash tool vs factory reset?
Click to expand...
Click to collapse
At this point, that's more information than you really need to know to try to fix your phone. I don't want to overcomplicate things. You can look at Google search results for "Pixel flash both slots" if you really want to go down that road right now.
Spoiler: Some of the details you're asking for, but you don't need right now
In short, starting with the Pixel 1 in 2016, they have two copies of almost everything (except only one copy of user data). On a Pixel, and another phone that employs dual slots, when you receive an OTA update, it updates the copy of Android that you're not currently running, then reboots into the one it just updated, and once rebooted it goes ahead and updates the copy that you're no longer running, so they're both now updated.
Not all OEMs use the dual partition strategy, which is frustrating. When I briefly had the Note 10+ before the P6P came out, I was amazed that Samsung still hasn't adopted the method. It beats the old style OTA method that Samsung still uses to this day as far as I know where it takes 15-20 minutes or more to run the update while your phone is unable to be used at all, and then even when it boots up the next time Android has to finish the job "optimizing" your apps for the new update. Dual partitions for Android save a lot of time when updating the phone.
In some manual flashing processes, you end up with one slot with a different copy of what you have in the other slot - and you don't want that. The slots are referred to as Slot A and Slot B.
I can go further into detail but you don't really need that to fix your phone.
All you need to know right now is Official Google Android Flash Tool.
If you haven't already tried the factory reset, et cetera, which we had recommended to you at least once in the other thread, then by all means, you can try that. But if you're going to try that, you might as well just use the Official Google Android Flash Tool and ensure you are 100% stock. Official Google Android Flash Tool has fixed a good dozen or two folks' issues (I haven't been keeping count) in these forums in the past 2+ months.
So if the factory resetting doesn't solve things then you'll still have to try Official Google Android Flash Tool to be closer to sure that you tried everything that you could. We had already suggested the Factory Reset to you in the other thread. Since you created a new thread, I figured you might be looking for information you hadn't been given yet.
So the short answer is because Official Google Android Flash Tool will do an even more complete job of putting your phone back to 100% stock, with a lot less doubt than a simple factory reset. Sure, a factory reset, in theory, should get you the same thing, but there are all sorts of circumstances where a factory reset won't. Something is wrong with your phone and we don't know what it is.
There's the Factory Reset idea and then there's the Official Google Android Flash Tool idea - either coupled with the staggered manual installation of apps until you narrow down if it was a particular app causing the issue. It doesn't matter which one you choose to try first. If you try just a Factory Reset, and things still go haywire, then you'll still have to try Official Google Android Flash Tool after that. It's your choice, now pick one and go forth and hopefully reboot no more.
Also, I wasn't going to mention this but I will now. Forums generally discourage users from creating multiple threads about the same issue or posting about the same issue in multiple threads. You can always update the OP (opening/first post) if you need to, and give an update as a reply to your existing thread.
MarkAnthony121 said:
So I posted about this previously but here's more info and a clearer summary
The Issue:
Phone randomly reboots about an average of once per day. Screen freezes, goes black, comes back on for 3 seconds still frozen, then proceeds to reboot. I've kept track and 100% of of the time this seems to happen when I'm typing. Initially I thought it was Textra, but it has happened in Snapchat, and Twitch whenever the google keyboard is up. Google sent a replacement phone and the issues persists, and I find it hard to believe that both phone would have the exact same hardware issue. Furthermore it very much seems like a software issue considering it ONLY happens when the google keyboard is up.
My hope is that someone might have encountered this and has a simple solution although I doubt it. Unfortunately since I don't have another phone, I have to wait to obtain one before I do a safe mode test. And even if I do it's not realistic for me to test it that way because I'd have to spend hours typing away just to try to get the issue to occur (since it's not frequent like every 5 minutes).
I'm suspecting some data or a setting is getting transferred over from my previous backup that's affecting google keyboard or something of the sort. My next step will be a factory reset, and then reinstalling everything bit by bit manually. Of course I have to link my google account, but I won't have it automatically restore the backup. If that doesn't help then I'm at a loss. At that point I'd probably pick up a cheap Pixel 2XL as my daily, and use my P6Pro in safe mode as much as I can to try to trigger the issue I guess?
The Phone:
Pixel 6 Pro
Not Rooted
November 5 Update
Set up done using my google account to restore all apps and settings, not cable
Click to expand...
Click to collapse
I've heard of freezing problems from others related to gboard. This would indeed appear to be a software flaw. I've never really used gboard since the first step for me was google-free AOSP, then put in my sim card and start using it (I don't like spyware).
Simplest solution for you would likely be to try a different soft keyboard. Personally, I would suggest finding one on f-droid rather than play store because open source.
For what it's worth, I've been using GBoard for 5+ years and have never had a problem.
96carboard said:
I've heard of freezing problems from others related to gboard. This would indeed appear to be a software flaw. I've never really used gboard since the first step for me was google-free AOSP, then put in my sim card and start using it (I don't like spyware).
Simplest solution for you would likely be to try a different soft keyboard. Personally, I would suggest finding one on f-droid rather than play store because open source.
Click to expand...
Click to collapse
I used to root back in the day and use a custom ROM. If I do that there's no automatic updates right? Have to reload a new ROM for updates?
MarkAnthony121 said:
I used to root back in the day and use a custom ROM. If I do that there's no automatic updates right? Have to reload a new ROM for updates?
Click to expand...
Click to collapse
Depends on the ROM. I believe GrapheneOS has OTA updates. I know some others over the years have had that, too. Certainly not most custom ROMs but some.
roirraW edor ehT said:
Depends on the ROM. I believe GrapheneOS has OTA updates. I know some others over the years have had that, too. Certainly not most custom ROMs but some.
Click to expand...
Click to collapse
Thanks for all the help. (sorry for posting twice, I tried to delete the other) And I did appreciate the extra info so that I understood WHY I needed to do it this way and how it all functions. Two final questions. On modern phones like this one, does running a custom rom really improve battery/performance much? It's already pretty snappy for me, so I feel if I don't care about customizability it's probably not worth the effort for minimal reward. And second question, will the flash tool give me the option to clear both slots ?
Oh and third, is it ok to link my google account, (to get my contacts and such) as long as I'm not restoring any backups from it?
MarkAnthony121 said:
Thanks for all the help. (sorry for posting twice, I tried to delete the other) And I did appreciate the extra info so that I understood WHY I needed to do it this way and how it all functions.
Click to expand...
Click to collapse
You're very welcome!
MarkAnthony121 said:
Two final questions. On modern phones like this one, does running a custom rom really improve battery/performance much?
Click to expand...
Click to collapse
In my opinion, no, but the object of some ROMs (like GrapheneOS) are more geared towards very much increased security and avoidance of all the Google data-collecting that goes on with everything Google, although you can use some or most Google apps with GrapheneOS if you choose.
I've never actually tried GrapheneOS, though - I've only kept up with the two threads about them because I was curious about it. To me, starting with my first Pixel (I never owned a Nexus device), I liked stock Android way better for my purposes.
But just as for a lot of phone-related subjects, the answer to this question is very subjective. What's right for me isn't right for everyone. Everyone's needs are different. The only way of knowing for sure is to try it. You might try something and very quickly say "to heck with that, I'm going back", or you might say "oh, I like this loads better". I'm not a betting man unless something is a near 100% chance, so it's really a toss-up whether you would like a different ROM or not.
Also, how I handle my battery works great for me - but it wouldn't for everyone. I don't charge the phone until it gets down to 25%, and I try not to let it get any lower than 25%. I only charge the phone up to 75% when I can. I never charge overnight, and I never quick charge. That 50% range of battery still lasts me about 24 hours. My Pixel 1 battery is in great shape because of this habit. My wife's, on the other hand, since she didn't do this - her battery on her old Pixel 1 is relatively shot.
MarkAnthony121 said:
It's already pretty snappy for me, so I feel if I don't care about customizability it's probably not worth the effort for minimal reward.
Click to expand...
Click to collapse
Sounds as if you already have made up your mind to me. I mean, that's how I feel, and I like using Google's services for the most part. I'm more a function over form person. While I don't want something downright fugly, I really don't care what things look like - only how they do what I want them to do. Yet again, "how they do what I want them to do" is very subjective. The Samsung Galaxy Note 10+ didn't do what my wife and I wanted it to do, but we were both spoiled on the Pixel 1 before that. We don't regret our choice to go back to Pixel via the 6 Pro. For others, the Samsung phones are what they need.
MarkAnthony121 said:
And second question, will the flash tool give me the option to clear both slots ?
Click to expand...
Click to collapse
You don't want to "clear" both slots, you want to flash both slots. In answer to your question, I don't think you'll have a choice via the site (or offline flashing the full factory image). In other words, both slots are going to get flashed whether you like it or not. You would have to go to extra efforts to *not* flash both slots. Hence yet another reason why you don't have to worry about that aspect.
Google's official methods would never flash only one slot by default. That would be just plain idiotic of them.
Before you ask, the reason I recommend the site rather than offline flashing of the full factory image is:
It's more user-friendly.
It has solved problems when manually flashing the full factory image has not for some others with particular problems.
MarkAnthony121 said:
Oh and third, is it ok to link my google account, (to get my contacts and such) as long as I'm not restoring any backups from it?
Click to expand...
Click to collapse
Yes, absolutely, although in some cases I've recommended going completely fresh and not even doing that, at least before testing long enough to see if you have the issue. You certainly could go without putting your Google account in, etc, but I don't feel that's warranted at this point. The only time I think you should do that, in this case, is if you do it the other way (with your Google account), and you still have the same problem right away (without installing any additional apps).
Just remember don't install any additional apps to start with, long enough to be sure that the problem isn't happening. I know it's a painful process - I've done this before on several devices for different reasons. Usually, the cause of issues becomes evident but it's possible it won't be completely obvious.
FYI, just putting your Google account in will, I believe, possibly still automatically restore your phone's most basic settings but I could be wrong about that. You could always try it without your account at first, use the phone in it's limited state for long enough to know there's no problem, and only then put your Google account in.

Question Hacked pixel 6

Can anyone help me carrier unlock my Verizon phone? My phone has been hacked and I hope being able to flash it will help me to get rid of whatever they have done to it. Can anyone tell me why I get this message when I reset my phone? Any help would be greatly appreciated
there is no carrier unlock for VZW models. if you can boot into recovery, sideload the OTA version that was last on your device.
What did you do that resulted in the phone being hacked? With the sectors being wiped that are shown in the images, it looks like you have provided total device access to something whilst having an unlocked bootloader or something similar. If you let us know what happened, it might help us to figure out what options you may still have.
But definitely see if you can do what @uicnren mentioned first.
Im not sure who or how they wiped anything. It happened one day after connecting to my girlfriends wifi. I got ahold of Verizon and they sent me a new phone and as soon as I started it the same thing happened to it also
How do I find what OTA version was used on my phone?
Nothing hacked here... this is an error when wiping the Secure Element (the trusted secure module).
(https://android-review.linaro.org/p...cure_element/1.0/SecureElementHalCallback.cpp line #66)
Are you initiating the wipe from the recovery? If so, that's likely the reason. If there is an account attached to the device, a wipe must first be initiated from within Android (Settings)
Woodruff87 said:
Im not sure who or how they wiped anything. It happened one day after connecting to my girlfriends wifi. I got ahold of Verizon and they sent me a new phone and as soon as I started it the same thing happened to it also
Click to expand...
Click to collapse
what symptoms were you seeing that made you think you were hacked?
Those errors are normal in Recovery Mode. I see them all the time, sometimes they don't appear, usually they do.
Did you remove your google accounts from settings, do a factory reset from the reset menu and lastly in recovery mode where you posted the screenshots from.
Your Account might be hacked but the phone is unlikely hacked. You would get a message at boot telling you that the device has been modified. With a locked bootloader its extremely unlikely (unless NSO Group is targeting you).
Woodruff87 said:
Can anyone help me carrier unlock my Verizon phone? My phone has been hacked and I hope being able to flash it will help me to get rid of whatever they have done to it. Can anyone tell me why I get this message when I reset my phone? Any help would be greatly appreciated
Click to expand...
Click to collapse
Did you unlock the bootloader? Have custom firmware/kernel installed?
A "hacker" wins nothing by resetting/wiping your phone. They want data, and that only works if the phone can turn on and works. This looks like a wipe/factory reset gone wrong, which spells user error or software error and less likely a "hacker" attack. Most hacks you will never notice. A hacker that makes you notice that something went wrong, is either an amateur or did it on purpose. Ergo, he wants you to know that something went wrong, which usually only happens in order to extort you. If there is no extortion, then an obvious act by a hacker is highly unlikely.
We need some more information. What firmware had you installed? What happened exactly when. Did you install any new apps recently? What did you do prior to something going wrong? All the information that could help us troubleshoot your issue.
You said your phone wiped itself a day after connecting to your girlfriends wifi, and that a replacement device that you got sent by your carrier, did the same. Did you check your Google account? Do you have two factor authentication activated? It sounds like your phone got wiped over wifi, which would require access to your Google account. It's just odd that you get errors, which normally shouldn't happen if someone would use the erase a lost Android device function.
It's also possible that your backup from your GAccount is simply corrupted (many people had issues with random reboots). You should try and set up your (replacement) phone anew without any backup, maybe that can fix your issue.
Beyond that Google account thing-y, anything else is highly unlikely. Even specialized companies have serious issues getting into a modern smartphone, lest alone an Android 12 phone with a Google Server grade Titan m2 chip. The newer the firmware, the less likely the chance that someone from the outside could get in, especially with a phone like a Pixel that isn't very common. Most security firms/govermental agencies can only abuse older, known security loopholes. It's more likely that very popular phones like a Samsung or IPhone are targets from "the bad guys", since there will be bigger payoff for breaking the security of those phones, since there is a greater pool of users to target. Most hacks I've witnessed weren't random, they were targeted. Ask yourself: Am I worth the trouble of getting hacked? Do you have anything of interest on your phone that would warrant an excessive use of resources? Managing to hack a Pixel is not only unlikely in terms of the security you need to breach, but also in terms of the potential payoff in relation to the necessary knowhow and resources. It's just "not worth it".
What you should do immediately, just in case, is secure your Google account. Change your password. Maybe even change your two-factor authentication, if you have one (sms is not secure, use a token generating software/device). Change the wifi password from your girlfriend and check the list of connected devices. make a list of these connected devices + history (find that in the rooter software) and check them against the devices you know of. Also check the list of connected devices to your GAccount. Use the option to log out ALL devices from your Google account, so only your device is connected.
Do any other people have access to your phone? Do any other people know your passwords? Does your girlfriend has access? Do any other people have biometric security saved on your phone? Do you trust your girlfriend completely?
Make sure you use a special, new password for your GAccount, never reuse old ones that you have used somewhere else. Also check your emails on https://haveibeenpwned.com/
Beyond that, if you are not doing already, use a password manager.
Woodruff87 said:
Im not sure who or how they wiped anything. It happened one day after connecting to my girlfriends wifi. I got ahold of Verizon and they sent me a new phone and as soon as I started it the same thing happened to it also
Click to expand...
Click to collapse
Wait a sec. Verizon sent you a new (refurbished probably but new nonetheless) phone and when you turned it on weren't you greeted with the startup menu? Am I missing something?
Morgrain said:
Did you unlock the bootloader? Have custom firmware/kernel installed?
A "hacker" wins nothing by resetting/wiping your phone. They want data, and that only works if the phone can turn on and works. This looks like a wipe/factory reset gone wrong, which spells user error or software error and less likely a "hacker" attack. Most hacks you will never notice. A hacker that makes you notice that something went wrong, is either an amateur or did it on purpose. Ergo, he wants you to know that something went wrong, which usually only happens in order to extort you. If there is no extortion, then an obvious act by a hacker is highly unlikely.
We need some more information. What firmware had you installed? What happened exactly when. Did you install any new apps recently? What did you do prior to something going wrong? All the information that could help us troubleshoot your issue.
You said your phone wiped itself a day after connecting to your girlfriends wifi, and that a replacement device that you got sent by your carrier, did the same. Did you check your Google account? Do you have two factor authentication activated? It sounds like your phone got wiped over wifi, which would require access to your Google account. It's just odd that you get errors, which normally shouldn't happen if someone would use the erase a lost Android device function.
It's also possible that your backup from your GAccount is simply corrupted (many people had issues with random reboots). You should try and set up your (replacement) phone anew without any backup, maybe that can fix your issue.
Beyond that Google account thing-y, anything else is highly unlikely. Even specialized companies have serious issues getting into a modern smartphone, lest alone an Android 12 phone with a Google Server grade Titan m2 chip. The newer the firmware, the less likely the chance that someone from the outside could get in, especially with a phone like a Pixel that isn't very common. Most security firms/govermental agencies can only abuse older, known security loopholes. It's more likely that very popular phones like a Samsung or IPhone are targets from "the bad guys", since there will be bigger payoff for breaking the security of those phones, since there is a greater pool of users to target. Most hacks I've witnessed weren't random, they were targeted. Ask yourself: Am I worth the trouble of getting hacked? Do you have anything of interest on your phone that would warrant an excessive use of resources? Managing to hack a Pixel is not only unlikely in terms of the security you need to breach, but also in terms of the potential payoff in relation to the necessary knowhow and resources. It's just "not worth it".
What you should do immediately, just in case, is secure your Google account. Change your password. Maybe even change your two-factor authentication, if you have one (sms is not secure, use a token generating software/device). Change the wifi password from your girlfriend and check the list of connected devices. make a list of these connected devices + history (find that in the rooter software) and check them against the devices you know of. Also check the list of connected devices to your GAccount. Use the option to log out ALL devices from your Google account, so only your device is connected.
Do any other people have access to your phone? Do any other people know your passwords? Does your girlfriend has access? Do any other people have biometric security saved on your phone? Do you trust your girlfriend completely?
Make sure you use a special, new password for your GAccount, never reuse old ones that you have used somewhere else. Also check your emails on https://haveibeenpwned.com/
Beyond that, if you are not doing already, use a password manager.
Click to expand...
Click to collapse
Thanks I really appreciate the help and all the advice. I checked https://haveibeenpwned.com/ and my account has been pawned in 1 data breach... I will deactivate the Google account and start over fresh. Thanks again for all the info
bencozzy said:
Two things are they refurbished? And do they work without signing into google?
Click to expand...
Click to collapse
The first one was new, but the one I got from Google as a replacement was refurbished. Ill try resetting through the settings and deactivating all my accounts.
Woodruff87 said:
Thanks I really appreciate the help and all the advice. I checked https://haveibeenpwned.com/ and my account has been pawned in 1 data breach... I will deactivate the Google account and start over fresh. Thanks again for all the info
Click to expand...
Click to collapse
This, among many other things, is one of the reasons I use GrapheneOS and NO gooble services (despite all the attention they give to sandboxed gooble services).
Woodruff87 said:
Thanks I really appreciate the help and all the advice. I checked https://haveibeenpwned.com/ and my account has been pawned in 1 data breach... I will deactivate the Google account and start over fresh. Thanks again for all the info
Click to expand...
Click to collapse
your google address was found on that site for another service and you used the same password for both services, correct?
despite what some believe, your google account will not get hacked unless your password is insecure (ie. leaked or insufficient with 2FA). anything less and your asking for trouble (also using GrapheneOS).

Categories

Resources