Related
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
Guys,
We've seen several people have flashed system.img's and OTA's and ended up in a bootloop.. Not the end of the world really, BUT for some reason, before you can unlock your bootloader using fastboot, you must enable OEM unlock in Developer options in Android settings - which you cannot do if you are bootlooping.
If you still have a custom recovery, you'll be fine but if you're 100%, locked bootloader and bootlooping, we haven't found a fix yet so please do not lock your bootloader.
If you feel you absolutely must relock your bootloader (at your own risk) please boot the phone up to check it works properly before doing this. If you intend flashing roms and kernels or custom recoveries, locking the bootloader is not a good idea
Please also see the below link provided by @efrant
https://support.google.com/nexus/answer/6172890?hl=en
This goes into more detail about how google have enhanced device security with 5.1 and some other pitfalls that you may wish to avoid. This is pretty salient information, so do give it a read.
Good advice, i would add to that NEVER LOCK YOUR BOOTLOADER. ???
Sent from my Nexus 9 using XDA Free mobile app
ChristianJay said:
Good advice, i would add to that NEVER LOCK YOUR BOOTLOADER.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
And I would add that I completely disagree with this statement. Coming from an infosec standpoint, I keep my bootloader locked, and just suffer the reset when I need to tweak. If you don't, anyone - not just you - can replace your system partition or boot a random IMG which could inject functionality. This may not be the most common mechanism for attack as it requires physical access, but it basically obviates the encryption with a deepfreeze style boot IMG.
Additionally, when you think about this in context of the border crossing exemptions many countries, including the US, have to protections against unwarranted search, I would recommend that anyone with proprietary or sensitive business data who crosses international borders keeps their bootloader locked when not modifying the system. Also, until custom recoveries include security features, I recommend using stock.
Why are we making our phones so insecure just to have root? Not cool.
So just to be clear the correct procedure would be to boot the device after updating enable the setting and then go and lock your bootloader? Or just keep it unlocked overall.
Personally I keep mine unlocked but for those wanting to take full advantage of androids new device protection a locked bootloader would serve a purpose. Preventing someone from just flashing a custom rom and keeping your device.
:thumbup:
I thought I really #$# up
Thank you for posting this...when 5.1 was dropping, I attempted to return to stock...all the way.to be able to take Verizon's OTA...when i locked the boot loader, i was stuck in a boot loop with the android guy and the gear box spinning FOREVER.....its is not easy to get out of the loop, but i managed to boot back up into boot loader mode, and force a stock image using toolkit.
I am now unlocked, running 5.1 on Verizon, have full LTE/VOLTE, can speak and surf at same time...i have not rooted yet...but just glad it was not me....had a heart attack two nights ago...
xander45 said:
Thank you for posting this...when 5.1 was dropping, I attempted to return to stock...all the way.to be able to take Verizon's OTA...when i locked the boot loader, i was stuck in a boot loop with the android guy and the gear box spinning FOREVER.....its is not easy to get out of the loop, but i managed to boot back up into boot loader mode, and force a stock image using toolkit.
I am now unlocked, running 5.1 on Verizon, have full LTE/VOLTE, can speak and surf at same time...i have not rooted yet...but just glad it was not me....had a heart attack two nights ago...
Click to expand...
Click to collapse
im so new to this but im rooted with an unlocked bootloader but im running full stock android. i only rooted just so i can chance the provision to get free tethering with my unlimited data. i have the wugfresh nexus tool kit and cant for the life of me figure out how to upgrade my nexus 6 to 5.1. Is there in anyone that can get me a step by step on how to update so i can take advantage of hd calling and silmutaneous voice and data... ive been waiting tooooooooooo long for this update..
rootSU said:
Guys,
We've seen several people have flashed system.img's and OTA's and ended up in a bootloop.. Not the end of the world really, BUT for some reason, before you can unlock your bootloader using fastboot, you must enable OEM unlock in Developer options in Android settings - which you cannot do if you are bootlooping.
If you still have a custom recovery, you'll be fine but if you're 100%, locked bootloader and bootlooping, we haven't found a fix yet so please do not lock your bootloader.
Click to expand...
Click to collapse
Hi root,
I saw that thread yesterday ...
I thought this was already covered when the N6 came out, to get the bootloader unlocked you had to do a 1st boot of the device and ENABLE OEM Unlock, then you were good to go to get into fastboot and unlock.
The reason was google put the option there for 5.0, vice all our previous versions which had no toggle for it.
I think it was people jumping the gun and not doing that first boot, but immediately jumping into fastboot and flashing, and that caused it, yes? Because the BL wasn't unlocked, they couldn't flash the OTA and boot img ...
daijizai said:
And I would add that I completely disagree with this statement. Coming from an infosec standpoint, I keep my bootloader locked, and just suffer the reset when I need to tweak. If you don't, anyone - not just you - can replace your system partition or boot a random IMG which could inject functionality. This may not be the most common mechanism for attack as it requires physical access, but it basically obviates the encryption with a deepfreeze style boot IMG.
Additionally, when you think about this in context of the border crossing exemptions many countries, including the US, have to protections against unwarranted search, I would recommend that anyone with proprietary or sensitive business data who crosses international borders keeps their bootloader locked when not modifying the system. Also, until custom recoveries include security features, I recommend using stock.
Why are we making our phones so insecure just to have root? Not cool.
Click to expand...
Click to collapse
This is nonsense.
You need *physical* access to it in order to carry out such an attack.
If your phone leaves your PHYSICAL access, then you already know not to trust what is on it, whether or not it has an unlocked bootloader.
xander45 said:
Thank you for posting this...when 5.1 was dropping, I attempted to return to stock...all the way.to be able to take Verizon's OTA...when i locked the boot loader, i was stuck in a boot loop with the android guy and the gear box spinning FOREVER.....its is not easy to get out of the loop, but i managed to boot back up into boot loader mode, and force a stock image using toolkit.
I am now unlocked, running 5.1 on Verizon, have full LTE/VOLTE, can speak and surf at same time...i have not rooted yet...but just glad it was not me....had a heart attack two nights ago...
Click to expand...
Click to collapse
kng60ft said:
im so new to this but im rooted with an unlocked bootloader but im running full stock android. i only rooted just so i can chance the provision to get free tethering with my unlimited data. i have the wugfresh nexus tool kit and cant for the life of me figure out how to upgrade my nexus 6 to 5.1. Is there in anyone that can get me a step by step on how to update so i can take advantage of hd calling and silmutaneous voice and data... ive been waiting tooooooooooo long for this update..
Click to expand...
Click to collapse
There is no need to lock the device to take an OTA. You can keep it unlocked and do an ota
doitright said:
This is nonsense.
You need *physical* access to it in order to carry out such an attack.
If your phone leaves your PHYSICAL access, then you already know not to trust what is on it, whether or not it has an unlocked bootloader.
Click to expand...
Click to collapse
Not nonsense. Yes you need physical access to carry out the attack, but with a locked bootloader and the new precautions against unlocking and fastboot it makes locked bootloaders fairly bulletproof.
I cannot recommend unlocked bootloaders to anyone that works SCIF'd and leaves their phone in a shared box during the day, anyone that crosses international borders, or anyone whose phone might contain IP or trade secrets and could be a target of theft.
This is as much about trusting the phone afterwards as it is about protecting your data on the phone - even when encrypted.
y2whisper said:
So just to be clear the correct procedure would be to boot the device after updating enable the setting and then go and lock your bootloader? Or just keep it unlocked overall.
Personally I keep mine unlocked but for those wanting to take full advantage of androids new device detection a locked bootloader would serve a purpose.
Click to expand...
Click to collapse
Just keep it unlocked
rootSU said:
Guys,
We've seen several people have flashed system.img's and OTA's and ended up in a bootloop.. Not the end of the world really, BUT for some reason, before you can unlock your bootloader using fastboot, you must enable OEM unlock in Developer options in Android settings - which you cannot do if you are bootlooping.
If you still have a custom recovery, you'll be fine but if you're 100%, locked bootloader and bootlooping, we haven't found a fix yet so please do not lock your bootloader.
If you feel you absolutely must relock your bootloader (at your own risk) please boot the phone up to check it works properly before doing this. If you intend flashing roms and kernels or custom recoveries, locking the bootlaoder is not a good idea
Click to expand...
Click to collapse
I had this boot loop also, but clearing Cache and Dalvik seemed to fix the loop for me.
nyteryder79 said:
I had this boot loop also, but clearing Cache and Dalvik seemed to fix the loop for me.
Click to expand...
Click to collapse
Thats good.
http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833
This may help if you got stuck in a bootloop.
is there a fix if my mem shows i own a 32g device when i bought a 64g device, im unlocked/rooted and on custom rom?
darren.wlsn1 said:
is there a fix if my mem shows i own a 32g device when i bought a 64g device, im unlocked/rooted and on custom rom?
Click to expand...
Click to collapse
I'd like to know too. I'm unrooted, stock everything, with 64GB Blue, but it shows 23GB total space for the device with 16GB available. Was fine before the 5.1 update.
Marcellus1 said:
I'd like to know too. I'm unrooted, stock everything, with 64GB Blue, but it shows 23GB total space for the device with 16GB available. Was fine before the 5.1 update.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=58201783&postcount=106
should help
darren.wlsn1 said:
is there a fix if my mem shows i own a 32g device when i bought a 64g device, im unlocked/rooted and on custom rom?
Click to expand...
Click to collapse
Marcellus1 said:
I'd like to know too. I'm unrooted, stock everything, with 64GB Blue, but it shows 23GB total space for the device with 16GB available. Was fine before the 5.1 update.
Click to expand...
Click to collapse
Factory reset?
Not really the thread to ask this though.
rootSU said:
Factory reset?
Not really the thread to ask this though.
Click to expand...
Click to collapse
Thanks, and sorry
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
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
I'm currently unrooted on locked bootloader, and I'd like to keep my phone encrypted.
I read that newer versions of TWRP work with an encrypted device, but can I unlock the bootloader while keeping the phone encryted?
The process of unlocking your bootloader will wipe it, not rooting it or loading twrp. Your phone will still be encrypted when your done unlocking the bootloader. I imagine it's a safety feature if someone steals your phone that it wipes it if they try breaking in by unlocking the phone.
JeffBea said:
The process of unlocking your bootloader will wipe it, not rooting it or loading twrp. Your phone will still be encrypted when your done unlocking the bootloader. I imagine it's a safety feature if someone steals your phone that it wipes it if they try breaking in by unlocking the phone.
Click to expand...
Click to collapse
Thank you! So I can unlock the bootloader and then flash TWRP while keeping the encryption?
Yes
So change the pin code used for accessing the encryption key (which can be different than the short screen unlock one)
Otherwise encryption is useless (default password is... "default_password")
rchtk said:
So change the pin code used for accessing the encryption key (which can be different than the short screen unlock one)
Otherwise encryption is useless (default password is... "default_password")
Click to expand...
Click to collapse
Yea you're right but if attempting to break into a phone through twrp with " default_password" as pass code won't work. It won't recognize that value
rchtk said:
So change the pin code used for accessing the encryption key (which can be different than the short screen unlock one)
Otherwise encryption is useless (default password is... "default_password")
Click to expand...
Click to collapse
dontbeweakvato said:
Yea you're right but if attempting to break into a phone through twrp with " default_password" as pass code won't work. It won't recognize that value
Click to expand...
Click to collapse
I'm pretty sure both are the same no matter what you do. The code you'll have to enter on TWRP will get set once first boot is done and pattern or pin or passcode is selected during setup. That's the key that'll let twrp decrypt the partitions. If you ever flag a new ROM and change the method, it'll also change for TWRP as well.
Jammol said:
I'm pretty sure both are the same no matter what you do. The code you'll have to enter on TWRP will get set once first boot is done and pattern or pin or passcode is selected during setup. That's the key that'll let twrp decrypt the partitions. If you ever flag a new ROM and change the method, it'll also change for TWRP as well.
Click to expand...
Click to collapse
Not sure if I understand correctly what you mean but decryption key can be different from unlock pin. There's an API to change the decryption key so there are apps to make a super long decryption key while still having a small unlock pin code CM even integrated this distinction in their settings menu.
People have asked this feature to google for ages (as well as reboot after x wrong pin code) but they are still waiting..
rchtk said:
Not sure if I understand correctly what you mean but decryption key can be different from unlock pin. There's an API to change the decryption key so there are apps to make a super long decryption key while still having a small unlock pin code CM even integrated this distinction in their settings menu.
People have asked this feature to google for ages (as well as reboot after x wrong pin code) but they are still waiting..
Click to expand...
Click to collapse
Now I see what you're talking about. The original postings looked like you guys were talking about them being different on stock.