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.

[GUIDE] Unbrick Huawei P8 Lite 2017 PRA-LX1 No Brand

Hi folks
When I get back the device from Huawei services, I receive a boot.img without encryption that let me able to backup and restore the firmware hundred times without errors .
In this tutorial I'll show you how to do that without need to bring the phone to Huawei services to reset the software, starting from now can be done as well.
Requirements:
Unlocked bootloader, you know how to do that.
My own TWRP, that authorized Huawei store told should use my own TWRP to restore the phone, so get it from here by downloading the latest version.
Stock firmware, click here to download it, it's for single sim only.
Stock IMGS that needed for decrypt and to re-enable the encryption once firmware has been done with restoration, click here to download them.
7 zip to unpack the tar.gz.
Code:
[CENTER][COLOR="Red"][SIZE="4"][FONT="Comic Sans MS"]Please read the steps carefully because I'm not going to repeat them for each user, thanks[/FONT][/SIZE][/COLOR][/CENTER]
Reset Steps:
Download the C432B161.
Unpack the .tar.gz archive with 7 zip.
{
"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"
}
Rename from C432B161 to TWRP.
Copy to the Internal Storage.
Reboot to TWRP Recovery by the following command.
in the IMGS archive you will find a bootimage called boot.img, rename it to boot.emmc.win and copy to TWRP->BACKUPS->57UDU17709001769->2017-10-18--12-03-00_NRD90M_test-keys -> replace it and then follow the video
Go to the TWRP.
Wipe everything except the external_sd (the path where you copy the backup)
Tab on Restore.
Choose the copied backup make sure to rename from C432B161 to TWRP to match.
Select all partitions.
Swipe the screen and wait until finish.
Reboot to bootloader once done.
In the IMGS.tar.gz there is a file caller boot.img flash via fastboot as boot and will get booted like charm
Warning:
You are not allowed to copy or steal the files of my guide without ask my permissions.
Because I take almost week to upload the firmware after many times of failing upload.
Mention this guide for who looking helps to restore this device.
If I saw any piece of my contents in other threads, I'll report as abuse and ask a moderator to close his thread because I already saw someone rename my recovery and put it inside his thread without asking permission. that's all.
This guide could be helpful for who want to debrand his device, so we need tester.
to enable dual sim: you must flash an oeminfo partition from dual sim firmware.
Happy restoring.

Can I change from dualsim to monosim with this guide?

Wire1122 said:
Can I change from dualsim to monosim with this guide?
Click to expand...
Click to collapse
to be honest, I can't confirm since is the full backup from my single device.
in case dual sim still appear even after restore, you have to flash the single sim oeminfo partition.

when I must flash oeminfo?

Wire1122 said:
when I must flash oeminfo?
Click to expand...
Click to collapse
post firmware restoring

Wire1122 said:
when I must flash oeminfo?
Click to expand...
Click to collapse
not works to me. Pralx1c432b182 such before restoring

Wire112233 said:
not works to me. Pralx1c432b182 such before restoring
Click to expand...
Click to collapse
whats not work restoring firmware or converting from dual to single?

haky 86 said:
whats not work restoring firmware or converting from dual to single?
Click to expand...
Click to collapse
converting from dual to single. But after restoring the fw remains b182, not 161

Wire112233 said:
converting from dual to single. But after restoring the fw remains b182, not 161
Click to expand...
Click to collapse
yup because some partitions is upgraded to b182 (dual sim), same thing happen to me b181 (single sim). for converting to single sim, I'll upload the oeminfo partition soon.
Note: this operation might will lock bootloader/frp automatically, so I recommend to check them via fastboot mod.

When oeminfo?
Sent from my HUAWEI PRA-LX1 using XDA Labs

Looks like the images gone bad, and now point:
Wipe the following partitions like in the screenshot.
Click to expand...
Click to collapse
can be quite challenging
Wiped cache/data/system and restored everything that I was allowed to from your backup.
Meanwhile I changed name of directory: TWRP\BACKUPS\57UDU17709001769\2017-10-18--12-03-00_NRD90M_test-keys to
TWRP\BACKUPS\9DC7N17A17006059\2017-10-18--12-03-00_NRD90M_test-keys in order to make the backup visible in TWRP Restore menu.
(Hope that didn't change anything?)
Then I completed your "Reset Steps" tutorial, reboot and [...]
that hilarious green screen is still in place of previous Huawei:
After initial configuration my first impression was that I downloaded wrong backup, cause it looks more like the Elite ROM V6 (5 icons at bottom-screen menu, google searchbar, additional options (4 rows instead of 2) in upper-scroll menu and the pinkish-purple wallpaper) even the blinking NFC problem I had with that ROM is present there, but yet it's not that one. All informations in settings>about phone are from your backup, I even checked if the Android Studio will find my phone - and it did! That was unavaible in HassanMirza01's ROM.
So there's my question - does it suppose to look that way? Or I just messed something really hard and the visual theme files from previous OS's stayed somehow on my phone?
Don't take me wrong - after this tutorial I ended up with fully functional, nice looking (as soon as I change the pinkish wallpaper...) smartphone, so I'm really happy thanks to you!
Anyway I found it also interesting how the GreenScreen could ended up in such a place, so I'll try to figure that out.

Sixter said:
Looks like the images gone bad, and now point:
can be quite challenging
Wiped cache/data/system and restored everything that I was allowed to from your backup.
Meanwhile I changed name of directory: TWRP\BACKUPS\57UDU17709001769\2017-10-18--12-03-00_NRD90M_test-keys to
TWRP\BACKUPS\9DC7N17A17006059\2017-10-18--12-03-00_NRD90M_test-keys in order to make the backup visible in TWRP Restore menu.
(Hope that didn't change anything?)
Then I completed your "Reset Steps" tutorial, reboot and [...]
that hilarious green screen is still in place of previous Huawei:
After initial configuration my first impression was that I downloaded wrong backup, cause it looks more like the Elite ROM V6 (5 icons at bottom-screen menu, google searchbar, additional options (4 rows instead of 2) in upper-scroll menu and the pinkish-purple wallpaper) even the blinking NFC problem I had with that ROM is present there, but yet it's not that one. All informations in settings>about phone are from your backup, I even checked if the Android Studio will find my phone - and it did! That was unavaible in HassanMirza01's ROM.
So there's my question - does it suppose to look that way? Or I just messed something really hard and the visual theme files from previous OS's stayed somehow on my phone?
Don't take me wrong - after this tutorial I ended up with fully functional, nice looking (as soon as I change the pinkish wallpaper...) smartphone, so I'm really happy thanks to you!
Anyway I found it also interesting how the GreenScreen could ended up in such a place, so I'll try to figure that out.
Click to expand...
Click to collapse
might the elite rom v6 cause that issue, try to restore it again perhaps it will gone..I didn't get that green and red screen

Hey, any have oeminfo for single sim fw? its impossible to find

http://www.mediafire.com/file/0tnrmliuudsz9qo/OemInfo_EU_SS.zip
https://mega.nz/#F!0xcUWCBZ!FAXGLF3WC_uFsc5r--BqEQ

Wire1122 said:
http://www.mediafire.com/file/0tnrmliuudsz9qo/OemInfo_EU_SS.zip
https://mega.nz/#F!0xcUWCBZ!FAXGLF3WC_uFsc5r--BqEQ
Click to expand...
Click to collapse
Thanks for the help! For what version is this oem? (b161?)

dannyzamora said:
Thanks for the help! For what version is this oem? (b161?)
Click to expand...
Click to collapse
I don't know Sorry It is monosim c432

Wire1122 said:
I don't know Sorry It is monosim c432
Click to expand...
Click to collapse
Thx! One question... I have now installed b182, can i "downgrade" installing the b161 twrp backup with the tutorial and later install this oem?
Enviado desde mi PRA-LX1 mediante Tapatalk

dannyzamora said:
Thx! One question... I have now installed b182, can i "downgrade" installing the b161 twrp backup with the tutorial and later install this oem?
Enviado desde mi PRA-LX1 mediante Tapatalk
Click to expand...
Click to collapse
even if downgraded will keep on b182 because some partitions will not downgraded since my twrp is designed to backup/restore only necessary partitions for fully worked firmware.

I also had to rename TWRP\BACKUPS\57UDU17709001769\2017-10-18--12-03-00_NRD90M_test-keys to
TWRP\BACKUPS\<my device ID visible in adb devices>\2017-10-18--12-03-00_NRD90M_test-keys in order to make the backup visible in TWRP Restore menu, thanks @Sixter. Please update the first page accordingly.
But even doing so, when coming to Huawei eRecovery I'm still stuck with "Getting package info failed" issue, I cannot get back EMUI yet. Any hint?

bagage said:
I also had to rename TWRP\BACKUPS\57UDU17709001769\2017-10-18--12-03-00_NRD90M_test-keys to
TWRP\BACKUPS\<my device ID visible in adb devices>\2017-10-18--12-03-00_NRD90M_test-keys in order to make the backup visible in TWRP Restore menu, thanks @Sixter. Please update the first page accordingly.
But even doing so, when coming to Huawei eRecovery I'm still stuck with "Getting package info failed" issue, I cannot get back EMUI yet. Any hint?
Click to expand...
Click to collapse
You might want to try the Recovery MITM approach but its a tad more complicated. https://forum.xda-developers.com/p8lite/p8-lite-2017-discussion/guide-local-recovery-server-t3714900

[GUIDE] How to install early Android Pie build on Nokia 5

UPDATE: ND1-612E released. If you have already installed ND1-612D or 558K, you can download it from https://androidfilehost.com/?w=files&flid=287909 and install it manually by dialing *#*#874#*#*.
I strongly recommend you to unlock the bootloader before proceed - I won't tell how to unlock the bootloader in this guide.
Take a look to this video first if you want to know the experience of Android Pie: https://youtu.be/ay6CeonzoD8
Click to expand...
Click to collapse
In this guide, I'll provide two different methods to get Android Pie on your Nokia 5.
Both methods will erase your userdata.
I only tested it on TA-1024, but it should also work on TA-1053.
Here's an important hint: Nokia 5 (ND1) and Nokia 6 (D1C or PLE) can flash each other's stock firmware, including TA-1000 Chinese firmware.
So the TWRP ported for Nokia 6 can be also used on Nokia 5.
If you want to experience fully customized Android Pie (CN) on your Nokia 5, read this guide:
https://forum.xda-developers.com/nokia-6/how-to/guide-how-to-install-android-pie-build-t3879899/
To confirm your current firmware revision, please dial *#*#227#*#*.
If you're running ND1-558*-0-00WW-B01, you can use both methods.
If you're running ND1-560*-0-00WW-B01 or ND1-563*-0-00WW-B01, you can only use method 1.
Click to expand...
Click to collapse
Method 1: Use OST LA to flash my homebrew firmware
You should be familiar with this method.
1. Download "ND1-612C-0-00WW-B01.7z" from following site:
Or, you can also download ND1-558K-0-00WW-B01.7z instead then perform method 2.
Click to expand...
Click to collapse
https://androidfilehost.com/?w=files&flid=287885
https://fih-firmware.hikaricalyx.com/index_en.html
2. If you have Android 8.x running with LOCKED bootloader, please downgrade bootloader back before processing. If you have unlocked bootloader, you needn't to downgrade the bootloader.
3. Open OST LA or NOST and load the mlf file, in download options, only choose "Normal Download" and "Erase userdata".
If your phone boots suddenly when flashing splash, close OST LA and force power off your phone then flash again.
You can download NOST from https://github.com/StollD/NOST
4. All done, enjoy Android Pie.
Method 2: OTA Update from ND1-558J or ND1-558K
1. Download packages from here:
https://androidfilehost.com/?w=files&flid=287909
https://tpedutw-my.sharepoint.com/:...1BsF1FoPk--uIBfiMbYurDs7NCwOHd05fanA?e=MToYsb
2. Place both packages to root directory of internal storage.
5. Dial *#*#874#*#* to update.
6. After update installed, it will tell you "Encryption failed", click "Factory Reset".
If your phone encountered boot loop, you can enter recovery to perform factory reset manually.
Here's how:
1. Press and hold both volume keys and power key.
2. When you see "shutdown device:" on the left up corner of the screen, release these keys.
3. Connect your phone to a charger.
4. When you see a charging animation, press and hold volume up key and power key.
5. When you feel the phone vibrates, release the power key but only hold the volume up key.
6. When you see Android Robot lying and "No command", press the volume up key with power key holding to get the recovery menu.
7. I needn't to mention what to do next.
Click to expand...
Click to collapse
7. Enjoy Android Pie.
FAQ:
Q1: Can I root it?
A1: Yes, but you must have unlocked bootloader, and Magisk 18 seems unusable.
Q2: How to downgrade bootloader in case I want to roll back without unlocked bootloader?
A2: Rename existing Android 7.x or 8.x OTA package for your model to ND1-9999-0-00WW-B09-update.zip. Then you should know what to do next.
Q3: When will you unlock Nokia X7 / Nokia 8.1?
A3: I don't know!
Q4: When will you get Nokia 9 Penta Camera Phone?
A4: I don't know, don't ask.

How to use method 2 if unlocked bootloader and updated to December security patch
---------- Post added at 04:14 PM ---------- Previous post was at 04:13 PM ----------
And which file download for india android pie

I can watch your video!

Jitender Baloda said:
How to use method 2 if unlocked bootloader and updated to December security patch
---------- Post added at 04:14 PM ---------- Previous post was at 04:13 PM ----------
And which file download for india android pie
Click to expand...
Click to collapse
You still need to check if you're running ND1-558J. If yes, download both packages and follow the guide.
You'll need to update twice.

How to check which version is running on my phone

Here's an important hint: Nokia 5 (ND1) and Nokia 6 (D1C or PLE) can flash each other's stock firmware, including TA-1000 Chinese firmware.
So the TWRP ported for Nokia 6 can be also used on Nokia 5.
Click to expand...
Click to collapse
Anything else, guy? except stock firmware, please!

Installed on TA-1053
{
"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"
}

Good evening, to use method 2, is it also necessary to have the bootloader unlocked?

Hiiii Sir I am not able to boot into twrp recovery give me solution
Bootloader is unlocked

Jitender Baloda said:
Hiiii Sir I am not able to boot into twrp recovery give me solution
Bootloader is unlocked
Click to expand...
Click to collapse
Flash TWRP-3.2.3-0-PLE.img to recovery partition, then power off the phone:
Code:
.\fastboot oem HALT
Pull the USB cable, connect your phone to a charger. When you see the charging animation, press and hold volume up and power key.

two things in a single post
noe zapata said:
Good evening, to use method 2, is it also necessary to have the bootloader unlocked?
Click to expand...
Click to collapse
(my device is TA-1027, and my version was ND1-558J-0-00WW-B01 before the process)
it is not necessary to unlock the bootloader of the device, in my case (I do not know if it was just good luck) but do not need to restore the phone to the factory state (keep my complete info, even some banking applications that are more delicate than usual with the updates)
-----
Installed on a TA-1027, method 2
No problems encountered after 3 hours of testing.

Does the temporary bootloader unlock method suffice for said unlocked bootloader requirements?
I can't get NOST working as it says i have to be in critical bootloader state(?)
When doing OTA update method, it says file not found

+1

One question
Would I be able to further update my phone by OTA updates or not

the link is broken
the link to download the file from nd1-558j can not be access

Looks like a great tutorial. Too bad that official version is just around the corner. On the other hand.. Are there any plans to make NOST linux-friendly? Not talking about wine.

Benderisas said:
Looks like a great tutorial. Too bad that official version is just around the corner. On the other hand.. Are there any plans to make NOST linux-friendly? Not talking about wine.
Click to expand...
Click to collapse
Yeah official update will roll out January 2019

Question, is adoptable storage feature still present in this pie build?

Respected which file is to download to upgrade Nokia 5 T-1053 to android pie

wick00750 said:
Respected which file is to download to upgrade Nokia 5 T-1053 to android pie
Click to expand...
Click to collapse
Check using *#*#227#*#* then you'll se which version you're using the files doesn't matter but the method does

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.