Please, anyone that has a decent depth of knowledge regarding mounting, binding, unmounting, remounting elsewhere while not destroying anything that was mounted incorrectly causing the ultimate demise of my phone. Also scripting, code and queries to find out what had been accidentally mounted and how to move it appropriately. Explanation follows:
I am in need of a little assistance.
And by a little I mean a lot.
I have been using link2sd for a long time and the ext partition would normally be mounted /dev/block/mmcblk0p2. Or vold/ 179:2.
I use the ext4 driver like Prime had recommended due to lower cpu load.
I don't know how I messed things up, but it may have been messing around with Swapper 2 and the linux swap partition. I think what ever I did screwed up all of my mount points.
I can no longer even mount the sdext in recovery to format and if I try to restore a pre mess up backup, it isn't allowing the sdext to mount so the nandroid doesn't fully restore.
I get the following error message in recovery:
E: can't mount /dev/block/mmcblk0p2 (file exists)
Error mounting SDEXT:!
So restoring the ext gets skipped. I tried.flashing new ROMs to see if that would overwrite whatever was the cause, but no luck. Flashed gb and froyo ROMs but still no luck.
Also I can't seem to find out what exactly exists on mmcblk0p2 or how to move those files to the correct location.
It won't show when running bb commands cat process mounts.
Though it shows the fs mounted to obb and asec and yaffs.
Using "Root System Tools" app, that handles a lot of root functions, terminal, file directory viewer..etc.
But now when using the directories manager to figure out what is mmcblk0p2 mounted to and what resides within. But even though all permissions fixed, when I try to access and see what is on /dev/block/mmcblk0p2 I get the following pop up:
Permission denied to open the file
I think there is an outside chance that java coding now resides there, but that its merely a guess based on what problems are now suddenly occurring for the first time ever.
My main concern is that something important indirectly was bound to mmcblk0p2. Something that if formatted before it is mounted correctly could brick the phone.
Since this mount mishap, notification sounds don't work.
Lockscreen never happens, so even on boot no lockscreen.
The home key now won't do anything, return to home, open app drawer or show recent apps when long pressed.
Nor does the search button.
They give haptic but that is it.
So frustrating and why I'm worried about what now resides incorrectly mounted and how any poorly thought up attempt could destroy the ability for the phone to function whatsoever.
I've tried flashing a bunch of different ROMs to see if they would fix it as they might have different set ups including froyo and a real old MIUI and PE.
Still same problem.
That's no way for an OG to live.
Thanks to all with offers of assistance, ideas and solutions.
I really need help on this one.
Don't let me down, please, as it is clear many previously posting in this thread possess great wealths of knowledge in this area.
This helper needs help.
Motorola Droid Rooted
SD with ext partition and linux swap partition
Rescue squad, throw me a line please!!!
walkin the walk while tappin the talk