Related
I have just bought oneplus 7 t pro and want to root it. How do I extract boot.img from the firmware so I can patch it using magisk ? Any help in rooting this device would be greatly appreciated. Thanks
you should wait the stock rom or you can try to boot the oneplus 7t twrp and backup the boot.img
Thanks
Will try and report back
boots into the twrp 7t recovery but boot.img is not being backed up . It fails to mount any partition . adb pull command not working .
I have boot image
are you able to patch it with magisk ?
ask77 said:
are you able to patch it with magisk ?
Click to expand...
Click to collapse
unfortunately not
I have now extracted boot.img and patched it with magisk but the output image is of 36.44 MB while the original image is of 96 MB so I am a bit wary in flashing this image as I do not want to go into a boot loop also I have a boot.img and a recovery.img both are identical in size and are identified by magisk as stock boot.img . i am uploading the install log . I will research a bit more before flashing the patched boot img to achieve root
ask77 said:
I have now extracted boot.img and patched it with magisk but the output image is of 36.44 MB while the original image is of 96 MB so I am a bit wary in flashing this image as I do not want to go into a boot loop also I have a boot.img and a recovery.img both are identical in size and are identified by magisk as stock boot.img . i am uploading the install log . I will research a bit more before flashing the patched boot img to achieve root
Click to expand...
Click to collapse
try just doing fastboot boot patchedbootimghere.img
if it bootloops you can just restart the phone and it will be back to normal since its not flashed
HolyChickenGuy said:
try just doing fastboot boot patchedbootimghere.img
if it bootloops you can just restart the phone and it will be back to normal since its not flashed
Click to expand...
Click to collapse
Thanks will do that.
sorry no go . It either goes to crashdump or is stuck with the fastboot screen
ask77 said:
sorry no go . It either goes to crashdump or is stuck with the fastboot screen
Click to expand...
Click to collapse
I'm having the same results
Sent from my OnePlus 7T Pro
same there no luck. just the crash dump screen
digitalashley said:
same there no luck. just the crash dump screen
Click to expand...
Click to collapse
Make sure to check Preserve AVB 2.0/dm-verify in advance settings before patching boot.img, then use command
fastboot boot imagenamehere.img, after boot, perform direct install to preserve root.
Hi,
I just updated to 10.0.9.HD01BA on my OP7T Pro and after that I tried to root it with Magisk by patching the OTA update.
This didn't work and it was stuck at the boot animation, so I extracted the boot.img and patched it with Magisk.
But with the patched version I'm also always stuck at the boot animation.
If I flash the original boot.img again, everything is fine, except that there is no root of course.
I already rooted many OP7 and OP7T and never got this result.
Is Magisk currently not supporting 10.0.9, or am I doing something wrong?
I really don't know what else I could do.
Is someone else experiencing this issue?
Catter38 said:
Hi,
I just updated to 10.0.9.HD01BA on my OP7T Pro and after that I tried to root it with Magisk by patching the OTA update.
This didn't work and it was stuck at the boot animation, so I extracted the boot.img and patched it with Magisk.
But with the patched version I'm also always stuck at the boot animation.
If I flash the original boot.img again, everything is fine, except that there is no root of course.
I already rooted many OP7 and OP7T and never got this result.
Is Magisk currently not supporting 10.0.9, or am I doing something wrong?
I really don't know what else I could do.
Is someone else experiencing this issue?
Click to expand...
Click to collapse
Did you disable and delete all Magisk modules before updating to OOS 10.0.9? If not, do the following:
- Boot your phone and enable ADB debugging in dev settings.
- Flash the patched Magisk boot.img.
- During boot connect your device to a PC and enter:
"adb wait-for-device shell magisk --remove-modules"
- Your device should reboot without any modules and you can install them again.
Macusercom said:
Did you disable and delete all Magisk modules before updating to OOS 10.0.9? If not, do the following:
- Boot your phone and enable ADB debugging in dev settings.
- Flash the patched Magisk boot.img.
- During boot connect your device to a PC and enter:
"adb wait-for-device shell magisk --remove-modules"
- Your device should reboot without any modules and you can install them again.
Click to expand...
Click to collapse
Unfortunately, I forgot to uninstall the modules.
I tried the adb command and the device reboots, but it's still in the same bootloop.
I also tried to uninstall the modules with TWRP, but since there isn't a fully working version for the OP7T Pro, this also didn't work.
What's weird is, that the magisk patched version of the boot.img always results in a way smaller file than the original.
The original file is ~100mb, while the patched version is ~40mb.
I don't know if this is normal, but it seems odd.
I also tried it with the canary version of magisk, which results in the same small boot.img.
Looks like I have to stay unrooted until this is fixed.
Ok, finally I got it to work.
Since my girlfriend also has a OP7T Pro and still is on 10.0.8 with root, I simply took her boot image and booted it with fastboot. This also resulted in the same bootloop, but now the adb command worked and I was able to boot a rooted 10.0.8 boot.img. Now I was able to use the direct install of magisk and patched the 10.0.9 installation with it.
I think my problem was, that I did't remove the modules in the first place, which screwed up the whole update.
I still can't explain why I wasn't able to patch the boot.img with magisk. It didn't work on my phone with the canary build of magisk, neither did it work on the phone of my girlfriend with magisk 20.4.
Anyway. Now I have a working 10.0.9 boot.img and can safely upgrade my girlfriends phone too.
Thanks for the help!
https://app.box.com/s/9r77wcvk2dnbos87rpr1lfcnmnd091le
Here is.... HD10.0.9BA Patched and the original boot.img..... ?
kovacsabesz said:
https://app.box.com/s/9r77wcvk2dnbos87rpr1lfcnmnd091le
Here is.... Last build... Patched and the original img..... ?
Click to expand...
Click to collapse
Interesting, your patched image also is way smaller than the original.
Did you verify, that it's working?
https://app.box.com/s/at1mhbvpkspg4wfzp16cqppgdvvidese
I'm using it now.... Without problem
Catter38 said:
Interesting, your patched image also is way smaller than the original.
Did you verify, that it's working?
Click to expand...
Click to collapse
It seems to be normal. I'm not sure why but it might be due to compression. Anyway, glad you figured it out.
Catter38 said:
Interesting, your patched image also is way smaller than the original.
Did you verify, that it's working?
Click to expand...
Click to collapse
kovacsabesz said:
https://app.box.com/s/9r77wcvk2dnbos87rpr1lfcnmnd091le
Here is.... HD10.0.9BA Patched and the original boot.img.....
Click to expand...
Click to collapse
Would you mind uploading the files again if you can? I'm struggling with my device being in bootloop and I can't remove the module causing it bc I can't access adb with the bootloop. With the stock boot img I'm hoping to boot the device again and remove the bad module via adb
Macusercom said:
Did you disable and delete all Magisk modules before updating to OOS 10.0.9? If not, do the following:
- Boot your phone and enable ADB debugging in dev settings.
- Flash the patched Magisk boot.img.
- During boot connect your device to a PC and enter:
"adb wait-for-device shell magisk --remove-modules"
- Your device should reboot without any modules and you can install them again.
Click to expand...
Click to collapse
Im im a similar situation now, is there a way before removing the modules all i can backup them or atleast access a file or something with the modules names ?
kovacsabesz: can you please reupload the file? Thanks
Before rooting, you'll need an unlocked bootloader. Check my previous guide here: https://forum.xda-developers.com/x3...ck-bootloader-realme-x3-t4136325/post83109505.
After unlocking, we can get started with rooting.
First, you'll want to install Magisk Manager. You can find the latest APK here: https://github.com/topjohnwu/magisk/releases.
Next, you'll need to download the latest OTA OZIP. There's a link at the end of the post for this.
While that's downloading, you'll also need to grab a copy of an OZIP extractor. Follow the link below, download the repository as a ZIP, and unzip it.
For this program to work, you'll need Python 3 installed. On Linux systems, it should already be installed. On Windows 10, you can install Python from the Store.
Open a terminal or CMD window and cd to where you extracted the OZIP extractor files.
Use pip to install the docopt module: "pip3 install docopt".
Once the OZIP has finished downloading, move it to the same folder as the extractor program.
Run the following command: "python3 ozipdecrypt.py NAME_OF_OZIP_FILE". This will take a while!
Once it's done extracting, there will be a ZIP file with the same name as the OZIP. We only need two files from here: boot.img and vbmeta.img.
Extract those two files to the same folder as the extractor program.
Copy the boot.img file to your device.
Open Magisk Manager and choose the "INSTALL" option next to the Magisk status. Tap "INSTALL" in the dialog that appears and then choose "Select and Patch a File."
Browse to where you copied your boot.img to and select it. Magisk will now patch it and create a file named magisk_patched.img in your Download folder. Copy magisk_patched.img back to your computer.
Reboot your phone into fastboot: "adb reboot bootloader". If you don't have ADB or fastboot installed (which you should, since you needed them for the previous guide), you can find the link in the bootloader unlocking guide.
Before you flash the patched boot image, you need to disable image verification, which is where the vbmeta.img comes in.
Run "fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification" (remember, you'll probably need to unplug and replug the device after hitting Enter). This will disable boot verification and allow the patched image to actually work.
Finally, run "fastboot flash boot magisk_patched.img". This will flash the rooted boot image to your device.
Run "fastboot reboot" and let the phone boot back into the system. Check Magisk Manager and you should now be rooted!
Troubleshooting:
If you get an error that the boot image was "destroyed," don't worry. You'll just need to flash the stock boot.img and try again. Unplug your phone from your computer and wait for it to turn off. Once the screen is black, hold down VOL-DWN and PWR to enter fastboot mode. You can then run "fastboot flash boot boot.img" (where boot.img is the stock image) to restore. Reboot, then try the vbmeta and patched image flashing again.
You can get the OTA OZIPs from Realme EU's site: https://www.realme.com/eu/support/software-update.
You can get an OZIP extractor from here: https://github.com/bkerler/oppo_ozip_decrypt. (NOTE: you'll need to install the "docopt" Python module.)
OZIPs contain a boot.img, which you can extract and patch with Magisk for root. If someone else has an idea for patching Magisk into the boot.img, this is where to start.
Here's my patched boot.img for A.32. I don't recommend using this on other versions: https://www.androidfilehost.com/?w=files&flid=315334
Could you share your patched boot.img for the latest OS version? And could you check if the aux magisk module from X2 pro works to activate all aux cameras in Gcam? Thanks
Patched boot image
Thanks Zacharee1....Could someone upload the patched boot image for the latest one? Also do we have a generic version of twrp that can be installed on x3 ?? If yes, then we could try installing havoc gsi...
I've added a link to a patched A.32 boot.img.
also needed pip install pycryptodome win10
Zacharee1 said:
I've added a link to a patched A.32 boot.img.
Click to expand...
Click to collapse
Thanks a ton Zacharee!!
But it seems like I have A.33 version (https://www.realme.com/in/support/software-update)
I wish we had a video guide or something. Does anyone have a patched A.33 boot.img?
cheth20 said:
Thanks a ton Zacharee!!
But it seems like I have A.33 version (https://www.realme.com/in/support/software-update)
I wish we had a video guide or something. Does anyone have a patched A.33 boot.img?
Click to expand...
Click to collapse
It's pretty simple to patch it yourself. Download the OZIP, use the Python tool to unencrypt it, take the boot.img file out of the created ZIP, copy it to your device, and then patch with with Magisk Manager.
https://drive.google.com/file/d/1Od99thSd_a8sCOSpDYb0KyBLOzREiG76/view?usp=sharing
From Software Update - realme (India)
Firmware for RMX2085
I have RMX2085 model. So installing RMX2081 would be okay?
Actually I installed GSI ROM after this and now stuck with boot animation loops. Any idea if it would be okay to flash 2081 ROM else where can I get the one for 2085 version?
sukhad86 said:
https://drive.google.com/file/d/1Od99thSd_a8sCOSpDYb0KyBLOzREiG76/view?usp=sharing
From Software Update - realme (India)
Click to expand...
Click to collapse
cheth20 said:
I have RMX2085 model. So installing RMX2081 would be okay?
Actually I installed GSI ROM after this and now stuck with boot animation loops. Any idea if it would be okay to flash 2081 ROM else where can I get the one for 2085 version?
Click to expand...
Click to collapse
The firmware is the same for them all.
Great thread @Zacharee1. I have been waiting for this!
I have one question - is it mandatory to download the OTA package and do the patching? Is it because of the absence of recovery software like TWRP yet, for the X3 Super Zoom?
phonedroid said:
Great thread @Zacharee1. I have been waiting for this!
I have one question - is it mandatory to download the OTA package and do the patching? Is it because of the absence of recovery software like TWRP yet, for the X3 Super Zoom?
Click to expand...
Click to collapse
Yes, and that's why. It might be possible to pull the boot image directly from your device, but I'm not sure.
Can someone tell me if I can use realme 6 pro vbmeta.img?
realme x3 super zoom twrp recovery bro give me
Hi Sukhad,
I updated the system to the latest OTA (39), but I do not have the latest magisk patched file. Could you kindly help me with latest version patched boot for x3 superzoom?
sukhad86 said:
https://drive.google.com/file/d/1Od99thSd_a8sCOSpDYb0KyBLOzREiG76/view?usp=sharing
From Software Update - realme (India)
Click to expand...
Click to collapse
Thanks Zacharee1!
Finally did it (15/20 year old windows machines... Win7 was dificult and finally use a win8). Worth big as root gives me a new smartphone
Had all sorts of problems (installing python... But once installed was pretty quick) mainly adb conneting...
Anyway I will share vbmeta.img attached for a38 rom.
Also link to boot img, again a38.
For A38 rom
http://www.mediafire.com/file/i9jvl1al95k40vv/magisk_patched_a38.img/file
bro please could u tell me.. help
cheth20 said:
I have RMX2085 model. So installing RMX2081 would be okay?
Actually I installed GSI ROM after this and now stuck with boot animation loops. Any idea if it would be okay to flash 2081 ROM else where can I get the one for 2085 version?
Click to expand...
Click to collapse
bro please could u tell me.. after unlocking the bootloader of realme X3 superzoom , does it breaks the fingerprint sensor?
ota update after root
Someone have experiencing ota update failed on rooted device with this procedure? I m on RMX2081EU_11.A.40 but ota update to RMX2081EU_11.A.42 fails. how to update now?
Good afternoon. I want to get a root for my X3 super zoom, but I literally do not understand all the manipulations so that your description is attached with an image (screenshots). I think it will be useful for everyone who can't.
Anyone have working patched boot.img for a46?? I'm trying and always boot destroyed. Magisk 21.4
It's really weird on official en site there is a42 soft from September but on pl site there is a46 from December.
Hi guys so Many users are facing issue while they are rooted and twrp installed on there phone.
They can't able to Flash update through stock settings OR via twrp if they tries to flash it via twrp manually facing no wifi and Bluetooth.
So here is the process to flash any incremental update via twrp just we need update zip, vbmeta image and boot image of old oos version respective to your new update means if. We are upgrading to V11 we need V10 boot img
U can use following commands to extract your current stock boot img after connecting to PC
adb shell
dd if=/dev/block/sdc49 of=/sdcard/boot.img
exit
Note: Remember this process will replace your twrp and removes root to gain root access. We need to repeat twrp installation shown in the following tutorial
TUTORIAL TWRP AND ROOT NORD 2 OXYGEN OS 11 ( Links updated!)
SO finally I successfully rooted with TWRP and root access.thanks to all developers @Eastw1ng @TheMalachite Following are all download links combined in one post Also there are two threads like unlocking boot loader and twrp but there are some...
forum.xda-developers.com
You can gain root acess only by flashing magisk.zip file after step no 7 given under instructions but I didn't tested it yet.
DOWNLOADS:
1)Download update v11 from Telegram :
®D$ in OnePlus Nord 2 Community
t.me
2) DOWNLOAD V13:
®D$ in OnePlus Nord 2 Community
t.me
3) Download V14 update zip:
️ in OnePlus Nord 2 Community
t.me
4) Download A15 update zip:
e9708c8610bae8fa64d76e0f9a55dda444ce981a.zip
drive.google.com
We can also download update in system update process. Just download OTA update and when we boot in twrp just click install and then go to following folder there you will find update.zip
/data/OTA-package/update.zip
5)A17 update zip:
https://t.me/OnePlusNord2GlobalOfficial/81364
Download vbmeta:
vbmeta.img | by TheMalachite for OnePlus Nord 2 5G
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Download boot.img:
1) upgrade from v10 to v11(indian)
boot.img
drive.google.com
2) upgrade from v11 to v13(indian)
bootnew.img
drive.google.com
3)Upgrade from v13 to v14:
Rose in OnePlus Nord 2 Community
t.me
4)Upgrade from A14 to A15:
Rose in OnePlus Nord 2 Community
t.me
5)15 Boot img india (update from A15 to AA16)
https://t.me/OnePlusNord2GlobalOfficial/57795
5)A16 boot.img to upgrade to A17:
Rose in OnePlus Nord 2 Community
A16 stock boot image
t.me
6)17 BOOT IMG Upgrade to A18 (boot.img vbmeta zip extract file)
Rose in OnePlus Nord 2 Community
t.me
Boot img for nord 2 EU REGION :
File folder on MEGA
mega.nz
This another thread for all boot img of EU region
Stock Boot & Patched images Oneplus Nord 2 Oxygen 11.3 DN2103_11_A.07/09/10 EEA
Flash at your own risk. I am not responsible for any damage or data loss to the device during this process! https://mega.nz/folder/fZx2nBaR#Q33lJstFRMQg6_0j7Z0TJw Special Thanks: @HofaTheRipper @phhusson
forum.xda-developers.com
Instructions :
1) Download all file from the link given under this thread place them at one place on your phone so it can be easily accessible when we boot in TWRP.
2)Now to boot in TWRP use following root acess app called as advance reboot. Open it and click reboot to recovery
Advanced Reboot Tools [ROOT] - Apps on Google Play
Provides lots of options for restarting your device; excellent for tweakers.
play.google.com
Or you can use adb command after connecting phone to pc in USB debugging mode.
adb reboot recovery
3) when phone boot in TWRP click install tab now go to folder where we placed All files.
4) click install image tab at bottom now you we see image files boot. img and vbmeta.img that we downloaded
5)now select boot.img and then select boot partation and slide bottom bar after successful installation
6)click reboot and select recovery phone will boots back to twrp( This step is optional)
7)Now again click Install and find our old folder now select update.zip file and slide bottom bar it will take 2min for complete falshing of zip.
8)now agian click install now click install image and select vbmeta.img
9)Now click reboot system phone will reboots and take 10min.
Now you are successfully updated and have new OOS 11.3 A11 version on your phone without any issues.
Follow the video:
New update v13 update process :
New update A14 update process:
New update A15:
New update A16:
New A18 update:
pankspoo said:
Hi guys so Many users are facing issue while they are rooted and twrp installed on there phone.
They can't able to Flash update via twrp if they tries to flash it via twrp manually facing no wifi and Bluetooth.
So here is the process to flash any incremental update via twrp just we need update zip, vbmeta image and boot image of old oos version respective to your new update means if. We are upgrading to V11 we need V10 boot img.
Follow the video:
Click to expand...
Click to collapse
good Instructions! Reboot after flashing boot.img isnt necessary. OTA Update zip can be downloaded within OTA App in Settings (do not press reboot). After downloading you can reboot to TWRP and the file location is: /data/OTA-package/update.zip.
HofaTheRipper said:
good Instructions! Reboot after flashing boot.img isnt necessary. OTA Update zip can be downloaded within OTA App in Settings (do not press reboot). After downloading you can reboot to TWRP and the file location is: /data/OTA-package/update.zip.
Click to expand...
Click to collapse
Yes but I don't want to go to automatic reboot and flashing process of OTA Update installation after download which may cause some issues for new users.
The old boot.img I image is the stock one not rooted right? How can you extract it from your firmware if you're not rooted? From the Nandroid backup maybe?
Edit, found out: https://forum.xda-developers.com/t/how-to-extract-your-boot-img-from-any-rom-adb.3760210/ Just had to google it
Don't wo
Raygen said:
The old boot.img I image is the stock one not rooted right? How can you extract it from your firmware if you're not rooted? From the Nandroid backup maybe?
Click to expand...
Click to collapse
Donts worry from here every new updates we will provide all stock boot. img
Thread updated for latest update v13 for India region
HI. This is my 1st OnePlus and OxygenOS. I am now on DN2103_11_A.11 and OTA is available. It is DN2103_11_A.12
Basically I can flash it from TWRP and I do not need to save and flash boot.img afterwards bec OS will be the same version. Is that so? Or am I wrong? And I have to follow threads instructions ?
Thank you
jis251 said:
HI. This is my 1st OnePlus and OxygenOS. I am now on DN2103_11_A.11 and OTA is available. It is DN2103_11_A.12
Basically I can flash it from TWRP and I do not need to save and flash boot.img afterwards bec OS will be the same version. Is that so? Or am I wrong? And I have to follow threads instructions ?
Thank you
Click to expand...
Click to collapse
NO u need A11 boot img of only DN 2103 firmware not indian I don't have that now first flash that then flash update zip of v12 then flash Vbmeta now that's done
pankspoo said:
NO u need A11 boot img of only DN 2103 firmware not indian I don't have that now first flash that then flash update zip of v12 then flash Vbmeta now that's done
Click to expand...
Click to collapse
HI. And thx for quick reply. I mange now, thank you.
DN2103 A.11 stock boot img :
HofaTheRipper said:
DN2103 A.11 stock boot img :
Click to expand...
Click to collapse
You got it do it now
HofaTheRipper said:
DN2103 A.11 stock boot img :
Click to expand...
Click to collapse
HI and thx. I have made TWRP backup, boot and vbmeta
So I can first restore boot then flash OTA and then restore vbmeta, yes? (Version 11)
I do not have to flash boot and vbmeta, restore does the same??
jis251 said:
HI and thx. I have made TWRP backup, boot and vbmeta
So I can first restore boot then flash OTA and then restore vbmeta, yes? (Version 11)
I do not have to flash boot and vbmeta, restore does the same??
Click to expand...
Click to collapse
Don't use backup boot image restore process.
Just download above boot image given
https://forum.xda-developers.com/attachments/boot_stock_a11-img.5461307/
and vbmeta image given in. My thread
vbmeta.img | by TheMalachite for OnePlus Nord 2 5G
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
And u r update zip of device of your region not mine
First flash boot img then. Install update zip then. Flash Vbmeta done
pankspoo said:
Don't use backup boot image restore process.
Just download above boot image given
https://forum.xda-developers.com/attachments/boot_stock_a11-img.5461307/
and vbmeta image given in. My thread
vbmeta.img | by TheMalachite for OnePlus Nord 2 5G
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
And u r update zip of device of your region not mine
First flash boot img then. Install update zip then. Flash Vbmeta done
Click to expand...
Click to collapse
Thx. OK I do that.
Magisk is installed (patched) to boot image so after OTA and Vbmeta I flash Magisk to keep root.
jis251 said:
Thx. OK I do that.
Magisk is installed (patched) to boot image so after OTA and Vbmeta I flash Magisk to keep root.
Click to expand...
Click to collapse
Yes
pankspoo said:
Download boot.img:
1) upgrade from v10 to v11(indian)
boot.img
drive.google.com
2) upgrade from v11 to v13(indian)
bootnew.img
drive.google.com
Click to expand...
Click to collapse
Do the boot.img files in the original post only work on the Indian variant? Where can I get the A11 boot.img for the European variant if I want to update to A12?
NetSoerfer said:
Do the boot.img files in the original post only work on the Indian variant? Where can I get the A11 boot.img for the European variant if I want to update to A12?
Click to expand...
Click to collapse
Ok I will upload in thread
NetSoerfer said:
Do the boot.img files in the original post only work on the Indian variant? Where can I get the A11 boot.img for the European variant if I want to update to A12?
Click to expand...
Click to collapse
File folder on MEGA
mega.nz
Use boot images from stock folder
pankspoo said:
U can use following commands to extract your current stock boot img after connecting to PC
adb shell
dd if=/dev/block/sdc49 of=/sdcard/boot.img
exit
Click to expand...
Click to collapse
Still trying to wrap my head around this (although updating worked fine from A11 to A12 on my EEA variant, thanks @pankspoo!).
Can I actually extract a stock boot.img from a Magisk-rooted phone? Is it stock (in which case why is root removed by the update.zip) or is it modified (in which case, why can I extract it as stock)?
NetSoerfer said:
Still trying to wrap my head around this (although updating worked fine from A11 to A12 on my EEA variant, thanks @pankspoo!).
Can I actually extract a stock boot.img from a Magisk-rooted phone? Is it stock (in which case why is root removed by the update.zip) or is it modified (in which case, why can I extract it as stock)?
Click to expand...
Click to collapse
You can use those adb commands while booted in TWRP, without being rooted. So you'll extract the stock boot image
I have updated to ANDROID 13 in my Realme GT 5G and i have unlocked bootloader, does anyone know how to root it?
F0Xie said:
I have updated to ANDROID 13 in my Realme GT 5G and i have unlocked bootloader, does anyone know how to root it?
Click to expand...
Click to collapse
How you updated?
Please let me know how you did it.
Tanks
snorlex said:
How you updated?
Please let me know how you did it.
Tanks
Click to expand...
Click to collapse
Public Beta
For clarification, does this method not work anymore on Android 13?
How I rooted my international (EU) Realme GT 5G
I couldn't find any simple instructions for rooting so hopefully this helps someone. I'm assuming you've already unlocked your bootloader. If not, download the deep testing app (there are various apks on xda e.g. from here). Then submit the...
forum.xda-developers.com
Polo4413 said:
Public Beta
Click to expand...
Click to collapse
Hello!
Where can I download it? Can you send us a download link?
kovidancsi said:
Hello!
Where can I download it? Can you send us a download link?
Click to expand...
Click to collapse
Only for chinese rom (domestic). There's a thread on the GT forum page
I extracted the boot.img from RMX2202_11_F.02 (Android 13 global stable version) using payload dumper
You can patch it with your Magisk app (like Magisk Delta to get Magisk hide back) and then flash the patched file with fastboot :
fastboot flash boot_ab patched_boot.img
If your bootloader isn't unlocked, you need to unlock it via the deeptest apk somewhere in this forum
Also since you're in beta version, you may need to wipe to get back to stable Android 13
Altefier said:
For clarification, does this method not work anymore on Android 13?
How I rooted my international (EU) Realme GT 5G
I couldn't find any simple instructions for rooting so hopefully this helps someone. I'm assuming you've already unlocked your bootloader. If not, download the deep testing app (there are various apks on xda e.g. from here). Then submit the...
forum.xda-developers.com
Click to expand...
Click to collapse
It may not work, because the twrp provided is for Android 12, we need to wait for a TWRP Android 13
[RMX2202] Realme GT 5G (UI2.0, UI3.0 & UI4.0) - Full Package Update File
RMX2202 GDPR : UK, FR, IT, DE,ES, PL, CZ RMX2202 export : TW, TH, IN, RU RMX2202 domestic : CN How to check? Dial *#899# 👉 Software Version Realme GT 5G - Tutorial How to Convert Your ROM to Other Region using TWRP Realme UI 2.0...
forum.xda-developers.com
You can find the boot.img for your version here
boot to twrp,
then adb push Magisk-v25.2.zip /tmp
then adb shell /bin/twrp install /tmp/Magisk-v25.2.zip
and then reboot to system
callme-sy said:
It may not work, because the twrp provided is for Android 12, we need to wait for a TWRP Android 13
Click to expand...
Click to collapse
I tried it and it worked
Note that I already had Magisk root before updating to Android 13, then I simply repeated the steps like I usually do whenever there was an update for Android 12. I don't know if that makes a difference, probably not, but better to mention it I think
Hello,
I was rooted on F.02 (realui 4 - android 13). My method was to
1. go in bootloader (adb reboot bootloader)
2. boot in twrp (fastboot boot twrp.img)
3. extract boot.img (adb shell - dd if=... of=...)
4. reboot and patch the file via magisk
5. boot only with the patched boot image
6. let magisk (that in this moment has root) patch, making a backup for next otas, and root the existing installed boot image
Unfortunately from F.03, installed succesfully today via OTA, the step 4 (fastboot boot magisk_patched_boot.img) is not going anymore.
Does anyone has news for a new magisk version for android 13 (or realui4 - f.03)?
Thanks
xranix said:
Hello,
I was rooted on F.02 (realui 4 - android 13). My method was to
1. go in bootloader (adb reboot bootloader)
2. boot in twrp (fastboot boot twrp.img)
3. extract boot.img (adb shell - dd if=... of=...)
4. reboot and patch the file via magisk
5. boot only with the patched boot image
6. let magisk (that in this moment has root) patch, making a backup for next otas, and root the existing installed boot image
Unfortunately from F.03, installed succesfully today via OTA, the step 4 (fastboot boot magisk_patched_boot.img) is not going anymore.
Does anyone has news for a new magisk version for android 13 (or realui4 - f.03)?
Thanks
Click to expand...
Click to collapse
Sorry, my bad. was using wrong boot slot (boot_b instead of boot_a) for boot extrction/dump - point 3. nevermind.
bye
im on rui 4 android 14 can i open the botloader?