Is It supposed to be normal? Shouldn't It be formatted to f2fs?
try diskinfo from the play store
if it still hows EXT4
run the april factory image with flash-all.bat
then once complete go to bootloader (make sure locked bootloader) and format /data
boot into factory recovery, and read the recovery logs, will tell you exactly how each partition is formatted.
Related
Hello,
My first gen Kindle Fire has been setup in the OtterX format and has been running well on the CM STG7 ROM. I decided to update to the latest version last week and since then, my OtterX has not recognized the SDCard.
TWRP does see the SDcard and will view it's contents when browsing the file manager, but it won't mount the SDcard to my computer desktop. Nothing happens when I click the mount button.
When the OtterX boots, the System > Storage sees the SDcard and contents, but when I try to browse to it with a file manager, it says the path is invalid.
ADB shell sees the /sdcard/ directory and I can browse it from the shell as well.
I've tried formatting the entire device, including wiping the internal storage and formatting data (where you have to type in "yes") and nothing has resolved this issue.
Any idea what's going on?
I have had similar problem, rebooting a couple of this times seemed to fix.
But may need to reformat in twrp or do otter x partitions in bootloader
sd_shadow said:
I have had similar problem, rebooting a couple of this times seemed to fix.
But may need to reformat in twrp or do otter x partitions in bootloader
Click to expand...
Click to collapse
I'll try reformatting again.
My partitions became corrupted a couple years ago and I had to rebuild them manually, following a tutorial. OtterX partitions in the bootloader doesn't work on my device. I'm guessing it's because the partitions are spot-on with the sizing.
Do you know of a way to rebuild the partitions manually so they match the stock specs - maybe that way the bootloader partitioning would work?
Just restore amazon partitions in bootloader, reboot, restore otter x partitions.
sd_shadow said:
Just restore amazon partitions in bootloader, reboot, restore otter x partitions.
Click to expand...
Click to collapse
Bingo! That seemed to fix it. CM11 is seeing the SDcard just fine now. Thank you!
sd_shadow said:
Just restore amazon partitions in bootloader, reboot, restore otter x partitions.
Click to expand...
Click to collapse
For some reason after trying a different ROM (can't remember which one), I lost my SD card again and I can't seem to get it back. I even reverted the bootloader to FFF and did the "OEM Format", then followed the steps back to OtterX.
Attached is my partition table. I don't see a 'media' table, which is the SDcard, correct?
Any idea what else to do?
Otterx utilizes space that was already there, but reserved for the system. In order to better use available space for user data, the storage is placed elsewhere on the tree. The sd card should be located under storage on the otterx tree.
Ixthusdan said:
Otterx utilizes space that was already there, but reserved for the system. In order to better use available space for user data, the storage is placed elsewhere on the tree. The sd card should be located under storage on the otterx tree.
Click to expand...
Click to collapse
The strange thing is TWRP sees and accesses the SD card just fine.
I have a feeling the SD card isn't formatted in the correct format. Any idea how to format (or check/change format type) of the SD card through ADB?
Did you try the Repair file system in TWRP?
In OtterX Twrp 2.7.1.0 not 2.7.0.1
Wipe>advanced wipe
check data>current file system should be f2fs
tap Repair or change file system if you want to change back to ext4
sd_shadow said:
Did you try the Repair file system in TWRP?
In OtterX Twrp 2.7.1.0 not 2.7.0.1
Wipe>advanced wipe
check data>current file system should be f2fs
tap Repair or change file system if you want to change back to ext4
Click to expand...
Click to collapse
Just checked the partitions with TWRP 2.7.1.0...
Dalvik Cache - Invalid partition selection
Data - f2fs
Internal Storage - Invalid partition selection
Cache - f2fs
System - ext4
I then formatted data as ext4 and the ROM still doesn't see the SD partition.
MrBrady said:
Just checked the partitions with TWRP 2.7.1.0...
Dalvik Cache - Invalid partition selection
Data - f2fs
Internal Storage - Invalid partition selection
Cache - f2fs
System - ext4
I then formatted data as ext4 and the ROM still doesn't see the SD partition.
Click to expand...
Click to collapse
did you try the repair option?
sd_shadow said:
did you try the repair option?
Click to expand...
Click to collapse
Yup! Didn't seem to fix the issue.
Is there a way to put the Kindle back to 100% factory specs, like SBF for the Droid X or Odin for Galaxy S3?
VZW SGSIII
Is this what you used to re-partition the system, data, and cache partitions?
[HOW TO] Fix "Failure to mount" sdcard, system, data or cache
So I flahed the new MDB08M image and since it uses the "I" boot image I went ahead and flashed the modified boot.img and flashed TWRP and used it to root as I didn't have SuperSU zip on the device yet. After flashing the new system I didn't do any factory reset.
Now TWRP says that internal storage is 0mb and it can't mount /data. Every time I boot into it, it comes up with the screen asking me if I want to modify /system or leave it read only. I check the box to not show it again and swipe to modify.
I've tried using adb again to flash recovery but it didn't help. Any suggestions?
Edit: bootloader also sais I'm secure, and in security it sais I'm encrypted..
TWRP can't decrypt /data on the N5X yet. You can format from TWRP, but you'll lose the contents, of course.
PhoenixTank said:
TWRP can't decrypt /data on the N5X yet. You can format from TWRP, but you'll lose the contents, of course.
Click to expand...
Click to collapse
I thought by flashing the modified boot image that would decrypt? It did on MDB08I..
The modified boot just changes flag to encrytable instead of force encryption. It doesn't actually decrypt the drive contents. Once you wipe it then you can mount data in TWRP.
eqjunkie829 said:
The modified boot just changes flag to encrytable instead of force encryption. It doesn't actually decrypt the drive contents. Once you wipe it then you can mount data in TWRP.
Click to expand...
Click to collapse
so just factory reset in TWRP?
Edit: reflashed firmware, flashed modified boot and did a factory reset in stock recovery. reflashed TWRP and all is good. thank you
Hello to everyone. I am using Xperia M and can not mount data, system mount via TWRP Recovery. I also can not load the stock version and kernel with Flashtool. The device goes into recovery mode, is charged and is recognized as a nickname when connected to a PC. I will be glad if you help me.
didyou said:
Hello to everyone. I am using Xperia M and can not mount data, system mount via TWRP Recovery. I also can not load the stock version and kernel with Flashtool. The device goes into recovery mode, is charged and is recognized as a nickname when connected to a PC. I will be glad if you help me.
Click to expand...
Click to collapse
Your device got ebola. There is no solution. Sorry mate.
Use internal storage 0 mb problem in TWRP Recovery. No flashing kernel and roms.
didyou said:
Hello to everyone. I am using Xperia M and can not mount data, system mount via TWRP Recovery. I also can not load the stock version and kernel with Flashtool. The device goes into recovery mode, is charged and is recognized as a nickname when connected to a PC. I will be glad if you help me.
Click to expand...
Click to collapse
i am having same problem . but my internal storage is mounted as android os and my actual storage is not visible please help me.
fix for 0MB internal storage problem
Your device is still recoverable if you can boot into twrp successfully
Go to advanced --> terminal
Check your partition table with
fdisk -l /dev/block/mmcblk0
it will print out the partition table, last 3 should be system, cache and data
format system with ext4, for me that was /dev/mmcblk0p25 - YOURS MAY DIFFER
make_ext4fs /dev/block/mmcblk0p25
format data with ext4, for me that was /dev/mmcblk0p27
make_ext4fs /dev/block/mmcblk0p27
For me, this was met with errors, so format it with exfat first, mkfs.exfat /dev/mmcblk0p27, reboot into recovery, then format with make_ext4fs.
You cannot do this through advanced wipe, because twrp tries to guess your partitions AFTER mounting them, then reads /system is mounted on /dev/block/mmdblk0p25, but it's not mounted, so no repairing/formatting through that. Use the terminal instead, then reboot, twrp will find the partitions then.
afterwards reboot again into recovery. I didn't have to reformat cache, but you may have to. try mkfs.ext2 on that. You will always want to go with make_ext4fs though.
internal storage should show up again now, wiping and installing zips will work again.
rak-zero said:
Your device is still recoverable if you can boot into twrp successfully
Go to advanced --> terminal
Check your partition table with
fdisk -l /dev/block/mmcblk0
it will print out the partition table, last 3 should be system, cache and data
format system with ext4, for me that was /dev/mmcblk0p25 - YOURS MAY DIFFER
make_ext4fs /dev/block/mmcblk0p25
format data with ext4, for me that was /dev/mmcblk0p27
make_ext4fs /dev/block/mmcblk0p27
For me, this was met with errors, so format it with exfat first, mkfs.exfat /dev/mmcblk0p27, reboot into recovery, then format with make_ext4fs.
You cannot do this through advanced wipe, because twrp tries to guess your partitions AFTER mounting them, then reads /system is mounted on /dev/block/mmdblk0p25, but it's not mounted, so no repairing/formatting through that. Use the terminal instead, then reboot, twrp will find the partitions then.
afterwards reboot again into recovery. I didn't have to reformat cache, but you may have to. try mkfs.ext2 on that. You will always want to go with make_ext4fs though.
internal storage should show up again now, wiping and installing zips will work again.
Click to expand...
Click to collapse
Thank you for your message I just saw. I tried, but I still see the internal memory of 0MB when I try to Wipe.
https://imgyukle.com/i/Rk24Gt
https://imgyukle.com/i/Rk264c
https://imgyukle.com/i/Rk2fyR
didyou said:
Thank you for your message I just saw. I tried, but I still see the internal memory of 0MB when I try to Wipe.
Did you reboot after? You can try the advanced format in twrp, maybe you need to use exfat for your partition 27 (data) or ext3 not ext4 for system. Try some combinations.
Which twrp version is installed?
I checked mine and partitions 25 to 27 are formatted with ext4. I have latest twrp 3.0.2.0 and use lineage 14.1. from here.
Partition table looks fine, same sizes as me.
Click to expand...
Click to collapse
rak-zero said:
didyou said:
Thank you for your message I just saw. I tried, but I still see the internal memory of 0MB when I try to Wipe.
Did you reboot after? You can try the advanced format in twrp, maybe you need to use exfat for your partition 27 (data) or ext3 not ext4 for system. Try some combinations.
Which twrp version is installed?
I checked mine and partitions 25 to 27 are formatted with ext4. I have latest twrp 3.0.2.0 and use lineage 14.1. from here.
Partition table looks fine, same sizes as me.
Click to expand...
Click to collapse
I am using TWRP version 3.1.1.0. I tried to make Wipe after it restarted after operations but it still seems to be 0MB. I tried to change the file system, but not through the terminal.
Click to expand...
Click to collapse
I know how to format system and cache to f2fs, but what's the proper way to revert back to ext4? On my old Nexus 6p I could just fastboot the factory image and everything went back fine, but given the the 5t doesn't have factory images, I can't do that.
So would I just format to ex4 the same exact way that I would format to f2fs?
Format data and then change filesystem?
swapavi said:
I know how to format system and cache to f2fs, but what's the proper way to revert back to ext4? On my old Nexus 6p I could just fastboot the factory image and everything went back fine, but given the the 5t doesn't have factory images, I can't do that.
So would I just format to ex4 the same exact way that I would format to f2fs?
Format data and then change filesystem?
Click to expand...
Click to collapse
Yes just change fs and fastboot or twrp flash full ROM zip
I finally properly rooted my A5 2017 (SW-A520W) and installed the TWRP recovery. But I can't do a full backup of the phone. It won't let me have access to /data. I know this is because the partition is encrypted. I also know I am to run no-verity-opt-encrypt-6.0 zip after wiping the /data partition. But guess what?! Everytime I go back into recovery, /data is encrypted again.
Please Help.