Fail safetynet even after complete wipe!! - Nexus 6P Q&A, Help & Troubleshooting

So my safetynet checker says I failed even though I completely wiped all data! Even the sdcard data! I did a complete fastboot flash of all the system image files including the userdata file. I did not root the phone yet and I don't plan to either, I just want Android Pay.
CTS Profile Match = fail
That's what I get from the safetnet checker...My only other idea is to relock and unlock the bootloader again.

It seems you're not alone. I saw a few posts on reddit describing the same thing. The consensus is that Google may possibly be requiring locked bootloaders as well now for Safetynet.
Granted, I live in Canada and we don't have Android Pay yet. But I just won't even bother if this is the case.

It appears you are right mattkroeder...I relocked my bootloader and it passed, I unlocked it again and it failed....

Damn! I could not figure out why my Pay didn't work today. I'm stock, unlocked, custom ROM, no root. I just tried safetynet and its red. That seems like a bigger hurdle then not allowing rooted phones no pay.

It has been said all along that it was a losing battle....I just hoped that they would eventually block any and all root access at worst. Blocking the bootloader unlock I think puts a nail in the coffin of that little game. You will only be able to have Android Pay with a completely stock phone....

Looks like it is the case now. Now I'm gonna waste 2-3 hours of my precious life, reverting everything back to stock and locked.
GatorsUF said:
It has been said all along that it was a losing battle....I just hoped that they would eventually block any and all root access at worst. Blocking the bootloader unlock I think puts a nail in the coffin of that little game. You will only be able to have Android Pay with a completely stock phone....
Click to expand...
Click to collapse

Related

[Q] Root Question related later ota

after a few hours searching, I am still a bit confusing on following question:
1. trip rootchecker
If I do not choose do this during rooting, in other word, I only have adb shell root.
a) should I still be able to install twrp and flash other rom? my impression is "yes", am I right?
b) But if I choose do this, then my warranty is gone. If I later flash back the stock,
will this be wiped and "forget"? i.e. the warranty is back?
Or is this "root checker" will send somthing to LG once it is tripped, hence warranty
is permanently voided?
2. ota
It seems once rooted, one can not take any ota, right? even the kitkat in future?
would "trip rootchecker" matter in this case?
even though thanks to thecubed, it seems we do have a solution.
If you choose not to trip the root checker, root will not work properly and neither will the apps that require it.
It doesn't send any info to LG or your carriers. All it does is... If in the future you break your phone somehow and take it into your carrier store to get it fixed, they will check the phone to see if it's ever been rooted. If it's been tripped, it'll give a number code on the screen to tell them it either was rooted in the past but isn't anymore, is currently rooted, or was never rooted.
Then it will be at the store's discretion on whether or not they'll help you out or make you pay full price to fix it or get it replaced.
I don't know how it is for the G2, but I know awhile back some newer HTC phones got S-OFF which allowed them to reset the root checker to make the device think it's never been rooted. Our phones may have a similar method out there somewhere... Though probably not as it'd be fairly big news. I am however, willing to bet that there is a crack team or two working on disabling that for our devices.
Sent from CAMACHO, my Verizon G2 (VS980) running PAC ROM.

Another RMA disaster...

I bought my Pure Edition about a month ago. A week and a half ago, I wake up and check Google Now for the weather and the phone shuts down and is fried. It has been hot a lot, but I heard it was normal and no big deal. I went through the ordeal of getting a replacement phone a week ago Monday. I then got the email saying it would ship the day after it was received. Sweet! I was thrilled! Only 3 days with a cheap prepaid temp phone. So it doesn't get delivered on that Thursday as stated. Or the next day. I call them to check on it and they said it wasn't going to be here until Today. Surprise! I got it a day early! Yes! However, they sent me a phone that had the bootloader still locked, but the software was modified so I can't use it for work as it shows compromised in Airwatch. I'm fairly certain my account has been flagged, but that's another issue to fix. I called them again today. They will send me a new one. Again. Another week without a phone that I bought only a month ago. I really wish they had the Nexus 6 in stock the day I bought this because that is the one I wanted. I absolutely loved by 2013 Moto X. This one, not so much. The several people I was transfered between had no idea what compromised means on the bootloader. The last guy, thought that the bootloader was used for loading Airwatch in the first place. Has anyone else recieved a phone from the OEM that was compromised or modified software? Slowly, but surely losing faith in this company.
That's a disaster? We must have a very different definition of that word
OK, So I am a little upset by it all, but I just bought the phone a month ago and now I am going to be without it for 2 out of the 5 weeks of ownership. Maybe its not the RMA process, but that I am having to go through it so soon and twice at that.
I do agree that is a PITA. I bought mine used and did not have this experience. It's funny you say you liked the 2013, because I actually very much disliked the 2013 and could not be happier with my 2014.
I'm not quite following the modified software thing. They sent you a phone with a locked bootloader but was not all the way stock? I found that either a) AirWatch does not look for whether the bootloader is locked/unlocked, or b) my firm did not include that in the AirWatch policies or whatever. I unlocked my bootloader, installed TWRP, and rooted, and my phone showed up as compromised. I returned to pure stock with stock recovery, but kept my bootloader unlocked, and had no problems clearing AirWatch. I've heard the same from others on XDA. But I find it weird that Moto would ship out a phone that had compromised software. Even if it was one someone else returned, you would think it would be standard policy to ensure it is completely wiped and returned to full on factory stock condition.
anidrin said:
Has anyone else recieved a phone from the OEM that was compromised or modified software?
Click to expand...
Click to collapse
I would return it again. This is Moto's fault for having these flags in the first place.
Yeah, shipping it locked is not a surprise, showing up in Airwatch as compromised when it's still stock recovery, locked, and non rooted? That's odd.
Paddington said:
I'm not quite following the modified software thing. They sent you a phone with a locked bootloader but was not all the way stock?
Click to expand...
Click to collapse
There is a root checker on Motorola phones since I think ICS days. If a device has never been rooted it's status is 0/0, if it is currently rooted it is 1/1 and if it was rooted and unrooted it is 0/1. If it is either of the latter 2, it will show as modified software in bootloader mode.
---------- Post added at 01:12 AM ---------- Previous post was at 01:11 AM ----------
scottricketts said:
Yeah, shipping it locked is not a surprise, showing up in Airwatch as compromised when it's still stock recovery, locked, and non rooted? That's odd.
Click to expand...
Click to collapse
No it's not, it means it has been rooted in the past.
JulesJam said:
There is a root checker on Motorola phones since I think ICS days. If a device has never been rooted it's status is 0/0, if it is currently rooted it is 1/1 and if it was rooted and unrooted it is 0/1. If it is either of the latter 2, it will show as modified software in bootloader mode.
---------- Post added at 01:12 AM ---------- Previous post was at 01:11 AM ----------
No it's not, it means it has been rooted in the past.
Click to expand...
Click to collapse
Did you try running a root checker app to see if the phone is currently rooted? Because my device was rooted, but reflashing a stock unrooted system made my phone go from compromised to compliant on our AirWatch system. And our AirWatch policies are pretty strict, because they have to meet the security tests of our clients with the strictest security policies, and we are a big law firm that represents most of the Fortune 100 and nearly (or every) major bank.
Although I do agree with your initial stance that there is really no excuse for them to ship you a pre-rooted phone without you requesting it. In the past, that would have saved me 10 minutes, but now, it would be a hassle.
Paddington said:
Did you try running a root checker app to see if the phone is currently rooted?
Click to expand...
Click to collapse
I did it with my N6. I know the phone is unrooted as I flashed a stock system image. In the bootloader mode, it still says software is modified.
This is well known to be how it works with Motorola phones.
Paddington said:
Although I do agree with your initial stance that there is really no excuse for them to ship you a pre-rooted phone without you requesting it. In the past, that would have saved me 10 minutes, but now, it would be a hassle.
Click to expand...
Click to collapse
His phone wasn't pre-rooted - it had been rooted in the past and that then creates the 0/1 state.
JulesJam said:
I did it with my N6. I know the phone is unrooted as I flashed a stock system image. In the bootloader mode, it still says software is modified.
This is well known to be how it works with Motorola phones.
His phone wasn't pre-rooted - it had been rooted in the past and that then creates the 0/1 state.
Click to expand...
Click to collapse
So I just tried this out. I booted into fastboot and it says my device is UNLOCKED, and then it says:
"Status Code: 3"
"Software Status: Official"
I unlocked this phone, flashed TWRP, and rooted it. I screwed around with it, downloaded a few root apps (busybox, rootbrowser, quick boot), then saw it was listed as compromised on AirWatch. I used a toolkit to do a full wipe and revert back to stock, unrooted 4.4.4 and factory recovery. I then upgraded to 5.0 through the OTA. I never relocked the bootloader. My device showed up as compliant when I redownloaded AirWatch.
And I still agree with the original premise that Motorola should have made sure this didn't happen originally--which is why they are going to fix it--but I'm not understanding why he can't get around this the same way I did. I'm not understanding why he is showing up as a modified software while I am not.
Paddington said:
So I just tried this out. I booted into fastboot and it says my device is UNLOCKED, and then it says:
"Status Code: 3"
"Software Status: Official"
I unlocked this phone, flashed TWRP, and rooted it. I screwed around with it, downloaded a few root apps (busybox, rootbrowser, quick boot), then saw it was listed as compromised on AirWatch. I used a toolkit to do a full wipe and revert back to stock, unrooted 4.4.4 and factory recovery. I then upgraded to 5.0 through the OTA. I never relocked the bootloader. My device showed up as compliant when I redownloaded AirWatch.
Click to expand...
Click to collapse
Hmm, that is not what is happening with my N6 or on the Droid Turbo forums for those who are using MoFo. For us, once we root, that is it, even unrooting, flashing back to stock doesn't reset that root check flag.
JulesJam said:
Hmm, that is not what is happening with my N6 or on the Droid Turbo forums for those who are using MoFo. For us, once we root, that is it, even unrooting, flashing back to stock doesn't reset that root check flag.
Click to expand...
Click to collapse
If it was just Droid Turbo, I'd guess it has to do with the MoFo exploit and the fact that it is not supposed to be unlocked and rooted. And by "not supposed to be," I of course mean in the eyes of Verizon, because it is ridiculous that a company will not let you unlock your bootloader on a $600 phone once you've fully paid it off. But that is beside the point. The fact that it is also happening with your Nexus 6 pretty much defeats my theory that it is MoFo causing it.
Could it be that when I updated through a true OTA, like went to Settings > About Phone > Updates, it reset this counter? Or, ignoring the counter for a moment, that the true OTA update re-established my system as being 100% unmodified stock--"Software Status: Official"? Troubleshooting based on recent experiences without the ability to test my hypotheses (it is my work phone ,after all) is driving me nuts.
Paddington said:
The fact that it is also happening with your Nexus 6 pretty much defeats my theory that it is MoFo causing it.
Click to expand...
Click to collapse
I just flashed my N6 back to total stock using factory images and relocked it. Software status says modified and bootloader status is status code 2 locked (which means relocked). And AFAIK, this is what everyone's experience on a Motorola phone is:
Locked Status Code 0 = never been unlocked before by the fastboot oem unlock command
Unlocked Status Code 1 = unlocked in its original factory state and never been locked before*
Locked Status Code 2 = locked but has been unlocked before
Unlocked Status Code 3 = currently unlocked
*You can't buy a phone in the Status Code 1 Unlocked state in the US. You can buy them off of Tao Bao and they are referred to as "factory" devices. They are "removed" from the Chinese factory before they are locked. However, I would not do that as I am not sure if they are on the global blacklist or not.
The Software state can be any of the following:
qe 0/0 = never been rooted
qe 1/1 = currently rooted
qe 0/1 = not currently rooted but rooted at some point in the past
States qe 1/1 and qe 0/1 will show the Software status as modified IME. So Software Modified means modified currently or at some point in the past.

Does unlocking the bootloader leave traces apps can see?

My apologies if this is a well-known question/answer, but I've not been able to find anything...
I have an old GS4 which was nicely rooted. Some apps try to determine if you've got root and so the eXposed "Root Cloak" module came in handy.
Yesterday I received my Moto X Pure. So little bloat on it that I almost decided I didn't need root. But, wow, I'd forgotten just how many adverts spring up all over the place. OK, root needed. Reading around it seems that to root this device requires unlocking the bootloader and using TWRP. OK... I can do that.
But the question I have is whether this will stop the "oh noes, malware!" detecting apps from running because my device is now "insecure".
(Alternatively, ability to block ads inside apps without needing root would work )
Thanks!
So I took this risk, anyway. Unlocked the bootloader (which caused a reset of the phone), reinstalled my apps etc etc, and they seem to work and are not complaining about the unlocked loader.
So that's good

Finally rooted then I rebooted...

So hi all, this is my first post on XDA. Finding information these days you think would be easy but alas it's been one big waiting game.
A little background, I've wanted for the longest time to link my ps3 controller (WIRELESSLY) to my s4, but Verizon forced an upgrade to Lollipop, I hate it and it's been a nightmare for me.
I learned I would have to be root to get the controller to work wirelessly, but I wanted root access for other reasons well such as bloatware removal and interface customization.
So I've been skulking around forums like a hawk, finally I found king root but it wouldn't root my phone and I wasn't about to install it on my PC, too risky... so I waited and waited and waited.
several months pass...
New update for King root will now work to root my phone, and I was able to replace it with super-sume, root checker showed I was rooted and Bazinga! Off I was at last. I removed a couple pieces of bloatware but before I continued I thought it might be wise to reboot the phone while rooted to make sure everything is kosher.
Phone comes back up, no problems. but now ROOT ACCESS IS GONE. I read up and discovered that in some cases the boot-loader will unroot the phone everytime you reboot. I don't want to have to re-root my phone over and over again, that's a pain in the arse.
I read up on some laws felt confident if I called Verizon they wouldn't be able to give me a hard-time, I just wanted to know how to disable the boot-loader locking things up.
I ended up with tier two, who they stated all their 4G devices are unlocked... when I got into the nitty gritty regarding the bootloader the techs I spoke with were lost.
I just want to be able to root my phone and KEEP root. I wish I had Kit-Kat because this wouldn't even be an issue but I don't. Can anyone help? I'm so sick of this crap.
HALP PLZ :crying: :crying:
Another small caveat I should mention, when I reboot my phone, it has an unlocked padlock but root checker states that root access in no longer properly installed and I can't do anything that I'd be able to do rooted either. Before the reboot, root was showing as properly installed.
Wrong forum, there is a Verizon subsection.
Verizon phones are all unlocked...... meaning you can insert whatever SIM card you feel like putting into it.
The bootloader, however, is locked. It will remain locked and it's more than likely never going to be unlocked. Write access is dependent on an unlocked bootloader. The security checks are set up as such that if you attempt to alter the system files, they'll just all return to normal on a reboot.
You can use a temp root method on Android 4.4, but as you figured out.... when you reboot, Bye Bye Root!
There is not, nor has there been, nor will there be a bootloader unlock unless somebody cracks Samsung's encryption keys. You have a better chance of winning the Powerball jackpot than doing that.
Use CF root if you wanna perm and thing solved..

Locking bootloader on US variant xt1806

I went to switch to a different carrier, and was on cricket, and also tried tmobile both wich worked fine unlocked bootloader and rooted.
I then switched to sprint, and verizon and found out both carriers the phone would not work right. The data worked but the call and texting did not.
As a side note, I was informed by someone who was on sprint, and he said that you had to get on the network unrooted and locked bootloader, once registered you could then root and get the bootloader unlocked and be just fine.
So I then proceeded to unroot the phone ie: removing everything root, and keeping twrp with an unocked bootloader only, no sign of root. I took the phone back to the stores and tried again, and the phone still had the same issue.
After finally finding a way to finally after 6mo lock the bootloader again, and was at pure stock, locked bootloader and no root.
What this tells me is that some how verizon and sprint both some how some way detect an unlocked bootloader....how? I have no clue, I've never in my 5+ years of rooting multiple phones, never ever ever seen anything like this. The only reason I know this is what it was, is from common deduction and reasoning.........unroot = still doesn't work.....locked bl = works fine with not a single issue. Keep in mind this was all with base stock rom, not a custom rom.....everything was stock, accept for the root and un;ocked bootloader part. I rooted with magisk.
Since I had a very long time and issue with locking the bootloader, (about 6mo) after trying a ton of things, without resolve, I FINALLY got the bootloader locked.
If it's going to be anything like before trying to get it locked again to work on sprint and verzion, I really do not want to bother with unlocking it to begin with. It was an utter nightmare to get locked, no matter what I tried it just would not lock for whatever reason.
So given all that, my question is, how hard or easy is it now to unlock and lock the bootloader?

Categories

Resources