Database Users

Installing Ubuntu Phone on using Mac OS X and ADB / Fastboot

I thought there might be a few people who have Macs with questions who'd like to get a quick express guide to getting up and running with Ubuntu Touch on their phone. This isn't that different than flashing your ROM and in fact is the same procedure on linux or windows except the adb and fastboot bins come from somewhere else.
* If you don't already have it, install ADB and Fastboot
http://code.google.com/p/adb-fastboot-install/
* Download the five images files for your device from Ubuntu
http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/
CODENAMES
Galaxy Nexus - maguro
Nexus 4 - mako
Nexus 7 - grouper
Nexus 10 - manta​
quantal-preinstalled-boot-armel+CODENAME.img
quantal-preinstalled-recovery-armel+CODENAME.img
quantal-preinstalled-system-armel+CODENAME.img
quantal-preinstalled-armel+CODENAME.img
All Phones need this main image
quantal-preinstalled-phablet-armhf.img
* Plug in your phone and open a terminal to the folder where you saved the images. Unlock your phone if it's not already.
Code:
fastboot oem unlock
* Power your device down and enter fastboot by holding both volume buttons and the power button until the phone comes on.
* In fastboot, enter the following commands in the terminal:
Be sure to replace CODENAME with your device's code name.
Code:
fastboot flash recovery recovery-quantal-preinstalled-armel+CODENAME.img
fastboot flash system quantal-preinstalled-system-armel+CODENAME.img
fastboot flash boot quantal-preinstalled-boot-armel+CODENAME.img
* Use the volume keys to choose recovery and press the power button
* Enter the following command in the terminal:
Code:
adb sideload quantal-preinstalled-armel+CODENAME.zip
Wait for the sideload to finish.
If you see the message “fixing fs_size in crypto footer”, it’s finished.
From the main menu choose "Advanced" and "Reboot" to recovery.
When the phone has rebooted back to recovery, execute the following command in the terminal:
Code:
adb sideload quantal-preinstalled-phablet-armhf.zip”
When the sideload is finished, restart the device.
Now you're running Ubuntu.

Wouldn't this also work on Windows?
PHONE SLOW CLICK ME?
_____________________________________
"If your doing the right thing then to hell with everyone else -Deadly"​

TingTingin said:
Wouldn't this also work on Windows?
PHONE SLOW CLICK ME?
_____________________________________
"If your doing the right thing then to hell with everyone else -Deadly"​
Click to expand...
Click to collapse
There should be no reason why not (Same with Linux)

TingTingin said:
Wouldn't this also work on Windows?
PHONE SLOW CLICK ME?
_____________________________________
"If your doing the right thing then to hell with everyone else -Deadly"​
Click to expand...
Click to collapse
yes. they are the same instructions on linux, mac, and windows

Pirateghost said:
yes. they are the same instructions on linux, mac, and windows
Click to expand...
Click to collapse
I did mention that
- Nexus 4 / PA 3 / Franco r83 -

Hmm... I keep getting an error when trying to load the recovery. Weird since the other 2 work. Let me check the MD5Sum. I'm on Windows.
EDIT: Fixed: I just used this link and followed the instructions here. http://liliputing.com/2013/02/how-t...h-on-a-nexus-7-with-windows-mac-or-linux.html I didn't really know what was going on with your instructions. =.3 I'm sorry.

can you show some photo for your operating...i'm very interesting..............

Thank you so much, I did it with linux. Just add a couple of things;
To fastboot mode you just need volum down botton.
I had error with adb sideload (never before flashing android roms), but I solve executing "adb usb" just before adb sideload, in both cases (maybe is a problem with the last recovery...)

I also got the error: closed message
To fix first do ADB Devices to ensure that your system in online then in the recovery screen on your device select 'INSTALL ZIP FROM SIDELOAD' and reexecute the command in terminal

how to use galaxy s3 mini ? it's not fastboot mode

[Solved] Stuck in Fastboot, USB does not connect

Hi.
I need help. I already checked any relating topics on this and other boards, but I couldn't find any help.
I tried to flash TWRP Recovery with the "All-In-One-Tool", but as soon as the phone entered fastboot-mode it couldn't be recognized by the system anymore.
Error Code 43. (USB\DEVICE_DESCRIPTOR_FAILURE)
I am running a Windows 10 Machine.
Solutions I already tried:
- using different drivers (lenovo v1.1.16, zuk v1.0.8, latest google usb drivers from sdk)
- with deactivated driver-signing-check (or what it is called)
- different adb, fastboot tools (mini adb, etc.)
- running live cd of FWUI (forget windows use linux)
- using different usb ports on my pc
Additional to that, my power-button isn't working anymore (since a few weeks now) and I have no idea how to reboot my phone.
I would really appreciate your help.

Follow these steps to install twrp in easy manner:
1.Firstly install lenovo usb drivers.( look download one at bottom of this post for files)
2.Then Go to the adb driver folder and do install necessary set ups according to your system(64 bit or 32 bit).
3.Now go back and move to AndroidSDKSlim\android-sdk-windows\platform-tools folder (put on your phone into bootloader mode and connect usb).
4.Type fastboot -i 0x2b4c devices in cmd and see if there is a reply.If you got reply It means that your drivers are properly installed otherwise not.
5.Once you get reply type fastboot -i 0x2b4c flash recovery twrp_recovery.img
6.After flashing done Disconnect USB then go to the recovery mode and that's it you will see twrp installed as successfully.
(To boot your Device into recovery mode, just turn your device off and then press and hold volume down and power keys at the same time)
Note: It worked for me in windows 10(64 bit).Don't disconnect Usb from your PC while flashing Twrp.
Download:Because xda won't allowing me to put download links up to 10 posts as i'm new So give your email in reply i will send files to that email.
thank you.

delete

Problem solved. I don't know the exact solution.
I waited until the battery was empty and recharged it, phone was booting normal. I installed another set of lenovo driver on my pc and gave it a shot. This time the device got recognized by windows and i was able to unlock the bootloader and flash the recovery.

Stuck in Fastboot, USB does not connect
srk2521 said:
Follow these steps to install twrp in easy manner:
1.Firstly install lenovo usb drivers.( look download one at bottom of this post for files)
2.Then Go to the adb driver folder and do install necessary set ups according to your system(64 bit or 32 bit).
3.Now go back and move to AndroidSDKSlim\android-sdk-windows\platform-tools folder (put on your phone into bootloader mode and connect usb).
4.Type fastboot -i 0x2b4c devices in cmd and see if there is a reply.If you got reply It means that your drivers are properly installed otherwise not.
5.Once you get reply type fastboot -i 0x2b4c flash recovery twrp_recovery.img
6.After flashing done Disconnect USB then go to the recovery mode and that's it you will see twrp installed as successfully.
(To boot your Device into recovery mode, just turn your device off and then press and hold volume down and power keys at the same time)
Note: It worked for me in windows 10(64 bit).Don't disconnect Usb from your PC while flashing Twrp.
Download:Because xda won't allowing me to put download links up to 10 posts as i'm new So give your email in reply i will send files to that email.
thank you.
Click to expand...
Click to collapse
Please send the download link to my email id : [email protected]
Thank you in Advance.

srk2521 said:
Follow these steps to install twrp in easy manner:
1.Firstly install lenovo usb drivers.( look download one at bottom of this post for files)
2.Then Go to the adb driver folder and do install necessary set ups according to your system(64 bit or 32 bit).
3.Now go back and move to AndroidSDKSlim\android-sdk-windows\platform-tools folder (put on your phone into bootloader mode and connect usb).
4.Type fastboot -i 0x2b4c devices in cmd and see if there is a reply.If you got reply It means that your drivers are properly installed otherwise not.
5.Once you get reply type fastboot -i 0x2b4c flash recovery twrp_recovery.img
6.After flashing done Disconnect USB then go to the recovery mode and that's it you will see twrp installed as successfully.
(To boot your Device into recovery mode, just turn your device off and then press and hold volume down and power keys at the same time)
Note: It worked for me in windows 10(64 bit).Don't disconnect Usb from your PC while flashing Twrp.
Download:Because xda won't allowing me to put download links up to 10 posts as i'm new So give your email in reply i will send files to that email.
thank you.
Click to expand...
Click to collapse
When i am connecting my lenovo zuk z1 in laptop its only charging......does not recognize my zuk z1..i am getting irritating..
plz solve this issue....
send me also personally...
thanks for advance
my mail id: [email protected]

srk2521 said:
Follow these steps to install twrp in easy manner:
1.Firstly install lenovo usb drivers.( look download one at bottom of this post for files)
2.Then Go to the adb driver folder and do install necessary set ups according to your system(64 bit or 32 bit).
3.Now go back and move to AndroidSDKSlim\android-sdk-windows\platform-tools folder (put on your phone into bootloader mode and connect usb).
4.Type fastboot -i 0x2b4c devices in cmd and see if there is a reply.If you got reply It means that your drivers are properly installed otherwise not.
5.Once you get reply type fastboot -i 0x2b4c flash recovery twrp_recovery.img
6.After flashing done Disconnect USB then go to the recovery mode and that's it you will see twrp installed as successfully.
(To boot your Device into recovery mode, just turn your device off and then press and hold volume down and power keys at the same time)
Note: It worked for me in windows 10(64 bit).Don't disconnect Usb from your PC while flashing Twrp.
Download:Because xda won't allowing me to put download links up to 10 posts as i'm new So give your email in reply i will send files to that email.
thank you.
Click to expand...
Click to collapse
Same happened to me..computer not recognising my phone (zuk z1 ham) even after installing drivers.
It is showing usb not recognized in device manager.and Please share fastboot tutorial for flashing stock rom as I also hardbricked my phone.
Send me files to= [email protected]
thanks i advance.:angel:

hello, may i have the drivers to my dnalexxio on gmail com mailbox?
thanks

Help me my dear friend!!!!
srk2521 said:
Follow these steps to install twrp in easy manner:
1.Firstly install lenovo usb drivers.( look download one at bottom of this post for files)
2.Then Go to the adb driver folder and do install necessary set ups according to your system(64 bit or 32 bit).
3.Now go back and move to AndroidSDKSlim\android-sdk-windows\platform-tools folder (put on your phone into bootloader mode and connect usb).
4.Type fastboot -i 0x2b4c devices in cmd and see if there is a reply.If you got reply It means that your drivers are properly installed otherwise not.
5.Once you get reply type fastboot -i 0x2b4c flash recovery twrp_recovery.img
6.After flashing done Disconnect USB then go to the recovery mode and that's it you will see twrp installed as successfully.
(To boot your Device into recovery mode, just turn your device off and then press and hold volume down and power keys at the same time)
Note: It worked for me in windows 10(64 bit).Don't disconnect Usb from your PC while flashing Twrp.
Download:Because xda won't allowing me to put download links up to 10 posts as i'm new So give your email in reply i will send files to that email.
thank you.
Click to expand...
Click to collapse
Email ID: [email protected]
Pls send me the files as soon as possible.......... I will be grateful to you!

srk2521 said:
Follow these steps to install twrp in easy manner:
1.Firstly install lenovo usb drivers.( look download one at bottom of this post for files)
2.Then Go to the adb driver folder and do install necessary set ups according to your system(64 bit or 32 bit).
3.Now go back and move to AndroidSDKSlim\android-sdk-windows\platform-tools folder (put on your phone into bootloader mode and connect usb).
4.Type fastboot -i 0x2b4c devices in cmd and see if there is a reply.If you got reply It means that your drivers are properly installed otherwise not.
5.Once you get reply type fastboot -i 0x2b4c flash recovery twrp_recovery.img
6.After flashing done Disconnect USB then go to the recovery mode and that's it you will see twrp installed as successfully.
(To boot your Device into recovery mode, just turn your device off and then press and hold volume down and power keys at the same time)
Note: It worked for me in windows 10(64 bit).Don't disconnect Usb from your PC while flashing Twrp.
Download:Because xda won't allowing me to put download links up to 10 posts as i'm new So give your email in reply i will send files to that email.
thank you.
Click to expand...
Click to collapse
Please email me at [email protected] Thank you!!

Stuck in fastboot
srk2521 said:
Follow these steps to install twrp in easy manner:
1.Firstly install lenovo usb drivers.( look download one at bottom of this post for files)
2.Then Go to the adb driver folder and do install necessary set ups according to your system(64 bit or 32 bit).
3.Now go back and move to AndroidSDKSlim\android-sdk-windows\platform-tools folder (put on your phone into bootloader mode and connect usb).
4.Type fastboot -i 0x2b4c devices in cmd and see if there is a reply.If you got reply It means that your drivers are properly installed otherwise not.
5.Once you get reply type fastboot -i 0x2b4c flash recovery twrp_recovery.img
6.After flashing done Disconnect USB then go to the recovery mode and that's it you will see twrp installed as successfully.
(To boot your Device into recovery mode, just turn your device off and then press and hold volume down and power keys at the same time)
Note: It worked for me in windows 10(64 bit).Don't disconnect Usb from your PC while flashing Twrp.
Download:Because xda won't allowing me to put download links up to 10 posts as i'm new So give your email in reply i will send files to that email.
thank you.
Click to expand...
Click to collapse
Same here, I'm desperately trying to unlock the bootloader. On Windows 10 adb correctly recognize my Z1, but when I reboot in fastboot mode I can't get past the "<waiting for device>" message.
Could you please send a download link to [email protected]?
Thanks a lot!

srk2521 said:
Follow these steps to install twrp in easy manner:
1.Firstly install lenovo usb drivers.( look download one at bottom of this post for files)
2.Then Go to the adb driver folder and do install necessary set ups according to your system(64 bit or 32 bit).
3.Now go back and move to AndroidSDKSlim\android-sdk-windows\platform-tools folder (put on your phone into bootloader mode and connect usb).
4.Type fastboot -i 0x2b4c devices in cmd and see if there is a reply.If you got reply It means that your drivers are properly installed otherwise not.
5.Once you get reply type fastboot -i 0x2b4c flash recovery twrp_recovery.img
6.After flashing done Disconnect USB then go to the recovery mode and that's it you will see twrp installed as successfully.
(To boot your Device into recovery mode, just turn your device off and then press and hold volume down and power keys at the same time)
Note: It worked for me in windows 10(64 bit).Don't disconnect Usb from your PC while flashing Twrp.
Download:Because xda won't allowing me to put download links up to 10 posts as i'm new So give your email in reply i will send files to that email.
thank you.
Click to expand...
Click to collapse
Can you please send me on [email protected]
Thanks in advance

Need Link for Fastboot Drivers
Please send the download link to me on [email protected]

VictKibal said:
Same here, I'm desperately trying to unlock the bootloader. On Windows 10 adb correctly recognize my Z1, but when I reboot in fastboot mode I can't get past the "<waiting for device>" message.
Could you please send a download link to [email protected]?
Thanks a lot!
Click to expand...
Click to collapse
santakittu said:
Can you please send me on [email protected]
Thanks in advance
Click to expand...
Click to collapse
waqas9783 said:
Please send the download link to me on [email protected]
Click to expand...
Click to collapse
Here are working drivers I used for my Zuk Z1 many times on windows 10 without problems.
https://drive.google.com/folderview?id=0B4Zy8uoEfFKLRFlCNVJ6aGxlYVk
I posted these drivers in other threads too
Please do not give your private mail here...

A1 stuck in bootloop

Let me know if this post belongs somewhere else.
My Mi A1 is stuck in a bootloop as a result of trying to install magisk 14.4. At the moment I can boot it into fastboot mode, but not into recovery mode. In fastboot I can execute the command
fastboot devices
that returns the hex number followed by "fastboot." However, it does not respond to any other fastboot commands, e.g.
fastboot reboot
fastboot oem device-info
I have been attempting to flash the stock rom without success as follows:
in win10 32-bit environment:
fastboot responds as above. I cannot install the MiFlash-2017-7-20 version. Windows complains. I conclude that version must be a w10 64-bit app, although it doesn't say so.
win10 64-bit
MiFlash-2017-7-20 installs and runs, but does not see the device. Apparently, the adb drivers are at fault. I have turned off signature enforcement and tried installing various versions of the adb drivers. The device manager shows them as installed, but reports that they cannot start.
Centos 7 linux
Adb drivers install. "Fastboot devices" reports correctly. All other fastboot commands fail, i.e. they hang. I tried installing the tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794 image using the linux shell script provided, but that just hung also.
Is this phone well and truly bricked at this point? Is there any other recovery available?

I think it is not hard bricked by any means. Try booting into the Quallcomm EDL and try flashing the fastboot rom with MiFlash too. You can setup a virtual environment in which the flash tool can run and the drivers can install properly.

Maybe you should boot to other partition (A or B)
Just fastboot then try boot to other partition, hope it works

GalihBK said:
Maybe you should boot to other partition (A or B)
Just fastboot then try boot to other partition, hope it works
Click to expand...
Click to collapse
As he said, he can't execute fastboot commands so that isn't a option.

@yuoip
1. You say that "fastboot devices" works, but "fastboot reboot" not. What error do you receive? Could you paste full log?
2. Sometimes drivers in Windows must be installed manually - open device manager, find unknown device, choose from list and find and choose "android fastboot" or "android adb" device depending on the mode you're in. If you have installed fastboot device before, you should be good to go. Otherwise you'll need to download minimal adb package (https://freeandroidroot.com/download-minimal-adb-and-fastboot-all-versions/), or Google development kit (much larger).
3. stock recovery mode is started by pressing "power button + volume up", once "no command" screen appears, press shortly "power button + volume up" to show the menu.
4. please post full log of command "adb devices" as well

Hola guys. I got mostly the same issue here. While I still can use adb comand while on fastboot. But i can't flash stock rom using mi flash.. i mean after the done notice my phone still stuck and wont reboot. Like the flash doesnt apply to the phone. I wonder what was wrong

dhewaghost said:
Hola guys. I got mostly the same issue here. While I still can use adb comand while on fastboot. But i can't flash stock rom using mi flash.. i mean after the done notice my phone still stuck and wont reboot. Like the flash doesnt apply to the phone. I wonder what was wrong
Click to expand...
Click to collapse
Unpack ROM image, extract directory, open cmd, run "flash_all_except_storage.bat" (you might want to remove command "fastboot %* oem lock" from the end of bat first), check/show log.

The easiest thing that worked for me in a similar situation is going into stock recovery and factory resetting the device. I had tried pretty much everything before this and my device was still dead for 1 and a half days before i hit upon this idea without any guides and it worked!!
Do this to get into recovery mode:
1. Power off your phone
2. Press power button and volume up button at the same time
3. You will get "No command" Screen with Android robot with exclamation mark
4. Press power button (don't release) then press volume up button..
5. You will enter into recovery...
The phone may just reboot normally the 1st time you try it as it requires some practice to get it right, but keep trying..
Hope this helps

Edwin Hamal said:
I think it is not hard bricked by any means. Try booting into the Quallcomm EDL and try flashing the fastboot rom with MiFlash too. You can setup a virtual environment in which the flash tool can run and the drivers can install properly.
Click to expand...
Click to collapse
1. I tried this method to boot into EDL with no luck. Is there any other way?
C:\Downloads\xiaomi mi a1 root>adb reboot edl
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device '(null)' not found
2. On my win10 32-bit installation I am able to run MiFlash-2017045. It reports the device. I attempted to flash this image:
tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794
It completed and reported "success" however it did so in only 7 seconds, so it must not actually have succeeded. In any case the phone still will not boot.
3. However, I distrust MiFlash 20170425 because it comes from an androidmtk.com site and the processor is Qualcomm, not Mediatek. So I attempted to install MiFlash2017-07-20. However, that program will not install on my win10 32-bit installation. There is a Windows msg saying it cannot be installed, but does not give a reason. I suspect it is a 64-bit program. So, I installed MiFlash2017-7-20 in a win 10 64-bit installation. The program does run, but it does not see the device. I suspect that the adb drivers do not install correctly. I did turn off signature enforcement and the drivers appear to install, but the device manager reports that the drive cannot start.
The tissot images include bourne shell scripts to install, so I installed the adb drivers on my Centos box. Fastboot reports the device, but just as in win10 no other fastboot commands work. So, even though I did try to execute the install_all.sh script, it just hung on the first "fastboot getvar product" command.
So, I do not have a way to flash the stock rom.

_mysiak_ said:
@yuoip
1. You say that "fastboot devices" works, but "fastboot reboot" not. What error do you receive? Could you paste full log?
2. Sometimes drivers in Windows must be installed manually - open device manager, find unknown device, choose from list and find and choose "android fastboot" or "android adb" device depending on the mode you're in. If you have installed fastboot device before, you should be good to go. Otherwise you'll need to download minimal adb package (https://freeandroidroot.com/download-minimal-adb-and-fastboot-all-versions/), or Google development kit (much larger).
3. stock recovery mode is started by pressing "power button + volume up", once "no command" screen appears, press shortly "power button + volume up" to show the menu.
4. please post full log of command "adb devices" as well
Click to expand...
Click to collapse
1. All fastboot commands, other than "fastboot devices" just hang on "<waiting for device>" with no error message in the linux environment. In the win10 environment they timeout after a few seconds with a message like this:
C:\Downloads\xiaomi mi a1 root\tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794\tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794\tissot_images_7.8.23_7.1>fastboot oem device-info
...
FAILED (command write failed (Unknown error))
finished. total time: 7.000s
2. I had already installed adb-setup-1.43.exe, but I ran it again anyway. Same result.
3. The device will not boot into recovery mode. Pressing power and volume up brings it the "no command" screen with the supine robot image.
4. C:\Downloads\xiaomi mi a1 root>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
No other output.

dhewaghost said:
Hola guys. I got mostly the same issue here. While I still can use adb comand while on fastboot. But i can't flash stock rom using mi flash.. i mean after the done notice my phone still stuck and wont reboot. Like the flash doesnt apply to the phone. I wonder what was wrong
Click to expand...
Click to collapse
Use fastboot commands manually. Mi flash tool is very buggy. Many time it doesn't work.

_mysiak_ said:
Unpack ROM image, extract directory, open cmd, run "flash_all_except_storage.bat" (you might want to remove command "fastboot %* oem lock" from the end of bat first), check/show log.
Click to expand...
Click to collapse
Did the command:
C:\Downloads\xiaomi mi a1 root\tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794\tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794\tissot_images_7.8.23_7.1>fastboot getvar product 2>&1 | findstr /r /c:"^product: *tissot" ||
"Missmatching image and device"
So this is a little interesting. However, I don't think that the image is actually the wrong one, but that the script cannot get the device info since both "fastboot getvar product" and "fastboot oem device-info" fail on a timeout.

zazzy24 said:
The easiest thing that worked for me in a similar situation is going into stock recovery and factory resetting the device. I had tried pretty much everything before this and my device was still dead for 1 and a half days before i hit upon this idea without any guides and it worked!!
Do this to get into recovery mode:
1. Power off your phone
2. Press power button and volume up button at the same time
3. You will get "No command" Screen with Android robot with exclamation mark
4. Press power button (don't release) then press volume up button..
5. You will enter into recovery...
The phone may just reboot normally the 1st time you try it as it requires some practice to get it right, but keep trying..
Hope this helps
Click to expand...
Click to collapse
When I do that it just keeps going back to the "no command" screen. I think the recovery image is either damaged or gone.

yuoip said:
1. All fastboot commands, other than "fastboot devices" just hang on "<waiting for device>" with no error message in the linux environment. In the win10 environment they timeout after a few seconds with a message like this:
C:\Downloads\xiaomi mi a1 root\tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794\tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794\tissot_images_7.8.23_7.1>fastboot oem device-info
...
FAILED (command write failed (Unknown error))
finished. total time: 7.000s
2. I had already installed adb-setup-1.43.exe, but I ran it again anyway. Same result.
3. The device will not boot into recovery mode. Pressing power and volume up brings it the "no command" screen with the supine robot image.
4. C:\Downloads\xiaomi mi a1 root>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
No other output.
Click to expand...
Click to collapse
1. & 2. It sounds like you don't have installed fastboot drivers (install them manually via device manager) or phone isn't connected in fastboot mode (make sure there is a picture with fastboot written on the phone).
3. this IS the recovery mode, just press power + volume up again to show the menu
4. you won't see ADB devices in fastboot or recovery mode, unless you enable ADB sideload from recovery

Device Manager shows:
Android Phone

yuoip said:
Device Manager shows:
Android Phone
Click to expand...
Click to collapse
Wrong drivers then, it should say Android bootloader interface. Reinstall them correctly.

1. I did the manual install, but I don't see anything labeled "fastboot driver."
Device manager now reports:
Android Phone
Android ADB Interface
Android Bootloader Interface
Android Bootloader Interface
Android Composite ADB Interface
However, all these entries have a warning symbol on them. The Device status for each is:
This device cannot start. (Code 10)
The specified request is not a valid operation for the target device.
Is one of these the fastboot driver? Apparently not, since the behavior of the fastboot command hasn't changed.
When I try using the fastboot command the A1 shows "Fastboot" with the rabbit character and the sick robot.
I should mention that in the Centos environment I have installed the android-tools package, which include adb and fastboot drivers and tools. The behavior of the fastboot command there is the same.
So, this leads me to believe that the problem is the A1, not the windows or linux environment, but I don't know enough to know for sure. Also, I would assume that if the fastboot drivers were not installed, the command "fastboot devices" would fail, but it doesn't.
3. At the "no command screen" if I do press and hold the power button and then the vol. up button it boots right back into the "no command" screen. There is no menu.
4. With no recovery menu I can't set any options.

Uninstall/remove everything with android name in it, disconnect phone, reconnect phone in fastboot mode. Make sure that there is only one item under Android Phone - Android Bootloader Interface. You should not see 4 devices - do you have Android emulator running or anything else connected?
When in recovery, do not hold power + volume up, just press it briefly. Sometimes it takes few tries to show the menu, but I can assure you that it's there.

Yes! You're right. The recovery menu is indeed there. I didn't know that it had to be a short press to bring it up. Thanks.
Device manager now shows only one "Android Bootloader Interface" entry. I am not running any emulator.
So now what do I do? Do I need to flash the tissot... image? The fastboot command still behaves as before.

Quick Google search suggests to avoid using USB 3.0 ports. So..maybe try another ports on your PC..?

Nvidia Shield 2019 Pro Developer images 8.1.0

It's seems like Nvidia released the developers image for the shield 2019 pro. There is no description at links only some dots see images.
Shield Android TV SW Version: 8.1.0 (32.7.301.32)
Android Paches: 5 oct 2019
https://developer.nvidia.com/search/site/Shield 2019
NVIDIA SHIELD ANDROID TV 2019 Pro Developer Only OS Image
https://developer.nvidia.com/nvidia-shield-android-tv-pro-developer-only-os-image
Filename: nv-recovery-image-shield-atv-pro-2019-8.1.0-dev-rooted.zip
NVIDIA SHIELD ANDROID TV 2019 Pro Recovery OS Image
https://developer.nvidia.com/nvidia-shield-android-tv-pro-recovery-os-image
Filename: nv-recovery-image-shield-atv-pro-2019-8.1.0.zip
I have downloaded them let see what happens, i'm not responsible if you brick your device.
Both recovery images are working on the Shield 2019 PRO and I was able to fully flash my shield and got things running again.
Image files contains a flash-all file and all the images to recover you device
fastboot oem unlock
:: Confirm the prompt on the screen
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash dtb mdarcy.dtb.img
fastboot flash vbmeta vbmeta.img
fastboot oem lock
:: Confirm the prompt on the screen
The developer version contains 1 extra file called vbmeta_skipped.img.
NOTE: After unlocking your bootloader you will lose Dolby Vision, after locking you bootloader you will get back Dolby Vision

See also https://forum.xda-developers.com/showpost.php?p=81200005&postcount=380
Below are the steps we used to root our Nvidia Shield 2019 PRO, if you are new to rooting devices you better can wait until their are less steps.
For some reason this post doesn't show correctly in the XDA app.
UPDATE: it's possible to use the official release of Magisk.
PreRequisites:
Download: Experimental TWRP is from https://forum.xda-developers.com/showpost.php?p=80769929&postcount=312
Download: Magisk official release https://github.com/topjohnwu/Magisk/releases/tag/v20.4
Download: Filename: nv-recovery-image-shield-atv-pro-2019-8.1.0-dev-rooted.zip (see above post)
Download: Filename: nv-recovery-image-shield-atv-pro-2019-8.1.0.zip (see above post)
Working ADB/Fastboot.
Coffee and a bit of luck.
Enable Developers options/Enable USB Debugging/Authorize device.
Step 1
Reboot to bootloader to start fresh...(you will need a keyboard)
Use files from filename: nv-recovery-image-shield-atv-pro-2019-8.1.0.zip
Use vbmeta_skipped.img from filename:
nv-recovery-image-shield-atv-pro-2019-8.1.0-dev-rooted.zip
a) fastboot oem unlock and confirm by pressing A
b) fastboot flash staging blob
c) fastboot flash boot boot.img
d) fastboot flash recovery recovery.img
e) fastboot flash system system.img
f) fastboot flash vendor vendor.img
g) fastboot flash dtb mdarcy.dtb.img
h) fastboot flash vbmeta vbmeta_skip.img
I) fastboot -w
j) fastboot reboot bootloader
Step 2
Now we will boot to twrp and install magisk...
a) fastboot boot twrp.img (you will need a mouse for this)
b) select mount and mount everything it lets you (usually data, system_root, vendor, cache)
c) adb remount all
d) adb shell
e) rm /system (removes symlinked folder)
f) mkdir /system
g) mount -o bind /system_root/system /system
h) exit
i) adb push Magisk-v20.4.zip /data/media
j) In twrp press install and navigate to magisk zip and flash it
k) adb reboot bootloader
l) fastboot -w
m) fastboot reboot bootloader
n) fastboot flash dtb mdarcy.dtb.img
o) fastboot flash vbmeta vbmeta_skip.img
p) fastboot reboot
q) let it reboot a couple of times, after Nvidia blinks and then reboots).
Optional
r) If Shield doesn't go passed the Nvidia logo.
s) start shield with A+B pressed to get in fastboot
t) in fastboot menu select reset factory default.
u) fastboot flash dtb mdarcy.dtb.img
v) fastboot flash vbmeta vbmeta_skip.img
w) fastboot reboot
x) let it reboot a couple of time
Step 3
Device eventually loads.. when it does follow these steps
a) Enable usb debugging
b) make sure its authorized and connected
c) adb install -g magisk.apk
d) adb shell
e) su (grant root to shell when it pops up)
f) mount -o rw,remount /
g) Go to apps (trough settings), show all apps, start/open magisk manager
h) When it pops up telling you it needs to install stuff select ok and install it.. device will reboot in 5 seconds...
Step 4
When device tries to boot you should now be stuck at the android boot ani (NOT the nvidia logo).. then follow these steps..
a) adb shell
b) su
c) resetprop ro.boot.verifiedbootstate orange
d) after device boots run: resetprop ro.boot.verifiedbootstate green
Step 5
If you have registerd for the hotfix (32.7.301.43) then you can start the upgrade now. The device will reboot and starts the upgrade, after that you lost root again.
a) adb reboot bootloader
b) fastboot boot twrp.img (you will need a mouse for this)
c) select mount and mount everything it lets you (usually data, system_root, vendor, cache)
d) adb remount all
e) adb shell
f) rm /system (removes symlinked folder)
g) mkdir /system
h) mount -o bind /system_root/system /system
i) exit
j) adb push Magisk-v20.4.zip /data/media
k) In twrp press install and navigate to magisk zip and flash it
l) adb reboot bootloader
m) fastboot flash dtb mdarcy.dtb.img
n) fastboot flash vbmeta vbmeta_skip.img
o) fastboot reboot
p) When device tries to boot you should now be stuck at the android boot ani (NOT the nvidia logo).. then follow these steps..
q) adb shell
r) su
s) resetprop ro.boot.verifiedbootstate orange
t) after device boots run: resetprop ro.boot.verifiedbootstate green
After every reboot
When device tries to boot you should now be stuck at the android boot ani (NOT the nvidia logo).. then follow these steps..
a) adb shell
b) su
c) resetprop ro.boot.verifiedbootstate orange
d) after device boots run: resetprop ro.boot.verifiedbootstate green
Stuck at Nvidia Logo
a) Power off Shield, remove power cable
b) Press & Hold A+B on keyboard or controller.
c) Plugin power cable will holding keys.
d) You will see the fastboot menu.
Restore Stock
Use files from Filename: nv-recovery-image-shield-atv-pro-2019-8.1.0.zip
a) Power off Shield, remove power cable
b) Press & Hold A+B on keyboard or controller.
c) Plugin power cable will holding keys.
d) You will see the fastboot menu.
e) fastboot flash staging blob
f) fastboot flash boot boot.img
g) fastboot flash recovery recovery.img
h) fastboot flash system system.img
i) fastboot flash vendor vendor.img
j) fastboot flash dtb mdarcy.dtb.img
k) fastboot flash vbmeta vbmeta.img
l) fastboot -w
m) fastboot reboot bootloader
n) fastboot oem lock and confirm by pressing A
Like I mentioned before, only use this when you know what your are doing. I'm not responsible for any brick devices.
All the credits are for @elliwigy and @rootfan

reserved

Hello and thank you for sharing this.
I'm looking for the fastboot drivers (the 2017 don't works with the pro 2019), I have contacted Nvidia by chat and he doesn't found too.
Can you please tell me where I can download them ?
And sorry for my poor english I'm french.
EDIT :
Ok I have resolved the problem, I have manually installed the .inf.
Regards.

After every reboot
When device tries to boot you should now be stuck at the android boot ani (NOT the nvidia logo).. then follow these steps..
a) adb shell
b) su
c) resetprop ro.boot.verifiedbootstate orange
d) after device boots run: resetprop ro.boot.verifiedbootstate green
Click to expand...
Click to collapse
I don't understand, does this mean we have to do these steps every time the shield reboot ?

lycaos said:
Hello and thank you for sharing this.
I'm looking for the fastboot drivers (the 2017 don't works with the pro 2019), I have contacted Nvidia by chat and he doesn't found too.
Can you please tell me where I can download them ?
And sorry for my poor english I'm french.
EDIT :
Ok I have resolved the problem, I have manually installed the .inf.
Regards.
Click to expand...
Click to collapse
Hi,lycaoslease tell me how to edit the .inf,thanks a lot!

marokino95 said:
I don't understand, does this mean we have to do these steps every time the shield reboot ?
Click to expand...
Click to collapse
Yes every time you reboot you will have to do this. I have connected a Raspberry to the shield which makes it easier.

song4 said:
Hi,lycaoslease tell me how to edit the .inf,thanks a lot!
Click to expand...
Click to collapse
Hello.
It's not easy for me to explain in english, I have Windows in french. But simply go to "device manager" or something like that, select update fastboot, select choose manually, and select again the option to choose manually the driver. Select the .inf and choose boooader driver (it is really simple but like I've said It's not easy for me to explain in english, just don't select the option to search automatically the driver in folder/sub folders, select the other option).
Ok so, I have a big problem when I boot twrp.img : My mouses are not recognized (I have tried 4 wired mouses and bought one very basic old mouse. All the mouses are detected in normal or fastboot mode but 0 device are detected except the computer (I can send adb commands in twrp mode, it's all I can do).
I have also tried a lot of wired controller...
If someone have a solution to use twrp...
(All that things just for modify the Vendor_045e_Product_028e.kl to change A to B and Y to X to use my switch controller pro connected to the 8bitdo recognized as xbox 360 controller >< because natively the switch have pads issues and button mapper have a big latence and don't works in nvidia gamestream !!).
Have a good week-end guys, french kisses :silly:

lycaos said:
Hello.
It's not easy for me to explain in english, I have Windows in french. But simply go to "device manager" or something like that, select update fastboot, select choose manually, and select again the option to choose manually the driver. Select the .inf and choose boooader driver (it is really simple but like I've said It's not easy for me to explain in english, just don't select the option to search automatically the driver in folder/sub folders, select the other option).
Ok so, I have a big problem when I boot twrp.img : My mouses are not recognized (I have tried 4 wired mouses and bought one very basic old mouse. All the mouses are detected in normal or fastboot mode but 0 device are detected except the computer (I can send adb commands in twrp mode, it's all I can do).
I have also tried a lot of wired controller...
If someone have a solution to use twrp...
(All that things just for modify the Vendor_045e_Product_028e.kl to change A to B and Y to X to use my switch controller pro connected to the 8bitdo recognized as xbox 360 controller >< because natively the switch have pads issues and button mapper have a big latence and don't works in nvidia gamestream !!).
Have a good week-end guys, french kisses :silly:
Click to expand...
Click to collapse
Dear lycaos,Thank you for your kindness to help me.Wish you have a good weekend.

Thanks

hi, I am trying to root my Shield 2019 Pro. However I am stuck at installing Fastboot drivers for Windows 10. I only found the Windows drivers for older Shield models. And they don't work. How can I make these work? Thanks a lot!

Well, some of you know this because you have successfully rooted the Shield Pro 2019.
How do I install Fastboot drivers on Windows 10?

thanks for absolutely no help.

Rey3000 said:
thanks for absolutely no help.
Click to expand...
Click to collapse
That's a interesting reply, I also have a busy job and a family. And the same goes for other people on xda.
I'm using Linux and I don't have a problem with the drivers. But you can use the drivers on the Nvidia site.
https://developer.nvidia.com/gameworksdownload#?search=SHIELD Family Windows USB
If that doesn't work you could maybe try
https://xdaflash.com/download-universal-adb-driver-installer-windows

Rey3000 said:
thanks for absolutely no help.
Click to expand...
Click to collapse
Maybe read all post next time ? Lycaos had the same problem you have and he explained how he resolved it on the first page, i had it too and resolved it by following what he said.

powercommy said:
Below are the steps we used to root our Nvidia Shield 2019 PRO, if you are new to rooting devices you better can wait until their are less steps.
Click to expand...
Click to collapse
While I'm generally familiar with Android, I'm new to rooting devices. Where is the best place to keep tabs on progress? Also, out of curiosity, how long does it usually take "until there are fewer steps"?

Exosq said:
Maybe read all post next time ? Lycaos had the same problem you have and he explained how he resolved it on the first page, i had it too and resolved it by following what he said.
Click to expand...
Click to collapse
Of course I tried. Doesn't work. Windows 10. Tried all USB ports. Hence my plea. - how dare I ask for help??
---------- Post added at 08:12 PM ---------- Previous post was at 08:10 PM ----------
besides ... he didn't mention what drivers he used. I OBVIOUSLY tried the latest ones from Nvidia - 2018. They do NOT work ffs.

Rey3000 said:
Of course I tried. Doesn't work. Windows 10. Tried all USB ports. Hence my plea. - how dare I ask for help??
---------- Post added at 08:12 PM ---------- Previous post was at 08:10 PM ----------
besides ... he didn't mention what drivers he used. I OBVIOUSLY tried the latest ones from Nvidia - 2018. They do NOT work ffs.
Click to expand...
Click to collapse
Maybe you should try a different approach with users of XDA and tone down your attitude a little bit. I have no interest in helping you out this way. Maybe other xda-ers will.

powercommy said:
Maybe you should try a different approach with users of XDA and tone down your attitude a little bit. I have no interest in helping you out this way. Maybe other xda-ers will.
Click to expand...
Click to collapse
In case you haven't noticed ... you DIDN'T help me.

mgmcd said:
While I'm generally familiar with Android, I'm new to rooting devices. Where is the best place to keep tabs on progress? Also, out of curiosity, how long does it usually take "until there are fewer steps"?
Click to expand...
Click to collapse
It really depends on how many users are using their Nvidia 2019 Pro before things gets easier. Their is not much differents between rooting your phone/tablet. As long as you follow the the steps you should be okay. It's very difficult to brick your device.
You could also monitor this thread @elliwigy is a user to watch.
https://forum.xda-developers.com/sh...-twrp-shield-android-tv-t3510456/post81811131

HTC U Ultra stuck in bootloop..Can you experts validate the STEPS to solve the issue?

So, my HTC U Ultra got stuck in bootloop just 3 days after warranty ended(tough luck level : 100).
My phone runs on everything stock and no root.
I press all the buttons when powered off and it goes into bootloader mode. It displays options to boot into recovery mode, boot into download mode and power down, all of which(except power down) gets device into bootloop again.
THE PRIORITY OF GOALS IS : DATA RECOVERY > PHONE BOOTING AND WORKING PROPERLY AGAIN
I did a little research and figured out some sort of procedure by putting bits and pieces together :
1. Download ADB/Fastboot toolkit || universal driver from koush github // I have HTC Sync manager installed as well || twrp custom recovery image for htc u ultra || new ruu from htc support for rom update.
2. Now I put my phone into fastboot mode (since it doesn't show up on adb devices), connect to pc using usb.
3. I type in cmd : "fastboot devices" --> My device shows up there --> Again in cmd : "fastboot boot recovery mytwrp.img" --> the twrp boots into my phone
I was able to put this many steps together and after the last step, i have an abstract idea of what to do :
Enable USB Debugging using twrp recovery --> Use ADB Pull Command to get my all my data from phone to pc --> Use adb wipe the old Firmware (Not sure which command) --> Use adb again to flash new RUU (again not sure how, I've got an .exe file as RUU || should I get it in zip or img or any other format ? || Please help on this too) --> Finally Boot and hopefully everything turns out smooth and secure.
CAN YOU EXPERTS HELP ME TO PUT TOGETHER REMAINING STEPS (AND MODIFY ERRORS, IF ANY, OF EXISTING STEPS ) OF THIS PROCEDURE...???

Only to clarify: ADB and Fastboot are 2 completely different things.
ADB
is a protocol that allows you to communicate with an Android device that got booted, means its main Android OS is running
At Windows command prompt you enter commands - one by one -
Code:
adb devices
adb <ANY_SUPPORTED_ADB_SUBCOMMAND>
FASTBOOT
is a program used to manipulate (list, install, erase) the non-volatile memory such as flash filesystem partitions on devices that adhere to the fastboot protocol, via a USB connection from a host computer. It requires that the device be started in a boot loader mode with the fastboot protocol enabled.
IMPORTANT: Fastboot will only work if the OEM/Carrier has included support for the Fastboot protocol.
At Windows command prompt you enter commands - one by one -
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot <ANY_SUPPORTED_FASTBOOT_SUBCOMMAND>

jwoegerbauer said:
Only to clarify: ADB and Fastboot are 2 completely different things.
ADB
is a protocol that allows you to communicate with an Android device that got booted, means its main Android OS is running
At Windows command prompt you enter commands - one by one -
Code:
adb devices
adb <ANY_SUPPORTED_ADB_SUBCOMMAND>
FASTBOOT
is a program used to manipulate (list, install, erase) the non-volatile memory such as flash filesystem partitions on devices that adhere to the fastboot protocol, via a USB connection from a host computer. It requires that the device be started in a boot loader mode with the fastboot protocol enabled.
IMPORTANT: Fastboot will only work if the OEM/Carrier has included support for the Fastboot protocol.
At Windows command prompt you enter commands - one by one -
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot <ANY_SUPPORTED_FASTBOOT_SUBCOMMAND>
Click to expand...
Click to collapse
@jwoegerbauer Yes, thank you for the description, I understood the difference later on. Do you think the fastboot and adb steps I've mentioned will work properly ?

noobie12112 said:
@jwoegerbauer Yes, thank you for the description, I understood the difference later on. Do you think the fastboot and adb steps I've mentioned will work properly in my case?
Click to expand...
Click to collapse
Android boot loop error does not come out of thin air. There are several cases that may cause the Android is starting loop. If phone didn't get physically damaged then an action of the user is the main reason .
To answer your question: NO.
As already said:
ADB is integral part of Android OS hence if Android OS isn't started you can't make use of ADB, Fastboot is integral part of phone's bootloader ( comparable to a Windows PC's UEFI/BIOS ) means you can't access Android OS - will say its folders and files.

jwoegerbauer said:
Android boot loop error does not come out of thin air. There are several cases that may cause the Android is starting loop. If phone didn't get physically damaged then an action of the user is the main reason .
To answer your question: NO.
As already said:
ADB is integral part of Android OS hence if Android OS isn't started you can't make use of ADB, Fastboot is integral part of phone's bootloader ( comparable to a Windows PC's UEFI/BIOS ) means you can't access Android OS - will say its folders and files.
Click to expand...
Click to collapse
@jwoegerbauer Thank you for the insight. In my case, the phone wasn't physically damaged, the bootloop occurred out of the blue one day. Now, what I presumed I should do, is to flash a custom recovery (twrp) using "fastboot boot recovery.img" command, and using twrp (Can I enable USB Debugging using twrp ?) to access files, backup and then flash a new RUU. But I found that I need to unlock bootloader, is there any way to use command "fastboot oem unlock" and not lose data, or any other method to unlock bootloader, where i don't lose data?
Thank you for your help.

Unlocking phone's bootloader always causes complete loss of data.
Forget the TWRP thing, it's not helpful at all in your case.
Try to flash phone's Stock ROM by means of ADB - what requires ADB got installed on Windows computer and USB debugging got ( manually !!! ) enabled on phone.