Database Users

How to flash GSI-s on ATU-Lxx after the April 2019 security patch?

Code:
*** I'm not responsible for dead sd cards, thermonuclear war, getting you fired because the alarm has failed. Your warranty is void if you continue! ***
Code:
*** Everything you read here was a success for my ATU-L21 variant of the Huawei Y6 (2018). Don't be alarmed, the files mentioned here are 100% compatible with the phone ***
Hey, dear Forum Users!
Prerequisite things:
Install HiSuite, it has the proprietary drivers needed to operate ADB and Fastboot.
You need to unlock your bootloader, get them from dc-unlocker, it's 4 euros.
You need the following:
The 2018 kernel and vendor image: https://drive.google.com/open?id=1aFTTMSArwBuF5tsJBkWJ7f_d7IQc7zyy (credits goes to Boki, @deadliestPixel on Twitter)
You need this TWRP to boot up: https://forum.xda-developers.com/huawei-y6/development/guide-backup-current-partitions-t3853831 (thanks to @leepicstitch on Twitter for finding this)
You'll need to flash this TWRP to recovery_ramdisk: https://www.mediafire.com/file/7nyab3whb6bp7r8/twrp_3.2.3_atu.rar/file
Choose a ROM that will suit your needs from this thread: https://forum.xda-developers.com/huawei-y6/development/index-list-roms-y62018-t3854167 or try other GSIs
(I recommend Resurrection Remix with gapps and su)
So if you have everything, let's do this.
Before we start everything make sure you have a microSD card that has the VENDOR.img and the system.img you downloaded.
So, we need to make a backup of our current recovery_ramdisk for later, you can follow the TWRP XDA post above to do so.
After you've done that go to fastboot and flash the older kernel with this command:
Code:
fastboot flash kernel /path/to/KERNEL.img
Flash the recovery you downloaded with
Code:
fastboot flash recovery_ramdisk /path/to/recovery.img
Now boot up that screen flasher recovery you had before. If you booted it up just reboot the phone to recovery with
Code:
adb reboot recovery
, the Y6 Prime 2018 recovery should boot up.
Now go to Install -> Change Storage -> Micro SD -> flash image -> choose the vendor.img and flash it to the VENDOR partition.
Do the same for the system.img file.
Go to the main menu and go to wipe, then wipe dalvik/art cache, cache, data, internal storage.
go to the main menu and go to reboot, then bootloader.
Now we need to flash our stock recovery_ramdisk back, because eRecovery will complain about a damaged data partition. Do a low level data format, type yes, and when the emui recovery pops up, do another data wipe.
Now, just hit reboot and the phone should boot into the ROM.
Turn off the phone and reboot back into fastboot and flash back the Y6 Prime 2018 recovery just in case if eRecovery wants to do something weird.
Now just reboot your phone and enjoy it.
If you need any help send me a DM on Twitter (@miklos_akos) or on Discord (miklos_akos#0001).

hawkhu said:
Hey, dear Forum Users!
Prerequisite things:
Install HiSuite, it has the proprietary drivers needed to operate ADB and Fastboot.
You need to unlock your bootloader, get them from dc-unlocker, it's 4 euros.
You need the following:
The 2018 kernel and vendor image: https://drive.google.com/open?id=1aFTTMSArwBuF5tsJBkWJ7f_d7IQc7zyy (credits goes to Boki, @deadliestPixel on Twitter)
You need this TWRP to boot up: https://forum.xda-developers.com/huawei-y6/development/guide-backup-current-partitions-t3853831 (thanks to @leepicstitch on Twitter for finding this)
You'll need to flash this TWRP to recovery_ramdisk: https://www.mediafire.com/file/7nyab3whb6bp7r8/twrp_3.2.3_atu.rar/file
Choose a ROM that will suit your needs from this thread: https://forum.xda-developers.com/huawei-y6/development/index-list-roms-y62018-t3854167 or try other GSIs
(I recommend Resurrection Remix with gapps and su)
So if you have everything, let's do this.
Before we start everything make sure you have a microSD card that has the VENDOR.img and the system.img you downloaded.
So, we need to make a backup of our current recovery_ramdisk for later, you can follow the TWRP XDA post above to do so.
After you've done that go to fastboot and flash the older kernel with this command:
Flash the recovery you downloaded with
Now boot up that screen flasher recovery you had before. If you booted it up just reboot the phone to recovery with , the Y6 Prime 2018 recovery should boot up.
Now go to Install -> Change Storage -> Micro SD -> flash image -> choose the vendor.img and flash it to the VENDOR partition.
Do the same for the system.img file.
Go to the main menu and go to wipe, then wipe dalvik/art cache, cache, data, internal storage.
go to the main menu and go to reboot, then bootloader.
Now we need to flash our stock recovery_ramdisk back, because eRecovery will complain about a damaged data partition. Do a low level data format, type yes, and when the emui recovery pops up, do another data wipe.
Now, just hit reboot and the phone should boot into the ROM.
Turn off the phone and reboot back into fastboot and flash back the Y6 Prime 2018 recovery just in case if eRecovery wants to do something weird.
Now just reboot your phone and enjoy it.
If you need any help send me a DM on Twitter (@miklos_akos) or on Discord (miklos_akos#0001).
Click to expand...
Click to collapse
One question, I have to flash the system.img as a vendor?... (BECAUSE YOU SAY ABOVE THAT WITH THE SYSTEM. IMG WE MADE THE SAME AS WITH THE VENDOR)

dj 77mx said:
One question, I have to flash the system.img as a vendor?... (BECAUSE YOU SAY ABOVE THAT WITH THE SYSTEM. IMG WE MADE THE SAME AS WITH THE VENDOR)
Click to expand...
Click to collapse
System.img goes to the system partition, obviously.

This worked flawlessly, the only difference is that I couldn't flash Kernel.
The ROM I used: PHH Treble 9.0 github.com/phhusson/treble_experimentations/releases/tag/v117
The steps I took:
- Factory reset phone
- Backup stock recovery_ramdisk
- Download kernel (unused) and vendor
- Boot fastboot
- Flash twrp in recovery_ramdisk
- Boot twrp
- Flash vendor, flash system
- Clean caches
- Reboot fastboot
- Flash stock recovery_ramdisk
- Reboot
erecovery did not complain, everything was ok there

Anyone tried this at atu l22 latest build?

UlysistheNewbie said:
Anyone tried this at atu l22 latest build?
Click to expand...
Click to collapse
Since the ATU-L21 and L22 is the same hardware wise it should work without any problems.

i keep either getting a black screen or vendor not mount or system not mount if not vendor ( ATU-L22 Y6 2018 )

UlysistheNewbie said:
Anyone tried this at atu l22 latest build?
Click to expand...
Click to collapse
.REPLYING--- Hey bro have you tryed flashing custom rom to the Atu-L22 with any luck?

Still trying to flash a custom system.img to my Atu-L22 after weeks of no success but flowing thru with countless amounts of tutorials, Anyone have any ideas for this phone, any help much appreciated haha?

I'm stuck in a boot splashscreen... This phone is really not easy to work with x(
edit : Narrowing it down, apparently, I don't have a vendor partition to flash the vendor to... I am starting to loose hope.

I need stock recovery_ramdisk.img . Anyone have? (Im sorry for my bad English )

Cannot install LineageOS from TWRP (bootloop, error 7, etc.)

Hello, I'm trying to install LineageOS on my Asus Zenfone Max Pro m1 (ZB602KL) but I'm stuck in TWRP and cannot install any OS.
(Sorry I cannot post proper external links as i am new on this forum)
I will try to explain what I did as clearly as possible (I was following the install page X00TD from the LineageOS website) :
1. Unlocking the bootloader
No problem here I guess, I just downloaded the from asus.com/Phone/ZenFone-Max-Pro-M1/HelpDesk_Download/ then
Code:
adb install
it then run the application from the device.
2. Installing a custom recovery using fastboot
This is where is start to be blurry for me. I download the TWRP from the link given by the LineageOS install page (androidfilehost.com/?fid=3700668719832241089) I can
Code:
fastboot flash recovery <recovery_filename>.img
without any problem but when I reboot into recovery I don't get TWRP and when try to
Code:
fastboot boot <recovery_filename>.img
I get something like this :
Code:
downloading 'boot.img'...
OKAY [ 2.292s]
booting...
FAILED (remote: unknown command)
So I'm trying to get an other version of TWRP from the TWRP website but the Asus Zenfone Max Pro m1 is not listed in the devices section (twrp.me/Devices/Asus/). I finally found this reddit post reddit.com/r/LineageOS/comments/aiiw3f/flashing_twrp_on_linux_fastboot_doesnt_work/ , download this TWRP androidfilehost.com/?fid=11410963190603879312 and flash it using
Code:
fastboot flash:raw boot <recovery_filename>.img
as recommended on the post and can finaly boot into TWRP.
3. Installing LineageOS from recovery
I "format data" and do an "advanced wipe" as indicated on the LineageOS install page, I get some error messages (encryption, etc.) so I reboot into recovery and try again and it seems to work. I try to sideload the last lineage build downloaded here download.lineageos.org/X00TD but I get this :
Code:
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
so I decided to
Code:
adb push
it and install it via TWRP but I get an
Code:
Updater process ended with ERROR: 7
. I found this reddit post reddit.com/r/LineageOS/comments/cfwnox/x00td_lineageos_16_firmware_error/. I downloaded the firmware from asus.com/Phone/ZenFone-Max-Pro-M1/HelpDesk_Download/ but I cannot install it from TWRP (error 7 again).
Then I found some link to a "PIE" firmware that I can install from TWRP after installing the "PIE" firmware I can finally install LineageOS but when I reboot I get some warning message saying : "the boot loaded is unlocked and software integrity..." after this I get the LineageOS loading animation (the right to left blue bubble) for 2 minutes then it reboot to TWRP.
Voila.
- I don't really understand the difference between the FIRMWARE (1.5 Gb) or the PIE FIRMWARE (60 Mb) or even the LineageOS file. I'm still trying to adb push some firmware or OS and install them but i'm affraid of making an irreversible mistake and "brick" the phone.
- I don't know if the problem come from my
Code:
fastboot flash:raw boot <recovery_filename>.img
TWRP install or from a bad TWRP file, or from the OS/firmware file.
So what should I do now? How do I clean this mess and install a working OS (LineageOS or even back to Asus/Android factory OS)?
Any help is appreciated, Thank you

uncheck TWRP boxes?
I found this post reddit.com/r/LineageOS/comments/dtnec5/infinite_loading_screen_after_fresh_installation/
and I simply unchecked the TWRP auto install boxes before reboot... and it seems to work for the moment.
The OS takes 7.8Gb, I don't know if it's a normal size or I messed something.

Flash newer firmware

[Laurel_Sprout] [ROM] [UNOFFICIAL] Lineage OS 17.1

Code:
/*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Lineage OS 17.1
Properties
Selinux mode : Enforcing
Build type : user
Gapps : not included
LOS recovery : included
Known issues
FM radio
You have to wake up the phone to use the FOD
No charging icon when off
Maybe others you tell me
Installation
I'm not sure about that but you can try :
1 - Download latest stock android 10 ROM from here
2 - Install OrangeFox from here
3 - Set A as active slot, flash stock rom, orangefox installer zip, reboot recovery
4 - Set B as active slot, flash stock rom, orangefox installer zip, reboot recovery again (now you have A10 vendor blobs in both A/B slots)
5 - Flash custom ROM zip
5,5- Maybe factory reset on los recovery
6 - Flash OrangeFox installer
7 - Reboot recovery
8 - Flash Gapps / Magisk(optional)
9 - fastboot format:f2fs userdata
Troubleshoot
If wifi/bluetooth is not working, flash stock dtbo.img with fastboot flash dtbo.img
If ROM keeps rebooting to recovery, format userdata (wipes internal storage!) with fastboot format:f2fs userdata
Downloads
Download 28/03/2020
Checksum : 05a147341c33bf1e04b16bad721d2961
Download 21/03/2020
Checksum : e2fbec3542e8d9c164854103cceb38cf
Telegarm Group
Sources
ROM
Device tree
Kernel
Vendor
Credits
Big thank's to @Golbinex !
LineageOS team - ROM
@Harukey
@prakaship78
@charliespencerchaplin
XDAevDB Information
[ROM][10][UNOFFICIAL] Lineage OS 17.1, ROM for the Xiaomi Mi A3
Contributors
dantir
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: Lineage OS 17.1
Created 2020-03-21
Last Updated 2020-03-28

Changelog
28/03/2020 : FOD fix
23/03/2020 : DO NOT USE THIS BUILD IT DOESN'T BOOT
21/03/2020 : first relase

Nice, will check it out once I get TWRP working again

Plans for official?

amnher said:
Plans for official?
Click to expand...
Click to collapse
I would love to but it's my first rom, I have a lot to learn.
Also I think to be official it must be perfect like no dtbo.img to flash.

fm radio
would there be a way to get fm radio working?

thank you

how to do this (If ROM keeps rebooting to recovery, format userdata (wipes internal storage!) with fastboot format:f2fs userdata)

I just cannot get it to boot, it always leads to a bootloop. I have followed the guide here and here and also installed latest Android 10 fastboot zip to both slots and flashed the twrp-patched boot image to boot to recovery (flashing regular images included in recovery threads will always boot to bootloader) to flash this, it just doesn't boot... Anyone had any luck?

Any way we could have this rom as permissive ?
In order to have gravitybox working we just need permissive selinux ?

vaykossil said:
Any way we could have this rom as permissive ?
In order to have gravitybox working we just need permissive selinux ?
Click to expand...
Click to collapse
Change it, if you use Gravitybox you should know how to root your phone.
Then is easy to change SELinux status, temporaly in a terminal
Code:
setenforce 0
If you want it to stick is better to have a script running at boot with Magisk instead of editing system config files.
The point is if you want permissive mode do it your self, the default state should be Enforced for everyone is a matter of security.

Makishima said:
I just cannot get it to boot, it always leads to a bootloop. I have followed the guide here and here and also installed latest Android 10 fastboot zip to both slots and flashed the twrp-patched boot image to boot to recovery (flashing regular images included in recovery threads will always boot to bootloader) to flash this, it just doesn't boot... Anyone had any luck?
Click to expand...
Click to collapse
me too, I tried different recoverys, different steps but no luck, I just can't get it to boot.

Many thanks for the ROM!
I followed the current installation instructions on the start page (but i did NOT "5,5- Maybe factory reset on los recovery") and the rom seems to work very well (Fingerprint sensor, Bluetooth music box, ...).
After I booted to Lineage OS the first time the android logo appeared two times but then Lineage OS started correctly. I didn't need to flash the dtbo.img.
Initially I also did the step "5,5- Maybe factory reset on los recovery", but when I tried to boot to OrangeFox recovery from fastboot again the bootloader/fastboot screen was launched.
I found one minor issue: When you disable the screen lock then the background image is shifted a little bit for a short time. I also successfully tested data decryption in the provided OrangeFox recovery.
I would be glad if "Signature Spoofing" would be enabled so you can use microG with this rom.
I own the global version of the Mi A3.

facundonak said:
me too, I tried different recoverys, different steps but no luck, I just can't get it to boot.
Click to expand...
Click to collapse
I think you installed 23/03 build. Try the last one : 28/03 It should be better.

FOD works in general, but does it much slower than on stock ROM, and you have to wake up phone first...

Hey dantir,
Thanks for your efforts on this ROM. Been on lineageOS on multiple phones till date. Rooting for you to get this to a more stable state. Kindly request you to not abandon this ROM.
Thanks a lot.

Do magisk modules work well? call recording, busybox, etc ...?

hello
i have bootloop error
before to install lineageos my data partition was encrypted, so i formated it, in order to send via adb the lineageos zip
then i installed lineageos
this command has error :
fastboot format:f2fs userdata
/usr/bin/make_f2fs failed with status 1
fastboot: error: Cannot generate image for userdata
can you confirm we must flash lineageos in orangefox
after installing lineageos must i reboot in fastboot to execute this command : fastboot format:f2fs userdata

hello i installed the rom
how do you create this rom, can you post the instructions
i would like to create a custom rom with my app included as a system app
thnaks

noogpout said:
hello
i have bootloop error
before to install lineageos my data partition was encrypted, so i formated it, in order to send via adb the lineageos zip
then i installed lineageos
this command has error :
fastboot format:f2fs userdata
/usr/bin/make_f2fs failed with status 1
fastboot: error: Cannot generate image for userdata
can you confirm we must flash lineageos in orangefox
after installing lineageos must i reboot in fastboot to execute this command : fastboot format:f2fs userdata
Click to expand...
Click to collapse
Hey! Just use official TWRP (link), works fine with! Did not have to do anything special.
Also, this rom seems stable, gonna start using it as daily driver this weekend I guess. Thanks @dantir, will you keep this updated? You use it as a daily driver too? Any bugs found in the 28th version?

X2Pro - C.29 Stock to LOS with Magisk

Firstly, I would like to thank @karthick mostwanted for his work and a thumbs up for keeping Lineage OS updated.
I have an Indian Unit of X2 Pro with 128 Gigs of RAM and I got the ROM working with FP and the payment apps at once. Everything works good here. Only thing which I did not like is the camera, so I'm using PixelPlus GCAM on this ROM.
Coming to the steps (assuming ADB & Fastboot drivers installed) -
1. Unlock the Bootloader. For the same Install the In Depth Test app (pm if you do not get the links for the app on Google) and apply. After a successful review message on the app, use the following commands.
adb reboot bootloader (For reboot into fastboot mode)
fastboot flashing unlock
Select the confirmation dialog on the screen and its done. Then type fastboot reboot for the phone OS to boot. It will erase all your data too.
2. Next step is to install TWRP img file by Mauronofrio (Google it). Download vbmeta.img also, you will get in LOS thread downloads section. Copy the recovery file and vbmeta into the ADB folder where the powershell/cmd is running so the you can fetch it. Reboot into the fastboot mode and give the following command.
fastboot flash recovery recoveryfilename.img
DO NOT REBOOT YET. Immediately type fastboot flash --disable-verification vbmeta vbmeta.img and enter. Don't reboot, with help of Volume and power button combination, boot directly into recovery. Remember, do not reboot phone in any other mode or even the present OS because it will wipe the recovery installed.
3. Format Data. (Don't Wipe, Use FORMAT DATA Option). Wipe Cache & Dalvik.
4. Keep the Files in a USB Storage such as Lineage OS, Magisk 20.3, Open Gapps Nano ARM 64.
5. Insert the USB drive through an OTG and go to TWRP mount option and mount external storage. It will start showing files. Now go to install and select OS. Wait, don't run now. Add Gapps to the same queue and then run.
6. After successful installation, wipe cache and dalvik and reboot your phone.
7. After you setup everything, again boot into TWRP recovery and install magisk 20.3.
You are done and all set !
Note - Do not remove/uninstall system apps using root access in LOS, it may break. Happened with me when I tried to uninstall DuckDuckGo, it went into bootloops.
Will be happy to answer any doubts for this installation. Comment below if you need further help !

oreopie said:
Note - Do not remove/uninstall system apps using root access in LOS
Click to expand...
Click to collapse
Do you mean by using apps like titanium backup, systemapp remover or similar?

Did you rooted with new lineage OS 18 ?

flashing ROMs

After flashing SuperiorOS and also LineageOS Android 11 I get message "No OS installed" after reboot system after flashing and it is stuck on booting screen then and it only helps to flash official build via fastboot. What am I doing wrong? I am doing clean flash.
P.S.: I get many errors about something with vendor that failed with red letters while flashing

Dont worry here are the steps i follow every time and it works for me
- Download platform and fastboot drivers
- Download TWRP from offical website for tissot there should be one .img and other zip file latest version is 3.4.0-0 i think
- Download ROM whichever you like
- Press and hold power button with volume down until it boots to fastboot connect your phone to pc make sure you have fastboot drivers installed
- Open command prompt with administrator privileges locate to platform folder where you have fastboot.exe before doing anything type fastboot devices if it shows few numbers and fastboot than it means you are good to go
- Make sure you put TWRPxxxxx.img file in platform for easy access type fastboot boot TWRPxxxx.img or which link for ur twrp image file press enter after few seconds your phone will be booted up in twrp from there go ahead and transfer TWRPxxxx.zip to your internal or sd card and flash it when its done from twrp restart it to recovery wipe , delvik cache , data , system ---> flash rom zip than install twrpxxxx.zip again restart to recovery than go ahead and intall nikGapps 11 and ( MagiskR if you want root access ) when its done restart to system it should boot into OS without any problem it will take some time
dont worry about vendor errors i get them everytime but without any issues its normal
Hope it helps if you need anything ask away