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

[GUIDE][ROOT][TWRP-MOTOMODS] How To Root Moto Z with SuperSU

{
"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"
}
someone should write tutorial about rooting, and clarify things about new nougat so let's start
there's 2 way to root stock N :
old phh's superuser
and new systemless superSU, i'm gonna show this way
first make sure you have stock boot partition (not rooted, installed turboZ is OK) and absolutely unlocked bootloader : How to Unlock Bootloader
How to root ?
flash my custom modded TWRP(with Battery Mod Support) : https://www.androidfilehost.com/?w=files&flid=157130
Code:
fastboot flash recovery twrp.img
flash latest TurboZ Stock kernel with TWRP : TurboZ_*_N(or 7.1.1)_Stock.zip
flash latest SuperSU by chainfire with TWRP : https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
(optional) flash latest magisk with TWRP : https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Reboot system
FAQ :
Can I mount system as R/W? or swipe "allow system modification" in TWRP first screen?
Yes But just after Mounting, you need to flash TurboZ Kernel otherwise bootloop will happen​
Can I update superSU in future?
Sure​
any Side Effects?
Not Yet, Please test and tell me how's going on​
Can I root This Installed Nougat? : https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342
Yes​
What About OTA and New Updates ?
after flashing kernel you can't install(sideload) OTA's, so you have to back to stock and not rooted system, update then root again​
ScreenShots :

It works.. Thanks

Hi @erfanoabdi, just for your info.. Tried MagiskSU on stock kernel couldn't acquire root but tried with latest TurboZ and its worked.. Now fully rooted which passes SafetyNet as well..

silvercat said:
Hi @erfanoabdi, just for your info.. Tried MagiskSU on stock kernel couldn't acquire root but tried with latest TurboZ and its worked.. Now fully rooted which passes SafetyNet as well..
Click to expand...
Click to collapse
Oh man, thanks for testing

erfanoabdi said:
Oh man, thanks for testing
Click to expand...
Click to collapse
Damn after a reboot SafetyNet failed but everything else works..

If anyone asks why the kernel is necessary when mounting system as R/W.
This is because by default, dm-verity is enabled, and will prevent the phone from booting if it detects an unauthorized change in the system partition. Flashing the kernel will disable dm-verity, which makes it a must if you're going to be using the stock ROM but plan on making changes to the system via root access and whatnot.
If you're going to flash a custom ROM, many already come with their own kernel which disables dm-verity (and forced encryption), so flashing a custom kernel that disables it isn't needed if the ROM already has one (it most likely does). However, I do still recommend that you flash a custom kernel on the stock ROM anyway as it makes it less painful if you choose to go back to a stock ROM as you don't need to flash an entire factory image* just to make your phone work due to dm-verity being an ass. It also gives better performance, so it's quite a win-win.
* - You may be able to get around this by just flashing the boot image and then installing the kernel, but I have not tested this.

Question - do you rally need the custom kernel?
I am just curious to know. - is this a requirement for N?
Granted, I am on MM and not N, but managed to get phh's supersu installled and working without modifying the kernel.
I just flashed TWRP and installed su from there, went into playstore and installed phh's superuser.
No problem so far - all mods are working fine.
Thanks

bert269 said:
I am just curious to know. - is this a requirement for N?
Granted, I am on MM and not N, but managed to get phh's supersu installled and working without modifying the kernel.
I just flashed TWRP and installed su from there, went into playstore and installed phh's superuser.
No problem so far - all mods are working fine.
Thanks
Click to expand...
Click to collapse
Yes,
For this systemless, Only kernel needs to be based on MM (which is not available right now)
On mm you can also flash forcedsystem superSU (available in XDA) with force encryption and dm-verify Disabler patch (available in motoZ forum) only if you want chainfire's superSU
But your phh's superuser is working too

erfanoabdi said:
Yes,
For this systemless, Only kernel needs to be based on MM (which is not available right now)
On mm you can also flash forcedsystem superSU (available in XDA) with force encryption and dm-verify Disabler patch (available in motoZ forum) only if you want chainfire's superSU
But your phh's superuser is working too
Click to expand...
Click to collapse
Thank you kindly - I appreciate your response.

I am on nougat and rooted with phh supersuser so can i uninstall the phh su and follow you guide of flashing turbo kernel and super su

kethsawant said:
I am on nougat and rooted with phh supersuser so can i uninstall the phh su and follow you guide of flashing turbo kernel and super su
Click to expand...
Click to collapse
Yes you need to reflash stock boot.img from firmware's (or your TWRP backup)
Then follow OP guide

erfanoabdi said:
Yes you need to reflash stock boot.img from firmware's (or your TWRP backup)
Then follow OP guide
Click to expand...
Click to collapse
ok then i dont have a twrp back up before rooting the phone so i guess i have to flash the stock boot.img by fastboot mode from original firmware

excuse me, I am in the nougat version that you mention in the main post, but I don't know where to look for the stock boot partition or get the right one, please can you tell me?
Greetings

Getting an error
I get the error
(bootloader) Image not signed or corrupt
with both this and the official twrp recovery. And yes, my bootloader is unlocked.
Any way to fix this?

Stuck at "Your device will boot in 5 seconds"
Hi guys,
I've installed TWRP, I then flashed the TurboZ Stock kernel and it automatically rebooted.
Now it's stuck at the screen
"Your device has been unlocked and can't be trusted
...bla bla bla....
Your device will boot in 5 seconds"
I've tried living it there for hours without any luck.
I've tried flashing TurboZ Stock kernel again but with the same result.
What do I do now?
Thanks

andrea_x said:
Hi guys,
I've installed TWRP, I then flashed the TurboZ Stock kernel and it automatically rebooted.
Now it's stuck at the screen
"Your device has been unlocked and can't be trusted
...bla bla bla....
Your device will boot in 5 seconds"
I've tried living it there for hours without any luck.
I've tried flashing TurboZ Stock kernel again but with the same result.
What do I do now?
Thanks
Click to expand...
Click to collapse
Flash this: http://forum.xda-developers.com/showpost.php?p=69439969&postcount=17

erfanoabdi said:
Flash this: http://forum.xda-developers.com/showpost.php?p=69439969&postcount=17
Click to expand...
Click to collapse
Thanks for the advice, but it didn't work, it's still stuck at "Your device will boot in 5 seconds."
I forgot to mention that the system is encrypted. Does this change things?
I've tried to restore a previous TWRP backup to do a factory reset but when it start up it ask for the password but...there is not keyboard!!!

Do you think that can cause conflict if I use this TWRP? [RECOVERY][UNOFFICIAL][XT1650][griffin] TWRP 3.0.3-n2 for Moto Z
Also after rooting I should be on the stock kernel to keep the root? if not, is any other recommended to install?

lilloscar said:
Do you think that can cause conflict if I use this TWRP? [RECOVERY][UNOFFICIAL][XT1650][griffin] TWRP 3.0.3-n2 for Moto Z
Also after rooting I should be on the stock kernel to keep the root? if not, is any other recommended to install?
Click to expand...
Click to collapse
You can use this TWRP
You need to install f2fs patched kernel to keep root

New TWRP is here (testing): https://www.androidfilehost.com/?w=files&flid=157130
Fixed ugly cursor
Updated with latest TWRP version

How to root oreo

Bonjour,
I have problems after rooting (like camera app stops to work)
I enabled OEM debug,
flash twrp-3.2.1-1-herolte.img.tar,
format data,
reboot recovery,
flash no-verity-opt-encrypt-6.0.zip,
and Magisk-v16.4(1642).zip
Thank you for your help

Is TWRP / SuperSU updated for Oreo yet?

fred.eric said:
Bonjour,
I have problems after rooting (like camera app stops to work)
I enabled OEM debug,
flash twrp-3.2.1-1-herolte.img.tar,
format data,
reboot recovery,
flash no-verity-opt-encrypt-6.0.zip,
and Magisk-v16.4(1642).zip
Thank you for your help
Click to expand...
Click to collapse
I work with odin rode oreo rum. I am installing TWRP, but TWRP is not opening. When I want to turn on TWRP with the help of 3 keys, the device has its own recovery.

*Detection* said:
Is TWRP / SuperSU updated for Oreo yet?
Click to expand...
Click to collapse
From what I understood, TWRP version 3.2 is only fro OREO ROMS
for SuperSU, some people recommend to use Magisk instead

mpasa said:
I work with odin rode oreo rum. I am installing TWRP, but TWRP is not opening. When I want to turn on TWRP with the help of 3 keys, the device has its own recovery.
Click to expand...
Click to collapse
Do you use odin 3.13.1?

fred.eric said:
Do you use odin 3.13.1?
Click to expand...
Click to collapse
yes I am using Odin 3.13.1. I'm flashing TWRP 3.2.1.1

mpasa said:
yes I am using Odin 3.13.1. I'm flashing TWRP 3.2.1.1
Click to expand...
Click to collapse
do you check OEM unlock under Developer options?

fred.eric said:
do you check OEM unlock under Developer options?
Click to expand...
Click to collapse
OEM with unlocking and USB debugging turned on.

mpasa said:
OEM with unlocking and USB debugging turned on.
Click to expand...
Click to collapse
And there is noting in odin logs?

{
"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"
}

very strange

After installing the S7 G930f device oreo stock rum I can not TWRP. I am installing TWRP 3.0.24 or 3.2.1.1 with Odin and the PASS writer is also opening the device itself. Then when I want to enter TWRP with 3 keys, the following error occurs when I come to the menu and factory reset. I can not upload Custom rom for this. There is a different way you can install custom rom.
Developer options on, OEM unlock on, System auto update, USB debug on
I have a brief knowledge of you. Before Oreo TWRP was established and I was using custom ROMs. Then I downloaded the BTU stock oreo and set it up with ODIN. But I can not TWRP. It seems to be installed but it does not open when the file is not found when opening its own recoverysi. There is a screen display. It even gives me an error when I run samsung share. Access is denied. because of unauthorized change. But I just made a new one. Also, when I run Samsung Pass, the root directory of your device is accessed. can not be used. But I have re-established the stock rom with ODIN and give these mistakes.
translation of mistakes given in the screen image of the first message
fail to open recovery_caIuse (No such file or directory)
reboot recovey cause unknown
No support Single-sku
Successfully verified dmverity hash tree
E: failed to clear BCB message: fail to find / misc partition

I found a solution.
first I installed BTU 7.0 with Odin. I turned off the phone and installed TWRP 3.0.2.4 with ODIN. TWRP was turned on when the phone was turned on as a solid recovery after it was turned on. I formatted and erased all the data. and Ambassadii's latest oreo roman.

fix twrp /data access
After reading this thread [ROM][8.0.0] Dylan's S7 Oreo ROM V4 https://forum.xda-developers.com/galaxy-s7/development/rom-dylan-s-s7-oreo-rom-t3784715
I used SuperSU instead of Magisk and no-verity-opt-encrypt-6.0.zip works

fred.eric said:
After reading this thread [ROM][8.0.0] Dylan's S7 Oreo ROM V4 https://forum.xda-developers.com/galaxy-s7/development/rom-dylan-s-s7-oreo-rom-t3784715
I used SuperSU instead of Magisk and no-verity-opt-encrypt-6.0.zip works
Click to expand...
Click to collapse
can you please upload the ( no-verity-opt-encrypt-6.0.zip ) as I can't find it any more on the internet and also please if there is any special TWRP for rooting the S7 oreo version .
thanks in advance

machhho said:
can you please upload the ( no-verity-opt-encrypt-6.0.zip ) as I can't find it any more on the internet and also please if there is any special TWRP for rooting the S7 oreo version .
thanks in advance
Click to expand...
Click to collapse
Please go here for the files and guide you require
https://techbeasts.com/how-to-root-galaxy-s7-s7-edge-on-android-oreo/

machhho said:
can you please upload the ( no-verity-opt-encrypt-6.0.zip ) as I can't find it any more on the internet and also please if there is any special TWRP for rooting the S7 oreo version .
thanks in advance
Click to expand...
Click to collapse
I found no-verity-opt-encrypt on https://build.nethunter.com/samsung-tools/
TWRP is a recovery tool. To root your S7, you will need Magisk or SuperSU

11.0.4.4.IN21AA OTA notification

My phone gave me the update download notification, but somehow cannot download the OTA - get an error each time. Anyone else on global has same problem?
{
"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"
}

Same problem here.

I have a T-mobile device converted to global & rooted. Could it have anything to do with this?

I'm on T-Mobile but bought from OnePlus directly. Same problem.

you have to uninstall magisk using "restore images", then install the OTA, then reinstall magisk to the inactive slot. it's failing the check on the boot partition if you're rooted

zander21510 said:
you have to uninstall magisk using "restore images", then install the OTA, then reinstall magisk to the inactive slot. it's failing the check on the boot partition if you're rooted
Click to expand...
Click to collapse
Thanks.
I think that the "Restore Images" option shows up when pressing the "Uninstall" in the Manager. Is it so?
Question: After OTA, can I just "Install" Magisk directly from the Magisk Manager?
Or would I need to patch the boot image and then flash it manually.

sjgoel said:
Thanks.
I think that the "Restore Images" option shows up when pressing the "Uninstall" in the Manager. Is it so?
Question: After OTA, can I just "Install" Magisk directly from the Magisk Manager?
Or would I need to patch the boot image and then flash it manually.
Click to expand...
Click to collapse
I tried the whole restore images and it failed so I tried to fastboot boot the unpatched 11.0.2.2. it booted but no wifi for. Whatever reason. I tried to download 11.0.4.4 on cellular but I don't have a stable signal so it kept failing. Can someone please post the 11.0.4.4 download image and post a link. It would be most appreciated. I cannot find any other way to download it.

zander21510 said:
you have to uninstall magisk using "restore images", then install the OTA, then reinstall magisk to the inactive slot. it's failing the check on the boot partition if you're rooted
Click to expand...
Click to collapse
Not that I don't believe you, but OnePlus never did this before for rooted users. It seems odd that they'd start doing this now.

BeardKing said:
Not that I don't believe you, but OnePlus never did this before for rooted users. It seems odd that they'd start doing this now.
Click to expand...
Click to collapse
It seems so. With an unpatched boot I can try to download, but with a patched boot it gives an error. I'm starting to lose my fondness for OnePlus.

BeardKing said:
Not that I don't believe you, but OnePlus never did this before for rooted users. It seems odd that they'd start doing this now.
Click to expand...
Click to collapse
Agree, never experienced this earlier.

It looks like an increment update (593MB) and will not download for rooted devices. I was able to update on an unrooted device but keep getting error message on mine which is rooted.
I guess we have to wait for the full update zip.

aieromon said:
It looks like an increment update (593MB) and will not download for rooted devices. I was able to update on an unrooted device but keep getting error message on mine which is rooted.
I guess we have to wait for the full update zip.
Click to expand...
Click to collapse
Yes, that was it. I had to MSM back to TMobile A10, unlock bootloader, convert to global A10, and then OTA to 11.0.4.4 - and then root.

aieromon said:
It looks like an increment update (593MB) and will not download for rooted devices. I was able to update on an unrooted device but keep getting error message on mine which is rooted.
I guess we have to wait for the full update zip.
Click to expand...
Click to collapse
Will wait for that full update. TY!

Disregard

If you're using the global version you can use these, 11.0.4.4.IN21AA global kernels patched and stock, tested on an IN2010.
Stock: https://www.davesanthology.com/publ....IN21AA/11.0.4.4.IN21AA_boot_stock_IN2010.img
MD5: https://www.davesanthology.com/publ....IN21AA/11.0.4.4.IN21AA_boot_stock_IN2010.md5
Patched: https://www.davesanthology.com/publ...1.0.4.4.IN21AA_boot_magisk_patched_IN2010.img
MD5: https://www.davesanthology.com/publ...1.0.4.4.IN21AA_boot_magisk_patched_IN2010.md5
For any other version you can d/load and install with a rooted device if you temporarily remove root, I've just done it this way. This assumes you have a stock and patched boot.img for your current ROM available (either in Magisk as a backup image or somewhere else). 4.4 wouldn't download whist I had the patched kernel installed, yes a new OP method.
1. Disable (no need to delete) your Magisk modules (to be safe)
2. Flash the stock boot image (for the ROM you're currently using) in fastboot:
Code:
fastboot flash boot <stock_boot>.img
3. Reboot and test, just to be sure (you shouldn't have root)
4. Boot from the patched (root) boot image (for the ROM you're currently using) in fastboot:
Code:
fastboot boot <patched_boot>.img
5. Now you'll have root back but the stock image will still be installed
6. Download the update, if it's taking a long time hit pause them resume a couple of times
7. Install the update and DO NOT REBOOT!
8. Open Magisk and install via direct method and DO NOT REBOOT!
9. Install Magisk again but this time use install to inactive slot method
10. Reboot when prompted
11. Reenable your Magisk modules

Full update is now available for download

aieromon said:
Full update is now available for download
Click to expand...
Click to collapse
Thanks.
Full update link: https://www.oneplus.com/support/softwareupgrade/details?code=PM1586920535300

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.