EE:Can't mount /sdcard when in Recovery v5.8.3.4 or boots into CM10 & hangs... - Asus Eee Pad Transformer Prime

Hello All,
I can see my files are all there (on the external sd card located permanently inside the TF201) when look via the pc but recovery doesn't seem to be able to mount the internal sdcard so I cannot get at the zip files I put on the internal sdcard to flash from recovery.
I was running a very happy TF201 running Virtuous Prime until I decided to change a font a few days ago. That was a bad move. On reboot everything was stuck on the intro splash screen. I managed to get into recovery & somehow managed to get my new rom (CM10 ish) flashed & i thought all was well until I realised that in all the 'heat of battle' the usual wipe re wipe/wipe dalvick/reset privileges routine had been omitted from my routine. Worse still I had flashed the rom but not yet flashed the Jelly Bean GAPPS.
So the system was still hanging at the splash screen (although this time at least it was the CM10 splash screen (progress is so sweet) but now, just when I thought it couldn't get any worse, when I go into recovery to apply a zip from an sdcard I get told that E:Can't mount /sdcard/ so I cant get at my file to flash!
I'm 3 days into this now & I am definitely loosing the plot so please please give me a nudge in the right direction .A have adb up & running & have just fastbooted a new recovery img over onto the prime because I read that this might sort my problem. Well, it didn't so here I am. Please assume I am a noob 1st class although I may surprise you with some of my knowledge that I've picked up over the last few days & years working in systems (though not Android) so maybe I wont!
Get this sorted with me & I'll be forever in your debt. Please let me know what other information you may need to give me a push in the right direction. Thanks for reading this & thanks for deciding to help me hang on to that thread of sanity that is left.
I have also asked for help on TransformerForums; because I'm new to this site I cannot provide you with the link. Sorry.

correct me if i got this wrong; so you are able to get into CWM und you see your device via
Code:
adb devices
right?
now can you push files via
Code:
adb push
to your device?
If so we had the exact same problem don't worry theres a fix for this:
first if you're in adb type:
Code:
adb shell
now you should see this "#" somewhere in front of your command line
type
Code:
ls
now it should show you the folders on your device, try to navigate to the directory /data/media via
Code:
cd /data/media/
now push the rom you want to flash in this directory, for example:
Code:
adb push ROM.zip /data/media/ROM.zip
the rom should be in the same folder as your adb.exe
essentially /data/media is your internal storage so you should now be able to flash the rom of your choice.
I hope i could help because I had almost exactly the same problem and was about to go crazy until i found this solution

success...
s0undless said:
correct me if i got this wrong; so you are able to get into CWM und you see your device via
Code:
adb devices
right?
now can you push files via
Code:
adb push
to your device?
If so we had the exact same problem don't worry theres a fix for this:
first if you're in adb type:
Code:
adb shell
now you should see this "#" somewhere in front of your command line
type
Code:
ls
now it should show you the folders on your device, try to navigate to the directory /data/media via
Code:
cd /data/media/
now push the rom you want to flash in this directory, for example:
Code:
adb push ROM.zip /data/media/ROM.zip
the rom should be in the same folder as your adb.exe
essentially /data/media is your internal storage so you should now be able to flash the rom of your choice.
I hope i could help because I had almost exactly the same problem and was about to go crazy until i found this solution
Click to expand...
Click to collapse
This has sorted the problem. Thank you very much for this. Could you please tell me the significance of the 'ls' line?
I followed your instruction which resulted in my being able to flash a ROM which still hung at the intro flash screen. Since I could now see the internal file system was mounting (& accessible) I decided to attempt to replace the recovery package with TWRP which is absolutely fantastic; you are able to access both internal & external sdcards + there's a very intuitive 'touch' UI.
I was beginning to wonder if I was going to get out of this one, but, thanks to you all is well.

ls is just to ensure you are in the right directory. the next time your rom is stuck at the boot screen try to give it some more time if this doesn't work wipe the dalvik and cache via recovery and it should be able to boot if flashing was successful. and yes you are absolutly right TWRP is waaay better than CWM. Glad I was able to help you get this sorted.
Enjoy your Weekend
soundless

No dice
I have same issue as user above. I connect my TF201 to my computer and I get Driver issues saying This device cannot start. (Code 10). I did everything restared computer, deleted drivers scan hardware changes reinstalled drivers, and everything. I can't get the adb working. I keep scanning and it says there isn't any devices.
I had a bad ROM flash and my TF201 will no longer boot. I can get it into the CWM v5.8.3.4 but it will not read my SD card. I tried 3 SD cards and none of them will read. I formatted them FAT32 from what I read and even tried FAT and NTFS just to see if that made a difference and that didn't work. WHen I click to install zip from sdcard it points to my internal storage. I created a backup but again just my luck the first time while reading on ways to fix the issue I ended up in the Asus fastboot load screen and being use to the CWM commands I hit volume down (moved cursor to the left hovering over wipe data) and hit volume up thinking it would go back to the USB symbol but that wiped all the data off the device.
I restared and booted back into CWM and selected install zip from SD card now nothing shows up since it no longer reads any internal data (accidently deleted) and it doesn't read my SD card.
So, at this point I feel I'm out of ideas. ADB doesn't work to try transfering a file directly to the device and CWM doesn't read SDcards so I can't flash a new ROM on the device to get it working again.
Any help would be much appreciated.

Why is CWM still used !!!!!
All recent bricks I've seen here were CWM related!!
See here: http://forum.xda-developers.com/showthread.php?t=1841001 second post for replacing cwm by twrp.

Just had this issue with the bad cm10 rom. TWRP saved the day!
---------- Post added at 02:04 PM ---------- Previous post was at 02:02 PM ----------
Crezabek said:
I have same issue as user above. I connect my TF201 to my computer and I get Driver issues saying This device cannot start. (Code 10). I did everything restared computer, deleted drivers scan hardware changes reinstalled drivers, and everything. I can't get the adb working. I keep scanning and it says there isn't any devices.
I had a bad ROM flash and my TF201 will no longer boot. I can get it into the CWM v5.8.3.4 but it will not read my SD card. I tried 3 SD cards and none of them will read. I formatted them FAT32 from what I read and even tried FAT and NTFS just to see if that made a difference and that didn't work. WHen I click to install zip from sdcard it points to my internal storage. I created a backup but again just my luck the first time while reading on ways to fix the issue I ended up in the Asus fastboot load screen and being use to the CWM commands I hit volume down (moved cursor to the left hovering over wipe data) and hit volume up thinking it would go back to the USB symbol but that wiped all the data off the device.
I restared and booted back into CWM and selected install zip from SD card now nothing shows up since it no longer reads any internal data (accidently deleted) and it doesn't read my SD card.
So, at this point I feel I'm out of ideas. ADB doesn't work to try transfering a file directly to the device and CWM doesn't read SDcards so I can't flash a new ROM on the device to get it working again.
Any help would be much appreciated.
Click to expand...
Click to collapse
Use Fastboot and flash TWRP Recovery. CWM still cannot use external sd cards! There are simple instructions on their website.

TWRP will give you the option to install from either the internal sd card or external sd card. I've found it to be a better bet all round than clockwork mod recovery. It uses a touch interface which saves more time than you'd imagine. Just one tip; occasionally the contents of the external sd card don't show. If that happens, just reboot into recovery (again) & everything will be as it should be. Hope this helps.!...
Sent from my GT-I9100 using xda premium

Crezabek said:
I have same issue as user above. I connect my TF201 to my computer and I get Driver issues saying This device cannot start. (Code 10). I did everything restared computer, deleted drivers scan hardware changes reinstalled drivers, and everything. I can't get the adb working. I keep scanning and it says there isn't any devices.
I had a bad ROM flash and my TF201 will no longer boot. I can get it into the CWM v5.8.3.4 but it will not read my SD card. I tried 3 SD cards and none of them will read. I formatted them FAT32 from what I read and even tried FAT and NTFS just to see if that made a difference and that didn't work. WHen I click to install zip from sdcard it points to my internal storage. I created a backup but again just my luck the first time while reading on ways to fix the issue I ended up in the Asus fastboot load screen and being use to the CWM commands I hit volume down (moved cursor to the left hovering over wipe data) and hit volume up thinking it would go back to the USB symbol but that wiped all the data off the device.
I restared and booted back into CWM and selected install zip from SD card now nothing shows up since it no longer reads any internal data (accidently deleted) and it doesn't read my SD card.
So, at this point I feel I'm out of ideas. ADB doesn't work to try transfering a file directly to the device and CWM doesn't read SDcards so I can't flash a new ROM on the device to get it working again.
Any help would be much appreciated.
Click to expand...
Click to collapse
Did updating recovery sort this out? If not, shout & I may be able to help.

Some people act this way: come to ask for help, and never come back...

Hi all,
I was using latest Revolver and gave a try on CM10 Beta4
I can open a adb shell but could not execute adb push file /dir propertly
EE:Can't mount /sdcard
damn!
wish restore my Revolver4 backup :good:

rafael_mfr said:
Hi all,
I was using latest Revolver and gave a try on CM10 Beta4
I can open a adb shell but could not execute adb push file /dir propertly
EE:Can't mount /sdcard
damn!
wish restore my Revolver4 backup :good:
Click to expand...
Click to collapse
push it to /data/media
sent from my i9250

bk201doesntexist said:
push it to /data/media
sent from my i9250
Click to expand...
Click to collapse
I tried to push it already, but I can't as mentioned before.
ADB recognizes my device, open 'adb shell' but push command don't work.
push file.zip /data/media/file.zip
*file is on the same folder as adb.exe
EDIT: Resolved using EasyFlasher Tool. As described on this post.

Related

Fix for bricked nooks from CM7 "formatted sd"

for this fix, you will need to have a CWM sdcard ready and waiting followed by and drivers properly installed for your tablet.
YOU MUST have CWM running from sdcard to fix this issue. Otherwise nothing will happen.
instructions to install to sdcard are here (I suggest using windows)
Needed files for download:
just download this zip and run the script while booted into cwm from sdcard.
download it here.
Instructions: Boot from sd (don't worry, it will work), ensure sdcard is mounted, and then you just run the fix.bat from the computer after extracting.
Credits: Succulent for the xloader image
Fattire for the idea that it might have formatted mmcblk0p1 (which it dead instead of mmc1)
You're welcome.
Might want to add that the cause of the "brick" appears to be that CM7 is confusing mmc1 and mmc0 and instead of wiping the first partition of the SD card, it's presumably wiping the first partition of the emmc, which contains the x-loader.
I already have said it.
Ah okay... well glad everything is fixed now.
fattire said:
You're welcome.
Might want to add that the cause of the "brick" appears to be that CM7 is confusing mmc1 and mmc0 and instead of wiping the first partition of the SD card, it's presumably wiping the first partition of the emmc, which contains the x-loader.
Click to expand...
Click to collapse
Bowing head in shame here...... Rookie mistake!
Looks like we have to make a bit of a tweak to the system then do some testing.
New download link due to a small scripting error.
Need help
Hi Indirect. I see that you have fixed your NT. I did not use sd i did install cm7 internally but i did format all the mounts . And now it just restarts in CWM. What should i do. Any idea please
Well guys, I'm still having problems. I ran the brick fix before you updated it - didn't work. I then re-ran after you updated it - still didn't work. It'll boot to CWM from SD, but won't boot to any ROM. Tried re-installing CM7 (didn't work), then I tried the Nook141root.zip which supposedly installs the BN 1.4.1 from CWM (also didn't work). Tried re-running the brick fix a handful of times after and before installing each ROM with no luck. Then I tried running it without installing a ROM. Tried the brick fix then I tried the BN 1.4.0 restore file. I tried on multiple freshly formatted SD cards and I even tried on a computer I was working on with a fresh install of Win7 with a fresh install of the drivers just to rule that out.
Before all this I had CWM and CM7 installed internally - if that makes a difference. Ideas?
Edit: More info. When trying to wipe data/factory reset in CWM I get the errror "E:format_volume: make_ext4fs failed on /dev/block/mmcblk1p2"...this occurs right after rebooting from the brick fix.
Edit 2: More info yet...in the brick fix I'm getting the text "error: device not found" twice right after entering "y" then again a handful of times later. Is there anything special I have to do in CWM to get it to detect it? I have sdcard mounted...
Im geting this and then my nt restarts by itself and then im back in cwm again so nothing is fixed.
Fatos said:
Im geting this and then my nt restarts by itself and then im back in cwm again so nothing is fixed.
Click to expand...
Click to collapse
What do you have mounted to get it the fix to detect the tablet? Does it matter?
scsione889 said:
What do you have mounted to get it the fix to detect the tablet? Does it matter?
Click to expand...
Click to collapse
Actually with mine it does not matter . I get till the step y or n without mounting nothing. Than i mount the sd card and press y and enter.
Than as u can see does try to write something and than my nook does reboot .
And the ending is the same. So no progress so far.
Fatos said:
Actually with mine it does not matter . I get till the step y or n without mounting nothing. Than i mount the sd card and press y and enter.
Than as u can see does try to write something and than my nook does reboot .
And the ending is the same. So no progress so far.
Click to expand...
Click to collapse
Were you running from internal or SD when it bricked?
Does it boot to CWM on it's own without an sd in the slot? If it does have you tried restoring/flashing a backup?
Reason I say about the backup is I just bricked my own systems on purpose when running from sdcard, it kept gpoing back to CWM after the xloader was returned to it. Restored an original backup and all is well again
CelticWebSolutions said:
Were you running from internal or SD when it bricked?
Does it boot to CWM on it's own without an sd in the slot? If it does have you tried restoring/flashing a backup?
Reason I say about the backup is I just bricked my own systems on purpose when running from sdcard, it kept gpoing back to CWM after the xloader was returned to it. Restored an original backup and all is well again
Click to expand...
Click to collapse
Yes i have had it internally.Not in an sd.
Yes mine doew boot to CWM on its own without and sd in slot. And yes i have tried restoring to re flash back up. Cause i have installed CM7 once and it did run well. But than after installing some programs became slow so i wanted to redo it again. And than i did format all: bootdata, cache, emmc, rom, system,sd-ext.
And then i installet cm7 again and all the installing went well againg . But it just want start cause is missing something in one of the mounts. So what i think is only needed if ill be able to restore the data that is in all those small partitions like emmc. I know that bootdata,and cached gets backed up but i dont know if the orthers are backed up or not.
Thanks for trying to help.
Edit: I have to go to university now. But if it would make it easier for you to help, I can shot a video afterwards with all the steps what i have done and how is my nook behaving now.Just let me know .
Edit1: I did try to restore to stock or update to 1.4.1 but it tells me MD5 mismatch.
Is it possible that i can push in with adb the files that are in the boot data, eMMc and other mounts i mean one by one.
I was running internal when it bricked. Only boots to cwm from SD now.
Sent from my Incredible 2 using XDA App
Fatos said:
Yes i have had it internally.Not in an sd.
Yes mine doew boot to CWM on its own without and sd in slot. And yes i have tried restoring to re flash back up. Cause i have installed CM7 once and it did run well. But than after installing some programs became slow so i wanted to redo it again. And than i did format all: bootdata, cache, emmc, rom, system,sd-ext.
And then i installet cm7 again and all the installing went well againg . But it just want start cause is missing something in one of the mounts. So what i think is only needed if ill be able to restore the data that is in all those small partitions like emmc. I know that bootdata,and cached gets backed up but i dont know if the orthers are backed up or not.
Thanks for trying to help.
Edit: I have to go to university now. But if it would make it easier for you to help, I can shot a video afterwards with all the steps what i have done and how is my nook behaving now.Just let me know .
Edit1: I did try to restore to stock or update to 1.4.1 but it tells me MD5 mismatch.
Is it possible that i can push in with adb the files that are in the boot data, eMMc and other mounts i mean one by one.
Click to expand...
Click to collapse
I'm in the same boat...I think when we did a format of the rom partition, we lost some data that was not backed up...That being said I have done a lot of reading and I think all hope is not lost.
We did not format the "factory" partition which from what I have been reading may contain a backup of the "rom" and other partitions.
I wonder if it is possible to pull the data from the factory partition, extract the data that we need and then push the appropriate files back to where they belong? It's way beyond my expertise, although I do have ADB working and I think if someone could point us in the right direction, it wouldn't be that difficult...I could be completely off base though...Good Luck and If I make any progress I'll make sure I pass the info along.
Need help!
I got the bloody ADB issue.... I was able to boot to CWM from SD card, and it's mounted. BUT! Adb devices gives me nothing, no device. I did all the troubleshooting of the driver, i got the "Android composite ADB interface" device but still no adb device appearing. Please help! My only idea if this fix can be incorporated into a flashable zip. May be there is some other way?
Thanks.
ElectroMike said:
I got the bloody ADB issue.... I was able to boot to CWM from SD card, and it's mounted. BUT! Adb devices gives me nothing, no device. I did all the troubleshooting of the driver, i got the "Android composite ADB interface" device but still no adb device appearing. Please help! My only idea if this fix can be incorporated into a flashable zip. May be there is some other way?
Thanks.
Click to expand...
Click to collapse
That's exactly what I've got. I'm going to spend a little time on fixing that up today. ADB just won't work through CWM for me.
ElectroMike said:
I got the bloody ADB issue.... I was able to boot to CWM from SD card, and it's mounted. BUT! Adb devices gives me nothing, no device. I did all the troubleshooting of the driver, i got the "Android composite ADB interface" device but still no adb device appearing. Please help! My only idea if this fix can be incorporated into a flashable zip. May be there is some other way?
Thanks.
Click to expand...
Click to collapse
I had thought about a flashable zip. I will look shortly and build one
I tried repartitioning my nook and it really bricked it now. It won't boot from SD. Tried a different card and fresh download of CWM. I think it's totally borked.
Edit for clarification: repartitioned from within CWM on SD
Edit2: Tried a 3rd card (first 2 were 32gb, 3rd was 16gb) and it let me back into CWM. ADB still isn't working though.
Edit2 clarification: I only say ADB isn't working because the brick fix says device not found. If I'm wrong please feel free to correct me.
scsione889 said:
I tried repartitioning my nook and it really bricked it now. It won't boot from SD. Tried a different card and fresh download of CWM. I think it's totally borked.
Edit for clarification: repartitioned from within CWM on SD
Edit2: Tried a 3rd card (first 2 were 32gb, 3rd was 16gb) and it let me back into CWM. ADB still isn't working though.
Edit2 clarification: I only say ADB isn't working because the brick fix says device not found. If I'm wrong please feel free to correct me.
Click to expand...
Click to collapse
Mne does not say that but it restarts my nook. But it does not fix it. I think its just some small starting files missing. But im not so good so i cant help it. So im just sitting and watching around internet if there is any fix. It looks that they have had the same problem with NC to start with to.

[Guide] SD Partition for Encryption Unsuccessful (ICS Bug)

THIS GUIDE IS ONLY FOR ICS USERS WHO HAVE ENCOUNTERED THE ENCRYPTION UNSUCCESSFUL SCREEN ON THEIR PHONE. If you have no idea what the ENCRYPTION UNSUCCESSFUL screen is disregard this guide.
First and foremost I would like to thank and give credit to 'cgugino' for his guide over at the Captivate forums. Thanks to tabthelab and Woodrube for their helpful advice and guidence.
cgugino's guide (captivate)
http://forum.xda-developers.com/showthread.php?t=1447303
This is a similar guide if not identical to his guide for "fixing" the Encryption Unsuccessful bug that occurs in certain ICS roms (DocMasters V5 confirmed). Not sure about other ICS roms.Here is a screenshot of the "Encryption Unsuccessful" screen that will eventually appear on your ICS rom.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you have already selected reset phone well don't panic just proceed. It will not make a difference regardless.
Note: If you still have access to CWM not stock recovery proceed to step 6 and create your new partition. But REMEMBER TO BACK UP YOUR SD CARD AS IT WILL BE WIPED COMPLETELY. Do this by going under 'mounts and storage' > 'mount /emmc' or 'mount usb storage' in CWM
DO THIS GUIDE ONLY IF YOU HAVE ALREADY FLASHED BACK TO STOCK JFD THROUGH ODIN OR IF YOU NO LONGER HAVE ACCESS TO CWM. OTHERWISE READ THE NOTE ABOVE
WITH THAT BEING SAID THIS GUIDE DOES NOT FIX THE BUG. IT IS A WORKAROUND TO CREATE A PARTITION ON YOUR SD CARD TO BE ABLE TO USE YOUR "BRICKED" PHONE AGAIN
So lets begin:
Tools/Files Needed
-ADB (Android Debugging Bridge) and Android SDK must be set up on your PC.
Here is a guide that shows how to setup ADB and SDK with the necessary drivers:
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
-You need the latest ODIN 1.7 or whatever the latest version is along with the .pit file found here:
http://forum.xda-developers.com/showthread.php?t=848737
-Download this froyo .tar and extract it to the same directory where you have odin.
http://forum.xda-developers.com/showthread.php?t=833024&page=49
-Download CWM from here:
http://sourceforge.net/projects/stockodinjfd/files/update.zip/download
-Download any ICS rom Yes an ICS rom. You will use later to flash in CWM.
-You need a microSD card 8gb or larger which you will use to create the partition.
Thats it I think.
Here are the steps:
1. Enter download mode. Remove your battery/Then insert your battery/ hold both Volume Up and Down rocker and plug in your usb cable. You should now see the yellow android dude and it should say "Downloading".
2. Open odin and select the .pit file along with the froyo .tar file you've downloaded from above. Make sure "Re-Partition" is checked under options in odin. Click start and patiently wait for the process to be completed. DO NOT UNPLUG YOUR PHONE YET
Once odin finishes wait till the phone boots up with the new froyo rom youve just flashed.
3. Once your phone boots up and is setup copy CWM update.zip to the root of your external SD card. Do this by selecting the "mount usb storage" option in the notification bar.
Or
You can also copy the update.zip using a sd card adapter (only if your pc has an sd card reader).
You can use another phone or device which has a micro sd card slot. Just insert the sd card and plug in that phone via usb and copy update.zip.
You can also use adb to copy the update.zip.
adb remount
adb push update.zip /mnt/emmc
You must have the update.zip in the "platform-tools" folder in the android-sdk before executing the commands above.
4. BACKUP YOUR EXTERNAL SD CARD WHILE YOU CAN. IT WILL BE ERASED WHEN CREATING THE NEW PARTITION
5. Unplug your phone. Enter recovery mode using the 3 button combo or through adb using the following command: adb reboot recovery
Hit reinstall packages in recovery if CWM is not set yet. It will eventually install just keep clicking reinstall packages.
6. Once your are in CWM create the partition by going to 'advanced' > 'Partition SD Card' > Choose your data partition size 2gb is fine > Swap size 0M > You will get an error but just ignore it.
WAIT WAIT and WAIT it will take more than 5mins to create the partition. Just be patient it will eventually finish.
7. Connect your phone and while still in CWM mount your "USB Storage" under 'mounts and storage' > 'Mount USB Storage'. Then copy your ICS rom along with the update.zip (just incase) to flash. Don't flash update.zip though just keep it on your sd for future use.
8. Now while still in CWM umount your USB Storage. Go Back and select Wipe data factory rest / clear cache. Then install the ICS rom you've downloaded and flash it. (I used ICS Passion v13) Again be patient and wait till it finishes flashing and ignore any errors.
9. Once it has finished flashing it will eventually reboot. Or select 'reboot system now' in CWM if it already hasn't. Now this part you will have to be extremely patient. It may take up to 10mins or more to boot up. Once finished just set up your system using the setup wizard on your phone if there is one.
10. Check to see if your new partition has been successfully created by going to: Settings/Storage. You may see that your new partition is still 'unavailable' or it may say something like 00 for available storage. Don't worry just proceed to the next step.
11. Now to see if your partition is mounted properly. (Most likely not)Open the camera app and check to see if you get a message saying "Insert an SD card before using the camera." or something along those lines. If you get this message proceed to the following step. If not well you are lucky And you are now finished.
12. Now get ready to use adb so make sure adb debugging is enabled in Settings/Developer Options/ Android debugging [checked]
Open a command prompt on your pc in directory in which you installed your android sdk package. It should be something like this
C:\android-sdk\platform-tools
While in the platform-tools folder click on a blank space and Hold the SHIFT key + RIGHT CLICK > and select 'Open Command Window Here'. Now a command window should show up. If it doesnt show up well you didnt set up the SDK package properly go back to the guide which i suggested and make sure you have it set up properly or else you will not be able to issue commands.
13. With the command window open and your phone plugged in. Enter these commands to swap your external sdcard with your internal storage. This is the part where you will now use your new partition as your primary storage or internal storage.
Type in the following code into the command window or copy and paste it (easier) Remember to press the enter key after every command:
1) adb devices "This is to check if your device is properly attached"
2) adb remount "This is to check if your device is properly mounted"
3) adb pull /system/etc/vold.fstab "This will copy the vold.fstab file to the platform-tools folder on your PC."
3a) Now open the vold.fstab file you've just copied to your PC located in platform-tools. Right click vold.fstab and open it with notepad for editing.
Or you can also use a root explorer type of app on your phone
to edit the vold.fstab file. This might be the easier option. Just
remember to reboot your phone after editing the file.
3b) With the vold.fstab file open in notepad edit the following lines:
(They should be at the very end of the file and look something like this)
Line 1:
internal sdcarddev_mount sdcard /mnt/sdcard 1 /devices/platform/s3c-sdhci.0/mmc_host/mmc0#
Replace both instances of sdcard with emmc
Line 2:
external sdcarddev_mount emmc /mnt/emmc auto /devices/platform/s3c-sdhci.2/mmc_host/mmc2
Replace both instances of emmc with sdcard
Now that you have finished editing vold.fstab save the file close it and proceed to the next step.
3c) Now copy the edited vold.fstab file to your new partition by using the following commands:
adb remount "Followed by"
adb push vold.fstab /system/etc/vold.fstab "The file should now be overwritten."
REBOOT YOUR PHONE IF YOU DON'T GET ANY ERRORS WHEN EXECUTING THE COMMAND ABOVE.
(READ BELOW "IN RED" BEFORE REBOOTING IF YOU GET AN ERROR IN THE COMMAND WINDOW)
YOU ARE NOW FINISHED. AND SHOULD BE ABLE TO USE YOUR PHONE AGAIN WITH THE NEW PARTITION MOUNTED PROPERLY
IF YOU GET AN ERROR IN THE COMMAND WINDOW saying permission denied or something enter the following commands.
adb push vold.fstab /emmc/vold.fstab
adb shell
su
mount -o remount rw /system
cp /emmc/vold.fstab /system/etc/vold.fstab
chmod 644 /system/etc/vold.fstab
mount -o remount ro /system
exit
exit
adb reboot "This command will reboot your device so don't panic."
Once you have entered the commands above. Your phone will reboot. And the new vold.fstab file will be programmed to mount your new partition as your primary storage. And you should be finished by now. Now to test it open the camera app once again and see if you get any error messages. If so repeat step(s) 13. Otherwise You should now see that you have 1.88gb internal storage for apps etc and about 13 gb for the user (Assuming you have a 16gb) It should look something like this:
(Continued)
YOUR ARE NOW FINISHED AND SHOULD BE ABLE TO USE YOUR PHONE ONCE AGAIN. DOWNLOAD AN APP FROM THE MARKET TO SEE IF EVERYTHING WENT WELL. ALSO MOUNT YOUR PHONE TO YOUR PC TO SEE IF THE NEW PARTITION IS BEING RECOGNIZED.
Notes:
-Those of you who are new to ADB remember to hit enter after every command. dont just copy and paste all of them and expect them to work.
-You must perform step(s) 13 everytime after flashing a new rom. Reason for this is because the new vold.fstab file in the new rom will overwrite the old one you have edited in step 13. So keep that in mind.
-I have only tried this with the latest build of ICS Passion v13. It may work for other ICS roms aswell but i cannot confirm. I have tried it with a froyo rom but was unable to successfully mount the new partition. As for GB roms well you are going to have to try that your self. All you have to do is edit the vold.fstab file (Step 13) they should be identical if not similar.
-You can also edit the vold.fstab file using "Root explorer" app on your phone if you have it.
-Remember you no longer have access to your old internal memory since it is gone and I don't know what happened to it. SO SAY GOODBYE TO YOUR OLD INTERNAL STORAGE.
-Do not remove your SD CARD while your phone is on. It contains all of your system files and will probably make your phone blow up if you do so.
-If you haven't already flashed back to stock 2.1 and still have access to CWM you can skip to step 6 and create the partition from there. But remember to BACKUP YOUR SD CARD because it will be wiped.
I haven't tried this method but i assume it will work the same. Give it a try and let me know what happens
Good Luck and feel free to ask me any questions. I will be more than happy to assist you if you need any help.
[Reserved for future use]
I just read comment about the bug and your thread pops up. Great work!
Just for clarification, does this mean you must rely on the SD indefinitely to utilize the phone?
ast32 said:
I just read comment about the bug and your thread pops up. Great work!
Just for clarification, does this mean you must rely on the SD indefinitely to utilize the phone?
Click to expand...
Click to collapse
Yes... Once you've completed this guide your EXTERNAL SD CARD will then act as the INTERNAL SD CARD that was previously there prior to the bug. So in other words your sdcard will be your primary storage for the OS and other things such as music photos apps etc.
Merio90 said:
-Do not remove your SD CARD while your phone is on. It contains all of your system files and will probably make your phone blow up if you do so.
Click to expand...
Click to collapse
This also means that if you ever want to swap out any SD card, you will have to repartition your new one to fit exactly the same "smaller" partition and also find some program that will be able to pull your data from your 2g partition, save it to your desktop and then copy it over to your new partition on your new card. Or you may have to reflash whatever ROM you are wanting/restoring from scratch. You are new essentially SDcard branded to your phone.
My old phone had 2.1 with no upgrade EVER from the manufacturer. So me and a few others began building/kanging 2.2 and with 2.2's ability of app2sd we had to figure out a way to do that for it to work. Long story short, with a few init hijacks at boot and some ADB we were able to get apps to install directly to a partition that we created on our SD cards. Went from 170mb internal to "you pick the size" partition on the external. I still have that phone and do some dev-ing on it and have brought a 2.1 all the way to CM9.
If anyone needs help with the partitioning, just ask. Also, 2gb is the standard but 2gb is a ton of space. Figure that your biggest app is going to be around 20-30mb executable. 1gb is 1024mb, you can do the math but it is also your call.
Problemo
So, this guide is great, but one of the initial problems was connecting to my SD card, when I plug in via usb my computer doesn't even recognize I plugged in. How am I to get the "update.zip" and the CFW on to it? also, when I use Clockwork, I can't seem to make my partition work... I've done it many many times, but nothing. it's almost like it doesn't even work... I just have the standard 2gb micro SD, so I make a partition of 1024mb. But it doesn't seem to work.
tabthelab said:
So, this guide is great, but one of the initial problems was connecting to my SD card, when I plug in via usb my computer doesn't even recognize I plugged in. How am I to get the "update.zip" and the CFW on to it? also, when I use Clockwork, I can't seem to make my partition work... I've done it many many times, but nothing. it's almost like it doesn't even work... I just have the standard 2gb micro SD, so I make a partition of 1024mb. But it doesn't seem to work.
Click to expand...
Click to collapse
Try using the sd card adapter that came with your phone to copy the update.zip. That's if your computer has an sd card slot. Or simply use another phone to copy it by inserting the sd into that phone and plugging in the usb cable.
Right when you finish flashing the 2.2 .tar it should mount properly to your pc. Just select usb storage from the notification bar.
Sent from my Galaxy Nexus using XDA
Merio90 said:
Try using the sd card adapter that came with your phone to copy the update.zip. That's if your computer has an sd card slot. Or simply use another phone to copy it by inserting the sd into that phone and plugging in the usb cable.
Right when you finish flashing the 2.2 .tar it should mount properly to your pc. Just select usb storage from the notification bar.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
I'm getting the same problem as him. and when i flash the 2.2 tar, it goes straight to stock recovery. it doesn't boot up android. even in cwm, my phone instantly "partitions" the sd card. and it only has a 1024mb option. no 2gb. And when you press mount usb, it does nothing at all. my computer shows two devices that haven't been mounted. Any ideas? i've been trying to fix this phone for almost a week straight and nothing works....
EDIT:I have no idea what just happened but i rebooted a few times and its starting to boot up.
Yep.
Exactly the same thing. I do have another phone that I can do all of that on, but it matters not it I can't even recognize the SD card to partition. I think it could (which doesn't really makes sense to me) be the fact we're using the standard 2gb one, I should go get a bit of a bigger one.
Either way, if it works or not, I can just give it to my fiance to use on her phone :\
I will keep tinkering though, and I'll of course post my results, if I have any.
---------- Post added at 05:04 AM ---------- Previous post was at 04:55 AM ----------
I just used my ladys phone to partition my sd card. ICS Passion makes me so angry, so instead of partitioning the SD CARD, it partitioned her internal memory, yay. phone is all clean. ffs.
Okay, so I figured out how to fix the problem with the partitioning. If you are able to install a zip file from recovery, install the ICS Passion kernel with CWM 5.x.x.x http://dl.dropbox.com/u/33572867/ICS_Passion_v13_cleanup.zip
You might have to rename it to update.zip but I think it should work for everyone. From there reboot recovery into the new kernel CWM. Now when you try to partition the sd card, it should take a long time and it should work.
tabthelab said:
Exactly the same thing. I do have another phone that I can do all of that on, but it matters not it I can't even recognize the SD card to partition. I think it could (which doesn't really makes sense to me) be the fact we're using the standard 2gb one, I should go get a bit of a bigger one.
Either way, if it works or not, I can just give it to my fiance to use on her phone :\
I will keep tinkering though, and I'll of course post my results, if I have any.
---------- Post added at 05:04 AM ---------- Previous post was at 04:55 AM ----------
I just used my ladys phone to partition my sd card. ICS Passion makes me so angry, so instead of partitioning the SD CARD, it partitioned her internal memory, yay. phone is all clean. ffs.
Click to expand...
Click to collapse
Your mistake sorry. The only reason why I suggested using another phone was to simply copy CWM while having the already partitioned sd card in your lady's phone. Now i don't why you decided to create the partition on your lady's phone a second time...this was obviously going to wipe the internal memory since it is still intact.
Try this
For those of you having trouble copying CWM to the sd card try the following commands. You can execute these commands through stock recovery or with the phone already set up and going. Just remember you must have usb debugging enabled on your phone.
check to see if the phone is mounted: adb devices
now copy CWM to your sdcard: adb push update.zip /emmc/update.zip Just make sure that CWM is named
update.zip
To be honest the easiest way to copy CWM to your sd card is to use another phone or device which has a microsd card slot. Or if your computer happens to have sdcard slot simply use an sdcard adapter and copy CWM.
maybe it's not meant to be
So, I've done nearly everything I can even think of. I got the ICS installed but I keep getting the "power reset" or "unknown upload mode" now. I swear.... haha.
did you get the sd card partitioned? if so, odin back to froyo eugenes rom, install cwm, factory reset, wipe cache, and reinstall the passion 13 rom. I had the same problem and i think thats what i did to fix it.
alright. I see. Let me try that.
---------- Post added at 07:11 AM ---------- Previous post was at 07:09 AM ----------
did you have "re-partition" checked though??
yes i did.
Nirmalspeed said:
did you get the sd card partitioned? if so, odin back to froyo eugenes rom, install cwm, factory reset, wipe cache, and reinstall the passion 13 rom. I had the same problem and i think thats what i did to fix it.
Click to expand...
Click to collapse
@Nirmalspeed...Did you successfully partition the sdcard? I'm just wondering if your were able to successfully complete the guide. How did you manage to copy CWM to your sdcard? By any chance did you try anything different?
trying something now, I might have fudged up for a very obvious reason...
Merio90 said:
@Nirmalspeed...Did you successfully partition the sdcard? I'm just wondering if your were able to successfully complete the guide. How did you manage to copy CWM to your sdcard? By any chance did you try anything different?
Click to expand...
Click to collapse
what i did was that i flashed the ICS Kiss kernel that i linked on page one of this thread. And from there i was able to partition the sd card no problem. After i partitioned it, i had to redo everything from step 1 except i skip the partitioning. If i don't redo those steps, the rom gives me an error for some reason.
I'm getting a boot load!?!?! XX XX X fingers and toes crossed.

[Q] Aw Carp, someone else needs help!

Sorry, I know there's a million threads on xda for people requesting help so I hope someone can help me.
I don't know why but my phone won't mount it's storage. When I try to flash a .zip through CWM, the phone just states it can't mount /sdcard/. When I power the phone on, and I plug it into my PC, the PC says it doesn't recognize the device. Trying to boot the phone into RSD mode makes it semi-recognizable, but is only recognized as a composite device, and I am nervous about flashing back to stock. I haven't tried fastboot and the only time I mess with it is to unlock my photon again.
If anyone has some sage advice, I would be more than grateful for it. Thank you!
What rom are you running? and were you able to mount before a possible flash or update? need more info first before assistance can be given
Oh sorry, I forgot! I'm Running MIUI build MIUI.us_sunfire_v4_2.3.30. and I was able to mount without any incident at all. In fact, I didn't even notice it until just recently, because post-flash of MIUI I was still able to use my usb storage without a hitch. And I was able to flash before.
ok so are you referring to the internal sd/external/both? if external try testing the card in a stand alone reader to see if it could possibly be corrupt
The SD card is definitely okay, and I experience the issue with the SD card in the phone and out. In fact, I don't usually have one in my Photon because of the internal storage.
so external sd then? are you able to see the internal sd? if so try flashing a nandroid back up through the internal and see if you regain connectivity
Hey, I hadn't, unfortunately, had more time to troubleshoot my phone. But I basically was unable to restore from a backup because it was saying /sdcard directory does not exist. I was, strangely enough, able to reinstall the drivers from my PC and RSD back to stock 198_6. However, I still get an error message that my device has malfunctioned when I plug into PC, and just to test, trying to do an "apply update.zip via sd card" in the stock recovery 3e just gives me the same message.../sdcard directory does not exist.
Zimmle said:
Hey, I hadn't, unfortunately, had more time to troubleshoot my phone. But I basically was unable to restore from a backup because it was saying /sdcard directory does not exist. I was, strangely enough, able to reinstall the drivers from my PC and RSD back to stock 198_6. However, I still get an error message that my device has malfunctioned when I plug into PC, and just to test, trying to do an "apply update.zip via sd card" in the stock recovery 3e just gives me the same message.../sdcard directory does not exist.
Click to expand...
Click to collapse
Sorry if this is too obvious a question but does the /sdcard directory exist? Can you navigate to it with a file explorer and open it? Does it look like the structure is intact?
CCallahan said:
Sorry if this is too obvious a question but does the /sdcard directory exist? Can you navigate to it with a file explorer and open it? Does it look like the structure is intact?
Click to expand...
Click to collapse
Ah, as strangely enough, I can. I can even navigate to /mnt/sdcard and /mnt/sdcard-ext. So there's a /sdcard directory and the previous two. in the /mnt directory there are /usbdisk1.0-7 files as well. Not sure if that helps, though...
Woo! Information bump! So I've been fiddling with my photon and from what I can tell, I get the same issue on 3 PCs(2 at home and 1 at work) where windows states the device has malfunctioned. I don't think it's a driver issue because it's happened multiple times on different PCs, and I know one of them definitely works.. I can definitely navigate to the /sdcard but my PC and phone recovery won't find it. Is there a way I can force the phone to mount it via fastboot? I will literally do ANYTHING to get my phone's internal storage to be read and any help would be mega appreciated!
Weren't people having issues when downgrading from a 198_7 base rom to stock 198_6. You have done a lot of fiddling around that you may have done something by accident and not have even noticed. Btw I believe anything ics based has to have 198_7 as the phones primary. Could be wrong.
That could have been the start of your problem from the beginning
just want to throw in my two cents. when I was haveing a problem with usb I couldnt mount it in cwm. Once i switched to twrp recovery i was able to mount just fine.
To everyone in this thread, THANK YOU! You guys are what make the xda community awesome. And apparently, I got it all figured out. Not sure what I did, but now the computer is recognizing the phone and so are all my other computers.
Still eternally grateful, though, to everyone in this thread.

[HOWTO] Install CM9 on 8GB Nook Tablet

The 16GB Nook Tablet was released in the United States on Nov 17, 2011 (about 6 months ago). It is reasonably well-documented and a great deal of progress has been made on getting it to do cool stuff that its developers did not intend.
On February 21, 2012 (about 2 months ago) Barnes and Noble released an 8GB version of the Nook Tablet. It is much newer and most of the developers on XDA who were going to work with the Nook Tablet had already purchased 16GB devices by the time the 8GB was released; therefore, it is not documented nearly as well and many of its quirks are not as well known.
The purpose of this thread is to begin the process of documenting the differences between the two tablets. I spent a lot of time messing around with unsuccessful processes and asking questions to people who didn't know answers, and would like to contribute by saving that time for others.
By following this guide, you will be able to take an 8GB Nook Tablet out of the box and get it running an alpha version of CM9.
As of 04/25, CM9 for the Nook Tablet is an alpha state and many, many things do not work. I urge you not to try this yet unless you want to contribute to the development process, because you might irreversibly mess up your $200 toy. I am not responsible if you do this. Please, please do not try this unless you know what you are doing!
You will need:
8GB Nook Tablet (duh)
1 MicroSD card that you don't mind wiping
Linux (I only know how to flash images to an SD card using Linux, if someone else wants to add Windows instructions it's appreciated, but honestly if you can't find your way around Linux you shouldn't do this)
ADB properly set up (there are other guides on how to do this, I will add it in later if necessary)
Some way of writing to a MicroSD (an SD reader preferably, you could use an android device but I would feel much safer with just an SD reader)
The recovery image from the bottom of this post (ignore the instructions, just get the image. Meghdoot please let me know if I can just include the direct link in this post.)
CM9 Alpha 0.03 zipped package from this post (filename: update-cm9-acclaim-alpha0.03-fullofbugs.zip)
Google Apps ICS flashable zip (optional, find it somewhere if you want it)
Actually flashing CM9 is not that hard. The problem is that we want to make sure we have a way out of any problems we might cause (maybe you get sick of CM9 for example.) There are slight differences between the 8 and 16GB versions of the NT. These differences make a lot of the recovery methods for the 16GB not work on the 8GB. Do NOT flash anything to your tablet unless you are sure it works for the 8GB model!
Overview: What We Are Going To Do To Your Tablet
Create ClockWork Mod Recovery SD card
Back up your existing stock system
Save rombackup.zip, which contains files that are critical to the Stock OS
Flash CM9
Step 1: Create CWM Recovery SD Card
This step is the most important because it lets us do just about everything else. It is very important that you follow this step precisely and not cut corners; for example, it is tempting to use xIndirect's Nook Tab Recovery Flasher app because it downloads CWM and flashes it to your tablet so you don't have to mess with an SD; the CWM version it flashes will not work on the 8GB tablet, and once you realize this and use the app to "revert to stock recovery", you will find that you have reverted to a 16GB stock recovery. I made this mistake, and so far don't know how to undo it (hopefully I won't have to).
1) Get your SD card readable in your computer
Alternate, perhaps easier method: Copy the contents of this file onto the sd card. Either do this or steps 2-4 below, whichever you prefer.
2) Unmount your SD card, but do not remove it
3) Unzip the CWM image you downloaded above, which should contain myrecovery.img
4)In Linux, do the following:
Code:
sudo dd if=myrecovery.img of=WhateverTheMountPointofSDCardIs bs=1M
Don't know how to find what your SD card's mount point is? TURN BACK.
In Windows, do the following:
lavero.burgos said:
- Format your sdcard with SDFormatter (recommended) or any other but not windows native.
- Download latest Win32DiskImage-binary.zip from https://launchpad.net/win32-image-writer/+download
- Unzip the file
- Run Win32DiskImage.exe - Right click "run as administrator"
- Click the folder button and navigate to select the .img file you just unzipped.
- Click on the disk drive letter label on the right, and choose the letter that corresponds to your SD card.
- Press Write. When it finishes, press Exit.
- Safely eject/remove your sdcard and put it back to your NT
- Plug your device to the a/c power or PC using the USB cable, let it power on by itself do not press any button.
Click to expand...
Click to collapse
Once this is done you should be able to place the SD card into your Nook Tablet, power it down, plug the USB cable while it is off, and it will turn on, show the Nook logo, a white screen with a cardboard box, and then load up CWM recovery.
Step 2: Nandroid Backup
This should be the simplest way to have a plan B - if you want to go back to stock ever, this should do it.
1) In ClockworkMod Recovery, press volume down until Backup and Restore is highlighted; press the home key to select it.
2) Choose "Backup to Internal Sdcard"
3) After a few minutes, verify that the backup was successfully completed.
You should have about 3.5GB free on your eMMC before the backup, and the backup will likely take about 800MB. (Please chime in if your backup is bigger / smaller.)
Step 3: Get Rombackup.zip
This file is very important. In the event that your tablet is completely borked, we could try flashing an image of a stock OS to it; however, there is a file in the stock OS called rombackup.zip which identifies your Nook when it tries to connect to BN's services. If you flash someone else's image you will have someone else's rombackup.zip and BN will not let you in.
1) On Ubuntu, with your tablet in CWM Recovery, do
Code:
$ adb shell
This will open up a terminal to your tablet, where you must type these commands VERY PRECISELY (!!!!):
Code:
mkdir /mnt
mkdir /mnt/factory
mount -t ext4 /dev/block/mmcblk0p7 /mnt/factory
exit
2)After "exit", you will be returned to your Ubuntu terminal; from there do
Code:
adb pull /mnt/factory/rombackup.zip
3) Put that file somewhere safe! Dropbox is a good idea.
Step 4: Flash CM9
1) Reboot your tablet into stock OS one last time.
2) Mount your nook's storage to your PC
3) Place the cm9 update zip file you downloaded above onto the nook's storage
4) Reboot into CWM Recovery
5) Choose "Install zip from sdcard"
6) Choose "Choose zip from internal sdcard"
7) Find the CM9 zip, flash it
8) Find gapps (if you got it), flash it
9) NOT OPTIONALChoose "wipe data/factory reset" (if not visible, press power button to go back)
10) Reboot, pray
Your tablet should boot into a shiny new operating system. If you get tired of it, just restore stock using nandroid (takes seconds and works without a problem.) The experience within CM9 is not so different from the 16GB; however you will find since it only has 512MB of ram instead of 1GB, apps have to restart a lot more frequently than you would hope, because they are killed by Android's memory management if you hop to too many other apps. That's the tradeoff for the $50 you saved, cheapskate.
MANY THANKS TO:
The entire CM9 Nook Tablet team (too many to list)
Meghdoot for producing a working 8GB recovery + answering some ?s
fattire, bauwks, etc - for cracking the **** out of the security on these things
Anybody else I left out - this dev community just amazes me
Lastly - this is my first attempt at being useful on XDA, so please let me know if I made any mistakes, or if there is something you think I should add.
Worked perfectly. Thank you for taking the time to do this.
Windows Instructions
- Power off your NT and remove sdcard
- Put your sdcard into a card reader (preferably)
- Format your sdcard with SDFormatter (recommended) or any other but not windows native.
- Download latest Win32DiskImage-binary.zip from https://launchpad.net/win32-image-writer/+download
- Unzip the file
- Run Win32DiskImage.exe - Right click "run as administrator"
- Click the folder button and navigate to select the .img file you just unzipped.
- Click on the disk drive letter label on the right, and choose the letter that corresponds to your SD card.
- Press Write. When it finishes, press Exit.
- Safely eject/remove your sdcard and put it back to your NT
- Plug your device to the a/c power or PC using the USB cable, let it power on by itself do not press any button.
~ Veronica
lost101 said:
Worked perfectly. Thank you for taking the time to do this.
Click to expand...
Click to collapse
what have you noticed working vs not working?
jshields1986 said:
what have you noticed working vs not working?
Click to expand...
Click to collapse
It's very impressive. Anything said here about the rom running on 16gb NT applies.
lost101 in a PM said:
Download "8gb-16gb_cwm_sdcard.zip" from here.
Follow instructions and put SD card in Nook Tablet.
In CyanoBoot Menu > Boot from SD Card Normal.
Perhaps some people might find it of value if you added this to your tutorial as the current method of accessing CWM on a 8gb Nook Tablet.
Click to expand...
Click to collapse
I suppose; however, I'm still able to easily get to CWM from the same SD card I used to flash CM9, either by booting while holding the N key (I guess this doesn't work for everyone?) or shutting off the device and plugging it in. Either way seems to get CWM going from the SD card, though I suppose you could also do cyanoboot; my understanding is that that should work without any additional files as well.
Download "8gb-16gb_cwm_sdcard.zip" from here.
1 - Follow instructions and put SD card in Nook Tablet.
2 - In CyanoBoot Menu > Boot from SD Card Normal.
Perhaps some people might find it of value if you added this to your tutorial as the current method of accessing CWM on a 8gb Nook Tablet.
Click to expand...
Click to collapse
That's with working a link.
You can also skip step one and put these files onto an SD card.
So I've followed the directions precisely, but can't seem to boot into recovery. Plugging in while powered off just boots normal, and holding "n" and power just gives the factory reset options. I want to check one step in the OP's instructions:
Code:
sudo dd if=myrecovery.img of=WhateverTheMountPointofSDCardIs bs=1M
By mount point do you mean the /media/XXXXXX folder it mounts to, or the /dev/sdx? I tried both, but neither seemed to work.
Also, by SDcard, you do mean an external microsd card, yes? Or are you talking internal storage?
And finally, what's the output supposed to look like from the above line of code?
AbbaSou said:
So I've followed the directions precisely, but can't seem to boot into recovery. Plugging in while powered off just boots normal, and holding "n" and power just gives the factory reset options. I want to check one step in the OP's instructions:
Code:
sudo dd if=myrecovery.img of=WhateverTheMountPointofSDCardIs bs=1M
By mount point do you mean the /media/XXXXXX folder it mounts to, or the /dev/sdx? I tried both, but neither seemed to work.
Also, by SDcard, you do mean an external microsd card, yes? Or are you talking internal storage?
And finally, what's the output supposed to look like from the above line of code?
Click to expand...
Click to collapse
I personally used the win32 method, but I suspect there would be no output unless an error occurred.
FYI, I updated to the latest build of CM9 by wiping in CWM and flashing it. No need for a *special* 512mb build.
AbbaSou said:
So I've followed the directions precisely, but can't seem to boot into recovery. Plugging in while powered off just boots normal, and holding "n" and power just gives the factory reset options. I want to check one step in the OP's instructions:
Code:
sudo dd if=myrecovery.img of=WhateverTheMountPointofSDCardIs bs=1M
By mount point do you mean the /media/XXXXXX folder it mounts to, or the /dev/sdx? I tried both, but neither seemed to work.
Also, by SDcard, you do mean an external microsd card, yes? Or are you talking internal storage?
And finally, what's the output supposed to look like from the above line of code?
Click to expand...
Click to collapse
On my desktop computer, the argument I used read "of=/dev/sdc". This will likely not work on your computer, as the mount point won't be /dev/sdc on yours, but that's the format you should follow.
Make sure all three arguments are there and it should work, after about 3-4 seconds you should see a message saying how long it took and how many bytes were copied.
And yes, what this step does is to copy on to an external microSD card; if you instead use the mount point of the user-accessible storage partition of your Nook's eMMC, it won't work.
If it doesn't work, double check that you are flashing the correct file, and perhaps redownload it (not sure if meghdoot made md5sums available or not but that may be worth a check.)
lost101 said:
That's with working a link.
You can also skip step one and put these files onto an SD card.
Click to expand...
Click to collapse
I guess I may be misunderstanding what you are looking to accomplish; are you trying to make it so you can get into recovery without plugging the tablet in? If so that can be accomplished without any extra steps, once CM9 is succesfully installed:
Power the tablet on while holding the home key (doesn't work on every NT apparently)
At Cyanoboot prompt, which should come up whenever you power the tablet on without holding the home key, you can THERE hold the home key and select "SD Card Normal" (not "SD Card Recovery")
RomBackup.Zip
In the O.P., your step 3 says...
"Save rombackup.zip, which contains files that are critical to the Stock OS"
Could you make a copy of that file available for download?
I was one of the early testers who tried to flash CWM & CM7a onto the internal EMMC memory. Of course, it bricked my NT8 and now I can ONLY boot from a (bootable) SDCard.
I am running CM7a from an SDCard now and it works fine. But, I would like to get my NT8 back to working (something) on the EMMC.
Perhaps, if I could push (or flash, or backup) the rombackup file to my device, it would restore the missing "critical" files? I can do ADB & CWM works from SDCard. I figure that it is worth a shot since I am pretty sure that I have tried every other "solution" on XDA - all failed.
Any suggestions would be greatly appreciated.
raywaldo said:
In the O.P., your step 3 says...
"Save rombackup.zip, which contains files that are critical to the Stock OS"
Could you make a copy of that file available for download?
Click to expand...
Click to collapse
This is the contents, however the values in some of the files are unique to each device. Maybe changing some of the values in the files would work for you.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
RomBackup.Zip
lost101 said:
This is the contents, however the values in some of the files are unique to each device. Maybe changing some of the values in the files would work for you.
Click to expand...
Click to collapse
Thanks. I see what you mean about the unique values. I don't know how I could do much with this data however.
Interestingly, my s/n is still intact. When I do ADB, it displays properly. But SOMETHING is still missing and it will not boot internally.
Thanks again for the response.
Your article is well-written and would have been a great help to me BEFORE I bricked it.
raywaldo said:
Thanks. I see what you mean about the unique values. I don't know how I could do much with this data however.
Interestingly, my s/n is still intact. When I do ADB, it displays properly. But SOMETHING is still missing and it will not boot internally.
Click to expand...
Click to collapse
Have you tried creating a Rombackup.zip as described? It sounds like you may still have all the files.
raywaldo said:
In the O.P., your step 3 says...
"Save rombackup.zip, which contains files that are critical to the Stock OS"
Could you make a copy of that file available for download?
I was one of the early testers who tried to flash CWM & CM7a onto the internal EMMC memory. Of course, it bricked my NT8 and now I can ONLY boot from a (bootable) SDCard.
I am running CM7a from an SDCard now and it works fine. But, I would like to get my NT8 back to working (something) on the EMMC.
Perhaps, if I could push (or flash, or backup) the rombackup file to my device, it would restore the missing "critical" files? I can do ADB & CWM works from SDCard. I figure that it is worth a shot since I am pretty sure that I have tried every other "solution" on XDA - all failed.
Any suggestions would be greatly appreciated.
Click to expand...
Click to collapse
After 3 weeks just been able to boot CM7 from sd I succesfully installed CM9 in EMMC on my NT8. I wasn't able to restore anything else into the EMMC after I bricked it trying to install CM7.
I'm very satisfied with CM9. Fo me is more responsive than running CM7 from sd.
RomBackup.Zip
lost101 said:
Have you tried creating a Rombackup.zip as described? It sounds like you may still have all the files.
Click to expand...
Click to collapse
I was able to create the backup file... Rombackup.zip
Attached is a screen shot of the contents. Notice that it is down a few layers of directories: /rom/devconf/ Is that correct?
However, I have not had any success in getting CM9 (or any other ROM) to run on the EMMC.
raywaldo said:
I was able to create the backup file... Rombackup.zip
Attached is a screen shot of the contents. Notice that it is down a few layers of directories: /rom/devconf/ Is that correct?
However, I have not had any success in getting CM9 (or any other ROM) to run on the EMMC.
Click to expand...
Click to collapse
Yes, everything is correct. What method are you using to install CM9? Have you tried installing 0.03 using CWM?
lost101 said:
Yes, everything is correct. What method are you using to install CM9? Have you tried installing 0.03 using CWM?
Click to expand...
Click to collapse
Be aware that after you install CM9 and reboot into Cyanoboot it will try to boot from the alternate partition by default so you'll get an error message. You need to force Cyanoboot menu by pressing the n while booting and then select boot from eMMC normal (where CM9 is located).
Later you can change default boot in /bootdata by following instructions from fattire about
Cyanoboot .
Sent from my NT8 with CM9.
lumav said:
Be aware that after you install CM9 and reboot into Cyanoboot it will try to boot from the alternate partition by default so you'll get an error message. You need to force Cyanoboot menu by pressing the n while booting and then select boot from eMMC normal (where CM9 is located).
Later you can change default boot in /bootdata by following instructions from fattire about
Cyanoboot .
Sent from my NT8 with CM9.
Click to expand...
Click to collapse
I have no such problem with NT8, Cyanoboot boots from eMMC automatically. But then I still have the nook partition and never tried to flash CWM internally.

[Q] Bricked nook tablet (boot video added)

My nook tablet is bricked
Turn on the tablet will see the screen will a big n
and nothing happen
I tried to boot from sdcard but it seem don't recognize the sdcard during boot
putting zip files on sdcard is not working
CWM sdcard and ubuntu sdcard also not working
cannot get into CWM and how can I fix it?
I spend over 5 hours but nothing work......
Sometimes the SD Card boot "only" works by plugging in the nook power cable.
I tried more than 50 times by plugging the power cable and still the same....
BTW thank you for answering, if you have any other method, once I can do it, I will try it....
Is the Nook store near by ?
Sad to say no...
I am from Hong Kong....
What SD card are you using, i.e. Class and brand.
The higher class cards do not work all that well for booting from. The Sandisk Class 4 card, any size I imagine, works well for booting off card.
Not sure if this is your problem, but trying a different card my be a good direction to go for a fix, if you can get into CWM it will help.
Also, what specifically did you do/try to get yourself to this point? Always helps to know how you broke it to be able to fix it.
I am using sandisk class sd card
This happen will I try to change back from CM9 with new kernel and TWRP to CWM and CM7.2
After flashing CM7.2 and CWM, it successfully boot for once and then get into this situation on next reboot
I tried ubuntu recovery, sdcard version CM7.2 and this, but nothing work....
It looks like you have a similar problem to this http://forum.xda-developers.com/showthread.php?p=27381972. I think, form skimming over the thread they were able to get into CWM from sdcard - after many attempts. If you can get to that point you should be able to get an adb connection where as you can work your way out of this. Just read the linked thread, it should point you in the right direction.
Good Luck
I tried more than 100 times still noting happen
But when plugging in the power cable and boot the tablet, the indicator keep orange light and not green as it is in that post...
more options
what sdcard version of CWM are you using? you should try with another sdcard just in case, the procedures for a succesful CWM sdcard are the following:
For Windows users:
- Power off your NT and remove sdcard
- Put your sdcard into a card reader (preferably)
- Format your sdcard with SDFormatter https://www.sdcard.org/downloads/formatter_3/eula_windows/ (recommended) or any other but not windows native.
- Download latest Win32DiskImage-binary.zip from https://launchpad.net/win32-image-writer/+download (v5.0 recommended)
- Unzip the file
- Run Win32DiskImage.exe - Right click "run as administrator"
- Click the folder button and navigate to select the .img file you just unzipped.
- Click on the disk drive letter label on the right, and choose the letter that corresponds to your SD card.
- Press Write. When it finishes, press Exit.
- Safely eject/remove your sdcard and put it back to your NT
- Plug your device to the a/c power or PC using the USB cable, let it power on by itself do not press any button.
WARNING: This will completely erase your microSD card. Be sure to back it up!
Click to expand...
Click to collapse
You may also want to try the unbrick methods posted by @succulent here in his repo - Original Thread (PLease READ)
flash-restore-stock.zip could be useful for you
~ V
I can now go into the recovery by using a new transcend class 10 card
But I after I flash flash_stock_recovery.zip and CM7, it still behave the same
Still showing the big n and nothing loaded....
slxar said:
I can now go into the recovery by using a new transcend class 10 card
But I after I flash flash_stock_recovery.zip and CM7, it still behave the same
Still showing the big n and nothing loaded....
Click to expand...
Click to collapse
OK let me get in puter I have other options. Obviously something in the boot process is corrupted
Edit: back!
Please try the following:
1. Verify the md5sum the ROM(s) you want to install just to make sure is not corrupted
2. Follow the instructions i posted in here to flash another CWM to discard CWM being part of the problem. Now as you already have the CWM sdcard you just need to add 8gb-16gb_cwm_internal.zip to the sdcard then boot again into CWM sdcard and flash that package
3. After that remove your sdcard and select reboot system now from the CWM menu, if your device boots fine then Congrats, if not then read the options below:
4. Read and try this. If no go, goto #5:
5. Read and try this
LAST RESOURCE:
6. [unbrick] - Fixing partition table, or completely dead nook. Use this ONLY if you have the 16GB model as you did not mention that detail in your posts i'm giving you a warning!
~ V
Sent from my SGH-I897 using Tapatalk 2
method 4 and 5 not working and I can't download a file told in method 6 here, the second file show 404...
slxar said:
method 4 and 5 not working and I can't download a file told in method 6 here, the second file show 404...
Click to expand...
Click to collapse
Right i forgot to add that @meghd00t's cwm sdcard already contain the 2 files (tools) that @soshite was talking about , so basically you just need the cwm sdcard, my partition images and adb working.
BTW what happened with option 2-3?
~ V
Sent from my SGH-I897 using Tapatalk 2
after trying option 6, the tablet now can boot into internal CWM
But after I flash CM7, it still keep booting into CWM rather than CM7....
Thanks for all, I can now get into the stock 1.4.0
I flash the flash-restore-stock.zip from here in CWM
and then using acclaim_update.zip to restore the tablet back to 1.4.0
I guest I may change the boot data and get mess up with it
Finally, thanks again for all help:laugh:
Yeah, for everyone else out there:
You must have stock recovery in order for the acclaim_update.zip to work.

Categories

Resources