Database Develop

can i...?

push a ROM onto my sdcard through adb?
my win xp is so old it wont read the root of my sdcard unless its only fat32...
so i was wondering if i could do it that way...
ive looked through threads but hadnt found a definite answer seeing as im new to all this
any help would be appreciated!

I am not sure you are understanding the process or I am not understanding the question.
But lets just roll with it...
You can do:
adb push c:\romNam.zip /sdcard
Click to expand...
Click to collapse
This will put the romName.zip file on the root of your sdcard (fat32 partition). From there you can reboot into recovery mode (turn off phone, then hold down the HOME button and then hit the POWER button). If you have the CM 1.4 recovery image installed then you can install any zip file and you would just point to the romName.zip file. If you have the CM 1.3 recovery image you should rename the romName.zip file to update.zip and then apply that update from the menu in CM 1.3.
If you do not have the CM recovery image installed, well, then you need to back and read some more.

i think you are on the right track for what im asking...
im using cm 1.4 recovery
lets say i dl drizzys 1.5.5
do i rename it update?update.zip?or leave it as is the way i downloaded it?
i tried putting it on my c drive and naming it update and it didnt work
or course i was using someone elses thread to go by so maybe i did it wrong

Do you have adb set up so it can connect to your phone?
If you have CM recovery 1.4 you do not have to rename it to update.zip but go ahead and do that for this test.
When you say
i tried putting it on my c drive and naming it update and it didnt work
Click to expand...
Click to collapse
what do you mean?
The renaming didn't work, or the adb push didn't work

renaming it update and trying to push it through adb didnt work...
im downloading another ROM and im gonna try again and see if it might work this time...

Right. But what I am asking is, what "didnt work." Was the file not there on the sdcard after you pushed? Did the CM recovery image fail to apply the update?

the file wasnt on the sd and cm didnt see it to install...

i may have named it wrong...or missed the space between zip and /
i will try again and see if thats what was wrong...

Okay.
When you set up adb did you follow this thread?
If you are not able to mount your sdcard in windows that may or may not be a showstopper. How do you have your sdcard formatted? All fat32 or did you split it up into fat32, ext3, linux-swap?
If you are going to adb push files to your sdcard you should NOT mount the sdcard.

yes...i followed that thread
and i repartitioned my 4gb sdcard as such:
fat32 0 1405
ext3 1405 1905
linux-swap 1905 2001
and i did not mount my phone...i at least saw not to do that in very bold letters so i took it to heart...lol!

Okay, cool.
What does the CM 1.4 tell you when you try to apply the update.zip?
After you adb push the file, go into the device via adb shell.
CD to the /sdcard and do an "ls" and tell me what you see.
If you do not see anything but the adb push returned no errors, your sdcard may be fubar (don't freak yet, there are fixes for it and we will get there if we need to).
If you do see the zip file then reboot into recovery again. But this time do not try to apply an update, instead drop to a console and CD into the /sdcard again and do another "ls" and let me know what you see.

i just tried doing this:
cd c:\android-sdk-windows-1.6_r1\tools>adb shell
/ # adb push c:\KiNgxKxROM_Beta1_RedRosieThemev1_signed.zip /sdcard
/sbin/sh: adb: not found
then i tried:
/ # adb push c:\KiNgxKxROM_Beta1_RedRosieThemev1_signed /sdcard
/sbin/sh: adb: not found
then:
/ # adb push c:\update /sdcard
/sbin/sh: adb: not found
nothing

and where do i look in the forums...or how exactly do i cd to the sdcard?

aha!
I see the issue.
You do not need to adb shell then do adb push
it shoul be like:
C:c:\android-sdk-windows-1.6_r1\tools> adb push c:\KiNgxKxROM_Beta1_RedRosieThemev1_signed.zip /sdcard
Click to expand...
Click to collapse
adb push is done from your local dos window not from within the adb shell.
Try that out and let me know.

wow!
that did it! thank you sooooo much!
thats just one more step i can eliminate now!

no Problem. Welcome to the world of roms.

care to walk me through how to use switchrom? lol!
all these hero builds seem to crash on me after awhile and i kinda wanna have several to switch to if/when they fail...

Temp-root for IS on Android 2.3 without PC

I tested this and it work on Incredible S with Android 2.3!
Gingerbreak download here: http://forum.xda-developers.com/showthread.php?t=1044765
1. Copied v1.2 apk in a fresh sd card and installed it to phone.
2. ran the tool and clicked root
3. Message saying "Not sure what happened here..." came within like 30sec of clicking root.
4. waited for another 5-6 mins with the message on screen no crash no restart on the device.
5. Clicked Ok on the message and checked if i have a root(without a restart): SUCCESS!!!
Click to expand...
Click to collapse
If you get a get a permission denied error to copy files on /system partition
please type:
su
chmod 777 /system in terminal emulator

Pacjonek said:
I tested this and it work on Incredible S with Android 2.3!
Gingerbreak download here: http://forum.xda-developers.com/showthread.php?t=1044765
If you get a get a permission denied error to copy files on /system partition
please type:
chmod 777 /system/app in terminal emulator
Click to expand...
Click to collapse
This should not be used for temproot on a S-On device. You can't use your sdcard and it also makes a few apps unusable.
Please read the original thread carefully.

ADB Shell not working, but my N1 isn't bricked

I wanted to use USB Tunnel to share my PC's internet connection with the phone, but I got the error:
Code:
- exec '/system/bin/sh' failed: No such file or directory (2) -
I tried to install other APK's through ADB and they also failed, so I googled this error and I saw that the main issue is a failing ADB Shell. I tried to open Shell and I got the same error. The difference between me and the other users is that my phone is booting as usual, USB Mass Storage works, the phone is detected by fastboot- and adb devices commands and everything is working as intended, except for installing APKs through ADB/opening Shell.
Here is my phone's current config:
MeDroidMod 1.4.4 w/ HWA
Latest Tiamat kernel
TexasICE HBOOT w/ 210/8/218 partition layout
4GB microSD card...I don't know the filesystem but it's definitely NOT ext4, so there's not A2SD for me (I think it's FAT or FAT32)
ClockWorkMod Recovery

gnexus47 said:
I wanted to use USB Tunnel to share my PC's internet connection with the phone, but I got the error:
Code:
- exec '/system/bin/sh' failed: No such file or directory (2) -
I tried to install other APK's through ADB and they also failed, so I googled this error and I saw that the main issue is a failing ADB Shell. I tried to open Shell and I got the same error. The difference between me and the other users is that my phone is booting as usual, USB Mass Storage works, the phone is detected by fastboot- and adb devices commands and everything is working as intended, except for installing APKs through ADB/opening Shell.
Here is my phone's current config:
MeDroidMod 1.4.4 w/ HWA
Latest Tiamat kernel
TexasICE HBOOT w/ 210/8/218 partition layout
4GB microSD card...I don't know the filesystem but it's definitely NOT ext4, so there's not A2SD for me (I think it's FAT or FAT32)
ClockWorkMod Recovery
Click to expand...
Click to collapse
Which adb commands did you use? Can you list the commands here that you had used? It could be that you didn't issue su command to get superuser rights?

you don't need to be in Shell to push apk
put the apk on your C: drive
open command window and navigate to the folder you have adb/fastboot in--normally tools of your sdk
then:
type adb devices--then
1. adb remount
2. adb push C:/CalendarGoogle.apk /system/app/CalendarGoogle.apk
3. adb push C:/CalendarProvider.apk /system/app/CalendarProvider.apk
4. adb shell
7. chmod 777 system/app/CalendarGoogle.apk
11. chmod 777 system/app/CalendarProvider.apk
12. exit
13. Reboot
use the apk name of whatever you are flashing in place of mine and your chmod may not be exactly like mine--

ADB Shell
rugmankc said:
you don't need to be in Shell to push apk
put the apk on your C: drive
open command window and navigate to the folder you have adb/fastboot in--normally tools of your sdk
then:
type adb devices--then
1. adb remount
2. adb push C:/CalendarGoogle.apk /system/app/CalendarGoogle.apk
3. adb push C:/CalendarProvider.apk /system/app/CalendarProvider.apk
4. adb shell
7. chmod 777 system/app/CalendarGoogle.apk
11. chmod 777 system/app/CalendarProvider.apk
12. exit
13. Reboot
use the apk name of whatever you are flashing in place of mine and your chmod may not be exactly like mine--
Click to expand...
Click to collapse
I don't use ADB Shell to push APK's. That's just another thing which doesn't work.
@taodan: I only use: adb install xxxxx.apk.

A work around is to mount the sdcard and drag and drop the apks to the sdcard. Then install using your favorite file manager.

evilkorn said:
A work around is to mount the sdcard and drag and drop the apks to the sdcard. Then install using your favorite file manager.
Click to expand...
Click to collapse
that will work too, i've used root explorer to copy paste from sdcard to correct file location. prefer adb. set your permissions after
did you try adb remount first, not sure if that would help
what i was saying is you don't need to type adb shell. assuming you are doing this from a pc command terminal window.
you can use the commands I gave above to push apk. i think when you push it copies apk to phone leaving apk on pc also. install actually moves it to phone--as i understand it
here is some links and info that might help.*
http://www.talkandroid.com/guides/beginner/install-apk-files-on-android/#.T2-cdaJST3U
http://www.brighthub.com/mobile/google-android/articles/37151.aspx
also, have you ever had luck installing/pushing apk's. you may not have the correct environmental path on pc or are typing incorrect path in your command line
you can google environmental path editing for android and get examples of how to do it--i am not even sure mine is set right since I still have to type the full path in command window to use adb
sorry if this is old news just trying to find your problem

[Noob TUT]ADB - The Easy Way. 5 Seconds. Portable :)

I saw a lot of threads asking for instructions on how to use ADB to reboot into recovery, Push/Pull Files, etc, etc.
Just follow this guide to set up ADB in 5 seconds WITHOUT THE ANDROID SDK.
This ADB setup is less than one MB and no need to download the entire useless (for us, anyway) Android SDK.
1. Extract the Mini ADB archive attached below to any folder.
2. Just use the RunME.bat file to open a console directly in the ADB folder, so you can get started directly without the cd command!
To reboot into recovery:
Extract, Open RunMe.bat, type adb reboot recovery.
That easy.
Just make sure to have LG Phone Drivers installed beforehand.
Get Drivers here: Here

thanks mate ,, i never used adb when i get bootloops ,, i thought its complicated

rrgrrg said:
thanks mate ,, i never used adb when i get bootloops ,, i thought its complicated
Click to expand...
Click to collapse
Now you see how easy it is! Did you try it?
Its Super simple!

Does it work on any Android?
cm9 htc a310e

Yes.. It works when debugging is On.....
But how to get into recovery when we have bootloops or system force close

Type adb reboot recovery... it's in the op...
Sent from my LG-P970 using xda app-developers app

When you have bootloops:
Remove battery.
Re insert.
Connect phone to computer using USB.
Try to turn on phone, when bootanimation keeps looping,
run the runme.bat, type adb reboot recovery.
Done
And remember to press thanks
Sent from my LG-P970 using Tapatalk 2

thanks ykumar00 :good:

You can use adb also to install applications from your pc. I keep copies of my apks on windows machine - sending via usb and installing from phone is a tedious task (mounting usb, copying file, unmounting, waiting for sdcard scanning, navigating to apk file, installing). Just type:
adb install -r name.apk
USB debugging should be on.
I've created a batch and registry entry so I just make right click on apk and choose "install to sd" or "install to phone"

kretos said:
You can use adb also to install applications from your pc. I keep copies of my apks on windows machine - sending via usb and installing from phone is a tedious task (mounting usb, copying file, unmounting, waiting for sdcard scanning, navigating to apk file, installing). Just type:
adb install -r name.apk
USB debugging should be on.
I've created a batch and registry entry so I just make right click on apk and choose "install to sd" or "install to phone"
Click to expand...
Click to collapse
That's just one thing adb can do! Apart from reebooting normally and recovery, You can push/pull files to/from any folder, you can take logcats, and on ics, you can use adb to even take phone backups!

Also, could you share the bat and registry file? Looks interesting.

Sure, I'll post it here in the evening (in 4 hours)

Yup it would be really very useful and if someone has something to share related to adb please do so... it would be really very usefull for all ob users.
Sent from my LG-P970 using xda app-developers app

I could add it to the OP. With credits of course....

Ok, here you go:
the scripts assume that adb.exe is extracted to e:\MiniADB\
download attachments and remove .txt extension from them.
put scripts install.bat and install_tel.bat to e:\MiniADB and run (double click and confirm in Vista/W7/W8 to run as administrator) apk_install.reg.
After that you will get two options in context menu for apk files:
Install in phone
Install in SD card
First option will install application in phone's memory, second in sd card. If application is already installed, it will be overwritten.
If you wish to put MiniADB somewhere else you have to:
modify install.bat and install_tel.bat and replace e:\MiniADB\ with your path
modify apk_install.reg and replace e:\\MiniADB\\ with your path but remember to make all \ doubled \\
Example:
if you want to put MiniADB into c:\Android\MiniADB then replace e:\\MiniADB\\ with c:\\Android\\MiniADB\\ in a .reg file
Those scripts are for Windows only. I'm not sure if it works for Windows NT/9x as registry file format was changed as I remember.
Edit:
USB debugging must be on in a phone to adb work properly. Phone must be connected to computer
Sorry for delay

When trying adb, I am having this problem.
Sent from my LG-P970 using xda premium

vishaldhamnekar said:
When trying adb, I am having this problem.
Sent from my LG-P970 using xda premium
Click to expand...
Click to collapse
the command is "adb reboot recovery".

dcop7 said:
the command is "adb reboot recovery".
Click to expand...
Click to collapse
Ohhh sorry,my mistake. I didn't read it carefully.
And Thanks...

About flash CMW V20A

Hello,
I had posted this in Frequently Asked Questions about the LG Optimus 4x HD but got no help so I post here for a last try.
Just followed all dexter's steps in this thread to flash CMW
http://forum.xda-developers.com/showthread.php?t=2180138
but I got stuck here. Tried to read 34 pages of the thread but still couldnt solve my problem
My LG was rooted and unlocked.
Any help? thanks
Ekio

The error message says it all: no such file or directory. Change /mnt/sdcard/ to /storage/external_SD/

AlderCass said:
The error message says it all: no such file or directory. Change /mnt/sdcard/ to /storage/external_SD/
Click to expand...
Click to collapse
Tried and still not such files and directory thx anyway

ekiong said:
Tried and still not such files and directory thx anyway
Click to expand...
Click to collapse
Are u sure, u have copied the neede files to the root of ur SD-Card? Seems not... U have to unpack the zip-files for CWM and copy both files to the root of ur SD-Card... After that the commands should work...

Bogeyof said:
Are u sure, u have copied the neede files to the root of ur SD-Card? Seems not... U have to unpack the zip-files for CWM and copy both files to the root of ur SD-Card... After that the commands should work...
Click to expand...
Click to collapse
Omg I already did
Look pics

ekiong said:
Omg I already did
Look pics
Click to expand...
Click to collapse
I needed to allow SuperSU access before I be able to do it...
Pay attention to your phone, when you give the command "adb shell", if Superuser/SuperSU don't ask permition.
Its just a idea...

RuedasLocas said:
I needed to allow SuperSU access before I be able to do it...
Pay attention to your phone, when you give the command "adb shell", if Superuser/SuperSU don't ask permition.
Its just a idea...
Click to expand...
Click to collapse
I did it in recovery mode and tried it in terminal app aswell, but nothing happened with "cat /mnt/sdcard/recovery-6028.img >/dev/block/mmcblk0p1"

ekiong said:
Omg I already did
Look pics
Click to expand...
Click to collapse
Looks like the path to your SD card is different to mine. Try replacing /mnt/sdcard/ in the original command with /sdcard/ , ie:
Code:
su
cat /sdcard/recovery-6028.img >/dev/block/mmcblk0p1
sync
Code:
su
cat /sdcard/unsecure-boot-mmcblk0p2.img >/dev/block/mmcblk0p2
sync
Also no need to get aggravated, none of us are being rewarded for helping you here but we're trying to help anyway...
*edit*
ooops didn't look at all the screenshots. The last one shows your SD card path actually is indeed the same as mine. I'm all out of ideas then.
---------- Post added at 06:48 PM ---------- Previous post was at 06:40 PM ----------
ekiong said:
I did it in recovery mode and tried it in terminal app aswell, but nothing happened with "cat /mnt/sdcard/recovery-6028.img >/dev/block/mmcblk0p1"
Click to expand...
Click to collapse
Did you do it in recovery mode from the start? When I did it it was when the phone was just switched on normally into the main OS.

ekiong said:
I did it in recovery mode and tried it in terminal app aswell, but nothing happened with "cat /mnt/sdcard/recovery-6028.img >/dev/block/mmcblk0p1"
Click to expand...
Click to collapse
AlderCass said:
Looks like the path to your SD card is different to mine. Try replacing /mnt/sdcard/ in the original command with /sdcard/ , ie:
Code:
su
cat /sdcard/recovery-6028.img >/dev/block/mmcblk0p1
sync
Code:
su
cat /sdcard/unsecure-boot-mmcblk0p2.img >/dev/block/mmcblk0p2
sync
Also no need to get aggravated, none of us are being rewarded for helping you here but we're trying to help anyway...
*edit*
ooops didn't look at all the screenshots. The last one shows your SD card path actually is indeed the same as mine. I'm all out of ideas then.
Click to expand...
Click to collapse
Where the hell did you found that path /mnt/sdcard/....... ???

Tutorial CWM
Dude forget what they say everyone tells different way, read here what i writeto you and make the steps like me.
1. Unlock Bootloader and get SU Permissions
2. Go to PlayStore download SuperSU and than start give permisions to it to update Binary , than go to Setting in SuperSU and install in System
3. Reboot Phone
4. Copy the 2 IMG data to root from SD and rename recovery-6028.img > recovery.img & unsecure-boot-mmcblk0p2.img > boot.img
this to IMG data must be unpacked from RAR(Zip) from Dexter.
5. make sure you have Unknow Sources and USB Debug Active , and also make sure that Superuser is replaced by SuperSU after reboot
6. Go to PlayStore and Download Android Terminal Emulator
and give in Terminal
Type "su" without quotes and than accept the permissions from SuperSU after that give in
----------------------------------------------------------------------------------------------------------------------------------
cat /mnt/sdcard/recovery.img >/dev/block/mmcblk0p1
sync
IF YOU USE UNSECURE BOOT tha use this
su
cat /mnt/sdcard/boot.img >/dev/block/mmcblk0p2
sync
Hope it helps and youv got it run :laugh:

RuedasLocas said:
Where the hell did you found that path /mnt/sdcard/....... ???
Click to expand...
Click to collapse
It's in the system root for me, it's a symlink. Though it didn't work for me in the cat command, which is why I suggested using /storage/external_SD/ instead which did work for me. It looks like the OP has the files in the right places, and the hash in the command line screenshot implies that SU is working correctly, so I'm all out of ideas now.
---------- Post added at 06:57 PM ---------- Previous post was at 06:55 PM ----------
x0BlackTeresis0x said:
Dude forget what they say everyone tells different way, read here what i writeto you and make the steps like me.
Click to expand...
Click to collapse
Little bit arrogant, we're all trying to help here, so I hope for your sake your way works for the OP

AlderCass said:
Looks like the path to your SD card is different to mine. Try replacing /mnt/sdcard/ in the original command with /sdcard/
Also no need to get aggravated, none of us are being rewarded for helping you here but we're trying to help anyway...
Click to expand...
Click to collapse
Sorry man, just had a bad feeling .
--------------------------------------------------------------------------
x0BlackTeresis0x said:
Dude forget what they say everyone tells different way, read here what i writeto you and make the steps like me.
1. Unlock Bootloader and get SU Permissions
2. Go to PlayStore download SuperSU and than start give permisions to it to update Binary , than go to Setting in SuperSU and install in System
3. Reboot Phone
4. Copy the 2 IMG data to root from SD and rename recovery-6028.img > recovery.img & unsecure-boot-mmcblk0p2.img > boot.img
this to IMG data must be unpacked from RAR(Zip) from Dexter.
5. make sure you have Unknow Sources and USB Debug Active , and also make sure that Superuser is replaced by SuperSU after reboot
6. Go to PlayStore and Download Android Terminal Emulator
and give in Terminal
Type "su" without quotes and than accept the permissions from SuperSU after that give in
----------------------------------------------------------------------------------------------------------------------------------
cat /mnt/sdcard/recovery.img >/dev/block/mmcblk0p1
sync
IF YOU USE UNSECURE BOOT tha use this
su
cat /mnt/sdcard/boot.img >/dev/block/mmcblk0p2
sync
Hope it helps and youv got it run :laugh:
Click to expand...
Click to collapse
Tried and looked like I'm typing in word lol, nothing happen, still android system recovery, not CMW.
Need CWM to wipe battery status, battery goes down to 93% in 1 min after full chagring.

ekiong said:
Sorry man, just had a bad feeling .
--------------------------------------------------------------------------
Tried and looked like I'm typing in word lol, nothing happen, still android system recovery, not CMW.
Need CWM to wipe battery status, battery goes down to 93% in 1 min after full chagring.
Click to expand...
Click to collapse
Remove micro sd from the phone.
Stick to the guide, pay atention to the phone screen behavior soo, keep the screen always on, in case of SuperSU ask for permition...
Dexter_nlb said:
......
GUIDE:
1. when you are running unlocked bootloader and is rooted goto step 2.
2. download attached zip files and extract content to internal sdcard location
3. use adb shell or terminal from market and execute the commands below
4. you are now running with native CWM recovery and unsecure boot, which enable adb root at boot instantly.
5. boot into recovery, by rebooting device and hold VOL-DOWN during bootup. (from power-off = keep holding vol-down during power on)
execute these 3 commands for recovery image install
Code:
su
cat /mnt/sdcard/recovery-6028.img >/dev/block/mmcblk0p1
sync
execute these 3 commands for unsecure boot image install
Code:
su
cat /mnt/sdcard/unsecure-boot-mmcblk0p2.img >/dev/block/mmcblk0p2
sync
or see screenshot here
do this at your own risk, and do NOT try this on old 4.0.3, which is not with unlocked bootloader, and you are required to install KDZ again.
THANKS to:
skydev - for his continued effort in finding root and giving our device full freedom with boot/recovery.
Click to expand...
Click to collapse
Copy and past the command lines from the post, like that you'll be sure that you don't miss write the path.
And like I use to say, be creative
Good luck !

RuedasLocas said:
Remove micro sd from the phone.
Stick to the guide, pay atention to the phone screen behavior soo, keep the screen always on, in case of SuperSU ask for permition...
Copy and past the command lines from the post, like that you'll be sure that you don't miss write the path.
And like I use to say, be creative
Good luck !
Click to expand...
Click to collapse
Still no such file, I give up :angel:
Thx every one

ekiong said:
Still no such file, I give up :angel:
Thx every one
Click to expand...
Click to collapse
You tried this? Only the path changes, but... I ran out of ideas.
Like I told you, be creative. Change /sdcard/ to /sdcard0/... don't know man...
"01. You must have Root access (https://mega.co.nz/#!0opzyBjS!DSoW-CaTRi49JcW58yvwCCEug4hz6VmnevdJ1prcdpE)
02. Extract both *.img files somewhere
03. Copy those files to your phone (no matter if internal or external storage, I used /sdcard/Unlocking/ so below commands will contains my directory)
04. Run terminal app on your phone or adb shell from PC while you have connected phone
05. Run those commands:
su
cat /sdcard/recovery-6028.img >/dev/block/mmcblk0p1
sync
su
cat /sdcard/unsecure-boot-mmcblk0p2.img >/dev/block/mmcblk0p1
sync
REMEMBER!
If your folder is different than /sdcard replace it in those commands above!
Methods and necessary files are found also here: http://forum.xda-developers.com/showthread.php?t=2180138
All credits goes to Dexter_nlb from xda community."

RuedasLocas said:
You tried this? Only the path changes, but... I ran out of ideas.
Like I told you, be creative. Change /sdcard/ to /sdcard0/... don't know man...
"01. You must have Root access (https://mega.co.nz/#!0opzyBjS!DSoW-CaTRi49JcW58yvwCCEug4hz6VmnevdJ1prcdpE)
02. Extract both *.img files somewhere
03. Copy those files to your phone (no matter if internal or external storage, I used /sdcard/Unlocking/ so below commands will contains my directory)
04. Run terminal app on your phone or adb shell from PC while you have connected phone
05. Run those commands:
su
cat /sdcard/recovery-6028.img >/dev/block/mmcblk0p1
sync
su
cat /sdcard/unsecure-boot-mmcblk0p2.img >/dev/block/mmcblk0p1
sync
REMEMBER!
If your folder is different than /sdcard replace it in those commands above!
Methods and necessary files are found also here: http://forum.xda-developers.com/showthread.php?t=2180138
All credits goes to Dexter_nlb from xda community."
Click to expand...
Click to collapse
OH MY GOD I'm stupid, I copied files with ZERO byte.
sorry I used airdroid to copy them to my phone. But only their icons moved into my phone, not contents.
It works now THANKSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS :laugh:
Close thread and my stupid problem :silly: