Related
I'm running OpenEclair 1.2.2 on a standard UK G1. I have no swap partition, and no EXT3 on my card as I prefer the idea of keeping all my apps on my phone.
However, it would seem like I have a corrupt file system on my phone, as after a restart, apps will disappear, force close, or behave very strangely!
So my question is, how do I repair my phone filing system? Not my SD card, but the one in my phone where apps are stored?
Thanks
Rebooted again and now all my contacts are missing. Also tired running this command (don't know if it's correct)
e2fsck -fpDC0 /dev/block/mmcblk0p2
I get an error saying no such file or directory.
Funkstar De Luxe said:
Rebooted again and now all my contacts are missing. Also tired running this command (don't know if it's correct)
e2fsck -fpDC0 /dev/block/mmcblk0p2
I get an error saying no such file or directory.
Click to expand...
Click to collapse
Did you run this from recovery console? I don't think it will work from adb or terminal.
Yeah, I get the same error
Funkstar De Luxe said:
Yeah, I get the same error
Click to expand...
Click to collapse
Sorry, just reread your first post. That command is to repair your Ext2(3) partition. Since you don't have that, you would get that message. I understand why you would want to not use ext as your phone should load apps faster off the phone itself. The problem is, the rom itself needs more space than the standard rom that came with the phone. Your best bet is to wipe, partition, and reinstall OE. You could try a different rom to see how it performs without the ext for app to sd. In fact, if you find 1 that works well you should post your results to help others.
I was dicking around with the Rom Explorer (can't remember the exact name) app that comes with CM7 and I installed CMR onto my Nook. Problem is, it installed the 3.0.0.5 version over the previously installed 3.0.0.6, which I didn't know until I rebooted. When I did, it booted straight into Recovery version 3.0.0.5 and threw up the following errors:
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
Fine, no problem. I'll just flash 3.0.0.6 on and... ADB won't work.
Okay, new tactic. I'll just wipe /system, /data, /cache, and reinstall CM7, which might fix recovery. Only...
E:Can't mount /sdcard
Ah.
Well, no problem, B&N wisely made the NC basically unbrickible to stop returns from idiots like me. I'll just boot 3.0.0.6 from my sdcard and flash CM7 again. Yay, it works! Only... it doesn't quite. It refuses to show up in ADB, and the root that I have is buggy. Titanium backup offers to install a newer version of su, but I already have the latest. I double check by trying to rename a file in /system with Root Explorer. No dice.
Well wonderful. Time to start from scratch. So I try all the return-to-stock methods in this thread, but none of them work.
At this point, I'm not really sure what I messed up... obviously flashing the older recovery image is a big part of it, but I'm completely flabbergasted as to why I apparently can't overwrite it with ANYTHING.
Does anyone have any ideas how I can fix this?
Sigh. I know this is the wrong section, but I don't have enough posts to post in the development subforum... certainly someone must have an idea of what I can do? Or am I completely SOL?
Finally got back to stock using brian21's stock 1.1 image! Now to start all over again.
lelandjs said:
Finally got back to stock using brian21's stock 1.1 image! Now to start all over again.
Click to expand...
Click to collapse
Glad you got it working again.
Isn't the Nook a wonderful device. It makes your world shine when you first root it. And then comes CM7. And even a HC preview. And then of course it throws a wrench in everything when we aren't paying attention to details and our happiness is turned into frustration.. and from the frustration brings us some actual knowledge.
I find the best part about my Nook is all the great things that I have learned along the way. From never touching an android platform to actually starting to learn some linux along the way.
Just my 2 cents.
racks11479 said:
Glad you got it working again.
Isn't the Nook a wonderful device. It makes your world shine when you first root it. And then comes CM7. And even a HC preview. And then of course it throws a wrench in everything when we aren't paying attention to details and our happiness is turned into frustration.. and from the frustration brings us some actual knowledge.
I find the best part about my Nook is all the great things that I have learned along the way. From never touching an android platform to actually starting to learn some linux along the way.
Just my 2 cents.
Click to expand...
Click to collapse
Not gonna lie, I was... underwhelmed by the rooted default Nook firmware. It just ended up being too slow. But CM7?
The NC actually marks my return to Android; I was slinging roms on my G1 back in the day (hence my vague knowledge of rom flashing).
Can't wait for a Honeycomb build, though I'm happy enough with CM7 for the moment. This really is a great tablet; the perfect size for taking with you to work and reading some comics on the subway. I liked the iPad but it (and other 10" tablets) was just too large for practical use.
i have the same problem,
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
is this due to the CWR version, I have 3.0.0.5. I have CWR installed on the internal as well as booting it from sd.
were you able to format system and data under mount and settings because i get an error when doing so. Seems like this is a crucial step. This stops me from completing the steps necessary to flashing the file. If I try flashing the zip without formatting, my install aborts and gives me an error.
Sam is actually helping me sort out when he can but we still haven't been able to get it going. My emmc is corrupt is all i know and needs reformatting but abd won't even allow.
I am having the same problem as the post above me. I am a noob any help would be greatly appreciated.
lelandjs said:
Can't wait for a Honeycomb build, though I'm happy enough with CM7 for the moment.
Click to expand...
Click to collapse
Until now and you are still waiting for HC? Seriously?
wendellc said:
My emmc is corrupt is all i know and needs reformatting but abd won't even allow.
Click to expand...
Click to collapse
I had a very good double-boot configuration from NC stock 1.0.1-cm7 on a 32Gb SanDisk card. At that point, I could easily sideload media into the NC and the SDCard. I thought that I had successfully upgraded to the NC to 1.4 and then installed the triple-boot configuration stock/cm7/cm9 from the SDCard. The NookColor showed up in XP Pro Device Manager > Hardware. However, I began to run into problems at this point, I can't recall specifically (that was several weeks ago) what these problems were, other than that, after reading the forums here, I suspected that it might have had to do with upgrading the NC stock from 1.0.1 to 1.4. So, I managed to restore the NC 1.4 back to 1.2 (I read that NC stock 1.3 auto-updated if it were the boot). Then I burned the triple-boot back onto to the SDCard. I could access NC 1.2 stock/cm7/cm9 but I could no longer sideload media into the NC. When I take out the SDCard and plug the NC into XP, only two partitions appear as separate drives. The only partition that appears in XP Pro Windows explorer is the "boot" (115MB), with the list of files for the NookColor, it looks like.
I thought that, maybe, this was an acceptable price to pay, this loss of access to the internal 5Gb of the NC but access to the rest of the storage on the 32Gb SDCard. But, I need the NC ebook reader's access to its internal 5Gb storage and the 32Gb storage. When I recently booted into cm9, I got the message "Unfortunately, Trebuchet has stopped" so I tried to use adb to load an .apk into the appropriate place in order to attempt to repair/correct this. This is when I discovered that it seems like my NC emmc has, somehow, been corrupted because it doesn't appear in adb > adb devices. And when I've closed the 5037 connection in TCPView, adb still will not connect.
So, besides no longer being able to access the NC 5Gb storage from inside NC nor being able to sideload into NC, I can't repair the cm9 installation. If the NC emmc has been corrupted, would a simple upgrade to 1.3 repair this? If so, do I put the 1.3 update into the root NC by copying it to the "boot" 115MB drive and then inserting the SDCard into the NC and booting into NC?
Is there a way to repair or restore the NC so that I can sideload files into it?
I've plugged the NC into two other Windows XP machines with similar results, so it's a problem with the NC.
Thank You!
Sorry i didn't read all the details, but you really shouldn't be using such old CWM recoveries.
http://forum.xda-developers.com/showthread.php?t=1469732
boldred said:
I had a very good double-boot configuration from NC stock 1.0.1-cm7 on a 32Gb SanDisk card. At that point, I could easily sideload media into the NC and the SDCard. I thought that I had successfully upgraded to the NC to 1.4 and then installed the triple-boot configuration stock/cm7/cm9 from the SDCard. The NookColor showed up in XP Pro Device Manager > Hardware. However, I began to run into problems at this point, I can't recall specifically (that was several weeks ago) what these problems were, other than that, after reading the forums here, I suspected that it might have had to do with upgrading the NC stock from 1.0.1 to 1.4. So, I managed to restore the NC 1.4 back to 1.2 (I read that NC stock 1.3 auto-updated if it were the boot). Then I burned the triple-boot back onto to the SDCard. I could access NC 1.2 stock/cm7/cm9 but I could no longer sideload media into the NC. When I take out the SDCard and plug the NC into XP, only two partitions appear as separate drives. The only partition that appears in XP Pro Windows explorer is the "boot" (115MB), with the list of files for the NookColor, it looks like.
I thought that, maybe, this was an acceptable price to pay, this loss of access to the internal 5Gb of the NC but access to the rest of the storage on the 32Gb SDCard. But, I need the NC ebook reader's access to its internal 5Gb storage and the 32Gb storage. When I recently booted into cm9, I got the message "Unfortunately, Trebuchet has stopped" so I tried to use adb to load an .apk into the appropriate place in order to attempt to repair/correct this. This is when I discovered that it seems like my NC emmc has, somehow, been corrupted because it doesn't appear in adb > adb devices. And when I've closed the 5037 connection in TCPView, adb still will not connect.
So, besides no longer being able to access the NC 5Gb storage from inside NC nor being able to sideload into NC, I can't repair the cm9 installation. If the NC emmc has been corrupted, would a simple upgrade to 1.3 repair this? If so, do I put the 1.3 update into the root NC by copying it to the "boot" 115MB drive and then inserting the SDCard into the NC and booting into NC?
Is there a way to repair or restore the NC so that I can sideload files into it?
I've plugged the NC into two other Windows XP machines with similar results, so it's a problem with the NC.
Thank You!
Click to expand...
Click to collapse
First, your adb problem with CM9 is because CM9 uses different device ids for the windows usb adb driver than stock or CM7. If you want to know how to fix that, I can quote one of my posts for you.
I think you should take your SD and make a new single CM7 SD. You are getting too complex with triple booting while trying to debug. Then you can see if your emmc media partition is corrupt or not as I said in my other post about mounting drives in windows. Then once you are sure everything is ok with emmc, you can go back to triple booting.
The reason you are seeing 'boot' show up in windows when you plug the NC into windows running stock is the stock looks at partition 1 of an SD for 'sdcard'. On your triple boot SD partition 1 is the boot partition.
If it turns out that your emmc media partition is corrupt, I can help you fix that.
To learn more about fixing your stock if you need to again, read eyeballers thread (the epilogue of the first post).
http://forum.xda-developers.com/showthread.php?p=12797652
By doing the repartitioning he talks about in Dean Gibson's thread you can follow it but instead of going from 1GB media to 5GB media, back up, repartition to 5GB again and you will have a new reformated 5GB media. Then restore your data partition.
votinh said:
Until now and you are still waiting for HC? Seriously?
Click to expand...
Click to collapse
eyeballer said:
Sorry i didn't read all the details, but you really shouldn't be using such old CWM recoveries.
Click to expand...
Click to collapse
Folks, if you look at the dates of these earlier posts you will see they are from February of 2011 not 2012. That's why they were talking about Honeycomb and CWR 3.0.0.5.
leapinlar said:
Folks, if you look at the dates of these earlier posts you will see they are from February of 2011 not 2012. That's why they were talking about Honeycomb and CWR 3.0.0.5.
Click to expand...
Click to collapse
Ahh, my bad, getting old, I guess.
Apologize to OP, beer on me
Hey there, fellow users,
Earlier this week, I went through the process of installing Arch Linux ARM on my Touchpad (it already had CM9 and webOS.)
About midway through, I had to unmount /media/internal. Umount returned that the device was busy, so I ran fuser -vm /media/internal and found that pid 13093 was using the file system. Sadly, I didn't notice what the name of the process was when I killed it...
Yesterday, I booted up CM and got the "Damaged SD Card" message. After a little trial and error, I remembered /media/internal. So I booted into webOS and listed the contents, and there were all of the Android files. Then I tried to remount the partition. I got this error:
mount: mounting /dev/mapper/store-media on /media/internal failed: Device or resource busy
So, is there anything I can do? Do I have to backup the files and reinstall CM?
Thank you.
I guess I wasn't clear.
The virtual SD card in CM won't mount, and won't format. It seems to mount in CWM, though. It is represented by the file system /mount/internal in webOS. Also, all of the music in webOS disappeared.
Is there anything that I can do to get the SD card and the music back?
WMH7 said:
Hey there, fellow users,
Earlier this week, I went through the process of installing Arch Linux ARM on my Touchpad (it already had CM9 and webOS.)
About midway through, I had to unmount /media/internal. Umount returned that the device was busy, so I ran fuser -vm /media/internal and found that pid 13093 was using the file system. Sadly, I didn't notice what the name of the process was when I killed it...
Yesterday, I booted up CM and got the "Damaged SD Card" message. After a little trial and error, I remembered /media/internal. So I booted into webOS and listed the contents, and there were all of the Android files. Then I tried to remount the partition. I got this error:
mount: mounting /dev/mapper/store-media on /media/internal failed: Device or resource busy
So, is there anything I can do? Do I have to backup the files and reinstall CM?
Thank you.
Click to expand...
Click to collapse
Read this thread: http://forum.xda-developers.com/showthread.php?t=1426244
If you're having problems with novaterm, there's a good work around in page 12 (I'm pretty sure that's where it is). This guide has helped me a couple of times already.
Good luck.
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?
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