Disclaimer: I am not responsible for any malfunctions of your device or any damage, disintegration, or insanity that results to you or your phone if said event occurs. However I will help out in anyway I can if your device dies after an install of this ROM
Now for the cool stuff, the ROM features are:
It is Deodexed
It is Zipaligned
It has the new GAPPS
It has been Debloated ~200-300mb
Features to come:
Viper4Android
Pure Performance X
Pure Graphics
Xposed Framework (will be optional)
and a couple others.
Rom bugs:
Cant install apps from playstore!!! (if you want to help me out with figuring this out that would be much appreciated)
Steps to flash
1.Flash ROM
2.Clear DATA
3.Flash Gapps Package
4.Boot into bootloader and flash the boot.img from your pc via fastboot with the command fastboot flash boot boot.img
5.Boot go through the setup and wait for the Play Store to update
Links:
ROM
Gapps
Boot.img
Credits for the boot.img go to summer.cat
post pictures, please!
Some people fixed the play store issue simply by changing the timezone of their android device, i think it was a CM branch bug.
If I took the 4.4.4 OTA update, is there any way for me to get root at the current time?
So I can flash this through my safestrap recovery and run 4.4.4 on my Maxx that is rooted with WP Off?
I'm just trying to make sure that Im not reading this wrong, thats all.
Thanks for all of your hard work!
CurbThePain said:
Disclaimer: I am not responsible for any malfunctions of your device or any damage, disintegration, or insanity that results to you or your phone if said event occurs. However I will help out in anyway I can if your device dies after an install of this ROM
Now for the cool stuff, the ROM features are:
It is Deodexed
It is Zipaligned
It has the new GAPPS
It has been Debloated ~200-300mb
Features to come:
Viper4Android
Pure Performance X
Pure Graphics
Xposed Framework (will be optional)
and a couple others.
Rom bugs:
Cant install apps from playstore!!! (if you want to help me out with figuring this out that would be much appreciated)
Steps to flash
1.Flash ROM
2.Clear DATA
3.Flash Gapps Package
4.Boot into bootloader and flash the boot.img from your pc via fastboot with the command fastboot flash boot boot.img
5.Boot go through the setup and wait for the Play Store to update
Links:
ROM
Gapps
Boot.img
Credits for the boot.img go to summer.cat
Click to expand...
Click to collapse
Jaocagomez said:
post pictures, please!
Some people fixed the play store issue simply by changing the timezone of their android device, i think it was a CM branch bug.
Click to expand...
Click to collapse
If someone could test that and see if it actually works on this rom that would be amazing and I will post pictures asap.
Blade765 said:
So I can flash this through my safestrap recovery and run 4.4.4 on my Maxx that is rooted with WP Off?
I'm just trying to make sure that Im not reading this wrong, thats all.
Thanks for all of your hard work!
Click to expand...
Click to collapse
Please do not quote the the op. But yes. You can also always go back to the old 19.5.3 4.4 rom. But dont forget to flash the boot.img provided in the op post. Lastly you will still have wp off. But for some od reason there are a lot of google play issues with this rom. Ive redone all of my work 2 times and it still ends up with the same issues.
If you want to stay rooted with wp off stay on 4.4 but you can still flash this. So basically no you cant get root on 4.4.4 ota to my knowledge. Yet.
Works on the MINI
Just wanted to say THANK YOU!
This worked on my DROID MINI (was on 4.4 Rooted WP Off/ SafeStrapped)
Hello guys, I'm Leonardo and I'm new on XDA. I own this device since July 2016, and throughout 1 year and a half I tried a lot of roms. I've seen a few roms based on Oreo and I'd like to try them, but every time i flash one of those roms, the device bootloops. I think the cause might be the Cofface TWRP I have installed on the but I haven't found a guide on how to switch from a recovery to another. Can you please link me a guide or, if someone already switched recovery, tell me the way to do that?
Thanks in advance
Leo
Just select install from twrp menu select image and choose the file of recovery then select the recovery partition
leoalbore said:
Hello guys, I'm Leonardo and I'm new on XDA. I own this device since July 2016, and throughout 1 year and a half I tried a lot of roms. I've seen a few roms based on Oreo and I'd like to try them, but every time i flash one of those roms, the device bootloops. I think the cause might be the Cofface TWRP I have installed on the but I haven't found a guide on how to switch from a recovery to another. Can you please link me a guide or, if someone already switched recovery, tell me the way to do that?
Thanks in advance
Leo
Click to expand...
Click to collapse
download Redworlf recovery (check if you have 2GB or 3GB variant) Select install from twrp menu select image and choose the file of recovery, then select the recovery partition and swipe bar.
I don't suggest using Red Wolf recovery since it is closed source and the code hasn't been properly audited, the same goes for ZCX, comes from some unknown china user (but so far it has been safe), it's up to you if you want to risk your phone and/or data, you have to ask why they are hiding the source code and for what reason, it could just be they are bad coders and don't want people to see messy code....who knows.
anyways I suggest using the official twrp, you might have to use the lazyflasher thing but at least you know you are getting a safe recovery and its great our device is getting official twrps we really don't need to use hacked ones.
if you want to use the OTA update feature I suggest just sticking with ZCX, or if you need access to additional partitions.
[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
{
"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"
}
YOUR WARRANTY WILL BE VOID
I AM NOT responsible for anything that may happen to your phone while attempting to follow this guide.
You are doing so at your own risk, and you take full responsibility for your decisions and actions.
You are not to blame me or XDA, or any of it's respected developers.
Anyways, now that that is out of the way. Those of us who have been in the Axon 7 forums know that information is quite scattered about. So it can be difficult for any newcomers to find everything they need before making any leaps or dives with their device. This guide’s purpose is to centralize the quickest and easiest steps to follow in order to get Treblized and to get on a stable Pie GSI build that can be used as a home base before experimenting further with other ROMs and/or GSIs.
Even if you are not satisfied with the Havoc Pie GSI, your device will still be in an optimal state to try the latest Oreo 8.1 ROMs, such as LOS 15.1 or DotOS 2.5, or to try any of the other Pie GSIs in the Treble forums.
Things you will sacrifice:
No VOLTE
No Encryption
No Dolby
No Daydream
No AK4490 DAC (will default to AK4491)
Camera Flash out of sync (Use OpenCamera for flash shots)
Not able to set password for Hotspot (Open connection only)
Again, if you don't find using a Pie GSI worth these sacrifices after trying it out, you can easily move to an Oreo ROM like LOS 15.1 or DotOS 2.5, which have more functioning features.
----------------------------------------
DOWNLOAD
----------------------------------------
(NOTE: The below setup will be fluid as discussion in this thread finds more stability with newer vendor builds and newer HavocOS 2.0 GSI builds)
After completion of this guide, your device will be setup with the following (might as well download everything):
Oki's TWRP 3.2.3.0 Lab's Mod v1.3
B20 Bootstack by DrakenFX - Modified by Verequies (Splash or NoSplash)
Oreo Modem (U, G, or Chinese)
DotOS 2.5 boot.img (This also contains the DotOS vendor, if you wish to use it)
LOS 15.1 vendor (20181110) build
HavocOS 2.0 Pie GSI (20181027) build - NOTE: Most GSIs are provided compressed. You must extract the .img file from the downloaded file.
Your preferred GApps ( https://opengapps.org/ ) (ARM64, 9.0, Micro or below only)
Also download OrdenKrieger's TWRP 3.2.3.0, going to need it handy to flash the vendor img.
And the NFC_Hotspot Fix by Kountry83 (You will need this for almost every GSI you try)
----------------------------------------
FAQ
----------------------------------------
WHATS UP WITH THE BOOTSTACKS?
The bootstacks that are currently available for the Axon are somewhat of a mess, if not careful, you can easily brick your device.
For Pie GSI setups, I recommend the B20 bootstack by DrakenFX that has been modified by Verequies, Splash version.
Verequies has asked that I also link the NoSplash version in case some users have issues with the Splash version, but many testers have had no problems with the Splash version on this setup.
Unlike the DrakenFX B20 bootstack, these modified versions do not flash the modem, so there is no need to flash modem again when switching between them. Sometimes will need to Unlock Password in TWRP when switching though, it will say not recognized.
Splash
Ability to have Read/Write access in system.
Nice three logo splash screen, replacing bootloader warning screen.
No bootloader warning screen means not able hit volume button during boot to get menu for Recovery, Fastboot, etc.
Which also means you will have to use power button + volume up combo to enter Recovery, or reboot to recovery from the ROM.
No EDL three button combo.
Can't charge without booting system or TWRP.
NoSplash
Read Only access in system. (Which will break Magisk)
Ugly bootloader warning screen.
Able hit volume button during boot to get menu for Recovery, Fastboot, etc.
Able to use EDL three button combo.
Allows offline charging without booting into system.
WHY EDL?
Starting out with Oki’s LOS 15.1 EDL package just makes it easier for everyone. It’s easier for you because there will be less steps needed to get treblized, which will also mean less room for error. It’s easier for me because it makes for a much shorter guide, and it’s easier to find answers to issues if we all started on the same page. However, if there are enough requests, I’ll make a longer guide without the use of EDL.
If you are already treblized you won’t necessarily need to EDL (in most cases), but if you run into issues please don’t comment until you’ve tried starting with first step.
----------------------------------------
GUIDE
----------------------------------------
STEP 1:
Please follow Oki’s Easy Guide to EDL LOS15.1
IT IS IMPORTANT TO FOLLOW EVERY STEP
Try not to boot into system while going through the steps if possible, but it’s ok if you do.
You can use @djkuz Axon 7 EDL Tool, instead of MiFlash, if you are more familiar with that.
Also, in step 12, it states to format to F2FS, but I recommend to format to EXT4 for the best compatibility with GSIs. As a precaution, to make sure your partitions will read correctly, format the partitions to F2FS per the instructions, then format them back to EXT4.
You can always test if F2FS works for you later.
Thank you @Oki for this wonderful starting point for new Treble users.
CONGRATULATIONS - You are now TREBLIZED and should never have to do Step 1 again.
STEP 2:
Once done with Oki’s guide, stay in TWRP
Wipe Dalvik, Cache, Vendor, System and Data.
Flash the bootstack you chose.
Flash the appropriate modem for your variant.
CONGRATULATIONS - You should never have to flash those again, unless changing bootstack for whatever reason.
STEP 3:
In TWRP make sure System and Vendor partitions are mounted.
Flash the DotOS Vendor flashable.
(It doesn’t have DotOS in the file name, so it should be named something like “Vendor_Flashable_GSI…”)
In TWRP go to Install and in the bottom right select Install Image
Now we flash the Havoc GSI image you extracted, selecting the System partition.
DO NOT BOOT TO SYSTEM - We need to use OrdenKrieger’s TWRP 3.2.3.0 to flash the LOS 15.1 vendor.img
(If you wish to use the DotOS vendor, you can skip to Step 5. You will still need to reboot to Recovery, so don't skip that.)
STEP 4:
Flash TWRP 3.2.3.0 to Recovery partition and then reboot to Recovery
You should now be in TWRP 3.2.3.0
Flash the LOS 15.1 vendor.img to the Vendor partition
DO NOT BOOT TO SYSTEM - We need to restore Oki’s TWRP and flash GApps.
STEP 5:
Flash Oki’s TWRP 3.2.3.0 Lab’s Mod to Recovery partition and then reboot to Recovery
You should now be in Oki’s TWRP 3.2.3.0 Lab’s Mod
Flash GApps
Make sure System and Vendor are mounted
Flash the NFC_Hotspot Fix
NOW BOOT SYSTEM
I will wait here while you setup your device.
DONE? GOOD. Lets set up Magisk and pass SafetyNet
STEP 5:
At this time I recommend Magisk 17.2
Find it, download it, and flash it in TWRP
Once booted, in Magisk search for the module “MagiskHide Props Config” and install it.
Then search for BusyBox module by Osmosis and install it.
Reboot
Using a terminal app (not in TWRP) like Termux, type “su”
Grant root privileges
Then type “props”
You should be greeted with a menu
Select 1 to Edit fingerprint
Select F to Pick a Certified fingerprint
Then follow the menu to select ZTE and Axon 7
Then yes and yes to reboot.
Everything should be good to go now. ENJOY!!
To add just a few more options to your setup without overdoing it with a heavy launcher, I highly recommend:
Lean Launcher Optimized
I will surely be adding to this guide and modifying it as the situation evolves. So feel free to give me any input on how to improve it.
----------------------------------------
THANKS
----------------------------------------
Thanks to @raystef66 and all of the testers in the [SUMMARY][PIE] BEST PIE ROMS to TRY thread, as well everyone in the "Axon7 (s)GSI trebleSHOOT" Telegram group, for testing, "trebleSHOOTing" and reporting your findings.
Thanks to @Oki again for his easy guide and LOS 15.1 EDL package.
Thanks to @Unjustified Dev for uploading separate vendors for us GSI users, and for all of the work he's done on LOS and his help in the LOS threads.
Thanks to @Verequies for creating the two modified versions of @DrakenFX 's B20 bootstacks, and of course @DrakenFX for his B20 and B12 bootstacks.
Thanks to @SaintZ93 for his work on DotOS and for providing a flashable for boot and vendor only.
Thanks to @SaintZ93 and @Skrem339 for their great work on the Schwifty kernel.
And thanks to @hundeva for his work on Lean Launcher.
----------------------------------------
GUIDE EDIT LOG
----------------------------------------
11/22 - Updated that it is optional to stay with DotOS vendor and skip a step.
11/30 - Changed Step 1 to recommend EXT4 for best compatibility. Also to format from EXT4 to F2FS, then back to EXT4, to avoid internal storage error some are getting.
12/10 - Props Config module now requires BusyBox module, updated Step 5.
Thanks for the guide!
On step 4, The vendor partition doesn't show up on orden's twrp. You probably already know you can't flash with Okis twrp. Skipped this step and it booted anyway.
Don't beat me up about this but for those of us with the 50% battery bug, it happens with this method.
JKSurf said:
Thanks for the guide!
On step 4, The vendor partition doesn't show up on orden's twrp. You probably already know you can't flash with Okis twrp. Skipped this step and it booted anyway.
Don't beat me up about this but for those of us with the 50% battery bug, it happens with this method.
Click to expand...
Click to collapse
Please make sure you redownload Ordens TWRP. There are two of them with the same name out there. The one I linked should allow you to see Vendor partition. I should list this step as optional, as the DotOS vendor works, Ive just found the LOS vendor to show improvement personally. I also wanted to teach how to flash vendor.img, as there is only one way atm, using Ordens TWRP.
The vendor setup in this guide is all based off LOS sources, so any issues LOS is having that are vendor related will carry over to this setup. Sorry.
Really nice guide, sadly I just flashed but one thing that I like is that you try to explain why you choose what you choose and I would really like if you could elaborate more on that for example why DotOS boot image and kernel or why LOS 15.1 vendor.
And also is there a way for me (or anyone on havoc), already on havoc but got there differently, to painlessly migrate to your setup?
I am using this gsi for a week and I like it a lot. It has better battery life than LOS 16 right now and you can customise so much.
And btw for me daydream works normally and I installed the ported pixel camera with night sight, which seems to work normal, too.
Mousman said:
Really nice guide, sadly I just flashed but one thing that I like is that you try to explain why you choose what you choose and I would really like if you could elaborate more on that for example why DotOS boot image and kernel or why LOS 15.1 vendor.
And also is there a way for me (or anyone on havoc), already on havoc but got there differently, to painlessly migrate to your setup?
Click to expand...
Click to collapse
I found minor things to work better with the LOS vendor, such as GPS locking and Bluetooth not freezing display data in my car. Of course this can vary from user to user. And my preference changes as well when I find improvements with other vendors.
The DotOS vendor flashable is provided as it's the easiest way to get an up to date vendor. Otherwise you would have to download and flash an entire ROM, or extract the boot.img from that ROM, or modify the install script. Unjustified didn't provide the LOS vendor in combo with the boot.img, so the DotOS flashable is the best option as of now.
If you're already on the Havoc GSI, then you can just flash the bootstack, wipe vendor, flash DotOS vendor flashable, flash LOS vendor.img if you want (using Ordens TWRP), flash Magisk. Then boot.
It will feel like a dirty flash, but it's not, thanks to Treble.
Please do a full backup before doing so, as I think if your vendor partition was created differently, pulled from data, it might not work.
Kleva94 said:
I am using this gsi for a week and I like it a lot. It has better battery life than LOS 16 right now and you can customise so much.
And btw for me daydream works normally and I installed the ported pixel camera with night sight, which seems to work normal, too.
Click to expand...
Click to collapse
I don't use Daydream, I only know what was reported by others. If more people want to test and report that it's working, I'll gladly remove it from the sacrifices.
EBeatFLA said:
I don't use Daydream, I only know what was reported by others. If more people want to test and report that it's working, I'll gladly remove it from the sacrifices.
Click to expand...
Click to collapse
Re. sacrificing encryption, I thought LOS 15.1 vendor supports it. Is that not enough?
In other words, do you need vendor + system + rom for encryption to work? Or just system + rom? Or...?
Thx for all your work.
piet8stevens said:
Re. sacrificing encryption, I thought LOS 15.1 vendor supports it. Is that not enough?
In other words, do you need vendor + system + rom for encryption to work? Or just system + rom? Or...?
Thx for all your work.
Click to expand...
Click to collapse
This particular setup will sacrifice encryption. Getting encryption on a GSI would be another path. The TWRP and bootstack options we have for our device play a part in why I find encryption to be a mess right now, and chose to move forward without it.
I'm kinda having issues flashing LOS 15.1 vendor.img. I flashed Ordens TWRP, the one you provided but I do not get an option to flash to vendor partition when I choose to flash that LOS 15.1 vendor.img
g0dzstar said:
I'm kinda having issues flashing LOS 15.1 vendor.img. I flashed Ordens TWRP, the one you provided but I do not get an option to flash to vendor partition when I choose to flash that LOS 15.1 vendor.img
Click to expand...
Click to collapse
JKSurf said:
Thanks for the guide!
On step 4, The vendor partition doesn't show up on orden's twrp. You probably already know you can't flash with Okis twrp. Skipped this step and it booted anyway.
Don't beat me up about this but for those of us with the 50% battery bug, it happens with this method.
Click to expand...
Click to collapse
OMG guys, so sorry, was linking to the wrong TWRP. Link updated. It's not on AFH, so if you don't trust it's a legit link and want to check, it's the same link in the LOS16 op.
Thanks for testing.
Did everything from guide, but it seems like i don't have access to internal storage in havoc os and still accesible in twrp. Any suggestion what i did wrong?
Reakleases said:
Did everything from guide, but it seems like i don't have access to internal storage in havoc os and still accesible in twrp. Any suggestion what i did wrong?
Click to expand...
Click to collapse
Make sure to follow all of the steps in Oki's guide. Also, if you used the NoSplash bootstack, that might be it. But I'm pretty sure it's a missed step in his guide.
did everything again without success, but something of that helped, tried chmod 755 on root directory and fix contexts.
Really nice guide, thanks!
Having an issue flashing the DotOS vendor file. Getting the error 7. Edited the file with Notepadd ++ and took out the assert line and deleted the empty line. Resaved and recompressed zip and tried to flash and still getting the error. Followed all the steps to this point no issues.
juniorD said:
Having an issue flashing the DotOS vendor file. Getting the error 7. Edited the file with Notepadd ++ and took out the assert line and deleted the empty line. Resaved and recompressed zip and tried to flash and still getting the error. Followed all the steps to this point no issues.
Click to expand...
Click to collapse
Make sure system and vendor are mounted before flashing.
juniorD said:
Having an issue flashing the DotOS vendor file. Getting the error 7. Edited the file with Notepadd ++ and took out the assert line and deleted the empty line. Resaved and recompressed zip and tried to flash and still getting the error. Followed all the steps to this point no issues.
Click to expand...
Click to collapse
Wrong bootstack,flash bootstack again!
Also i read in previous post,people are not wiping correctly the system with clean flash
Predatorhaze said:
Wrong bootstack,flash bootstack again!
Also i read in previous post,people are not wiping correctly the system with clean flash
Click to expand...
Click to collapse
Thanks for the reply.
I flashed the bootstack in the EDL package uploaded in the guide using MiFlash went through fine. Also did a clean wipe of everything and formatted my Internal Storage before I flashed the package.
---------- Post added at 07:51 AM ---------- Previous post was at 07:50 AM ----------
EBeatFLA said:
Make sure system and vendor are mounted before flashing.
Click to expand...
Click to collapse
Yup did that and checked a second time to make sure I did. They were mounted.
---------- Post added at 07:52 AM ---------- Previous post was at 07:51 AM ----------
EBeatFLA said:
Make sure system and vendor are mounted before flashing.
Click to expand...
Click to collapse
Yup did that and checked a second time to make sure I did. They were mounted.
Since i am newbie to this forum and all this rooting stuff, i am lately confused about lot of stuff about poco f1 in respect of flashing new rom over miui rom and also over some other custom rom plus back up/restore of existing rom.
I faced lot of problems of encryption and decryption and had to format my phone number of times. I am listing out few procedure for installing new rom over other customer rom and miui rom which i learned from this wonderful forum plus also the procedure of backing up your existing rom. So request all the experience developers to guide newbie like us step wise so we can also enjoy the fruitful advantage of this lovely forum.
for installing new rom i learned from this link https://forum.xda-developers.com/poco-f1/help/to-custom-rom-want-to-install-rom-t3902913 to follow the below mentioned procedure. I also posted my respective questions along with this step for answer from my beloved developers.
1. Remove pattern and pin. If you don't do this step then you will have to factory reset your phone with stock MIUI. (Is it compulsory to remove pattern and pin, what if we remove lock screen password by simply deleting these files from twrp
1.gatekeeper password key
2.gatekeeper pattern key
3.locksettings.db
4.locksettings.db-shm
5.locksettings.db-wal
will there be a problem)
2. Wipe all except internal storage and external storage.(this is understood)
3. Flash vendor and rom.(do i really need to flash vendor before flashing rom and this is applicable to all the custom roms i mean if i have pixel rom and want to install nytrogen rom, do i need to flash vendor all the time....plus where can i get this vendor file, can anyone provide a link for that)
4. Flash disableforceencryption with magisk 18.0.(this is very important to me, what is disableforceencryption file do,do i need to flash every time whenever i try to flash new custom rom)
5. Flash your twrp again so it isn't replaced by stock.(i still did not understand this part but still which twrp to flash official one or unofficial one, since official one gave me lot of trouble so i had to revert back to unofficial one, kindly provide your input in this)
Further for backing up your existing rom following steps have been learned from some different thread, kindly provide your input whether the same is right or wrong.
System image
Vendor image
Boot
Data
Modem
Efs
Please co-operate on this because lot of newbie like me facing different problem, your valuable input can bring smile on our faces.
Thanks in advance.
mandyady said:
Since i am newbie to this forum and all this rooting stuff, i am lately confused about lot of stuff about poco f1 in respect of flashing new rom over miui rom and also over some other custom rom plus back up/restore of existing rom.
I faced lot of problems of encryption and decryption and had to format my phone number of times. I am listing out few procedure for installing new rom over other customer rom and miui rom which i learned from this wonderful forum plus also the procedure of backing up your existing rom. So request all the experience developers to guide newbie like us step wise so we can also enjoy the fruitful advantage of this lovely forum.
for installing new rom i learned from this link https://forum.xda-developers.com/poco-f1/help/to-custom-rom-want-to-install-rom-t3902913 to follow the below mentioned procedure. I also posted my respective questions along with this step for answer from my beloved developers.
1. Remove pattern and pin. If you don't do this step then you will have to factory reset your phone with stock MIUI. (Is it compulsory to remove pattern and pin, what if we remove lock screen password by simply deleting these files from twrp
1.gatekeeper password key
2.gatekeeper pattern key
3.locksettings.db
4.locksettings.db-shm
5.locksettings.db-wal
will there be a problem)
2. Wipe all except internal storage and external storage.(this is understood)
3. Flash vendor and rom.(do i really need to flash vendor before flashing rom and this is applicable to all the custom roms i mean if i have pixel rom and want to install nytrogen rom, do i need to flash vendor all the time....plus where can i get this vendor file, can anyone provide a link for that)
4. Flash disableforceencryption with magisk 18.0.(this is very important to me, what is disableforceencryption file do,do i need to flash every time whenever i try to flash new custom rom)
5. Flash your twrp again so it isn't replaced by stock.(i still did not understand this part but still which twrp to flash official one or unofficial one, since official one gave me lot of trouble so i had to revert back to unofficial one, kindly provide your input in this)
Further for backing up your existing rom following steps have been learned from some different thread, kindly provide your input whether the same is right or wrong.
System image
Vendor image
Boot
Data
Modem
Efs
Please co-operate on this because lot of newbie like me facing different problem, your valuable input can bring smile on our faces.
Thanks in advance.
Click to expand...
Click to collapse
1. Yes, if you are able to find all the files related to locks, then you can delete them and boot. But it is much easier to remove the locks before flashing the new ROM.
3. Vendor firmware has to be flashed if you wipe. Also when some custom ROM specifically asks for a particular version of vendor firmware. The vendor firmware can be found on the download page of Xiaomi.
4. When the OEM ROM is flashed, it will encrypt your phone. Custom ROMs require unencrypted phone (some of them don't). But the TWRP now handles encryption/decryption and so, in my opinion, you don't need DFE zip at all if you have the correct TWRP (you already seem to have it).
5. If you are flashing OEM ROM, the built in recovery will overwrite the TWRP. To avoid this, you can flash Magisk immediately after flashing the ROM, before booting. It will preserve TWRP. No need for re-flashing TWRP if you are flashing custom ROM since they do not have in-built recovery. Further, I understand that the unofficial TWRP handles encryption/decryption better. So stick with it unless you have problems with it.
If you backup all the partitions, you can choose which ones to restore, the downside being that a lot of space will be required. But it is safer.
Hope you are smiling!