Database Develop

[Tutorial] Installing ADB, Updating Market, Loading Gapps

PLEASE MAKE SURE YOU READ EACH STEP IN ITS ENTIRETY BEFORE DOING IT.
Table of Contents:
--1.0-Installing ADB
----1.1 Downloading the SDK
----1.2 Installing and Extracting the SDK
----1.3 Installing the Necessary USB Drivers
----1.4 Loading up ADB and Detecting Devices
--2.0 Installing GAPPS, The Newest Vending.APK (Market) or any APK for that matter.
----2.1 Installing the newest Vending APK (A.K.A Market Place)
----2.2 Installing the latest Google Applications (GAPPS)
--3.0 Help
Click to expand...
Click to collapse
Hey guys, I have noticed quite a few people have been having some problems with installing ADB and Google Applications on their newly loaded ROMs that don't have the GAPPS pre-installed. Well I am going to make this post to try and help some of those that are having a little bit of trouble. So please bare with me, as this is my first "Tutorial" post here at XDA. If you see any errors with this tutorial please let me know so I can make the appropriate changes ^_^
STEP ONE: Installing ADB
First thing is first, the method in which I will be showing you how to install GAPPS will be using ADB. If you don't know what Android Debug Bridge (adb) is it is simply a versatile tool lets you manage the state of your Android device. If you already know what ADB is and already have it installed feel free to skip to step 2.
-The Prerequisites for ADB-
1.1 Downloading the SDK
In order to gain access to using the ADB tool you need to first download the android SDK.
If you do NOT plan on developing any software for the AOSP you can skip to step 1.3 and download and install IOMonsters Easy ADB USB Driver installation. It contains a STRIPPED down version of the SDK which include the necessary components for using ADB. However, if you want to be on the safe side and download the whole sdk keep reading
The newest SDK can be found here:
http://developer.android.com/sdk/index.html
Click to expand...
Click to collapse
1.2 Installing and Extracting the SDK
For you windows users out there after you have downloaded the SDK for windows (preferably the .EXE) you are going to want to change the installation location to "C:\android-sdk-windows" or the paths you need to enter below will be different.
Now, once you have verified that the C:\android-sdk-windows folder exists you need to run the SDK Manager.exe - If you have any trouble with the SDK Manager downloading files try clicking Settings and choose "Force https:// sources to be fetched"
1.3 Installing the Necessary USB Drivers
NOTE: If you plan on NEVER using ADB over USB you can install the WirelessADB widget Go to market, and search for ADB Wireless. Install the app and run it.
Now that you have the SDK downloaded and extracted it is time to Patch the USB Driver files. Thank GOD for IOMonsters Easy USB (DRIVER ONLY) Pack. To use this tool you will need to download it. To do so you can choose from the following links:
http://legacyschool.us.to/nookdev/nook-usb-installer.rar
http://r00tyou.com/android/tools/nook_usb_driver.zip
Click to expand...
Click to collapse
I have noticed that for some people simply executing the "install.exe" from the USB drivers folder does not work. For me I had to run the install.exe and when that was finished I ran the "DPInst64.exe" NOTE: THE ONLY REASON I RAN THE DPInst64.exe WAS BECAUSE I AM USING A 64 BIT OPERATING SYSTEM. IF YOU ARE RUNNING A 32 BIT OPERATING SYSTEM PLEASE USE "DPInst.exe"
For those of you who do NOT want to download the ENTIRE Android SDK please refer to IOMonsters thread about installing and using the Easy ADB Drivers and SDK Tool:
http://forum.xda-developers.com/showthread.php?t=910008
Click to expand...
Click to collapse
1.4 Loading up ADB and Detecting Devices
Now that you have ADB up and running, and your computer is recognizing your nook through USB (or ADBWireless) it is time to load up the ADB tool and see if we can get your computer to find your device. To do so, please make sure your device is plugged into the computer via the proper USB cable. After that you are going to need to open the command prompt. To do so, click start and run, or for windows vista and up you click start and in the search bar type "cmd" and hit enter.
Once the windows console is opened you are going to need to type:
cd C:\android-sdk-windows\platform-tools
Click to expand...
Click to collapse
(assuming you installed the android-sdk in the root of C: - If not just replace it with the path of your sdk folder)
After you have successfully changed to the platform-tools directory proceed by issuing the following command:
adb devices
Click to expand...
Click to collapse
If you see the following output you are in good shape:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[Your device is listed here]
Click to expand...
Click to collapse
If not, please make sure you have your device plugged in, and the USB Drivers are functioning. If you are still at a loss at this step, feel free to PM me and I will assist you the best I can.
2.0 Installing GAPPS, The Newest Vending.APK (Market) or any APK for that matter.
This process of installing can be used for any APK you have on your computer and you want pushed over to your device.
2.1 Installing the newest Vending APK (A.K.A Market Place)
If all you want is the market, you can download the newest market APK from my webserver.
http://www.r00tyou.com/android/tools/Vending(new).apk
Click to expand...
Click to collapse
To push it to the device simple connect the device to your computer using ADB and type the following in the console:
adb devices
adb install \path\to\the\downloaded\apk\Vending(new).apk
Click to expand...
Click to collapse
Wait for it to successfully transfer over and install.
Viola, you have the newest market APK.
2.2 Installing the latest Google Applications (GAPPS)
For those of you who want the newest GAPPS, you can download the file from the cyanogen website and push over the whole gapps bundle.
To do this, simply download the latest GAPPS from here:
http://wiki.cyanogenmod.com/index.php?title=Latest_Version#Google_Apps
Click to expand...
Click to collapse
Again, using ADB type the following commands:
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
adb push [the path to your SDK tools folder]\system system/
adb reboot
Click to expand...
Click to collapse
The console will show the progress of what apps are being transferred over and installed. Once it is done rebooting it will prompt you for logging in to your Google account to setup your device. You can simply skip this (Tapping in each corner of the screen starting from the top left going clockwise) or you can proceed with the setup process.
Hope that helps
3.0 Help
If you have encountered an error while following this tutorial PLEASE PM me and I will list some common errors/problems here and make the necessary changes to this tutorial.
Problems/Solutions:
DISCLAIMER: I AM IN NO WAY RESPONSIBLE FOR ANYTHING THAT HAPPENS AS A RESULT OF FOLLOWING THESE INSTRUCTIONS. I ASSUME THAT EVERYONE READING THIS HAS SOME SORT OF KNOWLEDGE WITH HANDLING THIS DELICATE PROCESS.

will be looking this over later.
Thank you

Your welcome Please post some feed back and anything you run into while following the steps ^_^

Reneg4d3 said:
2.2 Installing the latest Google Applications (GAPPS)
For those of you who want the newest GAPPS, you can download the file from the cyanogen website and push over the whole gapps bundle.
To do this, simply download the latest GAPPS from here:
http://wiki.cyanogenmod.com/index.ph...on#Google_Apps
Again, using ADB type the following commands:
Code:
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
adb push [the path to your SDK tools folder]\system system/
adb reboot
The console will show the progress of what apps are being transferred over and installed. Once it is done rebooting it will prompt you for logging in to your Google account to setup your device. You can simply skip this (Tapping in each corner of the screen starting from the top left going clockwise) or you can proceed with the setup process.
Hope that helps
Click to expand...
Click to collapse
WRT the installation of latest gapps, can we use (gingerbread based) CM7 gapps with (eclair based) rooted stock?

met67 said:
WRT the installation of latest gapps, can we use (gingerbread based) CM7 gapps with (eclair based) rooted stock?
Click to expand...
Click to collapse
It might be backwards compatible, that I am not sure of. However, I tried using the eclair apps on the gingerbread ROM and it put me in a boot loop. I am not sure if that was just coincidence that I just so happened to push the gapps over or not, but when I reinstalled and pushed the gingerbread gapps over I did not get put in a boot loop, the boot loop consisted of the device booting up, it hit the screen where you tap the droid, then it would flash, and the CM7 loading screen would appear. It would continue to do this until I re-flashed the device.

Excellent post. All the steps seemed pretty straight forward. I couldn't install the vendor API, but at this point I'm thinking that something is wrong with my permission set. I'll go over the list again and see what I may have missed.

If you are stuck on anything please feel free to let me know. It is also a possibility that some of the steps are incorrect as I typed them out from memory

nookie froyo emmc
i'm not familiar with adb other than the method i rooted my evo with back in august so now i'm trying it with your guide (THANKS!!!)
after failing to install every version of vending.apk i have access to with root explorer, even putting marketupdater.apk in /system/apps.
It will open for a split second and then disappear so im giving up on the root explorer method. i attempted to adb install the version you have listed (the vending.apk single) and i get INSTALL_FAILED_ALREADY_EXISTS
so i removed the vending.apk and marketupdater.apk from /system/apps and then removed vending-1.apk from data/app (dunno how it got there but i found it and removed it). i try installing with adb again, i get INSTALL_FAILED_MISSING_SHARED_LIBRARY. did i remove an important file? i am now trying to install the gapps but am unsure exactly where i should put my gapps.zip and if i should unzip it first?
the link for the gapps you gave didnt show which version to download for nook color so i grabbed the hdpi for cm6, correct?
Edit, found my problem, i was trying to install wrong market, i grabbed the market i will link below from Here and then i adb install it and it installed
hmm, keeps FC. lemme wipe and try again

Ok, it appears I didn't compensate for a small variable when writting the tutorial. IF you want to install ONLY the new vendor.apk DO NOT push the whole GAPPS bundle over, simply download the vendor.apk from my website located here:
http://www.r00tyou.com/android/tools/Vending(new).apk
And push the Vendor(new).apk over by itself after RENAMING the old vendor.apk to something like vendor.apk.old then rename Vendor(new).apk to vendor.apk and run the installation.
If you need more help, or are still having problems feel free to send me a pm or post here.
Sent from my Droid using Tapatalk

mmmm, same FC to me, i can't restore the old market, via adb or via root explorer... eclair default rom here...

Can't the new market apk just be side loaded?

C:\Users\Kris>adb install C:\users\kris\downloads\vending(new).apk
2036 KB/s (2123059 bytes in 1.018s)
pkg: /data/local/tmp/vending(new).apk
Failure [INSTALL_FAILED_MISSING_SHARED_LIBRARY]
What's this about?

thereddog said:
C:\Users\Kris>adb install C:\users\kris\downloads\vending(new).apk
2036 KB/s (2123059 bytes in 1.018s)
pkg: /data/local/tmp/vending(new).apk
Failure [INSTALL_FAILED_MISSING_SHARED_LIBRARY]
What's this about?
Click to expand...
Click to collapse
Nevermind.. I just pushed gapps and got the market that way

Mariohyeah said:
mmmm, same FC to me, i can't restore the old market, via adb or via root explorer... eclair default rom here...
Click to expand...
Click to collapse
So what is the EXACT process that you are doing? And what is causing the FC? It's weird because I just retried this and I got it working :\

Does this tutorial work for DeeperBlue's HC 3.0 on microSD cards?
Hi,
Does this tutorial work if I have DeeperBlue's HC 3.0 preview v4 on a microSD card on NC? Or does it only work on internally rooted NC's? I'm encountering at the android market the error message "There are no android phones associated with this account. Please sign in with a different account". Have tried various things but not the ADB installation thing. I did download and install the android.vending_2.2.6.apk but still getting same message when trying to install something from the android market. Do I need ADB or could it be some wrong setting the "My Market Account" or "My Account"? Thanks in advance for any help!
Randy

Does this tutorial work for DeeperBlue's HC 3.0 on microSD cards?
Somehow my post repeated. Sorry.

Thank you so much for the Iomonsters! Finally after 2 days of trying it fixed my adb.

met67 said:
WRT the installation of latest gapps, can we use (gingerbread based) CM7 gapps with (eclair based) rooted stock?
Click to expand...
Click to collapse
Would like to know too as the CM7 version is not working for me on my Nook Simple Touch, will try CM6....

i root my nook touch and can't access market and have not any file managers (installed my devices);i follow steps &
i installed usb-driver but
software can't recognize device;
and this error
please help me
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[Your device is listed here]
showed nothing

Man, I just want to say, You are awesome! Nice tutorial it worked from the first time!

Lenovo Ideapad K1 One-Click Root (Mostly)

First, please forgive me if this is posted in the wrong section. It seemed most appropriate.
Second, I take no credit for anything here except for writing the .bat file here used to do the work, as well as assembling the files as per the original post.
All credit goes to djmwj and his article found here:
http://rootzwiki.com/topic/8722-lenovo-ideapad-k1-rooting-guide-messy/
As the title states, it was very messy. The OP figured out how to make it go, but it was a bit fuzzy to follow. So, I thought I'd help folks out a bit and clean things up.
So, I took the instructions presented in the OP, and condensed them into one download with one .bat that does everything from start to finish, minus installing the respective drivers for ADB and NVFlash. However, the drivers are included in the download.
Instructions:
1. Extract K1Root.rar to the directory of your choosing.
2. Connect your tablet to your PC with the USB cable.
3. With your tablet off, press POWER+VOL_UP+VOL_DOWN until the screen turns on, but displays only black.
4. Windows should detect the device, but not install drivers.
5. Go into device manager, select the APX device, choose update drivers, and install the drivers from the aptly named NVFlash_Drivers folder.
6. Open up the NVFLASH_HOME folder and run the file K1Flash.bat
7. Make your desired choices when prompted, and enjoy.
Notes (PLEASE READ BEFORE USING):
THERE MAY BE BUGS! I used it on my own stuff before releasing, and all of the essential components work as they should, however, there may possibly be a minor hiccup somewhere in the script. This should not damage anything. If you have doubts, you're welcome to examine the .bat and check it for yourself.
Please be gentle. I am not a full-time developer. I just wrote this to help make the process simpler for people.
The OP suggests you download and read the partition table, and then name the backup files based on that. This script names the backup files based on the flash.cfg script referenced in the OP, which is what controls the flashes used anyway. So, there shouldn't be any irregularities, however, I can't speak for every device on the planet.
This does NOT use the latest OTA updates. The rooted files being flashed are the default ones from the original download. You can easily adapt this to any files generated from the latest OTA files by simply dropping them in the NVFLASH_HOME file.
To install the SU properly, you have to install ADB drivers midway through the script. There's probably a way around this, but I didn't find it to be too inconvenient.
The ADB drivers are also located in the NVFLASH_HOME folder. Just do like you did when installing drivers in step #5, but instead point to NVFLASH_HOME.
Um...um...
That should be it. Obviously, use at your own risk. Let me know if there are problems with the script, and I will fix them.
Oh, and party on, Wayne.
http://www.megaupload.com/?d=AG10XE25
EDIT:
Attached is an updated .bat file which fixes a few errors in the original script, plus adds more userability. Just extract to the NVFLASH_HOME folder and run.

digitalhigh said:
First, please forgive me if this is posted in the wrong section. It seemed most appropriate.
Click to expand...
Click to collapse
You may want to change the title to Ideapad K1, I don't know if this will work for the Thinkpad tablet.
Thanks for this, I just picked up this tablet ($250 at staples) and was worrying about having to tackle linux and "compiling" just to be able to get hulu.com working. You're a lifesaver.

gallahad2000 said:
You may want to change the title to Ideapad K1, I don't know if this will work for the Thinkpad tablet.
Thanks for this, I just picked up this tablet ($250 at staples) and was worrying about having to tackle linux and "compiling" just to be able to get hulu.com working. You're a lifesaver.
Click to expand...
Click to collapse
Wow. Yeah, I'm pretty sure the key used is just for the Ideapad. Thanks for pointing that out. My dumb a$$ must've blanked out and just used the group name when posting.
And just to be fair, the original poster does include everything needed to do stuff in windows as well - it's just very hard to discern from the post.

question
Is anyone working on a custom ROM for this tablet? I am hopeing that there will be at least a few custom roms available at some point in the near future.

jfkerekes said:
Is anyone working on a custom ROM for this tablet? I am hopeing that there will be at least a few custom roms available at some point in the near future.
Click to expand...
Click to collapse
We need to be able to root and unlock the bootloader first.

Does the root method work on the 121211 update?
Or is there a way to flash back to the older firmware?

the OTA update 12 12 11.... seems to be update.zip style with no .img files inside. just loose files like normal rom updates. doesnt seeem like you can drop the files in as suggested. or i have the wrong OTA....
oh and is this for LINUX as the OP or work in windows too??

Hi, I was wondering, is this procedure works for the Lenovo ThinkPad 1838-25U? I'm thinking to buy it to give a test ride, i sold my Transformer 101 to buy the Prime but it seems like Asus is taking vacations on the delivery shipments. Is this a good tablet? or is better to wait for another version?

READ THE POST
IDEApad not THINKpad. no it wont work.

First of all- thank you so much for creating this script! I have been putting off rooting this device due to the "messy" nature of the original post.
I was hoping you could help me troubleshoot, I have tried both the new K1 root application and the original .bat file. I know the drivers are working because the script makes it as far as creating and formatting partitions and successfully pushes the bootlooder.bin but then:
bootloader.bin sent successfully
file not found: recovery.img
failed executing command 2147483647 NvError 0x4
command failure: create failed
I've tried everything I can think of... any ideas?
Thanks again.

I found problem.
after root done follow step. I cannot factory reset and update any ota.
anyone can help me ?

taiz said:
I found problem.
after root done follow step. I cannot factory reset and update any ota.
anyone can help me ?
Click to expand...
Click to collapse
Yes you have to roll-back to 04 stock and then apply the OTA's

Backup of the stock lenovo .apks!
File 1:http://www.mediafire.com/?r7iskr3wrfx4u01
File 2:http://www.mediafire.com/?fymdv9e9kmj332s
File 3:http://www.mediafire.com/?w33k205ej4fpbcl
A big thanks to Khanning who was nice enough to walk me through the adb commands and bear with me when I couldn't get adb over usb to work.

This may fix your issues http://forum.xda-developers.com/showpost.php?p=21309379&postcount=50

Can someone help I used this and I installed drivers from the drivers folder fine ....I ran option 1 fine and it said completed but said something about nvflash error make sure drivers are installed ....but on my tablet it said phone update success ....when I try option three to flash image it just stays at nvflash started and goes no further and when I try to install Su it won't connect adb , probably cause adb drivers wouldnt install ....any advice ....device is booting and seems stock ....it did not wipe my files either
Sent from my HTC EVO 3D X515a using XDA App

maek_it_happen said:
Can someone help I used this and I installed drivers from the drivers folder fine ....I ran option 1 fine and it said completed but said something about nvflash error make sure drivers are installed ....but on my tablet it said phone update success ....when I try option three to flash image it just stays at nvflash started and goes no further and when I try to install Su it won't connect adb , probably cause adb drivers wouldnt install ....any advice ....device is booting and seems stock ....it did not wipe my files either
Sent from my HTC EVO 3D X515a using XDA App
Click to expand...
Click to collapse
It means you are not in APX mode. Read the PDF and follow the instructions for installing the APX drivers. This should fix your issues.http://forum.xda-developers.com/show...9&postcount=50

I just completed step 3 flashing the image went fine up to bootloader .bin sent successfully ...then it says
File not found recovery.img
Failed executing command 2147473647 Nverror 0x4
Command failure : create failed
Edit the link u posted is not working and the drivers are installed
Edit 2 I just downloaded ur v2 root tool in ur other thread ....for some reason ur flash me Command actualy went past the recovery img error I was having with this tool .... But yours is flawless
Sent from my HTC EVO 3D X515a using XDA App

maek_it_happen said:
Edit 2 I just downloaded ur v2 root tool in ur other thread ....for some reason ur flash me Command actualy went past the recovery img error I was having with this tool .... But yours is flawless
Click to expand...
Click to collapse
Glad to hear it worked for you.
TD

I recently got this device and looking for a way to root this device without having to roll back to the factory default rom and then having to update again using OTA.
Question, am I in luck, is that at all possible or do I have to really rollback and reinstall everything again?
Thanks!
Sent from my K1 using Tapatalk

Anyone have the root? Megaupload is down forever.

Installing Xposed on the Android Emulator

I've done a fair amount of research and am still having trouble getting this installed on an emulated device. I have tried the base adt-sdk images for 4.1.2, 4.3 and 4.4.2 none of which I was able to attain the same "rooted" functionality as a phyical device. Most of the threads I read were a lot like this: http://forum.xda-developers.com/showthread.php?t=1731095
Xposed always gives me the following error: "Failed to get root access. Make sure your device is root properly and you have not blocked shell commands."
When I
Code:
adb shell
into the device I have [email protected], so I have access to root. The su binary is in both /system/bin and /system/xbin. I have also tried remounting the /system partition as rw, but nothing seems to help.
I'm not sold on any particualr version of android as long as it is >=4.1.2. I know some SELinux stuff came in at 4.3.
Any help you could offer would be great,
Thanks!

It worked flawlessly for me using Genymotion. I'm guessing you're using the normal Android emulator - apps won't get root on that directly and I'm not familiar with it.
You could, however, manually replace the necessary files. I'd recommend changing the installation mode to "Recovery" then checking the flashable ZIP's updater-script and basically replicate it from the shell (the updater-script is a shell script).

GermainZ said:
It worked flawlessly for me using Genymotion. I'm guessing you're using the normal Android emulator - apps won't get root on that directly and I'm not familiar with it.
You could, however, manually replace the necessary files. I'd recommend changing the installation mode to "Recovery" then checking the flashable ZIP's updater-script and basically replicate it from the shell (the updater-script is a shell script).
Click to expand...
Click to collapse
Where does it drop the script?

Blackdragon1400 said:
Where does it drop the script?
Click to expand...
Click to collapse
The script is inside the ZIP, which I think I saved to /sdcard/Android/data/de.robv.android.xposed.installer/ - check the output on your screen after pressing install, it should be noted there.

GermainZ said:
The script is inside the ZIP, which I think I saved to /sdcard/Android/data/de.robv.android.xposed.installer/ - check the output on your screen after pressing install, it should be noted there.
Click to expand...
Click to collapse
Alright, I will give it a try tomorrow, and post an update on the results. Thanks for the help!

Note that there are still a few minor things that are done via root, even when using the manual recovery installation mode. So the app needs to get root access.

[Q] Can install ROM, old recovery.

Hi mates, please help.
I have just update my girlfriends HTC One M7.
It was a 4.2 Android version from ARHD. I didn't notice that I needed to update Recovery in order to run new ROMs and now is looping in HTC logos.
The problem is that Fastboot isn't working with Windows 8.1 (I've been hours trying different drivers).
ADB is working right, but I can not install RECOVERY.IMG throught recovery or sideload.
I was thinking in installing through sideload an old ROM that works with my Recovery but I can not find any.
¿Any other solution?
¿A factory reset will work?
Thanks,
I'm in a hurry, i'm leaving soon and i do not like to let her with a brick mobile.

SergiNS said:
Hi mates, please help.
I have just update my girlfriends HTC One M7.
It was a 4.2 Android version from ARHD. I didn't notice that I needed to update Recovery in order to run new ROMs and now is looping in HTC logos.
The problem is that Fastboot isn't working with Windows 8.1 (I've been hours trying different drivers).
ADB is working right, but I can not install RECOVERY.IMG throught recovery or sideload.
I was thinking in installing through sideload an old ROM that works with my Recovery but I can not find any.
¿Any other solution?
¿A factory reset will work?
Thanks,
I'm in a hurry, i'm leaving soon and i do not like to let her with a brick mobile.
Click to expand...
Click to collapse
Win 8.1 does not work with lower hboots. You should try a Win 7 computer or Linux on USB.
HOW TO USE LINUX FOR FASTBOOT & ADB VIA USB
This guide originally posted by @Danny201281
http://forum.xda-developers.com/showpost.php?p=54272479&postcount=219​Linux is your friend; if your drivers are not working the chances of getting them working again without the phone booting are slim. But Linux doesn't need drivers to talk to your device.
Go here: http://www.pendrivelinux.com/ and download Universal USB Installer – Easy as 1 2 3
Then go here: http://releases.ubuntu.com/12.04/ and download Ubuntu from the first link at the top that says PC (Intel x86) desktop CD
Then use these files to create a bootable Linux USB drive with at least a 2 GB persistent file for storing files. You'll also probably need to change your boot settings in the computers bios to boot from USB.
MOVING YOUR FILES TO UBUNTU
Once booted you should be at a screen with options to "Try Ubuntu” or "Install Ubuntu". We don’t need to Install anything so just choose "Try Ubuntu" and the computer will boot to the Ubuntu Desktop (If you get a popup saying "system has encountered an error" or something similar just cancel and ignore it, it should have no effect on what we need to do as it is due to missing Linux OS updates we don’t need). On the left of the screen you'll see the Dock. Open the orange folder icon near the top this is the Home folder. It’s where we need to put any files we need to work with such as a rom.zip you want to push to the device or recovery.img files for flashing.
To get your files here is a simple drag and drop process. In the top left of the Home folder you'll see the drive structure of you pc under devices. Choose your PCs hard drive and Right-Click then" Open in a new window". Locate your .zip or .img files and drag them into the home folder. Now wait for the copy process to complete and rename them for easier typing later, e.g., rom.zip, firmware.zip or recovery.img etc.
USING ADB AND FASTBOOT
First you need to install adb fastboot; this is easy just 3 commands in the terminal. Thanks to Webupd8 team.
Code:
sudo add-apt-repository ppa:nilarimogard/webupd8
Code:
sudo apt-get update
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
Make sure your connected to the internet and press Ctrl+Alt+T to open the terminal then type or copy and paste the above commands one at a time waiting for each to complete their output. It may seem to have stopped at times but be patient when the prompt returns to normal enter the next command and when there all done you’re ready to use adb and fastboot.
Once you've moved all the files you need to the home folder that’s it you’re ready to go. Close everything down on the desktop (optional) and press Ctrl+Alt+T this will open the terminal now connect your phone with the USB cable. All fastboot commands need to have the "sudo" prefix added at the start, e.g.
fastboot flash recovery recovery.img becomes sudo fastboot flash recovery recovery.img
fastboot devices becomes sudo fastboot devices
However, adb should work basically the same as on windows. If you do have problems with normal adb commands adding “sudo” can help here as well.
If you get "no permissions ?????????" when trying to use adb, type:
Code:
killall adb
Disconnect the phone for a few seconds, then reconnect and type:
Code:
sudo adb devices
adb should now work as normal without the sudo prefix.
Click to expand...
Click to collapse

majmoz said:
Win 8.1 does not work with lower hboots. You should try a Win 7 computer or Linux on USB.
​
Click to expand...
Click to collapse
¿Isn't just easier to flash an old ROM that doesn't need TWRP 2.6 or higher?
I'm not used into Linux
Thanks a lot, please give any alternative you know.

SergiNS said:
¿Isn't just easier to flash an old ROM that doesn't need TWRP 2.6 or higher?
I'm not used into Linux
Thanks a lot, please give any alternative you know.
Click to expand...
Click to collapse
Yes, if you can find an older ROM that doesn't require an updated custom recovery. However, you wanted to update your girlfriends ROM and in order to do that you will need the newer custom recovery!
The other option, if you can find a newer RUU you could flash that and possibly Win 8.1 will work with the higher hboot.
Personally, Linux is not that difficult and if you follow the instructions posted you will not have an issue.

majmoz said:
Yes, if you can find an older ROM that doesn't require an updated custom recovery. However, you wanted to update your girlfriends ROM and in order to do that you will need the newer custom recovery!
The other option, if you can find a newer RUU you could flash that and possibly Win 8.1 will work with the higher hboot.
Personally, Linux is not that difficult and if you follow the instructions posted you will not have an issue.
Click to expand...
Click to collapse
I'm installing it on a pendrive right now.
Hope is easy.
Is taking time "Creating a persistent File"
As it seems, I can get files from HDD from Ubuntu isn't it?
Thanks

SergiNS said:
I'm installing it on a pendrive right now.
Hope is easy.
Is taking time "Creating a persistent File"
As it seems, I can get files from HDD from Ubuntu isn't it?
Thanks
Click to expand...
Click to collapse
Yes you will be able to access files on your pc's harddrive from the Linux pendrive. But it's better to copy them to the Linux home folder as in my guide before flashing. This is why you need the persistent file. It's like a Virtual Hard drive on your usb stick
Otherwise it will complicate flashing with long file paths needed for the adb and fastboot commands.
Just follow my mini guide and you'll be fine
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
Yes you will be able to access files on your pc's harddrive from the Linux pendrive. But it's better to copy them to the Linux home folder as in my guide before flashing. This is why you need the persistent file. It's like a Virtual Hard drive on your usb stick
Otherwise it will complicate flashing with long file paths needed for the adb and fastboot commands.
Just follow my mini guide and you'll be fine
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
Thanks a lot mate.
Right now is all done.
I will keep Ubuntu in my pendrive, it can help me in many ways.
Thanks for the guide and for the quick answers.
Always a pleasure to be in this forum.

SergiNS said:
Thanks a lot mate.
Right now is all done.
I will keep Ubuntu in my pendrive, it can help me in many ways.
Thanks for the guide and for the quick answers.
Always a pleasure to be in this forum.
Click to expand...
Click to collapse
Your welcome. Glad it got you out of trouble, Linux ain't so scary eh! [emoji12]
P.s no need to say thanks, there's a button for that sure majmoz would appreciate one or two :good:
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

[TOOL] crosshAtchDB: Pixel 3 XL Flash Tool

I'm trying to create an application to make flashing files on our pixel devices easier.
Features:
Install ADB
Unlock bootloader
Reboot to bootloader
Download and install factory images
Download and install TWRP
Download Magisk
Easy to use GUI
Enjoy! :good:
Credit to Dees_Troy and bigbiff for TWRP image.
Feel free to modify and hack away at the source.
WARNING: I am not responsible for anything that goes wrong using this tool, it works fine on my windows 10 machine, and tested on windows 7. However, make sure you know what these tools are doing beforehand.
New update!
Beta Release
What's New?:
All new base being built.
Better .exe support (requires installing the app)
Console interface for now.
Removed some features that were broken in the old app, will add them back one-by-one, but this time, not until they work 100%.
Usage:
Just follow the prompts on screen.
Allows picking the files for booting TWRP or pushing files via ADB.
Install:
Easy method (requires install): https://github.com/boostedd2/crosshatchdb/blob/boostedd2-patch-1/crosshAtchDB-2.3-win32.msi
Install the app with the provided .msi, choose where you want to install it. Open the folder where you installed it and run the crosshatchdbbeta.exe.
Build/Run from source:
Requires:
source .py file: https://github.com/boostedd2/crosshatchdb/blob/boostedd2-patch-1/crosshatchbeta.py
cxfreeze config: https://github.com/boostedd2/crosshatchdb/blob/boostedd2-patch-1/setup.py
To run from source, just install Python on your PC, then from cmd window run : "pip install requests".
Then just double click on the crosshatchdbbeta.py file.
To build the .exe:
You need both files from above.
Install Python
python -m pip install cx_Freeze --upgrade
With setup.py and crosshatchdbbeta.py in the same directory, run "python setup.py build"
This is a very minimal release, I will continue to fix any bugs and add features once they are working better.

Thank you so much for this! I was actually going to unlock my bootloader and root today after work. Now it will only take 2 minutes instead of 20!
I appreciate it and will report back later after testing!
**Didn't want to waste thread space so I'm editing this to reply** - Thank you so much for the response below! Very helpful! I'm up and running and really appreciate the tool and the help!

NippleSauce said:
Thank you so much for this! I was actually going to unlock my bootloader and root today after work. Now it will only take 2 minutes instead of 20!
I appreciate it and will report back later after testing!
Click to expand...
Click to collapse
No problem, quick usage guide to make sure it goes smooth.
Enable OEM unlock in developer options, also enable ADB debugging.
Plug in your phone, run crosshatchdb.
Select option 9, this will auto download and extract adb to your c: drive.
Select option 1 to check for ADB devices, check the box on the dialog that pops up on your phone.
All set. You can download magisk directly to your phone or push it from your PC.
Reboot bootloader option 2, from here you can unlock the bootloader(formats your phone btw).
Setup your phone, enable ADB debugging again and your free to reboot bootloader and download/boot TWRP to flash magisk.(use TWRP img not zip)
Hopefully these instructions are not too confusing, it is pretty easy once you do it once, and the tool really does make the next time you do it faster.
Tested on a windows 7 virtual machine and my own personal windows 10 machine.

NippleSauce said:
Thank you so much for this! I was actually going to unlock my bootloader and root today after work. Now it will only take 2 minutes instead of 20!
I appreciate it and will report back later after testing!
Click to expand...
Click to collapse
The time to unlock a Google purchased Pixel isn't the issue. The factory reset just sucks if you run stock for any time before doing it.

Two things I think you should add.
1) adb sideload for when adb works in twrp.
2) adb logcat for our great developers, so there isn't an excuse for getting them a logcat in event that they need one.
Sent from my Pixel 3 XL using Tapatalk

superchilpil said:
Two things I think you should add.
1) adb sideload for when adb works in twrp.
2) adb logcat for our great developers, so there isn't an excuse for getting them a logcat in event that they need one.
Click to expand...
Click to collapse
Good idea, should be easy to pipe logcat output to a text file.
ADB sideload can be added as well, next update will probably be when TWRP ADB is fixed, or sooner depending how long that takes.
Already thinking of ways to make the current version of this script more automated, but I like to err on the side of explicit is better than implicit.
Thanks for the ideas.

Can this install TWRP ?

Zorachus said:
Can this install TWRP ?
Click to expand...
Click to collapse
No. Everything you need to know is in the OP and everything else you need to know is in the twrp thread.
Sent from my Pixel 3 XL using Tapatalk

superchilpil said:
No. Everything you need to know is in the OP and everything else you need to know is in the twrp thread.
Click to expand...
Click to collapse
This.
It is a good option of you want an easy way to just boot TWRP in 1 button, if you don't want to install a custom recovery like TWRP.

New update coming soon, decided that command line didn't work very well for this purpose...
Also working on making all of the actions smoother.

New update released, let me know if you have any issues or feature requests, still waiting for TWRP to be fully functional before adding ADB sideload options.
CMD window still wants to hang out for now, you can minimize it though if needed.

can you add a (check for update)

Maty360414 said:
can you add a (check for update)
Click to expand...
Click to collapse
Yes, that is on the list for next update.
When TWRP is more reliable I will probably add options for copying TWRP backups to your PC as well.
Still need to get rid of the cmd window and cut down on having to open browser windows or file selection dialogs, just to get it feeling less clunky.

I'd like to send out a big thank you to boostedduece I've used platform tools and google flash all for years with no hitch whatsoever but I tried to glies an update to my kernel and ran into the red corrupt device thing and used my platform tools to flash all and halfway through it stopped and said error. I then tried this tool and it worked perfect!! Thank you so much!

quinejh said:
I'd like to send out a big thank you to boostedduece I've used platform tools and google flash all for years with no hitch whatsoever but I tried to glies an update to my kernel and ran into the red corrupt device thing and used my platform tools to flash all and halfway through it stopped and said error. I then tried this tool and it worked perfect!! Thank you so much!
Click to expand...
Click to collapse
Glad to hear it helped out, working on some new updates to make the UI even better.
Trying to make all of the download links update automatically too, just working on some web scraping again ?
It's a nice little tool if something gets messed up, also for new users to get up and running.

New update released, Download factory image has been overhauled, it will now download the image automatically, check the SHA-256 hash, then unzip it to the correct folder, just run the factory image flash option after and you're set. Be patient, the image.zip can take a while to download, takes several minutes for me, but I'm only at 50mbps down...and who knows if google throttled my connection after all the web scraper testing lol.
Pull TitaniumBackup folder via ADB to your PC, pull TWRP backup might not work it failed for me, but will not cause any damage to your PC or phone, ADB is copying the files read only from your device, and ADB just seemed to crash on me.
CMD window is still here for now until I pipe the output to the built in box on the GUI and bind keyboard keys to interact with it. For now it will help with any debugging.

boostedduece said:
New update released, Download factory image has been overhauled, it will now download the image automatically, check the SHA-256 hash, then unzip it to the correct folder, just run the factory image flash option after and you're set. Be patient, the image.zip can take a while to download, takes several minutes for me, but I'm only at 50mbps down...and who knows if google throttled my connection after all the web scraper testing lol.
Pull TitaniumBackup folder via ADB to your PC, pull TWRP backup might not work it failed for me, but will not cause any damage to your PC or phone, ADB is copying the files read only from your device, and ADB just seemed to crash on me.
CMD window is still here for now until I pipe the output to the built in box on the GUI and bind keyboard keys to interact with it. For now it will help with any debugging.
Click to expand...
Click to collapse
Can't believe I still haven't gotten the Ota Nov update
Will this work on p3?

frewys said:
Can't believe I still haven't gotten the Ota Nov update
Will this work on p3?
Click to expand...
Click to collapse
It will work for pixel 3, but you will need to download the factory image for your blueline device and extract it into c:\crosshatch_stuff\platform-tools. This program is basically a gui wrapper for ADB commands.
Just stick with the ADB tools section and find the downloads you need separately.

boostedduece said:
It will work for pixel 3, but you will need to download the factory image for your blueline device and extract it into c:\crosshatch_stuff\platform-tools. This program is basically a gui wrapper for ADB commands.
Just stick with the ADB tools section and find the downloads you need separately.
Click to expand...
Click to collapse
Right
So it doesn't automate the process the same as for xl?

frewys said:
Right
So it doesn't automate the process the same as for xl?
Click to expand...
Click to collapse
It will still install ADB and allow you to run reboot bootloader, boot TWRP, factory reset, ADB logcat, unlock bootloader.
But the only extra part that is manual would be extracting the factory image into the c:\crosshatch_stuff\platform-tools folder.