I'm currently using a 4GB MicroSDHC card in my Eris, and will soon be ordering a 16GB Class 10 MicroSDHC card.
How do I go about getting the recovery partition on the new card? Do I do it as if I were installing a recovery for the first time, as shown below:
III: Flashing a Custom Recovery
Flashing a custom recovery will make your life easier when flashing ROMs in the future.
1. Download this file: Recovery.zip
2. Extract file contents to your \tools\ directory of your Android SDK.
3. Open up a command prompt and go to your tools directory, and execute these commands:
* adb shell mount -o rw,remount /dev/block/mtdblock3 /system
* adb push recovery.img /sdcard
* adb push flash_image /system/bin
* adb shell chmod 755 /system/bin/flash_image
* adb shell flash_image recovery /sdcard/recovery.img
4. Success! You now have a recovery partition installed on your phone. You can access it by running "adb shell reboot recovery" or by powering off your phone, holding "Volume Up + Power On"
Click to expand...
Click to collapse
Courtesy: ivanmmj's Thread.
Thanks in advance
the recovery partition was actually flashed to your phone not the sdcard.
you can just copy your files from the 4gig to the 16gig
silverramsrt said:
the recovery partition was actually flashed to your phone not the sdcard.
you can just copy your files from the 4gig to the 16gig
Click to expand...
Click to collapse
Really? I learn something new every day
What's this 'ext partition' that's suppose to be on my memory card? I have the option to wipe it in recovery.. unless I'm mistaken, and I might be.
unless you specifically formatted the ext partition, you don't have one. it's just a standard recovery menu item.
ext is basically a linux file system, and if formatted this way you can run your apps from sdcard if your rom supports it.
silverramsrt said:
unless you specifically formatted the ext partition, you don't have one. it's just a standard recovery menu item.
ext is basically a linux file system, and if formatted this way you can run your apps from sdcard if your rom supports it.
Click to expand...
Click to collapse
I'm aware of what ext is, but thank you for the description anyway
I haven't specifically set that up, but I may when I get my new card should the need arise.
Do you happen to know the speed limitations of the MicroSDHC slot on the Eris? I've read of people using Class 4 with success, but not much about 6, let alone 10.. I wonder if the device even supports Class 10 speeds?
.mak
Do you happen to know the speed limitations of the MicroSDHC slot on the Eris? I've read of people using Class 4 with success, but not much about 6, let alone 10.. I wonder if the device even supports Class 10 speeds?
Click to expand...
Click to collapse
According to PDAdb.net, the Eris supports sdhc2.0, which according to the secure digital wiki maxes out at 200X, which is class 30.
.mak
What's this 'ext partition' that's suppose to be on my memory card?
Click to expand...
Click to collapse
I was just answering the question.
silverramsrt said:
According to PDAdb.net, the Eris supports sdhc2.0, which according to the secure digital wiki maxes out at 200X, which is class 30.
I was just answering the question.
Click to expand...
Click to collapse
Nice, thanks for the info
No worries on the question there, just pointing it out.
Related
This is one of those things that I've always assumed would work, but I don't think I've seen anyone actually confirm it or talk about it yet. Before doing any of this I did a clean wipe of everything, just to avoid confusion on my part.
Step 1) I DD'ed the entire filesystem to an 8GB microSD that I have.
Step 2) Mounted p1 from SD (which is a copy of P1 from internal)
Step 3a) Pulled ramdisk
Step 3b) Extracted ramdisk
Step 3c) Changed all mmcblk0 refs to mmcblk1 in init.rc
Step 3d) Recompiled ramdisk
Step 3e) Pushed ramdisk back to p1 on SD
Step 4) Shut down Nook, reboot, confirm via mount command that all mounted volumes are mmcblk1
As I said, this is nothing revolutionary, but I figured it could be good for testing, especially if anyone wants to take a shot at a potentially dangerous mod like recovery or installing a fresh /system. Also, if I ever seriously messed up my internal memory, I would hope to be able to somehow recover by booting via the SD and being able to DD to the internal memory that way.
Very interesting. Thanks for the effort. Might be worth saving the image in case someone actually DOES brick their nook.
I'm curious as to the specifics. Aren't there several filesystems on the device? What did you do to pull/extract/recompile the ramdisk?
APKs
Are you able to install apk files to the emulated rom/nand on SD card...
also are you able to mount an extra partion on the card....
Thanks
"I would hope to be able to somehow recover by booting via the SD and being able to DD to the internal memory that way"
That will be great if we can push those files back to NAND
FYI, Holding just power + Nook buttons for about 15-20 sec will bring up the factury reset screen.
nook'r said:
Are you able to install apk files to the emulated rom/nand on SD card...
Click to expand...
Click to collapse
I haven't yet, but I don't see why not. Nothing especially different about it as opposed to the internal filesystem.
nook'r said:
also are you able to mount an extra partion on the card....
Click to expand...
Click to collapse
Right now I left vold alone, so it rather stupidly mounts p1, which contains all the critical stuff. I don't see any reason why vold couldn't be made to point to another seperate partition. (which is what I did with some other trials when using the internal ramdisk to boot to /system on the SD - left p1 as a "sdcard" partition)
nook'r said:
"I would hope to be able to somehow recover by booting via the SD and being able to DD to the internal memory that way"
That will be great if we can push those files back to NAND
Click to expand...
Click to collapse
I've backed up my own partitions individually. I suppose if I zero'd empty space and gzipped I could probably find some way to write the entire partition table to somewhere.
Would this be useful to someone who would want to dual boot with Ubuntu or MeeGo?
Could this be used to "dual boot" the fully stock Nook in store and then from card when you want to be free?
Homer
Homer_S_xda said:
Could this be used to "dual boot" the fully stock Nook in store and then from card when you want to be free?
Homer
Click to expand...
Click to collapse
This can be used for whatever you want to use it for. I've been running this way for quite a while, and everything works just as it would if you're running from the internal. It's just like dual booting on your PC.
The first (that I saw) and best documentation for setting this up can be found at:
http://blog.fsck.com/
axe2 said:
This can be used for whatever you want to use it for. I've been running this way for quite a while, and everything works just as it would if you're running from the internal. It's just like dual booting on your PC.
The first (that I saw) and best documentation for setting this up can be found at:
http://blog.fsck.com/
Click to expand...
Click to collapse
This is intriguing.
I would love to run everything off a micro sd and then pop it out to put it back to stock.
Would a 1GB micro sd work ok for this?
Someone needs to come up with an automated way to do this. That would be awesome.
moovius said:
This is intriguing.
I would love to run everything off a micro sd and then pop it out to put it back to stock.
Would a 1GB micro sd work ok for this?
Someone needs to come up with an automated way to do this. That would be awesome.
Click to expand...
Click to collapse
1GB is going to be too small to hold the whole system, but 4GB should work.
It should be something that would be scriptable assuming that the required tools exist on the standard rom, but I don't know if the tools are on there.
You could probably get to 1 GB if you dumped all the recovery junk and made media and data tiny. I'm trying to think if there's anything earing up tons of space besides /system.
Of course, just because you can doesn't mean you should.
how about multiple partitions on a 16gb
clockworx said:
This is one of those things that I've always assumed would work, but I don't think I've seen anyone actually confirm it or talk about it yet. Before doing any of this I did a clean wipe of everything, just to avoid confusion on my part.
Step 1) I DD'ed the entire filesystem to an 8GB microSD that I have.
Step 2) Mounted p1 from SD (which is a copy of P1 from internal)
Step 3a) Pulled ramdisk
Step 3b) Extracted ramdisk
Step 3c) Changed all mmcblk0 refs to mmcblk1 in init.rc
Step 3d) Recompiled ramdisk
Step 3e) Pushed ramdisk back to p1 on SD
Step 4) Shut down Nook, reboot, confirm via mount command that all mounted volumes are mmcblk1
As I said, this is nothing revolutionary, but I figured it could be good for testing, especially if anyone wants to take a shot at a potentially dangerous mod like recovery or installing a fresh /system. Also, if I ever seriously messed up my internal memory, I would hope to be able to somehow recover by booting via the SD and being able to DD to the internal memory that way.
Click to expand...
Click to collapse
Think someone could put together a noob guide for this? I'd like to try running a rooted version of Nook Color from SDCARD (partitioned?) on my stock Nook Color.
If possible? Please & Thanks...
I'm opening a new thread as this is really the work of verygreen, racks11479, j4mm3r, stilger, and rookie1.... and I've hijacked their threads enough as I only did minor repackaging to put this together as a hopefully generic template image...
This is but an attempt to create a mostly generic SDcard template for installing all versions, as base for Froyo, CM7, or Honeycomb as an SDcard install...... Most of the features best lend themselves to CM7 as verygreen's Alternate (uAltImg/Ram) allows installing and upgrading all current variants of CM7... but with Recovery as CWR 3.0.1.0/Ext3/4 with verygreen's installer/upgrader as uAltImg/Ram it can handle all your CM7 variant install and upgrade/migrate to SDcard needs...
The generic 2GB expandable image is available from;
http://dev-host.org/aewwoavj437z/Nook-2GB-SDCard-CW3010-VGCM7InstallerAsALTinMultiBoot-v6.zip
I suspect/hope that this thread will fade fast from the first page but just hope it will be useful for folks when modeling and building generic SDcard bootable versions...
EDIT: For folks who just want to update just their existing SDcard boot partition and get this boot functionality
I removed the files you shouldn't change from an existing /boot dir and zipped up the rest and posted this zip in my dropbox
http://dl.dropbox.com/u/6922721/jtbnet-modified-bootfiles.zip
Just have your SDcard mounted as /boot on your PC and extract this zip to it to get the same boot options as my card...
The layout of the current .v6 template SDcard to allow it to fit on a 2GB minimum size card is;
Part. # Name FStype Alloc. size Free Space
1 /boot FAT32 149MB 120MB
2 /system EXT3 462MB 455MB
3 /data EXT3 964MB 948MB
4 /sdcard FAT32 39MB 38MB
This is a Generic 2GB expandable template SDcard image to use to create pretty much whatever bootable SDcard you want...
How it differs with earlier Generic SDcards is I reorganized the default, Recovery, and Alternate boot choices using j3mm4r's multi-boot bootloader.
I updated Recovery to the newest version CWR 3.0.1.0 modified to write to SDcard instead of Internal/eMMC memory partitions with the help of user stilger. This can be used for Backup and Restore of full cards... as well as installing of CW packages like Google Apps, and Custom CW Rom Install packages you can find for Froyo, Honeycomb Preview and Gingerbread in this forum...
I moved verygreen's CM7 Installer/updater to the Alternate boot choice... In verygreen's thread he uses this as the default Kernal and Ramdisk which gets overwritten by the package you install... thus the need for 2 cards or copying files around to reuse the original... with this as Alternate it doesn't get overwritten and thus is available next time you want to use it... like Install CM7 for the first time... then upgrade to the new Nitely the next day without need for finding and copying files or using 2 cards...
How verygreen's Installer/updater differs from CWR... With vg's installer you place the installable files on the /boot partition... this installer will install SDcard ready or agnostic installables AND will install eMMC designed version CM7 builds and do on the fly conversion to SDcard version during the install seemlessly...
CWR 3.0.1.0 for SDcard will expect the install zip or backup file to be on the 4th/sdcard partition and expects these to be agnostic installs as it doesn't do anything on the fly to make these run on SDcard... It they are built or modifed to run on SDcard thats fine and installing from this Recovery works as would be expected...
I extended the size of the boot partition to have ~120MB free to allow for installing larger images as the prior ~100MB space was too close to currently typical installable Custom Rom packages.
The 4th /sdcard partiiton is created Very small to fit on a 2GB SDcard and really needs to be expanded using Easeus Partition Manager on Windows or an equivalent program on your OS of choice to fit your size choice of SDcard...
I will offer some experience with SDcard here... I bought 10 different manufacturers, and Class/speed cards... I ran disk benchmarks for all and then used the ones that performed best for daily use... Sandisk brand is the most generally faster than the Class it's stamped... A Class 4 beats most brand's Class-6... I wanted the fastest... and settled on buying 8 cards as KingMax Class-10 SDcards, 4 4GB and 4 8GB, from buy.com... these aren't the cheapest cards by far, BUT in this case you DO get what you pay for...
So for daily use I'd reccommend the KingMax 8GB Class-10 cards as I've gotten better than 2000 Quadrant scores running these cards for Froyo, Honeycomb, and CM7 Gingerbread installs... this is as good or better performance than most scores I've seen from folks running the same installs on Internal/eMMC...
CM7 Install Example by User stilger
with comments added by jtbnet and xdabr:
----------------------------------
You *should* be able to do the following with the image provided in this thread on your 2gb card:
1. Download image from this thread (currently v6)
http://dl.dropbox.com/u/6922721/Nook-2GB-SDCard-CW3010-VGCM7InstallerAsALTinMultiBoot-v6.zip
2. Write this Image to your card (I use win32diskimager or dd in linux)
3. Use Easeus Partition Manager to extend the 30MB 4th FAT32 /sdcard partition to fit your current SDcard
4. Once the card is written, place the cm7 zip in the root of the boot filesystem.
(Should be a drive letter with boot in the name with files like uImage uRecImg etc on it)
http://mirror.teamdouche.net/?device=encore
5. Place the gapps zip of your choice in the same "boot" filesystem.
http://android.d3xt3r01.tk/cyanogen/gapps/gapps-gb-20110307-signed.zip
6. Place SDcard in your Nook.
7. Turn on Nook.
8. Hit N button when it says Press any key for menu.
9. Choose SD and Alternate as your boot option
10. Let it finish. It says it will reboot but usually hangs for me so I give it 10 seconds after the screen goes black and long press the power button until it starts up...
11. Boot into CM7
TIP: To have rooted stock eclair version nook use the same sdcard partition (#4) as you use when booting on an SDcard bootable you can make one simple edit to the stock eclair /system/etc/vold.conf...
There are 2 definition blocks in the file... the first is for mount of internal eMMC partition 8 as /media, while the second block is to mount the 1st sdcard partition as /sdcard... to change this so that the 4th partition on the SDcard gets mount to /sdcard just Add a line;
partition 4
in the second block with your favorite editor like Root Explorer, or via adb pull,edit,push of the vold.conf file... and reboot...
I.E.:
## vold configuration file for zoom2
# modified for encore
volume_sdcard {
## This is the direct uevent device path to the SD slot on the device
media_path /devices/platform/mmci-omap-hs.1/mmc_host/mmc0
partition 8
media_type mmc
##mount_point /sdcard
mount_point /media
ums_path /devices/platform/usb_mass_storage/lun0
}
volume_sdcard2 {
## Currently points to internal eMMC, assumes eMMC is formatted as FAT32
media_path /devices/platform/mmci-omap-hs.0/mmc_host/mmc1
partition 4
media_type mmc
##mount_point /media
mount_point /sdcard
ums_path /devices/platform/usb_mass_storage/lun1
}
Just to verify, this image has?
J4mm3r's multi-boot
CWM 3.0.1.0 but with correct mounts like racks11479's CWM 3.0.0.6 as uRecImg/Ram
verygreens installer as uAltImg/Ram
I had already done the same with racks CWM, but that's ext4 only I believe.
This will be great with CWM 3.0.1.0.
Thanks for putting this together
P.S. What is the CM7 vesion as uImage/uRamdisk?
Tried to burn the image on a 2Gb SDcard to look inside.
It's a 4GB image not 2GB.
bobshute said:
Tried to burn the image on a 2Gb SDcard to look inside.
It's a 4GB image not 2GB.
Click to expand...
Click to collapse
Sorry Bob... I uploaded the wrong image... Had a long day at work today so just getting to uploading a fresh image... this one IS 2 GB with larger/150MB /boot but a very small 4th /sdcard partition, and has formated system and data so won't boot to CM7 anymore but it's much cleaner...
Only thing this 2GB image only zips down to 800MB... strange as the wrong card I uploaded last night was a 4GB card I was testing with and with lots of data on system and data and it zipped down to 300MB... but this one is cleaner and does boot to CWR 3.0.1.0 as recovery and verygreen's CM7 install/updater as Alternate boot...
It's taking forever to upload so I may not be able to update the link in the original post till the morning as already well after midnight now...
bobshute said:
Just to verify, this image has?
J4mm3r's multi-boot
CWM 3.0.1.0 but with correct mounts like racks11479's CWM 3.0.0.6 as uRecImg/Ram
verygreens installer as uAltImg/Ram
I had already done the same with racks CWM, but that's ext4 only I believe.
This will be great with CWM 3.0.1.0.
Thanks for putting this together
P.S. What is the CM7 vesion as uImage/uRamdisk?
Click to expand...
Click to collapse
You are correct on what it has for uRecImg/Ram and uAltImg/Ram and yes Racks' 3.0.0.6 is Ext4 Only.... thus why I wanted to update to 3.0.1.0/Ext3 and Ext4...
That wrong 4GB upload from yestrday was the test card I had expanded and tested installing CM7 RC4 with UI tweaks to test VG's installer and then restored system and data from my normal card's backup to test CWR 3.0.1.0... so I mixed up the cards when I made the image and uploaded the expanded test 4GB version instead of the original blank 2GB version I started with...
Updated OP with cleaned up file...
Thanx to Verygreen's suggestion to zerofill the system and data partitions to allow for better compression I uploaded v4 where the zipped filesize is down to 420MB from prior zip of 770MB. OP link is updated...
I'm going to continue to see if I can find a way to make this significantly smaller while still containg all 4 mountable partitions and will upload any success story if/when it might occur...
I actually used the 2GB image itself booted to CWR and ran 'adb shell' to allow me to use the 'dd' command to zero fill the system and data partitions... THANX again to verygreen for that idea...
jtbnet said:
Thanx to Verygreen's suggestion to zerofill the system and data partitions to allow for better compression I uploaded v4 where the zipped filesize is down to 420MB from prior zip of 770MB. OP link is updated...
I'm going to continue to see if I can find a way to make this significantly smaller while still containg all 4 mountable partitions and will upload any success story if/when it might occur...
I actually used the 2GB image itself booted to CWR and ran 'adb shell' to allow me to use the 'dd' command to zero fill the system and data partitions... THANX again to verygreen for that idea...
Click to expand...
Click to collapse
jtbnet - I think zeroing the /data and /system file systems causes your script to fail. I put this image on an 8gb sd card today. I copied the latest Tablet Tweaks and gapps zip files to the boot partition rebooted into altboot.. It failed not being able to create files. Took the nook into recovery logged in via ADB and /system where full:
Before:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 250080 32 250048 0% /dev
/dev/block/mmcblk0p7 350021 52983 278967 16% /cache
/dev/block/mmcblk1p2 458925 458925 0 100% /system
/dev/block/mmcblk1p3 972436 972436 0 100% /data
Click to expand...
Click to collapse
Used recovery to format /data and /system.
After:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 250080 32 250048 0% /dev
/dev/block/mmcblk0p7 350021 52983 278967 16% /cache
/dev/block/mmcblk1p2 458925 8238 426992 2% /system
/dev/block/mmcblk1p3 972436 16424 906616 2% /data
Click to expand...
Click to collapse
Booted into alt boot after copying zip files to /boot again and everything installed fine.
stilger said:
jtbnet - I think zeroing the /data and /system file systems causes your script to fail. I put this image on an 8gb sd card today. I copied the latest Tablet Tweaks and gapps zip files to the boot partition rebooted into altboot.. It failed not being able to create files. Took the nook into recovery logged in via ADB and /system where full:
...
Used recovery to format /data and /system.
.
Booted into alt boot after copying zip files to /boot again and everything installed fine.
Click to expand...
Click to collapse
THANX
I had been just deleting the filler files in CWR (/system/zerofile and /data/zerofile) instead of formatting... BUT I think I have found the answer... I need to zerofill to cause the 2 partitions to compress reasonably... BUT if I create the files then sync,umount,re-mount then delete the files, sync, umount this frees space by freeing the inode but shouldn't actually touch the zerofill'd now freed space... so compression should be the same without the files...
I'll give this a try and upload v5 later hopefully...
EDIT: finally found time to upload v5... well mirror is still in process... /data and /system now empty and result is even a few bytes smaller...
Thank you jtbnet, but I am so confused.
Personally I'm mostly interested in SD card booting because I'd still like to leave the internal eMMC memory stock or near-stock.
But I get confused as to how the "size agnostic" approach ultimately writes to the card, whether it uses the NC or a PC as an intermediary to get the card written, how Clockwork Recovery comes into play if at all (I thought it was only used when you ARE futzing with the eMMC instead of cleanly booting off SD card), and more.
I would prefer a list of disk images I can write to an SD card with standard tools (I used "dd" on a Mac for brian's Nookie Froyo SD image), but it seems your mod here and the main size-agnostic installer are more complicated than that.
Is there a simple explanation you can give me (and other similar newbies)?
xdabr said:
Thank you jtbnet, but I am so confused.
Personally I'm mostly interested in SD card booting because I'd still like to leave the internal eMMC memory stock or near-stock.
But I get confused as to how the "size agnostic" approach ultimately writes to the card, whether it uses the NC or a PC as an intermediary to get the card written, how Clockwork Recovery comes into play if at all (I thought it was only used when you ARE futzing with the eMMC instead of cleanly booting off SD card), and more.
I would prefer a list of disk images I can write to an SD card with standard tools (I used "dd" on a Mac for brian's Nookie Froyo SD image), but it seems your mod here and the main size-agnostic installer are more complicated than that.
Is there a simple explanation you can give me (and other similar newbies)?
Click to expand...
Click to collapse
Check racks11479's thread for a good number of SDcard installable versions...
http://forum.xda-developers.com/showthread.php?t=998861
I do hope to find time to update the second post in this thread with some much better explanantion... but in short...
This is a Generic 2GB expandable template SDcard image to use to create pretty much whatever bootable SDcard you want...
How it differs with earlier Generic SDcards is I reorganized the default, Recovery, and Alternate boot choices using j3mm4r's multi-boot bootloader.
I updated Recovery to the newest version CWR 3.0.1.0 modified to write to SDcard instead of Internal/eMMC memory partitions with the help of user stilger. This can be used for Backup and Restore of full cards... as well as installing of CW packages like Google Apps, and Custom CW Rom Install packages you can find for Froyo, Honeycomb Preview and Gingerbread in this forum...
I moved verygreen's CM7 Installer/updater to the Alternate boot choice... In verygreen's thread he uses this as the default Kernal and Ramdisk which gets overwritten by the package you install... thus the need for 2 cards or copying files around to reuse the original... with this as Alternate it doesn't get overwritten and thus is available next time you want to use it... like Install CM7 for the first time... then upgrade to the new Nitely the next day without need for finding and copying files or using 2 cards...
How verygreen's Installer/updater differs from CWR... With vg's installer you place the installable files on the /boot partition... this installer will install SDcard ready or agnostic installables AND will install eMMC designed version CM7 builds and do on the fly conversion to SDcard version during the install seemlessly...
CWR 3.0.1.0 for SDcard will expect the install zip or backup file to be on the 4th/sdcard partition and expects these to be agnostic installs as it doesn't do anything on the fly to make these run on SDcard... It they are built or modifed to run on SDcard thats fine and installing from this Recovery works as would be expected...
I extended the size of the boot partition to have ~120MB free to allow for installing larger images as the prior ~100MB space was too close to currently typical installable Custom Rom packages.
The 4th /sdcard partiiton is created Very small to fit on a 2GB SDcard and really needs to be expanded using Easeus Partition Manager on Windows or an equivalent program on your OS of choice to fit your size choice of SDcard...
I will offer some experience with SDcard here... I bought 10 different manufacturers, and Class/speed cards... I ran disk benchmarks for all and then used the ones that performed best for daily use... Sandisk brand is the most generally faster than the Class it's stamped... A Class 4 beats most brand's Class-6... I wanted the fastest... and settled on buying 8 cards as KingMax Class-10 SDcards, 4 4GB and 4 8GB, from buy.com... these aren't the cheapest cards by far, BUT in this case you DO get what you pay for...
So for daily use I'd reccommend the KingMax 8GB Class-10 cards as I've gotten better than 2000 Quadrant scores running these cards for Froyo, Honeycomb, and CM7 Gingerbread installs... this is as good or better performance than most scores I've seen from folks running the same installs on Internal/eMMC...
Even 400M seems excessive for mostly zero filled card.
Basically your target compressed size should be the size of all real files on the card + a little bit.
Make sure you zero the extra fat partition and boot partition free space too as plenty of random data might be there.
verygreen said:
Even 400M seems excessive for mostly zero filled card.
Basically your target compressed size should be the size of all real files on the card + a little bit.
Make sure you zero the extra fat partition and boot partition free space too as plenty of random data might be there.
Click to expand...
Click to collapse
THANX...
I did think of that... after the fact... but the free space on those 2 partitions is <150MB which at the expected 4 to 1 compression I'm seeing would only save another ~35MB... so I didn't bother try and re-upload.... as less than 10% expected improvement... IF I need to upload another version I will include this in that version though...
I'd tend to agree with you on "your target compressed size should be the size of all real files on the card + a little bit." but the actual Used space is ~100MB, Total Space = 2GB, Unused space is thus around 1.9GB... so compression (1/5-1/4) really STINKS on this... but I'm not sure why as I've tried winzip and gzip with multiple levels of compression...
Thank you so much for the explanation, jtbnet, but it's hurting my noob brain!
It seems that most people like CM7 with Tablet Tweaks by mad-murdock. Could someone detail for me (step by step) the simplest way to get that in a bootable 2 GB SD card, preferably without involving a second card, and without touching the eMMC at all? I can't tell whether this project does that or not (and if so, how) or whether I should stick with racks11479's approach, or what. My apologies; I'm not usually this far behind.
Edit: I forgot that mad-murdock's Tablet Tweaks were already merged. So I guess just make that "CM7".
xdabr said:
Thank you so much for the explanation, jtbnet, but it's hurting my noob brain!
It seems that most people like CM7 with Tablet Tweaks by mad-murdock. Could someone detail for me (step by step) the simplest way to get that in a bootable 2 GB SD card, preferably without involving a second card, and without touching the eMMC at all? I can't tell whether this project does that or not (and if so, how) or whether I should stick with racks11479's approach, or what. My apologies; I'm not usually this far behind.
Edit: I forgot that mad-murdock's Tablet Tweaks were already merged. So I guess just make that "CM7".
Click to expand...
Click to collapse
You *should* be able to do the following with the image provided in this thread on your 2gb card:
1. Download image from this thread (currently v5)
2. Write this Image to your card (I use win32diskimager or dd in linux)
3. Once the card is written place the cm7 zip in the root of the boot filesystem. (Should be a drive letter with boot in the name with files like uImage uRecImg etc on it)
4. Place the gapps zip of your choice in the same "boot" filesystem.
5. Place sdcard in nook.
6. Turn on nook.
7. Hit N button when it says Press any key for menu.
8. Choose SD and Alternate as your boot option
9. Let it finish.
10. Boot into CM7
I did not provide you all the links but the CM7 nook image in mad murdocks Tablet Tweaks thread or the latest nightly for the nook (next nightly build should have Tablet Tweaks) should work. The gapps zip is also available at the CM site.
FYI - This image is based off the work of verygreen's thread: http://forum.xda-developers.com/showthread.php?t=1000957
Hopefully this will get you going.
Perfect recipe; thank you, stilger! Just what I (and likely lots of others) needed to know. I'll probably try this tonight.
I love this place.
stilger said:
You *should* be able to do the following with the image provided in this thread on your 2gb card:
1. Download image from this thread (currently v5)
2. Write this Image to your card (I use win32diskimager or dd in linux)
3. Once the card is written place the cm7 zip in the root of the boot filesystem. (Should be a drive letter with boot in the name with files like uImage uRecImg etc on it)
4. Place the gapps zip of your choice in the same "boot" filesystem.
5. Place sdcard in nook.
6. Turn on nook.
7. Hit N button when it says Press any key for menu.
8. Choose SD and Alternate as your boot option
9. Let it finish.
10. Boot into CM7
I did not provide you all the links but the CM7 nook image in mad murdocks Tablet Tweaks thread or the latest nightly for the nook (next nightly build should have Tablet Tweaks) should work. The gapps zip is also available at the CM site.
FYI - This image is based off the work of verygreen's thread: http://forum.xda-developers.com/showthread.php?t=1000957
Hopefully this will get you going.
Click to expand...
Click to collapse
THANX...
I'd add one step which is to use something like Easeus Partition Manager to extend the /sdcard partition to fill your larger than 2GB card between #2 and #3... as if only using the 2GB card image /sdcard is Only ~30MB big ... mostly just a Fat32 FS placeholder to allow extending...
jtbnet said:
THANX...
I'd add one step which is to use something like Easeus Partition Manager to extend the /sdcard partition to fill your larger than 2GB card between #2 and #3... as if only using the 2GB card image /sdcard is Only ~30MB big ... mostly just a Fat32 FS placeholder to allow extending...
Click to expand...
Click to collapse
You should take and add this step by step process to the first or second post.
Maybe even add links etc... Dunno. Up to you.
stilger said:
You should take and add this step by step process to the first or second post.
Maybe even add links etc... Dunno. Up to you.
Click to expand...
Click to collapse
THANX... Added your steps as an example in the Second post...
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.
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.
How do I go about converting my SD card from "Generic Hierarchical" File system to ExFAT?
trying to ROOT my phone for the 1st time.
I right click and it gives me an option to FORMAT,
but it does not give me any option as to what type of file system to format
to, no options for ExFAT or any other types of file system formats..
gymfreak81 said:
How do I go about converting my SD card from "Generic Hierarchical" File system to ExFAT?
trying to ROOT my phone for the 1st time.
I right click and it gives me an option to FORMAT,
but it does not give me any option as to what type of file system to format
to, no options for ExFAT or any other types of file system formats..
Click to expand...
Click to collapse
Assuming you are trying using your phone you will likely need a microSD-to-SD converted. I tried using a USB device and it just messed things up.
Oh, what size card? I think anything <64GB will format exFAT using the phone but since I have 64GB I'm not expert on that.
I assume PC if you're using right click. What OS?
In windows 7 it looks like this:
edit - oops apparently I'm too much of a noob to post a freaking picture on this freaking forum. Jesus.
And you can change the FAT32 to ExFat in the second drop-down.
Another option is to use minitool partition wizard (google it)
Another thought - are you trying to format this from your phone? If so you will need to get a card reader to format it from your pc, I do not think formatting the card using your phone as the "card reader" on your pc will work. (as stated in the post above me)
yes
Yes I was trying to format the SD card while it was plugged into my phone.
I am on WINDOWS 8
It is a 15 or 16 Gig SD card, the one that came with the phone.
Is that ok or do I need to get a new card with more GIGS?
Thanks for the fast replies!
denmalley said:
I assume PC if you're using right click. What OS?
In windows 7 it looks like this:
edit - oops apparently I'm too much of a noob to post a freaking picture on this freaking forum. Jesus.
And you can change the FAT32 to ExFat in the second drop-down.
Another option is to use minitool partition wizard (google it)
Another thought - are you trying to format this from your phone? If so you will need to get a card reader to format it from your pc, I do not think formatting the card using your phone as the "card reader" on your pc will work. (as stated in the post above me)
Click to expand...
Click to collapse
Oh no you'rre PLENTY good with 16 gigs. You really only need a very small amount of space to do this and then you can reformat the card in your phone and use it as extra storage if you'd like. But to do this exploit you'll need to get an external card reader to format the card on your pc. The only exception is if your card is 64gb, then you CAN apparently format to exfat in your phone. Go figure.
problem!
So i formatted the SD card..
I am using the latest Verizon samsung galaxy S4 the UAME7 one.. model # SCH-I545
I formatted the SD card, yet when i put it back in my phone and click properties.. it shows as a "GENERIC HEIRARCHICAL" file system
Is that right? It is not showing as ExFAT file system..
followed all these steps below..
when i get to typing the ./pwn , i get an error saying it cant find the file.. I hit ENTER or Return after i type each line correct?
1. Move all files and folders directly onto the root of your EXTERNAL microSD card only!
2. Download a Terminal Emulator app:
3. Open the Terminal Emulator app and run below 3 commands:
cd /mnt/extSdCard
./pwn
./script.sh
gymfreak81 said:
So i formatted the SD card..
I am using the latest Verizon samsung galaxy S4 the UAME7 one.. model # SCH-I545
I formatted the SD card, yet when i put it back in my phone and click properties.. it shows as a "GENERIC HEIRARCHICAL" file system
Is that right? It is not showing as ExFAT file system..
followed all these steps below..
when i get to typing the ./pwn , i get an error saying it cant find the file.. I hit ENTER or Return after i type each line correct?
1. Move all files and folders directly onto the root of your EXTERNAL microSD card only!
2. Download a Terminal Emulator app:
3. Open the Terminal Emulator app and run below 3 commands:
cd /mnt/extSdCard
./pwn
./script.sh
Click to expand...
Click to collapse
what steps did you take to format? (Used a card reader, right clicked in windows, select "format," change the filesystem type to from fat32 to exfat, etc)
and when you unzipped the zip file (root exploit package) in the link you found:
pwn
script.sh
readme
a folder called gs4ex
and moved all of these things to the root of your sd card?
when you type the first command in the terminal emulator and press enter what is the response you get back?
yea
I figured it out.. when i formatted it i had the QUICK FORMAT box checked.. i unchecked that, Formatted it again.. and finally got it to work!
So i got my phone rooted..
next step.. how do i backup the phone or ROM? Want to back it up before i install xprivacy or xposed.
Tried to do it holding the volume/home/power button, it shows me a recovery menu but no option to BACKUP the phone.
My goal here is to Permanently Disable the E911 GPS services.. for "911 calls/emergency only" which we all know is BS.. I would like to DIsable the E911 GPS but Would still like to be able to use my phone for GPS/DIrections. and disable any other apps from knowing my location etc.
I also want to disable any record keeping of phone calls or texts , is that even possible??
pretty much want to be untraceable, anonymous all around..
Any info on how to do so would be greatly appreciated.
From what my buddy told me i could install a custom ROM to turn off the Code for E911 GPS ?
or is there any other way to do so?
also formatted my SD card over all my PHOTOS, forgot to remove them first.... any way i can recover these? Or are they gone for good?
denmalley said:
what steps did you take to format? (Used a card reader, right clicked in windows, select "format," change the filesystem type to from fat32 to exfat, etc)
and when you unzipped the zip file (root exploit package) in the link you found:
pwn
script.sh
readme
a folder called gs4ex
and moved all of these things to the root of your sd card?
when you type the first command in the terminal emulator and press enter what is the response you get back?
Click to expand...
Click to collapse
ME7 currently has a locked bootloader and no exploit in sight. Still plenty you can do with root, and there appears to be workaround almost ready.
Check my response in this thread for all the relevant posts on the topic:
http://forum.xda-developers.com/showthread.php?t=2447640
E911
How do i DISABLE The E911 GPS feature?
I want to disable it, not just remove the ICON.. i want the E911 gps OFF
Why am i seeing things about people who want to just remove the E911 ICON?
That does not disable the actual E911 GPS does it?
gymfreak81 said:
...the one that came with the phone....
Click to expand...
Click to collapse
Woah...since when did it come with an SD card? Mine did not, and I just double checked the website and it still says sold separately for micro SD cards.