Database Develop

Droid X2 SD Storage Flip-Flop

I was wondering if a dev would be able to come up with a SD Storage flip flop for the Bionic? I had always used the modified app that navenedrob had posted here for my Droid X2,
http://forum.xda-developers.com/showthread.php?t=1229294
I'm hoping someone could come up with this for the Bionic.
Sent from my DROID BIONIC using XDA App

I'd also second this.
Sent from my DROID BIONIC using Tapatalk

Terri M said:
I was wondering if a dev would be able to come up with a SD Storage flip flop for the Bionic? I had always used the modified app that navenedrob had posted here for my Droid X2,
http://forum.xda-developers.com/showthread.php?t=1229294
I'm hoping someone could come up with this for the Bionic.
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
I would like to "third" this.

Fourth?
Sent from my DROID BIONIC using xda premium

sd flip flop
i would love to have the flip flop. it would fix a few things

Count me in!!
Sent from my DROID BIONIC using Tapatalk

+1 for me.
What a pain in the ass the two storage systems are.

I haven't tested this but it's just a theory since Linux is generally pretty flexible. Hypothetically you could just use the Terminal to unmount both the storage spaces, and then re-mount them but switch the addresses. See here:
/dev/block/vold/179:1 is the address of the external storage, named '/sdcard-ext'
/dev/block/vold/179:58 is the address of the internal storage, named '/sdcard'
so you could HYPOTHETICALLY type into the terminal:
su
unmount /sdcard-ext
unmount /sdcard
mount /dev/block/vold/179:58 /sdcard-ext
mount /dev/block/vold/179:1 /sdcard
and it should mount the two in each others' locations.
Again, I haven't tested this and my phone is on the charger right now so I'm not going to yet, but assuming that works it would probably just restore itself to normal when you reboot since I'm assuming there is a script that mounts the hardware locations to everything when Android loads.

K.AuthoR said:
I haven't tested this but it's just a theory since Linux is generally pretty flexible. Hypothetically you could just use the Terminal to unmount both the storage spaces, and then re-mount them but switch the addresses. See here:
/dev/block/vold/179:1 is the address of the external storage, named '/sdcard-ext'
/dev/block/vold/179:58 is the address of the internal storage, named '/sdcard'
so you could HYPOTHETICALLY type into the terminal:
su
unmount /sdcard-ext
unmount /sdcard
mount /dev/block/vold/179:58 /sdcard-ext
mount /dev/block/vold/179:1 /sdcard
and it should mount the two in each others' locations.
Again, I haven't tested this and my phone is on the charger right now so I'm not going to yet, but assuming that works it would probably just restore itself to normal when you reboot since I'm assuming there is a script that mounts the hardware locations to everything when Android loads.
Click to expand...
Click to collapse
The "script" is vold.fstab in /etc folder. I edited this and was able to change mount locations, but had random reboots when trying USB mount to computer.

sk8tingusmc said:
The "script" is vold.fstab in /etc folder. I edited this and was able to change mount locations, but had random reboots when trying USB mount to computer.
Click to expand...
Click to collapse
Probably because when it's trying to mount it sees them still as what they really are instead of the edited vold.fstab. There is probably somewhere else you would need to edit to get that working correctly also. Or you could try something such as Auto Mount in the Market. Maybe it'd work.

Anyone have luck downloading that file? Seems like its down or its just me?
Sent from my DROID BIONIC using Tapatalk

sk8tingusmc said:
The "script" is vold.fstab in /etc folder. I edited this and was able to change mount locations, but had random reboots when trying USB mount to computer.
Click to expand...
Click to collapse
I was wondering if it was an fstab file but I didn't really poke around. Good to know, thanks!

frostincredible said:
Probably because when it's trying to mount it sees them still as what they really are instead of the edited vold.fstab. There is probably somewhere else you would need to edit to get that working correctly also. Or you could try something such as Auto Mount in the Market. Maybe it'd work.
Click to expand...
Click to collapse
The problem is after the swap when you connect to the PC over USB it unmounts the internal memory, and dual-mounts the microSD card. If the phone accesses the card at the same time as the PC the phone will reboot. To fix this the init.rc file would need to be modified, but it reverts to the stock file on each reboot.

cvmaas said:
The problem is after the swap when you connect to the PC over USB it unmounts the internal memory, and dual-mounts the microSD card. If the phone accesses the card at the same time as the PC the phone will reboot. To fix this the init.rc file would need to be modified, but it reverts to the stock file on each reboot.
Click to expand...
Click to collapse
Good to know. I was messing around with it. Ill check into this. Maybe I can magically make something happen
Sent from my DROID BIONIC using Tapatalk

Let us know if you have any luck, even if it's just a temp solution, because I would most certainly like to quit using this stupid internal memory if possible.

cvmaas said:
The problem is after the swap when you connect to the PC over USB it unmounts the internal memory, and dual-mounts the microSD card. If the phone accesses the card at the same time as the PC the phone will reboot. To fix this the init.rc file would need to be modified, but it reverts to the stock file on each reboot.
Click to expand...
Click to collapse
Oh okay. Does the bootloader need to be unlocked to edit that? I'm coming from the Incredible (hence my name) and have just become used to the Incredible's unlocked bootloader.

Anyone have any luck downloading any file in the browser?
Sent from my DROID BIONIC using Tapatalk

CWM zip originally by navendrob
Does not have full functionality yet! Read below!
Here is a CWM zip that I have modified that will flip flop SD storage locations. This is just to speed the process when someone figures out how to mount them to computer.
Important Facts
make your own back up before flashing
mount storage in CWM
Flash
This will mount the actual SD card as SDCARD and internal as SDCARD-EXT, but will not mount via USB to a computer. This will reboot phone and has already been discussed in thread.

sk8tingusmc said:
Does not have full functionality yet! Read below!
Here is a CWM zip that I have modified that will flip flop SD storage locations. This is just to speed the process when someone figures out how to mount them to computer.
Important Facts
make your own back up before flashing
mount storage in CWM
Flash
This will mount the actual SD card as SDCARD and internal as SDCARD-EXT, but will not mount via USB to a computer. This will reboot phone and has already been discussed in thread.
Click to expand...
Click to collapse
Thanks to everyone who is working on this!! Sk8, I will give this a try and will let you know! Thank you!
Sent from my DROID BIONIC using XDA App

dadsterflip said:
Anyone have any luck downloading any file in the browser?
Sent from my DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
The stock browser is actually a POS. Try using the Dolphin hd browser.
Sent from my DROID BIONIC using XDA App

[Q] mmcblk0p2 corrupt?

Hi everyone and thank you for being so active on this forum.
I want to apologize in advance as this post may be (yet) another "bricked" Nook kind of post. Although my situation seems interesting for whomever is looking for this type of intellectual challenge.
I think I read as much as I could but wasn't able to find anything yet that would be similar to what I'm experiencing.
First a bit of history: bought a Nook color (refurb), like new, running 1.2 stock. I was able to start it, set it up and register to B&N, no problem.
Created a CM7 (7.0 to start with) on SD, work great.
Created a 7.1 on SD. I could get pretty much anything running except CWM and WIFI. Now, trying to fix wifi, and I guess also CWM, I obviously messed up and the Nook would not boot anymore on SD.
Tried to boot on emmc … not working anymore. So, I messed up even more than I thought.
Tried to restore to stock 1.2 on emmc (using a formatted SD 1g w/ CWM 3.2.1) and at reboot, it fails with a "ipod-like" icon "Failed to install" message.
Tried to restore to 1.0.1 stock. The Nook will boot but when I go through the setup/register process, it fails after the wifi connection settings with an error telling me to call B&N support. When I look at Device Info at this point, it says "Serial number / Model / MAC" are missing … hmmm.
Now, I tried to recreate a CM7 on SD but the process fails at the end with a message:
init: Mount returned errno=19
FAT: invalid media value (0x00)
VFS: Can't find a valid FAT filesystem on dev mmcblk0p2.
init: Mount returned errno=22
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
and reboot over and over.
Where I stand right now. I was able to install nookie froyo on emmc. Works (kinda). And I'm trying all I can to fix my issue which I suspect to be with /dev/block/mmcblk0p2 as I get the message in dmesg and the stock 1.0.1 would tell me that serial / mac are missing.
I have adb running. With nookie froyo running, I can get into the Nook and mess around. I'd like to try some e2fsck but can't find the tool for froyo.
Before that and before I try again with CM7, I'd like to have (smart) people ideas about this problem.
Any suggestion is welcome!
Thanks for reading.

Sorry to bother. Any idea anyone? It really looks like a problem with /dev/block/mmcblk0p2. The 8 failed restore process won't work as it's obviously not able to mount mmcblk0p2 on to /rom.
I tried manually doing a bunch of repairs but nothing will work. The mount gives me a:
mount -o dev /dev/block/mmcblk0p2 /rom
mount: mounting /dev/block/mmcblk0p2 on /rom failed: Invalid argument
I know that this partition contains device specifics but would anyone have something to share so I could dd into it to see if this is my problem?
Thanks anyway.

solution
All right,
I got it! For the community if anybody runs into the same problem, here is the story.
So, /dev/block/mmcblk0p2 was definitely corrupt. I had to use parted to fix it.
Using parted, this particular partition would not show as "fat32" as it should. I created a FS on this partition (using the mkfs sub-command). It erases everything in this partition but at least it fixes the corruption. After that, I was able to mount it over /rom. It as empty of course.
Restoring a 1.0.1 stock then trigerred the factory reset that I wasn't able to trigger before (the Failed install message) and now I'm able to reboot and go through the setup/registration process again. wow, not fun for a first pb.
Next step, update to latest stock and then will redo my CM7 testing on sd.
Thanks everyone for listening ;-)

mmcblk0p2 error
Thanks, you saved me a lot of time.

CWM mounting options question

Hi. First of all thanks guys for the CWM and instructions. Everything went smooth, and I'm already after my first backup, but I would appriciate a small clarification for me.
When I do "mount", does it mean that I tick the things I want to find it's way in this backup? If so, I have following question:
What does
1. eccm
2. sdcard
3. USB Storage
mean?
Many places call each differently, and it's worse that it changes when we talk in CWM terminology, so I would appriciate some clarification.
Also, I don't have "ext-sd" option in my mounting options, which some tutorials give, and I wanted to ask about that as well.
As for technical details. I have rooted phone, with Open Rom 2.3.6. The things I have in my backup directory I made are:
boot.img
recovery.img
system.ext4.tar
data.ext4.tar
.android_secure.vfat.tar
cache.ext4.tar
nandroid.md5
I chose everything but USB Storage, going with my gut. Was I correct?
cheers
Lucas

Man I thing this link is useful:http://www.addictivetips.com/mobile...-and-how-to-use-it-on-android-complete-guide/

umarian said:
Man I thing this link is useful:http://www.addictivetips.com/mobile...-and-how-to-use-it-on-android-complete-guide/
Click to expand...
Click to collapse
Thanks for the link and good reading. I learned much from it.
However, in the guide there, the terms used are still sdcard as the INTERNAL card. So while I know now what USB Storage in mounting option means, I still don't know, and there is no explanation in the guide in that linke, what these 2 reffer to:
What does
1. eccm
2. sdcard
cheers

emmc is your internal sdcard. Normally, it is mounted to /sdcard.
sdcard is your external micro sd card. In Android, it is mounted to /sdcard/external_sd.

wintel_mac said:
emmc is your internal sdcard. Normally, it is mounted to /sdcard.
sdcard is your external micro sd card. In Android, it is mounted to /sdcard/external_sd.
Click to expand...
Click to collapse
Awsome, thanks a lot for clarification.
One follow up question. If I mount the sdcard, so my external card, it won't backup the content of ext sd card as well into my backup? What I mean is, I don't want to break something, by trying to make a backup that includes over 20GB of stuff on my external memory card.
Also, I looked over polish forum of android, and someone told me, that there is no need to mount/unmount stuff as the backup that is made, is made all the time the same, no matter the mounting options. Strange a bit. Is it true what he said?
cheers
Lucas

Don't know exactly how it is implemented for your device (9000, I'm on 9001) but external SD cards are normally never backed up (which would not make any sense at all btw, since you might even backup the backup you're doing at that moment^^).
When you take a look at the structure of an CWM backup folder, you realize that also your internal sd card is not backed up (aside from .asec).
And yes, it is not ncecessary to mount anything for backup or restore purposes. CWM does what is necessary to perform the desired actions.

wintel_mac said:
Don't know exactly how it is implemented for your device (9000, I'm on 9001) but external SD cards are normally never backed up (which would not make any sense at all btw, since you might even backup the backup you're doing at that moment^^).
Click to expand...
Click to collapse
I'm on i9001 as well
When you take a look at the structure of an CWM backup folder, you realize that also your internal sd card is not backed up (aside from .asec).
And yes, it is not ncecessary to mount anything for backup or restore purposes. CWM does what is necessary to perform the desired actions.
Click to expand...
Click to collapse
I see...
But if that is the case, what's the point of mounting the eccm as well as sdcard if they are not backed up to begin with?
cheers

You can connect over adb to the phone and perform varous actions. And it makes no sense to mount every partition you may need with commands such as
"mount -o rw /dev/block/mmcblk0p15 /system" as you would have to remember where each file system resides.
So you can do it with few keypresses on the phone.
Moreover, there are some custom update-zips that do not do the mounting for you, so it would be necessary to apply them, too.

wintel_mac said:
You can connect over adb to the phone and perform varous actions. And it makes no sense to mount every partition you may need with commands such as
"mount -o rw /dev/block/mmcblk0p15 /system" as you would have to remember where each file system resides.
So you can do it with few keypresses on the phone.
Moreover, there are some custom update-zips that do not do the mounting for you, so it would be necessary to apply them, too.
Click to expand...
Click to collapse
I think I know what you mean. You are saying that there are other actions that require mounting, not backup in this case, and it's much easier to do it automaticly through cwm, rather than doing it manualy with linux lingo.
Thanks for the explanations.
Just one clarrification at the end. When I do backup with CWM, do I need to do any mounting, or it's done automaticly now and it mounts everything it needs to, to do backup?
cheers
Lucas

wintel_mac said:
And yes, it is not ncecessary to mount anything for backup or restore purposes. CWM does what is necessary to perform the desired actions.
Click to expand...
Click to collapse
As I wrote before

wintel_mac said:
As I wrote before
Click to expand...
Click to collapse
Awsome. Thank you wintel_mac so much, for very detailed answers.
cheers
The topic can be closed.

Recover a dead emmc?

Hello guys, I am running Android off SdCard because my HD+ has a dead emmc, I recently discovered that I can read and write to it using root explorer, does that mean that there's a chance that I could somehow recover it?

mmk92 said:
Hello guys, I am running Android off SdCard because my HD+ has a dead emmc, I recently discovered that I can read and write to it using root explorer, does that mean that there's a chance that I could somehow recover it?
Click to expand...
Click to collapse
how can you access your emmc? the (emmc-less) rom that verygreen made used our sdcards as the emmc I think that what you are seeing is a portion of your sdcard not your emmc

Hello,
I've seen your other thread here at XDA, and I'm not trying to be offensive, but I think you maybe confused with EMMC, Pure SD install and the term "dead EMMC". Apologies I didn't reply to your other thread earlier; I did/do not have much time. Please note, I do not indent to be offensive at all, just trying to put facts together; to hopefully ease you to achieve your solution.
For starters, I don't think your EMMC is "dead"; else you would have a difficult time booting your tablet up (I'd be surprised if a Nook turned on with a dead EMMC), even if you're purely installed on an SD card. Personally what I think is going on, you stated in the other thread your friend gave you this Nook. Your friend thought he (assuming he's male) could install CyanogenMod on his Nook, but unfortunately he couldn't. Effectively, he thought he had "bricked" or damaged his Nook; at this point it was not working the way he intended, and couldn't boot into CyanogenMod. He turned to you for help, or you stepped in, as your more "technical" with this stuff. Of course, I could be wrong. You knew you wouldn't be able to fix this, but you could use an alternative way to boot CyanogenMod; using only a SD card.
Not bad idea, but I'm quite confident that your EMMC is not "dead" and that you can install CyanogenMod on your internal storage without a SD card being required for boot. Apologies if my assumptions contain mistakes, I only completed reading the thread after posting the above.
I was going to post some suggestions and write up some guides, but before I do, please may I ask a question? You said you're using Root Explorer? Where is this? On your stock ROM on internal/EMMC, on a CyanogenMod build on EMMC, or on Pure SD? If you're booting using purely a SD card, and have Root Explorer running, you can edit files because it's editing files on your SD card, not your EMMC (although it may say internal, a pure SD install "emulates" the internal storage).
Again, please reply with the answer(s). I'll do my best to assist. Also, just a quick note; it's not necessary to make two threads. You could have still used your earlier thread.

HiddenG said:
Hello,
I've seen your other thread here at XDA, and I'm not trying to be offensive, but I think you maybe confused with EMMC, Pure SD install and the term "dead EMMC". Apologies I didn't reply to your other thread earlier; I did/do not have much time. Please note, I do not indent to be offensive at all, just trying to put facts together; to hopefully ease you to achieve your solution.
For starters, I don't think your EMMC is "dead"; else you would have a difficult time booting your tablet up (I'd be surprised if a Nook turned on with a dead EMMC), even if you're purely installed on an SD card. Personally what I think is going on, you stated in the other thread your friend gave you this Nook. Your friend thought he (assuming he's male) could install CyanogenMod on his Nook, but unfortunately he couldn't. Effectively, he thought he had "bricked" or damaged his Nook; at this point it was not working the way he intended, and couldn't boot into CyanogenMod. He turned to you for help, or you stepped in, as your more "technical" with this stuff. Of course, I could be wrong. You knew you wouldn't be able to fix this, but you could use an alternative way to boot CyanogenMod; using only a SD card.
Not bad idea, but I'm quite confident that your EMMC is not "dead" and that you can install CyanogenMod on your internal storage without a SD card being required for boot. Apologies if my assumptions contain mistakes, I only completed reading the thread after posting the above.
I was going to post some suggestions and write up some guides, but before I do, please may I ask a question? You said you're using Root Explorer? Where is this? On your stock ROM on internal/EMMC, on a CyanogenMod build on EMMC, or on Pure SD? If you're booting using purely a SD card, and have Root Explorer running, you can edit files because it's editing files on your SD card, not your EMMC (although it may say internal, a pure SD install "emulates" the internal storage).
Again, please reply with the answer(s). I'll do my best to assist. Also, just a quick note; it's not necessary to make two threads. You could have still used your earlier thread.
Click to expand...
Click to collapse
I think you are quite wrong.The lagfix app bug actually does kill the emmc what hes using is an emmc-less rom that verygreen created for all the users who were affected by the emmc bug. This rom doesnot use the emmc at all it treats the sdcard as the emmc

Ahh, no problem. Thank you Talha, that cleared a few things for me. Haha, I've been missing from the latest developments on the Nook's.
Still, I hold my statement in this case, as the OP stated he can boot into EMMC recovery (source). So the EMMC is not dead.

Thank you guys for the replies!
I am accessing the emmcs through Root explorer on a nonemmc ROM, so I could be accessing the SD card itself, makes perfect sense.
But if i boot up my tablet without an sd card, it goes to the internal EMMC recovery, in that recovery I can access the SD card, but can't mount the emmc itself. (it says E: error can't mount /emmc/
This is weird because I've always though the recovery and ROM resie on the emmc.
Please pardon my ignorance guys.

mmk92 said:
Thank you guys for the replies!
I am accessing the emmcs through Root explorer on a nonemmc ROM, so I could be accessing the SD card itself, makes perfect sense.
But if i boot up my tablet without an sd card, it goes to the internal EMMC recovery, in that recovery I can access the SD card, but can't mount the emmc itself. (it says E: error can't mount /emmc/
This is weird because I've always though the recovery and ROM resie on the emmc.
Please pardon my ignorance guys.
Click to expand...
Click to collapse
No problem, haha. Is the recovery on your EMMC ClockWorkMod or TeamWin Recovery? If either of these, and you can boot into them; then may be I have a solution for you. Please let me know.
Also, have you tried flashing a ROM using your EMMC recovery? I'm pretty sure you have, and I'm assuming an error was presented? Let me know.

Without an sd card inside the Nook, it boots straight to CWM recovery. I tried flashing " cm-10.2-20131207-NIGHTLY-ovation.zip" first it gave me "E:Can't mount /cache/recovery/last_install E: failed to open last_install: no such directory or file" then it started running then it gave me a (status 0) error and then eventually aborting. I tried flashing the TWR, reports the same "last_install"errors like the ROM flash, then it finished really fast(around a second) reports a "Done..! Install from sdcard complete." but changes absolutely nothing (if i restart it goes back to CWM).

mmk92 said:
Without an sd card inside the Nook, it boots straight to CWM recovery. I tried flashing " cm-10.2-20131207-NIGHTLY-ovation.zip" first it gave me "E:Can't mount /cache/recovery/last_install E: failed to open last_install: no such directory or file" then it started running then it gave me a (status 0) error and then eventually aborting. I tried flashing the TWR, reports the same "last_install"errors like the ROM flash, then it finished really fast(around a second) reports a "Done..! Install from sdcard complete." but changes absolutely nothing (if i restart it goes back to CWM).
Click to expand...
Click to collapse
I think that your emmc is working but your partitions are broken

So there's hope? What do you guys suggest I do

mmk92 said:
So there's hope? What do you guys suggest I do
Click to expand...
Click to collapse
It is possible that your emmc is readable, but not writeable. I had an SD where that happened. It would act like it was writing and the PC would say successful, but when I ejected the SD and reinserted, it has not changed. Nothing I could do would revive the SD. I had to throw it away.
I suggest you use your noemmc ROM to explore emmc to see if you can change anything and have it stick after a reboot.
Sent from my BN NookHD+ using XDA Premium HD app

Bits in SD cards have a certain lifespan, I believe between 10k-100k read/writes until they become unwritable. Some generic/defective cards have much less. So in your case it could've been an old/cheap brand SD card that happened to die. Although the eMMC shares these drawbacks, it has a much longer lifespan, and I highly doubt this the issue for the emmc.

I attached to this post a dump of logs that I have collected from my Nook. I see a bunch of "unknown partition table" in there, so could that be the problem? Does that mean that a partition fix should solve my problem?(I've read about lots of devices revived from broken partition tables).
What if this is the issue for most people and not a dead eMMC chip? If this theory proves to be true maybe many nooks will be brought back from the dead.
It's times like these that I wish that I was more experienced with such low level stuff I barely know the terminology so again, please ignore my ignorance.

Sorry for the mult-posts, why did you leave meeh out to dry I am willing to try anything on my Nook if it has a chance to get back to life.

mmk92 said:
Sorry for the mult-posts, why did you leave meeh out to dry I am willing to try anything on my Nook if it has a chance to get back to life.
Click to expand...
Click to collapse
Is yours like this? http://forum.xda-developers.com/showthread.php?p=44842492&highlight=partition#post44842492
Sent from HD+ MAG2GA CM 10.2 from SD

I get no output for the command dmesg|grep mmc1 nor dmesg|grep mmcblk1
I do however get response from dmesg|mmcblk0
~ # dmesg|grep mmcblk1
dmesg|grep mmcblk1
~ # dmesg|grep mmcblk0
dmesg|grep mmcblk0
<6>[ 3.039337] mmcblk0: mmc0:0001 MAG2GA 14.5 GiB
<6>[ 3.039611] mmcblk0boot0: mmc0:0001 MAG2GA partition 1 2.00 MiB
<6>[ 3.039825] mmcblk0boot1: mmc0:0001 MAG2GA partition 2 2.00 MiB
<6>[ 3.040649] mmcblk0: unknown partition table
<6>[ 3.041839] mmcblk0boot1: unknown partition table
<6>[ 3.042846] mmcblk0boot0: unknown partition table
~ #
Click to expand...
Click to collapse

mmk92 said:
I get no output for the command dmesg|grep mmc1 nor dmesg|grep mmcblk1
I do however get response from dmesg|mmcblk0
Click to expand...
Click to collapse
The 1 applies when booted from the noemmc sdcard.
Here's another possibly helpful post http://forum.xda-developers.com/showthread.php?p=44887350
Sent from HD+ MAG2GA CM 10.2 from SD

~ # mke2fs -t ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/cache
mke2fs -t ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/cache
mke2fs 1.41.14 (22-Dec-2010)
Could not stat /dev/block/platform/omap/omap_hsmmc.1/by-name/cache --- No such f
ile or directory
The device apparently does not exist; did you specify it correctly?
~ # mount .cache
mount .cache
mount: can't find .cache in /etc/fstab
~ # mount /cache
mount /cache
mount: mounting /dev/block/platform/omap/omap_hsmmc.1/by-name/cache on /cache fa
iled: No such file or directory
~ # mount /cache
mount /cache
mount: mounting /dev/block/platform/omap/omap_hsmmc.1/by-name/cache on /cache fa
iled: No such file or directory
~ # mke2fs -t ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/cache
mke2fs -t ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/cache
mke2fs 1.41.14 (22-Dec-2010)
Could not stat /dev/block/platform/omap/omap_hsmmc.1/by-name/cache --- No such f
ile or directory
The device apparently does not exist; did you specify it correctly?
~ # mke2fs -t ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/cache
mke2fs -t ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/cache
mke2fs 1.41.14 (22-Dec-2010)
Could not stat /dev/block/platform/omap/omap_hsmmc.1/by-name/cache --- No such f
ile or directory
The device apparently does not exist; did you specify it correctly?
~ #
Click to expand...
Click to collapse
I get the "Could not stat /dev/block/platform/omap/omap_hsmmc.1/by-name/cache --- No such f
ile or directory" on every run.
Also tried flashing Stock from all recoveries, still no change

mmk92 said:
I get the "Could not stat /dev/block/platform/omap/omap_hsmmc.1/by-name/cache --- No such f
ile or directory" on every run.
Also tried flashing Stock from all recoveries, still no change
Click to expand...
Click to collapse
Here is a link for recreating the partition table http://forum.xda-developers.com/showthread.php?p=44620340&highlight=table#post44620340
Sent from HD+ MAG2GA CM 10.2 from SD

I got this interesting message when I executed print in parted.
Warning: /dev/block/mmcblk0 contains GPT signatures, indicating that it has a
GPT table. However, it does not have a valid fake msdos partition table, as it
should. Perhaps it was corrupted -- possibly by a program that doesn't
understand GPT partition tables. Or perhaps you deleted the GPT table, and are
now using an msdos partition table. Is this a GPT partition table?
Yes/No? yes
yes
yes
Model: MMC MAG2GA (sd/mmc)
Disk /dev/block/mmcblk0: 30535680s
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 256s 511s 256s xloader
2 512s 1023s 512s bootloader
3 1024s 31743s 30720s recovery
4 32768s 65535s 32768s boot
5 65536s 163839s 98304s fat32 rom
6 163840s 262143s 98304s fat32 bootdata
7 262144s 1179647s 917504s ext4 factory
8 1179648s 2555903s 1376256s ext4 system
9 2555904s 3506175s 950272s ext4 cache
10 3506176s 30507007s 27000832s ext4 userdata
(parted)
Click to expand...
Click to collapse
Also the partitions seem intact, what do you suggest I do?

[Q] dead mmc -- ideas?

I've been having a grand old time tinkering with my new TF701t. I unlocked the bootloader, tried a few ROMs, went back to stock, and I've been busily playing with it. Earlier this evening, it spontaneously shut down. I booted it back up and it shut down again after 5 minutes. I went into recovery and flashed the xposed disabler zip just in case xposed was to blame, but it shut down from recovery. Now it won't boot at all.
I can connect via ADB in recovery, and when I run dmesg, I see all sorts of nasty mmc0-related timeouts and errors. I can't even mount /system anymore. It's pretty clearly either an issue with the internal memory card or with the bus.
Does anyone have any idea how I can fix this or get it fixed? Of course, with an unlocked bootloader, I'm sure ASUS is going to give me all manner of grief and probably refuse to repair/replace what is clearly a hardware failure. Does anyone know if there's any way at all of replacing this kind of mmc card, or is it just part of the SoC? How screwed am I?
EDIT: Not screwed at all! See my post on page 2 for a fairly simple procedure to boot and run the tf701t (and quite probably many other devices) completely off of the SD card.

lexelby said:
I've been having a grand old time tinkering with my new TF701t. I unlocked the bootloader, tried a few ROMs, went back to stock, and I've been busily playing with it. Earlier this evening, it spontaneously shut down. I booted it back up and it shut down again after 5 minutes. I went into recovery and flashed the xposed disabler zip just in case xposed was to blame, but it shut down from recovery. Now it won't boot at all.
I can connect via ADB in recovery, and when I run dmesg, I see all sorts of nasty mmc0-related timeouts and errors. I can't even mount /system anymore. It's pretty clearly either an issue with the internal memory card or with the bus.
Does anyone have any idea how I can fix this or get it fixed? Of course, with an unlocked bootloader, I'm sure ASUS is going to give me all manner of grief and probably refuse to repair/replace what is clearly a hardware failure. Does anyone know if there's any way at all of replacing this kind of mmc card, or is it just part of the SoC? How screwed am I?
Click to expand...
Click to collapse
See if you can mount /cache or /data. If you cannot then you have royally messed up your tablet. If you have replaced the recovery to something other than the original asus recovery then your best bet is to buy a logic board from ebay and replace it manually yourself.
I took mine to asus repair center and they said they will charge 200$ and 3 days to replace the logic board. I managed to buy the part for 70$ and do it myself. Just a side note, I bought and item that was AS-IS, so I am glad mine worked.

devbro said:
See if you can mount /cache or /data. If you cannot then you have royally messed up your tablet. If you have replaced the recovery to something other than the original asus recovery then your best bet is to buy a logic board from ebay and replace it manually yourself.
I took mine to asus repair center and they said they will charge 200$ and 3 days to replace the logic board. I managed to buy the part for 70$ and do it myself. Just a side note, I bought and item that was AS-IS, so I am glad mine worked.
Click to expand...
Click to collapse
Thanks for the tips!
It's quite weird. I booted it into recovery, and via adb I was able to mount /data fine and poke around. I unmounted, then mounted /system, and that worked fine too. Unmounted, rebooted, no dice; shutdown during reboot. Now I've booted back into recovery, and it locked up even trying to get into recovery, and I can't mount /data or /system (all result in long pauses and kernel errors).
You say I messed up my tablet... what do you think caused this? And yes, I've got CWM on here, although I could just fastboot the original recovery on if that would help...
Is there any way to boot this thing off of the external SD?
What was wrong with yours that required replacing the logic board?

lexelby said:
Thanks for the tips!
It's quite weird. I booted it into recovery, and via adb I was able to mount /data fine and poke around. I unmounted, then mounted /system, and that worked fine too. Unmounted, rebooted, no dice; shutdown during reboot. Now I've booted back into recovery, and it locked up even trying to get into recovery, and I can't mount /data or /system (all result in long pauses and kernel errors).
You say I messed up my tablet... what do you think caused this? And yes, I've got CWM on here, although I could just fastboot the original recovery on if that would help...
Is there any way to boot this thing off of the external SD?
What was wrong with yours that required replacing the logic board?
Click to expand...
Click to collapse
It sounds like your boot is corrupted. There may be a way for ASUS to recover it without replacing the board.
My problem was that I messed up my boot and I could no longer flash anything or even modify files on the filesystems.

devbro said:
It sounds like your boot is corrupted. There may be a way for ASUS to recover it without replacing the board.
My problem was that I messed up my boot and I could no longer flash anything or even modify files on the filesystems.
Click to expand...
Click to collapse
Powering off completely seems to restore the device's ability to mount /system. I think touching a certain place on the emmc puts the controller in a bad state. I'm going to see if I can narrow down the bad blocks and partition around them or similar.
Barring that, where did you find a logic board for so cheap?

lexelby said:
Powering off completely seems to restore the device's ability to mount /system. I think touching a certain place on the emmc puts the controller in a bad state. I'm going to see if I can narrow down the bad blocks and partition around them or similar.
Barring that, where did you find a logic board for so cheap?
Click to expand...
Click to collapse
If you can access it in adb, the first thing I would do is adb pull my data off the tablet.
Then you could run fsck on your partitions in an adb shell.
Maybe just a simple format of/system and /data would clear corruption already....
I don't know the correct fsck command for this tablet top of my head, but you have to unmount the partition you want to run it on and then something similar to this (this is for the /data partition of the TF700):
Code:
e2fsck -fvyD /dev/block/mmcblk0p8
You seem to know your way around, I'm sure you can find it.
Good luck!

berndblb said:
If you can access it in adb, the first thing I would is adb pull my data off the tablet.
Then you could run fsck on your partitions in an adb shell.
Maybe just a simple format of/system and /data would clear corruption already....
I don't know the correct fsck command for this tablet top of my head, but you have to unmount the partition you want to run it on and then
Code:
fsck /dev/target_partition_name
You seem to know your way around, I'm sure you can find it.
Good luck!
Click to expand...
Click to collapse
Nah, it's not simple fs corruption -- first thing I checked, but thanks for the suggestion Been poking at it for a few hours, and it seems like the actual mmc bus/chip is screwed, not just a bad block. I think replacing the logic board is the way to go. Anyone want to let a tf701t with a dead screen go for cheap?
And yeah, I know my way around a bit, but really only enough to sound like I know what I'm doing I recognized the problem because I lost my sgh-i777 to a very similar issue, a failing internal sd. Seems like the Achilles' heel of android devices.

lexelby said:
Seems like the Achilles' heel of android devices.
Click to expand...
Click to collapse
I've owned close to a dozen Android devices. The SD still has to fail on me...
Maybe it's not the hardware, maybe it's - you [emoji33][emoji12]
Anyway, good luck with this. Oh, and devbro found the logic board on ebay..

berndblb said:
If you can access it in adb, the first thing I would do is adb pull my data off the tablet.
Then you could run fsck on your partitions in an adb shell.
Maybe just a simple format of/system and /data would clear corruption already....
I don't know the correct fsck command for this tablet top of my head, but you have to unmount the partition you want to run it on and then something similar to this (this is for the /data partition of the TF700):
Code:
e2fsck -fvyD /dev/block/mmcblk0p8
You seem to know your way around, I'm sure you can find it.
Good luck!
Click to expand...
Click to collapse
lexelby said:
Nah, it's not simple fs corruption -- first thing I checked, but thanks for the suggestion Been poking at it for a few hours, and it seems like the actual mmc bus/chip is screwed, not just a bad block. I think replacing the logic board is the way to go. Anyone want to let a tf701t with a dead screen go for cheap?
And yeah, I know my way around a bit, but really only enough to sound like I know what I'm doing I recognized the problem because I lost my sgh-i777 to a very similar issue, a failing internal sd. Seems like the Achilles' heel of android devices.
Click to expand...
Click to collapse
berndblb said:
I've owned close to a dozen Android devices. The SD still has to fail on me...
Maybe it's not the hardware, maybe it's - you [emoji33][emoji12]
Anyway, good luck with this. Oh, and devbro found the logic board on ebay..
Click to expand...
Click to collapse
Be careful mmcblk0p8 is /data on the TF700, on the TF701 it is mmcblk0p14
Code:
name device mountpoint fs description
/dev/block/platform/sdhci-tegra.3/ADF /dev/block/mmcblk0p7 /ADF ext4 ?
/dev/block/platform/sdhci-tegra.3/APD /dev/block/mmcblk0p6 /APD ext4 ASUS Product Demo
/dev/block/platform/sdhci-tegra.3/APP /dev/block/mmcblk0p4 /system ext4 Android OS
/dev/block/platform/sdhci-tegra.3/CAC /dev/block/mmcblk0p5 /cache ext4 recovery logs
/dev/block/platform/sdhci-tegra.3/CRA /dev/block/mmcblk0p11 ?
/dev/block/platform/sdhci-tegra.3/DTB /dev/block/mmcblk0p2 ?
/dev/block/platform/sdhci-tegra.3/EKS /dev/block/mmcblk0p13 NVEKSP
/dev/block/platform/sdhci-tegra.3/LNX /dev/block/mmcblk0p3 Linux kernel (8388608 b)
/dev/block/platform/sdhci-tegra.3/MDA /dev/block/mmcblk0p12 ?
/dev/block/platform/sdhci-tegra.3/MSC /dev/block/mmcblk0p8 empty (misc, bootloader etc.)
/dev/block/platform/sdhci-tegra.3/PER /dev/block/mmcblk0p10 /persist ext4 config/calibration data
/dev/block/platform/sdhci-tegra.3/SOS /dev/block/mmcblk0p1 Recovery kernel (8388608 b)
/dev/block/platform/sdhci-tegra.3/UDA /dev/block/mmcblk0p14 /data ext4 Android user data
/dev/block/platform/sdhci-tegra.3/USP /dev/block/mmcblk0p9 Staging (blob)

sbdags said:
Be careful mmcblk0p8 is /data on the TF700, on the TF701 it is mmcblk0p14
Code:
name device mountpoint fs description
/dev/block/platform/sdhci-tegra.3/ADF /dev/block/mmcblk0p7 /ADF ext4 ?
/dev/block/platform/sdhci-tegra.3/APD /dev/block/mmcblk0p6 /APD ext4 ASUS Product Demo
/dev/block/platform/sdhci-tegra.3/APP /dev/block/mmcblk0p4 /system ext4 Android OS
/dev/block/platform/sdhci-tegra.3/CAC /dev/block/mmcblk0p5 /cache ext4 recovery logs
/dev/block/platform/sdhci-tegra.3/CRA /dev/block/mmcblk0p11 ?
/dev/block/platform/sdhci-tegra.3/DTB /dev/block/mmcblk0p2 ?
/dev/block/platform/sdhci-tegra.3/EKS /dev/block/mmcblk0p13 NVEKSP
/dev/block/platform/sdhci-tegra.3/LNX /dev/block/mmcblk0p3 Linux kernel (8388608 b)
/dev/block/platform/sdhci-tegra.3/MDA /dev/block/mmcblk0p12 ?
/dev/block/platform/sdhci-tegra.3/MSC /dev/block/mmcblk0p8 empty (misc, bootloader etc.)
/dev/block/platform/sdhci-tegra.3/PER /dev/block/mmcblk0p10 /persist ext4 config/calibration data
/dev/block/platform/sdhci-tegra.3/SOS /dev/block/mmcblk0p1 Recovery kernel (8388608 b)
/dev/block/platform/sdhci-tegra.3/UDA /dev/block/mmcblk0p14 /data ext4 Android user data
/dev/block/platform/sdhci-tegra.3/USP /dev/block/mmcblk0p9 Staging (blob)
Click to expand...
Click to collapse
Thanks sdbags, nice catch. Btw, having developed ROMs for this tablet, do you think it's possible at all to boot android off of the external sd? It'd be helpful to know if I shouldn't even bother trying to figure out how.

lexelby said:
Thanks sdbags, nice catch. Btw, having developed ROMs for this tablet, do you think it's possible at all to boot android off of the external sd? It'd be helpful to know if I shouldn't even bother trying to figure out how.
Click to expand...
Click to collapse
Yes I have it working But haven't released it maybe after CROMi-X 7 is finished I will release the flash files that allow you to run one ROM internally and one rom off the card as ROM2SD
It's just an awful lot of work to maintain that doing it for the 300, 201 and 700 transformer crowd has kind of put me off doing for the 701. Also the internal mmc is faster than most fast sdcards so we won't see the benefits that especially the 700 users get.

sbdags said:
Yes I have it working But haven't released it maybe after CROMi-X 7 is finished I will release the flash files that allow you to run one ROM internally and one rom off the card as ROM2SD
It's just an awful lot of work to maintain that doing it for the 300, 201 and 700 transformer crowd has kind of put me off doing for the 701. Also the internal mmc is faster than most fast sdcards so we won't see the benefits that especially the 700 users get.
Click to expand...
Click to collapse
Dude, that totally just made my day, knowing that this is possible Any way you'd be willing to share your development version with me? I'd be your best beta tester every -- hell, I'd be maintainer for the rom2sd part for tf701t if you'd let me. I'm rather motivated at this point, and I have years of professional Linux experience... probably about time I took up android ROM development

lexelby said:
Dude, that totally just made my day, knowing that this is possible Any way you'd be willing to share your development version with me? I'd be your best beta tester every -- hell, I'd be maintainer for the rom2sd part for tf701t if you'd let me. I'm rather motivated at this point, and I have years of professional Linux experience... probably about time I took up android ROM development
Click to expand...
Click to collapse
Hmmm Ok let me sort out the main CROMi-X release and I might take you up on that. I warn you that it is rather a lot to get ROM2SD working though! But if you are up for it ....

sbdags said:
Hmmm Ok let me sort out the main CROMi-X release and I might take you up on that. I warn you that it is rather a lot to get ROM2SD working though! But if you are up for it ....
Click to expand...
Click to collapse
I am totally up for it -- it's that or shelve my tablet until I can afford a logic board I'll be trying to port a ROM to sd from scratch anyway, so having your ROM to start from would be a huge leg up.

lexelby said:
I am totally up for it -- it's that or shelve my tablet until I can afford a logic board I'll be trying to port a ROM to sd from scratch anyway, so having your ROM to start from would be a huge leg up.
Click to expand...
Click to collapse
If your internal sd is completely dead then rom2sd won't work I'm afraid - it relies on the kernel being able to at least read some files from internal to allow it to switch to external....

sbdags said:
If your internal sd is completely dead then rom2sd won't work I'm afraid - it relies on the kernel being able to at least read some files from internal to allow it to switch to external....
Click to expand...
Click to collapse
That's the thing, it works enough to get it into recovery. My plan was to try to kexec from recovery into a modified ROM.

Victory!
I took sdbags's stock zip (4.3) and extracted it on my computer. I used unmkbootimg to extract the initramfs.gz and kernel.gz from the boot.img in the ROM. I unzipped the initramfs and un-cpio'd it, then modified macallan.fstab to refer to /dev/block/mmcblk1p1 for /data, p2 for /system, and p3 for /cache. I also modified init.macallan.rc to avoid having it try to make filesystems on the EMMC -- I want it not to try touching the EMMC at all.
Next I rebuilt the initramfs.gz. I bought a good quality class 10 microsd and partitioned it on my computer with 3 primary partitions, one for /data, one for /system, and one for /cache (about 2GB and 1GB for /system and /cache). I made ext4 filesystems on all 3 partitions, mounted p2, and copied the rom over and installed it by hand using the updater-script as a guide. Then I unmounted and popped the SD card into my TF701t.
To boot it, I put my tablet into fastboot mode. I booted the kernel and ramdisk using 'fastboot boot' -- no need for kexec from recovery. I can do this without any reliance whatsoever on the internal EMMC. It took awhile to boot up, but it booted first try. The app drawer was a bit slow to come up, but I'm pretty happy I get to use my tablet at all! This whole process turned out to be MUCH easier than I expected it would be, and I'm quite confident I could do this to boot any ROM I wanted. I only use stock because of driver issues with my bluetooth keyboard.
Still willing to try my hand at maintaining cromi's ROM2SD branch though
Thanks everyone for all of your help!

Now that it's finished booting, it's really not sluggish at all. Hooray for class 10 sd cards.
Just to make this whole thing even a bit easier, I grabbed an arm-compiled version of the fastboot tool (search for fastbootarm) and put the kernel and ramdisk on my phone, so I can jump-start the tablet using my phone (via USB OTG cable) even when I'm not near my computer.

Will this be usable only from OTG pendrive?(Moto G no sdcard slot)

I had a similar issue with my Nexus 5 and 7 (2013) where I could no longer mount or read the /data or /system partitions but I could still boot into recovery and thought I scored two brand new drink coasters, but then came across this thread where it repaired corrupted partitions and I could now read and mount all partitions normally.
Being a Transformer tablet and not a Nexus device i'm assuming one or two of the adb commands might be a bit different for the disk partitions like someone mentioned in a previous post though..?
Might not be useful to you but thought I'd post it here anyway incase it might help somehow