Related
[HOW-TO] Install & Use ADB tool | Android Debug Bridge | Drivers - Videos - Tutorial
WHAT DO I NEED?
FIRST: You need drivers, you should have them already if you are rooted eather with Indirect or Cfoesch methods.
If you don't have them then download ADB + Fastboot + Drivers.zip [There is NO need to install SDK on Windows]
To install Nook Tablet USB and ADB drivers correctly please watch the following video:
1. Windows
2. Ubuntu Linux
{
"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"
}
SECOND: In order to use "adb remount" you need to install [App]: ADB Root Hijack [ADB Runs as Root now] by Indirect
LET'S START...
*All the examples refers to /data/app path you can change to /system/app or any other path you need in your NOOK tablet
- Plug your Nook tablet to your computer
- Open a CMD terminal on Windows:
Start>>run>> type cmd>> click OK (WinXP)
Start>> in search box type cmd>> right click Run as Administrator (Win7)
- Once opened type:
*Let's say your adb tools are in C:\nookroot folder
cd C:\nookroot
adb devices (If you get a code of numbers and letter means your device is recognized, if not then something is wrong with your drivers > Troubleshoot)
adb remount (to change from r/o to r/w)
-----------------------------------------------------
Commands to Fix Permissions: (There is no need of this, when you push files it gives right permissions)
adb shell chmod 644 /system/app/appname.apk (for a specific application)
adb shell chmod 644 /data/app/appname.apk
adb shell chmod 644 /system/app/*.apk (for all the applications)
adb shell chmod 644 /data/app/*.apk
-----------------------------------------------------
Commands to Change Owner to Root:
adb shell chown root /system/app/appname.apk
Click to expand...
Click to collapse
Installing an Aplication .apk
Put the .apk file into C:\nookroot folder and type
Code:
adb install [B]appname[/B].apk
Uninstalling an Aplication
There is an uninstall adb commans that always shows failure!!!
So we are going to use Adb Shell:
Code:
adb shell
# cd data/app
# ls
# rm -r appname.apk
# ls (You will not find this application, you just removed it!)
Ctrl+c to exit shell mode
Push & Pull commands
Pull:
Code:
adb pull /data/app/appname.apk
If you want to PULL all the files located in a folder then:
Code:
adb pull /data/app test
to pull all the .apk's located /data/app and save them into a folder that it will create in C:\nookroot named test
Push:
Code:
adb push appname.apk /data/app
If you want to PUSH all the files located in a folder then:
Code:
adb push test /data/app
to push all the .apk's located in C:\nookroot\test folder to /data/app
Close ADB
Code:
adb reboot (to reboot your Nook Tablet)
--------------------------
adb kill-server (to stop adb server)
exit
good! is there a menu that contains full adb commands?
Nicely done. This is the best write up of how to use basic adb commands I have seen. Thanks for posting..
ms2003 said:
good! is there a menu that contains full adb commands?
Click to expand...
Click to collapse
type adb help to get the full list of them
Where's the troubleshooting FAQ? My Nook shows up as an Android phone in Device Manager, and adb doesn't list it.
Nevermind, got the drivers installed right. Stupid Windows.
Update april/10!!!
Added video to install SDK and ADB tools in Ubuntu Linux
~ Veronica
How do you change the name of a file??
Thank you
coolfreebies
coolfreebies said:
How do you change the name of a file??
Thank you
coolfreebies
Click to expand...
Click to collapse
If you refer to the .ini file ln windows, right click then edit. If on Ubunto, right click then open with the a text editor (i dont remember the name - just woke up lol).
~ V
Sent from my Nook Tablet using xda premium
Excellent. This will come in handy once I get time to start rooting the NT. Thanks
I am trying to create a batch file to run the ADB pull command so I can have my PC task scheduler run an Android backup automatically.
The one thing that is stumping me, though, is how to succesfully have the batch file auto date stamp the folder. I have this:
adb pull /sdcard/ /Galaxy Nexus Auto Backup/sdcard %date:~-10,2%-%date:~-7,2%-%date:~-4,4%/
which displays correctly in the CMD prompt, but doesn't run. It instead brings up the list of commands and switches.
If I use the standard:
adb pull /sdcard/ /sdcard/
it works correctly. Any suggestions on how to get the date stamp idea to work?
Thanks!!!
-David
Hello, a link took me here because i want to know how to use "adb".
I've read your instructions on how to use adb and i search it in youtube to see it in action.
Now i want to know the difference of these commands:
adb install
and
adb push
because im confused. but i believe they're both the same,am i right? to install an app.
and same as the adb pull and adb shell? uninstalling the app.
please, correct me if im wrong
This is a bit confusing... I bricked my Infinity and I need it back ASAP, but whenever I try to push a custom ROM into the SD, it always says "protocol failure", what could this be? I got the adb drivers installed...
Win 8 Driver Signature Enforcement Fix
Well, this is my first post on xda. BTW I am a noob, regular schlub, loser user but I do try to take xda's "find it before you ask an idiotic question" policy to heart. I was able to find this solution before asking for help and thought i would share it here. All I have done is summarize the original post and updates. I hope y'all find this helpful.
the problem i ran into was the drivers in the attached .zip file could not be installed on a Windows 8 machine. The error was a failure to install b/c of an error in reading the has of one of the catalog files. I found a site that gives you a solution to this error.. Here's a summary:
Go to cmd prompt and enter "| shutdown -o -r -t 0"
Wait for bit...
Click TROUBLESHOOT
Click ADVANCED OPTIONS
Click WINDOWS STARTUP SETTINGS
Click RESTART
The computer will restart and list of options will appear before logging in.
Select the Disable driver signature enforcement option. It was number 7 on the list i got.
To reenable the driver signature enforcement, just restart your computer normally.
Since this is my first post xda won't let me link the source site, so here it is below in case you would like to visit it. All credit goes to this guy.:good:
laslow.net/2012/03/14/disable-driver-signature-enforcement-in-windows-8/
Can you developers help me please!!
I've been doing just fine with ADB, etc. I have been flashing for a long time and now all of a sudden ADB is not working. I've installed SDK twice, unistalled and installed drivers. Did everything. I get it that this just won't work on Windows 7 so I'm back on XP where I never had a problem and currently am. Yes, debugging is on on the phone too. I'm above the basics. When I plug in an LG it just says sooner ADB (something like that and I know your familiar). When I plug in a Samsung device manager says Samusng Android Composite ADB interface. And when I direct the driver install to winsub inf I always get "the specified location does not contain information about your device". Also ADB devices is not recognizing anything either. I event tried this with the Samsung in download mode.
Thanx
Good tutorial, it´s help me a lot. Thanks!!!
How do I know where adb install ?
PalAlexander said:
How do I know where adb install ?
Click to expand...
Click to collapse
On Windows, typically C:\Program Files\Android\android-sdk\platform-tools\
ADB use instructions clearly formatted for referenxce
Hi, this is a post I just hope will be helpful. When I started using ADB I would look at the internal Help and the formatting was so screwed up it was hard to understand. Fighting with this for the umpteenth time last night I got mad, pulled out a code editor (too bad it wasn't emacs because that's probably the way the file was made-- either that or it was created as a man page) and spent a half hour straightening things out. The help is so much more useful now I'm putting it here in the hope it may help you, too. Now let's see if I should have formatted this as Code rather than a Quote to keep lines from breaking, etc.
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 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 r unning.
-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 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 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 i
<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 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 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 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 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 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
Best wishes,
Leon Malinofsky
lavero.burgos said:
WHAT DO I NEED?
FIRST: You need drivers, you should have them already if you are rooted eather with Indirect or Cfoesch methods.
If you don't have them then download ADB + Fastboot + Drivers.zip [There is NO need to install SDK on Windows]
To install Nook Tablet USB and ADB drivers correctly please watch the following video:
1. Windows
2. Ubuntu Linux
SECOND: In order to use "adb remount" you need to install [App]: ADB Root Hijack [ADB Runs as Root now] by Indirect
LET'S START...
*All the examples refers to /data/app path you can change to /system/app or any other path you need in your NOOK tablet
- Plug your Nook tablet to your computer
- Open a CMD terminal on Windows:
Start>>run>> type cmd>> click OK (WinXP)
Start>> in search box type cmd>> right click Run as Administrator (Win7)
- Once opened type:
*Let's say your adb tools are in C:\nookroot folder
Installing an Aplication .apk
Put the .apk file into C:\nookroot folder and type
Code:
adb install [B]appname[/B].apk
Uninstalling an Aplication
There is an uninstall adb commans that always shows failure!!!
So we are going to use Adb Shell:
Code:
adb shell
# cd data/app
# ls
# rm -r appname.apk
# ls (You will not find this application, you just removed it!)
Ctrl+c to exit shell mode
Push & Pull commands
Pull:
Code:
adb pull /data/app/appname.apk
If you want to PULL all the files located in a folder then:
Code:
adb pull /data/app test
to pull all the .apk's located /data/app and save them into a folder that it will create in C:\nookroot named test
Push:
Code:
adb push appname.apk /data/app
If you want to PUSH all the files located in a folder then:
Code:
adb push test /data/app
to push all the .apk's located in C:\nookroot\test folder to /data/app
Close ADB
Code:
adb reboot (to reboot your Nook Tablet)
--------------------------
adb kill-server (to stop adb server)
exit
Click to expand...
Click to collapse
When I run "adb devices" in command prompt, it says "list of devices attached" then a blank line.
The drivers for my tablet are fine because in 'My computer' my drive is listed as 'Xolo TW800' along with other HDD drives, without me installing any drivers for the tablet.
What to do?
Thanks
[TOOL]ADB + Fastboot v1.0.31 for OS X/4.3 [NOW Includes ADB & Fastboot][08-17-2013]
ADB & FASTBOOT FOR OS X
There has been some confusion since I discuss using Fastboot in this post, but the zip only contained ADB. This is completely my fault and I apologize. Either way I've updated the .zip to include ADB & Fastboot.UPDATED: 08/17/2013 - Added Fastboot to adb-1.0.31-mac.zip
I've seen several people having issues on OS X trying to use ADB since the release of Android 4.3. In my case ADB recognized my device, but each time I ran adb devices my device would be reported as offline. I downloaded the SDK from Google several times and always ended up with ADB v1.0.29 (4.2.2).
This will should solve your OS X & ADB issues if you're running Android 4.3. This ONLY includes the ADB & Fastboot executable files and is for Mac OS X ONLY. I, like many others, do not need the full SDK. If you're not an app developer, like myself, this is all you need to have ADB working on your machine.
For any new OS X users I'll add a how to just so you don't have to go search for it else where:
How to setup ADB + Fastboot on OS X
Note: This is for not for developers. This only includes ADB & Fastboot and is not the full Android SDK
Step 1: Download the ZIP containing ADB & Fastboot
Step 2: Extract the ZIP to the directory of your choice
Step 3: Optional Create an environment variable
1. Open Terminal
2. Type cd to take you to your home directory.
Code:
cd
3. Type touch .profile to create a hidden file in your home directory named .profile
Code:
touch .profile
4. Type open -e .profile to open the file you just created in TextEdit
Code:
open -e .profile
5. In the file, add the following:
Code:
export PATH=${PATH}:/PathToDirectoryWhereYouExtractedTheZIP
6. Save the file and close TextEdit, quit Terminal, and relaunch the Terminal
Step 4: In Terminal type adb devices, you should see your phone's corresponding serial number Ex: HXM1005HNF012345 device
Code:
adb devices
Note: If you choose not to create an environment variable from Step 3 it effects two things:
1. You will need to cd to the directory containing ADB each time you want to run ADB.
2. When executing ADB commands you will need to add ./ in front of ADB. Ex: ./adb devices
Dropbox Download
Alternate Download
wad3g, thanks for helping out.. but for some reason adb version is still showing 1.0.29 for me. I extracted the zip, removed the old adb and fasboot, restarted my machine.. ran kill-server, start-server but no luck.. any ideas? not sure what to do at this point.
mamba_nz said:
wad3g, thanks for helping out.. but for some reason adb version is still showing 1.0.29 for me. I extracted the zip, removed the old adb and fasboot, restarted my machine.. ran kill-server, start-server but no luck.. any ideas? not sure what to do at this point.
Click to expand...
Click to collapse
Hey, I was having the same issue so I took the adb and fastboot files from the SDK. You can copy them to usr/bin/ and run normally (as if the third step in the op's post had been completed), or by following the op's procedure if you're not an admin user.
kunjunk said:
Hey, I was having the same issue so I took the adb and fastboot files from the SDK. You can copy them to usr/bin/ and run normally (as if the third step in the op's post had been completed), or by following the op's procedure if you're not an admin user.
Click to expand...
Click to collapse
Thank you so much!
For some reason, that zip still reports ADB version 1.0.29.
I found the latest version (1.0.31) from https://ftp.mozilla.org/pub/mozilla.org/labs/r2d2b2g/. It has zips for linux, mac and windows adb.
kunjunk said:
Hey, I was having the same issue so I took the adb and fastboot files from the SDK. You can copy them to usr/bin/ and run normally (as if the third step in the op's post had been completed), or by following the op's procedure if you're not an admin user.
Click to expand...
Click to collapse
thanks that works fine 4 me
DISCLAIMER: ROOTING YOUR PHONE WILL PROBABLY VOID YOUR WARRANTY FROM BOTH THE CARRIER AND THE MANUFACTURER. IF YOU DO NOT WISH TO ACCEPT FAULT FOR ANY ADVERSE EFFECTS OF ROOTING, THEN DO NOT READ ANY FURTHER.
Please note that I am in no way responsible for any accident or loss of data caused by using this method to root your device. All ownership of potential risks and accidental damage will lie entirely with the user.
==========================
Instructions
==========================
1) Download the atached files:
http://forum.xda-developers.com/attachment.php?attachmentid=3333235&stc=1&d=1432679727
2)Install on your device the following aplications:
-"USB Debug" in order to enable USB Debugging (open and enable USB Debugging) ("\\Root kit\me.tennkia.apr.apk")
-"ADB Wireless (no root)" - wireless adb
("\\Root kit\Useful\ADB-Over-WiFi-Helper\helper\Helper.apk"
Launch the aplication and a IP will be displayed. (In my case was: 192.168.0.15:5555)
2)Open "cmd.exe" from Root Kit folder and type the following commands:
adb connect "192.168.0.15:5555" // enter between " " your device IP !!!
adb devices // it is used to check the connection (The conection should be listed)
adb push zergRush /data/local/ // This method uses zergRush
adb shell
chmod 755 /data/local/zergRush
/data/local/zergRush
### if finished succesfuly type the following:
adb connect "192.168.0.15:5555" // enter between " " your device IP !!!
adb remount
adb push su /system/bin/su
adb push su /system/bin/
adb shell
then insert:
chown root.shell /system/bin/su
chmod 06755 /system/bin/su
ln -s /system/bin/su /system/xbin/su
exit
adb push Superuser.apk /system/app/
===============
Optional steps:
===============
2.1) Add application which will be automatically installed after factory reset:
adb push ApplicationName /system/app/
Note: The applications you wish to add with this command should be added inside the root kit folder. ( Right where is :"Superuser.apk")
2.2) Delete unwanted aplications:
adb shell rm /system/app/"ApplicationName".apk
Note: Use the following command to view the default aplications on your device:
adb shell ls /system/app
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Warning: Do not remove aplications that are needed for the proper operation of your device!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
===============================
3) Disconnect from the device:
adb disconnect
4) Open "SuperSU" aplication and update the binary SU(Normal)
5) Restart the device (recomanded) and test if root is available.
6)Congrats! Your device is now rooted
hi, my phone ulefone armor 6e, I cannot upload firmware because the computer cannot see the phone. I tried all methods on 3 different cables and 3 different computers, in normal mode and fastboot mode, the computer does not see the phone. I installed the drivers properly, but when I connect the phone to the computer, there is no reaction or movement in the device manager section. The interesting thing is that the fast charging feature is lost. It also charges slowly when I plug it into wireless charging.
So i m trying this way, wifi debug and root using adb. but attach files not here, what can i do? please help
Broken link! Please fix!
faysoft said:
hi, my phone ulefone armor 6e, I cannot upload firmware because the computer cannot see the phone. I tried all methods on 3 different cables and 3 different computers, in normal mode and fastboot mode, the computer does not see the phone. I installed the drivers properly, but when I connect the phone to the computer, there is no reaction or movement in the device manager section. The interesting thing is that the fast charging feature is lost. It also charges slowly when I plug it into wireless charging.
So i m trying this way, wifi debug and root using adb. but attach files not here, what can i do? please help
Click to expand...
Click to collapse
Check ur charging port is in good condition or not.you had mentioned about slow charging,this is because ur charging port of ur is not good it may lead data transfer not able to work properly .
1. Better check ur charging port in service center about the data tranfer not working
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 ??
i am on macosx and installed android studio
the adb and fastboot and driver (kext) for android are broken in such the following ways
1. adb
it is not detecting even virtual machine , tried all the version
when i run ./adb usb or ./adb devices for the first time
it is not showing thing like
Dameon starting up bla bla
and run quietly and freezes
sudo ./adb devices
List of devices attached
*** it freezes i.e keep waiting
sudo ./adb usb
** it freezes and waiting
even
sudo ./adb kill-server
**8 it is freezing and waiting
sudo ./adb start-server
** it is waiting
i have given it all permission
chmod 777 adb
platform-tools Prodesign$ sudo ./adb start-server ** it is waiting
2. fastboot
./fastboot-mac devices
ERROR: could not get pipe properties
HQ65XBS32030 fastboot
fastboot oem get_identifier_token
ERROR: could not get pipe properties
... // i tired a htc android
not a single android in adb pr fastboot is working correctly
there is not adb_usb.ini file in sdk folder of adb also new adb does not uses adb_usb.ini file
also i added that file and device if like 0x1368 even though it is not working
Please help