[Guide] SD Partition for Encryption Unsuccessful (ICS Bug) - Vibrant Q&A, Help & Troubleshooting

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.

Related

[Q] idiot (me) w/ empty sdcard & inaccessible ext-sd, can't get anywhere

My Vibrant's internal sdcard was reporting corruption, so I put a fresh ROM (Macnut 12) on the external SD, rebooted into Clockwork, and formatted the SDcard, system & data partitions. Then went to install the ROM, but it turned out it wouldn't recognize the ext-sd card either! I get this error when i try to mount:
Code:
E:INFO is WRONGError mounting SDEXT:!
I've tried a different ext-sd, and even tried formatting that one on the computer (MBR partition scheme, FAT partition). Nothing is recognized by the phone.
Also when I try "mount USB storage" nothing shows up on my desktop either.
SO: I have an almost empty phone, and no way of putting any ROM whatsoever on there. Can anyone point me in the right direction?
note: i have a Mac, so AFAIK ODIN doesn't work for me.
I'm in "Clockwork 2.5.1.0 lagfix edition", and was previously rocking Eugene's Macnut R12 with the JFS+RFS lagfix.
thanks!
~peter in oakland
wrong section
huzzam said:
NOTE: I figured this out, don't bother replying! thanks for looking
My Vibrant's internal sdcard was reporting corruption, so I put a fresh ROM (Macnut 12) on the external SD, rebooted into Clockwork, and formatted the SDcard, system & data partitions. Then went to install the ROM, but it turned out it wouldn't recognize the ext-sd card either! I get this error when i try to mount:
Code:
E:INFO is WRONGError mounting SDEXT:!
I've tried a different ext-sd, and even tried formatting that one on the computer (MBR partition scheme, FAT partition). Nothing is recognized by the phone.
Also when I try "mount USB storage" nothing shows up on my desktop either.
SO: I have an almost empty phone, and no way of putting any ROM whatsoever on there. Can anyone point me in the right direction?
note: i have a Mac, so AFAIK ODIN doesn't work for me.
I'm in "Clockwork 2.5.1.0 lagfix edition", and was previously rocking Eugene's Macnut R12 with the JFS+RFS lagfix.
EDIT: "adb push" has saved the day!
thanks!
~peter in oakland
Click to expand...
Click to collapse
I also use a mac. You need to be careful how you delete and format your sd cards. I just deleted some stuff off my sd card by dragging it into the trash and it didnt free up any space on the sd card. I have also seen problems with formatting them with the mac also. Also ODIN is a great way to put things back to stock. you will need to use bootcamp to install windows on the partition. If I weere you I would still ODIN back to stock and reflash to make sure you dont have errors in the future
Format sd card through clockworkmod recovery. Itll wipe everything, but it should bring it back to being usable. Also heimdall works with mac right? I havent used heimdall but read its an open source rom flasher replacement for odin.
Sent from my SGH-T959 using XDA App
I was going to suggest Heimdall as well. You should be able to flash back to a stock firmware, then sort things out from there. If you want to do that and then report back here, we could help from there.
Information about Heimdall is available in this thread along with a link to download the program.
Good luck.

How to root 1.4.1 (or any other version) using just an sdcard {easy}

This method uses the files and method to install CWM from Goncezilla I just threw together the method to flash superuser and I'll work on getting rid of
Features of this root: It installs su, superuser apk, gapps
Future Features: Suggest something.
Note: Windows instructions are in this post
Changelog:
2.2: Removed all additions, sticking with basics for now.
2.1: Removed unknown source fix, removed adw and homecatcher due to problems with Gapps.
2.0: Sets unknown sources to be allowed since B&N wanted to play "hard to get" with that. Enjoy guys.
1.5: Included adw and homecatcher apk's, NTHidden settings as well.
1.0 Initial zip / method release.
Linux only instructions (unless you substitute the instructions with a known windows equivalent)
1. Setup SDCard
Using a new SDCard (not one you have info stored on) make a new MSDOS partition table and add a 50 MB FAT32 partition as the first primary partition. Then make sure you enable to boot and lda flags.
Any SDCARD larger than 50 MB should work but I used an extra 2GB laying around. You can add other partitions to the card if you want, but it is not necessary to allocate the entire card. Any added partitions would need to be manually mounted on your Nook anyway.
I used GParted on my Ubuntu machine to do this but any formating tool should work.
2. Copy Files onto SDCard
You can grab the files I used here:
http://www.mediafire.com/?dr6bqau194389te
Just UnZip the files directly to the root of the boot partition you created above (make sure flashing_boot.img, u-boot.bin, and boot.img are on the root not the folder SDCARD)
3. Insert SDCARD into NT
Now, with your NT powered off, eject the SDCARD you just created from your computer and insert it into the tablet. Then just turn it on and VOLA! You should now be in CWM!
Now you just need to download this zip file:
http://goo-inside.me/apps/Indirect/Nook_tablet/Flashable_Zips/Gapps_and_root.zip
just put onto the /mnt/media/ directory or you can push to /emmc/ while in CWM.
Credits:
loglud for taking the time to write instructions for windows.
ChainsDD for superuser and SU
Bauwkz for the exploit to be able to make a bootable sdcard
Nemith for the recovery
Goncezilla for the sdcard method (I didn't feel like typing it all out.)
Myself for the flashable zip.
Note: If anyone has 1.4.1 installed and uses this, I need a tester to see if the old package manager will work or not (it should.)
Don't mirror my files because I only use goo-inside to track download stats.
Proof it works (Screenshots)
{
"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"
}
I've been looking for something like this for a long time, haha. Thank you soooo much. Question: how do you partition, and what exactly is the root part of said partition?
...it tells you to use something like gparted...
Indirect said:
...it tells you to use something like gparted...
Click to expand...
Click to collapse
And my next question is if i have stuff on my card, can i just delete all of it to make it work?
Just format it.
will film this first chance I get and post here.
Update: As promised
Indirect said:
Just format it.
Click to expand...
Click to collapse
Alrighty! Thanks so much!
If you don't have Linux installed, you can burn gparted to a live CD and then just use that to set flags and partition. No, I will not offer support. This is as simple as I can make it, be happy. Just burn gparted to a live CD, and add files to a USB so then you can still access the 2nd partition. This method isn't figured out in windows and that is a hell of a lot of work especially for an OS I don't use. Sorry guys. If someone knows a windows freeware solution, I can add it to the open.
Sent from my Nexus S 4G using xda premium
I haven't had any luck rooting from CWM. I have CWM loaded on SD card. I tried with Gapps_and_root.zip both on internal and external SD card. After message "Installing update" I get "E:Error in /emmc/Gapps_and_root.zip (Status 0) Installation aborted.
Any thoughts on the problem? Thanks.
Note: Tablet is running version 1.4.0
hmm...I'll take a look at that zip.
edit: OOPS! Lol, I was using an outdated update-binary. Fixed zip is being uploaded right now. ^)^
edit2: Uploaded the fix. Same link as before.
Sent from my Nexus S 4G using xda premium
Also if it matters (not sure how many version of CWM may be out there) I have v5.5.0.4 of CWM on the sdcard.
It didn't matter. It was a bad update-binary in the file. I fixed it, just redownload.
New file worked fine. Thanks.
Description:​This is a image, and flasher for windows designed to make it so that anyone can flash make a magic SD card to load up CWM, and root their device. THIS IS A UNIVERSAL ROOT, AND CAN BE DONE ON ANY FIRMWARE.
Why:
There are way to many rooting methods out there for this device, and with so many rooting methods, it is very hard to help trouble shoot a device, and make it so that rooting is available to everyone. Also with the 1.4.1 breaking normal root, it is very hard to teach people how to flash back to the previous 1.4.0, without stepping them through it, and then they have to beat the gun, and root and block OTA's. Also there is a lot of "geometry" involved in making a bootable SD.
What is it?:
There are two things in this package, the first is a flasher, and an image. These can be used to flash an SD card from windows with CWM, as a bootable SD. The second package is a CWM flashable zip that will add su, superuser, gapps, and the side loading package to your Nook.
What do I need?:
You will need:
SD Card >2GB (all information will be lost, so back it up)
Windows
Nook Tablet (any Firmware)
Credits:
Loglud
Indirect
Nemith
Bauwks
Instructions:​
Download the packages listed in the download folder, and extract them to your desktop.
extract ALL the files from the single zip.
NOTE: Do not extract the .zip with superuser and su.
Open the image flasher .exe, and browse for the .img that you extracted from the same zip
Put your SD Card into your nook or reader, and select the drive letter from the drop down on the right.
Press write, and wait
Once it has completed open the SD Card from the Windows browser and place the .zip in the root of the SD card.
Turn your Nook off.
Turn your Nook on while holding both the N+Power button. Your device will turn on, and then turn off after holding it.
NOTE: Do not let go of either button until your device has powered on and off again.
Put the SD Card into your nook.
NOTE: If it is already in there eject it and then put it back in.
Power your Nook on normally.
You will see a picture of N on the screen followed by a box with a white background followed by CWM booting up.
Select flash update.zip.
Select Select from SD card.
Select your .zip
Reboot device
NOTE: Remove the SD card after your device reboots as if you don't it will continue to boot from the SD card.
Downloads:
http://www.mediafire.com/?dwwhzaixwwh2015
Doesn't work here, but ...
Indirect said:
...
1. Setup SDCard
Using a new SDCard (not one you have info stored on) make a new MSDOS partition table and add a 50 MB FAT32 partition as the first primary partition. Then make sure you enable to boot and lda flags.
Any SDCARD larger than 50 MB should work but I used an extra 2GB laying around. You can add other partitions to the card if you want, but it is not necessary to allocate the entire card. Any added partitions would need to be manually mounted on your Nook anyway.
I used GParted on my Ubuntu machine to do this but any formating tool should work.
2. Copy Files onto SDCard
You can grab the files I used here:
http://www.mediafire.com/?dr6bqau194389te
Just UnZip the files directly to the root of the boot partition you created above (make sure flashing_boot.img, u-boot.bin, and boot.img are on the root not the folder SDCARD)
3. Insert SDCARD into NT
Now, with your NT powered off, eject the SDCARD you just created from your computer and insert it into the tablet. Then just turn it on and VOLA! You should now be in CWM!
Click to expand...
Click to collapse
Ever since I created the "v1.4.1 minimal root" procedure, I have been looking for a technique to "side-boot" the NT. A few days ago I saw "bauwks" method, but try as I might, I could not get that to work (using 1.4.1 u-boot.bin). So, when I saw yours this morning and saw that it uses the 1.4.0 u-boot.bin, I thought I'd give it a try. Didn't work. I even used "dd" to clear 5MB of the SDcard, reestablished the desired disk geometry (255 heads, 63 sectors/track), and created a LBA/bootable partition at the beginning of the SDcard, all with "fdisk" (via busybox). Still no SDcard boot.
Symptoms:
With the SDcard (from above) inserted and the NT powered on, the NT shows a black screen for about 3 minutes, and then boots the internal memory.
Removing MLO from the SDcard causes normal NT internal memory booting, so clearly the NT boot process is looking at the correct place on the SDcard (note that the MLO for 1.4.0 and 1.4.1 are identical).
I tried this with both 1.4.1 and 1.4.0 (reverted) installed on the internal memory.
Note that this is my 2nd NT (bought Dec 9th). The 1st one (bought Nov 15th) was able to side-boot using an SDcard created per pokey9000's instructions, but when I tried to recreate that card for the 2nd NT, it didn't work. Both NTs came with 1.4.0 installed, but only the 2nd NT was ever updated to 1.4.1.
So, unless I am doing something really stupid, there's something different between the two NTs I've owned. Note that "bauwks" had a problem booting from the SDcard, unless he had the USB cable connected, but others have not seen that symptom.
Note to Indirect: I don't expect you to fix this; I'm just posting it here as information.
disregard this post.
DeanGibson said:
Ever since I created the "v1.4.1 minimal root" procedure, I have been looking for a technique to "side-boot" the NT. A few days ago I saw "bauwks" method, but try as I might, I could not get that to work (using 1.4.1 u-boot.bin). So, when I saw yours this morning and saw that it uses the 1.4.0 u-boot.bin, I thought I'd give it a try. Didn't work. I even used "dd" to clear 5MB of the SDcard, reestablished the desired disk geometry (255 heads, 63 sectors/track), and created a LBA/bootable partition at the beginning of the SDcard, all with "fdisk" (via busybox). Still no SDcard boot.
Symptoms:
With the SDcard (from above) inserted and the NT powered on, the NT shows a black screen for about 3 minutes, and then boots the internal memory.
Removing MLO from the SDcard causes normal NT internal memory booting, so clearly the NT boot process is looking at the correct place on the SDcard (note that the MLO for 1.4.0 and 1.4.1 are identical).
I tried this with both 1.4.1 and 1.4.0 (reverted) installed on the internal memory.
Note that this is my 2nd NT (bought Dec 9th). The 1st one (bought Nov 15th) was able to side-boot using an SDcard created per pokey9000's instructions, but when I tried to recreate that card for the 2nd NT, it didn't work. Both NTs came with 1.4.0 installed, but only the 2nd NT was ever updated to 1.4.1.
So, unless I am doing something really stupid, there's something different between the two NTs I've owned. Note that "bauwks" had a problem booting from the SDcard, unless he had the USB cable connected, but others have not seen that symptom.
Note to Indirect: I don't expect you to fix this; I'm just posting it here as information.
Click to expand...
Click to collapse
Dean;
Try the post right above this, and dont change anything, just format using the flasher(will automatically write all of the partitions as they should be), and see if it works. (Though im about 90% sure it should)
uploading a new version of the Gapps and Root zip that include several things, such as homecatcher and adw (for the next important part):
including NT Hidden settings app which will actually allow you to sideload apps.
Indirect said:
Description:​This is a image, and flasher for windows designed to make it so that anyone can flash make a magic SD card to load up CWM, and root their device. THIS IS A UNIVERSAL ROOT, AND CAN BE DONE ON ANY FIRMWARE.
Click to expand...
Click to collapse
Indirect does it again, thank you a million times!
MAC INSTRUCTIONS:
1. Insert the SD card into your Mac
2. Open "Disk Utility" and click on the SD card on the right
3. Click "Info" and note the disk identifier (in my case disk3)
4. Unmount partitions of sd card by clicking unmount
5. open Terminal.app
6. Navigate to folder containing cwm_sd_flashing_boot.img (requires knowledge of basic unix commands)
7. Type "sudo dd if=cwm_sd_flashing_boot.img of=/dev/[disk indentifier] bs=1m" which in my case read "sudo dd if=cwm_sd_flashing_boot.img of=/dev/disk3 bs=1m"
8. Wait as this process takes a while to complete (sometimes 10 minutes to write 2GB). You can type ctrl-t to get a status update, the number before records out represents MBs transfered (should end at 2048)
9. Eject the SD card and follow the instructions in other posts

[How-to] S-Off ext SD Fix (With Screenshots)

Guys, noticed a few people having trouble with the sd card fix so I ran it and took screenshots. Each screenshot is what you should see after running the command listed above the screenshot. (I am not going to post screenshots of how to open the command prompt.. if you made it this far you should already know)
Disclaimer: This formats your SD Card.
This requires busybox. I utilized the busybox installer found at https://play.google.com/store/apps/...usybox&feature=nav_result#?t=W251bGwsMSwyLDNd
1. adb shell
{
"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"
}
2. busybox fdisk /dev/block/mmcblk1
3. type the letter "o"
4. type the letter "w"
5. busybox fdisk /dev/block/mmcblk1
6. Type the letter "n"
7. Type the letter "p" for primary
8. Type the number "1" for first partition
9. Press the enter key for default size.
10. Press the enter key for default size.
11. Type the letter "w"
12. busybox mkfs.vfat /dev/block/mmcblk1p1
Edit: Step 13.. On your phone, click on the Notification that states "Blank SD Card" and choose format, the card should then format and mount properly.
This is my first How-to so if something does not make sense please let me know. Hope this helps guys.
Nicely done. I'll add this to my FAQ thread. Great guide.
Sent from my Htc Rezound
Follow me on twitter @lmrtech
Somebody tipped me off to the "adb shell" and then proceed portion prior to this walkthrough, but I know others struggled with this issue as well. I'm sure they'll appreciate this info, thanks!
Im getting this after entering the letter "w"
fdisk: WARNING: rereading partition table failed, kernel still uses old table: D
evice or resource busy
nnnnr14 said:
Im getting this after entering the letter "w"
fdisk: WARNING: rereading partition table failed, kernel still uses old table: D
evice or resource busy
Click to expand...
Click to collapse
Hmm, never got that before. Do you have your device mounted as Charge only? Also may reboot the device see if that resolves it.. Last would be to run it through the terminal emulator on the phone (that is how I fixed mine the first time, its a pain but it worked).
When doing it through the terminal emulator on the phone though you do not need to use the adb shell command, just the busybox commands.
sindroidx said:
Hmm, never got that before. Do you have your device mounted as Charge only? Also may reboot the device see if that resolves it.. Last would be to run it through the terminal emulator on the phone (that is how I fixed mine the first time, its a pain but it worked).
When doing it through the terminal emulator on the phone though you do not need to use the adb shell command, just the busybox commands.
Click to expand...
Click to collapse
what radio are you using? like are you on the new leak or the old one..
nnnnr14 said:
what radio are you using? like are you on the new leak or the old one..
Click to expand...
Click to collapse
First time (when I ran it on my phone) I was on the ICS leak. When I took the screenshots for this post I had downgraded to the GB RUU so I could install the eng hboot.
I'll add this to my OP in the S-Off Instructions thread. Thanks a lot.
i i followed the instructions to the t but i never got the [email protected] prompt is sh-3.2#, i didnt have any errors or anything but it still is not recognized when i plug it into the computer, i also tried it from the emulator on the phone and i get the warning about the kernel still uses old table, device or resource busy, any thoughts?
hoebag said:
i i followed the instructions to the t but i never got the [email protected] prompt is sh-3.2#, i didnt have any errors or anything but it still is not recognized when i plug it into the computer, i also tried it from the emulator on the phone and i get the warning about the kernel still uses old table, device or resource busy, any thoughts?
Click to expand...
Click to collapse
Did you format the SD card at the end? Don't have a screenshot for that one since I had already got mine working but if no errors happened, you should be able to click on the notification that states "Blank SD Card" and choose format and it should format then mount.
Edit: Just modified OP for step 13.
yes i did, my phone said the sd was blank and i formatted it, it said checking sd card, then preparing sd card, but when i plug it into the computer if only shows the internal sd card as a few kilobytes and no ext sd comes up, on my rom i open the camera and it says insert and ad card to use the camera
edit: just tried running it again and on the last step i get cant open /dev/block/mmcblk1p1 no such file or directory
hoebag said:
yes i did, my phone said the sd was blank and i formatted it, it said checking sd card, then preparing sd card, but when i plug it into the computer if only shows the internal sd card as a few kilobytes and no ext sd comes up, on my rom i open the camera and it says insert and ad card to use the camera
edit: just tried running it again and on the last step i get cant open /dev/block/mmcblk1p1 no such file or directory
Click to expand...
Click to collapse
Strange, the last command is what makes the file system for mmcblk1p1.. does recovery or fastboot recognize the sd?
Sent from my ADR6425LVW using xda premium
im actually having the same problem right now.... im running the 2.01.605.11 firmware using scotts clean rom de 1.2 with the firmware patch. it wouldnt install anything onto the sd card so i rebooted to recovery unmounted sd card and remounted it. enabled usb-ms and made a back up of my sd card, rebooted and tried the fix and i get the same issues the other guy does....
sindroidx said:
Strange, the last command is what makes the file system for mmcblk1p1.. does recovery or fastboot recognize the sd?
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
it seems that recovery sees it, windows certainly does when i format it using windows, the phone just cant see it, and the rom im using isnt helping as the settings to storage are force closing so i cant get into them but the camera still says to insert and sd card, im going to try and format the card using my thunderbolt real quick and see if that helps, ill post back and let you know
---------- Post added at 03:28 AM ---------- Previous post was at 02:55 AM ----------
i have no idea what i really did to fix it but its working now, i put the card in my computer, formatted it with windows, copied all of my backed up files to the card and put it back in the phone, it still didnt read it but recovery did so i flashed newts onexxx rc2 rom and bam it read everything from the first boot, internal and external cards, must have been the rom
sindroidx said:
This is my first How-to so if something does not make sense please let me know. Hope this helps guys.
Click to expand...
Click to collapse
Dude. I dont know how to thank you enough for this post.
Thanks for the post but still a no go. Will try again tomorrow.. somehow going to try to flashy a rom and see if it works..
RDxxASSASSINxx said:
im actually having the same problem right now.... im running the 2.01.605.11 firmware using scotts clean rom de 1.2 with the firmware patch. it wouldnt install anything onto the sd card so i rebooted to recovery unmounted sd card and remounted it. enabled usb-ms and made a back up of my sd card, rebooted and tried the fix and i get the same issues the other guy does....
Click to expand...
Click to collapse
I would try a couple things if you haven't already gotten this resolved. If showing in recovery I would try to re-apply the firmware patch. If that does not work I would try a clean install of your ROM once more. Looks like the other issue was resolved by a different ROM, so it would be a suggestion (if the card shows in recovery) to try at least a clean install of the same ROM.
kkeller87 said:
Dude. I dont know how to thank you enough for this post.
Click to expand...
Click to collapse
Not a problem man, just trying to do what I can to help out the community.
Still no go
I have tried again tonight to give the sd card fix a try. Formatted sd card with windows and ran fix. After typing w the outcome was Fdisk: WARNING rereading partition table failed: Kernel still uses old table: device or resource busy
Hope that give an idea for an answer.. Thanks
FYI..my phone won't install busybox (Stericson) cause of sd card not mounted or not reading. Had to use jrummy's. I tried to force busy box to work through my rom with titanium but that didn't work.
My sd card works in ra recovery. When I go into root explorer sdcard2 is in read only. Is there a way to change that?
droidrev71 said:
I have tried again tonight to give the sd card fix a try. Formatted sd card with windows and ran fix. After typing w the outcome was Fdisk: WARNING rereading partition table failed: Kernel still uses old table: device or resource busy
Hope that give an idea for an answer.. Thanks
FYI..my phone won't install busybox (Stericson) cause of sd card not mounted or not reading. Had to use jrummy's. I tried to force busy box to work through my rom with titanium but that didn't work.
My sd card works in ra recovery. When I go into root explorer sdcard2 is in read only. Is there a way to change that?
Click to expand...
Click to collapse
Hmm shows in recovery but R/O in root explorer.. I would try a couple things. First, if it shows in recovery, what firmware are you? If your on the GB firmware I would try the patch released (you can find it in almost all ICS ROM posts). If that does not work I would next try to format the SD Card in recovery, (not sure if that will work but I have heard that formatting in Windows fixed some so its worth a try). Last I would try flashing a new ROM (not saying you have to stay on it but another fix I have heard is new ROM).
If none of those work, I would grab another SD Card and try running to fix to see if maybe there is an issue with the SD card.
sindroidx said:
Hmm shows in recovery but R/O in root explorer.. I would try a couple things. First, if it shows in recovery, what firmware are you? If your on the GB firmware I would try the patch released (you can find it in almost all ICS ROM posts). If that does not work I would next try to format the SD Card in recovery, (not sure if that will work but I have heard that formatting in Windows fixed some so its worth a try). Last I would try flashing a new ROM (not saying you have to stay on it but another fix I have heard is new ROM).
If none of those work, I would grab another SD Card and try running to fix to see if maybe there is an issue with the SD card.
Click to expand...
Click to collapse
i have success.. i'm guessing the main fix was flashing newts rc2. that was the original rom i was on when i did the s-off. i lost my data on sd after using the external sd card fix. so didn't have a back up. i had cleanrom 3.7 on laptop and that is what i flashed to try to fix the first time(different rom which i thought would fix). so glad to be normal again.. exept with data loss which i didn't have much.. thanks for you patience and help
i can't believe the fix was that simple..what a trip..lol

[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.

EE:Can't mount /sdcard when in Recovery v5.8.3.4 or boots into CM10 & hangs...

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.

Categories

Resources