Database Users

Putting update on sd card w/o removing it?

I was wondering if there is an app that allows you to put an update (nighty) on an sd card without having to remove the card and attaching it to your computer.
I have wifi pro and that doesn't look like it allows me to do that and just hooking the nook to my pc doesn't look like it gives me the option either. Am I missing something?

I've haven't done myself yet but heard people mentioned about the app called "Root Explorer"??? or "Root Folder" or something with "root".
Download nightly build directly on the NC then use the app to drag the zip file over the "boot" partition.
I think it should be able to do, not done that myself.

The best I can offer is, if you eject the card long enough to start booting to stock, then re-insert it before stock fully loads (on one of the splash screens), the boot partition will be mounted as storage and you can connect to your PC by USB to drop an update file in there.
It might help you out if the issue is not having access to a card reader, but you still have to pop the card out and back in.
ETA: I never had any luck getting an update on the root of any SD, even one formatted for storage, using a file manager.

NookColorUMS allows you to mount any partition. Turn off compatibility mode in spare parts and then reboot to see app in full screen.
http://forum.xda-developers.com/showthread.php?t=952456

If you're running off of SD and adb is working then:
adb shell busybox mkdir /sdcard/boot
adb shell busybox mount /dev/block/mmcblk1p1 /sdcard/boot
adb push ***UPDATEFILE*** /sdcard/boot
adb reboot recovery
If running from EMMC then:
adb shell busybox mkdir /sdcard/boot
adb shell busybox mount /dev/block/mmcblk0p1 /sdcard/boot
adb push ***UPDATEFILE*** /sdcard/boot
adb reboot recovery

[Q] Gapps and CM7 auto update/upgrade when booting from SD card?

Hello all! New user here. I looked in the forums for this and can't find this question answered, but I am sure I missed it. My apologies before hand if that's the case.
I have a Nook with a 16GB SanDisk card with CM7 running off the card itself, which allows me to dualboot back to the original Nook software if I want to.
My question is this. Is there a way to automatically update CM7 and/or Google Apps without copying them to my Sd card on my PC, booting into recovery, etc?
I know there's the paid version of Rom Manager, but if I read that correctly, that only works when the Nook has CM7 running on the Nook directly and not on the SD card?
Thanks in advance for your time!

You can use adb and mount the boot partition to an empty folder on the partition CM7 sees as the SD card and push the nightly to that location... then just use adb's reboot recovery command...
(FIRST TIME ONLY) adb shell mkdir /sdcard/boot
adb shell mount /dev/block/mmcblk1p1 /sdcard/boot
adb push (UPDATE FILE) /sdcard/boot
adb reboot recovery

Thanks!
I will give this a try! Let's see if I can not break my root.
DizzyDen said:
You can use adb and mount the boot partition to an empty folder on the partition CM7 sees as the SD card and push the nightly to that location... then just use adb's reboot recovery command...
(FIRST TIME ONLY) adb shell mkdir /sdcard/boot
adb shell mount /dev/block/mmcblk1p1 /sdcard/boot
adb push (UPDATE FILE) /sdcard/boot
adb reboot recovery
Click to expand...
Click to collapse

[Q] TF101 doesn't recognize internal sdcard

I have CWMR 5,8 installed. First boot automatically loads into CWMR [this is, as far as I've read, a problem with the recovery and I can handle it if I can fix the internal sd card]. Rebooting and cold-booting helps me boot up my ROM (I've tried multiple ROMs, currently on CM9).
Everything works, except for my internal sdcard (weirdly thought I cannot access my external micro SD from CWMR). It seems as if its not mounted. I got ADB access to the device, /sdcard is there and all of the files are there. I can adb push and adb pull, so the internal storage seems to be working fine, it just doesn't mount it. Maybe the issue is permissions? ls -la sdcard outputs: lrwxrwxrwx root root 2012-10-26 20:43 sdcard -> /storage/sdcard0
Any ideas? I've tried installing different versions of CWM recoveries (adb push zip file and then using CWM to actually install it), they don't seem to stick.

Does /storage/sdcard0 exist on your device (AFAIK this is the new location defined by JB, but I don't know what CM9 does)?
If not, you may find your files in /data/media.

peeter.tomberg said:
I have CWMR 5,8 installed. First boot automatically loads into CWMR [this is, as far as I've read, a problem with the recovery and I can handle it if I can fix the internal sd card]. Rebooting and cold-booting helps me boot up my ROM (I've tried multiple ROMs, currently on CM9).
Everything works, except for my internal sdcard (weirdly thought I cannot access my external micro SD from CWMR). It seems as if its not mounted. I got ADB access to the device, /sdcard is there and all of the files are there. I can adb push and adb pull, so the internal storage seems to be working fine, it just doesn't mount it. Maybe the issue is permissions? ls -la sdcard outputs: lrwxrwxrwx root root 2012-10-26 20:43 sdcard -> /storage/sdcard0
Any ideas? I've tried installing different versions of CWM recoveries (adb push zip file and then using CWM to actually install it), they don't seem to stick.
Click to expand...
Click to collapse
ok first thing, your external microsd card should be /Removable/MicroSD/. also what do you mean when you say youre pushing zip files then installing them but they dont seem to stick? how are you connecting via adb are you using ./adb shell to connect and move files? theres a certain way you have to push files to the device when youre in recovery.

Fixed it
Hello,
Not being able to mount the internal sdcard
The problem was I installed CM10 then somehow rolled back to CM9. The sdcard location moved between those 2 versions and the CM9 version wasn't able to mount it anymore. After installing CM10 everything worked apart from the boot loop.
TF101 booted into recovery every time
I fixed that by flashing: http://forum.xda-developers.com/showthread.php?t=1213723
and running the command to actually load in the new recovery from here: http://forum.xda-developers.com/showthread.php?t=1530337
In summary
My tf101 works thanks to all the info available on xda

[Q] Retrieve data from CWM

Hello there
I was wondering, can the internal sd card can be mounted with CWM?
If so, can you provide the button count to do it?
I have a S4 with a broken LCD, and I want to retrieve the data, but since I can't enter the passcode, not kies or windows see the files.
I managed to root it and flash CWM but now I got stuck and I just don't remember if I can't mount the internal SD with CWM

dsv591 said:
Hello there
I was wondering, can the internal sd card can be mounted with CWM?
If so, can you provide the button count to do it?
I have a S4 with a broken LCD, and I want to retrieve the data, but since I can't enter the passcode, not kies or windows see the files.
I managed to root it and flash CWM but now I got stuck and I just don't remember if I can't mount the internal SD with CWM
Click to expand...
Click to collapse
install android sdk if you dont have it.
boot your phone into cwm and connect to pc.
open cmd line where adb file exist, and type:
Code:
adb devices
you must see your serial number with recovery
Code:
adb pull /sdcard/ /sdcard/
when it finish, "sdcard" folder in "c" directory

samersh72 said:
install android sdk if you dont have it.
boot your phone into cwm and connect to pc.
open cmd line where adb file exist, and type:
Code:
adb devices
you must see your serial number with recovery
Code:
adb pull /sdcard/ /sdcard/
when it finish, "sdcard" folder in "c" directory
Click to expand...
Click to collapse
So, after some struggling with the adb drivers I got the device detected by adb and gave this a try, but I think I hit another wall.
sdcard showed 0 files, so I entered the shell and realized the sdcard was not mounted.
I tried to mount it by running mount /sdcard/ but it says sdcard can't be found in fstab{
This is what my fstab has:
cat fstab
/dev/block/mmcblk0p19 /cache ext4 rw
/dev/block/mmcblk0p21 /data ext4 rw
/dev/block/mmcblk0p20 /system ext4 rw
Any suggestion? Thanks in advance
EDIT: I'm thinking that maybe CWM didn't flash correctly (I did it from Odin, and since I'm going blindly there is no way for me to know for sure)

dsv591 said:
So, after some struggling with the adb drivers I got the device detected by adb and gave this a try, but I think I hit another wall.
sdcard showed 0 files, so I entered the shell and realized the sdcard was not mounted.
I tried to mount it by running mount /sdcard/ but it says sdcard can't be found in fstab{
This is what my fstab has:
cat fstab
/dev/block/mmcblk0p19 /cache ext4 rw
/dev/block/mmcblk0p21 /data ext4 rw
/dev/block/mmcblk0p20 /system ext4 rw
Any suggestion? Thanks in advance
EDIT: I'm thinking that maybe CWM didn't flash correctly (I did it from Odin, and since I'm going blindly there is no way for me to know for sure)
Click to expand...
Click to collapse
did you try this
Code:
adb shell
mount /sdcard

samersh72 said:
did you try this
Code:
adb shell
mount /sdcard
Click to expand...
Click to collapse
I did. That's when it said that /sdcard/ coudn't be found in /etc/fstab
****************************
UPDATE
I got it to work.
If anyone is interested, this is how I mounted the sdcard
Code:
mount /dev/block/mmcblk0p21 /sdcard/
where mmcblk0p21 is the partition that sdcard usually mounts.
After that, it was a simple as exiting the shell and run
Code:
pull /sdcard/ /sdcard/
as recommended above

How to rename file in boot partition of sdcard

This may not be possible, but it would be good if it were
Attached below is the output of the "mount" command. The sdcard has four partitions:
(root--contains the boot information, u-boot.bin, uImage, mlo, etc.)--FAT32
system--ext3
cache--ext3
userdata--ext3
When the device boots from the card, the root or boot partition is invisible. I'd like to mount that partition while the ROM is running (if possible) and rename u-boot.bin to something else like u-boot.bin.bak. Or maybe the partition is already mounted and I just need to know how to access it.
I can't see in the mount output where to try this.
Is it possible?

nmyshkin said:
This may not be possible, but it would be good if it were
Click to expand...
Click to collapse
Huh? Why would you want to do that?
Code:
# mount -o rw,remount rootfs /
# mkdir /boot
# mount -t vfat /dev/block/mmcblk0p1 /boot
# ls -l boot

Renate NST said:
Huh? Why would you want to do that?
Code:
# mount -o rw,remount rootfs /
# mkdir /boot
# mount -t vfat /dev/block/mmcblk0p1 /boot
# ls -l boot
Click to expand...
Click to collapse
Oh so excellent! A simple mv command and the device will boot into the stock OS instead of the sd ROM!!! And from the stock OS, a simple rename of the u-boot.bin.bak file and the device will reboot into the sd ROM. A crude "boot menu" of sorts without removing the sdcard to effect the change. To be done by two little apps, one for each ROM.
That's why I would want to do that. Thank you!!
Hmm...is there any reason to unmount the rootfs before rebooting? And is the mkdir /boot permanent or does it need to be executed each time?
Edit: the answer to my second question seems to be "no" as after a reboot I had to execute the mkdir /boot command again.
But the desired effect is not achieved. After supposedly renaming u-boot.bin to u-boot.bin.bak a reboot resulted in the sdcard ROM booting up again. A check of the files in the boot partition (as above) shows u-boot.bin.bak so it should not have been able to find the file to boot from and therefore should have booted from the internal OS.
So...after powering down completely and removing the sdcard to take a look at the active (boot) partition, I find that u-boot.bin has NOT been renamed, even though the file listing showed it as such. That explains the reboot back into the sdcard ROM, but not much else.
Edit2: I see that a "boot" folder has been created in the root directory of the sdcard and it contains the files that are in the boot partition, plus a few I've not seen before. Even after a reboot this folder contains the renamed u-boot.bin file but it doesn't do me any good there.

So, I'm confused.
You have an SD card and the NST is booting from there, right?
You want to make it so you can select between SD card and internal?
The instructions I gave were for mounting the internal u-boot.bin
Since the SD card is preferred by the loader you want to rename the u-boot.bin on the SD card.
And you probably don't even want to do that.
The mlo is the first thing loaded, you probably want to incapacitate that instead.
This is for the SD card:
Code:
# mount -t vfat /dev/block/mmcblk1p1 /boot

Renate NST said:
The mlo is the first thing loaded, you probably want to incapacitate that instead.
This is for the SD card:
Code:
# mount -t vfat /dev/block/mmcblk1p1 /boot
Click to expand...
Click to collapse
Yes! Things were a little dicey at first because I had inadvertently incapacitated the stock OS during my fumbling around by renaming the internal u-boot.bin (oops). Fortunately the device was forgiving and allowed me to remove the sdcard without any apparent bad effects, rename u-boot.bin.bak again, reinsert the card and patiently try to force the power key to do it's stuff. I finally got a reboot to the card, fixed the internal boot issue and tried again.
It works!!!! But you knew it would
I agree, renaming MLO makes more sense (and works). I knew that was first in line but became a little fixated on u-boot.bin because my original search began with a dual boot scheme used for the Nook Color which involved patching a menu system into u-boot.bin. Way out of my league, but my mostly fruitless reading eventually led me to my rather more pedestrian idea.
In a way, it makes more sense in the context of the NST which most people don't turn off. As long as there is a way to move back and forth between the emmc and sdcard OSes without swapping cards or shutting down completely, that's what I was hoping for at a minimum. I think this will do nicely.
Thanks again for your help. Now back to work on this beast...