Hello developers ( @kalyansundhar@govind1233 @lohanbarth @squid2),
I think everybody heard of project Treble. (Link, Link)
Of course Motorola isn't going to support it to our device(OTA update with repartition is very risky).
But somebody did already a unofficial port to the Xiaomi redmi note 4. This device isn't the same as the Moto G5s.
Today there is a developer doing it to the Xiaomi redmi 3s(Screenshots). This device is almost the same as the Moto G5s.
Specs of Xiaomi redmi 3s(Link)
Qualcomm MSM8937 Snapdragon 430
Adreno 505
5.0 inches
Accelerometer, gyro, proximity, compass
16 GB, 2 GB RAM
Specs of Moto G5s (Link)
Qualcomm MSM8937 Snapdragon 430
Adreno 505
5.2 inches
Fingerprint (front-mounted), accelerometer, gyro, proximity, compass
32 GB, 3 GB RAM
Do you developers think its possible for the Motorola G5s?
If this works we can make a lot of custom roms based on Treble.
Update
I think we must use OEM partition as Vendor partition.
Since a new partition was required for full treble we converted an unused cust partition into vendor which is almost 830mb in size, No we are not re-partitioning your device or anything else which may hardbrick your device
(Source)
GoldeneyeS2 said:
Update
I think we must use OEM partition as Vendor partition.
Since a new partition was required for full treble we converted an unused cust partition into vendor which is almost 830mb in size, No we are not re-partitioning your device or anything else which may hardbrick your device
(Source)
Click to expand...
Click to collapse
We could take one step at a time. First within the current setup, we should separate system and vendor libraries completely. There should not be any mix. Means /system/lib and /system/bin should have only system related. Similarly /system/vendor/lib and /system/vendor/bin should have only vendor related stuff. If we make the device work with this change, then it would be easy to make 'vendor' as separate partition. Even now we have /vendor folder in device root. This is just a symlink to /system/vendor, not a partition. In my opinion this would be a better way to go. Please correct me if I am wrong.
Thanks
KS
kalyansundhar said:
We could take one step at a time. First within the current setup, we should separate system and vendor libraries completely. There should not be any mix. Means /system/lib and /system/bin should have only system related. Similarly /system/vendor/lib and /system/vendor/bin should have only vendor related stuff. If we make the device work with this change, then it would be easy to make 'vendor' as separate partition. Even now we have /vendor folder in device root. This is just a symlink to /system/vendor, not a partition. In my opinion this would be a better way to go. Please correct me if I am wrong.
Thanks
KS
Click to expand...
Click to collapse
Its a good idea to take one step at the time.
What's wrong with this vendor tree? https://github.com/kayesk/android_ve...torola_montana
Project Treble on the Xiaomi Redmi Note 4
How did he do it? He used the “cust” partition on the device for his make-shift vendor partition. The cust partition normally holds a lot of device-specific stuff from MIUI, so it’s essentially wasted space on an AOSP build. Using the approximately 830MB unused partition, he moved the vendor HALs from system into cust without needing to repartition—which was a justification that OEMs such as Nokia and OnePlus used in their statements about why they weren’t going to bring Treble compatibility to their devices
We can use OEM partition. But what's the size of the OEM partition? And how do we make the HAL files?
We can also wait for the xiami 3s and port it to our phone.
GoldeneyeS2 said:
Its a good idea to take one step at the time.
What's wrong with this vendor tree? https://github.com/kayesk/android_ve...torola_montana
Click to expand...
Click to collapse
There is nothing wrong with the vendor tree you mentioned. You take any device tree in github, you could notice mix of libraries and binaries in /system/lib and /system/bin folder. It was ok to have it mixed till Nougat. But with Oreo and with the introduction of HIDL, things are changed. In Nougat we had only one binder. But in Oreo we have 3 binders (binder, hwbinder and vndbinder). Inter process communication is dealt differently. Even with OREO the mixed setup would work. But If we want to go Treble route, then it is better to move out remaining vendor binaries and libraries from /system partition.
We can download the factory image of one of the Pixel like BULLHEAD, MARLIN, etc. And study how the system and vendor partitions are laid out in their OREO release. Theoretically a treble supported system image should be device and make independent (a plain android system). Boot and Vendor partitions would be device specific. I mentioned boot partition here because it would be having device specific boot scripts like init.qcom..., init.mmi..., etc.
Thanks
KS
kalyansundhar said:
There is nothing wrong with the vendor tree you mentioned. You take any device tree in github, you could notice mix of libraries and binaries in /system/lib and /system/bin folder. It was ok to have it mixed till Nougat. But with Oreo and with the introduction of HIDL, things are changed. In Nougat we had only one binder. But in Oreo we have 3 binders (binder, hwbinder and vndbinder). Inter process communication is dealt differently. Even with OREO the mixed setup would work. But If we want to go Treble route, then it is better to move out remaining vendor binaries and libraries from /system partition.
We can download the factory image of one of the Pixel like BULLHEAD, MARLIN, etc. And study how the system and vendor partitions are laid out in their OREO release. Theoretically a treble supported system image should be device and make independent (a plain android system). Boot and Vendor partitions would be device specific. I mentioned boot partition here because it would be having device specific boot scripts like init.qcom..., init.mmi..., etc.
Thanks
KS
Click to expand...
Click to collapse
https://forum.xda-developers.com/xiaomi-redmi-3s/development/oreo-xperience-12-t3672111/
TEST build with vendor:
xperience-12.1.0-20180214-NIGHTLY-land.zip
-----------------------
Initial treble support
U need a custom recovery
Downlaod from here!
http://downloads.hostingsharedbox.com/ascarex/XPerience/12/land/3.2.0.1-TWRP-Land-Treble.img
Download the rom from here!.
http://downloads.hostingsharedbox.c...nd/xperience-12.1.0-20180214-NIGHTLY-land.zip
remember this is a initial work may contain some bugs if u are in older xperience build u not need to perform a clean install
Root u need this
https://drive.google.com/a/my.smccd.edu/uc?id=1oi5G-zzmPMX-WurvyiFRF1u1JjGr-Jvt&export=download
was made by abhishek987 AKA TheScarastic for the redmi note 4
https://forum.xda-developers.com/showpost.php?p=75527103&postcount=2233
Moto g5s doesn't support compass.. (model XT1797) and several model doesn't have NFC too
michael50310 said:
Moto g5s doesn't support compass.. (model XT1797) and several model doesn't have NFC too
Click to expand...
Click to collapse
That's not a big problem.
GoldeneyeS2 said:
https://forum.xda-developers.com/xiaomi-redmi-3s/development/oreo-xperience-12-t3672111/
TEST build with vendor:
xperience-12.1.0-20180214-NIGHTLY-land.zip
-----------------------
Initial treble support
U need a custom recovery
Downlaod from here!
http://downloads.hostingsharedbox.com/ascarex/XPerience/12/land/3.2.0.1-TWRP-Land-Treble.img
Download the rom from here!.
http://downloads.hostingsharedbox.c...nd/xperience-12.1.0-20180214-NIGHTLY-land.zip
remember this is a initial work may contain some bugs if u are in older xperience build u not need to perform a clean install
Root u need this
https://drive.google.com/a/my.smccd.edu/uc?id=1oi5G-zzmPMX-WurvyiFRF1u1JjGr-Jvt&export=download
was made by abhishek987 AKA TheScarastic for the redmi note 4
https://forum.xda-developers.com/showpost.php?p=75527103&postcount=2233
Click to expand...
Click to collapse
Wait i'm a little confused. Did you post this rom for our device, because it looks like it's for the Redmi 3s. I know the whole idea is beased on this device, but i'm still confused. Don't want to flash anything and brick my device. Sorry if i'm being dumb, just want to be sure
Joseph Hill said:
Wait i'm a little confused. Did you post this rom for our device, because it looks like it's for the Redmi 3s. I know the whole idea is beased on this device, but i'm still confused. Don't want to flash anything and brick my device. Sorry if i'm being dumb, just want to be sure
Click to expand...
Click to collapse
Don't use this on Motorola G5s. Its for the Redmi 3s.
If there will be a version you will find it in another thread.
@vaserbanix (https://forum.xda-developers.com/moto-g5s/development/kernel-tweaks-t3744384/page2)
also i repaked that XperienceOS for mi3s from new.dat to meta-data for better wiev without install
download the rom and study it
https://drive.google.com/open?id=1Cp...L_gtJ1zQIqIOca
!!! do not install it!!!!
@kalyansundhar
Can you use this?
Many thanks for your hard work.
Can you maybe release your software on github?
I want to used it for the Motorola G5s. Its almost the same device only I need not suc as vendor but OEM as vendor. But that can I fix if I have your code.
Yeah I have it for Moto Z play too but u need to wait until my isp fix my internet issues , so for now I can't upload the source sorry
I hope it can be fixed in 3 days
-------------------------------------------------------------------
I ask the developer to release his source code. We have to wait till his internet is fixed:laugh:
Look there is a ARM 32bits system image thats support's Treble
Download:
v12 (android-8.1.0_r15):
system.img for A/B ARM64 devices with GApps and SU
system.img for A/B ARM64 devices vanilla
system.img for A-only ARM64 devices with GApps and SU
system.img for A-only ARM64 devices vanilla
system.img for A-only ARM32 devices vanilla
Patches for custom ROMs build
Source: https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
Dear members, any luck with porting MIUI for Moto G5s plus?
Request you to please guide and share link.
Related
I'm trying to build https://github.com/oneplusoss. I've generated vendor blobs from 3.5.4 full ota zip, because it can't work to access /system via adb pull on user builds (would need a rooted user-debug build in order to fetch all blobs). You can find the final blob collection here: https://github.com/nvertigo/android_vendor_oneplus_oneplus3T
I have massive issues to get device/qcom/hammerhead-kernel (2Mbit with consistent connectionmdrops), so I <remove-project .... /> that one, since that's prebuild kernels for hammerhead. Do I need some dtds from that git?
The build process runs fine (build.sh -c, as well as make, as well as make otaimage). But I can't get it boot far enough (with boot.img-nosecure) to get any logs: it starts with the oneplus-logo (not the three dot animation) the capacitive buttons show their lights, went off again and after about 10 s the device reboots to recovery. Any way I flash the source build rom (fastboot flash or flashing the ota-package via twrp shows the same results.
Sadly neither boot.img nor boot.img-nosecure give me a /proc/last_kmsg...
Any ideas are appriciated. Thanx in advance.
An other question: does the capacitive buttons light indicating extracting ramdisk? That would match my obsevation, that they are switched on longer on twrp boot, then on system boot, since recovery ramdisk is larger.
If someone wonders, why I are trying this: it's not for engancing features, but for two reasons: because the source is there, and because I'm an oldschool gentoo dickhead: what hasn't run through my compiler shouldn't be on my device (also some kind of chain of trust... ).
Been there, done that, have the t-shirt:
finally I got oss to boot: problem was missing f2fs support for data in fstab. It's running fine and srable.
I naivly thought, it's the source of oos - but it's not: it's plain aosp without any custumation (besides it's running on 3t and some codeaurora parts). No file manager, no capacitive buttons, no no-disturb-button-support, really insane AAPT comfiguration (elements and onscreen-buttons [as stated: no capacitive buttons availible]mare that large, that it feels like an htc magic on steroids).
But: it's a working codebase.
For me the most important finding is the camera used on oss: it's codeauroras snapdragon camera. I pulled the apk and 4 libs, and it's working on oos. If anybody is interested, I can make a flashable zip. Since I'm no photographer, I'm not the one to judge the quality and playing with manual options. The snapshots with default settings are as good (or as bad - YMMV) as with oos stock cam.
I Thing they need to put more features in one plus 3 OS cause there is lil bit heavy smartphone so they need to do more additions
harshsharma9619 said:
I Thing they need to put more features in one plus 3 OS cause there is lil bit heavy smartphone so they need to do more additions
Click to expand...
Click to collapse
Watch out to not confuse oos (oxygenos: proprietary closed source with quitemsome features; i.e. capacitive buttons) with oss (OnePlusOpenSourceSoftware: castrated aosp without anything).
For more features: I'm looking very forward to lineageos, when M kernelsources are published by oneplus.
SnapdragonCamera for OxygenOS
Packaged:
https://forum.xda-developers.com/oneplus-3t/themes/apk-snapdragoncamera-codeaurora-build-t3533687
nvertigo67 said:
I've generated vendor blobs from 3.5.4 full ota zip, because it can't work to access /system via adb pull on user builds ...
Click to expand...
Click to collapse
How do you extract the files from the OTA zip? Of course I know how to unzip a file but I mean how to get the actual files out of the image files. Can this be done with basic Linux Tools?
freepenguin84 said:
How do you extract the files from the OTA zip? Of course I know how to unzip a file but I mean how to get the actual files out of the image files. Can this be done with basic Linux Tools?
Click to expand...
Click to collapse
unpack the rom (you need unpackbootimage - either from your dist, or from android sdk); unpack system.new.dat (sdat2img.py - from your dist, or search with google, don't know if this is in sdk); mount system.img somewhere; edit pull_library.sh from adb pull to cp.
This pull_library.sh is for oss from end of february, you have to edit the current one and - of course - have to change the source of the cp command to meet your local paths:
https://github.com/nvertigo/local_manifest/blob/oneplus/oneplus3t_N/pull_library.sh
View attachment 4567426
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
What's a GSI?:
A GSI literally means Generic System Image. It is a general system image meant for no specific device. Treble enabled devices have the capability to run a GSI. You can find a GSI here: Phh-Treble
ZTE Axon 7 hardware vs Treble implementation:
Our Axon 7 is an 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
What's Packaged in the zip:
A boot image (kernel)
A compressed vendor image (vendor)
Requirements:
- Unlock bootloader
- Installed patch EDL to add /vendor part. 800Mb
- Installed TWRP 3.2.1-8 - TREBLE
How to install:
- Format /system, /data and /cache, wipe /vendor
- Install Treble flashable zip package Project_Treble_v1.0-by-NFound
- Install GSI .img in /system part. How to flash a Generic System Image (GSI) on Project Treble supported devices
- Reboot
Alternative Instruction
Working:
Camera (and flashlight)
WiFi
Bluetooth
Telephony (Calls and Data)
Audio (Record and Playback)
Video Playback
Sensors
Broken:
Encryption (format data or remove encryption when coming from a non-treble rom)
Sepolicy is still permissive
Nothing else? Otherwise please report it!
Download:
- TWRP 3.2.1-8 TREBLE
- AXON7_GPT_ADD_VENDOR_800MB
- Project_Treble_v1.1-Axon7-by-NFound
Available GSI images is here
Android Pie Release 1 and other (video proof on Axon 7)
Fixes:
- More fixes for Treble ROM by @Kranoner
Credits:
@djkuz for add part. /vendor
@NFound for the fact that this dude did this for us real
Contributors:
@NFound
OS Version based: 8.X Oreo
ROM Kernel: Linux 3.18.71
ROM Firmware Required: Official BETA B12 Oreo
Version Information
Status: Testing
Source-Code Vendor
Created 2018-08-08
Last Updated 2018-08-12
Reserved
Thank you very much @NFound, i will test this asap. Does the gapps need to be flashed after install?
Waancho said:
Thank you very much @NFound, i will test this asap. Does the gapps need to be flashed after install?
Click to expand...
Click to collapse
Any ARM64 with opengapps.org for 8.x, in GSI 9.x Gapps included
Dear friends! Do not forget to backup before installation, this is a test version. It's time for me to sleep, write. As time will be, I will read your comments. If you find bugs - be sure to specify the version of GSI Android 8.x or 9.x
Thank you!
Hey need fast answer! In this guide is talking about a Vendor 8.1 and 8.0 and 8.0 does not work with this rom, so my question is does this rom support your treble? https://forum.xda-developers.com/pr...development/aosp-9-0-android-9-0-gsi-t3826357
Source code vendor blobs in OP
NFound said:
Source code vendor blobs in OP
Click to expand...
Click to collapse
I am a bit confused: how would non-standard hardware like our famous DAC be used in a treble ROM? Would the vendor partition make specific APIs available for such non-standard hardware?
Thank you for this. Maybe its a stupid question, but does the DAC properly function even when we install a GSI?
I have a feeling that a proper fully functional treble will make the other custom ROM thread for Axon 7 obsolete.
so no EDL needed? I'm so happy because i dont have a windowscomputer.
*edit: i think i did not read good and windows is still needed
Zobat said:
so no EDL needed? I'm so happy because i dont have a windowscomputer.
*edit: i think i did not read good and windows is still needed
Click to expand...
Click to collapse
You dont need a windows-pc. Only twrp
Do we need to install the project treble zip in the OP if we already enabled treble by EDL?
Let me see if I got this whole treble situation straight :cyclops:
I'm running the latest AEX but I assume this guide contains a more updated "treble" so to speak, is that correct? In order to try the GSI's do I need to follow this guide and wipe everything or will the next AEX release update treble and contain the new fixes?
https://sourceforge.net/projects/resurrectionremix-oreo/files/arm64aonly/
Arm64 and A only. Should be working right?
BaamAlex said:
You dont need a windows-pc. Only twrp
Click to expand...
Click to collapse
He DOES need a windows pc since in order to enable treble he needs to flash a file via EDL
troy5890 said:
Do we need to install the project treble zip in the OP if we already enabled treble by EDL?
Click to expand...
Click to collapse
You will need to install this again Project_Treble_v1.0-by-NFound
it contains bug fixes
bornlivedie said:
He DOES need a windows pc since in order to enable treble he needs to flash a file via EDL
Click to expand...
Click to collapse
For this zip here he dont need a PC. For the EDL package yes.
Just wanted to thank you and talk about my experience.
Converting the device to Treble was a breeze. Can be done in under 5 minutes with no issues at all. I'm currently running Android P PR1 with no major problems.
However, when trying to install the GSI (totally not related to your work, but wanted to comment on this so everyone can enjoy treble) I ran into a small problem (error 7) when flashing the POST sGSI zip files. I resolved this by doing the following:
Install the treble zip
Install the GSI
Install the treble zip again
Install the 3 zip files in order
This worked out fine for me.
Again, thanks a million times on your epic feat. This is no small task, and is very welcome. It marks a before and an after.
You, sir, are heaven-sent. Thank you for your good work.
bornlivedie said:
Install the treble zip
Install the GSI
Install the treble zip again
Install the 3 zip files in order
Click to expand...
Click to collapse
Why a second time?
Dear friends!
In the video I am used Release 1.
1. Flash Project Treble
2. Flash GSI
3. !!! In Mounting - UNMOUNT and MOUNT system and vendor!
4. Install patches 1,2,3
5. Reboot
Android Pie Release 1 (Download A-only and patches): https://androidfilehost.com/?w=files&flid=280192
Work GCam: https://github.com/AospExtended/platform_vendor_aosp/blob/8.1.x/prebuilt/common/apk/Gcam.apk
NOTICE: If during a call on Android 9 you do not hear the subscriber. (thx @atakan33 )
PS Here is another list of available GSI ROMs, use the translator!
9.x https://4pda.ru/forum/index.php?act=findpost&pid=75394613&anchor=Spoil-75394613-2
8.x https://4pda.ru/forum/index.php?act=findpost&pid=75394613&anchor=Spoil-75394613-3
Thank you!
This is a TWRP fully Treble-ready with "Treble enabler" option in order to repartition safely the device.
Features:
TWRP fully Treble-ready;
Maintained with latest TWRP version;
Fully compatible with non-Treble devices - can be used as normal without Treble partitioning;
USB-OTG fixed
Has 'TWRP survival' function for automatically re-installing TWRP recovery when installing ROMs and kernels;
Adds a "Treble enabler" option that allows you to repartition your device in order to support Treble.
Has the option to shrink userdata to create Vendor partitions. All relevant partitions will be resized and formatted in one go.
If you shrink Userdata, it will ERASE DATA AND INTERNAL STORAGE COMPLETELY - but your device will stay compatible with all existing non-Treble ROM's
Instructions
Flash the recovery.
Reboot Recovery
Optional - Use the "Advanced > Treble enabler" option for repartition option.
If you opted to repartition for Treble, you are ready to flash a Treble ROM/Vendor pack.
About TWRP survival
TWRP survival is a simple hook that detects if a boot.img will be installed and restores TWRP after it's flashed. This only works if you have booted TWRP with Tissot Manager 2.0 from a real recovery boot - NOT from a recovery 'hot boot' (fastboot boot method).
You will see in the install log if a TWRP survival attempt is successful in the flash text output.
Automatic TWRP survival works when:
Flashing a ROM ZIP (or AIO) with TWRP
Flashing a boot.img in TWRP "Install Image" mode
Automatic TWRP survival does NOT work when:
Flashing a boot.img via fastboot
Restoring boot in a TWRP backup
Any other way of flashing a boot.img
In these cases, be sure the use the TWRP Installer immediately after flashing or restoring a backup - otherwise you may get the device into a confused state (especially if you restore a non-TWRP boot then try to install an AIO ROM without installing a new TWRP first).
Download
https://zenfone3-dev.gitlab.io/recovery/twrp-treble/
FAQ
Q) After I flash TWRP, I get kicked into fastboot when trying to boot the ROM!
A) Your kernel is not Treble-compatible.
Q) How do I update TWRP?
A) Just flash the ZIP installer again, then Reboot Recovery. Note that this will erase Magisk on BOTH slots if you have it installed to either, requiring you to reflash it to one/both slots. See my Treble guide FAQ section for more info on Magisk interaction.
Q) My PC can't see the MTP (storage) device from TWRP!
A) For dualboot compatibility, MTP is automatically disabled at various points. Just enable it manually in the Mounts menu to get access.
Q) If I shrink Userdata for Treble, will stock and OTA work?
A) I have heard varying results on this. It does for some, not for others. Please assume that this will NOT work.
Q) Can I restore a non-Treble TWRP backup after I repartition for Treble? And the other way around?
A) Yes!
Q) I see "Failed to mount '/system' (Device or resource busy)" red error in TWRP after flashing a ROM
A) You can safely ignore it. You just need to reboot recovery before you can flash anything else (like Gapps) to this ROM.
Thanks to:
@CosmicDan for his files for Tissot Manager & this thread template
@makorn645, @planet9, @Oki for Party
XDA:DevDB Information
TWRP Recovery for Zenfone 3, Tool/Utility for the Asus ZenFone 3
Contributors
Giovix92, makorn645,
Source Code: https://github.com/Giovix92/android_device_asus_zenfone3/tree/twrp-8.1
Version Information
Status: Stable
Current Stable Version: 20190312
Stable Release Date: 2019-03-12
Created 2019-03-12
Last Updated 2019-03-12
@Giovix92 Does this mean I can use any ROM that is Treble? Or have some restrictions.
dVinsmoke said:
@Giovix92 Does this mean I can use any ROM that is Treble? Or have some restrictions.
Click to expand...
Click to collapse
Just the treble los16 zenfone3 on our forum for now
iamROOTX said:
Just the treble los16 zenfone3 on our forum for now
Click to expand...
Click to collapse
But then I see no difference from a "normal" ROM ported specifically to a device. Should not Treble support be able to use them on several different devices?
For example, should not I be able to go to the AEX Treble download area and use it on ZF3? If it would not be the same as having to wait for a dev port AEX to ZF3.
I'm really confused lol
dVinsmoke said:
But then I see no difference from a "normal" ROM ported specifically to a device. Should not Treble support be able to use them on several different devices?
For example, should not I be able to go to the AEX Treble download area and use it on ZF3? If it would not be the same as having to wait for a dev port AEX to ZF3.
I'm really confused lol
Click to expand...
Click to collapse
What do you expect? It's still in an early stage of porting. Some device specific bits still run from /system. GSI's may work but I doubt anything will work properly.
And I don't plan of supporting GSIs anyway.
makorn645 said:
What do you expect? It's still in an early stage of porting. Some device specific bits still run from /system. GSI's may work but I doubt anything will work properly.
And I don't plan of supporting GSIs anyway.
Click to expand...
Click to collapse
Being sincere I did not expect anything, since I did not understand anything lol This Treble left me was confused lol
So what's the difference of the Lineage Treble for a Lineage normal running in ZF3?
dVinsmoke said:
Being sincere I did not expect anything, since I did not understand anything lol This Treble left me was confused lol
So what's the difference of the Lineage Treble for a Lineage normal running in ZF3?
Click to expand...
Click to collapse
Currently nothing much ( updated proprietary bits + vendor image taken in place )
Maybe in the near future when everything is in place. I'll seperate Vendor image from builds ( noticable smaller updates )
makorn645 said:
Currently nothing much ( updated proprietary bits + vendor image taken in place )
Maybe in the near future when everything is in place. I'll seperate Vendor image from builds ( noticable smaller updates )
Click to expand...
Click to collapse
Also, when vendor img will be split from the ota package, with (if necessary) some adjustments we can flash GSI ROMs easily.
Great work guys!! Waiting for vendor partition, for some tests!
Williknot said:
Great work guys!! Waiting for vendor partition, for some tests!
Click to expand...
Click to collapse
Well, repartition works fine. After repartition a new /vendor partition of 1024mb will be made.
Although, you'll loose your data (apps+personal). So make sure to do a full backup of your device.
Feedback:
* HAVE A BACKUP. This tool messes with your partition table and is still unstable. Your data partition can be resized to the wrong size.
Will come back after a few months to provide more feedback. Appreciate the work guys.
Works fine for me, data is correctly resized even with multiple changes from normal to treble and back...
Can't seem to wipe /cache partition.
Anyone knows why?
[QS said:
;79165451]Works fine for me, data is correctly resized even with multiple changes from normal to treble and back...
Can't seem to wipe /cache partition.
Anyone knows why?
Click to expand...
Click to collapse
A bugfix release will be coming along with the next LineageOS build.
fcbn98 said:
Feedback:
* HAVE A BACKUP. This tool messes with your partition table and is still unstable. Your data partition can be resized to the wrong size.
Will come back after a few months to provide more feedback. Appreciate the work guys.
Click to expand...
Click to collapse
Well, that's normal.
Since you're going to make a new /vendor partition of about 1024mb, /data should be deleted & recreated in order to give some space to the new partition.
Also, what do you mean with "can be resized to the wrong size"?
The tool is pretty stable tho. Can you give more info such as model (ex. ZE552KL 4/64), script version (ex. 4.3b) & other?
Thanks.
I've successfully installed this tool, although attempting to install the new LOS 16 Android 9 ROM we have on this forum results in an error: 7, "Failed to mount '/vendor' (Invalid argument)"
From what I've perused so far in my research, that error mostly crops up on non-treble builds of TWRP, yet I definitely used the latest version from your website. I also redownloaded the latest version of LOS just to recheck, and yep, nothing's changed.
Any clue about what's going on here? I don't know much about Treble ROMs, or custom ROMing to be all honest.
EDIT: I have found the enable Treble option. Even when enabled and installed, after reboot, the /vendor partition cannot be read. It seems that after doing this too, I can't load files over USB, or mount my SD Card. I'm getting pretty confused as to what's happening. I can't boot into system, and fastboot won't connect to my PC.
Kaisogen said:
I've successfully installed this tool, although attempting to install the new LOS 16 Android 9 ROM we have on this forum results in an error: 7, "Failed to mount '/vendor' (Invalid argument)"
From what I've perused so far in my research, that error mostly crops up on non-treble builds of TWRP, yet I definitely used the latest version from your website. I also redownloaded the latest version of LOS just to recheck, and yep, nothing's changed.
Any clue about what's going on here? I don't know much about Treble ROMs, or custom ROMing to be all honest.
EDIT: I have found the enable Treble option. Even when enabled and installed, after reboot, the /vendor partition cannot be read. It seems that after doing this too, I can't load files over USB, or mount my SD Card. I'm getting pretty confused as to what's happening. I can't boot into system, and fastboot won't connect to my PC.
Click to expand...
Click to collapse
Did you follow these steps properly?
https://zenfone3-dev.gitlab.io/tutorials/repartition
can i flash android q gsi images using treble recovery.
Switching back to stock rom
If I have made the treble partition using this recovery is there any way to go back to stock rom?
Avinash007 said:
If I have made the treble partition using this recovery is there any way to go back to stock rom?
Click to expand...
Click to collapse
Wipe vendor, data, cache, dalvik partition and flash any ROM normally.
Can i flash android Q gsi image using this recovery on ze520kl
Android Version : Android 10 Ported Pixel Easy recovery install.
You should be having proper knowledge of flashing Custom ROM and how to Restore a phone if anything goes wrong.
Take complete backup before taking any action based on this thread. I am not responsible for any action taken by you.
I am just compiling all the information / files available on different websites into this thread, I have patched together with cyber spit, bubblegum, and tape, for a pretty much fully working Android 10 running rom. I have removed what I believe to be all of the bloat. Worked to modify a working android 10 vendor. Latest Magisk 19.5 installer is all ready included as of Oct 10th 2019 as well as the modified boot for root access. Gapps are also included for a fully functioning playstore.
All Credit goes to respective developer/s. I request XDA moderator and or Developer of Respective files to let me know if I have forgotten to mentioned (give credit) their name in this thread. The Download Links are given directly from respective Developer/s.
You need the following two files to run Android 10 on Mi Max 2 (Oxygen). This ROM recovery is ported with many patches and customized from various sources. This ROM maybe Stable enough for your daily use on Mi Max 2. I have access to two MM2 4/64 Global versions using a 1tb sd card one on At&t the other on Tmobile.
1a. Treble Mi Max 2 Recovery 3.2.1 (https://androidfilehost.com/?fid=5862345805528056270)
1b. OrangeFox Recover 10
https://sourceforge.net/projects/orangefox/files/oxygen/OrangeFox-R10.0-Stable-oxygen.zip/download
2. Android 10 Ported Pixel.
https://drive.google.com/folderview?id=13Ro_0NRv4SfD3UqVUCyR2Ki2ojjiKwDL
First step:
Start your phone into recovery and Flash a Treble recovery, if already not flashed. Restart into Recovery.
Click Wipe then Advance wipe and clear System, Vendor, Boot, Data, Cache, and Dalvick cache.
Second step:
Now Extract the Downloaded Rom files in Recovery backup folder. You should know where and how to Extract. (Use extract tool for android or pc then copy paste to recovery backup folder.)
Third step:
Click Restore and Select System, Boot, Vendor and Swipe to confirm. Wait for restore to complete. If any errors, Reboot recovery and try again. Or Mount the System, Vendor, Boot and try again. After Restore completes Reboot. Please allow 1-2 Minutes for first boot, Ignore any errors.
If I missed anything in the above, kindly let me know to include. If you make any further updates / patches that makes this ROM more stable / perfect or enables new features, please don't hesitate to message me to include in this thread.
I have an old PC running windows with 8gb HDD (Asus 901 eeepc) max at any one given time, So if you would like to make the recovery image into a flashable zip, I'd be happy to update/add it.
If you can afford it, Im trying to save for a computer from this decade, any help is appreciated
https://www.paypal.me/LiamMcGinnisIv
If you would like to use the boot, vendor, system, or any other files, All I ask is pass on the proper credits.
Credits : liammc83 | Mohzuned
Original Pie Kernel Source - Hardrock83 (RIP) | beingtejas v5
Best of Luck and Happy Flashing )
Fixes:
Sound has been fixed since initial Android 10 port attempt ( Mohzuned ).
Also added exfat support for external SD cards, rapid charging shows to be working,
Latest magisk as of date posted, Screen mirroring working here as well.
Digital Wellbeing *
Parental Controls *
Main bugs:
Camera, Torch..
I am in my free time trying to come up with a solution, But have also attempted to reach out to V v3k , MaheshTechnicals and others for ideas, or fixes.
Password for the zip;
ungr8f00l
What's the difference between this ROM and one more 10 ROM u have posted , sorry noob here awesome work :good:
liammc83 said:
Android Version : Android 10 Ported Pixel Easy recovery install.
You should be having proper knowledge of flashing Custom ROM and how to Restore a phone if anything goes wrong.
Take complete backup before taking any action based on this thread. I am not responsible for any action taken by you.
I am just compiling all the information / files available on different websites into this thread, I have patched together with cyber spit, bubblegum, and tape, for a pretty much fully working Android 10 running rom. I have removed what I believe to be all of the bloat. Worked to modify a working android 10 vendor. Latest Magisk 19.5 installer is all ready included as of Oct 10th 2019 as well as the modified boot for root access. Gapps are also included for a fully functioning playstore.
All Credit goes to respective developer/s. I request XDA moderator and or Developer of Respective files to let me know if I have forgotten to mentioned (give credit) their name in this thread. The Download Links are given directly from respective Developer/s.
You need the following two files to run Android 10 on Mi Max 2 (Oxygen). This ROM recovery is ported with many patches and customized from various sources. This ROM maybe Stable enough for your daily use on Mi Max 2. I have access to two MM2 4/64 Global versions using a 1tb sd card one on At&t the other on Tmobile.
1a. Treble Mi Max 2 Recovery 3.2.1 (https://androidfilehost.com/?fid=5862345805528056270)
1b. OrangeFox Recover 10
https://sourceforge.net/projects/orangefox/files/oxygen/OrangeFox-R10.0-Stable-oxygen.zip/download
2. Android 10 Ported Pixel.
https://drive.google.com/folderview?id=13Ro_0NRv4SfD3UqVUCyR2Ki2ojjiKwDL
First step:
Start your phone into recovery and Flash a Treble recovery, if already not flashed. Restart into Recovery.
Click Wipe then Advance wipe and clear System, Vendor, Boot, Data, Cache, and Dalvick cache.
Second step:
Now Extract the Downloaded Rom files in Recovery backup folder. You should know where and how to Extract. (Use extract tool for android or pc then copy paste to recovery backup folder.)
Third step:
Click Restore and Select System, Boot, Vendor and Swipe to confirm. Wait for restore to complete. If any errors, Reboot recovery and try again. Or Mount the System, Vendor, Boot and try again. After Restore completes Reboot. Please allow 1-2 Minutes for first boot, Ignore any errors.
If I missed anything in the above, kindly let me know to include. If you make any further updates / patches that makes this ROM more stable / perfect or enables new features, please don't hesitate to message me to include in this thread.
I have an old PC running windows with 8gb HDD (Asus 901 eeepc) max at any one given time, So if you would like to make the recovery image into a flashable zip, I'd be happy to update/add it.
If you can afford it, Im trying to save for a computer from this decade, any help is appreciated
https://www.paypal.me/LiamMcGinnisIv
If you would like to use the boot, vendor, system, or any other files, All I ask is pass on the proper credits.
Credits : liammc83 | Mohzuned
Original Pie Kernel Source - Hardrock83 (RIP) | beingtejas v5
Best of Luck and Happy Flashing )
Fixes:
Sound has been fixed since initial Android 10 port attempt ( Mohzuned ).
Also added exfat support for external SD cards, rapid charging shows to be working,
Latest magisk as of date posted, Screen mirroring working here as well.
Digital Wellbeing *
Parental Controls *
Main bugs:
Camera, Torch..
I am in my free time trying to come up with a solution, But have also attempted to reach out to V v3k , MaheshTechnicals and others for ideas, or fixes.
Click to expand...
Click to collapse
Password?
MaheshTechnicals said:
Password?
Click to expand...
Click to collapse
at post 2
The files dont extract after password
diaselo said:
The files dont extract after password
Click to expand...
Click to collapse
There is an error while extracting files. Archive is corrupted.
Repacked , reupped, downloaded, uncompressed, tested.
Sorry y'all previously ran out of HDD space and tried to pack on external thumb drive, as y'all can tell didn't work out.
But all fixed now.
MaheshTechnicals said:
Password?
Click to expand...
Click to collapse
Password for the zip;
ungr8f00l
diaselo said:
The files dont extract after password
Click to expand...
Click to collapse
Fixed
zavorotnii said:
There is an error while extracting files. Archive is corrupted.
Click to expand...
Click to collapse
Corrected
faraaz3 said:
What's the difference between this ROM and one more 10 ROM u have posted , sorry noob here awesome work :good:
Click to expand...
Click to collapse
First was an attempt to boot.
This has many bug fixes, new features, and its PE
Some Fixes:
Sound has been fixed since initial Android 10 port attempt ( Mohzuned ).
Also added exfat support for external SD cards, rapid charging shows to be working,
Latest magisk as of date posted, Screen mirroring working here as well.
Digital Wellbeing *
Parental Controls *
Booted successfully. Nice ROM. Good job. Android 10 on Mi Max 2. Wow! Waiting when you will fix camera.
Please post Some SS
MaheshTechnicals said:
Please post Some SS
Click to expand...
Click to collapse
Samsung Sh*t ? :silly:
liammc83 said:
Samsung Sh*t ? :silly:
Click to expand...
Click to collapse
Screenshots
zavorotnii said:
Booted successfully. Nice ROM. Good job. Android 10 on Mi Max 2. Wow! Waiting when you will fix camera.
Click to expand...
Click to collapse
Hotspot , IR , working ?
Feel free to post some screen shots
MaheshTechnicals said:
Screenshots
Click to expand...
Click to collapse
Sorry didn't know what you meant
If someone doesn't, I'll try and get some later today, Still getting over illness, now on additional 2 meds for a total of 25...So a little loopy.
And now had a small house fire, So most electrical outlets down, no hotwater, sheesh..... Dogs still alive so no country song yet.
You have any ideas about camera controller fix ?
From Jio outgoing doesnt work might be due to absence of VoLTE but incoming call works on Jio.
OS looks smooth good work liammc83 mate.
maheshkondraju said:
From Jio outgoing doesnt work might be due to absence of VoLTE but incoming call works on Jio.
OS looks smooth good work liammc83 mate.
Click to expand...
Click to collapse
APN all correct ?
*#*#4636#*#*
Have any effect in adjustment ? Under phone information ?
Sorry I don't anything about JIo
No matter on the mi max 2, I never got volte, my carrier didn't support it.. I could barely get a real 4g connection, at only 1mb/down
Screen mirroring dont work..reboot phone
I was able to compile the realme X2 Pro's official kernel release from https://github.com/realme-kernel-opensource/realmeX2pro-X3-AndroidR-kernel-source and I got 3 files generated in arch/arm64/boot folder.
They are:
Image
Image-dtb
Image-dtb-hdr
I just wanted to know how to move further to be able to flash just this kernel (I have a GSI image flashed on /system from TWRP).
Based on the partitions I saw from TWRP, the ones I feel relevant are: Boot partition, Dtbo partition, Vendor Image partition. Which one is it and how do I package the kernel/device tree blob file above to be able to flash to one of these via fastboot? Is that even a valid operation?
I don't want to risk a trial and error approach and possibly screw up further (I have backups of these partitions, but still I'd love to get some insights from the community who might've done this before)
Thanks!