I have a Nook Tablet 16GB. It won't even power on to the "n" logo screen unless there is a CWM SD Boot card installed. I get mount errors once inside CWM.
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/
I've tried the Factory Restore (repart.img) and it runs through and tells me the device will shutdown in 5 seconds. (The other times I've used this it sits at a green check mark until I shut it down manually) This doesn't resolve the issue or make any changes at all.
I've tried Adam's Ubuntu method and the device boots to the SD card but sits at a blank screen after a few seconds and does nothing, even when left on over night. This doesn't resolve the issue or make any changes at all either.
I can connect to the device in ADB and the plan was to use parted to fix some partitions using Veronica's methods, but when I run the parted /dev/block/mmcblk0 print command no partitions are found at all on the device. I'm never prompted to fix any partitions either. The only thing it sees in the ext sd card partition. In the past when I've done this it shows 11 partitions with some details. This time it shows nothing. I am unable to find any information anywhere as to what to do next.
It is as though the internal SD Card (memory/hard drive whatever you call it) isn't working or detected by the system any longer.
Does anyone have any recommendations on what to try next? Please help!
I'd suggest burning a CM10.x pre-made SDcard image (e.g., cm_acclaim_10.1_21APR2013_HD_SDC_IMG.7z from Succulent's repo http://iamafanof.wordpress.com/2013/02/18/cm10-1-jellybean-android-4-2-2-for-nook-tablet-0218/) and see if your NT can successfully boot and run a ROM from SDcard. If it does then you can proceed to restoring stock ROM (or flashing CM10) internally on emmc.
Also, refrain from reformatting any partition (other than possibly /cache, /system, /data, if you have good reason to do so and know what you're doing), as you risk making the problem worse -- see http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31.
digixmax said:
I'd suggest burning a CM10.x pre-made SDcard image (e.g., cm_acclaim_10.1_21APR2013_HD_SDC_IMG.7z from Succulent's repo http://iamafanof.wordpress.com/2013/02/18/cm10-1-jellybean-android-4-2-2-for-nook-tablet-0218/) and see if your NT can successfully boot and run a ROM from SDcard. If it does then you can proceed to restoring stock ROM (or flashing CM10) internally on emmc.
Also, refrain from reformatting any partition (other than possibly /cache, /system, /data, if you have good reason to do so and know what you're doing), as you risk making the problem worse -- see http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31.
Click to expand...
Click to collapse
I made an SDCard using Succelent's repo and was able to boot to the Cyanoboot Bootloader but a few seconds later it just went to a blank screen. I rebooted and could get into recovery by holding the "n" button and selecting that. When I select to boot from SDC it just goes to Bootloader and then goes blank. It never boots into the OS.
I never mess around with partitions and I'm not sure how this thing got this way. I purchased it from eBay as a tablet for my daughter. It did say the device was bricked but that the hardware was okay. I've seen bricked devices in the past and the repart.img (Factory Reset) has always resolved the problem. I have a Nook Tablet that my son has been using so I've become pretty familiar with the basics of rooting, loading CWM, TWRP, Cyanogenmod, etc. But I've never seen it were I get mounting errors inside of CWM and am unable to flash anything. It won't even mount the external SDCard once inside CWM.
Not sure what to do and I hate to give up on this. Any help would be greatly appreciated.
Assuming that SD-based CWM is functional, you should try flashing flash_kernel_acclaim_30MAR2013_HD_SDC.zip under the heading "Flash this if your NT doesn’t boot newer kernel" in the SDC image section of http://iamafanof.wordpress.com/2013/02/18/cm10-1-jellybean-android-4-2-2-for-nook-tablet-0218/.
Also, you should try "wipe /cache" while in SD-based CWM recovery to see if that would take care of the /cache related mounting errors you encountered.
This happened to me last year. There is a post in development section about fixing partition table by So****e. It's the last resort, but worked for me.Also, Adam Outlers Ubuntu method loses your serial number, gone forever. Good luck
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
DEjaVu
Happened to my first nookT not to long ago....It died but the best advice I can give has already been given try not to erase more stuff. Digimax helped me not to long ago. Make sure you format your sdcards correctly and if you can flash a recovery or boot into it you should be able to use one of Succulents cards. Good luck
digixmax said:
Assuming that SD-based CWM is functional, you should try flashing flash_kernel_acclaim_30MAR2013_HD_SDC.zip under the heading "Flash this if your NT doesn’t boot newer kernel" in the SDC image section of http://iamafanof.wordpress.com/2013/02/18/cm10-1-jellybean-android-4-2-2-for-nook-tablet-0218/.
Also, you should try "wipe /cache" while in SD-based CWM recovery to see if that would take care of the /cache related mounting errors you encountered.
Click to expand...
Click to collapse
I tried to download the file you suggested, but the actual file isn't there any longer. When I click on the download link it takes me to GOO to download it, but said file can't be found. I also tried wiping my cache partition again from inside cwm, but no luck. Still getting the mount errors.
I believe the real issue is that my device doesn't see /dev/block/mmcblk0 (or rather is sees it as the external SD card). there is no /dev/block/mmcblk1 either. I thought perhaps the internal and external were swapped, but that doesn't appear to be the case. So since the device can't recognize the internal SD card I don't think I will be able to get anything to flash until I get that resolved first. I'm certain that is why Adam Ubuntu fix and Meg's reprt.img aren't working.
Probably the only way to do that, if it is even possible, is to do it through ADB. Veronica has a thread that shows how to recreate all of the partitions, but when I attempt to do that it doesn't see the internal storage at all so I can't even get started.
I really hate giving up on anything so I will keep trying as long as it takes if I know it is possible to fix this, but I'm not sure what steps to take next to try and get the internal storage recognized.
For all I know it could be a permission issue.
Do you know any commands I can run from ADB Shell to try and get the internal storage recognized?
When I run a list command from ADB shell I get the following:
~ # ls
ls
boot fstab.acclaim sd-ext
bootdata init sdcard
cache init.rc sys
data internal_sd system
datadata proc tmp
default.prop recovery ueventd.acclaim.rc
dev res ueventd.goldfish.rc
emmc rom ueventd.rc
etc root
external_sd sbin
~ #
So it looks like the internal storage is working after all and I can get into some of these directories and files and CAT or TAIL them. Perhaps the MBR is messed up or something?
skelnik said:
I tried to download the file you suggested, but the actual file isn't there any longer. When I click on the download link it takes me to GOO to download it, but said file can't be found.
...
Click to expand...
Click to collapse
You can try one of Succulent's more recent 10.2 builds listed at http://iamafanof.wordpress.com/2013...id-4-3-for-nook-tablet-imgsdc-boot-09aug2013/ which he uploaded onto Media Fire: "cm_acclaim_10.2.0-RC0_13OCT2013_HD_SDC_IMG.7z (mirror)".
You might also want to take a look at Succulent's recovery tools (in particular flash_stock_1.4.2.zip) at https://github.com/succulent/acclaim_recovery_sdcard.
Related
So I just finished putting the final tweak on a re-install of Vegan Ginger. My previous install had some issues with long boot times and the Gallery was not synchronizing with my Picasa Web Photos. The last step in the process was wiping the external SDcard which was complaining from Ginger since I formatted originally to FAT32 on my PC and was unsure of the "preferred" format for Android/Gingerbread. So I went into settings, and under sdcard2 selected "Erase". I then attempted to mount and got some errors regarding the sdcard was empty or not formatted, so I selected "Format". I attempted to re-mount again and got the same error. So I figured that I would give the CWM format a try and rebooted into CWM. I then selected "format sd-ext" and CWM complained that apps2sd did not exist. I then rebooted the tablet through the CWM main menu.
Somehow in this process my internal sdcard was formatted!
The next boot, Vegan Ginger displayed the G Tab Devs and Vegan Launch screen but would boot loop about 5 times until the screen went black.
I was able to boot into ClockWorkMod (CWM) and attempts to mount /data or /sdcard result in:
mount /sdcard
Code:
Can't mount /sdcard
Can't mount /dev/block/mmcblk3p1 (or /dev/block/mmcblk2p1)
(No such file or directory)
mount /data
Code:
Can't mount DATA:!
Can't mount /dev/block/mmcblk3p1 (or /dev/block/mmcblk2p1)
(No such file or directory)
I attempted to do a restore through CWM which resulted in a failure.
Any suggestions on how to get back to a running system? My guess is the following:
format data
format sdcard
The following information would be very helpful:
Is there any chance recovering the current system?
Is it possible to do a "system snapshot" of my tablet to avoid this issue in the future?
What is the preferred Android external SD card format?
Thanks!
Run nvflash from the dev section. There is nothing there to save anymore
I had this same issue with a 32gb micro sdcard formatted in fat32. After finally getting things back in order with nvflash/wipe/reload, Im hesitant to try again. Any idea on the cause or how to prevent it from happening?
brianafischer said:
Is it possible to do a "system snapshot" of my tablet to avoid this issue in the future?
Click to expand...
Click to collapse
In CWM, do a backup (this is the nandroid backup mentioned often here on xda)
When you boot into android, copy the backup file OFF the device, and onto a desktop PC, or a USB flash drive - anywhere but onto any storage that is on the gtab.
Repeat both those steps any time you're about to make major changes, or do any formatting, or otherwise play with sharp objects near your gtab.
When you screw the pooch, you can always copy your latest backup back to the backup directory on the gtab, and then restore from CWM. You may need to nvflash first to get the thing into some sane state, of course. But you'll have the image which will save lots of setup time after...
Maybe some of you guys have figured this out already but it's probably important to note for people developing custom recovery or boot ROMs.
There is a partition on the internal flash named "bootdata" that stores a files named BCB and BootCnt. The secure bootloader updates BootCnt on every non-sdcard boot and if it gets too high it will automatically boot into the recovery partition instead of the boot partition. So, if you're making any custom ROM to be run from the internal flash then you'll want to reset that file in a boot script somewhere. The shell command "dd if=/dev/zero of=/bootdata/BootCnt bs=1 count=4" would do it (Assuming you've mounted the bootdata partition )
The BCB file is similar in that if the secure bootloader boots into the recovery partition for any reason, it will write to that file and will always boot into the recovery partition until that file is cleared. The shell command to clear that file is "dd if=/dev/zero of=/bootdata/BCB bs=1 count=1088"
The bootdata partition just contains a standard vfat filesystem so you just mount it normally.
And for the love of your god do not delete those files! If you do then booting from internal memory will continue to boot into the recovery partition until they are replaced. You would be able to boot from an SD card to replace them though.
bauwks said:
Maybe some of you guys have figured this out already but it's probably important to note for people developing custom recovery or boot ROMs.
There is a partition on the internal flash named "bootdata" that stores a files named BCB and BootCnt. The secure bootloader updates BootCnt on every non-sdcard boot and if it gets too high it will automatically boot into the recovery partition instead of the boot partition. So, if you're making any custom ROM to be run from the internal flash then you'll want to reset that file in a boot script somewhere. The shell command "dd if=/dev/zero of=/bootdata/BootCnt bs=1 count=4" would do it (Assuming you've mounted the bootdata partition )
The BCB file is similar in that if the secure bootloader boots into the recovery partition for any reason, it will write to that file and will always boot into the recovery partition until that file is cleared. The shell command to clear that file is "dd if=/dev/zero of=/bootdata/BCB bs=1 count=1088"
The bootdata partition just contains a standard vfat filesystem so you just mount it normally.
And for the love of your god do not delete those files! If you do then booting from internal memory will continue to boot into the recovery partition until they are replaced. You would be able to boot from an SD card to replace them though.
Click to expand...
Click to collapse
Yup. On the NookColor these had the same functions. Lived on /rom instead of /bootdata however.
Note: My CWM image doesn't probably handle BCB or bootcnt yet (I do in my CM9 image but that is another thing )
nemith said:
Yup. On the NookColor these had the same functions. Lived on /rom instead of /bootdata however.
Note: My CWM image doesn't probably handle BCB or bootcnt yet (I do in my CM9 image but that is another thing )
Click to expand...
Click to collapse
My Ubuntu image does not mount this partition.
bauwks said:
Maybe some of you guys have figured this out already but it's probably important to note for people developing custom recovery or boot ROMs.
And for the love of your god do not delete those files! If you do then booting from internal memory will continue to boot into the recovery partition until they are replaced. You would be able to boot from an SD card to replace them though.
Click to expand...
Click to collapse
Yep-- this is all taken care of in cm9
Update: I don't think you mentioned, but for completeness, there's also the serial file in /rom at devconf/DeviceId that will trigger a rom reformat if it goes missing. there are also some edge conditions that will trigger recovery/flashing such as the presence of certain update.zip files on SD. Also SD boots are treated differently by default, don't increase the boot count, etc. In short, this is very similar to how NookColor works with the added disadvantage of having to deal with, rather than simply ignore or remove, these various "go to recovery' conditions.
I can verify that Bauwks script works and allows internal booting without a bootloop.
Nemith, if you find the time can you add something like this to your CWM recovery.img? I think just adding the /bootdata mount and dd calls to the init.rc file should work. I was going to build my own CWM .img but figured you already had the source code handy.
I'de like to dabble in a CM7 port soon, while CM9 and Ubuntu ports are in-work
Thanks for all your hard work guys!
CWM recovery bootloop
bauwks said:
And for the love of your god do not delete those files! If you do then booting from internal memory will continue to boot into the recovery partition until they are replaced. You would be able to boot from an SD card to replace them though.
Click to expand...
Click to collapse
I flashed cm9 alpha 0.2 on my nook tablet using the nook tablet recovery apk. It booted into cyanoboot, however it had an error message that said disc majic error. I noticed I had put the wrong boot image on my sd card from the alpha 0.1. I rebooted 8 times and booted into cwm. Now in cwm I flashed a backup of my tablet. I then made the common mistake of clicking reboot recovery. Then trying to fix the bootloop into cwm recovery while unaware of the sevarity of what I was doing I went into mounts and storage and formated each bootdata, cache, data, emmc, rom, and system. I just restored my backup again and now I know what I need to do. My stock Nook recovery was overwriten when I clicked reboot recovery. Also I formated my rom folder and that might have contained my serial number and info.
I basicaly deleted my partions. while stuck in the cwm boot loop. Can you please send me or send me the link to a step by step way that I can get my nook tablet 16gb stuck in the cwm boot loop back to normal.
I tried using fastboot but I dont know the commands to open it. Also I dont know how to use adb either. I have a 2gig, and a 256 mb micro sd. I have a windows pc. Can you show me step by step how to restore those partions, how to do it on adb or fastboot, or the update zip method. I need help as soon as possible. Thanks.
Its similar to this
This seems like the only place folks are looking at bcb in much detail, so I thought I'd post an observation: on the simple touch, if you boot from noogie after issuing an "erase and deregister" command from the OS, the bcb file contains command strings.
I don't know what reads the strings, but after erase and deregister, bcb seems to be used to tell the device to run recovery:
recovery --wipe_data
is an ascii string from bcb on a deregistered and not yet rebooted glowworm - I put the noogie disk in, did the erase and deregister, then dumped the partitions once it came back up.
the command flags available in recovery as of cupcake are documented at
http://www.netmite.com/android/mydroid/cupcake/bootable/recovery/recovery.c
Just wanted to bump this so more people know about it, because I didn't and I reformat my /bootdata.
Can anyone make an image of it for restore purposes?
An image of /factory would be nice as well But less important as we're all (likely) using CM.
edit
Actually disregard this.. I have the nook hd+, but the /bootdata format info will probably be handy for any nook device.
Don't format bootdata or factory!
roustabout said:
This seems like the only place folks are looking at bcb in much detail, so I thought I'd post an observation: on the simple touch, if you boot from noogie after issuing an "erase and deregister" command from the OS, the bcb file contains command strings.
I don't know what reads the strings, but after erase and deregister, bcb seems to be used to tell the device to run recovery:
recovery --wipe_data
is an ascii string from bcb on a deregistered and not yet rebooted glowworm - I put the noogie disk in, did the erase and deregister, then dumped the partitions once it came back up.
the command flags available in recovery as of cupcake are documented at
http://www.netmite.com/android/mydroid/cupcake/bootable/recovery/recovery.c
Click to expand...
Click to collapse
pbassjunk said:
Just wanted to bump this so more people know about it, because I didn't and I reformat my /bootdata.
Can anyone make an image of it for restore purposes?
Click to expand...
Click to collapse
To fix the Recovery Boot Loop caused by invalid/missing BCB and BootCnt in /bootdata, flash Succulent's flashable_fix_bootloop.zip posted at his blog http://iamafanof.wordpress.com/2013...-1-jellybean-sdcard-img-for-nook-tablet-0110/ (see under heading "I am stuck in a recovery boot loop?").
An image of /factory would be nice as well But less important as we're all (likely) using CM.
Click to expand...
Click to collapse
/factory contains a backup copy of stock ROM as well as a backup copy of the device data in /rom partition (romdata.zip), the latter includes data that is unique to each Nook (such as MAC address, security certificate, etc.) and hence is not replaceable with a copy from another Nook.
...
Don't format bootdata or factory!
Click to expand...
Click to collapse
Nor /romdata. See http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 for more info.
I created a flashable zip as well, which should reset that partition to a stock (zero-count) state. Hopefully it's not unique per device (I don't think it is, as I've used this successfully on two distinct devices.)
Is a fix being baked into any official roms, CM and the like? I don't mind the workaround via scripting, but the two I bought and modded I gave as gifts, so when they break (they both have) I definitely hear about it and receive the units back again for fixing.
ZIP is attached. Please let me know if it works or doesn't work for you, should you end up using it.
weasel5i2 said:
I created a flashable zip as well, which should reset that partition to a stock (zero-count) state. Hopefully it's not unique per device (I don't think it is, as I've used this successfully on two distinct devices.)
Is a fix being baked into any official roms, CM and the like? I don't mind the workaround via scripting, but the two I bought and modded I gave as gifts, so when they break (they both have) I definitely hear about it and receive the units back again for fixing.
ZIP is attached. Please let me know if it works or doesn't work for you, should you end up using it.
Click to expand...
Click to collapse
Having trouble with the /bootdata/BCB/ and my nook hd+ booting into recovery. Am I just supposed to flash the fix to the SD card boot partition?
tinkering said:
Having trouble with the /bootdata/BCB/ and my nook hd+ booting into recovery. Am I just supposed to flash the fix to the SD card boot partition?
Click to expand...
Click to collapse
You might want to see leapinlar's tip #10 in his post http://forum.xda-developers.com/showpost.php?p=35811322&postcount=1 for the Nook HD/HD+.
digixmax said:
You might want to see leapinlar's tip #10 in his post http://forum.xda-developers.com/showpost.php?p=35811322&postcount=1 for the Nook HD/HD+.
Click to expand...
Click to collapse
Thanks for the link to leapinlar's post. That helps me to understand the problem and fix a bit better. I didn't see the zip that seemed to fit my situation on his post. I did a SD install non-rooted and I see only only emmc fixes on his post. I tried your fix with these steps and I must have done something wrong. Maybe you could point me in the right direction.
DL, unzip, write image to sd using PC(could only write the .img, don't know what to do with the folder) , put SD into nook HD+, try to boot= no boot
Does the device have to be rooted to flash the repair zip? I don't think I am utilizing the fix properly.
tinkering said:
...
DL, unzip, write image to sd using PC(could only write the .img, don't know what to do with the folder) , put SD into nook HD+, try to boot= no boot
Does the device have to be rooted to flash the repair zip? I don't think I am utilizing the fix properly.
Click to expand...
Click to collapse
No, the device does not have to be rooted to get flashed.
If this is your first time trying to boot off SD, it's possible that your HD+ is one of the units that have difficulty booting off SD card -- see http://forum.xda-developers.com/showthread.php?t=2288688.
Is your device still on stock ROM and stock Recovery?
digixmax said:
No, the device does not have to be rooted to get flashed.
If this is your first time trying to boot off SD, it's possible that your HD+ is one of the units that have difficulty booting off SD card -- see http://forum.xda-developers.com/showthread.php?t=2288688.
Is your device still on stock ROM and stock Recovery?
Click to expand...
Click to collapse
Sorry, I probably should have updated my last post. I was attempting to flash the repair incorrectly. Unfortunately, I have a new problem and have moved my question to the "[Q][Panic] HD+ won't boot, can access CWM SD but can't mount sdcard or emmc" thread.
The device would boot from SD. Was running CM10.2 and CWM recovery. The trouble I am having now is that I can't flash anything from the SD in CWM recovery because it wont mount the SD. (See details in thread referenced above.)
Thanks
Hello, fellow gTablet users!
I'm kinda newbie here, so first of all my apologies to everyone if that was already asked, 'cause I did some research on the matter and couldn't find all the necessary info for solving my particular issue.
Ok, so here's the deal. I was using my gTab for about half-year now. When I received it, I installed VeganTab-7 Ginger Edition on it (thanks for the devs - very nice ROM!) and it worked flawlessly until yesterday. But then something not good happened and the tablet stopped booting. Now it starts from birds screen, goes on to G-Tabdevs screen, after which VeganTab GingerEd boot screen appears, it has flashing letters for a couple of seconds and then tablet goes black and tries to boot again. I guess it's a boot loop so it's kinda soft brick and I'll have to do wipe data/factory reset through CWM to solve the issue. So this isn't the biggest problem - I've already found all the instructions.
The real problem is that I didn't make backup of my data (guilty!), but I don't want to lose some of it, especially the browser data. I was using Opera Mobile, so I guess that its data should be on /data partition. So I'll need an advice on how I can dump the necessary data before doing factory reset!
I've already tried connecting to desktop, using guide from this (http://forum.xda-developers.com/showthread.php?t=1010943) thread (third method from it), but it didn't work, at least on my Win7 Pro x64 SP1: the tablet shows as removable disk, but I can't access it. I tried to mount /data or /sdcard partitions through CWM recovery menu, but it tells me that it can't find /dev/block/... - I guess that's block device, associated with those partitions. So what are my best options of backuping data?
And the last question: I'll probably install some other ROM just to try something different, but unfortunately I don't remember what loader I have. I'm nearly sure that I installed VeganTab for 1.1, 'cause I did it back in May 2011 and there wasn't one available for 1.2 yet. But just to make sure: how can I find my loader version before I do reset? Or maybe I just have to do the reset and look for it when back on stock ROM?
Seriously, guys, doesn't anybody know how to solve these problems?
Boot into CWM first, then try mounting both /data and /sdcard using the CWM menu. Note down the exact error message displayed in each case. Then connect the USB cable and run these ADB commands on your PC:
Code:
C:\> [B]adb shell dmesg >dmesg.txt[/B]
C:\> [B]adb shell fdisk -l /dev/block/mmcblk3 > fdisk.txt[/B]
C:\> [B]adb shell fdisk -l /dev/block/mmcblk2 >> fdisk.txt[/B]
Post the error messages and those 2 .txt files here.
Thank you for reply, rajeevvp.
When I'm trying to mount /data and /sdcard it says respectively:
Code:
E:Can't mount /dev/block/mmcblk3p2
(No such file or directory)
Error mounting DATA:!
E:Can't mount /dev/block/mmcblk3p1 (or /dev/block/mmcblk2p1)
(No such file or directory)
Error mounting SDCARD:!
Unfortunately I didn't have ADB installed. Now I'm trying to use the guide from here: http://forum.xda-developers.com/showthread.php?t=902860, but fail on step 4, cause there is nothing like "Nvidia harmony" appearing under other devices in my dev manager, just "Nvidia Tegra 2 USB Device" under Disk Drives and "USB Mass Storage Device" under Universal Serial Bus Controllers. I guess these devices are gTablet's internal memory presented as disk drive...
I'll try to install ADB and then write back how it worked.
Interesting error messages. Now I really have to see those text files.
If you're having problems installing ADB on Windows, try using Linux.
Ok, thanks you very much! I'll try that, but unfortunately tomorrow, as it's already too late here.
Btw, I read your post about linux - you're suggesting Knoppix Live CD there. Is it mandatory to use it? I mean I already have PartedMagic live CD burned, maybe I could use it instead...
anary said:
I mean I already have PartedMagic live CD burned, maybe I could use it instead...
Click to expand...
Click to collapse
If sudo and adb work, then no problem.
rajeevvp said:
Boot into CWM first, then try mounting both /data and /sdcard using the CWM menu. Note down the exact error message displayed in each case. Then connect the USB cable and run these ADB commands on your PC:
Code:
C:\> [B]adb shell dmesg >dmesg.txt[/B]
C:\> [B]adb shell fdisk -l /dev/block/mmcblk3 > fdisk.txt[/B]
C:\> [B]adb shell fdisk -l /dev/block/mmcblk2 >> fdisk.txt[/B]
Post the error messages and those 2 .txt files here.
Click to expand...
Click to collapse
Ok, I finally managed to do it. Sorry for the delay.
The files are attached. Did everything how you told me.
Actually I don't think that I understand too much in Android inner mechanics But having looked through these files, I thought that inner sdcard device (mmcblk3) doesn't seem to produce any strange behavior...
Btw, thanks a lot for your advice about using Knoppix - it's really very easy and handy!
anary said:
But having looked through these files, I thought that inner sdcard device (mmcblk3) doesn't seem to produce any strange behavior...
Click to expand...
Click to collapse
You have lost your /data partition altogether. You are supposed to have 2 partitions on that internal SD card: a 14GB FAT32 partition and a 2GB ext3 partition. You only have a single FAT32 partition spanning the entire SD card now.
I may be able to help you get both partitions back if you give me these details:
1. How and when did this happen?
2. Current ROM.
3. Current version of CWM.
4. Did you try to repartition the (internal) SD card recently?
5. Have you ever repartitioned the internal SD card? If yes, then using which version of CWM?
6. After you noticed the problem what steps did you take to fix the problem?
Yeah, I remember I was curious where it stores OS's kernel if all it has is FAT32 partition - now I get it...
Ok, here are the details:
1. I don't really know what has happened, but I guess that it happened when I tried to use tablet like cardreader for microsd card. During that I sort of formatted external sd - maybe that actually was internal memory? I checked through file manager though, and all the files seemed intact...
2. VeganTab GingerEd from this thread: http://forum.xda-developers.com/showthread.php?t=1031250. I'm pretty sure that I didn't install anything except for it.
3. Don't know. But it says ClockworkMod Recovery v2.5.1.1-bekit-0.8 in recovery menu, so I guess its version is maybe 0.8.
4. No I didn't, at least intentionally.
5. I think I did it just once, when installing the ROM. I'm pretty much sure that I used this instructions for repartitioning: http://viewsonic-gtablet-for-dummies.webs.com/repartition.htm (not exactly this, but I did the same as it's written there). To install the ROM I used the instructions from the ROM thread, mentioned above. I didn't whant to do a lot of modding, just wanted the device to work at least better than with stock ROM, so didn't try to change any other low-level things.
6. I just tried to mount partitions through CWM recovery and I tried wiping out cache partition and Dalvik cache. Nothing else.
anary said:
Yeah, I remember I was curious where it stores OS's kernel if all it has is FAT32 partition - now I get it...
Click to expand...
Click to collapse
The OS kernel is not stored on the SD cards. They're stored on a "boot" partition on the NAND flash. And, if the OS was messed up you would get hung up on the initial splash screen (the one with the 3 birds)--you wouldn't go into a boot loop.
1. I don't really know what has happened, but I guess that it happened when I tried to use tablet like cardreader for microsd card. During that I sort of formatted external sd - maybe that actually was internal memory?
Click to expand...
Click to collapse
That's what caused this problem. CWM-2.5.1.1-bekit-0.8 does not work on the external SD card (but, CWM-2.5.1.3 and CWM-4.0.1.5 do).
Did you format the internal SD card using CWM?
I checked through file manager though, and all the files seemed intact...
Click to expand...
Click to collapse
Files where? The internal SD card or the external one? And, how did you check this? After formatting the internal SD card, the very next boot into the ROM would've put you into a boot-loop because the /data partition is missing.
I think I may be able to get stuff from /data, but, everything on /sdcard is most likely gone. (Actually, the files are most likely all there, but, without direct access to the tablet, it's very difficult to get the retrieve any of them.) Just don't touch the tablet until I've figured out the commands you will have to use.
That's what caused this problem. CWM-2.5.1.1-bekit-0.8 does not work on the external SD card (but, CWM-2.5.1.3 and CWM-4.0.1.5 do).
Did you format the internal SD card using CWM?
Click to expand...
Click to collapse
No, I was going to format external SD card and I tried to do it through Android (or maybe VeganTab) menu. I think that doing this, I could accidentally format internal SD, but I'm not sure this could be done from within the OS. During the same logon session I checked files on internal SD with file manager and all of them were where they should have been. So I thought that all was ok. But when I rebooted next time, it wasn't booting... That's why I told you that maybe it was because of formatting.
And just to be clear: I didn't do anything using CWM after it stopped booting, apart from wiping system and Dalvik caches.
Do you have a large capacity micro SD card (anything larger than the maximum amount of data that's currently on the internal SD card) that you can use to save retrieved data into?
rajeevvp said:
Do you have a large capacity micro SD card (anything larger than the maximum amount of data that's currently on the internal SD card) that you can use to save retrieved data into?
Click to expand...
Click to collapse
Yep. Won't be any problem.
anary said:
Yep. Won't be any problem.
Click to expand...
Click to collapse
OK. Format that micro SD to contain a single DOS partition; then we'll proceed.
rajeevvp said:
OK. Format that micro SD to contain a single DOS partition; then we'll proceed.
Click to expand...
Click to collapse
Ok. That's done.
Boot into CWM, go into the "mounts and storage" menu, unmount all mounted partitions, connect the USB cable, and run these commands using ADB--do not back out of that "mounts and storage" menu while we're fixing this. We're trying to see if the data on the current /sdcard partition can be retrieved.
Code:
$ [B]adb shell[/B]
~ # [B]mount -r /dev/block/mmcblk3p1 /sdcard[/B]
~ # [B]ls -l /sdcard[/B]
If the ls listing looks OK, then we force a filesystem check before copying the data to the external micro SD card:
Code:
~ # [B]mount -r /system[/B]
~ # [B]umount /sdcard[/B]
~ # [B]/system/bin/fsck_msdos -f -y /dev/block/mmcblk3p1[/B]
If the listing doesn't look OK, then the data on /sdcard is lost.
Post the exact output of each command.
Ok, mount says this:
Code:
mount: mounting /dev/block/mmcblk3p1 on /sdcard failed: Invalid argument
and ls after that gives no output - I think it shouldn't give any, 'cause I didn't mount anything...
Does this mean I'm screwed?
Try this mount command:
Code:
~ # [B]mount -r -t vfat /dev/block/mmcblk3p1 /sdcard[/B]
The same result.
Hi, complete noob here, will try to explain as best I can. Trying to get cyanogenmod 12.1 booted from SD. This is my first attempt for flashing any ROM on any device. I followed the acclaim tutorial on CM webpage (wiki.cyanogenmod.com...can't post link because I'm a forum noob). I can boot into CWM (v5.5.0.4) but when I go to install zip from sdcard, I get lots of errors. Without copy/paste, I'll do my best to state the important parts:
...
Installing update...
Warning: Nofile_contextscould not detect filesystem for /dev/block/platform/omap/omap_hsmmc.1/by-name/system, assuming ext4
mount: failed to mount /dev/block/platform/omap/omap_hsmmc.1/by-name/system at /system: No such file or directory
unmount of /system failed; no such volume
The error continues with nearly the same thing but for .../by-name/userdata at /data.
It again repeats the error with the /system (same as above)
Error ends with:
script succeeded: result was [0.200000]
Install from sdcard complete.
When I reboot the system, it goes back into stock B&N startup as if the ROM was not updated. No surprise considering the errors. I tried again and this time used CWM to enter "mounts and storage" and manually mounted /data and /system. The error for /data went away but the /system errors (x2) remain.
I've now tried cm-12.1-20151007-SNAPSHOT-YOG4PAO331-acclaim.zip and cm-12.1-20150901-SNAPSHOT-YOG4PAO236-acclaim.zip with the same result.
Oddly enough, when I tried older versions (have tried cm-11-20150831-SNAPSHOT-XNG3CAO3FN-acclaim.zip and cm-10.2-20131102-SNAPSHOT-M1-acclaim.zip), those files give me a different error. They say (example for CM v11):
Installing update...
E:Error in /sdcard/cm-11-20150831-SNAPSHOT-XNG3CAO3FN-acclaim.zip
(Status 0)
Installation aborted.
Is something wrong with my SD?!? I am using Linux Mint and Gparted to format the SD. I have the boot and lba flags on. Since I'm getting CWM to boot on the NT, I feel like the SD is OK and the error is in the .zip file or some setting on the NT itself. Does anybody have any ideas??
Potentially related side note: I've alternatively used the dd command and USB Image Writer to copy an img file to the SD (tried twrp-2.8.6.0-acclaim-sdcard.img and cm-12.1-20151007-SNAPSHOT-YOG4PAO331-acclaim-recovery.img) and everytime I get an error when I try to mount it on my laptop. I'd be happy to post the whole error, but the synopsis is "mount: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error". Using sudo fdisk -l /dev/sdb shows that "Disk /dev/sdb doesn't contain a valid partition table". Putting it in the NT and trying to boot does nothing, just black screen after the n logo when it should go to recovery.
So I've tried numerous paths (~20 tries total) and every one seems to have a road block. I hope something in here makes sense to somebody a whole lot smarter than me! Please help!
~Nate
Are you sure that's the right CWM for CM 12.x? To flash 10.2 long ago I used CWM 6.0.2.x
Seems unlikely that an earlier version would be used for CM 12.x
That's a good point, your're on to something. I saw that in the cyanogenmod tutorial it says CWM doesn't support CM > 10.1.3. So your almost certainly right. (Why that's the active link in the beginner tutorial is still confusing to me.) I also see that CWM says it is not in active development for acclaim. So now on to twrp.
I tried the "Bootable SD card" instructions on the twrp acclaim page but can't get that to work. I've copied the img file to the root of the SD and renamed it to recovery.img but I don't know how to "boot TWRP using the cyanoboot menu from your sdcard". There is no cyanoboot menu on the sd card, it's only the img file, so no wonder nothing boots. How do I get the cyanoboot menu on the sd? My initial search led me to a page that has complex instructions on formatting the sd. Is that really the only way to get cyanoboot and ultimately get twrp to run??
Alternatively I've tried to burn the img to the sd using the dd command (thinking that an img file is meant to image an entire sd, not just live as a file on the sd). That gives me the errors that I posted originally (see section "Potentially related side note"). So I think you're right that I need a recovery other than CWM, but how do I get twrp to work?
Being a noob I feel like I'm missing something obvious but have been working for hours (ok, days) with no success.
Yeah, I think it *might* be that CWM is not going to cut it for CM 12.x, but the truth is I have no experience with TWRP so you're asking the wrong guy
I assume you looked at the "official" CM 12 thread here. For me the problem is what it is for you. There's not enough info there for someone who can follow good directions but is not already very familiar with all the ins and outs. What's needed is for digixmax to write a "how-to", but the last one he did was for CM 11. His directions are very clear. I was able to follow them as a noob for CM 10.2 without any trouble.
The hard way to do this is to sneak up on it by starting with CM 10.2, updating to CM 11 following digixmax's directions and then....well there must be a way to go from CM 11 to CM 12....maybe.....
I notice the sparse directions at CyanogenMod for CM 12 on Acclaim do refer to CWM so who knows?
coloradonate said:
Hi, complete noob here, will try to explain as best I can. Trying to get cyanogenmod 12.1 booted from SD. This is my first attempt for flashing any ROM on any device. I followed the acclaim tutorial on CM webpage (wiki.cyanogenmod.com...can't post link because I'm a forum noob). I can boot into CWM (v5.5.0.4) but when I go to install zip from sdcard, I get lots of errors. Without copy/paste, I'll do my best to state the important parts:
...
Installing update...
Warning: Nofile_contextscould not detect filesystem for /dev/block/platform/omap/omap_hsmmc.1/by-name/system, assuming ext4
mount: failed to mount /dev/block/platform/omap/omap_hsmmc.1/by-name/system at /system: No such file or directory
unmount of /system failed; no such volume
The error continues with nearly the same thing but for .../by-name/userdata at /data.
It again repeats the error with the /system (same as above)
Error ends with:
script succeeded: result was [0.200000]
Install from sdcard complete.
When I reboot the system, it goes back into stock B&N startup as if the ROM was not updated. No surprise considering the errors. I tried again and this time used CWM to enter "mounts and storage" and manually mounted /data and /system. The error for /data went away but the /system errors (x2) remain.
I've now tried cm-12.1-20151007-SNAPSHOT-YOG4PAO331-acclaim.zip and cm-12.1-20150901-SNAPSHOT-YOG4PAO236-acclaim.zip with the same result.
Oddly enough, when I tried older versions (have tried cm-11-20150831-SNAPSHOT-XNG3CAO3FN-acclaim.zip and cm-10.2-20131102-SNAPSHOT-M1-acclaim.zip), those files give me a different error. They say (example for CM v11):
Installing update...
E:Error in /sdcard/cm-11-20150831-SNAPSHOT-XNG3CAO3FN-acclaim.zip
(Status 0)
Installation aborted.
Is something wrong with my SD?!? I am using Linux Mint and Gparted to format the SD. I have the boot and lba flags on. Since I'm getting CWM to boot on the NT, I feel like the SD is OK and the error is in the .zip file or some setting on the NT itself. Does anybody have any ideas??
Potentially related side note: I've alternatively used the dd command and USB Image Writer to copy an img file to the SD (tried twrp-2.8.6.0-acclaim-sdcard.img and cm-12.1-20151007-SNAPSHOT-YOG4PAO331-acclaim-recovery.img) and everytime I get an error when I try to mount it on my laptop. I'd be happy to post the whole error, but the synopsis is "mount: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error". Using sudo fdisk -l /dev/sdb shows that "Disk /dev/sdb doesn't contain a valid partition table". Putting it in the NT and trying to boot does nothing, just black screen after the n logo when it should go to recovery.
So I've tried numerous paths (~20 tries total) and every one seems to have a road block. I hope something in here makes sense to somebody a whole lot smarter than me! Please help!
~Nate
Click to expand...
Click to collapse
Your description sounds exactly like the SD card was not properly formatted with an MSDOS partition table with a primary partition as FAT32. From the CyanogenMod wiki: "Put the micro SD card (SD card from now on) in the computer. Backup all the information on the SD card. Everything on it will be deleted. Make a new MSDOS partition table and add a FAT32 partition as the first primary partition with a minimum of 300 MB. Then make sure you enable the boot and lba flags. This can be done in Ubuntu using GParted. Formats like EXT2, EXT3, and EXT4 do not work. It is not necessary to allocate the entire card. You can add other partitions to the card, but they need to be manually mounted on your Nook anyway." When you set up the partition table a the primary partition, the format must be written/saved to the SD card. Unmount the SD card and mount it again to ensure that the formatting took. Once that is verified then you can write to files to the SD card, unmout it again, and insert it into the Tablet and go through the install steps.
I'm looking at putting 12.1 on my Tablet, which currently has 10.2 and runs pretty well. But the basic setup instructions for the SD card are the same - MSDOS table with a FAT32 primary partition. You can add 3 more FAT32 partitions, but they must be primary and FAT32.
Thanks for the reply. Unfortunately I did partition just like it asked. It is set as Primary, Fat 32, and the boot and lba flags are on.
I'm still stuck, but I'm understanding a few things. The Cyanogenmod install wiki is obviously out of date (even though it says it was last modified Oct. 25, 2015 when I looked tonight). The wiki has you download CWM 5.0.x, which is a 2012 file intended to work with CM 10.x. Then later in the same wiki it says that CWM no longer supports CM>10.1.3, so obviously it is not up to date for CM 11.x and 12.x. Unfortunately the wiki was not updated to provide a link to a recovery that works...at least not that I've found. I've lost faith in that wiki.
I'm totally fine using Twrp, but I can't even get a version of twrp that works with the latest CWM 12.1 release. Should be simple, but for some reason can't get it to work. If anybody is still willing to try to help me, please point me in the right direction!
And here's a total noob question that may solve my problems: why does the cyanogenmod downloads page have a link for the .zip and a "recovery" .img? Is that img THE recovery that I should be using for that particular version of CM? I tried writing the image to the SD but have the same SD errors as I previously reported.
So...did you try following these directions? They are sketchier than I am comfortable with but it is the "official" thread. And there's certainly a recovery link there.
I'm thinking about upgrading from 10.21 but I just can't find directions that make me feel like I'm not going to trash what I already have
2 things to report: 1) I'll respond to the reply above. 2) got it working with CM 11!
1) Yes I have tried following that and read it more times than I can count, but my extreme noobiness has left me floundering in tutorial after tutorial. I tried fastboot, couldn't get it to install. Finally got it to install, couldn't get it to connect to the NT. I tried bootable SD, couldn't get it. Tried root, couldn't get that. Why couldn't I get any of that to work?? I have absolutely no idea, but I hit dead end after dead end and was left unbelievably frustrated by this whole thing. On to #2...
2) I got CM 11 to work! I don't care one bit that it's not 12.1, what's important is that I got CM finally running on my stock NT! I followed this tutorial (http://forum.xda-developers.com/showthread.php?t=2692403). It required one *very* slight modification that I posted at the very end of that thread (post #14.) Don't laugh at my excitement, I'm just happy this things is finally over. (For now at least...I'm sure I'll be digging further now that I've gotten this far.)
I'm really glad that worked for you I still remember how I felt when I got CM 10.21 working starting from stock on an ebay special.
You've given me a little push to get serious about upgrading to CM 11 or perhaps CM 12. I need to read (and reread) those posts until I feel like I've got it down. Your discovery will help, I'm sure.
Just to wrap up this thread, I got CM12.1 to work! Please refer to my last post (post #18) in the following thread for somewhat detailed instructions for how I did it: http://forum.xda-developers.com/showthread.php?t=2692403&page=2#post63932363
I hope that explains it all to anyone interested, or anyone else who was floundering around like I was. Now I'm happily running CM12.1 and loving it. Thanks to all the developers, especially Digixmax for the post that finally helped me through this!
Hi
I'll try to make it brief. Some time ago, my stock Nook slowed down like a mule so I decided to root it, then applied Trimmer to enable trim. Beforehand I'd checked the eMMc with a Brickbug app and it popped up with "sane chip", as I'd read some Nooks had a faulty Samsung eMMc.
It went into a bootloop, and only started showing shredded Nook letters on an abstract background during boot. Then I tried various bootable SD cards to try to flash various stuff, as per available XDA threads, especially - leapinlar's, verygreen's and amaces'. First it would not complete the flashing of a ROM, just froze towards the end, then eventually wouldn't boot up at all.
Here's the weird part. Without an SD card, it doesn't boot up at all.
When I make a bootable SD, it only boots to TWRP 2.6.0.0 (some other versions [amaces] it won't boot to), but doesn't see any zips on the card and won't let me flash anything, even though it previously did, but wouldn't complete the flash.
Whatever else I burn on the card, it either doesn't boot up at all, or boots to whatever it is you can see on the attached printscreens, and won't mount anything. So if I'm guessing right, the eMMc is not borked, as it seems the device boots to some remnants of something that's there, and not on the SD.
Is there a way of fixing that mess? I'd appreciate any ideas.
Best
W.
You can try to flash this flashable_fix_bootdata-ovation.zip which typically should cure corrupted or missing bootdata issues.
Hi, thanks but how? The only thing I tried so far that the Nook boots to is a TWRP 2.6.0.0. bottable card and it won't see the zips on it. So how can I flash the fix bootdata zip?
wojtasys said:
Hi, thanks but how? The only thing I tried so far that the Nook boots to is a TWRP 2.6.0.0. bottable card and it w on't see the zips on it. So how can I flash the fix bootdata zip?
Click to expand...
Click to collapse
Have you tried the verygreen's old SD-based CWM recovery?
If you mean the one from that thread:
https://forum.xda-developers.com/showthread.php?t=2600572
I have. The download links for the initial card image don't work. I looked elsewhere - nowhere to be found.
Sorry about the trouble, guys, forgot to update the dns when the server moved. I just updated it, but it'll take some time to propagate. The actual new ip address is now 178.34.187.142 - you can place it into your hosts file if you don't want to wait.
Nook HD+ Bootloop error
OK, I tried the succulentboot.zip from your folder:
https://www.mediafire.com/folder/6a4rivb8kkdfu/Nook HD+):
Now the zips on the sd are accessible, so I tried flashing the flashable_fix_bootdata-ovation and the screen shows the result.
I tried flashing stock recovery too and it says it's done that, but I guess without the fixed bootfiles it won't work anyway.
wojtasys said:
OK, I tried the succulentboot.zip from your folder:
https://www.mediafire.com/folder/6a4rivb8kkdfu/Nook HD+):
Now the zips on the sd are accessible, so I tried flashing the flashable_fix_bootdata-ovation and the screen shows the result.
I tried flashing stock recovery too and it says it's done that, but I guess without the fixed bootfiles it won't work anyway.
Click to expand...
Click to collapse
Assuming that your flashing of stock recovery was successful (recovery's reports of successful completion can sometimes be erroneous) and also your factory backup partition is still intact, you can try to initiate a factory reset by using the "8 failed boots" method: with the Nook in the power-off state, power it on, then as soon as the boot screen appears hold down the power button until it powers off, do this 8 times, and the Nook should go into stock recovery to revert to factory-fresh state.
Flashing your flashable_restore_stock-recovery-ovation zip ends with the screen I'm attaching.
Then I tried "8 failed boots" but it only boots to CWM SD, without the card - it doesn't power up at all.
Eventually, nothing changes.
Tried putting the stock ROM on the card and flashing that, but the partition size is too small, even though its a 16GB card.
wojtasys said:
Now the zips on the sd are accessible, so I tried flashing the flashable_fix_bootdata-ovation and the screen shows the result.
Click to expand...
Click to collapse
If the issue is about the two files, you could mount /bootdata and copy them manually (ADB shell should be functional with any of these recoveries). You'd extract BCB and BootCnt from ZIP, and copy them onto SD card, then do something like:
Code:
mkdir -p /bootdata
mount -t vfat /dev/block/mmcblk0p6 /bootdata
cd /external_sd or /sdcard or /emmc (wherever SD card root is mounted)
cp BCB BootCnt /bootdata/
Or, you could edit the updater-script inside ZIP to remove the device assert line like in the attachment here. By the way, are the updated images here also failing?
Flashing your flashable_fix_bootdata-ovation-no-assert.zip shows "install from sd card complete" but the device still won't power up without the card.
Trying to mount bootdata results in "error mounting bootdata".
There's no adb command line in that sd recovery, just adb sideload. TWRP 2.6 had it but it didn't access the files on the sd.
Then, I'm not sure I'll know how to edit the updater-script inside ZIP to remove the device assert line.
Chances are your EMMC is hosed, in which case you can try running CM entirely off SD card using the succulent special build available at https://iamafanof.wordpress.com/201...-4-4-4-for-bricked-no-emmc-nook-hd-04nov2014/.