Database Users

[Q] Did I brick my Nexus 4?

Hi,
Last night i was playing with my N4 (with some root applications) and an app asked for a reboot. I just pressed yes so that the phone will reboot (I have done this earlier without any issues). Suddenly the device doesn't boot up. My N4 is stuck at a black screen. While trying to boot up, the Google logo appears and then a black screen. It doesn't advance to the 'X' logo. I'm running on stock, rooted phone (used N4 toolkit by Wugfresh to root).
I'm able to boot into recovery although. I tried all the possible means, wiped cache, dalvik cache, did a factory reset, backed up the system and tried to restore the same. Nothing happened.
Then i tried the "Back to Stock" option in the N4 toolkit and chose the option "Soft-brick/Bootloop" to recover my N4. These are what happened:
Downloaded the 4.2.2 image from Google servers and tried to flash in the device with prior instruction from the toolkit. Everything went fine until the flashing process. In the last step the CMD window opens up saying it is unrooting and flashing stock and immediately it'll bring up a complete message saying the flashing is complete and to wait until the device boots up. But nothing happens again.
I tried the automatic flashing and on the downloading window it saying download failed and hash checks failed meaning its not downloading.
I searched all the possible threads in a day to find a similar problem but in vain. I'm not a noob but i'm too lazy . But i would do anything to bring my N4 back to life. Anyone please show me a direction.
In short:
Status: Soft-Bricked (guess so), black screen after Google logo
Version: Stock 4.2.2 (rooted+busybox+supersu+twrp)
Able to boot to recovering: Yes, bootable to recovery and bootloader.
Tried Nexus toolkit recovery: Yes but in vain.
Gave up: No and never, I'm searching and searching for answers and I'm worried if I'll end up in a hard brick. :crying:
Guys, please help.
Thank You!
Aghil

I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?

ameinild said:
I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?
Click to expand...
Click to collapse
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.

Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.

aghilvr said:
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.
Click to expand...
Click to collapse
No, my suggestion would require that the ROM is still on the phone, so you should restore your ROM prior to my suggestion. And I'm by no means an expert (therefore the disclaimer), but I *think* that since it's a bootup problem, it could be solved by flashing a new boot.img (which is essentially flashing a new kernel to the system).
But yeah, let's see if others think this might help, haven't researched it, is at work right now. Just throwing in a suggestion, that's all...
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
I *think* (again, I'm totally not sure about this, as I haven't tried it) that you can sideload a ROM via zip file from recovery, but since I haven't tried it I'm not sure - can anybody confirm???
EDIT: Chromium's suggestion is better, by pushing the ROM.zip to the device and flashing from recovery (check md5 first, just in case).

aghilvr said:
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
Yes there is. Your nexus is not bricked and this is why you shouldnt use toolkits to do things. This is honestly an extremely easy and simple fix. Use adb to push a rom onto the n4.
Code:
adb push \path\to\rom.zip /sdcard
Boot into recovery, do a full wipe, and flash the rom.

You said you downloaded the Google images.
Just boot your phone into the bootloader and run the flashall.bat that is in the Google image folder.
Note this will probably fully wipe you're phone in the process
Sent from my Nexus 4 using xda app-developers app

try this it may help u this toolkit is damn easy to use :
http://forum.xda-developers.com/showthread.php?t=1995688

Okay, thanks guys. I'm on it. Will let you know when I'm done.

That same thing happened to me once. I had to extract the google file and look for the 4 img files(bootloader, system, userdata, recovery) and flash them with toolkit manually and it fixed it, but it erased everything on my sd

I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?

aghilvr said:
I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?
Click to expand...
Click to collapse
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.

chromium96 said:
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.
Click to expand...
Click to collapse
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images

aghilvr said:
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.

chromium96 said:
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.
Click to expand...
Click to collapse
Oh that's why it didn't work all the time
Thanks chromium :fingers-crossed:

Hey thanks guys, my device is back to normal. Chromium a special thanks for you for helping me out. See you guys with my next problem/queris!

help pls. n7 stuck at boot anim after 4.4 kitkat OTA upd.does not start

Hello mates,
this morning my nexus 7-wifi (unlocked bot not rooted. w/ CWM) said me there is a system update for new android os. Kitkat.
Then i install the update without getting any CWM backup.
Zip file started to be installed in CWM and it processed all install. steps successfully.
However when the progress bar reach to %100, it said something like "...status 7.... installation aborted" (do not remember clearly).
And after reboot i come across a new boot animation (kitkat's new animation i think) which does not end up to a system start or an error message.
Now,
what should i do to complete installation of kitkat?
Thanks in advance.

cozgun said:
Hello mates,
this morning my nexus 7-wifi (unlocked bot not rooted. w/ CWM) said me there is a system update for new android os. Kitkat.
Then i install the update without getting any CWM backup.
Zip file started to be installed in CWM and it processed all install. steps successfully.
However when the progress bar reach to %100, it said something like "...status 7.... installation aborted" (do not remember clearly).
And after reboot i come across a new boot animation (kitkat's new animation i think) which does not end up to a system start or an error message.
Now,
what should i do to complete installation of kitkat?
Thanks in advance.
Click to expand...
Click to collapse
OTA Update cannot be flashed using CWM,you will need to use stock recovery.
Sent from my Nexus 7 using XDA Premium 4 mobile app

Ben Ling said:
OTA Update cannot be flashed using CWM,you will need to use stock recovery.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi Ben,
what should i do now ? i downloaded a file of 360 MB into my PC, should i flash this file?
or
can i flash the file (~180 MB) which my nexus downloaded over wi-fi? if i am capable of using this file, in which directory should i look for this file ?
Thanks in advance.

cozgun said:
Hi Ben,
what should i do now ? i downloaded a file of 360 MB into my PC, should i flash this file?
or
can i flash the file (~180 MB) which my nexus downloaded over wi-fi? if i am capable of using this file, in which directory should i look for this file ?
Thanks in advance.
Click to expand...
Click to collapse
What file have you downloaded ?

Ben Ling said:
What file have you downloaded ?
Click to expand...
Click to collapse
tgz file of android 4.4 for nexus 7 2012 wifi. nakasig-krt16s

cozgun said:
tgz file of android 4.4 for nexus 7 2012 wifi. nakasig-krt16s
Click to expand...
Click to collapse
you downloaded the factory image ?

yes Ben, the factory image.

Ben,
by the way i cannot open stock recovery. when i push power + v.down, n7 opening in CWM. it will be great if you can help on this as well.

Ben,
by the way i cannot open stock recovery. when i push power + v.down, n7 opening in CWM. it will be great if you can help on this as well.

I did the same
cozgun said:
Ben,
by the way i cannot open stock recovery. when i push power + v.down, n7 opening in CWM. it will be great if you can help on this as well.
Click to expand...
Click to collapse
I did the same exact thing that you did and experienced the same error. Luckily, I came across a stickied thread, ""Flashing a factory image with fastboot / return to stock" and followed the instructions EXACTLY and.. it worked! It took me back to 4.3 which was great because at lease tablet was working again! (I had tried everything else I could think of!) What was funny was that within 2 minutes of the tablet up and running again I received the OTA push for 4.4!
I would strongly suggest following the instructions posted in the thread I mentioned above as they worked perfectly.

Boeing787Guy said:
I did the same exact thing that you did and experienced the same error. Luckily, I came across a stickied thread, ""Flashing a factory image with fastboot / return to stock" and followed the instructions EXACTLY and.. it worked! It took me back to 4.3 which was great because at lease tablet was working again! (I had tried everything else I could think of!) What was funny was that within 2 minutes of the tablet up and running again I received the OTA push for 4.4!
I would strongly suggest following the instructions posted in the thread I mentioned above as they worked perfectly.
Click to expand...
Click to collapse
Hello buddy,
thank you for the feedback. But i do not want to lose my data in the tablet. So, first i will try to fix this without wiping data.
Currently i install adb files to my pc.
And i managed to find the zip file i need to upgrade from 4.3 to 4.4 without losing any data.
If i can flash this zip file via adb i will be ok. but i cannot flash it via adb, because of the recovery i am using (i think ). With CWM i could not do that. after adb sideload **********.zip command, it says "error: device not found"
now i am looking for a solution to this error.
But if i could have had my tablet open in stock recovery, it might already be solved.

PROBLEM SOLVED.
HERE IS THE STEPS TAKEN:
DOWNLOAD OTA FILE FROM 4.3 TO 4.4 (NOT FACTORY IMAGE).
DOWNLOAD LATEST SDK, RUN SETUP.
PUT THE OTA FILE IN sdk\platform-tools DIRECTORY.
SIDELOADING THE OTAFILE:
http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/
IF YOUR DEVICE IS NOT RECOGNIZED DURING SIDELOADING CHECK THIS:
http://blog.dantup.com/2012/10/fixing-adb-device-not-found-with-nexus-7-in-recovery-mode/
AFTER SIDELOADING, IF YOU GET STATUS 7 ERROR, TRY THIS:
http://forum.xda-developers.com/showpost.php?p=47474021&postcount=26&nocache=1&z=7376160805579275
NO DATA LOST IN THIS METHOD.

cozgun said:
PROBLEM SOLVED.
HERE IS THE STEPS TAKEN:
DOWNLOAD OTA FILE FROM 4.3 TO 4.4 (NOT FACTORY IMAGE).
DOWNLOAD LATEST SDK, RUN SETUP.
PUT THE OTA FILE IN sdk\platform-tools DIRECTORY.
SIDELOADING THE OTAFILE:
http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/
IF YOUR DEVICE IS NOT RECOGNIZED DURING SIDELOADING CHECK THIS:
http://blog.dantup.com/2012/10/fixing-adb-device-not-found-with-nexus-7-in-recovery-mode/
AFTER SIDELOADING, IF YOU GET STATUS 7 ERROR, TRY THIS:
http://forum.xda-developers.com/showpost.php?p=47474021&postcount=26&nocache=1&z=7376160805579275
NO DATA LOST IN THIS METHOD.
Click to expand...
Click to collapse
i try to do that
but when i trying to adb sideload ...zip says error:closed
its maybe im on twrp?
what can i do
plz help me im stuck in bootloop too
plz

pediashkavar buddy,
I am sorry, i have never used twrp.

cozgun said:
PROBLEM SOLVED.
HERE IS THE STEPS TAKEN:
DOWNLOAD OTA FILE FROM 4.3 TO 4.4 (NOT FACTORY IMAGE).
DOWNLOAD LATEST SDK, RUN SETUP.
PUT THE OTA FILE IN sdk\platform-tools DIRECTORY.
SIDELOADING THE OTAFILE:
http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/
IF YOUR DEVICE IS NOT RECOGNIZED DURING SIDELOADING CHECK THIS:
http://blog.dantup.com/2012/10/fixing-adb-device-not-found-with-nexus-7-in-recovery-mode/
AFTER SIDELOADING, IF YOU GET STATUS 7 ERROR, TRY THIS:
http://forum.xda-developers.com/showpost.php?p=47474021&postcount=26&nocache=1&z=7376160805579275
NO DATA LOST IN THIS METHOD.
Click to expand...
Click to collapse
Does this work on a rooted nexus?
Only reason I'm asking is cause the sideloading link states "..to update nexus without root..."

Please help. Bricked. cant enter download mode after 4.4.2

I flashed Malladus stock 4.4.2 rom on my VS980 but wanted to try AOSP. I was watching tv when I was wiping everything to prepare the AOSP rom flash. I accidentally formatted internal storage and now I cant restore my backup file or flash any other rom i had stored on my phone or go into download mode. I think I really bricked my G2 this time. If anyone knows how to fix this please help me out thank you!

hi
http://forum.xda-developers.com/showthread.php?t=2432476 (pinned)
gl

On PhilZ you can use a usb drive to flash your rom... Or if you have a less functional recovery you can just use LGflash to restart from the start.. you are far from bricked dude..

whoamanwtf said:
On PhilZ you can use a usb drive to flash your rom... Or if you have a less functional recovery you can just use LGflash to restart from the start.. you are far from bricked dude..[/QU
I have TWRP 2.7.0.0. Which is the only screen i can boot into at this point. I do have the LG Flash tool installed on my pc that i have used before to get out of trouble. But since i flashed the 24a bootstack and rom, now i cant get into download mode so the the flash tool does not recognize my phone. is there a different method to go about it using the lf flash tool? There is a file that i should have flashed that allows me to get back my download mode after flashing 24a bootstack, but i never flashed it and now my whole storage is wiped. I appreciate your help.
Click to expand...
Click to collapse

fmrtz said:
whoamanwtf said:
On PhilZ you can use a usb drive to flash your rom... Or if you have a less functional recovery you can just use LGflash to restart from the start.. you are far from bricked dude..[/QU
I have TWRP 2.7.0.0. Which is the only screen i can boot into at this point. I do have the LG Flash tool installed on my pc that i have used before to get out of trouble. But since i flashed the 24a bootstack and rom, now i cant get into download mode so the the flash tool does not recognize my phone. is there a different method to go about it using the lf flash tool? There is a file that i should have flashed that allows me to get back my download mode after flashing 24a bootstack, but i never flashed it and now my whole storage is wiped. I appreciate your help.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2582142
Click to expand...
Click to collapse

x10tom said:
hi
http://forum.xda-developers.com/showthread.php?t=2432476 (pinned)
gl
Click to expand...
Click to collapse
I read the thread but doesnt this require you to boot in to download mode? How else would you run this method. sorry if I missed something.

fmrtz said:
I read the thread but doesnt this require you to boot in to download mode? How else would you run this method. sorry if I missed something.
Click to expand...
Click to collapse
Why don't you sideload/push a rom and install it ?

bender_007 said:
Why don't you sideload/push a rom and install it ?
Click to expand...
Click to collapse
ok I am new to this sideload but did some research and managed to figure it out. But now when I type in adb sideload romiwanttointall.zip it tells me *cannot read the zip file. I tried doing it with an APK file and it sideloaded fine. just the zip files it says it cannot read. Any ideas of how i can get past this? thanks alot i wasnt even aware of this feature.

fmrtz said:
ok I am new to this sideload but did some research and managed to figure it out. But now when I type in adb sideload romiwanttointall.zip it tells me *cannot read the zip file. I tried doing it with an APK file and it sideloaded fine. just the zip files it says it cannot read. Any ideas of how i can get past this? thanks alot i wasnt even aware of this feature.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2747964
try with this

fmrtz said:
whoamanwtf said:
On PhilZ you can use a usb drive to flash your rom... Or if you have a less functional recovery you can just use LGflash to restart from the start.. you are far from bricked dude..[/QU
I have TWRP 2.7.0.0. Which is the only screen i can boot into at this point. I do have the LG Flash tool installed on my pc that i have used before to get out of trouble. But since i flashed the 24a bootstack and rom, now i cant get into download mode so the the flash tool does not recognize my phone. is there a different method to go about it using the lf flash tool? There is a file that i should have flashed that allows me to get back my download mode after flashing 24a bootstack, but i never flashed it and now my whole storage is wiped. I appreciate your help.
Click to expand...
Click to collapse
TWRP + ADB SIDELOAD
http://forum.xda-developers.com/showthread.php?t=2746585
Click to expand...
Click to collapse

x10tom said:
fmrtz said:
TWRP + ADB SIDELOAD
http://forum.xda-developers.com/showthread.php?t=2746585
Click to expand...
Click to collapse
I installed the SDK and everything is showing up correctly such as when i type adb device it shows sideload. but once i enter "adb sideload malladus-vs980-2.0.2.zip" it says *cannot read malladus-vs980-2.0.2.zip*. Im stuck on this step. Tried sideloading the gapps package as well but get the same error. If I do an APK file it works fine.
Click to expand...
Click to collapse

fmrtz said:
x10tom said:
I installed the SDK and everything is showing up correctly such as when i type adb device it shows sideload. but once i enter "adb sideload malladus-vs980-2.0.2.zip" it says *cannot read malladus-vs980-2.0.2.zip*. Im stuck on this step. Tried sideloading the gapps package as well but get the same error. If I do an APK file it works fine.
Click to expand...
Click to collapse
did you select "adb sideload" in twrp
if not, then type "adb push malladus-vs980-2.0.2.zip /sdcard/malladus.zip"
Click to expand...
Click to collapse

bender_007 said:
fmrtz said:
did you select "adb sideload" in twrp
if not, then type "adb push malladus-vs980-2.0.2.zip /sdcard/malladus.zip"
Click to expand...
Click to collapse
Yes. adb sideload is running on the device. like I said, I sideloaded an APK just to see what would happen and it worked. Just when I push zip files it says cannot read
Click to expand...
Click to collapse

fmrtz said:
bender_007 said:
Yes. adb sideload is running on the device. like I said, I sideloaded an APK just to see what would happen and it worked. Just when I push zip files it says cannot read
Click to expand...
Click to collapse
try putting the rom.zip on c:\
then type adb push c:\rom.zip /sdcard/rom.zip
(turn off sideloading)
Click to expand...
Click to collapse

[Q] Bootloop

I recently attempted to flash a new rom and i accidentally wiped internal storage and i rebooted with no os so im stuck in a bootloop and i cant get to recovery. Is there any way I can get to recovery and load a rom from my pc? Thanks for suggestions.

theunknownshadow said:
I recently attempted to flash a new rom and i accidentally wiped internal storage and i rebooted with no os so im stuck in a bootloop and i cant get to recovery. Is there any way I can get to recovery and load a rom from my pc? Thanks for suggestions.
Click to expand...
Click to collapse
You can get to recovery by doing hard reset volume down + power, release and hold again after lg logo.
If you have adb setup you can load a ROM, or you can do back to stock.

Art Vanderlay said:
You can get to recovery by doing hard reset volume down + power, release and hold again after lg logo.
If you have adb setup you can load a ROM, or you can do back to stock.
Click to expand...
Click to collapse
Can you give me a link to d801 ADB?

theunknownshadow said:
Can you give me a link to d801 ADB?
Click to expand...
Click to collapse
ADB is the same for every device. Download the android ADT bundle from Google. ADB is in the "\SDK\Platform-tools\" folder. Put a small ROM zip in there (like that barebones ROM), then shift-right click in that folder and select "Open command window here..." and type "ADB sideload romname.zip" while your phone is plugged in and in its recovery's respective sideload mode.
Sent from my LG-D800 using XDA Free mobile app

i followed the steps for sideload but it says device not found though i installed the lg united d801 drivers. What do i do?

theunknownshadow said:
i followed the steps for sideload but it says device not found though i installed the lg united d801 drivers. What do i do?
Click to expand...
Click to collapse
Try this one
choose manually from the list(browse the dir)

bender_007 said:
Try this one
choose manually from the list(browse the dir)
Click to expand...
Click to collapse
I cant seem to find it. Can you help me?

theunknownshadow said:
I cant seem to find it. Can you help me?
Click to expand...
Click to collapse
Ok, give me few minutes to upload something, then my inet is usable.

bender_007 said:
Ok, give me few minutes to upload something, then my inet is usable.
Click to expand...
Click to collapse
i used the adb push tool, but i cant get past step 2

theunknownshadow said:
i used the adb push tool, but i cant get past step 2
Click to expand...
Click to collapse
well..you need to have the drivers installed.

Help!

How could I flash recovery without pc? I have twrp at the moment and i want the CWM. Im on 6.0 Emui 4.1

staska_lt said:
How could I flash recovery without pc? I have twrp at the moment and i want the CWM. Im on 6.0 Emui 4.1
Click to expand...
Click to collapse
Try with the Flashify app.

GaT7 said:
Try with the Flashify app.
Click to expand...
Click to collapse
I tried and i got black screen

Flash it via TWRP then? TWRP supports flashing .img too if you need to. :|

3. Post using a clear and descriptive subject and message.
You're most likely to receive a helpful answer to your question, if you use a short subject title that describes your problem and a message that explains in detail, what your problem is and what you've done to try solving it.
Click to expand...
Click to collapse
Source (Forum rules): http://forum.xda-developers.com/announcement.php?a=81
Just sayin bro...
And btw some things just dont work well without a PC. Even though it might be possible to work around it you might just wanna do this on a computer with these commands in adb:
Code:
adb reboot bootloader
and
Code:
fastboot flash recovery recovery.img
and then reboot

PCSE said:
Source (Forum rules): http://forum.xda-developers.com/announcement.php?a=81
Just sayin bro...
And btw some things just dont work well without a PC. Even though it might be possible to work around it you might just wanna do this on a computer with these commands in adb:
and
and then reboot
Click to expand...
Click to collapse
I tried to flash via twrp. It said that the install was succesful, but when i tried to go to recovery i got black screen

Why would you want cwm? TWRP is way better. Oh and your recovery is gone. You can be lucky that you didn't brick your phone. Next time, use TWRP instead and ONLY if you have the ability to restore everything with a PC. ONLY make such hard modifications to your phone if you have a PC nearby

Confirm that you're fully rooted using something like Root Checker

GaT7 said:
Confirm that you're fully rooted using something like Root Checker
Click to expand...
Click to collapse
Im sure im fully rooted

Ok, I suspect something may be wrong with your root or TWRP or ROM, which may be the reason for the odd problems.
So do check & confirm root anyway, & also tell us the versions of your TWRP & ROM (latter in Settings > About phone > Build number).

GaT7 said:
Ok, I suspect something may be wrong with your root or TWRP or ROM, which may be the reason for the odd problems.
So do check & confirm root anyway, & also tell us the versions of your TWRP & ROM (latter in Settings > About phone > Build number).
Click to expand...
Click to collapse
Im on sakoban's rom. B564