[Q] [N8010] - Randomly stuck at boot unable to mount internalSD - Galaxy Note 10.1 Q&A, Help & Troubleshooting

Hi,
I've been following the forum for a while and have rooted / ROM'd several devices and never had any serious issues, until now:crying:.
I've been running james's rom (Resurrection Remix) on a Samsung N8010, this has been fine and worked perfect for months.
All of a sudden for no apparent reason the tablet has decided to not boot fully and gets stuck at the Samsung 10.1 screen.
I've tried flashing several different roms / restoring to factory / wiping data partitions etc with no luck.
Flashing anything other than the current rom seems to fail as it can't mount the internalSD in order to flash to it.
It appears that somehow the internal memory has screwed itself and is now unable to mount /dev/block/mmcblk1p1.
I've tried to view the logs but it seems as the internal is messed up this errors with similar results.
Trying to browse the internal sd through CWM just crashes CWM.
I can still boot into both odin and CWM with no problems but seem stuck in cwm as i'm unable to flash / return to stock via ODIN. Potentially i was thinking i could flash to stock via odin with the 3 file method to sort the partitions out, but it seems practically impossible to find any of these files anywhere!
These are the errors i seem to get are:
Skipping execution of extendedcommand , file not found
Cant partition non-vfat: datamedia
Can't partition unsafe device: dev/block/mmcblk1p1
Can't format unknown volume: /mmc
Your assistance on the matter would be greatly appretiated!
Thanks in advance,
Ash.

Gash128 said:
Hi,
I've been following the forum for a while and have rooted / ROM'd several devices and never had any serious issues, until now:crying:.
I've been running james's rom (Resurrection Remix) on a Samsung N8010, this has been fine and worked perfect for months.
All of a sudden for no apparent reason the tablet has decided to not boot fully and gets stuck at the Samsung 10.1 screen.
I've tried flashing several different roms / restoring to factory / wiping data partitions etc with no luck.
Flashing anything other than the current rom seems to fail as it can't mount the internalSD in order to flash to it.
It appears that somehow the internal memory has screwed itself and is now unable to mount /dev/block/mmcblk1p1.
I've tried to view the logs but it seems as the internal is messed up this errors with similar results.
Trying to browse the internal sd through CWM just crashes CWM.
I can still boot into both odin and CWM with no problems but seem stuck in cwm as i'm unable to flash / return to stock via ODIN. Potentially i was thinking i could flash to stock via odin with the 3 file method to sort the partitions out, but it seems practically impossible to find any of these files anywhere!
These are the errors i seem to get are:
Skipping execution of extendedcommand , file not found
Cant partition non-vfat: datamedia
Can't partition unsafe device: dev/block/mmcblk1p1
Can't format unknown volume: /mmc
Your assistance on the matter would be greatly appretiated!
Thanks in advance,
Ash.
Click to expand...
Click to collapse
Had this on a older device. Go back to the oldest version of factory rom you can find. Now to note so i can only recommend Sam mobile to find one.sounds liks as you said partition are corrupt. Going back to okd os version will redo partitions Is my thinking . I did this on my Acer a500 with issues as you describe I n ics .I went bach to honeycomb. It is a different file part arrangement.
Good luck and please double check and verify my thinking. Do not want you to brick over my advise
Erica Renee

erica_renee said:
Had this on a older device. Go back to the oldest version of factory rom you can find. Now to note so i can only recommend Sam mobile to find one.sounds liks as you said partition are corrupt. Going back to okd os version will redo partitions Is my thinking . I did this on my Acer a500 with issues as you describe I n ics .I went bach to honeycomb. It is a different file part arrangement.
Good luck and please double check and verify my thinking. Do not want you to brick over my advise
Erica Renee
Click to expand...
Click to collapse
Worked perfect thanks! Wiped and flashed via odin back to 4.0 and then re-flashedback to 4.2.2 now no more problems:laugh:

Related

[Q] Curious Flashing (and sdcard?) problem!

Hey guys,
I have a problem, which i couldn't solve using the search. Sorry if i was too stupid to search at all
The thing is this:
I have a Nexus S I9020T which i bought as "broken"
It is stuck at the Google logo with the open lock. I thought i could save that device easily but i can't get that thing to work again.
At first: I still have my first android phone here: a Milestone. I had it for a year now and i would say that i flashed pretty much everything to that device. So i know a thing or two about android and flashing. But i have never had a nexus s in my hands before.
So i did this:
I Opened the Bootloader -> success
I flashed a few different CWM recovery -> also no problem here
I flashed a SU_2.3.6.1 which was already on the sdcard and it flashed without an error
I tried to delete all the files of the previous uswer -> at first I could delete all but as soon as i unmount and mount the usb storage, everything is back to the way it was. Means I can't delete or write anything onto the sdcard
Sometimes i have luck and i can write a .zip file to the card but as soon as I try to flash the ROM CWM says : e:can't open /sdcard/***.zip (bad)
so i know, that sometimes the zip files is just... bad. So i downloaded at least 10 different roms. Always the same problem.
I can'T format the SDcard, at every new mount, everything is back to how it was when i got the phone.
I tried to flash with Odin. But the only thing that changed was that i lost the recovery. So i flashed it new and here i am still stuck with that thing
Odin gets stuck while flashing with som PK[][][] thing -> screenshot. Doesn't seem to get further.. so flashin failed... any ideas?
So my question is:
Is there a problem with the SD card?
Is there just a problem with drivers?
Can My Phone be repaired?
Please you guys help me with your knowledge.
I am living in germany and the nexus is bought in the USW at bestbuy in december 2010. Does someone know how the warranty thing is handled for such a scenario?
Thanks a lot guys for even reading my problem.

[Q] Huawei U8510 stuck at first boot - Bricked?

Help.
I completely screwed up but do not know where.
Had problems rooting but eventually made it with 'Automatic-Root-Enabler--U8510--v1.1' which worked first time.
Then used rom manager to install HuaweiU8510.zip which did not work so tried U8500_Huaweid.zip.
cache and Delvic cleared, rebooted and red huawei came on screen and there it stayed.
Removed battery, boot into recovery went into firmware update(image in dload but cant remember name) starts step 1 unpacking get yellow triangle with ! and says update failed. also tried again with zip files on sd card but back to red Huawei
Any one got any ideas please as I can get to the sd card but not to the internal memory and not adb/fastboot. So no way of getting a new recovery image into dload
Keith
Here in the netherlands there are no huawei phones too bad because on the wmc they announced some pretty good phones ..
But on topic...
Does your phone still start normal?
If not try flashing it back to stock firmware..
Maybe it's a problem with the custom rom...
Sarvesh50 said:
Here in the netherlands there are no huawei phones too bad because on the wmc they announced some pretty good phones ..
But on topic...
Does your phone still start normal?
If not try flashing it back to stock firmware..
Maybe it's a problem with the custom rom...
Click to expand...
Click to collapse
Thanks
1. no
2. trying once I get original rom
3. Funny it is every one I tried
Keith
I do own a galaxy s...
Once i had a similar problem...
It was caused by the filesystem
Samsung uses the rfs system but custom roms prefer ext4 which is better...
When your filesystem isn't compatible with your custom rom than you will have a startup problem so try to figure out if you have to change the filesystem.
can't post links from other sites cause i am a newby to xda forums this is really annoying
Check this
http://forum.xda-developers.com/archive/index.php/t-1200195.html

Flytouch 8 BC1003 Custom Rom and Locked Recovery

Hey gang, I got this Flytouch 8 tablet last week, model number is BC1003, android version 4.0.4, baseband version 1.5rc4, kernel version 3.0.8+ [email protected] #68 Sat Dec 8 08:54:36 CST 2012, build number crane_bc1003-eng 4.0.4 IMM76D 20121217 test-keys.
I've tried several options to load the recovery partition, only way I can access the recovery is through the backup and reset menu in settings, if I try to do it with the device powered off and holding the menu and power it just boots normal. I've tried a number of options home+power, vol up or down + home, none work. When I do get into the recovery, I cannot scroll through the options only thing there is the android robot with a red triangle and an exclamtion point.
Recovery version says android system recovery 3e EVB-V13.
I also cant get the sd card to mount. I've tried refromatting it with fat32, fat16, ext3 ext4. everything I get a message saying sd card damaged. I've tried 3 different card and same thing.
Any ideas XDA friends? I would like to put a custom rom like AOSP or CM9 or CM10 on it and clockwork recovery if that is an option. I've searched the net high and low for roms, I find many for other Flytouch tablets, but not Flytouch 8. This is the allwinner A10 processor in this one.
Thanks for your help friends.
I
Same problem her with a rooted FT 8 (same as yours)
.
After reboot i get sd card damage error.. after give this da RW i can mount this card again in settings/ storage.
After a reboot i get alway the error sd card damage....
I can get CWM 6.02 on this flytouch but didn`t get any custum roms or CWM backup installed...so get back tio basic image file with Livesuite.
have same recovery : recovery 3e EVB-V13 but cannot do anything with it. It don`t react with all the combination button on my flytouch.
Hopefully you can?
Same problem her with my fluytouch 8 32GB any halp pleas.
Recovery menu
hi
I've got the same tablet from china, am stuck at same spot as you are all, but I figured out how to move through menu in recovery, use usb mouse or keyboard.... any news on some custom rom and installation on this lousy tablet would be appreciated......
Solved Recovery Issue.
Hey everyone. I found this thread today, I tried it and it works perfectly. http://forum.xda-developers.com/showthread.php?t=2189640
I also read somewhere that Allwinner A10 and A13 cannot be flashed using stock recovery, you must use a program like Livesuit to flash firmwares. You can flash custom roms using CWM once it's installed on your device.
fldave612 said:
Hey everyone. I found this thread today, I tried it and it works perfectly. http://forum.xda-developers.com/showthread.php?t=2189640
I also read somewhere that Allwinner A10 and A13 cannot be flashed using stock recovery, you must use a program like Livesuit to flash firmwares. You can flash custom roms using CWM once it's installed on your device.
Click to expand...
Click to collapse
thanks man, this is good news, first step forward in cracking this damn slow tablet....now we need decent rom to install, any ideas?
Possible bricked BC1003..
Hi there I've got the exact same tablet with you BC1003 Model Flytouch Allwinner A10 Superpad 8 1GB Ram version running Android 4.0.4 stock.
So after following guides and researching a lot I ended up trying to upgrade to Jelly Bean.
I got CWM 6.02 installed fine. So I started the flash process.
Firstly I backed up my stuff and then I did a wipe data / factory reset.
Then proceeded and installed the latest possible rom version which I found to be : AOKP JB 4.1.2 ALLWINNER A10.zip
So I installed that one and the process went fine.
Then I installed this compatibility pack : t05a-v3_compatibility_1.2.0.zip
It also went fine.
Then I installed this google apps pack : gapps-jb-20120726-signed.zip
And it also installed normally.
So I was ready to reboot my tablet and so I did.
It turned off and then on again and here we are :
I now notice the screen turn on but it never shows anything..
Before flashing it it would turn on and show the Android OEM screen, then show the android loading text and then turn off and on and show the locked screen which I had to unlock and enter my desktop.
I notice that the screen light follows that pattern so the system is running normally only I don't get to actually see anything on it.
Now I'm kinda stuck here.. I've installed LiveSuite but when I try to install the recovery.img I have from my backup it says invalid image..
Have I bricked it or is there a way out of this mess?
Actually it's not entirely bricked.. well I finally got it to work with LiveSuit 1.09 and managed to flash its firmware to a couple more roms.
1. sun4i_crane_t05a_20120409.img -> Ends up showing some messy stuff on the screen. Looks like the resolution is not correct.
2. sun4i_crane_futekoA90universal_20120531.img -> Shows lots of white stuff and colors switching jelly-like.. But still it doesn't work.
3. TAB360-364_Android_411_Jelly_Bean.img -> This is the official A10 Jelly Bean firmware for Yarvik TAB364 GoTab Gravity 8".. No wonder I still got back to the blank screen issue. I only notice the back light turn on and off following the pattern of normal functionality, only I'm not able to actually see it..
Well, at least I'm still able to keep flashing roms to it.. Any ideas?
I can't even find my stock rom to turn back to 4.0.4. Where exactly is it located in my recovery-mode backup?
Btw, in case it plays any part my tablet is 10.2''.
Any help would be greatly appreciated.
EDIT : Finally I figured it out! My correct stock rom is : sun4i_crane_bc1003.img
I found it through google and after flashing to it I managed to get my tablet at a working state. (ICS 4.0.4 ICS 4.0.3)
So, I'll now try to use more Jelly Bean roms without worrying about bricking it.
Oh, something I noticed that might help others too.. even though on the packaging it says Flytouch Superpad 8 Allwinner A10 this tablet model (BC1003) is actually the Flytouch Superpad 7 and that helped me find my correct rom. Keep that in mind from now on. I'll keep you updated if I succeed in booting to Jelly Bean.
Finally some success..
Well, I finally have some interesting updates on the subject.
I managed to get Jelly Bean to work (Versions 4.1.2 and 4.1.1) on my BC1003 tablet without a compatibility pack (still none has worked for me).
Details on 4.1.2 Version :
Rom File Name : AOKP-4.1.2-3.0.52-Revb.zip
System running smoothly with wifi working fine.
Sound is fine and no crashes occurred.
Touchscreen, screen rotation and camera do not work.
I noticed that I can't browse to my external sd card.. it doesn't seem to get mounted.
Details on 4.1.1 Version :
Rom File Name : cm10_a10_20120913.zip
System running extremely smooth with wifi working fine.
Sound is fine and I experienced no crashes.
Touchscreen, screen rotation and camera do not work.
Also could not mount my external sd card.
Important bug noticed : When I try to change the brightness of my tablet's screen it enters suspended mode no matter what I do and is not fixable. I had to reflash the rom to recover from that state.
I think most of the problems would go away if I found a compatible jelly bean compatibility pack for this tablet.
If anyone has any clue please let me know.
So far I've tried these with no luck :
t05a-v3_compatibility_1.2.0.zip
t05a-unk_compatibility_1.2.0.zip
907c_compatibility_1.2.0.zip
By the way the BC1003 ICS rom that I found to be working was actually not my manufacturer's and it was version 4.0.3 instead of 4.0.4 that my original one was.
So, @fldave612 if it's possible could you please backup and upload yours somewhere so that I can also have it?
EDIT: Actually I figured out that I had kept a good backup form my ICS 4.0.4 using clockwork backup/restore and switched back to that for now.
But I've kept a backup of my Jelly Bean installation too so it's very easy to switch to that now. I'll try again once we get a compatibility pack working.
I feel we're very close to completely upgrading to Jelly Bean now on this tablet. We only need a working compatibility pack.
How did you succeed to install these ROMs, I tried both, installation went OK, but after reboot, only black screen......
Sent from my GT-P5110 using xda app-developers app
baschelik said:
How did you succeed to install these ROMs, I tried both, installation went OK, but after reboot, only black screen......
Sent from my GT-P5110 using xda app-developers app
Click to expand...
Click to collapse
I just installed them without a compatibility pack. It's not the jelly bean build that fails.. it's just the compatibility pack.
I researched it a bit and starting to look for a compatibility pack that works on very similar tablets (10.2'' - 1024 x 600 - 1GB Ram).
I found some, and got it to boot without a blank screen. Some showed messy colors others seemed to be working fine but still no touch..
So until we get one working on our specific precious tablet, we're kinda stuck here..
The 4.1.2 version seemed to be working fine but without touchscreen it's pretty much useless.
We could live without a camera or screen rotation, but not without touchscreen..
I even figured out that I could browse to the external sd card by going to root and then storage folder.. instead of mnt..
Actually now I'm stuck with ICS 4.0.3 since the original backup I kept proved to not be working fine.. it kept on crashing all the time..
So if someone has the original BC1003 ICS 4.0.4 that came from the manufacturer please upload it somewhere and post a link here.
Also if someone works on it to create a touchscreen driver for the world would become more beautiful..
Go to this link: http://www.maixin-china.com/software-download.asp Scroll down about half way and go to the link for "MaPan F10B (Cortex A8 Flytouch 6 and Flytouch 8) Software". I used the newest one 11-28.
This is a firmware is the one for this tablet. Use Livesuit to flash it, it will restore the tablet back to 4.0.4 factory.
It is virtually impossible to brick an A10 tablet from what I'm reading because it can be flashed via usb and have to boot loader re-imaged.
This link is very helpful to flash via Livesuit: http://elinux.org/Hack_A10_devices
Hope this helps you all as much as it did for me. Hopefully in the near future some developers will build a CM10 or higher version that will work on this tablet, until then I'll use this rom with Clockwork recovery mod.
Moin @all
Ich have chrashed my tab too but the download link is dead.
Any ideas where ich can load the file ?
Sorry for my ****ty bad English :silly:
Gothfather
I've also got this tablet (BC1003) - thank you for all the useful information posted on this thread so far.
If I've understood correctly, it's possible to install custom firmware using LiveSuite but at the moment none of them fully support this tablet - is that right?
At the very least I'm looking for a way to increase the size of the internal memory partition - the stock partition table has this unnecessary virtual sdcard partition taking most of the 2GB internal memory...
i have one of these damn slow tablets
i watched a vid on youtube about how to remove the internal sd card it is so simple to do it only take like 3 mins and 7 screws ive done this and put a 16gb card in there
i cant post a link but heres the name of the vid "Flytouch 5 / Superpad 6 V10 - Disassembly - Access to internal TF"
it is not the same tablet but is pretty much the same
Tip use a knife to pop the caps off the outside i found this easier
try not to stab yourself.
thanks if i helped you out
noob
okay so i tried to install a new rom on my allwinner a10 bc1003 and ended up only booting a black screen i dont know what im doing as this is my first tablet an very little computer knolage but im interested i had seen in a post he used livesuit to flash the new rom.... i dont understand how that works if anyone could sit down and teach me that would be apriciated
---------- Post added at 12:21 PM ---------- Previous post was at 12:16 PM ----------
SolidSnakeGr said:
Actually it's not entirely bricked.. well I finally got it to work with LiveSuit 1.09 and managed to flash its firmware to a couple more roms.
1. sun4i_crane_t05a_20120409.img -> Ends up showing some messy stuff on the screen. Looks like the resolution is not correct.
2. sun4i_crane_futekoA90universal_20120531.img -> Shows lots of white stuff and colors switching jelly-like.. But still it doesn't work.
3. TAB360-364_Android_411_Jelly_Bean.img -> This is the official A10 Jelly Bean firmware for Yarvik TAB364 GoTab Gravity 8".. No wonder I still got back to the blank screen issue. I only notice the back light turn on and off following the pattern of normal functionality, only I'm not able to actually see it..
Well, at least I'm still able to keep flashing roms to it.. Any ideas?
I can't even find my stock rom to turn back to 4.0.4. Where exactly is it located in my recovery-mode backup?
Btw, in case it plays any part my tablet is 10.2''.
Any help would be greatly appreciated.
EDIT : Finally I figured it out! My correct stock rom is : sun4i_crane_bc1003.img
I found it through google and after flashing to it I managed to get my tablet at a working state. (ICS 4.0.4 ICS 4.0.3)
So, I'll now try to use more Jelly Bean roms without worrying about bricking it.
Oh, something I noticed that might help others too.. even though on the packaging it says Flytouch Superpad 8 Allwinner A10 this tablet model (BC1003) is actually the Flytouch Superpad 7 and that helped me find my correct rom. Keep that in mind from now on. I'll keep you updated if I succeed in booting to Jelly Bean.
Click to expand...
Click to collapse
okay im sitting at this point but i dont understand the flashing with livesuit
With the Windows utility "Phoenix Card" it is possible to burn the MaPan image mentioned above to a micro SD card. After inserting the micro SD card into the tablet and booting up the image will be flashed onto the tablet, indicated by a progress bar and a ticking sound.This works for our tablet, and should work for firmware for several Allwinner A10 and A20 tablets plus some other processor families (vimicro?).
where can i get Windows utility "Phoenix Card"
cant find 1 that works the inside says Yones toptech BC 1003 all winers A10
flusspferd said:
With the Windows utility "Phoenix Card" it is possible to burn the MaPan image mentioned above to a micro SD card. After inserting the micro SD card into the tablet and booting up the image will be flashed onto the tablet, indicated by a progress bar and a ticking sound.This works for our tablet, and should work for firmware for several Allwinner A10 and A20 tablets plus some other processor families (vimicro?).
Click to expand...
Click to collapse
hi ... i have a Yones toptech BC 1003 all winers A10 (superpad 8 / flaytouch) that im trying to fix...
after 3 days trying every possible firmware, and booting them from external sd card
all i could do was change de logo at boot start from (mapan to kosaco, to oem etc..)
than i had the idea of removing the internal sd card to look at it ...
and guess what it still runs the same with out no sd card in or out
so i thought ... the sd card was never read in the first place cause is damage or corrupted...
so on the 4th day im trying to format and partition the new internal sd card... hoping for the best.
so...
is the firmware installed in a built in memory ??
and how do i format the internall card TF card , and install all the software again
Problems with CWM v6.0.2.8
Sorry to interrupt people, but I'm quite new at this and I guess I made a mess....
I have a Flytouch Superpad VIII with A10 inside (BC1003), which is bricked.
Don't ask me how I got it this way, I guess **** happens.
Downloaded and installed CWM-based Recovery v6.0.2.8 only to find that on the log it cannot mount...
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache recovery/last log
My idea is that I probably used the wrong version of CWM, but if not the case, please tell me.
Anybody know a fix on this?
I've already intalled ADB drivers on my PC and at least I can communicate with my device using ADB.
Any help on unblocking the device and then flashing it would be greatly appreciated

[FIXED] Please Help! Lots of Flashing Errors

Just a quick heads up to everyone, I was able to fix my issue by SWITCHING TO A NEW SDCARD, I had been using a 64GB SDCARD and I switched to a 2GB SDCARD and I guess that my recovery or my phone couldn't handle such a large card.
It took me about two days to come to this conclusion but after lots of ODIN and reflashing just about everything possible I've decided this was the issue. Also I ran up my flash count a hell of a lot. I hope this helps someone out who may have issues like mine!
Hey all,
Today I decided I would try out a new ROM on my SGS3 so I decided to install the MIUIv5 ROM here: http://forum.xda-developers.com/showthread.php?t=2232800
Normally ROM installations go quite smooth for me so I opened up TWRP v2.5.0.0 and I did as I usually do by making a backup and wiping my system and then going to install my ROM. Instead today I got tons of errors saying:
Code:
Finding update package...
Opening update package...
E: Can't open /external_sd/MIUI5_d2vzw_3.4.12.420-signed (1).zip
(bad)
Installation aborted
So, I downloaded the ROM again, but this time from the mirror just in case I had a bad .zip or it didn't transfer to my SDCARD correctly, but then I started getting more and more errors.
Instead of getting a bad zip error I got the following:
Code:
E:Mount: Unable to find partition for path '/'
I guess this means it can't find my root partition?
Now all of a sudden I can't find my backups and I am just stuck without a ROM and I only have a recovery... quite inconvenient, also I can't flash any ROMS as I tried flashing some others but they didn't work at all no matter what I did and I am just running in circles... any help is GREAT APPRECIATED as I would love to have a functional phone by tomorrow.
I am fairly fluent with android and linux systems as well as computers in general so I should be able to provide any helpers with almost all information needed relative to my device, but sadly this whole issue has really stumped me.
Thanks so much!
ljbaumer
Click to expand...
Click to collapse
Have you tried flashing with Odin?
I know a lot of people swear by twrp but for me I always seemed to have issues. I had a similar issue you are having when I finally flashed cwm again. I was able to fix my issue by odin.
Sent from my GT-P5113 using xda premium
Thanks for both of your replies, I decided just to revert back to stock and I am in the process of re-obtaining root and such and then I am going to try to flash again just using recovery... by flashing by odin do you mean flashing a ROM or flashing back to stock?
FIXED! Read OP

Challenge for fixers: TWRP issue.

**edit:I feel like I posted this in the wrong place, but please feel free to help me work on this issue if you see this here...**
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/android/development/root-nextbook-ares-8-twrp-recovery-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.

Categories

Resources