Related
Hi,
I have a problem that hopefully can be easily fixed. Heeeelp!
After rooting with SalsichaNooter3 , unrooting, re-rooting. Well, basically trying everything (for fun), I’m ending with a Nook that have no storage space available. At one point, my Nook was connected to the same PC where I was doing a Wi32Image with SalsichaNooter to the SDCard. The image might have been written to the Nook instead of the SDCard (here I’m not sure). The Nook would not boot, so after different manipulation, I can now boot the Nook with original recovery firmware 1.0.0 but there is no storage available. I can download from B&N shop, read, do all of what is expected from this device but the NOOK folder doesn't appear when connected to the PC. If I look at ‘Available storage’ in the settings menu, I get ‘0. 00B free of 0.00B’
I tried ‘erase, reset Nook’ from the menu, also the recovery with the power-left,right bottom buttons. I tried with n2T-Recovery 0.1 and 0.2. All seems to properly do their job but the storage partition still doesn’t seem to be available.
I suspect that the ‘boot’, ‘rom’ and ‘firmware’ partition are proper since I can boot, register and use the device so I tried with Partition Wizard to adjust the ‘*:NOOK’ and ‘*:userdata’ partition (formatting, change ID, etc), without success.
I don’t have a valid backup – I did my original backup using the drive ref. instead of the physical disk (I know, I should have read more - sniff).
Below is the screen shoot of Partition Wizard. Does anyone have an idea? Have none left. Maybe replacing the NOOK partition from a valid image using Partition Wizard would work but I don’t have access to such image.
Thanks.
For those interrested in my solution.
Inspired by this thread:
http://forum.xda-developers.com/showthread.php?p=16818990
I recreated the image partitions under linux with dd and sfdisk and repopulate the boot, factory, rom and empty name partition with my broken backup.
Write image to Nook using Noogie and RoadKill Disk Image.
Did a factory restore with power+2 lower side button method to be on safe side.
Seems to work nicely with extra space for sideloading (used the same space assigments as describe in the above thread).
Now, my recovered 1.0.0 version doesn't seems to apply the updates - but that's another story.
Cheers,
GM
I was able to update my Nook touch to 1.1 by resizing the partition. Seems that the system needs more space in the ./factory area (I think) to apply an update. The resizing modification specified in the above didn't left enough space.
Thanks.
You should take the time to update your title with [Solved]
ros87 said:
You should take the time to update your title with [Solved]
Click to expand...
Click to collapse
ha! ok. Done
Hello,
Complete noob here and I am not ashamed to admit it. I did create a bootable sd card with CM7 stable on it and the card is partitioned into 4 spaces. The boot space only has a capacity of 117.63 MB, while the 4th partition named CM7 SDCARD has a whopping 28.21GB available.... 112.14MB used..... Im guessing for application. Anyways, I am trying to put books and videos on my NC and there is not enough space that is accessible. Any way to make that boot partition spave larger? Maybe move some of the extra space from the 4th partition? I have EASEUS Partition Master but I have been unable to get it to work..... Any help is greatly appreciated.
I did search for a post like this but did not find any answers which I understood.
Thanks in advance,
What is it that you are trying to do?
Homer
I am trying to put books on my sdcard that I downloaded on my computer for school. When I copy to the directory boot/myfiles/books it says that there is not enough space. So I want to enlarge the size of the boot partition
After you burn the partition image using Win32Image, the size of the boot partition is roughly 117mb. At this point use EASEUS partition to expand the boot partition to the size you want. In my 32gb SD card, I created a 16gb partition. Then I copied CM7.1 and Gapps to the partition, booted NC and CM7.1 was set up in the remaining space, with /data at 5gb and /media at 9gb.
Would you then access the files while booting from the SDcard or internal memory (eMMC)?
If you want to see them when booting from SDcard, don't put them on /boot as you have found out there is not much room. You want them on partition 4. Remember that Windows will not mount partition 4 without some heroic efforts. I use either NookColor UMS (free, see here) or WiFi Explorer Pro (paid, check either Android or Amazon Market).
If you want to see them when booting from eMMC, that is slightly more advanced. You don't have to root, but there is a file on the system on eMMC that needs to be edited to mount partition 4 rather than partition 1. It would take some time to search for it, but someone posted a guide a while back. Search for something like sharing SDcard and/or editing vold.
Homer
Ok...... So I got the boot partition resized to around 20gb and I have copied the books from my hd to the sd card E:\My Files\Books...... Problem is I now cannot acess them when I boot CM7..... Any fix to this or will I have to boot from the eMMC?
Ok....
You're making the easy stuff hard...
You want a large partition that is accessible by CM7 running off the SD and your windows PC. Like Homer said, it is nigh impossible to get windows to mount secondary partitions off of an SD card reader. What he forgot is that CM7 allows you to access partitions 3 and 4 over USB. CM7 can access the boot partition but most apps won't look there and it won't be accessible over USB.
I would recommend that you restart from scratch. Allow verygreens installer to set up the default partitions. Plug your device into your PC and transfer your pdfs to partition 4 that-a-ways. That way you won't have to remove the sd card anytime you want to access your pdf folder.
Even when you plug the CM7 booted NC into your PC, you still need to mount the /sdcard partition to Windows. I find it is easiest to use NookColorUMS on the NC to mount that partition, see above. Otherwise, when you plug into the Windows machine you only get /boot mounted.
Homer
Homer_S_xda said:
Even when you plug the CM7 booted NC into your PC, you still need to mount the /sdcard partition to Windows. I find it is easiest to use NookColorUMS on the NC to mount that partition, see above. Otherwise, when you plug into the Windows machine you only get /boot mounted.
Homer
Click to expand...
Click to collapse
Hmm, when I plugged a nook running CM7 from SD card, I get access to /media and /sdcard. I had to move the gapps.zip from /sdcard to /boot manually using a file explorer.
I'm offering an apology to gall and Homer first so pls don't jump on me.
You guys harden a simple issue and confusing the OP.
To OP,
I assume you got a 32GB uSD card, using verygreen's image. You got 117MB on boot.
LEAVE the boot partition ALONE. The only thing you should put there are the ROM (CM7 zip file) and the GApp zip file. NOTHING ELSE. Your music/ebook/video, etc. should NEVER go there. You will place them in the left-over storage created by CM7, normally called CM7SDCARD.
How do you access CM7SDCARD so that you can transfer files over?
The only way is
+ NC on
+ connecting NC to PC (windows)
+ look at the NC notification bar, usb icon should be displayed
+ tap on it, enable usb mass storage (connect to PC for file transferring....)
+ Windows PC should by now recognized the CM7SDCARD and ready for use.
That's the ONLY WAY and the correct way.
If you use that bootable CM7 uSD and plug directly into PC, you only see the boot partition which only 117MB. Again, the boot partition is NOT meant for personal stuff.
What may confuse some people is that when they plug the device into PC then it does not by default auto-mount so you don't get a drive in the PC until you use the USB notification and turn on USB storage.
For non-techie users I normally install the automount USB app from JRTStudio so the drive pops up straight away on the PC and there is no confusion over this point.
The other good reason for using the USB (or alternatively wireless connections like ES File Explorer) is that it reduces taking the SD card in and out and any risk of damaging the socket.
My apologies, I never checked out the USB notification. I sort of ignored it. It seems a handy implementation of the basic functionality of NooKColorUMS.
What is MyNOOKColor though? CM7 SDcard is the one I typically use. Nevermind: it is the eMMC. I never bothered with that one since going to SDcard boot.
Homer
Hi,
First off if this is answered I am sorry.
I did a lot of searching and was unable to see the answer to this...
I am running CM7.1 off uSD. Install went well, and have no issues. That being said, I am unable to find out where on the card to sideload books. I have booted into CM7.1, turned on USB storage, and have 2 drives appear in win: MYNOOK and CM7 SDCARD. I used the size agnostic image, and it appears that there is only the single partition on the card, and in file explorer, it shows the correct card size for memory, but only the single partition.
The only folders appearing on the card are:
.android_secure
Android
LOST.DIR
I tried to manually copy the books, media, etc. folders into a My Files folder on this drive, without success.
There is no other partition to repartition (shouldn't have to do that with size agnostic?). I have no problem loading books into the MYNOOK book folder, which I assume is the internal device memory.
Here is my question. How/where do I sideload books to use the storage on the uSD card? Do I have to create the folders somewhere? If so where?
My goal is to utilize the storage available on the card, but be able to read the titles in the stock software. Is it possible to do this without rooting, or do I need to root for any reason to access the right folders on the card for storage?
THANK YOU ALL!!
klewlessnoob said:
I tried to manually copy the books, media, etc. folders into a My Files folder on this drive, without success.
Click to expand...
Click to collapse
In what way was it not successful? Did the files copy and just can't find them with a reader? If so which reader?
The book I transferred over was not found in the stock software when I opened my library. Is there somewhere specific I am supposed to place it on the card for the Nook to see it? Thanks!
For the stock reader, I think you must use the 1gb area of the internal memory drive, which shows up as a separate drive on your PC when you plug it into the computer. When you are in CM7 and connect to the pc, cancel when it tries to install a device for the NC. Check the notifications on the NC, you need to click a button to enable copying files from your pc, and take care to properly safely remove/eject before disabling that and disconnecting the cable from your pc. Better to get a separate reader and install it from the market (e.g., Cool Reader). You can also install the Nook app from the market, but then books need to go within (possibly in a specific subdir) of the "Nook" folder on SDCARD.
So there is no way to use the card memory to store books if I want to use the stock reader??
Should there have been a "NOOK" folder created on the SD card as part of the CM7 process? Is that a file that the user needs to create? If so, does it go in the same partition as the CM7, as that is the only partition my machine is able to see?
thanks again
Hopefully you'll get more input on this, but I think the point of keeping the Nook stock available (aside from not voiding your warranty) relates to use of B&N books. However you can eject your CM sd card and use another sd card if you want more space for user media for use with the stock app. I thought the media drive was the 1gb area, but now I'm not so sure because on mine the MYNOOK disk is much smaller.
When you are in the stock firmware... you are seeing the boot partition of the uSD...
You can write the boot partition... resize it... then run the installer...
I have done it in the past... set up a 2GB boot partition... then setup the ROM on uSD. You then have a 2GB partition you can use when in stock.
Thanks for the info. I am a bit confused by your suggestion, can you please offer a bit more?
By writing the boot partition, then resizing it, does that mean I can resize now, after I have already set everything up? If so, what do you mean by the installer? Or do you mean I have to wipe the card and start over? If that is the case (start over) do you mean wipe the card, create a small partition for the boot to install on? Would that requre the use of an image that is not size agnostic?
Either way, how do I get the file structure in place on the non boot partition for the nook to see files that are saved there?
Thanks again for any help you can provide!
I have never had luck resizing it after it has been booted in the Nook and all the partitions created...
I have written the size agnostic image to the card... resized the only partition created at that point... then put the ROM on it and booted it in the nook so the installer script (size agnostic recovery) can do the partitioning and install the ROM.
For the question of getting the file structure... I'd have to ask how you wrote the files on the uSD... were you CM or stock?
I had always planned on running cm from the card, so when I wrote the files to the card, I was stock.
If I follow what you are saying, then steps for me to try at this point would be:
1. Reformat card
2. Write the disk image to the card
3. Shrink the single partition on the card (where the image is)
4. Add the CM ROM to same partition as the image
5. Install card and boot device
If this sounds right, I have 2 questions.
What size should the partition be for the image and CM ROM, maybe 2GB?
Will the Nook "see" the non-CM partition and create the file structure for saving files on the 2nd partition at some point? In my searches I saw that in early versions, there was a requirement that the 4th partition on the card be expanded to use for storage, won't I only have 2 at this point?
Thanks again so much for the help!
When you write the image to the card... it will only be about 114 MB.... you will probably want to increase the size to avoid any possible size issues later (with ROM's getting larger)
If you plan to use the stock nook ROM as well as CM7... you will probably want 2 GB boot partition... otherwise if you plan to only run CM7 you probably only want about 250 MB.
You can modify vold.fstab on the stock ROM to use partition 4 of the SD for its SD use... then you could avoid the 2 GB boot partition.
What happens when you use VG's SASD... the boot image is about 114 MB... when you boot it in the nook it creates partitions 2, 3 and 4... 2 and 3 are ext3 partitions, partition 4 is fat... partition 4 is the one set for sdcard in the ROM booted from SD...
This is why you can modify stock vold.fstab to point to partition 4... then both ROM's will be putting stuff on the same partition for "SD Card"
I think I follow that, but my issue is that currently I am unable to see partition 2,3 or 4 which I think is part of my problem.
When I set up the card, I used the SASD method, and all I can see in both win explorer and partition software is the single partition on the card. Should there also be partitions 2,3, and 4? Do I have to do something to make those partitions viewable?
I am not comfortable enough with my skill level to attempt to modify the stock vold.fstab file on the device, and was hopeful that by properly setting up the card, I would be able to keep stock as is, and use the card to multipurpose, ie run cm7 on part and use the remaining space on card to store books to be read in stock firmware. I am still hoping to do that....thanks
As far as only seeing partition 1.... that is a limitation of Windows.
By following the advice pertaining to starting over and increasing the size of the Boot partition immediately after writing the image... before doing anything else... you can provide more space for the stock ROM to use on the SD... it will use partiton 1 (the boot partition) without the other modifications to vold.fstab
ok, confused again
If I start over, write image, then resize that partition with the image, am I going to use the "rest" of the card, NOT in that partition to use with storage? OR am I going to resize the partition with the image to be big enough to use as the partition to put books on?
If it is the former, don't I again run into the problem of how to find the other partitions, or will I create them when resize the first partition after writing the image?
Thank you!
You will only ever see the first partition of the sd card when booting from the stock OS. Also with the card inserted in a usb flash card reader on Windows you can only mount the first partition as a drive letter. But you can see and resize partitions with contiguous unallocated space using MiniTools Partition Wizard.
OK thats good to know. Do you know if the SASD install should have created other partitions when I installed to the card? The reason I ask is that even in Partition Wizard, I am still only able to see the 1 large partition with everything in it.
If I start over again, will I need to use the wizard to create partitions first, then write the image to the resized 2 GB first partition, or should I write image to card, resize the first partition? If the latter, will resizing the first partition autmatically force the other partitions to be seen? I am not sure of this option, as I can't see where in the process the other partitions are created? Is this part of the process when CM7 boots?
Thanks!
Write the image. Safely remove from pc. Reinsert to pc. Use minitool partition to resize the (only, at that point) partition to the size you want. Use Apply in minitool software. Quit minitool and resume with the card setup.
does the minitool at that point (resizing) create the other partitions, or will the card setup do that? Do I have to do anything else to the other partitions to make them visable to the stock nook so that they can be used to access books while in stock os?
The card setup will create the other partitions. The stock os is never going to see anything but the 1st partition. You would need a terminal emulator or rooted file explorer installed in the stock os in order to mount another partition.
If that is the case, that stock os will never see anything other than the 1st partition, then there really is no way to accomplish what I am trying to do, correct?
In other words, put CM7 on the card, then when I want to use stock, boot into stock and have the reader find books saved on the card?
Hi, I have a Nook Simple Touch device with a traditional problem of improper backup of 76 MB before rooting.
Now I have managed to retrieve files from the /rom partition (/devconf folder with 20 files like serial no, public key etc.) - I have them in my laptop as regular files as well as 16 MB partition image on SD card.
Would anybody be so kind to offer a full recovery method? I believe backup of somebody's full image and then overwriting the /rom partition would revive the device?
How much of your partition table is left, if any, and how familiar are you with linux?
Were it me, I might have a go at creating just the first partition - boot from noogie, connect to a linux box, and use fdisk to create the partition.
I'd then try doing a
dd if=single.partition.backup.img of=/dev/mmcblk0p1
(writing my boot backup to the partition I just created) and see if that file wasn't enough to bootstrap the other partitions. Depending on how you created the backup, you may have the boot flag set and the partition table stored; so long as you haven't actually put data on the other partitions yet, it may be possible to at least trigger the onboard restore.
These are values that work on the glow, and I believe on the touch as well:
Disk /dev/block/mmcblk0: 2000 MB, 2000683008 bytes
128 heads, 32 sectors/track, 954 cylinders
Units = cylinders of 4096 * 512 = 2097152 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 38 77808 c Win95 FAT32 (LB
A)
Of the partitions, I still have:
- boot (I believe it is somewhat corrupted, but this I can restore from the backup)
- NOOK (FAT32) - should be OK, I see files in it;
- cache (Ext3)
- data (Ext3) - seems to be corrupted
Missing: factory (Ext2); one untitled partition and one unallocated segment.
Backup was created with Roadkil's DiskImage, with a source being the locigal drive (original boot partition).
I'm not good at Linux, but I know how to create partitions using Windows tools.
OK, I can try to recreate the boot partition and the rom partition, and restore the backup to it, then I'll see what happens.
Disk configuration for NST is different from the NSTG:
Cylinters: 238 Heads: 255 Sectors: 63
Nook is resurected!
Yes, I have managed to revive the Nook Simple Touch who had survived deletion of all partitions and restore of just the boot partition!
You will need for this:
- an micro SD card and card reader;
- Noogie;
- Minitool Partition Wizard (or other partition management software, if you like and it can do partition recovery and copying);
- ClockworkMod (sd_2gb_clockwork-rc2.zip)
- Alpha-FormatTouch-2.zip - to be copied onto ClockworkMod SD card;
The principle is this:
- first of all, do a PROPER backup of your device - backup ENTIRE PHYSICAL DISK (2 GB) into the image file.
- Using Minitool Partition Wizard, do a partition recovery operation - you should find all your deleted partitions - but do not apply changes yet!. However, due to improper restore of logical disk to a physical disk, the disk config info probably became corrupted and disk size appears to be 78MB, so you won't be able really restore the partitions. So, using Minitool Partition Wizard, do a copy of the recovered partitions one by one onto the SD card - and start with the most important rom partition. From Partion Wizard, you should be able, using Explore function, to check if the partition has all necessary files (20) like serial no, public key, mac address etc.
- from SD card, you can create a backup image of each partition on your hard disk.
- after you have copies of all necessary partitions (boot, rom, nook are vital; others are optional), you need to do a wipe on the NOOK disk to delete all partitions and the disk to obtain the original size of 2 GB.
- on an empty disk after wipe, you have to restore the partitions in the order:
1. restore, by copying using Minitool Partition Wizard, the boot partition (78 MB, FAT32, Primary, set it Active)
2. restore, by copying using Minitool Partition Wizard, the rom partition (16 MB, FAT32, Primary)
3. create manually new partition factory (190 MB, Ext2, Primary)
4. create manually new partition (no label) (288 MB, Ext2, Logical)
5. copy from backup partition NOOK (240 MB, FAT32, Logical)
6. create manually new partition cache (Ext3, 240 MB, Logical)
7. create manually new partition data (Ext3, 801 MB, Logical).
Then, boot the Nook from ClockWorkMod SD card, and format /system, /cache, /data partitions;
afterwards, install from zip card - Alpha-FormatTouch-2.zip.
And, hopefully, your Nook will be alive again!
(Now, I'm sure, you won't forget to do a proper backup of your working Nook :fingers-crossed
Yes, you save my nook. Thanks to your method i could revived my /rom.
but all is not done for me . i have a UK NST Glow and the glow is not working. I would like to update to firmware1.2 and may be this glow will function again. But When i plug the usb, windows cann see the drive but i don't have access to it. i have the message "please insert disc in F: drive"
wow wow wow . At last i successed to update to FW 1.2 for my almost bricked UK NSTGL. Now i have a US NSTGL but nevermind. now time to backup correctly.
but i'm not sure your method is fully working. I had to make a partition table with renater script "nookparted.sh" and then use roustabout's comment "dd if=boot.img of=....". and after that i put update 1.2.
In one week i have learn so much with my broken backup.
Hello, new here so hope it's ok to hijack this thread slightly, seems the original issue has been solved and I think my problem is similar although I'm way out of my depth here... I've managed to brick my nook, and although I took a backup which is AFAIK correctly sized 1.86gb I can't restore it. I've tried putting noogie and cmw on the sd card but it's refusing to boot, I suspect I nonced the partition table up and can't even get the nook to register when I plug it in to the PC now. I suspect is obvious I'm a dumb noob but if anyone could help point me in the right direction it would be much appreciated
welcome to the brave new world of the "bricked forever" and endless nights.
Nobody blames you since everybody and their mothers seem to fall into the trap even if they are told to make a good backup.
i had read so much threads to resurect my nook that i don't exactly know how i made it through, but here are some indications:
Here are the objectives:
1) make a correct backup of your bricked nook: -> you can make after all stupid commands and you 'll come back to this point.
2) you'll have to resurect your /rom or your rombackup.zip (inside factory).
3) have the correct partition of your nook
4) reinstall the rom
for 2) this thread gives a way to get back your /rom. read carefully even roustabout's comment can really help
for 3) thanks to Renate NST in this http://forum.xda-developers.com/showthread.php?t=1805936&highlight=to+stock and her script "nookpart.sh" i could have a correct size for my partition. (method with wizard partition gives wrong cylinders alignement). read all of this thread it is really rich.
for 4) if you reach that point that should be easy.
Thanks for the welcome and the reply jjinkou2.
I'm guessing I need to work on the nook through a PC. I've currently got 2 PCs, one running window 7 and one on vista, I'm mainly working on the W7 machine. When I plug the nook in to it, a device briefly shows up as the h: drive in My computer but then immediately disappears and so I can't actually access it yet. I note that roustabout mentions working in Linux, if I had a Linux machine available would it be easier to get it to recognize the nook?
Edit: Just tried plugging the nook into my vista machine (which it has not been used on before) and the Found New Hardware window briefly pops up but then vanishes and I get a message on the taskbar: Device driver software was not successfully installed - OMAO3630 Device unplugged. Is there a fix for this pelase?
Some easy instructions here http://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch/Installing_ADB
you'll need to install android sdk and check usb install in the extra.
Search for a file named "ADB + Fastboot + Drivers.zip" in the forum to easily have the adb.
With windows the usbdriver can be tricky to install. i had to use usbdview (look for it in google) and uninstall all B&N mass storage and OMAP3630.
The driver for usb inside the previous zip might not work also. i found one in the forum but can't find it right now.
Edit
found the usb driver that worked for me
http://forum.xda-developers.com/showthread.php?t=1125094
Excellent, thanks very much! Not entirely sure how I managed it but I managed to get to a point where I could use the method shown by budriunas and my nook is now working again, albeit with an older firmware and the glow light isn't working but at least it's not bricked! Now just to get the light working and then root the damn thing without killing it....
budriunas said:
Yes, I have managed to revive the Nook Simple Touch who had survived deletion of all partitions and restore of just the boot partition!
You will need for this:
- an micro SD card and card reader;
- Noogie;
- Minitool Partition Wizard (or other partition management software, if you like and it can do partition recovery and copying);
- ClockworkMod (sd_2gb_clockwork-rc2.zip)
- Alpha-FormatTouch-2.zip - to be copied onto ClockworkMod SD card;
The principle is this:
- first of all, do a PROPER backup of your device - backup ENTIRE PHYSICAL DISK (2 GB) into the image file.
- Using Minitool Partition Wizard, do a partition recovery operation - you should find all your deleted partitions - but do not apply changes yet!. However, due to improper restore of logical disk to a physical disk, the disk config info probably became corrupted and disk size appears to be 78MB, so you won't be able really restore the partitions. So, using Minitool Partition Wizard, do a copy of the recovered partitions one by one onto the SD card - and start with the most important rom partition. From Partion Wizard, you should be able, using Explore function, to check if the partition has all necessary files (20) like serial no, public key, mac address etc.
- from SD card, you can create a backup image of each partition on your hard disk.
- after you have copies of all necessary partitions (boot, rom, nook are vital; others are optional), you need to do a wipe on the NOOK disk to delete all partitions and the disk to obtain the original size of 2 GB.
- on an empty disk after wipe, you have to restore the partitions in the order:
1. restore, by copying using Minitool Partition Wizard, the boot partition (78 MB, FAT32, Primary, set it Active)
2. restore, by copying using Minitool Partition Wizard, the rom partition (16 MB, FAT32, Primary)
3. create manually new partition factory (190 MB, Ext2, Primary)
4. create manually new partition (no label) (288 MB, Ext2, Logical)
5. copy from backup partition NOOK (240 MB, FAT32, Logical)
6. create manually new partition cache (Ext3, 240 MB, Logical)
7. create manually new partition data (Ext3, 801 MB, Logical).
Then, boot the Nook from ClockWorkMod SD card, and format /system, /cache, /data partitions;
afterwards, install from zip card - Alpha-FormatTouch-2.zip.
And, hopefully, your Nook will be alive again!
(Now, I'm sure, you won't forget to do a proper backup of your working Nook :fingers-crossed
Click to expand...
Click to collapse
Thank you so much. My nook is back. I described my work in http://forum.xda-developers.com/showthread.php?p=34746242#post34746242.
jjinkou2 said:
wow wow wow . At last i successed to update to FW 1.2 for my almost bricked UK NSTGL. Now i have a US NSTGL but nevermind. now time to backup correctly.
but i'm not sure your method is fully working. I had to make a partition table with renater script "nookparted.sh" and then use roustabout's comment "dd if=boot.img of=....". and after that i put update 1.2.
In one week i have learn so much with my broken backup.
Click to expand...
Click to collapse
how did you do a partition table?? i have run nookpart.sh but i still get the problem : "When i plug the usb, windows cann see the drive but i don't have access to it. i have the message "please insert disc in F: drive"
nookpart.sh will partition the internal memory exactly like it was.
This is important if you actually still have valid data but the partition table was destroyed.
If partitions are not looking correctly they may need to be formatted.
Don't be too quick to repartition/reformat until you know what the situation is.
i have used nookpart.sh but still no good, here is the result when i execute nookpart.sh. Everything works except internal storage not mounted correctly i think, i want to update to 1.2
edit: see my thread http://forum.xda-developers.com/showthread.php?p=48015536#post48015536 for more details
I changed the Android ID on my Nook Color (with Titanium Backup Pro) and now it is boot-looping, at the point where the arrow head moves around in a circle. It is running CM7, but I'm sure the rom is at least a year old. I think it has CWM recovery. How do I get to recovery and what should I do?
[edit] I found this thread and will see if there is something I can use.[/edit]
I pulled the microSDHD from the device and I can read the boot partition on my PC. Before I attempt repair, I want to copy a few data files from the SDCard's data partition, but I do not see it. How do I mount the SDcard partition so that I can copy the files? I know how to do this once I can successfully boot to the Android desktop, but not without the desktop.
I looked through verygreen's SDCard installation instructions here and I can execute boot into recovery, but that just looks for update files and shuts down. I did not get a menu to allow me to mount the data partition via USB for the PC to read or for any options at all.
I have a bootable SDCard (verygreen's) and removed it to boot from emmc. That works, so the problem is on the microSDHC. When I insert the microSDHC (8GB) card in the card reader on my PC, I see the first three partitions are healthy and the last (5.9GB) is not. The only partition that I can assign a drive letter to is the first partition, Boot. Is there any repair I can do to that forth partition?