Hi,
Just got my new Nexus 6 64GB. Rooted and I transferred my titanium backup files from my Galaxy Note 3. Everything went fine. 3 hour later all my apps are up and running and I'm peachy.
After that I was doing some reading a I stumbled upon the tutorial on how to disable encryption. I gave it a go and upon restart it asked me for my pin number. I enter the pin and then I get the message saying that the phone has to be reset. I hit reset and after the procedure finished phone rebooted and all my files where completely wiped clean. In all my previous phones I could do a reset and keep all my downloaded and backed up files. Is there a way to do this too with the nexus or every time I screw something up I will loose everything?
Stock recovery always resets /sdcard too. Custom recovery only /data and /cache, etc.
However, ALL your data is on an encrypted file system so the only way to decrypt is by reformatting the places that contain ALL the data
rootSU said:
Stock recovery always resets /sdcard too. Custom recovery only /data and /cache, etc.
However, ALL your data is on an encrypted file system so the only way to decrypt is by reformatting the places that contain ALL the data
Click to expand...
Click to collapse
Does this apply even if I disabled the encryption?
I love the phone but this is an issue for me. Please give me your opinion on which is the best way to go. I was thinking to not install a custom recovery so I can be able to do the OTA updates even thought I never owned a phone that I didn't root and install custom recovery and ROM from day one (Only have used Samsung Note Phones all these years). Is there a ROM that is based on the Original with encryption disabled and has some good tweaks and will be updated as soon as there is an update? Thanks for your help.
slekkas said:
Does this apply even if I disabled the encryption?
I love the phone but this is an issue for me. Please give me your opinion on which is the best way to go. I was thinking to not install a custom recovery so I can be able to do the OTA updates even thought I never owned a phone that I didn't root and install custom recovery and ROM from day one (Only have used Samsung Note Phones all these years). Is there a ROM that is based on the Original with encryption disabled and has some good tweaks and will be updated as soon as there is an update? Thanks for your help.
Click to expand...
Click to collapse
All phones that have "internal storage" their stock recovery wipes "sdcard" when you factory reset.
slekkas said:
Does this apply even if I disabled the encryption?
I love the phone but this is an issue for me. Please give me your opinion on which is the best way to go. I was thinking to not install a custom recovery so I can be able to do the OTA updates even thought I never owned a phone that I didn't root and install custom recovery and ROM from day one (Only have used Samsung Note Phones all these years). Is there a ROM that is based on the Original with encryption disabled and has some good tweaks and will be updated as soon as there is an update? Thanks for your help.
Click to expand...
Click to collapse
The ROMs have nothing to do with encryption. When you want to turn encryption off, all your data will be reset, there is no way around it.
However, once you have disabled encryption, then you can stay on a stock rooted ROM, or go to any ROM you like, your internal files will not be touched (data will be deleted though). If you were to stay on the stock rooted ROM, and then accept an OTA update, your phone will automatically encrypt on first boot afterwards. Most ROMs update within a day (if not hours) after the OTA update, so best bet is to flash than to accept OTA if you want to stay unencrypted.
When you wipe your phone in recovery yo flash a different ROM, you do a custom wipe, where you uncheck "internal storage", so your files/pictures/etc don't get deleted.
The cool thing about the N6 is the restore option. If you were to completely wipe right now and go to a different ROM, on first boot, upon logging in you will be asked if you want to restore a backup (if you have enabled backup apps, data, WiFi passwords for your google account). If you select yes, all your apps will automatically be downloaded from the play store, you won't have to do it manually. However, I have seen data for the app is not restored, but you can log into most apps and most games save your progress on the cloud now.
Related
Please help, my nexus was unlocked rooted with trinity kernel. When i pushed update, my tablet restarted with clockwokmod and failed to update
to 4.2. i believed it was because of custom kernel so i then flashed to stock factory, and re locked using nexus toolkit.
When i go to setting for update, it's showing me that my system is up to date 4.1.2. I don't understand. I thought flashing it back to stock factory will solve the problem.
Thanks a lot in advance for you hep
diamondx911 said:
Please help, my nexus was unlocked rooted with trinity kernel. When i pushed update, my tablet restarted with clockwokmod and failed to update
to 4.2. i believed it was because of custom kernel so i then flashed to stock factory, and re locked using nexus toolkit.
When i go to setting for update, it's showing me that my system is up to date 4.1.2. I don't understand. I thought flashing it back to stock factory will solve the problem.
Thanks a lot in advance for you hep
Click to expand...
Click to collapse
1) If you are using a custom kernel and/or custom recovery and/or removed/froze required system apks and/or modified build.prop and/or have a dozen other "custom" things, then the OTA update will NOT work. Period. You need to revert ALL of that. Stock kernel, recovery, system apks, build.prop, etc. Because if any of those aren't stock, the install will abort.
2) Having root is irrelevant. The update will remove suid access on the binary, so you will need to "re-root", but the binaries presence is irrelevant.
3) If it failed the OTA update, it won't download it again right away. Your best bet is to download the file and try to flash manually in a custom recovery (which will work as long as everything else is stock).
4) Did you say you relocked the tablet? If so, why? That was NOT required, and you just f*cked yourself, because you won't be able to flash a custom recovery back without unlocking the bootloader again, which will wipe your sdcard. There is NO reason to relock unless you are returning the device.
5) Again, this is why I hate toolkits. Learn to do things manually and you will be much better off.
At this point, assuming you relocked the bootloader, you will probably need to do a full factory reset and unlock it again. Then flash custom recovery and then flash the update. Or, since it would have been reset at that point, just download the full image from Google and flash that, then flash custom recovery.
phonic said:
1) If you are using a custom kernel and/or custom recovery and/or removed/froze required system apks and/or modified build.prop and/or have a dozen other "custom" things, then the OTA update will NOT work. Period. You need to revert ALL of that. Stock kernel, recovery, system apks, build.prop, etc. Because if any of those aren't stock, the install will abort.
2) Having root is irrelevant. The update will remove suid access on the binary, so you will need to "re-root", but the binaries presence is irrelevant.
3) If it failed the OTA update, it won't download it again right away. Your best bet is to download the file and try to flash manually in a custom recovery (which will work as long as everything else is stock).
4) Did you say you relocked the tablet? If so, why? That was NOT required, and you just f*cked yourself, because you won't be able to flash a custom recovery back without unlocking the bootloader again, which will wipe your sdcard. There is NO reason to relock unless you are returning the device.
5) Again, this is why I hate toolkits. Learn to do things manually and you will be much better off.
At this point, assuming you relocked the bootloader, you will probably need to do a full factory reset and unlock it again. Then flash custom recovery and then flash the update. Or, since it would have been reset at that point, just download the full image from Google and flash that, then flash custom recovery.
Click to expand...
Click to collapse
Haha, thanks for answering... the update came back by itself.
I was not aware of anything when i unlocked and rooted my nexus. please bare with me. I'm new to the android scene. but i'm very familiar with the hacking tool, i hacked and unlocked everything i own in my house, from 3 iphones, to my psp , xbox, ps3 and psp. when i first got my hand on the nexus i saw some dead black line of pixel that was appearing for half a second, after i read that a custom kernel can fix it,
I just did it fast and was not in a mood to start learning that sh*t from scratch. so now i'm on 4.2 , i know i lost everything. i will just have to unlock again and and root it....
diamondx911 said:
Haha, thanks for answering... the update came back by itself.
I was not aware of anything when i unlocked and rooted my nexus. please bare with me. I'm new to the android scene. but i'm very familiar with the hacking tool, i hacked and unlocked everything i own in my house, from 3 iphones, to my psp , xbox, ps3 and psp. when i first got my hand on the nexus i saw some dead black line of pixel that was appearing for half a second, after i read that a custom kernel can fix it,
I just did it fast and was not in a mood to start learning that sh*t from scratch. so now i'm on 4.2 , i know i lost everything. i will just have to unlock again and and root it....
Click to expand...
Click to collapse
Understood, and "hacking" android, especially Google devices, is pretty easy once you know what you are doing. The reason I dislike toolkits is that it prevents people from understanding the process, which really is fairly easy to understand, and can complicate troubleshooting steps.
The bootloader can easily be unlocked and locked. It takes one command and it's done. In order to flash anything with fastboot, you need it to be unlocked. The problem is, when you do this, it factory resets the device. So if you inadvertantly relock it, your going to need to reset it to unlock it again.
Even without the toolkit, going from unopened stock Nexus7 to fully rooted, updated and custom firmware Nexus7 only takes maybe 10 minutes, and 9 minutes of that is waiting for it to finish doing the various steps (flashing, rebooting, etc.). The most time consuming part is, unless you have good backups, restoring all your apps and settings. Titanium Backup is the best tool (IMHO) for that.
But yeah, in this case, you're going to need to unlock/wipe again. However, you CAN backup your "sdcard" to your computer and push the files back to it after the wipe. That can be very time consuming depending on how much you have.
Dev edition. Unlocked and rooted with TWRP.
Put the 4.4.2 exchange apk's in /system then found out my company requires full device encryption on phones without an SD card.
I want to stay stock. Only reason I rooted was to get the new exchange apks.
If I encrypt everything will I still be able to:
-Use adb to go back to stock recovery
-use root explorer to restore the stock system apps
-take an OTA while maintaining unlock and root?
Sorry for the dumb questions. Every phone I've used had an SD card and I never had to deal with this.
Sent from my XT1060 using Tapatalk
Prior to posting this I read about 50 google results and learned that Google sucks.
So I'm slowly figuring out these answers as I go since no one else knows.
First I unlocked and rooted my device using this guide:
http://www.elementalxdesigns.com/ec...our-Moto-X-Developer-Edition-and-install-TWRP
Immediately after installing TWRP reboot into recovery and then tell TWRP to reboot. It will ask if you want to root, say yes. Install Super su from play store.
Next I used root explorer to get the 4.4.2 exchange and exchange services into /system/app then disabled the old ones in the normal settings/apps menu.
Then I set up my phone and configured my work exchange account and let it encrypt my device.
Here is what I have discovered:
- TWRP still can be booted into, but it can't see the /data partition. So you cant make a full nandroid or flash any files you saved to your phone.
- You can still use adb to flash TWRP or the stock recovery
Unknown:
-If I wasn't already rooted would TWRP have been able to root the device after unlocking and flashing TWRP earlier? It can't see the data partition, does it need to?
I don't have time right now to "start fresh" and see, but when I do I will update this thread.
I wish I could be of assistance, but I would love for you to keep us posted. I thought about encrypting my phones many times but I didn't know if/what that would prevent me from doing.
MotoX Developer Edition, Bootloader Unlocked, Rooted, Stock with tweaks!
You don't need to install a custom recovery to root. I have a Verizon Moto X which I used the "SlapMyMoto" method. After rooting I was able to encrypt the phone just fine without any issues to my root. I don't have an unlocked bootloader (don't see a point personally, since I don't plan to install another ROM).
If you intent to install another ROM then you'll want to not have the phone encrypted unless TWRP can access encrypted files on your device.
If you don't want to install a custom ROM then I recommend using the SlapMyMoto method, which works very well though it is a bit cumbersome to get done, once it is done you shouldn't need to redo it unless you accept an OTA.
The basic process is to root it using methods for 4.2 (you have to restore to 4.2 prior to rooting), then disable write protection using the appropriate tool, I think it is calle MotoWPNoNo or something along those lines. After that, accept the OTA to 4.4 and run SlapMyMoto to get root back.
Thanks titan. I think my biggest question right now is "can you root a phone that is already encrypted?"
I know I can unlock (dev edition) and install TWRP (abd) but can I root if TWRP can't see the /data partition meaning I can't flash the supersu zip.
If you root *then * encrypt it works fine. But since un-encrypting requires a wipe it would be nice to avoid having to go though that.
Sent from my XT1060 using Tapatalk
Restola said:
Thanks titan. I think my biggest question right now is "can you root a phone that is already encrypted?"
I know I can unlock (dev edition) and install TWRP (abd) but can I root if TWRP can't see the /data partition meaning I can't flash the supersu zip.
If you root *then * encrypt it works fine. But since un-encrypting requires a wipe it would be nice to avoid having to go though that.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Well, you don't actually need to see the /data partition to flash, if you have the ZIp somewhere else, or use ADB + TWRP (I think you can do that? I know you can with CWM). When you encrypt the OS isn't encrypted so /system isn't touched. The short answer is, yes, you can. TWRP should be able to read the encryption - in fact it should ask you for a password to decrypt when you boot into recovery.
I would still recommend using SlapMyMoto as it leave stock recovery in place, the reason this is good is because TWRP won't respond to an automatic wipe request from Android Device Manager or similar service. If you leave the stock recovery in place then you can still remote-wipe the device if you need to.
If you've already got TWRP in place it is simple... Does TWRP ask you to decrypt the phone before it goes in? If it does, can you see your internal SD Card and select a ZIP from it? If those are YES then, it'll work fine. TWRP can see the entire phone and thus you can install a zip without problem. If i can't, you'll need to get more creative, but I still would suggest seeing you can use ADB while you're booted into TWRP to push the SuperSU ZIP to the device to flash.
Here is a link from last year from Stack Exchange about TWRP and an encrypted device. I know that when I had my S3 running CyanogenMod TWRP would decrypt it just fine.
https://android.stackexchange.com/q...custom-recovery-work-with-an-encrypted-device
Should you need to do it, here is the link for using ADB with TWRP... (it is called Sideloading, forgot that)
http://teamw.in/ADBSideload
Thanks the side loading may be what I'm looking for If I ever go back to square one and want to root while encrypted. TWRP didn't ask to decrypt so no luck there.
Sent from my XT1060 using Tapatalk
Did you ever get this working? I just put TWRP on my MotoX DE, and I encrypted my phone (Exchange requirement). Anyway to have TWRP decrypt so i can sideload or root?
Hi,
I have a Nexus 6 with a shattered screen, and just bought another one to replace it (exact same model, XT1103 32GB).
I want to make a Nandroid dump of the old device by booting into TWRP temporarily, then restoring the backup to the new phone using the same method. Both phones are bootloader unlocked and totally stock (latest Android update).
Is there anything in particular that I should watch out for? Which partitions should I not touch - a friend on another forum suggested that I should not touch EFS?
Cheers,
Su
If you restore the efs from one to the other you'll loose your imei number on the second one
needleyepoke
---------- Post added at 07:49 PM ---------- Previous post was at 07:47 PM ----------
I've cloned a Nexus 5 but I'm not sure if it's the same way.... P.S. of course your not supposed to do it unless you own both phones... From what I've been told
needleyepoke
Hi,
I don't want to mess about with the IMEI etc - I just want the same system settings, apps etc.
What partitions should I backup/restore? I guess just System, Data, Cache, Boot & Recovery should be enough?
Thanks,
Su
[edit] This seems to suggest just System, Data and Boot is ok - but is that all I need if I am restoring to another device?
Sumanji said:
Hi,
I don't want to mess about with the IMEI etc - I just want the same system settings, apps etc.
What partitions should I backup/restore? I guess just System, Data, Cache, Boot & Recovery should be enough?
Thanks,
Su
[edit] This seems to suggest just System, Data and Boot is ok - but is that all I need if I am restoring to another device?
Click to expand...
Click to collapse
Yes if they're on the same version. I cloned a 32 into a 64.
Ok I just tried this now, and it is not working...
The restore to the new device worked fine, but when I power up I get the "your device is corrupt screen" (which I think is normal if you use TWRP), but then after that it's just a blank screen...
The phone is still able to boot into bootloader and recovery (stock).
Any ideas what could have gone wrong please?
Thanks,
Suman
I think this might be something to do with encryption... when booting into TWRP the new phone still requires the encryption pin I set up from its original software....
Do I need to start again?
Ok, I flashed the new phone with the factory image and started again... this time, when I restore the backup it just hangs on the white Google logo screen...
Any help appreciated please!
Thanks,
Su
If your firs N6 was encrpted (default) there's no way to clone it. Android will generate different encryption keys etc.
Secure lockscreen is a big no-no too. With it, you can't even properly restore backup on the same device!
Trying to take the lazy way out is just asking for trouble. There are many things that can go wrong.
Also just a side note. Cloning devices is illegal, even if you own both devices. The was set by the cell phone cloning laws set up by the FCC.
Your best bet is just to reset it up from scratch.
zelendel said:
Trying to take the lazy way out is just asking for trouble. There are many things that can go wrong.
Also just a side note. Cloning devices is illegal, even if you own both devices. The was set by the cell phone cloning laws set up by the FCC.
Your best bet is just to reset it up from scratch.
Click to expand...
Click to collapse
Oh well,
I'm remembering what I did and I did not restore the Nandroid from Device A to Device B, I titanium Backup'd all the apps and moved them to TitaniumBackup folder on the new phone, restored from there.
For /sdcard/ I had to copy and paste it from one phone to the other...
I'm going to reply this to your reddit thread also.
Lawstorant said:
If your firs N6 was encrpted (default) there's no way to clone it. Android will generate different encryption keys etc.
Secure lockscreen is a big no-no too. With it, you can't even properly restore backup on the same device!
Click to expand...
Click to collapse
Ah dang, so there is no way for me to do what I want then... that's annoying, I would have bought a different phone in that case!
I believe Google requires encryption to be active in all devices with Android 6.0.1 installed, so any new device you purchase will have this (non-) issue.
Think of the alternative however. You could always be dealing with Samsung and Knox.
Strephon Alkhalikoi said:
I believe Google requires encryption to be active in all devices with Android 6.0.1 installed, so any new device you purchase will have this (non-) issue.
Think of the alternative however. You could always be dealing with Samsung and Knox.
Click to expand...
Click to collapse
I believe that is correct. All Nexus devices going forward will have the kernel force encryption. The only way around it is to format data in TWRP (completely wipe the phone) and then when you re setup your ROM (or even the stock image) just make sure you flash a custom kernel that doesn't force encryption (which pretty much all custom kernels don't) before booting into OS for the first time. I run mine unencrypted because nandroid backups are wayyyyy quicker without encryption. I know the security isn't as good but not a deal breaker for me.
I asked this question a while back when I was in the same situation, and was told that it's a bad idea.
TriguyRN said:
I asked this question a while back when I was in the same situation, and was told that it's a bad idea.
Click to expand...
Click to collapse
It is a bad idea. Restoring any system files from one device to another is a risky game. I wouldn't even recommend restoring data from one device to another.
Start fresh, clean. No need to bring junk over, or risk issues. Takes 15 minutes to setup a phone how I like it after a clean rom flash. That's not a long time.
Last year I returned my N6 because of the peeling-back problem. I had a full TWRP backup on my laptop. I loaded it on to the replacement N6, renamed the backup folder to the new device id, and restored it. Worked perfectly, no problems.
Since there are not too many stable ROMs available on the XT1096 that support CDMA (I am using Verizon's network). I decided I would unlock my bootloader, flash TWRP and root the stock firmware. Well, the past few days I guess I did not update my phone all the way before doing this since I just got it not even a week ago and keep getting prompts to install an OTA. This will obviously not work with TWRP and when I flashed TWRP I selected to modify the system so the stock firmware would not rewrite recovery on boot. This has become a complete pain in the ass for me. Accidently I selected to install the OTA since it is always in my notifications and when it happened it would obviously fail in TWRP but then it would boot back into the ROM and then power cycle back into TWRP. The only way to stop it was to do a factory reset which is not what I would like to do every time I accidently select to install this OTA. So my questions to you awesome people who know more about this device are. 1. is there a way I can enable the to option to where I will always have a stock recovery and then I can just fastboot boot into TWRP if needed? Or is there another way where I can just possibly stop this OTA all together even though the prompt already says it's downloaded and waiting for me to hit install. Like can I just go into rootexplorrer and delete or modify a few system files that'll stop the phone for looking for OTAs? I don't reallyl care about the OTA since it's obviously not 6.0 since VZW got boned on that one. Looks like it's just some security patches.
I'm sure this is probably a really stupid and simple question, so I apologize in advance. But thank you SO MUCH to anyone who decides to help me out. I will appreciate it GREATLY!!!
aeb401 said:
Since there are not too many stable ROMs available on the XT1096 that support CDMA (I am using Verizon's network). I decided I would unlock my bootloader, flash TWRP and root the stock firmware. Well, the past few days I guess I did not update my phone all the way before doing this since I just got it not even a week ago and keep getting prompts to install an OTA. This will obviously not work with TWRP and when I flashed TWRP I selected to modify the system so the stock firmware would not rewrite recovery on boot. This has become a complete pain in the ass for me. Accidently I selected to install the OTA since it is always in my notifications and when it happened it would obviously fail in TWRP but then it would boot back into the ROM and then power cycle back into TWRP. The only way to stop it was to do a factory reset which is not what I would like to do every time I accidently select to install this OTA. So my questions to you awesome people who know more about this device are. 1. is there a way I can enable the to option to where I will always have a stock recovery and then I can just fastboot boot into TWRP if needed? Or is there another way where I can just possibly stop this OTA all together even though the prompt already says it's downloaded and waiting for me to hit install. Like can I just go into rootexplorrer and delete or modify a few system files that'll stop the phone for looking for OTAs? I don't reallyl care about the OTA since it's obviously not 6.0 since VZW got boned on that one. Looks like it's just some security patches.
I'm sure this is probably a really stupid and simple question, so I apologize in advance. But thank you SO MUCH to anyone who decides to help me out. I will appreciate it GREATLY!!!
Click to expand...
Click to collapse
Try using your favorite applications manager for root and freeze MotorolaOTA. This will prevent the update from being downloaded and you won't get messages about installing the OTA update.
I thought that while encrypting my phone, the result would be that my data is preserved, just encrypted. So I went through the encryption process only to find that all my data is wiped, so that I have to restore everything from backups, as far as I have them.
Did I overlook something, or is this a bug? I have LineageOS 14.1, installed yesterday, official.
Found that after a reboot, the data was again gone. (after I spent considerable time setting the phone up yet again), now factory reset, running unencrypted, until I know what has been going wrong here. Sigh. Custom roms and encryption continue to be a toxic mix for me.
yahya69 said:
Found that after a reboot, the data was again gone. (after I spent considerable time setting the phone up yet again), now factory reset, running unencrypted, until I know what has been going wrong here. Sigh. Custom roms and encryption continue to be a toxic mix for me.
Click to expand...
Click to collapse
When I first started playing around with encryption (Samsung Note 3) I discovered that to get encryption to work properly I had to format /data (you lose everything, including internal shared storage) and that it worked better on stock ROM rather than custom ROMs.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
When I first started playing around with encryption (Samsung Note 3) I discovered that to get encryption to work properly I had to format /data (you lose everything, including internal shared storage) and that it worked better on stock ROM rather than custom ROMs.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
which I kind of accepted after learning it the hard way, but the problem was that after encrypting the device, all data was wiped each time the phone was rebooted, so something is buggy here.
yahya69 said:
which I kind of accepted after learning it the hard way, but the problem was that after encrypting the device, all data was wiped each time the phone was rebooted, so something is buggy here.
Click to expand...
Click to collapse
I resolve this problem using latest official twrp.
dimon2242 said:
I resolve this problem using latest official twrp.
Click to expand...
Click to collapse
How did you? (What version of TWRP did you install) After all, it is not TWRP that does the encryption, or is it? So I don't see how this could be the cause.
With TWRP, I had the additional issue that it kept asking me for a password to mount /data, but it wouldn't accept the PIN that I had set in Android. I have no idea what other password it might want.
Oh, well, there is just too much fumbling in the dark in this whole mobile devices business. I have been a Linux user for some 20 years, and there, if things go wrong, you can actually view what is happening. On android, this is so much more difficult, even with logcat.
yahya69 said:
How did you? (What version of TWRP did you install) After all, it is not TWRP that does the encryption, or is it? So I don't see how this could be the cause.
With TWRP, I had the additional issue that it kept asking me for a password to mount /data, but it wouldn't accept the PIN that I had set in Android. I have no idea what other password it might want.
Oh, well, there is just too much fumbling in the dark in this whole mobile devices business. I have been a Linux user for some 20 years, and there, if things go wrong, you can actually view what is happening. On android, this is so much more difficult, even with logcat.
Click to expand...
Click to collapse
Have you tried default_password as the password in TWRP?
Also, if you can actual log into your system normally, then you can set the password again and require it on boot.
BillGoss said:
Have you tried default_password as the password in TWRP?
Click to expand...
Click to collapse
What "default password"? You mean, literally typing "default_password"? No I did not. What would that have done?
After all, again, it required a password for the /data partition, hence a password with whom it is encrypted. But I had used no password other than the PIN. And again, I can't see how my problem of data disappearing on each boot would be caused by TWRP.
Also, if you can actual log into your system normally, then you can set the password again and require it on boot.
Click to expand...
Click to collapse
Again, what password do you have in mind? The PIN? Yes, the system asked for the PIN at boot, but nonetheless, all data was wiped on each boot.
For the time being,I run the system without encryption, because I have had enough of setting is up again and again anew (had to do this three or four times.)
Again, it looks like this is a bug. Because after initially encrypting the phone, my data should still have been there. But it was gone. The phone was now encrypted, but there was nothing on it. That's something that I am pretty sure is not supposed to happen.
just had the same using Samsung S5 Duos with latest lineage-os (20180427): this is a cluster-f**k, I cannot believe it. I advocate using Lineage-OS whereever I go. Of course, it's my fault, I did trust Lineage-OS too much so I didn't think of backing-up. I didn't believe something like this could happen.
chaos_prevails said:
I did trust Lineage-OS too much so I didn't think of backing-up. I didn't believe something like this could happen.
Click to expand...
Click to collapse
You probably already realize this, at this point. But there is no such thing as an OS (on any device) that is so secure or stable, that backing up your data is not necessary. Even regardless of OS, memory corruption and data loss can happen for any number of reasons. Golden rule: If your data is important to you, back it up.
Of course, I know.
I took the loss of all data as opportunity to flash newest modem, CSC, and PDA firmware via latest stock-rom, and then re-flashed latest Lineage OS again. This time, it didn't factory reset my phone with encryption. Don't know if that had anything to do with my old firmware (I had G900FDXXS1CPK2 installed when factory reset-with-encryption happened).
Beside, I was lucky as no other migration method to my new phone worked out except going via a old-school micro-sd card copy. I could undelete almost all pictures on it