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

[Guide][NOOB-Friendly] How to share your Nandroid Backup and Modem

As we are having a lot of Jelly Bean leaks lately, a lot of users want to share the Nandroid backup to others but sometimes they make mistakes which ends up in md5 mismatches or some of them don't know how to create a share-able zip.
I have tried to create this guide to enable them in doing so. Hope this will help everyone.
Requirement:
CWM Recovery
7zip, Winrar or any file compressing tool
ADB setup in your PC
Click to expand...
Click to collapse
Once you have applied the OTA and done a factory reset, Follow the process given below:-
If your have ClockworkMod Touch Recovery 6.0.1.2 (Believe me it is easier and better in Touch recovery - Get it from here) follow these:-
In CWM Recovery
Reboot into Recovery => Hold Volume Up + Home + Power buttons together for about 5-7 seconds, release the buttons when you see the recovery menu
Choose -> Backup and Restore
Chooose -> Choose Backup Format (Optional)
Change Backup format to tar (Optional)
Choose -> Create image.zip
This will create an image.zip and an image folder in your Internal Sdcard inside the clockworkmod>backup folder
Copy the image.zip file to your PC, rename it to the software version you are sharing for e.g. GT-I9300-XXXXXXXX. Important do not put spaces in the name.
Upload this zip to whichever Filehosting site you want to share with.
*this image.zip can be flashed in CWM directly without having the need to extract the files inside*
Click to expand...
Click to collapse
If you have ClockworkMod Recovery 5.5 (Get it from here) Follow these:-
In CWM Recovery
Reboot into Recovery => Hold Volume Up + Home + Power buttons together for about 5-7 seconds, release the buttons when you see the recovery menu
Choose -> Backup and Restore
Choose -> Backup (either Internal or External SDcard by default it will backup to ExtSDcar)
Your Backup will now be there inside the clockworkmod>backup folder, Copy this folder to your PC
Zip the Folder and give it a name for e.g. GT-I9300-XXXXXX (Dont use spaces)
Now you can upload this zip to any filehosting service of your choice
Click to expand...
Click to collapse
How to extract the modem:-
For extracting the modem you need to be rooted (If you are not or want to know how go here)
Using ADB (Go here if you want to know how to set up ADB)
Connect your phone to you PC (Please ensure that ADB debugging option is checked in Developer Options)
Type
Code:
adb devices
You will get something like this:
Code:
List of devices attached
XXXXXXXXXXXXXX device
It shows your device is connected via ADB
Type
Code:
adb shell
You will get a output like this:
Code:
C:\adb>adb shell
[email protected]:/ $
Type
Code:
su
You will get:
Code:
su
[email protected]:/ #
(Those who are using Terminal Emulator can start from this step)
Type
Code:
dd if=/dev/block/mmcblk0p7 of=/sdcard/modem.bin bs=4096
You will get
Code:
[email protected]:/ # dd if=/dev/block/mmcblk0p7 of=/sdcard/modem.bin bs=4096
dd if=/dev/block/mmcblk0p7 of=/sdcard/modem.bin bs=4096
8192+0 records in
8192+0 records out
33554432 bytes transferred in 2.892 secs (11602500 bytes/sec)
[email protected]:/ #
Your modem.bin file is copied to the root of your sdcard, copy it to your PC and upload it to the file hosting site of your choice
Click to expand...
Click to collapse
I have tried to write everything to the best of my knowledge. If anyone feels that I have missed something or I have written something wrong please let me know. I will make the changes.

Thanx for this very useful
Sent from my GT-I9300 using Tapatalk 2

anurag549 said:
Thanx for this very useful
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
will be helpful for many ... nice work buddy

Q: When I dump modem I get a modem.bin and its ~30mb, while shipped modems in stock fw is ~12mb, why is this?

Perka said:
Q: When I dump modem I get a modem.bin and its ~30mb, while shipped modems in stock fw is ~12mb, why is this?
Click to expand...
Click to collapse
Well that escapes me..may be someone knowledgeable can shed some light on it..
Sorry..
Maybe the that provided with the firmware is a patch..I know OTA files are patches but can't say much about full firmwares..

I'm trying to do this using the terminal emulator in Rom toolbox and u keep getting permission denied?
(from what I understood we had two ways of doing this correct? A computer and adb or TE, correct?)

Danielhammons1 said:
I'm trying to do this using the terminal emulator in Rom toolbox and u keep getting permission denied?
(from what I understood we had two ways of doing this correct? A computer and adb or TE, correct?)
Click to expand...
Click to collapse
You have to type su in terminal to gain root access. It's just like a standard Linux terminal.

[GUIDE] Format EFS Folder without EFS-Professional (For Downgrading/Bootloop Fix)

Finally i've managed to downgrade to lollipop from marshmallow cm13.
For those who having errors in EFS Professional when you try to erase the efs partition, you MUST follow another way to format (else you'll not be able downgrade).
These errors you probably getting is because the efs partition is used already by the system, so the tool cannot format it.
What i did and worked perfectly (i lost my imei but i have kept a backup):
1) BACKUP YOUR IMEI (I used EFS-Professional to backup efs when i was in lollipop, if you did not then backup your IMEI files now as explained here)
2) Boot to TWRP (My version is 2.8.7.0)
3) Select Advanced and Terminal Command
4) Select the / directory
5) Format your efs by giving the follow command: mke2fs /dev/block/mmcblk0p3
6) Reboot to download mode and flash your stock firmware based on your baseband (mine was COJ5), follow the appropriate guide (here or here), including the pit file and repartition checked.
7) Let it reboot when odin finish, you are on lollipop now. (If you get bootloop again, try factory reset via stock recovery)
8) Flash cf-root with odin and TWRP as you always do.
9) Restore your IMEI and have fun
** For those who only kept an efs-professional backup of the efs partition BEFORE flashing cm13, you can restore it easily by extracting the efs.img from the backup to your phone sd, and using the terminal emulator give the follow commands:
Code:
su (grant permissions)
dd if=/sdcard/efs.img of=/dev/block/mmcblk0p3 bs=4096
reboot
** For those who only kept imei and nv_data backup, follow this guide and then give the follow permissions to these files:
Code:
[B]imei folder [/B]should have 0775 (rwxrwxr-x) with Owner: root, Group: radio
-inside imei folder [B]mps_code.dat[/B] should have 0664 (rw-rw-r--) with Owner: radio, Group: system
[B]nv_data.bin[/B] should have 0700 (rwx------) with Owner: radio, Group: radio

Sectoras said:
Finally i've managed to downgrade to lollipop from marshmallow cm13.
For those who having errors in EFS Professional when you try to erase the efs partition, you MUST follow another way to format (else you'll not be able downgrade).
These errors you probably getting is because the efs partition is used already by the system, so the tool cannot format it.
What i did and worked perfectly (i lost my imei but i have kept a backup):
1) BACKUP YOUR IMEI (I used EFS-Professional to backup efs when i was in lollipop, if you did not then backup your IMEI files now as explained here)
2) Boot to TWRP (My version is 2.8.7.0)
3) Select Advanced and Terminal Command
4) Select the / directory
5) Format your efs by giving the follow command: mke2fs /dev/block/mmcblk0p3
6) Reboot to download mode and flash your stock firmware based on your baseband (mine was COJ5), follow the appropriate guide (here or here), including the pit file and repartition checked.
7) Let it reboot when odin finish, you are on lollipop now. (If you get bootloop again, try factory reset via stock recovery)
8) Flash cf-root with odin and TWRP as you always do.
9) Restore your IMEI and have fun
** For those who only kept an efs-professional backup of the efs partition BEFORE flashing cm13, you can restore it easily by extracting the efs.img from the backup to your phone sd, and using the terminal emulator give the follow commands:
Code:
su (grant permissions)
dd if=/sdcard/efs.img of=/dev/block/mmcblk0p3 bs=4096
reboot
** For those who only kept imei and nv_data backup, follow this guide and then give the follow permissions to these files:
Code:
[B]imei folder [/B]should have 0775 (rwxrwxr-x) with Owner: root, Group: radio
-inside imei folder [B]mps_code.dat[/B] should have 0664 (rw-rw-r--) with Owner: radio, Group: system
[B]nv_data.bin[/B] should have 0700 (rwx------) with Owner: radio, Group: radio
Click to expand...
Click to collapse
thanks my friend you saved my phone... it took me two weeks to find your guide... thanks a lot.

Sectoras said:
Finally i've managed to downgrade to lollipop from marshmallow cm13.
For those who having errors in EFS Professional when you try to erase the efs partition, you MUST follow another way to format (else you'll not be able downgrade).
These errors you probably getting is because the efs partition is used already by the system, so the tool cannot format it.
What i did and worked perfectly (i lost my imei but i have kept a backup):
1) BACKUP YOUR IMEI (I used EFS-Professional to backup efs when i was in lollipop, if you did not then backup your IMEI files now as explained here)
2) Boot to TWRP (My version is 2.8.7.0)
3) Select Advanced and Terminal Command
4) Select the / directory
5) Format your efs by giving the follow command: mke2fs /dev/block/mmcblk0p3
6) Reboot to download mode and flash your stock firmware based on your baseband (mine was COJ5), follow the appropriate guide (here or here), including the pit file and repartition checked.
7) Let it reboot when odin finish, you are on lollipop now. (If you get bootloop again, try factory reset via stock recovery)
8) Flash cf-root with odin and TWRP as you always do.
9) Restore your IMEI and have fun
** For those who only kept an efs-professional backup of the efs partition BEFORE flashing cm13, you can restore it easily by extracting the efs.img from the backup to your phone sd, and using the terminal emulator give the follow commands:
Code:
su (grant permissions)
dd if=/sdcard/efs.img of=/dev/block/mmcblk0p3 bs=4096
reboot
** For those who only kept imei and nv_data backup, follow this guide and then give the follow permissions to these files:
Code:
[B]imei folder [/B]should have 0775 (rwxrwxr-x) with Owner: root, Group: radio
-inside imei folder [B]mps_code.dat[/B] should have 0664 (rw-rw-r--) with Owner: radio, Group: system
[B]nv_data.bin[/B] should have 0700 (rwx------) with Owner: radio, Group: radio
Click to expand...
Click to collapse
Hmm. Its the same partitions on N910H right? For the mke2fs command
---------- Post added at 02:21 PM ---------- Previous post was at 01:43 PM ----------
How to fix the DRK thing? Is it preventing to boot?

:) Solved EFS faild mount invalid argument (damage efs folder empty)

I finally managed to repair the damage caused by EFS and by when I go to the root explorer I had a clean empty folder EFS whatever I tried to install the new ROM moaning and costum and wipe reset Factory me is always the folder EFS empty my IMEI was correct as it was under the battery, the only thing I had a bad signal and wifi is deenergizes.
To repair the damage I'm desperate to be ordered from stock rom sammobil version 4.4.2 because my phone was slow I then ordered stoc 5.0 then I root the phone and ordered phils latest recover and then I went under the option to mount and put the mount seytem then I have connected phone to a PC and install the adb shell on the computer I Open cmd and typed it
adb shell
su
mke2fs /dev/block/mmcblk0p11 ( skip to next step if fail)
mount -w -t ext4 /dev/block/mmcblk0p11
reboot
This will create a generic EFS files on device
Root explorer/efs and delete factorymode(OFF) and replace with factorymode(ON)
reboot in recovery wipedata factory reset...don
This last what it says to me it was not necessary because I went in and looked exporer root file factorymode where it has been on only one I did factory reset and that's it I got back EFS files and I am so done with all programs EFS Bacup :good:
P : S: because I have a bad signal or should now install new modem in order to find the best signal

Yeah used to see that tutorial by nowy57.
Sent from my GT-N7000

can I flash my efs.img via odin?

can't boot my phone cause I have deleted my efs folder becasue in one of the guides here someone said that if you had full recovery of your efs and you sure that your efs folder is damged than delete the folder and recover, well so I did... (I downgrade from lolipop to 4.4.2, lost my imei in the "process"
I had the efs.img backup on my computer and I moved it to my phone, I deleted my efs folder using root browser and than I used some adb app to type the commend "dd if=/sdcard/efs.img of=/dev/block/mmcblk0p3 bs=4096" and I restred my phone, but it never left samsmung logo and I can't boot up my phone I tried to go to stock channgeing roms, nothing helps, in recovery mode it says "E:/can't mount efs" something like that.. and the phone won't boot up, just stuck on samsung logo.
somone have any Idea what can i do?

After flashing a stock ROM, did you perform a factory wipe before booting the phone for the first time?

audit13 said:
After flashing a stock ROM, did you perform a factory wipe before booting the phone for the first time?
Click to expand...
Click to collapse
you mean when I downgrade from lolipop to the stcok rom?, if yes Than I didn't and that what cause me losing my imei and started this whole efs problem...

Did you try flashing back to stock LP? Flashing stock kk would not normally damage the efs.

audit13 said:
Did you try flashing back to stock LP? Flashing stock kk would not normally damage the efs.
Click to expand...
Click to collapse
yey I manged to fix ti!!!! god that was hard **** yes!! to me!
if someone will see this so this is what I did
1) I flashed to stock rom based lolipop but still had the issue of "E:failed to mount /efs" cause it didn't recvoer the folder and my phone still won't boot up, so I found a fix
right here http://forum.xda-developers.com/galaxy-s3/general/how-to-fix-efailed-to-mount-efs-invalid-t2858056
adb shell
Code:
mke2fs /dev/block/mmcblk0p3
Code:
mount -w -t ext4 /dev/block/mmcblk0p3 (this line dind't even work for me so I skipped it)
Code:
reboot
affter I did it phone boot up finally but I still had a fake Imei so next I used this guide (this time I ain't deleting the efs folder like he wrote"
2)http://forum.xda-developers.com/showthread.php?t=2392632, I alredy had efs.img as back up so all I did is install latest "su" and the latest busybox than I installed "Terminal Emulator"
and used the second method
"Put your efs.img on your phone memory(not external sd card!) in the main memory, not inside folder.
Open terminal emulator
Write the following:
Code:
su
Then click enter. It will ask for super user permission, give it permissions.
Then write:
Code:
dd if=/sdcard/efs.img of=/dev/block/mmcblk0p3 bs=4096"
my phone rebooted and now I have my imei back!

Congratulations on your success and posting your solution!

worked for me
okdark4 said:
"Put your efs.img on your phone memory(not external sd card!) in the main memory, not inside folder.
Open terminal emulator
Write the following:
Code:
su
Then click enter. It will ask for super user permission, give it permissions.
Then write:
Code:
dd if=/sdcard/efs.img of=/dev/block/mmcblk0p3 bs=4096"
my phone rebooted and now I have my imei back!
Click to expand...
Click to collapse
Hi okdark4,
thanks for sharing!
For me, I hat to use a slightly different command - just for the others to know:
su
dd if=/sdcard/efs.img of=/dev/block/mmcblk0p3
reboot
That's it!