Related
ok that's the story. (sorry for bad english )
iv'e upgrade my android 4.4 to 5.0.1 and now i got no root , and my bootloader is locked.
i have pictures,apps,sms,whatsapp conversations that i want to keep , and i understaned that if i unlock my bootload so all the data will be removed.
in 4.4 kitkat i used TowelRoot to root my phone and it worked like magic without delete anything.
theres a way i can root my 5.0.1 nexus 4 without lose any data ?
Thanks !
No, there is no way to root without unlocking first.
Sent from my Nexus 5 using XDA Free mobile app
No, there is no way to unlock with it wiping. Why not just copy the data off the phone onto some other device and copy back once you are unlocked?
Just use AndroidSDK to backup your device. You can root and then restore your phone to its state just as it was. Even your offline games progresses will keep.
If root is working without problems, you could try to unlock it using BootUnlocker
EDIT: Sorry, I've overseen that you're on 5.0.1 without root. veketash's tip is the best you can do, then.
you can't do root before unlock...
Everyone saying you cant root without unlock is wrong. I have rooted my N4 with towelroot and then unlocked my bootloader without wiping any data at all using BootUnlocker. So you technically can unlock it without wiping data.
EDIT: Nevermind I didnt see he was using 5.0.1 yeah then there is no way of unlocking without wiping data.
veketash said:
Just use AndroidSDK to backup your device. You can root and then restore your phone to its state just as it was. Even your offline games progresses will keep.
Click to expand...
Click to collapse
well im gonna try this now .. i hope it will work good and all the data will keep in the phone.
thanks..
edit :
well i backup using guide that i found in google
and the backup file size is 196MB.
my phone has like 10GB of data
edit 2:
i tried again do the same thing and now the file is more then 300MB and its keep growing.
I wanted to share two things with you guys here in Tablet z forum:
1- First of all, @zxz0O0 has developed a code based on the CVE-2015-1805 vulnerability that gives temporary root access to a select range of devices (including Tablet Z4). Let me try to explain in my words what that means. A full blown root gives permanent read/write access to /system and /data partitions. On an unrooted Tablet Z4 you only have read access to /system and no access to /data. With this root, you will be able to have a temporary terminal or adb session that gives you read access to /system and read/write access to /data. Why not write access to /system? Because Sony runs a service called RIC on Xperia devices that makes it impossible to mount /system as writable. In the past this would be patched by modifying the system partition. But in the recent Kernels sony has implemented a mechanism (dm-verity) which checks /system and if it is modified the device does not boot. So even if this (or any other) root method gave you the ability to write in /system you could not use it because your device would not restart the next time you turn it off. The solution would be to patch the kernel which requires an unlocked bootloader. IF you unlock your bootloader you lose your TA partition permanently which includes some of the Xperia features and licenses that have to do with image processing and some DRM. So a lot of us do not want to unlock the bootloader.
Then what good is this new root method? Since it gives you read access to the system partitions you can use this method to back up your TA partition. The idea is that if you ever unlock your bootloader you may be able to use this TA back up to return the system to its original state if you ever decide to relock it. Another benefit is that tools like Titanium back up which require access to the /data partition can now function (in a limited sense) although someone has to work out the details of that.
To download the pack that allows backup and restore of the TA partition go to http://forum.xda-developers.com/crossdevice-dev/sony/iovyroot-temp-root-tool-t3349597
After you create the backup, you can unlock the bootloader, and use your TA backup and the procedure outlined here: http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605 to create a csutom kernel that uses all the good stuff in the TA backup and emulates an environment where your tablet behaves like one with an unlocked bootloader. The camera denoising algorithm and all other Sony proprietary software which would be disabled after unlocking the bootloader should work.
If you want to return the tablet to its unlocked condition you will need this TA backup. Some explanation about retrieving the TA partition from this backup, if you unlock the bootloader and decide to relock it, is given here http://forum.xda-developers.com/showpost.php?p=66142823&postcount=16 and methods to do so are outlined at: http://forum.xda-developers.com/showpost.php?p=66158970&postcount=68
Note that to use this root you need to downgrade to lollipop (preferably version 28.0.A.8.260)
I have explained procedures to use the above tools here http://forum.xda-developers.com/z4-tablet/general/guide-safe-bootloader-unlock-restore-t3362391 at length.
2- Now, here is the use I have found for this temporary root: I was always bothered by the fact that not only I could not (easily) get the 17 hour advertised on-screen use out of my tablet, the standby power consumption was always too much. Whereas I could optimize my other (rooted) devices to only drain 1-2% a day in standby, tablet Z4 seems to settle for nothing less that 5-10% a day in standby. This is what you can do to get excellent standby power from your tablet:
A) Say goodbye to your google apps (with the exception of Chrome and Maps) and other marginally advantageous apps. They wake your device up all the time when it is supposed be sleeping and endlessly chat with google servers even if you turn all the communications off in the google settings. So disable all of the apps listed in the attached pictures , plus lifelog,via settings. Don't complain about not being able to use the gmail or youtube apps. Other great replacements exist. Leave "Google App" active if you use the voice search or voice typing feature. Also uninstall the pre-loaded apps that you aren't using like facebook (which is cancer for any phone), Lifelog, Privilege, spotify, etc.
B) In settings under wifi open the advance menu turn off both "network notification" and "scanning always available", and change "keep wifi on" to "only when plugged in"
C) Under "power management" in settings, activate stamina mode and extended standby (no need to activate extended usage).
D) Finally (and here is where the temp root becomes useful) extract the file "iovyroot" from the file in the above link and put it in your adb directory. Open a command terminal and type:
Code:
adb push root\iovyroot /data/local/tmp/iovyroot
adb shell chmod 777 /data/local/tmp/iovyroot
adb shell
This gives you an android terminal shell. Continue with the following:
Code:
/data/local/tmp/iovyroot
pm disable com.sonyericsson.idd.agent
pm disable com.sonymobile.entrance
pm disable com.sonyericsson.updatecenter
pm disable com.sonymobile.anondata
pm disable com.dsi.ant.server
pm disable com.sonymobile.gmailreaderservice
pm disable com.sonymobile.googleanalyticsproxy
pm disable com.sonymobile.mx.android
pm disable com.sonymobile.enterprise.service
pm disable com.sonymobile.synchub
pm disable com.sonymobile.phoneusage
That is it. You just disabled the update service and a bunch of other things and extended your standby battery life. These settings will survive a reboot.
Let me know how it works out for you. If you find other creative uses for this temp root share here.
This is the BEST and probably the most right to the real point post ive ever readed in this particular forum since I joined....
Forgive me if I say I have had lost the faith on sony's z4t development here... It's a real pleasure to know there's still ppl working on what I think should be the right development direction on gettin' control of our loved devices, instead of breaking them and throw a lot of expensive features to the flush.
Thanks again mate to share it.
Interesting, if I downgrade do I also lose my Marshmallow data and settings (i.e. is it the same as factory reset?)
BTW Finally this tablet becomes viable, almost a year after its release...
Stevethegreat said:
Interesting, if I downgrade do I also lose my Marshmallow data and settings (i.e. is it the same as factory reset?)
BTW Finally this tablet becomes viable, almost a year after its release...
Click to expand...
Click to collapse
If you want to have a stable system you will need to overwrite the user data which means you will lose your apps and settings and possibly (depending on how you flash) your internal storage so make a back up.
In general application data of Android firmware are not downward compatible with older versions.
Hmm, but if you can also temp root then you can backup everything using TitaniumBackup anyway before unlocking.
So if I understand this right, if you can back up TA we can infact unlock the bootloader now with no loss of DRM ?
So can now actually get full root based on that ?
najoor said:
If you want to have a stable system you will need to overwrite the user data which means you will lose your apps and settings and possibly (depending on how you flash) your internal storage so make a back up.
In general application data of Android firmware are not downward compatible with older versions.
Click to expand...
Click to collapse
I will only downgrade to get a TA Backup, so stability is not an issue to me (after the TA Backup, I'll go back to MM and probably unlock it).
My only issue would be if downgrading would actually harm my data and/or my capacity to get the TA backup properly (if I'm not wipe first I mean).
Stevethegreat said:
I will only downgrade to get a TA Backup, so stability is not an issue to me (after the TA Backup, I'll go back to MM and probably unlock it).
My only issue would be if downgrading would actually harm my data and/or my capacity to get the TA backup properly (if I'm not wipe first I mean).
Click to expand...
Click to collapse
I don't think it will affect the TA back up process by it may harm you application data (not your sdcard data). The reason is that on every reboot android cleans up the) /data partition as much as it can (for example if it sees that an app has been uninstall but it has left some data behind). I'm doing so lollipop may corrupt some of your marshmallow data,
Why don't you take a backup of your data before a downgrade and the restore them later? The tablet itself has a utility to do it and I hear Helium is a tool that backs up your app data without the need for root.
najoor said:
I don't think it will affect the TA back up process by it may harm you application data (not your sdcard data). The reason is that on every reboot android cleans up the) /data partition as much as it can (for example if it sees that an app has been uninstall but it has left some data behind). I'm doing so lollipop may corrupt some of your marshmallow data,
Why don't you take a backup of your data before a downgrade and the restore them later? The tablet itself has a utility to do it and I hear Helium is a tool that backs up your app data without the need for root.
Click to expand...
Click to collapse
Mostly to save time as I have too much data. I though to do it like this
Downgrade to Lollipop -> Use the Exploit -> TA Backup -> Upgrade back to Marshmallow.
In principle everything should have had worked as by the end of it I would be back to Marshmallow (I would not linger into Lollipop). But now that you're telling me that lollipop may corrupt my data permanently I have second thoughts.
I thought, that my data would not work well on Lollipop, but that wouldn't matter to me; but now you're telling me that they won't work when I'll back in Marshmallow too, which is a totally different beast. Am I understanding you correctly?
Does everyone need to downgrade tho?
Once we have the TA partition available to restore, once its made available online surely everyone else can just restore the same one?
Or is the key unique?
Kinda assuming here that all the stuff that needs the TA partition will work with an unlocked bootloader, or does it have to be locked to be usable again?
Edit: Can we restore TA partition after unlocking bootloader?
Yes but this will also relock the bootloader.
Bugger
Ultimately never rooted my device for fear of losing something (that I will never use anyway!)
DRM Keys are unique, in fact that's the whole point of TA backups.
Also there's a talk (on the other thread) of a tool that would merge your particular keys with a particular custom kernel.
That way you'd keep all Sony Exclusive features, but also be able to make use of root apps. It would be great if such a tool becomes usable with AndroPlus Kernel...
Nice, had all but given up hope of being able to unlock my Z4 so that sounds promising!
I am looking for a high-end tablet and it seemed the Z4 Tablet was the best one for me over the Pixel C and even the iPad Air 2..though I did consider the budget Nvidia Shield K1 also.
The next thing I did was see if the bootloader could be unlocked and custom ROMs installed as I really hate the Sony UI that I have experienced with my sisters M2, and I never stick to the stock ROM in any of my phones. I just love knowing and doing customising!!
..Unfortunately, it seems like I will be stuck with it so I may have to look for another brand now
D0MINO said:
I am looking for a high-end tablet and it seemed the Z4 Tablet was the best one for me over the Pixel C and even the iPad Air 2..though I did consider the budget Nvidia Shield K1 also.
The next thing I did was see if the bootloader could be unlocked and custom ROMs installed as I really hate the Sony UI that I have experienced with my sisters M2, and I never stick to the stock ROM in any of my phones. I just love knowing and doing customising!!
..Unfortunately, it seems like I will be stuck with it so I may have to look for another brand now
Click to expand...
Click to collapse
I don't know how you got that impression, since the whole point of the OP and the links I posted with it is that you will not be stuck with the stock firmware.
So to summarize the points mentioned in the OP:
As of today, the following is possible with a tablet Z4:
1- The TA partition can be backed up.
2- The booloader can be unlocked.
3- The unlocking is reversible with the help of the backed up TA pertition
4- When the bootloader is unlocked a custom kernel can be flashed (currently one is posted in the Z4 forum courtesy of @AndroPlus).
5- When the bootloader is unlocked the stick Kernel can be patched to retrieve the Xperia proprietary facilities that are lost to the unlocking process (courtesy of @tobias.waldvogel).
6- When the bootloader is unlocked /system can be fully modified. That means flashing completely custom ROMs.
So you can either make your own modification to the system, or wait for someone to make a ROM. In light of the above possibilities it is only a matter of time before customs ROMs start to pop up.
By the way, to the extent that the stock firmware is customizable without unlocking the bootloader, it is actually a good ROM and you can change a lot of things from the general appearance to the default launcher.
PS: Tablet Z4 is my second Sony tablet and the third Sony mobile device and I have about 10 of this kind of devices at any given time. The other android devices are miles behind in terms of elegance and manufacturing quality. There is just something about a Sony device that is unique and unmatched.
Can anyone confirm how to re-lock the bootloader once unlocked?
I would say:
1. Flash a stock firmware (the lollipop version that you used to backup the TA partition).
2. Use the iovyroot temp root batch tarestore to restore your TA partition.
3. Reboot and that's it: you are back to unlocked bootloader unrooted original drm included stock firmware.
Anyone already tried?
Thank you.
I unlocked the bootloader and rooted the device SGP771.
Bevor that, i backed up the TA.
Then i flashed the androplus kernel.
Everything works great.
But you cannot modify androplus kernel with that tool. That means DRM restore is only possible on stock rom.
When you restore TA to stock rom, your bootloader will be in a lockes status again and there is no more root. Too bad
odicamillo said:
Can anyone confirm how to re-lock the bootloader once unlocked?
I would say:
1. Flash a stock firmware (the lollipop version that you used to backup the TA partition).
2. Use the iovyroot temp root batch tarestore to restore your TA partition.
3. Reboot and that's it: you are back to unlocked bootloader unrooted original drm included stock firmware.
Anyone already tried?
Thank you.
Click to expand...
Click to collapse
Can ta be restored on any fw like marshmallow or can it only be restored on the fw that you backed it up from?
This looks very promising, thanks OP.
Has anyone else managed to get it to work as described?
Thanks in advance
najoor said:
I don't know how you got that impression, since the whole point of the OP and the links I posted with it is that you will not be stuck with the stock firmware.
So to summarize the points mentioned in the OP:
As of today, the following is possible with a tablet Z4:
1- The TA partition can be backed up.
2- The booloader can be unlocked.
3- The unlocking is reversible with the help of the backed up TA pertition
4- When the bootloader is unlocked a custom kernel can be flashed (currently one is posted in the Z4 forum courtesy of @AndroPlus).
5- When the bootloader is unlocked the stick Kernel can be patched to retrieve the Xperia proprietary facilities that are lost to the unlocking process (courtesy of @tobias.waldvogel).
6- When the bootloader is unlocked /system can be fully modified. That means flashing completely custom ROMs.
So you can either make your own modification to the system, or wait for someone to make a ROM. In light of the above possibilities it is only a matter of time before customs ROMs start to pop up.
By the way, to the extent that the stock firmware is customizable without unlocking the bootloader, it is actually a good ROM and you can change a lot of things from the general appearance to the default launcher.
PS: Tablet Z4 is my second Sony tablet and the third Sony mobile device and I have about 10 of this kind of devices at any given time. The other android devices are miles behind in terms of elegance and manufacturing quality. There is just something about a Sony device that is unique and unmatched.
Click to expand...
Click to collapse
Dear najoor,
are you telling us that, now, we can unlock a z4 tablet which has the "rooting status: Bootloader unlock allowed: NO" , in the service info/configuration area ?!?
if it is the case, i would be delighted to know how to proceed step by step, as i would love to install a lineage rooted custom rom on it (it is the SGP771 one,with phone capability)!!!
thank you
kind regards from France
retikulatus said:
Dear najoor,
are you telling us that, now, we can unlock a z4 tablet which has the "rooting status: Bootloader unlock allowed: NO" , in the service info/configuration area ?!?
if it is the case, i would be delighted to know how to proceed step by step, as i would love to install a lineage rooted custom rom on it (it is the SGP771 one,with phone capability)!!!
thank you
kind regards from France
Click to expand...
Click to collapse
Unfortunately if that is the case you cannot unlock the bootloader.
I am just curious, why does yours look like that? Do you have myXperia or some other find-my-phone service activated on your phone?
najoor said:
Unfortunately if that is the case you cannot unlock the bootloader.
I am just curious, why does yours look like that? Do you have myXperia or some other find-my-phone service activated on your phone?
Click to expand...
Click to collapse
Thanks for the fast reply even if you ruined my hopes
no, i don't think i have myXperia , i checked on my apps and find nothing.
Since i had display issues with my tab s (sm-t800), i tried the z4 tablet for its LCD screen instead of the super amoled of samsung...
My bootloader was already locked when i purchased it, i updated it thinking it will change that but unfortunatly that did nothing.
It wasn't a new one though, perhaps the previews owner messed up with it and got its bootloader locked :/
Because it is some kind of lotery to have a bootloader unlockable with sony, i will wait patiently until samsumg release its 16:9/10 tab s4: imho, the tab s3 actual 4:3 format is a nonsense....
Thank you again
Kind regards from France
Hi I would like to unlock the bootloader and root once the new update rolls out but have quite a few private apps with preferences set. If I had TWRP I would just backup the data partition but I cannot do that.
I wanted to ask what you feel the most effective way to backup my apps and app data on a non-rooted virgin Shield? Does Google allow app data syncing on Android TV platform?
Thanks.
Please use the QUOTE feature when replying to me to get my attention. Thanks!
Bump
Please use the QUOTE feature when replying to me to get my attention. Thanks!
Bump
Please use the QUOTE feature when replying to me to get my attention. Thanks!
Anyone???
Please use the QUOTE feature when replying to me to get my attention. Thanks!
E--Man said:
Anyone???
Please use the QUOTE feature when replying to me to get my attention. Thanks!
Click to expand...
Click to collapse
Is it a 16GB og Pro version?
If it's a 16GB, there isn't really anything that just works, unfortunately.
If it's a Pro version, then you can pull the HDD and alter a partition to make it unlocked, then flash TWRP, backup and update (in theory).
E--Man said:
Anyone???
Please use the QUOTE feature when replying to me to get my attention. Thanks!
Click to expand...
Click to collapse
Umm you can't... That's kind of One, of the many other possible reasons why you root to begin with. e.g. being able to access restricted /data, and /system Partitions, for instance. As it is I would guess the only way you could possibly get at them would be though ADB. But, lol you have to also have root for that.*
NOTE: This is where those Rooted Recovery Images from nVIDIA come from. They are only rooted for ADB, and not for SuperSU. Or so I understand it.
So again I fairly sure your just going to have to bite it this time. Also (from someone with some experience in the matter), you may want to remove your SSHD, and make a few backups of it (See the SSHD to SSD Migration To), in case thing ever go ugh wrong. If your hell bent on rooting.
hallydamaster said:
Is it a 16GB og Pro version?
If it's a 16GB, there isn't really anything that just works, unfortunately.
If it's a Pro version, then you can pull the HDD and alter a partition to make it unlocked, then flash TWRP, backup and update (in theory).
Click to expand...
Click to collapse
Ichijoe said:
Umm you can't... That's kind of One, of the many other possible reasons why you root to begin with. e.g. being able to access restricted /data, and /system Partitions, for instance. As it is I would guess the only way you could possibly get at them would be though ADB. But, lol you have to also have root for that.*
NOTE: This is where those Rooted Recovery Images from nVIDIA come from. They are only rooted for ADB, and not for SuperSU. Or so I understand it.
So again I fairly sure your just going to have to bite it this time. Also (from someone with some experience in the matter), you may want to remove your SSHD, and make a few backups of it (See the SSHD to SSD Migration To), in case thing ever go ugh wrong. If your hell bent on rooting.
Click to expand...
Click to collapse
Taking the above into consideration, I am actually registered in the nVidia Developer Program and have access to the Developer images. Having said that, if I flash the Developer image, then I not just use the rooted ADB to make a backup of all the app data and then unlock boot loader and restore it?
Well irregardless of your having a Pro (Or, not)... You're still not going to get very far with what you are hoping to do. As you would have had, to have unlocked the Bootloader first. Before you could flash anything at all.
Unlocking the Bootloader will of course totally erase ALL OF YOUR PERSONAL DATA! And, that seems to be the catch-22 here, as you presumably do not want this. Of course OtOH if you ~are~ already unlocked then it shouldn't be a problem, then again booting TWRP from Fastboot, and eventually rooting shouldn't be a problem either.
But, since your Device has NOT yet been Bootloader unlocked, you CAN NOT actually do any of this yet.
I don't know what exactly it is you want to "backup", but you could use something like ES File Explorer to backup your Installed Apps, and your 'hidden' /system Apps (e.g. iPlayer), if thats your thing.
If you wanted to backup your Kodi stuff then ESFE could do that as well (But, you would have to enable Hidden Files to do this). Considering the recent loss of TVAddons. This in-and-of-itself, may well be good advice going forward for a while yet.
Ichijoe said:
Well irregardless of your having a Pro (Or, not)... You're still not going to get very far with what you are hoping to do. As you would have had, to have unlocked the Bootloader first. Before you could flash anything at all.
Unlocking the Bootloader will of course totally erase ALL OF YOUR PERSONAL DATA! And, that seems to be the catch-22 here, as you presumably do not want this. Of course OtOH if you ~are~ already unlocked then it shouldn't be a problem, then again booting TWRP from Fastboot, and eventually rooting shouldn't be a problem either.
But, since your Device has NOT yet been Bootloader unlocked, you CAN NOT actually do any of this yet.
I don't know what exactly it is you want to "backup", but you could use something like ES File Explorer to backup your Installed Apps, and your 'hidden' /system Apps (e.g. iPlayer), if thats your thing.
If you wanted to backup your Kodi stuff then ESFE could do that as well (But, you would have to enable Hidden Files to do this). Considering the recent loss of TVAddons. This in-and-of-itself, may well be good advice going forward for a while yet.
Click to expand...
Click to collapse
Thanks for the reply. There is only one discrepancy/question I have with your post - I was under the impression that I can flash the nVidia signed Developer ROM image *without* unlocking the bootloader, is that correct? If not, then I see your point and there is no way to access the app data files in the "data" partition. However, if I do not need to unlock the bootloader to flash the nVidia signed Developer image, and the nVidia signed Developer image is ADB rooted then I should be able to access the "data" partition.
Unless of course the flashing the nVidia signed Developer image will also wipe the "data" partition in the process
E--Man said:
Thanks for the reply. There is only one discrepancy/question I have with your post - I was under the impression that I can flash the nVidia signed Developer ROM image *without* unlocking the bootloader, is that correct? If not, then I see your point and there is no way to access the app data files in the "data" partition. However, if I do not need to unlock the bootloader to flash the nVidia signed Developer image, and the nVidia signed Developer image is ADB rooted then I should be able to access the "data" partition.
Unless of course the flashing the nVidia signed Developer image will also wipe the "data" partition in the process
Click to expand...
Click to collapse
This is taken from the Nvidia developer page:
NOTE: On the SHIELD Android TV Pro 500GB edition, some steps of the flash process may take a
Click to expand...
Click to collapse
hallydamaster said:
This is taken from the Nvidia developer page:
NOTE: On the SHIELD Android TV Pro 500GB edition, some steps of the flash process may take a
Click to expand...
Click to collapse
Darn, you are correct - it is required to unlock the bootloader to flash the nVidia Developer image. Too bad. Wish there was a way to extract app data! Some apps on mobile Devices use the Google Sync for app data, but I am not sure if this is employable on Android TV.
Click to expand...
Click to collapse
E--Man said:
Thanks for the reply. There is only one discrepancy/question I have with your post - I was under the impression that I can flash the nVidia signed Developer ROM image *without* unlocking the bootloader, is that correct? If not, then I see your point and there is no way to access the app data files in the "data" partition. However, if I do not need to unlock the bootloader to flash the nVidia signed Developer image, and the nVidia signed Developer image is ADB rooted then I should be able to access the "data" partition.
Unless of course the flashing the nVidia signed Developer image will also wipe the "data" partition in the process
Click to expand...
Click to collapse
To be fair, you would have to read the enclosed README File with the Dev ROM in question. I Have yet had no much reason to use it. So to be quite honest here I wouldn't know. OtOH though you do have to bootloader unlock the Device first of you wanted to flash a stock recovery Image. So everything that I think I know comes from that.
But, please extrapolate this idea of App Data further. I mean are we speaking about Apps, of pure Data (Al-la Kodi Data)?
'Cause these things can be backed up to degrees. If it's something well deeper than this. Well your just outta luck I'm afraid.
Ichijoe said:
To be fair, you would have to read the enclosed README File with the Dev ROM in question. I Have yet had no much reason to use it. So to be quite honest here I wouldn't know. OtOH though you do have to bootloader unlock the Device first of you wanted to flash a stock recovery Image. So everything that I think I know comes from that.
But, please extrapolate this idea of App Data further. I mean are we speaking about Apps, of pure Data (Al-la Kodi Data)?
'Cause these things can be backed up to degrees. If it's something well deeper than this. Well your just outta luck I'm afraid.
Click to expand...
Click to collapse
Hi lchijoe, I am just referring to the app preferences and their personal data that usually exists inside the "/data/data" folder. Some manufacturers allow exporting of this data even on non-rooted devices. For example, Huawei has a backup app which exports apps along with their personal data such that if you restore them it is as if you didn't even uninstall them to begin with. If I basically want to have everything restored as if I didn't do a factory reset.
.
Please use the QUOTE feature when replying to me to get my attention. Thanks!
Just bumping this in case anyone has any other input
Hello,
I doesn't know if this is a real problem in newer Android versions.
I apologize if this problem is already solved; i'm out of Android development since a while...
From me the problem is to protect MY data if I loss the phone...
If my phone is password protected (and bootloader locked), a person that found the device can't use it directly.
It can unlock the bootloader (more or less easily) but the phone data is removed by the unlock process.
My data is sure!
But if the bootloader is unlocked the person that has found my phone can acess to the custom recovery (or load a custom recovery if I'm on stock recovery) then force a wipe of the device.
Due to that, all my security (fingerprint and lock code) was erased and the user can access to my phone and also to all the data stored in /sdcard.
My data isn't sure!
It exists any mode to use a custom ROM but maintaining my data sure?
(I'm not confidence with the Google remote device access)
Thanks in advance!
I think you'll be fine, as the data on your internal memory should be encypted, which is enabled by default!
I'll be honest and I mean no offense but your data is worthless. If someone steals your device the first things done are Sim removed and devices reset or powered off. Data thieves don't get the data from stolen devices. They get it from the places we give it freely. Like shopping stores and on line accounts.
Nobody can access your phone data the way you describe unless you also run your phone decrypted --which is not the default for Android or even for custom ROMs for that matter. When you boot into recovery on a phone that is encrypted TWRP asks for your pin number and without it your data is not accessible. But that doesn't mean a thief couldn't still wipe and use your phone. You need to report it stolen so the IMEI number is blacklisted.
jhs39 said:
Nobody can access your phone data the way you describe unless you also run your phone decrypted --which is not the default for Android or even for custom ROMs for that matter. When you boot into recovery on a phone that is encrypted TWRP asks for your pin number and without it your data is not accessible. But that doesn't mean a thief couldn't still wipe and use your phone. You need to report it stolen so the IMEI number is blacklisted.
Click to expand...
Click to collapse
The /sdcard in phones that doesn't have external sdcard, like O+5, are also protected by the encriptation?
Thanks
bartito said:
The /sdcard in phones that doesn't have external sdcard, like O+5, are also protected by the encriptation?
Thanks
Click to expand...
Click to collapse
Yep, like any other android, the oneplus 5 has full disk encryption enabled by default:
http://www.androidpolice.com/2015/1...ll-disk-encryption-by-default-on-new-devices/
bartito said:
Hello,
I doesn't know if this is a real problem in newer Android versions.
I apologize if this problem is already solved; i'm out of Android development since a while...
...........................................
Click to expand...
Click to collapse
Well, IMO your concern is right to some extent.
With an unlocked bootloader, if there is some version of TWRP (or any other customer recovery for that matter) that can decrypt your data partition automatically or if you have ever formatted your /data partition from TWRP , or even an insecure kernel (most insecure kernels allow USB debugging without asking for authorization keys), all the thief needs is 2 adb commands and your screen lock will be turned off and all your stuff will be exposed 'as is'.
For educational purposes, the commands are:
Code:
adb shell rm /data/system/*.key
adb reboot
Now, for that matter, having a locked bootloader either doesn't ensure that your data is safe. For example, for HTC phones, you don't even need to unlock the bootloader for flashing a custom recovery or kernel. You can turn the phone to S-Off state using some proprietary tools (without losing data) and then flash custom images over a locked bootloader.
In case of Samsung, only FRP lock prevents you from flashing custom images (that too on newer phones) but in that case also, you can turn FRP off using some paid services and then flash any custom images and run the above mentioned commands.
In case of LG, it is even easier. Professional tools exist for communication over download mode protocol and turning off the screen lock doesn't even require a custom image in LG's case. However, most newer models are not supported by those tools yet.
In case of Apple, professional tools existed that used to read screen lock over a time span of 1-4 hours in an older version of iOS. I've heard that a tool is being made available for the current versions also in the coming weeks.
So, if you are conscious about your data, it is safe as far as the you have the phone in your possession. Once you lose it, you can't be sure about what is happening with it.
But then, as said in above posts, why would the thief want to crack open the data of a common man. If you are not a common man, you should worry. Otherwise I personally really don't care.
Hello,
Absolutelly appreciate your anwer.
I'm a common man, but I'm a bit worried due to 2 points:
1) I'm using LastPass and I doesn't would to my passwords to fall into someone's hands if I loss the device,
2) I'm using the app from my bank to pay using NFC and I doesn't would that anyone can use it
EDIT: 3) Of course, I'm using my Google account to store my contacts data. It would be a mess if someone erase my contacts
Thanks!
sikander3786 said:
Well, IMO your concern is right to some extent.
With an unlocked bootloader, if there is some version of TWRP (or any other customer recovery for that matter) that can decrypt your data partition automatically or if you have ever formatted your /data partition from TWRP , or even an insecure kernel (most insecure kernels allow USB debugging without asking for authorization keys), all the thief needs is 2 adb commands and your screen lock will be turned off and all your stuff will be exposed 'as is'.
For educational purposes, the commands are:
Code:
adb shell rm /data/system/*.key
adb reboot
Now, for that matter, having a locked bootloader either doesn't ensure that your data is safe. For example, for HTC phones, you don't even need to unlock the bootloader for flashing a custom recovery or kernel. You can turn the phone to S-Off state using some proprietary tools (without losing data) and then flash custom images over a locked bootloader.
In case of Samsung, only FRP lock prevents you from flashing custom images (that too on newer phones) but in that case also, you can turn FRP off using some paid services and then flash any custom images and run the above mentioned commands.
In case of LG, it is even easier. Professional tools exist for communication over download mode protocol and turning off the screen lock doesn't even require a custom image in LG's case. However, most newer models are not supported by those tools yet.
In case of Apple, professional tools existed that used to read screen lock over a time span of 1-4 hours in an older version of iOS. I've heard that a tool is being made available for the current versions also in the coming weeks.
So, if you are conscious about your data, it is safe as far as the you have the phone in your possession. Once you lose it, you can't be sure about what is happening with it.
But then, as said in above posts, why would the thief want to crack open the data of a common man. If you are not a common man, you should worry. Otherwise I personally really don't care.
Click to expand...
Click to collapse
jhs39 said:
Nobody can access your phone data the way you describe unless you also run your phone decrypted --which is not the default for Android or even for custom ROMs for that matter. When you boot into recovery on a phone that is encrypted TWRP asks for your pin number and without it your data is not accessible. But that doesn't mean a thief couldn't still wipe and use your phone. You need to report it stolen so the IMEI number is blacklisted.
Click to expand...
Click to collapse
Black listing the imei doesn't work everywhere. Plus while banned on xda so I can't say how. But the imei is not that hard to change.
bartito said:
Hello,
Absolutelly appreciate your anwer.
I'm a common man, but I'm a bit worried due to 2 points:
1) I'm using LastPass and I doesn't would to my passwords to fall into someone's hands if I loss the device,
2) I'm using the app from my bank to pay using NFC and I doesn't would that anyone can use it
EDIT: 3) Of course, I'm using my Google account to store my contacts data. It would be a mess if someone erase my contacts
Thanks!
Click to expand...
Click to collapse
Maybe some experts can give their opinion on how to protect your data using some third party apps or by using some other options that I am not aware of. But in my opinion, a phone with an unlocked bootloader is always more vulnerable than a phone with locked bootloader.
Of course, I agree with your affirmation at 100%
The question is: I can improve security if I keep TWRP as a recovery instead of return to the stock recovery and I lock the bootloader?
Thanks
sikander3786 said:
Maybe some experts can give their opinion on how to protect your data using some third party apps or by using some other options that I am not aware of. But in my opinion, a phone with an unlocked bootloader is always more vulnerable than a phone with locked bootloader.
Click to expand...
Click to collapse
bartito said:
Of course, I agree with your affirmation at 100%
The question is: I can improve security if I keep TWRP as a recovery instead of return to the stock recovery and I lock the bootloader?
Thanks
Click to expand...
Click to collapse
I don't think you will be able to boot TWRP after relocking the bootloader. You need to test it yourself. Chances are very few because locked bootloaders prevent from booting un-signed images.
If you do manage to boot TWRP after relocking, make sure your data is encrypted. If it is not, then it doesn't matter if the bootloader is locked or not.
Also, you will need to turn off "oem unlock" option from developer options.
sikander3786 said:
I don't think you will be able to boot TWRP after relocking the bootloader. You need to test it yourself. Chances are very few because locked bootloaders prevent from booting un-signed images.
If you do manage to boot TWRP after relocking, make sure your data is encrypted. If it is not, then it doesn't matter if the bootloader is locked or not.
Also, you will need to turn off "oem unlock" option from developer options.
Click to expand...
Click to collapse
I think in the end I will stay as I am: bootloader unlocked and TWRP instead of the original recovery.
After all... I've never lost a phone...
bartito said:
The /sdcard in phones that doesn't have external sdcard, like O+5, are also protected by the encriptation?
Thanks
Click to expand...
Click to collapse
I haven't checked, but I believe it should.
nxss4 said:
Yep, like any other android, the oneplus 5 has full disk encryption enabled by default:
http://www.androidpolice.com/2015/1...ll-disk-encryption-by-default-on-new-devices/
Click to expand...
Click to collapse
Uh no, OP5 with OOS 4.5.x Nougat uses File-Based Encryption (FBE), not FDE.
I know because I wrote the utility to get back to FDE, which works if you change the/fstab* file:
https://forum.xda-developers.com/showthread.php?t=3672477
sikander3786 said:
Well, IMO your concern is right to some extent.
With an unlocked bootloader, if there is some version of TWRP (or any other customer recovery for that matter) that can decrypt your data partition automatically or if you have ever formatted your /data partition from TWRP , or even an insecure kernel (most insecure kernels allow USB debugging without asking for authorization keys), all the thief needs is 2 adb commands and your screen lock will be turned off and all your stuff will be exposed 'as is'.
Click to expand...
Click to collapse
Do you have a source for the first part of that information? The part where if userdata is formatted with TWRP, it is vulnerable?
I don't see how that can happen unless you run decrypted. TWRP is never involved in the encryption process. When you format userdata, it just runs mkfs. Android upon booting sees the forceencrypt flag in the fstab and then promptly encrypt the device with a default passphrase. When you later set up security, the passphrase is changed to whatever you input.
How can TWRP decrypt the files at this point without your passphrase?
Note that if you are running FBE, and run adb shell on a device that's booted into TWRP while waiting for the password, you will be able to see the file structure under /data, but most of its contents will be garbage (=encrypted).
If you're running FDE, and run adb shell on a device that's booted into TWRP, /data will be completely inaccessible.
sikander3786 said:
For educational purposes, the commands are:
Code:
adb shell rm /data/system/*.key
adb reboot
Click to expand...
Click to collapse
This will remove the PIN/password phrase to get into Android, but won't give access to any encrypted files.
That may mess your phone royally as well.
Hello,
Thanks for your anwer. I appreciate the time that have you spend on my question
I need to go to the FDE thread to learn a bit more about the process and results.
Now, I have 2 more questions...
1) If the phone is encrypted with FBE a user can remove user passwords using "adb shell rm /data/system/*.key
&& adb reboot" commands, like @sikander3786 has explained but, due to the device is encripted, it can't access to my data
and the device will require for the decrypt password when booting in normal mode or recovery. I'm correct?
2) If the device is encrypted with FBE a user can access to /sdcard even without the decrypt password in recovery (TWRP) mode but not if encrypted with FDE?
Thanks again!
Fif_ said:
I haven't checked, but I believe it should.
Uh no, OP5 with OOS 4.5.x Nougat uses File-Based Encryption (FBE), not FDE.
I know because I wrote the utility to get back to FDE, which works if you change the/fstab* file:
https://forum.xda-developers.com/showthread.php?t=3672477
Do you have a source for the first part of that information? The part where if userdata is formatted with TWRP, it is vulnerable?
I don't see how that can happen unless you run decrypted. TWRP is never involved in the encryption process. When you format userdata, it just runs mkfs. Android upon booting sees the forceencrypt flag in the fstab and then promptly encrypt the device with a default passphrase. When you later set up security, the passphrase is changed to whatever you input.
How can TWRP decrypt the files at this point without your passphrase?
Note that if you are running FBE, and run adb shell on a device that's booted into TWRP while waiting for the password, you will be able to see the file structure under /data, but most of its contents will be garbage (=encrypted).
If you're running FDE, and run adb shell on a device that's booted into TWRP, /data will be completely inaccessible.
This will remove the PIN/password phrase to get into Android, but won't give access to any encrypted files.
That may mess your phone royally as well.
Click to expand...
Click to collapse
nxss4 said:
I think you'll be fine, as the data on your internal memory should be encypted, which is enabled by default!
Click to expand...
Click to collapse
Suppose i encrypt my device, i.e., it asks for password everytime before booting...
Q1. Will booting into fastboot or recovery require the password?
Q2. If no, how can i prevent access to fastboot and recovery on an unlocked bootloader?
anuragm13 said:
Suppose i encrypt my device, i.e., it asks for password everytime before booting...
Q1. Will booting into fastboot or recovery require the password?
Q2. If no, how can i prevent access to fastboot and recovery on an unlocked bootloader?
Click to expand...
Click to collapse
You can't, but your data isn't accessible without the password
bartito said:
You can't, but your data isn't accessible without the password
Click to expand...
Click to collapse
But one can flash custom recovery from fastboot and subsequently use it to flash custom roms.
Am i right?
anuragm13 said:
But one can flash custom recovery from fastboot and subsequently use it to flash custom roms.
Am i right?
Click to expand...
Click to collapse
Yes, you can flash any recovery and any rom, but phone data can't be accessible if you don't have the password.
To use the device you need to know the password or do a data format
Isn't your phone technically always safe as long as you keep it encrypt it?
Only thing a thief could do would be a reset in both cases, isn't it?
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?