Hi,
I screwed up my Amazfit Pace trying to install a Stratos custom rom (not intentionally). Using ADB I reinstalled the usual XDA Pace custom rom I had on my watch before but after installation the watch remains stuck in bootloop. I tried to unbrick it flashing the image parts in fasboot mode but once setted the watch in fastboot mode when I try to send the command "fastboot boot recovery.img" to boot the Amazfit in recovery mode, I get this from the prompt: "downloading 'boot.img'...
FAILED (remote: ED: The command is not allowed.)
finished. total time: 0.062s".
I don't knnow what to do now except trow the watch in the trashcan...
Help!
bootloader could be locked again or something with the serial nr.
Try in fastboot mode:
fastboot getvar all
Give us the output.
nhedgehog said:
bootloader could be locked again or something with the serial nr.
Try in fastboot mode:
fastboot getvar all
Give us the output.
Click to expand...
Click to collapse
Thx for the reply but I solved installing a custom image based on the original Stratos rom adapted for the Pace by Nicola Salgliano. I not used the fasboot mode but just the siple ADB commands: "adb push update.zip /sdcard/" then "adb push recovery.img /sdcard/" etc. and after the usual command cd /sdcard/; sh start_update.sh like a normal update.
Now my Pace works again.
But the dubt remain, why the watch didn't going in recovery mode?
I'd like to test your hints but I'm afraid to get stuck again...
Related
Hi all,
I have an issue where my device is not recognized by adb when in recovery.
it shows something like below when in recovery
adb devices
000000000 device
when is device is in fastboot
fastboot devices
it shows the serial number
but when i run command
fastboot reboot
rebooting...
finished. total time: 0.001s
and the device wont reboot,
also other fastboot commands like
fastboot flash recovery /(whatever path) will end up with some error
Please can any one help me out with this...
FYI: all commands in adb work fine with my Nexus one but these are the issues with HTC hero G2.
Apologize as this is also posted in a wrong section in http://forum.xda-developers.com/showthread.php?t=1841730
I have re-installed adb but still no luck,
is there no solution to this ????
Hello,
I accidentally flashed a Stratos firmware on my Amazfit Pace 1. Blame on me !
But since I cannot unbrick it.
I can boot in fastboot bootloader thank to thread https://forum.xda-developers.com/smartwatch/other-smartwatches/amazfit-boot-fastboot-directly-t3546829,
but I cannot boot into recovery with command :
> fastboot boot Amazfit-mod-recovery.img
downloading 'boot.img'...
FAILED (remote: ED: The command is not allowed.)
finished. total time: 0.063s
Can anybody provide help ?
Thanks in advance
The error message is because bootloader is locked. If you don't have root access nor unlocked bootloader, I guess the only option is trying to use Ingenic's "cloner" tool to flash the firmware directly (use option 2 instead of 1 to enter "force erase"). You should flash an old firmware with unlocked bootloader first, check if serial number is OK (if now, fix it using the info in the thread about fixing a null SN) then update.
PS: Do NOT enter "force erase" without having everything set up correctly because the watch won't leave this mode until you flash it.
lfom said:
The error message is because bootloader is locked. If you don't have root access nor unlocked bootloader, I guess the only option is trying to use Ingenic's "cloner" tool to flash the firmware directly (use option 2 instead of 1 to enter "force erase"). You should flash an old firmware with unlocked bootloader first, check if serial number is OK (if now, fix it using the info in the thread about fixing a null SN) then update.
PS: Do NOT enter "force erase" without having everything set up correctly because the watch won't leave this mode until you flash it.
Click to expand...
Click to collapse
Thanks @IFOm
the problem I have is that the swatch boots, then reboot, and finally fall into error screen. So I have little time to act with adb.
iznogoud! said:
Thanks @IFOm
the problem I have is that the swatch boots, then reboot, and finally fall into error screen. So I have little time to act with adb.
Click to expand...
Click to collapse
On Windows use:
Code:
adb wait-for-device & adb shell reboot bootloader
and on Linux/macOS:
Code:
adb wait-for-device; adb shell reboot bootloader
and watch will enter fastboot mode as soon as adb is detected (you can type the command and adb will wait for the device, as the words say, then issue the second one).
adb shell does not work, I get following message :
- exec '/system/bin/sh' failed: Exec format error (8) -
using port=5555
enter fastboot using this method https://www.youtube.com/watch?v=ZlXoeq30vM0 and check the correctness of the serial number and the bootloader lock
iznogoud! said:
adb shell does not work, I get following message :
- exec '/system/bin/sh' failed: Exec format error (8) -
using port=5555
Click to expand...
Click to collapse
Your system is messed up... You can go to fastboot mode manually, then try to flash the correct kernel (boot.img) and recovery from fastboot... this my fix your serial number and show locked status as unlocked again. If everything fails, your last resource is the cloner tool I mentioned a few comments before.
a bit similer with this case
my friend bought it 20 days ago and he unlock it
but he cant flash twrp as like guides
he had no expirience before this
so i get tablet and tried to solve the problem but
fastboot doesnt work properly
fastboot devices/reboot/device-info works
but
fastboot flash recovery twrp.img/ flash boot boot.img(guide on carbon rom)/boot twrp.img/and etc that for flashing or change any system
does not work
massage like failed(long link/bigger than max allowed)
changing everytime i try
i though there might some issues when my friend unlock the bootloader
so i 'fastboot oem lock' and try to unlock again
but from then fastboot not work properly
can be boot or 'adb reboot fastboot' to fastboot
but it become unknown device on windows device manager
fastboot command not work
when mi flash try to detect device, fastboot mode end and 'press any key to power off' screen came out
some times it working for few seconds so i try unlock with official xiaomi tool but tool said 'already unlocked'
right after i locked bootloader i used 'fastboot oem device-info' and checked bootloader is locked
i can switch oem unlock on/off in developer option but it doesnt change anything
i searched as i can and edl mode looks last
but few things to consider
1. its official chinese rom and working now
2. i dont know broken fastboot can be restored with flashing rom with edl (i flash rom with update app in settings but not solved)
3. adb reboot edl doesnt work it just rebooted(should teardown it but i dont know what pin to short)
the reason why i trying to install custom rom(or eu rom) is my friend and i not live in native english country
hope i get some help
thx
Ryzen CPU?
thE_29 said:
Ryzen CPU?
Click to expand...
Click to collapse
ryzen 1, 2, intel sandy etc
tried all i got
Im almost sure flashing stock rom with MiFlashTool should solve this problem as it does flash partritions as recovery and fastboot too. Have you tried this one?
KrakmanCz said:
Im almost sure flashing stock rom with MiFlashTool should solve this problem as it does flash partritions as recovery and fastboot too. Have you tried this one?
Click to expand...
Click to collapse
nope
cant go into edl mode until i teardown it
miflash 2018 doesnt connect with pad on fastboot mode
miflash should connect to mi devices when in fastboot mode. I would consider checking drivers for the device, try to install MiSuite, it should install all drivers needed for those actions. Also, in the fastboot mode you are trying some commands, are you using Windows 10 Powershell or basic cmd?
chocodesk said:
ryzen 1, 2, intel sandy etc
tried all i got
Click to expand...
Click to collapse
Ok, when you also tried Intel.. But Ryzen CPUs have major problems with the flash tool and the tablet. Would not do anything on Ryzen PCs.
KrakmanCz said:
miflash should connect to mi devices when in fastboot mode. I would consider checking drivers for the device, try to install MiSuite, it should install all drivers needed for those actions. Also, in the fastboot mode you are trying some commands, are you using Windows 10 Powershell or basic cmd?
Click to expand...
Click to collapse
on basic
with was detected as fastboot before
but know its unknown on device manager
update driver doesnt work
Try using a usb 2.0 port? If you ever need to, hard reset is holding all buttons at once for 30 seconds.
Dannyboy3210 said:
Try using a usb 2.0 port? If you ever need to, hard reset is holding all buttons at once for 30 seconds.
Click to expand...
Click to collapse
i tried 2.0 and 3.0
not work
tablet owner decide to use it on stock chinese rom
not in my hand now
$ adb reboot bootloader
List devices on fastboot :
$ fastboot devices
XXXXXX fastboot
Check if bootloader is unlocked :
$ fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
OKAY [ 0.001s]
Finished. Total time: 0.003s
Flash TWRP recovery :
$ fastboot flash recovery recovery.img
Sending 'recovery' (54400 KB) OKAY [ 1.540s]
Writing 'recovery' OKAY [ 0.410s]
Finished. Total time: 1.952s
Reboot your device
$ fastboot reboot
Rebooting
Finished. Total time: 0.000s
I installed TWRP on MIUI 10 using this description. On the end , after TWRP installed - I rebooted again to TWRP and installed stock rom at once . I not tested , but theory says , MIUI will reflash recovery if it will be booted in this situation .
Sorry to piggy-back off this post, but I'm having a similar issue with my Mi Pad I just received:
I can boot it into Fastboot mode no problem, even see it listed when I use the "Fastboot devices" command. When I run the OEM info everything comes back true for unlocked.
However, when I try to flash anything I get the max size error or just a "FAILED" and it kicks the Mi Pad to a black screen with the white text "Press any key to shut down".
Any ideas?
*edit*
I've continued testing, and I'm really at a loss here. See the response I'm getting using fastboot:
\minimal_adb_fastboot_1.4.3_portable>fastboot flash boot kernel.img
target didn't report max-download-size
sending 'boot' (15060 KB)...
FAILED (command write failed (No error))
finished. total time: 0.003s
I can transfer files in windows no problem... I can use adb commands no problem... fastboot just doesnt seem to work.
I figured out my issue. You cannot use USB 3 ports to connect and run fastboot commands. I bought a cheap USB 2 hub, ran the cable from that and had no problems at all.
hello everyone.
my phone is stuck in meizu 16th and fastboot mode.
I can't upload twrp.
I can't load rom.
can you help me please
my English is bad. sorry..
@ybk993
Try
Code:
fastboot devices
fastboot reboot
to boot into normal Android
jwoegerbauer said:
@ybk993
Try
Code:
fastboot devices
fastboot reboot
to boot into normal Android
Click to expand...
Click to collapse
I tried but it didn't work.
Hi did you manage to make it work again I have the same issue
Hi Guys,
can you help me out?
I have the 16th as well and I´m stuck during unlocking the bootloader.
adb devices
adb reboot bootloader
> all good.
fastboot devices
"shows the name"
But after "fastboot flashing unlock" there is an failed message:
"FAILED (remote: Command not support: the display is not enabled)"
The display is on and shows "=> Fastboot mode (sec, locked, unrooted)
OEM unlocking and USB debugging is activated....
What should i de next?
MrWukong said:
Hi Guys,
can you help me out?
I have the 16th as well and I´m stuck during unlocking the bootloader.
adb devices
adb reboot bootloader
> all good.
fastboot devices
"shows the name"
But after "fastboot flashing unlock" there is an failed message:
"FAILED (remote: Command not support: the display is not enabled)"
The display is on and shows "=> Fastboot mode (sec, locked, unrooted)
OEM unlocking and USB debugging is activated....
What should i de next?
Click to expand...
Click to collapse
Hi, I have the same problem. have you dealt with her? if yes, then tell me
Hi, just got a brand new Armour x5, bought unlocked. It has Android 10 on it. First, I would like to back up entire phone without installing any apps at all, adb or fastboot commands to do so would be appreciated.
I tapped developer options 7 times, enabled adb, and OEM unlocking. I then adb reboot fastboot after allowing pc to connect, and in fastboot I try:
fastboot oem unlock
and
fastboot flashing unlock
C:\adb>adb devices
List of devices attached
3082SH1001004262 device
C:\adb>adb reboot recovery
C:\adb>fastboot devices
3082SH1001004262 fastboot
C:\adb>fastboot oem unlock
...
FAILED (remote: Command not supported in default implementation)
finished. total time: 0.010s
C:\adb>fastboot flashing unlock
...
FAILED (remote: Unrecognized command flashing unlock)
finished. total time: 0.010s
to no avail, fastboot just looks blackscreen and the tiniest of fonts lol... yes drivers are installed.
So I reboot, and try the Armour 6 tut, but Magisk manager has no option to patch the boot.img I extracted from stock firmware, it also has a distinct lack of advanced settings, most likely due to my not yet having flashed a twrp or magisk-20.4 due to still unable to find out about dm-verity, (is dm-verity different between android 9 + 10?) meaning I wont flash anything that will brick the fone before i even put a sim into it.
Any help appreciated. Google sux.
Edit: Well after 12 or so hours I can honestly say that rooting is all gone downhill, does anyone actually know what they are doing nowadays?
I read all 5 copies of the rooting procedure for this phone, none of which is anywhere near complete, and so very wrong. What might have worked years ago does not work now.
In the Armour x5, when rebooting into fastboot using adb reboot fastboot, we are taken to a black screen with the smallest of txt saying fastboot. This fastboot does not ****in work ('scuse the swearing) so dont tell people to do this, it wont work. Nothing works in this fastboot mode. What you have to do is go into ANOTHER fastboot, by going into what we call recovery, by pressing power and volume up button, then choosing fastboot, ONLY then will fastboot commands kind of work. I say kind of, because most of the fastboot commands do nothing anyway, but at least show some output proving that booting into fastboot from adb is useless now.
For instance, in the pure black screen fastboot, nothing is found in adb or fastboot shell, no 'null' (needing activation), no waiting, just black nothingness. But in the recovery version of fastboot, we see fastbootd at the top of the screen, this is the fastboot that recognises at least partial commands. But none I have actually tried re finding bootloader lock status etc, nada.
I also noticed, I do have shell access when in adb, but not recovery, so if anyone knows how to flash a twrp for android 10 using shell with no root, I'll try it on my not so shiney brand spankin blank fastbootin fone