Over my fully stock mobile (With Stock OOS 4.1.7) had installed following in sequence: Factory Reset with TWRP, Flash Stock Modem and Firmware Open Beta 22, then Patch for dm-verity, and finally Resurrection ROM 5.8.4 with GAPPS and no wipe cache/data. Now mobile is working fine and rooted, but two problems still persist - any suggestions ?
Key Issue: Clean master autostarts does not show up, i think root is not detected with Magicsk ? Can I safely flash SuperSU with Magicsk to get it working or some other remedy to be done ?
Secondry Issue: Not sure its related or not, but SafteyNet shows ctsProfile=false, basicIntegrity=false. I've no supersu installed so no question of leftover files, also there is no USB debugging option so that I can enable this stuff (may be required for clean master ?). Alongside other apps like Android Pay, not working due to SafetyNet issues.
Related
Hi there. Has anybody built a ROM with the following specs?
- based on stock 14.6.A.1.236 (android 5.1.1)
- pre-rooted
- all security patches added, e.g. patches for those 10 critical bugs that have just been fixed
It is not stock but aosp: https://forum.xda-developers.com/sony-xperia-z1-compact/orig-development/rom-jaguar-amami-lp5-1-1-r37-hardened-t3396713
In Jaguar you get all the patches within 1 or 2 days. I am using it atm.
Alright, I just switched to Jaguar.
But it wasn't easy. Dual recovery with Philz & TWRP 2.8.x defended itself very persistently. Installing TWRP 3.0.2 had no effect - neither in recovery partition nor in FOTA kernel. Even the uninstall zip of dual recovery couldn't wipe TWRP 2.8.x, although the script said it had run successfully. So I kept installing images into different partitions in fastboot mode (which was the only mode that kept working all the time). In the end TWRP 3.0.2 suddenly appeared after 3 hours.
In Jaguar it was also a bit fiddling to get AFWall+ working. Optimumpro's dowload has a rather old version, which kept blocking all traffic. But after removing it and installing the current v2.9.1 it worked. Now I've installed all apps I need. Everything seems to work except for Gmail. That one always crashes on start. Its background process also steadily crashes, so every other minute I see a popup that tells me "Unfortunately, Gmail has stopped". Clearing cache and data has not solved the problem. Stopping sync had no effect either. Maybe re-installing the gapps.zip in TWRP will help...
I also had problems to install TWRP 3.0.2 persistantly. My solution was to install Philz TWRP 2.8 and inside TWRP 2.8 I flashed 3.0.2. After that only 3.0.2 TWRP was available.
OptimusPro pointed out that Internet is only working if you allow apps in AFWall.
I switched AFWall+ from white-listing to black-listing and put nothing on the list, so currently everything can access the internet. And that's also what I tried in the older version of AFWall+, but it didn't work there.
One more question: where did you find the zip (for installation in recovery) of TWRP 3.0.2? I can only find img files for installation with fastboot.
I think in optimuspro version he disabled it?
you do not need a zip. In TWRP 2.8 go to INSTALL and there should be a button "Install Image" Then you can load and flash an img file.
Oh, I didn't know that you can flash img files in some recoveries. However the only partition I can select in TWRP for installation is /boot. Well, I proceed with the installation just for the fun of it... (some minutes later)... and yes, it has really overwritten /boot. That's not where a recovery belongs.
Anyway, now I can hopefully solve my problems. I use a lot of Google applications, but I guess I took a package that overwrote some files in /system that are not compatible with the rest of optimuspro's ROM. So I just flash everything again, but this time with a smaller gapps package. Let's give "micro" a try...
edit: No, that was not the solution. Gmail is still crashing.
Which opengapps version are you using?
I use arm, 5.1, pico. And then I just download the gapps from the play store.
I do not have gmail account, so I cannot test gmail. It is strange that it is not working. I meand it is just a mail app or is it so deep diving in the system?
First I tried gapps "stock". Now I see that this package was too big, because it not only installed a bunch of apps I don't need, it also removed SlimPie launcher, the camera app, and the mail app that comes with Jaguar. I guess it also removed some more apps... probably every app that could be replaced by a Google app.
Now in the 2nd run I used gapps "micro". It looks like none of the Jaguar apps have been removed. Gmail still came with the gapps package, but now it has been installed side by side with the mail app that comes with Jaguar. The same for the launcher. And of course I had to install some apps in play store (e.g. maps), which were not included in the package.
Well, I'm not sure if I like the Jaguar ROM. Sure it has the right priorities. But aside from gmail I might have found some more problems. I installed Automate in order to automatically turn on/off wifi when coming home/leaving home. Turning wifi off (and using cellular data) works fine, but when coming home and wifi is being enabled AFWall+ blocks wifi traffic. So far I could manage to unblock wifi only by activating/deactivating airplane mode (or rebooting of course). And there might be problems with WhatsApp as well. Sometimes I don't receive messages until WhatsApp has been opened. Maybe the background process doesn't run or it is not able to receive data, even over wifi. Maybe AFWall+ is blocking traffic again... or some security defaults are blocking WhatsApp. I don't know. Threema doesn't seem to have the same problems, it works very well on Jaguar.
Whats App is working for me withour problems. And AFWall+ runs normal.
But yeah, I would say that custom roms are always trickier than stock roms. But for me Jaguar is the only rom where I can say, that I am on best security level. So I can live with the issues I have.
I realized that I need to do the gps fix which is mentioned in th main thread.
Hello everyone !
As you know this module help you to fix Safetynet by change build fingerprint to Xiaomi Mi 6s
But when you use the original module, Google will show your device as Xiaomi Mi 6s
I made a little modify to change build fingerprint to our HTC stock ROM, it'll show your device as HTC 10
A build will release when the original build release, same time !
Some report said that you can use this module for HTC stock ROM, I can't help you if you got error about this ROM
Download : Move to Download tab
ROM tested : LineageOS (official), RR (official)
This required :
No Xposed and SuperSU, even systemless
Systemless modifications in your system only
MagiskSU
Magisk Hide working properly
Main thread : https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431
Thanks to : @Deic for his source code
XDA:DevDB Information
HTC 10 (pme) SafetyNET fix, Tool/Utility for the HTC 10
Contributors
hiimpig1
Source Code: https://github.com/piiiggg/xiaomi-safetynet-fix/tree/pme
Version Information
Status: Stable
Created 2017-06-25
Last Updated 2017-06-28
Update some screenshot
Tested on : LOS official and RR official ROMs
Can confirm that this work on stock ROM, if any magisk module cause safetynet to fail. Thanks for your work!
azZA_09 said:
Can confirm that this work on stock ROM, if any magisk module cause safetynet to fail. Thanks for your work!
Click to expand...
Click to collapse
Thanks, I'll note it on #1
Installing it made my mobile data not turn on anymore, as well as killing off wifi, and magisk. it also unrooted me. it basically ruined my phone. wow.
tiki2134 said:
Installing it made my mobile data not turn on anymore, as well as killing off wifi, and magisk. it also unrooted me. it basically ruined my phone. wow.
Click to expand...
Click to collapse
I think you have to enable force encrypt when install magisk, try this
Install any kind of root like supersu - download magisk manager - install magisk without disable force encrypt - uninstall supersu - install module
I never use stock rom so idk, I only tested on custom ROM
tiki2134 said:
Installing it made my mobile data not turn on anymore, as well as killing off wifi, and magisk. it also unrooted me. it basically ruined my phone. wow.
Click to expand...
Click to collapse
Same thing happened to mine. Get the uninstall zip from the Deic thread referenced above and it will put your phone back where it was. You'll have to download it to your computer first and then copy it to your SD card via USB or putting your card into your computer. Then get into the recovery by powering down and holding the power and vol-down keys to get into Boot loader or using the power key options in your ROM, if present. I couldn't get into the Recovery with the power key options but could get into the Boot loader. Once in the Boot loader, use the volume-down key to get to the recovery option and execute it by pushing the power key. From recovery install the uninstall that you copied to your SD card (internal or external) and reboot. My phone came back up in the same state as before trying the module.
lichan said:
Same thing happened to mine. Get the uninstall zip from the Deic thread referenced above and it will put your phone back where it was. You'll have to download it to your computer first and then copy it to your SD card via USB or putting your card into your computer. Then get into the recovery by powering down and holding the power and vol-down keys to get into Boot loader or using the power key options in your ROM, if present. I couldn't get into the Recovery with the power key options but could get into the Boot loader. Once in the Boot loader, use the volume-down key to get to the recovery option and execute it by pushing the power key. From recovery install the uninstall that you copied to your SD card (internal or external) and reboot. My phone came back up in the same state as before trying the module.
Click to expand...
Click to collapse
The module change (faking) bootloader unlock status, could be a problem with HTC stock ROM. When you got this problem, after install Magisk or install my module ?
hiimpig1 said:
The module change (faking) bootloader unlock status, could be a problem with HTC stock ROM. When you got this problem, after install Magisk or install my module ?
Click to expand...
Click to collapse
This was on an HTC 10 with Viper 10 ROM with Magisk 12 and Magisk SU installed with Magisk Hide activated. It happened after installing the Safety Net fix. I did not have Magisk encryption enabled and may have had a couple of modules installed. I may try some different things to see if I can get it to work later.
lichan said:
This was on an HTC 10 with Viper 10 ROM with Magisk 12 and Magisk SU installed with Magisk Hide activated. It happened after installing the Safety Net fix. I did not have Magisk encryption enabled and may have had a couple of modules installed. I may try some different things to see if I can get it to work later.
Click to expand...
Click to collapse
Radio not working on stock ROM because encryption not enable, a guy was taking about this before. Or changing stock ROM bootloader status could cause this problem.
It was working fine earlier, but now I updated to 13.2 & safety check stopped working, uninstalled from Tarp uninstaller & reinstalled the 12.0, flashed safety check for HTC 10, but safety check fails please tell me how to fix
aryan_rulz_1983 said:
It was working fine earlier, but now I updated to 13.2 & safety check stopped working, uninstalled from Tarp uninstaller & reinstalled the 12.0, flashed safety check for HTC 10, but safety check fails please tell me how to fix
Click to expand...
Click to collapse
Sorry, I was sold my device. You can learn how to make new version of this module on main thread
aryan_rulz_1983 said:
It was working fine earlier, but now I updated to 13.2 & safety check stopped working, uninstalled from Tarp uninstaller & reinstalled the 12.0, flashed safety check for HTC 10, but safety check fails please tell me how to fix
Click to expand...
Click to collapse
The 13.3 update was released last night, thos should fix.
I have a Oneplus 5T and i'm struggling to install a google camera fix patch for my device but in the same time keep my phone root-free because i use a bank app called "BT pay" which detects magisk even with magisk hide, even with magisk manger hidden/uninstalled, i tried many times, can't get it done with root.
I keep tried to install TWRP (even if it being replaced by stock recovery evey boot) and install my gCam fix zip from there. but it seems like those files are replaced by stock files TOO...
I also tried to prevent TWRP from being replaced by deleting "install-recovery.sh" from /system/bin but this didn't work either.
Note that i have the official rom (oxigenOS beta 15) for my phone (official kernel too) which have Treble support, (the TWRP/gCam fix are also treble versions).
I take it you were using the MagiskHide Props Conifg Module right with Magisk 17.1? That is the only way you will pass Safety Net. Does your banking app still not work like that? (With a certified fingerprint)
Hi, I've bought a second Z2 on which I'm going to install Pie, TWRP, Magisk, edXposed and a lot of nice things...
On my previous Z2 I was still on Nougat, so A LOT of things are different to do....
Pie installation is done (not with some issues at first... )
TWRP is ok too.
Magisk is ok BUT I've found an issue with it trying to remove forced encryption (which I don't like a lot...).
On Nougat I removed it by SuperSU easy way...
With Magisk I've still not found the way to do the same...
I tried an "universal script" too here on XDA and it worked BUT.... as soon as Magisk reactive itself after formatting /data (Installer says Magisk is installed BUT it needs to download some "configuration files" and reboot...) phone begin to have an "early bootloop"....
To remove this I had to reflash at all... If I deleted /data and/or reflashed boot.img only, it begins to bootloop again after Magisk redownload these "configuration files"...
Anybody ( @erfanoabdi ?) has a solution for me?
My work project could be of great interest for many I think....
Hi. I was install LineaseOS 17.1 to xz2c. Then, installed the app that I use.
But, Some apps not work because, Rooting detected from my Phone.
Of course, I didn't rooting. (Wipe and only installed LOS and gapps)
I think I recognize it as a Rooted device due to the settings such as build.prop.
To solve this problem, I've tried Magesk or some other method( LOS Recovery -> pull build.prop and Modify), and there's still a problem.
I want to know which part of build.prop or what elements of something else are recognized as a routing device and how to solve this problem.
How should I fix something?
Previously, I tried to solve this problem with Magisk and Module, but it didn't work perfectly.
I have installed magisk and installed magiskHide Props Config 5.4.0 and universal safety net fix 1.1.1.
But Safetynet ctsProfile failed, and some apps works well, but others didn't.
There are only LOS and Gapps now.( Not Uninstall, Full Wipe and reflashing LOS17.1)