Related
Official Oreo has finally been leaked thanks to @NFound and since I've been extensively testing it this thread will be to teach you how to install it and to tell you what works and what doesn't.
Special THANK YOU to @NFound, @raystef66, @DrakenFX, @Oki, @WesTD and to everyone else who has helped with the development of the Axon 7 and with this thread
How to unlock the bootloader?
Follow this guide https://forum.xda-developers.com/axon-7/how-to/guide-unlock-bootloader-easily-t3704595 by @WestTD
Unlocked bootloader message removal:
Have not found a working method yet.
Always backup your intSD before flashing ROMs and other TWRPs (Recoveries)
Stock user, need to install TWRP?
Flash TWRP 3.2.1-0 https://androidfilehost.com/?fid=673791459329066789 by @raystef66
If you already have TWRP installed, any version will do since the ROM will replace it with TWRP 3.2.1-6 after installation.
Installation:
Download: https://androidfilehost.com/?fid=818222786056032764 (I hope this is allowed now, please forgive me if the links is still not allowed by XDA)
Move the .ZIP into your internal memory as you would by moving any other file into your phone through USB.
Boot into TWRP: adb reboot recovery or by turning the phone off and pressing VolUp+Power
Do a full backup!
Wipe to perform a clean install. Recommended.
Press Install
Select the .ZIP
Install with TWRP only! During installation it will be asked which modem you want to install. In my case this was the A2017G but that might not be yours. Please select correctly.
Wipe Cache and Dalvik Do not reboot yet if you want to root.
Rooting Download and install Magisk V16.4 or V16.0 exactly as you just installed the ROM.
Flash the safetynet fix linked below.
Wipe Cache and Dalvik
Reboot
Edit: Changing partitions to ext4 might be necessary for some non-stock users on f2fs.. Still updating
What's not working and how to fix it:
Magisk doesn't pass Safetynet? (ctsProfile: False). Download and flash https://androidfilehost.com/?fid=674106145207489292 Thank you @raystef66
Google play store shows as uncertified? The .ZIP above from @raystef66 fixes this as well. Your device is now certified.
How do I disable force encryption? Go to post #63 by @DrakenFX
Bad battery life? Flash Jojoc V2.1 or V3.1 module within Magisk or via TWRP V3.2 : https://androidfilehost.com/?fid=962187416754476535 V2.1 : https://androidfilehost.com/?fid=673956719939820457 by @raystef66
AdAway cannot install hosts file: Open Magisk -> Settings and select Systemless hosts.
Daydream is not working? Check post #23 B12 Thread by @kountry83 Download: Daydream.zip
How do I enable or disable the Navigation bar?: Check thread [A2017G][TWRP-ZIP]NAVIGATION BAR Enabler/Disabler by @raystef66 or Direct Link download for aroma installer
How do I remove the carrier label and center the clock on the status bar? Check thread [PATCH][A2017X V1.3.0B01] Remove Carrier & Center Clock by @raystef66 Download: A2017X_V1.3.0B01_carrier&clock
Remove carrier label only: Check post #342 by @raystef66 Download: A2017X_V1.3.0B01_carrierremover
Need modems, boot or bootstack? Download below by @raystef66
Modems:
ZTE_A2017X_Oreo_V1.30B01_Gmodem
ZTE_A2017X_Oreo_V1.30B01_Umodem
ZTE_A2017X_Oreo_V1.30B01_CNmodem
Boot:
A2017X-O_beta-B01-boot
Bootstack: twrp 3.2.1.6 included
ZTE_A2017X_V1.3.0B01_OREO_BootStack_twrp3216
What's working:
Pretty much everything other than what I wrote above it seems. The ROM is very fast and stable, my phone feels considerably snappier than it did on stock Nougat and there doesn't seem to be many bugs at all. Only thing I've noticed is the battery life doesn't seem to be great but that could just be some installed apps or my phone. Fixed by Jojoc V3.2 by @raystef66. Link above.
Testing Camera...
Working HDR+ Patch by @NFound: : HDR+ for v1.3.0 B01
GCAM: GCAM
Flashed an older version of that HDR+ Patch by @NFound and does your Magisk not pass the safetynet anymore? Flash this safetynet fix by @raystef66: A2017X-V1.30B01_safetynet_fix_HDR
Dual Sims: Fully working
I'll continue updating the thread according to your feedback and my testing.
Victor13f said:
Official Oreo has finally been leaked thanks to @NFound and since I've been extensively testing it this thread will be to teach you how to install it and to tell you what works and what doesn't.
Thank you @NFound once again for your hard work!
Thank you @Oki for having written https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-custom-oreo-roms-newbies-t3786693 If you need a better guide visit this thread and follow this guide simply using different files and not installing the bootstack separately.
How to unlock the bootloader?
Follow this guide https://forum.xda-developers.com/axon-7/how-to/guide-unlock-bootloader-easily-t3704595 by @WestTD
Unlock boot message removal:
If you want to remove the unlocked bootloader message at boot, you just need TWRP Exclusive. Just boot to recovery and go to the Advanced Menu -> More -> Del Inscription. You must to do this every time you update the bootloader. Thank you @Oki
Need to install TWRP?
Flash TWRP exclusive by @NFound https://androidfilehost.com/?fid=673956719939822011
Installation:
Download: https://androidfilehost.com/?fid=818222786056032764 (I hope this is allowed now, please forgive me if the links is still not allowed by XDA)
Move the .ZIP into your internal memory as you would by moving any other file into your phone through USB.
Boot into TWRP or ADB: adb reboot recovery or by turning the phone off and pressing VolUp+Power
Press Install
Select the .ZIP
Install with TWRP only! During installation it will be asked which bootstack you want to install. In my case this was the A2017G but that might not be yours. Please select correctly.
Wipe Cache and Dalvik Do not reboot yet if you want to root.
Rooting Download and install Magisk V16.4 or V16.0 exactly as you just installed the ROM or with TWRP Exclusive go to Advanced -> More -> Root -> Magisk
Wipe Cache and Dalvik
Reboot
What's not working?:
Magisk root doesn't pass Safetynet (ctsProfile: False). Tested with V16.4, V16.0 and V15.3. None of them passes the safetyNet. Have also tried installing the props module to no avail.
Google play store shows as uncertified (yet all the apps are available and install with no restrictions).
Battery charging light turns off when I turn the screen on and turns back on when the screen is off (Maybe it's intended to be like that, not sure)
What's working:
Pretty much everything other than what I wrote above it seems. The rom is very fast and stable, my phone feels considerably snappier than it did on stock Nougat and there doesn't seem to be many bugs at all. Only thing I've noticed is the battery life doesn't seem to be great but that could just be some installed apps or my phone. I haven't tested the dualsims yet but I will soon and I'll post the result here.
Testing Camera...
I'll continue updating the thread according to your feedback and my testing.
Click to expand...
Click to collapse
Sigh. First of all. Link is not allowed, delete it before we get trouble. Furthermore your guide isn't really helping anyone, since all information can be get in the other thread (nfound announced official oreo). You just snacked away Oki's guide and inserted a different ROM link. Tbf your information about magisk is fine and new, but that's it.
Cool, an easy guide to get you started.
Thanks man.
GabbaGandalf42 said:
Sigh. First of all. Link is not allowed, delete it before we get trouble. Furthermore your guide isn't really helping anyone, since all information can be get in the other thread (nfound announced official oreo). You just snacked away Oki's guide and inserted a different ROM link. Tbf your information about magisk is fine and new, but that's it.
Click to expand...
Click to collapse
I belive the link is allowed. A Forum mod said so on NFounds AEX thread.
I didn't snatch anything. I used guides that exist because they work and I gave props to every single person I could think of. I never claimed this was all my work. Just trying to help other people who want to try the ROM or are interested in how it performs.
I think the rom has something to do with CTS because it's a beta rom. It might not CTS approved. That's why magisk won't work. Similar to Android P DP.
https://developer.android.com/preview/release-notes
However, We can try to change or add ro.build.fingerprint in the build.prop file to the valid one. Not sure that it will work or not.
For example.
Code:
ro.build.fingerprint=ZTE/P996A04_N/ailsa_ii:7.0/NRD90M/20170215.164309:user/release-keys
Can /system be mounted as RW in this rom?
blackpac said:
Can /system be mounted as RW in this rom?
Click to expand...
Click to collapse
You can edit system just from TWRP.
mickey36736 said:
I think the rom has something to do with CTS because it's a beta rom. It might not CTS approved. That's why magisk won't work. Similar to Android P DP.
https://developer.android.com/preview/release-notes
However, We can try to change or add ro.build.fingerprint in the build.prop file to the valid one. Not sure that it will work or not.
For example.
Code:
ro.build.fingerprint=ZTE/P996A04_N/ailsa_ii:7.0/NRD90M/20170215.164309:user/release-keys
Click to expand...
Click to collapse
Didn't work unfortunately. Edited the ro.build.fingerprint and it still failed safetynet check.
SAFETYNET-FIX
Here you go : https://androidfilehost.com/?fid=674106145207489292
Fixes the safetynet - tested on 16.4 and 16.0
raystef66 said:
Here you go : https://androidfilehost.com/?fid=674106145207489292
Fixes the safetynet - tested on 16.4
Click to expand...
Click to collapse
Thank you, it works
all set up and running
Predatorhaze said:
all set up and running
Click to expand...
Click to collapse
How is battery life? Did you get substratum running? How is the sound without v4a and ainur. How is the sound with v4a+ainur?
battery dont know yet,but i dont use any sound mods on stock rom.Didnt try substratum.....i can try,but not gonna use it
GabbaGandalf42 said:
How is battery life? Did you get substratum running? How is the sound without v4a and ainur. How is the sound with v4a+ainur?
Click to expand...
Click to collapse
Accubattery says 5 hours SOT but I have only actually gotten 2. Again, this is probably a problem on my side and not the ROM. I need to check over the installed apps. Overall, actually better than 7.1.1 Nougat IMO since I was getting those bad results there too (Shouldn't have restored all the apps on first start).
Soundwise you shouldn't need anything. It's an official ROM and everything works properly. I haven't tested with any mods and I personally won't.
Victor13f said:
Accubattery says 5 hours SOT but I have only actually gotten 2. Again, this is probably a problem on my side and not the ROM. I need to check over the installed apps. Overall, actually better than 7.1.1 Nougat IMO since I was getting those bad results there too (Shouldn't have restored all the apps on first start).
Soundwise you shouldn't need anything. It's an official ROM and everything works properly. I haven't tested with any mods and I personally won't.
Click to expand...
Click to collapse
Battery doesn't sound too good. And personally I won't try it out until someone checked if substratum works. Cause if substratum works, I am able to enjoy the 'swift Black's theme, which boosts battery life by having real black everywhere. That means that the amoled screen will use less power. Also it's beautiful af and I don't want to miss it
Two questions please:
1. would flashing no-verity-opt-encrypt do anything for this ROM? as in, making encryption optional?
2. would it be a good idea to flash FASTBOOT_UNLOCK_EDL_N if I want to change my recovery now that I am no longer on N?
GabbaGandalf42 said:
Battery doesn't sound too good. And personally I won't try it out until someone checked if substratum works. Cause if substratum works, I am able to enjoy the 'swift Black's theme, which boosts battery life by having real black everywhere. That means that the amoled screen will use less power. Also it's beautiful af and I don't want to miss it
Click to expand...
Click to collapse
Substratum works, used swift black theme 8.0 pixel or nexus
GabbaGandalf42 said:
Battery doesn't sound too good. And personally I won't try it out until someone checked if substratum works. Cause if substratum works, I am able to enjoy the 'swift Black's theme, which boosts battery life by having real black everywhere. That means that the amoled screen will use less power. Also it's beautiful af and I don't want to miss it
Click to expand...
Click to collapse
Batterywise, I flashed the jojoc battery module and it's looking a lot better already
Here is working fine but how do I remove the operator name from the status bar?
Battery is absolutely horrible, coming from a beta tester. If you experience terrible battery it isn't a problem on your side, it's the beta rom. At best, I get barely 3 hours of screen on time only browsing Facebook
Updated OP since this thread became useful to track if magisk works with our stock ROM.
The most recent version you can use at the moment is magisk 16.7 and magisk manager 5.8.3.
I suggest that you change the update channel to custom and set the address to 127.0.0.1
For the most recent Magisk version:
mickey36736 said:
I tested 19.3 on B01 oreo and it still bootloop.
Click to expand...
Click to collapse
Thanks for checking @mickey36736
rzarectha said:
It bootloops
Click to expand...
Click to collapse
I don't have any problems on Magisk 17.0 - safetynetpass on AEX(O), NitrogenOS(P) and PE(P) :cyclops:
Open Manager and update. Download latest stable one and flash it. Reboot.
raystef66 said:
I don't have any problems on Magisk 17.0 - safetynetpass on AEX(O), NitrogenOS(P) and PE(P) :cyclops:
Open Manager and update. Download latest stable one and flash it. Reboot.
Click to expand...
Click to collapse
mine bootlooped on stock. I'm naive enough to wait for the big update also, I got it from the beta channel. I'll try the stable and see what happens. I was assuming it's the same build
update: it bootloops on stock no matter what channel (stable/beta) you get it from.
I'll try to get a mod to help me change the OP title, I can't seem to be able to do it myself.
rzarectha said:
mine bootlooped on stock. I'm naive enough to wait for the big update also, I got it from the beta channel. I'll try the stable and see what happens. I was assuming it's the same build
update: it bootloops on stock no matter what channel (stable/beta) you get it from.
I'll try to get a mod to help me change the OP title, I can't seem to be able to do it myself.
Click to expand...
Click to collapse
You can change the OP tittle by pressing Go Advanced button next to the Save button when editing the OP post.
Not only on stock...
I am on LOS 14.1, saw the update notification, did update, and now also a bootloop...
I installed the zip of an earlier version to no avail.
Prophet 5 said:
I am on LOS 14.1, saw the update notification, did update, and now also a bootloop...
I installed the zip of an earlier version to no avail.
Click to expand...
Click to collapse
use the uninstaller zip first
Try 17.1. supposedly solves the bootloops.
bootloops are easily fixed by using the uninstaller first.
koftheworld said:
Try 17.1. supposedly solves the bootloops.
Click to expand...
Click to collapse
Nope, it doesn't. I'm on B35 and it still bootloops. Had to use the uninstaller to remove and revert to v16.7
KwesiJnr said:
Nope, it doesn't. I'm on B35 and it still bootloops. Had to use the uninstaller to remove and revert to v16.7
Click to expand...
Click to collapse
You have to use the uninstaller first and then flash 17.1.
Too late for me. I was on last years' Darkrom (LOS14.1 based, really stable, so no recent backup) and immediately got a bootloop which I'm still working to recover from... :crying:
pnin said:
Too late for me. I was on last years' Darkrom (LOS14.1 based, really stable, so no recent backup) and immediately got a bootloop which I'm still working to recover from... :crying:
Click to expand...
Click to collapse
Did you use the magisk uninstaller? If not, just reflash your bootloader
koftheworld said:
Did you use the magisk uninstaller? If not, just reflash your bootloader
Click to expand...
Click to collapse
Excuse my ignorance but how would reflashing the bootloader help. Doesn't Magisk modify the boot image?
I figure that if flashing the uninstaller and then flashing v17.1 still results in a bootloop I (personally speaking) would go into TWRP and manually remove any Magisk related directories/files, maybe flash the uninstaller again (might catch something I missed), and then dirty flash Dark ROM (fresh boot image). Flash Magisk 17.x afterward.
That said, I am a non-Magisk kind of guy (not present on any ROMs or devices) so I might not know what I'm talking about. [emoji16]
Dark ROM. FTW. [emoji41]
ZTE Axon 7 A2017U, AospExtended v4.6 ROM, LlamaSweet 0.5 Kernel, microG (NoGapps), Multiboot, XDA Legacy
marcdw said:
I (personally speaking) would go into TWRP and manually remove any Magisk related directories/files, maybe flash the uninstaller again (might catch something I missed), and then dirty flash Dark ROM (fresh boot image).
Click to expand...
Click to collapse
Care to clue me in on those directories/files? I'm having a hard time here, dirty flashing my previous ROM, getting up to setup and then have something fail catastrophically over and over again...
I have even had to restore recovery through fastboot mode now. :silly:
I did not flash Magisk 17.x on Stock B35 (stayed with v16.4), but installing the latest Magisk Manager (v5.9.1) resolved the previous SafetyNet Check errors
Using stock anything above and v17.0 will bootloop using stock,
Just my 2cents, if that your issue just do the following:
-Download v16.7 first in case you don't have it yet, and move it to the SDCard.
* Head back to TWRP
* Flash v16.7 or your preferred release.
* You're good to go.
pnin said:
Care to clue me in on those directories/files? I'm having a hard time here, dirty flashing my previous ROM, getting up to setup and then have something fail catastrophically over and over again...
I have even had to restore recovery through fastboot mode now. :silly:
Click to expand...
Click to collapse
Not sure to be honest. Last time I had Magisk was around v15.x. When I initially rooted my Moto Magisk was part of the process. Even though the stock ROM is using SuperSU it seems I didn't fully remove Magisk. I have the following remnants visible in TWRP...
/data/magisk
/data/magisk.img
and files in /data/adb/
Not sure why everything is failing so badly on your end. I can't test things on my Axon 7 since I use DualBoot Patcher where Magisk is a no go.
Moto G5S Plus XT1806, MSM-Xtended v2.5 ROM, MultiROM, XDA Legacy
So I have managed to fully restore the phone, including updating Magisk to v17.1 (v16.0 didn't work at all, v14 did).
Apart from Goggle Messages that is, which FC whenever I try to start it (both current and past versions).
I was careful with Magisk in the past, I will be even more so in the future. No dot zero releases for me from now on. Thanks for your tips, people.
pnin said:
So I have managed to fully restore the phone, including updating Magisk to v17.1 (v16.0 didn't work at all, v14 did).
Apart from Goggle Messages that is, which FC whenever I try to start it (both current and past versions).
I was careful with Magisk in the past, I will be even more so in the future. No dot zero releases for me from now on. Thanks for your tips, people.
Click to expand...
Click to collapse
I'm not currently having Magisk issues, but Google Messages, after the recent update, does the same here. Gave up on it & switched to Textra.
New beta version released. Still bootloop
Welcome.
What can I say.. My phone: LG G5 H850 International, Android 8.0 Oreo. I'm doing everything like it's written in tutorial. Bootloader is unlocked, I have no problems with flash recovery via fastboot. **** happens when I try to root my device with SuperSU. Process of install is going like it supposed but after reboot I don't see supersu app and when I verify root status - it says it's not rooted. I tried again and again and again for about sixteen times and after last try I saw one failure command line: patching sepolicy failure aborting. I rooted and mod couple of devices and never had something like this. I hope someone will help me because without root - phone is trash with many sick problems like afterimages on screen, no manual video mode and not good quality of photos etc. Greetings from Poland.
EDIT: Maybe I should try Magisk in this case?
Thread should be closed because yesterday I rooted my LG with Magisk without any problems. Recovery is working, root too.
Yeah!
majhau said:
Thread should be closed because yesterday I rooted my LG with Magisk without any problems. Recovery is working, root too.
Yeah!
Click to expand...
Click to collapse
Okay, what was your solution?
Dear All , this method maybe already here somewhere ,
i have tried to root this specific device and i ran into many issues !
but successfully i have done it .
i'll upload the patched file here and i'll mention what method i have done ! ..
unlock boot loader is a must . ( Please read about it in google , All Samsung devices is the same method )
u might repeat the process to times until it successfully unlocked and greyed-out !
Next download this firmware only to be able to run the patched AP .
un-tick Auto-reboot before flashing .
once flash done , power + Volume down to restart , then volume up with power until u boot into the recovery
wipe data . restart . done
to make sure u have done every thing correctly u'll see RED massage once u boot you're device
Firmware ( This is UAE Firmware " T725XXS1ATC5_T725OJM1ASJ3_XSG " ) All Languages included . Link
Patched AP File Link
Please Note that i'm not responsible if u break your Tablet ! .
Proof ( IMG )
GD day :angel:
after rooting is it possible to update firmware to a new one?
moresat said:
after rooting is it possible to update firmware to a new one?
Click to expand...
Click to collapse
No ! ..
Hi
Do I just need to use odin to flash the Firmware you mentioned then use ODIN again to flash the patched ap
I can just add that with this specific fw version and patched ap everything worked on LTE version but I might add my little deviations ...
1st original firmware flash (BL,AP,CP,CSC-non-home one) instantly followed by wipe data in recovery mode.
2nd After the initial setup + wifi connection I installed and updated magisk.
3rd "adb restart bootloader" (here i am not sure if it mattered but anyway) and flush again with the provided Patched AP File (BL,the_patched_AP,CSC - the home one this time ... using CP failed with modem err with me so I just skipped it here)
4th get trough the init setup again with wifi on and open magisk which will install more stuff.
The prerequisites still apply oem unlocked bootloader before you start and keep your battery at least 60-70% since the process drained mine a lot.
You know you are on the right track when you have warning with tablet bootloader is unlocked (at startup yellow) and tablet not running Samsung's official software (red after the first one)
Ive just bought this SM-T725 model android 11. There is no sign of OEM Unlock Bootloader under development. Does anyone know how I can unlock this.
chadandchew said:
Ive just bought this SM-T725 model android 11. There is no sign of OEM Unlock Bootloader under development. Does anyone know how I can unlock this.
Click to expand...
Click to collapse
The option only shows up when you are connected to the internet.
Thanks for reply mate, I got it figured. I also manage to get root and twrp recovery but not both at the same time. After flashing and using twrp recovery I then lose root after reboot and have to flash a patched magisk bundle over odin again. Bit inconvenient but I only intend using twrp now and then for backup/recovery.
Can you recommend a stable rom for this device - far too much google bloat on it for my liking. I tried latest lineage but found it unstable.
chadandchew said:
Thanks for reply mate, I got it figured. I also manage to get root and twrp recovery but not both at the same time. After flashing and using twrp recovery I then lose root after reboot and have to flash a patched magisk bundle over odin again. Bit inconvenient but I only intend using twrp now and then for backup/recovery.
Can you recommend a stable rom for this device - far too much google bloat on it for my liking. I tried latest lineage but found it unstable.
Click to expand...
Click to collapse
Just install LineageOS. Clean, no Bloat, everything smooth and you can have TWRP and Root/Magisk at the same time.
Depending on how much Google you want to have on your device, you might rather choose LOS+MG ( https://lineage.microg.org/) I can highly recommend it. You get rid of Google which debloats it even more and is a plus for your privacy but almost everything works (at leat for me. But migh depend on your needs)
If you like Google, just use normal LineageOS (https://lineageos.org) + GAPPS
Thanks for reply. Will try the LOS ROM later. Wish Google crap would disappear totally. I hate it enormously.
By the way which folder am I looking for on that LOS ROM download page
Ah gts4lv I presume
chadandchew said:
Wish Google crap would disappear totally. I hate it enormously.
Click to expand...
Click to collapse
then go for LOS+MG: https://download.lineage.microg.org/gts4lv/
topaza said:
then go for LOS+MG: https://download.lineage.microg.org/gts4lv/
Click to expand...
Click to collapse
Recently switched to using MicroG Lineage. Timely enough, MicroG passes the SafetyNet now as per the instructions mentioned below and indicated in the attached screenshot. For the fingerprint, I had selected the T720 from the list.
https://www.reddit.com/r/MicroG/comments/shmpng
Along with Aurora store installed as a service, I think you don't need Google anymore.
topaza said:
Just install LineageOS. Clean, no Bloat, everything smooth and you can have TWRP and Root/Magisk at the same time.
Depending on how much Google you want to have on your device, you might rather choose LOS+MG ( https://lineage.microg.org/) I can highly recommend it. You get rid of Google which debloats it even more and is a plus for your privacy but almost everything works (at leat for me. But migh depend on your needs)
If you like Google, just use normal LineageOS (https://lineageos.org) + GAPPS
Click to expand...
Click to collapse
I'm having some problem here:
I can install LineageOS, I can root/Magisk, I can have TWRP, but not all together at once.
Can you help me on how to do this?
Working on a SM-T725 of course, actually rooted, lineage and TWRP installed, but my Magisk can't install modules, it seems it doens't have root privileges.
Thanks in advance for your answer
anybody have an updated one, the file has been archived on the said link... thanks in advance
Hello very friendly helping people!
Im a 10 year iPhone user, but over time i came to hate all the restrictions and so i got myself a K30 Ultra and later today it should finally arrive!
Unfortunately i found out that it doesnt check the Google SafetyNet thingy and i can't use Google Pay with it. That kinda sucks, I never thought about stuff like this on iOS, but I'm confident there is a solution for it.
I found out about rooting my device, but it somehow isn't possible because of the Mediatek chip. But then I also found out that apperenty there IS a way to use the program/thingy that makes the phone pass SafetyNet (Magisk) without the need of a custom ROM.
I'm sorry if im confusing words like rooting im very noobish about all this.
So here are my questions in short form:
1. Can I make Google Pay Work in any way on my Redmi K30 Ultra?
2. Does this also affect my banking apps (I'm using DKB and Kontist) and can this be solved, too?
3. Could you link me some guides how to do it?
4. Is there any danger doing it (like deleting my phone if it doesnt work) and is there a possibility to safe my device on the PC or something like this to be safe?
5. Are their any safety concerns doing "it" (not sure what the solution will be) and should I install an anti virus program on the device? I just read about the cerberus trojan and its kinda scary. I think iOS systems were always pretty safe against those.
6. Anything else i need to know?
Thank you so much! I appreciate it a lot that there is a place where i can go to get help on those things! <3
Google Pay and any other banking apps refuse to work when a rooted Android gets detected by them. BTW: SafetyNet API doesn't purely check whether the device's Android is rooted, as the API is designed to check the overall integrity of device's Android.
jwoegerbauer said:
Google Pay and any other banking apps refuse to work when a rooted Android gets detected by them. BTW: SafetyNet API doesn't purely check whether the device's Android is rooted, as the API is designed to check the overall integrity of device's Android.
Click to expand...
Click to collapse
Hey, thanks for your post!
Are you implying that there is no way around that and its doomed to forever not work on my device?
To clarify things: SafetyNet is run by an app that has implemented this API, it's not run by Android OS itself. Yes, Magisk allows you to lever out this test by manipulating device's fingerprint so you will possibly be able to use Google Pay etc.pp
FYI: Any app not having SafetyNet API implemented easily can check whether Android got rooted / tampered or not. The app simply runs functions like
Code:
isRootNative
isDetectedDevKeys
isDetectedTestKeys
isFoundBusyboxBinary
isFoundDangerousProps
isFoundHooks
isFoundResetprop
isFoundSuBinary
isFoundWrongPathPermission
isFoundXposed
isNotFoundReleaseKeys
isPermissiveSelinux
isSuExists
isMagiskSUExists
isFoundMagisk
isFoundRootCloakingApps
what can't get prevented by Magisk.
jwoegerbauer said:
Yes, Magisk allows you to lever out this test by manipulating device's fingerprint so you will possibly be able to use Google Pay etc.pp
Click to expand...
Click to collapse
Ok, perfect. Would you be able to link me to a guide that shows me how to install Magisk on my device? It has a Mediatek chip so a custom ROM isn't possible (as far as I understand).
Mirardt said:
Ok, perfect. Would you be able to link me to a guide that shows me how to install Magisk on my device? It has a Mediatek chip so a custom ROM isn't possible (as far as I understand).
Click to expand...
Click to collapse
How to install Magisk without a Custom ROM is explained here.
If a Custom ROM like TWRP isn't officially made public for your device then you have to compile TWRP at your own.
This is TWRP and Magisk for the latest firmware on the K30 Ultra. https://mifirm.net/downloadtwrp/166
---------- Post added at 07:39 PM ---------- Previous post was at 07:37 PM ----------
Google Pay on a rooted device with Magisk installed /is/ possible, my Galaxy Note 9 with Dr. Ketan's ROM works with Google Pay and I believe it's due to the CTS Profile fix which is available in its ROM Tool app. So there's going to be some way to make it work with the K30 Ultra.
JaboJG said:
This is TWRP and Magisk for the latest firmware on the K30 Ultra. https://mifirm.net/downloadtwrp/166
Click to expand...
Click to collapse
Oh wow how cool is that, that is custom for the K30 ultra
And do I install that with the guide linked above or do I need some certain skill and experience to do that. It says it isn't tested yet. If I do a mirror of my phone before nothing really bad can happen right?
Google Pay on a rooted device with Magisk installed /is/ possible, my Galaxy Note 9 with Dr. Ketan's ROM works with Google Pay and I believe it's due to the CTS Profile fix which is available in its ROM Tool app. So there's going to be some way to make it work with the K30 Ultra.
Click to expand...
Click to collapse
Nice!!!
Yeah the only think that failed SafetyNet Test is the "CTS profile match". But I can't use those roms for my K30 ultra, right, so I just do it with Magisk?
Thanks so much!!
You need to unlock your bootloader with the Mi Unlock tool then flash TWRP over fastboot, and in TWRP make the appropriate backups and flash Magisk. There's many guides and it's relatively straight forward.
K30 Ultra is basically a brand new phone, it's like a month old. It'll be a while but keep an eye on XDA Forums, on the internet, and on YouTube. Somebody will eventually describe or figure out how to fix the CTS Profile.
I think I'm not gonna modify mine and I'll just wear my Apple Watch to use it for contactless payments.
JaboJG said:
You need to unlock your bootloader with the Mi Unlock tool then flash TWRP over fastboot, and in TWRP make the appropriate backups and flash Magisk. There's many guides and it's relatively straight forward.
K30 Ultra is basically a brand new phone, it's like a month old. It'll be a while but keep an eye on XDA Forums, on the internet, and on YouTube. Somebody will eventually describe or figure out how to fix the CTS Profile.
I think I'm not gonna modify mine and I'll just wear my Apple Watch to use it for contactless payments.
Click to expand...
Click to collapse
Alright, so I read 12384 guides and had a very tiny sense of it. The Mi Unlock tool stopped me, though, and now I'll have to wait another 6 days.
As I understood it, my data will be erased, but can be just be restored by MIUI if backed up before. I'm gonna let you know how it worked after I'll do it in about a week.
Probably I won't have to patience to wait. Google Pay is a really nice to have, but neither voLTE, nor voWifi works on my device, so I for sure have do hack that some weird way, because i have no mobile network at all at home and absolutely need voWifi.
Thank you very much for your kind help! <3
No problem at all.
I'm not sure if Wifi-Calling (voWifi) works with my carrier as I've turned it on with the carrier and in the phone, and it doesn't seem to be making calls over wifi. Not a big deal for me though as I've got Unlimited calls with my carrier.
Please let us know if and when you do flash the TWRP as I'd like feedback before flashing it myself.
Do your banking apps refuse to work or is it only google pay that fails due to the safetynet fail?
JaboJG said:
No problem at all.
I'm not sure if Wifi-Calling (voWifi) works with my carrier as I've turned it on with the carrier and in the phone, and it doesn't seem to be making calls over wifi. Not a big deal for me though as I've got Unlimited calls with my carrier.
Please let us know if and when you do flash the TWRP as I'd like feedback before flashing it myself.
Click to expand...
Click to collapse
Yeah, me too, but I have a very bad connection in my flat so I do need voWifi anyway. I will let you know and hope I won't brick my device. But as I understand it, bricking the device just by flashing twrp is very unlikely, right?
MerlijnD said:
Do your banking apps refuse to work or is it only google pay that fails due to the safetynet fail?
Click to expand...
Click to collapse
Only Google Pay, both of my banking apps work perfectly. I couldnt scan the security bar code though, some internal google app wouldn't allow it. So i had to put in both the (very long) idendification and security numbers in manually.
Alright thanks. Another thing im interested in is if Snapchat works when safetynet fails. Did you do any tests regarding that?
MerlijnD said:
Alright thanks. Another thing im interested in is if Snapchat works when safetynet fails. Did you do any tests regarding that?
Click to expand...
Click to collapse
Not using Snapchat, but I just installed it and it starts without problems. Didn't made an account though.
So I'm gonna be able to flash twrp and Magisk in exactly 14 hours and have some questions i would really appreciate an answer to <3
Using this: https://mifirm.net/downloadtwrp/166
1. The thing i want to flash first is twrp and it is the file called "recovery.img" in the downloaded folder, is that correct?
2. Just flashing twrp is "relatively" safe and if I do a backup and the device bricks by installing Magsik after, i can recover it through twrp, correct?
3. Should I not install todays new security update to MIUI or does that not matter at all?
edit: 4. Do I need/want to have "USB debugging", "Install via USB" and "USBebugging (Security Settings)" enabled or just "OEM unlocking"?
Thank you so much! I'm very nervous since i didn't read any experiences of rooting the K30 Ultra before and I'm scared of killing it.
Hey Mirardt, good luck. Let us know how you get on!
1. Yeah, you'll use fastboot to flash the recovery.img for TWRP.
2. Do a full backup with TWRP and you should be safe.
3. Doesn't matter, it's just the September Android security update.
4. Yeah turn on USB Debugging and connect your phone to your computer - it will ask you if you want to allow this computer to debug your phone, choose accept and always (or something similar to those words.) Do this before flashing TWRP.
Mirardt said:
So I'm gonna be able to flash twrp and Magisk in exactly 14 hours and have some questions i would really appreciate an answer to <3
Using this: https://mifirm.net/downloadtwrp/166
1. The thing i want to flash first is twrp and it is the file called "recovery.img" in the downloaded folder, is that correct?
2. Just flashing twrp is "relatively" safe and if I do a backup and the device bricks by installing Magsik after, i can recover it through twrp, correct?
3. Should I not install todays new security update to MIUI or does that not matter at all?
edit: 4. Do I need/want to have "USB debugging", "Install via USB" and "USBebugging (Security Settings)" enabled or just "OEM unlocking"?
Thank you so much! I'm very nervous since i didn't read any experiences of rooting the K30 Ultra before and I'm scared of killing it.
Click to expand...
Click to collapse
JaboJG said:
Hey Mirardt, good luck. Let us know how you get on!
1. Yeah, you'll use fastboot to flash the recovery.img for TWRP.
2. Do a full backup with TWRP and you should be safe.
3. Doesn't matter, it's just the September Android security update.
4. Yeah turn on USB Debugging and connect your phone to your computer - it will ask you if you want to allow this computer to debug your phone, choose accept and always (or something similar to those words.) Do this before flashing TWRP.
Click to expand...
Click to collapse
Hey Jabo, nice, I'm gonna do just that! Just for clarification, I use Mi Unlock Tool first, THEN twrp, then backup, then magisk?
I'll let you know and thanks for the good luck!
edit: so the command would be "fastboot flash recovery recovery.img", right?
I'm VERY sorry for the noobish questions.
I'm going to quickly use this thread to ask how to actually unlock the K30 Ultra Bootloader. I did everything the guides said, but Mi Unlock still doesn't recognize the phone when it's plugged in. Any Advice?
Hey guys (especially JaboJG). quick update: Flashing twrp and Magsik both just worked perfectly. no brick. Thanks for your help!!
The only issue is that it didnt help in passing Google Safety Check. I tried almost everything there is and will post my logs of MagiskHide Props in their thread soon.
Also, now some apps don't work anymore because they detect the root. I hope we will find a fix.
macrett said:
I'm going to quickly use this thread to ask how to actually unlock the K30 Ultra Bootloader. I did everything the guides said, but Mi Unlock still doesn't recognize the phone when it's plugged in. Any Advice?
Click to expand...
Click to collapse
No idea, sorry. It just worked for me.