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
Related
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.
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.
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.
I was able to get cm 10 on my nook with 10 touch Firmware I loved it worked awesome. The battery died I plugged it in then my wife used it I went crazy on low power then when she policed it back in I believe it weren't into Bootloop and erased everything. When I came back home it was dead. First I tried the cwm SD and could not mount anything, then repart img and got red x, then Adams Linux restore and got blank screen, tried the DD command and get permission denied after every code with CD sdcard #. I would love to try anything I can to get it going.thanks
i can't flash in anything in cwm. Every time I get error can't mount SD card. Is there anyone I can send it to or have remote to see what its doing. I have done everything in every post and still nothing. Please help have big move coming and my boy loves to use it on long drives. Moving family across country in a month.
gowboy84 said:
i can't flash in anything in cwm. Every time I get error can't mount SD card. Is there anyone I can send it to or have remote to see what its doing. I have done everything in every post and still nothing. Please help have big move coming and my boy loves to use it on long drives. Moving family across country in a month.
Click to expand...
Click to collapse
Have you tried running cm10 from the sd card?
hwong96 said:
Have you tried running cm10 from the sd card?
Click to expand...
Click to collapse
Yea I get to Cynoboot but black screen anywhere else I go except cwm and get same errors there as cwm Sdcard
I just did 12/31 cm10 acclaim hd img and it goes straight to blank screen. Thanks for the help
Did you extract the sd image from cm-10-20121231-NOOKTABLET-acclaim-HD-SDC-img.rar and write the image to the sdcard (e.g., with win32diskimager or DiskImage_1_6_WinAll), and not just copying the file over to the card?
digixmax said:
Did you extract the sd image from cm-10-20121231-NOOKTABLET-acclaim-HD-SDC-img.rar and write the image to the sdcard (e.g., with win32diskimager or DiskImage_1_6_WinAll), and not just copying the file over to the card?
Click to expand...
Click to collapse
I extracted img with win ear and write in with win 32 imager. The only thing I could do was USB mount in twrp. The crappy thing is I don't even know how it died I was gone. It worked awesome then when I got back home it was dead.
gowboy84 said:
I extracted img with win ear and write in with win 32 imager. The only thing I could do was USB mount in twrp. The crappy thing is I don't even know how it died I was gone. It worked awesome then when I got back home it was dead.
Click to expand...
Click to collapse
Are you using Sandisk class 4 or 6 SD cards? All other brands do not work reliably with cm10. Higher sequential read/write speed cards do not have the high RANDOM read/write speeds of the Sandisk class 4 or 6 card.
hwong96 said:
Are you using Sandisk class 4 or 6 SD cards? All other brands do not work reliably with cm10. Higher sequential read/write speed cards do not have the high RANDOM read/write speeds of the Sandisk class 4 or 6 card.
Click to expand...
Click to collapse
Yea a SanDisk c4 4GB. I think it is something about not mounting sdcard looks like every one else in these posts can At least do that.
I noticed in Cynoboot it said install zip by sideload? Will I be able to do this. I need time to get drivers installed but I was wondering if it was worth a shot. And if it works is there a reason I'm having trouble installing drivers for cynoboot cwm.
gowboy84 said:
I noticed in Cynoboot it said install zip by sideload? Will I be able to do this. I need time to get drivers installed but I was wondering if it was worth a shot. And if it works is there a reason I'm having trouble installing drivers for cynoboot cwm.
Click to expand...
Click to collapse
You may want to try again so****e's thread in development to unbrick. His last reply said to use adb shell without the # sign. You should see $ not # in terminal (no su). Maybe that is why it didn't work for you before.
Per So****e:
Nononono. I'm sorry, the # just shows that you are in remote-shell. /sdcard # is just the directory you are in. any of that "$" and symbols at the beginning are just wat you see in the shell. Sorry to confuse anyone, I will put a note in the guide. If it is giving you permission denied, try to use exit, so you are back in adb and then take out the sdcard and put it back in and make sure you mount the sdcard
hwong96 said:
You may want to try again so****e's thread in development to unbrick. His last reply said to use adb shell without the # sign. You should see $ not # in terminal (no su). Maybe that is why it didn't work for you before.
Per So****e:
Nononono. I'm sorry, the # just shows that you are in remote-shell. /sdcard # is just the directory you are in. any of that "$" and symbols at the beginning are just wat you see in the shell. Sorry to confuse anyone, I will put a note in the guide. If it is giving you permission denied, try to use exit, so you are back in adb and then take out the sdcard and put it back in and make sure you mount the sdcard
Click to expand...
Click to collapse
I am not able to get my device in Ubuntu terminal only windows CMD. But I will try again in Ubuntu. Thank you I will try when I get some time.
I had my device rooted about a year ago, came back from Afghanistan and it updated and unrooted. Attempted to redo it and looks like i bricked my nook.
Any1 willing to remote in and fix my nook...? i've read just about all the stuff on here and cant figure it out. Thanks to anyone who would be willing to spend a few min and help.
Try the repart.img burned to sd-card.
http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
fml
So i followed the instructions and get to the point where my **** is bricked... I get the "fail" part of that link listed, so i follow it to the help links below that, but it gets into ADB push and stuff like that... so i google for a hour or 2 on how to do it. Which leads me to my ADB drivers dont work correctly, so i try to fix them for about and hour... and im back to the point where i need some advanced help....
"If you get a Red “X” instead of the checkmark, see the error notice at the bottom of this page for some options."
http://forum.xda-developers.com/showthread.php?t=1513583
https://github.com/succulent/acclaim_recovery_sdcard
bump
Is there anyone willing to help me out with this? Let me know, ty guys
I'd suggest burning a CM10.x pre-made SDcard image (e.g., cm_acclaim_10.1_21APR2013_HD_SDC_IMG.7z from Succulent's repo http://iamafanof.wordpress.com/2013/02/18/cm10-1-jellybean-android-4-2-2-for-nook-tablet-0218/) and see if your NT can successfully boot and run a ROM from SDcard. If it does then you can proceed to restoring stock ROM (or flashing CM10) internally on emmc.
Also, refrain from reformatting any partition (other than possibly /cache, /system, /data, if you have good reason to do so and know what you're doing), as you risk making the problem worse -- see http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31.
digixmax said:
I'd suggest burning a CM10.x pre-made SDcard image (e.g., cm_acclaim_10.1_21APR2013_HD_SDC_IMG.7z from Succulent's repo http://iamafanof.wordpress.com/2013/02/18/cm10-1-jellybean-android-4-2-2-for-nook-tablet-0218/) and see if your NT can successfully boot and run a ROM from SDcard. If it does then you can proceed to restoring stock ROM (or flashing CM10) internally on emmc.
Also, refrain from reformatting any partition (other than possibly /cache, /system, /data, if you have good reason to do so and know what you're doing), as you risk making the problem worse -- see http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31.
Click to expand...
Click to collapse
Much thanks for the attempt. But after trying everything you siad (and following them to dozen of other stuff) still no fix.
Basically i need help to re-write my emmc partions it seems. Is this correct?
I can get it to boot to CWM from a SD card, but no further.
Additional info -
I cant get ADB to work at all, it boots into CWM (CWRM?) where i can apply update.zip and all that stuff, but ADB doesnt list my device (i tried on 2 different computers). Was thinking my drivers were messed up or something, but in device manager it lists my device as a E: and F: (emmc and SD card?) so i dont really know where to go from here.... fml
https://github.com/succulent/acclaim_recovery_sdcard/blob/CM7/README.md
Wasn't a help? Worked like a charm when I hosed my NT.
champ1919 said:
https://github.com/succulent/acclaim_recovery_sdcard/blob/CM7/README.md
Wasn't a help? Worked like a charm when I hosed my NT.
Click to expand...
Click to collapse
Follow the guide for setting up the SD card. Get to the last step:
wait until device boot into recovery.
This never happens, it shows me the "n" and reboots over and over.
dand40 said:
Follow the guide for setting up the SD card. Get to the last step:
wait until device boot into recovery.
This never happens, it shows me the "n" and reboots over and over.
Click to expand...
Click to collapse
Do you have another SD Card to try? I had the same problem getting mine to boot from SD after I updated it to 1.4.3 (ages ago), but trying a different SD Card fixed the issue.
Also, I think the post I have in my signature has instructions that are similar to that other link but might be a bit easier to follow. I wrote them so that a non-technical person should be able to follow them. Nothing against succulent, he does wonderful work.
make sure you take out sdcard before it reboots
i had same porblem. the fix
stillblaze01 said:
make sure you take out sdcard before it reboots
Click to expand...
Click to collapse
i noticed that these new sd boots for recovery don't really work. i had to use the cwm and sd boot stuff from the nook color and worked like a charm. BUT! u have to be very patient and vigilant because depending on the type of usb cord u are using (factory nook usb cable, or generic cable) i may take awhile to boot from sd.
step1- download (https://www.mediafire.com/folder/dd1cwv3uw0u18/NOOK TABLET) <<-----sdboot.zip and cwm.zip
step2-download minitool partition wizzy
step3-put sd card into computer
step4-using minitool, delete partition, create partition (make primary, and fat32), right click on sd card (usually F set flag to active and change partition ID type to 0x0c fat32lba and then click apply. (IN THAT ORDER)
step5-once parted copy from the sdboot attatchment provided to sd card, the recovery.img, MLO,flashing_boot, and u-boot. Also put the cwm emmc.zip provided as well into sdcard.
step6-put sd into nook, MAKE SURE NOOK OFF BEFORE U PUT IT IN OR U WILL HAVE TO DO IT ALL OVER AGAIN, then plug nook into computer via usb cord, be patient and wait for nook to boot, once it finally boots, U MUST BE VERY QUICK AND PRESS "N" THE SECOND CYANOBOOT POPS UP, GO TO SDC RECOVERY NOT INTERNAL RECOVERY. that will load up sd cwm, once it is up it will now let u install the cwm i provided. install it.
step7-once this is done unplug it from comp, turn off, and repeat steps 3-6 (BUT THIS TIME ADD THE CYANOGENMOD 10.+ YOU WANT TO USE IN THE SD CARD AS WELL ALONG WITH THE CORRECT GAPPS) once sd cyanoboot pops up choose internal recovery instead of sdc recovery. install cm10+, gapps, and the internal cwm emmc.zip i gave u as well for good measure.
step8- once done take out sd card and reboot regularly with/without usb doesnt matter. u should be good...........it seems like alot but its actually rly fast when u got the hang of it.
I HOPE THIS HELPS YOU. LMK if my link doesnt work. these sd files are the only ones i found that actually work for me. maybe they work for u
newbtrigger69 said:
step7-once this is done unplug it from comp, turn off, and repeat steps 3-6 (BUT THIS TIME ADD THE CYANOGENMOD 10.+ YOU WANT TO USE IN THE SD CARD AS WELL ALONG WITH THE CORRECT GAPPS) once sd cyanoboot pops up choose internal recovery instead of sdc recovery. install cm10+, gapps, and the internal cwm emmc.zip i gave u as well for good measure.
step8- once done take out sd card and reboot regularly with/without usb doesnt matter. u should be good...........it seems like alot but its actually rly fast when u got the hang of it.
I HOPE THIS HELPS YOU. LMK if my link doesnt work. these sd files are the only ones i found that actually work for me. maybe they work for u
Click to expand...
Click to collapse
Closer than anything i've tried! When i try to choose internal recovery the system just freezes and i cant get it to go any further! I was soooooooo happy then this crushed my dreams lol....
Thank you so much dude, any suggestions to finish this out?
edit:
Added information, after installing the flash emmc provided, it says everything was fine.
Then when i go back to the main CWM menu, i have a error saying:
E:Cant mount /cache/recovery/log
E:Cant Open /cache/recovery/log
E:Cant mount /cache/recovery/last_log
E:Cant Open /cache/recovery/last_log
Dunno if this means anything really, but figured more info is better. Thanks!
dand40 said:
Closer than anything i've tried! When i try to choose internal recovery the system just freezes and i cant get it to go any further! I was soooooooo happy then this crushed my dreams lol....
Thank you so much dude, any suggestions to finish this out?
edit:
Added information, after installing the flash emmc provided, it says everything was fine.
Then when i go back to the main CWM menu, i have a error saying:
E:Cant mount /cache/recovery/log
E:Cant Open /cache/recovery/log
E:Cant mount /cache/recovery/last_log
E:Cant Open /cache/recovery/last_log
Dunno if this means anything really, but figured more info is better. Thanks!
Click to expand...
Click to collapse
that info is crucial actually. and this is what happened.
whatever you did to you nook prior to all this messed up ur internal pertitions. meaning they are all different sizes and such than they should be. maybe u installed something that belonged to another device (not the sdboot that wouldnt do it) more like a wrong cm version or something or even a kernel. whatever the case ur partitions are funky. going to work now but when i get back ill take a look and see if i can find something. i ran into same problem with my nook color a few weeks ago and got it fixed hopefully nook tablet has pretty much the same thing. getting it booted up is good though.will try to give u something later today
newbtrigger69 said:
that info is crucial actually. and this is what happened.
whatever you did to you nook prior to all this messed up ur internal pertitions. meaning they are all different sizes and such than they should be. maybe u installed something that belonged to another device (not the sdboot that wouldnt do it) more like a wrong cm version or something or even a kernel. whatever the case ur partitions are funky. going to work now but when i get back ill take a look and see if i can find something. i ran into same problem with my nook color a few weeks ago and got it fixed hopefully nook tablet has pretty much the same thing. getting it booted up is good though.will try to give u something later today
Click to expand...
Click to collapse
So last night i tried to load from SDC, internal recovery and pretty much any option it would let me. I have no idea what that broke but now when i plug my cable in it will not boot to SD or EMMC.... Take the SD Card out and try to boot and it will goto the "n" screen after about 2 min... then just stay black (im assuming its actually still on)...F M L
i think i got a fix.
dand40 said:
So last night i tried to load from SDC, internal recovery and pretty much any option it would let me. I have no idea what that broke but now when i plug my cable in it will not boot to SD or EMMC.... Take the SD Card out and try to boot and it will goto the "n" screen after about 2 min... then just stay black (im assuming its actually still on)...F M L
Click to expand...
Click to collapse
https://github.com/succulent/acclaim_recovery_sdcard <<<<<-----------------------go here
scroll down to Other flashable Files (Did you messed up your Nook Tablet?) and follow these directions. if ur confused on any of them ASK FOR CLARIFICATION BEFORE U JUMP INTO SOMETHING. this will help u repartition areas 1-6 which is would i did for my nook color and it worked when i ran into this EXACT problem so maybe this will help u. also if ur sdcard stopped booting to cyanoboot where u press "n" to enter cwm recovery, maybe a new one like i listed from sratch, go through all the steps again and jus add the appropriate zip files from succulents recovery tutorial listed above
get back to me asap if u have ANY questions :fingers-crossed:
---->>>IF THIS WORKS ALL CREDIT GOES TO SUCCULENT FOR HIS RECOVERY PROCESS<<<----:highfive:
newbtrigger69 said:
https://github.com/succulent/acclaim_recovery_sdcard <<<<<-----------------------go here
scroll down to Other flashable Files (Did you messed up your Nook Tablet?) and follow these directions. if ur confused on any of them ASK FOR CLARIFICATION BEFORE U JUMP INTO SOMETHING. this will help u repartition areas 1-6 which is would i did for my nook color and it worked when i ran into this EXACT problem so maybe this will help u. also if ur sdcard stopped booting to cyanoboot where u press "n" to enter cwm recovery, maybe a new one like i listed from sratch, go through all the steps again and jus add the appropriate zip files from succulents recovery tutorial listed above
get back to me asap if u have ANY questions :fingers-crossed:
---->>>IF THIS WORKS ALL CREDIT GOES TO SUCCULENT FOR HIS RECOVERY PROCESS<<<----:highfive:
Click to expand...
Click to collapse
ALSO!, i believe it talks about just flashing cm7 based on this 1.4.2 stock flash. 80% sure u may need to update to 1.4.3 stock in order to proceed to flash cm10+ (WHICH IS WUT U WANT) cm7=garbage now that bexus-n kernel has been out and even without it the new cm 10.+ cyanogenmods are pretty sweet.
(if u get it working, word of caution is the 10.2cm stable+ later nightlies have some NT related internal storage problems as of today. so u might want to flash 10.2m1 if u so choose to go past cm7 gingebread) GOOD LUCK! i hope u solve this. because i know this thread would help alot of newbs when troubleshooting.