Database Develop

Kernel Patch for Android Pay (LineageOS)?

I'm creating this thread since we're not allowed to discuss a kernel patch for LOS 14.1 to make Android Pay work on the official thread. From my understanding the biggest issue right now is that Android Pay does not work on LOS because it cannot pass SafetyNet because of unlocked bootloader. We cannot lock the bootloader because we risk hard-bricking the device.
Some (most?) banking apps can still work by flashing Magisk 10.2 and then using Magisk Hide on the banking app, however Android Pay cannot.
Anyone who has any work-in-progress on a kernel patch feel free to post or let us know of any updates. Thank you.
edit: SOLUTION: https://forum.xda-developers.com/showpost.php?p=70831797&postcount=3665

Was just looking for someone to pose the same question, I'm eagerly waiting to see if anyone has had any luck

Please try this patch
https://review.lineageos.org/#/c/152083/

josephjdrew said:
Was just looking for someone to pose the same question, I'm eagerly waiting to see if anyone has had any luck
Click to expand...
Click to collapse
deathscythemeng said:
Please try this patch
https://review.lineageos.org/#/c/152083/
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=70831797&postcount=3665

AfouToPatisa said:
https://forum.xda-developers.com/showpost.php?p=70831797&postcount=3665
Click to expand...
Click to collapse
Following the directions in that post I:
Flashed the Lineage addonsu-remove package because I was rooted the Lineage way
reboot
Flash the gemini-safetynetpass package
Reboot
That didn't work (Android Pay still rejected my device).
So I wiped System, Cache, Dalvik, then reinstalled latest LOS.
Reboot and reinstall the gemini-safetynet pass zip.
Still Android Pay won't work.
What is going wrong?
My final intention is to root the device with Magisk. If I install it now, will it help at all?

The patch is working for me. SafetyNet passed.
Please check SafetyNet at first.
{
"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 MI 5 using Tapatalk

p8pepe said:
The patch is working for me. SafetyNet passed.
Please check SafetyNet at first.
Click to expand...
Click to collapse
SafetyNet fails... "CTS profile mismatch"
I'll try again with a fully clean install tomorrow - unless I can get a better suggestion before then.

AaronWhiting said:
SafetyNet fails... "CTS profile mismatch"
I'll try again with a fully clean install tomorrow - unless I can get a better suggestion before then.
Click to expand...
Click to collapse
I pass SafetyNet too now. Are you sure you removed root completely? Maybe run a root checker or something. Did you flash the kernel patch with "install zip" option on twrp? Which twrp version are you on? I'm on 3.0.3, it has a small bug for me (takes long time to start) but it's quite good and stable.

AfouToPatisa said:
I pass SafetyNet too now. Are you sure you removed root completely? Maybe run a root checker or something. Did you flash the kernel patch with "install zip" option on twrp? Which twrp version are you on? I'm on 3.0.3, it has a small bug for me (takes long time to start) but it's quite good and stable.
Click to expand...
Click to collapse
Yes, I did all that. Root definitely not enabled. Installed zips using TWRP 3.0.3.

AaronWhiting said:
Yes, I did all that. Root definitely not enabled. Installed zips using TWRP 3.0.3.
Click to expand...
Click to collapse
It's very weird. Seems like you do everything right. I'm very new to this, so maybe wait for an advanced user to answer. If I was you, I might try to play with the developer options (disable debugging, enable oem unlock etc) or reflash the patch zip or flash magisk zip (and then open magisk app and enable magisk hide).

AaronWhiting said:
Yes, I did all that. Root definitely not enabled. Installed zips using TWRP 3.0.3.
Click to expand...
Click to collapse
Please try to downgrage TWRP to official 3.0.2-3 and install Lineage once again. Maybe that will help.
BTW, I've made first payment today on Mi 5 and it works flawlessly, so many thanks for the patch! [emoji1]
Sent from my MI 5 using Tapatalk

So, completely clean flash today. I wiped everything, including formatting my entire data partition.
Still failing... still trying...

You must do something wrong, but I don't know what exactly. Did you try to downgrade your TWRP version to official? Can you upload screenshot from TWRP after applying the patch?
Sent from my MI 5 using Tapatalk

p8pepe said:
You must do something wrong, but I don't know what exactly. Did you try to downgrade your TWRP version to official? Can you upload screenshot from TWRP after applying the patch?
Sent from my MI 5 using Tapatalk
Click to expand...
Click to collapse
No. The only users I know who have it working are using TWRP 3.0.3 as well. I don't want to downgrade it.
My patch install dialogue all looks good, but nevermind. I wasted a day on this. Can't afford any more time, so I've restored my backup.
Maybe I'll try another time.

I have TWRP 3.0.2-3 and Android Pay is working fine. I've advised you to temporarily downgrade to official, because 3.0.3 is not perfect yet. Personally I had major problem with booting on encrypted device so I had to do that. You can upgrade again to 3.0.3 at any time, but it's your choice.
Regards!
Sent from my MI 5 using Tapatalk

AaronWhiting said:
So, completely clean flash today. I wiped everything, including formatting my entire data partition.
Still failing... still trying...
Click to expand...
Click to collapse
I've heard stories of people who had root left after a factory reset. Maybe try to re-flash SU uninstall zip? And if you ever installed magisk then flash magisk uninstall zip too... Just to make sure 100% there is no traces of root left.
Btw you are flashing the whole safetynetpass zip not just the .img right?
I'm running out of ideas...

AfouToPatisa said:
I've heard stories of people who had root left after a factory reset. Maybe try to re-flash SU uninstall zip? And if you ever installed magisk then flash magisk uninstall zip too... Just to make sure 100% there is no traces of root left.
Btw you are flashing the whole safetynetpass zip not just the .img right?
I'm running out of ideas...
Click to expand...
Click to collapse
Its ok. I'm over it.
I definitely didn't have root. I'm sure that wasn't the problem.
I even tried it with super clean install. No gapps, no other apps restored, just one to check safety net.
Thanks anyway. I'd still rather carry a credit card than go back to MIUI or waste more time trying.

Me too...
I tried that patch on my Mi5 32GB running RR v5.8.1 after unrooting it and found the device in a bootloop. Just like @AaronWhiting, I'm also flashing from TWRP v3.0.3 stable (but unofficial). Now that would be an entirely new case in itself (since he didn't have any bootloop), but I don't think RR could be an issue since it is also LOS-based, and in fact, I used the 'addonsu-remove-arm64-signed.zip' from LOS extras section to unroot the ROM (RR has built-in root enabled by default) and it worked. Just wanted to ask you guys @p8pepe and @AfouToPatisa , what setup did you have to get a positive result, like say the LOS/other ROM version on which you flashed the safetynetpass zip, device encryption state, and of course the TWRP version as well? Though I understand that you @AaronWhiting have stopped trying to get this thing working, I request you to post your device state as well.
As for me, I am presently on RR v5.8.1 official, GApps micro, no encryption and TWRP 3.0.3. Please add any other important parameter that I may have missed. Let us see if we can solve this out...:fingers-crossed:

Hey,
I have official TWRP 3.0.2-3, LOS 20170131 (clean install - no experimental migration used), opengapps nano. The device is encrypted.
I also had bootloops on TWRP 3.0.3 (probably due to encryption), so downgraded to official.
Sent from my MI 5 using Tapatalk

I'm also using TWRP 3.0.3 & LOS 20170131. Ext partitions all around. Nothing encrypted.
I have been with CM and now LOS since early days of Mi5. Used experimental migration to LOS originally, but went straight to latest version when I did the recent clean flash.
I suspect it's something to do with Bootloader / boot partition but don't have the know-how to troubleshoot further.
I sent @kyasu a PM asking him to check out this thread and help if he can since its his mod were talking about and he'll have the expertise, but haven't heard back yet.
---------- Post added at 11:36 AM ---------- Previous post was at 11:33 AM ----------
Also, I'm surprised about your troubles with encryption on 3.0.3 @p8pepe since it was specifically meant to FIX those issues.

Confused About Different Options to Root P10 VTR-L09

Hi all,
My build number is
VTR-L09C432B171
I am at the stage where I can now run either of those TWRP version:
1. twrp-3.1.1-0-vtr.img
MD5: 47e83bee437506e1308ca2e29fe30e9c
2. twrp_3.1.1_fromfuture.img
MD5: a4dd832349d345e187b4c125f2a81e18
Before going further, I would like to ask some advice. As a newbie, I want to go SLOW so I don't take a step I might regret.
First, let me clarify my goal. At this stage I am not looking for a custom ROM, but just root access so I can run things like AdAway, Titanium, Uninstall, NotificationsOff...
I found different information about rooting the P10.
For my goal, which will be best?
1. SuperSU-v2.82.zip
http://www.teamandroid.com/2017/04/19/root-huawei-p10-emui-51-android-nougat/
2. Magisk
https://forum.xda-developers.com/p10/how-to/guide-huawei-p10-root-magisk-magisk-t3625151
3. SuperRoot_noverity_nocrypt.zip
https://forum.xda-developers.com/p10/help/root-huawei-p10-p10-t3589946
4. fRomFuture
https://forum.xda-developers.com/p10/development/rom-fromfuture-stock-rom-b164-t3657812
Thank you in advance for helping me out of this confusing place!

Hey Mate,
i also did try some of your posted links on my Huawei P10 but i runned in some problems. I think you also need an external SD Card to work with.
My experience so far :
1. SuperSU-v2.82.zip
When i flashed the ZIP, i didnt got any root rights on my devices.
The Phone wasn't brick, but i just had no root rights on it.
I am not sure this is defintly not working, i readed some postive Feedbacks in the internet. Its just my experience.
http://www.teamandroid.com/2017/04/19/root-huawei-p10-emui-51-android-nougat/
3. SuperRoot_noverity_nocrypt.zip
The behavoir was the same like the 1. SuperSu-v2.82.zip
I am not sure this is defintly not working, i readed also some postive Feedbacks in the internet. Its just my experience. Maybe if you got time to try i would be happy to get a Feedback from you.
https://forum.xda-developers.com/p10...0-p10-t3589946
2. Magisk
After my Trys with the Root Zips, i tried to enable the "Root" by systemless Rooting with Magisk.
First i tried the Version 14, which didnt worked for me.
After that i tried the Version 12 from Magisk, which i did exactly like the information as you got from MusicHeat:
https://forum.xda-developers.com/p10/how-to/guide-huawei-p10-root-magisk-magisk-t3625151
This got me the Root rights on my P10.
Important: When you try to Root your phone systemless with Magisk you must have your Stock Firmeware installed. It will get you some error by flashing magisk if you already tried another root methode. Like, if you tried your first or third opinion you have to flash your Stock Firmeware again (i did this in the fastboot with the extractet Update.app (Firmeware) from Huawei. The Boot.img, Recovery.img and System.img (also the Cust.img) is in the Update.app.) To extract the Update.app you can use HuaweiUpdateExtractor from worstenbrood.
https://forum.xda-developers.com/showthread.php?t=2433454
After all i tried xposed Framework on my systemless rooted P10, which was working fine.
The "Hide Root" Methode is also nice to have.
4. fRomFuture
I didnt try that on my own. But there is a requierment that you have prerootet with Magisk.
So in my opinion you should give a try at Number 2 (Magisk).
But its up to you. If you try 1 or 3 Possibility give me a Feedback in this thread
Kind regards

@ChipCollector
Wow, it's really lucky (for me) that you tried all these methods!
Thank you so much for sharing your experience. Isn't it weird that there are web pages out there saying the SuperSU method is the best, when in fact you and others have a completely different experience?
Alright then, based on your comments, I will probably try Magisk.
So far I have only unlocked, not rooted, so starting from a "fresh system".
Just so I am 100% sure I understand what Magisk does:
1. This is not a whole replacement ROM, right?
I am just trying to get root -- for the time being I still want to use the standard camera program for example as I would like to get to know the phone.
2. With Magisk, can you still get Huawei updates, or is that a problem?
Of course I'll go study the Magisk thread, but if you have any thoughts on those, I'd love to hear them.
Thanks, man! :good:

TRY
https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258
6a or 6b version 100% working!
but still the data partition remains encrypted.
The developer of Twrp describes this error precisely so that it does not work, they are looking for a solution.
It only works if the kernel is turned off by forced encryption and reformatted the whole data partition.

Update:
Tried Magisk v. 14
Device bricked immediately.
Now following unbricking steps from this thread.
Question: for my build number (VTR-L09C432B171) several firmwares are found (see screenshot). How do I know what to choose (OTA-MF / FullOTA-MF?) On that screenshot, where do I click to download a firmware?
Thanks in advance.
{
"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"
}
Update: these are three files I can download, looking like the latest on the screenshot (VTR-L09C432B201, FULLOTA-MF)
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1901/g1604/v102599/f2/full/update.zip
http://update.hicloud.com:8180/TDS/...99/f2/full/public/update_data_full_public.zip
http://update.hicloud.com:8180/TDS/...l/VTR-L09_hw_eu/update_full_VTR-L09_hw_eu.zip
Any thoughts on which is more appropriate?

I should add that I did a full backup with TWRP before bricking by installing Magisk 14.
But I am not managing to load TWRP to restore that backup. What I am trying: Press Power, when it vibrates press Volume Up and hold, quickly release power, keep holding Volume Up.
The phone boots into Huawei Recovery, with "Download latest version and recovery" the only meaningful option, and it sees my WIFI connection, but it keeps failing to download.

Update:
- Finally got TWRP to run.
- Restored the backup
- Phone is booting
- After that, tried to run TWRP again to try to install Magisk 12
NotificationsOff and other apps are saying Root Not Available, so I'm not sure what's going on. But at least the phone is booting.

Finally Working
Finally Working!!!
The steps:
- Restored the TWRP backup
- Installed Magisk 12 via TWRP
- Installed Magisk Manager via APK
- Within Magisk Manager, following this advice, checked the two boxes, selected Update, selected Direct (recommended), which updated to Magisk 14. Within SafetyNet Check, both come back Green.
Absolutely stoked. :good:
Huge thanks to everyone who puts these wonderful resources together.

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?

[GSI] [Android 13] Nord N10 GSI flasher. EU and Global.

First of all I'm not a developer. I`m not skilled enough to compile stuff myself.
I'm only using available stuff and write some basic scripts.
About
This is a simple script that will automatically delete the "Product" partition, resize the "System" partition to its maximum size, and flash the GSI image onto the device.
Make sure that your OnePlus runs latest (11.0.10) firmware. Tested on my personal device - EU variant. Global variant untested. Using at your own risk.
How to? Instrucions are available in zip file
Download
EU : https://mega.nz/file/7QxX3CJS#3eEyW61h9GAqubtgB8vtrF9c258Um9Iezb-uayBePSY
GLOBAL : https://mega.nz/file/2JBSgSID#9QR6I2nc5mJ0IVhoFtMwRZj3Eu4RbsuGOx59a5FFCI4
GSI LIST : https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
SafetyNet-Fix (Magisk Module) : https://github.com/kdrag0n/safetynet-fix/releases
Since it's GSI, bugs are expected. I only recommend this for testing ROMs features/customizability. If you want stable ROM for now you need to stay on stock. Just wait for more expirienced dev to port LineageOS to our awasome device.​

18.02.2023 :
-EU variant updated to 11.0.10, global still 11.0.8
-Added LineageOS recovery maded by kronflux
15.011.2022 :
-Files updated to 11.0.8 version.
05.09.2022 :
-Misc script improvments.
16.08.2022 :
-Files updated to 11.0.7 version.
-Added stock "boot.img" for those who don't wanna root.
27.07.2022 :
-Initial relesae.

Will this work for the BE86AA version?

How's it working out for you op?

Has anyone got fingerprint work in GSI? When I tried it last time, it worked only to unlock the device. It didn't work on any apps that uses biometric. Will you update script to 11.0.7?

Anyone have tested GSI rom ?

msi68 said:
Has anyone got fingerprint work in GSI? When I tried it last time, it worked only to unlock the device. It didn't work on any apps that uses biometric. Will you update script to 11.0.7?
Click to expand...
Click to collapse
Gonna update when the links for 11.0.7 OTA will be available.

Virgoraheel said:
Anyone have tested GSI rom ?
Click to expand...
Click to collapse
I use this as my daily: https://sourceforge.net/projects/gsi-projects/files/v415/ArrowOS-12.1/
I picked this one: ArrowOS-12.1-arm64_bgN-vndklite-Unofficial.img.xz
Tried LineageOS both 18 and 19 and it can't boot with magisk installed.
ArrowOS booting and passing safetynet. The only bug i found is bluetooth audio. The rest works just fine.

adi_adi said:
I use this as my daily: https://sourceforge.net/projects/gsi-projects/files/v415/ArrowOS-12.1/
I picked this one: ArrowOS-12.1-arm64_bgN-vndklite-Unofficial.img.xz
Tried LineageOS both 18 and 19 and it can't boot with magisk installed.
ArrowOS booting and passing safetynet. The only bug i found is bluetooth audio. The rest works just fine.
Click to expand...
Click to collapse
How's battery timing with arrows os and with Gapps

Bluetooth audio not working?

msi68 said:
Has anyone got fingerprint work in GSI? When I tried it last time, it worked only to unlock the device. It didn't work on any apps that uses biometric. Will you update script to 11.0.7?
Click to expand...
Click to collapse
Updated!

Anyone else besides OP attempted this with the US/GLOBAL variant of this phone? I tried this two days ago, soft bricked my phone and the last error I got was something about the partition being too small and eventually lead me to "qualcomm crash dump mode" but I thankfully got my device back up and running with the MSM tools provided by another XDA member, despite the issues I've encountered I'm still excited to try a GSI with this device eventually lol.

it's not working on my BE86AA (global)
how can i make it run?, im really tired of stock rom
{
"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"
}

fersabi said:
it's not working on my BE86AA (global)
how can i make it run?, im really tired of stock rom
View attachment 5702009
Click to expand...
Click to collapse
Make sure you have installed latest ADB and fastboot.
Edit: If you expirienced error like this you probably booted to bootloader mode. You need to reboot your device to fastboot mdoe.

Any theories on getting this working on the BE2028?. Im rooted on the pixel rom? As my previous post mentions the script didn't work for this device. I'm interested in getting at least android 12 on this device any help would be greatly appreciated. I'm aware of the risks!
I figured out a safer way to test them thanks though.

Hello,
Trying to flash same arrow rom as OP and following the instructions step by step, but I can't get to fastbootd. Regular fastboot works fine as i unlocked the bootloader. Tried fastboot reboot fastboot, but it reboots to a menu with a choice of languages, navigation works only through volume, power buttons. Any advice?
Thanks

Hematogenas said:
Hello,
Trying to flash same arrow rom as OP and following the instructions step by step, but I can't get to fastbootd. Regular fastboot works fine as i unlocked the bootloader. Tried fastboot reboot fastboot, but it reboots to a menu with a choice of languages, navigation works only through volume, power buttons. Any advice?
Thanks
Click to expand...
Click to collapse
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com

user76543210 said:
but I can't get to fastbootd
Click to expand...
Click to collapse
AFAIK Fastbootd was a thing in later versions of android which allowed certain partitions to be resized dynamically (e.g. with OTA updates). While Google I believe supported it in A10, other manufacturers may not have implemented it until later versions. I've never seen it on the Nord N10, but I stopped using this phone for a while.
Thus... you likely have only the OnePlus recovery and fastboot partitions - not the ones that OP had for whatever was running prior to flashing Arrow (Maybe a later OOS version, or another ROM? Sorry, too lazy to read the whole thread).
As long as you end up with the right partitions in the end, what you used to load them doesn't matter. While I haven't tried a GSI on the N10, IIRC they don't use a lot of the partitions that OnePlus ships with and you are probably fine. What happens if you just flash through the old-school fastboot?
(Also... you understand the whole A/B thing, right? This is the root of like 80% of flashes that go south).

Hematogenas said:
Hello,
Trying to flash same arrow rom as OP and following the instructions step by step, but I can't get to fastbootd. Regular fastboot works fine as i unlocked the bootloader. Tried fastboot reboot fastboot, but it reboots to a menu with a choice of languages, navigation works only through volume, power buttons. Any advice?
Thanks
Click to expand...
Click to collapse
This is fastbootd. When you are in this menu run "fastboot devices" command to confirm that. I belive that OnePlus integrated somehow recovery and fastbootd because the menu are almost identical in both. But in recovery or bootloader you can't use my script it will only work in fastbootd mode.

Is there any chance of you making a version for the US BE2026 variant?