Related
I am on rooted 1.1 v2 and everything works great. The only thing missing is the in store reading free books for an hour a day. I was wondering if I could boot stock BN image on sd card when I am in the BN store, so I could get the in store feature?
I have been reading a lot and many people with 1.1 v2 cannot get access to the free one hour reading. I am a newbie, so alot of android dev forum is a little over my head.
If anyone knows of another way to get in store reading, I would appreciate the help.
Not a bad question. In theory i bet its possible. Id love to have an sd for stock use....
Sent from my Nook Color (zoom2) using Tapatalk
I just want it for in store reading.
Why no one has thought of this before I have no idea, but its a Great Idea, Count me in if they can come up with this, maybe some high and mighty dev will come by and hear our pleas.
It would be great to have the Free Reading and to get books on free book Friday, Also i think they have in-store coupons.
therealguppy said:
Why no one has thought of this before I have no idea, but its a Great Idea, Count me in if they can come up with this, maybe some high and mighty dev will come by and hear our pleas.
It would be great to have the Free Reading and to get books on free book Friday, Also i think they have in-store coupons.
Click to expand...
Click to collapse
I believe it was tried previously, but there's things in the stock ROM that have hard coded reference points to parts of the system (if memory serves). The person trying to do this early on gave up for that reason. I could be wrong, but I think this was in mid December.
I was getting ready to ask this question when I found your thread. I really hope something like this does pop up in the Dev section - I'll use my nook daily with a custom froyo rom, but it would be nice to be able to use the stock image off a SD when I stop into a B&N.
Well, in theory it's quite easy to do. Read the entire post before attempting the trick.
As usual, I'm not responsible if your NC starts speaking Flemish. Be careful with your Internal partitions!
Requirements: stock on internal, gparted, maybe my UMS utility (DEV), an SDCard (8GB at least, to be safe), a few minutes.
Partition an SDcard following stock layout.
You can partition the SD by using gparted. Create a new partition table, then create the partitions. Then apply. Don't forget to use "round to cylinder" and always leave a 1mb space at the beginning of each partition (except boot). Or else, you'll end up with corrupt partitions, writing over one another. Partition size can be changed, just make sure they're big enough..
Make sure the first partition has the bootable/boot flag.
To print the layout, use ADB command "fdisk /dev/block/mmcblk0 -l".
Or search for the layout in dev forum.
Layout looks like this (by heart, so check):
(Primary: )
p1: boot = FAT32 ~70 MB
p2: rom = FAT32 ~70 MB
p3: factory = ext2 ~??MB (this can left at 1mb, its a recovery partition, no use here)
p4: extended (not a partition strictly speaking, it's an extension)
(Logical: )
p5: system = ext2 ~470MB
p6: data = ext3 ~900MB (this can be bigger, app data storage)
p7: cache = ext3 ~350MB
p8: media = media FAT32 ~5GB (this can use all the remaining space, as big as you can/wish: media storage, books, films)
Then, you'll need to copy partition contents onto the SDCard's newly created partitions.
The easyiest way of doing it is by making .tar files of internal partition contents and extracting the files onto the SD partitions.
To create the tar files:
- either use <tar XXX.tar *> adb command on each partition, make sure you compress the actual content, not the container folder (i.e tar system content and not system, the * in the command stands for all content). Then pull the tar file. Delete it afterwards from internal!
- OR, probably more user friendly, use my USB mass storage utility found in DEV, mount each partition and create tar files with your usual UI (Ubuntu, Windows, OSX).
Copy every tar file onto your PC.
Tar files of internal partitions aren't all mandatory, all depends on if you want to make a complete backup of running stock rom, or if you just want the general stock rom on an SD. For instance, cache and media can be ignored, if you just want a general version. If you want to backup your media, tar media as well.
Then, extract each file onto the corresponding partition of you partitioned SD. Delete .tars afterwards from SD partitions.
THEN: download attached file, erase uRamdisk from you SD's boot partition and replace it with the one in the attached zip file (rename SD-STOCK-uRamdisk to uRamdisk). Without this step, your SD will boot from system and data internal partitions.
This uRamdisk has adb activated, so you should be able to push files to the SD once booted. Some internal commands won't work though (i.e, mount). You'll have to install busybox and root (su) the system, well if that's your goal that is.
Then insert the SD and boot.
In theory, this should boot up to stock from SD.
I could be missing something, it's late here, and I haven't tried any of this.
Beware: recovery, even from SD, will affect the internal partitions! Maybe it's best you delete uRecRam and uRecImg from your SD's boot (NOT INTERNAL!).
NB: you need to edit vold.conf. See second page of this thread.
Note: you could also use 'dd' command instead of making tars, but you'd end up with huge .img files.
PS: If you have no way of accessing your SD partitions once they're created, use the following command from ADB while booted from working internal system, with SD inserted in NC:
echo /dev/block/mmcblk1 > /sys/devices/platform/usb_mass_storage/lun0/file
Click to expand...
Click to collapse
This last command should open every SD partition in you PC's explorer.
Sam
I don't see the point in asking a question if you're not interested in the answer...
Sent from my HTC Desire using XDA App
samuelhalff said:
I don't see the point in asking a question if you're not interested in the answer...
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
I for one appreciate it, but missed that reply. I'm going to need to stockpile some microSD cards for all these various things to try .
I tried these instructions and it boots to the initial setup screen. I can see broadcasting AP's, but unfortunately I can't get it to connect any WiFi hotspot.
It appears to associate, sits at obtaining IP, but eventually gives up.
ADB connects and I was able to look at dmesg, but nothing stands out.
I went back to the eMMC and registered, exported /data, imported it to the SD card, and was able to bypass registration. However, it still doesn't connect to WiFi.
Only point that is probably worth noting is that I used a 2GB SDCard and here's what my mount output looks like:
mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mmcblk1p2 /rom vfat rw,sync,noatime,nodiratime,uid=1000,gid=1000,fmask=0117,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,errors=remount-ro 0 0
/dev/block/mmcblk1p5 /system ext2 ro,errors=continue 0 0
/dev/block/mmcblk1p6 /data ext3 rw,nosuid,nodev,noatime,nodiratime,errors=continue,data=ordered 0 0
/dev/block//vold/179:17 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,
shortname=mixed,utf8,errors=remount-ro 0 0
Click to expand...
Click to collapse
Any ideas?
Success
I could follow the instruction and made a 8gb stock bootable micro sd card. Only problem I can see is it mounts the boot partition of sd card as "/sdcard" and creates few folders like "B&N Downloads", "My Files". Is there any way to disable the sd card mount.
If anyone is interested in getting a copy of the sd card I can upload.
pbcal said:
I could follow the instruction and made a 8gb stock bootable micro sd card. Only problem I can see is it mounts the boot partition of sd card as "/sdcard" and creates few folders like "B&N Downloads", "My Files". Is there any way to disable the sd card mount.
If anyone is interested in getting a copy of the sd card I can upload.
Click to expand...
Click to collapse
I'm interested in it, or at least a "dummies guide" to doing this via a Windows PC..
I mean, as I read samuelhalff's post, it looks like it should be relatively easy to follow, but I have a few questions...
I see things like creating the partitions on the SD using gparted (which appears to be a linux command) so I don't know if I can maybe use EASEUS in Windows do do it? And am I reading it correctly, that TAR is a command I can run from inside an ADB SHELL? (i.e. type ADB Shell, then TAR)
I'll upload it tonight and post the link.
pbcal said:
I'll upload it tonight and post the link.
Click to expand...
Click to collapse
only reason that might not be a good idea is copyrights... not sure what if any might make it against the rules here, or something B&N would frown upon... then again, I guess its no worse than the .ZIP image in the recovery threads?
In any case, Thank you!!! I do appreciate it!
pbcal said:
I could follow the instruction and made a 8gb stock bootable micro sd card. Only problem I can see is it mounts the boot partition of sd card as "/sdcard" and creates few folders like "B&N Downloads", "My Files". Is there any way to disable the sd card mount.
If anyone is interested in getting a copy of the sd card I can upload.
Click to expand...
Click to collapse
I eagerly await this...and thank you for the work. I would use this as a dual-boot SD card with my daily-use ROM installed to internal memory. There are fairly easy-to-follow directions here on xda that will allow us to dual boot your SD card and internal memory. If you choose to boot from internal memory, then the SD card just becomes your external storage. No SD card swapping needed to go between your daily OS and the B&N stock. Very cool.
Thanks again.
You're welcome..
Sent from my Desire HD using XDA App
I'd love to get this as well. I had a 1.1 rooted stock which didn't give me the free hour in the store laast weekend. Sort of bummed as I heard it worked for some people.
Dan
Sent from my NookColor using Tapatalk
As I mentioned above, this would be great for dual-booting from eemc and sd card. I messed around with this a bit this evening and got it working nicely with one of the old Honeycomb images. The instructions for setting up dual boot are here:
http://forum.xda-developers.com/showthread.php?t=947698&highlight=dual+boot
I did have to mess around with the SD card a bit as once you boot from the internal memory, it is the first partition of the SD card that is used as your SD storage. Most SD card images have this as a very small boot partition with the fourth partition the larger SD card partition. I used a free program called Parted Magic to move the second, third, and fourth partitions over and expand the first partition into the unused space, creating a 5GB boot partition. I then put the multi-boot files from the thread above into the large boot partition. Worked like a charm - when booting from the SD card, Honeycomb used the fourth partition as the SD card storage space. When booting from internal memory, CM7 (the ROM I have installed to internal memory) used the 5GB boot partition as the SD card storage space.
Eageraly awaiting someone to build this and post an image file. I will admit that I am not smart enough to carry out the lengthly and excellence directions posted by samuelhalff.
Here is the link for the image. You will need a 8 GB or higher SD card.
Sorry for the large file. It has all partitions with stock data except data, cache and media.
Post your results / issues.
[COLOR="Red"][B]Removed[/B][/COLOR]
Click to expand...
Click to collapse
To avoid having /sdcard mounted on boot, you need to edit /system/vold.conf :
Code:
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
media_type mmc
##mount_point /media
mount_point /sdcard
ums_path /devices/platform/usb_mass_storage/lun1
}
Add "partition 8" in the sdcard section.
Explanation: see, media is set to partition 8 of internal. That's right. But here, sdcard will mount automatically the first sdcard partition (boot), as partition isn't set. You need to manually set it mount partition 8 (sdcard)..
Sam
Ok guys, so this is my problem.
As you all know the RAZRi has 8gb of built in storage, but as I am aware, there is a 5gb virtual sd card which you have access to, for installing apps etc. The rest is for os. Now when you insert an sd card it counts as a 2nd sd card.
So you get 5gb of data fofjr apps, but as i think the phone thinks its on an sd card already, you cant move apps to your external sd card.
So when you have a few large games like max payne, that 5gb disappears real quick.
I have tried manually moving data for apps to my sd card but it did not work and the apps would not load.
What are your suggestions?
On my old motorola defy you could just install apps to either the internal storage or the sd card, nice and simple.
Can you disable this feature or is there a way to install large apps to external media.
Thanks in advance!!!!
Yes I found it rather odd too. Also the SD mount point has got a very funny path. It is /mnt/external1
I am afraid that I must disappoint you here. According to person called "Badger1313" most of root exploits are through the App file transfer software. Due to the fact Motorola decided to secure this vulnerability by disabling 'Move to SD'.
Uncle Google came unhelpful this time giving me no answers to this question. The only valid way to make it possible is to have your phone rooted. Lets hope JB will bring some changes.
zmesler said:
Yes I found it rather odd too. Also the SD mount point has got a very funny path. It is /mnt/external1
I am afraid that I must disappoint you here. According to person called "Badger1313" most of root exploits are through the App file transfer software. Due to the fact Motorola decided to secure this vulnerability by disabling 'Move to SD'.
Uncle Google came unhelpful this time giving me no answers to this question. The only valid way to make it possible is to have your phone rooted. Lets hope JB will bring some changes.
Click to expand...
Click to collapse
Razr I is "rootable" so how to mount sdcard to /sdcard ?
Maybe some stuff to edit in init.d !?
Maybe something like this:
http://www.theandroidsoul.com/use-external-sd-card-as-internal-memory-on-droid-razr/
Le_Poilu said:
Maybe something like this:
http://www.theandroidsoul.com/use-external-sd-card-as-internal-memory-on-droid-razr/
Click to expand...
Click to collapse
For sure, but at the moment this is still not possible to flash anything from the recovery.
Would a manual editing of the vold.fstab file to set the following line work ?
Code:
dev_mount sdcard /mnt/sdcard auto /devices/platform/mmci-omap-hs.0/mmc_host/mmc0
(still did not buy this awesome phone)
Or maybe using Directory Bind, don't know but I use it to mount my SD Card on diferent points for my SGS2.
JackyJack said:
For sure, but at the moment this is still not possible to flash anything from the recovery.
Would a manual editing of the vold.fstab file to set the following line work ?
Code:
dev_mount sdcard /mnt/sdcard auto /devices/platform/mmci-omap-hs.0/mmc_host/mmc0
(still did not buy this awesome phone)
Click to expand...
Click to collapse
I did try a manual edit of vold.stab, unsuccessfull
Each time I still have the intern memory accessible and extern1 still here but empty.
Here is the vold.fstab file of the Razr i, if you have an idea what to change.
Code:
# Copyright (C) 2009 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
## Vold 2.0 fstab for the Morrestown Platform
#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
######################
# Mounts the first usable partition of the specified device
dev_mount sdcard-ext /mnt/external1 auto /devices/pci0000:00/0000:00:04.0/mmc_host/mmc1 /devices/pci0000:00/0000:00:02.3/gadget/lun0
Le_Poilu said:
I did try a manual edit of vold.stab, unsuccessfull
Each time I still have the intern memory accessible and extern1 still here but empty.
Here is the vold.fstab file of the Razr i, if you have an idea what to change.
Code:
# Copyright (C) 2009 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
## Vold 2.0 fstab for the Morrestown Platform
#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
######################
# Mounts the first usable partition of the specified device
dev_mount sdcard-ext /mnt/external1 auto /devices/pci0000:00/0000:00:04.0/mmc_host/mmc1 /devices/pci0000:00/0000:00:02.3/gadget/lun0
Click to expand...
Click to collapse
Well, actually the vold.fstab file on the Razr i only handle the scard-ext partition (wich I don't know what it's used for, but for sure this not /sdcard either /external1).
I guess there is some init script somewhere or config file regarding sdcard and external1 mappings.
BUT, as /sdcard is mounted from internal memory, if you replace it with your µSD, then you'll lost the space used by the /mnt/sdcard partition, unless you mount it elsewhere...
I may be wrong there...
BUT, as /sdcard is mounted from internal memory, if you replace it with your µSD, then you'll lost the space used by the /mnt/sdcard partition, unless you mount it elsewhere...
I may be wrong there...
Click to expand...
Click to collapse
I think you right about this.
This is what appends for Droid Razr user when they use this:
http://www.theandroidsoul.com/use-external-sd-card-as-internal-memory-on-droid-razr/
External SD take the place of internal SD.
For me it's a very little problem. I can lost 5GB if I win 32GB on the other side (or even more as the Razr i can handle 64GB SDXC card.)
But maybe can we have both. My first android phone was the first Samsung Galaxy i7500 which had 8BG of internal SD storage and a SDHC extension slot. Both internal and external was fully usable as SDCard
Maybe with a custom ROM in the futur.
Yeah, maybe we should focus first on tweaking the recovery so we can flash custom roms, this partition stuff looks like deep modding...
I am looking for some documentation about our partition tables, don't really know where to find what size are /boot, /system and all other partition that may exists...
Im using JB..and still it doesnt work
I use directory bind and it works great i have 20gb of game data
Hello,
I think it would be interesting in the next buid of CM10 implement FUSE.
For those not familiar with FUSE, this makes the EMMC (Internal) and DATA partitions are one.
FUSE is the standard in new android devices like the Galaxy S3.
With this gain in space, since both would have 6.7 GB of user data (photos for example) and for applications.
This would require using a repartitioning and as it should be, we could give more space to the partition and Partition System Cache.
I made a build with FUSE on, and doing great. It should be a standard in CM10 for P990.
A greeting and I apologize for the translation.
no thanks, i really like having my system and sd card separated...
60nine said:
no thanks, i really like having my system and sd card separated...
Click to expand...
Click to collapse
Sorry, SDCARD is the defaul name for internal.
FUSE = (Internal EMMC + DATA)
Without FUSE:
Partition 8 = DATA [1,5GB]
Partition 9 = EMMC [5,3 GB]
With FUSE only have:
Partition 8 = USERDATA [6,8 GB]
The user can see 6,8 GB in Internal SD
Sounds good but will it work,
If you want the CM team to pick it up you will have to talk with them directly.
Good luck
Sent from my LG-P990 using xda app-developers app
Tamps said:
Sounds good but will it work,
If you want the CM team to pick it up you will have to talk with them directly.
Good luck
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
Only change two files, and they here in the p990 repo.
Other solution is clone a p990, change two files and create a p990-fuse repo.
why would i fuse those two partitions? they are fine like they are now.
if i want to format the internal storage without affecting apps data i can while i'm using the actual partitions set, i cannot with the new mixed one.
this fuse leads what advantages?
pidocchio said:
why would i fuse those two partitions? they are fine like they are now.
if i want to format the internal storage without affecting apps data i can while i'm using the actual partitions set, i cannot with the new mixed one.
this fuse leads what advantages?
Click to expand...
Click to collapse
- You can format only DATA, and can format only EMMC too with FUSE with CWM.
- When you use a file manager, you see the same that without FUSE but you have 6,7GB.
- You can install 6,7 GB of APP.
- FUSE is ANDROID standard. All new Android devices use FUSE.
sounds great. make a flashable zip, we'll start using it
Sure
I'd give it a try i have a device i can use for testing
Ok,
I'll upload a zip with NVFlash and partitions.
Anyone can upload misc and lgdrm partitions?
Open Terminal
su
dd if=/dev/block/mmcblk0p3 of=/storage/sdcard0/misc.img
dd if=/dev/block/mmcblk0p6 of=/storage/sdcard0/lgdrm.img
After doing this, in the internal memory of the device, there should be two new files: lgdrm.img and misc.img.
Screenshot:
http://imageshack.us/photo/my-images/90/screenshot2012110410465.png/
http://imageshack.us/photo/my-images/12/screenshot2012110410462.png/
ProgMaq said:
Ok,
I'll upload a zip with NVFlash and partitions.
Anyone can upload misc and lgdrm partitions?
Open Terminal
su
dd if=/dev/block/mmcblk0p3 of=/storage/sdcard0/misc.img
dd if=/dev/block/mmcblk0p6 of=/storage/sdcard0/lgdrm.img
After doing this, in the internal memory of the device, there should be two new files: lgdrm.img and misc.img.
Screenshot:
http://imageshack.us/photo/my-images/90/screenshot2012110410465.png/
http://imageshack.us/photo/my-images/12/screenshot2012110410462.png/
Click to expand...
Click to collapse
misc.img: http://www.mediafire.com/?ik7gq8ddxxx0ujz
lgdrm.img: http://www.mediafire.com/?mf6oe0mio7xh9g9
I hope they are useful
Very thanks Chuck Bartowski
But your lgdrm.img is empty when mount.
This occurs when you have used nVFlash, not a problem, but I would like the original partition lgdrm compare with mine.
Anyone can upload original misc and lgdrm.
Thanks.
What about usb storage(internal storage) mounting after FUSING ?
Will it work as before ?
Sent from my Galaxy Nexus using xda premium
ProgMaq said:
Very thanks Chuck Bartowski
But your lgdrm.img is empty when mount.
This occurs when you have used nVFlash, not a problem, but I would like the original partition lgdrm compare with mine.
Anyone can upload original misc and lgdrm.
Thanks.
Click to expand...
Click to collapse
Ok, sorry, I didn't know.
I have reflash 10b with NVflash ( stock partition ), ROOT and Recovery, and I have flash cm10.
misc.img: http://www.mediafire.com/?1n0pmdbembdeorr
lgdrm.img: http://www.mediafire.com/?dan8jpucxjdw4ok
Chuck Bartowski said:
Ok, sorry, I didn't know.
I have reflash 10b with NVflash ( stock partition ), ROOT and Recovery, and I have flash cm10.
misc.img: http://www.mediafire.com/?1n0pmdbembdeorr
lgdrm.img: http://www.mediafire.com/?dan8jpucxjdw4ok
Click to expand...
Click to collapse
Thanks again, but even installing the stock version, the misc partition lgdrm and do not return to be the same (missing files)
What about usb storage(internal storage) mounting after FUSING ?
Will it work as before ?
Click to expand...
Click to collapse
Working same
Good news, I have uploaded the file. Zip
http://forum.xda-developers.com/showthread.php?p=33671985
Take a look at this link
teamw.in/DataMedia
So i think we might loose usb mounting on pc
Sent from my LG-P990 using xda app-developers app
ProgMaq said:
Sorry, SDCARD is the defaul name for internal.
FUSE = (Internal EMMC + DATA)
Without FUSE:
Partition 8 = DATA [1,5GB]
Partition 9 = EMMC [5,3 GB]
With FUSE only have:
Partition 8 = USERDATA [6,8 GB]
The user can see 6,8 GB in Internal SD
Click to expand...
Click to collapse
and still - i like it as it is
i still have 2 partitions with 6,8 GB total - but i can keep things more organized with 2 partitions than with one...
for me it's just like having 2+ PC harddrives - one only for the system, and other disks for the other files...
how do I flsh this to files with nvflash?
instead of fuse of internal memory(1.5gb) n internal sd(5.5gb).....
can i have fuse of internal sd(5.5gb) n external sd(i have 16gb) so that i can get...
external sd---21.5gb....
imo 1.5gb is enough for app data but 5.5gb is not enough for sd data files(nova 3 almost 2gb)
i hav mounted my externalsd as internalsd so that sd data files are saved in ext but 16gb not enough(game addict)...
hope u can help..thanks
ullekh99 said:
instead of fuse of internal memory(1.5gb) n internal sd(5.5gb).....
can i have fuse of internal sd(5.5gb) n external sd(i have 16gb) so that i can get...
external sd---21.5gb....
imo 1.5gb is enough for app data but 5.5gb is not enough for sd data files(nova 3 almost 2gb)
i hav mounted my externalsd as internalsd so that sd data files are saved in ext but 16gb not enough(game addict)...
hope u can help..thanks
Click to expand...
Click to collapse
I like it ,interesting thought
But what will hapn when sd ejected and phone restarted
Sent from my LG-P990 using xda app-developers app
Hi, I'm wanting to swap my emmc and my sdcard mount points on cm10.
My current (vanilla) /etc/vold.fstab is:
Code:
## Vold 2.0 Acclaim
## emmc
dev_mount emmc /storage/sdcard0 10 /devices/platform/omap/omap_hsmmc.1/mmc_host/mmc0
## sdcard
dev_mount sdcard /storage/sdcard1 5 /devices/platform/omap/omap_hsmmc.0/mmc_host/mmc1
I am wanting to do this:
Code:
## Vold 2.0 Acclaim
## emmc
dev_mount sdcard /storage/sdcard0 10 /devices/platform/omap/omap_hsmmc.1/mmc_host/mmc0
## sdcard
dev_mount sdcard-ext /storage/sdcard1 5 /devices/platform/omap/omap_hsmmc.0/mmc_host/mmc1
Anyone else tried this?
kcuf it, I'm doing it!
WISH ME LUCKKKKKKKKKKK
and that didn't work? that's odd.
Even this suggests essentially the same thing?: http://forum.xda-developers.com/showthread.php?p=33253737
abense said:
and that didn't work? that's odd.
Even this suggests essentially the same thing?: http://forum.xda-developers.com/showthread.php?p=33253737
Click to expand...
Click to collapse
It didn't work because of the way verygreen mounted emmc in the initialization code. He did not use vold. I could probably make you a userinit.d script to do it but not sure how quickly I will get to it.
Why do you want to do this? Running from a small SD and you want apps to use emmc?
Sent from my HD+ running CM10 on SD with XDA Premium
leapinlar said:
Why do you want to do this? Running from a small SD and you want apps to use emmc?
Click to expand...
Click to collapse
I have quite an array of MicroSDs lol
Should you care to know, I developed an affinity for them during my days of PSP hacking, as can be seen here:
http://i7.photobucket.com/albums/y266/thebense/f20b_engine_pics/catashtrophe/psp1.jpg
http://i7.photobucket.com/albums/y266/thebense/f20b_engine_pics/catashtrophe/psp2.jpg
In fact, during this time period, the girl I was dating gave me THREE 8GB microsdhcs for Christmas one year. Thats all she gave me lol!
But anyways, yes. I have a lot of them. However, their "stop the world" characteristics (eloquently described here) seems to me to be a very drastic performance issue our application.
From what I've read, the fastest cards seem to be the smaller cards anyways. I was mostly asking about this for performance reasons.
abense said:
I have quite an array of MicroSDs lol
Should you care to know, I developed an affinity for them during my days of PSP hacking, as can be seen here:
In fact, during this time period, the girl I was dating gave me THREE 8GB microsdhcs for Christmas one year. Thats all she gave me lol!
But anyways, yes. I have a lot of them. However, their "stop the world" characteristics (eloquently described here) seems to me to be a very drastic performance issue our application.
From what I've read, the fastest cards seem to be the smaller cards anyways. I was mostly asking about this for performance reasons.
Click to expand...
Click to collapse
I'm still not sure why you want to do this, but it does not matter, I have your answer.
You need to go to Terminal Emulator and enable superuser mode by typing su enter. Then enter these two commands:
Code:
mount -o bind /int-data/media /storage/sdcard1
mount -t vfat -o umask=0000 /dev/block/vold/179:29 /storage/sdcard0
That will swap emmc and sdcard until the next reboot.
If you want to make it permanent, edit /system/bin/clear_bootcnt.sh to append these three lines:
Code:
sleep 15
mount -o bind /int-data/media /storage/sdcard1;
mount -t vfat -o umask=0000 /dev/block/vold/179:29 /storage/sdcard0;
Then reboot, they will be remain swapped every time you boot. If you want to swap them back, comment out or delete those lines and reboot again.
Edit: Make sure if you edit that file that its permissions remain the same. That is for execution.
Edit2: If on the Hybrid, change the 29 number to 27.
Hello guys, I am running Android off SdCard because my HD+ has a dead emmc, I recently discovered that I can read and write to it using root explorer, does that mean that there's a chance that I could somehow recover it?
mmk92 said:
Hello guys, I am running Android off SdCard because my HD+ has a dead emmc, I recently discovered that I can read and write to it using root explorer, does that mean that there's a chance that I could somehow recover it?
Click to expand...
Click to collapse
how can you access your emmc? the (emmc-less) rom that verygreen made used our sdcards as the emmc I think that what you are seeing is a portion of your sdcard not your emmc
Hello,
I've seen your other thread here at XDA, and I'm not trying to be offensive, but I think you maybe confused with EMMC, Pure SD install and the term "dead EMMC". Apologies I didn't reply to your other thread earlier; I did/do not have much time. Please note, I do not indent to be offensive at all, just trying to put facts together; to hopefully ease you to achieve your solution.
For starters, I don't think your EMMC is "dead"; else you would have a difficult time booting your tablet up (I'd be surprised if a Nook turned on with a dead EMMC), even if you're purely installed on an SD card. Personally what I think is going on, you stated in the other thread your friend gave you this Nook. Your friend thought he (assuming he's male) could install CyanogenMod on his Nook, but unfortunately he couldn't. Effectively, he thought he had "bricked" or damaged his Nook; at this point it was not working the way he intended, and couldn't boot into CyanogenMod. He turned to you for help, or you stepped in, as your more "technical" with this stuff. Of course, I could be wrong. You knew you wouldn't be able to fix this, but you could use an alternative way to boot CyanogenMod; using only a SD card.
Not bad idea, but I'm quite confident that your EMMC is not "dead" and that you can install CyanogenMod on your internal storage without a SD card being required for boot. Apologies if my assumptions contain mistakes, I only completed reading the thread after posting the above.
I was going to post some suggestions and write up some guides, but before I do, please may I ask a question? You said you're using Root Explorer? Where is this? On your stock ROM on internal/EMMC, on a CyanogenMod build on EMMC, or on Pure SD? If you're booting using purely a SD card, and have Root Explorer running, you can edit files because it's editing files on your SD card, not your EMMC (although it may say internal, a pure SD install "emulates" the internal storage).
Again, please reply with the answer(s). I'll do my best to assist. Also, just a quick note; it's not necessary to make two threads. You could have still used your earlier thread.
HiddenG said:
Hello,
I've seen your other thread here at XDA, and I'm not trying to be offensive, but I think you maybe confused with EMMC, Pure SD install and the term "dead EMMC". Apologies I didn't reply to your other thread earlier; I did/do not have much time. Please note, I do not indent to be offensive at all, just trying to put facts together; to hopefully ease you to achieve your solution.
For starters, I don't think your EMMC is "dead"; else you would have a difficult time booting your tablet up (I'd be surprised if a Nook turned on with a dead EMMC), even if you're purely installed on an SD card. Personally what I think is going on, you stated in the other thread your friend gave you this Nook. Your friend thought he (assuming he's male) could install CyanogenMod on his Nook, but unfortunately he couldn't. Effectively, he thought he had "bricked" or damaged his Nook; at this point it was not working the way he intended, and couldn't boot into CyanogenMod. He turned to you for help, or you stepped in, as your more "technical" with this stuff. Of course, I could be wrong. You knew you wouldn't be able to fix this, but you could use an alternative way to boot CyanogenMod; using only a SD card.
Not bad idea, but I'm quite confident that your EMMC is not "dead" and that you can install CyanogenMod on your internal storage without a SD card being required for boot. Apologies if my assumptions contain mistakes, I only completed reading the thread after posting the above.
I was going to post some suggestions and write up some guides, but before I do, please may I ask a question? You said you're using Root Explorer? Where is this? On your stock ROM on internal/EMMC, on a CyanogenMod build on EMMC, or on Pure SD? If you're booting using purely a SD card, and have Root Explorer running, you can edit files because it's editing files on your SD card, not your EMMC (although it may say internal, a pure SD install "emulates" the internal storage).
Again, please reply with the answer(s). I'll do my best to assist. Also, just a quick note; it's not necessary to make two threads. You could have still used your earlier thread.
Click to expand...
Click to collapse
I think you are quite wrong.The lagfix app bug actually does kill the emmc what hes using is an emmc-less rom that verygreen created for all the users who were affected by the emmc bug. This rom doesnot use the emmc at all it treats the sdcard as the emmc
Ahh, no problem. Thank you Talha, that cleared a few things for me. Haha, I've been missing from the latest developments on the Nook's.
Still, I hold my statement in this case, as the OP stated he can boot into EMMC recovery (source). So the EMMC is not dead.
Thank you guys for the replies!
I am accessing the emmcs through Root explorer on a nonemmc ROM, so I could be accessing the SD card itself, makes perfect sense.
But if i boot up my tablet without an sd card, it goes to the internal EMMC recovery, in that recovery I can access the SD card, but can't mount the emmc itself. (it says E: error can't mount /emmc/
This is weird because I've always though the recovery and ROM resie on the emmc.
Please pardon my ignorance guys.
mmk92 said:
Thank you guys for the replies!
I am accessing the emmcs through Root explorer on a nonemmc ROM, so I could be accessing the SD card itself, makes perfect sense.
But if i boot up my tablet without an sd card, it goes to the internal EMMC recovery, in that recovery I can access the SD card, but can't mount the emmc itself. (it says E: error can't mount /emmc/
This is weird because I've always though the recovery and ROM resie on the emmc.
Please pardon my ignorance guys.
Click to expand...
Click to collapse
No problem, haha. Is the recovery on your EMMC ClockWorkMod or TeamWin Recovery? If either of these, and you can boot into them; then may be I have a solution for you. Please let me know.
Also, have you tried flashing a ROM using your EMMC recovery? I'm pretty sure you have, and I'm assuming an error was presented? Let me know.
Without an sd card inside the Nook, it boots straight to CWM recovery. I tried flashing " cm-10.2-20131207-NIGHTLY-ovation.zip" first it gave me "E:Can't mount /cache/recovery/last_install E: failed to open last_install: no such directory or file" then it started running then it gave me a (status 0) error and then eventually aborting. I tried flashing the TWR, reports the same "last_install"errors like the ROM flash, then it finished really fast(around a second) reports a "Done..! Install from sdcard complete." but changes absolutely nothing (if i restart it goes back to CWM).
mmk92 said:
Without an sd card inside the Nook, it boots straight to CWM recovery. I tried flashing " cm-10.2-20131207-NIGHTLY-ovation.zip" first it gave me "E:Can't mount /cache/recovery/last_install E: failed to open last_install: no such directory or file" then it started running then it gave me a (status 0) error and then eventually aborting. I tried flashing the TWR, reports the same "last_install"errors like the ROM flash, then it finished really fast(around a second) reports a "Done..! Install from sdcard complete." but changes absolutely nothing (if i restart it goes back to CWM).
Click to expand...
Click to collapse
I think that your emmc is working but your partitions are broken
So there's hope? What do you guys suggest I do
mmk92 said:
So there's hope? What do you guys suggest I do
Click to expand...
Click to collapse
It is possible that your emmc is readable, but not writeable. I had an SD where that happened. It would act like it was writing and the PC would say successful, but when I ejected the SD and reinserted, it has not changed. Nothing I could do would revive the SD. I had to throw it away.
I suggest you use your noemmc ROM to explore emmc to see if you can change anything and have it stick after a reboot.
Sent from my BN NookHD+ using XDA Premium HD app
Bits in SD cards have a certain lifespan, I believe between 10k-100k read/writes until they become unwritable. Some generic/defective cards have much less. So in your case it could've been an old/cheap brand SD card that happened to die. Although the eMMC shares these drawbacks, it has a much longer lifespan, and I highly doubt this the issue for the emmc.
I attached to this post a dump of logs that I have collected from my Nook. I see a bunch of "unknown partition table" in there, so could that be the problem? Does that mean that a partition fix should solve my problem?(I've read about lots of devices revived from broken partition tables).
What if this is the issue for most people and not a dead eMMC chip? If this theory proves to be true maybe many nooks will be brought back from the dead.
It's times like these that I wish that I was more experienced with such low level stuff I barely know the terminology so again, please ignore my ignorance.
Sorry for the mult-posts, why did you leave meeh out to dry I am willing to try anything on my Nook if it has a chance to get back to life.
mmk92 said:
Sorry for the mult-posts, why did you leave meeh out to dry I am willing to try anything on my Nook if it has a chance to get back to life.
Click to expand...
Click to collapse
Is yours like this? http://forum.xda-developers.com/showthread.php?p=44842492&highlight=partition#post44842492
Sent from HD+ MAG2GA CM 10.2 from SD
I get no output for the command dmesg|grep mmc1 nor dmesg|grep mmcblk1
I do however get response from dmesg|mmcblk0
~ # dmesg|grep mmcblk1
dmesg|grep mmcblk1
~ # dmesg|grep mmcblk0
dmesg|grep mmcblk0
<6>[ 3.039337] mmcblk0: mmc0:0001 MAG2GA 14.5 GiB
<6>[ 3.039611] mmcblk0boot0: mmc0:0001 MAG2GA partition 1 2.00 MiB
<6>[ 3.039825] mmcblk0boot1: mmc0:0001 MAG2GA partition 2 2.00 MiB
<6>[ 3.040649] mmcblk0: unknown partition table
<6>[ 3.041839] mmcblk0boot1: unknown partition table
<6>[ 3.042846] mmcblk0boot0: unknown partition table
~ #
Click to expand...
Click to collapse
mmk92 said:
I get no output for the command dmesg|grep mmc1 nor dmesg|grep mmcblk1
I do however get response from dmesg|mmcblk0
Click to expand...
Click to collapse
The 1 applies when booted from the noemmc sdcard.
Here's another possibly helpful post http://forum.xda-developers.com/showthread.php?p=44887350
Sent from HD+ MAG2GA CM 10.2 from SD
~ # mke2fs -t ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/cache
mke2fs -t ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/cache
mke2fs 1.41.14 (22-Dec-2010)
Could not stat /dev/block/platform/omap/omap_hsmmc.1/by-name/cache --- No such f
ile or directory
The device apparently does not exist; did you specify it correctly?
~ # mount .cache
mount .cache
mount: can't find .cache in /etc/fstab
~ # mount /cache
mount /cache
mount: mounting /dev/block/platform/omap/omap_hsmmc.1/by-name/cache on /cache fa
iled: No such file or directory
~ # mount /cache
mount /cache
mount: mounting /dev/block/platform/omap/omap_hsmmc.1/by-name/cache on /cache fa
iled: No such file or directory
~ # mke2fs -t ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/cache
mke2fs -t ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/cache
mke2fs 1.41.14 (22-Dec-2010)
Could not stat /dev/block/platform/omap/omap_hsmmc.1/by-name/cache --- No such f
ile or directory
The device apparently does not exist; did you specify it correctly?
~ # mke2fs -t ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/cache
mke2fs -t ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/cache
mke2fs 1.41.14 (22-Dec-2010)
Could not stat /dev/block/platform/omap/omap_hsmmc.1/by-name/cache --- No such f
ile or directory
The device apparently does not exist; did you specify it correctly?
~ #
Click to expand...
Click to collapse
I get the "Could not stat /dev/block/platform/omap/omap_hsmmc.1/by-name/cache --- No such f
ile or directory" on every run.
Also tried flashing Stock from all recoveries, still no change
mmk92 said:
I get the "Could not stat /dev/block/platform/omap/omap_hsmmc.1/by-name/cache --- No such f
ile or directory" on every run.
Also tried flashing Stock from all recoveries, still no change
Click to expand...
Click to collapse
Here is a link for recreating the partition table http://forum.xda-developers.com/showthread.php?p=44620340&highlight=table#post44620340
Sent from HD+ MAG2GA CM 10.2 from SD
I got this interesting message when I executed print in parted.
Warning: /dev/block/mmcblk0 contains GPT signatures, indicating that it has a
GPT table. However, it does not have a valid fake msdos partition table, as it
should. Perhaps it was corrupted -- possibly by a program that doesn't
understand GPT partition tables. Or perhaps you deleted the GPT table, and are
now using an msdos partition table. Is this a GPT partition table?
Yes/No? yes
yes
yes
Model: MMC MAG2GA (sd/mmc)
Disk /dev/block/mmcblk0: 30535680s
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 256s 511s 256s xloader
2 512s 1023s 512s bootloader
3 1024s 31743s 30720s recovery
4 32768s 65535s 32768s boot
5 65536s 163839s 98304s fat32 rom
6 163840s 262143s 98304s fat32 bootdata
7 262144s 1179647s 917504s ext4 factory
8 1179648s 2555903s 1376256s ext4 system
9 2555904s 3506175s 950272s ext4 cache
10 3506176s 30507007s 27000832s ext4 userdata
(parted)
Click to expand...
Click to collapse
Also the partitions seem intact, what do you suggest I do?