Related
Hello Everyone. I'm trying to downgrade the software on my Asus Zenfone 2 to version 2.19.40.20 (currently 2.19.40.20) so I can unlock my bootloader. I've heard that the way to do this is following rooting procedure 1 from the main information thread but flashing the version of the files that you want your system to be. However when I download the zip it has the system.img file broken up in some weird way (apparently you need a tool called WinRar to put it back together again but I really don't want to have to go buy a piece of software I'm only gonna need once). Does anyone know how to put the files back together again, have a put together 2.19.40.20 system.img I can use or have some alternative solution to my problem. I'm currently using a Linux system too so if at all possible I would like for any software to be compatible with Linux. If anyone has any insight I would be highly appreciative.
Don't try to flash selectively, as that is very likely to brick your phone. What you want is the correct full ROM package containing a system.img, boot.img/kernel, fastboot (droidboot.img IIRC), IFWI.zip, and some other important partitions whose names escape me. Don't try to extract parts of it (e.g. just the system.img, boot.img, or bootloader), because the components appear to be interdependent. In particular, flashing the wrong version of the bootloader without flashing the corresponding kernel/system image will more than likely brick it. You should be able to supply the full ROM to fastboot (e.g. fastboot update <package_file>). Double check everything and back up before you proceed! @Tuanies should have some pointers for you in case I missed anything, and I would wait to hear from him before you try this.
WinRAR is free. It's a very small program that takes seconds to download and install. It is very simple to put the system image components back together with WinRAR and then you will have that file plus the other three you need. Please try it, I'm sure you'll manage it.
All I suggest is to get the full firmware of 2.19.40.20 and flash the images one by one, and sideload the firmware using adb...
Hope this helps
Good luck.
I'd just download the full package from that's ~1GB and sideload that via recovery in its entirety. If this is too complicated, I'd advise against attempting it.
Seriously it is just about writing 3 lines on adb... Not that hard
Sent from my ASUS_Z008D using Tapatalk
I did finally manage to get WinRar working. I had to go install it on my brother's computer. After I had the files to flash I had no trouble.
This seems like a good place to ask this I was on .22 and tried unlocking boot loader did not seem to work so I went back into my 2.19 folder and flashed back to 2.19 but was still unable to unlock though it appears possibly unlocked on boot loader shows bootloader unk and question marks on last 2 entries, but apparently I am unable to flash over the bootloader in fastboot it says fail cmd err can anyone tell me what that means? And how to get around it, tried flashing non tethered twrp says it wrote it but won't boot to it
Sent from my ASUS_Z00AD using Tapatalk
You must have done something wrong. I had the two question marks before I unlocked mine. When your bootloader is unlocked your boot screen will be white. If you're not sure what I'm talking about then you're not unlocked.
robopilot99 said:
You must have done something wrong. I had the two question marks before I unlocked mine. When your bootloader is unlocked your boot screen will be white. If you're not sure what I'm talking about then you're not unlocked.
Click to expand...
Click to collapse
Okay so I never have gotten the white boot screen and just not sure where to go from here does not seem to want me to flash a droidboot.img and I cannot seem to figure out how to make it take the img I can go back to 4.19 from 4.22 but from there I have tried using adb and terminal emulator to give the commands and after reboot to bootloader it just sits there, so am on 4.22's bootloader and is that why it won't work and would you suggest to get the bootloader unlocked?
---------- Post added at 06:09 PM ---------- Previous post was at 05:58 PM ----------
jimchee said:
Okay so I never have gotten the white boot screen and just not sure where to go from here does not seem to want me to flash a droidboot.img and I cannot seem to figure out how to make it take the img I can go back to 4.19 from 4.22 but from there I have tried using adb and terminal emulator to give the commands and after reboot to bootloader it just sits there, so am on 4.22's bootloader and is that why it won't work and would you suggest to get the bootloader unlocked?
Click to expand...
Click to collapse
The img's I am flashing are from shakalaka, hope thats spelled right
so in fastboot and using adb i did fastboot flash droidboot droidboot.img (enter)
sending droidboot (14410 kb)
Okay (0.622s)
writing "droidboot"
FAILED < Remote: flash_cmds error !
so this is the answer I am getting when trying to flash droidboot
so any ideas would be great
jimchee said:
Okay so I never have gotten the white boot screen and just not sure where to go from here does not seem to want me to flash a droidboot.img and I cannot seem to figure out how to make it take the img I can go back to 4.19 from 4.22 but from there I have tried using adb and terminal emulator to give the commands and after reboot to bootloader it just sits there, so am on 4.22's bootloader and is that why it won't work and would you suggest to get the bootloader unlocked?
---------- Post added at 06:09 PM ---------- Previous post was at 05:58 PM ----------
The img's I am flashing are from shakalaka, hope thats spelled right
so in fastboot and using adb i did fastboot flash droidboot droidboot.img (enter)
sending droidboot (14410 kb)
Okay (0.622s)
writing "droidboot"
FAILED < Remote: flash_cmds error !
so this is the answer I am getting when trying to flash droidboot
so any ideas would be great
Click to expand...
Click to collapse
I had to flash 4 files as it appears you are trying to do. The error is definitely not good. I'm not sure what it means though. Hopefully someone else knows what to do. I'm pretty sure being on this up to date bootloader is your issue. Did you manage to somehow flash the other 3 files?
robopilot99 said:
I had to flash 4 files as it appears you are trying to do. The error is definitely not good. I'm not sure what it means though. Hopefully someone else knows what to do. I'm pretty sure being on this up to date bootloader is your issue.
Click to expand...
Click to collapse
Yep I figure that might be it, just not sure what to do next, every other file flashes whether I am going up or down thinking of trying to flash older than 19 and then hopefully able to its to 2.19, but hopefully someone knows the proper way
Sent from my ASUS_Z00AD using Tapatalk
The files that I flashed I got from here. Don't know if that's where you are getting yours.
What I did is I downgraded to version Z00A_WW_2.19.40.18 of everything (I was warned about flashing different versions of different things so be careful). I then used the bootloader unlock method detailed in section 5 of the resource thread. I think your problem is that the files you are flashing are not pre-rooted. I used the files from section 3.1, method 1 of the same thread. The system.img was broken up in some strange fashion but I can send you the put together version somehow if you would like.
robopilot99 said:
What I did is I downgraded to version Z00A_WW_2.19.40.18 of everything (I was warned about flashing different versions of different things so be careful). I then used the bootloader unlock method detailed in section 5 of the resource thread. I think your problem is that the files you are flashing are not pre-rooted. I used the files from section 3.1, method 1 of the same thread. The system.img was broken up in some strange fashion but I can send you the put together version somehow if you would like.
Click to expand...
Click to collapse
I am using the pre rooted ones from shakalaka and i can get boot, recovery and system to flash but unable to get droidboot to flash and that is what I can't figure out even when i downgrade with all the other files i can't get bootloader unlocked
I couldn't find the files you were referring too. However I really don't know enough about fastboot to really help you resolve the error message. Hopefully someone a little more experienced will come along soon.
robopilot99 said:
I couldn't find the files you were referring too. However I really don't know enough about fastboot to really help you resolve the error message. Hopefully someone a little more experienced will come along soon.
Click to expand...
Click to collapse
They are the same files that you are using from mega.nz and my fastboot knowledge is not great either, so I'll just wait around and see if anyone with more knowledge can help me out, thanks for yoyr help though it's appreciated
@jimchee you are typing the wrong command to flash droidboot. its "fastboot flash fastboot droidboot.img"
Niropa said:
@jimchee you are typing the wrong command to flash droidboot. its "fastboot flash fastboot droidboot.img"
Click to expand...
Click to collapse
Thanks Niropa, I knew there was reason this works now I really appreciate the help
Just a quick note to let everyone know that everything worked without a hitch now have unlocked bootloader and twrp installed.
Sent from my ASUS_Z00AD using Tapatalk
I cant seem to find it in the forums, only for the 551ML... can someone help me? I figured out its via Asus flash tool...
Does it matter if i use WW or CN?
Don't go near raw unless you are bricked.
Just unroot, flash stock recovery, sideload stock firmware ...if you phone is working ?
timbernot said:
Don't go near raw unless you are bricked.
Just unroot, flash stock recovery, sideload stock firmware ...if you phone is working ?
Click to expand...
Click to collapse
That simple? But if i flash stock recovery, how can i do ADB sideload since i doubt i can boot into CM13 on stock recovery?
Anyway, do you have a concrete guide? something safe i can follow, i see many guides and its kinda confusing.
EDIT: Okay I found something, basically flash stock recovery... from somewhere? I guess its in the zip folder of the firmware im flashing (extract it out?)
then reboot into stock recovery mode, choose adb sideload...
enter commands to adb side stock firmware filename.zip?
profit?
Messing with phones is risky..nothing's ever concrete , the risks are outlayed when flashing custom roms and still applies. Heavens knows what might have happened trying to flash raw for a brilliant example !
That outta the way...
Yup , you going right so far except you need recovery.img if on ze550ml .latest recovery for an example for latest fw
Rename latest fw WW- BLA blah fw for example to MOFD_SDUPDATE and put it in adb fastboot folder.
ADB SIDELOAD CMD after booting in stock rec...>
adb sideload MOFD_SDUPDATE.zip
All risks are still applied to you and you only
Ps, if you bought this phone with CM already on...you need knowledge of running fastboot and adb before even contemplating.
timbernot said:
Messing with phones is risky..nothing's ever concrete , the risks are outlayed when flashing custom roms and still applies. Heavens knows what might have happened trying to flash raw for a brilliant example !
That outta the way...
Yup , you going right so far except you need .184 recovery.img if on ze551ml .184 fw for an example.
Rename latest fw WW- BLA blah fw for example to MOFD_SDUPDATE and put it in adb fastboot folder.
ADB SIDELOAD CMD after booting in stock rec...>
adb sideload MOFD_SDUPDATE.zip
All risks are still applied to you and you only
Ps, if you bought this phone with CM already on...you need knowledge of running fastboot and adb before even contemplating.
Click to expand...
Click to collapse
LOL true true, I dont disagree with ya... well i was the one who put that phone into CM13 but i gave it to someone, now im trying to revert it back to stock like since Feb as shes just a regular user and CM13 its kinda unstable for her usage...
Okay i downloaded from asus global website .... UL-Z008-WW-2.20.40.149-user.zip
but inside I only see boot.img and droidboot.img... there's no stock recovery image... there's a recovery folder though
\recovery\recovery-from-boot.p
\recovery\bin\install-recovery.sh
How can i extract the recovery img or... im lost at this part... And im also suppose to flash boot.img and droidboot.img right?
https://mega.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw
timbernot said:
https://mega.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw
Click to expand...
Click to collapse
omg bro, where did u find this repository from? Its like exactly the same as the Official asus zip but... with recovery.zip and...root?!
From general thread above
http://forum.xda-developers.com/zenfone2/general/android-6-0-beta-root-xposed-downgrade-t3404321
Lol
timbernot said:
From general thread above
http://forum.xda-developers.com/zenfone2/general/android-6-0-beta-root-xposed-downgrade-t3404321
Lol
Click to expand...
Click to collapse
lol... i inspected the file contents...
I got a feeling i can just simply fastboot flash everything since its all in .img files...
flash recovery boot and droidboot... reboot... then flash system.img...
How did you do ?
For the benefit of others who may be in the same boat , what did you do ?
Hi,
I have the flickering screen problem with my phone and it is out of warranty so i can't send it back to repair.
I tried upgrading to the latest firmware, tried factory reset, wipe cache, installing google launcher, enabling the HW thing in developer mode and nothing worked.
I read that WW_2.12.40.11 version doesn't have the screen problem and i want to try it, but i wanna be sure i'm doing it the right way.
1) I read that i can't just put the wanted firmware in my phone and install the update but i must also flash the matching recovery to flash the wanted version - is it true?
2) Can i downgrade straight from my version to the lower one because i think the other way around, i need to have higher version for upgrading to the higher version i now have.
3) Where can i find the adb driver for this?
Thanks
You can downgrade via ext sd card using the downgrade version from asus > 52.20.40.196 LP which when installed , reboots to 2.20.40.196LP
When putting WW-UL- 52.20.40.196.zip.zip ,make sure to put an extra .zip on the end in file manager or in sd from pc first and reboot.
If you then put WW-UL-2.12.40.11-user.zip.zip (extra .zip) on sd or in file manager . You might get that to give you notification after a reboot too. Although i have not tested to downgrade that far .
You must use the first 52.20 blah blah fw to initially downgrade first though. Ignore this and you are liable to brick. Here >
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-52.20.40.196-user.zip
See my downgrade via ext sd video and thread , familiarise yourself with the process first !
https://forum.xda-developers.com/zenfone2/help/success-downgrade-mm-to-lp-via-sd-card-t3520642
Any questions , just ask
timbernot said:
You can downgrade via ext sd card using the downgrade version from asus > 52.20.40.196 LP which when installed , reboots to 2.20.40.196LP
When putting WW-UL- 52.20.40.196.zip.zip ,make sure to put an extra .zip on the end in file manager or in sd from pc first and reboot.
If you then put WW-UL-2.12.40.11-user.zip.zip (extra .zip) on sd or in file manager . You might get that to give you notification after a reboot too. Although i have not tested to downgrade that far .
You must use the first 52.20 blah blah fw to initially downgrade first though. Ignore this and you are liable to brick. Here >
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-52.20.40.196-user.zip
See my downgrade via ext sd video and thread , familiarise yourself with the process first !
https://forum.xda-developers.com/zenfone2/help/success-downgrade-mm-to-lp-via-sd-card-t3520642
Any questions , just ask
Click to expand...
Click to collapse
Thanks alot
Just a question before i try your method: I already installed 2.12.40.11 recovery.img into the phone. can i still use your method or should i first flash 4.21.40.223 recovery.img back to the phone?
gifnooky said:
Thanks alot
Just a question before i try your method: I already installed 2.12.40.11 recovery.img into the phone. can i still use your method or should i first flash 4.21.40.223 recovery.img back to the phone?
Click to expand...
Click to collapse
OK, it's weird, i did flash the 2.12.40.11 recovery.img to the phone using adb and it was said in the console that the process completed, but now when i enter recovery mode it still shows me 4.21.40.223 version.
OK, I did downgrade with your method and it works great, but when i try to downgrade fro that version to the version i want to try i get error that i cant install the package over the existing newer version.
Just to inform.
gifnooky said:
OK, I did downgrade with your method and it works great, but when i try to downgrade fro that version to the version i want to try i get error that i cant install the package over the existing newer version.
Just to inform.
Click to expand...
Click to collapse
If you want to downgrade to such an old version, find the .raw file of that version (search here on XDA) and flash it via Asus Flash Tool.
JBolho said:
If you want to downgrade to such an old version, find the .raw file of that version (search here on XDA) and flash it via Asus Flash Tool.
Click to expand...
Click to collapse
Thanks for the advice.
I searched and found raw firmware versions but no the one i'm looking for.
Is there any way i can install the official firmware i have? i also found recovery.img, boot.img, droidboot.img of the version i want.
gifnooky said:
Thanks for the advice.
I searched and found raw firmware versions but no the one i'm looking for.
Is there any way i can install the official firmware i have? i also found recovery.img, boot.img, droidboot.img of the version i want.
Click to expand...
Click to collapse
If you have all the img partitions you can always try installing via fastboot commands but i really recommend using a raw with Asus Flash Tool...
Hai friend try flash 3 file of boot.img recovery.img and droidboot.img version 40.11.. and then flash rom with adb sideload.. its work for me... and solve my prob flicker display..
Sent from my ASUS_Z00AD using Tapatalk
savve said:
Hai friend try flash 3 file of boot.img recovery.img and droidboot.img version 40.11.. and then flash rom with adb sideload.. its work for me... and solve my prob flicker display..
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
Hi, thanks i'l try that.
does it matter in what order i flash this 3 files?
Edit: If i already flashed the ROM can i just flash the boot.img and droidboot.img or do i need to do the whole process including flashing the ROM again?
Is your screen flickering problem like this: https://www.youtube.com/watch?v=kRuxTefNcKw
If its like that I was told its a LCD hardware problem which gets fixed by replacing LCD.
Update:
Well, I installed firmware 2.12.40.11 and it worked fine for several days but then the screen started to flicker again.
i started to update the devices with OTA updates and then i saw that in firmware WW_2.20.40.174 the screen didn't flicker.
i had further updates and then the screen started to flicker again.
i tried to flash recovery.img, boot.img and droidboot.img but not the device only enters fastboot mode but when i try to enter normal boot or recovery mode, it only comes back to fast boot mode.
any suggestion what should i do to unbrick the phone?
Thanks
Recently I got my Note 5 and have been enjoying it, unlocked and custom ROM and everything with the latest TWRP. But recently I've wanted to flash a different custom ROM and everytime I do so, I get the error message:
E10001: Failed to update system image.
Updater process ended with Error 7: Error installing zip file xxx (xxx is just the filename)
No matter what ROM I flash, whether it is the Xiaomi.eu ROM or any other custom AOSP/LOS ROM, I get the same message.
I need help as I have no idea what to do at all and am worried that the phone might be messed up permanently.
Download notepad++ and 7zip. Unzip the file, go to meta.inf/com/google/android and open updater script with notepad++. Select and delete the assert lines, and make sure to remove the empty space. Zip the file and flash it.
ensure your phone is note 5 pro, not note 5
BlackHawk580 said:
Recently I got my Note 5 and have been enjoying it, unlocked and custom ROM and everything with the latest TWRP. But recently I've wanted to flash a different custom ROM and everytime I do so, I get the error message:
E10001: Failed to update system image.
Updater process ended with Error 7: Error installing zip file xxx (xxx is just the filename)
No matter what ROM I flash, whether it is the Xiaomi.eu ROM or any other custom AOSP/LOS ROM, I get the same message.
I need help as I have no idea what to do at all and am worried that the phone might be messed up permanently.
Click to expand...
Click to collapse
Could you solve the error?
Same issue here. If you updated to the most recent firmware, then it's impossible to flash anything using the TWRP recoveries available. I get the same E1001 error. I don't think it has anything to do with the model or the ROM. Be careful, because trying to reflash a firmware package will result in a hard brick, and you need to use an ARB authorisation bypass to be able to restore your phone.
For now I have to stay on the latest Global ROM, nothing else I can do.
wrathking said:
Download notepad++ and 7zip. Unzip the file, go to meta.inf/com/google/android and open updater script with notepad++. Select and delete the assert lines, and make sure to remove the empty space. Zip the file and flash it.
Click to expand...
Click to collapse
I tried this with the Xiaomi.eu ROM - no luck, same error. It's not about the ID of the device (TWRP reports that my device is indeed whyred), it's something else.
Mi rom
stephendt0 said:
Same issue here. If you updated to the most recent firmware, then it's impossible to flash anything using the TWRP recoveries available. I get the same E1001 error. I don't think it has anything to do with the model or the ROM. Be careful, because trying to reflash a firmware package will result in a hard brick, and you need to use an ARB authorisation bypass to be able to restore your phone.
For now I have to stay on the latest Global ROM, nothing else I can do.
I tried this with the Xiaomi.eu ROM - no luck, same error. It's not about the ID of the device (TWRP reports that my device is indeed whyred), it's something else.
Click to expand...
Click to collapse
Have you tried using miflash tool?
wrathking said:
Have you tried using miflash tool?
Click to expand...
Click to collapse
Yes. This triggers a hard brick.
Hey I have the same issue on a redmi 5 plus; does anyone found a solution for this? I updated to the last firmware too, and the only rom that works now is evolutionX.
i think i have a solution for this problem, i solved it on my redmi note 3, if anyone is active here, give reply, i will help u........
deepinsys said:
i think i have a solution for this problem, i solved it on my redmi note 3, if anyone is active here, give reply, i will help u........
Click to expand...
Click to collapse
I'm alive
deepinsys said:
i think i have a solution for this problem, i solved it on my redmi note 3, if anyone is active here, give reply, i will help u........
Click to expand...
Click to collapse
Hi, I'm facing the same issue. Can you help me bro? Thank you.
Check whether you are using latest twrp or Orange fox recovery. If not ,then update it. I guess this should solve the problem.
I am not responsible for any brick.
I tested this guide myself and decided to share it.
Make a backup before this guide because you will lose your data!
The unlock method has been updated and now you can unlock the bootloader more easily without the risk of bricking after an OTA and without changing the bootloader.
Now you can safely unlock the bootloader using mtkclient.
Link: https://github.com/bkerler/mtkclient
TWRP can be installed via mtkclient or manually from rooted Android.
TWRP Download link: https://github.com/XRedCubeX/twrp_meizu_m5c/releases
IF you unlocked the bootloader with the old method you can follow these steps:
1) Download the attached package.
2) Download OTA zip from flyme, link: http://www.flymeos.com/firmwarelist?modelId=70&type=1
3) Download the latest version of SP Flash Tool.
4) Download MTKClient and follow the instructions to install it.
5) Power off the phone and keep unplugged it from PC.
6) Open SP Flash Tool, select the downloaded package and select all partitions, then press the download button, don't plug phone for now.
7) Boot to recovery with vol +, plug the phone on PC, depending on recovery, TWRP or stock, use adb sideload or put update.zip in internal memory and install the zip.
8) Let the phone reboot or reboot it manually.
9) Now start the flash from SP Flash tool automatically, let it finish.
10) After the flash, unplug the phone and reboot into recovery.
11) Paste the update.zip in the phone and flash it.
12) After reboot, let your phone reboot into android and power off.
13) You can follow the guide to unlock bootloader with mtkclient.
FAQ:
A) But will I lose the data with this guide?
Yes.
Make sure to back up your data in any case!
B) But this guide is a bit different than usual, where is "fastboot oem unlock"? Or "fastboot flashing unlock"?
Meizu has not implemented an unlock command and in this case to unlock the bootloader we have to use a tool that makes us change the unlock status.
C) Are there Custom ROMs?
There is only one custom ROM for this device, the Lineage OS 14 but I advise against using it because it has a bit of a bug but I haven't had more time to work on it yet.
D) But wasn't the guide different?
It has been updated with a better method with more advantages.
E) My device is in Hard Brick! How can I solve?
There are various types of Hard Brick and it depends from situation to situation.
F) I have installed Lineage OS 14 but I am not satisfied, I want to go back to Flyme!
Flash update.zip from official website.
G) Can I relock the bootloader?
From MTKClient readme:
for relocking use:
python mtk da seccfg lock
Click to expand...
Click to collapse
H) TWRP? I am interested in Device Tree, where is the link?
Here: https://github.com/XRedCubeX/twrp_meizu_m5c
I) I have a Meizu A5 (Chinese M5c) will it work on it?
I can't assure you anything but it could work, the only way to be sure is to test on a Meizu A5.
J) Can I flash twrp from fastboot?
Fastboot refuses to flash partitions, strangely, I don't know if downgrade or anything changes the situation but for now I was able to flash it with mtkclient.
I can remove the FlameOs from the Meizu M5c and install a custom rom. So far I haven't found any rom for this device?
Mortaux said:
I can remove the FlameOs from the Meizu M5c and install a custom rom. So far I haven't found any rom for this device?
Click to expand...
Click to collapse
Im working on a Lineage OS 14 for this device.
I tried the procedure and it failed. Apparently it just formatted it but couldn't finish the process, returned an error. Then I tried to reinstall the stock ROM and it generated the error S_BROM_DOWNLOAD_DA_FAIL (0x7D4) & 2004). Now my phone is off and I can't turn it on anymore.
I tried this method but it didn't work:
HOW TO FIX FLASH TOOLS ERROR S_BROM_DOWNLOAD_DA_FAIL (0x7D4) & 2004) FOR MTK PHONES
HOW TO FIX FLASH TOOLS ERROR S_BROM_DOWNLOAD_DA_FAIL (0x7D4) & 2004) FOR MTK PHONES FIX FOR SP FLASH TOOLS ERROR S_BROM_DOWNLOAD_DA_FAIL (0x7D4) AND (2004) Follow the following steps: 1. Get SP flash tools (Latest version) 2. Download your...
forum.xda-developers.com
I know it's my responsibility, but I don't know what else to do. Could someone please help me?
thiagosousa777 said:
I tried the procedure and it failed. Apparently it just formatted it but couldn't finish the process, returned an error. Then I tried to reinstall the stock ROM and it generated the error S_BROM_DOWNLOAD_DA_FAIL (0x7D4) & 2004). Now my phone is off and I can't turn it on anymore.
I tried this method but it didn't work:
HOW TO FIX FLASH TOOLS ERROR S_BROM_DOWNLOAD_DA_FAIL (0x7D4) & 2004) FOR MTK PHONES
HOW TO FIX FLASH TOOLS ERROR S_BROM_DOWNLOAD_DA_FAIL (0x7D4) & 2004) FOR MTK PHONES FIX FOR SP FLASH TOOLS ERROR S_BROM_DOWNLOAD_DA_FAIL (0x7D4) AND (2004) Follow the following steps: 1. Get SP flash tools (Latest version) 2. Download your...
forum.xda-developers.com
I know it's my responsibility, but I don't know what else to do. Could someone please help me?
Click to expand...
Click to collapse
You unplugged the device while it was formatting, consequently it no longer has the bootloader, that error means that the device needs an authorization file that unfortunately only meizu has, shortly if I can try to release a tool to unbrick it in cases similar to these
XRed_CubeX said:
You unplugged the device while it was formatting, consequently it no longer has the bootloader, that error means that the device needs an authorization file that unfortunately only meizu has, shortly if I can try to release a tool to unbrick it in cases similar to these
Click to expand...
Click to collapse
It's a shame .. I hope you can really release this tool, so I can revive my phone. Thank you.
You can make a video on youtube showing the procedure on the Meizu M5c. Installing Twrp and LineageOs 14? Just to make sure it works
Mortaux said:
You can make a video on youtube showing the procedure on the Meizu M5c. Installing Twrp and LineageOs 14? Just to make sure it works
Click to expand...
Click to collapse
For now I can't make the video because I can't release the Lineage because I'm fixing some bugs and I want to do some checks before releasing it publicly
thiagosousa777 said:
It's a shame .. I hope you can really release this tool, so I can revive my phone. Thank you.
Click to expand...
Click to collapse
Ok i found a working guide, tried on my M5c and it works:
Search on YouTube: flash mtk without da ,
You will find a video called, just exactly as I write here: "How to flash MTK secure boot devices without a custom DA" and follow the video tutorial for unbrick your device.
P.S:Obviously when the guide ends you flash the ROM from SP flash tool as you normally would
XRed_CubeX said:
Ok i found a working guide, tried on my M5c and it works:
Search on YouTube: flash mtk without da ,
You will find a video called, just exactly as I write here: "How to flash MTK secure boot devices without a custom DA" and follow the video tutorial for unbrick your device.
P.S:Obviously when the guide ends you flash the ROM from SP flash tool as you normally would
Click to expand...
Click to collapse
I'll try that, thanks a lot!
thiagosousa777 said:
I'll try that, thanks a lot!
Click to expand...
Click to collapse
Did you finally manage to fix the device?
Were you able to get on with the guide?
XRed_CubeX said:
Did you finally manage to fix the device?
Were you able to get on with the guide?
Click to expand...
Click to collapse
I haven't had time to do it yet. When I have time I will follow the tutorial and tell you if it worked.
thiagosousa777 said:
I haven't had time to do it yet. When I have time I will follow the tutorial and tell you if it worked.
Click to expand...
Click to collapse
Ok good luck
XRed_CubeX said:
Ok good luck
Click to expand...
Click to collapse
XRed_CubeX, I followed the tutorial from start to finish. I used the SP Flash Tool to install the M5c stock ROM, the ROM was flashed 100%, but after disconnecting the USB cable the phone did not turn on.
thiagosousa777 said:
XRed_CubeX, I followed the tutorial from start to finish. I used the SP Flash Tool to install the M5c stock ROM, the ROM was flashed 100%, but after disconnecting the USB cable the phone did not turn on.
Click to expand...
Click to collapse
Have you flashed the Stock ROM or the Engineering ROM? I remind you that even if you have flashed the eng rom only once previously, you can no longer return to the flyme bootloader so use the normal stock ROM but you will have to flash the Engineering rom
XRed_CubeX said:
Have you flashed the Stock ROM or the Engineering ROM? I remind you that even if you have flashed the eng rom only once previously, you can no longer return to the flyme bootloader so use the normal stock ROM but you will have to flash the Engineering rom
Click to expand...
Click to collapse
Well, I flashed the stock ROM a second time, using the Firmware Upgrade option, and it worked. My phone turned on and I'm in the initial setup screen.
By the way, this Engineering ROM is the ROM you shared above? Do you think it is stable enough to be used? Maybe another day I'll install it, with care to not do anything wrong again
thiagosousa777 said:
Well, I flashed the stock ROM a second time, using the Firmware Upgrade option, and it worked. My phone turned on and I'm in the initial setup screen.
By the way, this Engineering ROM is the ROM you shared above? Do you think it is stable enough to be used? Maybe another day I'll install it, with care to not do anything wrong again
Click to expand...
Click to collapse
Yes, the ROM in this thread is ROM engineering, about the stability I can't tell you why I haven't tested it, the main purpose FOR ME was to get the bootloader unlock with this ROM, if you want to switch to ROM engineering you CAN install the flyme after installed the Engineering ROM but you must always modify the OTA zip so that some partitions do not flash but if you are interested I will talk about it in more detail and maybe I will give you a hand to flash flyme safely on bootloader engineering
XRed_CubeX said:
Yes, the ROM in this thread is ROM engineering, about the stability I can't tell you why I haven't tested it, the main purpose FOR ME was to get the bootloader unlock with this ROM, if you want to switch to ROM engineering you CAN install the flyme after installed the Engineering ROM but you must always modify the OTA zip so that some partitions do not flash but if you are interested I will talk about it in more detail and maybe I will give you a hand to flash flyme safely on bootloader engineering
Click to expand...
Click to collapse
Actually, the ROM I installed with SP Flash Tools was not the update.zip from the official Flyme OS website. I downloaded the stock rom from needrom.
I have done this several times before.
But now, strangely I can no longer update to the latest version. The version I'm running is Flyme 6.0.2.0G. I tried to download the update.zip file and install it manually by clicking on it, and it appeared "corrupted file". I also tried to use the Update application and "network error" appeared. But everything else is working perfectly.
XRed_CubeX said:
if you are interested I will talk about it in more detail and maybe I will give you a hand to flash flyme safely on bootloader engineering
Click to expand...
Click to collapse
I would like to know how to install the latest version of Flyme OS via TWRP. If you can tell how to do this..
XRed_CubeX said:
can't release the Lineage because I'm fixing some bugs and I want to do some checks before releasing it publicly
Click to expand...
Click to collapse
Are you working on a custom Lineage OS ROM for this device? I'm interested, when you can publish it.. Do you have a prediction of when you will be able to release that ROM?
thiagosousa777 said:
I would like to know how to install the latest version of Flyme OS via TWRP. If you can tell how to do this..
Are you working on a custom Lineage OS ROM for this device? I'm interested, when you can publish it.. Do you have a prediction of when you will be able to release that ROM?
Click to expand...
Click to collapse
Ok, I'll explain in detail how it works: In the guide you will have read that you cannot return to the flyme using the stock rom or an unmodified OTA. This is a tip because once you flash the Engineering ROM, the engineering bootloader (which is essential for unlocking) will also be flashed, but the problem is that if you flash the stock bootloader (the flyme one, the one you surely have when you get the phone), the device for a reason unknown to me, probably the Engineering ROM modifies something in the device (?) and then goes into brick if you try to return to the flyme bootloader. To flash an OTA flyme on TWRP, you must first have some precautions: you must take the OTA on your computer (or a file explorer capable of editing zip files) and remove the following files: lk.bin preloader.bin (it will have a name longer but you still have to remove that) and tz.bin / trustzone.bin. Done like this, now the OTA becomes safe to install, you install it from TWRP, at the end of the flash it will give you an error but it is because it does not find the files we have removed but we can safely ignore it because it will have successfully installed the flyme on the device.
Regarding lineage: I'm still working on it a bit and gradually I'm discovering bugs. I already warn you that the camera will not work in the Lineage, I have tried in every way to try to make it work but it does not want to go, I have asked for help everywhere but no one has been able to answer so I do not know what to do, for the rest I want to keep a little longer the ROM under test to fix the remaining bugs