Database Info

[Q] Corrupted internal storage

ill keep this simple. tried to advanced wipe data and cache with TWRP which returned an E:/ unable to mount for both data and cache. internal storage is now saying its 0MB after i "fastboot erase" on as many of the partitions it would return success with (ie, what was mounted) flashall is asking me for a specific device.
How do i reset the internal partitions so they become mountable again? i believe in erasing the ones i had, it has deleted them altogether and i need to flash original firmware to get it to auto restructure (im guessing)
EDIT: so i downloaded this (link not allowed) i just dont know how to implement it through adb or fastboot
somewhere i read that the latest moto PQ versions for CWM and TWRP both have some selinux problem when wiping data, causing a force unmount (parroting. i DONT know what im talking about)
the first time i installed with CM11 with twrp (after CMW only allowing me to install 10.2) it worked great, except google play and whisperpush(whatever that is) crashing consistently. i should have used 'fix permissions' instead of going for a wipe+re-install
please help, what commands do i need to use through fastboot to restore the partitions, or where can i get the fxz file to use with RSD?
this is a brand new out of the box Sim-modded and pre-rooted PQ

SOLVED (i think)
god im so ****ing stupid.
due to corrupting the file structure and not being able to mount the cache or data partitions, when i installed CM11 snapshot it picked my external SD as the data storage /android/data/
FIX: unmounting and removing the external SD i rebooted to system, booted back to recovery. -> factory reset.... auto reboot, cant mount messages, then a second time it said SELinux supported message. ->factory reset again and finally no red messages, wipe to system (got an error, but probably cause system = external SD). i then inserted the external SD, installed the ROM and everything looks normal and working right
TWRP will restore file structure with 'factory reset' BUT ONLY IF you remove your external sd
i hope this thread saves time and headaches for someone.

Disable encryption protection?

Hi Guys
Im having trouble flashing new Roms to my S7. When I enter TWRP recovery, it shows my device as 0MB and it doesnt picK up any files. I looked into this and read that Encryption should be disabled on the handset. I followed instructions to do this and noticed that there is no option for Encryption Protection. Its not there!
I disabled any passwords and Pin numbers to erase decryption and it still didnt work!
last resort was to try a factory reset and the device restarted to recovery and failed as TWRP recovery cant find any mounted devices due to the encryption crap.
Any help appreciated.
Chris

scientificharmony said:
Hi Guys
Im having trouble flashing new Roms to my S7. When I enter TWRP recovery, it shows my device as 0MB and it doesnt picK up any files. I looked into this and read that Encryption should be disabled on the handset. I followed instructions to do this and noticed that there is no option for Encryption Protection. Its not there!
I disabled any passwords and Pin numbers to erase decryption and it still didnt work!
last resort was to try a factory reset and the device restarted to recovery and failed as TWRP recovery cant find any mounted devices due to the encryption crap.
Any help appreciated.
Chris
Click to expand...
Click to collapse
Hi mate
Seems like you did not format your data partition during TWRP installation.........
Try flashing your custom rom from the External SD card......your data partition has all your app , files , passwords, photos...there is still a chance that there it may be a incompatibility issue between your apps and the new rom....that is why they recommend a factory reset when flashing a new custom rom

MAX 404 said:
Hi mate
Seems like you did not format your data partition during TWRP installation.........
Try flashing your custom rom from the External SD card......your data partition has all your app , files , passwords, photos...there is still a chance that there it may be a incompatibility issue between your apps and the new rom....that is why they recommend a factory reset when flashing a new custom rom
Click to expand...
Click to collapse
hi mate
thanks for your reply. I dont have an external SD card
Is there any other way of sorting this? I am downloading a stock rom as we speak.

scientificharmony said:
hi mate
thanks for your reply. I dont have an external SD card
Is there any other way of sorting this? I am downloading a stock rom as we speak.
Click to expand...
Click to collapse
Hi
TWRP can not handle Samsung encryption . if you wish to use TWRP and have access to the Data partition ( internal SD card) you need to format it so the encryption is disabled ( you lose all your apps , data and user configuration AKA factory reset) , you can have TWRP and data encryption but mods and roms have to be flashed from external memories also you will not have available MTP in recovery or factory reset from it.
There is no way to disable data encryption without format data.....

Ok, I got a friends SD card and placed the Rom on there. I can now see the Rom but the trouble is, TWRP wont let me wipe Dalvik / data / system / cache as it wont mount the storage....
can I still apply the ROM?

Unable to restart your device. The integrity verification has failed. You need to reset your device to factory default settings. This will erase all of your data.

scientificharmony said:
Unable to restart your device. The integrity verification has failed. You need to reset your device to factory default settings. This will erase all of your data.
Click to expand...
Click to collapse
That is why I point it out " factory reset is recommended when flashing custom rom" if you wish to flash a custom rom you will have to format your data partition and flash the data verify file........

MAX 404 said:
That is why I point it out " factory reset is recommended when flashing custom rom" if you wish to flash a custom rom you will have to format your data partition and flash the data verify file........
Click to expand...
Click to collapse
I have tried to format/wipe data. TWRP keeps saying it failed as it cant mount the storage.
I tried flashing the stock rom via odin and it also failed as it goes to recovery to wipe data and it fails again as it cant mount storage.

scientificharmony said:
I have tried to format/wipe data. TWRP keeps saying it failed as it cant mount the storage.
I tried flashing the stock rom via odin and it also failed as it goes to recovery to wipe data and it fails again as it cant mount storage.
Click to expand...
Click to collapse
How did you flash the stock rom...which files did you use?
Wipe data is not enough you have to Wipe / FORMAT DATA and type yes....

1 To get rid of encryption, go to "wipe", format data (TWRP) (keyboard will pop up) then type "yes" and format it, then reboot to recovery
2. After flashing this, hit wipe, full wipe (this will clean all internal memory and your data will be lost
3 you can test if encryption is still enabled, if TWRP shows error about not mounting data your phone is still encrypted
Sent from my SM-G930F using XDA-Developers mobile app

Josh Smith10 said:
1 To get rid of encryption, go to "wipe", format data (TWRP) (keyboard will pop up) then type "yes" and format it, then reboot to recovery
2. After flashing this, hit wipe, full wipe (this will clean all internal memory and your data will be lost
3 you can test if encryption is still enabled, if TWRP shows error about not mounting data your phone is still encrypted
Sent from my SM-G930F using XDA-Developers mobile app
Click to expand...
Click to collapse
What version of TWRP are you guys using and what version Super SU?

Delete

TWRP Unable to Mount storage on wiping all but Internal storage

Hi all,
I'm installing ResurrectionRemix on my device, and so to do that, of course, I have to wipe System, cache, data and dalvik. However, without anything happening, it says Unable to mount storage. So I go into TWRP mount and press System. When I try again, the same thing happens. The only thing I can do after is restore a full nandroid backup (With data included)
I have no idea how to provide a logcat, however I'm sure it's easy and if it's needed I shall find out how.
Thanks,
MajorPlayz

Encryption Unsucessful Fix

I am trying to install an Oreo based ROM lineage os 15.1
Currently data partition is ext4
Latest Twrp installed
But still whenever I try to install any Oreo ROM I get encryption unsuccessful message and even after factory reset with yes I get stuck on same thing again and again and if I try to change recovery after installing ROM the phone gets stuck in boot loop can anyone please help to solve this problem

I think this will solve ur issue
Yup I have also the same problem first of all do all these steps I think it resolve your issue:-
1. Go to settings of TWRP and reboot recovery.
2. Now format all the internal storage if u have important files in internal storage skip this step
3. After that go to advanced wipe and select system and data one by one and change its format to ext4.
4. Now advanced wipe everything.
5. Thats all now you can install lineage 15.1
I did the same and its working properly in my phone.
This problem occurs due to change of format of data to f2f so convert it to EXT4 and its fine

when you did advanced wipe to evertything is data, cache, system, etc? i already did this but still saying me that my phone was encrypted and i have to unlock with the pin or my account but i get a loop even if i put the correct user and password.
Udgam Tiwari said:
Yup I have also the same problem first of all do all these steps I think it resolve your issue:-
1. Go to settings of TWRP and reboot recovery.
2. Now format all the internal storage if u have important files in internal storage skip this step
3. After that go to advanced wipe and select system and data one by one and change its format to ext4.
4. Now advanced wipe everything.
5. Thats all now you can install lineage 15.1
I did the same and its working properly in my phone.
This problem occurs due to change of format of data to f2f so convert it to EXT4 and its fine
Click to expand...
Click to collapse

Normal procedure. Fastboot boot command
Boot to TWRP.
Reboot to TWRP through reboot menu.
Factory reset.
Advanced wipe: change data file format to ext4
Reboot to TWRP through reboot menu again.
Wipe, format data.
Now wipe system, cache and dalvik.
Reboot to TWRP again.
Flash rom.
Gapps.
Magisk if wanted.
Wipe dalvik and cache.
Reboot and enjoy

Murkroow said:
when you did advanced wipe to evertything is data, cache, system, etc? i already did this but still saying me that my phone was encrypted and i have to unlock with the pin or my account but i get a loop even if i put the correct user and password.
Click to expand...
Click to collapse
Bro I already mentioned first of all you have to Factory reset but it will wipe all your data from internal storage so do have a back up for that. Encryption issue can only resolved by factory reset.

Check out my video
​It helped many people hope it helps you.
https://m.youtube.com/watch?v=Ov_Eq268_4U

0 mb in TWRP internal storage

I searched for an answer and noticed it's a common issue. I am trying to flash a kernel on to my already flashed rom. I was wondering if there is a more current fix. More importantly, how can this be avoided in the future. Thank you guys!

Its caused by a bug/error with either the filesystem or encryption.
Did you wipe data after flashing the new ROM? Data from stock usually doesn't work with custom ROMs.
Do you have a PIN/password on Android?
Are you using the latest build of TWRP?
Press the menu button at the bottom of the screen in TWRP and post what the error message is in the red text.

It's caused by no root access

djhulk2 said:
It's caused by no root access
Click to expand...
Click to collapse
Something is probably wrong with the data partition. TWRP should always have root access.
Try in TWRP:
Wipe > Format Data > Slide to format
This will erase the data partition, so backup everything to a PC in Android first if needed. It should allow TWRP to mount /data again.

KemikalElite said:
Something is probably wrong with the data partition. TWRP should always have root access.
Try in TWRP:
Wipe > Format Data > Slide to format
This will erase the data partition, so backup everything to a PC in Android first if needed. It should allow TWRP to mount /data again.
Click to expand...
Click to collapse
I've debated on doing this. I'm not worried about losing pictures texts etc as they're backed up.
I read that it essentially leaves the device with no OS. If that's wrong please let me know!

I have found that if I choose Slot A and reboot system it reboots me in to TWRP. If I choose Slot B it runs the OS like normal (except I still have issues using Facebook and it's services).
The ROM works and I can perform all the custom mods on it. I just want to flash a kernel and the problem persists. 0 mb in storage.
It's trial and error at this point. Fail fast fail forward. I have another phone I can use but I love the OnePlus. Any help will be appreciated!

https://andi34.github.io/faq/faq_twrp.html
I'm not willing to risk it until I know how to get the custom ROM on to the storage to flash it.

Yes formating by typing in yes will wipe it all,everything including pictures, with no rom on it at all. If u choose to do that, don't close twrp. Instead you should be able mount after wards, once mounted transfer the magisk zip, twrp, and your custom rom(has to be 1.5gb not 200mb through magisk). Flash magesik, install ram disk twrp, install rom. That was a method I've done before but if u want to keep everything there is other way
fastboot boot twrp.img, that command boots twrp if u have it or don't, installing to ram disk makes it permant...this boot command is just a one time thing each time. It's what I do when new firmware update, I loose root but I regain it each time

Never heard of formating data removing the OS, that would be if you wipe the system and normal wipe is like a factory data reset and therefore will not wipe your phone of the OS

djhulk2 said:
Yes formating by typing in yes will wipe it all,everything including pictures, with no rom on it at all. If u choose to do that, don't close twrp. Instead you should be able mount after wards, once mounted transfer the magisk zip, twrp, and your custom rom(has to be 1.5gb not 200mb through magisk). Flash magesik, install ram disk twrp, install rom. That was a method I've done before but if u want to keep everything there is other way
fastboot boot twrp.img, that command boots twrp if u have it or don't, installing to ram disk makes it permant...this boot command is just a one time thing each time. It's what I do when new firmware update, I loose root but I regain it each time
Click to expand...
Click to collapse
I attempted to format. It said
"failed to mount /data (device or resource busy)
"unable to mount storage"

Try this in recovery, sometimes its known to work.
Wipe > Advanced Wipe > Check Data and press Repair or Change File System > Change File System > Change it to EXT2.
Repeat the same process selecting Ext4
Wipe > Advanced Wipe > Check Data and press Repair or Change File System > Change File System > Change it to back to EXT4.
Try formatting data after this.

drey4211 said:
I attempted to format. It said
"failed to mount /data (device or resource busy)
"unable to mount storage"
Click to expand...
Click to collapse
Since you dont care about the data on the phone I would just do 1 of 2 things. 1st I would reflash twrp on to you phone if that doesn't work then I would just grab the fastboot ROM and just flash your phone back to full stock reroot and install twrp from scratch. I would not try to start repairing partitions. I wouldn't want to worry about screwing up the EFS partition

Well in an update, I formatted the
Storage and now I'm stuck in bootloader screen. It's unlocked but I'm having a hard time flashing a ROM through adb.

I use the twrp version 3.3.1-2
Best would be to just use fast command to boot it
But it should be under wipe/format data/then type in yes

That was what I was trying to have you avoid. If your can boot to fastboot download the fastboot ROM I told you to and run the flash-all.bat file. If your on 9.5.8 make sure you use the fastboot ROM of the same version. Do not flash azip of a different version firmware like 9.5.7.

It happens to me any time I'm in twrp and flash a rom then reflash twrp. It doesn't matter if I flash Magisk or not the issue always happens. What I do is use a USB C flash drive and plug it in when I want to flash/backup a rom. This way I can always access it. After flashing any rom then booting I'm always able to access my internal storage again. It seems like a bug in twrp.
The strange part is when this bug happens your files are encrypted in a 0 folder but you can still copy from your PC to your internal storage while in twrp.

I essentially soft bricked my device. Called OnePlus and they got me up and running. That's awesome that they have that service!

Are you removing all security? Pattern, pin and fingerprints? Are you decrypted? Never had an issue with flashing a ROM causing these issues which is why I'm asking. Something you've done at some point is causing this

I'm not sure what that was. Ironically enough I am now stuck in TWRP boot loop. Hopefully I can figure this out otherwise I have to call oneplus again.
I will admit I may not know everything but it's trial and error. I don't have anyone to really teach me this so I try to read the forums and learn. You guys have been great!

ajsmsg78 said:
It happens to me any time I'm in twrp and flash a rom then reflash twrp. It doesn't matter if I flash Magisk or not the issue always happens. What I do is use a USB C flash drive and plug it in when I want to flash/backup a rom. This way I can always access it. After flashing any rom then booting I'm always able to access my internal storage again. It seems like a bug in twrp.
The strange part is when this bug happens your files are encrypted in a 0 folder but you can still copy from your PC to your internal storage while in twrp.
Click to expand...
Click to collapse
I've the same issue.. did you find a fix? So annoying