Develop Bugs

Bricked Huawei watch, please help

Was in the process of flashing the 2.0 preview, ADB worked as well as fastboot. Before I unlocked the bootloader I wanted to see what the recovery looked like. Now the watch will start up with the huawei logo then flashes to android on his back with the red exclamation mark and says:
Supported API: 3
E: failed to mount /cache invalid
(it happens so fast I can't catch it all) and just loops every 5 sec or so.
I can manually get it to restart into bootloader but regardless of what I choose I get the same result. ADB will no longer find the device. I've tried everything I can find here as far as changing drivers and nothing is working. The only thing I can come up with is that when it first connected to my pc I hit "allow" not "always allow from this device". Is that stopping ADB from locating it now?
any help would be appreciated, I love this watch and seriously regret not just waiting for the ota.
*FIXED* although adb could not find my device sending the unlock command worked. Would still like to know how booting into recovery caused this.

Misery420 said:
I can manually get it to restart into bootloader but regardless of what I choose I get the same result. ADB will no longer find the device. I've tried everything I can find here as far as changing drivers and nothing is working. The only thing I can come up with is that when it first connected to my pc I hit "allow" not "always allow from this device". Is that stopping ADB from locating it now?
any help would be appreciated, I love this watch and seriously regret not just waiting for the ota.
Click to expand...
Click to collapse
When you are in bootloader mode, you should use "fastboot" instead of "adb". So boot into bootloader mode, then try the command: fastboot devices. If your watch is recognized, it is easy now. Run flash-all.bat from "sturgeon-mec23l" to flash stock MM firmware.

quantan said:
When you are in bootloader mode, you should use "fastboot" instead of "adb". So boot into bootloader mode, then try the command: fastboot devices. If your watch is recognized, it is easy now. Run flash-all.bat from "sturgeon-mec23l" to flash stock MM firmware.
Click to expand...
Click to collapse
Thanks for the reply, everything is working now :good::good:

Oh I have the same problem, may opened a topic... Except my watch stays on the huawei logo without the android image, but same error. But my bootloader is already unlocked, what command do I use?
Sent from my SM-G935F using XDA-Developers mobile app

Fastboot flash-all.bat should do it.

Hi guys. I was also flashing android wear 2.0 to my watch. Suddenly my watch was bricked. It doesnt even want to connect to my computer. What can I do? Thanks
Gerald

Hello
I have purchase this huawei watch on ebay
and i have the logo huawei on the watch but nothing
When i push the boutton, the watch reboot and again on the logo
adb devices say no devices
fastboot is waiting a devices
please help me
thanks

nicolas90340 said:
Hello
I have purchase this huawei watch on ebay
and i have the logo huawei on the watch but nothing
When i push the boutton, the watch reboot and again on the logo
adb devices say no devices
fastboot is waiting a devices
please help me
thanks
Click to expand...
Click to collapse
Look here. Last post
http://forum.xda-developers.com/huawei-watch/help/stuck-boot-animation-screen-t3328862

Pkt_Lnt said:
Look here. Last post
http://forum.xda-developers.com/huawei-watch/help/stuck-boot-animation-screen-t3328862
Click to expand...
Click to collapse
Thanks
It's ok Now

Misery420 said:
Was in the process of flashing the 2.0 preview, ADB worked as well as fastboot. Before I unlocked the bootloader I wanted to see what the recovery looked like. Now the watch will start up with the huawei logo then flashes to android on his back with the red exclamation mark and says:
Supported API: 3
E: failed to mount /cache invalid
(it happens so fast I can't catch it all) and just loops every 5 sec or so.
I can manually get it to restart into bootloader but regardless of what I choose I get the same result. ADB will no longer find the device. I've tried everything I can find here as far as changing drivers and nothing is working. The only thing I can come up with is that when it first connected to my pc I hit "allow" not "always allow from this device". Is that stopping ADB from locating it now?
any help would be appreciated, I love this watch and seriously regret not just waiting for the ota.
*FIXED* although adb could not find my device sending the unlock command worked. Would still like to know how booting into recovery caused this.
Click to expand...
Click to collapse
I have the same problem now... Can you please help me
What should I do..
---------- Post added at 05:30 PM ---------- Previous post was at 05:11 PM ----------
quantan said:
When you are in bootloader mode, you should use "fastboot" instead of "adb". So boot into bootloader mode, then try the command: fastboot devices. If your watch is recognized, it is easy now. Run flash-all.bat from "sturgeon-mec23l" to flash stock MM firmware.
Click to expand...
Click to collapse
What can I do if my watch is not recognized??
Please help ??

Pher3ona said:
What can I do if my watch is not recognized??
Please help
Click to expand...
Click to collapse
Have you installed the driver? If not, take a look at this page: https://www.reddit.com/r/hwatch/comments/3n9ckp/how_to_get_adb_access_over_usb/

Fastboot Mode

I want to unlock bootloader of my Mi Max 3. Already follow the procedure to unlock. Login to Mi Account in Mi Unlock Tool. My phone is in fastboot mode. When I connect the phone to PC, the fastboot mode on the phone suddenly disappear. On the top left of the phone screen there is a message "Tap any key to reboot". I try few times, the problem still assist. How to solve this

try a different USB port on your computer.

Try other USB drive, still the problem still there. Should I reset my phone?

cikli66 said:
Try other USB drive, still the problem still there. Should I reset my phone?
Click to expand...
Click to collapse
It would be easier to enable USB debug, get the unlock program started and phone connected, and use adb command to reboot to fastboot mode:
> adb reboot bootloader

Turn on Moto G5 with broken power button

The problem is that my moto g5 power button does not work. Normally I would just use the fingerprint scanner to turn it on; but in order to put in the sims card or the micro sd I need to remove the battery. Is there a fastboot or adb command i can run. It successful booted by me putting it on the charger once in the last 2 weeks but thats it.

O.P.P said:
The problem is that my moto g5 power button does not work. Normally I would just use the fingerprint scanner to turn it on; but in order to put in the sims card or the micro sd I need to remove the battery. Is there a fastboot or adb command i can run. It successful booted by me putting it on the charger once in the last 2 weeks but thats it.
Click to expand...
Click to collapse
You can use in bootloader fastboot reboot to power on your device and ADB reboot to just a restart the device (adb command is use when device is on & fastboot command is use when you are in bootloader)

riyan65 said:
You can use in bootloader fastboot reboot to power on your device and ADB reboot to just a restart the device (adb command is use when device is on & fastboot command is use when you are in bootloader)
Click to expand...
Click to collapse
Hi thank you for the response. I tried running that and it says reboot is not recognized as an internal or external command. I am running the portable version as i do not have admin permission due to me doing this on a library computer.

O.P.P said:
Hi thank you for the response. I tried running that and it says reboot is not recognized as an internal or external command. I am running the portable version as i do not have admin permission due to me doing this on a library computer.
Click to expand...
Click to collapse
The correct command is actually "fastboot reboot" (not only "reboot") in folder where's adb installed/extracted (perhaps even "mfastboot reboot", if you are using mfastboot instead of fastboot). However, you will need to install adb and fastboot drivers first (I strongly doubt they are already installed) so you will need to use an admin account either.

O.P.P said:
The problem is that my moto g5 power button does not work. Normally I would just use the fingerprint scanner to turn it on; but in order to put in the sims card or the micro sd I need to remove the battery. Is there a fastboot or adb command i can run. It successful booted by me putting it on the charger once in the last 2 weeks but thats it.
Click to expand...
Click to collapse
You can hold volume down and connect charging, this will open fastboot where you can either press the power button, if possible, or connect your phone to a computer and run fastboot commands

Maybe some of this works for you:
If it simply does not press, try changing the lid, since the buttons are integrated there
If they press but do nothing, try to open it and change the buttons
If you installed a Custom ROM try to return to the stock, to check if it is the ROM or physical damage

Boot loop issue: cannot get into fastboot from "no command" screen

Hey everyone,
A2 lite phone is in bootloop - allegedly (not my phone) "out of nowhere". The user does not do any fancy things like flashing, and this has not been done either.
Phone is on continuous boot loop, and sometimes (really seems randomly), the device starts up in the "no command" mode and stays there for a while. I read that we could go into fastboot mode by pressing "power button and tapping volume up key", but this doesn't do anything.
I've tried this thread: https://www.the***********.com/boot-xiaomi-mi-a2-fastboot-mode-recovery-mode/
But I'm not even getting into fastboot.
I'm almost thinking that the volume buttons are just broken, though from the feedback of the buttons this doesn't seem realistic.
EDIT: ok, now I'm somehow able to get it into fastboot.... sometimes. Now I'm here:
I switched the partition from a to b, but it still goes into bootloop. Then I switched it back to a, still bootloop. Then back to b. Still bootloop! But at least now sometimes I'm able to get into fastboot. No matter what kind of commands I'm typing in the cmd console, after about 10 seconds on the fastboot screen, the phone just reboots.
idk, it looks almost as if both partitions have the bad android 10...
Do you guys have any idea? Please let me know if more info is helpful.

You go into fastboot mode by holding Vol Down + Power button. So try holding Vol Down and Power button at the same time to go into fastboot mode. (Don't tap it)
Go here and grab the image you prefer (latest should do the trick) : https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Then go ahead and follow this guide here to flash the stock ROM : https://c.mi.com/oc/miuidownload/detail?guide=2
This will wipe the data on the device, but it seems like you have no other option at this point. Cheers.

Thanks! I've tried that now. It starts flashing the device until... after about 10 seconds, the phone reboots from Fastboot mode .

As per this page: https://twrp.me/xiaomi/xiaomimia2lite.html
I've tried to do a recovery via TWRP. If I execute `fastboot boot path/to/twrp.img` then I go from fastboot to TWRP (the teamwin logo), but right after that the phone already reboots.
https://www.xda-developers.com/how-to-install-twrp/ - I don't know if it means anything, but when I execute `adb reboot bootloader`, the console returns `error: no devices/emulators found. If I execute `adb devices`, it does not list my device. However, if I execute `fastboot devices`, my device is listed.
I installed ADB usb drivers, so when I get my phone connected in fastboot, it shows up as Android Bootloader Interfacee in device manager. So not sure what's going on here, but it's all weird.
What I'm facing is very, very similar to https://www.reddit.com/r/Xiaomi/comments/4ltzt9/xiaomi_mi_note_boot_loop_even_in_fastboot/ <-- but that thread is a bit of a dead end (and 3 y/o)...

daize said:
after about 10 seconds, the phone reboots from Fastboot mode .
Click to expand...
Click to collapse
Hmm, it should never do that, maybe it's a hardware issue that we can not fix via Fastboot ?
daize said:
As per this page: https://twrp.me/xiaomi/xiaomimia2lite.html
when I execute `adb reboot bootloader`, the console returns `error: no devices/emulators found. If I execute `adb devices`, it does not list my device. However, if I execute `fastboot devices`, my device is listed.
Click to expand...
Click to collapse
When the device is in Fastboot mode, it will only be recognized as Fastboot. Only when it's properly booted, the device can be recognized in ADB, so no issues there.
I assume your bootloader is already unlocked as you have successfully booted into TWRP. You might try EDL (Emergency Download Mode) flash as a last resort :
Download MiFlash (20160401) from here : https://www.xiaomiflash.com/download/
You're downloading that particular version because it is able to EDL flash on your phone. Install the MiFlash you've downloaded and open it, then put the phone into fastboot mode. Connect it to your PC and use this code to take the phone into EDL mode:
Code:
fastboot oem edl
After you hit enter, you will see the screen turn off and notification LED blinking, this is normal. This means the phone is in EDL mode. Open the MiFlash you've installed (likely in C:\Program Files\Xiaomi\MiPhone) and browse to the ROM location and connect the phone. Choose "Flash All" and start flashing.
After the EDL flash is complete the phone will not reboot. It will stay in EDL mode. You need to disconnect the phone from PC and hold power button (about 10-15 seconds) to boot the phone. If the phone boots properly, you can go into fastboot and connect it to PC, then use:
Code:
fastboot oem lock
to relock your bootloader. Try it and let me know. :fingers-crossed:

Thanks for the continued help!
I've followed your steps - When I run fastboot oem edl, the console returns "... okay [ 0.0202s] finished. total time: 0.022s" and the phone turns to a black screen (no notification led blinking). Then... after a couple of seconds, goes back into the boot loop .
Something maybe to note: every time that my phone starts up, it (1) shows a screen saying "Your device software can'tbe checked for corruption.Please lock the bootloader.", and then slides down to the typical "androidone" white screen before it reboots again.

daize said:
every time that my phone starts up, it (1) shows a screen saying "Your device software can'tbe checked for corruption.Please lock the bootloader.", and then slides down to the typical "androidone" white screen before it reboots again.
Click to expand...
Click to collapse
The screen with the ugly text is normal, since you have an unlocked bootloader, it's there to warn you that the device's software might've been tampered with. On the main subject though, I'm out of ideas. You might try booting the phone by holding Power + Vol Up, which should normally boot into stock recovery or wipe the data on the device. But I'm slowly beginning to think that this might be a hardware issue rather than a software issue that I can help you to fix.
Under normal circumstances, EDL flash is the way to fix any problems you might encounter with the software, that's why it's called the Emergency Download mode. But since we're past that stage, I believe I will not be able to assist you further. Hope you can fix your device my dude/dudette!

If the phone gets out of fastboot mode your phone does not get recognized from your computer. Try to delete fastboot and minimal adb and download the latest version. [https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445]
Open MiFlash, click Driver left on the top and install them.
Set path to the downloaded firmware. Now boot into fastboot, once that is done connect your USB cable to both, computer and phone. If this doesn't work try different USB-Ports and USB-cables. Some work, some don't. This might be the reason for leaving the fastboot mode.
Click refresh and see if your device appears

@marstonpear thanks for your help so far <3 @Cappucinto, thanks for chiming in! What do you mean with this: "Open MiFlash, click Driver left on the top and install them." <-- in MiFlash, I do not see an option to select driver...

@marstonpear thanks for your help so far <3
 @Cappucinto, thanks for chiming in! What do you mean with this: "Open MiFlash, click Driver left on the top and install them." <-- in MiFlash, I do not see an option to select driver...

What did change now after installing these drivers: https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445]
I did try some other USB cables. The one I've been trying triggers the windows sound for "new device successfully connected" when I boot the phone up in fastboot, and then of course gives the "device disconnected" sound when the phone then reboots. With another USB cable in this case, windows just states: "USB device not recognized". So it seems like the cable I haven't been using is defect .

I'm unable to use MiFlash at the moment so I can't explain the whole procedure with installing the drivers in MiFlash. But there has to be something like "Install > Drivers" or something. Maybe someone else can help out.
Try to use the working cable again, open a command prompt and type: fastboot devices
Then wait for an answer, post it here and see if the phone reboots again or if it stays in fastboot

daize said:
Hey everyone,
A2 lite phone is in bootloop - allegedly (not my phone) "out of nowhere". The user does not do any fancy things like flashing, and this has not been done either.
Click to expand...
Click to collapse
The response by marstonpear below makes sense.
marstonpear said:
You go into fastboot mode by holding Vol Down + Power button. So try holding Vol Down and Power button at the same time to go into fastboot mode. (Don't tap it)
Click to expand...
Click to collapse
Although u shd consider this link, i tried to arrange it step by step:
https://forum.xda-developers.com/sho...php?p=79365091
Follow the instructions, as dat was how i revived mine. Hopefully it may help u.
Note; wen using twrp, preferably use " twrp - offain "
Miflash tool:
Link 1: https://www.xiaomiflash.com/download/
Preferably use Link 1 & choose either 2016, 2017 or 2018 versions. They come preloaded with the drivers u need
Link2: https://xiaomibuzz.com/downloads/download-xiaomi-mi-firmware-flash-tool-latest-version-2018.html
Lets know how it goes

Cappucinto said:
I'm unable to use MiFlash at the moment so I can't explain the whole procedure with installing the drivers in MiFlash. But there has to be something like "Install > Drivers" or something. Maybe someone else can help out.
Try to use the working cable again, open a command prompt and type: fastboot devices
Then wait for an answer, post it here and see if the phone reboots again or if it stays in fastboot
Click to expand...
Click to collapse
Hey there When I get into fastboot and run `fastboot devices`, a code returns <tab> fastboot.
... and then the phone restarts I'm trying but I guess I'm beyond the stage of being upset, haha.
@agbadino https://forum.xda-developers.com/sho...php?p=79365091 <-- that first link seems to be broken, could you check again? I'd love to try your steps!

daize said:
@agbadino https://forum.xda-developers.com/sho...php?p=79365091 <-- that first link seems to be broken, could you check again? I'd love to try your steps!
Click to expand...
Click to collapse
Sorry bout d previous link. I believe this shd take u directly to the tutorial:
https://forum.xda-developers.com/mi...tboot-mode-t3920925/post79365091#post79365091
remember to use "twrp offain for daisy". It works better than the regular twrp for daisy
It my take and procedure that worked for me at the time. Good luck tho

Thanks! Sadly, when I get to the `fastboot oem edl` step, it fails. I get into fastboot, I quickly enter `fastboot oem edl`. CMD says finished, the screen turns off. I immediately refresh in MiFlash (COM3 is the device), I start flashing. After 4 seconds, the device turns off (windows sound "device disconnected"). The flashing runs for a total of 7-9s says "the operation completed successfully.(0x000000000: cmd <?xml version="1.0" ?><data .. etc etc
So I don't really know what to do if I can't get into EDL mode .

daize said:
Thanks! Sadly, when I get to the `fastboot oem edl` step, it fails. I get into fastboot, I quickly enter `fastboot oem edl`. CMD says finished, the screen turns off. I immediately refresh in MiFlash (COM3 is the device), I start flashing. After 4 seconds, the device turns off (windows sound "device disconnected"). The flashing runs for a total of 7-9s says "the operation completed successfully.(0x000000000: cmd <?xml version="1.0" ?><data .. etc etc
So I don't really know what to do if I can't get into EDL mode .
Click to expand...
Click to collapse
Try getting another chord and try again.

Tried some other cables. Every time I run fastboot oem edl, it keeps saying "finished", and then reboots the phone in about 5 seconds. One time, it said "Catastrophic failure" as "status" for the flashing.
Otherwise, it most often says "The operation completed successfully.(0x00000000: cmd <?xml version="1.0"?><data><patch SECTOR_SIZE_IN_BYTES="512" byte_offset="16" filename="DISK" physical_partition_number="0" size_in_bytes="4" start_sector="NUM_DISC_SECTORS-1." value="CRC32(NM_DISK_SECTORS-1.,92)" what="Update"/></data>)
But then still continues in the bootloop...

Can't access Fastboot mode/ADB

So, I flashed Derpfest A12 ROM, It boots fine but gets stuck on "getting your Android 12 Ready" screen with the animation. I can access wifi and visiblity options but not settings. I flashed TWRP from the official website to install the recovery. But now when I reboot and press Volume Down, TWRP is stuck on boot animation. So I thought just reset using fastboot and start again and pressed volume up and power button but it does NOT work. I tried the volume buttons again in the rom [i can change volume in the starting screen] and they are working. I can press volume down and power button to reboot into recovery and it works fine but gets stuck. So, I just want to have access to adb or fastboot to reset this phone but neither seems possible. I Cant enable advanced reboot in the starting screen. Fastboot doesnt work. ADB not recognizing as it is a new rom and havent enabled it [i enabled in the previous rom]. Thanks for you Help in Advance!
P.S. I have tinkered POCO F1 fairly so I am not totally new to this scene!
EDIT: Thanks for all the replies! But I solved the problem, Idk how but i got access to fastboot mode after some tries and reflashed everything and now it works, also I use linux and the adb drivers and fastboot were in repos so it was easy.

hello,
I am a novice and use a translation tool to write to you (sorry if there are errors...).
Ok I already installed roms (but a long time ago on a OnePlus One...
I have an OP5T, I want to install lineage Os 19.1 on it.
I followed the tutorial on the lineage wiki.
I installed ADB and fastboot well, as well as universal adb driver.
I'm on windows 11, it works.
I enabled debug mode
The adb reboot bootloader command works, so the tel is well seen by the pc and the tel restarts in fastboot mode.
Then nothing, no command (oem unlock) works, the computer does not seem to see such after restarting in fastboot mode.
I read some topic on the net that say that the phone must be in "battery charging" mode and not "file transfer". Me to be visible by adb I have to put it in file transfer mode, otherwise it is not seen.
If I put in recharge mode, same thing to do.
Do you have a tip or should I give up?

ezivoco_163 said:
The adb reboot bootloader command works, so the tel is well seen by the pc and the tel restarts in fastboot mode.
Then nothing, no command (oem unlock) works, the computer does not seem to see such after restarting in fastboot mode.
I read some topic on the net that say that the phone must be in "battery charging" mode and not "file transfer". Me to be visible by adb I have to put it in file transfer mode, otherwise it is not seen.
If I put in recharge mode, same thing to do.
Do you have a tip or should I give up?
Click to expand...
Click to collapse
You need to install not just the adb drivers, but the fastboot ones as well, see this guide for example. This driver is the one needed for fastboot.
My devices have always been in file transfer mode btw, I've never heard of it needing to be in charging mode only.

No, you don't have to be in "charging only" vs "data transfer".
Still, those of us who distain to be plebian keep our devices in "charging only" (with ADB on) as MTP is beneath our contempt.
(Actually, the problem is that the USB VID/PID sometimes changes with each mode and that you may not have a driver loaded for ADB only.)

Nimueh said:
You need to install not just the adb drivers, but the fastboot ones as well, see this guide for example. This driver is the one needed for fastboot.
My devices have always been in file transfer mode btw, I've never heard of it needing to be in charging mode only.
Click to expand...
Click to collapse
Renate said:
No, you don't have to be in "charging only" vs "data transfer".
Still, those of us who distain to be plebian keep our devices in "charging only" (with ADB on) as MTP is beneath our contempt.
(Actually, the problem is that the USB VID/PID sometimes changes with each mode and that you may not have a driver loaded for ADB only.)
Click to expand...
Click to collapse
ok thanks, i a going to try this