Custom ROM for Huawei y6 (2018) - LineageOS Questions & Answers

I unlocked the bootloader of my Huawei y6 (atu-l21) 2 days ago. Now the problem is that I can't get working custom roms for twrp.
I had downloaded many .ZIP files but the zip file always contained only one image. When I wanted to download the ZIP file via twrp bottles, I always got a red message "invalid zip file format!
Does anyone have working custom ROMs for the Huawei y6 (atu-l21)
{
"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"
}

By you meaning by one file contains img file, you are trying to flash compressed gsi/treble image.
The installation procedure is different for treble devices. Instead do:
First you must uncompress it & do "adb reboot bootloader" & "fastboot flash system [UNCOMPRESSED_IMG_FILE]", wipe data by "fastboot -w", final reboot ur device "fastboot reboot"

do you think I should e.g. extract the customrom.zip to customrom.img and then the image with the commands Flash

Yes, Only if zip archive contains one *.img file like aonly, ab... etc

can I also flash the .IMG file via twrp. because when i try dan i don't know which partition to select.

System-Image

I just tried it and the message "Image is too large for the device" appears

You may read THIS POST about your device custom rom.
And if ab image doesn't work for you try aonly

Jannikoks06 said:
I just tried it and the message "Image is too large for the device" appears
Click to expand...
Click to collapse
Try with fastboot method

I'll do it later I'll report if it worked

Danielisko said:
Try with fastboot method
Click to expand...
Click to collapse
I did it but the phone doesn't boot, only the screen appears where it says that the bootloader on the phone has been unlocked

Related

[help]getting error while flash kernel

I extract the kernel.sin file from c2004_brazil.ftf and i try to flash this in fast boot mode i am getting following error
{
"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"
}
how to flash this in fastboot mode need any conversion to get correct boot image ?
Okay, try this:
Retry doing it not in a removable disk this time. I've had this issue the last time.
If that didn't do the trick, make sure that the FTF is not corrupted. If so, redownload in SUS/PCC if necessary, then decrypt.
elmkzgirxp said:
Okay, try this:
Retry doing it not in a removable disk this time. I've had this issue the last time.
If that didn't do the trick, make sure that the FTF is not corrupted. If so, redownload in SUS/PCC if necessary, then decrypt.
Click to expand...
Click to collapse
i placed the ftf in internal drive only, ftf also correct one check with flashmode.
and also same error when i try to flash "kernel.elf" file extracted from "kernel.sin" of ftf
stalin.sk2 said:
I extract the kernel.sin file from c2004_brazil.ftf and i try to flash this in fast boot mode i am getting following error
how to flash this in fastboot mode need any conversion to get correct boot image ?
Click to expand...
Click to collapse
U can also flash kernel in flaah mode just select the firmware and untick wipe data and system and in exclude everything except kernel and flash it , it will work
Sent from my C1905 using XDA Premium 4 mobile app

[Q] m8_dugl (M8 Dual SIM) boots only in bootloader

Hello everyone,
I really could need some help. I'm new to this forum and new to "rooting" an android device. I did a lot of reading before I made my first try, but how it seems not enough :crying:.
I followed the instructions in this thread. Everything worked as described just fine and I didn't get any errors. I did the following:
1) Unlock the bootloader
2) Flash custom recovery from fastboot - fastboot flash recovery openrecovery-twrp-2.8.3.0-m8.img
3) Flash boot.img from fastboot - fastboot flash boot boot.img
4) Fastboot erase cache - fastboot erase cache
5) Boot into custom recovery and flash root and busybox
6) reboot into bootloader
7) flash stock recovery - fastboot flash recovery stock_recovery.img
8) reboot device
The last step doesn't work. I'm stuck in the bootloader. Every time I try to reboot the device, the bootloader starts. When I choose "HBOOT" I get the following messages:
{
"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"
}
Now I think, I did not realize that dual sim version of the m8 is different from the single sim version. Am I right here? Or did I just miss something? Is there any way to fix this and get my device working again? Do I need a boot.img for the m8_dugl? Can perhaps anyone provide it? Every help is really appreciated! I'm totally stuck here
Many thanks in advance
Guss
Problem solved with boot.img from this Post. Thanks to Captain_Throwback.

Installing TWRP Problem

I have uncloked bootloader and I Flashed TWRP Recovery via ADB and when I send comand "adb reboot recovery" I have the Android guy (SS) I drop SS with Adb comand prompt too
{
"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"
}
Domolâ„¢ said:
I have uncloked bootloader and I Flashed TWRP Recovery via ADB and when I send comand "adb reboot recovery" I have the Android guy[/IMG]
Click to expand...
Click to collapse
Hey I had this exact same problem just a few moments ago. I didn't necessarily fix it but I found a different way of installing TWRP:
Basically what I did was temporarily boot into the recovery image I had (instead of properly flashing it) and then flashed a zip version of the recovery which works permanently.
To do that, go into the bootloader as normal (adb reboot bootloader) and then use [fastboot boot {filename}.img] (so replace filename with whatever file you have) to boot into the recovery temporarily, then flash the recovery zip.
Here's the link to the zip I used: https://www.androidfilehost.com/?fid=24407100847292484
UPDATE: OK turns out after a few reboots the recovery went back to not working, but I did try another method which definitely works. Temporarily boot into the recovery image as above, but this type install a Supersu zip. This will root the phone. Then boot into the phone as normal, install Flashify from the Play Store and use that to install the recovery image (which you should move onto the phone).
Here are some links:
Supersu zip I used: http://download.chainfire.eu/supersu-stable
Flashify: https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en_GB

Can't flash any img file using fastboot to root

As flashing frp.img: FAILED (remote: 'Requested download size is more than max allowed)
As flashing rooted-boot: FAILED (Write to device failed (Too many links)). It shows "press any key to shutdown" on my phone screen, even I enter the command at first, plug the phone then, or do both at the same time.
By the way the original fastboot shows the product name is g7ulm, but LG's official website says it's a sprint version according to my fastboot device-id.
Could you tell me what should I do if you knew the right way? I've been stucking here for a long time.
<hr />
{
"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"
}
Em_s'taht said:
As flashing frp.img: FAILED (remote: 'Requested download size is more than max allowed)
As flashing rooted-boot: FAILED (Write to device failed (Too many links)). It shows "press any key to shutdown" on my phone screen, even I enter the command at first, plug the phone then, or do both at the same time.
By the way the original fastboot shows the product name is g7ulm, but LG's official website says it's a sprint version according to my fastboot device-id.
Could you tell me what should I do if you knew the right way? I've been stucking here for a long time.
<hr />
View attachment 5232397
View attachment 5232403
Click to expand...
Click to collapse
Do you have the latest android platform tools (fastboot) installed?
For my phone, for root, you install magisk app.
Put stock boot.img on phone sdcard
In magisk, click "install magisk".
Choose patch file. Select your boot.img.
Patched image will be in download folder.
Put patched image on pc and boot to fastboot
fastboot flash boot magisk_patched***.img

Question SOLVED Faulty root access on Xiaomi Eu rom

I cleanly installed Xiaomi Eu rom, then got root access by flashing Magisk 24.3. The installation went smoothly. According to the Root Checker app, I have root access on my device. But when I try to modify a file in the system folder with the Root Explorer app, it won't let me do it and gives me an error message.
{
"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"
}
I don't know if I've missed something or I'm uninformed, but is it not possible anymore (or never was) to modify system files in Miui based roms?
Hmm... Try using FX File Manager
I highly recommend this File Manager!
Did you flash magisk directly using twrp? If so, that might be the problem.
See this post:
Gapps error 70, resize System Partition.
Hello. After I received my new Poco f3, the first I've done was unlocking the bootloader. 7 days later, everything was done and I flashed lineageos. >Fastboot boot twrp.img>advanced>flash current twrp. After that I've wiped and format data...
forum.xda-developers.com
user0u said:
Did you flash magisk directly using twrp? If so, that might be the problem.
See this post:
Gapps error 70, resize System Partition.
Hello. After I received my new Poco f3, the first I've done was unlocking the bootloader. 7 days later, everything was done and I flashed lineageos. >Fastboot boot twrp.img>advanced>flash current twrp. After that I've wiped and format data...
forum.xda-developers.com
Click to expand...
Click to collapse
Yes I have flashed it using twrp and also from fastboot mode.
Never mind, I fixed it flashing (using TWRP) the MAKERW-STABLE-4.1.11.zip file from this thread https://forum.xda-developers.com/t/...-script-to-install-all-roms-via-twrp.4405061/

Categories

Resources