Question Pixel 6a on Official 13 - is Root possible - Google Pixel 6a

Phone arrived today, got on the website, downloaded the latest August build. I did not notice it was 13. Unlocked the bootloader, flashed the image and the phone booted right up. I was about to root when I realized I was on 13 and then came here and saw the PSA about the phone can't be downgraded from 13 to a previous build.
My question (I've searched and found nothing), can I root the Pixel 6a on the official August 13 build with Magisc? Will I need to do anything differently like disable verifications and stuff? Usually I install the latest Magisk (v25.2), patch the boot.img, flash the patchedboot.img and profit.
Thanks in advance.

Bad Bimr said:
My question (I've searched and found nothing) can I root the Pixel 6a on the official August 13 build with Magisc?
Click to expand...
Click to collapse
Yes
Bad Bimr said:
Will I need to do anything differently like disable verifications and stuff?
Click to expand...
Click to collapse
No. Disabling verity and verification is optional.
Bad Bimr said:
Usually I install the latest Magisk (v25.2), patch the boot.img, flash the patchedboot.img and profit.
Thanks in advance.
Click to expand...
Click to collapse
Yep

Rooting Android 13 works exactly the same way as Android 12. The only thing that would prevent rooting is a locked bootloader. Google hasn't done anything to prevent root (yet).

Lughnasadh said:
Yes
Click to expand...
Click to collapse
It worked like a charm. Only thing is I cannot get YoutubeVanced to work on 13. I assume the Youtube Version in 13 is a higher build number and it will not work.
Thanks.

V0latyle said:
Google hasn't done anything to prevent root (yet).
Click to expand...
Click to collapse
I wish that, in addition to the "allow bootloader unlock" switch, there was a "don't be a nanny" switch.

Bad Bimr said:
It worked like a charm. Only thing is I cannot get YoutubeVanced to work on 13. I assume the Youtube Version in 13 is a higher build number and it will not work.
Thanks.
Click to expand...
Click to collapse
Glad it all worked out! Yeah, the version of YouTube that comes with A13 is higher than the Vanced YouTube version.

Just use the new revanced builder. It's on Reddit. There's even APKs there. You can scan for viruses if you want.
r/revancedapks
r/revancedapks: Share your revanced apks.
www.reddit.com

i wish i could unlock my bootloader, mine is still greyed out

beanaman said:
Just use the new revanced builder. It's on Reddit. There's even APKs there. You can scan for viruses if you want.
r/revancedapks
r/revancedapks: Share your revanced apks.
www.reddit.com
Click to expand...
Click to collapse
Are there any rooted versions that work with A13? Is building it simple? I didnt see anything there just doing a quick search.

Yes very simple to build. Just use the builder and follow instructions to patch current YouTube APK.
Here is link to GitHub w instructions.
How to use revanced builder on Android
A NodeJS ReVanced builder. Contribute to reisxd/revanced-builder development by creating an account on GitHub.
github.com

beanaman said:
Yes very simple to build. Just use the builder and follow instructions to patch current YouTube APK.
Here is link to GitHub w instructions.
How to use revanced builder on Android
A NodeJS ReVanced builder. Contribute to reisxd/revanced-builder development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Ok, that was stupid simple. Thanks

"Disabling verity and verification is optional"
What are the advantages or disadvantages of doing that?

beanaman said:
Just use the new revanced builder. It's on Reddit. There's even APKs there. You can scan for viruses if you want.
r/revancedapks
r/revancedapks: Share your revanced apks.
www.reddit.com
Click to expand...
Click to collapse
Thank you for this!

Bad Bimr said:
It worked like a charm. Only thing is I cannot get YoutubeVanced to work on 13. I assume the Youtube Version in 13 is a higher build number and it will not work.
Thanks.
Click to expand...
Click to collapse
Just got a pixel 6a, updated to 13, pulled Vanced Manager off my old phone, and installed it. It's working fine for me
¯⁠\⁠_⁠(⁠ツ⁠)⁠_⁠/⁠¯

Hi, how to fix this issue?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

7kAi said:
Hi, how to fix this issue?
View attachment 5804131
Click to expand...
Click to collapse
Try using the latest Platform Tools and also try using command prompt instead of PowerShell. Put the patched image in the Platform Tools folder, open up command prompt from that folder and flash.
fastboot flash boot <nameofpatchedimage>

Lughnasadh said:
Try using the latest Platform Tools and also try using command prompt instead of PowerShell. Put the patched image in the Platform Tools folder, open up command prompt from that folder and flash.
fastboot flash boot <nameofpatchedimage>
Click to expand...
Click to collapse
worked using
fastboot.exe flash boot <nameofpatchedimage>
Thanks!

people were reporting that the OTA Beta QPR2 (it was qp something) was having issues with root, but as far as I can tell, its cleared up.
Or just use AICP for the 6a. no issues. Had issues with crdroid

TechX1991 said:
people were reporting that the OTA Beta QPR2 (it was qp something) was having issues with root, but as far as I can tell, its cleared up.
Click to expand...
Click to collapse
It was QPR2 Beta 1 where root could not be obtained by flashing a patched Pixel 6 boot image, so people had to patch a Pixel 7 boot image to obtain root.
We don't know if this is "cleared up" since QPR2 Beta 2 has not been released yet.

Lughnasadh said:
It was QPR2 Beta 1 where root could not be obtained by flashing a patched Pixel 6 boot image, so people had to patch a Pixel 7 boot image to obtain root.
We don't know if this is "cleared up" since QPR2 Beta 2 has not been released yet.
Click to expand...
Click to collapse
Got it, thanks for clearing it up. I wonder if that's similar to the issues with crdroid rom. Root can't be done via recovery at all, it just errors out. When you patch the boot.img from crdroid's rom, at least for me, I had random crashes and bluetooth flat out didn't work. It would say the app for controlling bluetooth was crashing.

Related

[DISCONTINUED] Derpfest 11 alpha builds for sunfish

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I would like to share my personal derpfest 11 builds for sunfish:
Derpfest 11:
File folder on MEGA
mega.nz
boot.img for flashing first time:
File on MEGA
mega.nz
### Install instructions for custom roms ###
### (Lineage, DerpFest, Superior, Dirty Unicorns, etc) ###
- Flash stock 11 or upgrade to 11 if you are still on 10.
- Download the separate boot.img for use in next step (see notes)
- Flash the downloaded boot.img to both slots: fastboot flash --slot all boot boot.img
- Boot to recovery using the volume buttons on phone itself.
- Perform a factory reset (first install only) in the recovery menu
- Apply update from adb (Apply update >> Apply from ADB)
- Run command on PC: adb sideload zipname.zip and press enter
- Reboot
====
Device tree:
https://github.com/koen01/android_device_google_sunfish/tree/derp/
Kernel source:
https://github.com/koen01/Pixel-4/commits/kangtopia-sunfish
====
Many thanks to Dirty Unicorns and Flar2!
Using their works as base.
ny-hardcore said:
I would like to share my personal build for sunfish:
Defest 11:
https://mega.nz/file/FAdzBaLI#ImShMEXI2NSXf8e45myt6dZ06Ze79grj_Cg_dXxgDJU
====
Device tree:
https://github.com/koen01/android_device_google_sunfish/tree/derp/
Kernel source:
https://github.com/koen01/Pixel-4/commits/kangtopia-sunfish
====
Many thanks to Dirty Unicorns and Flar2!
Using their works as base.
Click to expand...
Click to collapse
Any chance you could post the boot image extracted from this so that people that want root can patch it with magisk?
beanaman said:
Any chance you could post the boot image extracted from this so that people that want root can patch it with magisk?
Click to expand...
Click to collapse
You can extract the payload.bin file with payload dumper to get the boot.img file. I can do it when I get a chance if the dev is too busy to do so. I'm kinda busy right now, but can do it later.
---------- Post added at 12:28 AM ---------- Previous post was at 12:00 AM ----------
I uploaded it to my drive after extracting payload.bin file. Here you go!!!!
https://drive.google.com/file/d/1DLsQjc0i0v4GknC4TlBL8mjvcF1wRx07/view?usp=sharing
I currently use DU and would like to try it, can someone write instructions please ?
beanaman said:
Any chance you could post the boot image extracted from this so that people that want root can patch it with magisk?
Click to expand...
Click to collapse
I uploaded it to my drive after extracting payload.bin file. Here you go!!!!
https://drive.google.com/file/d/1DLsQjc0i0v4GknC4TlBL8mjvcF1wRx07/view?usp=sharing
---------- Post added at 12:38 AM ---------- Previous post was at 12:29 AM ----------
switcher said:
I currently use DU and would like to try it, can someone write instructions please ?
Click to expand...
Click to collapse
You need to use the DU custom recovery which I assume you already have if you are using their rom. Boot to recovery and factory reset, then sideload rom.
Then boot your phone. If you want to root your phone, I supplied the boot.img file from the payload.bin file that I extracted for the dev. You can use that to patch file with magisk beta then flash that patched file in fastboot by the following, fastboot flash boot magisk_patched.img
This is awesome thank you to the dev for keeping our device alive!
Archangel said:
This is awesome thank you to the dev for keeping our device alive!
Click to expand...
Click to collapse
.....
Did you really just say that out loud about a device that is like 3 months old?
?
Sent from my Pixel 4a using Tapatalk
rignfool said:
.....
Did you really just say that out loud about a device that is like 3 months old?
?
Click to expand...
Click to collapse
Yup
Archangel said:
Yup
Click to expand...
Click to collapse
Lol
There's very little development for the 4a. This is a fact.
bobbarker2 said:
There's very little development for the 4a. This is a fact.
Click to expand...
Click to collapse
That's because since Android 11, there are many more obstacles in the way in building a rom. There is no working TWRP for our device for Android 11. Building a custom recovery into the rom is more work. These developers do this in their free time, they have full time jobs, and family.
Has anyone been successful at flashing this? When I tried, I got signature errors with install aborted. Even tried downloading the file again just to make sure that it wasn't corrupted.
Yes, and I'm betting that you are using stock recovery which is what would cause this error.
Download this: 20200913-OFFICIAL-boot.img
Download and put inside your adb tools folder. Reboot to bootloader and fastboot flash --slot all boot official-boot.img
Then boot into recovery and factory reset. Then sideload rom by the following, adb sideload rom.zip or whatever the name is called. Then reboot phone and it will work. If you want to root, I've given instructions on that previously.
fossiltkm said:
Has anyone been successful at flashing this? When I tried, I got signature errors with install aborted. Even tried downloading the file again just to make sure that it wasn't corrupted.
Click to expand...
Click to collapse
Yes, and I'm betting that you are using stock recovery which is what would cause this error.
Download this: 20200913-OFFICIAL-boot.img
Download and put inside your adb tools folder. Reboot to bootloader and fastboot flash --slot all boot official-boot.img
Then boot into recovery and factory reset. Then sideload rom by the following, adb sideload rom.zip or whatever the name is called. Then reboot phone and it will work. If you want to root, I've given instructions on that previously.
I just uploaded a new build synced with latest derpfest sources.
Also dit some changes to Devicetree for smoothnes (vulkan backend and triple buffering) and enabled the aosp blur
Check the mega folder linkt in first post for latest release
ny-hardcore said:
I just uploaded a new build synced with latest derpfest sources.
Also dit some changes to Devicetree for smoothnes (vulkan backend and triple buffering) and enabled the aosp blur
Check the mega folder linkt in first post for latest release
Click to expand...
Click to collapse
They can ignore my previous post. I appreciate your time in development here. It's limited with this device and I understand devs have full time jobs, and a family and they do what they can with their time. Much appreciated.
ny-hardcore said:
I just uploaded a new build synced with latest derpfest sources.
Also dit some changes to Devicetree for smoothnes (vulkan backend and triple buffering) and enabled the aosp blur
Check the mega folder linkt in first post for latest release
Click to expand...
Click to collapse
Your latest build is running great for me, and I love the AOSP Blur effect . One question though, are you able to set a lock screen wallpaper different from the home screen? By no means is it a big deal, just wondering if it's been working as it should for you.
I really appreciate you sharing your personal builds with us, your time as well!
fossiltkm said:
Has anyone been successful at flashing this? When I tried, I got signature errors with install aborted. Even tried downloading the file again just to make sure that it wasn't corrupted.
Click to expand...
Click to collapse
fossiltkm said:
Your latest build is running great for me, and I love the AOSP Blur effect . One question though, are you able to set a lock screen wallpaper different from the home screen? By no means is it a big deal, just wondering if it's been working as it should for you.
I really appreciate you sharing your personal builds with us, your time as well!
Click to expand...
Click to collapse
I noticed this on Superior os as well. Also navbar layout options don't work.
Edmontonchef said:
I noticed this on Superior os as well. Also navbar layout options don't work.
Click to expand...
Click to collapse
I only use gestural navigation so I can't comment on this. Will look into it to check if it's broken upstream.
fossiltkm said:
Your latest build is running great for me, and I love the AOSP Blur effect . One question though, are you able to set a lock screen wallpaper different from the home screen? By no means is it a big deal, just wondering if it's been working as it should for you.
I really appreciate you sharing your personal builds with us, your time as well!
Click to expand...
Click to collapse
I'm seeing this too. Will check with official derp.
Is there a list of features for this ROM? I'm particularly interested in navigation button customization, i.e. long-press kill-app, launch activity, toggle screen rotate, etc.

Signature Spoofing on unsuported Android 11 (R) Roms

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How to get Signature Spoofing working on Android 11 (R) Roms that have no support for Signature Spoofing?
In my Case here I use a Samsung Galaxy S8 with an unofficial LineageOS 18.1 (Android 11) by stricted
I use TWRP recovery but this should not matter !
First of all Flash your ROM and Magisk (you need to download the latest version to get Magisk working on Android 11)
Link for my ROM in case anyone needs it:
dreamlte(s8): https://images.stricted.net/test/18.1/lineage-18.1-20201231-UNOFFICIAL-dreamlte.zip
dream2lte(s8+): https://images.stricted.net/test/18.1/lineage-18.1-20201231-UNOFFICIAL-dream2lte.zip
greatlte(n8): https://images.stricted.net/test/18.1/lineage-18.1-20201231-UNOFFICIAL-greatlte.zip
Magisk Link: https://github.com/topjohnwu/Magisk/releases/tag/v21.2
Click on Build number (7x) to enable Developer Options
After that enable ADB-Debugging and Root-ADB-Debugging in your ROM in case of LineageOS go to Setting -> System -> Developer Options
So Lets go this is the more complicated part. but also really easy if you done it once.
I'm using Debian Linux but it should be possible on every OS. In Windows use the Linux Subsystem.
You need to have ADB installed on your System tho.
ADB link: https://adbdownload.com
First of all you need to download this 2 Files:
spoof_AVDapi30.zip.ONLY'MAGISK&ANDROID-STUDIO · 11-attempt · oF2pks / Haystack · GitLab
GitLab.com
gitlab.com
https://github.com/microg/GmsCore/files/5652857/microG_AVDx86api30_magiskMaRViN.zip
Rename "spoof\_AVDapi30.zip.ONLY'MAGISK&ANDROID-STUDIO" to "spoof\_AVDapi30.zip"
Next Download this zip: https://gitlab.com/oF2pks/haystack/-/archive/11-attempt/haystack-11-attempt.zip
Also download this jar file: https://github.com/DexPatcher/dexpa...nload/v1.8.0-beta1/dexpatcher-1.8.0-beta1.jar
So now unzip the haystack-11-attempt.zip and put the dexpatcher.jar file into to Folder.
This part I use Bash shell in Linux.
Bash:
adb pull /system/framework/services.jar
java -jar dexpatcher-1.8.0-beta1.jar -a 11 -M -v -d -o ./ services.jar 11-hook-services.jar.dex 11core-services.jar.dex
(After that Command you should have 4 files all named classes*.dex)
Bash:
mkdir repack
zip -j repack/services.jar classes*.dex
After that you should have a new services.jar in your repack Folder.
Now You need to open the spoof\_AVDapi30.zip go in /system/framework/ and delete the old services.jar and put your own file in. that's in your repack Folder.
Don't ruin the zip-format of the file tho because otherwise Magisk will cry while install.
After that put your spoof-AVDapi30.zip and your microG\_AVDx86api30\_magiskMaRViN.zip on your Phone and Flash via Magisk.
Reboot and you hopefully have Signature spoofig working. If you run in any Problems check out the GitHub Links here. there will be comments that maybe will help.
I also want to credit the real developers of this
on xda: Lanchon (DexPatcher & Haystack)
https://forum.xda-developers.com/m/lanchon.4141005/
I'm Sorry if there is ****ty English.
The best of luck for you guys i hope this helps.
Hello, I have a question, this ROM for the S8, is it in beta? or can it be used normally?
Thanks a lot, with the help of your instructions and files I installed it on my Mi Note 10 (tucana) with LineageOS 18.1!
However, it's not working when Magisk Hide is activated - any idea to combine both?
Thanks a lot too ~~ is very working grade ~~
Eriizoo said:
Hello, I have a question, this ROM for the S8, is it in beta? or can it be used normally?
Click to expand...
Click to collapse
Beta
DeanPhoenix said:
Thanks a lot too ~~ is very working grade ~~
Click to expand...
Click to collapse
No problem
UniNick said:
Thanks a lot, with the help of your instructions and files I installed it on my Mi Note 10 (tucana) with LineageOS 18.1!
However, it's not working when Magisk Hide is activated - any idea to combine both?
Click to expand...
Click to collapse
No sorry it shoud be working.
Thank you so much, worked like a charm on an unofficial LineageOS 18.1 ROM running on Lenovo K6 Power
Good stuff man. It really works. Got this running on LOS unofficial 18.1 on a Samsung G970F. Big
Kingslayer9988 said:
...
If you run in any Problems check out the GitHub Links here. there will be comments that maybe will help.
...
Click to expand...
Click to collapse
Check https://gitlab.com/Nanolx/NanoDroid/-/issues/169 for more specifics
LINK for s8?
Thom'S said:
LINK for s8?
Click to expand...
Click to collapse
dreamlte(s8): https://images.stricted.net/test/18.1/lineage-18.1-20201231-UNOFFICIAL-dreamlte.zip
dream2lte(s8+): https://images.stricted.net/test/18.1/lineage-18.1-20201231-UNOFFICIAL-dream2lte.zip
greatlte(n8): https://images.stricted.net/test/18.1/lineage-18.1-20201231-UNOFFICIAL-greatlte.zip
the link does not work, it gives me a "cardboard" instead of the download. How can i download this rom?
Thom'S said:
the link does not work, it gives me a "cardboard" instead of the download. How can i download this rom?
Click to expand...
Click to collapse
Sorry links got updated I fixed it.
dreamlte(s8): https://images.stricted.net/test/18.1/lineage-18.1-20201231-UNOFFICIAL-dreamlte.zip
dream2lte(s8+): https://images.stricted.net/test/18.1/lineage-18.1-20201231-UNOFFICIAL-dream2lte.zip
greatlte(n8): https://images.stricted.net/test/18.1/lineage-18.1-20201231-UNOFFICIAL-greatlte.zip
Kingslayer9988 said:
Don't ruin the zip-format of the file tho because otherwise Magisk will cry while install.
After that put your spoof-AVDapi30.zip and your microG\_AVDx86api30\_magiskMaRViN.zip on your Phone and Flash via Magisk.
Click to expand...
Click to collapse
So Magisk cried! It said not a Magisk module and 'installation failed'.
I re-zipped the spoof-AVDapi30 folder with included jar file, re-zipped by right clicking in Dolphin file manager and compressing as zip.
What am I doing wrong? How do I not ruin the zip-format? Thanks.
Thanks.
nb. I also renmaed it spoof\_AVDapi30.zip
Still the same fail.
anarchotaoist said:
So Magisk cried! It said not a Magisk module and 'installation failed'.
I re-zipped the spoof-AVDapi30 folder with included jar file, re-zipped by right clicking in Dolphin file manager and compressing as zip.
What am I doing wrong? How do I not ruin the zip-format? Thanks.
Thanks.
nb. I also renmaed it spoof\_AVDapi30.zip
Still the same fail.
Click to expand...
Click to collapse
Would I be able to fastboot sideload spoof\_AVDapi30.zip ??
anarchotaoist said:
So Magisk cried! It said not a Magisk module and 'installation failed'.
I re-zipped the spoof-AVDapi30 folder with included jar file, re-zipped by right clicking in Dolphin file manager and compressing as zip.
What am I doing wrong? How do I not ruin the zip-format? Thanks.
Thanks.
nb. I also renmaed it spoof\_AVDapi30.zip
Still the same fail.
Click to expand...
Click to collapse
Just open the zip on windows winrar on linux just click it. Go and find the .jar delete it and click on addfile and add yours. Pretty basic and if you know how to make a magisk-flashable zip you can also do that but my way is just a shortcut. But dont UNZIP.
anarchotaoist said:
Would I be able to fastboot sideload spoof\_AVDapi30.zip ??
Click to expand...
Click to collapse
I don't know about that but someone here more knowelaged then me will tell you probably.
what about gapps? no more contacts, maps, play store etc?
walid_loulou said:
what about gapps? no more contacts, maps, play store etc?
Click to expand...
Click to collapse
If you wan't Gapps don't install MicroG

Need Help for downloading GApps for LineageOS 17.1

Hello;
I am perhaps the newest member of the forum and I am in urgent need of assistance.
My problem:
I was unable to install the associated GApps file while installing the LineageOS 17.1 system on my LG G3 D855 phone. During the installation, the device gave an error warning -I think Error 70- and I completed the installation before I could install the GApss file.
Now; LineageOS 17.1 is installed on my device. However, there is no Google Play application on my device.
How should I go about installing Google Play applications on my device?
As someone who knows very little about installing new software on the phone, I have been able to do this much. Keeping this in mind, I will be happy if you can give me the solution suggestions, starting from the simplest possible.
Thanks..
yakari.the.redskin said:
Hello;
I am perhaps the newest member of the forum and I am in urgent need of assistance.
My problem:
I was unable to install the associated GApps file while installing the LineageOS 17.1 system on my LG G3 D855 phone. During the installation, the device gave an error warning -I think Error 70- and I completed the installation before I could install the GApss file.
Now; LineageOS 17.1 is installed on my device. However, there is no Google Play application on my device.
How should I go about installing Google Play applications on my device?
As someone who knows very little about installing new software on the phone, I have been able to do this much. Keeping this in mind, I will be happy if you can give me the solution suggestions, starting from the simplest possible.
Thanks..
Click to expand...
Click to collapse
The Open GApps Project
OpenGApps.org offers information and pre-built packages of The Open GApps Project. The Open GApps Project is an open-source effort to script the automatic generation of up-to-date Google Apps packages. All Android versions and platforms supported.
opengapps.org
Austinredstoner said:
The Open GApps Project
OpenGApps.org offers information and pre-built packages of The Open GApps Project. The Open GApps Project is an open-source effort to script the automatic generation of up-to-date Google Apps packages. All Android versions and platforms supported.
opengapps.org
Click to expand...
Click to collapse
i read there but i didn't fix my problem.
Said before that i'm not experienced person about installing software to the phones. is it possible to tell me the instructions step by step?
For example: how can i root my device with LineageOS 17.1?
Google Play Store app isn't part of any GApps distribution, AFAIK.
You have to download and install it at yourself:
Google PLAY (Android)
The best place to buy movies, books and apps for Android
google-play.en.uptodown.com
jwoegerbauer said:
Google Play Store app isn't part of any GApps distribution, AFAIK.
You have to download and install it at yourself:
Google PLAY (Android)
The best place to buy movies, books and apps for Android
google-play.en.uptodown.com
Click to expand...
Click to collapse
i downloaded the Google Play Apk from the link above you sent. Then tried to open but it didn't work.
in my opinion; i need the instruction that how to root my device with LineageOs 17.1
Are the any application that you advice for rooting the device easily?
yakari.the.redskin said:
i downloaded the Google Play Apk from the link above you sent. Then tried to open but it didn't work.
in my opinion; i need the instruction that how to root my device with LineageOs 17.1
Are the any application that you advice for rooting the device easily?
Click to expand...
Click to collapse
OMG. You have to install the downloaded APK.
jwoegerbauer said:
OMG. You have to install the downloaded APK.
Click to expand...
Click to collapse
i Did. But it didn't work.
Anyway; how can i root my device? Do you have any Application Advice for root it easily?
yakari.the.redskin said:
i Did. But it didn't work.
Anyway; how can i root my device? Do you have any Application Advice for root it easily?
Click to expand...
Click to collapse
Use magisk
1st download magisk with this link
Download Magisk Manager Latest Version 26.1 For Android 2023
Magisk Manager is an app which helps users to root their phone. With the help of Magisk you can run banking apps and also pass SafetyNet tests.
magiskmanager.com
2nd open magisk
3rd step rename magisk apk file to .zip example
If the file name is Magisk-v22.0.apk u would rename that to Magisk-v22.0.zip
4th step boot into recovery
5th flash the magisk zip file
6th boot out of recovery than use a root checker to see if u successfully installed magisk
yakari.the.redskin said:
i Did. But it didn't work.
Anyway; how can i root my device? Do you have any Application Advice for root it easily?
Click to expand...
Click to collapse
Google Play Store app doesn't require phone's Android is rooted.
jwoegerbauer said:
Google Play Store app doesn't require phone's Android is rooted.
Click to expand...
Click to collapse
i think he's asking two question in one thread lol
With OP only ONE question was asked what I referenced to. I am not interested in answering the question that was postponed.
jwoegerbauer said:
With OP only ONE question was asked what I referenced to. I am not interested in answering the question that was postponed.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Austinredstoner said:
Use magisk
1st download magisk with this link
Download Magisk Manager Latest Version 26.1 For Android 2023
Magisk Manager is an app which helps users to root their phone. With the help of Magisk you can run banking apps and also pass SafetyNet tests.
magiskmanager.com
2nd open magisk
3rd step rename magisk apk file to .zip example
If the file name is Magisk-v22.0.apk u would rename that to Magisk-v22.0.zip
4th step boot into recovery
5th flash the magisk zip file
6th boot out of recovery than use a root checker to see if u successfully installed magisk
Click to expand...
Click to collapse
Thanks to you, I fixed my problem.
yakari.the.redskin said:
Thanks to you, I fixed my problem.
Click to expand...
Click to collapse
glad it worked for u
U can mark mine as solution if u want

[ROM][11.0][Unofficial] LineageOS 18.1 with microG [hotdogb][Updated 05/09]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is my daily driver that I have decided to share. With the increase of big tech and government overreach in our lives, I felt more of a desire to move away from Google and the similar. Hotdogb isn't supported by other similar OS' so built this from microG/LineageOS source and is fully functional.
Based on Android 11
Last Updated: May 5th
Kernel Source: GitHub
Donate if you enjoy!​Changelogs:
05.09.2021 - Updated to LineageOS nightly 05.09.2021. Full changelog can be found at https://download.lineageos.org/hotdogb/changes.
05.05.2021 - Initial Release.
What is this?
This is LineageOS with all closed-source binary Google blobs removed and replaced with microG. I.E no Play services or GAPPS. UnifiedNLP is used as networking location provider vice Google's NLP. F-Droid is installed by default providing alternative app store. However, with Aurora store you can still install Google Play store apps with ease (requires additional installations).
Installation
Since this is a fork of LineageOS you can follow the same installation guide they provide here. Just ensure you are on Lineage recovery and ready to sideload LineageOS, use our ROM for that step.
Issues
None known. Post below if you have any.
Post Installation
- open the microG app --> Self-Check sections are successful.
Location services
- By default, MozillaNlpbackend, which uses Mozilla location service and NominatimNlpBackend, which uses Mapquest's Noninatim service; are disabled by default. Open microG app --> Location modules and enable whichever ones you prefer. Afterwards reboot device.
Other information
Google Play Store Alternative
If you want full access to normal android Play Store apps do the following:
Open F-Droid app. Search for Aurora Store and install. Once opened select the appropriate option, generally option #1 will be the most common used with this ROM as long as it has not been modified by the user. Once setup you will have access to all applications as normal.
Some apps require play services and I cannot use them, please help!
This will require both SU and Magisk installed, which is not provided in our base rom. Once you have achieved SU with Magisk you will need to read over and install NanoDroid which can be found here XDA| Website.
SuperUser
***Ensure boot.img date matches the date of the ROM you are installing. DO NOT use this boot.img with a different ROM.***
***This guide assumes you already have a working ADB/Fastboot.***
Download boot.img below to your phones storage.
Download latest Magisk apk from here to your device and install it.
Open Magisk on your phone. Click the Magisk Install option within the app.
For method "Select and Patch a File"
Select the boot.img you downloaded in Step 1.
Once the process is complete a Magisk patched boot.img will be in the Downloads folder on your phone. Drag it to a working folder on your Computer.
Ensure your has ADB debugging enabled in Developer Options settings and that your PC is authorized.
Open Command Prompt on your PC and run ADB Devices. Verify your phone is listed.
In Command Prompt run "ADB reboot bootloader". You will notice the phone reboot.
Once on Fastboot screen in Command Prompt run "Fastboot devices", ensure your phone is listed.
In Command Prompt run "Fastboot flash boot bootname.img. Replacing bootname with the name of your Magisk boot.img.
Once done start the device and load Magisk to confirm.
Download
Donate if you enjoy!
ROM (5.9.21)
BOOT.IMG (5.9.21)
Thanks for posting, I was looking to switch over to microG now with LOS 18.1 for hotdogb
Just wanna confirm, will these builds support OTA updater/dirty flashing for updates?
Vedarshi said:
Thanks for posting, I was looking to switch over to microG now with LOS 18.1 for hotdogb
Just wanna confirm, will these builds support OTA updater/dirty flashing for updates?
Click to expand...
Click to collapse
You will be able to dirty flash future updates similiar to LOS. Just be aware if you have modded any system files i.e. NanoDroid system install vice using Magisk; then you will have to reapply after dirty flash.
I'm working on OTA updates in the next release, just haven't set the hosting up at the moment.
Can I flash this right over top of the Official Lineage for HotdogB, or do I have to go stock 1st?
Thanks
Droid_Nut said:
Can I flash this right over top of the Official Lineage for HotdogB, or do I have to go stock 1st?
Thanks
Click to expand...
Click to collapse
I would recommend loading recovery Factory Reset, then Format data / factory reset. Dirty flash might work, but I have not tested it. It also may come with unwanted consequences.
jivy26 said:
I would recommend loading recovery Factory Reset, then Format data / factory reset. Dirty flash might work, but I have not tested it. It also may come with unwanted consequences.
Click to expand...
Click to collapse
I was going to factory reset anyways, since I never really made the Official Lineage a daily driver. I was really waiting for MicroG before I went all out.
Thanks for the effort.
All installed, and all the boxes are checked in MicroG! Thanks!
Droid_Nut said:
All installed, and all the boxes are checked in MicroG! Thanks!
Click to expand...
Click to collapse
No worries, I added the boot.img in case anyone wants to patch with Magisk. I had to do so and also install NanoDroid as a Magisk module to use a few apps that were expecting play store services.
How do I import google contacts?
HueyT said:
How do I import google contacts?
Click to expand...
Click to collapse
https://contacts.google.com
Click export then Vcard. Go into contacts on phone import then select the file.
jivy26 said:
No worries, I added the boot.img in case anyone wants to patch with Magisk. I had to do so and also install NanoDroid as a Magisk module to use a few apps that were expecting play store services.
Click to expand...
Click to collapse
I ended up using a boot.img that I had already patched in LOS Official.
Do you have a link or a download for the NanoDroid. It does not show up in the Magisk Module search?
HueyT said:
How do I import google contacts?
Click to expand...
Click to collapse
Once you go with MicroG you are out of the Google Eco System. And dont try to log in as they may wipe out your email and cancel you. I just imported my contacts, as suggested.
Droid_Nut said:
I ended up using a boot.img that I had already patched in LOS Official.
Do you have a link or a download for the NanoDroid. It does not show up in the Magisk Module search?
Click to expand...
Click to collapse
It is linked in my initial post.
I managed to get wear working, but if I open the app it tells me to get it from the playstore, and breaks connection to my watch.
Droid_Nut said:
Once you go with MicroG you are out of the Google Eco System. And dont try to log in as they may wipe out your email and cancel you. I just imported my contacts, as suggested.
Click to expand...
Click to collapse
Use MicroG to be the go-between for Google eco. You can login through MicroG if you have an app that is in need of it and MicroG will be the in-between.
Droid_Nut said:
I managed to get wear working, but if I open the app it tells me to get it from the playstore, and breaks connection to my watch.
Click to expand...
Click to collapse
Yes uninstall it. Install NanoDroid then install it from Aurora after you installed NanoDroid in Magisk module and rebooted.
jivy26 said:
It is linked in my initial post.
Click to expand...
Click to collapse
That's a big list, which one should I get? https://downloads.nanolx.org/NanoDroid/Stable/
Droid_Nut said:
That's a big list, which one should I get? https://downloads.nanolx.org/NanoDroid/Stable/
Click to expand...
Click to collapse
https://downloads.nanolx.org/NanoDroid/Stable/NanoDroid-23.1.2.20210117.zip
jivy26 said:
Use MicroG to be the go-between for Google eco. You can login through MicroG if you have an app that is in need of it and MicroG will be the in-between.
Click to expand...
Click to collapse
I heard it is against the terms, so it is safe to log into microg and get the apps that you paid for?
Droid_Nut said:
I heard it is against the terms, so it is safe to log into microg and get the apps that you paid for?
Click to expand...
Click to collapse
Of course its against their terms and you can login, but there is always the risk your account is banned. Though I have never had an issue.
If you're weary you can always make a separate Google account and use to try it out.

Question HELP!!! Pixel 7 Pro rooted - Magisk N/A [SOLVED]

Hi,
My Pixel 7 Pro has a problem.
My phone has QPR3 Beta 3 T3B3.230413.003.
The phone is rooted but Magisk dosen't work and root access and modules icons are grayed out.
I tried to patch the phone with PixelFlasher and ADB, but no way.
Attached you will find the screenshot of Magisk App.
Please help me.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm confused. I'd say... you're not rooted?
I'M ROOTED...
Yeah that's weird then
When you open a root app, does it request root?
krakout said:
Yeah that's weird then
When you open a root app, does it request root?
Click to expand...
Click to collapse
Just a thought - could it be you patched with another Magisk version rather than the official one?
krakout said:
Just a thought - could it be you patched with another Magisk version rather than the official one?
Click to expand...
Click to collapse
Installed Greenify. No root request. Attached the creenshot. I installed Magisk from the Github site. 26.1 version.
podon81 said:
Hi,
My Pixel 7 Pro has a problem.
My phone has QPR3 Beta 3 T3B3.230413.003.
The phone is rooted but Magisk dosen't work and root access and modules icons are grayed out.
I tried to patch the phone with PixelFlasher and ADB, but no way.
Attached you will find the screenshot of Magisk App.
Please help me.
Click to expand...
Click to collapse
Do you have another version of the Magisk app hidden? If so, uninstall it.
Also, what exact steps did you take to root?
^^^^ You most likely have another Magisk on your phone, but it's hidden.
That's why apps that previously had root still work.
Go through the apps list and look for the app "Settings" without an icon.
Ripthulhu said:
^^^^ You most likely have another Magisk on your phone, but it's hidden.
That's why apps that previously had root still work.
Go through the apps list and look for the app "Settings" without an icon.
Click to expand...
Click to collapse
Yeah but if that were the case the apps would ask for root and the prompt would appear.
Nope it doesn't. Not in this scenario
Ripthulhu said:
Nope it doesn't. Not in this scenario
Click to expand...
Click to collapse
"This scenario" meaning two managers? Actually yes, the prompt is given. I witnessed it myself (again) yesterday.
It seems like you are having trouble getting root access and modules to work on your Pixel 7 Pro. Try these things if they can work-
Update to the latest version of Magisk.
Uninstall and reinstall Magisk.
Check your device's firmware compatibility.Open the Magisk app and go to Settings. Check that the "Magisk Hide" option is enabled and that the "Magisk Core Only Mode" option is disabled.
If none of the above steps work, you may need to flash the stock firmware on your device.
Just try I am hopeful that it will resolve your issue.​
krakout said:
"This scenario" meaning two managers? Actually yes, the prompt is given. I witnessed it myself (again) yesterday.
Click to expand...
Click to collapse
I was in the same scenario and it did not prompt me for new apps.
Apps previously granted root would still work, but new ones didn't.
Ripthulhu said:
I was in the same scenario and it did not prompt me for new apps.
Apps previously granted root would still work, but new ones didn't.
Click to expand...
Click to collapse
Fair enough, I don't remember about new apps to be honest.
anyabaker said:
It seems like you are having trouble getting root access and modules to work on your Pixel 7 Pro. Try these things if they can work-​​Update to the latest version of Magisk.​Uninstall and reinstall Magisk.​Check your device's firmware compatibility.Open the Magisk app and go to Settings. Check that the "Magisk Hide" option is enabled and that the "Magisk Core Only Mode" option is disabled.​If none of the above steps work, you may need to flash the stock firmware on your device.​​Just try I am hopeful that it will resolve your issue.​
Click to expand...
Click to collapse
No way to access to the options you mentioned... Look at screenshot pls...
What version of Magisk are you flashing?
Others on the thread....wasn't there a bug on certain Magisk canary versions where root checks were passing and root access was supposedly given to apps, but Magisk wasn't able to implement modules or confirm its own root status? It most likely has to do with that and/or in conjunction with being on a QPR as well....
simplepinoi177 said:
What version of Magisk are you flashing?
Others on the thread....wasn't there a bug on certain Magisk canary versions where root checks were passing and root access was supposedly given to apps, but Magisk wasn't able to implement modules or confirm its own root status? It most likely has to do with that and/or in conjunction with being on a QPR as well....
Click to expand...
Click to collapse
Version 26.1 stable
podon81 said:
Version 26.1 stable
Click to expand...
Click to collapse
Hmmm...interesting...
I forgot where I saw it -- it might've been in the main Magisk thread here on XDA, or in one of the Pixel 7 Pro rooting guides, might've even been a PixelFlasher thread -- but there was an issue (I believe it was canary 25206-25209 or something like that) that spoke about this similar issue; root detection would detect root and apps wouldn't put up a warning of lack of root access, but Magisk itself wouldn't confirm its own root status, the modules couldn't be activated, and the apps couldn't actually accomplish the tasks that required root -- it just wouldn't put up a warning/error stating it was lack of root access. I can't recall whatever came of it; I believe it was either downgrading to stable or updating to higher canary of 25210, but I can't recall off the top of my head. I do believe being on QPR was a factor, but I might be misremembering...
I suggest you try "finegling" the search function as best you can and see what users ended up doing...I'll see if I can't find it later...
Just to note, T3B3 runs fine with 26101 for me.

Categories

Resources