Database Users

Meizu MX 4 Pro - Boot loop and firmware corrupt

Hi,
Bought the Meizu MX4 Pro recently. But upon first switch on, i got the screen showing: battery < 20%, cannot proceed with upgrade.
Now, once the battery was charged, i got the recovery screen to update and clean (With Flyme Logo), or to restart. Upon choosing restart, it stuck on the Flyme logo rotating...
I have downloaded the Flyme OS (5A, 4.5.7A, 4.5.7.1A, 4.5.7I) and placed it in the recovery drive of the mobile when connecting to a pc... but each and everytime, the screen shows checking firmware, then Firmware corrupt sign appears...
Thanks to point me in right direction... or what steps i need to follow to restore the mobile... I cannot find a dedicated forum for Meizu MX4 pro, only Meizu MX... i will try to post it there too, but if there is a better link please let me know...
Thanks,
Jinen

same problem! did you solve it? and even if i wanna clear data a screen with the unblock numbers appears and when i write my code i can't because there is just like 1 point every time i click instead 4 points so i must to restart again and the globe rotate again and system upgrade is always corrupt doesn't matter which firmware old or the latest... :S

Jinen_A said:
Hi,
Bought the Meizu MX4 Pro recently. But upon first switch on, i got the screen showing: battery < 20%, cannot proceed with upgrade.
Now, once the battery was charged, i got the recovery screen to update and clean (With Flyme Logo), or to restart. Upon choosing restart, it stuck on the Flyme logo rotating...
I have downloaded the Flyme OS (5A, 4.5.7A, 4.5.7.1A, 4.5.7I) and placed it in the recovery drive of the mobile when connecting to a pc... but each and everytime, the screen shows checking firmware, then Firmware corrupt sign appears...
Thanks to point me in right direction... or what steps i need to follow to restore the mobile... I cannot find a dedicated forum for Meizu MX4 pro, only Meizu MX... i will try to post it there too, but if there is a better link please let me know...
Thanks,
Jinen
Click to expand...
Click to collapse
Which your flyme version A o I? Do you remember the version that you have before flash? Try flash With 4.2.8.2(With the correct version A or I) good luck
Sent from my MX4 using Tapatalk

I have same problem.
javimad86 said:
same problem! did you solve it? and even if i wanna clear data a screen with the unblock numbers appears and when i write my code i can't because there is just like 1 point every time i click instead 4 points so i must to restart again and the globe rotate again and system upgrade is always corrupt doesn't matter which firmware old or the latest... :S
Click to expand...
Click to collapse
I have some problem with you, after I upgrade Firmware International to China. Before I don't now what firmware I use, I just follow step at internet tutorial upgrade Flyme OS, and I have wrong download firmware China. After that while I want to upgrade again the PIN password just can click only one number even though my PIN is 6 number. So while I click the first PIN the Command saya "Password is Wrong".
What I have to do please help me about this problem ...?

If your on (I) International download (I) version if your on (C) China download and so fourth. I found this site and it has worked for me https://www.flyme.cn/firmwarelist-7.html By the way Beta will never work on the Chinese model since they went with the only 3 traditional firmware upgrades for outside actual China itself! Hope this helps it owrked for me and I am on the Chinese model.

Nexus 4 stuck in Bootloop

Hi Guys,
I updated my N4 to CM13 with Android 6 via TWRP about two months ago and everything was fine. Today I accidentally deleted the System Partition through the TWRP Bootloader Application and the Phone logically does not boot up properly, it just freezes as the Google logo comes on.
The problem I am facing now is that i cant simply overwrite the OS with a fresh one, because my Computer does not recognize the Phone anymore.
When you go into the Bootloader Windows makes the typical sound effect but the phone does not show up as an external storage.
So I entered the printers and devices menu and it gives me this information : Model: Android Category: unknown
It is conspicious that the computer only recognises the phone when I enter the Bootloader by pressing power und vol down or when I am in the TWRP application.
The data on the phone is not important and I backed everything up, but I would really appreciate it when someone could help me to bring my phone to life again.
:good:
If I didnt express myself detailed enough just ask my everything.

MaxderGauner said:
Hi Guys,
I updated my N4 to CM13 with Android 6 via TWRP about two months ago and everything was fine. Today I accidentally deleted the System Partition through the TWRP Bootloader Application and the Phone logically does not boot up properly, it just freezes as the Google logo comes on.
The problem I am facing now is that i cant simply overwrite the OS with a fresh one, because my Computer does not recognize the Phone anymore.
When you go into the Bootloader Windows makes the typical sound effect but the phone does not show up as an external storage.
So I entered the printers and devices menu and it gives me this information : Model: Android Category: unknown
It is conspicious that the computer only recognises the phone when I enter the Bootloader by pressing power und vol down or when I am in the TWRP application.
The data on the phone is not important and I backed everything up, but I would really appreciate it when someone could help me to bring my phone to life again.
:good:
If I didnt express myself detailed enough just ask my everything.
Click to expand...
Click to collapse
Does fastboot recognize the device when in bootloader and/or does adb recognize the device in recovery? If so, it's easy to fix.
Sent from my Nexus 4 using XDA Labs

[Urgent help] Xiaomi Mi A1 Unlock bootloader

Hi All,
I'm new to this as I'm not an Android developer but a good Android user. Requesting moderator to update anything required.
I've Xiaomi mi A1 and it was working for the last 3 years. Last Sunday, it just got hanged while kids were playing with it(maybe multiple apps/videos/some ad clicked) and it got hanged.
I restarted and it stuck on "Android One" screen till now even after multiple attempts.
What I tried:
1. I tried to wipe/factory reset from the Android recovery option(power off + volume up) then it stuck there saying "Formatting data" and I've restarted it to come back to Android One screen after hours.
2. I tried using MiFlash tool and it continues throwing the error "remote device is locked. cannot erase".
Then I got to know bootloader must be unlocked. and for that:
1. I tried fast boot oem unlock but it just says OK and device reboots. When I check status back, it's again locked .
2.I tried to unlock it using MiFlashUnlock tool but it says not able to find account details as I may have logged in once but probably I may not have used Xiaomi as cloud instead I prefer Google cloud.
You can assume I'v already searched possibly all threads on the internet and added here all possible information.
Attached getvar-all.txt output

Is there anyone on the platform who knows on this issue?
Or it's just a platform of Ads?

oooooof, sounds like a harsh brick from some sort of malware downloaded into the device or your kids diddled with some kernel settings somehow
is your device running on qualcomm snapdragon? i have the fix for it in this site
but first try the update option on the recovery, might fix something

arshad4u said:
Hi All,
I'm new to this as I'm not an Android developer but a good Android user. Requesting moderator to update anything required.
I've Xiaomi mi A1 and it was working for the last 3 years. Last Sunday, it just got hanged while kids were playing with it(maybe multiple apps/videos/some ad clicked) and it got hanged.
I restarted and it stuck on "Android One" screen till now even after multiple attempts.
What I tried:
1. I tried to wipe/factory reset from the Android recovery option(power off + volume up) then it stuck there saying "Formatting data" and I've restarted it to come back to Android One screen after hours.
2. I tried using MiFlash tool and it continues throwing the error "remote device is locked. cannot erase".
Then I got to know bootloader must be unlocked. and for that:
1. I tried fast boot oem unlock but it just says OK and device reboots. When I check status back, it's again locked .
2.I tried to unlock it using MiFlashUnlock tool but it says not able to find account details as I may have logged in once but probably I may not have used Xiaomi as cloud instead I prefer Google cloud.
You can assume I'v already searched possibly all threads on the internet and added here all possible information.
Attached getvar-all.txt output
Click to expand...
Click to collapse
found some fix on a russian website, gonna translate it:
im gonna make a warning there off-script of the russian website, this is NOT guaranteed to work. if it doesnt, send it off for repairs.
what do you need to do this:
1 - fully charge the phone
2 - a working usb cable
3 - a computer with wifi on it (i can tell you have it since you likely posted it on the computer)
4 -you should have Mi flash pro
5 - a recovery image on chinese (WARNING: 1.9 GB, BE PATIENT)
6 - actually working braincells and hands ( you guaranteedly have em)
THE STEPS:
1 - Load in mi flash pro and register in it under your name (not always under your name)
2 - press recovery
3 - you should see a lightning bolt icon along with the IMEI of your device
4 - type in the path of the firmware
even if your device shows your system has been destroyed you can still boot into recovery.
5 - in your device boot into recovery
6 - you see connect with mi assistant? choose that option and confirm it
your device should direct you to connect the usb from your computer to your device
7 - After you setup everything you should see your device, if not, press refresh device, then you should see the flash button, press it
8 - and there begins the magic - wait 5-10 mins for the firmware to initialise, DO NOT DISCONNECT THE USB FROM YOUR DEVICE AT THIS POINT, IF YOU DO, YOU WILL SCREW IT UP AND HAVE TO DO IT ALL OVER AGAIN!
if you dont screw up and your device actually boots congratualtions! the power of xi jing ping has restored your phone to normal with a small drawback - its all in chinese
worry not, it doesnt end here:
9 - Unlock the bootloader AKA Unlock OEM (This is important, because otherwise you will brick yourself again and will have to do it all over again)
10 - boot your device into fast boot and flash the global firmware onto your device (the global firmware can be found on the same xiaomiui website you got the chinese firmware from)
i hope this lengthy guide helps

arshad4u said:
Hi All,
I'm new to this as I'm not an Android developer but a good Android user. Requesting moderator to update anything required.
I've Xiaomi mi A1 and it was working for the last 3 years. Last Sunday, it just got hanged while kids were playing with it(maybe multiple apps/videos/some ad clicked) and it got hanged.
I restarted and it stuck on "Android One" screen till now even after multiple attempts.
What I tried:
1. I tried to wipe/factory reset from the Android recovery option(power off + volume up) then it stuck there saying "Formatting data" and I've restarted it to come back to Android One screen after hours.
2. I tried using MiFlash tool and it continues throwing the error "remote device is locked. cannot erase".
Then I got to know bootloader must be unlocked. and for that:
1. I tried fast boot oem unlock but it just says OK and device reboots. When I check status back, it's again locked .
2.I tried to unlock it using MiFlashUnlock tool but it says not able to find account details as I may have logged in once but probably I may not have used Xiaomi as cloud instead I prefer Google cloud.
You can assume I'v already searched possibly all threads on the internet and added here all possible information.
Attached getvar-all.txt output
Click to expand...
Click to collapse
crud, i forgot the critical part:
it doesnt boot you to the average xiaomi screen, its the A1 model
at this point you need to use the ADB to flash the chinese firmware and unlock the bootloader on the chinese firmware, then flash the global one
though you can still use the same method i typed above

How's the progress so far?

Lamntox said:
oooooof, sounds like a harsh brick from some sort of malware downloaded into the device or your kids diddled with some kernel settings somehow
is your device running on qualcomm snapdragon? i have the fix for it in this site
but first try the update option on the recovery, might fix something
Click to expand...
Click to collapse
I tried recovery also try to format the disc with recovery mode(power on + Volume up ) but then it stuck on the formatting disc... line

arshad4u said:
I tried recovery also try to format the disc with recovery mode(power on + Volume up ) but then it stuck on the formatting disc... line
Click to expand...
Click to collapse
Yup, the device is probs bricked
Have you tried the other methods i described?

arshad4u said:
Hi All,
I'm new to this as I'm not an Android developer but a good Android user. Requesting moderator to update anything required.
I've Xiaomi mi A1 and it was working for the last 3 years. Last Sunday, it just got hanged while kids were playing with it(maybe multiple apps/videos/some ad clicked) and it got hanged.
I restarted and it stuck on "Android One" screen till now even after multiple attempts.
What I tried:
1. I tried to wipe/factory reset from the Android recovery option(power off + volume up) then it stuck there saying "Formatting data" and I've restarted it to come back to Android One screen after hours.
2. I tried using MiFlash tool and it continues throwing the error "remote device is locked. cannot erase".
Then I got to know bootloader must be unlocked. and for that:
1. I tried fast boot oem unlock but it just says OK and device reboots. When I check status back, it's again locked .
2.I tried to unlock it using MiFlashUnlock tool but it says not able to find account details as I may have logged in once but probably I may not have used Xiaomi as cloud instead I prefer Google cloud.
You can assume I'v already searched possibly all threads on the internet and added here all possible information.
Attached getvar-all.txt output
Click to expand...
Click to collapse
Hi i dont have that kind of a problem!
my problem is when i try to do oem unlock it says error 0x1002 and idk what to do (i have same phone btw) i tried anything but nothing works!

(SOLVED) Urgent ! My OP8P is dead I think, stuck Fastboot

Hello everyone !
I'm new on this forum but I really need your help. I tried to fix my mistake all day long yesterday (9am to 2am non stop).
So, basically, I have a OnePlus 8 Pro, Model IN2023.
I had OOS 11 updated. I tried to install OOS 12 Bêta and I did but I had a indian version so a lot of bugs.
I wanted to go back to OOS 11 but it was impossible because I was now in an indian version.
I tried with MyApplication2 to local upgrade and downgrade as recommand in Internet.
I tried to unlock bootloader and the following steps but here my problem:
I unlocked my bootloader then I misclick and I locked again my bootloader.
Then my phone just crashed and put this message:
"The current image (boot/recovery) have been destroyed and can not boot."
So, I forced to turn off the phone and try to go in EDL mode but:
1. ADB doesn't work anymore
2. Fastboot work fine
3. EDL mode is impossible
So, my bootloader is unlocked again. My phone is stuck on Fastboot mode:
Fastboot mode
Product_name - kona
Variant - SM8 UFS
Bootloader version -
Baseband version -
Serial number - eed52b71
Secure boot - yes
Device state - unlocked
I used the official firmware on OnePlus website, I used Python and Payload_dumper.py to have the .img from the .bin of the official firmware.
I tried to flash all the images, I tried to install TWRP, I tried almost everything I found but still stuck in Fastboot. Recovery mode doesn't work.
I tried to boot, to flash, to do everything I could.
I also tried MSM Download Tool but nothing appears inside.
Now, when I connect my phone, it's with a cable in USB-C but 3.0, not 2.0. Maybe that's the problem ?
When I plug my phone, in Device Manager, I have a "!" but the phone is recognized under
"Qualcomm HS-USB QDLoader 9008 (COM6). When I click on it, it says (sorry, I'm about to translate from french):
"Windows can not verify the numeric signature for the drives required for this peripheric. It is possible that a material ou software modification has been installed a corrupted file or with an incorrect signature, or it is a malware from an unknown source (Code 52)"
Please help me, contact me on Whatsapp, or here. Let's do this in direct.
Btw, I have a Macbook Pro to do all this. I used also Windows with Bootcamp.

So... I finally did it. 2 days to do it.
I asked a friend to lend his computer (Windows).
So my phone turned into EDL Mode immediatly without trying to do so.
I plugged into my MacBook under Windows (Bootcamp) and launch MSM Download Tool under an old version and it worked.
I tried first with the latest but I had "param preload failed" so I found a good article MAGIC and tada.
SUCCESS. My OnePlus 8 Pro works better than never.
Don't install OxygenOS 12, it's really bad.

andshura said:
So... I finally did it. 2 days to do it.
I asked a friend to lend his computer (Windows).
So my phone turned into EDL Mode immediatly without trying to do so.
I plugged into my MacBook under Windows (Bootcamp) and launch MSM Download Tool under an old version and it worked.
I tried first with the latest but I had "param preload failed" so I found a good article MAGIC and tada.
SUCCESS. My OnePlus 8 Pro works better than never.
Don't install OxygenOS 12, it's really bad.
Click to expand...
Click to collapse
Im happy you fixed your phone.
Read this before you even think to go to A12 again on this device.
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com

Bricked Nokia 6 TA-1021

Hello everyone, I have a Nokia 6 TA-1021 that I think is soft bricked as it does not get past the Nokia logo on boot, but it can go in recovery and download modes. My PC correctly recognizes the phone when using fastboot.
I did not unlock the bootloader previously (only used it as a plain user, no custom roms, no root, only OTA updates...). Also, I never turned on the "Allow OEM unlock" flag when the phone was working. I think it was running Android 9 Pie, but I'm not 100% sure, could also be Android 8 Oreo.
I don't know exactly how and when it did get into this situation, because when I changed my phone two years ago it was still working (I even booted it up a couple times last year). Then I wanted to boot it up last week and found this situation.
I've been looking inside the entire Nokia 6 section here to find a possible solution to no luck.
I managed to get a stock firmware to be flashed with OST LA, but as I said, the bootloader is not unlocked and the "Allow OEM unlock" switch is off, so I'm pretty much stuck.
I don't know if this helps, but in recovery mode it displays an error message that reads "E:[libfs_mgr]dt_fstab: Failed to find device for partition system". Also, I tried to do a factory reset a couple times, also to no luck.
Can this phone be unbricked? ANY help will be much appreciated!