Database Users

Need Help Locating Some Files

I cannot find fastboot files, adb files and moto-fastboot. I recently had to reinstall windows on my computer and lost all my original files. Can someone link me to where I can download all there of these sets?

http://forum.xda-developers.com/showthread.php?t=1138092
there ya go

Thanks! Any links on the adb and fastboot files?
I am trying to flash Tenfars CWM and am having trouble, I had that moto-fastboot file in the same directory (In my case C:/root) with the img file but it says moto-fastboot is not a recognized command. There is mention of a moto-fastboot.rar with everything you would presumably need but I cannot find it.

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

(GUIDE) HOW-TO-LINUX --- Restore your BRICKED Nexus 7 using fastboot and Linux

Hello all,
I haven't really seen any options for restoring our Nexus 7's using Linux and terminal commands....
SO I made one!
This guide is the simplest I could make it and it only uses a few commands to get your Nexus 7 back up and running in the event of a brick or loss of data.
AS long as you have access to the Bootloader option of the device, this tool should work.
INSTRUCTIONS
1.Make sure that you have ADB and Fastboot installed
Open Terminal (CTRL+ALT+T)
Just type what's in the quotation marks, do not include the marks
Type "sudo apt-get update"
Type "sudo apt-get install android-tools-adb android-tools-fastboot"
2. While in Terminal, browse to location of downloaded files (boot.img , system.img)
ex. Type something like "cd ~/Downloads/NexusRestore"
3. Connect your Nexus 7 to your computer with USB cable and make sure that the device is in bootloader mode
HINT: type "fastboot devices" and it should show a set of random characters and then the word "Fastboot" to the right
4. Type these commands to restore your device to a stock rooted Jellybean ROM
fastboot devices
fastboot flash system system.img
fastboot flash recovery recovery.img (ONLY use this if you DO NOT want to kep your original recovery or if you lost it due to your situation)
fastboot flash boot boot.img
fastboot -w
fastboot reboot
5. Profit
You may now go back to recovery and flash the ROM of your choice or do whatever your heart desires
DOWNLOADS​
Dev-Host: http://d-h.st/KaZ
Extract the ZIP file and work from that directory.
Happy Restoring!! Let me know if you have any questions or need more Help :laugh:

Not to be nit picky but the instructions you gave are for Debian based distros (most likely Ubuntu/Mint- since android-tools are a backport in Debian Wheezy), IMHO it would be better to specify that this is a Ubuntu/Mint (Debian) Guide, since other distros use different package managers.
Once you have android tools installed there is an easier method.
Download factory image, extract the tar archive, run flash-all.sh
(optionally edit flash-all and remove the -w switch to preserve user data)

oldsoldier2003 said:
Not to be nit picky but the instructions you gave are for Debian based distros (most likely Ubuntu/Mint- since android-tools are a backport in Debian Wheezy), IMHO it would be better to specify that this is a Ubuntu/Mint (Debian) Guide, since other distros use different package managers.
Once you have android tools installed there is an easier method.
Download factory image, extract the tar archive, run flash-all.sh
(optionally edit flash-all and remove the -w switch to preserve user data)
Click to expand...
Click to collapse
I appreciate the info, I've only ever used Ubuntu Linux and every method that I had found so far was super in depth and not exactly simple. I've been doing this stuff for a while, so it's no big deal for me, but I wanted to provide something for people who don't do this kind of stuff every day. Just trying to contribute to the "cause" i guess. lol

Good tutorial

Help
Zesty01 said:
Hello all,
I haven't really seen any options for restoring our Nexus 7's using Linux and terminal commands....
SO I made one!
This guide is the simplest I could make it and it only uses a few commands to get your Nexus 7 back up and running in the event of a brick or loss of data.
AS long as you have access to the Bootloader option of the device, this tool should work.
INSTRUCTIONS
1.Make sure that you have ADB and Fastboot installed
Open Terminal (CTRL+ALT+T)
Just type what's in the quotation marks, do not include the marks
Type "sudo apt-get update"
Type "sudo apt-get install android-tools-adb android-tools-fastboot"
2. While in Terminal, browse to location of downloaded files (boot.img , system.img)
ex. Type something like "cd ~/Downloads/NexusRestore"
3. Connect your Nexus 7 to your computer with USB cable and make sure that the device is in bootloader mode
HINT: type "fastboot devices" and it should show a set of random characters and then the word "Fastboot" to the right
4. Type these commands to restore your device to a stock rooted Jellybean ROM
fastboot devices
fastboot flash system system.img
fastboot flash recovery recovery.img (ONLY use this if you DO NOT want to kep your original recovery or if you lost it due to your situation)
fastboot flash boot boot.img
fastboot -w
fastboot reboot
5. Profit
You may now go back to recovery and flash the ROM of your choice or do whatever your heart desires
DOWNLOADS​
Dev-Host: http://d-h.st/KaZ
Extract the ZIP file and work from that directory.
Happy Restoring!! Let me know if you have any questions or need more Help :laugh:
Click to expand...
Click to collapse
First link in "Dowload" is dead !

Thanks for this simple tuto !
In introduction of your thread, you can put this link : http://developer.android.com/tools/device.html

Remove root from 6T

Hi guys!
I need to remove magisk, root and lock the booloader for my device. How can I do it?
Thanks

Download the Magisk uninstall zip (same site where you load the Magisk zip file or see the how to root threads) and flash it with twrp (same way as you flashed the Magisk zip or see the how to root threads).
Next do the same as you did to unlock the bootloader, change the command from unlock to lock.
That should do it.
Sent from my OnePlus6T using XDA Labs

-MrMM- said:
Download the Magisk uninstall zip (same site where you load the Magisk zip file or see the how to root threads) and flash it with twrp (same way as you flashed the Magisk zip or see the how to root threads).
Next do the same as you did to unlock the bootloader, change the command from unlock to lock.
That should do it.
Sent from my OnePlus6T using XDA Labs
Click to expand...
Click to collapse
so I don't need to flash strock rom?
thanks!

lele90 said:
so I don't need to flash strock rom?
thanks!
Click to expand...
Click to collapse
EDIT: I'm not able to unistall it due to: "I cannot access /data please uninstall with Magisk Manager"

Currently I did a factory reset, software install (from 6t settings) and lock bootloader...
I was not able to unistall magisk with ZIP

lele90 said:
Hi guys!
I need to remove magisk, root and lock the booloader for my device. How can I do it?
Thanks
Click to expand...
Click to collapse
If you cannot get the unroot/un-install for Magisk to work you can do it manually. Here is how using Linux, sorry not a windows user, so you need to find a utility to unzip the GZ file if this is the case, 7zip? The /data folder contains your backup and when you boot the device up normally you can pull the file down to your PC , then use fastboot to flash the un-=compressed boot image back to A or B (or both) sides.
1. adb shell to the rooted device and type $su to enter super user, $ cd /data to look at the data folder.
2. Locate the img.gz file with the long name such as stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img.gz and copy it to your sdcard folder so you can pull it off the handset. Use $cp /data/stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img.gz /sdcard/ . exit from the shell and back to the pc
3. de-compress the stock_boot file to boot.img. using $gunzip stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img.gz
4. start the device in fastboot mode, using adb you can type $ adb reboot bootloader or hold power and vol-
5. $ fastboot flash boot_a stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img
This will restore your un-patched boot image

PulpoRojo said:
If you cannot get the unroot/un-install for Magisk to work you can do it manually. Here is how using Linux, sorry not a windows user, so you need to find a utility to unzip the GZ file if this is the case, 7zip? The /data folder contains your backup and when you boot the device up normally you can pull the file down to your PC , then use fastboot to flash the un-=compressed boot image back to A or B (or both) sides.
1. adb shell to the rooted device and type $su to enter super user, $ cd /data to look at the data folder.
2. Locate the img.gz file with the long name such as stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img.gz and copy it to your sdcard folder so you can pull it off the handset. Use $cp /data/stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img.gz /sdcard/ . exit from the shell and back to the pc
3. de-compress the stock_boot file to boot.img. using $gunzip stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img.gz
4. start the device in fastboot mode, using adb you can type $ adb reboot bootloader or hold power and vol-
5. $ fastboot flash boot_a stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img
This will restore your un-patched boot image
Click to expand...
Click to collapse
MMM sorry I'm not a linux user...
But is enough to do a factory reset, restore the firmware (via software update in settings menu) ? Or I need to flash the stock firmware in that way: https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516 ?

lele90 said:
MMM sorry I'm not a linux user...
But is enough to do a factory reset, restore the firmware (via software update in settings menu) ? Or I need to flash the stock firmware in that way: https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516 ?
Click to expand...
Click to collapse
Try to flash the entire update file from OnePlus.com:
https://www.oneplus.com/support/softwareupgrade/details?code=9
Download the file, place it in your root internal storage (the parent dir of the Downloads folder), and flash it locally from the settings>system update>local upgrade menu.

ducted said:
Try to flash the entire update file from OnePlus.com:
https://www.oneplus.com/support/softwareupgrade/details?code=9
Download the file, place it in your root internal storage (the parent dir of the Downloads folder), and flash it locally from the settings>system update>local upgrade menu.
Click to expand...
Click to collapse
Already done and then locked my bootloader! Thanks

lele90 said:
Hi guys!
I need to remove magisk, root and lock the booloader for my device. How can I do it?
Thanks
Click to expand...
Click to collapse
Why do you want to do all that? You can prevent applications from detecting root access using magisk. Just saying...

papadi said:
Why do you want to do all that? You can prevent applications from detecting root access using magisk. Just saying...
Click to expand...
Click to collapse
It does not work for my Home banking app ... I need it!

PulpoRojo said:
If you cannot get the unroot/un-install for Magisk to work you can do it manually. Here is how using Linux, sorry not a windows user, so you need to find a utility to unzip the GZ file if this is the case, 7zip? The /data folder contains your backup and when you boot the device up normally you can pull the file down to your PC , then use fastboot to flash the un-=compressed boot image back to A or B (or both) sides.
1. adb shell to the rooted device and type $su to enter super user, $ cd /data to look at the data folder.
2. Locate the img.gz file with the long name such as stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img.gz and copy it to your sdcard folder so you can pull it off the handset. Use $cp /data/stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img.gz /sdcard/ . exit from the shell and back to the pc
3. de-compress the stock_boot file to boot.img. using $gunzip stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img.gz
4. start the device in fastboot mode, using adb you can type $ adb reboot bootloader or hold power and vol-
5. $ fastboot flash boot_a stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img
This will restore your un-patched boot image
Click to expand...
Click to collapse
I tried this and now am stuck on the unlocked bootloader screen (where is says your boot loader is unlocked and software integrity cannot be guarenteed...), any ideas?

dipole said:
I tried this and now am stuck on the unlocked bootloader screen (where is says your boot loader is unlocked and software integrity cannot be guarenteed...), any ideas?
Click to expand...
Click to collapse
Did you press power off button? if yes, you stopped the boot...

PulpoRojo said:
If you cannot get the unroot/un-install for Magisk to work you can do it manually. Here is how using Linux, sorry not a windows user, so you need to find a utility to unzip the GZ file if this is the case, 7zip? The /data folder contains your backup and when you boot the device up normally you can pull the file down to your PC , then use fastboot to flash the un-=compressed boot image back to A or B (or both) sides.
1. adb shell to the rooted device and type $su to enter super user, $ cd /data to look at the data folder.
2. Locate the img.gz file with the long name such as stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img.gz and copy it to your sdcard folder so you can pull it off the handset. Use $cp /data/stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img.gz /sdcard/ . exit from the shell and back to the pc
3. de-compress the stock_boot file to boot.img. using $gunzip stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img.gz
4. start the device in fastboot mode, using adb you can type $ adb reboot bootloader or hold power and vol-
5. $ fastboot flash boot_a stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img
This will restore your un-patched boot image
Click to expand...
Click to collapse
lele90 said:
Did you press power off button? if yes, you stopped the boot...
Click to expand...
Click to collapse
I forgot the _a after boot (boot_a). i just rerooted to fix my issue so haven't tried with the correct boot_a.
Question though, shouldn't that be boot_a and boot_b? still trying to get my head around the two slots..
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img

Finally... Android 10 with working root!!!!

So i've been having a hell of a time getting the latest image working on my phone... For a bit, I was soft bricked, even after running deuces and formatting user data and what not. For a while had to go back to android 8.1 (kinda nice having PIP/split screen mode!!). Finally figured it all out today... Download: The latest Magisk, the latest TWRP both .img and installer .zip. Then latest factory image, extract with winrar, go to extracted folder and extract the big .zip again with winrar, load deuces into that folder, put phone in fastboot (hold vol - and power or adb reboot bootloader).
Open an admin command prompt (admin maybe not necessary) and here we go: fastboot --set-active=a
Run Deuces, once finished go to admin command prompt and: fastboot boot twrp-3.3.0-0-taimen.img adb push twrp-pixel2-installer-taimen-3.3.0-0.zip /sdcard adb push Magisk-v19.4.zip /sdcard
Reboot, took a while to start, open magisk, says not installed, so click install, download zip only or patch boot? I just went to the factory image folder, pushed "boot.img" to phone, and selected that.
Read a bunch of threads saying like, find/extract your own boot image (which i don't think was necessary) but if you did want to do that, the location for pixel 2 xl is: /dev/block/sde8
Hopefully that makes sense, let me know if you have comments/questions/smart remarks

noob
Zooandbio4me said:
So i've been having a hell of a time getting the latest image working on my phone... For a bit, I was soft bricked, even after running deuces and formatting user data and what not. For a while had to go back to android 8.1 (kinda nice having PIP/split screen mode!!). Finally figured it all out today... Download: The latest Magisk, the latest TWRP both .img and installer .zip. Then latest factory image, extract with winrar, go to extracted folder and extract the big .zip again with winrar, load deuces into that folder, put phone in fastboot (hold vol - and power or adb reboot bootloader).
Open an admin command prompt (admin maybe not necessary) and here we go: fastboot --set-active=a
Run Deuces, once finished go to admin command prompt and: fastboot boot twrp-3.3.0-0-taimen.img adb push twrp-pixel2-installer-taimen-3.3.0-0.zip /sdcard adb push Magisk-v19.4.zip /sdcard
Reboot, took a while to start, open magisk, says not installed, so click install, download zip only or patch boot? I just went to the factory image folder, pushed "boot.img" to phone, and selected that.
Read a bunch of threads saying like, find/extract your own boot image (which i don't think was necessary) but if you did want to do that, the location for pixel 2 xl is: /dev/block/sde8
Hopefully that makes sense, let me know if you have comments/questions/smart remarks
Click to expand...
Click to collapse
I have just bought my pixel2xl, and recieved it the DAY 10 came out.
I have not had an a/b device, my last phone was the note 4 verizon, and the tabs2 i currently have.
could you perhaps make a simple list, of what this has ?
Currently i can adb devices with linux in my phone, and fastboot reboot bootloader ?
what is "run Deuces"
i presume fastboot --set-active=a means you are setting to write to the a partition ?
the first part,is where do i download the factory image ? google ? then unzip and sideload " push boot.img ?" the file to the /sdcard folder with the other files for twrp and magisk ?
thanks a lot for the announcment. i seriously just got my usb cable attached and ran fastboot, when i searched in xda and found your post. thanks alot

Ok.
I got it kinda figured out.
Gonna make a how 2 for noobs
Step 1. Download magisk and Google image for your device to your favorite machine.
Step 2. Dow load the newest adb tools from Google to your machine. Install and make sure your adb tools are in your $PATH
On my Linux machine, I unzipped the files and copied them to my local binary folder in ~/bin
3. Extract the Google image for your device, the extract the partitions zip file.
4. Go-to the folder and Sidleload the image to your phone
Code:
adb push *.img /sdcard/
5 . GOTO where you downloaded your magisk*.apk
And install with adb
adb install *.apk
6. Open your phone, and open magisk.
Patch the boot.img file you placed in /sdcard/
7. Pull the new patched file from your phone to your computer.
adb pull /sdcard/Download/*.img
That's as far as I got this morning.
Will update you all with the finished commands then copy it over to a how-to guide for noobs.

Yayy

Everytime uninstall magisk and get it working reboots bootloop, and or I try to install a module it boot loops