Hello guys!
Well, it looks like official TWRP (latest version) doesn't work for me as I use f2fs. I used a bsmitty build that worked like a charm but then updated to a more recent Ziyan build. I've noticed that the phone is giving error codes when I try to flash data or internal storage (so... the data partition) and I want to go back to a TWRP that doesn't have those kinds of problems. Especially because nowadays I try to erase everything apart from internal storage so I check all the boxes exept internal storage but it deletes internal storage too, it's annoying.
Does anyone have a older build or a new build without those problems and with f2fs support? I would appreciate if you share it with me :highfive:
Related
Flashed slimbean via freegee/cwm. All works fine however, the available memory shows ~20GB with a total of 23GB. The 23GB is the same as what was available with the stock firmware.
Should I have increased my memory due to slimbean being much smaller than the stock?
Or is this a case of the locked bootloader and the original rom still taking up its own space and I just boot into slimbean due to loki, thus I only have the 23GB to work with to put a ROM on and apps, etc.?
Thanks.
think I figured out the issue. . .
To answer my own question, possibly. I need to format system in cwm if I want the old ROM gone, but is that ok to do on the OGP?
formating system + works
after more reading, for anyone else who is curious, I found that formatting some of the partitions is required. If you are on stock and don't format anything and install a new rom, that rom will be put in a new folder which will take away ~3GB of space. After formatting a few of the partitions the new ROM installed properly and I have back the 23.3GB of space.
Hi XDA colleagues,
I am writing this post because I have installed Marshmallow GPE ROM on my M8 and I would like to install the Sense 7 HTC A9 Camera and gallery.
As I have selected my sdcard as Internal Memory, I can't find anymore it under TWRP (2.8.7.0).
And I have see that the /system partition is only 22MB free.
Previously I had a Sense ROM and I don't have used the GPE RUU so my /system partition should not have been resized?
Someone is knowing how is the behavior of TWRP with MM? or maybe a new version is needed?
Many thanks in advance!
Seriously? No reply? Well I'm in the same boat as you, except I have a Moto X pure 2015
Hello,
I have found more details here:
https://www.reddit.com/r/Android/comments/3oz7eu/guidelines_for_marshmallow_users_formatting/
So, formatting SDCard as Internal Memory will crypt it and TWRP will not be able to read it anymore.
You have to rollback to External Memory to gain access again (do a backup of the content before).
Starting with version 3.0.0-0, TWRP has gained the ability to decrypt and mount SD cards that have been migrated to Internal storage under Marshmallow. Of course, the SD card has to be inserted in the device where it was originally encrypted, and I strongly suspect that you would lose the decryption keys if you ever wipe the device.
Your mileage may vary, because there may be some individual devices for which the feature doesn't work perfectly yet. But I can confirm that it appears to work as expected with TWRP 3.0.2-0 on my Galaxy S4.
Hopefully someone else has experienced something similar to this and can offer help....
I just successfully rooted/bootloader unlocked/flashed new ROM to my SM-T700. The ROM that I found that works is a "vanilla" version of AOSP (aosp-eng.ubuntu.20160805.143038). I love both having my device rooted and running Marshmallow. I was also able to format a 32GB SDCard as "adoptable storage," which is terrific -- I love having so much space.
After awhile, I decided to be adventurous and try a couple other ROMS including a custom Cyanogenmod and Resurrection Remix. I liked both of these better than the AOSP, but for some reason, when running these ROMs, my phone cannot format an SDCard as internal ("adoptable") storage. The process crashes, and in once case, it actually destroyed a 64GB SDCard that now cannot be formatted on any device.
My question -- if I format an SDCard as internal storage under AOSP, and then flash to Resurrection Remix, for example, will the new ROM be able to use the space created by the previous one? Will I keep the apps I have installed and be able to continue to use all the extra storage space?
Thanks!
CAaronL said:
Hopefully someone else has experienced something similar to this and can offer help....
I just successfully rooted/bootloader unlocked/flashed new ROM to my SM-T700. The ROM that I found that works is a "vanilla" version of AOSP (aosp-eng.ubuntu.20160805.143038). I love both having my device rooted and running Marshmallow. I was also able to format a 32GB SDCard as "adoptable storage," which is terrific -- I love having so much space.
After awhile, I decided to be adventurous and try a couple other ROMS including a custom Cyanogenmod and Resurrection Remix. I liked both of these better than the AOSP, but for some reason, when running these ROMs, my phone cannot format an SDCard as internal ("adoptable") storage. The process crashes, and in once case, it actually destroyed a 64GB SDCard that now cannot be formatted on any device.
My question -- if I format an SDCard as internal storage under AOSP, and then flash to Resurrection Remix, for example, will the new ROM be able to use the space created by the previous one? Will I keep the apps I have installed and be able to continue to use all the extra storage space?
Thanks!
Click to expand...
Click to collapse
No. Because if you use your sdcard as adoptive storage. It will encrypt the data and will not be able to work if you wipe (data partition) and in many cases you need clean flash to install new rom. That mean you are going to format SYSTEM, DATA AND CACHE partitions because of that you need to move all your data back to internal storage and install new rom and then make adoptive storage again. You can't use it continously crossed the roms.
Sent from my SM-T815 using Tapatalk
Is there a chance I can change ROMs without wiping? And any idea why adoptable storage would work fine on AOSP but not on the Cyanogen-based ones?
CAaronL said:
Is there a chance I can change ROMs without wiping?
Click to expand...
Click to collapse
No, you can't because when you use adoptive storage that mean part of your system Apps data will move there, that mean you already have old system apps (Adoptive storage) and you want to install new system apps . And it depends on if apps are matching on both roms but this doesn't happen in most of the time.
CAaronL said:
And any idea why adoptable storage would work fine on AOSP but not on the Cyanogen-based ones?
Click to expand...
Click to collapse
I don't know maybe there is anyone here can answer your question or try to ask the dev who works on the CM based rom.
Sent from my SM-T815 using Tapatalk
CAaronL said:
Is there a chance I can change ROMs without wiping? And any idea why adoptable storage would work fine on AOSP but not on the Cyanogen-based ones?
Click to expand...
Click to collapse
Try the adoptable storage patch.
Hi,
I don't know why my phone only has 94MB of storage available. My phone was on CrDroid 6.0.1 before I tried to flash LineageOS 16.0 with TWRP 3.3.0 and somehow got messing up. After I flashed the room and booted the system, I found that my storage only has 94MB to install any apps on it. What's really strange is that it showed 16GB internal storage, but I cannot use it. I can use only 94MB from sdcard and this is what became weirder. I didn't put any sdcard on this phone and somehow it shows on my storage. How can I solve this problem?
Currently, the phone is on CrDroid 7.1.2 with TWRP 2.8.7.2
spiritfire said:
Hi,
I don't know why my phone only has 94MB of storage available. My phone was on CrDroid 6.0.1 before I tried to flash LineageOS 16.0 with TWRP 3.3.0 and somehow got messing up. After I flashed the room and booted the system, I found that my storage only has 94MB to install any apps on it. What's really strange is that it showed 16GB internal storage, but I cannot use it. I can use only 94MB from sdcard and this is what became weirder. I didn't put any sdcard on this phone and somehow it shows on my storage. How can I solve this problem?
Currently, the phone is on CrDroid 7.1.2 with TWRP 2.8.7.2
Click to expand...
Click to collapse
You should follow the steps here to unify the storage: https://forum.xda-developers.com/find-7/general/how-to-guide-8-1-android-lvm-chinese-t3783168
If you didn't know, the Find 7 has a weird thing where they have partitions and only allow ~3gb of app storage unless you unify the storage.
XoticPhones said:
You should follow the steps here to unify the storage: https://forum.xda-developers.com/find-7/general/how-to-guide-8-1-android-lvm-chinese-t3783168
If you didn't know, the Find 7 has a weird thing where they have partitions and only allow ~3gb of app storage unless you unify the storage.
Click to expand...
Click to collapse
Thank you. I will try to do as you told and update the feedback asap.
So i recently wanted to use my old Samsung A5 2016 and flashed LOS on it. There are not official ones so i toke one randomly from the internet (LOS 17.1). It worked fine but one app required google so i flashed GApps on it, but this also doesn't worked so i wanted to remove the GApps with a backup but i forgot to make one so i just installed a new version of LOS but now stuff like camera and storage doesn't work anymore.
I tried
- LOS17.1
- LOS 18.1
- LOS 19.1
I think its because i accidentally wiped the internal storage in TWRP and now it doesn't have the specific folder and stuff anymore.
I hope someone knows how to fix it
So i fixed it
https://appuals.com/how-to-fix-twrp-unable-to-mount-storage-internal-storage-0mb/
I reformatted the file system to Ext2 and then back to Ext4