[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
Related
As we(in the TG group) have tested a bunch of Pie9.0 (s)GSI Roms on the XDA forum (https://forum.xda-developers.com/project-treble/trebleenabled-device-development) I was asked to make a guide/summary of what there was already been tested and in our opinion the better ones out of the Pie-list.
It’s not to be intented to be ‘the’list but only to give you a guidance to what there is at the moment. And most of, it’s very easy to install
The ones that I will list are the ones WITHOUT call bugs on our Axon 7. As you wish you can vote for your favorite of the listed ones above.
Note : the LOS16 PPR2 is not the same as the one under ROM section (Ordenkrieger)
LIST AVAILABLE : (not in a specific order and more to come)
1. HavocOS : based on https://forum.xda-developers.com/pr...-device-development/rom-havoc-os-8-1-t3819050
Latest stable : https://sourceforge.net/projects/havoc-os/files/arm64aonly/
2. BenzoROM : based on https://forum.xda-developers.com/pr...device-development/gsi-benzo-rom-9-0-t3837127
Latest stable : https://forum.xda-developers.com/showpost.php?p=78312149&postcount=284
3. PixelExperience : based on https://forum.xda-developers.com/pr...ce-development/9-0-pixelexperience-p-t3833294
Latest stable : https://github.com/EnesSastim/Downloads/releases/tag/PE-A-2018-09-05
4. LOS16.0 PPR2 : based on https://forum.xda-developers.com/pr...vice-development/9-0-lineage-os-16-0-t3840801
Latest stable : https://mega.nz/#F!3XwFlAaC!VdzCKlrR-f6D-a8oEz9JkQ!DD4z0AhA . More info.
5. ArrowOS : based on https://forum.xda-developers.com/pr...abled-device-development/gsi-arrowos-t3835111
Latest stable : https://sourceforge.net/projects/arrow-os/files/arrow-9.x/GSI/7_sep_2018/
6. DescendantOS : https://forum.xda-developers.com/pr...escendant-android-pie-custom-rom-ver-t3840578
7. PixelDust : https://forum.xda-developers.com/showpost.php?p=78184921&postcount=212
8. AEX 6.0 OFFICIAL : https://forum.xda-developers.com/showpost.php?p=78245997&postcount=254
Pre Requisitions :
Unlocked BL, Bootstack B12 NFound or your preferred one
Vendor partition by @djkuz or your preferred one
TWRP3218-treble under the hood @NFound or your preferred one
Installation : or your own preferred method as this is just an example
Wipe System. Data, Vendor, cache dalvik (although data does the job)
Flash the v1.1 NFound
Flash the .img that you have extracted and if needed renamed to system.img
And just….reboot
After installation there can be applied some fixes :
a* Use the aroma COMBIFIX v3.1 to fix the NFC/HS general lag, choose button reverse, flash new kran framework overlay, magisk and gapps
update : for magisk 18.1 use the latest Combifix v5.1 or with Magisk 19.0 you can use Combifix v6.0 or the latest one with magisk 19.1 and latest MHPC : COMBIFIX 6.1
a. NFC when laggy or not working combined with Hotspot : Pie_NFC /Hotspot fix by @kountry83
On ArrowOS and Benzo they both work after applying the fix although the Hotspot works on ArrowOS and Benzo die to v105 phh
b. GCAM when default one isn’t working
c. Camera fix if you have a settings bug
d. Reverse BACK/RECENT (mount system / vendor) or A2017X_softkey_reverse_module
e. System settings color accents
f. DarkMode & SettingsColorAccents thnx @kountry83
g. safetynet issues
Misc :
* A2017X-MoKee_vendor_boot_combo
* AEX bootanimation
* Havoc bootanimation
* There is no need to an incall fix as all of the listed are free of the bug.
* Also no problems with SD card or booting the roms.
* In some cases the package provided by the dev is GAPPS included. If no gapps provided you can simply flash the OFFICIAL GAPPS.
* All roms have NFC working. Hotspot isn’t reliable and mostly not working.
* Some Pie Roms do have more customization as to the other. Up to you to vote which one you do prefer. When voting it would be good when you make your vote based on ‘most stable/most customs/best battery life’
* Substratum works (tested on Benzo and NOS...)
I’m not going get into detail about each rom. I’ll leave that up to you to discuss further on. Perhaps if voting leads us to a one of a kind, we can focus on that in the future.
It would be much appreciated as you add your input even with your fixes or additions you want to point out.
This is something that is growing on XDA and all the input is welcome to improve what we have.
ENJOY !
@Oki, thnx for your guidance on flashing back and forth between (treble) roms
Credits to all mentioned in the thread and to all members for testing and improving it on TG !
Feel free to join us too on Axon7-trebleshoot
-----
Havoc P seems to be a good option. Im voting for havoc.
nays_pl said:
Havoc P seems to be a good option. Im voting for havoc.
Click to expand...
Click to collapse
A good one. As for me the Benzo, Los16PPR2 and Havoc are the best to this point.
Especially smoothness, battery life and customization are more then ok atm.
Updates will follow and improve things where needed.
Thanks @raystef66 ! Took some time away from flashing and was a bit lost of where to go on my axon after moving to aex5.8 and how to do. Good that you also have the instructions
Was on benzo for a week or so...was pretty stable but the battery life wasnt that great even with the schwifty kernel. It lacked some of the customizations that i use so i am back at AEX 5.8...pretty sure these gsi will become more stable over time...will be worth the wait
Axebladewarrior said:
Was on benzo for a week or so...was pretty stable but the battery life wasnt that great even with the schwifty kernel. It lacked some of the customizations that i use so i am back at AEX 5.8...pretty sure these gsi will become more stable over time...will be worth the wait
Click to expand...
Click to collapse
Thnx for the input !
True, as for me too, the AEX Oreo has a bunch of customs that Benzo still hasnt. But out of all GSI's Benzo and a couple others have the most.
Even on some Pie GSI's the displayed features aren't even working.
Batterylife as on NOS gave me 4-5 SOT on average use.
Anyway, like you said, still building up....
raystef66 said:
@Oki, if you want to guide the users on your method to flash a (s)GSI from scratch with your PartyTool, be our guest
Click to expand...
Click to collapse
Sure! more people testing means more options explored and better outcome for everyone. You are doing a great job testing and bringing Android 9 ROMs to the Axon 7 scene. I have been very busy the last couple of weekends preparing my version of the TWRP for the Axon 7, the TWRP 2.3.2-0L Labs Mod. It has been for me the key for fast switching between the testing environment and the daily driver configuration in a matter of minutes and without requiring a computer at all. It can backup/restore internal storage, create and remove the vendor partition and even create firmware zip packages able to be flashed using TWRP or MiFlash. I'll create the guide this afternoon on how to switch back and forth from Nougat or Oreo to Pie.
Cheers!
Oki said:
Sure! more people testing means more options explored and better outcome for everyone. You are doing a great job testing and bringing Android 9 ROMs to the Axon 7 scene. I have been very busy the last couple of weekends preparing my version of the TWRP for the Axon 7, the TWRP 2.3.2-0L Labs Mod. It has been for me the key for fast switching between the testing environment and the daily driver configuration in a matter of minutes and without requiring a computer at all. It can backup/restore internal storage, create and remove the vendor partition and even create firmware zip packages able to be flashed using TWRP or MiFlash. I'll create the guide this afternoon on how to switch back and forth from Nougat or Oreo to Pie.
Cheers!
Click to expand...
Click to collapse
Awesome :highfive:
Oki said:
Sure! more people testing means more options explored and better outcome for everyone. You are doing a great job testing and bringing Android 9 ROMs to the Axon 7 scene. I have been very busy the last couple of weekends preparing my version of the TWRP for the Axon 7, the TWRP 2.3.2-0L Labs Mod. It has been for me the key for fast switching between the testing environment and the daily driver configuration in a matter of minutes and without requiring a computer at all. It can backup/restore internal storage, create and remove the vendor partition and even create firmware zip packages able to be flashed using TWRP or MiFlash. I'll create the guide this afternoon on how to switch back and forth from Nougat or Oreo to Pie.
Cheers!
Click to expand...
Click to collapse
That would be great and much appreciated as you have followed your own guideline next to NFounds ! That's why I asked
I follow what you're trying to achieve and in fact I'm waiting to test the LabMods. Thnx !
As said, I come along with many people asking how to go back and forth between N,O and Pie. I know what to do in such occasions but many don't.
Because of your tools I'll leave the full guide on that up to you
Oki said:
Sure! more people testing means more options explored and better outcome for everyone. You are doing a great job testing and bringing Android 9 ROMs to the Axon 7 scene. I have been very busy the last couple of weekends preparing my version of the TWRP for the Axon 7, the TWRP 2.3.2-0L Labs Mod. It has been for me the key for fast switching between the testing environment and the daily driver configuration in a matter of minutes and without requiring a computer at all. It can backup/restore internal storage, create and remove the vendor partition and even create firmware zip packages able to be flashed using TWRP or MiFlash. I'll create the guide this afternoon on how to switch back and forth from Nougat or Oreo to Pie.
Cheers!
Click to expand...
Click to collapse
Thx. How about adb and encryption for TWRP2. 3.2-0L?
piet8stevens said:
Thx. How about adb and encryption for TWRP2. 3.2-0L?
Click to expand...
Click to collapse
Read his OP in the thread he linked.
piet8stevens said:
Thx. How about adb and encryption for TWRP2. 3.2-0L?
Click to expand...
Click to collapse
I have not developed new kernels but I have taken care of both situations. Just go to the TWRP Labs Mod thread, the info is in the OP and you can ask there too. This thread is all about the Pie implementations, Let's try to keep on topic as much as possible.
really hope MIUI 10 will be stable enough, miss MIUI
HOW TO...
Round Trip from NOUGAT or OREO to PIE GSI
OK, the full instructions to go from Nougat or Oreo to Pie, and back, would be:
Prerequisite
Bootloader Unlocked Axon 7
Install tools and configuration
1. Install TWRP Labs Mod Custom Recovery. Use the B12 version in case you are currently using Oreo encryption. Reboot to recovery.
2. Open the PARTY tool under Advanced > Oki Labs. If you do not have vendor partition you need to create one. Use the default configuration (System, 512MiB, at the end). Accept to reboot recovery. If the vendor partition is there, then just leave PARTY tool and continue with the next step.
Backup your daily driver config:
3. Go to the EDL Backup tool under Advanced > Oki Labs and create the Backup zip choosing FULL. If something goes wrong you will be able to restore your device using TWRP or MiFlash
4. From the Main Menu, backup your Data partition to the External SD.
5. Backup your Internal Storage using the option under Advanced > Oki Labs (Check the available space, the tool is not yet checking for available space, I will add it this weekend)
Prepare Treble configuration:
6. From TWRP Install the special B12 Bootloader with enabled EDL key combo support (The Universal Bootstack leads to DFU mode) and the modem for your region.
7. From the Main Menu, Wipe Vendor
8. Flash Axon 7 Treble ROM v1.1
Flash GSI package:
9. From the Main Menu, Wipe Dalvik / Cache / System / Data
10. From here you have to follow the installation instruction for the Generic System Image (GSI). Usually it is a single img file. So go to Install, press Install_Image button and navigate to the GSI file to flash it. Then just reboot. Some images would require additional ZIPs such as GApps or recommended patches.
Here you test the Pie ROM. If you want to test another Pie ROM you can try just going back to step 9. However, to ensure everything is clean you should start in step 7.
Return to your Daily Driver Config
11. Boot Recovery and flash the backup EDL ZIP you created in step 4. If you bricked your device just extract the contents of the file in your HD, Boot your phone into EDL mode, and use MiFlash. This step restore your original bootstack, modem and OS.
12. From main menu restore your Data partition
13. Go to Advanced > Oki Labs and restore Storage.
14. If you had to create the vendor partition in step 2, just run the PARTY tool again to remove the vendor partition.
15. From the Main Menu, Wipe Dalvik / Cache and reboot to system.
New Builds :A-only !
Pixel Experience seems default camera is working now
ArrowOS
Misc
Magisk Camera Module (MI A2 stock camera for Pie) - tested and works very good. Even flash is synchronised as well.
@Oki, I'm having an issue flashing your B12 bootloader. When I flash I get an error saying the zip is corrupt. I've tried downloading 3 times, and flashed from both internal and external storage. Any suggestions?
raystef66 said:
New Builds :A-only !
Pixel Experience seems default camera is working now
ArrowOS
Click to expand...
Click to collapse
How about hotspot? Is it working now?
privatedoodle said:
@Oki, I'm having an issue flashing your B12 bootloader. When I flash I get an error saying the zip is corrupt. I've tried downloading 3 times, and flashed from both internal and external storage. Any suggestions?
Click to expand...
Click to collapse
I have experienced some problems with AFH server. I have deleted the other version and uploaded it again here.
Oki said:
I have experienced some problems with AFH server. I have deleted the other version and uploaded it again here.
Click to expand...
Click to collapse
This new version works. Thanks!
WARNING: You'll most probably loose ALL your data, and might break your phone. Please use with extreme caution!
The goal of this ROM is to experience ColorOS 6.0 on any non-oppo and non-realme phone.
For a list of treble supported devices, consult and fill https://github.com/phhusson/treble_experimentations/wiki
How to flash:
1- Flash a treble pie rom (CAF vendor recommended.)
2- Extract 7z file and flash system.img
3- If base rom isn't permissive flash permissiver.
4- Reboot
Bugs:
- Fingerprint
- Since it's oem port maybe more on your device. But common bug is Fingerprint.
Download:
system.img for A-A/B ARM64 devices
Telegram Account: MacTavishAO In case of any problem please send me logs.
Thanks to: @erfanoabdi for everything..
Reserved. You can follow me on github.
Changelog:
1.0: Initial release.
Does it include stock sounds and ringtones? Thanks
ZoiraP said:
Does it include stock sounds and ringtones? Thanks
Click to expand...
Click to collapse
yes
Nice work.
Keep it up.
After reebot after flashing system, back to recovery. Any solution? Device Nubia Z17 (NX563J)
surfer30 said:
After reebot after flashing system, back to recovery. Any solution? Device Nubia Z17 (NX563J)
Click to expand...
Click to collapse
You need pie treble vendor, permissiver.
I flashed over Lineage 16GSI (android 9). But not flashed permissiver - you sugested tryed once more?
Kanka Lenovo Z5 direk crash diag bölümüne atıyor dediklerini harfiyen yaptığım halde.
Lenovo Z5(L78011) didnt work.
Stuck on boot logo. My Vendor is CAF and flashed permissiver V2
Couldn't flash in nokia 6.1 plus
Image file size larger than target device eror in twrp ..
Plz solve my problem..:crying:
Either bootloops or doesn't get past the boot image on Note9 N960F no matter what. (Different kernels, flash on different systems etc.)
rahul387 said:
Image file size larger than target device eror in twrp ..
Plz solve my problem..:crying:
Click to expand...
Click to collapse
That isnt how it works
Some random said:
That isnt how it works
Click to expand...
Click to collapse
When i flash color os in my nokia 6.1 plus .. its showing me that the image file is bigger than target device!!
Any solution for me ..?
I have 2 questions :
1) Can I flash this ROM on Mi Max 2 with Orange Fox 10 recovery?
2) Can this be used for daily life usage?
Thank you
No boot
System partition smaller than image
rahul387 said:
When i flash color os in my nokia 6.1 plus .. its showing me that the image file is bigger than target device!!
Any solution for me ..?
Click to expand...
Click to collapse
I read that we have to resize the system partition when that error occurs. It's too advanced for me so I left it.
Kicked into fastboot
I've tried installing it exactly as described here and also how it's described for other pie GSIs for oneplus5t but I only get kicked into the fastboot mode. I really like to try out this rom on an amoled display. Any specific methods I should follow? (I used mokee phh treble vendor as that was recommended in most forums, am also decrypted..maybe i have to try by flashing noverity too) all gsi tutorials and pages for oneplus 5t are about a year old so i'm not sure I can follow that and succeed. Any help would be appreciated. Thanks.
I cant install in redmi 6a
Galaxy A3 2017? (a3y17lte)
I have discovered a thread of the project treble port, how to fix stuck on boot screen?
Team Win Recovery Project 3.x, or TWRP3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
I’d recommend to read everything in this post, if you care about your phone.
If you already unlocked your bootloader, start with step 3.
First you need to unlock your bootloader. You can do so by enabling developer settings first, enable oem unlocking, then shut down your phone, hold volume up and down at the same time and while holding them plugin your charger. Your phone now should show a green screen with instructions to unlock the bootloader. Just follow them and after the unlocking your data should get wiped. After that your device will boot up and land in setup screen. Do not setup anything, just skip as much as possible, because your phone will get wiped again. Enable developer settings and make sure oem unlocking is greyed out and enabled. (If it does not show up, connect to a network first!)
Flash Galaxy A20e TWRP.tar via Odin or heimdall
Reboot into TWRP AS SOON AS THE FLASHING PROCESS IS DONE because otherwise TWRP will get replaced with the stock Android recovery
If you want to flash a GSI, skip to step 7
Factory reset in TWRP and reboot to stock
Wipe everything in TWRP excluding SD Card / USB OTG
Put a GSI image file onto an SD Card, alongside GSI_Fix_boot.zip and Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
Flash the GSI image, flash Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip, flash GSI_Fix_boot.zip, wipe cache and reboot.
Enjoy
Current bugs
Encryption/Decryption on stock does not work, you cannot read the internal storage while using the stock firmware
ADB and USB connection / USB OTG does not work
Latest release: https://drive.google.com/file/d/1Nbrmn7BgA3BxA1bqnLXYMuCY4KjpR0Vn/view?usp=sharing
Social media
Twitter: https://twitter.com/xyn_dev
Telegram: https://t.me/xyn_dev
Reserved.
Wow finally... thx a lot for that
Xyn XDotnest said:
Reserved.
Click to expand...
Click to collapse
Great work
Can you now install GSIs
Make sure you backup boot, data, system before you start
physwizz said:
Great work
Can you now install GSIs
Make sure you backup boot, data, system before you start
Click to expand...
Click to collapse
Yep, GSIs work, I am currently using Descendant X on mine.
Xyn XDotnest said:
Yep, GSIs work, I am currently using Descendant X on mine.
Click to expand...
Click to collapse
Beautiful
I'm stuck at GSI (PixelExperience) installation. I've extracted the img file on sd card and the wizard is asking which partition should be used to flash image (boot,recovery,product image,system image,vendor image).
ZemoDroid said:
I'm stuck at GSI (PixelExperience) installation. I've extracted the img file on sd card and the wizard is asking which partition should be used to flash image (boot,recovery,product image,system image,vendor image).
Click to expand...
Click to collapse
System
A few Questions about the process
Xyn XDotnest said:
Team Win Recovery Project 3.x, or TWRP3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
I’d recommend to read everything in this post, if you care about your phone.
If you already unlocked your bootloader, start with step 3.
First you need to unlock your bootloader. You can do so by enabling developer settings first, enable oem unlocking, then shut down your phone, hold volume up and down at the same time and while holding them plugin your charger. Your phone now should show a green screen with instructions to unlock the bootloader. Just follow them and after the unlocking your data should get wiped. After that your device will boot up and land in setup screen. Do not setup anything, just skip as much as possible, because your phone will get wiped again. Enable developer settings and make sure oem unlocking is greyed out and enabled. (If it does not show up, connect to a network first!)
Flash Galaxy A20e TWRP.tar via Odin or heimdall
Reboot into TWRP AS SOON AS THE FLASHING PROCESS IS DONE because otherwise TWRP will get replaced with the stock Android recovery
If you want to flash a GSI, skip to step 7
Factory reset in TWRP and reboot to stock
Wipe everything in TWRP excluding SD Card / USB OTG
Put a GSI image file onto an SD Card, alongside GSI_Fix_boot.zip and Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
Flash the GSI image, flash Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip, flash GSI_Fix_boot.zip, wipe cache and reboot.
Enjoy
Current bugs
Encryption/Decryption on stock does not work, you cannot read the internal storage while using the stock firmware
ADB and USB connection / USB OTG does not work
Latest release: https://drive.google.com/file/d/1Nbrmn7BgA3BxA1bqnLXYMuCY4KjpR0Vn/view?usp=sharing
Social media
Twitter: https://twitter.com/xdotnest
Telegram: https://t.me/dotnest
Click to expand...
Click to collapse
,
Hey thanks for this, I´ve got a few questions about the process that might also help others.
Do you recommend this method of rooting still over the new method using Magisk?
Do we still need to wipe everything in TWRP after first boot? And what specifically steps should we take to wipe?
Can you recommend any specific GSI images that are known to boot on the A20e (A202F) because so far I've tried LineageOS 17.1 / AOSP system -quack-arm64-ab-gapps.img and system -quack-arm64-ab-vanilla.img / Crdroid and nothing gets past the loading icon.
Do we still need to flash Disable_Verity_ForceEncrypt and GSI_Fix_boot.zip if not installing a GSI ?
a few notes
for anyone else. It helps if you boot into the rom and install magisk manager via APK (recent version is fine) before installing it via TWRP. After I did that rooting worked properly.
Lost ADB for some reason though, might be unrelated.
I also think that the a20e (SM-a202f) is an A device and not an A/B partition device at least according to treble check app.
ADB and USB connection / USB OTG does not work
Click to expand...
Click to collapse
oh.....right. that stinks
moogle said:
,
Hey thanks for this, I´ve got a few questions about the process that might also help others.
Do you recommend this method of rooting still over the new method using Magisk?
Do we still need to wipe everything in TWRP after first boot? And what specifically steps should we take to wipe?
Can you recommend any specific GSI images that are known to boot on the A20e (A202F) because so far I've tried LineageOS 17.1 / AOSP system -quack-arm64-ab-gapps.img and system -quack-arm64-ab-vanilla.img / Crdroid and nothing gets past the loading icon.
Do we still need to flash Disable_Verity_ForceEncrypt and GSI_Fix_boot.zip if not installing a GSI ?
Click to expand...
Click to collapse
1. This method does use Magisk
The tar file contains boot.img patched with Magisk
It also contains recovery.img and vbmeta.img
2. The boot.img is from Android 10 firmware so you need to upgrade to Q first.
3 there is a step missing in the instructions
It should say
6. Reboot the A20e into TWRP and mount everything you can.
Click Wipe then Format Data (not just wipe) - don't restart
Flash Disable_Dm-Verity_ForceEncrypt
Reboot to recovery and wipe both caches
Reboot system .
Click to expand...
Click to collapse
You can then backup boot, data and system for stock.
You can then install GSIs
I'm having some major problems with sd cards not being recognized by google play store as external storage and whatsapp unable to download images. any idea what it might be?
moogle said:
I'm having some major problems with sd cards not being recognized by google play store as external storage and whatsapp unable to download images. any idea what it might be?
Click to expand...
Click to collapse
What OS are you running?
physwizz said:
What OS are you running?
Click to expand...
Click to collapse
Just the stock android 10, I didn't find a GSI that worked for me.
moogle said:
Just the stock android 10, I didn't find a GSI that worked for me.
Click to expand...
Click to collapse
try Crdroid
physwizz said:
try Crdroid
Click to expand...
Click to collapse
Already have, and LOS 17.1 and AOSP system-quack-arm64-ab-vanilla
all of them got stuck at boot icon for an hour. Thats why I went back to stock.
I'm more interested in why I cannot seem to install discord or firefox from the app store, or whatsapp cannot download images.
moogle said:
Already have, and LOS 17.1 and AOSP system-quack-arm64-ab-vanilla
all of them got stuck at boot icon for an hour. Thats why I went back to stock.
I'm more interested in why I cannot seem to install discord or firefox from the app store, or whatsapp cannot download images.
Click to expand...
Click to collapse
Go into magisk and hide any apps that misbehave
physwizz said:
Go into magisk and hide any apps that misbehave
Click to expand...
Click to collapse
Tried it, no change, there's no apps misbehaving, just strange sd storage card behaviour
Is the SM-A202F/DS supported by these methods, I noticed in some other threads it wasn't working back in March, that's the unit I have.
moogle said:
Tried it, no change, there's no apps misbehaving, just strange sd storage card behaviour
Is the SM-A202F/DS supported by these methods, I noticed in some other threads it wasn't working back in March, that's the unit I have.
Click to expand...
Click to collapse
There is a fix here
https://forum.xda-developers.com/showpost.php?p=80184282&postcount=2
physwizz said:
There is a fix here
https://forum.xda-developers.com/showpost.php?p=80184282&postcount=2
Click to expand...
Click to collapse
Which part are you referring to in that thread?
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
Hello, this is TWRP, for Oneplus 7/Pro/5G that supports Android 11
can be flashed to boot with working decryption on android 11 roms
bugs:
backup/restore is unreliable
Installation:
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3. after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
Updating to a newer build:
1. download new build to internal storage
2. go to Advanced > Install Recovery Ramdisk
4. select the new image
5. after that is done, if you were using a custom kernel, reflash it now
6. if you were using magisk, reflash it now
Send me a beer: Crypto(Preferred) | PayPal
Trees:
https://github.com/TeamWin/android_device_oneplus_guacamole
https://github.com/TeamWin/android_device_oneplus_sm8150-common
Telegram group: https://t.me/NSSFB
Download: https://twrp.me/oneplus/oneplus7pro.html
Unofficial 12 builds: https://www.pling.com/p/1835156/
Will there be an installer zip or just an .img?
bdwilk said:
Will there be an installer zip or just an .img?
Click to expand...
Click to collapse
Read the Installation instructions, there's a new experimental feature replacing the need for zips.
Nice, at least no more torturing my poor 7Pro with test images, haha.
Thanks.
And yes, the new feature is neat and works here pretty well.
Good job, @Nebrassy !
It says a11 ROMs can be decrypted is oos 11 also included in that ?
jaggillararla said:
It says a11 ROMs can be decrypted is oos 11 also included in that ?
Click to expand...
Click to collapse
Why don't you try it and give us feedback
@Nebrassy thank you . I am sure the entire Oneplus guys here appreciate it.
wartomato said:
Nice, at least no more torturing my poor 7Pro with test images, haha.
Thanks.
And yes, the new feature is neat and works here pretty well.
Good job, @Nebrassy !
Click to expand...
Click to collapse
Been using for awhile now it's awesome this will make things easier great job
jaggillararla said:
It says a11 ROMs can be decrypted is oos 11 also included in that ?
Click to expand...
Click to collapse
I'm using HavocOS 4.5 based on OOS 11 and managed to decrypt data partition just fine.
I can confirm it's working on OP7 with OB4 / Android 11.
Many thanks for the great job!
Uploaded new build with f2fs support
Toutatis_ said:
I'm using HavocOS 4.5 based on OOS 11 and managed to decrypt data partition just fine.
Click to expand...
Click to collapse
Did you need to wipe your phone? Recently installed Android 11 and I can't do nandroid backup and don't want to mess it again.
1 said:
Did you need to wipe your phone? Recently installed Android 11 and I can't do nandroid backup and don't want to mess it again.
Click to expand...
Click to collapse
No, I rebooted to bootloader mode, ran sudo fastboot boot filename.img and TWRP splash screen appeared, asking for password. I entered my password and that's it, data partition was decrypted. I finally rebooted to system.
@Nebrassy
Thanks for the great work btw. Appreciated.
This work with stock oos11 encrypted?
Can somebody elaborate this?
1. fastboot boot twrp.img (Which twrp is this? The one shared here?)
2. go to Advanced > Flash Current TWRP (What does current TWRP mean? Official TWRP? and where is that advanced? Advanced in new TWRP?)
1 said:
Can somebody elaborate this?
1. fastboot boot twrp.img (Which twrp is this? The one shared here?)
2. go to Advanced > Flash Current TWRP (What does current TWRP mean? Official TWRP? and where is that advanced? Advanced in new TWRP?)
Click to expand...
Click to collapse
Yes, run fastboot boot TWRP-3.5.1-guacamole-Nebrassy-2.img (this is the filename for the current latest version)
See my screenshot
Toutatis_ said:
Yes, run fastboot boot TWRP-3.5.1-guacamole-Nebrassy-2.img (this is the filename for the current latest version)
See my screenshot
Click to expand...
Click to collapse
Thanks a lot.
Can this be flashed within twrp if we're on the latest version from https://dl.twrp.me/guacamole/ ?
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
/*
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
Works:
1. Decryption(Support pattern/pin, tested on V12.5.6 and 21.9.27)
2. MTP/ADB
3. Fastbootd
4. ADB Sideload
5. Vibration
6. ...
Features:
1. Android 11 Support
2. Magisk-v23.0 included
2. Prevent from replacing TWRP with stock recovery
3. DTBO Patch
4. Support for flashing rom(>=4GB)
5. Enable /cache partition
Not working:
1. Tell me
Changelog:
1. Initial release
INSTALLATION:
1. Download the TWRP image file to your PC.
2. Put your device into fastboot.
3. Type the following command to flash the recovery:-
Code:
fastboot flash recovery twrp-3.5.2-cas-xayah.img
4. Reboot to recovery
Download:
TWRP
Donation:
PayPal: https://paypal.me/XayahSuSuSu
Telegram Group: https://t.me/joinchat/iSOZ2LngNXEzYzk9
Source Code:
Tree: https://github.com/XayahSuSuSu/twrp_device_xiaomi_cas
Great job
But i faced one issue when i try to make a backup
How can i solve it ?
EDIT: In TWRP, go in "Advanced" menu => "Terminal" => Type: rm /data/extm -Rf
Source: Poney70
From Xiaomi.ea
Hi, when going from stock (fastboot) to this, which other images do I need, and where should I get them? I can see that the (old) guides mention flashing a "vbmeta"?
ballajalla said:
Hi, when going from stock (fastboot) to this, which other images do I need, and where should I get them? I can see that the (old) guides mention flashing a "vbmeta"?
Click to expand...
Click to collapse
Just follow my guide. You only need to flash rec.img
Can I also flash the Twrp.img through the Twrp I already have.?
*justintime* said:
Can I also flash the Twrp.img through the Twrp I already have.?
Click to expand...
Click to collapse
Of course
Xayah said:
Just follow my guide. You only need to flash rec.img
Click to expand...
Click to collapse
Thank you for your replay, but I am confused about the `rec.img` you mention, which image is this? I can only see one on github, which is `twrp-3.5.2-cas-xayah.img`
ballajalla said:
Thank you for your replay, but I am confused about the `rec.img` you mention, which image is this? I can only see one on github, which is `twrp-3.5.2-cas-xayah.img`
Click to expand...
Click to collapse
Thats it. My guide is just a example
Hi, why it take so much time for decrypting data?
Anyone installed an Android 12 ROM using this? I want to try updating to Xiaomi.eu MIUI13 the instant it comes out for the Mi 10 Ultra.
AerationCheese said:
Anyone installed an Android 12 ROM using this? I want to try updating to Xiaomi.eu MIUI13 the instant it comes out for the Mi 10 Ultra.
Click to expand...
Click to collapse
Not support A12
What are people using to flash the Android 12 ROMs on the Mi 10 Ultra then?
AerationCheese said:
What are people using to flash the Android 12 ROMs on the Mi 10 Ultra then?
Click to expand...
Click to collapse
I will flash Xiaomi EU Weekly MIUI 13 with fastboot. It was released yesterday.
MIUI 13 - 22.2.17/19
Status: RELEASED RULES WHEN POSTING 1. If a ROM is not published DONT ASK ABOUT ITS ETA 2. If a ROM is not published DONT ASK why! 3. If a ROM is available, download it and use it 4. If a ROM has bugs, post the bug to the bug section if the BUG is not already listed 5. If you use any form of...
xiaomi.eu
Could that Project be a solution for the camera? :
GitHub - AtomicXZ/vendor_xiaomi_miuicamera: MIUI cam for AOSP
MIUI cam for AOSP. Contribute to AtomicXZ/vendor_xiaomi_miuicamera development by creating an account on GitHub.
github.com