Database Info

XT1575 February 2016 Security Update OTA (24.201.3.en.US) + Updated Stock ROM

Pulled from my US X Pure Edition.
Place in Internal Storage and flash in recovery.
Untested with flashing via TWRP as I've waited all day on complete stock ROM to capture and pull this zip.
MUST BE ON STOCK RECOVERY TO FLASH IT. If you flash it in TWRP and boot loop, without making a backup beforehand, you're on your own. You should've made a backup AS ALWAYS.
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
February 2016 Security Update OTA
Google Drive: blur_version.24.11.18.clark_retus.retus.en.us (flash in stock recovery ONLY)
MD5: e08d5e837d59d9b4ecd88f15ba2906f7
Stock odexed ROM with the February 2016 Security Update applied. No root. Flash in TWRP.
Google Drive: stock_marshmallow_for_moto_x_pure_edition-mphs24.49-18-3 (flash in TWRP)
MD5: 2a1505d2626aa1ef1d18da904a3d5093
Modified boot.img post for use with traditional SuperSU root by DaMadOne here:
http://forum.xda-developers.com/showpost.php?p=65541582&postcount=61
Stock 6.0 Marshmallow Recovery:
IMG version
Google Drive: stock-6.0-mph24.49-18-recovery.img (flash in fastboot or TWRP)
MD5: 2ac9b589a3dc14d4000cbbe082b36ba9
ZIP version
Google Drive: stock-6.0-mph24.49-18-recovery.zip (flash in TWRP)
MD5: a59bb1d9eca25608658cd67f7b4707c2
NOTE: If you get "No command" while booting into stock recovery, hold the power button and press up on the volume key. Options should now be available. I'm not sure why it does that but it used to do it on Nexus devices (and probably still does.)

Spasticdroid said:
Pulled from my US X Pure Edition.
Place in Internal Storage and flash in recovery.
Untested with flashing via TWRP as I've waited all day on complete stock ROM to capture and pull this zip.
Screenshots:
Google Drive: blur_version.24.11.18.clark_retus.retus.en.us
Click to expand...
Click to collapse
So is this captured ota or a stock twrp backup

Google~Android said:
So is this captured ota or a stock twrp backup
Click to expand...
Click to collapse
Spasticdroid said:
capture and pull this zip.
Click to expand...
Click to collapse
It's the OTA.

Hi do you know how to flash this using twrp? I tried and it failed. Thank you in advance.

Hey dude, I just got the notification. I'm using the stock ROM, rooted and obviously bootloader unlocked, also using xposed, do you know if it's safe for me to install the update from the notification? I just don't want to screw it and start from scratch.

I flashed supersu 2.66 as I had done previous but wouldn't boot past the logo. Anyone gotten this rooted?
Nexus 10

Vinrock2244 said:
Hi do you know how to flash this using twrp? I tried and it failed. Thank you in advance.
Click to expand...
Click to collapse
What error? Where's your recovery log?
Doesn't work with TWRP 3.x? Use an older version.
Doesn't work with the older TWRP 2.x? Use TWRP 3.x.
Not working with TWRP period? Flash stock recovery, flash the OTA, put TWRP back.
blkcr said:
Hey dude, I just got the notification. I'm using the stock ROM, rooted and obviously bootloader unlocked, also using xposed, do you know if it's safe for me to install the update from the notification? I just don't want to screw it and start from scratch.
Click to expand...
Click to collapse
I don't use Xposed so I wouldn't know if the OTA will work even after uninstalling it. Also, if you're not using systemless root, you'll have to wipe clean. Back up data apps using Titanium or similar. Systemless root however restores original kernel and files.
rocketsaucev2 said:
I flashed supersu 2.66 as I had done previous but wouldn't boot past the logo. Anyone gotten this rooted?
Nexus 10
Click to expand...
Click to collapse
2.67 systemless works fine.

Spasticdroid said:
2.67 systemless works fine.
Click to expand...
Click to collapse
Do you have a link handy? Is it just twrp flashable?
Nexus 10

Also in for a twrp flashable version

rocketsaucev2 said:
Do you have a link handy? Is it just twrp flashable?
Nexus 10
Click to expand...
Click to collapse
Google SuperSU Beta. Should be the first link to Chainfire's thread.
Run this in a Terminal app (with su) or TWRP's Terminal
Code:
echo "SYSTEMLESS=true" >> /data/.supersu
Then flash SuperSU 2.67.

Spasticdroid said:
Google SuperSU Beta. Should be the first link to Chainfire's thread.
Run this in a Terminal app (with su) or TWRP's Terminal
Code:
echo "SYSTEMLESS=true" >> /data/.supersu
Then flash SuperSU 2.67.
Click to expand...
Click to collapse
Got it. Thanks
Nexus 10

Just popped up on mine as well. Small.

Interesting, the zip contains baseband patches but the version in the OP remained the same. Anyone notice any differences in reception?

Decided to give this a go... Have combined storage and was on a custom stock rom with xposed and viper.
Flashed stock system and recovery, did not wipe data.
Reboot system, let everything update, verify combined storage untouched.
Stock recovery could not find the update since I have combined storage.
Tried TWRP with no success
Flashed stock recovery and sideloaded the update
Update flashed succesfully
Reboot to bootloader and flash TWRP and kernel of choice.
Reboot system
Reboot to bootloader and flash super su, xposed etc.
2.67 non systemless did not work for me. 2.64 worked fine as usual. Well maybe not, getting a lot of system fc's. Will update once I have it worked out.
So flashing 2.62-3, then flashing 2.64 got me out of bootloops and system fc's. Seems to be good to go now.

I am very interested in systemless root specifically for the security updates and benefits of root.
Using this guide
http://forum.xda-developers.com/showpost.php?p=64624664&postcount=454
and SuperSU beta should all be ok?
I am ATM on trupurexmm 2.6.2, frankenclark v0.7, xt1575 and twrp 3.0.0-1.

Can someone on an untouched stock system pull /system after the update and upload it for me? I would like to create a flashable zip so we don't have to go through all this nonsense to update.

Is there any detailed guide on how to make this OTA update work on a machine with root + twrp?

blkcr said:
Hey dude, I just got the notification. I'm using the stock ROM, rooted and obviously bootloader unlocked, also using xposed, do you know if it's safe for me to install the update from the notification? I just don't want to screw it and start from scratch.
Click to expand...
Click to collapse
Same boat here. Stock rooted with Xposed. Rooted with 2.62.
---------- Post added at 09:02 AM ---------- Previous post was at 08:54 AM ----------
There is a stock 6.0 twrp backup file available. Perhaps you could restore that, take the OTA, then root again?

bostonirishguy13 said:
Same boat here. Stock rooted with Xposed. Rooted with 2.62.
---------- Post added at 09:02 AM ---------- Previous post was at 08:54 AM ----------
There is a stock 6.0 twrp backup file available. Perhaps you could restore that, take the OTA, then root again?
Click to expand...
Click to collapse
I was thinking of this same thing.
For I, I have a stock non root twrp backup. Was thinking of flashing the stock ota mm that I have then flashing the recovery to stock then take the ota. Install twrp, then root.
Sent from XT1575,TPXMM 2.6.2,Frankenclark v0.7

shoman94 said:
Can someone on an untouched stock system pull /system after the update and upload it for me? I would like to create a flashable zip so we don't have to go through all this nonsense to update.
Click to expand...
Click to collapse
I was going to keep this to myself and one other person on here. It's unmodified, meaning no root, and odexed. Only converted to be flashable.
Also note that I have included other items in the ROM including radios/modem and an unmodified logo.bin, meaning you will get the "bootloader unlocked" splash.
Too lazy to make a thread for it. Any one wants to? Have at it.
https://drive.google.com/file/d/0B5AiGacWcBRzMTBlWmppOC1DS3c/view?usp=docslist_api
Sent from my XT1575 using Tapatalk

[RECOVERY][OFFICIAL] TWRP for Galaxy A40 [A405FN]

Team Win Recovery Project 3.6.1​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Special Notes:
DON'T FORGET TO ENABLE "OEM UNLOCK" (located in Developers options)
KNOX will be tripped once you flash custom binaries to your phone. Your warranty may be voided. However this may not affect you if your country forces Samsung to provide hardware warranty regardless of software status
Samsung Firmware OTA (aka System Updates) will no longer work once you flash custom binaries. You can flash custom ROMs if you want to keep the OS up-to-date
All apps that use KNOX like Samsung Pay, Secure Folder and maybe more will no longer work
Download:
Recovery
VBMeta
Multidisabler
Changelog:
21.10.2021
Rebased kernel source to CUH4
16.06.2021
Rebased kernel source to CUC2
03.05.2020
Rebased kernel source to BTB8
25.04.2020
Rebased kernel source to ATA4
07.12.2019
Initial Release
Guide:
If you already have a custom recovery installed:
Boot to your custom recovery
Flash the recovery image
If you are starting from scratch:
Go to Developer Settings and enable "OEM Unlock" option
Power off the device and boot in download mode
In download mode, you will see the long press and volume up option to unlock the bootloader
Unlock the bootloader. That will wipe your device so be sure you made a backup of your data
After bootloader unlock, boot up the phone and make sure it is connected to the internet or it will trigger rmm prenormal
Setup the phone without google account and others
Reboot in download mode and flash the recovery and vbmeta images
Boot to TWRP
Format data in TWRP
Flash the Multidisabler zip
Now you can reboot
Contributors
ponces, geiti94, ianmacd
Source Code: https://github.com/TeamWin/android_device_samsung_a40
Kernel Source Code: https://github.com/ponces/android_kernel_samsung_universal7904

Reserved

I'm really tempted to flash this TWRP and root my A40. Though I know Android 10 has been announced (at least in my region) for April 2020. Should I wait until then? My main concern is, if i flash it now, how easy will it be to upgrade to Android 10 then?
The only real thing I use root privileges for is to remove bloatware completely and edit the hosts file, so I can wait a few months. Also what about dm-verity? Are there any problems there?

My question and can I use this recovery on ITV-A405FNXXU2ASK2-20191218161204?

bishsop said:
I'm really tempted to flash this TWRP and root my A40. Though I know Android 10 has been announced (at least in my region) for April 2020. Should I wait until then? My main concern is, if i flash it now, how easy will it be to upgrade to Android 10 then?
The only real thing I use root privileges for is to remove bloatware completely and edit the hosts file, so I can wait a few months. Also what about dm-verity? Are there any problems there?
Click to expand...
Click to collapse
The choice of waiting is only yours.
In my case I need this as I'm using a custom Treble ROM and not Samsung's firmware.
The ease to upgrade to Android 10 relies only on the your expertise on how to flash the original firmware using ODIN.
At the time of the upgrade you need to use ODIN to flash an original firmware from Android 9 to be able to fully restore the original behavior and flash Android 10.
As far as I'm concerned, DM-Verity is related with both DT and DTBO partitions and those partitions are not even touched during this process.
The ones that are changed are BOOT, RECOVERY and VBMETA to disable a few security procedures from Samsung to be able to flash and boot custom binaries.
Because of this, take in consideration the "Special Notes" section in the first post.
Nevertheless, if the need of changing the hosts file is to block ads, you can reach the same goal by using the "Private DNS" feature introduced in Android 9 as explained here.

costa11 said:
My question and can I use this recovery on ITV-A405FNXXU2ASK2-20191218161204?
Click to expand...
Click to collapse
As you can see in the first post, this TWRP version is for the firmware A405FNXXU2ASJ1 (October's update).
I am still waiting for Samsung to drop A405FNXXU2ASK2 (December's update) sources here to update TWRP.
I'll keep you posted when the sources drop and work on TWRP update begins.

ponces said:
As you can see in the first post, this TWRP version is for the firmware A405FNXXU2ASJ1 (October's update).
I am still waiting for Samsung to drop A405FNXXU2ASK2 (December's update) sources here to update TWRP.
I'll keep you posted when the sources drop and work on TWRP update begins.
Click to expand...
Click to collapse
So I tried to install this recovery on the ASK2 firmware and it worked, there is only one problem when it goes down the brightness does not return anymore remains low! Then another thing I rooted with Magisk is it's not working, come up with an error and then I'll try to take a screenshot!

thank you again for your job
i just updated my rom to the SK2 (downloaded the rom, flashed it with Odin)
then installed you twrp (the SJ1 is OK)
then flashed with magisk manager the boot.img to Root the Rom
and then flashed the param.bin with a better boot logo
thank you so much for your job !!

costa11 said:
Then another thing I rooted with Magisk is it's not working, come up with an error and then I'll try to take a screenshot!
Click to expand...
Click to collapse
Magisk-Root is working for me.
I did this:
[*]Backup of ASJ1 with TWRP
[*]Complete odin flash of ASK1
[*]TWRP - ASJ1 - Version
[*]direct reboot into TWRP
[*]Format Data
[*]Flash Multidisabler
[*]Full Boot
[*]Install Magisk.APK from sd-card
[*]Reboot into TWRP
[*]Flash Magisk
[*]Full boot to check of root access => ok
[*]Reboot into TWRP
[*]Restore of ASJ1-Data​
​
Everything working!

Thanks for the recovery, is working fine with latest ITV (Italian no brand) firmware, to have root is only simple necessary to flash latest Magisk ZIP via twrp (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)

i have a big problem about twrp on my phone
I have followed this thread
But when i flash twrp (i have uncheck "reboot" on odin of course) i can't get access to the recovery mode, when i do power button + volume up it doesn't do nothing and show this :
(I have already unlock my boot loader)
I think its DM VERITY who block the access to recovery mode but i can't disable this, cause i can't get access to twrp :/
Thanks for any answers c:

cioce said:
Thanks for the recovery, is working fine with latest ITV (Italian no brand) firmware, to have root is only simple necessary to flash latest Magisk ZIP via twrp (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)
Click to expand...
Click to collapse
Can confirm it works with ATA4 (region DBT). Same procedure my post above. With restoring Data as last step there isn't anything lost as well... :good:
Be sure to enable usb debugging after flash of new firmware. Otherwise TWRP flash would fail...
:good:

Leak.dll said:
i have a big problem about twrp on my phone
I have followed this thread
But when i flash twrp (i have uncheck "reboot" on odin of course) i can't get access to the recovery mode, when i do power button + volume up it doesn't do nothing and show this :
...
(I have already unlock my boot loader)
I think its DM VERITY who block the access to recovery mode but i can't disable this, cause i can't get access to twrp :/
Thanks for any answers c:
Click to expand...
Click to collapse
I had some similar problem.
It was a wrong TWRP, I had to try 3 different ones until it finally worked (the one for AJ1 worked for me).
If you are in a bootloop you still can press Volume UP + DOWN and at the same time put the USB cable in when booting. This should set your phone into the download mode and you can flash TWRP or OS again.

Has anyone tried this TWRP build with ATB1 February patch version? It has increased BL version (2->3) so it is not possible to roll back to any older FW...

From my information ATB1 is still the same security patch level as ATA4.
General question: How can I judge the BL version of the firmware?

ruffyrisco said:
Magisk-Root is working for me.
I did this:
Backup of ASJ1 with TWRP
...
Click to expand...
Click to collapse
what TWRP is this and how did you manage to install it before being rooted?

toshibashi said:
what TWRP is this and how did you manage to install it before being rooted?
Click to expand...
Click to collapse
I used the modified TWRP from post #1: https://androidfilehost.com/?fid=4349826312261685733

ruffyrisco said:
From my information ATB1 is still the same security patch level as ATA4.
General question: How can I judge the BL version of the firmware?
Click to expand...
Click to collapse
Well, my info comes from samfw.com/firmware/SM-A405FN/TMZ, not sure how do they extract it.
both ATB1 - samfw.com/firmware/SM-A405FN/TMZ/A405FNXXS3ATB1 and ATA4 - samfw.com/firmware/SM-A405FN/XEZ/A405FNXXU3ATA4 seems like BL (or some OTP bits, I am noob with android internals) bumped from 2 to 3.
(sorry about URL formatting, as a XDA newbie, I am no allowed to post URLs)

xorly said:
both ATB1 - samfw.com/firmware/SM-A405FN/TMZ/A405FNXXS3ATB1 and ATA4 - samfw.com/firmware/SM-A405FN/XEZ/A405FNXXU3ATA4 seems like BL (or some OTP bits, I am noob with android internals) bumped from 2 to 3.
Click to expand...
Click to collapse
As I mentioned earlier ATA4 firmware works fine with TRWP.
But I'm not sure if ATA4 has BL 3.
Does the digit 10 in the firmware number represents the BL?

ruffyrisco said:
But I'm not sure if ATA4 has BL 3.
Click to expand...
Click to collapse
Then reboot into Download mode (you have to do it manually, not via ADB command) and look into top left corner. On ATB1, one of last lines says
Code:
AP SWREV B:3 K:3 S:3
I assume that some fo those numbers (B?) is OTP number set by BL version.
ruffyrisco said:
Does the digit 10 in the firmware number represents the BL?
Click to expand...
Click to collapse
I am not sure which *10* do you mean. It looks like version prefix is bootloader version, number 3 in A405FNXXS3ATB1 or number 2 in A405FNXXU2ASK2. It is the only number which seems to corellate with BL version.
Also, now I can confirm that that this TWRP build (based on A405FNXXU2ASJ1) works with ATB1 firmware! (february sec. patch) Successfuly tested with Phhussons Android 10 GSI quack v213.

(Guide) Relock Bootloader/Back To Stock.

This guide is for those who are on unlocked bootloader/custom roms and want to go back to realme UI 1.0 and relock
Needless to say, me, and the makers of realme flash-tool and TWRP/other recoveries wouldn't be responsible for any damage caused to your device. Having said that, this method has been tested and should be fine for realme UI 1.0.
First things first, if you are on custom rom or on rooted stock rom you need to revert to unmodified stock rom.
*Warning :-Make absolutely sure that you are not relocking by flashing an older version, always flash the current or newer i:e If you unlocked while being on version A.19 make sure to flash A.19 and/or newer versions and not A.17. While I'm not sure if this will result in a brick or not and have no intentions of trying, this may result in a hardbrick.*
Links to firmware (RMX2061/EUxxxxxxx.ozip). Search for realme 6pro from the list.
IN.- https://www.realme.com/in/support/software-update
EU.- https://www.realme.com/eu/support/software-update
*Do not lock bootloader while on custom rom.*
*Do not lock bootloader if you're rooted.*
*Do not lock bootloader with any custom partitions even vbmeta with disabled verity and verification.*
IF YOU DO SO YOU'LL END UP WITH A BRICK WHICH CAN ONLY BE FIXED AT A SERVICE CENTER. YOUR PHONE WILL DISPLAY AN ERROR MESSAGE SAYING PARTITONS ARE CORRUPT/DAMAGED.
Backup your stuff before proceeding.
There are three ways to revert to stock:
1. Using RFT (Realme Flashtool) by @sayaoks :-
Instructions provided on the thread.
https://forum.xda-developers.com/re.../tool-rtf-realme-flash-tool-to-flash-t4144969
2. Using TWRP (use the latest from the recovery section).
*Wipe>Format Data> type yes> format
*Reboot>reboot to recovery
*Install > Select .ozip> Swipe to flash
*Reboot
Do not select disable-vbmeta or avb_patcher or anything of that sort.
Recommended-
https://forum.xda-developers.com/realme-6-pro/development/recovery-twrp-recovery-t4171759
3. Using stock recovery.
From system:- To flash using stock recovery, download and put the .ozip in the root of storage and from realme file manager tap on it. It will start Flashing in the stock recovery.
From recovery:- Download and put the .ozip in the root of storage, then reboot to recovery.
Your Language> Install from storage> enter password(only if you have one)> Phone/SDcard and then select the .ozip.
Any custom recovery.img/boot.img should now be replaced with stock.
After flashing is successful and the device has booted to stock rom reboot to the bootloader.
If you want to be extra careful, and used RFT or TWRP/Custom Recovery to flash stock rom, you can flash the fw again using stock recovery after the phone has booted up(steps mentioned above).
Connect the phone to PC and enter command
Code:
fastboot flashing lock
Now on the phone select lock bootloader with the help of volume up and power buttons.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Wait for it to complete... and you will boot into the OS with a locked bootloader.
Thanks to @Satham spot & @sayaoks

I'm on RMX2063_11_A35 I can't find an update more recent than RMX2061EU_11.A.26 Can I use this method and update via OTA and then lock the bootloader?

Andres88z said:
I'm on RMX2063_11_A35 I can't find an update more recent than RMX2061EU_11.A.26 Can I use this method and update via OTA and then lock the bootloader?
Click to expand...
Click to collapse
A35 is the latest version for IN firmware. Latest for EU is A28, which is up on realme EU website.
If you want A35 firmware just visit the Indian downloads page.
And yes you can update to a newer version than whatever you unlocked on and then lock on the newer version. Make sure everything is just stock meaning no twrp,patched boot and/or custom recovery.

Don't have a brick to use the rmx2061 model? instead of device 2063, what method do you recommend.

Andres88z said:
Don't have a brick to use the rmx2061 model? instead of device 2063, what method do you recommend.
Click to expand...
Click to collapse
Well I know someone having Indonesian/Indian model and locking on the EU firmware. It didn't brick but not sure what will happen in the future when an OTA drops.
Lock on the same firmware as the device, like eu device with eu fw and so on (just to be safe).
You can use any methods to get to stock, just to be extra sure, when the phone boots up after flashing stock and before locking, put the fw in the root storage of the phone and re-flash again with the stock recovery. And then proceed to lock.

thanks to carry out the process and start correctly, I got an update of only 300 mb ls which gave me an error, but soon the same RMX2063a1135 came out but 3.5 gb which if it was installed and now I am as I started, without root or magisk, The question is, since the most recent was installed via ota, can I close the bootloader?

Andres88z said:
thanks to carry out the process and start correctly, I got an update of only 300 mb ls which gave me an error, but soon the same RMX2063a1135 came out but 3.5 gb which if it was installed and now I am as I started, without root or magisk, The question is, since the most recent was installed via ota, can I close the bootloader?
Click to expand...
Click to collapse
Yes

can i use orange fox recovery ? which one should i wipe if i use orange fox recovery?

Can this guide help me rollback my realme 6 pro from android 11 beta to android 10? If it does, which steps do I need to add or change. Thanks

noside_143 said:
Can this guide help me rollback my realme 6 pro from android 11 beta to android 10? If it does, which steps do I need to add or change. Thanks
Click to expand...
Click to collapse
Yes but you must use the latest Android 10 image, seem realme blocks to downgrade to older version than this

I have installed custom rom and I need to return to stock rom
all stock versions I found are ui 1.0 only
I unlocked the bootloader while using latest ui 2.0
what should I do to return to stock rom please ?

kiro_koko said:
I have installed custom rom and I need to return to stock rom
all stock versions I found are ui 1.0 only
I unlocked the bootloader while using latest ui 2.0
what should I do to return to stock rom please ?
Click to expand...
Click to collapse
You can use RUI 2.0 to lock. Just be sure that all partitions are stock. Use the .ozips made by @ctapchuk

How To Guide Root OnePlus 9

This is for Europe (11.2.2.2.LE25DA). If you are on Global, EU version works, but up to you. It appears for last year, unless you are from India, OnePlus doesn't care. It might be a while before a Full OTA update for Global is released, you'll notice updates come without it for Global or on their Global support site, the firmware is outdated.
- On T-Mobile have full 5G. I don't know about AT&T and Verizon. Should be same.
If you are on Global and you just received your phone. Do all the updates from the incremental through device. If you want root, you can flash with the EU patched boot.img and everything will work as normal
**** but once you do this, you will need to wait for Global full OTA to update next time, unless you managed to have a backup copy of the unpatched boot.img
Do the usual to unlock your OnePlus 9: oem unlock, usb debugging from developer. Boot into bootloader and use adb command /fastboot flashing unlock
This will wipe your phone and reboot. Setup your phone
Install Magisk from his official github: https://github.com/topjohnwu/Magisk/releases/tag/v22.0
- Topjohn provides full instructions on how to do this yourself as well.
Reboot into bootloader
Flash boot the magisk modified boot.img. /fastboost flash boot boot.img
Go into Magisk app and install via direct install and all done.
Return to stock
- Restore boot.img from Magisk
- Uninstall Magisk
- Flash the stock boot.img
- Relock the bootloader, will wipe and return to factory reset.
Stock 11.2.33 Boot.img
boot11233_stock.img | by zymphad for OnePlus 9
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Magisk Patched 11.2.33 boot.img
boot11233_patched.img | by zymphad for OnePlus 9
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Spoiler: Previous Boot Images
Patched Boot.img for Europe (11.2.2.2.LE25DA)
boot93.img | by zymphad for OnePlus 9
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Stock Boot.img for Europe (11.2.2.2.LE25DA)
boot.img | by zymphad for OnePlus 9
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Future Full OTA Updates
- Update as usual
- Go into Magisk and choose direct install and then install to inactive slot after OTA
- This will retain root
How to do it yourself:
Download full OTA, usually Oxygen Updater App, XDA has links or from https://www.oneplus.com/support/softwareupgrade
Download Payload Dumper
payload_dumper-win64.zip | Tool by geminids14 for Utilities
Extract payload.bin in xiaomi weekly build zip for MI A1
androidfilehost.com
Extract and place payload.bin in input folder
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Run the payload_dumper.exe
In the output folder will be boot.img, move that onto your phone, folder of your choice
Go to Magisk app, click install
Choose Select and Patch a File
Choose the file and it will patch it, Magisk will say where the file is located.
That is your patched boot.img file. Use that to flash / root your phone.
Remember only have do this once, you don't have to do this again with subsequent updates.

zymphad said:
Do the usual to unlock your OnePlus 9: oem unlock, usb debugging from developer. Boot into bootloader and use adb command /fastboot flashing unlock
This will wipe your phone and reboot. Setup your phone
Install Magisk from his official github: https://github.com/topjohnwu/Magisk/releases/tag/v22.0
Reboot into bootloader
Flash boot the magisk modified boot.img. /fastboost flash boot boot.img
AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Go into Magisk app and install via direct install and all done.
Click to expand...
Click to collapse
What version/region of the OP9 is this boot.img for? Where did you get the original unmodified one? I need Canadian.

Slikkster2k said:
What version/region of the OP9 is this boot.img for? Where did you get the original unmodified one? I need Canadian.
Click to expand...
Click to collapse
So there seems to be confusion about version. The boot image doesn't matter. When you flash a custom rom, there isn't a EU or US version. The only difference I can think of if it's T-Mobile, so when you flash, then it would just be an international/global. This is from XDA.
Honestly I would bet the Indian version is same as well.
This is the EU, which is the same boot.img for US unlocked.
If the future you should be able to do this yourself once OnePlus adds the 9 series to their global firmware downloads list.

Good to know, thanks! I'm not planning to flash a custom rom, I just want root. So I just have to make sure the bootloader is unlocked, and then follow the steps for Magisk.

Yep, working great here. Mobile payments working fine. Using energized for adblock.

So I successfully rooted yesterday, all is working great. Today my phone prompts me that system update 11.2.1.1 is available. Of course, I cannot upgrade while rooted. However, I also can't restore my stock boot.img because I don't have a copy of it... Any way to update without doing a factory reset, or am I screwed?
Edit: From what I've found, factory reset doesn't touch the boot partition. So that won't help.

This method worked for me, though I'm now running the same issue as Slikkster2k, since I don't have an unpatched boot.img, I can't uninstall magisk to update via OTA.
I would suggest, for those wanting to be able to update in the future (until we get a custom recovery), that instead of /fastboot flash boot boot.img, use /fastboot boot boot.img and then let Magisk finish the install. When Magisk patches the boot image, it will take a backup of the stock one to be used for uninstallation.

Slikkster2k said:
So I successfully rooted yesterday, all is working great. Today my phone prompts me that system update 11.2.1.1 is available. Of course, I cannot upgrade while rooted. However, I also can't restore my stock boot.img because I don't have a copy of it... Any way to update without doing a factory reset, or am I screwed?
Click to expand...
Click to collapse

Install magisk module-a/b install-before you reboot, then select direct install to second slot and reboot. Works beautifully.

[email protected] said:
Install magisk module-a/b install-before you reboot, then select direct install to second slot and reboot. Works beautifully.
Click to expand...
Click to collapse
I can't install the OTA update at all -- I'm on global ROM, so it fails because it's attempting a partial OTA update, rather than flashing a full ROM.

@zymphad
Do you also have a copy of the unpatched boot.img file?

Slikkster2k said:
I can't install the OTA update at all -- I'm on global ROM, so it fails because it's attempting a partial OTA update, rather than flashing a full ROM.
Click to expand...
Click to collapse
With rooted phone you need to do full not partial.
We are on the February security update. The latest update for OP9 is still on it, so disappointing.
We have to wait until the March security update that is already out for other oneplus devices.
You can unroot and re-lock your bootloader and then install the partial and then do the whole process again. I am not going to do that, seems waste of time.
Uninstall Magisk -- Flash stock boot.img -- lock bootloader.
This will wipe your phone back to factory reset!!!
But I expect we will see March update soon since Nord and 8 series have them already.

zymphad said:
With rooted phone you need to do full not partial.
We are on the February security update. The latest update for OP9 is still on it, so disappointing.
We have to wait until the March security update that is already out for other oneplus devices.
You can unroot and re-lock your bootloader and then install the partial and then do the whole process again. I am not going to do that, seems waste of time.
Uninstall Magisk -- Flash stock boot.img -- lock bootloader.
This will wipe your phone back to factory reset!!!
But I expect we will see March update soon since Nord and 8 series have them already.
Click to expand...
Click to collapse
The issue is that even if we wanted to do this, Slikkster2k and I (and possibly others), don't have the stock boot.img, since we flashed the magisk patched boot.img directly. Since you provided the patched boot.img originally, do you have the unpatched version available?
That way if anyone still on the original version that came pre-loaded wants to flash back to fully stock (and maybe re-lock bootloader) they can.

Those of us on the Global/US variant (AA) don't have the full zip available, and since we can't flash incremental while rooted, we currently have no way of actually reverting to stock until OnePlus publishes the full ROM zip.

Will post the stock.
I mean dunno why would want to since to do the incremental think have to relock bootloader which would factory reset.
And the to root again would factory reset again...
The March security update is already out for Nord and 8 series. Would just wait.
The incremental is still the Feb security update which you are already on.

Thanks, I mostly just wanted to redo the root process, but use /fastboot boot boot.img instead of /fastboot flash boot boot.img, so that magisk has a backup of the stock bootloader. That way, if for some reason I need to flash back to stock before the March Security update comes out, I can do so from my phone without needing my PC.

zymphad said:
I mean dunno why would want to since to do the incremental think have to relock bootloader which would factory reset.
Click to expand...
Click to collapse
Ah, was not aware of that. In that case we'll just have to wait, hopefully OnePlus posts it soon.
Besides, the patched bootloader you posted is from 11.2.1.1 (I compared the hash to the one in the other thread), so I assume the stock image is the same. So it's no good to us anyways.

Slikkster2k said:
Besides, the patched bootloader you posted is from 11.2.1.1 (I compared the hash to the one in the other thread), so I assume the stock image is the same. So it's no good to us anyways.
Click to expand...
Click to collapse
Ahh, I didn't realize that, I guess it's just a good thing that the 11.2.1.1 boot.img doesn't cause any issues when flashed onto 11.2, since we would have had no way to undo it

reffu said:
Ahh, I didn't realize that, I guess it's just a good thing that the 11.2.1.1 boot.img doesn't cause any issues when flashed onto 11.2, since we would have had no way to undo it
Click to expand...
Click to collapse
Actually I tested it using fastboot boot boot.img before I flashed it, just to make sure it would work (I didn't know it was from 11.2.1.1 at the time, but I'm paranoid).

Seems the rest of the world is getting the March update except US again. Still no full package, and this time not even partial. Dunno what is going on with OnePlus and US, but it's annoying.
Will update for EU AB firmware in the OP. And then put disclaimer for Global to do all their updates prior to rooting.

How To Guide RUI 3.0 Easy Rooting Guide - On GT NEO 2

This thread going to guide you on how you can root Realme GT NEO 2 Device with RUI 3.0 installed.
This boot image is fresh, and it's patched for root access.
Caution: Before flashing, you need to have your bootloader unlocked, for bootloader unlocking, go to this link and follow the procedure to get approval and unlock your device bootloader.
Link: https://forum.xda-developers.com/t/bootloader-unlock-realme-gt-neo-2-rmx3370-all-variants.4391679/
After you get approval, you are ready to root your device!
For this tutorial, I gonna use a windows device.
​WARNING!​
I am not responsible for anything. proceed at your own risk. Rooting or Unlocking the Bootloader voids the device warranty, keep it in your mind.
STEP - ONE​
Only follow this step, if you get approval for the bootloader, and you didn't unlock this device or your flashing environment needs to be configured. You need to visit the following link to set up your environment for flashing a custom boot image.
Link: https://njpsmultimedia.blogspot.com/2022/04/realme-gt-neo-2-bootloader-unlock.html you just need to follow the video tutorial on this website.
STEP - TWO​​It's assumed that your environment is properly configured. Let's flash this boot image to root your device.
Download this zip file from here https://drive.google.com/file/d/1Xk1yBp5EDCZbl3i3jMtOhjfaVtTCQqYB/view?usp=sharing and copy the boot.img file to platform-tools folder.
Then open the terminal and cd to the platform-tools folder.
Then, shut down your device and hold the vol up + vol down + power button together to boot this device into fastboot mode.
First, you need to run
Code:
fastboot devices
to check if your device is properly connected to the bootloader interface. If it shows something then your device is properly connected, If not, try to install the device driver, change the cable, or boot into the bootloader mode again.
If your device is connected properly, then you will see a screen like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And then run this command:
Code:
fastboot flash boot boot.img
Then,
Code:
fastboot reboot
You are done! Congratulation.
Note: This method was tested with Realme UI 3.0 android 12 on GT NEO 2. Do not try this method on RUI 2.0 or on other devices.
SCREENSHOTS​
Note ​
If you face NO WIFI, Sound issue on the C04 version, you are advised to flash this alternate version from here: https://forum.xda-developers.com/t/...uide-on-gt-neo-2.4435919/page-2#post-86985433

Do you lose all data ? On the root part the bootloader is already unlocked

theogr91 said:
Do you lose all data ? On the root part the bootlocker is already unlocked
Click to expand...
Click to collapse
- it is necessary to have the bootloader unlocked before flash (instructions on how to unlock the bootloader can be found in the video in the post above or here on the forum)
- after flash just install Magisk manager
no data loss, tested and functional

theogr91 said:
Do you lose all data ? On the root part the bootlocker is already unlocked
Click to expand...
Click to collapse
If your bootloader is already unlocked, no data loss. but If your device bootloader is not unlocked, then unlocking your device data will be erased.

Do we flash magisk or other way of root ?

theogr91 said:
Do we flash magisk or other way of root ?
Click to expand...
Click to collapse
You need not flash anything extra than flashing customized boot.img. Just simply follow this step and your device will be rooted.

Worked like charm thanks. Will the phone be ok after an OTA update ?

Help...After flashing boot image and rebooted , Wifi is not scanning the networks and I am unable to take calls but 4g(internet) is working fine. Please reply me for any fix. I followed the exact steps you mentioned. My Device Realme Gt neo 2 UI 3.0

mahesh.pujala said:
Help...After flashing boot image and rebooted , Wifi is not scanning the networks and I am unable to take calls but 4g(internet) is working fine. Please reply me for any fix. I followed the exact steps you mentioned. My Device Realme Gt neo 2 UI 3.0
Click to expand...
Click to collapse
In my case, all is fine.
You can try backup data and then reset your device through recovery.

theogr91 said:
Worked like charm thanks. Will the phone be ok after an OTA update ?
Click to expand...
Click to collapse
After the OTA update, you may need to flash this boot image again.

Help...After flashing boot image and rebooted , Wifi is not scanning the networks and I am unable to take calls but 4g(internet) is working fine. Please reply me for any fix. I followed the exact steps you mentioned. My Device Realme Gt neo 2 UI 3.0
Nurujjamanpollob said:
In my case, all is fine.
You can try backup data and then reset your device through recovery.
Click to expand...
Click to collapse
Thanks for the reply . Any way I reverted back to previous state by flashing stock boot image and firmeware. Now everthing works fine. I will think about rooting later..

Removed root and updated to RMX3370_11_C.04 is it safe to reflash root image on this version?

theogr91 said:
Removed root and updated to RMX3370_11_C.04 is it safe to reflash root image on this version?
Click to expand...
Click to collapse
I just tried this and it worked for me...

Meanwhile I realised that my wifi and my phone don't work anymore... I have no idea if this boot image is the cause.

Grobie13 said:
Meanwhile I realised that my wifi and my phone don't work anymore... I have no idea if this boot image is the cause.
Click to expand...
Click to collapse
I have no wifi after the flash and i have no twp on RMX3370_11_C.04 any way to fix it ?

theogr91 said:
I have no wifi after the flash and i have no twp on RMX3370_11_C.04 any way to fix it ?
Click to expand...
Click to collapse
No solution so far. I think first everything was fine, after flashing the magisk boot image it's gone worse... But I'm not sure.

I do not recommend updating on RMX3370_11_C.0. After flashing boot image (without Magisk) wifi no longer working.

I flashed clean firmware and lock bl i am done moding this device only adb debloat.. And after clean flash netflix still wont open login screen...

Grobie13 said:
No solution so far. I think first everything was fine, after flashing the magisk boot image it's gone worse... But I'm not sure.
Click to expand...
Click to collapse
What device variant you use? India or global?
Probably I gonna update this boot image today with latest update.

Nurujjamanpollob said:
What device variant you use? India or global?
Probably I gonna update this boot image today with latest update.
Click to expand...
Click to collapse
It's global respectively EU. But I start from scratch yesterday. I flashed twrp, format data and flashed magisk. But other people need your patched boot image. Thanks for providing.