ГОТОВО! Шаг был выполнен правильно, но теперь проблема в инструменте SPFlash, который устройство не видит, или я указываю не то. Скриншот прилагается. Может, в этом случае есть ссылка на рекавери и рекавери?
excuse, more clearly sir? about backup seccfg with dd?
Check the fastboot drivers carefully and see if the device is recognized.
Check the fastboot drivers, however this guide makes you unlock the bootloader, do not change the operating system so it is normal that you find yourself in flymeHi! I tried flashing recovery and stuck where you need to erase seccfg and install twrp, my device just simply does not show up in the fastboot devices list. What i need to do then? And also, when I wall flash twrp, will I be able to boot back again in the system, if it's just a stock image of flymeos 220.127.116.11G?
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 theseI 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...forum.xda-developers.com
I know it's my responsibility, but I don't know what else to do. Could someone please help me?
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.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?
https://mega.nz/#!H1k0za6R!FjfhscOlnUQmuOj-9Ml09133-eAUzKNgF0bD5KaBKok , right click on cdc-acm.inf and installUnfortunately I don't have Windows installed here. I can install it, but it will take a long time and I will have a lot of work to find the right MTK drivers, and even then I doubt it will work.
Also, I had a lot of work to apply a patch and compile the Linux kernel so I could use the MTK-bypass tool.
If you can send me a link with the specific drivers for this device for Windows 10, I'd appreciate it, because I've tried it dozens of times in Windows and couldn't, so I use the SP Flash Tool in Linux, which already comes with these drivers included by default.