I did a great mistake.
I used a commend 'fastboot erase data' and my watch doesn't turn on.
Can I fix my watch?
wltjd0217 said:
I did a great mistake.
I used a commend 'fastboot erase data' and my watch doesn't turn on.
Can I fix my watch?
Click to expand...
Click to collapse
Use Cloner Tool.
Related
My moto z before using RSD lite flash NPL 25.86-30, then OTA updated to NPL25.86-30.3. It seems that bootloarder is also updated. now I want to re-use RSD lite to flash NPL25.86-30. But RSD has shown an error in flashing GPT.bin, show "FAIL"
Who can help me?:crying:
You can't go back, if the Bootloader got updated.
jump the step of flashing gpt by editing the xml file(delete the line)
Now my device have a very strange question, if I use the battery mod, is unable to shutdown, automatically enter the bootloarder. Do not use the module can shutdown, but the connection charger will automatically enter the bootloarder,can not be charged in the shutdown state.
Sorry,my english is bad.
rakee said:
Now my device have a very strange question, if I use the battery mod, is unable to shutdown, automatically enter the bootloarder. Do not use the module can shutdown, but the connection charger will automatically enter the bootloarder,can not be charged in the shutdown state.
Sorry,my english is bad.
Click to expand...
Click to collapse
start fastboot in the cmd and start the following command
fastboot oem fb_mode_clear
this should solve your bootlader at reboot issue...
treibstoff said:
start fastboot in the cmd and start the following command
fastboot oem fb_mode_clear
this should solve your bootlader at reboot issue...
Click to expand...
Click to collapse
Its work for me,thanks man!:highfive::highfive:
treibstoff said:
start fastboot in the cmd and start the following command
fastboot oem fb_mode_clear
this should solve your bootlader at reboot issue...
Click to expand...
Click to collapse
After the last OTA (july) update has failed, I got an issue very similar, but in my case, everytime I restart or turn off the device, it gets to twrp recovery and I need do restart it on fastboot mode then choose START on side menu to get boot properly. Can you help?
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.
Hello,
I have specific problem.
I was on the stock rom 10.3.6... with root and twrp installed. So I wanted to update to Miui 11 and I uninstall Magisk and done the update through the twrp.
So, in order to back magisk I wanna to go to twrp via fastboot and PC. But I am constantly getting message "ADB devices unauthorized". Anyway... this is only happening when phone is shutted off(in order to go to fastboot mode). When phone is turned on everything is fine and I can se device via adb command prompt. I tried any written solution on internet but nothing could solve the problem. When I connect turned on phone I regularly get the question to authorize phone and I click ok. And while phone is turned on everything is fine and I have accsess to internal and external memory of phone.
Is there any possible solution to solve this stuck ? Is there some other way to boot into twrp besides fastboot ? For now I would skip installing magisk via stock recovery or without twrp access.
Thanks infront !
This is how its susposed to work. Device should be online when turned on, and not when off. This is first time i heard someone try to connect device wiht adb via fastboot.
EugenStanis said:
This is how its susposed to work. Device should be online when turned on, and not when off. This is first time i heard someone try to connect device wiht adb via fastboot.
Click to expand...
Click to collapse
Thank you for reply.
I think that the reguar way for boot into twrp via pc is that your phone is turned off. Than you connect with pc and start adb commands. I dont understand, really.
Ok, how can I boot into twrp without pc if dfe is not flashed ?
visinacgile said:
Thank you for reply.
I think that the reguar way for boot into twrp via pc is that your phone is turned off. Than you connect with pc and start adb commands. I dont understand, really.
Ok, how can I boot into twrp without pc if dfe is not flashed ?
Click to expand...
Click to collapse
You use fastboot instead of adb commands when phone is off. Put your phone in fastboot mode and type commands like fastboot boot (drop your twrp image here) and hit enter
EugenStanis said:
You use fastboot instead of adb commands when phone is off. Put your phone in fastboot mode and type commands like fastboot boot (drop your twrp image here) and hit enter
Click to expand...
Click to collapse
Yes. My mistake... huge. Thank you. I forget tottaly.
Should I delete this thread ?
visinacgile said:
Yes. My mistake... huge. Thank you. I forget tottaly.
Should I delete this thread ?
Click to expand...
Click to collapse
No problem. Leave it like it is for other users :highfive:
Hey guys, my friend gave me his a21s to unlock it but I really can't find a way to do that.
The phone has a pattern lock that he doesn't remember it...
Also it doesn't have Developer mode enabled.
and in recovery mode, FactoryReset option is not available...
any idea?
The door to any Android device is ADB: because it's not got enabled you have to chance, IMO.
BTW: A Factory Reset doesn't remove FRP lock.
jwoegerbauer said:
The door to any Android device is ADB: because it's not got enabled you have to chance, IMO.
BTW: A Factory Reset doesn't remove FRP lock.
Click to expand...
Click to collapse
thanks for replay, but what else can I do?
I can get into the Fastboot mode from recovery menu but no command works there...
Dr TJ said:
thanks for replay, but what else can I do?
I can get into the Fastboot mode from recovery menu but no command works there...
Click to expand...
Click to collapse
Fastboot deals with device's bootloader, but NOT with Android OS as ADB does.
HI to all
I got my phone back from service, latest version installed (DN2103_11_A.14 EU).
I will flash TWRP and root, so do I need A.14 vbmeta or can I just use vbmeta from same post I will download TWRP?
If I need A.14 vbmeta, does anyone have it?
Thanks
There is no difference, the same one can be used for all versions.
you can use the vbmeta from TWRP Thread.
Zombnombs said:
There is no difference, the same one can be used for all versions.
Click to expand...
Click to collapse
HI and thank you.
HofaTheRipper said:
you can use the vbmeta from TWRP Thread.
Click to expand...
Click to collapse
HI and thank you.
How do you enter fastboot mode? There is no option from power button, and when I use adb reboot bootloader, I go to a black screen with font size 1 that says we are in fastboot mode, and this is for developers only, press power up + power to exit.
In recovery there is no "Advanced" option to reboot to fastboot.
krugm0f0 said:
I use adb reboot bootloader, I go to a black screen with font size 1 that says we are in fastboot mode, and this is for developers only, press power up + power to exit
Click to expand...
Click to collapse
That's exactly what fastboot mode is. Your phone is in fastboot mode. Use your poershell terminal on the pc to start sending fastboot commands. Eg "fastboot devices" to test the connection.
If you phone is not responding to fastboot commands, try adding "./" to the start of every fastboot command instead, eg "./fastboot devices"
Zombnombs said:
That's exactly what fastboot mode is. Your phone is in fastboot mode. Use your poershell terminal on the pc to start sending fastboot commands. Eg "fastboot devices" to test the connection.
If you phone is not responding to fastboot commands, try adding "./" to the start of every fastboot command instead, eg "./fastboot devices"
Click to expand...
Click to collapse
It's just that it looks nothing like the fastboot mode on my OP2, OPX, OP5T or OP Nord 5G. And it's not recognized by fastboot devices, and does not accept any commands. <waiting for device>
krugm0f0 said:
It's just that it looks nothing like the fastboot mode on my OP2, OPX, OP5T or OP Nord 5G. And it's not recognized by fastboot devices, and does not accept any commands. <waiting for device>
Click to expand...
Click to collapse
Seems like you just don't have the right drivers installed. Sure it looks different but that doesn't mean it has to work differently.
Windows can get the drivers automatically for you, connect in fastboot mode, then check for updates in windows, then they should either get installed or show up in optional updates as Mediatek ADB something.