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?
I installed a Magisk Module, called Notch killer or something to that effect from magisk downloads. Reboot caused my phone to not boot, but be stuck on the boot animation forever.
Is there a way to uninstall the module alone or recover the system without losing data. I am more concerned about the storage card data and would like to keep that for sure. Any insights / help is greatly appreciated.
srikaran said:
I installed a Magisk Module, called Notch killer or something to that effect from magisk downloads. Reboot caused my phone to not boot, but be stuck on the boot animation forever.
Is there a way to uninstall the module alone or recover the system without losing data. I am more concerned about the storage card data and would like to keep that for sure. Any insights / help is greatly appreciated.
Click to expand...
Click to collapse
If u search properly there is already a thread about this
v.konvict said:
If u search properly there is already a thread about this
Click to expand...
Click to collapse
Thanks for the pointer. I did go through all the threads and did find similar issue already addressed. For anyone that's keen, I ended up installing the stock boot.img and that ensured that I could boot. Out of curiosity, I tried to flash the patched boot.img and that ended up in the same loop again. Will search further as to how to remove that module first and then flash the patched boot.img, that should work somehow, not sure yet.
https://forum.xda-developers.com/oneplus-7t/help/magisk-modules-causing-bootloop-t3981427
OK, finally got everything back to running the way it was. After getting the stock boot image, to root it again, I followed the following steps.
1. Download the full OTA image
2. Install Payload Dumper
3. Extract recovery.img using the Payload Dumper from the full image (Payload.bin)
4. Extract the recovery.img using Android Image Kitchen.
5. Modify the default.prop to enable adb in ramdisk folder
6. Repackaged the recovery.img
7. Flashed the modified recovery.img to recovery partition.
8. Booted to recovery.
9. On the PC, went into adb shell, navigated to /data/adb/modules and identified the rogue magisk module and deleted that folder completely.
10. Booted back to bootloader
11. Flashed the stock recovery back to the recovery partition.
12. Rebooted to recovery, just to verify that everything was intact.
13. Rebooted to bootloader
14. Installed the patched boot.img for root
15. Reboot the system
That made it work as it was before without any issues. Thanks a ton to the great community that had already solved these issues. Here are the links to the forum posts and tools used.
How to Root: https://forum.xda-developers.com/oneplus-7t/how-to/guide-how-to-root-oneplus-7t-twrp-t3979307
Patched boot.img (10.3.0, Indian version): https://forum.xda-developers.com/oneplus-7t/how-to/oneplus-7t-10-3-0-indian-hd1901-t4021047
Payload Dumper: https://github.com/vm03/payload_dumper
Android Image Kitchen: https://forum.xda-developers.com/showthread.php?t=2073775
ADB in recovery: https://forum.xda-developers.com/7t-pro/development/recovery-oxygen-os-stock-recovery-adb-t3991865
Remove Magisk Modules: https://forum.xda-developers.com/oneplus-7t/how-to/magisk-twrp-root-module-uninstall-t4002843
10.0.11 Global - ADB Enabled - Insecure Recovery
I've tested it on my OP7T, worked for me.
https://drive.google.com/file/d/1FgngmAJQ-GKc0nIjngcspkU_xzwb-Y7T/view?usp=sharing
Please follow this guide on how to remove magisk modules
https://forum.xda-developers.com/7t-pro/how-to/guide-remove-magisk-modules-twrp-t3995677
Hi all,
Have seen a lot of requests for patched boot images on these threads so thought i'd share a guide on how to get it yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it without obtaining one yourself
Please read the process before committing to proceeding, so you know what's required and what you should and shouldn't use!
Stock and patched images are UK/ EU but the guides are universal and could be used on multiple devices.
NOTE:
For these guides the versions used are:
Stable, Canary or BETA depending on firmware, simply change the channel in Magisk settings then select install / update:
11.0.1.1
Magisk Manager - Magisk (Canary) version: 1469b82a (21101)
11.0.2.2
Boot img patched using Magisk (Canary) version: 1469b82a (21101)
11.0.3.3
Boot img patched using Magisk beta 21.4 (21400)
11.0.4.4 (DO NOT UPDATE TO 22.0 YOU WILL BOOTLOOP!
Boot Img patched using Magisk beta
21.4 (21400)
11.0.5.5
Boot img patched using Magisk Stable 22.0 (22000) (18)
11.0.6.6
Boot img patched using Magisk Stable 22.1 (22100)
11.0.7.7
Boot.img patched using Magisk Stable 23.0 (23000) (21)
11.0.8.8
Boot.img patched using Magisk Stable 23.0 (23000) (21)
11.0.9.9
Boot.img patched using Magisk Stable 23.0 (23000) (21)
11.0.10.10
Boot.img patched using Magisk Stable 23.0 (23000) (21)
11.0.11.11
Boot.img patched using Magisk 24
https://forum.xda-developers.com/attachments/11-0-11-11-europe-patched-24303-zip.5566283/
Thanks @tfae
12 11.C.15 EU. Thanks @tfae
1st
Extracting a boot.img using Payload dumper
Pre-requisites
A device with a working version of magisk manager installed, simply change the channel to the version outlined in the list above relevant to your firmware then select install / update:
A Windows 10 computer / laptop
A full update downloaded firmware zip for your model (recommend oxygen updater)
Payload dumper program for Windows.
Process
On your computer
1. Download and copy the PAYLOAD DUMPER folder to your desktop, there will be one folder with 2 files and 2 folders inside.
Download from here: https://mega.nz/folder/vU00FZDa#PIEfjl5w5wonyNAwHW3FBQ
2. Download the firmware of your choice and open it using Winrar or a similar zip program, extract the file called payload.bin to the folder within the payload folder called payload_input.
3. Run the program payload_dumper.exe, a Command prompt will open to show extraction progress (this will extract a bunch of files to the payload_output folder) allow it to completely finish (the CMD window will close automatically)
4. One of the files will be called boot.img, this is the file we'll be patching, copy this to your phone, root of storage which is called /sdcard.
On your phone
5. Open up Magisk and click Install / Update, if you don't see update then change channel, so this by changing the channel in magisk settings, it'll then show the install/ update buttons.
6. Select "Select and Patch a file" it'll open up a file browser, navigate to the boot.img you copied earlier and select it, allow it to complete (this will output a file called "magisk_patched" (which will be in the Downloads folder)
You now have a patched boot.img ready to flash to either slot with fastboot or boot via fastboot, would recommend booting as this is risk free, if it's a bad image for whatever reason and you choose to flash then your phone may bootloop.
NOTE** Some people have noticed that an already patched boot.img when flashed can fail and cause a boot loop when flashed,so if you have downloaded a magisk_patched img from somewhere else then you WILL need to re-patch it on your own device preferably using the afore mentioned magisk manager based on what firmware it's from.
If you intend to follow the guide below with your own patched img then you shouldn't need to patch twice but it won't hurt if you do.
2nd
Upgrading from rooted Android 10 to rooted Android 11
Pre-requisites
A rooted device running Android 10
Canary magisk manager or beta version that works:
Windows 10 computer / laptop
Process
On your phone
1. Disable all Magisk mods
2. Download the Android 11 firmware using Oxygen updater DO NOT INSTALL AUTOMATICALLY, WE NEED TO INSTALL MANUALLY!!!
3. Once downloaded; open settings / system / system updates
4. Click the settings cog and click 'install from local storage'
5. Locate the firmware you downloaded, it's in the root of storage.
6. Click install and allow it to finish, DO NOT CLICK THE REBOOT BUTTON YET!
7. Open Magisk. manager and click "Install / Update"
8. Click "Install to Inactive slot (After OTA) (Once complete, click reboot)
As this is a new base the first boot may take a little longer.
Your phone will now boot with Android 11.0.0 and will have retained root, all your apps will remain as you left them.
Be careful what mods you re-enable as they may not be 11 compatible.
3rd
Update from 11 stable to 11+ stable whilst retaining root
Guide
1. Download the relevant firmware for your device via oxygen updater
2. Open Magisk and remove all the modules you have installed, then reboot
**NOTE- At this point I tend to copy out the whole firmware to my computer, incase I need it in the future, the boot img and patched boot img are at the foot of this guide, I'll always upload the latest firmware as soon as it comes out for the UK/EU model
3. Open up settings / system / system updates , click the cog and select "Local Upgrade" the file should be listed on screen, if not then move the file to the root of your phones storage.
4. Click install and allow it to go through the process
**NOTE- DO NOT REBOOT AT THIS POINT YOU WILL LOSE THE ABILITY TO PATCH ON THE FLY, SIMPLY BACK OUT OF THE SCREEN WHICH SAYS "INSTALLATION COMPLETED. RESTART TO EXPERIENCE NEW FEATURES"
5. Open up magisk and click install (you may see two install buttons, top one is magisk and the bottom is magisk manager, we need the top one)
6. You'll be faced with a screen that has several options, you want to select "Install to Inactive slot (After OTA)" then select "LET'S GO" once complete click reboot.
7. Once your phones booted back up your system / files should all remain as they were and you should have root access.
You can now install all your modules again so long as they're compatible with the firmware you've just updated to.
4th
Rooting using fastboot commands
Method 1
Booting the patched image
1. Obtain a patched boot image for your device variant preferably using payload dumper or download one of mine from the foot of this guide or if you've just performed the above guide you should already have a functional one, copy this file to your fastboot folder on your computer
**NOTE - The above suggested downloads are for the EU / UK variant- if you have another model / firmware please use that instead, If you did not obtain the boot.img from a firmware and patch it yourself, you will need to patch it again in magisk manager to avoid a bootloop, if you still get a bootloop it's best to obtain one yourself using the guide at the top of this post.
2. Reboot your phone to fastboot
and connect to your computer.
3. Boot the magisk patched img
fastboot boot magisk_patched (or name of your patched boot img)
Your phone should now boot automatically, you should now be rooted but we need to make this permanent, if you were to reboot you would lose root.
4. Open magisk manager and click install/update, if you are missing the install/ update buttons, change magisk version to beta in magisk settings and install the update, the buttons should then show.
5. Select Direct install (recommended) then click ok.
6. Allow magisk to permanently root your device then click reboot.
You should now boot and remain rooted.
Method 2
Flashing to both slots
1. Obtain a patched boot img for your device variant or download one of mine from the foot of this guide or if you've just performed the above guide you should already have a functional one, copy this file to your fastboot folder on your computer
**NOTE - Again the above suggested downloads are for the EU/ UK variant- if you have another model / firmware please use that instead, if you did not obtain the boot.img from a firmware and patch it yourself, you will need to patch it again in magisk manager, to avoid a bootloop
2. Reboot your phone to fastboot and connect to your computer.
Command: adb reboot bootloader
3. Open a command prompt on your computer and navigate to your ADB/fastboot folder.
4. Type the following.
fastboot flash boot_a magisk_patched
Press enter.
fastboot flash boot_b magisk_patched
Press enter
fastboot reboot
Press enter
6. Your phone should now boot, open magisk and verify you're rooted.
Troubleshooting
If flashing succeeds but you don't have root and you've followed all the instructions, you may have some magisk modules still active, try performing the following.
1. Connect your phone to your computer.
2. Reboot the phone, then during the boot animation enter this command via ADB.
adb wait-for-device shell magisk --remove-modules
3. Allow to boot, modules will be removed and root should then be active.
Thanks @nycdiplomat for this tip.
If there is no magisk install / update buttons.
1. Make sure you have granted permission to magisk in settings / apps / magisk / permissions
2. Make sure that the update channel is on canary, then force close magisk and then re-open
3. If it still doesn't work then update magisk using canary
4. Last method to check would be to change to the beta channel in magisk settings, then install it.
Or change the update channel, install the version on offer, then change back to canary, install and you should be good to go.
Window's version
Windows 7 will not work with fastboot, please use Windows 10
USB
Use USB 2.0 not 3.0 or 3.1
ADB
These are the files i use for ADB (1st in the below list) tested these on fresh installs of windows on several windows machines, all win 10
Place them into the root of C so it reads C:\ADB much easier to navigate to that way.
Files:
ADB Files for Windows 10:
7.69 MB folder on MEGA
5 files
mega.nz
Payload dumper program for Windows-
https://mega.nz/folder/vU00FZDa#PIEfjl5w5wonyNAwHW3FBQ
Full OTA - Oxygen OS 11.0.1.1 - EU IN11BA -IN2023 FIRMWARE -
https://mega.nz/file/TZl2WIBR#wSP3_bkoWl1FZZX7zfhobo3cYIAhWvDQ9f0ot3_qNFo
Oxygen OS 11.0.0 EU 11.IN11BA - IN2023 Patched boot.img -
https://mega.nz/folder/TE8yWbIL#a6woc43pCpTX_URX5dWr1A
Oxygen OS 11.0.1.1 - EU IN11BA -IN2023 Stock boot.img -
https://mega.nz/folder/6d1mVYgJ#tE90TcwqTLp71SgZX9Xxhg
Oxygen OS 11.0.1.1 - EU IN11BA -IN2023 Patched boot.img -
https://mega.nz/folder/CINjAQCZ#Sns
sRugbc0sELF0ajSAEXg
Boot img patched using Magisk (Canary) version: 1469b82a (21101)
Oxygen OS 11.0.2.2 - EU IN11BA -IN2023 Stock boot.img -
https://mega.nz/folder/PFsmFDKY#01sGzxzVpiAELjcT0LuZmQ
Oxygen OS 11.0.2.2 - EU IN11BA -IN2023 Patched boot.img -
https://mega.nz/folder/vJs0FRBD#SisIJ5FrmkJ3ej1RB6Yz3Q
Boot img patched using Magisk (Canary) version: 1469b82a (21101)
Oxygen OS 11.0.3.3 - EU IN11BA -IN2023 Stock boot.img -
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.3.3 - EU IN11BA -IN2023 Patched boot.img -
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.4.4 - EU IN11BA -IN2023 Stock boot.img -
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.4.4 - EU IN11BA -IN2023 Patched boot.img -
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.5.5 - EU IN11BA -IN2023 Stock boot.img -
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.5.5 - EU IN11BA -IN2023 Patched boot.img -
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.6.6 - EU IN11BA -IN2023 Stock boot.img -
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.6.6 - EU IN11BA -IN2023 Patched boot.img -
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.7.7 - EU IN11BA -IN2023 Stock boot.img
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.7.7 - EU IN11BA -IN2023 Patched boot.img
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.8.8 - EU IN11BA -IN2023 Stock boot.img
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.8.8 - EU IN11BA -IN2023 Patched boot.img
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.9.9 - EU IN11BA -IN2023 Stock boot.img
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.9.9 - EU IN11BA -IN2023 Patched boot.img
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.10.10 - EU IN11BA -IN2023 Stock boot.img
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.10.10 - EU IN11BA -IN2023 Patched boot.img
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.11.11 EU IN11BA - IN2023
Stock boot.img
16.98 MB file on MEGA
mega.nz
Oxygen OS 11.0.11.11 EU IN11BA - IN2023
Patched boot.img
https://forum.xda-developers.com/attachments/11-0-11-11-europe-patched-24303-zip.5566283/
Android 12 11.C.15 - Stock and patched images from. @tfae
File on MEGA
mega.nz
Hi bro thank you so much for this. I don't understand what to do next now. My phone is already updated to 11 and I want to root it and install masigk etc how do I do that? Its already on version 11 I installed normal version 11 stock rom.
So I was on version 10 before and it was rooted and I had magisk I updated and lost root access and magisk. So now I'm on version 11. I have downloaded your patched boot image but what do I do next could you please hell me?
dblane82222 said:
Hi bro thank you so much for this. I don't understand what to do next now. My phone is already updated to 11 and I want to root it and install masigk etc how do I do that? Its already on version 11 I installed normal version 11 stock rom.
So I was on version 10 before and it was rooted and I had magisk I updated and lost root access and magisk. So now I'm on version 11. I have downloaded your patched boot image but what do I do next could you please hell me?
Click to expand...
Click to collapse
Ah so you're on 11 stock? Have you unlocked the bootloader?
I have a guide based on android 10 here for unlocking the bootloader, lot of similarities.
https://forum.xda-developers.com/oneplus-8-pro/how-to/guide-unlocking-bootloader-rooting-t4151823
Please don't dive in without reading first.
If you've already unlocked the bootloader then you can simply use the magisk_patched img on step 1 of the Rooting section.
Please let me know before you start.
PS: thanks for not quoting the entire post
Bootloader is already unlocked.
Yes I'm on stock 11.
If you've already unlocked the bootloader then you can simply use the magisk_patched img on step 1 of the Rooting section. (Where is this section?)
I'm about to start the process now.
dblane82222 said:
Bootloader is already unlocked.
Yes I'm on stock 11.
If you've already unlocked the bootloader then you can simply use the magisk_patched img on step 1 of the Rooting section. (Where is this section?)
I'm about to start the process now.
Click to expand...
Click to collapse
Yep that should be fine. I think you can also do this from magisk under direct install but I've not tried before and I think it's possible that this may require twrp. So yea go with the root guide.
Should be ok.
Could you give me the link to the Rooting section you have referred too so I know what to do please?
And magisk won't install for me won't let me. So I can't do that. I even tried installing twrp but it won't work.
dblane82222 said:
Could you give me the link to the Rooting section you have referred too so I know what to do please?
And magisk won't install for me won't let me. So I can't do that. I even tried installing twrp but it won't work.
Click to expand...
Click to collapse
No don't install twrp it doesn't work..
Rooting should be a case of installing the magisk_patched IMG to the active slot, you can do both..
The root process is at the bottom of the link i sent you mate.
This is the section on root.
You'll need the magisk_patched file from the OP
Rooting
1. On your computer
Get the magisk_patched file
2. Copy "magisk_patched.img" to C:\Android
3. Navigate to C:\Android
i) Hold shift and right click an empty space within the folder
ii) Click "Open Powershell Window here" or "Open a Command prompt Windows here"
iii) A black or blue window will appear with some text
4. Type the following into the window
adb reboot fastboot
press enter
On your phone
i) Your phone will reboot and show you a screen with 3 language choices, Choose "English" then "Advanced" and finally "Reboot to fastboot" and "Reboot to fastboot"
ii) You'll see a screen appear on your phone with some text, at the top you'll see the word "START" in green, you're now in Fastboot
On your computer
5. Type the following into the window
fastboot flash boot_a magisk_patched.img
press enter
then
fastboot flash boot_b magisk_patched.img
press enter
NOTE* THIS WILL FLASH THE PATCHED BOOT IMG TO BOTH SLOTS, THIS IS WHAT I DID, I HAVEN'T EXPLORED IF ONE SLOT IS ADEQUATE OR NOT, IT MAY BE POSSIBLE TO ONLY FLASH THE BOOT.IMG TO ONE SLOT BUT AS I HAVEN'T I CAN'T ADVISE.
6.. Once complete, type in the following command
fastboot reboot
press enter, your device will reboot
7. On your phone open up "Magisk Manager" you should now have two green ticks signifying that you now have root access.
So long as you have magisk manager installed that's all you need to do besides that guide
Let me know how u get on
dladz said:
Let me know how u get on
Click to expand...
Click to collapse
so every time i do this on my cmd it says unknown partition 'magisk_patched.img'
error cant determine image file name for 'magisk_patched.img'
sorry if i seems stupid.
---------- Post added at 09:44 PM ---------- Previous post was at 09:34 PM ----------
dladz said:
Let me know how u get on
Click to expand...
Click to collapse
okay so its worked now. i managed to flash it but once i restarted the phone its stuck in a loop keeps going to bootloader menu what do i do now?
---------- Post added at 09:57 PM ---------- Previous post was at 09:44 PM ----------
okay so now its gone to crashdump mode?
dblane82222 said:
so every time i do this on my cmd it says unknown partition 'magisk_patched.img'
error cant determine image file name for 'magisk_patched.img'
sorry if i seems stupid.
---------- Post added at 09:44 PM ---------- Previous post was at 09:34 PM ----------
okay so its worked now. i managed to flash it but once i restarted the phone its stuck in a loop keeps going to bootloader menu what do i do now?
---------- Post added at 09:57 PM ---------- Previous post was at 09:44 PM ----------
okay so now its gone to crashdump mode?
Click to expand...
Click to collapse
? What did you flash?
dladz said:
? What did you flash?
Click to expand...
Click to collapse
the file you gave .. the bootimage please help me because im screwed now i dont have a working phone...
so basicaly before i installed what u gave me and it was just stuck on the bootloader screen it wouldnt go off it. at all
so i installed twrp and then it jut crashed mode... please please help me?
So you needed the magisk_patched from the beginning of this thread (the OP)
Then boot to fastboot mode and flash to both slots using ADB / fastboot from Windows..
Then fastboot reboot.
That's literally it mate..that's all I did.
If you're in crashdump mode then i have no idea what you flashed or how you flashed it..shouldn't have done that.
You're on the EU/UK model right?
No reason why it wouldn't have worked.
dblane82222 said:
the file you gave .. the bootimage please help me because im screwed now i dont have a working phone...
so basicaly before i installed what u gave me and it was just stuck on the bootloader screen it wouldnt go off it. at all
so i installed twrp and then it jut crashed mode... please please help me?
Click to expand...
Click to collapse
Ok so do not install twrp it does not work on 11.
Calm down a moment you haven't broken anything so don't worry..
Tell me what screen you're on please. Also can you boot to fastboot mode? Or even bootloader?
Worse case scenario you will have EDL mode and the MSM tool which can get you back up and running..
Do not attempt to install twrp as it will not work and will cause more harm than good.
If you add steps besides what you're meant to do I can't help you pal.
dladz said:
Ok so do not install twrp it does not work on 11.
Calm down a moment you haven't broken anything so don't worry..
Tell me what screen you're on please. Also can you boot to fastboot mode? Or even bootloader?
Worse case scenario you will have EDL mode and the MSM tool which can get you back up and running..
Do not attempt to install twrp as it will not work and will cause more harm than good.
Click to expand...
Click to collapse
yes i think its edl mode. i cant access any mode at all. nothing is accesable. can you please give me the link for the msm tool and what i need to do please thank you ? i really do apprecite all the help.
---------- Post added at 10:20 PM ---------- Previous post was at 10:17 PM ----------
dblane82222 said:
yes i think its edl mode. i cant access any mode at all. nothing is accesable. can you please give me the link for the msm tool and what i need to do please thank you ? i really do apprecite all the help.
Click to expand...
Click to collapse
do you have anything that i can speal to u on thats more instant such as whts app or discord or icq or anything ??
dblane82222 said:
yes i think its edl mode. i cant access any mode at all. nothing is accesable. can you please give me the link for the msm tool and what i need to do please thank you ? i really do apprecite all the help.
---------- Post added at 10:20 PM ---------- Previous post was at 10:17 PM ----------
do you have anything that i can speal to u on thats more instant such as whts app or discord or icq or anything ??
Click to expand...
Click to collapse
I'm actually in bed at the moment pal.
Here's the MSM thread
https://forum.xda-developers.com/on...-tool-to-restore-device-t4084953/post82327013
I think it may have been trying to install twrp.
Before you go down the MSM route.
Try to power off the device without the cable connected..press and hold power and vol down..until the phone turns on.
Should go to bootloader.
If not try it the above with the cable connected to your phone and computer.
If you still can't get in then yes it's MSM time..
Personally have never used it but it's an active thread so always people in there and 10000% someone will have been in the same boat as you.
Not sure what happened with your situation tbh..I tested all the files again myself and they're all legit. I used them before I spoke with you and again just now.
Please though, try not to worry, you'd have to do something mental to break a OnePlus.
You'll be fine.
Let me know how your get on and I'll answer when I can..quite tired at moment.
yeah tried all of that still nothing. going to try the msm solution see what that does its downloading as we speak. but even before the twrp i done what u said and it was stuck on bootloader any idea why that would be ? i can understand it happened becuase i installed twrp and that casued the phone ot enter edl mode. but prior to it it was stuck on bootloader. following just the steps u had said ? once i have got he phone back up and running should i try your mehtod again and see what happens again ?
no problem really apprecite all the help you have given me thank so much.
dblane82222 said:
yeah tried all of that still nothing. going to try the msm solution see what that does its downloading as we speak. but even before the twrp i done what u said and it was stuck on bootloader any idea why that would be ? i can understand it happened becuase i installed twrp and that casued the phone ot enter edl mode. but prior to it it was stuck on bootloader. following just the steps u had said ? once i have got he phone back up and running should i try your mehtod again and see what happens again ?
no problem really apprecite all the help you have given me thank so much.
Click to expand...
Click to collapse
Nah no worries man, just trying to work out what happened..
Once you're back up, maybe ask another thread just to confirm as I'm second guessing myself now..
Don't want you to end up like this again..
See what the chap says in the MSM thread too, his telegram username is in his profile.
To confirm you do have a UK phone right? IN2023 BA
Could have just been the flash didn't go through. You did do a flash and not boot right? To get out of that. Could have just flashed the stock boot.img and that would have saved you
Hi guys.
I'm trying to patch a boot.img from latest version V11.0.19.0 with Magisk 23 but the resulting file does not complete the boot procedure when used with platform.tools.
It starts the booting process but after security pattern it remains with the booting animation forever. I need to restart the phone to access it.
i got the boot.img file from the Fastboot image available here - https://xiaomifirmwareupdater.com/miui/daisy/stable/V11.0.19.0.QDLMIXM/
Could any of you try to sort this out for me.
Thanks in adavance
Jiute
Problem resolved. It was the Magisk Modules still active. Had to Disable them and then all went smooth.
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.