Related
This guide lets you install any GSI treble roms on our Daisy.
Read carefully and go step by step!
Update: Since Havoc OS doesn´t need permissive Kernel, I just installed the latest stock rom (9.6.9.0), flashed Havoc, set everything up and ended with sh...t... Camera´s not working, Opera freezes, everything sucks. It was a waste of time... So it´s still the situation:
If you want to use a custom GSI-Rom Only use this combination: Stock rom before flashing GSI: 9.6.4.0 and Kernel: Unofficial TWRP by Yshalsager - this combination works like a charm
Let´s get started: Be sure you are on Stock 9.6.4.0 (july security patch) if not, your wifi will not work in treble rom!
1) Download latest AB arm 64 gsi build. - ONLY ARM 64 AB GSI WILL WORK!
2) If you don´t have fastboot and adb download it from here: https://forum.xda-developers.com/sho....php?t=2588979 and install it!
3) Extract gsi64-ab-image to adb folder and rename it to system.img
4.a) Windows 7: right klick on white space in your adb-folder: open command prompt here
4.b) Windows 10: open command prompt as admin and navigate to your adb folder
5.) Power off your Smartphone and press pwr and vol- together -> your screen will show FASTBOOT - connect your phone to your PC
6.) type in your command prompt
Code:
fastboot oem unlock
Important: this will format your SD - All data will be lost If you perform that step! -> Backup before!7.) Phone will reboot, erase data and boot up. Power off again after boot up. Power + vol- to enter fastboot.
Now you have to decide: If you want to use Android 9 roms and TWRP together, you have to decrypt your data - else TWRP will not be able to read data! If you don´t care continue on step 11
8.) Download a patched_boot.img and place it in your fastboot folder - since only 9.6.4.0 works without bugs, you have to choose the patched 9.6.4.0 boot
9)
Code:
fastboot boot patched_boot.img
10) Connect to internet and update Magisk manager, download a root explorer - you could use this and go to
/vendor/etc/ and open the file fstab.qcom in editorreplace the text "forceencryption=footer with "encryptable=footer" and reboot to bootloader
11) Download this, rename it to boot.img and copy it to your fastboot folder
Code:
fastboot flash boot boot.img
12) Install official TWRP
13) After installing official TWRP reboot to TWRP agian and go to "wipe" -> "format data" and type "yes". Reboot to bootloader
14.) Download your GSI AB Image and place it in your fastboot folder
Code:
fastboot flash system [imagename].img
If you want, you can boot now to twrp and install magisk and/or gapps whatever - everything will work. Else you boot up your new system - Sometimes your GSI-rom will not boot up without a rooted kernel.
So if you stay in bootloop, just install magisk.zip!
Violla - Now you have a treble gsi rom on your Mi A2 Lite!
theres working twrp out for daisy, does this change anything refering to your first line:
"1) Download latest AB arm 64 gsi build. I would always use the gappsed version - twrp still not running for daisy... - ONLY ARM 64 AB GSI WILL WORK!"
thanks for the guide!
i really want to try this but im not sure which rom fully works. Also i'm not sure to do this without TWRP cause i'd like to have a complete backup of my device.
i'm in 9.6.9 version now with locked bootloader and unrooted
any suggests for me to try this rom
tutankpusch said:
theres working twrp out for daisy, does this change anything refering to your first line:
"1) Download latest AB arm 64 gsi build. I would always use the gappsed version - twrp still not running for daisy... - ONLY ARM 64 AB GSI WILL WORK!"
Click to expand...
Click to collapse
Updated: I removed that line...
merlin.berlin said:
thanks for the guide!
i really want to try this but im not sure which rom fully works. Also i'm not sure to do this without TWRP cause i'd like to have a complete backup of my device.
Click to expand...
Click to collapse
No problem - meanwhile there´s a official twrp here - and you can still use this guide
If you want to flash havoc 2.0 - I think it´s the best rom on earth , you will need to change your kernel to permissive that it will boot. To do that, read the thread there´s a vivid discussion how to do it...
elkhshap said:
i'm in 9.6.9 version now with locked bootloader and unrooted
any suggests for me to try this rom
Click to expand...
Click to collapse
If you like to have more features and/or pie (Android 9), then I would suggest to flash a custom gsi rom. If you can live with stock, I wouldn´t touch it.
Voodoojonny said:
No problem - meanwhile there´s a official twrp here - and you can still use this guide
If you want to flash havoc 2.0 - I think it´s the best rom on earth , you will need to change your kernel to permissive that it will boot. To do that, read the thread there´s a vivid discussion how to do it...
Click to expand...
Click to collapse
i want havoc OS but as i understand i can't use the fastboot method because i need the permissive fix, which only can be installed via TWRP, correct?
i would prefer fastboot over TWRP because all the problems with sdcard reading, encrypting etc.
merlin.berlin said:
i want havoc OS but as i understand i can't use the fastboot method because i need the permissive fix, which only can be installed via TWRP, correct?
i would prefer fastboot over TWRP because all the problems with sdcard reading, encrypting etc.
Click to expand...
Click to collapse
Hi,
there are so many reasons for havoc not to boot... and so less to boot...
BUT... If you won´t mind to use an unencrypted phone or no twrp, you can use (as I think) the best Android OS, havoc.
So think about, what is more important for you: TWRP or encryption.
1. With encryption: (Quite easy)
a) Go to stock 9.6.4.0 - July patch with mi flash and choose clean all (yes you will loose all your data -> back up everything) - Important: don´t install any ota after that!b) Download latest havoc and place it in your fastboot folderc) Download this TWRP and place it in your fastboot folder - you need this as Kerneld) As lazy person, I would rename the havoc file to havoc.img and the twrp file to twrp.imge) copy userdata.bin from stock to fastboot
Code:
fastboot flash system havoc.img
Code:
fastboot flash boot twrp.img
Code:
fastboot flash userdata userdata.bin
Code:
fastboot reboot
Wait and wait and wait and violla, you have havoc!
f) Gapps: download gapps, copy it to your fastboot folder and rename it to gapps.zip. Boot to recovery - twrp will not be able to read your data -> skip and allow modifications
Code:
adb push ./gapps.zip /sdcard
- Now you see gapps in your zip and you can install it!
g) Magisk: for magisk you need to download my patched twrp and place it in your fastboot folder
Code:
fastboot boot patched_twrp.img
- After booting up, you can go to magisk manager (yes: upgrade first etc.... and install magisk using the "direct method"
2. If you want to remove encryption - then you can use twrp fully, use this guide: here
Important: If you use another stock rom than 9.6.4.0 or do an ota, you will loose wifi!after doing all the steps:
Code:
fastboot flash system havoc.img
- that´s it!
Now you can use havoc
Voodoojonny said:
Hi,
there are so many reasons for havoc not to boot... and so less to boot...
BUT... If you won´t mind to use an unencrypted phone or no twrp, you can use (as I think) the best Android OS, havoc.
So think about, what is more important for you: TWRP or encryption.
1. With encryption: (Quite easy)
a) Go to stock 9.6.4.0 - July patch with mi flash and choose clean all (yes you will loose all your data -> back up everything) - Important: don´t install any ota after that!b) Download latest havoc and place it in your fastboot folderc) Download this TWRP and place it in your fastboot folder - you need this as Kerneld) As lazy person, I would rename the havoc file to havoc.img and the twrp file to twrp.imge) copy userdata.bin from stock to fastboot
Code:
fastboot flash system havoc.img
Code:
fastboot flash boot twrp.img
Code:
fastboot flash userdata userdata.bin
Code:
fastboot reboot
Wait and wait and wait and violla, you have havoc!
f) Gapps: download gapps, copy it to your fastboot folder and rename it to gapps.zip. Boot to recovery - twrp will not be able to read your data -> skip and allow modifications
Code:
adb push ./gapps.zip /sdcard
- Now you see gapps in your zip and you can install it!
g) Magisk: for magisk you need to download my patched twrp and place it in your fastboot folder
Code:
fastboot boot patched_twrp.img
- After booting up, you can go to magisk manager (yes: upgrade first etc.... and install magisk using the "direct method"
2. If you want to remove encryption - then you can use twrp fully, use this guide: here
Important: If you use another stock rom than 9.6.4.0 or do an ota, you will loose wifi!after doing all the steps:
Code:
fastboot flash system havoc.img
- that´s it!
Now you can use havoc
Click to expand...
Click to collapse
Please explain by video
thank you so much for this guide:good:
i'll try it later when im home:fingers-crossed:
Where do I find a userdata.bin file?
monzer said:
Where do I find a userdata.bin file?
Click to expand...
Click to collapse
In the Images-Folder of your stockrom after extracting...
- download fastboot stock rom
- extract archive
- look inside "images"
update: it´s userdata.img
Voodoojonny said:
In the Images-Folder of your stockrom after extracting...
- download fastboot stock rom
- extract archive
- look inside "images"
update: it´s userdata.img
Click to expand...
Click to collapse
Please post a video for ease of action
monzer said:
Please post a video for ease of action
Click to expand...
Click to collapse
Sorry, that will not happen!
Updated: view first post. This guide will definitely work well - and it´s easy! At least more easy than the other guides .
Voodoojonny said:
Updated: view first post. This guide will definitely work well - and it´s easy! At least more easy than the other guides .
Click to expand...
Click to collapse
No idea why you're useless taking pot-shots at other people, especially when you keep spreading lies about stock roms because you use a broken recovery. But have it your way.
Just keeping telling people to use a broken/untested recovery and bricking their phones, that forces them to reflash boot images. Can't wait until the bricks pile up.
I'm done with this website.
KezraPlanes said:
No idea why you're useless taking pot-shots at other people, especially when you keep spreading lies about stock roms because you use a broken recovery. But have it your way.
Just keeping telling people to use a broken/untested recovery and bricking their phones, that forces them to reflash boot images. Can't wait until the bricks pile up.
I'm done with this website.
Click to expand...
Click to collapse
If you would read, you would have noticed, that that broken and untested recovery is used as kernel, becouse it works great as kernel for gsi roms. Within the process it will be upgreaded by official twrp.
I spend a lot time, testing how to install custom roms on this phone, becouse I don't like like stock and I share my experience with others. Noone will break his phone with this! Perhaps you can try before complaining.
KezraPlanes said:
No idea why you're useless taking pot-shots at other people, especially when you keep spreading lies about stock roms because you use a broken recovery. But have it your way.
Just keeping telling people to use a broken/untested recovery and bricking their phones, that forces them to reflash boot images. Can't wait until the bricks pile up.
I'm done with this website.
Click to expand...
Click to collapse
Voodoojonny said:
If you would read, you would have noticed, that that broken and untested recovery is used as kernel, becouse it works great as kernel for gsi roms. Within the process it will be upgreaded by official twrp.
I spend a lot time, testing how to install custom roms on this phone, becouse I don't like like stock and I share my experience with others. Noone will break his phone with this! Perhaps you can try before complaining.
Click to expand...
Click to collapse
Lol, this site has gone way down hill... It's almost a joke now.
So many people asking for the 'easy' way and want answers to easily searchable questions. Sooo many multiple posts, and people not wanting to do the research themselves. How many threads need to be created on bricked devices because you didn't heed the warnings or follow the directions...
I wonder if xda even cares? This place use to be a great tool for the ones who like to tinker.
There are definitely a few folks keeping the spirit alive, but so many unnecessary posts - like what I'm writing right now...
Anyway thanks to anyone who puts time and effort for the greater good, we should all understand that tinkering with our devices can potentially have adverse effects.
Thanks for this noob friendly guide! a massive thanks! But hotspot still not working. Haven't tried the gcam but the stock camera is working but has no portrait and other features. The havoc os 2.0 looks snappy and buggy. Ill try other treble roms in few days
Any suggestions?
Bokoko006 said:
Thanks for this noob friendly guide! a massive thanks! But hotspot still not working. Haven't tried the gcam but the stock camera is working but has no portrait and other features. The havoc os 2.0 looks snappy and buggy. Ill try other treble roms in few days
Any suggestions?
Click to expand...
Click to collapse
You're welcome. Don't have problems with bugs and havoc 2.0... Interesting to test would be arrow pie! Benzo had problems with camera and flashlight... All the 8.1 can't handle the notch and overlay!
Hi can anyone make an android 11 custom rom(Pixel experience/ evolution x/ havoc os) for this phone pls? Thank You.
Yes, you can:
go to https://forum.xda-developers.com/t/10-0-project-treble-for-xperia-xzs-2020-03-18.3976367/ then download the zip file and flash vendor.img and boot.img (steps provided in the zip).
then download any android 11 custom rom GSI having arm64 and AB or A/B NOT A only or B only and flash it with fastboot command:
Code:
fastboot flash system <GSI filename>.img
You will need to download and install adb and fastboot tools from google to get the above code working. Also have a bit of patience while first boot your custom ROM after flashing, I will take some time for it to boot up
I have tried:
- Pixel Experience Plus and non-Plus
- Corvus OS
- Havoc OS
Link to official GSI ROMs supporting Project treble devices(This device is included): https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
i get "Invalid sparse file format at header magic"
and my phone won't boot HELP
prayagprajapati17 said:
Yes, you can:
go to https://forum.xda-developers.com/t/10-0-project-treble-for-xperia-xzs-2020-03-18.3976367/ then download the zip file and flash vendor.img and boot.img (steps provided in the zip).
then download any android 11 custom rom GSI having arm64 and AB or A/B NOT A only or B only and flash it with fastboot command:
Code:
fastboot flash system <GSI filename>.img
You will need to download and install adb and fastboot tools from google to get the above code working. Also have a bit of patience while first boot your custom ROM after flashing, I will take some time for it to boot up
I have tried:
- Pixel Experience Plus and non-Plus
- Corvus OS
- Havoc OS
Link to official GSI ROMs supporting Project treble devices(This device is included): https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Click to expand...
Click to collapse
i get "Invalid sparse file format at header magic"
and my phone won't boot HELP
uh btw don't be stupid like me and rename .xz to .img use 7zip to OPEN the .xz then extract the .img inside
prayagprajapati17 said:
Yes, you can:
go to https://forum.xda-developers.com/t/10-0-project-treble-for-xperia-xzs-2020-03-18.3976367/ then download the zip file and flash vendor.img and boot.img (steps provided in the zip).
then download any android 11 custom rom GSI having arm64 and AB or A/B NOT A only or B only and flash it with fastboot command:
Code:
fastboot flash system <GSI filename>.img
You will need to download and install adb and fastboot tools from google to get the above code working. Also have a bit of patience while first boot your custom ROM after flashing, I will take some time for it to boot up
I have tried:
- Pixel Experience Plus and non-Plus
- Corvus OS
- Havoc OS
Link to official GSI ROMs supporting Project treble devices(This device is included): https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Click to expand...
Click to collapse
How did Havoc OS work for you?
I am always afraid to flash something that doesn't say precisely that it is for the XZs. But I should mainly be concerned about the kernel, right? If the image is wrong it just won't boot? But the kernel can brick it. Is my assumption correct?
Thanks to everyone who help us illiterates out...
Cordially,
Martin Book
Just follow the guide in the xda thread link I gave, you can use and android 11 GSI ARM64 AB image and you will be fine as far as my testing goes...
Just flash the vendor.img, boot.img and after that find a GSI image with ARM64 AND AB(The file name might use some other code name for this so just make sure the one you download has AB partition).
Note: Android 12 won't work and also daily use is not recommended
Hi,
I'm trying to flash Samsung Galaxy A8s (SM-G8870) with plain AOSP GSI. When I retrieve the ROM from https://samfw.com/firmware/SM-G8870/TGY/G8870ZHU5CUA1 I realized that there are no vbmeta.img file inside. Inside it, there is the AP file, as usual. It consists only of these files:
meta-data
boot.img.lz4
persist.img.ext4.lz4
recovery.img.lz4
system.img.ext4.lz4
userdata.img.ext4.lz4
vendor.img.ext4.lz4
Click to expand...
Click to collapse
When I tried to add vbmeta and re pack AP file and flash it using Odin, Odin throws Unassigned file error, which I think is due to newly added vbmeta.img. When I tried to flash the image without vbmeta.img, Odin completes successfully, but the phone then stuck in Download mode (every time it reboots, it returns to Download mode). This is the image that I use: https://github.com/phhusson/treble_...nload/v222/system-quack-arm64-ab-gapps.img.xz
I also tried Android GSI from official Android page, but get a write error when copying system.img.ext4. Can somebody help me? Is vbmeta.img is really needed? If so, why does the original firmware does not include one? This phone was released in 2018 with Android 10 preinstalled.
I already have this phone OEM unlocked, it is ON in developer options. I am not using TWRP. I also left bootloader file as is (I only repacked the AP file), as I do not need root.
AFAIK the AOSP GSI doesn't include a verify boot solution (such as AVB 1.0 or AVB 2.0 ).
Look also inside here:
Generic system images | Android Open Source Project
source.android.com
jwoegerbauer said:
AFAIK the AOSP GSI doesn't include a verify boot solution (such as AVB 1.0 or AVB 2.0 ).
Look also inside here:
Generic system images | Android Open Source Project
source.android.com
Click to expand...
Click to collapse
Can you explain more? Does that means Samsung A8s has verified boot and cannot be turn off? Or it does not have verified boot at all thus no vbmeta at all?
So, I want to install Lineage OS instead of Android 10 Go Edition on my Doogee X95, but I can't find any TWRP build for the Doogee X95, so the thing is: How can i do to install Lineage OS on Doogee X95 ? Can anyone help me please ?
The Dogee X95 is a low-end phone, hence Android 10 GO got pre-installed what IMO is absolutely correct.
Of course you can try to flash LOS via ADB Sideload method.
Read
Generic system images | Android Open Source Project
source.android.com
Use this GSI arm64 A-only
[DISCONTINUED][GSI][11] LineageOS 18.x GSI (all archs)
Background: This is a natural continuation/extension of the LineageOS 17.x GSIs I've been making since November 2019. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance...
forum.xda-developers.com
Unlock bootloader first
Ok i'll check that right now
Ok so i checked for ADB Sideload, but it seems like i need TWRP, and there is no TWRP build for the Doogee X95, so i think i'll try to use the Lineage OS GSI image, and i'll see how can i install it
LR7875, there is a problem with the GSI you told me to use, it's an ARM64; and when i install Droid Hardware Info, it say that i'm using an ARMv7 (armeabi-v7a, armeabi) CPU, same for Treble Check that's saying that i use a 32-bit ARM CPU, but if i check on google the Doogee X95 it says that, it is, indeed, a 64-bit ARM CPU, but the thing is why is it saying that i use a 32bit ARM if it is a 64bit ARM ? Is it safe to use the ARM64 A-Only GSI ?
DidierSardine said:
Ok so i checked for ADB Sideload, but it seems like i need TWRP, and there is no TWRP build for the Doogee X95, so i think i'll try to use the Lineage OS GSI image, and i'll see how can i install it
Click to expand...
Click to collapse
ADB Sideload is a mode bootloader boots into to allow to flash ROMs located on computer: has really nothing to do with TWRP.
Code:
adb devices
adb reboot sideload
adb sideload <ROM-ZIP>
ARMV7 CPU is 32-bit CPU. Hence you can only flash ROMs what are compiled for ARMV7 CPUs.
Ok i'll try to flash the A-only ARM 32bit rom of Lineage OS using sideload, i hope it will works
Hum i just remembered the Lineage OS is a .xz Archive containing the .img, what should i do ?
adb sideload lineage-18.1-20210808-UNOFFICIAL-treble_arm_avS.img (extracted .img file)
or
adb sideload lineage-18.1-20210808-UNOFFICIAL-treble_arm_avS.img.xz (archive)
Sorry, you need to flash arm (32) GSIs, not 64
DidierSardine said:
Hum i just remembered the Lineage OS is a .xz Archive containing the .img, what should i do ?
adb sideload lineage-18.1-20210808-UNOFFICIAL-treble_arm_avS.img (extracted .img file)
or
adb sideload lineage-18.1-20210808-UNOFFICIAL-treble_arm_avS.img.xz (archive)
Click to expand...
Click to collapse
Flash the extracted .IMG file.
jwoegerbauer said:
ADB Sideload is a mode bootloader boots into to allow to flash ROMs located on computer: has really nothing to do with TWRP.
Code:
adb devices
adb reboot sideload
adb sideload <ROM-ZIP>
Click to expand...
Click to collapse
As far as I have concerned it is impossible to ADB sideload a custom ROM via stock recovery.
Also a GSI is a system image, which is impossible to ADB sideload because you cannot dump it into a zip. For ADB sideloadable zips the zip always contains a META-INF file which vertified the ROM.
Hence it is only flashable in fastboot.
The original poster also needs a vbmeta.img from stock rom and flash it in fastboot with a special command, to disable boot vertification (even if bootloader unlocked you still need to disable vertification)
Because you quoted me: WTF? Has nothing whatsoever to do with what I said.
jwoegerbauer said:
Because you quoted me: WTF? Has nothing whatsoever to do with what I said.
Click to expand...
Click to collapse
I mean how can he ADB sideload without twrp
@DidierSardine
If your phone is Project Treble enabled ( should be - but verify this ) then take note that TWRP isn't needed at all to flash a GSI ROM.
How-to in detail is described here:
How to flash a Generic System Image (GSI) on Project Treble supported devices
So your device supports Project Treble, what does that mean for you? It means you can flash a Generic System Image such as LineageOS or Resurrection Remix! Enjoy AOSP-based custom ROMs! Here's a guide on how to install these ROMs.
www.xda-developers.com
Ok, so, i don't flash it using adb sideload, but using fastboot (as described in the link you sent), but the thing is, in the Flash GSI without TWRP section, there is that line:
fastboot -u flash system name_of_system.img
but the thing is: I have to put in the Lineage OS GSI .img file (lineage-18.1-20210808-UNOFFICIAL-treble_arm_avS.img) or the system.img file, because i don't have the system.img file of Lineage OS, and i don't know how can i get it. So i have to put "lineage-18.1-20210808-UNOFFICIAL-treble_arm_avS.img" instead of "name_of_system.img"
like this:
fastboot -u flash system lineage-18.1-20210808-UNOFFICIAL-treble_arm_avS.img
?
Yes, if it's a 32-bit image
Ok thanks, i'll try this right now
I've a problem, when i do
fastboot erase system
i get this error: FAILED (remote: 'not allowed in locked state')
but the thing is: my bootloader is unlocked, so why is it happening ?
Hey does anyone know about a custom recovery for oukitel k15 pro? Or can I get away with using the stock recovery and a patched magisk file? If so does anyone have a up to date link.
Also would lineage work on this phone.
Thanks in advance
Lewickham2022 said:
Hey does anyone know about a custom recovery for oukitel k15 pro? Or can I get away with using the stock recovery and a patched magisk file? If so does anyone have a up to date link.
Also would lineage work on this phone.
Thanks in advance
Click to expand...
Click to collapse
There is no custom recovery. Oukitel haven't even posted the official Android 11 ROM on their Download Center website yet, even though I sent them a message about it a week or two ago.
I bought the phone, but haven't gotten it yet.
I wouldn' t do anything to modify the ROM without having the official ROM from Oukitel to unbrick the phone just in case something goes wrong with Magisk or something.
There are ways to extract the ROM with SP Flash Tool or maybe something else, so I would do that first.
For rooting I found this link for Oukitel wp12 with Android 11, I think I would try the same method with K15 Pro
Oukitel WP12 Magisk root bootloop
I'm trying to root an Oukitel WP12 with Magisk. I've downloaded the firmware from the vendor's link and flashed it successfully just like for other Oukitel phones (WP6, WP10). I could also create a magisk-patched boot image. I followed regular...
forum.xda-developers.com
Then, if that's not enough and we want a custom ROM like Lineage, for example, then we would have to use a GSI ROM like those from here
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
and follow something like the fastboot method outlined here for wp5
GitHub - adil192/OukitelWP5TrebleTips: Sharing my experience with flashing a GSI on a friend's Oukitel WP5 (3GB model).
Sharing my experience with flashing a GSI on a friend's Oukitel WP5 (3GB model). - GitHub - adil192/OukitelWP5TrebleTips: Sharing my experience with flashing a GSI on a friend's Oukitel WP5...
github.com
Maybe there's a better link for GSI fastboot for Oukitel with Android 11
If you try anything, let me know. I'm waiting for my k15 pro to arrive, possibly next week.
I need it rooted, at least.
Let me know the outcome of rootin the k15 pro and if you succeed please tell me the steps. Also do you know if lineage will be compatible eventually?
Is there any news yet?
Lewickham2022 said:
Is there any news yet?
Click to expand...
Click to collapse
My phone came from AliExpress after 3.5 months, jeez. Got a refund, too, which I might return, never mind.
I dumped/backed up ROM partitions, except userdata because it's big and backup unnecessary, unless you want to keep your personal data in raw binary state for later, and rooted the phone.
You need MTK VCom drivers installed, e.g. from here:
Download MediaTek USB VCOM Drivers for Windows (32 & 64 bit)
Download MTK USB VCOM Drivers for Windows 10 to connect MediaTek phones even in a bricked state. Also, check the Installation guide.
www.ytechb.com
Use mtkclient:
mtkclient/README.md at main · bkerler/mtkclient
MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.
github.com
I unlocked bootloader first. Remember UNLOCKING BOOTLOADER WIPES ALL DATA, returns to factory settings, back up all personal data to PC or SD card first!
To unlock bootloader, if you don't know, go to Settings, About Phone, tap 7 times on Build Number, You are Developer flashes on, go to System, Developer Options, OEM unlocking on, USB debugging on.
MTKCLIENT has a command to unlock the bootloader, it would surely work, I used Fastboot before I learned of mtkclient.
If using Fastboot, turn off phone. Hold Volume up and Power. Choose Fastboot. Connect phone.
You need Minimal Fastboot and ADB installed:
Download Minimal ADB and Fastboot Tool (all versions)
Download the latest version of Minimal ADB and Fastboot Tool which allow you to install and setup the ADB and Fastboot files on the computer.
androidmtk.com
Open CMD, type:
fastboot devices
if phone is listed, then type:
fastboot flashing unlock
fastboot reboot
Never re-lock the bootloader if your phone is rooted or GSI Lineage or other ROM other than original is installed. More than likely would brick the phone.
Everything is explained in mtkclient readme, line by line.
I used Windows 10, works on 11 too, there is a guide for Linux, and even a Ubuntu live image to use. Back up partitions first. Oukitel still haven't posted ROM, but can extract it from the phone, no problem.
Root is explained, need to get modified Magisk for MTK, and flash patched boot and empty vbmeta. It worked like a charm. There are guides on XDA on how to flash System GSI images to Android Super partition. Might try it later. One is here:
How to flash GSIs on devices with dynamic super partition
* Disclaimer * 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 * before flashing GSI! YOU are choosing to make these modifications, and if *...
forum.xda-developers.com
GSI Lineage images are here:
Andy Yan's personal builds // GSI - Browse /lineage-19.x at SourceForge.net
sourceforge.net
You couldn't add GAPPS, though, no TWRP, unless there is another way, doubt it. Could install replacement MicroG. Plenty other GSI images here:
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Good luck.
MarkR7 said:
My phone came from AliExpress after 3.5 months, jeez. Got a refund, too, which I might return, never mind.
I dumped/backed up ROM partitions, except userdata because it's big and backup unnecessary, unless you want to keep your personal data in raw binary state for later, and rooted the phone.
You need MTK VCom drivers installed, e.g. from here:
Download MediaTek USB VCOM Drivers for Windows (32 & 64 bit)
Download MTK USB VCOM Drivers for Windows 10 to connect MediaTek phones even in a bricked state. Also, check the Installation guide.
www.ytechb.com
Use mtkclient:
mtkclient/README.md at main · bkerler/mtkclient
MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.
github.com
I unlocked bootloader first. Remember UNLOCKING BOOTLOADER WIPES ALL DATA, returns to factory settings, back up all personal data to PC or SD card first!
To unlock bootloader, if you don't know, go to Settings, About Phone, tap 7 times on Build Number, You are Developer flashes on, go to System, Developer Options, OEM unlocking on, USB debugging on.
MTKCLIENT has a command to unlock the bootloader, it would surely work, I used Fastboot before I learned of mtkclient.
If using Fastboot, turn off phone. Hold Volume up and Power. Choose Fastboot. Connect phone.
You need Minimal Fastboot and ADB installed:
Download Minimal ADB and Fastboot Tool (all versions)
Download the latest version of Minimal ADB and Fastboot Tool which allow you to install and setup the ADB and Fastboot files on the computer.
androidmtk.com
Open CMD, type:
fastboot devices
if phone is listed, then type:
fastboot flashing unlock
fastboot reboot
Never re-lock the bootloader if your phone is rooted or GSI Lineage or other ROM other than original is installed. More than likely would brick the phone.
Everything is explained in mtkclient readme, line by line.
I used Windows 10, works on 11 too, there is a guide for Linux, and even a Ubuntu live image to use. Back up partitions first. Oukitel still haven't posted ROM, but can extract it from the phone, no problem.
Root is explained, need to get modified Magisk for MTK, and flash patched boot and empty vbmeta. It worked like a charm. There are guides on XDA on how to flash System GSI images to Android Super partition. Might try it later. One is here:
How to flash GSIs on devices with dynamic super partition
* Disclaimer * 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 * before flashing GSI! YOU are choosing to make these modifications, and if *...
forum.xda-developers.com
GSI Lineage images are here:
Andy Yan's personal builds // GSI - Browse /lineage-19.x at SourceForge.net
sourceforge.net
You couldn't add GAPPS, though, no TWRP, unless there is another way, doubt it. Could install replacement MicroG. Plenty other GSI images here:
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Good luck.
Click to expand...
Click to collapse
Thanks for the reply. I had a few problems with micro g on MI A2. After flashing micro g in magisk is there a certain gapps I need to flash? Or can I just download Google services after flashing micro g
Lewickham2022 said:
Thanks for the reply. I had a few problems with micro g on MI A2. After flashing micro g in magisk is there a certain gapps I need to flash? Or can I just download Google services after flashing micro g
Click to expand...
Click to collapse
I was wrong about LineageOS not having GAPPS preinstalled. The link I gave you:
Andy Yan's personal builds // GSI - Browse /lineage-19.x at SourceForge.net
sourceforge.net
has this system image of LineageOS with GAPPS included, vndklite are read/write system images that I saw someone said were working on Oukitel phones with Android 11, and are generally probably best to use, so if you use that one, you don't need microG, which would have to be installed from F-Droid store or something like that:
https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/lineage-19.1-20220410-UNOFFICIAL-arm64_bgS-vndklite.img.xz/download
G or g in the name of the system indicates that GAPPS are included.
I will try to flash that one myself sooner or later. It's based on Android 12, and if it doesn't work for some reason then we would have to drop to Lineage 18.1, but those aren't with GAPPS, so microG required:
Andy Yan's personal builds // GSI - Browse /lineage-18.x at SourceForge.net
sourceforge.net
There are other ROM with plenty of customizations that might be ok.
Corvus OS
Download Corvus OS for free. Corvus OS is another retarded ROM with many retarded Customization. First, it's inspired by Dirty Unicorns (thanks to Alex Cruz), but then we picked many other features too.
sourceforge.net
has GAPPS
Rest is here to choose from:
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Funny, I'm using Xiaomi Mi A2 Lite now.
Lewickham2022 said:
Thanks for the reply. I had a few problems with micro g on MI A2. After flashing micro g in magisk is there a certain gapps I need to flash? Or can I just download Google services after flashing micro g
Click to expand...
Click to collapse
OK, it is possible to install Android 11 GSI system images on this phone. Android 12 images do not work, something to do with incompatible boot partition.
It's possible to try out GSI system images without flashing by installing this app:
GitHub - VegaBobo/DSU-Sideloader: A simple app made to help users easily install GSIs via DSU's Android feature.
A simple app made to help users easily install GSIs via DSU's Android feature. - GitHub - VegaBobo/DSU-Sideloader: A simple app made to help users easily install GSIs via DSU's Android feat...
github.com
Root is useful, but not necessary. Seems not to work, maybe needs flashed empty vbmeta_system and vbmeta_vendor like indicated below and I restored all to stock ROM except for boot.img with Magisk 24.3 and empty vbmeta.img
If you managed to make full backup of ROM with mtkclient, enable USB debugging, unlock bootloader, then to flash GSI images or Lineage 18.1 based on Android 11 (it works, but no image with gapps unless found somewhere else) you have to have installed Google Android USB driver from here
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
Unpack files, connect phone in recovery, power + volume up then power+ volume up fast click, choose fastboot, that gives you FastbootD (colorful menu), which is now used to flash system partitions. Connect phone, install driver with .inf file.
You also need Google platform tools
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Unpack anywhere if on Windows.
Run cmd, then "fastboot devices" to see if phone gets detected, should be there.
From here get product_gsi.img:
[Tutorial] Magisk on GSI on devices with dynamic partition
I hope you already know how to flash GSI on devices with dyamic partition already. If not then you can follow this guide: https://forum.xda-developers.com/t/how-to-flash-gsis-on-devices-with-dynamic-super-partition.4256667/#post-85271987 If...
forum.xda-developers.com
In mtk client is an empty vbmeta file - vbmeta.img.empty or similar, needs to be flashed to vbmeta, vbmeta_system, and vbmeta_vendor to disable verification of boot for magisk, and system and vendor for GSI system images. Can be done with mtkclient or normal fastboot ( power + volume down, choose fastboot, connect phone, run cmd, then "fastboot flash vbmeta vbmeta.img.empty (could be renamed to anything simple, name doesn't matter))
Then
fastboot flash vbmeta_system vbmeta_img.empty
Then
fastboot flash vbmeta_vendor vbmeta.img.empty
Same file to all three partitions, disables verification, worked for me. Can be done with GUI in mtkclient, same thing. Or commands in mtkclient
"python w vbmeta vbmeta.img.empty"
Etc.
Back to FastbootD -
"fastboot reboot fastboot" or power + volume up for recovery then click them again, choose fastboot.
Or probably "adb reboot fastboot" if phone is running system.
Run cmd, "fastboot devices" to be sure phone is detected, then
"fastboot flash product product_gsi.img"
This resizes dynamic system partition when flashing system images. This only modifies internal logical partitions within SUPER partition that contains Product, System, and Vendor. SUPER can be restored with mtkclient or just fastboot, I guess, I restored with mtkclient, works.
Then you can flash any system based on Android 11, stock phhusson GSI works. the system needs to be arm64, ab (for A/B partitions, indicated by letter B in name), vndklite, G or Gapps (if you want them), V is vanilla - no gapps, S is superuser but seems to have conflicts with magisk if you want that as root later. N is no superuser/root.
Eg.
"fastboot flash system Lineage-18.1-2021214-UNOFFICIAL-treble_arm64_bvS-vndklite.img" Rename this to 1.img or whatever, simpler to type
"fastboot flash system.1.img" or something like that.
"Invalid Sparse System Image At Magic Header" appears, but doesn't matter, starts flashing in 30 seconds or so, 10 or 11 chunks, maybe 2-3 minutes per system image.
Then
"fastboot reboot" go to recovery, power +volume up, click them again, choose wipe user data, wipe cache to get rid of old settings and apps from previous system.
"fastboot reboot recovery" should work too.
Seems that on custom ROMs Magisk 24.3 app gives option to directly patch boot image without need for flashing patched boot.img. Not sure about that. Just flashing patched boot.img in fastboot gives root, anyway.
If you just want newest Magisk then flash empty vbmeta and then patched boot Magisk generates. Those can be done in normal fastboot. Works fine.
Everything seems to work.