I ask this because the qfuse controversy and having the biometric sensor, maybe rooting this device is not safe as it is in the previous nexus, what do you think?
Quetzalcoalt_Lp said:
I ask this because the qfuse controversy and having the biometric sensor, maybe rooting this device is not safe as it is in the previous nexus, what do you think?
Click to expand...
Click to collapse
I'm rooted, q-fuse is still intact, fingerprint scanner still works, I haven't tried to use android pay yet.
Quetzalcoalt_Lp said:
I ask this because the qfuse controversy and having the biometric sensor, maybe rooting this device is not safe as it is in the previous nexus, what do you think?
Click to expand...
Click to collapse
I'm rooted and have no problems. I've heard Android pay will work on stock rom with systemless root, but have not tested it yet. I get my us bank card soon and will sign up then.
then i guess ill root today, thank you!
Quetzalcoalt_Lp said:
then i guess ill root today, thank you!
Click to expand...
Click to collapse
Just follow heisenbergs guide in the general stickies as some stuff is new on the 6p like the fastboot commands and the updated tools from the sdk. You will also want to have a stock copy of the vendor partition and the ems partition or whatever it's called. It's covered in the guide. Happy Flashing!
http://forum.xda-developers.com/showthread.php?p=62924043
You will not lose Nexus Imprint (fingerprint) functionality by rooting. The Qfuse will not blow when you unlock or root. Android Pay probably won't work if you root, but some people claim it does work. Any modifications to /system will cause it to fail.
fury683 said:
You will not lose Nexus Imprint (fingerprint) functionality by rooting. The Qfuse will not blow when you unlock or root. Android Pay probably won't work if you root, but some people claim it does work. Any modifications to /system will cause it to fail.
Click to expand...
Click to collapse
Nothing breaks after root if you use the new systemless root.
Just one more thing, do you guys know how to remove the splash screen when phone boots once rooted? it says something like "Your device software can't be checked for corruption. Please lock the bootloader."
Quetzalcoalt_Lp said:
Just one more thing, do you guys know how to remove the splash screen when phone boots once rooted? it says something like "Your device software can't be checked for corruption. Please lock the bootloader."
Click to expand...
Click to collapse
I am not 100% sure on this because I asked a while back. But I am fairly certain there is currently no way to remove that splash screen with the warning. If I am mistaken, please let me know as I would also like to remove mine.
Quetzalcoalt_Lp said:
Just one more thing, do you guys know how to remove the splash screen when phone boots once rooted? it says something like "Your device software can't be checked for corruption. Please lock the bootloader."
Click to expand...
Click to collapse
. It's something Google is doing now. It just warns of the system state. Here is the page
https://support.google.com/nexus/answer/6185381?hl=en
thesticks00 said:
I am not 100% sure on this because I asked a while back. But I am fairly certain there is currently no way to remove that splash screen with the warning. If I am mistaken, please let me know as I would also like to remove mine.
Click to expand...
Click to collapse
It must be a way, maybe flashing a modified boot.img or something.
Gizmoe said:
. It's something Google is doing now. It just warns of the system state. Here is the page
https://support.google.com/nexus/answer/6185381?hl=en
Click to expand...
Click to collapse
Yes, it's only a notification, it does nothing, but I would want to remove it since is pretty ugly xd.
Quetzalcoalt_Lp said:
It must be a way, maybe flashing a modified boot.img or something.
Yes, it's only a notification, it does nothing, but I would want to remove it since is pretty ugly xd.
Click to expand...
Click to collapse
It's in the bootloader. Don't mess with the bootloader. Just ignore it for the 5 seconds it shows up during the once or twice a week you reboot.
akellar said:
It's in the bootloader. Don't mess with the bootloader. Just ignore it for the 5 seconds it shows up during the once or twice a week you reboot.
Click to expand...
Click to collapse
Maybe with a custom kernel or something you make the BL think you are not rooted or unlocked.
But yes, I wont touch the BL.
I'm pretty sure that I read somewhere that the fuse is actually blown before it the device is even shipped out...
EDIT: I found what I read...
Quote #1
The QFuse is actually an array of different bits that control several different things on the device. In this case, we're talking about the Qualcomm secure boot fuse, which is actually blown at the factory (hence it always being enabled) to prevent an insecure bootloader from being run. It does not track any modifications to the phone other than that, so whatever you decide to do, the bootloader will always read the same thing. I think people are confusing this with Samsung Knox, which is specifically made for tracking modifications and storing them for warranty purposes.
Click to expand...
Click to collapse
Quote #2
Much of Qualcomm's security architecture is implemented using QFuses, which are software-programmable fuses that allow one-time configuration of device settings and cryptographic materials such as hashes or keys. Because of their physical nature, once a QFuse has been blown, it is impossible to "unblow" it to revert its original value.
If the FORCE_TRUSTED_BOOT QFuse is blown, as is the case on all production Motorola devices, each stage of the boot chain is cryptographically verified to ensure only authorized bootloader stages may be run. In particular, the PBL ("Primary Bootloader"), which resides in mask ROM, verifies the integrity of the SBL1 ("Secondary Bootloader") via a SHA1 hash. Each stage of the boot chain verifies the next stage using RSA signatures, until finally Motorola's APPSBL ("Application Secondary Bootloader"), "MBM", is loaded and run.
Click to expand...
Click to collapse
Quote #3
So it would seem the Qfuse has nothing to do with unlocking the bootloader. It's just a way to set cryptographic keys in the hardware for verifying the authenticity of the bootloader, in a manner that makes it impossible to change the keys. In other words, once the fuse is blown the keys can't phyically be changed or overwritten. Presumably Google has the key and can sign new bootloader images correctly, so that when there is an update to the bootloader it will be verified properly by the chipset.
Click to expand...
Click to collapse
Just close your eye's for a few seconds!
People that ask this question should stick to Crapple...
Sent from my Nexus 6P using Tapatalk
Related
I apologize if there is already a thread like this, but the search wasnt working.. I know what i can do with my phone once it is rooted, I am just interested in what happens tot he actual phone. I could be wrong, but once i root it isnt it always possible to tell that i rooted it even if i unroot it so therefor all warantees are voided? sorry if im being unclear, i cant think of another way to explain it haha.
The K-Zoo Kid said:
I apologize if there is already a thread like this, but the search wasnt working.. I know what i can do with my phone once it is rooted, I am just interested in what happens tot he actual phone. I could be wrong, but once i root it isnt it always possible to tell that i rooted it even if i unroot it so therefor all warantees are voided? sorry if im being unclear, i cant think of another way to explain it haha.
Click to expand...
Click to collapse
The language on the "warranty void" screen says that unlocking the bootloader "may" void your warranty. On the Nexus One, HTC usually honored the warranty if the issue was with anything hardware related and could not have been the result of software tampering. Granted, that's them and this is Samsung.
Further, unless there is something hidden in the system files that counts the number of times you unlock the bootloader, you can always relock it prior to sending it in for repair with fastboot oem lock.
unremarked said:
The language on the "warranty void" screen says that unlocking the bootloader "may" void your warranty. On the Nexus One, HTC usually honored the warranty if the issue was with anything hardware related and could not have been the result of software tampering. Granted, that's them and this is Samsung.
Further, unless there is something hidden in the system files that counts the number of times you unlock the bootloader, you can always relock it prior to sending it in for repair with fastboot oem lock.
Click to expand...
Click to collapse
So there is a way to kind of undo the root without them knowing? THanks a lot btw. I figured it was something like this.
The K-Zoo Kid said:
So there is a way to kind of undo the root without them knowing? THanks a lot btw. I figured it was something like this.
Click to expand...
Click to collapse
unlocking the bootloader and rooting are two different things
jblade1000 said:
unlocking the bootloader and rooting are two different things
Click to expand...
Click to collapse
Ahh i have no idea what unlocking the bootloader does then.
The K-Zoo Kid said:
Ahh i have no idea what unlocking the bootloader does then.
Click to expand...
Click to collapse
In a nutshell, unlocking the bootloader means you will be allowed to flash non-Google/custom files to the system partition and more or less enables superuser access(aka root). Once thats done, then you "root" the device, push the Superuser.apk which will enable the rooted apps. Please check out the rooted section of my stickied FAQ for more detail on how to do this if you decide to. There are two great threads I link to.
Once you lock the bootloader, you lose access to the system partition and superuser I believe which effectively unroots it.
unremarked said:
In a nutshell, unlocking the bootloader means you will be allowed to flash non-Google/custom files to the system partition and more or less enables superuser access(aka root). Once thats done, then you "root" the device, push the Superuser.apk which will enable the rooted apps. Please check out the rooted section of my stickied FAQ for more detail on how to do this if you decide to. There are two great threads I link to.
Once you lock the bootloader, you lose access to the system partition and superuser I believe which effectively unroots it.
Click to expand...
Click to collapse
So basically if you want to do any sort of mods, flash roms, etc. you need to unlock the bootload and root. Thanks a lot for explaining that. I think i understand it now, but just to clarify, if i unlock the bootloader and root will i be able to get the phone back to stock without samsung knowing that i rooted/unlock the bootloader?
The K-Zoo Kid said:
So basically if you want to do any sort of mods, flash roms, etc. you need to unlock the bootload and root. Thanks a lot for explaining that. I think i understand it now, but just to clarify, if i unlock the bootloader and root will i be able to get the phone back to stock without samsung knowing that i rooted/unlock the bootloader?
Click to expand...
Click to collapse
Yes, to mod/flash roms you need to unlock the bootloader. It's possible that sometime down the road someone may develop a method of gaining root access on the phone without touching it, but it's unlikely given the fact that we can both unlock and lock the bootloader very easily.
Right now, the answer is... more or less. If you make a NAND backup in Clockwork Recovery/Rom manager of your stock ROM, you can restore back to that, fastboot flash the closest thing we have currently to the stock recovery(check development section for this), then relock the bootloader. This will give the phone all appearances of being stock. Unless Samsung has something deep in the system files tracking the number of times you've unlocked/locked(which I doubt, since I'm sure such a system would have been found by now), you should be good to go.
Most people who have returned the phone to Best Buy have noted that they don't even power on the device or check to see if the bootloader is unlocked or if there's a custom recovery on there. But your mileage may vary.
Interesting stuff. I was under the impression that once clockworkmod is flashed there is no way to remove it at this time.
Reading this thread I'm guessing and hoping this is not the case?
I had clockworkmod installed but used rom manager to flash the 2.3.1 update and i've now got the stock bootloader back. I guess the ota update does the same? It would seem that getting back to stock is pretty easy.
Sent from my Nexus S using XDA App
xspyda said:
Interesting stuff. I was under the impression that once clockworkmod is flashed there is no way to remove it at this time.
Reading this thread I'm guessing and hoping this is not the case?
Click to expand...
Click to collapse
My apologies, I posted that before I came to the same understanding regarding the stock recovery.
Like the poster above me mentioned there is a NAND backup of stock 2.3.1 you could restore to which has the stock recovery.
Sent from my Nexus S using XDA App
Thanks for the clarification. I'll do some more reading in the dev section
Thanks a lot, this really helped me out a lot. I will proceed to rooting
So, just want to make sure I have this straight... You unlock the bootloader, load custom recovery, SU, and now phone is rooted. If you lock the bootloader, you lose root?
For me, I'm not big on custom roms since I just don't have time to keep things up to date or participate in the bug process, but I do like to maintain backups with Titanium (my primary reason for rooting). So by locking the bootloader down I will not be able to use Titanium. Furthermore, unlocking the bootloader wipes the device. So is there a reason one would not want to keep the bootloader unlocked? Have I completely misunderstood the system?
What is that SECURE BOOT at bootloader and how could I turn off?
Google is your friend.
Means you have a locked bootloader. Google or search xda on how to unlock it.
Sent from my Nexus 4 using xda premium
tiru.adi13 said:
Means you have a locked bootloader. Google or search xda on how to unlock it.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
That just means the boot (kernel) on the bootloader is protected there is no way or need to change it. https://plus.google.com/103583939320326217147/posts/P1i8qzLfkTm
Sent from my Nexus 4
spaceman860 said:
That just means the boot (kernel) on the bootloader is protected there is no way or need to change it. https://plus.google.com/103583939320326217147/posts/P1i8qzLfkTm
Sent from my Nexus 4
Click to expand...
Click to collapse
Because they say don't make it so. If Google says you can't root a phone, does that mean it can't be done?
If you tell me something is not possible with android it just means the right developer hasn't worked on it with the right team. Not that it can't be done because of what it says in a few links.
adeptustech said:
Because they say don't make it so. If Google says you can't root a phone, does that mean it can't be done?
If you tell me something is not possible with android it just means the right developer hasn't worked on it with the right team. Not that it can't be done because of what it says in a few links.
Click to expand...
Click to collapse
Don't know why you're commenting on a almost 3 year old thread for. Bootloader is closed sourced and if Google didn't want you to root your phone they can make it so you can't. I suggest you go do some research before you comment on something you don't know nothing about.
Sent from my Dirty Nexus 6
tiru.adi13 said:
Means you have a locked bootloader. Google or search xda on how to unlock it.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
don't give false answers, secure boot is not the same like the OEM-Lock / OEM-Unlock AKA locked or unlocked bootloader, it basically checks the boot.img and won't boot if it won't pass, hence and additional safety level.
MrDarkKV said:
Google is your friend.
Click to expand...
Click to collapse
FYI, Google brought me here. First link...
How to enable secure boot, i have dual boot taclast x80plus, when i am flashing android, it is giving me error
SECURE BOOT disabled
Lock state verfied
gpa_remove_prefix: Not Found,
gpa_remove_prefix: Not Found.
Device is already in required state.
Can anybody help?
I know i posted this in wrong section but no one is really helping anywhere and google always give this threat as best solution.
For anyone still searching the answer, Secure Boot is the same than S-OFF in HTC Devices: It is a trusted chain between the psychal bootloader (BootRom) and all the partitions booted by them (including SBL, which later boots ABOOT). BootRom -> SBL -> ABOOT chain is checked and if something is not signed it won't boot (this is Secure Boot), the step ABOOT -> boot.img (Kernel) is controlled not by Secure Boot but by the Locked/Unlocked Bootloader bit. Secure Boot also controls the call from BootRom to all other bootloader partitions, including the Radio.
In short words, The Locker/Unlocked bootloaders controls writing to partitions SYSTEM, USERDATA, CACHE, RECOVERY, BOOT, Bootloader (Signed stuff) and Radio (signed stuff). Secure Boot on the other hand controls access to the entire device partition set, including any Bootloader/Radio/Other patition, Trustzone, FRP, Bootloader info storage..
Great info for anyone that cares I'm sure, the question is how to turn it off.
how secure boot effect us?
RusherDude said:
...
In short words, The Locker/Unlocked bootloaders controls writing to partitions SYSTEM, USERDATA, CACHE, RECOVERY, BOOT, Bootloader (Signed stuff) and Radio (signed stuff). Secure Boot on the other hand controls access to the entire device partition set, including any Bootloader/Radio/Other patition, Trustzone, FRP, Bootloader info storage..
Click to expand...
Click to collapse
how does this secure boot effect my effort to root / put xposed framework on it? I*already have custom recovery installed and it doesn't seem to have a problem. but now that i upgraded my phone (with factory image, mind you), my phone now stuck at boot animation. I suspect this secure boot thing has something to do with it
kngharv said:
how does this secure boot effect my effort to root / put xposed framework on it? I*already have custom recovery installed and it doesn't seem to have a problem. but now that i upgraded my phone (with factory image, mind you), my phone now stuck at boot animation. I suspect this secure boot thing has something to do with it
Click to expand...
Click to collapse
No. As I said, secure chain works until bootloader. If there was an error on this chain, your phone wouldn't even turn on probably. You are having probably some kernel or system issue provoking bootloop.
RusherDude said:
No. As I said, secure chain works until bootloader. If there was an error on this chain, your phone wouldn't even turn on probably. You are having probably some kernel or system issue provoking bootloop.
Click to expand...
Click to collapse
I gotten around the problem by giving up the factory image and installed LineageOS instead. Still can't figure out why bootloop happened after I rooted it. but it's ok. it's an old phone (Nexus5) and LineageOS is actually pretty good for my purpose.
kngharv said:
I gotten around the problem by giving up the factory image and installed LineageOS instead. Still can't figure out why bootloop happened after I rooted it. but it's ok. it's an old phone (Nexus5) and LineageOS is actually pretty good for my purpose.
Click to expand...
Click to collapse
Of course.. on a Nexus 5 forget about official **** that got abandoned years ago!
tiru.adi13 said:
Means you have a locked bootloader. Google or search xda on how to unlock it.
Click to expand...
Click to collapse
no it doesnt my bootloader is unlocked and secure boot is enabled try explaining that back to me you dont know what ur talking about
After unlocking bootloader message is coming your device is corrupt and can't be checked for corruption but after some time I have reverted to stock and relocked OEM using Nexus Root toolkit but even then warning is coming any way to remove this..
Mohit M'S said:
After unlocking bootloader message is coming your device is corrupt and can't be checked for corruption but after some time I have reverted to stock and relocked OEM using Nexus Root toolkit but even then warning is coming any way to remove this..
Click to expand...
Click to collapse
It is highly unlikely that after relocking that message would come. Actually, that message could be ignored if your ROM boots fine.
What does the bootloader display about locked status?
DJBhardwaj said:
It is highly unlikely that after relocking that message would come. Actually, that message could be ignored if your ROM boots fine.
What does the bootloader display about locked status?
Click to expand...
Click to collapse
Your device is corrupt and can't be checked for corruption
Mohit M'S said:
Your device is corrupt and can't be checked for corruption
Click to expand...
Click to collapse
Not that. I meant in the bootloader mode itself. Does it display "Device is Locked" or "Device is Unlocked"?
DJBhardwaj said:
Not that. I meant in the bootloader mode itself. Does it display "Device is Locked" or "Device is Unlocked"?
Click to expand...
Click to collapse
Device is locked
Mohit M'S said:
Device is locked
Click to expand...
Click to collapse
Unlock it again. Go from scratch and flash the factory image using Heisenberg's guide in the General section. After flashing that, see if it solves the issue.
Using toolkits could be buggy at times. I am not against them, but it's good to flash manually, so that you can keep a track on things.
DJBhardwaj said:
Unlock it again. Go from scratch and flash the factory image using Heisenberg's guide in the General section. After flashing that, see if it solves the issue.
Using toolkits could be buggy at times. I am not against them, but it's good to flash manually, so that you can keep a track on things.
Click to expand...
Click to collapse
can I flash without unlocking bootloader because after unlocking bootloader there r some heat issues
Mohit M'S said:
can I flash without unlocking bootloader because after unlocking bootloader there r some heat issues
Click to expand...
Click to collapse
No you can't flash anything with a locked bootloader. Plus, it's entirely impossible for an unlocked bootloader to cause heat issues, that's either placebo or a coincidence (another cause).
PS. The title of this thread is useless, you should describe your issue in the title, not create text faces.
Heisenberg said:
No you can't flash anything with a locked bootloader. Plus, it's entirely impossible for an unlocked bootloader to cause heat issues, that's either placebo or a coincidence (another cause).
PS. The title of this thread is useless, you should describe your issue in the title, not create text faces.
Click to expand...
Click to collapse
OK OK but after unlocking it there is any way to relock it and remove this error message
Mohit M'S said:
OK OK but after unlocking it there is any way to relock it and remove this error message
Click to expand...
Click to collapse
Yes, of course. Infact that's the reason I asked you about the lock status on the first place. Stock ROM with locked bootloader shouldn't give this warning. It should make it go away.
That is why, I asked you to perform a flash manually. Please refer to Heisenberg's guide for the steps.
Here is the link: http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Mohit M'S said:
OK OK but after unlocking it there is any way to relock it and remove this error message
Click to expand...
Click to collapse
Yes, after locking the bootloader the message should disappear. But, I'd strongly recommend leaving it unlocked and just dealing with the message. If an OTA ever fails or something else goes wrong you'll need fastboot to flash the factory images to recover your device, you'll be forced to unlock the bootloader, this will wipe the device and you'll lose all of your data because there'll be no way to back it up first.
DJBhardwaj said:
Not that. I meant in the bootloader mode itself. Does it display "Device is Locked" or "Device is Unlocked"?
Click to expand...
Click to collapse
Sorry message is Device can't be trusted or it may not work properly
Mohit M'S said:
Sorry message is Device can't be trusted or it may not work properly
Click to expand...
Click to collapse
Did you reflash manually?
DJBhardwaj said:
Did you reflash manually?
Click to expand...
Click to collapse
Nope gonna do this by today or tomorrow
Mohit M'S said:
Nope gonna do this by today or tomorrow
Click to expand...
Click to collapse
Sure and then let us know. And keep the bootloader unlocked, it will help you to deal with a few issues (if any), in the future, as already mentioned above by Heisenberg.
-_____- why do people still use toolkits? Try getting use to Adb; it would save you a lot of time dealing with errors.
Mohit M'S said:
Sorry message is Device can't be trusted or it may not work properly
Click to expand...
Click to collapse
There is only one way to get rid of the message, and you have already been told.
The solution is to relock your bootloader. Nothing else will fix it.
uicnren said:
There is only one way to get rid of the message, and you have already been told.
The solution is to relock your bootloader. Nothing else will fix it.
Click to expand...
Click to collapse
First when I unlocked it message is coming your device is corrupt and can't be checked for corruption but after relocking it message is coming device can't be trusted or may not work properly and it is happening it is not working properly no system update for me even Android one got update and all my friends got update who r using it..??
Ruined my phone
Mohit M'S said:
First when I unlocked it message is coming your device is corrupt and can't be checked for corruption but after relocking it message is coming device can't be trusted or may not work properly and it is happening it is not working properly no system update for me even Android one got update and all my friends got update who r using it..
Ruined my phone
Click to expand...
Click to collapse
It didnt ruin your phone.
Simply reflash the stock images and start over from scratch.
If you root or modify the phone in any way from stock, you will get those messages. They are simply that, messages. They do not affect your phone negatively. Other things you have done (like root, or installing apps from unknown sources) WILL affect the phone.
Flash stock images, relock bootloader and it will be brand new, like the day you got it.
If you dont wish to go back to stock, but want to flash OTA updates when they come out (and you are already rooted) look into using FlashFire.
uicnren said:
It didnt ruin your phone.
Simply reflash the stock images and start over from scratch.
If you root or modify the phone in any way from stock, you will get those messages. They are simply that, messages. They do not affect your phone negatively. Other things you have done (like root, or installing apps from unknown sources) WILL affect the phone.
Flash stock images, relock bootloader and it will be brand new, like the day you got it.
If you dont wish to go back to stock, but want to flash OTA updates when they come out (and you are already rooted) look into using FlashFire.
Click to expand...
Click to collapse
U didn't understand what I said I have already reverted my to stock ROM and relocked the bootloader but even then message is coming device can't be trusted or may not work properly and I'm not even getting any updates not even April update and all friends got this I'm currently pure stock
Problem are:-
Message is still there
Updates r not coming
https://twitter.com/laginimaineb/status/737051964857561093
This should help with unlocking the bootloader on the T-Mobile Z1s, correct? I'll be so freaking happy if I can get this damn phone off 5.0.2.
WilliamTell13 said:
https://twitter.com/laginimaineb/status/737051964857561093
This should help with unlocking the bootloader on the T-Mobile Z1s, correct? I'll be so freaking happy if I can get this damn phone off 5.0.2.
Click to expand...
Click to collapse
Forget about it. This has nothing to do with bootloader, but just an attempt to decrypt data partition and on Nexus.
optimumpro said:
Forget about it. This has nothing to do with bootloader, but just an attempt to decrypt data partition and on Nexus.
Click to expand...
Click to collapse
Damn. Some guy on Reddit said it should help because the "Trustzone kernel is the entrance to the Linux kernel making it possible to unlock our device". Is that incorrect?
WilliamTell13 said:
Damn. Some guy on Reddit said it should help because the "Trustzone kernel is the entrance to the Linux kernel making it possible to unlock our device". Is that incorrect?
Click to expand...
Click to collapse
Trust Zone has nothing to do with bootloader. Since LP5.1.1, trust zone (hardware) certificate is used to sign the keymaster, which is used to encrypt data partition. If you can extract trust zone certificate, you can try to bruteforce the boot password off the device (because it takes a lot longer on the device). So, a hacker could take an image of your phone plus the hardware certificate and try to guess the password. That's all.
Things are different in Iphone, where the encryption key sits in the hardware module. So, if you get that key, you open the device. That's why Iphone security is non-existent...
Welp now that safetynet checks the bootloader, I have to lock it to continue using android pay etc (non-rooted device).
I'm getting conflicting reports, so I was hoping someone here can solve this mystery.
Does relocking the bootloader automatically wipe the device?
Thanks
Yup.
It does for me when I attempted to get AP to work. Nexus 6p
seems like we're stuck in the crossroads of wipe the whole thing or go full root and say to hell with android pay :-/
arts711 said:
Welp now that safetynet checks the bootloader, I have to lock it to continue using android pay etc (non-rooted device).
I'm getting conflicting reports, so I was hoping someone here can solve this mystery.
Does relocking the bootloader automatically wipe the device?
Thanks
Click to expand...
Click to collapse
Unfortunately, I crossed this road yesterday. Yes I had to relock my bootloader and, yes, I had to wipe my phone
arts711 said:
seems like we're stuck in the crossroads of wipe the whole thing or go full root and say to hell with android pay :-/
Click to expand...
Click to collapse
I'm passing on AndroidPay.
I will not allow them to dictate what I do with my device.
tech_head said:
I'm passing on AndroidPay.
I will not allow them to dictate what I do with my device.
Click to expand...
Click to collapse
Same decision. Unless they start requiring locked bootloader for ridiculous reasons. I can sort of understand the financial/bank access concerns. If they expand the requirements for a locked boot loader beyond that, I'll return to the iPhone.
hawgguy said:
Same decision. Unless they start requiring locked bootloader for ridiculous reasons. I can sort of understand the financial/bank access concerns. If they expand the requirements for a locked boot loader beyond that, I'll return to the iPhone.
Click to expand...
Click to collapse
Love it when people "threaten" to return to iPhone lol,
Sent from my Nexus 6P using Tapatalk