Hi all,
think i bricked/ defected my Pace today. The idea was a mod with german language so i began to read here at xda for info. I'm on iOS now but modding on Android is nothing new for me, i modded some mobiles before, everthing workedtill today. I unlocked the bootloader and installed the mod, something went wrong i think, maybe i tried an incorrect image or something else, i don't know. After installing the watch wanted to update via OTA an after that it was shown as a Stratos in the Huami Amazfit Tool, sn was NULL an so on. The watch booted to os but the app was not able to read the QS Code for connection, touch doesn't work...
I can't say which ways i tried the last 6 to 8 hours to repair it and now i'm sure there is no bootloader/ software anymore on the watch. It starts with Amazfit Logo and stops with "No Command" & and the triangle. The only way to connect is in Fastboot, which shows chinese signs at the bottom of the display. There is no connection possible on ADB or otherwise.
Is there any way to get back the software on my watch? Maybe download mode which starts from my pc or something else? I'm on win 10 here, there is no linux machine or something else.
Thanks for reading
If you can get to fastboot and recovery, you have not deleted the bootloader.
Follow this guide: https://forum.xda-developers.com/smartwatch/amazfit/tutorial-unbrick-huami-amazfit-t3547300
Quinny899 said:
If you can get to fastboot and recovery, you have not deleted the bootloader.
Follow this guide: https://forum.xda-developers.com/smartwatch/amazfit/tutorial-unbrick-huami-amazfit-t3547300
Click to expand...
Click to collapse
Hi,
i tried this yesterday for about 10 to 15 attempts, but after step 4 there is no adb connection for step 5 and adb commands doesn't work. Getting the watch in fastboot is no problem anymore for me after last night
You have flashed Stratos firmware on your Pace, that's why touch didn't work. If the unbrick tutorial didn't work for you, then you should check your drivers: both drivers for adb and fastboot (they are different) should be installed and working properly. Sometimes you must re-connect the watch for the computer to detect it when the mode change, I usually keep Device Manager when I am using Windows to check this.
Or try AmazeROM installer, it has an option to start flashing from fastboot and it will guide you through the process.
Hi all,
sorry for my later post but under week i have no time for doing things like this here.
I checked adb and fastboot on the pc, installed system wide and works, fastboot drivers seems to be ok, but i have no idea how to check adb drivers. It's all the same, if i try this guide https://forum.xda-developers.com/sma...azfit-t3547300 or if i install amazeos with installer. The watch is recognized in fastboot but afterwards switching to adb there is no new connection, it's still in fastboot and does not switch to anything, i can restart it when amazeos installer script runs but nothing happens and if i let it run for about three hours the watch is still in fastboot and nothing happens there. In the device manager i see only an ADB Testing Device when in fastboot connected, on adb nothing happens there.
I tried everything on a clean win 7 machine, in this case the watch won't even recognize, so i could't run an installer or try to use the unbrick guide.
Just for information, it was Stratosfied which killed my watch in my mistake, but after that i think i deleted all with Amazfit Tools for doing the worst case for me here an unplugged it before reinstalling something else.
I attached some pics of the watch, first is after starting and directly after Amazfit logo, second is in fastboot with this method https://forum.xda-developers.com/sm...tches/amazfit-boot-fastboot-directly-t3546829, Point two there is not reachable, only point one fastboot, but in it i can't do anything though.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And for information, every fastboot command will be determind with "The command is not allowed"
Related
My $20 hoot huawei p20 pro CLONE (here a link /w info about the phone with false specs full of bugs)https://www.freebrowsinglink.com/hoot-p20-pro/ got bricked a week ago after I left it connected to a Windows computer with internet access.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The story starts with when I tried to root the phone with KingoRoot, eventually ads started popping up, facebook, dating or porn sites and malware like that. I uninstalled KingoRoot and installed some anti spam software like avg and avast, but that did not help, ads kept coming. The phone has Android 5.1 Lollipop on it and after I left it connected to a Windows Laptop, like I said before, error messages with 'UI has stopped working' and 'other stuff stopped working' started popping up in a whole sequence of error messages so it rendered the phone unusable.
Next I started messing with it via platform-tools and wanted to flash TWRP on it and eventually a different OS like Lineage, but now the phone is totally shot and I can not use recovery any longer. The only thing that seems to work is fastboot mode, but it doesn't let me install a custom recovery like TWRP. Unlocking the bootloader seems to work, like shown in the attached pix, but other commands like 'fastboot devices' give a funny looking device name: '0123456789abcdef'. Other commands like fastboot erase -w and oem info show failure only; reboot-bootloader works and so on.
Any advice on this one? I'm just trying to learn about phones and android and this seems like a perfect opportunity, unless this cloned smartphone is piece of a worthless brick, which most assuredly is.
Try to flash corect stock firmwares for your device , check which one is yours .
https://hellostockrom.com/huawei-clone-p20-pro/
Yo TeddyLo, I tried already a similar website and after 2 hours of downloading through a slow internet connection the files were encrypted WinRaRs and probably useless anyway...thanks bro.
Hard Bricked Hoot P20 pro Clone
Yo, Teddy Lo, I had been busy last few days and tried to follow your suggestion, but to no avail. The device is now a hard brick, it does not come on at all, no more fastboot mode, or battery status logo when off and loading for that matter. It all happened when I tried to flash this file 'DOOGEE-Shoot_2-Android7.0--20170517' with SP Flash Tool. The device downloaded the files, but is completely dead now.
I am trying to do format and download with different ROMs for whatever is available on the internet for a P20 Pro clone phone, and phone manages to establish connection through USB with SP Flash Tool, but every time I get the following error message:
How can I fix this problem? Thanks.
Clone_Cat said:
Yo, Teddy Lo, I had been busy last few days and tried to follow your suggestion, but to no avail. The device is now a hard brick, it does not come on at all, no more fastboot mode, or battery status logo when off and loading for that matter. It all happened when I tried to flash this file 'DOOGEE-Shoot_2-Android7.0--20170517' with SP Flash Tool. The device downloaded the files, but is completely dead now.
I am trying to do format and download with different ROMs for whatever is available on the internet for a P20 Pro clone phone, and phone manages to establish connection through USB with SP Flash Tool, but every time I get the following error message:
How can I fix this problem? Thanks.
Click to expand...
Click to collapse
hi, i had the same problem, and i found this forum , it solved the issue ....
forum.gsmhosting.com/vbb/f296/clone-welcome-huawei-p20-pro-firmware-2574709/
Regards
Hi,
For a few weeks now, my stratos 3 doesn't work despite all my efforts. The problems started to occur on 4.2.5.0.
When I boot the watch in smart mode, I only see a black screen. But the watch can be linked to the phone in bluetooth and adb commands are working fine.
I can restart the watch in ultra mode using adb reboot mcu and it works fine in that mode.
I tried to wipe data with adb reboot wipe, same
I tried to install the stock firmware (https://forum.xda-developers.com/smartwatch/amazfit/fw-tool-stock-global-international-t4031153), no change (even with older FW)
I tried the PACEficator Custom ROM (https://forum.xda-developers.com/smartwatch/amazfit/paceficator-project-stratos-3-multi-t4033223), it worked for 2 minutes, then the problem reappeared.
I tried to flash the watch with the ingenic tool (https://forum.xda-developers.com/smartwatch/amazfit/tutorial-ingenic-cloner-tool-aamzfit-t3908237), same...
At this point I don't know what to do, except only using the watch in ultra mode.
Is my SD card damage? Or is it another component ?
If you have any lead, idea or insight, I would take it willingly :fingers-crossed:
elimeXCI said:
Hi,
For a few weeks now, my stratos 3 doesn't work despite all my efforts. The problems started to occur on 4.2.5.0.
When I boot the watch in smart mode, I only see a black screen. But the watch can be linked to the phone in bluetooth and adb commands are working fine.
I can restart the watch in ultra mode using adb reboot mcu and it works fine in that mode.
...
Click to expand...
Click to collapse
Hi! I have the same problem that I encountered in the same period ( the 4th May FW 4.2.5.0) but in my case the watch optimizes app for 20 minutes (15% of battery), then gives QR but can not pair the mobile. I skipped QR from adb and the watch boots in Smart mode but it works wery slowly and shows big charge leak. In my case i can pair with earphones but not with the mobile.
I did all to pair but adb shell dumpsys bluetooth_manager says:
enabled: false
state: 10
address: D8:80:3C:3B:71:F3
name: Watch
Bluetooth Service not connected
I upgraded with original OTA update to 4.2.6.0 - useles
I unlocked bootloader and flashed with Saratoga moded FW 4.2.6.0 - useless
Now thinking to downgrade or eraze and unbrick.
Taking into consideration mentioned above I don't think our problem is a hardware one.
Hello,
Little update...
I decided to downgrade to 4.2.2.1 to see what would happen.
But first I started to go into fastboot mode and then I rebooted the watch. A message that I had never seen before appeared :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I don't even know what is the launcher , so I closed it.
And then, :angel: :angel: :angel: the watch started to work normally.
I don't know what happened, and if the problems that I had will be coming back. But I'm praying that it won't.
So I'm now in 4.2.6.0 and everything seems to be working fine.
You're right Godfly, That's not a hardware issue.
elimeXCI said:
Hello,
Little update...
I decided to downgrade to 4.2.2.1 to see what would happen.
But first I started to go into fastboot mode and then I rebooted the watch. ....
I don't even know what is the launcher , so I closed it.
And then, :angel: :angel: :angel: the watch started to work normally.
I don't know what happened, and if the problems that I had will be coming back. But I'm praying that it won't.
So I'm now in 4.2.6.0 and everything seems to be working fine.
You're right Godfly, That's not a hardware issue.
Click to expand...
Click to collapse
Congrats! I downgraded to 4.2.2.1 - useless. Now upgrading to 4.2.4.0. I am afraid will have to to flash the watch with the Ingenic Cloner tool and dawngrade like you.
Don't go to 4.2.6.0 it's so bugged 4.2.5.0 is ok
Hi there! I need some help, I am trying to root my device and need a boot.img, but I cannot find a Rom for the x9 anywhere online.
This is my first time doing this, I got this phone just to mess around with rooting. But maybe I bought a bad phone for it.
If there are no Flash Roms online, what are the next steps? Can I use a Rom for the e9 which released alongside this phone? Sounds like it wouldnt work.. but IDK.
Looking for help from the experts ^^
Any help is appreciated.
Finally found one! Took over 2 hours to download a 2gb file O,O but it's finally done.
Now I am having problems getting into bootloader mode.
In developer mode with both OEM unlocking and USB debugging enabled.
Used the correct cmd prompt (adb reboot bootloader) but the phone just restarts.
I've tried restarting while holding the volume buttons.
VOL Down = Factory Test Mode, nothing works as expected there.
VOL UP = A boot menu letting me select from ~10 options, one of them is Boot to Bootloader. Selecting that simply boots normal, nothing special.
I have followed three guides:
How TO Root Vodafone Smart X9 Magisk without TWRP Recovery
If your Smart X9 is rooted using Magisk without TWRP Recovery. You can control a lot of features such as you can remove unwanted software.
www.getdroidpro.com
Vodafone Smart E9 Unlock Bootloader with Fastboot Method
How to unlock bootloader on your Vodafone with Fastboot Method. You can install custom ROM, custom recovery, kernel, flash all data
www.mobilewithdrivers.com
All seem logical enough, many similarities between them. I just cannot get into fastboot mode.
I've seen LOADS of threads with this same problem on this forum. And none of them have any solutions. So I think this is the end of the road. If nobody has figured it out .. then I am just out of luck I guess?
HalpNeeded said:
Forget, your phone have only 3 buttons
Click to expand...
Click to collapse
Hi @joke19 !
I havnt seen any of the guides mentioning needing a certain amount of buttons :O
How does that factor in - does that mean it cannot be rooted for some reason?
Still having this problem, and I have followed a lot of guides to the letter. I cant see what I am doing wrong. Here's where I am:
Phone is visible on device manager and the drivers are up-to-date.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PC is fully up to date on Windows 10.
I've got the lastest up-to-date version of platform-tools.
I'm using USB2.0 with the correct wires.
The phone is in developer mode with USB Debugging and OEM unlocking enabled.
I'm using the correct command lines. adb devices & adb reboot bootloader work as expected.
But none of these will work: fastboot devices, fastboot flashing unlock, fastboot oem unlock.
I just get < waiting for any device >
Can anyone help figure this out? I must be doing sooomething wrong. Everything online says its a driver issue, but then again, all the guides on how to fix that driver issue have been followed and completed. The first bullet with the image should also sort of verify that.
Praying some wizard out there has the knowledge I need to get this working! ^^
HalpNeeded said:
Still having this problem, and I have followed a lot of guides to the letter. I cant see what I am doing wrong. Here's where I am:
Phone is visible on device manager and the drivers are up-to-date.
View attachment 5671635
PC is fully up to date on Windows 10.
I've got the lastest up-to-date version of platform-tools.
I'm using USB2.0 with the correct wires.
The phone is in developer mode with USB Debugging and OEM unlocking enabled.
I'm using the correct command lines. adb devices & adb reboot bootloader work as expected.
But none of these will work: fastboot devices, fastboot flashing unlock, fastboot oem unlock.
I just get < waiting for any device >
Can anyone help figure this out? I must be doing sooomething wrong. Everything online says its a driver issue, but then again, all the guides on how to fix that driver issue have been followed and completed. The first bullet with the image should also sort of verify that.
Praying some wizard out there has the knowledge I need to get this working! ^^
Click to expand...
Click to collapse
did you manage to get this working?
Hi Folks,
I have a Xiomi Note 10 (camellian), unlocked and has USB Debugging switched on.
No matter what I do, I can't install TWRP or Orangefox because it fails with "FAILED: Too Many Links"
I've followed so many guides on how to fix this and they all fail. I tried to flash the stock rom with Mi Flash and that failed too (Constant "Unhandled exception" error as it doesnt seem to want to install drivers and wont continue without them). I've manually updated the ADB drivers for the Note and that worked fine. Mi Pc Suite doesnt recognise my phone unless i "Update your phone before you connect" (The phone is fully updated)
Please, for the love of the baby jesus and the little donkey, tell me what I can do to try and figure out what the smeg is going wrong
EDIT:
Ive changed ports/cables, tried compatibilty on programs, reinstalled ADB drivers
trying "fastboot flash boot recovery.img" (for orange fox) throws up "FAILED: remote: size too large"
hellfirehound said:
Hi Folks,
I have a Xiomi Note 10 (camellian), unlocked and has USB Debugging switched on.
No matter what I do, I can't install TWRP or Orangefox because it fails with "FAILED: Too Many Links"
I've followed so many guides on how to fix this and they all fail. I tried to flash the stock rom with Mi Flash and that failed too (Constant "Unhandled exception" error as it doesnt seem to want to install drivers and wont continue without them). I've manually updated the ADB drivers for the Note and that worked fine. Mi Pc Suite doesnt recognise my phone unless i "Update your phone before you connect" (The phone is fully updated)
Please, for the love of the baby jesus and the little donkey, tell me what I can do to try and figure out what the smeg is going wrong
EDIT:
Ive changed ports/cables, tried compatibilty on programs, reinstalled ADB drivers
trying "fastboot flash boot recovery.img" (for orange fox) throws up "FAILED: remote: size too large"
Click to expand...
Click to collapse
i see none TWRP and O.F for camellian, can you post the links +Miflash log?
The TWRP is unofficial https://forum.xda-developers.com/t/unofficial-twrp-camellia-camellian.4304717/
There is no MiFlash log anywhere. Sorry im new to this
I think I need to flash the original rom before trying to install a recovery rom
hellfirehound said:
The TWRP is unofficial https://forum.xda-developers.com/t/unofficial-twrp-camellia-camellian.4304717/
There is no MiFlash log anywhere. Sorry im new to this
Click to expand...
Click to collapse
The Mi Flash logs are in the Miflash Log folder (post the last + or - 20/22ko
This twrp seems not to work (closed thread).
Try the command: fastboot boot twrp.img
The phone will reboot in TWRP after that go to Advanced > Flash Current TWRP
And what do you want to do with the TWRP, your device has a Mediatek soc and there is little or no development for Xiaomi with a Mediatek soc.
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It looks like a mediatek device.
Never Mind, ill keep the phone as is. Thanks for trying to help
Download and extract to the root of the disk.C:/platform....
https://developer.android.com/studio/releases/platform-tools
rename the Twrp to twrp.img
Put it in the Platform tools folder
Execute the command from this folder
Since no custom is available for your phone I guess you want to update or downgrade for these 2 cases use Miflash not TWRP.
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
this error
is frequent with certain version of W10.
Disable driver verification.
.
Hello. I recently brought back my x820 to life. I need a phone.
It had TWRP and a custom rom. I tried to wipe and I actually wiped too much. So I had to install stock rom again because for some reason, lineage gave me an error at install (like it wasn't the right rom but it really was since I found it here https://download.lineageos.org/x2).
So I try to install TWRP again: twrp-3.7.0_9-0-x2.img found here: https://eu.dl.twrp.me/x2/
I launch ADB on a cmd prompt
- adb devices (List of devices attached e816a730 device). Super it's working and recognized
- adb reboot bootloader (phone miraculousely reboots in fastboot mode - YAY)
- fastboot devices ....... goes back to c:\ADB .... no devices found
So I reinstall ADB (from here: https://forum.xda-developers.com/t/...vers-15-seconds-adb-installer-v1-4-3.2588979/). Y to all, reinstall drivers and everything. Reboot PC. Do everything again.....still the same weird fastboot < waiting for devices >.
Devloper options are enabled.
OEM is unlocked.
USB debugging is ON.
Cable has been changed.
Cables have been plugged on USB 2.0 ports (in the back), on 2 different computers.....still the same thing.
*#*#76937#*#* typed in and AT ports enabled.
Could someone have the kindness to help me figure out what's wrong with what I'm doing? I'm usually pretty comfortable with rooting, flashing etc....but I'm clueless here.
Thanks for any help or input.
First off, please install the Android SDK Platform Tools [instead of 15 seconds ADB installer]
Once done, install the Fastboot Drivers on your PC.
The ADB Tools [Platform Tools, 15 seconds installer, etc] don't have Fastboot binaries, so you will only be able to execute ADB-related commands and not the Fastboot ones.
Thanks.
I downloaded the fastboot drivers. But I can't seem to install them. In fastboot mode, I see this in my device manager:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I follow instructions from here: https://www.droidwin.com/how-to-install-fastboot-drivers-in-windows-11/ (your link). Although I'm on windows 10.
When I try to update driver, whatever I do, I get this error:
Which means "the folder doesn't contain any compatible driver for your device. If it contains a driver, make sure it can work for x64 computers".
So I'm pretty sure it's a driver problem. Is there a way to completely uninstall previous drivers and go from scratch again? Or any cleverer solution?
Try removing the faulty device then disable driver signature enforcement and install drivers.
https://avalonsciences.com/wp-conte...Signature-Verification-on-Windows-8-or-10.pdf
Thanks to both of you. Especially to you binary who pointed me on the right tutorial. I was doing something wrong when updating drivers in fastboot mode. I chose a device before locating the .inf file.
YES
NOOOOOOOOOOOOOOOOOOO
The bottom screen was taken from here: https://forum.xda-developers.com/t/...vers-15-seconds-adb-installer-v1-4-3.2588979/
"Show all devices" MUST be selected before going a step further apparently. All 3 drivers were installed flawlessly. TWRP was flashed successfully. I just need to figure out why it's still the old stock recovery showing up when I VOL+ and POWER start.
Cheers guys.
lucky24i said:
I just need to figure out why it's still the old stock recovery showing up when I VOL+ and POWER start.
Click to expand...
Click to collapse
Glad that you were able to rectify the driver issue. As far as TWRP is concerned, as soon as you flash it, boot straight to it [without booting to the system] and then check out the result.
In some instances, the device tends to replace TWRP with stock recovery upon boot. So avoid booting to the OS and use fastboot reboot recovery to straightaway boot to TWRP after flashing it.
Thanks. Working great