Hello, I have a serious problem.
I am using adb for hacking my Android Galaxy 5 smartphone.
Wifi got broken because I can't make file /data/misc/wifi/wpa_supplicant.conf executable.
Issuing chmod 755 have no effect, even after remounting the system as rw with command
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Consequence: Wifi is broken. I have no idea about how to prevent this behaviour of chmod. Can you help me?
Solved: I was confunding two files: wpa_supplicant and wpa_supplicant.conf. Sorry
Related
how to replace? by using metamorph? i did with root explorer and ended up with bricked x10 mini.
It's probably best to do it via ADB.
yes adb / shell is my favourite method
I use Root expl. only to rw mount /system partition.
How to do via adb?
Sent from my E10i using XDA App
from: http://forum.xda-developers.com/showthread.php?t=759320
0. Root !
1. adb push framework-res.apk /sdcard/fr-black.apk
2. adb shell
3. su
4. mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
5. mv /system/framework/framework-res.apk /sdcard/framework-resORIG.apk
6. cat /sdcard/fr-black.apk > /system/framework/framework-res.apk
7. chmod 755 /system/framework/framework-res.apk
8. sync
9. reboot
why cat and not mv/cp ? Because the file is created with "root" user and group and not "sdcard" group.
Means the framework file is first placed on sd card which i want to replace? Asking noob questions cause dnt want to install whole software again
Sent from my E10i using XDA App
abhi98228 said:
Means the framework file is first placed on sd card which i want to replace? Asking noob questions cause dnt want to install whole software again
Click to expand...
Click to collapse
Here, I'll try to explain what happens
1. adb push framework-res.apk /sdcard/fr-black.apk
-copies "frarework-res.apk" from ADB's folder and moves it to the phone's SD card, names it "fr-black.apk"
2. adb shell
-opens the linux shell on the phone
3. su
-goes into superuser mode, i.e. runs apps as admin if you're familiar with windows terms
4. mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
-remounts the /system folder on the phone so that it is read-write, allowing you to mess with the system files
5. mv /system/framework/framework-res.apk /sdcard/framework-resORIG.apk
-backs up the default framework-res.apk from the phone by moving it to the SD card
6. cat /sdcard/fr-black.apk > /system/framework/framework-res.apk
-copies the fr-black.apk from the SD card and puts it in the old framework-res' place
7. chmod 755 /system/framework/framework-res.apk
-changes the user permissions for the new file
Eseb0 said:
Here, I'll try to explain what happens
1. adb push framework-res.apk /sdcard/fr-black.apk
-copies "frarework-res.apk" from ADB's folder and moves it to the phone's SD card, names it "fr-black.apk"
2. adb shell
-opens the linux shell on the phone
3. su
-goes into superuser mode, i.e. runs apps as admin if you're familiar with windows terms
4. mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
-remounts the /system folder on the phone so that it is read-write, allowing you to mess with the system files
5. mv /system/framework/framework-res.apk /sdcard/framework-resORIG.apk
-backs up the default framework-res.apk from the phone by moving it to the SD card
6. cat /sdcard/fr-black.apk > /system/framework/framework-res.apk
-copies the fr-black.apk from the SD card and puts it in the old framework-res' place
7. chmod 755 /system/framework/framework-res.apk
-changes the user permissions for the new file
Click to expand...
Click to collapse
hehe ty bro
Hi
I need some help pls, when i wanna replace the framework-res.apk i get this:
C:\exploid_x10mini>adb push framework-res.apk /sdcard/fr-black.apk
* daemon not running. starting it now *
* daemon started successfully *
1523 KB/s (7108054 bytes in 4.557s)
C:\exploid_x10mini>adb shell
$ su
su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
# mv /system/framework/framework-res.apk /sdcard/framework-resORIG.apk
mv /system/framework/framework-res.apk /sdcard/framework-resORIG.apk
failed on '/system/framework/framework-res.apk' - Cross-device link
Please help
try
mount -o rw,remount /dev/block/mtdblock0 /system
and check first-after with mount bash command the mountpoint
oversim said:
try
mount -o rw,remount /dev/block/mtdblock0 /system
and check first-after with mount bash command the mountpoint
Click to expand...
Click to collapse
I still get the same:
C:\exploid_x10mini>adb shell
$ su
su
# mount -o rw,remount /dev/block/mtdblock0 /system
mount -o rw,remount /dev/block/mtdblock0 /system
# mv /system/framework/framework-res.apk /sdcard/framework-resORIG.apk
mv /system/framework/framework-res.apk /sdcard/framework-resORIG.apk
failed on '/system/framework/framework-res.apk' - Cross-device link
#
Can you explain .. " and check first-after with mount bash command the mountpoint" .. please
Skip mv step instade backup by root expkorer.
Sent from my E10i using XDA App
Thank you my mini is now black
kimb0 said:
Hi
I need some help pls, when i wanna replace the framework-res.apk i get this:
C:\exploid_x10mini>adb push framework-res.apk /sdcard/fr-black.apk
* daemon not running. starting it now *
* daemon started successfully *
1523 KB/s (7108054 bytes in 4.557s)
C:\exploid_x10mini>adb shell
$ su
su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
# mv /system/framework/framework-res.apk /sdcard/framework-resORIG.apk
mv /system/framework/framework-res.apk /sdcard/framework-resORIG.apk
failed on '/system/framework/framework-res.apk' - Cross-device link
Please help
Click to expand...
Click to collapse
you can use cat /system/framework/framework-res.apk > /sdcard/framework-resORIG.a
as a work around
It help me
can't remount...trying to push .apk
sh-3.2# ./adb devices
List of devices attached
TA07302MDF device
sh-3.2# ./adb remount
remount failed: Operation not permitted
sh-3.2# ./adb shell
$ su
#
you can see i have root
droid x2 liberty 3 rom moto one click root
fixed it for anyone else having trouble
sh-3.2# ./adb devices
List of devices attached
TA07302MDF device
sh-3.2# ./adb remount
remount failed: Operation not permitted
sh-3.2# ./adb shell
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# chmod 777 /system/framework
# exit
$ exit
sh-3.2# ./adb push framework-res.apk system/framework/
1055 KB/s (4096287 bytes in 3.788s)
sh-3.2#
thetdy said:
fixed it for anyone else having trouble
sh-3.2# ./adb devices
List of devices attached
TA07302MDF device
sh-3.2# ./adb remount
remount failed: Operation not permitted
sh-3.2# ./adb shell
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# chmod 777 /system/framework
# exit
$ exit
sh-3.2# ./adb push framework-res.apk system/framework/
1055 KB/s (4096287 bytes in 3.788s)
sh-3.2#
Click to expand...
Click to collapse
accually you could just us this
# mount -o remount,rw /dev/block/mtdblock3 /system
should work just fine without the -t yaffs2 i know it works on the samsungs
Is it possible to do the AdHoc modification on a rooted HD/HD+ as documented in the below thread...
[FIX] adhoc wifi Nook Tablet 0.6.10 tiwlan0
Or will it cause the bootloop/reformat issue?
PokrTom
Unfortunately, the answer is no.
After waiting for an answer from those who had more knowledge then myself I decided to make myself the Guinean pig, Did a Timbuktu backup and made the mod, rebooted and watched my Nook reboot eight times and reformat.
So the short answer, at least for now, is no.
Which sucks because I make a regular use of using my phone for net use, so I hope something comes along soon.
Interim fix?
I tried seeing if there might be an interim fix option and I am hoping there is someone with more expertise that might be able to help me here.
Here is my thought.
When a user wants to use An Ad-Hoc connection they would execute a script like the below...
Code:
mount -o remount,rw /system
chmod 777 /system/bin/wpa_supplicant
cp /system/bin/wpa_supplicant /mnt/sdcard/mods/wpa_supplicant.nookhd
cp /mnt/sdcard/mods/wpa_supplicant.omap4.adhocfix /system/bin/wpa_supplicant
chown root /system/bin/wpa_supplicant
chmod 755 /system/bin/wpa_supplicant
mount -o remount,ro /system
When they were finished they would then have to run a clean up script like this...
Code:
mount -o remount,rw /system
chmod 777 /system/bin/wpa_supplicant
cp /mnt/sdcard/mods/wpa_supplicant.nookhd /system/bin/wpa_supplicant
chown root /system/bin/wpa_supplicant
chmod 755 /system/bin/wpa_supplicant
mount -o remount,ro /system
I used G-Script for the above steps for ease of use.
Obviously, they could not reboot while utilizing Ad-Hoc
Whats needed is the wpa_supplicant file to use for the fix. The one utilized by the Nook Tablet above does not work. The process itself has promise as I have tried it and while I could not get it to work, it did put the wpa_supplicant file to use and it did not reformat my device after I power cycled my device.
im running 2.3.4 android version..
unlocked bootloader....followed the instruction in this link to root my atrix
http://forum.xda-developers.com/showthread.php?t=1202883
but after entering this command
/preinstall/dosu
im getting this error..
please see cmd log below
C:\>cd atrix
C:\atrix>adb shell
$ /preinstall/dosu
/preinstall/dosu
bash: groups: command not found
[email protected]:/# /bin/mount -o remount,rw /system
/bin/mount -o remount,rw /system
[email protected]:/# cp /preinstall/su /system/bin/
cp /preinstall/su /system/bin/
cp: write error: Read-only file system
[email protected]:/# chmod 6755 /system/bin/su
chmod 6755 /system/bin/su
chmod: /system/bin/su: Read-only file system
[email protected]:/#
vdpraneeth said:
im running 2.3.4 android version..
unlocked bootloader....followed the instruction in this link to root my atrix
http://forum.xda-developers.com/showthread.php?t=1202883
but after entering this command
/preinstall/dosu
im getting this error..
please see cmd log below
C:\>cd atrix
C:\atrix>adb shell
$ /preinstall/dosu
/preinstall/dosu
bash: groups: command not found
[email protected]:/# /bin/mount -o remount,rw /system
/bin/mount -o remount,rw /system
[email protected]:/# cp /preinstall/su /system/bin/
cp /preinstall/su /system/bin/
cp: write error: Read-only file system
[email protected]:/# chmod 6755 /system/bin/su
chmod 6755 /system/bin/su
chmod: /system/bin/su: Read-only file system
[email protected]:/#
Click to expand...
Click to collapse
this is the other more error im getting
# /bin/mount /system -o remount,rw
/bin/mount /system -o remount,rw
mount: block device /dev/block/mmcblk0p12 is write-protected, mounting read-only
/system file remains read only
vdpraneeth said:
im running 2.3.4 android version..
unlocked bootloader....followed the instruction in this link to root my atrix
http://forum.xda-developers.com/showthread.php?t=1202883
but after entering this command
/preinstall/dosu
im getting this error..
please see cmd log below
C:\>cd atrix
C:\atrix>adb shell
$ /preinstall/dosu
/preinstall/dosu
bash: groups: command not found
[email protected]:/# /bin/mount -o remount,rw /system
/bin/mount -o remount,rw /system
[email protected]:/# cp /preinstall/su /system/bin/
cp /preinstall/su /system/bin/
cp: write error: Read-only file system
[email protected]:/# chmod 6755 /system/bin/su
chmod 6755 /system/bin/su
chmod: /system/bin/su: Read-only file system
[email protected]:/#
Click to expand...
Click to collapse
I have an unlocked AT&T Atrix (MB860) with GB 2.3.4 and I have exactly the same problem: that the /system folder remains stubbornly read only, no matter what I do. I have tried a lot of the methods I found in the forums and elsewhere, but to no avail. I suspect the only effective solution will be to install a full .sbf image with an already rooted /system folder, but that will be the very last resort. We are not the only ones with this problem; I have seen the messages of a few others. On some phones, the easy methods just do not seem to work.
So, have you, or others, found an acceptable solution other than to install a rooted sbf image?
I'm a Sony user so not sure if this applies too but is USB debugging on?
Sent from my LT18i using xda premium
/system remains read only
I have an unlocked AT&T Atrix (MB860) with GB 2.3.4 and I have exactly the same problem: that the /system folder remains stubbornly read only, no matter what I do. I have tried a lot of the methods I found in the forums and elsewhere, but to no avail. I suspect the only effective solution will be to install a full .sbf image with an already rooted /system folder, but that will be the very last resort. We are not the only ones with this problem; I have seen the messages of a few others. On some phones, the easy methods just do not seem to work.
So, have you, or others, found an acceptable solution other than to install a rooted sbf image?
I don't remember how i rooted the phone but specifing the filesystem might help
try using
/system/bin/mount -t ext3 -o remount,rw /system
Click to expand...
Click to collapse
My Kindle fire hdx 8.9 worked normally since I bought it. Yesterday I remove the signature to install google service, and the wrong was it can't restart and I reset it to the factory from recovery. Now it still rest on the colored "kindle fire". But it seems some processes have been loaded because the MTP devices can be found in PC and the adb mode seems work normally. I think some steps losed in the boot. Can I recover it by adb mode or other methods? Thank you.
I reset it to the factory from recovery.
Click to expand...
Click to collapse
very bad, you lost root, so no ideas.
But try:
Code:
adb shell
su
ONYXis said:
very bad, you lost root, so no ideas.
But try:
Code:
adb shell
su
Click to expand...
Click to collapse
Yes , the root tools can work. Input su and display "[email protected]:/#". It seems something different with the bricked in forum.
tianlie said:
Yes , the root tools can work. Input su and display "[email protected]:/#". It seems something different with the bricked in forum.
Click to expand...
Click to collapse
Good.
You need put back original files:
services.odex and any others that you changed
like this:
Code:
adb shell
su
mount -o remount /system
adb push services.odex /data/local/tmp
chmod 755 /data/local/tmp/services.odex
rm /system/framework/services.odex
cp /data/local/tmp/services.odex /system/framework/services.odex
chmod 755 /system/framework/services.odex
reboot
or simple
Code:
adb shell
su
mount -o remount /system
rm /system/framework/services.odex
adb push services.odex /system/framework/
chmod 755 /system/framework/services.odex
reboot
ONYXis said:
Good.
You need put back original files:
services.odex and any others that you changed
like this:
Code:
adb shell
su
mount -o remount /system
adb push services.odex /data/local/tmp
chmod 755 /data/local/tmp/services.odex
rm /system/framework/services.odex
cp /data/local/tmp/services.odex /system/framework/services.odex
chmod 755 /system/framework/services.odex
reboot
or simple
Code:
adb shell
su
mount -o remount /system
rm /system/framework/services.odex
adb push services.odex /system/framework/
chmod 755 /system/framework/services.odex
reboot
Click to expand...
Click to collapse
"adb push services.odex /data/local/tmp" This command give an error: device not found.
Does it need the file "services.odex"? Where?
Thanks a lot.
The complete response:
D:\win32>adb shell
[email protected]:/ $ su
su
[email protected]:/ # mount -o remount /system
mount -o remount /system
[email protected]:/ # rm /system/framework/services.odex
rm /system/framework/services.odex
[email protected]:/ # adb push services.odex /system/framework/
adb push services.odex /system/framework/
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/ # chmod 755 /system/framework/services.odex
chmod 755 /system/framework/services.odex
Unable to chmod /system/framework/services.odex: No such file or directory
10|[email protected]:/ # reboot
reboot
Sorry. Syntax error. I am at gym now. Ill help you when come home. What version of firmware do you use?
ONYXis said:
Sorry. Syntax error. I am at gym now. Ill help you when come home. What version of firmware do you use?
Click to expand...
Click to collapse
It should be 14.3.2.5. OK. I wait you.:good:
https://www.dropbox.com/s/tfd5htc9smt17nx/Desktop.zip?dl=0
Code:
adb push C:\Users\xxx\Desktop\services.odex /sdcard/services.odex
adb shell
su
mount -o remount /system
cp /sdcard/services.odex /system/framework/services.odex
chmod 755 /system/framework/services.odex
reboot
If it will not help - try to put back framework-res.apk.
ONYXis said:
https://www.dropbox.com/s/tfd5htc9smt17nx/Desktop.zip?dl=0
Code:
adb push C:\Users\xxx\Desktop\services.odex /sdcard/services.odex
adb shell
su
mount -o remount /system
cp /sdcard/services.odex /system/framework/services.odex
chmod 755 /system/framework/services.odex
reboot
If it will not help - try to put back framework-res.apk.
Click to expand...
Click to collapse
That's great! Kindle is upgrading... Select language, register, the desktop come back.
Thank you, ONYXis, you are my god!:good:
To others, don't think the factory set is best.
Thank you again.