Hello, I have an Amazfit Stratos (details attached as a screenshot from AmazMod app) and I have a problem entering fastboot (I want to unlock the bootloader and start having fun with the watch )
What I've already tried:
- standard ADB mode, the watch is recognized and seen in ADB, but when I enter adb shell reboot fastboot - it just reboots back to the usual OS...
- the All In One Tool available on XDA - the same issue - watch is recognized but when I click reboot to fastboot - it just boots up normally...
- manual method described on the forum and shown on youtube - the issue is, when the screen goes dark I'm supposed to wait 4 seconds before releasing the power key - and my watch shows up the Amazfit logo after 2 seconds - the whole bootup process is different than on the video - I've been at it for 2 hours and did not manage to get it to fastboot once
- I've also tried using the AmazMod app - there's a section there that allows you to send direct commands to the watch shell - I've tried reboot fastboot and the watch also reboots back to the standard OS
- I tried the method with adb kill-server / adb start-server / adb wait-for-device and then rebooting the watch (method found on the forum as well) - no cigar.
I'm getting desperate - I wanted the stratos mostly because of the awesome job devs do making it better - now I'm left with the stock watch and to be honest I think Huawei Watch GT would be better for my needs if I'm comparing stock vs stock...
Did anyone have any similar issues?
Anyone? Getting desperate and still no solution in sight...
AmazMod widget also has a "Reboot to fastboot" option, but it is the same as the adb command, I think you are using the wrong command, the correct one is:
Code:
adb shell reboot bootloader
and not "reboot fastboot". Manually always works too, if watch turns on (you can see Amazfit logo) and button isn't broken.
Yeah I've tried both reboot fastboot and reboot bootloader with the same non result
maslosky said:
Yeah I've tried both reboot fastboot and reboot bootloader with the same non result
Click to expand...
Click to collapse
You must use exactly the same commands as I wrote, "adb reboot bootoloader" does not work.
ADB method just causes the watch to reboot regularly... Nobody is able to help?
If the adb command doesn't work for some weird reason, then the only way is doing it manually. It is very trick, but it works. You may want to flash a stock ROM first, as it is the only explanation why "adb shell reboot bootloader" does not work for you...
I do have a stock rom since I haven't been able to unlock bootloader (because I can't enter fastboot) - manual entry is not working, as I've mentioned my watch is acting differently than the watch presented in the YouTube video... I'm stuck
Did you try to facttory reset yet?
Code:
adb reboot wipe
OK so I finally managed to get the watch to fastboot mode, manual method is still not working, but after a factory reset and TOTAL removal of ALL adb drivers (total wipe of any adb/fastboot drivers from Win10) - it finally worked using the All In One Tool from the forum. This can be closed now. Thanks for all the suggestions - I'm not sure if the factory wipe helped or the Win10 drivers wipe - but it works I'm on to bigger and better things
maslosky said:
OK so I finally managed to get the watch to fastboot mode, manual method is still not working, but after a factory reset and TOTAL removal of ALL adb drivers (total wipe of any adb/fastboot drivers from Win10) - it finally worked using the All In One Tool from the forum. This can be closed now. Thanks for all the suggestions - I'm not sure if the factory wipe helped or the Win10 drivers wipe - but it works I'm on to bigger and better things
Click to expand...
Click to collapse
Can u elaborate on thr driver's removal?
Related
hi everyone,
I'm coming from this thread http://forum.xda-developers.com/showthread.php?t=1834761
I have been stuck for more than one week now and i didn't find any solution.
My problem is that I'm currently stock in a clockworkmod recovery boot loop on my Asus Transformer Prime without adb/fastboot connection:
1 - I had install CM9 stable on my Transformer Prime, after a wide data and then send throw "adb push" the CM9.zip,
2 - I reboot by CM9 in recovery mod to install Gapps,
3 - I install the Gapps zip,
4 - I ask to clockworkmod to reboot,
5 - Since then I'm in a clockworkmod recovery boot loop without adb/fastboot connection (witch used to be working),
If kown how can I get adb/fastboot connection back to be able to find my device with the adb command " adb devices " and then be able to send this command => " dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1 "
Thank you for your understanding,
Kind regards,
Adb and fastboot are two different things... Fastboot is obtained buring booting process with vol down pressed, then not selecting recovery with volume up. So you should have fastboot access.
In this case I would suggest to fastboot flash TWRP (see on their website for instructions) it will perhaps fix things or at least give you adb access.
If you use cwm take the old 5.8.2.0 modded for not looping with reboot to recovery feature, or stay with twrp.
I would look at the following thread for unbricking the TF201:
http://forum.xda-developers.com/showthread.php?t=1514088
Sounds like you might fall into Option 1a.
I was having your same issue but it was because I rebooted into recovery from the reboot option on the CM10 rom. In any event, I couldn't get adb to work or recognize my device no matter what. I then decided to use my macbook pro. I can tell you that using adb on a mac is much easier as you don't have to download the drivers or sdk, just the platform tools. Here's a link: http://forum.xda-developers.com/showthread.php?t=1387527. I know this may not help if you or someone you know doesn't have a mac, but it saved me.
So I'm in the process of trying to Root my ZTE Smarttab 10 on firmware v03b.
Ive been following instructions on the following pages:
http://forum.xda-developers.com/showthread.php?t=1629630
http://forum.xda-developers.com/showthread.php?t=1473555
The instructions are spread out across those threads and my problem starts kind of early in the process.
My goal is to use ADB to boot in to the Bootloader and then use a recovery rom to use TWRP to install a rom.
What i have done:
I have installed the ZTE Drivers
I have installed the SDK tools and updated it.
Now when the tablet is running normally I can see it in ADB and is able to run the command.
ADB Reboot Bootloader
This reboots the devices to a black screen (I assume this is the bootloader) and windows recognizes that a device is there.
The problem is that when I try to see this from ADB i cannot see the device when running ADB Devices.
This makes the next step impossible as I need to use ADB to boot a recovery rom.
So I would have posted in the development treads listed above but as I dont have 10 posts (this being my first post) I cannot post in the threads above.
I'm confident that this is a driver problem and I have uninstalled and re-installed all the drivers related to this including SDK.
But no luck yet.
Where other people say they have succeeded is when in the device manager they have ADB interface and ZTE Handset ADB interface listed.
This is the state where I'm at but I still cannot see the device in ADB.
Anyone have any insight on this kind of problem and can offer any help for a solution or direction to get to the solution.
Thank you for your help and attention!
//Nagarutu
Vodafone (ZTE) SmartTab10 3.2 HoneyComb
You can't use adb in bootloader mode, you want fastboot. So when you do 'adb reboot bootloader'. It reboots to the black screen (that is the bootloader). Try typing 'fastboot devices' and see if you're device comes up. It should if you have all drivers installed correctly and fastboot on your system. Then you'll be able to do 'fastboot flash recovery recovery.img' to install the custom recovery, then a 'fastboot reboot' and lastly an 'adb reboot recovery' will get you into your custom recovery to flash a new rom. Don't forget to make a backup.
matt4321 said:
You can't use adb in bootloader mode, you want fastboot. So when you do 'adb reboot bootloader'. It reboots to the black screen (that is the bootloader). Try typing 'fastboot devices' and see if you're device comes up. It should if you have all drivers installed correctly and fastboot on your system. Then you'll be able to do 'fastboot flash recovery recovery.img' to install the custom recovery, then a 'fastboot reboot' and lastly an 'adb reboot recovery' will get you into your custom recovery to flash a new rom. Don't forget to make a backup.
Click to expand...
Click to collapse
Thank you for the help ! it cleared things up for me.
Now the trouble's continue.
With the firmware im on (v03b) you cannot use the fastboot flash method but only fastboot.
And they way it is supposed to be done is that you run
fastboot boot recovery.img (recovery being a twrp recovery for my device)
When its booted to TWRP i should be able to see it in ADB to be able to run the following commands to it:
--> adb remount
--> adb shell
--> ln -s /system/xbin/su /system/bin/su
However I cannot get it to show in ADB (or fastboot) when its booted in to TWRP.
Any ideas?
I managed to solve the last bit to.
Now it was actually a driver problem, so i just updated the driver in device manager and located the ADB driver from ZTE and it worked to boot in to TWRP and then to flash the device.
Now I have CM10 installed and is smiling!
Took me 4 days but damn it its done!
Thanks for the help!
Glad you've figured it out
1a
2a
3a
4a
5a
Hi. I have a Amazfit Stratos with stock CN firmware 2.0.34.2 and I can't seem to get it to boot into fastboot mode. Whenever I run "adb shell reboot bootloader" in CMD, the watch just reboots normally. The watch is recognized by my computer in device manager. Just trying to unlock the bootloader. Any ideas what I could try?
Thanks!
vinny13 said:
Hi. I have a Amazfit Stratos with stock CN firmware 2.0.34.2 and I can't seem to get it to boot into fastboot mode. Whenever I run "adb shell reboot bootloader" in CMD, the watch just reboots normally. The watch is recognized by my computer in device manager. Just trying to unlock the bootloader. Any ideas what I could try?
Thanks!
Click to expand...
Click to collapse
How about this? adb shell reboot fastboot
If that doesn't work, then try this. https://forum.xda-developers.com/sm...tches/amazfit-boot-fastboot-directly-t3546829
What does the code below do?
Code:
adb shell
reboot bootloader
You can always use manual mode, as it's explained in Anox link.
Hi guys sorry for the delayed response. Tried both suggested ADB commands and attempted a handful of times to manually enter fastboot mode (according to instructions in link) and in each case it just reboots normally. Is there a debug mode setting that needs to be toggled beforehand or something?
I've also tried using the Huami Amazfit Tool app to reboot it into fastboot mode and it still reboots normally.
vinny13 said:
Hi guys sorry for the delayed response. Tried both suggested ADB commands and attempted a handful of times to manually enter fastboot mode (according to instructions in link) and in each case it just reboots normally. Is there a debug mode setting that needs to be toggled beforehand or something?
I've also tried using the Huami Amazfit Tool app to reboot it into fastboot mode and it still reboots normally.
Click to expand...
Click to collapse
Fastboot mode should always be accessible.
That tool & others basically use the same command to access fastboot mode.
The manual method is supposed to be the last resort. I now have no idea, sorry.
Have you found a solution yet? I have exactly the same problem.
Gavros7 said:
Have you found a solution yet? I have exactly the same problem.
Click to expand...
Click to collapse
If
Code:
adb shell reboot bootloader
does not work for you due to some reason, you can do it manually only: it uses the buttons and need some tries because it's tricky. It is the same process as Pace, search forum or YouTube for more info.
lfom said:
If
Code:
adb shell reboot bootloader
does not work for you due to some reason, you can do it manually only: it uses the buttons and need some tries because it's tricky. It is the same process as Pace, search forum or YouTube for more info.
Click to expand...
Click to collapse
@vinny13 Did you solve your problem?
I have exactly the same problem.
When I try "adb shell reboot bootloader" the answer that appears is "- exec '/ system / bin / sh' failed: Permission denied (13) -
using port = 5555 "
Manually I've tried over 70 times and I don't know what else to do to get into this FastBoot ...
I think I was drawn!
Thanks for any help.
alexsouza said:
@vinny13 Did you solve your problem?
I have exactly the same problem.
When I try "adb shell reboot bootloader" the answer that appears is "- exec '/ system / bin / sh' failed: Permission denied (13) -
using port = 5555 "
Manually I've tried over 70 times and I don't know what else to do to get into this FastBoot ...
I think I was drawn!
Thanks for any help.
Click to expand...
Click to collapse
Using the button trick is the only way you have to enter into fastboot.
Saratoga79 said:
Using the button trick is the only way you have to enter into fastboot.
Click to expand...
Click to collapse
Thanks for your response, @Saratoga79. Has anyone seen any cases that the watch does not enter Fastboot or the button? I say this because the operating system of the clock was always crashing ... Now the only screens that appear to me are "A" and "No Command".
I will keep trying the button method. I confess it has been over 90 times.
After not using my pace for a few months I decided to start wearing it again, but I'm having a problem, I can't install any apps.
In the time I had not been using the Pace, I uninstalled the Amazfit app, so I needed to factory reset the Pace to get it paired again.
After the reset I can no longer install apks. I have tried apk installer and just directly using ADB but both fail.
Whenever I try to install an app, I hear the windows USB disconnect/reconnect sounds and the install fails.
I have tried, rebooting the watch, factory resetting the watch again, rebooting the PC, reinstalling ADB drivers (several times) and so far none of it has helped
Below is the output from ADB. If anyone can tell me how to fix this I'd really appreciated it.
__________________________________________________________
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Minimal-ADB-and-Fastboot>adb devices
List of devices attached
adb server version (40) doesn't match this client (35); killing...
* daemon started successfully *
b3291104 device
C:\Minimal-ADB-and-Fastboot>adb install rl.apk
adb: error: failed to copy 'rl.apk' to '/data/local/tmp/rl.apk': couldn't read f
rom device
- waiting for device -
C:\Minimal-ADB-and-Fastboot>
__________________________________________________________
Just bumping this since I am still having this issue and am hoping someone has some idea how to fix it.
I have managed to install some apps, but most won't work, not sure if it is random or something to do with the apps themselves. However they are all apps that I have used in the past on my Pace so I'm really not sure whats going on.
Whenever I try to install an app ADB seems to disconnect then reconnect and the install fails.
Any help with this would be great.
I recommend you doing a factory reset in fastboot if you already have unlocked bootloader (sync all data before):
Code:
adb shell reboot bootloader
fastboot erase cache
fastboot erase data
fastboot reboot
If your bootloader is locked, just do a reset from the watch settings.
Saratoga79 said:
I recommend you doing a factory reset in fastboot if you already have unlocked bootloader (sync all data before):
Code:
adb shell reboot bootloader
fastboot erase cache
fastboot erase data
fastboot reboot
If your bootloader is locked, just do a reset from the watch settings.
Click to expand...
Click to collapse
I already tired a couple of factory resets but unfortunately it didn't help. I have not unlock or modified the watch so I'm not sure what else I can do.
Is there any kind of official tool to reflash the stock ROM on a locked device?
Hi,
I am new in this topic and not a great geek ans please excuse mi for my aprroximative english ! but i am trying to convert an old cube tablet to a domotic tablet. So i have to flash the old rom to a newer like lineageos for example.
So the tablet is an U30GT C4H with android 4.2.2 and the original rom.
I connect the device to my Mac Os and with adb tools (from plateform tools find here) and terminal i wrote adb devices (tablet on) i see the device. OK
When i command fastboot devices, nothing, no line
When i command adb reboot-bootloader, the tablet take off and the screen keep black. With the terminal fastboot devices, no response, with adb devices command > List of devices attached but no more, no device.
With this tablet it is possible to start in recovery mode with power + audio down but with this option i have the android logo and no command. If i take power on no change.
If with adb command and tablet on, i write adb reboot recovery, the tablet restart and the screen see logo android and no command.
I know this kind of topic do not interese a lot of people but i would like use this cube for my house to command domotic (music, heaters etc..). More, i think it's a shame not to recycle this type of device for the planet !!!
Thanx
Fastboot only works if in your tablet's Android's Settings -> Developer options the option OEM unlock got enabled and tablet got restarted afterwards.
i don't see any option OEM in the menu developer
I found that the solution is use slideload protocol. I reseted the tablet and now i get recovery mode. Then i can connect the tablet to my Mac and use terminal with slideload lines. OK
But each time the process failed with rom i found on the net...
Is there an universal rom !!!
Any idea ?
You don't have to boot the device into Recovery mode:
Code:
adb devices
adb reboot sideload
adb sideload <PROPERLY-SiIGNED-FILE.ZIP>
adb reboot
BTW: adb sideload is meant to re-flash Stock ROMs only.
jwoegerbauer said:
You don't have to boot the device into Recovery mode:
Code:
adb devices
adb reboot sideload
adb sideload <PROPERLY-SiIGNED-FILE.ZIP>
adb reboot
BTW: adb sideload is meant to re-flash Stock ROMs only.
Click to expand...
Click to collapse
maybe the issue is the rom i doawnloaded ?
it is kasty-cube_u30gt_h-411-111-rooted4_4gb.zip
or
kasty-cube_u30gtc4-441-20131212-rooted4.zip
both failed.
Perhaps i have to unlock the bootloader as you said but i don't know
I'm pretty sure the 2 mentioned ROMs are a Custom ROM. Hence you can't use adb sideload method to flash them. To install a Custom ROM it's required that a Custom Recovery already got installed on device's Android.
I don't find any way to instal a recovery. I had arctools.zip but the app failed to acess to the SD disk or internal storage...