I've got a G1 which I suspect of having major FS corruption (apps and data disappearing and corrupting). I don't have A2SD, so I need to repair the inbuilt filing system. Can anyone tell me the command to do this?
I tried e2fsck /dev/block/mmcblk0p2 but I get file not found. And something about super block not being there. I don;t even think that's the command I need!
Any help would be appreciated, my phone is totally unusable at the moment.
Aw Crap guys,
I restored a Leedroid 2.2f and since that moment theres nothing working anymore. I cant access the progs on the cache partition anymore. When i go to the Recovery Menu it tells me, that the Cachepartition is mounted
How can i redo this? PLS HELP
Regards
Heba
Hi Guys,
After installing the Jellybean version of Resurrection Remix using a clean install like I'd done a million times before, I came across the problem where now the internal "/sdcard" won't mount. I've read a lot of different threads on the web about this but no one seems to have a fix, except for a similar thread from Android Stack Exchange (I can't post it yet).
However, that doesn't work (when I use the ADB shell, I can detect the device, reboot it, remount the /system but not remount the /sdcard). I thought it might possibly be because I tried to fix it a few days ago by formatting the "phone" drive when it popped up on my after connecting it, and the page I referred to talks about the internal SD card being FAT formatted (not NTFS which WIn7 does automatically!).
I've also used Odin to reflash a stock ROM thinking that would fix it, done the whole "format", "factory reset", wiped partitions, caches and delvik caches etc etc to no avail. Now, even when I use recovery to try to mount the /sdcard I get an error, and if I try to format the /sdcard from the recovery menu that doesn't work either.
Problem started with Clockwork Mod 6.6 and so I've downgraded to 5.5 and ICS stock ROM. Still no good.
It's affecting a lot of apps (for example, I can't restore by backup password file to awallet, and it has all my banking details on there!) and I really need to fix it ASAP.
Any ideas?
I'm absolutely desperate and have spent days trying to figure this one out, but I am beat. I need some serious help here and you guys are the ones I think who could help. Anyone??
Cheers,
CJ.
:crying:
I am a newbie into this rooting and upgrading stuffs on my android phone. Iv rooted, installed custom ROMs etc etc and tinkered with my phone a lot of times. I am also a curious learner. could anyone please tell me what exactly mounting storage, mounting data or mounting cache mean. Iv mounted and unmounted them alot of times going by the guidelines provided for the specific installations. Would be nice if i actually know why i am doing it Also Kindly let me on what actions can be performed or not performed when.they are mounted/ unmounted thank you.
#wannabeDeveloper
if you want to install a custom rom, sometimes a procedure for mounting tell you, it's like you open a permission to install that rom to your device
Sorry for my bad english
Achesh97 said:
I am a newbie into this rooting and upgrading stuffs on my android phone. Iv rooted, installed custom ROMs etc etc and tinkered with my phone a lot of times. I am also a curious learner. could anyone please tell me what exactly mounting storage, mounting data or mounting cache mean. Iv mounted and unmounted them alot of times going by the guidelines provided for the specific installations. Would be nice if i actually know why i am doing it Also Kindly let me on what actions can be performed or not performed when.they are mounted/ unmounted thank you.
#wannabeDeveloper
Click to expand...
Click to collapse
Mounting is the point where you can edit the files in the folder that you mount, it similar to that of mounting drives.
Similarly there are mounting such as when you use root explorers you can mount them as read/write or read only.
A Linux user can explain you in the best way, coz they usually mount their partitions as drives to work on them.
Hit thanks rather than typing it now Free
zipperX said:
if you want to install a custom rom, sometimes a procedure for mounting tell you, it's like you open a permission to install that rom to your device
Sorry for my bad english
Click to expand...
Click to collapse
your English is fine
so everytime you have to perform an update or flashing anything, you have to make sure that all the three are mounted? rigjt?
parkourkarthik said:
Mounting is the point where you can edit the files in the folder that you mount, it similar to that of mounting drives.
Similarly there are mounting such as when you use root explorers you can mount them as read/write or read only.
A Linux user can explain you in the best way, coz they usually mount their partitions as drives to work on them.
Hit thanks rather than typing it
Click to expand...
Click to collapse
Thank You there so whenever i have to flash a zip file or particularly an update, i have to mount everything? and what should be their states before rebooting? like mounted or unmounted?
Achesh97 said:
Thank You there so whenever i have to flash a zip file or particularly an update, i have to mount everything? and what should be their states before rebooting? like mounted or unmounted?
Click to expand...
Click to collapse
No need of mounting everytime you flash.
Mostly the zip files itself contains scripts to mount your partition, they do the job theirself.
In rare cases the developer of the flashable zip file would recommend you to mount the partitions required, in those cases only you need to mount through CWM
Hit thanks rather than typing it now Free
Look at the screenshots guys getting this error with every rom.
Looks like its not writing my /system at all.
Anyone faced the similar issues before?
And this is not a rom problem
nick2013 said:
Look at the screenshots guys getting this error with every rom.
Looks like its not writing my /system at all.
Anyone faced the similar issues before?
And this is not a rom problem
Click to expand...
Click to collapse
That is ok. After SuperSu flashed the system is unmounted and there is another call in the script for unmount. But since it is already unmounted it gives you the warning.
It should be like this