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?
Related
Can anyone provide a guide to install Magisk root on Honor 9 with Oreo B360.
I did search here but didn't find it anywhere.
Thank you.
This magisk 15.4 fully works with honor 9 :
https://forum.xda-developers.com/showthread.php?t=3749280
I'm waiting for someone to confirm everythings also work on magisk 16.0 ; I think one user told it didn't.
oslo83 said:
This magisk 15.4 fully works with honor 9 :
https://forum.xda-developers.com/showthread.php?t=3749280
I'm waiting for someone to confirm everythings also work on magisk 16.0 ; I think one user told it didn't.
Click to expand...
Click to collapse
So, can I just install Magisk zip file with Twrp or do I need to do something else?
It you read the link i sent you, you'll see:
"Instructions
If your device have TWRP support, just directly flash it via TWRP. For devices without TWRP yet (currently all Huawei Treble devices), you can follow the instructions below)"
I didn't tried the twrp way, I did the fastboot way as I did not had a twrp when i did it.
1) Unlock your device (if you haven't not already)
2) Install this TWRP: https://forum.xda-developers.com/honor-9/development/oreo-t3754483
3) Install last version of magisk from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Via custom recovery:
Download the latest Magisk zip file
Reboot to a custom recovery and flash the flashable zip
Reboot to system, and check whether Magisk Manager is installed and the version matches the latest one in the OP
If for some reason Magisk Manager isn't installed/upgraded automatically, please install/upgrade it manually!
Click to expand...
Click to collapse
I've done this and all working well on B360.
@WFree So you confirm : root, hide root & safetynet checks work fine on Magisk v16.0 with honor 9 on oreo ?
(They do on 15.4(1541))
oslo83 said:
@WFree So you confirm : root, hide root & safetynet checks work fine on Magisk v16.0 with honor 9 on oreo ?
(They do on 15.4(1541))
Click to expand...
Click to collapse
Yes.
Proof here: https://forum.xda-developers.com/showpost.php?p=75689044&postcount=12
The patched image is only 8 mo, is it ok?
How are things going with the OTA updates?
So, using method from " [OFFICIAL] Magisk v16.0 - Root & Universal Systemless Interface [Android 5.0+] " I use adb command , the first is ok
Copy the patched boot image to your PC. If you can't find it via MTP, you can pull the file with ADB:
adb pull /sdcard/MagiskManager/patched_boot.img
When I try the second :
Flash the patched boot image to your device and reboot. Here is the command if using fastboot:
fastboot flash boot /path/to/patched_boot.img
I get this message : " < waiting for any device >
Can you help me for that ?
I'm using stock rom , STF L09 8.0.0 360 / c432 to be exact
Thanks !
EDIT : Did I need unlocked bootloader to flash patched boot image ?
sonneper said:
So, using method from " [OFFICIAL] Magisk v16.0 - Root & Universal Systemless Interface [Android 5.0+] " I use adb command , the first is ok
Copy the patched boot image to your PC. If you can't find it via MTP, you can pull the file with ADB:
adb pull /sdcard/MagiskManager/patched_boot.img
When I try the second :
Flash the patched boot image to your device and reboot. Here is the command if using fastboot:
fastboot flash boot /path/to/patched_boot.img
I get this message : " < waiting for any device >
Can you help me for that ?
I'm using stock rom , STF L09 8.0.0 360 / c432 to be exact
Thanks !
EDIT : Did I need unlocked bootloader to flash patched boot image ?
Click to expand...
Click to collapse
UP !
is there many people using Magisk on Honor 9 ? some experiences ?
Sorry for that, but same question : Did I need unlocked bootloader to use fasboot command with adb method ? It's only write : " no need root, no need custom recovery "
thanks !
I think you need unlocked bootloader to be able to flash image through fastboot.
So with the adb command you pulled the patched boot from your phone to your computer.
Now about the fastboot command ; the fact you get a '< waiting for any device >' means your phone isn't on bootloader, or isn't connected while you issue that command.
You could type :
' fastboot devices ' to test your fastboot connection while your phone is booted in bootloader aka fastboot mode.
---------- Post added at 21:31 ---------- Previous post was at 21:27 ----------
By the way l'm on honor 9 with magisk and all is working great ! (magisk 15.41 then 16.00)
Ok, thanks for your answer , I've try again and I can use fastboot command . Is no problem with patched image who is only 8mo vs 16mo for original ?
sonneper said:
Is no problem with patched image who is only 8mo vs 16mo for original ?
Click to expand...
Click to collapse
No problem
: ) Now, i know what I have to do ! Thanks !
someone have stock boot.img STF L09 8.0.0 360 / c432??
https://forum.xda-developers.com/honor-9/help/stock-boot-imf-b360-oreo-t3756967
Bla bla
oslo83 said:
By the way l'm on honor 9 with magisk and all is working great ! (magisk 15.41 then 16.00)
Click to expand...
Click to collapse
How do you did that? Do you have TWRP on your H9 or did you use fastboot way?
Thanks!
Fastboot way, but i heard twrp way was also working.
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.
This article is for those of you who are using android 11 version, and have problems that can't work with old version twrp, you can't root the device.
This is the auto root link for devices using android 11 version, joyui 12.5 global.
Using:
way 1. Just open usb debugging, and open file [Click_Run] enter number 1 and wait for device to reboot and check root.​way 2. boot device into start mode (bootloader - fastboot) .. and open file [Click_Run] enter number 2.. and wait for device to reboot, check root.​
Click to expand...
Click to collapse
Good luck to you, with other versions you can message me, I will make another similar file. This is the solution for devices that can't click twrp, twrp is not compatible, twrp doesn't work, can't install root.zip at twrp.
Link Mega preventive
Hello,
Just a question to see if I am mistaken. Those using Android 11 can't have TWRP or is it just that they can't root with TWRP? (cause I want to know if I should upgrade or not, and I won't without a recovery)
do you have file for bs3 global 8/128
do you have for bs3 8/128
I've just received today the 10T 5G CPH2415.
I unlocked the bootloader in the same way as the Oneplus 10Pro
in settigs OEM unlock and ADB Debug.
by Powershell:
adb devices
Adb reboot bootloader
fastboot devices
fastboot flashing unlock
in case of issue on installing the driver, in fastboot mode, on win11, you need to reboot Windows in the mode "Disable driver signature enforcement"
when the phone is started, reboot again in fastboot then I booted it with the boot.img of the indian version which I found (I patched it with Magisk 25.2).
fastboot devices
fastboot boot patched_boot.img
when it stared, I patched it with Magisk directly.
____________________________
Firmware updating (Full update) keeping the Root:
by using "oneplus local update for android 12" the root can be kept.
Install the firmware with oplocal, dont reboot, open magisk flash it on the second slot; only now you can reboot.
DON'T REBOOT after the FW installation.
The firmware can be downloaded through the app Oxygen Updater. (Full update)
---------------------------
Attachment:
Boot Patched 10T from Indian version img
OPLocal Update for Android 12 apk
Stock boot A06 CPH2415 img
Patched Boot A06 CPH2415 (Magisk 25.2) img
Marco589 said:
I've just received today the 10T 5G CPH2415.
I unlocked the bootloader in the same way as the Oneplus 10Pro
in settigs OEM unlock and ADB Debug.
by Powershell:
adb devices
Adb reboot bootloader
fastboot devices
fastboot flashing unlock
in case of issue on installing the driver, in fastboot mode, on win11, you need to reboot Windows in the mode "Disable driver signature enforcement"
when the phone is started, reboot again in fastboot then I booted it with the boot.img of the indian version which I found (I patched it with Magisk 25.2).
fastboot devices
fastboot boot patched_boot.img
You followed this guide
https://www.droidwin.com/root-oneplus-10t-via-magisk-patched-boot-img/
or did you only flash the patched boot.img?
Click to expand...
Click to collapse
You followed this guide
https://www.droidwin.com/root-oneplus-10t-via-magisk-patched-boot-img/
or did you only flash the patched boot.img?
slavekve said:
You followed this guide
https://www.droidwin.com/root-oneplus-10t-via-magisk-patched-boot-img/
or did you only flash the patched boot.img?
Click to expand...
Click to collapse
Don't follow that guide. You just need to boot (not flash) a patched boot image and then run direct install. This also creates backups of your stock images which you'll need when you OTA.
EtherealRemnant said:
Don't follow that guide. You just need to boot (not flash) a patched boot image and then run direct install. This also creates backups of your stock images which you'll need when you OTA.
Click to expand...
Click to collapse
It is true that when rooting the OnePlus 7 pro I only flashed the repaired boot.img. I was surprised that Sadique Hassan recommends otherwise for this model.
slavekve said:
It is true that when rooting the OnePlus 7 pro I only flashed the repaired boot.img. I was surprised that Sadique Hassan recommends otherwise for this model.
Click to expand...
Click to collapse
Again, DON'T flash the patched image! You must use the direct install method in Magisk after booting the patched image.
EtherealRemnant said:
Again, DON'T flash the patched image! You must use the direct install method in Magisk after booting the patched image.
Click to expand...
Click to collapse
I understand that, but in the instructions, the repaired vendor_boot.img is also flashed. Oneplus 7 Pro does not contain vendor_boot.img file in payload.bin
slavekve said:
I understand that, but in the instructions, the repaired vendor_boot.img is also flashed
Click to expand...
Click to collapse
Are you not listening to me? I just told you how to do it. Boot the patched image and run the direct install. Magisk installer will do what needs to be done for you. This is also the same thing the OP has done. Ignore those other instructions you found, they are incorrect and pose problems when you take OTA updates as OnePlus is moving away from full OTAs to incremental ones that will not flash to a phone with modified images.
For the record, patched dtbo and vendor_boot are needed as well but Magisk does this for you.
Ok, I will follow the instructions above when my phone arrives
any way to activate 5g & volte on non supported carriers - countries?
akaloith said:
any way to activate 5g & volte on non supported carriers - countries?
Click to expand...
Click to collapse
Unlock the bootloader, Install the Global ROM that supports 17 5G Bands both SA & NSA. Which Country you are in ?
Marco589 said:
I've just received today the 10T 5G CPH2415.
I unlocked the bootloader in the same way as the Oneplus 10Pro
in settigs OEM unlock and ADB Debug.
by Powershell:
adb devices
Adb reboot bootloader
fastboot devices
fastboot flashing unlock
in case of issue on installing the driver, in fastboot mode, on win11, you need to reboot Windows in the mode "Disable driver signature enforcement"
when the phone is started, reboot again in fastboot then I booted it with the boot.img of the indian version which I found (I patched it with Magisk 25.2).
fastboot devices
fastboot boot patched_boot.img
when it stared, I patched it with Magisk directly.
Click to expand...
Click to collapse
I have 10T Global, Indian and Chinese ROM Full Package ZIP file, I want to try Global & Chinese ROM on Indian 8/128GB Version
already unlocked bootloader, if I Flash Global or Chinese ROM will my device brick ?
As previously I was using MSM Download Tool which was free now it need authentication, so shifted to Fastboot Enhance
Will the process of flashing via payload.bin brick my device ?
Today it is possible to download EU full package CPH2315_11_A.06 using Oxygen updater
slavekve said:
Today it is possible to download EU full package CPH2315_11_A.06 using Oxygen updater
Click to expand...
Click to collapse
I already root mine OP10T Model CPH2415 which is international ROM but i tried to flash that CPH2315 in Oxygen Updater it was a success but the model of my phone was change also from CPH2415 to CPH2315.
I have OP8T Cyberpunk Edition Which Is Chinese ROM and i Flash Global ROM the thing is it change only the Build number which is right and the model Number still The same KB2000 but this OP10T is different including the model was change when i flash. Anyway it was a success but it shouldn't be like that.
ryu091 said:
I already root mine OP10T Model CPH2415 which is international ROM but i tried to flash that CPH2315 in Oxygen Updater it was a success but the model of my phone was change also from CPH2415 to CPH2315.
I have OP8T Cyberpunk Edition Which Is Chinese ROM and i Flash Global ROM the thing is it change only the Build number which is right and the model Number still The same KB2000 but this OP10T is different including the model was change when i flash. Anyway it was a success but it shouldn't be like that.
Click to expand...
Click to collapse
So that mean all 10T devices are China made and later flashed with region specific firmware's.
slavekve said:
It is true that when rooting the OnePlus 7 pro I only flashed the repaired boot.img. I was surprised that Sadique Hassan recommends otherwise for this model.
Click to expand...
Click to collapse
Hi @slavekve , Sadique this side, sorry for the confusion. Till the OnePlus 9, you only needed to flash the patched boot.img for root.
But with the OnePlus 10 series [10 Pro], flashing patched vendor_boot and vbmeta for disabling verity seems to have become an additional requirement in numerous instances.
But thanks to @Marco589 for letting us know that he has already achieved root without the vbmeta and vendor. Henceforth I have updated my post accordingly as well.
Guys, I have a CPH 2413 device and have tried several times to unlock bootloader... But fastboot commands do not work on my device. Have tried "OEM unlock" as well "flashing unlock" through fastboot. Updated the fastboot and adb drivers, tried to do it through platform tools as well... Got my device replaced as well after the first one didn't get unlocked...
Help needed please
gonetask said:
Unlock the bootloader, Install the Global ROM that supports 17 5G Bands both SA & NSA. Which Country you are in ?
Click to expand...
Click to collapse
I am in greece and carrier vodafone
will i sure have 5g and volte? cause device is not supported by vodafone greece
SREEPRAJAY said:
Guys, I have a CPH 2413 device and have tried several times to unlock bootloader... But fastboot commands do not work on my device. Have tried "OEM unlock" as well "flashing unlock" through fastboot. Updated the fastboot and adb drivers, tried to do it through platform tools as well... Got my device replaced as well after the first one didn't get unlocked...
Help needed please
Click to expand...
Click to collapse
I came across to the same issue, I solved by adding ".\":
.\fastboot devices
.\fastboot flashing unlock
PS
did the OS install the driver of the phone in fastboot mode?
Marco589 said:
I came across to the same issue, I solved by adding ".\":
.\fastboot devices
.\fastboot flashing unlock
PS
did the OS install the driver of the phone in fastboot mode?
Click to expand...
Click to collapse
.\ does not work. Can you please explain which tool you used? or how you managed?
Hello everyone hope you are all keeping well.
Since I believe that many of you don't know about this, I've decided to share the steps I've done in order to root the OP 11R ( ACE 2 )
I cannot be responsible if you brick your device. Your phone, your choices, your responsibility!
1 - Unlock the bootloader (if you haven't done it already...beware that this will erase all of your user data). To do so, you must:
Enable developer options
Enable the "OEM unlocking" option
Enable USB debugging
Have both adb and fastboot, from SDK Platform Tools available on your PC
Connect your phone to your PC using the USB cable and run the following commands:
adb devices
adb reboot bootloader
(so your phone will reboot into fastboot mode)
fastboot flashing unlock
(device should now unlock)
fastboot reboot
(device reboots with an unlocked bootloader and data partition wiped so set up the device from scratch again)
2 - Download OP 11R stock boot.img that you may find later on this post, that matches your current build.
Copy the boot.img to your devices internal memory
Leave a copy of it on your PC (on the same folder you have adb and fastboot...you never know if you will need to use it again in the future...to restore the stock boot.img, aka revert to stock...)
Indian Boot.img A_0.8 - download
3 - Download latest Magisk Manager from HERE and install it on your phone
4 - Open Magisk Manager App and press:
Install
Select and Patch a File
Browse to the path where you saved stock boot.img and select it
Magisk Manager will now patch the boot image and store it in [Internal Storage]/Download/magisk_patched.img
5 - Copy the patched boot image from your device to your PC (Store it on the same folder where you have adb and fastboot)
6 - Flash the patched boot image to your phone by running these commands (remember, you must have patched boot image on the same folder you have adb and fastboot and, of course, your device must be connected to your PC...)
adb reboot bootloader
fastboot flash boot magisk_patched.img
fastboot reboot
7 - After the phone boots up, hopefully with a normal boot (almost feels like nothing happened....), install/open Magisk Manager App again and watch Magisk doing it's magic!
8 - Enjoy!
All credits goes to topjohnwu and his incredible work with Magisk.
Why title says NORD 2T?
firoz3321 said:
Why title says NORD 2T?
Click to expand...
Click to collapse
MB ... typo
Thank you for detailed steps.
Is there any benefit with KernelSU over this method ?
I always used Magisk on OP8, but recently saw an article for OP11 with Kernel SU.
Also is there MSM tool support to recover softbriked device ?
firoz3321 said:
Thank you for detailed steps.
Is there any benefit with KernelSU over this method ?
I always used Magisk on OP8, but recently saw an article for OP11 with Kernel SU.
Also is there MSM tool support to recover softbriked device ?
Click to expand...
Click to collapse
Sorry but there is no msm tool available for new OnePlus devices. + You can use Fastboot enhance tool from github to recover softbrick , magisk is always recommended for rooting because of ease of steps and simple to use
Hello, thanks for the detailed instructions. Today I updated to A. 10, and unfortunately lost my root access. Without the root cannot extract the boot image. If you're already updated and have a backup of A. 10 boot, can you please share?
saifsohel said:
Hello, thanks for the detailed instructions. Today I updated to A. 10, and unfortunately lost my root access. Without the root cannot extract the boot image. If you're already updated and have a backup of A. 10 boot, can you please share?
Click to expand...
Click to collapse
i didn't got the update yet ... + oxygen updater also showing A.08. i will update this post soon as I got update
shiki_senpai said:
i didn't got the update yet ... + oxygen updater also showing A.08. i will update this post soon as I got update
Click to expand...
Click to collapse
Then remember to take a backup of the boot before rebooting. I messed up big time.
Thanks for the detailed information man. Can I know if bootloader unlock decreases widevine L1 to L3? As this was case with my OP6