Related
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.
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?
Hi togehter,
I had some problems with flashing new custom roms and ended up in a bootloop with not being able to boot to recovery. This could be solved by flashing the stock image with the xiaomi flash tool.
Before I will fu up again I would like to bring some light into the darkness.
When coming from Stock Rom:
1. Unlock Bootloader -> done successfully
2. Flashed TWRP Recovery -> done successfully but storage (data) was encrypted
3. Flashed Magisk via Recovery -> done successfully (storage still encrypted)
from here I was happy using the Stock Rom with Root.
Now I started messing things up:
Because there are a few things that bother me about the stock rom i wanted to use lineageOS/Pixel Experience. So I proceeded as following:
1. Backup my data (still have to enter key when starting twrp to decrypt the storage) -> done successfully
2. Flash LineageOS -> resulted in bootloop to TWRP
When entering twrp there was no query about the key and data where encrypted. Also the Backup was not accessible .
3. I used all in one tool to erase storage and decrypt data. -> successfully... Now i was able to place data on the internal storage again and start flashing a rom
4. Flashing LineageOS -> done successfully and able to boot into rom
Back to TWRP data was encrypted and I had to enter key.
5. Flashing remove force encryption script via twrp. -> done but now i was facing boot to black screen. TWRP was not working anymore.
Only way to get it work again, was flashing stock image.
Why is the data system always encrypted. This is rly annoying and backups don't work, because i can not encrypt them. Also, I can not put any files on the memory because it is encrypted.
I would rly like to try a custom rom, but I would also like to be able to go back to a backup. What have i done wrong?
You have to flash no dm verify right after formatting data & flashing rom. Don't let it boot.
I would recommend using the stock firmware. Los/AOSP is rubbish for our device, it's too unstable, lacking features and has worse gestures.
SeppGoPro said:
Hi togehter,
.... What have i done wrong?
Click to expand...
Click to collapse
You need to format data (not just wipe data) in TWRP. Some people suggest before flashing a ROM and some say after, but I don't think it makes a great deal of difference either way.
Make sure you either flash the appropriate firmware and vendor recommended, or the fastboot ROM of that version.
Then in TWRP wipe cache and dalvik, then format data.
Reboot into TWRP, or unmount and mount the data partition in TWRP so it correctly reads the data partition.
Copy across the ROM (and GApps if needed)
Them flash.
Boot into the ROM and you should be good.
After initial setup, if you want root, boot into TWRP and flash Magisk.
From here, if you've set a pin on the ROM, you'll be encrypted, but everything should still work normally. You should be able to access everything normally in TWRP and also perform backups. You should be able to got data across from/to a PC normally.
Turbine1991 said:
You have to flash no dm verify right after formatting data & flashing rom. Don't let it boot.
I would recommend using the stock firmware. Los/AOSP is rubbish for our device, it's too unstable, lacking features and has worse gestures.
Click to expand...
Click to collapse
Not true in many ways.
There is need to flash no dm verity. It's one way of solving the issue, but it's not the only way. You should only do this if you know what it's for and if you know you want this.
AOSP ROMs are not unstable. I've been using them on mine for over 4 months. None are perfect and they have a few minor issues/bugs, but they are far from being considered unstable. I've never had shutdowns, reboots or FC'S.
Thanks for the replies.
Robbo.5000 said:
Make sure you either flash the appropriate firmware and vendor recommended, or the fastboot ROM of that version.
Click to expand...
Click to collapse
So for example with LineageOS 17 I can use the global vendor and firmware, but sometimes in the thread it is recommended to use chinese vendor and firmware. In this case I should flash another vendor and firmware then the global one.
What do you mean with a fastboot rom. How can I identify one of them?
Is the MiuiMix Rom a fastboot rom. This one changed my vendor and firmware. After flashing this rom, my bootlogo changed to redmi... Am i right with this suggestion?
SeppGoPro said:
Thanks for the replies.
So for example with LineageOS 17 I can use the global vendor and firmware, but sometimes in the thread it is recommended to use chinese vendor and firmware. In this case I should flash another vendor and firmware then the global one.
What do you mean with a fastboot rom. How can I identify one of them?
Is the MiuiMix Rom a fastboot rom. This one changed my vendor and firmware. After flashing this rom, my bootlogo changed to redmi... Am i right with this suggestion?
Click to expand...
Click to collapse
Fastboot ROMs are official ROMs that are flashed through the Mi Flash Tool
, with the phone booted into fastboot mode and connected to the PC. They contains almost all partitions, including vendor and all firmware. They will be a .tgz file. They are mainly used as an almost failsafe way to recover the phone, should you mess things up. Flashing them will restore the phone to factory, so will lose TWRP, but you're guaranteed a clean starting point.
If, for example, you want to install Havoc 3, it is recommended to flash it on top of either China or India 10.4 vendor and firmware. So if you're phone is currently on global firmware, you would then need to flash, say, Chinese firmware and vendor flies, before flashing Havoc.
If you have been previously flashing other mods, such as 75Hz, screen refresh rate, for example, then you might choose to flash the official Chinese fastboot ROM, instead of just the firmware and vendor, to ensure that you've cleaned the phone of any mods, etc. In most cases you will be fine flashing firmware and vendor, though.
Miuimix is a custom ROM, which is based on the official China MIUI ROM. Because it's based on the China ROM this is why the logo changed to Redmi.
Robbo.5000 said:
Miuimix is a custom ROM, which is based on the official China MIUI ROM. Because it's based on the China ROM this is why the logo changed to Redmi.
Click to expand...
Click to collapse
So in this case, i can just flash this rom and there is no need of flashing a diffrent vendor or firmware.
So final question: I'm happy with the stock rom plus root. I would like to try a custom rom but I'm not willing to go through the whole installtion procedure again. Is there a way of making a backup and keeping it?
When I backup the stock rom right now, the backup will ne encrypted again...When I formate the data, all my data will be gone again ?
I have TWRP on my Mi 9T Pro but whenever I try to boot into a new rom it just boots back into TWRP, I think it's because I accidentally wiped everything including my kernel, but I'm not entirely sure, there's no errors when I try to install one, I've tried multiple, my phone doesn't have an OS installed ATM, no MiUI, I've tried flashing stock rom but that also doesn't work. I really don't know what to do.
sternje said:
I have TWRP on my Mi 9T Pro but whenever I try to boot into a new rom it just boots back into TWRP, I think it's because I accidentally wiped everything including my kernel, but I'm not entirely sure, there's no errors when I try to install one, I've tried multiple, my phone doesn't have an OS installed ATM, no MiUI, I've tried flashing stock rom but that also doesn't work. I really don't know what to do.
Click to expand...
Click to collapse
Restore MIUI by flashing a MIUI fastboot ROM.
Get the fastboot ROM from here
https://xiaomifirmwareupdater.com/miui/raphael/
Choose the fastboot ROM for the phone you have (European or Global). Make sure it is a fastboot ROM, not a recovery ROM.
Use this guide to flash it
https://c.mi.com/oc/miuidownload/detail?guide=2
View the page in desktop mode if viewing on a phone.
In step 5 make sure you change flash option to 'clean all' before hitting flash. This is three radio button options at the bottom of the flash tool. The default locks the bootloader, so you need to change it to keep the bootloader unlocked.
After doing this boot into MIUI at least once before trying to install something again.
When flashing a custom ROM over MIUI you need to format data in TWRP.
After installing TWRP, boot into it a do the following.
Perform a factory reset.
Format data - make sure you format, not wipe, need to type 'yes' to confirm.
Reboot back into TWRP - this makes sure the data partition is properly mounted after formatting.
Now flash the ROM you want and GApps if needed.
Reboot to system and it should be good.
Flash Magisk if needed.
Do not wipe anything else in TWRP. It's not needed.
sternje said:
I have TWRP on my Mi 9T Pro but whenever I try to boot into a new rom it just boots back into TWRP, I think it's because I accidentally wiped everything including my kernel, but I'm not entirely sure, there's no errors when I try to install one, I've tried multiple, my phone doesn't have an OS installed ATM, no MiUI, I've tried flashing stock rom but that also doesn't work. I really don't know what to do.
Click to expand...
Click to collapse
First Learn Basics while messing with your device.
Kernel is a part of ROM's Zip,
So even if you wiped kernel(so called boot), it will again gets re flashed with new ROM.
Second your problem is,
You are booting into wrong partition.
I am not sure , what you did.
But Mi9TPro has two partitions, Google's new A/B partition table for Android.
And you may have wiped both Flashed A(example) and booting into B.
Therefore it is not booting properly.
Ask in Telegram group for faster solution.
Or wait here for better solution in reply.
OR
Simply flash Fastboot,
And then try everything again.
Ans from next time, read everything step carefully and then proceed.
Sent from my Redmi K20 Pro using Tapatalk
itspdp said:
First Learn Basics while messing with your device.
Kernel is a part of ROM's Zip,
So even if you wiped kernel(so called boot), it will again gets re flashed with new ROM.
Second your problem is,
You are booting into wrong partition.
I am not sure , what you did.
But Mi9TPro has two partitions, Google's new A/B partition table for Android.
And you may have wiped both Flashed A(example) and booting into B.
Therefore it is not booting properly.
Ask in Telegram group for faster solution.
Or wait here for better solution in reply.
OR
Simply flash Fastboot,
And then try everything again.
Ans from next time, read everything step carefully and then proceed.
Click to expand...
Click to collapse
This phone does not have A/B partitions.
Robbo.5000 said:
This phone does not have A/B partitions.
Click to expand...
Click to collapse
It has, but you can't see then normally in twrp.
Ask in telegram group for fast solution.
And please do read about android partition tables feom android oreo.
Sent from my Redmi K20 Pro using Tapatalk
itspdp said:
It has, but you can't see then normally in twrp.
Ask in telegram group for fast solution.
And please do read about android partition tables feom android oreo.
Click to expand...
Click to collapse
It's an A only, system as root device. It is not an A/B device.
This is why MIUI updates need to be installed in system recovery. It does not install updates when the system is live.
if it's booting back into twrp. It's usually one of the three mistakes.
1. wrong vendor
2. didnt flash dfe
3. flashed dfe for stock rom
4. encrypted, so format data partition.
you can follow the guide: https://forum.xda-developers.com/k20-pro/how-to/simple-beginners-guide-to-raphaelin-t4020543
also, k20p is A partition only, not dual.
kernel is included with rom.
ask in telegram group for faster replies.
Sandeeep Kiran said:
if it's booting back into twrp. It's usually one of the three mistakes.
1. wrong vendor
2. didnt flash dfe
3. flashed dfe for stock rom
4. encrypted, so format data partition.
you can follow the guide: https://forum.xda-developers.com/k20-pro/how-to/simple-beginners-guide-to-raphaelin-t4020543
also, k20p is A partition only, not dual.
ask in telegram group for faster replies.
Click to expand...
Click to collapse
You don't need to flash dfe. I've not yet come across a situation where it is required. Flashing dfe will make life easier, at the cost of greatly reduced security, but there are always options to do what you want without flashing dfe.
Robbo.5000 said:
You don't need to flash dfe. I've not yet come across a situation where it is required. Flashing dfe will make life easier, at the cost of greatly reduced security, but there are always options to do what you want without flashing dfe.
Click to expand...
Click to collapse
It's required for oss based builds now.
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.