Hello all
Please is it possible to install stock ROM or stock OTA update without ADB commands?
Some other way for install?
Because my watch blocking ADB authorization!!!
Simply not show confirmation ADB dialog window
I tryed everything around ADB and nothing
I´m on stock recovery for info...
Thank you very much for help :good:
Have a nice day for all
Somebody help me?
Thank you very much
https://forum.xda-developers.com/zenwatch-3/how-to/guide-how-to-revert-to-android-wear-1-5-t3635196
No adb commands required. To enter fastboot press and hold Upper button+ Center button on turned off watch.
Here you can find more useful info https://forum.xda-developers.com/zenwatch-3/how-to/guide-reboot-recovery-fastboot-unlock-t3546743
djdarkrider said:
https://forum.xda-developers.com/zenwatch-3/how-to/guide-how-to-revert-to-android-wear-1-5-t3635196
No adb commands required. To enter fastboot press and hold Upper button+ Center button on turned off watch.
Here you can find more useful info https://forum.xda-developers.com/zenwatch-3/how-to/guide-reboot-recovery-fastboot-unlock-t3546743
Click to expand...
Click to collapse
Thank you for reply but in both links are adb commands...
those are fastboot commands. You don't need adb popup on watch to use them.
djdarkrider said:
those are fastboot commands. You don't need adb popup on watch to use them.
Click to expand...
Click to collapse
I can't use adb commands because my device is unauthorized for adb commands
I can't authorize my watch because not showing pop up window for allow adb.
Note: all my other Android devices works fine for adb commands and authorization...
This mean that problem is in the watch...
Hoffmanns said:
I can't use adb commands because my device is unauthorized for adb commands
I can't authorize my watch because not showing pop up window for allow adb.
Note: all my other Android devices works fine for adb commands and authorization...
This mean that problem is in the watch...
Click to expand...
Click to collapse
I get it.
Those commands are typed in adb command line, when your watch are in FASTBOOT mode. There will be no authorization for fastboot mode. Turn your watch off, then press and hold power+upper buttons, until you are in fastboot mode(it will be written on watch screen). Then connect watch to pc and type "fastboot devices" in adb window.
Just try it. NO AUTHORIZATION REQUIRED
djdarkrider said:
I get it.
Those commands are typed in adb command line, when your watch are in FASTBOOT mode. There will be no authorization for fastboot mode. Turn your watch off, then press and hold power+upper buttons, until you are in fastboot mode(it will be written on watch screen). Then connect watch to pc and type "fastboot devices" in adb window.
Just try it. NO AUTHORIZATION REQUIRED
Click to expand...
Click to collapse
God bless you :laugh::good:
It's working :laugh:
I tryed many many things but not this
Thank you very much for your help and time :good::good::good:
Related
Ok, now we know that fastboot and adb can be troublesome on WIndows, but despite lots of reading, I;m a bit stumped as to what if anything is wrong with my WIN 7 setup.
ADB works fine, I can get into adb from a cmd window, enter commands and get the expected result.
"adb devices" returns the 16 digit serial number, a few spaces and "device"
"adb reboot" reboots as normal
I cannot get into fastboot from adb though. (I can use a factory cable to enter fastboot, no problem, and using the Quick Boot app, I can get into Fastboot no probs.
Once there,
"fastboot -i 0x1949 getvar product" returns -> product: Tate-PVT-08
"fastboot -i 0x1949 devices" returns -> 13EE000200000001 fastboot
"fastboot -i 0x1949 reboot" gets me out into normal mode.
All above leads me (correctly or not) to think that the drivers, system etc are ok and I'm doing something wrong.
eg
" adb reboot-bootloader" (as written in adb help) simply reboots the device as usual
as does
"adb reboot bootloader"
"adb reboot boot loader"
I've seen the various syntax here and elsewhere
It seems as if the command is read as far as "reboot" and everything after that is ignored. So, what am I doing wrong?
You're doing nothing wrong. I believe that command does not work in the later os versions.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Red_81 said:
You're doing nothing wrong. I believe that command does not work in the later os versions.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Oh bum. You know, I thought maybe the drivers were wrong, or my syntax wrong, but I never thought the OS would be wrong!! Lol
Does anyone know when this change was introduced and which was the last OS release that could be booted into fastboot via adb?
If you're rooted you could try the methods in the FAQ post. Otherwise, buy/build a fastboot cable. It makes everything much easier.
Q17: How can I access fastboot mode on 2nd generation Kindle Fires?
There are 3 methods currently used for accessing fastboot mode on the 2nd generation Kindle Fires. Depending on the model, one or more of these methods may not work.
For all devices, entering “reboot bootloader” in the shell as the root user should reboot the device into fastboot mode.
On HD models, entering a fastboot command that waits for a handshake from the device (i.e. <waiting for device>”) such as “fastboot -i 0x1949 getvar product” and rebooting the device will usually enable fastboot mode when the device reboots.
On the KFHD7 and KF2, a factory cable can be used to access fastboot mode by plugging it into the device after it has been powered down.
Thanks Red. The shell command works, but issuing a command that waits for a handshake then rebooting doesn't. I also tried the same command whilst the device was powered down, but in both cases it just booted normally.
Of course my factory cable also works, and I am rooted
Code:
adb shell su -c reboot-bootloader
SafinWasi said:
Code:
adb shell su -c reboot-bootloader
Click to expand...
Click to collapse
thanks safinwasi. I managed ok without needing this option, It was more for reassurance. For the benefit of anyone who might need to do this, I have seen that command without quotes, so try both.
I think you should get a fastboot cable less hassle!
Bao289 said:
I think you should get a fastboot cable less hassle!
Click to expand...
Click to collapse
Hmmm, I think you should read posts properly before making comments.
cecr said:
I can use a factory cable to enter fastboot, no problem, and using the Quick Boot app, I can get into Fastboot no probs.
Click to expand...
Click to collapse
I've had my factory cable since I rooted my first Kindle about 15 months ago.
Hey Guys any1 knows the fastboot commands for booting Device into recovery Mode and checking connected Devices?
Help would be nice, need to know
Thx Advanced
Function: Check connection and get basic information about devices connected to the computer.
"adb devices"
"fastboot devices" - This is essentially the same command as adb devices above. However, it works in the bootloader, which ADB does not.
Function: Reboot your phone into recovery mode.
"adb reboot recovery"
Obviously without the speech marks.
man, i am losing my mind over this now. i have no idea why my phone seems like it isn't recognized in adb fastboot. however, when i am not in fastboot it shows just fine.
before i go into fastboot mode on the phone i can use command prompt and it shows
>adb devices
List of devices attached
d858f4c6 device
i can even command the phone to go into fastboot
adb reboot bootloader - and my phone goes into fastboot
then when in fastboot:
i type fastboot devices - nothing listed
adb devices - nothing listed
what am i doing wrong here? everything seems to be fine before going into fastboot but once i am in fastboot none of the same commands work the device isn't recognized
yes, of course i have usb debugging turned on.
any ideas? i've been messing with this going on two hours now uninstalling my files and reinstalling them.
EDIT - ok it took me like 3 hours but the device needs different drivers when in fastboot but you can only fix it while its in fastboot on my machine for some reason
You can't use adb commands when in fastboot mode and vice versa.
knives of ice said:
man, i am losing my mind over this now. i have no idea why my phone seems like it isn't recognized in adb fastboot. however, when i am not in fastboot it shows just fine.
before i go into fastboot mode on the phone i can use command prompt and it shows
>adb devices
List of devices attached
d858f4c6 device
i can even command the phone to go into fastboot
adb reboot bootloader - and my phone goes into fastboot
then when in fastboot:
i type fastboot devices - nothing listed
adb devices - nothing listed
what am i doing wrong here? everything seems to be fine before going into fastboot but once i am in fastboot none of the same commands work the device isn't recognized
yes, of course i have usb debugging turned on.
any ideas? i've been messing with this going on two hours now uninstalling my files and reinstalling them.
EDIT - ok it took me like 3 hours but the device needs different drivers when in fastboot but you can only fix it while its in fastboot on my machine for some reason
Click to expand...
Click to collapse
I have same problems. Please explain how you have solved. Which drivers the Mi Mix needs in fast boot mode?
basically, you have to watch your device manager for the ANDROID to pop up and it should have a yellow exclamation. you have to fix the drivers, but the problem is at least in my case you have to complete and fix the drivers before the mix puts itselt out of fastboot and into charging (which it does quite quickly when not connected)
install this:
http://forum.xda-developers.com/showthread.php?t=2588979
and follow the guide that he posts in the pictures on what you need to change
here
http://forum.xda-developers.com/attachment.php?attachmentid=2480396&d=1388281089
as soon as you have the drivers fixed windows will tell you and the mix will stay connected
Someone please.help...
tott2003 said:
Someone please.help...
Click to expand...
Click to collapse
1. Connect the USB cable from the side of the phone and make sure that developer mode and USB debugging is activated.
2. Connect your phone to the PC, make sure it's connected in data transfer mode.
3. Go to adb.exe and fastboot.exe folder, hold shift and right click to open CMD or PowerShell from there. If you open PowerShell use .\ before the command, if you are using CMD just type the command without it.
4. Type in CMD: "adb devices" without parenthesis, you should see your device serial number.
5. Type then in CMD: "adb reboot bootloader" without parenthesis, you will go to fastboot mode or the "Green Start Screen" after the phone boots.
6. Type "fastboot devices" you should see you device serial number. which means you can run fastboot commands without any issues.
P.S I am using PowerShell instead of CMD, so the pictures show the commands with .\ in the beginning.
Rashad83 said:
1. Connect the USB cable from the side of the phone and make sure that developer mode and USB debugging is activated.
2. Connect your phone to the PC, make sure it's connected in data transfer mode.
3. Go to adb.exe and fastboot.exe folder, hold shift and right click to open CMD or PowerShell from there. If you open PowerShell use . before the command, if you are using CMD just type the command without it.
4. Type in CMD: "adb devices" without parenthesis, you should see your device serial number.
5. Type then in CMD: "adb reboot bootloader" without parenthesis, you will go to fastboot mode or the "Green Start Screen" after the phone boots.
6. Type "fastboot devices" you should see you device serial number. which means you can run fastboot commands without any issues.
P.S I am using PowerShell instead of CMD, so the pictures show the commands with . in the beginning.
Click to expand...
Click to collapse
Cheers mate ?
Rashad83 said:
1. Connect the USB cable from the side of the phone and make sure that developer mode and USB debugging is activated.
2. Connect your phone to the PC, make sure it's connected in data transfer mode.
3. Go to adb.exe and fastboot.exe folder, hold shift and right click to open CMD or PowerShell from there. If you open PowerShell use .\ before the command, if you are using CMD just type the command without it.
4. Type in CMD: "adb devices" without parenthesis, you should see your device serial number.
5. Type then in CMD: "adb reboot bootloader" without parenthesis, you will go to fastboot mode or the "Green Start Screen" after the phone boots.
6. Type "fastboot devices" you should see you device serial number. which means you can run fastboot commands without any issues.
P.S I am using PowerShell instead of CMD, so the pictures show the commands with .\ in the beginning.
Click to expand...
Click to collapse
HOLY. ****ING. ****.
I have spent the past two days trying to figure this out. Not *one* other person on the internet, so much as I have seen, has mentioned using the side port. Seriously, you just made my day. Thank you so much! :good:
Created a new topic, disregard
A lot of work was done with the Chinese Zte A2121 but it worked
[email protected] said:
Zte Axon 20 CN version Working Google Play & multilanuage I was able to modify it.
Click to expand...
Click to collapse
Photo
I want multilenguage rom (spanish), how do you make multilenguage?? Morelocale2 or any other app??
MoreLocale 2 you connect the phone in debug mode you use the command console with adb & fastboot. You enter adb devices, confirm on the phone screen adb connection, in response you will get a number and the text device, enter the adb shell command and confirm with enter, then enter the command
pm grant jp.co.c_lis.ccl.morelocale android.permission.CHANGE_CONFIGURATION and confirm. From now on, you can choose any language in MoreLocale2, including the entire telephone interface, including settings. You also have to do this every time Axon is restarted but it works
[email protected] said:
MoreLocale 2 you connect the phone in debug mode you use the command console with adb & fastboot. You enter adb devices, confirm on the phone screen adb connection, in response you will get a number and the text device, enter the adb shell command and confirm with enter, then enter the command
pm grant jp.co.c_lis.ccl.morelocale android.permission.CHANGE_CONFIGURATION and confirm. From now on, you can choose any language in MoreLocale2, including the entire telephone interface, including settings. You also have to do this every time Axon is restarted but it works
Click to expand...
Click to collapse
that's the way I´ll do.. thnx!!