everthing I read refers to load adb driver.
what do you do if you dont have the driver?
adb drivers == nothing found
any attempt with adb
error: device not found
trying to root Audiosonic 7"
every program refers to loading the adb driver no adb driver to load
I've rooted other devices the easy way, someone advises howto
I WOULD like to learn how to root the device, without a know adb driver.
can someone point me to the RIGHT information to read or do please
android 4.0.4
Kernal version :
3.0.36 +
[email protected] #76
Build number :
RK292X_ANDROID4.0.4-SDK-v1.00.00
rk2926sdk-eng 4.0.4 IMM760 20121215.042649 release-keys
There is a way to make your device compatible with adb, even if you can't find driver for it. Below is how I made my old Creative Ziio compatible with adb:
- download and install Google USB driver
- open file android_winusb.inf from the driver's directory. Find section [Google.NTx86] (if you have 32-bit Windows) or [Google.NTamd64] (for 64-bit). At the end of the section, add the following lines:
; Creative Ziio 7"
%SingleAdbInterface% = USB_Install, USB\VID_2350&PID_0102
%CompositeAdbInterface% = USB_Install, USB\VID_2350&PID_0102&MI_01
- find the device in Device Manager and update driver using previously installed USB driver
- add the folowing line to %HOME/.android/adb_usb.ini:
0x2350
- restart adb server
You can get vid&pid from the DeviceManager.
knutson said:
There is a way to make your device compatible with adb, even if you can't find driver for it. Below is how I made my old Creative Ziio compatible with adb:
- download and install Google USB driver
- open file android_winusb.inf from the driver's directory. Find section [Google.NTx86] (if you have 32-bit Windows) or [Google.NTamd64] (for 64-bit). At the end of the section, add the following lines:
; Creative Ziio 7"
%SingleAdbInterface% = USB_Install, USB\VID_2350&PID_0102
%CompositeAdbInterface% = USB_Install, USB\VID_2350&PID_0102&MI_01
- find the device in Device Manager and update driver using previously installed USB driver
- add the folowing line to %HOME/.android/adb_usb.ini:
0x2350
- restart adb server
You can get vid&pid from the DeviceManager.
Click to expand...
Click to collapse
Very informative post. That's what we like to see
well the audiosonic in normal mode shows up as T-07B in recovery it shows as rk2928sdk
added the vid/pid I got from each (different)
unmerged/merged
nomal mode adb devices finds nothing
recovery mode adb devices finds 0123456789ABCDEF RECOVERY
tried adb shell in recovery and got exec '/system/bin/sh' folder or file not found
ok need a break and try attacking this again
singleadbinterface
compositeinterface
best to use both? 1? looking through android_winusb.ini seem like a mixed bag some both, one etc
Yes, both singleadbinterface and compositeinterface are needed. Also do not forget to modify adb_usb.ini.
Also, make sure that USB debugging is enabled on your device, note that this option should be changed only when device is disconnected from USB.
To check that adb is working,try to install something with
adb install ./some_application.apk
knutson said:
Yes, both singleadbinterface and compositeinterface are needed. Also do not forget to modify adb_usb.ini.
Also, make sure that USB debugging is enabled on your device, note that this option should be changed only when device is disconnected from USB.
To check that adb is working,try to install something with
adb install ./some_application.apk
Click to expand...
Click to collapse
so, just to be specific, and not presuming
to root the device I should be in normal mode or recovery? (last 2 roots I did was in normal mode but they where design root methods)
if normal mode, how can you install if the device not found (which device)
device set and confirmed in debugging mode
thanks for the help, even just confirming things for me
just to advised
I tried installing an app
in normal mode error device not found---- waiting on device
in recovery mode seemd to load but got exec '/system/bin/sh' folder or file not found (interestingly enough, got twice)
so either still a driver problem or need to solve the error (god i've been at this for a few days now)
wolfbite.aus said:
just to advised
I tried installing an app
in normal mode error device not found---- waiting on device
in recovery mode seemd to load but got exec '/system/bin/sh' folder or file not found (interestingly enough, got twice)
so either still a driver problem or need to solve the error (god i've been at this for a few days now)
Click to expand...
Click to collapse
Are you mounting /system partition with ADB prior to trying to push files to the partition?
cant mount /system
# adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
is there a sh file somewhere I can push and try???
but adb pull /system gave me bin/busybox
adb pull /data gave me
But each clue you give me gives new ideas (mount got me looking into push/pull
seems I can
adb push so found a su and did adb push /system/bin/su
seemed to work
# adb push su /system/bin/
4576 KB/s (91980 bytes in 0.019s)
then tried
# adb pull /system/
pull: building file list...
pull: /system/bin/busybox -> ./bin/busybox
pull: /system/bin/su -> ./bin/su
2 files pulled. 0 files skipped.
2443 KB/s (1899036 bytes in 0.758s)
adb pull /
pull: building file list...
skipping special file 'rknand_sys_storage'
skipping special file 'ppp'
skipping special file 'network_throughput'
skipping special file 'network_latency'
skipping special file 'cpu_dma_latency'
skipping special file 'rk29-ipp'
skipping special file 'xt_qtaguid'
skipping special file 'galcore'
skipping special file 'binder'
skipping special file 'device-mapper'
skipping special file 'i2c-dev'
skipping special file 'alarm'
skipping special file 'uinput'
skipping special file 'keychord'
skipping special file 'usb_accessory'
skipping special file 'mtp_usb'
skipping special file 'android_adb'
skipping special file 'pmem'
skipping special file 'ion'
skipping special file 'fuse'
skipping special file 'ashmem'
skipping special file 'verifyid'
skipping special file 'vcsa1'
skipping special file 'vcs1'
skipping special file 'vcsa'
skipping special file 'vcs'
skipping special file 'ptmx'
skipping special file 'tty63'
skipping special file 'tty62'
skipping special file 'tty61'
skipping special file 'tty60'
skipping special file 'tty59'
skipping special file 'tty58'
skipping special file 'tty57'
skipping special file 'tty56'
skipping special file 'tty55'
skipping special file 'tty54'
skipping special file 'tty53'
skipping special file 'tty52'
skipping special file 'tty51'
skipping special file 'tty50'
skipping special file 'tty49'
skipping special file 'tty48'
skipping special file 'tty47'
skipping special file 'tty46'
skipping special file 'tty45'
skipping special file 'tty44'
skipping special file 'tty43'
skipping special file 'tty42'
skipping special file 'tty41'
skipping special file 'tty40'
skipping special file 'tty39'
skipping special file 'tty38'
skipping special file 'tty37'
skipping special file 'tty36'
skipping special file 'tty35'
skipping special file 'tty34'
skipping special file 'tty33'
skipping special file 'tty32'
skipping special file 'tty31'
skipping special file 'tty30'
skipping special file 'tty29'
skipping special file 'tty28'
skipping special file 'tty27'
skipping special file 'tty26'
skipping special file 'tty25'
skipping special file 'tty24'
skipping special file 'tty23'
skipping special file 'tty22'
skipping special file 'tty21'
skipping special file 'tty20'
skipping special file 'tty19'
skipping special file 'tty18'
skipping special file 'tty17'
skipping special file 'tty16'
skipping special file 'tty15'
skipping special file 'tty14'
skipping special file 'tty13'
skipping special file 'tty12'
skipping special file 'tty11'
skipping special file 'tty10'
skipping special file 'tty9'
skipping special file 'tty8'
skipping special file 'tty7'
skipping special file 'tty6'
skipping special file 'tty5'
skipping special file 'tty4'
skipping special file 'tty3'
skipping special file 'tty2'
skipping special file 'tty1'
skipping special file 'tty0'
skipping special file 'console'
skipping special file 'tty'
skipping special file 'kmsg'
skipping special file 'urandom'
skipping special file 'random'
skipping special file 'full'
skipping special file 'zero'
skipping special file 'null'
skipping special file 'kmem'
skipping special file 'mem'
skipping special file 'ttyGS3'
skipping special file 'ttyGS2'
skipping special file 'ttyGS1'
skipping special file 'ttyGS0'
skipping special file 'video0'
skipping special file 'rtc0'
skipping special file 'mma8452_daemon'
skipping special file 'ttyS2'
skipping special file 'ttyS0'
skipping special file 'ttyS1'
skipping special file 'property_service'
skipping special file 'event2'
skipping special file 'event0'
skipping special file 'event1'
skipping special file 'fb1'
skipping special file 'fb0'
skipping special file '001'
skipping special file '001'
skipping special file 'timer'
skipping special file 'controlC0'
skipping special file 'pcmC0D0c'
skipping special file 'pcmC0D0p'
skipping special file 'system'
skipping special file 'radio'
skipping special file 'events'
skipping special file 'main'
skipping special file 'mtdblock10'
skipping special file 'mtdblock9'
skipping special file 'mtdblock8'
skipping special file 'mtdblock7'
skipping special file 'mtdblock6'
skipping special file 'mtdblock5'
skipping special file 'mtdblock4'
skipping special file 'mtdblock3'
skipping special file 'mtdblock2'
skipping special file 'mtdblock1'
skipping special file 'mtdblock0'
skipping special file 'loop7'
skipping special file 'loop6'
skipping special file 'loop5'
skipping special file 'loop4'
skipping special file 'loop3'
skipping special file 'loop2'
skipping special file 'loop1'
skipping special file 'loop0'
skipping special file 'mtd10ro'
skipping special file 'mtd10'
skipping special file 'mtd9ro'
skipping special file 'mtd9'
skipping special file 'mtd8ro'
skipping special file 'mtd8'
skipping special file 'mtd7ro'
skipping special file 'mtd7'
skipping special file 'mtd6ro'
skipping special file 'mtd6'
skipping special file 'mtd5ro'
skipping special file 'mtd5'
skipping special file 'mtd4ro'
skipping special file 'mtd4'
skipping special file 'mtd3ro'
skipping special file 'mtd3'
skipping special file 'mtd2ro'
skipping special file 'mtd2'
skipping special file 'mtd1ro'
skipping special file 'mtd1'
skipping special file 'mtd0ro'
skipping special file 'mtd0'
^C
# adb pull /system
pull: building file list...
pull: /system/bin/busybox -> ./bin/busybox
1 file pulled. 0 files skipped.
2736 KB/s (1807056 bytes in 0.644s)
# ls
bin
# ls bin
busybox
adb ls /
still no sh
any ideas?
what about
000081a4 0001e9ff 00000000 rk29xxnand_ko.ko.3.0.8+
000081a4 0001e995 00000000 rk29xxnand_ko.ko.2.6.32.27
# adb ls /
000041ed 00000000 51470583 .
000041ed 00000000 51470583 ..
000041ed 00000000 51470583 cache
000041ed 00000000 51470583 mnt
000081a4 000006f9 00000000 ueventd.rk29board.rc
000081a4 00000f71 00000000 ueventd.rc
000081a4 00000110 00000000 ueventd.goldfish.rc
000041ed 00000000 51470585 tmp
000041ed 00000000 00000000 system
000041ed 00000000 51470583 sys
000041e8 00000000 00000000 sbin
000081a4 0001e9ff 00000000 rk29xxnand_ko.ko.3.0.8+
000081a4 0001e995 00000000 rk29xxnand_ko.ko.2.6.32.27
000041ed 00000000 00000000 res
0000416d 00000000 00000000 proc
000081e8 00000626 00000000 init.rc
000081e8 000191ac 00000000 init
000041ed 00000000 00000000 etc
000081a4 00000908 00000000 default.prop
000041ed 00000000 51470d4e data
000081e8 0003abe4 00000000 charger
000041c0 00000000 4fd5637e root
000041ed 000009b0 51470585 dev
# adb ls /sys
000041ed 00000000 51470583 .
000041ed 00000000 51470583 ..
000041ed 00000000 514718d3 fs
000041ed 00000000 51470583 devices
000041ed 00000000 514718d3 dev
000041ed 00000000 514718d3 bus
000041ed 00000000 51470583 class
000041ed 00000000 514718d3 firmware
000041ed 00000000 514718d3 kernel
000041ed 00000000 514718d3 power
000041ed 00000000 514718d3 module
000041ed 00000000 51470583 block
000041ed 00000000 514718d3 android_gsensor
000041ed 00000000 514718d3 sd-sdio
# adb ls /sbin
000041e8 00000000 00000000 .
000041ed 00000000 51470583 ..
0000a1ff 00000007 00000000 ueventd
000081e8 0001dd74 00000000 resize2fs
000081e8 00046330 00000000 recovery
000081e8 0002da68 00000000 mke2fs
000081e8 00012700 00000000 mkdosfs
000081e8 0004345c 00000000 e2fsck
000081e8 00022d40 00000000 adbd
.s
tried copying over the sh from second android
pushed to 1st android
# adb ls /system/bin/
000041ed 00000000 514722b2 .
000041ed 00000000 00000000 ..
000081ff 00025744 514721d6 sh
000081b6 0001674c 4ffd3b72 su
000081ed 001b92d0 00000000 busybox
# adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
still fails
wonder if file permission thing, if so howto chage without shell capability
# adb root
adbd is already running as root
wolfbite.aus said:
tried copying over the sh from second android
pushed to 1st android
# adb ls /system/bin/
000041ed 00000000 514722b2 .
000041ed 00000000 00000000 ..
000081ff 00025744 514721d6 sh
000081b6 0001674c 4ffd3b72 su
000081ed 001b92d0 00000000 busybox
# adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
still fails
wonder if file permission thing, if so howto chage without shell capability
# adb root
adbd is already running as root
Click to expand...
Click to collapse
As for the sh script, there isn't one that I know of. Sorry.
You must also apply file permissions with chmod for each file that you push to the device. Most file permissions are going to be 0644 or 0755.
All the Linux commands you are using are actually symlinked to busybox in your /system/bin folder. I would recommend updating your busybox installation while you are in the process of rooting with this method.
You should also update the SuperUser.apk in /system/app since you updated/replaced the su binary in /system/bin. A wise precautionary measure is to also install a copy of the su binary in /system/xbin.
the adb command seems to work push, pull, /
adb shell still gives me
- exec '/system/bin/sh' failed: No such file or directory (2) -
tried pushing busybox (succesful)
but getting same error with shell
how do you apply chmod without shell?
can you break down what the hexidecimal values mean (tried searching)
# adb ls /system/bin/
000041ed 00000000 514722b2 .
000041ed 00000000 00000000 ..
000081ff 00025744 514721d6 sh
000081b6 0001674c 4ffd3b72 su
000081ed 001b92d0 00000000 busybox
tried setting file permissions befor pushing, didnt work
tried upgrading img but got signature verification errors no matter what I through at it
(not worried about bricking this one, slight kid damaged screen and another to use for final results
theres probably mor i can do with adb but its learn as we go
wolfbite.aus said:
the adb command seems to work push, pull, /
adb shell still gives me
- exec '/system/bin/sh' failed: No such file or directory (2) -
tried pushing busybox (succesful)
but getting same error with shell
how do you apply chmod without shell?
can you break down what the hexidecimal values mean (tried searching)
# adb ls /system/bin/
000041ed 00000000 514722b2 .
000041ed 00000000 00000000 ..
000081ff 00025744 514721d6 sh
000081b6 0001674c 4ffd3b72 su
000081ed 001b92d0 00000000 busybox
tried setting file permissions befor pushing, didnt work
tried upgrading img but got signature verification errors no matter what I through at it
(not worried about bricking this one, slight kid damaged screen and another to use for final results
theres probably mor i can do with adb but its learn as we go
Click to expand...
Click to collapse
Permissions must be set after pushing to the device.
guess thats it then
if I cant get a shell, then nothing else to do
[Failed] ROOT without adb driver?
close thread
useful post
but afraid of the codes
What i Did
I took the google usb driver, then downloaded the (supposed) usb drivers from my manufactuer. The maker of my phone, totally screwed up their usb drivers, they didn't have the right vid/pid 's for it( checked the drivers in a linux distro) . Opened the manufactuer's driver, changed the vid/pid's to what was supposed to be there, in it, and the google driver too. Opened the device manager(windows) and ran the "have disk" option, to get the right recognition, and all of the (ADB interface, Bootloader Interface, Composite..) intalled correctly.SDK, eclipse, QtAdb, run great, the only problem is not recognizing what bootloader is in phone( it's locked). I think you're doing a little too much, for your problem.
wolfbite.aus said:
guess thats it then
if I cant get a shell, then nothing else to do
Click to expand...
Click to collapse
hang in there brah i rooted my 2 days ago. i got the a/sonic 10.1 rk2928 chip
how i did it? hrmm i downloaded the rk29 root tool its some where on xda forums. find it.! once i plugged the usb cable into my tablet from pc all drivers installed only one didn't that one t-22b i think. so i used my samsung s2 drivers that was already installed. and walla! adb started working the rest i left for the root kit runme.bat hope that helped good luck!
Related
Hi xda-developers.
I've a Galaxy S Player 5.0 (YP-G70) and I have the following situation:
The device uses MMC partition table, and the internal storage partitions are listed as /dev/block/mmcblk0p*, external SD -> /dev/block/mmcblk1p*. I got my partition table deleted by accident, so my device doesn't boot.
I tried to repartition with Odin using the right PIT file but it didn't work. So I compiled my own kernel with stock initrd, activating unsecure mode, adb and busybox in order to manually repartition my internal storage. Now it boots into recovery mode and I can do some things with adb (push, pull), but when I try 'adb shell', I get the following error:
Code:
- exec '/system/bin/sh' failed: No such file or directory (2) -
Obiously, I put the file in /system/bin/sh in the ramdisk with +x permissions. Even I can pull the file doing 'adb pull /system/bin/sh'. I compiled a modified adbd so it can use /sbin/sh and got the same result.
Code:
- exec '/sbin/sh' failed: No such file or directory (2) -
So for now I can't get into shell to manually repartition my device.
I tried other things:
Code:
adb pull /dev/block
pull: building file list...
skipping special file 'loop7'
skipping special file 'loop6'
skipping special file 'loop5'
skipping special file 'loop4'
skipping special file 'loop3'
skipping special file 'loop2'
skipping special file 'loop1'
skipping special file 'loop0'
skipping special file 'ram15'
skipping special file 'ram14'
skipping special file 'ram13'
skipping special file 'ram12'
skipping special file 'ram11'
skipping special file 'ram10'
skipping special file 'ram9'
skipping special file 'ram8'
skipping special file 'ram7'
skipping special file 'ram6'
skipping special file 'ram5'
skipping special file 'ram4'
skipping special file 'ram3'
skipping special file 'ram2'
skipping special file 'ram1'
skipping special file 'ram0'
skipping special file 'mmcblk0'
By reading the output I know it detects internal storage but it doesn't have any partitions, only mmcblk0.
Also, I got a full dd dump from another device and tried to push it via adb, it didn't work.
I'm running out of ideas. Maybe someone can help me to create a working initrd in which I can get into console or has another idea to rebuild my partition table.
Thanks in advance!
Hey guys I have had an android phone since the first of their kind came out and am well knowledgeable of the software and all the good stuff that comes packed in an android device. Currently I own a SONY Xperia ION (which I do not want to root for certain reasons) and a SONY Walkman series F PMP (NWZ-F806). The Walkman mp3 player runs on android version 4.0.4 and kernel version 2.6.39.4 (don't know if this information is actually necessary.
Now I do not have enough experience with rooting but I have seen it done with other devices. Just wondering if a root for the Walkman exists. I am aware that the SONY Walkman series Z is able to accept a root similar to the process found when rooting the SONY Tablet S. Though I do not know if this same exploit is applicable to the F version.
Any help would be great. Personally I rather root the Walkman than the ION, reasons leaning more towards warranty voiding. Thanks.
Looking for this information as well!
I wish i was brave enough to try the walkman Z root to see if it's the same, but for a $$$ device i'm not that brave.
Anyone has dump for nwz f800 series?
Anyone can provide me the system files of nwz 804/805/806 ?
Just copy the whole system folder and zip it and upload it somewhere on internet.
Really grateful
zhuhang said:
Anyone can provide me the system files of nwz 804/805/806 ?
Just copy the whole system folder and zip it and upload it somewhere on internet.
Really grateful
Click to expand...
Click to collapse
hope this thread isnt dead yet...
here is the dump from recently updated my nw-f708, jp model, 64gb. build number is 1.10.0000.
im not sure its same as global model but ill upload it anyway.
http://www.mediafire.com/download.php?zasur3029343vmc
http://www.mediafire.com/download.php?fokyvqeanwccorc
utubo_sk8 said:
hope this thread isnt dead yet...
here is the dump from recently updated my nw-f708, jp model, 64gb. build number is 1.10.0000.
im not sure its same as global model but ill upload it anyway.
http://www.mediafire.com/download.php?zasur3029343vmc
http://www.mediafire.com/download.php?fokyvqeanwccorc
Click to expand...
Click to collapse
Thanks anyway! Will check it out.
---------- Post added at 06:23 PM ---------- Previous post was at 06:00 PM ----------
utubo_sk8 said:
hope this thread isnt dead yet...
here is the dump from recently updated my nw-f708, jp model, 64gb. build number is 1.10.0000.
im not sure its same as global model but ill upload it anyway.
http://www.mediafire.com/download.php?zasur3029343vmc
http://www.mediafire.com/download.php?fokyvqeanwccorc
Click to expand...
Click to collapse
Yes ,indeed it is almost the same. THANKS FOR YOUR CONTRIBUTION!
U uploaded it yourself?
utubo_sk8 said:
hope this thread isnt dead yet...
here is the dump from recently updated my nw-f708, jp model, 64gb. build number is 1.10.0000.
im not sure its same as global model but ill upload it anyway.
http://www.mediafire.com/download.php?zasur3029343vmc
http://www.mediafire.com/download.php?fokyvqeanwccorc
Click to expand...
Click to collapse
Can u also give me your init.rc file located on root of the device?
zhuhang said:
Thanks anyway! Will check it out.
---------- Post added at 06:23 PM ---------- Previous post was at 06:00 PM ----------
Yes ,indeed it is almost the same. THANKS FOR YOUR CONTRIBUTION!
U uploaded it yourself?
Click to expand...
Click to collapse
yes, i uploaded it.
how to pull that init.rc out? tried adb pull init.rc and says permission denied
utubo_sk8 said:
yes, i uploaded it.
how to pull that init.rc out? tried adb pull init.rc and says permission denied
Click to expand...
Click to collapse
How about using file manager on phone and copy it to sdcard manually?
zhuhang said:
How about using file manager on phone and copy it to sdcard manually?
Click to expand...
Click to collapse
didnt work... permission was "-rwxr-x---".
i saw something on 2ch that since its updated to 1.10.0000 the bin4ry's root method won't work anymore, but look like it was working before the update.
utubo_sk8 said:
didnt work... permission was "-rwxr-x---".
i saw something on 2ch that since its updated to 1.10.0000 the bin4ry's root method won't work anymore, but look like it was working before the update.
Click to expand...
Click to collapse
I see, u have the init.rc for previous version?
zhuhang said:
I see, u have the init.rc for previous version?
Click to expand...
Click to collapse
erm, nope.
utubo_sk8 said:
erm, nope.
Click to expand...
Click to collapse
Its ok. I dont need it already. Thanks for the system upload!
zhuhang said:
Its ok. I dont need it already. Thanks for the system upload!
Click to expand...
Click to collapse
yea no problem.
one thing i found out, i could just extract the firmware from the walkman updater with archiver LOL and it contains zip file and theres one file called hidden.img there.
not sure if it contains something useful for rooting but maybe worth checking.
walkman 1.10.0000 updater
http://walkman.update.sony.net/fw/pc/F800/NW-F800_V1_10_0000.exe
hidden.img inside of NW-WM-FW.zip
http://www.mediafire.com/?0rtgy5cwnja6dfr
utubo_sk8 said:
yea no problem.
one thing i found out, i could just extract the firmware from the walkman updater with archiver LOL and it contains zip file and theres one file called hidden.img there.
not sure if it contains something useful for rooting but maybe worth checking.
walkman 1.10.0000 updater
http://walkman.update.sony.net/fw/pc/F800/NW-F800_V1_10_0000.exe
hidden.img inside of NW-WM-FW.zip
http://www.mediafire.com/?0rtgy5cwnja6dfr
Click to expand...
Click to collapse
English version of update is also available right now.
So english dump can be extracted easily.
Just bought this device and waiting for a root solution.
p.s. on 1.10
Anyone able to provide /dev/ folder?
zhuhang said:
Anyone able to provide /dev/ folder?
Click to expand...
Click to collapse
Code:
pull: building file list...
skipping special file 'mgscsi'
skipping special file 'mgscc'
skipping special file 'icx_diag'
skipping special file 'radio0'
skipping special file 'tegra_dc_0'
skipping special file 'ppp'
skipping special file 'tegra_dc_ctrl'
skipping special file 'nvhost-ctrl'
skipping special file 'nvhost-dsi'
skipping special file 'nvhost-mpe'
skipping special file 'nvhost-vi'
skipping special file 'nvhost-isp'
skipping special file 'nvhost-gr2d'
skipping special file 'nvhost-gr3d'
skipping special file 'nvhost-display'
skipping special file 'wmport'
skipping special file 'ptmx'
skipping special file 'console'
skipping special file 'tty'
skipping special file 'kmsg'
skipping special file 'urandom'
skipping special file 'random'
skipping special file 'full'
skipping special file 'zero'
skipping special file 'port'
skipping special file 'null'
skipping special file 'mem'
skipping special file 'tegra-crypto'
skipping special file 'cpu_freq_max'
skipping special file 'cpu_freq_min'
skipping special file 'max_online_cpus'
skipping special file 'min_online_cpus'
skipping special file 'network_throughput'
skipping special file 'network_latency'
skipping special file 'cpu_dma_latency'
skipping special file 'xt_qtaguid'
skipping special file 'binder'
skipping special file 'device-mapper'
skipping special file 'tegra_mediaserver'
skipping special file 'tegra_avp'
skipping special file 'tegra_rpc'
skipping special file 'tegra_sema'
skipping special file 'alarm'
skipping special file 'uinput'
skipping special file 'keychord'
skipping special file 'usb_accessory'
skipping special file 'mtp_usb'
skipping special file 'android_adb'
skipping special file 'tun'
skipping special file 'timerirq'
skipping special file 'fuse'
skipping special file 'ashmem'
skipping special file 'timerinfo'
skipping special file 'rfkill'
skipping special file 'vga_arbiter'
skipping special file 'ttyS3'
skipping special file 'ttyS2'
skipping special file 'knvmap'
skipping special file 'nvmap'
skipping special file 'ttyGS3'
skipping special file 'ttyGS2'
skipping special file 'ttyGS1'
skipping special file 'ttyGS0'
skipping special file 'watchdog'
skipping special file 'ttyS1'
skipping special file 'ttyHS2'
skipping special file 'ttyHS1'
skipping special file 'ttyS0'
skipping special file 'i2c-4'
skipping special file 'rtc0'
skipping special file 'i2c-3'
skipping special file 'i2c-2'
skipping special file 'i2c-1'
skipping special file 'stuid'
skipping special file 'i2c-0'
skipping special file '0'
skipping special file 'wpa_wlan0'
skipping special file 'vold'
skipping special file 'dbus'
skipping special file 'keystore'
skipping special file 'installd'
skipping special file 'netd'
skipping special file 'dnsproxyd'
skipping special file 'rild'
skipping special file 'rild-debug'
skipping special file 'zygote'
skipping special file 'property_service'
skipping special file 'event3'
skipping special file 'event2'
skipping special file 'event0'
skipping special file 'event1'
skipping special file 'timer'
skipping special file 'controlC0'
skipping special file 'pcmC0D0c'
skipping special file 'pcmC0D0p'
skipping special file 'pcmC0D1c'
skipping special file 'pcmC0D1p'
skipping special file 'loop7'
skipping special file 'loop6'
skipping special file 'loop5'
skipping special file 'loop4'
skipping special file 'loop3'
skipping special file 'loop2'
skipping special file 'loop1'
skipping special file 'loop0'
skipping special file 'mmcblk0p12'
skipping special file 'mmcblk0p11'
skipping special file 'mmcblk0p10'
skipping special file 'mmcblk0p9'
skipping special file 'mmcblk0p8'
skipping special file 'mmcblk0p7'
skipping special file 'mmcblk0p6'
skipping special file 'mmcblk0p5'
skipping special file 'mmcblk0p4'
skipping special file 'mmcblk0p3'
skipping special file 'mmcblk0p2'
skipping special file 'mmcblk0p1'
skipping special file 'mmcblk0'
skipping special file 'mmcblk0p12'
skipping special file 'mmcblk0p11'
skipping special file 'mmcblk0p10'
skipping special file 'mmcblk0p9'
skipping special file 'mmcblk0p8'
skipping special file 'mmcblk0p7'
skipping special file 'mmcblk0p6'
skipping special file 'mmcblk0p5'
skipping special file 'mmcblk0p4'
skipping special file 'mmcblk0p3'
skipping special file 'mmcblk0p2'
skipping special file 'mmcblk0p1'
skipping special file 'mmcblk0'
skipping special file 'SDC'
skipping special file 'MAN'
skipping special file 'ZZ3'
skipping special file 'LOG'
skipping special file 'DAP'
skipping special file 'ZZN'
skipping special file 'BLF'
skipping special file 'USP'
skipping special file 'MSC'
skipping special file 'CAC'
skipping special file 'ZZ1'
skipping special file 'ZZ0'
skipping special file 'p12'
skipping special file 'p11'
skipping special file 'p10'
skipping special file 'p9'
skipping special file 'p8'
skipping special file 'p7'
skipping special file 'p6'
skipping special file 'p5'
skipping special file 'p4'
skipping special file 'p3'
skipping special file 'p2'
skipping special file 'p1'
skipping special file '179:12'
skipping special file '179:11'
skipping special file '179:10'
skipping special file '179:9'
skipping special file '179:8'
skipping special file '179:7'
skipping special file '179:6'
skipping special file '179:5'
skipping special file '179:4'
skipping special file '179:3'
skipping special file '179:2'
skipping special file '179:1'
skipping special file '179:0'
skipping special file 'system'
skipping special file 'radio'
skipping special file 'events'
skipping special file 'main'
skipping special file 'fb0'
skipping special file '089'
skipping special file '088'
skipping special file '087'
skipping special file '086'
skipping special file '085'
skipping special file '084'
skipping special file '083'
skipping special file '082'
skipping special file '081'
skipping special file '080'
skipping special file '079'
skipping special file '078'
skipping special file '077'
skipping special file '076'
skipping special file '075'
skipping special file '074'
skipping special file '073'
skipping special file '072'
skipping special file '071'
skipping special file '070'
skipping special file '069'
skipping special file '068'
skipping special file '067'
skipping special file '066'
skipping special file '066'
skipping special file '065'
skipping special file '064'
skipping special file '063'
skipping special file '062'
skipping special file '061'
skipping special file '060'
skipping special file '059'
skipping special file '058'
skipping special file '057'
skipping special file '056'
skipping special file '055'
skipping special file '054'
skipping special file '053'
skipping special file '052'
skipping special file '051'
skipping special file '050'
skipping special file '049'
skipping special file '048'
skipping special file '047'
skipping special file '046'
skipping special file '045'
skipping special file '044'
skipping special file '043'
skipping special file '042'
skipping special file '041'
skipping special file '040'
skipping special file '039'
skipping special file '038'
skipping special file '037'
skipping special file '036'
skipping special file '035'
skipping special file '034'
skipping special file '033'
skipping special file '032'
skipping special file '031'
skipping special file '030'
skipping special file '029'
skipping special file '028'
skipping special file '027'
skipping special file '026'
skipping special file '025'
skipping special file '024'
skipping special file '023'
skipping special file '022'
skipping special file '021'
skipping special file '020'
skipping special file '019'
skipping special file '018'
skipping special file '017'
skipping special file '016'
skipping special file '015'
skipping special file '014'
skipping special file '013'
skipping special file '012'
skipping special file '011'
skipping special file '010'
skipping special file '009'
skipping special file '008'
skipping special file '007'
skipping special file '006'
skipping special file '005'
skipping special file '004'
skipping special file '003'
skipping special file '002'
skipping special file '001'
skipping special file '000'
pull: /dev/cpuctl/bg_non_interactive/tasks -> ./cpuctl/bg_non_interactive/tasks
pull: /dev/cpuctl/bg_non_interactive/cgroup.procs -> ./cpuctl/bg_non_interactive/cgroup.procs
pull: /dev/cpuctl/bg_non_interactive/notify_on_release -> ./cpuctl/bg_non_interactive/notify_on_release
pull: /dev/cpuctl/bg_non_interactive/cgroup.event_control -> ./cpuctl/bg_non_interactive/cgroup.event_control
failed to copy '/dev/cpuctl/bg_non_interactive/cgroup.event_control' to './cpuctl/bg_non_interactive/cgroup.event_control': Permission denied
pull: /dev/cpuctl/bg_non_interactive/cgroup.clone_children -> ./cpuctl/bg_non_interactive/cgroup.clone_children
pull: /dev/cpuctl/bg_non_interactive/cpu.shares -> ./cpuctl/bg_non_interactive/cpu.shares
pull: /dev/cpuctl/bg_non_interactive/cpu.rt_runtime_us -> ./cpuctl/bg_non_interactive/cpu.rt_runtime_us
pull: /dev/cpuctl/bg_non_interactive/cpu.rt_period_us -> ./cpuctl/bg_non_interactive/cpu.rt_period_us
pull: /dev/cpuctl/fg_boost/tasks -> ./cpuctl/fg_boost/tasks
pull: /dev/cpuctl/fg_boost/cgroup.procs -> ./cpuctl/fg_boost/cgroup.procspull: /dev/cpuctl/fg_boost/notify_on_release -> ./cpuctl/fg_boost/notify_on_release
pull: /dev/cpuctl/fg_boost/cgroup.event_control -> ./cpuctl/fg_boost/cgroup.event_control
failed to copy '/dev/cpuctl/fg_boost/cgroup.event_control' to './cpuctl/fg_boost/cgroup.event_control': Permission denied
pull: /dev/cpuctl/fg_boost/cgroup.clone_children -> ./cpuctl/fg_boost/cgroup.clone_children
pull: /dev/cpuctl/fg_boost/cpu.shares -> ./cpuctl/fg_boost/cpu.shares
pull: /dev/cpuctl/fg_boost/cpu.rt_runtime_us -> ./cpuctl/fg_boost/cpu.rt_runtime_us
pull: /dev/cpuctl/fg_boost/cpu.rt_period_us -> ./cpuctl/fg_boost/cpu.rt_period_us
pull: /dev/cpuctl/tasks -> ./cpuctl/tasks
pull: /dev/cpuctl/cgroup.procs -> ./cpuctl/cgroup.procs
pull: /dev/cpuctl/notify_on_release -> ./cpuctl/notify_on_release
pull: /dev/cpuctl/cgroup.event_control -> ./cpuctl/cgroup.event_control
failed to copy '/dev/cpuctl/cgroup.event_control' to './cpuctl/cgroup.event_control': Permission denied
pull: /dev/cpuctl/cgroup.clone_children -> ./cpuctl/cgroup.clone_children
pull: /dev/cpuctl/release_agent -> ./cpuctl/release_agent
pull: /dev/cpuctl/cpu.shares -> ./cpuctl/cpu.shares
pull: /dev/cpuctl/cpu.rt_runtime_us -> ./cpuctl/cpu.rt_runtime_us
pull: /dev/cpuctl/cpu.rt_period_us -> ./cpuctl/cpu.rt_period_us
pull: /dev/.coldboot_done -> ./.coldboot_done
failed to copy '/dev/.coldboot_done' to './.coldboot_done': Permission denied
26 files pulled. 0 files skipped.
4 KB/s (3279 bytes in 0.709s)
Code:
[email protected]:/dev $ ls -l
ls -l
crw-rw-r-- system radio 10, 52 2012-12-17 20:24 alarm
crw-rw---- adb adb 10, 56 2012-12-17 20:24 android_adb
crw-rw-rw- root root 10, 58 2012-12-17 20:24 ashmem
crw-rw-rw- root root 10, 47 2012-12-17 20:24 binder
drwxr-xr-x root root 2012-12-17 20:24 block
crw------- root root 5, 1 2012-12-17 20:24 console
crw------- root root 10, 41 2012-12-17 20:24 cpu_dma_latency
crw------- root root 10, 35 2012-12-17 20:24 cpu_freq_max
crw------- root root 10, 36 2012-12-17 20:24 cpu_freq_min
drwxr-xr-x system system 2012-12-17 20:24 cpuctl
crw------- root root 10, 236 2012-12-17 20:24 device-mapper
crw-rw-rw- root root 1, 7 2012-12-17 20:24 full
crw------- root root 10, 229 2012-12-17 20:24 fuse
drwxr-xr-x root root 2012-12-17 20:24 graphics
crw------- root root 89, 0 2012-12-17 20:24 i2c-0
crw------- root root 89, 1 2012-12-17 20:24 i2c-1
crw------- root root 89, 2 2012-12-17 20:24 i2c-2
crw------- root root 89, 3 2012-12-17 20:24 i2c-3
crw------- root root 89, 4 2012-12-17 20:24 i2c-4
crw-rw---- system system 10, 32 2012-12-17 20:24 icx_diag
drwxr-xr-x root root 2012-12-17 20:24 icx_nvp
drwxr-xr-x root root 2012-12-17 20:24 input
crw------- root root 10, 53 2012-12-17 20:24 keychord
crw------- root root 1, 11 2012-12-17 20:24 kmsg
crw-rw---- system system 10, 60 2012-12-17 20:26 knvmap
drwxr-xr-x root root 2012-12-17 20:24 log
crw------- root root 10, 37 2012-12-17 20:24 max_online_cpus
crw------- root root 1, 1 2012-12-17 20:24 mem
crw-rw---- root icx_mg 10, 244 2012-12-17 20:24 mgscc
crw-rw---- root icx_mg 10, 245 2012-12-17 20:24 mgscsi
crw------- root root 10, 38 2012-12-17 20:24 min_online_cpus
crw-rw---- root mtp 10, 55 2012-12-17 20:24 mtp_usb
crw------- root root 10, 40 2012-12-17 20:24 network_latency
crw------- root root 10, 39 2012-12-17 20:24 network_throughput
crw-rw-rw- root root 1, 3 2012-12-17 20:24 null
crw-rw-rw- root root 251, 7 2012-12-17 20:24 nvhost-ctrl
crw-rw-rw- root root 251, 0 2012-12-17 20:24 nvhost-display
crw-rw-rw- root root 251, 6 2012-12-17 20:24 nvhost-dsi
crw-rw-rw- root root 251, 2 2012-12-17 20:24 nvhost-gr2d
crw-rw-rw- root root 251, 1 2012-12-17 20:24 nvhost-gr3d
crw-rw-rw- root root 251, 3 2012-12-17 20:24 nvhost-isp
crw-rw-rw- root root 251, 5 2012-12-17 20:24 nvhost-mpe
crw-rw-rw- root root 251, 4 2012-12-17 20:24 nvhost-vi
crw-rw-rw- system system 10, 61 2012-12-17 20:24 nvmap
crw------- root root 1, 4 2012-12-17 20:24 port
crw-rw---- radio vpn 108, 0 2012-12-17 20:24 ppp
crw-rw-rw- root root 5, 2 2012-12-17 20:34 ptmx
drwxr-xr-x root root 1970-01-01 09:00 pts
crw-rw---- system fm 81, 0 2012-12-17 20:24 radio0
crw-rw-rw- root root 1, 8 2012-12-17 20:24 random
crw------- root root 10, 62 2012-12-17 20:24 rfkill
crw-r--r-- root system 254, 0 2012-12-17 20:24 rtc0
drwxr-xr-x root root 2012-12-17 20:24 snd
drwxr-xr-x root root 2012-12-17 20:24 socket
cr--r--r-- root root 10, 33 2012-12-17 20:24 stuid
crw------- root root 10, 34 2012-12-17 20:24 tegra-crypto
crw-rw---- media wmmedia 10, 49 2012-12-17 20:24 tegra_avp
crw-rw---- system system 250, 1 2012-12-17 20:24 tegra_dc_0
crw-rw---- system system 250, 0 2012-12-17 20:24 tegra_dc_ctrl
crw-rw---- media wmmedia 10, 48 2012-12-17 20:24 tegra_mediaserver
crw-rw---- media wmmedia 10, 50 2012-12-17 20:24 tegra_rpc
crw-rw---- media wmmedia 10, 51 2012-12-17 20:24 tegra_sema
cr--r--r-- system system 10, 59 2012-12-17 20:24 timerinfo
crw-r----- system system 10, 57 2012-12-17 20:24 timerirq
crw-rw-rw- root root 5, 0 2012-12-17 20:24 tty
crw------- root root 248, 0 2012-12-17 20:24 ttyGS0
crw------- root root 248, 1 2012-12-17 20:24 ttyGS1
crw------- root root 248, 2 2012-12-17 20:24 ttyGS2
crw------- root root 248, 3 2012-12-17 20:24 ttyGS3
crw------- system system 249, 1 2012-12-17 20:24 ttyHS1
crw-rw---- bluetooth bluetooth 249, 2 2012-12-17 20:24 ttyHS2
crw------- root root 4, 64 2012-12-17 20:24 ttyS0
crw------- system system 4, 65 2012-12-17 20:24 ttyS1
crw------- root root 4, 66 2012-12-17 20:24 ttyS2
crw------- root root 4, 67 2012-12-17 20:24 ttyS3
crw-rw---- system vpn 10, 200 2012-12-17 20:24 tun
crw-rw---- system bluetooth 10, 223 2012-12-17 20:24 uinput
crw-rw-rw- root root 1, 9 2012-12-17 20:24 urandom
crw-rw---- root usb 10, 54 2012-12-17 20:24 usb_accessory
crw------- root root 10, 63 2012-12-17 20:24 vga_arbiter
crw------- root root 10, 130 2012-12-17 20:24 watchdog
crw------- system system 252, 0 2012-12-17 20:24 wmport
crw-r--r-- root root 10, 42 2012-12-17 20:24 xt_qtaguid
crw-rw-rw- root root 1, 5 2012-12-17 20:24 zero
probably not useful... i cant pull the files out.
EDIT: tar worked. got a tons of dummy files.
utubo_sk8 said:
Code:
pull: building file list...
skipping special file 'mgscsi'
skipping special file 'mgscc'
skipping special file 'icx_diag'
skipping special file 'radio0'
skipping special file 'tegra_dc_0'
skipping special file 'ppp'
skipping special file 'tegra_dc_ctrl'
skipping special file 'nvhost-ctrl'
skipping special file 'nvhost-dsi'
skipping special file 'nvhost-mpe'
skipping special file 'nvhost-vi'
skipping special file 'nvhost-isp'
skipping special file 'nvhost-gr2d'
skipping special file 'nvhost-gr3d'
skipping special file 'nvhost-display'
skipping special file 'wmport'
skipping special file 'ptmx'
skipping special file 'console'
skipping special file 'tty'
skipping special file 'kmsg'
skipping special file 'urandom'
skipping special file 'random'
skipping special file 'full'
skipping special file 'zero'
skipping special file 'port'
skipping special file 'null'
skipping special file 'mem'
skipping special file 'tegra-crypto'
skipping special file 'cpu_freq_max'
skipping special file 'cpu_freq_min'
skipping special file 'max_online_cpus'
skipping special file 'min_online_cpus'
skipping special file 'network_throughput'
skipping special file 'network_latency'
skipping special file 'cpu_dma_latency'
skipping special file 'xt_qtaguid'
skipping special file 'binder'
skipping special file 'device-mapper'
skipping special file 'tegra_mediaserver'
skipping special file 'tegra_avp'
skipping special file 'tegra_rpc'
skipping special file 'tegra_sema'
skipping special file 'alarm'
skipping special file 'uinput'
skipping special file 'keychord'
skipping special file 'usb_accessory'
skipping special file 'mtp_usb'
skipping special file 'android_adb'
skipping special file 'tun'
skipping special file 'timerirq'
skipping special file 'fuse'
skipping special file 'ashmem'
skipping special file 'timerinfo'
skipping special file 'rfkill'
skipping special file 'vga_arbiter'
skipping special file 'ttyS3'
skipping special file 'ttyS2'
skipping special file 'knvmap'
skipping special file 'nvmap'
skipping special file 'ttyGS3'
skipping special file 'ttyGS2'
skipping special file 'ttyGS1'
skipping special file 'ttyGS0'
skipping special file 'watchdog'
skipping special file 'ttyS1'
skipping special file 'ttyHS2'
skipping special file 'ttyHS1'
skipping special file 'ttyS0'
skipping special file 'i2c-4'
skipping special file 'rtc0'
skipping special file 'i2c-3'
skipping special file 'i2c-2'
skipping special file 'i2c-1'
skipping special file 'stuid'
skipping special file 'i2c-0'
skipping special file '0'
skipping special file 'wpa_wlan0'
skipping special file 'vold'
skipping special file 'dbus'
skipping special file 'keystore'
skipping special file 'installd'
skipping special file 'netd'
skipping special file 'dnsproxyd'
skipping special file 'rild'
skipping special file 'rild-debug'
skipping special file 'zygote'
skipping special file 'property_service'
skipping special file 'event3'
skipping special file 'event2'
skipping special file 'event0'
skipping special file 'event1'
skipping special file 'timer'
skipping special file 'controlC0'
skipping special file 'pcmC0D0c'
skipping special file 'pcmC0D0p'
skipping special file 'pcmC0D1c'
skipping special file 'pcmC0D1p'
skipping special file 'loop7'
skipping special file 'loop6'
skipping special file 'loop5'
skipping special file 'loop4'
skipping special file 'loop3'
skipping special file 'loop2'
skipping special file 'loop1'
skipping special file 'loop0'
skipping special file 'mmcblk0p12'
skipping special file 'mmcblk0p11'
skipping special file 'mmcblk0p10'
skipping special file 'mmcblk0p9'
skipping special file 'mmcblk0p8'
skipping special file 'mmcblk0p7'
skipping special file 'mmcblk0p6'
skipping special file 'mmcblk0p5'
skipping special file 'mmcblk0p4'
skipping special file 'mmcblk0p3'
skipping special file 'mmcblk0p2'
skipping special file 'mmcblk0p1'
skipping special file 'mmcblk0'
skipping special file 'mmcblk0p12'
skipping special file 'mmcblk0p11'
skipping special file 'mmcblk0p10'
skipping special file 'mmcblk0p9'
skipping special file 'mmcblk0p8'
skipping special file 'mmcblk0p7'
skipping special file 'mmcblk0p6'
skipping special file 'mmcblk0p5'
skipping special file 'mmcblk0p4'
skipping special file 'mmcblk0p3'
skipping special file 'mmcblk0p2'
skipping special file 'mmcblk0p1'
skipping special file 'mmcblk0'
skipping special file 'SDC'
skipping special file 'MAN'
skipping special file 'ZZ3'
skipping special file 'LOG'
skipping special file 'DAP'
skipping special file 'ZZN'
skipping special file 'BLF'
skipping special file 'USP'
skipping special file 'MSC'
skipping special file 'CAC'
skipping special file 'ZZ1'
skipping special file 'ZZ0'
skipping special file 'p12'
skipping special file 'p11'
skipping special file 'p10'
skipping special file 'p9'
skipping special file 'p8'
skipping special file 'p7'
skipping special file 'p6'
skipping special file 'p5'
skipping special file 'p4'
skipping special file 'p3'
skipping special file 'p2'
skipping special file 'p1'
skipping special file '179:12'
skipping special file '179:11'
skipping special file '179:10'
skipping special file '179:9'
skipping special file '179:8'
skipping special file '179:7'
skipping special file '179:6'
skipping special file '179:5'
skipping special file '179:4'
skipping special file '179:3'
skipping special file '179:2'
skipping special file '179:1'
skipping special file '179:0'
skipping special file 'system'
skipping special file 'radio'
skipping special file 'events'
skipping special file 'main'
skipping special file 'fb0'
skipping special file '089'
skipping special file '088'
skipping special file '087'
skipping special file '086'
skipping special file '085'
skipping special file '084'
skipping special file '083'
skipping special file '082'
skipping special file '081'
skipping special file '080'
skipping special file '079'
skipping special file '078'
skipping special file '077'
skipping special file '076'
skipping special file '075'
skipping special file '074'
skipping special file '073'
skipping special file '072'
skipping special file '071'
skipping special file '070'
skipping special file '069'
skipping special file '068'
skipping special file '067'
skipping special file '066'
skipping special file '066'
skipping special file '065'
skipping special file '064'
skipping special file '063'
skipping special file '062'
skipping special file '061'
skipping special file '060'
skipping special file '059'
skipping special file '058'
skipping special file '057'
skipping special file '056'
skipping special file '055'
skipping special file '054'
skipping special file '053'
skipping special file '052'
skipping special file '051'
skipping special file '050'
skipping special file '049'
skipping special file '048'
skipping special file '047'
skipping special file '046'
skipping special file '045'
skipping special file '044'
skipping special file '043'
skipping special file '042'
skipping special file '041'
skipping special file '040'
skipping special file '039'
skipping special file '038'
skipping special file '037'
skipping special file '036'
skipping special file '035'
skipping special file '034'
skipping special file '033'
skipping special file '032'
skipping special file '031'
skipping special file '030'
skipping special file '029'
skipping special file '028'
skipping special file '027'
skipping special file '026'
skipping special file '025'
skipping special file '024'
skipping special file '023'
skipping special file '022'
skipping special file '021'
skipping special file '020'
skipping special file '019'
skipping special file '018'
skipping special file '017'
skipping special file '016'
skipping special file '015'
skipping special file '014'
skipping special file '013'
skipping special file '012'
skipping special file '011'
skipping special file '010'
skipping special file '009'
skipping special file '008'
skipping special file '007'
skipping special file '006'
skipping special file '005'
skipping special file '004'
skipping special file '003'
skipping special file '002'
skipping special file '001'
skipping special file '000'
pull: /dev/cpuctl/bg_non_interactive/tasks -> ./cpuctl/bg_non_interactive/tasks
pull: /dev/cpuctl/bg_non_interactive/cgroup.procs -> ./cpuctl/bg_non_interactive/cgroup.procs
pull: /dev/cpuctl/bg_non_interactive/notify_on_release -> ./cpuctl/bg_non_interactive/notify_on_release
pull: /dev/cpuctl/bg_non_interactive/cgroup.event_control -> ./cpuctl/bg_non_interactive/cgroup.event_control
failed to copy '/dev/cpuctl/bg_non_interactive/cgroup.event_control' to './cpuctl/bg_non_interactive/cgroup.event_control': Permission denied
pull: /dev/cpuctl/bg_non_interactive/cgroup.clone_children -> ./cpuctl/bg_non_interactive/cgroup.clone_children
pull: /dev/cpuctl/bg_non_interactive/cpu.shares -> ./cpuctl/bg_non_interactive/cpu.shares
pull: /dev/cpuctl/bg_non_interactive/cpu.rt_runtime_us -> ./cpuctl/bg_non_interactive/cpu.rt_runtime_us
pull: /dev/cpuctl/bg_non_interactive/cpu.rt_period_us -> ./cpuctl/bg_non_interactive/cpu.rt_period_us
pull: /dev/cpuctl/fg_boost/tasks -> ./cpuctl/fg_boost/tasks
pull: /dev/cpuctl/fg_boost/cgroup.procs -> ./cpuctl/fg_boost/cgroup.procspull: /dev/cpuctl/fg_boost/notify_on_release -> ./cpuctl/fg_boost/notify_on_release
pull: /dev/cpuctl/fg_boost/cgroup.event_control -> ./cpuctl/fg_boost/cgroup.event_control
failed to copy '/dev/cpuctl/fg_boost/cgroup.event_control' to './cpuctl/fg_boost/cgroup.event_control': Permission denied
pull: /dev/cpuctl/fg_boost/cgroup.clone_children -> ./cpuctl/fg_boost/cgroup.clone_children
pull: /dev/cpuctl/fg_boost/cpu.shares -> ./cpuctl/fg_boost/cpu.shares
pull: /dev/cpuctl/fg_boost/cpu.rt_runtime_us -> ./cpuctl/fg_boost/cpu.rt_runtime_us
pull: /dev/cpuctl/fg_boost/cpu.rt_period_us -> ./cpuctl/fg_boost/cpu.rt_period_us
pull: /dev/cpuctl/tasks -> ./cpuctl/tasks
pull: /dev/cpuctl/cgroup.procs -> ./cpuctl/cgroup.procs
pull: /dev/cpuctl/notify_on_release -> ./cpuctl/notify_on_release
pull: /dev/cpuctl/cgroup.event_control -> ./cpuctl/cgroup.event_control
failed to copy '/dev/cpuctl/cgroup.event_control' to './cpuctl/cgroup.event_control': Permission denied
pull: /dev/cpuctl/cgroup.clone_children -> ./cpuctl/cgroup.clone_children
pull: /dev/cpuctl/release_agent -> ./cpuctl/release_agent
pull: /dev/cpuctl/cpu.shares -> ./cpuctl/cpu.shares
pull: /dev/cpuctl/cpu.rt_runtime_us -> ./cpuctl/cpu.rt_runtime_us
pull: /dev/cpuctl/cpu.rt_period_us -> ./cpuctl/cpu.rt_period_us
pull: /dev/.coldboot_done -> ./.coldboot_done
failed to copy '/dev/.coldboot_done' to './.coldboot_done': Permission denied
26 files pulled. 0 files skipped.
4 KB/s (3279 bytes in 0.709s)
Code:
[email protected]:/dev $ ls -l
ls -l
crw-rw-r-- system radio 10, 52 2012-12-17 20:24 alarm
crw-rw---- adb adb 10, 56 2012-12-17 20:24 android_adb
crw-rw-rw- root root 10, 58 2012-12-17 20:24 ashmem
crw-rw-rw- root root 10, 47 2012-12-17 20:24 binder
drwxr-xr-x root root 2012-12-17 20:24 block
crw------- root root 5, 1 2012-12-17 20:24 console
crw------- root root 10, 41 2012-12-17 20:24 cpu_dma_latency
crw------- root root 10, 35 2012-12-17 20:24 cpu_freq_max
crw------- root root 10, 36 2012-12-17 20:24 cpu_freq_min
drwxr-xr-x system system 2012-12-17 20:24 cpuctl
crw------- root root 10, 236 2012-12-17 20:24 device-mapper
crw-rw-rw- root root 1, 7 2012-12-17 20:24 full
crw------- root root 10, 229 2012-12-17 20:24 fuse
drwxr-xr-x root root 2012-12-17 20:24 graphics
crw------- root root 89, 0 2012-12-17 20:24 i2c-0
crw------- root root 89, 1 2012-12-17 20:24 i2c-1
crw------- root root 89, 2 2012-12-17 20:24 i2c-2
crw------- root root 89, 3 2012-12-17 20:24 i2c-3
crw------- root root 89, 4 2012-12-17 20:24 i2c-4
crw-rw---- system system 10, 32 2012-12-17 20:24 icx_diag
drwxr-xr-x root root 2012-12-17 20:24 icx_nvp
drwxr-xr-x root root 2012-12-17 20:24 input
crw------- root root 10, 53 2012-12-17 20:24 keychord
crw------- root root 1, 11 2012-12-17 20:24 kmsg
crw-rw---- system system 10, 60 2012-12-17 20:26 knvmap
drwxr-xr-x root root 2012-12-17 20:24 log
crw------- root root 10, 37 2012-12-17 20:24 max_online_cpus
crw------- root root 1, 1 2012-12-17 20:24 mem
crw-rw---- root icx_mg 10, 244 2012-12-17 20:24 mgscc
crw-rw---- root icx_mg 10, 245 2012-12-17 20:24 mgscsi
crw------- root root 10, 38 2012-12-17 20:24 min_online_cpus
crw-rw---- root mtp 10, 55 2012-12-17 20:24 mtp_usb
crw------- root root 10, 40 2012-12-17 20:24 network_latency
crw------- root root 10, 39 2012-12-17 20:24 network_throughput
crw-rw-rw- root root 1, 3 2012-12-17 20:24 null
crw-rw-rw- root root 251, 7 2012-12-17 20:24 nvhost-ctrl
crw-rw-rw- root root 251, 0 2012-12-17 20:24 nvhost-display
crw-rw-rw- root root 251, 6 2012-12-17 20:24 nvhost-dsi
crw-rw-rw- root root 251, 2 2012-12-17 20:24 nvhost-gr2d
crw-rw-rw- root root 251, 1 2012-12-17 20:24 nvhost-gr3d
crw-rw-rw- root root 251, 3 2012-12-17 20:24 nvhost-isp
crw-rw-rw- root root 251, 5 2012-12-17 20:24 nvhost-mpe
crw-rw-rw- root root 251, 4 2012-12-17 20:24 nvhost-vi
crw-rw-rw- system system 10, 61 2012-12-17 20:24 nvmap
crw------- root root 1, 4 2012-12-17 20:24 port
crw-rw---- radio vpn 108, 0 2012-12-17 20:24 ppp
crw-rw-rw- root root 5, 2 2012-12-17 20:34 ptmx
drwxr-xr-x root root 1970-01-01 09:00 pts
crw-rw---- system fm 81, 0 2012-12-17 20:24 radio0
crw-rw-rw- root root 1, 8 2012-12-17 20:24 random
crw------- root root 10, 62 2012-12-17 20:24 rfkill
crw-r--r-- root system 254, 0 2012-12-17 20:24 rtc0
drwxr-xr-x root root 2012-12-17 20:24 snd
drwxr-xr-x root root 2012-12-17 20:24 socket
cr--r--r-- root root 10, 33 2012-12-17 20:24 stuid
crw------- root root 10, 34 2012-12-17 20:24 tegra-crypto
crw-rw---- media wmmedia 10, 49 2012-12-17 20:24 tegra_avp
crw-rw---- system system 250, 1 2012-12-17 20:24 tegra_dc_0
crw-rw---- system system 250, 0 2012-12-17 20:24 tegra_dc_ctrl
crw-rw---- media wmmedia 10, 48 2012-12-17 20:24 tegra_mediaserver
crw-rw---- media wmmedia 10, 50 2012-12-17 20:24 tegra_rpc
crw-rw---- media wmmedia 10, 51 2012-12-17 20:24 tegra_sema
cr--r--r-- system system 10, 59 2012-12-17 20:24 timerinfo
crw-r----- system system 10, 57 2012-12-17 20:24 timerirq
crw-rw-rw- root root 5, 0 2012-12-17 20:24 tty
crw------- root root 248, 0 2012-12-17 20:24 ttyGS0
crw------- root root 248, 1 2012-12-17 20:24 ttyGS1
crw------- root root 248, 2 2012-12-17 20:24 ttyGS2
crw------- root root 248, 3 2012-12-17 20:24 ttyGS3
crw------- system system 249, 1 2012-12-17 20:24 ttyHS1
crw-rw---- bluetooth bluetooth 249, 2 2012-12-17 20:24 ttyHS2
crw------- root root 4, 64 2012-12-17 20:24 ttyS0
crw------- system system 4, 65 2012-12-17 20:24 ttyS1
crw------- root root 4, 66 2012-12-17 20:24 ttyS2
crw------- root root 4, 67 2012-12-17 20:24 ttyS3
crw-rw---- system vpn 10, 200 2012-12-17 20:24 tun
crw-rw---- system bluetooth 10, 223 2012-12-17 20:24 uinput
crw-rw-rw- root root 1, 9 2012-12-17 20:24 urandom
crw-rw---- root usb 10, 54 2012-12-17 20:24 usb_accessory
crw------- root root 10, 63 2012-12-17 20:24 vga_arbiter
crw------- root root 10, 130 2012-12-17 20:24 watchdog
crw------- system system 252, 0 2012-12-17 20:24 wmport
crw-r--r-- root root 10, 42 2012-12-17 20:24 xt_qtaguid
crw-rw-rw- root root 1, 5 2012-12-17 20:24 zero
probably not useful... i cant pull the files out.
EDIT: tar worked. got a tons of dummy files.
Click to expand...
Click to collapse
32kb? so small?
I'll have a look. What do u mean tar works?
zhuhang said:
32kb? so small?
I'll have a look. What do u mean tar works?
Click to expand...
Click to collapse
adb pull /dev didnt really work and when i zipped it, just gave me a 8kb file
i mean, compressing with busybox tar.
Hello everybody!
This will be my first XDA-wide release of my new utility for all LG phones.
What is this?
This is a utility to extract the new format KDZ files that LG distributes, specifically the 'compressed' ones.
LG frequently distributes firmware for phones as KDZ files, which are essentially a firmware image of the eMMC and a DLL file that is used by the downloader utility to communicate with the phone.
In the past, there were utilities to extract KDZ files to a DLL file and a DZ file, but no further (at least to my knowledge).
This utility lets you break the KDZ file into it's respective partitions (aboot, rpm, tz, and so on)
What good does this do me?
If you're an phone modder, haxxor, or just an enthusiast that has access to their phone's KDZ file and would like to have a copy of the actual partitions stored within, this will let you.
As an example, firmware for the new LG G2 on many device models is distributed as a KDZ file only.
Other phones use a TOT file, which is essentially a disk image of the eMMC with no compression.
If someone with a KDZ firmware-only phone wiped a partition (for example, modem) and wanted to get it back without flashing the whole phone all over again, they would be stuck.
TOT files are easily extractable, as there is software available currently for that but until today there was none (to my knowledge) for these new KDZ files.
How do I use this?
Glad you asked.
Inside the ZIP file you'll see two Python scripts, KDZFileTools.py and DZFileTools.py.
There's also a README.txt file for more in-depth information if you're curious.
Both scripts respond to --help or -h, so if you're even more curious, try that too!
KDZ files contain DZ files and DLL files, so the first step will be to split those into their respective parts:
LAS_V08d_pre3_00.kdz is the name of the KDZ file that I've copied to the working directory for this example.
Code:
# python KDZFileTools.py -l -f LAS_V08d_pre3_00.kdz
[+] KDZ Partition List
=========================================
0 : LAS_V08d_pre3_00.dz (1428092632 bytes)
1 : LGUP_8974.dll (1477632 bytes)
This shows me that there are two files inside the KDZ file: LAS_V08d_pre3_00.dz and LGUP_8974.dll
You can now extract them by ID by using the -s option, or by using -x to extract all of the files.
Code:
# python KDZFileTools.py -f LAS_V08d_pre3_00.kdz -x
[+] Extracting all partitions!
[+] Extracting LAS_V08d_pre3_00.dz to kdzextracted\LAS_V08d_pre3_00.dz
[+] Extracting LGUP_8974.dll to kdzextracted\LGUP_8974.dll
Now you'll see a folder called "kdzextracted" in your current working directory, which will contain the extracted files.
The next step would be to extract the DZ file to get the partitions it contains:
Code:
# python DZFileTools.py -f kdzextracted/LAS_V08d_pre3_00.dz -l
[+] DZ Partition List
=========================================
0 : PrimaryGPT_0.bin (4299 bytes)
1 : modem_32768.bin (25719664 bytes)
2 : sbl1_163840.bin (179443 bytes)
3 : dbi_165888.bin (10505 bytes)
4 : aboot_229376.bin (288082 bytes)
5 : rpm_231424.bin (93084 bytes)
6 : boot_262144.bin (8959565 bytes)
7 : tz_294912.bin (149388 bytes)
8 : persist_393216.bin (23621 bytes)
9 : recovery_458752.bin (10454494 bytes)
10 : laf_622592.bin (14244284 bytes)
11 : system_7176192.bin (66791740 bytes)
12 : system_7438336.bin (2651 bytes)
13 : system_7440008.bin (2313 bytes)
14 : system_7444120.bin (103727934 bytes)
15 : system_7704592.bin (114239263 bytes)
16 : system_7964296.bin (2313 bytes)
17 : system_7968408.bin (103349001 bytes)
18 : system_8228880.bin (121921125 bytes)
19 : system_8488584.bin (2313 bytes)
20 : system_8492696.bin (101078725 bytes)
21 : system_8753168.bin (125454806 bytes)
22 : system_9012872.bin (2313 bytes)
23 : system_9016984.bin (105806605 bytes)
24 : system_9277456.bin (115830981 bytes)
25 : system_9537160.bin (2313 bytes)
26 : system_9541272.bin (108458465 bytes)
27 : system_9801744.bin (83280847 bytes)
28 : system_10063888.bin (67940827 bytes)
29 : system_10326032.bin (91997923 bytes)
30 : system_10588176.bin (58015487 bytes)
31 : system_10846208.bin (2314 bytes)
32 : system_11108352.bin (2314 bytes)
33 : system_11370496.bin (2314 bytes)
34 : system_11632640.bin (2314 bytes)
35 : system_11894784.bin (2314 bytes)
36 : system_12156928.bin (2314 bytes)
37 : system_12419072.bin (2314 bytes)
38 : system_12681216.bin (2314 bytes)
39 : system_12943360.bin (2314 bytes)
40 : system_13205504.bin (2314 bytes)
41 : system_13467648.bin (2314 bytes)
42 : system_13729792.bin (2652 bytes)
43 : system_13731464.bin (2314 bytes)
44 : BackupGPT_61070336.bin (4286 bytes)
Excellent! All the files are there!
Large images are split up by LG, and can be combined with "cat" or something like that.
The filename actually is in the form "partname_offset.bin" where "offset" is the actual location that the file should be written to on the phone's eMMC (handy!)
You can substitute -l in the options for -x again to extract all the partitions to the folder "dzextracted" in the current working directory as well.
The option --out or -o will change the output directory, so it doesn't have to output to {kdz|dz}extracted
Where can I download this?
Code:
[URL="http://downloads.codefi.re/thecubed/androidtools/Compressed_KDZUtils.zip"]http://downloads.codefi.re/thecubed/androidtools/Compressed_KDZUtils.zip[/URL]
Please don't mirror this file, as having it in one location makes it easy for me to keep it up to date, or pull it if there are problems with this script
It doesn't work? Can you help me?!
Sure, join #lg-g2 on Freenode and ask for IOMonster and I'll try to help out as best I can.
I will not answer questions in PM or via email, please don't PM me about this script!
As usual, if this script eats your dog/cat/uncle please don't blame me either. I didn't mean to do it, I swear!
Whoo! Thanks! It works! How can I say thanks?
"Thanking" this thread is great!
If you feel that I absolutely saved you many hours of time, feel free to click on the "Donate to Me" button next to my username in this post.
This project was funded by a boring day at work and lots of caffiene
Alright guys, let me know if you've got any questions and I'll see what I can do!
Ha! Just what I was looking for but now to get it to work in Windows...
Thanks!
Edit
So I installed Python for Windows and this was the output...
C:\Python33>KDZFileTools.py -l -f F320K11D_00.kdz
File "C:\Python33\KDZFileTools.py", line 159
print "[!] Error: Unsupported KDZ file format."
^
SyntaxError: invalid syntax
C:\Python33>python.exe DZFileTools.py -l -f D80210C_00.kdz
File "DZFileTools.py", line 96
print "[!] Bad DZ sub header!"
^
SyntaxError: invalid syntax
C:\Python33>python.exe KDZFileTools.py -l -f D80210C_00.kdz
File "KDZFileTools.py", line 159
print "[!] Error: Unsupported KDZ file format."
^
SyntaxError: invalid syntax
AndroidUser00110001 said:
Ha! Just what I was looking for but now to get it to work in Windows...
Thanks!
Edit
So I installed Python for Windows and this was the output...
C:\Python33>KDZFileTools.py -l -f F320K11D_00.kdz
File "C:\Python33\KDZFileTools.py", line 159
print "[!] Error: Unsupported KDZ file format."
^
SyntaxError: invalid syntax
C:\Python33>python.exe DZFileTools.py -l -f D80210C_00.kdz
File "DZFileTools.py", line 96
print "[!] Bad DZ sub header!"
^
SyntaxError: invalid syntax
C:\Python33>python.exe KDZFileTools.py -l -f D80210C_00.kdz
File "KDZFileTools.py", line 159
print "[!] Error: Unsupported KDZ file format."
^
SyntaxError: invalid syntax
Click to expand...
Click to collapse
Not sure what's happening here, but I wrote this in Windows, so it works for me...
Try using Python 2.7 ? I haven't tested it with Py3k...
If it still gives you invalid headers after you get rid of the SyntaxError messages, let me know and I'll take a look. I've only verified that this works on a handful of KDZ files.
Thanks for such a awesome tool. After extracting D80210E_00.kdz, I found that system_xxxxxxx.bin files is not contiguous. Merge into one file, you can not mount it.
would you like to develop a tool more for system partitions merge?
honentan said:
Thanks for such a awesome tool. After extracting D80210E_00.kdz, I found that system_xxxxxxx.bin files is not contiguous. Merge into one file, you can not mount it.
would you like to develop a tool more for system partitions merge?
Click to expand...
Click to collapse
Excellent timing I'm actually working on that right now.
It would appear that the KDZ file contains only the 'sparse' data from large partitions.
Basically, it's the same as if you fed the utility "hexdump" a large file with multiple sections will have the empty sections 'collapsed' and shown as a "*".
My utility needs to take the beginning position of the first system_xxxx.bin file into account, and the end system_xxxx.bin 's position and size.
From there, it knows how big the image file needs to be, then it can simply seek to the position in the new file as defined by each .bin file and write it's contents there.
Ultimately, I'd like to have in-place extraction from the KDZ files, without the need to extract the DZ file itself (since it really is just copying the bytes from the right position to a new file on the hdd), and a utility to merge split partitions, like system.
Until then, if you need to create this image yourself, you can do so with a hex editor or dd
1. Take the first system_xxxxx.bin file and write down the value of xxxxx somewhere. We're going to use this as an offset.
2. Take the last system_xxxxx.bin file and write down it's xxxxx as well. Subtract the two. You should now get the size of the system.img file
3. Use "dd" to create a file of proper length: dd if=/dev/zero of=system.img bs=1 count=SIZE_FROM_EARLIER
4. Now, let's put our files into the right places. The first file can just be merged into it with dd if=system_xxxxx.bin of=system.img conv=notrunc
5. For every file after the first one, you'll have to take the xxxxx value from the file, and subtract the offset you found from step 1. use dd if=system_xxxxx.bin of=system.img seek=VALUE_YOU_JUST_FOUND
6. The end file is no different. Subtract it's xxxxx value again and run the above DD command.
If I'm right, this should leave you with a working partition image.
I haven't verified yet, but it seems logical and should work
thanks for your reply. I am going to try the method as you mentioned just now to merge the system.img using winhex, but I have not verified yet too. I will try it tomorrow.
as a advice, new tool should be able to extract and repack new kdz file.
honentan said:
Thanks for such a awesome tool. After extracting D80210E_00.kdz, I found that system_xxxxxxx.bin files is not contiguous. Merge into one file, you can not mount it.
would you like to develop a tool more for system partitions merge?
Click to expand...
Click to collapse
thecubed said:
Excellent timing I'm actually working on that right now.
It would appear that the KDZ file contains only the 'sparse' data from large partitions.
Basically, it's the same as if you fed the utility "hexdump" a large file with multiple sections will have the empty sections 'collapsed' and shown as a "*".
My utility needs to take the beginning position of the first system_xxxx.bin file into account, and the end system_xxxx.bin 's position and size.
From there, it knows how big the image file needs to be, then it can simply seek to the position in the new file as defined by each .bin file and write it's contents there.
Ultimately, I'd like to have in-place extraction from the KDZ files, without the need to extract the DZ file itself (since it really is just copying the bytes from the right position to a new file on the hdd), and a utility to merge split partitions, like system.
Until then, if you need to create this image yourself, you can do so with a hex editor or dd
1. Take the first system_xxxxx.bin file and write down the value of xxxxx somewhere. We're going to use this as an offset.
2. Take the last system_xxxxx.bin file and write down it's xxxxx as well. Subtract the two. You should now get the size of the system.img file
3. Use "dd" to create a file of proper length: dd if=/dev/zero of=system.img bs=1 count=SIZE_FROM_EARLIER
4. Now, let's put our files into the right places. The first file can just be merged into it with dd if=system_xxxxx.bin of=system.img conv=notrunc
5. For every file after the first one, you'll have to take the xxxxx value from the file, and subtract the offset you found from step 1. use dd if=system_xxxxx.bin of=system.img seek=VALUE_YOU_JUST_FOUND
6. The end file is no different. Subtract it's xxxxx value again and run the above DD command.
If I'm right, this should leave you with a working partition image.
I haven't verified yet, but it seems logical and should work
Click to expand...
Click to collapse
I merged system.img using script as you mentioned, but it couldn't be mounted also.
Progress was obtained, I got all files in system.img using ext2explore(version2.1).
Code:
dd if=/dev/zero of=system.img bs=1 count=5505024
dd if=system_819200.bin of=system.img conv=notrunc seek=0
dd if=system_1081344.bin of=system.img conv=notrunc seek=262144
dd if=system_1082760.bin of=system.img conv=notrunc seek=263560
dd if=system_1086808.bin of=system.img conv=notrunc seek=267608
dd if=system_1347536.bin of=system.img conv=notrunc seek=528336
dd if=system_1607048.bin of=system.img conv=notrunc seek=787848
dd if=system_1611096.bin of=system.img conv=notrunc seek=791896
dd if=system_1871824.bin of=system.img conv=notrunc seek=1052624
dd if=system_2131336.bin of=system.img conv=notrunc seek=1312136
dd if=system_2135384.bin of=system.img conv=notrunc seek=1316184
dd if=system_2396112.bin of=system.img conv=notrunc seek=1576912
dd if=system_2655624.bin of=system.img conv=notrunc seek=1836424
dd if=system_2659672.bin of=system.img conv=notrunc seek=1840472
dd if=system_2920400.bin of=system.img conv=notrunc seek=2101200
dd if=system_3179912.bin of=system.img conv=notrunc seek=2360712
dd if=system_3183960.bin of=system.img conv=notrunc seek=2364760
dd if=system_3444688.bin of=system.img conv=notrunc seek=2625488
dd if=system_3706832.bin of=system.img conv=notrunc seek=2887632
dd if=system_3968976.bin of=system.img conv=notrunc seek=3149776
dd if=system_4231120.bin of=system.img conv=notrunc seek=3411920
dd if=system_4493264.bin of=system.img conv=notrunc seek=3674064
dd if=system_4755408.bin of=system.img conv=notrunc seek=3936208
dd if=system_5017552.bin of=system.img conv=notrunc seek=4198352
dd if=system_5275648.bin of=system.img conv=notrunc seek=4456448
dd if=system_5537792.bin of=system.img conv=notrunc seek=4718592
dd if=system_5799936.bin of=system.img conv=notrunc seek=4980736
dd if=system_6062080.bin of=system.img conv=notrunc seek=5242880
dd if=system_6324224.bin of=system.img conv=notrunc seek=5505024
ext2explore log:
Partition Table Error on D:/Android-ROM/980VS/system.img
Invalid End of sector markerBlock size 4096, inp 8064, inodesize 256
Linux Partition found on disk 1 partition 0
Inode 727 with file size 0
thecubed said:
Not sure what's happening here, but I wrote this in Windows, so it works for me...
Try using Python 2.7 ? I haven't tested it with Py3k...
If it still gives you invalid headers after you get rid of the SyntaxError messages, let me know and I'll take a look. I've only verified that this works on a handful of KDZ files.
Click to expand...
Click to collapse
Thanks, I got it working using 2.7 I have everything extracted and now I need to learn how to merge all the system files.
Thanks!
AndroidUser00110001 said:
Thanks, I got it working using 2.7 I have everything extracted and now I need to learn how to merge all the system files.
Thanks!
Click to expand...
Click to collapse
I'm working on a modified version of the DZFileUtils.py script, since the DZ file actually contains the proper information to regenerate the full system.img easier than using DD or a hex editor.
Work has been a little crazy for the past few days, so I may not get a chance to work on the script until next week, but it won't be that hard to have this script put the system.img files back together.
I could modify the whole toolsets to do in-place extraction from a KDZ file (skipping the intermediate DZ file) but for now this is the easiest and accomplishes my goal the fastest (which is to allow extraction of bootloader stacks from KDZ files found on the interwebs)
I have no plans on creating a utility to generate KDZ files, since myself and @Shelnutt2 are in the process of writing a utility to flash images without needing any LG software on your PC.
I used dd for windows and was able to merge all the files with the script that someone posted. Sorry on XDA App and can't see full thread but thanks for the script.
If you guys need help with testing let me know.
Sent from my LG-D800 using XDA Premium 4 mobile app
thecubed said:
Hello everybody!
This will be my first XDA-wide release of my new utility for all LG phones.
What is this?
This is a utility to extract the new format KDZ files that LG distributes, specifically the 'compressed' ones.
LG frequently distributes firmware for phones as KDZ files, which are essentially a firmware image of the eMMC and a DLL file that is used by the downloader utility to communicate with the phone.
In the past, there were utilities to extract KDZ files to a DLL file and a DZ file, but no further (at least to my knowledge).
This utility lets you break the KDZ file into it's respective partitions (aboot, rpm, tz, and so on)
What good does this do me?
If you're an phone modder, haxxor, or just an enthusiast that has access to their phone's KDZ file and would like to have a copy of the actual partitions stored within, this will let you.
As an example, firmware for the new LG G2 on many device models is distributed as a KDZ file only.
Other phones use a TOT file, which is essentially a disk image of the eMMC with no compression.
If someone with a KDZ firmware-only phone wiped a partition (for example, modem) and wanted to get it back without flashing the whole phone all over again, they would be stuck.
TOT files are easily extractable, as there is software available currently for that but until today there was none (to my knowledge) for these new KDZ files.
How do I use this?
Glad you asked.
Inside the ZIP file you'll see two Python scripts, KDZFileTools.py and DZFileTools.py.
There's also a README.txt file for more in-depth information if you're curious.
Both scripts respond to --help or -h, so if you're even more curious, try that too!
KDZ files contain DZ files and DLL files, so the first step will be to split those into their respective parts:
LAS_V08d_pre3_00.kdz is the name of the KDZ file that I've copied to the working directory for this example.
Code:
# python KDZFileTools.py -l -f LAS_V08d_pre3_00.kdz
[+] KDZ Partition List
=========================================
0 : LAS_V08d_pre3_00.dz (1428092632 bytes)
1 : LGUP_8974.dll (1477632 bytes)
This shows me that there are two files inside the KDZ file: LAS_V08d_pre3_00.dz and LGUP_8974.dll
You can now extract them by ID by using the -s option, or by using -x to extract all of the files.
Code:
# python KDZFileTools.py -f LAS_V08d_pre3_00.kdz -x
[+] Extracting all partitions!
[+] Extracting LAS_V08d_pre3_00.dz to kdzextracted\LAS_V08d_pre3_00.dz
[+] Extracting LGUP_8974.dll to kdzextracted\LGUP_8974.dll
Now you'll see a folder called "kdzextracted" in your current working directory, which will contain the extracted files.
The next step would be to extract the DZ file to get the partitions it contains:
Code:
# python DZFileTools.py -f kdzextracted/LAS_V08d_pre3_00.dz -l
[+] DZ Partition List
=========================================
0 : PrimaryGPT_0.bin (4299 bytes)
1 : modem_32768.bin (25719664 bytes)
2 : sbl1_163840.bin (179443 bytes)
3 : dbi_165888.bin (10505 bytes)
4 : aboot_229376.bin (288082 bytes)
5 : rpm_231424.bin (93084 bytes)
6 : boot_262144.bin (8959565 bytes)
7 : tz_294912.bin (149388 bytes)
8 : persist_393216.bin (23621 bytes)
9 : recovery_458752.bin (10454494 bytes)
10 : laf_622592.bin (14244284 bytes)
11 : system_7176192.bin (66791740 bytes)
12 : system_7438336.bin (2651 bytes)
13 : system_7440008.bin (2313 bytes)
14 : system_7444120.bin (103727934 bytes)
15 : system_7704592.bin (114239263 bytes)
16 : system_7964296.bin (2313 bytes)
17 : system_7968408.bin (103349001 bytes)
18 : system_8228880.bin (121921125 bytes)
19 : system_8488584.bin (2313 bytes)
20 : system_8492696.bin (101078725 bytes)
21 : system_8753168.bin (125454806 bytes)
22 : system_9012872.bin (2313 bytes)
23 : system_9016984.bin (105806605 bytes)
24 : system_9277456.bin (115830981 bytes)
25 : system_9537160.bin (2313 bytes)
26 : system_9541272.bin (108458465 bytes)
27 : system_9801744.bin (83280847 bytes)
28 : system_10063888.bin (67940827 bytes)
29 : system_10326032.bin (91997923 bytes)
30 : system_10588176.bin (58015487 bytes)
31 : system_10846208.bin (2314 bytes)
32 : system_11108352.bin (2314 bytes)
33 : system_11370496.bin (2314 bytes)
34 : system_11632640.bin (2314 bytes)
35 : system_11894784.bin (2314 bytes)
36 : system_12156928.bin (2314 bytes)
37 : system_12419072.bin (2314 bytes)
38 : system_12681216.bin (2314 bytes)
39 : system_12943360.bin (2314 bytes)
40 : system_13205504.bin (2314 bytes)
41 : system_13467648.bin (2314 bytes)
42 : system_13729792.bin (2652 bytes)
43 : system_13731464.bin (2314 bytes)
44 : BackupGPT_61070336.bin (4286 bytes)
Excellent! All the files are there!
Large images are split up by LG, and can be combined with "cat" or something like that.
The filename actually is in the form "partname_offset.bin" where "offset" is the actual location that the file should be written to on the phone's eMMC (handy!)
You can substitute -l in the options for -x again to extract all the partitions to the folder "dzextracted" in the current working directory as well.
The option --out or -o will change the output directory, so it doesn't have to output to {kdz|dz}extracted
Where can I download this?
Code:
[URL="http://downloads.codefi.re/thecubed/androidtools/Compressed_KDZUtils.zip"]http://downloads.codefi.re/thecubed/androidtools/Compressed_KDZUtils.zip[/URL]
Please don't mirror this file, as having it in one location makes it easy for me to keep it up to date, or pull it if there are problems with this script
It doesn't work? Can you help me?!
Sure, join #lg-g2 on Freenode and ask for IOMonster and I'll try to help out as best I can.
I will not answer questions in PM or via email, please don't PM me about this script!
As usual, if this script eats your dog/cat/uncle please don't blame me either. I didn't mean to do it, I swear!
Whoo! Thanks! It works! How can I say thanks?
"Thanking" this thread is great!
If you feel that I absolutely saved you many hours of time, feel free to click on the "Donate to Me" button next to my username in this post.
This project was funded by a boring day at work and lots of caffiene
Alright guys, let me know if you've got any questions and I'll see what I can do!
Click to expand...
Click to collapse
Hi, i make my phone soft bricked. no other method works. i need bin file to flash my phone.i have the orignal kdz file.how can i make a single bin file to flash it using LGNPST? If you want to read my whole phone bricking story, please follow this
http://forum.xda-developers.com/showthread.php?t=2492105
AAAAwesome!!!
Thank you very much!
Able to customize LG's ROM easier than ever!
thecubed said:
I'm working on a modified version of the DZFileUtils.py script, since the DZ file actually contains the proper information to regenerate the full system.img easier than using DD or a hex editor.
Work has been a little crazy for the past few days, so I may not get a chance to work on the script until next week, but it won't be that hard to have this script put the system.img files back together.
I could modify the whole toolsets to do in-place extraction from a KDZ file (skipping the intermediate DZ file) but for now this is the easiest and accomplishes my goal the fastest (which is to allow extraction of bootloader stacks from KDZ files found on the interwebs)
I have no plans on creating a utility to generate KDZ files, since myself and @Shelnutt2 are in the process of writing a utility to flash images without needing any LG software on your PC.
Click to expand...
Click to collapse
Any word on the DZfileUtils.py script? I am trying to convert the dz to the system img and all I get is errors when trying to use dd. If there is a better way than dd for windows could someone let me know.
Well I think I have found where my error was at with what I was trying to do.
Thank you for all your hard work on this
honentan said:
I merged system.img using script as you mentioned, but it couldn't be mounted also.
Progress was obtained, I got all files in system.img using ext2explore(version2.1).
ext2explore log:
Partition Table Error on D:/Android-ROM/980VS/system.img
Invalid End of sector markerBlock size 4096, inp 8064, inodesize 256
Linux Partition found on disk 1 partition 0
Inode 727 with file size 0
Click to expand...
Click to collapse
I can confirm I could not mount or use normal methods I have used in the past for getting the system image extracted but I also used ext2explore on windows and it worked like a charm. Thank you
Thanks for tools:good:
but I got this error when I tried with KDZ file.
C:\Users\VM\Desktop\Compressed_KDZUtils>KDZFileTools.py -f L01E20A_00.kdz -x
[!] Error: Unsupported KDZ file format.
[ ] Expected: 0x28 0x5 0x0 0x0 0x34 0x31 0x25 0x80 ,
but received 0x31 0x23 0x53 0x7f 0x89 0x1e 0xe6 0x9b .
Click to expand...
Click to collapse
and when I got DZ file from other KDZ extracter and tried DZ file I got this
C:\Users\VM\Desktop\Compressed_KDZUtils>DZFileTools.py -f L01E20A_00.dz -l
[!] Error: Unsupported DZ file format.
[ ] Expected: 0x32 0x96 0x18 0x74 ,
but received 0x22 0x12 0x84 0x19 .
Traceback (most recent call last):
File "C:\Users\VM\Desktop\Compressed_KDZUtils\DZFileTools.py", line 212, in
<module>
dztools.main()
File "C:\Users\VM\Desktop\Compressed_KDZUtils\DZFileTools.py", line 196, in
main
self.openFile(args.dzfile)
File "C:\Users\VM\Desktop\Compressed_KDZUtils\DZFileTools.py", line 173, in
openFile
sys.exit(0)
NameError: global name 'sys' is not defined
Click to expand...
Click to collapse
I never run python script but I think I did it right.
I'm installed python 2.7. and KDZ file is for Optimus G
rquiett said:
I can confirm I could not mount or use normal methods I have used in the past for getting the system image extracted but I also used ext2explore on windows and it worked like a charm. Thank you
Click to expand...
Click to collapse
honentan said:
I merged system.img using script as you mentioned, but it couldn't be mounted also.
Progress was obtained, I got all files in system.img using ext2explore(version2.1).
Click to expand...
Click to collapse
in linux
Code:
mkdir -p /mnt/dsk
mount -o loop system.img /mnt/dsk
this will return an error
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
Click to expand...
Click to collapse
run dmesg
Code:
dmesg | tail
there will be a line like this:
EXT4-fs (loop0): bad geometry: block count 851968 exceeds size of device (819537 blocks)
Click to expand...
Click to collapse
now truncate the file with the value of the first number
Code:
truncate -o -s 851968
remount, and hey presto.
thank you @Flinny for this
edit: not needed anymore, just ignore it. keeping it here for reference though
merging the bins on linux
ok, so there have been a few issues with getting this done on any platform. I was asked to try to get into a kdz for someone, so I did it
included below is a python script that takes advantage of dd. I've set it up for the system partition (as that's the only one that is split)
I have left all my comments and tweaks in so you can see how it was formed
to run:
Code:
python SystemMerger.py
It should run with python3 (untested). can someone please report any errors and I'll see if I can fix them up.
after running the script, just mount the image, and you're away
Happy Hacking
ps, don't forget to change the extension to .py
ok final version here, should support windows now
https://github.com/cybojenix/random-scripts/blob/master/SystemMerger.py
it should also support python3 still, but someone please check, same with windows (though I'm sceptical about the way I write zeros. might not work on winblows...)
anyway, happy hacking again
cybojenix said:
ok final version here, should support windows now
https://github.com/cybojenix/random-scripts/blob/master/SystemMerger.py
it should also support python3 still, but someone please check, same with windows (though I'm sceptical about the way I write zeros. might not work on winblows...)
anyway, happy hacking again
Click to expand...
Click to collapse
good job! awesome! thanks.
AndroidUser00110001 said:
Ha! Just what I was looking for but now to get it to work in Windows...
Thanks!
Edit
So I installed Python for Windows and this was the output...
C:\Python33>KDZFileTools.py -l -f F320K11D_00.kdz
File "C:\Python33\KDZFileTools.py", line 159
print "[!] Error: Unsupported KDZ file format."
^
SyntaxError: invalid syntax
C:\Python33>python.exe DZFileTools.py -l -f D80210C_00.kdz
File "DZFileTools.py", line 96
print "[!] Bad DZ sub header!"
^
SyntaxError: invalid syntax
C:\Python33>python.exe KDZFileTools.py -l -f D80210C_00.kdz
File "KDZFileTools.py", line 159
print "[!] Error: Unsupported KDZ file format."
^
SyntaxError: invalid syntax
Click to expand...
Click to collapse
just put bracket on each print params, then it should work
like this print ("[!] Error: Unsupported KDZ file format.")
also the KDZFileTools not work on LG G2, the header doesnt match with required
here
i debug to find what is the actual value on verify_header
D80210b.kdz header found
>>> verify_header
b'(\x05\x00\x0041%\x80'
kdz_header = '0x28 0x5 0x0 0x0 0x34 0x31 0x25 0x80'
KDZFileTools error log
[!] Error: Unsupported KDZ file format.
Traceback (most recent call last):
File "C:\Downloads\KDZFileTools.py", line 197, in <module>
kdztools.main()
File "C:\Downloads\KDZFileTools.py", line 182, in main
self.openFile(args.kdzfile)
File "C:\Downloads\KDZFileTools.py", line 160, in openFile
print ("[ ] Expected: %s ,\n\tbut received %s ." % (" ".join(hex(ord) for n in self.kdz_header), " ".join(hex(ord) for n in verify_header)))
File "C:\Downloads\KDZFileTools.py", line 160, in <genexpr>
print ("[ ] Expected: %s ,\n\tbut received %s ." % (" ".join(hex(ord) for n in self.kdz_header), " ".join(hex(ord) for n in verify_header)))
TypeError: ord() expected string of length 1, but int found
Click to expand...
Click to collapse
SAMSUNG GENERAL PATCHER V2.2
SUPPORT: TELEGRAM CHANNEL - TELEGRAM GROUP - SUPPORT ME
ABOUT THIS:Magisk module to automatically patch the services.jar of Samsung devices, based on Dynamic Installer
The compatibility is relative but Android 10+ is recommended
ALL features:
Disable Signature Verification
Disable Flag Secure
Try to patch SecureFolder (Android 10 method and Android 11)
Enable Biometrics (Fingerprint/FaceUnlock) after reboot
General APK recompiling with stock Signature to prevent rejects from system
HOW DO I USE IT?
Code:
1. Simply install the module on 64bits devices (Not tested on 32bits) by Magisk app
2. The process requires the recompilation of a .JAR so be patient!
CREDITS TO:
Me @BlassGO (Developer of Samsung Patcher and Dynamic Installer)
General Samsung Patcher 2.2
WARNING: In case of any ERROR, delete the module: /data/adb/modules/samsung-patcher
Download link not working, it says the file got removed
SkylinesHD said:
Download link not working, it says the file got removed
Click to expand...
Click to collapse
Thanks for the report, the download is now available
BlassGO said:
Thanks for the report, the download is now available
Click to expand...
Click to collapse
Now it says the file is infected and that's why I'm not permitted to download it
SkylinesHD said:
Now it says the file is infected and that's why I'm not permitted to download it
Click to expand...
Click to collapse
Okey I updated it in AFH, Ill stop using gdrive
where is the link?
dolf123 said:
where is the link?
Click to expand...
Click to collapse
Open General Samsung Patcher from the end
When trying to install module I got this error..
Please tell me how to fix it..
ahmed.sbahii said:
When trying to install module I got this error..
Please tell me how to fix it..
Click to expand...
Click to collapse
Plz send a magisk log
Not hav
BlassGO said:
Plz send a magisk log
Click to expand...
Click to collapse
Not have magisk
Should I use magisk only..?
ahmed.sbahii said:
Not hav
Not have magisk
Should I use magisk only..?
Click to expand...
Click to collapse
Yeah, its a magisk module
BlassGO said:
Yeah, its a magisk module
Click to expand...
Click to collapse
My device Doesn't accept Magisk...!
I don' know why..!
After I install magisk it doesn't give any permission root...!
Can you give me another way to install this model or do it myself manually...
Without Magisk or TWRP..?
If you have it please tell me because I need run secure folder again..
Thanks in advance..
ahmed.sbahii said:
My device Doesn't accept Magisk...!
I don' know why..!
After I install magisk it doesn't give any permission root...!
Can you give me another way to install this model or do it myself manually...
Without Magisk or TWRP..?
If you have it please tell me because I need run secure folder again..
Thanks in advance..
Click to expand...
Click to collapse
If u have root access (without magisk) and based on ur screenshots, it seemed that almost everything worked, in that case edit the zip META-INF/com/google/android/magisk/customize.sh and change the mod="$MODPATH/system/framework/services.jar" to mod="/sdcard/services.jar", then replace the services.jar that will be generated in your internal memory in /system/framework
Additionally replace the libs from the zip in /system/lib and /system/lib64
NOTE: The SecureFolder patch is based on Android 10 method, maybe it not work in older Android versions
ahmed.sbahii said:
My device Doesn't accept Magisk...!
I don' know why..!
After I install magisk it doesn't give any permission root...!
Can you give me another way to install this model or do it myself manually...
Without Magisk or TWRP..?
If you have it please tell me because I need run secure folder again..
Thanks in advance..
Click to expand...
Click to collapse
If u have root access (without magisk) and based on ur screenshots, it seemed that almost everything worked, in that case edit the zip META-INF/com/google/android/magisk/customize.sh and change the mod="$MODPATH/system/framework/services.jar" to mod="/sdcard/services.jar", then replace the services.jar that will be generated in your internal memory in /system/framework
NOTE: The SecureFolder patch is based on Android 10 method, maybe it not work in
BlassGO said:
If u have root access (without magisk) and based on ur screenshots, it seemed that almost everything worked, in that case edit the zip META-INF/com/google/android/magisk/customize.sh and change the mod="$MODPATH/system/framework/services.jar" to mod="/sdcard/services.jar", then replace the services.jar that will be generated in your internal memory in /system/framework
NOTE: The SecureFolder patch is based on Android 10 method, maybe it not work in
Click to expand...
Click to collapse
Now after many tryies to install magisk
Succesfully installed and try with magisk but same error nothing changed..
My sevice is on Android 10
What is the pronlem with my device..?
My device is N970F..?
What should I do now..?
BlassGO said:
If u have root access (without magisk) and based on ur screenshots, it seemed that almost everything worked, in that case edit the zip META-INF/com/google/android/magisk/customize.sh and change the mod="$MODPATH/system/framework/services.jar" to mod="/sdcard/services.jar", then replace the services.jar that will be generated in your internal memory in /system/framework
Additionally replace the libs from the zip in /system/lib and /system/lib64
NOTE: The SecureFolder patch is based on Android 10 method, maybe it not work in older Android versions
Click to expand...
Click to collapse
And this is the log from Magisk
ahmed.sbahii said:
And this is the log from Magisk
Click to expand...
Click to collapse
Huh, press the top save button for a full log
BlassGO said:
Huh, press the top save button for a full log
Click to expand...
Click to collapse
- Copying zip to temp directory
- Installing General_Samsung_Patcher_BlassGO.zip
ls: /system/sbin: No such file or directory
ls: /product/bin: No such file or directory
ls: /system/xbin: No such file or directory
ls: /odm/bin: No such file or directory
ls: /vendor/xbin: No such file or directory
- Device is system-as-root
chown: 0: No such file or directory
chown: 0: No such file or directory
----------------------------------------
>>> Powered by Magisk 23000
----------------------------------------
chown: 0: No such file or directory
chown: 0: No such file or directory
chown: 0: No such file or directory
chown: 0: No such file or directory
chown: 0: No such file or directory
chown: 0: No such file or directory
--------------------------------------------------
General Samsung Patcher
--------------------------------------------------
by @BlassGO | Version: Beta-1.0
--------------------------------------------------
-- Disable Signature Verification
-- Disable Flag Secure
-- Try to patch SecureFolder (Android 10+)
--------------------------------------------------
-- Making magisk space
-- Decompiling services.jar...
chown: 0: No such file or directory
chown: 0: No such file or directory
chown: 0: No such file or directory
chown: 0: No such file or directory
-- Patching services.jar for SecureFolder...
Edited: /dev/tmp/services/smali_classes2/com/android/server/locksettings/SyntheticPasswordManager.smali
Edited: /dev/tmp/services/smali_classes2/com/android/server/pm/TimaHelper.smali
Edited: /dev/tmp/services/smali/com/android/server/KnoxFileHandler.smali
Edited: /dev/tmp/services/smali_classes2/com/android/server/pm/PersonaServiceHelper.smali
Edited: /dev/tmp/services/smali_classes2/com/android/server/pm/PersonaServiceHelper.smali
-- Disabling Flag Secure in services.jar...
Edited: /dev/tmp/services/smali_classes2/com/android/server/wm/ScreenshotController.smali
-- Disabling Signature Verification in services.jar...
Edited: /dev/tmp/services/smali_classes2/com/android/server/pm/PackageManagerServiceUtils.smali
Edited: /dev/tmp/services/smali_classes2/com/android/server/pm/PackageManagerServiceUtils.smali
Edited: /dev/tmp/services/smali_classes2/com/android/server/pm/PackageManagerServiceUtils.smali
Edited: /dev/tmp/services/smali_classes2/com/android/server/pm/PackageManagerService.smali
Edited: /dev/tmp/services/smali_classes2/com/android/server/pm/PackageManagerService$InstallParams.smali
-- Recompiling services.jar...
-- Please wait...( Long Process )
chown: 0: No such file or directory
chown: 0: No such file or directory
chown: 0: No such file or directory
chown: 0: No such file or directory
W: Could not find resources
CANNOT LINK EXECUTABLE "zip": library "libandroid-support.so" not found
mv: can't create '/data/adb/modules_update/samsung-patcher/system/framework/services.jar': Permission denied
-- Some ERROR occurred during the recompilation !
! Installation failed
A full log..!!
ahmed.sbahii said:
- Copying zip to temp directory
- Installing General_Samsung_Patcher_BlassGO.zip
ls: /system/sbin: No such file or directory
ls: /product/bin: No such file or directory
ls: /system/xbin: No such file or directory
ls: /odm/bin: No such file or directory
ls: /vendor/xbin: No such file or directory
- Device is system-as-root
chown: 0: No such file or directory
chown: 0: No such file or directory
----------------------------------------
>>> Powered by Magisk 23000
----------------------------------------
chown: 0: No such file or directory
chown: 0: No such file or directory
chown: 0: No such file or directory
chown: 0: No such file or directory
chown: 0: No such file or directory
chown: 0: No such file or directory
--------------------------------------------------
General Samsung Patcher
--------------------------------------------------
by @BlassGO | Version: Beta-1.0
--------------------------------------------------
-- Disable Signature Verification
-- Disable Flag Secure
-- Try to patch SecureFolder (Android 10+)
--------------------------------------------------
-- Making magisk space
-- Decompiling services.jar...
chown: 0: No such file or directory
chown: 0: No such file or directory
chown: 0: No such file or directory
chown: 0: No such file or directory
-- Patching services.jar for SecureFolder...
Edited: /dev/tmp/services/smali_classes2/com/android/server/locksettings/SyntheticPasswordManager.smali
Edited: /dev/tmp/services/smali_classes2/com/android/server/pm/TimaHelper.smali
Edited: /dev/tmp/services/smali/com/android/server/KnoxFileHandler.smali
Edited: /dev/tmp/services/smali_classes2/com/android/server/pm/PersonaServiceHelper.smali
Edited: /dev/tmp/services/smali_classes2/com/android/server/pm/PersonaServiceHelper.smali
-- Disabling Flag Secure in services.jar...
Edited: /dev/tmp/services/smali_classes2/com/android/server/wm/ScreenshotController.smali
-- Disabling Signature Verification in services.jar...
Edited: /dev/tmp/services/smali_classes2/com/android/server/pm/PackageManagerServiceUtils.smali
Edited: /dev/tmp/services/smali_classes2/com/android/server/pm/PackageManagerServiceUtils.smali
Edited: /dev/tmp/services/smali_classes2/com/android/server/pm/PackageManagerServiceUtils.smali
Edited: /dev/tmp/services/smali_classes2/com/android/server/pm/PackageManagerService.smali
Edited: /dev/tmp/services/smali_classes2/com/android/server/pm/PackageManagerService$InstallParams.smali
-- Recompiling services.jar...
-- Please wait...( Long Process )
chown: 0: No such file or directory
chown: 0: No such file or directory
chown: 0: No such file or directory
chown: 0: No such file or directory
W: Could not find resources
CANNOT LINK EXECUTABLE "zip": library "libandroid-support.so" not found
mv: can't create '/data/adb/modules_update/samsung-patcher/system/framework/services.jar': Permission denied
-- Some ERROR occurred during the recompilation !
! Installation failed
A full log..!!
Click to expand...
Click to collapse
Okey thx
It seems a problem with the Dynamic Installer base, but currently I already developed a v2.0 based on a new version of Dynamic Installer, contact me on pv
Ok I contact with you
I'm attempting to use adb's push command on Windows 10 in order to transfer files from my PC to my Oneplus 9 Pro. I installed adb by following the instructions here. When I attempt to do the file transfer, I receive a large number of error message for some of the files, that all look like this:
Code:
E:\>adb push Music /sdcard/Music
cannot lstat 'Music/??????': No such file or directory
cannot lstat 'Music/????? ??....flac': No such file or directory
cannot lstat 'Music/????? ????????? - ??????? ?????? (2011)': No such file or directory
cannot lstat 'Music/????????? ??????? ??? - 1990 - ??? ?? ??????': No such file or directory
cannot lstat 'Music/???? ? ????????.mp3': No such file or directory
cannot lstat 'Music/??? ?????? ?????.flac': No such file or directory
cannot lstat 'Music/??????? ????.mp3': No such file or directory
cannot lstat 'Music/??????': No such file or directory
cannot lstat 'Music/?????? ????.flac': No such file or directory
cannot lstat 'Music/?? ?????? ???? ??? ? ? ????? ?? ??????.mp3': No such file or directory
cannot lstat 'Music/??, ???????.mp3': No such file or directory
I have used adb with these exact same files before, when I was still running Manjaro, with no issues or error messages such as these, so I'm fairly confident the issue is not with the files themselves. Even more bizarrely, when I attempt to use the --sync command, it doesn't even recognize it as a command:
Code:
E:\>adb push --sync Music /sdcard/Music
cannot stat '--sync': No such file or directory
I've attempted to uninstall and reinstall adb, but the issues persists in spite of that. What possible solutions are there to this?
Youn have to name the fullpathname of folder Music on PC.
xXx yYy said:
Youn have to name the fullpathname of folder Music on PC.
Click to expand...
Click to collapse
I do have the full path name, Music folder is located in E:\Music and I open Command Prompt to E:\ drive. I also know it's the correct path name because some of the files do transfer, but a large number have errors as discussed above.