Follow the instructions
Files required to be download:
Aosp 9:here
build.prop: here
Flash GSI with TWRP use this fix sd card not read in twrp here
reboot to twrp by pressing power + volume up
Perform a factory reset within TWRP. format data
Download and extract system-arm-aonly-gapps-su.img.xz and you will get system-arm-aonly-gapps-su.img
Transfer the system-arm-aonly-gapps-su.img from your PC to your device’s internal storage where TWRP can access it.
Tap on “Install
Change the type from “zip” to “image.
Find and select the system-arm-aonly-gapps-su.img you downloaded.
Choose to flash to the system partition
no need to flash modified vendor
Once that is done, reboot your device.
Fix : performance copy the build.prop to system/
Bugs: google certification (fix here) after registration clear the google apps data (framewrork/services)
XDA:DevDB Information
Aosp 9 Redmi Go, ROM for all devices (see above for details)
Contributors
samsungics1200, phhusson
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
Based On: Aosp 9
Version Information
Status: Testing
Current Beta Version: April 16 2019
Created 2019-04-17
Last Updated 2019-06-11
is there any bug?
Fix : performance copy the build.prop : here copy to system/
Click to expand...
Click to collapse
File needs permission to access - is there another link?
Thanks - the file is available for download now.
I have installed the ROM and it works well but do you know if it is possible to disable the forced device encryption?
Also, my SIM2 is not recognised. Any ideas?
Auto booting to fastboot after installing... (installed to redmi go, it is unlocked, followed instruction, tried minimum 3-4 times, tried several variants of 9.0 Pie GSI etc.)
If You installed 9.0 by the instruction above and it successfully started, it means there is some hardware difference between different region redmi go devices. Mine is Global version.
Stock 8.1 GO is installing and starting normally from TWRP. Problem occurs only with the rom from this thread.
I want to switch to 9.0 beacuse stock 8.1 GO have push notification issue. Believe me, I tried everything to fix it, but unsuccessfully...
Waiting for Your help.
Instructions
NOTE: Do not flash the vendor file from the OP, that causes bootloops on my device.
This is what I did - now happily running AOSP 9:
- Restore stock firmware (http://en.miui.com/download-365.html)
- Reboot then perform system update to get latest release
- Reboot to bootloader (fastboot mode)
- Download the GSI image from the OP
- fastboot flash system system-test-20190415-arm-a.img
- Boot to TWRP recovery
- Mount system partition
- Replace /system/build.prop with one from OP
- Reboot
Additionally, if you want to disable encryption:
- Format data partition (You will loose all of your data!)
- Download vendor image file from OP
- Extract default.prop and fstab.qcom
- Mount vendor partition
- Replace extracted files to phone
Update
Hello to my Russian friends who are following this thread from http://4pda.ru/forum/index.php?showtopic=939092&view=findpost&p=84933744
I have attached the files that need to be replaced to this post
hello guys. i have tried both procedures. it gets stuck on "android" logo (booting i guess).
shall i use vendor? shall not use vendor?
"
- Restore stock firmware (http://en.miui.com/download-365.html)
....
- Replace /system/build.prop with one from OP
- Reboot"
now it should boot?
i tried stopping here, and no luck. i tried doing those "additionally.." steps, same lack of luck.
You only need to touch vendor if you want to disable forced encryption.
These instructions worked when I posted them on 4pda:
- Unlock bootloader - there are instructions elsewhere
- Download: http://treble.phh.me/system-test-20190415-arm-a.img (system.img)
- Download TWRP from other thread (trwp.img)
- Download files.zip from my previous post and extract build.prop
- Power off the phone
- Press volume down and power buttons to go to fastboot bootloader
- Connect your phone to your computer via usb cable
- Type in terminal: fastboot flash system system.img
- Wait for process to finish
- Type in terminal: fastboot boot twrp.img
- Phone will reboot to TRWP recovery mode
- Select "Mount" then "System"
- Type in terminal: adb push build.prop /system/
- Type in terminal: adb shell chmod 600 /system/build.prop
- Reboot phone
If you need GApps, grab the latest pico from https://github.com/opengapps/arm/releases - ie https://github.com/opengapps/arm/releases/download/20190507/open_gapps-arm-9.0-pico-20190507.zip - and install from TWRP.
in locks every time in the "Encryption unsuccessful ... RESET PHONE"
/vendor issue
What process did you use? Did you touch the /vendor partition? Does formatting /data from TWRP help?
Restore stock formware (all partitions from fastboot) then follow steps here: post 10
Camera issue
Only issue I spotted on this ROM for now is - Camera quality became worse. Is it a driver or just app level issue?
This is a Project Treble device which means that the drivers remain untouched in the /vendor partition and the new GSI uses them, unlike older ROMs which contained their own drivers. Which version of firmware did you have before installing the GSI? On 4pda it was observed that camera2 api apps was the issue but I have not seen any such problem.
Just updated to the May 2019 build (v113) and all is good - just had to resize the image to fit the partition. I shall keep updating monthly as long as phh keeps making them.
The ROM from the original post is no longer available. If anyone is interested then I can make an updated GSI available.
Note: FM radio is missing
Kyuunex said:
Note: FM radio is missing
Click to expand...
Click to collapse
Indeed, but the developer is on it, follow progress here: Include FM Radio app
I can't find a gsi that will fit my system partition
need the smallest GSI possible for an obscure mt6580 device
EDIT: would love to try the outdated image that's no longer available ANYWHERE
Related
Hey everyone,
During the initial versions of LineageOS, I wasn't been able to install it due to error:7 (Baseband error).
Now, I have tried a method that worked on my yu Yunique device.
This method can be used for any other device also but you have to find corresponding ROM file and other stuffs for your device only.
**Remember to take a full backup before experimenting with your device**
Procedure:
You need following things before you start-
1. LineageOS rom file: https://download.lineageos.org/jalebi
2. Open Gapps: http://opengapps.org (choose platform=ARM, android=7.1 and variant of your choice)
3.Caesium kernel: https://transfer.sh/Yqhm8/Caesium-jalebi-20170701-140319-v2.1.zip
4:LineageOS root file:https://download.lineageos.org/extras (Name: su(arm), version:14.1)
5. Firmware File: https://www.androidfilehost.com/?fid=673368273298934200
NOTE **There are some times that this method won't work in the latest TWRP i.e 3.0.3-0. So, revert back to TWRP 2.8.7.0 and then try the given method.**
Method:
1. After taking a backup of your previous working ROM, wipe off the Dalvik cache + system + cache + data in the recovery.
2. Flash the firmware image.( This solves the baseband error problem)
3. Flash the lineageOS rom file.
4. Now flash the caesium kernel( prevents bootloop)
5. after flashing all 3 files, reboot into system.
The first bootup will take about 2-3 minute(can go upto 5-7 min also). so have patience.
This worked for me. If it also works for you too, then please tell.
Also, you can watch my youtube video for the same:https://youtu.be/nYOsDeG5Kfs
Thank you
NOTE**All the file provided above belongs to their corresponding developers. I am just sharing it for help**
helpful guide
You can also solve this prob by delete baseband line in updater script
Helpful !!!!
This guide lets you install any GSI treble roms on our Daisy.
Read carefully and go step by step!
Update: Since Havoc OS doesn´t need permissive Kernel, I just installed the latest stock rom (9.6.9.0), flashed Havoc, set everything up and ended with sh...t... Camera´s not working, Opera freezes, everything sucks. It was a waste of time... So it´s still the situation:
If you want to use a custom GSI-Rom Only use this combination: Stock rom before flashing GSI: 9.6.4.0 and Kernel: Unofficial TWRP by Yshalsager - this combination works like a charm
Let´s get started: Be sure you are on Stock 9.6.4.0 (july security patch) if not, your wifi will not work in treble rom!
1) Download latest AB arm 64 gsi build. - ONLY ARM 64 AB GSI WILL WORK!
2) If you don´t have fastboot and adb download it from here: https://forum.xda-developers.com/sho....php?t=2588979 and install it!
3) Extract gsi64-ab-image to adb folder and rename it to system.img
4.a) Windows 7: right klick on white space in your adb-folder: open command prompt here
4.b) Windows 10: open command prompt as admin and navigate to your adb folder
5.) Power off your Smartphone and press pwr and vol- together -> your screen will show FASTBOOT - connect your phone to your PC
6.) type in your command prompt
Code:
fastboot oem unlock
Important: this will format your SD - All data will be lost If you perform that step! -> Backup before!7.) Phone will reboot, erase data and boot up. Power off again after boot up. Power + vol- to enter fastboot.
Now you have to decide: If you want to use Android 9 roms and TWRP together, you have to decrypt your data - else TWRP will not be able to read data! If you don´t care continue on step 11
8.) Download a patched_boot.img and place it in your fastboot folder - since only 9.6.4.0 works without bugs, you have to choose the patched 9.6.4.0 boot
9)
Code:
fastboot boot patched_boot.img
10) Connect to internet and update Magisk manager, download a root explorer - you could use this and go to
/vendor/etc/ and open the file fstab.qcom in editorreplace the text "forceencryption=footer with "encryptable=footer" and reboot to bootloader
11) Download this, rename it to boot.img and copy it to your fastboot folder
Code:
fastboot flash boot boot.img
12) Install official TWRP
13) After installing official TWRP reboot to TWRP agian and go to "wipe" -> "format data" and type "yes". Reboot to bootloader
14.) Download your GSI AB Image and place it in your fastboot folder
Code:
fastboot flash system [imagename].img
If you want, you can boot now to twrp and install magisk and/or gapps whatever - everything will work. Else you boot up your new system - Sometimes your GSI-rom will not boot up without a rooted kernel.
So if you stay in bootloop, just install magisk.zip!
Violla - Now you have a treble gsi rom on your Mi A2 Lite!
theres working twrp out for daisy, does this change anything refering to your first line:
"1) Download latest AB arm 64 gsi build. I would always use the gappsed version - twrp still not running for daisy... - ONLY ARM 64 AB GSI WILL WORK!"
thanks for the guide!
i really want to try this but im not sure which rom fully works. Also i'm not sure to do this without TWRP cause i'd like to have a complete backup of my device.
i'm in 9.6.9 version now with locked bootloader and unrooted
any suggests for me to try this rom
tutankpusch said:
theres working twrp out for daisy, does this change anything refering to your first line:
"1) Download latest AB arm 64 gsi build. I would always use the gappsed version - twrp still not running for daisy... - ONLY ARM 64 AB GSI WILL WORK!"
Click to expand...
Click to collapse
Updated: I removed that line...
merlin.berlin said:
thanks for the guide!
i really want to try this but im not sure which rom fully works. Also i'm not sure to do this without TWRP cause i'd like to have a complete backup of my device.
Click to expand...
Click to collapse
No problem - meanwhile there´s a official twrp here - and you can still use this guide
If you want to flash havoc 2.0 - I think it´s the best rom on earth , you will need to change your kernel to permissive that it will boot. To do that, read the thread there´s a vivid discussion how to do it...
elkhshap said:
i'm in 9.6.9 version now with locked bootloader and unrooted
any suggests for me to try this rom
Click to expand...
Click to collapse
If you like to have more features and/or pie (Android 9), then I would suggest to flash a custom gsi rom. If you can live with stock, I wouldn´t touch it.
Voodoojonny said:
No problem - meanwhile there´s a official twrp here - and you can still use this guide
If you want to flash havoc 2.0 - I think it´s the best rom on earth , you will need to change your kernel to permissive that it will boot. To do that, read the thread there´s a vivid discussion how to do it...
Click to expand...
Click to collapse
i want havoc OS but as i understand i can't use the fastboot method because i need the permissive fix, which only can be installed via TWRP, correct?
i would prefer fastboot over TWRP because all the problems with sdcard reading, encrypting etc.
merlin.berlin said:
i want havoc OS but as i understand i can't use the fastboot method because i need the permissive fix, which only can be installed via TWRP, correct?
i would prefer fastboot over TWRP because all the problems with sdcard reading, encrypting etc.
Click to expand...
Click to collapse
Hi,
there are so many reasons for havoc not to boot... and so less to boot...
BUT... If you won´t mind to use an unencrypted phone or no twrp, you can use (as I think) the best Android OS, havoc.
So think about, what is more important for you: TWRP or encryption.
1. With encryption: (Quite easy)
a) Go to stock 9.6.4.0 - July patch with mi flash and choose clean all (yes you will loose all your data -> back up everything) - Important: don´t install any ota after that!b) Download latest havoc and place it in your fastboot folderc) Download this TWRP and place it in your fastboot folder - you need this as Kerneld) As lazy person, I would rename the havoc file to havoc.img and the twrp file to twrp.imge) copy userdata.bin from stock to fastboot
Code:
fastboot flash system havoc.img
Code:
fastboot flash boot twrp.img
Code:
fastboot flash userdata userdata.bin
Code:
fastboot reboot
Wait and wait and wait and violla, you have havoc!
f) Gapps: download gapps, copy it to your fastboot folder and rename it to gapps.zip. Boot to recovery - twrp will not be able to read your data -> skip and allow modifications
Code:
adb push ./gapps.zip /sdcard
- Now you see gapps in your zip and you can install it!
g) Magisk: for magisk you need to download my patched twrp and place it in your fastboot folder
Code:
fastboot boot patched_twrp.img
- After booting up, you can go to magisk manager (yes: upgrade first etc.... and install magisk using the "direct method"
2. If you want to remove encryption - then you can use twrp fully, use this guide: here
Important: If you use another stock rom than 9.6.4.0 or do an ota, you will loose wifi!after doing all the steps:
Code:
fastboot flash system havoc.img
- that´s it!
Now you can use havoc
Voodoojonny said:
Hi,
there are so many reasons for havoc not to boot... and so less to boot...
BUT... If you won´t mind to use an unencrypted phone or no twrp, you can use (as I think) the best Android OS, havoc.
So think about, what is more important for you: TWRP or encryption.
1. With encryption: (Quite easy)
a) Go to stock 9.6.4.0 - July patch with mi flash and choose clean all (yes you will loose all your data -> back up everything) - Important: don´t install any ota after that!b) Download latest havoc and place it in your fastboot folderc) Download this TWRP and place it in your fastboot folder - you need this as Kerneld) As lazy person, I would rename the havoc file to havoc.img and the twrp file to twrp.imge) copy userdata.bin from stock to fastboot
Code:
fastboot flash system havoc.img
Code:
fastboot flash boot twrp.img
Code:
fastboot flash userdata userdata.bin
Code:
fastboot reboot
Wait and wait and wait and violla, you have havoc!
f) Gapps: download gapps, copy it to your fastboot folder and rename it to gapps.zip. Boot to recovery - twrp will not be able to read your data -> skip and allow modifications
Code:
adb push ./gapps.zip /sdcard
- Now you see gapps in your zip and you can install it!
g) Magisk: for magisk you need to download my patched twrp and place it in your fastboot folder
Code:
fastboot boot patched_twrp.img
- After booting up, you can go to magisk manager (yes: upgrade first etc.... and install magisk using the "direct method"
2. If you want to remove encryption - then you can use twrp fully, use this guide: here
Important: If you use another stock rom than 9.6.4.0 or do an ota, you will loose wifi!after doing all the steps:
Code:
fastboot flash system havoc.img
- that´s it!
Now you can use havoc
Click to expand...
Click to collapse
Please explain by video
thank you so much for this guide:good:
i'll try it later when im home:fingers-crossed:
Where do I find a userdata.bin file?
monzer said:
Where do I find a userdata.bin file?
Click to expand...
Click to collapse
In the Images-Folder of your stockrom after extracting...
- download fastboot stock rom
- extract archive
- look inside "images"
update: it´s userdata.img
Voodoojonny said:
In the Images-Folder of your stockrom after extracting...
- download fastboot stock rom
- extract archive
- look inside "images"
update: it´s userdata.img
Click to expand...
Click to collapse
Please post a video for ease of action
monzer said:
Please post a video for ease of action
Click to expand...
Click to collapse
Sorry, that will not happen!
Updated: view first post. This guide will definitely work well - and it´s easy! At least more easy than the other guides .
Voodoojonny said:
Updated: view first post. This guide will definitely work well - and it´s easy! At least more easy than the other guides .
Click to expand...
Click to collapse
No idea why you're useless taking pot-shots at other people, especially when you keep spreading lies about stock roms because you use a broken recovery. But have it your way.
Just keeping telling people to use a broken/untested recovery and bricking their phones, that forces them to reflash boot images. Can't wait until the bricks pile up.
I'm done with this website.
KezraPlanes said:
No idea why you're useless taking pot-shots at other people, especially when you keep spreading lies about stock roms because you use a broken recovery. But have it your way.
Just keeping telling people to use a broken/untested recovery and bricking their phones, that forces them to reflash boot images. Can't wait until the bricks pile up.
I'm done with this website.
Click to expand...
Click to collapse
If you would read, you would have noticed, that that broken and untested recovery is used as kernel, becouse it works great as kernel for gsi roms. Within the process it will be upgreaded by official twrp.
I spend a lot time, testing how to install custom roms on this phone, becouse I don't like like stock and I share my experience with others. Noone will break his phone with this! Perhaps you can try before complaining.
KezraPlanes said:
No idea why you're useless taking pot-shots at other people, especially when you keep spreading lies about stock roms because you use a broken recovery. But have it your way.
Just keeping telling people to use a broken/untested recovery and bricking their phones, that forces them to reflash boot images. Can't wait until the bricks pile up.
I'm done with this website.
Click to expand...
Click to collapse
Voodoojonny said:
If you would read, you would have noticed, that that broken and untested recovery is used as kernel, becouse it works great as kernel for gsi roms. Within the process it will be upgreaded by official twrp.
I spend a lot time, testing how to install custom roms on this phone, becouse I don't like like stock and I share my experience with others. Noone will break his phone with this! Perhaps you can try before complaining.
Click to expand...
Click to collapse
Lol, this site has gone way down hill... It's almost a joke now.
So many people asking for the 'easy' way and want answers to easily searchable questions. Sooo many multiple posts, and people not wanting to do the research themselves. How many threads need to be created on bricked devices because you didn't heed the warnings or follow the directions...
I wonder if xda even cares? This place use to be a great tool for the ones who like to tinker.
There are definitely a few folks keeping the spirit alive, but so many unnecessary posts - like what I'm writing right now...
Anyway thanks to anyone who puts time and effort for the greater good, we should all understand that tinkering with our devices can potentially have adverse effects.
Thanks for this noob friendly guide! a massive thanks! But hotspot still not working. Haven't tried the gcam but the stock camera is working but has no portrait and other features. The havoc os 2.0 looks snappy and buggy. Ill try other treble roms in few days
Any suggestions?
Bokoko006 said:
Thanks for this noob friendly guide! a massive thanks! But hotspot still not working. Haven't tried the gcam but the stock camera is working but has no portrait and other features. The havoc os 2.0 looks snappy and buggy. Ill try other treble roms in few days
Any suggestions?
Click to expand...
Click to collapse
You're welcome. Don't have problems with bugs and havoc 2.0... Interesting to test would be arrow pie! Benzo had problems with camera and flashlight... All the 8.1 can't handle the notch and overlay!
This guide is specifically aimed for Z010DD users who want to flash custom ROMs:If you want to stay on stock and only wanna flash TWRP and root the Stock ROM, please skip this thread and refer to @jide1 's guide here instead: https://forum.xda-developers.com/as...ot-asus-zenfone-max-zc550kl-qualcomm-t3652518
Things to be noted beforehand:
1. Make sure you are on the latest/final stock rom/firmware
2. Need Unlocked bootloader (Linked below, install the apk and follow the steps)
3. Take backup of all of your data from the internal storage. (To avoid depression if accidentally wiped your precious data)
4. Minimal ADB and Fastboot (Thread Linked below, Download from there and follow on-screen steps).
Steps:
A. To flash TWRP:
1. Once you have unlocked the bootloader, download 'minimal adb and fastboot zip' and PBRP zip(extract img from it).
2. Boot into fastboot by switching off the device, then POWER + VOLUME 'UP'. (You'll enter CSC ode screen, which is fastboot so don't worry)
3. Place the recovery image into the fastboot folder and open a command window there.
4. Connect your device, then type 'fastboot devices' and Enter, just to verify if your device is shown.
5. type: fastboot flash recovery recoveryname.img
THE NEXT STEP IS IMPORTANT, Pay Attention.
6. Now REBOOT Directly to twrp by holding POWER + VOLUME 'DOWN'. Don't boot into system else stock recovery will get restored.
B. Preparing for Flashing ROMs:
Once you have booted to twrp successfully, you will need to 'format' all the partitions, which includes:
System, Data, Cache, Dalvik/ART Cache, & Internal Storage.
HERE YOU WILL LOSE ALL OF YOUR DATA, YOU HAVE BEEN WARNED ALREADY SO, yeah.
Click to expand...
Click to collapse
1. In TWRP, go to WIPE -> ADVANCED WIPE;
2. Select the above listed partitions and then SWIPE TO WIPE.
Note: You will notice a partition called 'ASDF' ,wipe/skip, doesn't matter.
3. Come back to home, go to REBOOT -> RECOVERY
C. Flashing ROMs:
1. Download the ROM, Patch, and Kernel zip (Linked Below).
2. Flash them in the mentioned order.
3. Flash Opengapps (if needed) (Nano Gapps recomended).
4. Reboot.
(NOTE: FOR MAGISK, FLASH IT 'AFTER FIRST BOOT ONLY', AND IF FLASHING ZIP NOT WORKING, THEN see POST #3)
Bugs and Notes:
1. Notification LED doesn't BLINK when a notification arrives, it stays on (colors are correct though).
2. VoLTE is broken on pie roms (ignore the volte logo), stick to Oreo if you want VoLTE. (LTE data works fine).
3. Reboot Sometimes get stuck in black screen, its RANDOM, LONG Press the power button for 15 secs instead if that happens.
4. If any ROM contains 'Always On' functionality, disable it as the feature doesn't work properly. (Ambient display has no issues)
Links: Refer POST #2 .
Credits:
@SakilMondal for roms.
@YaAlex for kernel and patch for Z010DD.
Myself for testing.
Created 2019-04-22
Last Updated 2019-05-20
Links:
ROMs: https://sourceforge.net/projects/zenfone-max-updates/files/Z010D/ (Please flash the latest ones only, don't use old ones)
Patch (link updated): https://anonymousfiles.io/3WLplRtD/
Kernel (link updated + new kernel update): https://anonymousfiles.io/m4oKP6wL/
TWRP Recovery (Image file, Flash via fastboot): https://drive.google.com/file/d/1txHT0vRNo0gTMkD0Sb5kpuQQT0dAiphH/view
ASUS Official Bootloader Unlock Tool for 8939 Devices: http://dlcdnet.asus.com/pub/ASUS/Ze...513.74708998.1502054577-2083321676.1502054577
Minimal ADB and Fastboot: https://forum.xda-developers.com/showthread.php?t=2317790
Troubleshooting:
Instructions for Magisk:
1. Extract boot image from the rom zip
2. Go to Magisk Manager app
3. Tap 'Install' next to 'Magisk is not installed' line.
4. Tap 'Select and patch a file'
5. Navigate to the extracted boot image. It will now create a new boot image and save it in mentioned location.
6. Reboot to recovery, Flash the Boot image + KERNEL zip.
7. Reboot to system.
To fix CTS Mismatch in Magisk:
Open /system/build.prop, replace the line 'ro.build.fingerprint=' with:
Code:
ro.build.fingerprint=asus/WW_Phone/ASUS_Z010_2:6.0.1/MMB29P/13.8.26.80-20161230:user/release-keys
Open /system/vendor/build.prop , replace the line 'ro.vendor.build.fingerprint=' with:
Code:
ro.vendor.build.fingerprint=asus/WW_Phone/ASUS_Z010_2:6.0.1/MMB29P/13.8.26.80-20161230:user/release-keys
Patch is required for sd410 devices??
koushik99 said:
Patch is required for sd410 devices??
Click to expand...
Click to collapse
Nope, patch is only for DD.
Guide has been updated. Please check.
unable to flash GAPPS
Hai , i got a problem , phone shutdowns after flashing GAPPS (opengapps) , i tried Many RAMS(DOT OS, lineage-16.0-20190514-Z010D, BootleggersROM-Pie4Z010D.4.1-Stable-Unshishufied-20190421-170442 ,RR-P-v7.0.2-20190505-Z010D-Unofficial ) , without GAPPS Flashing it is , ROM working good , please let us know how to fl
I cant turn off the phone with pie,
i need to go in recovery first to power off otherwise after a while it turns back on
is it a known bug?
PRASAD.ASRS said:
Hai , i got a problem , phone shutdowns after flashing GAPPS (opengapps) , i tried Many RAMS(DOT OS, lineage-16.0-20190514-Z010D, BootleggersROM-Pie4Z010D.4.1-Stable-Unshishufied-20190421-170442 ,RR-P-v7.0.2-20190505-Z010D-Unofficial ) , without GAPPS Flashing it is , ROM working good , please let us know how to fl
Click to expand...
Click to collapse
Looks like you're using aroma gapps..
Use micro gapps or below. Here everything works fine.
ihatebarrels said:
I cant turn off the phone with pie,
i need to go in recovery first to power off otherwise after a while it turns back on
is it a known bug?
Click to expand...
Click to collapse
In both oreo and pie, for both z010d and dd, reboot and shutdown is an issue
It doesn't happen everytime, its random, and no fix is found yet.
Is it working on asus zenfone max 2016 sd 615?
Can anyone give me the updated link for the dd-fix-r5.zip and GUNMetal-R3.zip files
james_imch said:
Can anyone give me the updated link for the dd-fix-r5.zip and GUNMetal-R3.zip files
Click to expand...
Click to collapse
I just saw that the link was no longer working (would have been better if you pointed out that first instead)
Anyways,
Link is updated, check again (kernel is updated,patch remains the same).
Kaustav365 said:
Is it working on asus zenfone max 2016 sd 615?
Click to expand...
Click to collapse
Hope you have read the OP properly
This thread is only for sd615/Z010DD/MSM8939, and its clearly mentioned.
TechNova said:
I just saw that the link was no longer working (would have been better if you pointed out that first instead)
Anyways,
Link is updated, check again (kernel is updated,patch remains the same).
Click to expand...
Click to collapse
PBRP Recovery (flashable zip) link is also not working. Please update it.
james_imch said:
PBRP Recovery (flashable zip) link is also not working. Please update it.
Click to expand...
Click to collapse
Done,
Removed pbrp and now Twrp link posted.
TechNova said:
Looks like you're using aroma gapps..
Use micro gapps or below. Here everything works fine.
Click to expand...
Click to collapse
Hey! I am also facing the same issue. I tried the nano version of Gapps on my Asus Zenfone Max Z010D and my phone is still crashing it keeps restarting and then automatically turns off. Is there any issue to fix this?
unable to flash roms it shows up no digest found or invalid zip or update error 7
please help how do i find correct rom for sd615 8939
Eric0000 said:
unable to flash roms it shows up no digest found or invalid zip or update error 7
please help how do i find correct rom for sd615 8939
Click to expand...
Click to collapse
I too facing same problem
Unlocking the apk no longer works
Welcome to this guide, where I will guide you through rooting, flashing custom roms, and more, on our little Umidigi One Max !
WARNING : I am not responsible for your phone breaking or exploding during the night under your pillow. Please advice. If you cannot boot anymore, keep reading, your phone is NOT dead.
OFFICIAL ROM (Android 8.1)
The Umidigi One Max comes with Android 8.1 Out of the Box. Manufacturer has no plan on having 9.0 on the phone. That's why we root then ! Let's get into it.
Rooting the phone without unlocking it, or installing TWRP
Everything you'll do on this phone will NOT require a bootloader unlock. Note that this method is only in case you don't want to have your data wiped, or don't have access to an SD card (thus you cannot flash .zip in TWRP, except for ADB Sideloads)
What you'll need
Download the latest ROM from Umidigi's website : https://community.umidigi.com/forum.php?mod=forumdisplay&fid=211
Choose the ".rar" file
"E" ROMs are for European versions. It doesn't really matter what you choose.
Download SP Flash Tool on the same thread you opened for the ROM. It's "SPFT" for short
Unzip both
Install Magisk Manager on your phone : https://github.com/topjohnwu/Magisk/releases/
Steps
IMAGE COURTESY OF bencebacsi @ Umidigi forums
In the unzipped ROM folder, find boot.img
Copy it to your phone storage using an USB cable or any other method
Open Magisk Manager, press install
Choose "patch boot image file"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Let magisk do it's job
Find the boot.img file you just copied
Copy the patched_boot.img back to your computer
Open SP Flash Tool
Open the "Download" tab
In "Scatter-loading file", press the folder icon and browse to the downloaded ROM folder. Choose the only file that shows up
Untick every box except for boot. There is a column called "Location" with a path, click on it to change to file.
Choose patched_boot.img
MAKE SURE YOU UNTICKED EVERYTHING EXCEPT BOOT
Click the "Download" button
Turn off your phone (not reboot) and connect is via USB
wait for the flash to succeed. Once done, unplug, boot, voila ! You got magisk !
Credits to topjohnwu for Magisk, what a great piece of work
Installing TWRP
Note that if you want to access the /data partition (internal storage), you'll have to wipe it ! If you do not need it, keep going, it won't wipe unless you want to.
What you'll need
Official TWRP recovery.img by chankruze : https://twrp.me/umidigi/onemax.html
Magisk.zip installer (NOT the manager) : https://github.com/topjohnwu/Magisk/releases/
SP Flash Tool : http://www.mediafire.com/file/wxlld9dfywk67jl/SP_Flash_Tool_v5.1916.rar/file
This method is shorter and requires less downloaded files.
Steps
Turn off your phone
Run SP Flash Tool
Load the scatter file (see pictures above) you downloaded from the latest ROM (see above as well)
Untick everything except recovery
Change path to recovery.img to be the TWRP image
Click "Download" and plug your phone
After it's done, unplug, and press Power + Vol Up
You'll see three options appearing. That's how you'll get to the recovery. Use Vol Up to scroll, and Vol Down to select. Choose Recovery Mode !
TWRP should boot by now
EXTRA STEP : Make /data readable. You will need to format data (YOU'LL LOSE ALL YOUR DATA) (Wipe > Format Data > Type "yes") and after that, flash this zip : https://androidfilehost.com/?fid=1322778262904004415
You can now proceed to flash zips, including Magisk.zip. If you made /data readable, you can send it to your internal storage. If not, use an SD CARD or ADB PUSH / SIDELOAD.
Returning to stock to fix issues / brick
Use SP Flash tool but instead of unticking everything, tick everything. Note that USERDATA, if ticked, will clear your data.
Ticking only certain partitions may work if you got issues with magisk or system mods and are still on Official ROM. Flashing boot and system will remove Magisk. If you are on custom ROM, you can flash their system again to fix issues as well. Make sure to choose the right system.img in SPFT !
OTHER ROMS
Installing GSI (Generic System Image) to get Android Pie 9.0
GSI takes advantage of Project Treble to create one system image that will work on most devices without issues due to a separate "vendor" partition. The One Max is Treble-compatible, but only up to 9.0 (No 10 Q for now)
This will allow you to get an AOSP experience, with it comes easy modding and theming, and less bugs, less chinese-spying (that's a thing apparently, but who cares really ? Not me to say the least)
GSI List
You can find a GSI List including bugs and download links in my other thread here : https://forum.xda-developers.com/android/development/gsi-gsi-experiments-t3941194
WARNING : DOWNLOAD GSIs WHICH ARE ARM64-AONLY AND NOT AB !
Installing a GSI
You will need TWRP Installed. Check above if it's not done yet. You'll also need the Magisk.zip, and I highly recommend you getting the disable-force-encryption zip
Start up by wiping /data in twrp (Wipe > Swipe the bar). It will not wipe the files in your internal storage (Music, Download, etc...). If you want to get access to /data in TWRP (which I highly recommend), you'll need to do a full format (Wipe > Format data > type yes).
Download a GSI (.img) and send it to your phone (Either using an SD Card, or adb push [file on computer] [destination folder]). Send Magisk and the disable-force-encryption zip at the same time.
Flash that system image using Install > Install Image > Browse to the .img file
Flash disable-force-encryption if you formatted /data (don't flash it if you didn't do that !)
Flash Magisk.zip
Reboot and profit !
Note that there might be some issues with the GSI you choose. Most GSI suffers issues regarding Wifi Tethering/Hotspot. Other than that, check for my thread for issues regarding GSIs.
Some GSI require installation of GAPPS (Google Apps). Download a GAPPS zip and flash it at : https://opengapps.org/ (Choose ARM64 and 9.0)
If Installation fails, saying that system size is too small, go to (Wipe > Advanced Format > Tick "System" > Repair or change file system > Resize File System) and try flashing again.
INTERESTING MODS FOR ALL ROMS
Magisk FDE.AI
A great system manager. Saves a ton of battery without a performance hit. You need magisk installed. XDA Thread : https://forum.xda-developers.com/apps/magisk/beta-feradroid-engine-v0-19-ultimate-t3284421
Fix SafetyNet not passing on custom ROMs/GSIs
SafetyNet will not pass by default on custom ROMs / GSIs.
Use Magisk Hide Prop Config : https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
Run 'su' then 'props' in a terminal emulator. Edit Device fingerprint, choose Pick a certified fingerprint. I recommend using Xiaomi Redmi Note 7, as it changes the status-bar to be notch sized.
Note that you may need to do this next fix to make 'su' work :
Root request not working with Magisk
On some GSIs, root requests will not show up. You need to move some vendor files over to system.
Use TWRP's File Manager (Advanced > File Manager) or Adb shell to copy theses files :
Code:
/vendor/lib/libdirect-coredump.so
COPIED TO
Code:
/system/lib/libdirect-coredump.so
Code:
/vendor/lib64/libdirect-coredump.so
COPIED TO
Code:
/system/lib64/libdirect-coredump.so
This will fix this issue until GSI / ROM creator fixes it in their ROM;
Enjoy your new phone ! Don't forget to say thanks to all the developers behind every project (not me ! I didn't do anything )
If you have any issues, feel free to ask questions !
See you on the other side
Downloaded phhusson's AOSP ROM
Extracted compressed image. Then...
Wiped Phone from TWRP w/ all three options Swipe, Formatted (Type "Yes"), and advanced wipe.
From TWRP went to:
Install > Install Image > Selected system-arm64-ab-gapp-su.img > Select Partition to flash image
From this screen it lists these partitions for selection:
-recovery
-nvram
-uboot
-boot
-logo
-tee
-System Image
I select System image. It starts flashing. After it has finished, I go to reboot, and that is when TWRP states "No OS installed".
Am I downloading the wrong image file?
*********************EDIT****************************
Nevermind. I downloaded system-arm64-aonly-gapps-su.img.xz and it boots fine with gapps included
Exactly, you downloaded A/B image, not A-only.
Using phhusson's AOSP ROM. I got the root requests show up. However the superuser app is blank. Nothing shows in the list.
Request for a video to install GSI
Hello
I'm using Umidigi One Max Android 8.1 and want to upgrade to 9.0 . Can you please make a YouTube video showing how to install the GSI version I'd gladly appreciate it.
Over the last month or so, I've tried multiple GSI ROMs, and stock. I've rooted stock, and everything runs nicely, I just can't stand the lack of features. Even rooted on stock, Google Pay still works. If I install a GSI ROM like Havok, root it, gpay will not work. Not sure why it works on stock rooted with magisk, but not with other ROMs.
I'm looking for a hacked stock rom for the one max that:
A.) Can be rooted.
B.) Can still run gpay.
C.) Has a advanced restart option to boot directly into recovery.
D.) Displays the battery in the status bar as a percentage rather a symbol, and a clock with seconds option.
If I had those options, I would stick with stock. I can accomplish all those options with Havoc GSI ROM, I just can't get NFC/gpay to work.
su
how did you repair su binsaries after flasing (in twrp the vendor folder is empty)
everything else works
@ _cab13_
thanks for tutorial
some comments/questions
Image shows MT6739 in phone image and scatter file of mt6739
My phone is MT6363 and appears to agree with online specs site such as
https://www.gsmarena.com/_umidigi_one_max-9525.php
Am I looking at the wrong tutorial or umm have you grabbed images from another phone and forgot to say so?
w1lh3lm3d said:
how did you repair su binsaries after flasing (in twrp the vendor folder is empty)
everything else works
Click to expand...
Click to collapse
You have to mount the folder system and vendor for reading and writing and you can copy it, this is in recovery mount
Very helpfull, thanks)
Has anyone tried dual SIM and SD hack on this phone? I cant get my to work. When I do the hack, phone does not see any sim cards nor SD card.
However if I put only two sims, or sim and SD everything works well.
It is almost like issue w Samsung but no warning message
can i use this process on umidigi one as well
q1. Can i use this process on umidigi one as well?
When i visit "Official TWRP recovery.img by chankruze : https://twrp.me/umidigi/onemax.html" and search on devices they don't have umidigi one or one pro only the one max option. Other than screen size all three are pretty much spec'd the same. The umidigi one just doesn't have wireless charging or nfc that one pro and one max have and one max has 6.3 waterdrop vs one/one pro 5.9 notch display but all 720x1520 9:19 aspect ratio configurations. I found a umidigi one and one pro twrp recovery image here _https://unofficialtwrp.com/umidigi-one-umidigi-one-pro-root-twrp-recovery/ so if i have that are all the other downloads for doing non-rooted device upgrade to 9 pie non-device specific downloads?
q2. Nice to see this process covers a way to get form 8.1 to 9 w/o rooting device. Having never done so i'm curious why other search hits cover steps that require rooting device if the upgrade can be achieved without doing that, any insights?
q3. Would you say the likelyhood of bricking my device, if trying to follow these instructions using umidigi one vs one max, very low? Trying to determine if i should first line up and have on hand backup phone to use if the chance of that happening is high.
does magisk install allow me to upgrade to android 9 pie?
does magisk install allow me to upgrade to android 9 pie from the default android 8.1 oreo on my umidigi one or do i have to use the twrp recovery setup option to enable installing gsi arrowos or pixel experience android 9 pie update?
myusrn said:
does magisk install allow me to upgrade to android 9 pie from the default android 8.1 oreo on my umidigi one or do i have to use the twrp recovery setup option to enable installing gsi arrowos or pixel experience android 9 pie update?
Click to expand...
Click to collapse
Yes, with the single installation of magisk you could upgrade to Android 9, but you would have many more functions through TWRP. how to remove encryption, backup, etc.
drkiro said:
Yes, with the single installation of magisk you could upgrade to Android 9, but you would have many more functions through TWRP. how to remove encryption, backup, etc.
Click to expand...
Click to collapse
Thanks for reply. I was trying to see android 9 pie in magisk modules listings reviewed elsewhere and wasn't seeing what looked like a full android 9 install but rather options that themed and existing android 8.1 like android 9.
q1. If i complete the spft application of magisk_patched.img version of boot.img and try the android 9 module update option that's a one way street correct?
q2. Can one disable magish_patched.img version of boot.img by using spft to put the oem boot.img back in place?
q3. Sounds like twrp is the best way to put the official pixel experience android 9 [ or 10 ] custom rom on my umidigi one device. Your article shows how to get twrp enabled without bootloader unlocking the device. Any insights as to why there are so many articles suggesting that you have to bootloader unlock device to get twrp custom recovery image installed?
myusrn said:
Thanks for reply. I was trying to see android 9 pie in magisk modules listings reviewed elsewhere and wasn't seeing what looked like a full android 9 install but rather options that themed and existing android 8.1 like android 9.
q1. If i complete the spft application of magisk_patched.img version of boot.img and try the android 9 module update option that's a one way street correct?
q2. Can one disable magish_patched.img version of boot.img by using spft to put the oem boot.img back in place?
q3. Sounds like twrp is the best way to put the official pixel experience android 9 [ or 10 ] custom rom on my umidigi one device. Your article shows how to get twrp enabled without bootloader unlocking the device. Any insights as to why there are so many articles suggesting that you have to bootloader unlock device to get twrp custom recovery image installed?
Click to expand...
Click to collapse
Magisik, is used so that android 9 can boot, (now 10), in the system update to android 9, you only update the System partition, everything else remains as the manufacturer installed it, when you install twrp, you only change the partition recovery, and when you install magisk you change the boot partition, all this can be reversed, if you install the original versions.
drkiro said:
Magisik, is used so that android 9 can boot, (now 10), in the system update to android 9, you only update the System partition, everything else remains as the manufacturer installed it, when you install twrp, you only change the partition recovery, and when you install magisk you change the boot partition, all this can be reversed, if you install the original versions.
Click to expand...
Click to collapse
just to clarify, with the magisik patched boot.img i'm then able to apply a module that enables access to android 9 [ or 10 ] in the system update UI at which point i will carry out a standard issue android 8.1 to 9 [ or 10 ] upgrade process vs twrp where it appears you directly apply a gis custom rom like the mainstream pixel experience or arrowos options?
myusrn said:
just to clarify, with the magisik patched boot.img i'm then able to apply a module that enables access to android 9 [ or 10 ] in the system update UI at which point i will carry out a standard issue android 8.1 to 9 [ or 10 ] upgrade process vs twrp where it appears you directly apply a gis custom rom like the mainstream pixel experience or arrowos options?
Click to expand...
Click to collapse
No, there is no custom rom, which can be installed from the system update, all are images of the system partition, which are called GSI, which are installed by means of fastboot, or by twrp, all of them can be found here: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
drkiro said:
No, there is no custom rom, which can be installed from the system update, all are images of the system partition, which are called GSI, which are installed by means of fastboot, or by twrp, all of them can be found here: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Click to expand...
Click to collapse
interested in what makes a gsi [ generic system image ] custom rom an official vs an unofficial image given the pixel experience is listed as unofficial and aosp, arrowos and resurrectionremix offerings i've seen referenced in many places are listed as official.
i'd like to try the only official android 10 q aosp listing on my umidigi one to get off the dated android 8.1 experience and onto the more current one. This article suggests i can get twrp onto my device without bootloader unlocking it and with ability to revert back to the factory oem image setup currently running on it, if that update causes me to loose functionality or stability, using twrp recovery.
Is that a correct interpretation of the instructions in this article, and your clarifications in our exchange? I'm interested in experimenting but would like to not loose ability to go back to non-bootloader unlocked factory oem image in the event i need to exercise device hardware warranty or sell it. Thanks for your clarifications and additional insights.
myusrn said:
interested in what makes a gsi [ generic system image ] custom rom an official vs an unofficial image given the pixel experience is listed as unofficial and aosp, arrowos and resurrectionremix offerings i've seen referenced in many places are listed as official.
i'd like to try the only official android 10 q aosp listing on my umidigi one to get off the dated android 8.1 experience and onto the more current one. This article suggests i can get twrp onto my device without bootloader unlocking it and with ability to revert back to the factory oem image setup currently running on it, if that update causes me to loose functionality or stability, using twrp recovery.
Is that a correct interpretation of the instructions in this article, and your clarifications in our exchange? I'm interested in experimenting but would like to not loose ability to go back to non-bootloader unlocked factory oem image in the event i need to exercise device hardware warranty or sell it. Thanks for your clarifications and additional insights.
Click to expand...
Click to collapse
You can return, to the Originate flashing state, this image, https://community.umidigi.com/forum.php?mod=viewthread&tid=18692&extra=page=1 , can experiment with any image and return it to the original state, the pixel experience does not work with this phone, in Android Q the NFC does not work, and the videos in whastapp, do not work. Android 10 image comes without gapps, you have to flash them. If the twrp you can flash it through fastboot
My new Xiaomi Poco X3 Pro is showing an error screen after some time, like in this post:
https://forum.xda-developers.com/t/cant-load-android-system-lineageos.4314035/
It reads "Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device"
This happened so far:
I just unlocked the boot loader of my new phone after week of waiting.
I followed the official lineage instructions to install the OS: https://wiki.lineageos.org/devices/vayu/install
Everything worked including the sideloading via db.
I downloaded those two files for the LineageOS-Site:
- Recovery via fastboot: lineage-18.1-20211203-recovery-vayu.img (recovery works, I can still boot into recovery)
- System via adb: lineage-18.1-20211203-nightly-vayu-signed.zip
I also added Gapps via adb: "open_gapps-arm64-11.0-nano-20211204.zip"
Both adb transfers exited successfully.
After the first error screen
- I tapped Try again,
- When the error occurred again, I tapped "Factory data reset," but the error still occurred. The phone is new, no user data is on the phone.
- I booted into recovery and reset all the data I could. When I tap "Format system partition" it throws an error "E: Failed to open /dev/block/dm-0: No such file or directory. System wipe failed."
- Then I repeated the adb sideload. The error occurs again.
- I removed the SIM card, as someone in the forum suggested this could be a problem source. The error still occurs.
What can I do now?
----
Update [2021-12-05 Sun 20:09]
It seems to be a Problem with the GApps Version.
What I did Try so far is:
- Install 03-12-LOS and latest GApps via LOS recovery (didn't work)
- Install 03-12-LOS and latest GApps via TWRP recovery (didn't work)
- install LOS Build from 26-11-2021 without GApps (works)
- Install LOS Build from 26-11-2021 with latest GApps (didn't work)
- Install LOS Build form 26-11-2021 with GApps from 25-11-2021 (works)
Just use TWRP, flash ROM and AFTER flashing ROM Format Data where you have to type "yes". (Format, not Wipe)
Xiaomi Poco X3 Pro
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
Thanks for the Idea. At the moment it has not solved the problem.
This is what I did:
- Flash TWRP
Code:
fastboot flash recovery TWRP-3.5.2-vayu-Nebrassy-2.img
- copy lineage-18.1-20211203-nightly-vayu-signed.zip and "open_gapps-arm64-11.0-nano-20211204.zip" to the Poco device
- install via "install" option, wipe cache at the end of installation
- Format files (via "Wipe" -> "Format Data" -> type "yes")
- Reboot
After some time of the animated Lineage OS logo, the phone reboots into TWRP.
To me this seems very similar to the Lineage recovery before.
Any ideas what could be wrong?
You probably wiped System or Vendor partition or something, you are not supposed to do that.
Most likely you have to reflash MIUI now first. Make sure it's atleast version 12.5.X.X.
Flashing instructions are really simple, this apply to all ROM's.
FIRST INSTALL?:
Remove any fingerprint, PIN, or password in MIUI
Unlock the bootloader
Transfer ROM to internal storage
Install any suitable recovery
Flash ROM zip file
Do a data wipe in recovery (format data)
Reboot to the system, wait and enjoy
FLASHING UPDATES?:
Download via OTA Updater and let it automatically install; OR
Download an update, transfer to internal/external storage (always check file sha256)
Flash ROM zip and reboot.
Do not wipe anything else or add any additional steps. (maybe except Gapps if ROM doesn't have them included)
ps.
In first post there is no mention if you did Format Data or not and when you did it. Like i said before - you have to Formata DATA AFTER flashing ROM . Not before.
This happened so far:
I just unlocked the boot loader of my new phone after week of waiting.
I followed the official lineage instructions to install the OS: https://wiki.lineageos.org/devices/vayu/install
Everything worked including the sideloading via db.
I downloaded those two files for the LineageOS-Site:
- Recovery via fastboot: lineage-18.1-20211203-recovery-vayu.img (recovery works, I can still boot into recovery)
- System via adb: lineage-18.1-20211203-nightly-vayu-signed.zip
I also added Gapps via adb: "open_gapps-arm64-11.0-nano-20211204.zip"
Both adb transfers exited successfully.
Click to expand...
Click to collapse
k3lcior said:
In first post there is no mention if you did Format Data or not and when you did it. Like i said before - you have to Formata DATA AFTER flashing ROM . Not before.
Click to expand...
Click to collapse
I followed the LOS Install Guide: https://wiki.lineageos.org/devices/vayu/install But this procedure does not seem to bee the cause (see below).
Download the LineageOS installation package that you would like to install or build the package yourself.
Optionally, download an application package add-on such as Google Apps (use the arm64 architecture).
If you are not in recovery, reboot into recovery:
With the device powered off, hold Volume Up + Power. When Xiaomi/POCO/Redmi splash appears, release Power and keep pressed Volume Up until recovery appears.
Now tap Factory Reset, then Format data / factory reset and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one).
Return to the main menu.
Sideload the LineageOS .zip package:
On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
On the host machine, sideload the package using: adb sideload filename.zip.
Click to expand...
Click to collapse
Okay so this is what I did (the part that works):
- I downloaded the latest possible stock ROM from https://www.xda-developers.com/down...ut-several-xiaomi-redmi-mi-poco-devices/#vayu The fastboot ROM is more than 5GB.
- Extract the file "vayu_eea_global_images_V12.5.3.0.RJUEUXM_20211015.0000.00_11.0_eea_05cc38de43.tgz"
- then connect the phone via USB cable in fastboot mode and:
Bash:
cd ~/Downloads/vayu_eea_global_images_V12.5.3.0.RJUEUXM_20211015.0000.00_11.0_eea
/bin/bash ./flash_all.sh
- The default MIUI starts flawless, as it dit the first time I turned on the phone. So far so good.
What didn't work:
1. I installed the LOS Recovery again and flashed the OS and Gapps. Only after that I did step 3 - formating. The result ist the same bootloop as in the beginning.
2. I flashed the stock MIUI ROM again (which woks fine). Then I flashed TWRP, transfered the OS and GApps file and installed. I did not wipe anything, just used "format data" like above.
In both cases the OS does not start. After a while displaying the LOS-logo the phone reboots to recovery.
What did work:
I downloaded lineage-18.1-20211126-nightly-vayu-signed.zip, one version before the latest verion and the corresponding recovery lineage-18.1-20211126-recovery-vayu.img
I flashed only the OS, and no GApps -- and it launched successfully. Installing with the latest GApps failed again.
Install older gapp, not all gapp is compatible