Related
So i recently updated to the new mhc19l version on my nexus 6p (this is not android N, just the latest android update for the 6p). I did it via the flashfire method following this youtube video: https://www.youtube.com/watch?v=cvs0JQswTWw&feature=youtu.be
I dont have multirom so i didnt do the stuff it mentioned about that. At first I thought I was successful and everything was working great. I reflashed xposed to the latest version, and updated my elemental X kernal too.
But now when I do anything with the camera the phone gets really weird. Post reboot the camera preview will work only once. If I take a photo it crashes. And every time I try to do anything with the camera involved the thing will crash and not even load preview anymore. That includes 3rd party apps like snap chat. Also I can't edit quick setting tiles in system ui as it tells me system ui tuner has crashed, but that i can live with. The camera issues I can not live with.
None of that happens with my rooted 6p on the same build. I think you need to look at xposed, the kernel changes and all the other jiggerypokery you've done. I'd do begin by reflashing the factory image and do this manually either using Heisenberg's extremely clear guide, or by the flash-all.bat command that google supplies in the factory build. Then you can check camera, flash recovery (again, using Heisenberg's guide, it takes but a couple of commands), then root, add xposed, kernels and all that special sauce. Do it step by step, then you'll know when something goes wrong and only have to fix that.
Thank you for your help. I'll check that out. Do you think it may be because I updated from a pretty old build? (808L) I skipped a few updates and went right to the latest one, could that cause any problems?
Not really. I think it's because you've done too much using a tool and without checking things after each step. Stop using tools like flashfire when you don't understand what they do and get yourself up to speed with using the commands. After that, you'll spot where things have gone wrong and be able to fix or troubleshoot it within the community. No one can help you when it's an issue that could caused by one or more of a hundred things you've tinkered with.
It's not hard and worth the little bit of busy work and brain thought. You'll enjoy it!
Yea I like to tinker and stuff. It's just the customizations with dashclock and stuff that I don't want to lose. But I did app backups so hopefully I won't.
Something probably went wrong during the flash process. I highly doubt xposed or kernel modifications are to blame. I keep 12 xposed modules running at all times with kylo kernel which I have heavily modified with EX kernel app. Read Heisenberg's guide and learn to flash images properly and you should be good to go.
Before I do any reflashing today can anyone do me a favour and upload their camera APK?
Im just hoping it has something to do with that. Last ditch effort.
And thanks for the help guys
So i gotta ask. Using flashire only is it possible to lock the bootloader and flash small incremental updates without a problem? Its a bit sad to have a unlocked bootloader...
Sent from my Nexus 6P using Tapatalk
and313 said:
So i gotta ask. Using flashire only is it possible to lock the bootloader and flash small incremental updates without a problem? Its a bit sad to have a unlocked bootloader...
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
You can't flash anything with a locked bl. Locking the BL is nothing but trouble if you like to tinker.
Sent from my Nexus 6P using Tapatalk
and313 said:
So i gotta ask. Using flashire only is it possible to lock the bootloader and flash small incremental updates without a problem? Its a bit sad to have a unlocked bootloader...
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Locking the bootloader is nothing but trouble. You know what's sadder than having an unlocked bootloader? Having a bricked phone because an OTA failed and your bootloader is locked. If that happens there's no way to save it.
dirtyuzbek said:
Before I do any reflashing today can anyone do me a favour and upload their camera APK?
Im just hoping it has something to do with that. Last ditch effort.
And thanks for the help guys
Click to expand...
Click to collapse
What method did you use to update? Did you use an OTA zip? Or factory images? I'd Is there a reason you used Flashfire instead of updating the proper way?
Any Advice ?
Heisenberg said:
Locking the bootloader is nothing but trouble. You know what's sadder than having an unlocked bootloader? Having a bricked phone because an OTA failed and your bootloader is locked. If that happens there's no way to save it.
What method did you use to update? Did you use an OTA zip? Or factory images? I'd Is there a reason you used Flashfire instead of updating the proper way?
Click to expand...
Click to collapse
Hello you seem very knowledgeable on the subject. I just picked up a 6P and was wondering how does encryption affect things such as TWRP and root. Do you advise to disable encryption on the device for ease-of-use in TWRP and root.
naruto.ninjakid said:
Hello you seem very knowledgeable on the subject. I just picked up a 6P and was wondering how does encryption affect things such as TWRP and root. Do you advise to disable encryption on the device for ease-of-use in TWRP and root.
Click to expand...
Click to collapse
Look at my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Deception isn't necessary anymore, as long as you use the latest TWRP you should have no problems.
did it flash the vendor?
Heisenberg said:
Locking the bootloader is nothing but trouble. You know what's sadder than having an unlocked bootloader? Having a bricked phone because an OTA failed and your bootloader is locked. If that happens there's no way to save it.
What method did you use to update? Did you use an OTA zip? Or factory images? I'd Is there a reason you used Flashfire instead of updating the proper way?
Click to expand...
Click to collapse
Wait.. If the bootloader is locked and a ota fails you cant oem unlock it?
Sent from my Nexus 6P using Tapatalk
and313 said:
Wait.. If the bootloader is locked and a ota fails you cant oem unlock it?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
No, because if the OTA fails you won't have access to the option in Developer Options to enable OEM unlocking. Trust me, you want to have that bootloader unlocked. You don't wanna end up like the other guys who had to send their phone back for repair because they locked it.
Heisenberg said:
No, because if the OTA fails you won't have access to the option in Developer Options to enable OEM unlocking. Trust me, you want to have that bootloader unlocked. You don't wanna end up like the other guys who had to send their phone back for repair because they locked it.
Click to expand...
Click to collapse
Right... I did not think that the first step (enable bootloader unlock from dev options) is actually necessary.
Sent from my Nexus 6P using Tapatalk
Its been reported that merely having an unlocked bootloader now trips safetynet. Google has officially turned their backs on developers and enthusiasts.
I never had a problem with xposed or magisk tripping safetynet; but an unlocked bootloader is by no means a security risk. So I'm not happy having to choose between snapchat and an unlocked bootloader.
Sources: https://www.reddit.com/r/Android/comments/587ss9/psa_android_safetynet_now_tripped_by_unlocking/
https://www.reddit.com/r/Nexus6P/comments/586bq7/android_pay_stopped_working_on_nonrooted_device/
Discuss.
Well RIP AP....
Pixel and now this, I guess Google is becoming Apple 2.0
can confirm, I have unrooted stock 7.0 as my primary on multirom and is tripping safetynet, no more AP for me I guess since I'm NOT locking the bootloader, nice play Google
Sent from my Nexus 6 using Tapatalk
IIRC chainfire DID warn us about this..saying if we keep trying to hide root, they'll keep trying to make it harder for us to do so.
Doing it to the pixel? Fine..but to a nexus phone? Kinda murders the whole selling point of Nexus.
Either way elgoog has been making some really odd decisions this past month or so.
I have an unlocked bootloader with everything stock and no root and I got past safety net for Pokemon Go.
biggiesmalls657 said:
I have an unlocked bootloader with everything stock and no root and I got past safety net for Pokemon Go.
Click to expand...
Click to collapse
Last I heard pokemon go isn't working with safetynet properly right now. Download SafetyNet Helper Sample from the PlayStore, it'll tell you whether you pass or not.
geokhentix said:
Last I heard pokemon go isn't working with safetynet properly right now. Download SafetyNet Helper Sample from the PlayStore, it'll tell you whether you pass or not.
Click to expand...
Click to collapse
Well I guess that a smartphone isn't for me, I'm gonna get a dumb phone again. Google can suck it. This is so ridiculous.
geokhentix said:
IIRC chainfire DID warn us about this..saying if we keep trying to hide root, they'll keep trying to make it harder for us to do so.
Doing it to the pixel? Fine..but to a nexus phone? Kinda murders the whole selling point of Nexus.
Either way elgoog has been making some really odd decisions this past month or so.
Click to expand...
Click to collapse
The only pixel that is locked is the Verizon version
holeindalip said:
The only pixel that is locked is the Verizon version
Click to expand...
Click to collapse
Yeah, that one isn't a part of this as its not unlockable. I'm talking about the Google Pixel.
This f's people who just want to install the latest factory image too; non power users who don't root and just want the latest OS..considering you need an unlocked boot loader to flash the images.
geokhentix said:
Yeah, that one isn't a part of this as its not unlockable. I'm talking about the Google Pixel.
This f's people who just want to install the latest factory image too; non power users who don't root and just want the latest OS..considering you need an unlocked boot loader to flash the images.
Click to expand...
Click to collapse
Not if you side load the latest ota files posted the same day:good:
By the way, does re-locking bootloader wipe data or internal? Factory image page says that "Locking bootloader will wipe the data on some devices. ".
Pretty sure on the n6, we wipe everything on both unlock & relock.
I'm planning on getting a new Nexus 6. Is it not the right time? I'm afraid this issue will make me unable to customize my new phone.
jesuajovan said:
I'm planning on getting a new Nexus 6. Is it not the right time? I'm afraid this issue will make me unable to customize my new phone.
Click to expand...
Click to collapse
You can still customize. You just can't do crap that you probably shouldn't be worrying about anyway. Android pay is a sham, since your credit card has an RF chip in it that works on the same scanner... but ONE FEWER companies get to track all your purchases when you use it since it leaves google out of the loop.
Indeed; also as long as you log into Snapchat once before you install root, it seems to continue to work after root / magisk installation.
I'm on 7.0 stock, rooted and unlocked bootloader and snapchat works fine.
pharpe said:
I'm on 7.0 stock, rooted and unlocked bootloader and snapchat works fine.
Click to expand...
Click to collapse
I just want to say that Snapchat is one of the worst coded apps ever
For Snapchat to work, you have to login before rooting your device, just don't log out lol
holeindalip said:
I just want to say that Snapchat is one of the worst coded apps ever
Click to expand...
Click to collapse
Amen.
I wonder what the hook is that it uses to check if the bootloader is locked...? It *must* go through the kernel, so maybe this is as simple as telling the kernel to LIE about it.
Well, that is simple conceptually, but not necessarily *easy* to implement.
Hello, I just installed TRWP and custom firmware, so my knox obviously is broken. I was wondering is there a way to make samsung pay work yet? Or maybe Android pay? I really liked nfc payments.
If you have a gear watch you may be able to sideload an older version of SPay onto each and have a working SPay on your watch.
Not sure if that technique works for this device or only non Samsung devices though...
But otherwise, no you won't have working SPay on your 0x1 device. Android Pay probably, yes.
Magisk could be working I guess
Gesendet von meinem LG-D802 mit Tapatalk
murok9042 said:
Magisk could be working I guess
Gesendet von meinem LG-D802 mit Tapatalk
Click to expand...
Click to collapse
Can you explain please? Is there a special magisk module for nfc payments?
kazzaqov said:
Can you explain please? Is there a special magisk module for nfc payments?
Click to expand...
Click to collapse
The way Android Pay works is by using a check called SafetyNet. Magisk fools the system with root by being a systemless root so nothing is tampered with, and in a nutshell, SafetyNet passes its checks and such Android Pay works.
Samsung Pay uses a different set of checks which fail majority of the time. There's been a few instances where people have been able to use Samsung Pay with the use of Magisk but is patched rather quickly.
TehPirate_ said:
Samsung Pay uses a different set of checks which fail majority of the time. There's been a few instances where people have been able to use Samsung Pay with the use of Magisk but is patched rather quickly.
Click to expand...
Click to collapse
Samsung Pay stores info in KNOX, so blowing your e-fuse kills Samsung Pay for the life of the device. Doubt there's a way around it.
Can i still usee samsung pay with my rooted s8
will there be any way i can still use samsung pay with my rooted s8 plus
luke1517 said:
will there be any way i can still use samsung pay with my rooted s8 plus
Click to expand...
Click to collapse
*Face palm* >_<
luke1517 said:
will there be any way i can still use samsung pay with my rooted s8 plus
Click to expand...
Click to collapse
Nope
I know this is an old thread but don't want to start a new just for an update.
Still not possible to get it to work with a rooted tripped phone?
Coming from nexus, first thing I did was root and make a nandroid...
Also flashing stock and locking doesn't revert this? How does this fuse work? Is it hardware or how come you can't just flash the original?
Bresch said:
I know this is an old thread but don't want to start a new just for an update.
Still not possible to get it to work with a rooted tripped phone?
Coming from nexus, first thing I did was root and make a nandroid...
Also flashing stock and locking doesn't revert this? How does this fuse work? Is it hardware or how come you can't just flash the original?
Click to expand...
Click to collapse
It's a fuse located on mainboard which is being "blown" after unlocking the bootloader / rooting. So there's no way to revert this unless you change the mobo on it.... Which I doubt ?
With Magisk, Android Pay is working flawlessly. I'm using it all the time on Note8 port.
jonny908 said:
It's a fuse located on mainboard which is being "blown" after unlocking the bootloader / rooting. So there's no way to revert this unless you change the mobo on it.... Which I doubt
With Magisk, Android Pay is working flawlessly. I'm using it all the time on Note8 port.
Click to expand...
Click to collapse
Ah, thought it wasn't a hardware thing and just code.
How are you getting that to work? I have magisk 15.2 on the s8+ and hidden from all the apps i can think of in magisk and it still tells me access denied blabla
Bresch said:
Ah, thought it wasn't a hardware thing and just code.
How are you getting that to work? I have magisk 15.2 on the s8+ and hidden from all the apps i can think of in magisk and it still tells me access denied blabla
Click to expand...
Click to collapse
It just works... Using 7.1.1 rom.
Bresch said:
I know this is an old thread but don't want to start a new just for an update.
Still not possible to get it to work with a rooted tripped phone?
Coming from nexus, first thing I did was root and make a nandroid...
Also flashing stock and locking doesn't revert this? How does this fuse work? Is it hardware or how come you can't just flash the original?
Click to expand...
Click to collapse
Nope and never will work. It's a hardware efuse on the main board of the phone. It's literally trips and burns out. You can't flash stock or anything to revert it.
The only way you can revert it is to buy a new motherboard.
Samsung Pay
callumbr1 said:
Nope and never will work. It's a hardware efuse on the main board of the phone. It's literally trips and burns out. You can't flash stock or anything to revert it.
The only way you can revert it is to buy a new motherboard.
Click to expand...
Click to collapse
I just rooted my S8+ with Party Cyborg it is a 955U1 and I did not like the fact it could not use health or Samsung pay with my S3 so I put back the orig factory rom and all is working now, Before I factory defaulted it the my device has been rooted and Samsung pay will not work was keeping me from using it but when I went back to factory it works great now. The phone was on V2 firmware not sure if they did away with the efuse or what but I was glad....
Jabercrombie1 said:
I just rooted my S8+ with Party Cyborg it is a 955U1 and I did not like the fact it could not use health or Samsung pay with my S3 so I put back the orig factory rom and all is working now, Before I factory defaulted it the my device has been rooted and Samsung pay will not work was keeping me from using it but when I went back to factory it works great now. The phone was on V2 firmware not sure if they did away with the efuse or what but I was glad....
Click to expand...
Click to collapse
Because rooting snapdragon doesn't trip Knox.
im sorry to necropost, but has anything developed in the 10 months since this was last discussed? i miss samsung pay on my gear s3 frontier
youdoofus said:
im sorry to necropost, but has anything developed in the 10 months since this was last discussed? i miss samsung pay on my gear s3 frontier
Click to expand...
Click to collapse
You can use samsung pay on your gear s3 on a rooted phone by hiding samsung pay (gear) in magiskhide and setting it up like normal, make sure you pass safetynet
Bresch said:
I know this is an old thread but don't want to start a new just for an update.
Still not possible to get it to work with a rooted tripped phone?
Coming from nexus, first thing I did was root and make a nandroid...
Also flashing stock and locking doesn't revert this? How does this fuse work? Is it hardware or how come you can't just flash the original?
Click to expand...
Click to collapse
Unfortunately, once you rooted your Sammy device you can't get features such as Samsung Pay back due to the blown e-fuse. However, rooting with Magisk will let you use Google Pay. I've been using it basically every day for the past 6 months and not once have I missed Samsung Pay. If by any chance your phone doesn't pass the SafetyNet check there is always modules such as MagiskHide Props Config which will let you change your fingerprint to a certified one, therefore passing the SafetyNet check.
I did some searching, however I was getting a lot of results not related EXACTLY to the my question and a lot outdated (since Xposed is just now officially working for Nougat). So I figured it would be best just to ask. I'm not asking for people to do searching for me or HOW to do these things, I can do that on my own I just want to make sure its all possible before I go and buy a new phone. My LG G3 is currently in my oven and I'm trying to fix it, its been a good phone to me but I don't think its going to last long.
I've been eyeing the Moto G5 plus. My question is it possible to systemless root with Magisk (I want to bypass SafteyNet) and also get Xposed working on this device? There are quite a few xposed apps I can't live without anymore.
Thank you.
You can get magisk and xposed working in the g5 plus, I was running both for awhile. However, I don't think it's possible to pass safetynet if you install Xposed framework since it modifies the system.
Cats_PJs said:
You can get magisk and xposed working in the g5 plus, I was running both for awhile. However, I don't think it's possible to pass safetynet if you install Xposed framework since it modifies the system.
Click to expand...
Click to collapse
Can you just "turn off" xposed? I thought there was systemless xposed?
Helltech said:
Can you just "turn off" xposed? I thought there was systemless xposed?
Click to expand...
Click to collapse
Yes, you can toggle it when you need to pass safetynet.
Just an FYI... NONE of these things are possible on an Amazon ad supported Moto G5+ because the bootloader is not unlockable... No root, no Xposed, no custom ROMs, nothing. You need the full retail version for that.
acejavelin said:
Just an FYI... NONE of these things are possible on an Amazon ad supported Moto G5+ because the bootloader is not unlockable... No root, no Xposed, no custom ROMs, nothing. You need the full retail version for that.
Click to expand...
Click to collapse
And that was why I asked, thank you... Apparently the standard version is cheaper on Amazon regardless, go figure.
Helltech said:
And that was why I asked, thank you... Apparently the standard version is cheaper on Amazon regardless, go figure.
Click to expand...
Click to collapse
Must be a sale then... The ad version is normally about 50-60 bucks cheaper.
acejavelin said:
Must be a sale then... The ad version is normally about 50-60 bucks cheaper.
Click to expand...
Click to collapse
So I can run systemless root with Magisk and systemless xposed also with the non Amazon Moto G5 Plus then?
Helltech said:
So I can run systemless root with Magisk and systemless xposed also with the non Amazon Moto G5 Plus then?
Click to expand...
Click to collapse
On the standard retail version? Of course... even if purchased from Amazon. The bootloader is unlockable, Magisk supports the device, and Xposed supports Nougat now. Just make sure to backup before flashing TWRP (boot it and make a complete backup since we don't have current software images).
But you will never be able to do it on the Amazon supported version.
Does your device pass SafetyNet test after the latest update? I've heard that somebody's device does not, but mine does. That ia strange behavior.
TrueMS said:
Does your device pass SafetyNet test after the latest update? I've heard that somebody's device does not, but mine does. That ia strange behavior.
Click to expand...
Click to collapse
Maybe he have the bootloader unlocked.
He may be using Xposed. Unlocked bootloader doesn't have anything to do with passing safetynet. My device is unlocked and it always passes safetynet check (except June OTA).
Rowdyy Ronnie said:
He may be using Xposed. Unlocked bootloader doesn't have anything to do with passing safetynet. My device is unlocked and it always passes safetynet check (except June OTA).
Click to expand...
Click to collapse
Wrong unlocked bootloader can break safetynet
It is the case for me and I don't care ?
Dead-neM said:
Wrong unlocked bootloader can break safetynet
It is the case for me and I don't care
Click to expand...
Click to collapse
Well, it never happened to me. Safetynet never fails after unlocking bootloader (not with me, never).