I have a chinese Allwinner 7" tablet ( Rocky M713HD ) , I was trying install a CWM recovery image. I connected my tablet to PC, opened my terminal and taped:
adb push recovery.img /data/
adb shell "cat /data/recovery.img > /dev/block/nandg; sync"
adb shell "echo -n boot-recovery | busybox dd of=/dev/block/nandf count=1 conv=sync; sync; reboot"
After that, my tablet freezes on bootloader with no single info on adb when typing "adb devices"
As you can see, I missed a caracter on the 3rd line: ( nandg/nandf )
Can anyone give me a solution to flash my tablet? I was on Allwinner 4.2.2 ROM.
Thank you in advance!
Was your bootloader unlocked prior to flashing recovery?
Rudjgaard said:
Was your bootloader unlocked prior to flashing recovery?
Click to expand...
Click to collapse
No
Then that's most likely your problem.
You should restore stock fw and then start from scratch remembering to unlock bootloader this time
(or you can use cwm app from playstore i think it can install recovery on locked bl)
can u go to download mode
ummarrkhan said:
can u go to download mode
Click to expand...
Click to collapse
No, now, it's only showing me the manufacturer's logo. I only have Power and Home buttons, I tried some combinations but nothing happened
elacheche.bedis said:
No, now, it's only showing me the manufacturer's logo. I only have Power and Home buttons, I tried some combinations but nothing happened
Click to expand...
Click to collapse
bring to service center
Related
Noticed this morning, when I power up holding HOME the phone lockes on the 'HERO' first screen and I can not get into RA...
Anyone got any ideas ?
somebody ? anybody ? this is a disaster, i can not get into my boot menu to install or flash or anything. the phone boots normally if i dont hold the HOME button, but when i power on with the home button held, it locks..... please help me...
Ian_4614 said:
somebody ? anybody ? this is a disaster, i can not get into my boot menu to install or flash or anything. the phone boots normally if i dont hold the HOME button, but when i power on with the home button held, it locks..... please help me...
Click to expand...
Click to collapse
Happened to me too.. no worries..
Re-flash AR through fastboot and it will work again..
adb shell reboot bootloader
adb shell mount /sdcard
adb push recovery-RA-hero-v1.6.2.img /sdcard/recovery-RA-hero-v1.6.2.img
adb shell flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img
adb shell reboot
that's it .. you can rename recovery-RA-hero-v1.6.2.img to something shorter so you don't have to type so much
inertiax3 said:
Happened to me too.. no worries..
Re-flash AR through fastboot and it will work again..
adb shell reboot bootloader
adb shell mount /sdcard
adb push recovery-RA-hero-v1.6.2.img /sdcard/recovery-RA-hero-v1.6.2.img
adb shell flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img
adb shell reboot
that's it .. you can rename recovery-RA-hero-v1.6.2.img to something shorter so you don't have to type so much
Click to expand...
Click to collapse
thanks, but i do not understand, how do i access fastboot ? i am keen to learn but this is new to me...
I'm pretty sure that this is the process, got this from the RA-heroc-v1.6.2.img thread:
adb shell reboot bootloader
fastboot boot recovery-RA-heroc-v1.6.2.img
adb shell mount /sdcard
adb push recovery-RA-heroc-v1.6.2.img /sdcard/recovery-RA-heroc-v1.6.2.img
adb shell flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img
adb shell reboot
Click to expand...
Click to collapse
muzz3256 said:
I'm pretty sure that this is the process, got this from the RA-heroc-v1.6.2.img thread:
Click to expand...
Click to collapse
Appreciate that,, but i am sorry to say it does not make any sense to me. How to i get into FastBoot,, what do I press etc,, and once I am there,, what do I do ?
Ian_4614 said:
Appreciate that,, but i am sorry to say it does not make any sense to me. How to i get into FastBoot,, what do I press etc,, and once I am there,, what do I do ?
Click to expand...
Click to collapse
I NEVER DONE THIS BEFORE...
back + power button will take you to fastboot...
BUT, I believe "adb shell reboot bootloader" will take you to the right place instead of trying button combinations. So, you can run these commands from normal boot itself.
so when you say, run from normal boot itself, you mean from a file manager etc ?
Ian_4614 said:
so when you say, run from normal boot itself, you mean from a file manager etc ?
Click to expand...
Click to collapse
No!
Do you have adb setup? If not set it up using this link:
http : // theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
Check this link as well: http://forum.xda-developers.com/showthread.php?t=502010
no, you start your phone up normal, go to settings and make sure usb debugging is enabled, then connect your usb-cabel, go to your sdk-directory and type adb shell reboot bootloader, then your phone will reboot into fastboot
Not sure,, this is what I added when I flashed the phone..
boot up the hero, plug in the usb, execute the commands that were given to you on the pc. that is all. you need adb on the pc for that.
right, i dod not know i had to have a programe on the PC,,, I will look for adb and see where I can find it. Is this an app I need to install on the PC ? where do I get it ?
Ian_4614 said:
right, i dod not know i had to have a programe on the PC,,, I will look for adb and see where I can find it. Is this an app I need to install on the PC ? where do I get it ?
Click to expand...
Click to collapse
cracked it, downloaded ROM MANAGER app and this enabled me to flash alternative RA Recovery,, and all now working,
Im starting this new thread because I was not able to find a solution for my problem for about 2 weeks now.
Issue : Unable to install recovery. Im trying to install recovery by following this thread : http://forum.xda-developers.com/showthread.php?t=2221102 - in the 3rd step when i flash the recovery i get this error "command write failed - unknown error"
- tried almost all the different types of steps available in xda and also outside xda.
My Environment:
Win8 Pro 32bit
LG optimus L9 flashed and rooted by lelus method - Current ROM - P76020c
Installed all LG drivers - PC suite is installed
Have SDK manager installed
Device is recognized when I run the "adb devices" command keeping phone switched on.
Device is recognized when I run the "fastboot devices" command when phone is in fastboot mode.
So I guess this is not a driver issue.
Im also attaching screenshots of the error and the commands that I have ran ....
SOOOOOOOOOOOO ... whats the prob here .... ... anyone faced this same prob ???? HELPPPP
rkn989 said:
Im starting this new thread because I was not able to find a solution for my problem for about 2 weeks now.
Issue : Unable to install recovery. Im trying to install recovery by following this thread : http://forum.xda-developers.com/showthread.php?t=2221102 - in the 3rd step when i flash the recovery i get this error "command write failed - unknown error"
- tried almost all the different types of steps available in xda and also outside xda.
My Environment:
Win8 Pro 32bit
LG optimus L9 flashed and rooted by lelus method - Current ROM - P76020c
Installed all LG drivers - PC suite is installed
Have SDK manager installed
Device is recognized when I run the "adb devices" command keeping phone switched on.
Device is recognized when I run the "fastboot devices" command when phone is in fastboot mode.
So I guess this is not a driver issue.
Im also attaching screenshots of the error and the commands that I have ran ....
SOOOOOOOOOOOO ... whats the prob here .... ... anyone faced this same prob ???? HELPPPP
Click to expand...
Click to collapse
As always, use at your own risk.
Upload recovery image to sdcard and change the file name to recovery.img if that helps
flash via adb from your computer
Code:
adb shell su -c busybox dd if=/sdcard/external_sd/recovery.img of=/dev/block/mmcblk0p4
or terminal emulator straight from the phone
Code:
su
busybox dd if=/sdcard/external_sd/recovery.img of=/dev/block/mmcblk0p4
Lelus said:
flash via adb from your computer
Code:
adb shell su -c busybox dd if=/sdcard/external_sd/recovery.img of=/dev/block/mmcblk0p4
[/QUOTE]
is this the exact code that we should type into the cmd after getting to fastboot mode ??? or shud this be ran while phone is switched on ???
Click to expand...
Click to collapse
rkn989 said:
is this the exact code that we should type into the cmd after getting to fastboot mode ??? or shud this be ran while phone is switched on ???
Click to expand...
Click to collapse
phone switched on, usb mode: camera or lg software
btw, you have unlocked the bootloader , right ?
Lelus said:
phone switched on, usb mode: camera or lg software
btw, you have unlocked the bootloader , right ?
Click to expand...
Click to collapse
yess .... my bootloader is unlocked ....
tried this and get an error - su not found - check screenshot
im not getting the command that we tried :
adb shell su -c busybox dd if=/sdcard/external_sd/recovery.img of=/dev/block/mmcblk0p4
"su" stands for ???
and where should i copy the .img file to ?? (i copied it to the root of the ext sd card)
anyone any suggestions ?????
May be your file is corrupt. Just give it a try.
Download latest version of CWM Touch and Non-touch version from http://www.clockworkmod.com/rommanager and try again.
cmahendra said:
May be your file is corrupt. Just give it a try.
Download latest version of CWM Touch and Non-touch version from http://www.clockworkmod.com/rommanager and try again.
Click to expand...
Click to collapse
Ive already tried that ... have tried downloading the files many times .. already have 4-5 copies of both the normal and touch recoveries ...
Its the same error !!!!!!
And yu want me to try by the fastboot method rite ?? not the method lelus juzz said ???
Lelus said:
flash via adb from your computer
Code:
adb shell su -c busybox dd if=/sdcard/external_sd/recovery.img of=/dev/block/mmcblk0p4
or terminal emulator straight from the phone
Code:
su
busybox dd if=/sdcard/external_sd/recovery.img of=/dev/block/mmcblk0p4
Click to expand...
Click to collapse
Can yu explain this in more detail. ????
Sent from my LG-P760 using xda app-developers app
rkn989 said:
Ive already tried that ... have tried downloading the files many times .. already have 4-5 copies of both the normal and touch recoveries ...
Its the same error !!!!!!
And yu want me to try by the fastboot method rite ?? not the method lelus juzz said ???
Click to expand...
Click to collapse
Lelus is explaining you in details and he is expert here. I am just confirming that if you have tried the basic things or not. By the way, your fastboot drivers seem working as device responds to "fastboot devices" command properly.
The fastboot screen should show the phone is unlocked or not, exactly like this....does it show like this screenshot?
SW Upgrade mode also should show unlocked like this screnshot.
If not, you may not be yet Unlocked and fastboot will not work.
cmahendra said:
Lelus is explaining you in details and he is expert here. I am just confirming that if you have tried the basic things or not. By the way, your fastboot drivers seem working as device responds to "fastboot devices" command properly.
The fastboot screen should show the phone is unlocked or not, exactly like this....does it show like this screenshot?
SW Upgrade mode also should show unlocked like this screnshot.
If not, you may not be yet Unlocked and fastboot will not work.
Click to expand...
Click to collapse
I din know where exactly to run those commands, so asked detailed steps
And the my bootloader is unlocked, I get the fastboot boot mode when I run the adb reboot command to unlock bootloader, yday when I flashed my phone with v20c, I gt the second screenshot as yu mentioned, also i tried running that *# command from inside the phone and it showed bootloader status- unlock.
So I hope it is unlocked! !!
Sent from my LG-P760 using xda app-developers app
ATLASTTT !!!!!!!!!!!!! I have succeeded in flashing my recovery .....
but the resolution is strange .... it just worked fine in WIN7 .... isn't that strange ???????????
Hello all
I have installed the paranoid android 3+ rom but now I cannot access TWRP or the bootloader screen. Android boots normally and the tablet is perfectly functional. When the tablet is off, there is no way to get to TWRP using the keys (power on with Vol- pressed etc. I have used all possible combinations). Also, there is no option to boot into recovery mode from the menu in "Backup & reset". Also, when I try to boot into recovery through a terminal emulator it again boots into andoid normally as if I just did a normal reboot. The "reboot recovery" command issued from the terminal emulator does not boot into TWRP. Trying to boot into recovery mode from within Phoenix Suite again boots the machine normally rather than in recovery mode. It's driving me nuts. Could it be a corrupt/locked bootloader? Is it something else? It seems to me that the only possible path for the bootloader is to load Android.
Is there any way to blind flash the bootloader again? It seems that this is the culprit since I can copy TWRP to nandg through the terminal emulator ("cat /extsd/recovery.img > /dev/block/nandg; sync; sync ;sync" but then again rebooting goes into android rather than recovery mode. Could there be a similar solution like "cat /extsd/boot.img > /dev/block/nanda" for example?).
The tablet connects normally through USB to my PC and adb sees it properly.
Any ideas?
Thanks in advance
Nobody?
Try it via adb.
Command: adb reboot bootloader
It works for me.
Sent from my PC36100
merden765 said:
Try it via adb.
Command: adb reboot bootloader
It works for me.
Sent from my PC36100
Click to expand...
Click to collapse
Whatever I tried it does not boot into the bootloader, be it adb, Phoenix suite, or the terminal emulator. Is there any way to write the original booloader raw to the respective nand partition? And where can I get the original bootloader?
tzoykas said:
Whatever I tried it does not boot into the bootloader, be it adb, Phoenix suite, or the terminal emulator. Is there any way to write the original booloader raw to the respective nand partition? And where can I get the original bootloader?
Click to expand...
Click to collapse
I have same your problem and now i use goomanager this app can bring you to recovery mode or install in to your tablet.
Hello to all
I'm trying to porting cyanogenmod, but I have a problem unlocking the bootloader for recovery. Let me explain what I've done so far.
Root Phone via framaroot
Extracts recovery.img boot.img via adb
Code:
sudo adb start-server
adb shell
su
dd if=/dev/block/mmcblk0p9 of=/sdcard/boot.img
dd if=/dev/block/mmcblk0p17 of=/sdcard/recovery.img
exit
exit
adb pull /sdcard/booty.img
adb pull /sdcard/recovery.img
Initialized the project via mkvendor.sh
Code:
mkdir ~/android/system/vendor/LGE/vee7e
mkdir ~/android/system/device/LGE/vee7e
~/android/system/build/tools/device/mkvendor.sh LGE vee7e ~/boot.img
cd ~/android/system/
. build/envsetup.sh
make -j4 revoveryimage
make -j4 recoveryzip
I now have the CWM Recovery, and I inserted in my phone
Code:
cd ~/android/system/out/target/product/vee7e/
adb push recovery.img /sdcard/recovery-cwm.img
adb shell
su
dd if=/sdcard/recovery-cwm.img of=/dev/block/mmcblk0p17
Reboot the phone for enter in recovery mode (hold volume up + home button), and I had this surprise
Code:
[4380] -------------------------------------------------------------------
[4380]
[4380] Secure booting Error!
[4390] Cause: boot certification verify
[4390]
[4390] -------------------------------------------------------------------
Is there anyone who can help me?
Thanks
P.S. In the attached you will find my recovery and the error message.
P.P.S. Sorry for my bad English
Dexter885 said:
Hello to all
I'm trying to porting cyanogenmod, but I have a problem unlocking the bootloader for recovery. Let me explain what I've done so far.
Root Phone via framaroot
Extracts recovery.img boot.img via adb
Code:
sudo adb start-server
adb shell
su
dd if=/dev/block/mmcblk0p9 of=/sdcard/boot.img
dd if=/dev/block/mmcblk0p17 of=/sdcard/recovery.img
exit
exit
adb pull /sdcard/booty.img
adb pull /sdcard/recovery.img
Initialized the project via mkvendor.sh
Code:
mkdir ~/android/system/vendor/LGE/vee7e
mkdir ~/android/system/device/LGE/vee7e
~/android/system/build/tools/device/mkvendor.sh LGE vee7e ~/boot.img
cd ~/android/system/
. build/envsetup.sh
make -j4 revoveryimage
make -j4 recoveryzip
I now have the CWM Recovery, and I inserted in my phone
Code:
cd ~/android/system/out/target/product/vee7e/
adb push recovery.img /sdcard/recovery-cwm.img
adb shell
su
dd if=/sdcard/recovery-cwm.img of=/dev/block/mmcblk0p17
Reboot the phone for enter in recovery mode (hold volume up + home button), and I had this surprise
Code:
[4380] -------------------------------------------------------------------
[4380]
[4380] Secure booting Error!
[4390] Cause: boot certification verify
[4390]
[4390] -------------------------------------------------------------------
Is there anyone who can help me?
Thanks
P.S. In the attached you will find my recovery and the error message.
P.P.S. Sorry for my bad English
Click to expand...
Click to collapse
Look here: http://forum.xda-developers.com/showthread.php?t=2439949.
It seems that the bootloader is locked.
tylerr55 said:
Look here: http://forum.xda-developers.com/showthread.php?t=2439949.
It seems that the bootloader is locked.
Click to expand...
Click to collapse
If overwriting / dev/block/mmcblk0p5 with emmc_appsboot.bin, the phone will not boot up. It must be restored with an image kdz.
Any news? I've been waiting for cwm for long
Hey,
The correct comand on adb to unlock bootloader on Lg devices is:
adb reboot oem-unlock
6) now pull out your usb cable and your battery, too
7) put your battery back in and boot
8) set up your system
9) now go to the hidden menu and check your BL status (dialer: 3845#*880# --> Bootloader Unlock Check --> Bootloader Unlock Check --> Unlock)
reffer to http://forum.xda-developers.com/showthread.php?t=2224020
pedrocel85 said:
Hey,
The correct comand on adb to unlock bootloader on Lg devices is:
adb reboot oem-unlock
6) now pull out your usb cable and your battery, too
7) put your battery back in and boot
8) set up your system
9) now go to the hidden menu and check your BL status (dialer: 3845#*880# --> Bootloader Unlock Check --> Bootloader Unlock Check --> Unlock)
reffer to http://forum.xda-developers.com/showthread.php?t=2224020
Click to expand...
Click to collapse
Someone try this method on P710?
try, it will do no harm
maxx_hr said:
Someone try this method on P710?
Click to expand...
Click to collapse
Did you try it?
Did it work?
======================
OP:
Dexter885 said:
Hello to all
I'm trying to porting cyanogenmod, but I have a problem unlocking the bootloader for recovery. Let me explain what I've done so far.
Root Phone via framaroot
Extracts recovery.img boot.img via adb
Code:
sudo adb start-server
adb shell
su
dd if=/dev/block/mmcblk0p9 of=/sdcard/boot.img
dd if=/dev/block/mmcblk0p17 of=/sdcard/recovery.img
exit
exit
adb pull /sdcard/booty.img
adb pull /sdcard/recovery.img
Initialized the project via mkvendor.sh
Code:
mkdir ~/android/system/vendor/LGE/vee7e
mkdir ~/android/system/device/LGE/vee7e
~/android/system/build/tools/device/mkvendor.sh LGE vee7e ~/boot.img
cd ~/android/system/
. build/envsetup.sh
make -j4 revoveryimage
make -j4 recoveryzip
I now have the CWM Recovery, and I inserted in my phone
Code:
cd ~/android/system/out/target/product/vee7e/
adb push recovery.img /sdcard/recovery-cwm.img
adb shell
su
dd if=/sdcard/recovery-cwm.img of=/dev/block/mmcblk0p17
Reboot the phone for enter in recovery mode (hold volume up + home button), and I had this surprise
Code:
[4380] -------------------------------------------------------------------
[4380]
[4380] Secure booting Error!
[4390] Cause: boot certification verify
[4390]
[4390] -------------------------------------------------------------------
Is there anyone who can help me?
Thanks
P.S. In the attached you will find my recovery and the error message.
P.P.S. Sorry for my bad English
Click to expand...
Click to collapse
Any news about the recovery?
Vagelis1608 said:
Did you try it?
Did it work?
======================
OP:
Any news about the recovery?
Click to expand...
Click to collapse
Tried, does not work!, Googling I found this guide,
Code:
://translate.googleusercontent.com/translate_c?depth=1&hl=it&rurl=translate.google.it&sl=ru&tl=en&u=http://4pda.ru/forum/index.php%3Fshowtopic%3D466295%26st%3D0&usg=ALkJrhhM8yja33NUhK__pNP0aLRznOSGhg#entry22312158
But it not work well on the P710. I found this bug: when you disconnect and reconnect the battery the phone will not turn over and go into an infinite loop!
Necessary to crack the bootloader, but I nn I know these ...
The cwm start on my lg p710 but the same problem with battery,if i go in cwm(volum down+home+power)and rebot from there the phone start.
Sorry for my bad english.
I try CWM from this thread:
http://forum.xda-developers.com/show...2700579&page=3
on my P710, and it works-no upside down problem, no bootloops.
But I dont install gscript, just put APPSSBL.bin and recovery.img on their places.
After that, i perform backup with one warning message-no file_contexts, but on second backup it dissapears...:good:
nobody here still unlocked L7 II bootloader ?
please take look at this
http://forum.xda-developers.com/showthread.php?t=2212092&page=4
since page 4 there are users talking about unlocking bootloader and it seems some of them did unlock bootloader and installed succesfully CWM.
RenatoNismo said:
nobody here still unlocked L7 II bootloader ?
please take look at this
http://forum.xda-developers.com/showthread.php?t=2212092&page=4
since page 4 there are users talking about unlocking bootloader and it seems some of them did unlock bootloader and installed succesfully CWM.
Click to expand...
Click to collapse
Just see link from my post, this is newer version of your, taken from same russian site.
With this bootloader and CWM, i just flash some P713 mod (deodexed, with kit-kat look), but i can confirm some problem with restoring-everything works, but restoring data (maby because i have more than 500 files in one folder ) failed. I must try restoring without that amount of data.
Anyway, backup in my case, is success, because restoration of sistem/boot gives me result like factory reset of original (but some data, before error is restored). After restoring, i just reset/clean dalvik to clean garbage, and phone works like new one, and even stay rooted.
Sorry for bad english...
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.