Database Develop

HD+ Softbricked (?)

Hey guys!
I'm have a Nook HD+ running AOSP Nougat from amaces along with TWRP 3.0.2-0 as recovery.
(http://forum.xda-developers.com/nook-hd/development/marshmallow-nook-hd-hd-t3239269)
After a while of use, some apps started to crash as soon as I open them, and more and more apps started crashing over time.
I decided to get into recovery and reflash the ROM, but the recovery got stuck on the first screen, where you can see name and version of the recovery and nothing else (I believe it's called splash screen?). Since then, it always boot into the recovery and stays at the splash screen, whatever I do. Doesn't matter if I boot it normally or boot to recovery or have a bootable micro SD with recovery inserted, it always goes directly into the emmc recovery and gets stuck.
Any idea how I could rescue my tablet? Thank you very much!

N0he said:
Hey guys!
I'm have a Nook HD+ running AOSP Nougat from amaces along with TWRP 3.0.2-0 as recovery.
(http://forum.xda-developers.com/nook-hd/development/marshmallow-nook-hd-hd-t3239269)
After a while of use, some apps started to crash as soon as I open them, and more and more apps started crashing over time.
I decided to get into recovery and reflash the ROM, but the recovery got stuck on the first screen, where you can see name and version of the recovery and nothing else (I believe it's called splash screen?). Since then, it always boot into the recovery and stays at the splash screen, whatever I do. Doesn't matter if I boot it normally or boot to recovery or have a bootable micro SD with recovery inserted, it always goes directly into the emmc recovery and gets stuck.
Any idea how I could rescue my tablet? Thank you very much!
Click to expand...
Click to collapse
+1 on this, I am seeing the exact same behavior. After running a while there seems to start cascading failures of apps. Browser stopped, google play most common, MTP host stops...
TWRP hangs on the splash screen , Ive tried all (3) 3.0.2. variants.... I am running the NDE63P 7.1 build...
in my case, however, if I boot from a card into OLD Cwm, don't do anything, and then reboot from the tablet, I am then able to boot from emmc normally.

N0he said:
After a while of use, some apps started to crash as soon as I open them, and more and more apps started crashing over time.
I decided to get into recovery and reflash the ROM, but the recovery got stuck on the first screen, where you can see name and version of the recovery and nothing else (I believe it's called splash screen?).
Click to expand...
Click to collapse
Sounds like your userdata partitions got corrupted; F2FS? Anyway, you will need to find a way to re-format it manually, preferably ext4 (make_ext4fs /dev/block/bootdevice/by-name/userdata, I think).
N0he said:
Since then, it always boot into the recovery and stays at the splash screen, whatever I do. Doesn't matter if I boot it normally or boot to recovery or have a bootable micro SD with recovery inserted, it always goes directly into the emmc recovery and gets stuck.
Click to expand...
Click to collapse
When recovery cannot mount its partitions (by default, including /data and /cache), it will hang, so you have to either build a TWRP image that doesn't attempt to use /data, or use the old CWM from the external card, which doesn't understand F2FS. The external recoveries should always boot, if nothing else is broken.
mikeataol said:
in my case, however, if I boot from a card into OLD Cwm, don't do anything, and then reboot from the tablet, I am then able to boot from emmc normally.
Click to expand...
Click to collapse
Yes, all these recoveries clear the boot count, but only after they finish booting. When TWRP doesn't finish a full boot, the system is still marked for recovery.
As a side note, I really don't understand why people insist on using (highly) experimental builds without a good understanding of how to rescue from soft-bricks…

amaces said:
Sounds like your userdata partitions got corrupted; F2FS? Anyway, you will need to find a way to re-format it manually, preferably ext4 (make_ext4fs /dev/block/bootdevice/by-name/userdata, I think).
The external recoveries should always boot, if nothing else is broken.
Click to expand...
Click to collapse
The TWRP recoveries on the SD card ddont boot, they hang as well. Only the CWM boots
I was trying to ascertain if the file system was corrupted, or if just TWRP was broken.
The rom boots and runs normally from emmc, no signs anywhere that there is corruption, except subtle hints... (change settings on an app, clear data and cache on an app, and on the successful reboot into the rom those changes don't seem to have stuck.

mikeataol said:
The TWRP recoveries on the SD card ddont boot, they hang as well. Only the CWM boots
I was trying to ascertain if the file system was corrupted, or if just TWRP was broken.
Click to expand...
Click to collapse
Right, CWM is one of the recoveries on the SD card. No recovery that supports F2FS and wants to access /data will work at this point; it just happens that CWM can skip that step.

@amaces and as you suggested, booting cwm from the card
reformatting userdata (make_ext4fs /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata )
allowed TWRP to work again just ducky.....

Thank you for taking your time to help me!
amaces said:
When recovery cannot mount its partitions (by default, including /data and /cache), it will hang, so you have to either build a TWRP image that doesn't attempt to use /data, or use the old CWM from the external card, which doesn't understand F2FS. The external recoveries should always boot, if nothing else is broken.
Click to expand...
Click to collapse
In my case, I am unable to boot from the microSD card at all, the device always boots into the emmc recovery no matter what I do.
amaces said:
Sounds like your userdata partitions got corrupted; F2FS?
Click to expand...
Click to collapse
I did not know what F2FS is, but from googling, I assume it is something the user would have to manually set, which did not happen in my case.
amaces said:
Anyway, you will need to find a way to re-format it manually, preferably ext4 (make_ext4fs /dev/block/bootdevice/by-name/userdata, I think).
Click to expand...
Click to collapse
Is it possible to do so without access to recovery? Can you give me some directions to where I can get the info to be able to do so? Any good posts on that, or any keyword I could research around? Would fastboot work? I'm not too sure where to start.
amaces said:
As a side note, I really don't understand why people insist on using (highly) experimental builds without a good understanding of how to rescue from soft-bricks…
Click to expand...
Click to collapse
From what I have seen in the forums, I assumed having a "rescue microSD card" would make flashing ROMs fairly save, but I guess I'll stick to stable builds from now on then. But then again, doing stupid stuff does make me learn new things, and I was willing to risk bricking my tablet.
Anyways, thank you for helping me and for all your work to keep the Nooks alive!

N0he said:
In my case, I am unable to boot from the microSD card at all, the device always boots into the emmc recovery no matter what I do.
Click to expand...
Click to collapse
Hi
You should make another card using a different MicroSD. Not all cards work for booting NOOKS.
A class 4 brand name card usually works
the disk image amace has here :https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3332706778/59738502081/1
has a CWM recovery and 2 TWRP recoveries to choose from on boot.

mikeataol said:
Hi
You should make another card using a different MicroSD. Not all cards work for booting NOOKS.
A class 4 brand name card usually works
the disk image amace has here :https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3332706778/59738502081/1
has a CWM recovery and 2 TWRP recoveries to choose from on boot.
Click to expand...
Click to collapse
I am using a card that has worked for me multiple times in the past. This is not the first time I had to reflash my recovery, it's just the first time I cannot get into the external recovery.

N0he said:
I am using a card that has worked for me multiple times in the past. This is not the first time I had to reflash my recovery, it's just the first time I cannot get into the external recovery.
Click to expand...
Click to collapse
Have you checked whether adb is working while you are sitting at the splash screen for TWRP?
If yes, then you can execute the make_ext4fs command
"make_ext4fs /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata"
to format your /userdata partition.
I was able to do this while stuck on a TWRP splash screen
this will reset your file system back to ext4, (and wipe it) . if you are going to reload one of the newer roms , you'd of course want to convert it back to f2fs before installing.
the NBD90Z 161019 build is working very well for me....

N0he said:
I am using a card that has worked for me multiple times in the past. This is not the first time I had to reflash my recovery, it's just the first time I cannot get into the external recovery.
Click to expand...
Click to collapse
So, it never presents the external recovery menu, where you could select CWM before? You might need to format and re-build that SD card if that's the case.
mikeataol said:
Have you checked whether adb is working while you are sitting at the splash screen for TWRP?
If yes, then you can execute the make_ext4fs command
"make_ext4fs /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata"
to format your /userdata partition.
Click to expand...
Click to collapse
Yes, do try this even with the eMMC recovery; ADB should be working, and you might be able format userdata if it was ext4 before. With some F2FS corruption, it's less likely to work, since it'll say /data is in use, and you can't unmount it.
mikeataol said:
if you are going to reload one of the newer roms , you'd of course want to convert it back to f2fs before installing.
Click to expand...
Click to collapse
I think you should stick to ext4 while testing these issues. I did notice more corruption with F2FS on the new kernel, but didn't have time to investigate yet.

My tablet randomly booted into the microSD card overnight while charging for some reason, and since then, I'm able to boot into the card cwm.
Trying to format the device, I get following error: /sbin/sh: make_ext4fs: not found
I looked into /sbin/sh and found mke2fs and mkfs.ext2, how should I proceed?

N0he said:
My tablet randomly booted into the microSD card overnight while charging for some reason, and since then, I'm able to boot into the card cwm.
Trying to format the device, I get following error: /sbin/sh: make_ext4fs: not found
I looked into /sbin/sh and found mke2fs and mkfs.ext2, how should I proceed?
Click to expand...
Click to collapse
I think you should format it mkfs.ext2 then, ....
that should allow you to boot into the internal recovery and then convert it to ext4

Thank you both for taking your time to help me!
I'm going to summarize what I did to get my tablet back to working:
1. Having the tablet shut down because of low battery seems to have been the reason why I could boot from the microSD card again. So what can be done in that situation is to boot into the emmc recovery (which gets stuck at the splash screen) and then just leave it on until it shuts itself off. Then charge it up again and try to boot into the microSD card. Worked for me.
2. To then actually fix the problem, make sure to have CWM on the microSD card. There are at least two ways to get the tablet to work again:
- Boot into CWM, then connect to a pc with adb, reformat with adb shell using "make_ext4fs /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata" (didn't work for me, as it couldn't find make_ext4fs)
- Boot into CWM, install stock recovery, use it to factory reset the tablet, boot into stock ROM once to make sure, boot into CWM, flash all your stuff.

How to prevent data/internal storage encryption after ROM switch?

Yesterday i flashed xiome eu stable ROM from weekly beta but couldn't boot as all my data was encrypted with strange random folder name. I had to format data to boot into ROM. I am using orange fox kwrnel 11.0. How can i prevent this from happen in future when flashing other ROM?

shoeseat said:
Yesterday i flashed xiome eu stable ROM from weekly beta but couldn't boot as all my data was encrypted with strange random folder name. I had to format data to boot into ROM. I am using orange fox kwrnel 11.0. How can i prevent this from happen in future when flashing other ROM?
Click to expand...
Click to collapse
When switching ROM you have to Format Data in TWRP. Not just because of strange folder names but to avoid all kinds of troubles. New ROM will encrypt Data and Internal storage, you will have protection and everything will properly work as originally
New TWRP versions know how to read encryption, when booting to TWRP you will have to enter your Android Pin/Pattern (same as when you boot to Android or you use to unlock the screem in Android) and TWRP will then also work properly
That's the price of switching ROMs. Backup your Data to PC, backup things (WA and so) to Google and cloud, etc, and restore upon installing the new ROM (btw, I use also Mi Cloud and it restores automatically my apps and other things)
Otherwise, you had to Forrmat Data originally and flash DFE = Disable Forced Encryption (I never used, old school from the times when TWRP did not know to work with encrypted Data and Internal storage) with all your ROMs to prevent them to encrypt. However, you would have no protection then (in Android and TWRP).
Furthermore, after switching the ROM, you could expect then various troubles since new ROM trying to work with settings saved by the old ROM.
Hence, you would still have to Wipe Data upon that ROM switch - therefore, what do you get then by avoiding formatting and proper encryption to automatically happen when booting to the newly installed ROM

Thanks for the explanation but this encryption of data and formatting data partition was never the problem in my past devicea like nexus 5 and oneplus 3 roms. I freely flashed many roms in those devices without formatting my internal storage. Wiping data and system were the only thing i did in past to flash new rom. Is this the xiome phones only restriction?
Also if i have to backup all my data in PC Everytime i want to switch to new rom then it's very troublesome and time consuming aa i have 200GB of data in my internal storage. Isn't their any easy way to flash ROMS without entirely formatting my personal data?

shoeseat said:
Thanks for the explanation but this encryption of data and formatting data partition was never the problem in my past devicea like nexus 5 and oneplus 3 roms. I freely flashed many roms in those devices without formatting my internal storage. Wiping data and system were the only thing i did in past to flash new rom. Is this the xiome phones only restriction?
Also if i have to backup all my data in PC Everytime i want to switch to new rom then it's very troublesome and time consuming aa i have 200GB of data in my internal storage. Isn't their any easy way to flash ROMS without entirely formatting my personal data?
Click to expand...
Click to collapse
Things change with the evolution of Android. In the old times rooting was simple, just run King(o) root and then flash CM recovery by flashify, and flash the ROM you wanted - but it doesn't apply anymore

zgfg said:
When switching ROM you have to Format Data in TWRP. Not just because of strange folder names but to avoid all kinds of troubles. New ROM will encrypt Data and Internal storage, you will have protection and everything will properly work as originally
New TWRP versions know how to read encryption, when booting to TWRP you will have to enter your Android Pin/Pattern (same as when you boot to Android or you use to unlock the screem in Android) and TWRP will then also work properly
That's the price of switching ROMs. Backup your Data to PC, backup things (WA and so) to Google and cloud, etc, and restore upon installing the new ROM (btw, I use also Mi Cloud and it restores automatically my apps and other things)
Otherwise, you had to Forrmat Data originally and flash DFE = Disable Forced Encryption (I never used, old school from the times when TWRP did not know to work with encrypted Data and Internal storage) with all your ROMs to prevent them to encrypt. However, you would have no protection then (in Android and TWRP).
Furthermore, after switching the ROM, you could expect then various troubles since new ROM trying to work with settings saved by the old ROM.
Hence, you would still have to Wipe Data upon that ROM switch - therefore, what do you get then by avoiding formatting and proper encryption to automatically happen when booting to the newly installed ROM
Click to expand...
Click to collapse
I agree with you point here but i have been using decrypted storage since i go this phone..Mostly i delete my android folder and other folder which might be created by rom itself after flashing any rom with dfe and never had any issue on new roms.

Question UNABLE TO BACK UP ANY ANDROID 12 MIUI OR CUSTOM ROM (internal storage 0mb) in TWRP

I'm able to use backup & restore in Android 11 custom or miui rom. but unable to use it when i flashed android 12 roms.
Can anyone walk me through how to fix this.
Did the ff workaround in youtube as well in any similar post but still not working.
1. Advance wipe > click data >Repair or Change File System > Change File System to EXT2 & EXT4
2. Format data
This process is temporarily working the internal storage is visible, but after booting to system and go back to twrp recovery, the internal storage appears 0mb again.
I flashed stock rom/ eu rom as well in TWRP as i read this is worked with them. but not on my end.
Kindly help me to solve this issue please.

TWRP is not yet compatible with Android 12, it can't decrypt the internal storage. You can't fix it until TWRP (or some other recovery) solves Android 12 support.
I think in theory you might be able to back up the ROM to an unencrypted storage like an SD Card or OTG USB drive, but I'm not sure (and I'm even less sure if such backup could even be successfully restored if you back the partition up without decrypting).

Use otg usb

rufio85 said:
I'm able to use backup & restore in Android 11 custom or miui rom. but unable to use it when i flashed android 12 roms.
Can anyone walk me through how to fix this.
Did the ff workaround in youtube as well in any similar post but still not working.
1. Advance wipe > click data >Repair or Change File System > Change File System to EXT2 & EXT4
2. Format data
This process is temporarily working the internal storage is visible, but after booting to system and go back to twrp recovery, the internal storage appears 0mb again.
I flashed stock rom/ eu rom as well in TWRP as i read this is worked with them. but not on my end.
Kindly help me to solve this issue please.
Click to expand...
Click to collapse
Case_ said:
TWRP is not yet compatible with Android 12, it can't decrypt the internal storage. You can't fix it until TWRP (or some other recovery) solves Android 12 support.
I think in theory you might be able to back up the ROM to an unencrypted storage like an SD Card or OTG USB drive, but I'm not sure (and I'm even less sure if such backup could even be successfully restored if you back the partition up without decrypting).
Click to expand...
Click to collapse
Cisuwek said:
Use otg usb
Click to expand...
Click to collapse
In my opinion it's only possible to backup encrypted storage as in A12 if you flash DfE but then you'll have to format and later you're decrypted and in future you can backup via TWRP.
But you can copy actual personal files with a file manager, if android is booted up, to external storages or internal micro SD. android internal app data can't copied.

Laptapper said:
In my opinion it's only possible to backup encrypted storage as in A12 if you flash DfE but then you'll have to format and later you're decrypted and in future you can backup via TWRP.
But you can copy actual personal files with a file manager, if android is booted up, to external storages or internal micro SD. android internal app data can't copied.
Click to expand...
Click to collapse
You can install cutom roms, flash magisk, kernel and other stuff. The memory is only encrypted, the rest works perfectly fine. Have you checked on the latest recovery?
A new kernel was flashed an hour ago. I have made a backup of the boot and dtbo images. It really works
Not checked to backup complete rom, but suppose it's possible with otg

Cisuwek said:
You can install cutom roms, flash magisk, kernel and other stuff. The memory is only encrypted, the rest works perfectly fine. Have you checked on the latest recovery?
A new kernel was flashed an hour ago. I have made a backup of the boot and dtbo images. It really works
Not checked to backup complete rom, but suppose it's possible with otg
Click to expand...
Click to collapse
.....Not checked to backup complete rom, but suppose it's possible with otg....?
But this is what he wants to do, or not?

Cisuwek said:
You can install cutom roms, flash magisk, kernel and other stuff.
Click to expand...
Click to collapse
I guess (I was in fact asking about exactly this in another thread recently), but then if the install script tries to modify the data partition in any way (which remains encrypted with current recoveries under Android 12), you're almost certainly screwed and at best the installation will fail, at worst you'll have to reinstall everything.

Thanks for the reply guys..this already solved..with the help of @Laptapper in other thread. Using orangefox, dfe,

How to flash a Android 12 ROM without decryption problem?
I've been struggling to flash Android 12 without my internal storage to be unaccessible by TWRP... I simply can't decrypt my data and the only way to fix it is to format data and revert back to a Android 11 ROM. Did anyone manage to flash Android...
forum.xda-developers.com
here's the thread.

Case_ said:
I guess (I was in fact asking about exactly this in another thread recently), but then if the install script tries to modify the data partition in any way (which remains encrypted with current recoveries under Android 12), you're almost certainly screwed and at best the installation will fail, at worst you'll have to reinstall everything.
Click to expand...
Click to collapse
Previously I had a Redmi note 7. On the encrypted partition, I could also install everything in the same way. I am not a specialist, my knowledge has ended here.

Question TWRP Help.

Okay, so thanks to the help of you guys I finally managed to root my phone. Now I want to install Arrow OS on it but before that want to take a nandroid backup. Unfortunately, it shows 0mb internal storage and some error like "Unable to mount /data". !!Not sure if this is the perfect error!! but it's close to this.
I've read how to fix this, by changing the type of filesystem to Ex2 then back to Ex4. But,
1. Is this the way to do it?
2. Will It delete all my data, and/or Custom ROM (ie, will I have to perform the android first time setup again). If yes, is there any other way?
And no, I haven't kept any lock on my device.
Some questions may be extremely basic but I'm completely new and would like to confirm things before regretting them later!
Thanks!

doughnut9 said:
Okay, so thanks to the help of you guys I finally managed to root my phone. Now I want to install Arrow OS on it but before that want to take a nandroid backup. Unfortunately, it shows 0mb internal storage and some error like "Unable to mount /data". !!Not sure if this is the perfect error!! but it's close to this.
I've read how to fix this, by changing the type of filesystem to Ex2 then back to Ex4. But,
1. Is this the way to do it?
2. Will It delete all my data, and/or Custom ROM (ie, will I have to perform the android first time setup again). If yes, is there any other way?
And no, I haven't kept any lock on my device.
Some questions may be extremely basic but I'm completely new and would like to confirm things before regretting them later!
Thanks!
Click to expand...
Click to collapse
Yes, it shows 0mb internal storage because is encrypted, twrp, orange fox cannot deal with android 12 to decrypt.
Changing the type of filesystem to Ex2 then back to Ex4 will delete your files.
So, the only way to do a nandroid backup is to decrypt first, but even so you'll loose all your files because you must format data
how to decrypt xiaomi.eu roms internal storage is now showing in custom recovery
I managed to decrypt Xiaomi.eu rom. my internal storage is now showing in twrp and OrangeFox. The main problem was that is was not able to run mcrypt.zip because Vendor partition was in Read only mode. I use xiaomi.eu Stable 12.0.15. (I have not...
forum.xda-developers.com
I tested this kind of decryption, works fine on MIUI and any other android 12 custom roms.

Hellera said:
Yes, it shows 0mb internal storage because is encrypted, twrp, orange fox cannot deal with android 12 to decrypt.
Changing the type of filesystem to Ex2 then back to Ex4 will delete your files.
So, the only way to do a nandroid backup is to decrypt first, but even so you'll loose all your files because you must format data
how to decrypt xiaomi.eu roms internal storage is now showing in custom recovery
I managed to decrypt Xiaomi.eu rom. my internal storage is now showing in twrp and OrangeFox. The main problem was that is was not able to run mcrypt.zip because Vendor partition was in Read only mode. I use xiaomi.eu Stable 12.0.15. (I have not...
forum.xda-developers.com
I tested this kind of decryption, works fine on MIUI and any other android 12 custom roms.
Click to expand...
Click to collapse
Lose all my "files", not my MIUI. Like I wont have to do the Android setup again right?
Thanks for the reply.

doughnut9 said:
Lose all my "files", not my MIUI. Like I wont have to do the Android setup again right?
Thanks for the reply.
Click to expand...
Click to collapse
Yes, but after format data you must setup MIUI again from scratch... not installing again.

Hellera said:
Sorry, but after format data you must setup MIUI again from scratch...
Click to expand...
Click to collapse
I guess Ill just clear it and directly install ArrowOS without setting MIUI up.
Will work?

doughnut9 said:
I guess Ill just clear it and directly install ArrowOS without setting MIUI up.
Will work?
Click to expand...
Click to collapse
Yes, it will work, but Arrow os is android 12 based, so you'll be not able to backup it because of encryption (0mb internal storage), so you must decrypt it for backup

Hellera said:
Yes, it will work, but Arrow os is android 12 based, so you'll be not able to backup it because of encryption (0mb internal storage), so you must decrypt it for backup
Click to expand...
Click to collapse
Decrypt what for backup? And how?

doughnut9 said:
Decrypt what for backup? And how?
Click to expand...
Click to collapse
I think you don't understand me... I gave you a link above... how to decript... if you don't need to backup don't do it!

Hellera said:
I think you don't understand me... I gave you a link above... how to decript... if you don't need to backup don't do it!
Click to expand...
Click to collapse
Ohhhh! Im extremely sorry for being ignorant! Actually I was outside so couldn't read that link. Thanks a lot!!

unable to mount internal storage due to encryption

Long story short, I've been trying to get into my internal storage via TWRP but its saying that there are 0MB in the internal storage and that there is nothing in the sdcard folder
I've tried formatting it, hasn't worked
I've tried changing the format to FAT and then back to EXT4
then after that didn't work i tried the same but with EXT2 , it showed the amount of storage but still didn't let me see what was inside of the sdcard folder, whenever i'd go in there its just completely empty
Can I please have some help with this, I've been stuck on this for a couple hours now

Ouch! Please don't say that you just formatted userdata (/data).
You've just killed all your data on your phone.
No, I'm not that experienced with TWRP and I don't know which versions under which circumstances it can mount userdata.
I use custom recoveries and just presume that I can't mount userdata in them.
In the normal system (which mounts and decrypts) I use normal tools to sync or backup.

Renate said:
Ouch! Please don't say that you just formatted userdata (/data).
You've just killed all your data on your phone.
No, I'm not that experienced with TWRP and I don't know which versions under which circumstances it can mount userdata.
I use custom recoveries and just presume that I can't mount userdata in them.
In the normal system (which mounts and decrypts) I use normal tools to sync or backup.
Click to expand...
Click to collapse
I didn't format data it self i meant that i factory reset it, sorry i should of been a lot more clear on that

Oh, ok.
Well, in any case, if it's encrypted you need to mount it not with a simple "mount" command but something fancier using dm.
They don't try to make it easy to do.
Unless you're destroyed your system and you're trying to recover your data, whatever you're trying to do is best done in the normal system.

never mind i found a fix for it
well not really a fix just a way around it
thanks for the help ^^

SoftieIsVibing said:
never mind i found a fix for it
well not really a fix just a way around it
thanks for the help ^^
Click to expand...
Click to collapse
I had the same issue so I flashed a raw firmware after taking full system backup. Now TWRP is working fine.