Related
When i try to push or pull anything it says, e/ddms the file cannot be pushed because its a read-only file system. Any help?
Mdawg112 said:
When i try to push or pull anything it says, e/ddms the file cannot be pushed because its a read-only file system. Any help?
Click to expand...
Click to collapse
You have to remount the FS in read/write mode.
With adb it's 'adb remount'.
smw6180 said:
You have to remount the FS in read/write mode.
With adb it's 'adb remount'.
Click to expand...
Click to collapse
Ha, I feel stupid now.
Mdawg112 said:
Ha, I feel stupid now.
Click to expand...
Click to collapse
Happens to everyone at times. Don't sweat it
So what do you do, if you run adb remount
and it still say's read-only system when trying to push?
been dealing with it for a few days, looked all around the forums and didn't find anything that helped :-/
jubi23 said:
So what do you do, if you run adb remount
and it still say's read-only system when trying to push?
been dealing with it for a few days, looked all around the forums and didn't find anything that helped :-/
Click to expand...
Click to collapse
Good question. Unfortunately I have no idea. Never seen it fail. theoretically there's a command line you can run in adb shell to mount the FS read/write, but I can't remember it off the top of my head.
Something like mount -o rw /dev/m3blk (as I said I can't remember the exact filesystem name). I'd do a search for 'mount -o' on the forums. It's been posted more than once and I'm too lazy to find it for you
I believe you're refering to
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
if so, tried that too :-/ still nothing
i read someone had reformatted their card on xp vs 7, so tried that to and still nothing haha
i give up
thanks btw
Yeah, I'm having the same problem as you sometimes. Other times it works. It's very strange! It annoys me. Anyone have any idea on a fix?
jubi23 said:
I believe you're refering to
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
if so, tried that too :-/ still nothing
i read someone had reformatted their card on xp vs 7, so tried that to and still nothing haha
i give up
thanks btw
Click to expand...
Click to collapse
Yeah that's the one, thanks.
Have you tried that from recovery? Are you using a2sd and if so, what ext?
Are you able to mount the card as a disk drive? Are you sure the SD card isn't going bad on you?
Sounds like you've checked anything else I would have thought of...wish I could help.
Have you tried that from recovery? Are you using a2sd and if so, what ext?
Are you able to mount the card as a disk drive? Are you sure the SD card isn't going bad on you?
Click to expand...
Click to collapse
Well i'm actually trying to flash a new recovery (all in the pursuit of installing flipz new fresh rom with ext4 haha), so was doing it from the computer
I tried using a2sd but i'm pretty sure it didn't work, because i went to ext4 and to my knowledge fresh 2.0d can't use ext4, so yea, i fail
i am able to mount the card as a disk drive and can move things back and fourth via explorer, play music, everything except this seems to be fine, it's only a few weeks old, so i really hope it's not dying
jubi23 said:
Well i'm actually trying to flash a new recovery (all in the pursuit of installing flipz new fresh rom with ext4 haha), so was doing it from the computer
I tried using a2sd but i'm pretty sure it didn't work, because i went to ext4 and to my knowledge fresh 2.0d can't use ext4, so yea, i fail
i am able to mount the card as a disk drive and can move things back and fourth via explorer, play music, everything except this seems to be fine, it's only a few weeks old, so i really hope it's not dying
Click to expand...
Click to collapse
That could be it. ext4 doesn't play nicely with ext3 based stuff. It's 'semi' backward compatible (meaning you can mount ext4 as ext3) but it seems to have some serious inconsistencies that way. I'd recommend a re-partition and then upgrade ext3->ext4 AFTER you install the new ROM.
Heh. I had all KINDS of problems restoring an ext3 based nandroid after upgrading to ext4. Had to repartition and then restore the nandroid to get it to work.
well, loaded recovery, re-partitioned my sdcard, upgraded to ext3 and left it there, still nothing
the sd card wouldnt have any bearing on the ability to adb remount.
the /system partition is stored on the phone itself, so the mount -o ..yadda yadda
remounts the /system partition in this case /dev/block/mtdblock3.
the only reason a sd card would come to play is if youre runnign a2sd, in which case it makes symlinks (shortcuts) to the sdcard, if the sdcard is formatted improperly then a2sd will either cause a bootloop, or crash and then youre phone should boot normally but you wont have access to your ext4 partition (the partition with your apps).
im not sure how to fix a problem with adb remount, perhaps try a new version of the SDK or just a clean one.
good luck
I'm wondering if there is something wrong with my mounting
When i'm in the shell
if i cd /sdcard
then do a ls
nothing is returned
I've also directly copied the recovery image from my computer to the sdcard, and attempted to run the flash_image command and it says no such file or directory
I do have usb debugging enabled and am selected to mount the sdcard, is there some other step or something i'm missing?
nenn, i had actually just a little bit ago downloaded the latest sdk on a completely different machine and still same results
Alrite, so I was able to copy the image recovery from
explorer and flash from.terminal on my phone
Although I'd prefer to work from the pc, anyone have any other possible ideas?! I'm at a loss
-------------------------------------
Sent from my HERO200
Now.. coming from linux shouldn't this work now that we have root?
In theory this SHOULD work no?
ln -s /sdcard/app /data/app
I've tried to but with no avail. The phone refuses to boot.
Does it need a special rom to? I'm guessing the SDCard doesn't get mounted till its fully in? theres no /etc/fstab is there another mounting script I'm missing?
Thanks
xxsashixx said:
Now.. coming from linux shouldn't this work now that we have root?
In theory this SHOULD work no?
ln -s /sdcard/app /data/app
I've tried to but with no avail. The phone refuses to boot.
Does it need a special rom to? I'm guessing the SDCard doesn't get mounted till its fully in? theres no /etc/fstab is there another mounting script I'm missing?
Thanks
Click to expand...
Click to collapse
The mount of the partitions of the sd is managed by vold; the configuration file is /etc/vold.conf.
Ciao Angelo
Ok so how would I modify this so it will work for Apps to the SD?
xxsashixx said:
Ok so how would I modify this so it will work for Apps to the SD?
Click to expand...
Click to collapse
I think you can add an entry in vold.conf as the examples in the file.
An other solution could be to mount the partition in /init.rc
Ciao Angelo
Does the partition in the SDCard have to put Ext2 for the apps?
Yes. You have to partition the SD
Hmm the phone still refuses to boot..
has anyone gotten this to work?
i agree with this
so anyone got this working? I assume no
After setting up my wife's A7 and using it for three weeks, I have decided to open mine up. I waited because I wanted to see if CES had anything I wanted more. I decided they didn't.
So, I am starting from scratch again.
The main issue I've had with my wife's A7 has been the lack of storage space for apps, especially the big games.
Bazbob seems to have a solution by partioning the microSD card and using Apps2sd.
I took a new Class 10 16GB microSD card.
I downloaded and burned Ubuntu onto a CD from here: http://www.ubuntu.com/desktop/get-ubuntu/download
Put the card in my laptop, restarted it into Ubuntu.
Ran gparted.
Shrunk the Fat32 partition to just under 8GB and added another partion as ext2 primary.
When I restarted my laptop, my sd reader in the laptop doesn't work.
When I put it into the A7, it says the SD card has Total Space of 7.73GB.
At this point, I'm not sure what to do next.
Help is appreciated!
jazzbone said:
After setting up my wife's A7 and using it for three weeks, I have decided to open mine up. I waited because I wanted to see if CES had anything I wanted more. I decided they didn't.
So, I am starting from scratch again.
The main issue I've had with my wife's A7 has been the lack of storage space for apps, especially the big games.
Bazbob seems to have a solution by partioning the microSD card and using Apps2sd.
I took a new Class 10 16GB microSD card.
I downloaded and burned Ubuntu onto a CD from here: http://www.ubuntu.com/desktop/get-ubuntu/download
Put the card in my laptop, restarted it into Ubuntu.
Ran gparted.
Shrunk the Fat32 partition to just under 8GB and added another partion as ext2 primary.
When I restarted my laptop, my sd reader in the laptop doesn't work.
When I put it into the A7, it says the SD card has Total Space of 7.73GB.
At this point, I'm not sure what to do next.
Help is appreciated!
Click to expand...
Click to collapse
You needed to make a second partition EXT2 and format it. You then need to mount the partition. I did this by using the install-recovery.sh that it located in /system/etc. I used the following tutorial and it worked. I got over 12gb of space to install apps.
http://forum.xda-developers.com/showthread.php?t=832799
I did try to mount the new partition to /storage which is also /sdcard and i was still not able to use titanium backup to move apps. The only way i have alot of space is use this method.
I'm also mounting the fat32 partition to location /storage so that when i download apps thats where they are stored until you install them. Also Titanium backup dumps the backups here. This is done with a custom mod of Dexters 1.0c mod.
I did not use adb, i used a app called quicksshd which allows you secure ftp into the tablet and make changes. I suggest using a windows programs called winscp and putty.
Thanks for replying rfisher.
Turns out that my laptop lost the drive letter for the sd card. That's fixed now. When I insert the card into my laptop, it says that you need to format the card in the drive to use it. Any idea why?
I am confused by your instructions.
You said
You needed to make a second partition EXT2 and format it.
Click to expand...
Click to collapse
I did that. First partition is FAT 32, and second partition is EXT2, primary.
Maybe I didn't format the partition? I just created it.
I'll install busybox and see how far I can get with it.
With the other A7, I was never able to work with ADB.
This device really makes me feel like an idiot.
Still can't believe I was the first to get Google Apps working on my wife's tablet!
no adb
Well, the hours of frustration have returned...
I can't get adb running on my laptop.
I installed Android SDK.
When I type adb in the cmd window on my laptop, I get
"adb" is not recognized as an internal or external command, operable program or batch file"
I have tried moving the ADK folder to c:\
and
to:
C:\Users\Bucks HP
No luck.
I added the path c:\android-sdk-windows\platform-tools
to the environment variables in my system properties.
My head is going to explode!
Well, I got adb working, I think...
Problem was in the cmd window. I had to change the path.
Now, I can't install busybox. I followed the instructions from the wiki.
When I type "adb push busybox /data/local"
it returns: cannot stat 'busybox' : no such file or directory.
I pasted the busybox file in the
C:\android-sdk-windows\platform-tools
folder.
Was that the right place for it?
Is the busybox file just a text file?
Also, mine is named busybox-armv6l
Should it be renamed? I tried "adb push busybox-armv6l /data/local"
and got the same result...
I gave up on installing busybox via the wiki instructions.
I installed Titanium Backup and installed busybox through it.
Now, when I type: cd /system
mkdir sd
I get :
mkdir failed for sd, read-only file system
What does that mean and how do I fix it?
Thanks
The saga continues...
With the busybox from Titanium Backup installed,
I needed to type:
adb shell
su
mount -o remount,rw /dev/block/mmcblk3p1 /system
exit
exit
Then, following the tutorial, I am up to step 12:
12) Now comes the tricky part: making Android mount your new partition at boot time. All the hard work would be useless if Android discarded the mount points every time we restarted our phones. To do this we’ll need to create 2 scripts and store then into /system/etc. Obviously the scripts should be started by init.rc and need to run as root. Fortunately Android’s init.rc have a gap that makes this possible. The scripts are named install-recovery.sh and init-sd2.sh.
My question is: How do you create scripts?
You would create them with notepad++ which is a windows program. Then using adb push them to the /system/etc directory.
I used a app called quicksshd and a windows program called winscp to copy the files to the directory. If you used my method you first need to make the /system directory rw before it will let you copy the files. It worked for me, the only thing i did differently is edit init.rc to mount the first partition of the sd card to /storage, but this was creating a modded 1.0c rom. So the result is about 4gb for my sd memory and 12gb for installing apps.
jazzbone said:
The saga continues...
With the busybox from Titanium Backup installed,
I needed to type:
adb shell
su
mount -o remount,rw /dev/block/mmcblk3p1 /system
exit
exit
Then, following the tutorial, I am up to step 12:
12) Now comes the tricky part: making Android mount your new partition at boot time. All the hard work would be useless if Android discarded the mount points every time we restarted our phones. To do this we’ll need to create 2 scripts and store then into /system/etc. Obviously the scripts should be started by init.rc and need to run as root. Fortunately Android’s init.rc have a gap that makes this possible. The scripts are named install-recovery.sh and init-sd2.sh.
My question is: How do you create scripts?
Click to expand...
Click to collapse
Hi rfisher
Thanks for replying!
While waiting, I opened Notepad++, copied the text in the tutorial window into it and saved the file as Unix.
Then, I copied it to a USB drive, put it in the A7, and copied to the system/etc folder.
Is that acceptable?
Then, I followed steps 13-15.
I think I did something wrong. I am not seeing it in Root Explorer. What should I be looking for?
Was I supposed to install Apps2SD already?
I got winscp and quicksshd working. YEAH!
Used them to copy the files as you did.
Restarted A7.
Still don't see the other partition.
PS. I was just rereading your earlier post and you mentioned:
I did try to mount the new partition to /storage which is also /sdcard and i was still not able to use titanium backup to move apps. The only way i have alot of space is use this method.
I'm also mounting the fat32 partition to location /storage so that when i download apps thats where they are stored until you install them. Also Titanium backup dumps the backups here. This is done with a custom mod of Dexters 1.0c mod.
Looking on my A7, I don't see a location that is /storage
My tablet is fresh out of the box, without any firmware updates yet.
I have downloaded a nand androuid build that I am 99% happy with. I do however want to change a couple of things on the build.
I have downloaed and got ubutu up and running on a virtual box. I have then copied the system.img file on to a usb drive and copied it into ubuntu. Location of the file is in stephen which is my logon name.
I have also created a folder called mount which I want to mount the img file to.
I have done this before in ubuntu using ext2 files but I can not get the mount command to work for an img file. Is there an way to mount the img file, remove the files I do not want and then comple a newer smaller img file?
EDIT: logged on as root and moved the system.img and mount folder to main file system folder. Ran command mount -t img /system.img /mount but now getting error unknown filesystem type 'img'
Any help would be appreciated.
The Issue
Hi, I have a Nook Simple Touch that gets stuck trying to boot. First I see the Barnes and Noble Screen, Next for a brief moment it tries to load a Rom and shows a small nook icon with a loading bar. Next it says "Install Failed". I am unable to do anything other than a factory reset, which doesn't help.
Background
I should add that the device previously was working fine, then one day it froze as I was highlighting some text. When I tried to boot it, it was stuck in the scenario described above. I believe it was already updated to 1.2.2 with seemingly no issues.
What I've tried:
I have tried restoring it back with noogie and a backup, and I have also tried the Nook Manager- Rescue from .zip and Rescue from backup to no avail. Still get that same blasted "Rom Restore Image" Screen followed by "Install Failed".
I have an update from Barnes and Noble called "nook_1_2_update.zip" which I tried to copy over to the nook but the file is too large.
Any ideas? I love this thing and don't want to let it go!:crying::good:
I guess You can insert an SD card with NookManager back and boot properly?
If so lets connect to Your nook via ADB, mount /boot partition and prepare copy of its files.
Code:
mount -o rw,remount rootfs /
mkdir boot
mount -t vfat /dev/block/mmcblk0p1 /boot
[B]...
copy files inside boot partition from
...[/B]
mount -o ro,remount rootfs /
umount /boot
Then put this exact copy onto new (vfat formatted) SD card, and try to boot from new card.
Let us know whats happen.
Is this booting from new SD, showing same fail screens?
Thanks so much for the assistance! I will give it a try and report back.
Also , to note, I do have an old glowlight here that has a cracked screen. Wonder if I could get a copy of it's IMG and use that too?
Trigrammaton said:
... I do have an old glowlight here that has a cracked screen. Wonder if I could get a copy of it's IMG and use that too?
Click to expand...
Click to collapse
Im not quite sure. Another version, etc...
You can use NST boot partition image from this post
For preparing another booting SD card too...
Trigrammaton said:
Thanks so much for the assistance! I will give it a try and report back.
Also , to note, I do have an old glowlight here that has a cracked screen. Wonder if I could get a copy of it's IMG and use that too?
Click to expand...
Click to collapse
If you restore the image from a different device the serial number, MAC address, etc. will be messed up. You will never be able to register the device. This may not be an issue, but just so you are aware.
nmyshkin said:
If you restore the image from a different device the serial number, MAC address, etc. will be messed up.
Click to expand...
Click to collapse
The serial number is written inside the little door for the SD card (if you haven't worn it off).
The serial number and the MAC are also on a sticker in the inside.
ucy74 said:
I guess You can insert an SD card with NookManager back and boot properly?
If so lets connect to Your nook via ADB, mount /boot partition and prepare copy of its files.
Code:
mount -o rw,remount rootfs /
mkdir boot
mount -t vfat /dev/block/mmcblk0p1 /boot
[B]...
copy files inside boot partition from
...[/B]
mount -o ro,remount rootfs /
umount /boot
Then put this exact copy onto new (vfat formatted) SD card, and try to boot from new card.
Let us know whats happen.
Is this booting from new SD, showing same fail screens?
Click to expand...
Click to collapse
Ucy - It boots from nook manager and I am able to use that utility just fine without the failed rom screen. What do you mean by "new" sd? If i put a blank sd into the slot and boot?
When you talk about ADB above and using that - I just download the sdk then use the code you pasted above to copy over the boot partition you linked to my nook (not sd) and try booting like that, correct?
Thanks! I can figure things out with a little guidance, I'm just not really well versed on some of this. Appreciate your help very much!
Trigrammaton said:
Ucy - It boots from nook manager and I am able to use that utility just fine without the failed rom screen.
Click to expand...
Click to collapse
Super, it means so You can connect to Your Nook and dump boot partition files to PC using ADB.
What do you mean by "new" sd? If i put a blank sd into the slot and boot?
Click to expand...
Click to collapse
You can copy files dumped above onto vfat formated SD card. Then try to boot from this "new" - freshly prepared card. Check whats happen.
When you talk about ADB above and using that - I just download the sdk then use the code you pasted above to copy over the boot partition you linked to my nook (not sd) and try booting like that, correct?
Click to expand...
Click to collapse
NOT SO FAST!!! Do not put linked partinion into nook! There are different cases and commands to do that. If You are new to ADB lets try to dump boot partition first, as mentioned before. Maybe there will be not necessary to replace whole partition rather than single file.
Thanks! I can figure things out with a little guidance, I'm just not really well versed on some of this. Appreciate your help very much!
Click to expand...
Click to collapse
Prepare this dumped SD first. We try to heal it to make bootable...
Thanks! I will give it a whirl this weekend and report back. Really appreciate you taking time to respond - Very kind of you!