Database Info

[Solved] Bricked? Would really appreciate help.

So I had my Honor 8 (FRD L04) unlocked, rooted and running stock just fine. Then I decided to flash the unofficial Lineage rom. After doing so I got a prompt to enter a password to decrypt, while booting into Lineage and even into TWRP, I never set the password so I wasn't sure what to do. I tried a few things then eventually reflashed TWRP and got rid of the password problem then tried to restore my back up but it didn't work. Now I'm stuck. I can access fastboot, TWRP and eRecovery. eRecovery always fails to get package info. And whenever I try to do anything in TWRP it says it failed to mount cust, vendor and product. I've tried a lot of different solutions I've seen on here the dload method always goes to 5% then fails. I've flashed stock boot, recovery and system.img but didn't change anything. And I can't seem to get it to boot to stock recovery to format/wipe that way.
If there's anything anyone knows that I can do it'd be appreciated.

Got my issue solved thanks to the thread above. Not sure how to mark this as solved or closed.

Rommco05 said:
Good to know if you want rename thread u can, but I know how to do it only in phone XDA app
Click to expand...
Click to collapse
Just found how to do it on the app. Name offically changed. Thanks again for the help.

Stuck on Boot screen after flashing TWRP

Hello,
I just flashed the latest ROM for the S8+ (AQL5) and that went well.
Afterwards I tried to flash TWRP, but now the phone is stuck on the Samsung screen.
I then followed the guide I found here to use the BL file of AQF7 in Odin and spam the Start button so I managed to get into TWRP.
Question is, what do I do next? I restart the system it's the same problem all over again.
No one explains anywhere what to do in TWRP to save the phone.
Can I remove TWRP or somehow save the phone (without wiping my data)
Please help

Can you get to download mode? Then go to ODIN and redo your flashing of the OS and then TWRP. After the flash of TWRP, immediately boot into TWRP, and do Verity if you want that, and your root, if not already done. Clear Dalvik/cache and reboot to system.
It is not uncommon for folks, following TWRP flash, to get stuck in boot loop, unfortunately. Can take a little time, but you will get through it and finally to System.

But I thought all new firmware versions are incompatible with TWRP and cause this error.
I might try to install TWRP again if I flash the latest compatible version (I think it's the F7 one).
Does "Verify" in TWRP make that annoying "Your phone is not verified" message go away? The only option is to Reset phone when that thing comes up and I don't want to do that.
I managed to get out of that by reflashing the AQL5 version and just not installing TWPR.
Kind of scared to retry because everything goes wrong when I try to follow the guides on here or youtube

nkomp18 said:
But I thought all new firmware versions are incompatible with TWRP and cause this error.
I might try to install TWRP again if I flash the latest compatible version (I think it's the F7 one).
Does "Verify" in TWRP make that annoying "Your phone is not verified" message go away? The only option is to Reset phone when that thing comes up and I don't want to do that.
I managed to get out of that by reflashing the AQL5 version and just not installing TWPR.
Kind of scared to retry because everything goes wrong when I try to follow the guides on here or youtube
Click to expand...
Click to collapse
Would you please provide the info from my first post? and Exynos of Snapdragon?

JeffDC said:
Would you please provide the info from my first post? and Exynos of Snapdragon?
Click to expand...
Click to collapse
I have Exynos - model SM-G955F
Yes I can go to download mode but I won't do the things you ask because they're guaranteed to soft-brick the phone again and I have it working now

i have the same problem, followed this guide https://forum.xda-developers.com/galaxy-s8/how-to/guide-how-to-root-galaxy-s8-crgh-rom-t3846009 managed to get to TWRP no problems, once i reset the device though im stuck at the samung galaxy s8+ boot screen and can't get it off
any suggestions ? i did try to search but this old thread was the only relevant one i could find

stuck on boot screen after flashing twrp for magisk manager
i flashed magisk manager in twrp youtube.com/watch?v=r3R9kiBIx34 by this and now not booting to android . before i had this i reflashed miui 11 using official software and coulnt be sucess this time also please help me any one . my mobile is redmi 6 pro.:crying::crying::crying::crying:

Moto G Bricked?

Hi.
A friend gave me his Moto G1 2013 to install Linage OS but I'm really having troubles with it, first of all it doesn't allow me to install TWRP, when I type fastboot flash recovery recovery.img it says that it installs but it doesn't, when I try to boot on it it just doesn't boot, the way I had access to TWRP was typing fastboot boot recovery.img...
When I got in I did the first step when you install a new Custom ROM that is wipe system, cache and dalvik cache, then I tried to install the ROM zip file but it gave me "error 7" I looked for solutions and I found one that is modifying updater-script file, I did it but it gave me another error about mount system, I looked for solutions too and I found one that is modifying file system format to anotherone and then bringing it back to the original format but still having the same error.
After that I decided to go back to stock ROM, I have flashed many times the stock ROM with fastboot commands but it just doesn't boot into the OS, when I try to boot the phone it boots into bootloader again... Any solution to this? Is it a hardware problem? Please help me I'm so embarrased with my friend.

Same thing happened to me!
Basidialfiddle said:
Hi.
A friend gave me his Moto G1 2013 to install Linage OS but I'm really having troubles with it, first of all it doesn't allow me to install TWRP, when I type fastboot flash recovery recovery.img it says that it installs but it doesn't, when I try to boot on it it just doesn't boot, the way I had access to TWRP was typing fastboot boot recovery.img...
When I got in I did the first step when you install a new Custom ROM that is wipe system, cache and dalvik cache, then I tried to install the ROM zip file but it gave me "error 7" I looked for solutions and I found one that is modifying updater-script file, I did it but it gave me another error about mount system, I looked for solutions too and I found one that is modifying file system format to anotherone and then bringing it back to the original format but still having the same error.
After that I decided to go back to stock ROM, I have flashed many times the stock ROM with fastboot commands but it just doesn't boot into the OS, when I try to boot the phone it boots into bootloader again... Any solution to this? Is it a hardware problem? Please help me I'm so embarrased with my friend.
Click to expand...
Click to collapse
Hi! I tried something similar with a similar result. I first unlocked my Moto G's bootloader. Then installed TWRP using fastboot. After that I tried flashing Resurrection Remix rom which failed. I've been stuck in a kind of bootloop since then. My handset powers up, finds something wrong, tries to go into recovery, fails and does this over and over again.
Since I am able to boot into bootloader mode, I tried to flash the stock rom by following instructions from this thread https://forum.xda-developers.com/showthread.php?p=47820707#post47820707
I have tried different variations from many different forums (fora?) all with the same result. Still stuck in the bootloop-thingie.
Btw, I also tried the unbricking guide from this thread
https://forum.xda-developers.com/moto-g/help/how-to-unbrick-moto-g-falcon-t3394788 without any success. My phone shows up as a Motorola ADB device and also as XT1033 in Device Manager when its plugged in.
Anyone know anything to help me out?

gaurav.kar said:
Hi! I tried something similar with a similar result. I first unlocked my Moto G's bootloader. Then installed TWRP using fastboot. After that I tried flashing Resurrection Remix rom which failed. I've been stuck in a kind of bootloop since then. My handset powers up, finds something wrong, tries to go into recovery, fails and does this over and over again.
Since I am able to boot into bootloader mode, I tried to flash the stock rom by following instructions from this thread https://forum.xda-developers.com/showthread.php?p=47820707#post47820707
I have tried different variations from many different forums (fora?) all with the same result. Still stuck in the bootloop-thingie.
Btw, I also tried the unbricking guide from this thread
https://forum.xda-developers.com/moto-g/help/how-to-unbrick-moto-g-falcon-t3394788 without any success. My phone shows up as a Motorola ADB device and also as XT1033 in Device Manager when its plugged in.
Anyone know anything to help me out?
Click to expand...
Click to collapse
Hi, I found the solution time ago, sorry for answering to late, hope I can still be helpful.
Well, what I did is, I booted into TWRP, then I did a total format to the storage, after that I did something kind of crazy, I switched my storage format to anotherone and then I turned it back to how it was before (example: I was on fat32, I switched to exFAT and then I switched again to fat32) after doing that I tried to flash LinageOS and it allowed me, it booted and now my friend has Android Oreo on his Moto G1
Hope it works for you mate, those situations are very frustrating, good luck

bootloop after using twrp (can't start smartphone, please help!)

i cant really explain what i was doing but i was trying to root the phone and after rooting it i tried to fix an issue with twrp crashing. it ended up with me stuck in a bootloop that i cant get out of. i have basicly no experience in the stuff so i am in desperate need of help. you can reply to the forum or msg me on an a platform like discord (TobiS137#2131) preferably discord tho. thanks in advance! i really want it fixed asap so if you can help then please be quick. please reply under the thread if you have msg me on discord. i really need help.

TobiS137 said:
i cant really explain what i was doing but i was trying to root the phone and after rooting it i tried to fix an issue with twrp crashing. it ended up with me stuck in a bootloop that i cant get out of. i have basicly no experience in the stuff so i am in desperate need of help. you can reply to the forum or msg me on an a platform like discord (TobiS137#2131) preferably discord tho. thanks in advance! i really want it fixed asap so if you can help then please be quick. please reply under the thread if you have msg me on discord. i really need help.
Click to expand...
Click to collapse
Enter fastboot, flash official twrp.Flash magisk in twrp.

vrda08 said:
Enter fastboot, flash official twrp.Flash magisk in twrp.
Click to expand...
Click to collapse
can you help me further? as i said i am a huge newbie and i only understood a little of that. is there any other ways you can contact me?

vrda08 said:
Enter fastboot, flash official twrp.Flash magisk in twrp.
Click to expand...
Click to collapse
Can you explain what exactly were you doing ?!

Just hold the power button for 60 seconds or so, it should reboot normally. Did you flash twrp or just do fastboot boot twrp?

I'm new to this while A/B partition. I went through all the steps and my phone is rooted, with Magisk and TWRP. All seems to be fine. My question is this. When I boot to the recovery (TWRP) and choose the reboot option it defaults to Current Slot: Partition B. If I reboot to partition B it goes back to TWRP. I have to select Partition A to get the device to boot to the system.
Is this normal? Do I need to set it up in a different way?

samteeee said:
Can you explain what exactly were you doing ?!
Click to expand...
Click to collapse
i was trying to root the phone (wich i did) and then the twrp app that was on my phone after i had tried to install it using the img. it then turned into an ap that told me to update it in google play
after that was done i tried to flash it but everytime i tried it just crashed. a little time later after trying some more times i found that i started it in the bootloader and it ended up with me stuck in a bootloop. again i might not have explained enough. i am huge noob so i really need help.

ooshkamils said:
Just hold the power button for 60 seconds or so, it should reboot normally. Did you flash twrp or just do fastboot boot twrp?
Click to expand...
Click to collapse
i think i did fastboot boot twrp. still not sure tho :\ . Does it change anything that i use twrp enchilada or does that not matter?

ooshkamils said:
Just hold the power button for 60 seconds or so, it should reboot normally. Did you flash twrp or just do fastboot boot twrp?
Click to expand...
Click to collapse
i think i did fastboot boot twrp. still not sure tho :\

discord
ignore the "discord" title. i dont think the phone has an OS right now. when i turn it on it goes directly to twrp. if i reboot the system it just goes back to twrp recovery. i think i need a way to install an OS (preferably OxygenOS if that is even possible). i realised that you guys properbly won't msg on discord. you dont have to. you can use the forums . i just really want help to get my phone back up and running. it is a OnePlus 6 btw if that is important.

TobiS137 said:
i think i did fastboot boot twrp. still not sure tho :\
Click to expand...
Click to collapse
To keep TWRP as the phones recovery, you'd first need to do as you did "Fastboot boot twrp" but that command will only allow you to boot into TWRP through your pc or whatever you ran that command on. After you've entered that temporary recovery, you'll need the TWRP installer .zip file, and flash that inside of that temporary TWRP. Then you can reboot into recovery on your phone again since it has been installed to one of the partitions.

TobiS137 said:
ignore the "discord" title. i dont think the phone has an OS right now. when i turn it on it goes directly to twrp. if i reboot the system it just goes back to twrp recovery. i think i need a way to install an OS (preferably OxygenOS if that is even possible). i realised that you guys properbly won't msg on discord. you dont have to. you can use the forums . i just really want help to get my phone back up and running. it is a OnePlus 6 btw if that is important.
Click to expand...
Click to collapse
You have to flash magisk after flashing twrp or else you are going to get this bootloop you are talking about

phone open again
my phone is back up and running again. i changed the partitian slot from A( the broken one with no OS) to B(the unchanged one) and it is now working again. if anyone is having the same problem the try to change to the second slot. it happend in twrp enchilada 3.2.2-0 if it is important. thank you all for your support.

I may be mistaken but I believe all you need to do is flash magisk to get up and running again

hallo dare said:
You have to flash magisk after flashing twrp or else you are going to get this bootloop you are talking about
Click to expand...
Click to collapse
Why? You should be able to just flash the TWRP installer into TWRP and so its flashed into both boot_a and boot_b. It should boot ok to system from there, Magisk is just another mod to the boot partitions, like a custom kernel, etc. It should not be necessary at all, why you guys keep sayin Magisk is necessary for anything? it isn't.

RusherDude said:
Why? You should be able to just flash the TWRP installer into TWRP and so its flashed into both boot_a and boot_b. It should boot ok to system from there, Magisk is just another mod to the boot partitions, like a custom kernel, etc. It should not be necessary at all, why you guys keep sayin Magisk is necessary for anything? it isn't.
Click to expand...
Click to collapse
Because you do. The OP6 will not boot with custom recovery unless it's rooted. I believe this is because the recovery and boot partitions are merged on this device. You're welcome to bootloop all day if you don't believe us.

iElvis said:
Because you do. The OP6 will not boot with custom recovery unless it's rooted. I believe this is because the recovery and boot partitions are merged on this device. You're welcome to bootloop all day if you don't believe us.
Click to expand...
Click to collapse
Asking "why?" is not to not believe you, and the personal bootloop all day attack is out of the matter. TWRP is flashed on the ramdisk and should boot stock, unless something derped, if it doesn't boot I honeslty don't understand why, what is the exact reason? TWRP installer doesn't overwrite the boot, just patches it to have a mini recovery on it. It should boot...

RusherDude said:
Asking "why?" is not to not believe you, and the personal bootloop all day attack is out of the matter. TWRP is flashed on the ramdisk and should boot stock, unless something derped, if it doesn't boot I honeslty don't understand why, what is the exact reason? TWRP installer doesn't overwrite the boot, just patches it to have a mini recovery on it. It should boot...
Click to expand...
Click to collapse
I don't know for sure either, beyond what I said above. But everyone who has reported not flashing magisk has bootlooped.
If I sounded snippy, it was only because your post above was appearing to deny the reality of what is a very well-known issue with this phone.

iElvis said:
I don't know for sure either, beyond what I said above. But everyone who has reported not flashing magisk has bootlooped.
If I sounded snippy, it was only because your post above was appearing to deny the reality of what is a very well-known issue with this phone.
Click to expand...
Click to collapse
I am not denying anything! just surprised because on TWRP website they clearly state that no post-twrp-flashing step is needed:
https://twrp.me/oneplus/oneplus6.html
The OnePlus 6 uses the newer AB partition scheme first introduced on the Pixel 1. As such there is no recovery partition. Instead, the recovery is part of the boot image. You will temporarily boot TWRP to perform and later perform a more permanent TWRP installation. First download the TWRP zip file directly on your device. If you don't download the zip file to your device first for any reason, you will need to adb push the zip to the device because MTP is not currently working on the OnePlus 6 in TWRP. If you are unable to use adb, you can also use a USB stick with an OTG cable, if you have those handy. Power off the device. Hold volume up to get into fastboot mode. Run this command on your computer: fastboot boot twrp-3.2.1-0-enchilada.img
In TWRP, tap on Install and browse to the zip and install it (the zip will probably be in /sdcard/Downloads). TWRP will now be installed to both slots. TWRP is now installed and you can reboot and use your device as normal.
MTP is disabled because it causes a kernel panic sometimes with the stock kernel.
Click to expand...
Click to collapse
Maybe the issue here is that the unofficial TWRP that everyone used NEEDS magisk while the official doesn't?

RusherDude said:
Maybe the issue here is that the unofficial TWRP that everyone used NEEDS magisk while the official doesn't?
Click to expand...
Click to collapse
I think most people have moved to the official version. If it doesn't need magisk to avoid a bootloop, that's news to me. Not saying it's not the case, but I haven't seen any mention of it.

Need help recovering my phone from bootloop after trying to update custom rom

Today I tried to finally update to the latest version of crDroid, but ended up having a bunch of issues doing so, and after a lot of troubleshooting and trying to fix it, I ended up putting it into a bootloop of some sort instead.
I'm pretty sure the last thing I tried was installing a different version of TWRP to see if that version would let me properly install the rom, and stop my phone from always rebooting into recovery mode.
Trying to turn it on normally or boot into TWRP leaves it hanging on the "Redmi" boot screen, it can boot into fastboot mode though.
I'm guessing that the only way to recover my phone at this point is to flash the Official MIUI rom back onto the phone, but that also involves wiping Data and losing pretty much everything I've put on the phone.
I was smart enough to make a TWRP of the Data folder, but while making the backup, the console said it doesn't include all personal files or something.
How much of my personal data and files can I rescue from the phone in this state, and how can I do that before it gets wiped when fixing it?
Also, I think I really need some help in actually restoring my phone and flashing the custom rom properly.
No matter how much effort I put into figuring out how to do this stuff, unexpected issues always seem to happen, and turns something that initially seemed so simple into multiple hours of troubleshooting.
The only way I think i've gotten rom flashing to work at all was by wiping everything and installing the official MIUI rom, but I don't want to be losing my data every month when an update comes out.
So, could someone please help me get my phone working again?
Edit: I ended up fixing my own issue by ADB flashing on a different release of TWRP, and then installing fcrypt disabler after the rom but before everything else.

Sanarise said:
Today I tried to finally update to the latest version of crDroid, but ended up having a bunch of issues doing so, and after a lot of troubleshooting and trying to fix it, I ended up putting it into a bootloop of some sort instead.
I'm pretty sure the last thing I tried was installing a different version of TWRP to see if that version would let me properly install the rom, and stop my phone from always rebooting into recovery mode.
Trying to turn it on normally or boot into TWRP leaves it hanging on the "Redmi" boot screen, it can boot into fastboot mode though.
I'm guessing that the only way to recover my phone at this point is to flash the Official MIUI rom back onto the phone, but that also involves wiping Data and losing pretty much everything I've put on the phone.
I was smart enough to make a TWRP of the Data folder, but while making the backup, the console said it doesn't include all personal files or something.
How much of my personal data and files can I rescue from the phone in this state, and how can I do that before it gets wiped when fixing it?
Also, I think I really need some help in actually restoring my phone and flashing the custom rom properly.
No matter how much effort I put into figuring out how to do this stuff, unexpected issues always seem to happen, and turns something that initially seemed so simple into multiple hours of troubleshooting.
The only way I think i've gotten rom flashing to work at all was by wiping everything and installing the official MIUI rom, but I don't want to be losing my data every month when an update comes out.
So, could someone please help me get my phone working again?
Click to expand...
Click to collapse
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc

Simoom Sadik said:
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Click to expand...
Click to collapse
Unfortunately, I can't.
Trying to boot into TWRP just gets stuck on the 'Redmi' boot logo.
I just remembered that you can install TWRP over ADB, and that Peter's one says it works even when the system partition is empty, so maybe the issue is the TWRP I installed and could possibly undo this part of the issue over ADB.
It won't fix the issue preventing my from updating my rom, but recovery only is still better than a soft brick.
Edit: That worked, i've put Peter's TWRP back on, and it's launching into recovery mode/TWRP again now

twrp not boot after successfully flash in this rom
Sanarise said:
Unfortunately, I can't.
Trying to boot into TWRP just gets stuck on the 'Redmi' boot logo.
I just remembered that you can install TWRP over ADB, and that Peter's one says it works even when the system partition is empty, so maybe the issue is the TWRP I installed and could possibly undo this part of the issue over ADB.
It won't fix the issue preventing my from updating my rom, but recovery only is still better than a soft brick.
Edit: That worked, i've put Peter's TWRP back on, and it's launching into recovery mode/TWRP again now
Click to expand...
Click to collapse
flash latest twrp download from github, install twrpbuilder img twrp ,it boot fine and you will copy your data to pc and then install any other twrp img which u want , dont wipe anything from phone before phone boot.flash only original twrp builder 3.2.3.1 official,it boot only on latest updates.

Why nobody use orangefox?

is your issue solve or not tell,
Simoom Sadik said:
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Click to expand...
Click to collapse
if your problem is not solve then tell me you need to flash a fastboot rom first with save user data.bat file and when it installed then you can install twrp builder 3.2.1. and then boot to twrp this methods working fine,if you recently flashed any android 10 rom then first you need to flash a miui fastboot rom,or flash it via command mode direct only 3 files
first click on extract a fastboot rom and copy boot system and vender file with flash.all bat file and make a new folder then click on flash.bat save user data file to flash these images
or you can do this manually
fastboot flash system system.img
fastboot flash vender vender.img
fastboot flash boot boot.img
then reboot device to fastboot again
now flash latest official twrp builder 3.2.3.1 img twrp and take all your data backup,
in fastboot flash latest miui do not downgrade direct otherwise you lost your data,
after this if you sucess then you can flash your old rom which is running before issue of boot loop of redmi logo
it will deincrypt your data safely and then root device and boot normally, if you lost anything then contact me with mail or whatsapp i will help you,7009197673 india
and this twrp work on all version from chines to global beta stable and indian stable

joke19 said:
Why nobody use orangefox?
Click to expand...
Click to collapse
In the end, I did try orangefox, and it might have been part of why it worked.
However, the crDroid installation instructions specifically mentions using Peter's TWRP, so I initially used that one.
anmoltinder said:
if your problem is not solve then tell me you need to flash a fastboot rom first with save user data.bat file and when it installed then you can install twrp builder 3.2.1. and then boot to twrp this methods working fine,if you recently flashed any android 10 rom then first you need to flash a miui fastboot rom,or flash it via command mode direct only 3 files
Click to expand...
Click to collapse
Thank you for the effort you put into typing up a guide to help me, but I ended up fixing my own problem.
I was able to use fastboot to flash on a better TWRP release, and then get the rom to install properly by installing fcrypt-disabler just after it.

Sanarise said:
Today I tried to finally update to the latest version of crDroid, but ended up having a bunch of issues doing so, and after a lot of troubleshooting and trying to fix it, I ended up putting it into a bootloop of some sort instead.
I'm pretty sure the last thing I tried was installing a different version of TWRP to see if that version would let me properly install the rom, and stop my phone from always rebooting into recovery mode.
Trying to turn it on normally or boot into TWRP leaves it hanging on the "Redmi" boot screen, it can boot into fastboot mode though.
I'm guessing that the only way to recover my phone at this point is to flash the Official MIUI rom back onto the phone, but that also involves wiping Data and losing pretty much everything I've put on the phone.
I was smart enough to make a TWRP of the Data folder, but while making the backup, the console said it doesn't include all personal files or something.
How much of my personal data and files can I rescue from the phone in this state, and how can I do that before it gets wiped when fixing it?
Also, I think I really need some help in actually restoring my phone and flashing the custom rom properly.
No matter how much effort I put into figuring out how to do this stuff, unexpected issues always seem to happen, and turns something that initially seemed so simple into multiple hours of troubleshooting.
The only way I think i've gotten rom flashing to work at all was by wiping everything and installing the official MIUI rom, but I don't want to be losing my data every month when an update comes out.
So, could someone please help me get my phone working again?
Edit: I ended up fixing my own issue by ADB flashing on a different release of TWRP, and then installing fcrypt disabler after the rom but before everything else.
Click to expand...
Click to collapse
help.I woke up yesterday and I turned on my phone and it is stuck on the Mi logo.All i can do is get it to fastboot thing.It seems like you and I have the same problem and I would love to have some help from you

Fcsubxrhi said:
help.I woke up yesterday and I turned on my phone and it is stuck on the Mi logo.All i can do is get it to fastboot thing.It seems like you and I have the same problem and I would love to have some help from you
Click to expand...
Click to collapse
If you can access fastboot, then flash TWRP.... Enter recovery, wipe your system partitions and then flash the Stock MIUI ROM or use the MiFlash tool. Make sure you aren't flashing an older version of the ROM than the onle already installed.

CongestedHangman said:
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Click to expand...
Click to collapse
I have the same problem that stated after installing the update for derpfest and I can boot into twrp. Any solution for me?