Related
Hi all,
I'm trying to put a font in my new wildfire so I'll be able to read stuff in Hebrew.
I tried this guide : https://sites.google.com/a/bardavid.com/android-g1/Home/adding-hebrew-fonts
to add the fonts to my htc, but I had a little problem.
When I tried to give to command su in the shell, it worked, but then I tried the:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
and then it told me: mount: Operation not permitted.
I used the SoftRoot to get the root permission, but it did not help, as you can see.
If someone here has a better idea of getting root permission, or a way to get Hebrew fonts on my HTC, I'll be more than happy, since I feel like I bought a plastic box and not a smartphone.
One more question: When I go to settings in my cell, and check for updates - does the update check is made in my cell provider (which in my case is Orange), or does the update check is made somewhere over the net?
And is there a date for Froyo release to the wildfire?
thanks all, I really appreciate it!
Can somebody please explain the difference between these two commands.
1) mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
2) mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
In adb I'm using the latter to mount my system dir as rw. I perform what I have to then issue the next command:
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
But it tells me the device is busy and to try again later. Well it never lets me remount as ro so I just exit, perform a reboot of the phone, and it is back to ro. I can't help think this is not a good way of doing it though. So I was gonna try this other command but don't know what exactly either is or the difference between the two. Anyway some help would be greatly appreciated.
***EDIT***
OK I finally got it to work. Seems you can not enter adb, root, exit adb, then enter adb again, attempt to unroot. The unroot takes and all works until I try to remount as ro, then I get above problem. Now when I root, exit adb, reboot phone, re-enter adb, and attempt to unroot everthing goes as expected with remounting as ro.
So thanks for anybody that at least took a look at the thread. Seems I have it squashed though. If you are wondering I'm testing some things out that is why I'm rooting, and unrooting back to back.
I don't even bother remounting. I just type #reboot. It will remount, by default, when the system starts up.
Str0ntium said:
I don't even bother remounting. I just type #reboot. It will remount, by default, when the system starts up.
Click to expand...
Click to collapse
Yeah that's what I had to resort to, but as I stated. I just can't help think that's not a good practice to get into.
Anyway I found what was causing my trouble and remounting as ro with the previous command works fine.
Sent from my DROIDX using Tapatalk
To answer your question about the difference in the two commands... The yaffs2 or ext3 is the specifying the you're off file system you are mounting as.
overfiendx2 said:
Can somebody please explain the difference between these two commands.
1) mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
2) mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
In adb I'm using the latter to mount my system dir as rw. I perform what I have to then issue the next command:
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
But it tells me the device is busy and to try again later. Well it never lets me remount as ro so I just exit, perform a reboot of the phone, and it is back to ro. I can't help think this is not a good way of doing it though. So I was gonna try this other command but don't know what exactly either is or the difference between the two. Anyway some help would be greatly appreciated.
***EDIT***
OK I finally got it to work. Seems you can not enter adb, root, exit adb, then enter adb again, attempt to unroot. The unroot takes and all works until I try to remount as ro, then I get above problem. Now when I root, exit adb, reboot phone, re-enter adb, and attempt to unroot everthing goes as expected with remounting as ro.
So thanks for anybody that at least took a look at the thread. Seems I have it squashed though. If you are wondering I'm testing some things out that is why I'm rooting, and unrooting back to back.
Click to expand...
Click to collapse
Sent from my DROIDX using XDA App
SysAdmin-X said:
To answer your question about the difference in the two commands... The yaffs2 or ext3 is the specifying the you're off file system you are mounting as.
Click to expand...
Click to collapse
Thanks for the response. Could you explain in more detail. I don't understand what you mean. Again thank you for taking time with such a noob thing.
Sent from my DROIDX using Tapatalk
mount command line options...
"-t <option>"
"t" stands for "type" and <option> = the linux filesystem type. Linux supports many. "yaffs" = "yet another flash file system" (lot's of tongue-in-cheek developers work on linux). "yaffs2" is v2 of this type of file system.
ext3 is a widely used linux file system.
essentially, the filesystem type tells linux how the data is actually organized on the disk.
the /dev/... that follows is the raw device to associate the filesystem type with.
So I take it that the phone or more directly adb can handle either file system? What of the mtdblock4 and mmcblk1p21 entries? I guess i just don't understand how two so different commands can mount/unmount the same folder. Again thank you very much for your time.
Sent from my DROIDX using Tapatalk
well, adb is just a way to open a terminal session on your phone. Think of it like opening a command prompt on windows. So it is the linux OS on your DX that is processing (handling) the command.
The two commands mount different raw devices (that actually are formatted with different filesystems) to the same "/system" mountpoint. In linux, a mountpoint is kind of like a drive letter would be in dos. What's cool about linux is that you can mount a raw device anywhere in the filesystem tree (where the root is specifiied as "/"). Windows provides that same functionality now with it's ability to map devices to folders.
I believe I'm beginning to wrap my head around it. Been fool'n w/ computer for awhile. I really have no excuse to be so illiterate on linux. I really need to just dig in. Any suggested starting points? I really loved dos and miss it so. lol. So I'm thinking I will probably enjoy linux more.
Sent from my DROIDX using Tapatalk
+5 to sleuth's response! I forgot to kinda expand on the rest of the command. Thnx sleuth for filling in the rest.
Sent from my DROIDX using XDA App
Hello
I have a Galaxy S4 i337m canadian model (firmware i337MVLUFNC1) that has unknown baseband and null imei.
WIfi and blutooth work. it does not recognize sim card.
I have been reading for two weeks about this problem and tried all the methods that i found on google.
I dont have efs backup.
I don't see the nv_data files in efs folder ( file manager =show hidden files enabled)
Any chance I can fix this phone without the original efs folder backup?
Thanks.
Twisteddd said:
Hello
I have a Galaxy S4 i337m canadian model (firmware i337MVLUFNC1) that has unknown baseband and null imei.
WIfi and blutooth work. it does not recognize sim card.
I have been reading for two weeks about this problem and tried all the methods that i found on google.
I dont have efs backup.
I don't see the nv_data files in efs folder ( file manager =show hidden files enabled)
Any chance I can fix this phone without the original efs folder backup?
Thanks.
Click to expand...
Click to collapse
Haven't done it on the gs4 but you'd have to be able to connect it to qpst
I've actually been looking around at this but haven't been able to find much most information is under backup gs3 imei.
Asadullah said:
Haven't done it on the gs4 but you'd have to be able to connect it to qpst
I've actually been looking around at this but haven't been able to find much most information is under backup gs3 imei.
Click to expand...
Click to collapse
Thanks for replay
But that is a way to explore the phone files?
I did a lot of research to find out if the efs file on this model s4 actually contains the .nv_data.bin at all? or it is somewhere else?
Do you know if these files are actually missing from efs folder on i337m? or they are stored somewhere else?
Thanks.
Tried the following method with no luck
http://forum.xda-developers.com/showthread.php?t=1852255
Twisteddd said:
Tried the following method with no luck
http://forum.xda-developers.com/showthread.php?t=1852255
Click to expand...
Click to collapse
Taking the device back to your carrier and letting them factory restore it your best option other then that you are limited without a backup.
You can try this method... if your rooted but there are no guarantees.
Do these commands from ADB from your PC.
adb shell
su
mke2fs -t ext4 /dev/block/mmcblk0p10
mount -w -t ext4 /dev/block/mmcblk0p10
reboot
On your S4, download the Android Terminal Emulator from the Play Store and enter the following commands.
su
echo -n ON > /efs/FactoryApp/factorymode
sync
exit
exit
Reboot into Recovery, and preform a Factory Reset.
NighthawkXL said:
Taking the device back to your carrier and letting them factory restore it your best option other then that you are limited without a backup.
You can try this method... if your rooted but there are no guarantees.
Do these commands from ADB from your PC.
adb shell
su
mke2fs -t ext4 /dev/block/mmcblk0p10
mount -w -t ext4 /dev/block/mmcblk0p10
reboot
On your S4, download the Android Terminal Emulator from the Play Store and enter the following commands.
su
echo -n ON > /efs/FactoryApp/factorymode
sync
exit
exit
Reboot into Recovery, and preform a Factory Reset.
Click to expand...
Click to collapse
Tried and gave me the following error in shell
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>adb shell
[email protected]:/ $ su
su
root[email protected]:/ # mke2fs -t ext4 /dev/block/mmcblk0p10
mke2fs -t ext4 /dev/block/mmcblk0p10
mke2fs: invalid option -- t
BusyBox v1.22.1-Stericson (2014-01-25 17:27:18 CET) multi-call binary.
Usage: mke2fs [-Fn] [-b BLK_SIZE] [-i INODE_RATIO] [-I INODE_SIZE] [-m RESERVED_
PERCENT] [-L LABEL] BLOCKDEV [KBYTES]
-b BLK_SIZE Block size, bytes
-F Force
-i RATIO Max number of files is filesystem_size / RATIO
-I BYTES Inode size (min 128)
-L LBL Volume label
-m PERCENT Percent of blocks to reserve for admin
-n Dry run
1|[email protected]:/ #
Twisteddd said:
Thanks for replay
But that is a way to explore the phone files?
Thanks.
Click to expand...
Click to collapse
Thats how people were re-writing / repairing their meids
Asadullah said:
Thats how people were re-writing / repairing their meids
Click to expand...
Click to collapse
I cant find anything for i337m
I don't have service menu either. it says service mode on top of the phone and nothing on the screen.
This phone has to be completely reformated even the system partition. There must be a way of rebuilding the whole phone software.
Twisteddd said:
I cant find anything for i337m
I don't have service menu either. it says service mode on top of the phone and nothing on the screen.
This phone has to be completely reformated even the system partition. There must be a way of rebuilding the whole phone software.
Click to expand...
Click to collapse
Yeah its a rough road ahead of you. I know it can be done because people advertise it on craigslist. But I don't know exactly how.
get on stock nb1 and dial *#0808# change usb settings to dm+modem+adb might get you on the right road.
Looks like they use service box like z3x
I am trying to find alternative ways to do this because where I live, nobody offers this sort of services
Twisteddd said:
Looks like they use service box like z3x
I am trying to find alternative ways to do this because where I live, nobody offers this sort of services
Click to expand...
Click to collapse
There's definitely a different way z3x is such a rip off. I don't know it but as I get time I'm looking around. I'm wondering if you can locate all of the spots that carry the imei if you can change them to something else.
Can some one tell me if the following z3x box sold on ebay enough for repairing baseband on my phone i337m? Or do I need to buy the smart card with it also?
http://m.ebay.ca/itm/151500466184?nav=SEARCH
I know i will need the uart micro usb.
Thanks.
Does null IMEI cause unknown baseband or unknown baseband causes null IMEI?
Which one should be fixed first?
Also the service mode (*#0011#) being blank is it because of the modem is not working?
Thatnks.
When I try qpst in windows 7 to connect to the phone in order to rewrite IMEI;
I can change usb setting to RMNET by dialling *#0808#, the device manager it installs two usb ports under ports. Com6 and com7
RMNET SAMSUNG network driver installs but cant be started. it shows a yellow caution sign on the driver. Restarting windows and phone does not fix it.
When I enter the com ports to qpst configuration, it says active but says no phone.
Any help is appreciated.
Hello fellow xda'ers,
A few weeks I am experiencing a problem with my moto x style. The problem is that i don't have access anymore to my system folder. I have full root access, I can use rooted apps, but i can't switch my file system to r/w. Also when I boot into recovery I can flash roms etc, they are fully working, but once again, no system access. Also when I try to mount the system folder in recovery it seems it won't stick. Also when I use root explorer it says it switched to r/w but in fact it is r/o..
Can someone please hint me out what I could do to fix this problem?
Thanks in advance,
Bump
Have you tried something like this in terminal as root, or via ADB root?
Code:
mount -o rw,remount,rw /system
Then for r/o...
Code:
mount -o ro,remount,ro /system
quakeaz said:
Have you tried something like this in terminal as root, or via ADB root?
Then for r/o...
Click to expand...
Click to collapse
Thanks for your reply. But i still can't get system access.
bartjeh1991 said:
Thanks for your reply. But i still can't get system access.
Click to expand...
Click to collapse
Did you receive an error running the command? You are root, correct? Possibly just use:
Code:
mount -o remount,rw /system
Then run...
Code:
mount | grep system
Mine is read-only, but this should tell you if yours is rw or not.
Code:
u0 a114 clark:/ mount | grep system
/dev/block/bootdevice/by-name/system /system ext4 [B]ro[/B],seclabel,relatime,data=ordered 0 0
quakeaz said:
Did you receive an error running the command? You are root, correct? Possibly just use:
Then run...
Mine is read-only, but this should tell you if yours is rw or not.
Click to expand...
Click to collapse
I get this message everytime i run the commands you give me.
Hi,
I'm using a VS995 with Weta ROM. My phone keeps making a voice announcement of "roaming" . I can't find where to turn that off. Does anyone know how to disable these announcements?
Thanks
In case anyone comes across this issue, I found a file at /system/media/audio/eri/Roaming.wav
I did the following, from Android terminal emulator
su
#You should get a prompt from root manager to let the shell be root
mount -o rw,remount /system
cd /system/media/audio/eri
mv Roaming.wav Roaming.wav.sav
mount -o ro,remount /system
#This command will reboot your phone. It's Probably not needed.
reboot
It seems to have solved the issue, with no untoward effects, but wait for some of the more knowledgeable people on here to reply before doing this, in case this is a bad idea. I remember doing similar to kill the camera sound on earlier Adroidia, without harm, but ya never know.