Rooting Pixel, any drawbacks or missing features since its still 'new/beta' - Google Pixel Questions & Answers

So I just finally received my phone and of course want to root it and switch over from my htc one m7.
are there any features of rooting that still are in the process of being worked out?
main concern does titanium backup work fully

kazemitsui said:
So I just finally received my phone and of course want to root it and switch over from my htc one m7.
are there any features of rooting that still are in the process of being worked out?
main concern does titanium backup work fully
Click to expand...
Click to collapse
Titanium Backup works fine. Any apps that use SafetyNet(Android Pay, Snapchat, etc) won't work once you unlock your bootloader/root.

Obaterista93 said:
Titanium Backup works fine. Any apps that use SafetyNet(Android Pay, Snapchat, etc) won't work once you unlock your bootloader/root.
Click to expand...
Click to collapse
is there a list of the most common SafetyNet apps? I use neither of the two you listed. I just know pkmn go doesnt work but any others or you have a link to the list?

kazemitsui said:
is there a list of the most common SafetyNet apps? I use neither of the two you listed. I just know pkmn go doesnt work but any others or you have a link to the list?
Click to expand...
Click to collapse
Snapchat, and most banking apps. Except simple and chase that I know of.

There are still tons of warnings of permanent bad things happening if you relock the bootloader without stock software installed. I know no details but I recommend you research that first before starting anything.

What if you just root to modify the hosts file, then into it and lock? Seems like that should be fine

I know one workaround for Snapchat used to be unlocking the bootloader, installing the app and logging in, then rooting. Any word on if that still applies? I'm using a 2014 Moto X still on Lollipop, so I'm afraid I'm a touch out of the loop.

NegativeOne said:
What if you just root to modify the hosts file, then into it and lock? Seems like that should be fine
Click to expand...
Click to collapse
Test and find out if you still get yellow warning at boot. If no warning... Maybe you won't be potentially bricked by red lockout if you lock.
If you you see yellow warning, certainly that is not fine.
Sent from my sailfish using XDA Labs

Apparently, as I've been informed, to lock the BL again, you will have to do a wipe, so no good.

Just flash a custom kernel, they bypass the bootloader unlock check for safetynet. Doesnt' help you with root though

Yeah, I might end up doing that. So SafetyNet detects systemless root now?

sovanyio said:
Just flash a custom kernel, they bypass the bootloader unlock check for safetynet. Doesnt' help you with root though
Click to expand...
Click to collapse
So either one of the 2 kernel's listed here will bypass the bootloader unlock check which will make Android Pay work?

JAYNO20 said:
So either one of the 2 kernel's listed here will bypass the bootloader unlock check which will make Android Pay work?
Click to expand...
Click to collapse
Yeah I'm running franco and have AP working
Edit: And snapchat, for that matter

sovanyio said:
Yeah I'm running franco and have AP working
Edit: And snapchat, for that matter
Click to expand...
Click to collapse
Any issues from using that kernel? I am hoping for stock or better than stock.

JAYNO20 said:
Any issues from using that kernel? I am hoping for stock or better than stock.
Click to expand...
Click to collapse
Nothing I've noticed so far

sovanyio said:
Nothing I've noticed so far
Click to expand...
Click to collapse
Awesome. I might give it a shot then.

Is there a way to get root without resetting the phone? I am told if you the supported BL unlock, it wipes you.

sovanyio said:
Yeah I'm running franco and have AP working
Edit: And snapchat, for that matter
Click to expand...
Click to collapse
Did you have to enable something to make AP work after loading that kernel? It isn't working for me.

JAYNO20 said:
Did you have to enable something to make AP work after loading that kernel? It isn't working for me.
Click to expand...
Click to collapse
No.. are you running at least r2? I didn't root or anything that will still trip safetynet

sovanyio said:
No.. are you running at least r2? I didn't root or anything that will still trip safetynet
Click to expand...
Click to collapse
Oh I didn't know that. I did root. Any way to hide that too?

Related

which ROM for as close to stock android as possible for SM-G930F

I see a lot of custom ROMs on https://forum.xda-developers.com/galaxy-s7/development but I am not sure which to use. My main goal is to remove all the builtin Samsung apps that I cannot disable/uninstall like Calendar and Internet. I started looking at SuperMan but then saw it has a lot of other enhancements too. I also want to avoid my device being rooted because I have to install apps that won't install if my phone is rooted (GFE/BlackBerry Work).
LineageOS or Resurrection Remix.
Just disable the Samsung apps you don't want. That's the only remedy for you.
SuperMan is probably the closest you'll get to stock. If that's too far off, I'm not really sure of any other options. You could temporarily root and try removing the offending apps, I'm not sure how much the system depends on them.
There's also the option of Magisk (Systemless) root, which shouldn't effect root-adverse apps.
I have rooted stock G930F rom with Magisk and removed close to a 100 system apps. No bugs, no crashes, and it is the best rom there is, if you tweak it right. Btw, you can hide root with Magisk and install your apps.
Memovic said:
I have rooted stock G930F rom with Magisk and removed close to a 100 system apps. No bugs, no crashes, and it is the best rom there is, if you tweak it right. Btw, you can hide root with Magisk and install your apps.
Click to expand...
Click to collapse
This is awesome. Any details/links/help on how to install remove those 100 system apps? I I see lots of articles on how to install Magisk so I can probably figure that out but not sure about how to install the system apps.
imthenachoman said:
This is awesome. Any details/links/help on how to install remove those 100 system apps? I I see lots of articles on how to install Magisk so I can probably figure that out but not sure about how to install the system apps.
Click to expand...
Click to collapse
Please take my advice:
Do NOT root your device.
Cause that has some side effects and nearly no benefits:
You won't be able to encrypt your phone again.
You'll have to install magisk to get some things to work
Do NOT install an AOKP based ROM cause there are severe bluetooth bugs.
Just install "BK Package Disabler (Samsung)" on stockrom and get rid of Samsungs bloatware.
PS:
I'm back to stockrom after installing LOS and I regret that step, cause it tripped the knox-bit.
Perhaps the BT bugs will be fixed in future; then I'll give LOS another shot.
Lol @ this lad above, get your facts straight.
On-topic: I followed root instructions from galaxys7root. For the debloating part, there is a topic called "Debloat your S7" or something like that, which helped me uninstall most of the apps, and the other ones I just uninstalled cause I didn't need them.
Memovic said:
Lol @ this lad above, get your facts straight.
Click to expand...
Click to collapse
Laughing isn't very polite.
On-topic:
How did you get your phone encrypted again?
What are the benefits of being rooted nowadays?
OK, TB would be one thing for me.
And... tinkering.
Do some Google-ing, should get the answers.
Memovic said:
Do some Google-ing, should get the answers.
Click to expand...
Click to collapse
Thanks for sharing your limitless wisdom :good:
if you want a rom as close to perfect, try helios 7.22.1
sammydoro said:
Please take my adviceo NOT root your device.
Click to expand...
Click to collapse
Everything I have read says that there are no issues rooting. Lots of folks have done it w/o issues. Maybe yours was a one-off?
Memovic said:
On-topic: I followed root instructions from galaxys7root. For the debloating part, there is a topic called "Debloat your S7" or something like that, which helped me uninstall most of the apps, and the other ones I just uninstalled cause I didn't need them.
Click to expand...
Click to collapse
Thank you! I will give it a shot.
imthenachoman said:
Everything I have read says that there are no issues rooting. Lots of folks have done it w/o issues. Maybe yours was a one-off?
Click to expand...
Click to collapse
Rooting went flawlessly.
I took the TWRP / Magisk way.
OK, loosing all the data is quite normal, when formating data, to get rid of the encryption.
But it trips your knox-fuse with the following consequences:
S-Health does not work anymore. OK, there is a build.prop hack to get it working.
OTA updates will not work anymore.
S-Pay (and others) is said to not work anymore.
Encryption does not work or is risky (look at Chainfires post):
forum.xda-developers.com/showpost.php?p=72204306&postcount=978
No one knows, how long safetynet will be covered by Magisk. Btw.: Magisk is great!
If I am wrong at any point, pls correct me.
I only rooted to use LOS. But there are too many errors atm.
So I returned to stock and have to live with these issues.
So it depends on your usecase.
If you just want to debloat your stockrom, use BK- disabler.
If you want more, root it.
sammydoro said:
If you just want to debloat your stockrom, use BK- disabler.
Click to expand...
Click to collapse
Can BK disabler disable or uninstall some of the built-in apps like Calendar and Contacts?
imthenachoman said:
Can BK disabler disable or uninstall some of the built-in apps like Calendar and Contacts?
Click to expand...
Click to collapse
Yes. That is the purpose of the app.
And, in my opinion, it works reliable and comfortable.
sammydoro said:
Rooting went flawlessly.
I took the TWRP / Magisk way.
OK, loosing all the data is quite normal, when formating data, to get rid of the encryption.
But it trips your knox-fuse with the following consequences:
S-Health does not work anymore. OK, there is a build.prop hack to get it working.
Click to expand...
Click to collapse
I rooted, but my S Health is still working
sammydoro said:
OTA updates will not work anymore.
[/QOUTE]
Yes, that's good, so Samsung won't remove my root or any system apps I am using or adding system apps I removed.
sammydoro said:
S-Pay (and others) is said to not work anymore.
[/QOUTE]
S-Pay doesn't work in our country, so what? It's a fail project anyhow.
sammydoro said:
Encryption does not work or is risky (look at Chainfires post):
forum.xda-developers.com/showpost.php?p=72204306&postcount=978
No one knows, how long safetynet will be covered by Magisk. Btw.: Magisk is great!
[/QOUTE]
sammydoro said:
If I am wrong at any point, pls correct me.
[/QOUTE]
done
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse

T-Mobile Revvl OTA captured

I managed to capture an OTA update for the T-Mobile Revvl. It contains the boot image, preloader, and a bunch of other system stuff. If we can mod this for root or custom recoveries, that would be great.
Here's a mdeiafire link to the OTA update.
https://www.mediafire.com/file/izns3i5hd23ye6o/update.zip
SHA-1 is F2D7E8D8B6755DF6E5265352F21C59ED0EC2597D
SiberianLeopard said:
I managed to capture an OTA update for the T-Mobile Revvl. It contains the boot image, preloader, and a bunch of other system stuff. If we can mod this for root or custom recoveries, that would be great.
Here's a mdeiafire link to the OTA update.
https://www.mediafire.com/file/izns3i5hd23ye6o/update.zip
SHA-1 is F2D7E8D8B6755DF6E5265352F21C59ED0EC2597D
Click to expand...
Click to collapse
has anyone got a root to this phone yet
murda59 said:
has anyone got a root to this phone yet
Click to expand...
Click to collapse
Working on it. Be patient.
Thanks for the copy see what I can find out. Is this for a c3701a? That would be helpful thanks.
SiberianLeopard said:
I managed to capture an OTA update for the T-Mobile Revvl. It contains the boot image, preloader, and a bunch of other system stuff. If we can mod this for root or custom recoveries, that would be great.
Here's a mdeiafire link to the OTA update.
https://www.mediafire.com/file/izns3i5hd23ye6o/update.zip
SHA-1 is F2D7E8D8B6755DF6E5265352F21C59ED0EC2597D
Click to expand...
Click to collapse
Is this for the c3701a.
What makes you think that this is for the C3701a? This is for the T-Mobile Revvl...a totally different phone
niisan518 said:
Is this for the c3701a.
Click to expand...
Click to collapse
No, that's a completely different phone. Are you legally blind?
murda59 said:
has anyone got a root to this phone yet
Click to expand...
Click to collapse
there are exploits available but nobody has implemented them yet. If you want root, DO NOT UPDATE THE PHONE
Can you not use sp flash tools to root?
Warrior1988 said:
Can you not use sp flash tools to root?
Click to expand...
Click to collapse
No, it's been already tried. Me and a few other people are working on it but progress is slow due to personal schedules.
SiberianLeopard said:
No, it's been already tried. Me and a few other people are working on it but progress is slow due to personal schedules.
Click to expand...
Click to collapse
Odd I never had a problem with sp flash tools to root a device even with locked bootloader and lock HW.
Warrior1988 said:
Odd I never had a problem with sp flash tools to root a device even with locked bootloader and lock HW.
Click to expand...
Click to collapse
The OTA contains the special key needed for SP flash tools to work, and even when trying that it fails.
Warrior1988 said:
Odd I never had a problem with sp flash tools to root a device even with locked bootloader and lock HW.
Click to expand...
Click to collapse
I also tried Framaroot, doesn't work.
SiberianLeopard said:
No, it's been already tried. Me and a few other people are working on it but progress is slow due to personal schedules.
Click to expand...
Click to collapse
SiberianLeopard said:
I also tried Framaroot, doesn't work.
Click to expand...
Click to collapse
Have you tried dirtycow? Also you don't need the keys it's direct flash. Have you tried Advanced Mode and used the Write memory Function? Only use this if you know how.
Warrior1988 said:
Have you tried dirtycow? Also you don't need the keys it's direct flash. Have you tried Advanced Mode and used the Write memory Function? Only use this if you know how.
Click to expand...
Click to collapse
Yeah. Will try dirtycow
Warrior1988 said:
Have you tried dirtycow? Also you don't need the keys it's direct flash. Have you tried Advanced Mode and used the Write memory Function? Only use this if you know how.
Click to expand...
Click to collapse
You must have missed the memo, Dirt Cow was patched out in 7.0.1. This phone released with 7.0.1. Meaning Dirty Cow will NEVER work
SiberianLeopard said:
You must have missed the memo, Dirt Cow was patched out in 7.0.1. This phone released with 7.0.1. Meaning Dirty Cow will NEVER work
Click to expand...
Click to collapse
Dirtycow uses kernel so you need to check what security
version kernel you have it doesn't go by Android version. Or try Rowhammer.
Warrior1988 said:
Dirtycow uses kernel so you need to check what security
version kernel you have it doesn't go by Android version. Or try Rowhammer.
Click to expand...
Click to collapse
Tried Dirtycow anyway, the stock Revvl is not vilnerable.
Why don't you spit out all of the root exploit tools you know of and quit wasting my time?
I am willing to jump on the bandwagon and help developers to gain root access for this phone and the plus version. Fairly tech savvy with adb and fairly comfortable to be able to redirect if something went wrong let me know what's needed!!!
Would love to see this happen! Have one if you need someone to beta test

got G955FD today and question

I know if I flash TWRP via odin and root it and it will trip knox permanently and lose Pay and Secure Folder I think.
But my question is will everything else working like fingerprint, GPS, etc... as normal phone?
Thanks.
cline2 said:
But my question is will everything else working like fingerprint, GPS, etc... as normal phone?
Click to expand...
Click to collapse
No one would root the phone if those things didn't work.
peachpuff said:
No one would root the phone if those things didn't work.
Click to expand...
Click to collapse
LOL true. Just wanted to make sure. Thanks.
Before I root this. I got notification that there is software update for Oreo. Should I update it before I root it or what??
Don't update just in case theres a new bootloader in oreo.

cosequence if unlock bootloader on google pixel 3?

hi guys
im new on pixel series. i want to know if i do unlock bootloader, is there any feature will gone if i do that?
like samsung lost knox or sony lost drm for camera and entertaiment
thankyou
xerxess said:
hi guys
im new on pixel series. i want to know if i do unlock bootloader, is there any feature will gone if i do that?
like samsung lost knox or sony lost drm for camera and entertaiment
thankyou
Click to expand...
Click to collapse
You have to work a bit to keep GPay working, and the solution definitely requires root. The current solution has been working for a few months and works on Android 10, but who knows if they will "fix" the current hack. You will absolutely not be able to download Netflix from the Play Store. There is one build on APK Mirror that will sideload and run, but of course you will get no updates. I've been running that build on the Pixel for about 6 months, and I have a tablet that does get Netflix updates yet I see no difference between that Feb build and Netflix even from a few days ago. Those are the only two things impacting me. Obviously, need to hide apps with Magisk and such is user specific (my car's door unlock/diagnostics/etc detects root without hiding it, but it works fine once hidden).
sliding_billy said:
You have to work a bit to keep GPay working, and the solution definitely requires root. The current solution has been working for a few months and works on Android 10, but who knows if they will "fix" the current hack. You will absolutely not be able to download Netflix from the Play Store. There is one build on APK Mirror that will sideload and run, but of course you will get no updates. I've been running that build on the Pixel for about 6 months, and I have a tablet that does get Netflix updates yet I see no difference between that Feb build and Netflix even from a few days ago. Those are the only two things impacting me. Obviously, need to hide apps with Magisk and such is user specific (my car's door unlock/diagnostics/etc detects root without hiding it, but it works fine once hidden).
Click to expand...
Click to collapse
first i wanna say thankyou for reply. ah i see so the only thing feature lost function is GPay (without little tweak). is it possible to relock again? if yes , is feature fully function again? tbh i dont really need GPay.
xerxess said:
first i wanna say thankyou for reply. ah i see so the only thing feature lost function is GPay (without little tweak). is it possible to relock again? if yes , is feature fully function again? tbh i dont really need GPay.
Click to expand...
Click to collapse
You can relock the BL, but you need to first return to absolute stock (no root, no kernel, no custom recovery, etc - pretty much flash the factory image with wipe to both slots to be safe). Then the relock will perform another factory reset anyways. So, if you are asking if you can keep anything you've done while unlocked the answer is no. To me, the biggest reason for unlocking beyond root is that it is almost impossible to hard brick the Pixel with an unlocked BL. It is pretty easily accomplished when locked down and can even happen as a result of a bad OTA or something that is not your fault at all.
sliding_billy said:
You can relock the BL, but you need to first return to absolute stock (no root, no kernel, no custom recovery, etc - pretty much flash the factory image with wipe to both slots to be safe). Then the relock will perform another factory reset anyways. So, if you are asking if you can keep anything you've done while unlocked the answer is no. To me, the biggest reason for unlocking beyond root is that it is almost impossible to hard brick the Pixel with an unlocked BL. It is pretty easily accomplished when locked down and can even happen as a result of a bad OTA or something that is not your fault at all.
Click to expand...
Click to collapse
understood, if only need back to absolute stock its okay for me. though it will like other smartphone need "drm" to relock.
yeah agree, why i think to unlock is about avoid brick or similar thing. but before i do that i need to know what feature will lost, so i asking here.
if relock again, all things will back to normal again right?
xerxess said:
understood, if only need back to absolute stock its okay for me. though it will like other smartphone need "drm" to relock.
yeah agree, why i think to unlock is about avoid brick or similar thing. but before i do that i need to know what feature will lost, so i asking here.
if relock again, all things will back to normal again right?
Click to expand...
Click to collapse
No, there is no residual damage like lost Knox. Everything would return to normal once BL is locked back up.
sliding_billy said:
No, there is no residual damage like lost Knox. Everything would return to normal once BL is locked back up.
Click to expand...
Click to collapse
understood, thank you very much. really appreciate your time.

Bootloader Lock after root [URGENT HELP NEEDED]

I have a rooted OnePlus 7 Pro running OOS 10.0.1 rooted with Magisk but everything is very glitchy and I probably did something wrong. WiFi doesn’t work, boot slot b is non functional, and I’m just done with root. I need help. How do I return COMPLETELY TO STOCK, and lock the bootloader and unroot without tripping safety net or bricking? OnePlus support said they could do nothing. Every post on XDA advises to never relock, but I don’t know what else to do. I’m new to this stuff. Thank you for your time.
jwbritt01 said:
I have a rooted OnePlus 7 Pro running OOS 10.0.1 rooted with Magisk but everything is very glitchy and I probably did something wrong. WiFi doesn’t work, boot slot b is non functional, and I’m just done with root. I need help. How do I return COMPLETELY TO STOCK, and lock the bootloader and unroot without tripping safety net or bricking? OnePlus support said they could do nothing. Every post on XDA advises to never relock, but I don’t know what else to do. I’m new to this stuff. Thank you for your time.
Click to expand...
Click to collapse
If you want to go completely stock locked, Use MSM tool it will put full stock and lock the bootloader for you. Beware will wipe all your data backup all your personal data first
Follow instructions here: https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
liam_davenport said:
If you want to go completely stock locked, Use MSM tool it will put full stock and lock the bootloader for you. Beware will wipe all your data backup all your personal data first
Follow instructions here: https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Click to expand...
Click to collapse
Will Safety Net he tripped still after this? Because this seems too good to be true
jwbritt01 said:
Will Safety Net he tripped still after this? Because this seems too good to be true
Click to expand...
Click to collapse
No as you will be FULL stock with locked bootloader.
liam_davenport said:
No as you will be FULL stock with locked bootloader.
Click to expand...
Click to collapse
And does this work for the GM21AA model of the phone too?
jwbritt01 said:
And does this work for the GM21AA model of the phone too?
Click to expand...
Click to collapse
Yes
jwbritt01 said:
I have a rooted OnePlus 7 Pro running OOS 10.0.1 rooted with Magisk but everything is very glitchy and I probably did something wrong. WiFi doesn’t work
Click to expand...
Click to collapse
If you manually flashed a patched boot.img, you probably just flashed in incompatible one (broken WiFi is a dead giveaway for this issue). Better to just boot TWRP, flash Magisk and let Magisk patch the boot.img.
liam_davenport said:
Yes
Click to expand...
Click to collapse
Everything went through and I have my phone working again. But I have one last question... My phone was the GM1915 model and that's what's printed on the box. But now in settings the model number is listed as GM1917. What kind of issues, if any, will this cause? Or am I good to go?
redpoint73 said:
If you manually flashed a patched boot.img, you probably just flashed in incompatible one (broken WiFi is a dead giveaway for this issue). Better to just boot TWRP, flash Magisk and let Magisk patch the boot.img.
Click to expand...
Click to collapse
If I ever go back to rooting in the future (I'm staying stock until I learn more about the technical stuff) this will be a life safer. Thanks!

Categories

Resources