Redmi Note 8 Ginkgo Q build question? - Redmi Note 8 Questions & Answers

Redmi Note 8 Ginkgo Q build question? - Redmi Note 8 Questions & Answers

When I try to build Redmi Note 8 Q, the build process finished successfully, but I got into black screen after boot splash, where boot animation should appear. After a very long time (~10 mins), phone reboot into recovery.
I have tried LineageOS with trinket-devs trees, and Resurrection Remix with trinket-devs / Arrow OS/ DqrKn3Zz (rr-Official) trees, and I get the same results.
The steps I used to build (using Ubuntu 20.04):
1. repo init
2. add local_manifests includes device/vendor/kernel/proto-clang/miuicamera
3. repo sync
4. RR-ify device tree (only for build resurrection remix rom)
5. . build/envsetup.sh && brunch ginkgo | tee log.txt
Could anyone point out where things go wrong, do I get a wrong building environments, or miss some steps?

Related

Rootbox ROM for HOV?

Hello,
just stumbled upon this nifty looking ROM called Rootbox;
http://www.modaco.com/topic/360867-romskate-rootbox-cmaokppa-mix-android-422-18022013/
Currently running on a ZTE Skate (Armv6 device, 800mhz processor with no official support above Gingerbread) albeit it's not running perfect but it's running. Any chance of this ROM making it's way to our device once the 4.2 builds start to get to a more stable status. I'd attempt it myself but I'm not a developer and my only experience is porting ROMs!
But yeah, check out that topic, it looks really nice, it's similar to PAC (In terms of hybrid between different ROMs)
Oh and here is the (What seems to be) original thread for the Galaxy S3;
http://forum.xda-developers.com/showthread.php?t=1806401
Discuss!
EDIT--
If anybody wants to give this a bash then here are some instructions from the S3 thread on building Rootbox from source;
How to Build RootBox from Source
Getting started
I will assume that you have some kind of knowledge with Linux and how to use a terminal. I will also assume that you have already setup all the android building requirements. First, you must create your working folder and initialize a repository with RootBox sources. The following steps will guide you in creating this working folder where you will be able to build RootBox.
You should now open a terminal (By default you should be in your home folder: /home/yourusername/)
Step 1: Let's create a folder in your home directory named RootBox. This will be referred as your working folder.
Code:
~$ mkdir RootBox
Step 2: Let's change our directory to the new RootBox folder we just created.
Code:
~$ cd RootBox
Step 3: Now that we are in our working folder (RootBox), we will initialize our RootBox repository by entering the following command:
Code:
~$ repo init -u git://github.com/Root-Box/platform_manifest.git -b jb-mr1
Step 4: It's now time to sync RootBox sources which could vary from a few minutes to a few hours depending on your internet connection.
Code:
~$ repo sync
Building Vanilla RootBox
Now that you have synced the sources, you're ready to build RootBox.
You can run the following build script:
Code:
~$ . build_rootbox.sh -device- -sync- -thread- -clean-
Device: Choose between the following supported devices: i9100, i9100g, i9300, d2att, d2tmo, d2vzw, mako and grouper.
Sync: Will sync latest RootBox sources before building
Threads: Allows to choose a number of threads for syncing and building operation.
Clean: Will remove the entire out folder and start a clean build. (Use this at your discretion)
Examples:
1) Sync sources and Build RootBox for GT-I9100 with 12 threads
Code:
~$ . build_rootbox.sh i9100 sync 12
2) Don't sync sources, clean out folder and build RootBox for GT-I9300 with 6 threads
Code:
~$ . build_rootbox.sh i9300 nosync 6 clean
3) Don't sync sources, clean out folder and build RootBox for SGH-I747 with 4 threads
Code:
~$ . build_rootbox.sh d2att nosync 4 clean
4) Sync sources, clean out folder and build RootBox for Nexus 4 with 5 threads
Code:
~$ . build_rootbox.sh mako sync 5 clean
This script will make a signed flashable zip file located in out/target/product/-device-/RootBox-JB-(Device)-Nightly-(Date).zip
Click to expand...
Click to collapse

[GUIDE] How to build ROMs for LB from source

Hi,
since many people asked me how I build my ROMs for locked bootloaders, I have decided to write a short guide.
Getting started
As always, you need to set up a build environment. Since I don’t want to elaborate on this, I suggest you to follow the building instructions on the CyanogenMod wiki. You can also use the AOKP website as a reference.
Initializing the repos
To start, you may want to initialize the repos that you will use later on. Just open a terminal and issue the following command:
Code:
repo init -u git://github.com/aosp-lb-nozomi/manifest.git -b <ROM>
Where <ROM> is the ROM you want to build. You have to choice between aokp, pac, slimbean and mokee.
So, let's say you want to build AOKP - this would be the command you would have to issue:
Code:
repo init -u git://github.com/aosp-lb-nozomi/manifest.git -b aokp
Syncing the code
Now that this is done, you can start syncing (this may take some time):
Code:
repo sync -jX
Replace the X with your core count (eventually +1 or -1). (e.g. If you have a dualcore processor, it can be -j2 or -j3)
Building
Start with:
Code:
. build/envsetup.sh
Now you should be good to go. Lunchtime!
Code:
lunch <ROM>_<device>-userdebug
(e.g. lunch aokp_nozomi-userdebug OR lunch slim_aoba-userdebug)
Finally, you are ready to build.
Code:
make -jX bacon
Patching the ROM to work with LB
If everything went right, you should find an AOKP build in your out folder. But this build is unpatched, so it can be flashed on UB devices only. To patch it, go to your root directory (type "cd"), clone my repo and navigate to it:
Code:
git clone [email protected]:aosp-lb-nozomi/rom_builder.git -b [B]<ROM>[/B] patcher;cd patcher
Again, you have to replace <ROM> by the ROM you want to build. Possible ROMs: aokp, pac, slimbean and mk.
NOTE: If you build for the Sony Xperia Ion (aoba), you have to add that. (e.g. git clone [email protected]:aosp-lb-nozomi/rom_builder.git -b aokp-aoba patcher;cd patcher)
Finally, execute the script (to patch the ROM):
Code:
sh makezip
That’s it! Find your build in the folder “patcher” and flash it.

[WIP] [8.1][UNOFFICIAL] PixelExperience 8.1 for hammerhead

IMPORTANT: Read this before installing
A bug in the installer causes installation to fail. Please create the folder /tmp/install/bin in TWRP before flashing!
GApps is NOT included in this build, and installing OpenGApps causes Google apps to crash. Try mindthegapps or another package, and let me know what works.
The device tree and kernel are from LineageOS sources. The device tree for @clamor's repartition can be found here. (If you're interested, I just modified BoardConfig.mk for the patch.)
Features (note, this is a WIP, so most of the Pixel stuff doesn't work):
Google Sans on the launcher
Version compatible with @Clamor's repartition
That's about it.
Downloads:
Downloads will be in my Android File Host folder, under PixelExperience and PixelExperience-clamor (for @Clamor's repartition), and maybe DevDB, if it actually works.
Please leave a review!
XDA:DevDB Information
PixelExperience 8.1 for hammerhead, ROM for the Google Nexus 5
Contributors
yagyaxt1068, jhenrique09 (the creator)
Source Code: https://github.com/PixelExperience
ROM OS Version: 8.x Oreo
Based On: AOSP
Version Information
Status: Testing
Created 2019-02-20
Last Updated 2019-02-19

Installed on my Nexus 5 -
* As already stated, we have to create a folder \tmp\install\bin (every time) before installing.
* installation and booting went smooth without boot loop. (I kinda like the boot animation)
* I found it strange that there is no keyboard come along with this rom, I had to get .apk file and install it manually.
* Through mobile data is turned on, I'm not getting data (for this reason I have to switch back to my old rom)
* Apps started crashing unless permitted manually from settings.
* The below given Gaps worked find for me
http://downloads.codefi.re/jdcteam/javelinanddart/gapps
MindTheGapps-8.1.0-arm-20180808_153837.zip
I wish I could use it for longer.

I have the twrp 3.3.1-1 UA with the memory increase to 1.5gb. I created the tmp / install / bin folder but it always keeps giving me error 7 "no such file or directory".
Do I have to go back to the 1gb distribution? to change twrp? also i have unlimited space using google photos?

[ROM][13.0][Daredevil] LineageOS 20.0 [UNOFFICIAL]

Note - please take your data backup and do clean flash as per the instructions linked in the main thread. On top of it, my builds will boot on any stock firmware as base. So there is no special recommendation towards which stock rom you need to be on.
Changelog - Sun Jan 22 19:01:23 UTC 2023
============================
• Initial Android 13 build
• Based on android-13.0.0_r20
• Improved system stability
• User interface enhancements
• Google security patch 2023-01
• Selinux enforced
• Vendor built from Source
• Imported CTS profile patches
• Safety net pass by default & no need zygisk
• Updated build fingerprint from Pixel 7 Pro (cheetah)
Reminder - for reporting bugs please mention the issue and attach the logcat.
Thank you!

Awesome..!

Any chance it would run on Nokia 8.1 after unlocking/rooting with Hikari files ?
I'm mean ... someday / when updates are over .

Changelog Sat Apr 3 08:41:31 UTC 2020
===================================
1. Initial stable build
2. March security patch
3. Comes with stock kernel
4. Linux version 4.4.194
5. Vendor image from 2250
6. System blobs from 2250
7. Ota support available
Note- Installation process changed so please go ahead and follow the instructions as I mentioned in installation section

I tested now and I found Google Services - are GApps included? I installed lineageos in this build to AVOID this. Or did I make something wrong?

overclockA said:
I tested now and I found Google Services - are GApps included? I installed lineageos in this build to AVOID this. Or did I make something wrong?
Click to expand...
Click to collapse
Thanks, saved me some time. Defeats the entire purpose for me.

xe500linux said:
Thanks, saved me some time. Defeats the entire purpose for me.
Click to expand...
Click to collapse
I wrote to Raghu varma for the same question.
Technically it seems to not be that simple - if lineage 17.1 has been compiled without gapps and the build process was done by using private keys, flashing gapps would brick the device or the lineageos installation.
So Raghu varma compiled the version with gapps included to avoid this.
So I took his scripts from github and I built lineageos 17.1 on my own (with private keys and without gapps as I don't think about flashing them afterwards) - this worked fine.
Now I couldn't find his scripts for Daredevil on his github profile anymore - maybe they will come back for the 7.2 build process.

overclockA said:
I wrote to Raghu varma for the same question.
Technically it seems to not be that simple - if lineage 17.1 has been compiled without gapps and the build process was done by using private keys, flashing gapps would brick the device or the lineageos installation.
So Raghu varma compiled the version with gapps included to avoid this.
So I took his scripts from github and I built lineageos 17.1 on my own (with private keys and without gapps as I don't think about flashing them afterwards) - this worked fine.
Now I couldn't find his scripts for Daredevil on his github profile anymore - maybe they will come back for the 7.2 build process.
Click to expand...
Click to collapse
Ah I see. Any chance you still have a copy of your non-g build?

xe500linux said:
Ah I see. Any chance you still have a copy of your non-g build?
Click to expand...
Click to collapse
This should be OK. I'll upload a copy and send a link.
Be aware that the security patch level is dated on march 2020 and doesn't include the latest Google security patches from june.

overclockA said:
This should be OK. I'll upload a copy and send a link.
Be aware that the security patch level is dated on march 2020 and doesn't include the latest Google security patches from june.
Click to expand...
Click to collapse
Much appreciated!!

i posted already in the twrp thread of my problem "touch not working with twrp", that's still persisting.
so i got another idea. i used adb commands to control twrp. like you know, adb shell twrp sideload and then do the adb sideload commands for installing lineageos 17.1.
what did i do so far is:
*flash twrp 3.4.0
*boot up to twrp 3.4.0
*use adb shell twrp remountrw
*use adb to sideload lineageos 17.1 zipfile with commands (adb shell twrp sideload and then adb sideload lineageos.zip) - but the progress bar only goes to 47% and say like it would have "finished" - i dont believe in it
*use adb to sideload vendor zipfile zipfile with commands (adb shell twrp sideload and then adb sideload vendor.zip) - that one works normally
*changed slot from B (i was on before) to A on fastboot and flashed the vbmeta to current slot (A)
*reboot without wiping system partition and installing lineageos only brings up normal stock rom
*even wiped system partition one time (or should i say system_root?) - and installed lineageOS via adb sideload. but nothing was in the system_root folder as i mounted it back again
*wiping system partition and reboot only brings up android one loading screen endlessly
so basically, the installer says it has installed the rom, but in reality it didnt seem to touch the system partition at all. am i doing something wrong or may it be that because i dont have touch access i miss to move some unlock slider which is not implemented via adb shell twrp? i think something along these lines might be the case but.. i was able to adb shell twrp wipe system. so basically it should not be a big deal to write to system partition or system_root in general.
oh and of accusation that the adb sideload probably doesnt send data correctly (from which i heard lots of stories of the past), i even pushed the zip file via adb push to / and installed it with adb shell twrp install /lineageos.zip. same result.
what i would really like to see is an debug log of the installer zip. you only see "part 1 and part 2" installing and percentage, but no informations what the installer is doing currently. this would help a lot if there would be a switch for the installer like "verbose information"
edit again.
I finally managed to do the install. You know what? it is possible without the touch gui. what i did was:
*reflashed via fastboot the stock rom
*booted normally, installed the latest upgrade (Stock ROM OTA - took a long while) - (may be obsolete)
*booted to fastboot, flashed newest twrp to boot
*booted to recovery
*adb shell twrp remountrw
*adb shell twrp remountrw (the /tmp/recovery.log showed interestingly at first remountrw the page set of readonly, at second time not - why?)
*adb shell
*entered in adb shell mount /system
*adb shell twrp wipe data
*adb push lineageos.zip /data/
*adb shell twrp install /data/lineageos.zip
*adb push ddv.zip /data/
*adb shell twrp install /data/ddv.zip
*adb shell getprop ro.boot.slot_suffix (to get the actual boot slot)
*adb reboot bootloader
*fastboot --set-active=_a (for me i was on b before, so i needed to go to a)
*fastboot flash vbmeta_a --disable-verity --disable-verification vbmeta.img
*fastboot reboot
*then the phone - now on lineage - asked me to factory reset, i did
*booted finally successfully up to lineage 17.1 - wlan, mobile network working just fine
if you want gapps on it, install them ideally direct after your custom rom is able to boot. in my case gps didnt worked with gapps and other apps till i did another factory reset. and the original launcher that comes with the cust-rom doesnt work anymore after installing the gapps. use the pixel launcher instead. after that, it works like a charme
in conclusion: a bit odd how the install not works as in the description was told. maybe the TA-1196 is just a bit different.

Hello Together,
i've installed LineageOs yesterday and i realy like it . I just can't find an camera App that supports the wideAngle Camera at the back.
Open Camera only recognizes 2 Cameras, and GCam 7.0 Nokia 7.2 Mod can't seem to access it either.
Is there a solution to this?
Best regards
Alex

Changelog Fri Nov 13 23:24:47 IST 2020
==============================
- based on latest lineage sources
- November 2020 security patch
- fixed bluetooth audio
- fixed mic
- fixed RIL
- fixed headset
- based on android 10 prebuilt vendor for now ( DDV2.340 )
- Comes with stock kernel
- linux version 4.4.192
- compiled using gcc
- fixed battery drain
- fixed styles and wallpapers
- selinux enforced
- banking apps working
- use NikGapps

Got brand new nokia 7.2 yesterday, developer loaded old android build 1_130 and unlocked bootloader, didnt recommend twrp as this wol break wi-fi. Can I flash this OS on my phone directly without twrp ? will wifi and camera work as it should? Sorry for the questions I am new here and just started reading this Thank you

Nokia is nowadays very slow in giving security patch updates to its devices. Its a high time we switch to custom rom..?
I'm waiting for my phone's warranty to get over. Anyways, do anyone have any eta on when this rom will get official?

I have managed finally to install it, but sorry, nothing mentioned work: no double tapp sleep or wake up, no fingerprint, no slinux enforced, camera is not worth to mention at all and i still didnt test bluetooth or microphones yet. ..

dariuslapsys said:
I have managed finally to install it, but sorry, nothing mentioned work: no double tapp sleep or wake up, no fingerprint, no slinux enforced, camera is not worth to mention at all and i still didnt test bluetooth or microphones yet. ..
Click to expand...
Click to collapse
I agree for tapp to wake up and selinux.
Nevertheless, bluetooth and microphones and fingerprint sensors are working like a charm.
NFC is not mentioned anywhere, but I don't need this function at all.
I installed the build from 14/11.
@Raghu varma: Can we help you out sending logfiles for some issues? Do you need testers?

Raghu varma said:
Note - Iam Not Responsible for bricked devices
About LineageOS
LineageOS is a free and open-source operating system for set-top boxes, smartphones and tablet computers, based on the Android mobile platform. It is the successor to the custom ROM CyanogenMod, from which it was forked in December 2016 when Cyanogen Inc. announced it was discontinuing development and shut down the infrastructure behind the project. Since Cyanogen Inc. retained the rights to the Cyanogen name, the project rebranded its fork as LineageOS.
LineageOS was officially launched on December 24, 2016, with the source code available on GitHub. Since that time, LineageOS development builds now cover more than 185 phone models with over 1.9 million active installs,having doubled its user base in the month February–March 2017 And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Installation procedure
Note - I don't recommend you people to flash any other custom kernels on this ROM untill Nokia release kernel sources. Because this ROM supports only stock kernel .
1. Download Rom.zip , twrp.img & vbmeta.img
2. power off your phone boot in to bootloader mode and flash twrp
3. Boot in to Twrp
4. Format data by typing yes
5. Wipe everything
6. Flash rom.zip & vendor.zip
7. Now tap on reboot and check your current active slot.
Example - if twrp shows current active slot A change to B if B change to A
8. Tap on reboot and tap on bootloader ( this will reboots your phone to bootloder mode )
9. Now open cmd in pc flash vbmeta using this command
for slot-a > fastboot flash vbmeta_a --disable-verity --disable-verification vbmeta.img
for slot-b> fastboot flash vbmeta_b --disable-verity --disable-verification vbmeta.img
( thanks to @singhnsk for this step )
10. now type fastboot reboot
and wait for 3 min rom will boot up
Credits
* LineageOS & CO (For Source Code)
* All the authors in my git sources
* Nokia For Prebuilt Vendor & Kernel Source
* Moderators (For Giving Freedom To Post Threads)
* My entire Nokia 7.2 community Thank you all for your massive support Again
Join Nokia 7.2 Community

Download Rom
Download Vendor
Download vbmeta
Download GApps
Download Official Twrp
Android OS version: 11.0.0_r17
Security patch level: November 2020
Build author: Raghu varma
My build script: https://github.com/RaghuVarma331/scripts
Kernel Source code: https://github.com/RaghuVarma331/android_kernel_nokia_sdm660
Source code: https://github.com/LineageOS
Click to expand...
Click to collapse
When i install this rom volte function not proper working outgoing not work incoming volte works reply what is this

When i install this rom volte function not proper working outgoing not work incoming volte works reply what is this

[OFFICIAL][ZS620KL] LineageOS 17.1 (Android 10) for the Asus Zenfone 5z

{
"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 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 restores 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 our Gerrit Code Review.
Code:
#include
/*
* 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.
*/
SUPPORTED DEVICES
- ZS620KL (Asus Zenfone 5z)
HOW TO INSTALL LINEAGEOS WITH LINEAGE RECOVERY
Please follow the official LineageOS Wiki instructions for our device
Install LineageOS on Z01R | LineageOS Wiki
wiki.lineageos.org
MAIN DOWNLOADS
LineageOS:
- Official:
LineageOS Downloads
download.lineageos.org
- Unofficial test builds:
https://osdn.net/projects/lineageos-for-z01r/releases/p17177
GOOGLE APPS (GAPPS) DOWNLOADS
- Open GApps (pico or nano):
The Open GApps Project
OpenGApps.org offers information and pre-built packages of The Open GApps Project. The Open GApps Project is an open-source effort to script the automatic generation of up-to-date Google Apps packages. All Android versions and platforms supported.
opengapps.org
GOOGLE CAMERA (GCAM) DOWNLOADS
Google Camera:
Wichaya GCam APKs - Google Camera Port
Modified Google Camera app by Wichaya.
www.celsoazevedo.com
DEVELOPER RESOURCES
Asus ZenFone 5Z
Asus ZenFone 5Z has 7 repositories available. Follow their code on GitHub.
github.com
GitHub - LineageOS/android_device_asus_Z01R
Contribute to LineageOS/android_device_asus_Z01R development by creating an account on GitHub.
github.com
GitHub - LineageOS/android_kernel_asus_sdm845
Contribute to LineageOS/android_kernel_asus_sdm845 development by creating an account on GitHub.
github.com
GitHub - TheMuppets/proprietary_vendor_asus
Contribute to TheMuppets/proprietary_vendor_asus development by creating an account on GitHub.
github.com
HOW TO CONTRIBUTE?
Send your patches up for review:
https://review.lineageos.org
Read the guides on the LineageOS Wiki:
LineageOS Wiki
wiki.lineageos.org
XDA: DevDB Information
[OFFICIAL][ZS620KL][10.x] LineageOS 17.1 (Android 10) for the Asus Zenfone 5z
Contributors
Jackeagle, ThE_MarD, rohanpurohit, TARKZiM
Source Code:
LineageOS
A free and open-source operating system for various devices, based on the Android mobile platform. This is a mirror of https://review.lineageos.org/ - LineageOS
github.com
ROM OS Version: Android 10
ROM Kernel: Linux 4.9
Based On: AOSP

Features over Stock
FM Radio, File-Based Encryption (which allows power-off Alarm to actually work and no annoying PIN prompt half-ways through boot)
Known Bugs
4K UHD Video recording does not work in LineageOS Snap Camera app. (A workaround is to use other camera apps like OpenCamera or Gcam Mods)
Touch sometimes doesn't work in Lineage Recovery. The workaround is to use the volume buttons to move around the menu and power to select or to reboot to recovery.
Bluetooth A2DP can cause crashes during voice calls with certain Bluetooth devices (a workaround is to disable Bluetooth A2DP offload via developer options)
The current official build of TWRP doesn't support File-Based Encryption. The workaround is to use my modified build of TWRP found here

Just a heads up, I'm unsure when official builds will be starting, so please be patient. I'm guessing between Monday to Friday of this coming week
w00t! We got mentioned in an XDA article!
LineageOS 17.1 adds support for the OnePlus Nord, ASUS ZenFone 5Z, and more
Official LineageOS 17.1 builds are now available for the OnePlus Nord, the ASUS ZenFone 5Z, the Fairphone 3, and the Samsung Galaxy SIII Neo.
www.xda-developers.com

can't waiiit, thank you

Awesome work!

can someone help me, i tried the noob-friendly guide to install the recovery and ROM but whenever I install the recovery and try to install the recovery permanently, it gives me errors and phone sort of bricks. I really want to install an android 11 ROM please help.

amitrahi04 said:
can someone help me, i tried the noob-friendly guide to install the recovery and ROM but whenever I install the recovery and try to install the recovery permanently, it gives me errors and phone sort of bricks. I really want to install an android 11 ROM please help.
Click to expand...
Click to collapse
what steps you following?

Heyyo @amitrahi04 , sorry I accidentally had Android 11 in the thread title when LineageOS 17.1 is Android 10.
In order to use Android 11 ROMs please check their threads and their instructions.
I do plan to work on LineageOS 18.1 for Z01R later, but first I want to work on my Zippo (Lenovo Z6 Pro) and Payton (Motorola X4) and my x2 (LeEco Le Max 2) as they're already in progress for 18.1 and tbh I didn't expect 17.1 for Z01R to take this long, but OSS Vendor took a lot of time and effort

decentguy49 said:
what steps you following?
Click to expand...
Click to collapse
I'm following this guide: https://forum.xda-developers.com/t/guide-noob-friendly-custom-rom-flashing-guide.3944849/
I want to try this ROM: https://forum.xda-developers.com/t/rom-11-r-official-evolution-x-z01r-19-12.3981601/

amitrahi04 said:
I'm following this guide: https://forum.xda-developers.com/t/guide-noob-friendly-custom-rom-flashing-guide.3944849/
I want to try this ROM: https://forum.xda-developers.com/t/rom-11-r-official-evolution-x-z01r-19-12.3981601/
Click to expand...
Click to collapse
If you have anything important on your device then back it up
Download the LOS ROM, LOS recovery and GAPPS if you want to flash
Use official tool to unlock bootloader
Once bootloader is unlocked, reboot to bootloader
adb reboot bootloader
Click to expand...
Click to collapse
Flash LOS recovery
fastboot flash boot RecoveryName.img
Click to expand...
Click to collapse
Now reboot to recovery
Select Factory Reset.
Flash the LOS ROM
if you want to use GAPPS, then reboot to recovery and flash Open GApps
Reboot to system

@amitrahi04 , if you want help for that ROM I'd recommend posting in the thread for that ROM as this thread is for LineageOS 17.1 for Z01R, so please keep posts in this thread for this ROM

Heyyo! It is time! Official LineageOS 17.1 for Z01R is released!!!

I tried to install GAPPS nano for it, but when it starts, G Apps as (Play Store) does not appear on the system. First time I had this error. I ended up going back to Stock, i tried 5x...

ThE_MarD said:
Heyyo! It is time! Official LineageOS 17.1 for Z01R is released!!!
Click to expand...
Click to collapse
I installed it right away when it is available. Everything's working fine. Using it as my daily driver.

iShaKinGameR said:
I tried to install GAPPS nano for it, but when it starts, G Apps as (Play Store) does not appear on the system. First time I had this error. I ended up going back to Stock, i tried 5x...
Click to expand...
Click to collapse
Assuming that you used the Lineage Recovery, the same thing happened to me on my first attempt. Right after flashing the ROM, i continued to flash GAPPS and reboot. Like your problem, Google apps did not show up when i boot the system.
However, i missed one step as stated in the installation process. As per the instruction, right after flashing the ROM itself, you have to click Advanced, then Reboot to Recovery, then when your device reboots, click Apply Update, then Apply from ADB, then adb sideload <filename>.zip, which in this case is the gapps.zip. Then, reboot to system. The google apps will now appear in the system. Hope it works for you also

HtMawia said:
Assuming that you used the Lineage Recovery, the same thing happened to me on my first attempt. Right after flashing the ROM, i continued to flash GAPPS and reboot. Like your problem, Google apps did not show up when i boot the system.
However, i missed one step as stated in the installation process. As per the instruction, right after flashing the ROM itself, you have to click Advanced, then Reboot to Recovery, then when your device reboots, click Apply Update, then Apply from ADB, then adb sideload <filename>.zip, which in this case is the gapps.zip. Then, reboot to system. The google apps will now appear in the system. Hope it works for you also
Click to expand...
Click to collapse
Thank you very much! I took advantage of this function and put the Magisk, so I can use the rom to test.

Heyyo @iShaKinGameR and @HtMawia , the step after ROM flash and reboot to recovery is very important for us as Z01R is an A/B partitioned device. The ROM always flashes to the inactive slot and then it tells the bootloader to switch slots which requires a reboot. So the reboot to recovery is to get recovery to reload onto the slot that the ROM was flashed so that you can then install gapps and such.
Devices that are A-Only, such as the Lenovo Z6 Pro (Zippo) do not need this step as there is only one slot it can flash to. I think the Asus Zenfone Max Pro M1 (X00TD) Is only A-Only as well.

So far everything is OK and more fluid than ZenUI. I just realized that the ROM doesn't seem to have a Camera Wide-Angle, I tried to activate it through build.prop and went into bootloop. I am trying to use it daily.
Edit: The HDR DCI mode does not activate on YouTube.

Hi, the rom is great, but I have no mobile network. It should just reigster on the network automatically... Any ideas? I think maybe it has something to do with the vendor file. How do I update this? Which file is correct, and at what point do I flash it? Thanks!

@iShaKinGameR , the LOS snap camera app only supports the main rear camera. For the aux rear camera I recommend switching to a different camera app like OpenCamera or better yet, the Wichaya GCam mods which I link to in my first post.
There's no need for that aux camera app prop as I used the newer prop that just exposes the aux camera to all camera apps
Z01R: Expose aux camera globally · LineageOS/[email protected]
Switch out vendor.camera.aux.packagelist for persist.vendor.camera.expose.aux Change-Id: I7295184a001d4c851b2d147bd35399b06a185bc4
github.com
Tbh I'm unsure of any HDR DCI videos on YouTube, but I do know that HDR itself does work for me on the LOS official build...
If it doesn't work for you, can you please provide logcat?
@greves1 , can you please provide logcat? There is no need to modify anything in the vendor partition as we use a source-built vendor partition which includes everything needed to make our device work on LineageOS 17.1.

Develop Bugs

welcome