hey all i think i did evrething... im trying to install hebrew fonts on my rooted g1
i tryed to put the hebrew fonts on the sd and went to the terminal on the phone and typed :
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cat /sdcard/DroidSans-Bold.ttf > /system/fonts/DroidSans-Bold.ttf
cat /sdcard/DroidSansMono.ttf > /system/fonts/DroidSansMono.ttf
cat /sdcard/DroidSans.ttf > /system/fonts/DroidSans.ttf
cat /sdcard/DroidSerif-Bold.ttf > /system/fonts/DroidSerif-Bold.ttf
cat /sdcard/DroidSerif-Regular.ttf > /system/fonts/DroidSerif-Regular.ttf
reboot
i did it all after every line is said "#"
and after the reboot nothing....
what am i doing wrong ?
please! i cant see my contacts and messeges and nothing....
i dont realy understand this thing so if some1 cant tell me slowly what to do...
think alot...
Related
Hi every body !
I made my G1 connecting with Ad Hoc mode:
Code:
adb shell mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
adb push tiwlan.ini /data/misc/wifi/tiwlan.ini
adb push wpa_supplicant.conf /data/misc/wifi/wpa_supplicant.conf
adb shell mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
And i have made a correct tiwlan.ini and wpa_supplicant.conf, this is why it works like a charm.
Now, i have two problems:
1- After every reboot, i can't start my Wifi(no Wifi at all, it is OFF), i have to redo all that script
2- Even i made a Shell Script, noway, it works only by using the ADB. Here is a very basic script that i tried:
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cp -f ./tiwlan.ini /data/misc/wifi/tiwlan.ini
cp -f ./wpa_supplicant.conf /data/misc/wifi/wpa_supplicant.conf
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
Any idea ?
Thank you.
G1 - Cyanogen 5.0.8-N1
(Sorry for my english writing)
Hi !
UP
I didn't resolve the problem yet
A+
I don't know how much of the script you understand, but your /system partition doesn't seem to be mounted until you run that script. That doesn't seem normal, /system sounds rather important :-/ If you don't know how to undo whatever modifications you have made, I would recommend resetting your phone to factory settings. It should fix it.
hi guys,
i hope someone can help me out with this;
i have rooted my DHD with Visionairy and all works fine, except...
doh...i forgot to check the option to set rw on /system partition
now i have tried the following from Terminal App;
#su
#mount -o rw -t yaffs2/dev/block/mtdblock3 /system
i read somewhere that this should set rw on /system but it didn't work;
then i tried the 'Unroot Now' option in Visionairy but that doesn't work either....
how can i set rw on my /system partition??
thnx in advance!
odin
Hey mate, I had the same problem. Took a mistake while entering mount information before I figured out where I went wrong.
Try entering 'mount' by itself, you'll get all your relivant information. You need to find '/system' in the stings of information and then which 'mmcblk0p*' (the * will be a number, your folder might be something different, like mtdblock3) it is attached to.
I think some ROM's use different locations, as I was told something simmilar to you, which wasn't working, I'm no expert so I had to fiddle and look to find the right string.
For example mine goes;
/dev/block/mmcblk0p25 on /system type ext3 (ro,relatime,errors=continue,data=or)
This told me I had to enter the following string to set it to rw;
mount -o remount,rw -t yaffs2 /dev/block/mmcblk0p25 /system
This seemed to work for me, but I need to enter it every time I restart the handset and want to change something in the /system folder.
Hi everyone,
I am kind of stuck with getting a custom ROM on my HTC Magic 32B (spl:1.33.0013 radio:2.22.28.25 os:2.2.1ota)
I cant flash custom recovery...or anything else
Here´s what happend so far:
http://forum.xda-developers.com/showthread.php?t=939749
Hope someone can help
There was another person that I was working with having the same problem. For whatever reason we couldn't get the custom recovery to stick no matter what we tried and we ended up stopping with him trying to downgrade to root. I'm not sure where he got. You can try using "flash_image" from terminal, but it probably won't help. Download the attached "Flash_image.zip", unzip the file, and put in on the root of your SD card. Then open up terminal on the phone and type the following hitting enter at the end of each line:
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 755 /system/bin/flash_image
mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
flash_image recovery /sdcard/*name of recovery*.img
reboot recovery
Thanks for your instructions...but it did not work for me.
I kind of gave up on getting my Magic flashed.
Did you check to see if there are any scripts that will override the recovery on closure?
Do this:
Pull out the battery when you execution of the flash_image command has succeeded.
This way you can avoid any scripts being executed on turn-off.
Now try to see if you can get the custom recovery to work!
Want to switch to Natural mode colors on your recently Cyanogenmoded phone ?
Tested on Galaxy Note 2 N-7100 CM10 but it should work any Android 4.1+ Samsung AMOLED phone.
Open a shell on your phone
HTML:
echo 2 > /sys/class/mdnie/mdnie/mode
echo 2 > /sys/class/mdnie/mdnie/scenario
You should have the right colors (Natural mode)
How to make it directly at boot :
HTML:
su
mount -o remount,rw / && mount -o remount,rw /system
echo "#!/system/bin/sh
echo 2 > /sys/class/mdnie/mdnie/mode
echo 2 > /sys/class/mdnie/mdnie/scenario
" > /etc/init.d/99color
chmod 755 /etc/init.d/99color
mount -o remount,ro / && mount -o remount,ro /system
Original source here :
mathieumeuh said:
Want to switch to Natural mode colors on your recently Cyanogenmoded phone ?
Tested on Galaxy Note 2 N-7100 CM10 but it should work any Android 4.1+ Samsung AMOLED phone.
Open a shell on your phone
HTML:
echo 2 > /sys/class/mdnie/mdnie/mode
echo 2 > /sys/class/mdnie/mdnie/scenario
You should have the right colors (Natural mode)
How to make it directly at boot :
HTML:
su
mount -o remount,rw /
mount -o remount,rw /system
echo "#!/system/bin/sh
echo 2 > /sys/class/mdnie/mdnie/mode
echo 2 > /sys/class/mdnie/mdnie/scenario
" > /etc/init.d/99color
chmod +x /etc/init.d/99color
mount -o remount,ro /
mount -o remount,ro /system
Original source here :
Click to expand...
Click to collapse
thanks a lot. i can use it on my 4.3 mokee rom and neak kernel
Sent from my GT-N7100 using xda premium
Awesome Tips... I didn't know that on Other than Sammy based rom can use color mode
THanks for this Valuable Information
I tried this on my cm-10.1.3 Samsung Galaxy 2 phone (android 4.2.2) and it wouldn't write. I opened up the files themselves with vim and tried, and got some errors:
After successfully getting superuser, it told me a swap file couldnt be recovered (i hadnt even opened the file before). Then after the changes and trying to write&quit, it said
Code:
"mod" E509: Cannot create backup file (add ! to override)
Press ENTER or type command to continue
So i did :wq! and then
Code:
"mode" E667: Fsync failed
WARNING: Original file may be lost or damaged
don't quit the editor until the file is successfully written!
I quit. The file "mode" is still there, and the command "cat" reveals it still has one line, one character, being "0" (like it originally had).
There is also a GUI controller under System Settings > Advanced Settings under the "Color" heading, but changing anything doesnt seem to have an affect. I wonder if it's related to the "fsync" error.
I would upgrade to 10.2, but i just read that 10.2 has the system menu entry removed, so mdnie can only be controlled by command line. Lame.
gatchipatchi said:
I tried this on my cm-10.1.3 Samsung Galaxy 2 phone (android 4.2.2) and it wouldn't write. I opened up the files themselves with vim and tried, and got some errors:
After successfully getting superuser, it told me a swap file couldnt be recovered (i hadnt even opened the file before). Then after the changes and trying to write&quit, it said
Code:
"mod" E509: Cannot create backup file (add ! to override)
Press ENTER or type command to continue
So i did :wq! and then
Code:
"mode" E667: Fsync failed
WARNING: Original file may be lost or damaged
don't quit the editor until the file is successfully written!
I quit. The file "mode" is still there, and the command "cat" reveals it still has one line, one character, being "0" (like it originally had).
There is also a GUI controller under System Settings > Advanced Settings under the "Color" heading, but changing anything doesnt seem to have an affect. I wonder if it's related to the "fsync" error.
I would upgrade to 10.2, but i just read that 10.2 has the system menu entry removed, so mdnie can only be controlled by command line. Lame.
Click to expand...
Click to collapse
Do not try to open this file, it's not really a file. Just push the value to it.
Hi guys,
A friend of mine recently rooted his I9505 and tried to install a custom Rom.
He made an Nandroid backup of his Stock rom but TWRP wasn't able to mount /efs.
So he ignored it and made a Backup without checking /efs.
As he installed a custom Rom he did something wrong and wasn't able to boot system.
So he went back to stock rom.
The Problem now is that his /efs folder is empty and he has no lockscreen and powermenu.
But the strange thing is that he has no problems with IMEI or Baseband.
Is it somehow possible to get his /efs files back?
Or at least get his lockscreen an powermenu back working?
He would be even happy with and alternative lockscreen and powermenu. maybe a app?
I hope someone can help us
Thank you very much in advance for your answers
SOLVED:
I tried many different methods so i don't really know which one worked.
But here are several methods you can try if you have the same problem:
Method 1:
Code:
su
busybox mount /efs
echo -n ON > /efs/FactoryApp/keystr
echo -n ON > /efs/FactoryApp/factorymode
reboot
Method 2:
Code:
su
mke2fs /dev/block/mmcblk0p10
mount -w -t ext4 /dev/block/mmcblk0p10
echo -n ON > /efs/FactoryApp/keystr
echo -n ON > /efs/FactoryApp/factorymode
reboot
Method 3:
Code:
su
mount -w -t ext4 /dev/block/mmcblk0p10
echo -n ON > /efs/FactoryApp/keystr
echo -n ON > /efs/FactoryApp/factorymode
reboot
Try them all and one of them should work
Try a factory reset. If that doesn't work odin to stock should get you fixed up
Sent from my Nexus 10
9233 said:
Hi guys,
A friend of mine recently rooted his I9505 and tried to install a custom Rom.
He made an Nandroid backup of his Stock rom but TWRP wasn't able to mount /efs.
So he ignored it and made a Backup without checking /efs.
As he installed a custom Rom he did something wrong and wasn't able to boot system.
So he went back to stock rom.
The Problem now is that his /efs folder is empty and he has no lockscreen and powermenu.
But the strange thing is that he has no problems with IMEI or Baseband.
Is it somehow possible to get his /efs files back?
Or at least get his lockscreen an powermenu back working?
He would be even happy with and alternative lockscreen and powermenu. maybe a app?
I hope someone can help us
Thank you very much in advance for your answers
Click to expand...
Click to collapse
efs is not empty. you can not see inside because it is not mounted.
root the device, install terminal emulator. type:
Code:
su
mount /efs
mount -o remount,rw /efs
echo -n ON > /efs/FactoryApp/keystr
echo -n ON > /efs/FactoryApp/factorymode
reboot
samersh72 said:
efs is not empty. you can not see inside because it is not mounted.
root the device, install terminal emulator. type:
Code:
su
mount /efs
mount -o remount,rw /efs
echo -n ON > /efs/FactoryApp/keystr
echo -n ON > /efs/FactoryApp/factorymode
reboot
Click to expand...
Click to collapse
mount /efs is not working. I'm getting this Error Message:
http://dl.xda-developers.com/attachdl/8c9fb4bc3dc504c869fd2aebc109f0df/523b4bef/2/2/6/8/9/0/0/IMG-20130919-WA0003.jpg
9233 said:
mount /efs is not working. I'm getting this Error Message:
http://dl.xda-developers.com/attachdl/8c9fb4bc3dc504c869fd2aebc109f0df/523b4bef/2/2/6/8/9/0/0/IMG-20130919-WA0003.jpg
Click to expand...
Click to collapse
try without mounting: "su" then the "echo"
if not try mounting with these commands:
Code:
su
mke2fs /dev/block/mmcblk0p10
mount -w -t ext4 /dev/block/mmcblk0p10
reboot
if not, ignore mke2fs...... line
samersh72 said:
try without mounting: "su" then the "echo"
if not try mounting with these commands:
Code:
su
mke2fs /dev/block/mmcblk0p10
mount -w -t ext4 /dev/block/mmcblk0p10
reboot
if not, ignore mke2fs...... line
Click to expand...
Click to collapse
Thank you.
I don't have the phone here so i'll try it tomorrow and see what happens.
Your mount command didn't work because you are using the /system/bin/mount that is a part of Android. This version must get the device name and the mount point, you cannot omit one of them (with busybox mount you can omit one or the other).
I had the EXACT problem and already started a thread.
There was a lot of help given to me, try reading through my thread mate.
http://forum.xda-developers.com/showthread.php?t=2388663
In the end it turned out my EFS partition was so corrupt it had to go to service centre.
Sent from my GT-I9505 using XDA Premium HD app
Hi guys,
I tried it with the following and it works!!!
Code:
su
busybox mount /efs
echo -n ON > /efs/FactoryApp/keystr
echo -n ON > /efs/FactoryApp/factorymode
reboot
Thank you all for your Help and have a nice day!