Database Users

Android Pay Compatibility?

Hi,
Wondering if anyone has succeeded in using Android Pay on their Mi Note 2?
I have the bootloader unlocked on mine and while I've had a play with Magisk and such, unsurprisingly since the bootloader is unlocked I'm not getting anywhere.
I'm aware there are kernel hacks that can return support to unlocked devices but I'm having a hard time telling if I'd require the full kernel source in order to implement them or if there are any other ways around this or if it is simply to MIUI being an unsupported ROM. I have heard that running stock MIUI with a an originally locked bootloader still fails SafetyNet and is incompatible. With the difficulties Xiaomi place on unlocking/relocking the bootloader etc
I was hoping someone who is still running stock would be able to verify it works on a stock device
If you could also post a screenshot of the ROM you're using that would be great. With so many devices shipping with vendor ROMs rather than the official it only complicates things further.
I'm happy to keep trying and post a tutorial for others if I can get it working but frankly at this stage if the issue is MIUI itself rather than the state of the bootlock then I'd rather not waste any more hours on this.
Cheers,
StoneTrap

Can confirm Android Pay works - I am using a rom provided by Hong Kong Goldway. I haven't rooted yet but I will see if it works afterwards.

thedeejay said:
Can confirm Android Pay works - I am using MIUI Global Stable 8.0.9.0.0. I haven't rooted yet but I will see if it works afterwards.
Click to expand...
Click to collapse
That's great to know.
I'm guessing your bootloader is still locked if you're unrooted. I'm fairly sure that's the only thing left tripping safetynet. AFAIK there's no bypass until we can build our own kernel but I'd love for someone to porve me wrong.

Did you try to lock bootloader again?
I think the Magisk trick is for hiding root, not unlocked bootloader.

terstor said:
Did you try to lock bootloader again?
I think the Magisk trick is for hiding root, not unlocked bootloader.
Click to expand...
Click to collapse
Thanks for the reply.
Like I said, I realise the issue is the unlocked bootloader. I know what Magisk is for
What I was asking is if a full kernel source is needed to build a hacked kernel that supports an unlocked bootloader meeting SafetyNet or if there are is any way of patching or rebuilding a pre-existing one?
There are already compatibility issues with some MIUI versions and Android Pay even with a locked bootloader. Rather than testing every rom myself I was wondering if anyone here had any experience with it working on a certain rom.

I know that you know
I'm just curious if android pay will work again if you lock bootloader again for example using 'fastboot oem lock'.
If someone is unlocking bootloader to install custom recovery only, it would be good idea to unlock -> install recovery -> lock -> install android Pay.
But does anyone know if this will work? Is this fastboot "lock" differs from the original "lock"?

terstor said:
I know that you know
I'm just curious if android pay will work again if you lock bootloader again for example using 'fastboot oem lock'.
If someone is unlocking bootloader to install custom recovery only, it would be good idea to unlock -> install recovery -> lock -> install android Pay.
But does anyone know if this will work? Is this fastboot "lock" differs from the original "lock"?
Click to expand...
Click to collapse
Ah sorry it's hard to tell sometimes when people are making posts just to hit that first 5 posts for access. If there was a signed recovery file, Magisk would be perfect for all sorts of hi-jinx (Like for example on the ZTE Axon 7)
Unfortunately because of the way xiaomi controls unlocking the bootloader there is no way to have a custom recovery and a locked bootloader. The recovery would have to be signed by xiaomi in order to boot it.
Signing system components isn't something I know much about, all we seem to have access to is the firehose in the fastboot images but even then with the way xiaomi have locked down fastboot it seems to require some kind of authorisation first.
I was able to flash the custom recovery with a locked bootloader by modifying a fastboot image before flashing and reclocking. This just forces the phone into EDL mode when trying to boot into recovery. The system itself continues to work and will quickly overwrite the unsigned recovery with the MIUI one if an attempt to boot into recovery doesn't happen.
The locks are all the same, this can be checked with
Code:
fastboot oem device-status
on locked and unlocked phones.

Ok, so if I understood correctly, custom recovery will stop working when i will lock the bootloader.
Sorry for the little offtop, but i have another question connected with this issue. And i can't verify it by myself because i'm still waiting for unlock approval. What will happen in this scenerio:
stock rom *stable* (not dev) -> unlock bootloader -> install custom recovery -> flash eg. SuperSu.zip (to get root) via recovery -> instal magisk/xposed -> lock bootloader.
3 questions:
1. Will root 'survive' after locking or not?
2. Will xposed/magisk survive and works correctly or not?
3. OTA updates will be available or not?

I can confirm locking the boot loader and flashing original firmware global works with Android pay
Sent from my Mi Note 2 using Tapatalk

I am able to get Xiaomi Mi Note 2 and Android Pay working WITH Magisk and unlocked bootloader.
1. Install Magisk
2. Install this patch
There are some issues with files unmounting correctly. I had to manually stop and start magisk hide to get this working.
But right now, I have Android Pay confirmed working, with an unlocked phone.

thedeejay said:
I am able to get Xiaomi Mi Note 2 and Android Pay working WITH Magisk and unlocked bootloader.
1. Install Magisk
2. Install this patch
There are some issues with files unmounting correctly. I had to manually stop and start magisk hide to get this working.
But right now, I have Android Pay confirmed working, with an unlocked phone.
Click to expand...
Click to collapse
Sorry, I have one more question. Which root did you use? (SuperSU, MagiskSU, or ?)

Felixweaster said:
Sorry, I have one more question. Which root did you use? (SuperSU, MagiskSU, or ?)
Click to expand...
Click to collapse
MagiskSU

thedeejay said:
MagiskSU
Click to expand...
Click to collapse
Sorry, which ROM do you install in phone?
I installed the modified MIUI 8 China Developer ROM 7.5.6 without root in my phone.
After flash Magisk V.12 in twrp 3.0.2.0, the Magisk do nothing in my phone.

Felixweaster said:
Sorry, which ROM do you install in phone?
I installed the modified MIUI 8 China Developer ROM 7.5.6 without root in my phone.
After flash Magisk V.12 in twrp 3.0.2.0, the Magisk do nothing in my phone.
Click to expand...
Click to collapse
I am using MIUI Global Stable 8.2.5. However, with the patch (which I think you haven't installed), it shouldn't matter which ROM you are using - China or Global, Stable or Dev. What the patch does is mainly changes the build.prop to a recognised device version and a few other things on the back end to hide being unlocked.

thedeejay said:
I am using MIUI Global Stable 8.2.5. However, with the patch (which I think you haven't installed), it shouldn't matter which ROM you are using - China or Global, Stable or Dev. What the patch does is mainly changes the build.prop to a recognised device version and a few other things on the back end to hide being unlocked.
Click to expand...
Click to collapse
My problem is nothing working after flash Magisk only or with patch!! Q___Q!
I will test and discuss with other people and developer on Sunday with new ROM.
Thank you very much.

Felixweaster said:
My problem is nothing working after flash Magisk only or with patch!! Q___Q!
I will test and discuss with other people and developer on Sunday with new ROM.
Thank you very much.
Click to expand...
Click to collapse
Can you send a copy of your Magisk log? Go to Magisk -> Log and click on Magisk.
I have a feeling that the issue may be that Magisk might not be unmounting correctly. There is quite a bit of a discussion on this (as well as even MORE patches to get this to work)
(and to make sure, you also don't have xposed?)

thedeejay said:
Can you send a copy of your Magisk log? Go to Magisk -> Log and click on Magisk.
I have a feeling that the issue may be that Magisk might not be unmounting correctly. There is quite a bit of a discussion on this (as well as even MORE patches to get this to work)
(and to make sure, you also don't have xposed?)
Click to expand...
Click to collapse
You can find the log as attached.
I did NOT have xposed.

Felixweaster said:
You can find the log as attached.
I did NOT have xposed.
Click to expand...
Click to collapse
It is mounting xposed so you still have traces of it left. Go through these steps:
flash this file in TWRP: - Xposed Uninstaller
Reboot. Check if Magisk is working. If it is not, reboot back into TWRP and flash Magisk v12.0 again: Latest Magisk
Reboot. Do a few keypresses before going back into TWRP. Flash This patch here: Xiaomi safetynet fix v1.3
Reboot back into system, and check if SafetyNet is working (can be done in Magisk Manager). If it isn't, reboot into TWRP once again and flash THIS one here: Magisk v12.0 fix
(So total of 4 files that need to be flashed and cycled through).
Also make sure that you DO NOT clear cache/dalvik cache at any stage!
Give that a shot and let me know how it goes.

thedeejay said:
It is mounting xposed so you still have traces of it left. Go through these steps:
flash this file in TWRP: - Xposed Uninstaller
Reboot. Check if Magisk is working. If it is not, reboot back into TWRP and flash Magisk v12.0 again: Latest Magisk
Reboot. Do a few keypresses before going back into TWRP. Flash This patch here: Xiaomi safetynet fix v1.3
Reboot back into system, and check if SafetyNet is working (can be done in Magisk Manager). If it isn't, reboot into TWRP once again and flash THIS one here: Magisk v12.0 fix
(So total of 4 files that need to be flashed and cycled through).
Also make sure that you DO NOT clear cache/dalvik cache at any stage!
Give that a shot and let me know how it goes.
Click to expand...
Click to collapse
After flash Xposed Uninstaller & reboot => magisk nothing working
After flash Magisk v12.0 => magisk nothing working
After flash Magisk v12.0 again & Xiaomi safetynet fix v1.3 => magisk nothing working
After flash Magisk v12.0 again & Xiaomi safetynet fix v1.3 again & Magisk v12.0 fix => magisk nothing working
After flash Xiaomi official root
I get the same error log as attached.
I also attach the recovery log in attachment.
When I check the recovery log, there are something strange as below.
============
MagiskBoot (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
grep: init.rc: No such file or directory
sed: init.rc: No such file or directory
sed: init.rc: No such file or directory
Cannot open init.rc
MagiskBoot (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
Cannot find the file entry [sepolicy]
MagiskBoot (by topjohnwu) - Boot Image Modification Tool
Loading cpio: [ramdisk.cpio]
Can't open 'sepolicy': No such file or directory
Could not load policy
Cannot open sepolicy
......
......
- Flashing new boot image
I:Set overlay: ''
5745+0 records in
5745+0 records out
23531520 bytes (22.4MB) copied, 0.291553 seconds, 77.0MB/s
- Unmounting partitions
losetup: /dev/block/loop0: No such device or address
umount: can't unmount /system: Device or resource busy
- Done
I:Updater process ended with RC=0
I:Legacy property environment disabled.
I:Install took 30 second(s).
I:Install zip Success,and install cofface-no-verity by cofface.
================

1. After flash the TWRP Unofficial TWRP 3.1.0-0 Mi Note 2 (scorpio)
2. Mount the /system read-write (I'm NOT sure do it cause something wrong?)
3. flash Magisk v12.0 => magisk working, saftnet false
4. Xiaomi safetynet fix v1.3 => magisk working, saftnet false
5. flash Magisk v12.0 fix => magisk working, saftnet true (before check saftnet, I found Magisk Hide in Magisk Manager and I also selected the safetynet attest app.)
Three more question
1. When you flash Magisk, is the /system read-only ?
2. Where do you have Magisk v12.0 fix ??
3. Why do you ask to flash Xiaomi safetynet fix v1.3 not Xiaomi safetynet fix v1.6 ?
thedeejay!! Thank you very much!!

Rebranding/Root P10 Plus VKY-L09C432B175 - rooting issue with TWRP and superSU

I just rebranded my p10+ with the last firmware VKY-L09C432B175 and everything worked fine
i am having an issue trying to root it using TWRP 3.0.2-2 and superSU 2.82
issue seems to be related on the installation of superSU; next the log about the installation
*********************
Boot image patcher
*********************
- Finding boot image
--- Boot image: /boot"unreadable chars"emmc"unreadable chars"/dev/block/platform/ff3b0000.ufs/by-name/boot_a"unreadable chars"flags=display="boot";
backup=1
- Extracting ramdisk
--- Failure, aborting
.
.
.
- Unmounting /system
- Done !
Updating partition details....
... done
i am installing superSU on a SD card because i can not find the file on main memory of the phone and it seems crypted
when i rebbot the device it looks not rooted
anyone has an idea?
thanks in advance

more info
i just tried to use the system mode superSU from the following link:
https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
the installation seems to end fine but the device is not rooted

Hi,
I am facing the same issue. I have got a stock Huawei P10 Plus. I flashed TWRP 3.0.2-2. Right now I am also stuck at flashing superSU 2.82 with exactly the same problem.
I cannot read /sdcard
the log also shown some unknown chars in the boot command line
flashing superSU from a SD-Card quits after (trying to) "extracting ramdisk"
Regards,
Alex

Hello could you please share your method for rebranding?

Need Untouched Stock Boot Image XT1643 NPJS25.93-14-15

Hi ,
I am new and Beginner to Rooting and Unrooting Stuff.
Already unlocked Bootloader and Root by Flashing SU.Zip through TWRP.
Flashed Element X Kernel.
Now Wants to Switch from SuperSu to Magisk ofcourse due to Root Hide Module.
Unable to Flash ever after uninstall SuperSu and UNSu Flash.
Return below Error on Flasing magisk
-Mounting /System, /Vendor, /cache, /data
-Device platform: arm64
-Constructing environment
-/data/magisk.img detected!
-Mounting /data/magisk.img to /magisk
-Found Boot Image: /dev/block/mmclk0p34
-Unpacking boot image
-Checking ramdisk status
! Boot image patched by other programs!
! Please restore stock boot image
Updater process ended with ERROR:1
Error installing zip file '/sdcard/MagiskManager/Magisk-v13.3.zip'
Updating partition details...
...done
Even Flashing UnSu asks to Flash "Stock Boot Image"
Any help me and Share Unmodified Stock Boot Image of XT1643 NPJS25.93-14-15.
Hope it will Help.
Thanks in advance.

You can find the stock kernel here: https://drive.google.com/drive/folders/0B-GUyOfb8OgzcUl1NUtHYWNIR2M
It's listed under NPJS25_93_14_15_Feb2018_stock_kernel. Download the image in that folder and flash via TWRP Install, as an image install, to your boot partition (make sure you don't have recovery selected)
The kernel image and all the other images in that folder have been taken from their respective stock ROMs.
I'm not sure why the boot image was reported as: Found Boot Image: /dev/block/mmclk0p34 Normally, for a stock ROM boot image on G4/Plus devices, the partition is mmcblk0p28.

Thanks it's worked for me.

[email protected] said:
Thanks it's worked for me.[/Q
Please tell me the full procedure of unistalling supersu and flashing the stock img and magisk.
I am also the beginner and all the stuffs are very confusing. Please Help
I am on nougat april patch. rooted, installed xposed and phh's supersu.
Click to expand...
Click to collapse

Magisk 19.2 on 47.2.A.10.62?

Hey everyone, I flashed my G8142 yesterday with the newest firmware, I was on oreo still. I ran into a few issues, mainly that TWRP couldn't read data, but it turned out it was because I used the newest image, 3.3.1, downgrading to 3.2.3 fixed that issue. After getting TWRP fixed, I tried flashing Magisk, but no matter what I do, magisk manager says that I do not have it installed. I tried flashing it on TWRP, and I tried using XperiFIX to flash it, and it still does not work. The log below shows what happens when I run the Zip. I even tried running the uninstall then installing it again, but got the same thing. Any help is appreciated
************************
* Magisk v19.2 Installer
************************
- Mounting system
- Encrypted data, keep forceencrypt
- Target image: /dev/block/sde35
- Device platform: arm64
- Constructing environment
- Unpacking boot image
- Checking ramdisk status
- Magisk patched boot image detected
- Patching ramdisk
- Repacking boot image
- Flashing new boot image
- Unmounting partitions
- Done

To add on, I now have tried installing 18.1 and downgrading the app to 7.1, but still the same result.

There was an issue in history, if you have hide the Magisk Manager itself.
In this case: don't hide the Manager, reboot, upgrade the manager and try if it's work.

flizer said:
Hey everyone, I flashed my G8142 yesterday with the newest firmware, I was on oreo still. I ran into a few issues, mainly that TWRP couldn't read data, but it turned out it was because I used the newest image, 3.3.1, downgrading to 3.2.3 fixed that issue. After getting TWRP fixed, I tried flashing Magisk, but no matter what I do, magisk manager says that I do not have it installed. I tried flashing it on TWRP, and I tried using XperiFIX to flash it, and it still does not work. The log below shows what happens when I run the Zip. I even tried running the uninstall then installing it again, but got the same thing. Any help is appreciated
************************
* Magisk v19.2 Installer
************************
- Mounting system
- Encrypted data, keep forceencrypt
- Target image: /dev/block/sde35
- Device platform: arm64
- Constructing environment
- Unpacking boot image
- Checking ramdisk status
- Magisk patched boot image detected
- Patching ramdisk
- Repacking boot image
- Flashing new boot image
- Unmounting partitions
- Done
Click to expand...
Click to collapse
I just bought an XZ Premium and was going to unlock but have heard it messes up the camera and maybe a few other things. Did you encounter any of this? I unlocked my XA2 and it works the same as before. So just wondering, should I unlock or no?

bobsright said:
I just bought an XZ Premium and was going to unlock but have heard it messes up the camera and maybe a few other things. Did you encounter any of this? I unlocked my XA2 and it works the same as before. So just wondering, should I unlock or no?
Click to expand...
Click to collapse
there is no problem unlocking the bootloader

Yeah, I ended up doing it and everything is good except for being able to use 3rd party tethering apps like Secure Tether and CWM Tether. Can't understand why they don't work. I have an XZ2Compact, locked b/l and they work on it. Also have the XA2 as I mentioned, on Oreo, unlocked b/l, works on it. For some reason combination of Pie and unlocked b/l messes it up. Native tether and hotspot functions fine.

Can't Root Samsung SM-T380

Hello,
I was wondering if the T380 is rootable?
I tried to follow [TWRP 3.2.1-1] [ROOT] Tab A SM-T380/T385 - 10/02/2018 but it didn't work ( as I assume) since the guide is quite old. I also tried patching the boot.img using the magisk tutorial but I end up with the Installed: N\A Ramdisk: Yes A\B & Sars: no.
I can't also downgrade since I have the latest 2021 patch and the binary is 4 while the version below that is on 3. ROM STOCK
PS: I can install TWRP without any problems, the only issue is rooting with magisk
Any help or suggestion really appreciated.

This is exactly the same problem that I've been having with my T380. I've flashed the stock rom and retried many different methods of rooting with Magisk but they all have failed. If you got it workiing, please tell me what made it work for you. Thanks!
These are the steps that I took using post by Winston Churchill as a guide:
1. Enable OEM Unlock
2. Use Odin to flash TWRP with twrp_3.2.3-1_sm-t380_oo_4119.tar on AP Slot
3. TWRP Wipe/Reformat Data then reboot to recovery
4. Install boot.img patched by Magisk using TWRP (I extracted boot.img from stock firmware and used Magisk to make patched boot.img)
5. Install Magisk.zip using TWRP (this didn't do anything, I had to manually install the apk later on)
6. Install Tab_A_2017_Pie_forced+encryption_disabler.zip using TWRP
7. Wipe Cache and Dalvik
8. Reboot System
I tried alternative approach for installing Magisk using this guide. It basically is extracting boot.img off your current device firmware and using Magisk to patch that boot.img. Then flash the patched boot.img using TWRP (it didn't work for me though)
These are the places I went to get my files:
https://forum.xda-developers.com/t/rooting-sm-t380-with-pie.4049951/ (Post by Winston Churchill)
https://forum.xda-developers.com/t/guide-comprehensive-t380-tab-a-2017-8-0-root-guide.3753203/
https://forum.xda-developers.com/t/twrp-3-2-1-1-root-tab-a-sm-t380-t385-10-02-2018.3747564/

Barto604 said:
Hello,
I was wondering if the T380 is rootable?
I tried to follow [TWRP 3.2.1-1] [ROOT] Tab A SM-T380/T385 - 10/02/2018 but it didn't work ( as I assume) since the guide is quite old. I also tried patching the boot.img using the magisk tutorial but I end up with the Installed: N\A Ramdisk: Yes A\B & Sars: no.
I can't also downgrade since I have the latest 2021 patch and the binary is 4 while the version below that is on 3. ROM STOCK
PS: I can install TWRP without any problems, the only issue is rooting with magisk
Any help or suggestion really appreciated.
Click to expand...
Click to collapse
I haven't done this on the T380, but it works on other Samsung tablets. Instead of the rigamarole of patching the boot image, just flash Magisk-v21.4.zip with TWRP. It won't give you the latest version, but it installs Magisk Manager, and you can use that to update to the latest version of Magisk and Magisk Manager.

lewmur said:
I haven't done this on the T380, but it works on other Samsung tablets. Instead of the rigamarole of patching the boot image, just flash Magisk-v21.4.zip with TWRP. It won't give you the latest version, but it installs Magisk Manager, and you can use that to update to the latest version of Magisk and Magisk Manager.
Click to expand...
Click to collapse
Hi, sorry for the late reply, I already tried using earlier versions of magisk it says it patch and everything via TWRP but when I reboot magisk app is not found and when I install the APK it says Installed: N/A

Barto604 said:
Hi, sorry for the late reply, I already tried using earlier versions of magisk it says it patch and everything via TWRP but when I reboot magisk app is not found and when I install the APK it says Installed: N/A
Click to expand...
Click to collapse
Try flashing Magisk23.apk with TWRP as if it were a zip. That worked with latest 11 ROM with T500.

Tried it, didn't work either, I think them latest security patch for this tablet block root or something, I'm literally stuck.