Related
[GUIDE] UNLOCK - ROOT - RETURN TO STOCK and/ or UNBRICK your Nexus 7 3G “Nakasig- Tilapia” v4.2.2
- Disclaimer: I don't take any responsibility for anything you do to your tablet, which is to transform it into brick, break, or transform it into coffee machine -
Requirements:
1. You must have the sdk (ADT Bundle for Win) installed on your Pc and you are able to access, and use adb and fastboot.
NOTE: Notice the install location. This defaults to C:\Users\<user name>\AppData\Local\Android\android-sdk the platform tools (adb, fastboot) and usb drivers will be downloaded to this location. This will be referred to from here on as your sdk directory
But in case you haven't install all SDK, you can use only fastboot by the easy way.(Go here if you want to use the easy way to fastboot)
2. You must have ticked USB Debugging mode in your Nexus 7 3G
3 You must download and install - USB DRIVERS r_06 for Windows 7 & 8
4. Download one of both root-tool
CF- Auto-Root by Chainfire - Download link for Version Tilapia - Nakasig
or the Superboot r4 by Paul O’Brien - Actually I'm not sure if Superboot is functionnal for version 4.2.2 - I tested with my Grouper v4.2.2 and I stayed in Google screen with bootloop.
5. Download your recovery special for your Tilapia - Nakasig
CWM (Touch version or not)
TWRP - latest versions
ClockworkMod - Google Nexus 7 (GSM) - Superuser (fixed) for Android 4.2.
and rename your select with the name of the recovery image you chose to download.
6. The factory image for the Nexus 7 3G => 4.2.2 (JDQ39) - nakasig-jdq39-factory-0798439d.tgz - md5: ee8db1ed6ff1c007fe12136d4bc65cd8- size: 279.9MB - The Version Zip if you prefer
Click to expand...
Click to collapse
AND DON'T FORGET THAN IT'S BETTER FOR YOUR SPECIAL N7 3G+
TO USE THE SPECIAL RECOVERIES "TILAPIA - NAKASIG"
and NOT "GROUPER" WHICH ARE DIFFERENTS
Click to expand...
Click to collapse
**********************************************************************************************************************************************************************
Pre-Steps
To make this easier,
1 - you should put the root-tool.zip selected on the folder “fastboot” (if you use the easy way - Goto post #2)
2 – You should put the recovery.img selected on the folder “fastboot”
UNLOCK YOUR NEXUS 7 3G+
Click to expand...
Click to collapse
To unlock your device, you must go to your bootloader. To do that, you have possibilities;
1. Turn your device on while pressing volume down
or
1. Connect your device and go to cmd terminal
Code:
> cd \Users\<user name>\AppData\Local\Android\android-sdk\platform-tools (it's common localization for an auto install)
> adb devices
# the following output should be returned
List of devices attached
<device serial number> device
2. Boot to the bootloader by use adb
Code:
adb reboot bootloader
or
2 Bis. Boot to the bootloader by use fastboot
Code:
fastboot reboot-bootloader
3. Unlock your device* by
Code:
fastboot oem unlock
*You will have to accept and erase all of your data on the tablet.
You are unlocked :good:
By Fastboot only easy way - Unlock you device
Code:
C:\Users\Username>cd c:\fastboot
Code:
c:\fastboot>fastboot oem unlock
**********************************************************************************************************************************************************************
FLASH THE RECOVERY
Click to expand...
Click to collapse
You can choose one of both recoveries - CWM or TWRP
Flash ClockworkMod Recovery as Permanent recovery
Click to expand...
Click to collapse
(You're still inside the bootloader and connected through the usb cable)
1. Flash CWM especially for your N7 3G
Code:
fastboot flash recovery recovery-name of your recovery.img
To make CWM Permanent recovery
2. Boot into recovery by pressing “volume up” and when the menu says ‘recovery mode’ press the power button
3. Go to “Mounts and Storage” menu
4. select “mount system”
5. Type in cmd terminal
Code:
adb shell
cd /system
mv recovery-from-boot.p recovery-from-boot.bak
exit
If you having trouble gaining shell, try
Code:
adb kill-server
then
Code:
adb start-server
. And restart the lines command above
* For some people, it has been reported that you don't have to replace recovery-from-boot.bak. The flash is enough to make the recovery stick.
**********************************************************************************************************************************************************************
Flash TWRP as Permanent recovery
Click to expand...
Click to collapse
(You're still inside the bootloader and connected through the usb cable)
1. Flash TWRP especially for your N7 3G
Code:
fastboot flash recovery recovery-twrp-tilapia-2.4.4.0.img
To make TWRP Permanent recovery
2. Boot into recovery by pressing “volume up” and when the menu says ‘recovery mode’ press the power button
3. Go to “Mounts and Storage” menu
4. select “mount system”
5. Type in cmd terminal
Code:
adb shell
cd /system
mv recovery-from-boot.p recovery-from-boot.bak
exit
**********************************************************************************************************************************************************************
FOR THE ROOT
Click to expand...
Click to collapse
- [2013.02.20][N7 WiFi | N7 3G] CF-Auto-Root
Click to expand...
Click to collapse
What's installed
- SuperSU binary and APK
- Nothing else, that's it.
Installation and usage
- Download the ZIP file (see post below for link)
- Extract the ZIP file (you will see - 2 folders=> images & tools and 3 files: root-windows // root-mac // root-linux)
- Boot your device in bootloader/fastboot mode. Usually this can be done by turning your device off, then holding VolUp+VolDown+Power to turn it on.
- Connect your device to your computer using USB
- Windows:
Code:
Run root-windows.bat
- Linux
Code:
chmod +x root-linux.sh
Code:
Run root-linux.sh
- Mac OS X
Code:
chmod +x root-mac.sh
Code:
Run root-mac.sh
- [ROOT] Superboot - Nexus 7 WiFi / 3G root solution
Click to expand...
Click to collapse
How to use Superboot - Windows, Linux and OSX
- Download the Superboot zip file above and extract to a directory
- Put your device in bootloader mode - Turn off the phone then turn on with the 'volume up' and 'volume down' buttons both pressed to enter the bootloader (as pictured below)
- WINDOWS - double click 'superboot-windows.bat'
- MAC - Open a terminal window to the directory containing the files,
and type
Code:
chmod +x superboot-mac.sh
followed by
Code:
./superboot-mac.sh
- LINUX - Open a terminal window to the directory containing the files,
and type
Code:
chmod +x superboot-linux.sh
followed by
Code:
./superboot-linux.sh
**********************************************************************************************************************************************************************
RETURN TO STOCK and/or UNBRICK your N7 3G+
Click to expand...
Click to collapse
Before you begin, please make sure you have ADB and Fastboot drivers installed and working.
1. Download the factory image for the Nexus 7 3G=> 4.2.2 (JDQ39) - nakasig-jdq39-factory-0798439d.tgz - md5: ee8db1ed6ff1c007fe12136d4bc65cd8- size: 279.9MB - The Version Zip if you prefer
2. Extract the factory image into the same directory as your ADB and Fastboot executables (e.g. "\android-sdk\platform-tools")
3. Plug in your device. If you are booted into Android, open a command prompt to your ADB and Fastboot directory, then type:
Code:
adb reboot bootloader
If your device is powered off, press and hold both volume keys and the power button simultaneously. After holding all three buttons for a couple of seconds, your bootloader should launch. This should reboot you into the bootloader.
4. Type:
Code:
fastboot flash bootloader bootloader-tilapia-4.18.img
5. Type:
Code:
fastboot reboot-bootloader
6. Now type:
Code:
fastboot -w update image-nakasig-jdq39.zip
7. Optional: If you would like to relock your bootloader for warranty or security purposes, make sure you are in your bootloader screen again and type:
Code:
fastboot oem lock
8. If your tablet hasn't already rebooted automatically, you can type
Code:
fastboot reboot
Well done. You should now be back on stock Android 4.2.2
**************************************************************************************************************************************************************************************
These root tools are actually the easy way for rooting your device, so you can use them without problems.
IF YOU NEED MORE ABOUT THE NEXUS 7 3G+ "NAKASIG - TILAPIA" YOU MUST GO HERE
=> [Index]- 29 Dec 2012 - All for NEXUS 7 - "Nakasig/Tilapia" - (GSM/HSPA+)
and
=> NEXUS 7 3G-"nakasig"-For all Your Jelly Bean Discussions, Problems and Solutions
Click to expand...
Click to collapse
For my part I’ve used
the easy way by my fastboot guide for unlock my device,
Adb lines command for flash TWRP as permanent recovery,
Thanks for @mateorod, @Chainfire, @paulobrien and all members who helps for the development about the Nexus 7 3G+
The EASY WAY TO USE FASTBOOT LINES COMMAND
HELP FOR FLASH MORE FASTER WHEN YOU USE FASTBOOT LINE COMMAND
If you have got a problem with your adb or fastboot or recovery....it's very simply and faster
use this:
Download this file "fastboot.zip"
Install this file somewhere in one folder which is named "fastboot" on your PC
=> disk C: root
Unzipped this file on the folder "fastboot" and you will find 3 files:
- adb.exe
- AdbWinApi.dll
- fastboot.exe
and when you need to push something by the bootloader, you can use it.
Don't forget to push on this folder the file that you need. For exemple: boot.img or a recovery.img, etc...
The line command is :
Code:
c:\fastboot>
Enter
Code:
c:\fastboot>fastboot flash recovery recovery.img
Enter
If you want to flash the "recovery.img" file
******************************************************************
******************************************************************
If you want to know all lines of command
Code:
c:\fastboot>fastboot
Code:
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default: 2048
Reserved in case
Hello, this is my first post on xda.
When i tried use "adb fastboot bootloader" cmd say to me : no device. Where is problem?
piski93 said:
Hello, this is my first post on xda.
When i tried use "adb fastboot bootloader" cmd say to me : no device. Where is problem?
Click to expand...
Click to collapse
Try the easy way on first
Use the post 2.
You can use it for all the install, except for for the permanent recovery where you will have to use ADB line command.
The best you can do, it's to use fastboot easy way and when you have finished, you learn and install correctly your sdk and check all your parameters. And when you will be ready you will be able to use adb lines command easily to install your recovery in a permanent way.
It's too long for a course about sdk, the best you can do it's to to search and read. Go to my index, and read the General guides
Gonna try this later today. Though something is a bit fishy. When I use adb from the fastboot.zip it can't find my device but from the platform-tools dir it seems to work fine. Are they different versions? How big risk is it to brick the device while unlocking/rooting and installing recovery? Pls tell me its unbrickable. cheers
Skickat från min GT-I9300 via Tapatalk 2
znejk said:
Gonna try this later today. Though something is a bit fishy. When I use adb from the fastboot.zip it can't find my device but from the platform-tools dir it seems to work fine. Are they different versions? How big risk is it to brick the device while unlocking/rooting and installing recovery? Pls tell me its unbrickable. cheers
Click to expand...
Click to collapse
I can't says it's unbrickable !!!
The differences between these versions is:
If you use sdk/platform tools it's the more complete install and the easy way for fastboot, that just if you need to use fastboot line command, but it's not more complete for using with adb lines command.
If you go to the post 2, you will see all the lines command for fastboot.
If your sdk install is correct, you can use it without problems.
The easy way by fastboot is just a shotcut
philos64 said:
I can't says it's unbrickable !!!
The differences between these versions is:
If you use sdk/platform tools it's the more complete install and the easy way for fastboot, that just if you need to use fastboot line command, but it's not more complete for using with adb lines command.
If you go to the post 2, you will see all the lines command for fastboot.
If your sdk install is correct, you can use it without problems.
The easy way by fastboot is just a shotcut
Click to expand...
Click to collapse
I tried and everything seemed to work fine ... i Unlocked/flashed twrp then "mv recovery-from-boot.p recovery-from-boot.bak" didnt work cause it couldnt find the file... :/ i continued and flashed superboot and it seemed to work fine. Downloaded latest cm and gapps rebooted inte recovery and flashed them. Now I only have bootloop with cm10.1...
I know it aint bricked cause I think I can get into bootloader.
Edit: After a factory reset it worked! :>
znejk said:
How big risk is it to brick the device while unlocking/rooting and installing recovery? Pls tell me its unbrickable. cheers
Click to expand...
Click to collapse
The Nexus7 is very difficult to brick. It still is possible, but as far as I know there is only one way to do it - remove or destroy the bootloader.
Under normal circumstances, the only time you do anything with the bootloader is unlocking/locking it, which simply does a minor modification. That's perfectly fine. And the normal custom-recovery/root process doesn't touch it, so that's fine too. Doing system updates (even legit OTA ones) might upgrade the bootloader, as might flashing custom roms. But as long as you don't interrupt the process during that critical step, it should be OK.
So outside of erasing the bootloader or flashing a completely incompatible bootloader and rebooting, your N7 should be safe.
adb command line Linux support
Hi All,
Am new to this forum and also to my newly bought N73G. So I am unsure about the complete process though explained step by step. One thing that i wanted to confirm was Does ADT Bundle for linux work the same as that of windows? Cause I run the same on my PC; these command line instructions would they work the same way on Linux terminal?
It's not the same as Windows. You can download the ADT Bundle for Linux.
Sent from my N7 3G between sky and earth
Is there any solution for unlock and root Nexus 7 3G only with Apple Mac assistance? Thank you in advance!!!
foxstam said:
Is there any solution for unlock and root Nexus 7 3G only with Apple Mac assistance? Thank you in advance!!!
Click to expand...
Click to collapse
Can you explain what do you think by Apple Mac Assistance ?
If it's for SDK Tools, you will find here the Apple version => DOWNLOAD FOR OTHER PLATFORMS
I'm not sure which recovery images should be downloaded.
Is this one correct? - recovery-twrp-tilapia-2.3.2.1.img
what does this mean? "rename your select with the name of the recovery image you chose to download."
quote:
Requirements:
...
4. Download:
CWM (Touch version or not) or TWRP and rename your select with the name of the recovery image you chose to download.
thanks
elelab said:
I'm not sure which recovery images should be downloaded.
Is this one correct? - recovery-twrp-tilapia-2.3.2.1.img
what does this mean? "rename your select with the name of the recovery image you chose to download."
Requirements:
4. Download:
CWM (Touch version or not) or TWRP and rename your select with the name of the recovery image you chose to download.
Click to expand...
Click to collapse
Yes, you can use the recovery-twrp-tilapia-2.3.2.1.img without problem
and when I writes "rename your select with the name of the recovery image you chose to download", I mean that you can rename the IMG file by "recovery" simply. It's more faster.
minimum steps to root Nexus7(3G) - for beginners
confused by too much info. on how to root Nexus 7
can this be as simple as:
1 unlock
2 root
question:
1. unlock step - erase all of your data on the tablet
If I don't care my data (I just bought it), after unlocking, can Nexus start as normal?
2. Why do we need flash the recovery?
"Pre-Steps
To make this easier,
1 - ...
2 – You should put the recovery.img selected on the folder “fastboot” (if you use the easy way - Goto post #2)
" fastboot flash recovery recovery-twrp-tilapia-2.3.2.1.img"
does "recovery-twrp-tilapia-2.3.2.1.img" mean the "recovery.img"?
thanks
elelab said:
confused by too much info. on how to root Nexus 7
can this be as simple as:
1 unlock
2 root
question:
1. unlock step - erase all of your data on the tablet
If I don't care my data (I just bought it), after unlocking, can Nexus start as normal?
2. Why do we need flash the recovery?
Click to expand...
Click to collapse
Answers:
1 - Yes, the advert is clear, all of your data will be erased !
2 - If you want to flash a rom custom, you need a recovery
elelab said:
"Pre-Steps
To make this easier,
1 - ...
2 – You should put the recovery.img selected on the folder “fastboot” (if you use the easy way - Goto post #2)
" fastboot flash recovery recovery-twrp-tilapia-2.3.2.1.img"
does "recovery-twrp-tilapia-2.3.2.1.img" mean the "recovery.img"?
Click to expand...
Click to collapse
Yes, it's correct. it's more faster to write: "recovery.img" than "recovery-twrp-tilapia-2.3.2.1.img".
It's the same file, just rename.
This has no effect on the recovery flash
Can I root my device (4.2.2) using Superboot yet ?
Re: [GUIDE] - Updated 08 Feb - Unlock and Root a Nexus7 3G “Nakasig- Tilapia”
I received 4.2.2 update today. I haven't installed it for fear of losing root. Should i repeat the procedure to root again after updating my n7. Will i again loose my data? Or the bootloader will remain unlocked? Please help
Sent from my Nexus 7 using xda app-developers app
sukhjit_bhullar said:
I received 4.2.2 update today. I haven't installed it for fear of losing root. Should i repeat the procedure to root again after updating my n7. Will i again loose my data? Or the bootloader will remain unlocked? Please help
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I can flash UPDATE-SuperSU-v1.04.zip in CWM/TWRP recovery to get root after update from 4.2.1
You will not loose any data.
Your bootloader will upgrade to 4.18 and still unlocked.
Updated ADB and Fastboot from Androiod SDK (Pkg.Revision=24.0) dd 11/07/2016
ADB - version 1.0.36
Revision fd9e4d07b0f5-android
Download: fastboot_adb(1.0.36)_110716_r24.0.rar
The last SDK Platform-Tools for Win, Linux and Mac you can always find here - https://developer.android.com/studio/releases/platform-tools
Arhive:
ADB and Fastboot from Androiod SDK (Pkg.Revision=21, 16 Oct 2014)
*Updated ADB to version 1.0.32
*Updated Fastboot to latest version
Download:
fastboot_adb(1.0.32)_071114_r21.rar
sorry for being a noob and asking for another device in a different forum,
but will these adb drivers also work with nexus 4???
need them to sideload 5.0.1
IS this for android 5.0 GPE?
http://forum.xda-developers.com/htc-one/general/guide-windows-8-1-fastboot-adb-t2970692
i have anaged to get it working after expereincing the problems stated here by others ... follow my steps here for those who still have trouble
lewonsky said:
IS this for android 5.0 GPE?
Click to expand...
Click to collapse
Yes, this for all version. It' latest update from official Android SDK Platforms.
See link in OP.
Golv said:
ADB and Fastboot from Androiod SDK (Pkg.Revision=21, 16 Oct 2014)
*Updated ADB to version 1.0.32
*Updated Fastboot to latest version
Download:
fastboot_adb(1.0.32)_071114_r21.rar
Click to expand...
Click to collapse
I think you forgot to mention that this is only for Windows. So it does not work for Linux or Mac.
Quick, fast, no frills, just the necessary files itself. Hopefully this thread gets updated whenever a new release comes up
thanks, nice share bro :good:
how to use those files
I thank you for the files but... how are we supposed to use them. I ask since I'm new to adb. And need this vision of adb to sideload to my fire hd6
[email protected] said:
I thank you for the files but... how are we supposed to use them. I ask since I'm new to adb. And need this vision of adb to sideload to my fire hd6
Click to expand...
Click to collapse
open a command window and change directory to the folder where adb.exe is installed. Then you can use adb commands. Commands syntax is as follow:
Code:
adb [target] <command>
You only need to specify the [target] if you have more than 1 android device or emulator connected simultaneously, otherwise the command will be directed to the only connected device, so the syntax will be:
Code:
adb <command>
So if you want to sideload a rom to your device, boot in your custom recovery and start the "sideload" mode.
In the command window:
Code:
adb sideload my_rom.zip
Don't forget that the rom.zip must be in the same folder where adb.exe is
If you want to use "adb push" instead of "adb sideload" then boot in custom recovery (not in sideload mode) and use the following command:
Code:
adb push my_rom.zip /sdcard
You can read more about adb commands here: http://developer.android.com/tools/help/adb.html#issuingcommands
adb sideload explained here: http://android-revolution-hd.blogspot.in/2013/12/ow-to-use-adb-sideload.html
If you have more question about what file to sideload or push a rom to your device, you should ask in the correct forum, Amazon Fire HD 6 forum is here: http://forum.xda-developers.com/fire-hd
thank u
save my day
How do you install the new adb 1.0.32 over the old version and will it work with the moto X 2014?
its dosnt work for me
and i need it ((
every phone i want use sideload , its say me , use adb 1.0.32 or newer
and when i want use adb 1.0.32 , show me this error in all adb commands :
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error: unknown host service
what should i do ?
update adb
[email protected] said:
I thank you for the files but... how are we supposed to use them. I ask since I'm new to adb. And need this vision of adb to sideload to my fire hd6
Click to expand...
Click to collapse
go to this website: https://fl1.androidfilehost.com/dl/...803384/minimal_adb_fastboot_v1.3.1_setup.exe?
download and install it to your computer, then try to sideload it through there.
if that doesn't work just download the stand alone SDK from the android studio website and after its downloaded, open the .rar file and extract it to a new folder to your desktop. after that open it and search for a folder that says platform tools and look for the ADB .exe file and copy it, then go to your C drive and go to programs and try to find the android studio folder, when you have located it open it and look for a folder named platform tools, then delete the adb.exe in that folder and paste the new one in there or you can probably just copy the whole platform tools folder and replace the other one in the C drive.
I hope this helps, if it doesnt just message me and im sorry for the late reply.
alishadlou said:
* failed to start daemon *
error: unknown host service
what should i do ?
Click to expand...
Click to collapse
this usually means the phone is not communicating with your PC.
- either your phone is corrupt
- the connection is corrupt
- or the cable is bad
Tip: add the path of ADB.exe to your system Environment Variables, so you can call it w/out first navigating to it.
- Right click Computer > Properties > Advanced system settings
- Environment Variables ... > edit "Path" by adding the path to ADB.exe.
ie.
Windows 10 x64, i simply add: D:\PortableApps\ADB
for other Windows, you may have to add to the end of "Path", click edit > scroll to the end > add ;D:\PortableApps\ADB;
(don't forget to add the semicolon at the end)
Now you can simply launch Command Prompt and enter: ADB sideload *file*
Updated ADB and Fastboot from Androiod SDK (Pkg.Revision=24.0) dd 11/07/2016
ADB - version 1.0.36
Revision fd9e4d07b0f5-android
Download: fastboot_adb(1.0.36)_110716_r24.0.rar
Not working on Android 6.0
This and older versions will not work on Samsung S7E for system backup and restore.
It accepts the commands, but the confirmation popup supposed to open on the device never does. For a few 6.0 users on other devices, it opened up but the backups were not really completed.
thanks bro. nice share :good:
Thanks, you save me too much time!!
my adb was working fine for my Note 4. I followed the instructions to upgrade bootloader
https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144
Now, I keep getting device offline when used adb devices command. Do you think, upgrading ADB will solve this? thank you
INTRODUCTION:
This GUIDE contains instructions on how to setup your Mac for Flashing Firmwares and ROMS using your Mac. This guide contains downloads of the latest ADB and Fastboot (extracted from the latest Android SDK for Mac OS X) that are compatible with the Mac OS X operating system (Supports Yosemite also).
Click to expand...
Click to collapse
COMPATIBILITY:
Supports from OS X Mountain Lion to the latest OS X Yosemite (10.10)
Click to expand...
Click to collapse
FEATURES:
Fully Compatible & Ready to use, No need to use any other Terminal commands to convert the downloaded scripts.
No more ./ before commands. Just type adb <command> or fastboot <command>
Click to expand...
Click to collapse
INSTRUCTIONS:
Download the given zip file from below and extract it's contents into a folder. (Preferably create a New Folder in the Desktop.
Open the folder and Install MDM_Installer_2.1.8.dmg
After Installation of the Motorola Drivers, Reboot (Recommended).
After Reboot, Open Terminal, cd to the folder to which you extracted the adb and fastboot files.
Connect your Device (Enable USB Debugging) and try:
Code:
adb devices
You will see adb daemon starting up.
Your device serial number along with state will be displayed.
Now you are ready to use your Mac for flashing your Moto devices. Copy the files for flashing into this folder and follow the respective guides for flashing.
Click to expand...
Click to collapse
DOWNLOAD:
moto_adb_mac.zip (13 MB)
Click to expand...
Click to collapse
FAQ:
My Device is listed as offline.
Try reconnecting the device in another USB port on your Mac.
My Device is listed as Unauthorised.
Unlock your device and grant permission to enable USB Debugging on the Mac. (A notification with the Mac's RSA fingerprint will be displayed).
Click to expand...
Click to collapse
Hope this helps you guys. Keep rocking XDA!
Works on Mac OSX 10.11 also?
Thank you for providing a method for flashing the Moto g 2014 using a Mac. Before I download the files, I would like to know if they are compatible with Mac OSX v 10.11 as well?
Thanks
Hello,
I am in need of setting ADB and Fastboot on my Macbook Pro (OS: Mac El Capitan - 10.11.6). I tried to download the flip file showed under Download.
Download fails with "Google Drive -- Page Not Found" error. Please help me to get latest versions of these tools. I am stuck w/o them.
Warm Regards,
Ravi
After month of searching to find a way to use fastboot on Linux Mint for my ZE551ML, Minimal_adb_fastboot from GitHub work.
https://github.com/simmac/minimal_adb_fastboot
note: I use software manager to remove ADB and FastBoot.
After uncompress Minimal_adb_fastboot,
I double click on install.sh and click on run in terminal => he voila it work!
To test types in terminal
sudo adb reboot bootloader
sudo fastboot devices
Please do not replay with thanks, use the thanks button instead.
This is simply ADB/Fastboot, with a Graphical User Interface.
Click to expand...
Click to collapse
HOW-TO
• Installation
make sure you have java installed on your PC
• first you have to install adb system-wide:
[windows] : try ADB Installer tool.
[Linux] : adb support comes with most Linux distributions.
• then run Simple-ADB.jar and that's it!
[Windows shortcut]
[Linux shortcut]
Click to expand...
Click to collapse
• Usage
• select from "ADB", "Fastboot" or "Your command" modes:
- if "ADB" is selected the dropdown will contain lots of adb commands :
adb devices -l
adb connect <host>
adb disconnect
adb usb
adb logcat
adb install
adb uninstall
adb push
adb pull
adb kill-all
adb shell top
adb shell free
adb shell ps,
adb shell netstat,
adb shell pm list packages,
busybox df -h
rm /data/system/gesture.key
adb reboot
adb reboot recovery
adb reboot download
adb reboot bootloader
adb reboot fastboot
adb reboot sideload
adb help
adb kill-server
- if "Fastboot" is selected the dropdown will contain lots of Fastboot commands :
fastboot devices -l
fastboot reboot-bootloader
fastboot erase system
fastboot erase data
fastboot erase cache
fastboot flash
fastboot flash recovery
fastboot flash boot
fastboot flash system
fastboot flash data
fastboot flash cache
fastboot flash userdata
fastboot flash bootloader
fastboot flash radio
fastboot help
- if "Your command" is selected the dropdown will be disabled , and you can write your own command.
• You can Save output from the Options menu or simply press Ctrl+S.
Click to expand...
Click to collapse
COMPATIBILITY
• Windows
• Linux (Thanks a lot for @topnomi for testing and confirming Linux support, follow his Instructions for linux).
• Mac OS (read this post for details)
TO-DO/FIX
• fix memory leak because of large output to the JTextArea [(e.g during adb logcat).
• support for Mac (I really don't know why it's not working there, contributions are always welcome!)
Code:
*** Disclaimer
there are some commands I've never tested (like password command),
please use the tool at your own risk.
If you want to support the development of this program, feel free to donate.
Click to expand...
Click to collapse
XDA:DevDB Information
S-ADB, Tool/Utility for all devices (see above for details)
Contributors
mhashim6
Source Code:
GitHub
Source-Forge
This tool is based on System Command Executor Library
Version Information
Status: Stable
Current Stable Version: update6
Stable Release Date: 2018-02-03
Created 2016-07-12
Last Updated 2020-06-15
XDA:DevDB Information
S-ADB, Tool/Utility for all devices (see above for details)
Contributors
Mohamed Hashem
Source Code: https://github.com/mhashim6/Simple-ADB
Version Information
Status: Stable
Current Stable Version: update6
Stable Release Date: 2018-02-03
Created 2016-07-12
Last Updated 2020-06-14
CHANGELOG
update6 [stable] [16/09/2017]
Code:
• fixed the memory leak that occurred when a command with a large output is being executed, finally!
• support for using quotes in commands.
• fixed a bug in adb push command.
• updated with latest version of System Command Executor library.
.
update5 [stable] [16/09/2017]
Code:
• fixed the memory leak that occurred when a command with a large output is being executed, finally!
• fixed a freeze in some special cases.
• fixed the weird layout issue on linux.
• replaced the "output contains errors" prompt with a more informative text, including the exit code.
• update to the last version of System-Command-Executer library.
• updated donate url.
• overall performance improvements
• reduced jar size to 44 kbs
.
update4 [stable] [07/05/2017]
Code:
•I quote google: "several bug fixes, and speedy improvements".
•fixed a bug in adb pull command.
•errors are highlighted in red.
•added:
adb shell ip,
adb shell ps,
adb shell netstat,
adb shell pm list packages,
adb usb
version 5.6 [stable] [31/07/2016]
Code:
•Stability, stability, stability, all possible weak spots are fixed, with lots of enhancements , this program is now stable (Hopefully)
•Saving output now is through File dialog
•Shortcuts added for options menu items
•lots of fixes to "your own command" mode + (you can execute by hitting enter)
Version 5.5 [27/07/2016]
Code:
now it's open-source; check the op.
in supported commands:
•added:
adb connect [to connect the phone wirelessly]
adb disconnect
adb root
adb unroot
adb reboot sideload
fastboot reboot-bootloader
•renamed:
adb > adb help
fastboot > fastboot help
in UI :
•enhanced all UI colors.
Version 5.2 [21/07/2106] :
Code:
in compatiblity with Linux and Mac :
•Confirmed for Linux
need a confirmation from you for OsX.
in UI :
•new icon
•the whole UI (including file explorer and information panels) now is totally revamped to Windows Look and feel, now You can say it's beautiful.
•now every mode (adb, fastboot, your own command) has it's output color.
in Errors and Exception:
•now all exceptions are more detailed, to guide you and me to the problem.
in supported commands
•renamed all commands in the list to what they really are to avoid confusion and complexity.
•added :
adb
adb kill-server
fastboot
•changed :
adb devices to adb devices -l
fastboot devices to fastboot devices -l
•removed :
unlock password 2nd method to avoid confusion and complexity.
in output :
•you can save the output using "save output" in "options" menu.
•fixed some output issues.
in code :
•I've changed some algorithms > hmmm, the app size now is 30 kbs lol.
900 downloads
Version 5.0 [initial release] [12/07/2016] :
Code:
the tool now is much more stable and smart, renamed to SADB [Simple ADB]
in how the tool is working:
as I said I've rewrittten the whole code:
•now we have an output area, no files or any leftover data files at all, it's just the tool
•now the tool is executing the commands in really different and cleaner/faster way
•added the Abort button, to abort currently running operations
•added "Your own command" mode [experimental]
•the tool size is 27 kbs
in Errors and Exception:
•all exceptions and errors are caught and handled i believe
•the tool now can determine whatever the output is an error or not
in UI :
•now you can choose from adb, fastboot by radio buttons, instead of this large comboBox
•removed most of the annoying dialog panes
•the overall UI is certainly better and smoother
2800 downloads
Code:
In the future, I might make other changes and fixes,
but they may not be that big to include in separate updates,
so, if you're interested in the latest releases,
feel free to compile the code yourself.
In Debian, there are "android tools" packages and adb and fastboot are simply there. Otherwise, the executable may come with any of Android API packages.
So this runs on Linux. Install adb does nothing. Own command has no command input to use. Need a on-phone file-browser for file to pull. Need option to save logcat to a file. Small things.
I run adb CLI without much ado.
Dovidhalevi said:
In Debian, there are "android tools" packages and adb is simply there. Otherwise, the executable may come with any of Android API packages.
Click to expand...
Click to collapse
Thanks for the help, I'll check.
Edit: own command, intended to allow users to write their command in the same red area, But I'll check, and yes save logcat into file is coming.
Mohamed Hashem said:
ANNOUNCEMENT:
one year & half ago I've created this tool, the main idea was not new, it has been implemented so many times, but I believe that majority of implementations has just covered the most basic and direct commands of ADB/Fastboot,
So, this revive shall FIX WHATEVER PROBLEM YOU FACED WITH THE OLD TOOL. make sure to check the changelog [2nd post].
INSTALLATION :
(make sure you have java installed on your PC)
• first you have to install ADB Installer tool, it will install ADB to your System directly, so no need for any additional files (make sure to give @Snoop05 a Thanks :good .
• then run Simple ADB.jar and that's it!
GUIDE :
• select from "ADB", "Fastboot" or "Your own command" buttons :
- if "ADB" is selected the combobox will contain lots of adb commands :
Check if Device connected properly (adb devices).
Android Logcat.
Install a specific APK file(Android Application).
Uninstall apk <package> .
pull a file from your Android Device to your PC.
push a file from your PC to your Android Device.
View tasks running in your Android device.
Check your Android Device Memory usage.
Check your Android Device storage usage.
Kill all background processes.
Normal Reboot.
Reboot to recovery mode
Reboot to download mode (for Samsung Devices).
Reboot to bootloader mode.
Unlock Patterns/passwords [first method]
Unlock Patterns/passwords [formatting phone method]
- if "Fastboot" is selected the combobox will contain lots of Fastboot commands :
Reboot to Fastboot mode.
Flash Update.zip.
Flash recovery.img.
Flash boot.img.
Wipe (System,data & cache) before restoring nandroid backup.
Flash system.img.
Flash data.img.
Flash cache.img.
- if "Your own command" is selected the combobox will be disabled , and you can write your (still one line) command in the red area.
• Hit Activate to (well, activate the command :cyclops: ).
• Hit Abort to stop the currently running operation ( please think twice before aborting a command).
• You have the Options menu that contains :
-Donate : to support my development and studying (first year college :cyclops: )
- Main thread : to visit this thread.
- ADB Installer : to visit ADB Installer thread.
- Reset : to set the frame as you first opened it.
COMPATIBILITY:
windows (till now)
•the first issue preventing it from being compatible with other OS's is that the way java is executing commands, it's tricky to keep the same simple functionality with the mass compatibility, so i'm still working on that.
•also in other OS's you need to install adb system-wide, and i didn't find any adb-installer-like tool for Linux or Mac os.
I hope i'll get help from the community
Code:
*** Disclaimer
there are some commands I've never tested (like password commands),
because I don't have a spare phone to test on, please use the tool at your own risk.
! note: if you want to support the development of this program, it would be appreciated to click
under my avatar, and Click
:good:
XDA:DevDB Information
SADB, Tool/Utility for all devices (see above for details)
Contributors
Mohamed Hashem
Version Information
Status: Beta
Current Beta Version: 5.0
Beta Release Date: 2016-07-13
Created 2016-07-12
Last Updated 2016-07-12
Click to expand...
Click to collapse
This seems like a really nice tool to users new to ADB, nice work man!
FYI, there is an Ubuntu package called android-tools-adb that includes ADB & Fastboot.
It also appears to be in Debian repositories, so it likely works with all Debian derivatives.
I'd be happy to help test your linux based tool if/when you get to that point.
I'm no programmer, but i've been running all linux at home for a couple years, so I might have some good ideas :highfive:
topnomi said:
FYI, there is an Ubuntu package called android-tools-adb that includes ADB & Fastboot.
It also appears to be in Debian repositories, so it likely works with all Debian derivatives.
I'd be happy to help test your linux based tool if/when you get to that point.
I'm no programmer, but i've been running all linux at home for a couple years, so I might have some good ideas :highfive:
Click to expand...
Click to collapse
thanks, that would be great help for sure.
Just ran it in Ubuntu 14.04 with:
Code:
java -jar Simple_ADB.jar
Please change "adb devices" to "adb devices -l" (lowercase L). Longer output with board name.
ranf said:
Just ran it in Ubuntu 14.04 with:
Code:
java -jar Simple_ADB.jar
Please change "adb devices" to "adb devices -l" (lowercase L).
Click to expand...
Click to collapse
Does everything work fine? Thanks for testing!
I only tried adb devices and logcat so far. -l is just a feature request.
More features I miss
Code:
fastboot devices -l
fastboot reboot
ranf said:
Just ran it in Ubuntu 14.04 with:
Code:
java -jar Simple_ADB.jar
ranf said:
I only tried ad devices and logcat so far. -l is just a feature request.
Click to expand...
Click to collapse
@ranf fastboot reboot does exists: reboot to fastboot mode
Thanks, I'll change it, and thanks for testing, feel free to test other commands
topnomi said:
FYI, there is an Ubuntu package called android-tools-adb that includes ADB & Fastboot.
It also appears to be in Debian repositories, so it likely works with all Debian derivatives.
I'd be happy to help test your linux based tool if/when you get to that point.
I'm no programmer, but i've been running all linux at home for a couple years, so I might have some good ideas :highfive:
Click to expand...
Click to collapse
What about starting now, it would be helpful if you tested it now, it seems working, although I don't really know (why) lol
Click to expand...
Click to collapse
Mohamed Hashem said:
@ranf fastboot reboot does exists: reboot to fastboot mode
Click to expand...
Click to collapse
fastboot knows 2 reboots:
- reboot reboot device normally
- reboot-bootloader reboot device into bootloader
ranf said:
fastboot knows 2 reboots:
- reboot reboot device normally
- reboot-bootloader reboot device into bootloader
Click to expand...
Click to collapse
Oh I see, it's found under adb commands as reboot to bootloader, maybe I'll move it to fastboot to avoid confusion.
Great! I love it.
Will you add more commands?
Newyork! said:
Great! I love it.
Will you add more commands?
Click to expand...
Click to collapse
I'm open for suggestions
Also, that's why I've implemented "Your own command" option.
@Mohamed Hashem i belive i can tweak the UI to get close to the window's metro ui which is attractive, stunning and simple if you make it's source open. It's already a good program. And with some furnishings on the UI, it can be the de facto adb for a few years. What say?
iamsubhranil said:
@Mohamed Hashem i belive i can tweak the UI to get close to the window's metro ui which is attractive, stunning and simple if you make it's source open. It's already a good program. And with some furnishings on the UI, it can be the de facto adb for a few years. What say?
Click to expand...
Click to collapse
well, after seeing the initial poll answers, I think I'm taking the Open-source option seriously so whenever I publish it, You're free to do so
Also, I'm about to take a look at JavaFx to polish the ui, thus, We will have multiple good user interfaces, and this is definitely always better
Mohamed Hashem said:
well, after seeing the initial poll answers, I think I'm taking the Open-source option seriously so whenever I publish it, You're free to do so
Also, I'm about to learn javaFx to polish the ui, thus, We will have multiple good user interfaces, and this is definitely always better
Click to expand...
Click to collapse
I know about JavaFX and CSS stuff quite well from my self learning of 1 and a half years. I have some good metro like stylesheets ready to go with built in accent and base theme changing support. I look forward to the aforementioned happening.
Dovidhalevi said:
...
So this runs on Linux. Install adb does nothing. Own command has no command input to use. Need a on-phone file-browser for file to pull. Need option to save logcat to a file. Small things..
Click to expand...
Click to collapse
I indeed ran it under linux, usual java -jar ....was able to exercise adb commands as I describe.
Will always get io-exceptions when hitting abort.
Other exceptions may be due to the Process.start()
Mohamed Hashem said:
Till now I've been using java's regular Process.start() method, It's for Windows only,
Thanks for the help, I'll check.
Edit: own command, intended to allow users to write their command in the same red area, But I'll check, and yes save logcat into file is coming.
Click to expand...
Click to collapse
Great!
topnomi said:
FYI, there is an Ubuntu package called android-tools-adb that includes ADB & Fastboot.
It also appears to be in Debian repositories, so it likely works with all Debian derivatives.
I'd be happy to help test your linux based tool if/when you get to that point.
I'm no programmer, but i've been running all linux at home for a couple years, so I might have some good ideas :highfive:
Click to expand...
Click to collapse
You can run it right now as described!
Dovidhalevi said:
I indeed ran it under linux, usual java -jar ....was able to exercise adb commands as I describe.
Will always get io-exceptions when hitting abort.
Other exceptions may be due to the Process.start()
Actually I think that IOExeption comes from start()
did you face other exceptions?
Besides Abort, does executing commands actually work?
You can run it right now as described!
Click to expand...
Click to collapse
The described solves the second problem (adb installation) but the second problem still needs testing\investigation
Thanks for testing and information