Original thread.
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here 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.
* Your warranty will be void if you tamper with any part of your device / software. *This is not entirely true for Realme devices since bootloader unlock or custom rom flash via TWRP or fastboot does not void your warranty but rooting does.
* So I heard. But that's question of detail.
* Same statement for XDA.
[DETAILED DESCRIPTION]:
I've spent my whole afternoon testing. And found out there are way more well made gsi roms out there and theoretically all of them should work. First, you gotta read this one. Then pick a gsi rom. I recommend one that has everything (must be AB image) since we don't have a working twrp yet thus can't flash opengapps but if the image file contains it then it's good to go. Go there. Pick one. Make sure it has ab-gapps-su in it's name meaning it's A/B partition dependent treble rom. Gapps means it has gapps ofc. Su means it has built in superuser (that you can ignore later for you'll be replacing it with Magisk naturally). After picking a gsi rom image successfully you can download it to your external sd card and flash it via twrp (yes, that half ass twrp for rmq provided on xda) or you can flash it via fastboot flash system system.img. Wiping data, cache, dalvik, system is necessary before doing so. Also formatting data in twrp after flashing the system image helps a lot just as OP said. If you want to try out other gsi roms you must flash stock vendor image file and do the flashing circle again. If you don't flash stock rom or stock vendor img before doing so your new gsi rom won't be able to work with screen lock. At least that's what I got on 4 different gsi roms. And one more thing. These gsi systems doesn't seem to support exfat file system. Meaning they'll want to format your external sd card. This can by bypassed if you flash lineage os boot.img. And then Magisk and at last modified vbmeta.img for RMQ. That file will make realme vendor think nothing is changed and won't try to fck you over with recovery destroyed issue.
[Prerequisites]:
unlocked bootloader
twrp recovery
External SD card
[BUGS]:
Face unlock and fingerprint isn't present on gsi roms which means they cannot work
Screen lock issue in cases when you don't flash stock vendor.img before migrating from one custom rom, be it gsi or zip to system gsi.img
[STEP BY STEP TUTORIAL IN CASE YOU'RE COMING FROM OTHER ROM]:
!! Most of these steps are precaution !!
Read these points carefully to have a basic knowledge what you're about to do
Pick a gsi image of your choice (official Android 9 Pie, especially AOSP is highly advised)
Put your image file onto your external SD card for your internal one will likely be erased
You should grab the appropriate vendor.img and boot.img files for your device by decompressing the 7z files
Get the modified vbmeta.img file for spoofing system to boot
Get Magisk
Get SuperSu remover(Beware! It also removes Magisk if installed)
Get Lineage OS boot.img
It's better to be safe than sorry so you better download whole rom package too
Put all these files onto your external SD card
Make sure you have your twrp recovery on your external SD card too
If you done everything well you should have these on your external SD: twrp, desired system gsi.img as AB variant, your vendor.img, modified vbmeta.img, stock boot.img, Lineage OS boot.img, color os flashable.ozip/zip, Magisk, SuperSu remover
Wipe system, data, dalvik, cache
Flash stock vendor.img as vendor
Flash system gsi.img as system
Flash lineage os boot.img as boot
Flash twrp.img as recovery
Flash modified vbmeta.img as vbmeta
Reboot to system (if the device reboots into recovery you'll have to format data sadly)
After reboot successful and you've done the initial google setup steps reboot to recovery and flash superuser unroot
Flash Magsik
Reboot, now you should have a working aosp like system as I do
[STEP BY STEP TUTORIAL IN CASE YOU'RE COMING FROM COLOR OS]:
!! You could have the same files as above just to make sure but system gsi.img,vbmeta.img,SuperSu remover,Magisk and Lineage OS boot.img should be enough if everything goes as planned and system boots for first try !!
Read the frequently asked questions, step one previously
Get your desired system gsi.img
Put your system gsi.img, twrp.img, Magisk, SuperSu remover, vbmeta.img, Lineage OS boot.img onto your external SD card
Wipe data, system, cache, dalvik
Flash system gsi.img as system
Flash lineage os boot.img
Flash twrp.img as recovery
Flash vbmeta.img ad vbmeta
Reboot (if reboots to recovery you have to format data) then do the Android setup
Reboot to recovery
Flash SuperSu remover.zip
Flash Magisk.zip
Reboot
Now your device should have successfully booted up
In case the gsi rom would be stuck on boot logo then you may reboot back to recovery by holding down volume up + power button and flash permissiver_v5.zip. It helped me boot Pixel Experience gsi rom.
Update.:
As you already know development on realme devices suck beacuse of ****ty or incomplete sources, lack of developers interest and biggest reason is lack of community support.
Our man here @BabluS is a legendary developer of Asus Zenfone Max M1 Pro and is willing to compile stable ROMs for our device. But, he needs some donations to buy the device. He has already compiled Android 10 (PE) for our device which is 99% stable. To continue this tremendous work he needs to have the device in hand.
Reasons To Donate:
1. Official PixelExperience ROM
2. Official POSP ROM
3. Will maintain & provide public Device Trees/Sources (So anyone can compile ROMs)
4. More development for realme 5 Pro
Name : Baswanth Madhav Saladi
Donate Using UPI: [email protected]
Donate using Paypal : [email protected]
Send screenshots of payment to @orgasmtron
We have to reach 6-7k in total out of which we have collected 2.6k..
Keep donating & get closer to stable custom ROM experience. Kudos!
All the donations will be public.Anyone can view and verify them.All details will be transparent.
NOTE:
We will update money collection daily evening. All details will be transparent.
List of Donators will get updated here
CLICK HERE TO CHECK!
Has anybody got Android 10 working properly?
tonibm19 said:
Has anybody got Android 10 working properly?
Click to expand...
Click to collapse
Yes. Method is same.
greenys' said:
Yes. Method is same.
Click to expand...
Click to collapse
Yeah but I mean, everything is working fine?
Fingerprint? Camera?
tonibm19 said:
Yeah but I mean, everything is working fine?
Fingerprint? Camera?
Click to expand...
Click to collapse
Dunno. As I said I never tried Android Q. But I presume fingerprint is missing and I'm quite sure no 48mp camera is present either.
What GSI File for Realme 5 Pro
what type GSI Image for Realme 5 pro, A or AB type?
Tegarcs142 said:
what type GSI Image for Realme 5 pro, A or AB type?
Click to expand...
Click to collapse
AB. On Android 9 and above you must use AB variant. It doesn't matter whether or not does your device use seamless updates. If you try to flash A only variant your device won't boot.
I installed GSI resurrection remix on my Realme 5 Pro and when I trying install Gapps get error not enough system partition. So I use resize file system in twrp and it worked.
Tegarcs142 said:
I installed GSI resurrection remix on my Realme 5 Pro and when I trying install Gapps get error not enough system partition. So I use resize file system in twrp and it worked.
Click to expand...
Click to collapse
Nice. Which twrp did you use?
greenys' said:
Nice. Which twrp did you use?
Click to expand...
Click to collapse
3.3.1-0
Tegarcs142 said:
... So I use resize file system in twrp and it worked.
Click to expand...
Click to collapse
Hi, can you please tell me what option you clicked for resizing the system partition?
the steps you did.
I tried doing that but don't find the option in TWRP.
For better experience with using gsi make sure to check Screenshot resolution if it's lower than our Device
Change Resolution :
1) download termux app
https://play.google.com/store/apps/d...?id=com.termux
2) run commands:
su
wm size 1080x2340
3) reboot*device
Enjoy better experience with gsi
greenys' said:
Original thread.
[DETAILED DESCRIPTION]:
I've spent my whole afternoon testing. And found out there are way more well made gsi roms out there and theoretically all of them should work. First, you gotta read this one. Then pick a gsi rom. I recommend one that has everything (must be AB image) since we don't have a working twrp yet thus can't flash opengapps but if the image file contains it then it's good to go. Go there. Pick one. Make sure it has ab-gapps-su in it's name meaning it's A/B partition dependent treble rom. Gapps means it has gapps ofc. Su means it has built in superuser (that you can ignore later for you'll be replacing it with Magisk naturally). After picking a gsi rom image successfully you can download it to your external sd card and flash it via twrp (yes, that half ass twrp for rmq provided on xda) or you can flash it via fastboot flash system system.img. Wiping data, cache, dalvik, system is necessary before doing so. Also formatting data in twrp after flashing the system image helps a lot just as OP said. If you want to try out other gsi roms you must flash stock vendor image file and do the flashing circle again. If you don't flash stock rom or stock vendor img before doing so your new gsi rom won't be able to work with screen lock. At least that's what I got on 4 different gsi roms. And one more thing. These gsi systems doesn't seem to support exfat file system. Meaning they'll want to format your external sd card. This can by bypassed if you flash lineage os boot.img. And then Magisk and at last modified vbmeta.img for RMQ. That file will make realme vendor think nothing is changed and won't try to fck you over with recovery destroyed issue.
[Prerequisites]:
unlocked bootloader
twrp recovery
External SD card
[BUGS]:
Face unlock and fingerprint isn't present on gsi roms which means they cannot work
Screen lock issue in cases when you don't flash stock vendor.img before migrating from one custom rom, be it gsi or zip to system gsi.img
[STEP BY STEP TUTORIAL IN CASE YOU'RE COMING FROM OTHER ROM]:
!! Most of these steps are precaution !!
Read these points carefully to have a basic knowledge what you're about to do
Pick a gsi image of your choice (official Android 9 Pie, especially AOSP is highly advised)
Put your image file onto your external SD card for your internal one will likely be erased
You should grab the appropriate vendor.img and boot.img files for your device by decompressing the 7z files
Get the modified vbmeta.img file for spoofing system to boot
Get Magisk
Get SuperSu remover(Beware! It also removes Magisk if installed)
Get Lineage OS boot.img
It's better to be safe than sorry so you better download whole rom package too
Put all these files onto your external SD card
Make sure you have your twrp recovery on your external SD card too
If you done everything well you should have these on your external SD: twrp, desired system gsi.img as AB variant, your vendor.img, modified vbmeta.img, stock boot.img, Lineage OS boot.img, color os flashable.ozip/zip, Magisk, SuperSu remover
Wipe system, data, dalvik, cache
Flash stock vendor.img as vendor
Flash system gsi.img as system
Flash lineage os boot.img as boot
Flash twrp.img as recovery
Flash modified vbmeta.img as vbmeta
Reboot to system (if the device reboots into recovery you'll have to format data sadly)
After reboot successful and you've done the initial google setup steps reboot to recovery and flash superuser unroot
Flash Magsik
Reboot, now you should have a working aosp like system as I do
[STEP BY STEP TUTORIAL IN CASE YOU'RE COMING FROM COLOR OS]:
!! You could have the same files as above just to make sure but system gsi.img,vbmeta.img,SuperSu remover,Magisk and Lineage OS boot.img should be enough if everything goes as planned and system boots for first try !!
Read the frequently asked questions, step one previously
Get your desired system gsi.img
Put your system gsi.img, twrp.img, Magisk, SuperSu remover, vbmeta.img, Lineage OS boot.img onto your external SD card
Wipe data, system, cache, dalvik
Flash system gsi.img as system
Flash lineage os boot.img
Flash twrp.img as recovery
Flash vbmeta.img ad vbmeta
Reboot (if reboots to recovery you have to format data) then do the Android setup
Reboot to recovery
Flash SuperSu remover.zip
Flash Magisk.zip
Reboot
Now your device should have successfully booted up
In case the gsi rom would be stuck on boot logo then you may reboot back to recovery by holding down volume up + power button and flash permissiver_v5.zip. It helped me boot Pixel Experience gsi rom.
Click to expand...
Click to collapse
Hi
I wanna install fortnite on RMQ
Through epic games I should register a realme account (but I can do that only with a Chinese phone number which I don't have )
Any solution pls
Tarikooo said:
Hi
I wanna install fortnite on RMQ
Through epic games I should register a realme account (but I can do that only with a Chinese phone number which I don't have )
Any solution pls
Click to expand...
Click to collapse
Wth no. Idk. It's not even a gsi related thing. I have no idea sorry.
hi guys i tried flashing havoc 3.0 gsi, and it works great. which one gapps should i use?
Does fingerprint and face unlock work?
This method worked on global rm5p.
I tried to flash the GSI Miui Erfan, but when entered in the initial settings, the screen cannot be touched.
Salmankapuas said:
I tried to flash the GSI Miui Erfan, but when entered in the initial settings, the screen cannot be touched.
Click to expand...
Click to collapse
Don't bother with miui. Only aosp or caf.
i flashed GSI rom, pixel, OxygenOS but the system cannot boot, only stuck on boot loading screen, is that normal?? how do i fix it?
Hi There!
I come to you with a request for help. Well, I wanted to install the GSI system straight from the Google website, but during the installation it turns out that my system partition is definitely too small.
Is there any way to properly install the IMG image straight from the Google site? Probably should enlarge the system partition, just HOW? I need the help of experts, and I know that at the XDA Forum I will find them.
Below you will need information:
- My device is Google Pixel XL (marlin),
- My phone supports Treble A and B updates,
- The system I wanted to install was the beta GSI Android 11 straight from the Google website,
- The recovery I used when trying to install the system: twrp-3.4.0-0-marlin.img from TWRP site,
- I also tried to install the system using CMD with ADB and fastboot,
- I have fastboot unlocked on my device,
- Information about too small partition also occurs when trying to install GSI Android 10,
- My device does not support fastbootd,
- LineageOS ZIP packages work normally and install without any errors,
- Updates from ADB sideload also load smoothly,
- Here is the link from where I got GSI Android 11 and 10: https://developer.android.com/topic/generic-system-image/releases#android-gsi-11,
I'm trying this also, credited the error to the system partition on marlin being 2gb and the system img on Google GSI being 2.1gb.
I know there's also an AOSP GSI which i downloaded from the same Google website and the image is 1.3gb if I'm not mistaken. I was able to flash this but phone wont boot. It will just bootloop on the Google with white background image and that's it.
I also tried downgrading to Android 8.1 factory image since I heard that another user got GSI Android 11 working coming from 8.1 but after trying this way I got the same bootloop error.
Solution
I was able to install Android 10 GSI on my Pixel, this method should work. You just need to reflash Android 9, see: https://forum.highonandroid.com/t/how-to-flash-android-10-gsi-roms-on-pixel-or-pixel-xl/217
I spent hours trying to figure this out but worked.
What happend:
I bought a used Mi A2 lite with stock Android 8. Because i already used LineageOS and really love it, i want to continue to use it.
I did the flashing process a few times wrong. After the help of a very kind user i did it as it was supposed to be.
mustaphakosar said:
Let me sum up the process which will probably answer your all questions.
Once you opened the bootloader and flashed TWRP image successfully and saw TWRP screen on your phone, unplug it from PC.
IF you will install a custom rom, than
1- format data, type 'yes'. Reboot to recovery
2- advaanced wipe( everyting except sd card) (ı assume you should have put custom rom file and twrp.installer.zip to your sd card)
3- install custom rom and twrp.installer.zip(choosing to upload from your sdcard, you will be able to see them)
4- go back. Press "reboot" but don't reboot anything. From reboot menu, change slot(if you're at slot 'a', change your slot to 'b', vice versa)
5- now you can press reboot to recovery.
6- once recovery(twrp) opens, you can install gapps and magisk.
7- reboot the system.
Click to expand...
Click to collapse
Doing so cause, that my Phone didn't boot the OS anymore. I could see the Android ONE bootlogo, after that the screen turned black. Phone must be still running because PC detected a device, when i connected the phone to my PC.
If i keep pressing Louder and Start i could enter recovery, with quieter i could enter fastboot.
Thankfully i discovered this thread:
never ending boot after stock ROM install
My Mi A2 Lite had stock rom v10.0.18.0, unlocked bootloader, Magisk v20.3 and TWRP using Offain v3.3.1. I wanted to try dotOS custom ROM and followed this tutorial: https://github.com/tkchn/daisyinstall I begin with step 1 installing daisy...
forum.xda-developers.com
and fixed the Phone so i can start an OS again. Now is my question, what did go wrong? What is the best way to continue from this point to flash LineageOS on my phone? Do i have to update the OS from the thread first and try it again?
Phone is still OEM unlocked.
Thank you guys in advance!
Ok i got it now. For whoever will find this in the future:
I started at the point above and updated the Stock Android 9 to the latest version.
1. Enable USB-Debugging and open Bootloader in the settings
2. Shut down Phone and start into fastboot
3. Use command: "fastbood oem unlock"
This will cause a factory reset, be aware
4. Check settings and go into fastboot again, then use command
"fastboot boot <name of your twrp image>"
Proceed this way:
GitHub - tkchn/daisyinstall: An installation guide for custom ROMs on Xiaomi Mi A2 Lite
An installation guide for custom ROMs on Xiaomi Mi A2 Lite - GitHub - tkchn/daisyinstall: An installation guide for custom ROMs on Xiaomi Mi A2 Lite
github.com
Enjoy
cross-posting from the Galaxy Tab S5e forum because getting the gapps will be the same for all devices
Installed android 12 beta GSI. any way to get google apps?
I just installed the ARM64 GSI adapting the steps from https://www.xda-developers.com/android-12-beta-gsi/ let me share: I rebooted into recovery (had twrp flashed as recovery and lineageos 18.1 as system) flashed lineageos recovery directly for...
forum.xda-developers.com
I just installed the ARM64 GSI adapting the steps from https://www.xda-developers.com/android-12-beta-gsi/
let me share:
I rebooted into recovery (had twrp flashed as recovery and lineageos 18.1 as system)
flashed lineageos recovery directly for fastbootd:
Code:
adb push /path/to/lineageos-recovery.img /cache/lineageos-recovery.img
Code:
adb shell
Code:
cat /cache/lineageos-recovery.img > /dev/block/by-name/recovery
rebooted again into recovery (to lineageos recovery)
entered fastboot mode
followed the fastboot steps in https://www.xda-developers.com/android-12-beta-gsi/
rebooted into system
and it booted! still carrying many lineageos settings since it turns out lineageos recovery ignored fastboot -w
anyway. Google apps were crashing and I thought it was because it didn't wipe user data. so I did that, rebooted, and... well, the GSI does not come with google apps. any way to get them from the Pixel's GSIs?
attaching pictures I took with my phone because the OS is super barebones without google apps so it's kinda meh and I also want you to see it's the tablet
also look at that the shining pixels effect when you hold a row and ripples. so Godly
ok I didn't see there were links with GMS and without lmao
tomatoketchup said:
ok I didn't see there were links with GMS and without lmao
Click to expand...
Click to collapse
Lmao
Hello guys. So, i want to install an unofficial lineage os to my Xiaomi redmi 6 (cereus). But th problem is the custom rom file format is img.xz and it's not detected by the TWRP recovery. I've tried to extract the img.xz into a img file. And it actually detected with the TWRP, so i tried to install it and locate the rom to System Image. It's tecnically got the rom image installed succesfully, but when i tried to boot it up, it's just got to the xiaomi logo and then it's just restarted repeatedly to the xiaomi logo again and again. So at this point, I don't know what can i do?
Note : Gapps and magisk installed without any issues because they're zip files. So i don't think the problem is in the magisk or Gapps.
Device : Xiaomi Redmi 6 ( Cereus )
TWRP Version : 3.6.2_9.0
Lineage OS ROM : Lineage OS Unofficial cereus (a64 and ab rom ) ( I got it from Andy Yan's Personal Builds SourceForge ).
NarenTheNoobFlasher said:
Hello guys. So, i want to install an unofficial lineage os to my Xiaomi redmi 6 (cereus). But th problem is the custom rom file format is img.xz and it's not detected by the TWRP recovery. I've tried to extract the img.xz into a img file. And it actually detected with the TWRP, so i tried to install it and locate the rom to System Image. It's tecnically got the rom image installed succesfully, but when i tried to boot it up, it's just got to the xiaomi logo and then it's just restarted repeatedly to the xiaomi logo again and again. So at this point, I don't know what can i do?
Note : Gapps and magisk installed without any issues because they're zip files. So i don't think the problem is in the magisk or Gapps.
Device : Xiaomi Redmi 6 ( Cereus )
TWRP Version : 3.6.2_9.0
Lineage OS ROM : Lineage OS Unofficial cereus (a64 and ab rom ) ( I got it from Andy Yan's Personal Builds SourceForge ).
Click to expand...
Click to collapse
Its Feb 2023 and I've just done EXACTLY the same thing trying to put lineageOS 20 onto a Galaxy TAB A 8..0 LTE. Hope I find a solution as my device is resting in download mode just to stop it from looping/buzzing.