Hi there,
I've tried to flash my phone.
At first I've flashed the China Version Miui Beta 12.5 and it runs.
Then I've tried to flash MiuiPlus and when it starts to boot into the Rom, there comes the MiuiPlus and it didn't boot completely.
Then I've tried to flash an other Europe Miui 12.5 and after flash I did a start into the system from TWRP.
It shut down and then I saw half a second, the Display shows a little light, then it turns of.
This happens also when I wants tot start into Recovery and when I plug it on.
When I wants to start it into Fastboot Mode, there is just have a second the Fastboot Symbol, then it turns off.
Can somebody help me?
Is this a brick?
Thks. for every try to help me
Do you unlock your phone?
In case of brick, you will need to flash in QCOM mode, but that is limited to only a few service center, officially. But thanks to recent discovery, it isn't necessary. Here is how you bypass the security measures and flash your device via SPFT. If you are on latest windows 10, you will need to install the microsoft store version of python instead, and then install the necessary libraries manually.
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
Hello, I have Moto Z play with chinese firmware (64gb model) and tried to flash european version of firmware so I can use google services. flashing succeeded until i got to the part where firmware flashing starts (fastboot flash system system.img_sparsechunk.0) and thats where it started to fail. So I assumed it cannot be flashed as phone model differes as well as some hardware potentially, my model is XT1635-03 when non chinese are XT1635-02 with 32gb max memory. I completed flashing all parts from european firmware and as system imgs failed - chinese version remained. Later I found another way of having google services on my phone, I flashed TWRP recovery with SuperSU and then installed Xposed framwork to allow install other frameworks like google play services framework. So everything went well and I managed to enable google services on chinese phone, but I couldn't upgrade software version as it fails verification when it finds european boot, recovery, logo and modem ( I assumed). My solution was to reinstall stock chinese firmware and flash everything again to use google services. Afther reinstalling firmware I was allowed to upgrade it, next step was to flash TWRP recovery and the rest, but that's where it started to go wrong. It will not let me flash anything anymore.
Fastboot devices will find my phone, adb devices works when phone is switched on, but not when in bootloader mode, adb reboot bootloader will not work - no devices found. When I try to flash something it just gets stuck in cmd window and phone bootloader (volume buttons will not navigate, but power button will switch off). Also I noticed when I switch USB debugging on, go to bootloader mode and out or restart phone it will switch by itself off. Tried to reinstall every driver and program, nothing worked... maybe firmware update triggered something, even when version didn't change, only build number when I thought it will upgrade to android 7.
Please someone help me, my brains hurt so much and I don't know what to do. Thank you in advanced
I have a Xiaomi Note 8 Pro initially came with China Stable Rom V11.0.3.0.PGGCNXM. It was also unlocked.
I accidentally flashed Global Stable ROMV11.0.6.0.PGGMIXM via MiFlashTool and while it was successful, it rebooted to Recovery Mode with the message "This MIUI version can't be installed on this device".
After that, I pressed "Wipe All Data", so now the device is also locked.
Since there is no OS installed, I cannot access the device and consiquently to use Mi Unlock Tool properly to Unlock it again.
The device is now locked, without OS installed. However I can access Fastboot menu and Recovery mode.
Is there anyway to unlock the device in this state and flash it's original Rom again?
Please if you have anything to suggest that might help me, answer my question. I'm desperate. :crying:
Hmmm. Can you still access fastboot mode? If yes I recommend using miflash pro and flashing the correct rom for your device, or manually flashing all images via fastboot.
You've likely selected Clean all and lock (default setting) which flashed MIUI and locked the bootloader afterwards which bricked the device because of cross-region ROM flashing. Since you can't flash it with locked bootloader your only option is to take it to the service center.
@JuanM2020 @n0b0dy666 First of all, thank you guys for your suggestions.
Update: I tried to flash it's original Rom via MiFlash Pro, however when I connected my device on the final step, as for the SP tool to flash the Rom, my pc couldn't detect it. I even risked and disassembled the device to remove the battery in order to turn off the device, but it didn't work either. (Cdc & Vcom Mediatek drivers both installed properly on my pc).
The device is recognized by my computer when in Flashboot menu. However for the SP tool to work, it should be turned off, but recognizable from computer.
Before posting here, of course I went to a service center, but they told me because I tried to install Global Rom 11.0.06, while it's original Rom was China Stable Rom 11.0.03, I should wait for the 11.0.06, as a downgrade is not possible (not sure if it's true). We don't have an official Xiaomi Center in my county, where I go was the best chance I had.
Any other recommendations?
RenginaP said:
@JuanM2020 @n0b0dy666 First of all, thank you guys for your suggestions.
Update: I tried to flash it's original Rom via MiFlash Pro, however when I connected my device on the final step, as for the SP tool to flash the Rom, my pc couldn't detect it. I even risked and disassembled the device to remove the battery in order to turn off the device, but it didn't work either. (Cdc & Vcom Mediatek drivers both installed properly on my pc).
The device is recognized by my computer when in Flashboot menu. However for the SP tool to work, it should be turned off, but recognizable from computer.
Before posting here, of course I went to a service center, but they told me because I tried to install Global Rom 11.0.06, while it's original Rom was China Stable Rom 11.0.03, I should wait for the 11.0.06, as a downgrade is not possible (not sure if it's true). We don't have an official Xiaomi Center in my county, where I go was the best chance I had.
Any other recommendations?
Click to expand...
Click to collapse
If you can still access fastboot mode flash correct images manually.
E.g.:
Fastboot flash system system.img
Fastboot flash vendor vendor.img
Fastboot flash recovery recovery.img
Etc etc
JuanM2020 said:
If you can still access fastboot mode flash correct images manually.
E.g.:
Fastboot flash system system.img
Fastboot flash vendor vendor.img
Fastboot flash recovery recovery.img
Etc etc
Click to expand...
Click to collapse
So sorry for my late response. Is there any guide about manual flashing which I can follow for that?
RenginaP said:
So sorry for my late response. Is there any guide about manual flashing which I can follow for that?
Click to expand...
Click to collapse
https://www.xiaomigeek.com/flash-miui-fastboot-rom-using-command.html
Could you fix it?
Hello, has been a w hile since I was here last time. However, my moto g 5g plus gives me a hard time now. I was using it and at some point the power button stopped working. First it worked only randomly but now it is dead. Before the phone shut down i was able to test the fingerprint sensor and it worked. The last few days i noticed that the connection resets randomly from 5G to 4G to H+ and sometimes i had to restart the phone to have a working connection. I was thinking there is a firmware bug in the stock firmware that continues showing up over time. Last time i did a firmware recovery using the motorola rescue tool but that doesen't work anymore because i cant enter boot loader mode. I have seen that there is the qualcom flash tool out there and im wondering if im able to flash the device without bootloader mode as im not able to start it. And if the problem is software related or not. For the qualcom flash tool i probably need the "firehose" files, where can i find the right one for my device?
I have an update, I think it is a software problem. I have tried unlocking the bootloader and as soon I did everything worked same before. Then I flashed linageos and as as able to use it for one day until (when playing pokemon go it happened again) now the power button responds with delay. But it responds. I have tried to reflash lineage and stock using rescue assistant but nothing helps. Then I tried reboot in edl mode for blankflash but that one also doesent work. It starts the process when it sees the device but it terminates with an error. I have dumped all partitions using the recovery shell. But not sure where to search for as I don't have a dump of the stock partitions. I think there has been some corruption of one of the data in _a slot and now _b slot too. Someone knows what and where to look for? Maybe I need a dump of stock device?
It seems there is something wrong with bootloader. Now I'm not able to flash in fastboot mode. But it works when I flash the gpt.bin after restart in fastboot. I start the download on the PC and then connect the phone and power up in bootloader mode. After that I can flash as normal but after reboot everything same before, no fastboot working. And if I flash stock ROM and lock the bootloader it says no operating system found. I have tried using blankflash from lolinet but that one also doesent work. It recognises the device but then it stops. Is it possible that I have got this sort of thing ota? This is so weird. The power button works but just delayed. Is it on a different chip what is maybe broken? But that would be very strange. I have another phone I treat not as nice as this one and that works like new.
Ah I enter edl by using linage recovery
Deleted all the partitions, now it seems the device doesn't boot the stock ROM if I flash it. What are the essential partitions needed to boot the stock ROM? How can I restore the missing partitions? Thanks
good evening
I have been trying to return to stock miui from Pixel Experience since yesterday but get this error every time I try to flash the Firmware and do not know what I can do about it. I would be happy if somebody knew what this error is from and what might fix it.
Same problem. Don't try more things because you will brick your phone like mine.
Thanks for your reply. What did you do that bricked your Phonem? This way I know what to avoid. Thanks you in advance
As you are sure your device is a eea one, try with this last official stable firmware : Version: V13.0.7.0.SKHEUXM
You can find it here https://new.c.mi.com/global/miuidownload/detail/device/1900394
Fastboot version here at bottom : https://xiaomifirmwareupdater.com/miui/alioth/stable/V13.0.7.0.SKHEUXM/
Or https://bigota.d.miui.com/V13.0.7.0...EUXM_20220627.0000.00_12.0_eea_e461331a7d.tgz
Thanks you so much I will try that
and i did not mention this but I started this whole project of returning to miui because my poco was and still is in a bootloop and is only accessible over fastboot, not recovery and even though it sometimes gets to the system it almost instantly crashes and reboots
Still the Same Error unfortunatelly
nockcx said:
and i did not mention this but I started this whole project of returning to miui because my poco was and still is in a bootloop and is only accessible over fastboot, not recovery and even though it sometimes gets to the system it almost instantly crashes and reboots
Click to expand...
Click to collapse
Ok,
Do you have any idea what you did that may have caused this bootloop ?
Have you used any Qualcomm Tools or any soft in EDL mode ?
No, I did not do anything that would mess with the system to my knowledge . which is why i really do not know what to do. Can This Error occur because of a USB 3.0 used to flash? The Phone even tries to reboot when it is detected as a Fastboot device, maybe This has Something to do with it. Maybe it loses the Connection and therefore the flashing process stops. Are there possible ways to fix This?
Try with the latest android platform tools.
Put the content of platform tools archive in the fastboot folder and launch flash_all.bat don't use flash_all_lock
Still the Same Error . Can This be because of a Driver or a hardware issue?
i had similar issues but with the super partition when trying to flash from cmd.
flashing with miflash instead solved it.
It doesnt seem to make any difference to the error whether i flash it via cmd or miflash
nockcx said:
Still the Same Error . Can This be because of a Driver or a hardware issue?
Click to expand...
Click to collapse
Maybe : So as you can try with other PC, USB cable, USB connector, reinstall USB drivers...
I already tried with two Notebooks, I will try again tomorrow with another PC and installing USB drivers again. Thank you
You could try redownloading the MIUI ROM... you got it from xiaomifirmwareupdater.com right?
And yes ^^, try other PCs/laptops and other USB-cables.
Just please make sure
Unfortunately, Fastboot-Flashing is a gamble. It's not a solid protocol. It has zero protection against sudden USB-connection loss.
And manufacturers like Xiaomi go out of their way and block Qualcomm's EDL Mode, which is the only way to recover your phone in case Fastboot Mode stops working, because that Mode itself can also get damaged.
Fixed - first flash a miui recovery rom from twrp make sure the rom version lower than the latest one, now flash and boot miui , now just update from miui updater once you updated to the latest version , now try to flash the fastboot rom that you trying to flash, it should work.
I cant access a bootloader like TWRP because the phone still keeps rebooting after a couple of seconds in the bootloader so i cant really do much. I only have access to fastboot
nockcx said:
just flash a custom vbmeta and then install a custom recovery in to the boot partition like fastboot flash boot ....flash both the slots boot_a and boot_b the run fastboot reboot recovery do all this with latest platform tools
Click to expand...
Click to collapse
okay Im as far as I have never been with a very weird method, maybe somebody can explain. Because my poco always wants to reboot I found out a way to keep in in Fastboot mode. I repeatedly press the power and volume down button, This way it stays on for a lot longer, but it still is not enough to succeed at flashing the rom. It also lets me believe that my problem is not a software but probably a hardware problem, otherwise and cannot explain this suuuper weird behavior. what do you guys think? is there a possible fix you know?