Related
Method was kindly shown to me by user Mefody in answer to a thread I posted.
Rooting SM-T380/T385 via Magisk Manager APK v.5.5.3 & Magisk 15.2:
1. Unpack stock firmvare ***.tar.md5 that is currently installed on your tablet (they MUST BE the same!!!).
2. Then unpack AP-block from step 1 to obtain "boot.img" file.
3. Download & install on tablet Magisk Manager APK.
4. Put "boot.img" on SDCARD.
5. Run Magisk Manager, in setiings set "Patch kernel", then setup the Magisk zip (Wi-Fi must be connected to Internet ).
6. When asked, point Magisk Manager to place on SDCARD where "boot.img" saved.
7. After some time You will get "OK".
8. Find on SDCARD file "patched_boot.img". Copy in on PC & rename to "boot.img". Then archive it to "<any name>.tar".
9. Set tablet to download mode & flash above tar-file via AP-slot of Odin-programm.
10. Tablet will reboot & ask to wipe all data to factory's params. Do it... Be noticed, that all passwords, setting, google registry will be wiped.
11. After wiping & rebooting install Magisk Manager APK again... And YEAH!!! You got root!
Thanks for creating this thread. I used the original thread to root my tab, so seeing this as its own thing will be helpful to a lot of people.
a.brooding.mage said:
Thanks for creating this thread. I used the original thread to root my tab, so seeing this as its own thing will be helpful to a lot of people.
Click to expand...
Click to collapse
Now all we need is TWRP and we'll have Xposed and custom rom support
shahmir_k said:
Now all we need is TWRP and we'll have Xposed and custom rom support
Click to expand...
Click to collapse
For TWRP: https://forum.xda-developers.com/galaxy-tab-a/development/recovery-t3426560
I will get this tab.
BTW, can it install Samsung Game Tuner?
mingkee said:
I will get this tab.
BTW, can it install Samsung Game Tuner?
Click to expand...
Click to collapse
Yes... Game Tuner installs & wokrs good.
Could you clarify on these two steps?
1. Unpack stock firmvare ***.tar.md5 that is currently installed on your tablet (they MUST BE the same!!!).
2. Then unpack AP-block from step 1 to obtain "boot.img" file.
Nerd10 said:
Could you clarify on these two steps?
1. Unpack stock firmvare ***.tar.md5 that is currently installed on your tablet (they MUST BE the same!!!).
2. Then unpack AP-block from step 1 to obtain "boot.img" file.
Click to expand...
Click to collapse
You have to open the stock firmware with an archive manager like WinRar or 7zip. Inside you should find an AP-Block folder. Inside of that should be your boot.img file
shahmir_k said:
You have to open the stock firmware with an archive manager like WinRar or 7zip. Inside you should find an AP-Block folder. Inside of that should be your boot.img file
Click to expand...
Click to collapse
Thanks, where can I find the stock firmwares?
Here is another problem
Is OEM unlock in Developer Section required to install patched kernel and TWRP with Odin?
I can't find it even it's updated.
Does anybody know if this rooting method will work with T-585 on Android 7.0 (January 2018 update)? I guess KNOX will be triggered, right?
Yours
WeT-Klb
I say the root is TOTALLY FALSE!!!
I have been waiting for two week and there's no update to enable OEM Unlock option.
I have returned the unit with restocking fee.
mingkee said:
I say the root is TOTALLY FALSE!!!
I have been waiting for two week and there's no update to enable OEM Unlock option.
I have returned the unit with restocking fee.
Click to expand...
Click to collapse
Have you tried this method even without the option in developer settings to OEM Unlock? On my SM-T350, I don't have the option to OEM unlock either. But I can still root and install TWRP anyways.
Delgoth said:
Have you tried this method even without the option in developer settings to OEM Unlock? On my SM-T350, I don't have the option to OEM unlock either. But I can still root and install TWRP anyways.
Click to expand...
Click to collapse
I tried to flash modified kernel or TWRP with Odin and I got error
Only official software can be installed.
Perhaps someone could provide boot.img files and links here?
I for instance found no matching firmwares for mine. The one that had both matching versions numbers, said it was for Cellular US. This is a wifi only model. Confused
Thanks
Barsky said:
Perhaps someone could provide boot.img files and links here?
I for instance found no matching firmwares for mine. The one that had both matching versions numbers, said it was for Cellular US. This is a wifi only model. Confused
Thanks
Click to expand...
Click to collapse
I have that original boot.img and magisk modified one.
There's a 7 days waiting period after you turned it on the first time regardless reboot or not.
I will make a instruction how to root and I will post kernel and modified kernel.
mingkee said:
I have that original boot.img and magisk modified one.
Click to expand...
Click to collapse
I didn't realize it was so effortless to pull the boot.img out. BUt, until I have that oem unlock option in there, doesn't matter.
Come on, 14 days
Finally, mine has successfully rooted with Magisk.
I will post a guide.
Trouble rooting SM-t380
shahmir_k said:
Method was kindly shown to me by user Mefody in answer to a thread I posted.
Rooting SM-T380/T385 via Magisk Manager APK v.5.5.3 & Magisk 15.2:
1. Unpack stock firmvare ***.tar.md5 that is currently installed on your tablet (they MUST BE the same!!!).
2. Then unpack AP-block from step 1 to obtain "boot.img" file.
3. Download & install on tablet Magisk Manager APK.
4. Put "boot.img" on SDCARD.
5. Run Magisk Manager, in setiings set "Patch kernel", then setup the Magisk zip (Wi-Fi must be connected to Internet ).
6. When asked, point Magisk Manager to place on SDCARD where "boot.img" saved.
7. After some time You will get "OK".
8. Find on SDCARD file "patched_boot.img". Copy in on PC & rename to "boot.img". Then archive it to "<any name>.tar".
9. Set tablet to download mode & flash above tar-file via AP-slot of Odin-programm.
10. Tablet will reboot & ask to wipe all data to factory's params. Do it... Be noticed, that all passwords, setting, google registry will be wiped.
11. After wiping & rebooting install Magisk Manager APK again... And YEAH!!! You got root!
Click to expand...
Click to collapse
When I try to flash the archived boot.tar via Odin it just hangs and sits there. Any help would be much appreciated. Thank You.
Disclaimer: Your warranty will be void, use at your own risk. YOU are choosing to make these modifications and I am not responsible for any damages these changes might do to your device or sanity.
Hi.
Based on the feedback from this thread, the following steps can be used to aquire root on the SM-T590. The process is quite similar to rooting other devices by using Magisk. It might also work on other versions of the SM-T59x family, which can be OEM unlocked (sorry Verizon users).
Obtain the boot image
Get the firmware that matches the version installed on your device. This is important, otherwise you can easily end up in a bootloop.
Extract the AP tar.md5 file, e.g. "AP_T590XXU2ARJ1_CL14463952_QB20043720_REV00_user_low_ship_MULTI_CERT_meta.tar.md5".
Upon the extracted files, there is a file called boot.img.lz4. Extract it. Important: Most standard compression tools, e.g. 7-zip, are unable to extract lz4 compression ccorrectly. Use the offical lz4 binary from your Linux distribution or get the Windows version here. Once extracted, you should have a file called boot.img.
Patch the boot image
Copy the boot.img file to your device.
Download and install the Magisk Manager apk from the offical Magisk Thread.
In Magisk Manager settings, set the image format to "img.tar".
Enable the "Keep AVB2.0/dm-verity" in the Magisk main screen.
Hit "Install" and select "Patch boot image".
Select the boot image copied previously to your device.
Once finished, the patched image will be located in the Download directory on the internal storage.
Copy the patched image back to your PC.
Unlock and flash
Go into settings and enable developer settings.
In the developer settings, select OEM unlock, read the help text and enable the unlock, if you consent.
Once the device is factory reset and rebooted, turn the device off.
Boot the tablet into download mode.
Flash the patched boot image with Odin in the AP-slot
Reboot, Install Magisk Manager apk again and check if root is available.
Have fun.
Thanks to @gscollier, @airmaxx23 and @EinsamerSpieler for testing.
Rooting works but having the same problem as the others. Modifying system files leads to reboot.... damn
J.Edwards(not the killer) said:
Rooting works but having the same problem as the others. Modifying system files leads to reboot.... damn
Click to expand...
Click to collapse
Yes, there is such problem.
I have Root Explorer app installed
When I try to move some app from "/data/app" to "/system/priv-app" (using Root Explorer) the device reboots and nothing is being saved at "/system/priv-app"
I want to make my app a system one
This method works ok on many other devices
Any ideas how to solve this problem?
I think system apps Device Security and Device Maintenance prevents me to do it.
I tried to delete them using Titanium Backup but phone reboots and they are installed again
Also there is Samsung Knox security technology
J.Edwards(not the killer) said:
Rooting works but having the same problem as the others. Modifying system files leads to reboot.... damn
Click to expand...
Click to collapse
did you find a solution?
stupid question
I know this is a dumb question but where do you get the firmware....
Also was wondering if that reboot thing is still an issue.
I'll still root, I would like to try the LineageOS, eventually... how well does this work with Android apps/F-droid?
Update: still looking for confirmation on which boot image to use... guess you can't do a backup before flashing like you used to be able to do.
I installed heimdall and adb both seem to work
heimdall instructions
User848 said:
Yes, there is such problem.
I have Root Explorer app installed
When I try to move some app from "/data/app" to "/system/priv-app" (using Root Explorer) the device reboots and nothing is being saved at "/system/priv-app"
I want to make my app a system one
This method works ok on many other devices
Any ideas how to solve this problem?
I think system apps Device Security and Device Maintenance prevents me to do it.
I tried to delete them using Titanium Backup but phone reboots and they are installed again
Also there is Samsung Knox security technology
Click to expand...
Click to collapse
the same happens to me.
I also tried removing some microsoft apps with Titanium, but after removing the excel, it goes to a kernel panic...
And then there's the "Security notice" from "SecurityLogAgent" notifications (unauthorised actions have been detected, unauthorised access to a secured area)
any solutions, followed steps but no root
I have the same problem Root is present but once i try to rename a file in /system/app, the device reboots.
Using SM-T590 with canadian image:T590XXU2ASC1
Using Magisk version V7.1.2(208) - V19.1 (19100)
I Found this procedure inside git magisk code:
https://github.com/topjohnwu/Magisk/blob/master/docs/samsung.md
Follow the Instructions part and it should work.
Quick help please, I have the patched boot image on my pc but when I click the AP slot on odin it doesnt detect it only finds tar, md5 files etc. in the settings i cant change the format to .tar there is no option.
IET_DEMO said:
I Found this procedure inside git magisk code:
https://github.com/topjohnwu/Magisk/blob/master/docs/samsung.md
Follow the Instructions part and it should work.
Click to expand...
Click to collapse
Be advised it's for Android 9 (Pie)
You can try to patch entire AP file, but I was told 19.1 may have problem. Try 18.0 first and see.
Unfortunately, there's no TWRP at this time
mingkee said:
Be advised it's for Android 9 (Pie)
You can try to patch entire AP file, but I was told 19.1 may have problem. Try 18.0 first and see.
Unfortunately, there's no TWRP at this time
Click to expand...
Click to collapse
Well I did it on android 8.1.0, seems like it work on Oreo too
IET_DEMO said:
Well I did it on android 8.1.0, seems like it work on Oreo too
Click to expand...
Click to collapse
How about Titanium Backup?
It works on rooted T510
mingkee said:
How about Titanium Backup?
It works on rooted T510
Click to expand...
Click to collapse
I dont have or use Titanium Backup, I usually clone my devices with twrp backup
There needs to be a better option that works without the current issues when rooting. You either end up with reboots or can not log in to Samsung account at all
For anyone who needs it, here's the latest tar for both stock boot and the magisk patched boot. works in Pie.
kidkrooks said:
For anyone who needs it, here's the latest tar for both stock boot and the magisk patched boot. works in Pie.
Click to expand...
Click to collapse
Would it work on 595? Bootloaders should be the same without boot loop?
vq8acsxht said:
Would it work on 595? Bootloaders should be the same without boot loop?
Click to expand...
Click to collapse
I honestly don't know as I don't have a 595. I took a chance on mine and it worked
kidkrooks said:
I honestly don't know as I don't have a 595. I took a chance on mine and it worked
Click to expand...
Click to collapse
Mine is on it's way. I will try it when I get it. I think bootloaders should be same in in both 590/595.
kidkrooks said:
For anyone who needs it, here's the latest tar for both stock boot and the magisk patched boot. works in Pie.
Click to expand...
Click to collapse
Does this still have "Modifying system files leads to reboot" issue or it's solved ?
I know Magisk can be flashed via TWRP, and that is the preferred way for me, usually. But on Magisk 19.3 I don't see an option to patch the boot.img without flashing the Magisk installer zip from TWRP. I just want to patch the img and flash it via Odin (I have a Samsung device, fastboot not available on those). I would like to keep the recovery as stock and system partition unmodified with dm-verity enabled. That way I can just use system less modules.
I normally prefer Phh's Superuser or SuperSU, I like old fashioned, traditional root without systemless or modules. But there are some tests I would like to run, and modules I would like to try.
Thanks!
It's right there if you press the install button and choose "Install"... If it it isn't on your setup you need to provide more information.
And both phh's and SuperSU are systemless root.
My setup:
Samsung Galaxy Note 4 N910F (international unbranded variant, latest stock Marshmallow firmware)
When I press install in Magisk Manager, it only offers the option to download a zip, no boot.img patching. I need the output file as tar or tar.md5, not img, so it can be flashed with Odin (no need for TWRP if flashed that way).
You're right, Phh is systemless, but it doesn't offer modules. SuperSU can be systemless or forced as system-installed.
So you don't have the "Select and patch a file" option at all? If you're looking for a specific tar file option there isn't one anymore. Just pick the file and let the Manager do the rest.
Didgeridoohan said:
So you don't have the "Select and patch a file" option at all? If you're looking for a specific tar file option there isn't one anymore. Just pick the file and let the Manager do the rest.
Click to expand...
Click to collapse
Hi, I am confused. I did use Manager 7.3.5 with Magisk 19 and now latest 20 .
When I use "select and patch a file". Use a stock boot.img file from my Tab 4 8.0 T330 Android v5.1.1 last version available. Whilst patched file is being created, a message flashes on screen img or tar file can be selected.
The problem is there is No option to "select img or tar file in output" as was the case in earlier versions of Manager v5 or 6. Which I previously used to create either patched img or tar files.
I have created different img files using the same original boot.img, only created using different Manager updates as they are created and released. Each time a new version creates a different file size.
Therefore you comment "tar file option is no more". WHY NOT.???
Next comment Just pick the file and let the Manager do the rest". Please explain or provide link to method you are referring to.
Another Question. Can I use an earlier img or tar file created on earlier Manager version with the latest Magisk version to install Magisk 20 on the Tablet. I have also used "img to tar to md5" convertor software and use ODIN to update the patched boot file, or install TWRP and use patched img file.
Any comments would be appreciated. Cheers
@BeeJ1109 It just means that the Manager will detect what type of file you're providing and outputs an img or tar file depending on the input. Tar in, tar out, etc.
There's no specific option for it in the settings anymore, since it is handled automatically now.
Didgeridoohan said:
@BeeJ1109 It just means that the Manager will detect what type of file you're providing and outputs an img or tar file depending on the input. Tar in, tar out, etc.
There's no specific option for it in the settings anymore, since it is handled automatically now.
Click to expand...
Click to collapse
Hi, Didgeridoohan, Thanks for your reply.
So I understand that if I use boot.img it will convert to patched.boot.img or patched.magisk.img.
If I use boot.tar it will convert to patched.boot.tar or patched.magisk.tar.
Question 1: So you are now saying I have to use another app to convert img to tar before patching or after patching.
Seems to me a backward function of your latest Manager, when previously you had a choice to select which option you received as the output file. So much extra time and effort to achieve the same result.
Question 2: This the case then I have to install latest manager and reinstall older version that worked. Create patched file as tar. Use ODIN to install patched boot file.
Do I need to rename magisk to boot, so ODIN will accept the patched tar file.
I use latest ODIN 13 on my Samsung Galaxy Tabs 4 & S4 and Phones S3, S4, & S8.
Question 3: Will older version created Tar file work with latest version Magisk to Root device, Then update both Magisk and Manager as normal when updates are released.
Or do I root using same version Magisk and Manager that created the patched boot file, then update to latest version.
I have successfully updated Stock and RR or Lineage OS Firmwares for years.
Samsung devices do not allow sideload installs and ODIN is so easy to use to install updates or new versions for all devices.
I also used other methods to root devices ie TWRP, Flashfire, but now Magisk is updated regularly, Hide Apps works on 7.1 thru 10, whereas old apps don't work past Android 4.4.
Thanks for your assistance, Cheers BJ.
@BeeJ1109 I know very little about Samsung so I can't really answer most of your questions, but wouldn't the file be a tar file to start with?
Anyway, if you wish for some functions to work differently than they currently do I would suggest opening a feature request issue in GitHub (with a detailed description of what you want).
Any solution?
Hi there, i know this is an old thread, but i was wondering if anyone found a solution for this.
I am also trying to install Magisk Manager, modifying the boot.img file from my firmware. The problem i find is that the boot.img is inside a boot.img.lz4 (which i open with the modified 7zip), and that is inside another img.tar file.
Now, i seem to understand the old Magisk Manager (version 6 for example), would allow to decide the output file, while the v7 does not anymore. I would just receive a repatched_boot.img file, which i cannot use to flash using Odin.
I also tried installing Magisk v6, but it will force to update upon doing the repatching.
Do you have any other solution?
PS: all reason i'm trying to do this is trying to install (any) TWRP on my tablet SM-P580 will show a blue/black screen.
walty80 said:
Hi there, i know this is an old thread, but i was wondering if anyone found a solution for this.
I am also trying to install Magisk Manager, modifying the boot.img file from my firmware. The problem i find is that the boot.img is inside a boot.img.lz4 (which i open with the modified 7zip), and that is inside another img.tar file.
Now, i seem to understand the old Magisk Manager (version 6 for example), would allow to decide the output file, while the v7 does not anymore. I would just receive a repatched_boot.img file, which i cannot use to flash using Odin.
I also tried installing Magisk v6, but it will force to update upon doing the repatching.
Do you have any other solution?
PS: all reason i'm trying to do this is trying to install (any) TWRP on my tablet SM-P580 will show a blue/black screen.
Click to expand...
Click to collapse
Hi.
Use Magisk Manager to create a modified stock boot.img. as you have mentioned.
What I do is search for Windoows PC "img to tar converter" app. on Google search.
Lots will be found. They a small executable batch file. Which you Right click on the "convert tar".exe file to run on a Windows PC.
Best one will have Input and Output directories. You can inset your patched boot .img file, you have just downloaded for your device. Add this file into Input directory of the app using Windows Explorer File Manager. May have to setup the location of resultant output directory. Then run Img to Tar converter . The application will convert your patched_boot img file into a patched_boot.tar file.
That newly modified .tar can now use ODIN. To install patched_boot.tar onto your connected device via PC USB port using the Latest version of ODIN 3.14.1.
Hope that helps. CHEERS
One of the things I missed most since moving to Oreo and Pie on the Note 4 has been trying out the new ROMs without having to mess with my daily driver setup. After a ton of research and some training on building ROMs from source, I was finally able to make Android Pie boot from any slot on Dualboot patcher. *
What you need?
* An Android Pie ROM
* Android Image Kitchen (AIK)
* modified device tree binary (dtb)
* a text editor
* RAR or some other zip file manager.
Instructions
1) Download and extract AIK from https://forum.xda-developers.com/showthread.php?t=2073775
2) extract the boot.IMG from your ROM to the same folder where you extracted AIK.
3) unpack the boot image using the unpackimg.sh script. This will create a split_img folder and a ramdisk folder.
4) go to the split_img folder and delete boot.img_dt (or boot.img_dtb depending on which version of AIK you are using).
5) copy the attached dtb.img file to the split_img folder and rename it to the original file name (boot.img_dt or boot.img_dtb)
6) go to the ramdisk folder and edit fstab.qcom. change this line:
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,barrier=1 wait,recoveryonly
To this:
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,barrier=1,discard wait
7) still in the ramdisk folder, modify init.qcom.rc. change this line **:
mount_all fstab.qcom
To this:
mount_all /fstab.qcom
8) go back to the AIK folder and run repacking.sh. this will create a file called image_new.img.
9) rename image_new.img to boot.img
10) replace the boot.img in your ROM zip file with the new one you just created.
Now you can use DualBoot Patcher to patch the ROM file for any slot and flash the patched file.
Just a few extra notes here:
* I only built these images for Android Pie for Snapdragon Note 4 devices. Make sure you use the the correct file for your device.
** in step 7, I noticed that some ROMs have an earlymount flag. You must delete that flag, otherwise the phone reboots to download mode.
***If anyone has any ideas to make this a flashable process, let me know. I would push these change upstream, but I don't know know enough about Git to do that. And, I don't know if the other devs want these changes.
Ok, so that was the manual way, but these changes can also be added to the kernel and boot image files at the time you build your ROM. Here is where you make the changes:
In the kernel, go to the dts sources. The file to modify is this one:
kernel/samsung/apq8084/arch/arm/boot/dts/qcom/aps8084.dtsi
Find this section and delete it:
Code:
system {
compatible = "android,system";
dev = "/dev/block/platform/msm_sdcc.1/by-name/system";
type = "ext4";
mnt_flags = "ro,barrier=1,discard";
fsmgr_flags = "wait";
status = "ok";
};
In the boot image, there are 2 files to modify.
1) device/samsung/trlte-common/rootdir/etc/fstab.qcom
Change this line:
Code:
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,barrier=1 wait,recoveryonly
to this:
Code:
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,barrier=1,discard wait
2) device/samsung/trlte-common/rootdir/etc/init.qcom.rc
Change this line:
Code:
mount_all fstab.qcom
to this:
Code:
mount_all /fstab.qcom
That's it. Build the ROM and it will be compatible with DualBoot Patcher. Since those are common files across the TRLTE, TBLTE and DUOS devices, all of those builds will be compatible with dualboot patcher.
So, one more thing. There are limitations to what you can install with DualBoot Patcher. Most things are easy to get around, though.
1) Flashable zip's that use Aroma installer might not change their behavior after being patched, and might install to your primary ROM slot anyway. Just something to be aware of.
2) Any flashable zip that has a custom script for updater-binary will fail to flash after being patched. For example, all the MicroG installers that I know of use custom scripts instead of the real updater-binary.
3) you cannot install a patched Magisk zip. But, you can install the Magisk Manager in your ROM, tap the install button (and the next install button that shows up), choose "Select and Patch a file", then choose the boot image from the Multiboot folder on your internal storage (/sdcard). It will patch the boot image and leave a file called "magisk_patched.img" in your Download folder on the internal storage (/sdcard). Use TWRP to flash this file to your boot partition, then reboot. Open DualBoot Patcher, tap the 3-dot button next to the ROM name, and tap "Set Kernel" to replace the saved boot image with the Magisk patched boot image. Note: if you accidentally
4) Magisk doesn't do much. You can use it to grant superuser permissions, but modules only work on the primary ROM.
5) custom kernels probably include their own dtb files. Flashpoint is an example of this. You may have to update the zip to remove the existing dtb file and add one of the files attached to OP. Make sure you rename it to match the original name in the zip file.
I set up my primary ROM per the above instructions, installed it, and I am trying to get my secondary rom installed. Do I need to set it up the same way (it is a 7.1.2 rom). When I patch it (7.1.2) through Dual Boot and try to flash it I get the following error.... " Failed to create temporary image /raw/data/.system.img.tmp" and it fails to flash. I've tried setting it both as secondary and in slot 1.... Any help would be appreciated... Hopefully I am just missing something simple.
rickpub said:
I set up my primary ROM per the above instructions, installed it, and I am trying to get my secondary rom installed. Do I need to set it up the same way (it is a 7.1.2 rom). When I patch it (7.1.2) through Dual Boot and try to flash it I get the following error.... " Failed to create temporary image /raw/data/.system.img.tmp" and it fails to flash. I've tried setting it both as secondary and in slot 1.... Any help would be appreciated... Hopefully I am just missing something simple.
Click to expand...
Click to collapse
What Rom are you trying to flash? Do you have enough space available on system or cache to flash that Rom? If not, try patching it for a data slot instead.
thanks
why when i do this the rom that have modified wont turn wifi on ?
n910f
i try it on linageos pie and havocos 2.8 and both have same issue after doing this solution
samdakid said:
thanks
why when i do this the rom that have modified wont turn wifi on ?
n910f
i try it on linageos pie and havocos 2.8 and both have same issue after doing this solution
Click to expand...
Click to collapse
That's really odd. Maybe I need to update the dtb images here. I will try to do that this weekend.
Would love to try this out
Pre requisites
• Unlocked Bootloader (probably only Indian variant?)
• ADB and Fastboot drivers (I'm assuming you've set that up since you unlocked bootloader)
• Python (used to extract boot image)
• Your stock rom (I found it here: https://realmefirmware.com/)
• time (need some time to download your stock rom and get a hold of your boot image)
Steps:
1) Download Oppo_Decrypt tool from here:
https://github.com/bkerler/oppo_decrypt
2) Extract the contents and place in a folder
3) go to that folder and open a command prompt/power shell in the folder
4) Use commands accordingly
If you've added pip to path:
pip install -r requirements.txt
If you've not added pip to path:
Python -m pip install -r requirements.txt
done? Everything installed?
now get your rom zip file, inside it you'll find a big .ofp file, extract that ofp file and place in the folder where you've extracted your tools
now inside this very folder where ur tools are, create another folder and name it "extract" (tbh u can name the folder anything you want but for the sake of explanation I named it that)
now open a command prompt in the folder where the tools are kept
type: Python
Press space
drag and drop the "ofp_qc_decrypt.py" file in the command prompt
Press space
Drag and drop the large .ofp file you extracted
Press space
Drag and drop the extract folder
Press enter
Wait for a while till there's a message saying
"Extracting super.img" or something along the lines
Exit out of command prompt
Go to the extract folder you'll see a file called "boot.img"
Send this boot.img file to your phone
(Also recommend keeping a copy of the boot.img on your PC for safety)
Install Magisk Manager Apk from the official website on your phone
Open Magisk manager
Click on Install
Click on select and patch a file
Choose the boot.img file you just sent from your PC
after done send the magisk_patched.img to your PC
Now boot your phone into Fastboot mode
(I'll assume you know how to since you've unlocked bootloader)
Connect your phone to your PC using USB cable
open a command prompt and check if your device is connected by typing:
fastboot devices
if it shows up then proceed
type:
fastboot flash boot magisk_patched.img
(Your file name can be different you can just drag and drop the file)
after it says success, type:
fastboot reboot
after reboot open Magisk manager app (might ask u to download?)
and reboot if it asks you to
Congratulations you now have root access!
How to extract images from OTA zip files:
Extract the OTA zip file
Download and extract payload-dumper-go
Drag and drop payload.bin on payload-dumper-go executable
Spoiler: Video instructions
//seems to work for others, i thought it's only for indian roms, because of other posts and EU was locked out for so long, seems to work for EU, too.
IMEI and Baseband only get lost if you unlock the bootloader with the wrong version or boot.img.
smashda said:
BEWARE:Only Indian variant, you lose your IMEI and Baseband!
Click to expand...
Click to collapse
I test it on RMX3311 EU and work fine.
Deleted
Can we make a boot.IMG for the RMX3311 so we can flash in Magisk ?
Hello,
Is there a easy way to hide banking apps some function don't work because my device is unlocked.
karayemis said:
Can we make a boot.IMG for the RMX3311 so we can flash in Magisk ?
Click to expand...
Click to collapse
It is the same method to extract boot image just get your corresponding rom and either use oppo decrypt tool if on version the phone ships with otherwise use payload dumper with correct ota
karayemis said:
Hello,
Is there a easy way to hide banking apps some function don't work because my device is unlocked.
Click to expand...
Click to collapse
Safetynet fix may help but you need root
BR4UTAL said:
It is the same method to extract boot image just get your corresponding rom and either use oppo decrypt tool if on version the phone ships with otherwise use payload dumper with correct ota
Click to expand...
Click to collapse
Hi,
Thanks, worked for me my device it is rooted now and banking apps are working now.
Device: RMX3311 EU
2 more questions:
1. is there a module i can use to activate call recorder on google dialer ?
2. When there is a new OTA can I just install and repeat all above ?
karayemis said:
2 more questions:
1. is there a module i can use to activate call recorder on google dialer ?
2. When there is a new OTA can I just install and repeat all above ?
Click to expand...
Click to collapse
When there is an ota update download it from software update and wait for it to finish extracting
DO NOT CLICK ON INSTALL
Go into Magisk
Do Uninstall Magisk > Restore System Images
Now Click on Install Magisk > Click Install to Inactive slot (after ota)
click ok and let's go
DO NOT CLICK ON THE REBOOT BUTTON
Now go to software update and click Install, your phone will reboot with root available still and ota update applied
For the model 3311 (EU) is there a step by step guide for root? Please, if exists, drop it here. Thank you
geovision said:
For the model 3311 (EU) is there a step by step guide for root? Please, if exists, drop it here. Thank you
Click to expand...
Click to collapse
The process is the same but instead of IN rom you need to get boot image from EU rom
karayemis said:
Hi,
Thanks, worked for me my device it is rooted now and banking apps are working now.
Device: RMX3311 EU
Click to expand...
Click to collapse
Banking app stops working after a while, this is the second time it stopped working.
karayemis said:
Banking app stops working after a while, this is the second time it stopped working.
Click to expand...
Click to collapse
Here's the Thread for it, you can just use the search on top of the page for things you want to fix, the banking issues come with root and you can find the appropriate Threads when searching for Magisk.
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com
Currently iam on this version rmx3312_11_A.20 of realme ui so how can i get the boot image of this version
_PsyDuck_ said:
Currently iam on this version rmx3312_11_A.20 of realme ui so how can i get the boot image of this version
Click to expand...
Click to collapse
The Ota server only offers the latest version of Android 12 with the A.22 software