Database Users

[GUIDE] Workaround Issues (Unofficial MoDaCo 1.2c)

This is meant to be a compliment to the post: [GUIDE] Root Hero [MAC], Load Unofficial MoDaCo 1.2c, Nandroid Backup/Restore!
However, if you are using other rooted ROMs, you can feel welcome to try the steps described to workaround your issues as well! Tell us how it goes!
For this guide, I will be providing steps to workaround most of the known issues that exist with the unit using Unofficial MoDaCo 1.2c
PLEASE NOTE: These are the best possible WORKAROUNDS I have been able to find scattered across various forums. They are not FIXES. Most of these issues will most likely require an update from Sprint/HTC in order to be "FIXED". If you would like to keep up with new developments, you can check the Sprint Discussion forums for any official announcements by Admins:
http://community.sprint.com/baw/com...-devices/android_phones/hero?view=discussions
Feel free to reply with any further fixes and corrections of any errors I may make now or in the future! Happy Rooting!
BEFORE FOLLOWING THE WORKAROUND GUIDE
Most all of my workarounds will require some type of app. To make loading apps into your phone easier (and fun!), I will have you first download Barcode Scanner. For those who don't wish to rely on the Barcode Scanner, I will also provide links to the App from androlib.com, and you are of course free to run searches of the app name. In fact, we have to do that initially for Barcode Scanner!
Open "Market" and select "Search". Type in "barcode scanner". The name of the app we want is "Barcode Scanner" and it is by "ZXing Team". You are in theory able to use any other barcode scanning apps as well, I'm just having you get the one I use!
AndroLib Link: Barcode Scanner
From this point forward, you can use Barcode Scanner to scan QR Codes that I will place of Apps I instruct you to download and use.
Quick Boot
If you wish to be able to reboot the phone or load it into recovery mode without plugging in and running adb, download this app called "Quick Boot":
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
AndroLib: Quick Boot
Workarounds
Please use these workarounds in order (if possible) for best results.
Voice Search/Maps Force Close (Thanks dom2114!)
Forum Post: Google Voice Search/Maps Force Closes on MoDaCo
Connect to your Mac via USB, Open Terminal, and enter the following commands (Thanks thecodemonk!):
Code:
adb remount
adb shell
mv /data/app/com.google.android.voicesearch.apk /system/app
mv /data/app/com.google.android.apps.maps.apk /system/app
Prevent apps from using wrong names / reverting to previous versions after reboot (Thanks jonnythan!)
Forum Post: Misnamed apps? Wrong versions? Fix here
The way this workaround works, you will unfortunately have to use it every time you install and/or update an app. The reasoning behind this is that if any data exists in the /data/boot-cache directory that we are emptying, then there is the possibility that we will have this issue occur. Only though repeated use of this command have people been able to successfully avoid this issue. Therefore, I will provide instructions so that you can simply run a single command after any app install and/or update, which should help you avoid the issue!
Download "Command Executer" from Market.
AndroLib: Command Executer
On your phone, open the App called "Notes" (Yes, it's there I promise, it came with MoDaCo!)
Select Menu>New>Text Note
Name the note: "clear-boot-cache"
Save the following into the body of the note:
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system && rm -r /data/boot-cache/*
Make sure the cursor is in the actual body of the note, long press, and select "Copy all"
Open "Command "Executer", select the "Super User" radio button, long press in the text box provided, select "Paste".
You should see the code you copied from the note
When running this command for the first time, you will have to grant su access. the Superuser Permission app will open asking you to allow this command to run. Select "Always allow" so that you don't have to go through the pop-up again. If you don't receive any errors, you are good! If you do get an error, just try it again.
If nothing spits out then you are good for reboot, and your app names and versions should all remain intact!
Remove Useless Preloaded Apps (Thanks chuckhriczko and VoXHTC!)
Forum Post 1: How to remove Stocks, Nascar, and other useless apps...
Forum Post 2: APPS that are SAFE to remove
List of Apps I remove (and can confirm everything left still works after reboot!):
-Sprint NFL
-Sprint Nascar
-Stocks + Widget
-Peep (Twitter) + Widget
-Foorprints + Widget
Code:
adb remount
adb shell
cd /system/app
rm Sprint_NFL.apk
rm Sprint_NFL.odex
rm Sprint_Nscar.apk
rm Sprint_Nscar.odex
rm Stock.apk
rm Stock.odex
rm com.htc.StockWidget.apk
rm com.htc.StockWidget.odex
rm HtcTwitter.apk
rm HtcTwitter.odex
rm com.htc.TwitterWidget.apk
rm com.htc.TwitterWidget.odex
rm HtcFootprints.apk
rm HtcFootprints.odex
rm HtcFootprintsWidget.apk
rm HtcFootprintsWidget.odex
rm LearnMore.apk
rm LearnMore.odex
Not all apps you try to remove will have matching ".odex" files. This is OK. We must make sure to remove them just in case, as leaving either the .apk or the .odex can result in the app reinstalling itself!
NOTE: For the following apps, I use Google Voice and Maps, so I do not need them. HOWEVER, if you want to use the Sprint provided Visual Voicemail and turn-by-turn Navigation, DO NOT REMOVE!
Code:
rm Sprint_Navigator.apk
rm Sprint_Navigator.odex
rm Sprint_Core.apk
rm Sprint_Core.odex
cd /system/sd/app
rm com.coremobility.app.vnotes.apk
Wifi-Sleep Policy (Possible Battery Life Improvement!)
Forum Post: Battery Drain...Fixed for me!
This seems to have helped many users on the Sprint forums with battery life issues. Worth a shot!
Code:
Settings->Wireless Controls->WiFi Settings>Press Menu>Advanced>Wi-Fi sleep policy>Never
Alarm Volume
Forum Post: Alarm not working properly?
I use a combination of an app and widget to keep my alarm volume at max and making sure it stays there.
"Sound Manager" will allow you to schedule the alarm volume to adjust at a specific time (default 8AM). I set a default alarm for everyday of the week at the default time (8AM), and I have not had any problems with the alarm not going off since!
AndroLib: Sound Manager
You can also use the "AudioManager Widget" widget to monitor the alarm volume. I check it anytime I swipe to the home screen that holds it.
AndroLib: AudioManager Widget
Helpful Hints
How to tell if apps2sd (A2SD) is working
Connect to your Mac via USB, Open Terminal, and enter the following commands:
Code:
adb remount
adb shell
ls /system/sd/app/
If you get a list of applications, then A2SD is working properly.

[Q] ADB and recovery mode

Firmware JP9, power-on to recovery mode => install update.zip => error can't mount sdcard => try to using adb for mounting sdcard manually but adb did not active.
One more thing, root using one click 1.5.5 OK for apps but can not achieve SU @ adb (and adb only work while boot into normal mode)
Any suggestion for install the update.zip from sdcard?

No more recovery for me either (I didn't flash the bootloader althrough).
When you use adb and type "su", the phone should prompt you a window.

Gsam101 said:
No more recovery for me either (I didn't flash the bootloader althrough).
When you use adb and type "su", the phone should prompt you a window.
Click to expand...
Click to collapse
for the same reason I can not update gps.conf with european settings, it says error message when I try adb

nastyba said:
for the same reason I can not update gps.conf with european settings, it says error message when I try adb
Click to expand...
Click to collapse
root your phone using super one click 1.5.5 (Run the soft first, and click root wait until the software said that waitting devices... plug your phone to PC using usb cable and wait more 2'' or 5'' . DONE! It's safe and you can unroot as well)
you can using some missing command by busybox (the easiest way in install titanium backup and click the problems? button in the right bottom it will automatically install new busy box to your phone)
adb shell
$su
#busybox mount -o remount,rw /system (change to your path to the gps.conf - with this command you can edit or replace the old file)
#busybox cp /sdcard/gps.conf /system/.../gps.conf
DONE
Good luk!

kenblat said:
adb shell
$su
#busybox mount -o remount,rw /system (change to your path to the gps.conf - with this command you can edit or replace the old file)
#busybox cp /sdcard/gps.conf /system/.../gps.conf
Click to expand...
Click to collapse
Or you can install "Root explorer" - RO/RW mount in 1 click + file explorer

kenblat said:
root your phone using super one click 1.5.5 (Run the soft first, and click root wait until the software said that waitting devices... plug your phone to PC using usb cable and wait more 2'' or 5'' . DONE! It's safe and you can unroot as well)
you can using some missing command by busybox (the easiest way in install titanium backup and click the problems? button in the right bottom it will automatically install new busy box to your phone)
adb shell
$su
#busybox mount -o remount,rw /system (change to your path to the gps.conf - with this command you can edit or replace the old file)
#busybox cp /sdcard/gps.conf /system/.../gps.conf
DONE
Good luk!
Click to expand...
Click to collapse
Thank you for your effort - I have rooted phone & Titanium backup installed and busybox installed after Titanium was launched first time.
I can not run Adb Shell
#su works OK
after "busybox..." it says error message
I cannot find root explorer on market
and finaly I was trying Terminal emulator and SUFBS and I still can not edit system/etc/GPS.CONF ((
any ideas please ?

angry_friend said:
Or you can install "Root explorer" - RO/RW mount in 1 click + file explorer
Click to expand...
Click to collapse
hi, where did you get it pls ?

nastyba said:
hi, where did you get it pls ?
Click to expand...
Click to collapse
google for blackdroid and there search for root explorer...

google for "android+ root explorer.apk download"

nastyba said:
hi, where did you get it pls ?
Click to expand...
Click to collapse
QR Code of the app:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
yeah I forgot, it's not free, but it worth 3.90$ to pay, trust me

I deleted some files in root accidentally; now it won't boot.

I deleted some critical files in /system directory accidentally, and it force closed / shut off.
When I tried turning it back on, it never gets past the "kindle fire" screen.
Connecting it to the computer and using adb, su command doesn't work, mount doesn't work... but it can detect the device.
So... am I screwed?

Unless someone discovers, or Kindle support can give you, a way to load the software via the boot loader, you're probably bricked.
I'm not sure if the boot loader has this functionality. Has anyone successfully extracted it yet?

I was playing around last night replacing packages and I did something similar...where I got stuck in the same situation. What I was able to do (and was very happy/surprised it worked) was using the root process to get back in.
The one I used was the one with the script you run which does everything for you. I'm on a mac so I hacked the runmemac.sh script and add in a few lines after the /system mount point was remounted rw to push out the apk's I had swapped and make sure the permissions were set right. I kicked off the script and it proceeded to root my kindle (even though it was not necessary) and put my packages back.
It's an ugly way...I could have just ran the individual commands but I was being lazy. It also means you need the original packages you removed first in order to put them back. But it worked.
Basically find this section in the script:
echo "--- remounting /system"
./$varadb shell "/data/local/tmp/busybox mount -o remount,rw /system"
and add:
./$varadb push whatever.apk /system/app/
./$varadb shell "chown root.root /system/app/whatever.apk"
./$varadb shell "chmod 644 /system/app/whatever.apk"
If push doesn't work, you can try install. I had a few trial and errors in the process but that is from my last go around which worked...twice.

ivanemoore said:
The one I used was the one with the script you run which does everything for you. I'm on a mac so I hacked the runmemac.sh script and add in a few lines after the /system mount point was remounted rw to push out the apk's I had swapped and make sure the permissions were set right.
Click to expand...
Click to collapse
It wouldn't mount... :/. *sigh*

The fire does have a recovery partition but I've not figured out how to trigger it during boot..

have you tried getting to it through ADB?
---------- Post added at 09:42 PM ---------- Previous post was at 09:38 PM ----------
MayfairDROID said:
have you tried getting to it through ADB?
Click to expand...
Click to collapse
Nope..to easy I guess I tried ADB REBOOT RECOVERY with no success. It rebooted back to the lock screen

Download the standalone 6.1 update and adb in and put it in the updates folder. Then reboot.
Sent from my Kindle Fire using Tapatalk

Lkish said:
Download the standalone 6.1 update and adb in and put it in the updates folder. Then reboot.
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
How do I adb push files to /sdcard/kindleupdates/ directory?
After typing "adb devices" to show the device, I typed:
C:\adb> adb push update-kindle-6.1_D01E_2017120.bin /sdcard/kindlefireupdates/
To which I got:
failed to copy 'update-kindle....bin' to '/sdcard/kindlefireupdates/': Permission denied
I tried using "\":
C:\adb> adb push update-kindle-6.1_D01E_2017120.bin \sdcard\kindlefireupdates\
To which I got:
failed to copy 'update....bin' to '\sdcard\kindlefireupdates\': Read-only file system
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Try this:
adb shell mount -w -t vfat /dev/block/mmcblk0p12 /mnt/sdcard
adb push update-kindle....bin /mnt/sdcard/kindleupdates

transfuntioner said:
Try this:
adb shell mount -w -t vfat /dev/block/mmcblk0p12 /mnt/sdcard
adb push update-kindle....bin /mnt/sdcard/kindleupdates
Click to expand...
Click to collapse
mount: Operation not permitted.
Doing:
adb shell su
results in "[1] Segmentation fault su"

Sorry, forgot about the su part.. I am guessing adb remount also does not work.
[email protected] said:
Unless someone discovers, or Kindle support can give you, a way to load the software via the boot loader, you're probably bricked.
I'm not sure if the boot loader has this functionality. Has anyone successfully extracted it yet?
Click to expand...
Click to collapse
Yes, I've been able to get at this functionality! I am still working on documenting my findings in my fastboot thread. However, be forewarned, the method & instructions are not user friendly at the moment!

transfuntioner said:
I am guessing adb remount also does not work.
Click to expand...
Click to collapse
Nope. Guess this is bricked 'till bootloader is available (which, I hope, can be pushed through adb)... *sigh*

if you have busybox installed try adb shell first, then busybox mount.. like
adb shell
# busybox mount -w -t vfat /dev/block/mmcblk0p12 /mnt/sdcard
for me it wouldnt do the command unless i used busybox
or you could use the other..
busybox mount -o rw,remount /mnt/sdcard
but if your getting at least the adb console then all is not lost..

pyrorob said:
if you have busybox installed try adb shell first, then busybox mount.. like
adb shell
# busybox mount -w -t vfat /dev/block/mmcblk0p12 /mnt/sdcard
for me it wouldnt do the command unless i used busybox
or you could use the other..
busybox mount -o rw,remount /mnt/sdcard
but if your getting at least the adb console then all is not lost..
Click to expand...
Click to collapse
Didn't work either... I could've sworn I installed busybox as a method of rooting... >.>
Oh well... until recovery is out, guess this is just a $200 paperweight x.x.

I did it using a Mac to download the kindle software 6.1 update then usb connected the fire and it mounts on the Mac as a drive. Then drag the file into kindleupdates folder. Reboot will then run the update automatically.
Sent from my Kindle Fire using Tapatalk

Printerscape said:
I deleted some critical files in /system directory accidentally, and it force closed / shut off.
When I tried turning it back on, it never gets past the "kindle fire" screen.
Connecting it to the computer and using adb, su command doesn't work, mount doesn't work... but it can detect the device.
So... am I screwed?
Click to expand...
Click to collapse
I was having the same issues.. bootlooped/bricked after rooting, pretty sure I removed system files somehow when adding google apps. Anyway, my friend and I figured out how to recover it back to out of the box state. This is what fixed my Kindle. I just posted a thread on it here with all the steps: forum.xda-developers.com/showthread.php?t=1356257 hope it helps!

Has anyone had any luck writing the files from the Kindle 6.1 Update Rom dump to the Kindle fire?

Basic ADB Functions -

Basic Commands :
++++++++++++++++++++++++++++
Following are the basic commands which we usually use :
pull - to copy file/dir from Xoom to computer
push - to copy file/dir from computer to Xoom , we will call it "X"
delete - delete file/dir from X
install – install apps on X [either on SD Card or internal storage]
reboot - reboot your X
ADB Shell command -
Code:
adb shell
In command prompt, just type
Code:
adb
list of all commands will show up.
Examples :
++++++++++++++++++++++++++++
The following command, (pull) takes the file avi.apk from the device and saves it as file.apk to the Android Tools directory of computer.
Pull
Code:
Code:
adb pull /system/app/avi.apk file.apk
Push
The following command will copy avi.apk file as happy.apk, from the computer Android tools folder to /system/app of the device
Code:
Code:
adb push avi.apk /system/app/happy.apk
Delete :
The following command removes file avi.apk
Code:
Code:
adb shell rm /system/app/avi.apk
Install :
adb can also be used to install apks. Place the downloaded apks in C:/ drive. for eg, I have placed angrybirds.apk in C:/ drive of my computer. To install it, just run the following command.
Code:
Code:
adb install angrybirds.apk
By above command it will install to internal storage.
*You can also install to SD card by -s switch. (example below)
Code:
Code:
adb install -s angrybirds.apk
Reboot :
The following command will reboot your (device)
Code:
Code:
adb shell su reboot
Quick tips :
++++++++++++++++++++++++++++
1. The commands are case sensitive.
2. Using adb you will be accessing system files, play commands safely or else you might end up making your device unusable.
RENAME : File or APK -
++++++++++++++++++++++++++++
Linux commands. You 'move' the file from the old name to the new one.
Make sure your phone or Tab has enabled USB debugging, connect it to your computer, on your computer type: adb shell
The command you can use is mv (move a file or rename a file)
mv - renames files, apk ...
Code:
Code:
[COLOR=Red]mv[/COLOR] filename[COLOR=Red].[/COLOR]old filename[COLOR=Red].[/COLOR]new
(If it's a system file, you'll will have to have superuser permission and have to make the file system read-write.)
Stubborn Folder Removal -
Intro:
++++++++++++++++++++++++++++
rm - remove files or directories
rm Does not work on directories (unless you use -r, but CAREFUL of this command)
rm -rf /foldername
(This is an example)
Code:
[COLOR=Red]rm[/COLOR] [COLOR=Red]-rf[/COLOR] /system/your stubborn folder
This will remove 'stubborn folder' and everything inside that bad boy)
-r = recursive -f = force
if rm -rf complains about the -rf part,
(Try to run):
Code:
busybox [COLOR=Red]rm -rf[/COLOR] /foldername
IMPORTANT: there is no warning to remove the entire folder, once you hit enter it's gone.
-f can also be used as an alternative
Manual RM: http://unixhelp.ed.ac.uk/CGI/man-cgi?rm
How To:
ADB Shell Removal - (we will use BT5 as an example)
++++++++++++++++++++++++++++
1. Connect Xoom
2. Boot into recovery
3. Toggle to internal storage as /sdcard
mount /data
Enter adb shell via pc
(cd to file location) in this case BT5, is in the sdcard directory
Code:
cd /sdcard #
(once typed, you will be at.... /data/media prompt)
Code:
rm -r stubborn Folder
*Side note ... This works for any other stubborn folder that you want to delete as well...
USE AT YOU OWN RISK - MAKE SURE YOU DO A BACKUP FIRST
If this was helpful Hit The thanks!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

helpful!!
buddy tell me 1 thing...i need to delete an .apk from system/app/
should i do these:-
1)adb root
2)adb shell
3)adb shell getprop ro.secure
4)adb shell mount -oremount,rw /dev/block/system /system
5)adb delete /system/app/<filename>.apk
6)adb shell mount -oremount,ro /dev/block/system /system
is that it??
or the step 5 should be 5)adb shell rm /system/app/<filename>.apk
please....reply.thanks in advabce....i am a total noob in this case(knows a little bit of programming stuff so the commands seems understandable, copied steps 1-4 and 6 from a rooting device site)thought matching both of them shall do the thing...will it??

Your best bet since you say that you are unfamiliar with adb commands, is to remove the "apk" via an app named Root Explorer. As long as you are uzing a rooted device it will make any apk available for easy removal. Be Careful.

I made a mistake
actually I have copied the superuser.apk into system/app/ folder so that it gets automatically installed when i reset the device...and then the problem starts....SUPERUSER stopped responding(getting force closed automatically) and therefore no explorer/titanium backup....nothing is getting root access....so hav to do dis using adb...will hav to delete supeuser 3.1.apk and then reset the device again...
just tell me which step 5 should i use since u have mentioned two ways...

santy_sayantan said:
actually I have copied the superuser.apk into system/app/ folder so hav to do dis using adb...will hav to delete supeuser 3.1.apk and then reset the device again...
Click to expand...
Click to collapse
First and foremost, Superuser or Supersu MUST be installed in data/app directory otherwise you run into issues.
adb shell rm /system/stubborn.apk
Or (wherever directory you put the .apk)
adb shell rm /system/app/stubborn.apk

Write to /proc/asound not possible

Since 3 months im having audio problems with my moto g4 plus , when i checked log
its something like
/proc/asound/card---/state failed:no such directory
i posted a thread in another forum and advised to check the proc directory, so using root explorer and on comparison with the xda member's asound directory, i found that the card0 folder in which the state file is there is missing
I got the files and tried to copy paste them using many root browsers
result: permission denied,cant copy..etc
tried pushing through adb, tried asb shell su and then cp command
i can write to almost all directories in the root but not proc
I know that /proc is a directory linked to the kernel where info about all running process is stored
but Pasting the missing file is the only thing that can save my phone, heard that i need a insecure kernel to do that,
Can anyone please help me with this?? i badly need to write to /proc
Can any kernel developer make a insecure kernel with these requirements for stock android 7.0.0 xt1643(Sorry,if i sounded noob)

Have you tried to mount the 'proc' partition?
From a terminal emulator app, type:
# su
# mount -o remount,rw /proc
Whether this display an error message, install BusyBox (i recommend this one) and type:
# su
# busybox mount -o remount,rw /proc
Always without the numeral sign.

moonlightdrive said:
Have you tried to mount the 'proc' partition?
From a terminal emulator app, type:
# su
# mount -o remount,rw /proc
Whether this display an error message, install BusyBox (i recommend this one) and type:
# su
# busybox mount -o remount,rw /proc
Always without the numeral sign.
Click to expand...
Click to collapse
Still, couldnt write to proc.See here
Note: I just checked whether i can write or not using cat and mkdir commands
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Karthik Veenam said:
Since 3 months im having audio problems with my moto g4 plus , when i checked log
its something like
/proc/asound/card---/state failed:no such directory
i posted a thread in another forum and advised to check the proc directory, so using root explorer and on comparison with the xda member's asound directory, i found that the card0 folder in which the state file is there is missing
I got the files and tried to copy paste them using many root browsers
result: permission denied,cant copy..etc
tried pushing through adb, tried asb shell su and then cp command
i can write to almost all directories in the root but not proc
I know that /proc is a directory linked to the kernel where info about all running process is stored
but Pasting the missing file is the only thing that can save my phone, heard that i need a insecure kernel to do that,
Can anyone please help me with this?? i badly need to write to /proc
Can any kernel developer make a insecure kernel with these requirements for stock android 7.0.0 xt1643(Sorry,if i sounded noob)
Click to expand...
Click to collapse
did you found the solution to the audio problem,
the same problem happened to me too.
dot know what to do.

Moto G4 audio not working
Moto G4 audio not working (works after reboot for 2mins and audio goes off)...suddenly my mobile rebooted and after that no audio is playing
Tried hard reset changed custom roms ,stock ROM 6.0 and nougat
Still issues not solved
Tried lot of ways but not working
Please anybody share the method to solve the issue (I have been trying for 2 weeks )
Please help!!