yashsingh1/xdaforums huggingface dataset:
[Treble-Enabled Device Development A/AB ROMS] moonraver:
Hello harvey186,

I have Huawei Y6 2018 and it is Treble enabled and arm64 A-only.

I want to install your LeOS A11 based ROM (LeOS-R-RW-arm64-avN) because your A12 based ROMs don't have A-only variant.

I unlocked bootloader and started to flash but now I am experiencing a problem:

- fastboot flash system LeOS-R-RW-arm64-avN.img

Invalid sparse file format at header magic

Sending sparse 'system' 1/4 (523260 KB) OKAY [ 23.505s]

Writing 'system' FAILED (remote: 'size too large')

fastboot: error: Command failed

I tried:

- fastboot delete-logical-partition product

- fastboot flash -S 256M system

- fastboot flash -S 300M system

None of them work. Does it mean that system partition is smaller than your IMG file?

Do I have to resize system partition? Please tell me how.

After unlocking bootloader, is it necessary to run:

- fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img? Because in my downloaded STOCK rom there is no vbmeta.img and I can not find it anywhere on internet.

Thank you very much
[Treble-Enabled Device Development A/AB ROMS] harvey186:
OK, first, the Invalit sparse think is a normal warning which you can ignore.

I don't think the image is to large. It must be something different. I have to search, because never have had this kind of error before :/

If your device doesn't have a vbmeta partition you can get trouble, because you must flash the permissiverV5 l.zip with a custom recovery like TWRP

If your device is still boot, pls post a screenshot of Treble Info app ( not treble check app)
[Treble-Enabled Device Development A/AB ROMS] moonraver:
I tried TWRP 3.2.3 for Y6 with Andy Yan's GSI Lineage 16 but it can not mount SYSTEM partition at all.

Device is not booting, only fastboot or TWRP.

Treble Info_v4.3.7 previously said:

- arm64

- A only

- VNDK

- no writing to system partition (or something similar)

In TWRP I can see partitons:

system,data,cache,cust,dsp,firmware,odm,persist,product,vendor,version,microsd card,usb otg. There is NO vbmeta and there are only 2 partitions I can not mount: SYSTEM and USB OTG.
[Treble-Enabled Device Development A/AB ROMS] harvey186:
- no writing to system partition (or something similar) this is the important part. I must know the right details.

So pls post a screenshot
[Treble-Enabled Device Development A/AB ROMS] moonraver:
Sorry but I don't have screenshot. It was NO WRITING TO SYSTEM PARTITIONS...... But I can see SYSTEM partition in TWRP:

/system

file system: ext4

present: yes

size: 1782MB

Free: 1779MB

used: 2MB

I tried to change it from ext4 to ext2 and back to ext4 to be able to mount and wipe. Now I can mount it, but 1,7GB vs LeOS image=2,08 GB can be that problem. I tried to Resize File System in TWRP but there is only swipe to resize and afterwards it does the same size but without any filesystem. So I formatted it to EXT4 again.
[Treble-Enabled Device Development A/AB ROMS] harvey186:
You can try deleltig cust and product partition
[Treble-Enabled Device Development A/AB ROMS] moonraver:
I did Huawei system restore via WIFI and this is my Treble Info screenshot. Do I still have to delete cust and product partition? If yes what are the fastboot commands? And what about that vbmeta if there is no? I really want to flash LeOS into this phone to get rid of Huawei and Google services.

Thank you very much!
[Treble-Enabled Device Development A/AB ROMS] harvey186:
you have a a-only device. That means, no LeOS-S only LeOS-R and flashing is different and there will be no partition to erase.

You can use this way: https://gitlab.com/leos1/leos-wiki/-/wikis/Flashing-Instructions/Standard-Android-8-and-9

and this GSI: https://leos-gsi.de/downloads/LeOS-R/June/LeOS-R-RW-arm-avN.img.xz

all other needed files you will find here: https://leos-gsi.de/downloads/miscellaneous/
[Treble-Enabled Device Development A/AB ROMS] moonraver:
Are you sure with ARM and not ARM64 image?
[Treble-Enabled Device Development A/AB ROMS] moonraver:
ARM image works! but now I have bootloop. How can I do this commands with fastboot (not with TWRP?

- flash permissverV5.zip

- flash DisableForceEncryption.zip
[Treble-Enabled Device Development A/AB ROMS] moonraver:
So I did everything with TWRP method and stuck on installing Permissiver V5:

New image larger than boot partition. Aborting ...

Updater process ended with ERROR: 1

Error installing zip file '/external_sd/

Updating partition details...

... done
[Treble-Enabled Device Development A/AB ROMS] harvey186:
oh, sorry, sorry, sorry, sure you need arm64-avN version, Have hit the wrong link :(
[Treble-Enabled Device Development A/AB ROMS] harvey186:
Sorry, no way, you will need a custom recovery for that. But first try booting the arm64 version. If it is booting, all fine. If not, You can't use a GSI, sorry
[Treble-Enabled Device Development A/AB ROMS] harvey186:
so you have flashed LeOS.img with TWRP or fastboot.

- Then you have formatted /data and reboot. Then you stuck where ? At manufacturer logo or at LeOS bootanimation or ??

- Then you have installed DisableForceEncrytion with TWRP and rebooted. Then you stuck where ? At manufacturer logo or at LeOS bootanimation or ??

- Then you have tied to install Permissiver with TWRP and running into that ERROR 1 ?
[Treble-Enabled Device Development A/AB ROMS] moonraver:
I spent 2 days with flashing and still no success. I went back to stock image.

What I did:

- flashed TWRP

- format data with TWRP

- reboot to TWRP

- with TWRP: flashed LeOS arm64 a-only (was too big for system partition) so I tried AOSP 9 and AOSP 8 both fit to partition

- got bootloop with Logo Huawei only

- flashed permissverV5.zip with result:

New image larger than boot partition. Aborting ...

Updater process ended with ERROR: 1

Error installing zip file '/external_sd/

Updating partition details...

... done

- so I flashed only DisableForceEncryption.zip = successfully

- still bootloop with Huawei logo
[Treble-Enabled Device Development A/AB ROMS] harvey186:
OK, I'm sorry. Huawei is a very critical device. And flashing AOSP 8+9 GSI was working fine ?? OK, LeOS-R is A11 and bigger. You can try with LeOS-Q.

Where AOSP 8 + 9 booting fine ? no bootloop?
[Treble-Enabled Device Development A/AB ROMS] moonraver:
AOSP 8.1, AOSP 9.0, Lineage 15.1 = bootloop. Huawei is a really horrible device. I had a big problem with unlocking bootloader. Then and I have found any article saying that Huawei did some changes to partitions for Y6 device in it's last official update and now people can not flash custom roms.

Never mind, I got back to stock, disabled some Huawei and Google services and installed Netguard firewall and FDroid apps.

Thank you for your fast responses and help.
[Treble-Enabled Device Development A/AB ROMS] harvey186:
OK, so I don't know why you have tried a A11 GSI. If A8 and A9 isn't booting, why should a 11 boot ??

But anyway, yes, Huawei/Homor are terrible. We have tried on some devices, but they where always buggy/no usable.
[Treble-Enabled Device Development A/AB ROMS] moonraver:
So what are the best phone brands for installing LeOS today? Just in case of buying a new phone. You know, to find a really completely-degoogled Android today is very hard.
[Treble-Enabled Device Development A/AB ROMS] harvey186:
First of all: I hope you are meaning with 'buying a new phone' that you will buy a used one.

In LeOS group most people are using Xiaomi devices. We also have FairPhone4 users and a lot Samsung users. But Samsung is bad for modding. I always prefer Xiaomi devices. Redmi or MI, both are good for modding

And you will find only one 'completely-degoogled Android' OS -> LeOS-GSI.
[Treble-Enabled Device Development A/AB ROMS] moonraver:
So I can see that Chinese brands are dominating for LeOS. I am not going to buy a new phone. If I do, I will certainly consult it with you. I have now a quite new Cubot KKM2 and had no problems with installing LeOS and also no problems with flashing back STOCK ROM with SP Flash Tool - advantages of Mediatek SoC and Chinese phone manufacturer :)

And what are your experiences about different SoC in phones and LeOS? Do they matter for installing?
[Treble-Enabled Device Development A/AB ROMS] harvey186:
We have had that discussion in our telegram group. I see no difference in CPU fpr LeOS. But in general: Qualcomm is faster and MTK is cheaper. That's all
[Treble-Enabled Device Development A/AB ROMS] moonraver:
Hello harvey186,

I have a question: Is there a way how to downgrade from Stock A11 to LeOS A10? I have tried this but still getting bootloop.

And is there a way how to change default camera app in LeOS A11? I know that it is fixed in A11 but LeOS Camera gives me only 8MP photos instead of 13 MP. I want to use HedgeCam2 as a default built-in camera.Do I need to use VNDKlite ROM and change some config files? I am really missing option to use 3party camera app launching from other apps.

Thank you
[Treble-Enabled Device Development A/AB ROMS] harvey186:
First, you can't use a A10 GSI with a a11 vendor firmware. You have to downgrade original firmware. ....if it is possible.

Second, you can install / use as much camera apps as you want. Install camera app of choice and use it. If you want, you can disable LeOS Cam, but no need.
[Treble-Enabled Device Development A/AB ROMS] moonraver:
For example: I use Osmand navigation app for mapping. In this app, when I click "add photo note" or "add video note" into map, it opens only built-in camera app which is LeOS Camera in this moment. When there was no LeOS built-in camera (in August or July LeOS edition) it was saying: There is no default camera installed,please install camera app though I had HedgeCam2 installed. This is that one of the bad features in Android 11. In LeOS 10 in Osmand I was able to choose which camera app I want to use but now it is gone.
[Treble-Enabled Device Development A/AB ROMS] harvey186:
You can set your camera app as default. Open Settings/Apps/YourCamera anx then scroll down to 'Open by default'

And disable LeOS cam in Settings/Apps/LeOS-cam

And wait til next release in around 2 weeks. There the cam app will be removed
[Treble-Enabled Device Development A/AB ROMS] moonraver:
Sorry but generally in Android 11 you can not set different camera app as default. At least in non-root ROM you can not. I use LeOS 11 GSI bvN. The procedure you wrote can not be done because all options are grey and can not be changed. That was the reason why I asked you. But somehow you were successful in this because you set the LeOS Camera as a built-in default camera. Maybe I should root and change some config files.
[Treble-Enabled Device Development A/AB ROMS] harvey186:
LeOS-19.1 has adb root. You can activate it in.developer options. Then you can remove the LeOS Cam with adb
[Treble-Enabled Device Development A/AB ROMS] moonraver:
Let's forget about LeOS Camera, it is not a problem. No need to remove it. If I do, I will get info that there is no built-in camera installed when I try to take pictures from other apps like Osmand, etc. This setting is written somewhere in system config files in Android 11 and can not be changed by users. I am trying to find out a way if it is possible to change it in system files. You have made it when you set LeOS camera as a "built-in" default camera for your Android 11 ROMs. How did you do that?
[Treble-Enabled Device Development A/AB ROMS] harvey186:
as soon as you add any app in sources it will be a 'default' app. I think you should wait til mid of October. Next version will be without LeOS-Cam
[Treble-Enabled Device Development A/AB ROMS] moonraver:
If I use your LeOS vndklite or bvS version, do I have to install anything else like magisk or simillar app to have system rooted (or to have access to system files, if it is not the same)?
[Treble-Enabled Device Development A/AB ROMS] harvey186:
You need VNDKLITE if you want edit something in /system. On LeOS-19.1 bvN you have adb root. So no need for installing MagisK.
[Treble-Enabled Device Development A/AB ROMS] trefix:
Hi harvey.

Will try your LeOS - 19.1 soon with my Samsung A317LTE (cause eOS-q...)

Thanks for the work ;)
[Treble-Enabled Device Development A/AB ROMS] KenHerman:
I just dirty flashed the October update to LeOS 19.1. I then tried to install SimpleContacts Pro unsuccessfully.

I read the following in the October changelog:

- replaced hidden SimpleContacts with AOSP Contacts. So people could use again SimpleContacts with UI

Do I need to do a wipe to remove the hidden SimpleContacts? Or, will should a dirty flash do it?

Thanks for any input.
[Treble-Enabled Device Development A/AB ROMS] harvey186:
Oh, I'm sorry, I have just seen, that SimpleContacts are still included. :(( I will update the changelog.

By The way, This is the Android 11 threat. pls use Android 12 threat in future. thx
[Treble-Enabled Device Development A/AB ROMS] moonraver:
Hello harvey186

I have installed your latest October LeOS-R-VNDKLITE-arm64-bvS.img.

1. boot animation is somehow zoomed, doesn't fit the screen and only 5 letters can be seen

2. LeosDroid is missing

3. "Install Superuser, the SU binary is out of date" notification. Is it necessary to update? If yes, can you tell me how? Don't want to screw anything :)

Thank you very much
[Treble-Enabled Device Development A/AB ROMS] harvey186:
Seems there is something wrong with your install. LeOS Droid is available and Bootanimation should fit the screen.

could be that it happens because of dirty flash. But on others users, no issue
[Treble-Enabled Device Development A/AB ROMS] moonraver:
It was a brand new instalation, downloaded and installed yesterday /saturday/, no dirty flash. And what about that old SU binary?
[Treble-Enabled Device Development A/AB ROMS] harvey186:
Oh, that's unbelievable. I will install the version on my test device and check it. By the way, if it'S brand new, why don't use LeOS-19.1 ??
[Treble-Enabled Device Development A/AB ROMS] moonraver:
I have tried LeOS-19.1 3 days ago - in this ROM everyting is OK. But my phone with Helio P22 4GB 64GB is not running so smooth with A12 versions that is why I am back on A11. Also touch reactions were not good globally in whole system. There was a problem during swiping to unlock display, it take 2-3 times to unlock and had to be done slower to unlock it at 1st time. And those big buttons of "quick settings tiles" - not a good choice for 4-inch displays......they are something I have a big problem to get used to.
[Treble-Enabled Device Development A/AB ROMS] harvey186:
Ah, OK. Now I understand why the bootanimation isn't full working. The screen is really small. You can remove the bootanimation.zip in /system/media. Then you will have the standard Android bootlogo

the message about old su is normal. su is always outdated. 99% of root users are using MagisK

regarding missing LeOS-Droid, I have attached the apk. But you can also add my repo in every f-droid client:

https://raw.githubusercontent.com/LeOS-GSI/repo/master/fdroid/repo?fingerprint=AA397AA3D66DE4AF62EBEF240C8DF60D508F5DA3080F79A7EAB97A48DCE2CE7D
[Treble-Enabled Device Development A/AB ROMS] moonraver:
Thank you. Could you please add LeOSDroid.apk into your cloud = /special_apps/LeOS-APPs . APK file will be more helpful and faster instead of having TXT repo file.

BTW: Now when I have LeOS VNDKLITE bvS ROM installed................do you know how to increase "in-call volume via back speaker" during calls? Not Media volume, that one is loud enough. I use only back speaker during calls and still haven't found any relevant app or procedure on internet how to increase it during calls (of course, my in-call volume is on maximum level). I think you are a higher master in Android OS and can advice how change some system config files like build.prop or simillar :)
[Treble-Enabled Device Development A/AB ROMS] moonraver:
There is another problem, I found out that OCTOBER Leos-R-vndklite-arm64-bvS image is not rooted. I checked root via terminal and Root Checker app. Am I wrong?
[Treble-Enabled Device Development A/AB ROMS] harvey186:
Mhm, now I ’ m a bit confused. Some days before you have written, that su is outdated and now you are writing it is not rooted 🤔
[Treble-Enabled Device Development A/AB ROMS] moonraver:
I am confused too. I have to flash once again to make sure what went wrong.
[Treble-Enabled Device Development A/AB ROMS] harvey186:
why don't use an older version from month before (September). It will have not the October issues
[Treble-Enabled Device Development A/AB ROMS] moonraver:
Results of root state on my Cubot King Kong mini 2 pro:

- Leos-R-vndklite-arm64-bvS September + October = not functional root

- Leos-vndklite-arm64-bvS-19.1 September = functional root

I am on 19.1 now.

What do you think about it? :)

Here is my TrebleInfo:

View attachment 5741649
[Treble-Enabled Device Development A/AB ROMS] harvey186:
Don't know what you are meaning with 'I am on 19.1 now'. You where all the time om 19.1

And I don't know why you are posting the TrebleInfo ?
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
@harvey186: LeOS android 13 GSI doesn't boot on my Galaxy Tab S7+. I'm using the latest Android 12 stock firmware (there is no official Android 13 firmware for my device).

I have TWRP, a Magisk patched boot.img from my firmware, and a patched vbmeta that I edited myself. Under these circumstances, the phhhusson A12 and Pixel Experience A13 GSIs boot fine, but LeOS doesn't (I've only tested the A13 GSI).

The img I used is LeOS T beta.
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
I got the 19.1 GSI to boot, but it's unusable, literally, for anything that's actually useful. The only things I can do are power it off, reboot, or go to the emergency call screen. That's it.

I get stuck on a screen with a signal icon, a battery icon, a grey bar at the bottom, and the dog from Charlie Brown (don't know his name, but I recognize the character because my dad used to watch reruns all the time).
[Treble-Enabled Device Development A/AB ROMS] harvey186:
A13 is only booting on a handful of devices. We are far away from a 'treble' A13.
[Treble-Enabled Device Development A/AB ROMS] harvey186:
You are talking about the setup wizard. You have flashed all needed files ? I'm mean vbmeta and LeOS ? You have made a factory reset before booting ?
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Yes, I did all of that. LeOS 19.1, your Android 13 doesn't make it past the bootloader screen.

What setup wizard? I got no such thing. Just the screen I described in my previous post. I wasn't asked to set anything up. And yes, it was a clean flash.
[Treble-Enabled Device Development A/AB ROMS] harvey186:
the black secreen with Snoopy on it is the setup wizard.

https://leos-cloud.de/core/preview?fileId=5592&x=1920&y=1200&a=true

LePS-19.1 is normally working fine on Samsung devices. Im my group are several Samsung users.

But anyway, as I have written, ALL A13 GSI are not really treble GSIs and only booting on newer devices. And as fas as I know, Samsung has more issues as other devices
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
Hmm, well, I tried tapping everywhere on the screen when Snoopy appeared. But nothing happened. The only things I was able to do are reboot, power off, or make an emergency call. Besides that it was totally unresponsive.

So...how do you complete the setup wizard, since it didn't ask me to do anything, and wouldn't let me do anything else?

It would be nice if your GSI were more clear in this regard, instead of just showing a dog from an old cartoon, but not giving any idea what to do next.

Oh, and your link asks me to log in...click it yourself...no photo is shown, but I don't need to see it. Maybe you would get a different page, I'd imagine you're already logged in.
[Treble-Enabled Device Development A/AB ROMS] harvey186:
I'm sorry, if you have flashed all needed files and made a factory reset before booting and the display has no touch, I can't help. If you where on stock Samsung it should work. Samsung is bad for modding, And A12 vendor made it much heavier. Sorry
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
I'll try again later, maybe with a short video. I don't remember there being any touch, IIRC i had to use the power button to access the reboot/emergency call menu. Touching the buttons inside that worked, and in the dialer. But I wasn't able to trigger anything else.

Maybe I'll join your Telegram, since you say you have Samsung users. Someone there might know the solution.

Besides the GSI img, what else is needed? I'm guessing just just a compatible boot.img/vbmeta. My vendor is from my latest Android 12 stock firmware. I've already got those covered, all other GSIs I've tried are working 100%. I used the dd command in TWRP to flash the img, same as all my other GSI img files. I've done a factory reset, and my data partition isn't encrypted.
[Treble-Enabled Device Development A/AB ROMS] harvey186:
wow, dd for flashing a GSI. Can't imagine that it will work. Because modern devices have a super dynamic partition and the system partition is INSIDE the super partition. So you will need fastbootd or Odin for flashing the system.img.

And the vbmeta must be flashed also by fastboot like

fastboot --disable-verity --disable-verification flash vbmeta google_vbmeta.img
[Treble-Enabled Device Development A/AB ROMS] AnonVendetta:
i used this. it's worked for all my gsi roms.

https://xdaforums.com/t/guide-a10-a11-flashing-and-booting-gsi-on-galaxy-tab-s7.4282085/

and yes, it does work, all have booted fine except your LOS T Beta.

I'm fully aware that the system partition is inside the super img. dd can write to that directly.

Also, Samsung devices dont have a fastboot mode. Even if you can get a fastboot prompt up and running, it's a neutered fastboot that can't do anything useful. You dont have to take my word on this, feel free to google it.
[Treble-Enabled Device Development A/AB ROMS] harvey186:
You are talking about LeOS-T beta ???? This is the LeOS-R threat. !!!!!!

If you want have support for A13, pls use Telegram group. thx
[Treble-Enabled Device Development A/AB ROMS] Madacam:
Hello, harvey186,

Thank you for creating LeOS, custom rom that I really appreciate.

I flashed on my galaxy tab a7 lite sm-t225, from magisk patched, "LeOS-20-VNDKLITE-arm64-bvS.img".

I can't get rid of the "bootloader unlocked" boot warning.

Terminal commands: adb devices; adb shell; su: dd if=/storage/emulated/0/Download/up_param.tarof=/dev/block/platform/bootdevice/by-name/up_param. On reboot, the warning is still present. Is there another solution?

What are the differences between custom AOSP LeOS-T and basic LeOS?

Thanks again for your work. (excuse my English translation)
[Treble-Enabled Device Development A/AB ROMS] harvey186:
to 99,99% there will be no way stop this warning. For rare devices there is a patch or workaround. But therefore you need to search in device specific forum or telegram groups.
[Treble-Enabled Device Development A/AB ROMS] DerivativeOfLog7:
Dead link
[Treble-Enabled Device Development A/AB ROMS] harvey186:
Sure, it's an 3 years old post

But this is still working: https://leos-gsi.de
[Treble-Enabled Device Development A/AB ROMS] anon5678:
Hello.

Is LeOS-20 GSI open source?
[P8 Lite (2017) Discussion] olivi25:
Hello,

I try to install any ROM and is not possible same problem.

I tested :

[ROM][OTA][8.1] LineageOS 15.1 for Huawei P8 Lite 2017

[ROM][UNOFFICIAL][prague][9] LineageOS 16.0

[ROM][10] DarkJoker360 AOSP 10 for Huawei P8 Lite 2017

this is what i do every time :

go to TWRP and do a full wipe (system, data, cache, dalvik/art cache)

format data

* install LineageOS ROM or AOSP 10 zip wtih bootloader

flash NFC.zip

* boot the rom

View attachment 5143089View attachment 5143087

I have [RECOVERY][prague][OFFICIAL][3.4.0-0]TWRP for Huawei P8 Lite 2017

I have the message " your device is bootion now" and after one or more reboot : I arrive on the huawei eRecovery.

what to do? and especially how to do?

thank you for your help because I no longer have a phone :(

UPDATE DarkJoker360 AOSP 10 for Huawei P8 Lite 2017 OK

CLOSE THIS POST :)