Related
{
"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"
}
The Full Treble Project for MI5 Gemini
Brought to you by Jflte DevConnection Team
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this TREBLE
* SUPPORT before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
What is Project Treble:
Project Treble basically partitions your device into two separate partitions, a system and a vendor: system contains your generic system image, while vendor partition has your device specific files required for booting and running your phone. This way we can easily change the system image and be able to run our device on different system images with the same kernel and vendor partition
Read more about Project Treble
Gemini hardware vs Treble implementation:
Gemini is an ARM64 and A-ONLY device. This means that regarding the GSI images (GSI = Generic System Image) to be used, you need to get ARM64 and A-ONLY system images.
Available GSI downloads:
Up today, thanks to @phhusson and other devs, are available a bunch of Android 9.0 system images that can be flashed on Gemini.
You can find these Gsi at the following links:
- ANDROID Q (Gsi)... Is just a preview... but it works on our Mi5!!
- Phh AOSP 9.0 (Gsi).
- Resurrection Remix v7.0 (Gsi).
- LineageOS 16.0 (Gsi).
- HavocOS v2.0 (Gsi) (Use A only).
- ViperOS v6.0 (Gsi) (Use A only).
- JDC AOSP 9.0 (PURE AOSP Gsi, built from sources, just for testing purpose, no gapps support for this preview version).
- GSI & sGSI List page
Treble implementation and download:
JDCTeam is working from latest months of 2017 to implement on Gemini (un-supported from producer) the full support of Treble.
Thanks to @sir mordred, we reached on MI5 the full working status... from v5 we moved to full versioned vndk v28 (aka PIE support... and Q ready!).
NOTE: just to be clear, it's a work in progress development...
We tested with some available Gsi and we put over here some links to these images.
We are sharing a TWRP flashable zip that include vendor and boot images (flash only through TWRP 3.2.3-0 Official).
NOTE: ONLY with TWRP 3.2.3-0 version is possible to handle the treble flash!
How to use:
Download the TREBLE zip provided here: Mediafire
Download a GSI image (Remember: ARM64 and A-ONLY version)
Reboot to recovery (TWRP 3.3.1-0 REQUIRED)
Clean the device (wipe Dalvik/Cache/System/Data partitions)
Flash Treble gemini zip
Flash the GSI system image you wish to use
Reboot
---> Video on How to install <---
Screenshots:
Youtube review: (To Be Updated when new links available)
- ANDROID Q Gsi on MI5 (How to Install) ---> Click here to play the video
- ANDROID Q Gsi on MI5 ---> Click here to play the video
- RR v7.0.0 Gsi on MI5 ---> Click here to play the video
- PHH AOSP 8.1 Gsi on MI5 ---> Click here to play the video
- AEX 8.1 Gsi on MI5 ---> Click here to play the video
What's working (... and not working):
The development is now @ an RC status (this is not a rom)... you have the possibility to have a look and test the phone with a GSI rom... let us know what does not work (not related to the GSI itself)!!
Issue reporting:
We already say that this is not the place to report issues or bugs ROM related... but in any case a bug encountered can be linked to the treble support not perfect or missing supported features... be free to post about issues you encountered, and please provide logs with the description of the issue. We will check the logs to understand the reason, and in case of fixes to be done, we will update on post#3 (MISCELLANEA) a kind of todo list for us and for users as a "bug list"... but the meaning is "what has to be checked/fixed to get a better treble support for future".
Any question?
If you have any question about, please check first on the post#2 (FAQ) to see if your question has already an answer... if not, post in the thread and we will give you informations.
Sources
GitHub
Social
YouTube: JDCTeam TV
XDA News: Read article
Credits
JDCTeam
LinageOS
Google
MI5Devs
Special thanks:
@sir mordred (developer)
@musabcel (for his test support)
Team Codefire - JDCTeam-Build03
XDA:DevDB Information
GEMINI Full Treble support project, ROM for the Xiaomi Mi 5
Contributors
smeroni68, sir mordred, mzo, ktulu84
Source Code: https://github.com/Project-Treble-Mi5
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: Latest available
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: v6
Stable Release Date: 2019-03-16
Created 2018-03-10
Last Updated 2019-06-27
FAQ Section...
This is the FAQ (Frequently Asked Questions).
Have a look here before asking in the thread... in the worst case you will not find the answer you are searching!
If this section is useful for most users needs, I'll be glad to continue investing time to update this Q/A list!!
Q1:Fingerprint wake/home button works?
A: Yes, now we have the complete support and this feature is available on standard GSI roms (treble support is ready for it)
Q2: How can I revert back from treble to custom ROM whenever required?
A: Just flash the custom rom you like from TWRP and that's all. Custom rom flash will overwrite the boot.img,system and vendor partitions.
Q3: If I revert to a Custom rom, what I need to do to restore treble support?
A: Just flash the Treble zip through TWRP as the first time. Treble support need boot.img and vendor.img to be installed into the phone... nothing more... nothing less...
Q4: Phh GSI rom is quite poor in functionality. Why?
A: The purpose of Phh GSI AOSP rom is not to be a custom/featured rom. It is an experimental project that is born to have a common rom (better to say the same system.img) usable on many devices with treble support.
This support can be native, acquired after an Oreo original update or as we have done a custom integration on an "unsupported" device.
The meaning today of using a GSI rom is not to be a perfect rom for dayly use... or let's say, it can be a dayly rom only for users that like pure vanilla code.
In future we hope that many others custom roms will move to be a GSI (as JDC will try to do), so we will have the treble base to use these new project also on our devices.
Q5: If a new version of treble support is out, did I need to flash it or not?
A: Our project is on the way. This means that if is available a new update from us, it is for sure an enhancement with more support of feature or fixes.
In case you will need to install a GSI rom, check always here if there is any new version and get it.
In case you are running a custom rom without treble support, DO NOT update with treble flash, because most probably you will break your current installation.
Treble flash is 100% safe from the phone point of view... isn't safe for your current installation!! Why? Mainly because your current boot.img will be overwritten with treble support... 99% you will get a bootloop with a not treble rom!
Q6: How to get ROOT on phh gsi?
A: Firstly download the phh-gapps-su image. After installation, go to the market and install "phh superuser" app to manage the su access for the apps that need it. In the other cases, you can flash from TWRP the correct Magisk zip to gain root.
Q7: Where I can find the GSI images available?
A: Have a look in the OP post over here... there you can find the available ones. In any case here the LINK to the Treble Enabled Device Development section on XDA or here on GSI & sGSI List page
Q8: Everytime I entered the password, it says Decryption Unsuccessful!
A: You have internal SD encrypted. If after MIUI stock, you haven't FORMATTED the internal SD (FORMAT is not WIPE... Format will erase all data and files from the phone, so you must know what you are doing before formatting), the phone result as encrypted, so the rom is asking the password to decrypt the datas... Decryption Unsuccesful clearly states that the decryption procedure is not working. Post about the issue on the GSI rom you are using and provide logs to the developer to help digging the problem... if Developer will answer that encryption is not supported, you can only do one thing: backup all your data, files and pictures on an external storage (eg. a PC) and procede with a FORMAT DATA from TWRP to "destroy" the encryption and "free your phone from it"!
Q9: Is Google Camera working on Gsi?
A: Yes. But remember you need to install gapps package to let gcam works as it should.
We tested Gcam up to v6.1.021 on AOSiP Gsi. If you have greenish selfies pics, go in the Settings -> Fix ->and enable the fix for Front Camera and reboot. For SlowMotion, set 120fps.
Q10: Why can't flash a micro gapps and only pico is flashable?
A: If you get an error of Insufficent space on system partition, you need to resize the partition. Do in this way:
Flash the SYSTEM.IMG you wanna use (select a Vanilla based one)
Reboot to RECOVERY
MOUNT the SYSTEM partition
Go in WIPE menu -> ADVANCED WIPE -> select SYSTEM from the list and press the button REPAIR OR CHANGE FILE SYSTEM
select RESIZE FILE SYSTEM
than SWIPE to execute the command...
in case of error (you will see in red), repeat the RESIZE until it goes completed (Resizing... Done)
After this operation, the system partition will be resized to his maximum dimension (on Mi5 is around 2992MB)
before the installation of gapps package, do a REBOOT to recovery and after MOUNT the SYSTEM partition (check that it is really mounted)
Now you can flash the micro gapps without problem.
Q11: Is there any Magisk version working on Treble gsi?
A: Yes, you need to get v18.1 version or newer with treble support (check around).
Q12: VoLTE is working[/B]?
A: Yes. Install this ims.apk to use it!
Q13: ADB Logs are needed in case of Issue reporting...
A: In case you need help and want report an issue (eg. a boot problem), we need logcat of the phone. Just as sample, we report here what to do (but you must able to do by yourself... we are not giving help on how to do...)
prepare a PC (with adb package to support debug via usb connection)
flash on the phone our treble and the GSI image (just these 2 files, not any patch or other stuff)
reboot the phone
connect the usb cable
after the Mi logo screen, wait to hear from PC a sound that means the usb periferial has been recognised
go in a command window and type:
--> adb devices (if the phone is connected, you will see the code written after the command executed)
--> adb shell logcat > bootlog.txt (this will start real time recording of logs into the pc in the bootlog.txt file)
--> when the phone has completed boot/reboot (eg. a boot loop or fastboot), you need to press Ctrl+C from keyboard to stop log recording.
send attached to the issue description post the bootlog.txt
...let's dev check what's happening by reading the logcat.
... list will be updated...
Miscellanea...
Download (public versions history)
Here you can find the shared folder with all the version released of Treble support: GEMINI-TREBLE
Changelog's
v6 (20190316) - Release Candidate 2 full versioned_vndk v28
- VERSİONED_VNDK support is fully implemented
- FIXED NFC support
- FIXED Ambient Display main icon size and settings menu icons style... Thanks to Subezhj for helping fixing.
- FIXED ConfigPanel - Fingerprint settings menu icons style
v5 (20190308) - Release Candidate full versioned_vndk v28
- VERSİONED_VNDK support is fully implemented
- Mostly all library dependencies between system/vendor which are called as violations against treble's rule are succesfully eliminated
- Updated kernel as per treble's kernel docs (enforced)
- Vendor image's version is now 28
- Misc updates and fixes
- GSI Pie roms support (check in OP for some links)
- JDC PIE GSI rom given just as a preview for testing (JDC PIE GSI is build from sources without ANY hack!!)... It's pure AOSP as Google bring to their devices... NOTE: No support for gapps... they do not complete setup... you are advised.
v4 (20180409) - Beta partially versioned_vndk with the following updates:
- VERSİONED_VNDK support is partially implemented
- Lots of library dependencies between system/vendor which are called as violations against treble's rule are succesfully eliminated, only small number of lib dependencies which needs to be resolved are left
- Updated kernel as per treble's kernel docs
- Vendor image is now using google's stock vndk-sp, ll-ndk libs which are called as treble layer libs
- Vendor image's version is now 27.1.0
- Misc updates and fixes
v3 (20180329) - Beta status with the following updates:
- Updated camera Hal from latest qualcomm 8996 repo
- Hexedited more libs and removed more vendor system dependency (better treble and preparation for versioned vndk)
- Updated wifi configs from lates CAF
v2 (20180318) - Still alpha build with the following updates:
- Upstreamed kernel
- Hexedited blobs to correct path (for treble)
- Linker issues fixed
- Vendor overlays
- Latest device tree updates from CAF and miui oreo beta
- Disabled non-working apps (custom xiaomi doze package and configpanel app which were designed to work with LOS APIs)
- Disabled userspace thermal hal initialization which we dont have in cameraHal (faster cam launch)
- Increased jpeg quality parameters
- other misc. dev tree updates
v1 (20180310) - Initial release (Alpha)
Reported/Known Issues
- Camera works perfectly, but on some apk after a shot is taken with Flash active, the camera do not get more pictures... Close the app will clear the issue and you can get other pictures! Suggestion: do not use the flash with this camera apk if you have the issue! ... or use a working camera apk (is a better solution)!
to be updated...
Big thanx and credits also goes to @smeroni68
All of the story is started with the identifying unused CUST partition which xiaomi left on our device Mi5 https://forum.xda-developers.com/showpost.php?p=74702470&postcount=300
And after we determined that the /cust partiton is unused on AOSP roms, we used it as /vendor partition as per the requirement of Full-Treble https://github.com/sirmordred/android_device_xiaomi_gemini-twrp/commit/5faf9c4e162e8144b71f87d6d21c384931b1ac0c nearly 3 month ago
And that is also the reason of nearly all devices which get Full-Treble support via custom implementation, are Xiaomi devices (Redmi Note 4, Mi5S and our Mi5)
Thanx also to my teammates who contributed this project :good:
Our goal is now separating/isolating all vendor <=> system interactions (which will be enforced on future android releases for treble devices) and stabilizing vendor.img while getting closer to pure AOSP sources
Enjoy
...
...
Finally we are out for both MI5 and MI5S... yeah... now let's go ahead...
Thanks for all JDCTeam
Great Job dude! Finally we got treble. Downloading now. Can't wait flashing.
通过我的 MI 5 上的 Tapatalk发言
Thank you Sir, downloading now
Great news ..only one query .. How can I revert back from treble to custom ROM whenever required?
kishan314 said:
Great news ..only one query .. How can I revert back from treble to custom ROM whenever required?
Click to expand...
Click to collapse
Good question... I'll report also in post#2 in FAQ section.
Q: How can I revert back from treble to custom ROM whenever required?
A: Just flash the custom rom you like from TWRP and that's all. Custom rom flash will overwrite the boot.img and the system partition... vendor partition will stay there waiting for your next test!
So... P GSI is coming for the "old" Mi5. Thank u guys! This is the way
atembleque said:
So... P GSI is coming for the "old" Mi5. Thank u guys! This is the way
Click to expand...
Click to collapse
This is something we can try to build... but only when sources of P will be released and will be good to build an AOSP based on them...
Very very thankful
Thanks for your hardwork, downloading now.
When charging, the battery icon won't show. The bug is phh's?
Sent from my MI 5 using Tapatalk
Installed. Yeap, we finally got a vanilla android
For first alpha, it working flawlessly.
Some bugs i founded.
1. After magisk install on stock kernel, got bootloop. Fixed after installing AEXMod latest kernel.
2. Gcam not working. buildprop (vendor folder) doesnt help. Got FC anyway
3. HMP... stock governor settings cant provide smooth scrolling in settings, 820 sd stuttering like 210, okay. It happens on every gemini hmp kernel on 8.1 oreo. Maybe some to perfd related. Need EAS.
4. Gpay wont work, magisk can't help, maybe device id change will help
All other working fine
MichaelPan01 said:
When charging, the battery icon won't show. The bug is phh's?
Sent from my MI 5 using Tapatalk
Click to expand...
Click to collapse
Here it is working.
Have you set the battery icon visibility status under the statusbar settings?
StealthHD said:
Installed. Yeap, we finally got a vanilla android
For first alpha, it working flawlessly.
Some bugs i founded.
1. After magisk install on stock kernel, got bootloop. Fixed after installing AEXMod latest kernel.
2. Gcam not working. buildprop (vendor folder) doesnt help. Got FC anyway
3. HMP... stock governor settings cant provide smooth scrolling in settings, 820 sd stuttering like 210, okay. It happens on every gemini hmp kernel on 8.1 oreo. Maybe some to perfd related. Need EAS.
4. Gpay wont work, magisk can't help, maybe device id change will help
All other working fine
Click to expand...
Click to collapse
1) Phh rom support natively Phh superuser app (from market) with stock kernel and phh-gapps-su gsi image.
2) Gcam require API2/HAL3 support, and on phh gsi hasn't been implemented (as written is an experimental rom with the meaning to be compatible with stock Oreo treble devices). Instead, it has API1/HAL1 support for stock vanilla camera.
3) Stock kernel is HMP. We do not develop till now the EAS kernel on stock treble kernel (we will do for our JDC gsi).
4) Magisk is clearly reported into Phh thread to not be used. In custom development we have a plus, because we can change the kernel (as you have done)...
Thanks for this testing report.
{
"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"
}
Code:
/*
*Disclaimer
*
* Your warranty may be void.
*
* We're not responsible for bricked devices, dead OTGs or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
Introduction
Pitch Black Recovery is a fork of TWRP with many improvements to make your experience better. It's more flexible & easy to use.
Based on: TWRP v3.4.0
PitchBlack version: 3.0.0
Device: picasso (all models should work)
Picasso TG general group: https://t.me/XiaomiRedmiK30
Maintainer/Authors build: masemoel and Hadenix
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Device tree: https://github.com/Redmi-K30-5G/device_xiaomi_picasso_recovery
PitchBlack Team: @rezaadi0105, @shovon, @manjot.gni, @androiabledroid, sagar
Features
Fully native android like UI
Supports Treble and non-Treble ROMs
Up-to-date kernel, built from sources
Full dark theme with changeable accents
Reorganized menus
MIUI OTA support
Disable DM Verity
Use AromaFM as default file manager
Various tools are include
Universal flash-able file for all variant of a device
Many bug fixes & optimization & much more
Click to expand...
Click to collapse
Installation Instructions
From previous version/another recovery
Download the PitchBlack zip to your device
Reboot to your current custom recovery
Flash the PitchBlack zip
The device will automatically reboot into PitchBlack Recovery after installation
Enjoy
From fastboot
Download PitchBlack Recovery flashable zip from bellow
Extract the PBRP zip
Goto fastboot mode in your device
Flash the recovery.img by fastboot flash recovery.img
Boot into PBRP
Copy the zip to internal storage
Flash it
Enjoy
From TWRP app
(Ideal if you don't own a PC).
Download Official TWRP app from Play Store.
Extract the PBRP zip.
Flash the recovery.img with the TWRP app.
Reboot to recovery.
Flash the whole PBRP zip (otherwise you won't have PBRP tools working properly).
Enjoy
Changelog
PBRP changelog
Code:
v3.0.0
- Fully Redesigned UI
- Added new Keychecks While Flashing PBRP or recovery.img or Ramdisk
- Fully Redesigned Website https://pitchblackrecovery.com
- New Android like Power Menu (Activated via power key hold)
- Flashlight toggled by Vol up(+) on hold
- New Scrollable Advanced menu
- Totally Redesigned Icons
- Removed old unnecessary Theming Stuff
- Tested on almost all handy Resolutions
- Flashlight toggle on Lockscreen
- More checks for SAR/Non-SAR\
- New Navbar
- Support on almost all Android version (5.0+)
- Update ozip decrypt
- Fix up ozip print logs & take all paths
- Update FUNDING.yml
- Fixed encrypted removal checks & buttons
- Add Flag for disabling treble compatibility by default
- Is_Data_Wiped: Simplify function signature
- Unified AB_OTA_UPDATER
- Change AB device log storage to /data/recovery
- Delay start if specified in board
- Optimize touchscreen driver initialization delay.
v2.9.0
- Update kernel
- Update DM Verity Logic
- Update magisk
- Update unroot magisk
- Some bug fixed
Picasso changelog
Code:
PBRP 3.0.0 2020-12-17 - Android Q and R
- Added nano editor.
- Fixed decryption issues with Android 11 (now it should decrypt even when the password is not a pattern). This makes now A11 PBRP be marked as stable!
- All PBRP changes in the latest month.
PBRP 3.0.0 2020-11-10 - Android Q and R
- Fixed errors when wiping some partitions.
- Touch delay on the first 5 seconds has gone.
- Minor touches on fstabs.
- All PBRP work in the latest week.
PBRP 3.0.0 2020-11-03 - Android Q and R
- Updated vendor, kernel and dtbo to xiaomi.eu 12.0.7.0 ones.
- Fixed wiping errors in [U]Wipe[/U] section.
- Fixed some flags in dynamic partitions.
- (Hopefully) Fixed asking decryption key when it's not needed.
- Fixed flashing failure with multiple Migrate zips.
- Fixed duplicated super partition in backup section.
- Translations updated (PBRP team) and other minor stuff by the team as well :).
PBRP 3.0.0 2020-10-03 - Android R
- Initial XDA release, based on Q tree.
PBRP 3.0.0 2020-10-03 - Android Q
- Update kernel stuff to stable MiUI 12.0.6.
- Remove DTBO partition from Wipe section (it can't be wiped).
- Some PBRP UI fixes by the team.
PBRP 3.0.0 2020-10-01 - Android Q
- Now we don't need to unmount anything before flashing.
- Translation characters are now showed correctly (fixes issue with Asian fonts not showing).
- Some UI fixes and other improvement by the PBRP team.
PBRP 3.0.0 2020-09-19 - Android Q
- Initial XDA release
Bugs
- You tell me!
- Check current issues at the GitHub Issues tracker before reporting one (it may already exist): https://github.com/Redmi-K30-5G/device_xiaomi_picasso_recovery/issues
Downloads
Flashable Android 10/Q zip [MEGA folder]
https://mega.nz/folder/10I1RKgC#onjHUvM4-trZ9qcfkWkLtw
Flashable Android 11/R zip [MEGA folder]
https://mega.nz/folder/EoIHDYIL#kFemXVyMKd53kKCdZm3SUg
Note that this is still experimental as Android 11 source for PBRP hasn't been still released!
Version information
Status: Stable
Created: 2020-09-19
Last updated: 2020-11-03
Beers & coffees (obviously hitting the thanks button is always enough, but this will motivate me 1000%): https://www.paypal.com/paypalme/masemoel
Little reminder here: I abandoned this project in favour of OrangeFox Recovery Project, so don't expect any updates from my side here anymore. If anyone is willing to continue this project, my trees are available as always on my GitHub (see the OP).
OrangeFox Recovery Project for picasso
Ey, Jienensse. Sabes porque cada vez que intento flashear este PichBlack recovery, flasheandose correctamente no inicia nada? Directamente entra a Android como si no hubiera recovery alguno...
Saludos de un murciano
(PD) Estoy en la ROM Xiaomi.EU 11.0.11, actualmente atrapado sin TWRP... ?
Dan Ratia said:
Ey, Jienensse. Sabes porque cada vez que intento flashear este PichBlack recovery, flasheandose correctamente no inicia nada? Directamente entra a Android como si no hubiera recovery alguno...
Saludos de un murciano
(PD) Estoy en la ROM Xiaomi.EU 11.0.11, actualmente atrapado sin TWRP... ?
Click to expand...
Click to collapse
Hola. ¿Has seguido los pasos que indico para instalar PBRP mediante TWRP o fastboot?
Para entrar a la recovery tienes que hacer volumen + y botón de encendido a la misma vez.
(Recuerda que, según las reglas de XDA, sólo se puede hablar inglés en los foros)
----------------------------
Hi. Have you followed the steps in the main post to flash via TWRP or fastboot?
To enter into recovery, you must shut on your phone by pressing volume + and power button at the same time.
(Remember that you can only speak English here, XDA rules).
Sent from my Redmi K30 5G using XDA Labs
masemoel said:
Hola. ¿Has seguido los pasos que indico para instalar PBRP mediante TWRP o fastboot?
Para entrar a la recovery tienes que hacer volumen + y botón de encendido a la misma vez.
(Recuerda que, según las reglas de XDA, sólo se puede hablar inglés en los foros)
----------------------------
Hi. Have you followed the steps in the main post to flash via TWRP or fastboot?
To enter into recovery, you must shut on your phone by pressing volume + and power button at the same time.
(Remember that you can only speak English here, XDA rules).
Sent from my Redmi K30 5G using XDA Labs
Click to expand...
Click to collapse
Of course, first I tried an unofficial Chinese TWRP, which although it worked, it did not let me interact with the system partition and I wanted to change to this one. It flashes but does not start.
Then I tried from Flashify and from the TWRP app. Same result.
Then from the PC via fastboot, first from the Xiaomi ADB Fastboot Tool and then from CMD, with and without vbmeta.img. Same result.
In fact, I tried other versions and the same ...
It's strange, I have never had problems with flashing TWRP on Xiaomi, what's more, I have a YouTube channel where I show the processes in many of them and I wanted to make a video of this PichBlack for the K30.
Dan Ratia said:
Of course, first I tried an unofficial Chinese TWRP, which although it worked, it did not let me interact with the system partition and I wanted to change to this one. It flashes but does not start.
Then I tried from Flashify and from the TWRP app. Same result.
Then from the PC via fastboot, first from the Xiaomi ADB Fastboot Tool and then from CMD, with and without vbmeta.img. Same result.
In fact, I tried other versions and the same ...
It's strange, I have never had problems with flashing TWRP on Xiaomi, what's more, I have a YouTube channel where I show the processes in many of them and I wanted to make a video of this PichBlack for the K30.
Click to expand...
Click to collapse
Weird... Ensure that you have Redmi K30 5G version, and not normal K30 (aka phoenix).
Sent from my Redmi K30 5G using XDA Labs
Yes, i am sure it is Redmi K30 5G
Dan Ratia said:
Yes, i am sure it is Redmi K30 5G
Click to expand...
Click to collapse
Then it's very weird... No one has reported that the recovery is not booting on their picasso.
Did you flashed that modified vbmeta image by PeterCxy for his LineageOS recovery? (If you flashed it, then flash the original one)
Either that or your outdated vendor base would be the reason why it's not booting for you.
Sent from my Redmi K30 5G using XDA Labs
I don't know, man, this has never happened to me and I've been using modified recovery since CMW 3. The only thing I have not tried yet is to install the original Miui recovery and try again with the modified recovery.
Dan Ratia said:
I don't know, man, this has never happened to me and I've been using modified recovery since CMW 3. The only thing I have not tried yet is to install the original Miui recovery and try again with the modified recovery.
Click to expand...
Click to collapse
Consider upgrading to a newer MiUI version (like latest 11 or 12 version) via LRTWRP.
Then PBRP should boot.
Sent from my Redmi K30 5G using XDA Labs
Dear Masemoel：
Appreciate your contribution to such a nice work. I have noticed that you are working on another unofficial TWRP, and it also works great. Do you consider to add it in this thread or creat another thread? Cuz i think both recoveries are very cool custom recoveries and ppl are very willing to use them.
ThomasRhin said:
Dear Masemoel：
Appreciate your contribution to such a nice work. I have noticed that you are working on another unofficial TWRP, and it also works great. Do you consider to add it in this thread or creat another thread? Cuz i think both recoveries are very cool custom recoveries and ppl are very willing to use them.
Click to expand...
Click to collapse
Hello and thanks, Thomas.
The unofficial TWRP is being maintained by Hadenix in GitHub's picasso group right now.
Me I will stay in PBRP as I feel comfortable, safe, and has a lot of features with a nice UI ?
I once built TWRP to ensure that the device tree I did was working as it should, and also to see if an issue in PBRP was happening in TWRP as well.
https://github.com/Redmi-K30-5G/device_xiaomi_picasso_recovery/releases/tag/TWRP
But I won't build it anymore for now, PBRP works flawlessly + there is already another dev compiling and improving it.
Sent from my Redmi K30 5G using XDA Labs
so its only for k30 5g or it will aslo work on k30i 5g?
@tensionless said:
so its only for k30 5g or it will aslo work on k30i 5g?
Click to expand...
Click to collapse
It should work... I haven't tested though as I don't have that picasso variant
Sent from my Redmi K30 5G using XDA Labs
masemoel said:
Consider upgrading to a newer MiUI version (like latest 11 or 12 version) via LRTWRP.
Then PBRP should boot.
Sent from my Redmi K30 5G using XDA Labs
Click to expand...
Click to collapse
Thanks man, I had to do that to make PBRP work in the end :highfive:
One more doubt, I installed the CrDdroid port ROM that I found in your repository and I am not able to root. I have tried Magisk 20.1, 20.2, 20.3 and 20.4 (including the canary version), but when flashing the ROM it does not start. Is there any way to get Magisk to work on this unofficial CrDroid?
Dan Ratia said:
Thanks man, I had to do that to make PBRP work in the end :highfive:
One more doubt, I installed the CrDdroid port ROM that I found in your repository and I am not able to root. I have tried Magisk 20.1, 20.2, 20.3 and 20.4 (including the canary version), but when flashing the ROM it does not start. Is there any way to get Magisk to work on this unofficial CrDroid?
Click to expand...
Click to collapse
I could root it when I was using crDroid (I assume you're using my build from my personal git account...)
Remember the steps to flash a ROM: Flash ROM, Magisk, GApps, format data and then reboot to system (otherwise you will have bootloop due to forced-encryption problems).
Just use Magisk ZIPs from here (official releases): https://github.com/topjohnwu/Magisk/releases or in PBRP tools...
If you format data after flash a ROM, you have to install Magisk Manager (see the above link as well) and, when you install that apk, then you'll have root access
masemoel said:
I could root it when I was using crDroid (I assume you're using my build from my personal git account...)
Remember the steps to flash a ROM: Flash ROM, Magisk, GApps, format data and then reboot to system (otherwise you will have bootloop due to forced-encryption problems).
Just use Magisk ZIPs from here (official releases): https://github.com/topjohnwu/Magisk/releases or in PBRP tools...
If you format data after flash a ROM, you have to install Magisk Manager (see the above link as well) and, when you install that apk, then you'll have root access
Click to expand...
Click to collapse
Well i wil try again, i flashed ROM, Gapps, start ROM, Format data and Magisk.
masemoel said:
I could root it when I was using crDroid (I assume you're using my build from my personal git account...)
Remember the steps to flash a ROM: Flash ROM, Magisk, GApps, format data and then reboot to system (otherwise you will have bootloop due to forced-encryption problems).
Just use Magisk ZIPs from here (official releases): https://github.com/topjohnwu/Magisk/releases or in PBRP tools...
If you format data after flash a ROM, you have to install Magisk Manager (see the above link as well) and, when you install that apk, then you'll have root access
Click to expand...
Click to collapse
I already did the steps you mention, but the result is the same, the ROM does not start. It only starts when uninstalling magisk.
In fact, CrDroid itself tries to install the Magisk addon and it doesn't succeed (I attach images), try Magisk 20.4 and 20.1 from the official website.
Could you pass me the AICP that you are using? I want AOSP with root ...
Dan Ratia said:
I already did the steps you mention, but the result is the same, the ROM does not start. It only starts when uninstalling magisk.
In fact, CrDroid itself tries to install the Magisk addon and it doesn't succeed (I attach images), try Magisk 20.4 and 20.1 from the official website.
Could you pass me the AICP that you are using? I want AOSP with root ...
Click to expand...
Click to collapse
You are flashing Magisk and then flashing crDroid????
Wipe everything (data, cache and dalvik)
Reboot to recovery
Flash crDroid
Flash Magisk
Flash GApps (obviously this is optional)
Wipe data and dalvik again
Reboot
I don't know what's that Magisk addon.d ... But it might be causing the bootloop.
Also ensure that you're using the latest PBRP release for Android 10 and that you are not mounting any partition other than data and cache.
Use the zip from the GitHub's Magisk releases pages I sent you...
Sent from my Redmi K30 5G using XDA Labs
masemoel said:
You are flashing Magisk and then flashing crDroid????
Wipe everything (data, cache and dalvik)
Reboot to recovery
Flash crDroid
Flash Magisk
Flash GApps (obviously this is optional)
Wipe data and dalvik again
Reboot
I don't know what's that Magisk addon.d ... But it might be causing the bootloop.
Also ensure that you're using the latest PBRP release for Android 10 and that you are not mounting any partition other than data and cache.
Use the zip from the GitHub's Magisk releases pages I sent you...
Click to expand...
Click to collapse
Ok I got it... You are flashing the forcing encryption disabler... Then you have to flash Magisk 20.3 only, and later you can upgrade if you want...
Flash it after crDroid as well
EDIT: You can look at my AICP build either in the Telegram group mentioned in the OP, or by looking at Redmi-30-5G GitHub.
Sent from my Redmi K30 5G using XDA Labs
https://gitlab.com/hackintosh5/TrebleInfo
Credits
https://github.com/8890q/ for LineageOS 19.1/18.1 device tree, kernel, hardware support, blobs
https://forum.xda-developers.com/t/treble-aosp-g930x-g935x-project_pizza-trebleport-v2-0.3956076/ for libsensor blobs
https://github.com/osm0sis/ for anykernel, used for the twrp patching zip
Special thankshttps://github.com/ExpressLuke for hero2lte testing
https://github.com/00p513-dev for suggesting using squashfs for vendor partition, making it possible to skip partition table modding
https://github.com/phhusson for looking into the double tap to wake issues with phh GSI
https://github.com/ivanmeler for prompting me to look into lpm again, now it is migrated into /vendor
Notes:
I do not own a hero2lte(edge)
I'll mostly work on this only during weekends/holidays
and on that note the hero2lte build is not tested by myself
for vndk30 based vendor (LineageOS 18.1), use with android 11 and up GSIs
for vndk32 based vendor (LineageOS 19.1), use with android 12L and up GSIs
2022-06-12 the CACHE partition is now used as vendor, the HIDDEN patition is now used as cache, no more partition table mods required
Updates:
2023-02-23
added store_mode.zip flashable that uses "/sys/class/power_supply/battery/store_mode" and "/sys/module/sec_battery/parameters/store_mode_max" interfaces for limiting battery charging
flash to limit battery charging to 70%, flash again to disable charging limitafter flashing, charging limit can be adjusted at "/system/etc/init/8890_store_mode.rc" by changing "70" on the line "service enable_store_mode /system/bin/8890_store_mode 1 70" to other percentage values
2023-02-15
include libaptX_encoder.so in patchers
adding patches to support phh android 13 GSIs:
includes lineage lmkd, LineageOS/[email protected] seems required for lmkd to work on this kernelfix bluetooth audio by disabling sysbta (generic in-system bluetooth audio implementation), see phhusson/treble_experimentations#2519disable full disk encryption and quota when booting android 13, 8890q/[email protected] 8890q/[email protected] ; FDE still works when using android 12 GSIsdisable healthd offline charging service, conflicts with lpm
2022-10-04
update gps blobs from https://github.com/8890q/proprietary_vendor_samsung/commit/698ddd9acd7bdca78ecea93e06fd78a0d9dbc407
2022-09-05
adding keystore fixes to a12_patcher.zip:
https://github.com/LineageOS/android_system_security/commit/356c125115c0a9b9f9670b5b86b6e291c5ec5404
https://github.com/8890q/patches/commit/9a322b4e71ca784d4a2f71494d1ef0e52f835efe
which fixes keystore apps and device encryption on Google 12L GSI, might also fix some keystore apps issues on phh GSI
2022-07-10
moved lpm to vendor partition
2022-06-26
rebased vndk32 on 2022-06-24 build from ivan
new smaller vendor flasher, flashes only boot and vendor
2022-06-24
lpm_installer.zip should work with Phh and Andy Yan GSIs better now
2022-06-18
vndk30 prop changes, might help booting exotic GSIs
2022-06-13
android 12 data usage meter now works with a12_patcher.zip
2022-06-12
fixed neural network api hal
fixed fingerprint sensor
switched vendor image to squashfs, no CreateVendor required anymore with it's small size
new twrp patcher zip, should no longer cause "twrp is stuck after flashing CreateVendor"
bigger GSIs should fit better now with the original ~4.5GB SYSTEM partition; device native roms can be used without RevertVendor
2022-05-31
fixed wifi tethering
vndk32: rebased on 2022-05-26 12L build from ivan
phh_wifitethering_patcher.zip for wifi hotspot on phh GSIs
2022-05-26
added vndk32 based release
lpm_installer.zip for offline charging
fixed keystore errors on android 12 GSIs, lock screens work now
2022-02-15
rebased on February build from 8890q
January android updates
2021-12-16
install libaudioroute into /vendor/lib
December android updates
2021-12-10
move properties to /vendor
Tested GSIs
vndk30
https://github.com/phhusson/treble_experimentations/releases/tag/v313 (vanilla/bvS)
https://github.com/phhusson/treble_experimentations/releases/tag/v413 (vanilla/bvS)
https://developer.android.com/topic/generic-system-image/releases (android 12 gsi, with a12_patch.zip flashed after)
vndk32
https://github.com/phhusson/treble_experimentations/releases/tag/v413 (vanilla/bvS)
https://developer.android.com/topic/generic-system-image/releases (android 12 gsi, with a12_patch.zip flashed after)
important: system as root builds, you'd want ab build GSIs
Known issues:
some GSIs like official google GSIs lacks the /efs mount point, it has to be added manually or it will boot loop at samsung logo failing to mount /efs
some android 12 GSIs does not boot due to the lack of ebpf on the 3.18 kernel, android 12 GSIs needs to have patched bpfloader and netd, see below
https://github.com/8890q/patches
https://github.com/phhusson/platform_system_bpf/commit/c81966c23d79241458ebf874cfa8662f44705549
https://github.com/phhusson/platform_system_netd/commit/3a6efa1ff3717a613d1ba4a0eff5e751262d1074
data usage stays at 0 MB used on android 12 GSIs, because ebpf is used for metering
a12_patcher.zip attempts to fix the above issues by creating /system_root/efs and importing bpfloader+netd from https://github.com/8890q/patches
a11_patcher.zip creates /system_root/efs if required
usb adb does not work on android 12 GSIs
a legacy implementation of usb adb is required for this kernel, see https://review.lineageos.org/c/LineageOS/android_packages_modules_adb/+/326385
as a workaround, disable usb adb and use wifi adb
Wifi tethering does not work on phh GSIs <= 414
https://github.com/phhusson/vendor_hardware_overlay/tree/pie/Tethering conflicts with our Tethering overlay
flash phh_wifitethering_patcher.zip after installing phh GSIs
Alarm clock not working on aosp GSI
it should be fixed on phh 414 and up, it is not a vendor issue. If you are using an older aosp GSI, flash deskclock_powersaving.zip to fix that. See https://github.com/LineageOS/androi...mmit/8dd096c4cfb647960be1695a57246727878b8c8d
Google android 13 GSIs do not work
post-build patching got more involved in android 13 since on-java patches are now required, stick with phh/treble droid GSIs which already include build time patches for bpf-less kernel support
Disk encryption does not work on android 13 GSIs
full disk encryption is removed in android 13, file based encryption not available currently https://github.com/8890q/android_de...mmit/3cbcf972465419c18bf4850d26320896df465b18
Installation
If you are using the old partition table mod zip heroxlte_CreateVendor_2.0.zip from older versions, first flash heroxlte_RevertVendor_2.0.zip, or revert your partition table other ways such as odin. Skip this step if you have never touched your partition table
Install twrp-3.6.2_9-0 from https://eu.dl.twrp.me/herolte/ (s7) or https://eu.dl.twrp.me/hero2lte/ (s7 edge), as of rignt now newest(twrp-3.7.0_9-0) is too big for flashing
Flash twrp_patcher.zip to enable system.img flashing, it'll reboot to recovery once it's done, tested on 3.6.2_9-0 but newer versions should work unless recovery.fstab changes
Flash vndk32 for android 12.1(api level 32) and android 13.0(api level 33) GSIs, flash vndk30 for android 11(api level 30) and 12(api level 31) GSIs, herolte for s7 and hero2lte for s7edge
Flash the system.img of your choice
If you are using phh GSI version <= 414, flash phh_wifitethering_patcher.zip
If you are using phh GSI version <= 414, flash phh_dt2w_patcher.zip to fix double tap to wake
If you are using phh GSI version <= 413 or pure aosp, flash deskclock_powersaving.zip to fix alarm clock
If you are using an android 12/12L GSI, flash a12_patcher.zip
If you are using an android 11 GSI, flash a11_patcher.zip
If you are using a phh/treble droid android 13 GSI, flash phh_aosp13_patcher.zip
Updating vendor
Flash vndk32 for android 12.1(api level 32) and android 13.0(api level 33) GSIs, flash vndk30 for android 11(api level 30) and 12(api level 31) GSIs, herolte for s7 and hero2lte for s7edge
Undo twrp_patcher.zip and revert to device native romsThis is not required for using device native roms, however OTA updates might require this
Flash the newest twrp again
Format cache using wipe -> select cache -> repair or change file system -> change file system -> ext4
Flash a device native rom
Buildinglineage_build_herolte_vendor_part, lineage_build_hero2lte_vendor_part, lineage_build_herolte_vendor_part_18.1 and lineage_build_hero2lte_vendor_part_18.1 builds lineageos along with treble vendor using https://github.com/lineageos4microg/docker-lineage-cicd
you'll need ~15GB of free ram, ~300GB free disk space and podman
# create directories
mkdir src
mkdir zips
mkdir logs
mkdir ccache
# builds lineage 19.1 along with vndk32 for herolte (s7 flat exynos)
bash lineage_build_herolte_vendor_part
Reporting issues besides the known ones:
You can report them over https://github.com/Kethen/herolte_treble/issues
Downloadshttps://github.com/Kethen/herolte_treble/releases
katharinechui said:
Creditshttps://github.com/8890q/ https://forum.xda-developers.com/t/...e-spoofing-ota-updates-for-s7-exynos.4368995/ for LineageOS 19.1/18.1 device tree, kernel, hardware support, blobs
https://forum.xda-developers.com/t/treble-aosp-g930x-g935x-project_pizza-trebleport-v2-0.3956076/ for libsensor blobs
Notes:
I do not own a hero2lte(edge)
I'll mostly work on this only during weekends/holidays
and on that note the hero2lte build is not tested by myself
for vndk30 based vendor (LineageOS 18.1), use with android 11 and up GSIs
for vndk32 based vendor (LineageOS 19.1), use with android 12L and up GSIs
Updates:
2022-05-26
added vndk32 based release
lpm_installer.zip for offline charging
fixed keystore errors on android 12 GSIs, lock screens work now
2022-02-15
rebased on February build from 8890q
January android updates
2021-12-16
install libaudioroute into /vendor/lib
December android updates
2021-12-10
move properties to /vendor
Tested GSIs
vndk30
https://github.com/phhusson/treble_experimentations/releases/tag/v313 (vanilla/bvS)
https://github.com/phhusson/treble_experimentations/releases/tag/v413 (vanilla/bvS)
https://developer.android.com/topic/generic-system-image/releases (android 12 gsi, with a12_patch.zip flashed after)
vndk32
https://github.com/phhusson/treble_experimentations/releases/tag/v413 (vanilla/bvS)
https://developer.android.com/topic/generic-system-image/releases (android 12 gsi, with a12_patch.zip flashed after)
important: system as root builds, you'd want ab build GSIs
Known issues:some GSIs like official google GSIs lacks the /efs mount point, it has to be added manually or it will boot loop at samsung logo failing to mount /efs
some android 12 GSIs does not boot due to the lack of ebpf on the 3.18 kernel, android 12 GSIs needs to have patched bpfloader and netd, see below
https://github.com/8890q/patches
https://github.com/phhusson/platform_system_bpf/commit/c81966c23d79241458ebf874cfa8662f44705549
https://github.com/phhusson/platform_system_netd/commit/3a6efa1ff3717a613d1ba4a0eff5e751262d1074
You can attempt to copy bpfloader and netd binaries from phh GSIs
a12_patcher.zip attempts to fix the above issues by creating /system_root/efs and importing bpfloader+netd from phh android 12 v413
usb adb does not work on android 12 GSIs
a legacy implementation of usb adb is required for this kernel, see https://review.lineageos.org/c/LineageOS/android_packages_modules_adb/+/326385
fingerprint sensor does not work, the vendor blob segfaults when it can't access /data/biometrics due to vndk selinux compliance
neuralnetworks hal does not work, perhaps it can be fix by linking it with another c/c++ library, missing a symbol that should be included in libc++ but not vndk libc++
phhgsi_arm64_ab:/ $ ldd /vendor/bin/hw/[email protected]
linux-vdso.so.1 => [vdso] (0x7138c71000)
CANNOT LINK EXECUTABLE "linker64": cannot locate symbol "__cxa_demangle" referenced by "/vendor/bin/hw/[email protected]"...
lpm/power off charging does not quite work, /system/bin/lpm links libandroid.so (violates vndk) and looks for media assets in /system
charging powered off will likely send you to recovery/system
flash lpm_instasller.zip after installing gsi if power off charging is desired, it might or might not work depending on GSI (tested on phh 413)
$ readelf -d proprietary/bin/lpm | grep NEEDED
0x0000000000000001 (NEEDED) Shared library: [libcutils.so]
0x0000000000000001 (NEEDED) Shared library: [libbinder.so]
0x0000000000000001 (NEEDED) Shared library: [libutils.so]
0x0000000000000001 (NEEDED) Shared library: [libsuspend.so]
0x0000000000000001 (NEEDED) Shared library: [libhardware.so]
0x0000000000000001 (NEEDED) Shared library: [libandroid.so]
0x0000000000000001 (NEEDED) Shared library: [libmaet.so]
0x0000000000000001 (NEEDED) Shared library: [libsxqk_skia.so]
0x0000000000000001 (NEEDED) Shared library: [liblog.so]
0x0000000000000001 (NEEDED) Shared library: [libc++.so]
0x0000000000000001 (NEEDED) Shared library: [libc.so]
0x0000000000000001 (NEEDED) Shared library: [libm.so]
0x0000000000000001 (NEEDED) Shared library: [libdl.so]
InstallationThere are two requirements for testing this treble build:
A /vendor partition that is at least 250 MB
A recovery that is aware of the /vendor partition
You can fulfill these requirements by:
Install twrp normally
Flash heroxlte_CreateVendor_2.0.zip from https://forum.xda-developers.com/t/treble-aosp-g930x-g935x-project_pizza-trebleport-v2-0.3956076/ , it will create a ~400 MiB vendor partition and patch the current twrp you have
Or:
Modify the partition table manually and add a 250 MB partition named VENDOR, build/modify twrp manually to support the new partition
Once that's fulfilled, flash the zip in this release, herolte for flat and hero2lte for edge. The zips comes with an install of LineageOS 19.1/18.1. After Installing the zip you can write any system.img of your choice
After writing system.img, flash lpm_installer.zip if poweroff charging is needed. Note that that has been tested on phh v413 and google android 12 gsi
a12_patcher.zip replaces /system/bin/bpfloader and /system/bin/netd with phh versions, also creates /system_root/efs if required, allowing google android 12 gsi to boot
Building/SourcePlease refer to manifests_herolte_vendor_part/roomservice.xml and manifests_herolte_vendor_part_18.1/roomservice.xml on https://github.com/Kethen/lineage_build_scripts for your own builds
Download
Release 2022-05-26 · Kethen/lineage_build_scripts
18.1 herolte native build does not need patches
github.com
Click to expand...
Click to collapse
Excellent work.
katharinechui said:
https://gitlab.com/hackintosh5/TrebleInfo
Credits
https://github.com/8890q/ for LineageOS 19.1/18.1 device tree, kernel, hardware support, blobs
https://forum.xda-developers.com/t/treble-aosp-g930x-g935x-project_pizza-trebleport-v2-0.3956076/ for libsensor blobs
https://github.com/osm0sis/ for anykernel, used for the twrp patching zip
Special thankshttps://github.com/ExpressLuke for hero2lte testing
https://github.com/00p513-dev for suggesting using squashfs for vendor partition, making it possible to skip partition table modding
https://github.com/phhusson for looking into the double tap to wake issues with phh GSI
Notes:
I do not own a hero2lte(edge)
I'll mostly work on this only during weekends/holidays
and on that note the hero2lte build is not tested by myself
for vndk30 based vendor (LineageOS 18.1), use with android 11 and up GSIs
for vndk32 based vendor (LineageOS 19.1), use with android 12L and up GSIs
2022-06-12 the CACHE partition is now used as vendor, the HIDDEN patition is now used as cache, no more partition table mods required
Updates:
2022-06-13
android 12 data usage meter now works with a12_patcher.zip
2022-06-12
fixed neural network api hal
fixed fingerprint sensor
switched vendor image to squashfs, no CreateVendor required anymore with it's small size
new twrp patcher zip, should no longer cause "twrp is stuck after flashing CreateVendor"
bigger GSIs should fit better now with the original ~4.5GB SYSTEM partition; device native roms can be used without RevertVendor
2022-05-31
fixed wifi tethering
vndk32: rebased on 2022-05-26 12L build from ivan
phh_wifitethering_patcher.zip for wifi hotspot on phh GSIs
2022-05-26
added vndk32 based release
lpm_installer.zip for offline charging
fixed keystore errors on android 12 GSIs, lock screens work now
2022-02-15
rebased on February build from 8890q
January android updates
2021-12-16
install libaudioroute into /vendor/lib
December android updates
2021-12-10
move properties to /vendor
Tested GSIs
vndk30
https://github.com/phhusson/treble_experimentations/releases/tag/v313 (vanilla/bvS)
https://github.com/phhusson/treble_experimentations/releases/tag/v413 (vanilla/bvS)
https://developer.android.com/topic/generic-system-image/releases (android 12 gsi, with a12_patch.zip flashed after)
vndk32
https://github.com/phhusson/treble_experimentations/releases/tag/v413 (vanilla/bvS)
https://developer.android.com/topic/generic-system-image/releases (android 12 gsi, with a12_patch.zip flashed after)
important: system as root builds, you'd want ab build GSIs
Known issues:
some GSIs like official google GSIs lacks the /efs mount point, it has to be added manually or it will boot loop at samsung logo failing to mount /efs
some android 12 GSIs does not boot due to the lack of ebpf on the 3.18 kernel, android 12 GSIs needs to have patched bpfloader and netd, see below
https://github.com/8890q/patches
https://github.com/phhusson/platform_system_bpf/commit/c81966c23d79241458ebf874cfa8662f44705549
https://github.com/phhusson/platform_system_netd/commit/3a6efa1ff3717a613d1ba4a0eff5e751262d1074
data usage stays at 0 MB used on android 12 GSIs, because ebpf is used for metering
a12_patcher.zip attempts to fix the above issues by creating /system_root/efs and importing bpfloader+netd from https://github.com/8890q/patches
a11_patcher.zip creates /system_root/efs if required
usb adb does not work on android 12 GSIs
a legacy implementation of usb adb is required for this kernel, see https://review.lineageos.org/c/LineageOS/android_packages_modules_adb/+/326385
as a workaround, disable usb adb and use wifi adb
lpm/power off charging does not work
lpm related blobs sadly has to be installed on /system, flash lpm_instasller.zip after installing gsi if power off charging is desired, it might or might not work depending on GSI (tested on phh 413 and 313)
Wifi tethering does not work on phh GSIs
https://github.com/phhusson/vendor_hardware_overlay/tree/pie/Tethering conflicts with our Tethering overlay
flash phh_wifitethering_patcher.zip after installing phh GSIs
Alarm clock not working on aosp GSI
it should be fixed on phh 414 and up, it is not a vendor issue. If you are using an older aosp GSI, flash deskclock_powersaving.zip to fix that. See https://github.com/LineageOS/androi...mmit/8dd096c4cfb647960be1695a57246727878b8c8d
Installation
If you are using the old partition table mod zip heroxlte_CreateVendor_2.0.zip from older versions, first flash heroxlte_RevertVendor_2.0.zip, or revert your partition table other ways such as odin. Skip this step if you have never touched your partition table
Install the newest twrp from https://eu.dl.twrp.me/herolte/ (s7) or https://eu.dl.twrp.me/hero2lte/ (s7 edge)
Flash twrp_patcher.zip to enable system.img flashing, it'll reboot to recovery once it's done, tested on 3.6.2_9-0 but newer versions should work unless recovery.fstab changes
Flash Lineage 19.1 for android 12.1(api level 32) GSIs, flash Lineage 18.1 for android 11(api level 30) and 12(api level 31) GSIs, herolte for s7 and hero2lte for s7edge
Flash the system.img of your choice
If you are using a phh patched GSI, flash phh_wifitethering_patcher.zip
If you are using an android 12/12L GSI, flash a12_patcher.zip
If you are using an android 11 GSI, flash a11_patcher.zip
Flash lpm_installer.zip to enable poweroff charging
If you are using an aosp GSI that is not phh patched or older than phh 414, flash deskclock_powersaving.zip to fix alarm clock
If you are using phh GSI version <= 414, flash phh_dt2w_patcher.zip to fix double tap to wake
Undo twrp_patcher.zip and revert to device native romsThis is not required for using device native roms, however OTA updates might require this
Flash the newest twrp again
Wipe cache
Flash a device native rom
Buildinglineage_build_herolte_vendor_part, lineage_build_hero2lte_vendor_part, lineage_build_herolte_vendor_part_18.1 and lineage_build_hero2lte_vendor_part_18.1 builds lineageos along with treble vendor using https://github.com/lineageos4microg/docker-lineage-cicd
you'll need ~15GB of free ram, ~300GB free disk space and podman
# create directories
mkdir src
mkdir zips
mkdir logs
mkdir ccache
# builds lineage 19.1 along with vndk32 for herolte (s7 flat exynos)
bash lineage_build_herolte_vendor_part
Reporting issues besides the known ones:
You can report them over https://github.com/Kethen/herolte_treble/issues
Downloadshttps://github.com/Kethen/herolte_treble/releases
Click to expand...
Click to collapse
on my phone nfc is not working what the hell should i do now?
the files are so much different to other devices i don't can handle....
aljoscha81 said:
on my phone nfc is not working what the hell should i do now?
Click to expand...
Click to collapse
wdym not working? what the hell did you do? mine is working, at least in terms of reading smart cards
(like seriously, what did you do to end up with non-working nfc)
{
"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"
}
please send a logcat to https://github.com/Kethen/herolte_treble/issues
katharinechui said:
wdym not working? what the hell did you do? mine is working, at least in terms of reading smart cards
(like seriously, what did you do to end up with non-working nfc)
View attachment 5640219
please send a logcat to https://github.com/Kethen/herolte_treble/issues
Click to expand...
Click to collapse
ok i will get with matlog app if it help?
by the way it don't react while some machine is reading my blood.....
it is a freestyle libre sensor to monitoring diabetis .....
katharinechui said:
wdym not working? what the hell did you do? mine is working, at least in terms of reading smart cards
(like seriously, what did you do to end up with non-working nfc)
View attachment 5640219
please send a logcat to https://github.com/Kethen/herolte_treble/issues
Click to expand...
Click to collapse
sry here it is ....
forgot my git logging....
it is nfc enabled and running sensor scan modus with freestyle libre 3.3.1 app ...
the phone does not get any signal from device it is as doesn't have been real no error message ..... nothing....!
aljoscha81 said:
sry here it is ....
forgot my git logging....
Click to expand...
Click to collapse
sorry, the log is not helpful at all, all it shows is you have some kind of broken gapps installed and it kept crashing, and nfc scanned something
please capture log with `adb logcat`
what GSI are you using? can you check if nfc works with ivan's lineage 19.1?
like not existence....
katharinechui said:
sorry, the log is not helpful at all, all it shows is you have some kind of broken gapps installed
please capture log with `adb logcat`
what GSI are you using? can you check if nfc works with ivan's lineage 19.1?
Click to expand...
Click to collapse
ok ...
i'm on cr droid 8.5 nazim has post few min ago 8.6....
but adb must?....
broken gapps? it is inbuild... so .... oh nooooo
i got an other device is ran into same issue
can you send link to los 19.1 .....?
i ll give it a try
i will try adb log wait i must have a beer it is a long time for me like to have a12 gsi up and running ....... elstway?
aljoscha81 said:
ok ...
i'm on cr droid 8.5 nazim has post few min ago 8.6....
but adb must?....
broken gapps? it is inbuild... so .... oh nooooo
i got an other device is ran into same issue
can you send link to los 19.1 .....?
i ll give it a try
Click to expand...
Click to collapse
Ivan's LineageOS 19.1
LineageOS 19.1 (Android 12L) [Signature Spoofing][OTA updates] for S7 Exynos
LineageOS 19.1 for herolte /* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns...
forum.xda-developers.com
also try other GSIs, test https://developer.android.com/topic/generic-system-image/releases#android-gsi-12 ARM64+GMS if you need gapps, remember to flash a12_patcher.zip, deskclock_powersaving.zip and lpm_installer.zip after flashing that particular gsi
katharinechui said:
Ivan's LineageOS 19.1
LineageOS 19.1 (Android 12L) [Signature Spoofing][OTA updates] for S7 Exynos
LineageOS 19.1 for herolte /* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns...
forum.xda-developers.com
also try other GSIs, test https://developer.android.com/topic/generic-system-image/releases#android-gsi-12 ARM64+GMS if you need gapps, remember to flash a12_patcher.zip, deskclock_powersaving.zip and lpm_installer.zip after flashing that particular gsi
Click to expand...
Click to collapse
ok i see .. the los in the link you post is different to the one i installed i think i have installed before and got response to the nfc sensor but also only few times then no more nfc working also no android beam from other device....
aljoscha81 said:
ok i see .. the los in the link you post is different to the one i installed i think i have installed before and got response to the nfc sensor but also only few times then no more nfc working also no android beam from other device....
Click to expand...
Click to collapse
I had a look at the sensor app, it has 3 apps for 3 different sensors from abott, are you using the correct version?
The FreeStyle Libre 2 app is only compatible with FreeStyle Libre 2 Sensors. Learn more about compatibility at http://FreeStyleLibre.com
Click to expand...
Click to collapse
You can only use the FreeStyle Libre 3 app with FreeStyle Libre 3 Sensors. It is not compatible with FreeStyle Libre or FreeStyle Libre 2 Sensors.
Click to expand...
Click to collapse
katharinechui said:
I had a look at the sensor app, it has 3 apps for 3 different sensors from abott, are you using the correct version?
Click to expand...
Click to collapse
yes that is not harmfull for me
i use freestyle libre 3.......
that is forced to be not bypassing cause of decrypt of some company?
whiteanywaysomethingcryptingsomehow?...
you know?
?
aljoscha81 said:
?
Click to expand...
Click to collapse
if you have a FreeStyle Libre 3 sensor, you need a FreeStyle Libre 3 app
if you have a FreeStyle Libre 2 sensor, you need a FreeStyle Libre 2 app
if you have a FreeStyle Libre sensor, you need a FreeStyle Libre app
yes i do
I want to install a Pixel Experince Plus 12.1 GSI but there are diffrent versions: Default VNDK, VNDKLite and Slim. My device has Treble support with VNDK 28.0, so what are VNDKLite GSI ROMs and what devices can boot these ROMs??
Here is Pixel Experince Plus with diffrent versions of VNDK: https://github.com/ponces/treble_build_pe/releases
Bella domanda amico, me lo chiedo anche io ma in un forum dove dovrebbe essere un supporto, nessuno ti ascolta.
Mod translation via GT: Good question man, I ask myself too but in a forum where there should be a support, nobody listens to you.
https://source.android.com/devices/architecture/vndk explains some what
VNDK Lite (same-Process HAL (SP-HAL))Same-Process HAL (SP-HAL) is a set of predetermined HALs implemented as Vendor Shared Libraries and loaded into Framework Processes. SP-HALs are isolated by a linker namespace (controls the libraries and symbols that are visible to the shared libraries). SP-HALs must depend only on LL-NDK and VNDK-SP.
This is a patched stock kernel and Magisk module to enable Wireguard's "kernel module backend" feature on stock or GSI firmwares. The patched kernel is required for unofficial modules to be loadable and is an offical kernel with binary patches applied.
The boot image is not already prepatched with Magisk as some users may not want to use it. You can always extract the kernel module from the magisk module zip and insmod it by any means you like.
Kernel Patches:
module_sig_check - always pass - bypass CONFIG_MODULE_SIG and CONFIG_MODULE_SIG_FORCE
check_version - always return true - similar to CONFIG_MODULE_FORCE_LOAD
Spoiler: Resources Used
Build instructions
readme/MMI-QPG30.82-95.txt at master · MotorolaMobilityLLC/readme
Readme's for motorola builds. Contribute to MotorolaMobilityLLC/readme development by creating an account on GitHub.
github.com
Kernel Sources
Release MMI-QPG30.82-135 · MotorolaMobilityLLC/kernel-msm
ginna push for android 10
github.com
AOSP dtc
refs/heads/android10-release - platform/external/dtc - Git at Google
magiskboot - Unpacking and repacking boot image
GitHub - topjohnwu/Magisk: The Magic Mask for Android
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
vmlinux-to-elf - Format the kernel for analysis and recover symbols
GitHub - marin-m/vmlinux-to-elf: A tool to recover a fully analyzable .ELF from a raw kernel, through extracting the kernel symbol table (kallsyms)
A tool to recover a fully analyzable .ELF from a raw kernel, through extracting the kernel symbol table (kallsyms) - GitHub - marin-m/vmlinux-to-elf: A tool to recover a fully analyzable .ELF from ...
github.com
Ghidra - Static analysis and patching
Ghidra
Download:
Running a kernel module built for an older kernel like that seems to be the wrong approach. Whenever I build a kernel with the "kernel: module: Hack to force load prebuilt vendor modules" patch and load it with a recent vendor image, I get boot loops, so the kernels are probably too different to safely force load modules.
Everything works fine with a QPG30.82-135 boot and vendor though, and doesn't need the check_version patch.