Hi, my device is running a CM10.1 nightly. After encrypting it, TWRP 2.4.2.0 is not able to decrypt the /data partition when I enter the password. So I updated to 2.5.0.0 using the Goo Manager thinking it will fix this issue. 2.5.0.0 seems to accept the password but burps a" 'unable to mount /data' message when I try to access data storage. TWRP seems to see /data as the entire size of the internal storage too. Then I flashed 2.5.0.0 with ODIN, to exclude any problems related to local installation, and still the same issue is there. From what i read TWRP should support encryption, these bugs show that there are serious issues, how would I go about reporting that to them? Also is there a way I can resolve this without tearing down this setup?
Another issue is that my file manager cannot access my /data partiton any longer. Everytime it comes up it hangs and crashes without showing any directories. Maybe this issue would go away with a firmware update but I can't get that going because of the issue above.
you can also try CWM touch recovery if that doesn't work. just flash it from odin and install another custom rom. good luck.
-------------------------------------
please let me know if i'm wrong and CLICK thanks if i help
SRIRAM
sent from my GT-I9300 running CM10.1 RC4.4 by Temasek
Do you have a similar setup to mine I want to confirm that this is a general bug rather than an issue with mine specifically. If you are anyone else let me know I'd appreciate it. From what I have researched CWM does not support encryption so it would be a non-starter.
Related
Somehow I managed to really mess something up.
The other day my TWRP was working just fine, I was doing some fiddling and backing up and everything was working fine.
Then I encrypted my device.
Now TWRP cannot mount /data or any internal storage and talks about being unable to find /TWRP/.twrp
I've been reading a few threads where other people have been able to fix this but none of them seem to apply or work in this situation.
If anyone has a stock 4.4.3 ATT Desire 610 kernel, rom, and especially a stock recovery I would be forever grateful. I've tried reinstalling different versions of TWRP using fastboot/adb which didn't help. I've tried to advance wipe the data partition, which didn't work. The only thing I haven't done is format because I haven't got an OS to replace it yet. I tried to use the TWRP repair disk function on /data, that too did not work. I'm not sure what else I can try.
HTC says they cannot send me those things and that the only thing I can do is send them my phone for 10 days.
Right now it will still boot into stock 4.4.3 and everything works but I cannot initiate a factory reset from there as it simply calls open TWRP and I'm back to the same problem.
Please if anyone has any advice, I'm all ears. I'm comfortable with the terminal and am a linux guy so I can understand various different aspects of the Android operating system.
Thanks in advance for the help here, I'm really in a bind.
I own an i9500 (Galaxy S IV). Recently, it dropped. I was lucky enough to install RomSwitcher (a multi-boot app) on it before, so I could still access an Android version.
However, in order to fix the problem, I decided to format the whole device. That didn't work out, and now I'm always stuck on bootloader screen( if it boots at all) and data partitions give I/O errors in recovery.
Now I would be glad if I could install another ROM on my sdcard, probably that'll have to go via RomSwitcher(http://forum.xda-developers.com/showthread.php?t=2417600). I would be glad if someone could send me the kernel and recovery images.
Kind Regards,
Richard Fennigan
p.s. Logcats give the issue of Constantly being in wakelock because of the GPS.
bump
bump
Hi,
I have an unlocked bootloader on the XT1521, with TWRP and Cyanogenmod 13.0 installed. I just updated CM via OTG, which worked correctly, but all Google Apps were removed. When I tried to flash them afterwards, nothing happened.
So I went on and wanted to wipe /system to reinstall CM and GAppsbut apparently, my /system partition is "busy" and cannot be unmounted. I get this error all the time, regardless if I try to a) uncheck the "mount system partition read-only" and swipe to allow modifications, b) try to unmount it manually via the mount menu, c) try to wipe it (the "repair" option is not available for \system unlike for /data, e.g.), d) try to flash CM13.0 zip. The error message is always like "failed to unmount '/system' (Device or resource busy)" and, oddly, I did not find any similar issue via Google, as it is not just a "read-only"-related problem.
Does anybody have a solution to that issue? Thanks!
Alex
alexounet2 said:
Hi,
I have an unlocked bootloader on the XT1521, with TWRP and Cyanogenmod 13.0 installed. I just updated CM via OTG, which worked correctly, but all Google Apps were removed. When I tried to flash them afterwards, nothing happened.
So I went on and wanted to wipe /system to reinstall CM and GAppsbut apparently, my /system partition is "busy" and cannot be unmounted. I get this error all the time, regardless if I try to a) uncheck the "mount system partition read-only" and swipe to allow modifications, b) try to unmount it manually via the mount menu, c) try to wipe it (the "repair" option is not available for \system unlike for /data, e.g.), d) try to flash CM13.0 zip. The error message is always like "failed to unmount '/system' (Device or resource busy)" and, oddly, I did not find any similar issue via Google, as it is not just a "read-only"-related problem.
Does anybody have a solution to that issue? Thanks!
Alex
Click to expand...
Click to collapse
Hey i had this issue and finally pinned it down to the TWRP I was using. It turns Official TWRP has this issue. This can easily be resolved if u flash Squid's TWRP
Download the latest version from here:
http://forum.xda-developers.com/devdb/project/?id=10398#downloads
That was the problem apparently. Thank you!
Thank you! I was having this problem as well and that fixed it.
Thanks very much for your help!!!
I was scared of loosing my phone...
Thanks.
I have a US Cellular XT1526 and was unable to install GApps on CM13 without this. CM13 installed fine, and GApps looked like it installed, but on reboot nothing was there; GApps failed to install. Using Squid's TWRP fixed it; thanks!
ayush rao said:
hey i had this issue and finally pinned it down to the twrp i was using. It turns official twrp has this issue. This can easily be resolved if u flash squid's twrp
download the latest version from here:
http://forum.xda-developers.com/devdb/project/?id=10398#downloads
Click to expand...
Click to collapse
thank you so much :d
thank you buddy.....
my mother is using Motorola E 2nd gen LTE and i flashed it with cyanogenmod 13 used officialTWRP recovery... and i faced the same problem. thank you very much for your answer and also the other guy for asking the question.
Should I select boot or recovery as partition when flashing this img
cannot restore system mounted read only
My bootloader is unlocked and Twrp is installed. I flashed CM13 but was having issues with root so I ran "adb shell reboot disemmcwp" that made Adaway work but Titanium backup still would not uninstall system apps. Twrp says it can't dycrypt data and I am unable to move my TWRP backup off the device. I've formatted everything. I don't entirely understand the encryption, if I need encryption? Should I be having errors in Twrp or be able to mount system? I don't know if I did something wrong and what to do to fix it? I was hoping to figure this out before reflashing cm13.
mod please move to questions, sry
Not sure if this will fix your problem but I had the encryption issue when I flashed CM. When I set up my pin I unknowingly chose ask for pin when starting device. So TWRP asked for a password to decrypt. My pin did work in TWRP. I fixed it in the security settings. Does TWRP ask for a password?
Fixed it. I had choose a pin setting up CM. The fix for me was to hit cancel in Twrp when it asked for a pinand then format the data.
After the latest magisk update 20.0, twrp (3.3.1-0) asks to Swipe to allow modification or keep read only. I always choose swipe to allow modification as that's what you primarily install twrp for, but even after doing so twrp fails to read my internal memory. Before this magisk update it didn't ever ask me this, except for the first time i installed twrp. Just shows 0MB and fails to mount storage for backing up or repair (Repair file system gives an error code 8).
Now the thing is that everything was working perfectly fine until this latest magisk update. Rom works fine (Havoc OS v2. 5), magisk works fine, root works fine, phone is encrypted just as it was before, everything is fine except twrp and i really need twrp to keep working as it was before.
Now yes, I have removed pin/password and tried to make twrp work, switched from pattern to pin as some solutions out there say that twrp will ask for the pin on boot up and on entering the correct pin it will decrypt the internal storage and all will be fine. But no, it didn't work.
Whatever it is am damn sure its magisk. Rom is the same, kernel is what came with the rom, no magisk modules installed, infact I run magisk in core mode only (yes I have disabled core mode only to see if it fixes the problem). I have attached a screen shot of magisk home screen and you can see that under the advanced settings Force encryption is enabled (just like it was enabled while installing magisk for the first time, I have never messed with those settings) and the other two are disabled. Do i need to check that recovery mode? Whatever the solution is, it is preferable that I don't loose my rom and data. But if there's a 100% working solution which involves wiping everything then please mention that too.
Also some solutions need you to change the file format of the internal storage, and I am a little afraid to try that.
Sorry for the extra long post, Thanks in advance.
ronish.x said:
After the latest magisk update 20.0, twrp (3.3.1-0) asks to Swipe to allow modification or keep read only. I always choose swipe to allow modification as that's what you primarily install twrp for, but even after doing so twrp fails to read my internal memory. Before this magisk update it didn't ever ask me this, except for the first time i installed twrp. Just shows 0MB and fails to mount storage for backing up or repair (Repair file system gives an error code 8)....
Click to expand...
Click to collapse
Check your TWRP logs. They will contain clues as to what might be the problem. Then post the logs in your TWRP forum. You can get the logs via adb
Code:
adb pull /tmp/recovery.log
adb pull /tmp/dmesg.log
Did you try changing the storage type? That helped me once. Also what helped was using the latest or an older version of twrp, you can also try doing this. Let me know what happens.
Soojikahalwa said:
Did you try changing the storage type? That helped me once. Also what helped was using the latest or an older version of twrp, you can also try doing this. Let me know what happens.
Click to expand...
Click to collapse
Changing the storage type would be safer or flashing the same version of twrp on top of it (as I have the latest one) or an older version would be better? I will use the official twrp app for the later.
ronish.x said:
Changing the storage type would be safer or flashing the same version of twrp on top of it (as I have the latest one) or an older version would be better? I will use the official twrp app for the later.
Click to expand...
Click to collapse
Try using an older version of twrp first. Changing storage type for system or data might lead to data lose. Make a backup in any case.