Steven98
Lurker
The title says it all, but I explain calmly how it happened.
I was trying to want to install the official version of LineageOS for my Zenfone 2 and after downloading all the necessary files, have formatted and clean everything (except the SD), trying to install the new custom rom and then have the same "error 7". Then I realized immediately that lacked the Bootloader for Marshmellow, so I tried to look for a ZIP file for this, being able to find it right for my smartphone. The folder was known as "M_BL_upgrade_for_zf2_ze551ml_6.0" and once I had entered the USB cable to my PC and started the "Upgrade.bat" program, after the strangely reboot bootloader returned closed (it was understood from the screen, which instead to be white background with black writing was black with white lettering), then I tried to go back in recovery mode, realizing that every time I tried to get in, it was as if I were locked in a deadly circle and then kept restart and then return to where we started ... you have any idea how to do it, maybe re-add the Recovery Mode standard via CMD?
I was trying to want to install the official version of LineageOS for my Zenfone 2 and after downloading all the necessary files, have formatted and clean everything (except the SD), trying to install the new custom rom and then have the same "error 7". Then I realized immediately that lacked the Bootloader for Marshmellow, so I tried to look for a ZIP file for this, being able to find it right for my smartphone. The folder was known as "M_BL_upgrade_for_zf2_ze551ml_6.0" and once I had entered the USB cable to my PC and started the "Upgrade.bat" program, after the strangely reboot bootloader returned closed (it was understood from the screen, which instead to be white background with black writing was black with white lettering), then I tried to go back in recovery mode, realizing that every time I tried to get in, it was as if I were locked in a deadly circle and then kept restart and then return to where we started ... you have any idea how to do it, maybe re-add the Recovery Mode standard via CMD?