Related
Ah... just having fun with root...!
So, if you want to get rid of the camera sounds, follow these steps on your rooted X10:
Prerequisite:
Rooted X10 using the root tutorial (http://forum.xda-developers.com/showthread.php?t=711907).
Busybox installed (download from market)
Fire up your favorite terminal emulator on the phone or launch a shell using "adb shell" (requires android sdk) and run along:
First make the /system partition writable:
Code:
# mount -o remount,rw -t yaffs2 /dev/mtdblock2 /system
Checkout these files:
Code:
# cd /system/media/audio/camera
# ls -l sound0
-rw-r--r-- 1 0 0 9164 Feb 21 02:48 no_sound.ogg
# ls -l sound1
-rw-r--r-- 1 0 0 4384 Jun 29 04:33 af_success.ogg
-rw-r--r-- 1 0 0 6515 Jun 29 04:33 self_timer.ogg
-rw-r--r-- 1 0 0 10806 Jun 29 04:33 shutter.ogg
-rw-r--r-- 1 0 0 5987 Jun 29 04:33 start_rec.ogg
-rw-r--r-- 1 0 0 6279 Jun 29 04:33 stop_rec.ogg
And there are more directories like sound2 and sound3. OK so basically, just replace each of the sounds under soundX folder with no_sound.ogg
Code:
# cp sound0/no_sound.ogg sound1/af_success.ogg
# cp sound0/no_sound.ogg sound1/self_timer.ogg
# cp sound0/no_sound.ogg sound1/shutter.ogg
# cp sound0/no_sound.ogg sound1/start_rec.ogg
# cp sound0/no_sound.ogg sound1/stop_rec.ogg
So when you've got sound1 folder fully patched, simply copy it over sound2 and sound3:
Code:
# cp sound1/* sound2/
# cp sound1/* sound3/
Et Voila!
(You may have to restart the Camera app by killing it via Task killer application or simply restart your phone)
Further development:
Want the phone to say "Say Cheese..."?
You can basically record your own sounds in "ogg" format and replace them in the respective folder either sound1, 2 or 3... but just make sure that you record sounds which are under 5 seconds or so... longer sounds really doesnt make much sense and I really don't know how the Camera app is designed to handle it... YMMV.
You pervy, upskirt-shooting /b/-tard.
Actually, I can set there to be no camera-sound through the settings. Can't you guys do that?
pally777 said:
Actually, I can set there to be no camera-sound through the settings. Can't you guys do that?
Click to expand...
Click to collapse
yea i think I had that option before I rooted my phone... but the japanese firmware that the root relies upon doesnt !
j4mm3r said:
yea i think I had that option before I rooted my phone... but the japanese firmware that the root relies upon doesnt !
Click to expand...
Click to collapse
Slightly off-topic: Didn't Japan recently made it a law that cameras had to make a sound to avoid the secret upskirt-shots the japanese guys are so fond of?
ddewbofh said:
Slightly off-topic: Didn't Japan recently made it a law that cameras had to make a sound to avoid the secret upskirt-shots the japanese guys are so fond of?
Click to expand...
Click to collapse
thats it... this is why i wanted to help our japanese fan boys!!
or.. you know.. /system/default.prop
ro.camera.sound.forced=0
...
HI,
I need big help, any comments are appreciated.
I was rooting my kindle again after 6.2.1 update.
Everything was OK, until I changed the /system/apps folder permission to r/w for all users using file exporer.
After that, I started not to be able to launch anything.
I tied to reboot and my kindle now stuck at the screen saying "kindle fire" and it flashes every 10 secs or so.
I tried Kindle_Fire_Utility_v0.9.1 several options with no success.
I can connect via adb and see the directories but I can not do adb root.
It mount the files system as read only.
c:\Program Files (x86)\Android\android-sdk\platform-tools>adb root
adbd cannot run as root in production builds
It is almost like, everything is fine but the system can not find the apps to run.
Is there any way I can recover?
Here are directories and permissions:
c:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell ls -l /system
drwxr-xr-x root root 1969-12-31 19:00 lost+found
drwsrwsrwt root root 2011-12-23 00:57 app
drwxr-xr-x root shell 2011-12-23 00:57 bin
-rw-r--r-- root root 2151 2008-08-01 08:00 build.prop
drwxr-xr-x root root 2011-12-23 00:57 etc
drwxr-xr-x root root 2011-12-23 00:57 fonts
drwxr-xr-x root root 2011-12-23 00:57 framework
drwxr-xr-x root root 2011-12-23 00:57 lib
drwxr-xr-x root root 2011-12-23 00:57 media
drwxr-xr-x root root 2011-12-23 00:57 tts
drwxr-xr-x root root 2011-12-23 00:57 usr
drwxr-xr-x root shell 2011-12-23 00:57 vendor
drwxr-xr-x root shell 2012-01-01 20:57 xbin
c:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell ls -l /system/app
-rwsr-sr-x root root 2669573 2008-08-01 08:00 ATVAndroidClient.apk
-rwsr-sr-x root root 233689 2008-08-01 08:00 AccountAndSyncSettings.apk
-rwsr-sr-x root root 3581882 2008-08-01 08:00 AmazonVenezia.apk
-rwsr-sr-x root root 29574 2008-08-01 08:00 ApplicationsProvider.apk
-rwsr-sr-x root root 3574986 2008-08-01 08:00 AudibleAndroidApplication-venezia.apk
-rwsr-sr-x root root 164188 2008-08-01 08:00 CSApp-unsigned.apk
-rwsr-sr-x root root 152004 2008-08-01 08:00 CalendarProvider.apk
-rwsr-sr-x root root 116225 2008-08-01 08:00 CertInstaller.apk
-rwsr-sr-x root root 2981513 2008-08-01 08:00 Cloud9-unsigned.apk
-rwsr-sr-x root root 57201 2008-08-01 08:00 Cloud9SystemBrowserProvider-unsigned.apk
-rwsr-sr-x root root 2049942 2008-08-01 08:00 Contacts.apk
-rwsr-sr-x root root 145545 2008-08-01 08:00 ContactsProvider.apk
-rwsr-sr-x root root 20748 2008-08-01 08:00 DefaultContainerService.apk
-rwsr-sr-x root root 196150 2008-08-01 08:00 DownloadProvider.apk
-rwsr-sr-x root root 106749 2008-08-01 08:00 DownloadProviderUi.apk
-rwsr-sr-x root root 32432 2008-08-01 08:00 DrmProvider.apk
-rwsr-sr-x root root 2314082 2008-08-01 08:00 Email.apk
-rwsr-sr-x root root 16891 2008-08-01 08:00 Facebook.apk
-rwsr-sr-x root root 833544 2008-08-01 08:00 Gallery3D.apk
-rwsr-sr-x root root 22792 2008-08-01 08:00 HTMLViewer.apk
-rwsr-sr-x root root 1685594 2008-08-01 08:00 IMDb-2.3.apk
-rwsr-sr-x root root 16424248 2008-08-01 08:00 KindleForOtter.apk
-rwsr-sr-x root root 1082002 2008-08-01 08:00 LatinIME.apk
-rwsr-sr-x root root 12174501 2008-08-01 08:00 Launcher.apk
-rwsr-sr-x root root 1140587 2008-08-01 08:00 LiveWallpapers.apk
-rwsr-sr-x root root 51276 2008-08-01 08:00 LiveWallpapersPicker.apk
-rwsr-sr-x root root 224152 2008-08-01 08:00 MagicSmokeWallpapers.apk
-rwsr-sr-x root root 20783 2008-08-01 08:00 MarketIntentProxy.apk
-rwsr-sr-x root root 62533 2008-08-01 08:00 MediaProvider.apk
-rwsr-sr-x root root 149113 2008-08-01 08:00 MyAccount-unsigned.apk
-rwsr-sr-x root root 253119 2008-08-01 08:00 OOBE-unsigned.apk
-rwsr-sr-x root root 26979 2008-08-01 08:00 OTASilentInstall.apk
Some more and strange info:
$ cd /mnt
$ ls -l
ls -l
drwxr-xr-x root system 2012-01-02 01:38 obb
drwxr-xr-x root system 2012-01-02 01:38 asec
drwx------ root root 2012-01-02 01:38 secure
d--------- system system 2012-01-02 01:38 sdcard
I can not do su, I can not reach any directory. (including sdcard).
I can not do even whoami:
$ whoami
whoami
whoami: permission denied
as a first step you could try if this is successfull:
adb shell
look if your prompt is $ or # - if it is $ type su - must change to #
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod 755 /system/app
if not you can try to install twrp (if you not allready have)
http://forum.xda-developers.com/showthread.php?t=1414832
and flash a backup, the stockrom or one of the roms available in the forum
HI Thanks for the reply.
adb shell works and prompt changes to #
su does not work.
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod 755 /system/app
does not work, says I don't have the permission. I think this is because of readonly file system.
have you tried the second solution ?
I will try tonight but, I am not sure whether it will work. Because, if I am not calling wrong, I tried to get into data directory last night and could not.
But I will try tonight again and will let you know.
Thanks again.
Second solution works, I fixed this same problem that way.
BUT. Be careful what you do next, as I flashed the stock rom and now my Fire is bricked again and with a non working adb. So, again, be VERY CAREFUL
osozraz,
So given you experience, which rom should I use?
absolutely right ! - i would suggest one of the prerooted stock roms from here
http://forum.xda-developers.com/showthread.php?t=1402440
uniqua97 said:
osozraz,
So given you experience, which rom should I use?
Click to expand...
Click to collapse
I can´t say, as my Fire is still bricked and that was the first rom i installed. For my experience, DON´T flash the stock rom.
Thanks a lot for all the help.
The solution about fbmode in the following thread is worked:
http://forum.xda-developers.com/showthread.php?t=1414832
Then I installed TWRP using Kindle Fire Utility v0.9.1:
http://forum.xda-developers.com/showthread.php?t=1399889
Then I used update-6.2.1-rooted-unsecureboot.zip with TWRP:
http://forum.xda-developers.com/showthread.php?t=1402440
The videos from the following links are also awesome:
http://www.jayceooi.com/2011/12/29/how-to-install-twrp-2-0-recovery-on-kindle-fire-video/
http://www.jayceooi.com/2011/12/30/...droid-rom-on-kindle-fire-with-twrp-2-0-video/
There are more videos in those links.
Hope this helps to others as well.
Problem fixed !!! Thansk!
Any ONE can help?
My kindle fire already rooted, every time i want to install the input method by adb remount is fail.
remount failed: operation not permitted!
how can i fix it??
would thing you get the $ prompt if you open the adb shell
enter "su" - the prompt should change to #
then the remount command should succeed
enter "su" - the prompt should change to # in shell mode
then type : # adb remount ?
could you get me a detail command set ?. because kindle fire is my first's android device , BIG THANKS!
this should be the way it works:
adb shell
$ su
su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
#
the bold commands are the ones to enter ...
My file is saved in c:\apps\hk.cedime.inputmethod.apk
and also have a copy in c:\adb\hk.cedime.inputmethod.apk
Show many error ??? Any expert can help?
adb shell
$ su
su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
# install c:\apps\hk.cedime.inputmethod.apk /system/app/
install c:\apps\hk.cedime.inputmethod.apk /system/app/
install: can't stat ' c:appshk.cedime.inputmethod.apk' : No such file or directory
# install hk.cedime.inputmethod.apk /system/app/
install hk.cedime.inputmethod.apk /system/app/
install: can't stat ' hk.cedime.inputmethod.apk' : No such file or directory
#cp hk.cedime.inputmethod.apk /system/app/
cp hk.cedime.inputmethod.apk /system/app/
cp: can't stat ' hk.cedime.inputmethod.apk' : No such file or directory
#cp c:\apps\hk.cedime.inputmethod.apk /system/app/
cp c:\apps\hk.cedime.inputmethod.apk /system/app/
cp: can't stat ' c:appshk.cedime.inputmethod.apk' : No such file or directory
install: can't stat ' c:appshk.cedime.inputmethod.apk' : No such file or directory
Click to expand...
Click to collapse
it don't find the .apk file
i use to put the files to install in the directory where adb.exe resides
and do the command without a path ie: install hk.cedime.inputmethod.apk /system/app/
furthermore i'm not shure if the command works inside the adb shell
would also try (from command prompt):
adb install c:\apps\hk.cedime.inputmethod.apk /system/app/
or if .apk in current directory (where adb resides):
adb install hk.cedime.inputmethod.apk /system/app/
Adb command is my first choice
But the system show the error : can't find '/system/app/' to install
then it seems not to be mounted ...
try to check with:
"adb shell"
"su"
"mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system"
"cd \system"
"ls -l" -> any directory listing here ?
"cd app"
"ls -l" -> any apk's listed ?
OH! my God!
c:\ADB>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
6C18000600000001 device
c:\ADB>adb shell
$ su
su
# mount -o remount, rw -t yaffs2/dev/block/mtdblock3/system
mount -o remount, rw -t yaffs2/dev/block/mtdblock3/system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
#
no problem - if it's not mounted it's hard to remount
would try:
"mount /system" in adb shell
or
"adb shell mount -o remount rw /system" from the command prompt
Sorry, many problem can't fix...............
c:\ADB>adb shell mount -o remount rw/system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
c:\ADB>
c:\ADB>adb shell mount -o remount rw/system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
c:\ADB>adb shell
$ su
su
# mount -o remount, rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount, rw -t yaffs2 /dev/block/mtdblock3 /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
# ls -l
ls -l
dr-x------ root root 2012-03-19 05:51 config
drwxrwx--- system system 2012-03-20 07:00 dropbox
drwxrwx--- system cache 2012-03-19 05:51 cache
lrwxrwxrwx root root 2012-03-19 05:51 sdcard -> /mnt/sdcard
drwxr-xr-x root root 2012-03-19 05:51 acct
drwxrwxr-x root system 2012-03-19 05:51 mnt
lrwxrwxrwx root root 2012-03-19 05:51 vendor -> /system/vendor
lrwxrwxrwx root root 2012-03-19 05:51 d -> /sys/kernel/debug
lrwxrwxrwx root root 2012-03-19 05:51 etc -> /system/etc
-rw-r--r-- root root 4203 1969-12-31 16:00 ueventd.rc
-rw-r--r-- root root 840 1969-12-31 16:00 ueventd.omap4430.rc
-rw-r--r-- root root 0 1969-12-31 16:00 ueventd.goldfish.rc
drwxr-xr-x root root 2012-01-19 04:27 system
drwxr-xr-x root root 2012-03-19 05:51 sys
drwxr-x--- root root 1969-12-31 16:00 sbin
dr-xr-xr-x root root 1969-12-31 16:00 proc
-rwxr-x--- root root 14869 1969-12-31 16:00 init.rc
-rwxr-x--- root root 11357 1969-12-31 16:00 init.omap4430.rc
-rwxr-x--- root root 1677 1969-12-31 16:00 init.goldfish.rc
-rwxr-x--- root root 94200 1969-12-31 16:00 init
-rw-r--r-- root root 118 1969-12-31 16:00 default.prop
drwxrwx--x system system 2012-03-18 06:53 data
drwx------ root root 2012-01-09 22:20 root
drwxr-xr-x root root 2012-03-19 06:01 dev
# cd app
cd app
cd: can't cd to app
#
from your post #5:
adb shell
$ su
su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
this has seemed to work - or was there allways a error message following up which you did'nt copy and paste ?
usually "mount /system" is sufficient - "mount -w /system" should work too
# cd app
cd app
cd: can't cd to app
Click to expand...
Click to collapse
if you look to the directory listing you are on the root - there is no directory or mountpoint "app" - it is in the system directory - the command should be:
"cd \system"
"ls -l" -> any directory listing here ?
and then if you are in "system"
"cd app"
"ls -l" -> any apk's listed ?
as in post #8
Expert ! Next step what can i do?
C:\ADB>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
6C18000600000001 device
C:\ADB>adb shell mount -o remount rw /system
mount: Operation not permitted
C:\ADB>adb shell
$ su
su
# mount -o remount, rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount, rw -t yaffs2 /dev/block/mtdblock3 /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
# cd \system
cd \system
# ls -l
ls -l
drwxr-xr-x root root 1969-12-31 16:00 lost+found
drwxr-xr-x root root 2012-03-19 05:49 app
drwxr-xr-x root shell 2012-03-17 18:19 bin
-rw-r--r-- root root 2151 2008-08-01 05:00 build.prop
drwxr-xr-x root root 2012-01-19 04:27 etc
drwxr-xr-x root root 2012-01-19 04:27 fonts
drwxr-xr-x root root 2012-01-19 04:27 framework
drwxr-xr-x root root 2012-01-19 04:27 lib
drwxr-xr-x root root 2012-01-19 04:27 media
drwxr-xr-x root root 2012-01-19 04:27 tts
drwxr-xr-x root root 2012-01-19 04:27 usr
drwxr-xr-x root shell 2012-01-19 04:27 vendor
drwxr-xr-x root shell 2012-03-17 20:51 xbin
# cd app
cd app
# ls -l
ls -l
-rw-r--r-- root root 2669573 2008-08-01 05:00 ATVAndroidClient.apk
-rw-r--r-- root root 233689 2008-08-01 05:00 AccountAndSyncSettings.ap
k
-rw-r--r-- root root 3581879 2008-08-01 05:00 AmazonVenezia.apk
-rw-r--r-- root root 29574 2008-08-01 05:00 ApplicationsProvider.apk
-rw-r--r-- root root 3574986 2008-08-01 05:00 AudibleAndroidApplication
-venezia.apk
-rw-r--r-- root root 164188 2008-08-01 05:00 CSApp-unsigned.apk
-rw-r--r-- root root 152004 2008-08-01 05:00 CalendarProvider.apk
-rw-r--r-- root root 116225 2008-08-01 05:00 CertInstaller.apk
-rw-r--r-- root root 4019454 2008-08-01 05:00 Cloud9-release-unsigned.a
pk
-rw-r--r-- root root 57208 2008-08-01 05:00 Cloud9SystemBrowserProvid
er-unsigned.apk
-rw-r--r-- root root 2049942 2008-08-01 05:00 Contacts.apk
-rw-r--r-- root root 145545 2008-08-01 05:00 ContactsProvider.apk
-rw-r--r-- root root 20748 2008-08-01 05:00 DefaultContainerService.a
pk
-rw-r--r-- root root 196150 2008-08-01 05:00 DownloadProvider.apk
-rw-r--r-- root root 106749 2008-08-01 05:00 DownloadProviderUi.apk
-rw-r--r-- root root 32432 2008-08-01 05:00 DrmProvider.apk
-rw-r--r-- root root 2315338 2008-08-01 05:00 Email.apk
-rw-r--r-- root root 16892 2008-08-01 05:00 Facebook.apk
-rw-r--r-- root root 833544 2008-08-01 05:00 Gallery3D.apk
-rw-r--r-- root root 22792 2008-08-01 05:00 HTMLViewer.apk
-rw-r--r-- root root 1685594 2008-08-01 05:00 IMDb-2.3.apk
-rw-r--r-- root root 16424244 2008-08-01 05:00 KindleForOtter.apk
-rw-r--r-- root root 1082002 2008-08-01 05:00 LatinIME.apk
-rw-r--r-- root root 12174497 2008-08-01 05:00 Launcher.apk
-rw-r--r-- root root 1140587 2008-08-01 05:00 LiveWallpapers.apk
-rw-r--r-- root root 51276 2008-08-01 05:00 LiveWallpapersPicker.apk
-rw-r--r-- root root 224152 2008-08-01 05:00 MagicSmokeWallpapers.apk
-rw-r--r-- root root 20778 2008-08-01 05:00 MarketIntentProxy.apk
-rw-r--r-- root root 62533 2008-08-01 05:00 MediaProvider.apk
-rw-r--r-- root root 149119 2008-08-01 05:00 MyAccount-unsigned.apk
-rw-r--r-- root root 253116 2008-08-01 05:00 OOBE-unsigned.apk
-rw-r--r-- root root 26983 2008-08-01 05:00 OTASilentInstall.apk
-rw-r--r-- root root 110563 2008-08-01 05:00 OtterAppManager.apk
-rw-r--r-- root root 1907710 2008-08-01 05:00 OtterTutorial.apk
-rw-r--r-- root root 122758 2008-08-01 05:00 PackageInstaller.apk
-rw-r--r-- root root 22282 2008-08-01 05:00 PicoTts.apk
-rw-r--r-- root root 10496 2008-08-01 05:00 Provision.apk
-rw-r--r-- root root 2305323 2008-08-01 05:00 Pulse-amazon.apk
-rw-r--r-- root root 412698 2008-08-01 05:00 QuickSearchBox.apk
-rw-r--r-- root root 320688 2008-08-01 05:00 QuickSettings.apk
-rw-r--r-- root root 6302776 2008-08-01 05:00 Quickoffice_AMAZON_4.1.46
7_VC.apk
-rw-r--r-- root root 3751962 2008-08-01 05:00 Settings.apk
-rw-r--r-- root root 48682 2008-08-01 05:00 SettingsProvider.apk
-rw-r--r-- root root 604484 2008-08-01 05:00 SystemUI.apk
-rw-r--r-- root root 30187 2008-08-01 05:00 TtsService.apk
-rw-r--r-- root root 16928 2008-08-01 05:00 UserDictionaryProvider.ap
k
-rw-r--r-- root root 165579 2008-08-01 05:00 VisualizationWallpapers.a
pk
-rw-r--r-- root root 34247 2008-08-01 05:00 VpnServices.apk
-rw-r--r-- root root 1669753 2008-08-01 05:00 Windowshop.apk
-rw-r--r-- root root 6113490 2008-08-01 05:00 air_runtime.apk
-rw-r--r-- root root 2109670 2008-08-01 05:00 amazonmp3-unsigned.apk
-rw-r--r-- root root 2500819 2008-08-01 05:00 com.amazon.dcp.apk
-rw-r--r-- root root 45888 2008-08-01 05:00 oem_install_flash_player_
signed.apk
-rw-r--r-- root root 843503 2008-02-28 10:33 Superuser.apk
-rw-rw-rw- root root 89707 2011-12-07 02:26 GoogleFeedback.apk
-rw-rw-rw- root root 1401398 2011-12-07 02:13 GoogleServicesFramework.a
pk
-rw-rw-rw- root root 1529836 2011-12-07 02:15 Vending.apk
-rw-rw-rw- root root 4089926 2011-12-07 02:22 GO_Launcher_EX_2.65.apk
-rw-rw-rw- root root 2053065 2012-03-19 05:49 hk.cedime.inputmethod.apk
#
C:\ADB>adb shell mount -o remount rw /system
mount: Operation not permitted
Click to expand...
Click to collapse
as you run a unsecure kernel i think the command should be:
adb shell su -c "remount"
or
adb shell su -c "mount -o remount rw /system"
C:\ADB>adb shell
$ su
su
# mount -o remount, rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount, rw -t yaffs2 /dev/block/mtdblock3 /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
the second attempt succeeded - so your question seems to be answered or not ?
Any ONE can help?
My kindle fire already rooted, every time i want to install the input method by adb remount is fail.
remount failed: operation not permitted!
how can i fix it??
Click to expand...
Click to collapse
Expert!
i follow this link
http://forum.xda-developers.com/showthread.php?t=1364543
to fixed my problem, Thanks for your support again!!
glad to help ...
please mark the subject of the topic (edit first post) with [Solved]
K, i've got a wii emulator, but i don't understand how to run these commands !!! +_+
To increase stability on Galaxy S4 and other Adreno 3xx devices with driver v14, you need to root and run the following commands on the device as root.
Code:
echo 0 > /sys/kernel/debug/kgsl/kgsl-3d0/fast_hang_detect
echo 0 > /sys/kernel/debug/kgsl/kgsl-3d0/ft_pagefault_policy
echo 0 > /sys/kernel/debug/kgsl/kgsl-3d0/ft_policy
echo 0 > /sys/kernel/debug/kgsl/kgsl-3d0/ib_check
echo 0 > /sys/kernel/debug/kgsl/kgsl-3d0/long_ib_detect
Can someone please educate me on how this is suppose to work? do i need an android terminal? or how do i go about running these commands?
(yes my phone is rooted)
Thanks
Ryan
milkydude12 said:
i don't understand how to run these commands
Click to expand...
Click to collapse
These are system commands and you need to run them from the "command line". The easiest way to do that would be to install a terminal application. Android Terminal Emulator by Jack Palevich is one good choice. Or you could run an adb shell.
After you install terminal emulator, enter
su [enter]
Click to expand...
Click to collapse
"su" is the command for superuser (root access). Then you can use the system configuration commands that you have for your wii emulator.
If any commands need to be reentered each time you use your emulator, then you could use a scripting app like gscript light which can be configured to enter these commands from a bookmark. i.e. just click on a bookmark and it will run a set of commands for you.
.
Hi,
Thanks for replying!!! I've a problem though , after i enter su (enter) then grant superuser, i type in echo 0 > /sys/kernel/debug/kgsl/kgsl-3d0/fast_hang_detect
then i get no such file or directory , what am i doing wrong???
milkydude12 said:
Hi,
Thanks for replying!!! I've a problem though , after i enter su (enter) then grant superuser, i type in echo 0 > /sys/kernel/debug/kgsl/kgsl-3d0/fast_hang_detect
then i get no such file or directory , what am i doing wrong???
Click to expand...
Click to collapse
Do you have those directories on your phone? Where did you get the commands to type in? Are they specific to the s4?
jd1639 said:
Do you have those directories on your phone? Where did you get the commands to type in? Are they specific to the s4?
Click to expand...
Click to collapse
I got the commands from here https://forums.dolphin-emu.org/Thread-opengl-es-3-guide i apologize if im not supposed to post link +_+
I can't add much more than jd1639 already suggested. These commands would just make a temporary configuration change to half a dozen driver settings in aid of your emulator program. The "echo 0" command ensures that a particular setting is set to "0", if the target file exists.
Check for typos. If there weren't any typos, then it would seem likely that the information from the original thread is inaccurate or out of date. What model of phone are you trying this on? The original thread refers to the i9505 and similar phones. Is your phone a i9505? The fact that you're posting this in an AT&T, et al forum suggest that you might actually have a i337 /i337m phone. Depending on what model you actually have, your phone may have a Snapdragon 800 or Exynos processor rather than the Snapdragon 600.
The drivers may or may not be the same across different phones and processors. Or the drivers names may have changed in a subsequent firmware update. You check your filesystem to see if those paths exist or if the file names can be found elsewhere. Then look to the emulator thread for further guidance.
I had a quick look at a S3 and some, but not all of those files exist. If you find the same thing on your S4, then you'll have to refer to the emulator thread to discern if you need to have all of those items to enable your emulator or if a subset will suffice.
You can probably just create any "missing" files for a workable solution. They're just text files that the drivers refer to for guidance. It's something that I'd at least try in your place. However while I don't perceive any real risk in that i.e. worst case it wouldn't boot and you'd need to restore a backup.. don't look to me if your phone unexpectedly wimpers, fails or becomes sentient and disagrees. Anything you actually do is at your own risk.
You can search paths and file names as follows below. And you should be able to use the touch, mv or cp commands (or install a text editor) to create a missing file.
$ su
# cd /sys/kernel/debug/kgsl/kgsl-3d0
# ls -la
# find / -name fast_hang_detect
.
fffft said:
I can't add much more than jd1639 already suggested. These commands would just make a temporary configuration change to half a dozen driver settings in aid of your emulator program. The "echo 0" command ensures that a particular setting is set to "0", if the target file exists.
Check for typos. If there weren't any typos, then it would seem likely that the information from the original thread is inaccurate or out of date. What model of phone are trying this on? The original thread refers to the i9505 and similar phones. Is your phone a i9505? The fact that you're posting this in an AT&T, et al forum suggest that you might actually have a i337 /i337m phone. Depending on what model you actually have, your phone may have a Snapdragon 800 or Exynos processor rather than the Snapdragon 600.
The drivers may or may not be the same across different phones and processors. Or the drivers names may have changed in a subsequent firmware update. You should look at your filesystem as jd1639 suggested to see if those paths exist or if the file names can be found elsewhere. And if necessary, re-read the emulator thread for further guidance.
I had a quick look at a S3 and some, but not all of those files exist. If you find the same thing on your S4, then you'll have to refer to the emulator thread to discern if you need to have all of those items to enable your emulator or if a subset will suffice.
You can probably just create any "missing" files for a workable solution. They're just text files that the drivers refer to for guidance. It's something that I'd at least try in your place. However while I don't perceive any real risk in that i.e. worst case it wouldn't boot and you'd need to restore a backup.. don't look to me if your phone unexpectedly wimpers, fails or becomes sentient and disagrees. Anything you actually do is at your own risk.
You can search paths and file names as follows below. And you should be able to use the touch, mv or cp commands to create a missing file.
$ su
# cd /sys/kernel/debug/kgsl/kgsl-3d0
# ls -la
# find / -name fast_hang_detect
.
Click to expand...
Click to collapse
Hi, I have the I337m variety of the Samsung S4 will that make a difference?
milkydude12 said:
Hi, I have the I337m variety of the Samsung S4 will that make a difference?
Click to expand...
Click to collapse
The answer to that will be in your emulator thread.
More to the point, you haven't done your homework yet. Do those paths and files exist on your phone? Does the emulator thread clarify if all of those settings are required? And did you try creating any missing files? People are trying to help you here, but we can't see what your phone screen actually shows. And you should be doing most of the work to see what does or doesn't work.
.
[email protected]:/ $ su
[email protected]:/ # cd /sys/kernal/debugkgsl-3d0
tmp-mksh: cd: /sys/kernal/debugkgsl-3d0: No such file or directory
2|[email protected]:/ # ls -la
-rw-r--r-- root root 4721 1969-12-31 17:00 MSM8960_lpm.rc
drwxr-xr-x root root 1970-05-26 22:16 acct
drwxrwx--- system cache 2014-02-07 20:41 cache-rwxr-x--- root root 268036 1969-12-31 17:00 charger
dr-x------ root root 1970-05-26 22:16 config
lrwxrwxrwx root root 1970-05-26 22:16 d -> /sys/kernel/debug
drwxrwx--x system system 2014-02-07 19:42 data
drwxrwx--- system system 1970-05-26 22:16 data_1
drwxrwx--- system system 1970-05-26 22:16 data_2
drwxrwx--- system system 1970-05-26 22:16 data_3
-rw-r--r-- root root 165 1969-12-31 17:00 default.prop
drwxr-xr-x root root 2014-02-07 01:35 dev
drwxrwx--x system radio 2014-01-31 20:30 efs
lrwxrwxrwx root root 1970-05-26 22:16 etc -> /system/etc
-rw-r--r-- root root 21233 1969-12-31 17:00 file_contexts
dr-xr-x--- system system 1970-05-26 22:16 firmware
dr-xr-x--- system system 1970-05-26 22:16 firmware-mdm
-rw-r----- root root 1494 1969-12-31 17:00 fstab.qcom
-rwxr-x--- root root 171036 1969-12-31 17:00 init
-rwxr-x--- root root 3068 1969-12-31 17:00 init.carrier.rc
-rwxr-x--- root root 769 1969-12-31 17:00 init.container.rc
-rwxr-x--- root root 6737 1969-12-31 17:00 init.qcom.class_core.sh
-rwxr-x--- root root 2320 1969-12-31 17:00 init.qcom.class_main.sh
-rwxr-x--- root root 4266 1969-12-31 17:00 init.qcom.early_boot.sh
-rwxr-x--- root root 5142 1969-12-31 17:00 init.qcom.lpm_boot.sh
-rwxr-x--- root root 22920 1969-12-31 17:00 init.qcom.rc
-rwxr-x--- root root 3045 1969-12-31 17:00 init.qcom.ril.sh
-rwxr-x--- root root 4486 1969-12-31 17:00 init.qcom.sh
-rwxr-x--- root root 3830 1969-12-31 17:00 init.qcom.syspart_fixup.sh
-rwxr-x--- root root 35468 1969-12-31 17:00 init.qcom.usb.rc
-rwxr-x--- root root 6004 1969-12-31 17:00 init.qcom.usb.sh
-rwxr-x--- root root 41170 1969-12-31 17:00 init.rc
-rwxr-x--- root root 9314 1969-12-31 17:00 init.target.rc
-rwxr-x--- root root 1795 1969-12-31 17:00 init.trace.rc
-rwxr-x--- root root 3915 1969-12-31 17:00 init.usb.rc
drwxrwxr-x root system 1970-05-26 22:16 mnt
drwxrwxr-x root system 1970-05-26 22:16 mnt_1drwxr-xr-x system system 1970-05-26 22:16 persdata
drwxrwx--x system system 1970-05-26 22:16 preload
dr-xr-xr-x root root 1969-12-31 17:00 proc
-rw-r--r-- root root 2838 1969-12-31 17:00 property_contexts
drwxr-xr-x root root 1969-12-31 17:00 res
drwx------ root root 2013-11-15 08:26 root
drwxr-x--- root root 1969-12-31 17:00 sbin
lrwxrwxrwx root root 1970-05-26 22:16 sdcard -> /storage/emulated/legacy
-rw-r--r-- root root 3887 1969-12-31 17:00 seapp_contexts
-rw-r--r-- root root 610434 1969-12-31 17:00 sepolicy
-rw-r--r-- root root 207 1969-12-31 17:00 sepolicy_version
dr-xr-x--- system sdcard_r 1970-05-26 22:16 storage
dr-xr-xr-x root root 1970-05-26 22:16 sys
drwxr-xr-x root root 1970-03-21 22:11 system
drwxr-xr-x root root 2014-01-31 20:30 tmp-mksh
lrwxrwxrwx root root 1970-05-26 22:16 tombstones -> /data/tombstones
-rw-r--r-- root root 6662 1969-12-31 17:00 ueventd.qcom.rc
-rw-r--r-- root root 4794 1969-12-31 17:00 ueventd.rc
lrwxrwxrwx root root 1970-05-26 22:16 vendor -> /system/vendor
[email protected]:/ # find / -namefast_hang_detect
find: unrecognized: -namefast_hang_detect
BusyBox v1.21.1-Stericson (2013-09-26 14:33:26 BST) multi-call binary.
Usage: find [PATH]... [OPTIONS] [ACTIONS]
Search for files and perform actions on them.
First failed action stops processing of current file.
Defaults: PATH is current directory, action is '-print'
-follow Follow symlinks
-xdev Don't descend directories on other filesystems
-maxdepth N Descend at most N levels. -maxdepth 0 applies
actions to command line arguments only
-mindepth N Don't act on first N levels
-depth Act on directory *after* traversing it
Actions:
( ACTIONS ) Group actions for -o / -a
! ACT Invert ACT's success/failure
ACT1 [-a] ACT2 If ACT1 fails, stop, else do ACT2
ACT1 -o ACT2 If ACT1 succeeds, stop, else do ACT2 Note: -a has higher priority than -o -name PATTERN Match file name (w/o directory name) to PATTERN
-iname PATTERN Case insensitive -name
-path PATTERN Match path to PATTERN
-ipath PATTERN Case insensitive -path
-regex PATTERN Match path to regex PATTERN
-type X File type is X (one of: f,d,l,b,c,...)
-perm MASK At least one mask bit (+MASK), all bits (-MASK),
or exactly MASK bits are set in file's mode
-mtime DAYS mtime is greater than (+N), less than (-N),
or exactly N days in the past
-mmin MINS mtime is greater than (+N), less than (-N),
or exactly N minutes in the past
-newer FILE mtime is more recent than FILE's
-inum N File has inode number N
-user NAME/ID File is owned by given user
-group NAME/ID File is owned by given group
-size N[bck] File size is N (c:bytes,k:kbytes,b:512 bytes(def.))
+/-N: file size is bigger/smaller than N
-links N Number of links is greater than (+N), less than (-N),
or exactly N
-prune If current file is directory, don't descend into it
If none of the following actions is specified, -print is assumed
-print Print file name
-print0 Print file name, NUL terminated
-exec CMD ARG ; Run CMD with all instances of {} replaced by
file name. Fails if CMD exits with nonzero
-delete Delete current file/directory. Turns on -depth option
1|[email protected]:/ #
That is what i get, for the life of me i can't figure out if that means i have it or i don't. "On the Thread it says To increase stability on Galaxy S4 and other Adreno 3xx devices with driver v14, you need to root and run the following commands on the device as root."
So I'm assuming i require all of them to work in order for any difference. Certain sites list the I337m varient as one of which supports Open Gl ES 3 so i assume it would work
All right, I can understand how a lot of this might be a challenge to understand if you have no experience with linux. But you at least need to make sure that you aren't making typos when using these commands.
e.g.
[email protected]:/ # find / -namefast_hang_detect
Click to expand...
Click to collapse
You missed a space between -name and the actual file name. And yes, that is critical. Nothing here is likely to work if you have typos. Try the following and paste the results back here. And I or someone else will better understand what is going on::
$ su
# cd /sys/kernel/debug/kgsl/kgsl-3d0
# ls -la
(exactly as above and paste the result for us).
If you are ambitious then also try the following for any "missing" files and let us know if that succeeds in getting your emulator up and running.
e.g.
# touch /sys/kernel/debug/kgsl/kgsl-3d0/fast_hang_detect
# echo 0 > /sys/kernel/debug/kgsl/kgsl-3d0/fast_hang_detect
.
:S thanks i didn't know i had missed a space, and yea i have little to no experience with linux.
[email protected]:/ $ su
[email protected]:/ # cd /sys/kernal/debug/kgsl/3d0
tmp-mksh: cd: /sys/kernal/debug/kgsl/3d0: No such file or directory
2|[email protected]:/ # ls -la
-rw-r--r-- root root 4721 1969-12-31 17:00 MSM8960_lpm.rc
drwxr-xr-x root root 1970-05-26 22:16 acct
drwxrwx--- system cache 2014-02-07 22:44 cache
-rwxr-x--- root root 268036 1969-12-31 17:00 charger
dr-x------ root root 1970-05-26 22:16 config
lrwxrwxrwx root root 1970-05-26 22:16 d -> /sys/kernel/debug
drwxrwx--x system system 2014-02-07 19:42 data
drwxrwx--- system system 1970-05-26 22:16 data_1
drwxrwx--- system system 1970-05-26 22:16 data_2
drwxrwx--- system system 1970-05-26 22:16 data_3
-rw-r--r-- root root 165 1969-12-31 17:00 default.prop
drwxr-xr-x root root 2014-02-07 01:35 dev
drwxrwx--x system radio 2014-01-31 20:30 efs
lrwxrwxrwx root root 1970-05-26 22:16 etc -> /system/etc
-rw-r--r-- root root 21233 1969-12-31 17:00 file_contexts
dr-xr-x--- system system 1970-05-26 22:16 firmware
dr-xr-x--- system system 1970-05-26 22:16 firmware-mdm
-rw-r----- root root 1494 1969-12-31 17:00 fstab.qcom
-rwxr-x--- root root 171036 1969-12-31 17:00 init
-rwxr-x--- root root 3068 1969-12-31 17:00 init.carrier.rc
-rwxr-x--- root root 769 1969-12-31 17:00 init.container.rc
-rwxr-x--- root root 6737 1969-12-31 17:00 init.qcom.class_core.sh
-rwxr-x--- root root 2320 1969-12-31 17:00 init.qcom.class_main.sh
-rwxr-x--- root root 4266 1969-12-31 17:00 init.qcom.early_boot.sh
-rwxr-x--- root root 5142 1969-12-31 17:00 init.qcom.lpm_boot.sh
-rwxr-x--- root root 22920 1969-12-31 17:00 init.qcom.rc
-rwxr-x--- root root 3045 1969-12-31 17:00 init.qcom.ril.sh
-rwxr-x--- root root 4486 1969-12-31 17:00 init.qcom.sh
-rwxr-x--- root root 3830 1969-12-31 17:00 init.qcom.syspart_fixup.sh
-rwxr-x--- root root 35468 1969-12-31 17:00 init.qcom.usb.rc
-rwxr-x--- root root 6004 1969-12-31 17:00 init.qcom.usb.sh
-rwxr-x--- root root 41170 1969-12-31 17:00 init.rc
-rwxr-x--- root root 9314 1969-12-31 17:00 init.target.rc
-rwxr-x--- root root 1795 1969-12-31 17:00 init.trace.rc
-rwxr-x--- root root 3915 1969-12-31 17:00 init.usb.rc
drwxrwxr-x root system 1970-05-26 22:16 mnt
drwxrwxr-x root system 1970-05-26 22:16 mnt_1
drwxr-xr-x system system 1970-05-26 22:16 persdata
drwxrwx--x system system 1970-05-26 22:16 preload
dr-xr-xr-x root root 1969-12-31 17:00 proc
-rw-r--r-- root root 2838 1969-12-31 17:00 property_contexts
drwxr-xr-x root root 1969-12-31 17:00 res
drwx------ root root 2013-11-15 08:26 root
drwxr-x--- root root 1969-12-31 17:00 sbin
lrwxrwxrwx root root 1970-05-26 22:16 sdcard -> /storage/emulated/legacy
-rw-r--r-- root root 3887 1969-12-31 17:00 seapp_contexts
-rw-r--r-- root root 610434 1969-12-31 17:00 sepolicy
-rw-r--r-- root root 207 1969-12-31 17:00 sepolicy_version
dr-xr-x--- system sdcard_r 1970-05-26 22:16 storage
dr-xr-xr-x root root 1970-05-26 22:16 sys
drwxr-xr-x root root 1970-03-21 22:11 system
drwxr-xr-x root root 2014-01-31 20:30 tmp-mksh
lrwxrwxrwx root root 1970-05-26 22:16 tombstones -> /data/tombstones
-rw-r--r-- root root 6662 1969-12-31 17:00 ueventd.qcom.rc
-rw-r--r-- root root 4794 1969-12-31 17:00 ueventd.rc
lrwxrwxrwx root root 1970-05-26 22:16 vendor -> /system/vendor
[email protected]:/ # find / -name fast_hang_detect
find: /proc/718/task/1014/fdinfo/459: No such file or directory
find: /proc/718/task/1015/fd/459: No such file or directory
find: /proc/718/task/1040/fd/459: No such file or directory
find: /proc/718/task/1331/fd/459: No such file or directory
find: /proc/718/task/1702/fd/459: No such file or directory
find: /proc/718/task/15245/fdinfo/459: No such file or directory
1|[email protected]:/ # touch /sys/kernal/debug/kgsl/kgsl-3d0/fast_hang_detect
gsl/kgsl-3d0/fast_hang_detect <
tmp-mksh: can't create /sys/kernal/debug/kgsl/kgsl-3d0/fast_hang_detect: No such file or directory
1|[email protected]:/ #
You're still making multiple typos, so we didn't get the information that we need.
.
.
After fixing all my typos and spending hours trying to get it to work, ive come to the conclusion, yea ive got the wrong phone model :S .... well that was a waste of time
:cyclops:
Well, many people have problems on the /persist partition, maybe because some bad rom, or maybe because by a mistake you formatted them on a recovery (a bad recovery without forbid partitions).
Before this zip, you have to copy the "WCNSS_qcom_wlan_factory_nv.bin" to /persist manually, but some file managers don't mount well /persist.
But now, only flashing this zip, it will copy the file to /persist and Wifi go back to work.
:highfive:
Download from:
MEDIAFIRE!
MEGA!
Boss442 said:
Well, many people have problems on the /persist partition, maybe because some bad rom, or maybe because by a mistake you formatted them on a recovery (a bad recovery without forbid partitions).
Before this zip, you have to copy the "WCNSS_qcom_wlan_factory_nv.bin" to /persist manually, but some file managers don't mount well /persist.
But now, only flashing this zip, it will copy the file to /persist and Wifi go back to work.
:highfive:
Download from:
MEDIAFIRE!
MEGA!
Click to expand...
Click to collapse
Bro how to flash it ?
I flashed with twrp v3.0
it gave an error at the end. unable to mount something.
wifi is not working on my mot g2013. I have tried 5-6 roms.
Pls help
does it work?
No it dint.
Twrp gave error. Also the file whicg have to copy in that persist folder gets deleted automatically.
This works
OK, this works but not exactly by flashing.
First of all, this file is a WLAN Qualcom driver which is somehow missing after flashing errors.
Step by step:
1. Enable root for ADB in developer settings in your phone
2. Connect your phone with USB
3.
Code:
adb root
4. Now adb will reconnect as root. Enter command above again to make sure it's done (you will receive confirmation)
5. /persist is not accessible by default (read-only) so we must mount it as writable partition
6.
Code:
adb shell
7.
Code:
mount -o rw,remount /persist
8.
Code:
exit
- we are exiting shell now
9.
Code:
adb push WCNSS_qcom_wlan_factory_nv.bin /persist/
- we are copying driver to phone
10. OK, drivers are now saved on our phone. Let's remount /persist again to be read only:
11.
Code:
adb shell
12.
Code:
mount -o ro,remount /persist
13.
Code:
exit
14. Reboot your phone
If you have unsufficient permissions or something, try
Code:
chmod 777 /persist
after point 7 and
Code:
chmod 771 /persist
after point 11
Tell me if it works, was ok for me.
zyzioziom said:
OK, this works but not exactly by flashing.
First of all, this file is a WLAN Qualcom driver which is somehow missing after flashing errors.
Step by step:
1. Enable root for ADB in developer settings in your phone
2. Connect your phone with USB
3.
Code:
adb root
4. Now adb will reconnect as root. Enter command above again to make sure it's done (you will receive confirmation)
5. /persist is not accessible by default (read-only) so we must mount it as writable partition
6.
Code:
adb shell
7.
Code:
mount -o rw,remount /persist
8.
Code:
exit
- we are exiting shell now
9.
Code:
adb push WCNSS_qcom_wlan_factory_nv.bin /persist/
- we are copying driver to phone
10. OK, drivers are now saved on our phone. Let's remount /persist again to be read only:
11.
Code:
adb shell
12.
Code:
mount -o ro,remount /persist
13.
Code:
exit
14. Reboot your phone
If you have unsufficient permissions or something, try
Code:
chmod 777 /persist
after point 7 and
Code:
chmod 771 /persist
after point 11
Tell me if it works, was ok for me.
Click to expand...
Click to collapse
Zyzoom Hello, first of all sorry for my poor English, I have a XT1032 with the same problem, after installing TWRP recovery and CM13 Nightly 3.0.0, and was unable to enable Wi-Fi.
I followed your steps, but in step 9 out "Read-only file system", so I resume the steps from 6 (adb shell), then "mount -o rw, remount / persist" I write "chmod 777 / persist" but I back out the error " Read-only file system. "
Would you help me please?
norte112 said:
Zyzoom Hello, first of all sorry for my poor English, I have a XT1032 with the same problem, after installing TWRP recovery and CM13 Nightly 3.0.0, and was unable to enable Wi-Fi.
I followed your steps, but in step 9 out "Read-only file system", so I resume the steps from 6 (adb shell), then "mount -o rw, remount / persist" I write "chmod 777 / persist" but I back out the error " Read-only file system. "
Would you help me please?
Click to expand...
Click to collapse
norte112, you need to write commands exactly like I wrote. Do not put space between "/" and "persist" and between "rw," and "remount".
The best is to copy them directly to terminal, I think it's CTRL+INSERT or SHIFT+INSERT on Windows
zyzioziom said:
norte112, you need to write commands exactly like I wrote. Do not put space between "/" and "persist" and between "rw," and "remount".
The best is to copy them directly to terminal, I think it's CTRL+INSERT or SHIFT+INSERT on Windows
Click to expand...
Click to collapse
The commands were copied and pasted as contained in the post directly to cmd, for an error when writing this query, add spaces, but just confirm again (no spaces) and still gives the same error message.
norte112 said:
The commands were copied and pasted as contained in the post directly to cmd, for an error when writing this query, add spaces, but just confirm again (no spaces) and still gives the same error message.
Click to expand...
Click to collapse
Code:
adb shell
ls -al
And paste the results here
Also, try whole process again but after each "adb shell" add another command: "su"
zyzioziom said:
Code:
adb shell
ls -al
And paste the results here
Also, try whole process again but after each "adb shell" add another command: "su"
Click to expand...
Click to collapse
Deputy results:
D:\xt1032\ABD-fastboot>adb shell
←7←[r←[999;999H←[6nls -al
←[email protected]:/ $
I also tried adding SU command after SHELL, but after giving intro but does not allow me to enter any other line or command (attached results):
D:\xt1032\ABD-fastboot>adb root
adbd is already running as root
D:\xt1032\ABD-fastboot>adb shell su
[email protected]:/ #
norte112 said:
Deputy results:
D:\xt1032\ABD-fastboot>adb shell
←7←[r←[999;999H←[6nls -al
←[email protected]:/ $
I also tried adding SU command after SHELL, but after giving intro but does not allow me to enter any other line or command (attached results):
D:\xt1032\ABD-fastboot>adb root
adbd is already running as root
D:\xt1032\ABD-fastboot>adb shell su
[email protected]:/ #
Click to expand...
Click to collapse
You have strange results here :/
Here is my console:
Code:
Patryks-MacBook-Air:platform-tools patryk$ ./adb devices
List of devices attached
TA9290KDJ1 device
Patryks-MacBook-Air:platform-tools patryk$ ./adb root
adbd is already running as root
Patryks-MacBook-Air:platform-tools patryk$ ./adb shell
[email protected]:/ # ls -al
total 2382
drwxr-xr-x 19 root root 0 1970-06-28 19:00 .
drwxr-xr-x 19 root root 0 1970-06-28 19:00 ..
drwxr-xr-x 44 root root 0 1970-06-28 19:00 acct
drwxrwx--- 6 system cache 4096 2016-03-05 03:28 cache
lrwxrwxrwx 1 root root 13 1970-01-01 01:00 charger -> /sbin/healthd
dr-x------ 2 root root 0 1970-06-28 19:00 config
lrwxrwxrwx 1 root root 17 1970-06-28 19:00 d -> /sys/kernel/debug
drwxrwx--x 35 system system 4096 2016-03-09 18:37 data
-rw-r--r-- 1 root root 555 1970-01-01 01:00 default.prop
drwxr-xr-x 15 root root 15300 1970-06-28 19:00 dev
lrwxrwxrwx 1 root root 11 1970-06-28 19:00 etc -> /system/etc
-rw-r--r-- 1 root root 53465 1970-01-01 01:00 file_contexts
drwxr-xr-x 4 root root 4096 1970-01-01 01:00 firmware
drwxr-xr-x 3 root root 1024 1970-01-01 01:00 fsg
-rw-r----- 1 root root 2468 1970-01-01 01:00 fstab.qcom
-rwxr-x--- 1 root root 639808 1970-01-01 01:00 init
-rwxr-x--- 1 root root 8581 1970-01-01 01:00 init.cm.rc
-rwxr-x--- 1 root root 983 1970-01-01 01:00 init.environ.rc
-rwxr-x--- 1 root root 3816 1970-01-01 01:00 init.mmi.boot.sh
-rwxr-x--- 1 root root 4562 1970-01-01 01:00 init.mmi.touch.sh
-rwxr-x--- 1 root root 29483 1970-01-01 01:00 init.qcom.rc
-rwxr-x--- 1 root root 4561 1970-01-01 01:00 init.qcom.ssr.sh
-rwxr-x--- 1 root root 11797 1970-01-01 01:00 init.qcom.usb.rc
-rwxr-x--- 1 root root 26983 1970-01-01 01:00 init.rc
-rwxr-x--- 1 root root 1399 1970-01-01 01:00 init.recovery.qcom.rc
-rwxr-x--- 1 root root 319 1970-01-01 01:00 init.superuser.rc
-rwxr-x--- 1 root root 2764 1970-01-01 01:00 init.target.rc
-rwxr-x--- 1 root root 1921 1970-01-01 01:00 init.trace.rc
-rwxr-x--- 1 root root 9283 1970-01-01 01:00 init.usb.configfs.rc
-rwxr-x--- 1 root root 5339 1970-01-01 01:00 init.usb.rc
-rwxr-x--- 1 root root 342 1970-01-01 01:00 init.zygote32.rc
drwxr-xr-x 9 root system 200 1970-06-28 19:00 mnt
drwxr-xr-x 2 root root 0 1970-01-01 01:00 oem
drwxr-xr-x 12 root root 1024 1970-01-01 01:01 pds
drwxrwx--x 4 system system 4096 2016-03-09 12:01 persist
dr-xr-xr-x 220 root root 0 1970-01-01 01:00 proc
-rw-r--r-- 1 root root 6049 1970-01-01 01:00 property_contexts
drwx------ 2 root root 0 2016-03-05 03:29 root
drwxr-x--- 2 root root 0 1970-01-01 01:00 sbin
lrwxrwxrwx 1 root root 21 1970-06-28 19:00 sdcard -> /storage/self/primary
-rw-r--r-- 1 root root 2182 1970-01-01 01:00 seapp_contexts
-rw-r--r-- 1 root root 69 1970-01-01 01:00 selinux_version
-rw-r--r-- 1 root root 258562 1970-01-01 01:00 sepolicy
-rw-r--r-- 1 root root 14812 1970-01-01 01:00 service_contexts
drwxr-xr-x 4 root root 80 2016-03-09 11:57 storage
dr-xr-xr-x 14 root root 0 1970-06-28 19:00 sys
drwxr-xr-x 16 root root 4096 2016-03-08 21:09 system
lrwxrwxrwx 1 root root 16 1970-06-28 19:00 tombstones -> /data/tombstones
-rw-r--r-- 1 root root 12478 1970-01-01 01:00 ueventd.qcom.rc
-rw-r--r-- 1 root root 7606 1970-01-01 01:00 ueventd.rc
lrwxrwxrwx 1 root root 14 1970-06-28 19:00 vendor -> /system/vendor
Your "ls -al" displayed nothing, am I right?
zyzioziom said:
You have strange results here :/
Here is my console:
Code:
Patryks-MacBook-Air:platform-tools patryk$ ./adb devices
List of devices attached
TA9290KDJ1 device
Patryks-MacBook-Air:platform-tools patryk$ ./adb root
adbd is already running as root
Patryks-MacBook-Air:platform-tools patryk$ ./adb shell
[email protected]:/ # ls -al
total 2382
drwxr-xr-x 19 root root 0 1970-06-28 19:00 .
drwxr-xr-x 19 root root 0 1970-06-28 19:00 ..
drwxr-xr-x 44 root root 0 1970-06-28 19:00 acct
drwxrwx--- 6 system cache 4096 2016-03-05 03:28 cache
lrwxrwxrwx 1 root root 13 1970-01-01 01:00 charger -> /sbin/healthd
dr-x------ 2 root root 0 1970-06-28 19:00 config
lrwxrwxrwx 1 root root 17 1970-06-28 19:00 d -> /sys/kernel/debug
drwxrwx--x 35 system system 4096 2016-03-09 18:37 data
-rw-r--r-- 1 root root 555 1970-01-01 01:00 default.prop
drwxr-xr-x 15 root root 15300 1970-06-28 19:00 dev
lrwxrwxrwx 1 root root 11 1970-06-28 19:00 etc -> /system/etc
-rw-r--r-- 1 root root 53465 1970-01-01 01:00 file_contexts
drwxr-xr-x 4 root root 4096 1970-01-01 01:00 firmware
drwxr-xr-x 3 root root 1024 1970-01-01 01:00 fsg
-rw-r----- 1 root root 2468 1970-01-01 01:00 fstab.qcom
-rwxr-x--- 1 root root 639808 1970-01-01 01:00 init
-rwxr-x--- 1 root root 8581 1970-01-01 01:00 init.cm.rc
-rwxr-x--- 1 root root 983 1970-01-01 01:00 init.environ.rc
-rwxr-x--- 1 root root 3816 1970-01-01 01:00 init.mmi.boot.sh
-rwxr-x--- 1 root root 4562 1970-01-01 01:00 init.mmi.touch.sh
-rwxr-x--- 1 root root 29483 1970-01-01 01:00 init.qcom.rc
-rwxr-x--- 1 root root 4561 1970-01-01 01:00 init.qcom.ssr.sh
-rwxr-x--- 1 root root 11797 1970-01-01 01:00 init.qcom.usb.rc
-rwxr-x--- 1 root root 26983 1970-01-01 01:00 init.rc
-rwxr-x--- 1 root root 1399 1970-01-01 01:00 init.recovery.qcom.rc
-rwxr-x--- 1 root root 319 1970-01-01 01:00 init.superuser.rc
-rwxr-x--- 1 root root 2764 1970-01-01 01:00 init.target.rc
-rwxr-x--- 1 root root 1921 1970-01-01 01:00 init.trace.rc
-rwxr-x--- 1 root root 9283 1970-01-01 01:00 init.usb.configfs.rc
-rwxr-x--- 1 root root 5339 1970-01-01 01:00 init.usb.rc
-rwxr-x--- 1 root root 342 1970-01-01 01:00 init.zygote32.rc
drwxr-xr-x 9 root system 200 1970-06-28 19:00 mnt
drwxr-xr-x 2 root root 0 1970-01-01 01:00 oem
drwxr-xr-x 12 root root 1024 1970-01-01 01:01 pds
drwxrwx--x 4 system system 4096 2016-03-09 12:01 persist
dr-xr-xr-x 220 root root 0 1970-01-01 01:00 proc
-rw-r--r-- 1 root root 6049 1970-01-01 01:00 property_contexts
drwx------ 2 root root 0 2016-03-05 03:29 root
drwxr-x--- 2 root root 0 1970-01-01 01:00 sbin
lrwxrwxrwx 1 root root 21 1970-06-28 19:00 sdcard -> /storage/self/primary
-rw-r--r-- 1 root root 2182 1970-01-01 01:00 seapp_contexts
-rw-r--r-- 1 root root 69 1970-01-01 01:00 selinux_version
-rw-r--r-- 1 root root 258562 1970-01-01 01:00 sepolicy
-rw-r--r-- 1 root root 14812 1970-01-01 01:00 service_contexts
drwxr-xr-x 4 root root 80 2016-03-09 11:57 storage
dr-xr-xr-x 14 root root 0 1970-06-28 19:00 sys
drwxr-xr-x 16 root root 4096 2016-03-08 21:09 system
lrwxrwxrwx 1 root root 16 1970-06-28 19:00 tombstones -> /data/tombstones
-rw-r--r-- 1 root root 12478 1970-01-01 01:00 ueventd.qcom.rc
-rw-r--r-- 1 root root 7606 1970-01-01 01:00 ueventd.rc
lrwxrwxrwx 1 root root 14 1970-06-28 19:00 vendor -> /system/vendor
Your "ls -al" displayed nothing, am I right?
Click to expand...
Click to collapse
I found the problem, after writing the adb shell command, the console brings me the following result: ← 7 ← [r ← [999; ← 999H [6n
I just click on INTRO and I recently enabled the line: ← 8root @ falcon: / #
After that, I entered the commands and could properly install the drivers !!!
Problem solved.
Thank you very much for the support, help and above all, patience.
Boss442 said:
Well, many people have problems on the /persist partition, maybe because some bad rom, or maybe because by a mistake you formatted them on a recovery (a bad recovery without forbid partitions).
Before this zip, you have to copy the "WCNSS_qcom_wlan_factory_nv.bin" to /persist manually, but some file managers don't mount well /persist.
But now, only flashing this zip, it will copy the file to /persist and Wifi go back to work.
:highfive:
Download from:
MEDIAFIRE!
MEGA!
Click to expand...
Click to collapse
Worked perfect with flashify and twrp (copy first to a safe location)
Many thanks!
Didn't work for me
I tried flashing the zip, copying manually in CM file explorer and twrp and adb.
The driver is present in /persist but my Mac is stil 02:00:00:00:00
edit:
it's working after doing this:
http://forum.xda-developers.com/showpost.php?p=64771901&postcount=6
My wifi bug is kinda weird.
When I turn on and off my wifi 2-3times,the wifi I connected previously disappear.
Solution is to wipe everything including internal storage to have it working.But still I don't know what's the problem...
I had trouble installing the file no matter how it I flash the wifi did not return to work until I found a solution that apparently functioned normally every time I performed the procedure.
1. Make a full wipe on your smartphone (System / data / cache / dalvik and internal storage) I did the procedure using TWRP 3.0.2-0 on my bike G XT1033
2. Then copy the file persist_repair.zip and some version of CM13 I used (cm 13.0-20160708-NIGHTLY-falcon)
3. After placing the files in the memory of the first flash persist_repair.zip phone and then the CM13 (You can do using the option to install multiple zips the TWRP also the right)
4. Restart your phone and its wifi should resume functioning
Note: I performed the procedure 4 times here and it worked perfectly.
Sorry for the English I used the google translator
NoobByn-tek said:
I had trouble installing the file no matter how it I flash the wifi did not return to work until I found a solution that apparently functioned normally every time I performed the procedure.
1. Make a full wipe on your smartphone (System / data / cache / dalvik and internal storage) I did the procedure using TWRP 3.0.2-0 on my bike G XT1033
2. Then copy the file persist_repair.zip and some version of CM13 I used (cm 13.0-20160708-NIGHTLY-falcon)
3. After placing the files in the memory of the first flash persist_repair.zip phone and then the CM13 (You can do using the option to install multiple zips the TWRP also the right)
4. Restart your phone and its wifi should resume functioning
Note: I performed the procedure 4 times here and it worked perfectly.
Sorry for the English I used the google translator
Click to expand...
Click to collapse
I faced same problem after flashed custom rom; searching high and low, tried many method, and finally, bumped this thread, and specifically NoobByn-tek post. I followed exactly what your have done (but with different version CM13 [cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J1-falcon] because could not find the version you used), and multiple flashed with TWRP 3.0.2. With only one attempt, wifi connection is back.:victory:
Big thank you all.:good::good:
NoobByn-tek said:
I had trouble installing the file no matter how it I flash the wifi did not return to work until I found a solution that apparently functioned normally every time I performed the procedure.
1. Make a full wipe on your smartphone (System / data / cache / dalvik and internal storage) I did the procedure using TWRP 3.0.2-0 on my bike G XT1033
2. Then copy the file persist_repair.zip and some version of CM13 I used (cm 13.0-20160708-NIGHTLY-falcon)
3. After placing the files in the memory of the first flash persist_repair.zip phone and then the CM13 (You can do using the option to install multiple zips the TWRP also the right)
4. Restart your phone and its wifi should resume functioning
Note: I performed the procedure 4 times here and it worked perfectly.
Sorry for the English I used the google translator
Click to expand...
Click to collapse
tried this still no luck...:crying::crying:
Boss442 said:
Well, many people have problems on the /persist partition, maybe because some bad rom, or maybe because by a mistake you formatted them on a recovery (a bad recovery without forbid partitions).
Before this zip, you have to copy the "WCNSS_qcom_wlan_factory_nv.bin" to /persist manually, but some file managers don't mount well /persist.
But now, only flashing this zip, it will copy the file to /persist and Wifi go back to work.
:highfive:
Download from:
MEDIAFIRE!
MEGA!
Click to expand...
Click to collapse
Holy cow!!! After 2 weeks of trying everything under the sun this actually worked!!! I really really appreciate you posting this. Thank you so much!!!
My mac address was 00:00:00:00:02 or whatever it was and nothing would work. I simply flashed this and was back up and running. THANK YOU!
update link please