Database Info

Android/Linux question for rooted Galaxy Tab

Hi there
My knowledge of Android is very limited, I know a little about Linux from Ubuntu at command promt level, but not enough to fix this issue I'm having. Any help would be much appreciated.
I wish to modify a file which Android is telling me is locked. It's \system\etc\bluetooth\audio.config
I have found a modification to this file which may help me in connecting the Tab to a bluetooth peripheral I have.
I have rooted the Tab
I have installed a root file manager
I have installed a terminal app
I have tried to chmod this file when logged in as su, but this refused so still I cannot edit the file.
I read somewhere about mounting the system folder as rw, but this is a bit beyond my knowledge. So if this is necessary I need walking through this step-by-step.
Could someone please help me by posting some instructions to get me to the point where I can edit the file audio.config?
Many thanks
Gary

su
mount -o remount,rw /dev/mtdblock3 /system
You may still not be able to modify a file so copy it to /mnt/sdcard/file and edit it there and rename the source file when ready to mv it back in.
mount -o remount,ro /dev/mtdblock3 /system
when done.
This worked for me on my new Galaxy Tab Wifi after using A4 to root it.

[Q] some questions about the linux installer

hi there
this is about the "linux installer" app you can find on the marked.
i finally managed to install a debian squeeze into my ext2 partition on the sd card.
i managed to get my ext2 partition mounted on boot thanks to this guy after i read this post.
(actually i had to change line 2 and 7 to "/dev/stl12 /system" since im running his script on a samsung galaxy ace s5830)
in the installer i went to the settings did these changes:
install into: /data/sdext2
devicename: mmcblk0p2
with this configuration the installation process went fine.
using the android terminal app i can run my installation typing "linuxboot" but i
get soum mount errors on startup.
so i looked for the linuxboot.sh from the android terminal and located it in
/system/bin/linuxboot.sh
so far.
did anyone get this far and got the same errors?
i not shure that this is the reason for the mount problems, but the file seems to still contain some standartvalues for some reason.
for example theres this line:
export mnt=/data/data/com.galoula.LinuxInstall/mnt
Click to expand...
Click to collapse
maybe i should change it to "/data/sdext2" ? since this is what i did in the settings as well?
however theres no chance to do any changes on this file anyway since the prompt tells me that i have a readonly filesystem.
my phone runs android 2.3.3 and is rooted using this file (found on in this post), shouldnt i have write acces to the files?
EDIT:
*sigh ..ve been so stupid
to get write acces i need to remount the system folder as i did in the installation process before
su
mount -o remount,rw /dev/stl12 /system
Click to expand...
Click to collapse

http://forum.xda-developers.com/showthread.php?p=16961006
3.3 is out. Please update, and contact me by email if any trouble. [email protected]
Galoula made a huge update; I did all translations and debug. New tutorial, new quick installation guide.
Please update, and send an email if you still get errors.
Do not leave your /system writable; after you have changed what you wanted, you shall remount ro ...

[Completed] Permissions on /system/etc reference

I was trying to enable writing titanium backups to the SDCard by editing the file:
/system/etc/permissions/platform.xml
However I was not paying attention and now everytime I boot up I get spammed with error messages "Unfortunatley, the process com.google.process.gapps has stopped". All apps also produce a force close saying about the same thing. Continuously. I can recieve calls and open up a couple of apps but only by the small window between closing error messages. Here are the steps I took when editing the platform.xml
First I edited the file as suggested:
Original:
Add the media_rw group:
Then I copied the file back to the SDCard. After that I overwrote it in /system/etc/permissions. Not realizing the permissions were incorrect. I restarted the device and started getting errors. I assumed it was the file permissions so I started up ADB and entered the following lines:
mount | grep system
mount -o rw,remount /dev/block/platform/msm_sdcc.1/by-name/system /system
chmod 326 /system/etc
chmod 644 /system/etc/permissions/platform.xml
chmod 644 /system/etc
mount -o ro,remount /dev/block/platform/msm_sdcc.1/by-name/system /system
That changed the file permissions so I rebooted by my device and got stuck in a boot loop.
So I rebooted into Clockworkmod recovery and tried to restore a working backup of my stock ROM. Got past the boot loop but still spammed by errors, so I tried to restore just the /system partition from the recovery using Clockwork's advanced tab. Seems like the errors are even worse. I wanted to know if by my description someone could give me a push in the right direction. Does anyone know what permissions the /system/etc folder is supposed to have? I suspect the reason this is happening is because I changed the /system/etc permissions instead of just changing /system/etc/permissions. Please offer any knowledge you have. I've pretty much exhausted the first few pages of Google and I don't want to give up and factory reset just yet.
Thank you

Hi,
I need to know your device and exact model to point you in the right direction for help.

I have a Samsung S4 with Tmobile. SGH-M919 version 4.4.4.4, I'm running stock ROM with Clockworkmod recovery. Just an update I can use ADB reliably in Clockwork's recovery mode. Though I'm not familiar with the file structure now that /system isn't mounted and everything seems to be in a different place. After the previous post I tried to mount /dev/block/platform/msm_sdcc.1/by-name/system by using:
mount -o rw,remount /dev/block/platform/msm_sdcc.1/by-name/system
but the ADB session was disconnected in the middle and on reboot I'm now with no touch ability to close the error messages. I tried wiping the Dalvik Cache and the other Cache. Now I'm just browsing in Recovery through ADB looking for answers.

Then here is the best place to ask for help,
> T-Mobile Samsung Galaxy S 4 > T-Mobile Samsung Galaxy S 4 Q&A, Help & Troubleshooting > [HELP THREAD] Samsung Galaxy S4 T Mobile Version | Ask ANY Question | Noob Friendly
Good luck!

Thank you. Thread closed.

[Completed] irulu 10.1 root/remount problems solved

I own an irulu K1001L1 10.1 (build number A20_K1001_K1001L1.20130713), a cheap one.
Many people complain about "partial rooting" and being unable to remount system in rw mode. Clueless as I was, I had tried several times with Uberizer, z4root and SRSroot, to no avail (the problem is not in the root, in my tablet su came by default in xbin directory).
D_rex (http://forum.xda-developers.com/showthread.php?t=2606510&page=2) found an effective solution which also helped in my situation: I think my tablet came with "su" application by default (notice overclocking worked) but due to /dev/block/nandd ext4 partition (I think /system starts at some offset) containing some errors (seen in dmesg) and due to this partition having the "s_errors" flag (behavior when errors detected) set to "mount read-only (02)", the partition is ALWAYS mounted read only, and remount as root doesn't change anything. More info on this ext4 option can be found here
For me, the solution that worked was changing that flag s_errors to continue (01). I wasn't able to run e2fsck as the partition is already mounted; and I wasn't able to do a fsck in recovery mode since the recovery mode of this tablet lacks seems to lack both shell and e2fsck.
Tune2fs (old version precompiled here) can change that flag in the partition. Using adb shell I pushed it to de device, set attribute as executable and run it, successfuly changing that "behavior when errors detected" in both partitions.
It has been suggested filesystem errors are linked to stability and realiability problems. Unfortunately this tablet lacks a version of CWM o TWRP as a recovery custom rom. I also adjusted the "max-mount-counts" value via tune2fs -c hoping it forces Android to run e2fsck, but it seems dmesg keeps displaying errors. I can only hope this problem is given more attention by developers.
After this I used the usual tools to root the device, noticing I had spent many hours in this cheap tablet.
On a side note, the adb driver setup tool found here didnt work for me (it seems &USER_PROFILE% in the .bat file should be replaced by "%USER_PROFILE%" and Desktop should be replaced according to the language of your operating system. Nevertheless the tool didn't work for me and I had to install another driver found in Uberizer distribution as the official "android_winusb.inf" didn't work in my Windows XP computer.
Thanks to the creators of tune2fs, to D_rex and other people/programs mentioned here. This is my experience with this problem; I'm not responsible if anyone tries this and bricks his device. All brands are property of their owners.
edition: should also mention by default now my tablet mounts in read-only mode (which is of course safer) but lets me change to rw whenever I want

Hi there,
Sorry but this forum is not for guide and tutorials.
The mission of XDA Assist is to provide basic help to those who have tried searching but can't find what they are looking for and need assistance. This is not a "helpdesk" providing technical assistance but more to point you in the correct direction with your problem. Perhaps you can't find posts on how to root your phone, install custom recovery or maybe you have questions about how to navigate and use features on the site.
Click to expand...
Click to collapse
You can post your thread, in this forum:
> Android Development and Hacking > Android Q&A, Help & Troubleshooting
Good luck
Thread closed

[Completed] [Q] Chinese Tablet Root Problem

Hi all! I hope this is the correct place where to ask this kind of question. I have a Chinese tablet that I need to root in order to run some applications. It mounts a 4.4.2 Android version and I can access via adb by opening an adb root shell. The table is called letine lt707a .
This is what I did:
Code:
adb shell mount -o remount,rw /system
adb push su /system/xbin
adb shell busybox chmod 6755 /system/xbin/su
Then I installed a version of Superuser.apk. When I open a terminal emulator app from the device, if I write "su" I obtain a "Permission denied" message.
Where is the problem? Maybe I have an old binary su? I can't understand
I also tried with SuperSU without any results

Hi there,
I'm sorry but I can't find anything related to your question/device:
Please post that in the forum bellow for more answers from the experts:
> Android Development and Hacking > Android Q&A, Help & Troubleshooting
Good luck

Ok, thank you for your time!

Thread closed, thank you