Long story short, I screwed up my internal memory partition table and believe I've got it back.
Problem: I need a dump of /dev/block/blkmmc0p1 (and p5) if at ALL possible from anyone that has a working Nook.Color.
My problem is similar to this one: http://forum.xda-developers.com/showthread.php?t=918772
If only the files on this page were still active on Mediafire: http://forum.xda-developers.com/showthread.php?t=919353
That's the long and short of it. If you guys want some additional info I can provide any information, but as I said, a dump of someones boot partition would definitely help.
Thanks all!
-Josh
Your PM to me says you flashed my 3 zips. I generally don't respond directly to PMs, I prefer the forums. I assume you meant my three zips in my partition repair thread. The repair 145678 zip has a dump of that partition built onto it. So if that flashed successfully, and it still will not let you boot, finding another dump file will not help. If you want one, extract the one from there.
You may need to describe more what you have done and how it is acting now.
Sent from my Nook HD+ running CM10 on Hybrid SD
OK, I'll just start from the beginning with what I've done:
I have a Nook Tablet (not talking about it, just saying... I'm in the right forum lol) and a friend got a Nook Color and wanted to know if I could soup it up the same way.
Well I had it working and like an idiot, I accidently used the Nook Tablet "swap storage" routine to make /sdcard1 <-> /sdcard0 instead of the one for the Nook Color. It took the flash fine and upon reboot it claimed that the SD Card needed to be prepared so I let it format the "card"
That's all she wrote so far. I rebooted it again and it wouldn't even come on. It was at 30% power when I told it to reboot, so I figured it was plagued by the sleep of death so I let it charge all night.
Woke up, still nothing.
I made a CWM bootable SD card and LO AND BEHOLD, it started up without a hitch!!! But it complained constantly of "/cache" not mounting to store its log files (that was earlier today and it has been a LONG day so I cant recount the exact error message). When I tried to install the ROM again, however it failed all around.
Your partition 2 repair file failed at first for me, that's how bad it was.
After many different attempts, I setup a bootable SD card with Nookie and get a little further.
With Nookie, I was able to FINALLY adb into the device and fdisk -l /dev/block/mmcblk0 which revealed an empty table and with wrong cylinder, head, and sector count, which I fixed by using the information found here: http://forum.xda-developers.com/showthread.php?t=942324
After that, I remade my CWM bootable SD card and got better results. /cache errors are gone and I was able to use all three of your zip files for repairing partitions (forgive me for not having the file names handy).
That has gotten me a little further, but now I keep getting errors about /boot not mounting.
Also, I haven't just been using CWM, but also TWRP (which thinks my serial number is all 0s), but when I manually mount /rom I can see in the devconf folder that my serial number has been restored (before I recreated partition table and ran your 3 zips, that wasn't even the case).
I'm sorry this is so scatter brained. I've been at it for a solid 10 hours all while laid up in bed with walking pneumonia, so..yeah...fun times..
It could also be that I didn't partition it properly because partition 1 (the only 1) seems to lose it's file system type every time, while the other 7 remain intact.
If it did not have the proper cylinder head count, how did you repartition it? That quoted thread just says what the proper layout should be, not how to repartition it.
Sent from my Nook HD+ running CM10 on Hybrid SD
Well, I'm not EXACTLY a total n00b. I looked up the busybox/fdisk syntax.
First I did fdisk -C 965 -H 255 -S 63 /dev/block/mmcblk0 (as it was reporting nothing right)
That command got me the proper size of the disk and I, with help of the "m" help command" recreated it to this (now that I have adb working in TWRP, I'm back to my preferred parted, so this is not an fdisk printout, but a parted printout):
Number Start End Size Type File system Flags
1 32.3kB 74.0MB 74.0MB primary fat32 boot, lba
2 74.0MB 148MB 74.0MB primary fat32 lba
3 148MB 461MB 313MB primary ext2
4 461MB 7937MB 7477MB extended
5 461MB 938MB 477MB logical ext2
6 938MB 1941MB 1003MB logical ext3
7 1941MB 2311MB 370MB logical ext3
8 2311MB 7937MB 5626MB logical fat32 lba
In the past 5 minutes I have used mklabel to wipe partition table (shown above) again and am recreating them... again.
----EDIT-----
Here is that redone partition table:
Model: MMC SEM08G (sd/mmc)
Disk /dev/block/mmcblk0: 7944MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 512B 74.0MB 74.0MB primary fat32 boot, lba
2 74.0MB 148MB 74.0MB primary fat32 lba
3 148MB 461MB 313MB primary ext2
4 461MB 7944MB 7483MB extended lba
5 461MB 938MB 477MB logical ext2
6 938MB 1941MB 1003MB logical ext2
7 1941MB 2311MB 370MB logical ext2
8 2311MB 7944MB 5633MB logical fat32 lba
I'm not exactly a noob either and I could not find that -c -h -s command. I've been looking for that forever because I have a device that is showing the wrong count. So thanks.
Let me know how that new repartition comes out. I'll help if I can. I have all the images if you need them.
Sent from my Nook HD+ running CM10 on Hybrid SD
New layout:
Number Start End Size Type File system Flags
1 512B 74.0MB 74.0MB primary fat32 boot, lba
2 74.0MB 148MB 74.0MB primary fat32 lba
3 148MB 461MB 313MB primary ext2
4 461MB 7944MB 7483MB extended lba
5 461MB 938MB 477MB logical ext2
6 938MB 1941MB 1003MB logical ext2
7 1941MB 2311MB 370MB logical ext2
8 2311MB 7944MB 5633MB logical fat32 lba
Of your 3 zips, 1, 4, 5, 6, 7, 8 repair seemed to work without error, but I'm back to partition 2 repair not working. ARGH, talk about a step backwards LOL.
jmh363905 said:
New layout:
Number Start End Size Type File system Flags
1 512B 74.0MB 74.0MB primary fat32 boot, lba
2 74.0MB 148MB 74.0MB primary fat32 lba
3 148MB 461MB 313MB primary ext2
4 461MB 7944MB 7483MB extended lba
5 461MB 938MB 477MB logical ext2
6 938MB 1941MB 1003MB logical ext2
7 1941MB 2311MB 370MB logical ext2
8 2311MB 7944MB 5633MB logical fat32 lba
Of your 3 zips, 1, 4, 5, 6, 7, 8 repair seemed to work without error, but I'm back to partition 2 repair not working. ARGH, talk about a step backwards LOL.
Click to expand...
Click to collapse
I hope you saved an image of p3. That is critical.
Sent from my Nook HD+ running CM10 on Hybrid SD
leapinlar said:
I hope you saved an image of p3. That is critical.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
Hope of backing up any partitions went bye bye when I had to recreate the partition table the first time.
Now, is that the partition with devconf files or the factory.zip partition?
I'm still a bit unclear on that.
jmh363905 said:
Hope of backing up any partitions went bye bye when I had to recreate the partition table the first time.
Now, is that the partition with devconf files or the factory.zip partition?
I'm still a bit unclear on that.
Click to expand...
Click to collapse
P2 is the one with the devconf files. P3 has the factory.zip, but more importantly it has the rombackup.zip which was the backup of p2 when it was manufactured. That is what my p2 repair zip uses when it reconstructs p2. If you don't have that info, you will never be able to boot to stock again. But we can make dummy info so it can boot to CM. If you got a backup of the p2 before it died, you will be ok.
BTW, I just used your fdisk commands to fix my bad cylinder count. Thank you.
Sent from my Nook HD+ running CM10 on Hybrid SD
BTW, I just used you fdisk commands to fix my bad cylinder count. Thank you.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
No prob. That file is LOOOONG gone, but my only hopes are running CM10. Stock is for lusers. I have the serial number and wifi mac address written down so if we need to fake a few things, ANY help you can offer to get this thing working will be great.
I DID forget to mention that I have a TWRP backup of the Boot, Cache, System, and Data, but it won't restore :-/ I'm sure they're filled with all kinds of goodies.
Again, ANY HELP would be so great.
You tell me what you need me to submit and I'll be more than happy.
assert failed: (getprop("ro.product.device:") == "zoom2" || get prop("ro.build.product") == "zoom2") || getprop("ro.product.overallname:" == "NOOKcolor")
^^^ an error I'm getting trying to "install" the romrestore.zip file from my TWRP backup files. I'm not an expert, but is that saying my device and product name have been changed to something they shouldn't be?
jmh363905 said:
No prob. That file is LOOOONG gone, but my only hopes are running CM10. Stock is for lusers. I have the serial number and wifi mac address written down so if we need to fake a few things, ANY help you can offer to get this thing working will be great.
I DID forget to mention that I have a TWRP backup of the Boot, Cache, System, and Data, but it won't restore :-/ I'm sure they're filled with all kinds of goodies.
Again, ANY HELP would be so great.
You tell me what you need me to submit and I'll be more than happy.
Click to expand...
Click to collapse
You need to make three files to put in the devconf folder.
DeviceID has your 16 digit serial number
SerialNumber has the same info
MACAddress has your 12 digit MACaddress with no spaces or colons.
Also BootCnt should automatically get made by the system. It will not hurt to have a dummy one there. 4 bytes with nothing in it. That is the one that triggers an 8failed boot reset if it ever gets up to 8 in that file.
Also in the main folder should be a file call BCB (which means Boot Control Block). That should get created automatically by TWRP or CWM.
You get all that in there and flash a CM ROM and it should boot.
P3 does not matter unless there is a problem and stock recovery needs it. As long as you make sure that the DeviceID file is intact, you will never need p3.
Sent from my Nook HD+ running CM10 on Hybrid SD
---------- Post added at 06:50 PM ---------- Previous post was at 06:47 PM ----------
jmh363905 said:
assert failed: (getprop("ro.product.device:") == "zoom2" || get prop("ro.build.product") == "zoom2") || getprop("ro.product.overallname:" == "NOOKcolor")
^^^ an error I'm getting trying to "install" the romrestore.zip file from my TWRP backup files. I'm not an expert, but is that saying my device and product name have been changed to something they shouldn't be?
Click to expand...
Click to collapse
No, it is because the original device name was zoom2. You do not want to flash that anyway, since you do not have a working p3. It does the same as my repair p2 zip.
Sent from my Nook HD+ running CM10 on Hybrid SD
OK from ADB Shell, here are my commands so far:
cd /
mkdir rom
mount /dev/block/mmcblk0p2 rom
cd /rom
mkdir devconf
echo 2011460062572006 > DeviceID
echo 2011460062572006 > SerialNumber
echo 58671A19B85F > MACAddress
Do I need to chmod these files as well?
jmh363905 said:
OK from ADB Shell, here are my commands so far:
cd /
mkdir rom
mount /dev/block/mmcblk0p2 rom
cd /rom
mkdir devconf
echo 2011460062572006 > DeviceID
echo 2011460062572006 > SerialNumber
echo 58671A19B85F > MACAddress
Do I need to chmod these files as well?
Click to expand...
Click to collapse
Nope, once you verify those files are really there, just flash a CM ROM.
edit, well now that I think about it you might want to set it for 644. I usually flash those and that is what CWM sets them as.
Sent from my Nook HD+ running CM10 on Hybrid SD
leapinlar said:
Nope, once you verify those files are really there, just flash a CM ROM.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
-- Install /sdcard/cm-10-20130324-NIGHTLY-encore.zip ...
Finding update package....
Opening update package....
Installing update.... (a couple minutes like it's doing something)
*Verifying filesystems....
* Verifying partition sizes...
E: Unable to mount '/boot' (tw_mount)
E: Unable to mount '/emmc' (tw_mount)
E: Unable to mount '/emmc' (tw_mount)
E: Failed to mount /emmc (Invalid argument)
E: Failed to mount /emmc (Invalid argument)
E: Failed to mount /emmc (Invalid argument)
Rebooting system after that yields in the same ole same ole: First, using the software reboot failes.....always.. I'm taken to a blank (not backlit) screen that I have to press and hold Power + Nook. If I press both of these and an SD card is present, I'll get recovery again. If an SD card isn't present, it just sits there with a blank screen. (not backlit)
Ready to put a hole through it. LOL
jmh363905 said:
-- Install /sdcard/cm-10-20130324-NIGHTLY-encore.zip ...
Finding update package....
Opening update package....
Installing update.... (a couple minutes like it's doing something)
*Verifying filesystems....
* Verifying partition sizes...
E: Unable to mount '/boot' (tw_mount)
E: Unable to mount '/emmc' (tw_mount)
E: Unable to mount '/emmc' (tw_mount)
E: Failed to mount /emmc (Invalid argument)
E: Failed to mount /emmc (Invalid argument)
E: Failed to mount /emmc (Invalid argument)
Rebooting system after that yields in the same ole same ole: First, using the software reboot failes.....always.. I'm taken to a blank (not backlit) screen that I have to press and hold Power + Nook. If I press both of these and an SD card is present, I'll get recovery again. If an SD card isn't present, it just sits there with a blank screen. (not backlit)
Ready to put a hole through it. LOL
Click to expand...
Click to collapse
Two things, look at my edit above. And did you format those partitions after creating them? You need to. flashing my repair zip and format zips will take care of 145678. You still need to manually format p2 as fat32.
Edit: It looks to me like TWRP is doing some more checking that CWM does not do. You might try using CWM while trying to fix this. Also the new TWRPs do not like my zips.
Sent from my Nook HD+ running CM10 on Hybrid SD
leapinlar said:
Two things, look at my edit above. And did you format those partitions after creating them? You need to. flashing my repair zip and format zips will take care of 145678. You still need to manually format p2 as fat32.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
I verified that the files were still present after a reboot and they were (plus a Lost+Found directory indicates that there's an active, formatted partition), but I am going to go ahead and format both boot and rom with FAT32 file system:
ADB Shell Commands:
mkfs.vfat /dev/block/mmcblk0p1
mkfs.vfat /dev/block/mmcblk0p2
Then attempted restoring again. Same process as before, except NO errors AT ALL this time, so seeing it as a ray of hope, I followed it up with the GApps package (in hopes that THIS IS IT....)
Good news, PROGRESS has been made:
Now, WITHOUT an SD card, the unit will power on and give me the Cyanoboot Bootloader, but just hangs at loading from EMMC 01
What do you suggest now? ( and when this is all said and done with I'm gonna be needing your PayPal account so I can thank you)
Those other partitions need formatting too. Use my 5678 format zip.
Sent from my Nook HD+ running CM10 on Hybrid SD
Related
Whenever I try to format /data through CWM 3.0.2.8, it returns the message.
error while formatting /data
Click to expand...
Click to collapse
Also when I try to restore a backup, CWM cannot format /data.
I've also tried to install CM7. It says it completed its install in CWM but when I reboot, it retains the OS (rooted stock 1.2) I was currently on.
Me too. I just updated to MR1 and I am trying to restore the /data directory and I can't.
There's one thing I noticed about this refurb'd nook color. The space available in the device info is 1GB. Shouldn't it be higher or did they change the file structure with the latest models?
Also, I went into ADB and mounted EMMC. The last modified date for the files in there is May 4th.
Edit
Not sure if this would help.
~ # fdisk -l /dev/block/mmcblk0
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 (LB
A)
/dev/block/mmcblk0p2 10 18 72292+ c Win95 FAT32 (LB
A)
/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 (LB
A)
~ #
Click to expand...
Click to collapse
~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC SEM08G (sd/mmc)
Disk /dev/block/mmcblk0: 7944MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32.3kB 74.0MB 74.0MB primary fat32 boot, lba
2 74.0MB 148MB 74.0MB primary fat32 lba
3 148MB 461MB 313MB primary ext2
4 461MB 7937MB 7477MB extended
5 461MB 938MB 477MB logical ext2
6 938MB 6490MB 5552MB logical ext3
7 6490MB 6860MB 370MB logical ext3
8 6860MB 7937MB 1077MB logical fat32 lba
(parted)
Click to expand...
Click to collapse
Someone responded back to me on this forum.
http://androidforums.com/b-n-nookcolor/333668-format-internal-partition.html#post2672750
Barnes & Noble has started shipping new NOOK Color devices that are partitioned to allow only 1 GB of "user sideloaded" storage. The remaining 7 GB are partitioned for the OS, apps from the new B&N Apps store, and items downloaded directly from B&N. For the typical (non-rooted) device, the user would have to use the microSD slot for additional storage. I suspect you got one of the newly partitioned devices, which is why you are now seeing only 1 GB instead of the previous 5 GB of storage available.
Click to expand...
Click to collapse
Is there anyway to repartition the new devices or I'm stuck with this? If not, it's going to prevent me from dualbooting. This might also be the cause of my second problem, installing CM7 and still ending up with the original OS.
Oh man am I glad I found this thread. I was freakin' out when I couldn't load phiremod onto my newly purchased NC. Turns out I can only see 1GB of storage like the others in this thread. Hopefully some one will find a way to repartition the newer devices otherwise I am stuck with a rooted NC running the stock ROM with no way to return it.
You can just "Reset to factory default" and it'll remove the root. Then you can try to return it or exchange it. I'd probably say this if they ask for a reason...
"It's showing 1GB space as opposed to 8GB space as advertised"
Though I'm wondering why install CM7 doesn't change anything. After installation, it still boots up the stock OS.
jb7038 said:
You can just "Reset to factory default" and it'll remove the root. Then you can try to return it or exchange it. I'd probably say this if they ask for a reason...
"It's showing 1GB space as opposed to 8GB space as advertised"
Though I'm wondering why install CM7 doesn't change anything. After installation, it still boots up the stock OS.
Click to expand...
Click to collapse
Trying to load new ROMS fails because I can't do a data wipe as instructed.
I wonder if they made it so that outside sources can't write or modify /data now but it's still rootable with manualnooter.. I can format the other partitions through CWM and restore them easily.
EDIT
http://www.barnesandnoble.com/nookcolor/features/index.asp?cds2Pid=35583
*1GB = 1 billion bytes; Actual formatted capacity may be less. Approximately 5GB available to store content, of which up to 4GB may be reserved for content purchased from the Barnes & Noble NOOK Store.
I am not sure what kind of security they could have on the actual partitions, but the dual boot ROMS show that resizing the partitions should not be to hard, though it does mean you may lose data (possibly).
I don't mind losing my /data. I rather be able to install CM7 or something on the EMMC as opposed to running it on the SD.
I'd be grateful if someone could show me how to partition it so it's back to the original partition, 4gb/4gb as opposed to 7gb/1gb I think.
I hope something is figured out soon.
Here's the solution to anyone following this thread.
http://forum.xda-developers.com/showpost.php?p=13971291&postcount=110
I had this problem too.. bought a brand new nook color... this is what i did using CWM 3.0.2.8 to boot off SD...
1. used manual nooter 4.5.6
(after applying had all types of popup force close messages about /media this /media that)
2. changed my patitions to match this post
http://forum.xda-developers.com/showpost.php?p=13003431&postcount=166
(Note: Although it said that it didnt write the partitions it actually did)
3. did the 8 boot reset and nook button reset...
(This didn't reset the partitions actually and I had 5.sumthin GB free space not 1GB as before)
4. Manual nooted again then installed Phiremod 6.2 and Dalingrin's Kernel 042411 for cm7....
Sparks1641 said:
I had this problem too.. bought a brand new nook color... this is what i did using CWM 3.0.2.8 to boot off SD...
1. used manual nooter 4.5.6
(after applying had all types of popup force close messages about /media this /media that)
2. changed my patitions to match this post
http://forum.xda-developers.com/showpost.php?p=13003431&postcount=166
(Note: Although it said that it didnt write the partitions it actually did)
3. did the 8 boot reset and nook button reset...
(This didn't reset the partitions actually and I had 5.sumthin GB free space not 1GB as before)
4. Manual nooted again then installed Phiremod 6.2 and Dalingrin's Kernel 042411 for cm7....
Click to expand...
Click to collapse
I did this too and it scared the crap out of me when it kicked me out of fdisk. I thought I hosed it for good. Then when I did the 8 resets it kept going into CWM on the 8th reset. It wasn't until I rebooted it from CWM did it go and reflash itself.
Man that was scary. I thought I had a $250 paper weight.
I was a little freaked out when the fdisk said it didn't work... But reading around I seen that its almost impossible to break it as long as you don't mess with the first 3 partitions so what was the worse case I figured... This must be an issue with the CWR though.. Probably just updating the CWR to format different sizes of the partitions... A format with offset and length feature in an advanced menu... then we can change the sizes to what we want.. But going forward until CWR gets updated every new nook probably gonna have to do the partition change... Not like that's a big deal...
I bought a Nook Color used off craigslist cus they "bricked" it. I thought, no prob, through in the CWM uSD card, erase the data and system, and throw 1.2 on to root.
Can't erase the Data!
They said it was only a few weeks old. I'm guessing it was a refurb with new partition, they tried to root it somehow, and messed it up, then gave up.
Let's hope this fixes it!
Let us know if the partition thing works.. that would be cool.. GL.....
Sparks1641 said:
Let us know if the partition thing works.. that would be cool.. GL.....
Click to expand...
Click to collapse
I did the repartition here:
http://forum.xda-developers.com/showthread.php?t=1094371
and it worked like a charm - finally have CM7 on my 4th Nook!
Thanks to DeanGibson.
I bought my NC last week and immediately rooted it with out a hitch using ManualNooter for stock 1.2. In the process of trying to flash Phiremod my NC locked up in CWM when doing a wipe data/factory reset as instructed. I did a hard reset and tried to load Phiremod any way, which failed. I ended up using the backup I made of the rooted clean stock OS and it is working.
I read this thread
http://forum.xda-developers.com/showthread.php?t=1077973
and mine has the same issue of a partitioned eMMC that only reports 1GB. This prevents me from loading custom ROMs and side loading any applications.
One of the posts on that last thread mentions how dual booting essentially repartitions your eMMC to allow for the said dual booting, so I tried the "Step 1" in the repartition process here...
http://forum.xda-developers.com/showthread.php?t=959461
And it failed, but did boot back into my stock rooted OS.
My question is...
Is there a way to repartition my NC with what seems to be a new partition scheme that B&N moved to so that I can load custom ROMs, sideload programs, and/or dual boot off of eMMC?
Would like to see this answered as well.
grab your oars....
I'm in the same boat.... I have the 1 gig partition on my new Nook.
I can boot from SD ok but I would rather blow out the stock and save my SD.
Help?
MBK
Anyone out there can help us repartition the newer nooks?
side load partition 1 gb on newer NC's
guys check this out. I am doing it now and will report back after I get this done.
http://forum.xda-developers.com/showthread.php?t=914690
boot repartition with stock 1.0.0 or 1.0.1, then side load 1.2 update from b&n site:
http://www.barnesandnoble.com/u/nookcolor-support-software-update/379002520/
If I read all this correctly.. this should do the trick. as well as re-enabling apk installs correctly with rooted stock?
Already tried that.
You'll get a 1.0.0 or 1.0.1 with 0 Space available and you cannot sideload because of that. All that does is re-write the folders and not partition it.
I even tried changing the factory.zip with an older version in the /emmc and did a system/data wipe through the 8 boot fails and power + n reset.
One possibility
jb7038 said:
Anyone out there can help us repartition the newer nooks?
Click to expand...
Click to collapse
If you are familiar with fdisk and mkfs.ext2 or are willing to learn, and can boot a rooted OS from the SDcard, it should be trivial to delete, resize, repartition, and reformat /data (0p6 -- ext3), /cache (0p7 -- ext3) and /media (0p8 -- vfat). Do note the size of the partitions (especially 0p7/cache) before deleting them.
Then, when you restart the NC, it should recreate the contents of /data and /media to virgin content (meaning you better have backed up any non-B&N content). You will have to reregister with B&N, so you should probably do this on an UNROOTED Nook.
This is an experiment that I have wanted to try, but have not had the time; I've been too busy doing other experiments, like having B&N do the intentional repartitioning. I was using internal dual boot before, but uninstalled it before the repartitioning, because I knew there would not be enough space for dual boot afterwards.
I'm just unfamiliar with the block sizes and the commands to partition/change it.
/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)
Click to expand...
Click to collapse
6 938MB 6490MB 5552MB logical ext3
7 6490MB 6860MB 370MB logical ext3
8 6860MB 7937MB 1077MB logical fat32 lba
Click to expand...
Click to collapse
____________________________________________
I do have the NC I'm suppose to send back that's fully wiped.
~ # 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
~ #
Click to expand...
Click to collapse
~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC SEM08G (sd/mmc)
Disk /dev/block/mmcblk0: 7944MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
(parted)
Click to expand...
Click to collapse
I'd be willing to partition it myself before I send it back if someone could walk me through it.
DeanGibson said:
If you are familiar with fdisk and mkfs.ext2 or are willing to learn, and can boot a rooted OS from the SDcard, it should be trivial to delete, resize, repartition, and reformat /data (0p6 -- ext3), /cache (0p7 -- ext3) and /media (0p8 -- vfat). Do note the size of the partitions (especially 0p7/cache) before deleting them.
Then, when you restart the NC, it should recreate the contents of /data and /media to virgin content (meaning you better have backed up any non-B&N content). You will have to reregister with B&N, so you should probably do this on an UNROOTED Nook.
This is an experiment that I have wanted to try, but have not had the time; I've been too busy doing other experiments, like having B&N do the intentional repartitioning. I was using internal dual boot before, but uninstalled it before the repartitioning, because I knew there would not be enough space for dual boot afterwards.
Click to expand...
Click to collapse
Dear God I would love to try but honestly I don't know a think about command line linux. Also, mine is already rooted, but I can always take it back to stock.
If someone gets this to work please document the process. I would really like to be able to use the internal memory for custom ROMs and be able to side load programs.
Anyone that can help us?
hi guys i am in a big mess
1)i tried installing official 2.3.5 final and my phone(u8800) started bootlopping after factory reset i managed to start it once.
2)i restarted my phone after rooting it and had again bootloops that i didnt ever manage to overcome.
3)so i desided that i should reflash official(and the desaster started)update failed on 99% and the worst bootloader locked .
4)i tried installing an official froyo also failed at 99% but bootloader unlocked
5)now i am on ubuntu able to see pink screen files but unfortunately i dont have dd back up but i have many back ups from cwm on my sd from custom roms is there any posibility to unbrick my phone?
ps for admin sorry for same thread but the other started writing in some unknown language to me
Can you access recovery?
So you downgraded to 2.2, which version B138?
can you try to access recovery? official will do for factory reset, if doesn't start again try to flash it again, and after that do wipe and factory reset from recocery...
I managed to downgrade like that also failed at 99% but with factory reset the phone started normally...
Atanasov Goran said:
So you downgraded to 2.2, which version B138?
can you try to access recovery? official will do for factory reset, if doesn't start again try to flash it again, and after that do wipe and factory reset from recocery...
I managed to downgrade like that also failed at 99% but with factory reset the phone started normally...
Click to expand...
Click to collapse
1)yes my 2.2 froyo is 138 from how to root ginerbred thread and after this flash i lost adb compatibility in windows so now i am in ground zero if ther is a way to flash something from ubuntu or backtrack in bootloader mode because even after that still no access to phone not even from pc on cwm to see my sd card
2)in simple boot my phone stacks on huawei logo,i can also get to recovery menu and finaly and i think the most helpfull i can get pink screen and mount my files on linux.
3)i have also try to recover in last saved working recovery (custom rom)
4)i think that something went wrong with my partitions but i realy need help from a developer because i dont know what to do
try this
try to wipe/factory reset from the official recovery, should start normaly after that, my phone did the same when i downgraded from 2.3 stoped at 99% and said that the update failed but after a factory reset booted normaly
Maybe a partition is damaged.
Try from linux on pink screen to check partitions for errors. Maybe you can fix it like this and after to successfully flash the update.
dancer_69 said:
Maybe a partition is damaged.
Try from linux on pink screen to check partitions for errors. Maybe you can fix it like this and after to successfully flash the update.
Click to expand...
Click to collapse
can you give some info how to do that i see 3 partitions of 105mb,235 and recovery partition only who auto mount and on gparted i see 4gb unreachable
do you mean just to check disk this partitions ?
I haven' t specific infos, I'm using linux very rear the last year. I think that you can use the fsck tool of linux. You can find a lot of info about how to check partitions for linux if you search on google. Just be careful to not format them or erase them.
Tranos said:
can you give some info how to do that i see 3 partitions of 105mb,235 and recovery partition only who auto mount and on gparted i see 4gb unreachable
do you mean just to check disk this partitions ?
Click to expand...
Click to collapse
You should see 13 partitions total if you look at the drive with parted or gparted etc.. And yeah you could run fsck on all the ext3/ext4/fat32 partitions. But if you don't see all the 13 partitions in parted / gparted then I think the partition table is damaged or some weird bootloader lock issue.
after some tries and stock reflashes i am now on official cwm recovery and trying to wipe data/factory resets returns me an error :
E:cant mount @(or /dev/block/mmcblk0p13) both wipe and format same error
can you candly send me the official recovery files and what should i have in(i think something after so many custom roms failed)
and this are the partitions i can see now
You could run gparted and note down all partitions which are ext3, ext4 or fat32. Then you can check the disks with "sudo fsck /dev/sdxx". Also I can post my partition table later when I'm on my comp so you could compare it to yours.
Sent from my u8800 using xda premium
thies are all partitions but i think there are too many anallocated
Code:
GNU Parted 2.3
Using /dev/sdd
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
Error: Invalid partition table on /dev/sdd -- wrong signature 0.
Ignore/Cancel? i
Model: Qualcomm MMC Storage (scsi)
Disk /dev/sdd: 3959MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 512B 252MB 252MB primary fat32
2 252MB 252MB 512kB primary boot
3 252MB 255MB 3072kB primary
4 255MB 3959MB 3704MB extended
5 268MB 281MB 12,6MB logical
6 336MB 472MB 136MB logical ext3
7 537MB 537MB 512kB logical
8 604MB 607MB 3146kB logical
9 671MB 678MB 7168kB logical
10 738MB 741MB 3146kB logical
11 805MB 808MB 3146kB logical
12 872MB 1103MB 231MB logical ext3
(parted)
2 partitions are missing
Here's how mine looks. I'm guessing you don't have a dd backup of the whole phone? Anyway if your partition table is messed up, it would be possible to clone my partition table. Only the partition table, and leaving all other data intact. It would probably be a good idea also to check with others if the partition table is always exactly the same on all phones, or if there are different flash mems or something with diff. tables. Also did you run fsck on 1,6,12 and 13?
Code:
$ [B]sudo parted /dev/sdc[/B]
GNU Parted 2.3
Using /dev/sdc
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) [B]p[/B]
Model: Huawei eMMC Storage (scsi)
Disk /dev/sdc: 3959MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 512B 252MB 252MB primary fat32
2 252MB 252MB 512kB primary boot
3 252MB 255MB 3072kB primary
4 255MB 3959MB 3704MB extended
5 268MB 281MB 12.6MB logical
6 336MB 472MB 136MB logical ext4
7 537MB 537MB 512kB logical
8 604MB 607MB 3146kB logical
9 671MB 678MB 7168kB logical
10 738MB 741MB 3146kB logical
11 805MB 808MB 3146kB logical
12 872MB 1103MB 231MB logical ext2
13 1141MB 1770MB 629MB logical ext4
14 1812MB 3959MB 2147MB logical fat32
(parted)
do you know how ican fix my partitions again or should i sent it to service tbh it is huawei fault that my phone doesnt work now
I checked my partition table(I have 2.3 installed, not 2.2) and are same that ksata' s, except partition 12 which is in ext3, not ext2.
But I think that on 2.2 rom the partition table has 12 partitions and not 14(I've used command cat /proc/mounts some times when a was on 2.2 rom and always partitions count was until 12). So, I don' t think that it' s something wrong with the partition table.
But maybe some of the existing partitions is damaged and when update tries to write on it, gets an error and update stops.
You can check the ext2/3/4 partitions from gparted. First umount a partition end then check it(if you right click on a partition these options are available on the menu)
Looks like I have bricked mine too.. pretty badly. When updating to 2.3 if fails at step 2 (40 %) and shows "update failed" (same with 2.2). Can't access recovery either. In pink screen Windows and Ubuntu doesn't mount any partitions..
Looks like I have to send it in to change motherboard, but if any have suggestions how to fix it please tell me
ps. was on Cm7 before this happened.
skifyr123 said:
Looks like I have bricked mine too.. pretty badly. When updating to 2.3 if fails at step 2 (40 %) and shows "update failed" (same with 2.2). Can't access recovery either. In pink screen Windows and Ubuntu doesn't mount any partitions..
Looks like I have to send it in to change motherboard, but if any have suggestions how to fix it please tell me
ps. was on Cm7 before this happened.
Click to expand...
Click to collapse
Try to flash using internal SD card. Also, one user reported that removing battery worked.
Blefish said:
Try to flash using internal SD card. Also, one user reported that removing battery worked.
Click to expand...
Click to collapse
How to access internal when you can't boot (not even to recovery)? Tried to remove battery, but didn't work..
1)i managed to solve my problem by using the genokolars re-partition to stock from modaco and the partition zip that is at a reply of him not post start thank you everybody for the try .and after reflashed the chinese stock 162
2)but now i have nulled imei can i restor it by some clock works recoveries or ther is no way to restore it(i dont have dd back up)
skifyr123 said:
How to access internal when you can't boot (not even to recovery)? Tried to remove battery, but didn't work..
Click to expand...
Click to collapse
Have the same issue. Did you try to work it out somehow?
Try look at my thread here:
http://forum.xda-developers.com/showthread.php?t=1466953
A friend of mine tried to install CM7 on his NookColor. Something went wrong and so he brought it to me. I've done dozens of these. I thought it would be an easy fix so I stuck in my trusty SD boot card with encore_CM72-MiRaGe-03042012. I booted into CWM and did a factory reset and installed encore_CM72-MiRaGe-03042012. I booted it up and expected it to be fixed.
It did the same thing this time which is to boot to the initial splashcreen and then go blank. You can tell the screen is still backlit, but it never changes. You have to hold the power button for 30 seconds to turn it off.
When I boot back into CMW I see some unexpected messages
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 tried installing CM7 again and watched the messages closely. It says
Installeding update
Install from sdcard complete.
Reboots the same way
Can anyone point me in the right direction to fix this? Thanks
Well, I spent all day yesterday Googling and searching all the forums on XDA Of course I started with Dummies Guide to Fixing 'My Nook Won't Boot'. It is incredibly out of date and is likely to do more harm than good. I think that if it is going to be a sticky, then at least it should show current, relevant information.
I tried [HOW-TO] : Restore Nook Color back to stock EASILY!. I was unable to format several of the partitions specified, but proceeded anyway. It appeared to install OK, but now I am stuck at the N when it boots.
I am continuing to search but I keep running into dead links, downloads that say they will take 5 hours, and references to outdated files. I really would appreciate some knowledgeable help here guys. Thanks
I have the same deal. I think since the WIP clockwork update. I've tried most of the fixes from the links as I still have most. I tried everything you have as well as trying restoring and using different versions of clockwork and trying to get a cache up to no avail. The please keep me posted because this is the first replica of my situation. I am using an Asus t101 now so I'm in no hurry but I've had me NC forever and love the reading size.
Good luck.
How do you create or fix the cache for e:? I can you ADB into clockwork?
Just in case anyone ever reads this thread I thought I would give some more information regarding my problem.
I am able to get into CWM 3.2.0.1 internally. I stiil can't get any ROM loaded though. ( I have loaded several different ROMS to the NC previously including the CM7 nightlies from 75 to 130, so I am well versed in how to do it).
I'm thinking there is something wrong with my partitons. I'm not well versed in exactly what happens during the boot process and what is on each partiton.
I though it might be useful for those people who know about this stuff if I supplied more info (since my eyesight is giving out from reading so many threads)
If I go into the mounts and storage menu and do severals format, this is what I get.
Format system - Error formatting /system!
Format data- Error formatting /data!
Format cache- Error formatting /cache!
I was afraid to format emmc or boot.
Does this help anyone?
Have you tried creating a bootable CWM SD card? That always helps me out when things get screwy.
Tried the EMMC recovery repair?
p.s. - NEVER format Boot. You'll have many a difficulty if you do.
I do have a CWM SD card and can boot to that as well.
Neither one works. I tried installing
nookcolor_1_4_1_update.zip
update-nc-stock-1.3.zip
encore_CM72-MiRaGe-03232012.zip
All leave me where I am now
How old is the nook?
What happened when your friend tried to install cm7? What was going on with it prior to installation?
Don't really have much info.
I have no idea how old the NC is.
I believe that the guy had stock B&N running and tried to install CM7 (verson unknown) with a bootable microSD card, I don't know if he was using the latest CWM on the card.
Um........mail it to me. I'll fix it.
Minimum fees apply.
Here's another clue.
I have a dual boot SD card made based on the instructions in
[ROMS]NEW! Dualboot Mirage CM7 / ICS CM9 Image for SDcard [3/26].
If I use it on a stock B&N NC, the SD card works correctly.
If I use it in the borked NC, it still boots into a black screen.
I would prefer to try to resolve this mayself. I have 20+ years in PC support and feel if I can just get the right information, I can fix it.
If I can't get it done in the next 3 or 4 days, I may take you up on it. However, the frind would have to OK it and I don't know how he feels about sending it off. Thanks
BTW, I tried plugging in the USB cable to see if maybe I could try some ADB magic, but the laptop slings an error when trying to load the driver.
Let me amend that last post. I tried the dual boot (this time using the alternate boot image) and successfully got into CM9. Does this help me?
I am trying to find a way to fdisk or mount a way to change pemissions to rw,mode=0755 or but cannot find the usb yet. I will see what I can google.
Seems the emmc permissions are wrong possibly.
Edit: this is what my mount says about the nook when I mount it to linux:
/dev/sdb on /media/0838-AA8D type vfat (rw,nosuid,nodev,uid=1000,gid=1000,shortname=mixed,dmask=0077,utf8=1,showexec,flush,uhelper=udisks)
Since I have thee NC booting to CM9 off the SD card, I thought I would load ADB and see if there was something I could do..
I went to [Ref] Nook Color Links |Guides|How To|Utilities| Etc. 12/26 Read FIRST =) in the developer's section and went to the referenced
•Nook Color USB Drivers and ADB Setup (WinXP&7)
The links in that thread are dead. Can someone point out a link to the current prefered method?
have you tried
[UPDATE ZIP] Stock 1.2 update.zip flashable from CWM
from showthread.php?t=1050520
This is nookcolor easy adb 3:
http://db.tt/b3XfztAY
And the USB files file NC:
nookcolor usb
http://db.tt/QRhksG2n
Hi there,
If you are able to boot to CM9 off the sDcard. Try opening up terminal emulator and enter the following commands:
Code:
$ su
# fdisk -l /dev/block/mmcblk0
and paste the output here. That should give you you're EMMC partition layout.
-Racks
Yeah, what racks said. Sounds like you formatted your emmc boot partition to me. In one of the old resurrected threads that you posted to, the OP flat out says they formatted boot.
Don't format boot, everyone.
Post the output of racks command, and we'll know for sure.
If you just formatted (read: erased) the boot partition, then your ROM partition should be intact. That means 8 failed reboot can load the stock firmware. It may be a last-ditch effort for many, but it doesn't require any adb knowledge our even a computer, so I tend to recommend it early.
Reboot as it is loading the cyanogen screen eight times while holding down power,n, and the volume keys. If it doesn't work the first time, do the entire sequence again. Of course, if you enter rack's command, you will see if your ROM partition is still intact which is required for this method to work.
[email protected]:/ # fdisk -l /dev/block/mmcblk0
Warning: invalid flag 0x00,0x00 of partition table 5 will be corrected by w(rite)
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 935 7060567+ 5 Extended
[email protected]:/ #
Bonnie_Raitt said:
[email protected]:/ # fdisk -l /dev/block/mmcblk0
Warning: invalid flag 0x00,0x00 of partition table 5 will be corrected by w(rite)
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 935 7060567+ 5 Extended
[email protected]:/ #
Click to expand...
Click to collapse
Yep, your missing the last 4 partitions which are /system, /data, /cache, /media. Which you would need to flash any rom. You're gonna have to re-create them by using fdisk from and SDcard ROM (eg. CM7 or CM9). There's a thread here somewhere that dealt with all that. I'll browse through and see if I can find it for you.
-Racks
This it?
http://forum.xda-developers.com/showthread.php?t=958748
Not sure how to rebuild the missing partitions yet. Appreciate the help fellas.
[SOLVED: See last post]
Hi everybody !
That's aLL... I just flashed a SBF, performed a factory reset from motorola's recovery, rooted my phone, installed 2ndinit 2.3, flashed TWRP 2.6.3.0 and then Quark's 2014 01 20 CM11 build.
Did I miss some step in order to get the card mounted in recovery ?
By the way I can easily access it plugging the USB cable on my Ubuntu Linux desktop and choosing MTP/PTP/USBstorage.
EDIT: it was previously formatted ( it's a 32GB class 10 U1 card ) as a fat32 partition on Windows7
Alka-Seltzer PLUS said:
Hi everybody !
That's aLL... I just flashed a SBF, performed a factory reset from motorola's recovery, rooted my phone, installed 2ndinit 2.3, flashed TWRP 2.6.3.0 and then Quark's 2014 01 20 CM11 build.
Did I miss some step in order to get the card mounted in recovery ?
By the way I can easily access it plugging the USB cable on my Ubuntu Linux desktop and choosing MTP/PTP/USBstorage.
EDIT: it was previously formatted ( it's a 32GB class 10 U1 card ) as a fat32 partition on Windows7
Click to expand...
Click to collapse
Your SDcard is visible from file manager?
If not than is better to format it in a ... compact camera or something like this.!
pgreed said:
Your SDcard is visible from file manager?
If not than is better to format it in a ... compact camera or something like this.!
Click to expand...
Click to collapse
Thanks for your answer !
Yes it is; I can mount it on my desktop too as I previously said.
This happened to me 2 times after having installed Quarx's CM11 with the steps described before
Plugging it on my desktop results in a mounted partition on the file explorer ( nautilus ) but as an unmounted on the partitioning app ( Gparted ) with a broken filesystem but I am able to copy files
Bump!
Alka-Seltzer PLUS said:
Bump!
Click to expand...
Click to collapse
As I said before something similar happened to me and the only solution was to re-format entire SDcard in a compact camera. I tried to format in a android tablet and in the phone but always it gave errors. After formatted in camera all work fine and no error.
pgreed said:
As I said before something similar happened to me and the only solution was to re-format entire SDcard in a compact camera. I tried to format in a android tablet and in the phone but always it gave errors. After formatted in camera all work fine and no error.
Click to expand...
Click to collapse
I should try but ... uhm ... my question is: why does the same card mount ever on every recovery ( TWRP 2.6.3.0 included ) but not any more after 2014 01 20 build ?
If I would restart from scratch without doing anything on the card( flashing a SBF, root, 2ndinit, TWRP 2.6.3.0, CM11 ) it should be mounted until the first CM11's boot: I did it 2 days ago. I just used the same card without formatting it: TWRP 2.6.3.0 does mount it only on the first shoot.
After the first CM11's boot it won't be mounted anymore.
sudo fdisk -l
Code:
Disk /dev/sdc: 32.1 GB, 32090619904 bytes
64 testine, 32 settori/tracce, 30604 cilindri, totale 62676992 settori
Unità = settori di 1 * 512 = 512 byte
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Identificativo disco: 0x70707573
Questa non sembra una tabella delle partizioni.
Probabilmente è stato scelto il dispositivo sbagliato.
Dispositivo Boot Start End Blocks Id System
/dev/sdc1 ? 1701998450 3638285201 968143376 d Sconosciuto
/dev/sdc2 ? 1701995885 2246105740 272054928 a OS/2 Boot Manager
/dev/sdc3 ? 1769087090 3538458322 884685616+ 6f Sconosciuto
/dev/sdc4 ? 2885681152 2885734849 26849 a OS/2 Boot Manager
dmesg|tail
Code:
[16595.451780] sd 7:0:0:0: Attached scsi generic sg3 type 0
[16595.451862] sd 7:0:0:0: [sdc] No Caching mode page found
[16595.451871] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[16595.466630] sd 7:0:0:0: [sdc] No Caching mode page found
[16595.466647] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[16595.469344] sdc:
[16595.472449] sd 7:0:0:0: [sdc] No Caching mode page found
[16595.472461] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[16595.472471] sd 7:0:0:0: [sdc] Attached SCSI removable disk
[16595.775667] FAT-fs (sdc): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Oh LoL: it mounts flawlessy and really on the fly and I can manage aLL files!
sudo dosfsck -w -r -l -a -v -t /dev/sdc
Code:
dosfsck 3.0.16 (01 Mar 2013)
dosfsck 3.0.16, 01 Mar 2013, FAT32, LFN
Checking we can access the last sector of the filesystem
0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
Automaticaly removing dirty bit.
Boot sector contents:
System ID "MSDOS5.0"
Media byte 0xf8 (hard disk)
512 bytes per logical sector
65536 bytes per cluster
540 reserved sectors
First FAT starts at byte 276480 (sector 540)
2 FATs, 32 bit entries
1958912 bytes per FAT (= 3826 sectors)
Root directory start at cluster 2 (arbitrary size)
Data area starts at byte 4194304 (sector 8192)
489600 data clusters (32086425600 bytes)
63 sectors/track, 255 heads
0 hidden sectors
62676992 sectors total
...
...
...
Checking for bad clusters.
Reclaiming unconnected clusters.
Checking free cluster summary.
Performing changes.
/dev/sdc: 3703 files, 238236/489600 clusters
0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
Automaticaly removing dirty bit.
Click to expand...
Click to collapse
uhm ... I'm just writing zeros to the entire drive:
Code:
sudo dd if=/dev/zero of=/dev/sdc
Let's see if it helps
SOLVED
Okka roLLa !
So... trying to reformat the card via CM11 results in a random reboot; trying to wipe it on TWRP fails too.
I wrote zeros another 2 times in between and than i putted it into the defy, mounted it as USB Mass Storage in order to partition it with GParted creating 2 primary partitions ( 1024GB ext3 and aLL the other avaiable space FAT32 ) and now it is seen from recovery without mounting it :good:
I have the same problem: after installing any of the recent CM11 nightlies (since the autobot builds began), TWRP is unable to mount my sdcard. (It's a 16GB class 10 made by Topram.) I've tried fully formatting the card in my PC (as FAT32), also checked it for errors and bad sectors. So far as I can tell, there's nothing wrong with the card.
Earlier versions of CM11 (from pre-autobot builds, like the December 29th build) have no trouble mounting the card in recovery, and the latest builds of CM11 have no trouble reading from and writing to the card when the rom is fully booted; only TWRP is unable to mount it. Strangely, TWRP has no trouble mounting an older and slower 2GB card.
@Alka-Seltzer PLUS, I'd rather not use the workaround that you described above, because the last time I tried screwing around in TWRP trying to get it to mount the sdcard, I ended up hard-bricking my old defy.
So, does anyone know whether it is possible to replace the recovery in the latest nightlies with a recovery from an earlier build? I'm not sure exactly what files I'd need to replace in the CM11 zip file, or whether a simple replacement would even work. I tried taking what I thought were the correct files from the December 29th build and flashing them over the February 22 nightly, but that just soft-bricked the phone and I had to start over from sbf.
Proverbs2 said:
I have the same problem: after installing any of the recent CM11 nightlies (since the autobot builds began), TWRP is unable to mount my sdcard. (It's a 16GB class 10 made by Topram.) I've tried fully formatting the card in my PC (as FAT32), also checked it for errors and bad sectors. So far as I can tell, there's nothing wrong with the card.
Earlier versions of CM11 (from pre-autobot builds, like the December 29th build) have no trouble mounting the card in recovery, and the latest builds of CM11 have no trouble reading from and writing to the card when the rom is fully booted; only TWRP is unable to mount it. Strangely, TWRP has no trouble mounting an older and slower 2GB card.
@Alka-Seltzer PLUS, I'd rather not use the workaround that you described above, because the last time I tried screwing around in TWRP trying to get it to mount the sdcard, I ended up hard-bricking my old defy.
So, does anyone know whether it is possible to replace the recovery in the latest nightlies with a recovery from an earlier build? I'm not sure exactly what files I'd need to replace in the CM11 zip file, or whether a simple replacement would even work. I tried taking what I thought were the correct files from the December 29th build and flashing them over the February 22 nightly, but that just soft-bricked the phone and I had to start over from sbf.
Click to expand...
Click to collapse
Maybe there's a misunderstandig: the steps i described have been done with the microSD outside the phone; I did it with the card inserted in an adapter !
Alka-Seltzer PLUS said:
Maybe there's a misunderstandig: the steps i described have been done with the microSD outside the phone; I did it with the card inserted in an adapter !
Click to expand...
Click to collapse
Thanks for the reply. I'm still not sure that I understand your steps. Did you use gparted on your linux PC to create an ext3 partition and a FAT32 partition on the sdcard, then put the sdcard back into the phone and now TWRP recognizes it? If so, which partition does TWRP recognize, the ext3 or the FAT32?
In any case, I'd rather not resort to such a workaround, since I don't trust the latest version of the TWRP recovery (which hard-bricked my old defy). I would prefer to downgrade the recovery to the version that was working fine on the earlier CM11 builds (e.g. the December 29th build). Does anyone know how to do that?
Thanks in advance!
That's right: I did use gparted on my linux PC to create an ext3 partition and a FAT32 partition on the sdcard, then putted the sdcard back into the phone and now TWRP does recognize it.
The FAT32 is recognized, the ext3 i do not know because i did not look for it yet ^_^
Alka-Seltzer PLUS said:
That's right: I did use gparted on my linux PC to create an ext3 partition and a FAT32 partition on the sdcard, then putted the sdcard back into the phone and now TWRP does recognize it.
The FAT32 is recognized, the ext3 i do not know because i did not look for it yet ^_^
Click to expand...
Click to collapse
Wow, that actually worked! I just used gparted to fix the partition table and reformat the entire sdcard as FAT32 (I only created one partition), and now the card is recognized in TWRP! :good:
Apparently there was something wrong with the partition tables on my sdcard, and even a full format in Windows 7 didn't fix it, nor did the Windows disk check utility detect the problem, but Linux saves the day again!
Alka-Seltzer PLUS said:
I should try but ... uhm ... my question is: why does the same card mount ever on every recovery ( TWRP 2.6.3.0 included ) but not any more after 2014 01 20 build ?
If I would restart from scratch without doing anything on the card( flashing a SBF, root, 2ndinit, TWRP 2.6.3.0, CM11 ) it should be mounted until the first CM11's boot: I did it 2 days ago. I just used the same card without formatting it: TWRP 2.6.3.0 does mount it only on the first shoot.
After the first CM11's boot it won't be mounted anymore.
sudo fdisk -l
Code:
Disk /dev/sdc: 32.1 GB, 32090619904 bytes
64 testine, 32 settori/tracce, 30604 cilindri, totale 62676992 settori
Unità = settori di 1 * 512 = 512 byte
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Identificativo disco: 0x70707573
Questa non sembra una tabella delle partizioni.
Probabilmente è stato scelto il dispositivo sbagliato.
Dispositivo Boot Start End Blocks Id System
/dev/sdc1 ? 1701998450 3638285201 968143376 d Sconosciuto
/dev/sdc2 ? 1701995885 2246105740 272054928 a OS/2 Boot Manager
/dev/sdc3 ? 1769087090 3538458322 884685616+ 6f Sconosciuto
/dev/sdc4 ? 2885681152 2885734849 26849 a OS/2 Boot Manager
dmesg|tail
Code:
[16595.451780] sd 7:0:0:0: Attached scsi generic sg3 type 0
[16595.451862] sd 7:0:0:0: [sdc] No Caching mode page found
[16595.451871] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[16595.466630] sd 7:0:0:0: [sdc] No Caching mode page found
[16595.466647] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[16595.469344] sdc:
[16595.472449] sd 7:0:0:0: [sdc] No Caching mode page found
[16595.472461] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[16595.472471] sd 7:0:0:0: [sdc] Attached SCSI removable disk
[16595.775667] FAT-fs (sdc): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Oh LoL: it mounts flawlessy and really on the fly and I can manage aLL files!
sudo dosfsck -w -r -l -a -v -t /dev/sdc
Code:
dosfsck 3.0.16 (01 Mar 2013)
dosfsck 3.0.16, 01 Mar 2013, FAT32, LFN
Checking we can access the last sector of the filesystem
0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
Automaticaly removing dirty bit.
Boot sector contents:
System ID "MSDOS5.0"
Media byte 0xf8 (hard disk)
512 bytes per logical sector
65536 bytes per cluster
540 reserved sectors
First FAT starts at byte 276480 (sector 540)
2 FATs, 32 bit entries
1958912 bytes per FAT (= 3826 sectors)
Root directory start at cluster 2 (arbitrary size)
Data area starts at byte 4194304 (sector 8192)
489600 data clusters (32086425600 bytes)
63 sectors/track, 255 heads
0 hidden sectors
62676992 sectors total
...
...
...
Checking for bad clusters.
Reclaiming unconnected clusters.
Checking free cluster summary.
Performing changes.
/dev/sdc: 3703 files, 238236/489600 clusters
uhm ... I'm just writing zeros to the entire drive:
Code:
sudo dd if=/dev/zero of=/dev/sdc
Let's see if it helps
Click to expand...
Click to collapse
I think the problem here is that there is no partition table on your card, just a file system; you put a file system directly on the sd card, rather than creating a single partition spanning all of the card. Your file system would end up on /dev/block/mmcblk0 rather than /dev/block/mmcblk0p1, and twrp.fstab doesn't include an entry for that, so it doesn't get mounted.
This might be easy to fix, but testing the fix might also hard-brick the phone in question, as Proverbs2 discovered. It doesn't seem to be a hardware issue, and the overwhelming standard is for SD cards to have a partition table, so we're probably best off warning about such cards and not touching them at all. Whatever software you used to format your SD card initially needs to be fixed, though.
Proverbs2 said:
So, does anyone know whether it is possible to replace the recovery in the latest nightlies with a recovery from an earlier build? I'm not sure exactly what files I'd need to replace in the CM11 zip file, or whether a simple replacement would even work. I tried taking what I thought were the correct files from the December 29th build and flashing them over the February 22 nightly, but that just soft-bricked the phone and I had to start over from sbf.
Click to expand...
Click to collapse
I think there was a recent change to use separate kernels for recovery and normal 2nd-boot. You'd need to replace /system/bootmenu/2nd-boot/ramdisk-recovery with the old /system/bootmenu/2nd-boot/ramdisk-recovery and /system/bootmenu/2nd-boot/zImage-recovery with the old /system/bootmenu/2nd-boot/zImage (no "-recovery" suffix), I think, and I'd expect it to just work then. Don't touch the new /system/bootmenu/2nd-boot/ramdisk and /system/bootmenu/2nd-boot/zImage.
[PROBLEM SOLVED Time ago]
PhilipCetero said:
I think the problem here is that there is no partition table on your card, just a file system; you put a file system directly on the sd card, rather than creating a single partition spanning all of the card. Your file system would end up on /dev/block/mmcblk0 rather than /dev/block/mmcblk0p1, and twrp.fstab doesn't include an entry for that, so it doesn't get mounted.
This might be easy to fix, but testing the fix might also hard-brick the phone in question, as Proverbs2 discovered. It doesn't seem to be a hardware issue, and the overwhelming standard is for SD cards to have a partition table, so we're probably best off warning about such cards and not touching them at all. Whatever software you used to format your SD card initially needs to be fixed, though.
Click to expand...
Click to collapse
Alka-Seltzer PLUS said:
SOLVED
Okka roLLa !
So... trying to reformat the card via CM11 results in a random reboot; trying to wipe it on TWRP fails too.
I wrote zeros another 2 times in between and than i putted it into the defy, mounted it as USB Mass Storage in order to partition it with GParted creating 2 primary partitions ( 1024GB ext3 and aLL the other avaiable space FAT32 ) and now it is seen from recovery without mounting it :good:
Click to expand...
Click to collapse
Thanks for your answer but I do not realize what was wrong doing it my way ( now the card gets mounted ) !
After having write zeros on the card i tried to partition it in 3 different ways:
1) Booting up CM11 and letting it ask to format the empty card ( I thought it was supposed to create a partition table with a FAT32 partition spanning all the space on the microSD ) but it always resulted in a random reboot and a not partitioned card.
2) Entering TWRP and letting it partition the SDcard using its menu: it returns that the recovery tries to mount any partition which is supposed to be created from an empty card Maybe the card should have had at least a partition table in order to be partitioned ? This question let go to this another one: isn't TWRP able to write a partition table on an empty microSD ?
3) My way: using Gparted whom prompts a window which says to create a partition table before partitioning the device.
Alka-Seltzer PLUS said:
Thanks for your answer but I do not realize what was wrong doing it my way ( now the card gets mounted ) !
Click to expand...
Click to collapse
There's nothing wrong with your way! I just thought an explanation of what went wrong would be helpful. To actually fix it, gparted is what I would use, too; and now you've used it everything should work flawlessly
Sorry for the confusion: I was talking about fixing TWRP to recognize such cards (which it should) and working with them (which it shouldn't, because of the risk it's a broken card and we end up Proverbsing the phone).
is there any new solution?
or can i mount(in twrp) /dev/block/mmcblk0 sdcard
and install my new rom and do away