[How To] Collect as much info to help solve your problem - Xperia SP Q&A, Help & Troubleshooting

How to collect data​In this thread you can read all about collecting data to help yourself and us users with fixing your issues or problems. In this thread I will explain a some things with screenshots. If you have questions do not hesitate to post or contact me!​
1: How to collect Wakelocks?​What is a Wakelock?
- A wakelock is an application, service or process that prevents the phone from getting into deepsleep.
What is DeepSleep?
- DeepSleep is the name of the state from the CPU. In this state is the CPU almost off. The CPU is in a sort 'Stand-by" function where it keeps the needed functions working (like calls, sms, contact with your operator). In DeepSleep the battery usage is very low. When you turn your screen back on the CPU will start running normal again.
Where can I check my battery stats?
- See picture:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To collect the wakelock data you need an application that collect this. Here on XDA-Developers there is an application called Better Battery Stats it can be found here: Link. This application is free here on XDA and costs about €2 in the Google Playstore (which is more than fair since it is an amazing application).
There is another one which I use a lot: WakeLock Detector. This one can be found for free in the Google Play Store: Link
When you have installed a Wakelock Detector you need to use your phone as you normaly do. Do this for 24 hours to get as much data as possible. If you install BetterBatteryStats, root is needed for extra detailed information (see its thread). With the application WakeLock Detector you can see systemwakelocks aswell. However you need to enable this in settings see below:
After you use your phone for a while you will see a list like this:
(mine is very short because its connected to my pc)
If you see some "for your eyes" weird ones. Google them. Most of them can be found either here on XDA or on any other Android website
An amazing thread about WakeLocks and How to prevent them: Link.
You can check a bit futher. For other wakelocks you can select between a few diffrent settings:
For system wakelocks you can see a bit more. Some wakelocks do have its own wakelocks. For example Google Service has more in it than you might thing. By clicking on the wakelock you can see exact what the cause of the wakelock is:
2: How to create a logcat​A logcat is a logfile which tells us what the Android System is doing and where the things go wrong and what the cause may be. The logcat has some very nice information... if you know how to read them.
The only thing needed is ADB.
What is ADB?
- ADB stands for Android Debug Brigde. And is used for Debugging in Android. It is also needed to pull and push files and to fix things and even to help you deodex your ROM. It has some handy commands to remember..
Normaly ADB comes with the Android SDK kit which you can download here: Link.
Where can I find ADB Commands?
- See below:
Code:
-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
envivornment 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
disconnect <host>:<port> - disconnect from a TCP/IP device
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
(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] <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)
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 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 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.
To use ADB on your device you need to enable "USB Debugging"
Here is how:
If you have that enabled you need to install ADB. Google it. There are a lot of guides you can follow so I am not gonna write it down here.
When you have enabled USB Debugging and ADB is installed you can go futher.
To create a logcat you need to check if your device has been found by the pc and ADB.
To do so open a commantprompt and enter the following command:
Code:
Adb Devices
This will pull a list like this:
When there is no device it will show this:
To create a logcat enter the following command
Code:
adb logcat
If you press enter this will happen:
This is impossible to collect and to read. So we need to sort this out.
Try to use this command to sort it out:
Code:
adb logcat -v long > name of problem.txt
This command makes every logline seperate so that you will get a clean file that is a bit easier to read.
The output file can be found in C:\[name of drive]\[user]
When you have your file you need to understand it. Every single line starts with a letter. This letter has a purpose:
Code:
V — Verbose (lowest priority)
D — Debug
I — Info (default priority)
W — Warning
E — Error
F — Fatal
S — Silent (highest priority, on which nothing is ever printed)
Most of us will give the entire log to the developers of an application or ROM. But with this you can try to solve problems on your own.
- Work in progress - ​

#Reserved

Now lets hope people will read this, they should.
Maybe you could also add a part about the fact that XDA has a search function and therefor it is not needed to start a new thread for every question people want an answer too, as most of the times answers are already available. *WHY WONT IT READ* hehe.
And about logging, the free app "Syslog" is very useful for people who have a hard time using ADB.
Nog een laatstje puntje, misschien de screens in het Engels maken? Je hebt natuurlijk de logos die vrij duidelijk zijn, maar het staat wel beter

Robin>Hood said:
Now lets hope people will read this, they should.
Maybe you could also add a part about the fact that XDA has a search function and therefor it is not needed to start a new thread for every question people want an answer too, as most of the times answers are already available. *WHY WONT IT READ* hehe.
And about logging, the free app "Syslog" is very useful for people who have a hard time using ADB.
Nog een laatstje puntje, misschien de screens in het Engels maken? Je hebt natuurlijk de logos die vrij duidelijk zijn, maar het staat wel beter
Click to expand...
Click to collapse
Then I have to make them all over.. En dat is rot werk... :silly:

Related

Got ADB running, now what?

So I'm trying to get the Gapps from this link http://nookdevs.com/NookColor:_Nookie_Froyo_Tips#3rd-Party_App_support. I believe I got ADB and the drivers installed correctly. Now what do I do. I open up CMD and when I put in the first line of that script, it basically says $ is not a recognized command or something along those lines. I'm so close to doing the last thing I want to, but can't get over this hump. Can someone give me the play by play on what to do?
Don't type the $. The $ is representing the typical command prompt in *nix (such as Linux) based OSes. You just need to enter everything after the $.
Ok, after I do the first line of
adb shell mount -o remount,rw /dev/block/mmcblk1p2 /system
adb push C:\Documents and Settings\g018807\Desktop\system/
adb reboot
It won't let me type anything else or paste anything else. What am I doing wrong?
Is their anyone who can take me through this?
now I'm just getting ADB not found.
When you issue the command "adb devices" (without quotes), what do you see? Anything? If you see nothing, then your device isn't connected.
eyecrispy said:
When you issue the command "adb devices" (without quotes), what do you see? Anything? If you see nothing, then your device isn't connected.
Click to expand...
Click to collapse
It says list of devices attached
*****numbers* Device
Now it's back to the point where after I hit ADB Shell it just doesn't let me type anything.
Does it just lock up? can you try cntl-C out of it? Other than adb shell, can you do any other adb commands? like adb push or adb pull?
eyecrispy said:
Does it just lock up? can you try cntl-C out of it? Other than adb shell, can you do any other adb commands? like adb push or adb pull?
Click to expand...
Click to collapse
I can cntl-c out of it. If I type push or pull it gives me this
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 have USB debugging on, and I turned on storage mode. Are both of those right?
buffnutz1 said:
I have USB debugging on, and I turned on storage mode. Are both of those right?
Click to expand...
Click to collapse
Yeah, USB debugging is definitely needed. Having storage mode on is fine too.
But let's slow down and back up a little here. Btw, I'm not trying to be condescending with the following. Just being thorough.
First, unplug your Nook from USB. Next, on the Nook uncheck then recheck USB debugging. Now back up to the Home screen.
If you're running Windows Vista/7, make sure you're running command prompt as Administrator. Better safe than sorry. Now at a command prompt type:
adb kill-server
There won't be any result but you should get back to the command prompt.
Now connect the Nook via USB and type:
adb devices
This is just to re-connect your Nook to your computer. You should get a result like:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
xxxxxxxxxxxxxxxxxx device
Click to expand...
Click to collapse
Now type:
adb shell
If you don't get a $ (unrooted) or # (rooted) prompt, then I think there is something wrong with the drivers you installed.
If you do get a $ or # prompt, type:
exit
You should be back to your command prompt.
If you get this far, re-extract or move the zip from http://nookdevs.com/NookColor:_Nookie_Froyo_Tips#3rd-Party_App_support to C:\Temp.
At a command prompt type:
cd C:\Temp
dir
You should get something like
Volume in drive C has no label.
Volume Serial Number is B077-0836
Directory of C:\Temp
02/15/2011 03:06 PM <DIR> .
02/15/2011 03:06 PM <DIR> ..
02/15/2011 03:06 PM <DIR> META-INF
02/15/2011 03:06 PM <DIR> system
0 File(s) 0 bytes
4 Dir(s) 20,067,143,680 bytes free
Click to expand...
Click to collapse
Now type (or copy/paste):
adb shell mount -o remount,rw /dev/block/mmcblk1p2 /system
You should get back to a command prompt. Now type (or copy/paste):
adb push "C:\Temp\system" system/
Again you should get back to a command prompt. Now type (or copy/paste):
adb reboot
This will reboot your Nook and the Google Apps will be available.
You are seriously the best friggin guy ever. Thanks so much. I was missing this entire step
cd C:\Temp
dir
No problem. Actually I'm glad it worked because I just realized that my steps were assuming that you have Froyo on a micro SD card. This wouldn't have worked if you had Froyo on the internal memory. Also, that step you missed is really not necessary. That's just to make sure you had the zip extracted properly. In any case, good to hear it worked out.
Try this here>nookdevs{dotcom}/NookColor_USB_ADB
^ please insert .com for {dotcom} as i cant post links since i dont have enough posts, this forum is good but kinda harsh towards newcomers, otherwise love the forum.
I was stuck at the same spot as you and took me forever to find the fix until i stumbled upon that page. Im in Ubuntu 10.04 so i cant speak for the windows procedure, but it worked perfect for me. I now have HC v3 with gapps thanks to that site. hope this helps
I'm having similar issues. Unfortunately I'm leaving for Fl. for 4 days. As an aside, it would be great if there were some kind of adb gui program for windows. Something were instead of manually entering dos commands like "/dev/block/mmcblk1p2 /system" you could just browse to your nooks system dir. and drop the file in question. Probably just dreaming here. Anyway, I will try your guide as soon as I get back. Cant wait!

[Q] how do i get s off

can anyone help me get s off please i have unlocked my bootloader and have managed to get cmw installed but i cant find a way of getting s off i have the sensation xl x315e i looked at the wire trick but my phone does not have holes in the back to connect a wire to
southard26 said:
can anyone help me get s off please i have unlocked my bootloader and have managed to get cmw installed but i cant find a way of getting s off i have the sensation xl x315e i looked at the wire trick but my phone does not have holes in the back to connect a wire to
Click to expand...
Click to collapse
Have a look at this: http://forum.xda-developers.com/showthread.php?t=1865265.
This tool will do it for you (credit to Lexmazter), option 5 or 6, depending on what Android version you are on.
No need to do the wire trick, that is not for XL...
have tryed this when i ask to remove s off loads of information comes up then it just ends with a # and does nothing
southard26 said:
have tryed this when i ask to remove s off loads of information comes up then it just ends with a # and does nothing
Click to expand...
Click to collapse
I didn' try the tool myself, so I cannot help you further about it.
Otherwise you can go 2 ways: ask Lexmazter for help or go on unlimited.io and follow their instructions (as I did). If you follow the guide carefully you will get s-off :fingers-crossed:
have you got a link for unlimited.io please and this is what i get when i do multi tool flasher 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.
~ #
Sure.
This is the link to the guide: http://www.unlimited.io/runnymede.htm
On the right side you can download HBOOT. choose the one you need (unprotected version).
Sorry, but I can't understand what the log from the tool is showing...
ok so when i get to part 4 i get this
1|[email protected]:/ # dd if=/data/local/tmp/hboot_7230ddr2_Runnymede_6.28.6667.nb0
of=/dev/block/mmcblk0p18
230ddr2_Runnymede_6.28.6667.nb0of=/dev/block/mmcblk0p18 <
/data/local/tmp/hboot_7230ddr2_Runnymede_6.28.6667.nb0of=/dev/block/mmcblk0p18:
cannot open for read: No such file or directory
southard26 said:
ok so when i get to part 4 i get this
1|[email protected]:/ # dd if=/data/local/tmp/hboot_7230ddr2_Runnymede_6.28.6667.nb0
of=/dev/block/mmcblk0p18
230ddr2_Runnymede_6.28.6667.nb0of=/dev/block/mmcblk0p18 <
/data/local/tmp/hboot_7230ddr2_Runnymede_6.28.6667.nb0of=/dev/block/mmcblk0p18:
cannot open for read: No such file or directory
Click to expand...
Click to collapse
It seems you have typed something wrong. Maybe it happened when you performed adb push in step 1, since it reports it can't find the file or the directory. Try to repeat the whole sequence controlling exactly what you are typing.
i copy the text word for word and still get the same message it makes no sence
Weird... have you mounted system partition as writable? Is USB debug enabled? And still: are you going through the process while your device is powered on and your ROM fully loaded?
i have now got s off but since doing my memory card wont mount even when i plug phone into computer i don't even get the disk drive icon on my phone to select almost as if it don't exist and my phone says insert memory card
Try Multi Mount SD-Card from market. It should help fixing that issue.
southard26 said:
i have now got s off but since doing my memory card wont mount even when i plug phone into computer i don't even get the disk drive icon on my phone to select almost as if it don't exist and my phone says insert memory card
Click to expand...
Click to collapse
This problem often occurs when you have a different HBOOT version of ROM, for instance if you have 1.25 Hboot and flash a 1.28 ROM, this is what you get, same applies if you flash a different HBOOT over a existing version of ROM already installed
Hope this helps
--
As for the tool, it provides the same flashing steps as the one presented on unlimited.io, but it does all that without the need of you to kill you fingers reading and interptreting all that, is a script, that is what scripts do

[GUIDE] How to ADB Push to fix a formatted /sdcard (Mac + PC)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This guide will help you to restore your phone if you happen to have wiped your internal sdcard and have no way of getting your phone to boot to a functional state.
This method is 99.9% safe, and should anyone break their phones as a direct result of this guide, I will send a donation
Requirements: A computer running either Windows or Mac
An unlocked bootloader, which can be achieved at http://www.htcdev.com/bootloader
This guide, best served cold, comes in three parts:
Unlocking the bootloader
Installing the ADB drivers
Restoring your phone
Feel free to skip to the part you require, and I hazard a guess at saying most people can skip straight to the third and most important part, where the magic actually happens.
Unlockin' the bootloader
First off, you need to head over to HTC Dev and select 'All Other Supported Models' in the little drop down menu, then press the big green button as shown.
This will then require you to register, and you can then follow the steps provided by HTC. Obviously, during this process you're gonna come to a point where ADB drivers are needed to flash your unlock token, so take a peek down the page. I aren't going into detail with this unlock guide because I am fully aware that there are detailed guides elsewhere in the forums, from people who have a lot more time to sit and explain things than I do.
Installin' the ADB drivers
Howdy partner, this here thang be the most important thing you can ever do regarding your Android and PC ecosystem, and you're gonna be hella glad that you did it. After installing ADB, you're free to enjoy the wonderful world that is logcats, custom recoveries, ROMs, kernels; the whole package!
First off, select your OS!​
Windows 7
Congratulations! You have managed to avoid the flop that is Windows 8, kudos to you.
First, head over to HTC Sync Manager and download this and install, to gain the required drivers.
Now, head over to the Android SDK and download it, using the big blue download button. Simpless.
Extract this zip file to the root of your C:/ drive.
Now you're done! To check it's working, open the platform-tools folder of the SDK and then hold down Shift, Right Click and press 'Open Command Window here'.
Now, type
Code:
adb devices
If your device is plugged in, and powered into Android or a custom recovery, it should appear as a serial number here!
Windows 8
Sorry to hear you're stuck with the latest and far from greatest iteration of Windows, but don't let that Metro interface get you down! Lets crack on.
First, head over to HTC Sync Manager and download this and install, to gain the required drivers.
Now, head over to the Android SDK and download it, using the big blue download button. Simpless.
Extract this zip file to the root of your C:/ drive.
Now you're done! To check it's working, open the platform-tools folder of the SDK and then hold down Shift, Right Click and press 'Open Command Window here'.
Now, type
Code:
adb devices
If your device is plugged in, and powered into Android or a custom recovery, it should appear as a serial number here!
Mac
Finally, someone with a good taste in operating systems This is the easiest thing you will do all day, believe me.
First, head over to HTC Sync Manager and download this and install, to gain the required drivers.
Now, head over to the Android SDK and download it, using the big blue download button. Simpless.
Locate the zip, or folder (if you have 'Open "safe" files' turned on) in your Downloads folder and drag it to your Desktop. If it ain't extracted, give it a double click to extract it.
Now open the folder and navigate to 'platform-tools'. Drag this to your Desktop out of the main folder.
Open Terminal and type:
Code:
cd Desktop/platform-tools
./adb devices
If your phone is plugged in, and powered into Android or a custom recovery, the serial number will show up here. Congrats, adb is set up, now lets restore your phone.
Usin' ADB Push
So, you're stuck in recovery and cannot boot, or you just need to transfer a file to your phone for whatever reason... This is the method to transfer a rom back onto your phone, in order to make it fully functional again. This works in both recovery and booted Android, meaning it is also a good way to transfer music and photos when your phone boots again. This process doesn't wipe any data.
First, open platform-tools (your adb folder as described above). Download any ROM from the HTC One section of XDA and drag the .zip inside here
Hold down Shift and Right-Click, selecting 'Open Command Window Here'.
On a Mac, open Terminal and type;
Code:
cd Desktop/platform-tools
to achieve the same result.
Now, we are ready to use the ADB push command.
Plug your phone into your computer in recovery mode, and in CMD type:
Code:
adb push NameOfRom.zip /data/media/
Be aware that on Android 4.2.2, you need to type '/data/media/0/'
On a Mac, type:
Code:
./adb push NameOfRom.zip /data/media/
(or /data/media/0/ if coming from a 4.2.2 rom)
Now, wait for the process to complete. This takes on average around 260 seconds for a 900mb rom, with no progress indicator. Don't worry, it hasn't frozen.
When it completes, type:
Code:
adb reboot recovery
or
Code:
./adb reboot recovery
on a Mac.
Your file can now be found on your sdcard, and can be flashed from the 'Install zip from sdcard' screen.
That's it, you have saved your phone, and can now get back to using it again!​
Annddd I've posted this in the wrong section by accident... Sorry I was too excited about finishing ;D
Great tutorial. I wish I had seen that a couple of days ago when I accidentally wiped my internal SD and had no ROM to flash. Thanks to the members here and hours and hours of Googling, though, I was able o get ADB working. Bookmarked!
Great work - this should be a sticky on the Q & A page. This issue/problem comes up 2 or 3 times per day. Especially since 4.2.2 releases came out.
Sent from my HTC One using xda premium
Sticked until August 1st. If there is still a problem with formatted sd-cards then, we will re-asess.
I can't believe there are still people around android who don't know how to push I had to do that as well as I had my internal SD wiped too during the S-OFFing/unlocking...
One a bit OT, but does anyone know why the TWRP lacks the advanced "mount USB storage" feature? I had that one on my OneX....
Cheers
Dr.Romca said:
I can't believe there are still people around android who don't know how to push I had to do that as well as I had my internal SD wiped too during the S-OFFing/unlocking...
One a bit OT, but does anyone know why the TWRP lacks the advanced "mount USB storage" feature? I had that one on my OneX....
Cheers
Click to expand...
Click to collapse
Neither TWRP nor CWM are able to Mount USB Storage anymore and I have no idea why. They were not able to mount on my Galaxy S3 either.
thnx
thanks you very much it helps me allot
thanks again
anyone know how to get around this so it actually pushes teh rom to the phone?
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.
TarekElsakka said:
Neither TWRP nor CWM are able to Mount USB Storage anymore and I have no idea why. They were not able to mount on my Galaxy S3 either.
Click to expand...
Click to collapse
at least they allow to use OTG to install roms, so (if you have the cable) you just can wipe the internal sd, and flash using an usb with OTG :good:
SLver said:
at least they allow to use OTG to install roms, so (if you have the cable) you just can wipe the internal sd, and flash using an usb with OTG :good:
Click to expand...
Click to collapse
Yeah, I'm aware of that. I went ahead and ordered an OTG cable when I mistakenly wiped my internal SD card before. It arrived about four days later, though, so I had already fixed the problem. I am sure when I want to do a fresh install, it'll make life much easier than having to sideload or push using ADB.
Great guide although i'm a bit stuck, when I run the ./adb push Rom.zip /data/media/0 command it says:
-bash: /Users/archiedennis/Desktop/platform-tools: is a directory
Any ideas anyone?
Running OSX btw
JustArchiee said:
Great guide although i'm a bit stuck, when I run the ./adb push Rom.zip /data/media/0 command it says:
-bash: /Users/archiedennis/Desktop/platform-tools: is a directory
Any ideas anyone?
Running OSX btw
Click to expand...
Click to collapse
./adb push rom.zip /data/media/0/
MacHackz said:
./adb push rom.zip /data/media/0/
Click to expand...
Click to collapse
sry for noob question.. but adb won't show my device
have latest drivers and htc sync installed.. it was working before, now it just won't
fcjan said:
sry for noob question.. but adb won't show my device
have latest drivers and htc sync installed.. it was working before, now it just won't
Click to expand...
Click to collapse
Download and run this: http://adbdriver.com/upload/AdbDriverInstaller.exe
MacHackz said:
Download and run this: http://adbdriver.com/upload/AdbDriverInstaller.exe
Click to expand...
Click to collapse
thanks.. now there is a another problem -.-
I was trying to do a clean install of ARHD, had some problems..
enter CM recovery, tested adb (working)
wipe data/factory reset, wipe cache, wipe /sdcard.. full wipe
now adb is saying
C:\adb>adb devices
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
FIXED.. had do delete adb.exe in HTC Sync folder, it works now.. thank you!
MacHackz said:
./adb push rom.zip /data/media/0/
Click to expand...
Click to collapse
Nope still the same thing :L
Dude!!! You are the greatest! Help me alot and saved my weekend *muchlove*
An all nighter, os X and Win7, 8 hours later you saved me. Thanks!
crash087 said:
anyone know how to get around this so it actually pushes teh rom to the phone?
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.
Click to expand...
Click to collapse
I'm having the EXACT same issue....

[Q] help me adb sideload

-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
disconnect <host>:<port> - disconnect from a TCP/IP device
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
(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.
When I type "adb sideload filename.zip" cmd show me this. what's the problem?
Help this company said:
-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
disconnect <host>:<port> - disconnect from a TCP/IP device
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
(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.
When I type "adb sideload filename.zip" cmd show me this. what's the problem?
Click to expand...
Click to collapse
filename.zip needs to be replaced with the actual name of the rom.zip you are trying to upload. Try these for instructions
http://forum.xda-developers.com/showthread.php?t=2318497
mb_guy said:
filename.zip needs to be replaced with the actual name of the rom.zip you are trying to upload. Try these for instructions
http://forum.xda-developers.com/showthread.php?t=2318497
Click to expand...
Click to collapse
U mean that dont rename the file name? And Could U tell me where the Official rom?? Ah, I downloded my korea htc cafe. That file is "pn7140 ruu.zip"file. I did several times that explain.
Help this company said:
U mean that dont rename the file name? And Could U tell me where the Official rom?? Ah, I downloded my korea htc cafe. That file is "pn7140 ruu.zip"file. I did several times that explain.
Click to expand...
Click to collapse
I assumed you had not renamed the file to pn7140 ruu.zip since you are getting the help page information.
Is the actual file in the same directory folder as adb? It should be. You might rename the file to something shorted like just "pn7140.zip" to make it easier.
a
mb_guy said:
I assumed you had not renamed the file to pn7140 ruu.zip since you are getting the help page information.
Is the actual file in the same directory folder as adb? It should be. You might rename the file to something shorted like just "pn7140.zip" to make it easier.
Click to expand...
Click to collapse
adb sideload is only custum rom?? my device not booting just only logo. Whats the problem...
Help this company said:
U mean that dont rename the file name? And Could U tell me where the Official rom?? Ah, I downloded my korea htc cafe. That file is "pn7140 ruu.zip"file. I did several times that explain.
Click to expand...
Click to collapse
3 threads for the same issue.....
Thread 1
Thread 2
We were trying to help you in the other thread (thread 2). Why did you started two new threads? This only complicates things and makes it difficult to help you
5. Create a thread or post a message only once.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer.
Click to expand...
Click to collapse
http://forum.xda-developers.com/announcement.php?a=81
Help this company said:
adb sideload is only custum rom?? my device not booting just only logo. Whats the problem...
Click to expand...
Click to collapse
Alray had suggested you flash a custom rom like arhd, Are you not trying to do that??
Help this company said:
adb sideload is only custum rom?? my device not booting just only logo. Whats the problem...
Click to expand...
Click to collapse
Adb sideload is a feature of custom recovery (TWRP / CWM). You must boot to recovery and start sideload feature before running adb sideload from command prompt, otherwise adb doesn't recognize the command and displays the help text instead.
sprint lg optimus g
im trying to get my phone working, my kid picked it up when it was in twrp and started having fun... guess she did a full wipe. lol. anyway problem is now i can do adb devices and see phone, but when i swipe sideload it says host not sideload.
Wheelindude said:
im trying to get my phone working, my kid picked it up when it was in twrp and started having fun... guess she did a full wipe. lol. anyway problem is now i can do adb devices and see phone, but when i swipe sideload it says host not sideload.
Click to expand...
Click to collapse
You are currently in the HTC One Q&A forum better to ask your question in the right forum, everything you will find here may not apply to your phone. Here is the link for the Sprint LG Optimus G forums: http://forum.xda-developers.com/optimus-g-sprint

[RECOVERY][ Unofficially Open Recovery TWRP 2.8.1.0 ][ 09/11/2014 ]

Team Win Recovery Project !​​​​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Permanent TWRP Recovery 2.8.1.0
Huawei Ascend P7
Changelog :
Code:
What's new in 2.8.1.0 :
[CENTER]* MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
* TrueType Font support - optional as it takes up a decent amount of space so may not be available on all devices - thanks to Tassadar
* Temperature support - thanks to bigbiff
* Various other bugfixes and tweaks[/CENTER]
Downloads :
Code:
[CENTER]
* [B][I][SIZE="5"][COLOR="DeepSkyBlue"]New Update :[/COLOR][/SIZE][/I][/B] [URL="http://forum.xda-developers.com/showpost.php?p=56613952&postcount=176"]TWRP 2.8.1.0[/URL] !
* [URL="https://www.androidfilehost.com/?fid=23622183712471290"]openrecovery-twrp-2.8.0.0.img[/URL]
* openrecovery-twrp-2.7.1.0.img -> [URL="http://www.androidfilehost.com/?fid=23501681358560545"]openrecovery-twrp-2.7.1.0.v1.rar[/URL]
Installation :
Code:
[CENTER]
* [FONT="Arial Black"]Make Sure That Your Device Has Already Unlocked Bootloader ![/FONT]
* [B][I]Make Sure That You Have Already Removed "/system/set_immutable.list" Or Restore Your Previous Backup Will Fail ![/I][/B]
[LIST]
[*] For TWRP 2.8.0.0 :
[LIST]
[*] boot your device in bootloader mode :$ adb reboot bootloader
[*] flash custom twrp recovery :$ (sudo*) fastboot flash recovery openrecovery-twrp-2.8.0.0.img
[*] reboot your device :$ (sudo*) fastboot reboot
[*] * only for Ubuntu 14.xx !
[/LIST]
[*] For TWRP 2.7.1.0 :
[LIST]
[*] extract recovery image ( openrecovery-twrp-2.7.1.0 ) from archive openrecovery-twrp-2.7.1.0.v1.rar
[*] boot your device in bootloader mode :$ adb reboot bootloader
[*] flash custom twrp recovery :$ fastboot flash recovery openrecovery-twrp-2.7.1.0.img
[*] reboot your device :$ fastboot reboot
[/LIST]
[/LIST]
[/CENTER]
Issues :
Code:
[CENTER]
* Internal Storage Not Mount ;
* Wipe -> Advanced Wipe -> Internal Storage -> Repair or Change File System -> Cannot Be Done : [B][COLOR="Red"]Invalid partition selection[/COLOR][/B] ;[/CENTER]
Source :
Code:
[CENTER]* [URL="https://github.com/TeamWin/Team-Win-Recovery-Project/tree/twrp2.7"]TeamWin GitHub[/URL] !
* TWRP Huawei Ascend P7 -> [URL="https://github.com/surdupetru/p7_twrp"]GitHub[/URL]
[/CENTER]
Stock Recovery Ascend P7 :
Code:
[CENTER]
* [URL="http://forum.xda-developers.com/showpost.php?p=53980121&postcount=4"]Huawei Ascend P7-L10[/URL] thanks to [URL="http://forum.xda-developers.com/member.php?u=2775894"]XQC[/URL] ;
* [URL="http://forum.xda-developers.com/showpost.php?p=53981881&postcount=6"]Huawei Ascend P7-L00[/URL] thanks to [URL="http://forum.xda-developers.com/member.php?u=266181"]olegusss[/URL] ;
[/CENTER]
Credit :
Code:
[CENTER]* [URL="http://teamw.in/project/twrp2"][B]Team[COLOR="RoyalBlue"]Win[/B][/COLOR][/URL]
* [URL="http://forum.xda-developers.com/showthread.php?t=1943625"]Dees_Troy[/URL][/CENTER]
* Thanks for helping me with all info about P7 : [URL="http://forum.xda-developers.com/member.php?u=4221381"]Max4000[/URL] ; [URL="http://forum.xda-developers.com/member.php?u=2775894"]XQC[/URL] ; [URL="http://forum.xda-developers.com/member.php?u=266181"]olegusss[/URL] ; [URL="http://forum.xda-developers.com/member.php?u=5536121"]bibiloi[/URL]
​
Screenshots :
[/CENTER]
regards,
Surdu Petru
Please after test, report all issue !
I'll try to solve a part of them in the next update !
When you report an issue, please add this file ( > adb pull /cache/recovery/last_log ) -> to be able to see what was wrong !
Huawei Ascend P7 Donors :
Code:
[CENTER]* [URL="http://forum.xda-developers.com/member.php?u=4221381"]Max4000[/URL]
* [URL="http://forum.xda-developers.com/member.php?u=3456823"]zema1971[/URL]
* [B]Matthias Metz[/B]
* [URL="http://forum.xda-developers.com/member.php?u=5845719"]arthios[/URL]
* [URL="http://forum.xda-developers.com/member.php?u=4424350"]RICKROCKER[/URL]
* [URL="http://forum.xda-developers.com/member.php?u=5496921"]DJ BlackEagle[/URL]
* [B]Thorsten Legrand [/B]
* [URL="http://forum.xda-developers.com/member.php?u=5053142"]Superwitschi[/URL]
* [URL="http://forum.xda-developers.com/member.php?u=4640096"]julianceed[/URL]
* [URL="http://forum.xda-developers.com/member.php?u=4424350"]RICKROCKER[/URL]
* [URL="http://forum.xda-developers.com/member.php?u=4424350"]RICKROCKER[/URL]
* [URL="http://forum.xda-developers.com/member.php?u=3455314"]jack4280[/URL]
* [URL="http://forum.xda-developers.com/member.php?u=5355423"]seschaum[/URL]
* [URL="http://forum.xda-developers.com/member.php?u=519375"]mikesa[/URL]
* [URL="http://forum.xda-developers.com/member.php?u=1394516"]jesana1976 [/URL]
* [URL="http://forum.xda-developers.com/member.php?u=5650623"]craescu[/URL]
* [B]Ian Hawkins[/B]
* [URL="http://forum.xda-developers.com/member.php?u=5903110"]xdadevelkl[/URL]
* [B]Klaus Dosser[/B]
* [URL="http://forum.xda-developers.com/member.php?u=3032432"]Mik Komarov[/URL]
* [URL="http://forum.xda-developers.com/member.php?u=287963"]helowsa[/URL]
* [URL="http://forum.xda-developers.com/member.php?u=4424350"]RICKROCKER[/URL]
* [URL="http://forum.xda-developers.com/member.php?u=1217290"]hvy109[/URL]
* [URL="http://forum.xda-developers.com/member.php?u=6095039"]unimatrix_zero[/URL]
* [URL="http://forum.xda-developers.com/member.php?u=4224069"]Stryker_SK[/URL]
* [URL="http://forum.xda-developers.com/member.php?u=5863453"]3nDrold[/URL]
[B][I][FONT="Century Gothic"][COLOR="DarkOrange"]Thank you all very very much !!![/COLOR][/FONT][/I][/B]
[/CENTER]
​
Hats Off
Hats Off To You Sir !
You Have Done An Amazing Job Here
I wanted To ask will this work with all variants for specific ones only i have The P7-L10
andromodgod said:
Hats Off To You Sir !
You Have Done An Amazing Job Here
I wanted To ask will this work with all variants for specific ones only i have The P7-L10
Click to expand...
Click to collapse
This custom recovery is based on P7-L10 but should be works in all variants as well.
That`s great thanks very much
Nice job man! But are there any Roms available/ being worked on?
Thanks!!
Beukhof1 said:
Nice job man! But are there any Roms available/ being worked on?
Thanks!!
Click to expand...
Click to collapse
Thank you very much !
Once this device will enter in the hands of a developer, definitely will not delay to appear and some custom AOSP based ROMs!
Unfortunately I do not possess such a device - to be able to start this works !
Best regards !
Maybe we can crowdfund an device for you?
Max4000 said:
Maybe we can crowdfund an device for you?
Click to expand...
Click to collapse
Would be awesome, mate - thank you very much .
Provide us PayPal and/or bitcoin link. I hope I'm not the only one who is thankful for your work and would like to spend some money to see more of your great work on the P7.
Max4000 said:
Provide us PayPal and/or bitcoin link. I hope I'm not the only one who is thankful for your work and would like to spend some money to see more of your great work on the P7.
Click to expand...
Click to collapse
Once you check "
DONATE TO ME
Click to expand...
Click to collapse
" button under my avatar , you are able to send by PayPal.
Also I can provide a updated list with all donors for P7 ....
Another idea would be a loan phone for a longer period, it must not be new - but anyway you have a great idea !
Yeah I would really like to have cm11 on my p7!!
surdu_petru said:
Once you check "" button under my avatar , you are able to send by PayPal.
Click to expand...
Click to collapse
Transaction ID 7JR60444E71939453
I'll spread the idea in the russian and german forums so maybe we will get enough money for a brand new dev P7 for you.
Max4000 said:
Transaction ID 7JR60444E71939453
I'll spread the idea in the russian and german forums so maybe we will get enough money for a brand new dev P7 for you.
Click to expand...
Click to collapse
Confirmed !
Thank you very much for your donation ! :good:
Edit :
List of Donors for P7, opened on the second post .
Transaction ID:
57R99491RG623854L
That is going to be my little contribution to the work you are doing
zema1971 said:
Transaction ID:
57R99491RG623854L
That is going to be my little contribution to the work you are doing
Click to expand...
Click to collapse
Thank you very much for your donation , list of donors ( on the second post ) was already updated .
Good luck !
surdu_petru said:
Please after test, report all issue !
I'll try to solve a part of them in the next update !
When you report an issue, please add this file ( > adb pull /cache/recovery/last_log ) -> to be able to see what was wrong ! ​
Click to expand...
Click to collapse
I report my issue, restore dont work (FAILED), thanks Surdu:
Code:
C:\platform-tools>adb pull/cache/recovery/last_log
Android Debug Bridge version 1.0.31
-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 <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 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 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 instal
l 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)
('--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] [-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 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:\platform-tools>
jkmaxfli said:
I report my issue, restore dont work (FAILED), thanks Surdu:
Code:
C:\platform-tools>adb pull/cache/recovery/last_log
Android Debug Bridge version 1.0.31
-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 <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 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 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 instal
l 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)
('--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] [-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 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:\platform-tools>
Click to expand...
Click to collapse
So far I see you forgot a space between pull and /cache.
Originally Posted by taaeem
So far I see you forgot a space between pull and /cache.
Click to expand...
Click to collapse
It must be correctly without the space between pull and /cache. , look at the log dump .
Code:
C:\platform-tools>adb pull /cache/recovery/last_log
error: device not found
C:\platform-tools>adb pull/cache/recovery/last_log
Android Debug Bridge version 1.0.31
-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 <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 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 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 instal
l 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)
('--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] [-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 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:\platform-tools>
Do any of you know how to change the DPI on the p7? There is nothing in the build.prop.

Categories

Resources