Database Users

[HOW-TO]Convert Fastboot ROMs to Recovery Backups

Lets say you hate using fastboot, but the ROM you want is only available in a fastboot version. Here is how to convert a group of fastboot images into recovery backups.
First of all, you need a set of fastboot images (System.img and Boot.img)
You'll need either:
Unix (Mac OS X or Linux) with md5sum installed (It is included with Mac and Most Linux distros by default)
ADB (Android Debug Bridge)
Unix Method:
Get your two fastboot image files in a folder. Open a terminal and use the cd command to where your images are. For example, If your two images are in /home/username/images type:
Code:
cd /home/username/images/
Then type:
Code:
md5sum *img >nandroid.md5
It could take a while if your fastboot images are large. Once it is done, copy the system.img, boot.img and nandroid.md5 files to your sdcard/clockworkmod/backups/nameoffolder directory. (Replace nameoffolder with the name of your rom or something, but it must not contain spaces or special characters. A suitable choice would be to replace the space with a dot.)
You should now be able to restore your image from the Backup & Restore menu.
ADB Method (Ideal for Windows users):
The ADB method is similar, but you need to copy your image files to the sdcard first. So copy the system.img and boot.img files to: /sdcard/clockworkmod/backups/nameoffolder
(Replace nameoffolder with the name of your rom or something, but it must not contain spaces or special characters. A suitable choice would be to replace the space with a dot.)
Unmount your SDCard and boot into recovery.
When in recovery, connect the USB cable and ensure device is fully recognised by the computer (run adb devices and the serial number should appear and it should say "recovery" next to it) Next, go to mounts & storage and make sure the SDCard is mounted (If it says "unmount /sdcard" then it is mounted, if it says "mount /sdcard" then select it and it will mount.) then open an adb shell.
Type the following into the shell window:
Code:
cd /sdcard/clockworkmod/backups/nameoffolder
md5sum *img >nandroid.md5
exit
Now go into the Backup and Restore menu and your ROM should install.
Any questions? Ask below.
Hope it helps,
Jack

i found your "how-to" , it just does exactly what i wanted contrary way , i wanna make fastboot image ... how to do it ? thanks

qtwrk said:
i found your "how-to" , it just does exactly what i wanted contrary way , i wanna make fastboot image ... how to do it ? thanks
Click to expand...
Click to collapse
Just unzip it, and look for the boot.img and system.img
I think thats the way, hope it can help you.

Is there any option for Non SD card devices?

I have system, boot img file but Don't have fastboot ROM. It's a watch and i can't find any solution anywhere as it's in 9008 mode. If i can use my img file to flash it in hard brick then i think the watch would have revived. So can i convert my system img file to fastboot ROM?

Rakibboss said:
I have system, boot img file but Don't have fastboot ROM. It's a watch and i can't find any solution anywhere as it's in 9008 mode. If i can use my img file to flash it in hard brick then i think the watch would have revived. So can i convert my system img file to fastboot ROM?
Click to expand...
Click to collapse
The system.img and boot.img it's your fastboot rom, just flash them using fastboot command through fastboot mode.

LeoPosas said:
The system.img and boot.img it's your fastboot rom, just flash them using fastboot command through fastboot mode.
Click to expand...
Click to collapse
It doesn't get it fastboot mode. Basically there is no sign of power. Just shown as a Qualcomm 9008 device

How to convert fast boot rom to recovery rom ive full fast boot rom but i sell my pc recently so what can i do

**** off you ****s
Sent from my SM-A515F using Tapatalk

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.

[Q] Issues with Signing Android Factory Images, ROMs and OTA Files.

I am doing R&D on FOTA(Firmware Update Over the Air) using Nexus 7-Wifi(grouper). For which I followed the following steps.
1. Downloaded the android source from source.android.com for v 4.2.2_r1 and v 4.3_r1
2. Downloaded the binaries for grouper, extract it to my source folder.
3. Then I compiled the source code using following commands.
i. source build/envsetup.sh
ii. lunch full_grouper-userdebug
iii. make -j8 dist
4. After few tries, I had success in compiling the source for Nexus 7(grouper).
5. I got following files in $out/source_4.2.2/dist folder
-----------------------------------------------
adb*
android-common-carousel.jar
android-common.jar
android-info.txt
android-support-v13.jar
android-support-v4.jar
android-support-v7-gridlayout.jar
build.prop
com.android.nfc_extras.jar
fastboot*
full_grouper-apps-eng.root.zip
full_grouper-emulator-eng.root.zip
full_grouper-img-eng.root.zip
full_grouper-ota-eng.root.zip
full_grouper-symbols-eng.root.zip
full_grouper-target_files-eng.root.zip
gpl_source.tgz
guava.jar
installed-files.txt
jsr305.jar
mkbootfs*
mkbootimg*
mkyaffs2image*
mp4parser.jar
package-stats.txt
ramdisk.img
signapk.jar
vendor_owner_info.txt
-----------------------------------------------
6. Then I generated my own keys using /development/tools/make_key tool for media, testkey, releasekey, shared, platform.
Assume my keys are locate at /keys folder.
7. Then I created a signed target zip file using following command.
/source/build/tools/releasetools/sign_target_files_apks -v -p ../host/linux-x86 -d /keys full_grouper-target_files-eng.root.zip signed_target_files.zip
8. From signed target zip file I create
/source/build/tools/releasetools/img_from_target_files -v -p ../host/linux-x86 signed_target_files.zip signed_img_from_target_files.zip
9. Then I flashed the signed_img_from_target_files.zip using fastboot command using the following script:
----------------------------------------------------------------------
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot reboot-bootloader
sleep 10
fastboot -w update signed_img_from_target_files.zip
----------------------------------------------------------------------
10. The device gets flashed well and is working, but I am getting an log while flashing in which it is unable to find boot.sig, system.sig and recovery.sig
11. Now the otacerts.zip file contains a testkey which is not the one that I signed it with.
file located at "/system/etc/security/otacerts.zip" on device.
12. Now since the otacerts.zip is signed with the default key it gives a mismatch error which I tried to flash an OTA update which is signed by the my custom key.
Now my doubt is:
How can I add boot.sig, recovery.sig and system.sig to signed_img_from_target_files.zip?
Is there anything I am doing wrong?
Does the recovery checks the current ROM keys from "/system/etc/security/otacerts.zip"?
What is the correct procedure to sign the OTA update?

Late answer
I know that it's dead thread but may be somebody tries to solve this problem: you should use
Code:
-o or --replace_ota_keys
flag with
Code:
sign_target_files_apks

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

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