Database Develop

[GUIDE] [F.A.Q.] [chef] [TREBLE] Common Hurdles and Solutions for First Timers!

This thread is meant to address all the common hurdles that are commonly faced by people who are new to treble devices (chef to be specific) and help them to troubleshoot/avoid some small yet critical steps during flashing new ROMs and working with fastboot and recovery in general. It will be continually updated with new stuff as it goes along.
I will be referring to the Motorola One Power and Moto P30 Note as chef only from now on.
The unlocking guide is available in This XDA Thread!
IMPORTANT:
1. Flashing refers to the process of doing a clean flash, with the inclusion of fastboot -w command
2. Latest ADB and Fastboot drivers are required to be installed, else the installation may halt mid-way.
3. Stock ROM refers to the Android One ROM for the Motorola One Power [XT 1942-2]
IMPORTANT: AS OF RIGHT NOW, PEOPLE WHO HAVE INSTALLED STOCK PIE (EITHER VIA UPDATE OR FIRMWARE) WILL NOT BE ABLE TO USE ANY OTHER ROM OTHER THAN THE STOCK PIE ROM. RADIO INTERFACE LAYER IS BROKEN IN OREO SOURCE BUILT ROMS AND THAT CURRENTLY INCLUDES LINEAGE 16 SO PLEASE WAIT FOR PIE SOURCE CODE FROM MOTOROLA FOR THAT TO BE FIXED.
1. I unlocked my chef . How do I flash TWRP in place of the stock recovery?
Solution:Currently you cannot as there is no recovery partition in the device. You have to manually boot TWRP onto the device using fastboot to use it. Follow as directed:
Boot the device into fastboot mode
Use command fastboot boot <path/to/TWRP.img> to boot TWRP temporarily.
2. I am done with TWRP and I want to flash Lineage OS 16 on my chef. I simply flash the .zip archive right?
Solution:No. Before you flash anything,
Take a backup of atleast your EFS and PERSIST partitions using TWRP and off-load it for safekeeping to restore in future if needed. You can also trigger a full backup if you require.
SUPER IMPORTANT: Flash this .zip file to copy the System A/B partitions. If this step is skipped, you will be responsible to brick your own device. THIS STEP IS ONLY REQUIRED ONCE AND ONLY ONCE IN THE LIFETIME OF YOUR DEVICE! YOU WON'T BE NEEDING THIS THE NEXT TIME YOU FLASH ANY ROM. .
After that, flash your dearest custom ROM and get going.
For Lineage OS 16, follow This XDA Thread.​
3. I am done testing LOS 16, I want to flash a GSI. Shall I use a stock Vendor Image for the GSI on my chef?
Solution:No. The stock Vendor image is causing bootloop issue in most GSIs. It is recommended to use Lineage OS Vendor to flash a GSI on chef. So flash LOS and then flash your favourite GSI.
Also, Super Important: for those who haven't used lineage before flahing a GSI, it is required to boot Lineage OS first before flashing a GSI. ​
4. I am done experimenting, I want to go back to the stock image. How do I proceed?
Solution:Follow this XDA thread for it. And don't install OTA updates directly from the device. It will come in the next step.​
5. I want to install OTA updates on the stock ROM. How do I proceed?
Solution:Follow this XDA post for it. The installation process is described here. You have to be clever enough to get the appropriate OTA update. ​
Credits:
@erfanoabdi : TWRP, LOS 16, AB partition management
@rushiranpise : Unlocking guide
@dayask : Testing the process, guide for reflashing stock ROM
@nageen9211 : Testing ROMs
For any additional queries, feel free to contact us at our Telegram Group
For more regular updates, follow our Telegram Channel
Always remember: You have to be smarter than your smartphone to be able to use it!
Cheers and Happy Flashing!​

Note to readers
The above guide is for stock kernels only (including lineage)
The custom Darkone Kernel has constant updates and fixes major bugs often. Please follow the linked thread to test it out if you want to. Cheers!

Anyone have flashed GSI ROM? FOr me after flash GSI HavocOS have bootloop :/

DIdn't flash copy system A/B partitions, stuck on bootloop with custom roms.
Watched some youtube videos and didn't read this post before flashing custom ROM. Flashed Custom ROM without flashing A/B partitions. Now I have a phone stuck on bootloop when done anything in TWRP. or I can use my phone with stock ROM installed by fastboot method.
Installing or restoring anything from TWRP results in boot loop.
Restoring the backup I made before flashing, completes the restoration process normally. But when rebooting to system, TWRP prompts me that no OS is installed. If I reboot anyway, its either stuck on bootloop or reboots to recovery and asks me to try again or factory reset, or boots into bootloader mode.
Installing custom ROM begins with Step 1, takes a bit time and starts step 2 and shows completed. Doesn't echos any comments. But when i reboot, same prompt shows saying no OS installed. Reboot anyway and stuck on bootloop or reboots to recovery and aks me to try again or factory reset, or boots into bootloader mode.
Now I installed stock ROM with fastboot method and phone is boots up into system just fine.
Sometimes TWRP can't mount anything.
So am I stuck with stock rom or is there any solutions?
Also, installing stock ROM with fastboot mode showed this error in between scripts
(bootloader) is-logical:xxx_a: not found
and
(bootloader) is-logical:xxx_b: not found
but is able to use the phone just fine with stock ROM.

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.

Xiaomi mi 8 se global/eu rom

Hi guys, I'm new here. I haven't been playing with custom roms for a while now but I have xiaomi mi 8 se for which I would like to set up a custom global/eu rom. I read a lot of posts here and tried to do it but without access. First I applied to unlock my device via Xiaomi procedure, waited X hours and then went to download and install rom from here: https://mifirm.net/model/sirius.ttt#global
That's when I realized that I have to find fastboot rom for this way of flashing and there isn't one for global or eu version. After a bit more reasearch I decided to do it on my own with TWRP (just found out how that works). So I downloaded one from here: https://mifirm.net/model/sirius.ttt#twrp and after some time (and a lot of small steps I learned along the way) I got it installed.
Then I downloaded non fastboot EU rom and tried to flash it through recovery(twrp). Problem here is that the whole recovery is in chinese so I had to watch other people videos and compare location of buttons so I'm not sure I pressed everything correct. After "flashing" phone stuck in fastboot boot loop. Here I panicked I bricked the phone and downloaded "normal" chinese rom with fastboot and flashed that MIU flash tool. This went well so now I have factory reset phone with the same/similar rom I had before. I know this is an old device and probably there isn't some easy solution but I would love to hear if someone with more experience can give me some advice how to correctly flash eu rom (non fastboot). Also is there some version of twrp that isn't chinese and it would be perfect if I can flash twrp with fastboot (if thats possible).

For recovery: Link
Recommend to factory reset from TWRP before flashing any ROM. And speaking of custom ROM, can I recommend to you the Pixel Experience? It's the most solid ROM right now. If you are interested, you can try out.

Hello NesaiOmachi, thank you very much for your advice. Pixel experience looks great, my only prerequisite is that it has google play services support so will definitely check it out. I found this page with ROM downloads, can you please also point me which version to choose and which twrp (from your url) is compatible with it?
I assume I have to install twrp with ADB tools from my PC (already have that setup up), then I enter TWRP and do something like this: https://nerdschalk.com/how-to-install-a-custom-rom-using-twrp-recovery/
EDIT: just saw there are instructions at pixel experience site, awesome! Ignore my message, will try with latest twrp and latest pixel rom and see how it goes

Question HELP I bricked my phone - Stuck on fastboot loop

So I really new into this, I didn't really know what I was doing but i tried to install Pixel Experience on my device. After some struggle it seems that I managed to flash the rom into system. I followed the instruccions to the part where you wipe all data from the phone, but then it got stucked and didn't start the OS, maybe system got corrupted or something bc when I try to reinstall the rom cmd tells me "This partition doesn't exists".
As far as i know there isn't a version of twrp for Redmi note 10 5g so all I have is Xiaomi ADB Fastboot Tools. Pls help me.

What firmware do you want to install？
Can you elaborate on your installation process, guide instructions and firmware sources?

1:
Do not need to use twrp, general Fastboot command to brush the GSI on the line, after installation to play some black screen patch and settings.
GSI always jumps to Fastboot and Recovery after booting, indicating that there is a problem with GSI, replace it with another variant or downgrade version.
2:
Fastboot Method
https://c.mi.com/thread-1857937-1-0.html

jianjianus said:
What firmware do you want to install？
Can you elaborate on your installation process, guide instructions and firmware sources?
Click to expand...
Click to collapse
Correct me if im wrong. I tried to install a GSI of Pixel Experience from this pinned tutorial on the board.
Fire1511 said:
Code:
I am NOT responsible for bricked devices, destroyed SD cards or any
damage that may happen to your device.
Requirements:
Unlocked bootloader.
WARNING​Don't use Nippon gsi they aren't working,I recommend using phh gsi by @phhusson lineage os by @AndyYan and PE 12 by @ponces
How to guide:
power + volume down button
fastboot reboot fastboot
install fastbootd drivers,follow this tutorial
fastboot set_active a
fastboot erase system
fastboot flash system (name gsi.img)
fastboot --disable-verity --disable-verification flash vbmeta (vbmeta.img)
fastboot flash vbmeta_b (vbmeta.img)
fastboot set_active a
fastboot reboot recovery
in recovery select wipe data
reboot to system
The GSI will be installed in your phone
Bugs:
Brightness slider but you can fix it
Recommended rom:
Pixel experience:
Releases · ponces/treble_build_pe
Script and patches for building PHH-Treble Pixel Experience - ponces/treble_build_pe
github.com
Select arm64 ab variant
How to fix brightness slider:
Go to phh treble settings,misc settings enable "use alternative brightness scale", "use linear screen brightness slider" and "allow setting brightness to the lowest possible",reboot the device
There is an better alternative to fix this annoying bug,follow this guide!
[GSI] Brightness Fix & Other Fixes
Brightness black lockscreen fixed & Brightness Slider fix. GSI Misc Settings ✅Use Linear Brightness Scale ✅Force Alternatice Backlight Scale ✅Allow Settings to the lowest Flash this file on magisk and reboot :) Note: There's a better fix...
forum.xda-developers.com
How to fix bluetooth audio:
Go to phh treble settings,misc settings, "Force enable a2dp off-load" and "Bluetooth workarounds" select mediatek option and reboot the device.
How to install magisk on your device:
ROOT GAINED !!!!
THIS METHOD WORKS on both: POCO M3 Pro / Redmi Note 10 5G hey guys.. wonderful news.. been trying here and there and IT WORKS FINALLY i gained root of POCO m3 Pro 5G ! i'll write in steps how it works and post all files i've been using...
forum.xda-developers.com
How to flash gapps:
You need magisk on your phone
Download this file then flash from magisk
MagiskGApps - Browse /r/Stock at SourceForge.net
GApps for Magisk
sourceforge.net
Click to expand...
Click to collapse
My process was a total mess bc I didn't knew my device had 2 partitions in system and the post didn't clarify that, so I found this other tutorial (
). Everything went smoothly, the installation was completed and I wiped all data, rebooted to system, and got stuck on a loop of the Redmi logo. I assumed something gone wrong and I tried to go fastboot again and when i try to install the image sends me the error "This partition doesn't exists".
I don't have the precise commands on cmd I wrote bc i restarted my pc. Sorry.
The source Pixel Experience Plus v415.1 arm64 ab

chileangarbage said:
The source Pixel Experience Plus v415.1 arm64 ab
Click to expand...
Click to collapse
Some people have given feedback that this phenomenon occurs with v415.
I tried it and this problem also appeared. They said that dropping down to V414 would not cause this problem.
I don't know if the latest version has a fix?
I have not tried this firmware again and am currently using lineageos19.1
Andy Yan's personal builds // GSI - Browse Files at SourceForge.net
sourceforge.net

Pixel Experience Plus v415.1 is also reported not to work on MediaTek devices. v414 is the latest working version.

chileangarbage said:
Correct me if im wrong. I tried to install a GSI of Pixel Experience from this pinned tutorial on the board.
My process was a total mess bc I didn't knew my device had 2 partitions in system and the post didn't clarify that, so I found this other tutorial (
). Everything went smoothly, the installation was completed and I wiped all data, rebooted to system, and got stuck on a loop of the Redmi logo. I assumed something gone wrong and I tried to go fastboot again and when i try to install the image sends me the error "This partition doesn't exists".
I don't have the precise commands on cmd I wrote bc i restarted my pc. Sorry.
The source Pixel Experience Plus v415.1 arm64 ab
Click to expand...
Click to collapse
chileangarbage said:
Correct me if im wrong. I tried to install a GSI of Pixel Experience from this pinned tutorial on the board.
My process was a total mess bc I didn't knew my device had 2 partitions in system and the post didn't clarify that, so I found this other tutorial (
). Everything went smoothly, the installation was completed and I wiped all data, rebooted to system, and got stuck on a loop of the Redmi logo. I assumed something gone wrong and I tried to go fastboot again and when i try to install the image sends me the error "This partition doesn't exists".
I don't have the precise commands on cmd I wrote bc i restarted my pc. Sorry.
The source Pixel Experience Plus v415.1 arm64 ab
Click to expand...
Click to collapse
This tutorial works. But not ABSOLUTELY. I did get stucked on bootloader ever after flashing 3 different images. I think that problem was caused because versions of bootloader in my original ROM and installed GSI image didn't match(I was trying to flash latest Android version but my original ROM was Android 11). So I tried flashing the GSI image with Android version 11 and that worked. Therefore, I wanna say that just don't worry just keep flashing and you'll see the Love One.

How to flash ASOP based ROMs?

Hi
A few months ago I was able to flash on angelica lineage-17.1-20210326-UNOFFICIAL-angelica.zip and this worked well. Yesterday I tried to flash the s same image again and after several attempts I get a black backlit screen when lineage is meant to start. I reflash stock _V12.0.10.0.QCRMIXM then a recovery - PBRP 3.0.1. From there I was having issue
What is the flashing process for an unlocked device that has something like TWRP/Pitch Back/Orange Fox installed?
I guess once you unlock and can flash the recover you use the recover to flash the zip, then reboot and flash magisk.zip and everything should work? Or is there some step missing.

I had this problem too with the google pixel 7 pro. Can't help ya there on that one. I even tried re installing older firmware and it still didn't work. Maybe the bootloader is permanetly downgradable but the firmware of the stock is. Just a guess. Lineage os 20 is an unofficial build at the moment that receives hardly any updates.