yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] b8842dc0:
It isn't clear from your reply whether you are saying that you did that, previously, and it didn't work, or you just now tried it and it failed/succeeded. Regardless, those are the exact steps I used. If you are having problems with those steps, you need to provide more info. Are you getting any error messages? Also, you mentioned supersu. Don't use supersu! If you have that installed already, that is your problem.

Frequently Asked Questions

The Magic Mask for Android

topjohnwu.github.io

Installation

The Magic Mask for Android

topjohnwu.github.io
[Pixel C Android Development] pitchdown:
Hi, the procedure is working ok with magisk 2.2

Also no errors, but in lingeos i don`t have root-access (checked with root checker).
[Pixel C Android Development] b8842dc0:
Forget root checker. Open the magisk app on your device and see what is going on.
[Pixel C Android Development] b8842dc0:
Also, take a look at this page:

{{color text="Magisk and MagiskHide Installation and Troubleshooting gu:Magisk and MagiskHide Installation and Troubleshooting guide

www.didgeridoohan.com
[Pixel C Android Development] pitchdown:
In magisk app i can install the app, but i can`t see it`s rooted. When starting apps needing root (screen2auto) this isn`t working correct.
[Pixel C Android Development] b8842dc0:
Well, I'm out of ideas. If the troubleshooting guide I linked to doesn't help, you will need to get support from the Magisk folks. Good luck.
[Pixel C Android Development] pitchdown:
I think i did find a part of the problem.

When running magisk in android i see that the app is installed, but NOT magisk (the first one)

Installation : not available

I did the process within TWRP using Magisk-v22.0.zip (renamed from the .apk). But it seems it is not installed?

I just did the installation of the .zip again from TWRP, but still same result. What is going wrong?
[Pixel C Android Development] Alxoom33:
First turn off Magisk hide in Settings.Then, try it again with Magisk 22005.apk/zip and flash zip in TWRP.😄 There is a compatibility issue with Magisk hide.
[Pixel C Android Development] pitchdown:
Is a new recovery needed for this? 22005 as zip in recovery, and same file as apk in android?
[Pixel C Android Development] Alxoom33:
I always update my TWRP recovery. But probably not absolutely necessary. The rest is correct. Good luck, it should work.
[Pixel C Android Development] pitchdown:
Tried 22005.

Stil same issue (see picture)

With earlier version of magisk i did have magisk-app installed. With this version also n/a with the app (22005).

I have done now more then 10 times new flesh for my s10 with Lineageos 18.1 with 6 different magisk zips/apk.

All same result --> magisk is not installed when checking the app in android....

What is going wrong??
[Pixel C Android Development] brackenhill_mob:
Looks like something is blocking magisk from using the internet as app latest version is show as n/a. Might be worth starting there 😉
[Pixel C Android Development] pitchdown:
What could this be?
[Pixel C Android Development] brackenhill_mob:
Are you running some sort of firewall or VPN that is blocking access to the net for magisk?
[Pixel C Android Development] frozenemberz:
Will this method work to get wide vine l1?

https://xdaforums.com/t/netflix-hd-on-tab-s2.3274295/page-13
[Pixel C Android Development] Alxoom33:
Did you disable Magisk hide before trying to update Magisk¿
[Pixel C Android Development] pitchdown:
You mean on my computer or network or on the phone?

Is magisk connecting to outside for this to work? It is not a local run on the phone only?
[Pixel C Android Development] brackenhill_mob:
On your phone, although if you run a VPN or proxy on your network it might be worth turning it off or bypassing it for your phone while you debug this. Magisk runs locally but checks for newer versions when it loads. Your photo shows that this online check isn't working.
[Pixel C Android Development] pitchdown:
It is a clean install of lineage os. So no vpn or firewall running.
[Pixel C Android Development] ipdev:
If you are looking for a Samsung Galaxy S10, you have the wrong thread.

That is more than a bit Off-Topic for this thread. ;)

Samsung Galaxy S10 - xda forum - Link

Magisk - xda forum - Link

Magisk General Support / Discussion - xda thread - Link

I see you found this next one. ;)

[Magisk] Root for the Galaxy S10 Series - xda thread - Link

--

General note about Magisk.

There are some regressions in the last few canary builds.

They are being fix as fast as they can be.

Magisk - GitHub - Pull Request - Link

This issue might be what you are experiencing.

Magisk - GitHub - Issue #4047 - Link

There was one or two suggestions on a work-a-round.

--

Not that we are not willing to help but, what what works for one device might not work on another.

Generally better to ask in the Magisk threads or your device threads.

--

Sorry all for a bit more OT. 🙃

Cheers all. :cowboy:
[Pixel C Android Development] wqhjstudios:
to anyone thinking about giving this a try, i say go for it. the dev's that worked on this have done a stellar job. just stellar.
[Pixel C Android Development] j04nd03:
Hi,

as I've scooped up two more Pixel Cs on eBay some time ago (dirt cheap nearly unused 64GB versions with original keyboards, so I couldn't resist) and would like to use all three in my home WLAN, can the fixed MAC address be changed/overwritten somehow, probably by patching the NVRAM?

If not, are there any plans to fix this for LOS 18.1 in the near future? I'd prefer to install the latest LOS on all my devices, but since the two new Pixel Cs are gathering dust since two months now because of this, I'd probably have to look for another ROM if this problem can't be fixed.

Cheers,

JD
[Pixel C Android Development] piraton666:
Hi,

I'm new to LineageOS and yesterday I flashed the latest image on my PixelC.

After flashing the zip thru ADB sideload inside TWRP, I tried to flash the Google Apps (MindTheGapps) and also the LineageOS AddOn SU but both failed. (following instructions here: https://wiki.lineageos.org/devices/dragon/install)

Do I need to reboot between installs?. Once the image is flashed, I get the option to reboot so not sure.

Thanks
[Pixel C Android Development] j04nd03:
I can't help with your Gapps problem, but the su addon can't work, since there are only builds up to LOS 16. I'd suggest to use Magisk instead, as advised in the installation instructions.
[Pixel C Android Development] ipdev:
As @j04nd03 already mentioned, the Lineage SU addon is depreciated.

Magisk is the current preferred root provider.

---

As for MindTheGapps, I have seen mention and links to SDK30 (Android 11) downloads in other threads.

I have not tried the builds or build them myself yet.

GitLab was updated to SDK30.

Last time I looked (few months ago) it was still SDK29 (Android 10).

MindTheGapps - GitLab - Link

New downloads are still using javelinanddart's download folder on Codefire.

MindTheGapps Downloads - Codefire - Link

---

Just tested MindTheGapps-11.0.0-arm64-20210328_143848.zip

- Had an issue mounting system for me.

Note:

My dragon developed an issue in the last few weeks.

I have to fight around TWRP finding an encryption flag, OpenGApps installs. MindTheGapps fails.

LineageOS recovery (dragon) can not install OpenGApps or MindTheGapps.

OpenGApps fails on size. MindTheGapps fails due to mounting system.

I ran a personal build of l18.1 dragon (a few days ago) to get a l18.1 recovery image for testing my encryption issue.​

I use personal builds of OpenGApps.

[ROM][flo|deb][UNOFFICIAL][LineageOS 18.1] -> 2021-01-06 xda thread - Post 3,267 - Link

Feel free to use is you want. :)

---

Cheers all. :cowboy:
[Pixel C Android Development] j04nd03:
Does your build include resizing of the system partition, or should this still be done before flashing Gapps from within TWRP?
[Pixel C Android Development] Alxoom33:
I like Open Gapps ARM -64 Mini test package for A11. Full package works as well. This Dragon has a big System partition and can pack a lot of gapps!
[Pixel C Android Development] ipdev:
The post I linked to was in a thread for a different device.

For Nexus 7 (2013) [deb/flo] you have to (re)partition to install newer roms.

That was the post I gave a link to my fork of OpenGApps and a link to downloads.

A bit cleaner and easier to keep one post updated instead of posting links and notes across threads.

Installing GApps (OpenGApps, BitGApps, NikGApps, MindTheGapps, ..) has nothing to do with resizing.

Resizing, if needed, happens when a rom is installed.

Partitioning is different from resizing an image.

When you flash an image in recovery it basically restores a backup to a specific partition. As long as the image is equal to or smaller than the partition, it will restore the image. If the image is smaller than the partition it is being restored to, there is unused/extra space in the partition. To make the extra space available, you have to resize (expand) the image to use the whole partition space.

When you wipe/format a device you are just erasing what is stored in the partition.

The only time a partition size changes is if you manually change them.

Once the partition for system is (re)partitioned to say 1.2G, it will always have 1.2G allocated for system even if the system image you flash is only 850M. System will only have 850M available since the rest of the (system partition) is unallocated. So you have to resize system to fill the whole (system partition) to be able to use the 1.2G space allocated.

Pixel C [Dragon] is built using the stock partition sizes.

No need to partition or resize.​

followmsi - android_device_google_dragon (BoardConfig - Line 72) - GitHub - Link

Dragon has a 3.5G system. ;)

LineageOS 18.1 only uses 1.2G (1263M) leaving the rest of system free for Gapps.

Cheers. :cowboy:
[Pixel C Android Development] ipdev:
Nice big 3.5G system. :love:

Even using OpenGApps stock, there is still 712M free in system. :D

Cheers. :cowboy:
[Pixel C Android Development] j04nd03:
Thanks for the clarification.

I wasn't sure because here you wrote

"LineageOS recovery (dragon) can not install OpenGApps or MindTheGapps.

OpenGApps fails on size."

Cheers, JD
[Pixel C Android Development] Alxoom33:
Yeah. Huge System partition. Can install almost any Gapps package that's for ARM 64 device.
[Pixel C Android Development] funguy2:
!!!!!!

attention do not execute "fastboot erase recovery" this command has destroyed my tablet

!!!!!!!

# fastboot getvar unlocked

unlocked: yes

Finished. Total time: 0.000s

# fastboot getvar secure

secure: yes

Finished. Total time: 0.000s

# fastboot --version

fastboot version 31.0.1-7187441

version-bootloader: Google_Smaug.7900.139.0

product: dragon

# fastboot flash recovery twrp-3.5.1_9-0-dragon.img

..

Writing 'recovery' FAILED (remote: 'unsupported command')

fastboot: error: Command failed

# fastboot boot twrp-3.5.1_9-0-dragon.img

..

Booting FAILED (remote: 'image verification failed')

fastboot: error: Command failed

Same problem with stock image

# ryu-opm8.190605.005-factory-25b457f3\ryu-opm8.190605.005>flash-all.bat

Sending 'bootloader' (16384 KB) OKAY [ 0.548s]

Writing 'bootloader' FAILED (remote: 'unsupported command')

fastboot: error: Command failed

Rebooting into bootloader OKAY [ 0.000s]

Finished. Total time: 0.000s

--------------------------------------------

Bootloader Version...: Google_Smaug.7900.139.0

Baseband Version.....: N/A

Serial Number........: unknown variable

--------------------------------------------

extracting android-info.txt (0 MB) to RAM...

Checking 'product' OKAY [ 0.000s]

Checking 'version-bootloader' OKAY [ 0.016s]

Checking 'partition-size:system' OKAY [ 0.016s]

Snapshot cancel FAILED (remote: 'unknown command')

fastboot: error: Command failed

Press any key to exit...

.. and adb "fwtool vbnv write dev_boot_fastboot_full_cap 1" is not possible because twrp or recovery is deleted

basically the same problem as in thread:

https://xdaforums.com/t/bricked-pixel-c-no-recovery-no-os-fastboot-errors.3956596/

.. with not solution

now i own a tablet for the trash can
[Pixel C Android Development] followmsi:
LineageOS 18.1

The monthly security updates ..

lineage-18.1-20210406-UNOFFICIAL-dragon.zip

Changes:

- Google Security updates -> April 2021

- Backport of Wifi-Display (Miracst) for Android 11

- Patched frameworks/base to support microG

- Latest LineageOS changes for Android 11

Enjoy :p
[Pixel C Android Development] ipdev:
Hi. :)

Sorry to hear you are having issues. :(

I use those same steps on most devices that support fastboot.

Newer devices use fastboot_d to modify critical partitions. Slightly different if fastboot_d is also used.

Some devices [Example: OnePlus 6T] do not let you modify critical partitions using fastboot. (no fastboot_d).

I skimmed the thread you linked.

One thing to note, try using a USB 2.0 port.

USB 3.0 and/or USB-C ports can cause unexpected/unwanted issues with some devices.

You can normally use a USB hub that has a 2.0 port if you do not have a USB 2.0 port on your computer.

I still use a USB 2.0 port for flashing every device, including a Pixel 5.​

Did you try different cables and USB ports?

Connection issues can cause the failed command so, make sure you test different cables and USB ports.

Just because the device can connect and is recognized in fastboot does not always mean it is a proper connection.

Basic commands like erase will work. Flash will push it to the device but the device can not write the image.

The cable I used for years (a USB 3.0 rated cable), works with all but two of my devices.

My OnePlus 6T would work with adb and partially with fastboot.

Now I just use the USB 2.0 rated cable that worked with my OnePlus 6T for everything.​

Newer versions of fastboot do not seem to play well with older devices.

The snapshot error that halts the fastboot update is because it is not supported by the device.

Same thing happens on other/older devices.

You have to unzip image-ryu-opm8.190605.005.zip and then flash each partition by name.

Not sure if it will boot, normally you have to factory reset/format cache and data in stock recovery to get it to boot.

fastboot -w (fastboot format cache and data) generally errors out with newer fastboot.

It is one of the reasons I stopped using the fastboot -w and fastboot format commands on older devices.

This is the script I used to flash ryu-opm8.190605.005 the last few weeks while testing Magisk canary builds.

I unzip image-ryu-opm8.190605.005.zip to a directory then run the script from there.

You may need to make adjustments for Windows.

fastboot erase boot
fastboot erase recovery
fastboot reboot bootloader
fastboot erase system
fastboot erase vendor
#
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash boot boot.img

Skip the erase parts and just flash boot, system, vendor and recovery again.

If boot, system and vendor flash you might be able to boot it?

Try fastboot -w and see what happens.

Note: this will erase cache and data then try to format both.

I do not remember for sure but, I think this might be your issue.

secure: yes

Hope something here helps you figure out what path to look down.

Hope you can recover.

Do not give up too quick. ;)

I have not been actively using this device in a while so, I do not remember all the oddities and quirks.

Sorry, I do not have much time this week so, I will not be able to look into it until the weekend.

Cheers. :cowboy:
[Pixel C Android Development] dsapac:
I updated from previous build Just flashed rom gapps and magisk I changed webview to bromide and for now I use bromide browser instead of Firefox For Youtube I use Vanced and it's working great for 1080p and up Problem is still that a lot of apps have delay when loading Netflix is working in sd quality App from my IPTV provider doesn't have any problem From the most part device is snappy and responsive
[Pixel C Android Development] frozenemberz:
Any plans to make this enforcing?

Or an official build?
[Pixel C Android Development] thetample:
Dirty flashed the new rom and it works great as usual!
[Pixel C Android Development] followmsi:
Enforcing mode will come later .. for now you can switch manually. (setenfoce 1)

And no more official builds .. at least not by me.
[Pixel C Android Development] _benedict_:
Hi!

I clean installed the lastest ROM and on first boot it asks for a password. As far as I remember, this was not happening with Lineage 17. What should I do?
[Pixel C Android Development] Alxoom33:
Enter your password, lol!

There is a password delete zip in @followmsi' downloads database that you can flash in TWRP. It should fix your issue.
[Pixel C Android Development] TooYellow:
I had the Feb build and Nik gapps stock installed. The tablet ran fine but felt like a device running an OS three versions past its EOL. After installing the 202010406 build I got a boot loop. I fixed it by manually uninstalling nik and decided on installing Nik gapps core instead.

The tablet now performs like it was built for Android R! Scrolling is way smoother, switching apps is zippier, overall faster UI response. I don't know if it was the new build or swapping to a smaller gapps package but I'm loving it. Chrome is still slow though.

Just wanted to share my experience in case people are having sluggishness like I was.

My primary uses: google news, youtube, instagram, Firefox, kindle, google books
[Pixel C Android Development] Tiesemans:
I have such a stupid situation.

After ADB sideloading 202010406 build I lost my TWRP and Magisk.

Thinking I was smart I also sideloaded TWRP 3.5.2_9-0-guacamole-recovery.img

My bad ... bootloop hallo, with TWRP logo continuesly flashing.

I restored it by using

So now I am desperately trying to fastboot via bootloader fastboot boot and flash TWRP recovery.img ...

But when I do so I end up in bootloader :S loop.

When I restore via fastboot the lineage recovery all is well again :S

What am I doing wrong here?!

Honestly I think the lastest TWRP for oneplus 7 pro is not compatible with current nightly 18.1 Lineage boot/recovery?!
[Pixel C Android Development] ipdev:
This OT (Off Topic) for this thread.

This thread is for Pixel C (Dragon)

If you are having trouble on a OnePlus 7, you will be better off searching and/or asking in one of the OnePlus 7 Pro threads.

OnePlus 7 Pro - xdaForums - Link

[RECOVERY][3.4.0-10][U][guacamole]Official/Unofficial TWRP recovery for OnePlus 7 Pro - xdaThread - Link

Note about TWRP:

If your device has a separate recovery partition, you can flash TWRP to recovery.

If your device is Recovery-In-Boot, you need to patch the boot image with TWRP using the TWRP installer zip for your device.

I remember when I was looking at OP 7(s), one of them did have a separate recovery partition.​

Users in the OnePlus 7 threads will be able to help you more since, they have the device.

Good luck. :)

Cheers. :cowboy:
[Pixel C Android Development] rkjnsn:
In case it helps anyone else, I was running into the following error when trying to flash MindTheGapps from TWRP:

Could not mount /mnt/system! Aborting

The error turned out to be that /etc/recovery.fstab was using tabs for separators, but the MindTheGapps script was expecting it to use spaces. I was able to solve the problem by editing META-INF/com/google/android/update-binary in MindTheGapps-11.0.0-arm64-20210412_124247.zip. I replaced this line (line 44):

grep -v "^#" /etc/recovery.fstab | grep " $1 " | tail -n1 | tr -s ' ' | cut -d' ' -f1

With this one, which should work with both tabs and spaces:

grep -v "^#" /etc/recovery.fstab | grep "[[:space:]]$1[[:space:]]" | tail -n1 | tr -s [:space:] ' ' | cut -d' ' -f1
[Pixel C Android Development] ipdev:
Nice find. :D

MindTheGapps - GitLab - get_block_for_mount_point - Link

If you are signed up on GitLab, please bring this to their attention.

MindTheGapps - GitLab - Link

If not, let me know and I will bring it to their attention on your behalf.

Cheers. :cowboy:

PS.

Sorry all for a bit of OT. 🙃
[Pixel C Android Development] AmazingToast:
For the update released today, do I need to flash a new vendor image?
[Pixel C Android Development] followmsi:
No .. beginning of next Monday you will need the new vendor.img (2017-08)
[Pixel C Android Development] Razorsoup:
Using this version of Magick on my Pixel C results in modules not being able to be installed. Trying to install them by flashing the zip via TWRP results in an error stating "/data/magisk isn't set up properly" and via Magisk Manager doesn't give any helpful errors I can find, just a "installation failed" pop-up. Have you got any tips on where to start troubleshooting this issue?

Edit: I'm running the August 8, 2017 nightly of Lineage OS.
[Pixel C Android Development] followmsi:
This "special" version was just made to get Magisk 13.x installed at all - due to broken installer in "official" version.

The installer problem seems to be related to chromeos boot.img - like we have in Pixel C.

I do use MagiskSU and Magik Hide which is working fine .. I did not test any modules.

There are a few tickets regarding the boot-loop/installer problem on Pixel C.

This issue needs to be fixed at the source of the problem !

I will not have the time to push this issue .. maybe you can help to speed up the solution.

https://xdaforums.com/showpost.php?p=73226045&postcount=406

Once we use the "official" version you can get support for your modules problem too - if still persists.

Support from Magisk support thread - like it should be.

Sorry, can't help you better here ...
[Pixel C Android Development] Razorsoup:
Yeah, Magisk and Magisk Hide both seem to be working along with Magisk's systemless hosts functionality. It's just the modules that are giving me problems. I just wasn't sure if I did something wrong or missed something obvious. Hopefully those tickets will be resolved in the official version soon and I can move over with that. Thank you for this special version. It's a lot better than having nothing.

Edit: The 13.6 Beta of Magisk seems to be working for me on my Pixel C with the latest nightly of LineageOS. Hopefully it doesn't break again.
[Pixel C Android Development] followmsi:
Just saw your edit .. 13.6 beta fixes bootloop on Pixel C ?

Magisk.zip installation via TWRP ?

Did you re-install your original LineageOS boot.img before installation of Magisk ?

Thanks
[Pixel C Android Development] Razorsoup:
Just flashed the 13.6 via TWRP. I don't remember off hand if I still had your version of 13.3 installed. I'll restore everything to stock later today and try it out and report back.
[Pixel C Android Development] Razorsoup:
So, I just uninstalled Magisk using the official uninstaller. Wiped the system partition and reinstalled LineageOS for good measure. Booted to make sure everything works correctly. Rebooted into TWRP and installed the 13.6 Beta of Magisk. Everything seems to be in working order.
[Pixel C Android Development] followmsi:
Thanks for the update .. sounds good.

Will test 13.6 on O DP4 later on.
[Pixel C Android Development] Veritas06:
Has anyone else been having issues getting LOS running on their Pixel C? No matter which release I try, I never seem to get a stable build, always get bootloops. And I am not even flashing any extra yet (SU or GApps, etc). I tried to hit up Reddit, but they just pointed me back here =\

Just hoping to get this up & running again.

EDIT: Figures... Right after I post this, I'm able to get it working. Oh well, glad it works now =]
[Pixel C Android Development] followmsi:
Confirmed .. no boot-loops anymore !

Tested Magisk 13.6 BETA on Android Oreo Final version from today .. works fine.

Cheers
[Pixel C Android Development] xda_jm:
hi guys,

I was wondering if you also noticed a battery drain with the 2 last nightly builds.

Usually one battery charge could last me 3 to 5 days when I work (not using it much). But nowadays, the battery level goes down very fast.

PS: I already disabled most crap social apps from starting etc., and prevent most apps from running in the background.

Any hints on how to identify the culprit here?

Thx.