Hi!
I have a problem with an M2 that I am trying to recover. I don't know what exactly happened, but who gave it to me said they found it one morning stuck with the MIUI logo, and then turn it off and on again finding this error ... I'm afraid that the update process was interrupted, but usually the phone not start updating without asking.
The phone only goes in Fastboot, no recovery, has the bootloader locked and unfortunately an associated MI account was not made.
I have tried everything I found online, but I have not succeeded to flash on it anything or unlocking the bootloader.
If I use the command fastboot devices it is recognized, same in Mi Flash, but having the bootloader locked it does not flash anything.
I was unable to put it in EDL mode, as some advised.
Is there anything I can do or the only way is to take it to a service center?
Thanks for your help
Oh sorry, I think I got the wrong section by mistake.
If it was to be put in POCO M3 Questions & Answers I kindly ask if you can move it, thanks
Related
my phone is everything first off and i cannot do any thing erecovery cant do anything because im on unoffical 90nrdm os when i try do anything i adb it cannot find my device and just says waiting for device when trying to lock bootloader in fastboot mode so i tried unlocking it (i got the code) but it says s"FAILED stat does not match" and i cannot flash anything to fix my phone and i cannot find the huawei page to unlock my bootloader because it keeps saying " this id is registered on the other site" but never tells me where to go or find the "other site" bootloader unlock page i really need my phone to work resetting it is fine i got back ups but i really need the phone to work all help is welcome, i have adb and fastboot installed i tried useing srk tools 2.0 lod-chong and also cmd to try fix my issue but i get no where. i have no recovery either it just wont boot into twrp it just goes straight to erecovery so i cannot do any dload method. also when i tried other methods it said password wrong for some reason.
i flashed oeminfo.bin and custom.bin to go back to offical nougat from somewhere after this update nougat didnt work (hisuite refused to install it) : http://ministryofsolutions.com/2017/03/huawei-p9-lite-vns-l31-nougat-b371-update-stable-europe.html so i then looked into downgrading and got to this https://forum.xda-developers.com/hu...nt/europe-vns-l31-toolkit-bootloader-t3432873 and i did the oem info flash and it like the person said on my previews post ( https://forum.xda-developers.com/huawei-p9lite/help/bricked-device-dont-how-to-fix-l31-t3617851) and it just like he said but i did it before he commented and now my phone wont boot and when i enter my bootloader code it says FAILED stat does not match and because i cannot re lock and unlock my boot loader i cannot flash anything to get my phone back, how can i fix this.
Hi, I have a moto x style pure and it is on a bootloop. I have tried to send the fastboot codes for reset (erase userdata, erase cache) but keeps rebooting. So I tried to reinstall the complete system, but there is no software avaliable for the nphs 25.200.23 version I could only find the 25.200.22 version. If somebody could help me I would really appreciate.
Pdta: I could not enable oem unlock before the bootloop so I can´t reinstall a lower version of the software because of the locked bootloader. If somebody knows a way to unlock the bootloader (I have already did the test on the motorola web page but when I put the unlock code on fastboot it asks me to enable oem ulock via software) Sorry for my english is not my mother tongue.
Thanks in advance
vladimir1909 said:
Hi, I have a moto x style pure and it is on a bootloop. I have tried to send the fastboot codes for reset (erase userdata, erase cache) but keeps rebooting. So I tried to reinstall the complete system, but there is no software avaliable for the nphs 25.200.23 version I could only find the 25.200.22 version. If somebody could help me I would really appreciate.
Pdta: I could not enable oem unlock before the bootloop so I can´t reinstall a lower version of the software because of the locked bootloader. If somebody knows a way to unlock the bootloader (I have already did the test on the motorola web page but when I put the unlock code on fastboot it asks me to enable oem ulock via software) Sorry for my english is not my mother tongue.
Thanks in advance
Click to expand...
Click to collapse
As you wrote - with locked BL you can do... nothing.
Only You can wipe all in recovery mode - u can find "how to" with google.
Yeah I'm curious how come you didn't do a recovery in fast boot mode? I don't think you muffed any during a flash when your boot loader is locked.
dzidexx said:
As you wrote - with locked BL you can do... nothing.
Only You can wipe all in recovery mode - u can find "how to" with google.
Click to expand...
Click to collapse
The problem is that even wiping everything in recovery or via fastboot, the phone is still on a bootloop. So, thats why I am asking for help, or maybe somebody has the ota in a zip format or a full flash.
StankFiss said:
Yeah I'm curious how come you didn't do a recovery in fast boot mode? I don't think you muffed any during a flash when your boot loader is locked.
Click to expand...
Click to collapse
I tried to, and when it is done, keeps rebooting
You are locked... there is NOTHING we can do at this point other than a factory reset in recovery, if that fails to get the device booting and you cannot get it unlocked again (unlikely since OEM Unlocking gets turned off again when you re-lock), then the device is probably bricked.
I am a little curious how you got to this state... the only way you could have relocked the bootloader was on 200.22, so it must have booted then in order to take .23 OTA update... or what exactly happened? I doubt it would make a difference to help you, but the information might help others from bricking.
acejavelin said:
You are locked... there is NOTHING we can do at this point other than a factory reset in recovery, if that fails to get the device booting and you cannot get it unlocked again (unlikely since OEM Unlocking gets turned off again when you re-lock), then the device is probably bricked.
I am a little curious how you got to this state... the only way you could have relocked the bootloader was on 200.22, so it must have booted then in order to take .23 OTA update... or what exactly happened? I doubt it would make a difference to help you, but the information might help others from bricking.
Click to expand...
Click to collapse
Sure I can tell you my history.
My sister came with this phone she bought on the web. The problem was the data cable. It was faulty. And the battery was at 2%.
While I was looking for usb cable, the phone went off. So I did not thought in another thing just than let it charge for a while. After let it charge for 30 minutes, I tried to turn it on and it was only rebooting. So a said to myself: "Lets send fastboot commands for erasing userdata and cache, and then she can put her google account and using it" I have reset a lot of motorola phone before with this same method. After rebooting, the phone kept rebooting. Then I said: " Ok lets full flash the phone" But when I was searching for the firmware I could not find the same or higher version of the phone. There is only 25.200.22 on every website I have visited. And I cant unlock the bootloader because nobody actived the oem unlock when it was booting properly.
This is basically how my nightmares started. I was talking with some technitians and they say they need to replace the mainboard because when they try to flash it fails, of course cause they have an older version, and it is a hardware issue.
vladimir1909 said:
Hi, I have a moto x style pure and it is on a bootloop. I have tried to send the fastboot codes for reset (erase userdata, erase cache) but keeps rebooting. So I tried to reinstall the complete system, but there is no software avaliable for the nphs 25.200.23 version I could only find the 25.200.22 version. If somebody could help me I would really appreciate.
Click to expand...
Click to collapse
https://forum.xda-developers.com/moto-x-style/general/official-firmware-moto-x-purestyle-t3737472
Now im stuck in fastboot and whenever i try to boot my phone it opens recovery and says "This MIUI can't be installed on this device".
Also i tried mi unlock but it stops at 99% and says i need to access developer options and link my account which i cant since i dont have access to the phone...
I'm in a very ****ty situation so any help would be appreciated.
Also, did i completely brick my phone?
So, basically I will make this short as possible
Due to some problems I had to sell my G6 Plus (Brazilian -8 model) but it was on a custom rom, and did the most dumb thing that I could do: Reflashing pure stock and locking it, I've used the LMSA tool then relocked in Fastboot, the thing is some files were corrupt and when locked, it doesn't boot up anymore, as i still had hope for it, I tried to LSMA again, but it doesnt recognize anymore, as the lock flag is now "Flashing_Locked", flashing manually via Fastboot gives a error related to the lock flag (also LSMA resets the device, so using my unlock key asks to enable OEM Unlock at settings, a impossible thing when OS is broken) , then searched for some solutions, first it was booting a Boot.img file from the last stock, which was the flashed one, it bootloops, then tried something on the recovery that works, but is the stock one and pretty limited, so the logical thing to do is flashing a OTA file, but only works for old versions that requires one version before the target one, so its a no go. The last thing i tried to do is booting TWRP, but it gets stuck on a red warning that indicates that system is corrupt. Then the last hope was EDL Mode, and thats the point where i want to go, i've bought a EDL Cable that's basically a green and black wire thing used on most Qualcomm based Redmi/Xiaomi devices, but it automatically boots to fastboot, so I need help to get EDL Test Points for this device, im with access to the board, i just need the right Pads to short-circuit it and blankflash it, so i can finally get it to work like normal again.
Schematics (for people who understands): https://androidfilehost.com/?fid=4349826312261726244
Any help is important, I'm sorry for some typos, english isnt my main language considering i didnt use translate
and please don't come with instructions like "have you tried LSMA?, try booting up the device and select oem unlock" because its clear that it doesnt work.
Let me describe my issue in detail. In running call, suddenly device hang up and not starting up. So I tried below options to get it working but didn’t get luck.
So obviously, boot loader is locked as it done suddenly. So I cannot access developer menu options.
From the boot loader menu, I tried to wipe up data but it didn’t worked as it shows an error message like “…Failed to load bcb message and fsync error. …”. Tried an wait for almost one day but not worked.
After spending lots of time on web, I get to know the if boot loader is locked then only EDL mode will work to flash.
So I opened my phone and switched to EDL mode and tried to flash.
In a first iteration, I got many errors like ACK error, Hello packed not found error. But In some of the threads I got it like install M Flash Beta version to do that. (disconnect from internet just before flash)
I tried couple of firmware like ,
tissot_images_V10.0.24.0.PDHMIXM_9.0
tissot_images_7.8.23_7.1
With the both firmware, I get success message in flash after 7-8 minutes.
But phone remain in same condition.
Please read complete situation and please suggest if other than this can work. I appreciate your time and comment. Thanks.
Same situation here.
From my experience MiFlash Beta doesn't do anything, it shows a progress but it is probably not actually writing data to phone memory.
While I've seen some contradictory claims that you can flash through EDL without an authorized Xiaomi account on Mi A1, I don't think those claims are valid.
Please keep updating this thread, whether you find a solution or not. At least we can filter out non working suggestions.
I am also interested in this problem, I have the same situation