extract-files.sh won't extract proprietaries from /system/bin - Android Q&A, Help & Troubleshooting

Ok so I'm trying to extract propritaries from my phone script starts and extract files but it won't extract files from /system/bin and /xbin while files from /system/lib are extracted without any problems, I checked permissions and they are same for those folders (755).
I checked for files and they are there, they exist on phone while adb states otherwise.
Note that I don't have root and don't have a good way to do that.
here is extract-files.sh and proprietary-files-mtk.txt

What I am understanding from this post is that you have a script to extract files from your /system/bin directory for your phone? Since you have adb, go to adb shell and type in whoami. If it says shell, then you're not root and can't proceed further. If it says root, then do mount | grep system. If it shows system is ro, then you need to remount system by using mount -o rw,remount /system and make sure doing mount | grep system shows rw. It should work then.

mohhaxs said:
What I am understanding from this post is that you have a script to extract files from your /system/bin directory for your phone? Since you have adb, go to adb shell and type in whoami. If it says shell, then you're not root and can't proceed further. If it says root, then do mount | grep system. If it shows system is ro, then you need to remount system by using mount -o rw,remount /system and make sure doing mount | grep system shows rw. It should work then.
Click to expand...
Click to collapse
Why would I need rw permission on /system/ when I just want to pull files from it, not to push, and also why then it works with /system/lib/ folder, both have 755 permisons, and pull from /lib/ folder works but not for /bin/ and /xbin/ ?
It doesn't say permission denied it says file does not exist which is false because file does exist.

Professor Woland said:
Why would I need rw permission on /system/ when I just want to pull files from it, not to push, and also why then it works with /system/lib/ folder, both have 755 permisons, and pull from /lib/ folder works but not for /bin/ and /xbin/ ?
It doesn't say permission denied it says file does not exist which is false because file does exist.
Click to expand...
Click to collapse
It's because of your phones security. Look at the following files from my phones /system/lib. You can see, they're root group and only root user can modify them or even take them off device. Which means, you need to be root user to make any modifications to them.
drwxr-xr-x 2 root root 4096 2008-12-31 10:00 soundfx
drwxr-xr-x 3 root root 4096 2008-12-31 10:00 ssl
lv7:/system/lib #
Going to /system/bin ...
lrwxr-xr-x 1 root shell 6 2008-12-31 10:00 xxd -> toybox
lrwxr-xr-x 1 root shell 6 2008-12-31 10:00 yes -> toybox
lv7:/system/bin #
The following files are part of root group but shell user. So if you do the command "whoami" and are shell user, you can change these files and extract them off your phone.
The permissions don't matter here, you need to be root user and have rw permission on system. If you can give me the code of your script, I can tell you what it is doing. If I were you, try using the command prompt and use the adb pull command and it will give you the permission denied error.

mohhaxs said:
It's because of your phones security. Look at the following files from my phones /system/lib. You can see, they're root group and only root user can modify them or even take them off device. Which means, you need to be root user to make any modifications to them.
drwxr-xr-x 2 root root 4096 2008-12-31 10:00 soundfx
drwxr-xr-x 3 root root 4096 2008-12-31 10:00 ssl
lv7:/system/lib #
Going to /system/bin ...
lrwxr-xr-x 1 root shell 6 2008-12-31 10:00 xxd -> toybox
lrwxr-xr-x 1 root shell 6 2008-12-31 10:00 yes -> toybox
lv7:/system/bin #
The following files are part of root group but shell user. So if you do the command "whoami" and are shell user, you can change these files and extract them off your phone.
The permissions don't matter here, you need to be root user and have rw permission on system. If you can give me the code of your script, I can tell you what it is doing. If I were you, try using the command prompt and use the adb pull command and it will give you the permission denied error.
Click to expand...
Click to collapse
I used adb pull and it gave me same error, "file does not exist".
Why would I need rw permission when I only want to read file not modify it.
I pulled whole bin folder and when pulled it has missing about 100 files every one I have needed was in that 100 files. However I give up and just copy files to sd card from total commander and transfered them via USB to PC

Related

installing root, flash_image permission denied

going through the entire 1.5 to 2.1 root tutorial to a tee, but once i get to the recovery image, this happens (following is an entire copy/paste of what I went through, incase i did something wrong before i hit the point)
Code:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Lemcott>cd C:\android-sdk-windows\tools
C:\android-sdk-windows\tools>adb shell mount -o rw,remount /dev/block/mtdblock3
/system
adb server is out of date. killing...
* daemon started successfully *
C:\android-sdk-windows\tools>adb shell mount -o rw,remount /dev/block/mtdblock3
/system
C:\android-sdk-windows\tools>adb push recovery.img /sdcard
1192 KB/s (3926016 bytes in 3.215s)
C:\android-sdk-windows\tools>adb push flash_image /system/bin/flash_image
448 KB/s (9640 bytes in 0.021s)
C:\android-sdk-windows\tools>adb shell flash_image recovery /sdcard/recovery.img
flash_image: permission denied
C:\android-sdk-windows\tools>
EDIT: I am a complete ass hat. nothing to see here, move a long. mods delete this if you please.
P.S. Everyone else: ALWAYS DOUBLE CHECK BEFORE POSTING FOR HELP. *ahem* now be on your way.
try programming thru fastboot. press call + vol down and select the fastboot option and use this command from the pc
fastboot flash recovery recovery.ing
Sent from my Evil Eris v1.1 using the XDA mobile application powered by Tapatalk
It looks like you forgot the step where you modify the flash_image's permissions
Code:
adb shell chmod 755 /system/bin/flash_image
I had the same thing but I just kept reentering
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery.img /sdcard
adb push flash_image /system/bin
and after maybe 4 iterations it worked.
I have a very simular problem:
(moto droid with android 2.1)
$su
su
Permission denied
Click to expand...
Click to collapse
I have try to use chmod the file but it said permission denied on chmod... please help T_T
note this is rooted, of course, when i'm in the phone type su, it'll pop up ask for me to allow or not, allowed, everything seems fine, but when i try to modify files in /system/etc/wifi (trying to make it work for ad hoc) it said permission denied....(even in su???) I tried in adb and it's the same, very very frustrating, any help is appreciated, Thanks.
edit: here's what it looks like using chmod...
>adb shell chmod 755 /system
unable to chmod /system: Read-only file system
>
Click to expand...
Click to collapse
penthoy said:
I have a very simular problem:
(moto droid with android 2.1)
I have try to use chmod the file but it said permission denied on chmod... please help T_T
note this is rooted, of course, when i'm in the phone type su, it'll pop up ask for me to allow or not, allowed, everything seems fine, but when i try to modify files in /system/etc/wifi (trying to make it work for ad hoc) it said permission denied....(even in su???) I tried in adb and it's the same, very very frustrating, any help is appreciated, Thanks.
edit: here's what it looks like using chmod...
Click to expand...
Click to collapse
make it read/write
penthoy said:
I have a very simular problem:
(moto droid with android 2.1)
I have try to use chmod the file but it said permission denied on chmod... please help T_T
note this is rooted, of course, when i'm in the phone type su, it'll pop up ask for me to allow or not, allowed, everything seems fine, but when i try to modify files in /system/etc/wifi (trying to make it work for ad hoc) it said permission denied....(even in su???) I tried in adb and it's the same, very very frustrating, any help is appreciated, Thanks.
edit: here's what it looks like using chmod...
Click to expand...
Click to collapse
I wouldn't try to flash anything you find here to a Moto Droid.
This is for the HTC Droid Eris.
Otherwise, and if I'm misunderstanding you, good luck with your problem.
archmagus said:
It looks like you forgot the step where you modify the flash_image's permissions
Code:
adb shell chmod 755 /system/bin/flash_image
Click to expand...
Click to collapse
I've been bashing my head in ALL day trying to get past this and finally found this thread! This worked perfectly!
theboo7 said:
make it read/write
Click to expand...
Click to collapse
How should i make is read/write?????
i cant get it to work at all.. need help plz.
Hello Guys
why cant i mount that **** together, i have the root permission, but also i dont..somehow
Code:
Microsoft Windows [version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. Alle rettigheder forbeholdes.
C:\Users\Rasmus H. G. Johnsen>d:
D:\>cd android\tools
D:\android\tools>adb devices
List of devices attached
HT9B7LG00092 device
D:\android\tools>adb shell mount -o rw,remount /dev/block/mtdbloc3 /system
mount: Operation not permitted
D:\android\tools>adb shell
$ ls
ls
sqlite_stmt_journals
cache
sdcard
etc
system
sys
sbin
proc
logo.rle
init.rc
init.goldfish.rc
init.bahamas.rc
init
default.prop
data
root
dev
$ exit
exit
Also if I go on and try to do this:
Code:
D:\android\tools>adb push flash_image /system/bin
failed to copy 'flash_image' to '/system/bin/flash_image': Read-only file system
I know that the flash_image fil and my recovery.img file is in this library and also on my sdcard, but I cant push the gotdamn flas_image file in the /system/bin catalog.
Can some one please help me ?
PS. I have the USB-debugging turned ON.
How do you know that you have root? Or, how did you gain root?
doogald said:
How do you know that you have root? Or, how did you gain root?
Click to expand...
Click to collapse
I have the app called androot from google market, ang i have run it to get root.
wfdi said:
I have the app called androot from google market, ang i have run it to get root.
Click to expand...
Click to collapse
I'm not aware of that app, and cannot find it in the market myself (do you have a link?)
However, one way to check for sure if you truly have root is run the adb command adb shell and, when you get a prompt, type the command "su". If it returns with a "#" prompt (rather than the "$" prompt that you are seeing), then you have root on the phone.
Most people these days root with either jcase's 1click root for eris: https://market.android.com/details?id=net.andirc.erisrooter or they use the procedure here: http://androidforums.com/eris-all-things-root/127861-universal-eris-root-dummies.html
You may be able to use the steps here as well, since you seem pretty comfortable with adb and have that working already: http://androidforums.com/eris-all-things-root/125436-detailed-leak-root-tutorial.html
Guys new I found another solution (tested on u8150)
First make sure that you are rooted first.
Open adb shell
Type in su.
Remount the system partition as read write.
Change the owner of system from root to system via chown root system
the exit the shell and push flash_image to system/
also push clockworkmodrecover.img into the system partion dont forget the last /.
then exit.
use a file manager, I used rootbrowser.apk without a memory card and installed recovery.
with rootbrowser copy flash_image to the bin directory.
don't forget to change the owner back to root to the system partition after you finish with rootexplorer or whatever u use even adb can work.
then the rest follows.
The above works only if your'e rooted and have adb.
Goodluck
haha am a genius Installing ROM +Recover without sdcard on u8150
all you have to do is:-
1. Make sure u have installed clockwork mode recovery on your device and have su binary.
2. Open adb with the device normally on.
3. Remount the data partition as read write using mount remount in adb .
4. use adb and push the cynogenmode.zip or any rom that fits into the data partition using
adb push romname.zip /data/
5. Reboot into clockworkmod recovery using the various options available.
6. This is what to do if you don't have a sdcard.
open adb with phone connected and run
adb shell
mount /data /sdcard
then go back to the main recovery menu and wipe dalvik cache only
then choose update from sdcard
flash your rom and tadaaa.
your'e done.
NB:CAUTION MAKE SURE TO FLASH A ROM THAT DOES NOT WRITE INTO THE DATA PARTION
THIS CAN BE DONE BY LOOKING FOR A FILE CALL UPDATE SCRIPT IN THE zip OF THE ROM U WANT TO INSTALL
Am going to make a post about this later.
Goodluck
Lol, 3 and a half year break between responses.
The problem with flash_image & dump_image is that it doesn't work on devices devices which use emmc (recent phones)and have
mmcblk0
and cat /proc/mtd won't work here either.
This means that you have to use dd to write to this devices.
I wonder how guys determine the partitions to use on such devices, and someone should hint as to what is going on since it seems manufacturers seriously don't want people to exploit their devices.

[Q] Root Problem - adb Shell and Permisson Denied

Hi all,
I tried all root applications and scripts to make my rk30sdk device rooted. They were not working.
So i decided to make it with adb, istalled Android SDK and make platform-tools as a system variable.
So i can see my device with adb,
Code:
C:\android_sdk\sdk\platform-tools>adb devices
List of devices attached
LZXOJ5SDTF device
Aftet adb shell, i can took list of directories from device.
Code:
C:\Windows\System32>adb shell
[email protected]:/ $ ls
ls
acct
bcm4329_cybertan.hcd
bcm4329_samsung.hcd
bcm4329_usi.hcd
cache
charger
config
d
data
default.prop
dev
etc
init
init.goldfish.rc
init.rc
init.rk30board.rc
init.rk30board.usb.rc
init.trace.rc
init.usb.rc
initlogo19.rle
initlogo20.rle
mnt
proc
readahead_list.txt
res
rk30xxnand_ko.ko.3.0.36+
rk30xxnand_ko.ko.3.0.8+
root
sbin
storage
sys
system
ueventd.goldfish.rc
ueventd.rc
ueventd.rk30board.rc
vendor
But i can not copy su, pwd and other tools to correct folders. It gives me that Permission Denied. I know this means that the rk30sdk not rooted.
I can put su, pwd, Superuser.apk, busybox to an +rw directory in SD card, but i can not install Superuser.apk successfully, it says it can not find su file.
Could you please share your comments and ideas. I am using Win7 OS. But i tried it is same on MAC OS X.
Thanks.

adb shell root can not remove files

Hello,
I have one serious probleme !! When i use adb shell with root i can't remove files from one folder named clockwordmod in sdcard. I've tried chmod permissions of files and then does not work to :/ the output (name of file): permition denied . And the output of ls -l is -rw-rw---- root sdcard_r (size) (date) (name of fil) any one can help me with this situation? Thanks
Regards

modifying image with new files

Hello,
I am trying to create a custom system image.
I use simg2img & img2simg , to extract , change , and pack again.
I can flash modification in system.img,
so I try to program some files (called ranran1, ranran2), and su utility (arm build)in filesystem into /etc/su (Is that enough ?)
but on trying to view the files in /etc, it gives me "permission denied" on any new file (ranran1, ranran2), although I changed them in the mounted fs, to chmod 777.
-rw-r--r-- root root 76790 2009-01-01 10:00 preloaded-classes
-rw-r--r-- root root 16384 2009-01-01 10:00 qcril.db
lstat './ranran1' failed: Permission denied
lstat './ranran2' failed: Permission denied
-rw-r--r-- root root 749737 2009-01-01 10:00 recovery-resource.dat
-rw-r--r-- root root 34058 2009-01-01 10
Any idea what's wrong ? Is it correct to put "su" binary in system image in order to root device ?
Thanks,
ranchu

i/o error when trying to write to etc on rooted Xperia Premium

Hi, I'm completly lost. I'm trying to get Daydream running on a Sony Xperia XZ Premium (XZP). I read that 2 files must be modified for this. I already edited the build.prop file in /system. But the second one, the handheld_core_hardware.xml is for some reason not where it should be. I backed up the TA-partion and flashed the firmware "G8141_MobilTel EAD BG_1309-2357_47.2.A.10.62_R2C" with the kernel "boot-G8141-47.2.A.10.62-hideunlock-magisk-19.3.img" following the instructions here on XDA. Using ADB I open a root shell (ADB shell, su) and try to copy a modified version of the XML file from data/local/tmp to system/etc/permissions after re-mounting /system in rw-mode. I got the file by extracting the ext4-image in the system.sin of the firmware pack and pushed it to tmp using ADB. When I try to copy the file, I either get "I/O error" or no error. In the latter case the file is nevertheless not copied and I get the I/O error when mounting to ro-mode again. It's also strange that in this case I can cat the contents and list it via ls -l but only if I use the exact name no wildcards. On next boot or when ro-mounting succeeds its completely gone.
This is how it looks on the shell:
Code:
127|G8141:/system/etc/permissions # ls -l handheld_core_hardware.xml
ls: handheld_core_hardware.xml: No such file or directory
1|G8141:/system/etc/permissions # cp /data/local/tmp/handheld_core_hardware.xml /system/etc/permissions
cp: /system/etc/permissions/handheld_core_hardware.xml: I/O error
1|G8141:/system/etc/permissions # ls -l /data/local/tmp
total 12
-rw-rw-rw- 1 shell shell 4877 2019-09-06 10:03 handheld_core_hardware.xml
drwxr-xr-x 2 root root 4096 2019-09-06 11:47 test
G8141:/system/etc/permissions # mount | grep system
/dev/block/dm-0 on /system type ext4 (rw,seclabel,relatime,block_validity,discard,delalloc,barrier,user_xattr)
/dev/block/sde33 on /system/vendor/firmware_mnt type vfat (ro,context=u:object_r:firmware_file:s0,relatime,gid=1000,fmas
k=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)
/dev/block/sde37 on /system/vendor/bt_firmware type vfat (ro,context=u:object_r:bt_firmware_file:s0,relatime,uid=1002,gi
d=3002,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)
/dev/block/sde34 on /system/vendor/dsp type ext4 (ro,seclabel,nosuid,nodev,relatime,data=ordered)
/sbin/.magisk/block/system on /sbin/.magisk/mirror/system type ext4 (ro,seclabel,relatime,block_validity,discard,delallo
c,barrier,user_xattr)
G8141:/system/etc/permissions #
What am I doing wrong?
Is there maybe a better way meanwhile to enable Daydream on unsupported devices?
I mean, it's a bad joke, Sony makes this great 4k display but doesn't support VR properly. Daydream even starts and is working just to block the view a second later with a big PopUp telling that the device is not compatible.

Categories

Resources