Hello,
I recently decided to look into encrypting my Nexus 4 running stock 5.1.1, but have a few questions before doing so.
I have a handful of modifications, including custom kernel, root, and xposed. Would any of these prevent me from encrypting my device, or cause problems afterwards?
I am planning on making a full twrp backup prior to the process, but if I encounter a problem during the encrypting process or realize that encryption isn't for me , will I be able to simply restore my nandroid and my device will restore without issue?
In order to reverse encryption, does the device need to be factory reset, or will just a restore reverse the encryption? If I made a nandroid backup while my device is encrypted and tried to restore it after my device is no longer encrypted would it restore without a problem, or would it restore the encryption with it?
Sorry for all the questions, I just want to ensure my data stays protected during this process. Thanks in advance.
I would recommend not to do. Our N4 does not have hardware support for encryption so losing a little performance.
xim4 said:
I would recommend not to do. Our N4 does not have hardware support for encryption so losing a little performance.
Click to expand...
Click to collapse
Thank you for response. I went ahead and encrypted the device and I am not noticing any real world performance decrease. I don't play any games on my device, and use it for regular use. If I notice any issues, I will format and reactor my backup. Thanks again.
Related
Hey guys,
So I recently updated to KitKat 4.4.2 from 4.3 whatever, and it's been really nice. However, my battery length plummeted, and w/o root, I do not know what to do. So, I'm asking to see if anyone knows how to either root the XT926 or downgrade to 4.3?
Thanks
Neither are possible.
Even with an unlocked bootloader, you would you never get to 4.3 because 4.3 was never released for this phone.
As for battery, when you updated to Kit Kat, did you do so with all your apps installed, etc and not do a Factory Data Reset?
I would really encourage users to do the following before taking the OTA:
Backup whatever data you can to your PC or external SD card (pictures, etc). If you are rooted (and have an unlocked bootloader), then use a tool such as Titanium Backup to backup your apps and their settings. If you're not rooted and/or have a locked bootloader, then you won't be able to retain your app settings with TiBu. Sorry. That's the glory of having root I guess.
Do a factory data reset BEFORE taking the upgrade. This will wipe out your user data completely, including application data.
Apply the OTA and profit.
I have found my battery life is just as good, if not better, than under JB. People who are having issues with Wifi, Blue Tooth, battery life, usually have not done a FDR on their phones, so you have old cache sitting around, etc, that bogs down the phone as well as causes a host of issues.
The same holds true when upgrading Windows on your PC (for those that use Windows). I always backup user profiles and then I go and do a complete fresh install. There is so much gunk that gets left behind that it's just best to wipe the slate clean and start anew. The same goes for upgrading the OS on your mobile phones, especially when going from JB to KK.
KK is much better than JB, especially on this phone. No way I go back to JB. No way, no how. :good:
iBolski said:
Backup whatever data you can to your PC or external SD card (pictures, etc). If you are rooted (and have an unlocked bootloader), then use a tool such as Titanium Backup to backup your apps and their settings. If you're not rooted and/or have a locked bootloader, then you won't be able to retain your app settings with TiBu. Sorry. That's the glory of having root I guess.
Do a factory data reset BEFORE taking the upgrade. This will wipe out your user data completely, including application data.
Apply the OTA and profit.
Click to expand...
Click to collapse
To be clear, you can restore apps with TiBu without root? Because root = bye bye after OTA, I've only used TiBu with root..Thx
Edit, reading on Motopocalypse now, very helpful thread pages 3 4 5
No soup for you without root
iBolski said:
Even with an unlocked bootloader, you would you never get to 4.3 because 4.3 was never released for this phone.
As for battery, when you updated to Kit Kat, did you do so with all your apps installed, etc and not do a Factory Data Reset?
I would really encourage users to do the following before taking the OTA:
Backup whatever data you can to your PC or external SD card (pictures, etc). If you are rooted (and have an unlocked bootloader), then use a tool such as Titanium Backup to backup your apps and their settings. If you're not rooted and/or have a locked bootloader, then you won't be able to retain your app settings with TiBu. Sorry. That's the glory of having root I guess.
Do a factory data reset BEFORE taking the upgrade. This will wipe out your user data completely, including application data.
Apply the OTA and profit.
I have found my battery life is just as good, if not better, than under JB. People who are having issues with Wifi, Blue Tooth, battery life, usually have not done a FDR on their phones, so you have old cache sitting around, etc, that bogs down the phone as well as causes a host of issues.
The same holds true when upgrading Windows on your PC (for those that use Windows). I always backup user profiles and then I go and do a complete fresh install. There is so much gunk that gets left behind that it's just best to wipe the slate clean and start anew. The same goes for upgrading the OS on your mobile phones, especially when going from JB to KK.
KK is much better than JB, especially on this phone. No way I go back to JB. No way, no how. :good:
Click to expand...
Click to collapse
I did a factory reset after I upgraded, doesn't that do the same thing?
Hi.
I've updated to 6.0.1 ,re rooted and spent some time setting up my apps and stuff.
I want to install exposed again but I want to backup before I do in case anything goes wrong.
I'm sure I read on here that there's a problem with restoring TRWP backups?
I've done a search but I cant seem to find anything definitive, could someone be kind enough to explain what the issue is (if any) and how I avoid any problems?
Thanks
Stret
Any Help ?
Twrp restore caused me bootloop, but after flashing a couple of factory images (e.g. vendor, boot, bootloader) i was able to boot back to my phone, but i can't unlock the phone with the passcode i originally set. Cause could be related to the encryption android originally placed on all our 6p's. You could try removing fingerprint and disabling passcode, but i can't guarantee anything. Or you could be like me, screw the backup and just flash xposed and be on your merry way.
There's little chance of going wrong with flashing xposed, as long as you flash the sdk23 for arm64
Has anyone had issues setting up Imprint after importing a nandroid backup?
I had to RMA my 6P due to a faulty charging port and I can successfully set up Imprint in the factory state, however, after I import the backup, it won't allow me to set it up.
I've tried to do just a data import, a full nandroid import...pretty much every single option and constantly reflashing to stock to retry. I'm at a loss because it's definitely not a hardware problem as I can set it up during stock.
As soon as I click next to train my fingerprints, it flashes: "Enrollment was not completed. Fingerprint enrollment didn't work. Try again or use a different finger."
Has anyone ever run into this issue? Thanks for your help!
Never and I mean never restore a nandroid from one device to another. There are device specific files in that nandroid. Just hope you didn't kill your efs partition which kills your IMEI and in turn makes it not connect to any network.
RaysBucsBolts said:
Has anyone had issues setting up Imprint after importing a nandroid backup?
I had to RMA my 6P due to a faulty charging port and I can successfully set up Imprint in the factory state, however, after I import the backup, it won't allow me to set it up.
I've tried to do just a data import, a full nandroid import...pretty much every single option and constantly reflashing to stock to retry. I'm at a loss because it's definitely not a hardware problem as I can set it up during stock.
As soon as I click next to train my fingerprints, it flashes: "Enrollment was not completed. Fingerprint enrollment didn't work. Try again or use a different finger."
Has anyone ever run into this issue? Thanks for your help!
Click to expand...
Click to collapse
As already stated you should never restore a backup from a different device. If you had a pin and fingerprint setup when you made the backup then it will not restore properly on any device. A thread has been pinned in the general section about TWRP'S issues with lockscreen security and backups.
If you can get into adb try this after restoring:
rm /data/system/locksettings.db
rm /data/system/*.key
If this doesnt work, go to twrp file manager and manually delete the files.
As mentioned above, before backing up you should always remove security.
It was mentioned in the TWRP thread that you should NEVER make a Nandroid Backup before disabling the fingerprint and swipe gestures. If you did a Nandroid Backup without having removed the security options first, you won´t be able to use it.
I am having the same issue after getting my new phone and trying to do the same thing. Each device seems to have some kind of Sensor ID or something else that stops the scanner from working. check out the reddit thread and this other thread on xda...
https://www.reddit.com/r/Nexus6P/comments/3vjkq3/q_nandroid_from_6p_to_6p_which_partitions_to/cxqfcl1
http://forum.xda-developers.com/nexus-6p/help/fingerprint-hardware-unavailable-t3274436
seems everyone has the same issue. No fix as of yet but twrp will work to restore all of your data including your android id from a nandroid im pretty sure
jerflash said:
I am having the same issue after getting my new phone and trying to do the same thing. Each device seems to have some kind of Sensor ID or something else that stops the scanner from working. check out the reddit thread and this other thread on xda...
https://www.reddit.com/r/Nexus6P/co...oid_from_6p_to_6p_which_partitions_to/cxqfcl1
http://forum.xda-developers.com/nexus-6p/help/fingerprint-hardware-unavailable-t3274436
seems everyone has the same issue. No fix as of yet but twrp will work to restore all of your data including your android id from a nandroid im pretty sure
Click to expand...
Click to collapse
Of course each one has its own ID.
This is not what Nandroids are for. Restoring this way you risk ruining your imei which then requires you to get a new device which warranty will not cover. So come on guys stop being lazy and do things properly. If you mess up your device then you have no else to blame but yourself.
And we wonder why OEM/Google are locking devices down.
zelendel said:
Of course each one has its own ID.
This is not what Nandroids are for. Restoring this way you risk ruining your imei which then requires you to get a new device which warranty will not cover. So come on guys stop being lazy and do things properly. If you mess up your device then you have no else to blame but yourself.
And we wonder why OEM/Google are locking devices down.
Click to expand...
Click to collapse
I would never tell anyone to restore EFS between two different devices! That could really mess things up. What we are talking about here is restoring the "Userdata" backup between two devices which can be safe if you know what you are doing...(I have done it for years without issue.) problem comes form there must be something hidden inside the userdata that stops you from restoring and using the fingerprint reader. Its actually a good feature for most if not a high level user.
I'm sure there will be a work around soon enough
jerflash said:
I would never tell anyone to restore EFS between two different devices! That could really mess things up. What we are talking about here is restoring the "Userdata" backup between two devices which can be safe if you know what you are doing...(I have done it for years without issue.) problem comes form there must be something hidden inside the userdata that stops you from restoring and using the fingerprint reader. Its actually a good feature for most if not a high level user.
I'm sure there will be a work around soon enough
Click to expand...
Click to collapse
More and more apps are not storing their info into data partition.
Wouldn't count on a work around. With the new Qualcomm security settings many oem are really looking at doing it like the BB android device which can't even be rooted.
Did you find a solution guys? I have same problem.
Tell you the truth guys... just use helium, then factory reset. let google re-add everything and for what does not use helium. i did this and it works for most things. not very annoying at all
Hello All!
Before you tell me to search or check threads, I already have. This problem does not have anything to do with forgetting to disable the pins and fingerprints before backing up. My problem has do do with I have already disabled/removed security before backing up my nandroid. I check/select everything that I can to backup and it successfully completes. When I go to restore, everything looks to be properly restored, but alas, there is a problem. When I reboot, it asks me for a password to get into TWRP (apparently "default_password). But when I get in and go to file explorer to find anything, my entire storage is wiped. Like no OS or any files. The only other issue I've had besides this is when restoring a nandroid, it doesn't complete and reboots to a bootloop.
I am on the newest version of TWRP, 3.0.3-0. Any help would be greatly appreciated as I, and anyone who has had to redo the complete phone setup/customization, do not enjoy taking over an hour to get things back up and running. Cruddy thing is I did a Titanium Backup for my apps and settings, but they got wiped.
boostin91tsi01 said:
Hello All!
Before you tell me to search or check threads, I already have. This problem does not have anything to do with forgetting to disable the pins and fingerprints before backing up. My problem has do do with I have already disabled/removed security before backing up my nandroid. I check/select everything that I can to backup and it successfully completes. When I go to restore, everything looks to be properly restored, but alas, there is a problem. When I reboot, it asks me for a password to get into TWRP (apparently "default_password). But when I get in and go to file explorer to find anything, my entire storage is wiped. Like no OS or any files. The only other issue I've had besides this is when restoring a nandroid, it doesn't complete and reboots to a bootloop.
I am on the newest version of TWRP, 3.0.3-0. Any help would be greatly appreciated as I, and anyone who has had to redo the complete phone setup/customization, do not enjoy taking over an hour to get things back up and running. Cruddy thing is I did a Titanium Backup for my apps and settings, but they got wiped.
Click to expand...
Click to collapse
I am genuinely interested in this because I back up on a regular basis after each security update but I have never had to restore. Now it is my understanding that even if security is disable the data is still encrypted. Perhaps I'm wrong about that but if you ever did have a password or pin to log into the phone with have you tried to enter that into TWRP?
Sent from my Nexus 6P using Tapatalk
You only need to back up the defaults... system, data, and boot.
What should I back up in TWRP?
https://twrp.me/faq/whattobackup.html
redduc900 said:
You only need to back up the defaults... system, data, and boot.
What should I back up in TWRP?
https://twrp.me/faq/whattobackup.html
Click to expand...
Click to collapse
I understand the web is full of opinions, but I've read somewhere to backup EFS? I have also read somewhere before that what you said to backup, while is plenty sufficient, if you have space, to backup everything. I followed that and it lead me to an hour plus of restoring back to how it was. I will give it a go, hoping that I never have to use it, but it will work when the situation arises.
I've only ever backed up those three partitions, and never had an issue with restoring backups. You can certainly create a backup of the EFS/IMEI, but keep it stored in a safe place like on your computer or a thumb drive. One thing I should note is when restoring a backup, make sure to also flash the correct vendor.img if necessary.
I usually backup vendor with it but as earlier indicated I don't believe it's completely necessary. As far as EFS is concerned yes I would agree with backing that up however what I do is back it up to a separate backup folder and only write it if something were to ever happen to it otherwise leave it alone. That way you don't take a chance I'm corrupting something in that partition.
Sent from my Nexus 6P using Tapatalk
I've never successfully restored a backup on the Nexus 6P regardless of what version of TWRP I used. Different builds of TWRP give me different problems but none has ever worked. I've completely given up doing nandroid backups on this phone because it's a waste of time and disc space. I never had a similar issue on any other phone that I have ever owned and am not a newbie when it comes to rooting and custom roms. What I always ended up doing after a problem restoring a backup is flash the complete factory image using the flash-all.bat command and start over with everything I want to flash.
jhs39 said:
I've never successfully restored a backup on the Nexus 6P regardless of what version of TWRP I used. Different builds of TWRP give me different problems but none has ever worked. I've completely given up doing nandroid backups on this phone because it's a waste of time and disc space. I never had a similar issue on any other phone that I have ever owned and am not a newbie when it comes to rooting and custom roms. What I always ended up doing after a problem restoring a backup is flash the complete factory image using the flash-all.bat command and start over with everything I want to flash.
Click to expand...
Click to collapse
I have the same problem, so now I've started doing a TiBU and Verizon Messages backup, after all those are completed, transfer and save it to my PC. If I have any problems, I transfer from the PC to phone and it's less headache... kinda sorta.
Restore never worked to the fullest. I tried different versions of TWRP, same problem. Restore starts a red error line in beginning of the restore process an at the end it shows ‘Restore complete’. When I restart, everything looks restored but with bugs like:
-network or sim itself is not shown
-Bluetooth, wifi wont connect
-Quicksetting tiles not responding etc…
The idea of backing up via TWRP is to get every bit RESTORED properly, but it doesn’t work.
I take a full back up before moving to update the firmware version (example MIUI 10), if I do not like the firmware then I want to go back to the previous firmware version (example MIUI 9) and TWRP RESTORE feature never works. I have to again flash the rom and then restore everything via Titanium backup.
I always take a TWRP backup of all the items available:
System
Data
Cache
Cust
Recovery
Boot
EFS
Persist
Still it never restores properly. It’s a mere time waste or the restore option to be removed from TWRP as it never worked across of its versions.
Can anyone explain me in a line, what is Cust, EFS and Persist?
I really appreciate if anyone help me understand where I’m going wrong.
Hey there. While I was installing a Custom ROM, I did something incredibly stupid by factory resetting my phone whilst it was encrypted, thus effectively erasing the encryption keys. I am unable to access my data from things such as TWRP because no password is accepted.
Is there a way to re-encrypt my device with new encryption keys? I understand that I will not be recovering the keys I wiped so I figured if I started with an entirely new encryption, I would be able to create working keys again.
I am completely fine with losing personal data on this device.
Thank you.
JC_6a63 said:
Hey there. While I was installing a Custom ROM, I did something incredibly stupid by factory resetting my phone whilst it was encrypted, thus effectively erasing the encryption keys. I am unable to access my data from things such as TWRP because no password is accepted.
Is there a way to re-encrypt my device with new encryption keys? I understand that I will not be recovering the keys I wiped so I figured if I started with an entirely new encryption, I would be able to create working keys again.
I am completely fine with losing personal data on this device.
Thank you.
Click to expand...
Click to collapse
Pretty much anytime you find yourself in a pinch like this, the MSM Download Tool here on XDA is the best way to go. Have you tried that?
You can also try an OTG with pen drive. It's not encrypted so TWRP can read and flash files from it. Then clean flash a ROM.
Thank you both for your help. I will try these out later.
JC_6a63 said:
Hey there. While I was installing a Custom ROM, I did something incredibly stupid by factory resetting my phone whilst it was encrypted, thus effectively erasing the encryption keys. I am unable to access my data from things such as TWRP because no password is accepted.
Is there a way to re-encrypt my device with new encryption keys? I understand that I will not be recovering the keys I wiped so I figured if I started with an entirely new encryption, I would be able to create working keys again.
I am completely fine with losing personal data on this device.
Thank you.
Click to expand...
Click to collapse
Try simply to format data
Can I resurrect this thread, because I just did the same, stupid thing?
After a long time on the OB releases, when jumping to tresk I had forgotten the proper procedure so, of course, I ended up not able to access the FS from TWRP. I can see everything fine after I've booted, of course.
@VampireHeart I *had* formatted Data (actually, System, Data, Cache) before flashing so I'm not sure this will help?
@devilrulz4ever the OTG is a nice idea, but what is the proper 'clean' process? I must be getting old...
Thanks!
krakout said:
Can I resurrect this thread, because I just did the same, stupid thing?
After a long time on the OB releases, when jumping to tresk I had forgotten the proper procedure so, of course, I ended up not able to access the FS from TWRP. I can see everything fine after I've booted, of course.
@VampireHeart I *had* formatted Data (actually, System, Data, Cache) before flashing so I'm not sure this will help?
@devilrulz4ever the OTG is a nice idea, but what is the proper 'clean' process? I must be getting old...
Thanks!
Click to expand...
Click to collapse
Format data isn't wipe data, you find it at bottom of the screen into clean section, when you tap on that you may enter yes and confirm to make it, are two different thing.