Meizu M3 Note bricked - Meizu M3 Note Questions & Answers

Hello,
i have recently bricked my Meizu M3 Note phone when updating beta firmware.
Phone seems to be totally dead, unable to power on, stuck on black screen. My PC recognize the phone: Windows 10 seeing it as MediaTek USB Port, but it is continuously switch their status, as if the cable were connected and disconnected continuously.
I've tried with various versions of SP Flash tools, and also followed various howto including this:
https://forum.xda-developers.com/android/development/developer-verified-meizu-m3-note-hard-t3682743
But i get various code errors, depending on try flashing with auth file or without.
Particularly, it seem that version 5.13.52.200 of Flash Tool maybe working, but after a few time after pressing Download Button and plug the phone cable, it comes report a error:
"Can Not pass bootrom start command! Possibly target power on too early"
If someone have any suggestion, i appreciate. Thanks in advance, i hope that my phone is recoverable.

Related

Mi A1 locked in EDL mode by itself. Stuck at "Ping via firehose"

Hello everyone,
My phone suddenly got stuck in EDL mode (getting recognized as Qualcomm .... 9008 on my pc) and for the life of me, I cannot figure out how to get it out of it. Cannot even boot in fastboot.
I have tried almost all versions of MiFlash, back to a 2014 one, and each of them gets stuck at "Sending nop command" or "Ping target via firehose" which are practically the same in the logs.
I'm trying all this with the battery and fingerprint sensor unlocked.
Also tried to use QFIL but all I get is "FHLoader failed The system cannot find the specified file".
Unfortunately there's no Xiaomi tech support in my country so I cannot take my phone to any physical place as far as I know.
Any ideas?
Things I tried so far:
Various versions of MiFlash
Fastboot ROM
Stock ROM
QFIL
Windows on Test mode
Shorted to EDL mode
No battery connected
No Fingerprint connected
No module connected
Holding Vol Up / Vol Down and Power
Holding the Power button for more than 3 minutes and while flashing
Drained the battery and charged it back
Different voltages, chargers and cables
You will most likely need Deep Flash cable...\
Edit:
Your phone is most likely hardbricked, so DF cable is only solution.
OR
Try this:
http://en.miui.com/thread-380827-1-1.html

Lenovo Tab 3 8 (TB3-850M) - Hard Bricked

Hi,
It looks my tablet got hardbricked. Apparently, it looks like it was turned off completely automatically, when in sleep mode. When it's powered off now - pressing power button for a while makes nothing. When connected to charger - white LED flash is blinking only and when trying to power on, and there is no "Lenovo" logo at all. I've tried some of "power cycle" tutorials - but no luck. Once, when using power button, tablet was vibrating crazily and screen blinked, but it was shut down after moment.
Sorry, if there is existing similar thread - this tablet is not very popular. If there is any "magic trick" to make it work, I'll be grateful, if now - probably I'll need to flash new firmware. Currently, I'm discharging it completely.
Best regards.
wxtester said:
Hi,
It looks my tablet got hardbricked. Apparently, it looks like it was turned off completely automatically, when in sleep mode. When it's powered off now - pressing power button for a while makes nothing. When connected to charger - white LED flash is blinking only and when trying to power on, and there is no "Lenovo" logo at all. I've tried some of "power cycle" tutorials - but no luck. Once, when using power button, tablet was vibrating crazily and screen blinked, but it was shut down after moment.
Sorry, if there is existing similar thread - this tablet is not very popular. If there is any "magic trick" to make it work, I'll be grateful, if now - probably I'll need to flash new firmware. Currently, I'm discharging it completely.
Best regards.
Click to expand...
Click to collapse
Are you still bricked? There is the firmware flashing method using SP Flash Tool which restores both the 850F & 850M to full factory condition. Let me know if you need the method and I'll get you links to the guides here on XDA.
AeonFlux1603 said:
Are you still bricked? There is the firmware flashing method using SP Flash Tool which restores both the 850F & 850M to full factory condition. Let me know if you need the method and I'll get you links to the guides here on XDA.
Click to expand...
Click to collapse
Yes. I've asked for help guy from unauthorized repair service, he said device is completely bricked, probably EEPROM chip is broken. But ok, you can send me this instruction of course
wxtester said:
Yes. I've asked for help guy from unauthorized repair service, he said device is completely bricked, probably EEPROM chip is broken. But ok, you can send me this instruction of course
Click to expand...
Click to collapse
I've had two 850F devices hard bricked and was able to recover using SP Flash Tool and a stock firmware package. I'll get you the method posted here. But, out of curiosity, how did you hard brick yours?
(The 850F is pretty much an 850M without SIM/data connectivity support. They also have slightly different chipsets, but many of the specs are very similar. So, I know the method will work on both variants of the Tab3 8.
AeonFlux1603 said:
I've had two 850F devices hard bricked and was able to recover using SP Flash Tool and a stock firmware package. I'll get you the method posted here. But, out of curiosity, how did you hard brick yours?
(The 850F is pretty much an 850M without SIM/data connectivity support. They also have slightly different chipsets, but many of the specs are very similar. So, I know the method will work on both variants of the Tab3 8.
Click to expand...
Click to collapse
Hey, thanks for you reply! As I'm not owner of the tablet, it's hard to say how it was bricked. It was on stock firmware, it was not rooted and TWRP was not installed. I've helped to configure this tablet, tablet was turned off everyday at 11PM automatically, and powered on manually, by device owner. She said sometimes instead of powering on to Android, it was booting into FASTBOOT mode (green android image). Once, it just failed to boot, without any reaction. I've tried to recover it using Windows machine, when plugging it into computer (no matter, with, or without Vol+ pressed) it was recognized as Unknown device (instead of Qualcomm, or something). I've tried many drivers - but with no luck, device was not recognized. Also, I've tried 2 machines with Win7 & Windows XP. I've managed to reboot device using power key long pressed, but starting from this point device was not recognized at all... When plugged into USB, nothing was happening. Service guy said he was able to make his computer recognize device using some technical cable plugged directly with motherboard, but all methods to flash firmware failed. He said probably EEPROM chip is broken completely and replacing this part is half of device cost. Thing is, this tablet was bought from China - so no guarantee at all. Well, probably she need to buy next tablet from local electronic store...
wxtester said:
Hey, thanks for you reply! As I'm not owner of the tablet, it's hard to say how it was bricked. It was on stock firmware, it was not rooted and TWRP was not installed. I've helped to configure this tablet, tablet was turned off everyday at 11PM automatically, and powered on manually, by device owner. She said sometimes instead of powering on to Android, it was booting into FASTBOOT mode (green android image). Once, it just failed to boot, without any reaction. I've tried to recover it using Windows machine, when plugging it into computer (no matter, with, or without Vol+ pressed) it was recognized as Unknown device (instead of Qualcomm, or something). I've tried many drivers - but with no luck, device was not recognized. Also, I've tried 2 machines with Win7 & Windows XP. I've managed to reboot device using power key long pressed, but starting from this point device was not recognized at all... When plugged into USB, nothing was happening. Service guy said he was able to make his computer recognize device using some technical cable plugged directly with motherboard, but all methods to flash firmware failed. He said probably EEPROM chip is broken completely and replacing this part is half of device cost. Thing is, this tablet was bought from China - so no guarantee at all. Well, probably she need to buy next tablet from local electronic store...
Click to expand...
Click to collapse
Yeah, the service guy is full of it without any doubt. Using a modded fastboot cable, like he was likely referring to, will not only fail to push firmware to the eMMC, but will very likely damage or corrupt the partition index. I can't promise my method will work, but I can say with some certainty that it will. Ok, first things firstt: install the latest SP Flash Tool on your Windows PC or laptop. Also, you will need to install the latest vCOM drivers (for the Mediatek chipset). Do you know how to do this or do you need links? I can post a link for unbricking the 850F, which has been reported to work on 850M, but the thread is a bit erratic and non-concise. It will be much easier if you and I do this step by step. Also, you will need a stock firmware package for your 850M (build version is not relevant). Do you have one or do you need a link?
In a nutshell, this method will do an emergency recovery by directly pushing a stock firmware package to the device's eMMC flash memory. Although your PC is not currently recognizing your device, the vCOM drivers/SP Flash Tool, & your volume down button, will force recognition of the Mediatek chipset. Again, I cannot promise this will be successful, but I can say I've not yet seen a single hard bricked Tab 3 that could not be recovered from a hard brick this way.
Step 1 -- install the latest vCom drivers on your Windows (7, 8.1, or 10) PC/laptop. Here is an excellent XDA tutorial that provides sources and detailed instructions. https://forum-xda--developers-com.c...-10-mtk-vcom-usb-drivers-32-64-t3267033/page1 Sorry for the lengthy url.
Step 2 -- install the latest SP Flash Tool on your PC or laptop. Go to this website for download sources; https://spflashtool.com/
Step 3 -- download a stock firmware package for your TB3-850M. This is a link for a solid firmware package, confirmed to work (take note that build version isn't a factor. The SP Flash Tool will push a downgrade, upgrade, or collateral installation {same build version}): https://cloud.mail.ru/public/LHhe/NkpAi7WuL
When you've completed the above 3 steps, let me know and we will go forward with the firmware recovery process. :good:
I have the same issue. I dont know how but i got hard bricked completely. I was flashing rom on it and it got bricked. Now service centre guy is saying that i have to change motherboard altogether. But your post seems convincing. Please let me know the next detailed process.
i have the same issue.
one day stop working
AeonFlux1603 said:
Yeah, the service guy is full of it without any doubt. Using a modded fastboot cable, like he was likely referring to, will not only fail to push firmware to the eMMC, but will very likely damage or corrupt the partition index. I can't promise my method will work, but I can say with some certainty that it will. Ok, first things firstt: install the latest SP Flash Tool on your Windows PC or laptop. Also, you will need to install the latest vCOM drivers (for the Mediatek chipset). Do you know how to do this or do you need links? I can post a link for unbricking the 850F, which has been reported to work on 850M, but the thread is a bit erratic and non-concise. It will be much easier if you and I do this step by step. Also, you will need a stock firmware package for your 850M (build version is not relevant). Do you have one or do you need a link?
In a nutshell, this method will do an emergency recovery by directly pushing a stock firmware package to the device's eMMC flash memory. Although your PC is not currently recognizing your device, the vCOM drivers/SP Flash Tool, & your volume down button, will force recognition of the Mediatek chipset. Again, I cannot promise this will be successful, but I can say I've not yet seen a single hard bricked Tab 3 that could not be recovered from a hard brick this way.
Step 1 -- install the latest vCom drivers on your Windows (7, 8.1, or 10) PC/laptop. Here is an excellent XDA tutorial that provides sources and detailed instructions. https://forum-xda--developers-com.cdn.ampproject.org/v/s/forum.xda-developers.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033/amp/?amp_js_v=a2&amp_gsa=1&usqp=mq331AQCCAE=#aoh=15510379323239&amp_ct=1551037935701&referrer=https://www.google.com&amp_tf=From %1$s&ampshare=https://forum.xda-developers.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033/page1 Sorry for the lengthy url.
Step 2 -- install the latest SP Flash Tool on your PC or laptop. Go to this website for download sources; https://spflashtool.com/
Step 3 -- download a stock firmware package for your TB3-850M. This is a link for a solid firmware package, confirmed to work (take note that build version isn't a factor. The SP Flash Tool will push a downgrade, upgrade, or collateral installation {same build version}): https://cloud.mail.ru/public/LHhe/NkpAi7WuL
When you've completed the above 3 steps, let me know and we will go forward with the firmware recovery process. :good:
Click to expand...
Click to collapse
what is next? i have a tab 3 710f that is very dead.. hardbricked in wont boot into nothing.. black screen like its shut down

HIFI Image Security Verify Error

Hello,
I have a Huawei P8 Lite (ALE-L21) phone with this error: FUNC 8 : HIFI Image, Error 1 Security Verify failed. I think I have tried everything to fix it but had no success, hence why I have decided to create this thread.
As you can figure out, the phone does not turn on, it only shows the huawei logo and shuts down. When pressing VOLUME UP + DOWN and POWER button, it used to show the HIFI image error screen, however when I press the key combination now, it only shows a red screen and turns off. I am able to enter fastboot and rescue mode by holding down the VOLUME DOWN button and plugging in a USB cable to the phone from a computer. Apart from that, I can't do anything else with the phone. (I do not have any software related to the phone installed (HiSuite), no backups, no nothing because the phone actually isn't mine and I have never actually played with it and androids in general.)
There are some similar threads and videos here:
https://forum.xda-developers.com/p8lite/help/stuck-rescue-mode-fastbootrescue-mode-t3648105
https://forum.xda-developers.com/p8lite/help/stuck-rescue-mode-screen-please-help-t3244872
https://forum.xda-developers.com/mate-10/how-to/how-to-huawei-mate-10-pro-standard-t3709535
https://forum.xda-developers.com/honor-5c/help/writing-recovery-failed-remote-command-t3584208
https://forum.xda-developers.com/p8lite/help/huawei-p8-blinks-red-green-green-red-t3546038
https://youtu.be/UYmDBD7t1iM
I have tried a lot of things to make the phone work again but nothing worked.
Recovery mode using HiSuite - "Your device is not supported for system recovery"
I have tried flashing different ROM's using fastboot - when I try flashing it says "FAILED - command not allowed", which I assume is beacuse the bootloader is locked?
installing a ROM using a SD card (Force update or something) - the red screen shows and the phone shuts down
Huawei Update Extractor - updating specific files e.g. boot.img, still not allowed to flash
TWRP - the same error ( not allowed )
Rollback to the previous versions using fastboot - not allowed
At some point I was able to wipe the cache on the phone, not sure if that matters anyhow.
When I am in the fastboot & rescue mode, there is a text in green saying "Phone LOCKED", which I assume means that the bootloader is locked? So, I was trying to get the bootloader unlocked, however found no success. I have also tried emailing Huawei support to get the bootloader code, however as you may know, they did not want to provide the code.
I was able to extract some information from the phone though, using these commands: https://forum.xda-developers.com/showpost.php?p=70483520&postcount=2
To get the bootloader code I have tried:
dc-unlocker - I think you need a working phone and have usb drivers installed for this to work and also I think you have to pay for this service
Kingroot + fastboot - https://forum.xda-developers.com/p8lite/general/alternative-method-unlocking-bootloader-t3799294
Emailing Huawei support for the code - they don't want to provide one
https://forum.xda-developers.com/huawei-p8/help/bootloader-unlock-unlock-code-huawei-t3792987
Does anyone have any suggestions on how to resolve the problem, or is it unsolvable? I would prefer to do it myself and not send the phone to Huawei or whoever as I would like to spend the least money possible. Also the warranty is long gone, since the phone has been bought in 2015.
Cheers
I have same issue, please anybody help
Exact same problem here, any help would be great.

HIFI Image Security Verify Error

Hello,
I have a Huawei P8 Lite (ALE-L21) phone with this error: FUNC 8 : HIFI Image, Error 1 Security Verify failed. I think I have tried everything to fix it but had no success, hence why I have decided to create this thread.
As you can figure out, the phone does not turn on, it only shows the huawei logo and shuts down. When pressing VOLUME UP + DOWN and POWER button, it used to show the HIFI image error screen, however when I press the key combination now, it only shows a red screen and turns off. I am able to enter fastboot and rescue mode by holding down the VOLUME DOWN button and plugging in a USB cable to the phone from a computer. Apart from that, I can't do anything else with the phone. (I do not have any software related to the phone installed (HiSuite), no backups, no nothing because the phone actually isn't mine and I have never actually played with it and androids in general.)
There are some similar threads and videos here:
https://forum.xda-developers.com/p8lite/help/stuck-rescue-mode-fastbootrescue-mode-t3648105
https://forum.xda-developers.com/p8lite/help/stuck-rescue-mode-screen-please-help-t3244872
https://forum.xda-developers.com/mate-10/how-to/how-to-huawei-mate-10-pro-standard-t3709535
https://forum.xda-developers.com/honor-5c/help/writing-recovery-failed-remote-command-t3584208
https://forum.xda-developers.com/p8lite/help/huawei-p8-blinks-red-green-green-red-t3546038
https://youtu.be/UYmDBD7t1iM
I have tried a lot of things to make the phone work again but nothing worked.
Recovery mode using HiSuite - "Your device is not supported for system recovery"
I have tried flashing different ROM's using fastboot - when I try flashing it says "FAILED - command not allowed", which I assume is beacuse the bootloader is locked?
installing a ROM using a SD card (Force update or something) - the red screen shows and the phone shuts down
Huawei Update Extractor - updating specific files e.g. boot.img, still not allowed to flash
TWRP - the same error ( not allowed )
Rollback to the previous versions using fastboot - not allowed
At some point I was able to wipe the cache on the phone, not sure if that matters anyhow.
When I am in the fastboot & rescue mode, there is a text in green saying "Phone LOCKED", which I assume means that the bootloader is locked? So, I was trying to get the bootloader unlocked, however found no success. I have also tried emailing Huawei support to get the bootloader code, however as you may know, they did not want to provide the code.
I was able to extract some information from the phone though, using these commands: https://forum.xda-developers.com/showpost.php?p=70483520&postcount=2
To get the bootloader code I have tried:
dc-unlocker - I think you need a working phone and have usb drivers installed for this to work and also I think you have to pay for this service
Kingroot + fastboot - https://forum.xda-developers.com/p8lite/general/alternative-method-unlocking-bootloader-t3799294
Emailing Huawei support for the code - they don't want to provide one
https://forum.xda-developers.com/huawei-p8/help/bootloader-unlock-unlock-code-huawei-t3792987
Does anyone have any suggestions on how to resolve the problem, or is it unsolvable? I would prefer to do it myself and not send the phone to Huawei or whoever as I would like to spend the least money possible. Also the warranty is long gone, since the phone has been bought in 2015.
Cheers
have you found any solution, i have same problem
Most likely the phone showning this kinds of errors is broken and can not be fixed by simple flashing operations.

[HELP] Redmi Note 4(3+64) RED STATE

I have a redmi note 4 mediatek variant and it's been stuck in bootloop for the past 2 days. It keeps restarting and doesn't go into fastboot mode.
The bootloader is locked. It won't go into recovery or fastboot. Sometimes it turns on when holding the power button but then goes into a bootloop.
This was the message last displayed on the phone:
RED STATE
YOUR DEVICE HAS FAILED VERIFICATION AND MAY NOT WORK PROPERLY
YOUR DEVICE WILL BOOT IN 5 SECONDS
And then it shut down and hasn't responded since.
Going to a service center probably won't help since this is a chinese variant and I live in India. The service centers here are mostly useless.
All help is greatly appreciated.
You can always try to do test point. Download official rom file and flasher, make sure to install fastboot drivers. Take apart your phone and connect two golden contacts on the motherboard while plugging in USB cable connected to PC. The phone should boot up to bootloader and you should be able to flash rom.
Test points should look like this: http://en.miui.com/thread-646232-1-1.html (scroll down, there is one photo)
If you need anything you can e-mail me on [email protected]
timipisoboy said:
You can always try to do test point. Download official rom file and flasher, make sure to install fastboot drivers. Take apart your phone and connect two golden contacts on the motherboard while plugging in USB cable connected to PC. The phone should boot up to bootloader and you should be able to flash rom.
Test points should look like this: http://en.miui.com/thread-646232-1-1.html (scroll down, there is one photo)
If you need anything you can e-mail me on [email protected]
Click to expand...
Click to collapse
I somehow got it working by completely draining out the battery and then booting. It worked for a while normally (around 30 min) and then went into a bootloop again.

Categories

Resources