Related
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
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.
I picked up my Touchpad today to play with it, and my Internal Storage seems to have disappeared in Android. I rebooted to WebOS, and everything seems to be OK there, but when I reboot back to CM10, there's no "SD Card". There aren't any errors or anything...I wouldn't have noticed except that I opened ES File Explorer and it said "SD Card empty, unmounted or not present". I'm not sure how to troubleshoot this...any ideas? I'm running [12/16] Unofficial CM10 Preview by Jcsullins.
Strangely the same thing happened to me today as well. I booted into WebOS and checked the filesystem and there were some corruptions and I fixed that but it didn't change anything so I just reflashed my rom and that fixed everything...for now. I did notice that somehow I suddenly had both superuser and supersu so I had to disable one of those, maybe check that too
I have Ubuntu (13.04 alpha, from the thread in the Dev forum) installed on the Touchpad, and I noticed in the dev thread that there was some kind of problem with mounting the "SD Card", that it was mounted with the wrong uid or something. Could that be connected to my problem? I can access the "SD Card" in WebOS and Ubuntu, just not in Android, which makes me think it's some kind of mounting issue. I'd prefer to troubleshoot the issue, maybe get a solution that will benefit others, as opposed to going with the WebOS Doctor nuclear option. Any thoughts?
All that worked for me is reflashing the ROM.
Sent from my HP TouchPad using xda-developers app
Tired_ said:
I picked up my Touchpad today to play with it, and my Internal Storage seems to have disappeared in Android. I rebooted to WebOS, and everything seems to be OK there, but when I reboot back to CM10, there's no "SD Card". There aren't any errors or anything...I wouldn't have noticed except that I opened ES File Explorer and it said "SD Card empty, unmounted or not present". I'm not sure how to troubleshoot this...any ideas? I'm running [12/16] Unofficial CM10 Preview by Jcsullins.
Click to expand...
Click to collapse
I had the same thing happen. I wiped/reset, wiped cache, formatted system and wiped dalvik cache. Reflashed ROM and gapps. So far so good.
Ok, so I tried reflashing my Android. I wiped cache/Dalvik, but nothing else. My internal storage was fine when I was done this, and I didn't lose any files or settings. Sounds great, right? Well, I rebooted into Ubuntu 13.04 Alpha, and everything seemed fine there, till I rebooted into Android, and lo and behold, internal storage not found. Just for laughs, I went into Terminal, and typed "mount -t vfat /dev/store/media /sdcard", and then I was able to access the files on the internal storage, but only through a file manager by going to /storage/sdcard0...none of the apps could see the internal storage the normal way. I still think this is some kind of mounting or permissions problem, and now that I can replicate the problem reliably, maybe we can put our heads together and find out why.
What recovery have you been using please?
sstar said:
What recovery have you been using please?
Click to expand...
Click to collapse
I am currently using TWRP 2.4.3.0. I was using an earlier TWRP, in the 2.3 series, but I upgraded it today when I reflashed my rom.
Tired_ said:
I am currently using TWRP 2.4.3.0. I was using an earlier TWRP, in the 2.3 series, but I upgraded it today when I reflashed my rom.
Click to expand...
Click to collapse
Have a read of this http://forum.xda-developers.com/showthread.php?t=2177905.
You are not the only one, your files are probably in a folder called Lost.Dir but renamed to an unusable number.
sstar said:
Have a read of this http://forum.xda-developers.com/showthread.php?t=2177905.
You are not the only one, your files are probably in a folder called Lost.Dir but renamed to an unusable number.
Click to expand...
Click to collapse
My files are all there, not renamed, not in a lost directory. I can access each and every one in WebOS (same way as always), in TWRP (again, the same way I always could), and in Ubuntu...and in Android if I manually mount /dev/store/media (but they're in /storage/sdcard0 rather than /sdcard). I'm pretty sure I said this already.
The file "loss" happened from booting Ubuntu. Before I booted Ubuntu, the "SD Card" was present, and accessible in Android. I boot Ubuntu, just to see if it came up OK (it did), so I rebooted back to Android. Immediately, it says SD card unavailable or not mounted, until I remount manually, which made the files appear in /storage/sdcard0 until reboot, at which time I'd have to manually remount again to see them.
Hey guys, So i've been having a ton of internal sd card issues.
First off I used the "Updated vibrant update guide" from cyanogenmod's old wiki.
I flashed semaphore 2.7.4.tar, went to overstock screen, phone said it was partitioning, I waited about 30 minutes, nothing happened, so I continued to another way to get into cwm.
Next,
I flashed cmnard-t959-cwm.tar, successfully gotten into CWM v5.0.2.7, Afterwards I gotten this error when tried to mount USB storage:
"E: Unable to write ums lunfile (No such file or directory)"
Next, I tried flashing back to stock rom using the JW4.tar's provided by another post. here:http://forum.xda-developers.com/showthread.php?t=1647890
Then I got ANOTHER error along the lines of:
"
E:format_volume: make_extf4fs failed on dev/block/mmcb1k0p2
Formatting /sdcard.andriod_secure...
Error mounting /sdcard/.android_secure!
skipping format!
"
Another one was Error in /sdcard/dev/block/mmcb1k0p2 (status 0)
So then I figured, well I think I screwed the internal SD card, So then I tried the external replacement approach from this guide here: http://forum.xda-developers.com/showthread.php?t=1906089
Same exact errors, even after using minitools partition wizard,
So then again I tried another approach.
Why not just try and flash cyanogenmod 9.1 stable in CWM anyways?
So I did, and it worked, but then I get prompted with:
"The encryption on the devices was unsuccesful, please reset the phone's data to continue"
So pretty much internal sd card is screwed, I've been staying up til 4am almost 2 weeks straight, and no solutions yet.
Please for the love of god help this poor sap of a man(me).
Thanks for reading,
-Kx3clock
bump
see and ask here
http://forum.xda-developers.com/showthread.php?t=845708
https://www.youtube.com/watch?v=zdMhYYdMB08
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?