Develop Bugs

[ROM][UNOFFICIAL][LineageOS][19.1][dragon] -> 2023-01-11 (DISCONTINUED)

{
"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 19.1​
Android 12
lineage-19.1-20230111-UNOFFICIAL-dragon.zip -> DISCONTINUED
Known issues:
- Camera is not working yet.
- SELinux is permissive.
- Our "old" Nivida codecs do have problems to play videos in Chrome-based browsers.
(Rename or remove /vendor/lib/libnvomx.so and reboot system to switch to
software video codecs.)
- Chrome browser starts slowly.
- As it looks like Widevine L1 has been revoked by end of August 2020.
- Maybe more issues ..
Installation:
1. Boot into TWRP
2. Wipe SYSTEM and DATA partitions !
3. Install ROM.zip
4. install gapps (arm64)
5. install Magisk.zip (25.2)
6. Wipe CACHE and DAVLIK
7. Reboot into system
Enjoy 12
Android 11
lineage-18.1-20220216-UNOFFICIAL-dragon.zip -> DISCONTINUED
Known issues:
- SELinux is permissive.
- Our "old" Nivida codecs do have problems to play videos in Chrome-based browsers.
(Rename or remove /vendor/lib/libnvomx.so and reboot system to switch to
software video codecs.)
- Chrome browser starts slowly.
- Camera/Video may stops working after some time in use.
- As it looks like Widevine L1 has been revoked by end of August 2020.
Fresh Installation / Upgrade from any other ROM:
1. Boot into TWRP
2. Wipe SYSTEM and DATA partitions ! (If you are encrypted, pls format DATA partition !)
3. Install ROM.zip
4. install gapps (arm64)
5. install Magisk.zip (21.x)
6. Wipe CACHE and DAVLIK
7. Reboot into system
Upgrade from previous lineage-18.x builds:
1. Boot into TWRP
2. Install ROM.zip
3. Re-Install Magisk 21.x
4. Wipe CACHE and DAVLIK
5. Reboot into system
Enjoy 11
Android 10
lineage-17.1-20201211-UNOFFICIAL-dragon.zip -> DISCONTINUED
Known issues:
- SELinux is permissive.
- Our "old" Nivida codecs do have problems to play videos in Chrome-based browsers.
(Rename or remove /vendor/lib/libnvomx.so and reboot system to switch to
software video codecs.)
- Camera/Video may stops working after some time in use.
- As it looks like Widevine L1 has been revoked by end of August 2020.
system-as-root (SAR)
For gapps installation issues and more information ..
Pls read first .. https://forum.xda-developers.com/showpost.php?p=80693701&postcount=1350
Fresh Installation / Upgrade from any other ROM:
1. Boot into TWRP
2. Wipe SYSTEM and DATA partitions ! (If you are encrypted, pls format DATA partition !)
3. Install ROM.zip
4. install gapps (arm64)
5. install Magisk.zip (20.x+)
6. Wipe CACHE and DAVLIK
7. Reboot into system
Upgrade from previous lineage-17.1 builds:
1. Boot into TWRP
2. Install ROM.zip
3. Wipe CACHE and DAVLIK
4. Reboot into system
- The ROM does contain it's own vendor.img ! (If you go back to Oreo, pls reinstall stock vendor.img)
Enjoy TEN
Android Pie
lineage-16.0-20191017-UNOFFICIAL-dragon.zip -> DISCONTINUED
Known issues:
- Encryption seems not to work - and has not been tested. -> Pls do not encrypt your data partition yet !
- Keymaster -> If you set Pattern, PIN or Password the Screen unlock may not work correctly.
Workaround for Pattern: On fresh boot you will need to wait a bit longer before you enter credentials.
The waiting time is required on fresh boot only, the following unlocks are working normally.
In case of problems pls use Update.ZIP_TWRP_flashable_pattern_pin_remover_V2.zip to remove pattern/pin or password.
Installation:
1. Boot into TWRP (latest available version)
2. Wipe system, cache, dalvik and data partitions ! ( If you have encrypted /data partition - pls "format" /data via TWRP first ! )
3. Install lineage-16.0-201Yxxyy-UNOFFICIAL-dragon.zip
4. Install Opengapps
5. install Magisk.zip (tested with 18.x)
6. Reboot into system ..
- The ROM does contain it's own vendor.img ! (If you go back to Oreo, pls reinstall stock vendor.img)
And big thanks to @NYCHitman1 (Dirty Unicorn) !
Without his work the Android Pie project would not have been possible !
I have uploaded the last official Lineage Oreo build to androidfilehost.com ..
lineage-15.1-20200221-nightly-dragon-signed.zip - -> DISCONTINUED
SOURCES:
https://github.com/followmsi/manifests/tree/dragon-lineage-18.1
DOWNLOADS:
https://drive.google.com/drive/fold...oaU1iazg?resourcekey=0-4krcBcSF3tnMFvgcP4kMvw
https://androidfilehost.com/?w=files&flid=289293
Enjoy LineageOS on your Pixel C .. [/B]

RESERVED

Here you are ..

TWRP loop for me. Installs with no errors but won't boot into the os
I did a dirty (coming from AOSP 7.1.2) and then clean install. Haven't factory refreshed yet.
Tried wiping again and flashing back to aosp and having the same issue.
Any thoughts?
edit: now trying to pull some data off my tablet to do a full wipe, i dont NEED to do this, but would like to...but twrp wont recognize MTP on my system (win 10) ... problems problems today

minieod said:
TWRP loop for me. Installs with no errors but won't boot into the os
I did a dirty (coming from AOSP 7.1.2) and then clean install. Haven't factory refreshed yet.
Tried wiping again and flashing back to aosp and having the same issue.
Any thoughts?
edit: now trying to pull some data off my tablet to do a full wipe, i dont NEED to do this, but would like to...but twrp wont recognize MTP on my system (win 10) ... problems problems today
Click to expand...
Click to collapse
Did you format system ?
Pls do as first step.
If you boot loop install boot.img via fastboot.
No problems here.. it's quite fast !
Also dirty installation .. kept all my settings.
EDIT:
Mtp should work .. correct driver in Windows ?
We are using abd and mtp at the same time.
A Windows driver is on the share as well ..

Made a LineageOMS version as well ..
lineageOMS-14.1-20170418-UNOFFICIAL-dragon-followmsi.zip
Based on LineageOMS sources ...
https://github.com/LineageOMS
Enjoy

followmsi said:
Made a LineageOMS version as well ..
lineageOMS-14.1-20170418-UNOFFICIAL-dragon-followmsi.zip
Based on LineageOMS sources ...
https://github.com/LineageOMS
Enjoy [/QUOT
Is the nav bar laid out like stock
Click to expand...
Click to collapse

followmsi said:
Did you format system ?
Pls do as first step.
If you boot loop install boot.img via fastboot.
No problems here.. it's quite fast !
Also dirty installation .. kept all my settings.
EDIT:
Mtp should work .. correct driver in Windows ?
We are using abd and mtp at the same time.
A Windows driver is on the share as well ..
Click to expand...
Click to collapse
Hey follow
Yep did all of that. Formatted system, flashed boot.img, and no issues with mtp prior to the boot loops.
I went ahead and did a complete userdata reset and am sampling the O DP1 now ..I'm sure it'll work fine when (if) I come back to 7.x

Officialness
Thanks for building this. Hoping to try it out this weekend.
I'm hoping you intend to submit this build officially to LineageOS, so we continue to get updated builds. As you probably remember Cyanogen didn't accept the Pixel C. Hopefully with LineageOS things are better.

gaufres said:
Thanks for building this. Hoping to try it out this weekend.
I'm hoping you intend to submit this build officially to LineageOS, so we continue to get updated builds. As you probably remember Cyanogen didn't accept the Pixel C. Hopefully with LineageOS things are better.
Click to expand...
Click to collapse
You are not the first asking me this question ..
Here some more information ..
https://wiki.lineageos.org/submitting_device.html
Who is the maintainer ? .. me
- Changing vendor stuff .. monthly
- Applying kernel patches .. monthly
- Applying possible device tree patches and changes .. monthly
- Etc.
Here is the manifest for LOS ..
https://github.com/followmsi/manifests/tree/dragon-lineageos-cm-14.1
Also for the people who like to build their own verison
- As you may see we are removing 2 LOS repos today, due to build errors.
- This needs to be fixed on code level first - commited on LOS github.
- The stock google vendor.img needs to be integrated into the LOS Installer
Still not clear how this is done for "official" lineageos .. also from legal point of view.
Actually I need to get information here ... How is this done for other ROMs having a dedicated vendor.img ?
- The missing integrated kernel building was impemented a few minutes before
https://github.com/followmsi/androi...mmit/316a7e0e87b191bcf11b8de55778ddec83fac2f8
https://github.com/followmsi/android_kernel_tegra/commit/3e3e24c41db74693efc2fc74efaf6286b1c06013
You see there a few issues left ..
The ROM works perfectly but its not ready to be official yet.
Don't want to force and push a go live now .. No need to rush !
Hope you have a better understanding now ..
Cheers

Reuben_skelz92 said:
followmsi said:
Made a LineageOMS version as well ..
lineageOMS-14.1-20170418-UNOFFICIAL-dragon-followmsi.zip
Based on LineageOMS sources ...
https://github.com/LineageOMS
Enjoy [/QUOT
Is the nav bar laid out like stock
Click to expand...
Click to collapse
No !
The OMS version is the same like lineageOS but including OMS - to be ready to install substratum .. etc.
Made a version for Nexus 10 as well .. it seems to work fine.
Just have installed the ROM .. works fine - but did no special customizations or anything else.
Hope this helps ..
Click to expand...
Click to collapse

Debugging bootloop
followmsi said:
Did you format system ?
Pls do as first step.
If you boot loop install boot.img via fastboot.
Click to expand...
Click to collapse
Unfortunately this is also bootlooping for me. I've tried the steps above.
How can I help debug this? I was not able to use logcat. Does logcat work for you?

gaufres said:
Unfortunately this is also bootlooping for me. I've tried the steps above.
How can I help debug this? I was not able to use logcat. Does logcat work for you?
Click to expand...
Click to collapse
You did flash boot.img via fastboot ?
The ROM installation had no errors ?
What version of bootloader are you using .. .50 for 7.1.2 ?
Do you see the LOS logo (boot animation) when you boot-loop ?
Are you able to make a md5 hash ..Or similar to compare ?
File corrupt ?
Pls post a hash value to compare .. maybe onedrive is the problem.
Was not the first time a file was corrupted.
I am testing several ROMs and kernels in the last days .. no problems at all.
EDIT:
Which version of TWRP ?
EDIT2:
For your understanding.. logcat will start a short time after Android is booting.(boot animation)
But if you not pass the boot.img we have another issue. (Google logo)

Re: Debugging bootloop
followmsi said:
You did flash boot.img via fastboot ?
Click to expand...
Click to collapse
Yes. No errors.
followmsi said:
The ROM installation had no errors ?
Click to expand...
Click to collapse
None.
followmsi said:
What version of bootloader are you using .. .50 for 7.1.2 ?
Click to expand...
Click to collapse
I think so. Version 7900.50.0 from n2g47d.
followmsi said:
Do you see the LOS logo (boot animation) when you boot-loop ?
Click to expand...
Click to collapse
It doesn't get that far.
I see the unlocked bootloader warning. After thirty seconds it beeps, as expected. Then white "Google" text is then displayed for two or three seconds.
But after that it reboots into TWRP (blank screen, then unlocked bootloader warning, then beep, then white "Google" text, then TWRP).
followmsi said:
Are you able to make a md5 hash ..Or similar to compare ?
Click to expand...
Click to collapse
The update zip I'm installing from TWRP is lineage-14.1-20170417-UNOFFICIAL-dragon-followmsi.zip, which I downloaded from OneDrive. It has SHA256 hash
Code:
d124b4048f096317f593fa5dbf313ceaebbddd4352f0422276a86fd5f6707902
The boot.img I'm flashing with fastboot comes from the above zip. So it might be redundant for me to say the boot.img has SHA256 hash
Code:
cde8c7376d2d8d9d35ea5558473a669f91a27b0489f21b7a3cdb79af4a4ba931
followmsi said:
Pls post a hash value to compare .. maybe onedrive is the problem.
Was not the first time a file was corrupted.
Click to expand...
Click to collapse
I'm kinda hoping that is the problem, because otherwise this will be a pain to debug!
followmsi said:
I am testing several ROMs and kernels in the last days .. no problems at all.
Click to expand...
Click to collapse
Good. Weird.
followmsi said:
Which version of TWRP ?
Click to expand...
Click to collapse
Your build of 3.1.0-0.
followmsi said:
For your understanding.. logcat will start a short time after Android is booting.(boot animation)
But if you not pass the boot.img we have another issue. (Google logo)
Click to expand...
Click to collapse
Thanks for the explanation. So it might be boot.img given the boot sequence I described above?

I always get the TWRP bootloop if I boot before installing SuperSU. That happened with DU and with this.
I also had some issues with the setup wizard crashing. It was skipping the step of connecting wifi, and then it would crash when I tried to enter a Google account (which wouldn't have worked anyway without wifi.) I tried different gapps, same result. Finally I managed to swipe open settings and connect to wifi and now I'm set.
Now that I've got it running (OMS variant) it's great.

gaufres said:
Yes. No errors.
None.
I think so. Version 7900.50.0 from n2g47d.
It doesn't get that far.
I see the unlocked bootloader warning. After thirty seconds it beeps, as expected. Then white "Google" text is then displayed for two or three seconds.
But after that it reboots into TWRP (blank screen, then unlocked bootloader warning, then beep, then white "Google" text, then TWRP).
The update zip I'm installing from TWRP is lineage-14.1-20170417-UNOFFICIAL-dragon-followmsi.zip, which I downloaded from OneDrive. It has SHA256 hash
Code:
d124b4048f096317f593fa5dbf313ceaebbddd4352f0422276a86fd5f6707902
The boot.img I'm flashing with fastboot comes from the above zip. So it might be redundant for me to say the boot.img has SHA256 hash
Code:
cde8c7376d2d8d9d35ea5558473a669f91a27b0489f21b7a3cdb79af4a4ba931
I'm kinda hoping that is the problem, because otherwise this will be a pain to debug!
Good. Weird.
Your build of 3.1.0-0.
Thanks for the explanation. So it might be boot.img given the boot sequence I described above?
Click to expand...
Click to collapse
[HashChecker]
[File]/storage/emulated/0/download/lineage-14.1-20170417-UNOFFICIAL-dragon-followmsi.zip
[MD5]C79F1066186FF36C55643E264B3647E2
[SHA1]4DDD0A811FE22359D745335AA563023E95E808D3
[SHA256]D124B4048F096317F593FA5DBF313CEAEBBDDD4352F0422276A86FD5F6707902
At least the sha256 matches
Good bootloader
Good TWRP version ..
Do you install supersu at last step of your installation procedure ?
After you did install the ROM in TWRP, pls install supersu.zip (2.79 -sr3) as last step.
It will boot twice for the first time .. but then it should boot normally.

badwiring said:
I always get the TWRP bootloop if I boot before installing SuperSU. That happened with DU and with this.
I also had some issues with the setup wizard crashing. It was skipping the step of connecting wifi, and then it would crash when I tried to enter a Google account (which wouldn't have worked anyway without wifi.) I tried different gapps, same result. Finally I managed to swipe open settings and connect to wifi and now I'm set.
Now that I've got it running (OMS variant) it's great.
Click to expand...
Click to collapse
The SetupWizard is related to gapps .. the beans version seems to run perfectly.
Opengapps seems still to have issues on certain devices.
Will check supersu topic ..
Thanks for the feedback !

badwiring said:
I always get the TWRP bootloop if I boot before installing SuperSU.
Click to expand...
Click to collapse
followmsi said:
Do you install supersu at last step of your installation procedure ?
Click to expand...
Click to collapse
Thanks both. That's it.
No su: bootloops.
Lineage extras su: bootloops
SuperSU: boots OK
Magisk: boots OK

gaufres said:
Thanks both. That's it.
No su: bootloops.
Lineage extras su: bootloops
SuperSU: boots OK
Magisk: boots OK
Click to expand...
Click to collapse
Cool !
Found the issues as well ..
It's related to DM-verity .. even some config is missing.
Or the overwrite of build_fingerprint is related.
Need to investigate ..
Both supersu and magisk are removing the DM-verity checks in ramdisk.(boot.img)
As I always install supersu, I never realized.
Just compiling a new version .. changed the sources.
https://github.com/followmsi/androi...mmit/aae5804e75f4133ec82253cf6b2afbe39e46a56a
Removing DM-verity from fstab .. should solve this issue, also without supersu.
At later stage we can enable again, if it's working fine.
Thanks for your help testing ..
Cheers

New release ..
lineage-14.1-20170421-UNOFFICIAL-dragon-followmsi.zip
Changes:
- Integrated kernel compiling - using DU branch
- disabled DM-verity -> should fix proper booting even without supersu/magisk.
- General LineageOS changes -> fresh repo sync from today .. https://download.lineageos.org/
Installation:
1. Boot into TWRP
3. Install lineage-14.1-20170421-UNOFFICIAL-dragon-followmsi.zip
4. install SuperSU-v2.79-201612051815.zip (optional)
6. Reboot into system ..
- The ROM installer will keep your existing gapps installation.
- If you had SuperSu installed before you need to install it again - as we overwrite the boot.img completely.
A new OMS version will come later ..
Enjoy ..

[RECOVERY][ROOT]TWRP 3.1.1-1 Samsung Galaxy J7 MAX 2017 SM-G615F

Unofficial release -TWRP recovery for the Galaxy J7 Max 2017 - SM-G615F MEDIATEK MT6757
{
"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"
}
TWRP 3.1.1-0 Released
May 19, 2017
TWRP 3.1.1-0 is out now for all currently supported devices.
What's new in 3.1.1-0:
Backups will now include adopted storage keys (Dees_Troy)
Fixed an adb restore issue (bigbiff)
Fixed rebooting when no OS is present (Dees_Troy)
Fixed line wrapping in the GUI terminal (_that)
Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)Updated TWRP source code to AOSP 7.1.2
Update 25/11/2017
TWRP 3.1.1-1 NN build released.
Current status: BETA
Features:
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source
Factory Image flashing(see below)
NTFS support
F2FS support >> To be added
Twrp app support
New feature available in TWRP v3 is system image backup and restore and factory image flashing (see TWRP changelog for details)
Basically this means factory system images from the official firmware can now be flashed with TWRP.
This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
Flash with ODIN 3.12.7 in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: FAILURE TO FOLLOW THE STEPS ABOVE IMPLICITLY WILL RESULT IN STOCK RECOVERY REPLACING TWRP AT FIRST BOOT.
NOTE2: THIS DEVICE USES DM-VERITY, ANY CHANGES TO THE SYSTEM PARTITION COULD CAUSE THE DEVICE TO BOOTLOOP. IT MAY BE NECESSARY TO FLASH THE BOOT IMAGE PATCH BELOW.
NOTE: ON ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD:
twrp_3.1.1-1_sm-g615f_26817
To Root:
Flash the latest Magisk release with TWRP:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
To disable forced encryption, dm-verity and mount internal storage (/data) :
1. Boot to Twrp
2. Format the Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install Magisk
5. Reboot
TWRP DEVICE Tree: https://github.com/ashyx/TWRP_Samsung_j7maxlte
Kernel source: https://github.com/ashyx/KERNEL_j7maxlte
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, Teamwin
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU

NOTE: I built this months ago, but forgot to post it up!
.

Great work @ashyx can you please share device tree

I Tested the recovery on my J7 Max and it's working perfectly after flashing the "Boot image patch : no-verity-no-encrypt_ashyx".
one thing i want to tell that the recovery bootlooped(Rebooting the system or Shutting down and again powering on boots into Twrp) the first time i booted it but after flashing Magisk 14.0 and the "no-verity-no-encrypt" patch it works fine.
I've attached the recovery and kernel logs.
Also add a Warning for users to backup their data as i lost all my data after flashing (
and
Thank you for building a TWRP for my device
If you have free time can you please try to build LineageOS for J7 Max

Can you please share the device tree ?

Rumorbox33 said:
Can you please share the device tree ?
Click to expand...
Click to collapse
Yes when I have the opportunity, but be aware twrp device trees are no good for building LineageOS or other custom OS systems.

Thank you for replying.
i just want to study it, upload whenever you have the time

Samsung j700h

[email protected] said:
Samsung j700h
Click to expand...
Click to collapse
No

ashyx said:
Unofficial release -TWRP recovery for the Galaxy J7 Max 2017 - SM-G615F MEDIATEK MT6757
TWRP 3.1.1-0 Released
May 19, 2017
TWRP 3.1.1-0 is out now for all currently supported devices.
What's new in 3.1.1-0:
Backups will now include adopted storage keys (Dees_Troy)
Fixed an adb restore issue (bigbiff)
Fixed rebooting when no OS is present (Dees_Troy)
Fixed line wrapping in the GUI terminal (_that)
Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)Updated TWRP source code to AOSP 7.1.2
Update 25/11/2017
TWRP 3.1.1-1 NN build released.
Current status: BETA
Features:
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source
Factory Image flashing(see below)
NTFS support
F2FS support >> To be added
Twrp app support
New feature available in TWRP v3 is system image backup and restore and factory image flashing (see TWRP changelog for details)
Basically this means factory system images from the official firmware can now be flashed with TWRP.
This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
Flash with ODIN 3.12.7 in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: FAILURE TO FOLLOW THE STEPS ABOVE IMPLICITLY WILL RESULT IN STOCK RECOVERY REPLACING TWRP AT FIRST BOOT.
NOTE2: THIS DEVICE USES DM-VERITY, ANY CHANGES TO THE SYSTEM PARTITION COULD CAUSE THE DEVICE TO BOOTLOOP. IT MAY BE NECESSARY TO FLASH THE BOOT IMAGE PATCH BELOW.
NOTE: ON ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD:
twrp_3.1.1-1_sm-g615f_26817
To Root:
Flash the latest SuperSU release with TWRP:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
To disable forced encryption, dm-verity and mount internal storage:
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, Teamwin
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
Click to expand...
Click to collapse
Please post your source code This have been up for roughly a month And we need em....Thank you good sir for your hard work

Hi since j7 plus has same chipset.. Can we use this also? Thanks

ashyx said:
No
Click to expand...
Click to collapse
@ashyx Please read PMs.

TheMadScientist said:
@ashyx Please read PMs.
Click to expand...
Click to collapse
I'm guessing you're asking me to post the kernel source as I'm sure you're aware that TWRP device trees are not subject to any license as they are merely config files?
TWRP source code is freely available from their GITHUB.
However I shall endeavour to post the kernel source and device tree.

ashyx said:
I'm guessing you're asking me to post the kernel source as I'm sure you're aware that TWRP device trees are not subject to any license as they are merely config files?
TWRP source code is freely available from their GITHUB.
However I shall endeavour to post the kernel source and device tree.
Click to expand...
Click to collapse
Thank you and disregard any PMS and such all have been reversed

https://imgur.com/a/LHpfm
I did everything said amd everything worked fine and flawlessly. I wanted to spoof in pokemon go by changing an app to system app after rooting and installing magisk bt it gives the error as shown in pic. please help. i m a total noob. i think this was cause i formatted data partition bt i thought it was part of root process. was that necessasry for me do i.e format data partition? Can nybody tell me why i cant move app to system and what can be done? plsssss
Edit: is it beacause the system is not mounted? How to mount a system using twrp? And what does mounting a system actually mean ?

Yuaan rai said:
https://imgur.com/a/LHpfm
I did everything said amd everything worked fine and flawlessly. I wanted to spoof in pokemon go by changing an app to system app after rooting and installing magisk bt it gives the error as shown in pic. please help. i m a total noob. i think this was cause i formatted data partition bt i thought it was part of root process. was that necessasry for me do i.e format data partition? Can nybody tell me why i cant move app to system and what can be done? plsssss
Edit: is it beacause the system is not mounted? How to mount a system using twrp? And what does mounting a system actually mean ?
Click to expand...
Click to collapse
You can use any file manager with root support to move the apk to /system/app

Rumorbox33 said:
You can use any file manager with root support to move the apk to /system/app
Click to expand...
Click to collapse
Used every app and file manager but to no avail. Finally used twrp itself and boom the problem was solved. Thnks anyway.

Any custom roms for samsung j7 max sm-g615f ??
Plez help

Hey I am using samsumg galaxy j7 2015 model which rooted and have twrp recovery in it so I want to add kernel into it so can you give the file and the method to do so and also the best rom for my device

Hey, i built TWRP 3.2.1-1 for this device including some fixes such as pixel format and many more, will you update the thread if i give you the twrp and device trees or i have to make another thread ?

[ROM][OFFICIAL][RIVER][NIGHTLIES] LineageOS 17.1

{
"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"
}
Moto G7
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Introduction:
This is the Official Lineage OS 16.0 thread for the Motorola Moto G7, codename river.
Join our Moto G7 Development Telegram Group!
How to Install:
Please follow the instructions on our Official LineageOS Wiki page here.
IF YOU ARE COMING FROM STOCK AND WANT TO INSTALL CUSTOM ROMS FOR FIRST TIME, INSTALL "Copy Partitions Zip" FROM POST #2
If you don't follow these instructions, please don't expect support here. We also don't support 3rd party addons (Magisk/XPosed/Dolby/Viper/etc.), so please don't seek support if you use these.
Notes:
Official Lineage OS builds will not pass CTS/SafetyNet -- due to the AVB flag's "red" status. (Magisk works fine with SafetyNet patcher modules, though is not supported.)
Download:
LineageOS Updater
XDA:DevDB Information
river-lineageos, ROM for the Moto G7
Contributors
erfanoabdi, SyberHexen
Source Code: https://github.com/LineageOS
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: LineageOS
Version Information
Status: Nightly
Created 2019-11-16
Last Updated 2020-08-09

Copy Partitions Zip
- courtesy @ @filipepferraz
Download

Reserved

sim card is not working
currently I use
lineage-16.0-20191118-nightly-river version
XT1962-5 (Europe/Global) model
The phone didn't detect sim card.
It is dual sim model but in any slot, didn't work.

' . ' said:
currently I use
lineage-16.0-20191118-nightly-river version
XT1962-5 (Europe/Global) model
The phone didn't detect sim card.
It is dual sim model but in any slot, didn't work.
Click to expand...
Click to collapse
Did you try removing the sim and put back in while the system is on?

SyberHexen said:
Did you try removing the sim and put back in while the system is on?
Click to expand...
Click to collapse
I did, and tried when power off as well.
The other OS versions (NOV.15, NOV.16) also showed 'No sim' state.
But after I roll back to stock rom, they are working again.

SyberHexen said:
Did you try removing the sim and put back in while the system is on?
Click to expand...
Click to collapse
And I don't know why, but on your unofficial latest Lineage os (lineage-16.0-20191001-UNOFFICIAL-river) , the sim card working well...
but on the official version, didn't work.

' . ' said:
And I don't know why, but on your unofficial latest Lineage os (lineage-16.0-20191001-UNOFFICIAL-river) , the sim card working well...
but on the official version, didn't work.
Click to expand...
Click to collapse
My last build there was with prebuilt vendor.img
This official LOS 16.0 includes a source built vendor.img

install gapps
SyberHexen said:
My last build there was with prebuilt vendor.img
This official LOS 16.0 includes a source built vendor.img
Click to expand...
Click to collapse
does anyone know where I can download the gapps, the android version is 9.1, they don't accept at https://opengapps.org/
alguien sabe donde puedo descargar las gapps, la version de android es 9.1, no aceptan en https://opengapps.org/

I am having issues with installing Lineage OS 16.0 on my G7 (XT1962-1). I'm using the file named lineage-16.0-20191118-nightly-river-signed.zip. I followed the instructions on the https://wiki.lineageos.org/devices/river/install page.
My phone's bootloader is unlocked, Developer Options are configured to allow OEM unlocking, and USB debugging. Motorola firmware version PPOS29.114-134-4 from the US Retail channel was installed. I subscribe to Google Fi.
1. I temporarily booted TWRP 3.3.1-2 using the "fastboot boot twrp-3.3.1-2-river.img" command. The file was downloaded from the TWRP URL for River. I pushed the twrp-installer-3.3.1-2-river.zip to the phone using adb and did an install zip procedure. TWRP was installed to both the a and b slots. I rebooted recovery and TWRP 3.3.1-2 launched normally.
2. In TWRP, I formatted data to remove encryption. I then wiped Dalvik/ART cache and system in the Advanced Wipe menu. I rebooted TWRP as per recommendation when formatting the data partition.
<<edit>> I did install the copy-partitions-ab.zip at this point.
3. I used the adb sideload procedure per the Lineage installation instructions for the ROM file referenced above. The installation appeared to complete normally.
4. I restarted adb sideload to install open_gapps-arm64-9.0-micro-20191119.zip which was downloaded from the opengapps.org site.
This is where things go abnormally. The open-gapps installation script starts to run and then ab-ends with error 64. The architecture doesn't match the installation file. The script reports my phone is arm, not arm64. I think we all know that the G7 hardware is arm64. So, I downloaded the open_gapps-arm-9.0-micro-20191119.zip and tried installing. That attempt generated error 70 (insufficient space in the system partition). I ran a df -k command in a terminal window in TWRP and /system is mounted with almost 3GB of space available.
I was very confused at this point, but I decided to try installing Magisk 20.1 using TWRP zip file install procedure. Interestingly, the magisk install script reported the architecture as arm (not arm64) and completed normally.
I tried to reboot the system, but TWRP warned that no OS was installed. I cancelled the reboot and did a power off.
I'm not new to LineageOS installation, I've been running LineageOS on my Nexus 6 for a couple of years. Please review the steps I've done and let me know what I'm screwing up. Thanks.

Try "fastboot -w" as formatting data in TWRP breaks boot. "No OS" warning in TWRP can be ignored

cou94114 said:
I think we all know that the G7 hardware is arm64. So...
Click to expand...
Click to collapse
Don't have this device yet myself, but to your point, Motorola has been known to put out a 32 build on 64 hardware before, and so the corresponding Lineage build was also 32. The Moto Z Play for instance.
Given your issues, it would be good to have confirmation from the OP as to what is the case with the G7.
　

cou94114 said:
I am having issues with installing Lineage OS 16.0 on my G7 (XT1962-1). I'm using the file named lineage-16.0-20191118-nightly-river-signed.zip. I followed the instructions on the https://wiki.lineageos.org/devices/river/install page.
My phone's bootloader is unlocked, Developer Options are configured to allow OEM unlocking, and USB debugging. Motorola firmware version PPOS29.114-134-4 from the US Retail channel was installed. I subscribe to Google Fi.
1. I temporarily booted TWRP 3.3.1-2 using the "fastboot boot twrp-3.3.1-2-river.img" command. The file was downloaded from the TWRP URL for River. I pushed the twrp-installer-3.3.1-2-river.zip to the phone using adb and did an install zip procedure. TWRP was installed to both the a and b slots. I rebooted recovery and TWRP 3.3.1-2 launched normally.
2. In TWRP, I formatted data to remove encryption. I then wiped Dalvik/ART cache and system in the Advanced Wipe menu. I rebooted TWRP as per recommendation when formatting the data partition.
<<edit>> I did install the copy-partitions-ab.zip at this point.
3. I used the adb sideload procedure per the Lineage installation instructions for the ROM file referenced above. The installation appeared to complete normally.
4. I restarted adb sideload to install open_gapps-arm64-9.0-micro-20191119.zip which was downloaded from the opengapps.org site.
This is where things go abnormally. The open-gapps installation script starts to run and then ab-ends with error 64. The architecture doesn't match the installation file. The script reports my phone is arm, not arm64. I think we all know that the G7 hardware is arm64. So, I downloaded the open_gapps-arm-9.0-micro-20191119.zip and tried installing. That attempt generated error 70 (insufficient space in the system partition). I ran a df -k command in a terminal window in TWRP and /system is mounted with almost 3GB of space available.
I was very confused at this point, but I decided to try installing Magisk 20.1 using TWRP zip file install procedure. Interestingly, the magisk install script reported the architecture as arm (not arm64) and completed normally.
I tried to reboot the system, but TWRP warned that no OS was installed. I cancelled the reboot and did a power off.
I'm not new to LineageOS installation, I've been running LineageOS on my Nexus 6 for a couple of years. Please review the steps I've done and let me know what I'm screwing up. Thanks.
Click to expand...
Click to collapse
try to roll back stock and install again without install 'copy-partition.zip'. I had same problem but after do that I can install it.

With latest rom, sim cards working perfectly and stable!
In particular, the microphone function is greatly improved compared to the manufacturer ROM!
Thanks!

Amazon have an "exclusive" G7 which is dual SIM and cheap for black Friday. I've seen suggestions it ships with bloatware but can be flashed with vendor's standard image. Is this the same as "river" and likely to work with official or unofficial LO 16? It may be the same as the dual sim version mentioned in previous post on this thread?

Slight problem. Im getting an error 70 while installing gapps. And attempting to resize the system partition through twrp does nothing.
This phone has been a pain in the ass with anything like this since I got it. But, I was finally able to get the rom installed and fully booted, But gapps just will not install. Even with Pico, it still says not enough space.
What am i missing? Ive never had a such a problem rooting a phone before I got into motorolas lol

crypysmoker said:
Slight problem. Im getting an error 70 while installing gapps. And attempting to resize the system partition through twrp does nothing.
This phone has been a pain in the ass with anything like this since I got it. But, I was finally able to get the rom installed and fully booted, But gapps just will not install. Even with Pico, it still says not enough space.
What am i missing? Ive never had a such a problem rooting a phone before I got into motorolas lol
Click to expand...
Click to collapse
I had the same issue. It's not the size of the partition, its the order the software is installed and the reboots done during the process. I joined the telegram group for the G7 and found some very helpful information related to the installation of LineageOS 16.0 on the G7. Here are the steps for a clean flash.
Very important - Flash the copy-partitionsAB.zip to replicate the slot A and slot B layout.
- Clean flash:
1) Put the phone in bootloader mode
1.2) Connect phone to PC with a USB cable.
1.3) In a Command prompt window, run "fastboot getvar all".
1.4) Make slot A the active slot "fastboot set_active a".
1.5) Boot TWRP "fastboot boot twrp.img" (use the file name on your PC for the TWRP img file)
1.6) check active slot in Reboot menu - set to A
2) Flash lineage zip
3) Flash twrp installer zip
3.5) Format data while in TWRP.
4) Reboot to bootloader from TWRP.
5) fastboot -w (this will wipe your userdata partition)
6) Reboot to TWRP recovery (it should be installed when you flashed the twrp-installer zip)
6.5) check active slot in Reboot menu - set to A
7) Flash opengapps zip (use the arm64 version)
7.5) Flash magisk zip (optional, only if you want root)
8) Reboot system on slot A
The G7 is my first A/B slot device and I struggled with the configuration. TWRP recovery is part of the boot partition. Installing the lineage zip, then the TWRP installer zip seems to be the required order. Then, rebooting TWRP from the installed image works to install OpenGApps. The active slot is very important, too. Many times during my installation ordeal, I would think that slot a was active, but it was slot b. I installed the copy-partitions zip when we were made aware of no bootloader on slot b a few weeks ago.
Good luck.

To install gapps successfully, reboot twrp after installing lineageos:
* fastboot boot twrp-3.3.1-2-river.img
* adb sideload lineage-16.0-20191122-nightly-river-signed.zip
* adb reboot bootloader
* fastboot boot twrp-3.3.1-2-river.img
* adb sideload open_gapps-arm64-9.0-nano-20191121.zip
In other news: Does NFC work for anyone?

reddich said:
To install gapps successfully, reboot twrp after installing lineageos:
* fastboot boot twrp-3.3.1-2-river.img
* adb sideload lineage-16.0-20191122-nightly-river-signed.zip
* adb reboot bootloader
* fastboot boot twrp-3.3.1-2-river.img
* adb sideload open_gapps-arm64-9.0-nano-20191121.zip
In other news: Does NFC work for anyone?
Click to expand...
Click to collapse
I don't see a step to flash twrp installer. Do you permanently install twrp in your procedure?

Awesome. Thank you guys. Looks like the main problems I was having are not fastboot -w and not rebooting fully into twrp to flash gapps. After flashing the twrp installer and rebooting, I would get a totally different recovery. I've rooted hundreds of phones, but these a/b phones seems to just be a huge pain in the patooty.
---------- Post added at 09:17 AM ---------- Previous post was at 09:08 AM ----------
reddich said:
To install gapps successfully, reboot twrp after installing lineageos:
* fastboot boot twrp-3.3.1-2-river.img
* adb sideload lineage-16.0-20191122-nightly-river-signed.zip
* adb reboot bootloader
* fastboot boot twrp-3.3.1-2-river.img
* adb sideload open_gapps-arm64-9.0-nano-20191121.zip
In other news: Does NFC work for anyone?
Click to expand...
Click to collapse
These phones do not have NFC capabilities.

[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

[ROM][UNOFFICIAL][UNIFIED] VoltageOS v2.2 [Android 13][January 23th, 2023]

{
"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"
}
VoltageOS 13.0 | Tiramisu for Mi A2 Lite (daisy)​
ABOUT
Greetings, interested users! You have reached the gateway of a simplistic, no frills pure AOSP experience that will not let you down in getting through every day uninterrupted by inconveniences, with just the right dab of customizations. Be it requiring safetynet for banking or payment apps to receiving the latest security patches from Google as soon as they're released, we've got you covered. It doesn't end there. Sit back, relax and let the system theme your device according to your preferences with Monet support. Step in and begin your journey with Voltage OS.
Features
Pure AOSP
Latest Security Patches
Google Monet
SafetyNet
More info: HERE
Telegram Voltage: Group
If you like our work you can buy us a cup of coffee
*TogoFire Maintainer Daisy
*PIX: [email protected]
WHAT WORKS?
Almost everything
WHAT DOESN'T WORK?
You tell me
Be sure to include a log : check how to
DOWNLOAD:
VoltageOS 2.2 230123: CLICK HERE
SHA256: 3c21e3f7c2b8c6f90f8c7388e0a481c6e842f313d2dfd04c5f6c6e5fcda18385
Gapps $hit Package (Recommended): LiteGapps | Microg | MindTheGapps
Recovery: HERE
If you use instagram or any $hit like facebook, use this: LINK
Installation Guide​Clean Flash
1) If you are coming from any MiuiROM, GSI, or any other PortROM, edl miflash from firmware 10.0.18.0 or 11.x.x is mandatory.
2) Edl firmware 11.x.xx or 10.x.xx (install firmware via miflash if needed)
3) Restore your persist backup (to keep your mac).
If you don't have the backup, put the persist oreo / or persist.img by fastboot mode (twice), or by zip - (recommended/optional; to avoid bugs like missing IMEI and other strange bugs).
4) Reboot to recovery
5) Boot to Recoovery
6) Format Data--Yes
7) Reboot to recovery
8) Wipe data, system, dalvik cache, internal storage.
9) Install ROM
10) Install TWRP
12) Reboot to recovery
13) Install LiteGapps (optional)
16) Install Magisk (optional)
17) Reboot to system
Dirty Flash
1) Backup Everything (Most Important)
2) Download ROM
3) Boot to TWRP (Power and vol+; or Advanced Restart > Recovery)
4) Backup Data partition (optional)
5) Install the 'update' ROM
6) Install TWRP ZIP (optional)
7) Then reboot to recovery. (Note: in current recovery the slot changes by itself, no longer need to change manually)
8) Install GApps that you've used to installed, and Magisk.
9) Wipe dalvik and reboot
10) Reboot to system
GUIDE FULL
Link​
ROM Source: https://github.com/VoltageOS
Source: Kernel & Device & Vendor
Support Links:​TogoFireWork Channel
TogoFireWork Group
McQuaidLab
XDA:DevDB Information
ROM OS Version: Android 13.0 | Tiramisu
ROM Kernel: Linux 4.9.X
ROM Firmware Required: 10.0.18, 11.0.04, 11.0.16 or greater
Based On: AOSP

reserved!

reserved...!!!

@TogoFire
Hi mate. Thanks for your efforts. I'm on SyberiaOS A13 version. Do i still need to flash firmware or can i install directly from recovery with format data system etc.? Thanks.

dr.bahaeddin said:
@TogoFire
Hi mate. Thanks for your efforts. I'm on SyberiaOS A13 version. Do i still need to flash firmware or can i install directly from recovert with format data system etc.? Thanks.
Click to expand...
Click to collapse
Being firmware greater than or equal to 10.0.18, it's fine. If it's coming from a Lupe rom, then just go straight to install the rom

Is this pre-overclocked? What are the clocks?

ortizjammet said:
Is this pre-overclocked? What are the clocks?
Click to expand...
Click to collapse
McQuaid Lab
McQuaid Lab Kernel: https://t.me/McQuaidKernel Download & Changelog: LINK Kernel Source If you like our work you can buy us a cup of coffee *TogoFire Maintainer *PIX: [email protected] Orangefox old OrangeFox Recovery Project...
forum.xda-developers.com

It will be helpful is guys share your experience about this rom...

New update!
Small important fixes made.
Changelog of the last commits: IMG | DT
Enjoy!

@TogoFire thanks again for the update. I wonder how can i enable Google auto fill? Apps dont recognize my saved singin infos.

dr.bahaeddin said:
@TogoFire thanks again for the update. I wonder how can i enable Google auto fill? Apps dont recognize my saved singin infos.
Click to expand...
Click to collapse
I don't use anything from google. I can't help. And this rom is security focused, maybe something disabled it by default. Ask someone who uses the rom, in telegram groups, if he managed to activate this. Or try another gapps. Perhaps in some network configuration there is an option to enable and disable this.

TogoFire said:
I don't use anything from google. I can't help. And this rom is security focused, maybe something disabled it by default. Ask someone who uses the rom, in telegram groups, if he managed to activate this. Or try another gapps. Perhaps in some network configuration there is an option to enable and disable this
Click to expand...
Click to collapse
TogoFire said:
I don't use anything from google. I can't help. And this rom is security focused, maybe something disabled it by default. Ask someone who uses the rom, in telegram groups, if he managed to activate this. Or try another gapps. Perhaps in some network configuration there is an option to enable and disable this.
Click to expand...
Click to collapse
If you are so focused on security, why is your ROM UNofficial?
Will it become OFFICIAL in the near future so that it is also suitable as a daily driver?

cappuccini said:
If you are so focused on security, why is your ROM UNofficial?
Will it become OFFICIAL in the near future so that it is also suitable as a daily driver?
Click to expand...
Click to collapse
Since when does it have to be official to be safe?
There are so many roms whether official or not that aren't good, so this has no relevance.
The trees are opensource, by the way.
I'm not a buildbot. So my builds are decent.
I already keep Official Xtended. It's enough for me. I don't have time to keep two official ROMs.

TogoFire said:
Since when does it have to be official to be safe?
There are so many roms whether official or not that aren't good, so this has no relevance.
The trees are opensource, by the way.
I'm not a buildbot. So my builds are decent.
I already keep Official Xtended. It's enough for me. I don't have time to keep two official ROMs.
Click to expand...
Click to collapse
...I'm sure all is as you write, however, I think it is wrong to equate Official and UNofficial. For OFFICIAL ROMs there are rules, which among other things also serve the security of the users, and not every user can read and check a source code...
Thank you for your statement and your certainly also very good work!

cappuccini said:
...I'm sure all is as you write, however, I think it is wrong to equate Official and UNofficial. For OFFICIAL ROMs there are rules, which among other things also serve the security of the users, and not every user can read and check a source code...
Thank you for your statement and your certainly also very good work!
Click to expand...
Click to collapse
Np.
These rules are useless to tell you the truth. I maintain Xtended Official, so I have an idea of how it works. It's like I told you. Being decent construction, it doesn't have any problems.
The only thing they require is that you know how to cherry-pick, know how to author commits, and have built at least one unofficial rom of theirs, and have at least a notion of how to fix bugs, and respect colleagues. They will look at your history and see how you behave. These rules will not prevent a buildbot.

TogoFire said:
Np.
These rules are useless to tell you the truth. I maintain Xtended Official, so I have an idea of how it works. It's like I told you. Being decent construction, it doesn't have any problems.
The only thing they require is that you know how to cherry-pick, know how to author commits, and have built at least one unofficial rom of theirs, and have at least a notion of how to fix bugs, and respect colleagues. They will look at your history and see how you behave. These rules will not prevent a buildbot.
Click to expand...
Click to collapse
...the requirements of the individual ROMs seem to differ a lot, with LOS for example they are supposed to be significantly higher.
what about the XDA rules? These also have to be complied with in an official ROM. what about banking apps and other security-critical apps in case of damage? Metadata is stored with every login. Even the proprietary messenger WhatsApp registers a custom ROM and refuses support.
In a Samsung thread a maintainer wrote that the unofficial ROM is only for testing.... A very difficult topic for me, ultimately everyone must decide for themselves who they trust.
Thanks for the insight into the world of developers and best regards

Because I prefer a "simplistic, no frills pure AOSP experience that will not let you down in getting through every day uninterrupted by inconveniences" (first post ABOUT section xD), on the contrary of the full customizable Xtended rom), and to succeed to the very satisfying but now lacking security updates Syberia A12 rom, I tried to install this one.
Unfortunately my a2 lite stays one the boot screen (animated yellow rom logo, I forced the restart after 15 minutes stuck on this logo...). I am not very experienced in flashing custom roms but it seems to me that I carefully followed the clean flash procedure:
miflash daisy_global_images_V11.0.18.0.QDLMIXM_10.0
fastboot mode and "fastboot oem unlock" command from computer
skip persist, was a test
"fastboot boot twrp-3.5.2_9-2-daisy-unofficial.img"
Wipe data, system, dalvik cache, internal storage.
Install voltage-2.2-daisy-20230123-0113-UNOFFICIAL.zip
Install twrp-3.5.2_9-2-daisy-unofficial.zip
Reboot to recovery
Install [RECOVERY]LiteGapps_arm64_12.0_v2.7_official.zip
Reboot to system
Tried again from point 5 and without gapps (went on the other slot) but still stuck on the boot animation.
Did I do a noob mistake? Should I go with the Xtended rom which has more feedbacks?
Thanks for help
Edit: in fact after miflash when I reboot it seems I have no recovery. Holding power + vol up leads to the "No command" screen. I used twrp img boot to do the data format and wipe data, system, dalvik cache, and internal storage. Is it different? Should I miflash a stock recovery?
Edit2: considering this:
"3) Restore your persist backup (to keep your mac).
If you don't have the backup, put the persist oreo / or persist.img by fastboot mode (twice), or by zip - (recommended/optional; to avoid bugs like missing IMEI and other strange bugs)."
Is it about restoring a backup of the inital persist.img file or more? And "by fastboot mode (twice)", what does it mean? On each A/B slot?
Edit3: exact same issue with Xtended rom... forced reboot after 30 minutes logo...

norva said:
Because I prefer a "simplistic, no frills pure AOSP experience that will not let you down in getting through every day uninterrupted by inconveniences" (first post ABOUT section xD), on the contrary of the full customizable Xtended rom), and to succeed to the very satisfying but now lacking security updates Syberia A12 rom, I tried to install this one.
Unfortunately my a2 lite stays one the boot screen (animated yellow rom logo, I forced the restart after 15 minutes stuck on this logo...). I am not very experienced in flashing custom roms but it seems to me that I carefully followed the clean flash procedure:
miflash daisy_global_images_V11.0.18.0.QDLMIXM_10.0
fastboot mode and "fastboot oem unlock" command from computer
skip persist, was a test
"fastboot boot twrp-3.5.2_9-2-daisy-unofficial.img"
Wipe data, system, dalvik cache, internal storage.
Install voltage-2.2-daisy-20230123-0113-UNOFFICIAL.zip
Install twrp-3.5.2_9-2-daisy-unofficial.zip
Reboot to recovery
Install [RECOVERY]LiteGapps_arm64_12.0_v2.7_official.zip
Reboot to system
Tried again from point 5 and without gapps (went on the other slot) but still stuck on the boot animation.
Did I do a noob mistake? Should I go with the Xtended rom which has more feedbacks?
Thanks for help
Edit: in fact after miflash when I reboot it seems I have no recovery. Holding power + vol up leads to the "No command" screen. I used twrp img boot to do the data format and wipe data, system, dalvik cache, and internal storage. Is it different? Should I miflash a stock recovery?
Edit2: considering this:
"3) Restore your persist backup (to keep your mac).
If you don't have the backup, put the persist oreo / or persist.img by fastboot mode (twice), or by zip - (recommended/optional; to avoid bugs like missing IMEI and other strange bugs)."
Is it about restoring a backup of the inital persist.img file or more? And "by fastboot mode (twice)", what does it mean? On each A/B slot?
Edit3: exact same issue with Xtended rom... forced reboot after 30 minutes logo...
Click to expand...
Click to collapse
...this installation guide has been very helpful to me:
[DEPRECATED] Detailed Installation Guide for Custom Roms (Mi A2 Lite - Daisy)
Heya, This is a guide aimed on helping you to switch to a custom rom from the stock firmware. For any questions, feel free to join our Telegram groups. PREREQUISITES 1) Stock rom recommended by the maintainer of the rom that you want to flash...
forum.xda-developers.com
P.S. I am currently testing MSM Xtended v4 with LiteGapps core, there were no problems during installation.

norva said:
Because I prefer a "simplistic, no frills pure AOSP experience that will not let you down in getting through every day uninterrupted by inconveniences" (first post ABOUT section xD), on the contrary of the full customizable Xtended rom), and to succeed to the very satisfying but now lacking security updates Syberia A12 rom, I tried to install this one.
Unfortunately my a2 lite stays one the boot screen (animated yellow rom logo, I forced the restart after 15 minutes stuck on this logo...). I am not very experienced in flashing custom roms but it seems to me that I carefully followed the clean flash procedure:
miflash daisy_global_images_V11.0.18.0.QDLMIXM_10.0
fastboot mode and "fastboot oem unlock" command from computer
skip persist, was a test
"fastboot boot twrp-3.5.2_9-2-daisy-unofficial.img"
Wipe data, system, dalvik cache, internal storage.
Install voltage-2.2-daisy-20230123-0113-UNOFFICIAL.zip
Install twrp-3.5.2_9-2-daisy-unofficial.zip
Reboot to recovery
Install [RECOVERY]LiteGapps_arm64_12.0_v2.7_official.zip
Reboot to system
Tried again from point 5 and without gapps (went on the other slot) but still stuck on the boot animation.
Did I do a noob mistake? Should I go with the Xtended rom which has more feedbacks?
Thanks for help
Edit: in fact after miflash when I reboot it seems I have no recovery. Holding power + vol up leads to the "No command" screen. I used twrp img boot to do the data format and wipe data, system, dalvik cache, and internal storage. Is it different? Should I miflash a stock recovery?
Edit2: considering this:
"3) Restore your persist backup (to keep your mac).
If you don't have the backup, put the persist oreo / or persist.img by fastboot mode (twice), or by zip - (recommended/optional; to avoid bugs like missing IMEI and other strange bugs)."
Is it about restoring a backup of the inital persist.img file or more? And "by fastboot mode (twice)", what does it mean? On each A/B slot?
Edit3: exact same issue with Xtended rom... forced reboot after 30 minutes logo...
Click to expand...
Click to collapse
Can it be that you have installed GApps for Android 12? This ROM is Android 13...

SOLVED! YEAH! Took me hours but finally got it!
So either the new stock rom (daisy_global_images_V11.0.21.0.QDLMIXM_10.0) did it or it is related to the installation with adb sideload or from SD card which caused my issue (I finally simply copy the installation zip files through USB while TWRP is active on the phone and gives access to the memory from computer, and installed them using the dedicated button (no adb sideload)).
Time to test now
@cappuccini : yeah I read this guide and had the android 13 gapps version (but you are right, it took me a while to understand it was the folder 33 on sourceforge...).