Should I mount system In order to format system in cmw? And what if I just formatted system without mounting?
Sent from my SM-T210R using Tapatalk
Ripshock said:
Should I mount system In order to format system in cmw? And what if I just formatted system without mounting?
Sent from my SM-T210R using Tapatalk
Click to expand...
Click to collapse
You shouldn't need to do it manually, it should mount it for you.
Sent from my SCH-I605
gr8nole said:
You shouldn't need to do it manually, it should mount it for you.
Sent from my SCH-I605
Click to expand...
Click to collapse
I know that if I mount system, it allows me to access system files and edit them but what about mount data?
Sent from my SM-T210R using Tapatalk
Ripshock said:
I know that if I mount system, it allows me to access system files and edit them but what about mount data?
Sent from my SM-T210R using Tapatalk
Click to expand...
Click to collapse
/data doesn't usually get mounted on recovery boot. Most update scripts contain a line about mounting each partition that it needs to modify. You won't normally need to mount anything manually if you are simply using the "wipe" or "format" commands built into the recovery.
gr8nole said:
/data doesn't usually get mounted on recovery boot. Most update scripts contain a line about mounting each partition that it needs to modify. You won't normally need to mount anything manually if you are simply using the "wipe" or "format" commands built into the recovery.
Click to expand...
Click to collapse
What if I just format data and cache in cwm via updater-script without mounting said partitions after the format command? Would it cause any problems? I just want to automate everything in the zip file and I'm only flashing system partition.
iZLeeP said:
What if I just format data and cache in cwm via updater-script without mounting said partitions after the format command? Would it cause any problems? I just want to automate everything in the zip file and I'm only flashing system partition.
Click to expand...
Click to collapse
You need to mount system so you can do whatever you want with it
Sent from my SM-T210R using Tapatalk
Ripshock said:
You need to mount system so you can do whatever you want with it
Sent from my SM-T210R using Tapatalk
Click to expand...
Click to collapse
Yup, that's what I do.
1. Format system, cache, and data
2. Mount system
3. Extract system package
Never had problems with this order. What I want to confirm is if there is a need to mount cache and data after the format command even though the rom package is only for the system partition?
iZLeeP said:
Yup, that's what I do.
1. Format system, cache, and data
2. Mount system
3. Extract system package
Never had problems with this order. What I want to confirm is if there is a need to mount cache and data after the format command even though the rom package is only for the system partition?
Click to expand...
Click to collapse
Just unmount system after everything
Sent from my SM-T210R using Tapatalk
And i think that mounting system means mounting everything else because i never saw in a script mount /data nor /cache
Sent from my SM-T210R using Tapatalk
Ripshock said:
And i think that mounting system means mounting everything else because i never saw in a script mount /data nor /cache
Sent from my SM-T210R using Tapatalk
Click to expand...
Click to collapse
No, it's different! The mount system in updater-script refers to the partition where /system is located. Cache and data partitions are separate from the system partition. So, if you want to flash something to data partition (e.g., apps, etc.) you have to mount it aside from that of the system partition.
iZLeeP said:
No, it's different! The mount system in updater-script refers to the partition where /system is located. Cache and data partitions are separate from the system partition. So, if you want to flash something to data partition (e.g., apps, etc.) you have to mount it aside from that of the system partition.
Click to expand...
Click to collapse
Oh, thank you, you changrd my thinking 360 degree
Sent from my SM-T210R using Tapatalk
Related
Noob question... What will happen when I format system. What will I lose and keep. Will my internal storage get lost? And will I have to push new rom back to phone via usb transfer. I do understand wiping data, both caches, and system, but what does formatting system do.?
Sent from my Galaxy Nexus using xda app-developers app
Your ROM is installed on /system. If you wipe system you wipe the os. It doesn't touch the data or internal storage.
Sent from my Galaxy Nexus
Yes,you have to push new rom back to phone via usb transfer!
MrLifeguard said:
Yes,you have to push new rom back to phone via usb transfer!
Click to expand...
Click to collapse
no. no you dont.
wiping /system just erases the /system partition.
Thanx guys... I think I'm good. System wipe/format system will not erase data. But a data format wipe you lose everything. That's what I thought but wanted to double check so I didn't lose important data.
Sent from my Galaxy Nexus using xda app-developers app
hello.i just recently softbricked my sgh t999l ( samsung galaxy s3 t-mobile). my problem is that it cant mount my internal sd card. it wont wipe dalvik cache or data cach or factory data reset.it just says
--wiping data...
formatting /data...
error mounting /data!
skipping format...
formatting /cache..
formatting /sd-ext...
formatting /sdcard/.android_secure...
error mounting /sdcard/ .android_secure...
skipping format.....
data wipe complete...
I dont know what to do at this point.i tried flashing it to stock rom atleast 4 times. this incedent started after i did a wiping user data using the standard stock android recovery. yes i kno that wasnt smart.two days ago i didnt know what odin was.now i know it pretty well and i know if i could do this right if i had a second chance.all i wanted to do was to do a data reset.my phone was getting slow so i had to.
plzzzzz someone help me im going through withdrawal here XD
Have you tried to Odin it to stock?
Sent from my SGH-T999 using Tapatalk
serio22 said:
Have you tried to Odin it to stock?
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
yes i did.
And what was the error message?
Sent from my SGH-T999 using Tapatalk
serio22 said:
And what was the error message?
Sent from my SGH-T999 using Tapatalk[/QUOTE
E:error /can't mount /sdcard
when i try to install from zip from sdcard (internal)
and when i go to mounts and storage, it doesnt let me mount /data or mount /sdcard
it says error mounting /sdcard! and error mounting /data!
Click to expand...
Click to collapse
What? You flash tar files with Odin not zips, and are you using the PC version?
Sent from my SGH-M919 using Tapatalk
Did anyone ever find a solution to this problem. I'm having the same issue after doing a soft reset through the settings menu. Through Philz touch recovery wiping dalvik cache does not work and same error messages you receive come up when trying to wipe user data/factory reset through recovery. This is becoming really frustrating because I know there is a fix I just can't find it anywhere. Please help!!!!!!!
You need to debrick image and reflash/fix the corrupt partition on your phone. Go to the following thread. .http://forum.xda-developers.com/gal...a-unbrick-t-mobile-s-iii-qhsusbdload-t2904318 and if you follow exactly, down to the millisecond, as instructed, you will succeed, that is assuming your device is still able initiate into "download." mode and MOST IMPORTANTLY, you have your device specific debrick image. . If and when your device does succumb and is back online, give your utmost thanks to docholiday77.
Sent from my LGMS323 using XDA Free mobile app
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
Okay so today I tried to flash Inspirekat v2.1 rom on my galaxy tab 3 via latest TWRP, and after I wipe system, data, dalvik cache and cache I reboot into the system and I can't get passed the samsung galaxy tab 3 splash screen after some time I found out that the problem is the unability to mount the /system file, then I tried CWM and still the same thing.
Unfortunately I didn't make a backup because I didn't have any precious data there so I just thought I would skip that, I've also tried formatting all data on internal storage but with no avail...could anyone light up a candle for me?
shokolata said:
Okay so today I tried to flash Inspirekat v2.1 rom on my galaxy tab 3 via latest TWRP, and after I wipe system, data, dalvik cache and cache I reboot into the system and I can't get passed the samsung galaxy tab 3 splash screen after some time I found out that the problem is the unability to mount the /system file, then I tried CWM and still the same thing.
Unfortunately I didn't make a backup because I didn't have any precious data there so I just thought I would skip that, I've also tried formatting all data on internal storage but with no avail...could anyone light up a candle for me?
Click to expand...
Click to collapse
If you wiped "system" after you flashed, then you no longer have a rom installed. Re-flash the rom.
Sent from my SM-G920V using Tapatalk
gr8nole said:
If you wiped "system" after you flashed, then you no longer have a rom installed. Re-flash the rom.
Sent from my SM-G920V using Tapatalk
Click to expand...
Click to collapse
Sorry I messed it up a bit in my previous post, I didn't wipe system "after" I flash but before I flashed
Every time I try to flash it just takes a minute then I reboot into the system; same thing happens then I get back into recovery to see that the /system is unmounted and can't be mounted back also when I try "repair partition" it shows that only 54mb of /system partition is used and around 1300mb is free, any insight on that?
Some errors about not being able to read storage file context and can't find path to /sdcard also appear sometimes on the log window or however it's called at the top right.
shokolata said:
Sorry I messed it up a bit in my previous post, I didn't wipe system "after" I flash but before I flashed
Every time I try to flash it just takes a minute then I reboot into the system; same thing happens then I get back into recovery to see that the /system is unmounted and can't be mounted back also when I try "repair partition" it shows that only 54mb of /system partition is used and around 1300mb is free, any insight on that?
Some errors about not being able to read storage file context and can't find path to /sdcard also appear sometimes on the log window or however it's called at the top right.
Click to expand...
Click to collapse
TWRP does have some issues mounting system sometimes.
Once you boot into recovery, choose the reboot recovery option and try the flash sgain.
Sent from my SM-G920V using Tapatalk
gr8nole said:
TWRP does have some issues mounting system sometimes.
Once you boot into recovery, choose the reboot recovery option and try the flash sgain.
Sent from my SM-G920V using Tapatalk
Click to expand...
Click to collapse
After trying different combinations of wiping and repairing and also changing partition type IT WORKED, freaking nice.
Thanks for your support!
I'm on zenity rr latest build with render kernel eas, I'd like to know how i can change file system to f2fs and what it will erase...And then... Is it worth changing to f2fs? Probably this question has been asked many times, but if i found it i wouldn't have written noob in title
eraser3000 said:
I'm on zenity rr latest build with render kernel eas, I'd like to know how i can change file system to f2fs and what it will erase...And then... Is it worth changing to f2fs? Probably this question has been asked many times, but if i found it i wouldn't have written noob in title
Click to expand...
Click to collapse
f2fs is for good benchmarks in real life ext4 >> f2fs
and when you change the FS the data will be lost .
f2fs makes twrp very slow as well .
I was using f2fs for a month and reverted it back .
Didnt like it
Its very easy brother although formatting data to f2fs will erase everything like your download's/pictures, so the steps.
BACK UP YOUR SD CARD FOLDER.
1 - Reboot to twrp
2 - select wipe and then select advanced wipe/change filesystem.
3 - select data
4 - select change filesystem or format ( forgot which word it actually says )
5 - select f2fs and swipe to confirm flash
6 - reboot and restore data folder
People will say its not worth it but if you write to your data a lot and install apps you notice faster install times over EXT4
daviss101 said:
Its very easy brother although formatting data to f2fs will erase everything like your download's/pictures, so the steps.
BACK UP YOUR SD CARD FOLDER.
1 - Reboot to twrp
2 - select wipe and then select advanced wipe/change filesystem.
3 - select data
4 - select change filesystem or format ( forgot which word it actually says )
5 - select f2fs and swipe to confirm flash
6 - reboot and restore data folder
People will say its not worth it but if you write to your data a lot and install apps you notice faster install times over EXT4
Click to expand...
Click to collapse
Will it wipe even other partitions like /system? do I have to flash again something?
eraser3000 said:
Will it wipe even other partitions like /system? do I have to flash again something?
Click to expand...
Click to collapse
No just data so you won't have to flash ROM again
daviss101 said:
No just data so you won't have to flash ROM again
Click to expand...
Click to collapse
Ok thanks, i thought i had to flash rom again:silly:
daviss101 said:
No just data so you won't have to flash ROM again
Click to expand...
Click to collapse
Does supersu work with f2fs?
Format data in recovery WIPE ALL in youre phone.
Recovery > Wipe > Format Data > Yes.
null0seven said:
Format data in recovery WIPE ALL in youre phone.
Recovery > Wipe > Format Data > Yes.
Click to expand...
Click to collapse
yes but...It will wipe only internal not system partition right?
Mate, format data erase ALL.
You only have a empty TWRP directory in internal memory. It's healty for the phone, but if you like to keep data...
null0seven said:
Mate, format data erase ALL.
You only have a empty TWRP directory in internal memory. It's healty for the phone, but if you like to keep data...
Click to expand...
Click to collapse
Lol, now i only became more confused. If i format data all my internal storage will be wiped, right? But my other partitions will be kept? such as system? after formatting and clicking on reboot system it will boot or stay in boot loop?
eraser3000 said:
Lol, now i only became more confused. If i format data all my internal storage will be wiped, right? But my other partitions will be kept? such as system? after formatting and clicking on reboot system it will boot or stay in boot loop?
Click to expand...
Click to collapse
There's no major difference you will see in changing the filesystem to F2FS. I am using F2FS on Data Partition on Sultan CM & there is no major difference in real life.
qasimtb said:
There's no major difference you will see in changing the filesystem to F2FS. I am using F2FS on Data Partition on Sultan CM & there is no major difference in real life.
Click to expand...
Click to collapse
I want to give it a try, if I don't see any noticeable difference I could come back to ext4
eraser3000 said:
yes but...It will wipe only internal not system partition right?
Click to expand...
Click to collapse
There are a few partitions on your phone, just like a hard drive. Think of your /system partition as your C: drive. Your /data partition would then be D: Your apps, the data for the apps, your dalvik/art cache, and your "Internal storage" are all on /data.
Changing your file system is literally formatting the drive, which initializes a new file system. For Windows, it's NTFS, for Linux it's normally ext4. You are basically going to format D:
Got it? Your Rom is on C:, data and apps on D:
Sent from my ONEPLUS A3000 using Tapatalk
About F2FS some users sad that it's better on gaming. And benchmarks (this it's useless).
Other than that recovery open slowly comparing with ext4.
Le
You will see that youre internal memory it's smaller on F2FS.
uudruid74 said:
There are a few partitions on your phone, just like a hard drive. Think of your /system partition as your C: drive. Your /data partition would then be D: Your apps, the data for the apps, your dalvik/art cache, and your "Internal storage" are all on /data.
Changing your file system is literally formatting the drive, which initializes a new file system. For Windows, it's NTFS, for Linux it's normally ext4. You are basically going to format D:
Got it? Your Rom is on C:, data and apps on D:
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Ok, now things are clear!