Recovery Mode and Font Error ...Need help - Motorola Droid and Milestone General

Am using Android 2.2 Milestone 2...
I am Using Z4Root to root the phone...
I Installed a font.ttf yesterday using
su
mount -o rw, remount -t yaffs2 /dev/block/mtdblock3 /system
chmod 4755 /system/fonts/DroidSansFallback.ttf
dd if=/sdcard/DroidSansFallback.ttf of=/system/fonts/DroidSansFallback.ttf
reboot
after that the phone can`t display the Chinese character..it just show the boxes...
because of not displaying chinese character and also because of the slow performance...I done wipe/factory reset in Recovery mode
I also formatted the SD card
Now in recovery mode it`s showing
E:Can`t open/cache/recovery/command
E:can`t open/cache/recovery/Caller
Also in recovery mode ..along with wipe/factory reset and wipe cache partition ---,apply sdcard:update.zip is present...I hope this stuff not shown before ,
i mean at the first time...(When i bought it)
When i select apply Sdcard:update.zip
E:failed to open /sdcard/update.zip(no such file or directory)
E:signature verification failed
installation aborted
I would like to know..how can i restore the default chinese font and the missing stuffs....
Please help me..

Check the size of the font file to find out whether it was copied successfully,change the permission,tick all and reboot.I'm still working at the error recovery.

Related

[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

[Q] i957 lost /storage/sdcard0

I've lost sdcard after connection to PC with alert "No external storage available".
I have "Permission denied" in root shell when trying "cat > /storage/sdcard0/123.txt"
"Unable to mount sdc" in TWRP.
Finally I reformatted sdcard with latest busybox:
busybox mkfs.vfat /dev/block/mmcblk0p26
but now I have garbage in TWRP log and again "Unable to mount sdc"
in a root shell:
cat > /storage/sdcard0/123.txt
/system/bin/sh: can't create /storage/sdcard0/123.txt: I/O error
sdcard -f
cannot mount fuse filesystem (22)
(I'm not sure what is sdcard command but it has nice option -f fix up file system before starting)
OS: CM10.
Stock ROM not starting at all.
So I'm sure the problem is wrong formatting partition. Maybe someone knows i957 right data for correct partition?
Solved.
Odin stock.
Then flash TWRP.
Then I can access sdcard from adb in TWRP:
/dev/block/mmcblk0p26
13499512 1729408 11770104 13% /sdcard
but still error in TWRP wipe storage menu.(!!!)
Then upload CM10
./adb push ~/android/i957/cm10_p5att_nrvate_testrelease7.zip /sdcard/
2954 KB/s (156512846 bytes in 51.724s)
Flash&reboot.
Odin is your friend
God promised men that he'd put beautiful women in all corners of the world. Then he laughed and laughed and made the world round

"Invalid Argument" when attempting to remount /system as RW [Solved, sorta]

While I was trying to install the "GSAM Root Companion" app and having it fail, and I discovered that the problem was that /system is still mounted RO. No problem, says I, and fired up my terminal app, pop into a root prompt with su, and issue the old invocation:
Code:
#mount -o remount,rw /system
mount: Invalid argument
I did some googling, and tried various different ways of laying out the command that other people have had luck with. I didn't have any
Code:
# /system/bin/mount -o remount,rw /system
# /system/bin/mount -o remount,rw /system /system
# /system/bin/mount -o rw,remount,rw /system
# /system/bin/mount -o remount,rw /dev/block/platform/mtk-msdc.0/by-name/system
# /system/bin/mount -o remount,rw /dev/block/platform/mtk-msdc.0/by-name/system /system
..etc..
My device is properly rooted (typing 'su' in the terminal prompt gives me my '#' prompt), selinux is set to 'permissive' (per the output of 'getenforce'), but all of them just keep giving me "Invalid Argument". At this point, the only thing I can think of is that it's actually blocked in the kernel, but as I'm hardly an expert, I figured I should put it up here before I gave up for good.
Anyone have a line on this?
Solved (sort of)
When even TWRP wouldn't remount /system to RW, I figured it was just time to throw up my hands and reflash.
TL;DR
Reflash /system to stock using SPTool
Reflash TWRP using SPTool
Allow TWRP to change /system to RW
DO NOT allow TWRP to try to install SuperSu.
The Longer Process, for anyone interested in the details
Removed SD, SIM, and Battery
Used SPTool to flash BLU_V0030UU_V07_REPAIR shared by "William Smith", excluded "boot", "recovery", and "preloader"
SPTool: https://app.box.com/s/rhok6s65sfsmrkq9w6021dnqgj6l5120
Repair Rom: https://www.mediafire.com/folder/s7m0q284yuvd2/BLU#61m7ikt8k97j9
Install Battery, no SD or SIM, and boot into TWRP
Allowed TWRP to mount system as RW, wipe Dalvik, Cache, Data, and exit. Allowed root
Boot would not pass the white "BLU" screen.
Used SPTool to reflash the same image as in 3, but only "system"
Straight reboot - Passed white boot screen to colored logo.
It took awhile but eventually got to the setup wizard.
Booted into recovery. Got stock recovery (Overwritten by the stock recovery because I stopped TWRP from changing it, at a guess).
Removed Battery. Used SPTool to reinstall TWRP
http://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
Replaced battery. Booted into recovery. Got TWRP
Allowed modifications to /system
Rebooted to system. Did NOT allow TWRP to install SuperSU. Phone booted
Before installing SD/SIM, went through setup process.
* Skipped adding SIM
* Added google account
Powered down phone, inserted SD card with SuperSU zip, installed from TWRP
* Wiped Dalvik, then rebooted into system
SuperSu: https://docs.google.com/uc?id=0B9srKhKuVIMna0xCdXlLS2dIYUU
Verified Root.
Rebooted into TWRP and installed Xposed. Rebooted. Lingered for awhile on white screen, but passed.
XPosed Framework and Installer thread: http://forum.xda-developers.com/showthread.php?t=3034811
Installed XPosed Installer
Used ES File Explorer to confirm /system was read/writable.

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