Related
i don't know wither this fits here or in the guide section so i leave it for the moderators to decide to move this thread or not
with that being said
i wanted to share my experience on how easily you can boot to miui without converting your device using erfan gsi
Download :
1. Erfan miui 10 a/b gsi from here : https://mirrors.lolinet.com/firmware/gsi/MIUI-AB-9-20190413-ErfanGSI.img.7z
2 . Files in this thread : https://forum.xda-developers.com/mi...on-aio-gsi-thread-mi-a2-t3933356#post79601628
Instructions :
1. format both a and b completely ( Data , system , etc ) also format data completely from twrp ( there is option which let you format data and userdata together next to advance option)
2. Restore the android q backup but only vendors and boot DONT RESTORE SYSTEM
3. install your gsi as system image
4. install. DM-Verity & Forceencrypt Disabler
5 . install permissiver_v2
6. format data completely from twrp ( there is option which let you format data and userdata together next to advance option)
7. reboot system and enjoy
Known issues
stock camera doesn't work
sometimes the blur effect in the notifications shade will not work instead it would be completely transparent
disclaimer : i didn't make or port any of those files used in the thread i'm just sharing my experience
Google Camera works?
g.laterza9 said:
Google Camera works?
Click to expand...
Click to collapse
it should work if you enable api 2 by magisk
however i didn't try it yet
Hi everyone!
I present to you the practical and simple guide special for dummies that will allow you to try and use the wonders of google treble project in our beloved Moto Z [Griffin has no official support but...] thanks to the great work of the highly recognized developer @erfanoabdi we can enjoy project treble in an easy way [*could apply user restrictions] in our griffin.
*First of all, this guide is designed for those who are curious and have a high degree of autonomy when they try to solve low level or common problems of the Android system. You dont need to be a developer but you must have experience in using and applying the following words: unlocked bootloader, ADB and Fastboot basic commands, Lineage OS, TWRP, Magisk , Back to Stock, Frustration, No "daily driver user" or maybe according to your needs, contribute to general knowledge, dont demand from me more than here is already here because I'm not a developer, I'm just a curious user who likes to try new things in his griffin and I have already given you more than 168 hours of trial and error with the only goal of making the process easier and more fun to you.
Now let's go to what interests us, do you have your bootloader unlocked?
If the answer is no, go here and do it or you can not continue
First we start with the files that we need to download:
Latest Lineage OS from here:
https://download.lineageos.org/griffin
[Thanks to Erfanoabdi]GSI image of your favorite flavor from here:
https://mirrors.lolinet.com/firmware/gsi/
Only type A not AB just A like ColorOS-Aonly-9-20190605-ErfanGSI.img.7z not ColorOS-AB-9-20190605-ErfanGSI.img.7z and decompress the .7z file to get the IMG file inside.
To decompress the .7z file
https://www.7-zip.org/download.html
If everything goes to hell [100% sure to happen at least once] Stock ROM and adb-fastboot-latest.rar from here:
https://forum.xda-developers.com/moto-z/development/stock-moto-z-8-0-firmware-t3805226
Thanks to @thuybang for the post and @erfanoabdi again for the needed files.
Official TWRP from here:
https://dl.twrp.me/griffin/twrp-3.3.1-0-griffin.img.html
Latest Stable Magisk from here:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Thanks to @topjohnwu
Magisk module "Device Spoofing Tool" from here:
https://forum.xda-developers.com/apps/magisk/qa-want-to-install-modules-magisk-v13-3-t3800435
Thanks to @Dreamer(3MF)
Device ID apk from here:
https://androidfilehost.com/?fid=673956719939830832
Latest Android System WebView APK from here:
https://www.apkmirror.com/apk/googl.../android-system-webview-76-0-3809-36-release/
Finally put this on favorites because you will need it for the final touch:
https://www.google.com/android/uncertified/
Only if you have all those files downloaded and placed in your PC in the folder that you want you can continue.
Now the easy way step by step if you are on Official Stock ROM:
1 - Reboot to Bootloader and flash twrp-oemasvendor-2.img you can use ADB and fastboot of the .rar adb-fastboot-latest.rar that you ¿downloaded? from the back to stock link
Use
Code:
fastboot flash recovery twrp-3.3.1-0-griffin.img.img
Hard-reboot to bootloader again, down two steps and select reboot to recovery.
2 - Already in TWRP do this:
2.1 - Wipe Data - if it gives you error go reboot and select reboot recovery and again wipe data it should have been erased without errors, back and
2.2 - Manually wipe caches, system, vendor, data, internal storage
2.3 - Do "Swipe to Factory Reset" probably not necessary but for me it works.
3 - Now connect your Griffin and copy the Lineage OS ROM downloaded [obviously still inside of TWRP]
3.1 Go to Install and select the copied Lineage ROM and then install
3.2 Finished the installation restart and skip all startup, now in the launcher screen shutdown your griffin
4 - Power on your griffin again in bootloader, two steps down and select reboot recovery again.
4.1 - Now in TWRP copy the GSI type A image that you downloaded [MIUI, ColorOS, OneUI, Pixel, Flyme OS, etc)
4.2 - Allready copied go to Install and select "Install Image"
4.3 - Now you see the .IMG file, select and then flash as "System" and go let finish, clear cache and restart to System.
5 - Be very patient, you will see the warning image for having your bootloader unlocked for 5 to 10 seconds [may vary] then you will see the start animation according to the GSI image that you will select before, again be very patient it can take 3 to 15 minutes to your griffin to start completely (MIUI 3-5 minutes, Pixel 3-5 minutes, OneUI 5-10 minutes, Flyme 15 to 20 minutes in my experience) If you see that the start animation reduces its brightness after a few minutes, it means that we are on the right track wait a little longer.
5.1 - Finally we start system we enter directly without previous configurations (configure wifi, google account, PIN, etc) just start screen now go to step 6, if not then go here:
If everything goes to hell [100% sure to happen at least once] Stock ROM and adb-fastboot-latest.rar from here:
https://forum.xda-developers.com/moto-z/development/stock-moto-z-8-0-firmware-t3805226
Thanks to @thuybang for the post and @erfanoabdi again for the needed files.
And start again
6 - Ok you are one of those who managed to install and start their GSI image and you dont have google services enabled and your griffin is not certified you probably have app errors that crash infinitely [if they are 1 or 3 - example the camera] manage to go to app administration in the ROM and cancel auto-start of that apps, instead if you have so many apps errors that dont let you move anything in the interface you need to go to TWRP and clean davlink cache and cache and reboot.
That's why this step is important
Code:
4.3 - Now you see the .IMG file, select and then flash as "System" and go let finish, [B][COLOR="Red"]clear cache and restart to System
[/COLOR][/B].
7 - Now Root your griffin with Magisk, you know how otherwise I dont know how you got here
8 - Already in system, install the "Device Spoofing Tool" magisk module and reboot to activate the module.
9 - Again already in system, install Device ID APK
9.1 - Open Device ID app and find your device’s GSF (Google Service Framework) Device-ID
9.2 In your PC go HERE and use your GSF to register and certify your griffin
10 - Now install Android System WebView APK
10.1 - Go to TWRP again and clean cache one more time and reboot to system
11 - Configure your google account and be happy
11.1 - Camera its a common fail, use Gcam or Snapdragon Camera instead of GSI stock camera app
12 - Enjoy your griffin :highfive:
Well that's all from me and remember if something goes wrong or it does not work you can always go here:
If everything goes to hell [100% sure to happen at least once] Stock ROM and adb-fastboot-latest.rar from here:
https://forum.xda-developers.com/mot...mware-t3805226
Thanks to @thuybang for the post and @erfanoabdi again for the needed files.
The 99.99999999 percent of all this, maybe more, it's thanks to @erfanoabdi If you want to thank someone, buy a coffee for him.
Screenshots (sorry just from MIUI with my emotion I forgot to save from the other GSI that I proble) I feel comfortable with MIUI and now it is my ROM-GSI of daily use in my griffin (I really love taking screenshot with my three fingers )
https://ibb.co/bmDkRrz
https://ibb.co/HX3mghC
https://ibb.co/10jGLNr
https://ibb.co/jz6njXm
https://ibb.co/vv1Nr2F
https://ibb.co/9Gr29nv
https://ibb.co/qsZ2pFD
https://ibb.co/948H110
https://ibb.co/42nXM72
https://ibb.co/Jd73QwC
https://ibb.co/vVs15Hq
https://ibb.co/MVfptZ5
https://ibb.co/SywLwrW
https://ibb.co/ZXvg0QG
https://ibb.co/z8DF8L1
https://ibb.co/bBv1wxW
https://ibb.co/09nBnHW
Finally dont be mad with my english, itis very bad and I use translator
Thanks for guide, very cool
Official TWRP is updated with treble support BTW
Nice ,thanx to your contributions.
whats the waiting time for the moto image? ive installed the moto image, and still waiting for the device to bootup. its been about 15 mins
---------- Post added at 07:46 PM ---------- Previous post was at 07:25 PM ----------
after installing the image, im stuck on this (device will boot in 5 seconds screen) Can i boot back into recovery, and re install the image? its been more than 30 mins on this screen
Pixel image is the only one I managed to boot, but couldn't get gsf id from it, and it constantly force closed (cache was cleaned) and couldn't make it work at all. Moto image just gives black screen, all other images couldn't even be installed (either error in twrp or something else.) I'll try miui image one of these days, but would really like to try to make pixel image work, but without gsf id it's impossible
EDIT: Changed twrp to twrp-oemasvendor-2.img version, and managed to boot miui (but after magisk it bootlooped) and to start booting moto GSI images (moto bootloops), and just tried to boot pixel images, will see later... but I think that the problem was that twrp uses cache as vendor partition, and deleting cache, well, deletes vendor partition (will need clarification from @erfanoabdi on this)...
Can we flash the GSI over other Custom ROMs like the OMNI instead of Lineage...?
anwesh said:
Can we flash the GSI over other Custom ROMs like the OMNI instead of Lineage...?
Click to expand...
Click to collapse
Nop, Omni does not have the type of partition needed
After following this guide, I am able to boot into system (only with Pixel or MIUI GSI), but SIM is not getting detected. Frequent app crashes are also observed. Cache and dalvik are being cleared before booting...
Do I still need to follow this How to make GSI...?
But LOS 16 seems to flash vendor image, isn't it...?
What am I missing...?
By the way, clearing vendor partition always gives me an error...
anwesh said:
After following this guide, I am able to boot into system (only with Pixel or MIUI GSI), but SIM is not getting detected. Frequent app crashes are also observed. Cache and dalvik are being cleared before booting...
Do I still need to follow this How to make GSI...?
But LOS 16 seems to flash vendor image, isn't it...?
What am I missing...?
By the way, clearing vendor partition always gives me an error...
Click to expand...
Click to collapse
Go to TWRP and make full wipe factory, that fix the problem
I've been hunting down and trying out some different gsi's. With the latest twrp + los16 installed I've had success with some from this list
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
AOSP 10 with gapps included
Msm xtended gapps included
Blissrom + gapps
Aosip + gapps
EvolutionX gapps included
DU13 + gapps (not on list but works)
If installing gsi's without gapps included, let it boot first then reboot TWRP and install gapps + magisk if you want root.
Available kernel ?
I cannot retrieve the GSF id, how can I fix this?
Flashed OneUI GSI but it's stuck on the boot logo
So on my Moto Z running LineageOS 17, I can't launch Netflix on it. Will Treble-ing my Moto Z fix that problem?
This also works on moto z force?
DISCLAIMER: First off, I'm not a dev; I'm someone with a lot of time to spare that's trying to save quite a few headaches to people that don't like MIUI. If you're actually one of the talented people that worked on this stuff and don't like seeing your work shared here, just hit me up.
Secondly, all of this has been tested on my Mi 9 Lite. I can't guarantee it'll work on other variants such as the meitu edition or the Mi CC9, but then again I can't see why it wouldn't.
Lastly, please take all your due precautions before doing this: take your backups, be sure to have a plan in case anything goes wrong, the whole deal.
INSTRUCTIONS:
0) Unlock your bootloader and flash Brigudav's TWRP;
1) Format your data partition. This is mandatory, you need to get rid of the encryption!
2) Download and flash the latest Unofficial LineageOS 16 by gringo80. Compared to the xiaomi.eu build that I recommended before, the Vendor from LOS enables the use of the wide angle lens in GCam, Hypercam and ANXCamera.
3) Reboot into TWRP without booting into system; this ensures that the System partition is properly mounted before proceeding;
4) Under "Advanced Wipe", select the Cache, Dalvik, Data and System partition, but don't select "Vendor". Wipe them;
5) Download the A/B HavocOS 2.9 GSI, extract it and place the .img file into your phone's storage;
6) Under "Install", press "Install image file", select the GSI and flash it into the System partition;
7) Flash the nano OpenGapps (ARM64) package for Android 9.0;
7a) If you get an error that says that the System partition is too small, follow these steps: Wipe > Advanced Wipe > Select the System partition > Repair or Change File System > Resize File System. Flash the GApps package again and it should work;
8) Boot the phone, set it up and enjoy!
8a) If you need root, once you've passed the initial setup simply reboot into TWRP and flash Magisk 20.1.
GSIs' COMMON PROBLEMS AND FIXES:
To get Viper4Android working, install the V4A 2.7 apk from XDALabs, flash the GSI Enabler Magisk Module;
If your FOD is slow or inaccurate, set up the same finger twice;
To get ANXCamera working, be sure that the "ro.product.device" string's value in your build.prop file is set to "pyxis" and to have downloaded the "139.PastAdorableHawaiianmonkseal" build.
If you use Titanium Backup to restore your apps, the restoring process might get stuck on certain apps (for instance, Solid Explorer, Sound Cloud, Google Photos and so on). To fix this, simply go to the Play Store and manually download the app. Once it finishes installing, the backup will resume automatically;
To fix the Bluetooth audio in-call not working, flash this Magisk module.
BUGS:
DT2W doesn't work;
You might experience a slightly worse cellular reception depending on your phone's model;
That's... pretty much it!
STUFF THAT WORKS EVEN THOUGH I TOTALLY EXPECTED IT TO FAIL:
EdXposed (SandHook). If you experience sporadic SystemUI crashes, it's Gravity Box's fault;
The Screen OC Mod posted by @HelloRickyLee. I use the 72Hz dtbo file, since everything above that freezes my phone once I press the power button, but hey! Not complaining!
And that's pretty much it.
Enjoy!
Credits: The HavocOS team; xiaomi.eu team; @gringo80, @brigudav,
I already dont use DT2w, so tempted to try this once my waiting time is over thanks!
I am using this Rom from yesterday and I am very surprised because it is working prety well.
Just two or three bugs that I can live with.
Almost all personalizations of Havoc are operative.
Right? I was genuinely surprised at how well GSIs work, I'm glad I'm not the only one thinking so. I'll try to keep the post updated in the case of new builds being released, but since HavocOS 3.0 is already out in fairly sure that the one I linked in the OP is the final build.
Failure to get the rom out. Loops on screen where says MI.
Offline charging works?
Sent from my Mi 9 Lite using Tapatalk
has point 7a in OP any negative effects, when I switch to los17 or miui roms?
JimmyBondi said:
has point 7a in OP any negative effects, when I switch to los17 or miui roms?
Click to expand...
Click to collapse
Not for me. I've since switched to LOS17.1 (and tried a couple of MIUI-based ROM for good measure) and I've never had any issues.
WARNING
Author of this guide won't be responsible for damages that occur to your device
Proceed at your own risk
Overview-
After reading excellent guide by @SirCDA - Guide Link ,
I have tried several GSI's for our phone GT NEO 2 and in
this post I am sharing which GSI worked for me .
Requirements-
1) Backup All data , Internal storage will be wiped !
2) Use latest adb and fastboot binaries - Link
3) Enable USB Debugging
4) Bootloader should be unlocked - Link
5) TWRP installed (by @SathamHussainM - Link )
first connect phone to pc by usb cable
6) Empty vbmeta files by @SirCDA - Link )
Instructions-
Follow Guide from here ,
Basically you have to reboot to fastboot mode using adb or by going to TWRP and in reboot section selecting fastboot mode
after that flash vbmeta files
Then erase system partition by using command fastboot erase system
Then flash the downloaded GSI using fastboot flash system gsileos.img
It will take some time after that
Wipe all data using command fastboot -w
Then reboot to sysem using fastboot reboot command
List of Working GSI
1) LeOS Arm64 A/B Android 11 - reported by me
Boots =YesWorking = Calling(on 2g and 3g),Camera,GPS,Bluetooth,Wifi&Hotspot,FaceUnlock(with third party app)Bugs= Volte,Fingerprint ,Fast Charging , and some minor bugs
2) Havoc Os Arm64 A/B Android 11 - reported by me
Boots =NoWorking=NABugs= NA
3) Ancient OS Arm64 A/B Android 11 - reported by @SirCDA
Boots =YesWorking=Camera,GPS,Bluetooth,Wifi&Hotspot,Bugs=Not Reported
4)Ancient OS Arm64 A/B Android 12 - reported by me
Boots = NoWorking=NABugs= NA
5) crDRom11 Arm64 A/B Android 11 - reported by me
Boots = YesWorking=Calling(on 2g and 3g),Camera,GPS,Bluetooth,Wifi&Hotspot,FaceUnlock,Fingerprint(enrollment takes time to detect finger press slightly harder)Bugs= VOLTE and Fast Charging
LeOs Tips
Use Signal as SMS app for working Messaging ,Dont try to enroll fingerprint , it make system UI crash ,
Only use this Magisk if you want to root it else other magisk will cause system to hang at bootanimation .Follow this guide to get supefast face unlock Click HereUse LeOS laucher instead of Trebutchet Launcher since it has many customistaions .Enable Devloper mode and inside that setup Smallest Width as 392 and Display Cutout as Punch Hole Cutout .Customise your OS from these settings - Settings> Display>Styles and Wallpapers and Setting>System>Buttons , Status Bar and GesturescrDRom11 Tips
Use Signal as SMS app for working Messaging ,Be patient while enrolling fingerprint , use thumbs and make whole area of thumb connect with screen at the light green spotOnly use this Magisk if you want to root it else other magisk will cause system to hang at bootanimation FaceUnlock is included by default and it worksEnable Devloper mode and inside that setup Smallest Width as 392 and Display Cutout as Punch Hole Cutout Many customisations available in crDroid settings.Screenshots attached in this post
Thanks to @SirCDA for his guide from which I understood that you need to flash empty vbmeta files else phone will directly boot to fastboot mode only.
Thanks to @phhusson for making tools that allow GSI to work properly
Thanks to @harvey186 for making LeOS .
I also tried
Havoc OS Android 10 Arm64 A/B but that did not boot .
Ancient OS Android 11 Arm64 A/B but that did not boot .
RMX3370 said:
I also tried
Havoc OS Android 10 Arm64 A/B but that did not boot .
Ancient OS Android 11 Arm64 A/B but that did not boot .
Click to expand...
Click to collapse
Ancient OS Android 11 on mine it started normal
SrCDA said:
Ancient OS Android 11 on mine it started normal
Click to expand...
Click to collapse
Please also mention the bugs and exact ROM name
RMX3370 said:
Please also mention the bugs and exact ROM name
Click to expand...
Click to collapse
AncientOS-R-Society-v5.4_arm64_AB_bvN-IRON
Updated OP , currently the least buggy working GSI is crDrom11 with only two recognised bugs VOLTE and Fast Charging
I've tried the following roms:
https://sourceforge.net/projects/ancientrom/files/gsi/V6.2/AncientOS-S-Shield-v6.2-arm64_bgN-Steel-20220417.img.xz/download
https://builds.haridhayal.workers.dev/ProtonAOSP/2022_03_24/proton-12.3.0-2022_03_24-vndklite-arm64_bgN.img.xz
Haven't tried phone functions cause don't have a second sim card.
AncientOS have no fingerprint and face unlock. For face unlock there is the option but cannot detect the face. With magisk v24.3 there is no way to pass safetynet. On this one I've also copied my apps and settings from my previous phone and haven't found any malfunctions.
Proton also have no fingerprint and face unlock options into settings. After installing magisk v24.3 the system broke. It boots but the launcher sometimes works sometimes no. Settings app not opening and some other apps crashes (com.android.phone, etc). I've tried this for just a fews minutes so probably there is a solution for magisk but I don't like the rom and lack of personalization so no more testing for me..
For both roms the recovery is partially broken. /data and /cache partitions are inaccessible. Even if I format them, after a normal boot the partitions are broken again.
Also if the brightness is reduced to zero it completely disables the screen but the touch continues to work.
I think I'll try corvus as the next rom.
@maxysoft @RMX3370 crDroid Android 11, works fingerprint reader and face unlock
SrCDA said:
@maxysoft @RMX3370 crDroid Android 11, works fingerprint reader and face unlock
Click to expand...
Click to collapse
I had already added it to working list (I tried them on 20 but was not having enough free time to update OP)
maxysoft said:
I've tried the following roms:
https://sourceforge.net/projects/ancientrom/files/gsi/V6.2/AncientOS-S-Shield-v6.2-arm64_bgN-Steel-20220417.img.xz/download
https://builds.haridhayal.workers.dev/ProtonAOSP/2022_03_24/proton-12.3.0-2022_03_24-vndklite-arm64_bgN.img.xz
Haven't tried phone functions cause don't have a second sim card.
AncientOS have no fingerprint and face unlock. For face unlock there is the option but cannot detect the face. With magisk v24.3 there is no way to pass safetynet.
Proton also have no fingerprint and face unlock options into settings. After installing magisk v24.3 the system broke.
I think I'll try corvus as the next rom.
Click to expand...
Click to collapse
Please also comment if VOLTE works oon these ROMs by trying to open any webpage while on a call
RMX3370 said:
WARNING
Author of this guide won't be responsible for damages that occur to your device
Proceed at your own risk
Overview-
After reading excellent guide by @SirCDA - Guide Link ,
I have tried several GSI's for our phone GT NEO 2 and in
this post I am sharing which GSI worked for me .
Requirements-
1) Backup All data , Internal storage will be wiped !
2) Use latest adb and fastboot binaries - Link
3) Enable USB Debugging
4) Bootloader should be unlocked - Link
5) TWRP installed (by @SathamHussainM - Link )
first connect phone to pc by usb cable
6) Empty vbmeta files by @SirCDA - Link )
Instructions-
Follow Guide from here ,
Basically you have to reboot to fastboot mode using adb or by going to TWRP and in reboot section selecting fastboot mode
after that flash vbmeta files
Then erase system partition by using command fastboot erase system
Then flash the downloaded GSI using fastboot flash system gsileos.img
It will take some time after that
Wipe all data using command fastboot -w
Then reboot to sysem using fastboot reboot command
List of Working GSI
1) LeOS Arm64 A/B Android 11 - reported by me
Boots =YesWorking = Calling(on 2g and 3g),Camera,GPS,Bluetooth,Wifi&Hotspot,FaceUnlock(with third party app)Bugs= Volte,Fingerprint ,Fast Charging , and some minor bugs
2) Havoc Os Arm64 A/B Android 11 - reported by me
Boots =NoWorking=NABugs= NA
3) Ancient OS Arm64 A/B Android 11 - reported by @SirCDA
Boots =YesWorking=Camera,GPS,Bluetooth,Wifi&Hotspot,Bugs=Not Reported
4)Ancient OS Arm64 A/B Android 12 - reported by me
Boots = NoWorking=NABugs= NA
5) crDRom11 Arm64 A/B Android 11 - reported by me
Boots = YesWorking=Calling(on 2g and 3g),Camera,GPS,Bluetooth,Wifi&Hotspot,FaceUnlock,Fingerprint(enrollment takes time to detect finger press slightly harder)Bugs= VOLTE and Fast Charging
Click to expand...
Click to collapse
Hey, crdroid a11 gsi volte isnt working???
akgosai96 said:
Hey, crdroid a11 gsi volte isnt working???
Click to expand...
Click to collapse
Nope, not working on any GSI
Automated GSI flashing tool for Redmi Note 11 (spes)
I WON'T GIVE SUPPORT TO THOSE WHO FACE ISSUES BY NOT READING THE STEPS BELOW CAREFULLY!
I will get right into the topic here, find the answers to your questions below at near the end.
What this tool does:
1. Flash a GSI to your Dynamic partitioned Note 11
2. Patch your Vbmeta
3. Patch Product for magisk flashing
How to use this tool:
0. Flash a rom (stock rom, MIUI EU, AOSP, ...) - IMPORTANT
1. Download your GSI and the tool, extract them
2. Copy your GSI image to the tool's folder, rename the GSI to system.img if you are using Windows
3. Boot your phone to fastboot mode and plug it in
4. Run the "windows.bat" or "macos.sh" script based on your os
5. Wait until the process finishes, your phone will automatically reboot
Download: See attached file
Extras:
A ROM collection Telegram channel of mine, you can see screenshots of GSIs I booted on Note 11 by searching it there
The original post on Telegram
Credit:
kusti420 for Product file
AnhNotAnh (me) for the tool ofc
Main Q&A:
Q: What is a Generic System Image, GSI?
A: A GSI is a prebuilt system image that can be booted on devices that support Project Treble. In short, this System Image is a custom ROM but it uses your Vendor, Kernel from your previous/stock ROM.
Q: Okay, but why I would like to flash it on my Redmi Note 11?
A: As we have already known, MIUI does not perform exactly well in the recent years, especially on such a low end and underpowered phone. GSI helps us getting a taste of AOSP's cleanliness and smoothness before the developers finish making actual custom ROMs. This is a temporary solution, good enough to use, please don't think or complain if your GSI perform badly, since it is not a ROM or trying to be one either.
Q: Why do we need a dedicated tool and such time wasting thing to do? Can't you just flash it in a custom recovery?
A; From Android 10, devices with it come equipped with a new partition scheme, as known as Dynamic Partition. It helps speeding up OTA updates and make the partitions more flexible in size. But also creates a huge difficulty in flashing those GSI, that is why you cannot flash the image in a custom recovery.
Q: My terminal window freezes at a certain progress for too long! What should I do?
A: This case often happens with Windows users. Everything is quite complicated BTS, but the workaround is just spamming Enter key several times every minute or two.
Q: What if I want to install a GSI on top of another one? I already flashed one, do I need to restore my MIUI or AOSP rom to flash GSI?
A: It is not necessary, you can flash a new GSI on top. The tool will clear your previous GSI without erasing required stuff from ROM.
Q: My GSI does not boot, what should I do??
A: I highly suggest using GSIs based on Phh's work. Those are often called Phh GSIs. Secondly I would highly suggest against using "Ported GSIs", those are often based on Erfan or Xiaoxindada's GSI tool, they are a port from a different device's ROM instead of directly built from source like Phh. Here is a list of GSIs based on the man himself, Phh.
Q: Bro my phone just boot to TWRP and nothing happens, computer still waits for my device??
A: Like I said before, you can try spamming Enter key. It is also likely that your TWRP does not support Fastbootd (Fastboot Dynamic) environment, an easy workaround for this is using MIUI's boot (kernel) image, stock Fastbootd mode will be used.
Q: Which Android version can I flash??
A: You can flash corresponding or NEWER Android version GSI with the ROM you are coming from/installing GSI on top, you cannot flash a lower version one. For example, you can flash Android 11, 12, 12.1, 13, bla bla GSIs when coming from stock Android 11 MIUI ROM (Android 11 Vendor for people who understands)
Q: Can I use this tool on another device?
A: Yes, with proper bringup and changes in the tool for it to compatible with your device and it will work. But I will not be responsible for bricks, which I always won't xD
More questions and answers will be updated later.
Reserved.
Thanks for this Awesome Tool. Quiet Simple and efficient.
@PingVN This script works on Xiaomi redmi note 11 4g codename selene?