Related
Hi all,
I recently got a HK N7105 and because it lacked the possibility to use a french keyboard I upgraded to a stock unbranded ROM from Sweden (XXDLL1) and succesfully rooted with the relevant CF_autoroot through Odin. Also installed TWRP 2.3.3.1.
Then, I connected the Note 2 to my corporate exchange server which enforced a full encryption policy (device and external SD card) so I had to type in a password at each boot time (with a "nice" swedish prompt that took ma while to decypher), plus a password to unlock the screen. All was well as the root survived the process.
Next I upgraded to a later stock ROM from France (XXDLL4 from SFR) to try and get rid of the swedish prompt. That worked fine (and root was loast in the process, as expected) but I hated the branded stuff so much I reverted to XXDLL1 until a proper unbranded "english" or "french" ROM is available.
At this point I decided to root again. I was running XXDLL1 like the first time and used the same autoroot tar from Chainfire. Except my Note 2 was still encrypted and after that it would not accept my boot password (a four digit PIN) anymore so I was guted and had to factory reset and root then reinstall everything before reconnecting to the exchange server.
Question 1: Does anyone know of a safe, proven way to root a fully encrypted Samsung device so I can go another upgrade without having to wipe the device first?
Why reinstall everything? Why not backup everything first so you can restore after the wipe? Well, it so happens that no recovery (at least neither CWM or TWRP) can read any encrypted media on the Note 2 at the moment. And no Recovery can actually fully backup the device as well.
Question 2: Does anyone know of a proper way to handle this situation with minimum hassle?
So far, the best I can think of is doing a Titanium backup and FTP the files to my NAS so I can retrieve them later. But (Question 3) will this be enough to restore my phone to the expected state after a stock firmware upgrade?
Thanks in advance,
François
frankieGom said:
Hi all,
I recently got a HK N7105 and because it lacked the possibility to use a french keyboard I upgraded to a stock unbranded ROM from Sweden (XXDLL1) and succesfully rooted with the relevant CF_autoroot through Odin. Also installed TWRP 2.3.3.1.
Then, I connected the Note 2 to my corporate exchange server which enforced a full encryption policy (device and external SD card) so I had to type in a password at each boot time (with a "nice" swedish prompt that took ma while to decypher), plus a password to unlock the screen. All was well as the root survived the process.
Next I upgraded to a later stock ROM from France (XXDLL4 from SFR) to try and get rid of the swedish prompt. That worked fine (and root was loast in the process, as expected) but I hated the branded stuff so much I reverted to XXDLL1 until a proper unbranded "english" or "french" ROM is available.
At this point I decided to root again. I was running XXDLL1 like the first time and used the same autoroot tar from Chainfire. Except my Note 2 was still encrypted and after that it would not accept my boot password (a four digit PIN) anymore so I was guted and had to factory reset and root then reinstall everything before reconnecting to the exchange server.
Question 1: Does anyone know of a safe, proven way to root a fully encrypted Samsung device so I can go another upgrade without having to wipe the device first?
Why reinstall everything? Why not backup everything first so you can restore after the wipe? Well, it so happens that no recovery (at least neither CWM or TWRP) can read any encrypted media on the Note 2 at the moment. And no Recovery can actually fully backup the device as well.
Question 2: Does anyone know of a proper way to handle this situation with minimum hassle?
So far, the best I can think of is doing a Titanium backup and FTP the files to my NAS so I can retrieve them later. But (Question 3) will this be enough to restore my phone to the expected state after a stock firmware upgrade?
Thanks in advance,
François
Click to expand...
Click to collapse
I think using Exynos Abuse apk will do the work
http://forum.xda-developers.com/showthread.php?t=2050297
Thanks for the heads up, I'll look into it. But to be clear, that answers question 1, correct?
Sent from my GT-N7105 using xda app-developers app
frankieGom said:
Thanks for the heads up, I'll look into it. But to be clear, that answers question 1, correct?
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
Yes that's a way to root the device.
Regarding encryption, very few people on xda seem to use it. So for that reason you'll have trouble finding out what works... I do use it though through choice so I can help you a bit.
When you encrypt the device, just consider /data to be off limits to anything not booted fully. That's why it asks you for your key in swedish - it can't see what language is in use until you unlock /data.
You will have issues using recovery with the device, since they can't read /data. You can use an external sd to perhaps load data to the device though.
I believe that TWRP might soon support the Samsung encryption on the device, meaning you could use it as recovery. Once you have a recovery that supports Samsung encryption, you should be able to consider it a fairly normal device.
Just be more cautious to backup your data as it is hard to recover if something goes wrong...
If your using stock rom 4.1.2, exynos abuse method of root will not work. It's been patched
Sent from my GT-N7100 using xda app-developers app
pulser_g2 said:
Yes that's a way to root the device.
Regarding encryption, very few people on xda seem to use it. So for that reason you'll have trouble finding out what works... I do use it though through choice so I can help you a bit.
When you encrypt the device, just consider /data to be off limits to anything not booted fully. That's why it asks you for your key in swedish - it can't see what language is in use until you unlock /data.
You will have issues using recovery with the device, since they can't read /data. You can use an external sd to perhaps load data to the device though.
I believe that TWRP might soon support the Samsung encryption on the device, meaning you could use it as recovery. Once you have a recovery that supports Samsung encryption, you should be able to consider it a fairly normal device.
Just be more cautious to backup your data as it is hard to recover if something goes wrong...
Click to expand...
Click to collapse
Fine, I understand. As long as I have a way to recover my data if I need to wipe I'm okay... I just have to hope Titanium backup gives me that until TWRP can manage encruption on the Note 2.
I'm really waiting for a stock rom that boots in English or French now.
Sent from my GT-N7105 using xda app-developers app
vash_h said:
If your using stock rom 4.1.2, exynos abuse method of root will not work. It's been patched
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Not the case with xxdll1. When was it patched, xxdll4 or xxdll7?
Sent from my GT-N7105 using xda app-developers app
frankieGom said:
Not the case with xxdll1. When was it patched, xxdll4 or xxdll7?
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
I am on Stock 4.1.2 and Exynos Abuse did work on my device, it's successfully rooted using the Exynos AbuseAPK on 4.1.2 :good:
OK, now I have been experimenting a bit with backups and upgrade and have trouble restoring my device fully. Let me explain...
I got hold of a TWRP build that seems to handle Samsung encryption fine through one of the TWRP devs (thanks!), so I decided to go back and try to update my device.
Current ROM: N7105XXDLL1_N7105TLADLL1_N7105XXDLK7_HOME.tar (obtained from Samsung Updates)
New ROM: N7105XXDLL7_N7105OLBDLL2_N7105DXDLL1_HOME.tar (obtained from Samsung Updates)
First I performed a complete Titanium Backup on the device and pulled the files to my laptop using ADB.
Then I restarted into TWRP 2.4.0.0 (got a prompt for my password), performed a full backup and pulled the files to the laptop using ADB.
(for some reason, I could not install the new ROM from TWRP (unable to open ZIP), but the ZIP looked OK, as well as after a second download which TWRP since did not like, so I had to use Odin instead).
Next, I flashed DLL7 with Odin. It worked, asked for the password at boot, but the device was unrooted at this point (I expected that).
Then, I flashed CF-Auto-Root-t0lte-t0ltexx-gtn7105.tar from Odin, but the boot up password would not be accepted anymore as I already knew.
Tried to flash DLL7 again from Odin, same thing
Flashed TWRP back on recovery partition, but on startup it would not ask for password anymore and the external sdcard looked empty to it.
I then copied my backup to a different, non encrypted sdcard and could restore from TWRP but the password would still not work after reboot.
I did a factory reset, restored backup, same result.
At this point I decided to factory reset, wipe Dalvik and format /data. The format did the trick and after TWRP restore of my original back up the device booted up, did not ask for password and all my data was there. Except the Exchange account I use for Corporate email wants me to restore encryption in order to work (I expected that too).
Back at DLL1, so I flashed DLL7 again with Odin (OK), rooted the phone, triangled away the flash counter and reflashed TWRP to recovery.
I was where I wanted to be except for one thing: I need to restore Corporate access. But when I let it encryp the phone it does nothing. I let it through the night and nothing). And if I reboot the phone no password is needed at boot time, yet the phone seems to behave as if it thought the device was still encrypted...
I reflashed my original, full, backup (i.e DLL1) succesfully but Exchange still wants to encrypt my device. Isn't restore supposed to restore the encrypted /data I backed up?
At this point I'm left with possibly tryinjg to go back to full factory settings, not use the backup at all, encrypt the device then restore my data from the Titanium backup I made.
Is there a better option?
[edited jan 18 - TWRP/TB behaviour]
My comments apply to encrypted devices only! I am not trying to talk down TWRP or TB here, as they provide splendid performance on non encrypted devices. I have come upon hard time trying to upgrade/restore an encrypted device using thoise tools, that's all
For those considering upgrading & re-rooting encrypted devices, don't!
I am finding the hard way that this is a one way street. At this point, my TWRP made full backup does not restore the device to the expected status. Each time I apply it, subsequent bootup takes several minutes and I end up going through the initial setup procedure. It seems the device for some reasoin goes through a complete reset procedure.
[edit]
Clarification: The TWRP build I use, 2.4.0.0 is an alpha build and I was not current when I restored my backup. I so happens that it was overwriting the encryption header on the partition, which messed things up bad, and had issues writing back the data partition, ending up in a factory reset status!
Using the latest drop as of today (jan 27) I was able to restore my original backup and am now back to my original state. All is well.
[/edit]
Titanium Backup is none better. It keeps telling me that my Android ID has changed, a host of system applications start to fail when I try to restore and generally speaking I have now spent between a good 20 hours trying to simply restore my data.
[edit]
this behaviour is probably linked to encryption. I know for a fact that TB works very well on non encrypted phones. The 20h figure is overall, not just with TB.
[/edit]
The end story is: root before you encrypt, and either don't upgrade or don't re-root if you do! If you do, be prepared for some rough times...
Unless someone has a cleat idea of how to do this properly without losing all your data, that is.
François
frankieGom said:
For those considering upgrading & re-rooting encrypted devices, don't!
I am finding the hard way that this is a one way street. At this point, my TWRP made full backup does not restore the device to the expected status. Each time I apply it, subsequent bootup takes several minutes and I end up going through the initial setup procedure. It seems the device for some reasoin goes through a complete reset procedure.
Titanium Backup is none better. It keeps telling me that my Android ID has changed, a host of system applications start to fail when I try to restore and generally speaking I have now spent between a good 20 hours trying to simply restore my data.
The end story is: root before you encrypt, and either don't upgrade or don't re-root if you do!
Unless someone has a cleat idea of how to do this properly without losing all your data, that is.
François
Click to expand...
Click to collapse
I have had no issues despite doing upgrades, with and without wipes.
Titanium is fine, just stop restoring system app data. Seriously, what data do you have in a system app that you want to restore.
Restore your user apps, their data, and the xml based call, sms, Wifi backups. It will work fine.
Device ID isn't a problem - it's just trying to help you.
pulser_g2 said:
I have had no issues despite doing upgrades, with and without wipes.
Titanium is fine, just stop restoring system app data. Seriously, what data do you have in a system app that you want to restore.
Restore your user apps, their data, and the xml based call, sms, Wifi backups. It will work fine.
Device ID isn't a problem - it's just trying to help you.
Click to expand...
Click to collapse
Sorry if I came across dissing Titanium Backup and/or TWRP. This was not the intent... I am sure both tools work real nice in general cases (and I have had success restoring data on a Jetstream before).
My main issue here is _full device encryption_ enforced by my company's corporate IT to allow me on the corporate exchange server. Do you have full device encryption on?
On my device, even after a full wipe and flashing a fresh stock rom Titanium Backup just did not work as I hoped. When I had to confirm individual popups of apps closing unexpectedly while it was proceeding and got nothing back in the end, what was I supposed to think? It could be that I don't understand how TB works... I was neither able to restore missing apps after the flash (missing apps: 0) nor installed apps data (they would close unexpectedly when started after restoring the back up). So I say: until full operation of TB on encrypted devices is documented, I will stay away from it, even though I am a registered user (and I do not plan to seek reimbursment)!
Anyway, I got to a belated happy ending (previous post edited).
frankieGom said:
Sorry if I came across dissing Titanium Backup and/or TWRP. This was not the intent... I am sure both tools work real nice in general cases (and I have had success restoring data on a Jetstream before).
My main issue here is _full device encryption_ enforced by my company's corporate IT to allow me on the corporate exchange server. Do you have full device encryption on?
On my device, even after a full wipe and flashing a fresh stock rom Titanium Backup just did not work as I hoped. When I had to confirm individual popups of apps closing unexpectedly while it was proceeding and got nothing back in the end, what was I supposed to think? It could be that I don't understand how TB works... I was neither able to restore missing apps after the flash (missing apps: 0) nor installed apps data (they would close unexpectedly when started after restoring the back up). So I say: until full operation of TB on encrypted devices is documented, I will stay away from it, even though I am a registered user (and I do not plan to seek reimbursment)!
Anyway, I got to a belated happy ending (previous post edited).
Click to expand...
Click to collapse
Yup I use device encryption Enabled manually, but it's the same encryption.
You should find that titanium shouldn't even be aware of it - the encryption is transparent!
I wonder... I'm sure lenny had that issue on a recent 4.1.2 "stock" ROM... And he doesn't use encryption...
I personally have had no issues with titanium on an encrypted device anyway
I notice you were using the newest rom - that's the one lenny had issues on.
pulser_g2 said:
Yup I use device encryption Enabled manually, but it's the same encryption.
You should find that titanium shouldn't even be aware of it - the encryption is transparent!
I wonder... I'm sure lenny had that issue on a recent 4.1.2 "stock" ROM... And he doesn't use encryption...
I personally have had no issues with titanium on an encrypted device anyway
I notice you were using the newest rom - that's the one lenny had issues on.
Click to expand...
Click to collapse
Exactly like I thought, encryption should be transparent to Titanium Backup since it runs within the OS.
I have had problems restoring into 4.1.2 DLL1 (the build I came from) and DLL7 (the one I was trying to go to)
The point is moot anyway since the DLL7 I tried was actually branded (Singtel stuff all around the launcher) and did not include French, which is why restoring my TWRP backup was a tempting proposition.
Good to know TB runs fine with encryption as well. What ROM are you running?
François
frankieGom said:
Hi all,
I recently got a HK N7105 and because it lacked the possibility to use a french keyboard I upgraded to a stock unbranded ROM from Sweden (XXDLL1) and succesfully rooted with the relevant CF_autoroot through Odin. Also installed TWRP 2.3.3.1.
Then, I connected the Note 2 to my corporate exchange server which enforced a full encryption policy (device and external SD card) so I had to type in a password at each boot time (with a "nice" swedish prompt that took ma while to decypher), plus a password to unlock the screen. All was well as the root survived the process.
Next I upgraded to a later stock ROM from France (XXDLL4 from SFR) to try and get rid of the swedish prompt. That worked fine (and root was loast in the process, as expected) but I hated the branded stuff so much I reverted to XXDLL1 until a proper unbranded "english" or "french" ROM is available.
At this point I decided to root again. I was running XXDLL1 like the first time and used the same autoroot tar from Chainfire. Except my Note 2 was still encrypted and after that it would not accept my boot password (a four digit PIN) anymore so I was guted and had to factory reset and root then reinstall everything before reconnecting to the exchange server.
Question 1: Does anyone know of a safe, proven way to root a fully encrypted Samsung device so I can go another upgrade without having to wipe the device first?
Why reinstall everything? Why not backup everything first so you can restore after the wipe? Well, it so happens that no recovery (at least neither CWM or TWRP) can read any encrypted media on the Note 2 at the moment. And no Recovery can actually fully backup the device as well.
Question 2: Does anyone know of a proper way to handle this situation with minimum hassle?
So far, the best I can think of is doing a Titanium backup and FTP the files to my NAS so I can retrieve them later. But (Question 3) will this be enough to restore my phone to the expected state after a stock firmware upgrade?
Thanks in advance,
François
Click to expand...
Click to collapse
About a backup : have you tried Online Nandroid (Playstore) (or similar, based on Onandroid) ? This makes a CWM or TWRP compatible backup while the device is running (everything should be unencrypted at this moment).
See http://forum.xda-developers.com/showthread.php?t=1620255
About rooting : you can try the same trick as above, by using ADB-shell and pushing the needed files to root to the device while it is running.
For my S3 there is a Toolkit that automates all this (http://forum.xda-developers.com/showthread.php?t=1703488), maybe there is something similar for your device ?
If not, you should still be able to do it using manual ADB-pushing.
I'm sorry I can't give you detailed instructions about the rooting as I'm not familiar with your device. Search here on XDA and you'll find more details.
pat357 said:
About a backup : have you tried Online Nandroid (Playstore) (or similar, based on Onandroid) ? This makes a CWM or TWRP compatible backup while the device is running (everything should be unencrypted at this moment).
See http://forum.xda-developers.com/showthread.php?t=1620255
About rooting : you can try the same trick as above, by using ADB-shell and pushing the needed files to root to the device while it is running.
For my S3 there is a Toolkit that automates all this (http://forum.xda-developers.com/showthread.php?t=1703488), maybe there is something similar for your device ?
If not, you should still be able to do it using manual ADB-pushing.
I'm sorry I can't give you detailed instructions about the rooting as I'm not familiar with your device. Search here on XDA and you'll find more details.
Click to expand...
Click to collapse
Thanks for the suggestions, and no I had not tried Online Nandroid as I was not aware of it. Anyway, my main issue is now resolved since TWRP has include support for Samsung TouchWiz based encryption in 2.4 and that works well.
For those interested, the only remaining issues I have with TWRP regarding encryption are that if you want to format /data from TWRP (say, to remove encryption) it will fail unless you _do not_ enter the password at boot, and the TWRP formated /data cannot be re-encrypted (you must use stock recovery to factory reset/wipe the device or else the encryption step will sit deat in the water doing nothing). I suppose the second one is a bug that will be fixed in a later version.
I will check Online Nandroid out anyway, being able to make a backup from a live system sounds good!
François
frankieGom said:
Thanks for the suggestions, and no I had not tried Online Nandroid as I was not aware of it. Anyway, my main issue is now resolved since TWRP has include support for Samsung TouchWiz based encryption in 2.4 and that works well.
For those interested, the only remaining issues I have with TWRP regarding encryption are that if you want to format /data from TWRP (say, to remove encryption) it will fail unless you _do not_ enter the password at boot, and the TWRP formated /data cannot be re-encrypted (you must use stock recovery to factory reset/wipe the device or else the encryption step will sit deat in the water doing nothing). I suppose the second one is a bug that will be fixed in a later version.
I will check Online Nandroid out anyway, being able to make a backup from a live system sounds good!
François
Click to expand...
Click to collapse
I have a similar issue. I had the device encrypted and decided to ROOT (using CF-AutoRoot). Unfortunately I cannot bypass the password screen now, although I know that I'm entering the right password. You are saying that if I flash TWRP everything will be fine?
ludovicianul said:
I have a similar issue. I had the device encrypted and decided to ROOT (using CF-AutoRoot). Unfortunately I cannot bypass the password screen now, although I know that I'm entering the right password. You are saying that if I flash TWRP everything will be fine?
Click to expand...
Click to collapse
Two separate things:
Root messing up encrypted touchwiz devices and twrp not handling touchwiz encrypted partitions properly.
The 2nd one, as much as I can tell, is fixed since before 2.5 so if youwork with the latest (2.6) you should be fine.
The first one I haven't played with in a while, but my finding is that you don't want to root a device once it's been encrypted. I've tried several different methods including rooting as you flag as is possible with twrp and all end up the same:the password is not recognised anymore!
The only thing that works for me is rooting before encrypting or only flashing pre-rooted ROMs.
frankieGom said:
Two separate things:
Root messing up encrypted touchwiz devices and twrp not handling touchwiz encrypted partitions properly.
The 2nd one, as much as I can tell, is fixed since before 2.5 so if youwork with the latest (2.6) you should be fine.
The first one I haven't played with in a while, but my finding is that you don't want to root a device once it's been encrypted. I've tried several different methods including rooting as you flag as is possible with twrp and all end up the same:the password is not recognised anymore!
The only thing that works for me is rooting before encrypting or only flashing pre-rooted ROMs.
Click to expand...
Click to collapse
Yes - I had to factory reset the phone and format the SD Card. Never root AFTER encryption :silly:
Hey guys,
If I encrypt my M8, then do a full Nandroid backup to the SDcard, can this backup be restored to any device or is it device-specific?
Also, am I right in assuming that a backup of an encrypted handset can even be restored? If so, how is unencryption performed after the restore?
Just want to clarify as I'm unsure of 'best practice' when making a full backup.
I'd prefer to make encrypted backups and then store the SDcard safely, but if an encrypted backup is in fact device-specific, it almost seems counterproductive.
Anyone?
Just want to know an encrypted phone can be backed up and then restored before actually encrypting my M8!
I don't think you can make a backup if you encrypt your phone. Or even flash any files from recovery. The data will be encrypted and CWM can't access them AFAIK..at least not the HTC encryption.
And backups are not tied to the device as such.
You could make a nand backup with a tool that makes backups while you're booted into Android. Such as Online Nandroid Backup.
Thank you :good:
As mentioned in the initial post I'm using Nandroid Online Backup, so I kind of assumed that as the phone is effectively 'decrypted' whilst I'm booted into the Android, the Nandroid backup would be fully restorable.
But even if that is indeed the case, would the actual backup on the SDCard itself be encrypted data .. or unencrypted due to the decryption which is performed once booted into Android?
My ideal scenario is to have an encrypted M8 + an encrypted SDCard backup. But I assume there would be no way to restore an encrypted SDCard backup .. other than to the original handset/Device ID on which it was first created.
Unless I'm missing something?
westeight said:
Thank you :good:
As mentioned in the initial post I'm using Nandroid Online Backup, so I kind of assumed that as the phone is effectively 'decrypted' whilst I'm booted into the Android, the Nandroid backup would be fully restorable.
But even if that is indeed the case, would the actual backup on the SDCard itself be encrypted data .. or unencrypted due to the decryption which is performed once booted into Android?
My ideal scenario is to have an encrypted M8 + an encrypted SDCard backup. But I assume there would be no way to restore an encrypted SDCard backup .. other than to the original handset/Device ID on which it was first created.
Unless I'm missing something?
Click to expand...
Click to collapse
The backup would be unencrypted if you save it to the SD card. Unless you encrypt the SD card also, which is done separately. Not sure how that would work out though..never tried it You might wanna check the support for the Online Nandroid tool for that info.
As for the restoring backup to devices, since the backup is unencrypted and it's not tied to any device, it would be possible to restore it to other phones or just simply unpack it.
Thanks WarCow :good:
I guess the safest thing is to encrypt, reboot/decrypt, then backup and then bury my SDCard somewhere safe!
westeight said:
Thanks WarCow :good:
I guess the safest thing is to encrypt, reboot/decrypt, then backup and then bury my SDCard somewhere safe!
Click to expand...
Click to collapse
Except that decryption will require factory resetting your phone It's such a hassle. Also keep in mind that encryption will slow the phone down a bit compared to being unencrypted.
WarCow said:
Except that decryption will require factory resetting your phone It's such a hassle. Also keep in mind that encryption will slow the phone down a bit compared to being unencrypted.
Click to expand...
Click to collapse
Yes, I have noticed the difference: my personal phone is unencrypted and my work phone is encrypted. Both are M8s and there is a noticeable bootup lag. Performance wise, the difference is minimal and therefore tolerable.
But sadly I don't have a choice with the work phone.
Really just wanted to make sure that any encrypted device can be backup and subsequently restored. Now I'm confident it can, I have no trouble with resetting.
I can upgrade AndroidHD from 10.1 to 10.2 while I'm at it! :victory:
I managed to somehow break my 3 week old HTC 10's rear camera glass so I'm going to get it replaced via the "Uh-Oh Protection" since I bought from HTC directly.
I have the Unlocked US edition, but use it on Verizon. When I get my replacement phone, I'll go through the steps to Unlock via HTC dev, run Sunshine for S-OFF and change the CID/MID to Verizon. At that point, can I just flash a NANDROID backup from my old device onto the new one to get my ROM / Apps / etc. back? Will there be any issues since it'll be different hardware? The NANDROID will contain everything I need so I won't need to first apply the VZW RUU right? I think I've done it before on previous HTC hardware but I want to check if it'll work before I try it. Will encryption be an issue?
Sounds good as long as correct firmware is also flashed
drumz0rz said:
I managed to somehow break my 3 week old HTC 10's rear camera glass so I'm going to get it replaced via the "Uh-Oh Protection" since I bought from HTC directly.
I have the Unlocked US edition, but use it on Verizon. When I get my replacement phone, I'll go through the steps to Unlock via HTC dev, run Sunshine for S-OFF and change the CID/MID to Verizon. At that point, can I just flash a NANDROID backup from my old device onto the new one to get my ROM / Apps / etc. back? Will there be any issues since it'll be different hardware? The NANDROID will contain everything I need so I won't need to first apply the VZW RUU right? I think I've done it before on previous HTC hardware but I want to check if it'll work before I try it. Will encryption be an issue?
Click to expand...
Click to collapse
I don't see it being any issue.
So I just got my replacement phone. I followed the exact same steps as I did on my original HTC 10 to get s-off and convert to Verizon (used the same files as well). I made a fresh NANADROID backup on the old phone in TWRP, copied it over to the new phone, and restored it. When I reboot I get stuck on the white splash screen. I tried wiping the cache but I can't progress further.
I was really hoping I'd just be able to use the NANDROID so I don't have to go through the arduous process of backing up all of my apps and settings, and copying them over in TiBu, and having to recustomize everything in VenomHub/Xposed.
What am I doing wrong?
drumz0rz said:
So I just got my replacement phone. I followed the exact same steps as I did on my original HTC 10 to get s-off and convert to Verizon (used the same files as well). I made a fresh NANADROID backup on the old phone in TWRP, copied it over to the new phone, and restored it. When I reboot I get stuck on the white splash screen. I tried wiping the cache but I can't progress further.
I was really hoping I'd just be able to use the NANDROID so I don't have to go through the arduous process of backing up all of my apps and settings, and copying them over in TiBu, and having to recustomize everything in VenomHub/Xposed.
What am I doing wrong?
Click to expand...
Click to collapse
Try dirty flashing ROM
How would changing devices between TWRP backup/restore affect encryption?
EDIT: Since TWRP decrypts now, phone encryption would be a moot point in this context.
I received a replacement Uh-Oh phone from HTC. Unlocked bootloader, installed TWRP and S-Offed. Tried using my Nandroid to restore but TWRP would not see it (file names different, based on S/N). I created a small new backup to create the proper file structure and renamed the old Nandroid backup and placed it in the proper directory. Still would not work so I went to my TiBu backup and reset everything back up.
Here's a strange result though - my fingerprint works fine to unlock the phone but somewhere along the line (perhaps my attempt restoring Nandroid) the pattern lock changed. So now I cannot unlock phone using the pattern and cannot change it. I can use fingerprint so it works for now but I would like to reset the pattern lock - any ideas?
stebaile said:
I received a replacement Uh-Oh phone from HTC. Unlocked bootloader, installed TWRP and S-Offed. Tried using my Nandroid to restore but TWRP would not see it (file names different, based on S/N). I created a small new backup to create the proper file structure and renamed the old Nandroid backup and placed it in the proper directory. Still would not work so I went to my TiBu backup and reset everything back up.
Here's a strange result though - my fingerprint works fine to unlock the phone but somewhere along the line (perhaps my attempt restoring Nandroid) the pattern lock changed. So now I cannot unlock phone using the pattern and cannot change it. I can use fingerprint so it works for now but I would like to reset the pattern lock - any ideas?
Click to expand...
Click to collapse
So when you did a restore with TWRP, what was the result? What does "still would not work" mean exactly? What did the log say?
I'll have to dig into the log file but it is my habit to only backup /data. That's what I was trying to restore. I might need to factory reset to get the pin reset I suppose. Was hoping there was a file I could delete to reset the encryption.
Sent from my HTC 10 using XDA-Developers mobile app
Just in case anyone has this issue of losing their pattern lock from a Nandroid restore I found the answer in a different thread. Use a file manager with root access such as Root Explorer, or use TWRP's file manager capability to delete the locksettings.* files in /data/system. Reboot and your device will no longer have a pattern lock. You will need to create a new pattern lock along with new fingerprint unlocks.
stebaile said:
might need to factory reset to get the pin reset I suppose. Was hoping there was a file I could delete to reset the encryption.
Click to expand...
Click to collapse
Factory reset erases everything, leaving nothing to decrypt.
Your idea of "reset encryption" would make encryption useless if anyone could just remove the lock without the PIN/password.
stebaile said:
Just in case anyone has this issue of losing their pattern lock from a Nandroid restore I found the answer in a different thread. Use a file manager with root access such as Root Explorer, or use TWRP's file manager capability to delete the locksettings.* files in /data/system. Reboot and your device will no longer have a pattern lock. You will need to create a new pattern lock along with new fingerprint unlocks.
Click to expand...
Click to collapse
Rolo42 said:
Factory reset erases everything, leaving nothing to decrypt.
Your idea of "reset encryption" would make encryption useless if anyone could just remove the lock without the PIN/password.
Click to expand...
Click to collapse
Next time just read the TWRP FAQ
http://forum.xda-developers.com/htc-10/development/recovery-twrp-touch-recovery-t3358139/page74
10. After I restored my Data backup and boot back to Android, I'm entering the correct PIN/password, but it's telling me the password is wrong. What happened, and how do I fix it?
It appears that sometimes after restoring a backup of Data where security was enabled (such as a PIN or password lock), the device does not recognize the correct password. There are two ways to avoid this issue:
Disable security in Android?*before?*making a backup of data.
After restoring Data, while still in TWRP, use the TWRP File Manager to navigate to /data/system and delete all the locksettings.* files (such as locksettings.db, etc). When you reboot, the password will be gone.
Click to expand...
Click to collapse
Maik268 said:
Next time just read the TWRP FAQ
http://forum.xda-developers.com/htc-10/development/recovery-twrp-touch-recovery-t3358139/page74
Click to expand...
Click to collapse
Is that referring to unlocking the screen or decrypting the device?
The question was referring to encryption.
When TWRP restores a backup, is it encrypted? (There's a few "it depends" to that question I would think.)
Hi guys, first, sry for my bad english.
I have a huge Problem. I did a Twrp Backup from my Viper rom. After Backing up, i installed cm13. After that, i would go back to my backup from Viper. The Problem is, i can restore the Backup but ive got a bootloop. How can i go back to my Backup ?
Next Problem is, everytime i start into twrp i got asked for the Decrypt password. How can i deactivate that ?
Which TWRP version are you currently on? Sounds asbif it is an older one. If so, try the latest 3.0.2-6 and report back.
Sent from my htc_pmeuhl using XDA Labs
hi, im on 3.0.2-6.
Now i restored my Viper backup. It Boots normaly.
Then i have type my Pin, that works. But after that, i have to unlock the Pattern lock. But it says my Code is Wrong.
I know it is the right code. I can try 1000000 different times, i cant unlock
pboden83 said:
hi, im on 3.0.2-6.
Now i restored my Viper backup. It Boots normaly.
Then i have type my Pin, that works. But after that, i have to unlock the Pattern lock. But it says my Code is Wrong.
I know it is the right code. I can try 1000000 different times, i cant unlock
Click to expand...
Click to collapse
directly from twrp FAQ:
"After I restored my Data backup and boot back to Android, I'm entering the correct PIN/password, but it's telling me the password is wrong. What happened, and how do I fix it?
It appears that sometimes after restoring a backup of Data where security was enabled (such as a PIN or password lock), the device does not recognize the correct password. There are two ways to avoid this issue:
Disable security in Android before making a backup of data.
After restoring Data, while still in TWRP, use the TWRP File Manager to navigate to /data/system and delete all the locksettings.* files (such as locksettings.db, etc). When you reboot, the password will be gone."
pboden83 said:
hi, im on 3.0.2-6.
Now i restored my Viper backup. It Boots normaly.
Then i have type my Pin, that works. But after that, i have to unlock the Pattern lock. But it says my Code is Wrong.
I know it is the right code. I can try 1000000 different times, i cant unlock
Click to expand...
Click to collapse
adb into the phone via TWRP or live system and rm -rf /system/data/*.key and locksettings* this will reset the security. no one currently knows why twrp is doing this but it seems to only happen to me when flashing a different rom then going back. it does NOT does this if restoring a previous backup of my current rom.
really the only file you need to delete is the locksettings.db file. I've never had issues deleting just that one.
I also tried this way to delete the locksetting.db and can bypass the suck lockscreen!
BTW, highly recommend you that in addition to whole system backup in TWRP, also use Titanium Backup to backup all user apps. In case of restore failure, you still can preserve your user apps and restore in newly installed system.
So, after feb OTA, my TWRP decided to not decrypt my partition anymore . So I went ahead and deleted Locksettings.db, locksettings.db-wal, and locksettings.db-shm in /data/system.
Now the problem begins. I rebooted my phone and now the phone is stuck at "android is starting" of course I did not backup what I deleted.
I flashed-all without wiping but it is still doing the same thing. Any idea out there that I could do something without wiping my phone?
jlee08517 said:
So, after feb OTA, my TWRP decided to not decrypt my partition anymore . So I went ahead and deleted Locksettings.db, locksettings.db-wal, and locksettings.db-shm in /data/system.
Now the problem begins. I rebooted my phone and now the phone is stuck at "android is starting" of course I did not backup what I deleted.
I flashed-all without wiping but it is still doing the same thing. Any idea out there that I could do something without wiping my phone?
Click to expand...
Click to collapse
I have the same problem on LineageOS. I even removed password before booting to TWRP, which usually caused the encryption message in twrp asking for a password.
jlee08517 said:
So, after feb OTA, my TWRP decided to not decrypt my partition anymore . So I went ahead and deleted Locksettings.db, locksettings.db-wal, and locksettings.db-shm in /data/system.
Now the problem begins. I rebooted my phone and now the phone is stuck at "android is starting" of course I did not backup what I deleted.
I flashed-all without wiping but it is still doing the same thing. Any idea out there that I could do something without wiping my phone?
Click to expand...
Click to collapse
Oh boy! Your the first I've seen with this one. I've used that method on the 6p many many times without issue. The P2XL is a different beast evidently. I'm sure the code master guys could figure it out, but that's not me. Did you make a backup before you started (S.O.P)?? I always do that before any update, and then move it to the pc before I begin. Been burned to many times with this stuff. I'm afraid the only advice I can give is to do a clean install of the latest update, then restore your data from a previous backup through twrp. Sorry my friend...been there...done that! ??
---------- Post added at 11:59 AM ---------- Previous post was at 11:55 AM ----------
Btw...this is a known issue with twrp now until it's updated. You have to remove all lock screen security in order to use TWRP effectively. Unfortunately, that does you no good I know. But, at least, now you know.
Badger50 said:
Oh boy! Your the first I've seen with this one. I've used that method on the 6p many many times without issue. The P2XL is a different beast evidently. I'm sure the code master guys could figure it out, but that's not me. Did you make a backup before you started (S.O.P)?? I always do that before any update, and then move it to the pc before I begin. Been burned to many times with this stuff. I'm afraid the only advice I can give is to do a clean install of the latest update, then restore your data from a previous backup through twrp. Sorry my friend...been there...done that! ??
---------- Post added at 11:59 AM ---------- Previous post was at 11:55 AM ----------
Btw...this is a known issue with twrp now until it's updated. You have to remove all lock screen security in order to use TWRP effectively. Unfortunately, that does you no good I know. But, at least, now you know.
Click to expand...
Click to collapse
Well of course I made a twrp backup on the device before I did all this but I can't get to any of those since twrp can't decrypt...
Remember I deleted the locksettings since twrp won't take my pattern? Haha it was just unlucky on my part.
jlee08517 said:
Well of course I made a twrp backup on the device before I did all this but I can't get to any of those since twrp can't decrypt...
Remember I deleted the locksettings since twrp won't take my pattern? Haha it was just unlucky on my part.
Click to expand...
Click to collapse
Wasn't trying to criticize your method, but you'd be surprised how many don't do backups then flash away...then something goes wrong, and, well, you know the rest. Since you tried dirty flashing the factory image, I'm afraid all you can do is clean instal the factory image and wipe it clean. Stupid question, but if you fastboot twrp again, are you still in the same boat? Probably so, but thought I'd ask.
Badger50 said:
Wasn't trying to criticize your method, but you'd be surprised how many don't do backups then flash away...then something goes wrong, and, well, you know the rest. Since you tried dirty flashing the factory image, I'm afraid all you can do is clean instal the factory image and wipe it clean. Stupid question, but if you fastboot twrp again, are you still in the same boat? Probably so, but thought I'd ask.
Click to expand...
Click to collapse
Ah I didn't mean to come off that way. It's all good. Yeah I probably should write a PSA on twrp about this. So I went back to twrp and everything is gibberish since it's encrypted. I tried adb but it wasn't able to find the /sdcard path. I'm guessing that's also because the device was not being decrypted? And i tried to reboot into the safe mode. All kinds of mess. I just gave up and formatted the device. There goes all my /sdcard stuff.... I really need to start backing up titanium into the cloud..
jlee08517 said:
Ah I didn't mean to come off that way. It's all good. Yeah I probably should write a PSA on twrp about this. So I went back to twrp and everything is gibberish since it's encrypted. I tried adb but it wasn't able to find the /sdcard path. I'm guessing that's also because the device was not being decrypted? And i tried to reboot into the safe mode. All kinds of mess. I just gave up and formatted the device. There goes all my /sdcard stuff.... I really need to start backing up titanium into the cloud..
Click to expand...
Click to collapse
Sorry man, that sucks! I've done that more times than I can remember. Going forward, after I backup everything, including all my apps on TiBu, I save my TiBu file to my pc, then transfer it back after I'm back up and running. Best of luck to ya bro ?
A similar saga can be found here. For an encrypted data partition there is still no solution, as it seems, see my posting in that same thread.