Does anyone know when those in the beta programme can expect this ,I though I read so.e where we were getting it this month
Sent from my Nexus 6P using XDA-Developers mobile app
This month
You answered your own question
Most likely last Wednesday of this month which would be 26th
combat goofwing said:
Does anyone know when those in the beta programme can expect this ,I though I read so.e where we were getting it this month
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
its available now...
no google assistant though
Just Got Update
I just received Beta Version N-MR1 (NPF10C). Settings-About Phone shows Android Version 7.1.1. Support is listed as another heading under Settings.
Came thru over OTA, install went smooth, phone loaded smooth. Used the fancy new reboot button once, stuck in a boot loop. Recovery will not load either, just boot looping the google logo. Oddly cannot turn phone off in bootloader, it shuts down then starts itself up again to reboot loop, sorta funny yet annoying to have to flash back to 7.0 some bad karma here.
dajoey said:
no google assistant though
Click to expand...
Click to collapse
It's specifically only for the Pixel at this point. You can flash the Assistant mod, wipe app data, and you should get Assistant.
Howie Dub said:
It's specifically only for the Pixel at this point. You can flash the Assistant mod, wipe app data, and you should get Assistant.
Click to expand...
Click to collapse
Nope. Don't use the mod on 7.1.
You wont be able to boot.
AchillesTheGod said:
Nope. Don't use the mod on 7.1.
You wont be able to boot.
Click to expand...
Click to collapse
I booted just fine
Howie Dub said:
I booted just fine
Click to expand...
Click to collapse
Witch mod did you use. Maybe I used a different one
AchillesTheGod said:
Witch mod did you use. Maybe I used a different one
Click to expand...
Click to collapse
I used the flash method in this thread http://forum.xda-developers.com/android/software/guide-how-to-enable-google-assistant-t3477879
I only flashed the build.prop zip, not the velvet one. Couldn't get Assistant to work when I flashed both.
Just took OTA 7.1 smooth. Camera is a little different but don't see a focus lock.
Howie Dub said:
I used the flash method in this thread http://forum.xda-developers.com/android/software/guide-how-to-enable-google-assistant-t3477879
I only flashed the build.prop zip, not the velvet one. Couldn't get Assistant to work when I flashed both.
Click to expand...
Click to collapse
Thanks that was probably my mistake.
---------- Post added at 04:40 AM ---------- Previous post was at 04:24 AM ----------
Nope. Just tired it. Booted up. But no Assistant. Stock and rooted.
Downloading now -- 1263.5MB, wow!
Guessing the pixel launcher is still only for pixel phones as it's not in the beta. Shame
I flashed the pixel launcher and got this weird mic...
AchillesTheGod said:
I flashed the pixel launcher and got this weird mic...
Click to expand...
Click to collapse
That's when you don't have "OK Google everywhere" set up.
AchillesTheGod said:
I flashed the pixel launcher and got this weird mic...
Click to expand...
Click to collapse
How did you get it to show the weather? Mine shows date only.
Enviado desde mi Nexus 6P mediante Tapatalk
I think you have to give Location permission to the Pixel Launcher app.
Related
Hey guys,
I would like to ask if anyone was in similar situation. I'm running the newest Pure Nexus rom. Everything was perfect till today. I was surfing on Chrome when phone restarted suddenly. And since that time it's in a bootloop. I tried to flash factory 6.0.1, 7.0, twrp and yet... nothing. Keeps bootlooping. Does it mean it's a hard brick? It's still under warranty though. I bought it from Best Buy on February, 2016. Man! I'm glad I haven't sold my Nexus 5. It's just so small.
Any ideas? Is it over?
czaplin said:
Hey guys,
I would like to ask if anyone was in similar situation. I'm running the newest Pure Nexus rom. Everything was perfect till today. I was surfing on Chrome when phone restarted suddenly. And since that time it's in a bootloop. I tried to flash factory 6.0.1, 7.0, twrp and yet... nothing. Keeps bootlooping. Does it mean it's a hard brick? It's still under warranty though. I bought it from Best Buy on February, 2016. Man! I'm glad I haven't sold my Nexus 5. It's just so small.
Any ideas? Is it over?
Click to expand...
Click to collapse
To all people on this forum....hardbricked=no google screen...no twrp...no fastboot...no bootloader.....if you can flash images.....your not hardbricked
jamescable said:
To all people on this forum....hardbricked=no google screen...no twrp...no fastboot...no bootloader.....if you can flash images.....your not hardbricked
Click to expand...
Click to collapse
@jamescable TRUTH!! With that being Said I would go back to full stock. I'm not sure of your method but I would use Nexus Root Toolkit v2.1.9 with a full wipe. The App will do it all for you. If that doesn't work then it's hardware related but at least it's back stock!
I can access fastboot and flash the newest factory image from Google. But can't get into recovery after flashing twrp nor do a full wipe. It keeps switching between unlocked bootloader warning and Google logo. No matter what I do. I'll try toolkit as you suggested after returning from work.
Sent from my Nexus 5 using XDA-Developers mobile app
czaplin said:
I can access fastboot and flash the newest factory image from Google. But can't get into recovery after flashing twrp nor do a full wipe. It keeps switching between unlocked bootloader warning and Google logo. No matter what I do. I'll try toolkit as you suggested after returning from work.
Sent from my Nexus 5 using XDA-Developers mobile app
Click to expand...
Click to collapse
Ignore the warning, it scary but it's just warning you because the bootloader is unlocked even when flashing stock.
Sent from my Pixel XL using Tapatalk
rsalas187 said:
Ignore the warning, it scary but it's just warning you because the bootloader is unlocked even when flashing stock.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Yeah, I know. I mentioned it for reference. I'm getting stuck at Google logo no matter what I do. When I chose factory reset or recovery it gets stuck there. That happened yesterday while I was on chrome. Phone restarted without a reason and then it started.
I was on the newest PN. Then I flashed stock 7.0 and it's the same. I tried twrp and can't get into it as well.
Sent from my Nexus 5 using XDA-Developers mobile app
Btw I'm using N5 temporarily and it's more zippy than 6P. I can't believe it lol.
Sent from my Nexus 5 using XDA-Developers mobile app
czaplin said:
Hey guys,
I would like to ask if anyone was in similar situation. I'm running the newest Pure Nexus rom. Everything was perfect till today. I was surfing on Chrome when phone restarted suddenly. And since that time it's in a bootloop. I tried to flash factory 6.0.1, 7.0, twrp and yet... nothing. Keeps bootlooping. Does it mean it's a hard brick? It's still under warranty though. I bought it from Best Buy on February, 2016. Man! I'm glad I haven't sold my Nexus 5. It's just so small.
Any ideas? Is it over?
Click to expand...
Click to collapse
Had you flashed the 7.1 dev preview by chance?
edit: Or Magisk? I'm aware of a few cases like this, but haven't been able to pin down any common factors yet...
Did you make any build prop edits?
Morningstar said:
Had you flashed the 7.1 dev preview by chance?
edit: Or Magisk? I'm aware of a few cases like this, but haven't been able to pin down any common factors yet...
Click to expand...
Click to collapse
No, I had not.
Sent from my Nexus 5 using XDA-Developers mobile app
dadoc04 said:
Did you make any build prop edits?
Click to expand...
Click to collapse
Not at all.
Sent from my Nexus 5 using XDA-Developers mobile app
Ok guys, thank you all for your efforts. I found the right thread for my problem. Looks, like I'm not alone and it's a known issue.
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921
Assistant is rolling out to quarks now. This post is obsolete.
works with moto voice?
Will this work on CF's new Rom?
Edit tried and it didn't work, rebooted cleared Google app cashe and data.
adamantem said:
works with moto voice?
Click to expand...
Click to collapse
I don't see why not. When it comes to summoning it, it doesn't work any differently than Google Now.
Steve One said:
Will this work on CF's new Rom?
Edit tried and it didn't work, rebooted cleared Google app cashe and data.
Click to expand...
Click to collapse
Lame. I don't know what changes he makes, so I can't speculate as to why.
Wow downloaded and installed stock ROM, installed both files rebooted and still no assistant.
I about to give up.
Steve One said:
Wow downloaded and installed stock ROM, installed both files rebooted and still no assistant.
I about to give up.
Click to expand...
Click to collapse
Really? Wow. Maybe I just got lucky. I'm not sure why it doesn't seem to be working for anyone else. I installed the appropriate packages on my girlfriend's S6, and that didn't work either. Sorry if I mislead people.
Steve One said:
Wow downloaded and installed stock ROM, installed both files rebooted and still no assistant.
I about to give up.
Click to expand...
Click to collapse
Out of curiosity, does your phone pass safetynet?
Not sure Sir, after it didn't work I went back to my backed up CF Rom.
TheSt33v said:
Out of curiosity, does your phone pass safetynet?
Click to expand...
Click to collapse
It's enabled on the server side.
So has anyone else got it to work?
Has everyone set up google assistant voice recognition?
Open up the google app and say "OK GOOGLE"
It should open up setup for google assistant voice recognition.
I use apex launcher and holding home opens apex settings for me.
However saying OK google on any screen now opens google assistant for me.
I'm Running AOKP with the newest version of the google app and google play services
Some more info about my phone, if it helps anyone:
Before I installed the packages, I had just about everything enabled that could be enabled for Google Now. On tap: on, feed: on, OK Google everywhere: on. The first time I started it was by holding down the home button, not by saying OK Google (but that works too).
Well after flashing stock Rom yesterday and installing both apk's to no avail.
Switched back to CF's 1.7 mm Rom got off play services beta and Google's beta then called it a night.
Woke up this morning and had gotten the official update while I was asleep ?.
Got it working on my stock turbo. Although I didn't download anything. Just woke up this morning and it was on my phone.
Sent from my XT1254 using Tapatalk
Ah okay. So looks like it's a moot point now.
I got it working by uninstalling updates to Google app and Google play services, and updating the Google app through the play store.
The next time i held the home button i got the assistant
Steve One said:
Will this work on CF's new Rom.
Click to expand...
Click to collapse
Just got mine yesterday... had to wait for the server to allow it, I guess. I'm running CF 1.04.
TheSt33v said:
Ah okay. So looks like it's a moot point now.
Click to expand...
Click to collapse
I flashed your stock ROM MCG24.251-5-5 and Google Assistant was there?, I didnt have to do anything.
Guapo613 said:
I flashed your stock ROM MCG24.251-5-5 and Google Assistant was there?, I didnt have to do anything.
Click to expand...
Click to collapse
Right, which is why I edited the OP.
I just got the OTA update notification for the VZW Pixel, fully stock, unrooted, locked bootloader. Never joined the beta either. So now we'll see if any of these BT and reboot issues have been resolved. Here's hopin'
Update size: 938.4 MB
bobby janow said:
I just got the OTA update notification for the VZW Pixel, fully stock, unrooted, locked bootloader. Never joined the beta either. So now we'll see if any of these BT and reboot issues have been resolved. Here's hopin'
Update size: 938.4 MB
Click to expand...
Click to collapse
do you have always on ambient display with this update?
Tech_Savvy said:
do you have always on ambient display with this update?
Click to expand...
Click to collapse
Yes I do. Everything seems to have rolled over fine. Update screen was not the bouncing thingies but simply the G logo. Haven't rebooted to see.. oh just a little of the dots, then a quick G and then it was up. Like maybe 10 seconds for a reboot. Wow.
bobby janow said:
I just got the OTA update notification for the VZW Pixel, fully stock, unrooted, locked bootloader. Never joined the beta either. So now we'll see if any of these BT and reboot issues have been resolved. Here's hopin'
Update size: 938.4 MB
Click to expand...
Click to collapse
I just downloaded and installed it with a unlocked bootloader no problem. It's still unlocked and I just rooted it.
All the OTA images are available at https://developers.google.com/android/ota. You can all download as you wish.
henrique.mageste said:
All the OTA images are available at https://developers.google.com/android/ota. You can all download as you wish.
Click to expand...
Click to collapse
Anyone know which one is for Verizon?
jackdubl said:
Anyone know which one is for Verizon?
Click to expand...
Click to collapse
The .012 image. It is meant for all the phone's not covered by the .011 build.
Always On Ambient Display
Either, this didn't make it through in my update somehow or I'm overlooking the setting.
Can anyone offer any help on enabling this feature?
Thanks!
Man, that's annoying, I still haven't gotten it on my Project Fi pixel. I left vzw because I never got updates!
skyline315 said:
Either, this didn't make it through in my update somehow or I'm overlooking the setting.
Can anyone offer any help on enabling this feature?
Thanks!
Click to expand...
Click to collapse
I'd like to know as well
Where is the setting for always on ambient display? All I see is the regular ambient display, where it turns on for new notifications.
speedy859 said:
Where is the setting for always on ambient display? All I see is the regular ambient display, where it turns on for new notifications.
Click to expand...
Click to collapse
I've asked around and consensus seems to be that it was NOT included in this update after all. Looks like they're saving it for the Pixel 2.
JoeHockey said:
Man, that's annoying, I still haven't gotten it on my Project Fi pixel. I left vzw because I never got updates!
Click to expand...
Click to collapse
Im on fi I just downloaded the ota and then sideloaded it.
Go to settings - display - advanced and it will be towards the bottom.
Nevermind, misread. It is only for notifications. You can make it turn on when you pick it up though. By turning on "lift to check phone"
Sent from my Pixel using XDA Free mobile app
Misterxtc said:
I just downloaded and installed it with a unlocked bootloader no problem. It's still unlocked and I just rooted it.
Click to expand...
Click to collapse
Hi,
Can you let me know what version of twrp.img u used for fastboot? I tried rc1 and alpha 1. Both locked my phone up.
Really appreciate ur help
randogg65 said:
Hi,
Can you let me know what version of twrp.img u used for fastboot? I tried rc1 and alpha 1. Both locked my phone up.
Really appreciate ur help
Click to expand...
Click to collapse
I use the modded one for O here. You need to fastboot and load TWRP every time you use it because it is not flashable yet.
Misterxtc said:
I just downloaded and installed it with a unlocked bootloader no problem. It's still unlocked and I just rooted it.
Click to expand...
Click to collapse
which root method did you use since you didn't sideload? thanks.. jforgive me if it's been posted. ust getting back onto the forums and currently reading up
Misterxtc said:
I use the modded one for O here. You need to fastboot and load TWRP every time you use it because it is not flashable yet.
Click to expand...
Click to collapse
Thanks! Really appreciate it
honourbound68 said:
which root method did you use since you didn't sideload? thanks.. jforgive me if it's been posted. ust getting back onto the forums and currently reading up
Click to expand...
Click to collapse
I can't remember where I got the file I used so I would say try here.
Meanwhile...
cbusm30 said:
I'd like to know as well
Click to expand...
Click to collapse
There are also 8.0.0 factory images as well (along with the usual older factory images) - they are all here: http://www.infinitiofsuitland.com/VehicleSearchResults?search=new
To play it safe, I grabbed one 7.1.2 and one 8.0.0 factory image for the Pixel to put through the wringer (since this would be the first Pixel I've ever put through the paces).
https://developer.android.com/preview/download
Just installed. July security update. They changed the silent mode status bar icon. Still looking for other changes.
-edit- Dark theme is an option under display settings, advanced!
It seems to have some horrible contact bar in the app drawer when you pull it up now that shows 2 frequent contacts? Found out you can disable this under home screen settings.
-edit 2- root still works with magisk. Still P under build with same easter egg as before.
What's the status on root
kingbri said:
What's the status on root
Click to expand...
Click to collapse
It works with magisk 16.4
Is anyone able to tell me if Actions Services app is included in DP4 for the Pixel XL?
I originally grabbed the apk from a Pixel 2, but i suspect that it's now included in DP4.
xdatastic said:
Is anyone able to tell me if Actions Services app is included in DP4 for the Pixel XL?
I originally grabbed the apk from a Pixel 2, but i suspect that it's now included in DP4.
Click to expand...
Click to collapse
It's included.
Gordietm said:
It's included.
Click to expand...
Click to collapse
Thank you!
Anyone tried the ElementalX build for DP3 on this yet? ctsProfile seems to fail SafetyNet on Magisk 16.4, other than that haven't noticed any problems.
BoboBrazil said:
https://developer.android.com/preview/download
Just installed. July security update. They changed the silent mode status bar icon. Still looking for other changes.
-edit- Dark theme is an option under display settings, advanced!
It seems to have some horrible contact bar in the app drawer when you pull it up now that shows 2 frequent contacts? Found out you can disable this under home screen settings.
-edit 2- root still works with magisk. Still P under build with same easter egg as before.
Click to expand...
Click to collapse
Sorry, when you say root still works with magisk... do you have to unroot before updating, then reflash magisk? Or can you update right over the previous update if you're already rooted??
Hopefully Google fix up the device certification for DP4 - Google Pay won't work currently, but did on DP3. I think G need to add it server-side.
edit: Google fixed the device certification. Google Pay now works again.
Flash kernel failed cts. Might be something new detecting magisk
dht2005 said:
Sorry, when you say root still works with magisk... do you have to unroot before updating, then reflash magisk? Or can you update right over the previous update if you're already rooted??
Click to expand...
Click to collapse
Same way as always with Pixel XL ...
The theme light,dark,auto doesn't do anything for me....
Sent from my Pixel XL using Tapatalk
still not boot up, if you remove (debloat) APK's from system/app
Safety net fails but magisk hide takes care of my banking apps..so all good
I wish the OTA would hit.
Ota worked for me yesterday
shamelin73 said:
I wish the OTA would hit.
Click to expand...
Click to collapse
Sent from my Pixel XL using Tapatalk
I just need a little bit more patient it just dropped on mine too
perfoliate said:
Ota worked for me yesterday
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Sent from my Pixel XL using Tapatalk
Keep losing root, anyone else? A reboot will fix it, but it goes away eventually for me. Also magisk data partition isn't set up correctly (can't install modules).
Anyone having issues getting the light and dark themes to work?
Sent from my Pixel XL using Tapatalk
tttuning said:
Anyone having issues getting the light and dark themes to work?
Click to expand...
Click to collapse
I can't tell any difference from the settings...
---------- Post added at 07:07 AM ---------- Previous post was at 07:03 AM ----------
funkybrunk said:
Keep losing root, anyone else? A reboot will fix it, but it goes away eventually for me. Also magisk data partition isn't set up correctly (can't install modules).
Click to expand...
Click to collapse
Same for me. I install and check out everything... Everything is going great. Then randomly an app I use will say no root detected.. And I'll go to magisk and it says to install 16.4...
I've been looking around but you're the only one I've found saying what I'm seeing.
Installing the update right now. It'll be the first security update for Pixel 3a.
Here's a link with more details and download links, no 3a specific fixes in the June patch.
https://9to5google.com/2019/06/03/pixel-june-19-security-patch/
Thanks. I checked around 9 EDT but nothing new. Still locked so sideloaded.
I have a T-Mobile 3a (locked bootloader). I sideloaded the beta q but want to go back to pie. Can I sideload the ota to go back to pie?
dhoang said:
I have a T-Mobile 3a (locked bootloader). I sideloaded the beta q but want to go back to pie. Can I sideload the ota to go back to pie?
Click to expand...
Click to collapse
I don't believe so but... Try and let us know how it turns out. I think the bootloader and stuff is different so I think you need factory image
Sent from my Pixel 3a using Tapatalk
Is it save to update if you're rooted?
jmtjr278 said:
I don't believe so but... Try and let us know how it turns out. I think the bootloader and stuff is different so I think you need factory image
Click to expand...
Click to collapse
It does not work. It was running for a bit then an error message"missing config CONFIG NETFILTER_XT_MATCH_QTAGUID". Oh well I tried. I guess I will have to wait until Google officially includes 3a in it beta program.
BehelitOutlaw said:
Is it save to update if you're rooted?
Click to expand...
Click to collapse
Yup. Works just fine. Just fastboot the modded boot.img provided by @pbanj afterwards and your good to go
Sent from my Pixel 3a using Tapatalk
Your running the old boot.img? Do you know if there is a problem with altering the new boot.img with magisk?
jmtjr278 said:
Yup. Works just fine. Just fastboot the modded boot.img provided by @pbanj afterwards and your good to go
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
Archangel said:
Your running the old boot.img? Do you know if there is a problem with altering the new boot.img with magisk?
Click to expand...
Click to collapse
Nah. Check his first post. He's updated to the June modded boot.img. Save yourself since time and data because the OTA does not include the boot img that I could find. I downloaded the factory image to get it. Then I downloaded the OTA. Ugh. Almost 3gb if data by the time I was finished.
Sent from my Pixel 3a using Tapatalk
---------- Post added at 09:43 PM ---------- Previous post was at 09:32 PM ----------
jmtjr278 said:
Nah. Check his first post. He's updated to the June modded boot.img. Save yourself since time and data because the OTA does not include the boot img that I could find. I downloaded the factory image to get it. Then I downloaded the OTA. Ugh. Almost 3gb if data by the time I was finished.
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
https://drive.google.com/file/d/1eQ9QXQqYeQityqCR2fk2jgBt7UKBA_5P/view?usp=drivesdk
Here is the one I made. Enjoy
Sent from my Pixel 3a using Tapatalk
dhoang said:
I have a T-Mobile 3a (locked bootloader). I sideloaded the beta q but want to go back to pie. Can I sideload the ota to go back to pie?
Click to expand...
Click to collapse
No. Cannot go back to pie. I had a discussion with Google rep today. She said soon as the Q beta for this month comes out, we will be able to go back to Android Pie as normal. There is an issue on their side. Here's what my error was when trying to sideload back to Pie on my VZW Pixel 3a
Perfect thanks brother! Saves me some time.
jmtjr278 said:
Nah. Check his first post. He's updated to the June modded boot.img. Save yourself since time and data because the OTA does not include the boot img that I could find. I downloaded the factory image to get it. Then I downloaded the OTA. Ugh. Almost 3gb if data by the time I was finished.
Sent from my Pixel 3a using Tapatalk
---------- Post added at 09:43 PM ---------- Previous post was at 09:32 PM ----------
https://drive.google.com/file/d/1eQ9QXQqYeQityqCR2fk2jgBt7UKBA_5P/view?usp=drivesdk
Here is the one I made. Enjoy
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
sd_N said:
No. Cannot go back to pie. I had a discussion with Google rep today. She said soon as the Q beta for this month comes out, we will be able to go back to Android Pie as normal. There is an issue on their side. Here's what my error was when trying to sideload back to Pie on my VZW Pixel 3a
Click to expand...
Click to collapse
Did you try to fastboot pie factory images? That should get you back to pie, kinda weird if not.
Sent from my Pixel 3a using Tapatalk
jmtjr278 said:
Did you try to fastboot pie factory images? That should get you back to pie, kinda weird if not.
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
He has a VZW Pixel 3a. You can't fastboot a factory image with a locked bootloader. You can only sideload an OTA so he will need to wait in order to unenroll from the beta. Couple more days I think at the most.
Anyone else feel like the Multi tasking UI on the 3a has become faster after the update? Feels snappier to me
Rage1ofakind said:
Anyone else feel like the Multi tasking UI on the 3a has become faster after the update? Feels snappier to me
Click to expand...
Click to collapse
I think so. I have noticed you can swipe up from a bigger portion of the screen to show the appdrawer too. Now I can swipe up from the lower row of icons, and I think that before the update I had to swipe from the icon menu.
How do you even sideload the OTA ? When I do adb reboot recovery I just get a no command screen :/
EDIT: NVM Figured that out. When I sideload the OTA, I just get a signature verification failed error. I have a Tmobile 3a
Edit 2: I am dumb. I had the full image instead of OTA. Getting the OTA worked.
So i download the latest modded version on from pnabj "PQ3B.190605.006" then install it using this method "fastboot flash boot "whatever the boot.img is named" from the root guide and thats it?
oscar1823 said:
So i download the latest modded version on from pnabj "PQ3B.190605.006" then install it using this method "fastboot flash boot "whatever the boot.img is named" from the root guide and thats it?
Click to expand...
Click to collapse
If you have updated to the June security version and want to obtain root, then yes, flash the specific modified boot image. Then open the Magisk app and patch your boot image to complete the process.
12paq said:
If you have updated to the June security version and want to obtain root, then yes, flash the specific modified boot image. Then open the Magisk app and patch your boot image to complete the process.
Click to expand...
Click to collapse
Im already Rooted with magisk.
oscar1823 said:
Im already Rooted with magisk.
Click to expand...
Click to collapse
What are trying to do with the previously mentioned modified image?