Related
Computer sees the card, Astro sees the card. Phone acts like it's not there.
Please help. I cannot figure out how to fix this.
Thanks James
I am having a similar problem but when I plug the microsdcard in my computer through the sdcard adapter or in my tmo dash it works just fine. I did a nandroid backup and after that my card was read only. trying changing the attributes in terminal and adb but neither worked and I will admit that im very new to linux stuff so im trying to read as much as i can to figure it out but its not easy.
Hey since no one else replied I decided to try a few things out. I formatted my sdcard in my vista computer and now the phone recognizes it. Not sure what caused that. I was about to reflash jf 1.41 to see if that fixed it but not necessary now. I'm gonna try backing up my phone again with nandroid to see if it duplicates. Seems to e ok even after backup. so now I have no idea what caused it. only other thing i was doing was pushing a new theme to my card through adb but it only pushed the filename. 0 bytes of data. I've looked up a ton of stuff to try to find out what I did wrong. from now on I think I will just use my spare card to update anything on the phone.
btw, card i was having problem with was a sandisk 8gb micro sdhc class 2. For the time being im only going to use this card for backup purposes as I also have a class 6 8gb card. hope this info helps.
Using a Class 6 8GB card here as well and same thing. I may wipe the card as well, but I was hoping iI could find some info as to what caused this... My card is stuck in read only mode too.. sucks.
in Terminal type
mount<enter>
you will get a list of what is mounted, and any attributes ( rw , ro etc etc )
to save typing it all out here, do Menu --> email To...
you now have an email draft, which is nice and pasteable
Here it is:
Code:
$ mount
rootfs on / type rootfs (ro)
tmpfs on /dev type tmpfs (rw,mode=755)
devpts on /dev/pts type devpts (rw,mode=600)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
tmpfs on /sqlite_stmt_journals type tmpfs (rw,size=4096k)
/dev/block/mtdblock3 on /system type yaffs2 (rw)
/dev/block/loop0 on /system/modules type cramfs (ro)
/dev/block/loop1 on /system/xbin type cramfs (ro)
/dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev)
/dev/block/mmcblk0p1 on /sdcard type vfat (ro,dirsync,nosuid,nodev,noexec,uid=1000,gid=1000,fmask=0711,dmask=0700,codepage=cp437,iocharset=iso8859-1,utf8)
ok , its defiantly read only,
why? I have no idea
in terminal do
cat /etc/fstab
have a look at the sdcard line, suspect it reads :
Code:
/dev/block/mmcblk0p1 /sdcard vfat ro
if it does you can fix it with
Code:
su
mount -o rw,remount /system
vi /etc/fstab
ok, vi isn't all that friendly, so here is a quick guide
use the trackball to scroll down to the sdcard line
now press Shift + a
now delete, and type w ( we are telling it to mount read write instead of read only )
press Trackball+1 ( emulates Esc on Desktop )
now shift+z, shift+z ( yeap twice) this saves the changes
your fstab line should now read
Code:
/dev/block/mmcblk0p1 /sdcard vfat rw
this should resolve the ro issue next time sdcard is mount
unmount sdcard in settings, remove card, and reinsert
Code:
mount
fingers crossed, sdcard is rw
nearly forgot, you will probably want to put system back as read only, replace rw.remount with ro,remount
Code:
$ su
# cat /etc/fstab
/dev/block/mtdblock3 /system yaffs2 rw
/dev/block/mtdblock4 /cache yaffs2 rw
/dev/block/mtdblock5 /data yaffs2 rw
/dev/block/mmcblk0p1 /sdcard vfat rw
/system/modules/modules.cramfs /system/modules cramfs ro,loop
/system/xbin/xbin.cramfs/system/xbin cramfs ro,loop
#
fstab has it as rw.
When I first boot up and do a mount, it's rw. If I immediately go into ASTRO and try to remove any files or directories it crashes. Then, if I go and round mount again it gives me the same result as before. ro.
well, you have me stumped
have you tried reinstalling astro?
do you have the same issue with linda?
in the meantime I'll sleep on it, 03:39 here
Firerat said:
well, you have me stumped
have you tried reinstalling astro?
do you have the same issue with linda?
in the meantime I'll sleep on it, 03:39 here
Click to expand...
Click to collapse
I haven't tried linda. I have just noticed that I get a "this software is BETA" message in Astro now.
The root of all this is that I removed a bunch of pictures through ASTRO last week and I've had broken thumbnails ever since in all applications that browse for pictures... photoslide, wallpaper, Pictures, etc... I've been trying to remove the .thumbnail directory since friday, but I keep getting this damn "Read-only filesystem" error and it's starting to really tick me off. Times like this when I get kind of annoyed at some of the half-assedness of some of the android apps.
I was going to just re-format the sdcard but went ahead an ran a chkdsk from Windows beforehand... came up with a ton of errors. I did chkdsk /f and it fixed them all and now everything is working fin. I really think ASTRO screwed something up when it deleted all the files.. anyone else have this happen or was it just a freak occurance?
tbh I doubt Astro would have managed to screw it,
anyway glad everything is good now
But that was when everything started. I deleted about 40 images in astro then the next day I went to look through my photos and I had a ton of broken thumbnails so I tried to use astro to remove the .thumbnails and albumthumbs directors and it would either say the system was read only or it would would just force close. All of the file errors were on the images that I deleted. (there were all 0k files)
I went ahead and tested this myself because I have had the same issue and the idea clicked when you mentioned ASTRO. So All weekend I was using my phone just fine accessing the SDCARD with no problem. Read this post went ahead ran ASTRO deleted some thumbnails .... and guess what? Now the SDCARD is in RO mode and anything that tried to access it crashes.
So it can't be a coincidence that my sdcard decided to stop working.
KNK said:
I went ahead and tested this myself because I have had the same issue and the idea clicked when you mentioned ASTRO. So All weekend I was using my phone just fine accessing the SDCARD with no problem. Read this post went ahead ran ASTRO deleted some thumbnails .... and guess what? Now the SDCARD is in RO mode and anything that tried to access it crashes.
So it can't be a coincidence that my sdcard decided to stop working.
Click to expand...
Click to collapse
its something with astro, i was backin up my apps yesterday and the exact same thing started happening to me so i just moved everything off my sd card to a folder on my computer and formated my sd card. it worked and i deleted astro its about to expire anyway
I just updated my ASTRO last night to the latest beta so it wasn't going to expire till 5/15 but I have removed it as it has completely corrupted the partition map of the SDCARD ... kinda funny I don't have it even partitioned it's just all FAT32.
Thanks ASTRO!
KNK said:
I went ahead and tested this myself because I have had the same issue and the idea clicked when you mentioned ASTRO. So All weekend I was using my phone just fine accessing the SDCARD with no problem. Read this post went ahead ran ASTRO deleted some thumbnails .... and guess what? Now the SDCARD is in RO mode and anything that tried to access it crashes.
So it can't be a coincidence that my sdcard decided to stop working.
Click to expand...
Click to collapse
OK, you have Astro theory to me
tell me was it thumnails or original images that you deleted?
i'm wondering if thumnails get indexed in a db somewhere
Firerat said:
OK, you have Astro theory to me
tell me was it thumnails or original images that you deleted?
i'm wondering if thumnails get indexed in a db somewhere
Click to expand...
Click to collapse
I'm not sure what happened or even if it was related to Astro but yesturday for an unknown reason I phone was acting very strange.
Example:
The first occurance was when I opened Telenav to get me the directions back home (from hanging out with my gf) and the app said that I still needed to reactivate GPS. (Oh yeah... that's right... I deactivated it to save battery life. DUH!) After doing so the app crashed. I tried starting it up again and it would pop up for a second and the go back to my home screen (Open Home). So I did a reboot.
After my phone started back up all hell broke loose. About 12 of my apps popped up with Force Close!
Realizing the inevitable, I decided to use MyBackup to backup my settings (sms, caller log) and it gave me an unable to access DB or something like that.
I don't think that it was Astro but I can't figure out what could have caused this.
I spent about 3 hours last night reinstalling all of my apps from Market because even though they are all saved to the ext2 on the SD (Thank God!) it still says FREE in market the apps that I have installed. (BTW... anyone know a fix?)
So it wasn't my SD card, I didn't do anything new at all. No installed apps, no themes, no updates, nothing. I guess it was a ghost in the machine.
Any clues?
Firerat said:
OK, you have Astro theory to me
tell me was it thumnails or original images that you deleted?
i'm wondering if thumnails get indexed in a db somewhere
Click to expand...
Click to collapse
I did two things ... just to test it out. Cleared thumbnails ends up the same result corrupted partition(RO) then deleted a file from the SDCARD and once again it did the same thing.
I tried this with Linda File Manager and it is working fine no change to the SDCARD & I was able to do everything with it that I was able to do with ASTRO just about.
ASTRO is either locking the SDCARD to do it's deletes and not unlocking it after it's done or something is just not being done right that is ends up corrupting the card.
I had the same problem with the Discover app. I'd move images and music over wifi from my computer and then they wouldn't show up in the music/pictures app. Other apps would see them.. I was able to just delete them normally and then copy them over via USB and it worked fine. Seems some apps, when they write, bork up the permissions.
These patches add ext4 support for your sdcard (in the Nexus S - the internal card.) There are a number of reasons you might want to do this - performance (ext4 is faster, plus mounting ext4 is basically instantaneous, which is very nice on reboots...no more checking sdcard), it's more efficient, you get a bunch of file system security features (if you care...)
You should not apply them if you don't really know what you are doing. The patches are resonably benign. Converting your sdcard partition to ext4 is NOT NOT NOT benign and you can really hose yourself doing it.
I'm not going into great depth with these instructions. If you don't understand them, play around with building cyanogen, installing it, etc until they are crystal clear.
To swap your sdcard to ext4:
* Apply the patches and rebuild cyanogen. Rebuild it. They will change your recovery image and vold.
* Install vold and flash (and/or boot) the recovery image.
* Boot into recovery, mount your sdcard and back it up to your computer (i.e., not nandroid, copy the files.) Nandroid would be a good idea too.
* Format your media partition to ext4 (the one that is vfat, by-name is media, mine is partition 3) mkfs.ext4 can be found by googling, or you can use make_ext4fs from /system/bin. I used mkfs.ext4.
* You should be able to manually mount that.
* Push your files back.
* sync and reboot.
Et Voila, you should have an ext4 sdcard partition.
THIS IS VERY DANGEROUS.
YOU CAN REALLY HOSE YOURSELF DOING IT.
Here are the patches:
http://review.cyanogenmod.com/#change,1705
This one adds ext4 support to vold, thus allowing gingerbread to mount ext4 partitions for the sdcard (which on the Nexus S, is the 'media' partition.)
and:
http://review.cyanogenmod.com/#change,1716
This is a change to recovery, making it seamlessly mount ext4 partitions for /sdcard.
Code:
# mount
/dev/block/platform/s3c-sdhci.0/by-name/system on /system type ext4 (ro,noatime,barrier=1,data=ordered,noauto_da_alloc)
/dev/block/platform/s3c-sdhci.0/by-name/userdata on /data type ext4 (rw,nosuid,nodev,noatime,barrier=0,data=ordered)
[b]/dev/block/vold/179:3 on /mnt/sdcard type ext4 (rw,nosuid,nodev,noexec,noatime,barrier=1,data=ordered,noauto_da_alloc)[/b]
/dev/block/vold/179:3 on /mnt/secure/asec type ext4 (rw,nosuid,nodev,noexec,noatime,barrier=1,data=ordered,noauto_da_alloc)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
....and if you turn on USB Storage, the sdcard shows up as an ext4 disk...
As expected, but this is going to be one for the Linux geeks.
Wow, it is VERY nice to have that sdcard mount instantly on boot. VERY nice.
oh the read/write speeds
If anyone is interested in playing with this, I submitted the change to cyanogen:
http://review.cyanogenmod.com/#change,1705
The tricky bit is getting the filesystem created. You can use:
/system/bin/make_ext4fs.
That leaves me with a recovery which will not currently mount sdcard as ext4 unless I fiddle with fstab and mount it myself. On to look at that.
...and, here's a patch to the recovery which will let it mount /sdcard as either ext4 or vfat, making this change reasonably seamless.
http://review.cyanogenmod.com/#change,1716
i would love to see a Quadrant or a benchmark after this
this is and awesome hack to use with App 2 SD
it'll be lag less
the only annoyance, is that if you want to MOUNT USB on a Windows PC, then you'll need a software to read EXT4
for anyone interested this will be handy
http://www.ext2fsd.com/?page_id=16
i'll definitely be doing this MOD, as i'll be running anything i can from the Internal SD
So this will only work on CM7?
Please some of the genius here may post a step-by-step tutorial or howto for this one? It will be very apreciated.
No, it will work with any build, but you need to rebuild vold in order to get it to mount. The easiest way to get them outside of the CM tree would be to build cm and then copy the vold out and use that. It should work with any ROM.
The latest versions - which are in CM's gerrit - include modifications to the sdcard utility to use fuse to mount the filesystem using FAT semantics (i.e. - bypass security). Frankly, this is a waste. It slows everything down, noticeably, and app problems are few and easily fixed if you know how to fire off a chmod.
I haven't provided step by step instructions since it can seriously hose your phone if you don't know what you are doing.
DebauchedSloth said:
No, it will work with any build, but you need to rebuild vold in order to get it to mount. The easiest way to get them outside of the CM tree would be to build cm and then copy the vold out and use that. It should work with any ROM.
The latest versions - which are in CM's gerrit - include modifications to the sdcard utility to use fuse to mount the filesystem using FAT semantics (i.e. - bypass security). Frankly, this is a waste. It slows everything down, noticeably, and app problems are few and easily fixed if you know how to fire off a chmod.
I haven't provided step by step instructions since it can seriously hose your phone if you don't know what you are doing.
Click to expand...
Click to collapse
Wait so it's a waste? It isn't worth using ?
Anderdroid said:
Wait so it's a waste? It isn't worth using ?
Click to expand...
Click to collapse
If done right this would increase the read/write speeds. For example, your boot up time would be much faster and ext4 is more effecient. So it's not a waste but it has to be done correctly otherwise is could do more damage than good
Using the version I posted to CM gerrit, which bounces the file system through fuse and mimics FAT security, is still better than FAT (IMO), but it's not nearly as fast as just mounting the filesystem as Ext4 - though it is more compatible.
I've been running mine mounted as straight ext4 for a couple of weeks. Probably the single best mod I've made to any of my phones. There are occasional app bits that I need to fix manually (such Dropbox resetting file ownership), but it's worth it for the quicker boot up and faster overall operation.
Here you find the ROM CyanogenMod 7 compiled for Nexus One with ext4 sdcard mount support:
- https://github.com/diegostamigni/nexus/tree/master/one
Is the only reason to pipe it through fuse to get it to mount on m$? If so I'm not going to bother - I only use linux almost exclusively these days
diego.stamigni said:
Here you find the ROM CyanogenMod 7 compiled for Nexus One with ext4 sdcard mount support:
- https://github.com/diegostamigni/nexus/tree/master/one
Click to expand...
Click to collapse
No version for Nexus S?
Looking forward to this develpoing, as the ext4 conversion (done via modaco rom beta2 in recoverymode) made a HUGE difference to the galaxy tab i have (halved the loading times of everything). ^^
Unfortunately im far to noob to help out though ...will be keeping a keen eye on it all and learning
Forgive my ignorance, but why don't phones come like this?
NicholasQ said:
Forgive my ignorance, but why don't phones come like this?
Click to expand...
Click to collapse
window$ more then likely.
window$ can't even see Linux file systems without special drivers installed.
if i mess this up would it brick my phone? i'm really wanting to try this but i don't want to turn my Nexus S into a paperweight
so if we did this, would the windows computer be able to read the mounted sd card? is there any other things that would be needed after this mod? or just format to ext4 and be done with it?
Ok guys, so this is my problem.
As you all know the RAZRi has 8gb of built in storage, but as I am aware, there is a 5gb virtual sd card which you have access to, for installing apps etc. The rest is for os. Now when you insert an sd card it counts as a 2nd sd card.
So you get 5gb of data fofjr apps, but as i think the phone thinks its on an sd card already, you cant move apps to your external sd card.
So when you have a few large games like max payne, that 5gb disappears real quick.
I have tried manually moving data for apps to my sd card but it did not work and the apps would not load.
What are your suggestions?
On my old motorola defy you could just install apps to either the internal storage or the sd card, nice and simple.
Can you disable this feature or is there a way to install large apps to external media.
Thanks in advance!!!!
Yes I found it rather odd too. Also the SD mount point has got a very funny path. It is /mnt/external1
I am afraid that I must disappoint you here. According to person called "Badger1313" most of root exploits are through the App file transfer software. Due to the fact Motorola decided to secure this vulnerability by disabling 'Move to SD'.
Uncle Google came unhelpful this time giving me no answers to this question. The only valid way to make it possible is to have your phone rooted. Lets hope JB will bring some changes.
zmesler said:
Yes I found it rather odd too. Also the SD mount point has got a very funny path. It is /mnt/external1
I am afraid that I must disappoint you here. According to person called "Badger1313" most of root exploits are through the App file transfer software. Due to the fact Motorola decided to secure this vulnerability by disabling 'Move to SD'.
Uncle Google came unhelpful this time giving me no answers to this question. The only valid way to make it possible is to have your phone rooted. Lets hope JB will bring some changes.
Click to expand...
Click to collapse
Razr I is "rootable" so how to mount sdcard to /sdcard ?
Maybe some stuff to edit in init.d !?
Maybe something like this:
http://www.theandroidsoul.com/use-external-sd-card-as-internal-memory-on-droid-razr/
Le_Poilu said:
Maybe something like this:
http://www.theandroidsoul.com/use-external-sd-card-as-internal-memory-on-droid-razr/
Click to expand...
Click to collapse
For sure, but at the moment this is still not possible to flash anything from the recovery.
Would a manual editing of the vold.fstab file to set the following line work ?
Code:
dev_mount sdcard /mnt/sdcard auto /devices/platform/mmci-omap-hs.0/mmc_host/mmc0
(still did not buy this awesome phone)
Or maybe using Directory Bind, don't know but I use it to mount my SD Card on diferent points for my SGS2.
JackyJack said:
For sure, but at the moment this is still not possible to flash anything from the recovery.
Would a manual editing of the vold.fstab file to set the following line work ?
Code:
dev_mount sdcard /mnt/sdcard auto /devices/platform/mmci-omap-hs.0/mmc_host/mmc0
(still did not buy this awesome phone)
Click to expand...
Click to collapse
I did try a manual edit of vold.stab, unsuccessfull
Each time I still have the intern memory accessible and extern1 still here but empty.
Here is the vold.fstab file of the Razr i, if you have an idea what to change.
Code:
# Copyright (C) 2009 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
## Vold 2.0 fstab for the Morrestown Platform
#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
######################
# Mounts the first usable partition of the specified device
dev_mount sdcard-ext /mnt/external1 auto /devices/pci0000:00/0000:00:04.0/mmc_host/mmc1 /devices/pci0000:00/0000:00:02.3/gadget/lun0
Le_Poilu said:
I did try a manual edit of vold.stab, unsuccessfull
Each time I still have the intern memory accessible and extern1 still here but empty.
Here is the vold.fstab file of the Razr i, if you have an idea what to change.
Code:
# Copyright (C) 2009 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
## Vold 2.0 fstab for the Morrestown Platform
#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
######################
# Mounts the first usable partition of the specified device
dev_mount sdcard-ext /mnt/external1 auto /devices/pci0000:00/0000:00:04.0/mmc_host/mmc1 /devices/pci0000:00/0000:00:02.3/gadget/lun0
Click to expand...
Click to collapse
Well, actually the vold.fstab file on the Razr i only handle the scard-ext partition (wich I don't know what it's used for, but for sure this not /sdcard either /external1).
I guess there is some init script somewhere or config file regarding sdcard and external1 mappings.
BUT, as /sdcard is mounted from internal memory, if you replace it with your µSD, then you'll lost the space used by the /mnt/sdcard partition, unless you mount it elsewhere...
I may be wrong there...
BUT, as /sdcard is mounted from internal memory, if you replace it with your µSD, then you'll lost the space used by the /mnt/sdcard partition, unless you mount it elsewhere...
I may be wrong there...
Click to expand...
Click to collapse
I think you right about this.
This is what appends for Droid Razr user when they use this:
http://www.theandroidsoul.com/use-external-sd-card-as-internal-memory-on-droid-razr/
External SD take the place of internal SD.
For me it's a very little problem. I can lost 5GB if I win 32GB on the other side (or even more as the Razr i can handle 64GB SDXC card.)
But maybe can we have both. My first android phone was the first Samsung Galaxy i7500 which had 8BG of internal SD storage and a SDHC extension slot. Both internal and external was fully usable as SDCard
Maybe with a custom ROM in the futur.
Yeah, maybe we should focus first on tweaking the recovery so we can flash custom roms, this partition stuff looks like deep modding...
I am looking for some documentation about our partition tables, don't really know where to find what size are /boot, /system and all other partition that may exists...
Im using JB..and still it doesnt work
I use directory bind and it works great i have 20gb of game data
Hi,
first of all tnx to the penguins for the great CM10 based PA ROM. I'm running it since Build 02 and lovin it.
I noticed that the external SD is mounted under /storage/sdcard1 next to the internal /storage/sdcard0 or /sdcard
This leads to one strage thing: Under /sdcard/_ExternalSD I only see the empty folders .../DCIM/Camera while the Camera pictures get (correctly) filed under /sdcard/DCIM
I can only access the external SD with root explorer therefore and it's contents cannot be used by many apps and functions (like Airdroid)
Am I doing anything wrong? Is there an easy way to fix it?
tnx in advance
jolithan said:
Hi,
first of all tnx to the penguins for the great CM10 based PA ROM. I'm running it since Build 02 and lovin it.
I noticed that the external SD is mounted under /storage/sdcard1 next to the internal /storage/sdcard0 or /sdcard
This leads to one strage thing: Under /sdcard/_ExternalSD I only see the empty folders .../DCIM/Camera while the Camera pictures get (correctly) filed under /sdcard/DCIM
I can only access the external SD with root explorer therefore and it's contents cannot be used by many apps and functions (like Airdroid)
Am I doing anything wrong? Is there an easy way to fix it?
tnx in advance
Click to expand...
Click to collapse
Thats my Dear friend is our Beloved ICS Formatation there are Tools to Swap or Redefine Partitions like http://forum.xda-developers.com/showthread.php?t=2020737 its comes with a self explaining Manual.
And Well. Hit thanks if i Helped
Have a nice day
You can use in terminal : "mount -o bind /storage/sdcard1 /storage/sdcard0/_ExternalSD" after creat with "mkdir /storage/sdcard0/_ExternalSD". For have all the time, after boot, use SManager ( in play store ) for execute a small script, juste une ligne : mount -o ..... by.
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?