No, i'm not stupid
Had many custom roms on my N5, and with No Root/Xposed and a Locked bootloader, i can use apps that use safetynet and also android pay - this includes 6.0.1 Roms released recently, including CM13 Nightlys.
Does anyone know why the android 7.1 Roms on here (i tested most of them) Fail safetynet? I get a bluescreen from Safetynet Helper, saying "Response Validation Failed" - this is with root removed, and bootloader still locked just as i had before with 6.x roms that were working fine. I have tried both Banks Dynamic Gapps and OpenGapps in case anyone was wondering.
I have also tried unlocking the bootloader before installing (doesnt usually make a difference for some reason) and i still get the blue fail screen.
Norman
bump?
I don't have any help, but I've been struggling with Android Pay and this same issue.
jblaylock said:
I don't have any help, but I've been struggling with Android Pay and this same issue.
Click to expand...
Click to collapse
Yeah it's just the android 7 and 7.1 ROMs for the nexus 5, shame, as they run really well, much better than 6.x.x roms for me, but i use android pay.
Me too. I tried 7.1 many times, but I use AP too and at this point I'm not ready to give it up for 7.1, though I would really like the updated version. I kept hearing the Franco Kernel would bypass SafetyNet, but I've tried that many times and FK doesn't pass it either.
jblaylock said:
Me too. I tried 7.1 many times, but I use AP too and at this point I'm not ready to give it up for 7.1, though I would really like the updated version. I kept hearing the Franco Kernel would bypass SafetyNet, but I've tried that many times and FK doesn't pass it either.
Click to expand...
Click to collapse
I'm not a programmer, but it just seems like there is a file or 2 missing that's preventing the service from sending the request. It's not Failing safetynet, it's just not getting the request back
I so wish I could us 7.1 and AP...
Any SafetyNet work for CM13 ? i use magisk 18 not work
Related
I have been trying multiple different 7.0 & 7.1 Roms, in hopes of upgrading to the new OS. I have yet to find one that I can use Android Pay (AP) with. I have tried several kernels that I hoped would work, but to no avail.
Now, I know Google made changes to Safety Net with Nougat to not allow AP and unlocked bootloaders. But I was curious if anyone has found a Rom or another way around this? I'd love to have both 7.1 and AP.
I currently use AP often, and like the convenience of it, but I've been trying to decide which is more important to me, AP or Nougat. So, if there's a way out there, please let me know.
As android N is not official it will not work. Only official google factory images work with AP.
not necessarily
wangdaning said:
As android N is not official it will not work. Only official google factory images work with AP.
Click to expand...
Click to collapse
I don't believe this is true. There are cyanogenmod roms that work with AP.
The requirements that Google added for AP's safetynet I believe are bypassable by a kernel patch if I remember correctly.
As for the other requirements, I have no idea what is needed.
I would love if I could have AP working on the pixel rom, or cyanogenmod for nexus 5.
Mortimus said:
I don't believe this is true. There are cyanogenmod roms that work with AP.
The requirements that Google added for AP's safetynet I believe are bypassable by a kernel patch if I remember correctly.
As for the other requirements, I have no idea what is needed.
I would love if I could have AP working on the pixel rom, or cyanogenmod for nexus 5.
Click to expand...
Click to collapse
I had been told that Franco Kernel would bypass, but I tried many times and different versions, and no luck.
Android Stock
Will it work on stock rom?
maghat11 said:
Will it work on stock rom?
Click to expand...
Click to collapse
So far, even with an unlocked bootloader, it works on stock. 6.0.1
Thank You
Thank you a lot
Well, it was working on Stock. I tried to pay for my groceries at the supermarket over the weekend and got rejected with AP. I'm not sure if Google has made any additional changes, but my device passes SafetyNet.
Hi all,
I'm looking for a custom rom that still has builds available from before the Nov 2016 security update.
Very specifically, I'm looking to run xposed and still passing safetynet, the last time I was able to do that was running an OS version that was that old. I was running CM 13 at the time, however I can't find an osprey build of CM mirrored somewhere from that time...
Any suggestions?
Edit: I still have a .zip file for a version of CM from before then, however it's for a different device... How different are the builds? Could it conceivably work? (other device is a Xiaomi Mi5)
I don't think you understand how safetynet works... it will autoupdate itself and it checks an online database, it doesn't matter if your ROM is prior to november 2016 or not.
acejavelin said:
I don't think you understand how safetynet works... it will autoupdate itself and it checks an online database, it doesn't matter if your ROM is prior to november 2016 or not.
Click to expand...
Click to collapse
That may well, be, but until I recently changed from my old version of CM 13 to LineagOS, I could run pokemon go with xposed installed! I no longer can...
I'd like to at least try it again, hence need either an old mirror of CM builds, or another custom ROM that keeps available old builds...
cangurob said:
That may well, be, but until I recently changed from my old version of CM 13 to LineagOS, I could run pokemon go with xposed installed! I no longer can...
I'd like to at least try it again, hence need either an old mirror of CM builds, or another custom ROM that keeps available old builds...
Click to expand...
Click to collapse
You can try, you need CM13 (or other Marshmallow base ROM), CM14 is Nougat based and uses a more advanced Safetynet API... In the Pixel with Nougat, just having an unlocked bootloader but otherwise purely stock will not allow a SafetyNet API verification, but I can't say it's the same for other devices.
Most custom ROMs don't work with Xposed anyway, it isn't supported so other than finding someone with an old CM13 build around you might be out of luck.
cangurob said:
That may well, be, but until I recently changed from my old version of CM 13 to LineagOS, I could run pokemon go with xposed installed! I no longer can...
I'd like to at least try it again, hence need either an old mirror of CM builds, or another custom ROM that keeps available old builds...
Click to expand...
Click to collapse
I use LOS, when I want to play Pokemon I just boot into recovery and flash the unroot zip. When I'm done, just root again. Sure it takes a couple minutes, but you get the best of both worlds.
Sent from my MotoG3 using Tapatalk
riggerman0421 said:
I use LOS, when I want to play Pokemon I just boot into recovery and flash the unroot zip. When I'm done, just root again. Sure it takes a couple minutes, but you get the best of both worlds.
Click to expand...
Click to collapse
Just switch to Ingress, same basic principle from same company, no issues with root. Lol
acejavelin said:
so other than finding someone with an old CM13 build around you might be out of luck.
Click to expand...
Click to collapse
That's kinda what I was hoping for with this thread!
riggerman0421 said:
I use LOS, when I want to play Pokemon I just boot into recovery and flash the unroot zip. When I'm done, just root again. Sure it takes a couple minutes, but you get the best of both worlds.
Click to expand...
Click to collapse
I can play pogo on my rooter LOS device without a problem. Magisk takes care of it perfectly, no flashing required. Xposed is another story though!
acejavelin said:
Just switch to Ingress, same basic principle from same company, no issues with root. Lol
Click to expand...
Click to collapse
I'm level 10 Ingress (played since the beta)
Hi guys.
When trying to use these type of ROMS I get one BIG problem. A program that uses BANK ID , when logging in to banks won't work anymore.
I think the file is named STK.apk. if I am not wrong.
On all the Stock (based) Custom Roms this operation work. But in AOKP,AOSP it doesn't. On stock based this program is White Color and after entering PIN code it disappears and log me into the bank.
But on AOKP,AOSP it is black, and it doesn't disappear it just times out after I enter PIN code.
Does anyone know a workaround or what can be the issue ? Someone mentioned that I should switch Kernel to fireopal 3.3 unofficial but that didnt work. I flashed Kernel in TWRP, maybe it should have been flashed in ODIN ?
Caligula. Peace Out
This will likely be due to a SafetyNet issue.
Where you rooted on stock? if yes with magisk or otherwise?
If you're still on aosp you can download this SafetyNet Helper Sample and see if you pass.
If you don't there are a few things you can do to pass it again.
jaannnis said:
This will likely be due to a SafetyNet issue.
Where you rooted on stock? if yes with magisk or otherwise?
If you're still on aosp you can download this SafetyNet Helper Sample and see if you pass.
If you don't there are a few things you can do to pass it again.
Click to expand...
Click to collapse
Hi , I did use SuperManRom and BatmanRom, I think they both were rooted yes, and they use Magisk 14 beta there I think.
I will try to flash an Aosp-Aokp Rom again and then try with this App you are posting. Thank you. Now I am on STOCK Samsung since I couldn't get this to work. I used KIES to go back to fabric base.
I will make a backup and then try
UPDATE : I have now flashed Lineage Os 14.1 and I haven't root and Safetynet fails. So first thing I need is root maybe ?
mrcaligula said:
Hi , I did use SuperManRom and BatmanRom, I think they both were rooted yes, and they use Magisk 14 beta there I think.
I will try to flash an Aosp-Aokp Rom again and then try with this App you are posting. Thank you. Now I am on STOCK Samsung since I couldn't get this to work. I used KIES to go back to fabric base.
I will make a backup and then try.
Click to expand...
Click to collapse
Magisk has the capability to root your phone without triggering SafetyNet but that is (at least it was for me) a pain in the ass to get it working correctly.
Another thing I did with Snapchat (also doesn't work if SafetyNet is triggered) is that I set up the App on a clean stock rom, then backed it up with Titanium Backup and installed it on the rooted/aosp/... ROM. Note: This also works if the SafetyNet check in the app is only executed when you first login.
Thanks for info
I get false on the first CPTID(something) the heaviest of the 2 checks on SAFETYNET the other one I get ok.
After I install Magisk 14.
But I am giving up. Can't really find a 100 % workaround for this.
So I am running beta 3 of Ressurection Remix from OpenKirin website. Everything is smooth even after heavy tweaks. But I want to root this ROM. Reason is I want to uninstall built-in apps and some of my apps require root access. I already tried rooting the ramdisk.img. it failed. Even though it was rooted root access wasn't available. So can I directly flash latest magisk via elemental ROM TWRP? Or is there any other method?
Like you, I'm on the same build from yesterday, and obviously the minimum that I'd like to do is to root the ROM, since that we already miss a fully working TWRP and a compatible Xposed framework.
I discovered just yesterday topjohnwu's thread about patching the stock boot.img with the custom Magisk Manager apk for Huawei devices, but before doing everything I've decided to make a search on XDA, and I've stumbled upon this. So neither patching the stock ramdisk.img works?? Dammit. Becsuse standing by what i know, flashing latest Magisk on an A only GSI works, but i haven't read successful cases rooting an OpenKirin ROM yet.
I'd like to test this method, but i still have to setup some stuff on this ROM, and so i don't want to try something that could mess up system, trashing all the time that I've spent on configuring the device.
I'll update ya as soon as i can, if something useful should come out. I hope to update you soon!
Dude. I have done it and would like to tell you that it can be flashed normally. Currently enjoying root with all modules working. If you have an honor 6x just flash TWRP from elemental room thread and then latest magisk. So far no issues, no bootloop. However after first installation I recommend you to install via direct patch once again to ensure everything works. i.eif you still wanna know. This is way simpler
Thanks for letting me know mate, yeah i have a 6X. Actually I've installed TWRP and flashed latest stable Magisk, V17.1. Magisk is correctly detected by Magisk Manager.
Now, the file that i should provide to patch on Magisk Manager is stock EMUI 8.0 boot.img, correct?
Nope. If you have magisk installed just direct install once again via magisk manager and you're good to go
Thanks Mannan, I'm enjoying root goodies too now.
I take the chance to ask ya if sound mods like Viper/Dolby Atmos will also work or not as a Magisk module, since that time ago (but even recently) i saw some users that was saying in a couple of threads that flashing one of these would corrupt system files, and so EMUI 8 had to be flashed again.
First of all we aren't on EMUI 8bso no corruption. We are on Android 8.1 so any Sound Mod for this Firmware should work. Now I haven't flashed it yet cause mainly I have to find a working one and of the risk of soft brick. But I will try and let you know if I find a working one. Same goes for exposed framework
Got it. Well it would be great, especially Xposed in systemless version.
EDIT - going off topic a while, even you notice a charging time much slower than on stock? Before, i usually charged something like 60-65% in one hour, now it tooks at least 1 hour and an half to achieve the same percentage of battery. Gotta tweak this someway.
Tried installing Viper4android. Gives IO error while mounting driver. Xposed I havent tried
Mannan Qamar said:
Tried installing Viper4android. Gives IO error while mounting driver. Xposed I havent tried
Click to expand...
Click to collapse
Thanks for the feedback. Sadly i think that Xposed won't work too.
HD8 2018 6.3.1.5 (and 6.3.1.4) issues
HD8 2018 OS continues to present never ending issues (seems like a poorly supported product compared to the earlier Fires ...)
I flashed 6.3.1.5 (6.3.1.4) on top of 6.3.1.2 via TWRP (+Magisk/systemless Xposed), and, ended up with a weird WiFi crashloop that took a few tries to understand. Essentially, the moment it connects to a WiFi network, it reboots. If I set WiFi to off, it's stable (have to do it quick before it connects after a reboot!). If I disable Xposed module, it's stable. Neither Xposed 89.3 or 90beta work correctly.
On 6.3.1.2 Xposed worked more or less OK.
I tried to downgrade back to OS 6.3.1.2 or 6.3.0.1, but apparently the settings are not compatible once you load 6.3.1.4 on it. It never reaches the launcher, and keeps sitting at Fire screen. I could not even boot 6.3.1.2 or 6.3.0.1 without Magisk. Doing a factory reset was not in my plan yet. So I had to go to 6.3.1.4 again where it booted fine. I now run 6.3.1.4 with Xposed disabled.
Anybody has 6.3.1.4 with Xposed & WiFi working properly out there? I wonder if this is also a similar issue with Fire 7 2019 (mustang) - @Michajin
HD10 2017 40.6.5.0_user_650601220 issues
Well, what do you know ... I finally took the plunge to do the unlock and install TWRP on my Kingoroot rooted HD10 2017 (thanks @k4y0z !). I backed up all the apps via Titanium Backup, and then backed up the internal sdcard via Total Commander to a zip, which later nicely restores things back with the proper timestamps (yay!). It's very difficult to restore timestamps, but Total Commander with root can do it.
In my optimism, after getting TWRP, I immediately installed the latest FireOS, 40.6.5.0_user_650601220, with Magisk, and Xposed installed into system (xposed-v89-sdk22-arm64.zip). And, just like HD8 2018, the moment I activated Xposed modules, the tablet started rebooting when WiFi was on. If I managed to hit WiFi off button before it did so, it seemed stable. So both HD10 2017 and HD8 2018 appear to have the same Xposed bug in the latest FireOS versions!!! I wonder if it's related to the fix of MTK-SU issue.
I also ran into Google Play & battery drain issues. Tired of several attempts of troubleshooting, I actually ended up backtracking all the way to 40.6.2.6_user_626533320, which is the version I started with. Once Google Play went south after my 1st restore, I could not fix it over multiple tries, and I had to do a Factory reset again and restore apps via Titanium Backup a bit more carefully, starting with the latest versions of Google Play apps without data (rather than just all at once). Now everything appears to be working as before, with TWRP, and the same old FireOS version that I already had
The battery drain issue was an interesting one, apparently, Vanced Youtube helper app, microg_YouTube_Vanced_0.2.6.17455, creates a lot of battery drain via needless Wakelocks, which can be fixed by running the following commands:
Code:
adb shell
su
pm disable com.mgoogle.android.gms/org.microg.gms.people.ContactSyncService
P.S. A week ago I unlocked HD8 2017 (OS version 50.6.3.6_user_636558520), and successfully cloned HD8 2016 to this 2017 via TiBa & Total Commander. That attempt went without a glitch, and that's why I thought I could also do HD10 in no time, but HD10 gave me all kinds of issues.
bibikalka said:
HD8 2018 OS continues to present never ending issues (seems like a poorly supported product compared to the earlier Fires ...)
I flashed 6.3.1.4 on top of 6.3.1.2 via TWRP (+Magisk/systemless Xposed), and, ended up with a weird WiFi crashloop that took a few tries to understand. Essentially, the moment it connects to a WiFi network, it reboots. If I set WiFi to off, it's stable (have to do it quick before it connects after a reboot!). If I disable Xposed module, it's stable. Neither Xposed 89.3 or 90beta work correctly.
On 6.3.1.2 Xposed worked more or less OK.
I tried to downgrade back to OS 6.3.1.2 or 6.3.0.1, but apparently the settings are not compatible once you load 6.3.1.4 on it. It never reaches the launcher, and keeps sitting at Fire screen. I could not even boot 6.3.1.2 or 6.3.0.1 without Magisk. Doing a factory reset was not in my plan yet. So I had to go to 6.3.1.4 again where it booted fine. I now run 6.3.1.4 with Xposed disabled.
Anybody has 6.3.1.4 with Xposed & WiFi working properly out there? I wonder if this is also a similar issue with Fire 7 2019 (mustang) - @Michajin
Click to expand...
Click to collapse
you will have to refresh me where i had on the mustang. I am using los 16.0 on the hd8, dont really have a need for xposed. Seems like i had this on the mustang right after root when on stock? i will look into it and try and refresh myself if you cant point me into the thread...
Michajin said:
you will have to refresh me where i had on the mustang. I am using los 16.0 on the hd8, dont really have a need for xposed. Seems like i had this on the mustang right after root when on stock? i will look into it and try and refresh myself if you cant point me into the thread...
Click to expand...
Click to collapse
It was here :
https://forum.xda-developers.com/showpost.php?p=79841222&postcount=21
bibikalka said:
It was here :
https://forum.xda-developers.com/showpost.php?p=79841222&postcount=21
Click to expand...
Click to collapse
I am trying to remember but it seems i had to flash full xposed from TWRP. I think i had issues with the systemless version from magisk. I didn't know people would chose to run FIRE-OS once anything else was available (no offense) with 14.1 and 16, both being decent... lol
Michajin said:
I am trying to remember but it seems i had to flash full xposed from TWRP. I think i had issues with the systemless version from magisk. I didn't know people would chose to run FIRE-OS once anything else was available (no offense) with 14.1 and 16, both being decent... lol
Click to expand...
Click to collapse
You have a point here regarding LoS I thought I was gaining stability by sticking to FireOS, but this version has been anything but stable!
I need Skype to work - is the camera working in either LoS 14.1 or 16? The issue is that some of these ROMs seem to be in eternal beta, once the low hanging fruit is done, the polish is not applied further.
bibikalka said:
You have a point here regarding LoS I thought I was gaining stability by sticking to FireOS, but this version has been anything but stable!
I need Skype to work - is the camera working in either LoS 14.1 or 16? The issue is that some of these ROMs seem to be in eternal beta, once the low hanging fruit is done, the polish is not applied further.
Click to expand...
Click to collapse
The camera works on both 16.0 and 14.1. But 14.1 is by far more stable at this time. Bluetooth and headphones (plus more- see thread) issues on 16.0. The only issue on 14.1 is the headphone jack doesn't work (but i think someone has found a fix for it but it hasnt been updated in the rom). Backup in TWRP and install 14.1 and give it a shot, i am on 16.0. 14.1 was working really smooth. I have not tested skype on either. 14.1 seemed smoother and less buggy than fireOS right at Beta.
bibikalka said:
You have a point here regarding LoS I thought I was gaining stability by sticking to FireOS, but this version has been anything but stable!
I need Skype to work - is the camera working in either LoS 14.1 or 16? The issue is that some of these ROMs seem to be in eternal beta, once the low hanging fruit is done, the polish is not applied further.
Click to expand...
Click to collapse
Observation regarding custom ROMs is one reason I typically hang with 'stock' and tune to my liking. LOS 14.1 for this device/gen (and a few others) is an exception; worth considering. LOS 16.1 is less refined ATM with no meaningful advantage over 14.1.
bibikalka said:
You have a point here regarding LoS I thought I was gaining stability by sticking to FireOS, but this version has been anything but stable!
I need Skype to work - is the camera working in either LoS 14.1 or 16? The issue is that some of these ROMs seem to be in eternal beta, once the low hanging fruit is done, the polish is not applied further.
Click to expand...
Click to collapse
I needed to have headphones working, so I didn't try LOS 14 until recently. I'm extremely happy with it. It's so much snappier than stock for me, and videos load so much faster, like in Netflix, for example. I'm also using Magisk and Xposed with no issues.
I didn't realize the new build is up with fixes... Going back to 14.1, I think he is working on 17.0 (Kaijones23) 17.0 was updated last night....
https://github.com/mt8163/android_device_amazon_karnak/branches
Noob question - how do you flash lineage-16 or cm-14.1 onto the device? I downloaded the zip files from the link above, but they are way to small to be a complete rom. Is there a different location where I can download the roms?
xantiux said:
Noob question - how do you flash lineage-16 or cm-14.1 onto the device? I downloaded the zip files from the link above, but they are way to small to be a complete rom. Is there a different location where I can download the roms?
Click to expand...
Click to collapse
Have you unlocked the bootloader (prerequisite):
https://forum.xda-developers.com/hd...nlock-fire-hd-8-2018-karnak-amonet-3-t3963496
I have unlocked the bootloader, for which I had to open the tablet up in order to short a pin. I was able to load the FireOS 6.0.0.0 and 6.0.0.1, and was looking if there is a way to load 6.0.1.2 or 6.0.1.4, when I came upon this thread, and saw that it may be possible to load lineage or cm, but I don't know how to get my hands on the ROMs. The downloads from the links above are way too small.
xantiux said:
I have unlocked the bootloader, for which I had to open the tablet up in order to short a pin. I was able to load the FireOS 6.0.0.0 and 6.0.0.1, and was looking if there is a way to load 6.0.1.2 or 6.0.1.4, when I came upon this thread, and saw that it may be possible to load lineage or cm, but I don't know how to get my hands on the ROMs. The downloads from the links above are way too small.
Click to expand...
Click to collapse
This help?
https://forum.xda-developers.com/hd8-hd10/general/lineageos-14-1-fire-hd8-2018-t3936242
https://forum.xda-developers.com/hd8-hd10/orig-development/rom-lineage-16-0-t3981685
This is great, thank you!
Somewhat related question - is it hard to get a zip of fireOS 6.3.1.2, so it can be flashed via TWRP?
xantiux said:
This is great, thank you!
Somewhat related question - is it hard to get a zip of fireOS 6.3.1.2, so it can be flashed via TWRP?
Click to expand...
Click to collapse
Supposedly renaming .bin to .zip allows flashing from twrp. I'd be wary of other partitions such as recovery and aboot which could trigger a bad day.
Headphone fix for LOS 14 has been applied in the latest version of the ROM. If you don't feel like reflashing entire ROM, there is a flashable zip containing only the headphone fix (module). I don't have the links handy but it's all available on this forum.
Updated post #1 and described HD10 '17 Xposed WiFi crashloop as well.
Updated with the same HD8 2018 6.3.1.5 WiFi/Xposed issue.
bibikalka said:
Updated with the same HD8 2018 6.3.1.5 WiFi/Xposed issue.
Click to expand...
Click to collapse
Welcome back!