Steven98
Lurker
Sorry if I break the boxes, but it's serious the problem.
It's the continue to androidforums.com/threads/recovery-mode-removed.1117078/#post-7488338.
After managing to have a TWRP for Marshmallow, I immediately made the full format (except sd), then attempting to install LineageOS but again had the error not to recognize firm, perhaps because the bootloader is closed again, so I decided to restore my backup of CyanogenMod 13, succeeding thankfully, but once I rebooted the system, not only had failed to boot the operating system and returned to the bootloader, but even I could not re-enter the TWRP. So I went into a panic...
So what I decided to do? Groped to search all drivers and files to the Fastboot, to try to fix something. When found the files, I decided right away to open CMD and use the Fastboot command to install the files: boot, droidboot and recovery.img. And so it was that succeeded in killing my phone (I think). This is because once tried to turn, felt the vibration but did not display anything and never went beyond, despite everything, it was still possible to use the Fastboot command whenever it was on.
Do you say that I have to send it for repair or are there other possibilities?
It's the continue to androidforums.com/threads/recovery-mode-removed.1117078/#post-7488338.
After managing to have a TWRP for Marshmallow, I immediately made the full format (except sd), then attempting to install LineageOS but again had the error not to recognize firm, perhaps because the bootloader is closed again, so I decided to restore my backup of CyanogenMod 13, succeeding thankfully, but once I rebooted the system, not only had failed to boot the operating system and returned to the bootloader, but even I could not re-enter the TWRP. So I went into a panic...
So what I decided to do? Groped to search all drivers and files to the Fastboot, to try to fix something. When found the files, I decided right away to open CMD and use the Fastboot command to install the files: boot, droidboot and recovery.img. And so it was that succeeded in killing my phone (I think). This is because once tried to turn, felt the vibration but did not display anything and never went beyond, despite everything, it was still possible to use the Fastboot command whenever it was on.
Do you say that I have to send it for repair or are there other possibilities?
