Related
So I've got a wifi-only Samsung Galaxy Tab 10.1" and I have gone through the rooting guide. The guide includes ClockworkMod (CWM) v4.0.0.4, which for the most part, works just fine. I'm able to flash custom ROMs, make backups, and restore backups.
I'm having a problem mounting USB storage from CWM however. I go to the "Mounts and Storage Menu" and then select "mount USB storage." When I do this, I get a message saying:
E:Unable to open ums lunfile (No such file or directory)
Any ideas what this means, and how to fix it? Is anyone else able to mount USB storage from their CWM recovery image?
Anyone can correct me if I'm mistaken...but I believe the reason we see this error is because the Tab is not like phones and the internal storage works differently, there is no sd card so it has nothing to mount. I believe it works more like a hard drive. (MTP is different although I know nothing about it) so CWM produces this error but it is nothing to worry about.
More knowledgeable persons please expound on this, I would like to know more too...
Appreciate the insight -- I hope someone else can expand. To expound on that though, how do you transfer a ROM to the SDcard if you wipe /data and don't already have a ROM available on the SDcard?
I'm worried that I'll accidentally wipe data & cache, but will forget to double-check that I have a ROM on the SDcard partition.
Not to worry, wipe data/factory reset in CWM does nothing to the sd card partition everything will still be there including the ROM file you transferred over.
However factory reset from stock recovery DOES wipe sd card data. So back up your stuff if you do this.
Oh and always make a backup in CWM so you have something to flash in case things get crazy
I'm just trying to plan for a worst case scenario -- let's say all the storage volumes are completely wiped, and all you can do is boot into CWM. On my T-Mobile G2 (Desire Z / Vision), you can mount USB storage, copy over a ROM, and install it.
Looking for some sort of equivalent ability on the Galaxy Tab.
Hmm, let me boot into CWM and see if the computer still can read the tabs storage if I plug it in from there...
Also there is always an ODIN flash.
Nope no dice, i suppose if you were in that scenario ODIN would be your option. I'm not sure if there is an ODIN flashable of stock 3.1, I know there is a .zip i always keep it for emergencies.
Sorry I miss read, there is no ODIN flash.
Would the worst scenario is when you don't even have CWM on the tab?
ODIN flash would probably be your last resort. I am wondering if anyone has run into the worst scenario and got the tab back to the factory stock ROM.
your are right FilltheVoid. if things go completely wrong and you have no backup or rom to flash. Odin will be your savior. You can flash stock roms with Odin bro.
task650 said:
your are right FilltheVoid. if things go completely wrong and you have no backup or rom to flash. Odin will be your savior. You can flash stock roms with Odin bro.
Click to expand...
Click to collapse
Hey Task, do you know where I can find a stock ROM for pt7510 that is ODIN flashable? Ya know, just in case.
Well anywho, I think the point of this is, If you read and follow directions carefully, make backups, and read some more, you will not ever be in this scenario. And there are good, knowledgeable people in this forum that are willing to help you in a bind.
FillTheVoid said:
Hey Task, do you know where I can find a stock ROM for pt7510 that is ODIN flashable? Ya know, just in case.
Well anywho, I think the point of this is, If you read and follow directions carefully, make backups, and read some more, you will not ever be in this scenario. And there are good, knowledgeable people in this forum that are willing to help you in a bind.
Click to expand...
Click to collapse
Even though the question is to Task, i will answer it with whatever i know.
1. http://droidbasement.com/galaxy/sys-backup/hc_31/ - But i read somewhere that this is the ODIN flashable stock of I/O tab
2. ROM | 001002-P7510_KME_Restock.zip - ODIN flashable Stock UEKME ROM
Or you could do:
Boot cwm, then
adb shell
mount /data
mkdir /data/media
adb push stock.zip /data/media/
and flash with cwm
Voila !!!
thank you!
you just saved my tablet! thank you.
i managed to brick my tablet (or so i thought) by an interesting combination of things.
first, i installed Alegro graphing calculator. then, i encrypted my tablet. then, i tried to backup my apps, using titanium backup, and whenever it got to alegro, it crashed superuser, market, myapps, googleapps, calendar, acore...a ton of stuff. so i told titanium to ignore it and backup everyything else, and then i went to the market to try to uninstall. no dice..it force closed everything again. so i went to the settings and tried to factory reset. i went through the steps three times, and nothing happened...the tablet rebooted and was the same as i left it.
so as a last resort i went into clockwork and wiped data and cache. tried to boot, and it was stuck on the Samsung Galaxy Tab 10.1 screen.
rebooted..same...waiting hours...same.
i could still boot to odin and recovery, but i didn't have a zip on my tablet, so i couldn't flash anything. i never thought of using adb to push the zip! but this worked perfectly! (after installing the drivers again on my computer).
thank you thank you thank you!
ansonantonym said:
Even though the question is to Task, i will answer it with whatever i know.
1. http://droidbasement.com/galaxy/sys-backup/hc_31/ - But i read somewhere that this is the ODIN flashable stock of I/O tab
2. ROM | 001002-P7510_KME_Restock.zip - ODIN flashable Stock UEKME ROM
Click to expand...
Click to collapse
Hey 2 questions about the restock ROM:
1) Can it be flashed over In Paris V5?
2) Can it be flashed with CWM?
Update: answered this myself: Yes it can be flashed over in Paris, and no, it has to be flashed with Odin.
I still have a question though: This is not CWM, but is it the stock recovery or do I need to flash that too? Sending the tab in for service (newton's rings)....
This is what I was looking for. I have a slow internet connection, and Clockwork was still working, but nothing else was. Flashed Task's ROM v8... it's looking good so far... You rock, dude.
This worked for me this afternoon! Was stuck in a constant reboot after thinking that the samsung update would be a good thing. Gave thanks!!! Ordered the 30 pin adapter and now dont even need it. Will come in handy though I am sure.
FillTheVoid said:
Anyone can correct me if I'm mistaken...but I believe the reason we see this error is because the Tab is not like phones and the internal storage works differently, there is no sd card so it has nothing to mount. I believe it works more like a hard drive. (MTP is different although I know nothing about it) so CWM produces this error but it is nothing to worry about.
More knowledgeable persons please expound on this, I would like to know more too...
Click to expand...
Click to collapse
This maybe complete rubbish, but I can report a similar issue with the Galaxy S2.
When I install a new ROM, I usually do this:
1/ factory reset
2/ wipe cache
3/ wipe dalvik
4/ Mount ALL the folders, then format each one
When I do this and try to mount USB storage, it says the same error message.
If you then fire up ODIN and push another kernel to the phone, everything works fine. I know its something I am doing wrong, but no idea what!
For you, the solution is to use odin to push another kernel across.
Phil
If one enables full device encryption in Ice Cream Sandwich, am I correct in assuming that that the internal SD of that device is now not going to be available in the CWM recovery mode? And even if it was, the root fs would not be available? If so, this pretty much would make CWM flashing your device near impossible?
Does CWM even work if you use FDE? Or is it planned/
The question I guess is, when do you input your encryption password? Is it some pre-boot step?
I really want to enable device encryption but I can't find enugh details on how it works.
I did read this post on it., but it doesn't really answer my questions. And it is unclear if it encrypts the internal SD, or just the root FS?
http://source.android.com/tech/encryption/android_crypto_implementation.html
No one knows anything about this?
I got a Gnex today from Verizon in the US and I encrypted my phone after I unlocked the bootloader but before rooting. As a result I don't think I will be able to root because it doesn't seem that the modified boot.img that the instructions tell me to use can mount the encrypted system (it sat at the Google logo w/ the unlocked icon for 10 minutes before I pulled the battery and let it boot the stock boot.img) which came up fine.
It seems the only way to decrypt the phone is by doing a factory reset.
That's all I know. That being said, while a custom recovery may work for wiping partitions (such as cache), it would probably be mostly useless until the custom recovery is updated to support the encrypted file systems. I'm a *NIX user and an engineer, but don't have a lot of experience with Android's internals, so take all that with the appropriate sized grain of salt.
Regards,
Chris
Bump.
Anyone experimented with full device encryption / ROM flashing / SD Card? I'm curious about this as well, but not curious enough to experiment.
I dident try it myself, so i dont exactly know, how this works. But i think device encryption shouldent completly block clockworkmod recovery.
I think it could be a problem to make a backup while your device is encrypted. But i think it shouldent be a problem to recover a old system over an encrypted one. Encryption keeps people without the key away from reading data. This dosent mean you cant wright something over it and replace the locked data with some new one. But then you defenitly loose the old data. I dont think you can flash a new ROM or a recovery without a full wipe. You probably gona loose all the data you had on the old system.
But i general i think this is anyway a good think to do when you flash a new ROM.
I think you could give it a try, without briking your phone. But i dident try it, so i cant take any responsibility.
Would any of you happen to know how to get to the diagnostic mode?
ryfly65 said:
Would any of you happen to know how to get to the diagnostic mode?
Click to expand...
Click to collapse
I sonst exactly know hat diagnostic Mode you mean. Depends hat Diagnose you want to run. Do you want to read the logfiles in your phone, wher you can see what ist doing? You could use the app alogcat. An other way would be to run logcat over Eclipse.
Sent from my HTC Desire HD using XDA App
Hilmy said:
I sonst exactly know hat diagnostic Mode you mean. Depends hat Diagnose you want to run. Do you want to read the logfiles in your phone, wher you can see what ist doing? You could use the app alogcat. An other way would be to run logcat over Eclipse.
Click to expand...
Click to collapse
I need to edit modem information and enable a diag port for QPST, essentially allowing me to flash it to another carrier.
Is there any new information on this? Any help would be very appreciated!
Sent from my Galaxy Nexus using XDA App
I encrypted mine after flashing the stock ICS 4.0.3 image and rooting. CWM still loads, but when I try to use USB mass storage, windows tells me it needs to be formatted before the SD card can be used.
You can use titanium backup to make backups of your stuff, and restore them to a non-encrypted phone. I have found no other way to unencrypt the phone than factory reset either. When you encrypt, then go to settings > security > encryption, it just has a greyed out area saying "Phone is encrypted", which is stupid and needs to be fixed.
nevarDeath said:
I encrypted mine after flashing the stock ICS 4.0.3 image and rooting. CWM still loads, but when I try to use USB mass storage, windows tells me it needs to be formatted before the SD card can be used.
You can use titanium backup to make backups of your stuff, and restore them to a non-encrypted phone. I have found no other way to unencrypt the phone than factory reset either. When you encrypt, then go to settings > security > encryption, it just has a greyed out area saying "Phone is encrypted", which is stupid and needs to be fixed.
Click to expand...
Click to collapse
So if I factory reset the device from CMW I will not loose my pictures or TB in the internal SD?
What about flashing a new ROM?
Thanks!
I have been playing with ICS + FDE for several days doing different things. First off this is:
Nexus S 4G, running Pete's crespo4g OTA ROM
I flashed with CWM which is still on there and runs fine.
However: /data and /sdcard and /system (?) are encrypted and CANNOT be mounted.
To restore you have to 1) make a full backup over USB to a PC of the whole SDcard (or at least the important folders).
2) wipe and reformat everything. This isn't just a factory reset, this kills the sdcard as well.
3) mount (hopefully) the newly reformatted /sdcard and blow your backup from the PC onto the /sdcard
4) use CWM to restore a previous ROM.
That's pretty much it, give or take. Not for the faint of heart. However, if you are concerned enough to want encryption, you don't want to just say reboot recovery and voila all your files are belong to us, right?
---------- Post added at 03:58 PM ---------- Previous post was at 03:34 PM ----------
Also, the backup to PC part is just your sdcard. It doesn't back up the whole system. There might be a way to do that via adb, I don't know.
So i am running rooted runnig miui.us rom. I just tried to encrypt phone.. It ran for 2 and a half hours and I got impatient. thinking maybe i shouldnt have done it... Then after a little bit of panic i said **** it if i lose data i lose data... so i powered off and back on hoping i didnt and the rom booted back up with all my data intact..... •••••• Wish I had more to report but im not doing that again until someone can confirm that it works fine...... I have tried booting into cwm yet.. If i have an issue when i need to boot illl report back but if you dont hear from me here then assume I was able too.
Pete's to CM9 - still encrypted
IT does indeed take a fairly long time to encrypt. If I understand correctly it will build the encrypted partition on a loopback (or something like) before erasing the original (by overwriting?).
I've got more to report. I followed my plan (couple posts back) for unencrypting and reflashing my phone. (Nexus S 4g).
The first bits of this worked fine. I was able to flash CM9 onto my phone (works like a champ btw). While the phone was in recovery I mounted the SD and copied my backup back onto it.
However...
When CM9 booted I STILL got the "unlock your device" screen, still the same password, and it decrypted and booted. That was surprising, but not as much as when I looked for the SD card, it said it was incorrectly formatted! The only thing to do was reformat and copy with the phone on and unlocked.
So lessons learned: 1) a factory reset from _inside_the_ROM_ doesn't remove the encrypted partition at all and
2) As far as I can tell, the SD card _is_ encrypted along with /data
I'd be very interested to hear other's experiences, especially someone who can remove their SD storage.
Undoing FDE
First off - Lacking a device with removable storage to test with all I can tell you is that the sdcard is not accessible by any normal means after FDE is enabled without booting into the encrypted system.
"Removing" FDE required three steps beyond normal:
-Factory reset from within the ROM
-factory reset/wipe at recovery and/or format /data
-once into a running ROM, reformat the sdcard
Once all that is done (in addition to normal setup for ROM) you should be able to operate normally again.
problem with encryption on sgs2 with android 4.0.3
I really want to enable my device encryption too, but I can't !!!
the phone start encrypting after he ask me for a new secure password, rebooting and asking again for my password and surprise!!!.... the password is not match ?!?!
I repetead these steps for 3 times but the same result...the password does not match!!! ?
Please, if someone found a trick to repair this inconvenient, tell us in this post steps to be followed.
Regards!
SGS2, Android Icecream 4.0.3
leech2082 said:
So i am running rooted runnig miui.us rom. I just tried to encrypt phone.. It ran for 2 and a half hours and I got impatient. thinking maybe i shouldnt have done it... Then after a little bit of panic i said **** it if i lose data i lose data... so i powered off and back on hoping i didnt and the rom booted back up with all my data intact..... •••••• Wish I had more to report but im not doing that again until someone can confirm that it works fine...... I have tried booting into cwm yet.. If i have an issue when i need to boot illl report back but if you dont hear from me here then assume I was able too.
Click to expand...
Click to collapse
I did exactly what you did, and so far everything seems to be intact Thanks!
This error is still not answered on the forums so im starting a new thread.
i get the error as the title.
sd card space is not the problem.
i tried formatting the sd card.
i have less than 50 apps installed.
wiped dalvik cache, and all other sorts people say on other posts.
(my phone is LG P936 so "fix permission" screws up the phone. all text disappears)
have latest cwm recovery.
and still get the error.
any answers please?
and please dont reply if you are going to write an opinion.
only answers please.
sorry for my rude behaviour but I'm sick and tired of reading posts full of opinions and "maybe"s.
Not sure if you ever got this fixed but I 'm suffering from the same error. I tried pretty much everything you tried (even fix permissions) and I have about 20GB free on my SD card so space shouldn't be an issue. I have not yet tried formatting the SD card since it has always worked and CWM is able to write to it because the following files are created:
- boot.img
- data.ext3.tar
- recovery.img
- system.ext3.tar
The files that are missing are (based on older backups):
- .android_secure.vfat.tar
- cache.ext3.tar (probably because I wiped it first?)
- nandroid.md5
I have attached the log from CWM in the hopes that someone can tell me what is wrong. The error occurs at the end of the progress bar of 'backing up /data'.
hey just use TWRP Recovery. It's way better than CWM. normal backup on cwm took me like an hour but twrp was never longer than 10minutes.
Today I have formatted the SD card and tried again, but as expected it did not change anything.
ceoleaders said:
hey just use TWRP Recovery. It's way better than CWM. normal backup on cwm took me like an hour but twrp was never longer than 10minutes.
Click to expand...
Click to collapse
I guess I will give this a try. Can I just install it over CWM or can they run side by side?
different reciveries cannot be run side by side as they are installed on a different partition. so it will always be installed over your current one.
ceoleaders said:
different reciveries cannot be run side by side as they are installed on a different partition. so it will always be installed over your current one.
Click to expand...
Click to collapse
Well, I tried TWRP and it also fails at backing up my data partition. The log is a bit more clear though and it seems to get stuck on "/data/data/com.android.vending/cache/images" which is the last line before it gives an error. I checked the "images" folder and it seems empty but I cannot delete it. Tried ES File Explorer and Terminal Emulator but no way to get rid of it. The folder appears to be related to Google Play, so I cleared all data and cache from Google Play, even uninstalled the updates but there 's simply no way to get rid of it. I 'm not sure if this is the reason why the backup fails, but I CAN copy the folder and even rename it.
Pff looks like I 'm going to have to do a clean install after all .
Hello, I too have this problem and unfortunately TWRP is not available for my phone.
I used to be able to do CWM backups fine on my old phone, and they work great on my tablet. But they consistently fail at "/data" on my Galaxy Ace II x. Might it be because I'm using Link2SD? I don't see why that would cause a problem, but maybe it's having trouble with the symlinks?
Hmm. Seems the issue was that, despite having only 1.28 GB total available storage space on stock, the backups wanted more than 4 GB. Cleared some room on my microSD card and suddenly backups worked fine! Of course, shortly after I installed CyanogenMod, which has much smaller backups...
Sent from my GT-S7560M using Tapatalk 4
I forgot to report back here but the only way I found to fix the problem was by doing a clean install. After that, I was able to backup my data partition again. I then restored my apps ' data with TB and was unable to backup the data partition again. I 'm guessing one of my apps had corrupt data, but never got to find out which one it was.
maybe your partition not match with recovery, like something wrong vold.fstab
Just in case anyone still wants to know how to fix this, I managed to solve it by running these commands:
1. run adb shell in recovery.
2. unmount data partition (umount /dev/block/mmcblk0p26). -> this one failed so I skipped it
3. run e2fsck /dev/block/mmcblk0p26
See http://forum.xda-developers.com/showpost.php?p=48659092&postcount=868 for original post.
I got a few HTREE errors and a bunch of duplicate names which I renamed when prompted. Booted the phone and rebooted into TWRP and now I am able to backup my data partition again. :good:
EDIT: Problem reappeared so I tried the above commands again but it said that the filesystem was clean. Ran 'e2fsck -f /dev/block/mmcblk0p26' instead and had to fix a bunch of HTREE errors from Facebook again and duplicate names from Xprivacy but now I 'm able to backup my data partition again.
Dude just selest the backup format as both zip and tar filea
Hi all,
I didn't find any relevant threads through searches, so I'm reduced to asking for help. Please!
My DNA's been running great on Newt's ROM. I'm S-OFF, rooted, using CM, and all's been great. I'm on T-Mo. I installed the most recent patch on the OP page and, now, my phone won't connect to wifi and in settings>storage it shows "unavailable" for storage.
I've wiped cache and dalvik, done a factory reset, and everything I can think of to get things right - but to no avail so far. When connected to my PC, the phone shows up fine and I can see and delete phone files. But, I cannot copy to the phone so I can't put the ROM zip there to start anew. And, since wifi is in a perpetual "turning on" (but never does) I cannot download directly to the phone.
My phone works fine for calls and texts and data, but I can't install apps or get wifi working.
So, gang, any ideas or suggestions?
Thanks much,
Ross
EDIT to add more detail: I just realized that I cannot even access storage through CM recovery. I may be totally hosed, right? I tried to use the install zip and restore functions in CM, but it reports no files found. And if I go to Gallery, for example, on the phone it says "install SD card". I clearly have some serious memory issue (on my phone too...). Help?
You try flashing back to the original ROM before the patch?
fr4nk1yn said:
You try flashing back to the original ROM before the patch?
Click to expand...
Click to collapse
No, I was already running Newt's NOS ROM and I just flashed the patch/update zip for GSM. I didn't do anything else.
rossvtaylor said:
Hi all,
I didn't find any relevant threads through searches, so I'm reduced to asking for help. Please!
My DNA's been running great on Newt's ROM. I'm S-OFF, rooted, using CM, and all's been great. I'm on T-Mo. I installed the most recent patch on the OP page and, now, my phone won't connect to wifi and in settings>storage it shows "unavailable" for storage.
I've wiped cache and dalvik, done a factory reset, and everything I can think of to get things right - but to no avail so far. When connected to my PC, the phone shows up fine and I can see and delete phone files. But, I cannot copy to the phone so I can't put the ROM zip there to start anew. And, since wifi is in a perpetual "turning on" (but never does) I cannot download directly to the phone.
My phone works fine for calls and texts and data, but I can't install apps or get wifi working.
So, gang, any ideas or suggestions?
Thanks much,
Ross
EDIT to add more detail: I just realized that I cannot even access storage through CM recovery. I may be totally hosed, right? I tried to use the install zip and restore functions in CM, but it reports no files found. And if I go to Gallery, for example, on the phone it says "install SD card". I clearly have some serious memory issue (on my phone too...). Help?
Click to expand...
Click to collapse
Ok, what you're probably going to want to try to do is get rid of CWM Recovery - it has proven short sighted in comparison to TWRP. Do the following;
1. Flash TWRP for the DNA (via GooManager or grab the flashable zip and flash via fastboot)
2. Wipe EVERYTHING - Davik, Cache, Data, System.
3. TWRP Main > Advanced > Sideload
4. Use the 'sideload' command via ADB to flash whichever ROM that you'd like to be running.
5. Reboot System (If it tells you no OS installed, click install from the main and install sideload.zip, normally sideloading the ROM will install aswell, but not always.)
With this method, you start with fresh radios, fresh kernels and a fresh storage.
Hopefully this helps get you back where you'd like to be. I had to do this when I switched from NEWT's NOS 4.3 GPE back to NEWT's NOS MY S5 ROM.
Mushroomhead, thanks. I'm up and alive again!
EDIT to add detail, in case someone else encounters this:
I've not ever used sideload before, but I now understand why it exists. I followed the guidance above, with the exception of changing from CWM to TWRP. I may, indeed, do that and give it a try. But I was unable to download any app - or, for that matter, take any photos or access the Play store or do anything which accessed memory. I couldn't even access my backup files. So, I forged ahead with ClockWorkMod Recovery, using sideload to install the original Newt NOS ROM I had. That worked great.
rossvtaylor said:
Mushroomhead, thanks. I'm up and alive again!
EDIT to add detail, in case someone else encounters this:
I've not ever used sideload before, but I now understand why it exists. I followed the guidance above, with the exception of changing from CWM to TWRP. I may, indeed, do that and give it a try. But I was unable to download any app - or, for that matter, take any photos or access the Play store or do anything which accessed memory. I couldn't even access my backup files. So, I forged ahead with ClockWorkMod Recovery, using sideload to install the original Newt NOS ROM I had. That worked great.
Click to expand...
Click to collapse
Glad to hear it! I've been in the modding game since the G1 was released. I know a bit or two about tons of phones. HTC & RUU. Samsung and ODIN. LG and BLEH (don't ever by an LG device). Glad that it worked out for you man, keep on keeping on.
I am having a problem that I am hoping someone can help me figure out. It is almost a problem I have found several people have, but my situation does not match any of the solutions that work for others with similar issues. Here it is:
I have two tablets, both are Nextbook Ares 8 tablets but one has android 5.0 and the other has 5.1 on it. I wanted to put android 5.1 on both, so I looked it up and found vampirefo's guide to rooting and putting twrp on the 5.0 tablets and figured I would start there to get to where I could put 5.1 on it. Problem is, I put TWRP on both tablets and neither one can mount the data partition so I can't get anywhere with it. I screwed up the 5.0 with a borked 5.1 but I cannot restore it because I can't put my backup on it where twrp can see it.
I, of course, looked up the issue of not being able to load /data and found several solutions. The only thing that sort of works is to format data through twrp on the data partition. This makes it so that while in twrp I can mount the partition, but since I cannot access it to put things on it while the tablet is in TWRP I cannot put the backup on the partition while the tablet can mount the partition. If I reboot the tablet in order to put data on it(or even reboot the tablet straight from TWRP after a reformat and mount to TWRP again) I am no longer able to mount the partition until I again format it(which wipes out any data I have put on it). This is not related to having data on the partition, it is not related to having booted to another mode or connected to any device, and this is not related to anything I have done because the only thing I did after getting the tablets was boot them all up and check the OS version and that the tablets were both the same model number and then I rebooted to bootloader and flashed TWRP on and booted to that. The 5.1 tab has the same issue with not mounting /data, but I am most concerned with it on the 5.0 tablet.
Both tablets are model NXA8QC116
One came with 5.1 on it stock, the other 5.0
TWRP I flashed to both was 2.8.6.0 from vampirefo's post here: https://forum.xda-developers.com/and...overy-t3133165
The tablets both see the data partition when booted normally, but not when in TWRP. That's all the information I know to provide, if anyone can help me figure this out I would appreciate being able to learn why and how this is an issue for me specifically in addition to just solving the problem. After all, I cannot find anyone else having this issue with Ares 8 tablets...they all seem to have no issue with this TWRP being put on this tablet.