I want to see the list of partitions
And I want to create a new partition
How do I do this?
In fact, I do not have the partition erecovery or recovery2
Thank you my friends
I also wanted to know, there is nothing on the net, talking about it, this would be the help for all models that n have twrp. and it shouldn't be difficult.
Related
Hey,
I'm generally new to the Android platform.
I got some hands on with simple guided procedures like rooting and flashing ROMs and updates.
I just wanted to get a better picture of how recovery works --
Where does the recovery sit? Is it on a different partition in the phone's internal storage?
Does booting into recovery actually mean that we're instructing the boot-loader to boot from a different partition rather than booting from the OS partition?
When using custom recovery images, do we actually override the phone's original recovery or is it loaded from a separate location (such as the SD card)?
By the way, if anyone knows some good resources where I can read more about the structure of the OS, it would be much appreciated.
Thanks!
good morning. please, the sdcard missing is a problem for we that want play with roms.... every time we have to save to pc before wipping.... is there a way for create a partition unformattable when we wipe for installing a new rom? where i can find something about? thanks
is there this possibility even with modded rom? every time you flash, have to reinstall all things from folder external?
In theory you should change gpt.bin inside firmware to change partitons memory scheme.
Edit: Nevermind
guys dose anyone knows the what is the data & cacsh type for mount is (fat ) or (exfat4 ) or exfat3 or what
i have install custom rom Lineage and stuck at boot animation for long time ......
so anyone have an idea how to make it work Plz help me
The data partition is F2FS.
It's filing system
And there is no need to ask something with language like this "help meeee"
If u want help, u should make ur subject more respectively because this is international forum.
Next time be carefull.
Thanks.
22trika said:
guys dose anyone knows the what is the data & cacsh type for mount is (fat ) or (exfat4 ) or exfat3 or what
i have install custom rom Lineage and stuck at boot animation for long time ......
so anyone have an idea how to make it work Plz help me
Click to expand...
Click to collapse
Data and cache to my knowledge are ext4... not fat.
There is no exfat4 or exfat3, you are extrapolating it incorrectly... there is exFat, Fat12, Fat16, and Fat32 (plus a few others that are of minor importance) that are collectively referred to as "fat" file systems and these are MS-DOS or Windows file system types. The file systems types ext2, ext3, ext4, XFS, JFS, ReiserFS, ZFS, and F2FS are all Linux file system types. These file system types fit into a partition type of MBR (MS-Dos Master Boot Record) or GPT (GUID Partition Table) with the later being used by Android.
None of that has any direct relation I can see to your problem of Lineage not working. What device, ROM, recovery, and process did you use? Did you clean flash? What Gapps? How long did you wait (first boot can exceed 20 minutes)?
You really are not giving us ANYTHING to go on here, just throwing out random questions that are most likely unrelated to your problem.
riggerman0421 said:
The data partition is F2FS.
Click to expand...
Click to collapse
and what about system and cache !!!
Cache is part of the data partition IIRC, the system should be ext 4.
help!!!
im having moto g3 xt1550 ... i had done lineage and custom recovery aslo rooted and bootloader unlocked but , for volte i mistakely installed miui 7.1.3
now the phone is dead (bricked) im tried all the ways to get into recovery but its not happening the screen is still black all!!!
please help me and thanks in advance !!!
the solution i need is to just enter the boot menu or recovery !!! :cyclops::cyclops::cyclops:
This is just an idea. I tried it on my Nokia 6.1 (2018) (PL2) running Android 10, and it worked; so I thought it might work on other devices too. My device:
Android 10 Q
System-as-root
A/B slots
Released with Project Treble support (and hence has the fstab in the vendor partition)
DM-verity, force-encryption and disk quota disabled with this mod by Zackptg5.
It basically uses a single partition to store the contents of what I call two different userdata "profiles". Normally, you have one userdata partition on a device, and that stores one profile. Here, however, I used a subdirectory on the root of the userdata partition to store the contents of the second profile, and modified the fstab to correctly bind-mount it on /data. Bind-mounting made things simple in my opinion--I didn't have to go about actually repartitioning my storage. The reason this works is that any changes you make to your phone on the lines of installing and updating apps, downloading files, changing settings, etc. are all reflected only on the userdata partition. No other partition on an android phone is ever touched unless the system is updated. Hence, the userdata partition is the only partition you need to mess around with in order to have two profiles.
===================================​DISCLAIMER:
I am NOT sharing a solution. I am only sharing an idea for you to try and/or improvise on. It may work, it may not. I will not hold your hand; you will have to use your own knowledge and common sense. I am not responsible for anything that goes wrong on your device.
If you do not understand what is going on in this post, please do not try this.
There is a reason I'm not explaining all the terms I'm using here. I assume that if you, the reader, want to try this out, you a) have some knowledge and experience, and b) have the fire in your belly to research to learn more about what you don't understand.
===================================​
Now for the fun:
The first thing I did was to create a new mountpoint the userdata partition. This I made on what is the root filesystem of the device; on a system-as-root device, it would be on the root of the system partition, and on a non-system-as-root device, it would be on the root of the boot ramdisk. I named it userdata/. Accordingly, I edited my fstab.qcom (at etc/fstab.qcom on the vendor partition for my device) to mount the userdata partition on /userdata/ instead of /data/:
Code:
#<device> <mountpoint> <type> <options>
/dev/block/bootdevice/by-name/userdata /userdata <whatever whatever whatever> <you'd probably have to disable options like fileencryption, quota, check (verification), etc.>
and to mount the second profile's directory. Note that it is bind-mounted:
Code:
/userdata/userdata/ /data none bind
Now to switch between the two profiles, you'd switch between the original fstab and the one you just modified.
That is (most of) it. Some things I noticed:
The device would refuse to boot initially. What worked was to backup and wipe my data, boot, create the second profile's directory and copy the contents of the just-created userdata profile into the second profile's directory. In other words, I couldn't run a "first boot" on the second data profile--I had to copy an existing profile into the second profile. I really don't know why this happens.
I suspect that disk quota, filesystem encryption and verification will mess with this (or rather, the other way around). I can't be sure, because I have all three disabled.
Having a shared Internal Storage (/data/media/0/) is convenient. For this, I just bind-mounted that too:
Code:
/userdata/media/0/ /data/media/0/ none bind
This can also be used to easily achieve dual booting on an A/B device, as long as you don't use seamless updates. One ROM per slot can be installed, and the fstab.qcom on one of the vendor partitions can be configured to use the second profile. This way, there would be no need for an external SD card or additional partitions.
I'm pretty sure there will be other hurdles with other devices and other android versions. As I said, I'm just here to share an IDEA, and NOT a foolproof, one-size-fits-all solution. I hope this helps other people make their lives simpler. Please do share your notes on this thread if you manage to get it working on your device!
Its easy to have two roms on one device and its simple,just take a nandroid aof your current rum,now flash another rom an set it up,when u need the other rom just restore your nandroid and so on,i have 4 roms,all fine,lol.
But that's kinda inefficient, don't you think? If you just swap a single file instead of the whole data partition, it's much faster--it takes as long as rebooting + a few milliseconds.
But well, whatever suits you
Hey bro can u pls explain the second code line u mentioned???
varunrocks17 said:
Hey bro can u pls explain the second code line u mentioned???
Click to expand...
Click to collapse
/userdata/userdata/ /data none bind: (this is the line right?)
This bind-mounts the directory /userdata/userdata on /data. /userdata/userdata (directory /userdata under the userdata partition that we previously mounted) is the directory under which the contents of the alternative userdata partition are stored.
Bind-mounting is a means by which a folder can be treated as a device to mount (as opposed to a normal block device or partition). As the mount(8) documentation states, it is a way to "Remount part of the file hierarchy somewhere else."
By this mechanism, the /userdata/userdata folder is made to look like the entire userdata partition. In other words, when you access anything under /data/, you're in fact accessing /userdata/userdata/.
I did something similar to a Jellybean. That is, quite long time ago. Stock fw didn't support encryption. So I made a hack that used cryptsetup and vold.decrypt triggers. That way only framework had to restart. It probably is not that simple anymore...
Anyways, what I learned that it wasn't worth it, so I didn't release it back then. Back then there was a real space shortage and it wasn't wasted like nowadays....
Thanks for that userdata idea that's what I was messing around and. Creating multiple partitions for each rom ...
Btw one question :
Kernel intially mounts vendor then from vendor/etc/fstab.qcom all others are mounted ..?
Or kernel have the predefined vendor system and userdata partition locations ..??
I am really confused here ..
That's why my multi boot was bit messy..
aryankaran said:
Thanks for that userdata idea that's what I was messing around and. Creating multiple partitions for each rom ...
Click to expand...
Click to collapse
Glad I could help
aryankaran said:
Kernel intially mounts vendor then from vendor/etc/fstab.qcom all others are mounted ..?
Or kernel have the predefined vendor system and userdata partition locations ..??
Click to expand...
Click to collapse
On my system-as-root device treble-enabled device, the vendor partition is mounted by the kernel. There is a node in the kernel's device tree blob (dtb) that specifies the vendor mount. When the kernel is fully initialized, it has its own /dev filesystem, using which it mounts the vendor partition. I hope that part is clear.... not sure if I explained it nicely...
Once the vendor is mounted, /vendor/etc/fstab.qcom is read and all the other partitions are mounted from there.
Ok it means it's just the same scenario as it was till Android 7.1.2 that boot image mounts all partitions..
Just difference that kernel now mounts vendor and further processed by fstab ..
Ok guys. I use custom ROM for a while know and I did some mistake that sometime I can fix sometime I can't.
Today I messed with backups and I need help.
I did a full backup using adb directly on my laptop (TWRP recovery).
I tried to restore it using adb restore backup comand line. It didn't worked, why memory got filed up, the phone wouldn't boot, neither on recovery or normal.
I succesfully managed to flash back TWRP using odin, and from there I flashed lineageOS and get my phone to boot.
Evrything was fine but... my external SD isn't regognize anymore, neither by lineage nor TWRP. It just didn't show anywhere, and when I try to mount it in TWRP, the box isn't checkable.
The card is fine, I've tested it on my laptop and on another phone.
So it's either a hardware issue and my phone is broken and it's OK I guess.
Or it's a software issue, and my restoring messed up something, a partition that I'm not aware of, that handles the sd card.
So my question is : what can I try to fix my problem ? And on a larger issue, what are exactly the different partitions on a S7 hardrive, what are their purpose, How can I restore them to their initial state ? How do I identify partition in TWRP ? In Odin ? In Heimdall (I'm a linux user) ? I know that there's something called MoDem, or EFS ? Can someone explain those or point me to a class that explain this ?
No harddrive. The EFS partition is especially important, it contains your phone's unique radio information such as your IMEI. Backup it as soon as possible, if you were to have a rainy day you will thank the stars you made that backup. You could try printing the partition table on ADB shell with gdisk and investigating it.
Wattsensi said:
No harddrive. The EFS partition is especially important, it contains your phone's unique radio information such as your IMEI. Backup it as soon as possible, if you were to have a rainy day you will thank the stars you made that backup. You could try printing the partition table on ADB shell with gdisk and investigating it.
Click to expand...
Click to collapse
df comand line and cat /proc/partition returns this. Can't say if it's right
Using gdisk on /dev/block/mmcblk0 you can print the exact GPT table in a human readable form :^)