Fix Windows Driver Problems: ADB and Fastboot from Linux (Extremely newbie friendly)

Fix Windows Driver Problems: ADB and Fastboot from Linux (Extremely newbie friendly) - LeEco Le 2 Guides, News, & Discussion

On Linux adb and fastboot work perfectly right out of box - it means you dont need to restart, tweak or install any drivers. Connect your phone and adb/fastboot will recognize it correctly.
I. You need Linux, if you have it - skip this part.
1. Downloading Ubuntu Linux.
Ubuntu is the most user friendly linux with the largest software pool. Download latest release here: https://www.ubuntu.com/download/desktop (note that LTS means long-term support (5 years), so prefer it).
2. Creating space for Linux installation.
Next you need a place to install it (8 GB is minimum, but also enough for everything). It can be a usb flash drive (in this case you will need two usb flash drives) or a hard drive (right click Start, select Disk Management, select Shrink Volume (any that has free space) and make 8 GB of unallocated space).
{
"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"
}
Read more here: https://technet.microsoft.com/en-us/library/gg309169.aspx
3. Creating a bootable USB Drive.
Next you need to create a bootable USB Drive. Download rufus: https://rufus.akeo.ie/ , run it.
Device - your usb drive that is to become a bootable usb drive. Check 'Create a bootable usb disk using ISO', then click on disk image right to it and select your downloaded Ubuntu .iso file. Click 'Yes' every time Rufus promtps and wait until it finishes installing.
4. Booting from USB Drive.
Reboot your PC, during boot repeatedly press Del key to enter BIOS. In bios go to Boot section and select to boot from your USB Flash Drive.
5. Installing Ubuntu.
When Ubuntu welcome screen opens - select Install Ubuntu. Uncheck prompt about 3rd-party software to save time (or dont, up to you). Installation type - select Something Else. Again select Something Else.
5.1 Creating Partition.
Device - select free (unallocated) space that you created earlier, click + to create a partition in it (do not click 'new partition table' - it will erase all data on that disk).
5.2 Configuring Partition.
Size - at least 8 GB (8192 MB), Type - Primary, Location - Beginning, File system - Ext4, Mount Point - /.
5.3 Selecting Partition.
Click OK, then select the partition you created (Ext4 /), then click Device for bootloader installation - select the same device that holds the partition you created.
5.4 Commencing installation.
Click Install Now and agree to prompts.
Finish installation.
6. Booting into installed Ubuntu linux.
Shut down PC.
Remove bootable usb drive.
Start PC and boot from the drive where you installed bootloader.
You should be able to boot into installed Ubuntu
7. Source list configuration.
7.1 Generating source list.
Press Win button, type firefox and open it. Go to https://repogen.simplylinux.ch/ to generate sources list, select your country and ubuntu release, then select the following sources:
Go to bottom and click Generate list. Then click Direct Link to Sources List, it should look like this:
Select everything and copy it.
7.2 Editing system source list.
Press Win button and type terminal, open it and type the following:
Code:
sudo gedit /etc/apt/sources.list
and enter your user password when prompted.
Gedit will open a text document (sources.list), delete there everything, then paste the sources you generated (they should be still in your copy buffer).
Press CTRL + S to save the document and close Gedit.
Return to the rource list you generated and pay attention to lines that start with:
Code:
## Run this command:
For each line copy everything that follows, paste into terminal (right click and select Paste) and press enter. It should look like this:
Code:
wget -q -O- http://archive.getdeb.net/getdeb-archive.key | sudo apt-key add -
7.3 Updating source list.
Afterwards in terminal type:
Code:
sudo apt update
and press Enter.
7.4 Installing ADB and Fastboot and updating them.
In terminal type:
Code:
sudo apt install android-tools-adb<press enter>
sudo apt install android-tools-fastboot<press enter>
<press enter> - means you need to press enter there.
Then:
Code:
sudo apt upgrade<press enter>
and wait till it updates your system.
8. Done!
Congratulations! You have a fully working Linux and a fully working ADB + Fastboot!
This step and onwards you may brick your device, proceed at your own risk!
II. Installing a default Stock Fastboot ROM.
You need this step to make sure your phone is using its own binary images, especially if you used custom ROM's previously.
1. Download default Stock Fastboot ROM.
You can find it here: https://www.needrom.com , or on other websites.
I have Leeco S3 x626, so i will use it as example.
ROM is located here: https://www.needrom.com/download/leeco-letv-le-s3-x626-multilanguage-eu-fastboot-stock-rom/
Download it and extract.
You should get a folder like this:
2. Getting file list and flashing order.
Inside should be a .bat file with an ordered list of fastboot commands to flash binary images to your phone. I edited it and for my phone it looks like this:
Code:
sudo fastboot devices
sudo fastboot oem unlock
sudo fastboot flash preloader preloader_s2_plus.bin (-)
sudo fastboot flash lk lk.bin (+)
sudo fastboot flash lk2 lk.bin (+)
sudo fastboot flash logo logo.bin (+)
sudo fastboot flash tee1 trustzone.bin (+)
sudo fastboot flash tee2 trustzone.bin (+)
sudo fastboot flash md1img md1rom.img (+)
sudo fastboot flash md1dsp md1dsp.img (+)
sudo fastboot flash md1arm7 md1arm7.img (+)
sudo fastboot flash md3img md3rom.img (+)
sudo fastboot flash scp1 tinysys-scp.bin (+)
sudo fastboot flash scp2 tinysys-scp.bin (+)
sudo fastboot flash boot boot.img (+)
sudo fastboot flash recovery recovery.img (+)
sudo fastboot flash cache cache.img (this step only for cuoco ROM)
sudo fastboot flash -S 100M system system.img (+) (-S 100M means sending data in 100 MB parts)
sudo fastboot -w (-w means to erase userdata and cache and format)
3. Locate binary image files.
In case of this ROM binary images are located in folder images.
Go to that folder and you should see something like this:
Open terminal, navigate to the folder with binary images. They should be in the folder /home/your_user_name/Downloads/
Type
Code:
ls -l
to see folder content.
Type
Code:
cd path
to enter folder,
Code:
cd ../
to go to previous folder.
When typing a file name - press TAB to auto-complete it.
Now that you are in the folder with binary images.
4. Enable OEM Unlocking, USB Debug and enter Fastboot mode.
In your Phone go to Settings -> About Phone and tap 7 times on Build Number.
Go back enter Developer Options and enable OEM Unlocking and USB Debugging.
Shut down your phone (hold power button).
Connect your phone to PC via USB cable.
Press Volume - and Power buttons for around 15 seconds to enter Fastboot.
In terminal type
Code:
sudo fastboot devices
- your phone should be listed there.
5. Flashing Fastboot ROM.
In terminal one after another type commands from step II.2, pressing enter after each line. You can copy them and paste (right click in terminal - Paste). Do not copy part in (), including () - they are for information purpose only.
Note that this file list is for my own phone (Leeco x626), for your phone you will want to generate your own file list and order.
Do not type "fastboot reboot", or your phone may get bricked!
6. Finishing.
After everything is done - hold power button until phone shuts down (around 15 sec), then start it and boot normally.
III. Flashing custom Fastboot ROM.
1. Download custom Fastboot ROM (for example on this website) and extract it.
2. In terminal navigate to the folder where you extracted it and find the folder with binary images.
3. Enable OEM Unlocking and USB debugging on your phone as in step II.4
4. As in step II.5 flash binary images of your custom ROM, except images that are not present. In my case i marked present images as (+) and absent images as (-).
5. When everything is done - hold power button for 15 seconds to shut down, then boot normally.

One thing you might include in the post... Rufus sometimes can mess up things. So, when making Linux bootable pen-drive, using Universal USB Installer seems like less of a hassle
Sent from my Beyond using Tapatalk

Related

[Tutorial] Root for LEAKERS 7/4/10

MAJOR Update 7/13/2010 15:48 PDT
Go to http://forum.xda-developers.com/showthread.php?t=724741 for the newer, confirmed root method
The following method is now outdated
Added optional instructions to flash Amon_RA's recovery image
Removed unnecessary steps (old step 6 and 7) because downloading the SDK folder in Step 2 already contains those files
Added .wav file of Tereg's cadence in the timing step
Added commands to Amon_RA's recovery image step
Added list of reported successes
Step 4 (Re-run SDK Setup) has been eliminated
Added 20th reported success with a new condition to try to test
Added YouTube video of user Dradien doing the count in the timing step
Added note in timing step about how long to wait after you see /!\ before you start the step over
Rearranged steps 2 and 3 since installing the USB driver after downloading Tereg's SDK folder might overwrite the modded .inf file
Added TODO note to at some point include instructions at various steps for other OS's where needed.
Tereg's testing has eliminated some extra steps, removed step 6 (the driver step), removed step 8 (maintaining a clean sd card, booting the phone back up, setting charge only, turning phone off), removed steps going into recovery where card DOES NOT HAVE TO BE IN when booting into FASTBOOT, therefore the timing step going from FASTBOOT to HBOOT has been removed.
Note about RUU OTA = Leak v3
More successes added with the new "60 partition" method explained by user anoek here: (http://forum.xda-developers.com/showpost.php?p=7089301&postcount=970)
Added 2 successes where both did not run loop.bat
Please note this process is experimental at best. While we have reported a number of successes, it has not been consistent and the success rate seems to be very low or non-existent for a number of users. We are doing the best we can to replicate this process in a more reliable way, and to continue testing for easier ways to achieve this.
**TODO**
Clarify/expand steps that need instructions based on user's OS
List of reported successes
If you find other people with reported successes, there are duplicates listed, or specific information needs to be added for an individual's case, please let Tereg or myself know.
1. Dc_striker (http://forum.xda-developers.com/showpost.php?p=6927162&postcount=1)
2. Hairson (http://forum.xda-developers.com/showpost.php?p=6942651&postcount=186)
3. tereg
4. a-wilcoxj (andirc) Also rooted another phone for another XDA member using his SD card
5. lame eris (http://forum.xda-developers.com/showpost.php?p=6974393&postcount=209)
6. kzoodroid (http://forum.xda-developers.com/showpost.php?p=6975283&postcount=225 and http://forum.xda-developers.com/showpost.php?p=6975440&postcount=228) Also rooted another phone for another person using his SD card
7. RKLamb2 (http://forum.xda-developers.com/showthread.php?p=6972493#post6972493)
8. Dradien (http://forum.xda-developers.com/showpost.php?p=6980387&postcount=318 and http://forum.xda-developers.com/showpost.php?p=6980491&postcount=320)
9. graphitedv (http://forum.xda-developers.com/showpost.php?p=6981435&postcount=334 http://forum.xda-developers.com/showpost.php?p=7011890&postcount=598) - Rooted a second phone, rooted using a Mac running 10.5.8 and the 2GB PNY card
10. djblade17 (http://forum.xda-developers.com/showpost.php?p=6981578&postcount=336) - Win 7 64 bit
11. xtreme3737 (http://forum.xda-developers.com/showpost.php?p=6985257&postcount=365)
12. reethewhat (http://forum.xda-developers.com/showpost.php?p=6987179&postcount=389) - Win7 64 bit
13. largerlager (http://forum.xda-developers.com/showpost.php?p=6988950&postcount=399)
14. Austinjs0102 (http://forum.xda-developers.com/showpost.php?p=6989397&postcount=405) - Windows XP SP3, 2GB PNY card
15. HaRdC0r3 (http://forum.xda-developers.com/showpost.php?p=6963059&postcount=457)
16. varkie (androidforums) (http://androidforums.com/htc-droid-eris/109901-how-many-successfully-went-leak-root.html#post1023198) - PNY 2GB National Geographic SD card
17. Pimpshit420 (http://forum.xda-developers.com/showpost.php?p=6990916&postcount=426)
18. rcharris (http://forum.xda-developers.com/showpost.php?p=6991694&postcount=437) -- Rooted using OS X. Originally tried in WinXP, switched to Mac OS X and got it rooted.
19. bpenney1 (http://forum.xda-developers.com/showpost.php?p=6993850&postcount=448) Had PNY card
20. davinci27 (http://forum.xda-developers.com/showpost.php?p=6996272&postcount=468 and http://forum.xda-developers.com/showpost.php?p=6996996&postcount=472)
21. Jdog94, on page 71, used airplane mode.
(http://forum.xda-developers.com/showpost.php?p=7034130&postcount=733)
22. NAA_Silent (androidforums) http://androidforums.com/htc-droid-eris/109865-leak-root-has-been-found-4.html#post1065772 -- "I tried about 30 times on my work machine running XP while using my Polaroid 16 gig card. I was not successful. Last night I tried again on my Win 7 64 laptop using the factory 8 gig card that came with my Eris. After about 5 attempts I hit the jackpot. I left the loop running instead of ctl+c after each attempt."
23. lostpilot28 (http://forum.xda-developers.com/showpost.php?p=7103114&postcount=1009 and http://forum.xda-developers.com/showpost.php?p=7113530&postcount=1038) - "I flashed the 60partitions.img file to my PNY 2GB SD card and did exactly as he said."
24. igot3ballz (http://forum.xda-developers.com/showpost.php?p=7104474&postcount=1013)
25. listyb01 (http://forum.xda-developers.com/showpost.php?p=7106183&postcount=1017)
26. homewmt (http://forum.xda-developers.com/showpost.php?p=7106822&postcount=1019) - Used anoek's dd image of 60 partition sd card
27. szgtr (http://forum.xda-developers.com/showpost.php?p=7122616&postcount=1055) - Used 4GB RiDATA card
28. lil_dez (http://forum.xda-developers.com/showpost.php?p=7142521&postcount=1087) - Did not run loop.bat
29. Nickboxer7 (http://forum.xda-developers.com/showpost.php?p=7143847&postcount=1088) - Did not run loop.bat
NEW thing to test "The last time I got /!\, I left the phone in the /!\ and popped the card out tand then right back in. Still had /!\ on the screen, but suddenly the device showed up in the loop." Also disable wifi, 3g, gps, bluetooth, and enable airplane mode.
Applications
-->Development-->and check the box titled "USB Debugging"
Video Tutorial by ECLIPS3 & Tereg
http://vimeo.com/album/250913
Prerequisites
Here is a dd image of teregs sdcard in a 7zip archive
http://www.multiupload.com/OT7SH4XNBP
1.Get the Java JDK
For the Java JDK go to http://java.sun.com/javase/downloads/index.jsp
Install Java Platform, Standard Edition, JDK 6 Update 20
2. Downloading Android SDK and running SDK_Setup
Go to http://developer.android.com/sdk/index.html and download the sdk for the platform you are using. Extract the folder contained in the .zip file to the C: drive. (In Windows's case, that would be C:\android-sdk-windows\).
Run SDK_Setup.exe from inside the android-sdk-windows folder.
*Note: you may get a prompt saying that it can't download the repository.xml*
To fix that error close the warning box and click on "Settings" on the left hand side and then check the box that says "Force Https://... sources to be fetched using http://"
Go to Available Packages, the list should now be populated, expand the list by clicking the little + next to https://dl-ssl.google.com/...
*Note: it is not necessary to download the SDK Platforms
Check the box marked "USB Driver Package" at the very bottom of the list
Click Install selected on the lower right corner of the window.
Click the Accept All Radio button on the lower right window that was brought up, and then click the Install button on the lower right corner.
To make sure you are on the right track you should now see in the list of installed packages two total packages:
Android SDK Tools, revision 6
USB Driver package, revision 3
3. Overwrite the android-sdk-windows folder with all the files you need
**TODO** (Include instructions for Mac and Linux SDK downloads)
Here you can download Tereg's complete SDK with all the files used http://www.multiupload.com/01Q1UXGLOF
Unzip the folder to C:
In our setup we have extracted the Android SDK to C:\android-sdk-windows
Root Process
Tereg's analysis has shown that RUU OTA = 2.1 Leak v3. If you have Leak v3 on your phone, then you probably do not have to do this step.
4. Flash the RUU OTA Update
Go to: http://shipped-roms.com/shipped/Des...WWE_2.36.605.1_release_signed_with_driver.exe and download the RUU OTA executable.
WARNING: THIS WILL WIPE YOUR PHONE. IF YOU HAVE ROOT YOU WILL LOSE ROOT. BACKUP THE CONTENTS OF YOUR SD CARD AND APPS YOU HAVE INSTALLED BEFORE YOU CONTINUE WITH THIS STEP.
If you need to backup the content of your SD Card, mount your phones SD card as a disk drive, open the drive within My Computer, and copy/paste all folders into a new folder. Copy the contents somewhere safe, we are not responsible for any lost data.
In addition to backing up your SD card, you should find a way to back up your phone (apps, settings, etc) using any method available (like MyBackup or Astro File Manager, etc). You will have a stock, wiped phone when you are finished with this step.
Execute the .exe and go through the wizard process.
5. Make sure USB Debugging is turned on on the phone
From the Home screen, press the Menu button -> Settings. Tap Applications -> Tap Development -> Make sure that USB Debugging is CHECKED.
Open a command prompt by going to Start -> Run. Type cmd in the text box, click OK.
If using Linux, open a terminal prompt and change your working directory to the android SDK tools folder and execute the "adb devices" command.
Execute these commands
Code:
cd \
If you don't see
Code:
C:\>
then type and execute
Code:
c:
Execute the following commands
Code:
cd android-sdk-windows
cd tools
adb devices
If you see the following
Code:
List of devices attached
HTxxxxxxxxxx device
where xxxxxxxxxx is some alphanumeric value, then you have done this step successfully.
Note: Old Step 6: Updating drivers for devices has been tested as unnecessary
6. Mounting the SD Card as a Disk Drive and formatting
Mount the SD card as a disk drive from within the phone. To do this, drag the notification bar down and tap the Ongoing notification (either Charge Only or HTC Sync) section. Tap the Disk Drive option (Mount as disk drive), and tap Done.
If you don't still have Computer Management open, click the "Start" button on your computer, RIGHT click on "My Computer", click "Manage", then Click "Disk Management" which is under "Storage" on the left pane and you will see all your drives.
Find your SD Card in the lower half of the right-hand pane. If you do not see your SD card, go to the Action menu and select "Refresh". If you bought the SD Card listed here, the size of the partition is 1.83 GB. Right click on this partition, and select "Format...", and click the "Yes" button that you are sure you want to do this.
Make the volume label blank, pick FAT32 as the file system, and select the allocation unit size 4096
DO NOT do a quick format.
Click the format button on the bottom right corner, then click OK to confirm the format.
Let it format, DO NOT eject the card while formatting.
When the format is complete, power off the phone.
Note: Old Step 8: Maintaining a clean SD card has been tested as unnecessary
7. Booting into recovery (the timing step)
.wav file of Tereg doing the count in this step: http://www.multiupload.com/IRL99EH394
NEW: Dradien has uploaded a video doing the count - http://www.youtube.com/watch?v=2bRl2ul7GdA
Note: The SD card does not have to be in. It can be out before you boot into FASTBOOT. Therefore, you do not need to press down on the SD card while in FASTBOOT, press Vol Down, then remove the SD card.
Make sure that the SD card is OUT before you begin this step.
Boot into FASTBOOT mode by pressing and holding the Send+Power buttons.
Go into HBOOT by pressing the Vol Down button.
NOTE: Running the loop is just for convenience purposes. It is not mandatory for this method to work.
Start -> Run -> type cmd in the box, click ok.
In the command prompt type
Code:
cd C:\android-sdk-windows\tools
Type
Code:
loop
and press enter
Position your right hand over the sd card and the left hand over the Volume Up button. As soon as you press Volume Up, starting counting "1-1000, 2-1000, 3-1000, 4-1000", which in Tereg's case took approximately 2.5-3.5 seconds. As soon as you finish counting, press the SD card into the phone.
Watch the command prompt. If it works it should display
List of devices attached
HTxxxxxxxxxx recovery
over and over again where xxxxxxxxxx is some alphanumeric value
If this succeeded you can stop the loop by pressing Ctrl+C
Important Note: After you see the /!\, you will need to wait for several seconds before you restart this step. You will need to wait for Device Manager to stop flickering before you pull the battery. Wait at least 10-15 seconds after you see the /!\ icon before you start this step over.
If this did not succeed, make sure that Device Manager is not flickering, then pull the battery to turn off the phone. Stop the loop in the command prompt by pressing Ctrl+C, and repeat this step again starting with the phone off.
8. Pushing files in recovery, and getting #
Next on the phone press Volume UP + Power at the same time, which will bring up a menu in Recovery.
Then select "Apply sdcard:update.zip"
THIS STEP WILL FAIL, don't worry, we expect it to.
Once the update has failed we need to go back to our command prompt (the one we stopped the loop in) and type
Code:
adb push ota.zip /sdcard/update.zip
and press enter, then type
Code:
adb push root.zip /sdcard
and press enter.
After each command, ensure there is no error message after executing the command.
The status for success will be something like
Code:
xxx KB/S (x bytes in xxxx.xxxs)
At the next prompt, type this command but DO NOT execute it yet.
Code:
adb push update.zip /sdcard
This is another timing step. You will need to scroll down to "Apply sdcard:update.zip", and press the Power button then look for a very faint, dim progress bar near the bottom of the screen. The progress bar will be green.
AS SOON AS YOU LOCATE THIS PROGRESS BAR, you need to execute the command you typed.
If successful you should see the Clockwork Mod Recovery along the top of the phone.
Go to the Partitions menu on your phone by rolling the trackball down and pressing the trackball to select it.
Then select "mount /system" once.
Scroll down to +++++Go Back+++++ and select it.
Scroll and select "Install zip from sd card". Then, scroll and select "Choose zip from sdcard", then scroll and select "root.zip"
Once this is done, select Reboot System from the menu, and let it boot normally.
After the phone comes back up to Sense UI, in the command prompt execute this command
Code:
adb install Superuser.apk
Again, you should see something like:
Code:
xxx KB/s (x bytes in xxx.xxxs)
pkg: /data/local/tmp/Superuser.apk
Success
underneath the command where x is some number
Once this step is done, make sure the phone is unlocked, awake and not asleep.
Type
Code:
adb shell
then type
Code:
su
You will get a prompt on the phone from superuser asking for permission. Allow this.
the $ symbol will change to #, which indicates you have root.
[Optional] Step 11. Flashing Amon_RA's recovery image
This step is optional. Follow these steps if you would like to flash Amon_RA's recovery image after you have achieved a root prompt.
Open the command prompt and change your working directory to C:\android-sdk-windows\tools exactly as you did in Step 12.
Execute these commands (Note: When you see $ or #, that does NOT mean you type $ or # respectively in the command. It means that is the prompt you should see at the time you are executing these commands.
If you extracted the android-sdk-tools folder in Step 3, you have all the files you need for this step.
Code:
adb shell
$ su
#mount -o rw,remount /dev/block/mtdblock3 /system
# exit
$ exit
adb push recovery.img /sdcard
adb push flash_image /data/local
adb shell
$ su
# chmod 755 /data/local/flash_image
# /data/local/flash_image recovery /sdcard/recovery.img
# reboot recovery
If you do these commands, you should be able to see Amon_RA's recovery.
At the bottom of the screen it should say "Build: RA-eris-v1.6.2", and you should have the following menu options.
Code:
- Reboot system now
- USB-MS toggle
- Backup/Restore
- Flash zip from sdcard
- Wipe
- Partition sdcard
- Other
- Power off
Note: If you are getting Permission Denied errors while doing any of these steps and you still have Clockwork's Recovery partition installed, user Dradien has reported success with the "Fix Permissions" function within Clockwork's Recovery main menu. Dradien reported that that function took about 5 minutes and afterwards was able to flash Amon_RA's recovery image.
Afterward
One thing to note, there is a step we did not do that Slide Root method did which is install a full root.zip that allows you complete root access when you execute an "adb shell ..." command.
i.e. if you run adb shell as the following example command prompt
Code:
C:\>adb shell
you will see a $ prompt, not a # prompt.
Therefore, any commands you are executing (at least for the moment) that require root access (like to flash Amon RA's recovery for instance):
Code:
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
you will need to do this in the following manner
Code:
adb shell
$su
#mount -o rw,remount /dev/block/mtdblock3 /system
So, if you are getting permission denied errors from a regular command prompt while executing commands (adb shell mount..., adb flash_image..., etc) that require root access, you will most likely need to drop into shell manually, su into root, then cut off the first part of the command, put the rest of the command into the prompt and execute it.
Example:
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
becomes
mount -o rw,remount /dev/block/mtdblock3 /system
Look at other tutorials on how to flash roms, if you have any questions pm me (Captainkrtek) or join us on irc.andirc.net #droideris & #leakroot and ask for any of the opers or Tereg for help.
Below are pictures and tools Tereg used, and how he oriented the phone and positioned his hands and screwdriver over the Vol Down/Vol Up buttons with left hand and over the SD card with the right hand during the SD card timing steps.
{
"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"
}

Well written, thank you for writing this guide.

Also, the easiest way to get on irc is to go to http://chat.andirc.net/ and make a nick.

char561 said:
Also, the easiest way to get on irc is to go to http://chat.andirc.net/ and make a nick.
Click to expand...
Click to collapse
Join #leakroot to discuss it

Congrats Tereg, and CaptainKrtek. Tereg your crazy to flash RUU, thank you for trying again and proving

I should note, just remembered, I had Wi-Fi, Mobile Network and GPS all turned off during the entirety of this process.

Wow yeah great guide, people report your success with it and stuff. I'm trying it soon.
Sent from my Eris using XDA App

Great guide hopefully more people start getting root using this method, I currently have root (s-0ff) may try and root the brother in laws phone now he has leakv3. Welcome to the party leakers.

I feel completely crazy for unrooting (and that process is now done), but that's kind of where my mind is. I really want this process to be repeatable.

Hey where is the modified Inf file?

jvward said:
Hey where is the modified Inf file?
Click to expand...
Click to collapse
oops my fault, uploading now! thanks!
EDIT: In the tutorial now

ok so, i t may be a bit early, but once we are rooted from this method, can we unroot using the standard unroot method, or does nobody know that yet?

jrhoades858 said:
ok so, i t may be a bit early, but once we are rooted from this method, can we unroot using the standard unroot method, or does nobody know that yet?
Click to expand...
Click to collapse
Yes i believe you can, tereg just unrooted his phone to try this method again

Awesome! Trying in about an hour. Thank you!
Sent from my Eris using XDA App

trying right now, and yea i deleted all the adk and everyhting to start fresh =P so when i got the the part to download modded.inf i was like where the link but i remembered i didnt delete my downloads folder so i still had tht file =D haha
edit: O and fat32 with no quick format is taking forever!!!

Is there any chance this will work with the stock Eris microSD? I would prefer not to go out and buy a new one but if I absolutely have to I will today.

To unroot once you do this all you have to do is use the ruu that is posted here and that will set it back to exactly how it was.

zigzackattack said:
Is there any chance this will work with the stock Eris microSD? I would prefer not to go out and buy a new one but if I absolutely have to I will today.
Click to expand...
Click to collapse
There is a slight chance though pretty much no. Everyone who has tried it with the stock card has failed so your best bet is to go buy a $12 card

Yea I also am wondering if the stock 8 GB on Eris will work. Please let us know or test it out leakers.

MyFixofAndroid said:
Yea I also am wondering if the stock 8 GB on Eris will work. Please let us know or test it out leakers.
Click to expand...
Click to collapse
I do not believe it will. Everyone who has tried has failed.

Need help returning to stock

I purchased my nexus 7 from Walmart. The first thing I did was unlock and root it. But it turns out that my nexus has the screen flicker hardware issue. So how do I unroot, relock, and return to stock?
I think Google gives the factory .img's that I could flash through fast boot, but will that relock the boot loader and unroot it?
Also does the splash screen keep the 'unlocked' icon after being relocked?
That's a lot of questions, but if anyone can help that'd be great. Thanks!
Sent from my Nexus 7 using xda app-developers app
EDIT: since its a hardware issue, can I just factory reset? Its not like the people at Walmart will know...

you can follow this guide.
1. Download the 4.1 (JRN84D) image files to your computer. A direct download link is found here: [Only registered users can view links. ]
While a link to the Google page you can search on if you need, is here: [Only registered users can view links. ]
2. Extract the files from that downloaded file. This will give you a folder called "nakasi-jrn84d-factory-8b0bd791"... inside of which you will find a folder called "nakasi-jrn84d"... and inside of that you will see the files we are going to fastboot to your tablet. We want to place these files into the folder we located earlier which contains our "fastboot" file. Move or copy them over to that folder.
Note: On Linux/Ubuntu you may just extract them to any easily located folder.. Create a new one on the desktop or your home folder is my recommendation.
For reference, there should be 4 files, named:
bootloader-grouper-3.34.img
flash-all.sh
flash-base.sh
image-nakasi-jrn84d.zip
3. Open a command prompt inside the folder we have set up our files in. On windows this can be done by holding shift as you right-click in the folder, then select "Open command window here". On Mac or on a Linux system you want to open a terminal/command prompt and navigate to that folder using "cd" or "change directory" commands. For example if your folder is called "fastbootfiles" and it is on your desktop, you would enter:
Code:
cd desktop
Code:
cd fastbootfiles
4. Power down your tablet. Reboot into the bootloader by holding Volume Down + Power until you see the bootloader screen. In red letters toward the top of the text you will see fastboot mode. Once here, plug it into your computer.
5. Let's make sure you have your fastboot drivers installed and recognizing your device. Enter in the command prompt:
Code:
fastboot devices
For Mac:
Code:
./fastboot-mac devices
And press enter. You should see "List of attached devices" Followed by a string of numbers. If you do not see this, you do not have your drivers installed correctly! Go back to Zero Neck's Unlocking guide and grab the correct drivers, and make sure you install them correctly. You can also find the procedure during the video posted by Ragnarokx.
If you got the expected response, let's move on to fastbooting you back to stock...
6. This first command is going to wipe all your old EVERYTHING from the device. Credit to our resident AC cowboy, Jerry Hildenbrand, for pointing out to me a minor bug with the Nexus 7 bootloader that makes this a wise step to do first. Type each of these lines followed by Enter between them, waiting for one to finish before moving on to the next:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
7. This command will flash the stock bootloader on to your device. Enter:
Code:
fastboot flash bootloader bootloader-grouper-3.34.img
And press enter. Make sure you type the command exactly as you see it.
Note: As we noted earlier, replace "fastboot" above with the exact name of the fastboot file in your folder, for your system, such as "fastboot-windows" or "fastboot-mac". Addtionally for Mac's only, the command should be entered as such
Code:
./fastboot-mac flash bootloader bootloader-grouper-3.34.img
Noting the period and forward slash before the command.
Going forward you Mac folks just remember that with the rest of the commands
Now reboot the bootloader:
Code:
fastboot reboot-bootloader
Enter.
8. This next command will both wipe your old system and flash the factory image in its place, which includes the stock system, recovery, kernel, and userdata partitions:
Code:
fastboot -w update image-nakasi-jrn84d.zip
Enter, and wait, make sure the command finishes. This might take a few minutes.
Reboot the bootloader again:
Code:
fastboot reboot-bootloader
Enter.
9. We are done with the hard part... pretty easy right? Now we're just going to lock that bootloader.
Code:
fastboot oem lock
Enter.
Yes, this step is optional but I strongly recommend it if you had issues earlier which led to this procedure. Now you can unlock again if you like, which will give your tablet that final full wipe to clear out any bad data remaining:
Code:
fastboot oem unlock
Enter.
10. Finally, reboot and setup your tablet again from scratch!
Code:
fastboot reboot

5implelove said:
you can follow this guide.
1. Download the 4.1 (JRN84D) image files to your computer. A direct download link is found here: [Only registered users can view links. ]
While a link to the Google page you can search on if you need, is here: [Only registered users can view links. ]
2. Extract the files from that downloaded file. This will give you a folder called "nakasi-jrn84d-factory-8b0bd791"... inside of which you will find a folder called "nakasi-jrn84d"... and inside of that you will see the files we are going to fastboot to your tablet. We want to place these files into the folder we located earlier which contains our "fastboot" file. Move or copy them over to that folder.
Note: On Linux/Ubuntu you may just extract them to any easily located folder.. Create a new one on the desktop or your home folder is my recommendation.
For reference, there should be 4 files, named:
bootloader-grouper-3.34.img
flash-all.sh
flash-base.sh
image-nakasi-jrn84d.zip
3. Open a command prompt inside the folder we have set up our files in. On windows this can be done by holding shift as you right-click in the folder, then select "Open command window here". On Mac or on a Linux system you want to open a terminal/command prompt and navigate to that folder using "cd" or "change directory" commands. For example if your folder is called "fastbootfiles" and it is on your desktop, you would enter:
Code:
cd desktop
Code:
cd fastbootfiles
4. Power down your tablet. Reboot into the bootloader by holding Volume Down + Power until you see the bootloader screen. In red letters toward the top of the text you will see fastboot mode. Once here, plug it into your computer.
5. Let's make sure you have your fastboot drivers installed and recognizing your device. Enter in the command prompt:
Code:
fastboot devices
For Mac:
Code:
./fastboot-mac devices
And press enter. You should see "List of attached devices" Followed by a string of numbers. If you do not see this, you do not have your drivers installed correctly! Go back to Zero Neck's Unlocking guide and grab the correct drivers, and make sure you install them correctly. You can also find the procedure during the video posted by Ragnarokx.
If you got the expected response, let's move on to fastbooting you back to stock...
6. This first command is going to wipe all your old EVERYTHING from the device. Credit to our resident AC cowboy, Jerry Hildenbrand, for pointing out to me a minor bug with the Nexus 7 bootloader that makes this a wise step to do first. Type each of these lines followed by Enter between them, waiting for one to finish before moving on to the next:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
7. This command will flash the stock bootloader on to your device. Enter:
Code:
fastboot flash bootloader bootloader-grouper-3.34.img
And press enter. Make sure you type the command exactly as you see it.
Note: As we noted earlier, replace "fastboot" above with the exact name of the fastboot file in your folder, for your system, such as "fastboot-windows" or "fastboot-mac". Addtionally for Mac's only, the command should be entered as such
Code:
./fastboot-mac flash bootloader bootloader-grouper-3.34.img
Noting the period and forward slash before the command.
Going forward you Mac folks just remember that with the rest of the commands
Now reboot the bootloader:
Code:
fastboot reboot-bootloader
Enter.
8. This next command will both wipe your old system and flash the factory image in its place, which includes the stock system, recovery, kernel, and userdata partitions:
Code:
fastboot -w update image-nakasi-jrn84d.zip
Enter, and wait, make sure the command finishes. This might take a few minutes.
Reboot the bootloader again:
Code:
fastboot reboot-bootloader
Enter.
9. We are done with the hard part... pretty easy right? Now we're just going to lock that bootloader.
Code:
fastboot oem lock
Enter.
Yes, this step is optional but I strongly recommend it if you had issues earlier which led to this procedure. Now you can unlock again if you like, which will give your tablet that final full wipe to clear out any bad data remaining:
Code:
fastboot oem unlock
Enter.
10. Finally, reboot and setup your tablet again from scratch!
Code:
fastboot reboot
Click to expand...
Click to collapse
Thanks for the quick reply! I'll do this in the morning and report back. Does anyone have a link to the factory .imgs?
Sent from my Nexus 7 using xda app-developers app

https://dl.google.com/dl/android/aosp/nakasi-jro03d-factory-e102ba72.tgz

A simpler and easier solution is to use the nexus root toolkit from http://forum.xda-developers.com/showthread.php?t=1766475
Get the latest official image from google from https://developers.google.com/android/nexus/images#nakasi and use the factory restore.
Just a few things:
1. Install the toolkit to default location
2. Restart after installing
3. Click where it says "full driver installation guide" and follow the simple instructions/script to install the appropriate drivers. (necessary before you can use it; there are two possible issues with v1.5.2 mentioned but I didn't encounter any driver issues on win7 x64 nor did I encountered the issue with adb mentioned)
4. Run the flash stock + unroot script.
5. Run the relock script.

taltamir said:
A simpler and easier solution is to use the nexus root toolkit from http://forum.xda-developers.com/showthread.php?t=1766475
Get the latest official image from google from https://developers.google.com/android/nexus/images#nakasi and use the factory restore.
Just a few things:
1. Install the toolkit to default location
2. Restart after installing
3. Click where it says "full driver installation guide" and follow the simple instructions/script to install the appropriate drivers. (necessary before you can use it; I didn't have any driver issues on win7 x64 not did I encountered the issue with adb mentioned there as a possible workaround)
4. Run the flash stock + unroot script.
5. Run the relock script.
Click to expand...
Click to collapse
I agree the toolkit is the way to go. I stayed away from it when I rooted because the whole one click method never appealed to me on any of my android devices. That was until I soft bricked my n7 by trying to change the LCD density, then I went to the toolkit it is the real deal.
Sent from my EVO using xda premium

taltamir said:
A simpler and easier solution is to use the nexus root toolkit from http://forum.xda-developers.com/showthread.php?t=1766475
Get the latest official image from google from https://developers.google.com/android/nexus/images#nakasi and use the factory restore.
Just a few things:
1. Install the toolkit to default location
2. Restart after installing
3. Click where it says "full driver installation guide" and follow the simple instructions/script to install the appropriate drivers. (necessary before you can use it; there are two possible issues with v1.5.2 mentioned but I didn't encounter any driver issues on win7 x64 nor did I encountered the issue with adb mentioned)
4. Run the flash stock + unroot script.
5. Run the relock script.
Click to expand...
Click to collapse
I used the root tool kit to root. I have a windows 7 x64 also and I had no problems with it.
Sent from my Nexus 7 using xda app-developers app

[GUIDE]-Updated 17March - Unlock/Root - Return to Stock/Unbrick - Nexus7 3G - 4.2.2

[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.

[noob-read] adb and fastboot. What is it? How can it help you?

Please note, I can only speak with any degree of certainty about devices bought from Play / Moto. I cannot attest to the accuracy of this information for US carrier versions etc. Anything you do is at your own risk
Contents / Thread overview
Introduction
What is Fastboot?
What is adb?
How to install adb and fastboot
How to test adb and fastboot work
OK Gimme some useful fastboot commands please!
OK Gimme some useful adb commands please!
A little more about using Windows command prompt
Myth Busters
Introduction
adb and fastboot are very useful command line tools. They can be used from Windows, Linux or Mac to carry out tasks on your android device, such as moving and backing up files, rooting and restoring your phone to it's factory state. Understanding how to use these tools could save your phone when you get yourself in trouble. This is especially true of rooted users. Particularly those of you who are "new to the scene". You definitely should read and understand this thread before you do ANYTHING root related.
This thread is not intended to be a non-exhausted reference. It is merely here to give an overview of the most basic of basics
{
"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"
}
What is fastboot?
Fastboot comprises of 2 components.
1) Fastboot mode on the phone (The Bootloader)
2) Fastboot tool on your computer
Fastboot is a small command line tool that you can use from your computer whilst the phone is connected via USB and you are booted into the bootloader. The most common uses for fastboot are:
Unlocking the bootloader - needed as part of the rooting process
Flashing a custom recovery to the device - needed as part of the rooting process
Flashing factory images - used for saving / trestoring your device back to stock
Being able to do these 3 things are essential before rooting. Many new users skip learning these and use a toolkit to root. As a result, when they mess up and we try to explain what they need to do to fix their issues, it becomes very difficult for us to help as fastboot is not understood. It is YOUR responsibility to understand these things BEFORE you mess up.
What is adb?
adb is another small command line tool that stands for "Android Debugging Bridge". Again, it can be used from a computer connected via USB to your android device. It can be used whilst the device is booted into Android or (if you have a custom recovery), it can be used in recovery too, unlike fastboot (yes, adb and fastboot are NOT the same thing) which can only be used in the bootloader.
adb can be used to push files to (or pull files from) your phone. It can also be used to execute many of the commands available in Linux terminals (Or Android terminal emulators) on the device itself. We're not here to cover all these commands however. We just want to cover the basics.
How to install adb and fastboot
adb and fastboot are very easy to install and can be installed on Windows, Linux and MAC computers. The Windows install can be a little bit more complicated than the other 2 and may need additional drivers installing too.
Windows.
There is a very handy tool that can install adb and fastboot in 15 seconds. It is recommended that you use this to install adb and fastboot. Please see the link immediately below for that tool:
ADB, Fastboot and Drivers - 15 seconds ADB Installer - Really quick and easy way to install adb and fastboot (by @Snoop05). Download links are at the bottom of post 1.
This tool asks if you want to install adb and fastboot (to which you should answer Y) and then creates c:\adb\adb.exe and c:\adb\fastboot.exe
It then asks if you want to install it system wide .. This is asking to install for all windows users. < 15 second installer needs updating to SDK 23, which is required for latest Android versions.
Download the latest SDK (adb and fastboot) versions here: https://developer.android.com/sdk/index.html (Scroll down to SDK tools only) then download the Windows *Installer*.
Open the installer and select "Platform-tools" and install the packages. This should create "C:\Program Files (x86)\Android\android-sdk\platform-tools"
Now we want to set this path as a Windows Environment variable PATH to make the executables work system wide:
right-click computer > properties > advanced > environment variables.
under system variables click "path" and click "edit"
at the end of the line, add the below:
Code:
;C:\Program Files (x86)\Android\android-sdk\platform-tools
Please note, the semi-colon ; is VERY important.
You may also need to install drivers.
Here is a link to the Google USB Driver: DOWNLOAD THIS
Code:
To install on Windows 7:
- Ensure existing drivers are uninstalled first*
- Extract the zip to c:\adb (created earlier by the installer)
- Right-click "Computer" > Manage in windows and choose "Device Manager"
- Boot the Nexus 6 to the bootloader (Volume down + Power) and connect the USB Cable
- Watch for any new devices with exclamation marks appearing
- Right-Click the new device > Update driver software
- Choose the "browse" method and browse to c:\adb, find teh folder you extracted then follow the wizard to the end - using amd6 64 if you're on a 64 bit system and i386 if you're on a 32 bit system.
*To uninstall existing drivers, boot into Android and connect the USB cable. Monitor device manager for the device showing up. To uninstall the device, right-click it to uninstall it. At the prompt, ensure you also choose to delete the driver. Repeat this for bootloader and recovery.
Code:
To Install on Windows 8, you may need to additionally disable driver enforcement
- From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the - -- pop-out bar to appear, then click the Gear icon).
- Click ‘More PC Settings’.
- Click ‘General’.
- Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
- Wait a bit.
- Click ‘Troubleshoot’.
- Click ‘Advanced Options’
- Click ‘Windows Startup Settings’
- Click Restart.
Once that is done, your Windows computer is configured for adb and fastboot.
In device manager, the device should show up as below, depending whether you are booted into recovery or bootloader...
Recovery - Android Device > Google Nexus 4 ADB Interface
Bootloader - Android Device > Google Nexus 4 Bootloader Interface
If it shows as something different, either you have existing drivers in the way or something went wrong.
Linux and Mac
Here is a really simple tool to install adb and fastboot on the above OS. The only expectation is you know how to open and run a terminal command. Please see the link immediately below:
Nexus Tools 2.2 (Featured by XDA) - adb and fastboot installer for Linux and Mac (by @corbin052198)
Once you have installed adb and fastboot from the above link, you're ready to go.
How to test adb and fastboot work
As previously mentioned, adb and fastboot are both command line tools. That means you must run these tools from command prompt (cmd in Windows) or Terminal (Linux and Mac).
Remember earlier, I mentioned that fastboot can only be used in bootloader? and adb can only be used in Android (or custom recovery - lets cover that later)? We can use the command "fastboot devices" and "adb devices to see if we have adb and fastboot working correctly.
Lets try it.
Boot your phone into android
Connect it to your computer via USB
Open cmd (start > type "cmd" on Windows) or Terminal (Mac/ Linux
Type in the windows "adb devices" and press enter
Here is what we don't want to see:
Notice how there is nothing underneath where it says "List of attached devices" That means it cannot see any device
Here is what we DO want to see:
We can see that there is now a device listed.
OK lets test fastboot. Unplug the USB and turn off the phone. When it is off, hold down Volume down + power until you feel the vibrate. You will now be in the bootloader. Reconnect the USB cable.
In the same window (cmd or terminal) we're going to now type "fastboot devices".
Again, here is an example of what we don't and do want to see:
If in both modes, you can see your devices "Serial Number", then you know they are both working.
Please note that if you cannot get adb and fastboot to work "system wide", you can open the command prompt to the location of the adb and fastboot executables exist and try from there.
OK Gimme some useful fastboot commands please!
Here are some of the most useful fastboot commands you will come across. Fastboot is used mostly for flashing images to the devices partitions on the internal memory.
Code:
fastboot oem unlock
This unlocks your bootloader and allows you to flash a recovery to root. WARNING, this will wipe your device. Rooting the N6 is essentially unlocking the bootloader, flashing a recovery and then putting the SuperSU zip on your sdcard and flashing it via the recovery. This thread covers rooting: [HOW-TO] The Nexus 6 All-In-One Beginner's Guide by @xBeerdroiDx
Code:
fastboot flash recovery recovery.img
This will flash a recovery.img to the recovery partition. The command is broken down into "fastboot flash" (what to do) "recovery" (where to flash to) "recovery.img" what to flash there. In the terminal or command prompt, you cannot just type "recovery.img" though. It has to be the path to where the recovery image is. For example, if my recovery image is on my desktop, I would have to type:
Code:
fastboot flash recovery c:\users\rootsu\desktop\recovery.img
It is worth noting, that it IS case sensitive, meaning if your file is called Recovery.img, you must type the capital R...
Other things you would flash:
Code:
fastboot flash system system.img
fastboot flash boot boot.img
These will flash the system image (ROM) and boot image (kernel) as you would if you were returning to stock.
A full guide to returning to stock can be found here: [TUTORIAL][GUIDE][HOW TO] Flash Factory Images || Unroot || Relock bootloader by @Mr hOaX
You can also boot into a recovery.img without flashing it...
Code:
fastboot boot c:\users\rootsu\desktop\recovery.img
which is "fastboot boot" (what to do) "c:\users\rootsu\desktop\recovery.img" what to do it with. As you may have noticed, we did not define the recovery partition in this command, that's because we're not flashing it....
OK Gimme some useful adb commands please!
At the moment, we are going to assume you have a custom recovery and you have booted into recovery. The reason for this is using adb in recovery can be much simpler.
Here are some useful scenarios for using adb.
Backup your sdcard to your PC
Code:
adb shell
mount data
exit
adb pull data/media/0 c:\MyBackup
**Please note, some recoveries may "mount data" automatically on boot, so don't be disheartened if you get an error stating device or resource busy. This probably just means you can't mount what is already mounted**
/data/media/0 is the real location of /sdcard for your information. Also referred to as "The mount point". What we have done here is "adb pull" (what to do) "data/media/0" (what to move) "c:\MyBackup" (where to move it to)
Push a zip file from your PC to your sdcard (useful if you wiped your sdcard and rom)
Code:
adb shell
mount data
exit
adb push c:\rom.zip data/media/0
What we have done here is "adb push" (what to do) "c:\rom.zip" (what to move) "data/media/0" (where to move it to)
You can of course also use adb to push and pull files to and from /system too. You just need to:
Code:
adb shell
mount system
exit
I mentioned earlier that using custom recovery is much easier for adb than whilst booted into Android. You need to ensure you have a kernel that allows insecure adb before you do anything with system and data partitions. You also need to ensure that USB debugging has been enabled in developer options.
For example, to mount system to pull files whilst android is running you have to:
Code:
adb root
adb shell
mount -o rw,remount /dev/block/platform/msm_sdcc.1/by-name/system /system
...which is clearly a little bit more involved, so I recommend you use recovery for adb push and pull. You can find more detailed information on adb here: http://developer.android.com/tools/help/adb.html
A little more about using Windows command prompt
One thing to understand is that like Windows, command prompt (cmd.exe) works with directories (or folders if you like). The Linux and Mac terminals are the same, but most linux users, we expect you would already know this.
Here you will see I have downloaded a recovery image that I want to flash using fastboot.
As you can see, the recovery.img is located in C:\users\rootSU\Desktop
Usually when you open the command prompt from the start menu, or run command, the command prompt will default to your user location as seen below:
So lets try and fastboot flash recovery recovery.img...
It fails with a not-too-accurate error message. It has failed because you have not told it where the recovery image is. It assumes it is in the directory as listed in the prompt
So, how do we deal with this? Well, there are 3 ways.
1) We tell the command prompt where the recovery.img actully is in the command itself
Success! As you can see, we have told the command that the location for the file is Desktop\recovery.img
2) We can change the directory in command prompt to the directory where the file is. In this example, we change directory to "Desktop". The change directory command is "cd " or in this case "cd Desktop"
3) ...and possibly the simplest method. We hold shift whilst we right-click on the folder we want to change directory to, and directly open a command prompt there:
Another point to make with command prompt or terminals, is if you do a particular command, it is "pre-programmed" to "expect" a particular format of that command.
For example, we know that adb push as a command expects after it . This means the command is actually
Code:
adb push
BUT if you put something AFTER , for example -
Code:
adb push somethingelse
, it will assume that the "somethingelse" is a bad parameter, and the command will fail. It will probably display (or "print" which is the technical term in a terminal) a helpful guide of how the command should be used instead of trying to run the command which it does not understand.
You're probably wondering why I am telling you this. Well quite simply, it is a warning about folder names. Imagine you have c:\users\rootSU\My Documents as a folder. You assume the command is then
Code:
adb pull /data/media/0 c:\users\rootSU\My Documents
but it is not... There is a space in between My and Documents. What you have actually done is
Code:
adb pull Documents
because it uses a space to signify the end of a command or parameter. It is best to avoid using folders with spaces in them. Avoid as much as you can. In the event it is unavoidable (Although when is it ever>) then please surround the path with quotation marks,
Code:
adb pull /data/media/0 "c:\users\rootSU\My Documents"
so that way, it sees everything between the " " as a single parameter.
Myth Busters
Myth 1: You need USB debugging on to use adb and fastboot
If you cannot boot into Android, it doesn't matter. You DO NOT need USB Debugging turned on to use adb outside of android. USB Debugging is an Android ONLY setting. Fastboot obviously also does not need debugging either as this too is outside of Android
Myth 2: to adb push or fastboot flash files, they must be in the same folder as adb or fastboot executables. Sorry but this is rubbish. You can pass the full path of the image you're flashing or file you're pushing in the command and fastboot / adb can be called system wide if you've set them as an environment variable or used the 15 second installer

thanks(im out of thanks). but ill be back to leave one here!!!!!

simms22 said:
thanks(im out of thanks). but ill be back to leave one here!!!!!
Click to expand...
Click to collapse
No worries. Just putting it here for info. It's not a new work, just a slightly amended version of my N5 thread. No need for thanks

rootSU said:
No worries. Just putting it here for info. It's not a new work, just a slightly amended version of my N5 thread. No need for thanks
Click to expand...
Click to collapse
it was up in the n5 threads before, and was needed here. but its here now as well, so thank you

Good guide. Needs to be a sticky. In fact, I think every device general forum should have a sticky like this. Would have saved me a lot of grief back when....

Excellent update.

Very good to see. I'm sure lots of people will be sending noobs here for the basics.

Up to your usual helpful, good work I see.

rootSU said:
This tool asks if you want to install adb and fastboot (to which you should answer Y) and then creates c:\adb\adb.exe and c:\adb\fastboot.exe
It then asks if you want to install it system wide (to which again, you should answer Y)... This then allows you to type adb commands in the command prompt without having to open a particular directory first. You may or may not understand what I mean when I say that, but take it from me, its much more convenient and easier to use this way.
Click to expand...
Click to collapse
Y option = System-wide = install to "C:\adb" and add path for system variable - This mean you can use it by any account on your pc.
N option = Current user only = install to "C:\Users\[YOUR USERNAME]\adb" and add path for user only - Only user account used for installation can actually use it.
So if you say Y or N you will be still able to use it from any directory with cmd.
rootSU said:
It will also ask if you want to install device drivers. Actually, say N to this as we're going to cover that next, using the google USB drivers
Here is a link to the Google USB Driver: DOWNLOAD THIS
Click to expand...
Click to collapse
Drivers in my installer are the one from the link you posted here. I'm not using any modified drivers, just the one that come with SDK. And they are also digitally signed.
I hope you will fix these But still nice work, beginners should understand it :good:

Snoop05 said:
Y option = System-wide = install to "C:\adb" and add path for system variable - This mean you can use it by any account on your pc.
N option = Current user only = install to "C:\Users\[YOUR USERNAME]\adb" and add path for user only - Only user account used for installation can actually use it.
So if you say Y or N you will be still able to use it from any directory with cmd.
Drivers in my installer are the one from the link you posted here. I'm not using any modified drivers, just the one that come with SDK. And they are also digitally signed.
I hope you will fix these But still nice work, beginners should understand it :good:
Click to expand...
Click to collapse
Thanks for the info. I thought system wide meant it was putting it as a path environment variable. Reason I didmt use the drivers from your tool originally is (well I wrote this thread for N5 originally) they didnt work so had to install the universal naked driver. But if yours are the same as the ones linked, I can update that.

rootSU said:
Thanks for the info. I thought system wide meant it was putting it as a path environment variable. Reason I didmt use the drivers from your tool originally is (well I wrote this thread for N5 originally) they didnt work so had to install the universal naked driver. But if yours are the same as the ones linked, I can update that.
Click to expand...
Click to collapse
Path is added in both cases.

Sooo I need a little help here. I followed the directions to unlock the bootloader and everything went good. I did the CF auto-root, and the phone booted back up as normal. Now, I was trying to flash the M preview, and all of a suddon now my phone isn't recognized in adb. You posted a pic of what we don't want to see when testing for adb, but you don't say how to fix it if we run into the problem. Any way to get it to recognize my phone again so I can get this build on?

papeshfoo said:
Sooo I need a little help here. I followed the directions to unlock the bootloader and everything went good. I did the CF auto-root, and the phone booted back up as normal. Now, I was trying to flash the M preview, and all of a suddon now my phone isn't recognized in adb. You posted a pic of what we don't want to see when testing for adb, but you don't say how to fix it if we run into the problem. Any way to get it to recognize my phone again so I can get this build on?
Click to expand...
Click to collapse
Can you be very specific with your issue please?

papeshfoo said:
Sooo I need a little help here. I followed the directions to unlock the bootloader and everything went good. I did the CF auto-root, and the phone booted back up as normal. Now, I was trying to flash the M preview, and all of a suddon now my phone isn't recognized in adb. You posted a pic of what we don't want to see when testing for adb, but you don't say how to fix it if we run into the problem. Any way to get it to recognize my phone again so I can get this build on?
Click to expand...
Click to collapse
Android M no like root, you'll either have to live with stock or wait for chainfire to do his thing.

This all worked well until I had to find my device in the cmd prompt. It listed no devices when I typed in "ADB Devices". The issue I found was with the ADB Interface Driver. I uninstalled it and reinstalled it thinking it might've been a driver issue, but it still wouldn't work. I tried the "Uninstall driver" then "scan for hardware changes" but that didn't work. Finally I found the universal ADB driver and tried using that. STILL nothing. I figured that, because I don't have my device's driver installed, it might've been that, so I tried to DL it and yet again, nothing. I have a Kyocera Hydro Life, if that helps. Also, I tried looking through the "update driver manually" in order to update the driver software by looking through the different ADB interfaces that it had but my Kyocera driver wasn't there. Is it supposed to be there or do I just use one of the ones provided?
I checked my programs and apps and it says that the Kyocera usb driver was installed. Did I do something wrong?

ScottyChaos said:
This all worked well until I had to find my device in the cmd prompt. It listed no devices when I typed in "ADB Devices". The issue I found was with the ADB Interface Driver. I uninstalled it and reinstalled it thinking it might've been a driver issue, but it still wouldn't work. I tried the "Uninstall driver" then "scan for hardware changes" but that didn't work. Finally I found the universal ADB driver and tried using that. STILL nothing. I figured that, because I don't have my device's driver installed, it might've been that, so I tried to DL it and yet again, nothing. I have a Kyocera Hydro Life, if that helps. Also, I tried looking through the "update driver manually" in order to update the driver software by looking through the different ADB interfaces that it had but my Kyocera driver wasn't there. Is it supposed to be there or do I just use one of the ones provided?
I checked my programs and apps and it says that the Kyocera usb driver was installed. Did I do something wrong?
Click to expand...
Click to collapse
Try a different USB port. If that doesn't work try a different USB cable. If that also doesn't work, you could try disabling driver signature checking for Windows.
If those don't work, try this thread > http://forum.xda-developers.com/showthread.php?t=1583801

cam30era said:
Try a different USB port. If that doesn't work try a different USB cable. If that also doesn't work, you could try disabling driver signature checking for Windows.
If those don't work, try this thread > http://forum.xda-developers.com/showthread.php?t=1583801
Click to expand...
Click to collapse
EDIT: I also forgot to mention that the error code that came up while I was in the dev manager was compatibility error code (28) when I clicked on "Device ADB interface".

ScottyChaos said:
EDIT: I also forgot to mention that the error code that came up while I was in the dev manager was compatibility error code (28) when I clicked on "Device ADB interface".
Click to expand...
Click to collapse
Error 28 means drivers not installed. Try the driver help thread that I linked above.
---------- Post added at 12:33 PM ---------- Previous post was at 12:04 PM ----------
cam30era said:
Error 28 means drivers not installed. Try the driver help thread that I linked above.
Click to expand...
Click to collapse
@ScottyChaos,
Just a fundamental question: I assume you have enabled "Developer Options" in Settings, and then checked "enable USB debugging"?
---------- Post added at 12:39 PM ---------- Previous post was at 12:33 PM ----------
[/COLOR @ScottyChaos,
Here is a thread that you might find interesting > http://forum.xda-developers.com/android/help/metro-pcs-kyocera-hydro-life-rooted-t2870678

Windows 10 device driver management is even more locked down then windows 8. I got two of the three drivers loaded but when going into adb mode on the phone through recovery it just disappeared out of the device manager. I had to unplug and plug in while in that mode to trigger a unloaded driver in the device manager. Once there I had to force the adb driver manually with the nasty windows driver warning and all. Once I did that I could see the device in adb mode and sideload my marshmallow OTA. woot!

I decided to drop a thanks bomb...
ADB is good.
But that fastboot.
Seriously, its ONE command. OK, a few different arguments to use.... But it is so easy, and so powerful. People are afraid to mess up on command line, but its actually way harder to type the wrong thing out then to click the wrong thing.
LEARN IT. Forget your toolkit.
You can fix almost anything, Its not too hard for you. It may be new... YOU CAN DO IT.
Also, I have to say it... Its not going to help anyone, but it will keep me from punching something. ADB and Fastboot... Not the same. You don't ADB a new system image....

DroidFlasher

{
"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"
}
DroidFlasher (latest build: r109)
DroidFlasher - Universal cross platform Adb/Fastboot/Recovery (TWRP) tool for any Android devices and any platforms (Windows, Mac, Linux).
DroidFlasher can:
- DroidFlasher Scripting (DFS) - plain-text format for batch job and advanced features, like automatic download and flash zip from the net, user interaction and more.
- push file to the device
- pull file from device
- install single or multiple APK
- uninstall package (keep cache option)
- backup / restore (application / settings / cache) via adb
- backup restore partition with TWRP
- flash recovery, kernel, etc, TWRP or Fastboot
- built-in binaries (adb/fastboot/mfastboot) for Mac, PC, *nix.
- work out of the box, just unpack and run (no need setup adb/fastboot).
- more to come
DroidFlasher r109 downloads:
---
Mac: DroidFlasher_r109_Mac.7z (43.6MB) - md5sum: 7e627dc7e9f65bab3685c3b2242f0654
Win: DroidFlasher_r109_Win.7z (39.9MB) - md5sum: d34e335fcf72403d29ae3d18c22885d6
*nix: DroidFlasher_r109_Nix.7z (51.3MB) - md5sum: 8fce1c52f73b9d7810cd3cd46b504d42
---
Source code: available at github under MIT License - https://github.com/ZorgeR/DroidFlasher
screenshot r107:
video:
simplemode+dragndrop: http://www.youtube.com/watch?v=TQEpm_md0is
flash recovery from network: http://www.youtube.com/watch?v=bqkpG_N6_Ys
dfs: http://www.youtube.com/watch?v=BkVdD_AVP58
dragndrop: http://www.youtube.com/watch?v=rpUT1WT00PU
console work: http://files.z-lab.me/video/sample/DroidFlasher_Console.mov
Push and pull progresbar (non actual build): file transfer.mov
Flashing recovery: http://files.z-lab.me/video/sample/DroidFlasher_recoveryFlash.mov
overview (non actual build) :http://cloud.z-lab.me/public.php?service=files&t=33fb35197a26e375d7caf72576e1b707&download
changelog:
Code:
r100:
- initial release
r101:
- mfastboot added
r102:
- added *.DFS scripting and sideload
r103:
- added code for recovery (openrecovery, twrp)
- flash zip
- backup
- restore
- wipe (cache/data/dalvik)
- more to come...
r104:
- multiple zip flasher (without manual sorting at this time)
- flash from phone/sdcard
- layout changes
r105:
- UI update
- drag and drop for file transfer and run dfs
- tons of refactoring
- used icons: fatcow, fugue, small-n-flat
- used fonts: PT Sans, PT Sans Narrow
- dfs under hood change
- dfs file downloading command added, for example:
[CODE]dfs download "http://files.z-lab.me/mobile/Moto X/recovery/openrecovery-twrp-2.8.5.0-ghost.img"
adb reboot bootloader
fastboot flash recovery openrecovery-twrp-2.8.5.0-ghost.img
r106:
- UI fixes
r107:
- added new command -> dfs set workdir, work only in simplemode and override automaticly created working folder in this mode. If simplemode is disabled, command will be ignored.
- refactoring
- code cleaning
- UI update
r108:
- check and notify if new version available
- refactoring
- simple mode enabled by default, less dialog, all working directory will be create automatically (use: dfs set workdir, for user manually set working directory if it really need)
r109:
- added new command: dfs radiobox
- added new command: dfs show
[/code]
XDA:DevDB Information
DroidFlasher, Tool/Utility for the Moto X
Contributors
Zorge.R
Version Information
Status: Beta
Current Beta Version: r109
Beta Release Date: 2015-03-22
Created 2015-03-11
Last Updated 2015-03-26

Reserved
about *.DFS scripting:
DFS (DroidFlasherScript) is simple way for batch job with fastboot, adb, or mfastboot.
*.dfs is plaint text file with simple structure, how it's work?
- press "run *.dfs" button and select dfs file
- select working directory (where application will search files), in next window.
- wait while all jobs done.
next example show revert to stock *.dfs file for moto x (plaint text file - xt1052revery.dfs. you can choose *.txt file as well):
Code:
dfs set workdir
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
Just save this as text file, and run from application.
Next example show download and flashing moto x twrp:
Code:
# 1. Download recovery
# 2. Reboot to fastboot
# 3. Flash downloaded recovery
dfs download "http://files.z-lab.me/mobile/Moto X/recovery/openrecovery-twrp-2.8.5.0-ghost.img"
adb reboot bootloader
fastboot flash recovery openrecovery-twrp-2.8.5.0-ghost.img
On last stage of this dfs, you can use only name or full path to img.
You can added any adb commands, next show reboot to fastboot, before run job:
Code:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
or you can do any other work:
Code:
adb devices -l
adb reboot bootloader
fastboot devices
also any other (fastboot/mfastboot/adb) command work, you can use it for batch work:
Code:
adb push /local /remote
fastboot oem unlock
Also for:
- "fastboot flash /local/file"
- "fastboot boot /local/file"
- "adb sideload /local/file"
- "adb push /local /remote"
- "adb pull /remote /local"
You can use in dfs file absolute path for local file or just name in working directory (DroidFlasher check if file exist with abs path, if not, will use file with this name from working directory.
For example, next code will show correctly *.dfs file, and work without issue:
Code:
fastboot flash boot boot.img
fastboot flash system /home/zorg/files/system.img
adb push my.apk /sdcard
adb push /home/zorg/downloads/mynext.apk /sdcard
boot.img and my.apk will used from working directory, system.img and mynext.apk with abs path.
Another advanced example:
Code:
dfs show exit "Recovery flasher" "Warning!" "If you press OK, recovery partition on %DEVICE_MODEL% - %DEVICE% will be rewrited!"
dfs radiobox "TWRP 2.8.6.0|Philz Touch Recovery 6.58.7" "http://files.z-lab.me/mobile/devices/%DEVICE%/twrp-2.8.6.0-%DEVICE%.img|http://files.z-lab.me/mobile/devices/%DEVICE%/philz_touch_6.58.7-%DEVICE%.img" "Recovery flasher" "Аttention!" "Choice preferred recovery:"
dfs download %RADIOBOX_RESULT%
adb reboot bootloader
dfs sleep 1
fastboot flash recovery %RADIOBOX_RESULT_FILENAME%
dfs sleep 2
dfs radiobox "Reboot to the system|Reboot to bootloader" "reboot|reboot-bootloader" "Recovery flasher" "What next?" "Make a choice:"
fastboot %RADIOBOX_RESULT%
%dialogtype% = info, error,warning, none, confirmation
Code:
dfs radiobox "txt1|txt2|txt3|txt4" "val1|val2|val3|val4" title header content
dfs show %dialogtype% title header content
Confirmation
Code:
# Recovery flashing from fastboot with choice and confirm dialog
dfs radiobox "TWRP|CWM Recovery|Phiz Touch Recovery" "http://z-lab.me/twrp/recovery.img|http://z-lab.me/cwm/recovery.img|http://z-lab.me/phiz/recovery.img" "Recovery flashing" "Make a choice" "Select preferred recovery:"
dfs download %RADIOBOXRESULT%
dfs show confirmation "FLASHING" "WARNING" "If you press OK, DroidFlasher will flash new recovery from %RADIOBOXRESULT%"
fastboot flash recovery recovery.img
Also I wont to make DFS repository, for various *.dfs files, reverting to stock for "all" device, flash cm12, and more, all with 1 click.
Also I wont to make DFS repository, for various *.dfs files, reverting to stock for "all" device, flash cm12, and more, all with 1 click.

Push and pull file via adb with progresbar : file transfer.mov

Thank you for your effort and time, you're doing a good job.
The option to flash zip files.

Application install, single apk, multiple apk, uninstalling.

Backup and restore coding complete, and tested, worked over adb backup/restore.
Now app can backup and restore app with settings in few minutes and restore it, no reboot required.
Recommended option selected by default.

added some icons

Now application has build in binaries:
Not needed to set platform-tools directory, just press unpack binary and choose directory you want. Binary included for Mac, PC, Unix.

first post updated.

First fastboot implement, now app can flash recovery, etc :
video: http://files.z-lab.me/video/sample/DroidFlasher_recoveryFlash.mov
screen:

new features, and console for adb and fastboot:
and video how console work: http://files.z-lab.me/video/sample/DroidFlasher_Console.mov

DroidFlasher_r100 testing build available:
Mac: http://files.z-lab.me/distr/DroidFlasher/DroidFlasher_r100_Mac.7z
Win: http://files.z-lab.me/distr/DroidFlasher/DroidFlasher_r100_Win.7z
*nix: http://files.z-lab.me/distr/DroidFlasher/D...her_r100_Nix.7z (may some glitch in layout on some distro, fonts related, will be fixed in next releases)

linux version added.

Suggestions, recommendations, comments, ideas?

News on fastboot tab:

r101:
- mfastboot added
---
Mac: http://files.z-lab.me/distr/DroidFlasher/DroidFlasher_r101_Mac.7z
Win: in few days.
*nix: in few days.
---

r102:
- added *.DFS scripting and sideload
---
build will be available in few days.
---
about *.DFS scripting:
DFS (DroidFlasherScript) is simple way for batch job with fastboot, adb, or mfastboot.
*.dfs is plaint text file with simple structure, how it's work?
- press "run *.dfs" button and select dfs file
- select working directory (where application will search files), in next window.
- wait while all jobs done.
next example show revert to stock *.dfs file for moto x (plaint text file - xt1052revery.dfs. you can choose *.txt file as well):
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
you can added any adb commands, next show reboot to fastboot, before run job:
Code:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
or you can do any other work:
Code:
adb devices -l
adb reboot bootloader
fastboot devices
also any other (fastboot/mfastboot/adb) command work, you can use it for batch work:
Code:
adb push /local /remote
fastboot oem unlock
Also for:
- "fastboot flash /local/file"
- "fastboot boot /local/file"
- "adb sideload /local/file"
- "adb push /local /remote"
- "adb pull /remote /local"
You can use in dfs file absolute path for local file or just name in working directory (DroidFlasher check if file exist with abs path, if not, will use file with this name from working directory.
For example, next code will show correctly *.dfs file, and work without issue:
Code:
fastboot flash boot boot.img
fastboot flash system /home/zorg/files/system.img
adb push my.apk /sdcard
adb push /home/zorg/downloads/mynext.apk /sdcard
boot.img and my.apk will used from working directory, system.img and mynext.apk with abs path.
from version r105, new command available - DFS DOWNLOAD, for example:
Code:
dfs download "http://files.z-lab.me/mobile/Moto X/recovery/openrecovery-twrp-2.8.5.0-ghost.img"
adb reboot bootloader
fastboot flash recovery openrecovery-twrp-2.8.5.0-ghost.img
On last stage of this dfs, you can use only name or full path to img.
I think to extend dfs scripting in feature:
Code:
dfs radiobox TWRP-2.8.5.0|PhilZ-Touch-6.58.7
fastboot flash RESULTS
dfs checkbox data|cache|dalvik
adb twrp wipe RESULTS
Also I wont to make DFS repository, for various *.dfs files, reverting to stock for "all" device, flash cm12, and more, all with 1 click.

Will be awesome to see any comment about dfs, before build released.
Also to moderator, please move this thread if needed in more general forum, development, or applications, etc.

DFS in action (revert moto x to full stock, one of the many possibilities of DFS):

r103:
- added code for recovery (openrecovery, twrp)
- flash zip
- backup
- restore
- wipe (cache/data/dalvik)
- more to come...

Database Users

welcome