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.
Related
im trying to unlock bootloader and i have downloaded the pudding sbf file (derpunlock.sbf)
but with no succes it failed everytime im trying to flash
flash error log :
00:41:34, October 07, 2011
Line: 768
ERROR: Phone[0001]: The "Secure_Motorola_Flash" Interface could not be found.
The super-file is secure and for re-flash;
the phone needs a super-file that is not secure and not for re-flash.
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\MIFlash.cpp
Device ID: 1
00:41:34, October 07, 2011
Line: 610
ERROR: Flash failure: Phone[0001]: The "Secure_Motorola_Flash" Interface could not be found.
The super-file is secure and for re-flash;
the phone needs a super-file that is not secure and not for re-flash. (Error Code: 66),
Detailed Error Details: Direction of the Error=No Direction, Command Value=0, Code Group Number=255
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 1
please help , thanks
salim said:
im trying to unlock bootloader and i have downloaded the pudding sbf file (derpunlock.sbf)
but with no succes it failed everytime im trying to flash
flash error log :
00:41:34, October 07, 2011
Line: 768
ERROR: Phone[0001]: The "Secure_Motorola_Flash" Interface could not be found.
The super-file is secure and for re-flash;
the phone needs a super-file that is not secure and not for re-flash.
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\MIFlash.cpp
Device ID: 1
00:41:34, October 07, 2011
Line: 610
ERROR: Flash failure: Phone[0001]: The "Secure_Motorola_Flash" Interface could not be found.
The super-file is secure and for re-flash;
the phone needs a super-file that is not secure and not for re-flash. (Error Code: 66),
Detailed Error Details: Direction of the Error=No Direction, Command Value=0, Code Group Number=255
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 1
please help , thanks
Click to expand...
Click to collapse
1) Take a deep breath - everything is okay
2) You're supposed to get that error
3) Pull the battery after your phone freezes up
4) Get into fastboot mode (power + Vol down)
5) Run the Moto-fastboot command to confirm being unlocked
You're set!
thanke u for helping ,
i just run the cmd command moto-fastboot and it has show me a list of options and commands... thats what it should happens ?
and when i reboot in fastboot it havent shown me that it unlocked... ( i just got my photon yesterday.. )
salim said:
thanke u for helping ,
i just run the cmd command moto-fastboot and it has show me a list of options and commands... thats what it should happens ?
and when i reboot in fastboot it havent shown me that it unlocked... ( i just got my photon yesterday.. )
Click to expand...
Click to collapse
Hmm...when you flash the unlocker, it will fail. This has exactly happened to me. I then proceeded to pull the battery. When I power on the phone again, it should say "Unlocked" at the top above the motorola screen. When you put into fastboot mode, press volume up and start the moto-fastboot commands:
- Type moto-fastboot oem unlock
- Look for the UNIQUE ID number and copy it, use copy or your fat fingers might mistype it.
- Type moto-fastboot oem unlock YOUR_UNIQUE_ID_THAT_YOU_JUST_COPIED
(from the original thread)
It should say "Your phone is already unlocked" or something like that....
- type moto-fastboot reboot or fastboot reboot depending
You should be all set...I'm not sure why it wouldn't say "Unlocked" when powering on the phone again...Try again...just make sure to fully charge your phone, plug it into the back of the computer, and wait for the unlocker to fail. It shouldn't take that long...keep trying!
thanke u very much ! you realy helped me =]
salim said:
thanke u very much ! you realy helped me =]
Click to expand...
Click to collapse
No problem..just hit that "Thanks" button..I'd appreciate it!
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...
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.
Hi all,
How can I wipe the cache partition on a Poco F1 with 10.3.6.0 Global stable (stock, so not rooted)? Booting in recovery mode gives me a custom recovery with only the option to wipe all data. Can Mi Assistant help here? Or are there other options?
Google would have helped you... Reboot to recovery and try 'fastboot erase cache'. Sometimes you need a 'sudo su' before that.
guhvanoh said:
Google would have helped you... Reboot to recovery and try 'fastboot erase cache'. Sometimes you need a 'sudo su' before that.
Click to expand...
Click to collapse
Well, as I said: I have stock ROM. As far as I see I do not have any option to erase system cache in the default recovery.
As I said as well: I have stock firmware, perhaps should have added locked bootloader. So no possibility to use fastboot (again, correct me if I'm wrong).
If the only option is to unlock the bootloader I can just replace recovery with TWRP, but I'd like to avoid having to unlock...
Hi there,
First enable USB debugging in the developer options. To enable developer options, you have to tap five times on the miui version in the about phone. Connect your PC and accept the pop up in your phone to register the pc in your phone. Power off your phone first and press power button and volume down simultaneously to take you to fastboot mode. If it goes to bootloader mode, then select the option to go to fastboot mode. If the bootloader mode is in Chinese then search some forums to select the fastboot mode appropriately.
Before all these. Install minimum ADB tools in your PC. Execute fastboot commands once connected to your phone in fastboot mode.
This is very simple once you are familiar with the process. Until then these seems a nightmare'.
Cheers
sssyraj
Hit thanks if it helps you.
And just to add to the above instructions, you don't need an unlocked bootloader, just have USB debugging enabled, to use fastboot.
You use fastboot to unlock the bootloader and it would be a mite hard (and redundant) if you needed the bootloader unlocked to unlock the bootloader...
Also, just to confirm the phone is being detected in fastboot mode use the command "fastboot devices" to see if the phone is recognised.. It should show a number otherwise if it is just a blank space fastboot hasn't recognised your phone...
ultramag69 said:
And just to add to the above instructions, you don't need an unlocked bootloader, just have USB debugging enabled, to use fastboot.
You use fastboot to unlock the bootloader and it would be a mite hard (and redundant) if you needed the bootloader unlocked to unlock the bootloader...
Also, just to confirm the phone is being detected in fastboot mode use the command "fastboot devices" to see if the phone is recognised.. It should show a number otherwise if it is just a blank space fastboot hasn't recognised your phone...
Click to expand...
Click to collapse
Got it into fastboot, but now it throws an error. Google search did not give a real solution.
Error shown:
Code:
******** Did you mean to fastboot format this ext4 partition?
erasing 'cache'...
FAILED (remote: Erase is not allowed in Lock State)
finished. total time: 0.007s
jvdv360 said:
Got it into fastboot, but now it throws an error. Google search did not give a real solution.
Error shown:
Click to expand...
Click to collapse
With that error shown I'm not sure what formatting will do. If the current type is ext4, then you should be fine. But it is looking like you're a candidate for unlocking your bootloader...
Hello I have a xiaomi mi mix 3 5g that I never removed the bootloader on, as it had the stock EU firmware on. It has recently been updated to to MIUI12. however the battery went low and went all weird and now constantly reboots.
I can get to fastboot by holding down the power and volume down, I have also tried a wipe device by holding down the power and up. From what I have read I i cant re-install fastboot firmware without and unlocked bootloader. (can someone confirm that this is correct) as its not clear.
***I have now confirmed this I have tried to install firmware using xiaomi flash tool and fails with the following
"Error: erasing boot Failed remote erase is not allowed in locked state. so this confirms it.
Also I cant unlock the bootloader as it wont boot. Does any body have any idea of what I can do with this phone? any help would be apprciated
thanks
The error I get when trying the mi unlock tool
Couldn't Unlock
Please add your account in MIUI;s Settings > Developer options > Mi Unlock Status
Seems the update miserably failed, Android OS got corrupted. My suggestion: Re-flash phone's Stock ROM ( phone's battery should be fully charged ! ).
To keep you updated:
FASTBOOT is a program used to manipulate ( list, install, erase ) the non-volatile memory such as flash filesystem partitions on devices that adhere to the fastboot protocol, via a USB connection from a host computer. It requires that the device be started in a boot loader mode ( AKA fastboot mode ) with the fastboot protocol enabled.
Take note that fastboot ( the fastboot daemon ) is integral part of phone's bootloader.
jwoegerbauer said:
Seems the update miserably failed, Android OS got corrupted. My suggestion: Re-flash phone's Stock ROM ( phone's battery should be fully charged ! ).
To keep you updated:
FASTBOOT is a program used to manipulate ( list, install, erase ) the non-volatile memory such as flash filesystem partitions on devices that adhere to the fastboot protocol, via a USB connection from a host computer. It requires that the device be started in a boot loader mode ( AKA fastboot mode ) with the fastboot protocol enabled.
Take note that fastboot ( the fastboot daemon ) is integral part of phone's bootloader.
Click to expand...
Click to collapse
How do I re-flash stock rom when the bootlloader is not unlocked.
I have already tried Xiaomi's flash tool and it when flashing the stock ROM and get the following error
"Error: erasing boot Failed remote erase is not allowed in locked state"
Are there any methods of flashing a stock rom with a locked bootloader ?
sivhead said:
How do I re-flash stock rom when the bootlloader is not unlocked.
I have already tried Xiaomi's flash tool and it when flashing the stock ROM and get the following error
"Error: erasing boot Failed remote erase is not allowed in locked state"
Are there any methods of flashing a stock rom with a locked bootloader ?
Click to expand...
Click to collapse
How to flash firmware to any Xiaomi smartphone is described here.
jwoegerbauer said:
How to flash firmware to any Xiaomi smartphone is described ["]here[/url].
Click to expand...
Click to collapse
I have already tried that method When I flash using the flash tool I get the error "Error: erasing boot Failed remote erase is not allowed in locked state" My bootloader is not unlocked is this method supposed to be work with a locked bootloader. Bit of chicken and egg situation. I cant unlock the bootloader as I cant boot the device and I cant reflash software as I don't have an unlocked bootloader.
AFAIK you always are allowed to flash an original firmware image without unlocking the phone's bootloader.
If you can access the device by means of ADB try to flash the Stock ROM via ADB:
Code:
adb devices
adb reboot sideload
adb sideload <LOCATION_OF_STOCK_ROM_ZIP_FILE_HERE>
C:\adb>adb devices
List of devices attached
f625af1 sideload
C:\adb>adb sideload miui_ANDROMEDAEEAGlobal_V12.0.1.0.PEMEUXM_9e4961bf09_9.0.zip
loading: 'miui_ANDROMEDAEEAGlobal_V12.0.1.0.PEMEUXM_9e4961bf09_9.0.zip'
* cannot read 'miui_ANDROMEDAEEAGlobal_V12.0.1.0.PEMEUXM_9e4961bf09_9.0.zip' *
@sivhead
Try this:
Rename the file to rom.zip and then start "adb sideload rom.zip"
jwoegerbauer said:
@sivhead
Try this:
Rename the file to rom.zip and then start "adb sideload rom.zip"
Click to expand...
Click to collapse
tried that same error cannot read rom.zip
sivhead said:
tried that same error cannot read rom.zip
Click to expand...
Click to collapse
C:\adb>adb sideload c:\Users\Administrator\Downloads\andromeda_eea_global_images_V12.0.1.0.PEMEUXM_20200823.0000.00_9.0_eea_70004ce050.zip
loading: 'c:\Users\Administrator\Downloads\andromeda_eea_global_images_V12.0.1.0.PEMEUXM_20200823.0000.00_9.0_eea_70004ce050.zip'* failed to read command: No error
I also thought its worth mentioning that I have never registered the device with mi connect
Also enable usb debugging is not enabled.
aqnd THe bootloader is locked .
Man I wish I would have unlocked the bootloader when I got it and put a custom rom on. then I wouldnt be in this situation. how ironic that I wanted to keep it stock
so I am at a loose end