Database Develop

Please help to install ROM in [Raphaelin]

Please help me. I can't seem to understand what exactly I need to do in order to install a custom ROM on my K20 Pro (Global 10.3.5.0.) I have tried following this (https://forum.xda-developers.com/k20...0-pro-t3953844) post thoroughly and others as well, but can't seem to exactly understand what I am required to do. Most custom ROM's state [Raphael], but as I purchased this device in India, it would most probably be [Raphaelin], after unlocking the Bootloader and installing TWRP, am I supposed to flash a Custom ROM (for ex. Lineage OS) directly or would I have to install a ROM which would make my device [Raphael]? Vendor and Firmware have gone over my head, I do not understand what I need to di. If someone could help me out, It would be mean a lot. Thank you.

Platinum_Pyth0n said:
Please help me. I can't seem to understand what exactly I need to do in order to install a custom ROM on my K20 Pro (Global 10.3.5.0.) I have tried following this (https://forum.xda-developers.com/k20...0-pro-t3953844) post thoroughly and others as well, but can't seem to exactly understand what I am required to do. Most custom ROM's state [Raphael], but as I purchased this device in India, it would most probably be [Raphaelin], after unlocking the Bootloader and installing TWRP, am I supposed to flash a Custom ROM (for ex. Lineage OS) directly or would I have to install a ROM which would make my device [Raphael]? Vendor and Firmware have gone over my head, I do not understand what I need to di. If someone could help me out, It would be mean a lot. Thank you.
Click to expand...
Click to collapse
If you're running stock MIUI and haven't moved to any custom MIUI's till date then you can straight away flash LOS. Moreover, most of the custom roms work on multiple vendors irrespective of whether it is a China Vendor or India or Global. It doesn't matter till the time the developer specifically asks you to be on a particular vendor.
Vendor isn't a dreaded thing. It's just the drivers needed to run the various components in the device (BT, WiFi etc). Till the time you don't wipe the vendor partion in twrp, you would always be good to go. You could carry on flashing custom roms w/o careing about the vendor.
Sent from my Redmi K20 Pro using Tapatalk

Sukhi said:
If you're running stock MIUI and haven't moved to any custom MIUI's till date then you can straight away flash LOS. Moreover, most of the custom roms work on multiple vendors irrespective of whether it is a China Vendor or India or Global. It doesn't matter till the time the developer specifically asks you to be on a particular vendor.
Vendor isn't a dreaded thing. It's just the drivers needed to run the various components in the device (BT, WiFi etc). Till the time you don't wipe the vendor partion in twrp, you would always be good to go. You could carry on flashing custom roms w/o careing about the vendor.
Sent from my Redmi K20 Pro using Tapatalk
Click to expand...
Click to collapse
Thank you very much for your reply. So, just to check if I have understood correctly. I can just install TWRP and then flash Lineage OS straight away, right? I checked (https://forum.xda-developers.com/k20-pro/development/rom-lineageos-16-0-t3965311), and it mentioned:
Instructions :
Download the latest build and GApps
Reboot to recovery
Flash proper vendor and firmware
Flash the latest build and GApps
Reboot
What is "proper vendor and firmware"? And would I also be required to flash this?
Thank you.

Platinum_Pyth0n said:
Thank you very much for your reply. So, just to check if I have understood correctly. I can just install TWRP and then flash Lineage OS straight away, right? I checked (https://forum.xda-developers.com/k20-pro/development/rom-lineageos-16-0-t3965311), and it mentioned:
Instructions :
Download the latest build and GApps
Reboot to recovery
Flash proper vendor and firmware
Flash the latest build and GApps
Reboot
What is "proper vendor and firmware"? And would I also be required to flash this?
Thank you.
Click to expand...
Click to collapse
Go back to the Lineage instructions and read immediately below that. It starts P.S.
It explains exactly proper vendor and firmware means.
No you won't need to install anything for this step

Platinum_Pyth0n said:
Thank you very much for your reply. So, just to check if I have understood correctly. I can just install TWRP and then flash Lineage OS straight away, right? I checked (https://forum.xda-developers.com/k20-pro/development/rom-lineageos-16-0-t3965311), and it mentioned:
Instructions :
Download the latest build and GApps
Reboot to recovery
Flash proper vendor and firmware
Flash the latest build and GApps
Reboot
What is "proper vendor and firmware"? And would I also be required to flash this?
Thank you.
Click to expand...
Click to collapse
Nope ! You don't need to flash vendor + firmware as you already running an untouched stock MIUI build. That is for people who are coming from either modified MIUI builds (EU, Miroom etc) or custom roms with a different vendor (India device running on China Vendor)
Custom roms don't carry the Vendor Firmware files and you can only modify the existing Vendor when you move to other region stock or custom MIUI roms.
Back up your data on Internal storage to a safe place either on a PC or OTG. Skip this step if you have nothing important.
Boot In TWRP
Wipe System, Data , Cache , Dalvik
(Don't reboot at this point, Not Even a Recovery reboot)
Flash LOS
Flash GApps
Go to Advanced Wipe and Format Data by typing Yes
Reboot
Sent from my Redmi K20 Pro using Tapatalk

Sukhi said:
Nope ! You don't need to flash vendor + firmware as you already running an untouched stock MIUI build. That is for people who are coming from either modified MIUI builds (EU, Miroom etc) or custom roms with a different vendor (India device running on China Vendor)
Custom roms don't carry the Vendor Firmware files and you can only modify the existing Vendor when you move to other region stock or custom MIUI roms.
Back up your data on Internal storage to a safe place either on a PC or OTG. Skip this step if you have nothing important.
Boot In TWRP
Wipe System, Data , Cache , Dalvik
(Don't reboot at this point, Not Even a Recovery reboot)
Flash LOS
Flash GApps
Go to Advanced Wipe and Format Data by typing Yes
Reboot
Sent from my Redmi K20 Pro using Tapatalk
Click to expand...
Click to collapse
I'm trying to install a custom rom in K20 pro raphaelin. But it is getting stucked at recovery. Then I have to install stock ROM using MIFlash. Any help on this issue?
Custom ROM is successfully flashed in TWRP.

MyNameIsAbey said:
I'm trying to install a custom rom in K20 pro raphaelin. But it is getting stucked at recovery. Then I have to install stock ROM using MIFlash. Any help on this issue?
Custom ROM is successfully flashed in TWRP.
Click to expand...
Click to collapse
Did you do FORMAT Data (not just Wipe) when you installed your custom ROM, and before rebooting?

Install TWRP, Root, LineageOS and Immensity Kernel from Stock?

Hey,
So after a lot of observation and reading I think LOS 17.1 seems stable enough to be used for a daily driver.
Right now I am on the normal stock ROM, without any modifications, no TWRP, no root whatsoever.
However, I have unlocked the bootloader a few months ago, so that's done already.
Current state of the phone:
Code:
MIUI version: 11.0.1.0 (QFKMIXM) - Is this the global version?
Device model: Mi 9T Pro (128GB, 6GB RAM)
I want to install TWRP, I want to root the phone, I want to install all needed modules for a proper camera etc, I want to install LineageOS 17.1 (latest build) and lastly I want to install Immensity Kernel (latest build) because I have heard it works well with LOS and provides lots of battery improvements.
I did lots of tinkering with my phone a couple years back, but I haven't done so in a while, and neither have I done anything with this device, so to make sure I am not breaking anything I decided its the best to ask here.
What steps do I have to provide in which order? Can someone provide my a detailed explanation of all the needed steps?
Also, can I install MicroG on it, or do I have to use GApps?
My guess is, first TWRP and root, then ROM and then kernel?
Also, I have read about some issues with Magisk and Android 10, is that still a problem, or is that solved by now?
Anything else I need to look out for?
Cheers

KuroRyu said:
Hey,
So after a lot of observation and reading I think LOS 17.1 seems stable enough to be used for a daily driver.
Right now I am on the normal stock ROM, without any modifications, no TWRP, no root whatsoever.
However, I have unlocked the bootloader a few months ago, so that's done already.
Current state of the phone:
I want to install TWRP, I want to root the phone, I want to install all needed modules for a proper camera etc, I want to install LineageOS 17.1 (latest build) and lastly I want to install Immensity Kernel (latest build) because I have heard it works well with LOS and provides lots of battery improvements.
I did lots of tinkering with my phone a couple years back, but I haven't done so in a while, and neither have I done anything with this device, so to make sure I am not breaking anything I decided its the best to ask here.
What steps do I have to provide in which order? Can someone provide my a detailed explanation of all the needed steps?
Also, can I install MicroG on it, or do I have to use GApps?
My guess is, first TWRP and root, then ROM and then kernel?
Also, I have read about some issues with Magisk and Android 10, is that still a problem, or is that solved by now?
Anything else I need to look out for?
Cheers
Click to expand...
Click to collapse
Make sure you are in the latest version of MIUI first.
For TWRP flash the latest Mauronofrio TWRP, he has the official TWRP, but his unofficial, latest version is probably a better option at its a little bit more up to date.
Once you've flashed TWRP you will need to boot immediately in to TWRP without allowing the phone to boot into MIUI, otherwise the phone will detect that recovery had been modified and will restore stock recovery.
When you've booted into TWRP, format data (needs to be format and not only wipe), then wipe cache and dalvik.
Reboot into TWRP, to ensure that the newly formatted data partition is correctly mounted.
Now flash lineage and a GApps package. I've only used Open GApps Pico, but I believe microG should be OK. If you use Open GApps it is still in beta and packages larger than the micro package are likely to cause issues, so stick with micro, pico or nano. (For clarification, micro G is a GApps package, what you are really asking is do you need to use Open GApps or not)
The latest Magisk is fine now. It is recommended to boot into LOS first at least once before flashing Magisk. I can't remember the details but sometimes you may get issues if you flash Magisk after flashing a ROM, without booting to the ROM first. You may be fine if you don't boot the ROM first, but since I've forgotten the reasons and can no longer find it, I now boot the ROM before flashing Magisk, just to be safe.
From here, you should be OK to flash different kernels, personally I've never felt the need to, as I'm happy with the performance of things as they are. My battery life is similar to what it was on stock MIUI. If you want to try kernels other than Immensity, just double check first that it is for AOSP ROMs. There are some kernels that have been created that are only compatible with Stock MIUI.
For the camera, I believe the latest advice for ANX Cam is still version 158 along with the 48MP fix for Q ROMs. There are a few later versions, which are not appropriate for this phone. I don't believe there has been a later version for this phone.
Edit: just noticed your question in the quote.
You have the global version of the phone. AFAIK 11.0.1 is still the latest version of the global version of MIUI.

Robbo.5000 said:
Make sure you are in the latest version of MIUI first.
For TWRP flash the latest Mauronofrio TWRP, he has the official TWRP, but his unofficial, latest version is probably a better option at its a little bit more up to date.
Once you've flashed TWRP you will need to boot immediately in to TWRP without allowing the phone to boot into MIUI, otherwise the phone will detect that recovery had been modified and will restore stock recovery.
When you've booted into TWRP, format data (needs to be format and not only wipe), then wipe cache and dalvik.
Reboot into TWRP, to ensure that the newly formatted data partition is correctly mounted.
Now flash lineage and a GApps package. I've only used Open GApps Pico, but I believe microG should be OK. If you use Open GApps it is still in beta and packages larger than the micro package are likely to cause issues, so stick with micro, pico or nano. (For clarification, micro G is a GApps package, what you are really asking is do you need to use Open GApps or not)
The latest Magisk is fine now. It is recommended to boot into LOS first at least once before flashing Magisk. I can't remember the details but sometimes you may get issues if you flash Magisk after flashing a ROM, without booting to the ROM first. You may be fine if you don't boot the ROM first, but since I've forgotten the reasons and can no longer find it, I now boot the ROM before flashing Magisk, just to be safe.
From here, you should be OK to flash different kernels, personally I've never felt the need to, as I'm happy with the performance of things as they are. My battery life is similar to what it was on stock MIUI. If you want to try kernels other than Immensity, just double check first that it is for AOSP ROMs. There are some kernels that have been created that are only compatible with Stock MIUI.
For the camera, I believe the latest advice for ANX Cam is still version 158 along with the 48MP fix for Q ROMs. There are a few later versions, which are not appropriate for this phone. I don't believe there has been a later version for this phone.
Edit: just noticed your question in the quote.
You have the global version of the phone. AFAIK 11.0.1 is still the latest version of the global version of MIUI.
Click to expand...
Click to collapse
Do I also need the force encrypt file? Some people mention it needs to be flashed too?
How do I properly install twrp? I boot into fastboot mode, and then I can flash it, I assume?
In the thread it also states that one should first flash vbmeta?
EDIT: Ok, I flashed vbmeta and twrp, booted into twrp, formated data and wiped dalvik and cache.
Now should I flash LOS next and then gapps ..? Which GApp package is the right one for 17.1? It is not linked in the LOS thread?
I've read that some people had issues when flashing the wrong gapps package
EDIT2: Ok, so far I have persisted TWRP and installed magisk. I flashed LOS 17.1 (latest build) and booted into it. I did not flash gapps yet as I dont know which gapps package to use. Also I would prefer to use microG if possible, but I dont think its possible to install it easiely? If it is, please let me know.
Now, the issue is, for some reason after the clean install of LOS17.1 I still see google apps like google drive (remember, I did not flash gapps). This shouldn't be the case? I did format data and cleared dalvik and cache, so it is a bit weird that this happens...
Also I constantly get "android.process.media keeps stopping" .. I assume that is because some applications try to access google service, which are not correctly available? What did I do wrong?
So my questions are:
1) Is it possible to use microG (opensrc implementation of google services), rather than gapps? If so, how?
2) If I need to use GApps, which one to flash?
3) Why were google apps still present on my device after flashing and formatting data ..?

KuroRyu said:
Do I also need the force encrypt file? Some people mention it needs to be flashed too?
How do I properly install twrp? I boot into fastboot mode, and then I can flash it, I assume?
In the thread it also states that one should first flash vbmeta?
EDIT: Ok, I flashed vbmeta and twrp, booted into twrp, formated data and wiped dalvik and cache.
Now should I flash LOS next and then gapps ..? Which GApp package is the right one for 17.1? It is not linked in the LOS thread?
I've read that some people had issues when flashing the wrong gapps package
EDIT2: Ok, so far I have persisted TWRP and installed magisk. I flashed LOS 17.1 (latest build) and booted into it. I did not flash gapps yet as I dont know which gapps package to use. Also I would prefer to use microG if possible, but I dont think its possible to install it easiely? If it is, please let me know.
Now, the issue is, for some reason after the clean install of LOS17.1 I still see google apps like google drive (remember, I did not flash gapps). This shouldn't be the case? I did format data and cleared dalvik and cache, so it is a bit weird that this happens...
Also I constantly get "android.process.media keeps stopping" .. I assume that is because some applications try to access google service, which are not correctly available? What did I do wrong?
So my questions are:
1) Is it possible to use microG (opensrc implementation of google services), rather than gapps? If so, how?
2) If I need to use GApps, which one to flash?
3) Why were google apps still present on my device after flashing and formatting data ..?
Click to expand...
Click to collapse
There is no need to flash force encrypt files or vbmeta.
I have never used MicroG so couldn't give any answers about that, however Open GApps are open source too. For android 10 it is still in beta. The beta files can be found here https://sourceforge.net/projects/opengapps/files/arm64/beta/20191209/. Pico is the smallest package that gives Google Play, personally I recommend going with that, then installing any other Google stuff from the play store, should you want them.
No idea why you would be seeing Google apps. I can only suggest formatting data again in TWRP.
If that doesn't work I would start again. Fastboot flash the latest MIUI 11.0.1 global ROM, boot into it once, there is no need to go through the set-up. Then go through the steps given before.
This time don't flash vbmeta, it is not needed.
The fastboot ROM can be found here http://bigota.d.miui.com/V11.0.1.0....M_20191111.0000.00_10.0_global_11d3a1700a.tgz
Edit:
Having seen some of your other posts, I'll give you some more info.
vbmeta is mainly used to persist TWRP. However flashing Magisk will persist TWRP and flashing a custom ROM will persist TWRP. You would only need to flash vbmeta if you wanted to stay on MIUI and not use Magisk. (There are other uses for vbmeta, but you don't need them, so I'll not go into them)

Is widevine L1 available on the ROM? Is the FOD working well?

[ROM][S9+/S9][LineageOS 17.1][UNOFFICIAL][05-06-20][OTA]

What's working:
Wi-Fi
Bluetooth
Mobile Network (Calling, Data, etc.)
Signal Strength
GPS
NFC
Audio (Stereo Speakers)
Camera
Fingerprint Sensor
HDMI
MTP
Call Recording
HWC
Encryption
SELinux Enforcing
OTA Updates
Bugs:
?
Notes:
If you are not on Q BL it will not boot.
I would suggest 3.2.3 TWRP or the included lineage recovery
For encryption to work make sure you are on 3.2.3 twrp and haven't formatted /data with any newer versions, issue described here.
Use a stock unmodified vendor and update whenever available, we are using our own fstab now for optional encryption and adoptable storage support so we don't need to touch the vendor.
If you go back to an official build after this with stock vendor, you will be force encrypted on first boot.
These builds are based on the official lineage device trees and kernel, but with more flexibility and my preferred configuration.
Lineage Recovery will be uploaded with each build and if you will only be running this rom i suggest to switch to it.
Instructions:
Make sure TWRP has been installed and is functional
Download the latest build and latest stock vendor.img that is available (optionally gapps and magisk if needed)
Reboot to recovery
Wipe data and cache (required if you switch from other ROMs)
Flash the vendor image
Flash the latest build (then gapps and magisk if needed)
Reboot
How to update builds?
OTA or manually like below
Do not wipe anything unless stated in the changelog
Flash only the rom.zip and it will automatically reinstall your gapps, magisk etc
use /system/addon.d if you would like to keep system mods after an update
Downloads:
Lineage-17.1: (mega) https://mega.nz/#F!0McClQKJ!ic8c0LEYF3zGSo_Ivv1nSw
Lineage-17.1: (github) https://github.com/synt4x93/OTA/releases
Google Apps: https://opengapps.org/
Telegram Channel:
@godlike9810
Paypal:
synt4x.93
XDA:DevDB Information
LineageOS 17.1, ROM for the Samsung Galaxy S9/+
Contributors
Synt4x.93, Erfanoabdi
Source Code: https://github.com/synt4x93/
ROM OS Version: Android 10
ROM Kernel: Linux 4.9.226
ROM Firmware Required: Q BL / Q Vendor
Version Information
Status: Stable
Created: 01-04-2020
Last Updated: 05-06-2020

temp

Great ROM really smooth but only one issue i have is when i try to record the screen with internal sound (gaming) it will mute the sound from the speaker and it's working fine Evox (sorry for my bad English

Hello everyone! Not sure how many people here already been trying this ROM from the Telegram group, but was wondering if anyone has the following issue. Google Chrome seems to become really laggy in the evening hours on my phone, but is fine during the day. Basically scrolling and animations within Chrome are really slow causing bad performance. Wanted to confirm if it's just me as Rob said the issue doesn't seem to happen with the Note 9 and see if anyone here has any suggestions? I am running DTB4 BL and vendor with TWRP 3.2.3.0.

so everything good other than Android Auto? Well done!

Great news! Thanks a lot for keeping our device alive and updated!
Can't wait to try this one out. I assume it's working fine as a daily driver?

geronimoge said:
Great news! Thanks a lot for keeping our device alive and updated!
Can't wait to try this one out. I assume it's working fine as a daily driver?
Click to expand...
Click to collapse
Yup, been using it for several weeks. No odd reboots and stuff, just very stable.

How can I check for the right BL?
What does it mean "Q BL"?
Thanks
EDIT:
Never mind, I found it! :good:

..ok, stupid question, but where can I get q bl?
Do I need to use odin to flash just bl from one of q roms or is there just q bl to download somewhere?

Great rom, thanks for this, I came from the LOS 16 and LOS 17.1 of the 09/01 and all good until now
Here is a link for download q bootloader
https://mega.nz/#F!oFJ1nK5Z!eWD2AU4CQxWSdA_kxxRkHA
vendor images and bootloader zip are taken from devbase rom by alexndr so big thank for his work
current vendor version
S9/S9+ : DTB5
N9 : DTB6

Hoooly ****, I tried to make dirty flash from LOS 16(with replacing bl and vendor, of course), with just cache and dalvik cache wipe, and everything just WORKS fine.
This is AMAZING!
So:
1. twrp - wipe dalvik and cache,
2. twrp - flash bl,
3. twrp - flash vendor, but vendor from OP(!),
4. twrp - flash ROM,
5. twrp - flash opengapps.
Damn, it saved me reinstalling 132 apps, and setting all accounts all over.
What's great - all settings are kept from previous OS.
Of course, I lost viperfx and all magisk-related plugs(list of plugins is still there, so all I needed to do was reinstalling plugins ), but, still, this is great.

Great, glad all went good for you

Thanks for working instructions and links!
Thanks a lot! :victory:
I guess it's to much to ask for those information from a developer...
Side note: there is a boot loader for DTB5 only, but the modified vendor for LOS is DTB4. It works, though.
I did update from the 09/01/2020, so far found two issues:
1. After installing White Wolfs Kernel, UI seems to crash after unlocking via pattern, returning me back to unlock pattern. Had to wipe and re-install (dirty install of LOS didn't solve the issue ).
2. AFWall doesn't work. Applying rules fails leaving the system without internet access.
First one is not that important, but I'd like a firewall on my device...
Anyway: Thanks for the work on the LOS.
HackAR
DeCo59 said:
Here is a link for download q bootloader
https://mega.nz/#F!oFJ1nK5Z!eWD2AU4CQxWSdA_kxxRkHA
vendor images and bootloader zip are taken from devbase rom by alexndr so big thank for his work
current vendor version
S9/S9+ : DTB5
N9 : DTB6
Click to expand...
Click to collapse
xo.en said:
1. twrp - wipe dalvik and cache,
2. twrp - flash bl,
3. twrp - flash vendor, but vendor from OP(!),
4. twrp - flash ROM,
5. twrp - flash opengapps.
Click to expand...
Click to collapse

Great work! ROM works great, even Google pay is working good!

I just installed your ROM. It is very nice that the keyboard is now bigger then the one of theolder version and my new bluetooth headset is finally working.
Unfortunately, I cannot get ctsProfile to pass.
Does anyone have ctsProfile passing?
Edit: nevermind, should have read the docs of MagiskHide Props, the last module did the config automatically...
All the best,
Daniel

Hack_AR said:
After installing White Wolfs Kernel, UI seems to crash after unlocking via pattern, returning me back to unlock pattern. Had to wipe and re-install (dirty install of LOS didn't solve the issue ).
Click to expand...
Click to collapse
Same here, can’t unlock after installing White Wolf kernel. Furthermore, the phone is in Emergency calls only mode, as if there is no SIM card.
How to “undo” or otherwise solve this?

Hack_AR said:
2. AFWall doesn't work. Applying rules fails leaving the system without internet access.
First one is not that important, but I'd like a firewall on my device...
Anyway: Thanks for the work on the LOS.
Click to expand...
Click to collapse
I have the same problem. I'm still on LOS 16 as a daily driver because of this (and because of its awesome battery live). I will keep testing though...
Also my thanks for the great work on LOS!

oldipp said:
Same here, can’t unlock after installing White Wolf kernel. Furthermore, the phone is in Emergency calls only mode, as if there is no SIM card.
How to “undo” or otherwise solve this?
Click to expand...
Click to collapse
I had the problem that the first boot after upgrade went without problems (or PIN prompt in my case) but after that, when entering the correct PIN, the screen got black and then locked again. If I entered the wrong PIN, the phone told me so.
My solution was to use TWRP to rename the file /data/system/locksettings.db to locksettings.db.bak and then reboot. By renaming the file, the screen lock was removed and I could reenable it in the settings.
Good luck,
Daniel

Speedmatze said:
I'm still on LOS 16 as a daily driver because of this
Click to expand...
Click to collapse
I didn't have the problem with the old 09/01/2020 version, so you ca try it, or wait for the fix
---------- Post added at 12:35 PM ---------- Previous post was at 12:21 PM ----------
Weirdly enough, my system doesn't have this file. BUT, another try of White Wolfs kernel just worked. It seems this is an obsolete file, that some times is left behind confused and causes problems in the kernel.
Hofedan said:
I had the problem that the first boot after upgrade went without problems (or PIN prompt in my case) but after that, when entering the correct PIN, the screen got black and then locked again. If I entered the wrong PIN, the phone told me so.
My solution was to use TWRP to rename the file /data/system/locksettings.db to locksettings.db.bak and then reboot. By renaming the file, the screen lock was removed and I could reenable it in the settings.
Good luck,
Daniel
Click to expand...
Click to collapse

Hofedan said:
My solution was to use TWRP to rename the file /data/system/locksettings.db to locksettings.db.bak and then reboot. By renaming the file, the screen lock was removed and I could reenable it in the settings.
Click to expand...
Click to collapse
It was too late for me to remove that file, because I had encrypted /data, was no longer able to access it from within LOS, and I don’t know if TWRP can decrypt /data. If it happens to you, I would suggest to seize the opportunity while LOS still unlocks on the first boot to delete that locksettings file. In any case, having a backup is a must, because I am not sure this will actually work.

Flashing GSI image bootloops the device

I have been using custom roms for years.
I wanted to try flashing GSI images, and i decided to start with Havoc-OS-v4.4-20210503-arm64-a-Official-vanilla.img
I installed twrp-3.5.2_9-0-z2_row
I completely wiped everything, system/cache/data etc.
I flashed Havoc-OS-v4.4-20210503-arm64-a-Official-vanilla.img then NikGapps-basic-arm64-11-20210514-signed.zip.
Rebooted.
Phone is instantly resetting right after the ZUK logo goes away. stuck in boot loop. Am i doing something wrong ?

hash02 said:
I have been using custom roms for years.
I wanted to try flashing GSI images, and i decided to start with Havoc-OS-v4.4-20210503-arm64-a-Official-vanilla.img
I installed twrp-3.5.2_9-0-z2_row
I completely wiped everything, system/cache/data etc.
I flashed Havoc-OS-v4.4-20210503-arm64-a-Official-vanilla.img then NikGapps-basic-arm64-11-20210514-signed.zip.
Rebooted.
Phone is instantly resetting right after the ZUK logo goes away. stuck in boot loop. Am i doing something wrong ?
Click to expand...
Click to collapse
Can you send me the link of the thread where you saw your rom?. Pretty sure theres a tutorial in it.. You are missing some important step like flashing create vendor.zip or repartitioner.zip and some other stuff.. Give me the link...

[11][OFFICIAL] Havoc-OS 4.1 [ARM64/ARM/A64][A/AB/AB-VNDKLITE][GApps/Vanilla]
Havoc-OS 4.x is based on AOSP, inspired by Google Pixel. Has a refined Material Design 2 UI crafted by @SKULSHADY. Many useful features that will blow your mind. All you can dream of and all you'll ever need. Just flash and enjoy... General...
forum.xda-developers.com
Your question is a bit weird because this is a GSI. it's not model specific and should apply to things treble.
So it's not "my rom" it's just a gsi rom that should just work, right ? (unless i did something wrong)
Procedure was standard, clean, no dirty flashing.
Flash img, then gapps, then reboot.
I remember the instructions were for an older version of havoc, i just took the latest build because that's what you usually do ???
Regardless, this is not a HAVOC issue, I later tried with caos build caos-v307-210507-arm64-agZ.img. The exact same behavior happened.

hash02 said:
[11][OFFICIAL] Havoc-OS 4.1 [ARM64/ARM/A64][A/AB/AB-VNDKLITE][GApps/Vanilla]
Havoc-OS 4.x is based on AOSP, inspired by Google Pixel. Has a refined Material Design 2 UI crafted by @SKULSHADY. Many useful features that will blow your mind. All you can dream of and all you'll ever need. Just flash and enjoy... General...
forum.xda-developers.com
Your question is a bit weird because this is a GSI. it's not model specific and should apply to things treble.
So it's not "my rom" it's just a gsi rom that should just work, right ? (unless i did something wrong)
Procedure was standard, clean, no dirty flashing.
Flash img, then gapps, then reboot.
I remember the instructions were for an older version of havoc, i just took the latest build because that's what you usually do ???
Regardless, this is not a HAVOC issue, I later tried with caos build caos-v307-210507-arm64-agZ.img. The exact same behavior happened.
Click to expand...
Click to collapse
Redo the process and try to flash the gsi only without gaps then boot..

r
ivanjudge said:
Redo the process and try to flash the gsi only without gaps then boot.. You can check this out also maybe it will help? https://forum.xda-developers.com/t/zuk-z2-pro-project-treble-android-10-11-12-gsi-ab.4197355/
Click to expand...
Click to collapse

to flash a GSI image first you should wipe all except internal storage.
then install a Vendor ie; Basic roms like AEX, ARROW OS according to the GSI Version
if you GSI image is based on Android 10 then you should flash a android 10 rom from aex or arrow, then flash the gsi to system, then reboot

prc.kailas said:
to flash a GSI image first you should wipe all except internal storage.
then install a Vendor ie; Basic roms like AEX, ARROW OS according to the GSI Version
if you GSI image is based on Android 10 then you should flash a android 10 rom from aex or arrow, then flash the gsi to system, then reboot
Click to expand...
Click to collapse
So, the gsi flashing just copies the image-byte-by-byte to the /system partition ?
Just like dd on linux ? Blind transfer from one direction to the other ?Is this why you recommend flashing "basic roms", so that by flashing the zips all other partitions are updated accordingly ? like /vendor and so on ?Please clarify and keep it technical, i want to learn

ivanjudge said:
Redo the process and try to flash the gsi only without gaps then boot..
Click to expand...
Click to collapse
I already did
right now i am on aospextended android 11 version. since it's not a gsi image it worked. but it is unstable and i really want to try the gsi images and make it work primarily out of technical curiosity

hash02 said:
I already did
right now i am on aospextended android 11 version. since it's not a gsi image it worked. but it is unstable and i really want to try the gsi images and make it work primarily out of technical curiosity
Click to expand...
Click to collapse
Try what @hash02 said you can check the link i gave you above to view the full detail and to avoid boot loops reboot to recovery after flashing the gsi then flash the gapss then factory reset then reboot...And dont use nikgaps instead use other Gapps..

ivanjudge said:
Try what @hash02 said you can check the link i gave you above to view the full detail and to avoid boot loops reboot to recovery after flashing the gsi then flash the gapss then factory reset then reboot...And dont use nikgaps instead use other Gapps..
Click to expand...
Click to collapse
Well, Ok but where do i find android 11 opengapps ?

I didn't find any other gapps for Android 11.
However I tried your method even if it makes absolutely no sense at all. This device is a-only not a/b. Can you explain that or is that an elephant in the room that you dont want to talk about ?
In any case, the device does not bootloop anymore, it just sits in fastboot mode.

These are the steps to flash a gsi on zuk z2 pro correctly:
Wipe clean all partitions excluding user data
Then flash https://forum.xda-developers.com/t/radio-modem-basebands-for-zuk-z2-pro-only.3715835/ latest baseband
Flash boot image [ linked below - it is the boot image extracted from a mokee 9.0 rom ]
flash vendor image [ copied from another thread ]
flash gsi image [which ever you want]
reboot to recovery again [ sometimes it doesnt work unless you do ]
reboot to system
https://mega.nz/folder/E55iTZQJ#jNsa9d7WxLKr-9q_LFPS1A saved here for anyone else's convenience.

hash02 said:
So, the gsi flashing just copies the image-byte-by-byte to the /system partition ?
Just like dd on linux ? Blind transfer from one direction to the other ?Is this why you recommend flashing "basic roms", so that by flashing the zips all other partitions are updated accordingly ? like /vendor and so on ?Please clarify and keep it technical, i want to learn
Click to expand...
Click to collapse
by flashing gsi no vendor is updated or modified. because gsi's are generic rom with only system image, no other partitions. so flashing a basic rom (especially made for your device) , that will update every partition, and then replacing system by gsi system thats all.

prc.kailas said:
by flashing gsi no vendor is updated or modified. because gsi's are generic rom with only system image, no other partitions. so flashing a basic rom (especially made for your device) , that will update every partition, and then replacing system by gsi system thats all.
Click to expand...
Click to collapse
Thank you, I figured as much as I did a lot of testing trial and error and flashed lots of files yesterday. Got it working booting etc. Unfortunately the ROMs don't support fingerprint scanner out of the box and didn't bother to make it work. Just wanted something stable to use my phone. Thx

hash02 said:
superior-arm64-bvN-userdebug.img with AEX 7.3 works awesome and stable enough.
Click to expand...
Click to collapse
havoc-arm64-bvN-vndklite.img with AEX 7.3 works

hash02 said:
Thank you, I figured as much as I did a lot of testing trial and error and flashed lots of files yesterday. Got it working booting etc. Unfortunately the ROMs don't support fingerprint scanner out of the box and didn't bother to make it work. Just wanted something stable to use my phone. Thx
Click to expand...
Click to collapse
for me AEX 8.1 is awesome, but none of custom support Uhealth with Sp02 sensor. its very usefull at this time.

Question Weird behavior in any custom rom

Hi guys, I'm here looking for any help
I'm having this weird behavior in any custom rom I flash.
A while after flashing some rom (some 2 or 3 cycles of battery, around 1 to 3 days) suddenly all apps start crashing, falling at that force close popup. I mean every app, when I try to launch some new app it goes to the force close immediately.
I can't take a screenshot because it fails, I can't take a screen record because it crashes.
So I have to reboot, and it boots normally, but already happened that some apps loose their cache/data, because they start from zero and I have to log in again.
Happening on any A13 build, I don't remember about A12.
Can that be a hardware issue? I doesn't happen on MIUI.
Tried PE+, LO, CrDroid, ArrowOS, CherishOS, Voltage, Spark... Well, I'm trying it all.
Tried changing recovery: Kewl TWRP, TWRP, OrangeFox
Tried leaving phone on LTE only.
Tried flash fastboot MIUI before other rom.
Flashing all of them like: wipes, install rom, format data.
Does anybody has any idea?
Thanks and sorry about my english!

Leonvrx said:
Hi guys, I'm here looking for any help
I'm having this weird behavior in any custom rom I flash.
A while after flashing some rom (some 2 or 3 cycles of battery, around 1 to 3 days) suddenly all apps start crashing, falling at that force close popup. I mean every app, when I try to launch some new app it goes to the force close immediately.
I can't take a screenshot because it fails, I can't take a screen record because it crashes.
So I have to reboot, and it boots normally, but already happened that some apps loose their cache/data, because they start from zero and I have to log in again.
Happening on any A13 build, I don't remember about A12.
Can that be a hardware issue? I doesn't happen on MIUI.
Tried PE+, LO, CrDroid, ArrowOS, CherishOS, Voltage, Spark... Well, I'm trying it all.
Tried changing recovery: Kewl TWRP, TWRP, OrangeFox
Tried leaving phone on LTE only.
Tried flash fastboot MIUI before other rom.
Flashing all of them like: wipes, install rom, format data.
Does anybody has any idea?
Thanks and sorry about my english!
Click to expand...
Click to collapse
Did you've formated DATA with yes and reboot recovery
Then flashed fw
and last the ROM?
I mean exactly like this?

Laptapper said:
Did you've formated DATA with yes and reboot recovery
Then flashed fw
and last the ROM?
I mean exactly like this?
Click to expand...
Click to collapse
No i've rebooted to the recovery, wiped, installed firmware, installed rom, formated data.
But would this order change anything even to roms that say that don't need any specific firmware?

Leonvrx said:
No i've rebooted to the recovery, wiped, installed firmware, installed rom, formated data.
But would this order change anything even to roms that say that don't need any specific firmware?
Click to expand...
Click to collapse
Wipe isn't enough, formating with yes is necessary.
Try exactly my procedure (fw isn't necessary for all roms / cherishos don't need, Los need)

Some ROMs installation instructions do not require an initial format of data before installation of the ROM itself, like EliteRom. Follow your ROM's installation instructions regarding required firmware. (MIUI)
​

Leonvrx said:
No i've rebooted to the recovery, wiped, installed firmware, installed rom, formated data.
But would this order change anything even to roms that say that don't need any specific firmware?
Click to expand...
Click to collapse
Sheist! said:
Some ROMs installation instructions do not require an initial format of data before installation of the ROM itself, like EliteRom. Follow your ROM's installation instructions regarding required firmware. (MIUI)
​
Click to expand...
Click to collapse
Also elite rom need format data if encrypted (normally data is encrypted!)

Leonvrx said:
No i've rebooted to the recovery, wiped, installed firmware, installed rom, formated data.
But would this order change anything even to roms that say that don't need any specific firmware?
Click to expand...
Click to collapse
If installing the EliteROM (for example), your formatting after installing the ROM is the correct procedure, per the declared instructions:
Installation Instructions:
- Install rom zip using TWRP/OFOX
- Format if you are encrypted, otherwise wipe data is enough
- Reboot
- Enjoy the smoothness+performance

Sheist! said:
If installing the EliteROM (for example), your formatting after installing the ROM is the correct procedure, per the declared instructions:
Installation Instructions:
- Install rom zip using TWRP/OFOX
- Format if you are encrypted, otherwise wipe data is enough
- Reboot
- Enjoy the smoothness+performance
Click to expand...
Click to collapse
@Leonvrx
according my experience it's not important if you format before ROM or after Rom installation but very important to restart recovery when you do it before ROM installation in encryption state.
If decrypted then only wiping data
Please feedback your trying and results.

Laptapper said:
@Leonvrx
according my experience it's not important if you format before ROM or after Rom installation but very important to restart recovery when you do it before ROM installation in encryption state.
If decrypted then only wiping data
Please feedback your trying and results.
Click to expand...
Click to collapse
I didn't know that; thank you for your help, guidance, and patience.
Tried your steps exactly this morning, so far so good, I'll update in the next days, for better or for worse.

@Laptapper
Yeah, same results, it crashed the same (using AlphaDroid atm).
I've rebooted it and it even started initial android setup again, after redoing it, i have all my apps like nothing happened, but my sound settings, fingerprint settings (and probably other too) reseted.
I've also already tried to remove the microSD expation slot, same results,
Tried Vanilla + NikGapps, Vanilla + BitGapps and Gapps builds.
I think it's just bad luck with this specific device :/

Leonvrx said:
@Laptapper
Yeah, same results, it crashed the same (using AlphaDroid atm).
I've rebooted it and it even started initial android setup again, after redoing it, i have all my apps like nothing happened, but my sound settings, fingerprint settings (and probably other too) reseted.
I've also already tried to remove the microSD expation slot, same results,
Tried Vanilla + NikGapps, Vanilla + BitGapps and Gapps builds.
I think it's just bad luck with this specific device :/
Click to expand...
Click to collapse
Which recovery?
Take this:
👍[SHARED] orange fox recovery with decryption for Android 12,13
Update post 9 with android 13 decryption support Here I'm sharing the nearly perfect recovery orange fox with implemented decryption for android 12 ( I've tested only pin protection) The main advantage comparing TWRP is the "beautiful" UI and...
forum.xda-developers.com
Try cherishos with exactly my procedure above. Fw isn't needed!

Laptapper said:
Which recovery?
Take this:
👍[SHARED] orange fox recovery with decryption for Android 12,13
Update post 9 with android 13 decryption support Here I'm sharing the nearly perfect recovery orange fox with implemented decryption for android 12 ( I've tested only pin protection) The main advantage comparing TWRP is the "beautiful" UI and...
forum.xda-developers.com
Try cherishos with exactly my procedure above. Fw isn't needed!
Click to expand...
Click to collapse
I think that it's exactly this version, but I will reflash to make sure and I'll try again

Leonvrx said:
I think that it's exactly this version, but I will reflash to make sure and I'll try again
Click to expand...
Click to collapse
If not working then try this:
In orange fox recovery
format data with manually typing yes
reboot recovery
install cherish gapps rom
format data/yes Again
Start system

Laptapper said:
If not working then try this:
In orange fox recovery
format data with manually typing yes
reboot recovery
install cherish gapps rom
format data/yes Again
Start system
Click to expand...
Click to collapse
Ok, I'll try if happens again. Sometimes it takes 2 or 3 days to happen.
But I have a problem in Cherish that on my bank app (C6 Bank Brazil) my facial recognition doesn't work. It stays on a black screen despite I had given camera permission.

Leonvrx said:
Ok, I'll try if happens again. Sometimes it takes 2 or 3 days to happen.
But I have a problem in Cherish that on my bank app (C6 Bank Brazil) my facial recognition doesn't work. It stays on a black screen despite I had given camera permission.
Click to expand...
Click to collapse
Playstore certified?
Rooted?
Cts matching?

Laptapper said:
Playstore certified?
Rooted?
Cts matching?
Click to expand...
Click to collapse
Non-rooted, CTS profile ok and certified.
It's a thing that just happen in this ROM.
Also this app is really annoying to hide root from, so I never root

Leonvrx said:
Non-rooted, CTS profile ok and certified.
It's a thing that just happen in this ROM.
Also this app is really annoying to hide root from, so I never root
Click to expand...
Click to collapse
Try kernelsu root
Then delete caches of playstore and Google play services.
Reboot
I've got non problems with banking and camera in cherish and kernelsu