Develop Bugs

[ROM][UNOFFICIAL][gts4lvwifi][9] LineageOS 16.0

{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions :
Download the latest build and gapps
Reboot to recovery
Flash the latest build and gapps
Reboot
Downloads :
Builds :
https://www.androidfilehost.com/?w=files&flid=298356
http://downloads.codefi.re/jdcteam/luk/lineage-16_0/gts4lvwifi
https://sourceforge.net/projects/luk-lineageos/files/gts4lvwifi/lineage-16.0
Root addon : https://download.lineageos.org/extras
Google Apps : https://wiki.lineageos.org/gapps.html
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
XDA:DevDB Information
[ROM][UNOFFICIAL][gts4lvwifi][9] LineageOS 16.0, ROM for the Samsung Galaxy Tab S5e
Contributors
LuK1337
Source Code: https://github.com/LineageOS
ROM OS Version: Windows 8 Mobile
Version Information
Status: Testing
Created 2019-08-24
Last Updated 2019-08-24

-- bit more friendly stock -> lineage instructions --
1. Unlock the bootloader
- Connect to WiFi network
- Enable OEM Unlock in developer options
- Turn off the tablet
- Boot to download mode manually by plugging in USB and holding all the buttons for few seconds
- Follow instructions on the screen
2. Connect to WiFi network and make sure OEM Unlock in developer options is still checked
3. Flash custom VBMeta image ( https://dl.twrp.me/gts4lvwifi/vbmeta.tar.html ) in Odin ( use AP slot )
4. After flashing VBMeta, boot to stock. It'll likely ask you to wipe data, if so do that
5. Connect to WiFi network and make sure OEM Unlock in developer options is still checked
6. Now you can flash TWRP ( https://dl.twrp.me/gts4lvwifi ) in Odin ( use AP slot once again ), for convenience you can hold volume up while flashing it so that you boot to recovery right after it's flashed
7. Install Lineage × whatever else you need ( gapps, addon-su, ... )
8. Format data
9. Reboot ( make sure to not install TWRP app when TWRP asks you to )
---
Also Odin download for those who can't find it on their own https://build.nethunter.com/samsung-tools/Odin_3.13.1.zip
( sha1sum 1057496afa34bfdf7e77caf0b99207dca77fcb2d )

Damn @LuK1337 you're all over this thing. About to install (well, at least try to) TWRP using terminal, then I'll do this.
Perfect timing, too. I just did the whole 'prepare for imminent disaster' thing so I could do some extreme debloating/deleting of stuff I don't want on my tablet.
I'll report my experience here.

Wow! Great work!

TiTiB said:
Damn @LuK1337 you're all over this thing. About to install (well, at least try to) TWRP using terminal, then I'll do this.
Perfect timing, too. I just did the whole 'prepare for imminent disaster' thing so I could do some extreme debloating/deleting of stuff I don't want on my tablet.
I'll report my experience here.
Click to expand...
Click to collapse
Install twrp with odin..
1st recovery
2nd vbmeta
Vbmeta's install failed a few times for me, just reboot back to bootloader if you get stuck on getting connection, then try vbmeta again.
That also depends on what firmware your on, June firmware was a easy on installing recovery and using key combo go to recovery, just worked.
Latest update, Juli needs vbmeta to be flashed, otherwise you (might} get an error about non compatible vbmeta installed atm you use the key combos to boot to recovery from bootloader.

RagingHarry said:
Install twrp with odin..
1st recovery
2nd vbmeta
Vbmeta's install failed a few times for me, just reboot back to bootloader if you get stuck on getting connection, then try vbmeta again.
That also depends on what firmware your on, June firmware was a easy on installing recovery and using key combo go to recovery, just worked.
Latest update, Juli needs vbmeta to be flashed, otherwise you (might} get an error about non compatible vbmeta installed atm you use the key combos to boot to recovery from bootloader.
Click to expand...
Click to collapse
1. flash vbmeta from twrp website
2. boot stock; it'll ask you to wipe data, do that.
4. make sure to connect to wifi on stock and that oem unlocking is selected
5. flash recovery, keep holding vol up while flashing
7. sideload lineage × gapps
8. wipe data
10. reboot
11. profit?

For the needed files incase of twrp https://twrp.me/samsung/samsunggalaxytabs5ewifi.html

Ok, so I'm on latest Samsung fw, root and twrp. Just wipe, flash rom, and gapps? Thanks.

suzook said:
Ok, so I'm on latest Samsung fw, root and twrp. Just wipe, flash rom, and gapps? Thanks.
Click to expand...
Click to collapse
There is more info here atm then the moment I 1st flashed a few days ago.
You can do it, read, let it sync to your brain, and just do..
Follow @LuK1337 steps, saves you some unnecessary steps I did getting there..

RagingHarry said:
There is more info here atm then the moment I 1st flashed a few days ago.
You can do it, read, let it sync to your brain, and just do..
Follow @LuK1337 steps, saves you some unnecessary steps I did getting there..
Click to expand...
Click to collapse
Can I flash magisk? Or the provided su for lineage?

I wiped, flashed rom, flashed gaps. it never boots. I see the lineage boot image, but it never completely boots. Any ideas?

Not sure how I got so messed up, but here I am. Not able to power off. PC knows something is hooked up, but 'adb devices' not showing anything. Device Manager shows yellow triangle for Android Phone>Android ADB Interface.
Looking for info on the internets, but no luck yet. Anyways, I'll check back here in a couple hours.
EDIT: More info.
Had TWRP installed.
Currently no key combos working, just goes to Samsung splash screen, then back to screenshot.

Welp. Guess I'm buying this thing tomorrow.

TiTiB said:
Not sure how I got so messed up, but here I am. Not able to power off. PC knows something is hooked up, but 'adb devices' not showing anything. Device Manager shows yellow triangle for Android Phone>Android ADB Interface.
Looking for info on the internets, but no luck yet. Anyways, I'll check back here in a couple hours.
EDIT: More info.
Had TWRP installed.
Currently no key combos working, just goes to Samsung splash screen, then back to screenshot.
Click to expand...
Click to collapse
Did you flash vbmeta from TWRP website? Also you shouldn't be using adb driver in this mode.
suzook said:
I wiped, flashed rom, flashed gaps. it never boots. I see the lineage boot image, but it never completely boots. Any ideas?
Click to expand...
Click to collapse
Wipe/format data? Oh also you can try to wipe system and install lineage × gapps again but this time make sure to NOT install twrp app.

hi
first i flash vbmeta (odin)
2-falsh recovery (odin)
3-flash lineage without gapps
after restart i get boot loop any solution?

jawadabomehsen said:
hi
first i flash vbmeta (odin)
2-falsh recovery (odin)
3-flash lineage without gapps
after restart i get boot loop any solution?
Click to expand...
Click to collapse
Did you install twrp app? If so, wipe system, install lineage again and don't install twrp app this time.
Did you wipe data?

no i didnt install twrp app
---------- Post added at 11:06 AM ---------- Previous post was at 11:02 AM ----------
yes i wipe data

LuK1337 said:
Did you flash vbmeta from TWRP website? Also you shouldn't be using adb driver in this mode.
Wipe/format data? Oh also you can try to wipe system and install lineage × gapps again but this time make sure to NOT install twrp app.
Click to expand...
Click to collapse
I will try wiping system this time. and yea, I dont install twrp app. I will update later. Thanks.
Nope. Same thing. I get the lineage animation for a few minutes, then it just reboots. I let this happen a few times. Arm 64 gapps, correct??

jawadabomehsen said:
no i didnt install twrp app
---------- Post added at 11:06 AM ---------- Previous post was at 11:02 AM ----------
yes i wipe data
Click to expand...
Click to collapse
Add me on hangouts or discord?
( see my signature )

So far, its running awesome! Thanks!

[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)

Root Motorola Devices with Magisk
Note:
This method has been working with most Moto Devices that the Bootloader can be UnLocked.
If the Bootloader cannot be Unlocked this method will not work.
Please only use this as a reference. If you require more help please post in your device's forum.
Mention me with @sd_shadow
Quick Steps
Unlock the Bootloader
Note: Unlocking will wipe Userdata
Install Magisk manager app
Spoiler: Check ramdisk status
{
"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"
}
If Ramdisk is Yes continue to Download Firmware
If Ramdisk is anything else see
New check ramdisk status -26 March 2021
Download Firmware Rescue and Smart Assistant(LMSA)(PC)
Spoiler: Check the Current software version with the download version.
If the download is newer, now is a good time to flash the update.
The newer boot.img may not work correctly with the older software on the device.
If you want to keep the firmware version that is on the device see Other Firmware Options
Other Firmware options
Find the boot.img in the LMSA Downloads Folder
"ProgramData\LMSA\Download\RomFiles\"
Copy boot.img to Moto Device
Spoiler: Tap Magisk > Install
Spoiler: Tap "Select and Patch a File"
Spoiler: Check the Patched.img Filename and Location
Copy magisk_patched.img to PC
Flash magisk_patched.img
Reboot
Open Magisk manager to verify you have the current version.
Hide Magisk
If you use apps the won't work if rooted devices (Banking apps) Enable Hide Magisk
Safetynet fix (21 March 2022)
https://github.com/kdrag0n/safetynet-fix
More​
Magisk Hide: Using banking Apps
Magisk Recovery Mode
Install Updates and Keep Root
Root with Magisk Twrp method
https://github.com/topjohnwu/Magisk/releases/

Troubleshooting
If you get a "no ramdisk" error​
Try flashing patched.img anyway it may still work
https://github.com/topjohnwu/Magisk/issues/3239
You may need to also patch the recovery.img
Like in this Post

Additional Links
[Stock ROM] How to root the Snapdragon Moto E 2020
Moto One 5G Ace root guide
Motorola One Macro [Root Tutorial]

Flashing magisk_patched.img
Change .img name to exact file name.
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
fastboot reboot
or
Code:
fastboot flash boot magisk_patched.img
fastboot reboot

Magisk in recovery
If your device does not have ramdisk in boot images, Magisk has no choice but to be installed in the recovery partition. For these devices, you will have to reboot to recovery every time you want Magisk.
When Magisk is installed in your recovery, you CANNOT use custom recoveries to install/upgrade Magisk! The only way to install/upgrade Magisk is through the Magisk app. It will be aware of your device state and install to the correct partition and reboot into the correct mode.
Since Magisk now hijacks the recovery of the device, there is a mechanism to let you actually boot into recovery mode when needed: it is determined by how long you press the recovery key combo.
Click to expand...
Click to collapse
This does not replace stock recovery.
Installation
The Magic Mask for Android
topjohnwu.github.io

Magisk
Magisk Manager is dead.​Long live the Magisk app!​Ever since the first Magisk release, Magisk (the core components) and Magisk Manager (the companion app) are released separately and isn't necessarily always in sync. This leads to some confusion and a lot of complexity when downloading/installing Magisk through the app. Starting from v22.0, the Magisk app (renamed from Magisk Manager) includes everything it needs within the APK itself, making installation a 100% offline process.
Custom recovery lovers, no worries! The Magisk app APK itself is a custom recovery flashable zip, just like MAGIC™. Check out the updated installation guide for more info.
Click to expand...
Click to collapse
Installation
The Magic Mask for Android
topjohnwu.github.io

Magisk Recovery mode
[DEPRECATED] [2019.4.4] Magisk Manager for Recovery Mode (mm)
THIS PROJECT IS NO LONGER SUPPORTED. # Magisk Manager for Recovery Mode (mm) ## LEGAL Copyright (C) 2017-2019, VR25 @ xda-developers This program is free software: you can redistribute it and/or modify it under the terms of the GNU General...
forum.xda-developers.com

New Magisk Instructions
Installation
The Magic Mask for Android
topjohnwu.github.io

Hiding root and bootloader from Banking apps
Magisk and MagiskHide Installation and Troubleshooting guide : MagiskHide
Magisk renaming is maybe required.
Try using VD INFOS, you can see every detectable thing. (Root/Magisk/Xposed/Riru/and others.)
[APP][v1.10] VD Infos (Package: com.vitaodoidao.vdinfos)
(Para quem fala PORTUGUÊS, o próximo post está totalmente traduzido !) VD Infos v1.10 As we all know, Android is a super powerful and super versatile operating system. What nobody tells you is that all your personal details and confidential...
forum.xda-developers.com

Wow, thanks so much for the comprehensive reply @sd_shadow. Think I may take a look at the non-TWRP method.
Interesting that you install Magisk immediately after unlocking bootloader. I had been following these instructions: https://appuals.com/root-Motorola-moto-g5-g5-plus/ which doesn't install Magisk until after TWRP - but then you're not using TWRP!
In answer to @Wolfcity, yes I had tried reboot to TWRP, but get the following:
C:\adb>fastboot boot recovery.img
cannot load 'recovery.img': No such file or directory
I should've said, that's mostly why I figured it had failed.
I'm actually rooting to make use of Nethunter on the device. It's an old device, so not one I'll be using for any everyday apps or accounts. It'll be dedicated to Nethunter - for legit purposes only!

sd_shadow said:
Root Motorola Devices with Magisk
Note:
This method has been working with most Moto Devices that the Bootloader can be UnLocked.
If the Bootloader cannot be Unlocked this method will not work.
Please only use this as a reference. If you require more help please post in your device's forum.
Mention me with @sd_shadow
Quick Steps
Unlock the Bootloader
Note: Unlocking will wipe Userdata
Install Magisk manager app
Spoiler: Check ramdisk status
If Ramdisk is Yes continue to Download Firmware
If Ramdisk is anything else see
New check ramdisk status -26 March 2021
Download Firmware Rescue and Smart Assistant(LMSA)(PC)
Spoiler: Check the Current software version with the download version.
If the download is newer, now is a good time to flash the update.
The newer boot.img may not work correctly with the older software on the device.
If you want to keep the firmware version that is on the device see Other Firmware Options
Other Firmware options
Find the boot.img in the LMSA Downloads Folder
"ProgramData\LMSA\Download\RomFiles\"
Copy boot.img to Moto Device
Spoiler: Tap Magisk > Install
Spoiler: Tap "Select and Patch a File"
Spoiler: Check the Patched.img Filename and Location
View attachment 5384841
Copy magisk_patched.img to PC
Flash magisk_patched.img
Reboot
Open Magisk manager to verify you have the current version.
Hide Magisk
If you use apps the won't work if rooted devices (Banking apps) Enable Hide Magisk
More​
Magisk Hide: Using banking Apps
Magisk Recovery Mode
Install Updates and Keep Root
Root with Magisk Twrp method
https://github.com/topjohnwu/Magisk/releases/
Click to expand...
Click to collapse
Question, when I did all of this through magisk everything went swell but my moto Touchscreen stopped working but booted just fine not sure if it was a one time fluke or not gonna try again any suggestions? Should I also Flash Recovery?

Jr.17 said:
Question, when I did all of this through magisk everything went swell but my moto Touchscreen stopped working but booted just fine not sure if it was a one time fluke or not gonna try again any suggestions? Should I also Flash Recovery?
Click to expand...
Click to collapse
If the touchscreen stopped working you likely used the wrong boot.img
You don't need a custom recovery just for root.

Sweet thanks I'll look again at what I got

Jr.17 said:
Sweet thanks I'll look again at what I got
Click to expand...
Click to collapse
boot.img must match build version and channel that is on the device.

Ok I see Where I messd up now looks like I used wrong channel

sd_shadow said:
Flashing magisk_patched.img
Change .img name to exact file name.
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
fastboot reboot
or
Code:
fastboot flash boot magisk_patched.img
fastboot reboot
Click to expand...
Click to collapse
I can't get my pc to see the phone when the phone is in fastboot mode

Grimace78 said:
I can't get my pc to see the phone when the phone is in fastboot mode
Click to expand...
Click to collapse
See device manager, how is it listed?

@sd_shadow My devices is edge xt2063-2 （USA，5G brand N71），It’s can't connect to chinatelecom（5G band N78）
But xt2603-3（Europe）ROM include N78 band
Can I flash XT2063-3 EU ROM on mydevices just by fastboot mode?
Or Just need modify some .img files

Vger20192019 said:
@sd_shadow My devices is edge xt2063-2 （USA，5G brand N71），It’s can't connect to chinatelecom（5G band N78）
But xt2603-3（Europe）ROM include N78 band
Can I flash XT2063-3 EU ROM on mydevices just by fastboot mode?
Or Just need modify some .img files
Click to expand...
Click to collapse
If the bootloader is unlocked, no problem.
If the bootloader is still locked, just flash the radio part.
Flashing the Radio Firmware

Grimace78 said:
I can't get my pc to see the phone when the phone is in fastboot modemak
Click to expand...
Click to collapse
Also Make sure To Update Drivers

Development [ROM][Android 11][OP9Pro] crDroid v7

{
"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"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Flashing Instructions:
Pre-installation:
Until TWRP is ready, this version of crDroid comes with prebaked core Gapps
Download LOS recovery
Download Tiny ADB & Fastboot
First time installation (clean flash):
It is recommended to come clean from latest OOS installation
Backup your data to PC, OTG flash drive
Reboot to bootloader (fastboot)
Run fastboot devices to confirm there is connection to the phone
Install LOS recovery with following command fastboot flash boot lineage-18.1-20210615-recovery-lemonadep.img
Power off and reboot to recovery by pressing VOL down + Power from shutdown state
Navigate with volume keys to Factory Reset -> Format data/factory reset and confirm format of data
Go back to main menu and choose Apply update and Apply from ADB
Now adb sideload latest crDroid package with adb sideload crDroid.zip
When asked to confirm flash, do confirm it
Sideload push will go up to 47% and fail - no worry is normal
Reboot to system
Update installation:
Through recovery:
Download latest crDroid zip and reboot to recovery
Choose Apply update and Apply from ADB
Now adb sideload latest crDroid package with adb sideload crDroid.zip
Sideload push will go up to 47% and fail - no worry is normal
Reboot to system
Built-in OTA (slower):
When ready
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/crdroidandroid/android_kernel_oneplus_sm8350
Download:
ROM https://crdroid.net/lemonadep#crDroid-v7
Changelog: https://crdroid.net/lemonadep#crDroid-v7/changelog
Known issues:
- waiting for more feedback to see
Visit official website @ crDroid.net
crDroid OnePlus 9 Pro Telegram
crDroid Community Telegram
crDroid is built with passion by @neobuddy89 and @gwolfu
If you like our work, do consider a donation to support further device development
ROM OS Version: Android 11
ROM Kernel: Linux 5.4

Awesome.

I have the Tmobile version of OP9pro. Will I need to flash the tmobile modem.img?

burtonlax said:
I have the Tmobile version of OP9pro. Will I need to flash the tmobile modem.img?
Click to expand...
Click to collapse
Testing of this rom has been done on the EU variant
I am not sure how Tmobile version works, but rom side, is same as on LOS

gwolfu said:
Testing of this rom has been done on the EU variant
I am not sure how Tmobile version works, but rom side, is same as on LOS
Click to expand...
Click to collapse
it's best to go global first coming from tmo. No, as long as you don't do an ota on Global. so flash global then boot, then flash custom rom(following their guide).
If u lose service modem is provided (Just unzip) Bootloader fastboot command "fastboot flash modem modem.img
This of course is assuming u got unlock.bin and unlocked Bootloader

Here we go!
Welcome @gwolfu
Hopefully we don't need 11.2.7.7?? It's not out here in EU yet, what's the reason most of the custom roms seem to want the EU build by the way?

CRDroid, fantastic to see this here my favorite ROM since the days of my LG G3! Can't wait to try this out, will sadly be waiting till TWRP tho as I'd prefer to avaoid gapps. Unless there is any chance of a non gapps build also? Cheeky....!

I'll flash and report tomorrow .
post logs through here or telegram?

ryantf420 said:
I'll flash and report tomorrow .
post logs through here or telegram?
Click to expand...
Click to collapse
preferably here as to better keep track of stuff

I know it may not be recommended, but has anyone been able to flash this without using a computer?

phr0zen said:
I know it may not be recommended, but has anyone been able to flash this without using a computer?
Click to expand...
Click to collapse
Since the instructions specify using fastboot (as well as sideloading the rom), that's not possible.

phr0zen said:
I know it may not be recommended, but has anyone been able to flash this without using a computer?
Click to expand...
Click to collapse
without TWRP, not possible

TWRP is death.

This is awesome news brother

So I've been out of the root and rom flashing game for a bit, got it side loaded and everything my issue is i cant get root permissions working wasn't sure how i go about setting it up since all i have worked with on the one plus is magisk and having to install to a .img and input on how to get it working?

crazyvash1 said:
So I've been out of the root and rom flashing game for a bit, got it side loaded and everything my issue is i cant get root permissions working wasn't sure how i go about setting it up since all i have worked with on the one plus is magisk and having to install to a .img and input on how to get it working?
Click to expand...
Click to collapse
extract crdroid.zip content
extract boot.img from payload.bin file using payload dumper
install magisk apk on phone as any other apk (I know we are not rooted yet)
copy boot.img to internal phone storage
open magisk and click on top install button
choose "select and patch a file"
select the boot.img from internal storage
after done, copy magisk patched boot image from Download folder on phone storage, to PC
now on PC, reboot to bootloader and run
Code:
fastboot flash boot magisk_patched-23000_xxxxx.img
check file name to match xxxxx = random generated text
reboot to system and enjoy

gwolfu said:
extract crdroid.zip content
extract boot.img from payload.bin file using payload dumper
install magisk apk on phone as any other apk (I know we are not rooted yet)
copy boot.img to internal phone storage
open magisk and click on top install button
choose "select and patch a file"
select the boot.img from internal storage
after done, copy magisk patched boot image from Download folder on phone storage, to PC
now on PC, reboot to bootloader and run
Code:
fastboot flash boot magisk_patched-23000_xxxxx.img
check file name to match xxxxx = random generated text
reboot to system and enjoy
Click to expand...
Click to collapse
Think you missed the last step to use Magisk again to root the installed boot image?

djsubterrain said:
Think you missed the last step to use Magisk again to root the installed boot image?
Click to expand...
Click to collapse
Not need
I used fastboot flash not fastboot boot so boot is already patched
No temp boot and patch after

gwolfu said:
Not need
I used fastboot flash not fastboot boot so boot is already patched
No temp boot and patch after
Click to expand...
Click to collapse
Didn't notice that, totally right. Sorry.

truly have found nothing broken
except power menu settings only work in crdroid Settings not in System>Gestures>power menu...
Great job

Question How to root OnePlus 9RT 5G?

I just got my new Oneplus 9RT 5G. I searched a lot but unable to find a method to root it via TWRP.
Can anyone please share a link to TWRP recovery so that I can flash it and root it via Magisk?
I tried to unlock the bootloader by going to the fastboot mode but keep getting 'failed' message.
{
"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 have enabled 'USB debugging' and 'allow OEM unlock' in the developer options.

Use fastboot flashing unlock instead of oem unlock.

penguinus said:
Use fastboot flashing unlock instead of oem unlock.
Click to expand...
Click to collapse
Okay and what about a compatible TWRP recovery file that I can flash?

No TWRP for now. You should get boot.img from stock firmware, then patch it using Magisk Manager, then load the phone using patched boot.img, an then install magisk to the system

penguinus said:
No TWRP for now. You should get boot.img from stock firmware, then patch it using Magisk Manager, then load the phone using patched boot.img, an then install magisk to the system
Click to expand...
Click to collapse
Okay. How to get the stock firmware? I checked the official website. It's not available.

archz2 said:
Okay. How to get the stock firmware? I checked the official website. It's not available.
Click to expand...
Click to collapse
Yes, it is not available on site. If you have chinese firmware (ColorOS), you can get full rom from OTA servers. Even more, for the most recent versions I can provide ready to use boot.img. But for indian Oxygen full roms not availabe yet. You can try to dump boot.img from your phone using dd.

penguinus said:
You can try to dump boot.img from your phone using dd.
Click to expand...
Click to collapse
How do I do it? Please provide step by step process. I bought this phone in India and it's running Android 11 , Oxygen OS.

Well, looks like to dump boot.img you need root. Please try attached file (unzip it). Found it in TG, labeled as boot.img for indian Oxigen. Please note that you should NOT flash it to your device, so it should be safe enough. We will try to sideload it.
You already have installed fastboot to your PC, so I will skip this part.
To check boot.img
1. Place boot.img to your computer, to the same folder where you have fastboot installed
2. Reboot your phone to fastboot mode i.e with adb reboot bootloader
3. Do fastboot boot boot.img.
If phone will start normally, looks like boot is ok and you can use it to get rooted.
To install Magisk (get root)
1. Place boot image to phone.
2. Download Magisk and install it to the phone. Note that we use canary version of Magisk. Latest stable version doesn't work at least on chinese (ColorOS) version.
3. Start Magisk on a phone, press "Install" and choose "Select and Patch a File" (the only available option), select boot.img file.
4. Patched boot.img will be placed to Download directory named something like "magisk_patched*.img". Download this file back to PC, place to the same directory with fastboot.
5. Reboot your phone to fastboot mode i.e with adb reboot bootloader
6. Do fastboot boot magisk_patched*.img (change to correct name of file). Phone should start correctly.
7. Start Magisk again. Select "Install". This time all options should be available. Select "Direct Install (Recommended)".
8. At the end reboot and check if root is working.

penguinus said:
Well, looks like to dump boot.img you need root. Please try attached file (unzip it). Found it in TG, labeled as boot.img for indian Oxigen. Please note that you should NOT flash it to your device, so it should be safe enough. We will try to sideload it.
You already have installed fastboot to your PC, so I will skip this part.
To check boot.img
1. Place boot.img to your computer, to the same folder where you have fastboot installed
2. Reboot your phone to fastboot mode i.e with adb reboot bootloader
3. Do fastboot boot boot.img.
If phone will start normally, looks like boot is ok and you can use it to get rooted.
To install Magisk (get root)
1. Place boot image to phone.
2. Download Magisk and install it to the phone. Note that we use canary version of Magisk. Latest stable version doesn't work at least on chinese (ColorOS) version.
3. Start Magisk on a phone, press "Install" and choose "Select and Patch a File" (the only available option), select boot.img file.
4. Patched boot.img will be placed to Download directory named something like "magisk_patched*.img". Download this file back to PC, place to the same directory with fastboot.
5. Reboot your phone to fastboot mode i.e with adb reboot bootloader
6. Do fastboot boot magisk_patched*.img (change to correct name of file). Phone should start correctly.
7. Start Magisk again. Select "Install". This time all options should be available. Select "Direct Install (Recommended)".
8. At the end reboot and check if root is working.
Click to expand...
Click to collapse
Okay. Thanks a lot.
I checked the boot image, all the three step went absolutely fine.
To obtain Magisk, everything went well till step no. 5.
When I try to reboot with the patched image in the bootloader, the phone keeps booting in the bootloader itself. I also changed the name of the image from 'magisk_patched_bco6o' to 'bestimage', just to make sure that there aren't any special characters in the filename. Same. The phone kept booting in the fastboot mode using the image.
Now what should I do?
Edit.
I just updated the Magisk app directly from its UI. Now the phone booted fine using step 6. My device is rooted! Thanks a ton!

Okay. I'm connected to the internet and ensure that magisk has internet connectivity. I cannot see any packages to download and install. Is this normal in canary version or I have to do something about it?

archz2 said:
Okay. I'm connected to the internet and ensure that magisk has internet connectivity. I cannot see any packages to download and install. Is this normal in canary version or I have to do something about it?
Click to expand...
Click to collapse
Canary doesn't have internet repository. You should install modules manually. Please note that "Magisk Hide" is not available also and replaced by Zygisk function in settings. Basically it works similar to magisk hide.

archz2 said:
My device is rooted! Thanks a ton!
Click to expand...
Click to collapse
What ROM version is it? Especially a build number. Want to know what version of Oxygen is elighble for rooting with provided boot.img.

Here's the build information

Okay.
penguinus said:
Canary doesn't have internet repository. You should install modules manually. Please note that "Magisk Hide" is not available also and replaced by Zygisk function in settings. Basically it works similar to magisk hide.
Click to expand...
Click to collapse
Okay can I install a normal magisk app now since my device is already rooted?
Having a direct internet repository in magisk is quite convenient.
Another question. I want to install Lsposed on this phone to install GravityBox module. Now in my previous phone, (oneplus 5t running stock oxygen OS, Android 10) , I always used to keep a edxposed uninstaller zip file which helped in cases when there would be a bootloop after installing a module. I used to flash that zip in the TWRP, get back things to normal, and then uninstall a particular xposed module.
Now I don't have any TWRP on this phone. I don't have any custom recovery installed on this phone!
What do you recommend for doing xposed/lsposed/edxposed based flashing and module installation?

I can't say for sure it will not work. I just know stable version of Magisk DOESN'T work with 9RT chinese version (ColorOS). The chance to get it worked on OxigenOS is minimal as it looks for me. And what is happening with chinese phone with current magisk is bootloop. So I think it is better to not even try. At least while you don't have full ROM to recover.
Regarding absense of net repository in canary, there is a post from Magisk creator about it. Unfortunately, these functions will not back. I don't use many Magisk modules - just installed safetynet-fix and Systemizer manually.
Sorry, I don't have much experience with Magisk modules, the only recommendation for now is to not experiment too much while we don't have msm tool or at least full ROM.

Okay. And any comment on installing xposed? I don't have any TWRP or any custom recovery.

I didn't tried it, but please check threads of lsposed and EdXposed
Looks like both can be installed as Magisk modules, but needs Riru. Probably will give them a try later.

Thanks. I successfully installed latest Riru, Lsposed and GravityBox. All good so far.
Having issues with Viper installations. Will post about it in a separate thread.

penguinus said:
I don't use many Magisk modules - just installed safetynet-fix and Systemizer manually.
Click to expand...
Click to collapse
I flashed safetynet fix and rebooted but I'm still not able to pass safetynet. Any solution?

archz2 said:
I flashed safetynet fix and rebooted but I'm still not able to pass safetynet. Any solution?
Click to expand...
Click to collapse
After installing and activating safetynet fix you should clear data for Google Play Store and Google Play Services. Then open Play Store -> Settings -> About -> Play Protect certification. Should be "Device is certified"

[ROM][Android 13][UNOFFICIAL][OTA] LineageOS 20.0 for Xiaomi Mi A2 Lite [daisy]

{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 13 (T), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Notes
- Selinux is enforcing
- FBE build, don't use twrp for these builds
- Custom kernels are NOT supported
- Read the instructions carefully
Downloads
- Here
Flashing instructions
- Here (Suggestions for improving the guide are welcome)
Sources:
- LineageOS
- Kernel Tree
Happy modding!

Reserved

Good news

Great!

Okay but does it run Crysis?

Stonks

I upgraded from 18.1 to 19.1. I just used the 18.1 recovery instead of flashing the 19.1 recovery. It worked fine.
Update: Apparently I spoke too soon. After turning the phone off and on again, it won't boot

a1291762 said:
I upgraded from 18.1 to 19.1. I just used the 18.1 recovery instead of flashing the 19.1 recovery. It worked fine.
Update: Apparently I spoke too soon. After turning the phone off and on again, it won't boot
Click to expand...
Click to collapse
Yeah, thx for reporting this, apparently i've just uploaded a build with privapp permissions broken
for now you can use some old build i made https://abhiramshibu.tuxforums.com/~saalim/giovanni/daisy/lineage-19.1-20220319-UNOFFICIAL-daisy.zip
i should upload a new one as soon as possible (maybe tomorrow/today)

Its_Vixano said:
Yeah, thx for reporting this, apparently i've just uploaded a build with privapp permissions broken
Click to expand...
Click to collapse
I poked at it some more. I seemingly cannot start the Lineage recovery anymore? It just ... boots into Lineage after a delay, but Lineage can't boot. I dunno if this is related to privapp or not
All of these do the same thing:
* Hold up when booting
* Hold down when booting then fastboot reboot recovery
* Hold down when booting then fastboot boot lineage-recovery.img
This isn't my daily driver so I'll get creative to try and restore it, or just blow it away
My recovery process:
* Boot into TWRP
* Flash Lineage 18.1
* Boot into (Lineage 18.1) recovery
* Install Lineage 19.1
* Boot into (Lineage 19.1) recovery
* Flash Gapps and Magisk
* Boot into system

a1291762 said:
I poked at it some more. I seemingly cannot start the Lineage recovery anymore? It just ... boots into Lineage after a delay, but Lineage can't boot. I dunno if this is related to privapp or not
All of these do the same thing:
* Hold up when booting
* Hold down when booting then fastboot reboot recovery
* Hold down when booting then fastboot boot lineage-recovery.img
This isn't my daily driver so I'll get creative to try and restore it, or just blow it away
Click to expand...
Click to collapse
Avoid using the 'fastboot boot' command, somehow it doesn't works
instead flash it directly into the boot partition 'fastboot flash boot lineage-recovery.img' and try to boot into the recovery

Its_Vixano said:
instead flash it directly into the boot partition 'fastboot flash boot lineage-recovery.img' and try to boot into the recovery
Click to expand...
Click to collapse
That didn't work for me even the first time - which is why I used the Lineage 18.1 recovery to flash the 19.1 zip.

a1291762 said:
That didn't work for me even the first time - which is why I used the Lineage 18.1 recovery to flash the 19.1 zip.
Click to expand...
Click to collapse
It should work, but sometimes it takes a couple of tries with reboots in between. I did not find a pattern yet, but in general flashing boot and doing the power vol+ combo should be fine. Maybe it's a timing thing, not sure. Try to switch which button you press first maybe, or try to press them at the exact same time. A bit weird, yeah
UPDATE: pressing the + button just a bit earlier seems to be doing the trick for me!

just done a test build for fixing the privapp permission issues (random bootloops caused by some normal reboots), seems fine here but i don't really trust my self
https://abhiramshibu.tuxforums.com/~saalim/giovanni/daisy/lineage-19.1-20220329-UNOFFICIAL-daisy.zip
report if something will be wrong with it
edit: Apparently it's fine so
New update released (20220329) (Checkout op for download link)
- Sync with latest lineageos changes
- Fix random bootloopos while rebooting

Its_Vixano said:
New update released (20220329) (Checkout op for download link)
- Sync with latest lineageos changes
- Fix random bootloopos while rebooting
Click to expand...
Click to collapse
I dunno how we're supposed to do updates for this ROM?
I did this:
* boot to recovery
* adb sideload lineage.zip
* reboot to recovery (changes slot)
* adb sideload gapps.zip (gotta do this each time?)
* adb sideload Magisk.apk (gotta do this each time?)
* reboot to system
I did a few reboots and power off/on cycles and it didn't fail to boot. So I guess the privapp thing was fixed

a1291762 said:
I dunno how we're supposed to do updates for this ROM?
I did this:
* boot to recovery
* adb sideload lineage.zip
* reboot to recovery (changes slot)
* adb sideload gapps.zip (gotta do this each time?)
* adb sideload Magisk.apk (gotta do this each time?)
* reboot to system
I did a few reboots and power off/on cycles and it didn't fail to boot. So I guess the privapp thing was fixed
Click to expand...
Click to collapse
Yep, that's the right way to update the rom

I have an old CrDroid rom on the phone
It is time to upgrade to a new and better 18.1 or 19.1 (the more stable is?).
I read the thread, but now I need to know and follow the correct procedure to avoid errors. I use Fdroid and Adway as adblock. Is Magisk necessary? Should the switch between the two A / B partitions always be done during installation or for updates?
Thanks to who will answer

nabav said:
I have an old CrDroid rom on the phone
It is time to upgrade to a new and better 18.1 or 19.1 (the more stable is?).
I read the thread, but now I need to know and follow the correct procedure to avoid errors. I use Fdroid and Adway as adblock. Is Magisk necessary? Should the switch between the two A / B partitions always be done during installation or for updates?
Thanks to who will answer
Click to expand...
Click to collapse
- Just follow the instructions, everything is written here
- Should be stable enough for daily driving it, sadly i don't use daisy anymore as a 'primary' device
- I also use fdroid and adaway and they don't require root

a1291762 said:
I dunno how we're supposed to do updates for this ROM?
I did this:
* boot to recovery
* adb sideload lineage.zip
* reboot to recovery (changes slot)
* adb sideload gapps.zip (gotta do this each time?)
* adb sideload Magisk.apk (gotta do this each time?)
* reboot to system
I did a few reboots and power off/on cycles and it didn't fail to boot. So I guess the privapp thing was fixed
Click to expand...
Click to collapse
Hi a1291762,
is the above an alternative method to go from Lineageos 18.1 to Lineagos 19.1 or should the original procedure from Its_Vixano be used? If it is an upgrade procedure rather than an update procedure (are those to be expected at all?) can you give a more detailed explanation? I have TWRP 3.5.2_9.2 and Magisk on my phone, however, TWRP should not be used for flashing 19.1 because of FBE build (what's that?). Does your procedure work with fastboot or adb? Whatsoever, though it is not my daily driver I am very happy with my Mi A2 Lite with TWRP and Magisk but I also like playing... (with 75 years).
Thanks for all of your efforts!
grufty47

grufty47 said:
is the above an alternative method to go from Lineageos 18.1 to Lineagos 19.1 or should the original procedure from Its_Vixano be used?
Click to expand...
Click to collapse
The OP guide seems to be written for people coming from something other than Lineage. The first part of it sets up the Lineage recovery and formats user data.
Since I was coming from Lineage and already had the recovery, I figured I could skip those steps. The OP guide says you can skip formatting data if you're coming from Lineage and I figured the recovery can't have changed too much.
I don't know how much testing was done for a Lineage 18 -> 19 upgrade. It worked for me but I barely had anything installed when I did it. Make backups in case of data loss and all that.
Something I don't understand in the OP guide is the suggestion to use the copy_partitions script. It only seems useful if your phone is somehow in an odd situation where miscellaneous A and B partitions don't match? It can't hurt to run it I guess.
grufty47 said:
can you give a more detailed explanation?
Click to expand...
Click to collapse
My 18->19 upgrade process matches the 19 "OTA" process. Refer to the OP guide for screenshots and details.
1. Boot to recovery
2. Sideload the lineage zip
3. Reboot to recovery (changes the active slot)
4. Sideload gapps
5. Sideload Magisk
The lineage zip is like a "full OTA" for the stock ROM. Flashing it overwrites system, boot and vendor, hence the need to flash gapps and magisk again. But the recovery only supports flashing to the current slot, hence the reboot in the middle.
grufty47 said:
I have TWRP 3.5.2_9.2 and Magisk on my phone, however, TWRP should not be used for flashing 19.1 because of FBE build (what's that?).
Click to expand...
Click to collapse
FBE has to do with encryption. I found this that might help explain it.
https://www.reddit.com/r/LineageOS/comments/hd534a
Booting TWRP 3.5.2_9.2 (fastboot boot twrp.img) shows only garbage names under /sdcard plus a bunch of other places (but not all of /data). So I guess TWRP doesn't support FBE encryption? I'm not sure why that matters for flashing system partitions, but if any of lineage, gapps or magisk expects to write to places covered by FBE then clearly that's not going to work properly under TWRP.
Since you have installed TWRP over the Lineage recovery, you'll have to get a Lineage recovery back on your phone before you can upgrade. Using the provided recovery should work I guess? If not, you could use TWRP to flash the most recent Lineage 18 zip, which will also replace TWRP with Lineage recovery. Part of the reason I attempted the 18->19 upgrade in the first place is because I couldn't get the provided recovery to boot on my phone.
I hope that helps.
Lincoln