All,
I'm attempting to figure out whether something in my flashing process broke down for one Zenfone 8 in particular that results in an unusable LineageOS 18.1 OS. This one particular phone was in a fastboot cycle that would not load the LineageOS Recovery mode or OS until I flashed the `dtbo.img` file. That fixed the fastboot and I was able to then sideload the OS.
However, the OS comes up with a white screen and extreme unresponsiveness. It's unusable. Other phones whereby I followed the same process (but did NOT need to flash `dtbo.img`) are working just fine.
I've run through the flashing process multiple times on the problem phone w/ no luck. Any thoughts appreciated. Should I get the phone back to complete stock and try again?
Flashing Process
-------------------------------
1. Unlock tool APK, unlock, etc.
2. fastboot flash vendor_boot sake_vendor_boot.img
3. fastboot flash boot recovery.img
a. When in fastboot cycle, I then flash `dtbo.img`, but I've only done this on the problematic phone
4. Factory reset
5. Restart, Recovery Mode, Update via ADB
6. adb sideload lineage.zip
chingtastical said:
All,
I'm attempting to figure out whether something in my flashing process broke down for one Zenfone 8 in particular that results in an unusable LineageOS 18.1 OS. This one particular phone was in a fastboot cycle that would not load the LineageOS Recovery mode or OS until I flashed the `dtbo.img` file. That fixed the fastboot and I was able to then sideload the OS.
However, the OS comes up with a white screen and extreme unresponsiveness. It's unusable. Other phones whereby I followed the same process (but did NOT need to flash `dtbo.img`) are working just fine.
I've run through the flashing process multiple times on the problem phone w/ no luck. Any thoughts appreciated. Should I get the phone back to complete stock and try again?
Flashing Process
-------------------------------
1. Unlock tool APK, unlock, etc.
2. fastboot flash vendor_boot sake_vendor_boot.img
3. fastboot flash boot recovery.img
a. When in fastboot cycle, I then flash `dtbo.img`, but I've only done this on the problematic phone
4. Factory reset
5. Restart, Recovery Mode, Update via ADB
6. adb sideload lineage.zip
Click to expand...
Click to collapse
HI
Lineage OS 18.x is based on Android 11 as far as I know so I suggest to install the original ASUS Android 11 raw image and then reinstall the LineageOS using the install instructions from LineageOS.
The raw image for Android 11 on the ASUS Zenfone 8 is available on this Website:
https://www.asus.com/Content/Android-12-Beta/
in the section
How to opt-out and revert back to Android 11
at the end of the page
That's how I reinstall my development Zenfone 8 from 12 to 11 or vice versa.
regards
Bernd
Just wanted to thank you for the information you posted; the re-flash to stock download worked perfectly for what I needed.
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.
Hi,
I have Carbon ROM with Android 10,
I wanted to flash Bliss ROM, and it says that I need a rooted device,
So I've downloaded Magisk and follow the instruction, created a boot.img and flashed it in fastboot, then I did the same only with twrp recovery & Magisk, flashed it and now it is wiered and I'm not sure what is the problem,
I have fastboot BUT when I try to perform any command, it shutsdown and preety useless, I've tried from PC, if I try from MAC, I can boot into twrp but every operation is causing the tablet to reboot.. So I can't even flash a stock ROM,
In PC, the recognized Android device (When in fastboot mode) I update it's driver to Android bootloader device
How can I solve it?
Thanks !!!
I was going crazy with the microphone not working in OOS 11. Tried few things, nothing worked. Even tried installing Lineage OS 18.1. Didn't help. I think there is some problem with the OOS Android 11 system files that are causing this issue. Reverted to OOS 10.3.9 and my microphone is still broken. Ugh. Now the only thing left is to try replacing the microphone part. Ordered new microphone and replaced it myself. Seems like the microphone got wrecked for some reason. New one works fine on Android 11. Anyways, here is the guide.
Download TWRP:
Download the modified TWRP recovery from here. Make sure you download the "fajita". (FYI, I also have attached it below)
[RECOVERY][3.4.0-11][fajita]Official/Unofficial TWRP recovery for OnePlus 6T (Stable)
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com
Download Oxygen OS (one of below):
Download the OOS 10.3.9 Stable from the official website here. You can always update to the Android 11 Stable build using the OTA inside.
https://oxygenos.oneplus.net/OnePlus6TOxygen_34.J.52_OTA_052_all_2103030004_e20debb3eb584411.zip
If you want to switch to the latest Android 11 build directly, grab the latest build using OxygenUpdater App from PlayStore and download a complete build, not an incremental build.
If OxygenOS filename ends with .jar, rename and remove the .jar extension. It should end with .zip.
We will be flashing it twice. Both A/B partitions.
Reboot into bootloader.
Run
Code:
fastboot flash fajita_twrp-3.5.2_11-0_test3.img
You will now be rebooted into TWRP recovery.
Go into Reboot and note down the current slot.
Copy the OxygenOS file to your OP6T internal storage.
Install the OxygenOS file.
After installation is completed, go back to TWRP home.
Go to Reboot and change to the other slot. If it was A before, now change to B.
Reboot to bootloader.
Run
Code:
fastboot flash fajita_twrp-3.5.2_11-0_test3.img
You will now be rebooted into TWRP recovery.
Install the same OxygenOS file again.
After installation is completed, go back to TWRP home.
Reboot to bootloader.
Now to lock the bootloader, run
Code:
fastboot oem lock
Reboot and your device should boot up properly.
You should be good now.
Tried the LOS 18.1 as it is one of few full functional ROMs with likely long security patch support. After realizing the ever changing steps to pass safetynet, I decided to give up and go back to OOS.
The steps outlined here is very helpful to me. The main problem I encountered is the recovery flash command needed for the A/B partition
fastboot flash boot_x fajita_twrp-3.5.2_11-0_test3.img (x=a or b)
Also the second recovery seem to skipped the password/pin prompt which messed up the disk content. I ended up reboot to system and then re-enter the recovery.
After some time I got a second Axon 10 and I spend some time figuring out what was possible with this phone in terms of root, custom ROM etc.
My results are as follows.
What is working:
Android 9 + Magisk and TWRP
Android 9 + TWRP + Custom ROMs (LineageOS 16 and patched GSI)
Android 10 + Magisk and TWRP
Android 10 + Magisk and MicroG flashed via Magisk (= stock ROM without Google Services)
Android 11 + Magisk
What is not working:
Android 11 + Magisk + TWRP (TWRP logo flashes randomly but TWRP does not load).
Android 11 + Magisk + MicroG (the nanolx patching script does not work with Android 11 as of yet)
Encryption in Custom ROMs
Method to flash files via EDL
Unzip / unrar my files into the backup\full folder of the EDL tool and choose restore + full in the tool.
Unlock Bootloader:
Before you try any of the files, you MUST unlock your bootloader!
BACKUP of your data as it will be lost!
Download the EDL tool from this Thread
If your phone is not on android 9, you must go back to Android 9 first. e.g. by using my Android 9 1.9 backup.
After you restored it, restart while holding the volume + key and do a factory reset / format data.
Boot into EDL again and unlock the bootloader.
Now you are on android 9 with unlocked bootloader.
From here you can follow the other guides in the form and install TWRP or lineageos. Or flash one of my files below.
Flashing EDL files:
Unzip / unrar my files into the backup\full folder of the EDL tool and choose restore + full in the tool.
I put all my files into this MEGA account: MEGA
Android 10 version 2.9 Magisk + TWRP
Android 11 version 3.5 stock
Android 11 version 3.5 Magisk
Android 10 version 2.10 stock
Android 10 version 2.10 Magisk (TWRP can be flashed with Magisk)
Install MicroG:
Only works on Android 9 and 10.
Before you install MicroG you must patch the stock ROM to allow for signature spoofing.
The patcher script I used is on https://downloads.nanolx.org/NanoDroid/Stable/ When I write these lines the up-to-date-version is NanoDroid-patcher-23.1.2.20210117.zip
Reboot.
Install MicroG from the Magisk repository.
After a restart there will be error messages that google apps keep crashing. With each warning, disable the apps one by one.
When you reboot again, no errors should appear and MicroG should report that it is fully working.
You can add the Bromite Framework and give F-droid system rights. Both are available from the Magisk repo.
Updates will likely install the Google apps again and uninstall Magisk...
Revive phone:
Not really related, but I bricked my phone several times.
If your phones does not boot anymore or hangs in a bootloop, try accessing the EDL mode.
The easy way:
Boot while holding volume -
The hard way:
Old Volume +, volume - and power until you end up in EDL. The screen will be black, so it helps if you have the Phone connected to Windows and can hear the system sound when the USB sees a connection.
In anyway you can then use the EDL tool to restore / flash an EDL image.
On custom ROM support:
Well there is LineageOS 16 by Unjustified Dev. https://forum.xda-developers.com/t/rom-unofficial-zte-axon-10-pro-9-lineageos-16-0.3992127/ It works well. But has a patch level that is outdated by now.
On top of it you can install the GSI ROMs created by Rafyvitto. The latest one is Resurrection Remix https://forum.xda-developers.com/t/...nofficial-resurrection-remix-q-8-6-7.4172527/
with a security patch level of mid 2021. Which is recent enough to use. The stock roms are not much better.
With both Custom ROMs, encryption is not working which poses a privacy/security risk when your phone is stolen. Do not forget that your phone does not only contain your photos and data but also your passwords to your accounts.
Added Android 10 2.10 files.
Its nice to see anything new for this phone. I wish I can use these roms but I have the American version.
Hi and thanks for your work and your files.
I'm stuck on "Loading the programmer: prog_ufs_firehose_sdm855.elf >>>", if I try to recover your edl files with EDL Tool, v 3.25.
I have to choose option 2: "Restore Full EDL from backup", right?
Is there a way to check if the bootlaoder is really unlocked?
Thanks in advance
OK, I was able to solve the problem with the "programmer" and try the backups. The next step was almost clear. The device is stuck in bootloop. I've already tried all the backups I could find on Mega. After the EDL Tool has done its work and the device has restarted, the mobile phone goes into the boot loop. And now? So the starting position was: Android 9 with an open bootloader. Maybe someone has an idea?
After I couldn't get the device out of the bootloop, I flashed the A2020G_PRO_V1.6_FULL_EDL via MiFlash and then did an OTA update to 1.8.
Then I tried unlocking the bootloader again, which unfortunately didn't work. The flash is carried out without errors, but the device then apparently does not start in the desired Fastboot mode.
Thanks for your guide. However am I missing something with the Android 11+Magisk installation? I restored all the correct files and everything flashed correctly, however upon reboot there is no Magisk installed anywhere. Did a factory reset after the flash and still not there. Tried installing Magisk via his github and tried patching the boot.img again and it says success but after rebooting it says Magisk is not installed.
brian117 said:
Thanks for your guide. However am I missing something with the Android 11+Magisk installation? I restored all the correct files and everything flashed correctly, however upon reboot there is no Magisk installed anywhere. Did a factory reset after the flash and still not there. Tried installing Magisk via his github and tried patching the boot.img again and it says success but after rebooting it says Magisk is not installed.
Click to expand...
Click to collapse
Maybe you need to switch the slot in TWRP. It sounds as if you install it to the other slot (like A) an then boot B. Or vice versa.
Hello,
This won't work for some reason. I flash spesn_global_images_V13.0.5.0.SGKMIXM_20221020.0000.00_12.0_global with fastboot.
Then I boot TWRP with fastboot boot twrp.img. I then install xiaomi.eu_multi_HMNote11_V13.0.5.0.SGKMIXM_v13-12.zip in twrp.
But then it just keeps booting to recovery.
Did anybody try this or have tips?
Thanks.
I don't remember exactly what I did, but I think I flashed the fastboot version and then updated
Be sure to get the version of recovery for the android version you want to flash. Or that was the case back then.
Be sure to format /data as well, not just wipe
Okay, I got it working like this:
1. Flash xiaomi.eu_multi_HMNote11_V13.0.10.0.RGKMIXM_v13-11-fastboot
2. Fastboot boot into OrangeFox-R11.1_A12.1-Unofficial-spes
3. Push xiaomi.eu_multi_HMNote11_V13.0.5.0.SGKMIXM_v13-12.zip via adb to /data/
4. reboot to bootloader
5. fastboot boot into twrp-3.6.1_11-0-spes
6. install xiaomi.eu_multi_HMNote11_V13.0.5.0.SGKMIXM_v13-12.zip and format data
7. reboot
Very annoying it doesn't work by just flashing the xiaomi eu zip on anything.
Strange, I got mine working first time flashing using TWRP 3.6.1
A bit of a messy procedure is required because of several technical changes from Android 11 to Android 12.
Plus, Xiaomi's messy encryption makes things worse.
Use TWRP 3.7.0