Database Users

[TOOLS][ADB][Windows]Push files to device through ADB*now include deodex tools*

See my previous post before in post#2
This is a simple batch file using ADB..
With this you can use ADB to manage your file or APK , Backup, Push Your File to device, or pull file from device..
ADB Work on Stand by Mode (Home Screen) or in Recovery Mode, just set it up..
Extract ADBTOOLSv1.0.1.zip and you will find :
command.bat : Windows Batch Command
_BACKUP_OUT : folder where your backup process done and made
_FLASHING_OUT:
folder for flashing your :
kernel (place your boot.img here)
recovery (place your recovery.img here),
modem (place your modem.bin here)--only for gt p7300
_MODDING_FILE: Folder where your file were created by PULL process
Folder where file for PUSH process should be here
_BATCH_INSTALL : place your APK here for batch install
tools: ADB.exe and busybox binary
success_APK : A folder created for All apk from _BATCH_INSTALL move here after instalation.
Click to expand...
Click to collapse
Notes:
ADB can access all file from device from CWM Recovery, especially CWMR 5.5.0.4
ALL you need to do is:
From Recovery menu, you need to mount /data and /system for ADB working..
THEN, From Command Prompt set ADB Mode to "recovery".(This Batch File set ADB mode to "Home Screen" by default)
So when you use ADB from Online device ( I mean a stand by device).. you dont need to change ADB Mode..
After you set up, you can use ADB as you like..
Code:
=============================================================================
:::: ADB TOOLS FOR GT P7300 and P7310 by suwandiapr
-----------------------------------------------------------------------------
| [*] Before use read this:
| --make sure you have installed adb drivers for your device
| --enable "USB DEBUGGING"
| from (Menu\Settings\Applications\Development)
| --enable "UNKNOWN SOURCES"
| from (Menu\Settings\Applications)
| --increase screen timeout to 10 minutes
| --connect USB cable to PHONE and then connect to PC
| --MAKE SURE YOU HAVE A ROOTED DEVICE AND BUSYBOX
| --Place the right file in the right folder
| --Some feature like Flashing need more tester..so please be aware
| --If you use adb recovery feature, set ADB Mode to recovery
| mount /data and /system from your device recovery
| --If you use adb from homescreen, set ADB Mode to HomeScreen
| --All you Do is your own Risk, use with carefull
-----------------------------------------------------------------------------
****Turn on the screen and allow superuser permission when asked!****
_____________________________________________________________________________
| Current MODDING FILE: NONE | ADB MODE :HomeScreen | sdcard path: /sdcard/|
=============================================================================
:::: ADB PULL ::::
=============================================================================
0 Pulling file from /data ( see result in _MODDING_FILE)
1 Pulling file from /system partition ( see result in _MODDING_FILE)
2 Pulling file from SDcard ( see result in _MODDING_FILE)
3 Backup recovery ( see result in _BACKUP_OUT)
4 Backup Kernel ( see result in _BACKUP_OUT)
5 Backup modem (for P7300 only-see result in _BACKUP_OUT)
6 Backup /system (tar format-see result in _BACKUP_OUT)
7 Backup /efs (tar and .img format-see result in _BACKUP_OUT)
8 Backup APK from /data/app (tar format-see result in _BACKUP_OUT)
=============================================================================
:::: ADB PUSH ::::
=============================================================================
9 Pushing file to /data ( from _MODDING_FILE to device)
10 Pushing file to /system ( from _MODDING_FILE to device)
11 Flashing recovery ( from _FLASHING_OUT to device)
12 Flashing Kernel ( from _FLASHING_OUT to device)
13 Flashing modem for GT P7300 ( from _FLASHING_OUT to device)
=============================================================================
:::: Setting ::::
=============================================================================
14 Set current working File ( for PUSH and PULL )
15 Install busybox on device (need root)
16 Set ADB mode (if you on recovery mode)
17 Install apk ( from _MODDING_FILE to device)
18 Install batch apk ( from _BATCH_INSTALL to device)
=============================================================================
:::: Reboot Menu ::::
=============================================================================
19 Reboot System
20 Boot Into Recovery
21 Reboot Bootloader
22 Quit

My previous post
inspiration from congox case
when you got a problem with bootlop and you forget make a nandroid backup
only have file from other ROM with flashable.zip and need to push the file from your computer to device
you have a recovery support with mount /system and mount /data (tested on CWM 5.5.0.4 and overcome CWM 5.1.2.6) and you can enter this menu while bootloop happen..
STEP 1 : MANUAL
Connect your device with computer
From device, Go to recovery - mounts and storage - mount /system and mount /data
From your computer go to adb terminal and type this
Code:
adb shell "ls /data/media/"
If you can see list of file from your device sdcard, so you make adb work for your device ..
Place your zip file on your path, says on C://backup.zip and you want to copy the file to /sdcard/download/ and type this code
Code:
adb push backup.zip /data/media/download/.
wait for copying progress done..
After you done with moving file to device sdcard, check content of your sdcard with this code
Code:
adb shell "ls /data/media/download/"
When you found your file from list, you can flash backup.zip from recovery
STEP 2 : WINDOWS BATCH FILE
I made a simple Batch File for windows (sorry i dont have MAC or LINUX distro) , this file will make a folder with name "emergency" in SDCARD and with your files inside that.
Extract the FLASHER.rar somewhere on your Local folder,example: on your " Desktop" Folder
in folder "FLASHER" you will find runme.bat and folder "files"
Rename your file ((flashable.zip files you want to send through ADB) to "backup.zip" and then Put your file into this path /FLASHER/files/myfiles/ (just replace the existing "backup.zip" with files from yours)
Connect your tab with Computer
Reboot into Recovery Menu from your device
From menu Mounts and Storage choose mount /system and /data
From your Computer go To Folder flasher and klik runme.bat
Follow the instruction on window untill copying process done and device reboot to recovery again (copying process will take a minutes depend on your file size)
Now you can flash a emergency ROM from recovery
Window instruction
Code:
-----------------------------------------------------------------------------
ADB EMERGENCY COPYING TOOL for TAB 8,9
created by SUWANDIAPR
-----------------------------------------------------------------------------
[*] This script will:
(1) COPY YOUR FILE FROM COMPUTER TO SDCARD/emergency/*
(2) CHECKING YOUR CONNECTED DEVICE DIRECTORY
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) make sure u have installed CWM 5.5.0.4 ON YOUR DEVICE
(3) connect USB cable to PHONE and then connect to PC
(4) Rename your Flashable .zip file with "backup.zip"
and place inside "myfiles" folder on your Computer
(5) from Recovery Menu, Choose "Mounts and storage" then
-mount /system and -mount /data
(6) CONNECT YOUR TAB WITH PC WHILE ON RECOVERY MENU
---------------------------------------------------------------
CONFIRM ALL ABOVE
Sorry for my Bad english, if there is somebody want to correct every words i use , im very welcome and will change with the proper words and sentence..
Hope this help someone..

Nice guide, thanks!!

I needed some help with mounting the system using adb through a batch file.
I use this command
adb -d shell mount -o remount rw /system
But the mounting fails (I have a rooted phone )
pleas help me I know this is off topic

2 possible reasons for this command to fail:
- /default.prop (on the phone) contains the following line: "ro.secure=1". Then you need another boot.img (in fact just a modified ramdisk). look for "unpack-bootimg.pl" or "unpackbootimage" you may find a guide how to do this manually (not too easy). A rooted kernel would also do the trick.
you can check your default prob with this command "adb shell cat /default.prop".
- in some cases mount requires more parameters. try "adb shell mount" and look for the line containing "/system". In front of system is the "device-name". in my case the mount command would look like this:
mount -o remount,rw /block/dev/mmcblk0p24 /system
hope this helps and sorry for answering off-topic questions....

nail16 said:
I needed some help with mounting the system using adb through a batch file.
I use this command
adb -d shell mount -o remount rw /system
But the mounting fails (I have a rooted phone )
pleas help me I know this is off topic
Click to expand...
Click to collapse
you can use busybox and call the binary from the shell
i assume that your device in normal mode ( in home screen)..
here some example..
Code:
su
adb push busybox /tmp/.
adb shell "chmod 755 /tmp/busybox"
adb shell "tmp/busybox mount -o remount,rw /system"
after you type "su" superuser will prompt a request, choose "allow".
glitschi667 said:
2 possible reasons for this command to fail:
- /default.prop (on the phone) contains the following line: "ro.secure=1". Then you need another boot.img (in fact just a modified ramdisk). look for "unpack-bootimg.pl" or "unpackbootimage" you may find a guide how to do this manually (not too easy). A rooted kernel would also do the trick.
you can check your default prob with this command "adb shell cat /default.prop".
- in some cases mount requires more parameters. try "adb shell mount" and look for the line containing "/system". In front of system is the "device-name". in my case the mount command would look like this:
mount -o remount,rw /block/dev/mmcblk0p24 /system
hope this helps and sorry for answering off-topic questions....
Click to expand...
Click to collapse
yes you right glistchi, samsung lock adb root on new firmware on my SG- Note..
And make me flash an older firmware for rooting..

new update

Never mind, got it to work

i want to push same file in data system (/data/data) but my tab is not root. can i??

if from cwm recovery, yes you can.. if from stand by mode (home screen) the answer is no... you need root to make it happen..

i got this error
please help

help please

i format my Nexus 4 on twrp recovery using advance wipe and i checked all the box there, and when i rebooted its stuck on google logo, what should i do?

Well why would you do that? If you selected everything under advanced in twrp, that means that you have also wiped the system partition so there is no rom to boot into, hence why you are stuck at the google logo. You will need to use adb to copy a rom onto your phone, and then flash it via twrp. Instructions:
1. Setup adb: http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
2. Install Koush's universal adb driver (google this for the download)
3. Put the phone into twrp
4. Download a rom on your pc and move it to your desktop. Rename it to "rom.zip".
5. Open a command prompt window and run the following commands:
Code:
adb devices
If your phones serial number shows up, continue. If not, reinstall drivers.
Code:
cd Desktop
adb push rom.zip /sdcard/
6. After its finished pushing, go to install within twrp and flash it.

when i typed in cd desktop it says "The system cannot find the path specified". and when i continue to adb push rom.zip /sdcard/ it says "cannot stat rom.zip: no such file or directory"

it worked, thanks for your help.

I hope you realized when you checked all the boxes, you checked to wipe the internal storage which holds all your personal data.
And you checked to wipe /system partition which house the operating system, of course there wouldn't be anything to boot into.
sent from xda premium app

[Q] How do I push zip file from PC to tablet in TWRP?

I did something stupid and I am embarrassed to say I don't know how to get out of it.
I didn't back up my ROM, and I ended up wiping everything. I lost the zip file that I had and now I can't flash it. I am unable to use TWRP's menu to mount the USB. The only option I see mount USB-OTG but it says unable to mount. How do I mount and transfer the zip file? I guess I have to use adb. But I am unable to get it to work. I've tried:
adb push update.zip
after setting the recovery in sideload mode, but nothing happens.
EDIT: never mind. I figured it out. For anyone else, here is what I did:
1) download adb 1.08
2) Put the zip file in the same folder as the adb.exe
3) Run adb usb
4) Do NOT put the tablet in sideload mode. Do nothing there. In fact I rebooted back into recovery.
5) Run adb push <name of zip file> /sdcard/
Nothing will appear to happen for a minute or so. Then you'll get a line to the tune of <kb> in <s> or something. That means it pushed the file to /sdcard/

[GUIDE][ROOT]How to install TWRP and ROOT your X507, X509 (PC Guide)

Okay, I have seen many people using the unofficial TWRP on their device, and that's a little dangerous because it may be malicious, and you might not even know that.
I am not saying it is, but it can be.
Now, back to the topic here,
HOW TO INSTALL TWRP[2] AND GET ROOT ACCESS[3] and more​Here goes..
Before anything, you need to get ADB and FASTBOOT programs on your PC and get your drivers installed so you can communicate with the device through your computer.
To Download ADB and fastboot program, you can download this file (not my upload)
Extract it anywhere you want(and remember that location).
(lets say "C:\workspace\ADB" and I will use this path for this guide).​Typically, the driver for ADB will install the first time you connect your device to your computer and:
Internet is available
USB Debugging is enabled on your phone
But the FASTBOOT driver would probably not be available yet. to get fastboot drivers, follow these steps:
Turn on and Unlock your device and connect it to PC via the USB cable.
Open CMD and execute "cd C:\workspace\ADB".(or you can open C:\workspace\ADB in file explorer and type CMD in the address bar to open CMD directly there.
Type "adb devices".
Now, your phone will ask something(permission to allow ADB access on the connected PC)allow it. After you allow it, the CMD will show a list of attached devices and the mode they are attached in, your device should show "device" for now.
If it does not, there is some problem, search on internet or ask for help here
Now type "adb reboot bootloader".
now your Phone will shutdown and open in a different state. It will say Fastboot on the screen.
Now the driver is installing or is already installed, to check, type this:
"adb devices" and it should show a list and your device's mode should change to "fastboot".
That's it for the ADB and FASTBOOT. You have the necessary things to continue.
Continue to next post for TWRP and the post next to it for ROOT ACCESS.

Now, we will talk about how to install TWRP​
@DroidThug has been kind enough to get Official support of TWRP for this device.
Head over to this thread to download the official image file of the TWRP Recovery and keep it on your computer, this is the very first step you need to take.
Here is the thread: https://forum.xda-developers.com/leeco-le-1s/development/official-twrp-t3527566
If you are lazy enough to go through the thread, which i suggest you to visit, here is the direct link to the download page: https://dl.twrp.me/x3/
And here is the direct download link of the v3.0.3(latest as of 31st Jan, 2017): https://dl.twrp.me/x3/twrp-3.0.3-0-x3.img
Once you have the recovery image, you need to flash it through fastboot.
If you are following this guide from start, you should already be in fastboot and have CMD open on your PC in adb folder.
Now, a few things you might want to follow strictly if you are unsure how to do it:
Copy the recovery image file to "C:\workspace\ADB" (adb folder).
Rename that file to "twrp.img"
Now you need to execute this command from CMD to flash the file:
"fastboot flash recovery twrp.img" and press enter.
This will take a few seconds and will will be over soon.
Now you need to reboot directly into RECOVERY, because if you will boot to the system first, the Device will replace your newly flashed recovery with the stock recovery and all this will be wasted. But if you reboot to recovery first, it will patch those things up and will stay.
So, to reboot to recovery, you need to use the key combo to get into the recovery,
Press and hold "Volume UP" and "Power" Buttons till the screen goes off(from fastboot mode) and is lit up again and then leave the power key and 2-3 seconds later, leave the Volume key too.
You will enter into recovery mode and it will ask you "if you want to keep the System partition to read only or not?"
I'd recommend keeping it to read only unless you know what you are doing.
There you have it!
You have successfully installed TWRP on your device!

GET ROOT ACCESS​
Okay, So you have the RECOVERY installed already
Now go to this page and download the latest "Recovery Flashable ZIP" from there. (Here is the latest one as on 31st Jan, 2017).
You can do this in two ways through Phone(with TWRP already present) and through PC.
Through Phone​All you need to do is flash it through the recovery and thats it, you will have root access!
Here are the steps to flash ZIPs from Recovery:
Get the zip file you want to flash(the one downloaded above) and place it somewhere in the Phone's internal storage.
Reboot to recovery(Power off and then hold "Vol UP" and "Power" keys till the screen is lit up.).
Tap on "Install".
Navigate to the ZIP file you placed in your phone's internal storage.
Select it and swipe to flash it.
The last step might take a few seconds and will be done then.
After its done, that't it!
Reboot to system and you have ROOT ACCESS!
Through PC​Okay, you would still need to reboot to recovery, but you can follow this guide if you don't want to copy the zip file on your phone for whatever reason you may have.
Here are the steps:
Enter recovery.
Select "Advanced->ADB Sideload" and swipe to start sideload.
Now connect your phone to PC.
Now open CMD in ADB folder.
Check if your device is detected by typing "adb devices". It should show a device with sideload state.
Now type "adb sideload " and drag the zip file into the cmd window.
OR
you can copy the zip to the adb folder and rename it to supersu.zip and write "adb sideload supersu.zip" in the CMD.
Now Press enter.
After this, in a few seconds, it will be over and you can reboot to system(it might automatically reboot to system too).
And that's it! There you have it!
You have ROOT ACCESS on your device!

5. Now the driver is installing or is already installed, to check, type this:
"adb devices" and it should show a list and your device's mode should change to "fastboot".
Click to expand...
Click to collapse
If the phone is on fastboot mode, "adb devices" supposed to not give any output. "fastboot devices" will show the device and mode as fastboot.
You will enter into recovery mode and it will ask you "if you want to keep the System partition to read only or not?"
I'd recommend keeping it to read only unless you know what you are doing.
Click to expand...
Click to collapse
My screen is broken (that's only white light and no digitiser). I dont have any other Le 1S to get idea.
1. Are you sure Vol Up + Power will enter into Recovery? Mine is 5.5.014S.
2. I want to make my system partition as writable. Can you tell how to achieve with hardware keys like Vol Up or down & power.
3. After step 2. Can I flash SuperSu from PC without enabling sideload. While on custom recovery , "adb devices" will show mode as recovery. So flashing supersu from here. Not sure if this is correct. On my Moto G falcon. whenever I go into TWRP, adb recovery and MTP works.
Also can you check whats the combination Vol Up+Vol Dn+Power. When it starts I can connect to adb but all partitions are read only and not allowing to make any change to device. Not sure if its due to encryption.
C:\Users\Mkn\Downloads\Le1s drivers\minimal_adb_fastboot_1.4.1_portable>adb devices
List of devices attached
0123456789ABCDEF device
C:\Users\Mkn\Downloads\Le1s drivers\minimal_adb_fastboot_1.4.1_portable>adb shell
[email protected]_HK:/ $ cat /data/misc/adb/adb_keys
/system/bin/sh: cat: /data/misc/adb/adb_keys: Permission denied
1|[email protected]_HK:/ $ id
uid=2000(shell) gid=2000(shell) groups=1003(graphics),1004(input),1007(log),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats) context=u:r:shell:s0
[email protected]_HK:/ $ su
/system/bin/sh: su: not found
[email protected]_HK:/ $ cd
[email protected]_HK:/data $ pwd
/data
[email protected]_HK:/ $ exit
C:\Users\Mkn\Downloads\Le1s drivers\minimal_adb_fastboot_1.4.1_portable>adb reboot bootloader
C:\Users\Mkn\Downloads\Le1s drivers\minimal_adb_fastboot_1.4.1_portable>fastboot devices
0123456789ABCDEF fastboot
**
C:\Users\Mkn\Downloads\Le1s drivers\minimal_adb_fastboot_1.4.1_portable>adb devices
List of devices attached
0123456789ABCDEF device
C:\Users\Mkn\Downloads\Le1s drivers\minimal_adb_fastboot_1.4.1_portable>adb install mirror.apk
[100%] /data/local/tmp/mirror.apk
Error: java.lang.NullPointerException: Attempt to invoke interface method 'android.os.IBinder android.os.IServiceManager.getService(java.lang.String)' on a null object reference
C:\Users\Mkn\Downloads\Le1s drivers\minimal_adb_fastboot_1.4.1_portable>adb shell am start -n com.android.settings/.wifi.WifiSettings
java.lang.NullPointerException: Attempt to invoke interface method 'android.os.IBinder android.os.IServiceManager.getService(java.lang.String)' on a null object reference
at android.os.ServiceManager.getService(ServiceManager.java:55)
at android.app.ActivityManagerNative$1.create(ActivityManagerNative.java:2494)
at android.app.ActivityManagerNative$1.create(ActivityManagerNative.java:2492)
at android.util.Singleton.get(Singleton.java:34)
at android.app.ActivityManagerNative.getDefault(ActivityManagerNative.java:88)
at com.android.commands.am.Am.onRun(Am.java:295)
at com.android.internal.os.BaseCommand.run(BaseCommand.java:47)
at com.android.commands.am.Am.main(Am.java:99)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:250)
C:\Users\Mkn\Downloads\Le1s drivers\minimal_adb_fastboot_1.4.1_portable>adb shell dumpsys wifi
adb shell dumpsys wifi^C
C:\Users\Mkn\Downloads\Le1s drivers\minimal_adb_fastboot_1.4.1_portable>adb shell
[email protected]_HK:/ $ ls -ld sdcard
lrwxrwxrwx root root 2017-03-21 11:12 sdcard -> /storage/sdcard0
[email protected]_HK:/ $ cd /storage/sdcard0
/system/bin/sh: cd: /storage/sdcard0: Permission denied
2|[email protected]_HK:/ $ ls -ld
drwxr-xr-x root root 2017-03-21 11:12 .
[email protected]_HK:/ $ ls -ld /storage/sdcard0
d--------- system system 2017-03-21 11:12 sdcard0
[email protected]_HK:/ $
Update:
I some how managed to side load. My Phone got bootlop after installing twrp. Then flashed userdata by following http://forum.le.com/in/index.php?th...op-restart-solution-letv-le1s-x507-x509.1155/ . Now its factory reset as I can see the screenshot from PC.
Still interested in knowing what's that Vol Up+Vol Down + Power.

If any one have le 1s related problem and solution or any one want to try new rom or kernal asap then all of u are welcome in our group on telegram so plz join with us
Requriemt
1. Download telegram from play store
2. Just click below link
https://telegram.me/LeSuperGroup
Thanks all of u

Need help with ADB trough recovery

Hello guys and gals,
my wife managed to break her screen on the SM-G900F Model from germany and she got her a new phone. The problem is now that she has some data on the phone she needs (like the google e-mail what she has forgotten the name of) and some other stuff. I want to enable usb debugging over recovery and mirror the screen on my pc (i did that once on my old Galaxy S3 Neo).
I was searching on this forums for a sollution to enable usb debugging over recovery https://forum.xda-developers.com/showthread.php?t=2697523.
I managed to flash the recovery, but adb still does not recognise the phone while in recovery mode. I am running out of options and i really need help of some dev to decompile the kernel, edit the init-rc, and to recompile the kernel, so i could flash it on the phone. I was looking at some guides, but i just don't get it how to do that
Click to expand...
Click to collapse
It would help if someone has some user friendly guide to do that, so i would try that on my own.
I hope there is someone who can help me.
Stock Rom version: G900FXXS1CPLV_G900FDBT1CPJ1_G900FXXU1CPJ1_HOME.tar.md5
Click to expand...
Click to collapse

Hi,
Why not using latest TWRP custom recovery instead of trying old/outdated and not officially supported CWM?
I have no problem with accessing to ADB from latest TWRP.

TomyVk said:
Hello guys and gals,
my wife managed to break her screen on the SM-G900F Model from germany and she got her a new phone. The problem is now that she has some data on the phone she needs (like the google e-mail what she has forgotten the name of) and some other stuff. I want to enable usb debugging over recovery and mirror the screen on my pc (i did that once on my old Galaxy S3 Neo).
I was searching on this forums for a sollution to enable usb debugging over recovery https://forum.xda-developers.com/showthread.php?t=2697523.
It would help if someone has some user friendly guide to do that, so i would try that on my own.
I hope there is someone who can help me.
Click to expand...
Click to collapse
Boot to TWRP recovery
Then enter these commands in a terminal/cmd window on pc
If you're not rooted leave out the su from below - think it should still work
Assuming you have Samsung USB drivers & adb setup on pc
Code:
adb shell
su
mount -o remount,rw /system
cd /
echo "persist.service.adb.enable=1" >> default.prop
echo "persist.service.debuggable=1" >> default.prop
echo "persist.sys.usb.config=mtp,adb" >> default.prop
echo "persist.service.adb.enable=1" >> /system/build.prop
echo "persist.service.debuggable=1" >> /system/build.prop
echo "persist.sys.usb.config=mtp,adb" >> /system/build.prop
This will enable adb but you still may face unauthorized as you get a prompt on phone screen to allow adb & to accept connection - you maybe able to manually send the rsa key but you will have to Google that if you face that problem - it will depend on Android version
ADB should be enabled in latest twrp recovery so pull the build.prop edit it then push it back setting correct permissions
However if you are simply copying files just enter twrp & you will be able to see all your phone files via USB connection on your pc
Obviously with Google email you would need to boot the phone so try the above to enable adb debugging in normal boot

TheFixItMan said:
Boot to TWRP recovery
Then enter these commands in a terminal/cmd window on pc
If you're not rooted leave out the su from below - think it should still work
Assuming you have Samsung USB drivers & adb setup on pc
Code:
adb shell
su
mount -o remount,rw /system
cd /
echo "persist.service.adb.enable=1" >> default.prop
echo "persist.service.debuggable=1" >> default.prop
echo "persist.sys.usb.config=mtp,adb" >> default.prop
echo "persist.service.adb.enable=1" >> /system/build.prop
echo "persist.service.debuggable=1" >> /system/build.prop
echo "persist.sys.usb.config=mtp,adb" >> /system/build.prop
This will enable adb but you still may face unauthorized as you get a prompt on phone screen to allow adb & to accept connection - you maybe able to manually send the rsa key but you will have to Google that if you face that problem - it will depend on Android version
ADB should be enabled in latest twrp recovery so pull the build.prop edit it then push it back setting correct permissions
However if you are simply copying files just enter twrp & you will be able to see all your phone files via USB connection on your pc
Obviously with Google email you would need to boot the phone so try the above to enable adb debugging in normal boot
Click to expand...
Click to collapse
Well, i have flashed the latest twrp recovery twrp-3.2.3-0-klte.img.tar over odin. It flashed without problems.
But the same problem persists, when i boot in to recovery mode adb does not recognise th phone in recovery mode.
When i type adb shell i just get a "error: device not found" from adb
I have installed the newest samsung drivers over Kies3.

TomyVk said:
Well, i have flashed the latest twrp recovery twrp-3.2.3-0-klte.img.tar over odin. It flashed without problems.
But the same problem persists, when i boot in to recovery mode adb does not recognise th phone in recovery mode.
When i type adb shell i just get a "error: device not found" from adb
I have installed the newest samsung drivers over Kies3.
Click to expand...
Click to collapse
How do you know twrp booted if you can't see the screen?
TWRP will have adb support so as long as twrp booted it will work
Once you have flashed twrp in odin you must boot into twrp as soon as the phone restarts for twrp to stick - if you switched the device off or the phone booted normally you will have to reflash twrp - if you can't see the screen that maybe an issue

TheFixItMan said:
How do you know twrp booted if you can't see the screen?
TWRP will have adb support so as long as twrp booted it will work
Once you have flashed twrp in odin you must boot into twrp as soon as the phone restarts for twrp to stick - if you switched the device off or the phone booted normally you will have to reflash twrp - if you can't see the screen that maybe an issue
Click to expand...
Click to collapse
Oh, that might be the problem. What do i have to do after the flashing to boot in to twrp?
The same key combination as for the recovery mode or something else, or do i just disable automatic reboot in odin?

TheFixItMan said:
How do you know twrp booted if you can't see the screen?
TWRP will have adb support so as long as twrp booted it will work
Once you have flashed twrp in odin you must boot into twrp as soon as the phone restarts for twrp to stick - if you switched the device off or the phone booted normally you will have to reflash twrp - if you can't see the screen that maybe an issue
Click to expand...
Click to collapse
TomyVk said:
Oh, that might be the problem. What do i have to do after the flashing to boot in to twrp?
The same key combination as for the recovery mode or something else, or do i just disable automatic reboot in odin?
Click to expand...
Click to collapse
As soon as the device restarts & the Samsung logo appears (that you can't see) hold Vol up home button & power button
Can try disabling auto restart then pull the battery after flash & then hold the button combo to start

TheFixItMan said:
As soon as the device restarts & the Samsung logo appears (that you can't see) hold Vol up home button & power button
Can try disabling auto restart then pull the battery after flash & then hold the button combo to start
Click to expand...
Click to collapse
Thank you, it worked. I will now try to enable the usb debugging

TheFixItMan said:
Boot to TWRP recovery
Then enter these commands in a terminal/cmd window on pc
If you're not rooted leave out the su from below - think it should still work
Assuming you have Samsung USB drivers & adb setup on pc
Code:
adb shell
su
mount -o remount,rw /system
cd /
echo "persist.service.adb.enable=1" >> default.prop
echo "persist.service.debuggable=1" >> default.prop
echo "persist.sys.usb.config=mtp,adb" >> default.prop
echo "persist.service.adb.enable=1" >> /system/build.prop
echo "persist.service.debuggable=1" >> /system/build.prop
echo "persist.sys.usb.config=mtp,adb" >> /system/build.prop
This will enable adb but you still may face unauthorized as you get a prompt on phone screen to allow adb & to accept connection - you maybe able to manually send the rsa key but you will have to Google that if you face that problem - it will depend on Android version
ADB should be enabled in latest twrp recovery so pull the build.prop edit it then push it back setting correct permissions
However if you are simply copying files just enter twrp & you will be able to see all your phone files via USB connection on your pc
Obviously with Google email you would need to boot the phone so try the above to enable adb debugging in normal boot
Click to expand...
Click to collapse
When i try to mount the system partition i just get this:
mount -o remount,rw /system
mount: can't find /system in /proc/mounts

TomyVk said:
When i try to mount the system partition i just get this:
mount -o remount,rw /system
mount: can't find /system in /proc/mounts
Click to expand...
Click to collapse
You might have a problem of when twrp starts it asks you to swipe to allow system modifications but you can't see that
See if are able to do an adb screen cast that allows you to control the screen via adb then you can fully get into twrp
Or see if you can simply pull the build.prop & default.prop to pc & edit it & push it back

TheFixItMan said:
You might have a problem of when twrp starts it asks you to swipe to allow system modifications but you can't see that
See if are able to do an adb screen cast that allows you to control the screen via adb then you can fully get into twrp
Or see if you can simply pull the build.prop & default.prop to pc & edit it & push it back
Click to expand...
Click to collapse
When i type ls in the shell i get this
Code:
ls
boot init.rc sdcard
cache init.recovery.hlthchrg.rc seapp_contexts
charger init.recovery.qcom.rc selinux_version
data init.recovery.service.rc sepolicy
default.prop init.recovery.usb.rc service_contexts
dev license sideload
efs modem sys
etc oem system
external_sd proc tmp
file_contexts property_contexts twres
file_contexts.bak recovery ueventd.qcom.rc
firmware res ueventd.rc
fstab.qcom root usbstorage
init sbin vendor
The system folder is empty tho. I have pulled the default.prop to my pc and pushed it back, created the build.prop and pushed it in to the system folder.
After i did that i typed exit and then adb reboot. Still no usb debugging. I checked the files again and the default.prop was back to the original, and the build.prop from the system folder was gone after the reboot. I don't know what i am doing wrong. I even have root access....

TomyVk said:
When i type ls in the shell i get this
Code:
ls
boot init.rc sdcard
cache init.recovery.hlthchrg.rc seapp_contexts
charger init.recovery.qcom.rc selinux_version
data init.recovery.service.rc sepolicy
default.prop init.recovery.usb.rc service_contexts
dev license sideload
efs modem sys
etc oem system
external_sd proc tmp
file_contexts property_contexts twres
file_contexts.bak recovery ueventd.qcom.rc
firmware res ueventd.rc
fstab.qcom root usbstorage
init sbin vendor
The system folder is empty tho. I have pulled the default.prop to my pc and pushed it back, created the build.prop and pushed it in to the system folder.
After i did that i typed exit and then adb reboot. Still no usb debugging. I checked the files again and the default.prop was back to the original, and the build.prop from the system folder was gone after the reboot. I don't know what i am doing wrong. I even have root access....
Click to expand...
Click to collapse
System isn't mounted which is why you can't access it - you need to swipe to enable system modification when you first start twrp which you can't see hence I said see if are able to control screen from pc
Make sure you set the correct permissions for the file - 644 or rw-r-r

TheFixItMan said:
System isn't mounted which is why you can't access it - you need to swipe to enable system modification when you first start twrp which you can't see hence I said see if are able to control screen from pc
Make sure you set the correct permissions for the file - 644 or rw-r-r
Click to expand...
Click to collapse
File permissions are correct, i have checked them as soon i saw that it wont work.
i have tried to mirror the screen over adb with
https://www.xda-developers.com/scrcpy-control-android-on-pc/
http://marian.schedenig.name/2014/07/03/remote-control-your-android-phone-through-adb/
and i was checking on google arround, nothing works. It also seems like that the touch screen is broken...
Anyone knows maybe annother option to mount the system?

TomyVk said:
File permissions are correct, i have checked them as soon i saw that it wont work.
i have tried to mirror the screen over adb with
https://www.xda-developers.com/scrcpy-control-android-on-pc/
http://marian.schedenig.name/2014/07/03/remote-control-your-android-phone-through-adb/
and i was checking on google arround, nothing works. It also seems like that the touch screen is broken...
Anyone knows maybe annother option to mount the system?
Click to expand...
Click to collapse
No other than the commands I've given you

TheFixItMan said:
No other than the commands I've given you
Click to expand...
Click to collapse
Means the only chance would be to pull a rom and edit it so that adb is enabled and flash it on the device....
Well, i think i got a new hobby xD