yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] Phlox49:
E: can’t mount /sdcard

Hi. I'm running stock ICS 4.0.4 on an Azpen A701. I successfully installed CWM build 5 from post #2, but I keep receiving the following error when I try to install a ZIP file from the internal storage using CWM:

E: Can't mount /sdcard

Does anyone have any ideas? I should also note that I got the tablet for free because the USB port physically broke off, which makes Livesuit impossible to use. Thank you.
[Android Q&A, Help & Troubleshooting] BLuFeNiX:
What filesystem (fat32, ext4, etc.) do you use on your sdcard? If you aren't sure, backup all your sdcard data, and reformat the card as fat32.
[Android Q&A, Help & Troubleshooting] Phlox49:
How would one go about checking this? It's my internal storage I'm talking about, and I had no problems mounting it with my stock recovery. I also don't know how one would go about reformatting the internal storage, particularly when CWM recovery cannot mount it in the first place.

On an unrelated note, I've noticed errors when I load CWM about it not being able to read or write particular files to /cache. I'm not sure if that information helps.

I also can't mount my external SD card in CWM recovery. I've never been able to get my external SD card working with the tablet in my stock recovery or outside of recovery, so I'm not terribly concerned about it as a problem; it might just be the SD card or another hardware issue. However, I did notice that the filepath to the external SD card would be /extsd, which isn't an option in CWM recovery.

Thanks for your help.
[Android Q&A, Help & Troubleshooting] BLuFeNiX:
Ah, my mistake. I forgot the internal storage was called /sdcard. Are you positive that you have a A700 or A701 tablet? I built this CWM myself, and I've seen sdcard mounting errors on unsupported tablets. If you can still boot into regular android, I would download build5 again and do the install process one more time, just in case the file was corrupted.

Edit: You could also try a factory reset. Make sure to backup your data.
[Android Q&A, Help & Troubleshooting] Phlox49:
I'm 100% sure it's an Azpen A701. Might it have anything to do with the fact that I'm on ICS 4.0.4 and not JB?

Fortunately, I can still boot into regular Android. I'll try re-downloading and re-flashing CWM build 5. I've already tried a factory reset, but I'll probably try that again too since I have no data on the tablet. I should also note that the links in post #2 are dead; I downloaded CWM build 5 from other sources:

forum.sdx-developers.com/viewtopic.php?f=531&t=23709

fathertom.net/Azpen/
[Android Q&A, Help & Troubleshooting] BLuFeNiX:
Those sources are probably fine. There is a big link at the top of post #2 though. Here it is for your convenience: https://www.mediafire.com/folder/gm9wb67b05bs4/Azpen_A700
[Android Q&A, Help & Troubleshooting] Phlox49:
Ah, I didn't see that. Thanks.

I re-downloaded and re-installed CWM build 5 and still have the same error.

And then when I try to install ZIP from my internal storage using CWM recovery:

When I try wipe data/factory reset from CWM recovery:
[Android Q&A, Help & Troubleshooting] BLuFeNiX:
Strange. You can try going into CWM's mounts and storage menu and mounting/unmounting sdcard from there. Can you pull up an ADB terminal on your computer, while CWM is running?
[Android Q&A, Help & Troubleshooting] Phlox49:
I've tried mounting/unmounting from CWM's mounts and storage menu, but I still receive the same error.

I don't know how I would pull up an ADB terminal on my computer while CWM is running without a functional USB port. I've been using Terminal Emulator within Android.
[Android Q&A, Help & Troubleshooting] BLuFeNiX:
Darn, I forgot you said that. Without ADB to debug within CWM, I can't help much. An interesting test might be to install stock recovery (http://www.mediafire.com/download/siqpxb9qzdurss9/stock_recovery-Azpen_A700.zip) and see if you can access the sdcard that way. You won't be able to do much of anything, but you should be able to at least browse for files. If that doesn't work, you probably have a hardware problem. If it *does* work, I'm not sure what to suggest next.
[Android Q&A, Help & Troubleshooting] Phlox49:
First of all, thanks for taking the time to help me out.

I re-flashed the stock recovery (I had to use the IMG on your mediafire page instead since I can't flash ZIP files without being able to mount /sdcard/ from CWM recovery). While I'm no longer seeing the error from before, the stock recovery doesn't show anything in /sdcard/. I suppose it could be a hardware issue, but I wasn't convinced since I was able to browse /sdcard/ from my stock recovery before all of this.

I'm not sure if it's relevant, but the stock recovery I installed from your mediafire account is apparently from 4.2, while I'm on ICS 4.0.4. I browsed this thread and found a stock recovery IMG from ICS and installed that, and I receive a "E:Failed to mount /sdcard (Invalid argument)" error.

My goal of all this was to flash JB 4.2 stock without a USB port. Oh well. Thanks again.
[Android Q&A, Help & Troubleshooting] BLuFeNiX:
You're welcome. I'm sorry you couldn't get it working. If I come up with anything useful to try, I'll let you know.
[Android Q&A, Help & Troubleshooting] Phlox49:
In case anyone else has any ideas, here is what's displayed when I select "show log" in CWM recovery build 5:
[Android Q&A, Help & Troubleshooting] BLuFeNiX:
It's almost definitely the ROM you are running. If you can point me to the stock recovery for that ROM (perhaps you made a backup?), I can probably fix it.
[Android Q&A, Help & Troubleshooting] Phlox49:
Unfortunately, I did not make a backup of my stock recovery. What confuses me is that the stock recovery provided in post #2 also presumably has problems mounting /sdcard (it shows no contents in /sdcard).
[Android Q&A, Help & Troubleshooting] BLuFeNiX:
Yeah, I think it's because the partition mapping is different in your ROM. Allwinner devices use one big flash memory module for all the partitions, so you can resize them and move them around as you please.

Can you open a terminal in Android and type in the following commands, and give me the output?

mount

cat /proc/partitions

cat /etc/vold.fstab

Edit: if it's easier for you, you can dump the output to a txt file like this:

mount > mount.txt

cat /proc/partitions > part.txt

cat /etc/vold.fstab > fstab.txt

And then just send me those txt files.
[Android Q&A, Help & Troubleshooting] Phlox49:
Thank you for your continued assistance. Attached are the .txt files you requested.
[Android Q&A, Help & Troubleshooting] BLuFeNiX:
No problem. I've got a couple ideas. I might be able to get to it this weekend and send you some stuff to try. If you don't hear back from me in a few days, feel free to bump this thread to send me a reminder.
[Android Q&A, Help & Troubleshooting] Phlox49:
Thank you very much. I really appreciate it. I'm not sure if it matters with regard to troubleshooting, but those .txt files were generated with the stock recovery from post #2 installed, not CWM.
[Android Q&A, Help & Troubleshooting] Phlox49:
Bump.
[Android Q&A, Help & Troubleshooting] BLuFeNiX:
Alright, this is a build that just runs an extra mount command after booting into recovery. Let me know if you can read access /sdcard.

http://www.mediafire.com/download/84w9n12jisz8q9f/A700-CWM-TEST-001.img
[Android Q&A, Help & Troubleshooting] Phlox49:
Thank you, but I'm still receiving the same "E:Can't mount /sdcard/" error.
[Android Q&A, Help & Troubleshooting] BLuFeNiX:
I should have been more descriptive. You'll probably still get the error, but I'm hoping the command I added will mount /sdcard after the error is shown. Can you try to look at the sdcard through "flash zip from sdcard" or something?

If that doesn't work, I'll have to think about what to try next. Since you don't have microusb access (and can't flash using LiveSuit), if I send you a bad build, you'll be permabricked.

Just to make sure I understand: Does anything happen when you plug the tablet into a computer? Have you tried using LiveSuit? How do you charge the tablet?
[Android Q&A, Help & Troubleshooting] Phlox49:
With the new CWM recovery, the "E:Can't mount /sdcard/" error comes up when I try to flash ZIP from /sdcard or try to mount /sdcard, just like with the other CWM recoveries. Sorry, I should have been more specific.

I'm not sure how it works, but I was under the impression that if I were to hypothetically flash a bad recovery build, it would be okay as long as I still had access to the Android OS and could flash a new one using Terminal Emulator.

On the tablet, the micro USB port is physically gone, so there's nothing to plug into. Allegedly, a previous owner tried to plug the wrong thing into that port, attempted to force it, and broke the port off the board. I charge it using the DC port.
[Android Q&A, Help & Troubleshooting] BLuFeNiX:
That's what I thought before I got this tablet, but if you read back at the beginning of this thread, you'll see that dsulliii and I had quite a bit of trouble with bad CWM builds bricking the device. You have to recover with LiveSuit. So far the only thing I know of that causes that kind of brick is a bad NAND kernel driver (used to read the internal flash memory), but there may be other things that cause the same behavior, so we should be cautious of what you flash.

Ah, that's too bad. At least you have the A701 with the DC port. The A700 doesn't have a DC port.
[Android Q&A, Help & Troubleshooting] Phlox49:
Ah, I see. Very informative. Well, thanks again for your help. You are a gentleman and a scholar. If you have any more ideas or CWM builds for me to try, I'm all ears.
[Android Q&A, Help & Troubleshooting] treecheetahdolo:
[MENTION=5075032]BLuFeNiX[/MENTION]

I used your CWM build 5 on my Azpen A727 using

su

dd if=/sdcard/name_of_recovery.img of=/dev/block/nandg

sync

In terminal and it bricked the tablet, lol. Livesuit is detecting the tablet i believe but the link you have for the livesuit image is invalid on the 2nd post of this thread
[Android Q&A, Help & Troubleshooting] BLuFeNiX:
Sorry, I don't support the A727. You might want to check http://www.mediafire.com/azpensupport for a Livesuit image.
[Android Q&A, Help & Troubleshooting] treecheetahdolo:
When going to the link it says its disabled. I tried that immediately.
[Android Q&A, Help & Troubleshooting] dsulliii:
CWM recovery test 3

__________________________

OUTSTANDING!

Okay, so I made ONE presumption. I presumed that "reboot recovery" probably would reboot system like it seems to want to.

So my steps were to download this recover-TEST3.img file to the internal SDcard, terminal, "su", "dd ...etc", "sync", then exit terminal. Then start the system's "settings" and do a reboot recovery the way that we know works.

The joy is... YES! It rebooted into your CWM. It doesn't work perfect yet, but this is a major start, eh?

| CWM-based Recover v6.0.0.8

|

| - reboot system now

| - install zip from sdcard

| - install zip from sideload

| - wipe data/factory reset

| - wipe cache partition

| - backup and restore

| - mounts and storage

| - advanced

| _________________________________________

.

.

| CWM-based Recovery v6.0.2.8

| 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

Within the CWM, the volume buttons were reversed. Down moved it up and Up moved it down. The power button worked correctly though.

I pressed the power button on "reboot system now", and instead of getting stuck, it rebooted RIGHT back into the CWM recovery and still showed the same mount errors.

I tried mounting each partition separately in "mounts and storage" and got a failure on each.

I will hold-off on reflashing the ICS ROM for a while in case you want me to check anything else out.

__________

EXCITING! Congratulations!

I don't have a place where I can post an image, maybe it will let me post it as a link to Google Drive?

https://drive.google.com/file/d/0B28pBpgXMDbrZ3o0aUMwNVhJdTA/edit?usp=sharing
[Android Q&A, Help & Troubleshooting] BLuFeNiX:
Great! :D I think I know what changes I have to make. You can go ahead and restore with livesuit if you want. I don't think I need any more info from this install. I'll get back to you, hopefully tomorrow, with another build.

---------- Post added at 07:11 AM ---------- Previous post was at 06:48 AM ----------

Okay, I actually found a better tool that allowed me to repack a new build pretty quickly, this one might work:

CWM test 4

You know the drill. Looking forward to hearing back about this one! :D
[Android Q&A, Help & Troubleshooting] dsulliii:
Test 4 -- GREAT SUCCESS!

______________

Huh, I just realized that when I posted the Google Drive link to my photo, it let me post it. Cool, I guess I can post links now, so I won't bother snipping your links this time.

ANYWAY! Your excitement is WELL-DESERVED, Bravo, dude, bravo!

CWM loaded perfectly without any errors at all.

I went into mounts and saw that "cache" was indeed mounted, everything else was not.

I mounted each of the non-sd/usb partitions individually without error.

In elation, I went back and rebooted. To my surprise, the ICS gui desktop DID load and worked AWESOMELY.

The only shortcoming I see so far is that the volume up and volume down buttons are reversed in the CWM. It kind of causes vertigo. But insaneness is something that keeps us ticking from day to day I presume.

I BELIEVE that you've got this working perfectly enough that I'm going to try to use it to restore my JellyBean4.2 dumps. IT SHOULD WORK. I'll let you know if it does.

Do you think you can correct the volume keys.

I hope some day to be HALF as good as you (even though I do lay claim to being a worthwhile tester <grin>).

THANKS BLuFeNiX! What an awesome day this has been!

-- David

:cyclops: :cyclops: :cyclops: :cyclops:

---------- Post added at 11:48 PM ---------- Previous post was at 11:32 PM ----------

Well, needless to say that your end worked perfectly. I have sad news to report, though. The Uberizer restore ROM function, although it worked perfectly, was unable to totally restore the JellyBean4.2 ROM due to running out of room on this particular device. I sure hope I can overcome it. If not, for a cheap device that ICS ROM is quite adequate. Here's the Uberizer output at the point of the failure with everything preceding being snipped:

.......

vendor/pittpatt/models/recognition/

vendor/pittpatt/models/recognition/face.face.y0-y0-22-b-N/

vendor/pittpatt/models/recognition/face.face.y0-y0-22-b-N/full_model.bin

tar: write error: No space left on device

If this step succeeded then

To continue to Step 11

Press any key to continue . . .

.......

So after I pressed [Enter], it went ahead and tar'd the system which went fine.

But upon reboot, instead of our favorite little colorful Andy, I get a slightly backlit screen.

None of this has anything to do with your CWM which works GREAT! It's just an issue with this device and restoring using Uberizer ROM dumps/restores. But it was worth the try. Too bad I don't know a way to make the "data" tgz file smaller so that it won't fail. I'm sure there was something critical after "vendor/pittpatt/models/recognition/face.face.y0-y0-22-b-N/full_model.bin" that killed it from the get-go.

PS -- after this disaster, it also seems to have overwritten your CWM because I couldn't boot recovery using the vol+pwr buttons. Reflashed ICS, reloaded your CWM, no problem. Still works excellent.
[Android Q&A, Help & Troubleshooting] BLuFeNiX:
Great news! Thanks, David! This is really exciting :laugh:

I will look into swapping the button mapping for up/down. I think it's just a matter of editing a file.

As for restoring your tablet, I have a complete backup from mine when I first got it. You can probably boot into CWM, connect with ADB and dd the backups to your tablet. You seem to know what you're doing with the command line, so I'll leave you to it. Here are the files (you probably don't need nandf.img, but I have included it anyway):

nanda.img

nandb.img

nandc.img

nandd.img

nande.img

nandf.img

nandg.img

nandh.img

nandi.img

nandj.img

Good luck and thanks again for all your help. If these dumps don't get you back to stock, let me know and I'll see what I can do. Also, I'll let you know when I fix the button mappings in CWM.
[Android Q&A, Help & Troubleshooting] comstar:
Guys - Outstanding teamwork on the recovery!! This is what XDA is supposed to be, I'll be loading you guys new "BluDsu" A700 recovery today!
[Android Q&A, Help & Troubleshooting] dsulliii:
Back to Stock JellyBean4.2 "WITH" CWM Recovery!

_____

BLuFeNiX.... You are my new most favoritest hero.

I had a little bit of trouble at first because I was trying to push your NANDx.img files onto the internal SD using ADB. I got to NANDD and it choked to death... finally got a com error and the works. Realized that by the time it got to NANDJ (if it could even get NANDD done), it would probably be hopeless. Then it dawned on me to copy them all to a MicroSD and mount that one in CWM... and use THOSE files directly.

Yeah.. that worked! Funny thing is, though, it wouldn't start past the Azpen logo. I waited about a half hour. I don't know why.

So then I re-ran the Uberizer restore using my own boot.img, bootloader.img, data.tgz, and system.tgz (purposefully bypassed the recovery.img so that I can keep your CWM in place. I still errored out while it was tarring the system.tgz. Out-of-space error... very weird. Almost makes me wonder if somehow that ICS rom somehow changed the partition size... I don't know.

But despite that error, when it was all said and done, it did reboot without a problem. I don't see ANY issues at all with anything not working as a result of the out of space error. If I do have one, I can most likely just dd your NANDD back onto it. Oh, I did my own rom dumps before I started too, but I only grabbed NANDA, NANDB, NANDC and NANDG. I have NO idea why I didn't get the other six.

But I'm covered now. And even if I encounter a /system/* issue, I've got both yours and my NANDD to try.

You, sir, have given me back my stock JellyBean4.2 WITH your awesomely beautiful CWM. I thank you. I thank you LOTS!

And I'll still be thrilled to keep taking a user-view look at any other little thing you might want an extra set of eyes for... like those volume buttons.

Thanks again, and have a GREAT Holiday weekend!

-- David :highfive: :highfive: :highfive:

---------- Post added at 03:05 AM ---------- Previous post was at 02:56 AM ----------

_______________

Sorry to question you on this, but you got my interest piqued. I looked for BluDsu to see if I missed something somewhere, but I couldn't find it on Google or XDA. Is this something you're working on yourself? Is it something that somebody has available and I just couldn't find it because I'm fatigued from a wholly fulfilling "make it work" day? What is it? And by "loading it", do you mean that you're going to replace your own personal A700s stock recovery with it? Or are you posting work of your own for us to check out?

So many questions from a dead-tired babbling mind. But when I wake up sometime late this morning, I'm probably going to forget I asked. Good thing that XDA sends us e-mails.

Thanks, comstar! :cool:

-- David
[Android Q&A, Help & Troubleshooting] pscherry78:
Newb Confusion on commands

I'm using the recovery-TEST4.img file from your reddit posting.

Using the method above it boots to CWM-based Recovery v6.0.2.8

Choosing -install zip from sdcard

Then -apply /sdcard/update.zip

Get an error E:Can't mount /sdcard/update.zip

Is the DD command supposed to change the .IMG file to a .ZIP? Because it doesn't seem to.:confused:

I've even attempted a sideload using ADB w/o success.
[Android Q&A, Help & Troubleshooting] comstar:
No problem. I'm a little tired my self and should have been clearer. I modified my post.

I was talking about the same recovery posted by BLuFeNiX you guys were working on, I was just trying to be cute and re-named it after the first 3 letters of both your user names! I just thought you guys deserved it.

I'm going to download and flash the recovery today and give it a test. Thanks again for both of your hard work.
[Android Q&A, Help & Troubleshooting] BLuFeNiX:
Thanks! I like the name :D Even if I don't call it "BluDsu", I will certainly be giving dsulliii (David) credit whenever I can make a post in a proper A700 subforum. How do we go about getting one of those?

Ah, sorry for the confusion. The img file needs to be flashed directly. Just boot up android, plug in USB, and make an ADB connection. Then type these commands:

su
dd if=/sdcard/recovery-TEST4.img of=/dev/block/nandg
sync
reboot

You must be rooted for this to work. If you need more explanation, let me know and I will elaborate. Good luck!

Hmm. Worst case scenario is that you wait until Azpen releases a proper livesuit image for the A700. I spoke to them via email and they said it usually takes about 1-2 months before they have an image available.

In the mean time, there are two more solutions I see possible:

1) keep trying different different livesuit images until you get one with proper (or close) partition sizes

2) try to edit the partition sizes of the image you already have. I am looking into this option, and if I figure it out, I'll send you a modified image to try.
[Android Q&A, Help & Troubleshooting] dsulliii:
THANKS BLuFeNiX. You got more info from them than I did -- which was nothing. That two-months isn't bad at all. GREAT. So, if you want me to try yours if you do play around with it, then you know I'm more than happy to.
[Android Q&A, Help & Troubleshooting] BLuFeNiX:
Alright, I've never done this before so I have no idea if it works. Try this livesuit image:

A13 Livesuit image w/ A700 partition values

This is a modified version of the image you have already been using. If it works, you should have the same ICS environment, but the partition sizes should match the original ones (ie: the one's I posted on reddit). So, after you flash this, you can install CWM and try to dd my stock backups again. I hope this works!

Note: if this doesn't work, let's try to find another livesuit image you can flash. When I unpacked this one it had a few errors, so I don't know if it is a good candidate for editing.

---------- Post added at 08:33 PM ---------- Previous post was at 08:23 PM ----------

Also, if this DOES work, I might convert my stock images into a real livesuit image for the A700. :D
[Android Q&A, Help & Troubleshooting] dsulliii:
PERFECT Partitions!

So can you hear me outbursting with girly squeemish eeks over here? Well, I am, BLuFeNiX!

NOT-only did it LiveSuit PERFECTLY, but after it booted up (perfectly again, I must add), I pulled the /proc/partitions to reveal:

| major minor #blocks name

|

| 93 0 16384 nanda

| 93 8 16384 nandb

| 93 16 32768 nandc

| 93 24 573440 nandd

| 93 32 1228800 nande

| 93 40 16384 nandf

| 93 48 32768 nandg

| 93 56 327680 nandh

| 93 64 262144 nandi

| 93 72 1343488 nandj

Which IS indeed an exact match. That means that there will be enough room to do what I set out to do in the first place.

Well, now we have to take the dog to a vet appointment, so I'll have to let you know later regarding the conversion back to stock JellyBean2.2.

But I'm having trouble containing my glee. (No, not really, I'm not trying to contain it at all.)

THRILLED! And Thanks. WOW!

You've done what I set out to do in the first place. I'm going to take all my kitchen tools and compare the internals of the original to the one you mod'ed and see if you did what it is that I think that you did, but I was too afraid to try. You... are.... GOOD!