Database Develop

Stock Nexus 6 (Verizon) will not update!

Hi guys,
As I wrote in the title, my Verizon Nexus 6 will not update. When I get a notification for the software update, I see that it downloads and is ready to restart the phone so it will install the update...
but when I do, it will display the android icon with the word "error" above it. No error number or details about why it did not work.
{
"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"
}
Things I tried already are:
formatting the phone (both through the settings menu as well as the stock bootloader)
deleting data and cache in Google Services Framework (via settings/apps/all apps)
I have more than enough space in my storage; more than 2/3rds of my storage is free space, so I really am having trouble wrapping my head around why this software update is failing to install. And since all the threads and help things I find are for rooted phones, I am having trouble finding something that would offer an answer. I was hoping to keep this phone stock as long as possible, which is an oddity for me because I usually want to root my phone immediately. I guess I just really like this phone as stock. And other than this update that fails to load, the phone has no other issues, other than a few emojis that fail to show, but I feel like that's from the software not being able to update for the 6 months that I've been trying to update it.
Any help with this would be greatly appreciated! Thank you!!

Is your device unlocked? Have you tried to sideload the update?
If your device is unlocked you can use NRT to update without loosing any data.

PickelledEggs said:
Hi guys,
As I wrote in the title, my Verizon Nexus 6 will not update. When I get a notification for the software update, I see that it downloads and is ready to restart the phone so it will install the update...
but when I do, it will display the android icon with the word "error" above it. No error number or details about why it did not work.
Things I tried already are:
formatting the phone (both through the settings menu as well as the stock bootloader)
deleting data and cache in Google Services Framework (via settings/apps/all apps)
I have more than enough space in my storage; more than 2/3rds of my storage is free space, so I really am having trouble wrapping my head around why this software update is failing to install. And since all the threads and help things I find are for rooted phones, I am having trouble finding something that would offer an answer. I was hoping to keep this phone stock as long as possible, which is an oddity for me because I usually want to root my phone immediately. I guess I just really like this phone as stock. And other than this update that fails to load, the phone has no other issues, other than a few emojis that fail to show, but I feel like that's from the software not being able to update for the 6 months that I've been trying to update it.
Any help with this would be greatly appreciated! Thank you!!
Click to expand...
Click to collapse
You might try clearing the cache partition in recovery and reboot. Maybe the next OTA will be install without issues.

lol!
if you made any kind of changes, chances are that any ota will not work. but that's alright, all you have to do is flash the factory image. it would've been updated already if you did that instead of writing out your post. you can grab it here https://developers.google.com/android/nexus/images

simms22 said:
lol!
if you made any kind of changes, chances are that any ota will not work. but that's alright, all you have to do is flash the factory image. it would've been updated already if you did that instead of writing out your post. you can grab it here https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
I don't think you read my post at all... I didn't make any changes. My phone is fully stock. No root at all. No unlock. No modifications whatsoever The ota Software update just will not work.
gee2012 said:
You might try clearing the cache partition in recovery and reboot. Maybe the next OTA will be install without issues.
Click to expand...
Click to collapse
I tried going in to recovery mode, but when I do, it gives me the same android error icon, but instead of "error" it says "no command"

Timza said:
Is your device unlocked? Have you tried to sideload the update?
If your device is unlocked you can use NRT to update without loosing any data.
Click to expand...
Click to collapse
Nope. Not unlocked. No modification whatsoever

PickelledEggs said:
Nope. Not unlocked. No modification whatsoever
Click to expand...
Click to collapse
If you nothing else works, I would try to sideload the update by downloading the image from Google's Factory Images for Nexus Devices page.

PickelledEggs said:
Nope. Not unlocked. No modification whatsoever
Click to expand...
Click to collapse
Best is to enable OEM UNLOCKING and usb debugging in developer options, reboot into fastboot and unlock the bootloader and after the reboot flash the latest MMB29S firmware as @simms22 allready stated. Flash the img`s seperately in fastboot, all i would flash personaly is the system and boot img.

Timza said:
If you nothing else works, I would try to sideload the update by downloading the image from Google's Factory Images for Nexus Devices page.
Click to expand...
Click to collapse
gee2012 said:
Best is to enable OEM UNLOCKING and usb debugging in developer options, reboot into recovery and unlock the bootloader and after the reboot flash the latest MMB29S firmware as @simms22 allready stated. Flash the img`s seperately in fastboot, all i would flash personaly is the system and boot img.
Click to expand...
Click to collapse
Oh ok, I must have misinterpereted what SImmz was saying, then. I got in to recovery mode and wiped cache finally, so I will see if that works, otherwise I'll try your guys' other suggestions

PickelledEggs said:
Oh ok, I must have misinterpereted what SImmz was saying, then. I got in to recovery mode and wiped cache finally, so I will see if that works, otherwise I'll try your guys' other suggestions
Click to expand...
Click to collapse
I had this issue with my Nexus 7 (stock) - wiped the cache partition in recovery, and waited for OTA to appear again - and it worked.

BTW, you don't need root to make certain changes(I don't know what changes, but I know many don't get ota because of). or google just made it to sensitive.

Timza said:
If you nothing else works, I would try to sideload the update by downloading the image from Google's Factory Images for Nexus Devices page.
Click to expand...
Click to collapse
You can only sideload OTA`s in stock recovery afaik, not complete images.

gee2012 said:
You can only sideload OTA`s in stock recovery afaik, not complete images.
Click to expand...
Click to collapse
Ah, my mistake. I (wrongly) assumed OTAs were included on that download page.

is using nexus root tool kit let you flash with su 2.5.2 or it using the lastest 2.66? or that makes no difference when flashing stock image?

MikePancake6 said:
is using nexus root tool kit let you flash with su 2.5.2 or it using the lastest 2.66? or that makes no difference when flashing stock image?
Click to expand...
Click to collapse
The latest version of NRT (v2.1.4) uses SuperSU 2.6.6.

Timza said:
The latest version of NRT (v2.1.4) uses SuperSU 2.6.6.
Click to expand...
Click to collapse
is there any way to use 2.5.2, or flashing a custom rom will system root or will it be systemless root anyhow?

MikePancake6 said:
is there any way to use 2.5.2, or flashing a custom rom will system root or will it be systemless root anyhow?
Click to expand...
Click to collapse
After you flash with TWRP (a step with NRT). When you opt to reboot system, you will get a message asking if you would like to install SuperSU. If you swipe to install you will have a "system root". If you opt to not install, you will have a systemless root.
Personally, I have a "system root", and it seems to be working fine, whereas before, I was having an issue with the systemless root.

Timza said:
After you flash with TWRP (a step with NRT). When you opt to reboot system, you will get a message asking if you would like to install SuperSU. If you swipe to install you will have a "system root". If you opt to not install, you will have a systemless root.
Personally, I have a "system root", and it seems to be working fine, whereas before, I was having an issue with the systemless root.
Click to expand...
Click to collapse
ok, thank you for all the help. i already unlocked the bootloader using the tool kit.
tonight i will root it and try a custom rom. maybe chrome or pure nexus project, those seem to be stock with extra options and rro customize.

Thanks guys. I just got around to sideloading the update last night and it's working like a dream.
I'll probably root it soon now. I've been feeling the itch recently... Lol
This (so far) is probably my favorite stock phone though. I might keep it stock for a bit longer
Sent from my Nexus 6 using Tapatalk

EMUI 9 root updates

I just looked up a few threads about rooting EMUI 9.
The one and only who kinda managed to do it is the developer of Magisk John Wu.
If you wanna stay updated about rooting EMUI 9 on Huawei P20pro, you should follow this guy:
EMUI9 root
still NO EMUI 9 kernel sources released

Rooting / Magisk is one thing. I think in addition to that we also need a working twrp or some recovery for Emui 9 to be able to flash stuff with relative ease. On top of that the OEM unlock option is greyed out which is problematical itself. So, this is all gonna be a bit complicated.

Well, there is a modded versions of TWRP Mate Rs Porsche with working decryption and for most people including me, oem-unlock is not greyed out when you have unlocked frp and unlocked bootloader.
I'm on the final of EMUI 9. So the last important thing would be a rooted EMUI 9 to get some important things working.
mrabcx said:
Rooting / Magisk is one thing. I think in addition to that we also need a working twrp or some recovery for Emui 9 to be able to flash stuff with relative ease. On top of that the OEM unlock option is greyed out which is problematical itself. So, this is all gonna be a bit complicated.
Click to expand...
Click to collapse

ArtaxXP said:
and for most people including me, oem-unlock is not greyed out when you have unlocked frp and unlocked bootloader.
Click to expand...
Click to collapse
Unlocked frp = oem unlock enabled in dev options
Unlock bootloader and frp itself doesn't cause "enable oem unlock" being greyed out. It's not getting greyed out just by upgrading to pie either. Upgrade to pie and factory reset does!
Good to know about twrp working on p20 pro

Hello, i changed my system font by using huawei themes.
Now it's not possible anymore, to edit photos and use different fonts for editing.
Does anybody have an idea, what i can do?i want to keep the new system font.
I hope to get a usefull help, i really would be grateful.
Sorry for this comment, i doesn't belong at this page

there is already something new on this topic?

not much but some
Heinzx3 said:
there is already something new on this topic?
Click to expand...
Click to collapse

some good news
good news

Rooted on 9.0
{
"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"
}
Sent from my CLT-L04 using Tapatalk

Dene_Bluesman said:
Rooted on 9.0 View attachment 4673784
Sent from my CLT-L04 using Tapatalk
Click to expand...
Click to collapse
Yeah awesome! Well done!
John Wu just released some info in a post: EMUI9 root

Dene_Bluesman said:
Rooted on 9.0 View attachment 4673784
Sent from my CLT-L04 using Tapatalk
Click to expand...
Click to collapse
Link pls

mr.mgmg said:
Link pls
Click to expand...
Click to collapse
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
Sent from my CLT-L04 using Tapatalk

Dene_Bluesman said:
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
Sent from my CLT-L04 using Tapatalk
Click to expand...
Click to collapse
There are alot files
https://github.com/topjohnwu/magisk_files/tree/master/canary_builds
Any file i must download and flash

mr.mgmg said:
There are alot files
https://github.com/topjohnwu/magisk_files/tree/master/canary_builds
Any file i must download and flash
Click to expand...
Click to collapse
Would like someone to drop round and flash it for you too? Do some reading, or don't flash.

purple patch said:
Would like someone to drop round and flash it for you too? Do some reading, or don't flash.
Click to expand...
Click to collapse
I think the Q not for you, just keep silent

mr.mgmg said:
I think the Q not for you, just keep silent
Click to expand...
Click to collapse
his point is, even you got the question wrong,
no files from that list will root your emui 9 simply by flashing any of it,
you gonna need a copy of RECOVERY_RAMDIS.img pulled from update.app of latest emui 9.0 firmware,
copy it to device with latest canary magisk & magisk manager installed,
patching the .img using that canary manager, and you will get patched_boot.img stored in download folder in that device,
copy it to your pc and flash it to recovery_ramdisk partition using fastboot,
or if you really are that lazy, simply download the prepatched one here : https://drive.google.com/file/d/1rhl405-ALbYrtGHilrNUR5Fuq4yATvTH/view?usp=drivesdk
and flash it from fastboot to your recovery_ramdisk partition
boot by holding vol up button

otonieru said:
his point is, even you got the question wrong,
no files from that list will root your emui 9 simply by flashing any of it,
you gonna need a copy of RECOVERY_RAMDIS.img pulled from update.app of latest emui 9.0 firmware,
copy it to device with latest canary magisk & magisk manager installed,
patching the .img using that canary manager, and you will get patched_boot.img stored in download folder in that device,
copy it to your pc and flash it to recovery_ramdisk partition using fastboot,
or if you really are that lazy, simply download the prepatched one here : https://drive.google.com/file/d/1rhl405-ALbYrtGHilrNUR5Fuq4yATvTH/view?usp=drivesdk
and flash it from fastboot to your recovery_ramdisk partition
boot by holding vol up button
Click to expand...
Click to collapse
Thanks for help

It will seem dumb for some of you but important to me and others (i Hope there are some lol)..... so just to be clear :
1- do we have to follow these steps AFTER installing emui 9 ? coming from emui 8.1 161 with evira kernel and using mods i wanna start 100% fresh because first time i installed emui 9 163 i came back a week later because of battery consuption that was way worse and real bad SOT so it's major to me to proceed the best way - i have to go first to twrp and wipe all, data+system+caches before flashing emui 9 ?
2- any reason not to use the easiest way ? why to prefer the complicated one : pulling the file from update.app and copy and etc....?
3- magisk modules will be usable ?
Thanks to those of you who will bring light or give me confident in re-installing pie.
And of course merry Christmas everyone

deltaman83 said:
It will seem dumb for some of you but important to me and others (i Hope there are some lol)..... so just to be clear :
1- do we have to follow these steps AFTER installing emui 9 ? coming from emui 8.1 161 with evira kernel and using mods i wanna start 100% fresh because first time i installed emui 9 163 i came back a week later because of battery consuption that was way worse and real bad SOT
2- any reason not to use the easiest way ? why to prefer the complicated one : pulling the file from update.app and copy and etc....?
3- magisk modules will be usable ?
Thanks to those of you who will bring light or give me confident in re-installing pie.
And of course merry Christmas everyone
Click to expand...
Click to collapse
1. Steps is for rooting, if you wanna start fresh, you can consider wiping /data after update. So none of your previous mods data no cache will tag along to your EMUI 9
2. Reason is, the difference of firmware versioning betweem region. You told me you updated to .163. My prepatched ramdisk is from C636 .168, although most of the time it can work universally across region and version (just like how custom recovery work in a universal way), there's no telling what huawei actually did between version update. So its always best to use and patch your own file. Since it will give you confidence, its your own doing after all.
3. I use youtubevanced, LKT, systemless host, swap torpedo, busybox and detach magisk modules, all work just fine on EMUI 9. You only need to redownload and reinstall all the modules (if you didnt wipe data, like me), because installation from oreo version wont work straight away on EMUI 9.
for extra information, SafetyNet and MagiskHide all working as well. I can use my banking app just fine.
as for precaution info,
i suggest you to use the flashy tools to install EMUI 9 from PC instead of using HuRU,
i did the HuRU way, and ends up with a messed up software serial number and broken recovery partition, meaning i can't flash TWRP, stock recovery nor a patched recovery ramdisk to acquired root. It will all fall to an error screen, telling me no recovery image available inside the system, and ask me to update system again. Fortunately the phone still boot just fine to system.
scratched my heads for hours until i manage to resolved it by flashing Recovery META and Recovery Vendor image through fastboot. After that i can reflash stock recovery, and the patched one (after i confirm stock one work fine)

Thanks a lot for your answers.
---------- Post added at 06:42 PM ---------- Previous post was at 06:24 PM ----------
otonieru said:
1. Steps is for rooting, if you wanna start fresh, you can consider wiping /data after update. So none of your previous mods data no cache will tag along to your EMUI 9
Click to expand...
Click to collapse
One thing no clear to me is what i do of the magisk canary Zip file...?.... ? As twrp not working on emui 9...

[GUIDE] Full process of installing Magisk & TWRP on a OnePlus 7 Pro (TMOBILE SUPPORT)

For me, pwning my new phone was a 7-hour process that required incredible learning capacity. Not everyone is prepared to go through a process like that, and it can easily take multiple days or weeks. This is a guide outlining a version of the exact process that got me to this point. It should be easy for anyone to follow, even people without much technical knowledge. (although, do be careful with the resulting root access)
I started with a GM1915, which is the T-Mobile model. You'd think it would require an unlock key from T-Mobile in order to work, but actually it doesn't. That's what they don't want you to know.
A well-known method for bypassing that requirement is to install an international OS and then upgrade it to a certain developer preview, causing the phone to update the bootloader to a non-crippled version that doesn't require an unlock key. So that's what I did.
However, the process is easier said than done. For someone like me who's done it, it's not too hard, but for a beginner it's intensely confusing. I was a beginner just yesterday and struggled with dumb error messages like "packed image not exist".
The guide is below. Sections starting with "T-MOBILE ONLY" and ending with "END OF T-MOBILE ONLY" are only to be performed on T-Mobile phones with T-Mobile firmware and a locked bootloader. If you have an unlocked bootloader then you can skip those steps.
Make sure you have a Windows machine. The Qualcomm drivers are only available for Windows, the programs are only available for Windows, people on this forum only know Windows. I have a Mac, personally, because Unix is awesome, but unfortunately nobody has thought about us and all the tools are Windows-only. I am just as disappointed as you, trust me. I used a virtual machine, but YMMV, depending on how good your hypervisor's USB passthrough is. You may want to use bare metal if you only have VirtualBox; it's not worth the effort. You will be hot plugging A LOT, and your phone will show up as many different types of USB devices.
You must have fastboot installed, but ADB is not required.
--- T-MOBILE ONLY ---
Install the "L2 drivers" for the phone. You can find them here. Just install as many of them as you can by right-clicking every `.inf` file you find and clicking Install on each one of them. Some of them will have missing files. Some of them won't have a signature. It doesn't matter, as long as you try every one of them, something will work. For me it was the 64-bit driver, in the 64 folder. All the others are 32-bit.
--- END OF T-MOBILE ONLY ---
You should probably plug the phone into your computer now and install the official OnePlus drivers as well. This is so that you can easily access the phone storage, which will become very important soon. Reboot your computer to apply the driver updates.
--- T-MOBILE ONLY ---
Download the "MSM Download Tool" from here (same link as above). Place it in its own folder. This is crucial because you must now download the guacamole-whatever.7z file and extract the .ots file into the same folder as the MSM Download Tool.
MSM Download Tool always looks in its folder for the image and pops up a cryptic error message if it's not found ("packed image not exist"). This is not very widely documented because MSM Download Tool is often distributed in the same folder as the image anyway. That's not the case when you are forced to download them as separate files.
Note that this is the only time you will have to use MSM Download Tool and all other updates can be installed by the phone itself. On international variants you don't have to do this because the bootloader will already be unlockable, which is why this is T-Mobile only.
You need to start downloading three updates. This patched version of international OOS is where you will start, the developer beta will upgrade the bootloader, and the full downgrade will roll you back so you can start updating. Start the downloads now, but you do not have to wait for them to finish yet; it will be a few steps before you have to use them.
Now is about the time to back up any data you want to keep. Everything on your phone will be wiped by the next step, including bootloader unlock status, all your data, the entire operating system and so on.
Now it's time to install international OOS. Place it inside the folder with MSM Download Tool and then start it up. Uncheck the SHA-256 checkbox!
Unplug your USB cable and THEN turn off your phone completely. If the USB cable is plugged in while it's turned off, it will automatically boot into the charging mode which is not what you want. Have your USB cable, and computer mouse, on the ready. You don't want to waste any time, because this may be physically painful: Hold down both volume buttons at the same time for at least 5 seconds, and then plug the USB cable into your phone. Make sure some COM port appears in the tool, then click the "Start" button in MSM Download Tool WHILE STILL HOLDING THEM DOWN. You can only let the volume buttons go AFTER you click "Start", or else the phone will drop out of EDL mode into fastboot.
The process will take a few minutes depending on how fast your USB connection is. Leave the phone plugged in until it is complete. This also gives time to download those two updates, which are together about four gigabytes in size.
Once MSM Download Tool is done flashing, you can reboot the phone and set it up using the setup wizard. Feel free to move fast and enable nothing. You don't need internet, you don't need a correct clock, you don't need accounts or telemetry or anything like that. All data will be wiped again later.
Use your computer to copy the developer preview update to the phone. Don't copy it to the Download folder or anything, copy it into the root (just inside the internal storage). Go to settings > local updates > settings icon in the top right > local update and update to the developer preview.
Once you're in the developer preview, enable OEM unlocking in developer options, reboot into fastboot mode (I do this by also enabling advanced reboot in developer options) and use fastboot oem unlock. Your bootloader is now unlocked! But we're not nearly done yet, there's still lots to do.
After rebooting, since the unlock wiped the phone, you'll have to set it up again. Just breeze through like before, then copy the rollback zip to the phone just like you did for the developer preview.
Go to local update again and use the rollback. This is required in order to go back to a stable OS that can accept OTAs. After this your data will be wiped. This is the real setup wizard. You can set it up with real data; your data will not be wiped again for the rest of this guide.
--- END OF T-MOBILE ONLY ---
If your bootloader is not already unlocked, enable OEM unlocking in developer options and then run `fastboot oem unlock` in Fastboot mode.
Next, you will want to install Magisk. This is a slightly complex process but once it's done your phone will become fully untethered.
First download a tool called Payload Dumper. Extract the entire archive into its own folder. Get an OTA update for your version of OxygenOS (if your phone is T-Mobile, that is the rollback update you just installed; if you aren't following the T-Mobile guide, you may have to download an OTA update from Google), and use WinRAR or similar to extract the `payload.bin` inside into the payload dumper's input folder.
Run the payload dumper. You don't need to run all of it; wait for "boot" to show up in the console window, then wait until something else shows up and then close the window. Inside the output folder there should be a `boot.img`; there may be other img files but the boot is what we're interested in.
Transfer this boot.img to your device and use Magisk Manager to patch it. Transfer the magisk_patched.img to your computer, reboot the phone into fastboot mode and use `fastboot flash boot magisk_patched.img`. Reboot the phone into Android.
If you start Magisk Manager you should see that Magisk is installed. Great. Next step is to install TWRP.
In my experience, flashing TWRP or using `fastboot boot twrp.img` didn't work. You're not clever if you try installing OxygenOS 9.5.4 which adds `fastboot boot` support to the bootloader; it still won't work. In my experience the only correct way to install TWRP on the OnePlus 7 Pro is to use Magisk.
(Someone in the replies below stated that you need to upgrade all the way to OOS 10 in order to boot TWRP using fastboot. This guide details the easier method using Magisk Manager.)
On the phone, go to the TWRP downloads page for the OnePlus 7 Pro, and download the latest installer. Then flash the zip using Magisk.
Crucially, at the end of the installer log it says "you are now unrooted". DO NOT IGNORE THIS MESSAGE! If you reboot now, Magisk will be gone and the stock ROM will immediately overwrite TWRP. You must use Magisk Manager to reinstall Magisk using a "Direct Install". That way, your boot.img will be patched again and your Magisk (and TWRP) will persist across reboots.
Go ahead and try it out. Reboot a few times, sometimes into recovery, sometimes into Android to test Magisk.
We're still not done yet. Wouldn't you love to stay rooted and still be running the latest version of OxygenOS? I sure would. Next I'll describe the process of applying an OTA update while keeping your root and everything. Thanks to A/B you can stay untethered.
Please note that, if you'd like to proceed with the EU version of OxygenOS, you should go grab 9.5.4 before proceeding to the next step, for example from here (MD5 fcec14e2ec053d67c793a27bfdef17d0), and use local update to install it. (note GM21BA instead of GM21AA) The EU version is supposed to have better privacy options and less bloatware, so that's what I personally went with. Converting your OxygenOS from GM21AA to GM21BA has no harmful side effects and should work on any phone. It affects the OTA you'll receive in the next step, and this is possibly the only chance you'll get to switch (or not). So choose wisely.
You can find other versions of OOS in this XDA post.
Remember to turn off all auto-updating in the OxygenOS settings. You don't want your phone suddenly losing Magisk and TWRP after any old reboot. Then you can use the OxygenOS updater to accept an official OTA update. It will recognize you're rooted and install an entire fresh new system to your inactive slot, which is exactly what we want.
There are two steps you need to perform before rebooting. The first is TWRP persistence and the second is Magisk persistence. For TWRP persistence you need to go into Magisk Manager and flash a module called "TWRP A/B retention script". Then for Magisk persistence you need to go install Magisk again, but this time to the inactive slot. You must do TWRP persistence first.
After this you should be good to go back to the update screen and hit reboot. You should still have TWRP and Magisk, but now on the very latest version of OxygenOS. Customize your phone to your heart's content now; it's all yours.
Recommended tweaks:
- install a Magisk module called "Debloater (Terminal Emulator)". Install a terminal emulator like Termux and use `su` to enter a root shell. Then you can run `debloat` and go through the list of apps, removing things you don't want. Certain services need to be watched out for, like PlayAutoInstallConfig (lets your carrier silently install apps without your consent). You can find tidbits online explaining what certain things do, like this pastebin, or this one. Houdini is the kernel driver which is very important.
- enable MagiskHide and hide yourself from Netflix and other DRM-enabled apps. Also hide yourself from Google Play's snet service.
- there is a Magisk module called F-Droid Privileged Extension, it's quite nice.
- use MagiskHide Props Config to set `net.tethering.noprovisioning=true`. This will prevent the carrier from knowing when you are using hotspot features, so they will not immediately cut your connection
- don't install a custom ROM. OxygenOS is high quality and everything you could ever want from a phone honestly. It has all the drivers and stuff for the phone and all of that cool stuff.
Small curiosities:
- SMT download mode is a special flashing mode used by the factory and it can overwrite things like the IMEI. Don't mess with it, you do not know what you're doing.
- Now that you have the software, you can literally just install a Dual SIM tray and have dual SIMs. Your phone is essentially the same as the international OP7P
- Feel free to post if you have any issues or need help with something.

Thank you mate. This will help out a lot of people coming to one plus such as myself. Only wonder I have about it all is the dual sim. I have 2 imei now but obviously both are the same. So I'm trying to figure out how that would work.

TheMadScientist said:
Thank you mate. This will help out a lot of people coming to one plus such as myself. Only wonder I have about it all is the dual sim. I have 2 imei now but obviously both are the same. So I'm trying to figure out how that would work.
Click to expand...
Click to collapse
Yeah, same here. Dual SIM phones are required to have two IMEI numbers since they technically have two transceivers, one for each SIM. Maybe one day someone will post a guide on how to change your IMEI numbers? You could keep one and change the other.

Today I had a little incident with SafetyNet.
{
"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"
}
I had installed the magisk modules Riru and Riru - EdXposed. Big mistake. Uninstalling them didn't fix it. Reinstalling the OS didn't fix it. I thought I was totally ****ed. However, toggling MagiskHide off and back on again and clearing Google Play Services' data seems to have fixed it:
Phew. This SafetyNet guide really helped
EDIT: Also make sure to clear Play Store's data so it re-checks your device for certification.

LoganDark said:
Yeah, same here. Dual SIM phones are required to have two IMEI numbers since they technically have two transceivers, one for each SIM. Maybe one day someone will post a guide on how to change your IMEI numbers? You could keep one and change the other.
Click to expand...
Click to collapse
Unfortunately we can't discuss that on xda.

TheMadScientist said:
Unfortunately we can't discuss that on xda.
Click to expand...
Click to collapse
Software spoofing is allowed. EMS flashing is not.

Riru - EdXposed seems to pass SafetyNet if you use HiddenCore module (and DO NOT BLACKLIST GOOGLE SERVICES or else they will not get patched and they will fail you). I haven't checked to see how deep this goes. Perhaps third party apps which do their own SafetyNet check will see through it. Anyone here with experience?
Edit: BAD ADVICE DO NOT USE HIDDENCORE IT WILL BREAK SAFETYNET EVEN MORE

Well I got to say your guide it's good. But the part where you can only install twrp with magisk I got to say no there. All you have to do is use the roll back package and then update your phone with the first update it allows in system update. That should put you on Oxygen os android 10. Then fastboot will work. Did it myself so I know. Best regards

LokifiedMee said:
Well I got to say your guide it's good. But the part where you can only install twrp with magisk I got to say no there. All you have to do is use the roll back package and then update your phone with the first update it allows in system update. That should put you on Oxygen os android 10. Then fastboot will work. Did it myself so I know. Best regards
Click to expand...
Click to collapse
People seem to have mixed luck regarding using fastboot to boot TWRP. I understand upgrading the bootloader can enable additional fastboot capabilities which is why I tried it myself. It didn't work for me so that's why this guide takes the safer/guaranteed approach.
I did only upgrade to a later version of OOS 9, though. It added `fastboot boot` but trying it softlocked the phone.
Note that in either case, the OnePlus 7 Pro's recovery is stored in the boot partition, and flashing a zip using Magisk is easier than flashing one with TWRP.
I have revised the post to acknowledge the alternative method.
(Also, it's worth mentioning that I know anyone following this guide probably knows how to flash a zip in TWRP. I'm not saying that's too complicated, but the guide details the process I followed specifically. There are many other guides online detailing alternative methods, but they did not work for me, which is why I made this one.)

LoganDark said:
People seem to have mixed luck regarding using fastboot to boot TWRP. I understand upgrading the bootloader can enable additional fastboot capabilities which is why I tried it myself. It didn't work for me so that's why this guide takes the safer/guaranteed approach.
I did only upgrade to a later version of OOS 9, though. It added `fastboot boot` but trying it softlocked the phone.
Note that in either case, the OnePlus 7 Pro's recovery is stored in the boot partition, and flashing a zip using Magisk is easier than flashing one with TWRP.
I have revised the post to acknowledge the alternative method.
(Also, it's worth mentioning that I know anyone following this guide probably knows how to flash a zip in TWRP. I'm not saying that's too complicated, but the guide details the process I followed specifically. There are many other guides online detailing alternative methods, but they did not work for me, which is why I made this one.)
Click to expand...
Click to collapse
No worries mate. Just giving you the heads up. Cheers

I'm unsure how to flash twrp using magisk. I used a friend's machine to flash magisk last night but don't have access now. I'm waiting on asusurion to send mine back. I stayed on the beta and updated to the latest. Would flashing or booting into twrp be possible? Thanks for the guide, btw

Leskanic said:
I'm unsure how to flash twrp using magisk. I used a friend's machine to flash magisk last night but don't have access now. I'm waiting on asusurion to send mine back. I stayed on the beta and updated to the latest. Would flashing or booting into twrp be possible? Thanks for the guide, btw
Click to expand...
Click to collapse
Apologies for the late reply.
Download the "twrp-installer" zip file and use Magisk to flash it.
After that, you have to "direct install" Magisk again.

I guess my question is which option do i use in magisk to flash the twrp installer zip file? Do I use the install module from storage option or in the section where you patch files? Could i just use terminal emulator to boot into twrp then flash twrp and magisk while I'm in twrp? Sorry for my ignorance it's been a couple years since I've had Android with an unlocked bootloader and not having my laptop doesn't help

Leskanic said:
I guess my question is which option do i use in magisk to flash the twrp installer zip file? Do I use the install module from storage option or in the section where you patch files? Could i just use terminal emulator to boot into twrp then flash twrp and magisk while I'm in twrp? Sorry for my ignorance it's been a couple years since I've had Android with an unlocked bootloader and not having my laptop doesn't help
Click to expand...
Click to collapse
The TWRP installer zip is just a Magisk module that you can flash by going to the modules section and tapping "install from storage".
Basically, step 1: go into this section and install the twrp-installer zip this way
Step 2: go here
and direct install Magisk like this
Yes, you are installing Magisk again. That is because the TWRP installer overwrote it, and if you rebooted, you would lose root (and the stock ROM would immediately overwrite TWRP, leaving your device completely stock)
As for flashing both things via TWRP, you would probably flash TWRP first and then Magisk. If you can get the phone to boot into TWRP in the first place, yeah it's probably possible and many others have probably installed their TWRP+Magisk that way.

Thanks i didn't realize the twrp installer zip could be flashed as a module. Sorry it's been a while and I'm trying to get back up to speed

I have a few XPrivacyLua hooks that can be used to change your model number to GM1917 (at least to Java apps). It doesn't have any side effects except peace of mind.
Add these using the XPrivacyLua Pro companion app (you don't need to buy Pro to edit hooks), MAKE SURE to enter GM1917 in the model text box and save, enable them for every app including system apps in XPrivacyLua, and reboot.
Enjoy

LoganDark said:
For me, pwning my new phone was a 7-hour process that required incredible learning capacity. Not everyone is prepared to go through a process like that, and it can easily take multiple days or weeks. This is a guide outlining a version of the exact process that got me to this point. It should be easy for anyone to follow, even people without much technical knowledge. (although, do be careful with the resulting root access)
I started with a GM1915, which is the T-Mobile model. You'd think it would require an unlock key from T-Mobile in order to work, but actually it doesn't. That's what they don't want you to know.
A well-known method for bypassing that requirement is to install an international OS and then upgrade it to a certain developer preview, causing the phone to update the bootloader to a non-crippled version that doesn't require an unlock key. So that's what I did.
However, the process is easier said than done. For someone like me who's done it, it's not too hard, but for a beginner it's intensely confusing. I was a beginner just yesterday and struggled with dumb error messages like "packed image not exist".
The guide is below. Sections starting with "T-MOBILE ONLY" and ending with "END OF T-MOBILE ONLY" are only to be performed on T-Mobile phones with T-Mobile firmware and a locked bootloader. If you have an unlocked bootloader then you can skip those steps.
Make sure you have a Windows machine. The Qualcomm drivers are only available for Windows, the programs are only available for Windows, people on this forum only know Windows. I have a Mac, personally, because Unix is awesome, but unfortunately nobody has thought about us and all the tools are Windows-only. I am just as disappointed as you, trust me. I used a virtual machine, but YMMV, depending on how good your hypervisor's USB passthrough is. You may want to use bare metal if you only have VirtualBox; it's not worth the effort. You will be hot plugging A LOT, and your phone will show up as many different types of USB devices.
You must have fastboot installed, but ADB is not required.
--- T-MOBILE ONLY ---
Install the "L2 drivers" for the phone. You can find them here. Just install as many of them as you can by right-clicking every `.inf` file you find and clicking Install on each one of them. Some of them will have missing files. Some of them won't have a signature. It doesn't matter, as long as you try every one of them, something will work. For me it was the 64-bit driver, in the 64 folder. All the others are 32-bit.
--- END OF T-MOBILE ONLY ---
You should probably plug the phone into your computer now and install the official OnePlus drivers as well. This is so that you can easily access the phone storage, which will become very important soon. Reboot your computer to apply the driver updates.
--- T-MOBILE ONLY ---
Download the "MSM Download Tool" from here (same link as above). Place it in its own folder. This is crucial because you must now download the guacamole-whatever.7z file and extract the .ots file into the same folder as the MSM Download Tool.
MSM Download Tool always looks in its folder for the image and pops up a cryptic error message if it's not found ("packed image not exist"). This is not very widely documented because MSM Download Tool is often distributed in the same folder as the image anyway. That's not the case when you are forced to download them as separate files.
Note that this is the only time you will have to use MSM Download Tool and all other updates can be installed by the phone itself. On international variants you don't have to do this because the bootloader will already be unlockable, which is why this is T-Mobile only.
Start the MSM Downloader tool and make sure that it's open and ready. Uncheck the SHA-256 checkbox!
You need to start downloading two updates. The developer beta will upgrade the bootloader, and the full downgrade will give you a reference boot.img to use for Magisk. Start the downloads now, but you do not have to wait for them to finish yet; it will be a few steps before you have to use them.
Now is about the time to back up any data you want to keep. Everything on your phone will be wiped by the next step, including bootloader unlock status, all your data, the entire operating system and so on.
Unplug your USB cable and THEN turn off your phone completely. If the USB cable is plugged in while it's turned off, it will automatically boot into the charging mode which is not what you want. Have your USB cable, and computer mouse, on the ready. You don't want to waste any time, because this may be physically painful: Hold down both volume buttons at the same time for at least 5 seconds, and then plug the USB cable into your phone. Make sure some COM port appears in the tool, then click the "Start" button in MSM Download Tool WHILE STILL HOLDING THEM DOWN. You can only let the volume buttons go AFTER you click "Start", or else the phone will drop out of MSM mode.
The process will take a few minutes depending on how fast your USB connection is. Leave the phone plugged in until it is complete. This also gives time to download those two updates, which are together about four gigabytes in size.
Once MSM Download Tool is done flashing, you can reboot the phone and set it up using the setup wizard. This one will be overwritten, so feel free to move fast and enable nothing. You don't need internet, you don't need a correct clock, you don't need accounts or telemetry or anything like that. All data will be wiped again later.
Use your computer to copy both updates (developer preview & rollback) to the phone. Don't copy them to the Download folder or anything, copy them into the root. Go to settings > local updates > settings icon in the top right > local update and update to the developer preview.
Once you're in the developer preview, enable OEM unlocking in developer options, reboot into fastboot mode (I do this by also enabling advanced reboot in developer options) and use `fastboot oem unlock`. Your bootloader is now unlocked! But we're not nearly done yet, there's still lots to do.
Go to local update again and use the rollback. This is required in order to go back to a stable OS that can accept OTAs. After this your data will be wiped. This is the real setup wizard. You can set it up with real data; your data will not be wiped again for the rest of this guide.
--- END OF T-MOBILE ONLY ---
If your bootloader is not already unlocked, enable OEM unlocking in developer options and then run `fastboot oem unlock` in Fastboot mode.
Next, you will want to install Magisk. This is a slightly complex process but once it's done your phone will become fully untethered.
First download a tool called Payload Dumper. Extract the entire archive into its own folder. Get an OTA update for your version of OxygenOS (if your phone is T-Mobile, that is the rollback update you just installed; if you aren't following the T-Mobile guide, you may have to download an OTA update from Google), and use WinRAR or similar to extract the `payload.bin` inside into the payload dumper's input folder.
Run the payload dumper. You don't need to run all of it; wait for "boot" to show up in the console window, then wait until something else shows up and then close the window. Inside the output folder there should be a `boot.img`; there may be other img files but the boot is what we're interested in.
Transfer this boot.img to your device and use Magisk Manager to patch it. Transfer the magisk_patched.img to your computer, reboot the phone into fastboot mode and use `fastboot flash boot magisk_patched.img`. Reboot the phone into Android.
If you start Magisk Manager you should see that Magisk is installed. Great. Next step is to install TWRP.
In my experience, flashing TWRP or using `fastboot boot twrp.img` didn't work. You're not clever if you try installing OxygenOS 9.5.4 which adds `fastboot boot` support to the bootloader; it still won't work. In my experience the only correct way to install TWRP on the OnePlus 7 Pro is to use Magisk.
(Someone in the replies below stated that you need to upgrade all the way to OOS 10 in order to boot TWRP using fastboot. This guide details the easier method using Magisk Manager.)
On the phone, go to the TWRP downloads page for the OnePlus 7 Pro, and download the latest installer. Then flash the zip using Magisk.
Crucially, at the end of the installer log it says "you are now unrooted". DO NOT IGNORE THIS MESSAGE! If you reboot now, Magisk will be gone and the stock ROM will immediately overwrite TWRP. You must use Magisk Manager to reinstall Magisk using a "Direct Install". That way, your boot.img will be patched again and your Magisk (and TWRP) will persist across reboots.
Go ahead and try it out. Reboot a few times, sometimes into recovery, sometimes into Android to test Magisk.
We're still not done yet. Wouldn't you love to stay rooted and still be running the latest version of OxygenOS? I sure would. Next I'll describe the process of applying an OTA update while keeping your root and everything. Thanks to A/B you can stay untethered.
Please note that, if you'd like to proceed with the EU version of OxygenOS, you should go grab 9.5.4 before proceeding to the next step, for example from here, and use local update to install it. (note GM27BA instead of GM27AA) The EU version is supposed to have better privacy options and less bloatware, so that's what I personally went with. Converting your OxygenOS from GM27AA to GM27BA has no harmful side effects and should work on any phone. It affects the OTA you'll receive in the next step, and this is possibly the only chance you'll get to switch (or not). So choose wisely.
Remember to turn off all auto-updating in the OxygenOS settings. You don't want your phone suddenly losing Magisk and TWRP after any old reboot. Then you can use the OxygenOS updater to accept an official OTA update. It will recognize you're rooted and install an entire fresh new system to your inactive slot, which is exactly what we want.
There are two steps you need to perform before rebooting. The first is TWRP persistence and the second is Magisk persistence. For TWRP persistence you need to go into Magisk Manager and flash a module called "TWRP A/B retention script". Then for Magisk persistence you need to go install Magisk again, but this time to the inactive slot. You must do TWRP persistence first.
After this you should be good to go back to the update screen and hit reboot. You should still have TWRP and Magisk, but now on the very latest version of OxygenOS. Customize your phone to your heart's content now; it's all yours.
Recommended tweaks:
- install a Magisk module called "Debloater (Terminal Emulator)". Install a terminal emulator like Termux and use `su` to enter a root shell. Then you can run `debloat` and go through the list of apps, removing things you don't want. Certain services need to be watched out for, like PlayAutoInstallConfig (lets your carrier silently install apps without your consent). You can find tidbits online explaining what certain things do, like this pastebin, or this one. Houdini is the kernel driver which is very important.
- enable MagiskHide and hide yourself from Netflix and other DRM-enabled apps. Also hide yourself from Google Play's snet service.
- there is a Magisk module called F-Droid Privileged Extension, it's quite nice.
- use MagiskHide Props Config to set `net.tethering.noprovisioning=true`. This will prevent the carrier from knowing when you are using hotspot features, so they will not immediately cut your connection
- don't install a custom ROM. OxygenOS is high quality and everything you could ever want from a phone honestly. It has all the drivers and stuff for the phone and all of that cool stuff.
Small curiosities:
- SMT download mode is a special flashing mode used by the factory and it can overwrite things like the IMEI. Don't mess with it, you do not know what you're doing.
- Now that you have the software, you can literally just install a Dual SIM tray and have dual SIMs. Your phone is essentially the same as the international OP7P
- Feel free to post if you have any issues or need help with something.
Click to expand...
Click to collapse
It isn't very clear what version of OOS you started on. If I'm running OOS10 on stock this should still (in theory) work right?

r4w0ne said:
It isn't very clear what version of OOS you started on. If I'm running OOS10 on stock this should still (in theory) work right?
Click to expand...
Click to collapse
OOPS, fuck, I missed a step. You have to use MSM Download Tool to clean install this patched OOS before installing the developer preview. I'll update the post ASAP
Edit: Post has been updated

LoganDark said:
OOPS, ****, I missed a step. You have to use MSM Download Tool to clean install this patched OOS before installing the developer preview. I'll update the post ASAP
Click to expand...
Click to collapse
Glad I asked lol.

r4w0ne said:
Glad I asked lol.
Click to expand...
Click to collapse
I actually mentioned installing international OOS in the post but for some reason I didn't link it or provide instructions. Silly me...
Edit: Post has been updated

LoganDark said:
I actually mentioned installing international OOS in the post but for some reason I didn't link it or provide instructions. Silly me...
Edit: Post has been updated
Click to expand...
Click to collapse
New problem, OEM unlocking is greyed out in the options on the developer preview...
EDIT: I'm a retard and didn't follow instructions. Ignore.

Question Root Guide

Method To Root New Oneplus Nord CE 5G?

Pradeep1407 said:
Method To Root New Oneplus Nord CE 5G
Click to expand...
Click to collapse
Are you asking or telling?

I just ordered and my phone is on its way. It will be my first time with anything that is not a Samsung.
I'd love to root it with Magisk but I understand its a new model, I won't find detailed procedures etc. Anyway, do any of the more experienced rooters and modders have advice for me?
Should I start by trying unlocking the bootloader with some procedure from another OnePlus model? Which one? Thanks
EDIT:
let me elaborate a bit more on why I am asking. I realize it might not be possible to fully root the phone now, maybe some details need to be ironed out. But I would love to avoid having to do later any steps that involve losing data.
Typically, the unlocking of bootloader clears everything in your phone, right? So it would be nice to get that part done as soon as it arrives, even if I can only do the rest later, once the pros develop the tutorials here.
By "do the rest later" I mean install a recovery like TWRP or OrangeFox, and put Magisk on it, EdXposed, etc.
Does my strategy make sense?

pgorod said:
I just ordered and my phone is on its way. It will be my first time with anything that is not a Samsung.
I'd love to root it with Magisk but I understand its a new model, I won't find detailed procedures etc. Anyway, do any of the more experienced rooters and modders have advice for me?
Should I start by trying unlocking the bootloader with some procedure from another OnePlus model? Which one? Thanks
EDIT:
let me elaborate a bit more on why I am asking. I realize it might not be possible to fully root the phone now, maybe some details need to be ironed out. But I would love to avoid having to do later any steps that involve losing data.
Typically, the unlocking of bootloader clears everything in your phone, right? So it would be nice to get that part done as soon as it arrives, even if I can only do the rest later, once the pros develop the tutorials here.
By "do the rest later" I mean install a recovery like TWRP or OrangeFox, and put Magisk on it, EdXposed, etc.
Does my strategy make sense?
Click to expand...
Click to collapse
Hey! Congrats on the new phone! I got it too. Your strategy does make sense to me but there are other things that need to be figured out too like the A-B system of Rom handling phones have. So I'd say wait for a bit and take a backup and restoe it when you root eventually.

The main reason I want root is to have proper, complete backups.
How exactly does one backup without root? I know, Google data is on the cloud, and I can copy files form the SD card, but that means dozens of wasted hours re-configuring every single option in every single app (I'm that kind of guy)... sigh...
Thanks for the tip on A/B updates, I went reading about it, it's news to me and it is quite interesting.

almost.lunatic said:
Hey! Congrats on the new phone! I got it too. Your strategy does make sense to me but there are other things that need to be figured out too like the A-B system of Rom handling phones have. So I'd say wait for a bit and take a backup and restoe it when you root eventually.
Click to expand...
Click to collapse
exactly, wait for a sometime and then rooting is better.

You can download the oos ZIP and extract the boot image, patch it with magisk app, unlock the bootloader (this will wipe your data!) boot to the boot image you made and install magisk via the app (direct install)
Rooting oneplus phones are fairly easy tho.
No idea about SafetyNet on the CE yet

SafetyNet is working
{
"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"
}

Manugamé said:
SafetyNet is working
Click to expand...
Click to collapse
Interesting - mine isn't!
How exactly did you root?
I downloaded the stock ROM from OTA, patched with Magisk on the device, moved it back to a PC, and flashed it from fastboot.
More details here: https://forum.xda-developers.com/t/...-stock-roms-for-nord-ce.4296379/post-85427971

pgorod said:
Interesting - mine isn't!
How exactly did you root?
I downloaded the stock ROM from OTA, patched with Magisk on the device, moved it back to a PC, and flashed it from fastboot.
More details here: https://forum.xda-developers.com/t/...-stock-roms-for-nord-ce.4296379/post-85427971
Click to expand...
Click to collapse
I used the same method, it's weird. do you have magisk hide activated ? I don't know if it's necessary.

Manugamé said:
I used the same method, it's weird. do you have magisk hide activated ? I don't know if it's necessary.
Click to expand...
Click to collapse
I tried turning it on (both MagiskHide and Hide the Magisk app, which renames the app), rebooted, but still the Safety Net check fails.
I am using Magisk 23.0...
Strange!

Im far from pro and after 3h on windows 10 trying to extrakt the payload.bin file with diffrent tools i have failed . Asking for help getting the boot.img i need to use with magisk.

krille74 said:
Im far from pro and after 3h on windows 10 trying to extrakt the payload.bin file with diffrent tools i have failed . Asking for help getting the boot.img i need to use with magisk.
Click to expand...
Click to collapse
You can use https://github.com/vm03/payload_dumper to dump the payload.bin.
Just follow the guide.

Manugamé said:
You can use https://github.com/vm03/payload_dumper to dump the payload.bin.
Just follow the guide.
Click to expand...
Click to collapse
thanks finaly was alot of work had problems with all thinks about windows possible .

So is it working with safety net or no . Bcuz I use payment apps , which require this.

ksulaiman579 said:
So is it working with safety net or no . Bcuz I use payment apps , which require this.
Click to expand...
Click to collapse
Safety net works with magisk hide + renaming magisk app

Installing ROOT
1. Reboot the device in TWRP recovery
2. Flashing Magisk
3. Reboot into the system.
4. Install Magisk manager. Rebuild Magisk with a different name and check the box on Magisk Hide.
5. Install 4 add-ons from under Magisk.
Checking.
ROOT is, Safety net is passing. Gpay working.

TWRP recovery? For Nord CE 5G? That's a novelty for me!
.... seaching ...
Here it is!
[RECOVERY] [11] [ALPHA] TeamWin Recovery Project (ebba) (2021-09-09)
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com

I tried installing the 4 Magisk 4 addons you provided, but my SafetyNet check still fails.
Desite all the installs apparently going well, now I only see these listed as installed:
MagiskHide Props v6.0.2
Riru 26.1.2
Riru-Edxposed (I already had this) 0.5.2.2
Universal SafetyNet Fix 2.0.0
Do I need to do something else?

pgorod said:
I tried installing the 4 Magisk 4 addons you provided, but my SafetyNet check still fails.
Desite all the installs apparently going well, now I only see these listed as installed:
MagiskHide Props v6.0.2
Riru 26.1.2
Riru-Edxposed (I already had this) 0.5.2.2
Universal SafetyNet Fix 2.0.0
Do I need to do something else?
Click to expand...
Click to collapse
Rebuild Magisk with a different name and check the box on Magisk Hide. Did you?

Question How to root Redmi Note 11?

Hi. I am new to this site.
I want to root my Redmi Note 11 but I don't know how to.
I tried looking up online but all I could find were guides on other devices. And outdated too.
I read about Magisk and Magisk Hide which allows you to pass SafetyNet but I also read that it's developer joined Google. So I don't know if it will work or not.
Please help me.
How can I root my phone and pass SafetyNet?
Device Specs:
{
"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"
}

The first step is to unlock your bootloader which usually takes a week. Do that first, then you can browse more and wait for answers while you wait

I have already requested Mi for permission to unlock bootloader. I had to wait 5 days and today is the last day.

parker_04 said:
I have already requested Mi for permission to unlock bootloader. I had to wait 5 days and today is the last day.
Click to expand...
Click to collapse
Make sure to backup all your data before unlocking bootloader as it will wipe them.
I strongly recommend flashing Xiaomi.eu Stable ROM first as it offers more features than stock and also, you don't have to look for the boot.img again. But in case you want to keep it stock, you want to find the flashboot ROM with the exact same version as the one you have right now and extract the boot.img from it. Then you want to get magisk on your phone, transfer the boot.img to your phone, patch it, transfer it back to your computer, and then use ADB to flash the boot.img

parker_04 said:
Hi. I am new to this site.
I want to root my Redmi Note 11 but I don't know how to.
I tried looking up online but all I could find were guides on other devices. And outdated too.
I read about Magisk and Magisk Hide which allows you to pass SafetyNet but I also read that it's developer joined Google. So I don't know if it will work or not.
Please help me.
How can I root my phone and pass SafetyNet?
Device Specs:
View attachment 5807325
Click to expand...
Click to collapse

notBradPitt said:
Make sure to backup all your data before unlocking bootloader as it will wipe them.
I strongly recommend flashing Xiaomi.eu Stable ROM first as it offers more features than stock and also, you don't have to look for the boot.img again. But in case you want to keep it stock, you want to find the flashboot ROM with the exact same version as the one you have right now and extract the boot.img from it. Then you want to get magisk on your phone, transfer the boot.img to your phone, patch it, transfer it back to your computer, and then use ADB to flash the boot.img
Click to expand...
Click to collapse
Thank you for replying.
I am quite newbie in rooting.
I can understand enough to follow your instructions but not enough to really know what I am doing.
Can you please elaborate each step and what it does?
Or maybe refer me to a trusted guide where I can understand the tidbits.

parker_04 said:
Thank you for replying.
I am quite newbie in rooting.
I can understand enough to follow your instructions but not enough to really know what I am doing.
Can you please elaborate each step and what it does?
Or maybe refer me to a trusted guide where I can understand the tidbits.
Click to expand...
Click to collapse
I think this sums it pretty well: https://forum.xda-developers.com/t/installing-miui-eu-rom-and-root.4426937/
- Backing up data: Back up your data so it won't be lost during bootloader unlock
- Unlock bootloader: allows you to flash into your phone
- Flashing Xiaomi.eu (optional): Their ROM is based on MIUI Global/China which has way more features than region based ROMs and no bloatware. Cons is you have to manually update it and you can't update system apps (as they're also modified to disable ads). Pros is, you know the version you just flashed and the boot.img is also there.
- Finding boot.img: This is the file you want to patch if you want to root your phone. You can find this by extracting the fastboot ROM and it should be inside. In case of stock MIUI, you have to download the exact version that you have right now on https://xiaomifirmwareupdater.com/ , get the flashboot version, extract, and boot.img should be inside
The rest should be explained in the post above and I think this will also help in installation of Magisk https://topjohnwu.github.io/Magisk/install.html

@notBradPitt Hey, is this the correct fastboot rom for my device?
https://sourceforge.net/projects/xi...MNote11_V13.0.5.0.SGKMIXM_v13-12.zip/download

parker_04 said:
@notBradPitt Hey, is this the correct fastboot rom for my device?
https://sourceforge.net/projects/xi...MNote11_V13.0.5.0.SGKMIXM_v13-12.zip/download
Click to expand...
Click to collapse
Yes. After unlocking bootloader, make sure USB debugging is enabled (because you just reset the phone), boot into flashboot mode, and run the "first install" script. Make sure your cables are connected properly so it doesn't corrupt any files. First time booting will take around 15-20 minutes for me, so this is normal and you shouldn't panic.
After that you can continue with the root process. The boot.img should be in "images" folder. Once you are done with it, you can try the tools listed here (https://www.xda-developers.com/how-to-pass-safetynet-android/) to pass SafetyNet. You can test the SafetyNet using the tool in Magisk or you can use YASNAC (from Google Play or GitHub)

notBradPitt said:
Yes. After unlocking bootloader, make sure USB debugging is enabled (because you just reset the phone), boot into flashboot mode, and run the "first install" script. Make sure your cables are connected properly so it doesn't corrupt any files. First time booting will take around 15-20 minutes for me, so this is normal and you shouldn't panic.
After that you can continue with the root process. The boot.img should be in "images" folder. Once you are done with it, you can try the tools listed here (https://www.xda-developers.com/how-to-pass-safetynet-android/) to pass SafetyNet. You can test the SafetyNet using the tool in Magisk or you can use YASNAC (from Google Play or GitHub)
Click to expand...
Click to collapse
Thank a lot for your help!
Reply from recently flashed Xiaomi Eu ROM.

parker_04 said:
Thank a lot for your help!
Reply from recently flashed Xiaomi Eu ROM.
Click to expand...
Click to collapse
No problem How do you like it? Have you proceeded with root yet?

notBradPitt said:
No problem How do you like it? Have you proceeded with root yet?
Click to expand...
Click to collapse
It's nice.
Xiaomi eu is certainly cleaner than stock. Adless and bloatless. It has new features although some of the stock's features are missing. Play Store is jittery for unknown reasons.
And when I try to open a file in another app, the app list appears quite late and it's laggy too. But that's all and I don't mind it.
Thanks again for recommending it.

notBradPitt said:
Have you proceeded with root yet?
Click to expand...
Click to collapse
Yeah. Rooting with magisk is so easy. And it's uninstallation is easy too.

parker_04 said:
I have already requested Mi for permission to unlock bootloader. I had to wait 5 days and today is the last day.
Click to expand...
Click to collapse
Yo I'm new to rooting ,so during the 168 hours period can I switch from data to Wi-Fi and use it for like watching videos and playing games?

creepystaircase66 said:
Yo I'm new to rooting ,so during the 168 hours period can I switch from data to Wi-Fi and use it for like watching videos and playing games?
Click to expand...
Click to collapse
Yes, data is only needed when you request for permission

Assuming you have unlocked the bootloader
Step by Step Guide:
1. Download Magisk APK and install it
2. Patch your Recovery (Stock, TWRP, Skyhawk, etc) in magisk app and copy the patched img to Computer
3. Switch it off, then boot to bootloader, and type "fastboot flash boot recovery_patched.img" where recovery_patched.img is your file name.
4. Reboot (Might take longer than usual) and open magisk to confirm the the result of actions.