[ROM][UNOFFICIAL][UNIFIED] VoltageOS v2.2 [Android 13][January 23th, 2023] - Xiaomi Mi A2 Lite ROMs, Kernels, Recoveries, & Oth

[ROM][UNOFFICIAL][UNIFIED] VoltageOS v2.2 [Android 13][January 23th, 2023] - Xiaomi Mi A2 Lite ROMs, Kernels, Recoveries, & Oth

{
"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 GuideClean 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...).

Related

[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][UNOFFICIAL_MOD][DECRYPTION][UPDATED-02-01-2019] TWRP 3.2.3-4 for nitrogen

SUPPORTS ALL TYPES OF USERDATA DECRYPTION FOR BOTH OREO AND PIE ROMS - PASSWORD, DEFAULT_PASSWORD, PATTERN, PIN!!!
SUPPORTS BOTH FULL AND INCREMENTAL OTA UPDATE PACKAGES AUTOMATIC INSTALL!!!
Sharing my unofficial TWRP recovery mod for nitrogen which I have started about 2 years ago for hydrogen/helium. For more details visit https://forum.xda-developers.com/mi-max/development/recovery-twrp-3-0-2-2-hydrogen-helium-t3512981...
This is and will be work in progress with fixes and reasonable features to be added.
Download:
(02-01-2019)twrp_v323-4_nitrogen_nijel8-MOD.img
To install:
- USB connect device to PC
- reboot to fastboot
- open Command prompt/Terminal in the folder with the recovery image and run these commands line by line:
Code:
fastboot flash recovery (XX-XX-XXXX)twrp_v323-X_nitrogen_nijel8-MOD.img
fastboot boot (XX-XX-XXXX)twrp_v323-X_nitrogen_nijel8-MOD.img
or just flash the image with TWRP selecting recovery partition
- reboot from the fresh recovery - it'll take few seconds... let it do its magic to survive MIUI stock recovery replace at system boot. This will happen whenever you install any new ROM.
Done... This TWRP will not go anywhere, /system is untouched so you can get MIUI OTAs, no need to root if you don't want to, no need to flash anything else, MIUI boots just fine having no idea about the recovery, everybody's happy...
NOTES:
ROM install:
- skip wiping Data even if switching different ROMs. Do dirty install, see how it runs, if no problems, great... you saved yourself from doing the initial
setup. If having issues then wipe Data and see how it goes...
- You do not need to wipe/format/factory reset anything before install(see above), especially System and Vendor.
- Do not install any patches like lazyflasher, sound or whatever mods, root-on-system etc that are altering System or Vendor partitions on stock MIUI without installing Magisk first or system will not boot!!!
MIUI OTA Install:
- Let MIUI download update and press "Reboot" when prompted
- Device will reboot to TWRP and start installing it.
- If device reboots to system automatically - all good, update successful
- If device does not reboot you should see some error in red
- Just flash the zip package in Internal storage -> downloaded_rom folder and reboot to system
- Done - you just got your OTA
Decryption:
If MIUI asks for decription password after reboot from TWRP don't panic!
You will most likely never see this but as anything in this live sh*t happens. I for example have seen this only once in hundreds of TWRP and MIUI flashings and reboots to system and it happen after reboot from MIUI OTA testing. Did I mentioned I never do clean installs? Why bother wiping if no post-install issues, right...
Anyway... here is how to get back to normal without loosing any data:
- Reboot back to recovery by pressing and holding POWER + VOLUME UP buttons
- Run Data backup in TWRP
- USB connect device to computer and copy all personal data you don't wanna loose from Internal storage to computer
- DO NOT FORGET TO COPY THE DATA BACKUP YOU JUST MADE FROM TWRP/BACKUPS/XXXXXX TO COMPUTER TOO!!!
- Click Wipe -> Format data -> type yes -> [ENTER]
- Reboot to MIUI and let it encrypt the device. You will see Setup new device wizard when its done
- Reboot back to recovery by pressing and holding POWER + VOLUME UP buttons
- Copy back all your personal data including the recent Data backup from computer to Internal storage -> TWRP/BACKUPS/XXXXXX
- Reboot recovery so TWRP can detect the Data backup you copied
- Restore Data backup and reboot to MIUI
- Done - MIUI should boot without complaining and all your data is intact... even your old lockscreen password and fingerprints should work
Backup/restore:
- normal backup includes Data only, you can always flash what you are running currently to restore boot, system and vendor
- if you have modified boot,system or vendor post install you can back them up to keep your changes
- You do not need to wipe/format/factory reset anything before restore... restore does that for you
Some observations during my extended decryption testing with China and Global MIUIs 8.1 and 9.0, EU MIUIs, MIUIPro, etc:
- Downgrading to ROM with lower security patch level brakes encryption in Android but not in TWRP so just boot back to recovery, backup your data to safe location, format data, restore data back and you are good to go...
- Some times switching back and forth passwords types(pin, pattern etc...) brakes encryption and you loose your data, no way back!!! This is ROM fault and not TWRP. Crypto footer just gets corrupted from Android... I have taken good measures for this not to happen in my TWRP so don't blame recovery if that happens to you...
Changelog:
[02-01-2019
- hide navbar during running operarions
- more userdata decryption reliability improvements
- Mi bunny is terrified loosing recovery control
- sync with latest Omnirom android-9.0 sources
[01-28-2019
- fix decryption with good user password on next retry if wrong password was entered before that
- improve TWRP persist
- sync with latest Omnirom android-9.0 sources
[01-09-2019
- fix system boot after restoring regular file-for-file backup on ext4 file systems(System and Vendor) - now any backup type works for any partition of any ROM
- sync with latest Omnirom android-9.0 sources
[01-07-2019
- fix installing incremental OTA patching boot - this will start working properly after your first full ROM install with new recovery(boot.img flash)
- fix loading settings from /persist if decryption fails
- made sure we always keep current settings copy on /persist
- remove excessive save settings calls
- some minor improvements
- sync with latest Omnirom android-9.0 sources
[01-05-2019
- fix incremental OTA update automatic install
- sync with latest Omnirom android-9.0 sources
[01-04-2019
- new much smaller Pie kernel built from source with LineageOS 16.0
- much smaller recovery image(see above)
- sync with latest Omnirom android-9.0 sources
[12-29-2018
- improved decrypt routine
- some minor fixes and improvements
- sync with latest Omnirom android-9.0 sources
12-28-2018
- much improved and reliable decryption routine for preventing crypto footer corruption and loosing all your data - this update is highly recomended
- fix Android 9.0 userdata decryption with custom user set password, pin or pattern
- more reliable format data routine for crypto footer support
- disable useless and sometime buggy reboot check for system size(No OS installed msg)
- sync with latest Omnirom android-9.0 sources
12-27-2018
- migrate to Android-9.0 for android tree and TWRP sources
- switch to MIUI Pie prebuilt kernel
- speed up userdata decryption
- fix userdata decryption for Android-9.0 with default password only. At this time userdata decryption wit user set password is not supported! Working on it...
- sync with latest Omnirom android-9.0 sources
11-25-2018
- fix survival routine hang/bootloop after openrecoveryscript execution(OTA)
- improved decryption handling
11-23-2018
- fix userdata decryption - no more inaccessible userdata in TWRP
- fix vendor missing from partitions to restore list in some cases
- fix TWRP bootloop trying to apply survive magic in some cases
- finaly fix crypto footer for F2FS partition formating(tested and working!!! - you can format userdata in TWRP without any system boot issues now)
- skip survive magic for good ROMs to speed up reboot
- translatable and more user friendly survive system boot screen - If you want to help translate and PM me these strings:"
Code:
<!-- Survive system boot strings -->
<string name="survive_line1">Checking if TWRP will survive system boot!</string>
<string name="survive_line2">Please, wait...</string>
- sync with latest Omnirom android-8.1 TWRP sources
11-12-2018
- fix TWRP system boot survive - no need to flash anything to prevent stock recovery reflash at MIUI boot
- fix crypto footer for F2FS partition format - need no more fastboot format userdata for system boot with forced encription enabled(needs testing)
- fix error when creating ext2, ext3, or ext4 filesystem in some cases(needs testing)
- some minor fixes and optimizations
- kernel compiled from source at build time
- build with latest Lineage OS 15.1 sources
- sync with latest Omnirom android-8.1 TWRP sources
Github sources:
NITROGEN TWRP device tree
TWRP Mod repo
Kernel source
Thank you:
TeamWin for the initial device tree!
Omnirom/TeamWin for the TWRP source code!
@topjohnwu for the magiskboot source code!

Yes, You finally stepped in.

you save my life thankyou sir. unlocked bootloader today as i waited for 720 hrs. as i known i can skip by 9001 mode i just wait the official unlock to play safe. missed you so much since max1 thankyou sir

Just noticed on 4PDA forum there is a bug when you try restore vendor is missing from the list of available partitions at first... Well, it's not a bug... It's something I had to add for hydrogen...
Yeah, I know exactly what you guys are talking about... Back in the days when I was trying to bring treble to Max1 I added some code to detect in the fly if vendor partition is available on the running device so I can hide it in UI if ROM was Nougat or show it if was treblelized. I forgot about it and now it causes inconvenience on Max3. Will get it fixed in the next release.
Thaks for the reminder 4PDA guys...

nijel8 said:
Just noticed on 4PDA forum there is a bug when you try restore vendor is missing from the list of available partitions at first... Well, it's not a bug... It's something I had to add for hydrogen...
Yeah, I know exactly what you guys are talking about... Back in the days when I was trying to bring treble to Max1 I added some code to detect in the fly if vendor partition is available on the running device so I can hide it in UI if ROM was Nougat or show it if was treblelized. I forgot about it and now it causes inconvenience on Max3. Will get it fixed in the next release.
Thaks for the reminder 4PDA guys...
Click to expand...
Click to collapse
I hope that you are able to create an un-official build of LineageOS for Mi Max 3
I thank you for your time for creating this un-offical twrp build as its faster than the official one
have a great week!

Going to keep an eye on this.
300 hours left for my Mi Max 3, will flash this when I unlock.
What's different between this and official TWRP may I ask?

omer919 said:
I hope that you are able to create an un-official build of LineageOS for Mi Max 3
I thank you for your time for creating this un-offical twrp build as its faster than the official one
have a great week!
Click to expand...
Click to collapse
Don't know if it's faster but should be more bugs free...
AsadP2013 said:
...
What's different between this and official TWRP may I ask?
Click to expand...
Click to collapse
Read first post and changelog, then click the link for more info and read the looong changelog there as well.
But if I have to summarize the dev is listening and every bug terminated right away...
Oh... and the most important thing... Dev has the device and runs on it only what he builds himself... You get what the dev gets and he hates it when something's not working as intended.
Hope this helps...

nijel8 said:
Don't know if it's faster but should be more bugs free...
Read first post and changelog, then click the link for more info and read the looong changelog there as well.
But if I have to summarize the dev is listening and every bug terminated right away...
Click to expand...
Click to collapse
Thanks, no I have had a look but in short, what would you say?
Do you reckon that it has more features and is capable of doing slightly more?
Basically, should I use this TWRP over official as I'm a modder/tweaker?
Or should I flash it for the sake of it providing more than official?

Ohh Sir @nijel8 I've tried, but incremental OTA updates does not installable with this rec.
(Or I am making a mistake.)

JulianJenner said:
Ohh Sir @nijel8 I've tried, but incremental OTA updates does not installable with this rec.
(Or I am making a mistake.)
Click to expand...
Click to collapse
More specifics, please, recovery.log. What not installable means?
The only reason OTA would not install is if the updater-script checks boot partition checksum. Can you post its content?
I would test it myself but I am away from home right now...

Thx. I am back to miui with chinese PC suite (full clean install)
I will try again. When I have time again.
I've found on baidu a new TWRP a lot of settings and partition backup
http://www.mediafire.com/file/04xqp...-1030-XIAOMI_MAX3-CN-wzsx150-fastboot.7z/file
{
"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"
}
小米MIX标准版4GB128GB银色MIUI10中国开发者8.11.13

JulianJenner said:
Thx. I am back to miui with chinese PC suite (full clean install)
I will try again. When I have time again.
I've found on baidu a new TWRP a lot of settings and partition backup
http://www.mediafire.com/file/04xqp...-1030-XIAOMI_MAX3-CN-wzsx150-fastboot.7z/file
View attachment 4642012
View attachment 4642013
View attachment 4642014
View attachment 4642015
小米MIX标准版4GB128GB银色MIUI10中国开发者8.11.13
Click to expand...
Click to collapse
One thing I should've mentioned... Since recovery hardware decryption is not fixed yet after OTA update.zip is downloaded you have to move it to nonencrypted accessable location like external SD Card or OTG reboot to recovery and flash it manually.
Another thing I should mention is although decryption with default passwords is not working decryption with user password should work. Don't ask me how to switch from default to user password encryption... I am not familiar with MIUI.

I just testing. No problem.
小米MIX标准版4GB128GB银色MIUI10中国开发者8.11.13

nijel8 said:
One thing I should've mentioned... Since recovery hardware decryption is not fixed yet after OTA update.zip is downloaded you have to move it to nonencrypted accessable location like external SD Card or OTG reboot to recovery and flash it manually.
Another thing I should mention is although decryption with default passwords is not working decryption with user password should work. Don't ask me how to switch from default to user password encryption... I am not familiar with MIUI.
Click to expand...
Click to collapse
I think, there is not the encryption/decryption is the bigger problem.
Max3 MIUI ROMs contains a scrip, that it rewrite MiRecovery, but this action occurs across boot. Earlier rewriting supervened after system installing/flashing. So far, we could have avoided this with Lazyflasher or something. At the moment, we install TWRP versions in vain, because after successfully TWRP install, MIUI system immediately restore MiRecovery at rebooting.

In Mi Max 1 I solved the problem of recovering stock recovery by deleting the file "Recovery from boot.p" in the system directory. You must do this before the first start of the system.

Guys, you have system verify in the kernel on Oreo so LazyFlasher doesn't work on Oreo and deleting files in system causes bootloop. The new approach for disabling recovery replace is to patch rc scripts in boot image. That's how this recovery does it.
Edit: BTW vendor is verified as well so modifying anything in that partition causes bootloop as well...

nijel8 said:
Guys, you have system verify in the kernel on Oreo so LazyFlasher doesn't work on Oreo and deleting files in system causes bootloop. The new approach for disabling recovery replace is to patch rc scripts in boot image. That's how this recovery does it.
Edit: BTW vendor is verified as well so modifying anything in that partition causes bootloop as well...
Click to expand...
Click to collapse
"nice" new security items...

Installed the recovery today. It went well. When I tried to boot to the system afterward it started running OpenRecoveryScript 'checking if TWRP will survive system boot!'. It has been over 2 hours. Is this normal? If Any way to stop it? Rebooting doesn't stop it.
EDIT: Figured it out. Didn't have writer permissions for /data. Had to reformat it. After that it went ok.

lowfat said:
Installed the recovery today. It went well. When I tried to boot to the system afterward it started running OpenRecoveryScript 'checking if TWRP will survive system boot!'. It has been over 2 hours. Is this normal? If Any way to stop it? Rebooting doesn't stop it.
EDIT: Figured it out. Didn't have writer permissions for /data. Had to reformat it. After that it went ok.
Click to expand...
Click to collapse
Doesn't sound right. /data should not affect that. Post any recovery related log you find in /cache, please...

Thanks for the recovery mod. I think that a translation into Russian will eventually be added. I am also grateful to nijel8 for his work!

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

-- 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!

[ROM][angler][10.0.0_r40] AOSP 10.0 [2020/07/05]

Install Instructions
Grab our recovery from the OP Post section and install it.
Through TWRP Recovery:
Install Zip > Install Image > Choose ‘recovery.img‘ > Select partition ‘Recovery’ > Swipe to confirm flash
Through Fastboot:
Code:
fastboot flash recovery recovery.img
Install the ROM and then wipe your internal data partition.
Through TWRP Recovery:
Wipe > Format data
Through Fastboot:
Code:
fastboot -w
Reboot into system and wait until the process finishes, it could take a little bit. After the installation is done, I suggest waiting before using the phone because it usually goes into thermal throttling after installing a ROM.

Changelog
AOSP-10.0 2020705
July Security Patch

Omg .. Pixelboot is amazong ???

Both build folders seems empty right now...

daigoro64 said:
Both build folders seems empty right now...
Click to expand...
Click to collapse
Check again. They should be back.

PixelBoot said:
Check again. They should be back.
Click to expand...
Click to collapse
Google Drive is fine. Thanks!

Probably a noob question, but how do I know if I have the bootloader, vendor and radio installed? And if they're installed (which I don't know) and I flash the ones linked above, would it cause any issues to my phone?
New here btw, thank you very much!

Rodeze said:
Probably a noob question, but how do I know if I have the bootloader, vendor and radio installed? And if they're installed (which I don't know) and I flash the ones linked above, would it cause any issues to my phone?
New here btw, thank you very much!
Click to expand...
Click to collapse
It will not cause any issues

Rodeze said:
Probably a noob question, but how do I know if I have the bootloader, vendor and radio installed? And if they're installed (which I don't know) and I flash the ones linked above, would it cause any issues to my phone?
Click to expand...
Click to collapse
Bootloader and radio are installed for sure by default. You can check their versions starting the device to bootloader.
If there is a Vendor mismatch is show to you as soon as you enter the home.

if I am doing a clean install is it necessary to flash Gapps ?

nueloc said:
if I am doing a clean install is it necessary to flash Gapps ?
Click to expand...
Click to collapse
No. You can either flash or not flash GApps.

I just wanted to chime in and Say thank you @PixelBoot! Also does anyone have a recommended stock like Gaaps that replaces all default apps with their Google counterpart?

I hope there's anybody can help me. I wiped system & data & cache, then flashed the rom. As TWRP said - successfully. While trying to boot the system I saw the message that there is "no OS installed". I tried to boot it anyway and it worked. System booted normally, but it's looking very old fashioned. According to system information in the menu it is android 10 aosp. I realized there is no gapps so I wanted to install them. And here my problem starts - while trying to open TWRP from bootloader by choosing 'Recovery mode' it every time boots the system instead TWRP.

1. It seems the official TWRP 3.1.1.0 does not work, and one must use the "FBE" version. Otherwise it will not boot and the recovery cannot decrypt the storage.
2. After each startup, recovery becomes inaccessible. Trying to boot to recovery just boots to the system instead. I had to re-flash the recovery each time.
3. Background music slightly stutters when other sound clip starts to play (for example, a button sound effect in an app) or the screen rotates.
4. Some useful LineageOS features are not present, such as: double-tap to wake, ADB over Wi-Fi, volume button reorient when rotating, scramble number positions for lock screen PIN input, power button long-press for torch.
5. Auto-brightness seems often suddenly to make the screen too dim.
6. Fingerprint sensor is a lot less sensitive than the stock or LineageOS.

yourrealking said:
1. It seems the official TWRP 3.1.1.0 does not work, and one must use the "FBE" version. Otherwise it will not boot and the recovery cannot decrypt the storage.
2. After each startup, recovery becomes inaccessible. Trying to boot to recovery just boots to the system instead. I had to re-flash the recovery each time.
3. Background music slightly stutters when other sound clip starts to play (for example, a button sound effect in an app) or the screen rotates.
4. Some useful LineageOS features are not present, such as: double-tap to wake, ADB over Wi-Fi, volume button reorient when rotating, scramble number positions for lock screen PIN input, power button long-press for torch.
5. Auto-brightness seems often suddenly to make the screen too dim.
6. Fingerprint sensor is a lot less sensitive than the stock or LineageOS.
Click to expand...
Click to collapse
Here is my takes on these "issues":
1. I have linked the recovery which works in the OP thread both for 4 core and 8 core users. Don't see the reason of flashing the recovery from the TWRP website.
2. Yes. I have noticed this. It is an inconvenient bug, but since recovery isn't used too much, we'll have to deal with this minor issue.
3. Logcat would be appreciated if sent while listening to the music.
4. I'm not sure if you are aware that the reason behind this ROM is for the simplicity and stock AOSP. This is not about being feature packed, but is supposed to simulate a newer version for the Nexus 6P's previous firmwares.
5. This setting is set to the default one of AOSP. No modifications were set unlike that of LineageOS.
6. This should be more or less the same as the experience found on LineageOS as the device tree is very similar.

1. I just happened to already have the official 3.1.1.0 installed before installing this ROM. I read the description and thought that since my version was already 3.1.1.0, I did not have to install a new TWRP. This caused me a lot of problems (wasted time waiting it for to boot, lost all files on the Data, because I had to re-flash the stock ROM). I wrote this to help other users so that the may not experience the same thing I had.
3. I have tried Google Music and another third-party music player and the symptom was the same, so I thought it was a known issue. Anyway, this is not really a big issue, just a small stuttering, and I have disabled screen rotation. I just wrote that to help others to know about it before they decide to move to this ROM.
4. Yeah, I know. I did not write that to complain, or force you to implement those, but as other things, I wrote that to help others to decide before installing. Because changing ROM is a big and time-consuming thing, so it is good to know what it can do and what it cannot do before doing it.
5. I see. I could find a workaround, like creating an app that can modify the dimming degree, or disable auto-brightness.
6. This is strange. I can definitely feel big difference. I had been using LineageOS, and most of the time, I used the fingerprint sensor to turn on the phone instead of pressing the power button. Well, this is not a deal-breaker. I just have to put my finger one or two more times or wait one more second till it gets unlocked.
Thanks for the ROM. So far, for me, the feature I can get from Android 10 outweighs the downsides above. I had been stuck at Android 8 for over two years, and it was boring.

Is it normal that my google bar looks like this?
link: https://www.fotosik.pl/zdjecie/7bfdf769a6834334- sorry for the link, but I've got some issues while uploading photo here

zzitam said:
Is it normal that my google bar looks like this?
link: https://www.fotosik.pl/zdjecie/7bfdf769a6834334- sorry for the link, but I've got some issues while uploading photo here
Click to expand...
Click to collapse
Yup, completely normal.

Can’t modify the system in any way e.g copying Pixel Launcher to system
Is this because of data encryption?

[RECOVERY][UNOFFICIAL] ORANGEFOX RECOVERY PROJECT for OnePlus Nord (avicii) - R11.1

Hey folks OrangeFox Recovery is finally here for OnePlus Nord (avicii)...
THIS RECOVERY WILL SUPPORT STOCK ROMS, FBEv1 CUSTOM ROMS, FBEv2 CUSTOM ROMS.
DISCLAMER
Your warranty is now void.
I am not responsible for any damage that is made due to this action.
{
"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 the device is encrypted, then you must format the data partition (NOTE: format - not just wipe). If the device is not encrypted, then you can just wipe the data partition (ie, no need to format)"
-source wiki.orangefox.tech
KNOWN ISSUE FOR FBEv1 Recovey : DATA BACKUP AND RESTORE NOT WORKING
DATA DECRYPTION NOT WORKING FOR SOME ROMS
KNOWN BUG FOR 00S12 Recovery (0.1%) : DATA BACKUP AND RESTORE WORKS, BUT HAVEN'T FOUND A PERFECT WAY TO RESTORE AND MAKE THE PHONE FULLY WORKING. IF YOU ARE FREE PLEASE CONSIDER TO FIND A WAY TO PERFECTLY BACKUP AND RESTORE OOS12 ROM DATA PARTITION
Note: Only boot and work with OOS12, never try to flash with FBEv1 or FBEv2 roms, if you do so, your device will face a softbrick. Similarly donot try FBEv1 or FBEv2 recoveries with OOS12. This is due to the mismatch in firmwares of OOS12 and other roms
If flashing rom from OOS12 variant, after installing custom rom, flash FBEv1, FBEv2 recovery accordingly. And vice versa
To flash OOS12 OTA (Only available from R11.1_3 onwards)
I added 2 scripts inside the recovery.
Before flashing OOS12 OTA
Go to terminal
Type and press enter
sh /system/bin/pre_oos_flash.sh
You will see an error "kPostinstallError" : just ignore it.
After flashing OOS12 OTA
Go to terminal
Type and press enter
sh /system/bin/post_oos_flash.sh
Then switch slot to updated slot
Downloads :
For FBEv1 Custom Roms :
OrangeFox Recovery R11.1_2 (Image File)
OrangeFox Recovery R11.1_2 (Flashable Zip Installer)
For OOS12 Rom:
OrangeFox Recovery R11.1_3 (Image File)
OrangeFox Recovery R11.1_3 (Flashable Zip Installer)
For FBEv2 Custom Roms :
OrangeFox Recovery R11.1_2 (Image File)
OrangeFox Recovery R11.1_2 (Flashable Zip Installer)
Guide to flash recovery :
• Reboot to FASTBOOT
• Connect your phone via USB to PC
• Open Command Prompt (You must install ADB and fastboot platform files) and type
• Only to boot the recovery
fastboot devices
fastboot boot <path to recovery image file>
• To flash recovery
fastboot devices
fastboot flash recovery <path to recovery image file>
Special Thanks to
OrangeFox Recovery Project
@DarthJabba9
@Wishmasterflo
@lordfinix
For People residing inside India
UPI :- [email protected]
For People residing outside India
Paypal
CHANGELOG (16/11/2022) - R11.1_3_OOS12
1) Initial Build
2) Support OOS12
3) 99.9% Features work
CHANGELOG (16/11/2022) - R11.1_2_FBEv1
1) Initial Build
2) Toggle Flashlight FIxed
3) Screen Ratio Fixed
4) Notch Positioning Fixed
5) Added CPU Temperature Monitor
6) Slot Switching Fixed
CHANGELOG (16/11/2022) - R11.1_2_FBEv2
1) Fixed Data Partition Backup & Restore
2) Fixed Data Partition Wipe
CHANGELOG (13/11/2022) - R11.1_1_FBEv2
1) Initial Build
2) Data Decryption Fixed
3) Toggle Flashlight FIxed
4) Screen Ratio Fixed
5) Notch Positioning Fixed
6) Added CPU Temperature Monitor
7) Slot Switching Fixed

Can you do one for a12 coloros?

skia16 said:
Can you do one for a12 coloros?
Click to expand...
Click to collapse
Ys. But require few edits. I need to build another separate version for Oxygen OS, Color OS and some other custom roms since they use FBEv1 file encryption.

Works super good! one of GOAT recoveries

@Sreeshankar K
Thanks for this great recovery! It´s working like a charm on my device.
One question: is it able to decrypt data/internal storage? I have a pattern, but there is no option in decryption to use this or am I wrong? I´m on Lineage OS 19.1.

gllark said:
@Sreeshankar K
Thanks for this great recovery! It´s working like a charm on my device.
One question: is it able to decrypt data/internal storage? I have a pattern, but there is no option in decryption to use this or am I wrong? I´m on Lineage OS 19.1.
Click to expand...
Click to collapse
Probably Lineage OS 19.1 is FBEv1 ROM. This recovery only support FBEv2 ROMs. I had mentioned it in the post. Currently no support for FBEv1 ROMs. If u want fully functioning recovery please go to the telegram group mentioned in the XDA post.
And also thanks for ur positive comment

Wasn't able to decrypt the data partition with LOS 18.1 and the FBEv1 version.
And now after booting, Bluetooth is no more starting/working.
It's doesn't turn on, it goes back to off every time.
Had this problem also in the past with the OFRP from the other thread.
Edit: was able to fix the Bluetooth problem with: restorecon -R /data

Doc Sniper said:
Wasn't able to decrypt the data partition with LOS 18.1 and the FBEv1 version.
And now after booting, Bluetooth is no more starting/working.
It's doesn't turn on, it goes back to off every time.
Had this problem also in the past with the OFRP from the other thread.
Edit: was able to fix the Bluetooth problem with: restorecon -R /data
Click to expand...
Click to collapse
Lemme check with lineage os 19.1. both 18.1 and 19.1 are FBEv1

Doc Sniper said:
Wasn't able to decrypt the data partition with LOS 18.1 and the FBEv1 version.
And now after booting, Bluetooth is no more starting/working.
It's doesn't turn on, it goes back to off every time.
Had this problem also in the past with the OFRP from the other thread.
Edit: was able to fix the Bluetooth problem with: restorecon -R /data
Click to expand...
Click to collapse
I checked it on superior os which is FBEv1. And data partition was successfully decrypted

Sreeshankar K said:
I checked it on superior os which is FBEv1. And data partition was successfully decrypted
Click to expand...
Click to collapse
Strange, because here the decryption doesn't work.
The partition was once encrypted by LOS 18.1, hence probably FBEv1.
Also tried the FBEv2 recovery, but as expected no decryption dialog appears.
Thanks for testing and also creating the recovery.
Do we have any other options to test or fix this?

Doc Sniper said:
Strange, because here the decryption doesn't work.
The partition was once encrypted by LOS 18.1, hence probably FBEv1.
Also tried the FBEv2 recovery, but as expected no decryption dialog appears.
Thanks for testing and also creating the recovery.
Do we have any other options to test or fix this?
Click to expand...
Click to collapse
Ys not working. It was the first build of FBEv1 recovery released yesterday. I will check it.. Thanks for testing it. I go through the logs found that FBE decrypt setup is working fine but it cannot decrypt metadata partition.

Sreeshankar K said:
Ys not working. It was the first build of FBEv1 recovery released yesterday. I will check it.. Thanks for testing it. I go through the logs found that FBE decrypt setup is working fine but it cannot decrypt metadata partition.
Click to expand...
Click to collapse
This could possibly cause the Bluetooth problem, because the SELinux permissions don't seem to match after trying to decrypt data.
In any case, it's great that you're taking the time to look for the problem and fix it. Thanks.

Doc Sniper said:
This could possibly cause the Bluetooth problem, because the SELinux permissions don't seem to match after trying to decrypt data.
In any case, it's great that you're taking the time to look for the problem and fix it. Thanks.
Click to expand...
Click to collapse
Recovery settings and rom settings have no connections. Recovery only look for the fstab of rom to do the operations like wipe, install, backup and restore etc. Idk why that prob is appeared

Sreeshankar K said:
Ys not working. It was the first build of FBEv1 recovery released yesterday. I will check it.. Thanks for testing it. I go through the logs found that FBE decrypt setup is working fine but it cannot decrypt metadata partition.
Click to expand...
Click to collapse
Any news ?

Tried booting then flashing the R11.1_2_FBEv1 build using the fastboot manual flash, with OOS F17 EU (the latest for my device at the time of writing), it doesn't boot and just show the "boot/recovery destroyed" screen, any idea why?
Phone was also not booting after the flash, stuck on the "destroyed" screen, and I had to reflash the boot.img (no, I did not flash over boot, I double checked that I did specify recovery_a/_b when flashing)

WORMSTweaker said:
Tried booting then flashing the R11.1_2_FBEv1 build using the fastboot manual flash, with OOS F17 EU (the latest for my device at the time of writing), it doesn't boot and just show the "boot/recovery destroyed" screen, any idea why?
Phone was also not booting after the flash, stuck on the "destroyed" screen, and I had to reflash the boot.img (no, I did not flash over boot, I double checked that I did specify recovery_a/_b when flashing)
Click to expand...
Click to collapse
It is bcoz, OOS12 firmware doesn't support other custom kernels, firmwares etc

Sreeshankar K said:
It is bcoz, OOS12 firmware doesn't support other custom kernels, firmwares etc
Click to expand...
Click to collapse
Isn't "For Stock Roms (Oxygen OS and Color OS) & FBEv1 Custom Roms" a bit misleading then? Since it mention OOS and it being "For Stock Roms"

Tried out the new OOS12 option, works like a charm! Both the img and the zip!
I haven't tested everything but decryption, usb mounting, usb_otg, backups, sideloading and a lot more works perfectly!
I did encounter a bug tho, after trying out a few features, my filesystem appeared encrypted, with gibberish names for the folders and files
Fortunately it didn't affect anything and a reboot fixed everything
Finally a proper working recovery for the Nord!

WORMSTweaker said:
Tried out the new OOS12 option, works like a charm! Both the img and the zip!
I haven't tested everything but decryption, usb mounting, usb_otg, backups, sideloading and a lot more works perfectly!
I did encounter a bug tho, after trying out a few features, my filesystem appeared encrypted, with gibberish names for the folders and files
Fortunately it didn't affect anything and a reboot fixed everything
Finally a proper working recovery for the Nord!
Click to expand...
Click to collapse
Data backup and restore is buggy, means not saying that it is not working, haven't found a correct way to restore the backup of data partition, so if you have time please found a correct way to restore data partition, and post it here. Data decryption and all other features work.
[RECOVERY] [13] [UNOFFICIAL] TeamWin Recovery Project (8T / 9R) (2022-07-27)
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
Like this we also need correct way to backup and restore data partition, so, if your are free do it.

WORMSTweaker said:
Tried out the new OOS12 option, works like a charm! Both the img and the zip!
I haven't tested everything but decryption, usb mounting, usb_otg, backups, sideloading and a lot more works perfectly!
I did encounter a bug tho, after trying out a few features, my filesystem appeared encrypted, with gibberish names for the folders and files
Fortunately it didn't affect anything and a reboot fixed everything
Finally a proper working recovery for the Nord!
Click to expand...
Click to collapse
"I did encounter a bug tho, after trying out a few features, my filesystem appeared encrypted, with gibberish names for the folders and files
Fortunately it didn't affect anything and a reboot fixed everything "
This is bcoz your data partition is not decrypted. Decrypt it using your rom password then everything will be normal. That's not a bug... Bug is in the restoration of backuped data. Actually not a bug. Didn't found a fully working way.
Need to find a perfect way to restore. OOS12 data restore is bit painful.
Take a look on data backup and restore
if you are free
Thank you

Develop Bugs

welcome