Related
I have rooted other devices, and I understand the benefits...but there is a bit of a pain. Once you root your device, the way I understand it, you need to wait for an OTA update to be made available via a developer here. Now that usually happens pretty quickly, so that's not the issue. However, usually when you get an update OTA, you don't have to reinstall all your apps again, set up your screens, etc. When you take an update from here, you usually do need to reinstall everything.
If I want to avoid that, and let OTAs happen as they should, is there an easy and right way for me to get Titanium Backup to restore but keep that ability? Do I unlock the bootloader and root, then unroot but leave the bootloader unlocked? It isn't clear, and there seems a lot of noise when people ask, about what you can do that would still allow OTAs. Some seem to say you can take them, others suggest you can't. I have searched, and it is confusing. I would love to know if someone really knows, or could cite a post or article that I may have missed. I know I could loose root in that process, I get that risk. I just want to understand my options.
It is, as an aside, so painful that Android has not properly dealt with backup and restore and migrating apps/data from one device to another in the OS. That seems such a gaping hole that Apple has filed, and one big reason (not always the only one) I seem to end up rooting a device right away. I suspect I would root eventually, but probably wait a bit except for this.
Thanks
RoboCuz said:
I have rooted other devices, and I understand the benefits...but there is a bit of a pain. Once you root your device, the way I understand it, you need to wait for an OTA update to be made available via a developer here. Now that usually happens pretty quickly, so that's not the issue. However, usually when you get an update OTA, you don't have to reinstall all your apps again, set up your screens, etc. When you take an update from here, you usually do need to reinstall everything.
If I want to avoid that, and let OTAs happen as they should, is there an easy and right way for me to get Titanium Backup to restore but keep that ability? Do I unlock the bootloader and root, then unroot but leave the bootloader unlocked? It isn't clear, and there seems a lot of noise when people ask, about what you can do that would still allow OTAs. Some seem to say you can take them, others suggest you can't. I have searched, and it is confusing. I would love to know if someone really knows, or could cite a post or article that I may have missed. I know I could loose root in that process, I get that risk. I just want to understand my options.
It is, as an aside, so painful that Android has not properly dealt with backup and restore and migrating apps/data from one device to another in the OS. That seems such a gaping hole that Apple has filed, and one big reason (not always the only one) I seem to end up rooting a device right away. I suspect I would root eventually, but probably wait a bit except for this.
Thanks
Click to expand...
Click to collapse
Why not just unroot get the OTA and reboot? It's so easy with the toolkit you could even relock and unlock at the same time if necessary
Sent from my Nexus 7 using Tapatalk 2
That's a good idea...I guess I hadn't thought of that...but unlocking and relocking would wipe the device, no? If I am going to wipe the device to get the OTA, then I would just proceed through the "normal" way of waiting for someone to release the update in a ROM and flash it. I would just like, in some way, to treat this device like an appliance, and not worry about OTAs bricking my phone, or needing to reinstall everything to get the latest...I just want to start off restoring some of my apps from another device, and then (maybe) just let the updates take their course. I know I could change my mind later and start ROMing, but I just wanted to understand my options....I know I wipe the device when I unlock, so assumed that would happen each time. And I wasn't sure if I needed to unlock to JUST get root, if I am not planning on flashing ROMs. And can I just root,and then use OTA rootkeeper if necessary, and allow updates?
So I guess the questions are:
- Do I need to unlock to root?
- Once I have done what I need to use Titanium (unlock and root or just root), can I take an OTA update, or do I need to undo some or all?
- If I undo some or all, will that incur a wipe?
I think I figured this out...I found the manual for the Nexus Root Toolkit (www.wugfresh.com/dev/nexus-root-toolkit/), and that spells out a LOT of really clear information.
I think I would:
- unlock
- root and install CWM
- use Titanium, etc.
Later, if an OTA comes out I want to allow:
- probably do full CWM backup
- flash stock recovery
- install and run OTA Rootkeeper
- allow the OTA, knowing I might loose root
- reflash CWM
I think this shouldn't cause any issues. This assumes I am basically running stock, and just using root for backup/restore app stuff with Titanium and maybe Root Explorer.
Make sense?
I've been rooting devices since my first android device. And using Titanium Backup, to always restore my app data across devices. Or restoring Nandroid backups at times. But it seems with that, upgrades to new OS have become more of a hassle. Since I can not simply let the OTA apply its self.
Having to change to stock recovery depending on the device and in some more recent cases, having to wipe data for the update to go well. It has become a bit of a pain, harder than it used to be.
With Marshmellow doing app data backup. I'm going to try keeping things virgin, no rooting. I may not need to continue with Titanium Backup and since OTAs will work flawlessly, I won't have much personal need to get into the system file area.
So what about you? Respond to the poll and give your take .
I've always done clean install of ROMs, and I always start from scratch with each ROM flash. I'll root as soon as there's a root out.
I mistakenly marked "Yes" to my poll .
Sent from my Nexus 10 using Tapatalk
Root/Unlocked Bootloader is 75% of the reason why I go with Android. I like the feeling of knowing that I "own" the device and can do with it as I please.
rockerrock said:
Root/Unlocked Bootloader is 75% of the reason why I go with Android. I like the feeling of knowing that I "own" the device and can do with it as I please.
Click to expand...
Click to collapse
+1. I got rid of my Verizon S6 because it was way too locked down.
lol asking this on a dev forum... I'd be surprised if anyone says no. It's more than just app back ups. I think phone should ship with root, just enable it/ disable it in the development options. It's like being a standard user on your own laptop instead of administrator... I mean why?
I can see this option on Nexus devices and non-carrier branded devices, but it would never be allowed with a Carrier device. It would be like a work laptop being allowed on that network with software meant to bypass firewalls. Bigger companies will never allow it because of security risks. That being said, I do agree that it should be an option for everyday users.
I need to recover data from a samsung galaxy s7 edge, but I don't know the code for unlocking the screen. There's a way to bypass this?
1. How could You forget a 4 digit pin code? Seriously.
2. Is it rooted? Any custom rom on it? Encryption?
ProtoDeVNan0 said:
1. How could You forget a 4 digit pin code? Seriously.
2. Is it rooted? Any custom rom on it? Encryption?
Click to expand...
Click to collapse
It isn't mine, it was of a dead person and the family asks me to recover data but they don't know the pin.
It's fully original.
Then I'm not sure if it's possible.
If it didn't have encryption enabled (it's enabled by default by samsung) then You could flash TWRP and then flash a zip file which removes certain files in Data partition and well, unlocks the device (I've done it before when I broke my lock screen buttons). But with Encryption being enabled TWRP won't be able to read Data partition and yeah. I'm not sure if You can even access internal storage through TWRP.
Maybe try all possible combinations? Or the most popular ones.
Try this:
Flash TWRP(a detailed instruction is on XDA)
Tap on advanced and then file manager.
You should be able to see internal storage if it's not encrypted, and then just copy all files that You want to sd card or just mount usb storage.
But if the encryption covers Data and internal storage then I don't think You can do anything.
Like I said, in the worst case try using most popular code combinations and maybe one will work. But try that before flashing TWRP, cause TWRP might soft brick the device.
No. Who knows what you're really after? I'm totally against questions like these and would urge people not to answer. If it's really your own device, you have to deal with the consequences of forgetting a 4 digit number.
Not possible with encryption, only way is brute forcing it and it might auto wipe after 15 attempts
Really??? Xda is the first place someone with this situation would ask for help? First post? I'm calling BS.
If - hah - you are legit, the "dead" person's phone is still under warranty, therefore the "family" can take the phone to the dealer/network provider and get help there.
sounds very suspicious
Hi all,
Just ordered my OnePlus 5 and doing a little research whilst waiting for it to reply.
I'm struggling to understand why people would choose to disable encryption - have I missed something?
The only 'downside' to having it (that I can see) is having to unlock with a pattern/PIN at first boot (and when entering TWPR etc). I guess there will also be a slight performance hit, but shouldn't be noticeable.
The 'upsides' to having it are the added security if you loose your phone (and maybe Magisk needs it).
Removing encryption needs an extra file to flash after installing TWRP, and then having to format the user partition / sd card.
Any thoughts?
Cheers,
phoenix1589 said:
Hi all,
Just ordered my OnePlus 5 and doing a little research whilst waiting for it to reply.
I'm struggling to understand why people would choose to disable encryption - have I missed something?
The only 'downside' to having it (that I can see) is having to unlock with a pattern/PIN at first boot (and when entering TWPR etc). I guess there will also be a slight performance hit, but shouldn't be noticeable.
The 'upsides' to having it are the added security if you loose your phone (and maybe Magisk needs it).
Removing encryption needs an extra file to flash after installing TWRP, and then having to format the user partition / sd card.
Any thoughts?
Cheers,
Click to expand...
Click to collapse
I second this opinion, I'd like to know before my device arrives tomorrow.
I did find a thread on the OP3 forums earlier, the read/write speed difference is negligible... So performance wise it doesn't make much difference.
My university requires an encrypted phone for Outlook though... Not a big deal as there are plenty of other alternate email apps available but it'd be nice to use for a change.
Alex Charles said:
I second this opinion, I'd like to know before my device arrives tomorrow.
I did find a thread on the OP3 forums earlier, the read/write speed difference is negligible... So performance wise it doesn't make much difference.
My university requires an encrypted phone for Outlook though... Not a big deal as there are plenty of other alternate email apps available but it'd be nice to use for a change.
Click to expand...
Click to collapse
my 1+3 was always encrypted, never had to wait for anything.
Gesendet von meinem Lenovo YT3-X50F mit Tapatalk
I remember reading something about not being able to restore data partition from a nandroid backup as it leads to bootloop and something about not being able to make a backup with security such as PIN, is this the case or an i mistaken?
AllEyezOnMe said:
I remember reading something about not being able to restore data partition from a nandroid backup as it leads to bootloop and something about not being able to make a backup with security such as PIN, is this the case or an i mistaken?
Click to expand...
Click to collapse
As far as nandroid backups and the data partition restore causing bootloops, there is a TWRP beta version released where the dev is asking for someone to test if it is fixed. As of that threads current posts no one has stepped up and confirmed if its fixed one way or the other.
You are correct that it is recommend that before you take a nandroid backup that you need to change your lock screen security to swipe or none. Otherwise a restore causes bootloops but there is a documented workaround using TWRP.
The workaround results in your lock screen security being removed (specific files are deleted). What I don't like about being forced to remove the lock screen security to do a nandroid backup is that it also wipes all your finger print input. Re-entering a pin number or swipe, is not much of a bother but doing four fingerprint training each time I want to take a safe nandroid backup is a pain. Previously I liked doing a nandroid backup at least once a week now I'll only do it when I feel any system changes (e.g. OTA, ROM flash), will put my phone at risk. With that being written I will still remain encrypted at least for the foreseeable future.
What I don't like about being forced to remove the lock screen security to do a nandroid backup is that it also wipes all your finger print input. Re-entering a pin number or swipe, is not much of a bother but doing four fingerprint training each time I want to take a safe nandroid backup is a pain.
Click to expand...
Click to collapse
Is there not some kind of system-app that holds this info, that we could back-up with Titanium, and restore after taking the Nandroid? Still a bit of work, but at least you'll be consequent.
Encryption is automatically enabled if you set up any sort of screen lock (PIN, etc). Booting into recovery gives you a password prompt by which the PIN does not work as a decryption password.
gdanko said:
Encryption is automatically enabled if you set up any sort of screen lock (PIN, etc). Booting into recovery gives you a password prompt by which the PIN does not work as a decryption password.
Click to expand...
Click to collapse
So how do you decrypt to access files from within TWRP recovery? Given this is needed to do backups (which are working, according to the TWRP 3.1.1 thread) there must be a way.
gdanko said:
Encryption is automatically enabled if you set up any sort of screen lock (PIN, etc). Booting into recovery gives you a password prompt by which the PIN does not work as a decryption password.
Click to expand...
Click to collapse
In my case the PIN I've set up works perfectly as decryption password.
phoenix1589 said:
So how do you decrypt to access files from within TWRP recovery? Given this is needed to do backups (which are working, according to the TWRP 3.1.1 thread) there must be a way.
Click to expand...
Click to collapse
depends on the right twrp version. dont look for the original one yet, look for the right one for the op5.
halfblack said:
In my case the PIN I've set up works perfectly as decryption password.
Click to expand...
Click to collapse
I've tried both PIN and password with zero success.
---------- Post added at 11:46 PM ---------- Previous post was at 11:44 PM ----------
halfblack said:
In my case the PIN I've set up works perfectly as decryption password.
Click to expand...
Click to collapse
What version of OxygenOS do you have?
gdanko said:
I've tried both PIN and password with zero success.
---------- Post added at 11:46 PM ---------- Previous post was at 11:44 PM ----------
What version of OxygenOS do you have?
Click to expand...
Click to collapse
I went from 4.5.0 to 4.5.3. I don't know what makes it work for me (I remember that I had issues just like you did on 3T).
From what I've gathered, you must remove pattern/PIN protection (I'm assuming this disables encryption?) before creating a backup via TWRP or else it will be impossible to decrypt (even with the right pattern/PIN), requiring a factory reset, which kinda negates the whole point of a backup. As long as you remember to do that (or TWRP for the OP5 matures a little more, it is after all only a few days old at this point), there isn't really a reason to disable it.
Also, any non OxygenOS based ROM will need the data to be decrypted for it to boot.
There are a few reasons to decrypt, but if you have to ask why you should or shouldn't, then you probably don't need to decrypt if the first place, so don't.
So I need to decrypt in order to flash roms?
Not, there is no reason to. Bare in mind I always decrypted my phone's
The trade off just isn't worth it.
Run a script is enter a password, either way you have work to do.
Sent from my ONEPLUS A5000 using XDA-Developers Legacy app
gursimar said:
So I need to decrypt in order to flash roms?
Click to expand...
Click to collapse
For the oreo Rom yes
Padres_1984 said:
For the oreo Rom yes
Click to expand...
Click to collapse
When it's completely released this should not be the case.
How I decrypt my phone. There is something called no verity, but I can't find it.
Odoslané z ONEPLUS A5000 pomocou Tapatalku
chlap said:
How I decrypt my phone. There is something called no verity, but I can't find it.
Odoslané z ONEPLUS A5000 pomocou Tapatalku
Click to expand...
Click to collapse
To decrypt your phone you need to back it up and format data..if you check my signature you'll see the method I used for no limits Oreo (decrypted) from nougat (encrypted)
This is typical story, didn't take backups, didn't read, my own fault. Just want you guy to help me to let go.
Xiaomi Mi A1 .
Android 8.1 July Updates.
Followed this guide: https://www.xda-developers.com/enable-google-camera-hdr-eis-xiaomi-mi-a1-without-root/
After oem unlock and reboot, got fully mint condition android, no files, no apps nothing. Don't remembrer if internal memory was encrypted.. maybe.. before I've removed pin and fingerprint.
After that, rooted phone using this guide: https://www.youtube.com/watch?v=cBkWUhJiqq8
Tried https://www.easeus.com - found nothing.
Can somebody just say: "It is impossible to restore any data after oem unlock and data being wiped out?"
Can I take some raw filesystem image and try to recover at least something?
IF your phone was encrypted, and got wiped during unlocking You can't do anything, especially on Oreo :c
I am not sure, but as Android clean itself, it not simply delete files, but overwrite space, that those files were stored on, to prevent unauthorised access.
you should've backed up before oem unlocking but if u ask me its good to reset ur phone because then u realize what apps u actually need and you will also realize it doesn't take that long to download the apps and btw you should enable the auto backuping feature so it doesn't matter if u forgot to backup because when u will reset ur phone u can access the backup that was backed up not that long ago
Erecik said:
IF your phone was encrypted, and got wiped during unlocking You can't do anything, especially on Oreo :c
I am not sure, but as Android clean itself, it not simply delete files, but overwrite space, that those files were stored on, to prevent unauthorised access.
Click to expand...
Click to collapse
Let's say it wasn't encrypted, what are the tools and process of trying it out?
YayJohn said:
you should've backed up before oem unlocking but if u ask me its good to reset ur phone because then u realize what apps u actually need and you will also realize it doesn't take that long to download the apps and btw you should enable the auto backuping feature so it doesn't matter if u forgot to backup because when u will reset ur phone u can access the backup that was backed up not that long ago
Click to expand...
Click to collapse
Yeah, thanks, it made me feel better but I've lost photos and files, that were important to me, and I'm paranoid enough not to have automatic backups to google
Try Disk Digger for Android. It helped me many times on PC. May be viable on android too. Use root mode if you can.
SiTox said:
Yeah, thanks, it made me feel better but I've lost photos and files, that were important to me, and I'm paranoid enough not to have automatic backups to google
Click to expand...
Click to collapse
I dont know what files you lost but you should use google photos so it automatically backs up photos when u just take them, and also what is there to be paranoid of from enabling automatic backups from google?