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

[hawkhu]

*** 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! ***

*** 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:

fastboot flash kernel /path/to/KERNEL.img

Flash the recovery you downloaded with

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

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).

 

[dj 77mx]

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).

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)

 

[hawkhu]

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)

System.img goes to the system partition, obviously.

 

[evolbug]

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

 

[UlysistheNewbie]

Anyone tried this at atu l22 latest build?

 

[hawkhu]

Anyone tried this at atu l22 latest build?

Since the ATU-L21 and L22 is the same hardware wise it should work without any problems.