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

[KERNEL] [NMF26U] [Jan 4] Stock Kernel + SafetyNet Patch

Stock Pixel/PixelXL Kernel + SafetyNet Patch
Current version: android-msm-marlin-3.18-nougat-mr1
Suitable for build: NMF26U
Security patch level: January 5, 2017
I compiled the stock kernel for the Pixel/PixelXL (they both use the same kernel) and applied the SafetyNet patch by sultanxda. The kernel name says marlin, but this also works on sailfish. Google just created one kernel that works on both sailfish (Pixel) and marlin (Pixel XL) devices.
Use case for this kernel:
- If you want to stay completely stock, but have an unlocked bootloader, the SafetyNet is tripped which disables features such as Android Pay.
- This kernel is completely stock except for the addition of a patch that removes the SafetyNet check.
- If you do not have an unlocked bootloader there is no need to use this kernel. It's exactly the same as the kernel included in the stock builds, except with the addition of the SafetyNet patch.
Installation:
- Download attached .zip and unzip into a folder
- Reboot device into bootloader (power down device, then Power + Volume down)
- Connect device to computer
- Verify connection by typing 'fastboot devices'. Your device should show up (check serial number)
- Enter command: fastboot flash kernel <kernel_image>
- Once flashing is complete, enter command: fastboot reboot
- Disconnect device and wait for reboot sequence to complete.
- You now have a stock Pixel with an unlocked bootloader that can use Android Pay
**WARNING**
If flashing this kernel for whatever reason ruins your device, please don't hold me accountable. Use this at your own risk!
And otherwise, I'm not a professional developer, just a hobbyist. Please don't ask me for a ton of help, I only created this kernel because I want to run completely stock, but still use Android Pay while having an unlocked bootloader in case I ever decide to root my device in the future (am running a Verizon Pixel). I will try to maintain this kernel with each new release until I lose interest
Downloads:
NMF26U
All versions

If one wants to stay completely stock wouldn't they just keep bootloader locked?
Edit: nevermind seems like this will cater to Verizon pixel owners since you can't unlock the bootloader on latest build. Good job!
Sent from my Pixel using Tapatalk

joetheshmo said:
If one wants to stay completely stock wouldn't they just keep bootloader locked?
Edit: nevermind seems like this will cater to Verizon pixel owners since you can't unlock the bootloader on latest build. Good job!
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Yep, let's us unlock the bootloader in case we need it in the future, without committing to any mods or losing Android Pay just yet.

Stock + Safetynet patch.... Finally.
Thank you

Thanks for sharing your work, OP.
Sent from my Pixel using Tapatalk

Any chance of you turning this into a flashable TWRP zip? Then I could run ElementalX and root when I want to, and flash back to stock if I want to, all from my phone, in a single reboot.

Just want to confirm that this is for Sailfish also. The name of the file is marlin and just want to make sure. Thanks

@Sakete, I appreciate your attitude.... You need something, you just make it.

jay661972 said:
Just want to confirm that this is for Sailfish also. The name of the file is marlin and just want to make sure. Thanks
Click to expand...
Click to collapse
Yes, it will also work on sailfish. Sailfish and marlin both use the same kernel. I installed it last night on my own Pixel (sailfish) and it works great, no issues so far (and am not expecting any since it's just stock + safety net bypass patch)
Sent from my Pixel using Tapatalk

Your Verizon Pixel can be unlocked and rooted, yet Android Pay works. What else can you want, right?

Sakete said:
Yes, it will also work on sailfish. Sailfish and marlin both use the same kernel. I installed it last night on my own Pixel (sailfish) and it works great, no issues so far (and am not expecting any since it's just stock + safety net bypass patch)
Click to expand...
Click to collapse
You are right there should have no issues at all since the change was the safetynet patch.
Thanks for this..

quangtran1 said:
Your Verizon Pixel can be unlocked and rooted, yet Android Pay works. What else can you want, right?
Click to expand...
Click to collapse
Android Pay will not work with root. This only enables Android Pay to work with an unlocked bootloader. If you root your phone as well, Android Pay will not work.

Sakete said:
Android Pay will not work with root. This only enables Android Pay to work with an unlocked bootloader. If you root your phone as well, Android Pay will not work.
Click to expand...
Click to collapse
Sure it does. AP works on both of my Pixel and Pixel XL. Here's the trick. Well, actually, it's no trick, but it's something I remembered from 6.0. With 6.0, you could temporarily unroot, add cards in AP, then resume root. You have to add your credit cards in AP prior to rooting.
In the beginning, I rooted first, then AP couldn't get past the Add Card screen. I flashed back to 7.1.1 stock, install your (or any) SafetyNet-bypassing kernel. That gets AP working (allows me to add cards). Then re-root.
If screenshots are needed to demonstrate this, I can do that, but that seems rather childish.
---------- Post added at 12:20 PM ---------- Previous post was at 12:15 PM ----------
Sakete said:
Android Pay will not work with root. This only enables Android Pay to work with an unlocked bootloader. If you root your phone as well, Android Pay will not work.
Click to expand...
Click to collapse
Here goes, unlocked BL + rooted + Android Pay. Screenshot of my multitask screen.
{
"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"
}

quangtran1 said:
Sure it does. AP works on both of my Pixel and Pixel XL. Here's the trick. Well, actually, it's no trick, but it's something I remembered from 6.0. With 6.0, you could temporarily unroot, add cards in AP, then resume root. You have to add your credit cards in AP prior to rooting.
In the beginning, I rooted first, then AP couldn't get past the Add A Card screen. I flashed back to 7.1.1 stock, install your (or any) SafetyNet-bypassing kernel. That gets AP working (allows me to add cards). Then re-root.
If screenshots are needed to demonstrate this, I can do that, but that seems rather childish.
---------- Post added at 12:20 PM ---------- Previous post was at 12:15 PM ----------
Here goes, unlocked BL + rooted + Android Pay. Screenshot of my multitask screen.
Click to expand...
Click to collapse
That's good to know. If I ever decide to root my device, this will be my workaround (and since I already added my card I should now be able to root it without incident regarding Android Pay).
Thanks for sharing!

Sakete said:
That's good to know. If I ever decide to root my device, this will be my workaround (and since I already added my card I should now be able to root it without incident regarding Android Pay).
Thanks for sharing!
Click to expand...
Click to collapse
No, thank YOU for the kernel.
One item I must mention. That is, AP will break if you disable login security, or even just changing from PIN to password, or anything that would normally require a reactivation of your Android Pay credit cards. Then you just need to reflash the kernel, which in essence kills root. Add back AP, then reroot.
... Of course, Google can always implement another layer to circumvent this workaround in the future. But that's what makes Android fun.

thank you for this kind sir.
*next on my list is a deodexed stock 7.1 so i can start themeing this device...
time to bring BuuF back

Doesn't work for me. I unlocked my VZW Pixel with depixel, took the OTA to 7.1.1, but when I flash this kernel it reverts me to 7.1, and lots of stuff is broken like the soft key buttons stop functioning. Gotta factory reset...

pigmoose said:
Doesn't work for me. I unlocked my VZW Pixel with depixel, took the OTA to 7.1.1, but when I flash this kernel it reverts me to 7.1, and lots of stuff is broken like the soft key buttons stop functioning. Gotta factory reset...
Click to expand...
Click to collapse
Odd... that isn't supposed to happen. Were you rooted when you flashed?
And did you by chance take the OTA for NMF26Q? This kernel is for NMF26O, might not be compatible with the Q build. Haven't created a new kernel yet, will probably just wait for the January update.

pigmoose said:
Doesn't work for me. I unlocked my VZW Pixel with depixel, took the OTA to 7.1.1, but when I flash this kernel it reverts me to 7.1, and lots of stuff is broken like the soft key buttons stop functioning. Gotta factory reset...
Click to expand...
Click to collapse
Sakete said:
Odd... that isn't supposed to happen. Were you rooted when you flashed?
And did you by chance take the OTA for NMF26Q? This kernel is for NMF26O, might not be compatible with the Q build. Haven't created a new kernel yet, will probably just wait for the January update.
Click to expand...
Click to collapse
almost sounds like the active slot got swapped from A to B or B to A. When that happens the previous update boots instead of the current build.
the active slot can be changed in bootloader w/fastboot.
I believe the command for that is:
1. fastboot set_active _a
or
2. fastboot set_active _b
depending on which slot you want active.

I assume that we can flash this over a custom kernel no problem in order to go back to stock?

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...

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.