Database Info

Rooting Pixel, any drawbacks or missing features since its still 'new/beta'

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?

Camera don't work after bootloader unlock + Sony Android 9 Flash with Emma

Hi guys, two days ago I flashed the stock sony android 9 on my xz2 (I had a branded device) but now the camera is not working properly, I can take picture but the screen always stay black. There is a way to fix this? I don't found anything simalar, but probably I did a bad research (if there is a post please give me the link)

ELDadda said:
Hi guys, two days ago I flashed the stock sony android 9 on my xz2 (I had a branded device) but now the camera is not working properly, I can take picture but the screen always stay black. There is a way to fix this? I don't found anything simalar, but probably I did a bad research (if there is a post please give me the link)
Click to expand...
Click to collapse
Did you unlock your bootloader to change firmware?
You are now going to need the drmfix for the rest of its life

marcogiannetta said:
Did you unlock your bootloader to change firmware?
You are now going to need the drmfix for the rest of its life
Click to expand...
Click to collapse
Ye I unlocked it. It's fine to do the drmfix, but how? I'm out of the flashing and similars since years I don't know how to do this.

ELDadda said:
Ye I unlocked it. It's fine to do the drmfix, but how? I'm out of the flashing and similars since years I don't know how to do this.
Click to expand...
Click to collapse
Bootloader unlock wasn't needed at all.
Anyway, search XperiFix here on xda, but I don't know if it's ready for xz2 family. Oh, it's a paid solution, about 19€.

marcogiannetta said:
Bootloader unlock wasn't needed at all.
Anyway, search XperiFix here on xda, but I don't know if it's ready for xz2 family. Oh, it's a paid solution, about 19€.
Click to expand...
Click to collapse
I just followed up the Sony site for the flash, btw maybe I'll spent this, but any free solution?

ELDadda said:
I just followed up the Sony site for the flash, btw maybe I'll spent this, but any free solution?
Click to expand...
Click to collapse
No

marcogiannetta said:
No
Click to expand...
Click to collapse
OK well, I'll do this little buy (19€ will not change my life at all) I'm upset of this ****ty trouble, none was said on sony site and Z2 doesn't have this trouble when unlocked...

ELDadda said:
OK well, I'll do this little buy (19€ will not change my life at all) I'm upset of this ****ty trouble, none was said on sony site and Z2 doesn't have this trouble when unlocked...
Click to expand...
Click to collapse
Z2 had even more troubles.
Maybe you never noticed, but the camera was really bad after bootloader unlock.

marcogiannetta said:
Z2 had even more troubles.
Maybe you never noticed, but the camera was really bad after bootloader unlock.
Click to expand...
Click to collapse
When I started to mod z2 I was more on the workpiece with fix and modding so I never cared too much of this troubles

At least it can take pictures, only the preview is black :silly:
Due to the lack of pie support of the pay solution at the moment, you can downgrade your phone to OREO, install the solution, take a picture and upgrade your phone to PIE again.
You need newflasher v13 from XDA and the stock Oreo ROM I uploaded in the TWRP thread.
And a downgrade requires factory reset.
Because of the encryption.
Feel free to ask for help.

MartinX3 said:
At least it can take pictures, only the preview is black :silly:
Due to the lack of pie support of the pay solution at the moment, you can downgrade your phone to OREO, install the solution, take a picture and upgrade your phone to PIE again.
You need newflasher v13 from XDA and the stock Oreo ROM I uploaded in the TWRP thread.
And a downgrade requires factory reset.
Because of the encryption.
Feel free to ask for help.
Click to expand...
Click to collapse
So I have to flash the previous version on mobile, run the fixer, and install again pie?

ELDadda said:
So I have to flash the previous version on mobile, run the fixer, and install again pie?
Click to expand...
Click to collapse
And use it a single time in OREO to take a picture.
And you need to backup your userdata before downgrading to Oreo.

MartinX3 said:
And use it a single time in OREO to take a picture.
And you need to backup your userdata before downgrading to Oreo.
Click to expand...
Click to collapse
Ye, understood. But it doesn't give me the root too right? I mean I can chose it? Cause otherwise pokemon go will not start on the phone

ELDadda said:
Ye, understood. But it doesn't give me the root too right? I mean I can chose it? Cause otherwise pokemon go will not start on the phone
Click to expand...
Click to collapse
Even with magisk hide?
You need magisk (it gives you root) to boot the phone after the twrp installation, because of Android Verified Boot 2.0

MartinX3 said:
Even with magisk hide?
You need magisk (it gives you root) to boot the phone after the twrp installation, because of Android Verified Boot 2.0
Click to expand...
Click to collapse
I have to see how it goes, maybe there is a way

ELDadda said:
I have to see how it goes, maybe there is a way
Click to expand...
Click to collapse
"Magisk hide" :silly:

Hello
Since I unlock the bootloader and install Android 9 with EMMA I have the same problem
Have you found a solution?
Sorry I'm really new I just wanted to change ROMs and I made the mistake of unlocking the bootloader
I look on the forum it offers solutions but with the level I have I really do not succeed

Matmani said:
Hello
Since I unlock the bootloader and install Android 9 with EMMA I have the same problem
Have you found a solution?
Sorry I'm really new I just wanted to change ROMs and I made the mistake of unlocking the bootloader
I look on the forum it offers solutions but with the level I have I really do not succeed
Click to expand...
Click to collapse
Go into my TWRP thread and install TWRP and magisk.
Root your phone, backup your apps with Titanium Backup
Downgrade to the Oreo firmware I uploaded there, use xperifix as DRMfix.
Boot into Oreo, use the camera to take one shot.
Upgrade to PIE and reinstall your apps with Titanium Backup.
Titanium Backup and xperifix costs some €/$
Then wait for xperifix PIE release to get your 100% photo quality back.

MartinX3 said:
Go into my TWRP thread and install TWRP and magisk.
Root your phone, backup your apps with Titanium Backup
Downgrade to the Oreo firmware I uploaded there, use xperifix as DRMfix.
Boot into Oreo, use the camera to take one shot.
Upgrade to PIE and reinstall your apps with Titanium Backup.
Titanium Backup and xperifix costs some €/$
Then wait for xperifix PIE release to get your 100% photo quality back.
Click to expand...
Click to collapse
I saw your thread, if it's the only solution I'll try it after. I am under Win7 and xperifix is ​​running under win8 and 10. Thanks for responding

Matmani said:
I saw your thread, if it's the only solution I'll try it after. I am under Win7 and xperifix is ​​running under win8 and 10. Thanks for responding
Click to expand...
Click to collapse
It should run under win 7 too
You're welcome
And a DRMfix reactivates every function back, like you never unlocked it.

TWRP on the P4a?

I was wondering if anyone knew about the partition schemes and whether there is enough room on the boot image to install custom recovery on the P4a?
The Pixel 3A did not have enough room on the RAM disk on the boot image. So installing TWRP, even a stripped down version compressed, on the P3a was a no-go.
Custom recovery was not necessary on the P3a. Just having and unlocked bootloader and root via Magisk gives a lot of options including custom ROMs.
However, I'm still curious if custom recovery will ever come to the P4a?

12paq said:
I was wondering if anyone knew about the partition schemes and whether there is enough room on the boot image to install custom recovery on the P4a?
The Pixel 3A did not have enough room on the RAM disk on the boot image. So installing TWRP, even a stripped down version compressed, on the P3a was a no-go.
Custom recovery was not necessary on the P3a. Just having and unlocked bootloader and root via Magisk gives a lot of options including custom ROMs.
However, I'm still curious if custom recovery will ever come to the P4a?
Click to expand...
Click to collapse
LMAO. Give it up. We're going to be on 11. Good night

Golf c said:
LMAO. Give it up. We're going to be on 11. Good night
Click to expand...
Click to collapse
Not everyone will move to 11 right away if thet can get TWRP working on A10 first.

digger16309 said:
Not everyone will move to 11 right away if thet can get TWRP working on A10 first.
Click to expand...
Click to collapse
Good luck my friend. Stay on 10

We don't even have kernel source yet..

I don't think there was twrp for a pixel for a couple years was there? Pixel 2? And that didn't get past rc I don't think.

Golf c said:
LMAO. Give it up. We're going to be on 11. Good night
Click to expand...
Click to collapse
Thanks! As I said TWRP has not been needed and I was just curious.
However I did enjoy your insecure condescending attitude. It made me LMAO.
Again, thanks! ??

dmb219 said:
I don't think there was twrp for a pixel for a couple years was there? Pixel 2? And that didn't get past rc I don't think.
Click to expand...
Click to collapse
I know, it looks like TWRP has been doing a long slow death spiral.
We have TWRP on Android 10 for the Pixel C tablet. But of course among other things, there's no A/B partitions and Google abandoned support for the device a while ago.

Might be a while, pixel 3+ devices haven't had a 100% working TWRP for a long time.
They can still sideload ROMs and patch boot images with adb/fastboot
I'll miss this moving on from my 2xl. Nice to flash and update things without needing a PC

Golf c said:
Good luck my friend. Stay on 10
Click to expand...
Click to collapse
I will until there is EdXposed for 11 + module updates.

digger16309 said:
I will until there is EdXposed for 11 + module updates.
Click to expand...
Click to collapse
Yucky

Someone correct me if I am wrong but there are no factory images yet for the 4a so no rooting with Magisk until then?

Is it at least possible to unlock the bootloader right away? Is that just standard fastboot ADB procedure or is there something Pixel specific(first one)

dpaine88 said:
Is it at least possible to unlock the bootloader right away? Is that just standard fastboot ADB procedure or is there something Pixel specific(first one)
Click to expand...
Click to collapse
Just unlocked my Pixel4a using the standard ADB commands. Will say that OEM Unlocking stayed grayed out, until I connected to my WiFi (No SIM) and let the phone connect to the mother-ship.

Archangel said:
Someone correct me if I am wrong but there are no factory images yet for the 4a so no rooting with Magisk until then?
Click to expand...
Click to collapse
yea i believe you are correct, i think same steps for the pix4 can be applied on the 4a https://www.xda-developers.com/google-pixel-4-root-magisk/
im not sure if there are other ways to get the boot img but id rather just wait for the factory images to release & mess with it then. gonna make a cronjob script to watch / notify me once its up.

renzyyy said:
yea i believe you are correct, i think same steps for the pix4 can be applied on the 4a https://www.xda-developers.com/google-pixel-4-root-magisk/
im not sure if there are other ways to get the boot img but id rather just wait for the factory images to release & mess with it then. gonna make a cronjob script to watch / notify me once its up.
Click to expand...
Click to collapse
If I get around to it this weekend, I may just do a rom dump to extract the boot.img. Haven't done it in a while. I'm still waiting for some screen protectors to arrive before I mess with my phone.

Archangel said:
Someone correct me if I am wrong but there are no factory images yet for the 4a so no rooting with Magisk until then?
Click to expand...
Click to collapse
I can't find them either.

Isn't Android 11 going to make it more difficult to hide root anymore? I am tempted to root, but heard (or read) somewhere that with android 11 that it may not be worth it as any app (or something like that) will be able to see and not work.

This is the first phone I've owned that I think I'll be satisfied with stock. Ad guard does everything I need as ad away did. And it doesn't need root. Everything is fast! Now I don't have to hack Google pay.

edufur said:
This is the first phone I've owned that I think I'll be satisfied with stock. Ad guard does everything I need as ad away did. And it doesn't need root. Everything is fast! Now I don't have to hack Google pay.
Click to expand...
Click to collapse
Curious about adguard. I just tried it and won't install with chrome as browser.
Sent from my OnePlus 5T using XDA Labs

Widevine L3

Hello. Yesterday I bought a oneplus 8T European version (kb2003). Global ROM was installed, so I upgraded to a European ROM (11.0.8.14.KB05BA). Later I have opened the bootloader and installed Magisk. All good. But my surprise was when I saw that I have widevine L3. I don't know if you've ever been with widevine L1, I forgot to look at it, but it's supposed to. It comes from a oneplus 8 and I have installed exactly the same things but that mobile has widevine L1. In another thread I read that it was an update problem, but it was solved with an OTA. I have also tried installing Hide Config in Magisk and changing for a European fingerprint (although it already comes with one from the factory) but without success. That could be happening?

If you pass the SafteyNet check in Magisk, there's nothing more to do in there.
Actually, sometimes you just have to wait for a few reboots to get L1 back. I've seen several reports on here with that situation.
My personal situation was that I had unlocked and flashed a ROM, but had L3. I didn't like the ROM so I used MSM tool to go back to stock.
Then I unlocked again and flashed a different ROM (YAAP). I had L1 immediately, even before flashing Magisk.

xocomaox said:
If you pass the SafteyNet check in Magisk, there's nothing more to do in there.
Actually, sometimes you just have to wait for a few reboots to get L1 back. I've seen several reports on here with that situation.
My personal situation was that I had unlocked and flashed a ROM, but had L3. I didn't like the ROM so I used MSM tool to go back to stock.
Then I unlocked again and flashed a different ROM (YAAP). I had L1 immediately, even before flashing Magisk.
Click to expand...
Click to collapse
Yes, I passed safetyNet. But I've rebooted many times and I'm still the same ...

sakun-ice said:
Yes, I passed safetyNet. But I've rebooted many times and I'm still the same ...
Click to expand...
Click to collapse
Try MSM back to stock and start again. It may work.

sakun-ice said:
Yes, I passed safetyNet. But I've rebooted many times and I'm still the same ...
Click to expand...
Click to collapse
Have you tried clearing the storage for both Google Play Services and Google Play and then rebooting?

BillGoss said:
Have you tried clearing the storage for both Google Play Services and Google Play and then rebooting?
Click to expand...
Click to collapse
Yes, but nothing...

sakun-ice said:
Yes, but nothing...
Click to expand...
Click to collapse
Go to google playstore > Settings > Biometric authentication. If it is disabled, enable it. If prompted to enter a password, enter it.
Reboot the phone once and check the widevine status using the DRM info app from the play store. It may take time for it to update, so give it up to 24 hours. Check if it has re-enabled L1.
This also may re-enable L1.
If Netflix is still showing SD, go to Netflix app info, clear cache, data, and uninstall updates. Reboot, install updates, and check if it now allows HD.

These tips are great, but easiest way to get L1 back is to flash stock from MSM Tool.

So you can't have L1 with a custom rom?

lazostat said:
So you can't have L1 with a custom rom?
Click to expand...
Click to collapse
You can. I have it right now on YAAP ROM.

xocomaox said:
These tips are great, but easiest way to get L1 back is to flash stock from MSM Tool.
Click to expand...
Click to collapse
Do you have the thread where it says the steps to restore the stock rom with msm tool? I'm not sure what tutorial it is and I don't want to brick the phone.

sakun-ice said:
Do you have the thread where it says the steps to restore the stock rom with msm tool? I'm not sure what tutorial it is and I don't want to brick the phone.
Click to expand...
Click to collapse
[OP8T][OOS KB05AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com

Rooting Oneplus 7 Pro using magisk soft-bricks my deivce.

I tried rooting my oneplus 7 pro using magisk with two different boot.img both time the device got soft bricked, wi-fi stopped working no volumes at own. i did get root access but i loose wi-fi connectivity and audio of my device.
I tried factory reset after rooting but it won't fix issue either.
I am currently on Oxygen OS 11.0.1.1.
Anyone having same issues? Or your magisk root works just fine? Any other way to root my OP7 pro.

A device's Android is rooted when SU ( AKA root ) is present.
Since Android 6 by default Toybox is part of any Android distribution. This Toybox release is restricted, means SU subcommand isn't supported. Hence all you have to do to get Android rooted is to replace pre-installed Toybox version by Toybox v0.8.5 what isn't restricted, will say contains SU support. Only requirement: ~200KB free space is available in /vendor/bin directory.

pbharesh82 said:
I tried rooting my oneplus 7 pro using magisk with two different boot.img both time the device got soft bricked, wi-fi stopped working no volumes at own. i did get root access but i loose wi-fi connectivity and audio of my device.
I tried factory reset after rooting but it won't fix issue either.
I am currently on Oxygen OS 11.0.1.1.
Anyone having same issues? Or your magisk root works just fine? Any other way to root my OP7 pro.
Click to expand...
Click to collapse
Buddy see here https://www.mediafire.com/folder/94rqh7g0zq0vq/Oneplus_7_series_Boot_images ,boot image try it and let me know if it works

jacgoh said:
Buddy see here https://www.mediafire.com/folder/94rqh7g0zq0vq/Oneplus_7_series_Boot_images ,boot image try it and let me know if it works
Click to expand...
Click to collapse
I tried this one and another one that i extracted myself from official oneplus oxygenos's zip. Both didn't work for me.

Botlooader unlocked? Upload 10 to your phone... unlock it and see if it works... there are some rom for downgrade...

jacgoh said:
Botlooader unlocked? Upload 10 to your phone... unlock it and see if it works... there are some rom for downgrade...
Click to expand...
Click to collapse
Yes, the bootloader is unlocked I will first try to patch it with 11.0.0.2 downgrade. I Will let you know when I am done.

pbharesh82 said:
Yes, the bootloader is unlocked I will first try to patch it with 11.0.0.2 downgrade. I Will let you know when I am done.
Click to expand...
Click to collapse
Hey man did you find a fix? I'm in the same boat :/

xRejectx said:
Hey man did you find a fix? I'm in the same boat :/
Click to expand...
Click to collapse
I tried, it worked I got root but it's not optimal, I had battery issues and the phone also runs a little sluggish.
So I reverted it back to stock using the MSM download tool.

pbharesh82 said:
I tried, it worked I got root but it's not optimal, I had battery issues and the phone also runs a little sluggish.
So I reverted it back to stock using the MSM download tool.
Click to expand...
Click to collapse
Is there any guide I can follow? Or could you show me the steps?