CWM For Galaxy Mega I9152
This is experimental CWM recovery. As I was free today so made this one!
I need some one to test!
PROCEDURE
Download and setup ADB drivers for your device
can be found her DOWNLOAD
Download two files in your computer! Odin3 and Recovery! Extract odin in a location! And extract the other zip in odin folder!
ODIN And Recovery
HERE IS TWRP TWRP Check If it work's are not!
Turn of your device and go to odin mode [ Vol down + power + home button (all at the same time) ] release it when you see GT-i9152 logo!
Press vol up to confirm!
Now that you are in odin mode connect your device via usb cable !
Open that odin.exe in ODIN folder!
If there is a pop-up like Installing ADB drivers let it get finished it is usually updates !!!!
Make sure the COM : xx (xx is usb port number it can be any number so dont worry about it,just verify COM is lit up)
Extract the recovery-adityaf_i9200.tar.zip ! Now select PDA and browse to where you have extracted recovery-adityaf_i9200.tar and select it
Click Start
Please tell me if it works! I want someone to confirm!!!
Guy's I have been working on this since long time! But i found some graphical gliches from recovery If CWM doesn't work TWRP will work for sure if nothing works tells me i have a different recovery too!
Please rate and thanks this thread
By mistake I used i9200 instead of i9152 I was busy so flash it on i9152 please sorry mistake from my side
Reserved#1
Reserved#2
F.A.Q
F.A.Q
1) My device is not detecting in ODIN!
Ans: Please make sure you have installed ADB drivers on your windows7!
2) What if i'm running Ubuntu?
Ans: Ubuntu doesn't support ODIN! So please use Windows!
3) I want this function that function!
Ans: Please don't ask for any new function!
4) I have this bug that bug! What can i do??
Ans: Just report the bug and stay clam till i solve!
adityaf said:
F.A.Q
2) What if i'm running Ubuntu?
Ans: Ubuntu doesn't support linux! So please use Windows!
Click to expand...
Click to collapse
Ubuntu uses Linux for its kernel and ADB is installable very easily.
Code:
$ uname -a
Linux <hostname> 3.5.0-37-generic #58-Ubuntu SMP Mon Jul 8 22:07:55 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Code:
$ adb
Android Debug Bridge version 1.0.29
-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is running.
-s <serial number> - directs command to the USB device or emulator with
the given serial number. Overrides ANDROID_SERIAL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devices.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] [--algo <algorithm name> --key <hex-encoded key> --iv <hex-encoded iv>] <file>
- push this package file to the device and install it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data)
('-s' means install on SD card instead of internal storage)
('--algo', '--key', and '--iv' mean the file is encrypted already)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories)
adb bugreport - return all information from the device
that should be included in a bug report.
adb backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosystem] [<packages...>]
- write an archive of the device's data to <file>.
If no -f option is supplied then the data is written
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks themselves
in the archive; the default is noapk.)
(-shared|-noshared enable/disable backup of the device's
shared storage / SD card contents; the default is noshared.)
(-all means to back up all installed applications)
(-system|-nosystem toggles whether -all automatically includes
system applications; the default is to include system apps)
(<packages...> is the list of applications to be backed up. If
the -all or -shared flags are passed, then the package
list is optional. Applications explicitly given on the
command line will be included even if -nosystem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup archive
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specified device
adb remount - remounts the /system partition on the device read-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the bootloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on the specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be updated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list of the following values
1 or all, adb, sockets, packets, rwx, usb, sync, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes priority over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these debug tags are printed.
Please delete that comment it was a typo
Sent from my GT-I9082 using xda premium
Thank, you show me to flash this, but it is for 9200, not for 9152?
I flash by ODIN and...it is sat that: no binary is selected.
I see this in Message box of ODIN:
<OSM> Enter CS for MD5
<OSM> Check MD5....Do not unplug the cable..
<OSM> Please wait...
<OSM> MD5 hash value is invalid
<OSM> recovery_adityaf_I9200.tar.md5 is invalid
<OSM> End...
oldmanhp said:
Thank, you show me to flash this, but it is for 9200, not for 9152?
I flash by ODIN and...it is sat that: no binary is selected.
I see this in Message box of ODIN:
<OSM> Enter CS for MD5
<OSM> Check MD5....Do not unplug the cable..
<OSM> Please wait...
<OSM> MD5 hash value is invalid
<OSM> recovery_adityaf_I9200.tar.md5 is invalid
<OSM> End...
Click to expand...
Click to collapse
Remove .md5 rename it and remove .md5
Sent from my GT-I9082 using xda premium
adityaf said:
Remove .md5 rename it and remove .md5
Sent from my GT-I9082 using xda premium
Click to expand...
Click to collapse
It work, but I can not see anything on the screen of CWM:
The screen exactly the same when I did with this recovery by sarath280 : http://forum.xda-developers.com/showthread.php?t=2329275
oldmanhp said:
It work, but I can not see anything on the screen of CWM:
Click to expand...
Click to collapse
Okay I will work it
Sent from my GT-I9082 using xda premium
adityaf said:
Okay I will work it
Sent from my GT-I9082 using xda premium
Click to expand...
Click to collapse
Yeah, waiting for yor help. Thank.
Anything new bro?
Can You write on title the Model Type please.
Thanks
oldmanhp said:
Anything new bro?
Click to expand...
Click to collapse
Yep I have one recovery! Wait till I upload!
Sent from my GT-I9082 using xda premium
oldmanhp said:
Anything new bro?
Click to expand...
Click to collapse
http://d-h.st/MOM
Chk it out flash this!!
adityaf said:
http://d-h.st/MOM
Chk it out flash this!!
Click to expand...
Click to collapse
Thank adityaf very much. Can anybody test this, I am outside now and can not test at the moment.
adityaf said:
http://d-h.st/MOM
Chk it out flash this!!
Click to expand...
Click to collapse
Downloaded it, but it is in zip format, how can I flash it with stock recovery?
oldmanhp said:
Downloaded it, but it is in zip format, how can I flash it with stock recovery?
Click to expand...
Click to collapse
Are u rooted? If yes flash it!
Sent from my GT-I9082 using xda premium
Off course rooted, but recovery is still stock from samsung, no way to flash zip file.
OK I try to flash it by another custom recovery (by sarath280), and the recovery screen event more difficult to see than your 1st release, any idea?
I think Samsung change something on resolution code, that why recovery can still work, but can not display normanly.
oldmanhp said:
Off course rooted, but recovery is still stock from samsung, no way to flash zip file.
OK I try to flash it by another custom recovery (by sarath280), and the recovery screen event more difficult to see than your 1st release, any idea?
I think Samsung change something on resolution code, that why recovery can still work, but can not display normanly.
Click to expand...
Click to collapse
Hmmm think so I have to drill deep in source code for a file till then u just check this ##it works or not!
Sent from my GT-I9082 using xda premium
Related
Ok im working on something big for the amaze but need someone to dump the boot.img here are the comands
1. Download ADB: http://www.mediafire.com/?5d0v316g9bg97
2. Extract the contents of the zip to C:\
3. Run the commands below:
Code:
cd c:\adb
adb shell
dd if=/dev/block/mmcblk0p22 of=/sdcard/boot.img
Note: If your device is not detected, download and install HTC Sync.
4. Connect your phone in USB Mode, copy the hboot.img file from your SD card and upload it to Multiupload.
Love to do it but I'm at work. If no one does by the time I get home ill be happy to.
Sent from my HTC_Amaze_4G using XDA App
I'll do it when I get home from school
Sent from my HTC_Amaze_4G using XDA Premium App
xboarder56 said:
Ok im working on something big for the amaze but need someone to dump the boot.img here are the comands
1. Download ADB: http://www.mediafire.com/?5d0v316g9bg97
2. Extract the contents of the zip to C:\
3. Run the commands below:
Code:
cd c:\adb
adb shell
dd if=/dev/block/mmcblk0p22 of=/sdcard/boot.img
Note: If your device is not detected, download and install HTC Sync.
4. Connect your phone in USB Mode, copy the hboot.img file from your SD card and upload it to Multiupload.
Click to expand...
Click to collapse
Didn't work. Any other ideas. This was the output.
List of devices attached
HT19RVP07371 device
C:\Users\Administrator>adb shell
$ dd if=/dev/block/mmcblk0p22 of=/sdcard/boot.img
dd if=/dev/block/mmcblk0p22 of=/sdcard/boot.img
/dev/block/mmcblk0p22: cannot open for read: Permission denied
$
Click to expand...
Click to collapse
Binary100100 said:
Didn't work. Any other ideas. This was the output.
Click to expand...
Click to collapse
maybe try this
adb pull dd if=/dev/block/mmcblk0p22 of=/sdcard/boot.img
Click to expand...
Click to collapse
xboarder56 said:
maybe try this
Click to expand...
Click to collapse
Here's the output:
C:\Users\Administrator>adb pull dd if=/dev/block/mmcblk0p22 of=/sdcard/boot.img
Android Debug Bridge version 1.0.26
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this ocmmand with no additional arguments
will disconnect from all connected TCP/IP devic
es.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
C:\Users\Administrator>
Click to expand...
Click to collapse
ohh i mean
adb pull dd if=/dev/block/mmcblk0p22
xboarder56 said:
ohh i mean
adb pull dd if=/dev/block/mmcblk0p22
Click to expand...
Click to collapse
remote object 'dd' does not exist
I tried and got the same errors...
Would it help to push busybox then try the adb pull?
EDIT: Nevermind. The reason none of this is working is because the block is only readable by root. I'm still a little too squimish to try the temp root thing, but that's the only way to get the file.
Here ya go.
HTC Amaze boot.img
Can someone return the favor an post a stock recovery image. I ruined mine and now I cannot do a factory reset or reboot into recovery.
After temp rooting the phone do this:
Code:
adb shell dd if=/dev/block/mmcblk0p23 of=/sdcard/recovery.img
Thanks,
-xdadevelopers-user
xdadevelopers-user said:
Here ya go.
HTC Amaze boot.img
Can someone return the favor an post a stock recovery image. I ruined mine and now I cannot do a factory reset or reboot into recovery.
After temp rooting the phone do this:
Code:
adb shell dd if=/dev/block/mmcblk0p23 of=/sdcard/recovery.img
Thanks,
-xdadevelopers-user
Click to expand...
Click to collapse
Will do so after phone arrives (and if i don't brick it with temp root + permanent fix). Hope you get it earlier, as that will be end of week at the earliest.
I used NVflash to originally flash Recovery on G2X - can Nvflash be used the same way here?
gaww said:
Will do so after phone arrives (and if i don't brick it with temp root + permanent fix). Hope you get it earlier, as that will be end of week at the earliest.
I used NVflash to originally flash Recovery on G2X - an Nvflash be used the same way here?
Click to expand...
Click to collapse
no its gonna have to be done through hboot
hello sir,
i am a htc one x+ user in india
device = htc one x+ (enrc2b)
H boot = 1.72.000
android = 4.2.2 sense 5
baseband version = 3.1204.171.33
build number 2.18.707.5
My problem is i unlocked my phone then i rooted it then i tried to install cyanogenmod 10.1.3 it stuck on boot animation then i remove that and unrooted my phone and relocked my phone....now when i reset my phone or go to recovey its says " this build is for development purposes only...." in red and i tried to install this stock ruu....."RUU_ENRC2B_U_JB_45_hTC_Asia_WWE_1.17.707.1_Radio_3.1204.168.32_release_299722_signed"
this shows error 158 i am in a big problem dnt know what to do plzz plzz help.
shivangshukla said:
hello sir,
i am a htc one x+ user in india
device = htc one x+ (enrc2b)
H boot = 1.72.000
android = 4.2.2 sense 5
baseband version = 3.1204.171.33
build number 2.18.707.5
My problem is i unlocked my phone then i rooted it then i tried to install cyanogenmod 10.1.3 it stuck on boot animation then i remove that and unrooted my phone and relocked my phone....now when i reset my phone or go to recovey its says " this build is for development purposes only...." in red and i tried to install this stock ruu....."RUU_ENRC2B_U_JB_45_hTC_Asia_WWE_1.17.707.1_Radio_3.1204.168.32_release_299722_signed"
this shows error 158 i am in a big problem dnt know what to do plzz plzz help.
Click to expand...
Click to collapse
First of all since ur hboot is 1.72 the RUU wont work...and there is no RUU out for the hboot version > 1.35
u can get back to stock by grabbing the nandroid backup from this thread and flash the kernel inside the zip file from fastboot
if u want to install any custom ROM after flashing the ROM do flash the Kernel(boot.img) from the ROM zip file from fastboot mode
sterps to do it
[email protected] said:
First of all since ur hboot is 1.72 the RUU wont work...and there is no RUU out for the hboot version > 1.35
u can get back to stock by grabbing the nandroid backup from this thread and flash the kernel inside the zip file from fastboot
if u want to install any custom ROM after flashing the ROM do flash the Kernel(boot.img) from the ROM zip file from fastboot mode
Click to expand...
Click to collapse
this its really helpful....plz will you tell me the steps to do it because this time i dont wana get into any trouble
shivangshukla said:
this its really helpful....plz will you tell me the steps to do it because this time i dont wana get into any trouble
Click to expand...
Click to collapse
Steps for Custom ROM or Stock Nandroid backup...????
quote
[email protected] said:
Steps for Custom ROM or Stock Nandroid backup...????
Click to expand...
Click to collapse
sorry sir Stock Nandroid backup....
quote
[email protected] said:
Steps for Custom ROM or Stock Nandroid backup...????
Click to expand...
Click to collapse
so what are the steps should i take...
shivangshukla said:
sorry sir Stock Nandroid backup....
Click to expand...
Click to collapse
Prerequisites : android development kit windows and Nandroid backup
download the Nandroid backup from the post here
connect ur phone to PC when on TWRP(recovery mode)
make sure ur device is recognized
do "adb devices"
This will show ur device serial no XXXX as in recovery
do "adb shell" that will enter ur phone storage (exclude the quotes in all the commands)
do "mkdir sdcard/TWRP/BACKUPS/XXXX/stock" this will create a directory as stock on the following path(replace XXXX with ur device serial number copy from the above result "adb devices")
now do "exit"
u ll be back on platform-tools folder
unzip the nandroid backup u have downloaded and put it in platform-tools folder now push those files one by one using adb push
"adb push system.ext4.win sdcard/TWRP/BACKUPS/xxxxxxx/stock"
like wise replace the system.ext4.win with all the files u had extracted from the zip
wipe all dalvik,system,cache,and data excluding ur internal storage(don't wipe internal storage which will wipe all the data u have copied)
now go to Restore on TWRP and u ll find the folder stock then just swipe to restore it
once u have done it
reboot to bootloader
flash the kernel from the zip just rename the boot.emmc.win to boot.img and
enter this command
"fastboot flash boot boot.img"
"fatsboot erase cache"
unplug ur device
now reboot ur phone
IT MUST BOOT
quote
[email protected] said:
Prerequisites : android development kit windows and Nandroid backup
download the Nandroid backup from the post here
connect ur phone to PC when on TWRP(recovery mode)
make sure ur device is recognized
do "adb devices"
This will show ur device serial no XXXX as in recovery
do "adb shell" that will enter ur phone storage (exclude the quotes in all the commands)
do "mkdir sdcard/TWRP/BACKUPS/XXXX/stock" this will create a directory as stock on the following path(replace XXXX with ur device serial number copy from the above result "adb devices")
now do "exit"
u ll be back on platform-tools folder
unzip the nandroid backup u have downloaded and put it in platform-tools folder now push those files one by one using adb push
"adb push system.ext4.win sdcard/TWRP/BACKUPS/xxxxxxx/stock"
like wise replace the system.ext4.win with all the files u had extracted from the zip
wipe all dalvik,system,cache,and data excluding ur internal storage(don't wipe internal storage which will wipe all the data u have copied)
now go to Restore on TWRP and u ll find the folder stock then just swipe to restore it
once u have done it
reboot to bootloader
flash the kernel from the zip just rename the boot.emmc.win to boot.img and
enter this command
"fastboot flash boot boot.img"
"fatsboot erase cache"
unplug ur device
now reboot ur phone
IT MUST BOOT
Click to expand...
Click to collapse
before doing all this i should unloacked my bootloader and install twrp recovery then i shoud do this...correct me if i m wrong
shivangshukla said:
before doing all this i should unloacked my bootloader and install twrp recovery then i shoud do this...correct me if i m wrong
Click to expand...
Click to collapse
u got that right...
quote
[email protected] said:
u got that right...
Click to expand...
Click to collapse
i copy file to twrp and i wipe dalvik,cache,data,and system then igo to restore and its showing nothing and when i go to restart it says no os install
shivangshukla said:
i copy file to twrp and i wipe dalvik,cache,data,and system then igo to restore and its showing nothing and when i go to restart it says no os install
Click to expand...
Click to collapse
I dont think then u have copied the files to this directory sdcard/TWRP/BACKUPS/XXXX/stock
this is the path which the TWRP cant recognize so u have to copy the files exactly on this directory only not anywhere else
U have to create a folder in this path sdcard/TWRP/BACKUPS/SERIALNO of ur phone
create a directory in the above mentioned path by this command from the command prompt
"mkdir sdcard/TWRP/BACKUPS/SERIALNO/STOCK"
this will create a directory STOCK inside ur serial number directory
Now u can copy all the files to the STOCK directory by doing "adb push"
refer to the this post for that
once u have copied all the files to that folder u can restore it from the restore option on TWRP and flash the kernel from the fastboot mode
quite
when doing adb slideload firmware.zip its showing tihs.
Android Debug Bridge version 1.0.26
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this ocmmand with no additional arguments
will disconnect from all connected TCP/IP devic
es.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
quote
[email protected] said:
I dont think then u have copied the files to this directory sdcard/TWRP/BACKUPS/XXXX/stock
this is the path which the TWRP cant recognize so u have to copy the files exactly on this directory only not anywhere else
U have to create a folder in this path sdcard/TWRP/BACKUPS/SERIALNO of ur phone
create a directory in the above mentioned path by this command from the command prompt
"mkdir sdcard/TWRP/BACKUPS/SERIALNO of ur phone/STOCK"
this will create a directory STOCK inside ur serial number directory
Now u can copy all the files to the STOCK directory by doing "adb push"
refer to the this post for that
once u have copied all the files to that folder u can restore it from the restore option on TWRP and flash the kernel from the fastboot mode
Click to expand...
Click to collapse
when ruining this step abd slideload firmware.zip its showing
Android Debug Bridge version 1.0.26
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this ocmmand with no additional arguments
will disconnect from all connected TCP/IP devic
es.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
shivangshukla said:
when ruining this step abd slideload firmware.zip its showing
Android Debug Bridge version 1.0.26
bug tags are printed.
Click to expand...
Click to collapse
U dont have to copy the firmware.zip at all leave it alone...
the firmware.zip is the file which upgrades ur radio and hboot to the latest one
u already have it so dont try to sideload or flash firmware.zip
Navigate to the folder where u have installed adb and open the command prompt in there
just try "adb devices" from there
u must see ur device serial number and as on recovery like this
if the list if devices attached shows as nothing then wait for five min or restart ur system
make sure ur phone is recognized on adb devices
after that follow the post I have mentioned earlier.......
Please please dont try the firmware.zip thats useless in ur case.....since u are alreay on hboot 1.72
[email protected] said:
U dont have to copy the firmware.zip at all leave it alone...
the firmware.zip is the file which upgrades ur radio and hboot to the latest one
u already have it so dont try to sideload or flash firmware.zip
Navigate to the folder where u have installed adb and open the command prompt in there
just try "adb devices" from there
u must see ur device serial number and as on recovery like this
if the list if devices attached shows as nothing then wait for five min or restart ur system
make sure ur phone is recognized on adb devices
after that follow the post I have mentioned earlier.......
Please please dont try the firmware.zip thats useless in ur case.....since u are alreay on hboot 1.72
Click to expand...
Click to collapse
firmware means i am using adb slideload when i write adb slidelload comand it says and my htc mtp device driver is not installing it says fail
Android Debug Bridge version 1.0.26
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this ocmmand with no additional arguments
will disconnect from all connected TCP/IP devic
es.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
shivangshukla said:
firmware means i am using adb slideload when i write adb slidelload comand it says and my htc mtp device driver is not installing it says fail
Android Debug Bridge version 1.0.26
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this ocmmand with no additional arguments
will disconnect from all connected TCP/IP devic
es.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
Click to expand...
Click to collapse
i did my restoration to nandroid backup i wana know how to flash the boot.img.....i copy the boot.img file to adb folder then i run yor command fastboot flash boot boot.img but it says error cant load
exit f problems
shivangshukla said:
i did my restoration to nandroid backup i wana know how to flash the boot.img.....i copy the boot.img file to adb folder then i run yor command fastboot flash boot boot.img but it says error cant load
Click to expand...
Click to collapse
fixed it back to your nandroid backup thanks alot for your help
reset problem
shivangshukla said:
fixed it back to your nandroid backup thanks alot for your help
Click to expand...
Click to collapse
every thing is good i m in my the stock rom.
after getting to stock i relocked my bootloader then i wish to reset my phone and my phone says that this is for development purpose only in red what to do with this stuff this problem was Earlier to and for this problem i did this nandroid backup so please tell me what to do with this problem.
quote
shivangshukla said:
every thing is good i m in my the stock rom.
after getting to stock i relocked my bootloader then i wish to reset my phone and my phone says that this is for development purpose only in red what to do with this stuff this problem was Earlier to and for this problem i did this nandroid backup so please tell me what to do with this problem.
Click to expand...
Click to collapse
installing stock recovery fixed the problem.
Can you post the download link of stock recovery please?
Another question: I have hboot. 1.40 ,
Do I have to go same steps as described here with same nandroid. Bckp ?
Sent from my LG-D802 using xda app-developers app
I ve got my Oppo Find5 into a boot loop by doing something stupid (modding the dpi).
I can get it into recovery and using adb (on ubuntu) and I can connect to the device (shows device id and that its in recovery), but I cant find any instructions on how to push the original build.prop to the device (without loosing any data, obviously).
Could anyone help ?
Can I edit the build.prop using adb ?
Thanks
You can pull the old one, edit it, then push it back
adb pull /system/build.prop /location/on/PC
Then edit
adb push /location/on/PC/build.prop /system/build.prop
You may then need to change permissions too
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
You can pull the old one, edit it, then push it back
adb pull /system/build.prop /location/on/PC
Then edit
adb push /location/on/PC/build.prop /system/build.prop
You may then need to change permissions too
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks "location/on/PC " is the path to my device ?
That should be shown in the terminal ?
And just noticed that the device id I got from the command "lsusb" is different to the one that abd reports after I connect my phone (seems its a Nexus 4 : ID 18d1:d001is what lsusb reports)
No, that's just me saying you need to tell it where to pull it to, like if you wanted to pull it to SD card command would be
adb pull /system/build.prop /sdcard
This would save it to your SD
You want it on desktop
adb pull /system/build.prop /home/yourubuntunamehere/Desktop
In this case change yourubuntunamehere to whatever this is for you
Sent from my Nexus 7 using XDA Premium 4 mobile app
Yes, that what I thought you meant, just checking.
Tried to pull it to my desktop and it says that build.prop does not exist.
Could this be because I m getting the code for a Nexus 4 if I type lsusb ? :
When I type *~/Android/sdk/platform-tools$ List of devices attached" it reports "604c7129".
Or could it be because the screen density app has deleted my build.prop ?
I have a copy of the original build prop, can I just push it to the device (overwriting any existing one if there is one) ?
I have tried to edit it on the device in Team Win Recovery, but there is no build.prop in system (or anywhere that I can find) to edit, so maybe adb is right and there is no build.pop ?
Yes you can pull the existing, but there should be one there unless deleted, try
adb shell
cd /system
ls -l
And look for the build.prop
But you're fine just pushing another one if you have it
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Yes you can pull the existing, but there should be one there unless deleted, try
adb shell
cd /system
ls -l
And look for the build.prop
But you're fine just pushing another one if you have it
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
On seperate lines ? Nothing happens and now I get this message
(gedit:5398): IBUS-WARNING **: The owner of /home/******/.config/ibus/bus is not root!
Yeah separate lines, this time try
adb shell
su
cd /system
ls -l
And for future reference paste full input/output from terminal session (either in code wraps or if real long pastebin link)
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Yeah separate lines, this time try
adb shell
su
cd /system
ls -l
And for future reference paste full input/output from terminal session (either in code wraps or if real long pastebin link)
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
OK thanks.
Could you tell me how to push a new build.prop it to the device ?
I am trying to sort out the issues I have with the device id being wrong. Once I have I ll try pushing it to the device, once I know how to do it.
Does it matter if the device id is wrong ? I mean is it ok as long as it connects ?
Thanks
Directions to push in first post from me, adb devices is only picking up your one device correct? If so yes feel free to push
Sent from my Nexus 4 using XDA Premium 4 mobile app
Sorry, very stressed ATM.
For location on pc do I just put Desktop, (thats where it is) or home/username/desktop/build.prop ?
And putting buid.prop at the end will overwrite the one on the device at the moment ?
Thanks
Well did it with home/username/Desktop and got this:
[******@******-HP-dx5150-SFF:~/Android/sdk/platform-tools$ adb push/home******/Desktop/build.prop /system/build.prop
Android Debug Bridge version 1.0.31
-a - directs adb to listen on all interfaces for a connection
-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is running.
-s <specific device> - directs command to the device or emulator with the given
serial number or qualifier. Overrides ANDROID_SERIAL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
-H - Name of adb server host (default: localhost)
-P - Port of adb server (default: 5037)
devices [-l] - list all connected devices
('-l' will also list device qualifiers)
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devices.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward --list - list all forward socket connections.
the format is a list of lines with the following format:
<serial> " " <local> " " <remote> "\n"
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb forward --no-rebind <local> <remote>
- same as 'adb forward <local> <remote>' but fails
if <local> is already forwarded
adb forward --remove <local> - remove a specific forward socket connection
adb forward --remove-all - remove all forward socket connections
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] [--algo <algorithm name> --key <hex-encoded key> --iv <hex-encoded iv>] <file>
- push this package file to the device and install it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data)
('-s' means install on SD card instead of internal storage)
('--algo', '--key', and '--iv' mean the file is encrypted already)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories)
adb bugreport - return all information from the device
that should be included in a bug report.
adb backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosystem] [<packages...>]
- write an archive of the device's data to <file>.
If no -f option is supplied then the data is written
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks themselves
in the archive; the default is noapk.)
(-shared|-noshared enable/disable backup of the device's
shared storage / SD card contents; the default is noshared.)
(-all means to back up all installed applications)
(-system|-nosystem toggles whether -all automatically includes
system applications; the default is to include system apps)
(<packages...> is the list of applications to be backed up. If
the -all or -shared flags are passed, then the package
list is optional. Applications explicitly given on the
command line will be included even if -nosystem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup archive
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb get-devpath - prints: <device-path>
adb status-window - continuously print device status for a specified device
adb remount - remounts the /system partition on the device read-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the bootloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on the specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be updated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list of the following values
1 or all, adb, sockets, packets, rwx, usb, sync, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes priority over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these debug tags are printed.
******@******-HP-dx5150-SFF:~/Android/sdk/platform-tools$ }
Which seems to just be a list of instructions for adb.
(sorry, been a while since I ve done it, but what do I put at the begining and end of the quotes from the terminal so it quotes it in different text ?)
Forgot the space
adb push /home****/Desktop/build.prop /system/build.prop
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Forgot the space
adb push /home****/Desktop/build.prop /system/build.prop
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks, it said it was successful, but phone still in same state and still cant find build.prop in system using the file explorer in TeamWinRecovery
Tried to pull it again and it doesnt exist, apparently, pushed it again and it said it was successful. Cant find it using the file explorer though, still in boot loop. Found out more info and the app sets permissions to 777 and they should be 644, got to chmod it, but unsure how to do that and if teh build.prop does not exist, well, I cant change permissions on it. Really stuck here.
Try either fixing permissions in recovery or chmod with adb, something like
adb shell
su
chmod 0755 /system/build.prop
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Try either fixing permissions in recovery or chmod with adb, something like
adb shell
su
chmod 0755 /system/build.prop
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks. So I just open adb make sure its connected then type:
"adb shell
su
chmod 0755 /system/build.prop"
Why 0755 not 644 or 00 644 ?
How do I fix permissions ? Do I mount the system in recovery ?
Shouldnt I do something in adb to get root ?
I have CM10.1 so recovery mode is TeamWinRecovery which has loads of features, including a file browser, but as I said I cant find build.prop, maybe I need to get root but nothing asks me for it.
It has a terminal emulator as well, but it asks me what folder I want to start from and thats stumped me as I was expecting a terminal just to open.
Sorry for all the questions !
No worries, questions are how you learn
In truth I can't recall what /system should be, I'm on mobile so this is off the top of my head, it may be 777 or 644 but I think it should be rw-r--r-- if I remember right, also been drinking, friends bday
You may need to mount system first too, fix permissions should be in advanced settings in twrp
When you type su that gives you root
Also dirty flashing your current ROM ontop of this one should fix your issue, shouldn't wipe anything
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
No worries, questions are how you learn
In truth I can't recall what /system should be, I'm on mobile so this is off the top of my head, it may be 777 or 644 but I think it should be rw-r--r-- if I remember right, also been drinking, friends bday
You may need to mount system first too, fix permissions should be in advanced settings in twrp
When you type su that gives you root
Also dirty flashing your current ROM ontop of this one should fix your issue, shouldn't wipe anything
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I didnt have root permissions and the system wasnt mounted, I mounted the system with TeamWinRecovery, re-pushed the build.prop to the phone and theres a chmod755 option in TWR so I did that and rebooted and the phone is back alive !!
Thanks for all your help !! !!
Really, really grateful.
Hi all and Sorry for my bad English.
I got a Kindle Fire hdx 7 3rd gen and i got it rooted everything was woking good. then i installed an apk called freedom and i used a function called "freecore" id restartedmy kindle and then it got a boot loop stuck, then i was reading that i need to do a hard reset, i charged my kindle fire full charge then press power and hold up volume up until i see the recovery mode with only restart kindle or factory reset options, so i did a factory restore and noting happen still on boot loop stuck i keep reading and i realized than i needed a custom recovery stock something i didn't installed when i rooted my kindle , i got adb installed on pc i tried kindle fire recovery and kindle fire unbrick tool but both software said waiting for device, still when i plug my kindle to pc i heard the sound that win 8 recognized it so please can someone help me or know a threat to a solution thank you .
Do you know what version of the Os you were running?
lekofraggle said:
Do you know what version of the Os you were running?
Click to expand...
Click to collapse
i downgraded 4.5.3 to 3.2.8 i think then updated to 4.5.2 to rooted
lekofraggle said:
Do you know what version of the Os you were running?
Click to expand...
Click to collapse
this is the thread i used http://forum.xda-developers.com/kin...lback-13-3-2-8-rollback-ota-captured-t3046204
I am sorry, but if you did not enable adb first, you may be out of luck. Try opening a command prompt in your adb folder and type adb devices. See if it shows up.
lekofraggle said:
I am sorry, but if you did not enable adb first, you may be out of luck. Try opening a command prompt in your adb folder and type adb devices. See if it shows up.
Click to expand...
Click to collapse
i tried command adb devices and it said device offline
That is odd. When I run the command with the device offline, it just prints a blank prompt.
lekofraggle said:
I am sorry, but if you did not enable adb first, you may be out of luck. Try opening a command prompt in your adb folder and type adb devices. See if it shows up.
Click to expand...
Click to collapse
ok i tried again now i got a message that said list of devices attached D0FCA0A04206008K offline
What happens if you try to push a file to the sd card?
lekofraggle said:
What happens if you try to push a file to the sd card?
Click to expand...
Click to collapse
this happened when i used push command
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\hector>cd C:\android-sdk
C:\android-sdk>adb push Copy.GBA/sdcard/
Android Debug Bridge version 1.0.32
-a - directs adb to listen on all interfaces for a c
onnection
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <specific device> - directs command to the device or emulator with
the given
serial number or qualifier. Overrides ANDROID_S
ERIAL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
-H - Name of adb server host (default: localhost)
-P - Port of adb server (default: 5037)
devices [-l] - list all connected devices
('-l' will also list device qualifiers)
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devic
es.
device commands:
adb push [-p] <local> <remote>
- copy file/dir to device
('-p' to display the transfer progress)
adb pull [-p] [-a] <remote> [<local>]
- copy file/dir from device
('-p' to display the transfer progress)
('-a' means copy timestamp and mode)
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward --list - list all forward socket connections.
the format is a list of lines with the followin
g format:
<serial> " " <local> " " <remote> "\n"
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb forward --no-rebind <local> <remote>
- same as 'adb forward <local> <remote>' but fail
s
if <local> is already forwarded
adb forward --remove <local> - remove a specific forward socket connection
adb forward --remove-all - remove all forward socket connections
adb reverse --list - list all reverse socket connections from device
adb reverse <remote> <local> - reverse socket connections
reverse specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
adb reverse --norebind <remote> <local>
- same as 'adb reverse <remote> <local>' but fail
s
if <remote> is already reversed.
adb reverse --remove <remote>
- remove a specific reversed socket connection
adb reverse --remove-all - remove all reversed socket connections from dev
ice
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-lrtsd] <file>
adb install-multiple [-lrtsdp] <file...>
- push this package file to the device and instal
l it
(-l: forward lock application)
(-r: replace existing application)
(-t: allow test packages)
(-s: install application on sdcard)
(-d: allow version code downgrade)
(-p: partial application install)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb backup [-f <file>] [-apk|-noapk] [-obb|-noobb] [-shared|-noshared] [-all]
[-system|-nosystem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is wr
itten
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks
themselves
in the archive; the default is noapk.)
(-obb|-noobb enable/disable backup of any insta
lled apk expansion
(aka .obb) files associated with each applic
ation; the default
is noobb.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the defau
lt is noshared.)
(-all means to back up all installed applicatio
ns)
(-system|-nosystem toggles whether -all automat
ically includes
system applications; the default is to inclu
de system apps)
(<packages...> is the list of applications to b
e backed up. If
the -all or -shared flags are passed, then t
he package
list is optional. Applications explicitly g
iven on the
command line will be included even if -nosys
tem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup
archive
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb get-devpath - prints: <device-path>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system and /vendor (if present) p
artitions on the device read-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, /system, /vendor (if present), and /data pa
rtitions will be updated.
- If it is "system", "vendor" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
C:\android-sdk>
lekofraggle said:
What happens if you try to push a file to the sd card?
Click to expand...
Click to collapse
i did it again looks like i missed typed something now i got "C:\android-sdk>adb push Copy.file /sdcard/
error: device offline
C:\android-sdk>"
Does your device show up in Windows explorer or in device manager?
---------- Post added at 06:24 PM ---------- Previous post was at 06:23 PM ----------
It could be that the drivers are not installed correctly, but at this point, I am just guessing. Sorry.
lekofraggle said:
Does your device show up in Windows explorer or in device manager?
---------- Post added at 06:24 PM ---------- Previous post was at 06:23 PM ----------
It could be that the drivers are not installed correctly, but at this point, I am just guessing. Sorry.
Click to expand...
Click to collapse
they dont show on windows explorer but in device manager i got:
kindle fire> Android Composite ADB Intercafe
Portable Devices> MTP USB Device
Okay, I do not think you have the driver loaded correctly. It is a long shot, but you could try uninstalling both devices (unplug your kindle first), then rebooting your computer and plugging your kindle back in. Hopefully, the drivers load okay. Then try adb again.
lekofraggle said:
Okay, I do not think you have the driver loaded correctly. It is a long shot, but you could try uninstalling both devices (unplug your kindle first), then rebooting your computer and plugging your kindle back in. Hopefully, the drivers load okay. Then try adb again.
Click to expand...
Click to collapse
the MTP USB Device got a little yellow triangle and on properties got this message "This device cannot start. (Code 10)
The process hosting the driver for this device has terminated."
Again, you have to remove it. Unhook your device, and uninstall them. Then, reboot and try to let it install.
lekofraggle said:
Again, you have to remove it. Unhook your device, and uninstall them. Then, reboot and try to let it install.
Click to expand...
Click to collapse
i did what told to do unhook it, unistalled and reinstalled then i got this when i push
"C:\android-sdk>adb push Copy /sdcard/
failed to copy 'Copy' to '/sdcard//Copy': Permission denied"
What about dab devices? Also, I think when you push a file, you need to make sure that the file is in the dab folder and the file type has to be valid. E.X.
adb push test.txt /sdcard/test.txt
Or, you could also try adb ls/
lekofraggle said:
What about dab devices? Also, I think when you push a file, you need to make sure that the file is in the dab folder and the file type has to be valid. E.X.
adb push test.txt /sdcard/test.txt
Or, you could also try adb ls/
Click to expand...
Click to collapse
a made a file inside adb folder called text and tried and again same message
C:\android-sdk>adb push text.txt /sdcard/text.txt
failed to copy 'text.txt' to '/sdcard/text.txt': Permission denied
C:\android-sdk>
also when i use adb root i can get into root and i did once adb fastboot reboot-bootloader and my kindle go into fastboot
C:\android-sdk>adb root
C:\android-sdk>adb devices
List of devices attached
D0FCA0A04206008K device
C:\android-sdk>
Hello,
I think some people asked for this, so I wrote down how I did it. I hope it helps for someone.
How to get from Ubuntu on the Meizu 5 Pro to Android.
Here is a little guide of how I installed Android (Flyme, CM and AICP) on my Meizu 5 Pro Ubuntu edition.
My desktop pc is running Ubuntu, so these commands are for the Ubuntu terminal. But should be very similar on Windows, probably.
First, install ADB and Fastboot on your pc :
Code:
sudo apt-get update
sudo apt-get install fastboot adb
Connect the Meizu phone to your pc with a usb cable. Then power up the Meizu 5 Pro with both the power button and volume down.
You’ll see a screen like this:
Type:
Code:
sudo fastboot devices
If all went well you’ll see a screen with an number/letter combination with the text fastboot behind it.
Now download TWRP_3.0_m86.img from http://xep.8800.org/pro5/.
With the next command you are going to flash TWRP custom recovery to your phone.
Code:
sudo fastboot flash recovery TWRP_3.0_m86.img
This should be done pretty fast. Power off your phone, and restart it with volume up and power button both pressed.
If all went well you’ll see a screen like this:
Now you can copy paste zip files containing Flyme OS and Cyanogenmod, through your desktop file manager while using the USB connection. Then you can use the Install button on the recovery screen to flash the zip files.
You can also copy files to your phone with adb.
Check if adb works:
Code:
sudo adb device
If correct you’ll see something like:
Code:
List of devices attached
0123456789ABCDEF device
You can download Flyme OS here: http://www.flymeos.com/firmwarelist?modelId=10&type=1
For Cyanogenmod look here: http://forum.xda-developers.com/mei...m-cyanogenmod12-1-temasek-unofficial-t3358744
I will install Flyme OS on my phone, but the procedure is just the same for Cyanogenmod. The next command copies the file to your phone:
Code:
sudo adb push -p update.zip /sdcard/
Where is update.zip is the file on your pc, and sdcard is the destination on your phone. Off course you’ll have to be in the same folder as the update.zip if you copy my command directly. If the download is in Downloads and your terminal shows:
Code:
[email protected]:~$
That means you are in your home directory. So either navigate to Downloads with cd Downloads, or change update.zip to Downloads/update.zip.
Now go back to the recovery. Press Install en browse to /sdcard/ If the operation succeeded you’ll see this:
Select update.zip and flash to confirm. Reboot. The recovery will probably ask if you want to install SuperSU, but that didn't work for me. I needed to download a different version of SuperSU and flash it to make it work.
There it is: Android on your Ubuntu Edition.
Thank you: Faust93 and all other people here on XDA for helping me learn stuff about phones and computers. I hope I can give something back by making this guide.
If you have any question, please ask. I'll try to answer them. I'm also making a back up file through TWRP, if anyone is interested, let me know.
Thank you for the guide. It would be very helpful when I get my device. If it's on stock again soon ?
Is there a way to restore Ubuntu on it? I suppose if you flash Ubuntu again using twrp it would work. No?
Sent from my GT-I9100 using XDA-Developers mobile app
Thank you!
Restoring Ubuntu is a little bit more difficult, but I have done it several times now. Going back an forth from Android to Ubuntu. I made a different guide about it, just now. Here
But it might not be easy for Windows users. So I will try to see if I can make a full backup with TWRP, so people can recover that. But I haven't tested that yet.
First of all, thanks for the tut
I have some weird problem, after flashing CM (everything went fine), I tried to reboot and it will only reboot to recovery.
No matter what I try.
I tried:
Re-flashing TWRP (I can go into fastboot mode)
Wiping everything & re-flashing cm
Wiping everything & re-flashing ubuntu (your other tut, always boots into recovery aswell)
Also tried the reboot option in TWRP, aswell as hard reboot
Tried changing/repairing filesystem of all partitions
Only method that works is if I erase recovery, then system works fine but I do not really want to have a phone without a recovery
Any other ideas?
EDIT:
I just flashed flyme recovery, used the clean option, re-flashed TWRP and now everything is working fine again
Meizu pro 5 ubuntu
I tried to install android with windows 10 but the procedure doesn't work like ubuntu.
Can please someone post a step by step method from a windows 10 pc how to from ubuntu to android?
Thank you in advance.
Thanks
got error " cannot load 'TWRP_3.0_m86.img' " what can i do ?
I'm missing something...
First, install ADB and Fastboot on your pc :
Code:
sudo apt-get update
sudo apt-get install fastboot adb
Connect the Meizu phone to your pc with a usb cable. Then power up the Meizu 5 Pro with both the power button and volume down.
You’ll see a screen like this:
Type:
:sudo fastboot devices
If all went well you’ll see a screen with an number/letter combination with the text fastboot behind it.
With the next command you are going to flash TWRP custom recovery to your phone.
Code:
sudo fastboot flash recovery TWRP_3.0_m86.img
This should be done pretty fast. Power off your phone, and restart it with volume up and power button both pressed.
I'm using Ubuntu 16.04 LTS.
Everything goes good ADB list a device. however when I tell it to :sudo fastboot flash recovery TWRP_3.0_m86.img
the terminal says:
[email protected]:~$ sudo adb fastboot flash recovery TWRP_3.0_m86.img
[sudo] password for tamashii:
Android Debug Bridge version 1.0.32
Revision debian
-a - directs adb to listen on all interfaces for a connection
-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is running.
-s <specific device> - directs command to the device or emulator with the given
serial number or qualifier. Overrides ANDROID_SERIAL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
-H - Name of adb server host (default: localhost)
-P - Port of adb server (default: 5037)
devices [-l] - list all connected devices
('-l' will also list device qualifiers)
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devices.
device commands:
adb push [-p] <local> <remote>
- copy file/dir to device
('-p' to display the transfer progress)
adb pull [-p] [-a] <remote> [<local>]
- copy file/dir from device
('-p' to display the transfer progress)
('-a' means copy timestamp and mode)
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward --list - list all forward socket connections.
the format is a list of lines with the following format:
<serial> " " <local> " " <remote> "\n"
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb forward --no-rebind <local> <remote>
- same as 'adb forward <local> <remote>' but fails
if <local> is already forwarded
adb forward --remove <local> - remove a specific forward socket connection
adb forward --remove-all - remove all forward socket connections
adb reverse --list - list all reverse socket connections from device
adb reverse <remote> <local> - reverse socket connections
reverse specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
adb reverse --norebind <remote> <local>
- same as 'adb reverse <remote> <local>' but fails
if <remote> is already reversed.
adb reverse --remove <remote>
- remove a specific reversed socket connection
adb reverse --remove-all - remove all reversed socket connections from device
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-lrtsdg] <file>
- push this package file to the device and install it
(-l: forward lock application)
(-r: replace existing application)
(-t: allow test packages)
(-s: install application on sdcard)
(-d: allow version code downgrade)
(-g: grant all runtime permissions)
adb install-multiple [-lrtsdpg] <file...>
- push this package file to the device and install it
(-l: forward lock application)
(-r: replace existing application)
(-t: allow test packages)
(-s: install application on sdcard)
(-d: allow version code downgrade)
(-p: partial application install)
(-g: grant all runtime permissions)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories)
adb bugreport - return all information from the device
that should be included in a bug report.
adb backup [-f <file>] [-apk|-noapk] [-obb|-noobb] [-shared|-noshared] [-all] [-system|-nosystem] [<packages...>]
- write an archive of the device's data to <file>.
If no -f option is supplied then the data is written
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks themselves
in the archive; the default is noapk.)
(-obb|-noobb enable/disable backup of any installed apk expansion
(aka .obb) files associated with each application; the default
is noobb.)
(-shared|-noshared enable/disable backup of the device's
shared storage / SD card contents; the default is noshared.)
(-all means to back up all installed applications)
(-system|-nosystem toggles whether -all automatically includes
system applications; the default is to include system apps)
(<packages...> is the list of applications to be backed up. If
the -all or -shared flags are passed, then the package
list is optional. Applications explicitly given on the
command line will be included even if -nosystem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup archive
adb disable-verity - disable dm-verity checking on USERDEBUG builds
adb enable-verity - re-enable dm-verity checking on USERDEBUG builds
adb keygen <file> - generate adb public/private key. The private key is stored in <file>,
and the public key is stored in <file>.pub. Any existing files
are overwritten.
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb get-devpath - prints: <device-path>
adb remount - remounts the /system, /vendor (if present) and /oem (if present) partitions on the device read-write
adb reboot [bootloader|recovery]
- reboots the device, optionally into the bootloader or recovery program.
adb reboot sideload - reboots the device into the sideload mode in recovery program (adb root required).
adb reboot sideload-auto-reboot
- reboots into the sideload mode, then reboots automatically after the sideload regardless of the result.
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb unroot - restarts the adbd daemon without root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on the specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, /system, /vendor (if present), /oem (if present) and /data partitions will be updated.
- If it is "system", "vendor", "oem" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list of the following values
1 or all, adb, sockets, packets, rwx, usb, sync, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes priority over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these debug tags are printed.
Sooo what did I do wrong? Did I miss a command (file location) or (destination)??
Thanks for your awesome work on this.
TamashiiTora said:
[email protected]:~$ sudo adb fastboot flash recovery TWRP_3.0_m86.img
Click to expand...
Click to collapse
Hi Tamashii! You should type
Code:
sudo fastboot flash recovery TWRP_3.0_m86.img
.
PS: it's better not to use sudo. You can add an udev rule for your device. You can find some advices here.
abePdIta said:
Hi Tamashii! You should type
Code:
sudo fastboot flash recovery TWRP_3.0_m86.img
.
QUOTE]
You are the Man! I never thought of that... thanks! I got CM loaded up and it's running good.
Click to expand...
Click to collapse
Storage full after installation
Hi Thank you for the guide, it is very helpful.
I have installed the Flyme OS successfully. But my phone's storage is showing only 25GB and more that 24GB is occupied. Should I wipe any specific partition before installing Flyme?
low menory
I have the same problem. Any solutions?
keerthi_cit said:
Hi Thank you for the guide, it is very helpful.
I have installed the Flyme OS successfully. But my phone's storage is showing only 25GB and more that 24GB is occupied. Should I wipe any specific partition before installing Flyme?
Click to expand...
Click to collapse
Search on root of device for folder phablet
I installed the Flyme as instructed and it worked fine, but now the bootloader is (locked, unrooted) and i can't get it to unlock! fastboot oem unlock does nothing, but says ok. How do i get it unlocked again? This Flyme OS is crap.
alestonut said:
I installed the Flyme as instructed and it worked fine, but now the bootloader is (locked, unrooted) and i can't get it to unlock! fastboot oem unlock does nothing, but says ok. How do i get it unlocked again? This Flyme OS is crap.
Click to expand...
Click to collapse
I tried to get the unlocked loader in many ways, nothing happened. Maybe there are some craftsmen who can do this. I can upload files like lk lk2 and others, I do not know exactly, but I think it's the bootloader checks the preloader exactly meizu account Officially the manufacturer Do not want to give instructions on how to unlock the bootloader Help tell me how to do this?
ubuntu to android
Get to this stage and get message " cannot load 'TWRP_3.0_m86.img' " and it won't go any further . am i doing something wrong ??