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've been playing around with which filesystems I can format the android systems partitions and then install a custom ROM on.
I tried formatting them to F2FS and then installing a CM and Squids kernel found it wouldn't boot, then wiped them back and formatted
them to ext4 (which I think is the default android filesystem) and installed CM and Squid's kernel
and now on boot its asking me to enter a password to boot my android system.
partitions were the filesystems were changed are /system /data /cache.
I really don't want to be admitting this right now that I bjorked my system while tinker gnoming,
and don't know enough to put it back.
But yeah formatting ext4 /data /cache /system and then flashing everything back should have done it right?
Damn think I may have run into a bug in the Recovery where no matter what happens it still thinks /data is f2fs even when its been formatted back to ext4
Never mind unbricked it, I think this is the end of late night beer fueled tinkering for me, but I've restored the system.
Should TWRP have been able to format /data to another filesystem besides ext4 or f2fs and which filesystem was the
default on /data from the beginning?
The recovery system seemed to assume that /data was F2FS and even after trying to format it with something different
the repair tool ran was always the F2FS one and always dropped some error messages even after a format to Ext4.
This whole project started when I got the 'good idea' into my head to see if I could format all the partitions that mattered with
F2FS and flash CM 12.1 R53 with Squid's R8 with the partitions formatted F2FS.
Eh I'm done shooting myself in the foot for awhile (or the ass).
Ended with /system (ext4), /data (f2fs), /cache (ext4) and then flashed everything and the system is running great.
The whole experience was worth getting more familiar with TWRP and learning that it is built noob 'tough'.
And can perform awesome awesome surgery for you, when your done shooting your self in the ass.
By the way bro... I think the data partition on this phone comes in f2fs by default
Sent from my MotoE2(4G-LTE) using Tapatalk
I have the same issue!
Fishy.. why in the hell would you do that unless you *found* a phone
and were then trying like a noob to reformat it ?
Back in the day I had my phone encrypted with data as a ext4 partition, I switched to using f2fs for a long time.
Now that I've tried to go back to using data as a ext4 partition while booting android asks for a invalid decryption password
using a really old pin number (I've had it encrypted several times since then using f2fs with different pin numbers) from the first
time I encrypted my partition while it was ext4.
Now when ever I wipe my data partition and try and use it as ext4 while booting android asks for a decryption pin which I can enter
but then complains that the filesystem it is trying to decrypt is corrupt.
I've tried doing a data format in twrp but it automatically formats it f2fs which doesn't solve the problem since
the problem only shows up while data is formated ext4.
I've tried every piece of wisdom I can find on the internet.
factory reset,
formatting all partitions,
dd front and back of userdata and then make_ext4 on userdata,
twrp format data,
recovery --wipe_data --set_encrypted_filesystem=off (from within twrp with the partition formated ext4),
format f2fs then boot up and reset and format ext4,
etc.
How do I give data the ultimate clean slate for being formatted ext4?
Or where is the remnant of the old encryption info stored from the first time I encrypted my phone?
I can format my data partition f2fs but frankly I was a little stunned when I saw the kind of overhead that filesystem has,
its space using overhead is way more then I want to have in a filesystem, or any filesystem I've ever seen.
Also is the problem not what I think it is?
Faced the same behaviour on my xt1524. Would be interesting to know if there is a solution for this
Is there a way to generate a new encryption from within the recovery?
Since it won't boot with data formatted as ext4.
Formatting it ext4 and then putting a new valid encryption on it?
From what I've found it, if the UI to unlock the partition on boot had a cancel button the system would boot as normal.
Unfortunately there is no cancel button on the unlock encrypted partition screen on our device. =/
Tried flashing a different recovery and using it wiping tools on data.
official twrp-3.0.2-0-surnia.img.
mkfs-f2fs -t 0 /dev/block/mmcblk0p44
process ended with ERROR:255
Unable to wipe Data.
Unable to format to remove encryption.
Also data wiping on TWRP is defaulting to trying to format data as F2FS which isn't even the default,
and while the partition has been switched to ext4.
I'd like to fastboot erase userdata and then fastboot format userdata.
But its giving me this error message.
fastboot format userdata
(bootloader) has-slot:userdata: not found
Formatting is not supported for file system with type 'raw'.
I've already done a lot of looking around on this issue, I'm normally not worried about this but
formatting internal system partitions that I don't understand how its different from a standard
desktop computers layout does worry me.
Should I be doing a full wipe and format everything to stock and then back to a custom rom?
God I wish this was a desktop computer right now, wipe the hard drive and reinstall the operating system,
there is something to be said for being simple and straight forward.
WTB cellular modem support in standard operating systems, and handheld devices that
can run standard operating systems.
I'd ditch this overcomplicated vendor locked sht so fast and never look back.
Following this guide to setup a new system encryption with rom in one go from the start with data as ext4 to see if I can bypass it this way.
But I'm getting a cannot find libraries error running cryptfs format command from adb shell or twrp terminal. b(>.<)d
http://android.stackexchange.com/questions/33398/cannot-factory-reset-after-encrypting
All this because someone thought it would be a great idea to take off the cancel button on data decryption
during boot.
This is why god invented beer and soaking you're brain in alcohol.
Damn been at this thing all day and still no luck.
Can I smoke the whole userdata partition with DD without bricking the phone?
In fact what can I effectively zero on a android phone without bricking it?
Am I miss reading this problem? Is the new inbuilt ext4 encryption (ext4 filesystem now has built in encryption support on newer kernels) support assumed to be on?
Never mind not as solved as I thought, But I just found another way to have my partition set to F2FS with letting me know. (^.^)
God this illustrates why formatting utilities that take shortcuts and 'ghetto erase' stuff are bad.
*Edited*
Default filesystem from the factory was F2FS (I have a bad memory : ) looks like it doesn't support putting data on Ext4.
Editing this post because I did a lot of post updates on what I was trouble shooting, but that might have
pissed people off because it does 'bump' the thread.
Sigh I'm throwing in the towel and formatting F2FS and moving on, F2FS is a one way door one which you never get back to ext4 from. > : (
Or ext4 formatting utilities suck balls and don't do their jobs.
Format all partitions to f2fs reboot to recovery again and format system and cache to ext4 now make a factory reset and reboot.
Hallo, guys!
Well, I bought myself Mate 10 Lite. Then I asked Huawei for oem unlock key, became a root/admin of my device. I flashed TWRP 3.1.1-0 (coloured version, not the black/grey) wiped all the Huawei mess, killed all unnecessary mem eaters and I am quite happy with stock firmware. BUT!
For some reason, no custom recovery will save my settings! Any time I access it, it always asks me for making the system writeable, my time zone, my display & vibro settings, etc., all is always reset to some default. I tried different TWRPs, I even fully wiped the rooted phone to factory defaults, formated Dalwik, Data, Cache, even internal SD (did not dare to format the other partitions since I dont know what would that do...). Well, I wiped it, rebooted to TWRP, set all things as I want them and powered off the device. Then powered on into TWRP and again, TWRP is in default... W T F...?
So, how to make the custom recovery to save my settings, please?
Gang-star said:
Hallo, guys!
Well, I bought myself Mate 10 Lite. Then I asked Huawei for oem unlock key, became a root/admin of my device. I flashed TWRP 3.1.1-0 (coloured version, not the black/grey) wiped all the Huawei mess, killed all unnecessary mem eaters and I am quite happy with stock firmware. BUT!
For some reason, no custom recovery will save my settings! Any time I access it, it always asks me for making the system writeable, my time zone, my display & vibro settings, etc., all is always reset to some default. I tried different TWRPs, I even fully wiped the rooted phone to factory defaults, formated Dalwik, Data, Cache, even internal SD (did not dare to format the other partitions since I dont know what would that do...). Well, I wiped it, rebooted to TWRP, set all things as I want them and powered off the device. Then powered on into TWRP and again, TWRP is in default... W T F...?
So, how to make the custom recovery to save my settings, please?
Click to expand...
Click to collapse
It's because TWRP saves settings to internal storage by default, and since you're probably encrypted (and your twrp can't decrypt) it won't save settings.
You can fix it by unpacking your twrp image using Android Image Kitchen, go to the ramdisk/etc/ folder and open recovery.fstab in Notepad ++.
Here you have a few choices.
I used to add settingsstorage to /cache but the downside is that it will remove settings when you clear /cache.
You can add it directly to /data instead, as the root of /data is not encrypted.
So basically you'd change
flags=display="data";backup=1
To
flags=display="data";settingsstorage;backup=1
Or you can add it to /product, /odm, /cust.
Wow! Thanks for advice! I Will surely try that! But I dont think I encryped the phone, I ll check that out and let you know. Thank you anyway! See, I am more Windoez BSODed rather than Linux freed... But I know the kichen and Notepad++ is my default text editorSo I am really thankful for any help. Cheeerzz, man!
Hallo again!
Bellow is all the content of my recovery.fstab:
/boot emmc /dev/block/bootdevice/by-name/boot
/cache ext4 /dev/block/bootdevice/by-name/cache
/cust ext4 /dev/block/bootdevice/by-name/cust flags=display="Cust";wipeingui;backup=1
/cust_image emmc /dev/block/bootdevice/by-name/cust flags=display="Cust Image";flashimg=1;backup=1
/data f2fs /dev/block/bootdevice/by-name/userdata
/misc emmc /dev/block/bootdevice/by-name/misc flags=display="Misc";backup=0
/product ext4 /dev/block/bootdevice/by-name/product flags=display="Product";backup=1
/product_image emmc /dev/block/bootdevice/by-name/product flags=display="Product Image";flashimg=1;backup=1
/recovery emmc /dev/block/bootdevice/by-name/recovery
/recovery2 emmc /dev/block/bootdevice/by-name/recovery2 flags=display="Recovery2";backup=1;flashimg=1
/system ext4 /dev/block/bootdevice/by-name/system
/vendor_image emmc /dev/block/bootdevice/by-name/vendor flags=display="Vendor Image";flashimg=1backup=1
/vendor ext4 /dev/block/bootdevice/by-name/vendor flags=display="Vendor";backup=1
/version_image emmc /dev/block/bootdevice/by-name/version flags=display="Version Image";flashimg=1;backup=1
/version ext4 /dev/block/bootdevice/by-name/version flags=display="Version";backup=1
/external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="MicroSD Card";storage;wipeingui;removable
/usbotg auto /dev/block/sda1 /dev/block/sda flags=display="USB OTG";storage;removable;backup=0
And there is no flags by /data. Here is what I did! I extended the line:
"/data f2fs /dev/block/bootdevice/by-name/userdata"
to
"/data f2fs /dev/block/bootdevice/by-name/userdata flags=display="data";settingsstorage;backup=1"
without quotes of course, but that did not work and after flashing the modded recovery and couple changes made in settings and restart, it still goes back to default
2 questions here: A) what if I simply mod the default settings to fit within my needs? B) How and where? Little quick guide would be appreciated ;o)))
A btw., I know my phone is not crypted. It seems like it would only allow to encrypt and external microSD card.
Cheers ;o)))
Hallo again!
Bellow is all the content of my recovery.fstab:
/boot emmc /dev/block/bootdevice/by-name/boot
/cache ext4 /dev/block/bootdevice/by-name/cache
/cust ext4 /dev/block/bootdevice/by-name/cust flags=display="Cust";wipeingui;backup=1
/cust_image emmc /dev/block/bootdevice/by-name/cust flags=display="Cust Image";flashimg=1;backup=1
/data f2fs /dev/block/bootdevice/by-name/userdata
/misc emmc /dev/block/bootdevice/by-name/misc flags=display="Misc";backup=0
/product ext4 /dev/block/bootdevice/by-name/product flags=display="Product";backup=1
/product_image emmc /dev/block/bootdevice/by-name/product flags=display="Product Image";flashimg=1;backup=1
/recovery emmc /dev/block/bootdevice/by-name/recovery
/recovery2 emmc /dev/block/bootdevice/by-name/recovery2 flags=display="Recovery2";backup=1;flashimg=1
/system ext4 /dev/block/bootdevice/by-name/system
/vendor_image emmc /dev/block/bootdevice/by-name/vendor flags=display="Vendor Image";flashimg=1backup=1
/vendor ext4 /dev/block/bootdevice/by-name/vendor flags=display="Vendor";backup=1
/version_image emmc /dev/block/bootdevice/by-name/version flags=display="Version Image";flashimg=1;backup=1
/version ext4 /dev/block/bootdevice/by-name/version flags=display="Version";backup=1
/external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="MicroSD Card";storage;wipeingui;removable
/usbotg auto /dev/block/sda1 /dev/block/sda flags=display="USB OTG";storage;removable;backup=0
And there is no flags by /data. Here is what I did! I extended the line:
"/data f2fs /dev/block/bootdevice/by-name/userdata"
to
"/data f2fs /dev/block/bootdevice/by-name/userdata flags=display="data";settingsstorage;backup=1"
without quotes of course, but that did not work and after flashing the modded recovery and couple changes made in settings and restart, it still goes back to default
2 questions here: A) what if I simply mod the default settings to fit within my needs? B) How and where? Little quick guide would be appreciated ;o)))
A btw., I know my phone is not crypted. It seems like it would only allow to encrypt and external microSD card.
Cheers ;o)))
Hello!
I googled that command settingsstorage a bit and it seemed to me like i mistyped it. It shall be "settings storage" not "settingsstorage", it should have contain a space between them 2 words. So I rewrote it, repacked, flashed it... but it did not work either. I am still trying to save the settings on DATA partatition. I will try other partition as well. I let you know.
Bye
Hallo!
Well I am very confused... I left the idea of being able to save the settings for any custom recovery within Android 7.0 and moved forward to Android 8 Oreo, thinking the new Andy will perform better that the old one. I have fully unlocked phone (RNE-L21C432). I was able to flash the oreo-dediacated TWRP then I struggled a bit with Huawei Firmware Finder for Windows and flashing it with the hwOTA tool. For some time, during the flashing, I recognized that the TWRP 3.2.1-0 from Catuva21 hold the settings. But after flashing the firmware files and couple of restarts, the recovery again always started in the default condition.
But what is even worse is the fact that the phone is soo damn slow with the Oreo ROM!! I rooted it with Magisk 16 succesfully, removed a lot of bloatware and services that I do not necessarilly need but still, for example the response for fingerprint unlock is soooo damn slow! It takes about 6-8secs. to unlock and lod the home screen fully. It took about 1-2 secs. in Android 7.0/MIUI5.1. DO NOT UPGRADE TO 8.0!!!
And another strange thing is that even that I downloaded the latest RNE-LE21C432CUSTC432 8.0.0.330 firmware from early June 2018 and flashed it successfully, I still only see 8.0.0.046(0BYF) in my device info tab. I cant even move to 8.0.0.304 that is also downloadable. I followed the guide here https://forum.xda-developers.com/ma...development/hwota-huawei-mate10-lite-t3777115
and I think if I repete the procedure with the latest files for my phone I should be fine and fully up to date, but no.... I wish I never moved to Oreo...ever!!!
Gang-star said:
Hallo again!
Bellow is all the content of my recovery.fstab:
/boot emmc /dev/block/bootdevice/by-name/boot
/cache ext4 /dev/block/bootdevice/by-name/cache
/cust ext4 /dev/block/bootdevice/by-name/cust flags=display="Cust";wipeingui;backup=1
/cust_image emmc /dev/block/bootdevice/by-name/cust flags=display="Cust Image";flashimg=1;backup=1
/data f2fs /dev/block/bootdevice/by-name/userdata
/misc emmc /dev/block/bootdevice/by-name/misc flags=display="Misc";backup=0
/product ext4 /dev/block/bootdevice/by-name/product flags=display="Product";backup=1
/product_image emmc /dev/block/bootdevice/by-name/product flags=display="Product Image";flashimg=1;backup=1
/recovery emmc /dev/block/bootdevice/by-name/recovery
/recovery2 emmc /dev/block/bootdevice/by-name/recovery2 flags=display="Recovery2";backup=1;flashimg=1
/system ext4 /dev/block/bootdevice/by-name/system
/vendor_image emmc /dev/block/bootdevice/by-name/vendor flags=display="Vendor Image";flashimg=1backup=1
/vendor ext4 /dev/block/bootdevice/by-name/vendor flags=display="Vendor";backup=1
/version_image emmc /dev/block/bootdevice/by-name/version flags=display="Version Image";flashimg=1;backup=1
/version ext4 /dev/block/bootdevice/by-name/version flags=display="Version";backup=1
/external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="MicroSD Card";storage;wipeingui;removable
/usbotg auto /dev/block/sda1 /dev/block/sda flags=display="USB OTG";storage;removable;backup=0
And there is no flags by /data. Here is what I did! I extended the line:
"/data f2fs /dev/block/bootdevice/by-name/userdata"
to
"/data f2fs /dev/block/bootdevice/by-name/userdata flags=display="data";settingsstorage;backup=1"
without quotes of course, but that did not work and after flashing the modded recovery and couple changes made in settings and restart, it still goes back to default
2 questions here: A) what if I simply mod the default settings to fit within my needs? B) How and where? Little quick guide would be appreciated ;o)))
A btw., I know my phone is not crypted. It seems like it would only allow to encrypt and external microSD card.
Cheers ;o)))
Click to expand...
Click to collapse
Gang-star said:
Hallo!
Well I am very confused... I left the idea of being able to save the settings for any custom recovery within Android 7.0 and moved forward to Android 8 Oreo, thinking the new Andy will perform better that the old one. I have fully unlocked phone (RNE-L21C432). I was able to flash the oreo-dediacated TWRP then I struggled a bit with Huawei Firmware Finder for Windows and flashing it with the hwOTA tool. For some time, during the flashing, I recognized that the TWRP 3.2.1-0 from Catuva21 hold the settings. But after flashing the firmware files and couple of restarts, the recovery again always started in the default condition.
But what is even worse is the fact that the phone is soo damn slow with the Oreo ROM!! I rooted it with Magisk 16 succesfully, removed a lot of bloatware and services that I do not necessarilly need but still, for example the response for fingerprint unlock is soooo damn slow! It takes about 6-8secs. to unlock and lod the home screen fully. It took about 1-2 secs. in Android 7.0/MIUI5.1. DO NOT UPGRADE TO 8.0!!!
And another strange thing is that even that I downloaded the latest RNE-LE21C432CUSTC432 8.0.0.330 firmware from early June 2018 and flashed it successfully, I still only see 8.0.0.046(0BYF) in my device info tab. I cant even move to 8.0.0.304 that is also downloadable. I followed the guide here https://forum.xda-developers.com/ma...development/hwota-huawei-mate10-lite-t3777115
and I think if I repete the procedure with the latest files for my phone I should be fine and fully up to date, but no.... I wish I never moved to Oreo...ever!!!
Click to expand...
Click to collapse
If you had quoted or mentioned me I would've seen this earlier.
Anyway, "settingsstorage" without a space is correct.
Huawei use fileencryption as default for both Nougat and Oreo so unless you removed encryption it will still be there.
To remove it you would have to edit fstab in boot (Nougat) or /vendor/etc (Oreo), then Format Data in TWRP.
I would suggest adding it to /cache instead if it doesn't want to work.
You should be able to downgrade back to Nougat.
ante0 said:
If you had quoted or mentioned me I would've seen this earlier.
Anyway, "settingsstorage" without a space is correct.
Huawei use fileencryption as default for both Nougat and Oreo so unless you removed encryption it will still be there.
To remove it you would have to edit fstab in boot (Nougat) or /vendor/etc (Oreo), then Format Data in TWRP.
I would suggest adding it to /cache instead if it doesn't want to work.
You should be able to downgrade back to Nougat.
Click to expand...
Click to collapse
Hallo!
Thank you for your time and advise. I am now on a family vacation and I am not going to mess with my phone here. I but I am definitely considered to revert back to Nougat. I already read some articles and guides about how to do that. But first I want to bring all the vacation records home and only then format the storage and revert. I let you know, if you wouldn't mind and eventually ask for help if I get stuck. Thanks again!
Regards, Gang-star
When i was uploading new rom, partitions connect to one. Many roms have a problems with this. Second partition has a 0MB size. I try upload stock rom by flashtool and no results. I want to restore original size. How I can do this? My phone is sony xperia lt30p.
What ROM have you flashed? Have you done a clean install, means having wiped existing Android OS before?
What's the name of the mentioned 0MB partition?
BTW:
Android comes with standard partitons as
/boot
/system
/recovery
/data
/cache
/misc
and their sizes basically are hardcoded.
Never have noticed, heard or read that when a ROM gets flashed a partition with size of 0MB will be created.
Name se
jwoegerbauer said:
What ROM have you flashed? Have you done a clean install, means having wiped existing Android OS before?
What's the name of the mentioned 0MB partition?
BTW:
Android comes with standard partitons as
/boot
/system
/recovery
/data
/cache
/misc
and their sizes basically are hardcoded.
Never have noticed, heard or read that when a ROM gets flashed a partition with size of 0MB will be created.
Click to expand...
Click to collapse
The name second partition is ,,sdcard". Tt isn't sdcard it is internal memory for photos and the like things
jareczex said:
Name se
The name second partition is ,,sdcard". Tt isn't sdcard it is internal memory for photos and the like things
Click to expand...
Click to collapse
Don't confuse /sdard and sdcard.
With regards to /sdcard:
This is NOT a partition on the internal storage memory of the device but rather the ( external ) SD card.
With regards to sdcard:
This simply is a symbolic link to device's /data/media partition what is mounted as /storage/emulated/0
And How i Can restore default memory this partition? Partition with external sdcard has other name.
OK it's the partition named /data/media you're referring to.
If a partitition shows 0MB ( can't get mounted ) then this is because it probably is encrypted. Hence decrypt it. The common method is to perform a Factory Reset. If you've TWRP installed / at your fingertips then decrypting also can be done with TWRP.
This phone is other than many phones
For me, everything you post is crazy stuff: I can not understand what the problem really is.
Since Android is on the market, it has more or less the same partition layout as shown above. And I'm pretty sure your phone has this, too.
I mean about problem, when i am installing rom, show me comunicat ,,Error instaling zip file 'external_sd/android9 sony t/open_gapps-arm-9.0-pico-20201114.zip" and i wanna get rid of this problem, across restore this partition. Do you know, what i have a mean?
My last 2 cents here: Open Gapps isn't a ROM. It's merely a suite of re-compiled Google apps.
FYI: I no longer participate this thread. I hope for you others jump in.
ok, thank you for your help. Information for other people: I can't install apps on this roms, so i want to restore this partition