Related
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?
Edit: Got it working. All I had to do was check both checkboxes on AVB 2.0 and also check both in RM Forceencrypt.
Hi! I recently tried to install a custom ROM (LineageOS, Pixel Experience, CesiumOS), but every time I tried I got stuck at boot animation.
I'm on MIUI 11 V11.0.3.0 PGGEUXM Android 9 (Should I flash V11.0.6.0 PGGMIXM Global? )
What i did:
1.Unlocked bootloader
2.Flashed factory preloader from the Megathread
3.Flashed TWRP (by wzsx150)
4.Formated Data (in TWRP) and then Dalvik, Cache and System
5.Transferred ROM and vendor.img (and Magisk 20.4) to /sdcard/ (I got vendor.img from CesiumOS thread)
6.Flashed vendor.img
7.Flashed ROM (LineageOS, Pixel Experience, CesiumOS) (and Magisk)
8.Cleared Dalvik
9.Closed AVB 2.0 (first checkbox)
10.Rebooted to system
11.Got stuck at boot animation
12.Went back to stock ROM (11.0.3.0 PGGEUXM )
13.Went to step 2 and tried another ROM
Every time I flash an official ROM I need to flash lk and preloader from the Megathread and when I deleted lk and preloader.bin from the official ROM MiFlash instantly said failure
I'd also like to add that this is the first phone that I rooted and tried a custom ROM on
I got my ROMs from here:
LineageOS - https://forum.xda-developers.com/redmi-note-8-pro/development/rom-lineageos-17-1-t4072137
CesiumOS - https://forum.xda-developers.com/redmi-note-8-pro/development/rom-cesiumos-v2-5-1-t4059543
Pixel Experience - https://forum.xda-developers.com/redmi-note-8-pro/development/rom-pixel-experience-t4059977
MIUI 11 V11.0.3.0 PGGEUXM - https://c.mi.com/oc/miuidownload/detail?device=1900375
And TWRP from here:
TWRP - https://forum.xda-developers.com/re...overy-twrp-recovery-redmi-note-8-pro-t4033695
just curious, youre clicking vendor img bubble when flashing a vendor img right? was having the same problem because i was flashing vendor img with system image..
shoeprano27 said:
just curious, youre clicking vendor img bubble when flashing a vendor img right? was having the same problem because i was flashing vendor img with system image..
Click to expand...
Click to collapse
Thanks for reply!
Yes, i was clicking that. Got it working, i just had to check both checkboxes on AVB 2.0 and also check both in RM Forceencrypt.
Hi everyone!
I've been testing installing Lineage 17.1 custom ROMs on merlin, here are the steps I followed plus a LOS 17.1.
I found out that this ROM works better than MIUI and its very stable as a daily driver.
Tested on Redmi Note 9 Global (merlin) - CPU (Helio G85) - ROM/RAM: 64GB/3GB, initialy flashed over MIUI 12.0.3 Global
This are the steps I followed:
Unlock bootloader (of course)
Backup all sensitive data (it maybe lost if things go wrong)
For you in case things go wrong, also download the exact fastboot rom of the MIUI version you are using from xiaomifirmwareupdater.com (it has to be fastboot ROM becouse it contains stock recovery)
Flash a TWRP with new MIUI kernel support
Download TWRP build by wzsx15, for example
Download a modifed vbmeta.img, like the one provided in this thread
Flash like this:
Bash:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash recovery recovery.img
Test TWRP, at least verify it can mount and read /data.
Wipe data, cache and dalvik
Flash LOS 17.1 for merlin (details below), or anything you want to test
Details about provided LOS 17.1:
LineageOS 17.1 - UNOFFICIAL | A10.
Released : 11/02/'21
By @CosmoFreak001 & @chcepizze
SElinux permissive
Changelog:
• Fixed VoLTE
• Fixed Brightness bug
• Fixed all major bugs
• Fixed Double tap to wake
• Fixed Offline Charging
Download
Source (build using generic kernel for Mediatek Helio G85)
Works at least over:
MIUI 12.0.4 Global and less
MIUI 12.0.1 Indonesia and less
--------------
⚠WARNING⚠
MIUI 12.0.5 Global (and 12.0.2 Indonesia) and any higher version, would probably need a downgrade.
--------------
In case things go wrong:
TWRP dosen't work correctly and now my system can't boot
Restore stock recovery, vbmeta and boot partition
Go to fastboot
Extract recovery.img file from your stock fastboot ROM and flash it like this
Code:
fastboot flash recovery recovery.img
Reboot, if system dosen't boot, go to next step
Extract vbmeta.img file from stock fastboot ROM and flash it like this
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Reboot, if it can't boot, go to next step
Extract boot.img file from your stock fastboot ROM and flash all (recovery, vbmeta and boot partition) it like this
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta.img
TWRP ask's me for a passoword
It's the first PIN number of the lockscreen you set when you first run the system
My PIN doesn't work or my phone never had a PIN and still asks me for one
Maybe /data is not accesible (TWRP compatibility problem)
Try mounting /system and /vendor partition
Navigate through them and verify you can see files and folder
If TWRP is unable to mount any partition restore stock recovery partition
If TWRP can see and mount partitions other than /data:
You can format /data (you are losing ALL data including internal storage)
I don't wont to lose all my data!
Restore stock recovery
Good work, Please note that the rom does not boot on every vendor version, So include the list of the vendors working for rom, As far as I know, it has booted successfully on MIUI 12.0.3 Global and 12.0.1 Indonesia.
Communos said:
Good work, Please note that the rom does not boot on every vendor version, So include the list of the vendors working for rom, As far as I know, it has booted successfully on MIUI 12.0.3 Global and 12.0.1 Indonesia.
Click to expand...
Click to collapse
Thanks. You are right I will add those comments.
thanks for this
Hello members after a long daunting minutes ,hours and days asking for the procedures in this forum on how i can install the custom rom on the Redmi note 9 Merlin MT 6768 3GB Ram ,64GB Rom Global version MiUI 12.0.3.0 i have managed to to install the 17.1 lineage through some experiences, First thanks to the two members who have been of help namely SparXFusion and Ma269 after i have read their post on this forum. Here is what i did i was on MIUI v11.0.4.0 which i later updated to 12.0.3.0 for this to work . Below is the procedure which i have been following and i discovered that the TWRP files i downloaded works fine from v 11.0.4 to 12.0.4.0 PROCEDURE
1- Download the TWRP file from this site : https://mega.nz/file/SuZn2QqZ#jJ6xRku...
2- Download the ADB file from this site : https://androidmtk.com/download-minim..
3- Below command prompts
fastboot devices
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta.img
fastboot flash misc misc.bin
fastboot boot recovery.img
Once boot in TWRP open Wipe/format then type yes. Then go to install to get the 17.1 lineage custom rom from internal or external storage if it was downloaded there . Then fine you are good to go
All in all i have noticed that to set the email its not working may the experts explain my observation.
Waiting to hear from some members the solution
One other question is where to get the Gapps for this rom 17.1 lineage merlin mt 6768
gruka said:
Hello members after a long daunting minutes ,hours and days asking for the procedures in this forum on how i can install the custom rom on the Redmi note 9 Merlin MT 6768 3GB Ram ,64GB Rom Global version MiUI 12.0.3.0 i have managed to to install the 17.1 lineage through some experiences, First thanks to the two members who have been of help namely SparXFusion and Ma269 after i have read their post on this forum. Here is what i did i was on MIUI v11.0.4.0 which i later updated to 12.0.3.0 for this to work . Below is the procedure which i have been following and i discovered that the TWRP files i downloaded works fine from v 11.0.4 to 12.0.4.0 PROCEDURE
1- Download the TWRP file from this site : https://mega.nz/file/SuZn2QqZ#jJ6xRku...
2- Download the ADB file from this site : https://androidmtk.com/download-minim..
3- Below command prompts
fastboot devices
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta.img
fastboot flash misc misc.bin
fastboot boot recovery.img
Once boot in TWRP open Wipe/format then type yes. Then go to install to get the 17.1 lineage custom rom from internal or external storage if it was downloaded there . Then fine you are good to go
All in all i have noticed that to set the email its not working may the experts explain my observation.
Waiting to hear from some memmbers the solution
Click to expand...
Click to collapse
Misc.bin isn't necessary for flashing twrp,
And what do you mean by "that to set the email it's not working"?
when you put your email on the email app you never log in , and one other question is which is the best gapps for this rom 17,1 lineage merlin
gruka said:
when you put your email on the email app you never log in , and one other question is which is the best gapps for this rom 17,1 lineage merlin
Click to expand...
Click to collapse
Pico Open Gappa or flame Gapps basic, both are fine.
And it's the stock email app, I never used it, so I don't know about that.
I am trying to get Magisk to work on my Xiaomi Redmi Note 8T with Lineage OS, but the step where I am patching the boot.img is failing. I am using LOS recovery, and I followed the instructions provided by topjohnwu [1]: because the 8T doesn't appear to have ramdisk (I don't know what that means btw), I need to patch an image (my recovery image?) with the magisk app - this is what I did:
1. Install Magisk App and check status: "Ramdisk: No"
2. Download Lineage recovery image [2] and patch in Magisk
3. Install patched recovery image using fastbook [3]
4. Wipe device and Install LOS + GApps
5. Reboot to system => still says "Ramdisk: No"
What am I doing wrong? How did everyone else root their Note 8T?
[1] https://topjohnwu.github.io/Magisk/install.html
[2] https://download.lineageos.org/ginkgo
[3] https://wiki.lineageos.org/devices/ginkgo/install#installing-a-custom-recovery-using-fastboot
---
EDIT: I just found this: https://github.com/topjohnwu/Magisk/issues/3239 - does that mean it worked? Doesn't look it did...I don't think I have root
lueromat said:
I am trying to get Magisk to work on my Xiaomi Redmi Note 8T with Lineage OS, but the step where I am patching the boot.img is failing. I am using LOS recovery, and I followed the instructions provided by topjohnwu [1]: because the 8T doesn't appear to have ramdisk (I don't know what that means btw), I need to patch an image (my recovery image?) with the magisk app - this is what I did:
1. Install Magisk App and check status: "Ramdisk: No"
2. Download Lineage recovery image [2] and patch in Magisk
3. Install patched recovery image using fastbook [3]
4. Wipe device and Install LOS + GApps
5. Reboot to system => still says "Ramdisk: No"
What am I doing wrong? How did everyone else root their Note 8T?
[1] https://topjohnwu.github.io/Magisk/install.html
[2] https://download.lineageos.org/ginkgo
[3] https://wiki.lineageos.org/devices/ginkgo/install#installing-a-custom-recovery-using-fastboot
---
EDIT: I just found this: https://github.com/topjohnwu/Magisk/issues/3239 - does that mean it worked? Doesn't look it did...I don't think I have root
Click to expand...
Click to collapse
install OrangeFox recovery
rename Magisk22.APK to Magisk22.ZIP
install it like any zip in recovery
reboot
(i suggest you do a clean flash to avoid problems)
(yess, RN8 have ramdisk but that's not required for root to work)
After clean flashing the official LOS 17.1, I re-tried to install Magisk giving it every request permission and following steps detailed above by loopypalm but (as before) I'm still seeing "Requires Additional Setup" followed by a "Setup failed" message...
I unlocked the phone recently, set up the latest OrangeFox recovery and flashed new RN8 global firmware v12.0.4.0, Lineage v17.1 nightly 20210405 and pico OpenGapps 20210406. The phone isn't even encrypted (i.e., I've set no fingerprint, pin or pattern).
I tried removing Magisk v22 with the official uninstaller and downgrading to v21.4 with the same result. Then I used the Manager facilities to upgrade both Manager and the underlying Magisk, but still no dice.
I'm scratching my head here about what else to try. Something I noticed that may or may not be related is, while it was working alright before I started setting up Magisk, advanced reboot became really sluggish and failed to reboot to recovery after this (only buttons work).
I'll keep searching and will maybe try a different ROM but this is a real bummer.
loopypalm said:
install OrangeFox recovery
rename Magisk22.APK to Magisk22.ZIP
install it like any zip in recovery
reboot
(i suggest you do a clean flash to avoid problems)
(yess, RN8 have ramdisk but that's not required for root to work)
Click to expand...
Click to collapse
after installing LOS, GApps and Magisk in OrangeFox, and then booting to system, the phone is stuck at the sim PIN entry - I can enter it, but it doesn't advance afterwards. this is what I did:
1. Install TWRP
2. Use TWRP to install OF
3. in OF, wipe everything except usbstorage and sdcard
4. create installation queue with latest LOS, GApps, and Magisk, and install
5. boot to system => stuck at sim PIN entry
any suggestions?
i have the same with the latest LOS 17.1 tried also 21.4 both not working, I flashed again without Magisk so far
cali.s said:
i have the same with the latest LOS 17.1 tried also 21.4 both not working, I flashed again without Magisk so far
Click to expand...
Click to collapse
I hit "Emergency", went back to the PIN mask, and then it would accept my SIM pin. So far so good...
pnin said:
After ...
Click to expand...
Click to collapse
please follow instruction and do not add/remove a step
-flash OFox (if you already have it = no need)
-reboot to recovery
-flash latest A10 stable FW RN8 Ginkgo / RN8T Willow
-format data (not wipe) (this will erase internal storage!)
-reboot to recovery
-wipe 5 (cache/dalvik/system/vendor/data)
-flash the rom you want
-flash kernel (if you have any)
-flash DFE
-format data again
-reboot to recovery
-reboot to system
-reboot to recovery and flash magisk
done
lueromat said:
after installing LOS, GApps and Magisk in OrangeFox, and then booting to system, the phone is stuck at the sim PIN entry - I can enter it, but it doesn't advance afterwards. this is what I did:
1. Install TWRP
2. Use TWRP to install OF
3. in OF, wipe everything except usbstorage and sdcard
4. create installation queue with latest LOS, GApps, and Magisk, and install
5. boot to system => stuck at sim PIN entry
any suggestions?
Click to expand...
Click to collapse
i heard about that bug
remove the pin from the sim in another phone
loopypalm said:
-flash the rom you want
-flash kernel
-flash DFE
Click to expand...
Click to collapse
The ROM I want is the official Lineage -- I'm no hardcore flasher, just want to take it easy with a tried and tested custom ROM. But the kernel and DFE got me stumped: do I really need them? Which ones?
pnin said:
The ROM I want is the official Lineage -- I'm no hardcore flasher, just want to take it easy with a tried and tested custom ROM. But the kernel and DFE got me stumped: do I really need them? Which ones?
Click to expand...
Click to collapse
i think you should try RRos (it's based on LOS and updated)
i said kernel, so if you have one in mind, that's the step (correct order) you flash it in
(people use "sixteen" for battery,or default "quicksilver" ,or ryzen or ...)
DFE is "Disables dm-verity, forced encryption"
lueromat said:
after installing LOS, GApps and Magisk in OrangeFox, and then booting to system, the phone is stuck at the sim PIN entry - I can enter it, but it doesn't advance afterwards. this is what I did:
1. Install TWRP
2. Use TWRP to install OF
3. in OF, wipe everything except usbstorage and sdcard
4. create installation queue with latest LOS, GApps, and Magisk, and install
5. boot to system => stuck at sim PIN entry
Click to expand...
Click to collapse
lueromat said:
I hit "Emergency", went back to the PIN mask, and then it would accept my SIM pin. So far so good...
Click to expand...
Click to collapse
so in the end this worked, LOS + root, and no complaints so far.
other users were also successful with not sticking to the official magisk installation instruction, but just flashing the zip in recovery: https://github.com/topjohnwu/Magisk/issues/3239#issuecomment-816164610
guess this is the way to go for willow
loopypalm said:
please follow instruction and do not add/remove a step
-flash OFox (if you already have it = no need)
-reboot to recovery
-flash latest A10 stable FW RN8 Ginkgo RN8T Willow
-format data (not wipe) (this will erase internal storage!)
-reboot to recovery
-wipe 5 (cache/dalvik/system/vendor/data)
-flash the rom you want
-flash kernel (if you have any)
-flash DFE
-format data again
-reboot to recovery
-reboot to system
-reboot to recovery and flash magisk
done
Click to expand...
Click to collapse
Hi loopypalm, only for curiosity: is there a reason why to wipe /data "again" in step 6 after having formatted /data already in step 4? And furthermore why to format /data for a second time in step 10? What happens to /data after the first formatting that makes these steps recommendable? Thx if you find a minute to explain...
HI , this is what devs been recommending since the beginning (on ginkgo)
Uluru25 said:
is there a reason why to wipe /data "again" in step 6 after having formatted /data already in step 4?
Click to expand...
Click to collapse
no
Uluru25 said:
And furthermore why to format /data for a second time in step 10? What happens to /data after the first formatting that makes these steps recommendable?
Click to expand...
Click to collapse
me personally i don't think formatting data a 2nd time is necessary
but as for what i think could be the reason is after formatting data you will get a "raw" file system , so the OS will choose the situable file system for it "EXT2" or "EXT4" or ...
that's why sometimes the system wont boot even if you flash DFE
(which (i think) is the case on all ports like ONEUI or OOS ...)
loopypalm said:
please follow instruction and do not add/remove a step
-flash OFox (if you already have it = no need)
-reboot to recovery
-flash latest A10 stable FW RN8 Ginkgo / RN8T Willow
-format data (not wipe) (this will erase internal storage!)
-reboot to recovery
-wipe 5 (cache/dalvik/system/vendor/data)
-flash the rom you want
-flash kernel (if you have any)
-flash DFE
-format data again
-reboot to recovery
-reboot to system
-reboot to recovery and flash magisk
done
Click to expand...
Click to collapse
loopypalm,
- Orange Fox, should "Allow modifications" be enabled OR "keep read-only"?
- will latest A11 (anrdoid 11) stable FW (Firmware) also be ok, or is this guide specifically for A10?
Other notes of mine:
- OrangeFox requires device to be unlocked with MiFlash unlocking software first. (It's a type A device it seems, NOT a/b)
jddcef said:
- Orange Fox, should "Allow modifications" be enabled OR "keep read-only"?
Click to expand...
Click to collapse
allow Read & write
jddcef said:
- will latest A11 (anrdoid 11) stable FW (Firmware) also be ok, or is this guide specifically for A10?
Click to expand...
Click to collapse
this guide is for all rom, if you are using A11 then use A11 FW
jddcef said:
- OrangeFox requires device to be unlocked with MiFlash unlocking software first. (It's a type A device it seems, NOT a/b)
Click to expand...
Click to collapse
The Ofox i linked is for Ginkgo/Willow if you have this device + unlocked BL = just flash
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.