Question How to install AospExtended-v9.1-I006D-OFFICIAL-20220510-1943.zip - ASUS ZenFone 8

Hi
When installing the new image
AospExtended-v9.1-I006D-OFFICIAL-20220510-1943.zip
I get again a ramdump error when I try to boot the Zenfone 8 after the installation -- just like when installing the previous release from march. After installing the image the Zenfone does not boot anymore -- not from any of the slots and also not into the recovery mode. The only thing that still works is booting into fastboot mode and I must reinstall the phone from scratch using the raw image for Android 11.
So I seems to be doing something wrong ... what is the correct process to install this image?
I tried installing the image using the recovery from Aospextended 9.0 and also using the recovery from Lineage 18.1 and Lineage 19.1 --nothing worked. Using OTA to install the image does also not work.
The only Aospextended image I was able to install successfully was the first Image from February:
That image could be installed via sideload using the recovery image of Lineage 18.1
Any help is appreciated.
regards
Bernd.

From what I've experienced; the ramdump issue seems to happen when trying to boot into an OS/Recovery that is calling for a different firmware version than what is on your current device.
For example:
- My Zenfone 8 is running Lineage 19, which requires the Android 12 firmware.
- If I flashed Lineage 18, which requires Android 11 firmware, I get ramdump, until I flash the proper firmware.
The links below are from the Asus' website.
Here is the official Android 11 Image = https://www.asus.com/Content/Android-12-Beta/
Here is the official Android 12 Image = https://www.asus.com/Content/Android-13-Beta/

DaemonDant said:
From what I've experienced; the ramdump issue seems to happen when trying to boot into an OS/Recovery that is calling for a different firmware version than what is on your current device.
For example:
- My Zenfone 8 is running Lineage 19, which requires the Android 12 firmware.
- If I flashed Lineage 18, which requires Android 11 firmware, I get ramdump, until I flash the proper firmware.
The links below are from the Asus' website.
Here is the official Android 11 Image = https://www.asus.com/Content/Android-12-Beta/
Here is the official Android 12 Image = https://www.asus.com/Content/Android-13-Beta/
Click to expand...
Click to collapse
Thanks for the hint -- I got the same error while first installing AospExtended . Therefor now I always first install the original Android 12 image from ASUS and then the AospExteneded. That approach does work for the first version of AospExtended on the ASUS Zenfone ( I did that now more then one time...)
But it does not work with AospExtended images from March and May .
regards
Bernd

DaemonDant said:
From what I've experienced; the ramdump issue seems to happen when trying to boot into an OS/Recovery that is calling for a different firmware version than what is on your current device.
For example:
- My Zenfone 8 is running Lineage 19, which requires the Android 12 firmware.
- If I flashed Lineage 18, which requires Android 11 firmware, I get ramdump, until I flash the proper firmware.
The links below are from the Asus' website.
Here is the official Android 11 Image = https://www.asus.com/Content/Android-12-Beta/
Here is the official Android 12 Image = https://www.asus.com/Content/Android-13-Beta/
Click to expand...
Click to collapse
Hi again
I have now managed the installation using this procedure:
- Install the raw image of the original Android 12 for the device (from the links in your message)
- install the vendor_boot image and the boot/recovery image from LineageOS 18
- install AospExtended 9.x via sideload from within the recovery
Lessions learned are:
installing the a raw image of the original Android 11 and updating to the original Android 12 is different to installing a raw image of Android 12.
Thanks again for the hint -- now I only wait for a AospExtended 9.1 image without GAPPS
regards
Bernd

Related

LIneage OS OTA needs new firmware

Hello.
I have installed Lineage OS 15.1-20180806-NIGHTLY-cheeseburger a few days ago on my Oneplus 5. Yesterday I got an OTA and by the system I was told that it will automatically boot into recovery and try to install itself or I have to install it manually if there is no compatible recovery.
When it booted into recovery there was an error:
This package requires firmware version 5.1.4 or newer. Please upgrade firmware and retry.
Updater process ended with ERROR 7
How can I install new firmware? The only link I have found is https://forum.xda-developers.com/oneplus-5/how-to/firmware-modem-collection-flashable-zips-t3627049 where is firmware with Oxygen OS.
Where can I fin firmware for Lineage OS? I am little bit confused with what actually firmware is...
OS: Lineage OS 15.1-20180806-NIGHTLY-cheeseburger
Phone: ONEPLUS A5000
Android version: 8.1.0
Recovery: TWRP 3.2.1-1
Thank you.
hazard16 said:
Hello.
I have installed Lineage OS 15.1-20180806-NIGHTLY-cheeseburger a few days ago on my Oneplus 5. Yesterday I got an OTA and by the system I was told that it will automatically boot into recovery and try to install itself or I have to install it manually if there is no compatible recovery.
When it booted into recovery there was an error:
This package requires firmware version 5.1.4 or newer. Please upgrade firmware and retry.
Updater process ended with ERROR 7
How can I install new firmware? The only link I have found is https://forum.xda-developers.com/oneplus-5/how-to/firmware-modem-collection-flashable-zips-t3627049 where is firmware with Oxygen OS.
Where can I fin firmware for Lineage OS? I am little bit confused with what actually firmware is...
OS: Lineage OS 15.1-20180806-NIGHTLY-cheeseburger
Phone: ONEPLUS A5000
Android version: 8.1.0
Recovery: TWRP 3.2.1-1
Thank you.
Click to expand...
Click to collapse
Flash OxygenOS 5.1.4 then you have the new firmware. afterwards you can proceed with LineageOS.
strongst said:
Flash OxygenOS 5.1.4 then you have the new firmware. afterwards you can proceed with LineageOS.
Click to expand...
Click to collapse
Does OxygenOS 5.1.4 only contain firmware without main OS? Because the filesize of that zip is only about 60MB. Will it wipe my actual OS? Which zip should I pick from the list provided on mentioned link? There are several OOS OBs. What does it mean?
Thanks
hazard16 said:
Does OxygenOS 5.1.4 only contain firmware without main OS? Because the filesize of that zip is only about 60MB. Will it wipe my actual OS? Which zip should I pick from the list provided on mentioned link? There are several OOS OBs. What does it mean?
Thanks
Click to expand...
Click to collapse
That's only the firmware, no rom included as mentioned. Full modem and firmware is around 1.7GB.
This is the one you're looking for https://forum.xda-developers.com/on...llection-flashable-zips-t3627049/post77185007
It should not wipe your os, but make backups as usual.
As it was already said, it is useless to flash whole OOS. You just need to flash given firmware and after reboot you should be able to upgrade LOS.
strongst said:
That's only the firmware, no rom included as mentioned. Full modem and firmware is around 1.7GB.
This is the one you're looking for https://forum.xda-developers.com/on...llection-flashable-zips-t3627049/post77185007
It should not wipe your os, but make backups as usual.
Click to expand...
Click to collapse
Thanks, it solved my problem.
This is where I got for Firmware and Modem ONLY packages, https://forum.xda-developers.com/showpost.php?p=76943628&postcount=8.

Am I doing something wrong (attempting to downgrading to Android 10)?

I am trying to fix a boot loop problem after installing a problematic Magisk Module, and I am stuck. After multiple efforts to try to undo the problem in Android 11, I believe I need to downgrade first to then boot into Magisk Core-Only mode to uninstall the module. The problem is I can't downgrade. I have tried to install the latest build for Pixel 4 XL on both Android 11 DP4 and 11 Beta, and I always get a boot loop. I used flash-all and Android Flash Tool and still get a bootloop. I switch the active partition and flash Android 10 there, nothing. Can anyone help?
Btw, if I flash Android 11 Beta (or the latest Android 11 build), it works.
Did you remember to wipe the data and factory reset?

Magisk with stock Android 10 / 11, MicroG with Android 10 stock

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.

Question LineageOS 18.1 / unusable on one Zenfone 8 but fine on others

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.

Samsung A605FN Booting in Odin Mode After flashing GSI

Hello, ive been trying to download a GSI for like 3 days but it seems impossible because it keeps booting me into Odin Mode everytime. Heres the steps i did:
1. Go into Odin Mode
2. Flash TWRP
3. Format Data
4. Wipe Dalvik ,Cache, Data,System
5. Flash the Android 13 (i also tried with the LineageOS one too)
6. reboot to recovery
7. Flash Magisk
I have tried not flashing Magisk but it just puts me in infinite boot
Use older Android versions, for Android 13 you need probably fixed/updated vendor. Follow this guide.
nqnxev said:
Use older Android versions, for Android 13 you need probably fixed/updated vendor. Follow this guide.
Click to expand...
Click to collapse
What about the LineageOS GSI? will i be able to boot in it after flashing Android 9?
nqnxev said:
Use older Android versions, for Android 13 you need probably fixed/updated vendor. Follow this guide.
Click to expand...
Click to collapse
Hello, i have followed the guide and used the LineageOS new rom from the list of ROMs that was in the thread and everytime Android restarts the phone reboots, any solution?

Categories

Resources