Related
So i messed up when trying to update my watch and somehow deleted the firmware so my watch bootloops upon start-up, any way to fix this?
Im have the same problem. Im stuck in bootloop after trying to flash custom kernel. I can not rech recovery. Not original recovery or TWRP. Fastboot works. What to do?
Is there any restore image to flasH?
Here are three solutions in one answer, because you did not give quite enough info.
First, try holding the button on boot up. Hopefully that will get you into usb mode. If it works, download the sony software, and go to the help section, and download and install the update.
Option two,
Code:
adb reboot recovery
Or, download the version of twrp for your build as well as your original image, and use fastboot.
Code:
Fastboot boot twrp.img
then use twrp to install the factory zip. You can do this directly in fastboot too, but it is more difficult because fastboot only installs each image separately. If I knew what versions of software you had, I could help you find the images you need.
I have tried both fastboot flash and fastboot boot for both original recovery and also TWRP, but non of the recoverys will boot, not even with Fastboot boot.
The command lines says OK on my PC, It is getting downloaded, and it says it is booting / flashed [OKAY].
But all I get on my Smartwatch 3 is bootloop.
My Smartwatch 3 is OEM unlocked. I even tried to lock it, and unlock it again.
I have full contact with fastboot on my PC, all the commands are taken in and seems to work, but my smartwatch won't boot no system or no recoverys. Only USB-mode and Fastboot mode...
I have also tried to clear cache and userdata in fastboot after OEM Unlock.
I will try the Sony Software now. That is my last way out I Think.
The Sony PC Companion software from sony's website worked for me to save my smartwatch from bootloops . I just did a update and installed it over what was already on the smartwatch.
Thanks lekofraggle for quick answeres. I had no idea the PC Companion had this feature.
SimDroid, I am glad that helped. If it hadn't, the next step would be to flash an image through fastboot. That would be scary, because it sounds like your boot loader was corrupt. It's nice to know the usb and PcCompanion piece still worked. Another reason this watch is incredible.
Cheers.
does anyone have a download for the original (5.0.2 im guessing) ROM for this watch? I want off the rubbish 5.1.1 update before i am forced to sell the watch due to the terrible battery
The smartwatch works as it should now, original recovery and everything is back!
So, if i may go back to where it started?
I noticed now that I flashed the custom kernel for the watch built for wrong firmware. Im on 5.1.1, and there doesnt seem to be a developed shared kernel with all four cores unlocked for it.
Im also interested in where I can find those images to flash via fastboot as you mentioned lekofraggle
Hi and happy new year
I think there is a problem when i have update my OnePlus 3 on Nougat and root it because now the OnePlus3 don't work.
The twrp don't work, only fastboot work.
Now when i boot the OP3, i have a black screen with this lines :
md5 checksum
cache failed
boot failed
boot aging failed
system failed
recovery failed
modem ok
bluetooth ok
adp ok
sec ok
.....
I can boot to fastboot, i have on my pc the zip of OnePlus3.OS.3.2.8.zip and OnePlus3.Nougat.zip.
Do you think is there any issue or is blocked ?
Thanks for help
Use Brick Guide.
I had the same issue since updating to OOS 4. Caused me massive headache today and basically I thought my device was bricked. I had to use a 3.2.6 zip and corresponding Rom via MSKIP toolkit and fastboot/adb to get my device working again. After more than a decade of flashing ROMS this was my biggest fXXk up yet. I feel that TWRP recovery (even the modified ones) are not yet compatible with this update in some way. I constantly got encryption/dm verity issues even when using the modified software. Sadly for now I have gone back to pure stock (Rom/Recovery) to get my device working and updated to Android 7. To be honest I am afraid to go down the custom recovery root on this device for a while due to the headache it caused me today. I can see a few posts of people having issues so this cant be isolated.
Thanks for help
I will success to reinstall the OP3 with nougat and root is ok ^^
It was long but all is ok and i was afraid to send the phone on sav.
So i use the method 2 in this link : https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
And i install again the stock rom 3.2.8 with "adb sideload" on fastboot and i install the Maj OTA with vpn.
I install the last TWRP here : https://forum.xda-developers.com/devdb/project/dl/?id=21835 and the last Supersu here : https://download.chainfire.eu/1017/SuperSU/SR1-SuperSU-v2.79-SR1-20161221223537.zip and all it's ok now
I will afraid too like you because my phone was brick when i root nougat.
But i tried and i'ts ok now, i don't know why the first time it's not working.
Hi !
Before tonight, i was on a lineageOS 7.1 and i tried to flash the stock Oreo android that i downloaded on google websites. My bootloader was unlocked, so i just used fastboot and flashed all. I had TWRP installed.
It worked. Then i had the stock 8.0.0 with no TWRP anymore ( and i forgot to re-flash it ). Then, i dunno what passed in my head, after the first reboot, i decided to **lock my bootloader**.
And now i'm in a bootloop on the vendor image ("Google"), with a LOCKED bootloader ( so no fastboot anymore ) and i cant do anything. I forgot to go to paramters and allow the bootloader to be unlocked before rebooting...
The only access i got is via adb in the stock recovery mode, but i'm not enough aware of wath i could do with that. I tried abd sideload with the same .zip, but it didnt worked. I get stuck on the same Error when the phone tries to verify the conformity of the flash.
So :
1° Cant use fastboot to take me out of here because bootloader's locked.
2° No TWRP anymore, only the stock android recovery.
3° Bootloop so i cant launch the device.
4° My only in is adb fastboot.
5° My build number is OPR6.170623.013
What do you think i could / should do to take me out of here ? I'm taking anything that allows me to boot the phone.... For what i saw, i'm kinda thinking it's bricked, but i still got hope. I'm comming to you because i'm desperate
Thanks for your advices.
useful threads
that nobody ever bother checking out
Very usefull post. Thank you very much. I'm still stuck but i've posted there so i'll hope someone will come.
This post can be closed
Hello everyone,
My Mi A2 Lite just died today. I was on stock 8.1 rooted and suddenly it freezes so I rebooted it and I got stuck on Android One logo WITHOUT ANY animation.
I tried to boot into recovery via adb but I get stuck on TWRP logo. I tried to flash fastboot image but nothing changes....
I really need help because I'm out of options
pocchio said:
Hello everyone,
My Mi A2 Lite just died today. I was on stock 8.1 rooted and suddenly it freezes so I rebooted it and I got stuck on Android One logo WITHOUT ANY animation.
I tried to boot into recovery via adb but I get stuck on TWRP logo. I tried to flash fastboot image but nothing changes....
I really need help because I'm out of options
Click to expand...
Click to collapse
Two quick questions:
1.The phone died on its self without your intervention or...?
2.Have you tried to flash the stock firmware via MiFlash , while the phone is in edl mode(the command is: fastboot oem edl)?
1) yes, it got stuck so I rebooted it
2) I tried flashing with MiFlash tool in fastboot mode. When I connect it in fastboot edl the mi flash tool sees it as COM and therefore I’m not able to flash it.
I’m I doing something wrong?
pocchio said:
Hello everyone,
My Mi A2 Lite just died today. I was on stock 8.1 rooted and suddenly it freezes so I rebooted it and I got stuck on Android One logo WITHOUT ANY animation.
I tried to boot into recovery via adb but I get stuck on TWRP logo. I tried to flash fastboot image but nothing changes....
I really need help because I'm out of options
Click to expand...
Click to collapse
pocchio said:
1) yes, it got stuck so I rebooted it
2) I tried flashing with MiFlash tool in fastboot mode. When I connect it in fastboot edl the mi flash tool sees it as COM and therefore I’m not able to flash it.
I’m I doing something wrong?
Click to expand...
Click to collapse
I think you are confusing some things here; adb is not an option now so you can´t boot device normally and also you said "fastboot edl" but they are different modes.
While in fastboot how did you try booting to TWRP image? (you said through adb but this is not right)
Can you get to fastboot? (hold vol down while booting, should see a rabbit on the screen)
pocchio said:
1) yes, it got stuck so I rebooted it
2) I tried flashing with MiFlash tool in fastboot mode. When I connect it in fastboot edl the mi flash tool sees it as COM and therefore I’m not able to flash it.
I’m I doing something wrong?
Click to expand...
Click to collapse
When your phone is in EDL mode(you won't be seeing any logo on your phone ,only black screen) it's absolutely normal to see the device as COM port , because the device is in another factory mode. And there is no problem flashing stock ,when your phone is seen as COM port. So if you can't flash the stock firmware in fastboot mode or EDL mode , maybe you have a hardware issue. To be sure -take a screenshot of the error in MiFalsh when the phone is in edl Mode (seen as a COM port) and you try to flash the stock firmware.
Ok, I understand the difference between EDL (black screen) and Fastboot mode. I can get in both mode. I tried to flash fastboot stock rom (taken from the thread in xda) and everything goes smoothly, but it stays in fastboot mode at the end and when I send the command fastboot reboot it gets stuck again on the Android One logo (no animation).
When I tried the EDL mode, mi flash returns something missing (I will post the screenshot asap) and it seems like is not the right thing I'm trying to flash or something similar (I will post more information as soon as I can). (I'm trying to flash the same fastboot roms found in xda)
So, just to make sure I'm doing the right thing, where I can find the stock firmware to flash?
Thanks again for your help!
pocchio said:
Ok, I understand the difference between EDL (black screen) and Fastboot mode. I can get in both mode. I tried to flash fastboot stock rom (taken from the thread in xda) and everything goes smoothly, but it stays in fastboot mode at the end and when I send the command fastboot reboot it gets stuck again on the Android One logo (no animation).
When I tried the EDL mode, mi flash returns something missing (I will post the screenshot asap) and it seems like is not the right thing I'm trying to flash or something similar (I will post more information as soon as I can). (I'm trying to flash the same fastboot roms found in xda)
So, just to make sure I'm doing the right thing, where I can find the stock firmware to flash?
Thanks again for your help!
Click to expand...
Click to collapse
Here is the stock firmware from Xiaomi site:
https://en.miui.com/getrom-354.html?m=yes&mobile=2
Don't worry that it says MIUI , the firmware is Android One , they just forgot to change the name from MIUI to Android One , I have already tried it ,and I can confirm that it's 100% stock Android One firmware , good luck!
Ok I performed the flash but the error i get is new.
I get the error ACK count don't match!
I tried the version
daisy_global_images_V10.0.9.0.PDLMIXM_20190514.0000.00_9.0_f9d0c739e0.tgz
pocchio said:
Ok I performed the flash but the error i get is new.
I get the error ACK count don't match!
I tried the version
daisy_global_images_V10.0.9.0.PDLMIXM_20190514.0000.00_9.0_f9d0c739e0.tgz
Click to expand...
Click to collapse
I will give a solution in a minute
EDIT: Are you sure your bootloader is unlocked? (fastboot oem unlock)
You have two choices , you need to find an older version of MiFlash beta , i'll give you a video :
https://m.youtube.com/watch?v=-7O1Svib14g
In the video description you can find a link for the MiFlash beta ,I hope it helps.
If not , you'll have to consider the Testpoint unbrick method , there are several guides.
OK, thanks to the use of the BETA version I was able to flash the rom but unfortunately I still get the same AndroidOne logo without any animation....
I really don't know what to do now...
Yes the bootloader is unlocked and I checked with fastboot getvar
pocchio said:
OK, thanks to the use of the BETA version I was able to flash the rom but unfortunately I still get the same AndroidOne logo without any animation....
I really don't know what to do now...
Yes the bootloader is unlocked and I checked with fastboot getvar
Click to expand...
Click to collapse
Ok , it totally sound like some kind of hardware issue with the storage . Is there any way to boot in TWRP ?
Download the TWRP version 3.3.3-1 offain and try to boot with it (fastboot boot recovery(the name of the recovery).IMG) and wait until the TWRP logo disappear. Wait at least 1 minute if the logo doesn't disappear , then in my opinion , you have a hardware problem , if you succeed to booting in TWRP download the GM 1.1 version from this thread :
https://forum.xda-developers.com/mi-a2-lite/development/9-miui-rom-t3960704
and flash it via TWRP. Then reboot and leave the phone without touching at least 10 minutes (until you see some movement like on the bottom of the screen , there will be a MI logo , right above the logo if you see 3 dots moving , then you're saved . From there we can proceed , but if you can't flash even this rom , if nothing helps. I hope you have a warranty , reflash the stock rom with the option flash_all_lock and go to your warranty service center.
EDIT: I googled and found another issue, that might be causing this strange situation: You may got scammed , and the device might not be a Mi A2 Lite , but rebranded Redmi 6X. See this thread:
http://en.miui.com/thread-5984082-1-1.html
If your phone is displayed "Wayne" ,not "Daisy" ,then you'll have to flash a Redmi 6X firmware to get rid of the bootloop
nikoman1987 said:
Ok , it totally sound like some kind of hardware issue with the storage . Is there any way to boot in TWRP ?
Download the TWRP version 3.3.3-1 offain and try to boot with it (fastboot boot recovery(the name of the recovery).IMG) and wait until the TWRP logo disappear. Wait at least 1 minute if the logo doesn't disappear , then in my opinion , you have a hardware problem , if you succeed to booting in TWRP download the GM 1.1 version from this thread :
https://forum.xda-developers.com/mi-a2-lite/development/9-miui-rom-t3960704
and flash it via TWRP. Then reboot and leave the phone without touching at least 10 minutes (until you see some movement like on the bottom of the screen , there will be a MI logo , right above the logo if you see 3 dots moving , then you're saved . From there we can proceed , but if you can't flash even this rom , if nothing helps. I hope you have a warranty , reflash the stock rom with the option flash_all_lock and go to your warranty service center.
EDIT: I googled and found another issue, that might be causing this strange situation: You may got scammed , and the device might not be a Mi A2 Lite , but rebranded Redmi 6X. See this thread:
http://en.miui.com/thread-5984082-1-1.html
If your phone is displayed "Wayne" ,not "Daisy" ,then you'll have to flash a Redmi 6X firmware to get rid of the bootloop
Click to expand...
Click to collapse
I will now try your solution, I just tried the testpoint unbrick method but still same problem.
The output from fastboot getvar all shows a DAISY bootloader. Where I can see the real name of the device to see if it is a Mi 6X?
pocchio said:
I will now try your solution, I just tried the testpoint unbrick method but still same problem.
The output from fastboot getvar all shows a DAISY bootloader. Where I can see the real name of the device to see if it is a Mi 6X?
Click to expand...
Click to collapse
the command is: fastboot oem get-product-model
nikoman1987 said:
the command is: fastboot oem get-product-model
Click to expand...
Click to collapse
Unfortunately I get unknown command.
Additionally when I try to boot the TWRP I get stuck at logo forever....
pocchio said:
Unfortunately I get unknown command.
Additionally when I try to boot the TWRP I get stuck at logo forever....
Click to expand...
Click to collapse
tried the command too, it doesn't work.
So test point doesn't work too.. That's bad news
EDIT: fastboot getvar product command works , you can try it
And another question , have you tried to boot with patched boot.IMG ?
It seems indeed some hardware problem... Is there any way I can try to boot something from the SD card? (In order to rule out the storage problem....
pocchio said:
It seems indeed some hardware problem... Is there any way I can try to boot something from the SD card? (In order to rule out the storage problem....
Click to expand...
Click to collapse
You need a recovery to flash , which has a specific partition in the phone storage. You can flash only via fastboot . You need to boot into recovery , so try with a patched boot image for your version of the rom
---------- Post added at 02:47 PM ---------- Previous post was at 02:38 PM ----------
pocchio said:
It seems indeed some hardware problem... Is there any way I can try to boot something from the SD card? (In order to rule out the storage problem....
Click to expand...
Click to collapse
So the last resort , we'll try to flash the ROM that I have mentioned before via fastboot. Place the zip file GM 1.1 in your PC (it has to be in the same directory as your adb and fastboot tools)
then open cmd and run the command
fastboot flash (the full name of the zip).zip
and hit enter
maybe that will solve it
And if this doesn't help again... type these fastboot commands :
fastboot format userdata
fastboot format system
fastboot format cache
fastboot format vendor
fastboot format recovery
fastboot format boot
then try again to reflash the stock rom (first try in edl mode ,if this doesn't do anything ,you'll have to format everything via fastboot commands again ,and try to flash the ROM in fastboot mode)
And if this doesn't help too... Then you're free to hit that ? in the ground hahahah (just kidding)
Tried both these two last but nothig works, I always get the same problem.
I just saw your comment on patched boot, can you elaborate a little bit on this?
I'm honestly very close to throw it in the trash
pocchio said:
Tried both these two last but nothig works, I always get the same problem.
I just saw your comment on patched boot, can you elaborate a little bit on this?
I'm honestly very close to throw it in the trash
Click to expand...
Click to collapse
which version of the firmware you are flashing? 10.0.9.0 or another version , so I can send you a link and walk you through the procedure.
And when you flashed the GM 1.1 the boot screen didn't changed from Android one? (the GM 1.1 version is a MIUI stock port and has to change your boot screen to black screen with white MI logo on it) It is very important to know
One of my friends told me to try this: just open the directory of the stock firmware , navigate to flash_all.bat and run the bat file (NOT THE FLASH_ALL_LOCK!!!) and wait for the end of the process. He had a similar problem , and it worked. He explained that for any reason , the recovery was the problem , because it was flashed in the boot partition. When you use flash_all.bat The file will erase all partitions and rewrite them. MiFlash won't , so try that
Greetings. First of all , I have to say that I think i messed up many things.I'm going to describe all of my steps and how I ended up stuck with fastboot and .. nothing else. So I started with installing stock rom by twrp . Booted to twrp , cleared cache and data and when I flashed the zip , I got error 1 . So I thought it would be easier to do it with Miflash tool. Next , after installing miflash and the fastboot version of the rom , I flashed it but it seemed that it was taking so long (more than 2000 seconds ) and it was stuck on flashing a specific file. The next and crucial imo move I did was to remove the usb cable from my phone resulting to an error in miflash (obviously). And this is when I realised that when I pressed the power button for a long time , it wouldnt boot to my custom rom . Instead it turned back to fastboot . I tried one more time flashing the stock rom with miflash but got an error after a few minutes. Also , I tried to boot to twrp by pressing volume up + power button , but it turned to fastboot again. So I opened cmd , booted to twrp from there and I thought about flashing twrp from the recovery (flash current twrp)and... guess what . Got an error and couldnt flash twrp. I have been searching for help online over the past 3 hours , but unfortunately I havent found any fixes yet. I would really appreciate any help from here , as I really dont want to lose my device. Thanks in advance.
EDIT: I have solved this issue.
NTClarity said:
Greetings. First of all , I have to say that I think i messed up many things.I'm going to describe all of my steps and how I ended up stuck with fastboot and .. nothing else. So I started with installing stock rom by twrp . Booted to twrp , cleared cache and data and when I flashed the zip , I got error 1 . So I thought it would be easier to do it with Miflash tool. Next , after installing miflash and the fastboot version of the rom , I flashed it but it seemed that it was taking so long (more than 2000 seconds ) and it was stuck on flashing a specific file. The next and crucial imo move I did was to remove the usb cable from my phone resulting to an error in miflash (obviously). And this is when I realised that when I pressed the power button for a long time , it wouldnt boot to my custom rom . Instead it turned back to fastboot . I tried one more time flashing the stock rom with miflash but got an error after a few minutes. Also , I tried to boot to twrp by pressing volume up + power button , but it turned to fastboot again. So I opened cmd , booted to twrp from there and I thought about flashing twrp from the recovery (flash current twrp)and... guess what . Got an error and couldnt flash twrp. I have been searching for help online over the past 3 hours , but unfortunately I havent found any fixes yet. I would really appreciate any help from here , as I really dont want to lose my device. Thanks in advance.
Click to expand...
Click to collapse
Try flashing miui via batch scripts is what I would do...
When you extract firmware there should be flash_all.bat file inside, run it via cmd - just type the name of it with cmd directed at the folder where the firmware is unpacked. ( For this you need adb tools installed properly so that the whole system has access to it , if you don't know how then download platform tools from google , unpack it and copy everything inside platform tools folder then paste into firmware folder , then you should be able to run the scripts inside firmware folder )
It will start regular process that mi flash does but if it fails then I guess you can see where it fails exactly and update here .
Idk...
You know, this would've been much easier to read if you put some effort into your grammar.
What error did you get in Mi Flash? Did you download the correct Fastboot Stock ROM for your specific region?
NTClarity said:
Greetings. First of all , I have to say that I think i messed up many things.I'm going to describe all of my steps and how I ended up stuck with fastboot and .. nothing else. So I started with installing stock rom by twrp . Booted to twrp , cleared cache and data and when I flashed the zip , I got error 1 . So I thought it would be easier to do it with Miflash tool. Next , after installing miflash and the fastboot version of the rom , I flashed it but it seemed that it was taking so long (more than 2000 seconds ) and it was stuck on flashing a specific file. The next and crucial imo move I did was to remove the usb cable from my phone resulting to an error in miflash (obviously). And this is when I realised that when I pressed the power button for a long time , it wouldnt boot to my custom rom . Instead it turned back to fastboot . I tried one more time flashing the stock rom with miflash but got an error after a few minutes. Also , I tried to boot to twrp by pressing volume up + power button , but it turned to fastboot again. So I opened cmd , booted to twrp from there and I thought about flashing twrp from the recovery (flash current twrp)and... guess what . Got an error and couldnt flash twrp. I have been searching for help online over the past 3 hours , but unfortunately I havent found any fixes yet. I would really appreciate any help from here , as I really dont want to lose my device. Thanks in advance.
Click to expand...
Click to collapse
try to download again the firmware, maybe the file you have been trying to flash is corrupted.
Most and foremost, try to be specific what it was you encountered. Feels like I was reading in a wattpad.
How did you do it?
Please share with how you solve it
NTClarity said:
Greetings. First of all , I have to say that I think i messed up many things.I'm going to describe all of my steps and how I ended up stuck with fastboot and .. nothing else. So I started with installing stock rom by twrp . Booted to twrp , cleared cache and data and when I flashed the zip , I got error 1 . So I thought it would be easier to do it with Miflash tool. Next , after installing miflash and the fastboot version of the rom , I flashed it but it seemed that it was taking so long (more than 2000 seconds ) and it was stuck on flashing a specific file. The next and crucial imo move I did was to remove the usb cable from my phone resulting to an error in miflash (obviously). And this is when I realised that when I pressed the power button for a long time , it wouldnt boot to my custom rom . Instead it turned back to fastboot . I tried one more time flashing the stock rom with miflash but got an error after a few minutes. Also , I tried to boot to twrp by pressing volume up + power button , but it turned to fastboot again. So I opened cmd , booted to twrp from there and I thought about flashing twrp from the recovery (flash current twrp)and... guess what . Got an error and couldnt flash twrp. I have been searching for help online over the past 3 hours , but unfortunately I havent found any fixes yet. I would really appreciate any help from here , as I really dont want to lose my device. Thanks in advance.
EDIT: I have solved this issue.
Click to expand...
Click to collapse
Please share with us how you solve it
miku1024 said:
Please share with how you solve it
Please share with us how you solve it
Click to expand...
Click to collapse
Basically , I managed to flash it successfully after many attempts. I was getting different errors every time when I was trying to flash the EU version in my PC , so I thought of switching to my laptop and trying with the GLOBAL version this time. I succeed the 2nd time . I also used a different usb cable. So it was just miflash being miflash... nothing to worry about.