Related
Hi, I´m trying to configure my new sdcard (sandisk 32gb cl4) but everytime I try to create the ext2 partition on my ubuntu i get this error
Code:
Error creating file system: helper exited with exit code 1: cannot mount /dev/sdb1 at /tmp/job-mkfs-WmyAZC: Invalid argument
Filesystem label=New Volume
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
2048000 inodes, 8191996 blocks
409599 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
250 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624
Writing inode tables: 0/250 1/250 2/250 3/250 4/250 5/250 6/250 7/250 8/250 9/250 10/250 11/250 12/250 13/250 14/250 15/250 16/250 17/250 18/250 19/250 20/250 21/250 22/250 23/250 24/250 25/250 26/250 27/250 28/250 29/250 30/250 31/250 32/250 33/250 34/250 35/250 36/250 37/250 38/250 39/250 40/250 41/250 42/250 43/250 44/250 45/250 46/250 47/250 48/250 49/250 50/250 51/250 52/250 53/250 54/250 55/250 56/250 57/250 58/250 59/250 60/250 61/250 62/250 63/250 64/250 65/250 66/250 67/250 68/250 69/250 70/250 71/250 72/250 73/250 74/250 75/250 76/250 77/250 78/250 79/250 80/250 81/250 82/250 83/250 84/250 85/250 86/250 87/250 88/250 89/250 90/250 91/250 92/250 93/250 94/250 95/250 96/250 97/250 98/250 99/250100/250101/250102/250103/250104/250105/250106/250107/250108/250109/250110/250111/250112/250113/250114/250115/250116/250117/250118/250119/250120/250121/250122/250123/250124/250125/250126/250127/250128/250129/250130/250131/250132/250133/250134/250135/250136/250137/250138/250139/250140/250141/250142/250143/250144/250145/250146/250147/250148/250149/250150/250151/250152/250153/250154/250155/250156/250157/250158/250159/250160/250161/250162/250163/250164/250165/250166/250167/250168/250169/250170/250171/250172/250173/250174/250175/250176/250177/250178/250179/250180/250181/250182/250183/250184/250185/250186/250187/250188/250189/250190/250191/250192/250193/250194/250195/250196/250197/250198/250199/250200/250201/250202/250203/250204/250205/250206/250207/250208/250209/250210/250211/250212/250213/250214/250215/250216/250217/250218/250219/250220/250221/250222/250223/250224/250225/250226/250227/250228/250229/250230/250231/250232/250233/250234/250235/250236/250237/250238/250239/250240/250241/250242/250243/250244/250245/250246/250247/250248/250249/250done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 26 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
And if I try to create the partition with the amonra recovery it says the partition was created but it wasn´t
and update ext2 to ext3 or ext3 to ext4 tells me to use "adb fs ext3(or 4)"
I don´t know what to do to get it working, my 2gb and 8gb sd card work pretty well with both methods listed above.
thx
"cannot mount /dev/sdb1 at /tmp/job-mkfs-WmyAZC: Invalid argument"
Thats probably the problem but I'm not sure what's causing it. What command are you using? Can you mount the card manually?
I thought there were only class 2 32gb sd cards Where'd you buy it?
I have pictures of the error now:
I can´t create an ext partition in gparted nor in amonra recovery tool
My sd card is a sandisk 32gb cl4 and it doesn´t accept the ext2/3/4 partition but accepts fat32 or linux swap
here are the screenshosts I take:
And someone replied:
It seems to some issue with the ext2 being logical or primary. Paragon seems to work first time for allot of people but then just crashes like in your case.
Mixing these two file system may cause some issues. The only way todo do it is using linux. Check mobile phone forums out they have good guides- avoid the paragon ones.
Click to expand...
Click to collapse
But I didn´t understand
mcp2009 said:
I thought there were only class 2 32gb sd cards Where'd you buy it?
Click to expand...
Click to collapse
Mercadolivre, it´s an ebay but in Brazil. It´s imported from US, brand new product
Im thinking it might be a fake because sandisk only makes class 2 32gb sd cards. Try running hwtest tool to check
mcp2009 said:
Im thinking it might be a fake because sandisk only makes class 2 32gb sd cards. Try running hwtest tool to check
Click to expand...
Click to collapse
I didn´t find hwtest but I tried Crystal Disk Mark
What do you say?
It seems like it could be a class 4 but search around for hwtest tool or "test fake memory card" cuz it might be a class 4 but not 32gbs. Hwtest tool will determine the actual free space and tell you if its a 4gb disguised as a 32gb
Using h2testw
Code:
The media is likely to be defective.
104 MByte OK (212992 sectors)
31.1 GByte DATA LOST (65282048 sectors)
Details:0 KByte overwritten (0 sectors)
0 KByte slightly changed (< 8 bit/sector, 0 sectors)
31.1 GByte corrupted (65282048 sectors)
0 KByte aliased memory (0 sectors)
First error at offset: 0x00000000058f2600
Expected: 0x00000000058f2600
Found: 0x0000000000000000
H2testw version 1.3
Writing speed: 5.76 MByte/s
Reading speed: 8.80 MByte/s
H2testw v1.4
Is it fake or broken?
paolobacci said:
Code:
The media is likely to be defective.
104 MByte OK (212992 sectors)
31.1 GByte DATA LOST (65282048 sectors)
Details:0 KByte overwritten (0 sectors)
0 KByte slightly changed (< 8 bit/sector, 0 sectors)
31.1 GByte corrupted (65282048 sectors)
0 KByte aliased memory (0 sectors)
First error at offset: 0x00000000058f2600
Expected: 0x00000000058f2600
Found: 0x0000000000000000
H2testw version 1.3
Writing speed: 5.76 MByte/s
Reading speed: 8.80 MByte/s
H2testw v1.4
Is it fake or broken?
Click to expand...
Click to collapse
I'm thinking fake. It's basically saying that 31.1gbs was fake. Can you get a refund?
Soooo, where did you buy the card? Cheap on ebay?
Yes, I´ll do that
khaytsus said:
Soooo, where did you buy the card? Cheap on ebay?
Click to expand...
Click to collapse
MercadoLivre it´s a br ebay
The vendor will get me refund and I´ll buy another one.
Thank you guys
Yeah, yeah. Sounds like a million other posts. I am a unix/linux sort of guy, so I'm quite familiar with navigating and working in *nix based operating systems.
Here is the synopsis:
Without an SD card, the device will not boot. I can hear the USB cycle and I'm stuck at a black screen. Sounds normal so far.
After booting up CWM, I can adb in. My first step was to check devices.
/dev/block # cd /dev/block
cd /dev/block
/dev/block # ls
ls
loop0 loop5 mmcblk0p2 ram10 ram15 ram6
loop1 loop6 mmcblk1 ram11 ram2 ram7
loop2 loop7 platform ram12 ram3 ram8
loop3 mmcblk0 ram0 ram13 ram4 ram9
loop4 mmcblk0p1 ram1 ram14 ram5
As you can see, there are a few missing block devices. I proceeded to mount each of these. Only mmcblk0p1 had anything on it: the boot partition, as I expected. Mmcblk1 was the device name for the SDCard, which deviates from what I would have expected. Blk0p2 contained nothing and was not mountable.
Next, I tried to do a 'mknod' to create the devices. This was successful to a degree, but did not actually create working devices. I attempted to mkfs.ext2 on them, that failed. For grins, I tried it on p1 and p2. The only one that worked was p1.
At this point, I decided to try and flash the boot.img I retrieved from here: "mrm3.net/nook-color-recover-any-bricked-device/" and see what I could do to get the device up and running - any self booting would be an improvement, I thought. This too failed. The 'dd' was successful and the partition now contained boot info, but when i tried to boot up, I still received a black screen:
/dev/block # dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1
144522+0 records in
144522+0 records out
73995264 bytes (70.6MB) copied, 44.914978 seconds, 1.6MB/s
/dev/block #
When I try to flash ANY rom, I get failures - obviously because there's no place for them to flash to.
'dmesg' doesn't contain any useful information. The device seems hosed. The last rom I was running was Cyanogen nightly #69, which wouldn't allow me to mount SDCard or do anything useful. When I tried to install nightly #80, I found that the device was no longer usable.
Hopefully this was thorough enough, I refrained from typing out the obvious stuff, but please feel free to suggest things. I'm stumped. I still think it can be saved, but I don't have a ton of hope.
Thanks a lot for giving this a read. I really hope someone can help out.
--
j.k
Ill add you to the list with everyone else here of people who are more advanced than I. But one of the fist things I learned about the Nook is that its pretty much impossible to brick. I'm sure someone from the list will be by to help soon.
I really hope so.
Logically, if the device nodes can be recreated, I could flash a new mod in. Perhaps I'm going about that the wrong way.
sangandongo said:
Next, I tried to do a 'mknod' to create the devices. This was successful to a degree, but did not actually create working devices. I attempted to mkfs.ext2 on them, that failed. For grins, I tried it on p1 and p2. The only one that worked was p1.
Click to expand...
Click to collapse
Have you verified that the partition table is actually intact/correct? No point trying to create device nodes if the underlying devices aren't there. What does "fdisk -l /dev/block/mmcblk0" give you, and how does it compare to the standard layout?
Maybe check notes with the OP of this thread -- appears that both of you have essentially the same problem.
jll544 said:
Have you verified that the partition table is actually intact/correct? No point trying to create device nodes if the underlying devices aren't there. What does "fdisk -l /dev/block/mmcblk0" give you, and how does it compare to the standard layout?
Maybe check notes with the OP of this thread -- appears that both of you have essentially the same problem.
Click to expand...
Click to collapse
Sorry, I should have included that earlier. The partition table is b0rked. I also had attempted applying the zips from the [ZIP][RECOVERY] EMMC Recovery Repair thread to no avail.
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
4 heads, 16 sectors/track, 242432 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 15260 488312 b Win95 FAT32
/dev/block/mmcblk0p2 15261 242432 7269504 83 Linux
Not to sounds like a smartass (or maybe a dumbass) but have you tried to restore back to stock?
Yes. In my initial post, I stated that no restoring via zip works.
Currently I am attempting to rebuild the partition table as mine is hosed. I get the following output though, which is troubling by comparison to what I should be seeing:
~ # busybox fdisk /dev/block/mmcblk0
busybox fdisk /dev/block/mmcblk0
The number of cylinders for this disk is set to 242432.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
p
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
4 heads, 16 sectors/track, 242432 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 15260 488312 b Win95 FAT32
/dev/block/mmcblk0p2 15261 242432 7269504 83 Linux
Command (m for help): d
d
Partition number (1-4):
Right, virtually all .zip restore files are filesystem-level recovery and assume that the partition table is unchanged.
Try forcing the geometry using "fdisk -H 255 -S 63 /dev/block/mmcblk0"
Before I write this, does the following look like what you'd expect? I mean, it makes sense considering...
Code:
~ # fdisk -H 255 -S 63 /dev/block/mmcblk0
fdisk -H 255 -S 63 /dev/block/mmcblk0
Code:
Command (m for help): p
p
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
255 heads, 63 sectors/track, 965 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 61 488312 b Win95 FAT32
Partition 1 has different physical/logical beginnings (non-Linux?):
phys=(0, 1, 1) logical=(0, 0, 17)
Partition 1 has different physical/logical endings:
phys=(1023, 3, 16) logical=(60, 202, 14)
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 61 966 7269504 83 Linux
Partition 2 has different physical/logical beginnings (non-Linux?):
phys=(1023, 3, 16) logical=(60, 202, 15)
Partition 2 has different physical/logical endings:
phys=(1023, 3, 16) logical=(965, 205, 8)
Partition 2 does not end on cylinder boundary
jll544 said:
Right, virtually all .zip restore files are filesystem-level recovery and assume that the partition table is unchanged.
Try forcing the geometry using "fdisk -H 255 -S 63 /dev/block/mmcblk0"
Click to expand...
Click to collapse
What he said. Texas Instrumentss OMAP devices such as the nook require that media, whether sd, mmc, etc, be formatted with particular geometry. One that's set up, you can create the partitions normally and forget it ever happened. Remember that the first partition should be FAT, and this is where the kernel (uImage) and ramdisk (uRamdisk) as well as bootloader (u-boot.bin) and pre-bootloader (mlo) go.
See here for more info.
I believe the version of busybox available to me on this 3.0.2.8 CWR SD image is too old to accomplish what the instructions on this post state: http://forum.xda-developers.com/showpost.php?p=13971291&postcount=110
I've been unable to find a bundle of the binaries yet, but I'm still looking. That being said, I changed the geometry of the partition table and wrote the changes, then tried to dd again - fail.
sangandongo said:
Before I write this, does the following look like what you'd expect? I mean, it makes sense considering...
Code:
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 61 488312 b Win95 FAT32
Partition 1 has different physical/logical beginnings (non-Linux?):
phys=(0, 1, 1) logical=(0, 0, 17)
Partition 1 has different physical/logical endings:
phys=(1023, 3, 16) logical=(60, 202, 14)
Partition 1 does not end on cylinder boundary
<snip>
Click to expand...
Click to collapse
You mean you wrote the partition table as shown above? That won't work. You need to run fdisk with the corrected geometry, delete the existing partitions, and create new ones. Those warnings say that your partition LBA's are still aligned to the incorrect geometry.
What happens when remove all if the partitioning on the emmc, format it, and repartition it? For some reason ive found linux has a tendency to corrupt storage bits of memory chips altogether and the only way to restore was to completely start over clean. Also, anyone tested for bad blocks? One of my laptops decided to take a **** and the only way I'm able to install an os on it is by installing ubuntu on half the hard drive. Maybe if it is bad blocks we could repartition around them?
Sent from my PC36100 using Tapatalk
RileyGrant said:
What happens when remove all if the partitioning on the emmc, format it, and repartition it? For some reason ive found linux has a tendency to corrupt storage bits of memory chips altogether and the only way to restore was to completely start over clean. Also, anyone tested for bad blocks? One of my laptops decided to take a **** and the only way I'm able to install an os on it is by installing ubuntu on half the hard drive. Maybe if it is bad blocks we could repartition around them?
Click to expand...
Click to collapse
Save the FUD for somewhere else....
RileyGrant said:
For some reason ive found linux has a tendency to corrupt storage bits of memory chips altogether and the only way to restore was to completely start over clean.
Click to expand...
Click to collapse
LOL, just about any operating system will write an unsuitable partition table if the end user commands it to do so. No, the OP has omitted details about what he did to get into his situation, but there is no chance it just happened on its own (i.e., his partition layout is technically valid but unbootable by OMAP). If we're going to hazard wild guesses, I'd say he was trying to install Backtrack or some other non-Android Linux distribution.
Hahah I only used linux as an example because ubuntu its all I have run for a coupe years now. but you sir are completely oblivious too the fact that evo users, thunderbolt users and now nook users have reported the same issue and symptoms, always on gingerbread. A self corruption of internal memory.
Sent from my PC36100 using Tapatalk
jll544 said:
LOL, just about any operating system will write an unsuitable partition table if the end user commands it to do so. No, the OP has omitted details about what he did to get into his situation, but there is no chance it just happened on its own (i.e., his partition layout is technically valid but unbootable by OMAP). If we're going to hazard wild guesses, I'd say he was trying to install Backtrack or some other non-Android Linux distribution.
Click to expand...
Click to collapse
In this case, I believe it was caused either by "fixing permissions" while using Rom Manager, or by doing it in CWM. This was in an attempt to get out of CM7 nightly #69, which all but rendered my system inoperable.
I agree with you though: there's likely no reason why linux would cause corruption on a disk. If anything, an app might be to blame, but it would have to explicitly do so.
That aside, I am very close to getting my Nook fixed. I rebuilt the partition table this morning after loading busybox 1.18 onto my SD card. ran 'fdisk' with the proper geometry, deleted the existing partitions, built each out to standard specs, then changed the filesystem id for each. After that I did a mkfs.vfat and mke2fs on the appropriate partitions and wrote the configuration.
I rebooted, did a dd of a 1.0.1 boot image to mmcblk0p1 and of a system image to mmcblk0p5 and tried to boot, but I'm still getting a black screen.
Here is my current partition table after I resized it and marked the partitions with their respective types:
Code:
/busybox fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
255 heads, 63 sectors/track, 965 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 9 72261 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p2 10 18 72292+ c Win95 FAT32 (LBA)
/dev/block/mmcblk0p3 19 56 305235 83 Linux
/dev/block/mmcblk0p4 57 965 7301542+ 5 Extended
/dev/block/mmcblk0p5 57 114 465853+ 83 Linux
/dev/block/mmcblk0p6 115 789 5421906 83 Linux
/dev/block/mmcblk0p7 790 834 361431 83 Linux
/dev/block/mmcblk0p8 835 965 1052226 c Win95 FAT32 (LBA)
I made the Fat32 Partitions using mk.vfat and the linux partitions with mke2fs -j -L <label>. Something still just isn't right.
Blah. I get so OCD about this sort of ****. I need to just go outside and play, this is driving me nuts.
sangandongo said:
Blah. I get so OCD about this sort of ****. I need to just go outside and play, this is driving me nuts.
Click to expand...
Click to collapse
It's not booting because you're missing your /rom partition. There is no data in /mmcblk0p2, which init calls for all your device info. Hopefully you have a backup of that as well. Without it, you won't be able to run any roms with your nook color.
And unfortunately that is a partition that is not good to share with anyone else besides each individual nook owner because is contains all the unique Device identifiers for your Nook. If two people would have the same Device info and you're both logged into your B&N stock, it will error out on the B&N server side and de-register your device and the other person as well.
If you need further guidance, PM me and I'll see what I can do to help to resolve your /rom partition issue.
-Racks
I DD'd every partition off my friend's Nook. Every one. Just to see if I could get this puppy running. Still black.
Has anyone else tried?
I backed up ICS boot.img and system.img before upgrading and then restore after flashing V20A.kdz but it doesn't boot. Just stays at the non-animated LG logo.
arararagi said:
Has anyone else tried?
I backed up ICS boot.img and system.img before upgrading and then restore after flashing V20A.kdz but it doesn't boot. Just stays at the non-animated LG logo.
Click to expand...
Click to collapse
Did you tried install Windows7 and after change the "windows" folder for the one from XP?
Doesn't make sense, right?
RuedasLocas said:
Did you tried install Windows7 and after change the "windows" folder for the one from XP?
Doesn't make sense, right?
Click to expand...
Click to collapse
It works if I also restore the MBR from XP.
arararagi said:
It works if I also restore the MBR from XP.
Click to expand...
Click to collapse
Here you don's have that "if"... sorry
Found this in another thread
gordon0001 said:
well, since no one answered i figured out the new kernel (3.1) is the issue. replacing the kernel with the old kernel (2.6) in recovery.img solved the problem, but partitions dont get mounted and couldnt get them mounted, since i barely know the internals of a linux kernel and the kernel ramdisk
Click to expand...
Click to collapse
I tried doing the same thing and just catting the resulting recovery image to boot.
It starts up and adb works, however only external SD on Tegra is accessible.
Code:
~ # find /dev/block/
/dev/block/
/dev/block/loop7
/dev/block/loop6
/dev/block/loop5
/dev/block/loop4
/dev/block/loop3
/dev/block/loop2
/dev/block/loop1
/dev/block/loop0
/dev/block/mmcblk0p1
/dev/block/platform
/dev/block/platform/sdhci-tegra.2
/dev/block/platform/sdhci-tegra.2/mmcblk0p1
/dev/block/platform/sdhci-tegra.2/by-num
/dev/block/platform/sdhci-tegra.2/by-num/p1
/dev/block/platform/sdhci-tegra.2/mmcblk0
/dev/block/mmcblk0
~ # cat /proc/partitions
major minor #blocks name
179 0 15351296 mmcblk0
179 1 15347200 mmcblk0p1
From dmesg:
Code:
<6>[ 3.855253] sdhci: Secure Digital Host Controller Interface driver
<6>[ 3.855433] sdhci: Copyright(c) Pierre Ossman
<4>[ 3.856721] mmc0: Invalid maximum block size, assuming 512 bytes
<6>[ 3.856848] mmc0: no vmmc regulator found
<7>[ 3.858202] Registered led device: mmc0::
<6>[ 3.861711] mmc0: SDHCI controller on platform [sdhci-tegra.3] using ADMA
<4>[ 3.863024] mmc1: Invalid maximum block size, assuming 512 bytes
<6>[ 3.863145] mmc1: no vmmc regulator found
<7>[ 3.864473] Registered led device: mmc1::
<6>[ 3.866846] mmc1: SDHCI controller on platform [sdhci-tegra.0] using ADMA
<4>[ 3.867178] tegra_gpio_irq_set_wake() called
<3>[ 3.867284] sdhci sdhci-tegra.2: SD card wake-up event registrationfailed with eroor: -22
<4>[ 3.868587] mmc2: Invalid maximum block size, assuming 512 bytes
<6>[ 3.868706] mmc2: no vmmc regulator found
<7>[ 3.870035] Registered led device: mmc2::
<6>[ 3.872372] mmc2: SDHCI controller on platform [sdhci-tegra.2] using ADMA
<7>[ 3.872860] Registered led device: button-backlight
<4>[ 3.872961] keypad_led_probe success
<6>[ 3.874563] tegra-se tegra-se: tegra_se_probe: complete
<6>[ 3.875491] usbcore: registered new interface driver usbhid
<6>[ 3.875681] usbhid: USB HID core driver
<6>[ 3.876370] logger: created 256K log 'log_main'
<6>[ 3.876608] logger: created 256K log 'log_events'
<6>[ 3.876939] logger: created 256K log 'log_radio'
<6>[ 3.877259] logger: created 256K log 'log_system'
<4>[ 3.972419] mmc0: switch to bus width 1 ddr 0 failed
<3>[ 3.972635] mmc0: error -110 whilst initialising MMC card
<4>[ 4.085800] mmc0: switch to bus width 1 ddr 0 failed
<3>[ 4.086013] mmc0: error -110 whilst initialising MMC card
<4>[ 4.213528] mmc0: switch to bus width 1 ddr 0 failed
<3>[ 4.213657] mmc0: error -110 whilst initialising MMC card
<4>[ 4.379808] mmc0: switch to bus width 1 ddr 0 failed
<3>[ 4.379939] mmc0: error -110 whilst initialising MMC card
This is how things should look (from the new kernel):
Code:
~ # find /dev/block/
/dev/block/
/dev/block/loop7
/dev/block/loop6
/dev/block/loop5
/dev/block/loop4
/dev/block/loop3
/dev/block/loop2
/dev/block/loop1
/dev/block/loop0
/dev/block/mmcblk1p1
/dev/block/mmcblk1
/dev/block/mmcblk0boot0
/dev/block/mmcblk0boot1
/dev/block/mmcblk0p13
/dev/block/mmcblk0p12
/dev/block/mmcblk0p11
/dev/block/mmcblk0p10
/dev/block/mmcblk0p9
/dev/block/mmcblk0p8
/dev/block/mmcblk0p7
/dev/block/mmcblk0p6
/dev/block/mmcblk0p5
/dev/block/mmcblk0p4
/dev/block/mmcblk0p3
/dev/block/mmcblk0p2
/dev/block/mmcblk0p1
/dev/block/platform
/dev/block/platform/sdhci-tegra.2
/dev/block/platform/sdhci-tegra.2/mmcblk1p1
/dev/block/platform/sdhci-tegra.2/by-num
/dev/block/platform/sdhci-tegra.2/by-num/p1
/dev/block/platform/sdhci-tegra.2/mmcblk1
/dev/block/platform/sdhci-tegra.3
/dev/block/platform/sdhci-tegra.3/mmcblk0boot0
/dev/block/platform/sdhci-tegra.3/mmcblk0boot1
/dev/block/platform/sdhci-tegra.3/mmcblk0p13
/dev/block/platform/sdhci-tegra.3/mmcblk0p12
/dev/block/platform/sdhci-tegra.3/mmcblk0p11
/dev/block/platform/sdhci-tegra.3/mmcblk0p10
/dev/block/platform/sdhci-tegra.3/mmcblk0p9
/dev/block/platform/sdhci-tegra.3/mmcblk0p8
/dev/block/platform/sdhci-tegra.3/mmcblk0p7
/dev/block/platform/sdhci-tegra.3/mmcblk0p6
/dev/block/platform/sdhci-tegra.3/mmcblk0p5
/dev/block/platform/sdhci-tegra.3/mmcblk0p4
/dev/block/platform/sdhci-tegra.3/mmcblk0p3
/dev/block/platform/sdhci-tegra.3/mmcblk0p2
/dev/block/platform/sdhci-tegra.3/mmcblk0p1
/dev/block/platform/sdhci-tegra.3/by-num
/dev/block/platform/sdhci-tegra.3/by-num/p13
/dev/block/platform/sdhci-tegra.3/by-num/p12
/dev/block/platform/sdhci-tegra.3/by-num/p11
/dev/block/platform/sdhci-tegra.3/by-num/p10
/dev/block/platform/sdhci-tegra.3/by-num/p9
/dev/block/platform/sdhci-tegra.3/by-num/p8
/dev/block/platform/sdhci-tegra.3/by-num/p7
/dev/block/platform/sdhci-tegra.3/by-num/p6
/dev/block/platform/sdhci-tegra.3/by-num/p5
/dev/block/platform/sdhci-tegra.3/by-num/p4
/dev/block/platform/sdhci-tegra.3/by-num/p3
/dev/block/platform/sdhci-tegra.3/by-num/p2
/dev/block/platform/sdhci-tegra.3/by-num/p1
/dev/block/platform/sdhci-tegra.3/by-name
/dev/block/platform/sdhci-tegra.3/by-name/UDB
/dev/block/platform/sdhci-tegra.3/by-name/CAL
/dev/block/platform/sdhci-tegra.3/by-name/FOT
/dev/block/platform/sdhci-tegra.3/by-name/MLT
/dev/block/platform/sdhci-tegra.3/by-name/DRM
/dev/block/platform/sdhci-tegra.3/by-name/UDA
/dev/block/platform/sdhci-tegra.3/by-name/NVA
/dev/block/platform/sdhci-tegra.3/by-name/USP
/dev/block/platform/sdhci-tegra.3/by-name/MSC
/dev/block/platform/sdhci-tegra.3/by-name/CAC
/dev/block/platform/sdhci-tegra.3/by-name/APP
/dev/block/platform/sdhci-tegra.3/by-name/LNX
/dev/block/platform/sdhci-tegra.3/by-name/SOS
/dev/block/platform/sdhci-tegra.3/mmcblk0
/dev/block/mmcblk0
~ # cat /proc/partitions
major minor #blocks name
179 0 15267840 mmcblk0
179 1 10240 mmcblk0p1
179 2 10240 mmcblk0p2
179 3 1572864 mmcblk0p3
179 4 393216 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 81920 mmcblk0p6
179 7 2048 mmcblk0p7
179 8 13062144 mmcblk0p8
179 9 16384 mmcblk0p9
179 10 16384 mmcblk0p10
179 11 20480 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 47104 mmcblk0p13
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0
179 48 15351296 mmcblk1
179 49 15347200 mmcblk1p1
And dmesg:
Code:
<6>[70:01:01 00:00:08.609] sdhci: Secure Digital Host Controller Interface driver
<6>[70:01:01 00:00:08.609] sdhci: Copyright(c) Pierre Ossman
<6>[70:01:01 00:00:08.609] sdhci-pltfm: SDHCI platform and OF driver helper
<4>[70:01:01 00:00:08.609] mmc0: Invalid maximum block size, assuming 512 bytes
<6>[70:01:01 00:00:08.609] mmc0: no vmmc regulator found
<7>[70:01:01 00:00:08.609] Registered led device: mmc0::
<6>[70:01:01 00:00:08.609] mmc0: SDHCI controller on sdhci-tegra.3 [sdhci-tegra.3] using ADMA
<6>[70:01:01 00:00:08.609] sdhci-tegra sdhci-tegra.0: vddio_sd_slot regulator not found: -19. Assuming vddio_sd_slot is not required.
<6>[70:01:01 00:00:08.609] sdhci-tegra sdhci-tegra.0: Error: tegra3 io dpd not supported for sdhci-tegra.0
<4>[70:01:01 00:00:08.609] mmc1: Invalid maximum block size, assuming 512 bytes
<6>[70:01:01 00:00:08.609] mmc1: no vmmc regulator found
<7>[70:01:01 00:00:08.609] Registered led device: mmc1::
<6>[70:01:01 00:00:08.619] mmc1: SDHCI controller on sdhci-tegra.0 [sdhci-tegra.0] using ADMA
<3>[70:01:01 00:00:08.619] Failed gpio lp0 enable for irq=405, error=-22
<3>[70:01:01 00:00:08.619] sdhci-tegra sdhci-tegra.2: SD card wake-up event registrationfailed with eroor: -22
<6>[70:01:01 00:00:08.619] sdhci-tegra sdhci-tegra.2: vddio_sd_slot regulator not found: -19. Assuming vddio_sd_slot is not required.
<4>[70:01:01 00:00:08.619] mmc2: Invalid maximum block size, assuming 512 bytes
<6>[70:01:01 00:00:08.619] mmc2: no vmmc regulator found
<7>[70:01:01 00:00:08.619] Registered led device: mmc2::
<6>[70:01:01 00:00:08.619] mmc2: SDHCI controller on sdhci-tegra.2 [sdhci-tegra.2] using ADMA
RuedasLocas said:
Did you tried install Windows7 and after change the "windows" folder for the one from XP?
Doesn't make sense, right?
Click to expand...
Click to collapse
That comparison doesn't make sense, in fact.
The linux kernel is not linked to the userspace like in windows, you can have the same system running either an early 2.6 version or a very latest 3.x with no changes at all to the rest of the programs.
And use the same version of lilo or grub to boot both kernels, for what the bootloader is concerned.
Not that android can be compared with no "if's" to a standard linux box, but makes more sense than compare it to windows.
And for what it's worth, Sony released an upgrade from Gingerbread to ICS for their 2011 line keeping the same kernel. (and GB to ICS is a way bigger leap than ICS to JB)
ircalf said:
That comparison doesn't make sense, in fact.
The linux kernel is not linked to the userspace like in windows, you can have the same system running either an early 2.6 version or a very latest 3.x with no changes at all to the rest of the programs.
And use the same version of lilo or grub to boot both kernels, for what the bootloader is concerned.
Not that android can be compared with no "if's" to a standard linux box, but makes more sense than compare it to windows.
And for what it's worth, Sony released an upgrade from Gingerbread to ICS for their 2011 line keeping the same kernel. (and GB to ICS is a way bigger leap than ICS to JB)
Click to expand...
Click to collapse
I confess that I was "unhappy" in that expression
ircalf said:
That comparison doesn't make sense, in fact.
The linux kernel is not linked to the userspace like in windows, you can have the same system running either an early 2.6 version or a very latest 3.x with no changes at all to the rest of the programs.
And use the same version of lilo or grub to boot both kernels, for what the bootloader is concerned.
Not that android can be compared with no "if's" to a standard linux box, but makes more sense than compare it to windows.
And for what it's worth, Sony released an upgrade from Gingerbread to ICS for their 2011 line keeping the same kernel. (and GB to ICS is a way bigger leap than ICS to JB)
Click to expand...
Click to collapse
i guess his point was that what the o.p tried to do didnt make sense, so what he said was in the same context, also its obvious that with new bootloader that it would not boot with the previous boot,img otherwise we wouldnt have such problems like not being able to use the v20a bootloader with the previous v10 firmware
like other people's can not mount anything ,
use TWRP boot , press install show internal storage 0mb
Is it means the storage over ?
ft7823 said:
like other people's can not mount anything ,
use TWRP boot , press install show internal storage 0mb
Is it means the storage over ?
Click to expand...
Click to collapse
hello anybody can help me ?
just after charging , the device can not open and use cwm boot in , showed can not mount anything ,
include the sdcard. I think the internal storage was damaged , is there any good ideas to get back ?
and I saw NT have a tool to unbrick ,is there also same tools for HD+?
What ROM were you using?
Are you booting from SD?
It seems that your emmc is bricked, unfortunately this seems not to be recoverable...
If you have adb access, try those commands mentioned here:
http://wiki.cyanogenmod.org/w/EMMC_Bugs#How_do_I_check_my_device.27s_eMMC_details.3F
CM10.2， I think you are right ,EMMC bricked.
but the strange thing is I use 3 sd card ,all can not boot from sdcard or emmc.
I want to flash noemmc version's cm, but also impossible now ...
so strange ..
wait, but you can boot into sd-recovery?
Jann F said:
wait, but you can boot into sd-recovery?
Click to expand...
Click to collapse
thank you , yesterday the devices can mount sdcard , so I install CM10.1 NOEMMC to sdcard
just one thing is not suit for me , the sdcard'format is not FAT32 and computer can only find the first part
so I can only download the file to my sdcard but cannot use usb or tf cardreader to put my files in.
but anyway , I can use it without emmc , the better thing than nothing to do.
1. My nook still bricked and cannot use any cwm except no-emmc version
2.I checked again, my nook is MGB4GA , I think should not be emmc bug
now
I use no-emmc version CWM flash EMMC recovery V6.0.3.2 ,
but without sdcard can only boot in the logo and stop there
e:can't mount /cache/revoery/command
and I use adb to check , show like below
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 398228 48 398180 0% /dev
~ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 15360 mmcblk0p3
179 4 16384 mmcblk0p4
179 5 49152 mmcblk0p5
179 6 49152 mmcblk0p6
179 7 458752 mmcblk0p7
259 0 688128 mmcblk0p8
259 1 475136 mmcblk0p9
259 2 28770304 mmcblk0p10
179 16 2048 mmcblk0boot1
179 8 2048 mmcblk0boot0
179 24 7761920 mmcblk1
179 25 7761888 mmcblk1p1
is this normal?
and is that able to restore from leapinlar's repari.zip?
Get yourself a 32gb class 4 sd card and you can boot into CWM recovery.
ft7823 said:
1. My nook still bricked and cannot use any cwm except no-emmc version
2.I checked again, my nook is MGB4GA , I think should not be emmc bug
now
I use no-emmc version CWM flash EMMC recovery V6.0.3.2 ,
but without sdcard can only boot in the logo and stop there
e:can't mount /cache/revoery/command
and I use adb to check , show like below
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 398228 48 398180 0% /dev
~ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 15360 mmcblk0p3
179 4 16384 mmcblk0p4
179 5 49152 mmcblk0p5
179 6 49152 mmcblk0p6
179 7 458752 mmcblk0p7
259 0 688128 mmcblk0p8
259 1 475136 mmcblk0p9
259 2 28770304 mmcblk0p10
179 16 2048 mmcblk0boot1
179 8 2048 mmcblk0boot0
179 24 7761920 mmcblk1
179 25 7761888 mmcblk1p1
is this normal?
and is that able to restore from leapinlar's repari.zip?
Click to expand...
Click to collapse
Your emmc looks ok. Do as the previous user suggested and get a SanDisk class 4 SD and make a bootable CWM SD per the instructions in item 1a in my HD/HD+ CWM thread linked in my signature. Then use that to flash a plain stock zip from item 6.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
Your emmc looks ok. Do as the previous user suggested and get a SanDisk class 4 SD and make a bootable CWM SD per the instructions in item 1a in my HD/HD+ CWM thread linked in my signature. Then use that to flash a plain stock zip from item 6.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
So i need a sandisk card.... unfortunately i have no such card in my hand.
use old card with no-emmc version cwm flash nook 2.1 ,random offset 0x29,final abort , other models unable to be flashed to the system.
use 6028 flash 2.1 or 2.2 can run half but then black screen and shut off.
flash CM10.1 CM10.2 can not run just at the beginning and then black screen and shut off.
so is that possible to use your repair.zip?
ft7823 said:
So i need a sandisk card.... unfortunately i have no such card in my hand.
use old card with no-emmc version cwm flash nook 2.1 ,random offset 0x29,final abort , other models unable to be flashed to the system.
use 6028 flash 2.1 or 2.2 can run half but then black screen and shut off.
flash CM10.1 CM10.2 can not run just at the beginning and then black screen and shut off.
so is that possible to use your repair.zip?
Click to expand...
Click to collapse
You do not want to use the noemmc CWM if you are wanting to flash to emmc. If the 2.2 will not flash with 6028 then any repair zip I make will not work either.
Sent from my SCH-i705 using XDA Premium HD app
168599699669
leapinlar said:
You do not want to use the noemmc CWM if you are wanting to flash to emmc. If the 2.2 will not flash with 6028 then any repair zip I make will not work either.
Sent from my SCH-i705 using XDA Premium HD app
Click to expand...
Click to collapse
ok , understood , anyway ,thank you for your reply.
Hello,
After a shutdown due to low battery, my tablet is soft bricked. :/ I suspect a corruption of the internal SD or the flash chip, I'm not really sure.
My tablet is unlocked, I have cwm 6.0.5.1 installed. If I remember correctly, I had some cromi-X rom.
I have access to the bootloader (11.4.1.29) and the recovery but the manipulations I'm doing aren't working.
When into recovery, I get the messages e: can't mount/open /cache/recovery/log (last_log, last_install).
I tried flashing all kind of roms, they all failed, the most successful install ended with an error creating symlinks.
Tried all the wipe/format/factory reset options in the recovery, most of the time, I get the "error mounting /data", "error mounting /sdcard/.android_secure".
I can mount /system but it doesn't work for /cache and /data.
I can fastboot boot other recoveries (other cwm, twrp) but somehow can't flash. I'm not getting any error, they're just not sticking.
I tried manually formatting with e2fsck commands but I get an error related with superblocks.
Here's my cat log /proc/partitions :
179 0 30535680 mmcblk0
179 1 8192 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 8192 mmcblk0p3
179 4 2097152 mmcblk0p4
179 5 897024 mmcblk0p5
179 6 512000 mmcblk0p6
179 7 8192 mmcblk0p7
179 8 4096 mmcblk0p8
179 9 16384 mmcblk0p9
179 10 8192 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 4096 mmcblk0p12
179 13 4096 mmcblk0p13
179 14 26916864 mmcblk0p14
179 32 4096 mmcblk0boot1
179 16 4096 mmcblk0boot0
Here's what "df" is showing :
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 960124 128 959996 0% /dev
/dev/block/platform/sdhci-tegra.3/by-name/APP
2064208 1110432 953776 54% /system
I've done so many things to try fixing this with all I could find googling, I may have done some mistakes in the process but I didn't spot any change. The only thing I haven't tried yet is to install/boot a rom from the external SD. But I'm not experienced enough for that, I prefer to keep as a last resort.
I just ran a dmesg command, there's several error messages there, maybe that'll help. As I can't post URLs yet, here's a sample :
<4>[ 12.192838] lost page write due to I/O error on mmcblk0p5
<3>[ 19.972559] mmcblk0: mmc_blk_err_check: general error sending status command, card status 0x80900
<4>[ 19.981660] mmcblk0: retrying write for general error
<4>[ 19.986857] lost page write due to I/O error on mmcblk0p14
<3>[ 20.217027] mmcblk0: packed cmd failed, nr 20, sectors 280, failure index: 0
<4>[ 20.693382] JBD2: recovery failed
<3>[ 20.696941] EXT4-fs (mmcblk0p14): error loading journal
I'm not sure how it works, maybe it's possible to manually wipe everything, keeping the bare minimum to recreate the partitions and push the files.
I may have missed something, some help would be really appreciated. ^^
Thanks in advance !
I have same problem!! Any solutions?
Same Problem here as well!
I have the same problem. Seems like the /cache and /data partitions are corrupt.
I have full CWM and Bootloader access with ADB and fastboot. I cannot flash new recoveries. Cannot mount /data or /cache.
Repairing the partitions with e2fsck get me nowhere as well.
I can shell in and run parted on the /data (mmcblk0p14) and /cache (mmcblk0p5) blocks. I attempted to recreate the partitions using parted but keep getting input/output error during write on /dev/block/mmcblk...
Can't even delete the old partitions in /data (mmcblk0p14) and /cache (mmcblk0p5) with fdisk. get failure error.
Any ideas how to overcome the partition recreation errors? Are we screwed?
Same problem here as well.
had cromix up and running, then suddenly black screen. Recovery working good, but mount errors. Cannot restore nandroid or flash any kind of rom.
realmastah said:
Same problem here as well.
had cromix up and running, then suddenly black screen. Recovery working good, but mount errors. Cannot restore nandroid or flash any kind of rom.
Click to expand...
Click to collapse
If you use TWRP, first try to wipe dalvik cache only and then try again to flash a rom or to restore a nandroid backup. This problem is TWRP related...
I had this exact issue when i was moving to lollipop. I tried to flash to zombi-x and it caused this issue. every time i turned the device on it would boot direct to recovery. I was unable to restore backups, flash new roms... nothing worked. In the end, i formatted my data partition and put blisspop on my external sd. After the format it took the new rom and has been running amazingly well since then.
Jerry1996 said:
If you use TWRP, first try to wipe dalvik cache only and then try again to flash a rom or to restore a nandroid backup. This problem is TWRP related...
Click to expand...
Click to collapse
thanks for the suggestion, tried it without success.
meanwhile i sent the device back as it was still under warranty, got refund.