Missing files on sd card - G1 Q&A, Help & Troubleshooting

hey guys, when i try and update my recovery through terminal emulator I get an error
after the line
"mount -a"
i get:
mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: No such file or directory
mount: mounting /system/modules/modules.sqf on /system/modules failed: No such file or directory
mount: mounting /system/xbin/xbin.sqf on /system/xbin failed: No such file or directory
What is wrong here? it seems as if my sd card is missing files?! Can someone give me the files i am missing or would an sd card reformat fix it?

asb123 said:
hey guys, when i try and update my recovery through terminal emulator I get an error
after the link
"mount -a"
i get:
mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: No such file or directory
mount: mounting /system/modules/modules.sqf on /system/modules failed: No such file or directory
mount: mounting /system/xbin/xbin.sqf on /system/xbin failed: No such file or directory
What is wrong here? it seems as if my sd card is missing files?! Can someone give me the files i am missing or would an sd card reformat fix it?
Click to expand...
Click to collapse
The first error means you don't have an ext2/3/4 partition and you should be fine
The second and third are common errors and don't really mean anything
Just continue flashing the recovery

alright cool, i have now got the new amon recovery!

Related

Unable to mount SD card in console / terminal

I am trying to mount my SD card via console in recovery, I get
mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: Invalid argument
Any ideas whats wrong?
In recovery you can try:
mount -a
to just mount everything. Try that out.
Are you trying to copy files to the sdcard or the extX partition? It looks like the ext partition because that's blk0p2...
The sdcard would be ums_enable.

Problems trying to install Android on HTC Vogue

I'm incredibly green when it comes to this, so please bear with me.
During the Linux screen where it asks me to Hold down the Volume Up or D Pad Button the Installer never launches when I do either action. What does happen however is, I see stuff being typed as I press the middle DPAD Button and nothing at all being typed when I press the Volume Up. Every other button is assigned characters such as ^2, ^3, ^4, etc.
No matter what button I've tried holding during that part, nothing every launches or opens.
Help would be greatly appreciated.
Thanks!
foolosophy said:
I'm incredibly green when it comes to this, so please bear with me.
During the Linux screen where it asks me to Hold down the Volume Up or D Pad Button the Installer never launches when I do either action. What does happen however is, I see stuff being typed as I press the middle DPAD Button and nothing at all being typed when I press the Volume Up. Every other button is assigned characters such as ^2, ^3, ^4, etc.
No matter what button I've tried holding during that part, nothing every launches or opens.
Help would be greatly appreciated.
Thanks!
Click to expand...
Click to collapse
yeah that shows up, just hold down the d-pad center button for a osecond or two then let go then hold it down again, etc
mrono said:
yeah that shows up, just hold down the d-pad center button for a osecond or two then let go then hold it down again, etc
Click to expand...
Click to collapse
I've tried it, nothing happens. It just types another ^@ symbol, no matter how long I hold, or how many times I stop holding and rehold.
foolosophy said:
I've tried it, nothing happens. It just types another ^@ symbol, no matter how long I hold, or how many times I stop holding and rehold.
Click to expand...
Click to collapse
Have you tried reflashing? Maybe try different versions of the kernel?
foolosophy said:
I've tried it, nothing happens. It just types another ^@ symbol, no matter how long I hold, or how many times I stop holding and rehold.
Click to expand...
Click to collapse
Try to get the latest package from myn. it should work ok.
vogue android should be discussed in the vogue android forum http://forum.xda-developers.com/forumdisplay.php?f=588
egzthunder1 said:
Try to get the latest package from myn. it should work ok.
Click to expand...
Click to collapse
Tried, same issue.
Any other suggestions?
When you press the d pad to run haret keep it pressed that's how I get it to work and do you have all the needed files to boot android
sak211l said:
When you press the d pad to run haret keep it pressed that's how I get it to work and do you have all the needed files to boot android
Click to expand...
Click to collapse
I did this but I was not aware that it wipes out windows mobile 6.5-I thought this was a dual boot install
narottam said:
I did this but I was not aware that it wipes out windows mobile 6.5-I thought this was a dual boot install
Click to expand...
Click to collapse
It doesn't unless you are installing in NAND. If you run from SD card, it will tell you that it is about to wipe all your data, but that only relates to Android files present in your card.
Thread Moved to Vogue Android Section.
Same problem
I am having the same problem. Used different kernels, tried to install from nand and SD card. Used 2 different SD cards and the same problem, the installer fails to load.
Mentioned this in Myms thread but no reponses
Heres my bootlog
** /dev/block/mmcblk0p1
** Phase 1 - Read FAT (compare skipped)
Attempting to allocate 7653 KB for FAT
** Phase 2 - Check Cluster Chains
** Phase 3 - Checking Directories
** Phase 4 - Checking for Lost Files
Next free cluster in FSInfo block (11080) not free
Fix? yes
5 files, 3001800 free (1948089 clusters)
sh: 0: unknown operand
mount: mounting /dev/block/mtdblock2 on /system failed: Invalid argument
mount: mounting /dev/block/mtdblock3 on /data failed: Invalid argument
mount: mounting /data/tmpcache on /cache failed: Invalid argument
mount: mounting /data/shared_prefs on /shared_prefs failed: Invalid argument
mount: mounting /data/tmpcache on /tmp failed: Invalid argument
mount: mounting /data/sysfiles/su on /system/bin/su failed: No such file or directory
mount: mounting /data/sysfiles/su on /system/xbin/su failed: No such file or directory
mount: mounting /data/sysfiles/su on /bin/su failed: Invalid argument
mount: mounting /data/sysfiles on /system/etc/ppp failed: No such file or directory
mount: mounting /data/sysfiles on /smodem failed: Invalid argumen
Did have this working, but went back and did the "Verizon GPS fix". After that the installer would never load.
Thanks
gorm said:
I am having the same problem. Used different kernels, tried to install from nand and SD card. Used 2 different SD cards and the same problem, the installer fails to load.
Mentioned this in Myms thread but no reponses
Heres my bootlog
** /dev/block/mmcblk0p1
** Phase 1 - Read FAT (compare skipped)
Attempting to allocate 7653 KB for FAT
** Phase 2 - Check Cluster Chains
** Phase 3 - Checking Directories
** Phase 4 - Checking for Lost Files
Next free cluster in FSInfo block (11080) not free
Fix? yes
5 files, 3001800 free (1948089 clusters)
sh: 0: unknown operand
mount: mounting /dev/block/mtdblock2 on /system failed: Invalid argument
mount: mounting /dev/block/mtdblock3 on /data failed: Invalid argument
mount: mounting /data/tmpcache on /cache failed: Invalid argument
mount: mounting /data/shared_prefs on /shared_prefs failed: Invalid argument
mount: mounting /data/tmpcache on /tmp failed: Invalid argument
mount: mounting /data/sysfiles/su on /system/bin/su failed: No such file or directory
mount: mounting /data/sysfiles/su on /system/xbin/su failed: No such file or directory
mount: mounting /data/sysfiles/su on /bin/su failed: Invalid argument
mount: mounting /data/sysfiles on /system/etc/ppp failed: No such file or directory
mount: mounting /data/sysfiles on /smodem failed: Invalid argumen
Did have this working, but went back and did the "Verizon GPS fix". After that the installer would never load.
Thanks
Click to expand...
Click to collapse
Try to hard reset your WM and then use HaRet.
Thanks but I tried that this morning.
After running the Android OS on this phone, I just dont want to have to go back to Win MO
gorm said:
I am having the same problem. Used different kernels, tried to install from nand and SD card. Used 2 different SD cards and the same problem, the installer fails to load.
Mentioned this in Myms thread but no reponses
Heres my bootlog
** /dev/block/mmcblk0p1
** Phase 1 - Read FAT (compare skipped)
Attempting to allocate 7653 KB for FAT
** Phase 2 - Check Cluster Chains
** Phase 3 - Checking Directories
** Phase 4 - Checking for Lost Files
Next free cluster in FSInfo block (11080) not free
Fix? yes
5 files, 3001800 free (1948089 clusters)
sh: 0: unknown operand
mount: mounting /dev/block/mtdblock2 on /system failed: Invalid argument
mount: mounting /dev/block/mtdblock3 on /data failed: Invalid argument
mount: mounting /data/tmpcache on /cache failed: Invalid argument
mount: mounting /data/shared_prefs on /shared_prefs failed: Invalid argument
mount: mounting /data/tmpcache on /tmp failed: Invalid argument
mount: mounting /data/sysfiles/su on /system/bin/su failed: No such file or directory
mount: mounting /data/sysfiles/su on /system/xbin/su failed: No such file or directory
mount: mounting /data/sysfiles/su on /bin/su failed: Invalid argument
mount: mounting /data/sysfiles on /system/etc/ppp failed: No such file or directory
mount: mounting /data/sysfiles on /smodem failed: Invalid argumen
Did have this working, but went back and did the "Verizon GPS fix". After that the installer would never load.
Thanks
Click to expand...
Click to collapse
Ok, so you CANNOT get into the installer? Do you ultimately want to use sd or nand? After doing the verizon GPS fix, did you reflash an android nbh?
would rather use nand. I have tried many different android nbhs from back in FEB . to the most recent dated kernels.
gorm said:
would rather use nand. I have tried many different android nbhs from back in FEB . to the most recent dated kernels.
Click to expand...
Click to collapse
Ok, so after running the verizon gps fix you did flash an nbh (correct?) and now when the phone boots you can't get into the installer by holding a button or the screen?
mrkite38 said:
Ok, so after running the verizon gps fix you did flash an nbh (correct?) and now when the phone boots you can't get into the installer by holding a button or the screen?
Click to expand...
Click to collapse
Yes that is correct.
gorm said:
Yes that is correct.
Click to expand...
Click to collapse
Are you seeing the 'Press to enter installer' message go by?
mrkite38 said:
Are you seeing the 'Press to enter installer' message go by?
Click to expand...
Click to collapse
Yes I am seeing the installer message, just nothing happens when I press the d pad or any other button. I have tried them all.
Just as foolosophy posted in post #3
TIA

[Q] Hello there have some problems with moving system files

Hi i moved some files from system/app into the sd card to get some space so i could use the metamorph app but i didnt work so i was going to move back the files from the sd card to system/app but now they wont move there anyone know a soloution how to do this?
thanks in advance
system is readonly
you must do an
adb shell
mount /dev/block/mtdblock3 /system
then you can fool around with your system apps
mount /dev/block/mtdblock3 /system || I wrote that but it says
"mount: mounting /dev/block/mtdblock3 on /system failed: Device or resource busy"
i rooted my phone yesterday quite knew to android and i have no clue what to do
You are doing that in recovery mode right?
I tried in ClockworkMod Recovery v2.5.0.1 but it says Device or resource busy :/ have no clue.
ClockworkMod has a nice green menu on screen from where you can see (partitions menu) which partitions are already mounter and which are not.
You can also do adb shell and run "mount" in it to see which partitions are mounted and in what way. ClockworkMod has /etc/fstab so you can mount system just by running "mount /system". If system is already mounted, you can cd to /system/app and try "touch test". If you get permission denied then your system is mounted read-only otherwise you will see test file in /system/app if you run "ls".
I did adb shell and did run "mount" and it says /dev/block/mtdblock3/ on /system type yaffs2 <ro>
I downloaded a app called root explore and the main reason for that was so i could move some files from system/app so i could get some free space so i could use metamorph that was my plan and i moved some files i have eard you could move that wouldnt harm anything but it wasnt enough free space, so my plan was to move back the files i had moved into the sd card some went great but i have like 4 files that i cant bks it says "You cannot paste here because the file system is read-only" is there any other way to push those file into the system/app again? have tried the things u wrote up.
And im not a very pro of theese things i started with this yesterday so excuse me for being stupid!
This:
/dev/block/mtdblock3/ on /system type yaffs2 <ro>
...means that system is mounted read-only (mind that "ro" at the end).
Try running "mount -o remount,rw /system". If it doesn't help run "cat /etc/fstab" and post here the output. You need to be in recovery mode while doing this of course!
did "mount -o remount,rw /system" and it said mount: can't find /system in /proc/mounts
and the other one said
/dev/block/mtdblock4 /cache yaffs2 rw
/dev/block/mtdblock5 /data yaffs2rw
/dev/block/mtdblock3 /system yaffs2 rw
/dev/block/mmcblk0p1 /sdcard vfat rw
/dev/block/mmcblk0p2 /sd-ext auto rw
used my brain a little now and in the recovery settings i did mount the /system in the menu and now i tried to write cd /system/app and now in the cmd it is like this "/system/app #" anything useful?
Sure... as I already told you try to run "touch /system/app/test". This command shoud make empty test file in /system/app. If you get permission denied then you have read-only system. If it suceede, then your /system is writable and you can see all the contents of /system/app by runing "ls".
I wrote that and it wrote the same
"touch /system/app/test"
no permmission denied then it may have worked?
i checked and there is a testfile in /system/app now
I think i got it to work now thanks man for all your help!

[Q]: Read-only filesystem

Hi!
I have rooted my phone (LG Optimus 2X) and mistakenly deleted some files.
I have these files, and want to push them back using adb, put my problem is, that when i try to mount the system in read / write mode using "adb remount" i get this error: "remount faileded: Operation not permitted".
I can't figure out how to fix it, i can pull files etc.
I have also tried to use the adb shell, and copy the files from the internal sdcard, but i'm getting the same error.
Only read-mode.. :/
Anybody who can help, fixing this problem?
If you want to mount /system just write:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Then you're good to go
How to unmount into read-mode only?
Thank! - You saved my day
mrhtml said:
How to unmount into read-mode only?
Thank! - You saved my day
Click to expand...
Click to collapse
A little easier to type...
Mount r/w
Code:
busybox mount -o,remount -rw /system
Mount r/only
Code:
busybox mount -o,remount -r /system
Edit: You shouldn't post stuff like this in dev

Data recovery, how to mount messed up /data - Internal SD - sda25 in Recovery/ADB

Hi:
I've messed up my Note 9 pretty bad, such that no partitions mount in TWRP except cache - I'll need to do a data wipe, but I need to save data that I have in the Internal SD.
I've discovered via fdisk in TWRP that the media part - the Internal SD is partition sda25 - however can
t mount it in the terminal through a simple: mount /dev/block/sda25 /mnt
I get an error: mount failed: Invalid argument
I've tried: mount -t sdcardfs /dev/block/sda25 /mnt
This gives me also an error: mount failed: Not a directory
Mounting with -t vfat or exfat gives the Invalid argument error.
Anyone can help me with how to mount it, so that I may copy data off of it manually? I don't want to lose it. Many thanks.
白い熊 said:
Hi:
I've messed up my Note 9 pretty bad, such that no partitions mount in TWRP except cache - I'll need to do a data wipe, but I need to save data that I have in the Internal SD.
I've discovered via fdisk in TWRP that the media part - the Internal SD is partition sda25 - however can
t mount it in the terminal through a simple: mount /dev/block/sda25 /mnt
I get an error: mount failed: Invalid argument
I've tried: mount -t sdcardfs /dev/block/sda25 /mnt
This gives me also an error: mount failed: Not a directory
Mounting with -t vfat or exfat gives the Invalid argument error.
Anyone can help me with how to mount it, so that I may copy data off of it manually? I don't want to lose it. Many thanks.
Click to expand...
Click to collapse
cant you simply wipe the affected partitions(except data of course)? then flash a rom?
have you tried;
mount /sys/block/sda25 /mydata
or
mount /dev/block/sda25 /mydata
or
adb
mount -o rw /dev/block/sda25/data /mydata
in both cases /mydata is just the mount point so I believe it can simply be called what ever you want including just /data
have you read:
https://android.stackexchange.com/q...data-partitions-in-recovery-mode-in-adb-shell
edit:
by any chance when you first flashed twrp, did you forget to format data?
if yes then flash back stock AP file(original phone's firmware) in Odin AP slot only and you should be good to go.( you shouldn't loose any files in internal storage)

Categories

Resources