Due to limited customisation on pixel launcher .Due to what?
Any problem?
Due to limited customisation on pixel launcher .Due to what?
https://www.xda-developers.com/customize-pixel-launcher-google-pixel-5-pixel-launcher-editor-root/ other options for people who want to use that launcher or you modifying itDue to limited customisation on pixel launcher .
Any problem?
try this: https://forum.xda-developers.com/t/...ction-remix-sept-9-2020.4151593/post-84090275cannot boot to fasbootd. I think I tried everything. I downloaded latest platform-tools_r30.0.4-windows.
adb reboot fastboot gives error device not found
fastboot reboot fastboot gives a list of commands
Any ideas?
fastboot reboot fastboot gives thw following result
PS D:\tmp\platform-tools_r30.0.4-windows(1)\platform-tools> fastboot reboot fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
Nope it will be broke fingerprintIs arter kernel compatible with this?
Dummy question but is it necessary to remove all magisk modules, substratum skins and then un-install Magisk completely in order to flash this ROM (coming from OOS)?When you update you need to flash magisk to inactive slot before reboot. Otherwise you'll flash un-patched boot.img
Coming from OOS you need to erase everything with "fastboot -w" so, it doesn't make sense to have all that work uninstalling apps one by one...Dummy question but is it necessary to remove all magisk modules, substratum skins and then un-install Magisk completely in order to flash this ROM (coming from OOS)?
Yes, you need RR patched boot.imgAlso, I assume that installing Magisk is the same - I just need to have patched boot.img? Thank you in advance.
Nope it will be broke fingerprint
I'm running Arter's kernel (r64) with no issues, fingerprint working fine. Just flashed it with Franco Kernel Manager.Is arter kernel compatible with this?