Database Users

[Q] SD Card mounting Issue!

I got my phone less than a year ago. Ran the 1 click root thing worked flawlessly since then and about a week ago my phone just decided to not work. All the applications i would open would force close and you couldn't do anything. So i turned it off and when i turned it on i got my problem.
The phone boots into the "S" and then it hangs at the loading screen until i pull the battery out.
I google searched a few times and i determined it was an SD card failure. The guide i followed told me to go into the 3 button combo thing and when i go to do a factory reset it gives me this "E:Can't mount /dev/block/mmblkOp1 (I/O error)
E:Can;t mount SDCARD:update.zip"
It's still on stock firmware, froyo i think?
Any help please?

Myhm... sometime happens.
It may be some issue.. try to flash clocworkmod 2.5.1.8.. if you are on Froyo, it may help. another solution may be (and I'd try it first) to apply Click

[Q] The Unbreakable Bootloop - Am I bricked?

The Device:
Nookcolor Refurb - came with stock 1.2 installed. Rooted with CM7 - initially had boot partition problems and went back and did the fix for it. (was using an old CWR, so had to redo that, too). Worked mostly fine for a few weeks. Had a little trouble installing the recent cm7 stable update. But after clearing and redo, no problems. Then I updated Adobe flash to 10.3 through the market. bad, bad, bad. (I've discovered). It has gone into a bootloop, but it doesn't even get in far enough to bring up CWR either internally or on a bootable SD card. It brings up "loading" - whether in CM7 or CWR - then shuts itself off. I have tried the 3 button salute and 8 interrupted boots, but neither works in any way. Is there something else I can do?
Also, a side note, the device will not charge to green light - even if charging overnight. At first I thought it was a battery issue, but after a day of combing the boards, I'm thinking bootloop from hell.
Help!!!!

Are you running CM 7 internally or from a card? If internally, try making a bootable CM 7 card and booting from that.

I am running it internally. The device will not boot from a card or internally. It doesn't get far enough into the boot before it loops for CWR to start up - either internally or off the sd card. I can get to the boot menu (hold down n when it starts up), but it doesn't boot off any of the options there, just goes to black screen.

What happens when you do the 8 failed boots?

Nothing really happens with 8 failed boots. I think it terminates the boot process before it gets far enough along for it to "count". Loading comes up, I count one thousand one....all the way to one thousand seven. Then it shuts off, often reboots itself. Same deal with CWR. Loading comes up, count to 7, shuts off. I can get to the boot menu in CM7, but I it doesn't respond when I request any type of boot from anywhere. Either hangs or restarts.
I'm trying ADB, but it won't stay connected. Flicks on right at the end of the loading process and then shuts down. It really sucks.

Shelly, shoot me a pm... i'll give ya my phone number and we'll work on getting it going.

Sorry if this is redundant, but in very basic troubleshooting have you tried charging your Nook? It probably is more complicated/serious than a low battery, but it wouldn't hurt to rule it out.

I finally did get it to charge to green light. Didn't make a difference. I can get it to hang sometimes when it's trying to get into CWR. And it will stay on the Boot Menu.

Just a side note, I have another NC that I've had since Jan. Autonootered, Manual Nootered, CM7ed, brought back from the dead many a times.
Dizzy Den - am shooting you a message shortly. Thanks.

Has this been solved? If yes how?
Could you find a solution to your problem?
I'm having the same issue now. Bought a Nook Color in November, Autonooted, flashed recovery from ROM Manager, flashed CM 7.1.0 internally from downloaded ZIP files via ROM Manager, was working just fine for a week, stable, fast, perfect. Overclocked to 1200 MHz after a few days which made the experience even nicer.
Then installed and started Google Maps which didn't work - the Nook turned off on launch of Google Maps app.
I had set Wifi to "stay on all the time" beforehand (which might have been bad because it creates Sleep of Death syndrome as i now know).
Now when i turn it on it shows "Loading" for 7 seconds and then the screen turns off. This is when booting CM, when booting the internal recovery (shows "loading recovery" for 7 seconds) and when booting from any SD card image (i've tried at least 10 different bootable SD card images, different cards and different card readers).
It recognizes and tries to boot off SD cards - i get different "Loading" screens depending on the image, honey-colored for a honeycomb image, with two skulls for a recovery, ... So that works.
The nook seems to be in some kind of "on" state because i need to hold the power button to turn it off before i can get it to boot again.
I can get to the boot menu as you could, but booting from there doesn't do anything at all. So the hardware seems to be OK because the boot menu itself works well and for more than 7 seconds.
I can charge it and it goes to a green light so it's no battery issue.
The nook does not show up on USB - well once it did for a second but that was it.
I even tried to let the battery run completely empty so internal registers can get reset - didn't change anything.
Help! Is it bricked now?
Going to a B&N store isn't an option btw - the next one is 6500 km from here.
(This is the first time i ever ask for help on a forum. I am running a ZTE Blade with CM7 just fine, and I've been stuck often enough but always found a solution myself...)
Gunnar

Have you guys tried this:
http://forum.xda-developers.com/showthread.php?t=1308304
Or completely restoring it to stock:
http://mrm3.net/nook-color-recover-any-bricked-device/

Tried, can't get far enough
Kingdruid, thanks, yes i've tried both of those links - sadly they don't help at all because i can't even boot SD card recovery images...
I tried various recovery images including the newest clockworkmod, but i am still stuck They all work for 7 seconds only.
So yes, a nook can actually be bricked it seems.
G.

tralulu said:
Kingdruid, thanks, yes i've tried both of those links - sadly they don't help at all because i can't even boot SD card recovery images...
I tried various recovery images including the newest clockworkmod, but i am still stuck They all work for 7 seconds only.
So yes, a nook can actually be bricked it seems.
G.
Click to expand...
Click to collapse
When you overclocked it, did you notice it getting hotter than usual? I wonder if it was due to the overclocking. All the users I see with unrecoverable nooks is after they overclocked.

No, i did not notice much heat. And it was working well in its overclocked state for a few days.
Do you think it's CPU is fried now?

tralulu said:
No, i did not notice much heat. And it was working well in its overclocked state for a few days.
Do you think it's CPU is fried now?
Click to expand...
Click to collapse
I own 4 of them so I would prefer the term "Unbrickable", but at this point I'm not really sure.

Try 8 failed boots and see if you can get into recovery to reset to factory.

cant get it working
so first noob post
i used this thread to root my nook color
http://forum.xda-developers.com/showthread.php?t=1000957
problem is i have followed the steps and re done it about 5 times and every time i turn on the nook it goes right to read forever and runs the stock OS
nook 1.2 brand new, and 8gig SD card
when i boot i hold the power button for the 5 seconds, am i missing something?

tntviper1 said:
so first noob post
i used this thread to root my nook color
http://forum.xda-developers.com/showthread.php?t=1000957
problem is i have followed the steps and re done it about 5 times and every time i turn on the nook it goes right to read forever and runs the stock OS
nook 1.2 brand new, and 8gig SD card
when i boot i hold the power button for the 5 seconds, am i missing something?
Click to expand...
Click to collapse
how did you write the image to the SD card? you can't just do the write button in winimage, you have to use the "convert virtual hard disk image to drive" or something... really should be mentioned in the n00b guides.
Sequence in winimage:
Disk->Use disk (whatever your sd card is)
Disk->Restore virtual hard disk image on physical drive (select the image you're trying to write)
Click ok on the warning and you should have a boot disk
"Write disk" is prominent but just copies the files to the disk, not resize or make it bootable.

Nope - no change
DizzyDen, nope, 8 failed boots does nothing. Just fails 8 times, no restore.

[Q] eMMC fail?

Is there anyway to check if the eMMC fails?
I was using ICS for several days, and I powered on the Nook after it was out of power one nite. Suddenly, it stops at the Cyanogen "loading..."
I'ved tried to boot into Recovery, and it stops at the Cyanogen "loading into recovery" ..
After several tests and trying, I finally use bootable uSD to boot into CWR 3.0.2.8, and now it shows can't mount boot/system/data if I try to format these partitions.
I am wondering if the eMMC is broken, and how can I fix it.
Appreciated and sorry for my bad English.

chinian said:
Is there anyway to check if the eMMC fails?
I was using ICS for several days, and I powered on the Nook after it was out of power one nite. Suddenly, it stops at the Cyanogen "loading..."
I'ved tried to boot into Recovery, and it stops at the Cyanogen "loading into recovery" ..
After several tests and trying, I finally use bootable uSD to boot into CWR 3.0.2.8, and now it shows can't mount boot/system/data if I try to format these partitions.
I am wondering if the eMMC is broken, and how can I fix it.
Appreciated and sorry for my bad English.
Click to expand...
Click to collapse
Try again with CwMR 3.2.0.1

votinh said:
Try again with CwMR 3.2.0.1
Click to expand...
Click to collapse
Same. (using 1gb_clockwork-3.2.0.1-eyeballer.img)
The error message:
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
Formatting /boot
Error mounting /boot!
Skipping format...
Done.
BTW, Nook won't boot directly from uSD, I have to use boot menu to choose booting from uSD card.

I too need help but I formated my emmc boot partition and gets stuck here won't power off either.. anybody we need some help please
Sent from my Inspire 4G using Tapatalk

Fixed it f'in yes!
All i did was followed this
http://forum.xda-developers.com/showthread.php?t=1448186
it booted into new recovery blue one then i took the sd out and rebooted into recovery and it worked i have no idea what happend i did not flash any thing to my knowledge
hope this help someone as dumb as me!

Ok so mine will not boot into rom. Every time I turn it on it goes strait to cwrm I can get it to boot select by holding down home but if I try to select to boot from emmc it still goes to cwrm and every time I go in to boot select it wants to select sd I do not have a sdboot I have always ran every rom from the reg emmc. Also I was running the nightly ics cm9. Please someone help me out with this please.
dincdoes.me said:
All i did was followed this
http://forum.xda-developers.com/showthread.php?t=1448186
it booted into new recovery blue one then i took the sd out and rebooted into recovery and it worked i have no idea what happend i did not flash any thing to my knowledge
hope this help someone as dumb as me!
Click to expand...
Click to collapse
Sent from my PG06100 using Tapatalk

dincdoes.me said:
All i did was followed this
http://forum.xda-developers.com/showthread.php?t=1448186
it booted into new recovery blue one then i took the sd out and rebooted into recovery and it worked i have no idea what happend i did not flash any thing to my knowledge
hope this help someone as dumb as me!
Click to expand...
Click to collapse
You are lucky. I am still stuck as usual.
Help~~ I can boot into CWM on uSD card, but can't mount /sdcard

I don't know what happens I was stuck like you then loaded that post onto a 4gb SD and hoped to boot into a Tom but recovery posted up then all I did was push reset and bam miui booted [previous ] rom and configuration I don't know if what I did really helped but all I know was it was bootlooping at cyanogenmods logo with booting symbol. Since its my wife's tab I just through 1.4.1 nook rom so she's happy now.
Did you try what I did to see if it would help out at all and do anyone know what is going on with this flashing was never this weird 6months ago when it was mine running honeycomb..
Sent from my A500 using Tapatalk

dincdoes.me said:
I don't know what happens I was stuck like you then loaded that post onto a 4gb SD and hoped to boot into a Tom but recovery posted up then all I did was push reset and bam miui booted [previous ] rom and configuration I don't know if what I did really helped but all I know was it was bootlooping at cyanogenmods logo with booting symbol. Since its my wife's tab I just through 1.4.1 nook rom so she's happy now.
Did you try what I did to see if it would help out at all and do anyone know what is going on with this flashing was never this weird 6months ago when it was mine running honeycomb..
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
Yes, I did try the method you mention. The only thing I got was a blank screen.
I tried the "fdisk" method, and found that there is no block device, so I think the hardware (eMMC) was broken. Just need to confirm that.
Thx anyway.

Fixed bootloop, back in bootloop. Crap.

How it started: I use a NC with mirage 7.2 flashed to the emmc in my car. It runs Torque to display engine data, and is switched in and out of sleep with the ignition. Two days ago I started the car and got the low-battery "exclamation point" icon thing, so I figured the charging cable must have come loose*. I took it all out and left it charging overnight, but when I went to boot it in the morning it was stuck in a cyanoboot loop. I couldn't power the device down or enter emmc recovery. When I completely unplug the NC I can't do anything, the screen remains black no matter what I press, except it flashes white every 5 seconds or so. If I manage to plug it on, get to the cyanoboot loading screen and unplug it while holding the power button down at the right time, I can sometimes get it to power off completely.
What I have done so far: Tried various recovery SD methods, none of which worked. Wiped cache/data/system, factory reset, tried loading 7.2 again over the top of whatever is left in there, lol. Basically after it first happened I probably made a big mess of the file system in a desperate attempt for some kind of stability. I tried this recovery SD: http://forum.xda-developers.com/showthread.php?p=25354258#post25354258 ; section A10, and managed to get into CWR. I've never felt such joy in my life.
What finally worked: I repaired the 2nd partition with the help of this thread: http://forum.xda-developers.com/showthread.php?t=1759558 . I did not repair or format any other partitions though. After repairing the partition, I did a factory reset and flashed mirage 7.2 and gapps back onto the emmc. Before I rebooted, I swapped a clean SD in but it still went back into the bootloop..BUT...when I put my recovery SD back in it booted into 7.2! I set everything up and was happy to have it running again. Battery level was at 88%.
What made it stop working: I was testing to make sure the NC would enter sleep mode when disconnected from power, so I unplugged it. Everything went black, no "sleeping" screen, just a hard shut-down. I powered it back on and I'm now back in a cyanomod boot loop.
So...any ideas? If there's a way to completely wipe and reinstall everything I'm OK with that. I've never used ADB before but I'll give it a shot if someone can lead me in the right direction. Thanks in advance.
*I'm using a 2amp USB car charger with a modified data-looped cable for a/c style charging in the car. I know the supplied nook cables are prone to going bad, and this may have happened with the vibration of the car and all. Not sure.

Little update: I can sometimes get into TWRP by selecting the "normal emmc" boot from the cyanoboot screen. I don't understand how that's possible, as I flashed that on my original install of 7.2 months ago. Guess I need to figure out how to completely wipe and re-flash everything.

SPLEclipse said:
Little update: I can sometimes get into TWRP by selecting the "normal emmc" boot from the cyanoboot screen. I don't understand how that's possible, as I flashed that on my original install of 7.2 months ago. Guess I need to figure out how to completely wipe and re-flash everything.
Click to expand...
Click to collapse
To completely wipe and reflash everything, do the other two zips that you said you did not do from my partition repair thread.
Sent from my Nook HD+ running CM10 on Hybrid SD

No luck with that. Here's exactly what I did, so tell me where I might be going wrong:
1) Burned an image of the 6.1.0.2 recovery onto SD, then put the (2) recovery zips and the (1) format zip as well as the mirage 7.2 and gapp zips onto the SD.
2) Booted into cyanoboot, it took a few tries to get out of the loop and into CWM. Note that I can't power on at all unless it's plugged in. As soon as I unplug the NC it turns of except the screen will flash every 5 seconds or so. Once I got into CWM, I installed both partition repair zips, starting with the 1-4-5-6-7-8, followed by the 2. Rebooted. There were no errors at all.
3) Again it took a few tries to get out of the bootloop and into CWM. Installed the format zip and rebooted again.
4) Installed Mirage 7.2 and gapps and restarted, but went straight back into bootloop. I know that the rom requires a clean formated SD card, so before rebooting after I installed the zips I took out the SD card, formatted with SDFormatter and reinserted in into the NC.
I'm beginning to think this is something hardware related. :crying:

Sounds like there might be some bad data in emmc, I had this problem before and fixed it by formatting everything , even emmc and wiping dalvik cache. Then boot off a SD card using the latest cwm.
Sent from my NookColor using xda app-developers app

SPLEclipse said:
No luck with that. Here's exactly what I did, so tell me where I might be going wrong:
1) Burned an image of the 6.1.0.2 recovery onto SD, then put the (2) recovery zips and the (1) format zip as well as the mirage 7.2 and gapp zips onto the SD.
2) Booted into cyanoboot, it took a few tries to get out of the loop and into CWM. Note that I can't power on at all unless it's plugged in. As soon as I unplug the NC it turns of except the screen will flash every 5 seconds or so. Once I got into CWM, I installed both partition repair zips, starting with the 1-4-5-6-7-8, followed by the 2. Rebooted. There were no errors at all.
3) Again it took a few tries to get out of the bootloop and into CWM. Installed the format zip and rebooted again.
4) Installed Mirage 7.2 and gapps and restarted, but went straight back into bootloop. I know that the rom requires a clean formated SD card, so before rebooting after I installed the zips I took out the SD card, formatted with SDFormatter and reinserted in into the NC.
I'm beginning to think this is something hardware related. :crying:
Click to expand...
Click to collapse
It is possible that your partition table is messed up. The only way to find out is to boot to recovery, connect your USB cable to the PC and run ADB. It is also possible to make a CM bootable SD and use terminal emulator to check it out.
Once you get ADB shell or terminal emulator working, type the following command:
fdisk -l /dev/block/mmcblk0
It should say 965 cylinders, 4 heads, 63 sectors.
If it does not, we need to do a manual repair.
You can also abandon emmc and just run off SD.
Sent from my Nook HD+ running CM10 on Hybrid SD

[Q] Cant flash any new firmware

Hi guys,
I have problem with my Lenovo Thinkpad Tablet. One day it just stopped working and get stuck on Lenovo logo on start. I tried to use recovery mod (pushing VOL UP several times during start), it says that it cant mount /cache directory. I tried Wipe cache and Factory reset options, non worked, still same problem. So I googled and found, that I am not the only one with this problem. I found and read this http://forum.xda-developers.com/showthread.php?t=2318140 and then this http://forum.xda-developers.com/showthread.php?t=1745450 and flashed CWM on partition 6, so now I have CWM-based Recovery (v6.0.1.2). I downloaded CyanogenMod (CM10 Alpha 0.8.1), copied to my SD Card (formated as FAT32) and tried Install zip from sdcard -> Choose zip from external sdcard. But I get E: Cant mount /extern_sd/ and I am stuck.
Tried to google this, but I found only alternative recovery mod (TWRP), but it cant be used for my device (at least I think so, since Lenovo Thinkpad Tablet is not listed in supported devices list).
Can you give me any pointers what to do next? I am kinda lost now

You need to re-format the external SD-Card on a computer, reload your files and then try again on the Tablet.
The tablet cannot access the card, it isn't your fault. Happens more often than you think. Just make sure you back up your sd-card contents before format.

pwstein said:
You need to re-format the external SD-Card on a computer, reload your files and then try again on the Tablet.
The tablet cannot access the card, it isn't your fault. Happens more often than you think. Just make sure you back up your sd-card contents before format.
Click to expand...
Click to collapse
Thanks for reply mate, I have tried this three times, even with another SD, still getting the same error -> "Cant mount /external_sd/", my SD is formated as FAT32 and has only CM zip on it. I can read it in my android phone and computer with no problem, but in tablet it isnt working

Shoot. Sorry that wasn't any help.
Have you tried booting to Dev mode and then rebooting or pressing the battery disconnect button?
My thought is to try to bust it out of a bad funk.

pwstein said:
Shoot. Sorry that wasn't any help.
Have you tried booting to Dev mode and then rebooting or pressing the battery disconnect button?
My thought is to try to bust it out of a bad funk.
Click to expand...
Click to collapse
Hmm, I have not, how can I do that?

The battery disconnect is the tiny, recessed, round button under the Sim Card/SD Card flap. With no charger connected, use a pen tip or paper clip. This completely (albeit temporarily) disconnects the battery and is the ultimate "shut down".
Dev mode - I should have called it Bootloader mode. From Battery Disconnect shut down, Hold Rotation button and press Power button for approx 2 seconds. You'll see that the red light on the back will light, but you'll likely not see anything on the screen. This is used when managing your device from a terminal on a different machine while connected via USB. Anyways, nothing I recommend to do here. Just forcing the device to go into other modes might help your issue.
I would use the battery disconnect button again to exit bootloader mode, or else long-holding the power button should do it.

Hi Pirozek
Since you already flashed CWM on partition 6, I guess you already have used nvflash and your bootloader is unlocked.
There was some discussion on flashing the other partitions of the tablet here "Can I reflash Lenovo thinkpad from NVFlash? Comands pls ?". A forum member used to share the original partition files but are not available anymore.
I don't have much experience using nvflash, but I think that you have a chance to fix it since you have your bootloader unlocked, we just need to get the images files.
Regards