After fumbling with install twrp in order to change over to CM13 from stock, I somehow managed to install the original recovery wrong as well as completely boning the OS. Because of this, on boot, all that shows is the honor screen continuously. Of course the obvious answer to this is to reinstall twrp and restore one of my recovery files. Unfortunately trying to flash twrp through fastboot results in an "FAILED (data transfer failure (Unknown error))". Any suggestions? I can't access the phones internal storage nor the SD card either when I plug it into my PC.
Only one solution, flash a stock firmware using a PC.
PalakMi said:
Only one solution, flash a stock firmware using a PC.
Click to expand...
Click to collapse
How would I go about doing this? I would really love to get my honor working again. Would it just be using fastboot to flash the firmware?
I'd be worried about that error you're getting. It's strange.
Have you considered trying to flash stock recovery? You can extract the recovery image file from the official website update download. Or use the repository.
Or have you tried flashing a different version of TWRP recovery? Here's the official website.
Dueter1um said:
How would I go about doing this? I would really love to get my honor working again. Would it just be using fastboot to flash the firmware?
Click to expand...
Click to collapse
I don't think only fastboot is enough, but take a look at the link provided by JT-on
JT-on said:
I'd be worried about that error you're getting. It's strange.
Have you considered trying to flash stock recovery? You can extract the recovery image file from the official website update download. Or use the repository.
Or have you tried flashing a different version of TWRP recovery? Here's the official website.
Click to expand...
Click to collapse
Luckily, after trying to reflash the twrp with a different version like you suggested, there was no error message and it was completed successfully! Currently restoring as I type this. Don't know how to upload an image so text should do
C:\Users\zakpw\Desktop\Honor 5x rooting>fastboot flash recovery twrp-3.0.2-0-kiwi.img
target reported max download size of 266338304 bytes
sending 'recovery' (45202 KB)...
OKAY [ 1.423s]
writing 'recovery'...
OKAY [ 0.694s]
finished. total time: 2.121s
Dueter1um said:
Luckily, after trying to reflash the twrp with a different version like you suggested, there was no error message and it was completed successfully! Currently restoring as I type this. Don't know how to upload an image so text should do
C:\Users\zakpw\Desktop\Honor 5x rooting>fastboot flash recovery twrp-3.0.2-0-kiwi.img
target reported max download size of 266338304 bytes
sending 'recovery' (45202 KB)...
OKAY [ 1.423s]
writing 'recovery'...
OKAY [ 0.694s]
finished. total time: 2.121s
Click to expand...
Click to collapse
Happy for you, next time be careful
I got this same error, had to use different USB cable and different USB port.
EDIT: Got TWRP on by flashing it to boot. Now i need either a custom rom or stock rom
Hi, i have been trying to install TWRP on my Hauwei Y5 2017 (MYA-L22) for a few months now. i have found multiple TWRP builds and i have tried to flash them but when i do it says:
Code:
C:\adb - Y5 (2017)>fastboot flash recovery twrp-huawei-y5.img
target reported max download size of 134217728 bytes
sending 'recovery' (13494 KB)...
OKAY [ 1.291s]
writing 'recovery'...
OKAY [ 0.408s]
finished. total time: 1.700s
and then i reboot back into the phone, and the run:
Code:
C:\adb - Y5 (2017)>adb reboot bootloader
and it goes into the stock recovery, although i just flashed a custom recovery.
The phone was bought in Vietnam and runs: Android 6.0 And EMUI 4.1
Any more info you may need I am willing to give.
Reddit Thread: https://redd.it/7vltsb
uneedsomemilk said:
EDIT: Got TWRP on by flashing it to boot. Now i need either a custom rom or stock rom
Hi, i have been trying to install TWRP on my Hauwei Y5 2017 (MYA-L22) for a few months now. i have found multiple TWRP builds and i have tried to flash them but when i do it says:
Code:
C:\adb - Y5 (2017)>fastboot flash recovery twrp-huawei-y5.img
target reported max download size of 134217728 bytes
sending 'recovery' (13494 KB)...
OKAY [ 1.291s]
writing 'recovery'...
OKAY [ 0.408s]
finished. total time: 1.700s
and then i reboot back into the phone, and the run:
Code:
C:\adb - Y5 (2017)>adb reboot bootloader
and it goes into the stock recovery, although i just flashed a custom recovery.
The phone was bought in Vietnam and runs: Android 6.0 And EMUI 4.1
Any more info you may need I am willing to give.
Reddit Thread: https://redd.it/7vltsb
Click to expand...
Click to collapse
Can you please tell me that how you unlock the bootloader and twrp link also?
Note- This is tested on BKL-L09 C675 Indian variant and BKL-L09 C432 EU variant but will work on any variant of V10.
Hi Folks,
As I shared my experience on the issues I faced while moving back to stock from custom ROMs here , in this thread, I will share the detailed steps to go back to on stock avoiding any issues.
If you are on any custom ROM i.e. with Android/EMUI 8.1 TWRP backup will not work except BKL-L04. And only way that comes handy is fastboot (haven't tested the dload method myself yet as didnt had the SD card when I faced the issue but you can follow that, it will not break anything).
So before you start moving further to stock, please have these 3 files handy-
1- Stock recovery ramdisk
2- Stock boot ramdisk
3- system.img
Case 1- Custom ROM + Stock Boot + Stock Recovery (Applicable for new Open Kirin ROMs- RR and LOS which needs stock Ramdisk and if you are not using magisk)
On custom ROM, connect your phone with USB debugging enabled. (please make sure all the drivers are installed, it will already be as you may have the same which flashing the custom ROM)
Run the command to boot to fastboot
Code:
adb reboot bootloader
On fastboot screen, you will have bootloader state as Unlocked and FRP Unlocked.
Flash System image as below, Wait for process to finish, it may take 1-2 minutes for entire flash (93 seconds in my case)
Code:
PS C:\adb> fastboot flash system BKL-C432B130_system.img or fastboot flash system <system_filename>.img
target reported max download size of 471859200 bytes
sending sparse 'system' (456507 KB)...
OKAY [ 11.572s]
writing 'system'...
OKAY [ 2.669s]
sending sparse 'system' (457797 KB)...
OKAY [ 11.722s]
writing 'system'...
OKAY [ 2.630s]
sending sparse 'system' (457585 KB)...
OKAY [ 11.793s]
writing 'system'...
OKAY [ 3.417s]
sending sparse 'system' (460798 KB)...
OKAY [ 12.008s]
writing 'system'...
OKAY [ 2.611s]
sending sparse 'system' (413494 KB)...
OKAY [ 10.682s]
writing 'system'...
OKAY [ 2.631s]
sending sparse 'system' (453913 KB)...
OKAY [ 11.785s]
writing 'system'...
OKAY [ 2.973s]
sending sparse 'system' (227740 KB)...
OKAY [ 5.856s]
writing 'system'...
OKAY [ 1.260s]
finished. total time: 93.634s
Once the system image is flashed successfully, run the command to boot but immediately remove USB and press volume up key to boot to recoevery rather than system (even if you skip, it may not boot to system)
Code:
fastboot reboot
Remove USB and press volume up key to boot to recovery.
Perform factory reset and wipe data as well.
Once completed, reboot to system.
Case 2- Custom ROM + Stock Recovery + Magisk (Root) ( applicable for New open Kirin ROMs- RR and LOS which needs stock ramdisk and if you are using magisk)
I forgot that I had magisk and had to gone through more issues as post boot, my IMEI was missing and no SIM service but if you have magisk installed, please be more careful and flash stock boot (attached for BKL-L09 EU version)
Run the command to boot to fastboot
Code:
adb reboot bootloader
On fastboot screen, you will have bootloader state as Unlocked and FRP Unlocked.
Flash the stock boot ramdisk.img as
Code:
fastboot flash ramdisk BKL-L09_ramdisk.img
Or fastboot flash ramdisk <ramdisk_File_Name>
Flash System image as below, Wait for process to finish, it may take 1-2 minutes for entire flash (93 seconds in my case)
Code:
PS C:\adb> fastboot flash system BKL-C432B130_system.img or fastboot flash system <system_filename>.img
target reported max download size of 471859200 bytes
sending sparse 'system' (456507 KB)...
OKAY [ 11.572s]
writing 'system'...
OKAY [ 2.669s]
sending sparse 'system' (457797 KB)...
OKAY [ 11.722s]
writing 'system'...
OKAY [ 2.630s]
sending sparse 'system' (457585 KB)...
OKAY [ 11.793s]
writing 'system'...
OKAY [ 3.417s]
sending sparse 'system' (460798 KB)...
OKAY [ 12.008s]
writing 'system'...
OKAY [ 2.611s]
sending sparse 'system' (413494 KB)...
OKAY [ 10.682s]
writing 'system'...
OKAY [ 2.631s]
sending sparse 'system' (453913 KB)...
OKAY [ 11.785s]
writing 'system'...
OKAY [ 2.973s]
sending sparse 'system' (227740 KB)...
OKAY [ 5.856s]
writing 'system'...
OKAY [ 1.260s]
finished. total time: 93.634s
Once the system image is flashed successfully, run the command to boot but immediately remove USB and press volume up key to boot to recoevery rather than system (even if you skip, it may not boot to system)
Code:
fastboot reboot
Remove USB and press volume up key to boot to recovery.
Perform factory reset and wipe data as well.
Once completed, reboot to system.
Case 3- Custom ROM + Custom Recovery + (Stock Ramdisk/ modified Ramdisk with Magisk) (Applicable for any custom ROM installed with TWRP and on stock boot or Magisk)
I forgot that I had magisk and had to gone through more issues as post boot, my IMEI was missing and no SIM service but if you have magisk installed, please be more careful and flash stock boot (attached for BKL-L09 EU version)
Run the command to boot to fastboot
Code:
adb reboot bootloader
On fastboot screen, you will have bootloader state as Unlocked and FRP Unlocked.
Flash the stock Recovery Ramdisk as
Code:
fastboot flash recovery_ramdisk recovery_ramdisk_bak.img
Or fastboot flash recovery_ramdisk <Recovery_File_Name>.img
If you have stock Boot Ramdisk, proceed to flashing system image and skip flashing the boot ramdisk.
If you have installed magisk, flash the stock boot ramdisk.img as
Code:
fastboot flash ramdisk BKL-L09_ramdisk.img
Or fastboot flash ramdisk <ramdisk_File_Name>
Flash System image as below, Wait for process to finish, it may take 1-2 minutes for entire flash (93 seconds in my case)
Code:
PS C:\adb> fastboot flash system BKL-C432B130_system.img or fastboot flash system <system_filename>.img
target reported max download size of 471859200 bytes
sending sparse 'system' (456507 KB)...
OKAY [ 11.572s]
writing 'system'...
OKAY [ 2.669s]
sending sparse 'system' (457797 KB)...
OKAY [ 11.722s]
writing 'system'...
OKAY [ 2.630s]
sending sparse 'system' (457585 KB)...
OKAY [ 11.793s]
writing 'system'...
OKAY [ 3.417s]
sending sparse 'system' (460798 KB)...
OKAY [ 12.008s]
writing 'system'...
OKAY [ 2.611s]
sending sparse 'system' (413494 KB)...
OKAY [ 10.682s]
writing 'system'...
OKAY [ 2.631s]
sending sparse 'system' (453913 KB)...
OKAY [ 11.785s]
writing 'system'...
OKAY [ 2.973s]
sending sparse 'system' (227740 KB)...
OKAY [ 5.856s]
writing 'system'...
OKAY [ 1.260s]
finished. total time: 93.634s
Once the system image is flashed successfully, run the command to boot but immediately remove USB and press volume up key to boot to recoevery rather than system (even if you skip, it may not boot to system)
Code:
fastboot reboot
Remove USB and press volume up key to boot to recovery.
Perform factory reset and wipe data as well.
Once completed, reboot to system.
Once booted on any of the case, you will be on full stock with unlocked bootloader. (you need to either dload to lock the bootlaoder or run the command - fastboot oem urelock <16 digit bootlaoder code> to relock the bootlaoder).
Working and tested myself and confirmed by one more user(Sandeep Dash). So, if you follow the steps correctly, you should not face any issue but in case you get stuck anywhere or not clear with steps and I will try to help as much as I can.
Attached files for BKL-L09 EU version. I will add other files as an when I get it.
Stock Ramdisk for BKL-L09 EU version - Thanks to @topjohnwu for sharing here
Stock Recovery for BKL-L04 EU version -I extracted this but thanks to @shihabsoft for sharing the step which helped me doing this.
Stock system image for BKL-L09 EU Version - Thanks to @surdu_petru for sharing here
Will these method work on bkl l09 model (indian variant)?
Really nice guide! Just one thing: Aren't you missing a
Code:
fastboot flash recovery_ramdisk <recovery_ramdisk_file>
step somewhere?
mondalakash said:
Will these method work on bkl l09 model (indian variant)?
Click to expand...
Click to collapse
Yes it will, 100%. The case 1 confirmation from Sandeep is for Indian variant only.
Smaehtin said:
Really nice guide! Just one thing: Aren't you missing a step somewhere?
Click to expand...
Click to collapse
Thanks. Nope buddy, as you already have stock recovery (for new Open Kirin ROMs) and only boot ramdisk was modified (for Magisk)
But yes, if you flashed twrp then you need it. Thanks for highlighting it, i will fix this.
shashank1320 said:
Yes it will, 100%. The case 1 confirmation from Sandeep is for Indian variant only.
Click to expand...
Click to collapse
Thanks for the confirmation...one question should i use the official twrp or the unofficial one for installing custom roms , decrypting internal storage and so on...
shashank1320 said:
Thanks. Nope buddy, as you already have stock recovery and only boot ramdisk was modified.
But yes, if you flashed twrp then you need it. Thanks for highlighting it, i will fix this.
Click to expand...
Click to collapse
Oh, I see. I was just a little confused about this part then:
shashank1320 said:
So before you start moving further to stock, please have these 3 files handy-
1- Stock recovery ramdisk
2- Stock boot ramdisk
3- system.img
Click to expand...
Click to collapse
mondalakash said:
Thanks for the confirmation...one question should i use the official twrp or the unofficial one for installing custom roms , decrypting internal storage and so on...
Click to expand...
Click to collapse
FOr me it was unofficial as I was using OpenKirin ROM as per requirement it should be stock recovery only.
for other ROMs or backup, you can try the unofficial one as official doesnt work on Android 8.1 and it will show random content or character in TWRP so you can not restore or say access the stuffs on your internal memory. I used the unofficial one given here
shashank1320 said:
FOr me it was unofficial as I was using OpenKirin ROM as per requirement it should be stock recovery only.
for other ROMs or backup, you can try the unofficial one as official doesnt work on Android 8.1 and it will show random content or character in TWRP so you can not restore or say access the stuffs on your internal memory. I used the unofficial one given here
Click to expand...
Click to collapse
Did you try dirty unicorn RC latest build?
Smaehtin said:
Oh, I see. I was just a little confused about this part then:
Click to expand...
Click to collapse
Fixed in OP. Added one more case for custom recovery users.
Thanks for valuable input buddy.
mondalakash said:
Did you try dirty unicorn RC latest build?
Click to expand...
Click to collapse
Nope buddy. Did you? Any feedback?
shashank1320 said:
Nope buddy. Did you? Any feedback?
Click to expand...
Click to collapse
using this method relocks bootloader?
mondalakash said:
using this method relocks bootloader?
Click to expand...
Click to collapse
No. It wont
Only dload or manual relock does
shashank1320 said:
No. It wont
Only dload or manual relock does
Click to expand...
Click to collapse
Thanks buddy
shashank1320 said:
No. It wont
Only dload or manual relock does
Click to expand...
Click to collapse
Same bootloader unlock can be used multiple times for unlocking? Any idea
mondalakash said:
Same bootloader unlock can be used multiple times for unlocking? Any idea
Click to expand...
Click to collapse
Yes. Code will remain the same throughout the phone lifecycle. It is based on phone serial number, product if amd IMEI which remains the same and unique for every phone
shashank1320 said:
Yes. Code will remain the same throughout the phone lifecycle. It is based on phone serial number, product if amd IMEI which remains the same and unique for every phone
Click to expand...
Click to collapse
Thanks buddy for these quick reply..I guess these recovery issues rom bootlopping issues will be fixed if huwaie gave l09 variants 8.1 update
---------- Post added at 07:07 PM ---------- Previous post was at 06:53 PM ----------
shashank1320 said:
Yes. Code will remain the same throughout the phone lifecycle. It is based on phone serial number, product if amd IMEI which remains the same and unique for every phone
Click to expand...
Click to collapse
Bro if flash system IMG of EU variant will this mean that I will on the EU update cycle?..I mean the dev pulled the system IMG from his V10 EU variant.…
mondalakash said:
Thanks buddy for these quick reply..I guess these recovery issues rom bootlopping issues will be fixed if huwaie gave l09 variants 8.1 update
---------- Post added at 07:07 PM ---------- Previous post was at 06:53 PM ----------
Bro if flash system IMG of EU variant will this mean that I will on the EU update cycle?..I mean the dev pulled the system IMG from his V10 EU variant.…
Click to expand...
Click to collapse
It will not allow to flash or wont boot.
You may need to flash the oeminfo file first and then system img. Had this been this easy, i would have rebranded to Indian version. See one of my debranding guide in signature
shashank1320 said:
It will not allow to flash or wont boot.
You may need to flash the oeminfo file first and then system img. Had this been this easy, i would have rebranded to Indian version. See one of my debranding guide in signature
Click to expand...
Click to collapse
Or I can pull my system ,boot,ramdisk by ADB since I haven't messed with the device apart from unlocking it
---------- Post added at 08:19 PM ---------- Previous post was at 08:11 PM ----------
mondalakash said:
Same bootloader unlock can be used multiple times for unlocking? Any idea
Click to expand...
Click to collapse
Using erecovery would be easier if u have fast internet and I heard it doesn't relock the bootloader
I mean the relock doesn't matter according to u as we can just use the code several times ...then I guess dload is easier only need a SD card...I mean it doesn't even matter which one of the scenarios we are in as mentioned by u in the OP.
mondalakash said:
Or I can pull my system ,boot,ramdisk by ADB since I haven't messed with the device apart from unlocking it
---------- Post added at 08:19 PM ---------- Previous post was at 08:11 PM ----------
Using erecovery would be easier if u have fast internet and I heard it doesn't relock the bootloader
I mean the relock doesn't according to u as we can just use the code several times ...then I guess dload is easier only need a SD card...I mean it doesn't even matter which one of the scenarios we are in as mentioned by u in the OP.
Click to expand...
Click to collapse
Erecovery download is difficult and give error many times.
Dload actually lock the bootloader and you will be on full stock.
In my case, i had to relock the bootloader as it was in bootloop and i knew relocking will give me erecovery to download.
Before:
I just unlocked the bootloader and installed a custom ROM (LineageOS 15.1: https://forum.xda-developers.com/huawei-y6/development/lineageos-15-1-huawei-y6-2018-t3832278) on my Huawei but it won't let me flash the TWRP from adb. I tried before flashing the custom ROM and also after but no progress. I tried with 'fastboot flash recovery recovery.img' as well as 'fastboot flash boot recovery.img' because I knew some smartphones include the recovery in the boot.img but I am always getting the same error:
Code:
fastboot flash recovery recovery.img
target reported max download size of 535822336 bytes
sending 'recovery' (16544 KB)...
OKAY [ 0.522s]
writing 'recovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.553s
I am not an expert but I understood that 'recovery' partition doesn't exist. I found some possible solutions online such as writing 'fastboot flash RECOVERY recovery.img' or 'fastboot flash erecovery recovery.img' (because Huawei calls the stock one 'erecovery') but they both gave me another error:
Code:
fastboot flash RECOVERY recovery.img
target reported max download size of 535822336 bytes
sending 'RECOVERY' (16544 KB)...
OKAY [ 0.522s]
writing 'RECOVERY'...
FAILED (remote: Command not allowed)
finished. total time: 0.528s
UPDATE: I found, maybe, the correct name of the recovery partition and it seems to work:
Code:
fastboot flash recovery_ramdisk twrp.img
< waiting for device >
target reported max download size of 535822336 bytes
sending 'recovery_ramdisk' (14026 KB)...
OKAY [ 0.443s]
writing 'recovery_ramdisk'...
OKAY [ 0.323s]
finished. total time: 0.767s
BUT it actually doesn't work properly because when I boot into recovery it boots the stock one. I tried other solutions found on the net like instantly unplug the phone after the flash and reboot it into recovery immediately but again it boots into stock one...
OTHER UPDATE: I managed to find and flash a TWRP that can boot up but it shows the internal storage 0MB not allowing me to install any .zip file. Because of that, I cannot install SuperSU to get root access.
I tried installing TWRP also with stock ROM but still showing 0MB because the phone is encrypted. To disable encryption I need to install the bluspark TWRP (As I found online), the problem is that bluspark won't boot and gets immediately overwritten by the stock ROM as it happened with the one I mentioned in the first update of the post.
Now I will try buying a microSD card and see if it shows right so that I can still flash .zip from the microSD card.
Now:
LATEST UPDATE: The SD card is working properly and I see it as around 60 GB instead of 64 but that's not the problem. I can see the .zip files I'd want to flash but when I try to do it it says me that it failed to mount every single partition and after some research I discovered that my Huawei has all the data encrypted. After other research I found that there are some TWRPs like blu_spark that could decrypt the data but every version I tried doesn't work and gets immediately overwritten by the stock recovery.
Does anyone know other methods to decrypt all the data on Huawei? Otherwise it's impossible to flash any .zip. Actually it flashes it but it fails to update the partitions state so the system doesn't recognize the changes.
Rooting Huawei is so difficult.. I will buy an OP5t as soon as I have the money XD.
Y6 2018 twrp
Any progress? I'm also looking for a version of TWRP that works with the Y6 2018.
Hi guys , i was running AOSIP PIE rooted and bootloader unlocked. I did an update of Magisk. And then i couldn't flash twrp it was not working , i could still boot phone normally and phone run smooth. Someone told me to flash TWRP with flashify and i did. Here the problems started , i started having error , can't boot anywhere etc...
I followed this tutorial https://forum.xda-developers.com/huawei-p20-pro/how-to/guide-erecovery-hisuite-failing-to-t3932203/ for last solution .
But unfortunatly i can't flash VENDOR.img in fastboot , i can flash all except VENDOR.img it says
C:\ADB>fastboot flash vendor VENDOR.img
target reported max download size of 471859200 bytes
sending sparse 'vendor' 1/2 (460796 KB)...
OKAY [ 10.697s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 10.711s
I have flashed with success TWRP twrp-3.3.1-0-charlotte , i can get to it but there is no files inside the phone and it's not supporting SD cards to i don't have any ROM to flash ...
Do you guys have any idea about what to do ?
Thank you very much
benkiller47 said:
Hi guys , i was running AOSIP PIE rooted and bootloader unlocked. I did an update of Magisk. And then i couldn't flash twrp it was not working , i could still boot phone normally and phone run smooth. Someone told me to flash TWRP with flashify and i did. Here the problems started , i started having error , can't boot anywhere etc...
I followed this tutorial https://forum.xda-developers.com/huawei-p20-pro/how-to/guide-erecovery-hisuite-failing-to-t3932203/ for last solution .
But unfortunatly i can't flash VENDOR.img in fastboot , i can flash all except VENDOR.img it says
C:\ADB>fastboot flash vendor VENDOR.img
target reported max download size of 471859200 bytes
sending sparse 'vendor' 1/2 (460796 KB)...
OKAY [ 10.697s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 10.711s
I have flashed with success TWRP twrp-3.3.1-0-charlotte , i can get to it but there is no files inside the phone and it's not supporting SD cards to i don't have any ROM to flash ...
Do you guys have any idea about what to do ?
Thank you very much
Click to expand...
Click to collapse
First, in TWRP, advance wipe everything! Now, you need a pc, connect the phone to PC with a USB, on pc, download any ROM you want (and gapps if you want) now transfer the files to your phone and then flash them, izi,
Thumbs up if I was useful.
DankMemz said:
First, in TWRP, advance wipe everything! Now, you need a pc, connect the phone to PC with a USB, on pc, download any ROM you want (and gapps if you want) now transfer the files to your phone and then flash them, izi,
Thumbs up if I was useful.
Click to expand...
Click to collapse
Hi thank you for your help , unfortunatly at the end of the ROM installation , my phone reboot back to fastboot mode , no matter wich ROM i boot in it
also good to precise i have a Huawei p20 pro
benkiller47 said:
Hi thank you for your help , unfortunatly at the end of the ROM installation , my phone reboot back to fastboot mode , no matter wich ROM i boot in it
also good to precise i have a Huawei p20 pro
Click to expand...
Click to collapse
Try reinstalling stock firmware trough download mode...
Try reinstalling the twrp image. Helped me once