hello! First of all, I don't know if this topic is in this subforum or in another. If it's not here, I'm sorry. I've been trying to lock the bootloader for days before flashing the stock immediately. I try it from fasboot flashing lock and I get this: "failed (remote: 'invalid android images, skip locking') fastboot: error: command failed ". I have the r33 of Adb fasboot. I have restarted in fasboot and from there choose to restart in bootloader as I read in the forums and the same. what happens is that regardless of the ROM, root or mod to pass the safetynet. wallet and among other apps it detects them as root or similar....
juaki said:
hello! First of all, I don't know if this topic is in this subforum or in another. If it's not here, I'm sorry. I've been trying to lock the bootloader for days before flashing the stock immediately. I try it from fasboot flashing lock and I get this: "failed (remote: 'invalid android images, skip locking') fastboot: error: command failed ". I have the r33 of Adb fasboot. I have restarted in fasboot and from there choose to restart in bootloader as I read in the forums and the same. what happens is that regardless of the ROM, root or mod to pass the safetynet. wallet and among other apps it detects them as root or similar....
Click to expand...
Click to collapse
I assume you're trying to relock the bootloader? You cannot do this if any of the images have been modified, including Magisk patching. You have to flash back to stock first.
If you are trying to use payment apps, please see this thread.
yes of course. I have the stock of May. no root or patched init.boot or magisk. Totally stock except for the bootloader, which I intend to close since with no method or module I can get the wallet and other things to work for me. in wallet it says "this device does not meet the requirements". I don't know if a partition has been touched or something, because before I had the crDroid...
juaki said:
yes of course. I have the stock of May. no root or patched init.boot or magisk. Totally stock except for the bootloader, which I intend to close since with no method or module I can get the wallet and other things to work for me. in wallet it says "this device does not meet the requirements". I don't know if a partition has been touched or something, because before I had the crDroid...
Click to expand...
Click to collapse
I wonder why that is. I don't use wallet for payments but I did use it for Megadeth last year and I have my Covid info on it.
I see people having issues so I tried to add a few cards and had no issues, but I know there are people like you where it just doesn't work
HipKat said:
I wonder why that is. I don't use wallet for payments but I did use it for Megadeth last year and I have my Covid info on it.
I see people having issues so I tried to add a few cards and had no issues, but I know there are people like you where it just doesn't work
Click to expand...
Click to collapse
The fact is that it worked perfectly for me with root, stock ROM, safetynet 2.40 mod 1.2 module and Kira kernel. anyway...
juaki said:
The fact is that it worked perfectly for me with root, stock ROM, safetynet 2.40 mod 1.2 module and Kira kernel. anyway...
Click to expand...
Click to collapse
Um you stated no method or module worked for you. Now you are saying you had Wallet and "other things" working with root.
indeed. What I wanted to say is that it used to work for me, and suddenly it has stopped working for me in any ROM. with module or without it, with root or without it. and when flashing the stock in both slots and doing the relevant process, I can't block the bootloader. I honestly don't know what to do anymore. The phone passes the safetynet test.
juaki said:
indeed. What I wanted to say is that it used to work for me, and suddenly it has stopped working for me in any ROM. with module or without it, with root or without it. and when flashing the stock in both slots and doing the relevant process, I can't block the bootloader. I honestly don't know what to do anymore. The phone passes the safetynet test.
Click to expand...
Click to collapse
For locking the bootloader, you many want to try Android Flash Tool. Select "Force Flash all Partitions", "Lock Device" and "Wipe".
What @Lughnasadh has said is your best bet if you are not familiar manually wiping/modifying your phone. If you are not rooted and your phone system image is stock, then you need to lock your bootloader.
As Google has posted on their site a good number of times, you cannot use any of their security based services with an unlocked bootloader.
With root access, you can circumvent these restrictions. But without root access, you need to lock your bootloader. And when you attempt to do so, be sure that you don't utilize the newer versions of platform-tools as they seem to still cause problems.
juaki said:
The fact is that it worked perfectly for me with root, stock ROM, safetynet 2.40 mod 1.2 module and Kira kernel. anyway...
Click to expand...
Click to collapse
The newest working Safetynet Module is 2.4.0-MOD_1.2 by Kdrag0n
I uploaded it to my Mediafire
HipKat said:
The newest working Safetynet Module is 2.4.0-MOD_1.2 by Kdrag0n
I uploaded it to my Mediafire
Click to expand...
Click to collapse
The original USNF module was indeed developed by @kdrag0n but the working module is the fork by @Displax .
It is always best to link to the official source of the module, rather than re-uploading it, due to the potential of someone modifying it for malicious purpose.
Here is the official source
V0latyle said:
The original USNF module was indeed developed by @kdrag0n but the working module is the fork by @Displax .
It is always best to link to the official source of the module, rather than re-uploading it, due to the potential of someone modifying it for malicious purpose.
Here is the official source
Click to expand...
Click to collapse
Yeah if I could have found it but the version I have on my phone is the one I listed, or it's named wrong
HipKat said:
Yeah if I could have found it but the version I have on my phone is the one I listed, or it's named wrong
Click to expand...
Click to collapse
Apologies in advanced if I misunderstood...
the one you listed & the one on your phone is the same one in the Github V0latyle linked (from Displax's very own USNF fork Github) -- it is not named wrong, but if you look at your own screenshot from your own device; it displays "modded by Displax"
Again, sorry if I'm taking it wrong that you didn't get it, but the words "but" and "or it's named wrong" in your post led me under that impression you think you are under kdrag0n's main branch just by name itself....
simplepinoi177 said:
Apologies in advanced if I misunderstood...
the one you listed & the one on your phone is the same one in the Github V0latyle linked (from Displax's very own USNF fork Github) -- it is not named wrong, but if you look at your own screenshot from your own device; it displays "modded by Displax"
Again, sorry if I'm taking it wrong that you didn't get it, but the words "but" and "or it's named wrong" in your post led me under that impression you think you are under kdrag0n's main branch just by name itself....
Click to expand...
Click to collapse
You are correct, I did not notice the Modded by in the name and did think this was Drag0n's but it's all good. It's the one that works and that's the important thing
Related
BETA-SuperSU-v2.52.zip just gets things stuck at the boot animation. Is there any working method at this point?
xichael said:
BETA-SuperSU-v2.52.zip just gets things stuck at the boot animation. Is there any working method at this point?
Click to expand...
Click to collapse
before you install supersu please install a different kernel, i personally use the elemental x kernel.
if its bootlooping now, what you can do is too go back to recovery and restore (assuming you have already backup) otherwise just reinstall (re flash) the mra58N
hope its help, if you need further instruction do not hesitate to reply
Removed - wrong device... duh... I don't want to be responsible for bricking someone's phone.
Sorry - one of the perils of belonging to different device groups.
dahawthorne said:
Removed - wrong device... duh... I don't want to be responsible for bricking someone's phone.
Sorry - one of the perils of belonging to different device groups.
Click to expand...
Click to collapse
I know what you were trying to say, and you're wrong. We have hammerhead support.
---------- Post added at 04:46 PM ---------- Previous post was at 04:45 PM ----------
xichael;
http://forum.xda-developers.com/nexus-6/general/root-t3231211
Oh well, it's not the first time I've been wrong, so no worries on that score, but at least it's ended up with a positive result for the OP.
Actually I do have a hammerhead root as well
http://superuser.phh.me/nexus/hammerhead/MRA58N/
Take boot-su-eng.img fastboot flash it, install phh's Superuser from playstore, and you're rooted.
The proper post would rather be http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394 instead
Edit: Oh right I'm laggy as well.
phhusson said:
Actually I do have a hammerhead root as well
http://superuser.phh.me/nexus/hammerhead/MRA58N/
Take boot-su-eng.img fastboot flash it, install phh's Superuser from playstore, and you're rooted.
The proper post would rather be http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394 instead
Edit: Oh right I'm laggy as well.
Click to expand...
Click to collapse
This worked after the MRA58N update but one of my apps that requires root does not work.(it says I don't have root???)
I'm sure it is an issue with the app because root checker says it is rooted along with es file explorer and adaway.
Thanks
Well, this root is still in development. Which app is it?
Thanks phh. It's working so far.
I couldn't get this app to work: http://forum.xda-developers.com/android/apps-games/widget-toggle-cell-radio-5-0-xda-t2945397
But it then I read the fine print:
Requirements: When SELinux is set to enforcing: a superuser app with support for a SELinux context parameter (-cn). Currently, only SuperSU supports this parameter.
Click to expand...
Click to collapse
Any chance of this happening with your root?
Can you test http://phhusson.free.fr/temp/new-boot.img ? I have no sim in my N5. I just ignore the -cn parameter, that seems to do the trick.
Incredible. That solved it. I never expected such instant gratification. Thank you!
Do you have a thread I can watch for a stable release?
Good, thanks.
I'm not sure what you're asking: You want to have a thread as for when this SuperUser will be considered stable, or when I'll make a properly generated version?
For the first one, I don't have such a thread yet (I mean except for http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394 )
For the latter, I've already regenerated (same http://superuser.phh.me/nexus/hammerhead/MRA58N/ place)
So being someone who hasn't rooted or installed ROMs in a few years...is there a guide I can follow and then use these files? It seems that some of the tools are the same as they were a few years ago, but would rather not mess things up too much. On a Nexus 6P...so time to play with the 5.
Hi phhusson!
phhusson said:
Good, thanks.
I'm not sure what you're asking: You want to have a thread as for when this SuperUser will be considered stable, or when I'll make a properly generated version?
For the first one, I don't have such a thread yet (I mean except for http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394 )
For the latter, I've already regenerated (same http://superuser.phh.me/nexus/hammerhead/MRA58N/ place)
Click to expand...
Click to collapse
Would you mind to point out the differences of these images in short?
[ ] boot-su-eng.img
[ ] boot-su-power.img
[ ] boot-su-user.img
My guess is that there are differences in sepolicies and/or dm-verity handling... Correct?
Would help me/others to decide which one to take for testing :highfive:
Cheers,
scholbert
None of them has dm-verity disabled. I might consider adding a version for it.
boot-su-eng has su permissive
boot-su-power has all known sepolicy enabled: ie as soon as I test a new usage which doesn't have SELinux rules, I add the rules.
boot-su-user has only the known policies I consider safe
su-power and su-user's policies are really light at the moment, and I don't expect it to be usable at the moment. (but any help/bug reports on them are welcomed)
phhusson said:
Well, this root is still in development. Which app is it?
Click to expand...
Click to collapse
This one https://play.google.com/store/apps/details?id=aws.apps.wifiKeyRecovery&hl=en
DXM31 said:
This one https://play.google.com/store/apps/details?id=aws.apps.wifiKeyRecovery&hl=en
Click to expand...
Click to collapse
Works on latest version, can you redownload the boot.img?
phhusson said:
Works on latest version, can you redownload the boot.img?
Click to expand...
Click to collapse
It sure does thx
I just noticed where your from, so sorry for your losses in your beautiful city.
My wife and I got to visit there several years ago and we both had a wonderful time.
The people were very friendly and helpful towards two people who do not speak your language.
Our payers and thoughts are with the people of Paris.
Phusson, I got a bit confused. I was trying hard to root my hammerhead with MRA58N, but it keeps bootlooping. Which of the files you uploaded should I flash? And if all, in what order. Should I do it via ADB?
Mishung said:
Phusson, I got a bit confused. I was trying hard to root my hammerhead with MRA58N, but it keeps bootlooping. Which of the files you uploaded should I flash? And if all, in what order. Should I do it via ADB?
Click to expand...
Click to collapse
Flash again the original factory image, and then fastboot flash boot boot-su-eng.img
With boot-su-eng.img coming from http://superuser.phh.me/nexus/hammerhead/MRA58N/boot-su-eng.img
Then reboot
All in fastboot mode
Thanks to some questions and awnsers I was able to create the
rooted boot.img for our HTC Bolt devices.
This was tested on the HTC Bolt Software 1.17.651.11 Android N 7
How To: (downloads at bottom of page)
Connect Device to computer
Insure that usb debugging is on as well as OEM unlock is checked.
The device must be Boot-loader unlocked to do this!
place both the patched_boot.img and the magisk_cache.img in the same directory your fastboot files are setup at ( c:/android/sdk/fastboot or wherever you have it)
Boot the phone into Download mode. ( Power + VOL down)
Open up terminal on the computer and run both these commands:
fastboot devices
fastboot flash boot patched_boot.img
fastboot flash cache magisk_cache.img
followed by fastboot reboot
you'll need to head over to :
http://forum.xda-developers.com/htc-10/development/root-magisk-autoroot-magisk-phhs-t3507505
Grab the manager.apk and the super user apk to complete the setup.
Give these guys a thanks also for getting this going, gonna build a rom with debloat next and see if the twrp will flash it with this boot.img behind it.
shall see
Thanks to:
@OMJ Everything!
@topjohnwu magisk
@Captain_Throwback -twrp,root
@Chainfire - root
Downloads
Patched boot.img (For Magisk) - https://www.androidfilehost.com/?fid=601296195406528674
Cache img (For Magisk) - https://www.androidfilehost.com/?fid=601296195406528673
***********DevDigitel Custom Images************
Secure Boot Img: https://www.androidfilehost.com/?fid=457095661767122602
Unsecure Boot Img: https://www.androidfilehost.com/?fid=745425885120693359
Flashable ZIPS:
SuperSU:
https://www.androidfilehost.com/?fid=673368273298916495
Radio Fix Zip/FP Scanner Fix : https://www.androidfilehost.com/?fid=673368273298916521
Device will bootloop once, and when done will install su. Please be patient
Nice!
suprised that it went so smoothly, su being systemless is a little buggy here and there with Android N, but otherwise i was able to navigate the internals, remove the bloat, make some build prop edits and theyve stuck. so far so good.
Went ahead and tried to use flashify and flash the twrp image from other post. Flashed and was able to make a backup to sd only. I didn't flash or try to restore it yet but I did have to relock and restore 3x with the stock ruu after removing too much system and trying to flash xposed
thanks for this! was able to get root on mine as well.
any idea how to get S-OFF? looks like Sunshine isn't compatible with Magisk, probably should have done that first
S off
urbster1 said:
thanks for this! was able to get root on mine as well.
any idea how to get S-OFF? looks like Sunshine isn't compatible with Magisk, probably should have done that first
Click to expand...
Click to collapse
Not sure.. Probably gonna be some time with Android N.
I was able to change carrier types in Ui.
Got vzw 1x 3g 4G icons
Hot-spot mod
And a few other things working.
No radios to flash.. No kernels and I don't dev kernels.
So I don't need s-off really.. It's more so just having to re-lock
To go back to stock.
I just ordered a Bolt, can't wait to play
Screen shots
OMJ said:
I just ordered a Bolt, can't wait to play
Click to expand...
Click to collapse
Yey can't wait! It didn't want to be the only one working
On it!
Just curious about how you went about unlocking the bootloader? Tried using the HTC dev service but they don't seem to support the Bolt yet. Also, haven't had too much experience with the bootloader since I've mostly been on Samsung Verizon devices. lol...
zombie673 said:
Just curious about how you went about unlocking the bootloader? Tried using the HTC dev service but they don't seem to support the Bolt yet. Also, haven't had too much experience with the bootloader since I've mostly been on Samsung Verizon devices. lol...
Click to expand...
Click to collapse
it is supported, just choose "All other supported models" and follow the instructions
Restored boot and tried Sunshine but it failed. Hopefully S-OFF will come soon.
zombie673 said:
Just curious about how you went about unlocking the bootloader? Tried using the HTC dev service but they don't seem to support the Bolt yet. Also, haven't had too much experience with the bootloader since I've mostly been on Samsung Verizon devices. lol...
Click to expand...
Click to collapse
Use the other supported devices section at bottom.
Just follow the steps on htc dev.
Save the unlock.bin file HTC will email you. You need it Every time you need to lock/unlock. Without s-off (removing the 2nd lock that protects the radios)
* the phone has to be re-locked to be restored with the stock htc software "ruu's"
Htc ruu is a 1 click style restore program...similar to odin that Will run on the PC and restore phone to stock.
It also comes in a update.zip format that can be flashed with the stock Signed recovery only via sd card slot.
Twrp is currently working on bolt / but has limitations because Its not 100%
More screenshots
Random stuff that can be unlocked hidden in the phone.
urbster1 said:
it is supported, just choose "All other supported models" and follow the instructions
Restored boot and tried Sunshine but it failed. Hopefully S-OFF will come soon.
Click to expand...
Click to collapse
@jcase has said Sunshine will support the Bolt but Android 7.0 must be supported 1st...
OMJ said:
@jcase has said Sunshine will support the Bolt but Android 7.0 must be supported 1st...
Click to expand...
Click to collapse
We are working on 7.0 support, we will have to build a device profile and test after 7.0 works. Probably just need to dump some data off a bolt, but may need to buy/borrow one.
jcase said:
We are working on 7.0 support, we will have to build a device profile and test after 7.0 works. Probably just need to dump some data off a bolt, but may need to buy/borrow one.
Click to expand...
Click to collapse
@jcase let me know if you need any more partitions, or anything else dumped... Worse case I can send you mine.
Full root with Su support in other thread
This will no longer be maintained. Links will still stay good for those wishing to use this. Please go to the magisk forum page for related questions to his root tools.
Thank you for the support!
Team DevDigitel said:
Full root with Su support in other thread
This will no longer be maintained. Links will still stay good for those wishing to use this. Please go to the magisk forum page for related questions to his root tools.
Thank you for the support!
Click to expand...
Click to collapse
I actually just switched to this method after s-off, due to safetynet failing after detecting a unlocked bootloader...magisk can hide the detection
I've done some research on safety net. What instances are people needing to pass the safety net check? Google api isn't stopping any of my processes or apps. Even banking etc. Is this directed towards things like android pay?
Team DevDigitel said:
I've done some research on safety net. What instances are people needing to pass the safety net check? Google api isn't stopping any of my processes or apps. Even banking etc. Is this directed towards things like android pay?
Click to expand...
Click to collapse
yep...AP is my only goal
there's a kernel patch to bypass detection but I don't know squat about kernel modding
Running stock ROM not rooted, getting this error? .. bootloader is unlocked though
Google has Google pay check for an unlocked bootloader. If you are unlocked it will fail, you do not have to be rooted just bootloader unlocked for Safteynet to fail. You might as well install Magisk and let it hide that you are unlocked and rooted if you wish to use Google Pay. If you do not want to root, then just relock the bootloader, JUST MAKE SURE YOU HAVE THE STOCK RECOVERY AND NO CUSTOM RECOVERY INSTALLED. Otherwise you will brick your device. Also, be aware that relocking your bootloader will wipe all internal data off the phone so backup any photos, files, anything of importance before relocking bootloader.
Eric214 said:
Google has Google pay check for an unlocked bootloader. If you are unlocked it will fail, you do not have to be rooted just bootloader unlocked for Safteynet to fail. You might as well install Magisk and let it hide that you are unlocked and rooted if you wish to use Google Pay. If you do not want to root, then just relock the bootloader, JUST MAKE SURE YOU HAVE THE STOCK RECOVERY AND NO CUSTOM RECOVERY INSTALLED. Otherwise you will brick your device. Also, be aware that relocking your bootloader will wipe all internal data off the phone so backup any photos, files, anything of importance before relocking bootloader.
Click to expand...
Click to collapse
Magisk hide won't hide it. Alot of apps not able to avail of the hide function.
hallo dare said:
Magisk hide won't hide it. Alot of apps not able to avail of the hide function.
Click to expand...
Click to collapse
Strange... on my OP 6 with unlocked bootloader and Magisk root, Google Pay runs fine. And even Magisk Hide was not enabled for Google Pay (now it is).
hallo dare said:
Magisk hide won't hide it. Alot of apps not able to avail of the hide function.
Click to expand...
Click to collapse
What are you talking about? I've been using Magisk with passing safetynet since it came out a couple years ago. I just used Google Pay times today with no issues.
The issue is Google will fail Safetynet if you just have an unlocked bootloader and no magisk installed to pass the safetynet checks.
Eric214 said:
What are you talking about? I've been using Magisk with passing safetynet since it came out a couple years ago. I just used Google Pay times today with no issues.
The issue is Google will fail Safetynet if you just have an unlocked bootloader and no magisk installed to pass the safetynet checks.
Click to expand...
Click to collapse
What I'm talking about is what I'm experiencing. I've magisk installed, Google Pay is ticket to magisk hide, along with other apps, and they all detect root
hallo dare said:
Magisk hide won't hide it. Alot of apps not able to avail of the hide function.
Click to expand...
Click to collapse
please dont give users the wrong impression
Magisk DOES hide it.
i have an unlocked bootloader, TWRP, MAGISK, and a custom kernel installed
and ive been using google pay for the past week without issues.
Why would I give users wrong impression? It's happening to me!!! Just because it doesn't happen to you or others then it cannot be true?
I've also an unlocked bootloader, TWRP and Magisk installed and Magisk is not hiding specific apps. Simple as that.
hallo dare said:
What I'm talking about is what I'm experiencing. I've magisk installed, Google Pay is ticket to magisk hide, along with other apps, and they all detect root
Click to expand...
Click to collapse
Then Magisk must not be installed properly. You must have done something wrong is all I can think of. I use Google pay 2-5 times a day without issue and on the OnePlus 6 since launch, zero issues.
Eric214 said:
Then Magisk must not be installed properly. You must have done something wrong is all I can think of. I use Google pay 2-5 times a day without issue and on the OnePlus 6 since launch, zero issues.
Click to expand...
Click to collapse
I've gone and done a complete format and re-installation of everything and the same issue is present.
hallo dare said:
I've gone and done a complete format and re-installation of everything and the same issue is present.
Click to expand...
Click to collapse
Maybe delete the Magisk APK/zip you have and download a fresh copy then.
Eric214 said:
Maybe delete the Magisk APK/zip you have and download a fresh copy then.
Click to expand...
Click to collapse
Done that, but made no difference. Just reading on another thread that it appears to be an issue for many.
Magisk Hide works fine out of the box (no alterations) with Google Pay for me.
Historically, when it fails it's because Magisk is out of date.
hallo dare, if you want help, post your Magisk Manager's landing page, then another of your test results. Past that, you should head over to the Magisk XDA thread.
Edit:
I guess I forgot to mention I am on the BETA channel - so not exactly without alteration.
Orito said:
Magisk Hide works fine out of the box (no alterations) with Google Pay for me.
Historically, when it fails it's because Magisk is out of date.
hallo dare, if you want help, post your Magisk Manager's landing page, then another of your test results. Past that, you should head over to the Magisk XDA thread.
Edit:
I guess I forgot to mention I am on the BETA channel - so not exactly without alteration.
Click to expand...
Click to collapse
Thanks Orito,
Yeah I'll do just that. Can you please post the magisk you flashed and I'll try it please.
I flashed the 16.4.
I'm running 16.42. In Magisk.
Open Magisk Manager.
Menu.
Settings.
Update Channel -> Beta
Check for Updates -> Enabled
Close Magisk Manager completely.
Reopen.
Orito said:
I'm running 16.42. In Magisk.
Open Magisk Manager.
Menu.
Settings.
Update Channel -> Beta
Check for Updates -> Enabled
Close Magisk Manager completely.
Reopen.
Click to expand...
Click to collapse
Exactly what I've been doing. Thanks
GrapheneOS for Pixel 4a Sunfish
This is the updated March 2021 security patch
OTA update, flash through recovery. https://releases.grapheneos.org/sunfish-ota_update-2021.03.02.10.zip
Full update, double click on flash-all in bootloader mode. https://releases.grapheneos.org/sunfish-factory-2021.03.02.10.zip
Warning, full update will wipe device unless you edit the flash-all file with notepad and remove the -w before the update file.
Graphene does not and will never include gapps and can not be installed on this rom.
MicroG is also not included but can be added separately.
No signature spoofing without rebuilding the rom and that would defeat the security/privacy of this rom.
Awesome, thank you very much.
TheSayaMan said:
GrapheneOS for Pixel 4a Sunfish
https://releases.grapheneos.org/sunfish-factory-2021.01.05.03.zip
Simple install. Extract link to your ADB tools folder. Double click on flash-all and let the flashing do the work on it's own.
This is the updated January 2021 security patch
Graphene does not and will never include gapps and can not be installed on this rom.
MicroG is also not included but can be added separately.
Signature spoofing is also not supported.
Click to expand...
Click to collapse
Is there a good guide that explains how to add signature spoofing. It all seems to be outdated info
kev15058 said:
Is there a good guide that explains how to add signature spoofing. It all seems to be outdated info
Click to expand...
Click to collapse
A patch for signature spoofing on Android 11 only works from Magisk if the ROM's services.jar already contains classes.dex which this does not. So as stated in the OP, signature spoofing is not supported with this ROM. This ROM could be rebuilt to allow such a thing but that would defeat the purpose of the ROM.
GrapheneOS is designed for the privacy/security users. So you won't ever see Google stuff in GrapheneOS unless someone does what @TheSayaMan said, but then that defeats the purpose of the ROMs focus of privacy/security.
I can recommend CalyxOS too. Its awesome. Both projects are awesome.
kev15058 said:
Is there a good guide that explains how to add signature spoofing. It all seems to be outdated info
Click to expand...
Click to collapse
Check this out : https://www.paulligocki.com/installing-graphineos-on-the-google-pixel-4a/
Moto_Fan said:
Check this out : https://www.paulligocki.com/installing-graphineos-on-the-google-pixel-4a/
Click to expand...
Click to collapse
This will not enable signature spoofing and also I don't recommend as stated on this link to lock the bootloader. You should never ever lock the bootloader on a custom rom. You can not flash software firmware on a locked bootloader and if you have a issue unlocking it afterwards then your screwed.
Updated February 2021 patch in OP.
TheSayaMan said:
This will not enable signature spoofing and also I don't recommend as stated on this link to lock the bootloader. You should never ever lock the bootloader on a custom rom. You can not flash software firmware on a locked bootloader and if you have a issue unlocking it afterwards then your screwed.
Click to expand...
Click to collapse
If you check out the Developer site, they tell you to RELOCK BOOTLOADER, these are the same instructions, much more straight forward.
*remember*
Don't forget to fact check, so I avoid sticking in .....
Edit
ATTACHED FOOT
Moto_Fan said:
If you check out the Developer site, they tell you to RELOCK BOOTLOADER, these are the same instructions, much more straight forward.
*remember*
Don't forget to fact check, so I avoid sticking in .....
Edit
ATTACHED FOOT
Click to expand...
Click to collapse
And...
My mans above you gives you a concrete reason to not listen to those knuckle dragging idiots...
Because... Unlike them... We have to listen to how you've destroyed your device by listening to the crayon eating morons...
If you ain't stock... Don't lock the damn bootloader
Edit: I will eat my words if Graphene or Calyx buys you a device for following their instructions
rignfool said:
And...
My mans above you gives you a concrete reason to not listen to those knuckle dragging idiots...
Because... Unlike them... We have to listen to how you've destroyed your device by listening to the crayon eating morons...
If you ain't stock... Don't lock the damn bootloader
Edit: I will eat my words if Graphene or Calyx buys you a device for following their instructions
Click to expand...
Click to collapse
Its is basically a stock ROM, cleaned up code, mods to harden security, name of the file is even stock bud.
I think imma listen to the morons... I got (2) sunfishes, let's call it a sacrifice on me....
TheSayaMan said:
This will not enable signature spoofing and also I don't recommend as stated on this link to lock the bootloader. You should never ever lock the bootloader on a custom rom. You can not flash software firmware on a locked bootloader and if you have a issue unlocking it afterwards then your screwed.
Click to expand...
Click to collapse
#2 you never flash custom or stock over a LOCKED BL. FASTBOOT will NOT allow it...
*Edit*
When u say "This won't allow Signature Spoofing," can you be a little more specific? What exactly is "This"?
I followed the instructions to the letter on my Windows 10 laptop. This is not the entire process, but did unlock the bootloader, flashed Grapheneos. Then locked the bootloader before rebooting and setting up the OS. I can say I am not 100% ready for a no Google os, but I will investigate more for alternative apps to meet my needs. I followed the same instructions to go back to stock (factory image) both unlocking the bootloader, flashing, and then re-locking bootloader before setting up factory os. This is not an endorsement of the process, and there is always issues that can come up with flashing. Use at your own risk
bill_in_mtl said:
I followed the instructions to the letter on my Windows 10 laptop. This is not the entire process, but did unlock the bootloader, flashed Grapheneos. Then locked the bootloader before rebooting and setting up the OS. I can say I am not 100% ready for a no Google os, but I will investigate more for alternative apps to meet my needs. I followed the same instructions to go back to stock (factory image) both unlocking the bootloader, flashing, and then re-locking bootloader before setting up factory os. This is not an endorsement of the process, and there is always issues that can come up with flashing. Use at your own risk
Click to expand...
Click to collapse
Yea, i hear ya about the NO GAPPS, i been using F-Droid which has a lot of alternatives. Everything flash back to stock ok?
Moto_Fan said:
Yea, i hear ya about the NO GAPPS, i been using F-Droid which has a lot of alternatives. Everything flash back to stock ok?
Click to expand...
Click to collapse
Yep, flashed back without issue. Back on stock with a locked bootloader. Going to spend some time going through all the non-google options to see if I can give it a real go
thanks
I'm having trouble setting up a APN with this OS. Does anyone know how to allow user access to APN Setting in Graphene?
Moto_Fan said:
Its is basically a stock ROM, cleaned up code, mods to harden security, name of the file is even stock bud.
I think imma listen to the morons... I got (2) sunfishes, let's call it a sacrifice on me....
Click to expand...
Click to collapse
All good and dandy know it all. Now that you locked the bootloader, try flashing back to stock android with the google factory images. You can't do it!!!!!!!!!!
Moto_Fan said:
#2 you never flash custom or stock over a LOCKED BL. FASTBOOT will NOT allow it...
*Edit*
When u say "This won't allow Signature Spoofing," can you be a little more specific? What exactly is "This"?
Click to expand...
Click to collapse
On Android, all applications are signed (usually using SHA1 with RSA). The certificate/key-combinations used to sign apps are self-signed. This means there is no PKI / certificate authority to verify a key to be owned by a person/company/entity. Thus everyone can come up with a key that has a equally valid Google certificate as keys used by Google to publish their apps.
TheSayaMan said:
All good and dandy know it all. Now that you locked the bootloader, try flashing back to stock android with the google factory images. You can't do it!!!!!!!!!!
Click to expand...
Click to collapse
Exactly, in this case you would have to fastboot oem unlocking to unluck bootloader before fastboot flashing Factory Images, obviously...
Hello I have a question. I have a OnePlus 7 Pro rooted with Magisk and of course the Dasher app wont work properly. Could I simply flash back and forth from a Magisk boot partition to a non rooted boot partition in order for Dasher to work? I wanted to get some insight before I start flashing things..
Thank you
ben_deez said:
Hello I have a question. I have a OnePlus 7 Pro rooted with Magisk and of course the Dasher app wont work properly. Could I simply flash back and forth from a Magisk boot partition to a non rooted boot partition in order for Dasher to work? I wanted to get some insight before I start flashing things..
Thank you
Click to expand...
Click to collapse
Does the Door Dash app detect root? Chances are you just need to make sure you're passing Play Integrity BASIC and DEVICE verdicts. More information here
It's generally inadvisable to try swapping back and forth between the slots on A/B devices. They aren't meant to be swapped at will; the purpose of A/B slots is for seamless system updates, and you could very well render both slots unbootable by attempting to do so.
So I installed the above Integrity Checker and I failed all three. What if I leave the other slot alone and flash back and forth TWRP backups of the boot partition on my current slot? What would you recommend at this point?
Thanks again
V0latyle said:
Does the Door Dash app detect root? Chances are you just need to make sure you're passing Play Integrity BASIC and DEVICE verdicts. More information here
It's generally inadvisable to try swapping back and forth between the slots on A/B devices. They aren't meant to be swapped at will; the purpose of A/B slots is for seamless system updates, and you could very well render both slots unbootable by attempting to do so.
Click to expand...
Click to collapse
Are you a Marine? Me too. Former Marine that is. Ooh-Rah.... I understand if you need to delete this reply since it is off topic.. But I had to shout out.
ben_deez said:
So I installed the above Integrity Checker and I failed all three. What if I leave the other slot alone and flash back and forth TWRP backups of the boot partition on my current slot? What would you recommend at this point?
Thanks again
Click to expand...
Click to collapse
Read the post, please. The answers to your questions are there. Changing your boot image won't matter because your bootloader is unlocked, and that alone means you're going to fail all Play Integrity verdicts without using USNF.
ben_deez said:
Are you a Marine? Me too. Former Marine that is. Ooh-Rah.... I understand if you need to delete this reply since it is off topic.. But I had to shout out.
Click to expand...
Click to collapse
There's no such thing as a former Marine, you should know better, knucklehead! 2007-2016, 2844/2841/2862/8411
We have several other mods who are Marines: @Az Biker, @Clark Joseph Kent for example, we even have a few veterans from other countries.
V0latyle said:
Read the post, please. The answers to your questions are there. Changing your boot image won't matter because your bootloader is unlocked, and that alone means you're going to fail all Play Integrity verdicts without using USNF.
There's no such thing as a former Marine, you should know better, knucklehead! 2007-2016, 2844/2841/2862/8411
We have several other mods who are Marines: @Az Biker, @Clark Joseph Kent for example, we even have a few veterans from other countries.
Click to expand...
Click to collapse
We were told to use the term Former Marine in bootcamp... and never use the term "X Marine" Former means "The same but at a different time" 1993-1997 1391... I'm from the "old Corps"....
But yes I did read everything on the post.. Good info thank you. I'm just trying to find a solution to this without having to lock the bootloader.
ben_deez said:
We were told to use the term Former Marine in bootcamp... and never use the term "X Marine" Former means "The same but at a different time" 1993-1997 1391... I'm from the "old Corps"....
Click to expand...
Click to collapse
One of my younger brothers was a bulk fuel specialist in Okinawa, he just got out a few months ago
ben_deez said:
But yes I did read everything on the post.. Good info thank you. I'm just trying to find a solution to this without having to lock the bootloader.
Click to expand...
Click to collapse
Well, as mentioned in that thread, you should be able to pass BASIC and DEVICE integrity by installing USNF 2.4.0, which forces Play Integrity to use basic evaluation instead of hardware methods. Don't worry about STRONG integrity, I am not aware of any apps that require that attestation. The vast majority of Play Store apps only use the DEVICE label as this indicates that the device (and software) has been tested via Android CTS; those which require additional security use the BASIC label as well. There are a few apps that use their own root detection techniques such as the presence of a SU binary or the Magisk app, but these are few and far between, and I highly doubt that the Dash app would be one of these. I would think it's a safe assumption that it simply uses the DEVICE label, maybe the BASIC label as well. Since you were failing all 3 labels, this would make sense.
Install the Magisk module mentioned in the thread and reboot, then use Integrity Checker to verify you're passing BASIC and DEVICE labels. If Dash still doesn't work, force stop and clear app data.
I installed USNF 2.4.0 rebooted and still failed all 3 integrity checks including BASIC and DEVICE. The Dasher app will install and seems to work fine until I select "Go Dash" to start accepting deliveries. It just loops back to the sign in page. I've cleared the data and cache and uninstalled and installed many times.... I even tried using older versions of the app with no success. I've tried using Magisk Hide and Zygist to no avail. appreciate you taking the time for my questions.. Much appreciation
ben_deez said:
I installed USNF 2.4.0 rebooted and still failed all 3 integrity checks including BASIC and DEVICE. The Dasher app will install and seems to work fine until I select "Go Dash" to start accepting deliveries. It just loops back to the sign in page. I've cleared the data and cache and uninstalled and installed many times.... I even tried using older versions of the app with no success. I've tried using Magisk Hide and Zygist to no avail. appreciate you taking the time for my questions.. Much appreciation
Click to expand...
Click to collapse
What version of Magisk are you using?
I believe that since you're using a Chinese device you may still need to use MagiskHide Props Config to spoof a valid fingerprint.
V0latyle said:
What version of Magisk are you using?
I believe that since you're using a Chinese device you may still need to use MagiskHide Props Config to spoof a valid fingerprint.
Click to expand...
Click to collapse
25.2
ben_deez said:
25.2
Click to expand...
Click to collapse
I installed MagiskHide Props Config but I'm not sure which fingerprint to use.. Many selections... I selected the TMobile fingerprint since I have a GM1915 . I'm also still on 10.0.3.GM21AA So far it hasn't fixed the problem.
What about a Dual Boot system? Is it possible to have dual boot systems with one rooted and one thats not rooted? It still wouldn't hide that the bootloader is unlocked tho right? Because I got the app to work on my old LG V20. Apparently once the bootloader was unlocked on the v20 it couldn't ever be locked again because of using Dirty Santa to unlock it. My v20 was vs995 and I converted it to un996.. all I did to make the app work was do a factory reset. I didn't have to flash the original vs995 firmware. But I think the bootloader should still be unlocked on the v20 even after the factory reset... The app didn't work on my OnePlus 7 pro even after I did a factory reset. frustrating.
V0latyle said:
One of my younger brothers was a bulk fuel specialist in Okinawa, he just got out a few months ago
No Kidding? How cool is that? I was at Camp Hansen 9th ESB Bulk Fuel Co.. Before that I was Station Fuels at MCAS El Toro in 1996 running the Hot Pits. Small world
Click to expand...
Click to collapse