One Plus Two (chinese version), oxygen os 2.0.2, twrp recovery & supersu.
If I try to encrypt the phone storage (settings -> security), accepting all the warning, the android robot appears a few seconds, then the phone reboots itself, but the device is not encrypted.
Any ideas?
Thanks!
I've tried also to do it in safe mode, but the same result, reboots and the device is not encrypted
I wiped the device and started from scratch and now it works
I think that it was my mistake because I was trying to encrypt it using PIN protection instead password... so maybe I didn't need to wipe it but...
Same problem on OneA2001
e-Minguez said:
I wiped the device and started from scratch and now it works
I think that it was my mistake because I was trying to encrypt it using PIN protection instead password... so maybe I didn't need to wipe it but...
Click to expand...
Click to collapse
Can anybody provide more details on this issue? Im having the exact same problem; Phone is 100% charged, Click encrypt and the phone briefly reboots but doesnt encrypt. Ive tried both PIN and Password as options but neither seems to work....
If you are using twrp I don't think it works. They don't support encryption on the OPT yet.
Sent from my ONE A2003 using Tapatalk
da_anton said:
If you are using twrp I don't think it works. They don't support encryption on the OPT yet.
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
Twrp cannot read your internal storage, but you can sideload otas, zips,...
Try a full wipe and encrypt it before starting to install apps... (it worked for me...)
if you encrypt while in OxyOS 2 you can keep the encryption and move forward with OxyOS 3 and onto other custom ROMs.
OS 3.1.0 | TWRP 3.0.2 - 2: encryption ?
Hello Team,
I have similar problem with encryption.
device configuration:
- Latest stock os 3.1.0
- TWRP 3.0.2-2
- root
- fully wiped
when I choise encrypt, phone reboots to bootanimation (spinig wheels) and do not go futher. Device left c.a 12h at this state and afer reboot no encryption.
As 3.1.0 is quite fresh compilation, there is not much at net about. Do you have any possibile solutions?
thnx
Encrypt for corporate e-mail and calendar access
Hi Guys, I have the same issue (Cannot encrypt my One Plus 2) , my settings:
Model - ONE A2011
OxygenOS - 3.5.8
Tried with pin and password, it justs reboots the device and doesn't encrypt.
I need the to encrypt in order to have access to corporate e-mail and calendar.
Thanks for the help.
Related
I have a new Galaxy Note 3 (having bricked one trying to understand why it wouldn't encrypt) and now with a full stock rom I still find that the phone is impossible to encrypt.
I have an encrypted SD card in it. (only thing I can think of that might be causing problems)..
Settings > General > Security > Encrypt Device keeps stopping after a single shutdown,
How the heck do I encrypt this thing?? - Am I missing the blindingly obvious..
Thanks
tahnoonp said:
I have a new Galaxy Note 3 (having bricked one trying to understand why it wouldn't encrypt) and now with a full stock rom I still find that the phone is impossible to encrypt.
I have an encrypted SD card in it. (only thing I can think of that might be causing problems)..
Settings > General > Security > Encrypt Device keeps stopping after a single shutdown,
How the heck do I encrypt this thing?? - Am I missing the blindingly obvious..
Thanks
Click to expand...
Click to collapse
I'm having the exact same issue. Encryption is requited to get my work email and I can't get it to go.
Finally got mine to encrypt
Took me a bunch of tries.. and finally once i opened a chat with samsung support it finally worked.. i was at 100% charge, plugged into the wall and if finally worked. not sure if thats a bug in its detection if your over the stated 80% or not... good luck.. i finally got it working though.. only did a fast encryption as it didn't work on previous tries either way... so i just chose one and tried it again.
tahnoonp said:
I have a new Galaxy Note 3 (having bricked one trying to understand why it wouldn't encrypt) and now with a full stock rom I still find that the phone is impossible to encrypt.
I have an encrypted SD card in it. (only thing I can think of that might be causing problems)..
Settings > General > Security > Encrypt Device keeps stopping after a single shutdown,
How the heck do I encrypt this thing?? - Am I missing the blindingly obvious..
Thanks
Click to expand...
Click to collapse
I have the Google Policy Manager and Encryption is required for me too. I started at 81% and the first time I did it, it just rebooted. The second time I did it it worked like it was suppose to. Try it again right after it reboots and see if it works.
Make sure the phone is charged and keep trying over and over.
It will work eventually.
I gave up. I'm using touchdown now for work email which will allow me to skip full device encryption
Sent from my SM-N900V using Tapatalk
Same problem here, it will not encrypt
....help please
This is the answer I found doing a couple of root and unroot
1.If you encrypt the device and then root it you will net get past the passcode in the phone (black screen)
2. If you root the phone first and ten try to encrypt you will get the problems mentioned in this thread
..any tips how to get the phone rooted and then encrypted?
greffel said:
This is the answer I found doing a couple of root and unroot
1.If you encrypt the device and then root it you will net get past the passcode in the phone (black screen)
2. If you root the phone first and ten try to encrypt you will get the problems mentioned in this thread
..any tips how to get the phone rooted and then encrypted?
Click to expand...
Click to collapse
Bump. I'm looking for this answer too.
digittante said:
Bump. I'm looking for this answer too.
Click to expand...
Click to collapse
anyone at all? im stuck. Bump!
was having a similar problem on nexus 4 but safe mode helped there.
dind't help on my new n3. shouldn't have rooted before encrypting.
tried pressing encrypt about 10 times.
tried boot into recovery + wipe . also tried safe mode. also tried unroot + factory reset (pretty sure recovery + wipe /data is the same as reset user data from settings).
waiting for the firmware image to download - decided to try a firmware reflash
and then before flashing it I tried rebooting to recovery and powering off and encrypting and it worked. or maybe it was that random 12th time it worked because of an unrelated reason.
and after trying to root it again it just booted to a black screen after cf-root and enter encryption password screen.
*sigh*
My Work-Around
svyr said:
and then before flashing it I tried rebooting to recovery and powering off and encrypting and it worked. or maybe it was that random 12th time it worked because of an unrelated reason.
and after trying to root it again it just booted to a black screen after cf-root and enter encryption password screen.
*sigh*
Click to expand...
Click to collapse
I'm an AT&T customer, but I bought a T Mobile Note 3 off of Craigslist, unlocked it, rooted using Chainfire's ODIN thread, and then used the RegionFree Lock Away app. I was unable to encrypt just like you guys until I did the following. Flashed TWRP tar file from the TWRP site using ODIN. Rebooted into recovery and made an image, backup up everything, just in case. Rebooted and went in the SU Superuser application that Chainfire originally installed and uninstalled through the settings in the program. Once I rebooted I was able to encrypt the device (without fast method), I already had my SD Card encrypted. Once I encrypted the device I downloaded Kingo Root at the advice of DesignGears and used the one click root application from the Kingo Root site (google it.) After I did that, I now have full root access back, encryption, and never had to uninstall the region lock, so I didn't lose phone connectivity, applications, or anything else during the process. I recommend using TitaniumBackup and syncing via Google Drive or Dropbox before you start the process so you can restore your apps and data, once again, just in case.
encrypted ATT Note 3 not able to root
I was able to unroot my ATT Note 3 and then encrypted it. But Kingo Root failed to root the device. (I used it to root the phone once previously)
Now I stuck in a status with encrypted phone not able to root anymore.
Any suggestions please?
GHolbrook4 said:
I'm an AT&T customer, but I bought a T Mobile Note 3 off of Craigslist, unlocked it, rooted using Chainfire's ODIN thread, and then used the RegionFree Lock Away app. I was unable to encrypt just like you guys until I did the following. Flashed TWRP tar file from the TWRP site using ODIN. Rebooted into recovery and made an image, backup up everything, just in case. Rebooted and went in the SU Superuser application that Chainfire originally installed and uninstalled through the settings in the program. Once I rebooted I was able to encrypt the device (without fast method), I already had my SD Card encrypted. Once I encrypted the device I downloaded Kingo Root at the advice of DesignGears and used the one click root application from the Kingo Root site (google it.) After I did that, I now have full root access back, encryption, and never had to uninstall the region lock, so I didn't lose phone connectivity, applications, or anything else during the process. I recommend using TitaniumBackup and syncing via Google Drive or Dropbox before you start the process so you can restore your apps and data, once again, just in case.
Click to expand...
Click to collapse
I was able to get mine to encrypt after killing the bloat apps. All Google sync, amazon, and Verizon services. I can't say which one was killing it since it stopped pretty much every app or service that wasn't critical to the device.
Can anyone confirm that Encryption will never work once we root our phone ?
nlatifolia said:
Can anyone confirm that Encryption will never work once we root our phone ?
Click to expand...
Click to collapse
Same question here... Anyone was able to encrypt after being rooted???
Same question, rooted can't encrypt.
Just got a note 3 and this is an old thread. So wanted to update this question.
To encrypt device after root all that is needed to do is run the following command from terminal or adb shell as root. You must have the latest busybox installed.
pkill -KILL daemonsu
After running this command you should be back at the "$" prompt and out of root. Do not run su again.
Then encrypt your device. Encryption should work fine. Once rebooted you will have root again.
I had to repeat the above steps because I ran su again. Running su restarts daemonsu.
Good luck
Hi,
I was able to root and encrypt my sm-n900 note3 using the steps mentioned on this post:
http://forum.xda-developers.com/showthread.php?t=2791587
Just make sure that you have your backups ready case something goes wrong
I've installed the bloatwares after rooting and encrypt.
Hi,
I installed a recent nightly and everything is fine, however, when restoring my TWRP backup (CM10.2), my encryption password is no longer recognised and system won't boot.
The password is accepted by TWRP and also by restoring the OMNI password, but when I restore the CM10.2 image, the password is not accepted.
Has anything major changed in dm-crypt?
Thanks.
Yes, 4.4 changed the encryption algorithm to use scrypt. It was converted when you upgraded, so you won't be able to switch between without removing the encryption
Sent from my Nexus 5
Mevordel said:
Yes, 4.4 changed the encryption algorithm to use scrypt. It was converted when you upgraded, so you won't be able to switch between without removing the encryption
Click to expand...
Click to collapse
Thanks, I had to remove encryption, restore and encrypt it again.
Looks like I have to wait a while until all features are added into omnirom (quiet hours, battery percentage (!) etc).
If you have the security feature Secure startup enabled, which requires you to enter your password/pin/pattern before your phone boots up, sRGB mode will reset every time. After turning secure start-up off, sRGB mode will stick and you won't need to re-enable it after every reboot. You can disable/enable this feature by going into security and resetting your password
Thanks for the tip, seems to work :good:
Any idea why I can't disable the secure startup feature? I've tried turning password on/off repeatedly, and it never gives me that option again.
amirfk12 said:
Any idea why I can't disable the secure startup feature? I've tried turning password on/off repeatedly, and it never gives me that option again.
Click to expand...
Click to collapse
You need to change it to another security type. For example if you have a PIN change it to pattern and back or vice versa
tried that. didn't work. any other ideas?
I never set secure startup and mine reset every reboot. Since I reboot every day.
Sent from my Nexus 6P using XDA Free mobile app
I can't turn off the secure reset feature as well. I tried changing from pattern to pin to password and still no dice. I even factory reset to see if that would help and it didn't. Maybe a bug that will get fixed in a future update.
Sent from my Nexus 6P using Tapatalk
Can not remove the secure startup
uknowme4me said:
I can't turn off the secure reset feature as well. I tried changing from pattern to pin to password and still no dice. I even factory reset to see if that would help and it didn't. Maybe a bug that will get fixed in a future update.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Did you factory reset through recovery mode or through backup and reset setting?
I did it through both. I just got my 64gb frost 6P yesterday and it does the same exact thing. I'm thinking a software bug.
Sent from my Nexus 6P using Tapatalk
uknowme4me said:
I did it through both. I just got my 64gb frost 6P yesterday and it does the same exact thing. I'm thinking a software bug.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
yeah, was chatting with Google CS....wiped cache, didn't work and so they suggested factory reset. if it didn't work for you, i don't think i'm going to do it
My 6P requires patern before boot up and sRGB does not reset by itself.
Sent from my Nexus 6P using Tapatalk
That did the trick! Thank you!
For those of you still having issues, here are the steps: Settings > Security > Screen Lock (top option on this page) > confirm your password/pattern/etc. > choose a new one (can be the same as before) > THEN you choose the "Secure Start-up" yes or no. CHOOSE " No Thanks" ...Problem solved. Well, for me at least.
Absolutely 100% stock
Non rooted
Build number MDB08K
enhancedcollagen said:
If you have the security feature Secure startup enabled, which requires you to enter your password/pin/pattern before your phone boots up, sRGB mode will reset every time. After turning secure start-up off, sRGB mode will stick and you won't need to re-enable it after every reboot. You can disable/enable this feature by going into security and resetting your password
Click to expand...
Click to collapse
if you disable Secure startup doesn't that make device encryption useless?
I'm having this issue too with my Nexus 6p running Nougat. I'm unable to turn off secure startup. I've tried a factory reset through recovery and that didn't help. I wonder if it's some kind of issue with the OTA. I wish they would hurry up and make the factory image available so I could try flashing it to see if that somehow fixes it. The odd thing is that while running marshmallow I had secure startup in place, but sRGB stuck during a restart. I'm also wondering if decrypting would resolve the issue since that would basically disable secure startup, but I'm reluctant to do that because I'm getting tired of setting up my phone again and again. The other reason I'm reluctant is because my phone was decrypted until I pushed the nougat OTA. If I'm going to go to the trouble of decrypting my phone just to have another OTA encrypt it in the future, I'd rather not bother. Does anyone know whether flashing factory image (not necessarily an OTA) always encrypts the device? (Sorry for my wordiness)
chaddesch said:
I'm having this issue too with my Nexus 6p running Nougat. I'm unable to turn off secure startup. I've tried a factory reset through recovery and that didn't help. I wonder if it's some kind of issue with the OTA. I wish they would hurry up and make the factory image available so I could try flashing it to see if that somehow fixes it. The odd thing is that while running marshmallow I had secure startup in place, but sRGB stuck during a restart. I'm also wondering if decrypting would resolve the issue since that would basically disable secure startup, but I'm reluctant to do that because I'm getting tired of setting up my phone again and again. The other reason I'm reluctant is because my phone was decrypted until I pushed the nougat OTA. If I'm going to go to the trouble of decrypting my phone just to have another OTA encrypt it in the future, I'd rather not bother. Does anyone know whether flashing factory image (not necessarily an OTA) always encrypts the device? (Sorry for my wordiness)
Click to expand...
Click to collapse
Yes. Every OTA will force encryption due to the "forceencrypt" flag in the boot.img. Flashing SuperSU, modified boot.img, or custom kernel will turn that off and keep you decrypted, if you are decrypted.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Yes. Every OTA will force encryption due to the "forceencrypt" flag in the boot.img. Flashing SuperSU, modified boot.img, or custom kernel will turn that off and keep you decrypted, if you are decrypted.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thanks for the quick reply, SlimSnoopOS. Can I infer that as long as I'm not flashing an OTA and just the system image from the factory image (not the boot image) then it won't screw with the decryption?
chaddesch said:
Thanks for the quick reply, SlimSnoopOS. Can I infer that as long as I'm not flashing an OTA and just the system image from the factory image (not the boot image) then it won't screw with the decryption?
Click to expand...
Click to collapse
It won't but there's nothing wrong with ADB Sideload the OTA zip or manually flashing boot, system and vendor. Just make sure to go directly into TWRP (do not boot into the rom) and flash superuser/custom kernel before booting up to stay decrypted. I've manually installed each OTA and kept decrypted doing those steps.
Sent from my Nexus 5X using Tapatalk
I recently bought a Nexus 6P and I just rooted it a few days ago. I have been reading about how it is less safe now that the bootloader is unlocked, so I figured I could encrypt my phone for more securities! I don't want ro re-lock since unlocking will wipe my data all over again.
So I went into Settings->Encrypt phone and started the encryption process. It first showed a green outline of an Android, then it started the boot animation. It stayed there for about half an hour and it was clearly not encrypting (not getting hot or anything) so I just rebooted (I have a backup, that's why I'm so bold ) and it just normally rebooted to a working phone with nothing encrypted. Tried it again, same result.
I'm running Marshmallow 6.0.1 MMB29M with TWRP, SuperSU (I'm pretty sure it's systemless) and Xposed. I'm not sure what kernel I flashed when I rooted (that is the boot.img, right?).
Is this a bug? Is it a feature? I would like to be able to encrypt my phone; does anyone have any ideas on how to achieve this, now that TWRP can decrypt stuff?
Thanks!
I have the same issue with a HTC One M8 running Marshmallow 6.0 and systemless root. I've had this phone encrypted in the past but that was with standard root. Seems like systemless root and something to do with the modification of the boot image has something to do with encryption breaking.
Glad I made a nandroid before starting also, just incase.
I got it to work
So I just flashed the latest 6.0.1 (MMB29P) system, boot, etc. partitions because of the January security update. I folllowed Heisenberg's guide, point 10. I then had to reflash TWRP and then install SuperSU and Xposed again, because they were gone.
What this did was re-encrypt the phone, but with the default password. This basically offers no protection, with the added benefit of processor overhead. Yay I noticed this because it said the phone is encrypted, in Settings->Security even though it did not ask for a password at boot-time or in TWRP.
What you need to do is to remove any security you set up (just set the lockscreen unlock to "None") and then re-add it. When the phone asks if you want it to require the password at startup, say yes. It will then change the encryption password to your custom one and voila, your phone is now encrypted and uses your password/pin/pattern/whatev.
tudy77 said:
What this did was re-encrypt the phone, but with the default password. This basically offers no protection, with the added benefit of processor overhead. Yay I noticed this because it said the phone is encrypted, in Settings->Security even though it did not ask for a password at boot-time or in TWRP.
Click to expand...
Click to collapse
Question, is the default password: "default_password" lowercase and all? Im on the same boat you were, about to do this just to get encryption back but i want to be 100% sure of the steps lol
Well that's what I read here, but I never actually typed it anywhere because, from what I understand, it gets completed automatically by TWRP or Android of it is the default one.
Sent from my Nexus 6P using Tapatalk
tudy77 said:
Well that's what I read here, but I never actually typed it anywhere because, from what I understand, it gets completed automatically by TWRP or Android of it is the default one.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
so i dont type anything just hit enter?
I was not prompted to type anything
Sent from my Nexus 6P using Tapatalk
EDIT 10/30/2016:
From some of the replies on this thread, I have reached the conclusion that this is not a widespread problem (duh.)
However, if you are locked out of your Nexus after a restore, I have found that the best solution was given by @toknitup420
Best Solution:
In TWRP (or ADB whatever you prefer) go into Advanced --> File Manager and navigate to /data/system/.
Locate locksettings.db and rename/delete it.
Reboot, unlock device, go to Settings --> Security and set a new screen lock passcode. The best part about this solution is that your previously registered fingerprints still work (mine did.)
Some suggested updating TWRP to the latest unofficial 3.0.2-3.
Flashing this version and restoring using it did not fix the issue for me personally, but if you would like to try then here is the link I found searching XDA.
**************************************************
OP:
Disclaimer: I am an XDA n00b, I've frequented these forums for a long while now, but I have never made an account and actually posted until now.
Also, I am using build NRD90U on my Nexus 6p
Not sure if anyone else has had these issues, but last night I had problems restoring from a nandroid backup on TWRP.
First issue:
TWRP would not restore System + Vendor + Data all in one operation. During the Data portion of the restore, it threw an error and cancelled the operation (for the life of me I wish I wrote it down, it was 3am and I just wanted to sleep.)
The Fix: I had to first restore System + Vendor, then reboot back into TWRP. Upon rebooting, TWRP prompts to allow modification of system. I accepted (by swiping) and proceeded to restore ONLY the Data from the nandroid backup.
Second issue:
Upon booting into my fully restored phone, I got locked out of the lockscreen. My pattern would not work, and no matter how many times I tried, I could not get to the "Forgot Pattern?" prompt so that I could change my password. Great.
The Fix: No option but to factory restore. I just booted into fastboot, followed Heisenberg's Flash Guide for the Nexus 6p Step 9 to flash everything except for my Internal Storage partition. Booted into a fresh version of android Nougat, and restored from a Titanium Backup.
I haven't seen any information or talk of turning off the passcode before backing up android in TWRP, but I suspect you should do this to avoid a fully restored system that you are locked out of . (Note: I am not talking about the passcode to boot feature, that was turned off for me in this case, and you should too because this is well known to cause issues when restoring. I am referring to the passcode at the actual lockscreen)
TLDR; Restore Data partition after restoring System + Vendor and reboot back into recovery, and turn off all passcode features before creating a nandroid backup.
This is a known topic, nothing new lol.
tatico28 said:
This is a known topic, nothing new lol.
Click to expand...
Click to collapse
Thanks for acknowledging the disclaimer, just trying to help folks on Google. I didn't find out about it until it was too late.
aeg3d said:
Disclaimer: I am an XDA n00b, I've frequented these forums for a long while now, but I have never made an account and actually posted until now.
Also, I am using build NRD90U on my Nexus 6p
Not sure if anyone else has had these issues, but last night I had problems restoring from a nandroid backup on TWRP.
First issue:
TWRP would not restore System + Vendor + Data all in one operation. During the Data portion of the restore, it threw an error and cancelled the operation (for the life of me I wish I wrote it down, it was 3am and I just wanted to sleep.)
The Fix: I had to first restore System + Vendor, then reboot back into TWRP. Upon rebooting, TWRP prompts to allow modification of system. I accepted (by swiping) and proceeded to restore ONLY the Data from the nandroid backup.
Second issue:
Upon booting into my fully restored phone, I got locked out of the lockscreen. My pattern would not work, and no matter how many times I tried, I could not get to the "Forgot Pattern?" prompt so that I could change my password. Great.
The Fix: No option but to factory restore. I just booted into fastboot, followed Heisenberg's Flash Guide for the Nexus 6p Step 9 to flash everything except for my Internal Storage partition. Booted into a fresh version of android Nougat, and restored from a Titanium Backup.
I haven't seen any information or talk of turning off the passcode before backing up android in TWRP, but I suspect you should do this to avoid a fully restored system that you are locked out of . (Note: I am not talking about the passcode to boot feature, that was turned off for me in this case, and you should too because this is well known to cause issues when restoring. I am referring to the passcode at the actual lockscreen)
TLDR; Restore Data partition after restoring System + Vendor and reboot back into recovery, and turn off all passcode features before creating a nandroid backup.
Click to expand...
Click to collapse
"Warning: before you make a backup with TWRP you must remove all lockscreen security. If you do not do this you will not be able to unlock your device after restoring your backup (entering your pin will result in an "incorrect pin" message), you'll be forced to perform a factory reset to boot into Android. To remove lockscreen security go to Settings>Security>Screen Lock and set it to swipe/none."
I have two pins. One to unlock sim and one to unlock phone. I'm not sure which one you're referring to because I didn't turn off my pin to unlock sim card and I didn't get locked out after restore.
What did stump me was getting a half working phone since the restore included vendor.img which no one said to uncheck before restoring.
tropical cactus said:
I have two pins. One to unlock sim and one to unlock phone. I'm not sure which one you're referring to because I didn't turn off my pin to unlock sim card and I didn't get locked out after restore.
Click to expand...
Click to collapse
Ah, that is a feature that I do not use and didn't consider. What I was referring to was turning off the lock screen passcode (boot passcode should also be off, this is a known issue)
tropical cactus said:
What did stump me was getting a half working phone since the restore included vendor.img which no one said to uncheck before restoring.
Click to expand...
Click to collapse
Ah yes it is very unclear exactly what to have checked/unchecked for TWRP. I've always been under the impression a System + Vendor + Data backup is sufficient, maybe also check the EFS for extra security (you should back up EFS at least once and keep in a safe place, your phone depends on this to connect to cell towers. If it's corrupted and you have no backup, you're in trouble)
I use TWRP 3.0.2.3 and nandroids restored fine on 7.0 and 7.1 DP with lock screen pin enabled
Sent from my Nexus 6P using Tapatalk
scoot0073 said:
I use TWRP 3.0.2.3 and nandroids restored fine on 7.0 and 7.1 DP with lock screen pin enabled
Click to expand...
Click to collapse
Perhaps it's because I was using TWRP 3.0.2-2.. I'll have to try again later tonight to see if that's the case.
Good to know though, maybe what I experienced is an isolated issue.
3.0.2.2 I believe if I remember I had to disable security lock screen pin b4 I made a nandroid.
But the unofficial 3.0.2.3 not the case
Sent from my Nexus 6P using Tapatalk
aeg3d said:
Disclaimer: I am an XDA n00b, I've frequented these forums for a long while now, but I have never made an account and actually posted until now.
Also, I am using build NRD90U on my Nexus 6p
Not sure if anyone else has had these issues, but last night I had problems restoring from a nandroid backup on TWRP.
First issue:
TWRP would not restore System + Vendor + Data all in one operation. During the Data portion of the restore, it threw an error and cancelled the operation (for the life of me I wish I wrote it down, it was 3am and I just wanted to sleep.)
The Fix: I had to first restore System + Vendor, then reboot back into TWRP. Upon rebooting, TWRP prompts to allow modification of system. I accepted (by swiping) and proceeded to restore ONLY the Data from the nandroid backup.
Second issue:
Upon booting into my fully restored phone, I got locked out of the lockscreen. My pattern would not work, and no matter how many times I tried, I could not get to the "Forgot Pattern?" prompt so that I could change my password. Great.
The Fix: No option but to factory restore. I just booted into fastboot, followed Heisenberg's Flash Guide for the Nexus 6p Step 9 to flash everything except for my Internal Storage partition. Booted into a fresh version of android Nougat, and restored from a Titanium Backup.
I haven't seen any information or talk of turning off the passcode before backing up android in TWRP, but I suspect you should do this to avoid a fully restored system that you are locked out of . (Note: I am not talking about the passcode to boot feature, that was turned off for me in this case, and you should too because this is well known to cause issues when restoring. I am referring to the passcode at the actual lockscreen)
TLDR; Restore Data partition after restoring System + Vendor and reboot back into recovery, and turn off all passcode features before creating a nandroid backup.
Click to expand...
Click to collapse
All you needed to do was delete locksettings.db in twrp before rebooting. That deletes lock screen security pin. Then you can just reboot and add pin back in settings. Easy.
toknitup420 said:
All you needed to do was delete locksettings.db in twrp before rebooting. That deletes lock screen security pin. Then you can just reboot and add pin back in settings. Easy.
Click to expand...
Click to collapse
I thought I read somewhere on XDA that this could potentially break the feature (a.k.a. wouldn't be able to reset a new passcode after getting access to homescreen.)
aeg3d said:
I thought I read somewhere on XDA that this could potentially break the feature (a.k.a. wouldn't be able to reset a new passcode after getting access to homescreen.)
Click to expand...
Click to collapse
I've been doing it like that for months now with no issues.
toknitup420 said:
I've been doing it like that for months now with no issues.
Click to expand...
Click to collapse
OK I'll have to try that as well, others seem to say it was an error that was patched in the latest TWRP (I was apparently using a slightly older version). Thanks for the tip!
scoot0073 said:
3.0.2.2 I believe if I remember I had to disable security lock screen pin b4 I made a nandroid.
But the unofficial 3.0.2.3 not the case
Click to expand...
Click to collapse
OK that seems to be the consensus, that I was using a slightly older version of TWRP with this bug. Going to flash tonight to confirm!