[ROM][11.0][4.9][AOSP][KUGO] Explosive Lobster - Sony Xperia X Compact ROMs, Kernels, Recoveries, &

[ROM][11.0][4.9][AOSP][KUGO] Explosive Lobster - Sony Xperia X Compact ROMs, Kernels, Recoveries, &

[ROM][11.0][4.9][AOSP][KUGO] Explosive Lobster
KUGO F5321
Hi! Just wanna share with you Android 11 ROM builded for Sony Xperia X Compact
Many Thanks for development @Cubbins
I'm not responsible for any damage caused with your device after flashing this ROM. Flash only on your own risk.
This ROM bring us Treble support ( ARM64 A/B ) structure for all GSI images based on 11 Android. Just flash any GSI at System partition after it.
How to Install:
1) Copy ROM to SD card and flash with recovery
2) Download SW_BINARIES_FOR_XPERIA_ANDROID_9.0_2.3.2_V9_LOIRE.ZIP, unzip and copy image to sdcard too
3) Flash Binaries with recovery to OEM/ODM partition
4) reboot
5) After reboot we need to flash/format userdata partition. So, download it and flash with ADB: fastboot flash userdata userdata.img or fastboot erase userdata
6) reboot.
Warning:
We use /cache partition at thid ROM as a /vendor, so if you format /cache partition on recovery - you'll catch a bootloop.
Features:
Working:
- Wi-Fi
- Bluetooth
- Fingerprint
- Sensors
- Camera
- Calling
- Music Playing
- GPS
Not Working:
You tell me
Sources:
build ROM sources:
github.com/ExplosiveLobster
kernel sources:
github.com/ExplosiveLobster/kernel_sony_msm-4.9
bug reports:
github.com/ExplosiveLobster/bug_tracker/issues
Screenshots:
{
"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"
}
Download:
Google Drive
Explosive Lobster - Google Drive
drive.google.com
Mega
3.11 GB folder on MEGA
12 files and 3 subfolders
mega.nz

So good to see some people still working on this device. I'm considering leaving the official rom to this one as soon as GPS is operational. Thank you very much.

mhemart said:
So good to see some people still working on this device. I'm considering leaving the official rom to this one as soon as GPS is operational. Thank you very much.
Click to expand...
Click to collapse
GPS Working fine with latest build, so you can try it right now

lubik1 said:
GPS Working fine with latest build, so you can try it right now
Click to expand...
Click to collapse
Really good, I have to backup my data and I'll give a try tonight. Thanks !

[QUOTE = "lubik1, post: 84244519, member: 5897890"]
Which vendor should I use?

mister-13x said:
Which vendor should I use?
Click to expand...
Click to collapse
F5321 is for X compact.

mister-13x said:
Which vendor should I use?
Click to expand...
Click to collapse
SW_binaries_for_Xperia_Android_9.0_2.3.2_v9_loire.img
The one vendor binaries for both devices - suzu and kugo

Are the Flame Gapps in your Google Drive the Gapps you recommend, or can we just use OpenGapps as usual? This is my first experience with Android 11.
Edit1: Installation worked like a charm with your description. For me, there was no change after flashing userdata.img. The phone behaved the same way, whether I flashed userdata.img or I did not. What did NOT work was just to delete userdata - then my phone would show an error message after boot and just shut down again.
After every boot, I receive the error message “There’s an internal problem with your device Contact your manufacturer for details”. According to Google, this has something to do with Treble. I will install my apps now and get the tests going. Thank you SO much for this. If you leave your PayPal here somewhere, I will send you some small bucks that I can afford for the good development.

Spaceoid said:
Are the Flame Gapps in your Google Drive the Gapps you recommend
Click to expand...
Click to collapse
You can flash any Gapps you want, but this gapps was tested with EL ROM and work fine.
Spaceoid said:
Thank you SO much for this. If you leave your PayPal here somewhere
Click to expand...
Click to collapse
It's allways on my profile, on section "about"

Hello. I had no time to perform an install yet but I have a question (maybe stupid ?). I noticed the binaries were for Android 9 but I saw that there was a newer version called SW_binaries_for_Xperia_Android_10.0.7.1_r1_v7a_loire (no more binaries for android 11). Do you think it could be used with your ROM ? Maybe it would prevent the message that Spaceoid see at every boot ?
Just in case, here is the link to the newest version : https://developer.sony.com/file/download/software-binaries-for-aosp-android-10-0-kernel-4-14-loire/

I just send you two coffees via PayPal for the good work. I know it is not much, sadly I am a student with little income... But I hope it keeps you energized for further improvements to the ROM!
After half a day of testing the pure ROM, without any apps and just Gapps, here is what I found so far:
- Wifi is working, but, at least for me, after like 30 minutes after every boot, it seems to break. After that, I am not able to reconnect to my home wifi network, or to find any Wifi networks in general. Only a reboot fixes this.
- Regarding the error message mentioned in my last post, I found this:
How to Fix Android system There's an internal problem with your device
How to Fix Android system error "There's an internal problem with your device Contact your manufacturer for details" and How to remove NFC Service 'NFC keeps stopping'.
www.recovery-mode.com
I cannot say how reliable/safe this procedure is, though.
- Connected to this, the NFC tile in the pulldown menu (from the status bar) does not work. I can activate NFC via the settings, though; I did not try yet if it really works, but at least it can be activated.
- After every reboot, the phone forgets the time and date until it is connected to cellular network or wifi for the first time.
(- one minor thing - the alarm clock does work well, but it does only sound the alarm and not wake up the screen. So, before disabling the alarm, one has to unlock the screen first.)
Will start installing my apps now and keep on further testing.

mhemart said:
Hello. I had no time to perform an install yet but I have a question (maybe stupid ?). I noticed the binaries were for Android 9 but I saw that there was a newer version called SW_binaries_for_Xperia_Android_10.0.7.1_r1_v7a_loire (no more binaries for android 11). Do you think it could be used with your ROM ? Maybe it would prevent the message that Spaceoid see at every boot ?
Just in case, here is the link to the newest version : https://developer.sony.com/file/download/software-binaries-for-aosp-android-10-0-kernel-4-14-loire/
Click to expand...
Click to collapse
I was about to ask the same. Are the 10 binaries not compatible?

@betacrypt
Binaries for 10 are available however the kernel development was abadoned. Kernel 4.14 did not mature into an operational state. Kernel 4.9 is the current stable version, using the 9 binaries are the most recent option at the moment.

@lubik1
This is being trebled? SELinux is permissive? If that's the case, I imagine the cache.img and boot.img can be used to GSI other OS'.
Warning:
We use /cache partition at thid ROM as a /vendor, so if you format /cache partition on recovery - you'll catch a bootloop. [QUOTE/]
Click to expand...
Click to collapse

&(*) said:
@betacrypt
Binaries for 10 are available however the kernel development was abadoned. Kernel 4.14 did not mature into an operational state. Kernel 4.9 is the current stable version, using the 9 binaries are the most recent option at the moment.
Click to expand...
Click to collapse
Ah that makes sense. Somehow I thought 4.14 was stable.
Also thanks @lubik1 for your efforts to create this! Glad to see continued support for the XC - was worried we'd lost support for it. I own two and had been hoping to see an update.

betacrypt said:
Ah that makes sense. Somehow I thought 4.14 was stable.
Also thanks for your efforts to create this! Glad to see continued support for the XC - was worried we'd lost support for it. I own two and had been hoping to see an update.
Click to expand...
Click to collapse
Don't forget to thank @Cubbins too for the build.

@lubik1 ,
Can you also provide a GSI variant (of boot.img and cache.img) for those of us who like to use other systems?

Anything different to do when rooting with Magisk? I flashed the latest Magisk in TWRP successfully but when I boot into system the Magisk App says no root.

betacrypt said:
Anything different to do when rooting with Magisk? I flashed the latest Magisk in TWRP successfully but when I boot into system the Magisk App says no root.
Click to expand...
Click to collapse
Strange. I did the same this morning, downloaded latest Magisk version from Github, and it worked for me. I already used root for Titanium Backup. I used v21.2.
On another note, after one day of usage, I'd already consider this ROM quite stable. The wifi problem really is the main problem, as I only can connect to my home wifi in 20% of the day. I already lost all my mobile data because of that, now I am surfing in less than 2G speed on my phone xD

Spaceoid said:
- Wifi is working, but, at least for me, after like 30 minutes after every boot, it seems to break. After that, I am not able to reconnect to my home wifi network, or to find any Wifi networks in general.
Click to expand...
Click to collapse
We'll switch to another wi-fi driver on next build.
Spaceoid said:
- Regarding the error message mentioned in my last post, I found this:
Click to expand...
Click to collapse
Will be Fixed on next build
Spaceoid said:
- Connected to this, the NFC tile in the pulldown menu (from the status bar) does not work. I can activate NFC via the settings, though; I did not try yet if it really works, but at least it can be activated.
Click to expand...
Click to collapse
Will be added on next build
Spaceoid said:
- After every reboot, the phone forgets the time and date until it is connected to cellular network or wifi for the first time.
Click to expand...
Click to collapse
Missing rtc-service, will be added on next build

Related

[ROM] LineageOS 14.1 (official)

Can this be flashed with current twrp?

Absolutely, that's what I did. Use sideload.
MrWhite0429 said:
Can this be flashed with current twrp?
Click to expand...
Click to collapse

Can't wait for those issues to be fixed so I can use it. Surprises me how fast you're working tdm

EEEEE I LOVE YOU
thank you so damn much tdm, i was scared this phone would be developmentally dead

Just installed and it works...pretty alright!
Bugs:
-Wi-Fi range seems to have shrunk ten-fold (LTE works perfectly fine, so it seems to be a problem with whatever Wi-Fi module(?) is being used with the ROM)
-Can't hear anyone on calls (What you already addressed)
That's all I've found so far. I was able to install SuperSU v2.79, which is super dope, and I've tested it with my good friend Titanium Backup to great results. Thanks a whole bunch for all the hard work, TDM!
P.S.: If you're dumb like me, and you're pretty new to all of this stuff, follow this guide that I sourced from the Open GApps FAQ to install the ROM:
A 'Clean' install consists of the following:
Factory Reset (or manually wipe (format) Data partition - Internal Storage wipe is NOT necessary)
Manually wipe (format) your System partition <-Unnecessary
Flash your ROM
Flash GApps package <-Use opengapps arm64 7.1 micro
Flash SuperSU v2.79 <-Use the arm64 version of SU found on the LineageOS website
Wipe the Dalvik & cache <-Unnecessary
Reboot (Because of the SuperSu install, there may be a bootloop or two. It also warned me before I rebooted that I didn't have an OS installed, even though I did.)
NOTE: YOU WILL LOSE ALL OF YOUR DATA AND APPLICATION SETTINGS using this method. Be sure to do a NANDroid backup prior in case you want to restore later.
Click to expand...
Click to collapse

Glad someone else got it to work, and thanks for the instructions. Note formatting /system is not necessary, neither is wiping cache or dalvik.
If you want su, lineage has a flashable root package. Check on their site. SuperSU may work but it's not supported in any way.
I'll check the WiFi stuff, I probably missed a config or calibration file or something.
The in-call audio is probably an issue in the amplifier code. I just got that working yesterday, so no surprise there. Fix should be relatively easy.
mattx1002 said:
Just installed and it works...pretty alright!
Bugs:
-Wi-Fi range seems to have shrunk ten-fold (LTE works perfectly fine, so it seems to be a problem with whatever Wi-Fi module(?) is being used with the ROM)
-Can't hear anyone on calls (What you already addressed)
That's all I've found so far. I was able to install SuperSU v2.79, which is super dope, and I've tested it with my good friend Titanium Backup to great results. Thanks a whole bunch for all the hard work, TDM!
P.S.: If you're dumb like me, and you're pretty new to all of this stuff, follow this guide that I sourced from the Open GApps FAQ to install the ROM:
Click to expand...
Click to collapse

I need a log from stock and I don't really want to flash back and forth. Can someone do me a favor and get a log of a phone call using stock 7.1.1? Just run eg. "adb logcat >call.log" and then make a call, establish voice communication, hang up, and hit ^C.
Thanks!

tdm said:
I need a log from stock and I don't really want to flash back and forth. Can someone do me a favor and get a log of a phone call using stock 7.1.1? Just run eg. "adb logcat >call.log" and then make a call, establish voice communication, hang up, and hit ^C.
Thanks!
Click to expand...
Click to collapse
Sent private message to you. That logfile was made right? (stock 1.2.0B09 7.1.1 tulip locked)

mattx1002 said:
LTE works perfectly fine
Click to expand...
Click to collapse
I know this is off topic, what carrier do you have? I think my carrier didn't activate LTE for me at all.

Thanks I got it. I used the amp parameters from your log but still can't get in-call audio. Need to keep looking....
maestromony said:
Sent private message to you. That logfile was made right? (stock 1.2.0B09 7.1.1 tulip locked)
Click to expand...
Click to collapse

Vixenko said:
I know this is off topic, what carrier do you have? I think my carrier didn't activate LTE for me at all.
Click to expand...
Click to collapse
I'm on T-Mobile.

I'm on AT&T. LTE works for me.
Vixenko said:
I know this is off topic, what carrier do you have? I think my carrier didn't activate LTE for me at all.
Click to expand...
Click to collapse

Okay been working away on this. Got the WiFi MAC and the notification light working. Still haven't figured out call audio, which is the biggest show stopper right now.
Got a question though....
As far as I can tell, the notification light hardware only seems to support a single color at a time (red, green, blue). They can't be mixed to provide eg. yellow or orange. So, it can't do the typical yellow for the "medium battery" color. What do you people prefer for that? What does stock show?

Thanks for your work again.
Stock:
Constant green when its fully charged (and blue blinking when notification arrived).
Constant blue when its charging.
Red Blinking when level is below 15%
In my opinion you can leave it like that.
tdm said:
Okay been working away on this. Got the WiFi MAC and the notification light working. Still haven't figured out call audio, which is the biggest show stopper right now.
Got a question though....
As far as I can tell, the notification light hardware only seems to support a single color at a time (red, green, blue). They can't be mixed to provide eg. yellow or orange. So, it can't do the typical yellow for the "medium battery" color. What do you people prefer for that? What does stock show?
Click to expand...
Click to collapse

mekzmaz323 said:
Thanks for your work again.
Stock:
Constant green when its fully charged (and blue blinking when notification arrived).
Constant blue when its charging.
Red Blinking when level is below 15%
In my opinion you can leave it like that.
Click to expand...
Click to collapse
I agree. I'm fine with it being the same.

WiFi and lte
My WiFi is very bad and unstable. Also I never have more than 1 bar of LTE signal. And when I make a call others can't here me and I can't here them.. Those are my only problems.
Version: B14
Thanks @tdm for all your work!
tdm said:
Here at long last, Lineage 14.1 for the Axon 7 Mini!
... I'll fill this post out more later ...
Current status: Alpha
Currently supported devices:
US variant (tulip) running 7.1.1 b14 firmware.
Known major issues:
Phone audio doesn't seem to work.
Bluetooth audio stutters incessantly, unusable.
Notification LED doesn't work.
Cannot seem to get NFC to work.
Known minor issues:
WiFi mac addr isn't set properly.
WiFi connection seems a bit flaky. (?)
Download:
lineage-14.1-20171019-UNOFFICIAL-tulip.zip
MD5=5b4ca59d5b9f69e59dc44ba28637b71a
Tested with opengapps arm64 7.1 micro.
Sources:
device_zte_tulip
kernel_zte_msm8952
Click to expand...
Click to collapse

These are known issues except for LTE. My LTE works fine and I have reports that others do also.
CRAFTER0302002 said:
My WiFi is very bad and unstable. Also I never have more than 1 bar of LTE signal. And when I make a call others can't here me and I can't here them.. Those are my only problems.
Version: B14
Thanks @tdm for all your work!
Click to expand...
Click to collapse

Today's build is up, with handset audio working!
I think the volume adjustments may need work, but I do hear audio.

I'm off work tomorrow so I may stay up tonight and give this a try! In anyone's opinion is this stable or suitable for daily use?

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

Hi,
{
"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"
}
DarkJoker360 AOSP 11 for Huawei P8 Lite 2017
*** Stable Version ***
About
Android is an open source software stack for mobile devices and a corresponding open source project led by Google. This site and the Android Open Source Project (AOSP) repository offer the information and source code needed to create custom variants of the Android stack, port devices and accessories to the Android platform, and ensure devices meet the compatibility requirements that keep the Android ecosystem a healthy and stable environment for millions of users.
Click to expand...
Click to collapse
Working
* Touchscreen
* Audio
* Boot
* Bluethoot
* Internal/External storage
* Mtp / Adb
* Sensors
* Wifi
* RIL
* Camera
* NFC
* FP gestures
Click to expand...
Click to collapse
Not Working
* You tell me
Click to expand...
Click to collapse
NOTE: The signal icon is buggy due to Huawei weird ril implementation, I am still looking to fix it over the new Android 10-11 telephony changes.
Installation
* you must have TWRP installed, use this one (make sure to have the unofficial Android 11 one ! )
WARNING: You must be decrypted before installing it otherwise it won't boot. (Read second post.)
* go to TWRP
* format data
* reboot to TWRP again
* do a full wipe (system, data, cache, dalvik/art cache) !
* reboot to bootloader
* extract AOSP 11
* run: fastboot flash system <drag system.img here>
* reboot to TWRP
* resize system
* flash gapps (optional)
* flash NFC.zip
NOTE: this zip is needed for having working NFC. DO NOT IGNORE IT !
* reboot to System
* Enjoy !!!
Click to expand...
Click to collapse
Update
* reboot to TWRP and do a wipe cache, dalvik/art cache
* reboot to bootloader
* extract AOSP 11
* run: fastboot flash system <drag system.img here>
* reboot to TWRP
* resize system
* flash gapps (optional)
* flash NFC.zip
NOTE: this zip is needed for having working NFC. DO NOT IGNORE IT !
* reboot to System
* Enjoy !!!
Click to expand...
Click to collapse
If you are getting Error 70 while flashing gapps just resize system from TWRP !
If gapps are giving network errors or other kind of errors install them after first boot !
Download
AOSP 11 and NFC fix
NikGapps
OpenGapps
Click to expand...
Click to collapse
Please support my work, it's very important! Thanks
DONATIONS
Regards !

NOTES
* For root method read this post, for rooting with magisk read this instead.
* If you face corrupted storage issues you need to go back on emui and re-install the rom.
* I recommend NikGapps core with SetupWizard add-on.
* Use 8.0.0.360 or maximum .400 firmware for booting the rom.
* Gapps can may give "Uncertified device" error and abort the google account login, use this guide to fix it (thanks to @latviandude )
* If you want VoLTE/Wifi Calling working flash this zip
** You must be decrypted for booting this rom **
Before following the installation steps format data and flash this file via TWRP.

Hi, I flashed yesterday AOSP 11via fastboot, storage decrypted with recommanded TWRP using edited fstab.hi6250. Rom seems to work better for me than AOSP 10, screen recorder works, backlight works, already resolved problem with bluetooth(connected/disconnected) by disabling HD Audio in developer options.
Battery drainage while using worries, but it is too early to say, still testing it. There is no way I can get NFC fix working(never could on any custom rom) so obviously I’m doing something wrong. Hope I’ll figure it out.
Thanks @DarkJoker360, great work!
EDIT: Flashing NFC fix worked and it is present in settings(Connected devices), but it's absent in status bar(I can live with that)

Hi . how can i "resize system" ?

piterconlai said:
Hi . how can i "resize system" ?
Click to expand...
Click to collapse
Go to twrp recovery, press "Wipe" Then choose "Advanced Wipe". After that select/check "System" box and then press on "Repair or Change File System" and then you will see down "Resize File System" - press on it and done ur System has been resized.

hardcorehenry said:
Hi, I flashed yesterday AOSP 11via fastboot, storage decrypted with recommanded TWRP using edited fstab.hi6250. Rom seems to work better for me than AOSP 10, screen recorder works, backlight works, already resolved problem with bluetooth(connected/disconnected) by disabling HD Audio in developer options.
Battery drainage while using worries, but it is too early to say, still testing it. There is no way I can get NFC fix working(never could on any custom rom) so obviously I’m doing something wrong. Hope I’ll figure it out.
Thanks @DarkJoker360, great work!
View attachment 5194331 View attachment 5194333
EDIT: Flashing NFC fix worked and it is present in settings(Connected devices), but it's absent in status bar(I can live with that)
Click to expand...
Click to collapse
Hello I would like to ask you some information
- the bluetooth headphones work?
- How's the battery drain going? More or less how many hours of screen does it make?

Added to AOSP 11 accent, font and icon shape picker (like theme picker), now working on an aosp icon pack picker (aka styles) !

piterconlai said:
Hello I would like to ask you some information
- the bluetooth headphones work?
- How's the battery drain going? More or less how many hours of screen does it make?
Click to expand...
Click to collapse
I made more thorough research, hope it’ll be useful for further development.
Battery:
When idle(sleep) it looses 1% overnight, when only screen on battery drain is 1% per 10 min, when only stopwatch on it looses 1% per 5 min. Checked without SIM and brightness level 45%. Now I’m going to let it drain completely and charge again. Maybe this results are normal(right define normal) and needles to worry about.
Bluetooth:
After pair my earbuds automatically trying to switch to aptX audio codec(they have aptX, AAC and SBC support) without success(connected/disconnected again and again), not possible to chose other codec when HD Audio in developer options is enabled. When disabled it automatically chooses SBC(without possibility of change), but this codec works without problems.

hardcorehenry said:
I made more thorough research, hope it’ll be useful for further development.
Battery:
When idle(sleep) it looses 1% overnight, when only screen on battery drain is 1% per 10 min, when only stopwatch on it looses 1% per 5 min. Checked without SIM and brightness level 45%. Now I’m going to let it drain completely and charge again. Maybe this results are normal(right define normal) and needles to worry about.
Bluetooth:
After pair my earbuds automatically trying to switch to aptX audio codec(they have aptX, AAC and SBC support) without success(connected/disconnected), not possible to chose other codec when HD Audio in developer options is enabled. When disabled it automatically chooses SBC(without possibility of change), but this codec works without problems.
Click to expand...
Click to collapse
Thanks for the reply
so can you do 8 h of screen with this rom?
Have you tried if the blutooth smartwatch works by accident?
Last question :
Would it be possible to go back to a previous version if I didn't like it? I am currently using lineage 16 and I am very happy with it

piterconlai said:
so can you do 8 h of screen with this rom?
Click to expand...
Click to collapse
Well you have to calculate yourself from data I provided or flash rom and find out.
piterconlai said:
Have you tried if the blutooth smartwatch works by accident?
Click to expand...
Click to collapse
I don’t have such device.
piterconlai said:
Would it be possible to go back to a previous version if I didn't like it? I am currently using lineage 16 and I am very happy with it
Click to expand...
Click to collapse
If you are more interested in comfort than struggle, testing and help DEV to perfect this rom don’t change anything. Going back means flash and install everything from scratch.

I'm always getting an error when flashing system img via fastboot...
error code : Invalid sparse file format at header magic
The system partition can't be written after the first sparse.
I tried with linux and windows, changed the usb cable but nothing change.
Is there anything to do before this operation except the ones in the insttructions ?

Junkilito said:
I'm always getting an error when flashing system img via fastboot...
error code : Invalid sparse file format at header magic
The system partition can't be written after the first sparse.
I tried with linux and windows, changed the usb cable but nothing change.
Is there anything to do before this operation except the ones in the insttructions ?
Click to expand...
Click to collapse
I’m not sure I also had this warning( Invalid sparse file format at header magic) but after a while flash went from beginning till the end without problems. Two things come to my head: outdated platform-tools or/and you are on wrong firmware(take a look at screenshots DarkJoker 8.0.0.400 and mine 8.0.0.402), but as I said not sure and it’s pure guess from my side. Wait for second opinion.

hardcorehenry said:
I’m not sure I also had this warning( Invalid sparse file format at header magic) but after a while flash went from beginning till the end without problems. Two things come to my head: outdated platform-tools or/and you are on wrong firmware(take a look at screenshots DarkJoker 8.0.0.400 and mine 8.0.0.402), but as I said not sure and it’s pure guess from my side. Wait for second opinion.
Click to expand...
Click to collapse
I have exactly the same problem. Adb also gives me this error, even though it always continues flashing though and also finishes then.
The ROM is however never bootable for me and I can't figure out what I have done wrong. I was on 8.0.0.402 before and used AEX 9 ROM just fine.
What version of TWRP did you use for successful results? I can't find a newer one from pretoriano80 but 3.2.1.0. Maybe that is a problem?
Regards

Friedensfurz said:
I have exactly the same problem. Adb also gives me this error, even though it always continues flashing though and also finishes then.
The ROM is however never bootable for me and I can't figure out what I have done wrong. I was on 8.0.0.402 before and used AEX 9 ROM just fine.
What version of TWRP did you use for successful results? I can't find a newer one from pretoriano80 but 3.2.1.0. Maybe that is a problem?
Regards
Click to expand...
Click to collapse
Hi,
I’ll try exactly step by step how I did it(I’m on macOS so there might be small differences). When on stock after unlocking bootloader and flashing TWRP(took from this post), you need to copy on your external sdcard or USBOTG NFC_fix.zip, gapps(optional) and fstab.hi6250b.zip or edit your own from /vendor/etc like in this post. Boot into TWRP (backup just in case your vendor partition)and either flash fstab.hi6250b.zip(easy way) or replace fstab.hi6250 in /vendor/etc with edited one via TWRP file manager(harder way). After flashing/replacing enter in TWRP into Wipe and Format Data>yes then reboot into TWRP, wipe: cache, dalvik cache and data and reboot into system. You should reboot into ugly looking stock rom. In settings>security>more you should see Encrypt phone that means storage is decrypted. Enable debug and confirm via adb and boot into TWRP. Make backup(ramdisk, kernel, data, system) enter section Wipe>Advanced Wipe and wipe Dalvik/ART Cache, Cache, Data and System. Don’t Format Data again because most probably it'll f*up Internal Storage besides internal storage is already decryptet. Reboot into bootloader. Run in terminal(macOS) or whatever is used in Windows/Linux:
fastboot devices
fastboot flash system drag and drop aosp-11_prague_20210117.img
Reboot into TWRP, resize System if needed, flash NFC_fix.zip and gapps(optional).
Wipe Cache and Dalvik, reboot and that should be all.

Junkilito said:
I'm always getting an error when flashing system img via fastboot...
error code : Invalid sparse file format at header magic
The system partition can't be written after the first sparse.
I tried with linux and windows, changed the usb cable but nothing change.
Is there anything to do before this operation except the ones in the insttructions ?
Click to expand...
Click to collapse
It is a know "issue", just ignore it and boot it.
It is most likely a warning.

DarkJoker360 said:
It is a know "issue", just ignore it and boot it.
It is most likely a warning.
Click to expand...
Click to collapse
Nope it's caused by new version of official firmware for this phone, system partition on newer versions is 2GB on b388 is 3GB.

That would explain why in the past I had troubles reflashing even stock SYSTEM.img via fastboot on latest official firmware. @DarkJoker360 maybe it’s worth mentioning that flashing anything on latest firmware is not advised, and firmware should be downgraded(latest safe confirmed working firmware 8.0.0.402[service rom] or 8.0.0.400 [the same as developer's]).

hardcorehenry said:
That would explain why in the past I had troubles reflashing even stock SYSTEM.img via fastboot on latest official firmware. @DarkJoker360 maybe it’s worth mentioning that flashing anything on latest firmware is not advised, and firmware should be downgraded(latest safe confirmed firmware 8.0.0.402[service rom]).
Click to expand...
Click to collapse
I recommend .360 firmware or .400 (the one I am using)
Newer firmwares with newer security patches may refure to boot due to some Huawei changes for avoiding modding.

Thanks for all of your help. I managed to get AOSP 11 to boot, the reason why it initially just bootlooped for me was that I did not directly come from Stock ROM. Very weird. Following @hardcorehenry 's steps worked fine. Is it somehow possible to get Magisk going on this ROM? I read the AOSP 10 thread and installed the "magisk phh v21.0".zip file, but now I am stuck on the "Your device cannot be trusted, your device is booting" screen. Any ideas for this? Many thanks.

Friedensfurz said:
Thanks for all of your help. I managed to get AOSP 11 to boot, the reason why it initially just bootlooped for me was that I did not directly come from Stock ROM. Very weird. Following @hardcorehenry 's steps worked fine. Is it somehow possible to get Magisk going on this ROM? I read the AOSP 10 thread and installed the "magisk phh v21.0".zip file, but now I am stuck on the "Your device cannot be trusted, your device is booting" screen. Any ideas for this? Many thanks.
Click to expand...
Click to collapse
No magisk at the moment, I'm sticking with A10 untill Magisk 19.3 will work on this rom (need to pass safety net)

[ROM][OFFICIAL][11] LineageOS 18.1 for Galaxy Note10/Note10+/Note10+ 5G Exynos

{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
Follow the instructions on the wiki page for your device https://wiki.lineageos.org/devices/#samsung
Only the provided lineage recovery will be supported, using TWRP might result in a possible data loss!
Note: You may use Odin instead of Heimdall, for this you will need to rename the recovery image to recovery.img and pack it into a tar archive.
Downloads:
Builds: https://download.lineageos.org
GApps: https://wiki.lineageos.org/gapps.html
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Support
Telegram group
Contributors
Linux4
Source Code: https://github.com/LineageOS
Kernel source: https://github.com/LineageOS/android_kernel_samsung_exynos9820

reserved

reserved

What is different between this build and your previous one ?

Big guy, can you come up with a LineageOS that d2q can use, d2q users feel distressed, and there is no rom available

Vishnarov said:
What is different between this build and your previous one ?
Click to expand...
Click to collapse
Read the thread's title ... It's official now.
[email protected] said:
Big guy, can you come up with a LineageOS that d2q can use, d2q users feel distressed, and there is no rom available
Click to expand...
Click to collapse
No, sorry hardware is too different.

builds have been removed from the lineage os website?

Enddo said:
builds have been removed from the lineage os website?
Click to expand...
Click to collapse
Yes, see this for the reason
This affected all devices so builds of last few days were pulled and sadly we had only that one build yet
There will be new ones next week

Does the build support hardware encryption or software encryption?

You should put what models this is for as to avoid confusion

just flashed the recovery image via heimdal (got recovery upload success message), but when I try to boot into recovery mode (or even just boot into Android now) I get pushed into download mode with a 'dt load fail' message at the top
says dt entry not found
load kernel could not do normal boot
error verifying vbmeta image - hash mismatch

Enddo said:
just flashed the recovery image via heimdal (got recovery upload success message), but when I try to boot into recovery mode (or even just boot into Android now) I get pushed into download mode with a 'dt load fail' message at the top
says dt entry not found
load kernel could not do normal boot
error verifying vbmeta image - hash mismatch
Click to expand...
Click to collapse
I recall getting a vbmeta error too and I think it was a locked bootloader issue? Not sure. Definitely a d2s model?
I just reflashed stock and started again. Long press the volume up button at download selection to unlock bootloader.
I'm fairly sure Odin accepted the recovery file if you convert it to .tar. and disable auto reboot so you can button combo directly to recovery. From there install the main ROM zip.
ROM runs fine, few thing missing that I needed so came away from it unfortunately.

CerebralFlex said:
I recall getting a vbmeta error too and I think it was a locked bootloader issue? Not sure. Definitely a d2s model?
I just reflashed stock and started again. Long press the volume up button at download selection to unlock bootloader.
I'm fairly sure Odin accepted the recovery file if you convert it to .tar. and disable auto reboot so you can button combo directly to recovery. From there install the main ROM zip.
ROM runs fine, few thing missing that I needed so came away from it unfortunately.
Click to expand...
Click to collapse
certainly no locked bootloader here (have had it unlocked since right after I bought it at launch)
but yea, I'm going to try and reflash the ROM and start from scratch. I was on an outdated version of ONe UI (maybe from December) so maybe that was part of the issue
EDIT - oddly enough, I couldn't get LOS recovery installed via Odin. I tried, got success messages, but a reboot into recovery mode just showed stock recovery (I wasn't missing the button combo, to my knowledge). tried a few times before going back to using heimdall
the second attempt (with a fresh install of OneUI's latest firmware) helped me get past that vbmeta error with heimdall
got LOS recovery installed, the ROM sideloaded, and I'm up and running
thanks for the hard work @Linux4 (and all others involved in working on lineageos)

First, thanks a lot for your work and for making it official, @Linux4 !
One question: I'd like to use MicroG instead of the google stuff. But since I'd rather keep it all simple, I'd not use Magisk, if possible. Is there a recommended and/or simple way to get the signature spoofing patch into this rom? Preferably so that OTA updates still work? Would NanoDroid in system mode work?

Phosphoros said:
First, thanks a lot for your work and for making it official, @Linux4 !
One question: I'd like to use MicroG instead of the google stuff. But since I'd rather keep it all simple, I'd not use Magisk, if possible. Is there a recommended and/or simple way to get the signature spoofing patch into this rom? Preferably so that OTA updates still work? Would NanoDroid in system mode work?
Click to expand...
Click to collapse
I guess the best way here would be waiting until there's a build for your device on https://lineage.microg.org/ (they build for all officially supported devices)

is the bug with registering a fingerprint common? I noticed the issue after I first installed it but then was able to add one very quickly
had to format /data to record a tutorial and after installing the build again, I can't seem to get past the fingerprint register issue I noticed before

Enddo said:
is the bug with registering a fingerprint common? I noticed the issue after I first installed it but then was able to add one very quickly
had to format /data to record a tutorial and after installing the build again, I can't seem to get past the fingerprint register issue I noticed before
Click to expand...
Click to collapse
It is not broken or whatever, see this from my telegram group in case you just don't figure it out on your own:
If fingerprint enrollment fails for first fingerprint do the following to get it working (doesn't apply to beyond0lte):
1. Retry adding fingerprint but this time tap fast and don't press too hard when putting your finger on the sensor for the first time
2. Repeat step 1 until enrollment continues without error
3. After that it will work fine and doesn't need any special handling anymore
Click to expand...
Click to collapse
All samsung devices using FOD have that issue it seems, only on first enrollment tho, after that it's completely fine

Linux4 said:
If fingerprint enrollment fails for first fingerprint do the following to get it working (doesn't apply to beyond0lte):
1. Retry adding fingerprint but this time tap fast and don't press too hard when putting your finger on the sensor for the first time
2. Repeat step 1 until enrollment continues without error
3. After that it will work fine and doesn't need any special handling anymore
Click to expand...
Click to collapse
EDIT - was able to get it working through a factory reset with the 'tap fast' being the key thing. it needs to fail that first attempt or something?
but it's quite quick once that hassle is over with

Enddo said:
this worked for me on my first install. describes my exact experience
but yea, it's not working right now. you need a logcat or something?
it's immediately throwing up the enrollment error message right when it attempts the first scan (every time)
Click to expand...
Click to collapse
No need for a logcat, it does work, for retrying you will need to close settings completely, just going *back* is not enough (HAL will stay in that error state)
I'm 100% sure you didn't do so also it works for everyone else

Linux4 said:
I guess the best way here would be waiting until there's a build for your device on https://lineage.microg.org/ (they build for all officially supported devices)
Click to expand...
Click to collapse
Ok, thought about waiting for this ... thanks for confirming it!

[ROM][13][UNOFFICIAL][redfin] Evolution-X 7.2 | Unbound | TP1A.221005.002

{
"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 am not affiliated with the official Evolution-X ROM developers
Updated for October 2022
Signed with my own keys
some features you may be used to from this ROM are not available (yet), I'm assuming it just takes time for the developers to add them to the still relatively new Android 13/tiramisu. If I have time, I'll see what I can do.If something is missing, it's not due to me excluding anything.
The Camera and Bluetooth are working fine now, I noticed in my last version I posted here last week for 220905 they were broken.
Kernel Source
Device, Kernel and Vendor Repos
Downloads
Instructions:
Flash the vendor_boot and boot
Sideload the ota in recovery

thank you

Can I flash from android 12?

Kings Android said:
Can I flash from android 12?
Click to expand...
Click to collapse
I think so but I was on stock Google 13 when I did mine.

Kings Android said:
Can I flash from android 12?
Click to expand...
Click to collapse
I was able to flash from the Android 12 image without issue.
The only thing I'm trying to figure out now is what's draining my battery. I've re-flashed clean this morning so I'm monitoring the battery usage to see what is consuming battery while idle.

twykomantis said:
I was able to flash from the Android 12 image without issue.
The only thing I'm trying to figure out now is what's draining my battery. I've re-flashed clean this morning so I'm monitoring the battery usage to see what is consuming battery while idle.
Click to expand...
Click to collapse
I personally haven't noticed a large drain in battery while idle on a13 evo-x but I did have that problem before I updated directly from 12. I put com.android.hbmsvmanager on restricted battery usage and it solved the problem. Maybe this will help on 13??

HI aleph.mercury,
on my P5 i flashed your ROM but WiFi / WLAN and mobile Data won't work.
Before I was on Stock Android 13 October 2022 Build, flashed the both boot images with slot all, I did an factory reset and then I installed the ROM and afterwards Wifi and mobile Data won't work.
Do you have any ideas how to solve this?
regards
EDIT: got it fixed, reflashed all the other stock partitions via flash.bat

Raz0Rfail said:
HI aleph.mercury,
on my P5 i flashed your ROM but WiFi / WLAN and mobile Data won't work.
Before I was on Stock Android 13 October 2022 Build, flashed the both boot images with slot all, I did an factory reset and then I installed the ROM and afterwards Wifi and mobile Data won't work.
Do you have any ideas how to solve this?
regards
Click to expand...
Click to collapse
Did you flash vendor_boot image with correct command?

Yep:
fastboot.exe flash boot boot.img --slot all
fastboot.exe flash vendor_boot vendor_boot.img --slot all
But I fixed it and thanks for the fast response .

just a heads-up any AT&T users will need flash this via magisk to get calling to work. This is also true with evo-x a12 rom for pixel 5. https://forum.xda-developers.com/t/mod-magisk-root-volte-enabler.4372705/

Rookie Question: how and when do I factory reset while installing this rom? I have never flashed a rom this way before and I want to make sure I do it right.

elong7681 said:
Rookie Question: how and when do I factory reset while installing this rom? I have never flashed a rom this way before and I want to make sure I do it right.
Click to expand...
Click to collapse
After flashing the boot.img and vendor_boot.img files you enter recovery and there is an option factory reset. Once you've done this you must reboot to recovery and adb sideload the rom and that's it. Make sure you keep an eye when installing the rom. I think around 47% it will ask you if you wish to continue with the flash on your phone screen. Tap yes and then it will flash the rest of the way. After this just reboot system and go through the rom setup like it's a brand new phone and welcome to Evo-x 13
TMI I'm sure but just thought I'd take you through it as best I can

DroidRommer said:
After flashing the boot.img and vendor_boot.img files you enter recovery and there is an option factory reset. Once you've done this you must reboot to recovery and adb sideload the rom and that's it. Make sure you keep an eye when installing the rom. I think around 47% it will ask you if you wish to continue with the flash on your phone screen. Tap yes and then it will flash the rest of the way. After this just reboot system and go through the rom setup like it's a brand new phone and welcome to Evo-x 13
TMI I'm sure but just thought I'd take you through it as best I can
Click to expand...
Click to collapse
Thanks for the response

To anyone noticing idle battery drain I stumbled across a magisk module called AOSP Enhancer it's supposed to tweak the kernal to be more AOSP friendly and definitely helps the battery in my opinion!
Just flash in magisk and reboot. Once booted you can open your file explorer app and navigate to / storage/emulated/0/Android. Here you will see aosp_enhancer.txt if you open this you will see something like the pic I posted
your phone may get kind of warm for about 10 or 15 mins while the module makes the tweaks but after that it will run like normal and hopefully you'll be thanking me. but for real I took my pixel off charge at 10am this morning and I'm still at 72% 13 hours later!
If this doesn't work for you pls let me know!
Thanks

DroidRommer said:
To anyone noticing idle battery drain I stumbled across a magisk module called AOSP Enhancer it's supposed to tweak the kernal to be more AOSP friendly and definitely helps the battery in my opinion!
Just flash in magisk and reboot. Once booted you can open your file explorer app and navigate to / storage/emulated/0/Android. Here you will see aosp_enhancer.txt if you open this you will see something like the pic I posted
your phone may get kind of warm for about 10 or 15 mins while the module makes the tweaks but after that it will run like normal and hopefully you'll be thanking me. but for real I took my pixel off charge at 10am this morning and I'm still at 72% 13 hours later!
If this doesn't work for you pls let me know!
Thanks
Click to expand...
Click to collapse
Did you stumble onto safetynet passing issues using magisk with evox13 ? Just checking before I load magisk onto mine

Crazyaboutroms said:
Did you stumble onto safetynet passing issues using magisk with evox13 ? Just checking before I load magisk onto mine
Click to expand...
Click to collapse
As long as you flash the latest safety net fix module in magisk you'll be fine

DroidRommer said:
just a heads-up any AT&T users will need flash this via magisk to get calling to work. This is also true with evo-x a12 rom for pixel 5. https://forum.xda-developers.com/t/mod-magisk-root-volte-enabler.4372705/
Click to expand...
Click to collapse
I added the items found in this magisk module's system.prop to this ROM, it should automatically be there in the November update. You won't have to be rooted or use magisk next time
I'm on Verizon and was missing WiFi calling as well without the module
Crazyaboutroms said:
Did you stumble onto safetynet passing issues using magisk with evox13 ? Just checking before I load magisk onto mine
Click to expand...
Click to collapse
this ROM should pass safety net rooted or not.
if you are rooted, it's possible to ruin this status by remounting the system partition RW while trying to build and install custom WiFi kernel modules on the phone in a live environment. if you do something like that, you can still pass safety net again if you use the magisk module by kdrag0n and/or the props module by didgeridoohan.

aleph.mercury said:
I added the items found in this magisk module's system.prop to this ROM, it should automatically be there in the November update. You won't have to be rooted or use magisk next time
I'm on Verizon and was missing WiFi calling as well without the module
this ROM should pass safety net rooted or not.
if you are rooted, it's possible to ruin this status by remounting the system partition RW while trying to build and install custom WiFi kernel modules on the phone in a live environment. if you do something like that, you can still pass safety net again if you use the magisk module by kdrag0n and/or the props module by didgeridoohan.
Click to expand...
Click to collapse
Thank you for this! I really appreciate you integrating that module for calling. Sorry I had no idea about the safety net thing Its pretty much just habit for me to flash the module in magisk at this point lol. Just cuz you mentioned kernels is there any chance there will be anymore cpu governors added in the future such as interactivex or anything like it? I like tweaking everything lol

I think if you want to tweak kernel parameters there's already apps that can do that; is there's kernel features you want available (such as wireguard kernel module (which I already added), a specific WiFi driver, Bluetooth feature, HID) I think I can make those available.
if you download my kernel repo on your PC (or any LINUX kernel for that matter), then navigate to it (cd kernel/Google/redbull) then type "make menuconfig" in the CLI, a GUI will show you all the available kernel settings. load the following arch/arm64/configs/redbull_defconfig from within the GUI, make changes and save. You can add the kernel to your boot.img , check out my first thread for this ROM from July/August for detailed instructions on how to use the Android boot image editor on how to replace the kernel using that technique

aleph.mercury said:
I think if you want to tweak kernel parameters there's already apps that can do that; is there's kernel features you want available (such as wireguard kernel module (which I already added), a specific WiFi driver, Bluetooth feature, HID) I think I can make those available.
if you download my kernel repo on your PC (or any LINUX kernel for that matter), then navigate to it (cd kernel/Google/redbull) then type "make menuconfig" in the CLI, a GUI will show you all the available kernel settings. load the following arch/arm64/configs/redbull_defconfig from within the GUI, make changes and save. then build the kernel. You can add the kernel to your boot.img , check out my first thread for this ROM from July/August for detailed instructions on how to use the Android boot image editor on how to replace the kernel using that technique
Click to expand...
Click to collapse

[ROM][Huawei][13] LeaOS - Lineage 20.0 for Huawei device (EMUI 9.1 version)

Non-Official Lineage 20.0 for EMUI 9 Huawei (ANE, FIG, POT, VTR, STF)
{
"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"
}
LeaOS is a project which based on LineageOS 20.1 with Andy Yan's and TrebleDroid GSI patches. I have added my personnals patches for Huawei devices : Encryption, Signal Strengh, Speed Boot, Assisted GPS, NFC, CAST/Miracast, Media App fixes, Camera HDR, SafetyNet etc..)
Changelog :
LeaOS Maarch 2023 version
Move to Android r35 (SPL Maarch)
Add offline charging
Add spoof model to pass safetynet
LeaOS February 2023 version
First release
Pre-requisite :
You must have TWRP installed if you want install patch. and a phone with unlock bootloader
Installation (crypt or uncrypt)
Download the version that corresponds to your Huawei phone model here and extract img file. You can choose with ou without GoogleApps
Flash system image : fastboot flash system <drag system.img here>
Flash twrp image: fastboot flash recovery_ramdisk <drag twrp img here>
Boot into twrp: power + vol+ while NOT connected to pc
Resize system: Wipe > Advanced Wipe > System > Repair or Change File System > Resize File System > Swipe
Wipe cache, dalvik/art cache, internal storage, data
(option) Install DRM patch for EMUI 9.1 to support DRM : 8-Huawei-FixPreav-AB-v1.3-signed.zip
(option) Install single modem patch for multi-sim device : 11-Huawei-MonoSim-AB-v1.1-signed.zip
reboot to System and set up the phone with Lineage first start assistant.
Enjoy !!!
Source Code:
https://github.com/Iceows
ROM OS Version: Android 13
ROM Kernel: Linux Huawei 4.9.148
ROM Firmware Required: EMUI 9.1
Based On: Lineage 20.0 and TrebleDroid
Credits:
@Frax3r (Testing)
@PHH
@eremitein
@RakinTheGreat (GCam)
@TureX (Kernel)
And all the others who tested my patches and helped me improve this ROM
Support Group
Channel update

Good news, I had just installed the 23/2/23 release and was going really good, except for the SIM card PIN request which was causing bootloop.After removed the PIN of the SIM card I was haven't any problem for the ROM which was running fine, but I could't fix a problem with mobile data which were not working even after re-set the correct APN and check with the dial number on phone info.
After all that I see the new release that I'm going to install RN.
Thanks for your work. Keep it UP!

I will try to fix this pin code and data problem. This is a problem that affects all dual sim huawei. Are you on dual sim?

AltairFR said:
Flash twrp image: fastboot flash recovery_ramdisk <drag twrp img here>
Click to expand...
Click to collapse
Is TWRP for Stanford (Honor 9) exist? Thanks

Smith Huang said:
Is TWRP for Stanford (Honor 9) exist? Thanks
Click to expand...
Click to collapse
Yes here
altairfr-huawei - Browse /TWRP-Recovery at SourceForge.net
sourceforge.net

AltairFR said:
I will try to fix this pin code and data problem. This is a problem that affects all dual sim huawei. Are you on dual sim?
Click to expand...
Click to collapse
Yes, It's a dual SIM phone. I have just one in it.Anyway I tried the no_gapps version and have not problem with data connection. I think is possibile it is a problem gapps related. Anyway I installed the new release with no gapps and installed LiteApp and works fine.

AltairFR said:
Yes here
altairfr-huawei - Browse /TWRP-Recovery at SourceForge.net
sourceforge.net
Click to expand...
Click to collapse
Thanks again!

It is so great to know that someone is still creating and maintaining honor 9 roms. However, I found a problem in this rom. I am a user from China and using China-mobile customized version STF-TL10 (Though I flashed it to normal China version of base firmware which is STF-AL10 EMUI:9.1.0.225, they are almost the same by the way.). I found there are 3 minor problems and my soloution to them, hope these information are useful to you:
1. rom with Gapps seems too big to flash into system partition, both TWRP and fastboot would just stop flashing process. I don't know why, but the non Gapps version plus "MindTheGapps-13.0.0-arm64-20221025_100653" works for me.
2. Battery Guru app and my own feeling about how fast is battery runs out indicate that the system can't enter deepsleep state and I think that is because of the kernel (maybe Kernel Suspending is not working). I flashed a custom kernel (https://github.com/maimaiguanfan/android_kernel_huawei_hi3660 I attached the file I used below) into the system by TWRP, then everything looks like it works normally.
3. developer USB debug mode will not work if you just turn it on until a system restart being applied. It is just a little bit annoying and I hope others get to know about this, so you won't waste time checking what is wrong...
Thanks for your hard work again! Have a nice day!

Is this project dead or is it in development

Not dead why ?

AltairFR said:
Not dead why ?
Click to expand...
Click to collapse
Oh ok cause I might install it

xqqy said:
It is so great to know that someone is still creating and maintaining honor 9 roms. However, I found a problem in this rom. I am a user from China and using China-mobile customized version STF-TL10 (Though I flashed it to normal China version of base firmware which is STF-AL10 EMUI:9.1.0.225, they are almost the same by the way.). I found there are 3 minor problems and my soloution to them, hope these information are useful to you:
1. rom with Gapps seems too big to flash into system partition, both TWRP and fastboot would just stop flashing process. I don't know why, but the non Gapps version plus "MindTheGapps-13.0.0-arm64-20221025_100653" works for me.
2. Battery Guru app and my own feeling about how fast is battery runs out indicate that the system can't enter deepsleep state and I think that is because of the kernel (maybe Kernel Suspending is not working). I flashed a custom kernel (https://github.com/maimaiguanfan/android_kernel_huawei_hi3660 I attached the file I used below) into the system by TWRP, then everything looks like it works normally.
3. developer USB debug mode will not work if you just turn it on until a system restart being applied. It is just a little bit annoying and I hope others get to know about this, so you won't waste time checking what is wrong...
Thanks for your hard work again! Have a nice day!
Click to expand...
Click to collapse
Good morning .
For partition size problems, it happens often, so I have developed a program to resize the system partition. He is on xda looking for Huawei partition tools.
For the battery I will look on my stf-l09. Have you tested with the aosp version of leaos?
For the USB problem, I did not see this problem.. thank you for the tests

Is this os pre-rooted? Cause I still wanna watch Netflix and stuff

uncognic said:
Is this os pre-rooted? Cause I still wanna watch Netflix and stuff
Click to expand...
Click to collapse
This OS have an option to pass safetynet, so you can use netflix

When i go to download recovery, im not sure which one to download between twrp-3.5.2-v1-figo-emui9.img, twrp-3.7.0_9-0-anne.img and twrp-3.7.0_9-0-anne.img. I have a Honor 9 STF-L09

With the last leaos, you can flash without twrp

Wait what. But the step-by-step giude asks me to flash twrp for a patch

uncognic said:
Wait what. But the step-by-step giude asks me to flash twrp for a patch
Click to expand...
Click to collapse
It is for drm and i don"t know if stf need
Use this twrp :
https://sourceforge.net/projects/altairfr-huawei/files/TWRP-Recovery/twrp-stf-ki960.img/download

xqqy said:
It is so great to know that someone is still creating and maintaining honor 9 roms. However, I found a problem in this rom. I am a user from China and using China-mobile customized version STF-TL10 (Though I flashed it to normal China version of base firmware which is STF-AL10 EMUI:9.1.0.225, they are almost the same by the way.). I found there are 3 minor problems and my soloution to them, hope these information are useful to you:
1. rom with Gapps seems too big to flash into system partition, both TWRP and fastboot would just stop flashing process. I don't know why, but the non Gapps version plus "MindTheGapps-13.0.0-arm64-20221025_100653" works for me.
2. Battery Guru app and my own feeling about how fast is battery runs out indicate that the system can't enter deepsleep state and I think that is because of the kernel (maybe Kernel Suspending is not working). I flashed a custom kernel (https://github.com/maimaiguanfan/android_kernel_huawei_hi3660 I attached the file I used below) into the system by TWRP, then everything looks like it works normally.
3. developer USB debug mode will not work if you just turn it on until a system restart being applied. It is just a little bit annoying and I hope others get to know about this, so you won't waste time checking what is wrong...
Thanks for your hard work again! Have a nice day!
Click to expand...
Click to collapse
Huawei Partition Kit - Enlarge system partition
Huawei Partition Kit This kit allows you to enlarge/reduce (2Go->5Go) the system partition on a Huawei kirin 65x, 960 or 970 phone. You can do it from a Huawei android 9 rom, a Lineage 18.1, 19.1, 20, or an AOSP 11,12 or 13. The kit reinstalls...
forum.xda-developers.com

Hi,
I gave this ROM a spin, but didn't get very far in the process documented in the FP.
First flashed TWRP from here with fastboot to recovery_ramdisk.
Code:
$ fastboot flash system LeaOS-20.0-20230304-iceows-google-stf.img
Invalid sparse file format at header magic
Sending sparse 'system' 1/7 (460241 KB) OKAY [ 11.774s]
Writing 'system' FAILED (remote: 'sparse flash write failure')
fastboot: error: Command failed
I also tried to flash from twrp with adb sideload, but that fails instantaneously.
And now I'm stuck with a phone that won't boot. Any suggestions how to proceed?
Btw, device is an STF-L09.

Database Info

welcome