Database Develop

Help! Infinite bootloop, can't enter Recovery, and Fastboot usb doesnt work

Super noob here. I was trying to update my android revolution hd rom and somehow I screwed everything.
Do I have a chance to fix my phone or should I purchase a new one?
My unit is a HTC One m7 (sprint).
I understand that in order to fix this I need to install a new recovery (I have a CWM old version). The phone reboots in regular mode but as ROM is not working it reboots to recovery, but this doesn't work either I just see a 0,5s splash screen and the loop goes on.
I have read the "disaster recovery" thread but they assume Fastboot USB works. My problem is I dont even know how to connect my phone to my computer in order to work from there.
My bootloader is still unlocked (fortunately).
I have Hboot 1.44 should I update it?
A step-by-step dumb proof will be appreciated!

First download a toolkit for the HTC one m7. You can find it in the android development section. With that you can install a new recovery. I recommend twrp. After that push a ROM via adb to the device and flash that Rom. There are hundreds of sprint ROMs and even more threads "how to adb push"
http://forum.xda-developers.com/showthread.php?t=2265618
[GUIDE] Complete Flashing Guide | Rooting | Going Back To Stock | 05.05.2013

Philipp_94 said:
First download a toolkit for the HTC one m7. You can find it in the android development section. With that you can install a new recovery. I recommend twrp. After that push a ROM via adb to the device and flash that Rom. There are hundreds of sprint ROMs and even more threads "how to adb push"
http://forum.xda-developers.com/showthread.php?t=2265618
[GUIDE] Complete Flashing Guide | Rooting | Going Back To Stock | 05.05.2013
Click to expand...
Click to collapse
Thanks, downloaded this tool seems great, but my phone is not getting recognized by the system. Im using Windows 8.1
http://forum.xda-developers.com/showthread.php?t=2727913
{
"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"
}
My drivers are installed, I have "HTC Sync Manager" installed. This is desperating.

Blocked ONE said:
Thanks, downloaded this tool seems great, but my phone is not getting recognized by the system. Im using Windows 8.1
http://forum.xda-developers.com/showthread.php?t=2727913
My drivers are installed, I have "HTC Sync Manager" installed. This is desperating.
Click to expand...
Click to collapse
First off if your running CWM and tried to install ARHD then your gonna have issues as ARHD is only compatible with TWRP recovery 2.6.3.3 or 2.7.1.1
If Windows 8 has stopped recognizing your phone and you can't boot to a Rom unfortunately there's little chance of you getting it working again.
So you have 2 good options. Get/make an otg cable and use it to install a Rom compatible with CWM.
Or create a Linux boot disk to use adb/fastboot. Linux doesn't need drivers for your phone so no detection problems then you can flash recovery or push a Rom whatever you want.
---------- Post added at 03:50 PM ---------- Previous post was at 03:27 PM ----------
Blocked ONE said:
I have read the "disaster recovery" thread but they assume Fastboot USB works. My problem is I dont even know how to connect my phone to my computer in order to work from there.
Click to expand...
Click to collapse
To use Fastboot :- boot the phone to the boot loader and select Fastboot from the menu. Then connect you phone via usb cable and Fastboot should change to fastbootusb.
Open the folder that contains adb and fast boot on your pc then hold Shift and right click on the empty white background space, from the menu that appears select "open command window here"
In the command window type
fastboot devices
If you get an output of your phone's serial no. Fastboot is working.

Danny201281 said:
First off if your running CWM and tried to install ARHD then your gonna have issues as ARHD is only compatible with TWRP recovery 2.6.3.3 or 2.7.1.1
If Windows 8 has stopped recognizing your phone and you can't boot to a Rom unfortunately there's little chance of you getting it working again.
So you have 2 good options. Get/make an otg cable and use it to install a Rom compatible with CWM.
Or create a Linux boot disk to use adb/fastboot. Linux doesn't need drivers for your phone so no detection problems then you can flash recovery or push a Rom whatever you want
To use Fastboot :- boot the phone to the boot loader and select Fastboot from the menu. Then connect you phone via usb cable and Fastboot should change to fastbootusb.
Open the folder that contains adb and fast boot on your pc then hold Shift and right click on the empty white background space, from the menu that appears select "open command window here"
In the command window type
fastboot devices
If you get an output of your phone's serial no. Fastboot is working.
Click to expand...
Click to collapse
I write fastboot devices and nothing happens.
I think I'm trying on a friends computer he has Linux. Hope this is not bricked lol. At least the phone turns ON, it can be charged as well, and bootloader works. But can't fastboot!

Blocked ONE said:
I write fastboot devices and nothing happens.
I think I'm trying on a friends computer he has Linux. Hope this is not bricked lol. At least the phone turns ON, it can be charged as well, and bootloader works. But can't fastboot!
Click to expand...
Click to collapse
Your not even close to being bricked
On Linux you will still need to install adb/fastboot but no drivers for your phone needed. As long as adb is working your on a winner
Also you will need to add sudo at the beginning of each command
E.g "adb devices" becomes " sudo adb devices" or "fastboot flash recovery" becomes " sudo fastboot flash recovery"

Blocked ONE said:
I write fastboot devices and nothing happens.
I think I'm trying on a friends computer he has Linux. Hope this is not bricked lol. At least the phone turns ON, it can be charged as well, and bootloader works. But can't fastboot!
Click to expand...
Click to collapse
Danny201281 said:
Your not even close to being bricked
On Linux you will still need to install adb/fastboot but no drivers for your phone needed. As long as adb is working your on a winner
Also you will need to add sudo at the beginning of each command
E.g "adb devices" becomes " sudo adb devices" or "fastboot flash recovery" becomes " sudo fastboot flash recovery"
Click to expand...
Click to collapse
also Sprint has a different partition structure you CANNOT use files for a GSM phone on yours ...please go to the sprint forums for the files and help you need

Sirs, ubuntu doesnt recognize it either!
While on the bootloop it says system can't mount the Android unit. This means the USB is working.
But on the bootloader/fastboot it doesn't even pop up this message, its like nothing is plugged. WTF I think it is bricked, can't connect anywhere. I feel stupid just trashed my phone for a non important ROM update.

Blocked ONE said:
Sirs, ubuntu doesnt recognize it either!
While on the bootloop it says system can't mount the Android unit. This means the USB is working.
But on the bootloader/fastboot it doesn't even pop up this message, its like nothing is plugged. WTF I think it is bricked, can't connect anywhere. I feel stupid just trashed my phone for a non important ROM update.
Click to expand...
Click to collapse
you need to calm down
first turn the phone off
hold power plus volume down
when the phone goes off keep holding volume down and let go of power
now your in the bootloader
use the volume key to select bootloader then power off
now wait
now hook the phone to the usb and hit power plus volume down
let go of both when you see the bootloader again
now your in fastboot USB
now you can flash the correct recovery to your phone.
next you need this >> http://forum.xda-developers.com/showthread.php?t=2658910

clsA said:
you need to calm down
first turn the phone off
hold power plus volume down
when the phone goes off keep holding volume down and let go of power
now your in the bootloader
use the volume key to select bootloader then power off
now wait
now hook the phone to the usb and hit power plus volume down
let go of both when you see the bootloader again
now your in fastboot USB
now you can flash the correct recovery to your phone.
next you need this >> http://forum.xda-developers.com/showthread.php?t=2658910
Click to expand...
Click to collapse
I followed your instructions but the device doesn't show up in Ubuntu.
But if I try to boot in regular mode, it shows! "Android Phone". The problem is I can't access this, since it just appears for some seconds because this is during the bootloop. Anyway during these seconds, if I click on "Android Phone" it says it cant access it... This is confusing.
I tried both USB 3.0 and 2.0 since I have read 3.0 has problems sometimes.
Should I install any kind of drivers on Ubuntu?

Blocked ONE said:
I followed your instructions but the device doesn't show up in Ubuntu.
But if I try to boot in regular mode, it shows! "Android Phone". The problem is I can't access this, since it just appears for some seconds because this is during the bootloop. Anyway during these seconds, if I click on "Android Phone" it says it cant access it... This is confusing.
I tried both USB 3.0 and 2.0 since I have read 3.0 has problems sometimes.
Should I install any kind of drivers on Ubuntu?
Click to expand...
Click to collapse
From @nkk71 Superguide
5) Q: How do I create a Linux Live USB
Windows users: http://click.xda-developers.com/api...ww.ubuntu.com/download/deskt...ick-on-windows
Mac users: http://www.ubuntu.com/download/deskt...ick-on-mac-osx
Ubuntu 12.04 LTS 32bit ISO from here: http://www.ubuntu.com/download/desktop
Once the Ubuntu Live USB is ready, shutdown your computer and restart from the USB
No need to install, just use the "Try Ubuntu" option
open a terminal
and install adb & fastboot using (copy/paste 1 line at a time into terminal):
Code:
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
you can then check version, by typing "adb version"
and check connection using "adb devices" in custom recovery or booted phone
and "sudo fastboot devices" in bootloader
you can also check @tobesedated guide for more info: [Guide]Suggestion For S-off On 1.55 HBoot Using Ubuntu---Step by step with pictures
Click to expand...
Click to collapse

OK i think im making some progress!!
I am running this ubuntu from USB, installed adb and fastboot, and I think its connected now. At console I type "fastboot devices" and it says: "HT359W90.... fastboot"
Then I downloaded the TWRP 2.7.1.1 and flashed it. Finally I rebooted the phone and now it enters recovery!!!!!! :good: Im now sure the one is not dead!! Thank you so much guys.
Now what? Should I make a factory reset or just go ahead and flash the ROM I intended to get? Don't want to screw it again...
p.s. Apparently I can't push the ROM from ubuntu to sdcard. It says "no such file or directory". And from phone, the ADB Sideload feature doesnt work either, it gest stuck at "starting ADB sideload feature" even after 15 minutes...

Blocked ONE said:
OK i think im making some progress!!
I am running this ubuntu from USB, installed adb and fastboot, and I think its connected now. At console I type "fastboot devices" and it says: "HT359W90.... fastboot"
Then I downloaded the TWRP 2.7.1.1 and flashed it. Finally I rebooted the phone and now it enters recovery!!!!!! :good: Im now sure the one is not dead!! Thank you so much guys.
Now what? Should I make a factory reset or just go ahead and flash the ROM I intended to get? Don't want to screw it again...
p.s. Apparently I can't push the ROM from ubuntu to sdcard. It says "no such file or directory". And from phone, the ADB Sideload feature doesnt work either, it gest stuck at "starting ADB sideload feature" even after 15 minutes...
Click to expand...
Click to collapse
Ok so you have usb Linux working that's great.
What method did you use to install adb/fastboot? Hopefully it was the Webupd8 repository install as this makes life easy.

Danny201281 said:
Ok so you have usb Linux working that's great.
What method did you use to install adb/fastboot? Hopefully it was the Webupd8 repository install as this makes life easy.
Click to expand...
Click to collapse
Yes I followed the method quoted by clsA

Make sure your Rom is compatible with Sprint then to push it to the phone do this.
Boot your Linux usb stick and select the try ubuntu option. Wait for the desktop to load. Open the Home folder. In the top left you should see other drives connected to your pc. Go into your hdd and copy the Rom to the Home folder of the Linux usb and rename it rom.zip.
Now reboot computer, and Wait for it to return to the try/install ubuntu screen. And press
Control + alt + F1 (this will take you to main Linux terminal)
Boot your phone into recovery and connect with usb and type
adb devices (to check phone is detected if phone is not detected see below)
Then
adb push rom.zip /sdcard
If phone is not detected type the following 3 commands waiting for each to complete there out put. Be patient it may seem stuck at some points and you may see some errors but just wait for the terminal to return to normal after each command I.E ready to accept another command. Once all 3 commands have completed try adb devices again.
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot

Danny201281 said:
Make sure your Rom is compatible with Sprint then to push it to the phone do this.
Boot your Linux usb stick and select the try ubuntu option. Wait for the desktop to load. Open the Home folder. In the top left you should see other drives connected to your pc. Go into your hdd and copy the Rom to the Home folder of the Linux usb and rename it rom.zip.
Now reboot computer, and Wait for it to return to the try/install ubuntu screen. And press
Control + alt + F1 (this will take you to main Linux terminal)
Boot your phone into recovery and connect with usb and type
adb devices (to check phone is detected if phone is not detected see below)
Then
adb push rom.zip /sdcard
If phone is not detected type the following 3 commands waiting for each to complete there out put. Be patient it may seem stuck at some points and you may see some errors but just wait for the terminal to return to normal after each command I.E ready to accept another command. Once all 3 commands have completed try adb devices again.
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
Click to expand...
Click to collapse
Ubuntu crashes whenever I press Ctrl+Alt+F1, tried twice and had to reboot.
I was using Ctrl+Alt+T for opening a console. Already did all those 3 commands but not working. This seems challenging! I have read something about 32-bits instructions needed for this? Im running under a 64bit computer and 64 bit linux distribution.
By the way a friend has got an OTG cable, would this work to get a ROM inside the SD-Card?

Blocked ONE said:
Ubuntu crashes whenever I press Ctrl+Alt+F1, tried twice and had to reboot.
I was using Ctrl+Alt+T for opening a console. Already did all those 3 commands but not working. This seems challenging! I have read something about 32-bits instructions needed for this? Im running under a 64bit computer and 64 bit linux distribution.
By the way a friend has got an OTG cable, would this work to get a ROM inside the SD-Card?
Click to expand...
Click to collapse
You should be using 32bit Linux it will run ok on a 64bit machine. But with 64bit Linux you will need to install 32bit libs I think.
Yes an otg cable can be used to copy the Rom to the phone
It's weird that you had Fastboot working but adb won't though. Try using adb without the sudo prefix. It should be working if Fastboot is. But remember you must be in recovery to use adb. Not the bootloader.
Fastboot = bootloader
Adb = recovery

Blocked ONE said:
p.s. Apparently I can't push the ROM from ubuntu to sdcard. It says "no such file or directory".
Click to expand...
Click to collapse
Ok slight brain fart on my part lol. The error you got implies that adb is working but your Rom is not in the right place.
You can put the Rom in the home folder and use the adb push command from the terminal as it is when opened.
Or if the Rom is for instance in the downloads folder you must first use
cd Downloads (to take the terminal to the downloads folder)
Then adb push

More problems lol
Apparently I can't flash any ROM because it says I cant mount cache, data nor internal storage.
Im on TWRP 2.7.1.1

Blocked ONE said:
More problems lol
Apparently I can't flash any ROM because it says I cant mount cache, data nor internal storage.
Im on TWRP 2.7.1.1
Click to expand...
Click to collapse
So you've got the Rom on the phone but when go To recovery you can't see the rom because of this error?
It's normal to see these type of errors after using fastboot erase cache. But not normally with internal storage.
If you can see the Rom just flash it it should work.

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

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

This should absolutely be a sticky!!
Sent from my EVO using XDA Premium 4 mobile app

Evolution_Freak said:
This should absolutely be a sticky!!
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks. I created it specifically to put in the general sticky in my signature. Section 1a and 4

Great work @rootSU definitely should be sticky!

psycho693 said:
Great work @rootSU definitely should be sticky!
Click to expand...
Click to collapse
Thanks. Its in there. All in the main sticky thread
Sent from my Nexus 5 using Tapatalk

rootSU said:
Thanks. Its in there. All in the main sticky thread
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It helps a lot because I have been looking for a good guide to pull system files while the phone is running

psycho693 said:
It helps a lot because I have been looking for a good guide to pull system files while the phone is running
Click to expand...
Click to collapse
Cool
The main thing for me was we had a diagnosis thread and we had a full guide for rooting or returning to stock but nothing to answer the how to set up or how to adb push basic questions... I've seen several threads today alone
Sent from my Nexus 5 using Tapatalk

Very cool, didn't actually know the push/pull commands or that driver you reference

wonderful(really wonderful)!
but i cant find the start button on this toolkit.. :silly:

simms22 said:
wonderful(really wonderful)!
but i cant find the start button on this toolkit.. :silly:
Click to expand...
Click to collapse
LMAO! rootSU, this is freakin awesome. Every thread that I find complaining about issues with toolkits will be redirected here. If this isn't stickied it should be a crime.
Sent from my Nexus 5 using xda premium

I suggested to the mods that we have just one sticky in general that has all the threads we believe to be Stickies within it. That way we can control it ourselves but without making it messy, so we have that now ( see signature).
Sent from my Nexus 5 using Tapatalk

Thanks for listing my Nexus Tools

corbin052198 said:
Thanks for listing my Nexus Tools
Click to expand...
Click to collapse
Thanks for making them
Sent from my Nexus 5 using Tapatalk

simms22 said:
wonderful(really wonderful)!
but i cant find the start button on this toolkit.. :silly:
Click to expand...
Click to collapse
How do I flash the toolkit? I think its bricked :silly:
Good thread.

Amazingly detailed thread. There's no way to mess up reading this thread, the noobs will definitely learn if they can do the reading first that is.
I will laugh when a noob asks, "fastboot? It takes about a minute for me to boot!"
Sent from my Nexus 5 using XDA Premium 4 mobile app

I'm not sure what this all is, but awesome guide!!!!
? I'll be frequently linking this too.

Good job my friend, i am sure it's really helpful for a lot of people
Tapatalk Team SlimRoms

Added the below section about using command prompt. Hopefully a little more detail should help.
A little more about using Windows command prompt
One thing to understand is that like Windows, command prompt (cmd.exe) works with directories (or folders if you like). The Linux and Mac terminals are the same, but most linux users, we expect you would already know this.
Here you will see I have downloaded a recovery image that I want to flash using fastboot.
As you can see, the recovery.img is located in C:\users\rootSU\Desktop
Usually when you open the command prompt from the start menu, or run command, the command prompt will default to your user location as seen below:
So lets try and fastboot flash recovery recovery.img...
It fails with a not-too-accurate error message. It has failed because you have not told it where the recovery image is. It assumes it is in the directory as listed in the prompt
So, how do we deal with this? Well, there are 3 ways.
1) We tell the command prompt where the recovery.img actully is in the command itself
Success! As you can see, we have told the command that the location for the file is Desktop\recovery.img
2) We can change the directory in command prompt to the directory where the file is. In this example, we change directory to "Desktop". The change directory command is "cd <directory>" or in this case "cd Desktop"
3) ...and possibly the simplest method. We hold shift whilst we right-click on the folder we want to change directory to, and directly open a command prompt there:
Click to expand...
Click to collapse

Added a bit more about using directory paths with spaces.
Sent from my Nexus 5 using Tapatalk

After a week with my new nexus, it's time for a litlle fun... But first must say thank you for this explanation.
Sent from my Nexus 5 using Tapatalk 2

[Q] Htc one M7 softbricked and can't connect to a computer

FYI: I am not tech savy at all so bare with me if I sound like a noob/idiot.
I basically formatted my phone from TWRP and I'm thinking there isn't any ROM/UI/kernel?..ect. so it cannot start up (basically stuck on the htc loading screen). My computer detects it but not as a storage device and I can't seem to find a way to access it. I believe I have what i need on my computer but my issue is that i dont know how to get into the internal storage of my htc one because it cannot detect it as a storage device on my computer.
The only trace of it at all i seem to be able to find is in
Control Panel\Hardware and Sound\Devices and Printers
Its called "android 1.0" and when i click on it, it takes me to its properties from device manager.
It says Location: Port_#0001.Hub_#0008
I dont know if any of this info i gave is relevant, if not, let me know what ups.

ray408 said:
FYI: I am not tech savy at all so bare with me if I sound like a noob/idiot.
I basically formatted my phone from TWRP and I'm thinking there isn't any ROM/UI/kernel?..ect. so it cannot start up (basically stuck on the htc loading screen). My computer detects it but not as a storage device and I can't seem to find a way to access it. I believe I have what i need on my computer but my issue is that i dont know how to get into the internal storage of my htc one because it cannot detect it as a storage device on my computer.
The only trace of it at all i seem to be able to find is in
Control Panel\Hardware and Sound\Devices and Printers
Its called "android 1.0" and when i click on it, it takes me to its properties from device manager.
It says Location: Port_#0001.Hub_#0008
I dont know if any of this info i gave is relevant, if not, let me know what ups.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2318497
Here is some reading material for you

Bro..I completely understand your predicament..
Just do this step by step
1. Download minimal adb from the internet and install it on your PC.
2. Download twrp image from the internet.this is a recovery loader.
3.copy the image file into the install directory of minimal adb.
4.execute the minimal adb shortcut from your PC.it should open a command prompt.
5.connect your device to the PC via usb.
6. Type this command to check if your device is recognized. "Fastboot devices"
It should show you a device ID..if your device is connected and recognized
7.flash tarp image with this command "fastboot flash recovery <twrp.img>"
8.reboot your device..press and hold volume down at the sametime to get into bootloader.
9.enter recovery.
10.Download any custom rom from htconeroot.com.it will be a zip file.
11. Copy the zip into minimal adb install directory and run this command to push the zip onto your device. "adb push <image file>.zip any name.zip"
12. After this completes you should be able to see this image in the filemanager in twrp.
13.move the zip file into sdcard directory.
14.make sure all options are checked in the mount in twrp
15.install the custom rom from install option in tarp.
This is 3 frantic days of research on the internet bro..
I had a brick in my hand too..got it up and running VIPERONE ROM
Hope you get through this fine

Thank you, i really appreciate the effort! but im stuck on step 6/7. When i typed in fastboot devices, it didn't show any new id. and when i typed fastboot flash recovery twrp.img it says "waiting on device" so im guessing it still didnt detect it. any idea on why this might be happening? thanks
gowda-the-grear said:
Bro..I completely understand your predicament..
Just do this step by step
1. Download minimal adb from the internet and install it on your PC.
2. Download twrp image from the internet.this is a recovery loader.
3.copy the image file into the install directory of minimal adb.
4.execute the minimal adb shortcut from your PC.it should open a command prompt.
5.connect your device to the PC via usb.
6. Type this command to check if your device is recognized. "Fastboot devices"
It should show you a device ID..if your device is connected and recognized
7.flash tarp image with this command "fastboot flash recovery <twrp.img>"
8.reboot your device..press and hold volume down at the sametime to get into bootloader.
9.enter recovery.
10.Download any custom rom from htconeroot.com.it will be a zip file.
11. Copy the zip into minimal adb install directory and run this command to push the zip onto your device. "adb push <image file>.zip any name.zip"
12. After this completes you should be able to see this image in the filemanager in twrp.
13.move the zip file into sdcard directory.
14.make sure all options are checked in the mount in twrp
15.install the custom rom from install option in tarp.
This is 3 frantic days of research on the internet bro..
I had a brick in my hand too..got it up and running VIPERONE ROM
Hope you get through this fine
Click to expand...
Click to collapse

ray408 said:
Thank you, i really appreciate the effort! but im stuck on step 6/7. When i typed in fastboot devices, it didn't show any new id. and when i typed fastboot flash recovery twrp.img it says "waiting on device" so im guessing it still didnt detect it. any idea on why this might be happening? thanks
Click to expand...
Click to collapse
Ok..try this..
Press down on the power and volume down button to enter the default boot loader.
If you hv rooted your phone..it should be showing tampered at the top.
select the fast boot option..
Now connect your phone via usb..
The display name should change to "fastboot usb"
Then again open minimal adb and continue from step 6.
Make sure you have all the htc drivers for Windows installed on your PC.
Windows can automatically download these drivers for you if you don't have them..
All the best

Are you using Windows 8.1?

everything works now, thank you guys. You are all awesome!

I think I seriously messed up my phone, can't copy stuff over while TWRP :(

Guys I have TWRP V2.8.10...I was trying to install ViperOne Rom. I had in installed but I foolishly did a FULL ADVANCED Whipe...Idk why I did that I wasn't thinking about it...well naturally it wiped the ROM clean off the device as well as EVERYTHING else. I don't even have my backup to restore to. UGH I'm so frustrated with myself. Well anyways I try to enable MTP while in TWRP and its shows the HTC One as a portable device as well as havin 24.9 of 25.0 GB of FREE Space however it will NOT let me copy the ViperOne ROM over....it keeps saying the file size is too large. IT most certainly is NOT too large. There has to be someway around this to FORCE this file onto to the device for a reflash. Any help would be appreciated here. Idk if this is a windows thing but I was thinking I could maybe even attach a micro to full size usb plug to the htc and put the rom on a flash drive and flash it onto the device but idk if this would work. I should also note that when I open internal storage on the device it only shows the TWRP folder. I'm half wondering if the device has lost its root as well...will a reflash over the terminal maybe help?

gravatrax1 said:
Guys I have TWRP V2.8.10...I was trying to install ViperOne Rom. I had in installed but I foolishly did a FULL ADVANCED Whipe...Idk why I did that I wasn't thinking about it...well naturally it wiped the ROM clean off the device as well as EVERYTHING else. I don't even have my backup to restore to. UGH I'm so frustrated with myself. Well anyways I try to enable MTP while in TWRP and its shows the HTC One as a portable device as well as havin 24.9 of 25.0 GB of FREE Space however it will NOT let me copy the ViperOne ROM over....it keeps saying the file size is too large. IT most certainly is NOT too large. There has to be someway around this to FORCE this file onto to the device for a reflash. Any help would be appreciated here. Idk if this is a windows thing but I was thinking I could maybe even attach a micro to full size usb plug to the htc and put the rom on a flash drive and flash it onto the device but idk if this would work.
Click to expand...
Click to collapse
If you have a USB-OTG adapter it will certainly work.
your other options are adb push rom.zip /sdcard
and adb sideload rom.zip
just be sure the rom.zip is in the same folder as adb

I have a fastboot folder on my desktop the directory is
C:\Users\GRAVATRAX\Desktop\fastboot
VIPER adb and fastboot are all in the same folder, how would enter this into the command terminal? I'm following instructions that I found but it cames throwing me errors
Attached a pic, what am i doing wrong here lol

gravatrax1 said:
I have a fastboot folder on my desktop the directory is
C:\Users\GRAVATRAX\Desktop\fastboot
VIPER adb and fastboot are all in the same folder, how would enter this into the command terminal? I'm following instructions that I found but it cames throwing me errors
Attached a pic, what am i doing wrong here lol
Click to expand...
Click to collapse
What does your storage show as in recovery? 0mb?
Since you wiped it all anyway you may as well try Wipe>Format Data, from within twrp. You will be prompted to type yes to confirm. When its done reboot recovery and try MTP again.
As for using adb and fastboot. Do this, Hold Shift and Right Click on your fastboot folder. From the drop down menu that appears select "Open a command window here" this should open a cmd prompt with your fastboot folder as it's working directory.
Now use the push command
Code:
adb push viper.zip /sdcard
The command window will appear unresponsive until the push completes. When it's done install the Rom with your recovery.

Danny201281 said:
What does your storage show as in recovery? 0mb?
Since you wiped it all anyway you may as well try Wipe>Format Data, from within twrp. You will be prompted to type yes to confirm. When its done reboot recovery and try MTP again.
As for using adb and fastboot. Do this, Hold Shift and Right Click on your fastboot folder. From the drop down menu that appears select "Open a command window here" this should open a cmd prompt with your fastboot folder as it's working directory.
Now use the push command
Code:
adb push viper.zip /sdcard
The command window will appear unresponsive until the push completes. When it's done install the Rom with your recovery.
Click to expand...
Click to collapse
How long does it usually take to transfer files via this method? It shows the file onthe device but in the amount of like 128kb, will it give some sort of confirmation when its done?
Also in recovery it would show the device as having an internal storage os 26034.
If this doesn't work where I can find an otg cable? Would it be possible to use lets say a male to female usb adapter with a standard micro usb cable to achieve this effect

gravatrax1 said:
How long does it usually take to transfer files via this method? It shows the file onthe device but in the amount of like 128kb, will it give some sort of confirmation when its done?
Click to expand...
Click to collapse
While the Rom is being pushed you will see only a blinking cursor in the command window. When it's complete you should get a confirmation and the prompt will return to normal
It can take several minutes.
A basic OTG cable looks like this
{
"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"
}
But they com in all sorts of shapes and sizes I use one like this
Picked up in my local tesco for a few quid

Danny201281 said:
While the Rom is being pushed you will see only a blinking cursor in the command window. When it's complete you should get a confirmation and the prompt will return to normal
It can take several minutes.
Click to expand...
Click to collapse
Alright Ill just be patient and let it do its thing....I tried to push the file via adb sideload however it kept saying device not found And yes i would enable ADB sideload via TWR
I might have to take a trip down to best buy and staples nad see if I can find one...I would call and see if they have what Im looking for...but LOL.
SO while we are waiting for this file to be pushed I am curious as to why this is happening. what exactly did I do for it cause to bring me this issue in Windows?

gravatrax1 said:
Alright Ill just be patient and let it do its thing....I tried to push the file via adb sideload however it kept saying device not found And yes i would enable ADB sideload via TWR
I might have to take a trip down to best buy and staples nad see if I can find one...I would call and see if they have what Im looking for...but LOL.
Click to expand...
Click to collapse
you need to fix your pc drivers while the phone is in recovery
look for the one in device manager with an exclamation mark and update the driver manually

clsA said:
you need to fix your pc drivers while the phone is in recovery
look for the one in device manager with an exclamation mark and update the driver manually
Click to expand...
Click to collapse
The deivce manager shows no issues with the drivers :/
Still trying to push the file...something gotta be wrong here.

gravatrax1 said:
Alright Ill just be patient and let it do its thing....I tried to push the file via adb sideload however it kept saying device not found And yes i would enable ADB sideload via TWR
I might have to take a trip down to best buy and staples nad see if I can find one...I would call and see if they have what Im looking for...but LOL.
SO while we are waiting for this file to be pushed I am curious as to why this is happening. what exactly did I do for it cause to bring me this issue in Windows?
Click to expand...
Click to collapse
Check your SDK is upto date by typing this into the fastboot command window
Code:
adb version
The latest is 1.0.32.
Also you may try TWRP 2.6.3.3 some other versions of TWRP have issues with adb. :good:
EDIT:- Infact reading back to your first post i see your using TWRP 2.8.1.0. It's been a while since i first tested that version but i'm sure I ditched it because of problems with adb

Device not detected in Fastbootmode.

SOLVED:
The reason Device was not detected in Fastbootmode was due to my new ryzen 3000 system, I tried it on my much older quad core 46XXk(?) Intel system and it gave me no problems whatsoever finding the device in fastboot mode in my first try! wtf amd!
The second Set of problems came with flashing 16.0631.1910.64. It gave me a ton of errors and it was on an infinite boot loop, nothing I tried fixed it, my device was a worthless brick in that state, but fastboot Power+Volume up > 16.0631.1910.64 worked perfectly.
I decided to instead try 16.0631.1910.35, but once I flashed it everything worked perfectly! I am in the latest version of android 10 atm and can acess banks, play nintendo games, etc with the rooted device.
Hi, I bought this phone (Rog 2) mostly Intended as a donation for a friend that was complaining on facebook that he's probably going to be homeless due to covid and didnt even have his phone since he cracked the screen. While I cant help with housing I can help with a measly phone and I heard for gaming this is one of the best.
I got the tencent version not knowing what the heck I was getting myself into ( I thought all ROG 2 were the same and didn't even think to look it up). Been googling for days, I am trying to make this a full WW variant and basically as hassle free as possible for him, it seems that it has an obscure version of "pkq1.190414.001.ww_phone-16.0622.1906.19-0 " Rom, but according to HWInfo the fingerprint is CN.
Problem is I tried following this guide, I unlocked the bootloader with the ROG phone unlock tool, but on step 2 I load into fastboot, click flashall_AFT but all I see is a cmd with the message [command] : fastboot.exe flash all WW_ZS660KL_16.0631.1910.35_M3.13.33.30-ASUS_1.1.207_Phone-user.raw and nothing happens.
I noticed that on the cmd of the minimal adb devices and fastboot folder, the "adb devices" gives my device , the "adb reboot bootloader" works by taking me to the bootloader, but the "fastboot devices" does not give me anything at all once im in bootloader. In fact when using adb reboot bootloader I hear the windows beep as if the cellphone is disconecting. Any ideas what is going on?

TeknoViking- said:
Hi, I bought this phone (Rog 2) mostly Intended as a donation for a friend that was complaining on facebook that he's probably going to be homeless due to covid and didnt even have his phone since he cracked the screen. While I cant help with housing I can help with a measly phone and I heard for gaming this is one of the best.
I got the tencent version not knowing what the heck I was getting myself into ( I thought all ROG 2 were the same and didn't even think to look it up). Been googling for days, I am trying to make this a full WW variant and basically as hassle free as possible for him, it seems that it has an obscure version of "pkq1.190414.001.ww_phone-16.0622.1906.19-0 " Rom, but according to HWInfo the fingerprint is CN.
Problem is I tried following this guide, I unlocked the bootloader with the ROG phone unlock tool, but on step 2 I load into fastboot, click flashall_AFT but all I see is a cmd with the message [command] : fastboot.exe flash all WW_ZS660KL_16.0631.1910.35_M3.13.33.30-ASUS_1.1.207_Phone-user.raw and nothing happens.
I noticed that on the cmd of the minimal adb devices and fastboot folder, the "adb devices" gives my device , the "adb reboot bootloader" works by taking me to the bootloader, but the "fastboot devices" does not give me anything at all once im in bootloader. In fact when using adb reboot bootloader I hear the windows beep as if the cellphone is disconecting. Any ideas what is going on?
Click to expand...
Click to collapse
Have you installed adb drivers https://github.com/koush/UniversalAdbDriver
Also, just checking the obvious, you are using the side port of the phone, not the bottom, right?

reg66 said:
Have you installed adb drivers https://github.com/koush/UniversalAdbDriver
Also, just checking the obvious, you are using the side port of the phone, not the bottom, right?
Click to expand...
Click to collapse
Hi! Yeah, I have the exact same driver you mentioned as well as Minimal ADB and Fastboot and using the black sideport.
It seems when I connect it during the fastboot(Green arrow menu) I do hear the "USB Device plugged" sound so there's that.
flashall_AFT still just gives me a black page with: [command] : fastboot.exe flash all WW_ZS660KL_16.0631.1910.35_M3.13.33.30-ASUS_1.1.207_Phone-user.raw

TeknoViking- said:
Hi! Yeah, I have the exact same driver you mentioned as well as Minimal ADB and Fastboot and using the black sideport.
It seems when I connect it during the fastboot(Green arrow menu) I do hear the "USB Device plugged" sound so there's that.
flashall_AFT still just gives me a black page with: [command] : fastboot.exe flash all WW_ZS660KL_16.0631.1910.35_M3.13.33.30-ASUS_1.1.207_Phone-user.raw
Click to expand...
Click to collapse
Before running flashall_AFT.cmd, when you hear the device connect, have you tried entering 'fastboot devices' before doing anything else? See if it gives you a serial. If it does.
Then have you removed the original zip file from the extracted folder that contains the raw img? Once you click flashall_AFT.cmd, the cmd window should stay open for around 5 minutes while the flash takes place, then the phone will reboot once done

reg66 said:
Before running flashall_AFT.cmd, when you hear the device connect, have you tried entering 'fastboot devices' before doing anything else? See if it gives you a serial. If it does.
Then have you removed the original zip file from the extracted folder that contains the raw img? Once you click flashall_AFT.cmd, the cmd window should stay open for around 5 minutes while the flash takes place, then the phone will reboot once done
Click to expand...
Click to collapse
Top left image is from using the "fastboot devices" command, as you can see I type it it doesn't show or seem to do anything really. The right image is from clicking flashall_AFT, both inside bootloader on my rog 2 and outside give the same result.
The Zip file? As in the 2.7 one I downloaded? Yeah that content of that is in a folder in root of C drive, the zip is in a completely different drive so they are not sharing a directory . I did not modify anything inside the extracted file though.
For reference I am following the steps here: https://forum.xda-developers.com/t/...rom-cn-to-ww-with-latest-1910-35-raw.4002279/
{
"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"
}

TeknoViking- said:
Top left image is from using the "fastboot devices" command, as you can see I type it it doesn't show or seem to do anything really. The right image is from clicking flashall_AFT, both inside bootloader on my rog 2 and outside give the same result.
The Zip file? As in the 2.7 one I downloaded? Yeah that content of that is in a folder in root of C drive, the zip is in a completely different drive so they are not sharing a directory . I did not modify anything inside the extracted file though.
For reference I am following the steps here: https://forum.xda-developers.com/t/...rom-cn-to-ww-with-latest-1910-35-raw.4002279/
View attachment 5173971
Click to expand...
Click to collapse
Ok, try unpacking the attached zip to root of C, like the other adb folder. Then click on 'cmd-here.exe' to launch cmd window and then try 'fastboot devices'. (that's assuming the drivers of the original install are working). Let me know if you get a serial response.

reg66 said:
Ok, try unpacking the attached zip to root of C, like the other adb folder. Then click on 'cmd-here.exe' to launch cmd window and then try 'fastboot devices'. (that's assuming the drivers of the original install are working). Let me know if you get a serial response.
Click to expand...
Click to collapse
Done, nothing happens, did it multiple times here's what I get:

TeknoViking- said:
Done, nothing happens, did it multiple times here's what I get:
Click to expand...
Click to collapse
Ok, what a pain! Try uninstall minimal adb drivers and I'll see if I can find ano version for you....

reg66 said:
Ok, what a pain! Try uninstall minimal adb drivers and I'll see if I can find ano version for you....
Click to expand...
Click to collapse
Will do! ty

TeknoViking- said:
Will do! ty
Click to expand...
Click to collapse
try this version, after installing the drivers you could also try that folder with the cmd-here file in combination. Also, try booting into android os and enable developer options (click on 'build' 7 or so times in settings/system/about phone/software information/build number), then go to developer options and enable USB debugging - might make a difference...

Also, check your pm, I sent you modified instructions for using the other guide that'll take you straight to last Android 9 version before you can update to Android 10 (1910.64). You could always be downloading that newer RAW + root img while tinkering with getting the damn thing recognised by your pc!!

Tried the 1910.64 you sent me and its the same problem unfortunately, still stuck on step 2. I already had USB debugging with the "USB debugging" option ticked on when I created the topic.
I take it doing number 4 Is a bad idea if can't get past 2? "4) Download the root&bootstockww191035.zip "rootww191064" and extract it to the Minimal ADB and Fastboot Folder (C:\Program Files (x86)\Minimal ADB and Fastboot) from here "

TeknoViking- said:
Tried the 1910.64 you sent me and its the same problem unfortunately, still stuck on step 2. I already had USB debugging with the "USB debugging" option ticked on when I created the topic.
I take it doing number 4 Is a bad idea if can't get past 2? "4) Download the root&bootstockww191035.zip "rootww191064" and extract it to the Minimal ADB and Fastboot Folder (C:\Program Files (x86)\Minimal ADB and Fastboot) from here "
Click to expand...
Click to collapse
Yeah, there's no point continuing until you can get fastboot devices to at least show your device. Do you have another pc/laptop you could try on? Are you using an AMD based system, pretty sure I read somewhere that can give issues, along with the system used! Sorry that's a bit vague...

TeknoViking- said:
Tried the 1910.64 you sent me and its the same problem unfortunately, still stuck on step 2. I already had USB debugging with the "USB debugging" option ticked on when I created the topic.
I take it doing number 4 Is a bad idea if can't get past 2? "4) Download the root&bootstockww191035.zip "rootww191064" and extract it to the Minimal ADB and Fastboot Folder (C:\Program Files (x86)\Minimal ADB and Fastboot) from here "
Click to expand...
Click to collapse
Oh sorry, you meant try flashing the root img, NO, definitely not. The root img MUST only flashed after successful flashing of RAW - both rom and boot/root boot img's must match. (But either way, if your device isn't recognised by fastboot it just won't flash, just an FYI)

See this thread for info on Ryzen issues, if that is what you're running. The OP says he used an external USB hub as a solution

reg66 said:
Yeah, there's no point continuing until you can get fastboot devices to at least show your device. Do you have another pc/laptop you could try on? Are you using an AMD based system, pretty sure I read somewhere that can give issues, along with the system used! Sorry that's a bit vague...
Click to expand...
Click to collapse
Ok I tried this on my intel system and it detected it!! "fastboot devices" gave me the serial. So when I tried to do step 2 and I used ADB_FASTBOOT to run flashall_AFT from the 1910.64 it failed and it it seems to be on a loop in bootloader "The boot loader is unlocked and software integrity cannot be guaranteed..) etc screen.
I attached the image. This is with the 1910.64 on step two.

Also I got this from continually trying to boot:

TeknoViking- said:
Ok I tried this on my intel system and it detected it!! "fastboot devices" gave me the serial. So when I tried to do step 2 and I used ADB_FASTBOOT to run flashall_AFT from the 1910.64 it failed and it it seems to be on a loop in bootloader "The boot loader is unlocked and software integrity cannot be guaranteed..) etc screen.
I attached the image. This is with the 1910.64 on step two.
Click to expand...
Click to collapse
Hmm, this phone is troublesome. Sorry dude, I've not seen that before. The bootloader unlock tool definitely worked, right? What about if you try using the original 1910.35 RAW - same error?

TeknoViking- said:
Also I got this from continually trying to boot:
Click to expand...
Click to collapse
Do you have above 50% charge? If not, definitely make sure to have enough charge for the whole process. I was always of the understanding, as a rule of thumb, to have devices above 50% before performing flashing of custom roms etc

reg66 said:
Do you have above 50% charge? If not, definitely make sure to have enough charge for the whole process. I was always of the understanding, as a rule of thumb, to have devices above 50% before performing flashing of custom roms etc
Click to expand...
Click to collapse
Yeah the charge is over 90 percent, anything I can do for that error? when I connect to the intel pc it doesn't even beep any more. I still can access the boot screen though.
EDIT: OOPS, noticed I had it plugged on the bottom, nvm intel system still detects the device. I did perform everything on the side port usb but I took it out to try and check back on the ryzen system.