I am just curious as to which files are cleaned when you format boot and/or system in recovery. I look through the root directory in root explorer "/" and see many files and I was curious if any of them are erased after a boot or system format?
Basically my main question is, if you make any changes to any of these folders can you reset them back by formatting boot and system and then flashing a new clean rom over it?
NicholasQ said:
I am just curious as to which files are cleaned when you format boot and/or system in recovery. I look through the root directory in root explorer "/" and see many files and I was curious if any of them are erased after a boot or system format?
Basically my main question is, if you make any changes to any of these folders can you reset them back by formatting boot and system and then flashing a new clean rom over it?
Click to expand...
Click to collapse
Formatting system.and.boot formats the boot and system partitions. This *erases* them.
System is mounted at /system
Boot contains the kernel, ramdisk, init scripts.
Sent from my Nexus S using xda premium
Related
i wanted to know if it is possible to format our system partition as f2fs and have it work our data partition on kitkat is already f2fs so are we able to do it to system? in twrp i attempted this by fro matting to f2fs but when restoring system it reformats system as ext 4 is there away around this? on twrps website there is a command to keep a the file system it is "tw_rm_rf – uses rm –rf instead of formatting system and data partitions, this option is used to prevent changes to the file system settings such as file system type, " i found it here http://www.teamw.in/twrp2-reference-guide would this help to do this? i don't know where to put this command in though
Edit: on a sidenote i formatted cache as f2fs and it booted
Edit 2: i looked at it again and cache was reformatted back to ext4
billycar11 said:
i wanted to know if it is possible to format our system partition as f2fs and have it work our data partition on kitkat is already f2fs so are we able to do it to system? in twrp i attempted this by fro matting to f2fs but when restoring system it reformats system as ext 4 is there away around this? on twrps website there is a command to keep a the file system it is "tw_rm_rf – uses rm –rf instead of formatting system and data partitions, this option is used to prevent changes to the file system settings such as file system type, " i found it here http://www.teamw.in/twrp2-reference-guide would this help to do this? i don't know where to put this command in though
Edit: on a sidenote i formatted cache as f2fs and it booted
Edit 2: i looked at it again and cache was reformatted back to ext4
Click to expand...
Click to collapse
Did you ever succeed in getting stock "DATA" partition to F2FS? I couldn't restore my backup and phone wouldn't boot anymore.. so went back to EXT4..
Maybe @djvita knows something, I think he has been experimenting a bit with F2FS..
StefanGA said:
Did you ever succeed in getting stock "DATA" partition to F2FS? I couldn't restore my backup and phone wouldn't boot anymore.. so went back to EXT4..
Maybe @djvita knows something, I think he has been experimenting a bit with F2FS..
Click to expand...
Click to collapse
yes i was able to get only the data partition to f2fs no other partition will stay another format once it boots it reformats or when restoring system in twrp it will restore the system partition as ext 4
billycar11 said:
yes i was able to get only the data partition to f2fs no other partition will stay another format once it boots it reformats or when restoring system in twrp it will restore the system partition as ext 4
Click to expand...
Click to collapse
interesting.. how did you do it? I did it in TWRP 2.8.1.0 via advanced wipe and after that got stuck on the motorola bootlogo..
That is the same thing I did but after whipeing I restored my data partition. I think the reason you got stuck in a bootloop is because you did not clear dalvic and cache or you do not have the kit Kat boot loader
billycar11 said:
That is the same thing I did but after whipeing I restored my data partition. I think the reason you got stuck in a bootloop is because you did not clear dalvic and cache or you do not have the kit Kat boot loader
Click to expand...
Click to collapse
I tried it again.. this time it worked.. I rebooted after format directly back into recovery and was then able to restore my data from ext4 to f2fs.. not sure, why it didn't work the first time around, but thanks for checking back!
I have a Galaxy GIO, which is a fairly old low-end phone. On factory reset, I have about 100MB memory free for apps, and the phone seems to start complaining as soon as I hit the 50MB mark; that's about one or 2 installed applications.
Because I would like to actually be able to, well, use my phone for anything else than calling, I want to move the /data partition to my SD card. I know this'll be slow, but slow still is better than not working at all.
I have done a bit of research, and came around plenty of scripts which claim to mount the second partition of the sd card as /data; none of these scripts work. I have tried 'INT2EXT', 'D2EXT', and I've heard about something called 'A2SD' but I have yet to find a copy of it . To install these scripts I've extracted them, and copied the scripts to '/system/etc/init.d/', after mounting '/system', using ADB.
I for an instant thought maybe my second partition isn't formatted properly, but using adb I am able to successfully mount the ext2 partition as /sd-ext, so I don't see why mounting them as /data should be a problem.
I have also tried to symbollicly link /data to /sd-ext/data and automatically mount my /sd-ext on boot. Obviously this didn't work, because the symbolic link isn't actually saved to disk.
How would I go about moving my data partition to my sd card? I am not affraid of doing some dirty work manually. I am running Cyanogenmod 11.
Binero said:
I have a Galaxy GIO, which is a fairly old low-end phone. On factory reset, I have about 100MB memory free for apps, and the phone seems to start complaining as soon as I hit the 50MB mark; that's about one or 2 installed applications.
Because I would like to actually be able to, well, use my phone for anything else than calling, I want to move the /data partition to my SD card. I know this'll be slow, but slow still is better than not working at all.
I have done a bit of research, and came around plenty of scripts which claim to mount the second partition of the sd card as /data; none of these scripts work. I have tried 'INT2EXT', 'D2EXT', and I've heard about something called 'A2SD' but I have yet to find a copy of it . To install these scripts I've extracted them, and copied the scripts to '/system/etc/init.d/', after mounting '/system', using ADB.
I for an instant thought maybe my second partition isn't formatted properly, but using adb I am able to successfully mount the ext2 partition as /sd-ext, so I don't see why mounting them as /data should be a problem.
I have also tried to symbollicly link /data to /sd-ext/data and automatically mount my /sd-ext on boot. Obviously this didn't work, because the symbolic link isn't actually saved to disk.
How would I go about moving my data partition to my sd card? I am not affraid of doing some dirty work manually. I am running Cyanogenmod 11.
Click to expand...
Click to collapse
I will introduce how to COPY(NOT MOVING) /data partition to /sdcard.
1. You should ROOT First.
2. Use Rootexplorer to Copy /data to /sdcard (WARNING:If your sdcard emulated with /data, Data WON'T copy to SDCARD --You need external Sdcard!)
2-1. if you don't want to use RootExplorer, you can use Android Debugging Bridge(adb)
(Youshould download Android sdks from developer.android.com)
--Command : adb shell su -C cp /data /sdcard/data
3. That's all.
Jason Hyunwoo said:
I will introduce how to COPY(NOT MOVING) /data partition to /sdcard.
1. You should ROOT First.
2. Use Rootexplorer to Copy /data to /sdcard (WARNING:If your sdcard emulated with /data, Data WON'T copy to SDCARD --You need external Sdcard!)
2-1. if you don't want to use RootExplorer, you can use Android Debugging Bridge(adb)
(Youshould download Android sdks from developer.android.com)
--Command : adb shell su -C cp /data /sdcard/data
3. That's all.
Click to expand...
Click to collapse
Thanks, but that's not entirely what I meant. I can manage to move my data to the SD card no problem, but I want my phone to actually use my second partition on my sd card, as the /data partition.
Binero said:
Thanks, but that's not entirely what I meant. I can manage to move my data to the SD card no problem, but I want my phone to actually use my second partition on my sd card, as the /data partition.
Click to expand...
Click to collapse
Oops.. Sorry about that!
First, I am not sure that will work or not, maybe you should try to edit init.*.rc. Which is from boot.mg. I think, maybe mounting sdcard as data is impossible, but you may try editing init.rc(or init.*.rc, * is manufacture). You could unpack your boot img, and you could edit mounting point which is from init.rc!
I hope this thing will help you..
Jason Hyunwoo said:
Oops.. Sorry about that!
First, I am not sure that will work or not, maybe you should try to edit init.*.rc. Which is from boot.mg. I think, maybe mounting sdcard as data is impossible, but you may try editing init.rc(or init.*.rc, * is manufacture). You could unpack your boot img, and you could edit mounting point which is from init.rc!
I hope this thing will help you..
Click to expand...
Click to collapse
I have looked into init.rc, but that only seemed to create the /data mountpoint, but not actually mount to it. I've no idea how to edit the boot image, or what that even is. Is that the filesystem that is built into the kernel?
Binero said:
I have looked into init.rc, but that only seemed to create the /data mountpoint, but not actually mount to it. I've no idea how to edit the boot image, or what that even is. Is that the filesystem that is built into the kernel?
Click to expand...
Click to collapse
Umm.. You should download unpackbootimg or dsixda's Android Kitchen to edit boot.mg. You cannot edit init.rc on Root explore. Use unpack boot.img menu which is from Android Kitchen!
Jason Hyunwoo said:
Umm.. You should download unpackbootimg or dsixda's Android Kitchen to edit boot.mg. You cannot edit init.rc on Root explore. Use unpack boot.img menu which is from Android Kitchen!
Click to expand...
Click to collapse
I'll try that out. Still not sure where to look though. As I said, init.rc does not contain any commands mounting /data.
Binero said:
I'll try that out. Still not sure where to look though. As I said, init.rc does not contain any commands mounting /data.
Click to expand...
Click to collapse
or you could edit look at other *.rc files!
Isn't this what you're looking for?
http://forum.xda-developers.com/galaxy-s2/themes-apps/tool-directorybind-data-to-externalsd-t1410262
sndsnd said:
Isn't this what you're looking for?
http://forum.xda-developers.com/galaxy-s2/themes-apps/tool-directorybind-data-to-externalsd-t1410262
Click to expand...
Click to collapse
I want to mount my sd card to my /data. That simply creates a symbolic link.
Jason Hyunwoo said:
or you could edit look at other *.rc files!
Click to expand...
Click to collapse
There is only 2 rc files, and one of them is specific to my recovery image.
In windows, I'd use a partition; in android, are there any folders (like /boot?) that are not deleted after I flash factory images (wiping data obviously)?
I'd like to know this because I have a lot of music, and don't want to have to re-copy it to my phone every time I flash it. (unfortunately N5 does not support sd cards)
My intention was to copy the music to /smth, will it get wiped?
sfs15 said:
In windows, I'd use a partition; in android, are there any folders (like /boot?) that are not deleted after I flash factory images (wiping data obviously)?
I'd like to know this because I have a lot of music, and don't want to have to re-copy it to my phone every time I flash it. (unfortunately N5 does not support sd cards)
My intention was to copy the music to /smth, will it get wiped?
Click to expand...
Click to collapse
There are only 1 partition which has a filesystem and does not get wiped after the factory reset. But it is only a 16 mb partition with a free space of 10 mb. It is mounted as /persist
bitdomo said:
There are only 1 partition which has a filesystem and does not get wiped after the factory reset. But it is only a 16 mb partition with a free space of 10 mb. It is mounted as /persist
Click to expand...
Click to collapse
No way to chance its size? I really need to backup my music somewhere in the phone and not have to copy it back every time!
sfs15 said:
No way to chance its size? I really need to backup my music somewhere in the phone and not have to copy it back every time!
Click to expand...
Click to collapse
There is, but complicated. Because of its location on the emmc you have to edit 6-8 partitions or more. And if there is something which uses the emmc in raw mode and not by the partitions then you could have problems. You will also lose the ability to flash stock rom.
The whole thing is unecessary if you are using twrp recovery and not cwm, because twrp will not fotmat the /data partition. It will just remove every folder and file except the /data/media/0 folder which contains all the files you have on the internal storage.
bitdomo said:
There is, but complicated. Because of its location on the emmc you have to edit 6-8 partitions or more. And if there is something which uses the emmc in raw mode and not by the partitions then you could have problems. You will also lose the ability to flash stock rom.
The whole thing is unecessary if you are using twrp recovery and not cwm, because twrp will not fotmat the /data partition. It will just remove every folder and file except the /data/media/0 folder which contains all the files you have on the internal storage.
Click to expand...
Click to collapse
You mean that if I install twrp recovery and then flash a stock factory image ( or for instance cyanogenmod 12) I won't lose /data/media/0 folder anymore?
sfs15 said:
You mean that if I install twrp recovery and then flash a stock factory image ( or for instance cyanogenmod 12) I won't lose /data/media/0 folder anymore?
Click to expand...
Click to collapse
No.
If you do factory reset in twrp then it will not delete that folder. It will not protrect you if you flash stock rom with fastboot with wipe.
bitdomo said:
No.
If you do factory reset in twrp then it will not delete that folder. It will not protrect you if you flash stock rom with fastboot with wipe.
Click to expand...
Click to collapse
Flashing without wipe will keep my applications and everything, so it's usually just useless ( not worth ); and flashing with wipe will delete any folders. Are you saying there's no way :/
sfs15 said:
Flashing without wipe will keep my applications and everything, so it's usually just useless ( not worth ); and flashing with wipe will delete any folders. Are you saying there's no way :/
Click to expand...
Click to collapse
Listen. If you use TWRP and do WIPE in TWRP it will not delete /data/media/0 folder. So with twrp you can flash roms with wipes without worrying to lose your music and pictures.
If you flash stock rom with fastoot you lose everything.
If you flash rom with wipe in cwm you lose everything.
bitdomo said:
Listen. If you use TWRP and do WIPE in TWRP it will not delete /data/media/0 folder. So with twrp you can flash roms with wipes without worrying to lose your music and pictures.
If you flash stock rom with fastoot you lose everything.
If you flash rom with wipe in cwm you lose everything.
Click to expand...
Click to collapse
Nice! This is very useful, I didn't know it was possible to flash factory images through a recovery; so I'll just have to move my music there and it'll stay forever. Just asking now, what will happen to the recovery (which should be stored in /recovery?) if I flash with fastboot, will it get wiped aswell? Thank you so much for your answers
sfs15 said:
Nice! This is very useful, I didn't know it was possible to flash factory images through a recovery; so I'll just have to move my music there and it'll stay forever. Just asking now, what will happen to the recovery (which should be stored in /recovery?) if I flash with fastboot, will it get wiped aswell? Thank you so much for your answers
Click to expand...
Click to collapse
That /data/media/0 folder is the folder of the internal storage. So your music is already there. To flash stock rom in twrp recovery you will need a flashable zip version of the stock rom. These does not contains recovery image so twrp will persist.
You cant flash stock rom from google's site in twrp.
bitdomo said:
That /data/media/0 folder is the folder of the internal storage. So your music is already there. To flash stock rom in twrp recovery you will need a flashable zip version of the stock rom. These does not contains recovery image so twrp will persist.
You cant flash stock rom from google's site in twrp.
Click to expand...
Click to collapse
Ah well it's not a solution then.. The /recovery folder gets wiped with fastboot -w?
sfs15 said:
Ah well it's not a solution then.. The /recovery folder gets wiped with fastboot -w?
Click to expand...
Click to collapse
Its complicated. That recovery folder if it exists, on stock roms there arent any folder called recovery, is a temporary folder. It is extracted from the kernel's ramdisk. As the its name says it is a ramdisk so if you turn off your phone it is gone and all its content.
Get a stock rom in a flashable zip. Do a wipe in twrp and flash the stock rom.
bitdomo said:
Its complicated. That recovery folder if it exists, on stock roms there arent any folder called recovery, is a temporary folder. It is extracted from the kernel's ramdisk. As the its name says it is a ramdisk so if you turn off your phone it is gone and all its content.
Get a stock rom in a flashable zip. Do a wipe in twrp and flash the stock rom.
Click to expand...
Click to collapse
Yeah, I think I'll do so, thanks a lot
Hello to everyone. Can anyone inform me about:
1. the exact commands in order to wipe all android partitions except /misc (/boot, /data, /cache, /recovery, /system).
2. the exact commands in order to flash two zip files (1. custom rom, 2. kernel)
3. is there anyway i can merge two android partitions specifically data with recovery because i don't want to use it anymore?
4. what exists after wiping a partition (unallocated space or allocated space)??
My device is HTC desire X UNLOCKED.
My purpose is to perform a clean install without using any custom recovery like TWRP or CWM.
Must have recovery
Got wipe then to advanced and click the box for cache do the wipe
Then go to install find your rom install it then find your kernel and install that then reboot
Kjssplass said:
Hello to everyone. Can anyone inform me about:
1. the exact commands in order to wipe all android partitions except /misc (/boot, /data, /cache, /recovery, /system).
2. the exact commands in order to flash two zip files (1. custom rom, 2. kernel)
3. is there anyway i can merge two android partitions specifically data with recovery because i don't want to use it anymore?
4. what exists after wiping a partition (unallocated space or allocated space)??
My device is HTC desire X UNLOCKED.
My purpose is to perform a clean install without using any custom recovery like TWRP or CWM.
Click to expand...
Click to collapse
1. You need a custom recovery.
2. You need a custom recovery.
3. If you need the data from them just copy and paste them. Not only is it not possible without compiling Android, but it is not useful.
4. Since wiping is usualy done with mkfs (or even rm -rf) allocated space will be made.
Does Format Data in twrp wipe the system partition or will I be fine to format data from twrp? I'm wanting to do this because I've read that doing this will remove encryption
Newrooter22 said:
Does Format Data in twrp wipe the system partition or will I be fine to format data from twrp? I'm wanting to do this because I've read that doing this will remove encryption
Click to expand...
Click to collapse
It only wipes /data.
Though, if you use TWRP by Pretoriano80 there's no point as that has decryption.
If you still want to continue you need to Format Data, 'reboot recovery', then remove fileencryption flag in /vendor/etc/fstab.hi3660. (you can pull this file using adb, edit on computer then push it back using adb.).
If you don't edit fstab your phone will re-encrypt on next boot to system.
You will also have to flash Public and HW zip for your firmware as these will be gone (system update ability and themes are stuff that will be gone if you don't flash these.)