I found following article: "android.stackexchange.com/questions/19286/will-a-custom-recovery-work-with-an-encrypted-device"
According to this description, it should be possible to use the ICS encryption after partitioning the SDcard. Has anyone already tried it?
Article:
"Mount one partition on /sdcard so that it could be used by system & leave other one (Clockwork Mod can do mounting too)."
How can I do this?
Bump
Nobody tried it yet???
i think is better u dont use encryption at all...
if u need encryption for security reason, then u have to stay stock (botloader locked, no root, no cwm, otherwise the encryption has no sense to be done)..in case u want leave the encryption mode, u have to factory reset the phone
clockwork mod is not able to to backup, restore or flash a zip on an encrypted rom (easy to search around to discover this, as i just did now)
Why do you think there are no point with encryption with unlocked bootloader and root?
To me it seems thats when its most important, since its then very easy to get to your data and the only way to protect them?
I am using Titanium Backup and send the backups encrypted to Dropbox, not that much work to wipe and flash ROMS. Kernels you can still flash, at least With Francos app. The only downside is that need a PC to wipe since you have to do it through fastboot.
andQlimax said:
i think is better u dont use encryption at all...
if u need encryption for security reason, then u have to stay stock (botloader locked, no root, no cwm, otherwise the encryption has no sense to be done)..in case u want leave the encryption mode, u have to factory reset the phone
clockwork mod is not able to to backup, restore or flash a zip on an encrypted rom (easy to search around to discover this, as i just did now)
Click to expand...
Click to collapse
B1ny said:
Why do you think there are no point with encryption with unlocked bootloader and root?
To me it seems thats when its most important, since its then very easy to get to your data and the only way to protect them?
Click to expand...
Click to collapse
yes, infact what i mean is that if u want protect more ur data, then stay also with the bootloader locked etc (even if the encryption should be enough)
Have thought about also locking the bootloader since you have to wipe anyways, and need a PC. Will not be much more work/time. But is it really any need?
andQlimax said:
yes, infact what i mean is that if u want protect more ur data, then stay also with the bootloader locked etc (even if the encryption should be enough)
Click to expand...
Click to collapse
if u need encryption for security reason, then u have to stay stock (botloader locked, no root, no cwm, otherwise the encryption has no sense to be done)..in case u want leave the encryption mode, u have to factory reset the phone
Click to expand...
Click to collapse
From my point of view I also think that encryption is very important for rooted devices. If you loose your phone, it's very easy to get your privat data on the sdcard and app-data (acounts,...). With an encrypted device, the data are safe and that's all what I want.
clockwork mod is not able to to backup, restore or flash a zip on an encrypted rom
Click to expand...
Click to collapse
Also if you create a seperate partition - see article in my first post ???
I would also be interested if this was possible.
Reason being - my employer requires that my phone be encrypted and unrooted. I have been investigating a dual boot setup where I could boot my unrooted, encrypted, stock android image so that I can use it for corporate email and when I need root for something like tethering I could boot off the rooted image.
This way my corporate data would be encrypted and I would be adhering to company policy but I can also enjoy the flexibility of a rooted phone when I need it without wiping my phone every time I want to switch back and fourth.
the /cache partition is the answer, i think
I found out that the stock recovery, as expected, also cannot access the /SDcard partition. However, it looks in the /cache partition for update.zip files when the phone is encrypted. I was able to copy the 4.0.4 update to the cache partition and load it from there. Seems like CWM just needs to be updated to have an option to look there for zip files and we should be able to load them up.
chhall said:
I found out that the stock recovery, as expected, also cannot access the /SDcard partition. However, it looks in the /cache partition for update.zip files when the phone is encrypted. I was able to copy the 4.0.4 update to the cache partition and load it from there. Seems like CWM just needs to be updated to have an option to look there for zip files and we should be able to load them up.
Click to expand...
Click to collapse
The problem is /cache is 100 MB, and some (most?) ROMs are way more than that.
So I don't think using /cache is a fix.
I'm not sure of how CWM mounts the external SD card, but if it uses /mnt/sdcard/external_sd then it's impossible to use the external SD card because it depends on the internal SD for the mount point.
If this isn't the case, then it should be possible to partition the external SD card... Is it?
That leaves us with the only possible solution the partitioning of the internal SD card as mentioned in the link provided by OP.
Has anyone done this?
EDIT:
According to CM9's nightlies "know issues" list, encryption has already been solved and is working. I'm wondering how did they fix it.
bump
anybody knows the answer?
ghost shell said:
According to CM9's nightlies "know issues" list, encryption has already been solved and is working.
Click to expand...
Click to collapse
Could you give me a link to this?
There is a work around for flashing in CWM recovery by using the system ram as a temp file system.
You can use the dd command in adb to backup the entire current firmware and restore it in fast boot.
You can also use the backup and restore feature in ics to backup your sdcard contents and some apks.
There is a dev who is working on a full nandroid equivalent on an encrypted system. He is half way there. It requires cm recovery which has dmcrypt support.
http://forum.xda-developers.com/showpost.php?p=25635462&postcount=54
Check out the entire thread for other info for flashing custom roms via system ram.
ghost shell said:
bump
anybody knows the answer?
Click to expand...
Click to collapse
DanderMan said:
Could you give me a link to this?
Click to expand...
Click to collapse
http://teamhacksung.org/wiki/index.php/CyanogenMod9:GT-I9100:Nightly:Known_issues
Encryption used to be on the know issues, but not anymore. I don't know the status for the Nexus.
Also: http://forum.xda-developers.com/showpost.php?p=25515675&postcount=53
@bunklung
Thanks.
I'm still digesting the information.
The sad part is that even a normal factory reset doesn't allow removing encryption. If at least that would be possible it wouldn't be that bad.
EDIT2:
I've been reading and not even the ram trick would work with me because I can't get adbd running in CWM.
adb doesn't detect any device when the phone is in CWM-recovery mode.
Anyone found a way to revert to stock with cwm already installed for an encrypted phone?
Related
First of, to not make everyone dismiss this question...
This is NOT another problem involving missing gapps.
The problem is, no matter what i do (factory reset/clear cache/clear dalvik + remove ANY TRACE of the google apps from the sdcard, and then reboots before installing a basic version of cmod6), i still cant get rid of those damn google apps.
Seems right not that they are installing on their own from absolutely nowhere(!)?
Doesn't matter what i do, have tried to look at every possible scenario from where the cmod flash-process finds, installs, and puts a copy in system/apps-folder without any success at all.
Posted this issue a few days ago, got no answer and then i marked it as solved, but it weren't. Just one single time did i manage to get the flashing to leave a clean copy, but haven't been able to reproduce that since then.
It is car home, gmail, latitude, maps, navigation, places and voice that is stuck in there. Does anyone have any idea of what to do?
Have, except the above, tried to clean out the sdcard completely, plus download+md5check the latest rom...didn't work. Also tried with verification and script assets ON when flashing directly from clockwork, and have tried to flash from rommanager aswell. same results.
Gonna buy a new sdcard tomorrow since im using the stock one which isn't that great (so it needs to be changed sometime anyway), because all i can think of now is if the card itself is bad and clockwork cant read from it properly. Longshot, but im just that badly out of ideas.
Sorry about this wall of text, but that pretty much explains every aspect i tried with no success of removing them. Desperately seeking for help about this now.
You might be able to wipe the system partition completely via fastboot although I don't know if this is a smart thing to do. Than you would be able to do a clean install without Gapps.
You can also try to flash a different rom boot up and then flash cyanogen mod again or you can manually delete the apps from the system partition either with root explorer or with adb while in recovery.
And are you absolutely sure that there are no Gapps in the rom file?
The install script of all CyanogenMods have a backup function for the gapps lol
So also if u wipe all and reflash the rom, the installer backup the gapps, then format system, then install rom and restore gapps..
If u want remove all gapps, just format the /system partition from the clockworkmod recovery (the option its under mounts and storage)..After that, install the rom zip
TheGhost1233 said:
You might be able to wipe the system partition completely via fastboot although I don't know if this is a smart thing to do.
Click to expand...
Click to collapse
'fastboot erase system' is completely safe to do, and a very good idea
andQlimax said:
If u want remove all gapps, just format the /system partition from the clockworkmod recovery (the option its under mounts and storage)..After that, install the rom zip
Click to expand...
Click to collapse
If you want to do this from Amon's recovery (no clear system option), flash the attached update (unsigned).
andQlimax said:
If u want remove all gapps, just format the /system partition from the clockworkmod recovery (the option its under mounts and storage)..After that, install the rom zip
Click to expand...
Click to collapse
Sorry for being such a slow replyer lol, have completed the personalized rom-package and are about to flash it right about now (...or when i got an answer).
First of, before doing it...that answer were really awesome, just curious, there is no way that will brick the base filesystem in any way? In other words, formating /system trough cwork is "completely safe"?
I ofc know things always can go wrong, like the phone bursts into fire or my apartment gets blown away by nuclear war...but it wont mess with anything by default making a restoration towards working state a pain in the lower back?
EDIT: Thought this could make me sound like a damn nervous user, which im not...but the hate i would have at not being able to use my phone during workhours exceeds all measurements known to man. it would get really really boring, not kidding.
I got a problem. I rooted my device, used TWRP in read only mode.(So I still got Stock Recovery)
Now I want to update from 3.1.3 to 3.2.1 but as soon as i want to flash them via TWRP it lists all my files in /, but nothing more. It looks like the internal storage disappeared. It also writes I got 0MB in Internal and USB Storage.
My Phone works fine, no problems at all.
The Folder /sdcard is empty, emulated/0 doesnt exist. Also /data is empty.
How do I fix this?
Adb side load (in stock recovery) the full 3.2.1 zip, wipe cache, fastboot flash twrp and flash root.
Fastboot flash stock recovery again (if you really need it) then boot.
No data will be lost.
In case youre wondering, going forward the stock zip files (ota included) are twrp flash able and don't wipe data. Just make sure to wipe cache after you flash them then re root.
k.s.deviate said:
Adb side load (in stock recovery) the full 3.2.1 zip, wipe cache, fastboot flash twrp and flash root.
Fastboot flash stock recovery again (if you really need it) then boot.
No data will be lost.
In case youre wondering, going forward the stock zip files (ota included) are twrp flash able and don't wipe data. Just make sure to wipe cache after you flash them then re root.
Click to expand...
Click to collapse
1.I have to use the Full 3.2.1 Zip (1.2 GB) right?
2.does this fix my sdcard problem? because if not im not gonna be able to reroot the phone...
thanks for the reply
Psy0ch said:
1.I have to use the Full 3.2.1 Zip (1.2 GB) right?
2.does this fix my sdcard problem? because if not im not gonna be able to reroot the phone...
thanks for the reply
Click to expand...
Click to collapse
Unless you formatted the device, I don't think you have a problem. I think twrp was not able to mount the internal storage the way you were using it. You should use a PC in case there are problems.
Edit: Yes full zip. You "might" be able to use the ota zip but if you already have the full zip just use that.
k.s.deviate said:
Unless you formatted the device, I don't think you have a problem. I think twrp was not able to mount the internal storage the way you were using it. You should use a PC in case there are problems.
Edit: Yes full zip. You "might" be able to use the ota zip but if you already have the full zip just use that.
Click to expand...
Click to collapse
Ok thanks! I got the update now on my device
But now I still have to problem of "How to root."
I cant access the zip...
Psy0ch said:
Ok thanks! I got the update now on my device
But now I still have to problem of "How to root."
I cant access the zip...
Click to expand...
Click to collapse
Have you flashed twrp and allowed it to modify the system? I think that's why you are not seeing internal storage. I could be wrong tho...
k.s.deviate said:
Have you flashed twrp and allowed it to modify the system? I think that's why you are not seeing internal storage. I could be wrong tho...
Click to expand...
Click to collapse
i kept it read only. did it once and then it worked too... should i flash twrp onto it?
Psy0ch said:
i kept it read only. did it once and then it worked too... should i flash twrp onto it?
Click to expand...
Click to collapse
I think so yes, that's what I did. You can always reflash the stock recovery if you want. But there is really no reason.
k.s.deviate said:
I think so yes, that's what I did. You can always reflash the stock recovery if you want. But there is really no reason.
Click to expand...
Click to collapse
Thanks alot man! Worked perfectly
Psy0ch said:
Thanks alot man! Worked perfectly
Click to expand...
Click to collapse
No worries, just thank the posts
Psy0ch said:
I got a problem. I rooted my device, used TWRP in read only mode.(So I still got Stock Recovery)
Now I want to update from 3.1.3 to 3.2.1 but as soon as i want to flash them via TWRP it lists all my files in /, but nothing more. It looks like the internal storage disappeared. It also writes I got 0MB in Internal and USB Storage.
My Phone works fine, no problems at all.
The Folder /sdcard is empty, emulated/0 doesnt exist. Also /data is empty.
How do I fix this?
Click to expand...
Click to collapse
Use the official twrp from their website. Even the unofficial ones fixed that bug now but we have official so you can easily backup EFS too
I know on most devices I've owned you needed a non-encrypted kernel and I had to perform a format of data to remove encryption. I have seen a few posts in a couple of other threads but nothing I saw was definitive. Does anyone know if unencrypting the XL is even possible? If so, which kernel are you using?
I also have the same question, I just want descrpt data partition to avoid risk when I turn to TWRP and MultiROM in future,
So anyone try this? I can not understand why I need Magisk here??
http://androiding.how/disable-verity-force-encryption-pixel-xl-decrypt/
Mike02z said:
I know on most devices I've owned you needed a non-encrypted kernel and I had to perform a format of data to remove encryption. I have seen a few posts in a couple of other threads but nothing I saw was definitive. Does anyone know if unencrypting the XL is even possible? If so, which kernel are you using?
Click to expand...
Click to collapse
Azlun said:
I also have the same question, I just want descrpt data partition to avoid risk when I turn to TWRP and MultiROM in future,
So anyone try this? I can not understand why I need Magisk here??
http://androiding.how/disable-verity-force-encryption-pixel-xl-decrypt/
Click to expand...
Click to collapse
Notice in the attached that it states that TWRP plus SuperSU decrypts file based encryption.... https://www.xda-developers.com/supersu-updated-to-work-with-twrp-on-pixel-and-pixelxl/
cam30era said:
Notice in the attached that it states that TWRP plus SuperSU decrypts file based encryption.... https://www.xda-developers.com/supersu-updated-to-work-with-twrp-on-pixel-and-pixelxl/
Click to expand...
Click to collapse
" Dees_Troy to allow TWRP to decrypt the data partition involves modifying the same init binary " is NOT what I want according developer's
https://plus.google.com/+DeesTroy Pixel update 4 picture.
What I want is need the full device decryption permanently, on Anroid running time, not only on TWRP.
so, I think that is maybe more than TWRP can do, I guess a special boot.img or a kernel patch zip is need to reach what I need.
Mike02z said:
I know on most devices I've owned you needed a non-encrypted kernel and I had to perform a format of data to remove encryption. I have seen a few posts in a couple of other threads but nothing I saw was definitive. Does anyone know if unencrypting the XL is even possible? If so, which kernel are you using?
Click to expand...
Click to collapse
Decrypting your pixel is possible. The process isn't much different than any previous Nexus. It differs due to the removal of the recovery partition thus the recovery fstab is now in the kernels ramdisk. So you must edit out forecencryption in both fstabs. (fstab.marlin,fstab.recovery).
Fastboot format userdata, flash a modified kernel, done..
Haven't seen any custom kernels that remove the flag yet so I modified ElementalX.
http://forum.xda-developers.com/pix...oem-unlock-t3498287/post69733387#post69733387
blueyes said:
Decrypting your pixel is possible. The process isn't much different than any previous Nexus. It differs due to the removal of the recovery partition thus the recovery fstab is now in the kernels ramdisk. So you must edit out forecencryption in both fstabs. (fstab.marlin,fstab.recovery).
Fastboot format userdata, flash a modified kernel, done..
Haven't seen any custom kernels that remove the flag yet so I modified ElementalX.
http://forum.xda-developers.com/pix...oem-unlock-t3498287/post69733387#post69733387
Click to expand...
Click to collapse
I did use your modified Elemental kernel that was in the thread about the ability to show that your bootloader is unlocked.
Here is what I did...
Went into TWRP and did a format data from the wipe menu.
Flashed your kernel via USB SD dongle.
Rebooted.
Took about 5-8 minutes to boot but when I went into "Security" it still showed my phone was encrypted. I did this with every Nexus device I've owned but not sure what I'm doing wrong.
Mike02z said:
I did use your modified Elemental kernel that was in the thread about the ability to show that your bootloader is unlocked.
Here is what I did...
Went into TWRP and did a format data from the wipe menu.
Flashed your kernel via USB SD dongle.
Rebooted.
Took about 5-8 minutes to boot but when I went into "Security" it still showed my phone was encrypted. I did this with every Nexus device I've owned but not sure what I'm doing wrong.
Click to expand...
Click to collapse
Don't you need to format user data with fast boot to decrypt?
Sent from my Google Pixel XL using XDA Labs
I've been using the forums for a while but this is the first time I post on here, so I'm not so sure if I'm posting this in the right place. But I need any help I can get at this point.
So a while ago I unlocked and rooted my Moto Z Play by flashing TWRP recovery with the fastboot ADB tools. Things were fine, but then I accidentally let the phone do an automatic OTA update. When the phone was going to boot, it went straight to TWRP recovery and after I input my unlock pattern, it gave me a couple lines of text. In these lines was a red line of text saying "Unable to mount storage" and then it would go to the recovery menu. It won't boot past the recovery anymore.
I looked it up but I can't seem to find clear answers anywhere, as many that I have found have their storage indicating that they have "0mb" when they go to backup. I don't have that problem as all my storage is present and even MTP is enabled. Hopefully someone can help me out here anyway possible.
You can not install OTA updates on ROOTED phone with TWRP recovery.
For working OTA you must have stock recovery and NO ROOT.
If you have XT 1635-02 version, you can reflash your phone using this RSD LITE unbrick tool https://forum.xda-developers.com/ge...orola-usb-drivers-rsd-lite-firmware-t3042687- and you can try to use this firmware for Moto Z Play : https://androidfilehost.com/?fid=673791459329058517
Your phone data will be deteled.
Ax1qwer said:
Your phone data will be deteled.
Click to expand...
Click to collapse
This sounds a bit too hard for me. Usually it is sufficient to flash a firmware with a similar version like you currently have installed, omitting "erase userdata", meaning you do a dirty flash keeping the data.
Alternative, if you want to keep data but erase the phone installing a firmware, you may do backup in twrp and restore data after the phone runs. But keep in mind that a) there were some problems restoring Nandroid backups on Z Play and b) /data/media must be treated separately, which usually is the data you want to keep (mainly: photos and videos you made). You need to enter your phone pin to decrypt data to mount it, maybe that is the missing step.
If you cannot receive OTA updates on a phone with custom recovery, even after (say) restoring a full TWRP System Image backup. . . doesn't that imply, in practice, that you cannot ever return to a stock experience?
I have a stock Z Play with the latest 7.1.1 updates. If I decide to unlock and install LineageOS, there is no way to get back to stock? ever? I mean, I knew about the warranty, that safetynet won't pass, and that I can't re-lock the bootloader. I'm fine with all that. But I thought I could at least get back to the stock ROM, and continue to receive OTA updates. Instead, it sounds like running my backup would be hell: the phone would constantly nag me to install OTA updates, yet if I ever slipped up and said "yes" it would be bricked.
Is there no way to back up the original recovery partition too, so that you can make the OTA updater happy?
mark04 said:
Is there no way to back up the original recovery partition too, so that you can make the OTA updater happy?
Click to expand...
Click to collapse
The are several easy possibilities.
You can get some firmware which you install using fastboot flash. You may decide to only flash stock recovery. For a successful update you need to have system, boot, recovery, logo, oem (from memory, hope I got this right) in exactly the same version.
You can use fastboot boot to start recovery. Then you should be able to restore your recovery backup.
My usual way: if you have stock, never install twrp. Always boot it when needed using fastboot boot. Then you don't need to care about recovery when updating.
If an update does not work, your always can decide to install a full stock ROM, if you omit the command "erase userdata", your data usually survives fine. No guarantee of course, always do a backup. Don't forget data/media where personal things are stored and never covered by Nandroid backup of twrp.
tag68 said:
My usual way: if you have stock, never install twrp. Always boot it when needed using fastboot boot. Then you don't need to care about recovery when updating.
Click to expand...
Click to collapse
Aha---great suggestion, thanks! I would never have thought of that, even though I had to do it on another device once where the bootloader kept overwriting the recovery.
tag68 said:
If an update does not work, your always can decide to install a full stock ROM, if you omit the command "erase userdata", your data usually survives fine. No guarantee of course, always do a backup. Don't forget data/media where personal things are stored and never covered by Nandroid backup of twrp.
Click to expand...
Click to collapse
I was just reading up on how to wipe and install a full stock ROM (factory image). It seems reasonably straightforward, IF you can find the correct image. This worries me a little, because my device is RETUS and there aren't many of those images floating around. None on lolinet.com for example. Some people say to use a RETAIL image but does anyone actually understand how they are different, and what the repercussions might be?
mark04 said:
... and there aren't many of those images floating around. None on lolinet.com for example.
Click to expand...
Click to collapse
You may have a look at firmware.center. They have a lot, but I'm not sure if all are working fine. You may need to do a backup and try. But you nowhere get the safety it's right, because Lenorola does not release signed versions (which would also allow relocking).
Note: For me all the firmwares from there worked by now.
mark04 said:
Some people say to use a RETAIL image but does anyone actually understand how they are different, and what the repercussions might be?
Click to expand...
Click to collapse
Changing update channel is said to be possible, but I never tried it. If you really want it you may try searching a bit in xda forums of similar but older phones how experiences with this are.
Good Afternoon.
A question for you guys, every time i try to wipe my current rom and flash another custom rom, or an update to the current rom on my begonia (with cfw installed), my damn internal storage gets encrypted, so ive got no choice but to format it, or else i can't access it, which is a major pain...
Do you guys know of a way to prevent this??
I'm running twrp recovery with cfw support.
And am pretty sure i'm not f-ing up with the rom installation instructions...
Jollld said:
Good Afternoon.
A question for you guys, every time i try to wipe my current rom and flash another custom rom, or an update to the current rom on my begonia (with cfw installed), my damn internal storage gets encrypted, so ive got no choice but to format it, or else i can't access it, which is a major pain...
Do you guys know of a way to prevent this??
I'm running twrp recovery with cfw support.
And am pretty sure i'm not f-ing up with the rom installation instructions...
Click to expand...
Click to collapse
Hi, If you setup the lockscreen on your ROM you will encrypt the internal storage and TWRP will ask you the password to decrypt it.
If u remove the lockscreen before entering recovery you won't have to decrypt the internal storage.
Thanks but some kind souls on discord helped me out, using a disable encryption zip fixed it.
Jollld said:
Thanks but some kind souls on discord helped me out, using a disable encryption zip fixed it.
Click to expand...
Click to collapse
Any chance for sharing it here? Thank you
porotikos said:
Any chance for sharing it here? Thank you
Click to expand...
Click to collapse
Install this then format data.
Also if you flash a new ROM you'll have to install this again.
Canny1913 said:
Install this then format data.
Also if you flash a new ROM you'll have to install this again.
Click to expand...
Click to collapse
oh my god i fecked up.
i installed this via twrp and didnt format. (i dont want to lose data).
Now the phone doesnt boot. it gets stuck in miui logo.
is there a way to go to twrp and revert the changes?
porotikos said:
oh my god i fecked up.
i installed this via twrp and didnt format. (i dont want to lose data).
Now the phone doesnt boot. it gets stuck in miui logo.
is there a way to go to twrp and revert the changes?
Click to expand...
Click to collapse
Can you tell me the ROM version? So i can try to give you some files and instructions for fixing it.
Canny1913 said:
Can you tell me the ROM version? So i can try to give you some files and instructions for fixing it.
Click to expand...
Click to collapse
On second thought, just reflash the ROM. (without wiping data of course) it should fix it.
Canny1913 said:
On second thought, just reflash the ROM. (without wiping data of course) it should fix it.
Click to expand...
Click to collapse
worked. thanks
Canny1913 said:
On second thought, just reflash the ROM. (without wiping data of course) it should fix it.
Click to expand...
Click to collapse
i have managed to turn on the phone. my internal storage isnt wiped. just the data. so i am setting up my accounts etc.
i can see tha tmy inernal storage that is used, is 215 gb. so my data is there. but they are not accessible. because they seem to be decryptewd from the module i guess.
is there any way i can get back my data so that i can back up, and then i can hard format the phone?
when i open the files appliucation, it doesnt even show my internal folders. nothing.
this is really strange
porotikos said:
i have managed to turn on the phone. my internal storage isnt wiped. just the data. so i am setting up my accounts etc.
i can see tha tmy inernal storage that is used, is 215 gb. so my data is there. but they are not accessible. because they seem to be decryptewd from the module i guess.
is there any way i can get back my data so that i can back up, and then i can hard format the phone?
when i open the files appliucation, it doesnt even show my internal folders. nothing.
this is really strange
Click to expand...
Click to collapse
In TWRP, mount Data and using the in-built File Manager, check inside /data/media/0 (this is where your Internal Storage is located)
Is your password intact btw?
Canny1913 said:
In TWRP, mount Data and using the in-built File Manager, check inside /data/media/0 (this is where your Internal Storage is located)
Is your password intact btw?
Click to expand...
Click to collapse
data kept showing encrypted. just did a hard format. thanks for your help anyway
porotikos said:
data kept showing encrypted. just did a hard format. thanks for your help anyway
Click to expand...
Click to collapse
This is why i hate android's "security"