Related
[TREBLE] Project Treble for LEECO MAX 2 (x2)
PHP:
#include "std_disclaimer.h"
/*
* 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 about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
### What is Treble? ###
https://android-developers.googleblog.com/2017/05/here-comes-treble-modular-base-for.html?m=1
I'll keep the technical details about treble away from this thread as it has been covered by xda already.
If you want to know more about that visit here : https://source.android.com/devices/architecture/
Treble is everywhere, so why shouldn't x2 join it?
I'm proud to announce that Le Max2 will now fully support project treble and you can flash Generic System Images (GSI) and even Android P. Exciting right ?
You just need to follow the instructions mentioned and you're good to go.
## How we did it? ##
You might be wondering how I managed to get treble support...
NO, I didn't repartition the phone so you shouldn't worry about bricking the phone unless the directions were not followed properly.
There is an empty and unformatted partition in the phone called "last_parti" with a size of <589mb> and I converted that to our vendor partition, similar to how OnePlus devices were able to achieve teble support without the need to repartition.
You may doubt that that you will still be able to flash stock eui rom, but yes u can and we have tested it. If you encounter any error no 7 during eui flashing? Please switch to a non-treble build of TWRP or just delete block checking in update-script.
If you have any difficulties? You may join our telegram group for help :
https://t.me/joinchat/HFzBDlHXN-52-GZBg7725w
## Things you'll need to download (instructions are below):
New method :
1) Treble supported TWRP : New one by @GalaticStryder https://drive.google.com/open?id=1mx-uGryLXiIR7fDSDL4iBPdXhd7qLHjQ
2) Treble supported builds can be found here : https://www.androidfilehost.com/?fid=5862345805528055916
Previous method :
1) Partition creator zip : https://www.androidfilehost.com/?fid=5862345805528055960
2) Treble supported TWRP : https://www.androidfilehost.com/?fid=5862345805528055961
3) Treble supported builds can be found here : https://www.androidfilehost.com/?fid=5862345805528055916
Let's trebelize your x2 shall we?
**Important: Instructions are absolutly clear, so please carefully follow the steps as written below. I shall not be held responsible for any bricked devices. You do this on your own risk.
New method :
1) Flash the Treble supported TWRP. Again there are multiple ways to flash TWRP like
Use TWRP and flash the new recovery as an image in the recovery partition.
Use fastboot on the computer to flash the recovery image.
If you have root access then you can use an app like Flashify to flash the recovery.
2) Reboot to recovery to ensure the treble version is launched.
3) In the "Advanced" menu please click and swipe on "Treblelize"
4) Try to wipe vendor partition. If Treblelize worked? It should wipe without errors.
Optionally, you can also try to mount Vendor partition to see if it mounts without errors too.
4) After completing 1-4 your device will have vendor partition but it won't be ready to flash GSIs. For being able to do it goto step
5) Wipe system, cache, dalvik cache and data.
6) Flash the AEX Treble ROM which you downloaded earlier.
Previous Method :
1)Flash the Treble supported TWRP. Again there are multiple ways to flash TWRP like
Use TWRP and flash the new recovery as an image in the recovery partition.
Use fastboot on the computer to flash the recovery image.
If you have root access then you can use an app like Flashify to flash the recovery.
2) Reboot to recovery once flashed. (Even if u flashed through twrp ,you should reboot to recovery again)
3) Flash the partition creator zip now. After flashing it it might show an error about cannot mount /vendor, ignore it and go on to
the next step.
4) Click wipe on TWRP homepage, select vendor and uncheck all other partitions and swipe to wipe. Nice you have successfully
created vendor partition.
optional. You can check if you are able to mount /vendor partition from the recovery.
5) After completing 1-4 your device will have vendor partition but it won't be ready to flash GSIs. For being able to do it goto step
6) Wipe system, cache, dalvik cache and data.
7) Flash the AEX Treble ROM which you downloaded earlier.
Bingo! You have successfully trebelized your x2!
Time for some DO NOTs
1) NEVER wipe /vendor. If you do that your device won't work with any GSI. (u should wipe vendor only if u flash non treble rom )In case you accidentally wiped it you can flash AEX Treble rom to get it back. I might provide a vendor.img but don't think like doing it right now.
2) NEVER install A/B GSIs. Our device is treble enabled but doesn't have an A/B partition structure. Le Max2 support A only GSIs.
Instructions for flashing GSI of any Rom
1) Download a GSI from here : https://forum.xda-developers.com/project-treble/trebleenabled-device-development
2) If it is in a zip archive, then please unpack it.
3) You can find instructions here : https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
and reboot
Want to try more awesome things like installing Android P?
Instructions for flashing Android P GSI :
Complete credit for P image goes to : @erfanoabdi
Xda link for P GSI : https://forum.xda-developers.com/project-treble/trebleenabled-device-development/rom-android-p-developer-preview-t3816659
Steps:
1) Download link for P gsi (DP4): https://androidfilehost.com/?w=files&flid=279295
2) Wipe all Paritions except : vendor, internal storage
3) Install P system image to system
4) Mount vendor in TWRP
5) Flash POST-sGSI zips from 1 to 3 in priority
6) Then flash my sensor fix zip here : https://drive.google.com/open?id=11l4p6NxwixMSQlTLhLM_8wuXpvmrNpJq
and reboot
Volte Fix for P : https://drive.google.com/file/d/1h-2qTwhUidU9gDBFzj86RMfZn-vwLOnG/view#
BUGS IN ANDROID P GSI
VOLTE-its fixed
U tell me
Ok, all the best to you!
It is not easy to make complete treble with Zero Bugs
and we tried our best in making that.
I want to include all the contributers so the list is quite large.
Credits and contributors :
@shivatejapeddi (yeah I myself worked very hard to achieve Treble for x2)
@davidevinavil (literally helped me in creating partition and helped in solving crucial bugs )
@ThE_MarD (our official lineage contributer and helped me in solving some bugs)
@Chityanj (helped me with server and testing)
@prajjwal.laad (tester)
@Abhishek4587Kumar (tester)
@yaser59527 (tester)
@Rk585(dunno)
@GalaticStryder (for his newer and easier method to "Treblelize" x2)
Please let us know if we missed anyone.
Donations :
We worked very hard for fixing things and making things work, and I finised all my free google credits and am now using a paid legacy server for building roms.
Want to donate me ?
You can Here : https://www.paypal.me/shivatejapeddi
XDA:DevDB Information
[TREBLE] Project Treble for LEECO MAX 2 (x2) (Complete), Tool/Utility for the LeEco Le Max 2
Contributors
shivatejapeddi, ThE_MarD, Chityanj
Source Code: https://github.com/Chityanj/treble_devicetree
Version Information
Status: Stable
Current Stable Version: 8.1.0
Stable Release Date: 2018-07-23
Created 2018-07-22
Last Updated 2018-09-01
reserved
.Guys If you have any problem or confusion ask us in telegram group or XDA before proceeding
.
Congratulations! Thanks everyone to work in this project!..
Great work guys.
good!
Wow! Impressive stuff guys! How is the P GSI? Working well?
****! All of you are incredible, thanks a mil for this hard work.
I have no words
Congrats to all devs involved
I am unable to understand anything. So dumb.
Pro3 users come to congratulate. How do I admire it! With the same CPU, zl1 can't use Android P.
It's a new way of life Thank you all.
This really works nice, and very easy process,. I am running the AEX treble ROM at the moment, but tried the P gsi for a while - it booted up OK and runs, looks nice, but has a message on boot saying there is an error with the device, and has a notification that the P system is updating that never seems to complete and so you can't log in to google account or complete phone set up.
kanagawaben said:
This really works nice, and very easy process,. I am running the AEX treble ROM at the moment, but tried the P gsi for a while - it booted up OK and runs, looks nice, but has a message on boot saying there is an error with the device, and has a notification that the P system is updating that never seems to complete and so you can't log in to google account or complete phone set up.
Click to expand...
Click to collapse
Did you flash post GSI zips for P?
prajjwal.laad said:
Did you flash post GSI zips for P?
Click to expand...
Click to collapse
Yes, the three of them
kanagawaben said:
Yes, the three of them
Click to expand...
Click to collapse
Ahh. Then it's typical GSI behaviour. Maybe a final version will be more stable.
Thanks to all of the developers for bringing the much awaited treble support in our device.
kanagawaben said:
This really works nice, and very easy process,. I am running the AEX treble ROM at the moment, but tried the P gsi for a while - it booted up OK and runs, looks nice, but has a message on boot saying there is an error with the device, and has a notification that the P system is updating that never seems to complete and so you can't log in to google account or complete phone set up.
Click to expand...
Click to collapse
U should install google play services app link is there in that android p gsi XDA ,download and install problem solved
Crystal-L said:
Pro3 users come to congratulate. How do I admire it! With the same CPU, zl1 can't use Android P.
Click to expand...
Click to collapse
Hi don't worry, pro 3 will get very soon, devs working on it,
shivatejapeddi said:
U should install google play services app link is there in that android p gsi XDA ,download and install problem solved
Click to expand...
Click to collapse
Should have noticed that link earlier when i first tried. many thanks!
just wanted to add i got FC while restoring from the cloud on my google account, i think it was called data transfer tool, i had click on the 'i' to bring up the service/app and then give it storage permissions to continue. after that everything back and even my apps are now updating from the play store.:good:
edit 2: also for those needing usb connectivity after for whatever reason you can enable by going to developer options and changing default usb configuration to file transfer. learning do and donts as i go here as well lol
I have been developing Ubuntu Touch for the Tab A 10.1 2019
This ROM has been tested on both SM-T510 (WiFi version) and SM-T515 (WiFi + LTE)
Any developers reading this and has the device with them and are interested in the project may contact me :
@midhunvnadh on Telegram
Not Working :-
Bluetooth
Audio
Anbox (Android Emulator)
MTP
I am trying to fix these.
Download Files
Download the Halium arm32 GSI file : from Here
(Optional) Download SamsungUSBTethering zip : from here
Ubports Patched Kernel : from here
Get all the above files copied to your External SD Card
Installation
WARNING : I am NOT responsible for any damage caused to your device
If you are following this post, please takeup full responsibility of your device.
Noobs at flashing ROM's can click here: https://telegra.ph/Installing-Ubuntu-Touch-T510T515-08-22
Thanks to @ahamshubham for making this
1.0 Flash STOCK Android 9.0 Pie on your device and install TWRP.
(Because not tested on STOCK Android 10.0)
1.5 Boot into TWRP and Wipe all except external SD. REBOOT to recovery.
2.0 On TWRP : Flash the Lineage 16.0 build. DON'T REBOOT.
3.0 On TWRP : Goto Install -> Install Image -> (Flash halium-boot.img) DON'T REBOOT.
4.0 On TWRP : Goto Install -> (Flash ubports_GSI_installer_V1-arm32.zip).
5.0 (Optional) : Goto Install -> (Flash samsung-usb-tethering.zip)
5.1 Reboot.
(Incase : unable to boot ? , boot into TWRP -> reboot -> system)
samsung-usb-tethering.zip is used to get an SSH console from device to PC. Credits to @erfanoabdi
Please report all the errors you encounter here.
Sources
Kernel : https://github.com/midhunvnadh/android_kernel_samsung_gta3xlwifi
Device Tree : https://github.com/midhunvnadh/device_samsung_gta3xlwifi
GSI arm32 : https://github.com/midhunvnadh/android_device_halium_ubport
The Device tree is a dummy tree with kernel sources linked. Which serves a purpose of compiling halium-boot.img. For more info contact me.
Donations are always appreciated : Just click here
Reserved
Reserved
Pick me! Pick me!
I will gladly take that on. Just got down installing lineage ,17.1 with Kali Linux.. I will see what I can't get done tonight.
mikehunt723 said:
I will gladly take that on. Just got down installing lineage ,17.1 with Kali Linux.. I will see what I can't get done tonight.
Click to expand...
Click to collapse
Hello, you gave me a first reply... !!!
This is my real thread post on ROM's.
I didn't understand what you meant by "Pick me" and "I will gladly take that on. "
Are you looking forward to make contribution to this project ?
Bruh this is amazing work, keep it going!
This looks like an interesting project, none of the download links work for me
nubianprince said:
This looks like an interesting project, none of the download links work for me
Click to expand...
Click to collapse
It is a direct link. It works for me ?
Can you support Galaxy Tab A6?
Mohamed677 said:
Can you support Galaxy Tab A6?
Click to expand...
Click to collapse
I can try if you can give me a device.
Mohamed677 said:
Can you support Galaxy Tab A6?
Click to expand...
Click to collapse
The sm-t580? I tryed like a month ago, and i got the boot.img file to compile for halium7, but not the system image, and los14 is broken so it cant work anyway, and, when i tryed to compile using halium9, i had missing libs.
I also tryed postmarketOS, and it did not boot
(Well, if it did, and i think it did because it didnt reboot into download mode automatically), and screen and usb wasnt working
MIDHUN.V.NADH said:
1.0 Flash STOCK Android 9.0 Pie on your device and install TWRP.
Click to expand...
Click to collapse
Wow. This is exciting news. Really have been longing for a non-android based OS for a long time. Thanks a ton. Will surely donate when I get a job(currently unemployed due to covid):good:
What do you mean by installing stock? You are going to installing LOS 16.0 so can that not be the starting point? Do I have to go back and install stock using Odin and do the whole process again?
aveemashfaq said:
Wow. This is exciting news. Really have been longing for a non-android based OS for a long time. Thanks a ton. Will surely donate when I get a job(currently unemployed due to covid):good:
What do you mean by installing stock? You are going to installing LOS 16.0 so can that not be the starting point? Do I have to go back and install stock using Odin and do the whole process again?
Click to expand...
Click to collapse
Yes, you have to do all those steps.
Why I am asking everyone to install Stock 9.0 is because :
1. On Samsung Exynos Devices developers have an hard time developing Ubuntu Touch.
2. There are changes in partition structure going on from upgrade to Stock 9.0 to 10.0
3. The kernel source of stock Android 9.0 is VERY different from 10.0
4. I wasn't able to get logs from Stock 10.0 due to the partition changes mentioned on (2)
5. Halium 9.0 (Build Engine for Touch) highly recommends Android 9.0/Lineage 16.0 as a base to install upon.
6. Moreover I haven't tested if it boots on stock 10.0 because of (2), (3), (5) and I am currently fixing the bugs.
Please try to out on AOSP 10.0 and let me know if it work
Hello! I installed it on my Galaxy Tab A 2019 T510, however, a strange problem happens. Suddenly the screen goes dark and I can't do anything, even pressing the power button. A little while later the screen goes black, forcing me to use the Volume - / Power keys to restart. Anyone else going through this? I have another question: the installation file (ubports gsi) says arm32. Is the architecture of this tablet arm34 or arm64?
Geek_Ceará said:
Hello! I installed it on my Galaxy Tab A 2019 T510, however, a strange problem happens. Suddenly the screen goes dark and I can't do anything, even pressing the power button. A little while later the screen goes black, forcing me to use the Volume - / Power keys to restart. Anyone else going through this? I have another question: the installation file (ubports gsi) says arm32. Is the architecture of this tablet arm34 or arm64?
Click to expand...
Click to collapse
Hi !, Were you able to boot into the OS ?
I haven't faced that issue can you elaborate ?
The Tablet has an arm64 kernel but the vendor and system are both arm32.
I had to make the arm32 GSI for ubuntu touch to run on this tablet.
The GSI will also work for devices with the arm32 vendor and system.
Geek_Ceará said:
Hello! I installed it on my Galaxy Tab A 2019 T510, however, a strange problem happens. Suddenly the screen goes dark and I can't do anything, even pressing the power button. A little while later the screen goes black, forcing me to use the Volume - / Power keys to restart. Anyone else going through this? I have another question: the installation file (ubports gsi) says arm32. Is the architecture of this tablet arm34 or arm64?
Click to expand...
Click to collapse
Hi ! Thank you for your reply.
Were you able to boot into the OS ?
I haven't faced that issue. Can you elaborate ?
The Tablet has an arm64 kernel but the vendor and system are both arm32 eventhough some devices with the same SoC has full arm64.
I am trying to port arm64 vendor into the device but I think arm32 will be better because the device only has 2GB RAM (Atleast on my device)
I had to make the arm32 GSI for ubuntu touch to run on this tablet.
The GSI will also work for devices with the arm32 vendor and system.
Worked!!
I was looking forward to run Ubuntu Touch on my Samsung Galaxy Tab A (SM-T515NZKDINU). I contacted MIDHUN.V.NADH, he helped me through the process and we got Ubuntu Touch running on my device. I would like to thank him for his help and his post. I, however, felt that I could not follow the instructions in the post very easily. Maybe, this is because I am doing something like this for the first time. So, I compiled a list of instructions to follow. I will send him this list of instructions and post them here too. I feel they will be helpful for people looking to run Ubuntu Touch on the same device.
MIDHUN.V.NADH said:
Hi !, Were you able to boot into the OS ?
I haven't faced that issue can you elaborate ?
The Tablet has an arm64 kernel but the vendor and system are both arm32.
I had to make the arm32 GSI for ubuntu touch to run on this tablet.
The GSI will also work for devices with the arm32 vendor and system.
Click to expand...
Click to collapse
Yes. I managed to initialize, however, this problem happens to me. I uninstalled Ubuntu and returned to android. Someday, when I have something stable, I test it again.
And about the processor architecture, I understand your explanation. Thank you!
Just adding instructions on how I did it on my device
My device details:
Device Model Number: SM-T515 (NZKDINU)
Linux Kernel Version: 4.4.111-17420370
Instructions for SM-T515:
1) Download these files using the links given in the post I am commenting on:
a) Halium arm32 GSI file
b) Ubports Patched Kernel
c) (Optional) SamsungUSBTethering zip
2) Copy all the above files to your External SD Card and insert this SD card in the device (tablet)
3) Flash STOCK Android 9.0 Pie on your device (tablet) and install TWRP:
a) For installing TWRP, use the following post: https://forum.xda-developers.com/ga...very-twrp-3-3-1-2019-galaxy-tab-10-1-t3934805. The instructions for installing TWRP as given in this post are:
i) Unlock bootloader (See the end of my comment)
ii) Hold Vol Up & Vol Down buttons during restart to enter Download mode
iii) Install TWRP to AP with Odin
iv) Hold Power & Vol Up buttons during restart to enter TWRP recovery
v) On TWRP: Swipe to allow modifications
vi) On TWRP: Wipe -> Advanced Wipe -> Select all except SD card
vii) On TWRP: Reboot -> Recovery
4) On TWRP: Go to Install -> Install Image -> (Flash halium-boot.img. Partition to flash image is BOOT). DON'T REBOOT. PRESS BACK.
5) On TWRP: Go to Install -> (Flash ubports_GSI_installer_V1-arm32.zip. Don't check any check boxes)
6) (Optional) On TWRP: Goto Install -> (Flash samsung-usb-tethering.zip)
7) Reboot
8) Ubuntu Touch will open. The password is: phablet
Unlocking Bootloader (Check this post: https://www.getdroidtips.com/oem-unlocking/):
1) Enable Developer Mode in Device Settings
2) Enable OEM Unlocking Option in Developer options after connecting to WiFi and setting the year in the phone to the year 2019
3) Get into Device Unlock Mode: Press (Volume Up Key + Volume Down Key + Insert USB Cable in the phone) while restarting the phone
4) Unlock bootloader. (Very Important!!) DON'T LET THE DEVICE BOOT INTO THE ANDROID OS AFTER UNLOCKING DEVICE BOOTLOADER
MIDHUN.V.NADH said:
Yes, you have to do all those steps.
Why I am asking everyone to install Stock 9.0 is because :
1. On Samsung Exynos Devices developers have an hard time developing Ubuntu Touch.
2. There are changes in partition structure going on from upgrade to Stock 9.0 to 10.0
3. The kernel source of stock Android 9.0 is VERY different from 10.0
4. I wasn't able to get logs from Stock 10.0 due to the partition changes mentioned on (2)
5. Halium 9.0 (Build Engine for Touch) highly recommends Android 9.0/Lineage 16.0 as a base to install upon.
6. Moreover I haven't tested if it boots on stock 10.0 because of (2), (3), (5) and I am currently fixing the bugs.
Please try to out on AOSP 10.0 and let me know if it work
Click to expand...
Click to collapse
Hi, I just tried it out on my device. I had stock 9.0 over which I had flashed Lineage OS 17.1(based on Android 10). Over that, I flashed LOS 16, halium-boot, ubports-gsi and usb tethering. Worked for me.
I have to say, I have a pinephone and it seems that ubports on Samsung tab is faster than on pinephone.
antoine62 said:
The sm-t580? I tryed like a month ago, and i got the boot.img file to compile for halium7, but not the system image, and los15 is broken so it cant work anyway, and, when i tryed to compile using halium9, i had missing libs.
I also tryed postmarketOS, and it did not boot
(Well, if it did, and i think it did because it didnt reboot into download mode automatically), and screen and usb wasnt working
Click to expand...
Click to collapse
Did you ever get this to work/ any tips for trying because I really want this to work (I am trying at the moment).
Hi. When I first installed LOS 18.1 I had problems with fingerprint not working, so I have written a detailed guide how to fix it. Just a disclaimer - I am not responsible if you somehow break your phone while following this guide.
I am also a noob on custom ROMs, but I have done the exact same steps, and my phone appears to be working fine, so you should be all right too. After all, these steps are almost identical to all custom ROMs installation instructions, the difference is that this time we use OrangeFox recovery instead of TWRP, because LOS 18.1 seems to work better with it.
NOTE:
When I used this method myself, I went back to latest MIUI ROM. I don't know if it is necessary, but I think everything should work fine without reverting to MIUI. If you would like to try fixing it without installing MIUI ROM, then go to the first reply below for a simplified guide. Nevertheless, I recommend reading the full guide anyway, just to get a better understanding of what steps you will have to do.
Also, some steps can be skipped because probably many of you have already done them when you were installing LOS or other custom ROMs. I have only tested this fix on LOS 18.1 but it might work on other custom ROMs too, I think.
I've written this guide while following OrangeFox recovery guides, and getting help from Redmi Note 4 users on Telegram groups.
FULL GUIDE (INCLUDES GOING BACK TO MIUI):
1. Install ADB + Fastboot in your PC (I assume you use Windows 10).
Download these files:
SDK platform tools: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Google USB Driver: https://dl.google.com/android/repository/usb_driver_r13-windows.zip
I am not sure if Google USB Driver is necessary, but install it anyway because I had it installed too.
For installation instructions, use the attached "ADB Fastboot installation.txt" file.
You can check this video for visual guide as well:
At this point I recommend backing up important data (photos, videos, documents, SD Card, etc.) from your phone to PC, Cloud or other safe storage.
2. You will need to go back to latest MIUI ROM. Use this page for instructions: https://c.mi.com/oc/miuidownload/detail?guide=2
If your Mido is global, then download "Redmi Note 4X Latest Global Stable Version Fastboot File Download" from (STEP 2).
VERY IMPORTANT! When flashing MIUI, make sure you select "Clean all" option. DO NOT select "Clean all and lock" (STEP 5).
3. After successful flashing, boot into MIUI. You may encounter this error when booting up MIUI 11: "Find device storage corrupted. Your device is unsafe now." This error also means that Wi-Fi and Bluetooth will not work. Don't worry, this will be fixed.
4. Next, download these files and put them in your SD Card (for example, Download folder).
(note: some zip file names written in this step will be outdated because Mido is still maintained - always make sure to check, download and use latest updated files).
OrangeFox recovery (R11.0) for mido:
https://dl.orangefox.download/5f14b74f26d98d90b476a532
Latest mido firmware:
https://xiaomifirmwareupdater.com/d...4XGlobal_V11.0.2.0.NCFMIXM_83170d3e3a_7.0.zip
LineageOS 17.1 with 3.18 kernel (you will need to install it first):
https://github.com/zeelog/OTA/releases/download/27.0/lineage-17.1-20201214-UNOFFICIAL-3.18-mido.zip
LineageOS 18.1:
https://github.com/zeelog/OTA/releases/download/41.0/lineage-18.1-20210417-UNOFFICIAL-mido.zip
GApps - "MindTheGapps arm64" was recommended by LOS Team for LOS 18.1 when I wrote this guide (before installing ask the ROM maintainer or users if this is still the recommended version of GApps):
MindTheGapps-11.0.0-arm64-20210412_124247.zip | by Alessandro Astone for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Also don't forget to download "persist.img" file attached below.
5. Now, make sure that your phone is charged and has more than 80% battery (just to be safe).
Also note that after the following step, you won't be able to boot to MIUI anymore, so make sure you have made a backup of your files.
Install OrangeFox recovery using this guide:
Installing OrangeFox Recovery
wiki.orangefox.tech
6. Now, follow the instructions written in the attached "Fingerprint fix and MIUI errors" text file. (note: some zip file names in step 3 of this text file will be outdated because Mido is still maintained - always make sure to check, download and use latest updated files)
7. Finally, follow the instructions written in the attached "Readme - LOS 17.1 and 18.1 installation" text file, you should start from step 4. (note: some zip file names in step 1 of this text file will be outdated because Mido is still maintained - always make sure to check, download and use latest updated files)
Good luck!
One user reported that he successfully fixed the fingerprint issue on LOS 18.1 using this guide without going back to MIUI.
When I was fixing this fingerprint problem myself, I went back to the latest MIUI ROM. I did not test this method to see if it works without installing MIUI, but it looks like it should work just fine. In case you want to try fixing it without going back to MIUI, do this:
SIMPLIFIED GUIDE (WITHOUT GOING BACK TO MIUI):
* Back up important data (photos, videos, documents, SD Card, etc.) from your phone to PC, Cloud or other safe storage.
* Make sure that you have OrangeFox recovery installed, if not - install it.
* Download all the files mentioned in the step 4 of my initial post of this thread and put them on your SD Card. (check if there are any updated files before downloading, like newer ROM update, etc.)
* Download attached "Fingerprint fix and MIUI errors" text file, "persist.img" file and "Readme - LOS 17.1 and 18.1 installation" text file.
* Follow the "Fingerprint fix and MIUI errors" text file guide starting from step 8.
* Follow the "Readme - LOS 17.1 and 18.1 installation" text file guide, starting from step 4. I advise not to skip steps 17-18, although I'm not sure if installing latest Mido firmware is necessary at this point. But I think you should install it, just in case.
Good luck!
Cheers for all your efforts, @Rigadelt !
I'm trying your guide, as I can't get my fingerprint working in LOS18.1, although it works just fine in LOS17.1 ...
Can I ask you:
1) what for are your steps 10+11 & 23+24 in your "Readme - LOS 17.1 and 18.1 installation.txt" ?
2) at what point/step have you encrypted your phone?
Cheers! raimerik
Hi, @raimerik
1) I was advised by the Mido Telegram group users that Rebooting to recovery after ROM or GApps installation ensures that there is a lesser chance of errors during the finalizing of the ROM installation. I'm not sure if that is true, but it shouldn't hurt doing it this way either.
2) I did not encrypt my Mido, so I can't answer this question. You can find info in this post: https://forum.xda-developers.com/t/...-mido-vanilla-by-zeelog.4186179/post-83861307
What I would try to do:
* I would follow the "Readme - LOS 17.1 and 18.1 installation.txt" guide and install LOS 18.1 ROM without GApps (step 19 is the last step).
* After 18.1 ROM flashing, I would tap on "Wipe Caches" and then reboot to recovery.
* After the phone successfully reboots to OrangeFox recovery, I would then follow the Encryption guide written in the post I linked.
* After Encryption -> Dirty flash of LOS 18.1 ROM -> GApps installation process, I would reboot to recovery once again, and then try to boot the phone and see if everything works.
If I'm not mistaken, @manizuwo has fixed the fingerprint problem and encrypted his Mido using this guide, so you could ask him for advice.
Good luck! I also encourage you to share the results and info with other users here or in the main LineageOS 18.1 thread.
Rigadelt said:
* After 18.1 ROM flashing, I would tap on "Wipe Caches" and then reboot to recovery.
* After the phone successfully reboots to OrangeFox recovery, I would then follow the Encryption guide written in the post I linked.
* After Encryption -> Dirty flash of LOS 18.1 ROM -> GApps installation process, I would reboot to recovery once again, and then try to boot the phone and see if everything works.
Click to expand...
Click to collapse
Hi @Rigadelt - two minds thinking/tinkering alike!
I had updated and booted the 18.1, encrypted, went to recovery, dirty flashed the 18.1 and the gApps, wiped caches and rebooted.
Then I set up security pattern and fingerprint, which still does ONLY work if you activate SECURESTART which is an annoying bug, which the 18.1-thread-manager does not seem to understand...
(In Zeelog's 17.1 with 4.9-Kernel the fingerprint worked WITHOUT SecureStart...)
Hello everyone!
I'm new to this. I have a kate and was able to unlock the bootloader. I installed a fastboot rom (8.1.4) that I downloaded from <https://xiaomifirmwareupdater.com>. I also downloaded a twrp from <https://twrp.me/> and installed it successfully via adb. Then there's this:
If I reboot to the system after twrp installation, it boots normally but when I try to enter twrp, it's not there, it enters standard recovery mode. So it seems it's not kept after rebooting.
If from Windows cmd I boot into twrp, there's no decryption process at the start (as I've seen in videos) and I can't install root (the option is not there). And worst of all, when I leave twrp and reboot the phone it wont start.
So because I'm quite limited in technical knowledge, my temporary solution is to reinstall the old rom again (8.1.4) and get the phone reset. I've already done this twice today.
I suppose I need to install some kind of zip file while I'm inside twrp to make it stay after rebooting (I've seen that for other devices). Is that correct? If yes, how can I identify and find this file, since at <https://twrp.me/> there was just the twrp listed for this device. No zip files there for kate/kenzo.
Any patient friend who would shed some light on this, please?
Thank you very much for reading this and for any help you can offer!
Best wishes!
GZ
Although I found it a little overwhelming at first, I found everything I needed here:
[NEWBIE GUIDE v2.0] MIUI ROMs, TWRPs, ZIPs, BACKUP, FLASH, RESTORE
UPDATED NEWBIE GUIDE v2.0 FOR REDMI NOTE 3 SNAPDRAGON (KENZO) (WORKS FOR ALL MIUI / AOSP / CM BASED ROMs) GUIDE SECTIONS : QUICK LINKS#1 : MIUI ROM | TYPES OF MIUI ROM | TWRP | TYPES OF TWRP #2 : TWRP FLASHABLE ZIPs | FULL PARTITION BACKUP |...
forum.xda-developers.com
Thank you!
In the developer options I have started uploading the GSI ARM64 dynamic system.
I was quite surprised by the possibility.
I'm on Miui Global 12.5.2.0 and AOSP Android 12 was loaded into the second slot automatically and without selection.
Starting the function started the upload and after the upload the prompt to reboot into the other system remained in the top bar.
The reboot went without problems and loaded the AOSP ROM Android 12 in a clean basic environment.
The top bar continued to hold a link to reboot back into Miui.
I returned to a pristine and fully functional Miui system (including settings and data).
The top bar still held a link to reboot into AOSP or remove it. I removed it.
This means that our phone can run two independent systems, one in slot "A" and one in slot "B". These are not virtual slots, but physical slots.
This could be relevant to building recovery.
I can confirm that. figured that's before.
Steps on booting the Android 12 on DSU? I'm using pixel experience and I tried to load the PB4 on DSU but it boots me into an android 11 environment. Does it only work on stock rom?
It could be related to the 12.5.2.0 update.
Presumably the vendor and others will be ready for Android 12.
The firmware package does not include the vendor file, it is obtained by installing the entire Miui ROM or by extraction. Firmware is therefore not enough for change.
StaryMuz said:
It could be related to the 12.5.2.0 update.
Presumably the vendor and others will be ready for Android 12.
The firmware package does not include the vendor file, it is obtained by installing the entire Miui ROM or by extraction. Firmware is therefore not enough for change.
Click to expand...
Click to collapse
i think it only works on stock rom. I installed 12.0.11 and used the DSU loader there. worked fine but the side mounted fingerprint sensor gets treated as a touch input. Could be the custom rom doesn't have the proper dsu config and stuff? Havent tried yet on xiaomi.eu
A little experiment:
I switched in Miui 12.5.2.0 using DSU Loader to GSI ROM. From developer.android.com I downloaded the Android 11 GSI ZIP and took the vbmeta.img from it. Then he downloaded IMG for Lineage OS 18.1 GSI from XDA. I switched the phone to fastboot and flash files (fastboot flash vbmeta vbmeta.img); (fastboot -w flash system system.img); fastbootD is required for system.img. Without deleting anything, I booted the system and Lineage OS 18.1 Treble works.
It's GSI so it's not fine-tuned for our phone, but it works for the vast majority of what's possible. Including fast charging, which detects after a while. For now, the camera is working as well.
A bit complicated, but Lineage OS 18.1 GSI was possible to install. The flash system.img (GSI) itself is not functional. I suppose any GSI system could be run this way.
Generic System Image releases | Platform | Android Developers
developer.android.com
Reverting to the default Miui is no longer available. It would have to be re-flashed.
inn000 said:
Steps on booting the Android 12 on DSU? I'm using pixel experience and I tried to load the PB4 on DSU but it boots me into an android 11 environment. Does it only work on stock rom?
Click to expand...
Click to collapse
Going now to crDroid and I tried running the DSU Loader.
After downloading and selecting reboot to GSI, I reloaded crDroid in the version with android 11.
But the GSI download was version SPB4.210715.014, which is Android 12.
As I found out, it's a GSI version of Android supplied by the Android developer to test and validate new apps.
The fact that Android 12 was not loaded, but again only crDroid Android 11 is related to the fact that our custom ROMs cannot work with the activation of the second slot (A/B).
This is also why OTA updates (running on the system) do not work properly.
For this update you need to automatically switch the active slot, which will not happen! This will cause the OTA update to fail.
Resolving the ability of custom boot.img to work with fastbootD commands can probably fix the problem with the broken OTA.
So far, switching to GSI only works on Miui.
StaryMuz said:
Going now to crDroid and I tried running the DSU Loader.
After downloading and selecting reboot to GSI, I reloaded crDroid in the version with android 11.
But the GSI download was version SPB4.210715.014, which is Android 12.
As I found out, it's a GSI version of Android supplied by the Android developer to test and validate new apps.
The fact that Android 12 was not loaded, but again only crDroid Android 11 is related to the fact that our custom ROMs cannot work with the activation of the second slot (A/B).
This is also why OTA updates (running on the system) do not work properly.
For this update you need to automatically switch the active slot, which will not happen! This will cause the OTA update to fail.
Resolving the ability of custom boot.img to work with fastbootD commands can probably fix the problem with the broken OTA.
So far, switching to GSI only works on Miui.
Click to expand...
Click to collapse
yep only works on stock miui loader. sgsi systems works too, I used pixel 5 pb4 sgsi and it works better than the one on stock miui dsu. the same problems still exists. Audio, power button, etc.
inn000 said:
yep only works on stock miui loader. sgsi systems works too, I used pixel 5 pb4 sgsi and it works better than the one on stock miui dsu. the same problems still exists. Audio, power button, etc.
Click to expand...
Click to collapse
Sorry to bring this up again, but what is SGSI ? What does the "S" stand for