I'm only speculating here... but the geniuses over at Gotab appears to have put very critical components for their tablet on a partition that you're allowed to flash in the settings menu. Of course theres no warning of the consequences of erasing this partition on their site, instruction booklet, or device so I found out the hard way.
So I erased the data on my erasable partition. Before that I:
Could get into the recovery menu had a partition of 400+ MB, had a partition of 2.3GB.
After I erased the data on the 2.3GB I:
Cannot get into Recovery menu, cannot download or update apps in play store, apparantly cannot install APK from file manager, have a partition of 0.00MB, had a partition of 2.3GB, and the device factory-resets after every time I power on/off.
Related
Hi, I have a lot of questions about Android Filesystem, ROM and recovery, i read a lot on internet but i couldn´t understand everything, I appreciate if someone take a little time to teach me the following questions:
These are the partitions I read there are on Android:
/boot
/system
/data
/recovery
/cache
so my first question:
1) why i cannot see on ES File Explorer or Link2SD, recovery partition? where is it?
When i wanted to enter into recovery automatically my phone was restored to the manufacturer status, and no menu was showed, so I have two more questions:
2) Does recovery restore Data and System partition or only clear Data partition and system is not changed?
3) If I open 'ROM Manager' and click on 'Flash ClockworkMod Recovery', will I have the famous menu to save a copy of my actual ROM?
In case i want to learn more about customs ROM,
4) Why everybody talk about to install it on SD? To flash a new ROM do not format the internal memory, I mean the actual partitions system, data, etc...?
5) Is there any way to change the size of these partitions?
from already thank you very much!!
I wanted to enable full gpu rendering on my Samsung P6200... I am running 4.1.2, rooted. I downloaded the zip file, booted into recovery and installed the zip file, I rebooted, it shows the normal model number and that on the screen, and about the time when the boot animation starts it just goes blank, although it is still on, now, I rebooted back to recovery, I had made a backup moments before, I only had 770 MB of space left so it made a full backup except my /data partition, that failed, but I didn't want that backed up anyway. I thought well maybe I should restore, so I went to advanced restore and chose the boot partition to restore, restore was succesful, I restarted and did the same thing, now I try to restore the whole backup and it says md5 mismatch, I connect to adb and mount everything, and find my mnt folder is missing, now I don't know how to fix this, if I go to install zip from sdcard it shows all my files and folders there, but if I go to /sdcard/storage/sdcard0 in adb it only shows two folders, Download and Webzine. How to fix this, I don't want to restore my /data partition due to the fact that it only did like 5% of the backup of it and need a lot of that data, if I were to fix the md5 mismatch (don't know how) what partition would I restore to fix the boot error? And how do I fix the missing mnt folder issue?
Ok, sorry, found my files are stored in /sdcard/, although I could swear they were in sdcard0
I was trying to expand my system partition size.
I flashed a zip via CWM on my phone, and must have made a mistake.
After i flash, my partition table seems to be messed up.
My "boot" partition is fine.
All other partition seems to be "invalid" now.
I am able to enter fastboot, and "fastboot boot recovery.img" to enter recovery
i am not able to boot, or enter recovery mode directly.
I tried to "erase" via fastboot, but the partition is invalid.
i tried to "flash" via fastboot, but the partition is invalid.
Is there any way to "fix" my partitions?
i have downloaded a CM11.zip for my phone.
I have downloaded a stock rom for my phone.
i have access to these files, which are supposed to be system partition tables. found here:
github mirom/android_bootable_recovery/tree/cm-10.1/res/partition
i guess a more specific question would be, "How can I create the partitions for a phone?"
My phone has a 4GB internal space and 1GB ram.
I have a ZTE Axon 7 (A2017U) and I'm trying to install a stock rom (A2017UV1.1.0B35). I currently have TWRP installed and an unlocked bootloader. I can access the device via fastboot and TWRP recovery mode, but otherwise it will not boot.
I'm stuck in a loop:
If I install my rom via TWRP, when I reboot the phone the /system partition is never mounted. I can see "Failed to mount '/system' (Invalid argument)" written in the log
If I view the /system partition details on TWRP's "Wipe->Advanced wipe->Repair or change file system" screen, the partition is listed as "Present: Yes, Removable: No, Size: 0MB, Used: 0MB, Free: 0MB, Backup size: 0MB
If I format the /system partition using "Wipe" function, the "Formatting system using make_ext4fs" operation succeeds and partition seems to be correctly formatted using ext4, and is listed as "Present: Yes, Removable: No, Size: 5455MB, Used: 10MB, Free: 5444MB, Backup size: 10MB
I'm able to access the partition via the terminal, and if I write a text file to it and reboot the device, I'm able to read it back... It seems the partition is working correctly.
I attempt to install the rom again using TWRP's "Install->Install zip" option, and after ~10 minutes it states that installation was completed successfully.
I reboot the device and the OS does not load. If I access TWRP, I see the /system partition is not mounted and the cycle continues
I've also tried installing other roms (e.g. Lineage OS), but they all fail assert checks, even thought I'm 100% positive they're for the correct device.
I'm tearing my hair out here. I'm a programmer by day and I'm fairly experienced with Unix, but admittedly I don't have much experience working with Android. There's a good chance I'm missing something.
Any idea what's going on, or what to try next? Is there any other information I can provide that might help me troubleshoot the problem?
I don't know of this will help, but I had a similar issue with a Samsung phone once. What had happened is when I flashed the new ROM the .dat or .img file was smaller than the original partition and it shrunk the system partition. I was lucky and I had previously dumped a copy of my system partition with terminal and was able to put it back.
When the partition was shrunk it wouldn't install any other ROM's either. If you could get another user with your same device to dump their system into an .img file we might be able to fix it with dd commands.
Sent from my LG-Q710AL using Tapatalk
Helo! I will explain the case.
Device: Samsung Galaxy S Duos S7562
Custom ROM: Lineage 15
I selected to perform device encryption in the default option of the system, after the whole process, the phone got stuck in the Samsung logo and won't start. So I accessed the TWRP and saw that it is not possible to access /data and it is also not possible to clean it.
Through the computer I can't get the device to be recognized by the ADB.
Is there any solution or can I schedule the wake?
TWRP >> Wipe >> format data >> type "yes" .
It appears the ROM does not support encryption/decryption, the phone is indeed encrypted, but the problem is when trying to decrypt the data, it seems to fail.
If you had any important files, there has been some tutorials on decrypting /data in TWRP using the decryption password.
Mohamedkam000Thanks for the tip. I went to research and found this tutorial. It worked for me from step 8.
I found it on another site, I don't know if I can quote the source here, but here are the steps, in case someone else needs it:
1. The first thing to try is whether the internal storage was somehow encrypted using a legacy screen lock method.
2. Go to Settings > Security > Screen lock of your Android device and change screen lock method to Approved or Pin. Create a new one.
3. Reboot into TWRP, and it should ask for a password - enter the pass or pin you just created.
4. TWRP will attempt to decrypt your device's internal storage and, if successful, you should have no further problems. However, if that doesn't solve the “unable to mount data, 0mb internal storage” issue, continue with the rest of this guide.
5. Reboot your device into TWRP again.
6. Navigate to Clean > Next Clean > Data and choose Repair or Change File System.
7. Press Repair File System to see if this resolves the issue. If not, continue.
8. Press Change File System, choose Ext2 and swipe to confirm.
9. Now go back to Ext4 and swipe to confirm.
10. Go back to the TWRP main menu, then to the Mount menu and check if your partitions can be mounted now.
11. If you are still unable to mount your partitions, you will need to repair the internal partition, which will likely clear your internal storage.
There are four points to clear it out:
For /data partition to show 0 MB, or failed to mount, it doesn't mean it has broken its filesystem, it didn't, it's just encrypted, that's how the protection works.
Choosing to repair filesystem or change filesystem may result in a bootable/mountable filesystems, however, you'll lose your data. Not all phones has decryption on TWRP, it needs a modified recovery.
Encryption has different security key than the regular lockscreen, it doesn't use pattern. So it doesn't matter what you've set on your lockscreen.
It seems to be your first time encountering this issue. On modern phones (S6 and above), when you flash TWRP, you won't be able to mount /data, because all phones come with forced encrypting mechanism, so in order to flash custom ROM, you'll have to format data (the option where you write "yes"). And any mount of /system will result in a bootloop haha.
Mohamedkam000 said:
There are four points to clear it out:
For /data partition to show 0 MB, or failed to mount, it doesn't mean it has broken its filesystem, it didn't, it's just encrypted, that's how the protection works.
Choosing to repair filesystem or change filesystem may result in a bootable/mountable filesystems, however, you'll lose your data. Not all phones has decryption on TWRP, it needs a modified recovery.
Encryption has different security key than the regular lockscreen, it doesn't use pattern. So it doesn't matter what you've set on your lockscreen.
It seems to be your first time encountering this issue. On modern phones (S6 and above), when you flash TWRP, you won't be able to mount /data, because all phones come with forced encrypting mechanism, so in order to flash custom ROM, you'll have to format data (the option where you write "yes"). And any mount of /system will result in a bootloop haha.
Click to expand...
Click to collapse
Thanks for the information. Next time I'm going to look for an encryption-compatible TWRP.